WANrockIT 200
Fibre Channel Node
User Manual
Eli-v4.05.204
Bridgeworks
Unit 1, Aero Centre, Ampress Lane,
Ampress Park, Lymington,
Hampshire SO41 8LW
Tel: +44 (0) 1590 615 444
Email: support@4bridgeworks.com
Warning
The Bridgeworks WANrockIT 200 Node contains no user serviceable components. Only an
Authorised Service Centre should carry out any servicing or repairs. Unauthorised repairs or
modifications will immediately void your warranty.
Before you start
There are a number of additional pieces of equipment you will require for the successful installation
of your Node:
Ethernet Cable
You will require at least one good quality cable of suitable length to go between your network access
point and the Node. This should be marked as certified to Cat 5e and have an RJ45 style connector
at the Node end.
Fibre Channel Cable
You will require at least one Multi-mode Optical Fibre 50/125 OM3/OM4 Patch Cable (LC) of suitable
length to go between your Node and device, host, or Fibre Channel switch.
If you are in any doubt, please contact your reseller for assistance.
2
Table of Contents
1 Introduction 7
1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.2 Manual Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.3 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.3.1 Logical Unit Number (LUN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.3.2 Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.3.3 Target Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.3.4 Initiating Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.4 Safety Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2 Quick Start Guide 11
3 Installing the WANrockIT 200 Node 12
3.1 Connecting the Ethernet Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.2 Connecting the Fibre Channel Interface . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.3 Connecting the Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4 Using the Web Interface 15
4.1 Browsers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.2 Connecting to the Web Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.3 Management Console (Home screen) . . . . . . . . . . . . . . . . . . . . . . . . . . 17
5 Node Configuration 19
5.1 Network Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
5.1.1 Global Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
5.1.1.1 Hostname . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
5.1.1.2 Enable IPv6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
5.1.2 Network Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
5.1.2.1 Setting the MTU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.1.2.2 Setting the IP Address . . . . . . . . . . . . . . . . . . . . . . . . . 21
3
5.1.2.3 Committing the Changes . . . . . . . . . . . . . . . . . . . . . . . . 21
5.2 Passwords & Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.2.1 System Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.2.2 Secure Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
5.2.3 IPsec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
5.3 Service Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
5.3.1 Simple Network Time Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . 24
5.3.2 Event Notification Email . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
5.3.3 Simple Mail Transfer Protocol (SMTP) . . . . . . . . . . . . . . . . . . . . . . 25
6 WANrockIT Configuration 26
6.1 Node Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
6.1.1 Remote Node Access Whitelist . . . . . . . . . . . . . . . . . . . . . . . . . . 27
6.1.2 Adding Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
6.1.3 Remote Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
6.1.4 Configuring a Node’s Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
6.1.4.1 Setting Primary and Failover Paths . . . . . . . . . . . . . . . . . . 32
6.1.5 Configuring a Node’s Bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . 33
6.1.6 Learning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
6.1.7 Restoring of a Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
6.2 Remote SCSI Target Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
6.2.1 Refreshing SCSI Devices from a Remote Node . . . . . . . . . . . . . . . . . 36
6.2.2 Restoring of Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
6.3 Transfer Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
6.3.1 Data Transmission Performance . . . . . . . . . . . . . . . . . . . . . . . . . 40
6.3.2 Download 24 Hour Transfer History . . . . . . . . . . . . . . . . . . . . . . . 41
7 Fibre Channel Target Connections 43
7.1 Port Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
7.2 Connected Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
7.3 Port Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
4
8 Fibre Channel Initiator Connections 48
9 SCSI Device Management 51
9.1 Viewing Attached Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
9.2 Viewing Device Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
10 Node Maintenance 54
10.1 System Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
10.2 System Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
10.3 Load/Save Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
10.3.1 Saving the Configuration to Disk . . . . . . . . . . . . . . . . . . . . . . . . . 56
10.3.2 Restore to Factory Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
10.4 Firmware Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
10.5 Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
10.6 Task Scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
10.6.1 Adding Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
10.6.2 Removing/Editing Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
10.6.3 Task Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
10.6.3.1 Action - Email Performance Statistics . . . . . . . . . . . . . . . . . 62
10.6.3.2 Action - WANrockIT Bandwidth Limit . . . . . . . . . . . . . . . . . . 63
10.6.3.3 Trigger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
10.6.3.4 Start Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
10.6.3.5 End Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
10.6.3.6 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
11 Troubleshooting 67
11.1 Network Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
11.2 Device Related Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
11.3 Lost IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
11.3.1 Downloading LAN Scan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
11.3.2 Using LAN Scan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
5
Appendix A Accessing the Node from Windows using a static IP Address 69
A.1 Windows Server 2003 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
A.2 Windows Vista, Server 2008 or 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Appendix B Transfer Statistics Graphing Instructions for Excel 2010 75
Appendix C Useful Links 82
Appendix D Technical Specifications 83
6
Introduction
Host WANrockIT Node WANrockIT Node Storage
WAN Link
Site A Site B
Thank you for purchasing the Bridgeworks WANrockIT 200 Node.
The Node has been designed to ensure that in the majority of installations it will require minimal
setup before use. However, we suggest you read the following section which will guide you through
setting up your WANrockIT 200.
Overview
The WANrockIT product range has been designed to connect storage devices over long distance,
high latency, TCP/IP networks with very little loss in performance. It supports all the major storage
protocols such as Fibre Channel, iSCSI and SAS. More interfaces will be added, as they become
part of the mainstream storage protocols.
Each Node’s storage interface can be configured to act either as a target interface - working in a
similar mode to a storage device - or as an initiator - working in a similar mode to a server. Or, if the
WANrockIT Node has multiple storage interfaces, one can be configured to be an initiator and one
as a target device.
A unique part of WANrockIT functionality is that all the Nodes within a WANrockIT installation do
not have to have the same storage interface. A typical configuration is shown in the image below,
where traffic from a server on site A is accelerated over a WAN link to site B.
7
Manual Layout
Throughout the manual, symbols will be used to quickly identify different pieces of information.
This icon represents a note of interest about a step or section of information.
This icon represents an important piece of information.
This icon represents a warning. Care must be taken and the warning should
be read thoroughly.
Definitions
Throughout this manual, selected terms will be used to describe pieces of equipment and concepts.
This section provides an explanation of those terms.
Logical Unit Number (LUN)
Each SCSI device on the SCSI bus can support sub-devices. These are called LUNs.
Node
A Node refers to the physical WANrockIT unit you have purchased.
Target Device
A disk or tape drive connected to a Node.
Initiating Device
A computer or other piece of equipment, which can perform backups connected to a Node.
8
Safety Notices
This device should only be installed by suitably trained personnel.
Protection provided by the equipment may be impaired if used in a manner
not specified by the manufacturer.
Do not block the enclosure’s vents. Air enters from the front and is exhausted
out the back of the device.
This device is connected to the AC power line. Before using the device,
please read the instructions carefully, in order to use the device correctly
and safely. For the installation instructions, refer to Chapter 3: Installing the
WANrockIT 200 Node.
Class I Equipment. This equipment must be earthed. The power plug must
be connected to a properly wired earth ground socket outlet. An improperly
wired socket outlet could place hazardous voltages on accessible metal parts.
Do not attempt to service the equipment yourself. Doing so will void the
warranty and may damage the system. This unit contains hazardous voltages
and should only be opened by a trained and qualified technician. To prevent
electric shock, do not remove the cover. There are no user-serviceable parts
inside.
The power cord is used as a disconnection device. To de-energise the
equipment, disconnect the power cord.
Do not use the equipment where it can get wet. Protect equipment from liquid
intrusion. If your equipment gets wet, disconnect power to the equipment
and to any attached devices. If the Node is connected to an electrical outlet,
turn off the AC power at the circuit breaker before attempting to remove the
power cables from the electrical outlet. Disconnect any attached devices.
Use only the power supply cord set provided with the system for this unit.
Should this not be correct for your geographical area, please contact your
supplier.
The mains plug to the rear of the unit is used as the power disconnect device;
please ensure that this is kept clear from any obstruction and is visible at all
times.
Before installing or removing signal cables, ensure that the power cables for
the system unit and all attached devices are unplugged.
To prevent electrical shock hazard, disconnect the power cable from the
electrical outlet before relocating the system.
9
Class 1 Laser Product: Certain models will use a Small Form factor Pluggable
(SFP) Transceiver module for connection to an optical network. These devices
may use a Class 1 Laser device—it is important that you do not stare into the
Laser beam.
10
Quick Start Guide
The following are basic steps required to setting up your WANrockIT 200. These instructions are
meant for those that have previously read this manual, and are setting up an additional Node. If
this is your first time setting up a Node, please read all the sections in this manual to ensure that all
the parameters of the WANrockIT 200 are set up properly.
1.
Connect the “MGMT” and “WAN” ports found behind the WANrockIT 200 to your network.
See Section 3.1: Connecting the Ethernet Interface.
2.
Connect the Fibre Channel ports found behind the WANrockIT 200 to your Fibre Channel
device and host. By default, Port A (left port) is the Target port, and Port B (right port) is the
Initiator port. See Section 3.2: Connecting the Fibre Channel Interface.
3. Power on the WANrockIT 200. See Section 3.3: Connecting the Power Supply.
4.
If your WANrockIT 200 is in a remote location, use a local Node to Remotely Control it. Add
the remote Node in Node Management and Start Remote Control. See Section 6.1.2: Adding
Nodes.
5.
Login to the web interface and set your new password. See Chapter 4: Using the Web
Interface.
6.
Add a remote node in the Node Management page. See Chapter 6: WANrockIT Configuration.
7.
Perform a Learn between your WANrockIT 200 and the remote node. If the speed between
your nodes is less than what you expect, ensure that the network the WAN port is connected
to is not already congested. See Section 6.1.6: Learning.
8.
Enable devices connected to the remote node using the Remote SCSI Target Management
page. See Section 6.2: Remote SCSI Target Management.
11
Installing the WANrockIT 200 Node
The following are the basic steps to installing the WANrockIT 200:
• Connecting the Ethernet cables
• Connecting the Fibre Channel Interface
• Connecting the Power Supply
Connecting the Ethernet Interface
The WANrockIT 200 Management Interface and onboard WAN Interface can be used on the
following network configurations:
• 10BASE-T
• 100BASE-T
• 1000BASE-T (Gigabit)
It is not necessary to specify which network type you are connected to, as the WANrockIT 200 will
automatically select the correct network speed.
The connection to the management Ethernet network can be found at the back of the WANrockIT
200, labelled “MGMT A”.
To connect the WANrockIT 200 to the management Ethernet network, insert a Cat 5E cable (or
better) into the “MGMT” port at the back of the unit . When the plug is in the correct position a “click”
should be heard. The other end of the cable should be connected to a network.
The WAN port can be found at the back of the WANrockIT 200, labelled “WAN”.
To connect the “WAN” port, insert a Cat 5E cable (or better) in to the port. The other end of the
cable should be connected to a network.
Important:
performance of Node-to-Node data transfer may be affected.
If the “WAN” port is connected to a congested network, the
Connecting the Fibre Channel Interface
With a 8Gb Fibre Channel card installed, the WANrockIT 200 may utilise the following link speeds:
• 2GB
• 4GB
• 8GB
12
It is not necessary to specify which link speed you are using as the WANrockIT 200 will automatically
negotiate the best speed when first powered up.
To connect to the Fibre Channel network, a Small Form-factor Pluggable (SFP) interface module
must be inserted into the SFP receptacle at the back of the WANrockIT 200 as shown in the following
image.
Note:
EU: IEC/EN 60825-1, North America: FCC, CDRH
The following Optical Fibre cables may be used:
• Multi-mode Optical Fibre 50/125 OM3 Patch Cable (LC), up to 300 meters.
• Multi-mode Optical Fibre 50/125 OM4 Patch Cable (LC), up to 550 meters.
When the multi-mode cables are inserted in to the SFP, a “click” should be heard.
Only use SFP transceivers that meet or exceed the following standards:
Connecting the Power Supply
Important:
plug is removed or is switched off.
The WANrockIT 200 contains two power supplies in a redundant supply configuration. The system
evenly distributes power across both power supplies to maximise efficiency. In order to utilise this
feature, please ensure that both power supplies are connected.
Before connecting the power cord, ensure that the wall or rack
Connect the power supply to the rear of the WANrockIT 200 as shown below and turn on the power
from the wall socket.
13
Note:
are properly connected and are powered up, and that you have connected
the Management port and the WAN porto your network.
To turn on the WANrockIT 200 push the switch on the opposite side to the power connector. The
following image shows the switch. Whenever the WANrockIT 200 is powered on, the switch will be
illuminated in the colour green and system fans will be easily heard.
Before powering up the WANrockIT 200, ensure that all peripherals
14
Using the Web Interface
The primary method for configuring any option is through the web interface. The following section
highlights the requirements needed to access the web interface of the Node.
Browsers
This Node supports the following browsers:
• Microsoft Internet Explorer 10
• Microsoft Internet Explorer 11
• Microsoft Edge
• Mozilla Firefox 61.0.1
• Google Chrome 66
1
1
1
Note:
interface.
Important:
browsers, Bridgeworks cannot guarantee the behaviour of the Node’s
functionality.
JavaScript must be enabled within the web browser to use the web
If you choose to use a browser that is not in the list of supported
Connecting to the Web Interface
Note:
• DHCP is enabled by default on the management interface.
• The default hostname is bridgeworks.
• The default static IP address of the management interface is:
Management A 10.10.10.10
If the Node is successfully connected to your DHCP server, and DNS resolution is enabled on
your network by default, you can access the Node’s web interface from the default hostname by
navigating to: http://bridgeworks/
If the Node fails to receive a DHCP address, the web interface can be accessed from the default
static IP address by navigating to: http://10.10.10.10/ or http://10.10.10.12/
1
Latest version as of release
15
Important:
Your host will likely need to be directly-connected to the Node
if DHCP is not enabled, and its subnet set appropriately. See Appendix A:
Accessing the Node from Windows using a static IP Address for help with
accessing the Node web interface without DHCP.
From within your web browser, connect to the Node’s web interface using default hostname or IP
address of a connected management interface.
Once you have connected to the web interface on the Node you will see the entry page shown
below:
Enter and confirm the new web interface password to be presented with the login screen. The
password must be between 5 and 65 characters and can contain symbols and numbers.
To access the web interface a username and password must be used. The default username is:
• Username: admin
16
Management Console (Home screen)
The web interface will now display the Console Home screen as shown below:
Note:
depending on the configuration you have purchased.
The web interface is split into two sections. The left hand Node Menu panel typically remains
constant wherever you are within the web interface. It allows you to reboot or logout of the web
interface. The Home link may be used from any page to return to the Home screen.
The web interface may have different icons to the ones shown above
17
Note:
for the Node to become accessible again.
The Support link will open up a new tab in your browser at the Bridgeworks website support page.
The Help is contextually aware of which page you are currently viewing on the web interface and
will provide you with help relevant to the display and configuration data.
Whenever a Reboot command is issued, it may take several minutes
18
Node Configuration
This section details the configuration of the Node’s basic network and service settings.
Network Connections
This configuration page allows the administrator to configure network interface settings and view
network statistics.
From the Home screen, select the Network Connections icon under the Node Configuration section.
The web interface will display the following:
Global Network Configuration
Hostname
In the Hostname field, enter the name you wish to use to address this Node. It is a good idea to
make the name relevant to the Node’s location and/or purpose.
19
You can then access the web interface from this hostname in future, from any DHCP-enabled
management interface.
Enable IPv6
Selecting the Enable IPv6 checkbox will enable the Node to use IPv6 addresses. As with IPv4, you
can either choose to use DHCP or assign a static IPv6 address.
Network Interfaces
This section displays each network port present on the Node, along with its current status/link
speed, and hardware identifier (MAC address).
To change the settings of a specific network port, click on its icon. The web interface will display the
page for the port.
20
Setting the MTU
Enabling larger frames on a jumbo frame-capable network can improve your network throughput.
Jumbo frames are Ethernet frames that contain more than 1500 bytes of payload (MTU).
Before enabling jumbo frames, ensure that all the devices/hosts located on the network support
the jumbo frame size that you intend to use to communicate with the Node. If you experience
network-related problems while using jumbo frames, use a smaller jumbo frame size. Consult your
networking equipment documentation for additional instructions.
Important:
jumbo frame (MTU) when enabling, as opposed to a simple enable command.
On these switches it might be required to add the necessary bytes needed for
the frame header to the MTU size you specify in the Node’s port configuration.
Typical header size is 28 bytes, so a 9000 byte MTU could translate to a
9028-byte total size. Refer to your switch documentation to understand what
the maximum frame size settings are for your switch.
Setting the IP Address
There are two possibilities when configuring the IP address of a network port:
DHCP
Static IP
The Node will seek out your network’s DHCP server and obtain an IP address for this port
each time it boots.
If the server is not found, this port will fall back to its saved static IP settings.
The IP address, netmask and gateway set in the corresponding fields will be used for
this port.
The gateway field may be left blank.
The IPv4 netmask field must be specified in dotted-decimal form, e.g. 255.255.255.0.
Some networking switches require you to specify the size of the
If IPv6 is enabled from the Network Connections page, you can choose to use DHCP to automatically
assign an IPv6 address, or you can set a static IPv6 address. If you choose to assign a static IPv6
address, you will also need to supply the IPv6 subnet mask in slash notation, e.g.
fe80::1234:ffff:fffe:5678/64
Note: DHCP is enabled by default on management interfaces.
Important:
automatically update the DNS server.
Committing the Changes
Click the Save button to save these parameters, then reboot the Node to apply them.
If DHCP is enabled, please ensure your DHCP server is set to
21
Passwords & Security
This configuration page allows the administrator to change the security settings of the Node.
From the Home screen, select the Passwords & Security icon under the Node Configuration section.
The web interface will display the following:
System Password
This section allows the administrator to change the access password for the web interface. The
new password must be between 5 and 65 characters and can contain symbols and numbers.
Enter the existing password into the Old Password field; then enter the desired new password into
the two following fields. Then click Change Password.
22
Secure Connection
To enable HTTPS, select the Use an encrypted web connection radio button, and click Save.
You will be logged out of the Node’s web interface, and further transactions with the web interface
will use SSL/TLS encryption.
Note:
is enabled.
You can use your own certifcate & key pair by selecting files to upload with the file-picker buttons.
You may upload the key pair as two separate files, or one combined file.
By default, an HTTPS certificate & key will be generated when HTTPS
IPsec
IPsec can be enabled on all WANrockIT connections, using AES encryption. To enable IPsec, tick
the Enable IPsec checkbox, enter a pre-shared key into the Pre-Shared Key field, and click Save.
A matching pre-shared key must be entered on all connected WANrockIT Nodes. This can be a
key of your choosing, or a key can be generated from the Node interface by clicking Generate Key,
and then copying and pasting this key from one Node to each remaining connected Node.
The pre-shared key will not display automatically when returning to the Passwords & Security page.
If you need to copy it to another Node, click the Show Key button.
Important:
connection (i.e. HTTP rather than HTTPS). To ensure your pre-shared key
cannot be intercepted over your network connection, enable HTTPS before
configuring IPsec as explained in Section 5.2.2: Secure Connection.
A warning may appear when configuring IPsec over an unsecured
The entered pre-shared key is saved in a secure configuration store, and is not removed automatically
when IPsec is disabled. To delete your pre-shared key, click Delete Key. This will also disable
IPsec, if enabled.
Service Control
This configuration page allows the administrator to configure network services for the Node. From
the Home screen, select the Service Control icon under the Node Configuration section.
23
The web interface will display the following:
Simple Network Time Protocol
SNTP is a protocol for synchronising the clock of computer systems. This feature is critical if you
are planning on using the scheduler or useful when viewing the logs to determine when an event
occurred. Refer to Section 10.2: System Log for more information.
To enable SNTP, select the Use NTP checkbox and enter the IP address for the NTP Server. Then
click Save.
24
Event Notification Email
The Node can notify a systems administrator when events of a certain urgency occur in the Node
log. Before this can be done, SMTP settings must be saved. Refer to Section 5.3.3: Simple Mail
Transfer Protocol (SMTP) for information on SMTP settings.
To enable email alerts on the Node, select the Enable Email Alerts checkbox. The two following
fields should then be completed:
Recipient Email Address
email addresses can be specified, separated by a semicolon, e.g.:
office@example.com; home@example.com.
Trigger Event Log Level
than the selected level will also trigger an email. The available levels are, in descending order
of urgency:
Critical Example: The Node is running at non-recommended temperatures.
Error Example: A device attached to the Node has been disconnected.
Warning Example: An invalid configuration file was uploaded.
Confirm these settings by clicking Save.
The Test button will send a test email to the recipient email address/addresses to confirm that the
email configuration is working correctly.
The email address/addresses to which the emails will be sent. Multiple
The minimum log level to trigger an email. Events of higher urgency
Simple Mail Transfer Protocol (SMTP)
This section allows an SMTP server to be configured, to send emails on behalf of the Node.
The fields in this subsection are:
SMTP Server
reachable from the Node’s Management interface (or whichever port the default route is set
to) on this address.
Sender Email Address
in-use address; it can be anything your SMTP server will allow. This can be used to identify
the emails from this Node.
Must be of the form: @ .
SMTP Username
blank, depending on your server’s configuration.
SMTP Password Password credential to be used to send emails from the SMTP server. May be
blank, depending on your server’s configuration.
Click Save to apply any changes made to the SMTP configuration.
To enable an SMTP server, enter its IP address or hostname in this field. It must be
The address from which emails will be sent. This needn’t be a previously
Username credential to be used to send emails from the SMTP server. May be
25
WANrockIT Configuration
[ In this guide you will learn how to connect your On-Premise ESXi Node to your Off-Premise Node.
If you are connecting the Nodes with NAT, you will need to setup port forwarding for port 16665 for
the WAN ports of both Nodes, and use their public IP addresses to establish a connection.
If you are going to connect your Nodes without NAT using a private IP address (where your WAN link
is via a VPN or direct connect) you can use the local IP address of your Nodes. ] The WANrockIT
section of the web interface allows the administrator to configure different aspects of the WANrockIT
200.
Node Management
This configuration page allows the adding and removing of Nodes, the instigation of a learning cycle
and the ability to take remote control of other Nodes.
From the Home screen, select the Node Management icon under the WANrockIT section.
The web interface will now display the following:
26
Remote Node Access Whitelist
If the Enable Whitelist drop down is set to None, then all incoming Remote Node Access Control
connections will be accepted. To only allow certain IP addresses to connect to this Node, change
the drop down to Whitelist and click on the Save button.
After navigating back to the Node Management page, the Remove Node Access Control box should
appear as shown:
27
If the whitelist is enabled, another WANrockIT Node will not be able connect to this Node unless the
IP address of any connecting WAN ports is added to the Remote Node Access Control list. To allow
a connection from a remote Node, enter the IP address(es) of the remote Node’s WAN interface(s)
in the space in the Remote Node Access Control table and click on the Add button.
Adding Nodes
Before establishing a connection between nodes it may be necessary to contact your network
administrator to ensure that the required IP protocols & port numbers that will be used for communication
between the devices are available.
28
Protocol/Port
Name Description
TCP 16665 axon-tunnel Reliable multipath data transport for high latencies
UDP 4500 ipsec-nat-t IPsec NAT-Traversal
UDP 500 isakmp Internet Security Association and Key Management Protocol
ESP IP Encapsulating Security Payload
To add a Node, click on the Add Node button on the Node Management page. Type the IP address
of the Node to be connected to in to the IP Address field, in the window shown below, and then
click the Add button.
Important:
Only IPv4 addresses are supported in the Add Remote Node
dialogue box.
The Node will then search for the remote Node on the Network Interface, which will be displayed
with a progress bar.
Once completed, a dialogue window will appear with the Nodes name and the number of target
devices attached to that Node. Any remote Node connection that has been added to the local Node
in this way will be automatically saved, and will restore on reboot until the Node is removed. The
remote Node should then be displayed on the remote Node list as shown:
29
To remove a Node that has been added previously, select the Node you want to remove from the
list, and click the Remove Node button. A confirmation box will appear; click OK to continue.
Remote Control
Remote Control can be used to take control of any other Node added to your local Node. This can
be useful if it is not possible to directly access the web interface of a remote Node at a later time.
To enable remote control of the Node you are currently using, select the Remote Administration
checkbox within the Home Node section at the top of the page; to disable, clear the checkbox.
Once you have chosen, click the Save button.
Select the Node you wish to connect to by clicking on the Nodes IP address or hostname in the
30
Remote Node list, and then click the Start Remote Control button below the list.
The web interface will now display the login screen of the remote Node as normal, and you will
have to login in the normal way using the credentials of the remote Node.
Whenever a remote control session is underway, there will be a yellow bar at the top of the web
interface which will contain the name of the Node you are connected to, as illustrated below:
If you close down the window or tab containing the remote control session, you can navigate back
to the Node Management page on your Local Node, select the Node you previously had remote
control over previously and click the Reload Remote Window button.
When you have finished configuring the remote Node, click the Stop Remote Control button on the
Node Management page to end the remote control session.
31
Configuring a Node’s Paths
The WANrockIT 200 will always attempt to get the best performance possible for the data it is
transferring. Once a link has been established between two Nodes, they will automatically check
for other available connections to each other through their WAN ports. Any available connections
that are found will be set as ‘failover’ paths and will not be used unless the ‘primary’ path fails.
To change the link settings between two Nodes, click on the Configure Node button, and a popup
box will appear as shown:
Setting Primary and Failover Paths
A path is a link between two IP addresses when you establish a link between two WANrockIT Nodes.
This link is set as the ‘primary’ path and is the default connection used by the Nodes.
Once this ‘primary’ path is established, the Nodes will then automatically check for other available
connections to each other through their WAN ports. Any possible connections that are found will
automatically be set as ‘failover’ paths. A failover path will not be used unless the primary path fails.
You can also select a Primary Failover path which will be the first one that is used in the event of a
failure with the primary path. To choose a Primary Failover path, select the path that you wish to
use from the Failover Target/ID drop down box on the far right of the path table.
32
Note:
cannot be manually changed.
To change the primary path, click on the Path Type drop box of the primary path and select Failover
from the drop down list. Click on the Path Type drop box of the path that you wish to set as the new
primary path and select Primary from the drop down list. Click on Apply to save your changes.
The order in which failover paths are used is set automatically and
Note:
will automatically attempt to use all available primary links simultaneously.
A green, red or grey arrow in the Path State box will indicate the state of each path:
• A green arrow pointing upwards means that it is a known link that is up.
• A red arrow pointing downwards means that it is a known link that is down.
•
A grey arrow pointing downwards means that it is an unknown link that is down (only shown if
the Show Unavailable Paths checkbox is checked).
If a path has never been established, the link will be set as inactive and will not be shown by
default. To view all possible connections that may exist between the two Nodes, select the Show
Unavailable Paths checkbox at the bottom of the window. This will now show any possible, but
never established links between the WAN ports of the two Nodes.
Multiple links can be assigned as primary paths; The WANrockIT 200
Configuring a Node’s Bandwidth
If there is other traffic on your network that needs to access a share of your bandwidth, you can
limit the bandwidth between your Nodes. The limit is induced on a per path basis.
To set a limit on a connection, select the Bandwidth Limit checkbox next to the connection that you
wish to limit. This will now allow the text box next to the checkbox to become editable. Type in a
value in megabytes per second and click the Apply button.
Note: The minimum bandwidth limit you can set is 1 MB/s.
To remove a Bandwidth Limit, click on your chosen Node and click the Configure Node button.
Untick the Bandwidth Limit checkbox on the connection that you wish to remove the limit on, and
click Apply. The limit will now be lifted.
Note:
pressing Apply.
Any changes to the bandwidth limit will become instantly effective on
33
Learning
This procedure will “kick start” the Artificial Intelligence module in learning the characteristics of the
link network. Once it has completed it will store these values ready for use whenever data transfer
occurs.
From the Home screen, select the Node Management icon. Select the remote Node that you are
going to use for the learn process from the Remote Node list. Then click on the Learn button just
above the list.
When a Learn process has been started the functionality and name of the Learn button will change
to Stop Learn where the Learn process can be terminated when clicked.
You can start multiple Nodes learning in this way simultaneously by clicking on each one and clicking
Learn.
The web interface will then display the Learning Status window as shown:
Each Node in the process of a “learn”, can be viewed by clicking on the drop down list of Nodes
and selecting the one you wish to monitor.
Once this has completed, as indicated by the bottom text displaying Learn Successful, the pop-up
window can then be closed.
34
Warning:
ends, it will continue in the background. To stop a learning process, navigate
to the Node Management page, click on the remote node in the List of Remote
Nodes and click on the Stop Learn button.
If the Stop Learn button is not shown, then a Learn is not running between
this Node and the remote Node.
If the Learning Status window is closed before the learning process
Restoring of a Node
When your Node has been restarted and is in the process of re-establishing its link to a remote
Node, the remote Node’s name may have (Connecting) after it, as shown:
During this time it will not be possible to use the features of the remote Node. A repeated attempt
at connecting to the remote Node can take up to a minute, and if the Node fails to connect it will
continually retry. After a successful connection, any newly discovered target devices will be added
automatically.
Remote SCSI Target Management
This configuration page will allow you to force a refresh of any SCSI devices that may have been
added to the remote Node.
From the Home screen, select the Remote SCSI Target Management icon under the WANrockIT
section.
35
The web interface will then display the following:
Refreshing SCSI Devices from a Remote Node
To refresh the devices on this list, select the Node you want to refresh the devices on from the Host
Name list by clicking on it. When successfully selected, the Node will become blue.
Click on the Refresh Devices button at the bottom of the screen. The screen will go grey and a
frame will appear with a blue loading bar as shown:
36
When the loading bar is complete, a report will be returned informing you of the progress of the
update. Discovered devices will be displayed the Devices Connected to: window, as shown:
37
Restoring of Devices
When a Node has been restarted and is in the process of re-establishing its link to another Node,
the Node’s name, and the name of any connected devices, may have (Connecting) after them as
shown:
All the functionality that can be used when a Node is active can be used whilst a Node is connecting
but the effects will not occur until the link is up.
Transfer Statistics
This configuration page will allow you to monitor, in real time, the performance of a link over the
span of a minute and to download the performance of the rig over the last 24 hours.
From the Home screen, select the Transfer Statistics icon under the WANrockIT section.
38
The GUI will now display the following window:
A Node will be offline if the link between two Nodes has not been re-established after a system
restart. You cannot start the monitoring of the Node until the link has been re-established. An offline
39
Node is indicated if the name of the Node has Offline next to it, as shown:
Data Transmission Performance
This section shows you both the transmit and the receive rate for any selected Nodes. The transmit
rate for a Node is in blue and the receive rate is in red. To view a Nodes transfer rate, click on the
name of the Node from the Remote Nodes list, and graphing will start automatically.
40
Download 24 Hour Transfer History
You are able to download the transfer rate statistics of the previous 24 hours by clicking on the
Click Here to Download button. The downloaded file is in .csv format and can then be viewed in a
compatible program. See Appendix B: Transfer Statistics Graphing Instructions for Excel 2010 for
more information.
41
Note: The 24 hour statistics are cleared on reboot.
42
Fibre Channel Target Connections
This configuration page allows the administrator to configure the Fibre Channel Interface of the
Node.
From the Home screen of the web interface, select the FC Target icon from the Devices and
Protocols section.
The web interface will then display the following:
The icons displayed in the Fibre Channel Interfaces section show the current state of each Fibre
Channel Port.
The green or red light in the icon display whether the port is up or down. This is also shown in text
next to each icon with the negotiated Fibre Channel speed and the selected topology. The port
WWN is also shown next to each icon.
Clicking on an icon will display different options related to the specific port as shown:
43
Port Configuration
Selecting the Configuration settings icon will display the following:
The first parameter is the Port Enable check box. Check this to enable the link onto the Fibre
Channel Storage Area Network (SAN).
The Link Speed drop down menu allows you to select the Fibre Channel network speed. In most
cases this can be kept as Automatic.
The Topology drop down menu allows you to force the Fibre Channel topology when the Node logs
on to the Fibre Channel SAN.
44
Note:
conversant with the lower levels of the Fibre Channel protocol, as certain
AL_PA addresses are reserved.
The Enable tERP check box, which is only present for 8Gb/s cards, will enable or disable the Target
Error Recovery Protocol for the port. tERP will attempt to recover frames that are missed or time
out during transfer. For tERP to correctly function, the connected initiator must also support tERP.
Clicking Save will save the configuration to memory for use at the next reboot.
It is recommended to leave Hard AL_PA unchecked unless you are
Connected Hosts
To list which hosts are connected to the Node, select a port under Fibre Channel Interfaces, then
select the icon labelled View all the Fibre Channel initiators which have logged into this target port.
The following will then be displayed:
Port Map
The Port Map page allows the administrator to assign devices to Fibre Channel ports with a fixed
Logic Unit Number (LUN).
Once the Fibre Channel interface has been configured, the target devices can be assigned to the
Fibre Channel ports.
From the Fibre Channel Target Management Console page select the Port Map icon.
45
The following will be displayed:
There are two choices from the drop down list:
Automatic
will assign all devices to all Fibre Channel target ports, so that any connected host will
see all devices.
Manual
will allow the administrator to manually assign which target devices appear on which Fibre
Channel port.
Important:
When Automatic port mapping is selected, LUN order is not
guaranteed to be the same between reboots.
Selecting Manual will show the following:
46
To assign a target device to a Fibre Channel Port:
1. Select a target device from the list in the Device & Logical Unit drop down menu.
2. Select which Fibre Channel Port you wish the device to appear on.
3. Select the LUN you wish the device to have on the selected Fibre Channel Port.
4. Click the Add Assignment button at the bottom of the panel.
The example above shows 1 device assigned to Port 1A with the LUN 0.
47
Fibre Channel Initiator Connections
The configuration page shown below will allow the administrator to configure ports designated as
Fibre Channel Initiator interfaces.
From the Home screen of the web interface, select the FC initiator icon from the Devices and
Protocols section.
You will see the following page:
This page lists each Fibre Channel port which has been designated as an initiator. Three pieces of
information are displayed about each port next to an icon. In order they are:
Port designation
that this is the left, or right-hand port of that slot, respectively.
Current state
of the link if it is currently up.
WWPN The unique World Wide Name identifier for this port.
Selecting one of the icons will navigate to the page for that initiator port, with 3 options:
the number is the designation of the PCI slot, and the letter ‘A’ or ‘B’ denotes
This shows whether the Fibre Channel link for this port is up or down, and the speed
48
Display status information for this Fibre Channel port
allows you to see verbose information
about the Fibre Channel port.
Configuration settings allows you to manually configure the Link Speed and Port Topology:
1.
The Link Speed drop down menu has the following options: Auto, 2 Gbit, 4 Gbit, and 8
Gbit. In most cases this option may be left set to Auto. If you are unsure, set the link
speed to the SFP speed.
2.
The Topology pull down menu has 3 options: Auto, Loop (arbitrated Loop, FC-AL), and
Point-to-Point (FC-P2P). It is recommended that you leave this option at Auto unless
you wish to force the link into a known topology.
Configure the initiator port to connect to only specified devices
connected Fibre Channel targets.
49
allows you to disable certain
The default configuration type is set to Automatic. Using the Configuration Link drop down,
you can change this to manual. This allows you to enable or disable each individual target on
the Fibre Channel link.
Select the FC target by clicking on its World Wide Port name, and then click enable or disable.
50
SCSI Device Management
The SCSI Device Management page of the web interface allows the administrator to view details of
devices connected to the WANrockIT 200, and devices attached to a connected remote node.
Viewing Attached Devices
From within the Home screen of the web interface, select the SCSI Device Management icon under
the Devices and Protocols section.
The web interface will then display the following:
You will be presented with a list of all the devices connected to the WANrockIT 200.
If your WANrockIT 200 is connected to a remote Node, devices connected to the remote Node will
also be displayed on this page under the Devices registered from other WANrockIT Nodes section.
Clicking on a device will open a page displaying more information about the device, as shown
below.
51
Viewing Device Mappings
Clicking on the Mappings option in the menu on the left-hand side of the page will display information
about all connected devices, as shown in the following image.
52
A target entry exists on this page for each device that is presented on the system. Two or more
entries may exist for a device, representing the mapping to the AI as well as the mapping to a
physical interface.By clicking on the blue triangle in the Device Info section you can display further
information about each device.
53
Node Maintenance
The following section describes the various pages that are available to the administrator to monitor
performance and maintain the Node.
System Information
The System Information page allows the administrator to view the performance of the Node. From
the Home screen, select the System Information icon from the Node Maintenance section.
The following page will be displayed:
In the Node & Firmware Details section, the following information is displayed:
Firmware Revision is the installed firmware revision level.
Serial Number/UUID is the unique identifier of that specific WANrockIT 200.
Uptime is the amount of time the WANrockIT 200 has been powered on for.
The System Performance section contains three meters which provide an approximation of the
54
following performance parameters:
Data Throughput This indicates the current performance in MB/s.
CPU Utilisation
management and scheduling the transfer of data between the two interfaces.
Memory Usage This indicates the percentage of memory used by all processes.
This indicates the percentage of the time the CPU is occupied undertaking the
System Log
This page displays the system log, useful for diagnosing problems with the Node, attached devices
and connections.
From the Home screen, select the System Log icon from the Node Maintenance section.
The web interface will now display the following:
55
Below the log display pane are two options:
Click Here to Download This will download the log file to your local machine.
Clear System Log This will clear all logs within the Node.
For information on troubleshooting your Node, see Chapter 11: Troubleshooting.
Load/Save Configuration
Saving the Configuration to Disk
Once you have finished configuring your Node we recommend that you save your configuration
data to a local disk. By doing so you could save valuable time if the Node requires replacement or
if configuration is lost during upgrades.
From the Home screen, select the Load/Save Configuration icon from the Node Maintenance
section.
The following page will be displayed:
To save the configuration data, click on the Click here to Download link from within the Export
Configuration subsection. Then choose to save the file.
56
The Node will now download an encoded file that contains all of its configuration settings.
To reload the configuration, click on the Browse button and locate the configuration file to upload to
the Node. Once located, click the upload button and the new configuration data will be uploaded.
Once the configuration file is uploaded, a reboot is required.
Restore to Factory Defaults
By clicking on this button all the parameters will be set back to the factory defaults. This includes IP
address, hostname and passwords. This option is useful to protect sensitive information if a Node
appliance is ever returned for maintenance.
Firmware Updates
From time to time it may be necessary to upgrade the firmware within the Node. New versions
contain resolutions to known issues as well as new features and improvements to the functionality
of the Node.
It is recommended to check for new versions of the firmware downloadable from the Bridgeworks
web site at:
http://www.4bridgeworks.com/support/download-firmware/
Warning:
unless you have been instructed to by the Bridgeworks support team. Always
ensure that you have the correct firmware for your product.
The Firmware Updates page allows the administrator to load new firmware onto the Node. From
the Home screen, select the Firmware Updates icon from the Node Maintenance section.
The following page will be displayed:
Do not load on a firmware which has an earlier release revision
IF IN DOUBT, ASK.
57
Once you have downloaded the new firmware to your local machine:
1. Click on the Browse button to locate the file you have downloaded from our website.
2.
Click on the Update button to start. A progress bar labelled Uploading will appear showing
the progress in uploading the new firmware on to the WANrockIT 200.
3.
When the label above the progress bar changes to Progress, you can navigate away from
this page and the installation will continue.
Updating the firmware will take a few minutes. After the update is complete, a notification will
appear under the Node Menu, indicating that a system reboot is necessary. To reboot the Node,
click on the Reboot button located in the Node Menu at the left side of the web interface.
Diagnostics
In the unlikely event that a problem arises with your WANrockIT 200, you may be requested by
Bridgeworks Support to provide a diagnostic file.
Important:
Troubleshooting for information on how the issue may be resolved.
Note:
Video “WANrockIT: Downloading Diagnostic Information” found at
//www.youtube.com/watch?v=8RZXFGCy3ZU.
To download the diagnostic file, click on the Diagnostics icon on the Home screen:
If an issue arises with your WANrockIT 200, check Chapter 11:
The following instructions are demonstrated in the Bridgeworks Support
58
https:
On the Diagnostics page, click on the Click Here to Download button.
Pressing the button will cause the WANrockIT 200 to collect data regarding various modules and
storing them in to a single file. Once this process is completed, a download for “diagnostics.bin” will
begin.
Task Scheduler
The Task Scheduler page allows the administrator to schedule tasks with the following actions:
Email Performance Statistics
address(es).
WANrockIT Bandwidth Limit
of Megabytes per second.
From the Home screen, select the Task Scheduler icon from the Node Maintenance section.
The web interface will now display the following:
This will email the log of the throughput rate to a given email
This will restrict the WANrockIT transmission rate to a given number
59
Adding Tasks
Tasks can be added by clicking on the Add New Scheduling Task button, which will start the task
wizard.
Removing/Editing Tasks
If you already have some tasks added, they will be listed in the Scheduled Tasks window as shown:
60
Clicking on a task will expand it as shown:
Clicking the Remove button will remove the task from the task scheduler. Clicking the Edit button
will start the task wizard for the task, allowing it to be edited.
61
Task Wizard
The task wizard will guide you through the adding or editing of scheduled tasks. There are a few
common buttons across the individual sections of the wizard:
Help Clicking this button will display the Online Help page for the Task Scheduler.
Cancel
Next If present, this button will navigate you to the next section of the wizard.
Previous If present, this button will navigate you to the previous section of the wizard.
Action - Email Performance Statistics
Clicking this button will discard the changes being made to the task and close the wizard.
Note:
on the left-hand side.
The currently active section of the wizard will be highlighted in orange
On the Action section of the wizard, enter the recipient email(s), separating multiple emails with
either commas or semi-colons.
Important:
to the Service Control page where SMTP can be set up. See Section 5.3.3:
Simple Mail Transfer Protocol (SMTP).
If you see the following image, click on the yellow box to be taken
62
Action - WANrockIT Bandwidth Limit
On the Action section of the wizard, enter a bandwidth limit in Megabytes per second or select the
Unlimited Bandwidth checkbox. Then select which Node should be affected by the bandwidth limit.
63
Trigger
On the Trigger section of the wizard, you can pick the frequency of the event. The options are:
Once This means the action will be performed at the specified time and not repeat.
Daily This means the action will be performed every day at the specified time.
Weekly
This means the action will be performed on specified days every week at the specified
time. When selecting this option, you will be able to pick which days to trigger the action by
selecting checkboxes. Each day will have its own checkbox, as shown:
64
Start Date
On the Start Date section of the wizard, you can pick the starting date and time for the new task.
Enter a time into the Time for the first trigger box and select your start date using the calendar. The
selected date will be marked with a red cross.
End Date
65
On the End Date section of the wizard, you can pick the end date for the new task. You can either
select the Ongoing Event checkbox for a task that should run until cancelled, or select a date using
the calendar. The selected date will be marked with a red cross.
Summary
On the Summary section of the wizard, a brief description of the task will be displayed. If you
are happy with this task, click the Save button to add the task to the task scheduler. Saving will
automatically close the wizard.
66
Troubleshooting
Network Problems
Under normal operation, you should be able to “ping” the network address of the Node and receive
a response. If this fails, run through the following checklist to help you identify the problem.
• Make sure that the power LED on the Node is illuminated.
• Ensure that the Ethernet cable is plugged in at both ends.
•
Note the status of the LEDs positioned within the Ethernet connector - make sure that the
Link present LED is illuminated. If it is not, check with your Network Administrator.
•
If the Node is transferring large amounts of data, then the response from the web interface
may seem slower than usual as the process that controls the web interface has the lowest
priority for Network and CPU resources.
•
If you can “ping” the Node but the web interface fails to appear, check the settings within the
web browser you are using. If you are directly connected to the Node then any proxy settings
will require adjustment and may require you to contact your administrator.
•
Ensure you are using the correct network address and netmask. See Appendix A: Accessing
the Node from Windows using a static IP Address.
•
Scan the network using the LAN Scan utility to find all the Node’s connected to the network in
case the network address is different than what was expected. See Section 11.3: Lost IP
Address.
If none of the above resolves your problem, then after consulting with your Network Administrator,
please contact support. See Appendix C: Useful Links for information on how to contact Bridgeworks
Support.
Device Related Problems
Once the Node has finished booting up, and the target devices have finished initialising, these
devices should be available on the host machine. After checking that you have correctly configured
the initiator, run through the following checklist to help you identify and solve the problem.
•
Ensure that the devices are powered on and are ready - some libraries can take 5 minutes or
more before they are ready and appear on the Node. The power up status of libraries are
usually displayed on the front panel.
If none of the above resolves your problem, please contact support. See Appendix C: Useful Links
for information on how to contact Bridgeworks Support.
Lost IP Address
The utility “LAN Scan” can be used to find any device irrespective of its IP address. This can be
helpful in determining the IP address of a Bridgeworks device with an unknown IP address and for
67
checking the number of Bridgeworks devices on a network.
Downloading LAN Scan
The utility can be downloaded from:
http://www.4bridgeworks.com/support/download-firmware/
LAN Scan may also be provided on the CD accompanying your WANrockIT 200.
Using LAN Scan
LAN Scan is a command line utility available for Windows.
The downloaded file is in .zip format and contains the files lanscan.exe and lanscan.bat.
To launch LAN Scan, double click on lanscan.bat. This will create a file named lanscan.txt. Open
lanscan.txt within a text editor to view the discovered Bridgeworks devices as shown:
68
Accessing the Node from Windows using
a static IP Address
This appendix describes how to configure a Windows host to access the Node’s web interface from
its default static IP address, if DHCP is not enabled on the Node.
Windows Server 2003
If your computer is running Windows Server 2003, follow the instructions below.
From the Desktop or Start menu, select My Computer.
In the My Computer window select Network and Dial-up Connections positioned in the bottom left
hand corner.
From within the displayed Network and Dial-up Connections select the interface connection that will
be used to connect to the Node - in this example we have selected the Gigabit Ethernet interface.
69
A general status page will be displayed. From within this page select Properties.
Select the Internet Protocol (TCP/IP) entry and then Properties.
70
Make a note of your current set up, then:
1. Click Use the following IP Address.
2. Enter 10.10.10.11 into the IP Address field.
3. Enter 255.255.255.0 into the Subnet Mask field.
4. Finally click the OK button.
71
Note:
computer to the original settings and reconnect to the Node.
Once you have completed the initial set up of the Node, return your
Windows Vista, Server 2008 or 7
If your computer is running Windows, Vista or 7 follow the instructions below.
From the Start menu, select Control Panel.
From the Control Panel select the Network and Internet link, followed by the Network and Sharing
Centre link. Click on Local Area Connection.
72
A general status page will be displayed. From within this page select Properties.
Select the Internet Protocol Version 4 (TCP/IPv4) entry and then Properties.
73
Make a note of your current set up, then:
1. Click Use the following IP Address.
2. Enter 10.10.10.11 into the IP Address field.
3. Enter 255.255.255.0 into the Subnet Mask field.
4. Finally click the OK button.
Note:
computer to the original settings and reconnect to the Node.
Once you have completed the initial set up of the Node, return your
74
Transfer Statistics Graphing Instructions
for Excel 2010
Open Microsoft Excel 2010. From the Open dialogue, navigate to the download location for the
transfer statistics. Open the file type drop down box and select the transfer statistics .csv file as
shown:
Note:
200, see Section 6.3.2: Download 24 Hour Transfer History.
Select the A column of the newly generated worksheet, right-click, and select Format Cells.
For information on obtaining transfer statistics from your WANrockIT
75
From the Number tab, select the Time category, and select the option
then click OK.
*13:30:55
as shown below
Note:
displayed in the final graph.
The time format chosen here is not the format in which the time will be
76
Select the first two rows (row 1 and row 2) then right-click and select Delete.
Select the first column by clicking on A. Then, hold down the
Ctrl
key on the keyboard and select
the columns B and C. The three columns should now be selected as shown below:
Warning:
Selecting all three columns at the same time may cause errors in
generating the graph in the following steps. Remember to select column A
first and then the other two columns with the Ctrl key held down.
On the Insert tab, in the Charts group, select the Line chart type and then the first icon shown.
77
A new chart will be created. Right click the vertical axis on this chart and select Format Axis.
78
From the Number tab, select the Custom category. Enter the following in the Format Code field:
#,,"MB/s"
Click Add, then Close.
Now right click the horizontal axis and select Format Axis.
79
From the Number tab, select the Time category. Select the format you wish for the time to be
displayed.
80
Alternatively, you can use a custom format for the date. In this case, select the Custom category,
and enter your custom format in to the Format Code text field. The following is an example of a
format code:
m/d/yy h:mm AM/PM
Click Add and then Close. Your chart should now look like the following:
81
Useful Links
Frequently Asked Questions
asked questions page may be able to help:
Bridgeworks Support
contact support at http://www.4bridgeworks.com/support/.
Bridgeworks Support Videos
in this manual. https://www.youtube.com/user/SANSlide/.
Product Manuals
support/user-manuals/.
If you continue to experience problems with the WANrockIT 200, please
The latest product manuals can be found at
If you experience problems with the WANrockIT 200, the frequently
http://www.4bridgeworks.com/support/faqs/
These videos will guide you through some of the instructions found
http://www.4bridgeworks.com/
82
Technical Specifications
Physical
Form Factor 1900rack mount
Overall Depth 673.3mm with redundant PSU, 656.2mm with cabled PSU
Rack Depth Required 612.6mm
Height 42.8mm
Width 482.4mm with rack latches
Weight 19.3kg at maximum configuration
Recommended minimum
clearance for cooling
Electrical
Input voltage 100–240V
Frequency 50–60Hz
Input current 4A max.
Maximum power consumption
Environmental
Operational temperature 10◦C to 35◦C
Non-operational temperature –20◦C to 60◦C
Humidity 8–85% non-condensing
Network Management
Interface
No. of interfaces 1
Physical RJ45 (8P8C)
Speed Auto-sensing 10 / 100 / 1000Mb/s
Standards IPv4, IPv6, NTP, SNMP, DHCP
WAN Interface
No. of interfaces 1
Physical RJ45 (8P8C)
Speed Auto-sensing 10 / 100 / 1000Mb/s, Limited to 200MB/s over
Maximum number of Nodes 1
Fibre Channel Interface
No. of interfaces 2
Physical SFP mini GBIC
Speed Auto-sensing 2 / 4 / 8Gb/s
Standards FC-AL, FC-PLDA, FC-PH, FC-FLA, FCP-SCSI, FC-FS,
Topology NL_port, FL_port, N_port, F_port
Visual Indicators
100mm on front and rear faces
350W approx.
all WAN interfaces for each connected remote Node
FC-TAPE
Power
Network Link, Activity & Speed
Fibre Channel Link & Status
83
Loading...