Brocade ISCSI Gateway MGR v326 Admin Guide

iSCSI Gateway Manager
Administrators Guide
Supporting Brocade iSCSI Gateway
Publication Number: 53-1000203-01 Rev. A
Copyright 2006, SANRAD, Inc..

ALL RIGHTS RESERVED.
Publication Number: 53-1000203-01 Rev. A
This manual contains information that is proprietary to SANRAD. No part of this publication may be reproduced in any
form whatsoever without prior written approval by SANRAD.
Right, title and interest, all information, copyrights, patents, know-how, trade secrets and other intellectual property or
other proprietary rights relating to this manual and to the StoragePro Management System and any software components
contained therein are proprietary products of SANRAD protected under international copyright law and shall be and
remain solely with SANRAD.
StoragePro Management System is a registered trademark of SANRAD. No right, license, or interest to such trademark
is granted hereunder, and you agree that no such right, license, or interest shall be asserted by you with respect to such
trademark.
Brocade, the Brocade B weave logo, Secure Fabric OS, and SilkWorm are registered trademarks and Tapestry is a
trademark of Brocade Communications Systems, Inc., in the United States and/or in other countries. All other brands,
products, or service names are or may be trademarks or service marks of, and are used to identify, products or services of
their respective owners.
Notice: The information in this document is provided AS IS, without warranty of any kind, including, without
limitation, any implied warranty of merchantability, noninfringement or fitness for a particular purpose. Disclosure of
information in this material in no way grants a recipient any rights under Brocade's patents, copyrights, trade secrets or
other intellectual property rights. Brocade reserves the right to make changes to this document at any time, without
notice, and assumes no responsibility for its use.
The authors and Brocade Communications Systems, Inc. shall have no liability or responsibility to any person or entity
with respect to any loss, cost, liability, or damages arising from the information contained in this book or the computer
programs that accompany it.
Export of technical data contained in this document may require an export license from the United States Government.
Brocade Communications Systems, Incorporated

Corporate Headquarters
Brocade Communications Systems, Inc.
1745 Technology Drive
San Jose, CA 95110
Tel: 1-408-333-8000
Fax: 1-408-333-8101
Email: info@brocade.com
Asia-Pacific Headquarters
Brocade Communications Singapore Pte. Ltd.
9 Raffles Place
#59-02 Republic Plaza 1
Singapore 048619
Tel: +65-6538-4700
Fax: +65-6538-0302
Email: apac-info@brocade.com
European and Latin American Headquarters

Brocade Communications Switzerland Srl
Centre Swissair
Tour A - 2me tage
29, Route de l'Aroport
Case Postale 105
CH-1215 Genve 15
Switzerland
Tel: +41 22 799 56 40
Fax: +41 22 799 56 41
Email: emea-info@brocade.com
Document History
Document Title
Publication Number
Summary of Changes
Publication
Date
Brocade iSCSI Gateway

Manager Administrators Guide
53-1000203-01 Rev. A
New document
March 2006
Table of Contents
Introduction to Brocade iSCSI Gateway Manager .................................1-1
Brocade iSCSI Gateway Topology ............................................................................. 1-1
iSCSI Overview ..........................................................................................................1-2
iSCSI Initiator and Targets............................................................................................ 1-2
Portals............................................................................................................... 1-2
Targets and LUNs ............................................................................................. 1-2
Discovery Methods ...................................................................................................... 1-3
iSCSI Discovery ................................................................................................ 1-3
SLP .................................................................................................................... 1-3
iSNS .................................................................................................................. 1-3
iSCSI Security................................................................................................................ 1-4
Access Rights.................................................................................................... 1-7
Target and Initiator Authentication ................................................................ 1-8
Brocade iSCSI Gateway Cluster ................................................................................1-11
Maintaining Cluster Communications .......................................................................1-14
Synchronizing a Cluster ..............................................................................................1-14
Brocade iSCSI Gateway Manager Overview ............................................................ 1-14
Managing the Brocade iSCSI Gateway....................................................................... 1-15
Brocade iSCSI Gateway Manager Icons .....................................................................1-16
Installation Operations ......................................................................... 2-1

Windows Platform .....................................................................................................2-1
Installing Brocade iSCSI Gateway Manager on a Windows Platform........................ 2-1
Running Brocade iSCSI Gateway Manager Server..................................................... 2-6
Brocade iSCSI Gateway Manager Server Located Behind NAT.....................2-7
Running Brocade iSCSI Gateway Manager Client ..................................................... 2-8
Accessing Brocade iSCSI Gateway Manager on the Local Management
Station ............................................................................................................. 2-8
Accessing Brocade iSCSI Gateway Manager through a Web Browser ........ 2-9
Linux Platform ........................................................................................................ 2-10
Installing Brocade iSCSI Gateway Manager on a Linux Platform.............................2-10
Running Brocade iSCSI Gateway Manager Server.....................................................2-11
Running Brocade iSCSI Gateway Manager Client .....................................................2-11
Brocade iSCSI Gateway Operations ..................................................... 3-1

Initial Brocade iSCSI Gateway Manager Configuration .............................................3-1
Assigning a Management IP Address .......................................................................... 3-1
Telnet/SSH Connection .................................................................................. 3-1
RS232 Serial Connection ................................................................................. 3-1
Brocade iSCSI Gateway Manager User Login Profiles .............................................. 3-2
Table of Contents
Publication Number: 53-1000203-01
Brocade iSCSI Gateway & Cluster Configuration ..................................................... 3-3

Adding a New Brocade iSCSI Gateway .......................................................................3-4
Setting Brocade iSCSI Gateway Properties ................................................................ 3-6
Date and Time .................................................................................................3-7
IP Address ....................................................................................................... 3-8
Portals.............................................................................................................. 3-11
IP Routing ....................................................................................................... 3-12
Creating a New Cluster .............................................................................................. 3-14
Creating a Cluster by Adding New Brocade iSCSI Gateway to a Stand-Alone
Gateway...................................................................................................................... 3-15
Synchronizing a Cluster................................................................................. 3-16
Setting Cluster Properties .......................................................................................... 3-16
Keep Alive, Suspicious and Faulty Intervals ................................................. 3-16
Breaking a Cluster ...................................................................................................... 3-18
Additional Brocade iSCSI Gateway Functionality .................................................... 3-19
FC Storage Port Configuration ...................................................................... 3-19
iSNS Configuration ....................................................................................... 3-20
RADIUS Server Configuration .......................................................................3-22
SNMP Configuration......................................................................................3-23
Opening a Telnet Session..............................................................................3-24
Telnet Port Designation.................................................................................3-25
Rediscovering Storage Devices.................................................................... 3-26
Report LUNs Command (Discovering Storage Devices) ............................ 3-26
Rediscover Brocade iSCSI Gateway or Cluster ........................................... 3-26
Reset Brocade iSCSI Gateway ...................................................................... 3-28
Storage Exposure & Security ................................................................. 4-1

Disk Operations........................................................................................................ 4-1
Displaying Available Storage ....................................................................................... 4-1
Storage Exposure & Targets ...................................................................................... 4-2
Exposing Disks and Creating a New Target.................................................................4-3
Creating a New Stand-Alone Target........................................................................... 4-6
Exposing Disks on Existing Targets ............................................................................. 4-8
Modifying & Displaying Target Properties................................................................. 4-8
Unexposing Disks (Deleting LUNs).......................................................................... 4-11
Disk Security ............................................................................................................4-13
Target Authentication ................................................................................................ 4-13
Identities ..................................................................................................................... 4-13
Creating Identities ......................................................................................... 4-13
Adding Initiators to an Identity ..................................................................... 4-14
Assigning Identity Credentials (Initiator Authentication) ............................ 4-16
Attaching Identities to Targets ...................................................................... 4-17
Monitoring & Statistics.......................................................................... 5-1

Health Monitoring .....................................................................................................5-1
ii
iSCSI Gateway Manager Administrators Guide

Scroll and Zoom Functions....................................................................................... 5-2

Interface Statistics and Counters .............................................................................. 5-6
TCP/IP.......................................................................................................................... 5-8
ICMP ............................................................................................................................ 5-8
TCP..............................................................................................................................5-10
UDP.............................................................................................................................. 5-11
iSCSI Statistics..........................................................................................................5-12
Viewing iSCSI Session Information ........................................................................... 5-13
Viewing iSCSI Sessions............................................................................................... 5-14
Viewing iSCSI Session Statistics ................................................................................. 5-15
iSCSI Connection Statistics ..................................................................................... 5-16
Viewing iSCSI Connections ....................................................................................... 5-16
Viewing Connected iSCSI Initiators .......................................................................... 5-16
Viewing iSCSI Initiator Statistics ................................................................................ 5-17
Troubleshooting ................................................................................... 6-1

Alarm Operations ..................................................................................................... 6-1
Configuring Email Alarm Notification ......................................................................... 6-1
Viewing Specific Alarms.............................................................................................. 6-4
Viewing Propagated Alarms ....................................................................................... 6-5
Viewing Alarms History............................................................................................... 6-6
Viewing Current Alarms.............................................................................................. 6-6
Acknowledging an Alarm ........................................................................................... 6-7
Closing an Alarm ......................................................................................................... 6-8
Viewing Alarm Properties ........................................................................................... 6-9
Alarm Severity ............................................................................................................6-10
Index ..................................................................................................... I-1
List of Figures
Figure 1-1.
Figure 1-2.
Figure 1-3.
Figure 1-4.
Figure 1-5.
Figure 1-6.
Figure 1-7.
Figure 1-8.
Figure 1-9.
Figure 1-10.
Figure 2-1.
Figure 2-2.
Figure 2-3.
Figure 2-4.
Figure 2-5.
Figure 2-6.
Figure 2-7.
Figure 2-8.
Brocade iSCSI Gateway Network Topology..................................................................1-1

iSCSI Target Access......................................................................................................... 1-3
Identities Coupled with Targets .................................................................................... 1-5
Default Identities............................................................................................................1-6
Access Rights per Identity-Target Pair........................................................................... 1-7
Identity with iSCSI Initiators and Credentials...............................................................1-9
Sending a CHAP Authentication Challenge ............................................................... 1-10
Brocade iSCSI Gateway Cluster Configuration .......................................................... 1-12
Re-Routing Storage Access with Off-line Brocade iSCSI Gateway ............................1-13
Brocade iSCSI Gateway Management Options ..........................................................1-15
Brocade iSCSI Gateway Manager Server Installation Wizard .................................... 2-2
Stand-Alone Client Installation Wizard ....................................................................... 2-3
Brocade iSCSI Gateway Manager Installation Location ............................................. 2-4
Brocade iSCSI Gateway Manager Installation Location Confirmation...................... 2-5
Complete Installation ................................................................................................... 2-6
Brocade iSCSI Gateway Manager Server Location ..................................................... 2-6
Tools Menu .................................................................................................................... 2-7
System Configuration Dialog Box ................................................................................ 2-7
Table of Contents
iii
Figure 2-9.
Figure 2-10.
Figure 2-11.
Figure 3-1.
Figure 3-2.
Figure 3-3.
Figure 3-4.
Figure 3-5.
Figure 3-6.
Figure 3-7.
Figure 3-8.
Figure 3-9.
Figure 3-10.
Figure 3-11.
Figure 3-12.
Figure 3-13.
Figure 3-14.
Figure 3-15.
Figure 3-16.
Figure 3-17.
Figure 3-18.
Figure 3-19.
Figure 3-20.
Figure 3-21.
Figure 3-22.
Figure 3-23.
Figure 3-24.
Figure 3-25.
Figure 3-26.
Figure 3-27.
Figure 3-28.
Figure 3-29.
Figure 3-30.
Figure 3-31.
Figure 3-31.
Figure 3-32.
Figure 3-33.
Figure 3-34.
Figure 3-35.
Figure 4-1.
Figure 4-2.
Figure 4-3.
Figure 4-4.
Figure 4-5.
Figure 4-6.
Figure 4-7.
Figure 4-8.
Figure 4-9.
Figure 4-10.
Figure 4-11.
Figure 4-12.
Figure 4-13.
Figure 4-14.
iv
Brocade iSCSI Gateway Manager Client Location...................................................... 2-8

Brocade iSCSI Gateway Manager Login Screen.......................................................... 2-9
Brocade iSCSI Gateway Manager URL......................................................................... 2-9
Terminal Properties....................................................................................................... 3-2
Admin Menu.................................................................................................................. 3-3
Users Window ............................................................................................................... 3-3
New Brocade iSCSI Gateway Menu............................................................................. 3-4
New Brocade iSCSI Gateway........................................................................................ 3-4
Brocade iSCSI Gateway Entity (Cluster Level) ............................................................. 3-5
Brocade iSCSI Gateway Physical Entity........................................................................ 3-6
Properties (Brocade iSCSI Gateway Menu) ................................................................. 3-6
Brocade iSCSI Gateway Properties .............................................................................. 3-7
Setting the Brocade iSCSI Gateway Date..................................................................... 3-8
Add Network Port IP Parameters ................................................................................3-10
Delete IP Address.........................................................................................................3-10
Portal Values ................................................................................................................. 3-12
Add IP Route Dialog Box ............................................................................................. 3-13
New Cluster Menu .......................................................................................................3-14
New Cluster Dialog Box............................................................................................... 3-15
Properties Selected ......................................................................................................3-16
Cluster Properties Dialog Box ..................................................................................... 3-17
Cluster Properties Dialog Box Neighbors Tab......................................................... 3-17
Offline Brocade iSCSI Gateway Selected ...................................................................3-18
Navigation Pane with Remaining Brocade iSCSI Gateway........................................3-19
Brocade iSCSI Gateway Fibre Channel Option..........................................................3-19
Setting FC Port Speed..................................................................................................3-20
Brocade iSCSI Gateway Selected ................................................................................ 3-21
RADIUS Server Configuration .................................................................................... 3-22
SNMP Tab..................................................................................................................... 3-23
Opening a Telnet Session ........................................................................................... 3-24
Telnet Session .............................................................................................................. 3-24
Advanced Properties - Setting Telnet Port, Report LUNs Discovery ....................... 3-25
Storage Discovery ....................................................................................................... 3-26
Rediscover Cluster ...................................................................................................... 3-27
Discovery Started Status ............................................................................................. 3-27
Ready Status................................................................................................................. 3-27
Reset Selected From Brocade iSCSI Gateway Menu ................................................ 3-28
Discovery Started ........................................................................................................ 3-28
Ready Status................................................................................................................. 3-29
Storage View Focus ........................................................................................................4-1
Disk Properties .............................................................................................................. 4-2
Expose Disk.................................................................................................................... 4-3
Expose Volume.............................................................................................................. 4-3
New Target..................................................................................................................... 4-4
New Target Listed in Expose Dialog Box ..................................................................... 4-5
New Target Listed in Navigation Pane ......................................................................... 4-5
Create New Target......................................................................................................... 4-6
New Target Alias and Name ......................................................................................... 4-7
New Target in Navigation Pane .................................................................................... 4-7
Expose ............................................................................................................................ 4-8
Target Properties ........................................................................................................... 4-9
Target Properties General Tab................................................................................... 4-9
Target Properties Details Tab................................................................................... 4-10
Figure 4-15.
Figure 4-16.
Figure 4-17.
Figure 4-18.
Figure 4-19.
Figure 4-20.
Figure 4-21.
Figure 4-22.
Figure 4-23.
Figure 4-24.
Figure 4-25.
Figure 4-26.
Figure 4-27.
Figure 5-1.
Figure 5-2.
Figure 5-3.
Figure 5-4.
Figure 5-5.
Figure 5-6.
Figure 5-7.
Figure 5-8.
Figure 5-9.
Figure 5-10.
Figure 5-11.
Figure 5-12.
Figure 5-13.
Figure 5-14.
Figure 5-15.
Figure 5-16.
Figure 5-17.
Figure 5-18.
Figure 5-19.
Figure 5-20.
Figure 5-21.
Figure 6-1.
Figure 6-2.
Figure 6-3.
Figure 6-4.
Figure 6-5.
Figure 6-6.
Figure 6-7.
Figure 6-8.
Figure 6-9.
Figure 6-10.
Figure 6-11.
Figure 6-12.
Figure 6-13.
Figure 6-14.
Figure 6-15.
Figure 6-16.
Figure 6-17.
Target Properties Authentication Tab ...................................................................... 4-11

Disk Selected to Unexpose .........................................................................................4-12
Delete LU Confirmation Box .......................................................................................4-12
Identities Selected........................................................................................................4-14
New Identity Parameters .............................................................................................4-14
Identity Selected...........................................................................................................4-15
Identity Properties Dialog Box ....................................................................................4-15
Add Identity ..................................................................................................................4-16
Authentication Method Parameters ...........................................................................4-17
Added Authentication Method...................................................................................4-17
Attaching Identities to Targets.....................................................................................4-18
Attach Identities to Target Window............................................................................4-19
Access Rights for Identity ............................................................................................4-20
Hardware Selected from Brocade iSCSI Gateway Menu ............................................ 5-1
Brocade iSCSI Gateway Hardware Status Window .................................................... 5-2
Scrolling within Graph .................................................................................................. 5-3
Graph Scrolled............................................................................................................... 5-3
Graph Area Selected ..................................................................................................... 5-4
Area Zoomed In ............................................................................................................ 5-4
Zoom Context Menu .................................................................................................... 5-5
Interface Statistics Selected from Brocade iSCSI Gateway Menu.............................. 5-6
Brocade iSCSI Gateway Interface Statistics ................................................................. 5-7
IP Statistics Window...................................................................................................... 5-8
ICMP Statistics Window................................................................................................ 5-9
TCP Statistics Window .................................................................................................5-10
UDP Statistics Window .................................................................................................5-11
iSCSI Menu....................................................................................................................5-12
iSCSI Information Window.......................................................................................... 5-13
iSCSI Sessions Window................................................................................................5-14
iSCSI Sessions Statistics ................................................................................................ 5-15
iSCSI Connections Window ........................................................................................5-16
Target Connected iSCSI Initiators ............................................................................... 5-17
Statistics Selected from the Connected Initiators Menu ........................................... 5-17
iSCSI Connected Initiators Statistics Window............................................................5-18
Alarms Menu...................................................................................................................6-1
Selected Alarms for Email Notification ........................................................................ 6-2
Configure Menu ............................................................................................................ 6-3
SMTP Server Configuration .......................................................................................... 6-3
Email to Send Alarm Notification to............................................................................. 6-4
Specific Alarms Selected............................................................................................... 6-4
Specific Alarms Window............................................................................................... 6-5
Propagated Alarms Window ........................................................................................ 6-5
Alarms Menu..................................................................................................................6-6
Alarms History Window................................................................................................6-6
Current Alarms Window............................................................................................... 6-7
Acknowledge Alarm......................................................................................................6-8
Ack Checkbox................................................................................................................6-8
Close Alarm....................................................................................................................6-9
Close Alarm Confirmation Dialog Box ........................................................................6-9
Properties..................................................................................................................... 6-10
Alarm Properties Window .......................................................................................... 6-10
Table of Contents
List of Tables
Table 3-1. Brocade iSCSI Gateway Management Parameters............................................................ 3-5
Table 3-2. General Tab ......................................................................................................................... 3-7
Table 3-3. Network Port Parameters...................................................................................................3-10
Table 3-4. Portal Parameters ............................................................................................................... 3-12
Table 3-5: IP Routing Parameters........................................................................................................ 3-13
Table 3-6. SNMP Tab Parameters ...................................................................................................... 3-23
Table 4-1. General Target Properties ................................................................................................. 4-10
Table 4-2. Target Details..................................................................................................................... 4-10
Table 6-1: Brocade iSCSI Gateway Manager Alarms ......................................................................... 6-11
vi

Chapter 1
Introduction to Brocade iSCSI Gateway Manager
This chapter provides an overview of the Brocade iSCSI Gateway, its topology and features.
Brocade iSCSI Gateway Topology

The Brocade iSCSI Gateway provides servers with IP access to storage through SCSI routing
using iSCSI protocol. Using SCSI routing, hosts on an IP network access storage attached to
gateways as local disks.
Figure 1-1 shows a standard Brocade iSCSI Gateway network topology.
z
The gateway in the center connects to the storage elements in the back-end while
connecting to the IP network on the front-end.
The gateway enables hosts to access attached storage using IP-SAN protocol iSCSI. For
more information, refer to iSCSI.
Storage elements can be a combination of FC JBOD (Just a Bunch Of Disks) or FC RAID

subsystems. Storage elements can be connected either directly to the iSCSI gateway or
connected across a Fibre Channel network.
Tower
Hostbox
Tower
Hostbox
Tower
Hostbox
Cloud
IP Network
iSCSI Gateway
10236b
FC
Cloud
Network
FC RAID
Figure 1-1.
RAID
RAID
RAID
Brocade iSCSI Gateway Network Topology

1-1
iSCSI Overview
iSCSI transmits native SCSI commands and data over the TCP/IP protocol stack. iSCSI
transfers and stores SCSI commands and data at any iSCSI enabled storage location with
access to a LAN, MAN, WAN or the Internet. iSCSI enables the creation of high performance
IP-SANs.
iSCSI has many benefits including:
z
Can use existing Ethernet cabling and existing network elements.
Uses common TCP/IP for global connectivity.
Leverages the existing expertise of network administrators, integrators and support

services.
iSCSI Initiator and Targets

iSCSI initiators establish TCP connections with iSCSI targets. Data can be transferred via
iSCSI when an iSCSI initiator establishes a TCP connection with an iSCSI target.
z
The iSCSI initiator resides in the host computer.
The iSCSI target resides in the Brocade iSCSI Gateway.
iSCSI initiators and targets have a World Wide Unique Identifier (WWUI) of up to 223
free form characters, e.g. www.brocade.switch1.target1.
Portals
To enable iSCSI communications over TCP, the system administrator must configure portals
during the initial gateway configuration. A portal is comprised of both an IP address and its
assigned TCP port. Each configured portal automatically becomes an iSCSI access point to
each target that exist in the gateway. Typically, there are few portals and many targets.
Targets and LUNs

An iSCSI initiator can access, read and write to a disk only after the disk is exposed. An
exposed disk is a disk that has been attached to a target and assigned a LUN (Logical Unit
Number). An exposed disk can be accessed by any iSCSI initiator unless ACL restrictions are
configured.
When creating iSCSI targets, the user administrator assigns an alias and name for each one.
The alias is an internal identifier for the system administrator. The name is the WWUI used
to connect initiators to the target.
Note:
When creating targets, keep in mind that:
1-2
Each target can have multiple LUNs.
Each target should be exposed by only one Brocade iSCSI Gateway in a cluster.
Each target can be accessed by multiple hosts.

Brocade iSCSI Gateway Manager Administrator's Guide
There are two ways to expose a disk:

1. Create a new target and assign a LUN in the same process. For more information see
Exposing Disks and Creating a New Target in Chapter 4.

2. Assign LUNs to previously created targets. For more information, see Creating a New
Stand-Alone Target in Chapter 4.

Example:
In Figure 1-2 Disk 1 is exposed via Target 1 and is accessible to any iSCSI initiator via
either portal (IP1, 3260) or (IP2, 3260). Likewise, Disk2 is exposed via Target 2, Disk 3
and Disk 4 are exposed via Target 3.
(IP1, 3260)
(IP2, 3260)
iSCSI Target 1
wwui1
iSCSI Target 2
wwui2
iSCSI Target 3
wwui3
Disk 1
Disk 2
Disk 3
Disk 4
LU0
LU0
LU0
LU1
10124b
iSCSI Gateway
Figure 1-2. iSCSI Target Access
Discovery Methods
The Brocade iSCSI Gateway supports three types of discovery: iSCSI Discovery, SLP and
iSNS.
iSCSI Discovery
In an iSCSI discovery session the user administrator configures an IP and port of the iSCSI
target in the initiator. The initiator discovers all applicable targets and LUNs.
SLP
SLP (Service Location Protocol) is a common broadcast-based discovery mechanism that
uses agents. The gateway acts as an SLP Service Agent (SA) and advertises its iSCSI service.
The initiator identifies the gateway and discovers the gateways targets.
iSNS
iSNS is a client/server protocol designed for compatibility with FCs Simple Name Server
(SNS). Once an iSNS server is located (either through DHCP or SLP), discovery can take
place without the need for broadcasts. iSNS enables iSCSI initiators in the IP-SAN to locate
the gateway targets automatically.

1-3
iSCSI Security
No matter what discovery method is used, ACL (Access Control List) allows only those
targets that are defined as available to be accessed. To allow selective iSCSI initiator access
to iSCSI target disks, the Brocade iSCSI Gateway uses identities to define pools of initiators.
An identity is a user-defined list of iSCSI initiators. Attaching an identity to a target restricts
its access to the list of initiators defined by that identity.
Note:
When planning and creating identities, keep in mind that:

z
Each identity can contain one or more iSCSI initiators.
Each identity can be assigned one or both login authentication methods (CHAP,
SRP).
Each identity can be attached to more than one target.
Each target is first automatically coupled to a default read-write un-authenticated

access identity and therefore can be accessed by everyone.
Each target can have more than one identity. The order of the identities is
important. The first match is used, not the best match.
Note:
If you are working with an iSNS server, all hosts are able to see all targets but only those hosts
with access rights are able to connect to the authorized targets.
1-4

Example:
In Figure 1-3 identities are coupled with iSCSI targets to limit iSCSI initiator access to a
targets underlying disks. An identity can be used with more than one target and each
target can have more than one identity.
Identity A is coupled with both Targets 1 and 2.
Identity B is coupled with Target 3.
Identity C is coupled with Target 4.
As a result, each iSCSI initiator has access to the following disks:

wwui1
Disk 1
iSCSI Target 1
wwui21
wwui2
wwui3
Ident A
Disk 2
wwui4
iSCSI Target 2
wwui22
Disk 3
wwui5
Ident B
wwui6
Disk 4
iSCSI Target 3
wwui23
wwui8
wwui9
Ident C
iSCSI Target 4
wwui24
Disk 5
Disk 6
wwui10
10151b
wwui7
Figure 1-3. Identities Coupled with Targets

When you assign an identity to a target, you give the identity a position. A position is an
identitys rank in the gateway scan for an iSCSI initiator identity match. When the
gateway scans the list of identities coupled with a target, it starts with the highest position
and stops with the first match. After matching, the initiator is granted the identitys access
rights.
An identity can be connected to more than one target to provide the same pre-defined list
of initiators for each target.

1-5
Example:
In Figure 1-4, the default identities for Target 1 and Target 2 have been modified to not
accessible (NA) for all initiators.
Target 1 is coupled with Identity A with read-write (RW) access to Identity As list of
iSCSI initiators (WWUI1).
Target 2 is coupled with Identity B with read-write (RW) access to Identity Bs list of
iSCSI initiators (WWUI2).
When iSCSI initiator WWUI1 logs in to Target 1, the gateway first scans Identity A and
finds the initiator listed there. The scan stops and the initiator is granted read-write
access to Target 1s underlying disk, Disk 1.
If iSCSI initiator WWUI1 tries to login to Target 2, the gateway first scans Identity B. It
does not find the initiator listed so it continues to scan the next identity, the default
identity. The default identity implicitly lists all iSCSI initiators, including WWUI1.
However, the scan stops and the initiator is denied access to Target 2s underlying disks
(Disk 2 and Disk 3), since the default identity is configured as not accessible.
iSCSI
initiator
iSCSI
initiator
Tower
box
wwui2
Tower
box
wwui1
Disk 1
Disk 2
RW
RW
Disk 3
RW
IPCloud
SAN
iSCSI Gateway
Identity A
Target 1
Identity B
Target 2
Def Ident
Def Ident
Ident A
wwui1
Ident B
wwui2
RW
RW
Default
all
Default
all
NA
NA
iSCSI Target 1
wwui3
iSCSI Target 2
wwui4
Disk 2
Disk 3
LU0
LU0
LU1
10156b
Disk 1
Figure 1-4. Default Identities
1-6

Access Rights
When you couple an identity and a target, you assign access rights: read-write (RW), readonly (RO) or not accessible (NA). The access rights are per identity-target pair.
z
An identity can be coupled with multiple targets, each time with different access rights.
A target can have multiple identities, each with different access rights.
Note:
If you add or modify Identities on a target after its disks have been exposed, the access
rights will take effect only at the next login for each iSCSI initiator.
Example:
In Figure 1-5 Identity A is coupled with both Target 1 and Target 2.
The pair Identity A Target 1 is assigned iSCSI initiator read-write access to Target 1
disks.
However, the pair Identity A Target 2, is assigned iSCSI initiator read-only access
to Target 2 disks.
wwui1
Disk 1
wwui2
wwui3
Ident A
wwui4
rite
d-W
Rea
Re
ad
-O
nly
iSCSI Target 1
wwui21
Disk 2
iSCSI Target 2
wwui22
Disk 3
wwui5
Re
ad
-W
rite
wwui7
wwui8
wwui9
Ident C
Rea
d-W
ri
te
Disk 4
iSCSI Target 3
wwui23
iSCSI Target 4
wwui24
wwui10
Disk 5
Disk 6
10152b
Ident B
wwui6
Figure 1-5. Access Rights per Identity-Target Pair

1-7
Target and Initiator Authentication

The Brocade iSCSI Gateway supports the authentication methods CHAP and SRP for the
iSCSI initiator. The credentials for CHAP and SRP are the combination of user name +
password.
CHAP
CHAP is a protocol that is used to authenticate the peer of a connection and is based upon
the peers sharing a secret (a security key that is similar to a password). The target and the
initiator authenticate each other.
The Brocade iSCSI Gateway supports two way CHAP authentication. The target
authenticates the initiator and the initiator can authenticate the target (it is up to the initiator
to request target authentication). A separate secret can be set for each target and for each
initiator in the storage area network (SAN).
Note:
An authentication method is assigned per identity and not per iSCSI initiator.
z
An identity can be assigned an additional authentication method.
If no authentication method is assigned, all listed iSCSI initiators in an identity

will have un-authenticated login access rights.
When an iSCSI initiator logs in to a target, its WWUI is checked against the identity initiator
list. After the iSCSI initiator passes the identity stage, if credentials are configured, the iSCSI
initiator must authenticate itself. The credentials list is checked for the iSCSI initiators user
name + password. The list can contain:
z
A separate user name + password for each initiator.
Note:
There is no strict link between an initiator from the initiator names in the identity and a
specific username + password from the credentials of the identity.
1-8
A few user name + password pairs common to a few initiators
A single user name + password for all initiators in the identity.

Example:
In Figure 1-6 there are:
Six iSCSI initiators in Identity B
Only four user name + password credentials. Certain initiators have the same user
name + password configured on them.
Ident B
Credentials
wwui3
CHAP
SRP
wwui4
Sarah C6H12O6
Dinos RockOn
wwui6
Dinos RockOn
Albert energy
10155
Initiators
wwui7
wwui8
wwui9
Figure 1-6. Identity with iSCSI Initiators and Credentials
Configuring a RADIUS Server

When a RADIUS Server exists in the network, you can use it to manage the Brocade iSCSI
Gateway. When CHAP user names and passwords are configured on the network in a
RADIUS server, the RADIUS server can be configured on the gateway to direct a CHAP
challenge to the RADIUS server and eliminate the need to configure all user name +
password pairs on the gateway. This decreases configuration time and increase overall
network security.

1-9
Example:
In Figure 1-7, a CHAP authentication challenge is sent to the Brocade iSCSI Gateway.
The gateway first checks if the user name is set for RADIUS authentication.
If it is, the CHAP challenge is passed on to the RADIUS server.
If it is not, the user name and password are compared against the pairs configured
in the gateway.
iSCSI
initiator
iSCSI
initiator
Tower box
iqn.1991-05.microsoft:steven.brocade
iqn.com.brocade.steven
Tower box
iqn.1991-05.microsoft:wilbur.brocade
CHAP Authentication
steven
isatwork
IPCloud
SAN
Tower box
RADIUS
Server
Yes
iSCSI Gateway
RADIUS
Authentication?
No
brocade.steven
accounting
steven
ilovecookies
microsoft:steven
Default
all
finance
brocade.billing
10261b
NA
Figure 1-7. Sending a CHAP Authentication Challenge
1-10

Brocade iSCSI Gateway Cluster

A cluster is made from two gateways that are attached to the same storage element(s). In a
cluster, the Brocade iSCSI Gateways interact in a peer-to-peer fashion with the other
neighbor gateway. In this active-active configuration, neither gateway is configured to act as
the master gateway. All disks are accessible to each gateway and can be exposed on either
gateway. This allows you to split the load between the two gateways. Clusters provide high
availability in the event of gateway failover.
Each network port on the Brocade iSCSI Gateway is configured with its own:
z
active, or functioning, IP addresses
inactive, or dormant, neighbor IP addresses.
When one Brocade iSCSI Gateway goes off-line, the remaining gateway activates its
neighbors IP addresses. The hosts continue to access disk targets through the same IP
address without sensing that their regular gateway has gone offline or noticing any impact
on storage performance.
Note:
All LUNs in a RAID controller must be simultaneously exposed through all ports connected to
both gateways.

1-11
Example
In Figure 1-8, two gateways are connected to one FC JBOD. From the four physical disks, two
disks have been exposed and are equally accessible to both gateways.
Brocade iSCSI Gateways are both fully operational in a cluster. No gateway must sit in standby mode.
Both Brocade iSCSI Gateways are also connected to two hosts via the IP SAN. Disk 1 is
exposed via Brocade iSCSI Gateway 1 to Host 1, represented by the orange dashed line. Disk
2 is exposed via Brocade iSCSI Gateway 2 to Host 2, represented by the purple dotted line.
Disk 1
IP1,Target 1
iSCSI
initiator
Disk 2
iSCSI
initiator
Tower
Hostbox
1
Tower
Hostbox
2
IP2,Target 2
IPCloud
SAN
IP1-active
IP2-inactive
IP2-active
IP1-inactive
iSCSI Gateway 1
iSCSI Gateway 2
iSCSI Target 1
wwui1
iSCSI Target 2
wwui2
Disk 1
Disk 2
LU0
LU0
FC JBOD
Disk 2
Disk 3
Disk 4
10228b
Disk 1
Figure 1-8. Brocade iSCSI Gateway Cluster Configuration
1-12

Example
In Figure 1-9, Brocade iSCSI Gateway 1 has gone off-line. Brocade iSCSI Gateway 2 activates
Brocade iSCSI Gateway 1s IP address and takes over exposure of Disk 1 to Host 1,
represented by the orange dashed line.
Host 1 continues to access Disk 1 through the same IP address as it did before its gateway
went off-line. Host 1 has no way of knowing that its regular gateway is off-line.
Disk 1
IP1,Target 1
iSCSI
initiator
Disk 2
iSCSI
initiator
Tower
Hostbox
1
Tower
Hostbox
2
IP2,Target 2
IPCloud
SAN
IP1-active
IP2-inactive
IP2-active
IP1-active
iSCSI Gateway 1
iSCSI Gateway 2
iSCSI Target 1
wwui1
iSCSI Target 2
wwui2
Disk 1
Disk 2
LU0
LU0
FC JBOD
Disk 2
Disk 3
Disk 4
10229b
Disk 1
Figure 1-9. Re-Routing Storage Access with Off-line Brocade iSCSI Gateway

1-13
Maintaining Cluster Communications

Once a Brocade iSCSI Gateway is configured as a cluster, it begins sending out a regular
keep alive signal to its neighbor. The gateway also begins listening for the keep alive signal
from its neighbor. The keep alive signal is transmitted through all connecting paths between
each neighbor. Thus, if one path fails, the remaining path(s) will still carry the keep alive
signal.
If a specified time period passes without a keep alive signal from the neighbor, a suspicious
interval, measured in seconds, is entered. The gateway suspects that its neighbor has gone
off-line and begins preparing to activate the neighbor IP addresses to take over disk
exposure.
If a keep alive signal is received during the suspicious interval, the timer is reset and the
Brocade iSCSI Gateway continues to function as usual. If a keep alive signal is not received
by the end of the suspicious interval, a faulty interval is entered. At the end of the faulty
interval, the neighboring gateway is considered off-line, the failover process is initiated and
the on-line gateway actives the neighbor IP addresses and takes over disk exposure.
Synchronizing a Cluster
If disks or targets are created on one Brocade iSCSI Gateway operating alone, when another
gateway is added, its database must be synchronized to the first gateways database. This
can happen in three situations:
1. A new gateway is added to a configured and functioning gateway to form a cluster.
2. An offline gateway in a cluster comes back online.
3. CLI is used to make an isolated configuration change in one gateway.
Note:
You should rediscover a cluster any time that CLI is used while Brocade iSCSI Gateway
Manager is open.
When an element is not synchronized, a yellow exclamation mark appears to the left of it
instead of a green check mark and the alarm Object not redundant is displayed.
Synchronization is possible at every level of the gateway manager: Cluster, Brocade iSCSI
Gateway, Target and Disk.
Synchronization is carried out from the selected level down. Synchronization at the cluster
level will synchronize the gateways and their disks. You cannot synchronize IP addresses or
IP routes.
Brocade iSCSI Gateway Manager Overview

Brocade iSCSI Gateway Manager is a network management system for the Brocade iSCSI
Gateway.
z
1-14
It centrally manages multiple Brocade iSCSI Gateways.

It automatically synchronizes parameters in both devices when they are part of a cluster.
It provides performance monitoring for advanced diagnostics.
It provides detailed alarm reporting including email notification and alarm propagation.
Managing the Brocade iSCSI Gateway

After powering up the gateway, the first thing you must do is to configure its management
parameters. This can be done via telnet, SSH or via a console or dumb terminal to open a
direct connection with the gateways RS232 console port.
The Brocade iSCSI Gateway can be managed in two different ways. Each way requires a
different configuration.
z
In-band
The management terminal (Telnet, SSH, SP server) connects to the gateways Eth1 port.
The Eth1 port is used by the gateway for management as well as by the hosts for
accessing data accessing storage data (refer to B, Figure 1-10).
RS232
The console connects to the Brocade iSCSI Gateways RS232 port in a direct connection
(refer to A, Figure 1-10). The RS232 port is used mainly for initial configuration: setting up
the management IP, Mask and gateway name. For more information on RS232 Serial
Connection refer to RS232 Serial Connection in Chapter 3.
Telnet Station
In-Band Management
IP
IPCloud
Cloud
Cloud
RS232 port
10223b
Clients
Figure 1-10. Brocade iSCSI Gateway Management Options

1-15
Brocade iSCSI Gateway Manager Icons

The gateway manager uses the following icons.
Icon
1-16
Icon
Icon
cluster
delete
help
Brocade iSCSI
Gateway
1 gateway
close
disk
warning alarm
move down
target
minor alarm
move up
LU
major Alarm
tape
exit
critical alarm
read/write
capabilities
ACL
Alarm
read only
capabilities
external
current alarms
attach
detach
no read/write
capabilities
(no access)

Chapter 2
Installation Operations
Brocade iSCSI Gateway Manager installation runs on Win32 and Linux platforms and works
on a client-server model with the following access options:
z
Client installed locally on the same host server.
Client and server installed remotely with the remote client accessing the local server
with a Web browser as a JAVA applet.
Stand-alone client installed remotely accessing the local server.
Windows Platform
The following section is for Win32 platform only. If you are using Linux, refer to Linux
Platform.
Installing Brocade iSCSI Gateway Manager on a Windows

Platform
Notes:
If you have a previous version of the gateway manager installed, you must remove the
previous version before upgrading your gateway manager system.
To install and run the gateway manager, you must have the JAVA Runtime Environment
(JRE) installed. If you have both a server and client installed, you need to install the JRE
in both places.
Brocade iSCSI Gateway Manager will not run if the correct version of the JRE is not
properly installed on the host machine. The correct version of Java is included on the
installation CDROM. Additionally, the JRE can be downloaded from
http://java.sun.com.
To install Brocade iSCSI Gateway Manager on a Windows platform:
1. Double click on the iSCSI_Gateway_Manager_X.X.X.X_Setup.exe file in the iSCSI
Gateway Manager folder on the CD shipped with the Brocade iSCSI Gateway.
Note:
If you install the gateway manager client as a stand-alone client, you will still need a
gateway manager server installed at some point in your network to be able to
communicate with your Brocade iSCSI Gateway(s) via the client.
To install only the client:
z
Double click on the iSCSI_Gateway_Manager_client_X.X.X.X_Setup.exe file in the
iSCSI Gateway Manager folder on the CD shipped with the Brocade iSCSI Gateway.
The Brocade iSCSI Gateway Manager Installation Wizard opens.

2. Click Next to begin installation.
2-1
Figure 2-1. Brocade iSCSI Gateway Manager Server Installation Wizard
2-2

Figure 2-2. Stand-Alone Client Installation Wizard

3. Install Brocade iSCSI Gateway Manager in the default location or use browse to specify
an alternate location.
Note:
If the Brocade iSCSI Gateway Manager user will be accessing the application through a
Web browser, the gateway manager must be installed under your systems Web server
documents root.
4. Click Next.
2-3
Figure 2-3. Brocade iSCSI Gateway Manager Installation Location

5. Confirm installation location and click Next.
2-4

Figure 2-4. Brocade iSCSI Gateway Manager Installation Location Confirmation

The Brocade iSCSI Gateway Manager Management System files are installed in the
designated location.
6. Click Finish to complete the installation wizard instructions and close the wizard.
2-5
Figure 2-5. Complete Installation
Running Brocade iSCSI Gateway Manager Server

The Brocade iSCSI Gateway Manager Server starts automatically. You can Stop/Restart/Run
the server.
To stop/restart/start the gateway manager server
z
From the Programs menu:

Start > Programs > Brocade > iSCSI Gateway Manager > Server > Start/Stop/Restart.
Figure 2-6. Brocade iSCSI Gateway Manager Server Location
2-6

Brocade iSCSI Gateway Manager Server Located Behind NAT

You need to configure the gateway manager server host machine alias or IP address if the
gateway manager server host machine is located behind a NAT (Network Translation)
environment. If the gateway manager server host machine is not located behind a NAT
environment, the System Configuration Hostname must be left blank.
To configure system parameters:
1. From the Programs menu:
Start > Programs > Brocade > iSCSI Gateway Manager > Server > Tools.
The Tools icon
appears in the system tray (Figure 2-7).
2. In the system tray, right click on the Tool icon and select Network Configuration...
Figure 2-7. Tools Menu

The Network Configuration dialog box opens.
3. Enter the Hostname (use iSCSI Gateway Manager server host machine alias or IP
address).
4. Enter the RMI registry port.
5. Click OK.
Figure 2-8. System Configuration Dialog Box
2-7
Running Brocade iSCSI Gateway Manager Client

After installing gateway manager you can open the gateway manager client at any time
either by running the client on the local management station, on another station or through
a Web browser.
Note:
When accessing Brocade iSCSI Gateway Manager through a Web browser, it must be
installed under your systems Web server documents root. The gateway manager URL is
in the form:
http://ip of host terminal or host name/Brocade iSCSI Gateway
Manager/index.html
Accessing Brocade iSCSI Gateway Manager on the Local Management

Station
To start the client:
1. From the Programs menu:
Start > Programs > Brocade > iSCSI Gateway Manager > Server > Local Client
(Figure 2-9)
Note:
If the client has been installed separately, the path is:

Start > Programs > Brocade > iSCSI Gateway Manager > Client > Client
Figure 2-9. Brocade iSCSI Gateway Manager Client Location

The Brocade iSCSI Gateway Manager Management System screen opens.
2. Enter the default User Name and Password: admin.
Note:
If the gateway manager client is located on a different host server from the gateway
manager server, you must enter the gateway manager server host name and server port
to enable communication between the client and server.
3. If necessary, enter Server Host and Server Port.
4. Click OK.
2-8

Figure 2-10. Brocade iSCSI Gateway Manager Login Screen
Accessing Brocade iSCSI Gateway Manager through a Web Browser

To access gateway manager via a Web browser:
1. Navigate to the gateway manager URL using your Web browser. The URL is in the form:
http:// IP address of host terminal or host name/ iSCSI Gateway Manager /index.html
Figure 2-11. Brocade iSCSI Gateway Manager URL

The gateway manager screen opens (Figure 2-10).
2. Enter the default User Name and Password: admin.
3. Click OK.
2-9
Linux Platform
The following section is for Linux platform only. If you are using Win32, refer to Windows
Platform.
Installing Brocade iSCSI Gateway Manager on a Linux

Platform
Notes:
If you have a previous version of the gateway manager installed, you must remove the
previous version before upgrading your gateway manager system.
To install and run gateway manager, you must have the JAVA Runtime Environment
(JRE) installed on the management station. The JRE is can be downloaded from the
Internet: http://java.sun.com. Brocade iSCSI Gateway Manager will not run if the
correct version of the JRE is not properly installed on the host machine.
When accessing gateway manager through a Web browser, gateway manager must be
installed under your systems Web server documents root. The gateway manager URL is
in the form:
http://ip of host terminal or host name/ iSCSI Gateway Manager /index.html
To install gateway manager on a Linux platform:
1. Copy the zip file iSCSI_Gateway_Manager_X.X.X.X.zip to the destination directory,
referred to as <dest_directory>.
2. Go to the <dest_directory> and unpack the zip file using the command:
unzip iSCSI_Gateway_Manager_X.X.X.X.zip
3. Set Java environment variable SP_JAVA_HOME to be the location of your JAVA runtime
environment (JRE) or SDK package.
4. In RedHat, add the following two lines to /etc/profile:
NMS_JAVA_HOME=/root/Java/jre-1_5_06# my Java home dir. . .
export NMS_JAVA_HOME
5. Log Out.
6. Log In.
2-10

Running Brocade iSCSI Gateway Manager Server

To run gateway manager server on a Linux platform:
1. Go to <dest_directory>/ Brocade iSCSI Gateway Manager /server.
2. Add execute permissions to the script runServer.sh using the commands:
chmod 777 runServer.sh
3. Run the script runserver.sh.
Running Brocade iSCSI Gateway Manager Client

To run gateway manager client on a Linux platform:
1. Go to <dest_directory>/ Brocade iSCSI Gateway Manager.
2. Add execute permissions to the script runClient.sh using the command:
chmod 777 runClient.sh
3. Run the script runclient.sh.
2-11
2-12

Chapter 3
Brocade iSCSI Gateway Operations
Brocade iSCSI Gateway Manager communicates with the gateway via the gateway
management port IP address. The gateway communicates with hosts via iSCSI portals which
are configured via the gateway manager. Brocade iSCSI Gateway Manager automatically
discovers all disks and LUNs connected to the gateway storage ports. The gateway manager
enables multi-cluster management.
Initial Brocade iSCSI Gateway Manager Configuration

The Brocade iSCSI Gateway has a default IP Address of 10.11.12.123. This allows you to set
initial startup parameters via a telnet session.
Assigning a Management IP Address

The management IP address can be set via:
z
RS-232 port
Telnet session
Telnet/SSH Connection
To initialize the gateway via telnet/SSH session:
1. Change your computers IP Address to anything on the same subnet 10.11.12.*
2. Connect to the management port on the gateway.
3. Telnet to 10.11.12.123.
4. Enter Username and Password: admin.
You will be asked to accept or change the default values for:
1. IP Address.
2. IP Mask.
3. Management port (eth1).
4. Default gateway name. This name will appear in the Brocade iSCSI Gateway Manager
Navigation Pane. If you dont enter a name, gateway manager will use the IP address.
This name can be changed later via the Brocade iSCSI Gateway Properties tab if there is
only one gateway present.
RS232 Serial Connection

To initialize the gateway via an RS-232 serial connection:
1. Connect the cable to the appropriate port on the management server, and open a
Terminal session. Set the following parameters in the terminal:
Bits per second = 115200, Flow Control = None, Emulation = Autodetect.

3-1
Figure 3-1. Terminal Properties

2. Enter Username and Password: admin.
3. Set the IP Address.
4. Set the IP Mask.
5. Set the management port (eth1).
6. Set the gateway name. This name will appear in the gateway manager Navigation Pane. If
you dont enter a name, gateway manager will use the IP address. This name can be
changed later via the Brocade iSCSI Gateway Properties tab if there is only one gateway
present.
Brocade iSCSI Gateway Manager User Login Profiles

The default user name and password for gateway manager is admin.
Notes:
z
Once you add a user profile, the default username and password is erased.
The password must be 5-12 characters.
The username must be 1-20 characters.
To set a user profile:

1. From the gateway manager toolbar, select Admin > Users
3-2

Figure 3-2. Admin Menu

The Users window opens.
2. Click Add.
The Add User dialog box opens.
3. Enter the user name and password in the appropriate fields.
4. Click OK.
The Add User dialog box closes. The new user name now appears in the Users window.
You can sort the user names by clicking the sort arrow.
Figure 3-3. Users Window
Brocade iSCSI Gateway & Cluster Configuration

A cluster is a group of FC storage units and switches that function as one unit, providing high
availability in the event of gateway failover.
Brocade iSCSI Gateway Manager enables you to make a cluster from two gateways and
configure both at the same time. Additionally, a cluster can be made by adding a new
gateway to an already configured stand-alone gateway and then synchronizing the cluster.

3-3
Note:
This section details the steps necessary for configuring a single, stand-alone gateway.
When additional steps must be taken for cluster configuration, they are noted.
Adding a New Brocade iSCSI Gateway

All stand-alone gateways must be added to the gateway manager.
To add a new gateway:
1. In the Navigation pane, right click on Brocade iSCSI Gateway Manager and select New >
Brocade iSCSI Gateway.
Figure 3-4. New Brocade iSCSI Gateway Menu

The New Brocade iSCSI Gateway dialog box opens.
2. Enter the Brocade iSCSI Gateway configuration parameters in the dialog box.
Note:
The IP address is mandatory. The remaining fields contain default values.
Figure 3-5. New Brocade iSCSI Gateway

3-4

Table 3-1. Brocade iSCSI Gateway Management Parameters

Parameter
IP Address
Mask
SNMP UDP Port
TRAP UDP Port
Read Community
Write Community
Timeout
Number of Retries
SNMP Version
Definition
IP address of the management interface configured on gateway during
initial setup.
IP mask for the management interface
UDP port on which SNMP manager-agent communications run
UDP port on which the SNMP agent will issue traps
Defined group granted read access to data
Defined group granted write access to data
Time in milliseconds before an SNMP session is considered closed.
Number of times to try to re-establish an active SNMP session
SNMP protocol version being used to establish gateway manager
communications with the specified gateway
3. The new gateway appears in the Navigation pane and is represented by two entities:
a virtual entity and a physical entity. The menu options differ for the two different
types of entities. The virtual entity is referred to as cluster level.
Figure 3-6. Brocade iSCSI Gateway Entity (Cluster Level)

3-5
Figure 3-7. Brocade iSCSI Gateway Physical Entity
Setting Brocade iSCSI Gateway Properties

You can change gateway properties via the different tabs in the Properties window (Figure 39).
To display gateway properties:
1. In the Navigation pane, right click on the Brocade iSCSI Gateway and select Properties.
Figure 3-8. Properties (Brocade iSCSI Gateway Menu)

The gateway Properties dialog box opens displaying different tabs.
2. Toggle between these tabs to configure the different gateway properties.
3-6

Figure 3-9. Brocade iSCSI Gateway Properties
Date and Time

You can set the local date and time on a gateway.
Note:
Alarms are time-stamped according to the computer clock that is running the Brocade
iSCSI Gateway Manager server.
To set Brocade iSCSI Gateway date and time:
1. In the Navigation pane, right click on the Brocade iSCSI Gateway on which you want to
add a network port IP address and select Properties
The gateway Properties dialog box opens (Figure 3-9).
Table 3-2. General Tab
Parameter
Name
Contact
Location
Mgmt IP Address
Mgmt Mask
Last Reset
Date
Definition
Name of the gateway
Contact person for technical support
Location of the contact person
IP address of the gateway management interface
IP mask for the management interface
Date and time since the last gateway reset
Local date

3-7
Parameter
Time
Status
Description
Definition
Local time
Connection status of the gateway
Description of gateway hardware and software
Figure 3-10. Setting the Brocade iSCSI Gateway Date

2. Select the year, month and day for the gateway.
3. Select the hour, minutes and seconds.
4. Select AM or PM. Select AM for morning, PM for evening (12:00 AM=midnight, 12:00
PM=noon).
5. Click OK.
IP Address
To enable a host to communicate with the Brocade iSCSI Gateway using iSCSI protocol, an
IP address must be assigned to the device. After adding an IP address, configure an iSCSI
portal on the IP address (see Portals).
3-8
Each interface can have multiple IP addresses assigned to it.
Each gateway has two 1Gb Ethernet interfaces.

Note:
If you are adding a network port IP address in a cluster, assign the IP address as active on
one gateway and inactive on the second gateway. In the event of a gateway failover, the
second gateway will activate its inactive IP addresses and begin exposing the IP address'
target LUNs.
To add network IP addresses:
1. In the Navigation pane, right click on the Brocade iSCSI Gateway on which you want to
add a network port IP address and select Properties
2. Toggle to the IP tab.
3. Click Add.
4. The Add IP dialog box opens (Figure 3-11).
5. Enter the network port IP values and click OK.
The new network port IP address is listed in the IP tab.
6. Click OK.
Cluster Note:
If you are working in a cluster, another Add IP dialog box will open, this time for the
second Brocade iSCSI Gateway.
z
Only the interface will be configurable. Click OK to configure the IP address on

the second gateway. Click Cancel to configure the IP on only the first gateway.
In the event of failover, the inactivate IP addresses are activated on the

functioning gateway to take over target LUN exposure. The IP addresss activity
will be shown as switched.

3-9
Figure 3-11. Add Network Port IP Parameters

Table 3-3. Network Port Parameters
Parameter
IP Address
IP Mask
Activity
Interface
Description
IP address of interface
IP mask of interface
activity status of IP address
Interface alias
To delete network IP addresses:

1. In the Navigation pane, right click on the gateway on which you want to delete a
network port IP address and select Properties
2. Toggle to the IP tab.
3. Click the IP address you want to delete.
4. Click Delete.
5. A dialog box opens asking you to confirm the delete (Figure 3-11).
Figure 3-12. Delete IP Address

6. Click Yes.
The IP Address is deleted.
3-10

Portals
A portal is the combination of an interface IP address and a TCP port. You must assign iSCSI
portals to enable iSCSI communication between an iSCSI initiator and iSCSI target.
Note:
z
In a cluster, you must assign TCP ports for each of the Brocade iSCSI Gateway
IP addresses.
If an inactive IP address does not have an assigned TCP port, the IP address
will not function during gateway failover.
To add an iSCSI portal:

1. In the Navigation pane, right click on the Brocade iSCSI Gateway and select Properties
2. Toggle to the Portals tab.
3. Click Add.
The Add Portal dialog box opens.
4. Select the IP address from the drop-down menu of existing IP address and enter the port
number. Click OK.
The IP Address is added to the gateway Properties tab.
5. If you are working in a cluster, a second Add Portal dialog box opens for the second
gateway. The IP address and port numbers are already listed and cannot be changed.
Cluster Note:
When you add an iSCSI portal to a Brocade iSCSI Gateway in a cluster, you need to add
the portal to the second gateway as well. In the event of a gateway failover, this allows
the second gateway to begin exposing the failed gateways target LUNs through the
portal.

3-11
Figure 3-13. Portal Values

Table 3-4. Portal Parameters
Parameter
IP Address
Port
Description
User-assigned IP address of an interface
TCP port through which the iSCSI protocol passes (usually 3260)
To delete an iSCSI portal:

2. Toggle to the Portals tab.
3. Select desired portal and click Delete.
A dialog box appears asking if you want to delete selected portals. Click Yes to confirm
delete.
IP Routing
To enable communications between the gateway and IP networks located outside the
gateway LAN, you must configure IP routing paths for each external network port.
z
Each Brocade iSCSI Gateway can have only one IP route designated to a specific
external network, even if there is more than one possible physical path to that network.
Cluster Note:
In a cluster, an IP route must be added to both iSCSI Gateways. In the event of a gateway
failover, the second gateway will be able to establish communications through the route
and expose the failed gateways target LUNs.
3-12

To add an IP route:
2. Toggle to the IP Route tab.
3. Click Add.
The Add IP Route dialog box opens.
Figure 3-14. Add IP Route Dialog Box

4. Enter the routing values (see Table 3-5).
5. You can configure a default gateway for each port, including the management port, for
routing all traffic not otherwise specified in the gateway routing table by using 0.0.0.0
for the IP address.
6. Click OK. The Add IP Route dialog box closes. The new IP route is listed in the IP
Route tab.
Table 3-5: IP Routing Parameters
Parameter
Destination IP
Address
Destination IP Mask
Gateway
Interface
Description
IP address of destination network
Use the IP address 0.0.0.0 to create a default gateway
IP mask of destination network
IP address of gateway router
Network interface to open route through

3-13
Cluster Note:
If you are working in a cluster, a second Add IP Route dialog box opens for the second
gateway. The destination IP address and mask as well as the gateway are already listed
cannot be changed. Only the network interface port is editable.
In the event of a gateway failover, the second gateway will be able to establish
communications through the route and expose the failed gateways target LUNs.
z
Click OK to add the route to the second gateway or Cancel to exclude the
route from the second gateway in the cluster.
Creating a New Cluster

Brocade iSCSI Gateway Manager enables you to easily configure network port IP addresses,
iSCSI portals and IP routes simultaneously on both gateways in the cluster.
To add a new cluster from two new gateways:
1. In the Navigation pane, right click on Brocade iSCSI Gateway Manager and select New >
Cluster
Figure 3-15. New Cluster Menu

The New Cluster dialog box opens.
3-14

Figure 3-16.New Cluster Dialog Box

2. Enter the new cluster alias. Click OK.
3. Add gateways to the cluster (refer to Adding a New ).
Creating a Cluster by Adding New Brocade iSCSI Gateway to a

Stand-Alone Gateway
To make a cluster by adding a new gateway to a stand-alone gateway:
1. In the Navigation pane, right click on the stand-alone Brocade iSCSI Gateway (at cluster
level), and select New > Brocade iSCSI Gateway
Cluster Note:
z Both gateways in a cluster must have different aliases. If you add a second
gateway with the same alias as the first gateway, no cluster will be created and
no failover will be possible.
z
The gateway will be listed in the gateway manager navigation pane with an
orange exclamation mark (major alarm) and the Last 10 Alarms pane will display
the alarm gateways are not neighbors. For the gateway manager to create a
cluster, you need to rename the second gateway via the gateway properties.
2. Synchronize the new gateway by following the steps outlined in Synchronizing a Cluster.
3. Define the gateway parameters for the second gateway (V2) as follows:
z
IP of V1 as passive
Portals of V1
Routing of V1
4. Manually configure the CHAP and Password from the Identities level (refer to Assigning
Identity Credentials).

3-15
Synchronizing a Cluster
If targets are created on one Brocade iSCSI Gateway operating alone, when another
gateway is added, its database must be manually synchronized to the first gateways
database. This can happen in three situations:
1. A new gateway is added to a configured and functioning gateway to form a cluster.
2. An offline gateway in a cluster comes back online.
3. The CLI is used to make an isolated configuration change in one gateway.
When an element is not synchronized, a yellow exclamation mark appears to the left of it
instead of a green check mark and the alarm Object not redundant is displayed.
To synchronize an element:
1. Select the element to synchronize: cluster or target.
2. Right click and select Cluster Sync from the open menu.
Synchronization is instantaneous. During synchronization, the yellow exclamation
marks at the selected element's level (and below ) are converted to green check marks
. The green check marks indicate that synchronization has completed.
Setting Cluster Properties

The Cluster Properties dialog box (Figure 3-18) allows you to configure general cluster
parameters as well as view the gateways neighbor details.
Keep Alive, Suspicious and Faulty Intervals

The Brocade iSCSI Gateway sends out keep-alive signals to the other gateway (its neighbor)
in a cluster. Suspicious and faulty intervals define the time interval for the gateway to not get
keep-alive signals from its neighbor and subsequently change its neighbors state to
suspicious and faulty. The faulty state triggers a takeover procedure.
To configure keep alive, suspicious and faulty intervals:
1. In the Navigation pane, right click the cluster and select Properties...
Figure 3-17. Properties Selected
3-16

The Cluster Properties dialog box opens (Figure 3-18).

2. On the General Tab, enter the desired intervals for Keep-alive Intervals, Suspicious
Intervals, and Faulty Intervals.
3. Click OK.
Figure 3-18.Cluster Properties Dialog Box

To view neighbor properties for a cluster:
1. In the Navigation pane, right click and select Properties
The Cluster Properties dialog box opens (Figure 3-18).
2. Toggle to the Neighbors tab (Figure 3-19).
Figure 3-19.Cluster Properties Dialog Box Neighbors Tab

3-17
Breaking a Cluster
You can break a cluster by removing one of its neighbors (Brocade iSCSI Gateway). A
gateway can be deleted from a cluster only after it is offline and Brocade iSCSI Gateway
Manager recognizes it as offline.
Cluster Note:
z If you remove a gateway from a cluster, all of its configurations will be
automatically transferred to its neighbor. However, the activity of the IP
addresses will be active and not switched.
z
If the removed gateway is re-added, the IP addresses will not failback to the
re-added gateway. The IP addresses and their exposed targets will be
exposed on both gateways.
If you want to re-add the gateway to the gateway manager, first return the
gateway to the default factory settings. See the Brocade iSCSI Gateway
Installation and Operation Guide for procedures on resetting an gateway to
factory default settings.
To break a cluster:
1. From the Navigation pane, right click on the Brocade iSCSI Gateway and select
Properties
2. Disconnect (turn off) the gateway from the system.
The offline gateway is marked with a red exclamation mark .
3. The remaining gateway is marked with a blue exclamation mark to show that it has
taken over exposing the offline gateways targets.
4. Right click on the offline Brocade iSCSI Gateway and select Delete.
Figure 3-20. Offline Brocade iSCSI Gateway Selected

5. A Dialog box opens asking if you want to delete the offline gateway. Click Yes.
3-18

6. Brocade iSCSI Gateway Manager begins removing the offline gateway from the gateway
manager database. The status bar displays Ready when the gateway has been removed
from the cluster.
7. The Navigation pane displays the remaining gateway in the cluster.
Figure 3-21. Navigation Pane with Remaining Brocade iSCSI Gateway
Additional Brocade iSCSI Gateway Functionality

This section describes routine and optional gateway configuration operations.
FC Storage Port Configuration

The gateway default configuration for FC connections is Auto NL_Port in a public loop. Each
storage port connected to an FC device can be reconfigured to change the connection
speed and topology.
To change FC/SCSI storage port parameters:
1. In the Navigation pane, select the Brocade iSCSI Gateway, right click and select Fibre
Channel...
Figure 3-22. Brocade iSCSI Gateway Fibre Channel Option

The Fibre Channel Parameters dialog box opens.
2. Toggle to the Interfaces tab.
3. Select new settings for parameters by selecting them from the drop down menu boxes.
4. Click OK.

3-19
Figure 3-23. Setting FC Port Speed
iSNS Configuration
The Brocade iSCSI Gateway supports Internet Storage Name Service (iSNS) protocol for
advertising its targets and portals on the iSNS server. This enables iSCSI initiators in the IPSAN to locate the gateway targets automatically. Targets defined by the gateways Access
Control List (ACL) as having controlled access are accessible only to those servers defined as
having access to the target.
To add an iSNS server:
1. In the Navigation pane, right click on desired Brocade iSCSI Gateway and select iSNS
The iSNS Servers dialog box opens.
3-20

Figure 3-24. Brocade iSCSI Gateway Selected

2. Click Add to open the New iSNS Server dialog box.
3. Enter the iSNS server IP address and click OK.
The IP address is added to the iSNS Server dialog box.
4. Click OK.

3-21
RADIUS Server Configuration

A RADIUS server can be configured on the gateway to direct a CHAP challenge to the
RADIUS server and eliminate the need to configure all user name + password pairs on the
gateway. This decreases configuration time and increase overall network security.
To configure a Radius server:
1. From the Navigation pane, select the cluster or stand-alone Brocade iSCSI Gateway.
Right click and select RADIUS.
The RADIUS Servers dialog box opens.
2. Click Add.
The Add RADIUS Server dialog box opens.
3. Enter the new RADIUS server parameters.
4. Click OK.
Figure 3-25. RADIUS Server Configuration
3-22

SNMP Configuration
SNMP and trap port configurations are editable from this tab.
Figure 3-26. SNMP Tab

Table 3-6. SNMP Tab Parameters
Parameter
SNMP UDP Port
TRAP UDP Port
Read Community
Write Community
Timeout
Number of Retries
SNMP Version
Definition
UDP port on which SNMP manager-agent communications run
UDP port on which the SNMP agent will issue traps
defined group granted read access to data
defined group granted write access to data
time in milliseconds before an SNMP session is considered closed
number of times to re-establish an active SNMP session
SNMP protocol version being used to establish gateway manager
communications with the specified gateway

3-23
Opening a Telnet Session

To open a Telnet session from the gateway manager:
z
From the Navigation pane, select Brocade iSCSI Gateway. Right click and select Telnet.
Figure 3-27. Opening a Telnet Session

A Telnet session is opened.
Figure 3-28. Telnet Session
3-24

Telnet Port Designation

If your network topology includes a management station communicating with the gateway
via CLI, you can enable Telnet communications to be transported through a port other than
the standard Telnet port 23. If your Telnet communications connection to the gateway
traverses a firewall, the standard Telnet port 23 may be blocked by the firewall as a security
measure. The designated port can be opened in the firewall for dedicated gateway management terminal communications.
To designate a telnet port:
1. In the Navigation pane, select the Brocade iSCSI Gateway.
2. Right click on the gateway and select Properties. The gateway Properties dialog box
opens (Figure 3-9).
3. Toggle to the Advanced tab (Figure 3-29).
4. Enter the new Telnet port and click OK.
Figure 3-29. Advanced Properties - Setting Telnet Port, Report LUNs Discovery
5. A message box opens stating that you must reset the gateway for the new Telnet port
properties to take effect. Click OK.
6. Reset the gateway (see Reset ).
7. Check that the new Telnet port was applied by checking the Advanced tab in the
gateway Properties dialog box (Figure 3-29).

3-25
Rediscovering Storage Devices

Manual discovery rediscovers the physical disks attached to the gateway.
To rediscover physical disks attached to the gateway:
z
Right click on cluster and select Storage Discovery (Figure 3-30).
Figure 3-30. Storage Discovery
Report LUNs Command (Discovering Storage Devices)

The Brocade iSCSI Gateway default algorithm for storage devices discovery uses the SCSI
command REPORT LUNS. Certain storage devices either do not support this command or
do not respond according to the SCSI standard.
Note:
When working with devices that do not support the SCSI command REPORT LUNS, To
discover these devices, the REPORT LUNs command must be disabled.
If certain devices in the SAN are not being discovered by the gateway, disable or re-enable
device discovery using REPORT LUNs.
To disable/enable report LUNs command:
2. Toggle to the Advanced tab (Figure 3-29).
3. Disable (uncheck) or re-enable (check) Report LUNs Discovery.
Rediscover Brocade iSCSI Gateway or Cluster

Rediscover causes Brocade iSCSI Gateway Manager to refresh the information and update
its database.
To rediscover a gateway or cluster:
1. Right click on cluster and select Rediscover (Figure 3-31).
3-26

Figure 3-31. Rediscover Cluster

2. The Status bar at the bottom of the window displays Discovery Started...
Figure 3-32. Discovery Started Status

3. When all attached storage devices and system configurations have been discovered, the
Status bar displays Ready.
Figure 3-33. Ready Status

3-27
Reset Brocade iSCSI Gateway

You can reset the gateway from the gateway manager. All configuration databases will be
maintained on the gateway, including network port aliases and all configured disks and
targets.
Note:
In the case of a cluster, Reset will cause the second gateway to take over.
To reset an gateway:
1. In the Navigation pane, select the Brocade iSCSI Gateway.
2. Right click on the gateway and select Reset.
Figure 3-34. Reset Selected From Brocade iSCSI Gateway Menu

3. A dialog box appears asking if you want to Reset the gateway. Click Yes.
4. The gateway manager status bar will display Resetting and then Discovery Started while
the gateway is being reset. During reset, all gateways are discovered.
Figure 3-35. Discovery Started

5. Brocade iSCSI Gateway Manager then rediscovers the gateway. After the discovery
process has completed, you can resume work. The status bar will display Ready.
3-28

Figure 3-36. Ready Status

Note:
If the reset gateway is part of a cluster, you may have to synchronize the cluster. See
Synchronizing a Cluster.

3-29
3-30

Chapter 4
Storage Exposure & Security
This chapter describes the disk operations enabled by Brocade iSCSI Gateway Manager
based on the physical storage attached to the gateway unit.
Disk Operations
Disk operations are performed from the Storage View window (Figure 4-1).
To display the storage view:
z
Click on Storage in the left hand side of the gateway manager main window.
The Available Storage Devices panel appears in the main window.
Figure 4-1. Storage View Focus
Displaying Available Storage

To display or modify available storage properties:
1. Select the desired disk by clicking on its name from the Available Storage Devices panel
(Figure 4-2).
2. Right click and select Properties.
The Disk Properties dialog box opens.
4-1
3. The fields Disk Alias, Information, and Write Cache Enabled are editable. Enter new
parameters, if desired and click OK.
Figure 4-2. Disk Properties
Storage Exposure & Targets

Disks must be exposed in order for it to be used by a FS Application. Every disk that is
exposed must have a target. When exposing disks, you can create a new target or use an
existing one. Basically there are two things you can do:
4-2
Expose a disk by creating a new target for it.
Expose a disk by using an existing target.

Exposing Disks and Creating a New Target

To expose a disk and create a new target:
1. Select the disk to expose.
2. Right click and select Expose
Figure 4-3. Expose Disk

The Expose Volume dialog box opens.
Figure 4-4. Expose Volume

3. From the Expose Volume dialog box, click New Target.
The New Target dialog box opens.
4-3
Figure 4-5. New Target

4. Enter the Target Alias and Target Name (target WWUI).
5. Select value for Brocade iSCSI Gateway exposed on (the gateway on which to expose the
target).
6. Select the Default Access rights for the target. Choose from Read/Write (RW), Read Only
(RO) or Not Available (N/A). The default is RW.
Note:
A target alias is an internal identifier and can be modified later.

z
A target name is the WWUI of the target and for external use when connecting
to an initiator and cannot be modified.
A target name must be in lower case letters.
A target alias and name can be the same but must be unique in the system.
7. Click OK.
The New Target dialog box closes and the new target appears in the Expose dialog
box (Figure 4-6). Because this is a new target, the selected disk is automatically
assigned LU0.
Note:
4-4
You can change the LUN if the storage is a disk.
You cannot change the LUN when the storage is a tape.

Figure 4-6. New Target Listed in Expose Dialog Box

The attached disk is now exposed on the target to all initiators as a read-write disk. To
restrict access, refer to Disk Security.
Figure 4-7. New Target Listed in Navigation Pane

4-5
Creating a New Stand-Alone Target

Note:
Targets can be created without a disk associated with it. These targets will have no initial
associated LUNs and will not be exposed to hosts when first created.
To create a new stand-alone target:
1. From the Navigation pane, right click the desired Cluster.
Figure 4-8. Create New Target

2. Enter the Target Alias and Target Name (target WWUI).
3. Select value for Brocade iSCSI Gateway Exposed on (the gateway on which to expose the
target).
4. Select the Default Access rights for the target. Choose from Read/Write (RW), Read Only
(RO) or Not Available (N/A). The default is RW.
Note:
4-6
A target alias is an internal identifier and can be modified later.
A target name is the WWUI of the target and for external use when connecting
to an initiator and cannot be modified.
A target name must be in lower case letters.
A target alias and name can be the same but must be unique in the system.

Figure 4-9. New Target Alias and Name

5. Click OK.
The new target is listed under Logical Units in the Navigation pane. The target is
displayed by its alias. Move the mouse over the alias to display the target name and
exposing gateway.
Figure 4-10. New Target in Navigation Pane

4-7
Exposing Disks on Existing Targets

To expose a disk on existing targets:
1. Select the disk to expose (Figure 4-3).
2. Right click and select Expose
The Expose dialog box opens.
Figure 4-11. Expose

3. Select and existing Target from the list.
4. Assign a LUN for the target.
5. Click OK.
Note:
A LUN value cannot be larger than 255.
Modifying & Displaying Target Properties

You can modify/display some target properties.
To modify or display target properties
1. In the Navigation pane, select the target.
2. Right click on the target and select Properties.
4-8

Figure 4-12. Target Properties

The Target Properties dialog box opens (Figure 4-13).
You may edit the following target properties.
z
Target Alias, Brocade iSCSI Gateway Exposed, Default Access (General tab)
User Name, Password (Authentication tab)
Figure 4-13. Target Properties General Tab

4-9
Table 4-1. General Target Properties

Parameter
Description
Target Alias
Target Name
Status
Number of LUs
Exposed On
Default Access
User-given alias for target

WWUI of target
Status of target
Number of LUs associated with the target
Brocade iSCSI Gateway on which the target and its attached LUs are
exposed
Default Access to the target
RW read-write
RO read only
NA no access
Number of SCSI ports on gateway
target port name
Number of SCSI ports

Port Name
Figure 4-14. Target Properties Details Tab
Table 4-2. Target Details

Parameter
Number of Login Failures
Last Failure Time
Last Failure Type
Last Failed Initiator Name
Last Failed Initiator IP
4-10
Description
Number of Login attempts that failed
Time of last failed login attempt
Type of login failure
options: other; redirect; authorize; authenticate; negotiate
Name of last initiator that failed to login
IP address of last initiator that failed to login

To configure CHAP two-way authentication parameters (for iSCSI initiators):

1. In the Navigation pane, right click on the target and select Properties (Figure 4-12).
The Target Properties dialog box appears.
2. Select the authentication tab (Figure 4-15).
3. Enter the desired User Name and Password.
4. Click OK.
Figure 4-15. Target Properties Authentication Tab

Note:
If no password is provided, no target authentication properties are applied. Passwords must be

12-16 character in length.
Unexposing Disks (Deleting LUNs)

When you unexpose a disk, its LUN is deleted.
To unexpose a disk:
1. Select the disk
2. From either the Logical Units or Logical Units Details pane, select the disk, right click and
select Unexpose.

4-11
Figure 4-16. Disk Selected to Unexpose

The Unexpose confirmation box opens.
Figure 4-17. Delete LU Confirmation Box

3. Click Yes.
The unexposed disk now appears in the list of available storage.
Note:
Removing LU0 from a target, when LU0 is the only LU, will inactivate the target.
4-12

Disk Security
Target Authentication
The Brocade iSCSI Gateway supports the authentication methods CHAP and SRP for the
iSCSI initiator.
Identities
An identity is a user-defined list of iSCSI initiators. The gateway uses identities to define
pools of initiators. This enables selective iSCSI initiator access to iSCSI targets. An identity
can contain from one to multiple initiators, with each initiator having a unique WWUI. If a
host has more than one iSCSI initiator installed, both initiators can be included in the
identity.
Note:
z
If you are working with an iSNS server, all hosts are able to see the target but
only those hosts with access rights are able to connect to the target.
If you add or modify Identities on a target after its disks have been exposed,
the access rights will take effect only at the next login for each iSCSI initiator.
Creating Identities
If you want to limit host (iSCSI initiator) access to targets, you must create an identity that is
more discriminate than the default identity. For a more detailed explanation refer to iSCSI
Overview.
Note:
When creating identities, keep in mind that:

z
Each identity can contain one or more iSCSI initiators.
An identity can be assigned an additional authentication method.
Each identity can be attached to more than one target.
Each target can have more than one identity.
To create identities:
1. In the Navigation pane, right click in Identities and select New Identity
The New Identity dialog box opens (Figure 4-19).

4-13
Figure 4-18. Identities Selected

2. Enter an Alias and Description for the identity.
Figure 4-19. New Identity Parameters

3. Click OK.
Adding Initiators to an Identity

After creating an identity, you can begin adding hosts to the identity by their iSCSI initiator
WWUIs.
To add initiators to an identity:
1. From the Identities List pane, select the identity, right click and select Properties (Figure
4-20).
4-14

Figure 4-20. Identity Selected

2. The Identity Properties dialog box opens (Figure 4-21).
Figure 4-21. Identity Properties Dialog Box

4-15
3. Click Add.
Figure 4-22. Add Identity

4. Enter the Identity Name (WWUI) of the initiator to add to the identity and Click OK.
5. The new initiator appears in the Names tab of the Identity Properties dialog box (Figure
4-21).
Assigning Identity Credentials (Initiator Authentication)

You can require initiator authentication before allowing access to a target and its underlying
disk(s). The Brocade iSCSI Gateway supports CHAP and SRP authentication methods.
Note:
z
When working with a Microsoft initiator and configuring target authentication:

Do not configure initiator passwords with a zero as the final character (since
the gateway exchanges the final character in the password with a zero).
CHAP passwords must be between twelve to sixteen characters in length.
If a host has more than one iSCSI initiator installed, both initiators can be
included in the identity and given authentication methods.
The user name and password do not need to be the same for different
initiators on the same host.
To assign authentication to an identity

1. From the Identities List pane, select the identity, right click and select Properties (Figure
4-20).
The Properties dialog box opens (Figure 4-21).
2. Toggle to the Authentication tab.
3. Click Add. Enter the authentication method parameters (Figure 4-23).
4-16

Figure 4-23. Authentication Method Parameters

4. Click OK. The added authentication method appears in the authentication table
(Figure 4-24).
Figure 4-24. Added Authentication Method
Attaching Identities to Targets

Once created, an identity must be attached to a target to provide it with access control. An
identity specifies which access rights the iSCSI initiators within the Identity have to the
target.
Note:
If you add or modify Identities on a target after its disks have been exposed, the access
rights will take effect only at the next login for each iSCSI initiator.

4-17
When an identity is attached to a target, it is also given a position in the target identity list.
The position of the identity determines its place in the gateway access rights evaluation.
z
The first identity in the list is the first identity evaluated when an initiator tries to access a
disk.
If the initiator meets the profile of the identity, it is granted that identitys access rights. If
not, the gateway continues to the next position. The gateway does not scan all identities
to determine which most specifically fits the host.
Identities must be positioned in decreasing specificity to function correctly.

The gateway scans for the first fit and not the best fit.
The default identity is evaluated last.
An identity can be connected to more than one target to provide the same pre-defined
list of initiators for each target.
To attach an identity to a target:

1. From the Navigation pane, select the target.
Figure 4-25. Attaching Identities to Targets

2. Click Attach Identities from the Authorized Identities pane (Figure 4-25).
The Attach Identities to Target window opens (Figure 4-26). Available identities are
listed in the bottom pane.
4-18

Figure 4-26. Attach Identities to Target Window

3. Select the identity to attach.
4. Click Attach
The identity is attached to the target.

5. Click the access rights for the identity and select the access rights from the list (Figure 427).
6. Click OK.

4-19
Figure 4-27. Access Rights for Identity

Note:
Restore returns the list to what exists in the devices.
4-20

Chapter 5
Monitoring & Statistics
The Brocade iSCSI Gateway enables RFC standards compliant health, interface and session
monitoring and statistics reporting of all gateway interfaces. For specific details on a
monitoring or statistic parameter, consult RFC standard 2863.
Health Monitoring
You can monitor the status of gateway hardware.
To view gateway hardware status:
z
In the Navigation pane, right click on the Brocade iSCSI Gateway and select Hardware.
Figure 5-1. Hardware Selected from Brocade iSCSI Gateway Menu

The gateway Hardware Status window opens.

5-1
Figure 5-2. Brocade iSCSI Gateway Hardware Status Window
Scroll and Zoom Functions

The performance statistics graphs include both scroll and zoom functions.
To scroll within a window:
1. Click the scroll icon
in the top right corner of the graph.
The cursor becomes a hand when placed inside the graph.
5-2
Brocade iSCI Gateway Manager Administrator's Guide

Figure 5-3. Scrolling within Graph

2. Holding down the left mouse button move the scroll hand in the direction you want to
scroll.
Figure 5-4. Graph Scrolled

5-3
To quick zoom an icon:

1. Click the zoom icon
2. Hold down the left mouse button and select the area to zoom in on.
Figure 5-5. Graph Area Selected

3. After the area is selected, release the mouse button.
Figure 5-6. Area Zoomed In
5-4

To zoom in/out on a specific range:

1. Click the zoom icon
2. Place the cursor in the graph. Right click and open the context menu.
3. Select to zoom in or out and along which axes.
Figure 5-7. Zoom Context Menu

5-5
Interface Statistics and Counters

You can view interface traffic statistics and errors for each gateway interface to aid in system
diagnostics
To view interface statistics:
z
In the Navigation pane, select the Brocade iSCSI Gateway, right click and select
Statistics > Interfaces.
Figure 5-8. Interface Statistics Selected from Brocade iSCSI Gateway Menu
The Interface Statistics window opens.
5-6

Figure 5-9. Brocade iSCSI Gateway Interface Statistics

5-7
TCP/IP
To view TCP/IP counters:
z
Statistics > IP.
The IP Statistics window opens.
Figure 5-10. IP Statistics Window
ICMP
To view ICMP statistics:
1. In the Navigation pane, select the Brocade iSCSI Gateway, right click and select Statistics
> ICMP.
The ICMP Statistics window opens.
5-8

Figure 5-11. ICMP Statistics Window

5-9
TCP
To view TCP statistics:
z
Statistics > TCP.
The TCP Statistics window opens.
Figure 5-12. TCP Statistics Window
5-10

UDP
To view UDP statistics:
z
Statistics > UDP.
The UPD Statistics window opens.
Figure 5-13. UDP Statistics Window

5-11
iSCSI Statistics
You can monitor iSCSI sessions including:
z
All iSCSI sessions in and out of the gateway.
All iSCSI sessions for a specific initiator or target.
Specific iSCSI session details.
Figure 5-14. iSCSI Menu
5-12

Viewing iSCSI Session Information

To view iSCSI session information:
z
In the Navigation pane, select the Brocade iSCSI Gateway, right click and select iSCSI >
Info (Figure 5-14).
The iSCSI Information window opens.
Figure 5-15. iSCSI Information Window

5-13
Viewing iSCSI Sessions

To view iSCSI sessions:
z
Sessions > Show (Figure 5-14).
The iSCSI Sessions window opens.
Figure 5-16. iSCSI Sessions Window
5-14

Viewing iSCSI Session Statistics

To view iSCSI Session Statistics:
z
Sessions > Statistics (Figure 5-14).
The iSCSI Sessions Statistics window opens.
Figure 5-17. iSCSI Sessions Statistics

5-15
iSCSI Connection Statistics

You can monitor iSCSI connections including:
z
All iSCSI connections in and out of the Brocade iSCSI Gateway.
All iSCSI connections for a specific initiator or target.
Specific iSCSI connection details.
Viewing iSCSI Connections

To view iSCSI connections:
z
Connections > Statistics (Figure 5-14).
The iSCSI Connections window opens.
Figure 5-18. iSCSI Connections Window
Viewing Connected iSCSI Initiators

To view connected iSCSI Initiators:
z
Connected Initiators > Show (Figure 5-14).
The iSCSI Connected Initiators window opens.
5-16

Figure 5-19. Target Connected iSCSI Initiators
Viewing iSCSI Initiator Statistics

To view iSCSI initiator statistics:
z
Connected Initiators > Statistics.
Figure 5-20. Statistics Selected from the Connected Initiators Menu

5-17
The Connected Initiators Statistics window opens.
Figure 5-21. iSCSI Connected Initiators Statistics Window
5-18

Chapter 6
Troubleshooting
The Brocade iSCSI Gateway generates traps while encountering specific events. Upon
receiving the event notification, the Brocade iSCSI Gateway Manager triggers an alarm
report.
The alarms are viewable and can be sorted. The last ten unacknowledged alarms generated
are displayed in the bottom pane of the gateway manager.
Alarm Operations
Brocade iSCSI Gateway Manager supports alarm messages for real-time tracking and
monitoring of both gateway manager and Brocade iSCSI Gateway configurations and
activity. Alarms are time-stamped according to the SP server date and time.
Configuring Email Alarm Notification

You can send alarm messages via Email for off-site alarm monitoring. The administrator
should configure the alarms which will trigger the Email notification using Brocade iSCSI
Gateway Manager Alarms Notification Configuration list.
A user profile must be configured on the SMTP server for sending Email notifications
received from gateway manager. The profile must include a user name and password for
authentication. The SMTP server parameters are:
z
Mail Server: Name or IP address of SMTP server
From Address: Address that Email appears to be sent from
User Name: User authentication name
Password: User authentication password
To configure the alarm notification list:

1. From the gateway manager toolbar, select Alarms > Configure
Figure 6-1. Alarms Menu

The Alarms Notification Configuration window opens.
Troubleshooting
6-1
2. Select each alarm for which you want to receive email notification.
3. Click OK.
Figure 6-2. Selected Alarms for Email Notification

To configure the email address for alarm notification:
1. From the gateway manager toolbar, select Configure > Email
Figure 6-3. Configure Menu

6-2

The Email Configuration dialog box opens.

2. Enter the name or IP address of the SMTP server.
3. Enter the email address for the outgoing email notification.
4. Enter the User Name and Password for user authentication.
Figure 6-4. SMTP Server Configuration

5. Toggle to the Destination tab and click Add
The Add Address dialog box opens.
6. Enter the Email address to send alarm notifications to and click OK.
Figure 6-5. Email to Send Alarm Notification to

Note:
Email is sent only at the time when an alarm is generated. If an alarm entry already exists during
the Email notification configuration, an Email notification will not be sent.
Troubleshooting
6-3
Viewing Specific Alarms

Every alarm can be associated with a specific Brocade iSCSI Gateway Manager element, e.g.
cluster, gateway, logical units or storage.
To view specific alarms:
1.
Select the element.
2. Right click and select Alarms > Specific.
Figure 6-6. Specific Alarms Selected

The Specific Alarms window opens.
Figure 6-7. Specific Alarms Window

From the Specific Alarms window, you can select an alarm and view its source and
properties. You can also close an alarm. This will remove the closed alarm from the Current
Alarms list and move it to the History Alarms list.
Viewing Propagated Alarms

z
A propagated alarm is generated by a source which is a logical member of a selected

element.
The Propagated Alarms window lists all the specific alarms of a selected element as
well as all the selected element derived alarms.
To view propagated alarms:

1. Select the element whose propagated alarms you want to view. Right click and select
Alarms > Propagated.
The Propagated Alarms window opens with all propagated alarms for the element.
6-4

Figure 6-8. Propagated Alarms Window

From the Propagated Alarms window, you can select an alarm in order to view its source
and properties. You can also close an alarm. This deletes it from the Current Alarms list and
moves it to the Closed Alarms list.
Viewing Alarms History

You can view the list of all acknowledged (previous) alarms.
To view previous alarms:
z
From the standard gateway manager toolbar, click Alarms > History or click the
History button
.
Figure 6-9. Alarms Menu

The Alarms History window opens.
Troubleshooting
6-5
Figure 6-10. Alarms History Window
Viewing Current Alarms

You can view all current open alarms for all the Brocade iSCSI Gateway Manager elements.
To view current alarms:
z
From the standard gateway manager toolbar, click Alarms > Current
The Current Alarms window opens.
Figure 6-11. Current Alarms Window
6-6

Acknowledging an Alarm
An acknowledged alarm still exists but its severity will not propagate to higher levels.
However, the alarm will still be listed in the Current Alarms window, along with the name of
the user who acknowledged the alarm.
Note:
If an alarm is listed in the Last 10 Alarms pane, after being acknowledged it is removed
from the pane.
To acknowledge an alarm:
1. Select the alarm to acknowledge.
2. Do one of the following:
z
Right click and select Acknowledge
OR
z
Check the Ack checkbox from any alarm pane.
If the alarm was in the Last 10 Alarms pane, it is removed.
Figure 6-12. Acknowledge Alarm
Troubleshooting
6-7
Figure 6-13. Ack Checkbox
Closing an Alarm
Once an alarm occurs, it remains in the current alarm list till the situation that caused it
ceases. However, it can be removed from the current alarm list and moved to the History
Alarm list.
If the event that generated the alarms occurs again, another alarm will be generated and
added to the current alarm list.
To close an alarm:
1. Select the alarm to close. Right click and select Close.
Figure 6-14. Close Alarm

The Close Alarm dialog box opens.
2. Click Yes to reconfirm the alarm closure.
6-8

Figure 6-15. Close Alarm Confirmation Dialog Box

The alarm will be closed and removed from the pane. You can view the closed alarm in
the Alarms History window (Figure 6-10).
Viewing Alarm Properties

You can view the properties of an alarm, including:
z
Alarm Severity
Alarm Name
Source Name
Source Type
Date Opened
Category
Probable Cause
Alarm Text
Use the alarm properties to help solve the alarm issue.

To display alarm properties:
1. From any of the alarm windows, select the alarm whose properties you want to view.
2. Right click and select Properties.
Figure 6-16. Properties
Troubleshooting
6-9
The Alarm Properties window opens.
Figure 6-17. Alarm Properties Window
Alarm Severity
Brocade iSCSI Gateway Manager supports four types of alarms:
z
Warning alarms: may be temporary but the administrator should be notified of.
Warning alarms are marked with a blue exclamation mark .
Minor alarms: may cause service interruption or have an administrative reason.

Minor alarms are marked with a yellow exclamation mark .
Major alarms: may cause service interruption and clearly indicated problems in the
gateway or gateway manager operation. Major alarms are marked with an orange
exclamation mark .
Critical alarms: represent service interruption. Critical alarms are marked with a
red exclamation mark .
Table 6-1: Brocade iSCSI Gateway Manager Alarms
6-10
Name
ID
Troubleshooting
Storage is missing
0101
Storage Invalid
0102
Reconnect.
Storage has been disconnected.
The administrator can reconnect the
storage.
A storage known by the system is configured Delete.
differently.
The administrator can delete the storage.
Action

Name
ID
Troubleshooting
Target will only be operational with a LU.

There is no LU exposed on this target.
Fans faulty
0401 One FAN (and only one) doesn't work. Call
support to replace the FAN.
Fans critical
0402 Both Fans don't work. Call support to
replace the Fans.
CPU temperature
0404 The temperature of the CPU is above the
warning
tolerable threshold. Turn off the switch and
call support.
On-board
0405 The on-board temperature is above the
temperature warning
tolerable threshold. Turn off the switch and
call support.
No fans
0406 No fans are working. Turn off the gateway
and call support.
CPU temperature
0407 The temperature of the CPU is above the
critical
critical threshold. Turn off the switch and
call support.
On-board
0408 The on-board temperature is above the
temperature critical
critical threshold. Turn off the switch and
call support.
Neighbor dead
0502 Brocade iSCSI Gateway lost connection with
one of its neighbors. Check the network.
Reconnecting the gateway will close the
alarm
Unknown Neighbor 0504 Brocade iSCSI Gateway doesnt know the
state of one of its neighbors.
Neighbor unknown 0504 Brocade iSCSI Gateway doesn't know the
state of one of its neighbors. After few
seconds this alarm will be closed.
Object not
0505 An object doesn't exist in the database of
redundant
one of the gateways of the cluster.
Synchronizing the object will solve the
problem.
Alias inconsistency
0506 Inconsistent Alias.
By giving a new alias to the object, the
administrator will remove the alarm
condition
LU number
0507 The same object has different LUNs on the
inconsistency
same target on two switches in the cluster.
Delete one of the LU and synchronize the
other one.
Data Attributes
0508 Some parameters of an object are different
inconsistency
according to the gateway; if the parameters
are writeable, re-writing them should solve
the problem.
LU storage
0512 A specific LUN is pointing to two different
inconsistency
objects within the cluster. Deleting the LU
and re-exposing will solve the problem.
Theoretical target
0301
Troubleshooting
Action
Expose LU
Fan is not
working.
Call Tech
Support.
Turn off gateway.
Turn off gateway.
Turn off gateway.

Turn off gateway.
Turn off gateway.
Reconnect
Wait.
Wait.
Synchronize.
Configure.
Delete and
synchronize.
Configure.
Delete and
expose.
6-11
Name
ID
Target disk
inconsistency
Delete.
An object is exposed on a different target
on two gateways of the cluster.
Delete one of the LU and synchronize the
other one.
Wait.
0514 Brocade iSCSI Gateway has taken over its
neighbor.
Reconnecting the second gateway will
solve this alarm condition.
0515 ACL configuration is different within the
Reconfigure ACL.
cluster.
Configure.
0518 The switches are not configured as being
neighbors. Try to rediscover your cluster.
Select cluster, right click and select
Rediscover.
0519 A target is inconsistently exposed among the Configuration.
cluster.
The administrator should change the
exposure of the target.
0525 ACL entry is not defined at the same target in Activate
each gateway in the cluster.
Synchronization.
0103 The gateway doesnt know the state of the Select cluster
storage.
level and
Rediscover.
Reconnect
0901 Brocade iSCSI Gateway Manager lost
connection with a gateway. Check the
network.
Reconnecting the gateway will close the
alarm.
You can check also that the server's IP
address is defined in the switch as manager
by using the CLI command: SNMP manager
show. If it is not, please add it by using the
CLI command: SNMP manager add -ip <IP
address>
0902 Brocade iSCSI Gateway trap port is already Configuration.
in use. Change the trap port via gateway
->Properties ->SNMP to receive traps from
this gateway.
This trap port is where Brocade iSCSI
Gateway Manager listens from. The trap port
must also be changed in the CLI. This trap
port is where the gateway sends from.
1001 An interface stopped functioning.
Reconnect.
Check that the cable is plugged in correctly.
Brocade iSCSI
Gateway takeover
Inconsistent ACL
Brocade iSCSI
Gateways are not
neighbors
Target exposed
inconsistency
ACL not redundant

Storage Unknown
Brocade iSCSI
Gateway
disconnected
Trap port in use
Link Down
6-12
Troubleshooting
Action
0513

Index
A
Add
iSCSI Portal ............................................ 3-11
iSNS .......................................................3-20
User Profile ............................................. 3-2
Address masks............................................. 5-8
Address masks reply ................................... 5-8
Alarm
Closing ....................................................6-8
Current....................................................6-6
History.....................................................6-6
Propagated ............................................. 6-5
Properties ...............................................6-9
Severity.................................................. 6-10
specific ....................................................6-4
Alarm ID
0101 ........................................................ 6-11
0102........................................................ 6-11
0301........................................................ 6-11
0401 ....................................................... 6-11
0402....................................................... 6-11
0404....................................................... 6-11
0405 ....................................................... 6-11
0406....................................................... 6-11
0407 ....................................................... 6-11
0408....................................................... 6-11
0502 ....................................................... 6-11
0504 ....................................................... 6-11
0504 ....................................................... 6-11
0505 ....................................................... 6-11
0506.......................................................6-12
0507 .......................................................6-12
0508.......................................................6-12
0512 ........................................................6-12
0513 ........................................................6-12
0514 ........................................................6-12
0515 ........................................................6-12
0518........................................................6-12
0519........................................................6-12
0525........................................................6-12
0901 .......................................................6-12
0902.......................................................6-13
Index
1001........................................................ 6-13
1003 ....................................................... 6-12
Authentication
target........................................................ 1-8
B
management .......................................... 1-15
Offline.................................................... 3-18
Resetting............................................... 3-28
Brocade iSCSI Gateway Cluster..................1-11
Brocade iSCSI Gateway Properties ............3-6
Date & Time ............................................3-7
IP Address................................................3-8
C
CHAP
double authentication ..........................4-11
Cluster ..........................................................1-11
Configure
IP Routing .............................................. 3-12
iSCSI........................................................ 3-11
Connections
current number..................................... 5-10
open active............................................ 5-10
open passive ......................................... 5-10
Current Alarms ........................................... 6-6
D
Datagrams
errors ...................................................... 5-11
received.................................................. 5-11
sent ......................................................... 5-11
wrong port.............................................. 5-11
Date and Time .............................................3-7
Delete..........................................................4-11
LU............................................................4-11
Delivers ........................................................5-8
I-1
Destinations unreachable.......................... 5-8

Discards....................................................... 5-8
Discover .................................................... 3-26
Disk Storage.......................................... 3-26
Discover LUNs .......................................... 3-26
Disk Storage .............................................. 3-26
Discovering........................................... 3-26
E
Errors
datagrams .............................................. 5-11
in address................................................ 5-8
in header................................................. 5-8
in/out ...................................................... 5-8
received ................................................ 5-10
Exclamation Mark ...................................... 1-14
F
Failback.......................................................3-18
Faulty interval ............................................. 1-14
Firewall ...................................................... 3-25
Interval
faulty .......................................................1-14
keep alive ...............................................1-14
suspicious...............................................1-14
IP
Active.......................................................1-11
Inactive ....................................................1-11
Neighbor .................................................1-11
IP Address ............................................3-8, 3-11
IP Route
Configuring ........................................... 3-12
iSCSI ............................................................ 3-11
Portal ...................................................... 3-11
Target...................................................... 3-11
iSCSI connection statistics ........................ 5-16
iSCSI session statistics ............................... 5-12
iSNS ........................................................... 3-20
K
Keep alive interval......................................1-14
Keep alive signal.........................................1-14
L
LU ........................................................ 4-8, 4-11
LUNs discovery......................................... 3-26
Health monitoring .......................................5-1
I
Icons
Critical Alarm......................................... 6-11
Major Alarm........................................... 6-11
Minor Alarm ......................................... 6-10
Warning Alarm ..................................... 6-10
In
address errors......................................... 5-8
delivers.................................................... 5-8
destination unreachable ....................... 5-8
discards ................................................... 5-8
echo reply............................................... 5-8
echos....................................................... 5-8
header errors .......................................... 5-8
parameter problems .............................. 5-8
receives ................................................... 5-8
redirect.................................................... 5-8
search quench ........................................ 5-8
time exceeds .......................................... 5-8
In-band ....................................................... 1-15
Interface statistics........................................ 5-6
Internet Storage Name Service ................3-20
I-2
M
Messages......................................................5-8
Monitoring
health....................................................... 5-1
N
NAT...............................................................2-7
Neighbor
Removing .............................................. 3-18
Network topology ........................................ 1-1
Network Translation Environment.............2-7
Number of connections............................ 5-10
O
Offline
Brocade iSCSI Gateway........................ 3-18
Open
active connections................................ 5-10
passive connections ............................. 5-10
Out
destination unreachable ....................... 5-8
discards ................................................... 5-8
echo reply............................................... 5-8
echos....................................................... 5-8
no routes................................................. 5-8
parameter problems .............................. 5-8
redirect.................................................... 5-8
requests................................................... 5-8
search quench ........................................ 5-8
time exceeds .......................................... 5-8
Out-of-band ............................................... 1-15
P
Password ..................................................... 3-2
Portal........................................................... 3-11
Propagated Alarms ..................................... 6-5
R
Read Community...................................... 3-23
Received
address masks......................................... 5-8
address masks reply ............................... 5-8
datagrams .............................................. 5-11
errors..................................................... 5-10
messages................................................. 5-8
segments............................................... 5-10
timestamps ............................................. 5-8
timestamps reply.................................... 5-8
Re-Discover............................................... 3-26
Rediscover gateway or Cluster ................ 3-26
Rediscovering Storage Devices ............... 3-26
Remove
Exposed Volume ................................... 4-11
LU0......................................................... 4-11
Neighbor................................................3-18
Report LUNs .............................................. 3-26
Reset establishments ................................ 5-10
Reset sent .................................................. 5-10
Retries ........................................................ 3-23
RS232 .......................................................... 1-15
S
Scroll Function ............................................ 5-2
Segments
received ................................................ 5-10
retransmitted ........................................ 5-10
sent........................................................ 5-10
Index
Sent
address masks .........................................5-8
datagrams............................................... 5-11
messages .................................................5-8
reset ....................................................... 5-10
segments ............................................... 5-10
timestamps..............................................5-8
timestamps reply ....................................5-8
Service Agent ............................................... 1-3
Service Location Protocol........................... 1-3
SNMP
Configuration........................................3-23
Version ..................................................3-23
Specific alarms............................................ 6-4
Statistics
interface...................................................5-6
iSCSI connections................................. 5-16
iSCSI sessions ........................................ 5-12
TCP......................................................... 5-10
TCP/IP Counters.....................................5-8
UDP ........................................................ 5-11
Suspicious interval .....................................1-14
Synchronize ........................................1-14, 3-11
T
Target ..................................................3-11, 4-11
Alias ........................................................ 4-8
authentication................................ 1-8, 4-16
Name ...................................................... 4-8
Properties ............................................... 4-8
TCP/IP Counters .........................................5-8
Telnet .................................................1-15, 3-25
Telnet Session, Opening...........................3-24
Time stamps.................................................5-8
Timeout......................................................3-23
TRAP UDP Port ..........................................3-23
U
UDP listeners .............................................. 5-11
UDP Port ....................................................3-23
UDP statistics .............................................. 5-11
Unexpose
Exposed Volume....................................4-11
User Password .............................................3-2
User Profile ..................................................3-2
V
View.................................................... 3-23, 4-8
I-3
SNMP Configuration............................ 3-23

Target Properties....................................4-8
Z
Zoom Functions ..........................................5-2
quick zoom .............................................5-4
zoom in/out............................................5-5
World Wide Unique Identifier ...................1-2

Write Community ..................................... 3-23
Wrong port datagrams .............................. 5-11
WWUI................................................... 1-2, 4-8
I-4


Brocade ISCSI Gateway MGR v326 Admin Guide

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Brocade ISCSI Gateway MGR v326 Admin Guide

Încărcat de

Drepturi de autor:

Formate disponibile

iSCSI Gateway Manager

Supporting Brocade iSCSI Gateway

Publication Number: 53-1000203-01 Rev. A

Copyright 2006, SANRAD, Inc..

Publication Number: 53-1000203-01 Rev. A

Brocade Communications Systems, Incorporated

European and Latin American Headquarters

Brocade iSCSI Gateway

Installation Operations ......................................................................... 2-1

Brocade iSCSI Gateway Operations ..................................................... 3-1

Brocade iSCSI Gateway & Cluster Configuration ..................................................... 3-3

Storage Exposure & Security ................................................................. 4-1

Monitoring & Statistics.......................................................................... 5-1

iSCSI Gateway Manager Administrators Guide

Scroll and Zoom Functions....................................................................................... 5-2

Troubleshooting ................................................................................... 6-1

Index ..................................................................................................... I-1

Brocade iSCSI Gateway Network Topology..................................................................1-1

Brocade iSCSI Gateway Manager Client Location...................................................... 2-8

Target Properties Authentication Tab ...................................................................... 4-11

iSCSI Gateway Manager Administrators Guide

Brocade iSCSI Gateway Topology

Storage elements can be a combination of FC JBOD (Just a Bunch Of Disks) or FC RAID

Brocade iSCSI Gateway Network Topology

Introduction to Brocade iSCSI Gateway Manager

Can use existing Ethernet cabling and existing network elements.

Uses common TCP/IP for global connectivity.

Leverages the existing expertise of network administrators, integrators and support

iSCSI Initiator and Targets

The iSCSI initiator resides in the host computer.

The iSCSI target resides in the Brocade iSCSI Gateway.

Targets and LUNs

When creating targets, keep in mind that:

Each target can have multiple LUNs.

Each target can be accessed by multiple hosts.

There are two ways to expose a disk:

Exposing Disks and Creating a New Target in Chapter 4.

Stand-Alone Target in Chapter 4.

Figure 1-2. iSCSI Target Access

Introduction to Brocade iSCSI Gateway Manager

When planning and creating identities, keep in mind that:

Each identity can contain one or more iSCSI initiators.

Each identity can be attached to more than one target.

Each target is first automatically coupled to a default read-write un-authenticated

Brocade iSCSI Gateway Manager Administrator's Guide

Identity A is coupled with both Targets 1 and 2.

Identity B is coupled with Target 3.

Identity C is coupled with Target 4.

As a result, each iSCSI initiator has access to the following disks:

Figure 1-3. Identities Coupled with Targets

Introduction to Brocade iSCSI Gateway Manager

Figure 1-4. Default Identities

Brocade iSCSI Gateway Manager Administrator's Guide

Figure 1-5. Access Rights per Identity-Target Pair

Introduction to Brocade iSCSI Gateway Manager

Target and Initiator Authentication

An identity can be assigned an additional authentication method.

If no authentication method is assigned, all listed iSCSI initiators in an identity

A separate user name + password for each initiator.

A few user name + password pairs common to a few initiators

A single user name + password for all initiators in the identity.

Brocade iSCSI Gateway Manager Administrator's Guide

Six iSCSI initiators in Identity B