Bridgeworks Oresund EFC402200 User manual

Oresund
EFC402200
iSCSI to FC Gateway
User Manual
Eli-v4.05.204
Bridgeworks
Unit 1, Aero Centre, Ampress Lane,
Ampress Park, Lymington,
Hampshire SO41 8LW
Tel: [phone]
Email: [email protected]

Warning
The Bridgeworks Oresund EFC402200 iSCSI to Fibre Channel Gateway 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 Gateway:
Ethernet Cable
You will require at least one good quality cable of suitable length to go between your network access
point and the Gateway. This should be marked as certified to Cat 5e and have an RJ45 style
connector at the Gateway end.
40Gb QSFP Cable
To connect the Gateway to your network for iSCSI transfer, you will require a copper QSFP cable.
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 Gateway 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 ManualLayout ....................................... 8
1.1.1 iSCSITargetDevice ................................ 8
1.1.2 iSCSI Qualified Name (IQN) . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.1.3 CHAP........................................ 8
1.1.4 SCSITargetDevice ................................ 8
1.1.5 Logical Unit Number (LUN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.2 SafetyNotices ....................................... 10
2 Installing the EFC402200 Gateway 12
2.1 Connecting the Ethernet Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.2 Connecting the 40Gb QSFP Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.3 Connecting the Fibre Channel Interface . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.4 Connecting the Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3 Using the Web Interface 16
3.1 Browsers .......................................... 16
3.2 Connecting to the Web Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3.3 Management Console (Home screen) . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4 Gateway Configuration 19
4.1 NetworkConnections ................................... 19
4.1.1 Global Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.1.1.1 Hostname ................................ 20
4.1.1.2 EnableIPv6 ............................... 20
4.1.2 NetworkInterfaces................................. 20
4.1.2.1 SettingtheMTU............................. 21
4.1.2.2 Setting the IP Address . . . . . . . . . . . . . . . . . . . . . . . . . 22
4.1.2.3 Committing the Changes . . . . . . . . . . . . . . . . . . . . . . . . 22
3

4.2 Passwords&Security ................................... 22
4.2.1 SystemPassword ................................. 23
4.2.2 SecureConnection................................. 23
4.3 ServiceControl....................................... 24
4.3.1 Simple Network Time Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . 25
4.3.2 Event Notification Email . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
4.3.3 Simple Mail Transfer Protocol (SMTP) . . . . . . . . . . . . . . . . . . . . . . 26
4.3.4 Internet Storage Name Service (iSNS) . . . . . . . . . . . . . . . . . . . . . . 26
5 iSCSI Target Configuration 28
5.1 Authorisation(CHAP) ................................... 28
5.2 NetworkInterfaces..................................... 29
5.3 iSCSISessions....................................... 29
6 Fibre Channel Initiator Connections 31
7 SCSI Device Management 34
7.1 ViewingAttachedDevices................................. 34
7.2 ViewingDeviceMappings................................. 35
8 Gateway Maintenance 37
8.1 SystemInformation..................................... 37
8.2 SystemLog......................................... 38
8.3 Load/SaveConfiguration ................................. 39
8.3.1 Saving the Configuration to Disk . . . . . . . . . . . . . . . . . . . . . . . . . 39
8.3.2 Restore to Factory Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
8.4 FirmwareUpdates ..................................... 40
8.5 Diagnostics ......................................... 42
8.6 TaskScheduler....................................... 42
8.6.1 AddingTasks.................................... 43
8.6.2 Removing/Editing Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
8.6.3 TaskWizard .................................... 45
4

8.6.3.1 Action - Email Performance Statistics . . . . . . . . . . . . . . . . . 45
8.6.3.2 Trigger .................................. 46
8.6.3.3 StartDate ................................ 47
8.6.3.4 EndDate................................. 48
8.6.3.5 Summary................................. 48
9 Troubleshooting 50
9.1 NetworkProblems ..................................... 50
9.2 DeviceRelatedProblems ................................. 50
9.3 PoorPerformance ..................................... 51
9.4 LostIPAddress....................................... 52
9.4.1 DownloadingLANScan.............................. 52
9.4.2 UsingLANScan .................................. 52
Appendix A Accessing the Gateway from Windows using a static IP Address 53
A.1 WindowsServer2003 ................................... 53
A.2 Windows Vista, Server 2008 or 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Appendix B Connecting to an iSCSI Device using the Microsoft iSCSI Initiator 59
B.1 GeneralSetup....................................... 59
B.2 DiscoveryofDevices.................................... 60
B.2.1 Adding an iSCSI Target Portal . . . . . . . . . . . . . . . . . . . . . . . . . . 61
B.2.2 AddinganiSNSServer .............................. 63
B.3 ConnectingtoaTarget................................... 64
B.4 Viewing iSCSI Session Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
B.5 Creating Multiple Connections (Optional) . . . . . . . . . . . . . . . . . . . . . . . . 68
B.6 Logging off an iSCSI Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Appendix C Connecting to an iSCSI Device using iscsiadm 74
C.1 DiscoveringiSCSITargets................................. 74
C.2 Loggingintoatarget.................................... 75
C.3 Loggingoutofatarget................................... 77
5

C.4 Loggingoutofalltargets.................................. 78
Appendix D Useful Links 80
Appendix E Technical Specifications 81
6

Introduction
Thank you for purchasing the Bridgeworks Oresund EFC402200 iSCSI to Fibre Channel Gateway.
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.
iSCSI Target Device
iSCSI target devices are devices such as disk drives, tape drives or RAID controllers that are
attached to the network. Each device is identified by an IQN (iSCSI Qualified Name).
iSCSI Qualified Name (IQN)
Anything connected to a network, be it a computer, printer or iSCSI device must have a unique
identifier, such as an IP address, to enable other devices to communicate with it. With iSCSI devices
(both targets and initiators) an extra level of identification in addition to the IP address is employed.
This is called the IQN. The IQN includes the iSCSI Target’s name and an identifier for the shared
iSCSI device.
Example: 2002-12.com.4bridgeworks.sdt600a014d10:5
CHAP
CHAP is an authentication scheme used by Servers to validate the identity of clients and vice versa.
When CHAP is enabled, the initiator must send the correct Username and Target Password to gain
access to the iSCSI Bridge. The Initiator Secret is provided to allow iSCSI mutual CHAP. If mutual
CHAP is selected on the Initiator, the iSCSI Bridge will authenticate itself with the initiator using the
initiator secret.
SCSI Target Device
A SCSI device is a device that is connected to the SCSI bus that can be accessed by the Server.
Each device on the SCSI bus has a Unique ID number in the range 0-15.
8

Note: By convention, ID 7 on the SCSI Bus is reserved by the Server’s Host
Bus Adaptor.
Logical Unit Number (LUN)
Each SCSI device on the SCSI bus can support sub-devices. These are called LUNs. Within the
iSCSI Connect Bridge each SCSI ID on the SCSI bus can support 7 LUNs.
9

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 2: Installing the
EFC402200 Gateway.
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 Gateway 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.
10

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.
11

Installing the EFC402200 Gateway
The following are the basic steps to installing the EFC402200:
• Connecting the Ethernet cables
• Connecting the 40Gb QSFP cables
• Connecting the Fibre Channel Interface
• Connecting the Power Supply
Connecting the Ethernet Interface
The EFC402200 Management 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 EFC402200 will
automatically select the correct network speed.
The connection to the management Ethernet network can be found at the back of the EFC402200,
labelled “MGMT A” and “MGMT B”.
To connect the EFC402200 to the management Ethernet network, insert a Cat 5E cable (or better)
into one of the “MGMT” ports at the back of the unit as shown in the following image. 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.
12

Rear Panel of the EFC402200 Showing Ethernet Cable Connections
Connecting the 40Gb QSFP Cables
To connect the Gateway to your network for iSCSI transfer, you will require a copper QSFP cable.
To connect the Gateway to your network, insert a QSFP cable into one of the ports as shown below.
When fully inserted the cable should ‘click’ and latch securely into place.
Depending on the configuration you have purchased one of two cables will be required for your
product.
13

Connecting the Fibre Channel Interface
With a 16Gb Fibre Channel card installed, the EFC402200 may utilise the following link speeds:
• 4GB
• 8GB
• 16GB
It is not necessary to specify which link speed you are using as the EFC402200 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 EFC402200 as shown in the following
image.
Note: Only use SFP transceivers that meet or exceed the following standards:
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.
Connecting the Power Supply
Important: Before connecting the power cord, ensure that the wall or rack
plug is removed or is switched off.
14

Connect the power cord to the rear of the EFC402200 as shown in the following image.
Note: Before powering up the EFC402200, ensure that all peripherals are
properly connected and are powered up, and that you have connected a
Management port to your network.
To turn on the EFC402200 push the switch on the opposite side to the power connector. The
following image shows the switch. Whenever the EFC402200 is powered on, the switch will be
illuminated in the colour green and system fans will be easily heard.
15

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 Gateway.
Browsers
This Gateway supports the following browsers:
• Microsoft Internet Explorer 10
• Microsoft Internet Explorer 11
• Microsoft Edge1
• Mozilla Firefox 61.0.1 1
• Google Chrome 66 1
Note: JavaScript must be enabled within the web browser to use the web
interface.
Important: If you choose to use a browser that is not in the list of supported
browsers, Bridgeworks cannot guarantee the behaviour of the Gateway’s
functionality.
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 interfaces are:
Management A (left-hand interface) 10.10.10.10
Management B (right-hand interface) 10.10.10.12
If the Gateway is successfully connected to your DHCP server, and DNS resolution is enabled on
your network by default, you can access the Gateway’s web interface from the default hostname by
navigating to: http://bridgeworks/
1Latest version as of release
16

If the Gateway 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/
Important: Your host will likely need to be directly-connected to the Gateway
if DHCP is not enabled, and its subnet set appropriately. See Appendix A:
Accessing the Gateway from Windows using a static IP Address for help with
accessing the Gateway web interface without DHCP.
From within your web browser, connect to the Gateway’s web interface using default hostname or
IP address of a connected management interface.
Once you have connected to the web interface on the Gateway 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
17

Management Console (Home screen)
The web interface will now display the Console Home screen as shown below:
The web interface is split into two sections. The left hand Bridge 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.
Note: Whenever a Reboot command is issued, it may take several minutes
for the Gateway 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.
18

Gateway Configuration
This section details the configuration of the Bridge’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 Bridge Configuration
section.
The web interface will display the following:
19

Global Network Configuration
Hostname
In the Hostname field, enter the name you wish to use to address this Gateway. It is a good idea to
make the name relevant to the Gateway’s location and/or purpose.
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 Gateway 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 Gateway, 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