Implementing an Open IBM SAN

Front cover
Implementing an
Open IBM SAN
Discover the latest additions to the IBM
SAN family
Enhance your skills while using
an easy-to-follow format
Grow with the new
technology
Jon Tate
Brian Cartwright
Sven Eichelbaum
Thomas Jahn
ibm.com/redbooks
International Technical Support Organization
Implementing an Open IBM SAN
November 2001
SG24-6116-01
Take Note! Before using this information and the product it supports, be sure to read the
general information in “Special notices” on page 849.
Second Edition (November 2001)
This edition applies to components, programs, architecture, and connections between multiple
platforms and storage systems and a diverse range of hardware and software.
Comments may be addressed to:
IBM Corporation, International Technical Support Organization
Dept. QXXE Building 80-E2
650 Harry Road
San Jose, California 95120-6099
When you send information to IBM, you grant IBM a non-exclusive right to use or distribute the
information in any way it believes appropriate without incurring any obligation to you.
© Copyright International Business Machines Corporation, 2000, 2001. All rights reserved.
Note to U.S Government Users – Documentation related to restricted rights – Use, duplication or disclosure is subject to
restrictions set forth in GSA ADP Schedule Contract with IBM Corp.
Summary of changes
This section describes the technical changes made in this edition of the book and
in previous editions. This edition may also include minor corrections and editorial
changes that are not identified.
Summary of Changes
for SG24-6116-01
for IBM SAN Implementation
as created or updated on November 27, 2001.
SG24-6116-01 November 2001
This revision reflects the addition, deletion, or modification of new and changed
information described below.
New information






2109 Model F16
INRANGE FC/9000
ED-6064
ES-3032
ES-3016
ES-1000
Changed information
 Removed planning information, as this is available in other IBM Redbooks on
SAN
 Host Bus Adapters
© Copyright IBM Corp. 2001
iii
iv
IBM SAN Implementation
Contents
Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
SG24-6116-01 November 2001 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxiii
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxv
The team that wrote this redbook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxv
Special notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxxvii
IBM trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxviii
Comments welcome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxviii
Chapter 1. Implementing Fibre Channel host adapter cards . . . . . . . . . . . 1
1.1 Fibre Channel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1.1 Fibre Channel cables and adapter types . . . . . . . . . . . . . . . . . . . . . . 2
1.1.2 Fibre Channel node-to-node distances . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1.3 LUN affinity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1.4 Targets and LUNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.2 Attaching an ESS to a FICON channel . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.2.1 Configuring the ESS for FICON attachment . . . . . . . . . . . . . . . . . . . . 4
1.2.2 Attachment considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.2.3 Setting up ESCON and FICON links . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.2.4 Multipathing for ESCON and FICON. . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.2.5 Attaching to a FICON channel or a FICON channel path group . . . . . 6
1.2.6 Attaching an ESS to FICON channels . . . . . . . . . . . . . . . . . . . . . . . . 7
1.3 IBM iSeries FC host system attachment . . . . . . . . . . . . . . . . . . . . . . . . 8
1.3.1 Host limitations for the iSeries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.3.2 Attachment requirements for the AS/400 or iSeries . . . . . . . . . . . . . . 9
1.3.3 Attachment considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.3.4 Recommended configurations for the AS/400 or iSeries . . . . . . . . . 10
1.3.5 Software requirements for the IBM OS/400 operating system . . . . . 11
1.4 IBM RS/6000 or pSeries FC host system attachment . . . . . . . . . . . . . 11
1.4.1 Attachment requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.4.2 Installing the 2105 host attachment package . . . . . . . . . . . . . . . . . . 13
1.4.3 Replacing an older version of the 2105 installation package . . . . . . 13
1.4.4 Installing the 2105 host attachment package . . . . . . . . . . . . . . . . . . 14
1.4.5 Verifying the ESS configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.4.6 ESS devices with multiple paths per LUN . . . . . . . . . . . . . . . . . . . . . 15
© Copyright IBM Corp. 2001
v
1.5 IBM eServer xSeries or IBM NUMA-Q FC attachment . . . . . . . . . . . . 15
1.5.1 Attachment requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.5.2 xSeries and NUMA-Q system requirements . . . . . . . . . . . . . . . . . . . 16
1.5.3 Installing the IOC-0210-54 adapter card . . . . . . . . . . . . . . . . . . . . . . 17
1.5.4 Configuring the IOC-0210-54 adapter card . . . . . . . . . . . . . . . . . . . . 17
1.6 Compaq host system FC attachment . . . . . . . . . . . . . . . . . . . . . . . . . 18
1.6.1 Attachment requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1.6.2 Compaq Tru64 UNIX Version 4.0x host system . . . . . . . . . . . . . . . . 19
1.6.3 Verifying the Compaq configuration . . . . . . . . . . . . . . . . . . . . . . . . . 19
1.6.4 Operating system device recognition . . . . . . . . . . . . . . . . . . . . . . . . 19
1.6.5 Configuring AdvFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
1.6.6 Configuring devices to mount automatically . . . . . . . . . . . . . . . . . . . 22
1.7 Hewlett Packard 9000 FC host system attachment . . . . . . . . . . . . . . . 23
1.7.1 Attachment requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
1.7.2 Installing the 2105 host install script file . . . . . . . . . . . . . . . . . . . . . . 24
1.7.3 Configuring the IBM 2105 for clustering . . . . . . . . . . . . . . . . . . . . . . 25
1.8 Novell NetWare FC host system attachment . . . . . . . . . . . . . . . . . . . 26
1.8.1 Installing the QLogic QLA2100F adapter card . . . . . . . . . . . . . . . . . 26
1.8.2 Installing the QLogic QLA2200F adapter card . . . . . . . . . . . . . . . . . 27
1.8.3 Loading the current Fibre Channel adapter driver . . . . . . . . . . . . . . 29
1.8.4 Installing the Fibre Channel adapter drivers . . . . . . . . . . . . . . . . . . . 29
1.8.5 ESS QLogic QLA2100F/2200F host adapter card . . . . . . . . . . . . . . 30
1.9 Sun FC host system attachment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
1.9.1 Attachment requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
1.9.2 Installing the Emulex LP8000 adapter card . . . . . . . . . . . . . . . . . . . 32
1.9.3 Downloading the current Emulex Fibre Channel adapter driver . . . . 33
1.9.4 Installing the Fibre Channel adapter drivers . . . . . . . . . . . . . . . . . . . 33
1.9.5 Installing the JNI PCI adapter card . . . . . . . . . . . . . . . . . . . . . . . . . . 35
1.9.6 Downloading the current JNI PCI Fibre Channel adapter driver . . . . 35
1.9.7 Installing the JNI PCI Fibre Channel adapter driver . . . . . . . . . . . . . 36
1.9.8 Installing the JNI SBUS adapter card . . . . . . . . . . . . . . . . . . . . . . . . 36
1.9.9 Downloading current JNI SBUS Fibre Channel adapter driver . . . . . 37
1.9.10 Installing the JNI SBUS Fibre Channel adapter driver . . . . . . . . . . 37
1.9.11 Installing the QLogic QLA2200F adapter card . . . . . . . . . . . . . . . . 38
1.9.12 Downloading the current Fibre Channel adapter driver . . . . . . . . . 39
1.9.13 Installing the Fibre Channel adapter drivers . . . . . . . . . . . . . . . . . . 40
1.9.14 Configuring host device drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
1.9.15 Tuning HBA configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
1.9.16 Installing the IBM Subsystem Device Driver . . . . . . . . . . . . . . . . . . 44
1.9.17 Setting the Sun host system parameters . . . . . . . . . . . . . . . . . . . . 45
1.10 Windows NT 4.0 FC host system attachment . . . . . . . . . . . . . . . . . . 47
1.10.1 Attachment requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
1.10.2 Installing the QLogic QLA2100F adapter card . . . . . . . . . . . . . . . . 48
vi
IBM SAN Implementation
1.10.3 Installing the QLogic QLA2200F adapter card . . . . . . . . . . . . . . . . 49
1.10.4 Downloading the current Fibre Channel adapter driver . . . . . . . . . 51
1.10.5 Installing the Fibre Channel adapter drivers . . . . . . . . . . . . . . . . . . 52
1.10.6 QLogic QLA2100F or QLogic QLA2200F configuration . . . . . . . . . 52
1.10.7 Configuring for availability and recoverability . . . . . . . . . . . . . . . . . 52
1.10.8 Setting the TimeOutValue registry . . . . . . . . . . . . . . . . . . . . . . . . . 53
1.10.9 Installing Emulex LP8000 adapter cards. . . . . . . . . . . . . . . . . . . . . 53
1.10.10 Downloading the current Fibre Channel adapter driver . . . . . . . . 54
1.10.11 Installing the Fibre Channel adapter drivers . . . . . . . . . . . . . . . . . 55
1.10.12 Parameter settings for the Emulex LP8000 on Windows NT . . . . 56
1.10.13 Verifying the configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
1.10.14 Verifying networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
1.11 Windows 2000 FC host system attachment . . . . . . . . . . . . . . . . . . . 58
1.11.1 Attachment requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
1.11.2 Installing the QLogic QLA2100F adapter card . . . . . . . . . . . . . . . . 59
1.11.3 Installing the QLogic QLA2200F adapter card . . . . . . . . . . . . . . . . 60
1.11.4 Downloading the current Fibre Channel adapter driver . . . . . . . . . 62
1.11.5 Installing the Fibre Channel adapter drivers . . . . . . . . . . . . . . . . . . 63
1.11.6 QLogic QLA2100F or QLogic QLA2200F configuration . . . . . . . . . 63
1.11.7 Configuring for availability and recoverability . . . . . . . . . . . . . . . . . 64
1.11.8 Setting the TimeOutValue registry . . . . . . . . . . . . . . . . . . . . . . . . . 64
1.11.9 Installing Emulex LP8000 adapter cards. . . . . . . . . . . . . . . . . . . . . 65
1.11.10 Downloading the current Fibre Channel adapter driver . . . . . . . . 65
1.11.11 Installing the Fibre Channel adapter drivers . . . . . . . . . . . . . . . . . 66
1.11.12 Parameter settings for the Emulex LP8000 on Windows 2000 . . . 67
1.11.13 Verifying the configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
1.11.14 Verifying networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
1.12 Locating the worldwide port name . . . . . . . . . . . . . . . . . . . . . . . . . . 69
1.12.1 Fibre Channel port name identification . . . . . . . . . . . . . . . . . . . . . . 69
1.12.2 Locating the WWPN for an AS/400 iSeries . . . . . . . . . . . . . . . . . . . 70
1.12.3 Locating the WWPN for an IBM eServer or IBM NUMA-Q host . . . 71
1.12.4 Locating the WWPN for an RS/6000 and pSeries host system . . . 71
1.12.5 Locating the WWPN for a Compaq host system . . . . . . . . . . . . . . . 71
1.12.6 Locating the WWPN for a Hewlett Packard host system . . . . . . . . 72
1.12.7 Locating the WWPN for a Novell NetWare host system . . . . . . . . . 73
1.12.8 Locating the WWPN for a Sun host system . . . . . . . . . . . . . . . . . . 73
1.12.9 Locating the WWPN for a Windows NT host system . . . . . . . . . . . 74
1.12.10 Locating the WWPN for a Windows 2000 host system . . . . . . . . . 74
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration . . 75
2.1 Introducing the ESS Web Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . 77
2.1.1 Logging on to the ESS Specialist . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
2.1.2 Operating the ESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Contents
vii
2.1.3 Configuring the ESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
2.1.4 Administer the ESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
2.2 Starting the Open Systems Storage Configuration . . . . . . . . . . . . . . . 96
2.2.1 Viewing the storage configuration status . . . . . . . . . . . . . . . . . . . . . 96
2.2.2 Using the Open System Storage panel. . . . . . . . . . . . . . . . . . . . . . 104
2.3 Configuring disk groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
2.3.1 Performing the disk group configuration . . . . . . . . . . . . . . . . . . . . . 108
2.4 Creating and modifying host FC port definitions . . . . . . . . . . . . . . . . 116
2.4.1 Creating host FC port definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . 117
2.4.2 Modifying a host FC port definition . . . . . . . . . . . . . . . . . . . . . . . . . 123
2.5 Creating and assigning ESS logical volumes . . . . . . . . . . . . . . . . . . 126
2.5.1 Adding ESS logical volumes, step one . . . . . . . . . . . . . . . . . . . . . . 126
2.5.2 Adding ESS logical volumes — step two . . . . . . . . . . . . . . . . . . . . 129
2.6 Modifying ESS logical volume assignments . . . . . . . . . . . . . . . . . . . 142
2.6.1 Sharing ESS logical volumes between two host FC ports . . . . . . . 143
2.6.2 Removing volume assignments from host FC ports . . . . . . . . . . . . 151
2.7 Configuring ESS FC ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
2.7.1 Defining the topology for ESS FC ports . . . . . . . . . . . . . . . . . . . . . 159
2.7.2 ESS managed ESS FC port WWPNs . . . . . . . . . . . . . . . . . . . . . . . 164
2.7.3 Configuring host FC ports for FC-SW and FC-AL . . . . . . . . . . . . . . 167
Chapter 3. Implementing the IBM Managed Hub and Unmanaged Hub . 175
3.1 IBM Fibre Channel Storage Hub, 2103-H07 . . . . . . . . . . . . . . . . . . . 176
3.1.1 Hub configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
3.1.2 Hub installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
3.2 IBM TotalStorage SAN Managed Hub . . . . . . . . . . . . . . . . . . . . . . . 179
3.2.1 The ITSO environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
3.3 Installation of the Managed Hub . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
3.3.1 Setting the IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
3.4 QuickLoop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
3.4.1 Private loop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
3.4.2 Public loop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
3.4.3 Private devices in public fabrics . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
3.4.4 QuickLoop feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
3.4.5 Managed hub zoning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
3.5 Managing the Managed Hub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
3.5.1 Launching the hub specialist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
3.5.2 Accessing the Event Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
3.5.3 Beaconing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
3.5.4 Starting Telnet Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
3.5.5 Performance Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
3.5.6 Admin View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
3.5.7 Firmware Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
viii
IBM SAN Implementation
3.5.8 Reboot Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
3.5.9 SNMP Admin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
3.5.10 License Admin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
3.5.11 QuickLoop Admin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
3.5.12 Config Admin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
3.5.13 Port Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
3.5.14 Fabric Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
3.5.15 Name Server Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
3.6 Zoning and cascading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
3.6.1 Implementing zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
3.6.2 Zone Alias Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
3.6.3 Zone Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
3.6.4 Zone Config Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
3.6.5 Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
Chapter 4. Implementing an IBM TotalStorage SAN Switch . . . . . . . . . . 251
4.1 Product overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
4.1.1 IBM TotalStorage SAN Switch hardware components . . . . . . . . . . 253
4.1.2 IBM TotalStorage SAN Switch software features . . . . . . . . . . . . . . 260
4.2 Installing the IBM TotalStorage SAN Switch . . . . . . . . . . . . . . . . . . . 260
4.2.1 Security relating to switch installation . . . . . . . . . . . . . . . . . . . . . . . 261
4.2.2 Installing the 2109-S08 switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
4.2.3 Setting the IP address using the serial port (2109-S08 only) . . . . . 263
4.2.4 Setting the IP address on an IBM 2109-S16 . . . . . . . . . . . . . . . . . . 264
4.2.5 Upgrading the switch firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
4.2.6 Connecting to the switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
4.2.7 SAN installation verification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
4.2.8 Launching the IBM TotalStorage Specialist . . . . . . . . . . . . . . . . . . 278
4.3 Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
4.3.1 Fabric View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
4.3.2 Switch View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
4.3.3 Fabric Watch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
4.3.4 Fabric Wide Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
4.3.5 QuickLoop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
4.4 Zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
4.4.1 Increasing availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
4.5 Implementing zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
4.6 Cascading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
4.6.1 Using aliases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
4.6.2 More complex zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
4.6.3 Incorporating additional switches . . . . . . . . . . . . . . . . . . . . . . . . . . 379
4.6.4 Zoning using Alias Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
4.6.5 Enabling a configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
Contents
ix
4.7 Merging SAN fabrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
4.8 Fabric OS V2.4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
4.8.1 Fabric Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
4.8.2 Fabric Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
4.8.3 Zone Admin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412
4.8.4 Fabric Watch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422
4.8.5 Performing maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438
4.9 2109-S16 Integrated fabric RPQ 8S0566 . . . . . . . . . . . . . . . . . . . . . 442
4.10 TotalStorage Fibre Channel Switch 2109-F16 . . . . . . . . . . . . . . . . 443
4.10.1 Product overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444
4.10.2 Hardware components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
4.10.3 Software specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452
4.10.4 Interoperability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459
4.11 Installing the 2109-F16 Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461
4.11.1 Configuration instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462
4.12 Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465
4.13 Zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466
4.13.1 Zone types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466
4.13.2 Zone enforcement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467
4.13.3 Zone configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468
4.13.4 Enabling a zone configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
4.14 Implementing zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
4.14.1 Zone administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
4.14.2 Implementing Switch/Port Level Zoning . . . . . . . . . . . . . . . . . . . . 472
4.14.3 WWN Level Zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482
4.14.4 AL_PA Level Zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491
4.14.5 Mixed Level Zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500
4.15 ISL Trunking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509
4.15.1 Trunking groups, ports, and masters . . . . . . . . . . . . . . . . . . . . . . 510
4.15.2 Installing ISL Trunking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511
4.15.3 Administering ISL Trunking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512
4.16 Performance Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513
4.16.1 Performance Monitor menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515
4.17 Advanced Performance Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . 520
4.17.1 Performance Monitoring with Telnet commands . . . . . . . . . . . . . . 520
4.17.2 Performance Monitoring with TotalStorage Specialist . . . . . . . . . 521
4.17.3 Installing Performance Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . 522
4.17.4 Using Advanced Performance Monitoring. . . . . . . . . . . . . . . . . . . 524
4.18 Administrative interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529
4.19 Distributed fabrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556
4.19.1 Remote Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557
4.19.2 Installing Remote Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558
4.19.3 Using Remote Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559
x
IBM SAN Implementation
4.19.4
4.19.5
4.19.6
4.19.7
4.19.8
Configuring a Remote Switch fabric . . . . . . . . . . . . . . . . . . . . . . . 560
Extended Fabrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
Installing Extended Fabrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562
Using Extended Fabrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564
Configuring Extended Fabrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564
Chapter 5. Implementing the INRANGE FC/9000 Fibre Channel Director567
5.1 Introduction to the INRANGE FC/9000 director . . . . . . . . . . . . . . . . 568
5.1.1 Product overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569
5.1.2 Currently supported zoning methodologies. . . . . . . . . . . . . . . . . . . 570
5.1.3 Management capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 570
5.1.4 Supported protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571
5.1.5 Supported host attachment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572
5.1.6 Supported device attachment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573
5.2 Installing an INRANGE SAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573
5.2.1 Target SAN environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573
5.2.2 Verifying all prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574
5.2.3 Initial setup of INRANGE FC/9000 IP settings . . . . . . . . . . . . . . . . 575
5.2.4 Establishing network connection . . . . . . . . . . . . . . . . . . . . . . . . . . . 575
5.2.5 Installing the IN-VSN Enterprise Manager software . . . . . . . . . . . . 579
5.2.6 Accessing the management tool . . . . . . . . . . . . . . . . . . . . . . . . . . . 584
5.2.7 Defining users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 589
5.2.8 Security considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 597
5.3 Management of an INRANGE SAN. . . . . . . . . . . . . . . . . . . . . . . . . . 599
5.3.1 Setting up operational parameters . . . . . . . . . . . . . . . . . . . . . . . . . 599
5.3.2 Connecting to an INRANGE fabric . . . . . . . . . . . . . . . . . . . . . . . . . 603
5.3.3 Assigning names and aliases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605
5.3.4 Setting the director clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 610
5.3.5 Attaching loop ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 612
5.4 INRANGE zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 629
5.4.1 Understanding INRANGE hard zoning . . . . . . . . . . . . . . . . . . . . . . 629
5.4.2 Understanding INRANGE broadcast zoning . . . . . . . . . . . . . . . . . . 633
5.4.3 Understanding INRANGE name server zoning . . . . . . . . . . . . . . . . 634
5.4.4 Hard zones and name server zones together . . . . . . . . . . . . . . . . . 635
5.4.5 Defining hard zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 638
5.4.6 Defining name server zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644
5.5 Cascading of directors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655
5.6 Monitoring and maintenance of an INRANGE SAN . . . . . . . . . . . . . . 658
5.6.1 Management communication protocols . . . . . . . . . . . . . . . . . . . . . 658
5.6.2 Microcode-loads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 659
5.6.3 Monitoring user activities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 659
5.6.4 Using the IN-VSN event log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 661
5.7 ESS configuration guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 662
Contents
xi
Chapter 6. Implementing a SAN with McDATA . . . . . . . . . . . . . . . . . . . . . 663
6.1 Introducing the McDATA products . . . . . . . . . . . . . . . . . . . . . . . . . . 664
6.1.1 ED-6064 Fibre Channel Director . . . . . . . . . . . . . . . . . . . . . . . . . . . 664
6.1.2 ED-5000 Fibre Channel Director . . . . . . . . . . . . . . . . . . . . . . . . . . . 666
6.1.3 ES-3032 and ES-3016 fabric switches . . . . . . . . . . . . . . . . . . . . . . 667
6.1.4 The ES-1000 loop switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 668
6.1.5 The Fabricenter equipment cabinet . . . . . . . . . . . . . . . . . . . . . . . . 669
6.2 Setting up the environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671
6.2.1 Setting up the network environment . . . . . . . . . . . . . . . . . . . . . . . . 671
6.2.2 Installing the EFC Manager client on remote workstations . . . . . . . 675
6.2.3 Introduction to the EFC Manager . . . . . . . . . . . . . . . . . . . . . . . . . . 676
6.3 Managing the environment using the EFC Manager . . . . . . . . . . . . . 681
6.3.1 Logging in to the EFC Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . 682
6.3.2 Administering the SAN using the EFC Manager . . . . . . . . . . . . . . . 684
6.3.3 Defining users on the EFC Manager . . . . . . . . . . . . . . . . . . . . . . . . 685
6.3.4 Identifying devices to the EFC Manager . . . . . . . . . . . . . . . . . . . . . 688
6.3.5 Assigning nicknames to World Wide Port Names . . . . . . . . . . . . . . 690
6.4 Managing the devices using the Product Manager . . . . . . . . . . . . . . 692
6.4.1 Managing the ED-6064 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 693
6.4.2 Configuring the ED-5000 with the Product Manager. . . . . . . . . . . . 703
6.4.3 Managing the ES-3016 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 705
6.4.4 Introduction to the ES-1000 Product Manager . . . . . . . . . . . . . . . . 705
6.5 Understanding the McDATA zoning concepts . . . . . . . . . . . . . . . . . . 711
6.5.1 Zoning implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 712
6.5.2 Zone member definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 712
6.5.3 Zone management with zone sets . . . . . . . . . . . . . . . . . . . . . . . . . 713
6.6 Managing the fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715
6.6.1 Using the Fabric Manager views . . . . . . . . . . . . . . . . . . . . . . . . . . . 716
6.6.2 Zones, zone sets, and zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717
6.6.3 Adding an AIX zone to the existing zone set. . . . . . . . . . . . . . . . . . 729
6.7 Building a multiswitch fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 734
6.7.1 Multiswitch fabric considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . 734
6.7.2 Solutions for high availability and disaster tolerance . . . . . . . . . . . 735
6.7.3 Setting up our zoned multiswitch fabric. . . . . . . . . . . . . . . . . . . . . . 739
Chapter 7. Implementing the SAN Data Gateway . . . . . . . . . . . . . . . . . . . 749
7.1 SAN Data Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 750
7.2 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 751
7.2.1 Setting the Ethernet address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753
7.2.2 Using Telnet on the SAN Data Gateway . . . . . . . . . . . . . . . . . . . . . 753
7.2.3 Startup sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 754
7.3 StorWatch SAN Data Gateway Specialist . . . . . . . . . . . . . . . . . . . . . 755
7.3.1 Installing StorWatch Specialist . . . . . . . . . . . . . . . . . . . . . . . . . . . . 756
xii
IBM SAN Implementation
7.3.2 Using the StorWatch SAN Data Gateway Specialist. . . . . . . . . . . . 758
7.3.3 Upgrading the firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 766
7.4 SCSI devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 772
7.4.1 LUN support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 772
7.4.2 Device discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 772
7.4.3 Assigning LUN IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 773
7.4.4 Adding SCSI devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 773
7.5 SAN Data Gateway access options . . . . . . . . . . . . . . . . . . . . . . . . . 774
7.5.1 Zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 774
7.5.2 Virtual Private SAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775
7.5.3 Combining Zoning and Virtual Private SAN . . . . . . . . . . . . . . . . . . 784
7.6 Adding Fibre Channel fabric components . . . . . . . . . . . . . . . . . . . . . 785
7.6.1 Connecting an IBM SAN Fibre Channel Switch . . . . . . . . . . . . . . . 785
7.6.2 Connecting a McDATA Enterprise Fibre Channel Director . . . . . . . 795
7.7 High availability considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 796
7.7.1 Single host with multiple Fibre Channel adapters . . . . . . . . . . . . . . 797
7.7.2 Multiple SCSI connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 797
7.7.3 Adding Fibre Channel switches. . . . . . . . . . . . . . . . . . . . . . . . . . . . 798
Chapter 8. Implementing the Vicom Fibre Channel SLIC Router . . . . . . 799
8.1 SLIC Router features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 800
8.2 Installing the SLIC Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 801
8.3 SLIC Manager software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 804
8.3.1 Installing the SLIC Manager software . . . . . . . . . . . . . . . . . . . . . . . 805
8.3.2 Communicating to the Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 805
8.3.3 Starting the SLIC Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 810
8.4 Using SLIC Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 811
8.4.1 Drive properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 812
8.4.2 Router properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 812
8.4.3 Setting Router to master . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 813
8.4.4 The SignOn drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 814
8.5 Composite drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 815
8.5.1 Creating a composite drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 815
8.5.2 Composite drive properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 819
8.6 Mirror drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 820
8.6.1 Creating a mirror drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 821
8.6.2 Mirror drive properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 824
8.7 Instant Copy drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 825
8.7.1 Creating an Instant Copy drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . 826
8.7.2 Instant copy drive properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 827
8.7.3 Adding an Instant Copy Drive to a mirror . . . . . . . . . . . . . . . . . . . . 828
8.7.4 Detach Instant Copy Drive from a mirror. . . . . . . . . . . . . . . . . . . . . 830
8.8 Combining composite and mirroring . . . . . . . . . . . . . . . . . . . . . . . . . 830
Contents
xiii
8.8.1 Creating a second composite drive . . . . . . . . . . . . . . . . . . . . . . . . . 831
8.8.2 Creating the mirror . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 833
8.8.3 Viewing mirror drive using composite drives . . . . . . . . . . . . . . . . . . 834
8.9 Reusing logical drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 835
8.9.1 Remove a logical drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 835
8.9.2 Mapping a general spare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 837
8.9.3 Removing a mirror containing composite drive . . . . . . . . . . . . . . . . 837
8.10 Expanding the SLIC system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 839
8.10.1 Adding disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 839
8.10.2 Adding Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 839
8.10.3 Adding hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 842
Related publications . . . . . . . . . . . . . . . . . . . . . .
IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Other resources . . . . . . . . . . . . . . . . . . . . . . . .
Referenced Web sites . . . . . . . . . . . . . . . . . . . . . .
How to get IBM Redbooks . . . . . . . . . . . . . . . . . . .
IBM Redbooks collections . . . . . . . . . . . . . . . . .
......
......
......
......
......
......
.......
.......
.......
.......
.......
.......
......
......
......
......
......
......
.
.
.
.
.
.
843
843
843
846
847
848
Special notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 849
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 851
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 863
xiv
IBM SAN Implementation
Figures
2-1
2-2
2-3
2-4
2-5
2-6
2-7
2-8
2-9
2-10
2-11
2-12
2-13
2-14
2-15
2-16
2-17
2-18
2-19
2-20
2-21
2-22
2-23
2-24
2-25
2-26
2-27
2-28
2-29
2-30
2-31
2-32
2-33
2-34
2-35
2-36
2-37
2-38
© Copyright IBM Corp. 2001
Enterprise Storage Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Introduction panel of the ESS specialist . . . . . . . . . . . . . . . . . . . . . . . . 78
New Site Certificate, start window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
New Site Certificate, information window. . . . . . . . . . . . . . . . . . . . . . . . 80
New Site Certificate, More Info window . . . . . . . . . . . . . . . . . . . . . . . . . 80
New Site Certificate, Accepting the certificate . . . . . . . . . . . . . . . . . . . . 81
Site login window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Status — Graphical View panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Status — Problem Log panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Problem Notification panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Communications panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Remote Support Modification panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Licensed Internal Code panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Storage Allocation — Graphical View panel . . . . . . . . . . . . . . . . . . . . . 89
Loading copy services server applets . . . . . . . . . . . . . . . . . . . . . . . . . . 90
ESS Web Copy Services introduction panel . . . . . . . . . . . . . . . . . . . . . 91
Tools help page, Web Copy Services trouble shooting . . . . . . . . . . . . . 92
Tools help page, Web Copy Services trouble shooting, continued . . . . 93
User Administration panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Modify Users panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Graphical View, unconfigured ESS with ESCON, SCSI and FC . . . . . . 96
Host interfaces row, without any configured host interface . . . . . . . . . . 97
Open systems host port icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Installed ESS interfaces row . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
ESS ESCON adapter with two ports . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
ESS SCSI adapter with two ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
ESS FC adapter with one port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
FC host port selected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
SCSI host port selected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
SSA device adapters without any disk group configured . . . . . . . . . . . 101
Disk groups, view all storage mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Disk groups, storage assigned to selected host FC port . . . . . . . . . . . 102
Legend of the disk group status colors . . . . . . . . . . . . . . . . . . . . . . . . 103
Tabular View, no ESS logical volumes configured . . . . . . . . . . . . . . . 104
Entry for open systems storage configurations . . . . . . . . . . . . . . . . . . 104
Open System Storage panel, no host FC ports defined . . . . . . . . . . . 105
ESS configuration dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Fixed Block Storage panel, no disk groups configured . . . . . . . . . . . . 108
xv
2-39
2-40
2-41
2-42
2-43
2-44
2-45
2-46
2-47
2-48
2-49
2-50
2-51
2-52
2-53
2-54
2-55
2-56
2-57
2-58
2-59
2-60
2-61
2-62
2-63
2-64
2-65
2-66
2-67
2-68
2-69
2-70
2-71
2-72
2-73
2-74
2-75
2-76
2-77
2-78
2-79
2-80
xvi
Open systems storage types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Disk groups defined for RAID 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Warning window, time consuming action . . . . . . . . . . . . . . . . . . . . . . . 110
Progress window, RAID configuration . . . . . . . . . . . . . . . . . . . . . . . . . 111
Status window, successful disk group configuration . . . . . . . . . . . . . . 111
Disk group section, configured disk group selected. . . . . . . . . . . . . . . 112
Information window, for RAID 5 configured disk group . . . . . . . . . . . . 113
Two disk groups configured, two defined and two undefined . . . . . . . 114
Four disk groups configured . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Status — Graphical View, four disk groups in the process of formatting . .
116
Entry to the Modify Hosts Systems panel . . . . . . . . . . . . . . . . . . . . . . 117
Modify Host Systems panel, no host FC ports defined . . . . . . . . . . . . 117
Host Attributes frame, host type selection . . . . . . . . . . . . . . . . . . . . . . 118
Host Attributes frame, host interface type selection. . . . . . . . . . . . . . . 119
Host Systems List, host FC ports defined . . . . . . . . . . . . . . . . . . . . . . 120
Performing the port definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Successfully added host FC port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Fibre Channel host adapter port; no volume assigned . . . . . . . . . . . . 121
Four disk groups, two host FC ports . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Information window, host FC port in PC server . . . . . . . . . . . . . . . . . . 122
Selected host FC port, no ESS FC port restrictions. . . . . . . . . . . . . . . 123
FC port PC1_2 selected for modification . . . . . . . . . . . . . . . . . . . . . . . 124
All installed ESS FC ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Host Systems List with restricted host FC port PC1_2 . . . . . . . . . . . . 125
Selected host FC port, restricted to one ESS FC port . . . . . . . . . . . . . 126
Entry to the Add Volumes (1 of 2) panel . . . . . . . . . . . . . . . . . . . . . . . 126
Add Volumes (1 of 2) panel with host FC port PC1_1 selected . . . . . . 127
host FC port and the ESS FC port selected. . . . . . . . . . . . . . . . . . . . . 127
Add Volumes (1 of 2) panel with disk group status shown . . . . . . . . . 128
One disk group selected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Add Volumes (2 of 2) panel, two RAID 5 disk groups to be used . . . . 129
Available Free Space frame, RAID-5 storage entry selected . . . . . . . 130
Volume Attributes frame, ESS logical volume size of 16.2 GB selected130
Volume Attributes frame, ESS logical volume size of 16.1 GB selected131
New Volumes frame, two volumes selected to be removed from frame131
Volume Placement frame, spreading volumes selected . . . . . . . . . . . 132
Add Volumes (2 of 2) panel, ready to perform the configuration update133
Warning window, time consuming action . . . . . . . . . . . . . . . . . . . . . . . 133
Progress window, volume creation . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Information window, successful volume creation . . . . . . . . . . . . . . . . . 134
Host FC port selected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Host FC port and ESS FC port selected . . . . . . . . . . . . . . . . . . . . . . . 136
IBM SAN Implementation
2-81
2-82
2-83
2-84
2-85
2-86
2-87
2-88
2-89
2-90
2-91
2-92
2-93
2-94
2-95
2-96
2-97
2-98
2-99
2-100
2-101
2-102
2-103
2-104
2-105
2-106
2-107
2-108
2-109
2-110
2-111
2-112
2-113
2-114
2-115
2-116
2-117
2-118
2-119
2-120
2-121
2-122
2-123
Information frame, host FC port, and disk group selected . . . . . . . . . . 136
Disk group selected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Information frame, disk group selected . . . . . . . . . . . . . . . . . . . . . . . . 138
FC port PC1_1 with two assigned volumes . . . . . . . . . . . . . . . . . . . . . 139
View All Storage mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Host FC port and ESS FC port selected . . . . . . . . . . . . . . . . . . . . . . . 141
Displays of all four volume assignments . . . . . . . . . . . . . . . . . . . . . . . 142
Entry point for modifying volume assignments . . . . . . . . . . . . . . . . . . 143
Four volume assignments, one for each existing volume . . . . . . . . . . 143
Two selected volume assignments, Action field accessible. . . . . . . . . 144
Adding assignments to other available host FC ports selected . . . . . . 145
Progress window, creating volume assignments . . . . . . . . . . . . . . . . . 146
Volume assignments successfully created for specified host FC ports 146
Assignments for the host FC port PC1_1 . . . . . . . . . . . . . . . . . . . . . . 147
PC1_1 and ESS FC port selected . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Disk group containing shared ESS logical volume(s) selected . . . . . . 149
Tabular View, two volumes shared, two not shared . . . . . . . . . . . . . . 150
Information window, opening another browser window. . . . . . . . . . . . 150
HTML file, List of Assigned Volumes table, list of existing assignments151
Entry point for modifying volume assignments . . . . . . . . . . . . . . . . . . 151
Removing volume assignments from both host FC ports. . . . . . . . . . . 152
Warning window one, volumes to be isolated from host FC ports . . . . 152
Warning window two, volumes to be isolated from host FC ports . . . . 153
Progress window, applying assignment changes . . . . . . . . . . . . . . . . 153
Information window, volume assignments successfully removed . . . . 153
Placeholder for unassigned ESS logical volume selected . . . . . . . . . . 154
Open System Storage panel, only one volume assigned to PC1_2 . . 154
No volume assignment to PC1_1 in disk group 2 of cluster 1 loop B . 155
No volume assignment to PC1_2 in disk group 2 of cluster 1 loop B . 155
Unassigned volume(s) in disk group 2 of cluster 1 loop B . . . . . . . . . . 156
Disk group selected, unassigned volume(s) in selected disk group . . 157
Tabular View, four volume assignments, three volumes . . . . . . . . . . . 158
Information frame, ESS FC port topology undefined . . . . . . . . . . . . . . 159
Entry point for configuring ESS FC ports . . . . . . . . . . . . . . . . . . . . . . . 159
Configure Host Adapter Ports panel, ESCON port selected . . . . . . . . 160
Port selection drop down list, SCSI port selected . . . . . . . . . . . . . . . . 161
Configure Host Adapter Ports panel, FC port selected . . . . . . . . . . . . 162
Storage Server Attributes field, ESS configured for Access_Restricted162
Anonymous host FC port icon in an ESS configured for Access_Any . 163
Pattern for the generation of the WWPNs of the ESS FC ports. . . . . . 165
Information Frame, reflecting the new locally administered WWPN . . 166
WWNN of the ESS with locally administered WWPNs . . . . . . . . . . . . 166
Pull down list, selected port currently undefined . . . . . . . . . . . . . . . . . 167
Figures
xvii
2-124
2-125
2-126
2-127
2-128
2-129
2-130
2-131
3-1
3-2
3-3
3-4
3-5
3-6
3-7
3-8
3-9
3-10
3-11
3-12
3-13
3-14
3-15
3-16
3-17
3-18
3-19
3-20
3-21
3-22
3-23
3-24
3-25
3-26
3-27
3-28
3-29
3-30
3-31
3-32
3-33
3-34
3-35
xviii
ESS FC port for Point to Point defined . . . . . . . . . . . . . . . . . . . . . . . . 168
ESS FC port for Arbitrated Loop defined . . . . . . . . . . . . . . . . . . . . . . . 169
Warning window, configuration changes are going to be discarded . . 169
Progress window, changing the topology . . . . . . . . . . . . . . . . . . . . . . 170
Information window, successful topology change . . . . . . . . . . . . . . . . 170
Information frame, ESS FC port topology Point to Point . . . . . . . . . . . 171
Information frame, ESS FC port topology Arbitrated Loop . . . . . . . . . 171
Storage allocation now completed . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
IBM Fibre Channel Storage Hub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Gigabit Interface Converter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
FC Storage Hub 2103-H07 front panel . . . . . . . . . . . . . . . . . . . . . . . . 178
Insert cable into GBIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
IBM TotalStorage SAN Managed Hub . . . . . . . . . . . . . . . . . . . . . . . . . 179
IBM TotalStorage SAN Hub faceplate . . . . . . . . . . . . . . . . . . . . . . . . . 180
IBM TotalStorage SAN Hub management ports . . . . . . . . . . . . . . . . . 183
Telnet logon screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Checking the IP address of the Managed Hub . . . . . . . . . . . . . . . . . . 185
Changing the IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
HyperTerm COM1 properties window . . . . . . . . . . . . . . . . . . . . . . . . . 187
HyperTerm File Properties screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Download the latest firmware levels . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Download the latest version of the RSHD and CAT utilities . . . . . . . . 191
Telnet to the Managed Hub using a DOS window . . . . . . . . . . . . . . . . 191
Logon to the Managed Hub via Telnet . . . . . . . . . . . . . . . . . . . . . . . . . 192
Starting the RSH daemon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Confirm the RSH daemon is running . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Issuing the Firmwaredownload command . . . . . . . . . . . . . . . . . . . . . . 193
Re-booting the Managed Hub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Launch the Admin View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Switch Admin screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Firmware Upgrade screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Upgrading the Firmware using the Managed Hub Specialist . . . . . . . . 197
Firmware download message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Fastboot the Managed Hub after downloading the firmware . . . . . . . . 198
Reboot in progress message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Firmware revision level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Arbitrated Loop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Private Loop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Public loop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
QuickLoop using managed hub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
QuickLoop spanning to switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
ITSO SAN fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Launch Admin View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
IBM SAN Implementation
3-36
3-37
3-38
3-39
3-40
3-41
3-42
3-43
3-44
3-45
3-46
3-47
3-48
3-49
3-50
3-51
3-52
3-53
3-54
3-55
3-56
3-57
3-58
3-59
3-60
3-61
3-62
3-63
3-64
3-65
3-66
3-67
3-68
3-69
3-70
3-71
3-72
3-73
3-74
3-75
3-76
3-77
3-78
QuickLoop Admin screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Selecting a QuickLoop partner. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
QuickLoop partner established . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Fabric View showing the Managed Hub in the bottom right hand side 209
Launch the Managed Hub Specialist . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Switch Management view for the Managed Hub . . . . . . . . . . . . . . . . . 210
Launch the Events screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Events Log for the Managed Hub . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Start Beaconing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Start Telnet session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Telnet session for the Managed Hub . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Go to the Performance report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Performance Report for the Managed Hub . . . . . . . . . . . . . . . . . . . . . 214
Go to the Admin View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Switch Admin screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
User Admin screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Firmware Upgrade screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Rebooting the Managed Hub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
SNMP Admin screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
License Admin screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
QuickLoopAdmin screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Config Admin screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Go to Switch Information Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
Managed Hub Information Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Go to Port Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Port Information screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Go to Port Information for Port_7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Port Information for Port_7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Go to Fabric Topology to check status of the Managed Hub . . . . . . . . 228
Fabric Topology showing the details for the Managed Hub . . . . . . . . . 229
Go to the Name Server table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
Name Server Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
Displaying the device attached to the Managed Hub. . . . . . . . . . . . . . 232
Go to Zone Admin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Zone Admin screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Zone Admin display of existing Aliases . . . . . . . . . . . . . . . . . . . . . . . . 236
Go to Zone Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
Create Zone for Managed Hub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Save Zone name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Add Port_0 to Zone for Managed Hub . . . . . . . . . . . . . . . . . . . . . . . . . 240
Add Port_1 to Managed Hub zone. . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
Add Port_2 to Managed Hub zone. . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Apply the new zone configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Figures
xix
3-79
3-80
3-81
3-82
3-83
3-84
3-85
3-86
4-1
4-2
4-3
4-4
4-5
4-6
4-7
4-8
4-9
4-10
4-11
4-12
4-13
4-14
4-15
4-16
4-17
4-18
4-19
4-20
4-21
4-22
4-23
4-24
4-25
4-26
4-27
4-28
4-29
4-30
4-31
4-32
4-33
4-34
4-35
xx
Go to Zone Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
Add Managed Hub zone to the Primary Configuration . . . . . . . . . . . . 245
Apply the changes to the fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Exit the Config Settings screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Back to Fabric View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
Go to Events Log for the Managed Hub . . . . . . . . . . . . . . . . . . . . . . . 248
Go to Admin View for the Managed Hub . . . . . . . . . . . . . . . . . . . . . . . 249
Go to Telnet for the Managed Hub . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
The IBM TotalStorage SAN Switch (2108-S08) . . . . . . . . . . . . . . . . . . 252
IBM TotalStorage SAN Switch (2109-S16) . . . . . . . . . . . . . . . . . . . . . 252
SAN Fibre Channel Switch, 2109-S08 Ethernet and serial connectors 253
2109-S08 front panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
IBM TotalStorage SAN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
2109-S16 display panel and controls . . . . . . . . . . . . . . . . . . . . . . . . . . 254
RJ-45 Ethernet Connector and Serial Port Connector . . . . . . . . . . . . . 263
Setting Ethernet IP addresses for the 2109-S08 . . . . . . . . . . . . . . . . . 264
Setting the Ethernet IP addresses for the 2109-S16 . . . . . . . . . . . . . . 265
Running the Remote Shell Daemon (RSH) . . . . . . . . . . . . . . . . . . . . . 269
Displaying Hostname and IP configuration details. . . . . . . . . . . . . . . . 270
Establish a Telnet session with the switch . . . . . . . . . . . . . . . . . . . . . . 270
Fabric OS and Telnet login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
Upgrading the switch firmware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
Rebooting the switch from a Telnet session . . . . . . . . . . . . . . . . . . . . 272
Go to Switch Admin screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
Switch Admin screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
Firmware Upgrade screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Reboot Switch message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Reboot Switch using Fastboot option . . . . . . . . . . . . . . . . . . . . . . . . . 276
Reboot in progress message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
RSH Daemon message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
Switch View showing new firmware level. . . . . . . . . . . . . . . . . . . . . . . 277
IBM StorWatch Switch Specialist — Fabric View . . . . . . . . . . . . . . . . 279
Fabric View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
Single Switch View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
Go to Switch Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
Switch Event log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
Go to Admin View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
Admin View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
User Admin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
Adding Users / Modify existing users . . . . . . . . . . . . . . . . . . . . . . . . . . 285
SysAdmin Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
Firmware Upgrade using the Switch Specialist . . . . . . . . . . . . . . . . . . 286
Reboot Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
IBM SAN Implementation
4-36
4-37
4-38
4-39
4-40
4-41
4-42
4-43
4-44
4-45
4-46
4-47
4-48
4-49
4-50
4-51
4-52
4-53
4-54
4-55
4-56
4-57
4-58
4-59
4-60
4-61
4-62
4-63
4-64
4-65
4-66
4-67
4-68
4-69
4-70
4-71
4-72
4-73
4-74
4-75
4-76
4-77
4-78
SNMP Admin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
License Admin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
Config Admin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
Go to Switch Information Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
Switch Information Report — Page 1. . . . . . . . . . . . . . . . . . . . . . . . . . 291
Switch Information Report — Page 2. . . . . . . . . . . . . . . . . . . . . . . . . . 292
Switch Information Report — Page 3. . . . . . . . . . . . . . . . . . . . . . . . . . 293
Switch Information Report — Page 4. . . . . . . . . . . . . . . . . . . . . . . . . . 294
Switch Information Report — Page 5. . . . . . . . . . . . . . . . . . . . . . . . . . 295
Switch Information Report — Page 6. . . . . . . . . . . . . . . . . . . . . . . . . . 295
Extended Fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
Go to Telnet session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
Telnet session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
Go to Switch View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
Switch View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
Go to Port Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
Port Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
Go to Performance Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
Performance Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
Start Beaconing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
Go to Fabric Watch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
Fabric Watch — Environment Temperature details . . . . . . . . . . . . . . . 306
Fabric Watch — Environment Boundaries screen . . . . . . . . . . . . . . . . 307
Changing the Fabric Watch boundaries for Temperature . . . . . . . . . . 308
Switch View showing temperature status . . . . . . . . . . . . . . . . . . . . . . 308
View of switch after exceeding the temperature threshold . . . . . . . . . 309
Fabric Watch — Environment Alarms Config screen. . . . . . . . . . . . . . 310
Fabric Watch — GBIC details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
Fabric Watch — Port details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
Fabric Watch — Fabric details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
Fabric Watch — E_port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
Fabric Watch — F/FL (Optical Port). . . . . . . . . . . . . . . . . . . . . . . . . . . 315
Switches with a “marginal” status . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
Changing the default setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
Three green switches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
Fabric wide options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
Go to Fabric Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
Go to Fabric Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
Fabric Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
Go to Name Server table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
Name Server table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
Go to Zone Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
Figures
xxi
4-79
4-80
4-81
4-82
4-83
4-84
4-85
4-86
4-87
4-88
4-89
4-90
4-91
4-92
4-93
4-94
4-95
4-96
4-97
4-98
4-99
4-100
4-101
4-102
4-103
4-104
4-105
4-106
4-107
4-108
4-109
4-110
4-111
4-112
4-113
4-114
4-115
4-116
4-117
4-118
4-119
4-120
4-121
xxii
Zone Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
Go to Summary View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
Fabric View — Summary View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
Go back to Detail View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
Fabric View — Detailed View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
A fabric consisting of three zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
Zone Admin — Zone Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
Zone Admin — create a zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
Creating a Zone Name — Solaris_sole_zone . . . . . . . . . . . . . . . . . . . 342
Adding a member to a zone. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
Zone Settings display after adding a member . . . . . . . . . . . . . . . . . . . 344
Adding another member to the Zone . . . . . . . . . . . . . . . . . . . . . . . . . . 345
Apply changes to Zone Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
Exit Zone Admin panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
A fault tolerant fabric with 6 switches . . . . . . . . . . . . . . . . . . . . . . . . . . 349
A fault tolerant fabric with four switches. . . . . . . . . . . . . . . . . . . . . . . . 349
Switch view of itsosw2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351
Switch view after cascading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351
Cascaded switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
Second cable plugged into switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
Zone Admin — displaying a cascaded switch . . . . . . . . . . . . . . . . . . . 353
Zone Settings — modifying zones across a cascaded fabric . . . . . . . 354
Zoning — across cascaded switches. . . . . . . . . . . . . . . . . . . . . . . . . . 355
Apply changes — applying changes across a cascaded fabric . . . . . . 356
Exiting Zone settings screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
Accessing Fabric Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
Zone Topology — after cascading switches . . . . . . . . . . . . . . . . . . . . 359
Fabric View — navigating to Zone Admin . . . . . . . . . . . . . . . . . . . . . . 360
Creating aliases screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
Create Alias — save name as MSS1. . . . . . . . . . . . . . . . . . . . . . . . . . 361
Creating an alias — based on port number . . . . . . . . . . . . . . . . . . . . . 362
Adding a second port number to an alias . . . . . . . . . . . . . . . . . . . . . . 363
Applying changes to the alias settings . . . . . . . . . . . . . . . . . . . . . . . . . 364
Switch view for ITSOSW1 after adding additional a cables . . . . . . . . . 365
Switch View of ITSOSW2 after adding additional cables. . . . . . . . . . . 365
Creating another new zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
Creating a Zone — for NT general purpose servers . . . . . . . . . . . . . . 366
Adding Port 4 to the NT zone. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
Adding Port 3 to NT zone. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
Adding Port 4 from the second switch to the NT zone . . . . . . . . . . . . . 369
Add an existing alias to the NT zone . . . . . . . . . . . . . . . . . . . . . . . . . . 370
Applying the changes to the NT zone . . . . . . . . . . . . . . . . . . . . . . . . . 371
Creating a zone for our Windows 2000 cluster . . . . . . . . . . . . . . . . . . 372
IBM SAN Implementation
4-122
4-123
4-124
4-125
4-126
4-127
4-128
4-129
4-130
4-131
4-132
4-133
4-134
4-135
4-136
4-137
4-138
4-139
4-140
4-141
4-142
4-143
4-144
4-145
4-146
4-147
4-148
4-149
4-150
4-151
4-152
4-153
4-154
4-155
4-156
4-157
4-158
4-159
4-160
4-161
4-162
4-163
4-164
Zone name for our Windows 2000 cluster . . . . . . . . . . . . . . . . . . . . . . 372
WWPN display for attached devices . . . . . . . . . . . . . . . . . . . . . . . . . . 373
Using the Name Server display to find a specific WWPN . . . . . . . . . . 374
Launching the Switch View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
Switch View of ITSOSW1 indicating a possible problem with port 2 . . 375
Check Name Server display after fixing Port_2 . . . . . . . . . . . . . . . . . . 375
Zone Settings and the WWPN list for attached devices . . . . . . . . . . . 376
Select another WWPN to add to the zone configuration . . . . . . . . . . . 377
Creating a zone consisting of WWPNs and Port number . . . . . . . . . . 378
Display the zone settings for the W2K zone and apply changes . . . . . 379
Configuring ITSOSW3 into the SAN fabric . . . . . . . . . . . . . . . . . . . . . 380
Switched Fabric with three switches . . . . . . . . . . . . . . . . . . . . . . . . . . 380
Refreshing the Name Server Table . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
Switch View after cabling ITSOSW3 . . . . . . . . . . . . . . . . . . . . . . . . . . 382
Port Information for Port_2 on ITSOSW3 . . . . . . . . . . . . . . . . . . . . . . 383
Creating an alias based on WWPN . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
Create alias called Bonnie . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
Adding a member based on WWPN . . . . . . . . . . . . . . . . . . . . . . . . . . 385
Display the aliases created . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386
Go to Zone Admin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
Go to Zone Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
Adding the alias Bonnie to our AIX zone definition . . . . . . . . . . . . . . . 389
Apply the configuration to the AIX zone . . . . . . . . . . . . . . . . . . . . . . . . 390
Go to Zone Admin function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
Select Config Settings tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
Create a switch configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
Save Configuration name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
Add AIX zone to our Primary Configuration (Primary_config) . . . . . . . 394
Apply and enable the Primary_config setting to the switch . . . . . . . . . 395
Config currently enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396
Two separate SAN fabrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
A merged fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
Fabric View of Fabric_1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
Fabric View of Fabric_2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
Switch View of ITSOSW3 showing segmented port . . . . . . . . . . . . . . 401
Go to Switch Event log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
Switch Event log for ITSOSW3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402
Go to Fabric Event log for Fabric_1 . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
Fabric Event log for Fabric_1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
Widen Message column. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
Domain ID conflict . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
Go to the Switch View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405
Go to the Admin functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405
Figures
xxiii
4-165
4-166
4-167
4-168
4-169
4-170
4-171
4-172
4-173
4-174
4-175
4-176
4-177
4-178
4-179
4-180
4-181
4-182
4-183
4-184
4-185
4-186
4-187
4-188
4-189
4-190
4-191
4-192
4-193
4-194
4-195
4-196
4-197
4-198
4-199
4-200
4-201
4-202
4-203
4-204
4-205
4-206
4-207
xxiv
Changing the Domain ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
Domain ID reset message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
Switch View after changing the Domain ID . . . . . . . . . . . . . . . . . . . . . 407
Successfully merged fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408
Fabric Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
Fabric Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
Zone Admin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412
Create an alias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
Save Alias Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
Creating an alias — Add Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414
Applying an alias with Host Names . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
Creating an alias using Add Member . . . . . . . . . . . . . . . . . . . . . . . . . . 416
Adding a Member to an Alias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416
Applying changes to an alias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
New alias definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418
Zone screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
QuickLoop screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
Fabric Assist screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
Config screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422
Switch View — go to Fabric View . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
Fabric Watch — Environment Alarm Notifications . . . . . . . . . . . . . . . . 423
Fabric Watch — Environmental Thresholds . . . . . . . . . . . . . . . . . . . . 424
Setting the Threshold types — In-Between . . . . . . . . . . . . . . . . . . . . . 425
Selecting the High and Low settings . . . . . . . . . . . . . . . . . . . . . . . . . . 426
Setting the High Threshold value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427
Setting the Low Threshold value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428
Alarm Mechanism screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428
Fabric Watch — Environment Current Settings . . . . . . . . . . . . . . . . . . 429
Setting Port Threshold values — Link Loss . . . . . . . . . . . . . . . . . . . . . 430
Setting Port Threshold values — State Changes . . . . . . . . . . . . . . . . 431
Fabric Watch — GBIC Alarm Notifications . . . . . . . . . . . . . . . . . . . . . 432
Fabric Watch — GBC Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
Fabric Watch — GBIC Current Settings . . . . . . . . . . . . . . . . . . . . . . . 434
Monitoring the Fabric — Alarm Notification . . . . . . . . . . . . . . . . . . . . . 435
Monitoring the Fabric — Setting Fabric Thresholds. . . . . . . . . . . . . . . 436
Monitoring the Fabric — Current Settings . . . . . . . . . . . . . . . . . . . . . . 437
Switch Admin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438
Disabling a switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439
Disabled Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440
Disabled switch message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440
Restarting a disabled switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
Switch enabled message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
2109-F16 switch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443
IBM SAN Implementation
4-208
4-209
4-210
4-211
4-212
4-213
4-214
4-215
4-216
4-217
4-218
4-219
4-220
4-221
4-222
4-223
4-224
4-225
4-226
4-227
4-228
4-229
4-230
4-231
4-232
4-233
4-234
4-235
4-236
4-237
4-238
4-239
4-240
4-241
4-242
4-243
4-244
4-245
4-246
4-247
4-248
4-249
4-250
Initial Switch View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470
Network password entry scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470
Zoning scheme selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471
Zone admin initial view. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472
Port Alias administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473
Port zone selection and display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475
QuickLoop screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
Port Config screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479
Analyze config selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481
Selecting WWN level zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482
WWN Alias screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483
WWN Zone screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485
QuickLoop screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487
WWN Config screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489
AL_PA Level zoning select . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491
Device Alias screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492
AL_PA device zone screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494
QuickLoop config screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496
AL_PA device config scree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498
Mixed level zoning selection window . . . . . . . . . . . . . . . . . . . . . . . . . . 500
Mixed zoning alias screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501
Mixed zoning zone screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503
Mixed level QuickLoop screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505
Mixed level config screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507
Switch management screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514
Actions menu displaying choices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515
Performance graphs menu showing choices . . . . . . . . . . . . . . . . . . . . 516
Basic monitoring full functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516
Canvas save screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517
Display resource usage screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517
Display resource screen output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518
Advanced monitoring options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522
Advanced monitoring range of options . . . . . . . . . . . . . . . . . . . . . . . . 524
SID/DID performance setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525
SCSI read/write LUN per port setup . . . . . . . . . . . . . . . . . . . . . . . . . . 526
SCSI read/write per port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526
Performance monitor canvas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527
Canvas options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528
Switch admin selection screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529
Switch settings screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530
Network config screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532
Firmware upgrade screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534
SNMP screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536
Figures
xxv
4-251
4-252
4-253
4-254
4-255
4-256
4-257
4-258
4-259
4-260
5-1
5-2
5-3
5-4
5-5
5-6
5-7
5-8
5-9
5-10
5-11
5-12
5-13
5-14
5-15
5-16
5-17
5-18
5-19
5-20
5-21
5-22
5-23
5-24
5-25
5-26
5-27
5-28
5-29
5-30
5-31
5-32
5-33
xxvi
License Administration screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538
Switch report information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540
Port settings screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
User admin screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543
Configure screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545
Routing screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548
Trunk information screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 550
QuickLoop screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551
Remote switch screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553
Extended fabrics screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555
front view of an INRANGE FC/9000 director . . . . . . . . . . . . . . . . . . . . 568
Example of IN-VSN management view . . . . . . . . . . . . . . . . . . . . . . . . 571
Initial INRANGE environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574
Private IP network for initial IN-VSN management ability . . . . . . . . . . 576
INRANGE setup attached to a corporate network . . . . . . . . . . . . . . . . 577
INRANGE setup with secure director access . . . . . . . . . . . . . . . . . . . 578
Running the IN-VSN setup: Initial screen . . . . . . . . . . . . . . . . . . . . . . 580
Running the IN-VSN setup: Java VM search . . . . . . . . . . . . . . . . . . . . 581
Running the IN-VSN setup: Feature selection . . . . . . . . . . . . . . . . . . . 582
Running the IN-VSN setup: Verifying all packages to install . . . . . . . . 583
Running obdc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584
Final IN-VSN software setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 585
IN-VSN server up and running . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586
Starting an IN-VSN client session . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587
Initial screen of an IN-VSN client session . . . . . . . . . . . . . . . . . . . . . . 588
Adding an IN-VSN user: Re-enter password . . . . . . . . . . . . . . . . . . . . 590
Adding an IN-VSN user: Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . 591
Adding an IN-VSN user: Creating an admin user . . . . . . . . . . . . . . . . 592
Adding an IN-VSN user: Saving new user configuration . . . . . . . . . . . 593
Deleting an IN-VSN user: Confirmation . . . . . . . . . . . . . . . . . . . . . . . . 594
Deleting an IN-VSN user: Updated user list. . . . . . . . . . . . . . . . . . . . . 595
Change attributes of an existing IN-VSN user . . . . . . . . . . . . . . . . . . . 596
Manual backup of IN-VSN server: Step 1 . . . . . . . . . . . . . . . . . . . . . . 600
Manual backup of IN-VSN server: Choosing the filename. . . . . . . . . . 600
AutoBackUp settings: Step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601
AutoBackUp settings: Enabling AutoBackUp. . . . . . . . . . . . . . . . . . . . 601
AutoBackUp settings: Specifying Filename and backup interval . . . . . 602
Inventory Update Call parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 602
IN-VSN fabric tool without any fabric known to it . . . . . . . . . . . . . . . . . 603
IN-VSN: Connecting to a new fabric . . . . . . . . . . . . . . . . . . . . . . . . . . 604
IN-VSN: Initial fabric view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605
IN-VSN: Director view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 607
IN-VSN: Changing the directors name. . . . . . . . . . . . . . . . . . . . . . . . . 607
IBM SAN Implementation
5-34
5-35
5-36
5-37
5-38
5-39
5-40
5-41
5-42
5-43
5-44
5-45
5-46
5-47
5-48
5-49
5-50
5-51
5-52
5-53
5-54
5-55
5-56
5-57
5-58
5-59
5-60
5-61
5-62
5-63
5-64
5-65
5-66
5-67
5-68
5-69
5-70
5-71
5-72
5-73
5-74
5-75
5-76
IN-VSN: Director view with all ports . . . . . . . . . . . . . . . . . . . . . . . . . . . 608
IN-VSN: Changing port names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609
IN-VSN: Director’s updated port view . . . . . . . . . . . . . . . . . . . . . . . . . 610
IN-VSN: Selecting the director clock menu . . . . . . . . . . . . . . . . . . . . . 611
IN-VSN: Setting the director clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . 612
IN-VSN: Port View to enable port specific loop attachment . . . . . . . . . 614
IN-VSN: Confirming the enabling of loop attachment . . . . . . . . . . . . . 615
IN-VSN: FC adapter set to public loop . . . . . . . . . . . . . . . . . . . . . . . . . 615
IN-VSN: Port Loop Devices View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 616
IN-VSN: Enabling Auto Sense Arbitrated Loop for the entire director . 617
IN-VSN: Confirming loop enabling for the entire director . . . . . . . . . . . 617
IN-VSN: loop port in name server table as NL_Port . . . . . . . . . . . . . . 618
IN-VSN: Bypassing loop devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619
IN-VSN: Enabling and Disabling Loop devices . . . . . . . . . . . . . . . . . . 620
IN-VSN: Name server table with NL_Port . . . . . . . . . . . . . . . . . . . . . . 622
IN-VSN: Setting a port to Translative Loop mode . . . . . . . . . . . . . . . . 623
IN-VSN: Selecting target or initiator mode for TL ports . . . . . . . . . . . . 624
IN-VSN: adding possible targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 626
IN-VSN: Adding WWN targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 626
Translation Entries List with zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . 627
INRANGE hard zoning: fixed location of port groups. . . . . . . . . . . . . . 631
INRANGE hard zoning: basic example with 2 zones . . . . . . . . . . . . . . 632
Violating the adjoining rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633
INRANGE access enforcements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 636
INRANGE fabric scenario with hard zoning and name server zoning . 637
INRANGE hard zoning: Layout scenario . . . . . . . . . . . . . . . . . . . . . . . 638
IN-VSN: Selecting hard zoning in the director view . . . . . . . . . . . . . . . 639
IN-VSN: Specifying a name for a hard zone . . . . . . . . . . . . . . . . . . . . 640
IN-VSN: two ports assigned to a hard zone . . . . . . . . . . . . . . . . . . . . . 641
IN-VSN: Having two hard zones defined . . . . . . . . . . . . . . . . . . . . . . . 642
Violation of ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 643
IN-VSN: Applying a hard zone setup . . . . . . . . . . . . . . . . . . . . . . . . . . 644
Server setup for soft zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645
Physical cable connection for soft zoning setup . . . . . . . . . . . . . . . . . 646
Logical view of our two name server zones . . . . . . . . . . . . . . . . . . . . . 647
IN-VSN: Entering the zone screen in fabric view mode . . . . . . . . . . . . 648
IN-VSN: Entering number and name for a new zone. . . . . . . . . . . . . . 649
IN-VSN: Selecting the members of a new zone. . . . . . . . . . . . . . . . . . 650
IN-VSN: Accepting settings for first new zone . . . . . . . . . . . . . . . . . . . 651
IN-VSN: Zone number 0 is not allowed to use . . . . . . . . . . . . . . . . . . . 652
IN-VSN: Saving a newly added zone . . . . . . . . . . . . . . . . . . . . . . . . . . 653
IN-VSN: Zone list with both zones added and saved. . . . . . . . . . . . . . 654
IN-VSN: Director Port View showing the port to zone relationship . . . 655
Figures
xxvii
5-77
5-78
5-79
5-80
6-1
6-2
6-3
6-4
6-5
6-6
6-7
6-8
6-9
6-10
6-11
6-12
6-13
6-14
6-15
6-16
6-17
6-18
6-19
6-20
6-21
6-22
6-23
6-24
6-25
6-26
6-27
6-28
6-29
6-30
6-31
6-32
6-33
6-34
6-35
6-36
6-37
6-38
6-39
xxviii
One INRANGE fabric consisting of two cascaded directors . . . . . . . . 656
IN-VSN: Fabric view with two cascaded directors . . . . . . . . . . . . . . . . 657
IN-VSN: Using the INRANGE Audit-Trail to monitor user activities . . . 660
IN-VSN: Accessing the INRANGE event log . . . . . . . . . . . . . . . . . . . . 661
ED-6064 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 664
ED-5000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 666
ES-3032 and ES-3016 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 667
ES-1000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 668
Fabricenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669
Fabricenter with four ED-6064 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 670
McDATA network setup with ethernet hub part of the LAN . . . . . . . . . 672
Suggested McDATA network setup . . . . . . . . . . . . . . . . . . . . . . . . . . . 674
Web interface of the ED-6064, unit view . . . . . . . . . . . . . . . . . . . . . . . 675
Start page for remote EFC Manager client installation . . . . . . . . . . . . 677
Start page for remote EFC Manager client installation, continued. . . . 678
EFC Manager client installation, granting additional rights . . . . . . . . . 679
EFC Manager client installation, starting the installation . . . . . . . . . . . 680
EFC Manager client installation, EFC Manager version . . . . . . . . . . . 681
Logging in to the EFC Manager on the EFC Server . . . . . . . . . . . . . . 682
EFC Manager icon on remote workstation. . . . . . . . . . . . . . . . . . . . . . 683
Remote login in to the EFC Manager. . . . . . . . . . . . . . . . . . . . . . . . . . 683
EFC Manager, Product View, no switches defined . . . . . . . . . . . . . . . 684
EFC Manager, Product View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685
EFC Manager, Configure Users, New User . . . . . . . . . . . . . . . . . . . . . 686
EFC Manager, Configuring Users, Modify User. . . . . . . . . . . . . . . . . . 687
EFC Manager, Product View, no switches defined . . . . . . . . . . . . . . . 688
EFC Manager, New Product... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 689
Defining new ED-6064 with its IP address. . . . . . . . . . . . . . . . . . . . . . 689
EFC Manager, Product View, new ED-6064 icon . . . . . . . . . . . . . . . . 690
EFC Manager, Configure Nicknames, Add Nickname . . . . . . . . . . . . . 691
EFC Manager, Configure Nicknames, nicknames assigned . . . . . . . . 692
Product Manager ED-6064, Hardware View . . . . . . . . . . . . . . . . . . . . 693
Product Manager ED-6064 port card view and properties . . . . . . . . . . 694
ED-6064 port card viewing and configuration options . . . . . . . . . . . . . 695
Product Manager ED-6064 back to hardware view . . . . . . . . . . . . . . . 696
Product Manager ED-6064 Configure Identification . . . . . . . . . . . . . . 696
ED-6064 Hardware View changed director information . . . . . . . . . . . . 697
Product Manager ED-6064 Configure Operating Mode . . . . . . . . . . . . 697
Product Manager ED-6064 Configure Operating Mode Open Fabric . 698
Product Manager ED-6064 Configure Ports . . . . . . . . . . . . . . . . . . . . 699
Product Manager ED-6064 Configure Ports port type . . . . . . . . . . . . . 700
Product Manager ED-6064 Link Incident Log . . . . . . . . . . . . . . . . . . . 700
Product Manager ED-6064, Port List View Port Properties . . . . . . . . . 701
IBM SAN Implementation
6-40
6-41
6-42
6-43
6-44
6-45
6-46
6-47
6-48
6-49
6-50
6-51
6-52
6-53
6-54
6-55
6-56
6-57
6-58
6-59
6-60
6-61
6-62
6-63
6-64
6-65
6-66
6-67
6-68
6-69
6-70
6-71
6-72
6-73
6-74
6-75
6-76
6-77
6-78
6-79
6-80
6-81
6-82
Product Manager ED-6064 Set Online State . . . . . . . . . . . . . . . . . . . . 701
Product Manager ED-6064 Configure Operating Parameters . . . . . . . 702
Product Manager ED-5000 Hardware View . . . . . . . . . . . . . . . . . . . . . 703
Product Manager ED-5000, Port Card View Port Properties . . . . . . . . 704
Product Manager ES-3016 Hardware View . . . . . . . . . . . . . . . . . . . . . 705
Product Manager ES-1000 Hardware View . . . . . . . . . . . . . . . . . . . . . 706
Product Manager ES-1000 Hardware View failed fan module. . . . . . . 707
Product Manager ED-1000 Configure Bridge Port. . . . . . . . . . . . . . . . 707
Product Manager ED-1000 Configure Hub Ports. . . . . . . . . . . . . . . . . 708
Product Manager ED-6064 Port List View Port Properties . . . . . . . . . 709
Product Manager ED-1000 Set Online State . . . . . . . . . . . . . . . . . . . . 710
Product Manager ED-1000 Configure Operating Parameters . . . . . . . 710
ED-1000 Configure Operating Parameters Loop Mode . . . . . . . . . . . . 711
Relationship of zone sets, zones, the default zone and node ports. . . 714
EFC Manager Fabric View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715
Fabric Manager, Topology View with one device . . . . . . . . . . . . . . . . 716
Fabric Manager Zoning View no zone set active . . . . . . . . . . . . . . . . . 717
NT zone with two Netfinity node ports and one ESS node port . . . . . . 718
Fabric Manager Zone Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 719
Fabric Manager Zone Sets and New Zone Set . . . . . . . . . . . . . . . . . . 720
Error saving empty zone set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721
Fabric Manager New Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721
Fabric Manager Add by port number . . . . . . . . . . . . . . . . . . . . . . . . . . 722
Fabric Manager Add Detached Node . . . . . . . . . . . . . . . . . . . . . . . . . 723
Fabric Manager incorrect zone name . . . . . . . . . . . . . . . . . . . . . . . . . 724
Fabric Manager View Zone Members . . . . . . . . . . . . . . . . . . . . . . . . . 725
Fabric Manager assigning zone to zone set . . . . . . . . . . . . . . . . . . . . 726
One zone set - one zone - three node ports . . . . . . . . . . . . . . . . . . . . 726
Fabric Manager zone set activated . . . . . . . . . . . . . . . . . . . . . . . . . . . 727
Fabric Manager Active Zone Set with one zone shown . . . . . . . . . . . . 728
Fabric Manager save active zone set as . . . . . . . . . . . . . . . . . . . . . . . 729
NT zone with three node ports and AIX zone with four node ports . . . 729
Fabric Manager modify selected zone set . . . . . . . . . . . . . . . . . . . . . . 730
Fabric Manager defining an AIX zone . . . . . . . . . . . . . . . . . . . . . . . . . 731
Adding AIX zone to zone set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 732
Two zones in one zone set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 732
Fabric Manager with two zones shown . . . . . . . . . . . . . . . . . . . . . . . . 733
LVM mirroring using the SAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736
Using two independent fabrics for high availability . . . . . . . . . . . . . . . 737
Our zoned multiswitch fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 738
EFC Manager with two managed switches . . . . . . . . . . . . . . . . . . . . . 739
EFC Manager, Configure, Configure Operating Parameters . . . . . . . . 740
EFC Manager Configure Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 742
Figures
xxix
6-83
6-84
6-85
6-86
6-87
6-88
6-89
7-1
7-2
7-3
7-4
7-5
7-6
7-7
7-8
7-9
7-10
7-11
7-12
7-13
7-14
7-15
7-16
7-17
7-18
7-19
7-20
7-21
7-22
7-23
7-24
7-25
7-26
7-27
7-28
7-29
7-30
7-31
7-32
7-33
7-34
7-35
7-36
xxx
EFC Manager two independent fabrics . . . . . . . . . . . . . . . . . . . . . . . . 743
EFC Manager, Fabric View, one merged fabric . . . . . . . . . . . . . . . . . . 744
Fabric Manager, Topology View, two switches defined and cascaded 745
Fabric Manager changing icon text . . . . . . . . . . . . . . . . . . . . . . . . . . . 745
Three switches cascaded, one not defined to the EFC Manager . . . . 746
ED-6064 with one E_Port online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 747
Active Zone Set corresponding to Figure 6-79 on page 738 . . . . . . . . 748
SAN Data Gateway configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 750
SAN connection port assignment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 751
IBM Storage Area Network Data Gateway startup . . . . . . . . . . . . . . . 752
StorWatch SAN Data Gateway Specialist startup . . . . . . . . . . . . . . . . 756
StorWatch SAN Data Gateway Specialist server. . . . . . . . . . . . . . . . . 757
StorWatch SAN Data Gateway Specialist initial view . . . . . . . . . . . . . 758
Selecting from multiple SAN Data Gateways. . . . . . . . . . . . . . . . . . . . 759
Expanded Gateway view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 759
SCSI channel expanded view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 760
SCSI channel data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 761
Disk device data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 762
Fibre Channel port data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763
Fibre Channel host data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 764
SCSI channel parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 764
Advanced SCSI parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 765
Fibre Channel port parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 765
Downloading the SAN Data Gateway firmware . . . . . . . . . . . . . . . . . . 766
SAN Data Gateway Firmware Revision Level . . . . . . . . . . . . . . . . . . . 767
Updating the SAN Data Gateway firmware . . . . . . . . . . . . . . . . . . . . . 767
Specifying location of the firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . 768
Warning message prior to downloading the firmware . . . . . . . . . . . . . 768
Download in progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 769
Message prior to restarting the SAN Data Gateway . . . . . . . . . . . . . . 769
Warning message prior to restarting the SAN Data Gateway . . . . . . . 770
SAN Data Gateway now restarting . . . . . . . . . . . . . . . . . . . . . . . . . . . 770
Restart completed message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 771
New firmware revision level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 771
IBM Storage Area Network Data Gateway channel zoning . . . . . . . . . 774
Enabling Virtual Private SAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775
Loading VPS Registration software on Windows NT . . . . . . . . . . . . . . 776
Specialist display without VPS enabled . . . . . . . . . . . . . . . . . . . . . . . . 777
Specialist after VPS enabled and host registration . . . . . . . . . . . . . . . 778
Host system with no host registration software . . . . . . . . . . . . . . . . . . 778
SAN Data Gateway with two hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . 779
VPS host settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 780
SCSI LUN assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 781
IBM SAN Implementation
7-37
7-38
7-39
7-40
7-41
7-42
7-43
7-44
7-45
7-46
7-47
7-48
7-49
7-50
7-51
8-1
8-2
8-3
8-4
8-5
8-6
8-7
8-8
8-9
8-10
8-11
8-12
8-13
8-14
8-15
8-16
8-17
8-18
8-19
8-20
8-21
8-22
8-23
8-24
8-25
8-26
8-27
8-28
Service terminal display of device map . . . . . . . . . . . . . . . . . . . . . . . . 782
Setting LUN masking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 783
Combining channel zoning and VPS . . . . . . . . . . . . . . . . . . . . . . . . . . 784
Fibre Channel port setting for switch attachment. . . . . . . . . . . . . . . . . 786
Switch registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 787
Switch port login. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 788
IBM SAN Fibre Channel Switch port settings . . . . . . . . . . . . . . . . . . . 788
Changing switch information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 789
Adding an IBM switch to the Gateway . . . . . . . . . . . . . . . . . . . . . . . . . 790
Switch port information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 791
Hosts and a switch on a Gateway port . . . . . . . . . . . . . . . . . . . . . . . . 791
Adding two heterogeneous hosts to the switch . . . . . . . . . . . . . . . . . . 792
VPS Access window with switch and two hosts. . . . . . . . . . . . . . . . . . 793
Setting LUN access for the host FIBRE1 . . . . . . . . . . . . . . . . . . . . . . . 794
McDATA Director connection to a Gateway . . . . . . . . . . . . . . . . . . . . 796
SLIC Router with a single host. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 800
SW1 dip switches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 802
SLIC Manager access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 804
Sample configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 806
Edited configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 807
SLIC daemon start up in Windows NT . . . . . . . . . . . . . . . . . . . . . . . . . 809
SLIC connection window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 810
SLIC Manager title bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 810
Control Center window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 811
Disk drive properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 812
SLIC Router properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 813
Setting the Router to master . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 813
Selecting SignOn drive dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . 814
Composite Drive Member Selection window . . . . . . . . . . . . . . . . . . . . 815
Creating composite drive from available drives . . . . . . . . . . . . . . . . . . 816
Assigning Composite Drive Properties window . . . . . . . . . . . . . . . . . . 817
Completing the Composite Drive setup . . . . . . . . . . . . . . . . . . . . . . . . 818
Control Center with composite drive . . . . . . . . . . . . . . . . . . . . . . . . . . 819
Composite Drive Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 820
Mirror drive member selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 821
Adding a dedicated spare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 822
Mirror drive properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 823
Control Center with Mirror Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 824
Mirror Drive Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 825
Instant Copy Drive Member Selection . . . . . . . . . . . . . . . . . . . . . . . . . 826
Instant Copy Drive Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 827
Control Center with Instant Copy Drive . . . . . . . . . . . . . . . . . . . . . . . . 828
Add Mirror Member display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 829
Figures
xxxi
8-29
8-30
8-31
8-32
8-33
8-34
8-35
8-36
8-37
8-38
8-39
xxxii
Adding drive members to a mirror . . . . . . . . . . . . . . . . . . . . . . . . . . . . 829
Mirror drive properties with copy drive attached . . . . . . . . . . . . . . . . . 830
Creating composite drive to be used in a mirror . . . . . . . . . . . . . . . . . 831
Control Center with two composite drives . . . . . . . . . . . . . . . . . . . . . . 832
Creating mirror drive from two composite drives . . . . . . . . . . . . . . . . . 833
Control Center with mirror drive using two composite drives . . . . . . . . 834
Removing a logical drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 836
Mapping a general spare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 837
UnMapped composite drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 838
Increasing storage capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 840
Increasing throughput . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 840
IBM SAN Implementation
Tables
1-1
1-2
1-3
1-4
1-5
1-6
1-7
1-8
1-9
1-10
1-11
4-1
4-2
4-3
4-4
4-5
4-6
4-7
4-8
4-9
4-10
4-11
4-12
4-13
4-14
4-15
4-16
4-17
4-18
4-19
4-20
4-21
4-22
4-23
4-24
4-25
4-26
4-27
© Copyright IBM Corp. 2001
Fibre Channel cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
iSeries host system limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
OS/400 program temporary fixes for V3R1.0 through V4R1.4 . . . . . . . 11
OS/400 program temporary fixes for V4R2.0 and higher. . . . . . . . . . . . 11
xSeries and NUMA-Q system requirements for the ESS. . . . . . . . . . . . 17
Solaris 2.6, 7, and 8 minimum revision level patches for Fibre Channel 31
Recommended JNI HBA settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Recommended Emulex LP8000 HBA settings. . . . . . . . . . . . . . . . . . . . 42
Recommended QLA2200F HBA settings . . . . . . . . . . . . . . . . . . . . . . . 43
Recommended LP8000 settings for NT . . . . . . . . . . . . . . . . . . . . . . . . . 56
Recommended LP8000 settings for Windows 2000 . . . . . . . . . . . . . . . 67
Fabric Watch — Classes and Areas . . . . . . . . . . . . . . . . . . . . . . . . . . 304
Compatible operating systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461
Port alias screen description: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474
Port zone screen description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476
QuickLoop screen description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
Port Config screen description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480
WWN Alias tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484
WWN zone tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486
QuickLoop tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488
WWN config tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490
AL_PA device alias tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493
AL_PA device zone tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495
QuickLoop tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497
AL_PA device config tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499
Alias tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502
Zone tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504
QuickLoop tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506
Config tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508
ISL Telnet commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513
Canvas configuration list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519
Canvas edit option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519
Switch settings tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531
Network config tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533
Firmware tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535
SNMP tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537
License admin tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
Port settings tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542
xxxiii
4-28
4-29
4-30
4-31
4-32
4-33
4-34
5-1
5-2
xxxiv
User admin tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
Configure tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546
Routing tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549
QuickLoop tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551
Remote switch tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554
Extended fabric tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556
Combination of long distance ports that are available . . . . . . . . . . . . . 565
User levels and default users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 589
Director and port names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 606
IBM SAN Implementation
Preface
“Do everything that is necessary and absolutely nothing that is not.”
In this IBM Redbook, which is an update and major revision of the previous
version, we have tried to consolidate as much of the critical information as
possible while covering procedures and tasks that are likely to be encountered
on a daily basis.
Each of the products described has much, much more functionality than we
could ever hope to cover in just one redbook. The IBM SAN portfolio is rich in
quality products that bring a vast amount of technicality and vitality to the SAN
world. Their inclusion and selection is based on a thorough understanding of the
storage networking environment that positions IBM, and therefore its customers
and partners, in an ideal position to take advantage by their deployment.
In this redbook we cover the latest additions to the IBM SAN family, which
includes products from companies such as Brocade, INRANGE, and McDATA.
We show how they can be implemented in an open systems environment, and
we focus on the Fibre Channel protocol (FCP) environment in particular. We
address some of the key concepts that they bring to the market, and in each
case, we give an overview of those functions that are essential to building a
robust SAN environment.
The team that wrote this redbook
This redbook was produced by a team of specialists from around the world
working at the International Technical Support Organization, San Jose Center.
Jon Tate is a Project Leader for SAN TotalStorage Solutions with the
International Technical Support Organization, San Jose Center. Before joining
the ITSO in 1999, he worked in the IBM Technical Support Center, providing level
2 support for IBM storage products. Jon has 16 years of experience in storage
software and management, services, and support, and he is an IBM SAN
Certified Specialist.
Brian Cartwright is an Advisory I/T Specialist with the Storage Systems Group
and is based in Brisbane, Australia. Brian has 14 years of experience in the I/T
industry with 6 years at IBM working as a Technical Specialist in the S/390 and
Storage Systems Groups. During this time, Brian has been providing pre-sales
and technical support for IBM Storage Solutions and has been heavily involved in
© Copyright IBM Corp. 2001
xxxv
the design and implementation of IBM Storage Area Networks across a wide
customer base. Brian’s expertise includes SAN design, implementation, and
management, and covers a wide range of disk and tape solutions across a
number of different operating system platforms.
Sven Eichelbaum is an I/T Specialist at StorAdvantage GmbH, an IBM Business
Partner based in Germany which specializes in SAN solutions. He has 4 years of
experience in designing and implementing storage architectures. Before joining
StorAdvantage in 2001 he worked in IBM SSD Germany as System Engineer. He
holds a Dipl. Betriebswirt degree in Computer Sciences for Economy from the
Staatliche Studienakademie Sachsen.
Thomas Jahn is an I/T Specialist with IBM Germany SSG. He has 4 years of
experience providing technical support in IBM. Thomas has provided technical
support for networking and server consolidation on OS/390 UNIX for IBM and its
customers before he joined SSD two years ago. He is currently engaged in
providing technical support for open systems storage solutions across multiple
platforms and customer bases. He holds a Dipl. Ing. degree in Computer Science
from the Staatliche Studienakademie Sachsen.
Thanks to the following people for their invaluable contributions to this project:
Scott Drummond
IBM Storage Subsystems Division
Emma Jacobs
Yvonne Lyon
Deanna Polm
Sokkieng Wang
International Technical Support Organization, San Jose Center
Henry Caudillo
Mac Diller
Glenda Fuller
Mike Hrencecin
Ronda Hruby
Robert Moon
Tammy Sokol
Peter Thurston
Diana Tseng
Karen Ward
Rainer Wolafka
Michelle Wright
John Young
Ruoyi Zhou
IBM Storage Subsystems Division
xxxvi
IBM SAN Implementation
Jim Baldyga
AJ Casamento
Al Hicks
Scott Jensen
Brocade Communications Systems
Richio Aikawa
Jon Krueger
Emulex Corporation
Dave Burchwell
Jack Consoli
Richard Kurzban
Mike Naylor
INRANGE Technologies Corporation
Chris Burke
JNI Corporation
Chris Cross
James Escalante
Sean Meagher
Chuy Perez
Jim Wild
McDATA Corporation
Rob Jones
QLogic Corporation
Philipp Alexander
StorAdvantage
Special notice
This publication is intended to help systems and storage administrators install
IBM SAN portfolio equipment. The information in this publication is not intended
as the specification of any programming interfaces that are provided by any of
the SAN hardware and software components contained herein. See the
PUBLICATIONS section of the IBM Programming Announcement for the SAN
hardware and software components contained herein for more information about
what publications are considered to be product documentation.
Preface
xxxvii
IBM trademarks
The following terms are trademarks of the International Business Machines
Corporation in the United States and/or other countries:
e (logo)®
IBM ®
Redbooks
Redbooks Logo
AIX
AS/400
BookMaster
Current
Early
Enterprise Storage Server
ESCON
FICON
FlashCopy
iSeries
Magstar
Netfinity
Notes
NUMA-Q
OS/390
OS/400
pSeries
PTX
RS/6000
S/390
SANergy
SP
StorWatch
System/390
TotalStorage
Wave
xSeries
zSeries
Comments welcome
Your comments are important to us!
We want our IBM Redbooks to be as helpful as possible. Send us your
comments about this or other Redbooks in one of the following ways:
 Use the online Contact us review redbook form found at:
ibm.com/redbooks
 Send your comments in an Internet note to:
redbook@us.ibm.com
 Mail your comments to the address on page ii.
xxxviii
IBM SAN Implementation
1
Chapter 1.
Implementing Fibre Channel
host adapter cards
In this chapter we describe the steps involved in implementing Fibre Channel
host adapter cards in an IBM TotalStorage Enterprise Storage Server (ESS)
environment.
Fibre Channel is a 100-MBps, full-duplex, serial communications technology to
interconnect I/O devices and host systems that are separated by tens of
kilometers.
© Copyright IBM Corp. 2001
1
1.1 Fibre Channel
Fibre Channel transfers information between the sources and the users of the
information. This information can include commands, controls, files, graphics,
video, and sound. Fibre Channel connections are established between Fibre
Channel ports that reside in I/O devices, host systems, and the network that
interconnect them. The network consists of elements like switches, hubs,
bridges, and repeaters that are used to interconnect the Fibre Channel ports.
The ESS architecture supports three basic topologies:
 Point-to-point
 Switched fabric
 Arbitrated loop
Before you start, check that the Fibre Channel host has the correct Fibre
Channel host bus adapters installed or at least has slots available for them. For a
list of operating systems and the host bus adapters for Fibre Channel
attachment, see following the Web site:
www.storage.ibm.com/hardsoft/products/ess/supserver.htm
1.1.1 Fibre Channel cables and adapter types
Use feature code 3022 for the short-wave, Fibre Channel host adapter card.
Feature code 3022 comes with a complimentary 31 m (101 ft), 50 micron
multimode fibre cable.
You can also use a 62.5-micron fiber-optic cable with the short-wave Fibre
Channel card. For a 50-micron multimode fiber-optic cable, use a cable length of
2 m - 500 m (6.5 ft - 1640 ft).
For a 62.5-micron multimode fiber-optic cable, use a cable length of 2 m - 175 m
(6.5 ft - 575 ft).
If you use Fibre Channel to ESCON cable converters at both ends of the link to
allow connection through an ESCON cable, the ESCON cable must be a
62.5-micron fiber-optic cable. The maximum length for the 62.5-micron
fiber-optic cable is 175 m (575 feet).
Limitations on distances between nodes on a Fibre Channel network might exist,
depending on the upper-layer protocol (ULP).
2
IBM SAN Implementation
1.1.2 Fibre Channel node-to-node distances
You can order and have IBM install a maximum of 16 Fibre Channel adapters on
ESS Models F10 and F20. Each adapter has a single host port. You can install
both long-wave adapters and short-wave adapters in a single ESS.
Table 1-1 lists the cables that are available for the long-wave and short-wave
adapters. This table also lists the distances that the cables support. See your
IBM field office about 62.5 micron cables or longer cables.
 Feature code 3021 — Fibre Channel long-wave host adapter (optional 1-16)
for open-systems, AS/400, iSeries, S/390, and zSeries hosts. This adapter
includes a 31 m (101 ft), long-wave optics (9 micron) cable, P/N 08H2774
with an SC-type connector. It provides an interface that supports 100 Mbps
full-duplex data transfer.
 Feature code 3023 — Fibre Channel short-wave host adapter (optional 1-16)
for open-systems, AS/400, iSeries, S/390, and zSeries hosts. This adapter
includes 31 m (101 ft), 50 micron cable, P/N 54G3384 with an SC-type
connector. It provides an interface that supports 100 Mbps full-duplex data
transfer.
Table 1-1 Fibre Channel cables
Adapter
Cable Type
Distance
FC 3023 (short wave)
50 micron, multimode (500 MHz/km)
500 m (1635 ft)
62.5 micron, multimode (200 MHz/km)
300 m (984 ft)
62.5 micron, multimode (160 MHz/km)
250 m (817 ft)
9 micron, singlemode
50 km (31 mi)
62.5 micron, multimode (500 MHz/km)
550 m (1799 ft)
62.5 micron, multimode (200 MHz/km)
550 m (1799 ft)
62.5 micron, multimode (160 MHz/km)
550 m (1799 ft)
FC 3021 (long wave)
For Fibre Channel, the maximum distance between fabric switches, fabric hubs,
and link extenders and a host Fibre Channel port or an ESS Fibre Channel port
is limited to 11 km (6 mi). The maximum distance might be greater than 11 km
(6 mi) when a link extender provides appropriate target initiator or controller
emulation functions such that the length of the connection perceived by the ESS
does not exceed 11 km (6 mi).
Link extenders with emulation functions should not be used on links over which
synchronous PPRC operations are performed because of the additional path
delay introduced by these units.
Chapter 1. Implementing Fibre Channel host adapter cards
3
1.1.3 LUN affinity
For Fibre Channel attachment, LUNs have an affinity to the host's Fibre Channel
adapter through the world-wide port name (WWPN) for the host adapter. In a
switched fabric configuration, a single Fibre Channel host could have physical
access to multiple Fibre Channel ports on the ESS. In this case, you can
configure the ESS to allow the host to use either:
 All physically accessible Fibre Channel ports on the ESS
 Only a subset of the physically accessible Fibre Channel ports on the ESS
In either case, the set of LUNs that are accessed by the Fibre Channel host are
the same on each of the ESS ports that can be used by that host.
1.1.4 Targets and LUNs
For Fibre Channel attachment, each Fibre Channel host adapter can
architecturally attach up to 256 LUNs. The ESS supports only a maximum of
4096 LUNs divided into a maximum of 16 logical subsystems each with up to 256
LUNs. If the software in the Fibre Channel host supports the SCSI command
Report LUNs, then you can configure all 4096 LUNs on the ESS to be accessible
by that host. Otherwise, you can configure no more than 256 of the LUNs in the
ESS to be accessible by that host.
1.2 Attaching an ESS to a FICON channel
This topic tells you how to configure the IBM Enterprise Storage Server for
FICON attachment.
1.2.1 Configuring the ESS for FICON attachment
You can perform a FICON channel attachment on the IBM 2105 Model F10 and
F20. You cannot perform a FICON channel attachment on the IBM 2105 Model
E10 and E20. When you attach an F10 or F20 to a FICON interface, you must
use the following host adapter feature codes:
 Feature code 3021 — This is a long wave laser adapter that includes a 31-m
(100-ft) 50-micron cable with duplex connectors. Because the 3021 uses one
of four slots in one of the four I/O bays, you can have a maximum of 16
adapters in the ESS. This allows you to have a maximum of 16 FICON
interface attachments.
4
IBM SAN Implementation
 Feature code 3023 — This is a short wave laser adapter that includes a 31-m
(100-ft) (50-micron) cable with duplex connectors. When you use the 3023
adapter to perform a FICON channel attachment, you must use the cables for
FICON. The adapters cannot be shared with any Fibre Channel protocol
attachments.
Because the 3023 uses one of four slots in one of the four I/O bays, you can
have a maximum of 16 adapters in the ESS. This allows you to have a maximum
of 16 FICON interface attachments. If the attachments are all point-to-point, you
can attach directly to 16 FICON channels. If you attach to a switch or director,
you can attach a maximum of 128 FICON channels per ESS FICON adapter. For
this scenario, you must be able to attach to a number of hosts. The ESS allows
256 logical paths per FICON link (compared to just 64 for ESCON), 128 logical
paths per logical subsystem, and 2048 logical paths for each ESS.
Before FICON, you could only do a Fibre Channel connect for Fibre Channel
protocol with feature code 3022. Feature code 3023, with a 9-micron single mode
fiber-optic cable, increases the point-to-point distance from 500 m to 10 km.
The increased distance provides greater configuration options with IBM S/390 or
zSeries processors with FICON host adapters.
1.2.2 Attachment considerations
This topic describes some things you should consider before you configure your
system with a FICON interface.
1.2.3 Setting up ESCON and FICON links
If the system requires x ESCON links, where x is the number of links to get the
performance and availability attributes you want, you must consider the number
of ESCON you need. For example, you can map four ESCON links to a single
FICON link and maintain approximately equivalent performance. If the ESCON
channel use is low, you can map six or eight ESCON links to a single FICON link.
1.2.4 Multipathing for ESCON and FICON
Consider the difference between the path groups when you compare FICON to
ESCON. For example, for ESCON, you can configure four or eight paths per
path group from a host to an ESS. For ESCON, you want at least four paths in
the path group to maximize performance. Most ESCON controllers implement
channel command execution that partially synchronizes the lower DASD
interface with the upper channel interface. This channel command only allows
you a very short time to reconnect. The consequence is reconnections that fail.
Chapter 1. Implementing Fibre Channel host adapter cards
5
When you have eight paths in the path group, it minimizes the number of missed
reconnections. Increasing the number of path groups does not minimize the
number of missed reconnections substantially. If you use eight paths in path
groups, you can increase the overall throughput.
For FICON controllers, there is no synchronization between the lower DASD
interface and the upper channel interface. The number of paths in the path group
depend on the throughput requirement. If it takes x paths to satisfy the
throughput requirement, where x is the number of paths, set the path group to x.
Note: x must be a minimum of two and cannot exceed a maximum of eight.
1.2.5 Attaching to a FICON channel or a FICON channel path group
When you attach multiple controllers to a channel, you can use a switch
(director) for each controller, or an ESCON or FICON channel that has a direct
connection to the channel. I/O does not flow through all the other controllers
before you get to the target controller. I/O goes directly to the target controller.
When multiple controllers are connected to a channel through a switch, you
create the logical equivalent of the parallel interconnection.
With the parallel interface and with the ESCON interface, the channel and
controller communicate to form a private connection. None of the other
controllers on the channel can communicate with the channel while this private
connection is in place. The private connection supports input and output between
the channel and the controller. It can run slowly, depending upon the factors that
affect the controller and the device. The protocol does not allow any of the
serially connected controllers to use any spare cycles. The result is poor
performance.
FICON does not support a private connection. FICON performs frame (or packet)
multiplexing. A configuration with the serially connected controllers
communicates with the controllers simultaneously. It can multiplex I/O operations
across all controllers simultaneously. No interface cycles are wasted because of
the private connection. You can serially connect controllers with FICON.
The next question though is whether or not it is OK to serially connect DASD
control units with tape controllers. Tape generally performs much larger I/O
operations at any instant in time. Therefore, even with FICON, when you have
Tape I/O running, you can temporarily lockout some DASD I/O. Hence, it is still
better not to put tape and DASD on the same FICON channel.
6
IBM SAN Implementation
1.2.6 Attaching an ESS to FICON channels
You can use the following FICON adapters with the IBM S/390 Enterprise
Storage Servers.
 Feature code 2314 — This is the long-wave laser adapter.
 Feature code 2316 — This is the short-wave laser adapter.
You can use the following FICON adapters with the IBM S/390 or zSeries
system:
 Feature code 2315 — This is the FICON long-wave laser adapter. This
adapter has two ports per adapter. This adapter is a 9-micron single mode
cable, but you can use it with a 62.5-micron multimode cable when you attach
mode-conditioning cables at each end.
 Feature code 2318 — This is the FICON short-wave laser adapter. This
adapter has two porters per adapter. The short-wave laser adapter supports
the 50 and 62.5-micron multimode cable.
You can attach the FICON channels directly to an ESS or you can attach the
FICON channels to a Fibre Channel switch. When you attach the FICON
channels directly to an ESS, the maximum number of FICON attachments is 16.
That is the maximum number of host adapters you can configure in an ESS.
When you use an ESS host adapter to attach to FICON channels either directly
or through a switch, the adapter is dedicated to FICON attachment and may not
be simultaneously attached to Fibre Channel protocol hosts.
When you attach an ESS to FICON channels through one or more switches, the
maximum number of FICON attachments is 128 per ESS adapter. The directors
provide very high availability with redundant components and no single points of
failure or repair.
You can use the McDATA ED-6064 Enterprise Fibre Channel director or
INRANGE FC/9000 Fibre Channel director.
You can use either director to attach Fibre Channel protocol hosts and devices in
addition to the FICON hosts and devices. For these configurations, the Fibre
Channel protocol hosts should communicate only with the Fibre Channel
protocol devices. The FICON hosts should communicate only with the FICON
devices. IBM recommends that you set up zones in the directors to guarantee
that none of the Fibre Channel protocol hosts or devices can affect the FICON
traffic.
When you attach FICON products to switches or directors, note that switch
cascading is not allowed. You cannot configure a fabric of multiple
interconnected directors and have a FICON channel attached to one director
communicate to a FICON control unit attached to another director.
Chapter 1. Implementing Fibre Channel host adapter cards
7
The FICON architecture prohibits this capability. The reason for the restriction is
because the base S/390 and zSeries I/O architecture uses a single byte for
addressing the I/O devices. This one-byte I/O address is not compatible with the
Fibre Channel, 3-byte port address. The FICON solution to this problem is to
disallow switch cascading.
1.3 IBM iSeries FC host system attachment
This topic describes the host system requirements and provides the procedure to
attach your IBM AS/400 or iSeries host system to the IBM Enterprise Storage
Server (ESS) with Fibre Channel adapters.
Note: The IBM AS/400 or iSeries host systems do not support serially
interconnected host systems attached to the ESS. They also do not support
serially interconnected ESS attachments to a single port on the host adapter.
Your IBM AS/400 or iSeries host systems support the ESS as a peripheral
device.
The ESS presents individual 2105 LUNs to the AS/400 or iSeries host system.
You do not need to perform manual tasks to assign LUN addresses, as the ESS
will do it automatically during configuration.
Note: You cannot use the IBM Subsystem Device Driver on the AS/400 or
iSeries host system.
1.3.1 Host limitations for the iSeries
In Table 1-2 we show a description of the LUN assignments for the iSeries host
system.
Table 1-2 iSeries host system limitations
Host system
LUN
assignments
per target
Configuration notes
iSeries (Fibre Channel)
0 - 32
There is one target per iSeries adapter
The naming convention for the iSeries now describes models 270 and 8xx, which
attach through an FC adapter 2766. Use migration tower 5035 or 5077 for the
model 8xx. You can also make a connection using a 6501 with SCSI cables.
8
IBM SAN Implementation
1.3.2 Attachment requirements for the AS/400 or iSeries
This section lists the requirements for attaching the ESS to your host system:
1. Ensure that you have all of the items in the equipment list.
2. Obtain the documents for the IBM AS/400 or iSeries host system from the
following Web site:
publib.boulder.ibm.com/pubs/html/as400/infocenter.htm
3. See the following Web site for details about program temporary fixes (PTFs)
that you need to install on your AS/400 or iSeries host system:
www.storage.ibm.com/hardsoft/products/ess/supserver.htm
4. Check the LUN limitations for your host system.
5. Contact your IBM service support representative to install and configure the
IBM ESS.
1.3.3 Attachment considerations
This section lists the attachment considerations for an AS/400 or iSeries host
system. The following must be taken into account:
 You can specify a LUN serial number that is eight characters. For example,
you can specify a LUN serial number, 0LLLLNNN, where:
The LUN serial number is eight characters in the format 0LLLLNNN, where:
LLLL — a unique volume number assigned by the ESS when the LUN is
created.
NNN — low-order three characters of the ESS unit serial number or unique
three character value entered using an ESS service panel menu option.
The menu option is found by using the following method:
a. From Service Menu choose the option Configuration Options Menu
b. Take the option Change / Show Control Switches.
c. Highlight the option AS/400 LUN Serial Number Suffix.
d. On the option Control Switch Value press F4 to list the available values.
Note: The default value is the last three digits of the serial number for the
ESS. This might create problems on iSeries systems that have multiple ESSs
attached to the same host system. We recommended that you use the value
Use_Box_S/N.
Chapter 1. Implementing Fibre Channel host adapter cards
9
The following considerations need to be taken into account:
 You cannot specify a LUN size of 4.190-GB LUN for the SCSI Fibre Channel
protocol (FCP) attachment.
 You can specify 1- 32 LUNs for each attachment to an AS/400 or iSeries Fibre
Channel protocol adapter.
 Fibre Channel attached LUNS are identified as the 2105 device type on the
iSeries host system.
 You can place an AS/400 or iSeries volume in the ESS storage arrays
according to the selected host system attachment type.
For a Fibre Channel attachment, you must place the volumes in ESS RAID-5
storage arrays that have capacity available. You can spread the volumes
across arrays that are attached to multiple device adapters.
 You cannot place an AS/400 or iSeries volumes in an ESS non-RAID storage
array.
 You cannot share an AS/400 or iSeries volume with more than one Fibre
Channel system attachment.
 The number of volumes that you can create is determined by the attachment
type and by the available ESS storage array capacity.
 You can create 1 - 32 LUNs for a Fibre Channel attachment.
1.3.4 Recommended configurations for the AS/400 or iSeries
IBM recommends the following configurations:
 Install the 2766 adapter card in the AS/400 iSeries system unit or the HSL
PCI I/O towers.
Feature code 2766 is an IOA (I/O adapter).
Important: Do not use more than two 2766 adapter cards for each AS/400
or iSeries tower.
The following must be taken into account:
1. Only one 2766 adapter is supported per I/O processor (IOP) and requires a
dedicated IOP. No other I/O adapters are supported under the same IOP.
2. Only two 2766 adapters are supported per a multi-adapter bridge.
10
IBM SAN Implementation
1.3.5 Software requirements for the IBM OS/400 operating system
Release V3R1.0 and later releases of the OS/400 or iSeries operating system
support 4-GB and 8-GB capacity disk drives. In Table 1-3 we list the required
program temporary fixes (PTFs) for OS/400 or iSeries versions that do not
include the PTFs in the base code.
Table 1-3 OS/400 program temporary fixes for V3R1.0 through V4R1.4
Operating System Version Level
PTF
V3R1.0
SF44131
V3R2.0
SF44132
V3R6.0
SF44126
V3R7.0
SF44127
V4R1.0
SF44113
V4R1.4
SF44745
Releases V4R2.0, V4R3.0, and V4R4.0 also support 18-GB and 36-GB capacity
logical unit numbers with the PTFs shown in Table 1-4.
Table 1-4 OS/400 program temporary fixes for V4R2.0 and higher
Operating System Version Level
PTF
V4R2.0
SF44114 MF21961
MF21975
V4R3.0
MF21962 MF21979
V4R4.0
MF21963 MF21978
1.4 IBM RS/6000 or pSeries FC host system attachment
This topic describes the host system requirements and provides the procedures
to attach an ESS to any of the following:




IBM RS/6000
pSeries host system
IBM RS/6000 Series Parallel (SP) Complex
pSeries SP Complex host system
Chapter 1. Implementing Fibre Channel host adapter cards
11
Note: For an RS/6000 and pSeries host system, you can use two topologies:
 Point-to-point (switched fabric) topology
 Arbitrated loop topology
The RS/6000 and pSeries host system does not support more than one host bus
adapter on the loop. The RS/6000 and pSeries host system does support a direct
connection of the RS/6000 and pSeries host system to an ESS using the Fibre
Channel arbitrated loop protocol.
1.4.1 Attachment requirements
This section lists the requirements for attaching the ESS to your host system.
 Ensure that you have all of the items listed in the Equipment requirements.
 Ensure that you have the installation script files. These files are on the
diskette and the compact disc you receive with the ESS.
 Ensure that you have 1 MB minimum of hard disk space available to install
the AIX host attachment package.
 Ensure that you have the documentation for your host system and the IBM
Enterprise Storage Server User's Guide. The User's Guide is on the compact
disc that you receive with the ESS.
For details about the release level for your operating system, see the following
Web site:
www.storage.ibm.com/hardsoft/products/ess/supserver.htm
Either you or an IBM service support representative (SSR) must perform the
following tasks to install and configure an ESS.
1. The IBM SSR installs the ESS by using the procedures in the IBM Enterprise
Storage Server Service Guide.
2. Either you or an IBM SSR defines the Fiber Channel port configuration if you
did not do it during the installation of the ESS or Fibre Channel adapters.
Note: Use the information on the logical configuration work sheet in the IBM
Enterprise Storage Server Configuration Planner that you previously filled out.
3. Either you or an IBM SSR configures the host system for the ESS. Use the
instructions in your host system publications.
12
IBM SAN Implementation
4. Either you or an IBM SSR checks the LUN limitations for the RS/6000 and
pSeries. See Table 2.
Note: The IBM Subsystem Device Driver supports RS/6000 and pSeries host
systems in a clustering environment. To have failover protection on an open
system, the IBM Subsystem Device Driver requires a minimum of 2 Fibre
Channel adapters. The maximum number of Fibre Channel adapters
supported is 16 for a total of 16 Fibre Channel ports.
1.4.2 Installing the 2105 host attachment package
This section provides the instructions to install the host attachment package for
the ESS on your host system. IBM recommends that you run the host attachment
package on each host system attached to the ESS for which an installation script
is provided.
Before installing the 2105 host attachment package
Perform the following steps before you install the host attachment package:
1. Attach the ESS to your host system. See Attaching an ESS to an
open-systems host with SCSI adapters.
2. Turn on the host system and all attachments.
3. Ensure that you have root access.
4. Ensure that you have administrator knowledge.
5. Ensure that you have knowledge of the System Management Interface Tool
(SMIT).
1.4.3 Replacing an older version of the 2105 installation package
If you want to replace an older version of the host attachment package (tar
version) and have data that exists on all configured 2105 disks, the code prompts
you to remove all ESS product-related hdisk devices. Perform the following steps
to remove the devices:
1. Run the umount command on the file system.
For example, type umount -t x, where x is the file system name.
2. Run the varyoffvg 2105 command for the volume group.
For example, type varyoffvg -s VGname
3. Type rmdev -dl on the command line to unconfigure the 2105 devices.
Chapter 1. Implementing Fibre Channel host adapter cards
13
After you install the ibm2105.rte file and all of the 2105 devices are reconfigured,
vary on the volume groups and remount the file systems. The data on the file
systems should be available again.
1.4.4 Installing the 2105 host attachment package
Perform the following steps by using SMIT to install the IBM 2105 host
attachment on your system. Install the host attachment package from a compact
disc or a diskette. You must have superuser authority to complete the
instructions.
Note: The following procedure is an example. The example uses /dev/cd0 for
the address of the CD-ROM drive. Your address might be different.
1. From your desktop window, type smit install_update to go directly to the
installation panel.
2. Click Install and Update from the Latest Available Software and press Enter.
3. Press F4 to open the Input Device/Directory for Software window.
4. Select the CD-ROM drive that you are using for the installation, for example,
/dev/cd0.
5. Press Enter.
The Install and Update from the Latest Available Software window opens.
6. Click Software to Install and press F4.
7. Select Software Packages and press F7.
The Install and Update from the Latest Available Software panel is displayed with
the name of the software you selected to install.
8. Check the default option settings to ensure that they are what you need.
9. Press Enter to install the software.
SMIT responds with the following question: Are you sure?
10.Press Enter to continue.
The installation process may take several minutes. A message is displayed when
the installation process is complete.
11.Press Enter to continue. The installation process may take several minutes.
A message is displayed when the installation process is complete.
12.Press F10 when the installation process is complete.
13.Exit from SMIT.
14
IBM SAN Implementation
14.Remove the compact disc.
15.Shut down the host system.
16.Turn on the host system.
1.4.5 Verifying the ESS configuration
To verify the configuration of the ESS on the AIX host system, type the following
command:
lsdev -Cc disk | grep 2105
A list of all IBM ESS devices is displayed as shown in the following example:
hdisk3 Available 30-68-01 IBM FC2105F20
hdisk4 Available 30-68-01 IBM FC2105F20
hdisk5 Available 30-68-01 IBM FC2105F20
These indicate that the installation is successful.
If a device is listed as another type of device, the message shown below is
displayed. This message indicates that the configuration was not successful.
hdisk3 Available 30-68-01, Other FCSCSI disk device
hdisk4 Available 30-68-01, Other FCSCSI disk device
hdisk5 Available 30-68-01, Other FCSCSI disk device
1.4.6 ESS devices with multiple paths per LUN
The ESS supports multiple path configurations for a LUN. This means that you
can have multiple hdisks available on the AIX server for each physical LUN. If
you create a PVID sector 0 of a LUN and you delete all hdisks from the system
with the rmdev command, you must restart the system. If you want to restore all
multiple paths for all LUNS, use the cfgmgr command for each Fibre Channel
adapter.
1.5 IBM eServer xSeries or IBM NUMA-Q FC attachment
This topic tells you how to attach an ESS to an xSeries or an IBM NUMA-Q host
system with Fibre Channel adapters. We also tell you how to install and configure
the IOC-0210-54 adapter card.
Note: You must use the switched fabric topology to attach the ESS to either an
xSeries or to an IBM NUMA-Q host system.
Chapter 1. Implementing Fibre Channel host adapter cards
15
The ESS also offers the following interim support for Fibre Channel attachment:
Feature Code 3019 — With the feature code 3019, you can attach an ESS to an
xSeries or an IBM NUMA-Q host system through the NUMA-Q Fibre Channel- toSCSI bridge. This feature code includes one SCSI adapter that you purchase
and a no-cost loan of a NUMA-Q Fibre Channel to SCSI bridge. IBM requires
that you sign a loan agreement for the bridge.
Note: Feature code 3019 is not a standard feature. To get feature code 3019,
contact your IBM sales representative.
For more information about how to attach an xSeries or a NUMA-Q host system
with Fibre Channel adapters, see the NUMA-Q ESS Integration Release Notes
and the Fibre Channel Subsystem Installation Guide. To obtain a copy, see your
IBM sales representative.
1.5.1 Attachment requirements
This section lists the requirements for attaching the ESS to your host system.
Either you or an IBM service support representative (SSR) must perform the
following tasks to install and configure an ESS:
1. The IBM SSR installs the IBM ESS by using the procedures in the IBM
Enterprise Storage Server Service Guide.
2. Either you or the IBM SSR defines the Fibre Channel host system with the
worldwide port name identifiers. For information about how to locate the
worldwide port name for an xSeries or an NUMA-Q host system, see 1.12,
“Locating the worldwide port name” on page 69.
3. Either you or the IBM SSR defines the Fiber Channel port configuration if you
did not do it during the installation of the ESS or Fibre Channel adapters.
Note: Use the information on the logical configuration work sheet in the IBM
Enterprise Storage Server Configuration Planner that you previously filled out.
4. Configure your host system for the ESS by using the instructions in your host
system publications.
1.5.2 xSeries and NUMA-Q system requirements
The ESS is supported on the xSeries and the NUMA-Q host systems by a
module of code that is incorporated into Service Pack 3 for PTX V4.5.2. To install
Service Pack 3:
16
IBM SAN Implementation
1. Insert the Service Pack 3 compact disc into the CD-ROM or CD-R drive.
2. Open the README file for instructions on installing Service Pack 3.
In Table 1-5 we show the NUMA-Q system requirements. Support for Copy
Services on PTX V4.5.2 requires a special Technology Pack. You can obtain the
Technology Pack through an IBM sales representative who handles your xSeries
and NUMA-Q purchases.
Table 1-5 xSeries and NUMA-Q system requirements for the ESS
xSeries and NUMA-Q System Element
Requirement
PTX operating system
Version 4.5.2 or higher
NUMA-Q and xSeries hardware models
All NUMA-Q and xSeries Quad-based systems
Fibre Channel host adapter
Emulex LP7000E with firmware SF 3.2.1
Fibre Channel switch
IBM 2109 Model S08 or IBM 2109 Model S16
Clustered NUMA-Q and xSeries hosts
ptx/Clusters V2.2.1
1.5.3 Installing the IOC-0210-54 adapter card
Perform the following steps to install the IOC-0210-54 adapter card:
1. Contact your IBM SSR to install the IOC-0210-54 adapter card in the ESS.
2. Connect the cable to the ESS port.
The SSR establishes the private LAN connection between both clusters on
the ESS, the Ethernet hub, and the ESS personal computer console.
Preconfigured multimode optical cables are available to connect the ESS to
the NUMA-Q host system. The 8m (24-ft) cable might be required. The way
you connect the cable to the ESS through the Fibre Channel switch depends
on the level of I/O throughput.
For information about connection schemes, see the Fibre Channel
Subsystems Installation Guide at the following Web site:
techdocs.sequent.com/staticpath/shsvccd/start.htm
3. Restart the server.
1.5.4 Configuring the IOC-0210-54 adapter card
To configure the IOC-0210-54 adapter card, contact your IBM SSR or see the
IBM Enterprise Storage Server Web Interface User's Guide.
Chapter 1. Implementing Fibre Channel host adapter cards
17
1.6 Compaq host system FC attachment
This topic describes the host system requirements and provides the procedure to
attach a Compaq Alpha server to an ESS. The ESS supports the following
Compaq Alpha server models:




2100
4100
8200
8400
1.6.1 Attachment requirements
This section lists the requirements to attach the ESS to your host system.
 Ensure that you have all of the items listed in Equipment requirements.
 Check the logical unit number limitations for your host system. See Table 2.
 Ensure that you have the documentation for your host system and the IBM
Enterprise Storage Server User's Guide. The User's Guide is on the compact
disc that you receive with the ESS.
See the following Web site for details about the release level for your
operating system:
www.storage.ibm.com/hardsoft/products/ess/supserver.htm
Either you or an IBM service support representative (SSR) must perform the
following tasks to install and configure an IBM ESS.
1. An IBM SSR installs the IBM Enterprise Storage Server by using the
procedures in the IBM Enterprise Storage Server Service Guide.
2. Either you or an IBM SSR assigns the Fibre Channel hosts to the Fibre
Channel ports on the ESS.
Note: Use the information on the logical configuration work sheet in the IBM
Enterprise Storage Server Configuration Planner that you should have
previously filled out.
3. Either you or an IBM SSR configures the host system for the ESS. Use the
instructions in your host system publications.
Note: The IBM Subsystem Device Driver does not support the Compaq open
system in a clustering environment. To have failover protection on an open
system, the IBM Subsystem Device Driver requires a minimum of two
adapters. You can run the Subsystem Device Driver with one Fibre Channel
adapter, but you have no failover protection. The maximum number of
adapters supported is 32.
18
IBM SAN Implementation
1.6.2 Compaq Tru64 UNIX Version 4.0x host system
In this topic we explain how to install and configure a Tru64 UNIX Version 4.0x
host system. Before you configure the ESS volumes, ensure that the system and
Fibre Channel adapter cards are at the minimum supported firmware revision.
1.6.3 Verifying the Compaq configuration
The following procedures tell you how to verify the configuration for the host
adapter cards and firmware for a Compaq host system:
1. From the console prompt, type show version
This is an example of what you see when you type the show version
command.
version V5.8-2, 21-Jul-2000 17:16:08
2. Type #view /var/adm/messages to display the log file that shows the system
version and the version of the Fibre Channel adapter cards.
This is an example of how the firmware version and the host adapter is
displayed
Sep 21 14:17:10 osplcpq-ds20 vmunix: Firmware revision: 5.8
Sep 21 14:17:10 osplcpq-ds20 vmunix: KGPSA adapter: Driver Rev 1.09 :
F/W Rev 2.22X1(1.13) : wwn 1000-0000-c922-d469
1.6.4 Operating system device recognition
You can access the disks in the special files. You can find the special files in the
/dev directory. The disk block special file starts with rz and the character disk
special file starts with rrz. Compaq Tru64 UNIX uses the following syntax to
identify the disk special files:
[r] rz [L] [B] [P]
In this syntax:
 [L] — LUN letter. If the LUN is 0, no letter is specified for the LUN. You can
specify LUNs 2 - 7 for letters b - h.
 [B] — Bus number multiplied by 8 plus the target number
 [P] — Disk partition from a - h
Following is an example of the output that is displayed from boot log or the scu
show edt command). This shows a disk at LUN 0, bus SCSI 16, target 0.
[r]rz[LUN 0][16 * 8 + 0][a-h] = rz128a, rz128b, rz128c, rz128d, rz128e, rz128f,
rz128g, rz128h,rrz128a, rrz128b, rrz128c, rrz128d, rrz128e, rrz128f, rrz128g,
rrz128h
Chapter 1. Implementing Fibre Channel host adapter cards
19
You do not need to perform any special operations on the Compaq system to
view the ESS volumes. Ensure that the host Fibre Channel is already configured.
If it is not configured, you must perform the instructions that come with the card
to install the driver. Make all the hardware connections, configure the ESS, and
restart the host system. If you can see the disks when you restart, all the special
files are created automatically.
If you cannot restart the host system, you can configure the devices manually by
typing #scu scan edt. You can check to see if you can see the volumes by typing
#scu show edt. To create the device special files type #doconfig -d. No kernel
rebuild is necessary.
When the ESS is configured, ensure that you can see the disks from the Compaq
system. Wait for the system to restart or use the file command on the device
special files. During restart, the following messages should be displayed:
emx0 at pci1 slot 7 KGPSA-BC : Driver Rev 1.21 : F/W Rev 2.22X1(1.13) : wwn
1000-0000-c922-d469
emx0: emx_assign_fcp_id: nport at DID 0x21300 assigned tgt id 10 - out of range
for CAM
scsi16 at emx0 slot 0
rz128 at scsi16 target 0 lun 0 (LID=0) (IBM 2105F20 1013)
rzb128 at scsi16 target 0 lun 1 (LID=1) (IBM 2105F20 1013)
rzc128 at scsi16 target 0 lun 2 (LID=2) (IBM 2105F20 1013)
rzd128 at scsi16 target 0 lun 3 (LID=3) (IBM 2105F20 1013)
rze128 at scsi16 target 0 lun 4 (LID=4) (IBM 2105F20 1013)
rzf128 at scsi16 target 0 lun 5 (LID=5) (IBM 2105F20 1013)
rzg128 at scsi16 target 0 lun 6 (LID=6) (IBM 2105F20 1013)
rzh128 at scsi16 target 0 lun 7 (LID=7) (IBM 2105F20 1013)
When the host system completes the restart, login as the root. Use the file
command to ensure that all the special files were created.
Use the file command to check the major number. If there is a description of the
disk, you will not find the model of the disk. Use the information from the output of
the previous command or calculate the special file syntax.
This shows an example of what you see when you type #file /dev/rrz*128c.
/dev/rrz128c:
character
ID #0) (SCSI LUN #0)
/dev/rrzb128c: character
ID #0) (SCSI LUN #1)
/dev/rrzc128c: character
ID #0) (SCSI LUN #2)
/dev/rrzd128c: character
ID #0) (SCSI LUN #3)
/dev/rrze128c: character
ID #0) (SCSI LUN #4)
20
IBM SAN Implementation
special (8/262146) SCSI #16 2105F20 disk #1024 (SCSI
special (8/262210) SCSI #16 2105F20 disk #1025 (SCSI
special (8/262274) SCSI #16 2105F20 disk #1026 (SCSI
special (8/262338) SCSI #16 2105F20 disk #1027 (SCSI
special (8/262402) SCSI #16 2105F20 disk #1028 (SCSI
/dev/rrzf128c: character special (8/262466) SCSI #16 2105F20 disk #1029 (SCSI
ID #0) (SCSI LUN #5)
/dev/rrzg128c: character special (8/262530) SCSI #16 2105F20 disk #1030 (SCSI
ID #0) (SCSI LUN #6)
/dev/rrzh128c: character special (8/262594) SCSI #16 2105F20 disk #1031 (SCSI
ID #0) (SCSI LUN #7)
If a special file does not have a disk associated with it, the output of the #file
command will only show the part concerning the major number. No disk model is
displayed.
This is an example showing a disk model:
/dev/rrzh128c:
character special (8/262594)
Type #disklabel rz128 to see if the disks have a valid disklabel. Then type
#/dev/rrz128a
The following shows an example of the output from these commands:
type: SCSI
disk: 2105F20
label:
flags: dynamic_geometry
bytes/sector: 512
sectors/track: 64
tracks/cylinder: 30
sectors/cylinder: 1920
cylinders: 1017
sectors/unit: 1953152
rpm: 7200
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0
# milliseconds
track-to-track seek: 0 # milliseconds
drivedata: 0
8 partitions:
#
size
offset
fstype
[fsize bsize
cpg] #
a:
131072
0
unused
0
0 # (Cyl.
0 - 68*)
b:
262144
131072
unused
0
0 # (Cyl.
68*- 204*)
c:
1953152
0
unused
0
0 # (Cyl.
0 - 1017*)
d:
0
0
unused
0
0 # (Cyl.
0 - -1)
e:
0
0
unused
0
0 # (Cyl.
0 - -1)
f:
0
0
unused
0
0 # (Cyl.
0 - -1)
g:
819200
393216
unused
0
0 # (Cyl. 204*- 631*)
h:
740736
1212416
unused
0
0 # (Cyl. 631*- 1017*)
Chapter 1. Implementing Fibre Channel host adapter cards
21
If there is no disklabel on the disk, type the following command to write the label
to the disk:
#disklabel -rw rzh128 shark
Substitute your specific disk with the rzh128 command. Always specify the rz
file without the partition.
1.6.5 Configuring AdvFS
Before you create an AdvFS file system, you must design a structure by
assigning a file domain and the file sets. Type the following commands to create
an AdvFS file system with file sets:
1. # cd /
2. # mkfdmn -rw /dev/rzXc vol1_dom
3. # mkfset vol1_dom vol1
4. # mkdir /vol1 # mount vol1_dom#vol1 /vol1
To display all mounted devices, type: df -k
1.6.6 Configuring devices to mount automatically
To enable an AdvFS file system to start automatically, add an entry to the
/etc/fstab file to the mount command during startup. The following shows an
example of a modified /etc/fstab file.
The lines that are shown in bold are the lines that were entered since the initial
operating system installation:
# root_domain#root / advfs rw,userquota,groupquota 0 0
/proc /proc procfs rw 0 0
usr_domain#usr /usr advfs rw,userquota,groupquota 0 0
/dev/rz8b swap1 ufs sw 0 2
vol1_dom#vol1 /vol1 advfs rw,userquota,groupquota 0 2
vol2_dom#vol1 /vol2 advfs rw,userquota,groupquota 0 2
vol3_dom#vol1 /vol3 advfs rw,userquota,groupquota 0 2
vol4_dom#vol1 /vol4 advfs rw,userquota,groupquota 0 2
vol5_dom#vol1 /vol5 advfs rw,userquota,groupquota 0 2
vol6_dom#vol1 /vol6 advfs rw,userquota,groupquota 0 2
vol7_dom#vol1 /vol7 advfs rw,userquota,groupquota 0 2
vol8_dom#vol1 /vol8 advfs rw,userquota,groupquota 0 2
vol9_dom#vol1 /vol9 advfs rw,userquota,groupquota 0 2
vol10_dom#vol1 /vol10 advfs rw,userquota,groupquota 0 2
When the host system starts, it mounts all volumes that you created in 1.6.5,
“Configuring AdvFS” on page 22.
22
IBM SAN Implementation
1.7 Hewlett Packard 9000 FC host system attachment
This topic describes the host system requirements and provides procedures to
attach an ESS to a Hewlett Packard 9000 host system with Fibre Channel
adapters.
1.7.1 Attachment requirements
This section lists the requirements for attaching the ESS to your host system:
 Ensure that you have all of the items listed in Equipment requirements.
 Ensure that you have the installation script files. The script file is on the
compact disc that you receive with the ESS.
 Ensure that you have 1 MB minimum of hard disk space available to install
the 2105inst script file.
 Check the LUN limitations for your host system; see Table 2.
 Ensure that you have the documentation for your host system and the IBM
Enterprise Storage Server User's Guide. The User's Guide is on the compact
disc that you receive with the ESS.
See the following Web site for details about the release level for your operating
system:
www.storage.ibm.com/hardsoft/products/ess/supserver.htm
Either you or an IBM service support representative (SSR) must perform the
following tasks to install and configure an ESS.
1. The IBM SSR installs the ESS by using the procedures in the IBM Enterprise
Storage Server Service Guide.
2. Either you or an IBM SSR defines the Fibre Channel host system with the
worldwide port name identifiers. For the list of worldwide port names, see
1.12, “Locating the worldwide port name” on page 69.
3. Either you or an IBM SSR defines the Fiber Channel port configuration if you
did not do it during the installation of the ESS or Fibre Channel adapters.
Note: Use the information on the logical configuration work sheet in the IBM
Enterprise Storage Server Configuration Planner that you previously filled out.
Chapter 1. Implementing Fibre Channel host adapter cards
23
4. Either you or an IBM SSR configures the host system for the ESS by using
the instructions in your host system publications.
Note: The IBM Subsystem Device Driver 1.1.3 supports the Hewlett Packard
host system in a clustering environment. To have failover protection on an
open system, the IBM Subsystem Device Driver requires a minimum of two
Fibre Channel adapters. The maximum number of Fibre Channel adapters
supported is 16 for a total of 16 Fibre Channel ports.
1.7.2 Installing the 2105 host install script file
This section provides the instructions to install the 2105 host install script file
from a compact disc for the ESS on your host system.
Before installing the 2105 host install script file, connect the host system to the
ESS. See Attaching an ESS to an open-systems host with SCSI adapters.
Install the 2105 host install script from a compact disc. You must have superuser
authority to complete these instructions. The following must be taken into
account:
1. You can only install and run the IBM 2105 set queue depth program (version
2.7.1.00) on HP-UX operating system 10.01or later.
2. If an ESS was used with the SAN Data Gateway on a Hewlett Packard host
system and the LUNs were created as Fibre Channel devices by spoofing
HP-UX and describing the ESS device types as Sun or other non-Hewlett
Packard Fibre Channel device types, the LUNs created under this false ID
must be deleted and recreated as Hewlett Packard device types.
Perform the following steps to install the 2105 host install script from a compact
disc.
1. If you do not already have a directory called /SD_CDROM, type mkdir
/SD_CDROM to create a new directory.
2. Insert the compact disc into the CD-ROM drive.
3. Mount the drive as a file system.
4. Type: ioscan -fnkC disk
Look for the device name on the list with a name of either compact disc or
DVD.
Type: mount -o cdcase /dev/dsk/c_t_d_ / SD_CDROM
Replace /dev/dsk/c_t_d_ with the device special file found in step 4.
5. Type: swinstall -s /SD_CDROM/hp-common/IBMis.depot
24
IBM SAN Implementation
6. From the Software Selection window, click IBMis_tag.
7. From the Action menu, click Mark for Install.
8. When you see the word Yes next to the IBMis_tag product, go to the Action
menu and click Install.
9. When the analysis completes with no errors (Status- Ready), click OK.
10.Click Yes in the Confirmation window to begin the installation.
A window opens, notifying you that the installation is complete and that the
system needs to be restarted.
11.Click OK to continue.
1.7.3 Configuring the IBM 2105 for clustering
This section describes how to configure a Hewlett Packard host system for
clustering.
The steps to configure MC/ServiceGuard with the IBM 2105 are the same as the
steps in the Hewlett Packard high availability documentation located at the
following Web site:
www.docs.hp.com/hpux/ha/index.html
If you are not familiar with the steps in the Hewlett Packard documentation, IBM
recommends that the system administrator attend the Hewlett Packard class
about high availability features.
After you configure your host for normal operating system access, the 2105 acts
as a normal disk device in the MC/ServiceGuard configuration. IBM recommends
that you create volume groups that contain the volumes using the Hewlett
Packard logical volume manager. This method of disk management is more
reliable, easier, and more flexible to manage than whole-disk management
techniques.
Creating volume groups also allows the implementation of PV-Links, Hewlett
Packard's built-in multipathing software, for highly available disks such as the
IBM 2105. To establish PV-Links, perform the following steps:
1. Create the volume group, using the path to the volumes that you want as the
primary path to the data.
2. Extend the volume group with the path to the volumes intended as alternate
paths. The logical volume manager reads the label on the disk and knows
that it is an alternate path to one of the volumes in the group. The logical
volume manager labels the volume. For example, if a host has access to a
volume on a 2105 with the device nodes c2t0d0 and c3t0d0, you can use the
c2 path as primary and create the volume group using only the c2t0d0 path.
Chapter 1. Implementing Fibre Channel host adapter cards
25
3. Extend the volume group to include the c3t0d0 path. When you issue a
vgdisplay -v command on the volume group, it lists c3t0d0 as an alternate
link to the data.
1.8 Novell NetWare FC host system attachment
This topic describes how to attach a Novell NetWare host system to an IBM ESS
with the following adapter cards:
 QLogic QLA2100F
 QLogic QLA2200F
Note: The IBM SAN Fibre Channel Switch 2109 S08 and IBM SAN Fibre
Channel Switch 2109 S16 are supported for Novell NetWare. The IBM SAN
Data Gateway 2108 Model G07 is not supported for Novell NetWare.
1.8.1 Installing the QLogic QLA2100F adapter card
This section tells you how to attach an ESS to a Novell NetWare host system
with the QLogic QLA2100F adapter card.
Single-port Fibre Channel interfaces with the QLogic QLA2100F adapter card
support the following loop modes:
 Target
 Initiator
 Target and initiator
Note: The arbitrated loop topology is the only topology available for the
QLogic QLA2100F adapter card.
Perform the following steps to install the QLogic QLA2100F adapter card:
Note: The following steps are an example of a configuration. The
configuration for your adapter might differ.
1. Install the QLogic QLA2100F adapter card in the host system.
2. Connect the cable to the ESS port.
3. Restart the server.
4. Press Alt+Q to get to the FAST!Util menu.
5. From the Configuration Settings menu, click Host Adapter Settings.
26
IBM SAN Implementation
6. From the Advanced Adapter Settings menu, press the Down Arrow to
highlight LUNs per target. Press Enter.
7. Press the Down Arrow to find and highlight 256. Press Enter.
8. Press Esc.
9. To save the changes, click Yes. Press Enter.
10.Restart the server.
1.8.2 Installing the QLogic QLA2200F adapter card
This section tells you how to attach an ESS to a Novell NetWare host system
with the QLogic QLA2200F adapter card. Single-and dual port Fibre Channel
interfaces with the QLogic QLA2200F adapter card support the following public
and private loop modes:





Target
Public initiator
Private initiator
Target and public initiator
Target and private initiator
Perform the following steps to install the QLogic QLA2200F adapter card:
Note: The following steps are an example of a configuration. The
configuration for your adapter might differ.
1. Install the QLogic QLA2200F adapter card in the host system.
2. Connect the cable to the ESS port.
3. Restart the server.
4. Press Alt+Q to get to the FAST!Util Command panel.
5. From the Configuration Settings menu, click Host Adapter Settings and set
the parameters and values from the Host Adapter Settings menu as follows:
a. Host adapter BIOS: Disabled
b. Frame size: 2048
c. Loop reset delay: 5 (minimum)
d. Adapter hard loop ID: Disabled
6. From the Advanced Adapter Settings menu, press the Down Arrow key to
highlight LUNs per target; then press Enter. Set the parameters and values
from the Advanced Adapter Settings menu as follows:
Chapter 1. Implementing Fibre Channel host adapter cards
27
a. Execution throttle: 240
b. Fast command posting: Enabled
c. >4 GB addressing: Disabled for 32 bit systems
d. LUNs per target: 0
e. Enable LIP reset: No
f. Enable LIP full login: No
g. Enable target reset: Yes
h. Login retry count: 20 (minimum)
i. Port down retry count: 20 (minimum)
j. Driver load RISC code: Enabled
k. Enable database updates: No
l. Disable database load: No
m. IOCB allocation: 256
n. Extended error logging: Disabled (might be enabled for debugging)
7. Press Esc to return to the Configuration Settings menu.
8. From the Configuration Settings menu, scroll down to Extended Firmware
Settings. Press Enter.
9. From the Extended Firmware Settings menu, scroll down to Connection
Options to open the Option and Type of Connection window.
10.Press Enter.
11.Select from one of the following options:
– 0: Loop only
– 1: Point-to-point
– 2: Loop preferred (If you cannot use arbitrated loop, then default to
point-to-point.)
– 3: Point-to point, otherwise loop (If you cannot use point-to-point, default
to arbitrated loop.)
Note: If you connect the ESS directly to the host system, the option you select
must match the port connections on the ESS.
12.Press Esc.
13.To save the changes, click Yes. Press Enter.
14.Restart the server.
28
IBM SAN Implementation
1.8.3 Loading the current Fibre Channel adapter driver
Perform the following steps to load the current driver onto the QLogic adapter
card.
1. Go to the following Web site:
www.qlc.com
2. From the home page, click Driver Download.
3. Click Drivers.
4. Click Fibre-Channel Adapter Drivers.
5. Click QLA2xxx drivers.
6. Click Novell NetWare.
7. Click QLogic Vx.xxx where V is the version and x.xxx is the version level of
the file name.
8. In the Save As window, find the current driver file, xxxxxxx.exe, where
xxxxxxx is the driver file name.
Note: We recommend that you save the file to a floppy diskette.
9. Click Save.
10.Close the Web site.
11.From your host system Start menu, click Run.
12.In the Run window, ensure that the drive letter in the field is the same as the
drive letter where you saved the xxxxxxx.exe file. If no drive letter appears,
type the letter of the drive where you saved the driver file.
13.Type the driver file name after x:, where x is the drive letter you specified to
save the file.
14.Type the directory name where you want to put the file. Click Zip.
15.Click OK to unzip the current driver file.
1.8.4 Installing the Fibre Channel adapter drivers
Perform the following steps to install the Fibre Channel adapter drivers.
1. From the NetWare server console, type nwconfig for NetWare 5.0 or 5.1 or
load install for NetWare 4.x.
2. Select Driver Options.
3. Select Configure Disk and Storage Device Drivers.
4. In the SCSI Adapters window, click the Drivers tab.
Chapter 1. Implementing Fibre Channel host adapter cards
29
5. Click “Select an additional driver.”
6. Press the Insert key.
7. Insert a floppy diskette with the QLogic drivers into the A:\ drive of the
NetWare server. Press Enter.
The available driver is displayed.
8. Select the driver for the QLogic card and press Enter.
9. Select Modify driver parameters and enter the slot number of the QLogic
card into the slot number parameter.
10.Set the Scan All Luns parameter to Yes.
11.Press Tab and select Save Parameters and Load Driver.
12.Exit the nwconfig or install utility.
13.If storage has already been assigned to the server from the ESS Specialist,
type SCAN FOR NEW DEVICES, SCAN ALL LUNS, and LIST DEVICES.
The ESS hosted volumes are displayed in the devices list. Create volumes using
the nwconfig utility if necessary.
1.8.5 ESS QLogic QLA2100F/2200F host adapter card
To configure the host adapter card, use the IBM TotalStorage ESS Specialist.
1.9 Sun FC host system attachment
This topic tells you how to change the Sun system kernel. Before you start, you
must meet several attachment requirements.
1.9.1 Attachment requirements
This section lists the requirements for attaching the ESS to your host system:
 Ensure that you have all the equipment you need.
 Ensure that there are enough Fibre Channel adapters installed in the server
to handle the total LUNS you want to attach. The maximum LUNs per adapter
in a Fibre Channel arbitrated loop topology is 50.
 Ensure that you have the documentation for your host system, and that the
IBM Enterprise Storage Server User’s Guide is on the compact disc that you
receive with the ESS.
30
IBM SAN Implementation
 Solaris 2.6, Solaris 7, and Solaris 8 require patches to ensure that the host
and the ESS function correctly. See Table 1-6 for the minimum revision level
that is required for each Solaris patch ID.
Table 1-6 Solaris 2.6, 7, and 8 minimum revision level patches for Fibre Channel
Solaris 2.6
Solaris 7
Solaris 8
105181-23 kernel update
106541-12 kernel update
108528-03 kernel update
105356-16 sd, ssd drivers
106924-06 isp driver
109524-02 ssd driver
105580-16 glm driver
106925-04 glm driver
109657-01 isp driver
105600-19 isp driver
107147-08 pci driver
108974-03 sd, uata drivers
Not applicable
107458-10 dad, sd, ssd,
uata drivers
Not applicable
 Review the Sun host SCSI adapter device driver installation and configuration
utility documents for additional Solaris patches that you might need.
 See the following Web site for details about the release level for your
operating system:
www.storage.ibm.com/hardsoft/products/ess/supserver.htm
Either you or an IBM service support representative (SSR) must perform the
following tasks to install and configure an ESS.
1. The IBM SSR installs the ESS by using the procedures in the IBM Enterprise
Storage Server Service Guide
2. Either you or an IBM SSR defines the Fibre Channel host system with the
worldwide port name identifiers.
3. Either you or an IBM SSR defines the Fiber Channel port configuration if you
did not do it during the installation of the ESS or Fibre Channel adapters.
Note: Use the information on the logical configuration work sheet in the IBM
Enterprise Storage Server Configuration Planner you should have previously
filled out.
Chapter 1. Implementing Fibre Channel host adapter cards
31
4. Either you or an IBM SSR configures the host system for the ESS by using
the instructions in your host system publications.
Note: The IBM Subsystem Device Driver does not support the Sun host
system in a clustering environment. To have failover protection on an open
system, the IBM Subsystem Device Driver requires a minimum of two Fibre
Channel adapters. The maximum number of Fibre Channel adapters
supported is 16 for a total of 16 Fibre Channel ports.
The two IBM Subsystem Device Drivers for Sun host systems support:
 Sun host hardware platforms limited to 32-bit mode and all Sun host
systems running Solaris 2.6.
 Sun host hardware platforms with 64-bit mode capabilities running Solaris
7 or Solaris 8.
1.9.2 Installing the Emulex LP8000 adapter card
This section tells you how to attach an ESS to a Windows NT host system with
the Emulex LP8000 adapter card. Single-and dual-port Fibre Channel interfaces
with the Emulex LP8000 adapter card support the following public and private
loop modes:





Target
Public initiator
Private initiator
Target and public initiator
Target and private initiator
The ESS supports increased connectivity with the use of Fibre Channel
(SCSI-FCP and FICON) directors. Specific details on status, availability, and
configuration options for the Fibre Channel directors supported by the ESS are
available on the Web site:
www.storage.ibm.com/hardsoft/products/ess/supserver.htm
Perform the following steps to install the adapter card:
1. Turn off and unplug the computer.
2. Remove the computer case.
3. Remove the blank panel from an empty PCI bus slot.
4. Insert the host adapter board into the empty PCI bus slot. Press firmly until
seated.
5. Secure the mounting bracket for the adapter to the case with the panel screw.
32
IBM SAN Implementation
6. Replace the computer case by tightening the screws on the case or use the
clamp to secure the cover.
1.9.3 Downloading the current Emulex Fibre Channel adapter driver
This section tells you how to install the Emulex driver:
1. Plug in and restart your host system.
2. Go to the following Web site:
www.emulex.com
3. From the left navigation menu for Quick Links, click Documentation, Drivers
and Software.
4. From the Fibre Channel menu, select the adapter model.
5. Click Drivers for Solaris.
6. Click SCSI/IP v4.xxx where xxx equals the level of the driver for Solaris.
7. Click Download Now for an Intel driver or Download Now for a SPARC
driver.
8. From the File Download window, click Save this file to disk.
9. Click OK.
10.In the Save As window, click Save.
A window that shows the progress of the download is displayed.
11.When the download completes, click Close.
Note: If you downloaded the driver file to a host system other than a Sun,
you must transfer the file to the Sun host system. Otherwise, go to
“Installing the Emulex LP8000 Fibre Channel adapter drivers”.
1.9.4 Installing the Fibre Channel adapter drivers
Perform the following steps to install the Fibre Channel adapter drivers:
1. Login as root.
2. Type emlxtemp to create a temporary directory.
3. Type cd emlxtemp to change the directory to the temporary directory. If you
are downloading the file from the FTP site or have the file on the CD-ROM, go
to step 5.
4. Type /etc/init.d/volmgt stop and then unmount /dev/fd to copy the tar file
from a floppy diskette
5. Copy or download the device driver file to the temporary directory.
Chapter 1. Implementing Fibre Channel host adapter cards
33
6. If the file is in the format of filename.tar.Z, type uncompress filename.tar.Z.
7. Type tar xvf lpfc-sparc.tar to “untar” the drive file from the temporary
directory.
8. Type pkgadd -d pwd to install the package.
Note: An installation script displays that prompts you to answer a number of
questions. For each question, enter the appropriate response. Or, press Enter
to each question to accept the default setting.
9. Specify the package number or press Enter to accept all packages.
10.Type y or n to answer the prompt that reads: Rebuild manual pages database
for section 7d [y,n?]:. If you typed y, go to step 11.
Note: Rebuilding the manual pages can take up to ten minutes. If you do not
want to build the manual pages, type n.You can run the command later.
11.At the prompt that reads Use IP networking over Fibre Channel [y,n?]: type y
or n. If you typed y, go to step 12.
12.Type the name of the network host name for the adapter.
Note: The network host name identifies the host adapter on a Fibre Channel
network and is associated with a unique IP address.
13.Edit the /etc/hosts file to add the IP address to the host name.
Note: If you have more than one adapter in the system, you must create a
hostname.lpfn#file for each adapter.
14.At the prompt that reads:
Do you want to continue with the installation of <lpfc>
Type y to proceed with the installation, or type n to undo all the settings and
end the installation.
15.At the prompt that reads:
Select package(s) you wish to process (or ’all’ to process all packages).
(default:all) [?,??,q ]:
Type q.
Note: We recommend that you configure the host adapter parameters before
you shut down and restart the host system.
16.At the system prompt, type shutdown to restart the host system.
17.Login as root.
34
IBM SAN Implementation
18.Update the parameter list. See Table 1-8 on page 42.
19.Restart the host system.
Note: You must restart your system twice if IP is enabled.
1.9.5 Installing the JNI PCI adapter card
This section tells you how to attach an ESS to a Sun host system with the JNI
PCI adapter card:
1. Perform the following steps to install the JNI PCI adapter card.
2. Turn off and unplug the computer.
3. Remove the computer case.
4. Remove the blank panel from an empty PCI bus slot.
5. Insert the host adapter board into the empty PCI bus slot. Press firmly until
seated.
6. Secure the mounting bracket for the adapter to the case with the panel screw.
7. Replace the computer case by tightening the screws on the case or use the
clamp to secure the cover.
1.9.6 Downloading the current JNI PCI Fibre Channel adapter driver
This section tells you how to download the JNI PCI Fibre Channel adapter driver:
1. Plug in and restart your host system.
2. Go to the following Web site:
www.jni.com
3. From the navigation menu at the top of the page, click Drivers.
4. From the menu for Locate Driver by Product, click FCI-1063.
5. From the menu for FCI-1063, find the section for Solaris -JNI. Click
fca-pci.pkg.
6. In the dialog box for File Download, click Save this file to disk. Click OK.
7. In the Save As dialog box, create a temporary folder.
8. Click Save.
9. When you click Save, a window displays that shows the progress of the
download.
10.When the download completes, click Close.
Chapter 1. Implementing Fibre Channel host adapter cards
35
11.If you downloaded the driver file from a Sun host system, go to Installing the
JNI PCI Fibre Channel adapter driver. If you downloaded the driver file from
a non-Sun host system, transfer the drive file to a Sun host system.
1.9.7 Installing the JNI PCI Fibre Channel adapter driver
Perform the following steps to install the JNI PCI Fibre Channel adapter drivers:
1. Go to the following Web site:
www.jni.com
2. From the navigation menu at the top of the page, click Drivers.
3. From the menu for Locate Driver by Product, click FCI-1063.
4. From the menu for FCI-1063, find the section for Solaris -JNI. Click
readme.txt.
5. Print the readme.txt file.
6. Follow the instructions in the readme.txt file to install the JNI PCI adapter
card.
7. Update the parameter list. See Table 1-7 on page 42.
8. Restart the host system.
1.9.8 Installing the JNI SBUS adapter card
This section tells you how to attach an ESS to a Sun host system with the JNI
SBUS adapter card.
Perform the following steps to install the JNI SBUS adapter card:
1. Turn off and unplug the computer.
2. Remove the computer case.
3. Remove the blank panel from an empty SBUS slot.
4. Insert the host adapter board into the empty SBUS slot. Press firmly until
seated.
5. Secure the mounting bracket for the adapter to the case with the panel screw.
6. Replace the computer case by tightening the screws on the case or use the
clamp to secure the cover.
36
IBM SAN Implementation
1.9.9 Downloading current JNI SBUS Fibre Channel adapter driver
This section tells you how to download the JNI SBUS Fibre Channel adapter
driver:
1. Plug in and restart your host system.
2. Go to the following Web site:
www.jni.com
3. From the navigation menu at the top of the page, click Drivers.
4. From the menu for Locate Driver by Product, click FC64-1063.
5. From the menu for FCI-1063, find the section for Solaris -JNI. Click fcw.pkg.
6. In the dialog box for File Download, click Save this file to disk. Click OK.
7. In the Save As dialog box, create a temporary folder.
8. Click Save.
9. When you click Save, a window displays that shows the progress of the
download.
10.When the download completes, click Close.
11.If you downloaded the driver file from a Sun host system, go to Installing the
JNI SBUS Fibre Channel adapter driver. If you downloaded the driver file
from a non-Sun host system, transfer the drive file to a Sun host system.
1.9.10 Installing the JNI SBUS Fibre Channel adapter driver
Perform the following steps to install the JNI SBUS Fibre Channel adapter
drivers.
1. Go to the following Web site:
www.jni.com
2. From the navigation menu at the top of the page, click Drivers.
3. From the menu for Locate Driver by Product, click FC64-1063.
4. From the menu for FC64-1063, find the section for Solaris -JNI. Click
readme.txt.
5. Print the readme.txt file.
6. Follow the instructions in the readme.txt file to install the JNI SBUS adapter
card.
7. Update the parameter list. See Table 1-7 on page 42.
8. Restart the host system.
Chapter 1. Implementing Fibre Channel host adapter cards
37
1.9.11 Installing the QLogic QLA2200F adapter card
This section tells you how to attach an ESS to a host system with the QLogic
QLA2200F adapter card. Single-and dual-port Fibre Channel interfaces with the
QLogic QLA2200F adapter card support the following public and private loop
modes:





Target
Public initiator
Private initiator
Target and public initiator
Target and private initiator
Perform the following steps to install the QLogic QLA2200F adapter card:
1. Install the QLogic QLA2200F adapter card in the host system.
2. Connect the cable to the ESS port.
3. Restart the server.
4. Press Alt+Q to get to the FAST!Util menu.
5. From the Configuration Settings menu, select Host Adapter Settings.
6. From the Host Adapter Settings menu, set the following parameters and
values:
a.
b.
c.
d.
Host adapter BIOS: Disabled
Frame size: 2048
Loop reset delay: 5 (minimum)
Adapter hard loop ID: Disabled
7. From the Advanced Adapter Settings menu, press the Down Arrow to
highlight LUNs per target. Press Enter. Set the parameters and values from
the Advanced Adapter Settings menu as follows:
a.
b.
c.
d.
e.
f.
Execution throttle: 100
Fast command posting: Enabled
>4 GB addressing: Disabled for 32 bit systems
LUNs per target: 0
Enable LIP reset: No
Enable LIP full login: No
Note: In a clustering environment, set Enable LIP full login to Yes.
g.
h.
i.
j.
k.
38
Enable target reset: Yes
Login retrycount: 20 (minimum)
Port down retrycount: 20 (minimum)
Driver load RISC code: Enabled
Enable database updates: No
IBM SAN Implementation
l. Disable database load: No
m. IOCB allocation: 256
n. Extended error logging: Disabled (might be enabled for debugging)
Note: The Enable LIP reset, Enable LIP full logon, and Enable target reset
parameters control the behavior of the adapter when Windows NT tries to do a
SCSI bus reset. You must perform a target reset to make cluster failovers
work.Use the SCSI bus device reset option to clear SCSI reservations.
8. Press Esc to return to the Configuration Settings menu.
9. From the Configuration Settings menu, scroll down to Extended Firmware
Settings. Press Enter.
10.From the Extended Firmware Settings menu, scroll down to Connection
Options to open the Option and Type of Connection window.
11.Select one of the following options:
a. 0: Loop only
b. 1: Point-to-point (preferred setting)
c. 2: Loop preferred (If you cannot use arbitrated loop, then default to
point-to-point)
d. 3: Point-to point, otherwise loop (If you cannot use point-to-point, default
to arbitrated loop).
Note: If you connect the ESS directly to the host system, the option you select
must match the port connections on the ESS. However, if you connect through
a switch, the options do not need to match the port connections because the
ESS is point-to-point. The appropriate HBA on the server must also support
point-to-point connection on a direct connection. Currently, disparate vendors
do not function properly in a direct point-to-point connection. This statement is
not true if you connect through a switch because the ESS is point-to-point.
12.Press Esc.
13.Save the changes. Highlight Yes.
14.Restart the server.
1.9.12 Downloading the current Fibre Channel adapter driver
Perform the following steps to load the current driver onto the QLogic adapter
card.
1. Go to the following Web site:
www.qlogic.com
Chapter 1. Implementing Fibre Channel host adapter cards
39
2. From the home page, click Driver Download.
3. Click Use QLogic Drivers.
4. Click Fibre Channel Adapter Drivers and Software.
5. In table, click QLA22xx drivers.
6. From the menu for Software and Drivers available for, click Solaris.
7. From the table for QLA22xx Driver Download Page, Solaris Sparc 2.6/2.7/2.8,
and Current released (Sparc) driver PCI to FC Adapter, click Link to Driver.
8. Download the file and save as required.
1.9.13 Installing the Fibre Channel adapter drivers
Perform the following steps to install the Fibre Channel adapter drivers.
Note: If you are installing the Fibre Channel adapter for the first time, you
must specify the correct topology. You must also select the appropriate device
mapping driver.
1. Go to the following Web site:
www.qlogic.com
2. From the home page, click Driver Download.
3. Click Use Qlogic Drivers button.
4. Click Fibre Channel Adapter Drivers and Software.
5. In the table for Qlogic Fibre Channel Adapters, click QLA22xx.
6. From the menu for Software and Drivers available for, click Solaris.
7. From the table for QLA22xx Driver Download Page, Solaris Sparc 2.6/2.7/2.8,
and Current released (Sparc) driver PCI to FC Adapter, click Read Me.
This action displays the contents of the Read Me file, which contains the
instructions to install the driver file.
8. Update the parameter file if necessary. See Table 1-9 on page 43.
1.9.14 Configuring host device drivers
The following procedures tell you how to update the Solaris SCSI driver
configuration file to enable access to target and LUN pairs configured on the
ESS.
40
IBM SAN Implementation
1. Change to the directory by typing: cd /kernel/drv
2. Back up the sd.conf file in this subdirectory.
3. Edit the sd.conf file to add support for the target and LUN pairs that are
configured on the host system. The following is an example of the lines that
you would add to the file to access LUNs 0-7 on target 8.
name="sd"class="scsi"
target=0 lun=0;
name="sd"class="scsi"
target=0 lun=1;
name="sd"class="scsi"
target=0 lun=2;
name="sd"class="scsi"
target=0 lun=3;
name="sd"class="scsi"
target=0 lun=4;
name="sd"class="scsi"
target=0 lun=5;
name="sd"class="scsi"
target=0 lun=6;
name="sd"class="scsi"
target=0 lun=7;
Note: Do not add duplicate target and LUN pairs.
Type reboot ---r from the Open Windows window to shut down and restart the
Sun host system with the kernel reconfiguration option, or type boot ---r from
the OK prompt after you shut down.
The Fibre Channel adapters that are supported for Sun attachment to the ESS
are capable of full fabric support. IBM recommends that all Fibre Channel driver
configurations include worldwide port name, worldwide node name, port ID, or
host-bus-adapter binding of target LUN pairs.
Binding of target LUN pairs implements the Solaris SCSI driver configuration file
or in the Fibre Channel host-bus-adapter configuration file installed by the
adapter software package. Refer to the vendor adapter documentation and
utilities for detailed configuration instructions.
1.9.15 Tuning HBA configuration files
Fibre Channel host-bus-adapter configuration files are tunable for host system
reliability and performance.
Chapter 1. Implementing Fibre Channel host adapter cards
41
See Table 1-7 for the recommended configuration settings for the
host-bus-adapter for a JNI FC64-1063 and a JNI FCI-1063.
Table 1-7 Recommended JNI HBA settings
Parameters
Recommended settings
fca_nport
0: Default. Initializes on a loop
1: Recommended for fabric. Initializes as an N_Port.
public loop
0: Default. Recommended. Initializes according to which
fca_nport is set as disabled.
ip_disable
0: Default. IP side of the driver is enabled.
1: Recommended for fabric. IP side of the adapters is
completely disabled.
failover
See the following Web site for details on how to set the
parameter setting:
www.storage.ibm.com/hardsoft/products/ess/supserver
.htm
busy_retry_delay
500: Recommended. Delay between retries after device
returns a busy response for a command.
scsi_probe_delay
5000: Recommended. Delay before SCSI probes are
allowed during startup.
See Table 1-8 for recommended host bus adapter configuration file parameters
for an Emulex LP8000 adapter
Table 1-8 Recommended Emulex LP8000 HBA settings.
42
Parameters
Recommended settings
automap
1: Default. Automatically assigns SCSI IDs to FCP targets.
fcp-on
1: Default. Turn on FCP.
lun-queue-depth
16: Recommended when there are less then 17 LUNs per
adapter. Set value = 256/(Total LUNs per adapter) when
there are more than 16 LUNs per adapter. If your
configuration includes more than one LP8000 adapter per
server, calculate the lun-queue-depth value using the
adapter with the most LUNs attached.
no-device-delay
15: Recommended.Delay to failback and I/O.
network-on
0: Default. Recommended for fabric. Do not turn on IP
networking
1: Turn on IP networking.
IBM SAN Implementation
Parameters
Recommended settings
scan-down
2: Recommended. Use inverted ALPA map and cause
target assignment in private loop.
topology
2: Recommended for fabric. Point-to-point mode only.
4: Recommended for non-fabric. Arbitrated loop mode only.
zone-rscn
0: Default
1: Recommended for fabric; check name server for RSCNs.
In Table 1-9 we show the recommended configuration file parameters for the host
bus adapters for the QLogic QLA2200F adapter.
Table 1-9 Recommended QLA2200F HBA settings
Parameters
Recommended settings
hba0-max-frame-length
2048
hba0-max-iocb-allocation
256
hba0-execution-throttle
31
hba0-login-timeout
4
hba0-login-retry-count
1
hba0-fabric-retry-count
10
hba0-enable-adapter-hard-loop
0
hba0-adapter-hard-loop-I
0
hba0-enable-64bit-addressing
0
hba0-enable-LIP-reset
0
hba0-enable-LIP-full-login
1
hba0-enable-target-reset
0: Non-clustered
1: Clustered
hba0-reset-delay
5
hba0-port-down-retry-count
30
hba0-link-down-error
1
hba0-loop-down-timeout
60
hba0-connection-options
1: Fabric connection
2: Direct connection
hba0-device-configuration-mode
1
hba0-fc-tape
0
hba0-command-completion-option
1
Chapter 1. Implementing Fibre Channel host adapter cards
43
1.9.16 Installing the IBM Subsystem Device Driver
The following instructions explain how to install the IBM Subsystem Device
Driver from a compact disc. You can use the IBM Subsystem Device Driver in
conjunction with the IBM Copy Services command-line interface program.
1. Type ps -ef |grep vold to ensure that the volume manager is running. This
command displays the /usr/sbin/vold process. If it does not display, type:
/etc/init.d/volmgt start
2. Insert the IBM Subsystem Device Driver CD into the CD-ROM drive. A File
Manager window opens showing the paths for the Subsystem Device Driver
package subdirectories.
Note: You must be on the host console to see this window.
3. Change to the subdirectory that contains the Subsystem Device Driver
package.
a. For Sun host hardware platforms limited to 32-bit mode and for all Sun
host systems running Solaris 2.6,type:
cd /cdrom/unnamed_cdrom/Sun32bit
b. For Sun host hardware platforms with 64-bit capabilities running Solaris 7
or Solaris 8,type:
cd /cdrom/unnamed_cdrom/Sun64bit
4. Type pkgadd -d to initiate the Package Add menu.
5. Select the option number for the IBM DPO driver (IBMdpo), and press Enter.
6. Select y to continue the installation for all prompts until the package
installation is complete.
7. Select q and press Enter to exit the package options menu.
8. Type cd to change back to the root directory.
9. Type eject cdrom and press Enter to remove the Subsystem Device Driver
CD.
Edit the profile file in the root directory and add the lines shown below to
include the IBM DPO subdirectory in the system path:
PATH=$PATH:/opt/IBMdpo/bin
export PATH
The IBM DPO driver subdirectory will be automatically added to the path when
the system is restarted.
44
IBM SAN Implementation
1.9.17 Setting the Sun host system parameters
The following sections contain the procedures to set the Sun host system
parameters for optimum performance on the ESS with the following adapters:
 JNI
 Emulex
 QLogic
JNI adapters
The following sections contain the procedures to set the Sun host system
parameters for optimum performance on the ESS with the JNI adapter:
1. Type cd /etc to change to the /etc subdirectory.
2. Back up the system file in the subdirectory.
3. Edit the system file and set the following parameters for servers with
configurations that use JNI adapters:
sd_max_throttle
This sd_max_throttle parameter specifies the maximum number of
commands that the sd driver can queue to the host bus adapter driver. The
default value is 256, but you must set the parameter to a value less than or
equal to a maximum queue depth for each LUN connected. Determine the
value using the following formula:
256/(LUNs per adapter)
The parameter shows thirty two 2105 LUNs attached to controller 1, (c1t#d#),
and forty eight 2105 LUNs attached to controller 2, (c2t#d#). The value for
sd_max_throttle is calculated using the controller with the highest number of
LUNs attached. The sd_max_throttle parameter for the ESS LUNs in this
example would be set by adding the following line to the /etc/system file:
set sd:sd_max_throttle=5
sd_io_time
This parameter specifies the timeout value for disk operations. Add the
following lines to the /etc/system file to set the sd_io_time parameter for the
ESS LUNs:
set sd:sd:_io_time=0x78
sd_retry_count
This parameter specifies the retry count for disk operations. Add the following
line to the /etc/system file to set the sd_retry_count parameter for the ESS
LUNs:
set sd:sd_retry_count=5
Chapter 1. Implementing Fibre Channel host adapter cards
45
maxphys
This parameter specifies the maximum number of bytes you can transfer for
each SCSI transaction. The default value is 126976 (124 KB). If the I/O block
size that you requested exceeds the default value, the request is broken into
more than one request. The value should be tuned to the intended use and
application requirements. For maximum bandwidth set the maxphys
parameter by adding the following line to the /etc/system file:
set maxphys=8388608
If you are using Veritas volume manager on the ESS LUNs, you must set the
VxVM max I/O size parameter (vol_maxio) to match the maxphys parameter.
If you set the maxphys parameter to 8388608, add the following line to the
/etc/system file to also set the VxVM I/O size to 8 MB:
set vxio:vol_maxio=16384
Emulex or QLogic adapters
The following sections contain the procedures to set the Sun host system
parameters for optimum performance on the ESS with the Emulex adapter:
1. Type cd /etc to change to the /etc subdirectory.
2. Back up the system file in the subdirectory.
3. Edit the system file and set the following parameters for servers with
configurations that only use Emulex adapters.
sd_io_time
This parameter specifies the timeout value for disk operations. Add the
following line to the /etc/system file to set the sd_io_time parameter for the
ESS LUNs:
set sd:sd:_io_time=0x78
sd_retry_count
This parameter specifies the retrycount for disk operations. Add the following
line to the /etc/system file to set the sd_retry_count parameter for the ESS
LUNs:
set sd:sd_retry_count=5
maxphys
This parameter specifies the maximum number of bytes you can transfer for
each SCSI transaction. The default value is 126976 (124 KB). If the I/O block
size that you requested exceeds the default value, the request is broken into
more than one request. The value should be tuned to the intended use and
application requirements. For maximum bandwidth, set the maxphys
parameter by adding the following line to the /etc/system file:
46
IBM SAN Implementation
set maxphys=8388608
If you are using Veritas volume manager on the ESS LUNs, you must set the
VxVM max I/O size parameter (vol_maxio) to match the maxphys parameter.
If you set the maxphys parameter to 8388608, add the following line to the
/etc/system file to also set the VxVM I/O size to 8 MB:
set vxio:vol_maxio=16384
1.10 Windows NT 4.0 FC host system attachment
In this topic we tell you how to attach an ESS to a Windows NT host system with
the following Fibre Channel adapters.
 QLogic QLA2100F adapter card
 QLogic QLA2200F adapter card
 Emulex LP8000 adapter card
This topic also tells you how to install, download, and configure the adapter
cards.
1.10.1 Attachment requirements
This section lists the requirements for attaching the ESS to your host system:
 Check the LUN limitations for your host system.
 Ensure that you have the documentation for your host system and the
IBM Enterprise Storage Server User’s Guide (the User’s Guide is on the
compact disc that you receive with the ESS).
 See the following Web site for details about the release level for your
operating system:
www.storage.ibm.com/hardsoft/products/ess/supserver.htm
Either you or an IBM SSR must perform the following tasks to install and
configure an ESS.
1. The IBM SSR installs the ESS by using the procedures in the IBM Enterprise
Storage Server Service Guide
2. Either you or an IBM SSR defines the Fibre Channel host system with the
worldwide port name identifiers.
Chapter 1. Implementing Fibre Channel host adapter cards
47
3. Either you or an IBM SSR defines the Fiber Channel port configuration if you
did not do it during the installation of the ESS or Fibre Channel adapters.
Note: Use the information on the logical configuration work sheet in the IBM
Enterprise Storage Server Configuration Planner that you should have
previously filled out.
You or an IBM SSR configures the host system for the ESS by using the
instructions in your host system publications.
Notes:
1. The IBM Subsystem Device Driver 1.2.1 supports the Windows NT 4.0
host system in a clustering environment. To have failover protection on an
open system, the IBM Subsystem Device Driver requires a minimum of two
Fibre Channel adapters. The maximum number of Fibre Channel adapters
supported is 16 for a total of 16 Fibre Channel ports.
2. To improve performance, IBM recommends that you map to the LUNs for
the target volumes of the Windows NT host until you need access to the
data on the target volume. Perform the LUN mapping after the PPRC
operation and immediately before you need access to the data. You must
restart the host system before you can access the data on the target
volume. You can greatly reduce the time it takes for the host system to
restart if you perform the LUN mapping. Otherwise, the time to reboot could
take 10 minutes per PPRC target volume.
1.10.2 Installing the QLogic QLA2100F adapter card
This section tells you how to attach an ESS to a Windows NT host system with
the QLogic QLA2100F adapter card. Single-port Fibre Channel interfaces with
the QLogic QLA2100F adapter card support the following loop modes:
 Target
 Initiator
 Target and initiator
Notes:
1. The arbitrated loop topology is the only topology available for the QLogic
QLA2100F adapter card.
2. When you install the QLA2100F adapter card on your host system, IBM
recommends that you install the card on a host system with four
processors. This ensures that you do not have a problem when you start
the host system.
48
IBM SAN Implementation
Perform the following steps to install the QLogic QLA2100F adapter card:
1. Install the QLogic QLA2100F adapter card in the host system.
2. Connect the cable to the ESS port.
3. Restart the host system.
4. Press Alt+Q to get to the FAST!Util menu.
5. From the Configuration Settings menu, select Host Adapter Settings.
6. From the Advanced Adapter Settings menu, press the Down Arrow to
highlight LUNs per target; then press Enter.
7. Use the Down Arrow to find and highlight 256. Press Enter.
8. Press Esc.
9. To save the changes, click Yes. Press Enter.
10.Restart the server.
1.10.3 Installing the QLogic QLA2200F adapter card
This section tells you how to attach an ESS to a Windows NT host system with
the QLogic QLA2200F adapter card. Single-and dual-port Fibre Channel
interfaces with the QLogic QLA2200F adapter card support the following public
and private loop modes:





Target
Public initiator
Private initiator
Target and public initiator
Target and private initiator
Perform the following steps to install the QLogic QLA2200F adapter card:
1. Install the QLogic QLA2200F adapter card in the host system.
2. Connect the cable to the ESS port.
3. Restart the server.
4. Press Alt+Q to get to the FAST!Util menu.
5. From the Configuration Settings menu, select Host Adapter Settings.
6. From the Host Adapter Settings menu, set the following parameters and
values:
a.
b.
c.
d.
Host adapter BIOS: Disabled
Frame size: 2048
Loop reset delay: 5 (minimum)
Adapter hard loop ID: Disabled
Chapter 1. Implementing Fibre Channel host adapter cards
49
7. From the Advanced Adapter Settings menu, press the Down Arrow to
highlight LUNs per target. Press Enter. Set the parameters and values from
the Advanced Adapter Settings menu as follows:
a.
b.
c.
d.
e.
f.
Execution throttle: 100
Fast command posting: Enabled
>4 GB addressing: Disabled for 32 bit systems
LUNs per target: 0
Enable LIP reset: No
Enable LIP full login: No
Note: In a clustering environment, set Enable LIP full login to Yes.
g.
h.
i.
j.
k.
l.
m.
n.
Enable target reset: Yes
Login retrycount: 20 (minimum)
Port down retrycount: 20 (minimum)
Driver load RISC code: Enabled
Enable database updates: No
Disable database load: No
IOCB allocation: 256
Extended error logging: Disabled (might be enabled for debugging)
Note: The Enable LIP reset, Enable LIP full logon, and Enable target reset
parameters control the behavior of the adapter when Windows NT tries to do a
SCSI bus reset. You must perform a target reset to make cluster failovers
work. Use the SCSI bus device reset option to clear SCSI reservations.
8. Press Esc to return to the Configuration Settings menu.
9. From the Configuration Settings menu, scroll down to Extended Firmware
Settings. Press Enter.
10.From the Extended Firmware Settings menu, scroll down to Connection
Options to open the Option and Type of Connection window.
11.Select one of the following options:
a. 0: Loop only
b. 1: Point-to-point (preferred setting)
c. 2: Loop preferred (If you cannot use arbitrated loop, then default to
point-to-point)
d. 3: Point-to point, otherwise loop (If you cannot use point-to-point, default
to arbitrated loop).
50
IBM SAN Implementation
Note: If you connect the ESS directly to the host system, the option you select
must match the port connections on the ESS. However, if you connect through
a switch, the options do not need to match the port connections because the
ESS is point-to-point. The appropriate HBA on the server must also support
point-to-point connection on a direct connection. Currently, disparate vendors
do not function properly in a direct point-to-point connection. This statement is
not true if you connect through a switch because the ESS is point-to-point.
12.Press Esc.
13.Save the changes. Highlight Yes.
14.Restart the server.
1.10.4 Downloading the current Fibre Channel adapter driver
Perform the following steps to load the current driver onto the QLogic adapter
card:
1. Go to the following Web site:
www.qlogic.com
2. From the home page, click Driver Download.
3. Click Use QLogic Drivers.
4. Click IBM Enterprise Subsystems Division approved drivers.
5. Click IBM Approved QLA22xx drivers or IBM Approved QLA21xx drivers.
6. Click Link to Driver for Windows NT.
7. In the window for File Download, click Save this Program to Disk.
8. Insert a floppy diskette into your floppy disk drive.
9. In the field for Save in, change the drive letter to A:\
10.Create a folder called Temp in the Save As window.
11.Click Save.
12.When the download completes, click Open Folder.
13.From the A:\ window, double-click the icon for the driver file you downloaded
to the floppy diskette.
14.In the window for WinZip Self-Extractor, type a:\
15.Click Unzip.
When the unzip process completes, you should see a message that says, x
files unzipped successfully, where x equals the number of files you unzipped.
Chapter 1. Implementing Fibre Channel host adapter cards
51
16.Click OK.
17.Click Close to close the window for WinZip Self-Extractor.
1.10.5 Installing the Fibre Channel adapter drivers
Perform the following steps to install the Fibre Channel adapter drivers.
Note: If you are installing the Fibre Channel adapter for the first time, you must
specify the correct topology. You must also select the appropriate device
mapping driver.
1. From your Windows NT desktop, double-click the icon for My Computer.
2. Double-click the icon for Control Panel.
3. Double-click the icon for SCSI Adapters.
4. In the SCSI Adapters window, click the Drivers tab.
5. Click Add.
6. In the Install Drivers window, click Have Disk.
7. In the Install from Disk window, ensure that the drive letter in the field for Copy
Manufacturer’s Files From is the drive letter you specified to save the .exe file
to when you downloaded the driver previously.
8. Type the name of the current driver file in the field for Copy Manufacturer’s
Files From after the drive letter prompt.
9. Click OK.
10.Click Cancel to exit.
11.Restart your host system.
1.10.6 QLogic QLA2100F or QLogic QLA2200F configuration
To configure the host adapter card, use the IBM TotalStorage ESS Specialist.
1.10.7 Configuring for availability and recoverability
This section describes how to ensure optimum availability and recoverability
when you attach an IBM ESS to a Windows NT host system. You must set the
time-out value associated with the supported host bus adapters to 240 seconds.
The setting is consistent with the configuration for IBM SSA adapters and disk
subsystems when attached to a Windows NT host system.
52
IBM SAN Implementation
The host bus adapter uses the time-out parameter to bound its recovery actions
and responses to the disk subsystem. The value exists in different places in the
system configuration. You can retrieve and use it in different ways, depending on
the type of host bus adapter. The following instructions tell you how to modify the
value safely in either the Windows NT registry or in the device adapter
parameters.
1.10.8 Setting the TimeOutValue registry
The following instructions tell you how to set the time-out value registry:
1. From the Run menu or command prompt, type:
Regedt32.exe
2. Navigate to the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Disk
3. Look for the value called TimeOutValue. If the value called TimeOutValue
does not exist, go to step 3a. If the TimeOutValue exists, go to step 4.
a.
b.
c.
d.
e.
f.
g.
Click Edit ->Add Value...
For ValueName, click TimeOutValue.
For data type, click REG_DWORD.
Click OK.
For data, click f0.
For radix, click Hex.
Click OK.
4. If the value exists and is less than 0x000000f0 (240 decimal), perform the
following steps to increase it to 0xf0:
a.
b.
c.
d.
e.
Click TimeOutValue.
Click Edit ->DWORD...
For data, click f0.
For radix, click hex.
Click OK.
5. Exit the Regedt32 program.
6. Restart your Windows NT server for the changes to take effect.
1.10.9 Installing Emulex LP8000 adapter cards
This section tells you how to attach an ESS to a Windows NT host system with
Emulex LP8000 adapter cards. Single-and dual-port Fibre Channel interfaces
with the Emulex LP8000 adapter cards support the following public and private
loop modes:
Chapter 1. Implementing Fibre Channel host adapter cards
53





Target
Public initiator
Private initiator
Target and public initiator
Target and private initiator
The ESS supports increased connectivity with the use of Fibre Channel
(SCSI-FCP and FICON) directors. Specific details on status, availability, and
configuration options for the Fibre Channel directors supported by the ESS are
available on the Web:
www.storage.ibm.com/hardsoft/products/ess/supserver.htm
Perform the following steps to install the Emulex LP8000 adapter card:
1. Turn off and unplug the computer.
2. Remove the computer case.
3. Remove the blank menu from an empty PCI bus slot.
4. Insert the host adapter board into the empty PCI bus slot. Press firmly until
seated.
5. Secure the mounting bracket for the adapter to the case with the panel screw.
6. Replace the computer case by tightening the screws on the case or use the
clamp to secure the cover.
1.10.10 Downloading the current Fibre Channel adapter driver
This section tells you how to install the port driver:
1. Plug in and restart your host system.
2. Go to the following Web site:
www.emulex.com
3. From the Quick Links menu, click Documentation, Drivers, and Software.
4. Click the host adapter type from the host adapter menu.
5. Click Drivers for Windows NT.
6. Click Specialized Drivers.
7. Click Fibre Channel Port xxxxx where xxxxx is the name of the adapter
driver.
8. Click the Download Now button.
54
IBM SAN Implementation
9. From the File Download window, click the appropriate radio button and
proceed as indicated:
– To open this file from its current location, go to step 9.
– To save this file to disk, go to step 16.
10.In the window for Winzip, click I agree.
11.In the window for WinZip Wizard - Welcome, click Next.
12.In the window for WinZip Wizard - Select Zip File xxxxxxxx.zip, where
xxxxxxxx is the name of the file, highlight the file that you want to unzip.
13.Click Next.
14.In the window for WinZip Wizard - Unzip, click Unzip now.
A progress indicator window appears when the operation to unzip the file
completes. A window opens to display the following file names:
–
–
–
–
–
Lpscsi
Lputilnt
Oemsetup
Readme
Txtsetup.oem
15.Double-click Readme to get the instructions to install the Fibre Channel
adapter driver. Print the Readme file.
16.In the window for WinZip Wizard -Unzip Complete, click Close.
17.Ensure that the name of the file you want to download is displayed in the
window.
18.Click Save to download and unzip the file to your hard drive.
A window opens that indicates the progress of the download operation. When the
progress indicator window closes, the download is complete.
1.10.11 Installing the Fibre Channel adapter drivers
Perform the following steps to install the Fibre Channel adapter drivers.
Note: If you are installing the Fibre Channel adapter for the first time, you must
specify the correct topology. You must also select the appropriate device
mapping driver.
1. From your desktop, click Start Settings.
2. Double-click Control Panel.
3. Double-click SCSI Adapters.
4. Click the Drivers tab.
Chapter 1. Implementing Fibre Channel host adapter cards
55
5. Click Add to create a list of drivers.
A window opens that indicates the progress. When the window closes, you
should see a window called Install Driver.
6. From the Install Driver window, click Have Disk.
7. Enter the path to the driver file that you downloaded and click OK.
8. To install the driver, highlight the line that lists the driver you want and click
OK.
Note: The driver affects every adapter in the system. If you have more than
one adapter that requires different parameter settings, you must change the
parameter settings with the port utility and restart your host system.
9. Click Yes to restart the host system.
10.After you restart your host system, click Start Settings.
11.Double-click Control Panel.
12.Double-click SCSI Adapters.
13.Click the Drivers tab and verify that the Emulex SCSI driver is present and
started.
14.Click the Devices tab and verify that the host adapter is on the list.
1.10.12 Parameter settings for the Emulex LP8000 on Windows NT
In Table 1-10 we show the recommended host bus adapter configuration file
parameters for an Emulex LP8000 adapter. The settings are for an IBM ESS
model F20 that is attached through a switch using the fabric, automap SCSI
devices port driver, and an IBM ESS model F20 that is attached directly, using
arbitrated loop, automap SCSI devices port driver.
Table 1-10 Recommended LP8000 settings for NT
56
Parameters
Recommended settings
Automatically map SCSI devices
Checked (enabled)
Query name server for all N-ports
Checked (enabled)
Allow multiple paths to SCSI targets
Checked (enabled)
Point-to-point
Not checked (disabled) for direct attach
Not shown for the fabric attach
Register for state change
Checked (enabled)
Use report LUNs
Checked (enabled)
IBM SAN Implementation
Parameters
Recommended settings
Use name server after RSCN
Checked (enabled) if fabric attached using
soft zoning
Not checked (disabled)
Lun mapping
Checked (enabled)
Automatic lun mapping
Checked (enabled)
Scan in device ID order
Not checked (disabled)
Enable class 2 for SCSI devices
Not checked (disabled)
Report unknown SCSI devices
Not checked (disabled)
Look for disappearing devices
Not checked (disabled)
Translate queue full to busy
Not checked (disabled)
Use bus reset status for retries
Not checked (disabled)
Retry unit attention
Not checked (disabled)
Retry PLOGI open failures
Not checked (disabled)
Maximum Number of LUNs
Equal to or greater than the number of the
ESS LUNs available to the host bus
adapter
Maximum Queue Depth
8
Link Timer
30 seconds
Retries
64
E_D_TOV
2000 milliseconds
AL_TOV
15 milliseconds
Wait ready timer
45 seconds
Retry timer
2000 milliseconds
R_A_TOV
2 seconds
ARB_TOV
1000 milliseconds
Link Control
Not shown for direct attach
Topology
Point-to-point (fabric)
Arbitrated loop (direct connect)
Link speed
Auto
Chapter 1. Implementing Fibre Channel host adapter cards
57
1.10.13 Verifying the configuration
The following tells you how to determine whether or not your Windows NT 4.0
host system is configured for storage:
1. From the Windows NT desktop, right-click Start.
2. Partition new Fibre Channel drives with Microsoft Disk Administrator. See
your Windows NT documentation for more instructions.
3. Click Explore and verify that you can see the Fibre Channel drives.
4. Select a large file (for example, a 9 MB file), and copy it to a Fibre Channel
drive.
1.10.14 Verifying networking
The following tells you how to determine whether or not your Windows NT 4.0
host system is configured for networking:
1. From the Windows NT desktop, click Start Programs Command Prompt.
2. From the command line, ping a known TCP/IP address.
1.11 Windows 2000 FC host system attachment
This topic tells you how to attach an ESS to a Windows 2000 host system with
the following Fibre Channel adapters.
 QLogic QLA2100F adapter card
 QLogic QLA2200F adapter card
 Emulex LP8000 adapter card
1.11.1 Attachment requirements
This section lists the requirements for attaching the ESS to your host system:
 Check the LUN limitations for your host system.
 Ensure that you have the documentation for your host system and the
IBM Enterprise Storage Server User’s Guide (the User’s Guide is on the
compact disc that you receive with the ESS).
See the following Web site for details about the release level for your
operating system:
www.storage.ibm.com/hardsoft/products/ess/supserver.htm
58
IBM SAN Implementation
Either you or an IBM SSR must perform the following tasks to install and
configure an ESS:
1. The IBM SSR installs the ESS by using the procedures in the IBM Enterprise
Storage Server Service Guide
2. You or an IBM SSR defines the Fibre Channel host system with the worldwide
port name identifiers.
3. You or an IBM SSR defines the Fiber Channel port configuration if you did not
do it during the installation of the ESS or Fibre Channel adapters. For the list
of worldwide port names, see 1.12, “Locating the worldwide port name” on
page 69.
Note: Use the information on the logical configuration work sheet in the IBM
Enterprise Storage Server Configuration Planner that you should have
previously filled out.
4. Either you or an IBM SSR configures the host system for the ESS by using
the instructions in your host system publications.
Note:
1. The IBM Subsystem Device Driver 1.2.1 does not support the Windows
2000 host system in a clustering environment. To have failover protection
on an open system, the IBM Subsystem Device Driver requires a minimum
of two Fibre Channel adapters. The maximum number of Fibre Channel
adapters supported is 16 for a total of 16 Fibre Channel ports.
2. To improve performance, IBM recommends that you map to the LUNs for
the target volumes of the Windows 2000 host until you need access to the
data on the target volume. Perform the LUN mapping after the PPRC
operation and immediately before you need access to the data. You must
restart the host system before you can access the data on the target
volume. You can greatly reduce the time it takes for the host system to
restart if you perform the LUN mapping. Otherwise, the time to restart could
take 10 minutes per PPRC target volume.
1.11.2 Installing the QLogic QLA2100F adapter card
This section tells you how to attach an ESS to a Windows NT host system with
the QLogic QLA2100F adapter card. Single-port Fibre Channel interfaces with
the QLogic QLA2100F adapter card support the following loop modes:
 Target
 Initiator
 Target and initiator
Chapter 1. Implementing Fibre Channel host adapter cards
59
Note:
1. The arbitrated loop topology is the only topology available for the QLogic
QLA2100F adapter card.
2. When you install the QLA2100F adapter card on your host system,
IBM recommends that you install the card on a host system with four
processors. This ensures that you do not have a problem when you start
the host system.
Perform the following steps to install the QLogic QLA2100F adapter card:
1. Install the QLogic QLA2100F adapter card in the host system.
2. Connect the cable to the ESS port.
3. Restart the host system.
4. Press Alt+Q to get to the FAST!Util menu.
5. From the Configuration Settings menu, select Host Adapter Settings.
6. From the Advanced Adapter Settings menu, press the Down Arrow to
highlight LUNs per target and then press Enter.
7. Use the Down Arrow to find and highlight 256. Press Enter.
8. Press Esc.
9. To save the changes, click Yes. Press Enter.
10.Restart the server.
1.11.3 Installing the QLogic QLA2200F adapter card
This section tells you how to attach an ESS to a Windows 2000 host system with
the QLogic QLA2200F adapter card. Single-and dual-port Fibre Channel
interfaces with the QLogic QLA2200F adapter card support the following public
and private loop modes:





Target
Public initiator
Private initiator
Target and public initiator
Target and private initiator
Perform the following steps to install the QLogic QLA2200F adapter card:
1. Install the QLogic QLA2200F adapter card in the host system.
2. Connect the cable to the ESS port.
3. Restart the server.
60
IBM SAN Implementation
4. Press Alt+Q to get to the FAST!Util menu.
5. From the Configuration Settings menu, select Host Adapter Settings.
6. From the Host Adapter Settings menu, set the following parameters and
values:
a. Host adapter BIOS: Disabled
b. Frame size: 2048
c. Loop reset delay: 5 (minimum)
d. Adapter hard loop ID: Disabled
7. From the Advanced Adapter Settings menu, press the Down Arrow to
highlight LUNs per target. Press Enter. Set the parameters and values from
the Advanced Adapter Settings menu as follows:
a. Execution throttle: 100
b. Fast command posting: Enabled
c. >4 GB addressing: Disabled for 32 bit systems
d. LUNs per target: 0
e. Enable LIP reset: No
f. Enable LIP full login: No
Note: In a clustering environment, set Enable LIP full login to Yes.
g. Enable target reset: Yes
h. Login retrycount: 20 (minimum)
i. Port down retrycount: 20 ((minimum)
j. Driver load RISC code: Enabled
k. Enable database updates: No
l. Disable database load: No
m. IOCB allocation: 256
n. Extended error logging: Disabled (might be enabled for debugging)
Note: The Enable LIP reset, Enable LIP full logon, and Enable target reset
parameters control the behavior of the adapter when Windows NT tries to do a
SCSI bus reset. You must perform a target reset to make cluster failovers
work.Use the SCSI bus device reset option to clear SCSI reservations.
8. Press Esc to return to the Configuration Settings menu.
9. From the Configuration Settings menu, scroll down to Extended Firmware
Settings. Press Enter.
Chapter 1. Implementing Fibre Channel host adapter cards
61
10.From the Extended Firmware Settings menu, scroll down to Connection
Options to open the Option and Type of Connection window.
11.Select one of the following options:
a. 0: Loop only
b. 1: Point-to-point (preferred setting)
c. 2: Loop preferred (If you cannot use arbitrated loop, then default to
point-to-point)
d. 3: Point-to point, otherwise loop (If you cannot use point-to-point, default
to arbitrated loop).
Note: If you connect the ESS directly to the host system, the option you select
must match the port connections on the ESS. However, if you connect through
a switch, the options do not need to match the port connections because the
ESS is point-to-point. The appropriate HBA on the server must also support
point-to-point connection on a direct connection. Currently, disparate vendors
do not function properly in a direct point-to-point connection. This statement is
not true if you connect through a switch because the ESS is point-to-point.
12.Press Esc.
13.Save the changes. Highlight Yes.
14.Restart the server.
1.11.4 Downloading the current Fibre Channel adapter driver
Perform the following steps to load the current driver onto the QLogic adapter
card.
1. Go to the following Web site:
www.qlogic.com
2. From the home page, click Driver Download.
3. Click Use QLogic Drivers.
4. Click IBM Enterprise Subsystems Division approved drivers.
5. Click IBM Approved QLA22xx drivers or IBM Approved QLA21xx drivers.
6. Click Link to Drivers.
7. In the window for File Download, click Save this Program to Disk.
8. Insert a floppy diskette into your floppy disk drive.
9. In the field for Save in, change the drive letter to A:\
10.Create a folder called Temp in the Save As window.
62
IBM SAN Implementation
11.Click Save.
12.When the download completes, click Open Folder.
13.From the A:\ window, double-click the icon for the driver file you downloaded
to the floppy diskette.
14.In the window for WinZip Self-Extractor, type a:\
15.Click Unzip.
When the unzip process completes, you should see a message that says, x
files unzipped successfully, where x equals the number of files you unzipped.
16.Click OK.
17.Click Close to close the window for WinZip Self-Extractor.
1.11.5 Installing the Fibre Channel adapter drivers
Perform the following steps to install the Fibre Channel adapter drivers.
Note: If you are installing the Fibre Channel adapter for the first time, you must
specify the correct topology. You must also select the appropriate device
mapping driver.
1. From your Windows 2000 desktop, double-click the icon for My Computer.
2. Double-click the icon for Control Panel.
3. Double-click the icon for SCSI Adapters.
4. In the SCSI Adapters window, click the Drivers tab.
5. Click Add.
6. In the Install Drivers window, click Have Disk.
7. In the Install from Disk window, ensure that the drive letter in the field for Copy
Manufacturer’s Files From is the drive letter you specified to save the .exe file
to when you downloaded the driver previously.
8. Type the name of the current driver file in the field for Copy Manufacturer’s
Files From after the drive letter prompt.
9. Click OK.
10.Click Cancel to exit.
11.Restart your host system.
1.11.6 QLogic QLA2100F or QLogic QLA2200F configuration
To configure the host adapter card, use the IBM TotalStorage ESS Specialist.
Chapter 1. Implementing Fibre Channel host adapter cards
63
1.11.7 Configuring for availability and recoverability
This section describes how to ensure optimum availability and recoverability
when you attach an IBM ESS to a Windows 2000 host system. You must set the
time-out value associated with the supported host bus adapters to 240 seconds.
The setting is consistent with the configuration for IBM SSA adapters and disk
subsystems when attached to Windows 2000 host system.
The host bus adapter uses the time-out parameter to bound its recovery actions
and responses to the disk subsystem. The value exists in different places in the
system configuration. You can retrieve and use it in different ways depending on
the type of host bus adapter. The following instructions tell you how to modify the
value safely in either the Windows 2000 registry or in the device adapter
parameters.
1.11.8 Setting the TimeOutValue registry
The following instructions tell you how to set the time-out value registry:
1. From the Run menu or command prompt, type:
Regedt32.exe
2. Navigate to the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Disk
3. Look for the value called TimeOutValue. If the value called TimeOutValue
does not exist, go to step 3a. If the TimeOutValue exists, go to step 4.
a.
b.
c.
d.
e.
f.
g.
Click Edit ->Add Value...
For ValueName, click TimeOutValue.
For data type, click REG_DWORD.
Click OK.
For data, click f0.
For radix, click Hex.
Click OK.
4. If the value exists and is less than 0x000000f0 (240 decimal), perform the
following steps to increase it to 0xf0:
a.
b.
c.
d.
e.
Click TimeOutValue.
Click Edit ->DWORD...
For data, click f0.
For radix, click hex.
Click OK.
5. Exit the Regedt32 program.
6. Restart your Windows 2000 server for the changes to take effect.
64
IBM SAN Implementation
1.11.9 Installing Emulex LP8000 adapter cards
This section tells you how to attach an ESS to a Windows 2000 host system with
Emulex LP8000 adapter cards. Single-and dual-port Fibre Channel interfaces
with the Emulex LP8000 adapter cards support the following public and private
loop modes:





Target
Public initiator
Private initiator
Target and public initiator
Target and private initiator
The ESS supports increased connectivity with the use of Fibre Channel
(SCSI-FCP and FICON) directors. Specific details on status, availability, and
configuration options for the Fibre Channel directors supported by the ESS are
available on the Web:
www.storage.ibm.com/hardsoft/products/ess/supserver.htm
Perform the following steps to install the Emulex LP8000 adapter card:
1. Turn off and unplug the computer.
2. Remove the computer case.
3. Remove the blank menu from an empty PCI bus slot.
4. Insert the host adapter board into the empty PCI bus slot. Press firmly until
seated.
5. Secure the mounting bracket for the adapter to the case with the panel screw.
6. Replace the computer case by tightening the screws on the case, or use the
clamp to secure the cover.
1.11.10 Downloading the current Fibre Channel adapter driver
This section tells you how to install the port driver.
1. Plug in and restart your host system.
2. Go to the following Web site:
www.emulex.com
3. From the Quick Links menu, click Documentation, Drivers, and Software.
4. Click the host adapter type from the host adapter menu.
5. Click Drivers for Windows 2000.
6. Click Fibre Channel Port v5-1.27a5.
7. Click the Download Now button.
Chapter 1. Implementing Fibre Channel host adapter cards
65
8. From the File Download window, click the appropriate radio button and
proceed as indicated:
– To open this file from its current location, go to step 9.
– To save this file to disk, go to step 16.
9. In the window for Winzip, click I agree.
10.In the window for WinZip Wizard - Welcome, click Next.
11.In the window for WinZip Wizard - Select Zip File xxxxxxxx.zip where
xxxxxxxx is the name of the file, highlight the file that you want to unzip.
12.Click Next.
13.In the window for WinZip Wizard - Unzip, click Unzip now.
A progress indicator window appears when the operation to unzip the file
completes. A window opens to display the following file names:
–
–
–
–
–
Lpscsi
Lputilnt
Oemsetup
Readme
Txtsetup.oem
14.Double-click Readme to get the instructions to install the Fibre Channel
adapter driver. Print the Readme file.
15.In the window for WinZip Wizard -Unzip Complete, click Close.
16.Ensure that the name of the file you want to download is displayed in the
window.
17.Click Save to download and unzip the file to your hard drive.
A window opens that indicates the progress of the download operation. When the
progress indicator window closes, the download is complete.
1.11.11 Installing the Fibre Channel adapter drivers
Perform the following steps to install the Fibre Channel adapter drivers.
Note: If you are installing the Fibre Channel adapter for the first time, you must
specify the correct topology. You must also select the appropriate device
mapping driver.
1. From your desktop, click Start Settings.
2. Double-click Control Panel.
3. Double-click SCSIAdapters.
4. Click the Drivers tab.
66
IBM SAN Implementation
5. Click Add to create a list of drivers.
A window opens that indicates the progress. When the window closes, you
should see a window called Install Driver.
6. From the Install Driver window, click Have Disk.
7. Enter the path to the driver file that you downloaded and click OK.
8. To install the driver, highlight the line that lists the driver you want and click
OK.
Note: The driver affects every adapter in the system. If you have more than
one adapter that requires different parameter settings, you must change the
parameter settings with the port utility and restart your host system.
9. Click Yes to restart the host system.
10.After you restart your host system, click Start Settings.
11.Double-click Control Panel.
12.Double-click SCSI Adapters.
13.Click the Drivers tab and verify that the Emulex SCSI driver is present and
started.
14.Click the Devices tab and verify that the host adapter is on the list.
1.11.12 Parameter settings for the Emulex LP8000 on Windows 2000
In Table 1-11 we show the recommended host bus adapter configuration file
parameters for an Emulex LP8000 adapter. The settings are for an IBM ESS
model F20 that is attached through a switch using the fabric, automap SCSI
devices port driver, and an IBM ESS model F20 that is attached directly, using
arbitrated loop, automap SCSI devices port driver.
Table 1-11 Recommended LP8000 settings for Windows 2000
Parameters
Recommended settings
Automatically map SCSI devices
Checked (enabled)
Query name server for all N-ports
Checked (enabled)
Allow multiple paths to SCSI targets
Checked (enabled)
Point-to-point
Not checked (disabled) for direct attach
Not shown for the fabric attach
Register for state change
Checked (enabled)
Use report LUNs
Checked (enabled)
Chapter 1. Implementing Fibre Channel host adapter cards
67
68
Parameters
Recommended settings
Use name server after RSCN
Checked (enabled) if fabric attached using
soft zoning
Not checked (disabled)
Lun mapping
Checked (enabled)
Automatic lun mapping
Checked (enabled)
Scan in device ID order
Not checked (disabled)
Enable class 2 for SCSI devices
Not checked (disabled)
Report unknown SCSI devices
Not checked (disabled)
Look for disappearing devices
Not checked (disabled)
Translate queue full to busy
Not checked (disabled)
Use bus reset status for retries
Not checked (disabled)
Retry unit attention
Not checked (disabled)
Retry PLOGI open failures
Not checked (disabled)
Maximum Number of LUNs
Equal to or greater than the number of the
ESS LUNs available to the host bus
adapter
Maximum Queue Depth
8
Link Timer
30 seconds
Retries
64
E_D_TOV
2000 milliseconds
AL_TOV
15 milliseconds
Wait ready timer
45 seconds
Retry timer
2000 milliseconds
R_A_TOV
2 seconds
ARB_TOV
1000 milliseconds
Link Control
Not shown for direct attach
Topology
Point-to-point (fabric)
Arbitrated loop (direct connect)
Link speed
Auto
IBM SAN Implementation
1.11.13 Verifying the configuration
The following tells you how to determine whether or not your Windows 2000 host
system is configured for storage.
1. From the Windows 2000 desktop, right-click Start.
2. Partition new Fibre Channel drives with Microsoft Disk Administrator. See
your Windows 2000 documentation for more instructions.
3. Click Explore and verify that you can see the Fibre Channel drives.
4. Select a large file (for example, a 9 MB file), and copy it to a Fibre Channel
drive.
1.11.14 Verifying networking
The following tells you how to determine whether or not your Windows 2000 host
system is configured for networking:
1. From the Windows 2000 desktop, click Start Programs Command Prompt.
2. From the command line, ping a known TCP/IP address.
1.12 Locating the worldwide port name
This topic tells you how to locate the WWPN value for a host system Fibre
Channel adapter for the following operating systems:









AS/400 iSeries
NUMA-Q and xSeries
RS/6000 and pSeries
Compaq
Hewlett Packard 9000
Novell NetWare
Sun
Windows NT
Windows 2000
1.12.1 Fibre Channel port name identification
The WWPN consists of exactly 16 hexadecimal characters (0-9 and A-F). It is
used by the ESS to uniquely identify the Fibre Channel adapter card that is
installed in your host system. The ESS automatically finds the WWPN for your
host Fibre Channel adapter when you attach your host system to the ESS.
Chapter 1. Implementing Fibre Channel host adapter cards
69
If your host system uses more than one Fibre Channel adapter to connect to your
ESS, you must add multiple entries to the host system list for this host, one for
each Fibre Channel adapter. Each adapter will have its own unique WWPN.
The format and content of the Fibre Channel port identifier are determined by the
manufacturer of the link control facility for the applicable Fibre Channel port. The
identifier is an eight-byte field, which the Fibre Channel protocols use to uniquely
identify the Fibre Channel port. An example is the ESS Fibre Channel port.
You can manually assign a unique worldwide port name for the ESS by
performing the steps in the following sections.
1.12.2 Locating the WWPN for an AS/400 iSeries
To locate the WWPN for a AS/400 host system, perform the following steps:
1. On the screen for the AS/400 Main Menu panel, type strsst.
2. On the Start Service Tools (STRSST) Sign On panel, type your service tools
userid and service tools password.
3. On the System Service Tools (SST) panel, type 1 to select Start a service
tool.
4. On the Start a Service Tool panel, type 7 to select Hardware service manager.
5. On the Hardware Service Manager panel, type 1 to select Packaging
hardware resources (systems,frames,cards,...).
6. On the Packaging Hardware Resources panel, type 9 to select the System
Expansion unit.
7. On the Packaging Hardware Resources panel, type 8 to select Multiple
Function IOA.
8. On the Logical Resources Associated with a Packaging Resource panel, type
5 to select Multiple Function IOA.
9. On the Auxiliary Storage Hardware Resource Detail panel, locate the field
name for Port worldwide name. Note the number in the right hand column.
Note: If you have exchanged a 2766 Fibre Channel IOA in the iSeries system,
the IBM 2105 ESS disk unit subsystem must be updated to use the worldwide
port name of the new 2766 IOA. You can find the name in the port worldwide
name field on the iSeries system by displaying detail on the 2766 IOA Logical
Hardware Resource information in Hardware Service Manager in SST/DST.
70
IBM SAN Implementation
1.12.3 Locating the WWPN for an IBM eServer or IBM NUMA-Q host
To locate the WWPN for a NUMA-Q host system with an IOC-0210-54 adapter,
perform the following steps from the IBM Enterprise Storage Specialist:
1. From the Enterprise Storage Specialist Welcome panel, click Storage
Allocation.
2. From the Storage Allocation graphical view panel, click Open System
Storage.
3. From the Open System Storage panel, click Modify Host Systems.
4. In the Host Nickname field, type the nickname.
5. In the Host Name field, click either IBM NUMA Server (WinNt) or IBM NUMA
Server (UNIX) from the list.
6. Click the Down Arrow to the right of the Host Attachment field.
7. From the list, highlight and click Fibre Channel Attached.
8. In the Hostname/IP Address field, type the hostname.
9. Click the Down Arrow to the right of the World-Wide Port Name field.
10.Select the worldwide port name from the list.
11.Click Perform Configuration Update.
1.12.4 Locating the WWPN for an RS/6000 and pSeries host system
To locate the WWPN for an RS/6000 or pSeries host system, perform the
following steps:
1. Login as root.
2. Type lscfg -vl fcsx, where x is the adapter number.
The network address is the Fibre Channel adapter port WWPN value.
Note: The lscfg -vl fcsx ROS level identifies the Fibre Channel adapter
firmware level.
1.12.5 Locating the WWPN for a Compaq host system
To locate the WWPN for a Compaq host system, perform the following steps:
1. From the console prompt, type P0>>>wwidmgr -show ada.
Following is an example of what is displayed:
Chapter 1. Implementing Fibre Channel host adapter cards
71
Probing timeout
item adapter WWN Cur.Topo Next Topo
[0 ]pga0.0.0.7.1 1000-0000-c922-d469 FABRIC FABRIC
[1 ]pgb0.0.0.8.1 2000-0000-c922-6a63 FABRIC FABRIC
[9999 ]All of the above.
If you receive the following error:
wwidmgr available only prior to booting. Reinit system and try again.
Type P00>>>init and repeat the wwidmgr command.
If you receive the following error:
wwidmgr: No such command
If you see this message, type P00>>set mode diag and type the wwidmgr
command again.
If the system is already running, you can find the WWPN in the log file
/var/adm/messages.
2. Type #fgrep wwn /var/adm/messages
Note: The worldwide port names are recorded at each system startup.
This is an example of typing var/adm/messages.
Nov 9 09:01:16 osplcpq-ds20 vmunix:KGPSA-BC :Driver Rev 1.21 :F/W Rev
2.22X1(1.13):wwn 1000-0000-c922-d469
Nov 10 10:07:12 osplcpq-ds20 vmunix:KGPSA-BC :Driver Rev 1.21 :F/W Rev
2.22X1(1.13):wwn 1000-0000-c922-d469
Nov 13 17:25:28 osplcpq-ds20 vmunix:KGPSA-BC :Driver Rev 1.21 :F/W Rev
2.22X1(1.13):wwn 1000-0000-c922-d469
Nov 14 11:08:16 osplcpq-ds20 vmunix:KGPSA-BC :Driver Rev 1.21 :F/W Rev
2.22X1(1.13):wwn 1000-0000-c922-d469
Nov 15 10:49:31 osplcpq-ds20 vmunix:KGPSA-BC :Driver Rev 1.21 :F/W Rev
2.22X1(1.13):wwn 1000-0000-c922-d469
1.12.6 Locating the WWPN for a Hewlett Packard host system
To locate the WWPN for a Hewlett Packard host system, perform the following
steps:
1. Go to the root directory.
2. Type ioscan -fn | more
3. Look under the description for the Fibre Channel Mass Storage adapter.
72
IBM SAN Implementation
For example, to look for the device path name /dev/td1, type:
fcmsutil /dev/td1 where /dev/td1
1.12.7 Locating the WWPN for a Novell NetWare host system
To locate the WWPN for a Novell NetWare host system with a QLogic adapter,
perform the following steps:
1. Restart the server.
2. Press Alt+Q to get the FAST!Util menu.
If you have more than one Fibre Channel adapter installed, you will see a
screen that displays all the Fibre Channel adapters. Scroll down to the
adapter you want.
3. Press Enter.
4. From the Fast Util!menu, scroll down and select Select Host Adapter.
5. Scroll up and highlight Configuration Settings. Press Enter.
6. From the Configuration Settings menu, click Host Adapter Settings.
7. Write down the host adapter name, for example: 200000E08B00C2D5.
1.12.8 Locating the WWPN for a Sun host system
To locate the WWPN for a Sun host system for a JNI Fibre Channel adapter card,
perform the following steps:
1. Go to the root directory
2. Type dmesg | more
All the devices in the directory are displayed. When you type dmesg | more, you
might find the worldwide port name of other Fibre Channel adapters if the driver
displays the worldwide port name during a restart.
Scan the output message file for fcaw or jnic, and the 64-bit number if you have
a different JNI Fibre Channel driver. Then look for the worldwide port name, for
example, 20000E06940028.,
Note:
1. There is no method to locate the WWPN for a QLogic QLA2100F adapter
installed on a Sun host system.
2. If you have multiple host adapters installed, you will see more than one
WWPN.
Chapter 1. Implementing Fibre Channel host adapter cards
73
1.12.9 Locating the WWPN for a Windows NT host system
To locate the WWPN for a Windows NT host system with a QLogic adapter,
perform the following steps:
1. Restart the server.
2. Press Alt+Q to get the FAST!Util menu.
If you have more than one Fibre Channel adapter installed, a panel displays
all the Fibre Channel adapters. Scroll down to the adapter you want. Press
Enter.
3. From the Fast!Util menu, scroll down and select Select Host Adapter.
4. Scroll up and highlight Configuration Settings.
5. Press Enter.
6. From the Configuration Settings menu, click Host Adapter Settings.
7. Write down the host adapter name, for example, 200000E08B00C2D5.
1.12.10 Locating the WWPN for a Windows 2000 host system
To locate the WWPN for a Windows 2000 host system with a QLogic adapter,
perform the following steps:
1. Restart the server.
2. Press Alt+Q to get the FAST!Util menu.
If you have more than one Fibre Channel adapter installed, all the Fibre
Channel adapters are displayed.
3. Scroll down to the adapter you want.
4. Press Enter.
5. From the Fast!Util menu, scroll down and select Select Host Adapter.
6. Scroll up and highlight Configuration Settings.
7. Press Enter.
8. From the Configuration Settings menu, click Host Adapter Settings.
9. Write down the host adapter name, for example: 200000E08B00C2D5.
74
IBM SAN Implementation
2
Chapter 2.
IBM TotalStorage
Enterprise Storage Server
configuration
One benefit of a SAN is to implement disk pooling. To do this successfully,
we need an easy-to-manage storage server with a Fibre Channel attachment.
This is the IBM TotalStorage Enterprise Storage Server, 2105-F20, shown in
Figure 2-1.
First we introduce the ESS Web Interface, including the functions to maintain,
configure, and administer the ESS. Then we perform storage configuration.
We describe the configuration for an ESS using RAID 5 for use in a Fibre
Channel environment. These functions are described in a task-oriented manner.
We start with an unconfigured ESS and explain the configuration steps as we
progress through our configuration. The final goal is to gain access to the
volumes from Fibre Channel attached hosts.
In greater detail, we cover the configuration of the ESS disk groups, host Fibre
Channel ports (host FC ports), ESS Fibre Channel ports (ESS FC ports), and the
ESS logical volumes to be accessed from the host FC ports. We also modify
volume assignments and make changes to the host FC port definition.
© Copyright IBM Corp. 2001
75
For further information on the configuration of the ESS, especially for ESCON
and SCSI attachment and the ESS Web Copy Services, refer to the ESS
documentation, as described in “Related information: For more information on
the ESS, see these references:” on page 172.
Figure 2-1 Enterprise Storage Server
76
IBM SAN Implementation
2.1 Introducing the ESS Web Interface
The Java based Web interface consists of two consoles, the IBM TotalStorage
Enterprise Storage Server Specialist (ESS Specialist) and the IBM TotalStorage
Enterprise Storage Server Web Copy Services (ESS Web Copy Services).
The ESS Specialist is used for querying the status of the ESS and for displaying,
defining and modifying the operation, configuration and administration of the
ESS.
The ESS Web Copy Services is used for querying the status of remote
operations and performing tasks with the advanced copy functions FlashCopy
and Peer to Peer Remote Copy (PPRC) of more than one ESS.
We will cover configurations performed using the ESS specialist.
Accessing the ESS specialist
To access the ESS specialist, we use the Netscape Navigator and point it to the
hostname or IP address of any of the two ESS clusters in the Uniform Resource
Locator (URL) field. The Web browser than connects to the Web server in the
ESS cluster, which handles the requests from the browser.
Since the programs, that run in the Web browser window, are Java applets, the
Java Virtual Machine (JVM) used by the browser needs to be capable of
supporting the applets. Browsers, that are supported by the ESS Web Interface
are:
 Netscape Navigator
–
–
–
–
–
4.04 with JDK 1.1 fixpack
4.05 with JDK 1.1 fixpack
4.06
4.5x
4.7x
 Microsoft Internet Explorer
– 4.x with JVM 4.0 or 5.0
– 5.x with JVM 4.0 or 5.0
The ESS Specialist does not support Netscape Navigator 6.0. Other Browsers
might work, but are not currently supported by IBM.
We show a short overview of the configuration panels of the ESS Specialist.
These are the panels that are accessed through the buttons displayed on the left
of the screen.
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration
77
2.1.1 Logging on to the ESS Specialist
Here we will detail the steps to log on to the ESS Specialist.
Viewing the Introduction panel
Once connected to one of the ESS clusters, either reloading the Web page,
using the Reload button of the Web browser, or clicking the Introduction button
will take us to the introduction panel of the ESS Specialist, as shown in
Figure 2-2.
Figure 2-2 Introduction panel of the ESS specialist
78
IBM SAN Implementation
To the left, we see the main button panel, from where we can access the viewing
and configuration panels of the ESS Specialist. Also, from there we can connect
to and troubleshoot the ESS Web Copy Service. On the main window we can see
the machine type, machine model, and serial number displayed. Also, we see the
identification of the Fibre Channel ESS in the Fibre Channel fabric in the form of
its World Wide Node Name (WWNN).
Accepting the ESS site certificate
By clicking on any one of the buttons to the left, we are forced to login to the site.
If this is the first time that our browser is connecting to the ESS, the browser will
display a sequence of access security panels. These are used to tell the browser
that the site that it is pointing to, should be considered as a secure site and that
encrypted communication should be allowed.
The first two panels containing information on the site are shown in Figure 2-3
and Figure 2-4.
Figure 2-3 New Site Certificate, start window
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration
79
Figure 2-4 New Site Certificate, information window
More information on the certificate, including the certificate fingerprint and the
time frame for which this certificate is valid, can be displayed by pressing the
More Info button, as shown in Figure 2-5.
Figure 2-5 New Site Certificate, More Info window
80
IBM SAN Implementation
After closing the Information window, we are asked about our decision to accept
the certificate or not, and if we would like to accept the certificate until it expires.
This is shown in Figure 2-6.
Figure 2-6 New Site Certificate, Accepting the certificate
Logging in with the default user
After completing the certification check, the Login Window, shown in Figure 2-7,
will display. The default user is storwatch and the default password is
specialist. Both are case sensitive and must be entered in lower case. For
security reasons, it makes sense to change the default user and password to
prevent unauthorized access.
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration
81
Figure 2-7 Site login window
The session will be valid as long as any browser window is open. Therefore,
when the work has been performed and security is important, we suggest closing
the browser to log off from the ESS specialist.
Be aware that a problem within the browser could keep the browser process
running, even when all browser windows are closed. This could lead to the
possibility of unauthorized personnel accessing the ESS with the Web interface.
A reboot or a new logon to the workstation would solve the problem, but there is
another method. This method involves ending the process with the Task
Manager. There will be a process netscape.exe in the Processes panel, which
can be closed with the End Process button.
2.1.2 Operating the ESS
Here we introduce the panels that we use to view the status of the ESS, for
instance, viewing the problem log and performing operation functions — for
example, changing the remote service access and resetting the PE password.
82
IBM SAN Implementation
Viewing the Status — Graphical View panel
Using the Status button, we get to the Status — Graphical View panel, as shown
in Figure 2-8.
Figure 2-8 Status — Graphical View panel
This panel allows us to quickly check for any errors in the ESS. To demonstrate
the features of the Status — Graphical View panel and the Status — Problem
Log panel we show them on a different ESS that is currently in service. What we
see is a problem detected in the storage arrays, with access to data not affected.
The other problem detected within the host bays, however, does affect access to
data, which is identified by a darker color.
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration
83
Viewing the Status — Problem Log panel
To get a detailed view on the problems encountered, we use the Problem Log
button on the upper right of the screen and get the Status — Problem Log panel,
as shown in Figure 2-9.
Figure 2-9 Status — Problem Log panel
Using the Graphical View button, we are able to go back to the graphical view.
84
IBM SAN Implementation
Viewing the Problem Notification panel
Using the Problem Notification button, we get the Problem Notification panel,
shown in Figure 2-10.
Figure 2-10 Problem Notification panel
From within this panel we can configure the various types of problem notification
provided with the ESS. The options available are e-mail, pager and Simple
Network Management Protocol (SNMP).
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration
85
Viewing the Communications panel
Using the Communications button, we get the Communications panel, as
shown in Figure 2-11.
Figure 2-11 Communications panel
Here we can view the network information for which the ESS is configured, and
verify if the Call Home feature and Remote Service Access is enabled. Also,
using the Reset PE Password button, we can reset the PE password. Only
users with administration or configuration levels of authority can modify these
panels. The network settings cannot be changed from within the ESS Specialist.
An IBM Service Support Representative (SSR) must perform this task using the
service terminal.
86
IBM SAN Implementation
Generating a new PE password
Resetting the PE password means actually that you generate a password for
Product Engineers (PE), which they can use to access the ESS from remote for
repair actions. By pressing the Reset PE Password button, a warning window
will appear, and after clicking the Yes button, the window with the new PE
password will be displayed. This password grants the PE unlimited access to the
ESS LIC and the ESS configuration files for 168 hours (7 days).
Using the Remote Support Modification panel
Using the Modify Remote Support button, we get the Remote Support
Modification panel, shown in Figure 2-12.
Figure 2-12 Remote Support Modification panel
The Remote Support Modification panel allows us to enable or disable the Call
Home feature and the Remote Service Access. In the event of failure of an ESS
component, the Call Home feature enables the ESS to dial to the IBM service
center. The Remote Service Access enables an SSR to dial into the ESS to
perform a limited set of non-disruptive diagnostic activities.
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration
87
Viewing the Licensed Internal Code panel
Using the Licensed Internal Code button we get the “Licensed Internal Code”
panel, as shown in Figure 2-13.
Figure 2-13 Licensed Internal Code panel
Here we can see the LIC levels of the ESS clusters and the licensed feature
codes that include all additional ESS functionality like copy services.
88
IBM SAN Implementation
2.1.3 Configuring the ESS
Following, we introduce the panels that serve as entry points to the logical
configuration of the ESS and link to the ESS Web Copy Services.
Viewing the Storage Allocation — Graphical View panel
Using the Storage Allocation button we get the Storage Allocation — Graphical
View panel, shown in Figure 2-14.
Figure 2-14 Storage Allocation — Graphical View panel
This is the start panel for host and storage based configurations. This panel
represents an ESS without anything configured.
Beginning with 2.2, “Starting the Open Systems Storage Configuration” on
page 96, we will start with this unconfigured ESS and show how to configure the
ESS for our SAN in detail.
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration
89
Using the Copy Services link
Using the Copy Services button we link to the copy services server.
We have to login to gain access, just like we did for the ESS Specialist. This
opens the Java based Web interface for the ESS Web Copy Services server in a
dedicated Navigator window, connects to it and loads the Java applets, as shown
in Figure 2-15.
Figure 2-15 Loading copy services server applets
Once connected, we get the introduction panel for the copy services
configuration options, as shown in Figure 2-16.
90
IBM SAN Implementation
Figure 2-16 ESS Web Copy Services introduction panel
Using the Tools help page
Using the Tools button we get a help page with embedded action links for
troubleshooting the ESS Web Copy Services.
As mentioned before, the ESS Web Copy Services is a separate server program
running on an ESS cluster, which is accessed through a different browser
window than the ESS Specialist. However, the ESS Specialist provides this panel
for troubleshooting, which makes sense because the ESS Specialist might not be
affected from the problem the ESS Web Copy Services server might have.
The helpfile with embedded action links we get is shown in Figure 2-17 and
continued in Figure 2-18.
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration
91
Figure 2-17 Tools help page, Web Copy Services trouble shooting
92
IBM SAN Implementation
Figure 2-18 Tools help page, Web Copy Services trouble shooting, continued
2.1.4 Administer the ESS
We will now introduce the administration of users on the ESS.
Using the User Administration panel
Using the Users button we get the User Administration panel, as shown in
Figure 2-19.
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration
93
Figure 2-19 User Administration panel
In our case there are no users configured, other than the default user that we
logged on with.
Using the Modify Users panel
In the Modify Users panel, as shown in Figure 2-20, we can add users with
different access levels.
94
IBM SAN Implementation
Figure 2-20 Modify Users panel
The access levels are:
View
Viewing the status and the configuration.
Operation
Viewing the status and the configuration and performing
operation functions.
Configuration
Viewing the status and the configuration, performing
operation and configuration functions.
Administration
Viewing the status and the configuration, performing
operation, configuration and administration functions.
After the first administrative user is defined on the ESS, the default user will be
removed. If all administration users have been, or get, deleted, the default user
will be restored after 30 minutes.
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration
95
2.2 Starting the Open Systems Storage Configuration
In the topics that follow, we will guide users through the storage and Fibre
Channel environment related parts as we progress through and build the
configuration. The tasks performed here will affect the way the ESS presents
itself in our SAN and to the SAN attached Fibre Channel hosts.
2.2.1 Viewing the storage configuration status
The panels described here will always show the status of the configuration of the
ESS. There are two panels, one that illustrates the configuration graphically, and
one that shows it in an tabular view.
Using the Storage Allocation — Graphical View panel
Using the Storage Allocation button we get the Storage Allocation — Graphical
View panel, as shown in Figure 2-21.
Figure 2-21 Graphical View, unconfigured ESS with ESCON, SCSI and FC
96
IBM SAN Implementation
In this panel, we get the logical view and the status of the installed and
configured storage related components of the ESS. These are the parts of the
ESS that need to be configured for ESS logical volumes to be accessible from
host FC ports.
The panel is interactive, which means, as we select different entities on this
panel, the panel will reflect the configuration of the ESS according to the selected
entity. Those can be the host interface icons, the ESS interface icons, the SSA
device adapter icons and the disk group rectangles. Also, the View All Storage
button allows us to see the status of all configured disk groups at once
To start with our ESS is unconfigured, and in the screen shots that follow we will
show how the panel will change.
Using the host interfaces row
The top row, shown in Figure 2-22, presents symbols for the host interfaces, that
have access to the ESS.
Figure 2-22 Host interfaces row, without any configured host interface
In the case of hosts with Fibre Channel connectivity, there will be an icon like the
one shown in Figure 2-23, for each host FC port that is defined in the ESS with
its World Wide Port Name (WWPN). The same applies to defined SCSI attached
hosts.
Figure 2-23 Open systems host port icon
There is no host FC port configured at this time, therefore, in Figure 2-22, there is
no icon shown. For ESCON attachment, if installed, there is a placeholder icon
for all connections. The host interface icons can be selected, which will change
the view of the panel to represent the configuration according to the selected
host interface.
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration
97
Using the ESS interfaces row
Below the host interface row, we see the row with icons for the ESS installed
interface adapters, shown in Figure 2-24.
Figure 2-24 Installed ESS interfaces row
The row is divided into four columns to show the location in the ESS interface
bays. Our ESS is equipped with four ESCON adapters and four SCSI adapters,
with one of them in each bay, and 8 Fibre Channel adapters, with two of them in
each bay. For a Fibre Channel ESS, which also has to serve a few SCSI and
ESCON attached hosts, this is a fairly balanced setup.
As opposed to the host interfaces row, the icons shown in the ESS interfaces row
represent adapters, not ports. If an adapter type, for instance a SCSI adapter,
features two ports, we have still one icon.
We can also see how many ports a specific adapter type offers. We can see that
ESCON and SCSI adapters are dual ported and the FC adapters are single
ported. For clarity, we use the term ESS FC port in this redbook, even when
talking about the adapter itself.
The ESS interface adapter icons can also be selected, which will change the
view of the panel. For instance, it will display information of the type and
configuration of the adapter.
Graphically, the representation of the adapters is different to help to distinguish
between them. The different representations of the adapters are shown in
Figure 2-25, Figure 2-26, and Figure 2-27.
Figure 2-25 ESS ESCON adapter with two ports
98
IBM SAN Implementation
Figure 2-26 ESS SCSI adapter with two ports
Figure 2-27 ESS FC adapter with one port
Viewing the association between host ports and ESS ports
In the ESS, we do not tie a host FC port to a Fibre Channel port in the ESS,
which was what we did with the SCSI adapters. Every host FC port within the
Fibre Channel fabric will be identified by its WWPN and can access data through
every ESS FC port unless other measures are taken. We will see later during the
ESS configuration, that we can restrict host FC ports through which ESS FC port
it will be able to access ESS logical volumes.
To show the independence of the port, the selected host FC port is graphically
connected to each ESS FC port, as shown in Figure 2-28. In this example, we
will assume that we already have two host FC ports configured to illustrate this
point.
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration
99
Figure 2-28 FC host port selected
In contrast to this, the host SCSI ports have an affinity to the ESS SCSI ports,
which is visible by selecting a host SCSI port, as shown in Figure 2-29.
Figure 2-29 SCSI host port selected
Using the disk group section
The two ESS clusters with the SSA device adapters and the SSA loops with the
disk groups are shown below the ESS Fibre Channel ports.
This is shown in Figure 2-30 and is how it looks if there is no disk group
configured.
100
IBM SAN Implementation
Figure 2-30 SSA device adapters without any disk group configured
Again, we are anticipating the configurations that are to be made later. To
graphically show the state the disk groups are in, we press the View All Storage
button on the upper right of the panel.
This is shown in Figure 2-31. Disk groups can also be selected to show the state
of the selected storage. Then, the host interface row will only show the host FC
ports, that have ESS logical volumes assigned to that exist on this particular disk
group.
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration
101
Figure 2-31 Disk groups, view all storage mode
To show the state of the disk groups, which contain ESS logical volumes
assigned to a particular host FC port, we select the host FC port first and then
one of the yellow highlighted ESS FC ports, which is shown in Figure 2-32.
Figure 2-32 Disk groups, storage assigned to selected host FC port
102
IBM SAN Implementation
There are different colors to indicate the state of the disk groups. At the upper
right of the screen, shown in Figure 2-33, a legend is displayed, which explains
what the different colors in the disk groups represent.
Figure 2-33 Legend of the disk group status colors
The colors indicate the following:
Purple, Host Storage Disk storage that contains ESS logical volumes that are
assigned to a specific (selected) host FC port. This
displays only if a host FC port is selected first.
Red, Assigned
Disk storage that contains ESS logical volumes that are
assigned to other than the selected host FC port, or that
are assigned to any host FC port, when no host FC port
was selected. This happens, for example, when we select
a specific disk group or when we press the View All
Storage button.
Yellow, Unassigned Disk storage that contains ESS logical volumes that were
assigned to host FC ports before and then were
unassigned. Those ESS logical volumes can be assigned
to any host FC ports.
Green, Not Allocated Disk storage that contains no ESS logical volumes. This
storage can be used to define and assign ESS logical
volumes.
We will explain more details of the Storage Allocation — Graphical View panel
later on as we progress with our configuration and the panel shows the
information relating to our configuration changes.
Using the Storage Allocation — Tabular View panel
To get a detailed view of the ESS logical volumes later on, we will use the
Tabular View button to get to the view as shown in Figure 2-34.
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration
103
Figure 2-34 Tabular View, no ESS logical volumes configured
As expected, the table that contains the detailed description of all volume
assignments made, is empty right now.
2.2.2 Using the Open System Storage panel
To start with the configuration of the ESS, we press the Open System Storage
button, as shown in Figure 2-35. This is the door to the configuration of open
systems storage. It will lead us to the Open System Storage panel, as shown in
Figure 2-36. The S/390 Storage button is also accessible, because there are
ESCON cards installed.
Figure 2-35 Entry for open systems storage configurations
Using the Open System Storage Panel
The Open System Storage panel consists of the Hosts Systems table, the
Assigned Volumes table and the configuration panel buttons. We will see shortly
that those two tables are showing the defined host FC ports and, to the selected
host FC port, the assigned ESS logical volumes, as shown in Figure 2-36.
104
IBM SAN Implementation
Figure 2-36 Open System Storage panel, no host FC ports defined
The configuration panel buttons at the bottom are the entry points to all of our
storage related configuration tasks. The Open System Storage panel is like a
hub, from where we start every open systems storage configuration. In this
section, we will indicate our use of the configuration panel buttons by pointing the
mouse on the button.
Using the proper order of configuration steps
This is an introduction to the dependencies that some configuration steps have.
Our ESS is not configured, so we show where we start the configuration. What
we want to achieve is to prepare the ESS to provide some ESS logical volumes
to host FC ports. Some of the configuration steps have to be done prior to others.
Figure 2-37 shows the dependencies of the configuration steps.
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration
105
Configuring disk groups and
defining host FC ports to be able
to add ESS logical volumes
Configuring the ESS FC ports
for FC-SW or FC-AL
Adding ESS logical volumes to
disk groups and assigning them to
host FC ports
Accessing the assigned
ESS logical volumes
Figure 2-37 ESS configuration dependencies
106
IBM SAN Implementation
One step that is independent from the others, is the configuration of the ESS FC
ports for FC-SW or FC-AL. For this we have to know what type of FC topology we
want to connect with a particular ESS FC port. Other steps rely on the
completion of others.
In order to add ESS logical volumes to disk groups, we need to perform two
configuration steps. Those are the configuration of some disk groups for RAID or
JBOD and the definition of one or more host FC ports by its host type and
WWPN. The host FC port definition is needed because the process of adding
volumes consists not only of creating the volumes but also of assigning them to a
host FC port.
If there are existing ESS logical volumes, we can also assign them to other host
FC ports. Now, if both requirements have been met (ESS logical volumes have
been assigned and the ESS FC ports are defined), we can access the volumes
from the Fibre Channel attached host. Of course, the connectivity must be there
and the host system has to be prepared also. How to achieve this is discussed in
other parts of this book.
2.3 Configuring disk groups
Now we will show how to configure the ESS for FC attachment in detail. We
choose to start our configuration with the disk groups, followed by the
configuration of the host FC ports. The completion of both configuration steps
enables us to add the ESS logical volumes later on.
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration
107
2.3.1 Performing the disk group configuration
Pressing the Configure Disk Groups button takes us to the Fixed Block Storage
panel, as shown in Figure 2-38.
Figure 2-38 Fixed Block Storage panel, no disk groups configured
Using the Fixed Block Storage panel
The Available Storage table lists all of the available physical storage in the ESS
with its location, storage type, track format, and capacity. As we can see, when
we scroll down the table, no disk array has been formatted at this time.
108
IBM SAN Implementation
Note: The disk groups should not be mistaken for the eight packs, which are
the physical disk packages, that are installed in the ESS. The disk groups are
logical groups that consist of disks from two eight packs, four disks from each
of the two. This is the reason why it is only possible to upgrade the ESS in
steps of two eight packs.
The unformatted size of the disk groups is 254.8 GB. This is equivalent to seven
disks of a capacity of 36.4 GB each. In the ESS, we have two spare disks per
SSA loop. In our ESS we have sixteen disk groups, four per device adapter pair
and two per SSA loop. This is the reason why every one of our disk groups
contains one spare disk. This makes up the total unformatted capacity of 254.8
GB per disk group.
Defining two disk groups for RAID 5
We are going to define the disk groups connected to the A loop of the device
adapter pair 4 as RAID array. To do this, we select the first disk group we want to
configure and select Raid Array from the Storage Type pull-down menu.
The storage type, as shown in Figure 2-39, can be RAID Array, or non-RAID.
Non-RAID means the disks are going to be configured as “just a bunch of disks”
(JBOD).
Figure 2-39 Open systems storage types
Doing this also changes the Track Format to Fixed Block (FB) in the Track
Format pull-down menu. After doing this, we select the second disk group in the
other cluster, and also select Raid Array.
The Modification column of the panel, as shown in Figure 2-40, shows that we
have made changes (Defined), and the Capacity column shows that our disk
groups are still unformatted. In this case, formatted to the ESS means it is not
formatted as either a RAID array or as non-RAID.
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration
109
Figure 2-40 Disk groups defined for RAID 5
Performing the configuration update
To apply the changes made, we press the Perform Configuration Update
button.
A warning message appears, stating that this will be a time consuming action, as
shown in Figure 2-41.
Figure 2-41 Warning window, time consuming action
110
IBM SAN Implementation
How time consuming this will be depends on how many disk groups are to be
configured at once. Pressing the OK button executes the script which changes
the configuration and gives us a progress window, where we can see which
arrays are initializing, as shown in Figure 2-42.
Figure 2-42 Progress window, RAID configuration
After completing the configuration, the ESS Specialist informs us of the success,
as shown in Figure 2-43.
Figure 2-43 Status window, successful disk group configuration
We have to press the OK button here, which takes us back to the Open System
Storage panel.
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration
111
Viewing changes on the Graphical View panel
From here we can continue with our configuration. To see how the Storage
Allocation — Graphical View panel now looks, we press the Storage Allocation
button on the left of the screen.
The panel shown in Figure 2-44 now illustrates the representation of the two disk
groups between the SSA device adapter pair four in loop A. It is the view of the
panel with the disk group in cluster one selected.
Figure 2-44 Disk group section, configured disk group selected
112
IBM SAN Implementation
The rectangle representing the disk group is green to show that this is empty
storage. We also see that the host FC port icon row is empty. When selecting a
particular disk group, the row will only present and highlight those host FC port
icons that have ESS logical volumes assigned to it in the selected disk group.
Because there is no host FC port defined, there cannot be any ESS logical
volume defined and assigned.
When the disk group is selected, the Information field to the right of the panel
shows specific information such as the location of the disk group, the type of
storage the disk group is configured for and the available and allocated capacity.
This is shown in Figure 2-45.
Figure 2-45 Information window, for RAID 5 configured disk group
Here we see that the capacity of the disk groups that are configured as RAID
array, has changed to 210.48 GB. This is mainly because of the space for the
redundancy information that is now spread over the disks in the disk group and
because of the RAID configuration information.
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration
113
Defining two more disk groups for RAID 5
We will configure two more disk groups and so we therefore navigate back to the
Fixed Block Storage panel.
In Figure 2-46 we show what the Available Storage table looks like with the two
disk groups in loop A of the fourth adapter pair for RAID configured. This is prior
to performing the configuration update of the next two disk groups.
Figure 2-46 Two disk groups configured, two defined and two undefined
After we have performed the configuration update, we go back to the Storage
Allocation window to see how it now looks as a result of our changes.
114
IBM SAN Implementation
Viewing changes on the Graphical View panel
Device adapter pair number four and the connected SSA loops now look like that
shown in Figure 2-47.
Figure 2-47 Four disk groups configured
Undefining disk groups or redefining disk groups
It may be necessary to reconfigure disk groups. They can be unconfigured or
configured to another storage type. If there is a disk group configured for RAID 5,
it can be reformatted to JBOD or unconfigured. Doing this is the same process as
we did before.
First we select the disk group in the Available Storage table and then we have to
choose Undefined or non-RAID in the Disk Group Attributes field. After we get a
warning that all volumes on the selected disk group will be destroyed, we can
select the next disk group to be reconfigured. After changing the attributes of the
disk groups we perform the update.
A window pops up, informing us that the process will take a while and that we
can view the progress on the Status panel. This is with four disk groups in the
process of formatting, as illustrated in Figure 2-48.
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration
115
Figure 2-48 Status — Graphical View, four disk groups in the process of formatting
This discussion was just intended to show how it is done. Now we continue from
the point where we defined the disk groups.
2.4 Creating and modifying host FC port definitions
To fulfil the second condition to be able to define and assign ESS logical
volumes, we will define the host FC ports that are installed in the Fibre Channel
attached hosts.
116
IBM SAN Implementation
2.4.1 Creating host FC port definitions
From the Open System Storage panel, we press the Modify Host Systems
button, as shown in Figure 2-49.
Figure 2-49 Entry to the Modify Hosts Systems panel
Viewing the Modify Host Systems panel
We are now taken to the Modify Host Systems panel, as shown in Figure 2-50.
This panel consists of the Host Attributes entry fields and The Host Systems List
table. The Host Systems List represents each defined host FC port. If a host has
two Fibre Channel ports, this appears as two entries in the Host Systems List.
As we can see, there are no host FC ports defined at this time.
Figure 2-50 Modify Host Systems panel, no host FC ports defined
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration
117
Creating two host FC port definitions
In the Host Attributes entry fields, we identify the host FC port that will access the
ESS. The first entry is a nickname to identify the port in the ESS. Also, we have
to choose the host type, which is a PC server; the type of the host attachment,
which is Fibre Channel, and the WWPN of the host FC port, as shown in
Figure 2-51 and Figure 2-52.
We are doing this for the two host FC ports that we want to access ESS logical
volumes, nicknamed PC1_1 and PC1_2.
Figure 2-51 Host Attributes frame, host type selection
118
IBM SAN Implementation
Figure 2-52 Host Attributes frame, host interface type selection
The IP Address is only used by the StorWatch Enterprise Storage Server Expert.
It is used to show which host FC ports are in a specific IP host. We will not be
using the Expert for our example, so we leave the entry field empty.
By pressing the Add button, we add the specified host FC port to the Host
Systems List. We do the same for a second host FC port, as shown in
Figure 2-53.
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration
119
Figure 2-53 Host Systems List, host FC ports defined
This host FC port can belong to the same system, or we can define ports for
other systems.
Performing the configuration update
Adding ports to the list puts together a script in the background which is executed
by pressing the Perform Configuration Update button.
A progress bar informs us about the steps that are being executed, as shown in
Figure 2-54.
Figure 2-54 Performing the port definition
120
IBM SAN Implementation
A window appears which indicates that the configuration update was successful,
as shown in Figure 2-55. If the update had failed for any reason, we would get an
error message.
Figure 2-55 Successfully added host FC port
Pressing the OK button on this window will immediately take us back to the Open
System Storage panel.
Viewing changes on the Open System Storage panel
We now see the newly configured host FC ports in the Host Systems Table, as
shown in Figure 2-56.
Figure 2-56 Fibre Channel host adapter port; no volume assigned
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration
121
As we select one of them, we see that there are no ESS logical volumes currently
assigned to the host FC ports.
Viewing changes on the Graphical View panel
Now, we would like to see what the Storage Allocation — Graphical View panel
looks like. This is shown in Figure 2-57.
Figure 2-57 Four disk groups, two host FC ports
The two host FC ports we just have configured, now show up with their
nicknames in the host interface row. Although we could have used longer
nicknames, they would have been truncated, which would make them very hard
to identify. The only way would be to click on them and catch their names along
with other information like the WWPN and the type of the host system, on the
Information window shown in Figure 2-58.
Figure 2-58 Information window, host FC port in PC server
122
IBM SAN Implementation
Clicking on the host FC port icon also shows that the port would be able to
access volumes through each of the eight installed ESS FC ports if they were all
connected to the SAN and no zoning in the fabric would prevent them from
accessing the ESS FC ports.
This is illustrated in Figure 2-59, with lines drawn from the selected host FC port
to each installed ESS FC port. The involved components also get highlighted
yellow.
Figure 2-59 Selected host FC port, no ESS FC port restrictions
2.4.2 Modifying a host FC port definition
Each one of the settings that we applied before, for instance the nickname or the
WWPN, can be modified from within the Modify Host Systems panel.
We will now restrict the host FC port PC1_2 to the ESS FC port 3 in bay 1, as an
example of modifying the settings for host FC ports from within the Modify Host
Systems panel.
Restricting the ESS FC port access of host FC port PC1_2
To do this, we select the host FC port PC1_2 in the Host Systems List table, as
shown in Figure 2-60. This enables us to change the settings for this port in the
Host Attributes section.
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration
123
Figure 2-60 FC port PC1_2 selected for modification
As we show here, the Fibre-Channel Ports list indicates the current setup, which
is not restricted in ESS FC ports. It lists all ESS FC ports that are available as
shown in Figure 2-61.
Figure 2-61 All installed ESS FC ports
124
IBM SAN Implementation
We scroll to and select the adapter tree in bay 1 to limit the host FC port PC1_2
to this ESS FC port. We could also select any other port in addition to the one we
have chosen. To update the Host Systems List table, we press the Modify
button.
The restriction is now reflected in the FC Ports column, shown in Figure 2-62.
Figure 2-62 Host Systems List with restricted host FC port PC1_2
Now we perform the configuration update, which makes the changes we made
active.
Viewing changes on the Graphical View panel
Back on the Storage Allocation — Graphical View panel, we will see that the
changes made are also graphically reflected. This is shown in Figure 2-63.
We see that a line is drawn from the host FC port PC1_2 to the ESS FC port
three in bay one.
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration
125
Figure 2-63 Selected host FC port, restricted to one ESS FC port
It shows us also that there are no ESS logical volumes currently assigned to the
selected host FC port. This is indicated by the color of the disk group which
indicates that no volume exists. This is going to change, as we are now prepared
to add volumes.
2.5 Creating and assigning ESS logical volumes
As mentioned before, adding volumes to the disk groups and assigning them to
the newly defined host FC ports is done in one process. It involves two steps
using the Add Volume panels.
2.5.1 Adding ESS logical volumes, step one
From the Open System Storage panel, we use the Add Volumes button to start
the definition of volumes on the newly configured disk groups, as shown in
Figure 2-64.
Figure 2-64 Entry to the Add Volumes (1 of 2) panel
126
IBM SAN Implementation
This takes us to the Add Volumes (1 of 2) panel, as shown in Figure 2-65.
Figure 2-65 Add Volumes (1 of 2) panel with host FC port PC1_1 selected
Selecting host FC port for the volume assignment
From here, we select the host FC port PC1_1 that we just have defined. We also
have to select one of the ESS FC ports (Figure 2-66), before we can go to the
next panel.
Figure 2-66 host FC port and the ESS FC port selected
Logically, there is no reason to have to select a specific ESS FC port, because
we can reach the ESS logical volumes through every properly configured ESS
FC port. Even in the case of the host FC port PC1_2 that we restricted to a
specific ESS FC port, this would not make any difference.
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration
127
Selecting the disk groups for the volume placement
By clicking on a port, we can now see the storage that we can use to define
volumes on. This is shown in Figure 2-67.
Figure 2-67 Add Volumes (1 of 2) panel with disk group status shown
There are different colors to indicate which state the disk groups are in. In our
case, none of the four disk groups that we configured contains an ESS logical
volume. This is indicated by a green color. Only disk groups that contain
unallocated storage can be used to add volumes.
In Figure 2-67, no disk group has been manually selected by us. This means that
all of them are automatically selected for the next step of the process of defining
and assigning volumes. Which disk groups are selected is shown in the
Information window of the panel. However, we mark the two disk groups for use
in the next step by clicking on these. This highlights them with a border, as
shown in Figure 2-68.
Figure 2-68 One disk group selected
128
IBM SAN Implementation
2.5.2 Adding ESS logical volumes — step two
Pressing the Next button, we are taken to the second step of defining the
volumes.
This is the Add Volumes (2 of 2) panel, shown in Figure 2-69. This is where we
define how many volumes of what size we want to place sequentially on, or
spread across all prior selected disk groups.
Figure 2-69 Add Volumes (2 of 2) panel, two RAID 5 disk groups to be used
At the top of the panel, we see the Available Free Space area. We can see the
available capacity and the maximum volume size of the disk groups we selected.
Those numbers are in the row corresponding to the storage type we configured
in the Configure Fixed Block Storage panel.
Because we did not configure and select any disk group for JBOD, the Available
Capacity and Maximum Volume Size column show both an available free space
of zero.
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration
129
Note: An ESS logical volume can be as big as we want it to be within the
boundaries of one disk group. In our case, using 36.4 GB disks, we can have a
maximum volume size of 210.45 GB. Looking at the Information window on
the Storage Allocation — Graphical View panel we see 210.48 GB.
Selecting the storage type
To create RAID 5 volumes, we have to click on the RAID-5 Array row shown in
Figure 2-70.
Figure 2-70 Available Free Space frame, RAID-5 storage entry selected
If no storage type has been selected, the Volume Attributes field on the left hand
side shows only a volume size of zero.
Choosing the size and number of volumes
Once we have selected RAID-5 Array as the storage type, we can choose the
size and the number of the ESS logical volumes that we want to configure.
We are able to choose the size of the volumes granularity, beginning from 0.1 GB
up to the total capacity of our disk group, which is 210.45 GB, with a granularity
of 0.1 GB. We want to define four volumes with 16.1 GB each. The reason for the
volumes being exactly 16.1 GB, is that we want to all volumes the same size
without wasting any space. Defining volumes with a little less or a little more
space will mean that we will either fill the remaining space with smaller volumes
or waste space. For example, with a volume size of 16.2 GB, we could only
define 24 of them in two disk groups, which is shown in Figure 2-71.
Figure 2-71 Volume Attributes frame, ESS logical volume size of 16.2 GB selected
130
IBM SAN Implementation
Instead, we use a volume size of 16.1 GB, which allows us to place 26 of them in
our selected disk groups.
To illustrate the process we only want to define two volumes here. We enter the
number of volumes in the entry field, as shown in Figure 2-72.
Figure 2-72 Volume Attributes frame, ESS logical volume size of 16.1 GB selected
Adding volume definitions to the New Volumes frame
We press the Add button to place the two volumes in the New Volumes frame.
The volumes are now shown in the New Volumes Panel, as shown in
Figure 2-73. We could also add other volumes with different sizes to the list.
Figure 2-73 New Volumes frame, two volumes selected to be removed from frame
Removing volume definitions from the New Volumes frame
To remove unwanted changes from the list, we simply highlight those volumes
that we wish to remove from the list and press the Remove button.
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration
131
Placing the volumes in selected disk groups
Now, as we have defined how many volumes and of what size we want to add,
we can also decide how the selected space should be used for the placement of
the volumes.
The two choices we have are shown in the Volume Placement frame. This is
shown in Figure 2-74.
Figure 2-74 Volume Placement frame, spreading volumes selected
Here we can choose whether we want to place the volumes sequentially on all
selected disk groups, or if we want to spread the volumes over all selected disk
groups.
Placing volumes sequentially means that, in our case, the two 16.1 GB volumes
would both be placed on the first selected disk group. If we wanted to configure a
large number of 16.1 GB volumes, this would mean that the first 13 of them
would be placed on the first disk group and the following would start to fill the
second disk group.
In contrast to this, spreading volumes across all selected storage areas means
exactly what it says. In our case, one of our two 16.1 GB volumes is going to be
placed on each selected disk group.
Performing the configuration update
Our panel now looks like that shown in Figure 2-75, just before we apply the
configuration changes by pressing the Perform Configuration Update button.
132
IBM SAN Implementation
Figure 2-75 Add Volumes (2 of 2) panel, ready to perform the configuration update
Again, we get a window warning us about a time intensive action, and we are
asked if we want to continue with the update. This is shown in Figure 2-76.
Figure 2-76 Warning window, time consuming action
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration
133
As with every run of a configuration update, there is a progress window, as
shown in Figure 2-77.
Figure 2-77 Progress window, volume creation
After the update has finished successfully, we are presented with the message
shown in Figure 2-78.
Figure 2-78 Information window, successful volume creation
Pressing OK leads us back to the Adding Volumes (1 of 2) panel, from where we
can start the process again and define other volumes.
134
IBM SAN Implementation
Viewing changes on the Graphical View panel
To see the updates we have made, we press the Storage Allocation button.
This takes us back to the Storage Allocation — Graphical View panel. There, we
select the host FC port that we configured. This is shown in Figure 2-79.
Figure 2-79 Host FC port selected
This shows the volumes defined for our host FC port. The small purple parts of
both disk arrays represent the space that is filled with volumes that are assigned
to the selected host FC port. The green part indicates space that is not yet
allocated.
Clicking on an ESS Fibre Channel port will draw lines to the volumes configured
for the selected host Fibre Channel port. This is shown in Figure 2-80.
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration
135
Figure 2-80 Host FC port and ESS FC port selected
The Information field now displays information relating to the configuration of the
ESS FC port, which is currently undefined. This information is useful later to see
which ESS FC port is configured for the appropriate topology.
We show how to configure this in 2.7, “Configuring ESS FC ports” on page 158.
After selecting one of the disk groups, the display changes again. Now the disk
group has a thick border, and the Information frame has changed too. This is
shown in Figure 2-81.
Figure 2-81 Information frame, host FC port, and disk group selected
136
IBM SAN Implementation
The items that have changed on the disk group information since our last visit,
are the Host Storage row and the Not Allocated row.
Host Storage is the space that now has an ESS logical volume of 16.1GB
assigned to the selected host FC port.
Not Allocated means the space that can be used to define other ESS logical
volumes on.
Last but not least, we can also click on the disk array without selecting a host FC
port first. The panel’s look changes again when only the disk group is selected.
This is shown in Figure 2-82.
Figure 2-82 Disk group selected
To deselect everything that is currently selected, we press the Clear View button
on the top of the panel, or we can click on the host FC port that is selected. Then
we select the disk group in cluster one.
Notice that the part of the disk group that was purple before has changed to red.
This is because we did not specify that we are interested in the volumes that are
assigned to a particular host FC port. Instead, we now see the storage that is
allocated to any of the host FC ports. The host FC port icons that have ESS
logical volumes assigned to them on this disk group, now show up in the host
interfaces row and are also highlighted yellow.
In our case, only the host FC port PC1_1 has a volume on this disk group
assigned to it, and therefore there is only the icon of this port visible.
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration
137
Again, the Information frame changed the look to represent the general
information of the disk group and is still not related to a specific host FC port. The
used space now shows up in the Assigned row instead of the Host Storage row.
This is shown in Figure 2-83.
Figure 2-83 Information frame, disk group selected
Now we want to go on and define more volumes and assign them to the host FC
port PC1_2.
Viewing changes on the Open System Storage panel
To perform this task, we navigate all the way back to the Add Volumes panel.
From the Storage Allocation — Graphical View panel, we press the Open
System Storage button.
This takes us to the Open System Storage panel, as shown in Figure 2-84.
138
IBM SAN Implementation
Figure 2-84 FC port PC1_1 with two assigned volumes
Now when we select the host FC port PC1_1 in the Host Systems field, the
associated volumes appear in the Assigned Volumes field with all the relevant
details.
For host FC port PC1_2, the Assigned Volumes table is still empty.
Creating two more ESS logical volumes
Now we do the same as we did before with the host FC port PC1_1, for PC1_2.
We are going to create and assign two volumes of 64 GB, one of them in disk
group 1 and disk group 2 in loop B of the device adapter pair 4. This is done
exactly like we did before with the host FC port PC1_1, so we only show the
results.
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration
139
Viewing changes on the Graphical View panel
Back on the Storage Allocation — Graphical View panel we see how the panel
now looks using the View All Storage mode, shown in Figure 2-85.
Figure 2-85 View All Storage mode
The four areas in the four disk groups now represent the space that is used for
ESS logical volumes. We cannot see to which host FC port they are assigned.
To discover what volumes are assigned to PC1_2, we select this host FC port.
At this stage, we see that the two disk groups have purple spaces on them,
which means they are assigned to the selected host FC port.
140
IBM SAN Implementation
We select the host PC1_2, and we see that lines now appear connecting the host
port, ESS FC port, and storage volumes. This is shown in Figure 2-86.
Figure 2-86 Host FC port and ESS FC port selected
Viewing changes on the Tabular View panel
Now we will look at the Storage Allocation — Tabular View panel. We reach this
from here using the Tabular View button on the top right of the panel.
This shows detailed information on all host FC ports assigned ESS logical
volumes in one table, as shown in Figure 2-87.
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration
141
Figure 2-87 Displays of all four volume assignments
We see all the information about the location and the current assignments here,
as well as the ESS logical volume ID. This is the ID that will help us later to
identify the ESS logical volumes on our host system. Right now, there are not too
many entries in the table.
Later on, as we define more volumes, the table will become large. To make it
easier to view the table, we can also perform a sort on the table. The sort can be
performed using three choices of levels using the drop down list boxes on the top
of each column. To perform the sort, we press the Perform Sort button.
Now, we will modify ESS logical volume assignments.
2.6 Modifying ESS logical volume assignments
At this time we would only have to configure all the ESS FC ports to enable the
ESS to present volumes to a Fibre Channel host. There are further changes of
the assignment of volumes to ports that might have to be performed. For this, we
use the Modify Volume Assignments panel.
142
IBM SAN Implementation
For example, we can share volumes between host FC ports. These ports can be
in the same host which uses, for example, the Subsystem Device Driver (SDD),
to increase the bandwidth and availability, or in different hosts, for example, for
clustering. Or, we might want to unassign volumes that were shared before, or
we might want to unassign volumes to keep them unused for later reuse. We
cover all this in the following topics.
2.6.1 Sharing ESS logical volumes between two host FC ports
We click on the Modify Volume Assignments button as shown in Figure 2-88.
Figure 2-88 Entry point for modifying volume assignments
This takes us to the Modify Volume Assignments panel, as shown in Figure 2-89.
Figure 2-89 Four volume assignments, one for each existing volume
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration
143
The Volume Assignments table provides a comprehensive overview of all
configured volume associations. We can also sort the table, specifying the
column which we want to use as sort criteria. The rows do not represent the
volumes. Instead there will be a row for each association that a volume has as
we will see later on.
There is an Action field, which is grayed out, and a Target Hosts field, which is
empty, when no volume association is selected. Now we show their interaction.
Figure 2-90 shows the two assignments of the 64 GB volumes assigned to host
FC port PC1_2. Both assignments are selected and ready for modification.
Figure 2-90 Two selected volume assignments, Action field accessible
Selecting ESS logical volume assignments for modification
Selections of more than one assignment can be done in two ways.
The first case is if the assignments to be selected are not adjacent. Then we click
on the first assignment to be selected, press and hold the Ctrl key, and click on
the next assignment to be selected until we have all the assignments we want
selected. While holding down the Ctrl key, we can also click on an already
selected assignment to deselect it.
144
IBM SAN Implementation
The second case is if the assignments to be selected are adjacent. Of course to
avoid the application of the first selection method, we can sort the assignments
to show up adjacent. We sort the assignment here by its host FC port. For
adjacent assignments, we click on the first assignment to be selected, press and
hold the Shift key and click on the last assignment to be selected. This selects all
assignments in between.
If, for some reason, one of the assignments just selected using the Shift key
should not be modified, we are also able to deselect this assignment by pressing
the Ctrl key and clicking on it. In the same way, we can also add other particular
assignments to the selection.
Once we have done this, we go on and choose what we want to do with the
assignments using the Action field.
Creating new volume assignments for selected host FC port
With the radio button, we decide if we want to create a new volume assignment
using the volume associated with selected assignments, or remove both selected
volume assignments. We want to create new assignments to share the volumes
and so we select the corresponding radio button shown in Figure 2-91.
Figure 2-91 Adding assignments to other available host FC ports selected
Selecting this allows us to choose the host FC port from those displayed in the
Target Hosts field. We have only the host FC port PC1_1 available for this action.
If there were to be more host FC ports configured, we would have to choose and
select the one on which we want the assignments altered, by highlighting its
name.
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration
145
Performing the configuration update
To apply the changes, we press the Perform Configuration Update button.
The progress bar indicates that the configuration update is taking place, as
shown in Figure 2-92.
Figure 2-92 Progress window, creating volume assignments
If successful, we get the message shown in Figure 2-92.
Figure 2-93 Volume assignments successfully created for specified host FC ports
146
IBM SAN Implementation
If we press OK, we do not change back to the Open System Storage panel.
Instead, we see the new volume assignments to the host FC port PC1_1, as
shown in Figure 2-94.
Figure 2-94 Assignments for the host FC port PC1_1
Viewing changes on the Graphical View panel
Back on the Storage Allocation — Graphical View panel, we now see that the
host FC port PC1_1 has volumes assigned to it on all four disk groups as shown
in Figure 2-95.
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration
147
Figure 2-95 PC1_1 and ESS FC port selected
In fact there is no volume configured on the ESS which is not assigned to this
port. This is indicated by the lack of any colored space on the disk group, apart
from the color of purple for the selected host FC port assigned volumes, or green
for unused space.
When a host FC port is selected, there is no indication that two of the volumes
are shared between both the defined host FC ports. To see if ESS logical
volumes are shared, we have to select a disk group. In Figure 2-96, we see a
disk group selected, that contains assigned volumes.
148
IBM SAN Implementation
Figure 2-96 Disk group containing shared ESS logical volume(s) selected
The red color indicates that it contains volumes that are assigned to the host FC
ports that show up highlighted yellow in the host interfaces row. When we
compare this with Figure 2-95, we see that the amount of space used for this disk
group is the same. Also, when we select the host FC port PC1_2, we will see the
same amount of storage assigned to it, which tells us that the volumes must be
shared between the two.
Viewing changes on the Tabular View panel
If we click on the Tabular View button and get the Storage Allocation — Tabular
View panel as shown in Figure 2-97, we see two rows for each of the two 64 GB
sized volumes. Once for the host FC port PC1_1 and once for PC1_2. Again, the
table does not represent the volumes but the assignments the volumes have, if
any. The rightmost column indicates the sharing of the volumes as well.
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration
149
Figure 2-97 Tabular View, two volumes shared, two not shared
Converting volume assignments table in HTML format
To view the table offline, or to print it, this panel features the Print Table button.
Then a window as shown in Figure 2-98 will appear, advising that the information
is going to be displayed in another browser window.
Figure 2-98 Information window, opening another browser window.
150
IBM SAN Implementation
Now the content of the table is displayed in HTML format, as shown in
Figure 2-99.
Figure 2-99 HTML file, List of Assigned Volumes table, list of existing assignments
It can now be printed from within the browser or it can also be saved as an HTML
file for later viewing.
2.6.2 Removing volume assignments from host FC ports
The second configuration change, regarding the volume assignments we want to
show, is removing the assignments of the ESS logical volume in disk group two
of loop B of the SSA device adapter pair 4, from both host FC ports.
Again, we click on the Modify Volume Assignments button, as shown in
Figure 2-100.
Figure 2-100 Entry point for modifying volume assignments
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration
151
Removing the assignments of one ESS logical volume
First as we did in, “Selecting ESS logical volume assignments for modification”
on page 144, we select the volume assignments for both host FC ports. Then,
when the Action field becomes available, we select the radio button to Unassign
selected volume(s) from target hosts, which means, remove selected ESS
logical volume assignments for the selected host FC ports. The Target Hosts field
now lists the host FC ports to which the assignments belong to. Here we select
both host FC ports to remove the assignments. This is shown in Figure 2-101.
Figure 2-101 Removing volume assignments from both host FC ports.
Doing so makes the warning message shown in Figure 2-102 appear, stating that
this action will cause ESS logical volumes to become isolated for the selected
host FC port.
Figure 2-102 Warning window one, volumes to be isolated from host FC ports
After pressing the Perform Configuration Update button, a second warning
window will show up as shown in Figure 2-103. This time, the window gives us
the choice to abort the configuration update.
152
IBM SAN Implementation
Figure 2-103 Warning window two, volumes to be isolated from host FC ports
We press the Yes button to proceed with the update and get a progress bar and
a message window as shown in Figure 2-104 and, as we already know from the
other actions we have done using this panel.
Figure 2-104 Progress window, applying assignment changes
In Figure 2-105 we are told that the volume assignments have been successfully
removed.
Figure 2-105 Information window, volume assignments successfully removed
Now the Volume Assignments table shows the just unassigned volume. This
table represents the assignments made for ESS logical volumes, not the volumes
themselves. An exception is if volumes are not assigned to any host FC port.
Then there will be one placeholder row that can be used to create an
assignment. This row selected is shown in Figure 2-106.
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration
153
Figure 2-106 Placeholder for unassigned ESS logical volume selected
Viewing changes on the Open System Storage panel
If we use the Back button of our browser we return to the Open System Storage
panel. There we see that the volume is not displayed any more on any of our host
FC ports. This is shown in Figure 2-107 for the host FC port PC1_2, which now
has only one volume assigned to it.
Figure 2-107 Open System Storage panel, only one volume assigned to PC1_2
154
IBM SAN Implementation
Viewing changes on the Graphical View panel
Now we want to see the changes on the Storage Allocation — Graphical View
panel. Figure 2-108 and Figure 2-109 show the selected host FC ports PC1_1
and PC1_2 with the disk groups that contain volumes that are assigned to it.
Figure 2-108 No volume assignment to PC1_1 in disk group 2 of cluster 1 loop B
Figure 2-109 No volume assignment to PC1_2 in disk group 2 of cluster 1 loop B
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration
155
The space of the disk groups that contains ESS logical volumes that are assigned
to the selected host FC port show up in purple, and unused space in green.
Both host FC ports have no ESS logical volumes assigned to them in the disk
group in cluster 1, adapter pair four, loop B. This is indicated by the absence of
colors.
However, on the particular disk group space is allocated for volumes. This means
that there is an existing volume (or more), which is not yet assigned to any host
FC port. To make this allocated space visible, we press the View All Storage
button and see all the allocated space on the disk groups. This is shown in
Figure 2-110.
Figure 2-110 Unassigned volume(s) in disk group 2 of cluster 1 loop B
Allocated, but unassigned, volumes are indicated by the yellow colored space in
the disk group. The space in the other disk groups, that contains allocated and
assigned volumes shows up in the color red.
156
IBM SAN Implementation
Another way to find out about the state of the space in a disk group is to select it.
In our example, shown in Figure 2-111, we select the disk group in which we
have an unassigned volume.
Figure 2-111 Disk group selected, unassigned volume(s) in selected disk group
Again, the space used for unassigned volumes is displayed in yellow. Also, we
see in the host interfaces row the interfaces that have volumes assigned to them
in the selected disk group, which is empty.
Viewing Changes on the Tabular View
Pressing the tabular View button from within the Storage Allocation — Graphical
View panel, displays the table containing all existing volume assignments, as
shown in Figure 2-112.
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration
157
Figure 2-112 Tabular View, four volume assignments, three volumes
Here we see that there is no longer any assignment for the volume we
unassigned. Unassigned volumes only show up in the Volume Assignments table
in the Modify Volume Assignments panel.
Now, as we have ESS logical volumes assigned to host FC ports, and we have
also made adjustments to the configuration, there is only one step left to be
performed.
2.7 Configuring ESS FC ports
The only configuration part left to enable us to access the volumes is the
configuration of the ESS FC ports for the topology that the ports are going to
connect to. This configuration step does not depend on any other configuration,
so we left it until we had finished the volume configurations.
158
IBM SAN Implementation
As we already know, the selection of an entity in the Storage Allocation —
Graphical View panel changes the information in the Information frame of the
panel. Clicking on an icon of an ESS FC port in the ESS interfaces row displays
information about the adapter. There we see the physical location in the ESS, the
topology the port is configured for and the WWPN. For any ESS FC port that we
have not configured, the window looks like that shown in Figure 2-113.
Figure 2-113 Information frame, ESS FC port topology undefined
2.7.1 Defining the topology for ESS FC ports
Pressing the Configure Host Adapter Ports button takes us to the Configure
Host Adapter Ports panel as shown in Figure 2-114.
Figure 2-114 Entry point for configuring ESS FC ports
Again, the naming convention in the ESS Specialist can be a little misleading.
The ESS has built in Fibre Channel adapters which provides the connectivity to
the SAN. An ESS, in its simplest form, is a Fibre Channel attached storage
device, not a host. We will refer to such a device as an ESS FC port to avoid any
confusion.
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration
159
Selecting the interface port to be configured
The Configure Host Adapter Ports panel is shown in Figure 2-115.
Figure 2-115 Configure Host Adapter Ports panel, ESCON port selected
From this panel, we select the port of the ESS interface adapters to be
configured, depending on the type of the adapter. We can select the ports by
clicking on the icons of the adapter (left or right on any adapter with two ports), or
by selecting the port from the drop down list as shown in Figure 2-116.
160
IBM SAN Implementation
Figure 2-116 Port selection drop down list, SCSI port selected
There is no configuration necessary for ESCON. There are different
configuration options for SCSI and Fibre Channel. However, we will focus on the
FC part.
By selecting an FC port, we are presented with the panel, as shown in
Figure 2-117.
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration
161
Figure 2-117 Configure Host Adapter Ports panel, FC port selected
The port we used is in bay 1, adapter 3, and is port A. It is called ‘A’ even if it is
the only port on the adapter.
Understanding the Storage Server Attributes field
As shown in Figure 2-118, the Storage Server Attributes field — also known as
the logical unit number (LUN) access mode — which specifies the channel
access mode, can only be changed by an IBM SSR using the service terminal.
Figure 2-118 Storage Server Attributes field, ESS configured for Access_Restricted
162
IBM SAN Implementation
There are two Fibre Channel Access Modes to which the ESS can be configured:
 Access_Any
In Access_Any mode, any host FC port that is not defined in the ESS
Specialist, can access all non-AS/400, ESS logical volumes. In Access-Any
mode, the ESS Specialist displays an anonymous pseudo-host FC port icon,
which is shown in Figure 2-119 and which is taken from another ESS,
because the one we used here is configured for Access_Restricted. An
anonymous host FC port is not a real host FC port in disguise and connected
to the storage server. It represents all host FC ports (if any) that are
connected to the ESS and that are not configured on the ESS. The
anonymous host FC ports do not have an access profile defined. You can
access specific ESS logical volumes that are defined in the ESS, by host FC
ports that are not identified by the ESS.
 Access_Restricted
In Access_Restricted mode, a connected host FC port, which is not
configured with the WWPN, cannot access any ESS logical volume. When
this host FC port gets configured by using the WWPN, it will only see the
volumes for which it is configured. Once a host FC port is configured, there
are no differences.
Figure 2-119 Anonymous host FC port icon in an ESS configured for Access_Any
Understanding access profiles
Whichever access mode is chosen, any host FC port that has an access profile
can access only those volumes that are defined in the profile. Depending on the
capability of the particular host operating system, an access profile can contain
up to 256 or up to 4096 volumes.
The setup of an access profile is transparent to the user when using the ESS
Specialist to configure the host FC ports and ESS logical volumes in the ESS.
Configuration actions that affect the access profile are:
 Configuring the host FC port in the ESS with its WWPN creates the access
profile for that host FC port. Initially the profile is empty. That is, it contains no
ESS logical volume assignments. The host FC port cannot access any ESS
logical volumes that are already defined in the ESS.
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration
163
 Adding new ESS logical volumes to the ESS, the new volumes go to the host
FC port that is selected.
 Assigning ESS logical volumes to host FC ports, means adding them to the
access profile of the selected host FC port and to pre-existing ESS logical
volumes.
Removing a host FC port from the ESS, means deleting the host FC port
definition and its access profile.
2.7.2 ESS managed ESS FC port WWPNs
Beginning with LIC level LBLD0312, there is a new function that allows the ESS
to locally administer the WWPNs for the ESS FC ports. This means the ESS FC
ports will have WWPNs which do not change when replacing an adapter. This is
especially useful if SDD is used for multipathing and when zoning is implemented
using the WWPNs of the ESS FC port.
Activating the WWPN naming convention
The activation of this feature for all of the ESS adapters requires a 45 minute
nonconcurrent service action and must be carried out by an IBM CE. Once this
feature has been activated by the CE, this is done from the service menu by
selecting:
1. Select Configuration Options Menu.
2. Select Change/Show Control Switches.
3. Fibre Channel WWPN Method - Standard should be displayed, and if so,
press the Enter key.
4. Press PF4, select WWNN, and then press Enter.
5. When instructed, IML the ESS.
From the time of activation onwards, all built in ESS FC ports and all new ESS
FC ports will have the locally administered WWPNs. However, even if the feature
is not activated, any replaced or added adapters will adopt the new locally
administered WWPN.
Host and switch considerations
After the CE has performed this service action and the naming convention has
been successfully changed from Standard to WWNN, there are some actions
that will need to be performed on the attached hosts and, in some cases, the
fabric components, in order to allow the host FC adapter to successfully login
using the new WWPN.
164
IBM SAN Implementation
These actions are host dependent. With respect to the fabric components, if
WWPN zoning has been implemented, then it will be necessary to update every
instance of the WWPN in the switches and/or directors.
The WWPNs of the adapter are built from the WWNN of the ESS and the
location of the adapter in the ESS interface bays. This is done using the pattern
shown in Figure 2-120.
World Wide Port Name
50:05:07:63:00:C3:0C:0D
C4 C3 C2 C1
Interface Bay 1
CC CB CA C9
C8 C7 C6 C5
D0 CF CE CD
Interface Bay 2
Interface Bay 3
Interface Bay 4
World Wide Node Name
50: 05: 07: 63: 00: C0: 0C: 0D
xx: xx: xx: xx: xx: yy: xx: xx
Figure 2-120 Pattern for the generation of the WWPNs of the ESS FC ports
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration
165
The Information frame on the Storage Allocation — Graphical View panel reflects
the new WWPNs of the ESS we have used for this illustration, which is shown in
Figure 2-121.
Figure 2-121 Information Frame, reflecting the new locally administered WWPN
In Figure 2-122 we show the WWNN of the ESS that is used and modified when
this feature is enabled.
Figure 2-122 WWNN of the ESS with locally administered WWPNs
What we also see in the information frame is that this is an ESS which has ESS
FC ports that are also FICON capable. This adapter indicates that it is configured
for FCP and not for FICON.
166
IBM SAN Implementation
2.7.3 Configuring host FC ports for FC-SW and FC-AL
Now, as we have selected the first ESS FC port, we are going to configure this
and two other ports to be able to communicate with our host FC ports. The first
two ports we configure for use in a switched fabric environment and the second
are for use in an arbitrated loop environment.
Selecting the topology for the ESS FC ports
The pull down list in the FC Port Attributes field as shown in Figure 2-123, is for
selecting the topology the port is going to be connected to.
Figure 2-123 Pull down list, selected port currently undefined
The selected ESS FC port in bay one adapter three we start with is unconfigured.
Because of this, we can choose by selecting between Fibre Channel Point to
Point and Fibre Channel Arbitrated Loop. If a port is already configured for one
topology and it has to be changed to another, the port must first be undefined.
Then it is possible to choose the appropriate topology.
We can choose between Fibre Channel Arbitrated Loop for FC-AL and Fibre
Channel Point-to-Point for FC-PP and for FC-SW. Some adapters — for
example, the IBM FC6227 — operate in arbitrated loop mode even though they
are directly connected to an ESS. This means that the ESS port will have to be
configured in FC-AL mode.
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration
167
As we have selected the topology for the selected ESS FC port, we see a small
red line directly below the icon of the just-defined ESS FC port, as shown in
Figure 2-124.
Figure 2-124 ESS FC port for Point to Point defined
This indicates that the port definition has been changed. We can now go on and
select and define the other ports. The red lines will remind us where we made
definition changes.
Now we go on and define port three in bay four for FC-SW and adapter three in
bay two for FC-AL. The panel then indicates us what port definitions have been
changed as shown in Figure 2-125.
168
IBM SAN Implementation
Figure 2-125 ESS FC port for Arbitrated Loop defined
Resetting changes made to a selected ESS FC port
Using the Reset Selected Port button on the upper right of the screen, we can
reset the definition for the selected port to the status the port was in before we
made any changes.
This brings up a warning window as shown in Figure 2-126, stating that the
configuration changes made are going to be discarded.
Figure 2-126 Warning window, configuration changes are going to be discarded
We do not want to reset our changes, so we are going to perform the changes.
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration
169
Performing the configuration update
Click on the Perform Configuration Update button. During the process of
performing the update we get a progress window as shown in Figure 2-127.
Figure 2-127 Progress window, changing the topology
Figure 2-128 shows a successful topology change of the ports.
Figure 2-128 Information window, successful topology change
Pressing the OK button takes us back to the Open System Storage panel.
Viewing changes in the Graphical View panel
The changed topology settings are reflected in the Storage Allocation —
Graphical View panel. Now when we click on one of the ESS FC ports that we
just configured, the information frame reflects the changes to the topology.
170
IBM SAN Implementation
For port three in bay one, which is now configured for use with FC Point to Point,
this is shown in Figure 2-129. For port three in bay two, which is now configured
for use with FC Arbitrated Loop, this is shown in Figure 2-130.
Figure 2-129 Information frame, ESS FC port topology Point to Point
Figure 2-130 Information frame, ESS FC port topology Arbitrated Loop
We have now prepared the ESS to provide storage to our hosts.
We have arrived at the end of journey! Here is our last picture of the Storage
Allocation — Graphical View panel, shown in Figure 2-131.
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration
171
Figure 2-131 Storage allocation now completed
We see that the host FC port PC1_2 is restricted to see the one volume it has left
through one FC port which is configured for point to point.
Related information: For more information on the ESS, see these references:
IBM Enterprise Storage Server Introduction and Planning Guide, 2105 Models
E10, E20, F10 and F20, GC26-7294
 Introduces the product and lists the features you can order. It also provides
guidelines on planning for the installation and configuration of the ESS.
IBM Enterprise Storage Server User’s Guide, 2105 Models E10, E20, F10 and
F20, SC26-7295
 Provides instructions for setting up and operating the ESS.
IBM Enterprise Storage Server Host Systems Attachment Guide, 2105 Models
E10, E20, F10 and F20, SC26-7296
 Provides guidelines for attaching the ESS to your host system.
172
IBM SAN Implementation
IBM Enterprise Storage Server SCSI Command Reference, 2105 Models E10,
E20, F10 and F20, SC26-7297
 Describes the functions of the ESS. It provides reference information for
UNIX and AS/400 hosts, such as channel commands, sense bytes, and error
recovery procedures.
IBM Enterprise Storage Server System/390 Command Reference, 2105 Models
E10, E20, F10 and F20, SC26-7298
 Describes the functions of the ESS and provides reference information for
System/390 hosts, such as channel commands, sense bytes, and error
recovery procedures.
ESS Web Interface User’s Guide for ESS Specialist and ESS Copy Services,
SC26-7346
 Provides instructions for using the IBM TotalStorage Enterprise Storage
Server Web interface, ESS Specialist.
IBM Storage Solutions Safety Notices, GC26-7229
 Provides translations of the danger notices and caution notices that IBM uses
in ESS publications.
IBM Enterprise Storage Server Configuration Planner, SC26-7353
 Provides work sheets for planning the logical configuration of the ESS. This
book is not available in hard copy. This book is only available on the following
Web site:
http://www.storage.ibm.com/hardsoft/products/ess/refinfo.htm
IBM Enterprise Storage Server Quick Configuration Guide, SC26-7354
 Provides flow charts for using the TotalStorage Enterprise Storage Server
Specialist. The flow charts provide a high-level view of the tasks the IBM
service support representative performs during initial logical configuration.
You can also use the flow charts for tasks that you might perform during
modification of the logical configuration.The hard copy of this booklet is a
9-inch by 4-inch fanfold.
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration
173
174
IBM SAN Implementation
3
Chapter 3.
Implementing the IBM
Managed Hub and
Unmanaged Hub
In this chapter we review the IBM SAN Fibre Channel Hub and the IBM
TotalStorage SAN Managed Hub. We cover the installation steps for both
devices.
We discuss the management and implementation of the Managed Hub, and
show how to use its QuickLoop feature and QuickLoop zoning.
The products we describe can be seen as entry level components of a SAN:
 IBM Fibre Channel Storage Hub, 2103-H07
 IBM TotalStorage SAN Managed Hub, 35341RU
© Copyright IBM Corp. 2001
175
3.1 IBM Fibre Channel Storage Hub, 2103-H07
The Fibre Channel Storage Hub is an entry level component for SAN fabric
installations designed for connecting one or more storage devices, to one or
more servers. It is not a very scalable solution and should not be chosen if many
devices are to be connected later. A hub can also be used to connect to a remote
location to extend the distance.
The Fibre Channel Storage Hub is designed to provide a centralized point of
connectivity, to provide loop fault tolerance, and to simplify configuration
management.
Fibre Channel products that are commonly interconnected to the Fibre Channel
Hub are Fibre Channel host bus adapters, FC-AL storage devices, and FC-AL
storage arrays.
In terms of scalability of bandwidth, one FC-AL loop by itself is not scalable. All
devices share the bandwidth of 100 MB/s, rather than that offered by the
Managed Hub.
The IBM Fibre Channel storage Hub 2103-H07 used in our first scenario, is a
7-port central interconnection for Fibre Channel Arbitrated Loops that follow the
ANSI FC-AL standard. In Figure 3-1 we show the hub.
Figure 3-1 IBM Fibre Channel Storage Hub
176
IBM SAN Implementation
3.1.1 Hub configuration
The IBM Fibre Channel Storage Hub interconnects multiple servers and storage
systems, over fiber-optic media, and transfers data at speeds up to 100 MB/s.
Each port requires a gigabit interface converter to connect it to each attached
node. The Fibre Channel Storage Hub supports any combination of shortwave or
longwave optical GBICs. We show a GBIC in Figure 3-2.
Figure 3-2 Gigabit Interface Converter
The GBICs are hot-pluggable into the IBM Fibre Channel Storage Hub, which
means you can add host computers, servers, and storage modules to the
arbitrated loop dynamically, without powering off the Fibre Channel Storage Hub
or any connected devices.
If you remove a GBIC from a Fibre Channel Storage Hub port, that port is
automatically bypassed. The remaining hub ports continue to operate normally
with no degradation of system performance. Conversely, if you plug a GBIC into
the Fibre Channel Storage Hub, it will automatically be inserted and become a
node on the loop, if valid Fibre Channel data is received from the device.
Chapter 3. Implementing the IBM Managed Hub and Unmanaged Hub
177
3.1.2 Hub installation
Figure 3-3 is the front panel of the IBM Fibre Channel Storage Hub, 2103-H07.
Figure 3-3 FC Storage Hub 2103-H07 front panel
The picture shows the front panel with the seven slots for GBICs. After GBIC
installation, they represent the FC Storage Hub ports 0 to 6.
GBIC insertion
The Unmanaged Hub is as close to plug-and-play as you are likely to encounter
in a SAN installation. Of course, there is more to consider, but in our installation,
we will show how to install GBICs for those that are new to the Fibre Channel
world. To insert the GBIC, follow these steps:
1. Remove the plastic cover from the GBIC.
2. Slide the GBIC into the port.
3. Connect the fiber-optic cable into the installed GBIC.
The GBIC housing has an integral guide key that is designed to prevent improper
insertion. This is shown in Figure 3-4.
Figure 3-4 Insert cable into GBIC
178
IBM SAN Implementation
4. Once you have installed the GBICs in your hub, attach the hub ports, using
standard 50/125 or 62.5/125 FC cable, to your Fibre Channel host and
storage device.
To check that the connections to the hub are working, you can view the Device
Active LEDs on the FC Storage Hub ports.
3.2 IBM TotalStorage SAN Managed Hub
The IBM TotalStorage SAN Managed Hub, 35341RU, is an 8-port Fibre Channel
hub that consists of a system board with connectors for supporting up to eight
ports. This includes seven fixed, short wavelength ports, one pluggable GBIC
port, and an operating system for building and managing a switched loop
architecture.
The Managed Hub is a non-blocking architecture that provides 8 x 100MB/sec
throughput.
The hub is supported on IBM PC, Netfinity servers, and other Intel-based
servers. Shown in Figure 3-5 is a picture of the Managed Hub with a shortwave
GBIC and a longwave GBIC.
Figure 3-5 IBM TotalStorage SAN Managed Hub
Chapter 3. Implementing the IBM Managed Hub and Unmanaged Hub
179
The latest support matrix, including adapters and operating system
requirements, can be found at the following Web page:
http://www.storage.ibm.com/hardsoft/products/fchub/msupserver.htm
In Figure 3-6, we show the faceplate of the IBM TotalStorage SAN Managed Hub,
35341RU. The ports are numbered sequentially, starting with zero for the
left-most port.
Figure 3-6 IBM TotalStorage SAN Hub faceplate
The system board is enclosed in an air-cooled chassis, which may be either
mounted in a standard rack or used as a stand-alone unit.
The chassis includes a power supply, an RJ-45 Ethernet connection for 3534
Managed Hub set up and management, and a serial port. If the default address is
not known, the serial port is used for recovering the factory settings and initial
configuration of the IP address.
The Managed Hub can accommodate one GBIC module and can be connected
to one other Managed Hub, to expand the loop capabilities to 14 ports. It can
also be connected with a single port into a SAN fabric as a loop extension.
The Managed Hub may be configured using the serial port or the 10/100BaseT
Ethernet port. Management interfaces include Telnet or Web-based
management using the IBM StorWatch SAN Managed Hub Specialist. This is
similar to the StorWatch Fibre Channel Switch Specialist.
The Managed Hub supports either the 50/125 or 62.5/125 Short Wave Length
(SWL) cable when attached to a shortwave GBIC or through 9/125 Long Wave
Length (LWL) cable when attaching to the longwave GBIC.
180
IBM SAN Implementation
Fibre Channel Storage Hubs are designed to provide a centralized point of
connectivity, to provide loop fault tolerance, and to simplify configuration
management. Specifically designed for entry-level workgroup FC-AL
applications, the hubs provide considerable flexibility in configuring loops and
segmenting them for performance or high-profile availability applications.
Performance
The Managed Hub supports a minimum aggregate routing capacity of 4,000,000
frames per second for Class 2, Class 3 and Class F frames. Non-blocking
throughput of up to 8 x 100 MB/s is provided.
Upgrading the Managed Hub to a switch
The Managed Hub can be upgraded to switched fabric capabilities with the Entry
Switch Activation Feature.
The upgrade provides a cost effective, and scalable approach to developing
fabric based SANs. The Entry Switch Activation feature provides the license key
necessary to convert the FC-AL based Managed Hub to fabric capability. This
provides up to eight F_Ports, one of which can be an interswitch link capable port
(E_Port), for attachment to the IBM TotalStorage SAN Fibre Channel Switch or
other supported switches.
The IBM TotalStorage SAN Managed Hub's Entry Switch Activation feature
offers:
 Upgrade to fabric switch capability on all eight ports, F_Ports
 Support for one interswitch link, or E_Port
 Fabric services such as the Simple Name Server and fabric-wide
management
 High-speed performance utilizing non-blocking switch-based technology
 Investment protection for small SAN environments moving from Arbitrated
Loop to switched fabrics
The Entry Switch Activation feature, P/N 19P3127, does not alter any of the
current Operating Environment specifications for the IBM TotalStorage SAN
Managed Hub.
Chapter 3. Implementing the IBM Managed Hub and Unmanaged Hub
181
3.2.1 The ITSO environment
From our ITSO environment, we show how to implement the IBM TotalStorage
SAN Managed Hub, 35341RU.
The ITSO target SAN installation consists of:
 3 x IBM Netfinity 5500s running Windows NT 4.0 Service pack 6a and
Windows 2000 Advanced Server
 1 x Sun E250 server running Solaris V7
 3 x RS/6000 J50
 1 x RS/6000 F50
 1 x 2106-Dxx IBM Modular Storage Server
 1 x 2105-F20 IBM Enterprise Storage Server with native FC adapters
 2 x 2109 S08 IBM SAN Fibre Channel Switch
 1 x 2109-S16 IBM SAN Fibre Channel Switch
 1 x 3534-1RU IBM TotalStorage SAN Managed Hub
 1 x 2108-G07 IBM SAN Data Gateway
 1 x 2108-R03 IBM SAN Data Gateway Router
 1 x Vicom SLIC Router
 Qlogic 2100F Host Bus Adapters
 Qlogic 2200F Host Bus Adapters
 Emulex LP7000 Host Bus Adapters
 Emulex LP8000 Host Bus Adapters
 JNI Host Bus Adapters
3.3 Installation of the Managed Hub
We recommend that you use a pre-installation checklist.
An example of a pre-installation checklist is detailed in the IBM SAN Fibre
Channel Managed Hub 3534 Installation and Service Guide, SY27-7616 and the
IBM SAN Fibre Channel Managed Hub 3534 User’s Guide, GC26-7391.
These manuals can downloaded from the following Web site:
http://www.storage.ibm.com/hardsoft/products/fchub/refinfo.htm
The checklist ensures a successful installation and includes checks on the host
operating system, host bus adapter, storage devices, cables and network
parameters, the most important of which is the Managed Hub IP address.
182
IBM SAN Implementation
3.3.1 Setting the IP address
The 3534 Managed Hub is shipped from the factory with a default IP address
(10.77.77.77). This IP address is printed on the label on the top front edge of the
3534 Managed Hub. This address is for the external Ethernet connection.
If you can, use this default address to attach to your local area network to
establish a network connection to the hub. In Figure 3-7 we show the Ethernet
and serial port locations.
Figure 3-7 IBM TotalStorage SAN Hub management ports
To the right of the power supply is the serial connection, and furthest to the right
is the ethernet port.
You can change this IP address later using a Telnet command, or by using the
StorWatch Specialist, issued from any server having access to the same LAN.
This is the easiest way to set the IP address.
Your system or network administrator will advise if the default address can be
used.
If using the default IP address is not possible, the IP address will have to be set
using the Ethernet port or the serial port. Set the IP address using the
information provided by the system administrator and record this on the
pre-installation checklist.
For a comprehensive description of how to set the IP address, using either the
serial, or the Ethernet port, refer to IBM SAN Fibre Channel Managed Hub 3534
Installation and Service Guide, SY27-7616.
The Managed Hub we used in our test scenario had been installed before, and
we had to change the IP address.
Chapter 3. Implementing the IBM Managed Hub and Unmanaged Hub
183
Setting the IP address using the Ethernet port
We show how to set the hub IP address by using the Ethernet port.
1. Attach the LAN to the front panel of the hub by plugging an existing Ethernet
10/100BaseT LAN cable to the RJ-45 connector on the front of the hub.
2. Turn on the hub by plugging it into an electrical outlet. Make sure that the
power cord is fully seated into the front of the unit, and the green ready LED is
on. Wait two minutes for diagnostics to complete.
3. From a LAN attached server, type the Telnet IP address.
For example, issue the command: Telnet 193.1.1.27
If this is the initial installation, use the default IP address found on the label on
the top left corner of the 3534 Managed Hub. If the 3534 Managed Hub has
been installed before using the IP address on the label, continue using the
current address from the label. If the IP address on the label was not used,
you will need to get the current IP address from the system administrator.
After the Telnet command has been issued, the Managed Hub will respond as
shown in Figure 3-8.
At each prompt, type in the information as shown and press Enter. The default
login is admin, and the default password is password.
Figure 3-8 Telnet logon screen
4. At the prompt, enter the command: ipAddrSet
This is the command to set the IP address, and the result is shown in
Figure 3-9.
184
IBM SAN Implementation
Figure 3-9 Checking the IP address of the Managed Hub
The current Ethernet IP address is shown. Now you can enter your new
address. Press Enter to keep the old one.
5. Ethernet Subnetmask [Current Subnetmask will be shown or None]: New
Subnetmask or press Enter.
This is the new Subnetmask from your system administrator or, if none is
required, press Enter.
6. Fibre Channel IP Address [None]: Press Enter.
Fibre Channel Subnetmask [None]: Press Enter.
7. Gateway Address [Current Gateway address or None]: enter new Gateway
address or press Enter.
This is the Gateway address the system administrator provided or, if none is
required, press Enter.
8. Ipaddress:admin> logout
This process, in step 5 through step 8, is shown in Figure 3-10.
In the example shown, we did not change the IP address; however, the process
illustrates how the addressing can be changed.
The final prompt will ask if you want to set the IP address to the new value now.
Entering ‘Y’ installs the new value; Typing ‘N’ delays the change until the next hub
restart.
Chapter 3. Implementing the IBM Managed Hub and Unmanaged Hub
185
Figure 3-10 Changing the IP address
9. Ipaddress:admin> logout
This ends the Telnet session. We have completed the installation of the 3534
Managed Hub.
Setting the IP address using the serial port
We also show how to set the hub IP address by using the serial port.
If you also choose to set up the IP address using the serial cable, open a
HyperTerminal session on your laptop, and proceed with these steps.
Note: Opening a HyperTerminal session varies depending on which version of
Windows you are using. With Windows NT to start a HyperTerminal session, go
to Start —> Programs —> Accessories.
You can configure HyperTerminal as follows:
1. We used a laptop with Windows NT 4.0.
Prior to plugging the hub into the electrical outlet, we attached the laptop to it
with the serial cable, female to female, shipped with the hub.
186
IBM SAN Implementation
2. In the Connection Description window, type the name you want to use for your
new session. Select any icon from the icon menu shown, and click OK.
The Connect to window appears. In this window, change the Connect using
setting from the default to Direct to Com1, and click OK.
The COM1 Properties window appears, as shown in Figure 3-11.
Figure 3-11 HyperTerm COM1 properties window
Set the following parameters in the Port Settings tab:
–
–
–
–
–
9600 bits per second
8-bit
No parity
One stop bit
Flow Control = None
Chapter 3. Implementing the IBM Managed Hub and Unmanaged Hub
187
3. Click File —> Properties. The Properties window appears, as shown in
Figure 3-12.
Figure 3-12 HyperTerm File Properties screen
4. Select the Settings tab, set the Emulation field to Autodetect.
5. After this, start up the hub by inserting the power cord into electrical outlet
and waiting for about two minutes for diagnostics to complete. Make sure that
the power cord is fully seated into the front of the unit, and the green ready
LED is on. You may see the log information as the Managed Hub initializes.
6. Press Enter on your laptop.
The hub responds with the prompt:
Admin>
7. The HyperTerminal session is now running. For each prompt, type in the
information as shown and press Enter at the end of each response.
8. Admin> ipAddrSet
This is the command to set the IP address.
9. Ethernet Subnetmask [Current sub net mask will be shown or None]: New
Subnetmask or press Enter.
This is the new Subnet mask from your system administrator or, if none is
required, press Enter.
188
IBM SAN Implementation
10.Fibre Channel IP Address [None]: Press Enter.
Fibre Channel Subnetmask [None]: Press Enter.
11.Gateway Address [Current Gateway address or None]: enter new Gateway
address or press Enter.
This is the Gateway address the system administrator provided or, if none is
required, press Enter.
12.Ipaddress:admin> logout
This ends the Serial port session. You have completed the installation of the
3534 Managed Hub by using the serial port. Remove the cable from the serial
port connector.
Downloading new Firmware levels
The hub is shipped with the latest level of code (firmware) available. However,
new code is periodically released that you can easily download to the hub. This
task requires that you save data and executable software to your server. This
should all be downloaded into the same directory. The latest code can be
obtained from the IBM TotalStorage SAN Managed Hub, 35341RU Web site:
http://www.storage.ibm.com/hardsoft/products/fchub/form.htm
Shown are the procedures to download the firmware to the switch using Telnet
and then using the IBM Storwatch Managed Hub Specialist.
By following the link given above, you will be prompted to fill out a registration
page and will then be asked to agree to the IBM Licensing Terms.
Once you have completed these, you will get to the screen shown in Figure 3-13.
Chapter 3. Implementing the IBM Managed Hub and Unmanaged Hub
189
Figure 3-13 Download the latest firmware levels
You will also need to download the latest version of the utilities, as shown in
Figure 3-14.
190
IBM SAN Implementation
Figure 3-14 Download the latest version of the RSHD and CAT utilities
Upgrading the Firmware using Telnet
By starting a Telnet session from a DOS command prompt, we can log in to the
Managed Hub, as shown in Figure 3-15.
Figure 3-15 Telnet to the Managed Hub using a DOS window
Chapter 3. Implementing the IBM Managed Hub and Unmanaged Hub
191
This will present the screen shown in Figure 3-16. From here we logon to the
Fabric OS operating system as shown.
Figure 3-16 Logon to the Managed Hub via Telnet
Before downloading the Firmware, we need to run the RSH daemon as shown in
Figure 3-17.
Figure 3-17 Starting the RSH daemon
192
IBM SAN Implementation
Once the RSH daemon is started, you will see a similar screen to that shown in
Figure 3-18. The symbol underneath the word rshd will rotate to indicate that the
RSH daemon is active.
Figure 3-18 Confirm the RSH daemon is running
Once you have established that the RSH daemon is running, you can download
the firmware as shown in Figure 3-19 by issuing the firmwaredownload
command.
You need to specify the host IP address of the host where you downloaded the
firmware to, the hostname and the full directory and filename of where the
firmware is located.
If you do not know the hostname or the host IP address, then open a DOS
command prompt and issue the following commands:
hostname
This returns the host name.
ipconfig
This returns the IP address of the host.
Figure 3-19 Issuing the Firmwaredownload command
Chapter 3. Implementing the IBM Managed Hub and Unmanaged Hub
193
Once this has completed, the switch will need to be re-booted to activate the new
new firmware level, as shown in Figure 3-20. This will then activate the new
firmware within the Managed Hub.
Figure 3-20 Re-booting the Managed Hub
Upgrading the Firmware using the Managed Hub Specialist
To upgrade the firmware using the Managed Hub Specialist, go to the Admin
View as shown in Figure 3-21.
Figure 3-21 Launch the Admin View
194
IBM SAN Implementation
This will display the Switch Admin screen, as shown in Figure 3-22.
Figure 3-22 Switch Admin screen
Chapter 3. Implementing the IBM Managed Hub and Unmanaged Hub
195
Select the Firmware Upgrade tab, as shown in Figure 3-23.
Figure 3-23 Firmware Upgrade screen
To download the firmware into the Managed Hub, specify the IP address for the
host system, and the directory and file name where the firmware resides, as
shown in Figure 3-24. Also, make sure that the RSH daemon is running and
select it from the drop-down list.
If you do not know the hostname or the host IP address then open a DOS
command prompt and issue the following commands:
196
hostname
returns the host name
ipconfig
returns the IP address of the host
IBM SAN Implementation
Figure 3-24 Upgrading the Firmware using the Managed Hub Specialist
After a minute or so a screen similar to the one shown in Figure 3-25 will be
displayed.
Figure 3-25 Firmware download message
From here, you can proceed to reboot the Managed Hub.
This will take you to the screen shown in Figure 3-26. From here we perform a
fastboot of the Managed Hub.
Chapter 3. Implementing the IBM Managed Hub and Unmanaged Hub
197
Figure 3-26 Fastboot the Managed Hub after downloading the firmware
The screen shown in Figure 3-27 is displayed and can be closed. You can also
terminate the RSH daemon.
Figure 3-27 Reboot in progress message
To check the firmware level, go to the Fabric View screen, as shown in
Figure 3-28.
Figure 3-28 Firmware revision level
198
IBM SAN Implementation
We can see that the firmware level is 2.2.1a.
3.4 QuickLoop
Fibre Channel provides three distinct interconnection topologies.The three Fibre
Channel topologies are:
 Point-to-point
 Arbitrated loop
 Switched — referred to as a fabric
The IBM 3534 Managed Hub that has not been upgraded to a switch is a Fibre
Channel Arbitrated Loop device.
A simple loop, configured using a hub, is shown in Figure 3-29.
Client
Open Server
Open Server
Hub
Client
Client
JBOD
Figure 3-29 Arbitrated Loop
There are two different kinds of loops, the private and the public loop.
Chapter 3. Implementing the IBM Managed Hub and Unmanaged Hub
199
3.4.1 Private loop
The private loop does not connect with a fabric, only to other private nodes using
attachment points called Node Loop Ports (NL_Ports). A private loop is enclosed
and known only to itself. NL_Ports can only attach to other NL_Ports or to Fabric
Loop Port (FL_Ports).
In Figure 3-30, we show a private loop.
Hub
Open Systems
Server
Client
Disk
Tape
Figure 3-30 Private Loop
3.4.2 Public loop
A public loop requires a fabric, and has at least one FL_Port connection to a
fabric. A public loop extends the reach of the loop topology by attaching the loop
to a fabric. FL_Ports can only attach to NL_Ports.
In Figure 3-31, we show a public loop.
200
IBM SAN Implementation
FCP
Switch
FC_AL
Hub
FC_AL
Open Systems
Server
Client
Disk
Tape
Figure 3-31 Public loop
3.4.3 Private devices in public fabrics
The characteristic of a fabric is allowing communication between any host or
storage device in the fabric. In other words, all communication is “public”.
Problems may arise when a private Fibre Channel device is attached to a switch.
Private Fibre Channel devices were designed to only work in private loops.
For more details about how node and port addressing works, refer to Designing
an IBM Storage Area Network, SG24-5758.
3.4.4 QuickLoop feature
QuickLoop applies to both the IBM managed hub and the IBM 2109 switch. On
the managed hub, QuickLoop is always in effect, on the switch, QuickLoop must
be enabled at a port level.
Chapter 3. Implementing the IBM Managed Hub and Unmanaged Hub
201
If you have a private host (server), communication of a public nature is not
possible. To solve this issue, switch vendors, including IBM, support a QuickLoop
feature, or a feature which allows public to private, or private to public bridging.
QuickLoop creates a unique Fibre Channel topology, that allows host bus
adapters that use Fibre Channel Arbitrated Loop (FC-AL) without knowledge of
the SAN fabric (that is to say, an adapter that cannot perform fabric login),
commonly referred to as private loop initiators, to communicate with Fibre
Channel Arbitrated Loop public storage devices. This can also include IBM 2109
Fibre Channel Switches.
QuickLoop allows individual switch ports to be designated as arbitrated loop
ports, allowing a private loop host initiator to communicate with arbitrated loop
storage devices as though they were all contained in one logical loop.
The QuickLoop feature supports legacy devices. Legacy devices are those that
are in a Private Loop Direct Attach (PLDA) environment. The QuickLoop feature
allows these devices to be attached to a SAN and operate no differently than in a
PLDA environment.
As opposed to the IBM SAN Fibre Channel Switch, where you have the option of
defining QuickLoop ports, the IBM TotalStorage SAN Managed Hub, 35341RU
ports work in QuickLoop mode as a default.
For a list of supported devices for the IBM 3534, see the Web site:
http://www.storage.ibm.com/hardsoft/products/fchub/msupserver.htm
In a simple scenario with one host, a single hub, and some storage devices, it
does not matter if we have a private or public loop or if there is a fabric.
Having a hub, rather than a switch, has an impact on the performance, and
integrating the hub with QuickLoop into a SAN fabric is beneficial.
If the hub, with its arbitrated loop devices, is part of a larger SAN fabric that
includes multiple 2109 switches, it is possible to expand the number of ports in
the QuickLoop (called looplets) to the total of the hub ports plus the ports of one
IBM SAN Fibre Channel Switch.
For example:
 7 hub ports + 7x 2109-S08 ports = total of 14 NL_Ports
 7 hub ports + 15x 2109-S16 ports = total of 22 NL_Ports
There are two options with regard to how a hub is employed in this manner:
 As a single-hub: all looplets of a QuickLoop reside in one hub.
202
IBM SAN Implementation
 In a Hub-Switch combination: looplets of a QuickLoop span across hub plus
switch.
In Figure 3-32, we show high-performance, multi-target connectivity to a single
PLDA, where all the ports of the hub operate in QuickLoop mode. The hub
serves as a concentrator.
Servers
Managed
Hub
Disks
Figure 3-32 QuickLoop using managed hub
In Figure 3-33 we show how the QuickLoop feature supports legacy devices.
The legacy devices refer to devices that are in a PLDA environment.
The QuickLoop feature allows these devices to be attached to a Storage Area
Network and operate no differently than if they were in a PLDA environment.
When QuickLoop mode is enabled, all ports defined as QuickLoop ports on the
switch behave as if they are one logical Fibre Channel Arbitrated Loop.
The switch needs the QuickLoop facility available from IBM as RPQ 8S0521.
RPQ 8S0521 is a licensed product requiring a valid license key. The RPQ
8S0521 License Agreement is covered by the IBM Agreement for the Licensed
Internal Code and is linked to the serial number of the hub.
Chapter 3. Implementing the IBM Managed Hub and Unmanaged Hub
203
Servers
2109
switch
Managed
Hub
Disks
Figure 3-33 QuickLoop spanning to switch
Both configurations allow up to 126 NL_Port devices in one QuickLoop.
Managing QuickLoop
To manage QuickLoop for the IBM 3534 Managed Hub, you can choose from two
methods:
 Using Telnet commands
 Using the Managed Hub StorWatch Specialist
204
IBM SAN Implementation
Figure 3-34 shows the Managed Hub / switch combination we used in our ITSO
scenario.
Figure 3-34 ITSO SAN fabric
To administer the QuickLoop facility, launch the Switch View as shown in
Figure 3-35 for the Managed Hub.
Figure 3-35 Launch Admin View
Chapter 3. Implementing the IBM Managed Hub and Unmanaged Hub
205
Selecting the QuickLoop Admin tab will display the screen shown in
Figure 3-36.
Figure 3-36 QuickLoop Admin screen
In Figure 3-37, we expanded the number of looplets (ports) in the private loop by
bringing in a QuickLoop partner, itsosw3.
You have two options:
 Select a QuickLoop partner and enter its WWN.
 Select None.
Refreshing the QuickLoop Admin screen will display the screen shown in
Figure 3-38.
206
IBM SAN Implementation
Figure 3-37 Selecting a QuickLoop partner
Figure 3-38 QuickLoop partner established
Chapter 3. Implementing the IBM Managed Hub and Unmanaged Hub
207
Telnet QuickLoop commands are also supported, and these are described in
IBM 3534 SAN Fibre Channel Managed Hub User’s Guide, GC26-7391.
3.4.5 Managed hub zoning
The IBM TotalStorage SAN Managed Hub, 35341RU, is able to use zoning for
finer segmentation in the access of devices. Also, it is used to protect devices
against LIP. As the managed hub is always in QuickLoop mode, this means that
all devices on that QuickLoop are subject to LIP exposure. By using zoning, it is
possible to limit the effect of LIP to QuickLoop zones. That is to say, a LIP in one
zone does not cause a LIP in another zone.
Zoning in the IBM 3534 works exactly the same as zoning does in the IBM SAN
Fibre Channel Switch, and can be managed by using Telnet commands or by
using the IBM Storwatch Specialist.
Zoning is described in greater detail in 4.4, “Zoning” on page 334.
3.5 Managing the Managed Hub
We cabled our IBM TotalStorage SAN Hub into our SAN fabric and the Managed
Hub performed a fabric login (FLOGI) and became part of a fabric consisting of
three 2109 switches with a number of hosts and devices configured. Pointing our
Web browser at the IP address for the hub presents the Fabric View screen as
shown in Figure 3-39.
208
IBM SAN Implementation
Figure 3-39 Fabric View showing the Managed Hub in the bottom right hand side
The screens and management procedures for the Managed Hub are almost
identical to those we have described in Chapter 4, “Implementing an IBM
TotalStorage SAN Switch” on page 251. It is not our intention to duplicate work,
so we will restrict ourselves to covering the differences between managing the
hub and a switch.
Chapter 3. Implementing the IBM Managed Hub and Unmanaged Hub
209
3.5.1 Launching the hub specialist
We can launch the Managed Hub Specialist by clicking on the picture of the
Managed Hub as shown in Figure 3-40.
Figure 3-40 Launch the Managed Hub Specialist
This will display the screen shown in Figure 3-41. It is similar to what we have
seen previously, except that the Fibre Channel ports are located next to each
other. The 2109 switches have the ports staggered in two layers.
Note also that seven of the Fibre Channel ports on the Managed Hub are fixed,
unlike the 2109 switches which have removable GBICs on each port.
The functions are the same as with the 2109 and are also license key dependent.
Figure 3-41 Switch Management view for the Managed Hub
210
IBM SAN Implementation
3.5.2 Accessing the Event Log
To launch the Events Log for the Managed Hub, click on the button as shown in
Figure 3-42.
Figure 3-42 Launch the Events screen
This will display the screen shown in Figure 3-43.
Figure 3-43 Events Log for the Managed Hub
As with the 2109, the columns can be moved by dragging and dropping them.
Clicking on the column headings will sort that particular column.
Chapter 3. Implementing the IBM Managed Hub and Unmanaged Hub
211
3.5.3 Beaconing
The Beaconing function can be activated by clicking on the button as shown in
Figure 3-44.
Figure 3-44 Start Beaconing
This will send a signal to the switch that causes an LED light pattern to
continuously flash from side to side on the switch. This command will toggle off
and on. When the lighthouse symbol is lit, beaconing is active on that particular
switch.
3.5.4 Starting Telnet Sessions
Clicking on the button as shown in Figure 3-45 will launch a Telnet Session for
the Managed Hub.
Figure 3-45 Start Telnet session
212
IBM SAN Implementation
The Telnet login screen is shown in Figure 3-46.
Figure 3-46 Telnet session for the Managed Hub
You will need a valid userid and password to log in to the Telnet session.
3.5.5 Performance Information
Performance information can be displayed for all the GBICs and for the switch
itself by clicking on the button as shown in Figure 3-47.
Figure 3-47 Go to the Performance report
Chapter 3. Implementing the IBM Managed Hub and Unmanaged Hub
213
The Performance View will give the send and receive throughput for all the
GBICs installed in the switch as shown in Figure 3-48.
Figure 3-48 Performance Report for the Managed Hub
Each tick in the graph represents one minute. At the bottom of the screen is a
view for the overall performance of the switch.
214
IBM SAN Implementation
3.5.6 Admin View
To launch the Admin View, click on the button as shown in Figure 3-49.
Figure 3-49 Go to the Admin View
Switch Admin
This will display the Switch Admin for the Managed Hub as shown in Figure 3-50.
Chapter 3. Implementing the IBM Managed Hub and Unmanaged Hub
215
Figure 3-50 Switch Admin screen
The main difference with this screen is that the Managed Hub has a QuickLoop
license by default, so a QuickLoop tab is available.
The Switch Admin screen is where we can change the following information:




216
IP address information
Disable / enable a switch
Change the switch name
Check status of ports / disable /enable ports
IBM SAN Implementation
User Admin
Clicking on the User Admin tab will display the screen shown in Figure 3-51.
Figure 3-51 User Admin screen
The User Admin screen is used to:
 Rename logon accounts
 Change passwords
3.5.7 Firmware Upgrade
Clicking on the Firmware Upgrade tab will display the screen shown in
Figure 3-52.
Figure 3-52 Firmware Upgrade screen
Chapter 3. Implementing the IBM Managed Hub and Unmanaged Hub
217
This screen is used to download firmware into the switch and provides an
alternative to using the Telnet commands.
3.5.8 Reboot Switch
Clicking on the Reboot Switch tab will display the screen shown in Figure 3-53.
Figure 3-53 Rebooting the Managed Hub
From here, we can reboot the switch using the normal boot sequence that
performs a Power On Self Test or we can issue a Fastboot. Fastboot will bypass
the POST and as the name implies is quicker. You can also disable the POST
function for normal reboots of the switch.
218
IBM SAN Implementation
3.5.9 SNMP Admin
Clicking on the SNMP Admin tab will display the screen shown in Figure 3-54.
Figure 3-54 SNMP Admin screen
From here, we can set up and manage the SNMP options for the Managed Hub.
Chapter 3. Implementing the IBM Managed Hub and Unmanaged Hub
219
3.5.10 License Admin
The License Admin screen is shown in Figure 3-55.
Figure 3-55 License Admin screen
This will display the configuration options that the switch is licensed for.
From this screen, you can add and remove licenses as required.
220
IBM SAN Implementation
3.5.11 QuickLoop Admin
The QuickLoop Admin screen, as shown in Figure 3-56, is used to modify a
QuickLoop or to set up a partner switch. You can also manage the QuickLoop
features from this screen.
Figure 3-56 QuickLoopAdmin screen
Chapter 3. Implementing the IBM Managed Hub and Unmanaged Hub
221
3.5.12 Config Admin
The Config Admin screen is shown in Figure 3-57.
Figure 3-57 Config Admin screen
This is used to upload the switch configuration file for archiving or to download a
new configuration file from the host.
222
IBM SAN Implementation
The Config Admin screen as shown in Figure 3-58 has an option to display the
Switch Information Report.
Figure 3-58 Go to Switch Information Report
This is a useful report that describes the configuration of the switch (or Managed
Hub). This information can then be printed or can be saved to a file.
In Figure 3-59 we show the Switch Information Report for the Managed Hub that
we have connected into our fabric.
Chapter 3. Implementing the IBM Managed Hub and Unmanaged Hub
223
Figure 3-59 Managed Hub Information Report
224
IBM SAN Implementation
3.5.13 Port Information
To display information on a specific port in the Managed Hub, click on the port as
shown in Figure 3-60.
Figure 3-60 Go to Port Information
This will display the Port Information screen as shown in Figure 3-61.
Figure 3-61 Port Information screen
Chapter 3. Implementing the IBM Managed Hub and Unmanaged Hub
225
The port information view is automatically updated when it is opened and is
refreshed periodically while the view remains open.
The PortStats tab provides information about the transaction speed, reception
speed and volume through the specified port.
The GBIC tab provides information about the GBICs and the information
displayed depends on the type of GBIC installed.
The Loop tab provides information about the loop on a port and includes:




Loop Statistics
Local AL_PA statistics
QuickLoop looplet statistics (is a QuickLoop license is available)
QuickLoop statistics (if a QuickLoop license is available)
The Managed Hub has a single port available in which a removable GBIC can be
installed as shown in Figure 3-62.
Figure 3-62 Go to Port Information for Port_7
This could be either a long wave or short wave GBIC. Similarly, we can display
the port information for this port.
226
IBM SAN Implementation
The Port Information report for Port_7 shown in Figure 3-63 indicates that no
module is present, and shows that the port is available as a Universal Port.
Figure 3-63 Port Information for Port_7
Chapter 3. Implementing the IBM Managed Hub and Unmanaged Hub
227
3.5.14 Fabric Topology
The Fabric Topology report described how the SAN fabric is connected and lists
the ISL between switches, active ports, and the hop counts for each ISL. This
report can be viewed by clicking on the button, as shown in Figure 3-64.
Figure 3-64 Go to Fabric Topology to check status of the Managed Hub
228
IBM SAN Implementation
In Figure 3-65 we show the end of the Fabric Topology Report with the entry for
the Managed Hub.
Figure 3-65 Fabric Topology showing the details for the Managed Hub
Chapter 3. Implementing the IBM Managed Hub and Unmanaged Hub
229
3.5.15 Name Server Table
The Name Server Table contains a list of all the devices connected in the fabric
and also correlates the WWPN / WWN with the Domain ID and port number. The
Name Server Table is accessed as shown in Figure 3-66.
Figure 3-66 Go to the Name Server table
230
IBM SAN Implementation
We have now connected a SAN Data Gateway Router into Port_6 of the
Managed Hub, and pressed the Refresh button, as shown in Figure 3-67.
Figure 3-67 Name Server Table
Chapter 3. Implementing the IBM Managed Hub and Unmanaged Hub
231
This action updated the Name Server Table as shown in Figure 3-68 and
discovered the SAN Data Gateway Router.
Figure 3-68 Displaying the device attached to the Managed Hub
You can also set up the Name Server Table so that it automatically refreshes at
5-second intervals by checking the Auto Refresh box and then entering a value
in the Auto-Refresh Interval box.
232
IBM SAN Implementation
3.6 Zoning and cascading
Zoning is used to set up barriers between different operating environments to
deploy logical fabric subsets by creating defined user groups, or to create test or
maintenance areas, or both, which are separated within the fabric.
Zoning gives you the flexibility to manage a Storage Area Network to meet
different user groups’ objectives.
Zoning components are discussed in greater depth in 4.4, “Zoning” on page 334,
where the same principles apply.
The method used to define zones, zone members, aliases and zone
configurations, and the administration of zones are the same for the IBM
TotalStorage SAN Managed Hub, 35341RU, as they are for the IBM SAN Fibre
Channel Switch.
When you start your SAN business, you might begin working with a simple SAN
fabric with perhaps only one switch and a few ports. But as you start
implementing more and more host and storage devices in your SAN, you will
reach limits where you have to add either more ports, or expand your fabric by
adding more switches.
Interconnecting your first switch with other switches allows you to build much
larger fabrics. Expanding the fabric in this manner is called cascading, which is a
term used for interconnecting multiple switches.
The hub can be connected to one other hub to expand the loop capabilities from
7 to 14 ports. It can also be connected with a single port into a SAN fabric as a
loop extension.
The attribute for interconnecting ports changes to an E_Port (expansion port).
In the examples shown we have connected the Managed Hub into an existing
SAN fabric, thereby cascading the Managed Hub.
Chapter 3. Implementing the IBM Managed Hub and Unmanaged Hub
233
3.6.1 Implementing zoning
The zoning administration and management is performed through the Zone
Admin function on the Fabric View menu, as shown in Figure 3-69.
Figure 3-69 Go to Zone Admin
234
IBM SAN Implementation
3.6.2 Zone Alias Settings
Once you have selected Zone Admin, this will take you to the Zone Aliases
screen. An Alias is a nickname for a port or for a WWPN / WWN and provides a
way of assigning a more meaningful name to a device in the SAN. As our
Managed Hub is connected to an existing SAN fabric, we can see all the zones
and aliases that are defined across the fabric, as shown in Figure 3-70.
Figure 3-70 Zone Admin screen
This shows that Bonnie is an alias for the WWPN of 10:00:00:00:c9:23:c3:05.
From this screen we can also see that the Managed Hub appears as part of the
SAN fabric, and it is displayed as Domain 4 in the Member selection list.
Chapter 3. Implementing the IBM Managed Hub and Unmanaged Hub
235
Clicking on the Alias Name drop-down list as shown in Figure 3-71 will display all
the Aliases defined in the fabric.
Figure 3-71 Zone Admin display of existing Aliases
236
IBM SAN Implementation
3.6.3 Zone Settings
To create a new zone, we select the Zone Settings tab as shown in Figure 3-72.
Figure 3-72 Go to Zone Settings
Chapter 3. Implementing the IBM Managed Hub and Unmanaged Hub
237
To create a new zone, we select the button as shown in Figure 3-73.
Figure 3-73 Create Zone for Managed Hub
This then requests a name for the new zone as shown in Figure 3-74.
238
IBM SAN Implementation
Figure 3-74 Save Zone name
It is worth employing a naming standard that is suitable for your environment.
In this example we are going to consolidate a number of NT servers onto the
Managed Hub to reduce the number of switch ports that we are using.
We then need to create the devices that will be part of the zone. To do this we
select the port (or WWPN / WWN) from the member selection list as shown in
Figure 3-75.
Chapter 3. Implementing the IBM Managed Hub and Unmanaged Hub
239
Figure 3-75 Add Port_0 to Zone for Managed Hub
In this example we are using the port numbers, a process which is referred to as
Hardware Enforced zoning.
240
IBM SAN Implementation
Similarly, we repeat the process for Port_1 as shown in Figure 3-76.
Figure 3-76 Add Port_1 to Managed Hub zone
Chapter 3. Implementing the IBM Managed Hub and Unmanaged Hub
241
We add Port_2 to the Zone in the same way as shown in Figure 3-77.
Figure 3-77 Add Port_2 to Managed Hub zone
242
IBM SAN Implementation
Once all the members are selected we can apply the zoning changes as shown
in Figure 3-78.
Figure 3-78 Apply the new zone configuration
This will commit the changes to the fabric.
It is worth noting that when creating a new zone the zone needs to be added to
the Zone Configuration and it needs to be re-enabled for it to take effect.
Chapter 3. Implementing the IBM Managed Hub and Unmanaged Hub
243
3.6.4 Zone Config Settings
We now go to the Zone Config Settings screen as shown in Figure 3-79.
Figure 3-79 Go to Zone Settings
This will add the recently created zone to the Zone Configuration.
244
IBM SAN Implementation
As shown in Figure 3-80, we select the zone that we have just created and add
this to the currently active configuration member.
Figure 3-80 Add Managed Hub zone to the Primary Configuration
Chapter 3. Implementing the IBM Managed Hub and Unmanaged Hub
245
We now apply the changes to the fabric as shown in Figure 3-81.
Figure 3-81 Apply the changes to the fabric
246
IBM SAN Implementation
Once the changes have been committed to the fabric we can exit the Zone
Configuration Settings screen as shown in Figure 3-82.
Figure 3-82 Exit the Config Settings screen
Chapter 3. Implementing the IBM Managed Hub and Unmanaged Hub
247
This will bring us back to the Fabric View screen, which displays the status and
elements of the SAN fabric, as shown in Figure 3-83.
Figure 3-83 Back to Fabric View
3.6.5 Shortcuts
A quicker method of accessing the individual switch (or managed hub) Events
Log is shown in Figure 3-84.
Figure 3-84 Go to Events Log for the Managed Hub
This is functionally the equivalent of going into the Switch View and then
selecting the command from within this window.
248
IBM SAN Implementation
Similarly, we can launch the Admin View directly from the Fabric View screen as
shown in Figure 3-85, rather than having to go into the Switch View.
Figure 3-85 Go to Admin View for the Managed Hub
The same applies for launching the Telnet interface, as shown in Figure 3-86.
s
Figure 3-86 Go to Telnet for the Managed Hub
We will cover more of the functions that are available on both the managed hub
and the switch in Chapter 4, “Implementing an IBM TotalStorage SAN Switch” on
page 251.
Chapter 3. Implementing the IBM Managed Hub and Unmanaged Hub
249
250
IBM SAN Implementation
4
Chapter 4.
Implementing an IBM
TotalStorage SAN Switch
The IBM TotalStorage SAN Switch interconnects multiple host servers with
storage servers and devices, creating a Storage Area Network or SAN. An IBM
TotalStorage SAN Switch can be used either as a standalone device to build a
simple SAN Fabric, or interconnected with other switches to build a larger SAN
Fabric.
The interconnection of IBM and IBM-compatible switches and hubs creates a
switched fabric containing hundreds of Fibre Channel ports. The SAN Fabric
provides the high performance, scalability, and fault tolerance required by the
most demanding e-business applications and enterprise storage management
applications, such as LAN-free backup, server-less backup, disk and tape
pooling, and data sharing.
© Copyright IBM Corp. 2001
251
4.1 Product overview
The IBM TotalStorage SAN Switch operates at up to 100 MB/s per port with
full-duplex data transfer with the 2109-S08 and 2109-S16 models, and up to 200
MB/s with the 2109-F16 model. Unlike hub-based Fibre Channel Arbitrated Loop
(FC-AL) solutions which reduce performance as devices are added, the SAN
Fabric performance increases as additional switches are interconnected.
IBM offers three different types of IBM TotalStorage SAN Switches which are
OEM products from the Brocade SilkWorm family:
 IBM TotalStorage SAN Switch Model 2109-S08 is an 8-port model:
– Equivalent to a SilkWorm 2400
 IBM TotalStorage SAN Switch Model 2109-S16 is a 16-port model:
– Equivalent to a SilkWorm 2800
 IBM TotalStorage SAN Switch Model 2109-F16 is a 16 port model:
– Equivalent to a SilkWorm 3800
Note: As there are significant differences between the 2109-S models and the
2109-F16, we describe the functions and features of the 2109-F16 in section
4.10, “TotalStorage Fibre Channel Switch 2109-F16” on page 443.
Figure 4-1 shows the 8-port model and Figure 4-2 shows the 16-port model.
Figure 4-1 The IBM TotalStorage SAN Switch (2108-S08)
Figure 4-2 IBM TotalStorage SAN Switch (2109-S16)
252
IBM SAN Implementation
4.1.1 IBM TotalStorage SAN Switch hardware components
The IBM TotalStorage SAN Switch is available as two models:
 2109-S08
This is an 8-port Fibre Channel gigabit switch that consists of a motherboard
with connectors for supporting up to 8 ports.
 2109-S16
This is a 16-port Fibre Channel gigabit switch that consists of a motherboard
with connectors for supporting up to 16 ports.
The motherboard is enclosed in an air-cooled chassis which may be a standard
rack or used as a standalone unit. The chassis includes one or two power
supplies, a fan tray, and an RJ-45 Ethernet connection for switch set up and
management. The S08 also has a serial port.
Serial port connection
The serial port is used for recovering factory settings only and for the initial
configuration of the IP address for the switch, if the default address is not known.
It is not used during normal operation.
The IBM SAN Fibre Channel Switch, 2109-S16, does not have a serial port, but
rather uses the LCD display.
Ethernet connection
It is possible to connect an existing Ethernet 10/100BaseT LAN to the switch
using the front panel RJ-45 Ethernet connector. This allows access to the
switch’s internal SNMP agent, and also allows remote Telnet and Web access for
remote monitoring and testing. The IP address may be changed using the
Ethernet Port, which is shown in Figure 4-3.
Figure 4-3 SAN Fibre Channel Switch, 2109-S08 Ethernet and serial connectors
In Figure 4-4, we show how the ports are numbered sequentially, starting with
zero for the left-most port. The two optional power supplies are shown to the left
and right of the switch ports.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
253
Figure 4-4 2109-S08 front panel
Similarly for the 2109-S16, Figure 4-5 shows the ports are labelled, starting with
zero for the left-most port. The two optional power supplies are shown to the left
and right of the switch ports. The 2109-s16 also has an Ethernet port that is used
to connect to the LAN so the switch can be managed remotely.
Figure 4-5 IBM TotalStorage SAN
The front panel of the 2109-S16, as shown in Figure 4-6, has a display panel that
is used to configure the switch. Generally, this mainly used as part of the initial
configuration when setting up the IP address or changing factory settings.
Figure 4-6 2109-S16 display panel and controls
254
IBM SAN Implementation
GBICs
The IBM TotalStorage SAN Switch uses Gigabit Interface Convertors which are
laser-based, hot-pluggable transceivers that use high data rates (typically 1063
or 1250 Mb/s). The GBICs for the IBM TotalStorage SAN Switch are available in
both short wave (SWL) and long wave (LWL) options and provide flexibility for
configuring a Storage Area Network. The short wave GBIC supports a distance
of up to 550 metres, whereas the long wave GBIC can support up to 10 km.
The IBM TotalStorage SAN Switch comes standard with 4 short wave GBICs and
supports a mix of additional long or short wave GBICs. The GBIC supports fiber
optic cables of 9 microns for long wave ports and 50 or 62.5 microns for the short
wave ports.
The GBICs are hot pluggable and are easy to configure and replace. The unused
port positions are protected by a metal, spring-loaded door which protects the
switch
The GBICs have status lights which are visible on the front panel, giving a quick,
visual check of the GBICs status and activity.
The status lights will indicate as follows:
 No light
No device is attached to the GBIC.
 Steady yellow
GBIC is receiving light but the attached device is not online.
 Rapidly flashing yellow
There is an error or fault with the GBIC
 Steady green
GBIC is online and connected by a Fibre Channel cable to a device.
 Slowly flashing green
The GBIC is online but is segmented.
 Rapidly flashing green
This occurs when the GBIC is in Internal Loopback mode (diagnostic).
 Flickering green
Represent the GBIC is online and is transmitting and receiving frames.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
255
Fibre Channel connections
The IBM TotalStorage SAN Switch supports the following types of Fibre Channel
connections:
 Fabric (F_Port)
 Arbitrated loop — public and private (FL_Port)
 Interswitch connection (E_Port)
Supported port types
The IBM 2109-S08 and 2109-S16 support the following port types:
 E_Port — is an expansion port.
 A port is designated an E_Port when it is used as an interswitch expansion
port to connect to the E_Port of another switch, to build a larger switch fabric.
 F_Port — is a fabric port that is not loop capable.
 Used to connect an N_Port to a switch.
 FL_Port — is a fabric port that is loop capable.
 Used to connect NL_Ports to the switch in a loop configuration.
 G_Port — is a generic port
 It can operate as either an E_Port or an F_Port. A port is defined as a G_Port
when it is not yet connected or has not yet assumed a specific function in the
fabric.
 Isolated E_Port
 This is a port that is online but not operational between switches due to
overlapping domain ID or nonidentical parameters such as E_D_TOVs.
 L_Port — is a loop capable fabric port or node.
 N_Port — is a node port that is not loop capable.
 Used to connect an equipment port to the fabric.
 NL_Port — is a node port that is loop capable.
 Used to connect an equipment port to the fabric in a loop configuration
through an FL_Port.
 U_Port — is a universal port.
 A port is defined as a U_Port when it is not connected or has not yet assumed
a specific function in the fabric.
Currently, the IBM TotalStorage SAN Switch only supports the same vendor
switch interconnection through the use of an E_Port. For example, the 2109-S08
can be connected to other 2109-S08, or 2109-S16 or even Brocade Silkworm
switches.
256
IBM SAN Implementation
Switch electronics
The system board incorporates the Fibre Channel port interfaces, two ASICs in
the IBM TotalStorage SAN Switch Model 2109-S08 and four in the Model
2109-S16, switching mechanism, the embedded switch control processor
(i960RP), and support logic for the embedded processor logic.
ASIC
The ASIC provides four Fibre Channel ports that may be used to connect to
external N_ports (as an F_port), external loop devices (as an FL_port), or to
other IBM TotalStorage SAN Switch (as an E_port). Each port operates at 1.0625
Gb/s. The ASIC contains the Fibre Channel interface logic, message/buffer
queuing logic, receive buffer memory for the four on-chip ports, and other
support logic.
Central Memory Module
The IBM TotalStorage SAN Switch is based on a central memory architecture
and has a central memory module (CMM). In this scheme, a set of buffers in the
central memory is assigned to each port, to be used for receipt of frames. As an
ASIC port receives and validates a frame, it stores the frame in one of its receive
buffers in the central memory and forwards a routing request (“Put” message) to
the appropriate destination ports.
When a destination port is capable of transmitting the frame, it reads the frame
contents from central memory and forwards the frame to its transmit interface. It
does not wait for the frame to be written in memory, unless the port is busy. Once
it has removed an entry for a frame from its internal transmit queue in preparation
for frame transmission, the destination port sends a “Finish” message to indicate
“transmission complete” to the port that received the frame, allowing the
receiving port to reuse the buffer for subsequent frames received.
The IBM TotalStorage SAN Switch central memory is incorporated into the
ASICs. Frames received on the four ports in an ASIC are written into the portion
of central memory in the receiving chip; received frames may not be written into
the sections of central memory located in other ASICs. All transmitters in a
switch may read from the memories in any of the ASICs, through inter-chip
connections clocked at 106.25 MHz.
Inside each ASIC, there are a total of 6272-by-34-bit static RAM devices plus
data path crossbar logic used to implement the central memory. This provides
112 receive buffers that accommodate full 2112-byte payload frames for 4 ports
(or 128 2048-byte typical frames). Each memory block is accessed in a
time-sliced fashion. The buffer design is efficient in that if frames are smaller than
2112 bytes, the buffer pool will expand proportionately, effectively providing
greater than 128 receive buffers. A single 4-port ASIC can buffer a total of 448
“small” frames (36-576 bytes), enabled using mini-buffers of 308 bytes in size.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
257
Control Message Interface
The IBM TotalStorage SAN Switch control message interface (CMI) consists of a
set of control signals used to pass hardware-level messages between ports.
These control signals are used by recipient ports to inform transmitting ports
when a new frame is to be added to the transmitter’s output queue. Transmitting
ports also use the CMI to inform recipient ports that a frame transmission has
been completed. A recipient port is free to reuse a receive buffer when it receives
notification that the frame has been transmitted. Multiple notifications are
required, in the case of multicast, to determine when a receive buffer is freed.
The CMI interfaces for the ASICs are connected inside each ASIC through a
message crossbar, implementing a “barrel shift” message scheme. Each chip
timeslices its output port to each possible destination chip in the switch. If it has a
message to send to a particular destination during the corresponding timeslot,
the chip will use the timeslot to send the message; otherwise, the output port
lines will be driven to indicate no message is present.
The timeslicing of the output CMI control signals of the ASICs are arranged out of
phase from each other, such that, in any given clock cycle, each chip’s output
port is timesliced to a different destination chip. Thus, messages appearing at the
input control signal interface of a given ASIC are also timesliced through each
possible source chip in the switch.
PCI bus operation
In the IBM TotalStorage SAN Switch, the interface between the embedded
i960RP processor and the ASICs is implemented using a 33 MHz PCI bus.
ASICs are connected directly to one of the PCI bus interfaces (Primary PCI@3.3
V) of the processor. A slave-only PCI interface is provided by each ASIC, to allow
the processor to program various registers, routing tables, and so on, within the
chip.
The PCI bus interface to the ASICs operates in 32-bit mode, and has a
word-wide even parity bit. The second PCI bus (Secondary, PCI@5V) connects
to an Ethernet MAC (media access controller) IC. This provides 10/100 BaseT
Ethernet connectivity. Either the i960RP or MAC may become bus master.
Embedded processor
The embedded processor is an Intel i960RP processor, with a clock speed of 33
MHz. It contains an integrated memory controller, a bridged dual PCI bus, and an
I2 C controller. The I2 C bus provides peripheral I/O control for the LCD module,
thermometers, general I/O functions, and others. In addition, the design includes
an RS232 serial port, 10/100 BaseT Ethernet port, SDRAM, and FLASH
258
IBM SAN Implementation
EEPROM for firmware text, initialized data, and switch configuration information.
Logic is also provided for the 16-port switch to allow the processor to display
characters on the Model 2109-S16 switch’s front panel and to read the state of
the front panel buttons.
Host attachment
The IBM TotalStorage SAN Switch supports attachments to multiple host
systems, including these:
 IBM Netfinity and Intel-based servers running Microsoft’s Windows NT,
Windows 2000, or Novell Netware
 IBM RS/6000 servers running AIX
 IBM NUMA-Q servers
 SUN servers running Solaris
 Hewlett Packard servers running HP-U
For a complete list of the supported platforms please check the IBM TotalStorage
SAN Switch Supported Servers site:
http://www.storage.ibm.com/hardsoft/products/fcswitch/supserver.htm
Device attachment
The SAN connectivity products and storage systems that can be attached to the
IBM TotalStorage SAN Switch include:
 IBM Enterprise Storage Sever
 IBM Modular Storage Server
 IBM FAStT 200 RAID / Storage unit
 IBM FAStT500 RAID controller
 IBM Fibre Channel RAID Storage Server; and the Netfinity Fibre Channel
RAID Controller Unit
 IBM 3494 Automated Tape Library and IBM Magstar 3590 Tape Drives with
Native Fibre Channel attachment feature
 IBM Fibre Channel Managed Hub, IBM Fibre Channel Hub (including the
Netfinity Fibre Channel Hub)
 IBM SAN Data Gateway with
–
–
–
–
IBM Magstar and Magstar MP libraries;
IBM 3502 DLT Tape Library
IBM Enterprise Storage Servers (SCSI attachment)
IBM LTO 3584 Tape Library
Chapter 4. Implementing an IBM TotalStorage SAN Switch
259
4.1.2 IBM TotalStorage SAN Switch software features
The IBM TotalStorage SAN Switch can be managed using three different
methods:
 By using the IBM TotalStorage Specialist, which provides a user-friendly,
Web browser interface
 By using Telnet commands
 With SNMP
For our purposes we mainly used the Fibre Channel Switch Specialist, which
provides advanced management capabilities for the following:
 Automatic discovery and registration of host and storage devices
 Intelligent rerouting of connection paths, should a port problem occur
 Cascading of switches, for scaling to larger configurations and to provide
resiliency for high data availability
 Switch zoning for fabric segmentation
 Configuration with hot pluggable port GBICs for shortwave or longwave
optical connections of up to 10 kilometers
 Fabric Watch, which provides monitoring and alert management for the switch
components.
Zoning is detailed in Section 4.4, “Zoning” on page 334, and cascading switches
is detailed in 4.6, “Cascading” on page 348.
4.2 Installing the IBM TotalStorage SAN Switch
We will be installing the switches into an environment that consists of:
 3 x IBM Netfinity 5500s running Windows NT 4.0 Service pack 6a and
Windows 2000 Advanced Server
 1 x Sun E250 server running Solaris V7
 3 x RS/6000 J50
 1 x RS/6000 F50
 1 x IBM Modular Storage Server
 1 x 2105-F20 IBM TotalStorage ESS with native FC adapters
 2 x 2109 S08 IBM TotalStorage SAN Switch
 1 x 2109-S16 IBM TotalStorage SAN Switch
 1 x 3534-1RU IBM TotalStorage SAN Managed Hub
 1 x 2108-G07 IBM SAN Data Gateway
 1 x 2108-R03 IBM SAN Data Gateway Router
 1 x Vicom SLIC Router
 Qlogic 2100F Host Bus Adapters
260
IBM SAN Implementation




Qlogic 2200F Host Bus Adapters
Emulex LP7000 Host Bus Adapters
Emulex LP8000 Host Bus Adapters
JNI Host Bus Adapters
4.2.1 Security relating to switch installation
It is important to consider the security of the switch, both from a physical
viewpoint and a logical one.
Physical security
Before thinking about installing a switch, we recommend that you review where
the switch will be located and what physical security is required. The switches
can be installed almost anywhere from an office environment through to a
specialized computer room. Much as we plan for planned/unplanned outages, it
is worth considering the possibility of accidental/deliberate damage to the switch.
The switch is the heart of the SAN and as a switch can have many different
devices connected to it the impact of a failure will affect many users. Due to
these considerations, we recommend that it is installed in a secure environment.
This could be inside a lockable 19-inch rack or in a computer room where access
cards are required. This will reduce the possibility of someone accidently tripping
on cables, for example, and will reduce the likely hood of deliberate damage.
Another point to consider is that the 2109-S16 has an LED control panel that
could be used by someone with unpleasant intentions.
You also need to plan for expansion as a SAN environment is often a rapidly
growing and changing entity.
Network security
Consideration needs to be given to the switches network setup and how this
needs should be secured for any given setup.
User security
The StorWatch Switch Specialist offers two levels of access to the switch:
User
Provides access to any function that does not change the state
of the switch (or switches). This level is recommended for
monitoring the switch activity.
Admin
Provides access to all commands and functions that have a valid
license. Most switch setup and configuration task require this
access.
We describe how to set up the User Security in “User Admin” on page 284.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
261
4.2.2 Installing the 2109-S08 switch
We recommend that a pre-installation checklist be used for setting up the switch.
An example of a pre-installation checklist and a description of the GBICs (and
how to insert them into the switch) is detailed in the IBM 2109 Model S08 User’s
Guide, SC26-7349, as well as the IBM 2109 Model S08 Installation and
Service Guide, SC26-7350.
To install the SAN Fibre Channel Switch, 2109-S08, we followed these steps:
1. Power-On Self Test
The switch is designed for maintenance free operation and supports
Power-On Self-Test (POST) and diagnostic tests. The diagnostic tests
determine the switch’s status, isolate problems, and will take approximately
two minutes.
As one of our first steps, we powered on the switch and ensured that the
POST completed successfully.
After the switch has completed the POST, the GBIC modules return to a
steady state from the flashing state that is shown during the test.
2. Setting the IP address
The switch is shipped from the factory with a default IP address on the switch
of 10.77.77.77. This IP address is noted on a label on the top front edge of the
switch. This address is for the external Ethernet connection.
In your environment, you will want to utilize your own range of IP addresses
and you will have to change the default address to establish a network
connection to the switch.
Your LAN administrator should be able to provide a valid, free IP address or a
range of addresses.
We changed the default IP address to reflect the ITSO environment.
To change an existing IP address, you can either use the Ethernet port and
Telnet commands entered from a server which has access to the same LAN,
or you can use the switch serial port using a serial terminal emulator. The IBM
SAN Fibre Channel Switch, 2109-S16, allows you to change the IP address
using the control panel on the front of the switch. We document this in 4.2.4,
“Setting the IP address on an IBM 2109-S16” on page 264.
In our installation, we explain how to use the serial port connector, shown in
Figure 4-7, to set the IP address.
262
IBM SAN Implementation
Figure 4-7 RJ-45 Ethernet Connector and Serial Port Connector
4.2.3 Setting the IP address using the serial port (2109-S08 only)
Here are the steps to set the IP address using the serial port:
1. Connect a system with a serial terminal emulator to the serial port (prior to
powering up the switch).
2. Start up a terminal emulation session (hyperterm).
3. Power up the switch. If two supplies are present, power up both. As the switch
goes through its diagnostics, it will post messages to your service terminal.
When the switch is fully powered on, the switch will respond: Admin>.
4. Admin> ipAddrSet (this is the command to set the IP address); press Enter.
5. Ethernet IP address [Current ipaddress or None]: new IP addr; press Enter.
This would be a new address provided by the Network Administrator and in
our example we used 193.1.1.14.
6. Ethernet Subnetmask [Current subnet mask or None]: new Subnetmask or
press Enter.
This would be a new Subnetmask provided by the network administrator and
we set ours to 255.255.255.0.
7. Fibre Channel IP Address [None]: press Enter.
8. Fibre Channel Subnetmask [None]: press Enter.
9. Gateway Address [Current Gateway address or None]: new Gateway
address or press Enter.
This would be a new Gateway address provided by the network administrator,
we set ours to 255.255.255.0.
10.Admin> Logout; press Enter.
This will end the Telnet session. This completes setting the IP address.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
263
Serial port settings
In our test scenario we used an IBM laptop as a serial terminal emulator and
linked it to the switch using a standard serial cable with two female 9-pin
connectors.
The serial port settings are:






8-bit
No parity
One stop bit
9600 baud
Flow Control = None
Emulation = Auto Detect
It is important to change the Ethernet Subnetmask and the Gateway address.You
can see the entries on the front panel of the switch in Figure 4-8.
Figure 4-8 Setting Ethernet IP addresses for the 2109-S08
Now the switch should be linked to the network and you should be able to access
it from any server in the network.
4.2.4 Setting the IP address on an IBM 2109-S16
One of the differences between the S08 and the S16, apart from the increase in
port counts, is the control panel that has been introduced. There is no serial port
on the S16.
From the control panel it is possible to set the IP address. The front panel of the
IBM SAN Fibre Channel Switch, 2109-S16 is shown in Figure 4-9.
264
IBM SAN Implementation
Figure 4-9 Setting the Ethernet IP addresses for the 2109-S16
The triangular buttons to the right of the display screen, just above port 12,
represent the data entry buttons referred to in the following steps:
1. Power up the switch
Wait two minutes while the diagnostics complete. The display panel will go
blank after the diagnostics are complete.
2. Press the ^ button. The switch will respond: Configuration menu.
3. Press the > button. The switch will respond: Ethernet IP address.
4. Press the > button. The switch will respond by:
Displaying the current Ethernet IP address in the form: XXX XXX XXX XXX
5. To change the current address to the preferred address, do the following:
– Pressing the < button, will move the cursor (the entry point) from one field
to the next. If you go past a field, continuing to press the < button will
cause the cursor to wrap around and return to the desired spot.
– Pressing the ^ button or the v button will either increment or decrement
the current field. Holding the button down will make this happen rapidly.
The numbers in the field will wrap to 0 from 255 or from 255 to 0,
depending on whether you are incrementing or decrementing. This will
help you get to the desired value quickly.
When you have all fields set to the desired value, continue with step 6.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
265
6. Press the > button. The switch will respond: Accept? Y N.
Pressing the < button indicates Yes. Pressing the > button indicates No.
– If you respond no, the switch will again respond: Ethernet IP address.
You can now restart the process.
– If you respond yes, the switch will respond: Updating the Config.
This will cause the new address to be stored. After the switch has made the
change, it will again display: Ethernet address.
If no other address is to be changed (Gateway, Subnet, and so on), you may
simply stop here by pressing the < button. At this point, you are done setting
up the switch. If you need to set other switch addresses (Gateway,
Subnetmask), press the ^ button. The switch will respond: Ethernet
Subnetmask.
7. Press the > button, the switch will respond by displaying the current Ethernet
Subnetmask in the form: XXX XXX XXX XXX
8. To change the current Subnetmask to the preferred address, do the following:
Pressing the ^ button or the v button will either increment or decrement the
current field. Holding the button down will make this happen rapidly. The
numbers in the field will wrap to 0 from 255 or from 255 to 0 depending on if
you are incrementing or decrementing. This can help you get to the desired
value quickly. When you have all fields set to the desired value, continue with
step 9.
9. Press the > button. The switch will respond: Accept? Y N.
Pressing the < button will indicate Yes. Pressing the > button will indicate No.
– If you say No, the switch will again respond: Ethernet Subnetmask, and
you can restart the process.
– If you say yes, the switch will respond: Updating the Config.
This will cause the new address to be stored. After the switch has made the
change, it will again display: Ethernet Subnetmask.
– If no other address is to be changed (Gateway, Subnet, and so on), you
may simply stop here by pressing the < button. At this point, you are done
setting up the switch.
– If you need to set other switch addresses (Gateway, Domain), press the ^
button. The switch will respond: Fibre Channel IP address
(will not be required at this time).
10.Press the ^ button. The switch will respond: Fibre Channel Subnetmask (will
not be required at this time).
11.Press the ^ button. The switch will respond: Gateway Address.
266
IBM SAN Implementation
12.Press the > button. The switch will respond by displaying the current Gateway
address in the form: XXX XXX XXX XXX
13.To change the current Gateway address to the preferred address:
– Press the < button to move the cursor (the entry point) from one field to the
next.
If you go past a field, continue to press the < button to wrap the cursor around
and return to the desired spot.
– Pressing the ^ button or the v button, will either increment or decrement
the current field. Holding the button down will make this happen rapidly.
The numbers in the field will wrap to 0 from 255 or from 255 to 0
depending on if you are incrementing or decrementing. This can help you
get to the desired value quickly.
When you have all fields set to the desired value, continue with step 14.
14.Press the > button. The switch will respond: Accept? Y N.
Pressing the < button will indicate Yes. Pressing the > button will indicate No.
– If you say no, the switch will again respond: Gateway Address, and you
can restart the process.
– If you say yes, the switch will respond: Updating the Config.
This will cause the new address to be stored. After the switch has made the
change, it will again display: Gateway Address.
– If no other address is to be changed (Gateway, Subnet, and so on), you
may simply stop here by pressing the < button. At this point you are done
setting up the switch.
– If you need to set other switch addresses (Domain), press the ^ button.
The switch will respond: Domain.
15.Press the > button. The switch will respond by: Displaying the current Domain
in the form: XXX XXX XXX XXX
To change the current Domain to the preferred address:
– Press the ^ button or the v button to increment or decrement the current
field. Holding the button down will make this happen rapidly. The numbers
in the field will wrap to 0 from 255 or from 255 to 0 depending on whether
you are incrementing or decrementing. This can help you get to the
desired value quickly.
When you have all fields set to the desired value, continue with step 16.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
267
16.Press the > button. The switch will respond: Accept? Y N.
Pressing the < button will indicate Yes. Pressing the > button will indicate No.
– If you say no, the switch will again respond: Domain, and you can restart
the process.
– If you say yes, the switch will respond: Updating the Config.
This will cause the new address to be stored.After the switch has made the
change, it will again display: Domain.
17.Respond by pressing the < button.
You have completed installation of the 2109 S16 switch. To perform a quick
check of the switch’s Fibre Channel ports, follow the switch installation
verification process.
Switch installation verification
1. Power down the switch.
2. Power up the switch (if dual power, power up both supplies).
3. Verify that the associated power supply LEDs are on.
4. Wait two minutes while POST diagnostics run.
5. Verify that the switch ready LED is on.
6. Plug the appropriate wrap connector (black for shortwave and gray for
longwave) into each GBIC. Verify that each associated port LED shows a
slow green (every two seconds) flash.
If any of these checks have failed, see Problem Determination Start Map on
page. If none of the checks fail, the switch is ready for use.
4.2.5 Upgrading the switch firmware
From time to time new versions of firmware will be released, we have
documented the steps to upgrade a switch to the latest levels of code (this
applies equally to the S08 and S16 models). This can be performed using Telnet
or by using the IBM StorWatch Switch Specialist. We will show both methods.
The latest microcode levels can be downloaded from:
http://www.storage.ibm.com/hardsoft/products/fcswitch/form.htm
Complete the registration form and then click the Submit Information button.
A new page will be displayed with the IBM License Agreement; read this carefully
and then click the I agree button.
268
IBM SAN Implementation
Another page will be displayed with the title “Download Firmware for the SAN
Fibre Channel Switch”. We need to download the actual code (for example,
v2.2.1a.zip). We also need to download the SNMP MIBs file and the RSH utility.
Download these to a system that can access the switch across the network.
Make sure that the new firmware and the RSHD and CAT utilities are all in the
same directory.
Once the files have been downloaded, we need to start a DOS session to run the
RSH program. This validates the user and delivers the files to the switch where it
is stored in flash memory. We show this in Figure 4-10.
Figure 4-10 Running the Remote Shell Daemon (RSH)
In this example, the directory “c:\temp\2109code” is used to store the switch
firmware.
The symbol underneath the rshd heading will rotate to indicate that the process
is alive and well.
The command to upgrade the firmware in the switch requires the host IP address
and name of the system where we stored the firmware. If these are not known
already, open a DOS window and issue the commands as shown in Figure 4-11.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
269
Figure 4-11 Displaying Hostname and IP configuration details
In our case, on the Windows 2000 server, we used the Ethernet adapter to
connect to the switch. Make a note of these details as they will be required when
transmitting the firmware to the switch.
Upgrading the Firmware using Telnet
To download the firmware to the switch we need a Telnet session. Start a DOS
window and issue the Telnet command with the IP address of the switch as
shown in Figure 4-12.
Figure 4-12 Establish a Telnet session with the switch
Once the Telnet session has been established with the switch, it is now possible
to login into the Fabric OS. The default logon id is admin and the password is
password. We suggest changing these immediately, otherwise it is possible for
undesirable elements to access the switch.
270
IBM SAN Implementation
When you are logged in, a screen similar to the one shown in Figure 4-13 is
presented.
Figure 4-13 Fabric OS and Telnet login
In Figure 4-14 we issue the firmwareDownload command.
Figure 4-14 Upgrading the switch firmware
On completion of the firmware upgrade, we need to reboot the switch. This can
be done anytime, but firmware changes will only take effect after a reboot is
successfully completed.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
271
This can be performed simply by issuing the Reboot command as shown in
Figure 4-15.
Figure 4-15 Rebooting the switch from a Telnet session
It will take approximately 2 minutes for the switch to reboot, but this does depend
on a number of factors. Some of those factors are the amount of switches that
are in the fabric and the amount of zoning and name server information that has
to be propagated to each switch in the fabric.
It is also possible to reboot the switch from within the IBM StorWatch Switch
Specialist as described.
Upgrading the firmware using the Switch Specialist
As with upgrading the firmware using Telnet we need to make sure that the RSH
daemon is running and we also need to know the host IP address. Refer to
Section 4.2.5, “Upgrading the switch firmware” on page 268 for these details.
272
IBM SAN Implementation
To upgrade the firmware using the Switch Specialist, we launch the Admin View
for the switch to be upgraded, as shown in Figure 4-16.
Figure 4-16 Go to Switch Admin screen
Chapter 4. Implementing an IBM TotalStorage SAN Switch
273
This takes us to the Switch Admin screen, as shown in Figure 4-17. From here,
we select the Firmware Upgrade tab.
Figure 4-17 Switch Admin screen
Selecting the Firmware Upgrade tab will display the screen shown in
Figure 4-18. We specify the Host IP address and the directory and file name of
where the firmware resides. We were using a Windows NT server, so we
selected the RSH option.
274
IBM SAN Implementation
Note that you need to have started an RSH daemon before initiating the
download process. You can start the RSH daemon using the method shown in
4.2.5, “Upgrading the switch firmware” on page 268.
Figure 4-18 Firmware Upgrade screen
Once the download process is initiated the message shown in Figure 4-19 is
displayed. From this screen we can also proceed to reboot the switch.
Figure 4-19 Reboot Switch message
Chapter 4. Implementing an IBM TotalStorage SAN Switch
275
Selecting the Reboot option will take us to the Reboot Switch screen as shown
in Figure 4-20.
Figure 4-20 Reboot Switch using Fastboot option
As shown, we select the Fastboot option to reboot the switch. Fastboot does not
perform the Power On Self Test function, and as the name suggests, it is faster
than the normal reboot process.
Once the reboot process is started, the screen shown in Figure 4-21 is displayed.
Figure 4-21 Reboot in progress message
276
IBM SAN Implementation
Returning to the RSH daemon will display the screen shown in Figure 4-22.
Figure 4-22 RSH Daemon message
The daemon should display a message indicating that it is processing the
command to transfer the firmware to the switch. We can now close this process.
Returning to the Fabric View main screen, we can verify that the firmware level
has been upgraded by checking the switch details as shown in Figure 4-23.
Figure 4-23 Switch View showing new firmware level
If all is as we expect it, we have successfully implemented the changes to the
switch.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
277
4.2.6 Connecting to the switch
Once we have verified that the switch is working correctly, attach one of the
available ports, using a Fibre Channel cable, to a host server Fibre Channel
adapter; and another switch port, again using a Fibre Channel cable, to a storage
device.
Depending on the GBIC in the port, this can be either an SWL fiber-optic link or a
LWL fiber-optic link.
The SWL fiber-optic GBIC module, with SC connector color-coded black, is
based on shortwave length lasers supporting 1.0625 Gb/s link speeds. This
GBIC module supports 50-micron, multi-mode, fiber-optic cables, with cables up
to 500 meters in length.
The LWL fiber-optic GBIC module, with SC connector color-coded blue, is based
on longwave length 1300nm lasers supporting 1.0625 Gb/s link speeds. This
GBIC module supports 9-micron, single-mode fiber. Cables up to 10 kilometers
in length with a maximum of five splices can be used.
Attaching the server and the storage device
To establish a SAN with fabric point-to-point connection between server and
storage, the server needs a Fibre Channel host bus adapter (HBA) card that
supports fabric point-to-point.
Support matrix
A host and storage support matrix for the IBM 2109-S08/S16 switches with host
bus adapter information can be found on the Web at:
http://www.storage.ibm.com/hardsoft/products/fcswitch/supserver.htm
4.2.7 SAN installation verification
If everything has been configured correctly, and all the parameters are set
appropriately, this entry-level SAN installation should now run as a Fibre Channel
Point to Point, fabric solution.
We used the IBM TotalStorage Specialist to verify our SAN solution.
4.2.8 Launching the IBM TotalStorage Specialist
Access to the IBM StorWatch Specialist is provided through one of the following
Java-enabled Web browsers:
278
IBM SAN Implementation
 For Windows 95/98NT or Windows 2000:
– Internet Explorer 4.0 or above
– Netscape 4.51 or above
 For UNIX:
– Netscape 4.51 or above
In addition to the above, Java Plug-In 1.3.0 is recommended.
To Launch
1. Start the Web browser, if it is not already active.
2. Enter a switch name or IP address in the Location/Address field.
3. The Fabric View appears, displaying all compatible switches in the fabric.
Figure 4-24 shows the IBM StorWatch Switch Specialist - Fabric View screen for
the single switch.
Figure 4-24 IBM StorWatch Switch Specialist — Fabric View
In the following sections we describe the features of the IBM StorWatch Switch
Specialist in more detail.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
279
4.3 Management
The StorWatch Switch Specialist is a Web browser based tool that assists with
the installation, setup, and management of the IBM TotalStorage SAN Switch.
4.3.1 Fabric View
The Fabric View screen is the first screen the StorWatch Switch Specialist will
display when you point your preferred Web browser to the switch, as shown in
Figure 4-25.
Figure 4-25 Fabric View
This screen is the main menu for all the management tasks that are required to
set up, manage, and maintain the switch fabric environment.
There are two main components of the Fabric View screen. On the left-hand side
are some options, complete with a legend, and in the main part of the screen is
the SAN fabric.
280
IBM SAN Implementation
This shows all the switches that are connected to form the SAN. This display will
show all the switches that are managed by the IBM StorWatch Switch Specialist
and can include switches from back-level versions of code, managed hubs and
switches with or without licenses for Fabric Watch.
Shown in Figure 4-26 is a display of a single switch that is part of the SAN fabric.
Figure 4-26 Single Switch View
This view consists of a thumbnail of the switch itself, information on the switch
including switch name, Domain ID, IP addressing information, firmware levels
and the switches WWN. Also displayed are three command buttons. These
command buttons can be launched from this screen, or from within the detail
Switch View which we cover in the topics that follow.
The commands in this view only relate to the individual switch, rather than the
entire fabric.
Switch Events log
To go to the Switch Events log, click the button as shown in Figure 4-27.
Figure 4-27 Go to Switch Events
Chapter 4. Implementing an IBM TotalStorage SAN Switch
281
The StorWatch Switch Specialist will launch the Event Log for this specific switch
as shown in Figure 4-28.
Figure 4-28 Switch Event log
From this panel it is possible to sort on the various fields shown by clicking the
title of the column. It is also possible to re-arrange the order of the fields by
dragging and dropping the columns to a different position. To exit from the log,
just close the window. The layout of the Fabric Watch error messages is
discussed in more detail in 4.3.1, “Fabric View” on page 280.
Switch Admin
To go to the Switch Admin View, click the picture of the key as shown in
Figure 4-29.
282
IBM SAN Implementation
Figure 4-29 Go to Admin View
The Switch Admin View is displayed in Figure 4-30.
Figure 4-30 Admin View
Chapter 4. Implementing an IBM TotalStorage SAN Switch
283
The first screen displayed is the Switch Admin screen.
The main actions to perform from this screen are the enabling and disabling of
the ports.
User Admin
To go to the User Admin screen, click the User Admin tab as shown in
Figure 4-31.
Figure 4-31 User Admin
From this screen, we can change the user names and passwords that allow
access to the switches from the StorWatch Switch Specialist.
Admin access level
This access level allows access to all commands in the help menu. Typically,
most switch administration is performed at this level.
User access level
This access level provides access to any commands that do not change a switch
state. This level is recommended for monitoring switch activity.
284
IBM SAN Implementation
To change a User Name, overtype the entry in the User Field and specify the
password as shown in Figure 4-32.
Figure 4-32 Adding Users / Modify existing users
If the password is changed and the changes committed, the screen shown in
Figure 4-33 will be displayed.
Figure 4-33 SysAdmin Changes
Firmware Upgrade
Close the previous window then click the Firmware Upgrade tab and this will
display the screen in Figure 4-34. This screen can be used to download firmware
upgrades.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
285
Figure 4-34 Firmware Upgrade using the Switch Specialist
Reboot Switch
Clicking the Reboot Switch tab will display the screen shown in Figure 4-35.
This screen can be used to start a reboot of the switch or to do a fast start of the
switch (this disables the POST function and is the equivalent of a reboot with the
POST function disabled).
Figure 4-35 Reboot Switch
POST is the Power On Self Test and takes about two minutes to complete. A
series of commands can be executed to test the switch. The Fabric OS POST
includes the following tests:
286
IBM SAN Implementation






ramTest
portRegTest
centralMemoryTest
cmiTest
camTest
portLoopbackTest
For more information about these tests, refer to the Brocade Fabric OS Version
2.2, 53-0001560-02 reference manual.
SNMP Admin
Clicking the SNMP Admin tab will display the screen shown in Figure 4-36. This
screen can be used to set up the SNMP options.
Figure 4-36 SNMP Admin
We discuss SNMP in greater detail in the IBM SAN Survival Guide Featuring
the IBM 2109, SG24-6127.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
287
License Admin
Clicking the License Admin tab will display the screen as shown in Figure 4-37.
From this screen you can view a list of the installed licenses and can add or
remove licenses as required.
Figure 4-37 License Admin
288
IBM SAN Implementation
Config Admin
Clicking the Config Admin tab will display the screen shown in Figure 4-38. This
option is used to upload the switch configuration file for archiving or for editing for
future uploading to the switch. This option can also be used to download a new
configuration file from the host.
Figure 4-38 Config Admin
Chapter 4. Implementing an IBM TotalStorage SAN Switch
289
Switch Information Report
Clicking the Switch Information Report heading as illustrated in Figure 4-39 will
display a detailed report on the Switch configuration. This will list the types of
switches, the inter-switch links, list of ports, the Name Server information, details
on the configured zones and GBIC serial ID information.
Figure 4-39 Go to Switch Information Report
290
IBM SAN Implementation
Portions of the Switch Information Report are listed in Figure 4-40 to Figure 4-45.
Figure 4-40 Switch Information Report — Page 1
The first part of the Switch Information Report shows detailed information for all
the switches in the fabric, including IP address information, domain names, and
WWN names.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
291
In Figure 4-41 we show the ISLs and the list of ports. The report shows the
Inter-Switch Links and lists the port number and domain IDs for each link.
Following this is a list of all the ports showing the status of the port, port type, and
the WWN / WWPN and symbolic names.
Figure 4-41 Switch Information Report — Page 2
292
IBM SAN Implementation
In Figure 4-42 we show the Name Server information.
Figure 4-42 Switch Information Report — Page 3
Chapter 4. Implementing an IBM TotalStorage SAN Switch
293
In Figure 4-43 the Zoning Information is displayed along with the Alias
information.
Figure 4-43 Switch Information Report — Page 4
The Report also shows details on Zoning across the fabric and shows all the
members defined in each zone as well as the Alias definitions.
294
IBM SAN Implementation
Towards the end of the Switch Information Report is a list of the zones in the
Effective or Active Configuration. This also shows the list of members belonging
to each zone, as shown in Figure 4-44.
Figure 4-44 Switch Information Report — Page 5
The last page of the report contains information on the GBICs within the fabric.
This is provided for the smart GBICs only, as shown in Figure 4-45.
Figure 4-45 Switch Information Report — Page 6
To exit the Switch Information Report, just close the window.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
295
Extended Fabric
Click the Extended Fabric tab as shown in Figure 4-46. This is an optional
screen that will require a license to activate. This function allows you to configure
ports for a long distance link of up to 100 km.
Figure 4-46 Extended Fabric
The Telnet interface
The StorWatch Switch Specialist also has a Telnet interface which can be
accessed by clicking the picture of the monitor, as shown in Figure 4-47.
Figure 4-47 Go to Telnet session
296
IBM SAN Implementation
In Figure 4-48 we show the HyperTerminal screen that is presented. From this
screen, the login and password are required.
Figure 4-48 Telnet session
Only one Telnet session per switch can be active at a time. Here are some of the
more useful Telnet commands:
 nsShow — prints the local name server information
 nsAllShow — displays the 24 bit Fibre Channel port IDs of all devices in all
switches in the fabric
 switchShow — prints the switch and port status
 fabricShow — display a list of switches and a list of multicast alias groups in
the fabric
 supportShow — displays a plethora of valuable diagnostic information
Chapter 4. Implementing an IBM TotalStorage SAN Switch
297
4.3.2 Switch View
By clicking the picture of the switch as shown in Figure 4-49, the StorWatch
Switch Specialist will display additional options for managing the switch.
Figure 4-49 Go to Switch View
The Switch View presents a picture of the switch as shown in Figure 4-50.
Figure 4-50 Switch View
From the Switch View, we can find more detailed information about the switch
itself, including WWN, domain IDs, IP addressing, firmware levels, and the role of
the switch (principal or subordinate). There are buttons that allow us to drill down
further into the switch; these are covered in more detail in later topics.
Also from the Switch View, we can click any of the ports, and this will present us
with more detailed information on the individual ports.
298
IBM SAN Implementation
Port Information
To access the detailed port information, click the port as shown in Figure 4-51.
Figure 4-51 Go to Port Information
The port information will be displayed for the switch, as shown in Figure 4-52.
Figure 4-52 Port Information
Chapter 4. Implementing an IBM TotalStorage SAN Switch
299
From this screen, you can select any of the switch ports. If a serial GBIC is
installed, then additional information on the GBIC itself can be selected by
accessing the GBIC tab. The Loop tab contains information about the loop on a
port, including QuickLoop statistics if a QuickLoop license is available.
Performance reporting
To access the performance information by port number, click the Performance
button, as shown in Figure 4-53.
Figure 4-53 Go to Performance Reporting
300
IBM SAN Implementation
The performance view displays the throughput in MB/s for each port and for the
entire switch. This is shown in Figure 4-54.
Figure 4-54 Performance Reporting
Port throughput represents the number of bytes sent plus the number received.
The switch throughput is the sum of the port throughputs. The horizontal axis
represents elapsed time, and the vertical axis represents throughput. Each port
graph contains up to 60 seconds of performance data, and the switch graph can
contain up to 4 minutes of data.
Beaconing
The Beaconing function will locate a switch by sending a signal to the specified
switch, which causes an LED yellow light pattern to flash from side to side of the
switch. This makes the switch very easy to find.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
301
To activate Beaconing, click the Lighthouse icon on the Switch View as shown
in Figure 4-55.
Figure 4-55 Start Beaconing
This function can be toggled on and off once the switch is identified.
4.3.3 Fabric Watch
Fabric Watch monitors key fabric and switch elements, making it easy to quickly
identify and escalate potential problems. It monitors each element for
out-of-boundary values or counters and provides notification when any exceed
the defined boundaries. Fabric Watch can configure which elements, such as
error, status, and performance counters within a switch, are monitored. If an
element exceeds the specified threshold or trigger value, Fabric Watch will issue
an alert. This can be in the form of writing to the event log, locking of the port log
or by issuing an SNMP trap (or a combination of all of these).
Accessing Fabric Watch
Fabric Watch runs on an IBM TotalStorage SAN Switch with Fabric OS version
2.2 or later, and can be accessed through the IBM StorWatch Switch Specialist, a
Telnet interface, an SNMP-based enterprise manager, or by modifying and
uploading the Fabric Watch configuration file to the switch.
Fabric Watch monitors the following elements:




302
Fabric events (such as topology re-configurations, zone changes)
Switch environment (fans, power supplies, and temperature)
Ports (state changes, errors, and performance)
GBICs (for switches equipped with Finisar SMART GBICs FTR-8519-3).
IBM SAN Implementation
Range monitoring
With Fabric Watch, each switch continuously monitors error and performance
counters against a set of defined ranges. This and other information specific to
each monitored element is made available by Fabric Watch for viewing and, in
some cases, modification. This set of information about each element is called a
threshold, and the upper and lower limits of the defined ranges are called
boundaries.
If conditions break out of acceptable ranges, an event is considered to have
occurred, and one or more alarms (reporting mechanisms) are generated if
configured for the relevant threshold. There are three types of alarms:
 SNMP trap
 Entry in the switch event log
 Locking of the port log to preserve the relevant information
For more information, refer to the following Web site:
http://www.storage.ibm.com/ibmsan/index.htm
Classes and Areas
Fabric and switch elements are organized into Classes, which are groupings of
closely related elements. There are seven major Classes with each Class having
a number of subclasses called Areas. The Areas are the elements that Fabric
Watch can monitor. Listed below are the 7 main Classes:
Fabric
Monitors key fabric resources, such as fabric
re-configuration, zoning changes, and new fabric logins
Environmental
Monitors switch environment functions, such as
temperature, power supply, and fan status
Port
Monitors port error and performance counters
E_Port
Monitors E_port errors and performance counters
F/FL_port (Optical)
Monitors optical F/FL_port error and performance
counters
F/FL_port (Copper)
Monitors copper F/FL_port error and performance
counters
GBIC
Monitors operational values for smart GBICs
Chapter 4. Implementing an IBM TotalStorage SAN Switch
303
Table 4-1 describes the Areas that are available to be monitored within each
Class.
Table 4-1 Fabric Watch — Classes and Areas
Classes
Areas
IBM Default Value
Fabric
Loss of an E_port
Fabric Reconfiguration
Segmentation changes
Domain ID change
Zoning changes
Fabric to QuickLoop changes
Fabric logins
GBIC changes
ON
ON
ON
ON
ON
ON
ON
ON
Environmental
Temperature
Fan
Power Supply
0 to 75o C (buffer =10o C)
2500 - 3500 rpm
1=Okay / 0 = bad
Port
Link Failure count
Loss of synchronization count
Loss of Signal count
Primitive sequence protocol error
Invalid transmission word
Invalid CRC count
Receive performance
Transmit performance
State Changes
Low: 1/min - High: 60/min
Low: 1/min - High: 120/min
Low: 1/min - High: 120/min
Low: 1/min - High: 60/min
Low: 1/min - High: 60/min
Low: 1/min - High: 60/min
none
none
Low: 1/min - High: 120/min
E_port
Link Failure count
Loss of synchronization count
Loss of Signal count
Primitive sequence protocol error
Invalid transmission word
Invalid CRC count
Receive performance
Low: 1/min - High: 0/min
Low: 1/min - High: 2/min
Low: 1/min - High: 2/min
Low: 1/min - High: 0/min
Low: 1/min - High: 0/min
Low: 1/min - High: 0/min
Low: 60MB
High: 80MB/sec
Low: 60MB
High: 80MB/sec
Low: 1/min - High: 2/min
Transmit performance
State Changes
304
IBM SAN Implementation
Classes
Areas
IBM Default Value
F/FL_port
(optical)
Link Failure count
Loss of synchronization count
Loss of Signal count
Primitive sequence protocol error
Invalid transmission word
Invalid CRC count
Receive performance
Transmit performance
State Changes
Low: 1/min - High: 0/min
Low: 1/min - High: 2/min
Low: 1/min - High: 2/min
Low: 1/min - High: 0/min
Low: 1/min - High: 0/min
Low: 1/min - High: 0/min
none
none
Low: 1/min - High: 8/min
F/FL_ports
(copper)
Link Failure count
Loss of synchronization count
Loss of Signal count
Primitive sequence protocol error
Invalid transmission word
Invalid CRC count
Receive performance
Transmit performance
State Changes
Low: 1/min - High: 0/min
Low: 1/min - High: 8/min
Low: 1/min - High: 8/min
Low: 1/min - High: 0/min
Low: 1/min - High: 0/min
Low: 1/min - High: 0/min
none
none
Low: 1/min - High: 2/min
GBIC (smart)
Temperature
Receiver power
Transmitter power
Current
-10 to 85o C Buffer=1not set
not set
1=Okay / 0=Bad
To access the Fabric Watch function, click the “magnifying glass” button
(labeled Watch) from the Switch View, as shown in Figure 4-56.
Figure 4-56 Go to Fabric Watch
Chapter 4. Implementing an IBM TotalStorage SAN Switch
305
Thresholds
The first Fabric Watch screen is shown in Figure 4-57.
Figure 4-57 Fabric Watch — Environment Temperature details
The screen is divided into two parts. The left-hand side has a tree structure that
lists the Classes that can be monitored using Fabric Watch. If you expand the
Classes, all the Areas that are associated with a particular Class are displayed.
The main part of the screen on the right-hand side has a display with three tabs.
These tabs are used to configure and set the various thresholds and to manage
the alert process.
The Thresholds tab displays events that have occurred outside the defined
range for a particular Class and Area.
In Figure 4-57 the Area selected is Environment and the Class is Temp
(temperature). The entries in the main window occur when a trigger or threshold
value has exceeded the limit. This is like a mini-log of error conditions.
Threshold naming conventions
All threshold names consist of three components:
Class Name
306
IBM SAN Implementation
This is an abbreviation of the Class name; its values are:
fabric (Fabric Class)
env (Environment Class)
port (Port Class)
eport (E_Port)
fopport (F/FL_port Optical)
fcuport (F/FL_port Copper)
Area Name
Index Number
This is an abbreviation for the Area name, for example:
temp (Temperature)
state (State Changes)
This is the index number of the item within the series and
will consist of three number. For example, 000 for Port_0,
001 for Port_1 and so on. Index numbers for the fabric,
port, E_port, F/FL_port (optical), F/FL_port (copper) and
GBIC Classes all begin with 000. Index numbers for the
Environment Class begin with 001.
An example is a threshold name of envTemp000 as seen in Figure 4-57
previously. The Class Name is env, the Area Name is Temp and the Index is 000
(referring to the first thermometer within the switch).
Boundaries
Clicking the Boundaries Config tab will display the screen shown in Figure 4-58.
Figure 4-58 Fabric Watch — Environment Boundaries screen
From this screen, you can set the various threshold limits for the Class and
specific Area that you wish to monitor. The default values are shown and these
can be easily modified by specifying the required values in the Custom Area and
then applying the changes.
To demonstrate the Fabric Watch monitoring capabilities we have set the
temperature threshold, as shown in Figure 4-59, to a value that is lower than the
current operating temperature being recorded.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
307
Figure 4-59 Changing the Fabric Watch boundaries for Temperature
Once the new value has been applied to the fabric, the Switch View will
immediately highlight the “temperature alert” button (labeled Temp) in red,
as shown in Figure 4-60.
Figure 4-60 Switch View showing temperature status
308
IBM SAN Implementation
This will also cause the Fabric View screen to indicate that the switch is
operating outside the specified boundaries. This reflects a status of DOWN, so
the switch is colored red, as shown in Figure 4-61.
Figure 4-61 View of switch after exceeding the temperature threshold
Chapter 4. Implementing an IBM TotalStorage SAN Switch
309
Alarms
From the Alarms Config screen, shown in Figure 4-62, we can set the alarm
process.
Figure 4-62 Fabric Watch — Environment Alarms Config screen
Each event can generate one or more alarms, SNMP trap, Switch Event log
entry, and locking of the port.
The Threshold, Boundaries Config and Alarms Config screens are the same for
every Area that is to be monitored.
If you expand the Class = GBIC as shown in Figure 4-63, 4, Areas are displayed:




310
Temperature
RX Power
RT Power
Current
IBM SAN Implementation
Clicking the Temp Area as shown in Figure 4-63 will cause Fabric Watch to
display any events that occurred outside the threshold specifications.
Figure 4-63 Fabric Watch — GBIC details
In this case, there have been no such events.
Expanding the Class = Port will display the screen shown in Figure 4-64. Here
we see that the Port Class has the following Areas:








Link Loss
Synch Loss
Protocol Error
Invalid Words
Invalid CRCS
RX Performance
RT Performance
State Changes
Chapter 4. Implementing an IBM TotalStorage SAN Switch
311
Figure 4-64 Fabric Watch — Port details
In this case, we have selected the Area of Link Loss. Fabric Watch displays all
the events that have occurred outside of the specified range. If we were to click a
different Class, this would generate a different set of events in the main part of
the screen.
312
IBM SAN Implementation
Expanding the Class = Fabric as shown in Figure 4-65 displays the Areas that
are being monitored by Fabric Watch.
Figure 4-65 Fabric Watch — Fabric details
These Areas are:








E_Port downs
Fabric reconfiguration
Domain ID changes
Segmentation changes
Zone changes
Fabric <-> QuickLoop
Fabric logins
GBIC state changes
This screen also shows that a Fabric reconfiguration event has occurred where
the number of changes to the fabric exceeded the Trigger value.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
313
If we expand the Class = E_Port as shown in Figure 4-66, the Areas that are
monitored for the E_Ports are displayed.
Figure 4-66 Fabric Watch — E_port
The Classes that are available to be monitored are:








Link Loss
Synch Loss
Protocol Error
Invalid Words
Invalid CRCS
RX Performance
RT Performance
State Changes
The display shows that Ports 0 and 7 have generated an alert as they are below
the threshold value specified.
314
IBM SAN Implementation
Similarly, expanding the Class = F/FL (Optical) will display all the Areas that are
monitored by Fabric Watch for this Class as shown in Figure 4-67.
Figure 4-67 Fabric Watch — F/FL (Optical Port)
The monitored Areas include:








Link Loss
Synch Loss
Protocol Error
Invalid Words
Invalid CRCS
RX Performance
RT Performance
State Changes
This screen shows a single event has occurred where the F/FL Class had
exceeded the thresholds set.
Modifying settings for switches with one power supply
The IBM Fibre Channel Switches default settings for Fabric Watch will cause a
switch with a single power supply to appear yellow in the Fabric View screen,
indicating a MARGINAL status.
To change this to indicate a HEALTHY status start a Telnet session by clicking
the button as shown in Figure 4-68.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
315
Figure 4-68 Switches with a “marginal” status
Figure 4-69 shows the sequence of commands that we issued to change the
status of the switches to ensure that a switch with only one power supply is shown
with a HEALTHY status.
First issue the command: switchstatuspolicyshow
This command displays a list of the default settings and shows that a switch is
considered to be in a MARGINAL state if it has only one power supply. This
assumes that the switch has two power supplies and that one has failed.
Obviously, for a switch with a single power supply this is not valid.
To change the default settings, issue the command: switchstatuspolicyset
We are then prompted to enter the new values for each setting starting with the
DOWN value for the Faulty GBICs then the MARGINAL value for a Faulty GBIC.
We specify the value and press Enter and are then prompted for the next setting.
Eventually, we are prompted for the Power supply DOWN and MARGINAL
values. For this we are indicating that if two power supplies fail then the switch
will be shown as a red color.
316
IBM SAN Implementation
At the bottom of the Telnet display in Figure 4-69 is a message indicating that the
status of the switch has changed from MARGINAL to HEALTHY.
Figure 4-69 Changing the default setting
Chapter 4. Implementing an IBM TotalStorage SAN Switch
317
Figure 4-70 Three green switches
The status of the three switch fabrics above is now green.
318
IBM SAN Implementation
4.3.4 Fabric Wide Configuration
From the Fabric View screen, we can select actions as shown in Figure 4-71.
Figure 4-71 Fabric wide options
These options apply to the complete SAN fabric rather than the individual switch.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
319
Fabric Events
Fabric Events is a log of all the events that have occurred across the fabric. The
Fabric Watch conditions will be logged as well as other Fabric-wide events.
To select the Fabric Events option, click the button as shown in Figure 4-72.
Figure 4-72 Go to Fabric Events
This will display the Fabric Event log as shown in Figure 4-73.
320
IBM SAN Implementation
Figure 4-73 Event Log
You can sort the columns into ascending or descending order by clicking the
column headings. You can also re-arrange the columns to suit your requirements
by dragging and dropping them as required.
Looking at some of the entries, the first six events indicate that configuration
changes have been made to the fabric. One of the default Fabric Watch settings
is to post an alert when the number of fabric configuration changes exceeds a
certain value. This is a Trigger alert whereby Fabric Watch monitors for the
number of configuration changes and when this is exceeded it generates an
alert.
The next two events indicate a change in the switch status for ITSOSW3. This
was because the role of the switch changed from Principal to Subordinate as we
modified the fabric configuration.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
321
Fabric Topology
The Fabric Topology shows the physical configuration of the fabric, including
active domains and paths. The topology is shown as viewed from the host
domain (the host domain is the switch that was pointed to by the Web browser).
To move to the Fabric Topology report, click the button as shown in Figure 4-74.
Figure 4-74 Go to Fabric Topology
322
IBM SAN Implementation
This takes us to the Fabric Topology view, as shown in Figure 4-75.
Figure 4-75 Fabric Topology
Chapter 4. Implementing an IBM TotalStorage SAN Switch
323
This displays the physical configuration of the switched fabric, including active
domains and paths. The topology is shown as viewed from the host domain (the
host domain is the domain whose IP address was entered into the Web browser).
The Fabric Topology view shows the Domain ID’s and switch names for all the
active domains in the fabric. The Local domain is the host domain and the
remote domains are the Destination domains.
For each switch in the fabric the screen displays the active paths to other
switches within the fabric (these are the Inter-Switch Links (ISL’s). Also shown
are the output port numbers (ISL ports), input port numbers and the hop count.
Name Server
The Name Server table provides the name server entries listed in the simple
name server database. This includes all name server entries for the fabric, not
only those local to the host domain. Each row in the table represents a different
device.
324
IBM SAN Implementation
To go to the Name Server table, click the button as shown in Figure 4-76.
Figure 4-76 Go to Name Server table
The Name Server table, as shown in Figure 4-77, provides a list of all devices
that are attached to the SAN fabric, as well as a cross reference between
WWPN / WWN and the port position on the switch.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
325
Figure 4-77 Name Server table
The Name Server table contains the following parameters:
326
Domain #
Domain ID of the switch to which the device is connected
Port #
Port number of the switch to which the device is
connected
Port ID
Port ID of the device (basically a 24bit hexadecimal
number)
Port Type
Shows whether the port is an arbitrated loop port (NL) or
whether it is a normal switch fabric port.
Port WWN
World-wide name for the device port
Node WWN
World-wide name of the device node
Symbolic name
Name of the device assigned through the SCSI INQUIRY
command
IBM SAN Implementation
FC4 types
Fibre Channel FC4 layer types supported by the device,
such as FCP or IP.
COS
Class of Service that the device supports
Fabric Port Name
Shows the port in use by the device
Port IP address
IP address of the fabric port (may be zeros)
Hard Addres s
Hard address assigned to the fabric port
Member of zones
List of zones to which the port belongs
Zone Admin
The Zone Admin function is used to set up and maintain the zones across the
fabric. From here we can also define aliases for members in a zone and can
create the zones that will form the active configuration across the fabric.
A zoning license and administrative privileges are required to access this screen.
To display the Zone Admin screen, click the button as shown in Figure 4-78.
Figure 4-78 Go to Zone Administration
Chapter 4. Implementing an IBM TotalStorage SAN Switch
327
The Zone Admin screen as shown in Figure 4-79 is where we set up, implement,
and maintain the zone settings, aliases, and the switch configuration. This is
discussed in more detail in Section 4.4, “Zoning” on page 334.
Figure 4-79 Zone Administration
The Zone Admin view requires an optional license, and administrative privileges
are required to access this view.
328
IBM SAN Implementation
Summary View and Detail View
The Summary View option will toggle the display size of the switches within the
Fabric View screen. This is useful when trying to display a large fabric consisting
of many switches.
To access the Summary View, click the button as shown in Figure 4-80.
Figure 4-80 Go to Summary View
Chapter 4. Implementing an IBM TotalStorage SAN Switch
329
Figure 4-81 shows the effect of toggling to the Summary View for the switches.
Figure 4-81 Fabric View — Summary View
330
IBM SAN Implementation
Conversely, we can toggle back by clicking the Detail View button, as shown in
Figure 4-82.
Figure 4-82 Go back to Detail View
Chapter 4. Implementing an IBM TotalStorage SAN Switch
331
Figure 4-83 shows the effect of toggling back to the Detailed View of the
switches.
Figure 4-83 Fabric View — Detailed View
4.3.5 QuickLoop
QuickLoop runs on IBM TotalStorage SAN Switch, with Fabric OS version 2.2 or
later if Fabric Watch is to be used. It is a unique Fibre Channel topology that
combines arbitrated loop and fabric topologies, and complies with FC-AL
standards. Because this topology allows private loops to be attached to fabrics, it
can best be described as a Private Loop Fabric Attach (PLFA), as compared to a
Private Loop Direct Attach (PLDA).
Looplets
A QuickLoop consists of multiple private arbitrated looplets (a set of devices
connected to a single port) that are connected by a fabric. All devices in a
QuickLoop share a single AL_PA space and behave as if they are in one loop.
This allows private devices to communicate with other devices over the fabric,
provided they are in the same QuickLoop.
332
IBM SAN Implementation
QuickLoop topology has the following characteristics:
 A QuickLoop can include up to two switches and support up to 126 devices.
 Each individual switch can only be included in one QuickLoop.
 A QuickLoop can include either all or a subset of the ports on an individual
switch.
 Multiple QuickLoops can exist in a fabric of multiple switches.
 QuickLoop enabled switches can exist in the same fabric as non QuickLoop
enabled switches.
 A device attached to a QuickLoop can communicate with all other devices
attached to the same QuickLoop.
 A private device in a QuickLoop can communicate with devices in the same
QuickLoop only. Existing PLDA capable host drivers need no modification to
perform I/O operations with storage devices.
 Public devices that are arbitrated loop capable are treated as private devices
when connected to QuickLoop ports (their fabric login, or “FLOGI,” is
rejected).
 QuickLoop supports the use of legacy devices, allowing them to be attached
to a fabric and operate as if in a Private Loop Direct Attach (PLDA)
environment.
 QuickLoop functionality can be enabled or disabled for either the entire switch
or for individual ports. When QuickLoop is disabled on an individual port, that
port returns to fabric mode.
 Each looplet in a QuickLoop has its own unshared bandwidth and can support
transfer rates up to 100 MB/sec.
 Multiple devices can communicate simultaneously and at full bandwidth
within multiple looplets located in the same QuickLoop.
 If a looplet error is detected, QuickLoop automatically takes the looplet out of
service. If the error condition is cleared, the looplet is automatically reinstated.
Private loop migration
QuickLoop provides a potential migration path from deploying a single private
loop to deploying a fabric-based Storage Area Network (SAN). Initially,
QuickLoop-enabled switches can be used to replace hubs when the SAN is first
deployed and only has private devices attached. Then, as the SAN grows, fabric
switches can be added without any detrimental effect to the QuickLoop enabled
switches.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
333
Address translation
QuickLoop address translation is transparent and requires no actions on the part
of the user. It is achieved through hardware translative mode (also known as
phantom mode), in which a device not physically located in a looplet is made
addressable by a unique AL_PA in that looplet. There are two hardware
translative modes available to a QuickLoop enabled switch:
 Standard translative mode — This allows public hosts to communicate with
private target devices across the fabric.
 QuickLoop mode — allows private hosts to communicate with private target
devices across the fabric.
The switch automatically determines and sets the appropriate mode.
QuickLoop and zoning
QuickLoop can be used in conjunction with zoning. Using the products together
provides the following additional features:
 AL_PAs from multiple QuickLoops can be used to add members to a zone —
This is due to the Zoning ability to name QuickLoops and therefore identify
the QuickLoop to which the AL_PA belongs.
 Additional control over access to QuickLoop devices — Fabric devices in a
zoned fabric can only access the QuickLoop (and fabric) devices that are in
the same zone.
Zones can be created within QuickLoops — Zoning can be used to partition
QuickLoops. This creates “QuickLoop zones” (as opposed to fabric zones),
which support identification by either physical port number or AL_PA
4.4 Zoning
Zoning allows you to partition your Storage Area Network (SAN) into logical
groupings of devices that can access each other. Using IBM zoning, you can
arrange fabric-connected devices into logical groups, or zones, over the physical
configuration of the fabric.
Zones can be configured dynamically. They can vary in size depending on the
number of fabric connected devices, and devices can belong to more than one
zone. Because zone members can access only other members of the same
zone, a device not included in a zone is not available to members of that zone.
334
IBM SAN Implementation
Therefore, you can use zones to do the following:
 Administer security — You can use zones to provide controlled access to
fabric segments and to establish barriers between operating environments.
For example, isolate systems with different uses or protect systems in a
heterogeneous environment.
 Customize environments — You can use zones to create logical subsets of
the fabric to accommodate closed user groups or to create functional areas
within the fabric. For example, include selected devices within a zone for the
exclusive use of zone members, or create separate test or maintenance
areas within the fabric.
 Optimize IT resources — You can use zones to consolidate equipment,
logically, for IT efficiency, or to facilitate time-sensitive functions. For example,
create a temporary zone to back up non-member devices.
Figure 4-84 shows three zones with some overlaps. It also contains devices
that are not assigned to a zone, and are thus not active in the fabric if the IBM
TotalStorage SAN Switch zoning is enabled.
JBOD
Blue zone
Loop 2
Managed
Hub
Server
Server
Fibre Channel
Fabric
Managed
Hub
bridge
Tape Library
Disk subsystem
Loop 1
SSA disk
Server
JBOD
Red zone
Green zone
Figure 4-84 A fabric consisting of three zones
Chapter 4. Implementing an IBM TotalStorage SAN Switch
335
Implementing zoning simplifies the zoning process in several ways:
 Zoning can be administered from any switch in the fabric — Changes
configured to one switch automatically replicate to all switches in the fabric; if
a new switch is added to an existing fabric, all zone characteristics are
automatically applied to the new switch. Because each switch stores zoning
information, zoning ensures a high level of reliability and redundancy.
 Zones can be configured dynamically — Configuring new zones does not
interrupt traffic on unaffected ports or devices. And, they do not affect data
traffic across interswitch links (ISLs) in cascaded switch configurations.
 Zoning uses policy-based administration — Because zoning uses
policy-based administration, separating zone specification from zone
enforcement, you can manage multiple zone configurations and easily enable
a specific configuration when it is required. A fabric can store any number of
zone configurations; however, only one configuration is active at a time. But,
because the configurations are pre-determined and stored, a new
configuration can be easily enabled.
 Zoning can be configured and administered using Telnet commands or the
IBM StorWatch Specialist.
4.4.1 Increasing availability
The easiest way to increase system availability is to prevent failures from ever
occurring, typically by monitoring fabric activity and performing corrective actions
prior to an actual failure. By leveraging advanced SAN features such as zoning
and predictive management, companies can deploy a much more reliable and
resilient SAN environment. To help prevent localized failures from impacting the
entire fabric, specific parts of SANs can be isolated through the use of zoning, in
which defined zones limit access between devices within the SAN fabric.
Companies can specify different availability criteria at the connection, node, and
network level to address the potential impact of certain types of outages.
For instance, several minor outages in one environment might be much less
destructive than a single large outage in another environment — even if the total
amount of downtime is the same. The use of zoning helps limit the types of
interactions between devices that might cause failures, and thus prevents
outages. Especially as companies build larger SANs with heterogeneous
operating systems and storage systems, zoning is an effective way to prevent
failures.
336
IBM SAN Implementation
Zone terminology
A zone is a group of fabric-connected devices arranged into a specified grouping.
Any device connected to a fabric can be included in one or more zones. Devices
within a zone possess an awareness of other devices within the same zone; they
are not aware of devices outside of their zone. Therefore, if zoning is enabled,
any device not in a zone is not able to communicate with any other device.
Zone members
Zone members (ports, WWNs, or aliases) are grouped into a zone; in turn, zones
are grouped in a zone configuration (a collection of zones). Zones can overlap; a
device can belong to more than one zone and a fabric can consist of multiple
zones. A zone configuration can include both hard and soft zones. There can be
any number of zone configurations resident on a switch; however, only one
configuration can be active (enabled) at a time. Because the number of zones
allowable is limited only by memory usage, the maximum number is virtually
limitless.
Zoning types
Zones can be hard (hardware enforced), soft (advisory) or broadcast. In a hard
zone, sometimes referred to as a port zone, zone members are specified by
physical port number. In a soft zone, at least one zone member is specified
logically by world-wide name (WWN).
Hard zones
In a hard zone, all zone members are specified as switch ports; any number of
ports in the fabric can be configured to the zone. When a zone member is
specified by port number, only the individual device port specified is included in
the zone.
Hard zones are position-dependent, that is, a device is identified by the physical
port to which it is connected. Switch hardware ensures that there is no data
transfer between unauthorized zone members. However, devices can transfer
data between ports within the same zone. Consequently, hard zoning provides
the greatest security possible. Use it where security must be rigidly enforced.
Soft zones
In a soft zone, at least one zone member is specified by WWN. A device is
included in a zone if either the node WWN or port WWN specified matches an
entry in the name server table. When a device logs in, it queries the name server
for devices within the fabric. If zoning is in effect, only the devices in the same
zones are returned. Other devices are hidden from the name server query reply.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
337
When a WWN is specified, all ports on the specified device are included in
the zone. Soft zones are name server-dependent and therefore provide more
flexibility — new devices can be attached without regard to physical location.
However, the switch does not control data transfer so there is no guarantee
against data transfer from unauthorized zone members. Use soft zoning
where flexibility is important and security can be ensured by the co-operating
hosts.
Hardware zoning
By blocking the flow of unauthorized data and control information, hardware
zoning can restrict interaction between devices within the fabric. For example, a
server in a heterogeneous environment might attempt to log in to all devices
within the fabric, whether those devices represent other servers or storage. If the
server resides in a zone with all the other servers, it could cause unnecessary
and potentially erroneous data flow when attempting to communicate with them.
If login attempts occur repeatedly, they could disrupt operations or even cause a
failure in other server connections. As a result, zoning servers, especially
heterogeneous servers, provides an additional level of assurance against
potential failures.
No zoning implemented
Without zoning, failing devices that are no longer following the defined rules
might attempt to interact with other devices in the fabric. (This type of event
would be similar to an Ethernet device causing collisions on only a segment of a
network.) With zoning, these failing devices cannot affect devices outside of their
zone.
Zoning requirements
Other critical requirements for zoning are the ability to overlap hardware zones
and to implement fabric-wide hardware zoning. The ability to overlap hardware
zones is essential for secure storage resource sharing. The ability to share
storage resources through logical volume allocation requires that multiple
servers share a physical path into the storage. If hardware zones cannot overlap,
all devices that utilize this physical path must reside in the same zone — creating
potential interaction and disruption between devices.
The overlapping of hardware zones enables each server (or groups of servers)
to reside in a zone with the storage connection while another hardware zone can
also see the storage connection. The two distinct zones and all their devices
cannot communicate with each other, only with the shared storage system.
338
IBM SAN Implementation
Effective hardware zoning
To be truly effective, hardware zoning must be available across the enterprise
fabric. Hard zones should be able to transcend physical switch products and
allow devices to be securely zoned, regardless of their location in the fabric.
Fabric-wide zoning, which enables information to be distributed to all switches in
the fabric, can be accessed and managed from any switch in the fabric. In
addition, the flexibility to locate devices at the most appropriate place within the
fabric can help ensure reliability by enabling remote physical placement of
devices and connections.
Policy based administration
Designing and implementing a zoning configuration for a SAN can be an involved
process including a series of complex tasks. Zoning simplifies the process by
separating the action of Zone Specification — in which the user specifies the
members of a zone — from Zone Enforcement — where the switch enforces a
Zone Configuration.
Managing multiple zones
This is a policy-based administration, allows the user to manage multiple zone
specifications and rapidly enable a specific configuration when required. This
provides flexibility in rapidly making SAN configuration changes with minimal
impact and risk.
Multiple zone configurations
A fabric can store multiple zone configurations with any one configuration being
active, or in force, at a time. This capability can be used in many ways. For
example, a policy can be defined to provide access to the tape library to NT
hosts during the day for continuous backup, but migrate access to the UNIX
hosts at the end of the day.
Policy based management
As an example, imagine you have a storage subsystem that under normal
circumstances is shared among multiple hosts. Your disaster policy includes that
this storage subsystem be used exclusively by a single host to recover critical
data. Using policy-based zoning administration, both zoning configurations are
configured and stored in the Fabric. In the event of disaster, the administrator
would simply enable the pre-configured zoning configuration — a few mouse
clicks — and the Fabric would automatically enforce your predetermined policy.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
339
Zoning administration
Zoning administration can be managed either using Telnet commands to any
switch in the fabric, or using a graphical user interface (GUI) using the IBM
StorWatch Switch Specialist. Configuring zones consists of four steps:
 Create aliases — Aliases allow you to rapidly give familiar name or group
multiple devices into a name. For example, you can create an alias called
“NT_Hosts” to define all NT hosts in the Fabric.
 Define zones — Create a zone and add members to it. Members can consist
of Switch Port Names, WWNs, or aliases. Changes to the zone layout does
not take effect until a zone configuration has been defined and enabled.
 Define a zone configuration — Create a zone configuration and add zones to
it. This step identifies the zones that should be enabled whenever this
configuration is enabled. Changes to the zone configuration will not take
effect until that zone is enabled.
 Enable the zone configuration — Select the zone configuration to be
activated. For Hard Zones, this action downloads the zone configuration to
the switch ASICs and begins the enforcement. For either Hard or Soft Zones,
a State Change Notification (RSCN) is issued to signal Hosts to re-query the
Name Server for a list of available devices.
A switch can maintain virtually an unlimited number of zone configurations, but
remember, only one zoning configuration is active at a time.
Fabric-wide administration and distribution
Zoning is a fabric-wide resource administered from any switch in the fabric and
automatically distributes itself to every switch in the Fabric, and simplifies
administration. Zone definitions and zones configurations are persistent and
remain in effect across reboots and power cycles until deleted or changed.
A new switch added to the fabric automatically inherits the Zoning Configuration
information and immediately begins enforcement. The fabric provides maximum
redundancy and reliability since each switch stores the zoning information locally
and can distribute it to any switch added to the fabric.
340
IBM SAN Implementation
4.5 Implementing zoning
To set up zoning within the IBM TotalStorage SAN Switch, click the Zone Admin
button from the Fabric View screen. This will display the screen shown in
Figure 4-85.
Figure 4-85 Zone Admin — Zone Settings
This screen displays the Alias Settings information. However, we found it more
useful to go into the Zone Settings first, by selecting the tab as shown.
The first action we need to do is to create a zone. To do this, we select the
Create Zone button as shown in Figure 4-86.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
341
Figure 4-86 Zone Admin — create a zone
This causes the StorWatch Switch Specialist to prompt us for a name for the
zone that we wish to create. It is useful to decide upon a good naming
convention for your environment before creating a zone. As we had a number of
different platforms, we used the convention shown in Figure 4-87.
Figure 4-87 Creating a Zone Name — Solaris_sole_zone
342
IBM SAN Implementation
Our naming convention was to use the platform operating system and a short
description. In the example, the server was a Sun Solaris server with the name of
sole which we wanted to isolate from all other environments.
The word zone in the zone name is somewhat redundant, but it helps makes the
name recognizable as a zone when performing other switch administration tasks.
Once the Zone Name has been created, the Specialist displays the screen
shown in Figure 4-88.
Figure 4-88 Adding a member to a zone.
From this screen, we choose the various elements that we want to include in
Solaris_sole_zone. We have a number of options here, but for this particular
example, we will be using the Port Numbers — a concept which, in Brocade
terminology, is called Hard Zoning.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
343
To set up the zone, we highlight Port_6 (this is a port we plugged into the switch
earlier) and click the Add Member button. The Specialist displays the screen as
shown in Figure 4-89, with Port_6 being one of the members of the zone.
Figure 4-89 Zone Settings display after adding a member
344
IBM SAN Implementation
We repeat this process for Port_1 as shown in Figure 4-90 by highlighting the
port and clicking the Add Member button.
Figure 4-90 Adding another member to the Zone
Chapter 4. Implementing an IBM TotalStorage SAN Switch
345
As these were the only members we wanted for our Sun Solaris zone, we clicked
the Apply button to set up the zoning information within the fabric, as shown in
Figure 4-91.
Figure 4-91 Apply changes to Zone Setting
This process commits the zone information to the switch, and if it is a cascaded
environment, the zone information will be propagated to all other switches within
the fabric.
346
IBM SAN Implementation
At this stage, we click the Done button as shown in Figure 4-92, as we have
finished with the Zone Admin tasks. This returns us to the Fabric View screen,
as shown in Figure 4-92.
Figure 4-92 Exit Zone Admin panels
Chapter 4. Implementing an IBM TotalStorage SAN Switch
347
4.6 Cascading
As the SAN fabric grows additional switches will be needed to handle the
increasing number of hosts and devices. This is referred to as cascading.
Cascading is a reliable, scalable, and cost effective way to build fabrics with
hundreds or thousands of ports.
Cascading of switches provides many benefits to a SAN environment:
 The fabric can be seamlessly extended. Additional switches can be added to
the fabric, without powering down the existing fabric.
 You can easily increase the distance between various SAN participants.
 By adding more switches to the fabric, you increase connectivity by providing
more available ports.
 Cascading provides high resilience in the fabric.
 inter switch links (ISL) can increase the bandwidth of the fabric. The frames
between the switches are delivered over all available data paths. So, the more
ISLs created, the faster the frame delivery will be. Consideration must be
employed to ensure that a bottleneck is not introduced.
 When the fabric grows, the SNS is fully distributed across all the switches in
fabric.
 Cascading provides greater fault tolerance within the fabric
A multiswitch fabric offers more flexibility to build a fault tolerant system.
The sophisticated path selection protocol allows multiple links to operate at the
same time between any two switches in the fabric, so multiple redundant paths
can be created. The extra links do not have to be reserved and maintained idle —
all links carry traffic.
If a link goes down, the traffic that was carried over that link will be simply
transferred to the other link(s). This transfer takes places automatically, with no
human intervention, and in a very short time.
Even if a switch goes down, all other switches in the fabric and the end nodes
connected to them are not affected.
Of course, if a switch goes down, all nodes connected to it will not be able to talk
to each other, or to a node connected to another switch. However, a node
running a mission critical application can have multiple Fibre Channel interfaces,
each one connected to a different switch in the fabric, to overcome this problem.
This is not possible in a single switch fabric.
348
IBM SAN Implementation
In Figure 4-93, we show a six-switch implementation of a fault tolerant fabric.
SW1
SW2
SW3
SW4
SW6
SW5
Figure 4-93 A fault tolerant fabric with 6 switches
This is an example of a completely fault tolerant fabric. If any link goes down,
every switch is still able to communicate with all the other switches. If a switch
goes down, all the remaining switches are able to communicate with each other.
Another example of a fault tolerant fabric with shorter distances between the
switches is shown in Figure 4-94.
SW1
SW3
SW2
SW4
Figure 4-94 A fault tolerant fabric with four switches
Chapter 4. Implementing an IBM TotalStorage SAN Switch
349
Fabric fault tolerance, distance, or performance considerations determine the
design of a multiswitch fabric; the number of involved devices decide the number
of switches.
Cascading using IBM switches
All IBM 2109 type switches can be interconnected, and due to the switch
software and embedded protocols, this is a non-disruptive topology change.
The 2109 ports are Fibre Channel G_Ports or FL_Ports. G_Ports can connect to
either an external device (F_Port mode) or to another switch (E_Port mode).
FL_Ports allow a Fibre Channel Arbitrated Loop to be connected to a (possibly
cascaded) fabric, supporting communication between loop devices and fabric
attached devices.
The IBM switch software automatically selects the port's mode of operation, so
that no configuration is necessary.
This feature is extremely useful in a cascaded environment, because it allows a
user to allocate more bandwidth between switches, if necessary, without having
to plug in a new card, or even to change a configuration parameter. Even a port
previously connected to an external device, such as a workstation, can be
connected to another switch by simply unplugging the old cable and plugging in
the new one, connected to another switch.
The 2109 software will detect the state transition and automatically configure the
port to be an E_Port.
Theoretically, up to 239 switches are supported in an IBM SAN fabric. This allows
thousands of fabric and Fibre Channel Arbitrated Loop connections. Practical
implementations tend not to have taken advantage of this number as yet.
Considering the complexity and performance that cascading may introduce, the
recommendation is to limit the number of cascaded switches to seven.
It should be noted that in a fabric environment some of the ports are used for
inter switch links (ISL), that is E_Ports. This means that the maximum number of
fabric attached device connections is actually less than the total number of ports.
The number of ports used as ISLs depends on the fabric configuration. This is
dictated by the amount of bandwidth required between switches, and by the
number of desired redundant links, to maintain connectivity in the case of link or
switch failures.
350
IBM SAN Implementation
Implementing cascading
Now we will cascade our existing switch with another switch which we have
installed and set up in a similar manner as described earlier in Section 4.2,
“Installing the IBM TotalStorage SAN Switch” on page 260. This switch is called
ITSOSW2 and has the Domain ID of 2. At the moment we have nothing
connected to the switch, as shown in Figure 4-95. It is also worth noting that the
switch has a Role of Principal, as it is a single switch that is not part of the fabric
we have created using ITSOSW1.
Figure 4-95 Switch view of itsosw2
We will bring this new switch into our fabric that we setup earlier by connecting
Port_0 on ITSOSW2 to ITSOSW1 as shown in Figure 4-96.
Figure 4-96 Switch view after cascading
Note that once the switches are connected and the new switch is logged into the
fabric, the role of the switch changes to become Subordinate.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
351
Closing the Switch View will take us back to the Fabric View as shown in
Figure 4-97.
Figure 4-97 Cascaded switches
This now displays both switches as being part of the SAN fabric.
We now connect another device to Port_4 on the new switch (ITSOSW2). This
device is actually a second connection to an IBM Modular Storage Server that
we have installed. Upon cabling the MSS into the switch the Switch View now
shows two ports as being connected to ITSOSW2 as shown in Figure 4-98.
Figure 4-98 Second cable plugged into switch
352
IBM SAN Implementation
Returning to the Zone Admin display (by clicking the Zone Admin button, which
is on the left-hand side of the Fabric View screen), we see the screen as
displayed in Figure 4-99.
Figure 4-99 Zone Admin — displaying a cascaded switch
You can see that the Member Selection list now displays the ports from both
switches. This will enable us to implement zoning across our cascaded switches.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
353
To add the port that we have plugged into the second switch, click the Zone
Settings tab, as shown in Figure 4-100.
Figure 4-100 Zone Settings — modifying zones across a cascaded fabric
Note that there is only one zone defined at the moment. If there were additional
zones defined, we would need to select the zone we wanted to change by
clicking the drop-down box next to the Zone Name.
354
IBM SAN Implementation
To add Port_4 on the second switch (ITSOSW2) to the Solaris zone, select it as
shown in Figure 4-101 and click the Add Member button.
Figure 4-101 Zoning — across cascaded switches
Chapter 4. Implementing an IBM TotalStorage SAN Switch
355
Now that we have completed the additions to the Solaris zone, we click the
Apply button to commit the changes to the fabric as shown in Figure 4-102.
Figure 4-102 Apply changes — applying changes across a cascaded fabric
356
IBM SAN Implementation
Once the changes have been committed to the fabric, we close the window by
clicking the Done button, as shown in Figure 4-103.
Figure 4-103 Exiting Zone settings screen
Chapter 4. Implementing an IBM TotalStorage SAN Switch
357
Now that we have a fabric set up across multiple switches, we can see the
details of the switch connections by clicking the Fabric Topology button as
shown in Figure 4-104.
Figure 4-104 Accessing Fabric Topology
358
IBM SAN Implementation
The Zone Topology display provides information on the fabric as shown in
Figure 4-105.
Figure 4-105 Zone Topology — after cascading switches
This display provides the Domain names for the switches in the fabric as well as
the WWN for each switch. Other useful information includes the output port
number that is being used as an Interswitch Link (ISL) and the Hop Count.
This information can be very useful particularly when dealing with larger more
complex fabrics.
To return back to the Fabric View display, close the Zone Topology display.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
359
4.6.1 Using aliases
Using aliases provides a way of labelling a Port or a WWPN with a more
informative (or recognizable) name. This helps simplify the task of Zone
Administration, as it removes the requirement to distinguish between names like
10:00:00:60:69:00:00:8a and 21:00:00:e0:8b:02:a7:2d, for example.
To define and use aliases from the Fabric View screen, click the Zone Admin
button as shown in Figure 4-106.
Figure 4-106 Fabric View — navigating to Zone Admin
From the Zone Admin screen, we can start to define and set up any aliases that
we may require. To do this, click the Create Alias button as shown in
Figure 4-107.
360
IBM SAN Implementation
Figure 4-107 Creating aliases screen
As you can see by the member selection list, any tasks that we implement within
Zone Admin are implemented across the fabric.
For this example, we create an alias for our Modular Storage Server’s Fibre
Channel connections. As shown in Figure 4-108, we save the name as MSS1.
Figure 4-108 Create Alias — save name as MSS1
Chapter 4. Implementing an IBM TotalStorage SAN Switch
361
We need to add the members that we want to include in the alias. An alias can
have multiple members or can consist of just a single member. Our example has
two members, and we have decided to create a member using the physical port
number that the MSS is attached to.
We could just as easily have chosen to create the alias using the WWPN for the
MSS. Our reason for using Port numbers in this example was that we assumed
that the MSS would not likely be re-cabled at the switch and we also wanted to
minimize any impact of a failed Fibre Channel card within the MSS. If we had
chosen to define an alias using WWPN and for some reason this changed, then
all our zones using this alias would be invalid. Therefore we decided to minimize
our risk for a failing Fibre Channel adapter and use port based zoning.
We selected Port_1 and clicked the Add Member button to add it to our alias
definition as shown in Figure 4-109.
Figure 4-109 Creating an alias — based on port number
362
IBM SAN Implementation
Similarly, we selected the second adapter port of the MSS which was connected
to Port 4 on the second switch (ITSOSW2), as shown in Figure 4-110.
Figure 4-110 Adding a second port number to an alias
This also adds redundancy across Fibre Channel switches in the unlikely event
that one fails.
Once we completed the alias definition, we apply these changes to the fabric by
clicking the Apply button as shown in Figure 4-111.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
363
Figure 4-111 Applying changes to the alias settings
It is worth noting that the screen also shows the members of the alias MSS1 in
the box on the right-hand side of Figure 4-111. This definition takes the form of
Switch ID and Port Number.
364
IBM SAN Implementation
4.6.2 More complex zoning
We have been through the steps required to set up a relatively simple zone using
hardware based zoning across a cascaded switch. We now look at setting up a
more complex zoning environment with multiple zones and multiple servers, as
well as using a mixture of software and hardware base zoning techniques.
Our first step is to cable more devices into the switches. We have added
additional devices into both switches, as the Switch View shows more active
ports. These are illustrated in Figure 4-112 for ITSOSW1.
Figure 4-112 Switch view for ITSOSW1 after adding additional a cables
In Figure 4-113 we show the active ports for ITSOSW2.
Figure 4-113 Switch View of ITSOSW2 after adding additional cables
Chapter 4. Implementing an IBM TotalStorage SAN Switch
365
From the Fabric View screen, we click the Zone Admin button, which will display
the screen shown in Figure 4-114.
Figure 4-114 Creating another new zone
This time, we create a new zone for a number of general purpose NT file and
print servers. We save the zone name as shown in Figure 4-115.
Figure 4-115 Creating a Zone — for NT general purpose servers
366
IBM SAN Implementation
We want to add Port_4 to the NT zone so as before we select the port and click
the Add Member button as shown in Figure 4-116.
Figure 4-116 Adding Port 4 to the NT zone
Chapter 4. Implementing an IBM TotalStorage SAN Switch
367
We continue adding the NT servers by selecting the ports they are connected to,
as shown in Figure 4-117, where Port_3 is also added to the zone.
Figure 4-117 Adding Port 3 to NT zone
368
IBM SAN Implementation
We also add Port 4 on the second switch in a similar manner as shown in
Figure 4-118.
Figure 4-118 Adding Port 4 from the second switch to the NT zone
Chapter 4. Implementing an IBM TotalStorage SAN Switch
369
Finally, we want to include the MSS as part of this zone, so we use the alias,
MSS1, that we created earlier. To do this, we select the MSS1 alias, as shown in
Figure 4-119.
Figure 4-119 Add an existing alias to the NT zone
370
IBM SAN Implementation
Now that we have selected all the zone members that we need, we commit the
changes to the switch by clicking the Apply button, as shown in Figure 4-120.
Figure 4-120 Applying the changes to the NT zone
Note that the box on the right-hand side of this screen (underneath the heading
NT_general_zone members) lists all the members in the zone, whether they are
WWN or port number based.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
371
We also want to set up a zone for our Windows 2000 cluster, and we will do this
using the WWN method. The procedure is similar to what we have shown earlier.
We create a new zone as shown in Figure 4-121.
Figure 4-121 Creating a zone for our Windows 2000 cluster
We create the zone name for the cluster as shown in Figure 4-122.
Figure 4-122 Zone name for our Windows 2000 cluster
372
IBM SAN Implementation
We then expand out the list of WWNs so we can see all the available entries that
the fabric recognizes, as shown in Figure 4-123.
Figure 4-123 WWPN display for attached devices
We had a problem at this point, as the WWPN for one of the servers we attached
did not appear in the WWPN list.
To diagnose the problem, we went back to the Fabric View and selected the
Name Server button. This displayed the screen shown in Figure 4-124.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
373
Figure 4-124 Using the Name Server display to find a specific WWPN
From this list, we could see that the WWPN / WWN for Port 2 on Domain ID 1
was not listed.
To check the status of Port 2, we closed this window and clicked the picture of
the switch from the Fabric View screen, as shown in Figure 4-125.
Figure 4-125 Launching the Switch View
From the Switch View in Figure 4-126, we can see that there is no status light
displayed for Port 2.
374
IBM SAN Implementation
Figure 4-126 Switch View of ITSOSW1 indicating a possible problem with port 2
This indicates that there is a possible problem with the connection to the device.
In our case Port 2 was connected to a Netfinity 5500 running a version of Red
Hat Linux. The Linux server was powered off so we powered the server on. Once
the Linux system had initialized the green light came on. We then closed the
Switch View and returned back to the Name Server table. Not all problems may
be this easy to solve, but checking for the basics may elicit a clue as to the likely
cause of the problem.
Note that Port_4 on the switch is displaying a steady yellow light, which indicates
that the port is receiving light but that the device is not online. In our case, Port_4
was connected to a Windows 2000 server that was unusable due to a failed disk
drive within the server.
The Name Server table shown in Figure 4-127 now shows the WWPN and WWN
for Port 2, as we originally expected.
Figure 4-127 Check Name Server display after fixing Port_2
Chapter 4. Implementing an IBM TotalStorage SAN Switch
375
We now close the Name Server table window and return to the Zone Settings for
our Windows 2000 zone. As we left the Zone Settings screen before applying the
changes we had to re-specify the zone name for the Windows 2000 cluster.
Once we had re-entered the zone name (as we originally entered in Figure 4-122
on page 372), we can add the WWPN for Port_2 as shown in Figure 4-128 by
highlighting the WWPN and clicking the Add Member button.
Figure 4-128 Zone Settings and the WWPN list for attached devices
376
IBM SAN Implementation
We repeat the process to add other WWPNs as illustrated in Figure 4-129 using
the relevant WWPN for our Windows 2000 cluster.
Figure 4-129 Select another WWPN to add to the zone configuration
Chapter 4. Implementing an IBM TotalStorage SAN Switch
377
We also add to this zone the connections to our MSS disk subsystem by
selecting the Port numbers as shown in Figure 4-130.
Figure 4-130 Creating a zone consisting of WWPNs and Port number
378
IBM SAN Implementation
This will create a zone that has both Hardware and Software based zoning.
Once we have completed the zone definitions, we click the Apply button to
commit the zone definition to the switch fabric, as shown Figure 4-131.
Figure 4-131 Display the zone settings for the W2K zone and apply changes
4.6.3 Incorporating additional switches
In this section we describe the steps for attaching another switch into the
switched fabric. We also review the use of aliases and how these can be used to
make setting up the SAN a little easier.
The new switch that we will connect is a 2109-S16 with 8 GBICs. We have cabled
Port_6 to one of our existing switches (ITSOSW1) as shown in Figure 4-132.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
379
Figure 4-132 Configuring ITSOSW3 into the SAN fabric
By returning to the Fabric View screen, we can now see all three switches
defined as part of the SAN fabric as show in Figure 4-133.
Figure 4-133 Switched Fabric with three switches
380
IBM SAN Implementation
An easy way of keeping track of the WWPNs for the attached servers is to go into
the Name Server Table, and as devices are plugged into the SAN, just keep
refreshing the display. This is shown in Figure 4-134.
Figure 4-134 Refreshing the Name Server Table
Keeping track of the WWPNs and WWNs for a server can be difficult as with
some platforms the only way of finding the WWPN / WWN is by rebooting and
using utility programs to configure the HBA card. You then have to write down the
relevant details. An easier way to find the WWPN and WWN for a device is to
plug them into the switch and refresh the Name Server Table as we have done.
This will display the WWPN / WWN by Domain ID and Port ID.
We used this approach as we plugged in a number of devices into our new
switch (ITSOSW3).
Chapter 4. Implementing an IBM TotalStorage SAN Switch
381
Once we had finished plugging the cables into the switch we checked the Switch
View in order to check the status of the attached devices as shown in
Figure 4-135.
Figure 4-135 Switch View after cabling ITSOSW3
This Switch View shows that this switch does not have a license for Fabric Watch
(if it did there would be a magnifying glass symbol above the beacon icon).
The IBM StorWatch Switch Specialist can still monitor the switch through the
Fabric View display, but we will not be able to use the Fabric View components to
monitor the status of the switch items such as fans, GBICs, performance,
temperature fluctuations, fan details, and so on.
382
IBM SAN Implementation
By clicking the Port_2 picture we can get more detailed information on the type of
port, its status and the GBIC specifications (assuming it is a “smart GBIC”). As
shown in Figure 4-136, Port_2 is defined as an E_port or Inter Switch Link (ISL).
Figure 4-136 Port Information for Port_2 on ITSOSW3
More alias definitions
For our third switch we have connected a number of servers and we have
decided to make an alias name for each server so it was easy to remember what
WWPN or WWN relates to the corresponding server name. To do this we created
aliases in the same way as in Section 4.6.1, “Using aliases” on page 360.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
383
We create an alias by going into the Zone Admin screen and clicking Create
Alias as shown in Figure 4-137.
Figure 4-137 Creating an alias based on WWPN
We are prompted to enter an alias name as shown in Figure 4-138.
Figure 4-138 Create alias called Bonnie
384
IBM SAN Implementation
We then select the relevant members using the member selection list on the
left-hand side of the screen show in Figure 4-139.
Figure 4-139 Adding a member based on WWPN
This will display all the WWPNs and WWNs that the switch can see. Once we
have selected the required WWPN / WWN, we click Add Member to build the
zone definition.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
385
We repeated the steps listed above to build aliases for the various devices, as
shown in Figure 4-140, in the drop-down list for Alias Names.
Figure 4-140 Display the aliases created
These new aliases are:
 RS/6000 servers
Bonnie, Clyde
 SAN device
SANDG1_port1
 NT servers
Jamaica
Brazil
386
IBM SAN Implementation
4.6.4 Zoning using Alias Names
Using the Alias Names created previously, we then created a new zone for our
AIX servers. To do this from the Fabric View screen, we clicked on the Zone
Admin button as shown in Figure 4-141.
Figure 4-141 Go to Zone Admin
Chapter 4. Implementing an IBM TotalStorage SAN Switch
387
From here, we select the Zone Settings tab as shown in Figure 4-142.
Figure 4-142 Go to Zone Settings
388
IBM SAN Implementation
From the Zone Settings screen, we selected the alias we wanted to add to the
AIX zone, as shown in Figure 4-143. Once selected, we then clicked the Add
Member button to update the Zone definition.
Figure 4-143 Adding the alias Bonnie to our AIX zone definition
Chapter 4. Implementing an IBM TotalStorage SAN Switch
389
We repeated this process for the aliases Clyde and MSS1 and then clicked the
Apply button to set up the AIX zone, as shown in Figure 4-144.
Figure 4-144 Apply the configuration to the AIX zone
This process created a new zone using the three aliases — MSS1, Bonnie, and
Clyde, with the MSS1 alias, using port numbers and the Bonnie and Clyde
aliases based on WWPNs.
This allows us great flexibility in creating and tailoring our zones, as we can use a
mix of port based and WWPN based aliases.
390
IBM SAN Implementation
4.6.5 Enabling a configuration
Once we have set up the required zones, we need to define an active
configuration for the fabric. This is done by selecting the Zone Admin function
from the Fabric View screen as shown in Figure 4-145.
Figure 4-145 Go to Zone Admin function
Chapter 4. Implementing an IBM TotalStorage SAN Switch
391
From the Zone Admin screen we select the Config Settings button as shown in
Figure 4-146.
Figure 4-146 Select Config Settings tab
392
IBM SAN Implementation
In a similar manner to creating zoning definitions, we click the Create Cfg button
as shown in Figure 4-147.
Figure 4-147 Create a switch configuration
This prompts us to enter a Configuration name as shown in Figure 4-148.
Figure 4-148 Save Configuration name
Chapter 4. Implementing an IBM TotalStorage SAN Switch
393
We then select the various zones that we want to include in the active
configuration. As shown in Figure 4-149, we select the AIX zone and confirm our
selection by clicking the Add Member function.
Figure 4-149 Add AIX zone to our Primary Configuration (Primary_config)
394
IBM SAN Implementation
We repeat the process for our three remaining zones (NT, Sun and W2K) and
then click the Apply button to activate the configuration as shown in
Figure 4-150.
Figure 4-150 Apply and enable the Primary_config setting to the switch
We also checked the Enable Config option which uses this configuration as the
active switch configuration.
This screen can be used to change configurations as required and will also show
the currently enabled configuration.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
395
Once the configuration is enabled, the config name will appear in the box marked
Config Currently Enabled as shown in Figure 4-151.
Figure 4-151 Config currently enabled
396
IBM SAN Implementation
4.7 Merging SAN fabrics
Merging a SAN fabric occurs where two or more separate fabrics are combined.
An example of this is shown in Figure 4-152.
Separate
Fabrics
Blue Fabric
Open Systems
Server
Open Systems
Server
Disk
Client
Tape
Disk
Switch
Red Fabric
Switch
Open Systems
Server
Client
Disk
Tape
Figure 4-152 Two separate SAN fabrics
Chapter 4. Implementing an IBM TotalStorage SAN Switch
397
These separate SAN fabrics can be merged to form a larger SAN fabric by
connecting the switches using an Inter-Switch Link (ISL) as shown in
Figure 4-153.
Merged
Fabrics
Open Systems
Server
Disk
Client
Open
Systems
Server
Tape
Disk
Switch
Inter Switch
Links
Switch
Open Systems
Server
Client
Disk
Tape
Figure 4-153 A merged fabric
The zoning information for each fabric is retained as are the domain IDs for the
switches, assuming that there are no conflicting definitions.
This could happen when an organization acquires another company or when two
business units within one company merge. The result is that a SAN fabric is
extended through the addition of another complete fabric.
Some conflicts might be identical zone names or, perhaps more common,
clashes with identical Domain IDs. In our next example, two fabrics are merged
and the domain IDs conflict. When this occurs, part of the SAN fabric is said to be
segmented.
398
IBM SAN Implementation
Figure 4-154 shows one SAN fabric called Fabric_1.
Figure 4-154 Fabric View of Fabric_1
This consists of two cascaded 2109-S08 switches (ITSOSW1 and ITSOSW2)
that are zoned.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
399
Figure 4-155 shows our second SAN fabric — Fabric_2.
Figure 4-155 Fabric View of Fabric_2
This fabric consists of a 2109-S16 (ITSOSW3) and a Fibre Channel Managed
Hub (ITSOHUB1).
400
IBM SAN Implementation
We connect the two fabrics together by cabling Port_6 on ITSOSW3 to Port_7 on
ITSOSW1. The Switch View for ITSOSW3 indicates Port_6 with a steadily
flashing green, as shown in Figure 4-156.
Figure 4-156 Switch View of ITSOSW3 showing segmented port
To check the status of the switch, we click the Switch Event button as shown in
Figure 4-157.
Figure 4-157 Go to Switch Event log
Chapter 4. Implementing an IBM TotalStorage SAN Switch
401
The Switch Event log is shown in Figure 4-158.
Figure 4-158 Switch Event log for ITSOSW3
This confirms that Port_6 is segmented. The message indicates that this is due
to the Domain ID’s overlapping.
We check the Fabric Event log for the other fabric by clicking the Fabric Events
button as shown in Figure 4-159.
402
IBM SAN Implementation
Figure 4-159 Go to Fabric Event log for Fabric_1
The Fabric Event log shown in Figure 4-160 confirms that the fabric has been
segmented.
Figure 4-160 Fabric Event log for Fabric_1
This log shows that Port_7 on ITSOSW1 has a problem.
The switches in Fabric_1 have a Fabric Watch license, and this has also
detected that the fabric has changed status due to the segmentation of the fabric.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
403
Expanding the message text as shown in Figure 4-161 indicates that the Fabric
Watch threshold was to notify when a segmentation of the fabric occurs.
Figure 4-161 Widen Message column
Pointing our browser back to the Fabric_2 switches, we can see from the Fabric
View screen in Figure 4-162 that the Domain ID for ITSOSW3 is set to 1.
Figure 4-162 Domain ID conflict
To change the Domain ID, we launch the Switch View as shown in Figure 4-163.
404
IBM SAN Implementation
Figure 4-163 Go to the Switch View
From the Switch View, we navigate to the Switch Admin View, as shown in
Figure 4-164.
Figure 4-164 Go to the Admin functions
Chapter 4. Implementing an IBM TotalStorage SAN Switch
405
From the Switch Admin screen, we change the Domain ID to 3 and commit the
configuration change as shown in Figure 4-165.
Figure 4-165 Changing the Domain ID
Figure 4-166 shows that Domain ID has been changed.
Figure 4-166 Domain ID reset message
406
IBM SAN Implementation
Returning to the Switch View, shown in Figure 4-167, we see that Port_6 is now a
steady green indicating that the port is now online and active.
The display reflects the Domain ID change and also shows that the switch is now
in a subordinate role as it is now cascaded to ITSOSW1.
Figure 4-167 Switch View after changing the Domain ID
Pointing our browser back to the IP address for ITSOSW1, as shown in
Figure 4-168, indicates that the SAN fabrics have successfully merged.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
407
Figure 4-168 Successfully merged fabric
Adding a previously configured switch
While the process described above is useful, not all segmentation issues will be
as simple as having duplicate Domain ID’s or zoning information. Therefore,
before adding a switch that has previously been configured, we recommend that
you reset the switch’s setup.
This can be done by issuing the configdefault and cfgclear commands. Using
these commands will reset the switch back to its factory default settings and
ensure that you will have a clean setup when you connect the used switch into
your SAN fabric.
408
IBM SAN Implementation
Follow the process shown to clear the switch’s configuration:
 Telnet into the switch that you are adding, for example, telnet 193.1.1.27,
and press Enter.
 Login, enter your userid and password, issue the command switchdisable.
and press Enter. This is necessary to modify switch parameters.
 Issue the configdefault command and press Enter to set the switch’s
configuration parameters back to the factory default settings. Any zone
information that was in this switch will be deleted.
 Issue the cfgclear command.
 Issue the switchenable command.
 Issue the reboot command.
After >switch:admin> configDefault, the switch will answer with “committing
configuration...done”
4.8 Fabric OS V2.4
Fabric OS V2.4 is the latest release of firmware supported by IBM on the S08
and S16. While similar to V2.1.7 and 2.2.1a, some Fabric Watch screens have
changed, and we review these differences in the following topics.
4.8.1 Fabric Events
This option provides a running log of events for all switches in the fabric.
By selecting the Fabric Events option, the screen shown in Figure 4-169 is
displayed. This is the same as we have seen previously.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
409
Figure 4-169 Fabric Event Log
4.8.2 Fabric Topology
Fabric Topology shows the physical view of the fabric, including active domains
and paths. The topology is shown as viewed from the host domain (this is the
switch definition that was entered in the Web browser)
The Fabric Topology report is also similar to what we have seen previously as
shown in Figure 4-170.
410
IBM SAN Implementation
Figure 4-170 Fabric Topology
Chapter 4. Implementing an IBM TotalStorage SAN Switch
411
4.8.3 Zone Admin
The Zone Admin function is used to set up and maintain the zones across the
fabric and to manage the active configuration.
To access the Zone Admin screens, you will need to be logged in using the
Admin userid.
Alias
The Alias tab is used to create and manage the aliases for devices in the fabric.
The alias can have one or more members, including switches, ports, WWNs and
QuickLoop AL_PAs.
As shown in Figure 4-171, the Zone Admin display is similar what we have seen
previously. The Alias screen has a new option — Add Host. This enables us to
more easily distinguish between hosts and other devices.
Figure 4-171 Zone Admin
412
IBM SAN Implementation
Creating an alias is similar to what we have done before. It is shown in
Figure 4-172.
Figure 4-172 Create an alias
We are prompted for an Alias Name as shown in Figure 4-173.
Figure 4-173 Save Alias Name
Chapter 4. Implementing an IBM TotalStorage SAN Switch
413
We then select the element from the Member Selection list that we want to
include in our alias, as shown in Figure 4-174. As we are creating an Alias for a
host, we use the Add Host option.
Figure 4-174 Creating an alias — Add Host
414
IBM SAN Implementation
Once the element has been added to the alias, we apply the change to the
switch configuration as shown in Figure 4-175.
Note that in the Member list, the alias is displayed with the letter H to distinguish
the member as a host. As with adding a member, the entry is in the form switch
ID and port ID.
Figure 4-175 Applying an alias with Host Names
Chapter 4. Implementing an IBM TotalStorage SAN Switch
415
Using a similar process, we can create a normal alias as shown in Figure 4-176.
Figure 4-176 Creating an alias using Add Member
We select the element to include in the alias from the Member Selection list and
add this to the Alias Member list, as shown in Figure 4-177.
Figure 4-177 Adding a Member to an Alias
416
IBM SAN Implementation
This time the alias is displayed in the format switch ID, port ID as shown in
Figure 4-178.
Figure 4-178 Applying changes to an alias
Chapter 4. Implementing an IBM TotalStorage SAN Switch
417
We now have two aliases, one defined as a Host Alias and one as a Device
Alias, as shown in Figure 4-179.
Figure 4-179 New alias definitions
418
IBM SAN Implementation
Zone
The Zone Settings tab is used to create and manage zones. A zone can have
one or more members, and can include switches, ports, WWNs, aliases, and
QuickLoop AL_PAs.
The Zone screen is the same as we have seen with the 2109 series, as shown in
Figure 4-180.
Figure 4-180 Zone screen
Chapter 4. Implementing an IBM TotalStorage SAN Switch
419
QuickLoop
This section can be used to create and manage the QuickLoops when used in
conjunction with zoning.
The QuickLoop screen is shown in Figure 4-181. For more information on
QuickLoop, refer to 4.3.5, “QuickLoop” on page 332.
Figure 4-181 QuickLoop screen
420
IBM SAN Implementation
In Figure 4-182 we show the Fabric Assist screen.
Figure 4-182 Fabric Assist screen
Chapter 4. Implementing an IBM TotalStorage SAN Switch
421
Configuration Settings
This screen is used to create and manage the zone configurations. The Zone
Configurations allow you to enable or disable a group of zones at the same time.
The Config screen is also the same as we have seen previously, as shown in
Figure 4-183.
Figure 4-183 Config screen
4.8.4 Fabric Watch
As with the previous version of firmware, Fabric Watch is used to monitor fabric
elements for potential problem conditions. This feature requires a Fabric Watch
license.
422
IBM SAN Implementation
One of the major differences with this version of the switch interface is in the
Fabric Watch Area. To select the Fabric Watch function, click the button as
shown in Figure 4-184.
Figure 4-184 Switch View — go to Fabric View
The Alarm notification screen is very similar to the previous version, but the
Classes in the frame on the left-hand side have been consolidated, and now all
Alarm notifications are displayed for the Select Class (previously the individual
Areas were displayed). This consolidates the information onto a single screen,
as shown in Figure 4-185.
Figure 4-185 Fabric Watch — Environment Alarm Notifications
Chapter 4. Implementing an IBM TotalStorage SAN Switch
423
Similarly, the Environmental Thresholds have been modified to show a graphical
view, as illustrated in Figure 4-186. This screen now uses a slider bar to set the
thresholds more easily. From this screen, the individual Classes can also be
selected.
Figure 4-186 Fabric Watch — Environmental Thresholds
424
IBM SAN Implementation
As shown in Figure 4-187, the Threshold type can be selected by clicking the
drop-down box. The threshold value can be a range or a trigger value, or it can
be set to issue an alert is a value is changed.
Figure 4-187 Setting the Threshold types — In-Between
Chapter 4. Implementing an IBM TotalStorage SAN Switch
425
Once the threshold type has been selected, we select the high and low threshold
values as shown in Figure 4-188.
Figure 4-188 Selecting the High and Low settings
426
IBM SAN Implementation
As we selected the High Value, we adjusted the slider bar to the required value,
as shown in Figure 4-189.
Figure 4-189 Setting the High Threshold value
Chapter 4. Implementing an IBM TotalStorage SAN Switch
427
We then select the Low Value and adjust the slider bar as shown in
Figure 4-190.
Figure 4-190 Setting the Low Threshold value
Once this is completed, we are prompted for the Alarm mechanisms that are to
be applied to the Class, as shown in Figure 4-191.
Figure 4-191 Alarm Mechanism screen
428
IBM SAN Implementation
The Current Settings tab will display information about the existing Fabric
Watch configuration for the particular Class, as shown in Figure 4-192.
Figure 4-192 Fabric Watch — Environment Current Settings
Chapter 4. Implementing an IBM TotalStorage SAN Switch
429
Selecting the Port details from the Fabric Watch Class list will display the Alarm
Notification screen, similar to that illustrated above. Selecting the Configure
Thresholds tab allows us to set the Areas that we want to monitor as shown in
Figure 4-193.
In this screen we have selected to monitor the Link Loss Area and have specified
this for Port 0.
Figure 4-193 Setting Port Threshold values — Link Loss
430
IBM SAN Implementation
As shown in Figure 4-194, we select to monitor the Link Loss and State
Change Areas for Port 1.
Figure 4-194 Setting Port Threshold values — State Changes
Chapter 4. Implementing an IBM TotalStorage SAN Switch
431
Selecting the GBIC details from the Fabric Watch Class list will display the Alarm
Notification screen, as shown in Figure 4-195.
Figure 4-195 Fabric Watch — GBIC Alarm Notifications
432
IBM SAN Implementation
Selecting the Configure Threshold tab displays the threshold settings as
displayed in Figure 4-196. For the GBIC Class, we can monitor the Temperature,
Transmit and Receive Power, and the Current for each GBIC.
Figure 4-196 Fabric Watch — GBC Thresholds
Chapter 4. Implementing an IBM TotalStorage SAN Switch
433
The Current Settings tab will display the existing values for the GBIC class as
shown in Figure 4-197.
Figure 4-197 Fabric Watch — GBIC Current Settings
Selecting the other Classes from the Fabric Watch list will display screens similar
to those described above, so we will not review each screen.
434
IBM SAN Implementation
Selecting the Fabric Details from the Fabric Watch Class list will display the
Alarm Notification screen as shown in Figure 4-197. This displays Fabric-wide
events that have generated Fabric Watch alerts.
Figure 4-198 Monitoring the Fabric — Alarm Notification
Chapter 4. Implementing an IBM TotalStorage SAN Switch
435
The Thresholds can be set as shown in Figure 4-199. From the drop-down box
on this screen, we can select whether to monitor the alerts using a threshold,
trigger or changed value.
Figure 4-199 Monitoring the Fabric — Setting Fabric Thresholds
436
IBM SAN Implementation
As for the other Classes, the Current Settings for the Fabric Class can be
displayed by selecting the tab as shown in Figure 4-200.
Figure 4-200 Monitoring the Fabric — Current Settings
Chapter 4. Implementing an IBM TotalStorage SAN Switch
437
4.8.5 Performing maintenance
In the following topics we show how to perform maintenance.
Disabling a switch
Sometimes a switch may need to be disabled and removed from the
configuration before making changes, for example, when using the configure or
configuredefault commands, or when running diagnostic tests. All Fibre
Channel ports will be taken offline. If the switch was part of a fabric, the
remaining switches will reconfigure.
This can be performed by launching the Admin View for the required switch,
which will then display the screen as shown in Figure 4-201.
Figure 4-201 Switch Admin
438
IBM SAN Implementation
To disable the switch, click the Switch Disabled button in the top right-hand
corner and commit the configuration changes as shown in Figure 4-202.
As this removes the switch from the configuration, care should be taken to
ensure that this action will not impact any users.
Figure 4-202 Disabling a switch
Chapter 4. Implementing an IBM TotalStorage SAN Switch
439
Once the Commit button is clicked, the switch is removed from the configuration,
and all the port LEDs will flash yellow simultaneously, as shown in Figure 4-203.
Figure 4-203 Disabled Switch
A message is issued advising that the switch has been disabled as shown in
Figure 4-204.
Figure 4-204 Disabled switch message
Once the switch goes offline, the other switches status may change, depending
on the Fabric Watch settings. The disabling of a switch will cause ISL links to
display as down, and this may change in the switch status.
To re-enable the switch, uncheck the Disable Switch box in the top right-hand
corner and click the Commit Changes button again as shown in Figure 4-205.
440
IBM SAN Implementation
Figure 4-205 Restarting a disabled switch
This will generate the message shown in Figure 4-206.
Note that the switch does not need to be re-booted. It is just removed from the
switch configuration.
Figure 4-206 Switch enabled message
Chapter 4. Implementing an IBM TotalStorage SAN Switch
441
4.9 2109-S16 Integrated fabric RPQ 8S0566
Available as a Request for Price Quotation (RPQ), the 2109-S16 Integrated
Fabric is designed to extend IBM TotalStorage SAN Switch Model S16 storage
networking by providing a cost-effective means of meeting large port count
requirements. The solution combines six rack-mounted IBM TotalStorage SAN
Switch Model S16s with preconfigured switch interconnections and management
software.
The Integrated Fabric approach can significantly simplify the deployment and
management of large SAN fabrics. The 64 user ports of the Integrated Fabric can
be managed as a single switch entity in the SAN Fabric. The Integrated Fabric
supports business-critical SAN applications such as storage consolidation, data
protection, disaster tolerance, data sharing, and new SAN-enabled applications
such as dynamic storage resource and volume management.
The integrated design accelerates the configuration of the cables and InterSwitch
Link (ISL) Gigabit Interface Converters (GBICs) that make up the fabric with 32
pre-installed and wired ISLs and associated cable management. The Integrated
Fabric delivers high-density connectivity for large SAN fabrics and helps simplify
the task of designing and building high-availability SANs.
SAN Fibre Channel Switch ISLs are prewired and installed with 32 short-wave
GBICs and cable management harnesses to make the integrated fabric easier to
install, upgrade, and manage. Color-coded ISL cable diagrams and cables, along
with the ability to replace a single switches, help improve availability and
minimize downtime in the event of a failure.
SAN Fibre Channel Switches may be configured with a second power supply for
high availability requirements. A GBIC-based modular design makes it easy to
hot-swap connections quickly. Highly reliable switch components, continuous
monitoring of environmental components (fan status and temperature), and
extremely durable construction all maximize MTBF to improve availability. Hot
swappable Fibre Channels Switches in an integrated switch fabric provide
redundancy. With host-based failover support, automatic rerouting across
switches help ensure continued operation if one module fails.
The management and administration is based on the functions and features that
we have discussed in the previous topics.
442
IBM SAN Implementation
4.10 TotalStorage Fibre Channel Switch 2109-F16
IBM introduces a new model of the IBM TotalStorage Storage Area Network
(SAN) Switch family, providing 2 Gigabit Fibre Channel (FC) performance and
additional functions to support the storage networking demands for higher
security, throughput, and management controls.
As there is a lot of similarity between the screen navigation of the S08/S16 and
F16 models, we restrict this particular topic to those new features that this brings
to the market. Users that are familiar with the S08/S16 will have no problem
upgrading their awareness to successfully encompass the F16.
We show a picture of the 2109-F16 in Figure 4-207.
Figure 4-207 2109-F16 switch
Chapter 4. Implementing an IBM TotalStorage SAN Switch
443
4.10.1 Product overview
The new IBM TotalStorage SAN Switch F16 is a 16-port Fibre Channel switch
based on a new generation of switch technology. It provides 2 gigabit per second
port-to-port throughput with auto-sensing capability for connecting to existing 1
gigabit per second host servers, storage, and switches, in a smaller 1U form
factor, requiring half the space of the previous 16-port SAN Switch.
The new model is fully interoperable with the current IBM TotalStorage SAN
Switches (Models S08 and S16), and can be added to existing fabrics with
minimal disruption, enabling an easy transition for existing Fibre Channel storage
networks to the faster technology.
The IBM TotalStorage SAN Switch Model F16 extends the broad range of
scalable SAN connectivity solutions available from IBM for a wide variety of host
and storage types. IBM TotalStorage SAN Switches enable storage resources to
be shared efficiently and to scale rapidly to meet the demands by users for highly
available, heterogeneous access to expanding storage pools.
The new Model F16 provides:
 Sixteen non blocking ports, each with full-duplex throughput at either 2
gigabits per second or 1 gigabit per second.
 Auto-sensing ports that self-negotiate to the highest speed supported by the
attached server, storage, or switch.
 Universal ports that self-configure as F_ports, FL_ports, or E_ports.
 Each port supports the new Small Form-Factor Pluggable (SFP) media with
options for either shortwave optical connection for distances up to 300
meters, or longwave optical connections for distances up to 10 kilometers.
 A smaller 1U package that can be either rack-mounted or used in a table-top
configuration, with the option of a redundant power supply, providing a highly
available switch.
 Hardware zoning controlled at the port level, and software zoning controlled at
the worldwide name level.
 Support for high-speed data traffic with the Performance Bundle feature,
which provides Inter-Switch Link (ISL) Trunking and Performance Monitoring.
Up to four ISLs can be combined for throughput capability of up to 8 gigabits
per second.
 Cascading support for flexibility in creating scalable fabric topologies.
 Distributed fabric services such as name serving, zoning, routing, and
microcode upgrade.
444
IBM SAN Implementation
 The IBM TotalStorage SAN Switch Specialist, which provides a
comprehensive set of management tools that support a Web browser
interface for flexible, easy-to-use operations.
4.10.2 Hardware components
The 2109 Model F16 system board is a single-board design with a highly
integrated CPU. The Intel 80960VH CPU is a RISC core processor and is the top
choice for this platform. It provides over 70% of the functionality for the digital
section of the system board. The system uses three types of memory devices:
DRAM, Flash File, and Boot Flash. On the Fibre Channel section of the system
board, the Bloom ASICs, the Serializer/Deserializer (SERDES), and the SFP
media are the key components that provide high-speed data transfer. SFP media
interfaces support SWL and LWL.
The system chassis is a 1U height enclosure with space for two power supply
units and one system board. The system board is placed in an Electromagnetic
Interference (EMI) enclosure tray as an EMI-proof system unit. Two 126-watt
removable, redundant power supplies provide hot-swappable capability. Cooling
fans are mounted in the rear to provide airflow for system cooling.
CPU subsystem
An Intel 80960VH CPU is used for switch initialization and management
functions. The CPU runs the Fabric OS and is responsible for switch initialization,
configuration, and management. IBM-designed ASICs provide the switching
functionality.
The following peripherals are supported as well:






An Ethernet port
A serial port
Three digital thermometers
A real-time clock
Two power supply controls
General I/O
The CPU subsystem is a mixed voltage system using 1.8 V, 2.5 V, 3.3 V, and 5 V
depending on the device. The maximum board power consumption is 78 W.
Features
The 2109-F16 CPU subsystem includes the following features:
 A 80960VH-100 MHz CPU
 A SDRAM controller with parity check at 33 MHz
 A peripheral control interconnect (PCI) bus arbiter
Chapter 4. Implementing an IBM TotalStorage SAN Switch
445
 An on-board SDRAM with data parity to support a 16 MB configuration
 One PLCC32 Boot Flash socket to support up to 512 KB of Flash memory
 8 MB (2 x 4 MB) Flash memory for software storage
 10BASE-T or 100BASE-T port for management connection with RJ45
connector
 One RS232 port with DB9 connector
 16 LEDs to indicate the status for each port
 16 LEDs to indicate the link speed for each port
 One LED (green) to indicate the system power-on status
 Three digital thermometers for temperature sensing
 Two analog switches to control the power supply inter-integrated circuit (I2C)
bus access
 One 3.3 V to 1.8 V dc/dc converter for Bloom ASIC core supply
 Two Bloom ASICs supporting up to 16 nonblocking ports
 16 SERDES
 One real-time clock with a battery and 56 bytes of nonvolatile RAM (NVRAM)
Embedded processor
The embedded processor is an Intel 80960VH processor with a clock speed of
100 MHz. It contains the following:
 A high-performance RISC processor core (compatible with the 2109 series of
switches and the 3534 switch)
 An integrated EDO memory controller (for DRAM, SRAM, ROM, and Flash
memory)
 A PCI bus interface
 A complex programmable logic device (CPLD) for SDRAM control
 Two direct memory access (DMA) channels
 An I2C interface
 General purpose I/O
You access system memory through the local bus. The external CPLD SDRAM
device provides SDRAM controller functionality at 33 MHz. It supports parity
checking to enhance the data integrity of the system. The CPU communicates
with the ASIC and the 10BASE-T or 100BASE-T Ethernet media access
controller (MAC) through the PCI interface. An external PCI bus arbiter enables
the Ethernet device to be a bus master.
446
IBM SAN Implementation
You can also access the RS232 Universal Asynchronous Receiver Transmitter
(UART) serial port through the local bus. Other I/O peripherals, such as the
real-time clock, the two power supply controls, the LEDs, the three digital
thermometers, and miscellaneous I/O are handled by the I2C bus of the CPU.
The CPU is the only I2C bus master in the system. The RS232 port and drivers,
Ethernet MAC/PHY, and LEDs are external components to the CPU. An RJ45
connector provides Ethernet connection to external systems. The DB9 RS232 is
a ribbon-cable connection through the on-board 10-pin header.
Bus operations
The interface between the embedded processor, the ASICs, and the 10BASE-T
or 100BASE-T Ethernet MAC is implemented using a PCI bus. All PCI devices
on the bus are PCI Revision 2.2 compliant. The PCI bus interface operates at
32-bit, up to 33 MHz and has a worldwide even parity bit. A slave-only PCI
interface is provided by each ASIC to allow the processor to program various
registers, routing tables, and so on within the chip. An external PCI bus arbiter
enables the Ethernet device to be a bus master.
The local bus, a 32-bit multiplexed burst bus, provides the interface between the
system memory and the I/O. Because the integrated EDO memory controller on
the CPU allows only direct control for DRAM, SRAM, ROM, and Flash memory,
the external CPLD controller is included to provide SDRAM controller
functionality.
The I2C bus provides peripheral I/O control for the LEDs, the thermometers, and
general I/O functions. The 80960VH CPU serves as the master on the I2C bus.
Each Bloom ASIC is an eight-port Fibre Channel switch controller. There are two
Bloom ASICs to support up to 16 ports. The communication between ASICs is
over a proprietary 10-bit wide SSTL2 bus running at 106.25 MHz. An SSTL2 bus
is also used between the Bloom ASICs and the SERDES.
Memory
The system design uses the following three types of memory devices:
 DRAM
 Flash File
 Boot Flash
Two on-board SDRAM chips provide up to 16 MB for system memory. Two
additional SDRAM chips provide data parity. The printed circuit board (PCB)
SDRAM footprint is designed to be compatible with 64 MB, 128 MB, and 256 MB
devices. An external CPLD device added to the local bus provides control
functions for the 80960VH processor.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
447
The system provides 4 MB of on-board redundant Flash File memory for
software and data storage. The Boot Flash is an 8-bit Flash device socket that is
used only for system start. The Boot Flash device contains a block area for
startup code protection. The PLCC32 socket supports 3.3 V Boot Flash memory
up to 512 KB.
Central memory
As with the 2109 series of switches and the 3534 switch, the 2109 Model F16 is
based on a central memory architecture. In this scheme, a set of buffers in the
central memory is assigned to each port, to be used for receipt of frames. As an
ASIC port receives and validates a frame, it stores the frame in one of its receive
buffers in the central memory and forwards a routing request (a Put message) to
the appropriate destination ports.
When a destination port is capable of transmitting the frame, it reads the frame
contents from central memory and forwards the frame to its transmit interface. It
does not wait for the frame to be written in memory, unless the port is busy. After
it has removed an entry for a frame from its internal transmit queue in preparation
for transmitting a frame, the destination port sends a transmission complete
message (a Finish message) to the port that received the frame. This allows the
receiving port to reuse the buffer for subsequent frames received.
The central memory is also incorporated into the ASICs. Frames received on the
ports in an ASIC are written into the portion of central memory in the receiving
chip; received frames cannot be written into the sections of central memory
located in other ASICs. All transmitters in a 2109 Model F16 switch can read
from the memories in any of the ASICs, through inter-chip connections clocked at
106.25 MHz.
Each ASIC contains RAM devices plus data path crossbar logic that is used to
implement the central memory. Memory blocks are accessed in a time-sliced
fashion. The buffer pool can be split into 2112-byte buffers or into 312-byte
mini-buffers. If frames that need to be buffered are smaller than the maximum
2112 bytes, using mini-buffers effectively expands the buffer pool and increases
the efficiency of memory usage by providing more (but smaller) receive buffers.
Additionally, the Bloom ASIC provides a special memory interface (SMI). The
SMI provides the firmware with a mechanism to read and write frame contents to
and from the ASIC. It also supports higher throughput transfers. The SMI
includes a set of two buffers that are large enough for an entire maximum-sized
frame to be transferred in a single operation. Additionally, because there are two
buffers available, the firmware can perform a read or write on a frame in one of
the buffers while the ASIC streams another frame into the other buffer.
448
IBM SAN Implementation
ASICs
Two ASICs within the system provide the switching functionality. Each ASIC
provides eight Fibre Channel ports that can be used to connect to external
N_ports (as an F_port), external loop devices (as an FL_port), or to other 3534 or
2109 series boxes (as an E_port).
Each port can operate at either 1.0625 Gb/s or 2.125 Gb/s link speeds. The ASIC
contains the Fibre Channel interface logic, message and buffer queuing logic,
receive buffer memory for the eight on-chip ports, and other support logic.
The Bloom ASICs are PCI slaves to the CPU. The two ASICs interface through
an inter-chip 10-bit SSLT2 bus connection clocked at 106.25 MHz. A 16-channel
SERDES is used to support 16 ports. The interface between ASIC and SERDES
is also a 10-bit SSTL2 bus running at 106.25 MHz. The SERDES converts the
10-bit wide parallel data from the SSTL2 bus into high-speed serial data for the
SFP media and vice versa. The SERDES supports single data rate (SDR) or
double data rate (DDR) transfer between the SERDES and the SFP media. The
DDR operation supports 2.125 Gb/s data transfer rate between ASICs.
Implementing the SERDES external to the ASIC reduces the risk of silicon
packaging as well as the risk of running 2.125 Gb/s signals on a board with a
long trace length.
The SFP media interfaces to external devices and enables support for
short-wave laser and long-wave laser. Two LEDs for each port provide port
status and link speed information.
Control Message Interface (CMI)
The 2109 Model F16 Control Message Interface (CMI) consists of a set of control
signals that are used to pass hardware-level messages between ports. Recipient
ports use these control signals to inform transmitting ports when a new frame
needs to be added to the output queue of the transmitter. Transmitting ports also
use the CMI to inform recipient ports that a frame transmission has been
completed. A recipient port is free to reuse a receive buffer when it receives
notification that the frame has been transmitted. In the case of multicast, multiple
notifications are required to determine when a receive buffer is freed.
The CMI interfaces for the ASICs are connected inside each ASIC through a
message crossbar, implementing a barrel shift message scheme. Each chip time
slices its output port to each possible destination chip in the switch. If it has a
message to send to a particular destination during the corresponding timeslot,
the chip uses the timeslot to send the message. Otherwise, the output port lines
are driven to indicate that no message is present.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
449
The time slicing of the output CMI control signals of the ASICs are arranged out
of phase from each other so that each chip’s output port is time sliced to a
different destination chip in any given clock cycle. Messages that are displayed
at the input control signal interface of a given ASIC are also time sliced through
each possible source chip in the switch.
Ports
The 2109 Model F16 supports the following port types:
 Optical ports
 Ethernet port
 Serial port
Each ASIC in the 2109 Model F16 switch connects up to eight SFP media. SFP
devices are encased in metal to ensure low emissions and high thermal
management. They are hot-swappable and use industry-standard local channel
connectors. Each port provides ISL, loop, and fabric (E, F, and FL respectively)
type connectivity that the 2109 Model F16 senses automatically; it requires no
administration to identify the port type.
Optical ports
For optical ports, the 2109 Model F16 uses SFP fiber-optic transceivers that
convert electrical signals to optical signals (and optical signals to electrical
signals). Capable of transmitting at both 1 and 2 Gb/s speeds, each SFP
fiber-optic transceiver supports 850 nm SWL on multimode fiber-optic cable,
1310 nm LWL on single-mode fiber-optic cable, and 1550 nm ELWL 5 on
single-mode fiber-optic cable. These miniature optical transceivers provide high
port density and deliver twice the port density of standard removable GBIC
transceivers.
Ethernet port
The 2109 Model F16 provides a fully IEEE-compliant 10BASE-T or 100BASE-T
Ethernet port for switch management console interface. When a device is
connected to the port, both ends negotiate to determine the optimal speed. The
Ethernet port uses an RJ45 connector. There are two LEDs for the port. One
LED indicates transmit and receive activity and one LED indicates speed (10
Mbps or 100 Mbps). The TCP/IP address for the port can be configured from the
serial port.
Serial port
An RS232 serial port is provided on the 2109 Model F16. The serial port uses a
DB9 connector. The connector is a header pin block on the system board. The
parameters of the serial port are fixed at 9600 baud, 8 data bits, no parity, no
hardware flow control, 1 start and 1 stop bit.
450
IBM SAN Implementation
You use this connector to configure the IP address and to recover the factory
default settings of the switch should Flash memory contents be lost. The serial
port connection should not be used to perform normal administration or
maintenance functions. Accessible functions are limited to connecting a terminal
to the port to reinitialize the switch defaults, which restores the switch to its
factory configuration. This is required to restore the switch passwords to a known
state and to allow customers to set a specific switch IP address.
Enclosure
The 2109 Model F16 enclosure is designed to be mounted in a 19-inch rack, with
a height of 1 RETMA unit (1µ), but it can also be used in a tabletop configuration.
The enclosure houses dual-redundant power supplies, dual-redundant fan
assemblies, and a system board that supports the two ASICs and the CPU.
The 2109 Model F16 enclosure has forced-air cooling. The fans push the air from
the rear chassis intake through the enclosure and exhaust the air through venting
holes in the front panel. The SFP media, the cooling fan, and the power supplies
are hot-swappable so that they can be removed and replaced without
interrupting the system power.
The top panel of the 2109 Model F16 enclosure can be removed without tools,
allowing access to the system board. The enclosure design provides for simple
assembly of the system board into the enclosure, allowing for ease of
manufacture and maintenance. All pieces of the product are modular, and all
maintenance can be performed without special tools.
On the front of the unit, there are two port connections (an RS232 connection
and an RJ45 connection). The RJ45 connection provides a 10BASE-T or
100BASE-T Ethernet port for a full system management console interface. The
RS232 connection provides a serial port interface for setting the IP address of
the switch and for resetting the switch to factory defaults
The fibre-optic cables, Ethernet cables, and serial port cables are located on the
front of the switch. AC power input cables, power supplies, and cooling modules
are inserted and removed from the rear of the switch.
Power supply
The 2109 Model F16 power supply is a hot-swappable switching unit, allowing
1+1 redundant configurations. The unit is a universal power supply capable of
functioning worldwide without voltage jumpers or switches. The fully enclosed,
self-contained unit has its own internal fans to provide cooling. It is auto-ranging
in terms of accommodating input voltages.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
451
The power supply has three DC outputs (3.3 V, 5 V, and 12 V) that provide a total
output power of 126 maximum usable watts. The power supplies plug directly
into the enclosure from the rear of the unit, mating to internal blind connectors
that connect both the DC outputs and the interface signals to the system
backplane. An integral on/off switch, input filter, and power indicator are provided
in the power supply.
LEDs
The 2109 Model F16 provides several LEDs to indicate status on the switch.
Each of the 16 ports has two status indicators. The first LED for the port is a
two-color (green and yellow) LED, and indicates the status for the port. Green
indicates normal status, and yellow indicates an error. The second LED is a
single-color (green) LED and indicates the link speed for the port. Green
indicates 2 Gb/s; if the LED is not lit (dark), it indicates 1 Gb/s.
A single-color (green) LED is located at the front of the unit and indicates system
power-on status. On the back of the unit, there is a two-color (green and yellow)
LED driven by an I2C I/O expander that indicates the mode of the unit (Green
indicates normal mode and yellow indicates diagnostic mode). All LEDs are
surface mount components with on-board light pipe and are visible externally
with full chassis enclosure. There are two LEDs for the Ethernet port. One LED
indicates the transmit and receive activity and one LED indicates speed (10
Mbps or 100 Mbps).
4.10.3 Software specifications
The 2109 Model F16 switch is supported by the Fabric OS Version 3.0. The
Fabric OS is implemented in firmware and manages the operation of the 2109
Model F16 switch. The switch firmware is designed to make a 2109 Model F16
easy to install and use while retaining the flexibility needed to accommodate user
requirements. A fabric constructed with cascaded 2109 Model F16 switches
automatically assigns individual switch addresses, establishes frame routes,
configures the internal name server, and so on.
Users can access internal management functions using standard host-based
Simple Network Management Protocol (SNMP) software or Web browsers. They
can access these functions using network connectivity through the Ethernet port
or using Internet Protocol (IP) over the Fibre Channel ports. SCSI Enclosure
Services (SES) is also supported as a management method. The management
functions of the switch allow a user to monitor frame throughput, error statistics,
fabric topology, fans, cooling, media type, port status, IDs, and other information
to aid in system debugging and performance analysis.
452
IBM SAN Implementation
The Fabric OS includes all basic switch and fabric support software as well as
optionally licensed software that is enabled using license keys. The fabric license
is pre-installed on the 2109 Model F16 switch to ensure fabric operation. The
Fabric OS is composed of two major software components:
 Firmware that initializes and manages the switch hardware
 Diagnostics that perform component self-testing algorithms for fault isolation
during the manufacturing process and in customer installations
The internal firmware can be viewed as a set of embedded applications running
on top of a proprietary real-time operating system.
Additionally, host-based software includes the drivers, utilities, and applications
that use the switch. You can obtain these components from your system vendor
or Fibre Channel component supplier.
2109 Model F16 software
The 2109 Model F16 software consists of a set of embedded applications
running on top of a real-time operating system kernel. The set of applications
include the following:
 Name server
 Alias server
 SNMP agent
The set of applications also includes several tasks to manage the following:











Address assignment
Routing
Link initialization
Fabric initialization
Link shutdown
Switch shutdown
Frame filtering
Performance monitoring
Trunking
Auto speed negotiation
The user interface
All embedded applications are written in C, except for the SNMP agent (included
with the real-time operating system package) and the Web Server.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
453
Applications
The 2109 Model F16 software applications implement a variety of functions.
Switch applications exist to provide fabric services, such as name server and
alias server functionality, to external devices. These particular applications
process requests from fabric-attached external devices, and communicate with
similar applications running on other switches within the fabric to obtain
fabric-wide information to satisfy these requests. The applications present an
interface to these standards-based services that provides access to information
throughout the fabric while hiding the details of how the information is distributed
across switches within the fabric from the external devices.
Other applications running in a switch implement functions used to manage
internal fabric operation. One task allows for automatic address assignment
throughout a fabric through a distributed algorithm run by participating switches.
Another task, used to set up routes within the fabric, communicates with tasks
that are running on other switches in the fabric to set up loop-free, lowest-cost
routes.
The 2109 Model F16 switch provides an extensive set of diagnostics. A number
of comprehensive low-level diagnostics can be used to detect failing switch
hardware components by performing hardware-specific tests. In general, these
diagnostics must be run when the switch is offline. However, an additional set of
high-level diagnostics can be used to exercise individual ports, passing data
through external media interfaces and cables. These allow various media, cable,
and port faults to be detected while normal switch operation continues on other
ports.
New features
The 2109 Model F16 software includes some new features and functionality. The
Fabric OS enables the 2109 Model F16 to support the new functionality
described in the following sections.
Auto-sensing speed negotiation
The 2109 Model F16 ASIC supports link operation at either 2 Gb/s or 1 Gb/s.
Auto-sensing negotiation allows easy configuration. Connect the device in and
the link speed is negotiated to the highest speed that is supported by the device.
Speed selection is auto-negotiated by the ASIC driver on a per-port basis.
After the speed is determined, the transmitter and receiver for the port are
automatically set. If multiple devices are connected to a port (for example, on an
FL_port), the driver auto-negotiates for the highest common speed and sets the
transmitter and receiver accordingly.
454
IBM SAN Implementation
Frame filtering
Zoning is a fabric management service that can be used to create logical subsets
of devices within a SAN and enable partitioning of resources for management
and access control purposes. Frame filtering is a new feature of the 2109 Model
F16 ASIC that enables it to provide zoning functions with finer granularity. Frame
filtering can be used to set up port level zoning, world wide name zoning, device
level zoning, protocol level zoning, and LUN level zoning. After the filter is set up,
the complicated function of zoning and filtering can be achieved at wire speed.
Performance Monitoring
Performance Monitoring is a licensed feature that provides error and
performance information to manage your storage environment. There are three
types of monitoring:
Arbitrated Loop Physical Address (AL_PA) monitoring — This provides
information regarding the number of CRC errors.
End-to-end monitoring — This provides information regarding a configured
source identifier (SID) to destination identifier (DID) pair. Information includes the
number of CRC errors for frames with the SID-DID pair, Fibre Channel words
transmitted from the port for the SID-DID pair, and Fibre Channel words received
for the port for the SID-DID pair.
Filter-based monitoring — This provides error information with a
customer-determined threshold.
Trunking
Trunking is a new feature on the 2109 Model F16 switch that enables traffic to be
distributed across available inter-switch links (ISLs) while still preserving in-order
delivery. On some Fibre Channel protocol devices, frame traffic between a
source device and destination device must be delivered in order within an
exchange.
This restriction forces current devices to fix a routing path within a fabric.
Consequently, certain traffic patterns in a fabric can cause all active routes to be
allocated to a single available path and leave other paths unused. The 2109
Model F16 ASIC creates a trunking group (a set of available paths linking two
adjacent switches).
Ports in the trunking group are called trunking ports. One trunking port is
designated as the trunking master port and is used to set up all routing paths for
the entire trunking group. The trunk provides an 8 Gb/s single-aggregate ISL
pipe between switches.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
455
Real-time operating system
The 2109 Model F16 real-time operating system consists of a
hardware-independent layer and a hardware-dependent section.
The hardware-independent portion of the operating system consists of a
third-party real-time kernel plus a number of interfaces. The interfaces provide a
structure for handling various layers in the Fibre Channel protocol hierarchy.
In this collection of modules, the FC-PH layer provides FC-2 functionality,
supporting reassembly of inbound frames into sequences. This layer also allows
for creation of a set of frames to transmit from an internal Fibre Channel
sequence description.
The FC-LS layer handles various sorts of Fibre Channel link services, including
basic link services and extended link services.
Operations using the Fibre Channel common transport interface, as defined in
the FC-GS specification, use the interface provided by FC-CT code in the 2109
Model F16.
Switch-to-switch communications used to manage fabric initialization and routing
use the services provided by the FC-SW layer to implement these functions.
Hardware-dependent functions of the real-time operating system contain a
number of elements, including the Board Support package. This code is used to
provide an interface between VxWorks and the 2109 Model F16-specific
hardware related to supporting the 80960VH processor.
Drivers for specific hardware interfaces are also considered part of the
hardware-dependent portion of the real-time operating system. A number of
drivers support interface hardware that is used for fabric management purposes,
such as the Ethernet port and serial port. Other drivers are used for
miscellaneous internal functions, including temperature monitoring and power
supply control.
Additional drivers, written for the Fibre Channel interfaces of the switch, are
managed through two layers. One of these, the port driver, creates a generic
interface to the underlying switch hardware, and provides functions common to
all switch implementations. Reporting to the port driver are the
switch-hardware-specific drivers, which handle the operations of individual types
of switch ASICs. Three of these drivers, for the Stitch, Flannel, and Loom chips,
are used for IBM’s first and second-generation hardware. A fourth module
implements the functionality required to drive the Bloom ASIC, which is used in
the 2109 Model F16 switch.
456
IBM SAN Implementation
Initialization
When the system is started or restarted, the following operations are performed:
1. Early power-on self test (POST) diagnostics are run. POST is run before
VxWorks is running.
2. VxWorks is initialized.
3. The hardware is initialized. The system is reset, the internal addresses are
assigned to Loom chips, the Ethernet port is initialized, the serial port is
initialized, and the front panel is initialized.
4. A full POST is run.
5. The links are initialized. Receiver and transmitter negotiation is run to bring
the connected ports online.
6. A fabric exploration is run. This determines whether any ports are connected
to other switches. If so, it determines the principal switch.
7. Addresses are assigned. After the principal switch is identified, port
addresses are assigned. Each 2109 Model F16 tries to keep the same
addresses that it used previously. Previous addresses are stored in the
configuration Flash memory.
8. The routing table is constructed. After the addresses are assigned, the
unicast routing tables are constructed.
9. Normal Nx_port operation is enabled.
Routing
The embedded processor maintains two routing tables, one for unicast and one
for multicast. The unicast routing tables are constructed during fabric
initialization. The multicast tables are initially empty, except for broadcast. After
the tables have been constructed they are loaded into each ASIC.
The unicast tables change if ports or links come online or go offline, or if some
other topology changes occur. When new paths become available, the
embedded processor can change some routes in order to share the traffic load.
The multicast tables change as ports register with the alias server to create, join,
or leave a multicast group. Each time a table changes it must be reloaded into
the ASICs.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
457
Service functions
The ASIC interrupts the embedded processor when a frame arrives that has an
error (for example, incorrect source ID), when a frame times-out, or when a
frame arrives for a destination that is not in its routing tables. In the latter case,
the frame might be addressed to an illegal destination ID, or it might be
addressed to one of the service functions that are provided by the embedded
processor such as SNMP, name server, or alias server.
SNMP
Simple Network Management Protocol (SNMP) allows network devices to be
monitored, controlled, and configured remotely from a network management
station running a network manager program.
SNMP agent code in the network device allows management by transferring data
that is specified by a Management Information Base (MIB).
The 2109 Model F16 switch agent supports the following:







SNMPv1 manager
Command-line utilities to provide access to and command the agent
MIB-II system group, interface group, and SNMP group
Fabric-element MIB
IBM-specific MIBs
Standard generic traps
IBM-specific traps
Diagnostics
The 2109 Model F16 switch supports a set of power-on self tests (POSTs), as
well as tests that can be invoked using Telnet commands. These diagnostics are
used during the manufacturing process as well as for fault isolation of the product
in customer installations.
Diagnostic environment
Most diagnostics are written to run in the VxWorks environment. However, as
VxWorks does not run without a working SDRAM, a SDRAM/boot EEPROM test
is run as part of the pre-VxWorks startup code to verify that the basic
processor-connected memories are functioning properly.
Hardware support
Loop-back paths for frame traffic are provided in the hardware for diagnostic
purposes. A loop-back path within the ASIC, at the final stages of the Fibre
Channel interface, can be used to verify that the internal Fibre Channel port logic
is functioning properly, as well as paths between the interface and the central
memory.
458
IBM SAN Implementation
Additionally, the SerialLink macro within the ASIC includes a serial data
loop-back function that can be enabled through a register in the corresponding
ASIC.
Diagnostics are provided to allow traffic to be circulated between two switch ports
that are connected with an external cable. This allows the diagnostics to verify
the integrity of the final stage of the SERDES interface, as well as the media
interface module.
Diagnostic coverage
The POST and diagnostic commands concentrate on the Fibre Channel ports
and verify switch functionality of the 2109 Model F16 switch.
4.10.4 Interoperability
In the topics that follow, we describe:
 Switch interoperability
 HBA interoperability
 Operating system support
Switch interoperability
The 2109 Model F16 switch supports both 1 Gb/s and 2 Gb/s transmit and
receive rates with auto-negotiation. The actual data signaling rate that is used on
a port is automatically sensed and is set to the rate that is supported by a device
or devices that are attached to the port. The 2109 Model F16 has been tested
and is compliant with the current FC standards. The 2109 Model F16 is
compatible with most current-generation switches N_ports, NL_ports, and
E_ports, as well as host adapters, Redundant Array of Independent Disks (RAID)
storage devices, hubs, and Fibre-SCSI bridge devices, including the 3534 and
2109 series of switches.
Implementation in existing environments
Because the 2109 Model F16 switch has a compatible 1 Gb/s auto-negotiated
signaling rate on each port, it can be used as a replacement for current 3534 and
2109 series switches. As newer technology is added to existing systems that
support 2 Gb/s signaling, the ports can accept these devices and interoperate
with existing 1 Gb/s devices. If the 2109 Model F16 is connected to a third-party
device but is unable to negotiate the signaling rate, the 2109 Model F16 allows
you to manually set the speed of each port through the management interfaces.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
459
Heterogeneous inter-switch operations
Fabric OS 3.0 supports interoperability for the following functions:
 Basic switch functions:
– Link initialization
– Principal switch selection
– Routing (FSPF)
 Basic services:
– Simple name service
– State change notification
– WWN zoning (typically referred to as soft zoning or name server zoning)
The following facilities are switch-based facilities and will continue to function on
any 2109 switch:





SNMP facilities
Simple QuickLoops with no zoning
Translative mode (private target support on fabrics)
Trunking (will only function between 2 IBM switches)
Enhanced performance metrics
The following facilities are IBM value-added facilities that would not be supported
in a multi-vendor fabric. Use of these facilities causes the Fabric to segment.
 QuickLoop zones
 QuickLoop Fabric assist mode
 Port, protocol, or LUN zoning
IBM is not aware of any areas of non-compliance with any ratified standards at
this time.
Host bus adapter interoperability
The 2109 Model F16 has been tested with the following host bus adapters
(HBAs) from the following vendors:
 Emulex
–
–
–
–
–
–
LP6000
LP7000
LP8000
LP850
LP952
LP9000
 QLogic
– QLA2100
– QLA2200
460
IBM SAN Implementation
 JNI
–
–
–
–
FC64-1063
FCI-1063
FCE-6410
FCE-6460
 Agilent
– HHBA-5100
– HHBA-5101
Operating system support
Fabric OS versions 2.x and 3.x have no specific OS dependencies. The Fabric
OS in the switches allows for any Fibre Channel compliant device to attach to the
switches as long as it conforms to the standards for device login, name service,
and related Fibre Channel features. Regardless of the operating environment,
proper interface to the fabric requires a Fibre Channel HBA with a
standards-compliant driver.
The operating systems versions listed in Table 4-2 have been tested (using HBA
devices and drivers supplied by QLogic, Emulex, JNI, and Agilent) for
interoperability:
Table 4-2 Compatible operating systems
OS
Version
AIX
4.3.3
NT
4.0
Windows 2000
Initial release
Solaris
2.5, 2.5.1, 2.6, 2.8, 7
HP-UX
10.0, 11.0
Linux RedHat
versions 6.2 and 7.0
PTX
Novel NetWare
NetWare 5.2
4.11 Installing the 2109-F16 Switch
Use this procedure to configure and connect the switch for use in a network and
fabric.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
461
The time required to accomplish this is approximately 15 minutes. The items
required are:
 2109-F16 installed and connected to a power source
 Workstation that has a terminal emulator application (such as HyperTerminal)
 Serial cable provided with the switch, for connecting the switch to the
workstation
 An unused IP address
 Ethernet cable for connecting the switch to the workstation or to a network
containing the workstation
 SWL or LWL SFPs and fiber optic cables as required.
4.11.1 Configuration instructions
The following instructions detail the steps necessary to configure the switch to
match your configuration:
1. Replace the factory IP address and related information with the IP information
provided by your network administrator.
a. Remove the shipping plug from the serial port and insert the serial cable
provided with the switch.
b. Connect the other end of the serial cable to an RS-232 serial port on the
workstation. If no RS-232 serial port is available on the workstation, the
adapter on the end of the serial cable can be removed to use the RJ-45
connector to create a serial connection.
c. Verify that the switch is on and POST is completed.
d. Disable any serial communication programs running on the workstation.
e. Open a terminal emulator application (such as HyperTerminal on a PC, or
TERM in a UNIX environment), and configure as follows:
•
In a Windows 95, 98, 2000, or NT environment adjust if necessary the
following parameters and values:
Bits per second: 9600
Databits: 8
Parity: None
Stop bits: 1
Flow control: None
•
In a UNIX environment, enter the following string at the prompt:
tip /dev/ttyb -9600
462
IBM SAN Implementation
f. From the terminal emulator application, log on to the switch through the
serial connection. The default administrative logon is admin and the
default password is password.
g. Enter the following at the prompt:
ipAddrSet
h. Enter the following information at the corresponding prompts, listed below:
Ethernet IP Address [10.77.77.77]:
Enter new ethernet IP address:
Ethernet Subnetmask [0.0.0.0]:
Enter new ethernet subnetmask:
Fibre Channel IP Address [none]:
Enter new Fibre Channel IP address if desired:
Fibre Channel Subnet Mask [none]:
Enter new Fibre Channel subnet mask if desired:
Gateway Address [172.17.1.1]:
Enter new gateway address:
Set IP address now? [y = set now, n = next reboot]:
Enter “y” to set now:
y
i. You can verify the address was correctly set by entering the following:
ipAddrShow
j. Once the IP address is verified as correct, remove the serial cable, and
replace the shipping plug in the serial port.
Note: The serial port is intended only for use during the initial setting of the
IP address and for service purposes. Using the serial port during normal
switch operation or for regular maintenance is not recommended.
k. Record the IP address for future reference.
2. Connect the switch to the workstation computer by ethernet cable (this can be
a direct connection or through a network).
a. Remove the shipping plug from the ethernet port.
b. Insert one end of an ethernet cable in the ethernet port.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
463
c. Connect the other end of the ethernet cable to the workstation or to an
ethernet network containing the workstation.
Note: The switch can now be accessed remotely, through Telnet or Web
Tools. As a result, it is important to ensure that the switch is not being
modified simultaneously from any other connections during the remaining
steps.
3. Log on to the switch by Telnet. The default administrative logon is admin and
the default password is password.
4. Modify the domain IDs if desired.
Note: The default domain ID is 1. If the domain ID is already in use when
the switch is connected to the fabric, the domain ID for the new switch is
automatically reset to a unique value. The domain IDs currently in use can
be determined by issuing the Telnet command fabricShow.
a. Disable the switch by entering the following:
switchDisable
b. Enter the following:
configure
c. Enter “y” after the “Fabric parameters” prompt:
Fabric parameters (yes, y, no, n): [no] y
d. Enter a unique domain ID (such as the domain ID used by the previous
switch, if still available).
Domain: (1..239) [1] 3
e. Complete the remaining prompts (or press CTRL+D to accept the
remaining settings without completing all the prompts).
f. Re-enable the switch by entering the following:
switchEnable
5. An optional step is to specify any custom status policies for the fabric.
a. Enter the following at the prompt:
switchStatusPolicySet
b. Specify the desired status policies. To completely deactivate the alarm for
a particular condition, enter “0” at the prompt for that condition.
464
IBM SAN Implementation
6. Add SFPs (small form factor pluggable media) and fiber optic cables to the
ports as required.
Note: The ports and cables used in trunking groups must meet specific
requirements.
a. Remove the shipping plug from the ports to be used.
b. Position the SFP so that the key (the tab near the cable-end of the SFP) is
on top, and insert the SFP into the port until it is firmly seated and the
latching mechanism makes a clicking sound. For specific instructions,
refer to the SFP manufacturer’s documentation.
Note: The SFP module is keyed so that it can only be correctly inserted
into the port. If the module does not slide in easily, try turning it over.
c. Connect the fiber optic cables to the SFPs as appropriate to the fabric
topology by positioning each cable so that the key (the ridge on one side
of the cable connector) is aligned with the slot in the SFP, then inserting
the cable into the SFP until it is firmly seated and the latching mechanism
makes a clicking sound.
Note: The cable is keyed so that it can only be correctly inserted into the
SFP. If the cable does not slide in easily, try turning it over.
7. Verify the correct operation of the 2109-F16.
a. Enter the following at the Telnet prompt:
switchShow
Note: This command provides information about the status of the switch
and the ports. Backing up the configuration after any initial configuration
changes and periodically thereafter is strongly recommended. This
ensures that a complete configuration is available if ever required for
uploading to a replacement switch.
4.12 Management
In the topics that follow we show some of the management functions that are
peculiar to the F16.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
465
Attention: We show the screen options that are available on the 2109-F16.
Typically they complement the features and functionality that we have already
covered in this chapter. For this reason, we will limit our examples to showing
the screen captures and describing the functions that can be performed.
4.13 Zoning
A zone is a group of fabric-connected devices arranged into a specified grouping.
Any device connected to a fabric can be included in one or more zones. Devices
within a zone possess an awareness of other devices within the same zone; they
are not aware of devices outside of their zone. Therefore, if zoning is enabled,
any device not in a zone is not able to communicate with any other device
outside of its own zone.
Zone members (ports, WWNs, or aliases) are grouped into a zone; in turn, zones
are grouped in a zone configuration (a collection of zones). Zones can overlap;
that is, a device can belong to more than one zone. A fabric can consist of
multiple zones.
A zone configuration can include both hard and soft zones (described below) and
there can be any number of zone configurations resident on a switch; however
only one configuration can be active, that is enabled, at a time. The number of
zones allowable is limited only by memory usage.
4.13.1 Zone types
The following list describes zone types:
 Port Level Zone — A zone containing members specified by switch ports
(domain ID, port number) only. Port level zoning is enforced by hardware in
the switch.
 WWN Zone — A zone containing members specified by device World Wide
Name (WWNs) only. WWN zones are hardware enforced in the switch.
 Mixed Zone — A zone containing some members specified by WWN and
some members specified by switch port. Mixed zones are software enforced
through the fabric name server.
Zones can be hard (hardware enforced), soft (advisory), or Broadcast zone. In a
hardware enforced zone, zone members can be specified by physical port
number, or through WWN, but not within the same zone. A software enforced
zone is created when a port member and WWN member are in the same zone.
466
IBM SAN Implementation
Hardware enforced zones
In a hardware enforced zone, all zone members can be specified as switch ports
or WWN; any number of ports or WWN’s in the fabric can be configured to the
zone. When a zone member is specified by port number or WWN, the individual
device port or WWN is included in the zone. Hard zones are not necessarily
position independent anymore. If WWN’s are used exclusively in a zone, new
devices can be attached without regard to physical location. In hard zones,
switch hardware ensures that there is no data transferred between unauthorized
zone members. However, devices can transfer data between ports within the
same zone. Consequently, hard zoning provides security.
Software enforced zones
In a software enforced zone, at least one zone member is specified by WWN and
one member is specified as a port. In this way, you have a mixed zone that is
software enforced. When a device logs in, it queries the name server for devices
within the fabric. If zoning is in effect, only the devices in the same zone(s) are
returned. Other devices are hidden from the name server query reply. When a
mixed zone of WWN’s and ports are specified all ports on the specified device
are included in the zone. Software enforced zones are created when a
combination of WWN’s and ports are used. When using software enforced
zones, the switch does not control data transfer and there is no guarantee of data
being transferred from unauthorized zone members. Use software zoning where
flexibility, and security is ensured by the cooperating hosts.
Broadcast zone
Only one broadcast zone can exist within a fabric. It is named “broadcast” and it
is used to specify those nodes that are to received broadcast traffic. This type of
one is a hardware enforced; the switch controls data transfer to a port.
4.13.2 Zone enforcement
Zones can be enforced in hardware through access control lists on the switch
ASIC (default) or by the fabric name server.
Hardware enforced zones
A zone enforced on the switch ASIC (most secure) containing members entirely
defined by switch ports or WWN, but not both within the single zone.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
467
Software enforced zones
A zone enforced through the fabric name server. Zones defined with members by
a mixture of switch ports and WWN’s is software enforced by the name server.
When zoning is disabled, devices can communicate without regard to zone
restrictions. When zoning is enabled, zoning is enforced throughout the fabric
and devices can communicate only within their zones.
4.13.3 Zone configurations
A switch can maintain any number of zone configurations; however, only one
zone configuration can be enabled, or enforced, at a time. Because multiple
configurations reside in the switch, you can switch from one configuration to
another as events dictate. For example, you can set up a pre-specified zone
configuration to be enabled at certain times of the day; or, in the event of a
disaster, you can quickly enable a defined configuration to implement your
disaster policy.
Zone configurations can be:
 Defined — This is the complete set of all zone objects that have been defined
in the fabric. When zone objects are defined, the information initially resides
in RAM; it must be saved to ensure that it is saved to flash memory and is not
lost during:
–
–
–
–
–
New zone configuration
Power down
Reboot
Fastboot
Power cycles
 Enabled — This is the zone configuration that is enabled (active). It resides in
RAM; it must be saved to ensure that it is not lost during power down. Any
changes replicate to all switches in the fabric when the configuration is
enabled or saved.
 Saved — This is the zone configuration that was last saved. It resides in flash
memory and it is persistent.
468
IBM SAN Implementation
4.13.4 Enabling a zone configuration
When a zone configuration is enabled, all zones within the configuration are
enabled. All devices within an enabled zone are visible to each other; however,
they cannot communicate outside their zone. Zones can overlap within a zone
configuration. When a zone configuration is enabled, the following happens:
 All aliases are expanded.
 Inconsistencies are checked. If inconsistencies are discovered, an error
occurs and the previous state of the fabric is preserved. (For example, if
zoning was disabled, it remains disabled; if an existing configuration was
enabled, it remains enabled.)
 Switch hardware is loaded with the zoning information.
 Zone members are loaded.
 Registered State Change Notifications (RSCNs) are generated.
4.14 Implementing zoning
When administering zoning, the following steps are recommended:




Define zone aliases to establish groupings.
Add zone members.
Place zones into one or more zone configurations.
Enable one of the zone configurations (only one can be enabled at a time).
There are three separate methods for adding members to a zone. Each method
corresponds to a zoning “mode”, and the combination of the methods
corresponds to an additional mode. Once a mode is selected, all operations on
zones must use the zoning object selected. Zoning operations must correspond
to that mode, and any zones, aliases, and configuration files which do not cannot
be selected.
4.14.1 Zone administration
To access zone administration, we must access the Zone Admin view. To do that,
we need to launch the Web browser.
We enter the switch name or IP address in the Location/Address field and press
Enter.
We show this in Figure 4-208.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
469
Figure 4-208 Initial Switch View
If we select Zone Admin, a prompt displays requesting User Name and
Password, as shown in Figure 4-209.
Figure 4-209 Network password entry scheme
470
IBM SAN Implementation
Enter the user name and the password and select OK.
The Zoning Scheme Selection menu displays as shown in Figure 4-210.
Figure 4-210 Zoning scheme selection
We describe the zoning schemes in the following topics and show the screens at
which you can apply zoning concepts that have previously been discussed in this
chapter.
Switch/Port Level Zoning
All alias, zoning and configuration file operations must be on ports. Aliases,
zones and configuration files which have objects other than ports cannot be
selected or operated on.
WWN Level Zoning
All aliases, zoning and configuration file operations must be on WWNs. Aliases,
zones and configuration files which have objects other than WWNs cannot be
selected or operated on.
AL_PA Level Zoning
All aliases, zoning and configuration file operations must be on AL_PA in a
QuickLoop. Aliases, zones and configuration files which have objects other than
AL_PAs in a QuickLoop cannot be selected or operated on.
Mixed Level Zoning
In this mode, any object can be selected to be a member of a zone, alias or
configuration file.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
471
4.14.2 Implementing Switch/Port Level Zoning
Upon selecting the Switch/Port Level Zoning button from the Zoning Selection
menu and selecting OK, the Switch/Port Level Zoning menu appears, with the
Port Alias tab displayed.
This is shown in Figure 4-211.
Figure 4-211 Zone admin initial view
Following is a list of the tabs provided in the Switch/Port Level Zoning menu:




472
Port Alias
Port Zone
QuickLoop
Port Config
IBM SAN Implementation
Port Alias tab
The Port Alias tab shows only Domain/Ports that are in the fabric. This tab is
used to configure zones that consist only of Domain/Ports and aliases that
contain only Domain/Ports.
The Port Alias tab is displayed as shown in Figure 4-212.
Figure 4-212 Port Alias administration
You will notice that we have created an alias called ITSO_Alias, but as yet there
are no members. Using the same principles for creating an alias that have been
employed throughout this chapter, and in previous iterations of zoning, we will
add some members to it.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
473
Table 4-3 describes the fields on the Port Alias tab.
Table 4-3 Port alias screen description:
Button
Function
Alias Name
Select an existing alias name to be modified.
Create Alias
Select to create a new alias. A new alias dialog displays. Enter a new alias name that is
unique. The new alias name cannot contain spaces.
Delete Alias
Select to delete the alias selected in the Alias Name field. Deleting an alias automatically
removes it from all zones.
Rename Alias
Select to rename the alias selected in the Alias Name field. A dialog displays in which
you can edit the alias name. Renaming an alias automatically renames it in all zones.
Member
Selection List
This field contains a list of potential alias members, including switches, ports, WWNs,
and QuickLoop AL_PAs.
Add Mem
Select to add the item selected in the Member Selection List to the Alias Members list.
You can add individual ports or an entire switch. If a switch is added, all ports on the
switch are added. To add a device WWN, select either a node WWN (folder icon) or port
WWN (blue circle icon) from the WWN sub-tree.
Remove Mem
Select to remove the member selected from the Alias Name Members Selection list.
Alias Members
This field lists the members of the alias selected in the Alias Name field. The name of
this list depends on the name of the selected alias. If no alias is selected, the name
displays as “Null Members”.
Search Mem
Select to search for a Switch name, WWN, Alias, Zone, QuickLoop, FA Zone in the
Member Selection List based on the type of objects displayed in that list.
Add Sw/Port
Select to add a switch/port combination that currently is not part of the fabric.
Ref Zone
Select to refresh the local zoning data base copied from the switch. This button
automatically flashes red/gray if the fabric zoning data is changed by another client.
A/D WWN
Select to add or delete a WWN to or from all the Aliases, Zones, FA Zones defined.
Rpl WWN
Select to replace a WWN with another one in all Aliases, Zones, FA Zones defined.
OK
Applies the changes to the switch and exits the frame.
Apply
Select to apply all changes made since the Zone Administration View was opened,
including changes made on other tabs in the view. Changes cannot be cancelled once
applied.
Close
Select to exit the frame without making any changes to the switch.
Clr All
Select to clear all Aliases, Zones, Configs, FA Zones locally on the switch.
474
IBM SAN Implementation
Port Zone tab
Use the Port Zone tab to specify which ports on a switch are to be in the
selected zone and to create and manage zones. A zone can have one or multiple
members, and can include switches, ports, WWNs, aliases, and QuickLoop
AL_PAs. The Port Zone tab is shown in Figure 4-213.
Figure 4-213 Port zone selection and display
Chapter 4. Implementing an IBM TotalStorage SAN Switch
475
Table 4-4 describes the fields on the Port Zone tab.
Table 4-4 Port zone screen description
Button
Function
Zone Name
To modify an existing zone, select a zone name.
Create Zone
Select to create a new zone. A dialog displays in which you can enter the name of the
new zone. All names must be unique and contain no spaces.
Delete Zone
Select to delete the zone selected in the Zone Name field. Deleting a zone automatically
removes it from all zone configurations.
Rename Zone
Select to edit the name of the zone selected in the Zone Name field. A dialog displays
in which you can edit the name of the zone.
Search Mem
Select to search the list of potential zone members.
Member
Selection List
A list of potential zone members, including switches, ports, WWNs, aliases, and
QuickLoop AL_PAs.
Add Mem
Select to add the member selected in the Member Selection List to the Zone Members
list. If an entire switch is selected, all ports on the switch are added to the zone. You can
also select individual ports. To add a device WWN, select either a node WWN (folder
icon) or port WWN (blue circle icon) from the WWN’s sub-tree. To add an alias to the
zone, select it from the Aliases sub-tree (the alias must already exist).
Remove Mem
Select to remove the selected member from the Zone name Members list. [Zone name]
Members
This field lists members of the zone selected in the Zone Name field. The name of this
list depends on the name of the selected zone. If no zone is selected, the name displays
as “null Members”.
Ref Zone
Click to refresh the local zoning data base copied from the switch. This button
automatically flashes red/gray if the fabric zoning data is changed by another client.
A/D WWN
Click to add or delete a WWN to or from all the Aliases, Zones, FA Zones defined.
Rpl WWN
Click to replace a WWN with another one in all Aliases, Zones, FA Zones defined.
OK
Applies the changes to the switch and exits the frame.
Apply
Click to apply all changes made since the Zone Administration View was opened,
including changes made on other tabs in the view. Changes cannot be cancelled once
they are applied.
Close
Click to exit the window without making any changes to the switch.
Clr All
Click to clear all Aliases, Zones, Configs, FA Zones locally on the switch.
476
IBM SAN Implementation
‘QuickLoop tab
A QuickLoop license is required to use this tab. You can use the QuickLoop tab
to create and manage QuickLoops if used in conjunction with zoning.
The QuickLoop tab is shown in Figure 4-214.
Figure 4-214 QuickLoop screen
Chapter 4. Implementing an IBM TotalStorage SAN Switch
477
You will notice that we have created a QuickLoop called ITSO_QLoop which has
two members which are both F16 switches.
Table 4-5 describes the fields on the QuickLoop tab.
Table 4-5 QuickLoop screen description
Field
Function
QuickLoop
Name
To modify an existing QuickLoop, select a QuickLoop name.
Create Qloop
Click to create a new QuickLoop. A dialog displays in which you can enter the name of
the new QuickLoop. All names must be unique and contain no spaces.
Delete Qloop
Click to delete the QuickLoop selected in the QuickLoop Name field. Deleting a
QuickLoop automatically removes it from all aliases, zones, and zone configurations,
including the associated AL_PAs.
Rename Qloop
Click to edit the name of the QuickLoop selected in the QuickLoop Name field. A dialog
displays in which you can edit the name of the QuickLoop.
Switch
Selection List
A list of the switches available to add to the QuickLoop.
Search Mem
Click to search for a Switch name, WWN, Alias, Zone, QuickLoop, FA Zone in the Switch
Selection List based on the type of objects displayed in that list.
Add Mem
Click to add the switch selected in the Switch Selection List to the QuickLoop Members
list.
Remove Mem
Click to remove the selected member from the QuickLoop Name list. [QuickLoop name]
Members
A list of the members of the QuickLoop currently selected in the QuickLoop Name field.
The name of this list depends on the name of the selected QuickLoop. If no QuickLoop
is selected, the name displays as “null Members”.
Apply
Click to apply all changes made since the Zone Administration View was opened,
including changes made on other tabs in the view. Changes cannot be cancelled once
they are applied.
Close
Click to cancel all changes since the changes were last applied and to exit Zone
Administration. Changes cannot be cancelled once they are applied.
Clr Al
Click to apply all changes made since the Zone Administration View was opened and to
exit the Zone Administration View.
478
IBM SAN Implementation
Port Config tab
Use the Port Config tab to create and manage zone configurations. Zone
configurations are used to enable or disable a group of zones at the same time.
The Port Config tab is shown in Figure 4-215.
Figure 4-215 Port Config screen
Table 4-6 contains a description of the fields and buttons that appear on the Port
Config tab.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
479
Table 4-6 Port Config screen description
Button
Function
Cfg Name
Select an existing configuration to modify.
Create Cfg
Click to create a new configuration. A dialog displays. Enter the name of the new
configuration. All names must be unique and contain no spaces.
Delete Cfg
Click to delete the configuration selected in the Cfg Name field.
Rename Cfg
Click to edit the name of the configuration selected in the Cfg Name field.
Zone/QLoop
Selection List
This field provides a list of the zones and QuickLoops available to add to the
configuration.
Add Mem
Click to add the switch selected in the Zone/QLoop Selection List to the Config Members
list.
Remove Mem
Click to remove the selected member from the Config Members list.
Search Mem
Click to search for a Switch name, WWN, Alias, Zone, QuickLoop, FA Zone in the
Member Selection List based on the type of objects displayed in that list.
Config
Members
The members of the configuration selected in the Cfg Name field. The name of this list
depends on the selection. Only one configuration can be enabled at a time; if none are
enabled, zoning is not active in the fabric.
Enable Config
Check to enable the configuration selected in the Cfg Name field, or uncheck to disable
it.
Disable Zoning
Check to disable zoning.
Analyze Config
Analyzes the configuration that is selected along with it’s member zones and aliases. A
zoning configuration error screen appears in the event of a conflict.
Refresh Fabric
Click to refresh the fabric view with the latest Domain/Port and WWN changes.
Ref Zone
Click to refresh the local zoning data base copied from the switch. This button
automatically flashes red/gray if the fabric zoning data is changed by another client.
A/D WWN
Click to add or delete a WWN to or from all the Aliases, Zones, FA Zones defined.
Rpl WWN
Click to replace a WWN with another one in all Aliases, Zones, FA Zones defined.
Apply
Click to apply all changes made since the Zone Administration View was opened,
including changes made on other tabs in the view. Changes cannot be cancelled once
they are applied.
Close
Click to exit the window without making any changes to the switch.
Ok
Applies the changes to the switch and exits the window.
Clr All
Click to clear all Aliases, Zones, Configs, FA Zones locally on the window.
480
IBM SAN Implementation
Zoning Configuration Analyze screen
The Zoning Configuration Analyze screen displays a summary of the saved
configuration and attempts to point out some of the zoning conflicts before
applying the changes to the switch. Some of the potential errors it might catch
are:
 Ports/WWNs/Devices that are part of the selected configuration, but not part
of the fabric.
 Zones with only a single member
The Analyze Config screen is shown in Figure 4-216.
Figure 4-216 Analyze config selection
Chapter 4. Implementing an IBM TotalStorage SAN Switch
481
4.14.3 WWN Level Zoning
With WWN Zoning, only World Wide Names are displayed on the tabs. This
window is used to configure aliases, zones, and configuration files. After
selecting the WWN Level Zoning button from the Zoning Selection menu and
clicking OK, the WWN Level Zoning menu displays.
We show how to select WWN Level Zoning in Figure 4-217.
Figure 4-217 Selecting WWN level zoning
Following is a list of the tabs provided in the WWN Level Zoning menu:




482
WWN Alias
WWN Zone
QuickLoop
WWN Config
IBM SAN Implementation
In Figure 4-218 we show the WWN Alias screen.
Figure 4-218 WWN Alias screen
Chapter 4. Implementing an IBM TotalStorage SAN Switch
483
Table 4-7 describes the fields on the WWN Alias tab.
Table 4-7 WWN Alias tab
Button
Function
Alias Name
Select an existing alias to modify.
Create Alias
Click to create a new alias. A dialog displays in which you can enter the name
of the new alias. All names must be unique and contain no spaces.
Delete Alias
Click to delete the alias selected in the Alias Name field. Deleting an alias
automatically removes it from all zones.
Rename Alias
Click to rename the alias selected in the Alias Name field. A dialog displays in
which you can edit the alias name. Renaming an alias automatically renames it
in all zones.
Member Selection List
A list of potential alias members, including switches, ports, WWNs, and
QuickLoop AL_PAs.
Alias Members
This field lists the members of the alias selected in the Alias Name field. The
name of this list depends on the name of the selected alias. If no alias is
selected, the name displays as “Null Members”.
Search Mem
Click to search for a Switch name, WWN, Alias, Zone, QuickLoop, FA Zone in
the Member Selection List based on the type of objects displayed in that list.
Add Mem
Click to add the item selected in the Member Selection List to the Alias Members
list. You can add individual ports or an entire switch. If a switch is added, all ports
on the switch are added. To add a device WWN, select either a node WWN
(folder icon) or port WWN (blue circle icon) from the WWN sub-tree.
Remove Mem
Click to remove the selected member from the Configuration name list.
Add WWN
Click to add a WWN that currently is not part of the Fabric.
Ref Zone
Click to refresh the local zoning data base copied from the switch. This button
automatically flashes red/gray if the fabric zoning data is changed by another
client.
A/D WWN
Click to add or delete a WWN to or from all the aliases, zones, FA zones defined.
Rpl WWN
Click to replace WWN with another one in all aliases, zones, FA Zones defined.
OK
Click to apply the changes to the switch and exit the window.
Apply
Click to apply the changes to the switch.
Close
Click to exit the window without making any changes to the switch.
Clr All
Click to clear all aliases, zones, configs, FA zones locally on the switch.
484
IBM SAN Implementation
WWN Zone tab
Use the WWN Zone tab to specify the members of the WWN Zone. In this
window, only switches and WWN are available to be selected as members of the
zone. The WWN Zone tab is shown in Figure 4-219.
Figure 4-219 WWN Zone screen
Chapter 4. Implementing an IBM TotalStorage SAN Switch
485
Table 4-8 describes the fields on the WWN Zone tab.
Table 4-8 WWN zone tab
Button
Function
Zone Name
Select an existing zone member to modify.
Create Zone
Click to create a new zone member.
Delete Zone
Click to delete a zone member.
Rename Zone
Click to rename a zone member.
Member Selection List
This field displays a list of potential zone members, including switches, ports,
WWNs, and QuickLoop AL_PAs.
Zone Members
This field lists the zone members selected in the Zone Name field. The name on
this list depends on the name of the selected zone member. If a name is not
selected, the name displays as “null Members”.
Search Mem
Click to search for a Switch name, WWN, Alias, Zone, QuickLoop, FA Zone in the
Member Selection List based on the type of objects displayed in that list.
Add Mem
Click to add a member from the Member Selection list into the Zone Member
contents.
Remove Mem
Click to remove a member from the Zone Member list.
Add WWN
Click to add a WWN that is not currently part of the Fabric.
Ref Zone
Click to refresh the local zoning data base copied from the switch. This button
automatically flashes red/gray if the fabric zoning data is changed by another
client.
A/D WWN
Click to add or delete a WWN to or from all the aliases, zones, FA zones defined
Rpl WWN
Click to replace WWN with another one in all aliases, zones, FA Zones defined.
OK
Click to apply the changes to the switch and exit the switch.
Apply
Click to apply the changes to the switch.
Close
Click to exit the window without making any changes to the switch.
Clr All
Click to clear all aliases, zones, configs, FA zones locally on the switch.
486
IBM SAN Implementation
QuickLoop tab
A QuickLoop license is required to use this tab. You can use the QuickLoop tab
to create and manage QuickLoops if used in conjunction with zoning.
The QuickLoop tab is shown in Figure 4-220.
Figure 4-220 QuickLoop screen
Chapter 4. Implementing an IBM TotalStorage SAN Switch
487
Table 4-9 describes the fields on the QuickLoop tab.
Table 4-9 QuickLoop tab
Button
Function
QuickLoop Name
Select an existing QuickLoop member to modify.
Create Qloop
Click to create a new QuickLoop member.
Delete Qloop
Click to delete a QuickLoop member.
Rename Qloop
Click to rename a QuickLoop member.
Switch Selection List
This field displays a list of potential QuickLoop members, including switches,
ports, WWNs, and QuickLoop AL_PAs.
QuickLoop Members
This field contains a list of the zone members selected in the QuickLoop Name
field. The name on this list depends on the name of the selected QuickLoop
member. If a name is not selected, the name displays as “null Members”.
Search Mem
Click to search for a Switch name, WWN, Alias, Zone, QuickLoop, FA Zone in the
Member Selection List based on the type of objects displayed in that list.
Add Mem
Click to add a member from the member selection list into the QuickLoop
member contents.
Remove Mem
Click to remove a member from the QuickLoop member list when selected.
Ref Zone
Click to refresh the local zoning data base copied from the switch. This button
automatically flashes red/gray if the fabric zoning data is changed by another
client.
A/D WWN
Click to add or delete a WWN to or from all the aliases, zones, FA zones defined.
Rpl WWN
Click to replace WWN with another one in all aliases, zones, FA Zones defined.
OK
Click to apply the changes to the switch and exit the switch.
Apply
Click to apply the changes to the switch.
Close
Click to exit the window without making any changes to the switch.
488
IBM SAN Implementation
WWN Config tab
Use the WWN Config tab to specify which zones comprise a WWN Zone
Configuration file. The WWN Config tab is shown in Figure 4-221.
Figure 4-221 WWN Config screen
Chapter 4. Implementing an IBM TotalStorage SAN Switch
489
Table 4-10 describes the fields on the WWN Config tab.
Table 4-10 WWN config tab
Button
Function
Cfg Name
Select to modify an existing WWN configuration name to be modified.
Create Cfg
Click to create a new WWN configuration.
Delete Cfg
Click to delete a WWN configuration.
Rename Cfg
Click to rename a WWN configuration.
Zone/QLoop
Selection List
This field displays a list of Zone and QuickLoop members available to add to the WWN
configuration.
Add Mem
Click to add a member from the config members list into the zone selection list.
Remove Mem
Click to remove a member from the zone selection list into the Config Member list.
Search Mem
Click to search for a Switch name, WWN, Alias, Zone, QLoop, FA Zone in the Zone
Selection List based on the type of objects displayed in that list.
Config
Members
This field displays a list of the members that belong to the WWN Configuration currently
selected in the Cfg Name field. The name of this list depends on the name of the WWN
configuration selected. If WWN configuration is not selected, the name displays as “null
Members”.
Analyze Config
Click to analyze the configuration that is selected along with its member zones and
aliases. A zoning error screen appears in the event of a conflict.
Enable Config
If this option is checked, and the Apply button clicked, the selected configuration would
be used for zoning the fabric.
Refresh Fabric
Click to refresh the fabric view with the latest Domain/Port and WWN changes.
Ref Zone
Click to refresh the local zoning data base copied from the switch. This button
automatically flashes red/gray if the fabric zoning data is changed by another client.
A/D WWN
Click to add/delete a WWN to/from all the Aliases, Zones, FA Zones defined.
Rpl WWN
Click to replace a WWN with another one in all Aliases, Zones, FA Zones defined.
OK
Applies the changes to the switch and exits the switch.
Apply
Click to apply all changes made including changes made on other tabs in the view.
Changes cannot be cancelled once they are applied.
Close
Click to exit the window without making any changes to the switch.
Clr All
Click to clear all Aliases, Zones, Configs, FA Zones locally on the switch.
490
IBM SAN Implementation
4.14.4 AL_PA Level Zoning
AL_PA Level Zoning is a replacement for QuickLoop Zoning. With AL_PA Level
Zoning, only members of a QuickLoop can be a member of the zone. Zone
members are specified through their AL_PA. Upon selecting the AL_PA Level
Zoning button from the Zoning Selection window and clicking OK, the AL_PA
Level Zoning menu with the AL_PA Device Alias tab displays.
We show how to select AL_PA Level Zoning in Figure 4-222.
Figure 4-222 AL_PA Level zoning select
Once this is selected, we are presented with the screen shown in Figure 4-223.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
491
Figure 4-223 Device Alias screen
Following is a list of the tabs provided in the AL_PA Level Zoning menu:




492
Device Alias
Device Zone
QuickLoop
Device Config
IBM SAN Implementation
Table 4-11 describes the fields on the AL_PA Device Alias tab.
Table 4-11 AL_PA device alias tab
Button
Function
Alias Name
Select an existing alias name to modify.
Create Alias
Click to create a new alias. A dialog displays. Enter the name of the new alias. All names
must be unique and contain no spaces.
Delete Alias
Click to delete the alias selected in the Alias Name field. Deleting an alias automatically
removes it from all zones.
Rename Alias
Click to rename the alias selected in the Alias Name field. A dialog displays in which you
can edit the alias name. Renaming an alias automatically renames it in all zones.
Member
Selection List
This field displays a list of potential alias members, including switches, ports, WWNs,
and QuickLoop AL_PAs.
Alias Members
This field lists the members of the alias selected in the Alias Name field. The name of
this list depends on the name of the selected alias. If no alias is selected, the name
displays as “Null Members”.
Search Mem
Click to search for a Switch name, WWN, Alias, Zone, QLoop, FA Zone in the Member
Selection List based on the type of objects displayed in that list.
Add Mem
Click to add a member from the Member Selection List to the Alias Members list.
Add Device
Click to allow adding a device that currently is not part of the Fabric.
Remove Mem
Click to remove the selected member from the Alias Members list.
Ref Zone
Click to refresh the local zoning data base copied from the switch. This button
automatically flashes red/gray if the fabric zoning data is changed by another client.
A/D WWN
Click to add or delete a WWN to or from all the aliases, zones, FA zones defined.
Rpl WWN
Click to replace WWN with another one in all aliases, zones, FA Zones defined.
OK
Click to apply the changes to the switch and exit the switch.
Apply
Click to apply the changes to the switch.
Close
Click to exit the window without making any changes to the switch.
Clr All
Click to clear all aliases, zones, configs, FA zones locally on the switch.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
493
AL_PA Device Zone tab
Use the AL_PA Device Zone tab to select members of a device zone. Members
are specified by their AL_PA. The AL_PA Device Zone tab is shown in
Figure 4-224.
Figure 4-224 AL_PA device zone screen
494
IBM SAN Implementation
Table 4-12 describes the fields on the AL_PA Device Zone tab.
Table 4-12 AL_PA device zone tab
Button
Function
Zone Name
Select an existing zone member to modify.
Create Zone
Click to create a new zone member.
Delete Zone
Click to delete a zone member.
Rename Zone
Click to rename a zone member.
Member
Selection List
This field displays a list of potential zone members, including switches, ports, WWNs,
and QuickLoop AL_PAs.
Zone Members
This field lists the zone members selected in the Zone Name field. The name on this list
depends on the name of the selected zone member. If a name is not selected, the name
displays as “null Members”.
Search Mem
Click to search for a Switch name, WWN, Alias, Zone, QuickLoop, FA Zone in the
Member Selection List based on the type of objects displayed in that list.
Add Device
Click to add a device that currently is not part of the Fabric.
Add Mem
Click to add a member from the member selection list into the Zone Members list.
Remove Mem
Click to remove a member from the Zone Member List when selected.
Ref Zone
Click to refresh the local zoning data base copied from the switch. This button
automatically flashes red/gray if the fabric zoning data is changed by another client.
A/D WWN
Click to add or delete a WWN to or from all the aliases, zones, FA zones defined
Rpl WWN
Click to replace WWN with another one in all aliases, zones, FA Zones defined.
OK
Click to apply the changes to the switch and exit the switch.
Apply
Click to apply the changes to the switch.
Close
Click to exit the window without making any changes to the switch.
Clr All
Click to clear all aliases, zones, configs, FA zones locally on the switch.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
495
QuickLoop tab
A QuickLoop license is required to use this tab. Use the QuickLoop tab to create
and manage QuickLoops.
The QuickLoop tab is shown in Figure 4-225.
Figure 4-225 QuickLoop config screen
496
IBM SAN Implementation
Table 4-13 describes the fields on the QuickLoop tab.
Table 4-13 QuickLoop tab
Button
Function
QuickLoop
Name
Select an existing QuickLoop member name to modify.
Create Qloop
Click to create a new QuickLoop member.
Delete Qloop
Click to delete a QuickLoop member.
Rename Qloop
Click to rename a QuickLoop member.
Switch
Selection List
This field displays a list of potential QuickLoop members, including switches, ports,
WWNs, and QuickLoop AL_PAs.
QuickLoop
Members
This field displays a list of the zone members selected in the QuickLoop Name field. The
name on this list depends on the name of the selected QuickLoop member. If a name is
not selected, the name displays as “null Members”.
Search Mem
Click to search for a Switch name, WWN, Alias, Zone, QuickLoop, FA Zone in the
Member Selection List based on the type of objects displayed in that list.
Add Mem
Click to add a member from the member selection list into the QuickLoop member
contents.
Remove Mem
Click to remove a member from the QuickLoop member list when selected.
Ref Zone
Click to refresh the local zoning data base copied from the switch. This button
automatically flashes red/gray if the fabric zoning data is changed by another client.
A/D WWN
Click to add or delete a WWN to or from all the aliases, zones, FA zones defined.
Rpl WWN
Click to replace WWN with another one in all aliases, zones, FA Zones defined.
OK
Click to apply the changes to the switch and exit the switch.
Apply
Click to apply the changes to the switch.
Close
Click to exit the window without making any changes to the switch.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
497
AL_PA Device Config tab
Use the AL_PA Device Config tab to specify the Device Zone that belongs to
the Device Zone Configuration file. All members of this configuration file must be
Zones consisting entirely of AL_PAs in a QuickLoop.
The AL_PA Device Config tab is shown in Figure 4-226.
Figure 4-226 AL_PA device config scree
Table 4-14 describes the fields on the AL_PA device config screen.
498
IBM SAN Implementation
Table 4-14 AL_PA device config tab
Button
Function
Cfg Name
Select an existing AL_PA Configuration name to modify.
Create Cfg
Click to create a new AL_PA configuration.
Delete Cfg
Click to delete a AL_PA configuration.
Rename Cfg
Click to rename a AL_PA configuration.
Zone/QLoop
Selection List
A list of Zone/QuickLoop members available to add to the AL_PA configuration.
Add Mem
Click to add a member from the Zone Selection List into the Configuration Member List.
Remove Mem
Click to remove a member from the Zone Selection List into the Configuration Member
List.
Search Mem
Click to search for a Switch name, WWN, Alias, Zone, QLoop, FA Zone in the Member
Selection List based on the type of objects displayed in that list.
AL_PA Config
Members
name
This field displays a list of the members that belong to the AL_PA Configuration currently
selected in the Cfg Name field. The name of this list depends on the name of the AL_PA
configuration selected. If a AL_PA configuration is not selected, the name displays as
“null Members”.
Analyze Config
Click to analyze the configuration that is selected along with it’s member zones and
aliases, and comes up with a zoning error screen in the event of a conflict.
Enable Config
Select this option and click the Apply button to enable the selected config for zoning the
fabric.
Disable Zoning
Select this option and click the Apply button to disable the selected config for zoning the
fabric.
Refresh Fabric
Click to refresh the fabric view with the latest Domain/Port and WWN changes.
Ref Zone
Click to refresh the local zoning data base copied from the switch. This button
automatically flashes red/gray if the fabric zoning data is changed by another client.
A/D WWN
Click to add or delete a WWN to or from all the Aliases, Zones, FA Zones defined.
Rpl WWN
Click to replace a WWN with another one in all Aliases, Zones, FA Zones defined.
OK
Applies the changes to the switch and exits the switch.
Apply
Click to apply all changes made including changes made on other tabs in the view.
Changes cannot be cancelled once they are applied.
Close
Click to exit the window without making any changes to the switch.
Clr All
Click to clear all Aliases, Zones, Configs, FA Zones locally on the switch.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
499
4.14.5 Mixed Level Zoning
Mixed Level Zoning is provided for backward compatibility of pre-3.0 zones.
The mixed level zoning selection window is shown in Figure 4-227.
Figure 4-227 Mixed level zoning selection window
After selecting the Mixed Level Zoning button from the Zoning Selection
window and clicking OK, the Mixed Level Zoning window with the Alias tab is
displayed.
The following is a list of the tabs provided in the Mixed Level Zoning menu:




500
Alias
Zone
QuickLoop
Config
IBM SAN Implementation
Alias tab
Use the Alias tab to set up mixed aliases. The Alias tab is shown in
Figure 4-228.
Figure 4-228 Mixed zoning alias screen
Chapter 4. Implementing an IBM TotalStorage SAN Switch
501
Table 4-15 describes the fields on the Alias tab.
Table 4-15 Alias tab
Button
Function
Alias Name
Select an existing alias to modify.
Create Alias
Click to create a new alias. A dialog displays. Enter the name of the new alias. All names
must be unique and contain no spaces.
Delete Alias
Click to delete the alias selected in the Alias Name field. Deleting an alias automatically
removes it from all zones.
Rename Alias
Click to rename the alias selected in the Alias Name field. A dialog displays in which you
can edit the alias name. Renaming an alias automatically renames it in all zones.
Member
Selection List
This field displays a of potential alias members, including switches, ports, WWNs, and
QuickLoop AL_PAs.
Alias Members
This field lists the members of the alias selected in the Alias Name field. The name of
this list depends on the name of the selected alias. If no alias is selected, the name
displays as “Null Members”.
Search Mem
Click to search for a Switch name, WWN, Alias, Zone, QLoop, FA Zone in the Member
Selection List based on the type of objects displayed in that list.
Add Mem
Click to add a member from the Member Selection List to the Alias Members list.
Add Other
Click to add a switch/port, WWN or a device that currently is not part of the fabric.
Remove Mem
Click to remove the selected member from the Alias Members list.
Ref Zone
Click to refresh the local zoning data base copied from the switch. This button
automatically flashes red/gray if the fabric zoning data is changed by another client.
A/D WWN
Click to add or delete a WWN to or from all the aliases, zones, FA zones defined
Rpl WWN
Click to replace WWN with another one in all aliases, zones, FA Zones defined.
OK
Click to apply the changes to the switch and exit the window.
Apply
Click to apply the changes to the switch.
Close
Click to exit the window without making any changes to the switch.
Clr All
Click to clear all aliases, zones, configs, FA zones locally on the switch.
502
IBM SAN Implementation
Zone tab
Use the Zone tab to specify the member of a mixed zone. Mixed zone members
can be AL_PAs, ports and WWNs.
The Zone tab is shown in Figure 4-229.
Figure 4-229 Mixed zoning zone screen
Chapter 4. Implementing an IBM TotalStorage SAN Switch
503
Table 4-16 describes the fields on the Zone tab.
Table 4-16 Zone tab
Button
Function
Zone Name
Select an existing zone member to modify.
Create Zone
Click to create a new zone member.
Delete Zone
Click to delete a zone member.
Rename Zone
Click to rename a zone member.
Member Selection List
This field displays a list of potential zone members, including switches, ports,
WWNs, and QuickLoop AL_PAs.
Zone Members
This field displays a list of the zone members selected in the Zone Name field.
The name on this list depends on the name of the selected zone member. If a
name is not selected, the name displays as “null Members”.
Search Mem
Click to search for a Switch name, WWN, Alias, Zone, QuickLoop, FA Zone in
the Member Selection List based on the type of objects displayed in that list.
Add Mem
Click to add a member from the Member Selection List into the Zone Member
contents.
Remove Mem
Click to remove a member from the zone member list when selected.
Add Other
Click to add a switch/port, WWN or a device that currently is not part of the
Fabric.
Ref Zone
Click to refresh the local zoning data base copied from the switch. This button
automatically flashes red/gray if the fabric zoning data is changed by another
client.
A/D WWN
Click to add or delete a WWN to or from all the aliases, zones, FA zones defined.
Rpl WWN
Click to replace WWN with another one in all aliases, zones, FA Zones defined.
OK
Click to apply the changes to the switch and exit the switch.
Apply
Click to apply the changes to the switch.
Close
Click to exit the window without making any changes to the switch.
Clr All
Click to clear all aliases, zones, configs, FA zones locally on the switch.
504
IBM SAN Implementation
QuickLoop tab
A QuickLoop license is required to use this tab. You can use the QuickLoop tab
to create and manage QuickLoops if used in conjunction with zoning.
The QuickLoop tab is shown in Figure 4-230.
Figure 4-230 Mixed level QuickLoop screen
Chapter 4. Implementing an IBM TotalStorage SAN Switch
505
Table 4-17 describes the fields on the QuickLoop tab.
Table 4-17 QuickLoop tab
Button
Function
QuickLoop Name
Select an existing QuickLoop member to modify.
Create Qloop
Click to create a new QuickLoop member.
Delete Qloop
Click to delete a QuickLoop member.
Rename Qloop
Click to rename a QuickLoop member.
Switch Selection List
This field displays a list of potential QuickLoop members, including switches,
ports, WWNs, and QuickLoop AL_PAs.
QuickLoop Members
This field contains a list of the zone members selected in the QuickLoop Name
field. The name on this list depends on the name of the selected QuickLoop
member. If a name is not selected, the name displays as “null Members”.
Search Mem
Click to search for a Switch name, WWN, Alias, Zone, QuickLoop, FA Zone in the
Member Selection List based on the type of objects displayed in that list.
Add Mem
Click to add a member from the member selection list into the QuickLoop member
contents.
Remove Mem
Click to remove a member from the QuickLoop member list when selected.
Ref Zone
Click to refresh the local zoning data base copied from the switch. This button
automatically flashes red/gray if the fabric zoning data is changed by another
client.
A/D WWN
Click to add or delete a WWN to or from all the aliases, zones, FA zones defined.
Rpl WWN
Click to replace WWN with another one in all aliases, zones, FA Zones defined.
OK
Click to apply the changes to the switch and exit the switch.
Apply
Click to apply the changes to the switch.
Close
Click to exit the window without making any changes to the switch.
506
IBM SAN Implementation
Config tab
Use the Config tab to save and enable a Mixed Zone Configuration File. A Mixed
Zone Configuration file can contain any type of zoneable objects, ports, WWNs
and AL_PAs.
The Config tab is shown in Figure 4-231.
Figure 4-231 Mixed level config screen
Chapter 4. Implementing an IBM TotalStorage SAN Switch
507
Table 4-18 describes the fields on the Config tab.
Table 4-18 Config tab
Button
Function
Cfg Name
Select the existing Cfg name to be modified.
Create Cfg
Click to create a new configuration.
Delete Cfg
Click to delete a configuration.
Rename Cfg
Click to rename a configuration.
Zone/QLoop
Selection List
A list of Zone/QuickLoop members available to add to the configuration.
Add Mem
Click to add a member from the Zone Selection list into the Config Member list.
Remove Mem
Click to remove a member from the Config Members list into the Zone Selection list.
Search Mem
Click to search for a Switch name, WWN, Alias, Zone, QLoop, FA Zone in the Member
Selection List based on the type of objects displayed in that list.
Config
Members
A list of the members that belong to the Configuration currently selected in the Cfg Name
field. The name of this list depends on the name of the configuration selected. If a
configuration is not selected, the name displays as “null Members”.
Analyze Config
Click to analyze the configuration that is selected along with its member zones and
aliases, and comes up with a zoning error screen in the event of a conflict.
Refresh Fabric
Click to refresh the fabric view with the latest Domain/Port and WWN changes.
Enable Config
If this option is checked, and the Apply button clicked, the selected config would be used
for zoning the fabric.
Disable Zoning
Select this option and click the Apply button to disable the selected zoning
configuration.
Ref Zone
Click to reload the local zoning data base copied from the switch. This button
automatically flashes red/gray if the fabric zoning data is changed by another client.
A/D WWN
Click to add or delete a WWN to or from all the Aliases, Zones, FA Zones defined.
Rpl WWN
Click to replace a WWN with another one in all Aliases, Zones, FA Zones defined.
OK
Applies the changes to the switch and exits the window.
Apply
Click to apply all changes made including changes made on other tabs in the view.
Changes cannot be cancelled once they are applied.
Close
Click to exit the window without making any changes to the switch.
Clr All
Select to clear all Aliases, Zones, Configs, FA Zones locally on the window.
508
IBM SAN Implementation
4.15 ISL Trunking
ISL Trunking is shipped as standard with the 2109-F16 switches with Fabric OS
version 3.0. ISL Trunking is managed using Telnet commands or the Web
interface.
The ISL Trunking feature allows up to four Interswitch Links (ISLs) to merge
logically into a single link. An ISL is a connection between two switches through
an Expansion Port (E_Port).
When using ISL Trunking to aggregate bandwidth of up to four ports, the speed
of the ISLs between switches in a fabric is quadrupled. For example, at 2 Gb/s
speeds, trunking delivers ISL throughput of up to 8 Gb/Sec.
ISL Trunking supports high-bandwidth, large-scale Storage Area Networks
(SANs) which include core switches. The primary task of ISL Trunking is to route
data and edge switches that aggregate connections to servers and storage. ISL
Trunking simplifies network design and reduces the cost of storage management
by optimizing bandwidth utilization and enabling load balancing of traffic at the
frame-level.
Advantages of ISL Trunking
The ISL Trunking feature has many advantages, for example, it ensures optimal
ISL bandwidth use across trunked links, while preserving in-order delivery. ISL
Trunking uses frame-level load balancing, as opposed to Fibre Channel Shortest
Path First (FSPF), to achieve faster fabric convergence, as well as higher
availability in the fabric.
Routing without the ISL Trunking Feature
Prior to the implementation of the ISL Trunking feature, device-level load sharing
was done through Fibre Channel networks that created ISLs and operated using
the FSPF routing protocol. The FSPF routing protocol established and
communicated the shortest paths for data to be carried from source to
destination.
Although FSPF compliant switches ensure fixed routing paths, and guarantee
that all frames are delivered in order, congestion occurs if the aggregation of the
stream exceeds the capacity of one of the ISLs in the path. For example, four
untrunked ISLs have a maximum capacity of 2Gb/Sec., which provides for a
maximum throughput of 8Gb/Sec. Due to traffic that is not trunked, the
throughput of the four ISLs is:
2Gb/Sec + 1.5Gb/Sec +.5G + 1Gb/Sec, which gives a 5Gb/Sec. total.
This is because two 2Gb/Sec data streams are competing for the same path.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
509
Routing with the ISL Trunking Feature
With ISL Trunking four ISLs provide 8Gb/Sec of total throughput. With the
implementation of ISL Trunking, bandwidth is shared across the trunked ISLs,
permitting a total throughput of:
2Gb/ Sec. + 1.5Gb/Sec + 0.5Gb/Sec + 1 Gb/Sec + 2Gb/Sec, for a total
7Gb/Sec.in this case.
Because the trunk aggregates the four individual paths into one and preserves
in-order deliver of frames, the total throughput is increased compared to a
non-trunked group of ISLs.
4.15.1 Trunking groups, ports, and masters
ISL Trunking dynamically performs load balancing, at the frame level, across a
set of available links between two adjacent switches to establish a trunking
group. Ports that belong to a trunking group are called trunking ports. One port is
used to assign traffic for the group, and is referred to as the trunking master.
Trunking groups
A trunking group is identified by the trunking master that represents the entire
group. The rest of the group members are referred to as slave links that help the
trunking master direct traffic across ISLs, allowing efficient and balanced in-order
communication.
Trunking ports
Trunking ports in a trunking group should meet the following criteria:
 Port must be configured as E_Ports.
 Ports must reside in the same contiguous four-port groups. For example: 0-3,
4-7, 8-11, 12-15.
 Ports must run at the 2G speed.
 The cable difference between all ports in a trunking group must be less than
500 meters.
Trunking masters
The trunking master implicitly defines the trunking group. All ports with the same
master are considered to be part of the same group. Each trunking group
includes a single trunking master and several trunking slave links. The first ISL
found in any trunking group is assigned to be the trunking master, also known as
the principle ISL. After the trunking group is fully established, all data packets
intended for transmission across the trunk are dynamically distributed at frame
level across the ISLs in the trunking group, while preserving in-order delivery.
510
IBM SAN Implementation
4.15.2 Installing ISL Trunking
Installing the ISL Trunking feature involves activating a license for each switch
you want to enable for trunking. A license may have been installed in the switch
at the factory. If not, contact your switch supplier to obtain a license key.
The ISL Trunking feature requires a 2109-F16 switch with Fabric OS Version 3.0.
A Trunking license can be installed using either Telnet or the Web interface.
Installing Brocade ISL Trunking through Telnet
To use Telnet to log on to the ISL Trunking feature, perform the following:
1. From a command prompt screen, use the Telnet command to log onto the
switch using an account that has administrative privileges. For example:
Z:\/telnet account
where account is replaced with assigned account number.
2. If you want to determine whether an ISL Trunking license is already installed
on the switch, type licenseShow on the Telnet command line.
A list displays of all the licenses currently installed on the switch. For
example:
admin> licenseShow
1A1AaAaaaAAAA1a:
Release v3.0
Web license
Zoning license
SES license
Trunking license
If the Trunking license is not included in the list, or is incorrect, continue with
the following.
3. Enter the following on the command line:
licenseAdd “key”
where “key” is the license key provided to you, enclosed in double quotes.
The license key is case sensitive and must be entered exactly as given.
4. Verify the license was added by entering the following on the command line:
licenseShow
If the ISL Trunking license is listed, the feature is installed and immediately
available.
If the license is not listed, repeat step three.
5. Disable the switch by entering the following command:
switchdisable
Chapter 4. Implementing an IBM TotalStorage SAN Switch
511
6. Enable the switch by entering the following command:
switchenable
Installing ISL Trunking through Web tools Tools
To enter the ISL Trunking license key using the Web interface, perform the
following:
1. Launch the Web browser, enter the switch name or IP address in the
Location/Address field, and press Enter. The Web interface launches,
displaying the Fabric View.
2. Click the Admin button on the relevant switch panel and the logon window
displays.
3. Enter a logon name and password with administrative privileges and press
Enter and the Administration View displays.
4. Select the License Admin tab, enter the license key in the License Key field,
and click Add. The Trunking feature is available as soon as the license key is
added.
5. Select Switch Settings tab, and disable the switch by selecting Disable.
6. Enable the switch by selecting Switch Enable.
4.15.3 Administering ISL Trunking
The ISL Trunking feature is managed by performing some administration tasks.
These tasks include:




Enabling or disabling the trunking
Enabling and disabling ports of a switch
Setting the speed of a port
Debugging a trunking link failure
The ISL Trunking feature is administered using Telnet commands, or through the
Web interface.
512
IBM SAN Implementation
ISL Trunking Telnet commands
Table 4-19 describes the Telnet commands used to manage the Brocade ISL
Trunking feature.
Table 4-19 ISL Telnet commands
Command
Description
Example
portCfgTrunkport
Use this command to
configure a port to be
enabled or disabled for
trunking.
To enable port 5 for ISL TRUNKING, enter:
portCfgTrunkport 5, 1
To disable port 5 for ISL TRUNKING, enter:
portCfgTrunkport 5, 0
switchCfgTrunk
Use this command to enable
or disable trunking on all
ports of a switch.
To enable trunking on all ports of a switch, enter:
switchCfgTrunk 1
To disable ISL Trunking on all ports of a switch,
enter:
switchCfgTrunk 0
trunkDebug
Use this command to debug
a trunk link failure.
To debug ports 1 and 2, enter:
trunkDebug 1, 2
trunkshow
Use this command to display
ISL Trunking membership
information.
To display ISL Trunking membership information
about users, enter:
trunkshow
4.16 Performance Monitor
The Performance Monitor performs the following functions:
 Graphically displays throughput (megabytes per second) for each port and for
the entire switch. Port throughput is the number of bytes that are received at a
port plus the number of bytes that are transmitted. Switch throughput is the
sum of the throughput for all the ports. The Performance Monitor also allows
the graphing of traffic based on the Source ID and the Destination ID
hardware-filtering mechanism.
 Provides the ability to change the configuration of a switch or port visually by
using the graphics.
Perform the following steps to access the Performance Monitor:
1. Launch the Web browser.
2. Type the switch name or IP address in the Location/Address field and press
Enter.
3. The TotalStorage Specialist launches, displaying the Fabric view.
4. Click the Switch icon, and the switch will display as shown in Figure 4-232.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
513
Figure 4-232 Switch management screen
The Performance Monitor contains a collection of graphs on the display panel, or
canvas. The graphs are sized based on the number of graphs loaded on the
canvas. Double-clicking a graph expands the graph to the size of the display.
Features
These are some of the features available in the Performance Monitor:
 An existing report can be selected from a list of reports that are predefined.
In some cases, you can supply the object to be monitored and graphed
(such as port number, SID/DID pair, AL_PA, or switch domain number).
 Graphs are displayed on a canvas, which can hold a maximum of eight
graphs simultaneously. An individual graph can be maximized to occupy the
entire canvas. The size of the graphs on the canvas is determined by the
number of graphs being displayed. The window does not need to be scrolled
to view all the selected graphs.
 The collection of graphs in the canvas can be stored for later retrieval on the
switch. Up to 20 individual canvases can be saved. Each canvas is saved
with its name, a brief description, and the graphs that comprise the canvas.
 Any graph can be magnified and detached from the main canvas or removed
from the main canvas using a pop-up menu. You can display the pop-up
menu by pointing the mouse at any graph on the main canvas and clicking the
right mouse button. To reattach the detached (Zoomed Out) graph back to the
main canvas, you can point the mouse to the detached graph, click the right
button and select Zoom In.
Each graph can be printed.
514
IBM SAN Implementation
Graph types
There are three graph types used to display port and switch information:
 Vertical
 Horizontal
 Line chart
All graphs are real-time. Each graph is updated either every 5 seconds or every
15 seconds.
4.16.1 Performance Monitor menus
The Performance Monitor is made up of two main menus:
 Performance monitor actions menu
 Performance graphs menu
Performance Monitor Actions menu
The Actions menu of the Performance Monitor feature is made up of the
following sub-menus:




Display canvas configurations
Save current canvas configuration
Resource usage display
Print all graphs
We show the Actions menu in Figure 4-233.
Figure 4-233 Actions menu displaying choices
Chapter 4. Implementing an IBM TotalStorage SAN Switch
515
We show the Performance Graphs menu in Figure 4-234.
Figure 4-234 Performance graphs menu showing choices
We have selected all the options available in basic monitoring and have created
a canvas that includes them. This is shown in Figure 4-235.
Figure 4-235 Basic monitoring full functions
516
IBM SAN Implementation
We can select the save current canvas configuration and give it a name and
description as shown in Figure 4-236.
Figure 4-236 Canvas save screen
We can show the display resource usage by selecting it as shown in
Figure 4-237.
Figure 4-237 Display resource usage screen
We are then presented with the screen shown in Figure 4-238.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
517
Figure 4-238 Display resource screen output
Display Canvas Configurations menu
The Display Canvas Configurations menu allows you to view all the canvas
configurations that have been saved on the switch.
We show how to access the Display Canvas Configuration menu in Figure 4-20.
518
IBM SAN Implementation
Table 4-20 Canvas configuration list
If we click the Load Canvas button after we have highlighted the canvases that
we wish to display, we will load that canvas.
Figure 4-21 shows the screen that is displayed after we have selected the edit
canvas option.
Table 4-21 Canvas edit option
Chapter 4. Implementing an IBM TotalStorage SAN Switch
519
4.17 Advanced Performance Monitoring
Performance Monitoring is an optionally licensed product that runs on 2109
Model F16 series switches. It provides SAN performance management through
an end-to-end monitoring system that enables you to:
 Increase end-to-end visibility into the fabric
 Enable more accurate reporting for service level agreements and charged
access applications
 Improve performance tuning and resource optimization
 Shorten troubleshooting time
 Promote better capacity planning
 Simplify administration and setup
 Increase productivity with pre formatted and customizable screens and
reports
The Performance Monitoring product:







Monitors transaction performance from its source to its destination
Provides device performance measurements by port, AL_PA, and LUN
Reports CRC error measurement statistics
Measures trunking performance
Compares IP versus SCSI traffic on each port
Includes a wide range of predefined reports
Allows you to create customized user-defined reports
You can administer Performance Monitoring through either Telnet commands or
TotalStorage Specialist. If you use TotalStorage Specialist, a TotalStorage
Specialist license must also be installed on the switch.
4.17.1 Performance Monitoring with Telnet commands
Three different types of Performance Monitoring can be done using Telnet
commands:
 AL_PA monitoring
 End-to-end monitoring
 Filter-based monitoring
AL_PA monitoring
AL_PA monitoring provides information about the number of CRC errors
occurring in Fibre Channel frames in a loop configuration. AL_PA monitoring
collects CRC error counts for each AL_PA that is attached to a specific port.
520
IBM SAN Implementation
End-to-end monitoring
End-to-end monitoring provides information about transaction performance
between the transactions source (SID) and destination (DID) on a fabric or a
loop. Up to 16 SID-DID pairs per port can be specified. For each of the SID-DID
pairs, the following information is available:
 CRC error count on the frames for the SID-DID pair
 Fibre-channel words transmitted from the port for the SID-DID pair
 Fibre-channel words received by the port for the SID-DID pair
Filter-based monitoring
Filter-based monitoring provides information about a filter’s hit count. Any
parameter in the first 64 bytes of the Fibre Channel frame can be measured. The
counter increases each time a frame is filtered through the corresponding port.
Examples of port filter statistics that can be measured are:
 SCSI read, write, or read/write commands
 CRC error statistics (port and AL_PA)
 IP versus SCSI traffic comparison
4.17.2 Performance Monitoring with TotalStorage Specialist
You can monitor performance using the TotalStorage Specialist if a TotalStorage
Specialist license is also installed. The enhanced Performance Monitoring
features in TotalStorage Specialist provide:






Predefined performance graphs for AL_PA, end-to-end, and filter-based
User-defined graphs
Performance canvas for application-level or fabric-level views
Configuration editor (save, copy, edit, and remove multiple configurations)
Persistent graphs across restarts (saves parameter data across restarts)
Print capabilities
Predefined performance graphs
Predefined graphs are provided to simplify performance monitoring. A wide
range of end-to-end fabric, LUN, device, and port metrics are included.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
521
Figure 4-239 shows the predefined performance graphs available.
Figure 4-239 Advanced monitoring options
4.17.3 Installing Performance Monitoring
To enable Performance Monitoring, you must install a license on each switch that
will use this feature. Contact your switch supplier to obtain a license key.
Note: A license might have already been installed on the switch at the factory.
You can install a Performance Monitoring license through Telnet commands or
using TotalStorage Specialist.
Note: Version 3.0 of Performance Monitoring requires a 2109 Model F16
series switch with Fabric OS 3.0 or later installed.
You can install a Performance Monitoring license by two methods:
 Installing through Telnet
 Installing through TotalStorage Specialist
522
IBM SAN Implementation
Installing through Telnet
Perform the following steps to install Performance Monitoring through Telnet:
1. Log into the switch through Telnet using an account that has administrative
privileges.
2. To determine whether a Performance Monitoring license is already installed
on the switch, type licenseShow on the Telnet command line. A list of all the
licenses that are currently installed on the switch displays. For example:
admin>licenseShow
1A1AaAaaaAAA1a:
Release v3.0
Zoning license
SES license
QuickLoop license
If the Performance Monitoring license is not included in the list, continue with
the following steps.
3. Type the following on the command line:
licenseAdd "key"
where key is the license key exactly as provided by your switch supplier,
surrounded by double quotation marks. The license key is case-sensitive and
must be entered exactly as given.
4. Verify that the license key was successfully added by typing licenseShow on
the command line.
A list of all the licenses displays. For example:
admin>licenseShow
1A1AaAaaaAAA1a:
Release v3.0
Zoning license
SES license
QuickLoop license
Performance Monitor license
The Performance Monitoring Telnet commands are available as soon as the
license key is added.
Installing through TotalStorage Specialist
You can install a license key through TotalStorage Specialist if a TotalStorage
Specialist license is already installed.
1. Launch a Web browser, type the switch name or IP address in the
Location/Address field of the browser, and press Enter.
The TotalStorage Specialist launches, displaying the Fabric view.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
523
2. Click the Admin button on the relevant switch panel.
The logon window displays.
3. Type a logon name and password with administrative privileges and press
Enter. The administrator account name is admin and the default password is
password.
The Administration view displays.
4. Select the License Admin tab.
5. Type the license key in the License Key field exactly as provided by your
switch supplier and click Add.
4.17.4 Using Advanced Performance Monitoring
In the screen captures that follow, we show the functions that are available using
the TotalStorage Specialist.
Attention: As the monitoring of any switch is subjective by nature, we just
show the screens to give the reader some familiarity with features that can be
monitored.
Figure 4-240 shows all the options that are available.
Figure 4-240 Advanced monitoring range of options
524
IBM SAN Implementation
To set up our parameters for SID/DID performance monitoring, we would use the
screen shown in Figure 4-241.
Figure 4-241 SID/DID performance setup
You will need to identify the port and SID/DID that you wish to monitor.
The SCSI commands have a number of options that allow you to monitor a
number of items. We show a selection of these in the screen captures that follow.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
525
Figure 4-242 shows SCSI Read/Write on a LUN per port.
Figure 4-242 SCSI read/write LUN per port setup
Figure 4-243 shows SCSI read/write per port setup.
Figure 4-243 SCSI read/write per port
In much the same way as we select the basic monitoring functions, we can select
items for the advanced monitoring canvas.
526
IBM SAN Implementation
Figure 4-244 shows a canvas with the maximum eight items that can be
displayed on a canvas.
Figure 4-244 Performance monitor canvas
Chapter 4. Implementing an IBM TotalStorage SAN Switch
527
To select and open up more options when a canvas is displayed, simply
right-click with the cursor position over the canvas. This is shown in Figure 4-245.
Figure 4-245 Canvas options
We have not shown all of the combinations that are possible with the
Performance Monitoring function, but we have showed a sample of the options
that are available to make sure that your SAN is performing in the way you would
wish it to.
528
IBM SAN Implementation
4.18 Administrative interface
The Administrative Interface provides access to the administrative functions
though the following tabs:














Switch Settings Tab
User Admin Tab
Firmware/Configuration File Administration Tab
SNMP Admin Tab
License Admin Tab
Remote Switch Tab (Optional Software)
QuickLoop Tab (Optional Software)
Configuration Tab
Extended Fabric Tab (Optional Software)
Routing
Network Config
Report
Port Settings
Trunk Information
We show these screen captures in the topics that follow. To enter the
administrative interface you will need to select the admin function. We show this
in Figure 4-246.
Figure 4-246 Switch admin selection screen
To access the Admin functions, you must first logon with an ID that has
administrative privileges. Once this has been done, and the relevant licenses
have been installed, you will be presented with the options that we show in
Figure 4-247.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
529
Figure 4-247 Switch settings screen
Use the Switch Settings tab to manage basic switch setup for items such as
switch name, switch domain ID, and enabling and disabling the switch and
compatibility modes.
530
IBM SAN Implementation
Table 4-22 describes the fields on the Switch Settings tab.
Table 4-22 Switch settings tab
Field
Description
Name
Enter data for the switch name. Enter a new name to
change a name in this field.
Domain ID
Displays or sets switch domain ID. Domain IDs must be
unique within a fabric. To change domain ID, enter new
domain ID in this field. Use a number from 1 to 239 for
normal operating mode (FCSW compatible) and a number
from 0 to 31 for VC encoded address format mode
(backward compatible to SilkWorm 1000 series).
Serial Number
Displays the serial number of the switch.
Extended Fabric Mode
Click the box to allow ports to be configured for long
distance, or uncheck to turn the option off.
(Status) Enabled
Click the radio button to enable the switch, or uncheck to
disable the switch.
(Status) Disabled
Click the radio button to disable the switch, or uncheck to
enable the switch.
OK
Click and exit Administrative View to save any changes.
Apply
Click to save any changes made to this tab and remain in
the current tab. Additional changes can be made and the
APPLY button clicked when making changes incrementally.
Close
Click to exit the Switch Admin view. If changes have been
made and not committed by clicking the APPLY button, a
dialog box is presented. It allows the changes to be
committed or deleted.
Reset
Click to reset the tab to the last set of saved changes.
Use the Network Configuration tab to manage the IP networking functionality of
the switch. Both Ethernet and FC IP networking is configured and the SYSLOG
daemon message recipients. The Network Configuration tab is shown in
Figure 4-248.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
531
Figure 4-248 Network config screen
532
IBM SAN Implementation
Table 4-23 describes the fields on the Network Config tab.
Table 4-23 Network config tab
Field
Description
Ethernet IP
Displays the Ethernet IP address
Ethernet SubnetMask
Displays the Ethernet SubnetMask address.
Gateway IP
Displays the Gateway IP address.
Fibre Channel IP
Displays the Fiber Channel IP address.
Fibre ChannelSubnetMask
Displays the Fiber Channel SubnetMask address.
Syslog IPs/~6
Displays the six Syslog IP address for a user to
configure.
OK
Click to save the changes made to the tab and to
exit the tab.
Apply
Click to save the changes made to this tab and to
stay in the current tab. Additional changes can be
made and the Apply button clicked when making
changes incrementally.
Close
Click to exit the current tab. If changes have been
made but not committed by clicking the APPLY
button, a dialog box displays.
Reset
Click to reset the tab to the last set of committed
changes. If the Apply button has not been clicked
on this tab, the parameters are returned to the
original values the tab had when it was initially
displayed.
Use the Firmware/Configuration File Administration tab to complete tasks
such as:
 Download firmware
 Boot the Switch
 Upload a Configuration file to the host
 Download the configuration from a file to the switch
 Reset the configuration to the default value
 Select the protocol of downloading (FTP or RSH).
 Select the location and authorization information and switch reboot directions.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
533
The Firmware/Configuration File Administration tab is shown in Figure 4-249.
Figure 4-249 Firmware upgrade screen
534
IBM SAN Implementation
Table 4-24 describes the fields on the Firmware/Configuration File
Administration tab.
Table 4-24 Firmware tab
Available in the Function section:
Firmware Download
Select the radio button to download firmware.
Bootswitch
Select the radio button to boot the switch.
Config Upload
Select the radio button to upload the configuration file to the
specified host. This allows for saving of the configuration
file to the switch using the specified filename (full path). The
User and Password must be valid for the specified host,
and the file path must be read-write capable by the user.
ConfigDownload
Select the radio button to download the firmware.
Config
Default Select the radio button to reset the configuration to
the default value.
Available in the Host Details section:
Protocol
Select the pull-down menu to chose the downloading
protocol.
User name
Enter the User Name.
Host IP
Enter the IP address of the host.
Filename
Enter the filename to be downloaded.
Available in the Boot Options section:
FastBoot
Select the radio button to do a Fastboot on the switch. This
will cause the switch to skip over the POST test.
Reboot
Select the radio button to reboot the switch.
Power on Self-Test
Check the box to have the switch do a POST test when it
reboots.
Reboot After Download
Check the box to have the switch reboot automatically after
the firmware download.
OK
Select and exit the tab to save any changes made.
Apply
Select to save any changes made to this tab and remain in
the tab. Additional changes can be made and the Apply
button clicked when making changes incrementally.
Close
Select to exit the Firmware/Configuration file tab. If changes
have been made and not committed, a dialog box will
display asking if want to save the changes.
Reset
Select to reset the tab to the last set of saved changes.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
535
Use the SNMP tab for administration of the SNMP Subsystem. From the SNMP
tab you can specify the switch community string, location, trap level, and trap
recipients.
Note: In order for the switches to send SNMP traps, you must first enter the
Telnet command snmpMibCapSet. This enables the MIBs on all switches to be
monitored.
The SNMP tab is shown in Figure 4-250.
Figure 4-250 SNMP screen
536
IBM SAN Implementation
Table 4-25 describes the fields on the SNMP tab.
Table 4-25 SNMP tab
Basic information:
Name
Displays or sets contact information for switch. Default is
Field Support.
Location
Displays or sets the location of switch. Default is End User
Premise.
Description
Displays or sets system description. Default is Fibre
Channel Switch.
Trap Level
Sets severity level of switch events that prompt SNMP
traps. Default is 0.
Enable Authentication
Trap
Check on to enable authentication traps; uncheck to
disable (recommended).
Community and Trap Recipient Configuration:
Community String
Displays the community strings that are available to use. A
community refers to a relationship between a group of
SNMP managers and an SNMP agent, in which
authentication, access control, and proxy characteristics
are defined. A maximum of six community strings can be
saved to the switch.
Recipient
Displays the IP address of the Trap Recipient. A trap
recipient receives the message sent by an SNMP agent to
inform the SNMP management station of a critical error.
Access Control List
Displays the Read/Write access of a particular community
string. Read only access means that a member of a
community string has the right to view, but cannot be
changed. Read/Write access means that a member of a
community string can be both viewed and changed.
Access Control List Configuration:
Access Host
Displays the IP address of the host of the access list.
Access Control List
Displays the Read/Write access of a particular access list.
Read only access means that a member of an access list
has the right to view, but cannot make changes. Read/Write
access means that a member of an access list can both
view and make changes.
OK
Click to save the changes made to the tab and to exit the
tab.
Apply
Click to save the changes made to this tab and to stay in the
current tab. Additional changes can be made and the Apply
button clicked when making changes incrementally.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
537
Close
Click to exit the current tab. If changes have been made but
not committed by clicking the Apply button, a dialog box
displays.
Reset
Click to reset the tab to the last set of committed changes.
If the Apply button has not been clicked on this tab, the
parameters are returned to the original values the tab had
when it was initially displayed.
You can use the License Administration tab to install license keys that are
provided. You can use the table within the Licence Administration tab to
remove a listed license from the switch. The License Administration tab is
shown in Figure 4-251.
Figure 4-251 License Administration screen
538
IBM SAN Implementation
Table 4-26 describes the fields on the License Administration tab.
Table 4-26 License admin tab
Field
Description
Feature
A list of the licenses installed on the switch.
License Key
Enter license key to be added or removed.
Add
Select to add the specified license.
Remove
Select to remove the specified license.
Close
Select to exit the current tab. If changes have been made but not
committed by clicking the Apply button, a dialog box displays.
Reset
Click to reset the tab to the last set of committed changes. If the
Apply button has not been clicked on this tab, the parameters are
returned to the original values the tab had when it was initially
displayed.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
539
Use the Report tab to display the printed report from the switch configuration.
The Switch Information Report can be generated by clicking the corresponding
link on the Configure tab in the Switch Administrative window. This report
provides information about all the switches, interswitch links and ports in the
Fabric. The Report display is shown in Figure 4-252.
Figure 4-252 Switch report information
540
IBM SAN Implementation
Use the Port Settings tab to disable/enable ports on the switch. This tab is also
used to set port speed to 1GB/2GB Autosense as well as to enable/disable
Trunking. The Port Settings tab is shown in Figure 4-253.
Figure 4-253 Port settings screen
Chapter 4. Implementing an IBM TotalStorage SAN Switch
541
Table 4-27 describes the fields on the Port Settings tab.
Table 4-27 Port settings tab
542
Field
Description
Port Number
The port number.
Trunking Enable:Disable
Check to enable or disable trunking. Four trunk
ports form a group, with one of them in the role of
master port, and the group can have member
ports.
Port Enable:Disable
Check to enable or disable ports on the switch.
Port Speed
Click to display port speed. Port speed can be
fixed to 1G, 2G, or negotiate. If the speed is set to
negotiate, the speed will depend on the negotiated
result.
OK
Click to save the changes made to the tab and to
exit the tab.
Apply
Click to save the changes made to this tab and to
stay in the current tab. Additional changes can be
made and the Apply button clicked when making
changes incrementally.
Close
Click to exit the current tab. If changes have been
made but not committed by clicking the Apply
button, a dialog box displays.
Reset
Click to reset the tab to the last set of committed
changes. If the Apply button has not been clicked
on this tab, the parameters are returned to the
original values the tab had when it was initially
displayed.
IBM SAN Implementation
You can use the User Admin tab to change the switch User and Admin account
names and passwords. The User Admin tab is shown in Figure 4-254.
Figure 4-254 User admin screen
Chapter 4. Implementing an IBM TotalStorage SAN Switch
543
Table 4-28 describes the fields on the User Admin tab.
Table 4-28 User admin tab
Field
Description
User Name
Enter new user name or modify the existing user
name.
New Password
Enter new password or modify the existing
password.
Verify Password
Re-enter password to verify.
OK
Click to save the changes made to the tab and exit
the Switch Administrative view.
Apply
Click to save the changes made to this tab.
Additional changes can be made and the Apply
button clicked when making changes
incrementally.
Close
Click to exit the Switch Administration view. If
changes have been made but not committed by
clicking the Apply button, a dialog box displays to
ask the user if they want to save the changes
before exiting the view.
Reset
Click to reset the tab to the last set of committed
changes. If the Apply button has not been clicked
on this tab, the parameters are returned to the
original values the tab had when it was initially
displayed.
The Configure tab provides the same functionality as the command-line
command configure. The following actions are controllable from the Configure
tab:




544
Fabric Parameters
Virtual Channel Parameters
Arbitrated Loop Parameters
Systems Services
IBM SAN Implementation
The valid values for each editable field are the same as those for use in the
configure command. The Configure tab is shown in Figure 4-255.
Figure 4-255 Configure screen
Chapter 4. Implementing an IBM TotalStorage SAN Switch
545
Table 4-29 describes the fields on the Configure tab, as shown in Table 4-29.
Table 4-29 Configure tab
546
Field
Description
BB Credit
Displays the number of buffers that are available
to attached devices for frame receipt.
E_D_TOV
Displays the Error Detect Time Out Value in
milliseconds. This timer is used to flag a potential
error condition when an expected response is not
received within the set time.
R_A_TOV
Displays the Resource Allocation Time Out Value
in milliseconds. This variable works with the
E_D_TOV to determine switch actions when
presented with an error condition.
Datafield Size
Specifies in bytes, the largest possible data field
size.
Per-Frame Routing Priority
When set, the virtual channel ID is used in
conjunction with a frame header to form the final
virtual channel ID.
Suppress Class F Traffic
Only applies if VC Encoded Address Mode is also
set. When set, translative addressing is disabled.
Disable Device Probing
When set, devices that do not register with the
Name Server are not present in the Name Server
data base. Set this mode only if the switch N_Port
discovery process (PLOGI, PRLI, INQUIRY)
causes an attached device to fail.
VC Encoded Address Mode
When set, the frame source and destination
address use an address format that is compatible
with SilkWorm 1000 switches. Set this mode only
if the fabric includes this type of switch.
Virtual Channel Parameters
Enables fine tuning for a specific application by
configuring the parameters for eight virtual
channels.
Send Fan Frames
Specifies that Fabric Access Notification frames
be sent to public loop devices to notify them of
their node ID and address.
Always Send RSCN
Issues a Remote State Change Notification,
following the completion of loop initialization,
when FL_Ports detect the presence of new
devices or the absence of preexisting devices.
IBM SAN Implementation
Do Not Allow AL_PA 0x00
Check box to specify that AL-PA is not allowed.
rstatd
Dynamically enables or disables a server that
returns information about system operation
information through remote procedure calls.
rapid
Check box to enable rapid system service.
rusersd
Dynamically enables or disables a server that
returns information about the user who is logged
into the system through remote procedure calls.
RLS Probing
Check to enable RLS Probing services.
OK
Click to save the changes made to the tab and to
exit the tab.
Apply
Click to save the changes made to this tab and to
stay in the current tab. Additional changes can be
made and the Apply button clicked when making
changes incrementally.
Close
Click to exit the current tab. If changes have been
made but not committed by clicking the Apply
button, a dialog box displays.
Reset
Click to reset the tab to the last set of committed
changes. If the Apply button has not been clicked
on this tab, the parameters are returned to the
original values the tab had when it was initially
displayed.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
547
The Routing tab is used to set the link cost for the selected ports and static
route. The Routing tab is shown in Figure 4-256.
Figure 4-256 Routing screen
548
IBM SAN Implementation
Following is a description of the fields on the Routing tab as shown in
Table 4-30.
Table 4-30 Routing tab
Field
Description
Dynamic Load Sharing (DLS)
Click the radio button to turn Dynamic Load
Sharing on or off.
In-Order Delivery (IOD)
Click the radio button to turn In-Order Delivery on
or off.
Port Number
Displays Port number.
Cost
You can use the Cost field to change the link cost
for a particular tab.
In Port
Displays Port number.
Destination
Displays the destination domain ID for the
“comma-separated” participating static routes for
a particular inport. The destination domain IDs
match the outports in the cell.
Out Port
Enter the Out port. It should be within the range of
ports that are available for static routes for the
current domain. More than one out port can be
used for any In port with a different domain ID.
Each domain ID requires an out port.
OK
Click to save the changes made to the tab and to
exit the tab.
Apply
Click to save the changes made to this tab and to
stay in the current tab. Additional changes can be
made and the Apply button clicked when making
changes incrementally.
Close
Click to exit the current tab. If changes have been
made but not committed by clicking the Apply
button, a dialog box displays.
Reset
Click to reset the tab to the last set of committed
changes. If the Apply button has not been clicked
on this tab, the parameters are returned to the
original values the tab had when it was initially
displayed.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
549
The Trunk Information tab is a read-only tab and has only the Close button
function. The Trunk Information tab is shown in Figure 4-257.
Figure 4-257 Trunk information screen
550
IBM SAN Implementation
Use the QuickLoop tab to manage QuickLoop configuration. The QuickLoop
tab is displayed only when the QuickLoop license is installed. The QuickLoop
tab is shown in Figure 4-258.
Figure 4-258 QuickLoop screen
Table 4-31 describes the fields on the QuickLoop tab.
Table 4-31 QuickLoop tab
Field
Description
QuickLoop Partner section
Current Name
Displays the current name of the remote switch.
World Wide Name
Displays the World Wide Name of the remote
switch.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
551
New Partner
Displays the current partner switch name of a
dual-switch QuickLoop.
QuickLoop Status section:
552
Enable
Click the radio button to enable the switch for
QuickLoop, or uncheck to disable the switch for
QuickLoop.
Disable
Click the radio button to disable the switch for
QuickLoop.
Port
Displays the port numbers.
Enabled
Click box to enable a port for QuickLoop, or
uncheck to disable the port for QuickLoop.
Local Switch Port
Lists the ports connected to the local switch.
Local Switch AL_PAs
Lists the AL_PAs of devices connected to the local
switch.
Partner Switch Port
Lists the ports connected to a remote switch.
Partner Switch AL_PAs
Lists the AL_PAs of devices connected to a
remote switch. This information displays if a
partner is configured.
OK
Click to save the changes made to the tab and to
exit the tab.
Apply
Click to save the changes made to this tab and to
stay in the current tab. Additional changes can be
made and the Apply button clicked when making
changes incrementally.
Close
Click to exit the current tab. If changes have been
made but not committed by clicking the APPLY
button, a dialog box displays.
Reset
Click to reset the tab to the last set of committed
changes. If the Apply button has not been clicked
on this tab, the parameters are returned to the
original values the tab had when it was initially
displayed.
IBM SAN Implementation
You can use the Remote Switch feature to configure a pair of switches to operate
over an extended WAN interface so that they can communicate across an ATM
network by using a compatible Fibre Channel to ATM gateway. This feature
requires an active Remote Switch sub-license in both switches.
Use the Remote Switch tab to manage the Remote Switch option. This tab
displays only when the Remote Switch is installed. We discuss this feature in
greater detail in “Remote Switch” on page 557.
The Remote Switch tab is shown in Figure 4-259.
Figure 4-259 Remote switch screen
Chapter 4. Implementing an IBM TotalStorage SAN Switch
553
Table 4-32 describes the fields on the Remote Switch tab.
Table 4-32 Remote switch tab
Field
Description
Remote Switch Status Section
554
Enabled
Click box to enable the Remote Switch feature, or
uncheck to disable it.
Disabled
Click the box to disable the Remote Switch
feature, or uncheck to disable it.
OK
Click to save the changes made to the tab and to
exit the tab.
Apply
Click to save the changes made to this tab and to
stay in the current tab. Additional changes can be
made and the Apply button clicked when making
changes incrementally.
Close
Click to exit the current tab. If changes have been
made but not committed by clicking the Apply
button, a dialog box displays.
Reset
Click to reset the tab to the last set of committed
changes. If the Apply button has not been clicked
on this tab, the parameters are returned to the
original values the tab had when it was initially
displayed.
IBM SAN Implementation
Use the Extended Fabric tab to manage the Extended Fabric feature. From the
Extended Fabric tab, you can specify which ports to be configured for distance
and at what level. The Extended Fabric tab appears only when the Extended
License is installed on the switch. For ports that are disabled, the rows appear
grayed-out in the table within the Extended Fabric tab. We discuss the extended
fabric feature in greater detail in “Extended Fabrics” on page 561.
The Extended Fabric tab is shown in Figure 4-260.
Figure 4-260 Extended fabrics screen
Chapter 4. Implementing an IBM TotalStorage SAN Switch
555
Table 4-33 describes the fields on the Extended Fabric tab.
Table 4-33 Extended fabric tab
Field
Description
Port Number
Port Number being used for the Extended
Fabric.
Long Distance Setting
Click to view Long Distance settings.
OK
Click to save the changes made to the tab
and to exit the tab.
Apply
Click to save the changes made to this tab
and to stay in the current tab. Additional
changes can be made and the Apply
button clicked when making changes
incrementally.
Close
Click to exit the current tab. If changes
have been made but not committed by
clicking the Apply button, a dialog box
displays.
Reset
Click to reset the tab to the last set of
committed changes. If the Apply button
has not been clicked on this tab, the
parameters are returned to the original
values the tab had when it was initially
displayed.
4.19 Distributed fabrics
There are two features available on the F16 switch that allow for distribution of
the fabric:
 Remote switch
 Extended fabrics
We will discuss these features in the topics that follow.
556
IBM SAN Implementation
4.19.1 Remote Switch
This topic describes the Remote Switch feature which is an optionally licensed
product that runs on 3534 and 2109 series switches or later with Fabric OS
version 3.0.
The Remote Switch feature, in conjunction with a compatible Fibre Channel to
asynchronous transfer mode (ATM) gateway, enables two 3534 or 2109 series
fabric switches to be connected over an ATM connection, with a distance of up to
10 kilometers between each switch and the respective ATM gateway.
The two switches are cascaded together to form a fabric that, from the viewpoint
of the connected hosts and storage devices, interact the same as locally
connected switches. The performance limitations depend only on the type of
ATM connection that is used.
Remote Switch supports a maximum of two switches in a fabric.
The Remote Switch feature provides:
 Any-to-any connectivity — A host connected on the local or remote switch can
communicate with storage devices at either location.
 Coordinated fabric services — The Remote Switch fabric configuration fully
supports all fabric services, the same as a centralized fabric configuration.
These services include Distributed Name Services, Registered State Change
Notifications, and Alias Services.
 Distributed management — Access to the management facilities
(TotalStorage Specialist, Telnet, SNMP, and SES) is available from either the
local or the remote switch. Interconnect for switch management is routed
through the Fibre Channel connection; no additional network connection is
required between sites.
 Ability to support multiple interswitch links (ISLs) — Sites requiring redundant
configurations can connect multiple E_ports to remote sites by using multiple
gateways. Standard Fabric OS routing facilities automatically maximize
throughput by using the E_ports to load share traffic during normal operation,
with automatic failover and failback during interruption on the Wide Area
Network (WAN) connection.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
557
4.19.2 Installing Remote Switch
A Remote Switch fabric requires two switches that are 3534 or 2109 series
switches with Fabric OS version 3.0 installed, with the switches configured the
same.
When you install a Remote Switch, you must also install a separate license on
each of the two switches. Licenses might have been installed on the switches at
the factory. If not, contact your switch supplier to obtain a license key.
You can install a Remote Switch license in two ways:
 By using Telnet
 By using TotalStorage Specialist
Installing the Remote Switch feature using Telnet
Perform the following steps to install Remote Switch using Telnet:
1. Login to the switch through Telnet using an account that has administrative
privileges.
2. To determine whether a Remote Switch license is already installed on the
switch, type licenseShow on the Telnet command line.
A list of all the licenses that are currently installed on the switch displays. For
example:
admin>licenseShow
cQebzbRdScRfcOiK:
Web license
Zoning license
AybbzQQ9edTzccOX:
Fabric license
If the Remote Switch license is listed, the feature is installed and is
immediately available. If the Remote Switch license is not included in the list
or is incorrect, continue with the following steps.
3. Type the following on the command line:
licenseAdd "key"
where key is the license key that was provided to you, surrounded by double
quotation marks. The license key is case sensitive and must be entered
exactly as given.
4. Verify that the license was added by typing the following on the command line:
licenseShow
If the Remote Switch license is listed, the feature is installed and is immediately
available. If the license is not listed, repeat step 3.
558
IBM SAN Implementation
Installing Remote Switch using TotalStorage Specialist
Perform the following steps to install Remote Switch using TotalStorage
Specialist:
1. Launch the Web browser.
2. Type the switch name or IP address in the Location/Address field and press
Enter. The TotalStorage Specialist launches, displaying the Fabric view.
3. Click Admin on the relevant switch panel.
The logon window displays.
4. Type a logon name and password with administrative privileges and press
Enter.
The Administration view displays.
5. Select the License Admin tab.
6. Type the license key in the License Key: field and click Add License.
The Remote Switch feature is available as soon as the license key is added.
4.19.3 Using Remote Switch
You can configure switches for use with Remote Switch through Telnet or
through TotalStorage Specialist.
The Remote Switch feature operates in conjunction with a Fibre Channel-to-ATM
gateway. The gateway provides both a Fibre Channel physical interface
functioning as an E_port and an ATM physical interface.
The gateway accepts Fibre Channel frames from one side of a Remote Switch
fabric, transfers them across a WAN using ATM protocol, and passes them to the
other side of the Remote Switch fabric.
To transfer frames across a WAN using ATM protocol, the Fibre Channel frames
(from 256 to 2112 bytes) must be broken into smaller pieces (53 byte ATM cells)
at the local end of the ATM network. After the frames are broken into smaller
pieces, they are tunnelled inside ATM cells to be transmitted across the ATM
network. At the remote end of the ATM network these pieces are reassembled
back into complete Fibre Channel frames and are transmitted through the remote
Fibre Channel interface.
To accomplish this, the gateway provides an E_port interface that links to the
2109 Model F16 E_port. After the link between the two E_ports is negotiated, the
gateway E_port moves to pass-through mode and passes Fibre Channel traffic
from the 2109 Model F16 E_port to the ATM network.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
559
4.19.4 Configuring a Remote Switch fabric
A Remote Switch fabric requires two 3534 or 2109 series switches with identical
configurations. A separate Extended Fabric license is not required to operate the
switch at distances greater than 100 km. This can be achieved when the switch
operates over ATM. Performance is limited to the ATM link, which is capable of
1.55 Mbps to 155 Mbps. Other FC-ATM devices such as ADVA DiskLink do not
require a remote switch. The DiskLink device does not perform E_port
connections, but rather imports devices from a remote SAN and is recognized as
an N_port device in the local SAN.
In addition to normal switch configuration options, the following parameters must
be configured:
 Time-out values — The Resource Allocation Time-out Value (R_A_TOV) and
Error Detect Time-out Value (E_D_TOV) must be increased, as appropriate,
for all switches participating in the Remote Switch fabric. This provides for the
possible increase in transit time caused by the introduction of WAN links into
the fabric.
 Data field size — All switches participating in the Remote Switch fabric must
have the data field size configured to the maximum of 2048 bytes to
accommodate the maximum field size that is supported by the ATM gateway.
Data field sizes smaller than 2048 bytes can be set, but they might cause
significant performance degradation.
 Class F frame suppression — All switches participating in the Remote Switch
fabric must have the Class F frame suppression flag set. Class F frames are
automatically converted to Class 2 frames.
 BB credit — The setting for BB credit must be the same on both switches.
Switches with a different value will segment.
Setting parameter values through Telnet
Use the telnet configure command to set the following parameter values:




BB credit
R_A_TOV and E_D_TOV
Data field size
Class F frame suppression flag
Using the following commands in the sequence shown, will allow you to change
the parameter values:
switch:admin>switchDisable
switch:admin>configure
Configure...
Fabric parameters (yes,y,no,n):[no]yes
Domain:(1..239)[2]
560
IBM SAN Implementation
BB credit:(1..16)[16 ]
R_A_TOV:(4000..120000)[10000]
E_D_TOV:(1000..5000)[2000]5000
Data field size:(256..2112)[2112]2048
Non-SCSI Tachyon Mode:(0..1)[0]
Disable Device Probing:(0..1)[0]
Suppress Class F Traffic:(0..1)[0]1
switch:admin>switchEnable
A prompt for each parameter is displayed. You can then set any parameter to
any allowed value.
Note: The allowable BB credit parameter values are 1 - 16. This value is the
BB credit that is offered to all F_ports that are using the Remote Switch
feature. E_ports that are not Remote Switch E_ports are not affected.
4.19.5 Extended Fabrics
Extended Fabrics is an optionally licensed product that runs on 3534 or 2109
series switches with Fabric OS version 3.0.
The Extended Fabrics feature uses Fibre Channel technology to create a fabric
interconnected at a distance of up to 100 km (328 084 ft.). Extended Fabrics can
increase the allowable distance between two switches or between a switch and
an ATM gateway used in a Remote Switch configuration.
Extended Fabrics optimizes the internal buffering algorithm for 3534 or 2109
series switches. It provides maximum buffering between E_ports that are
connected over an extended distance through buffer reconfiguration. This results
in line speed performance of close to full Fibre Channel speed for switches that
are interconnected at 100 km, thus providing the highest possible performance
for transfers between switches.
The Fibre Channel connection extensions can be provided by extended distance
GBICs, Fibre Channel repeaters, or wave division multiplexing (WDM) devices.
Note: Performance can vary depending on the condition of the fiber optic
connections between the switches. Losses due to splicing, connectors, tight
bends, and other degradation can affect the performance over the link and the
maximum distance possible.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
561
To enable Extended Fabrics, an Extended Fabrics license must be installed. If a
fabric is created with a 2109 Model F16 switch, the long distance extended fabric
configuration has to be set only once for each fabric at the edge port connector
switch. The edge port connector switch automatically works with the rest of the
switches in the fabric.
Note: To enable Extended Fabrics in a fabric created with 3534 switches,
each switch in the fabric must be configured individually.
4.19.6 Installing Extended Fabrics
When you install Extended Fabrics, you must also install a license on each
switch in the fabric. If a license was not installed in the switch at the factory,
contact your switch supplier to obtain a license key. You can install Extended
Fabrics licenses in two ways:
 By using Telnet
 By using TotalStorage Specialist
Installing the Extended Fabrics feature using Telnet
Perform the following steps to install Extended Fabrics using Telnet:
1. Login to the switch through Telnet using an account that has administrative
privileges.
2. To determine whether an Extended Fabrics license is already installed on the
switch, type licenseShow on the Telnet command line.
A list of all the licenses that are currently installed on the switch displays. For
example:
admin>licenseShow
1A1AaAaaaAAAA1a:
Release v2.2
Web license
Zoning license
SES license
QuickLoop license
If an Extended Fabrics license is correctly listed, the feature is installed and
immediately available. If an Extended Fabrics license is not included in the
list, or is incorrect, continue with steps 3 and 4.
3. Type the following on the command line:
licenseAdd "key"
where key is the license key that was provided to you, surrounded by double
quotation marks. The license key is case sensitive and must be entered
exactly as given.
562
IBM SAN Implementation
4. Verify that the license was added by typing the following on the command
line:
licenseShow
If the Extended Fabrics license is listed, the feature is installed and immediately
available. If the license is not listed, repeat step 3.
Installing the Extended Fabrics using TotalStorage Specialist
Perform the following steps to install Extended Fabrics through TotalStorage
Specialist:
1. Launch the Web browser.
2. Type the switch name or IP address in the Location/Address field and press
Enter. TotalStorage Specialist launches, displaying the Fabric view.
3. Click Admin on the relevant switch panel. The logon window displays.
4. Type a logon name and password with administrative privileges and press
Enter. The Administration view displays.
5. Select the License Admin tab.
6. Type the license key in the License Key field and click Add License. The
Extended Fabrics feature is available as soon as the license key is added.
4.19.7 Using Extended Fabrics
You can configure ports to support long distance links through Telnet or through
TotalStorage Specialist.
Support configurations
An Extended Fabric can be created with either 3534 or 2109 series switches
respectively, that are running Fabric OS v3.0. An Extended Fabric can consists
of:
 3534 switches only
 2109 series switches only
 A combination of 3534 and 2109 series switches
Chapter 4. Implementing an IBM TotalStorage SAN Switch
563
Note: In a combination (3534 and 2109 series) configuration, the
long-distance ISL that connects the fabrics must be installed between
edge-port switches of same series. An Extended Fabric does not work if the
long distance ISL is installed between non matching edge port switches.
4.19.8 Configuring Extended Fabrics
In order to run Extended Fabrics, the following two parameters need to be set:
 Switch configuration to enable long distance
 Port configuration to select the long distance mode
In the 3534 switches, each switch within the fabric must have the switch
configuration turned on. In the 2109 series switches, only the edge-port switches
need to have the switch configuration turned on.
Perform the following steps to set the long distance fabric mode bit:
1. Login to the switch through Telnet.
2. At the command line, type the following command:
switchDisable
3. At the command line, type the following command:
configure
4. Type Y at the Fabric parameters prompt.
5. Type 1 at the following prompt:
Long Distance Fabric [0]:
There are three possible long distance levels for a port:
 Level 0 — Reconfigures the port as a regular switch port. The number of
buffers reserved for the port supports up to 10 km links.
 Level 1 — Distances up to 50 km will support 1 Gb/s and 2 Gb/s switches
(3534 and 2109 series).
 Level 2 — Distances up to 100 km will support 1 Gb/s and 2 Gb/s switches
(3534 and 2109 series).
Ports are grouped into quads, each of which consists of four adjacent ports that
share a common pool of frame buffers. The possible quad groupings are:
 Ports 0 -3
 Ports 4 -7
 Ports 8 -11
564
IBM SAN Implementation
 Ports 12 - 15
Certain buffers are dedicated for each port, and others are shared among the
ports. In Extended Fabric mode, one port is given an increase of dedicated
buffers from this pool.
The total number of frame buffers in a quad is limited, and the Extended Fabric
port matrix introduces a combination of long distance ports that are available.
This is shown in Table 4-34.
Table 4-34 Combination of long distance ports that are available
Port 0
Port 1
Port 2
Port 3
L1
F or E
F or E
F or E
L1
L1
F or E
F or E
L1
L1
L1
F or E
L1
L1
L1
L1
L2
F
F
F
L2
E
F
L2
E
L2
L1
L2
L1
F
Where:





L0 represents an Extended Fabric mode of 10 km
L1 represents an Extended Fabric mode of 50 km
L2 represents an Extended Fabric mode of 100 km
F represents the F_port that is used when connected to devices
E represents the E_port that is used for interswitch connectivity
Setting the port configuration
You can configure a port to support long distance links by using the Telnet
command portCfgLongDistance or by using the TotalStorage Specialist.
Chapter 4. Implementing an IBM TotalStorage SAN Switch
565
566
IBM SAN Implementation
5
Chapter 5.
Implementing the INRANGE
FC/9000 Fibre Channel
Director
The IBM machine type 2042 model number 001, INRANGE FC/9000 Fibre
Channel Director, is the core product of a reseller agreement between IBM and
INRANGE Technologies, which adds the INRANGE FC/9000 Fibre Channel
Director to IBM’s growing list of enterprise-class SAN fabric offerings.
© Copyright IBM Corp. 2001
567
5.1 Introduction to the INRANGE FC/9000 director
In this chapter we introduce the INRANGE FC/9000 Director and cover the
following topics:






Product architecture
Zoning methodologies
Management features
Supported topologies
Supported servers
Supported devices
In Figure 5-1 we show the front view of an FC/9000.
Figure 5-1 front view of an INRANGE FC/9000 director
568
IBM SAN Implementation
5.1.1 Product overview
The FC/9000 Fibre Channel Director is INRANGE’s flagship SAN product. It was
designed as a director-class product and has the following significant features:






Support of Fibre Channel Protocol for open servers
Support of FICON attachment for Mainframe class servers
High port count, with up to 128 ports
Fully redundant architecture with non-disruptive code load-capabilities
Graphical user interface
Broad range of supported port-topologies
Full loop support
INRANGE’s Translative Loop Mode allows legacy nodes using loop protocols of
any kind to be managed as if they were truly fabric nodes. This includes public
and private loop ports with both initiators and targets.
We cover this in more detail in “Attaching loop ports” on page 612.
Port count
One chassis of an FC/9000 director can hold up to 64 GBICs. By interconnecting
the main boards of two directors, a non-blocking 128 director can be created.
Due to the usage of GBICs instead of fixed port-cards, the granularity of port
upgrades is one port.
Short wave and long wave ports can be mixed within all internal entities of this
director.
Redundancy and non-disruptive activities
The FC/9000 features a N+1 redundancy for all of its elements. This redundancy
results in high availability. Even in the case of failure of any internal elements, the
director is still operational.
Obviously, in case of port-failures, additional multipathing software is needed to
maintain this level of availability.
All activities, including code loads, code-activation, and replacement of failed
parts can be done non-disruptively.
Chapter 5. Implementing the INRANGE FC/9000 Fibre Channel Director
569
5.1.2 Currently supported zoning methodologies
Zoning is one of the key functions provided by SAN switches or directors.
Basically it provides methods to limit possible communication between ports.
This can be used to subdivide a physical SAN into separated logical ones.
Zoning can be seen as an important security feature of SAN products.
Since the definitions of different zoning-methods are not commonly agreed or
adhered to within the SAN industry, we will refer to INRANGE’s zoning
terminology throughout this chapter. INRANGE offers two kinds of zoning:
 Hardware zoning
 Software zoning
Hardware zoning actually isolates ports from other ports within the same director.
Consequently hardware zones are never overlapping. Any communication
between hard zones is blocked. This is widely considered as the highest level of
security.
Soft zoning allows you to overlap ports. That means it is possible to place ports
into different zones.
Routing information is stored in a central name server table, which will be
accessed by initiators before actually starting their I/O.
Soft zones within INRANGE reference to specific physical ports of the director.
Soft zoning referencing to WWPN of attached nodes is planned to be made
available by firmware upgrades in the second half of 2001.
You will find more detailed information on these topics in 5.4.6, “Defining name
server zones” on page 644.
5.1.3 Management capabilities
FC/9000 fabrics can be managed using different communication methods:





570
IN-VSN-Manager (IP based client/server management software
Simple network management protocol (SNMP)
Serial interface (RS232, dedicated for INRANGE/ IBM engineers)
Call Home (modem connection for notification purposes)
Trivial file transfer protocol (TFTP) to load microcode IP-settings
IBM SAN Implementation
Figure 5-2 shows an example of a director view with IN-VSN Manager.
Figure 5-2 Example of IN-VSN management view
The most commonly used interface with the INRANGE FC/9000 director is the
IN-VSN software tool. Therefore, in the following topics we will focus on how to
use IN-VSN.
5.1.4 Supported protocols
In most environments, a homogeneous landscape of servers and storage is hard
to find. For example, most tape-drives solely support FC_AL (known as
arbitrated loop), whereas modern disk systems are widely used with
point-to-point protocol (sometimes called P2P).
Thus, enterprise wide SAN solutions should be flexible enough to support
different FCP topologies.
Chapter 5. Implementing the INRANGE FC/9000 Fibre Channel Director
571
INRANGE does just that, by supporting these protocols:
 Open Systems:
– Arbitrated Loop
• Public loop
• Private loop
– FC-SW (Fibre Channel Switched Fabric)
 S/390 systems (zSeries):
– FICON
All these can attached to a single INRANGE director at the same time.
Support of cascading
To create even larger fabrics FC/9000 directors can be cascaded. By doing this
you can create fabrics with more than a thousand external ports. Today, IBM
supports fabrics with up to 8 cascaded INRANGE FC/9000 directors.
However, cascading is not supported when using FICON attachments in the
currently supported microcode releases.
5.1.5 Supported host attachment
Currently these servers are supported by IBM to attach to the FC/9000:
 IBM 9672 Enterprise G5, G6 and z-series server with FICON Channel Card
(FC2314 and FC2316), Longwave and Shortwave laser
 IBM Netfinity server with Windows NT 4.0 (SP6a) and FAStT Host Adapter
(P/N:00N6881)
 Intel-based servers with Windows NT 4.0(SP6a) or 2000K and QLogic
QLA2200F Host Bus Adapter
 Sun Servers with Solaris 2.6,2.7, 8 and Host Bust Adapters - SBus JNI
FC64-1063-N or PCI LP8000, QLA2200F, JNI FCI-1063
Additionally, the following servers are in their testing process now, and are
expected to be supported by IBM once testing is complete:
 IBM RS/6000 and RS/6000 SP Servers with AIX 4.3.3 and Gigabit Fibre
Channel Adapter (FC 6227)
 HP/9000 Servers with HP/UX 11.0 and A5158A Adapter
For the latest support matrix of INRANGE FC/9000, refer to:
http://www.storage.ibm.com/ibmsan/products/directors/prod_data/supserver-042.html
572
IBM SAN Implementation
5.1.6 Supported device attachment
Currently these Storage products are supported by IBM:
 IBM Magstar 3590 A60 Tape Subsystem with FC 3432 (FICON Attachment Longwave) in a 3494 Tape Library, in a 3590 Model A14 Frame, in a
standalone 19-inch rack; or C14 Silo Compatible Frame
 IBM Magstar 3590 Tape Subsystem 3590-E11/B11 in standalone rack mount;
3590-E1A/B1A in 3494 Tape Library or 3590C-Silo Compatible with
FCP-Attachment
 IBM Enterprise Storage Server (M/T: 2105-Fx0) and FICON Host Adapter
 IBM Enterprise Storage Server (M/T: 2105-Ex0 or 2105-Fx0) and Fibre
Channel Host Adapter (FC 3022)
Other attachable devices include HDS 7700E, HDS 99x, EMC SYM 5x and Sun
A5200. However, these devices are directly supported by INRANGE as a part of
the IBM-INRANGE cooperation.
For the latest INRANGE supported device list, refer to:
http://www.inrange.com/ibm/interoperability.php
For the latest IBM supported device list, refer to:
http://www.storage.ibm.com/ibmsan/products/directors/prod_data/supserver-042.html
5.2 Installing an INRANGE SAN
The following chapter covers how to install an INRANGE SAN including topics
like:






Target environment
Prerequisites
Initial setup
Installing the IN-VSN management software
Accessing the IN-VSN management software
User management
5.2.1 Target SAN environment
In our target ITSO environment we used these components:




One Enterprise Storage Server 2105 F20
One INRANGE Fibre Channel director FC/9000, equipped with 64 GBICs
Four Hewlett Packard servers running HP-UX 11
ShortWave fibre infrastructure with 50 micron core diameter
Chapter 5. Implementing the INRANGE FC/9000 Fibre Channel Director
573
In Figure 5-3 we show our target ITSO environment.
Hewlett Packard servers running HP-UX 11.0
HP L Class 2000
HP L Class 2000
HP D Class 280
64
HP K Class 360
Inrange FC/9000
ShortWave fibre optics (50micron)
ESS 2105 - F20
Figure 5-3 Initial INRANGE environment
For management purposes we have one dedicated PC server attached to the
director. This management station runs the server portion of the INRANGE
IN-VSN Manager to control all fabrics.
5.2.2 Verifying all prerequisites
Before starting the initial setup, it is important to have performed these steps:
 Obtain two power supplies for each director, for redundancy reasons.
 Ensure that you have the capability to attach directors and management
station to ethernet network.
 Prepare a stable floor ground — one director weighs from 8 to 95 kg.
 Use the official INRANGE 19” rack, or any 19” racks that meet NSI/EIA
230-standard.
574
IBM SAN Implementation
5.2.3 Initial setup of INRANGE FC/9000 IP settings
The INRANGE Director is delivered with the current supported level of firmware
and a default TCP/IP setting of 10.1.1.51 and 10.1.1.52, and a Subnet mask
setting of 255.255.255.0. There is also a default chassis ID, switch ID and fabric
ID. Without doing any kind of cascading, there is no need to change these IDs.
It is the responsibility of an IBM Customer Engineer (CE) to reset all default
addresses to reflect the environment in which it is being installed.
For added security, the TCP/IP address can only be set or reset by the CE, using
an RS232 connection and entering the CE userid and password. The new
TCP/IP address will be displayed in an LED panel that can be located on the
FCM module.
The PC that will be used for the IN-VSN server needs to be connected to the
FCM modules using the Ethernet ports.
You should also ascertain whether the applicable microcode level is installed or
needs to be installed. The same is true for the IN-VSN management software:
 The director microcode level that we will be using is: 02.00.
 The IN-VSN management tool release is: 2.0.0 (Build RC6).
Since these codes are subject to change as new functions are added and
improvements made, ask your IBM or INRANGE Technical contact what the
current supported levels are.
5.2.4 Establishing network connection
As mentioned above, the INRANGE director and its management PC are
delivered with pre-installed IP settings. They are efficient enough to set up a
small private network with just directors and the management PC as members.
You can leave the initial IP setup as it was delivered for use as, or like, a private
network. Consequently only local users can attach to the directors and its
IN-VSN management tool.
Or you can adopt your corporate network settings to enable remote IN-VSN
access.
Chapter 5. Implementing the INRANGE FC/9000 Fibre Channel Director
575
Leaving all IP settings as a private network
For using the IN-VSN software from this local private network, the supplied
3Com/US Robotics hub is sufficient enough. To enable all IP based components
to talk together, plug in the Management PC and both INRANGE IP ports to this
3Com Hub. So initially, our network setup looks like that shown in Figure 5-4.
Management PC
Ethernet-Hub
FC/9000
64
Figure 5-4 Private IP network for initial IN-VSN management ability
Enabling IN-VSN access from a corporate network
To exploit the remote management capabilities of the IN-VSN management
software, we recommend that you connect this network as a subnet to the
corporate LAN.
Before actually changing any parameters, it is important to obtain all the
information you will need in advance, such as:
 Available IP addresses
 Valid subnet mask
 Default gateway
To connect the INRANGE subnet to your corporate LAN, follow these steps:
1. Change the IP setting of the primary FCM blade using the RS232 Interface
(this should be done by INRANGE or IBM Customer Engineers).
2. Change the IP setting of the secondary FCM blade using the RS232 interface
(this should be done by INRANGE or IBM Customer Engineers).
3. Change the IP settings of the management PC using the common Windows
Control Panel tools. Reboot the Windows server.
4. From the management PC, ping both IP addresses of the director to ensure
that everything is set properly (provided that all components are still
connected to the 3Com IP-Hub).
5. Then attach all required ports to a switch or hub that is actually connected to
the corporate network. You could still use the 3Com Hub as a connecting
device.
576
IBM SAN Implementation
After attaching our INRANGE setup to IBM’s corporate network, as shown in
Figure 5-5, we are now able to access the IN-VSN software from wherever we
are in the corporate network.
Management PC
Ethernet-Hub
FC/9000
Corporate network
Figure 5-5 INRANGE setup attached to a corporate network
To gain actual access to the IN-VSN management tool, you will need to install an
IN-VSN client that can then communicate with the IN-VSN server over the
corporate network.
Instructions on how to install both the server and the client part of IN-VSN
software are provided in 5.2.5, “Installing the IN-VSN Enterprise Manager
software” on page 579.
Setting up high security network access
In the previous setup we described a network layout in which the Management
PC as well as the fabric components were connected to the corporate network.
However if this corporate network itself cannot be considered as secure enough,
we recommend that you separate the fabric components from the corporate
network. The only bridge between such a separated fabric management network
and the corporate network would be the Management PC.
Chapter 5. Implementing the INRANGE FC/9000 Fibre Channel Director
577
Referring to Figure 5-6, we see that now only the Management PC can access
the directors’s IP ports.
other directors
ITSO director
Ethernet
Ethernet-Hub
IN-VSN server
on Management PC
(with two network interfaces)
Corporate network
ITSO Workstation
with IN-VSN client
ITSO Workstation
with IN-VSN client
Figure 5-6 INRANGE setup with secure director access
Direct IP access from the corporate network to directors is now impossible. The
only way to gain access is using the IN-VSN server.
We consider this as the most secure network setup for remote IN-VSN access.
However, you will need two network interfaces in the Management PC.
578
IBM SAN Implementation
5.2.5 Installing the IN-VSN Enterprise Manager software
There are a number of different ways in which the IN-VSN software can be
delivered.
If software feature code 7600 is configured, the workstation pack will include a
PC, monitor, Ethernet Hub, and Modems. The management software comes
pre-installed on the PC.
If you require more than one version of the IN-VSN client code, this is achieved
by using feature code 7201.
If no additional software feature codes are configured when ordering the
INRANGE Director, you will receive a CD that contains the IN-VSN server and
client code. This CD is only licensed for one copy of the server and one copy of
the client.
PC hardware for IN-VSN server
The server and client can be installed on a customer owned and designated PC,
as long as it meets with the following minimum recommended specifications:
IBM Pentium III PC or an IBM-Compatible Pentium III PC
















500 MHz processor
128 MB SDRAM
4 MB Video RAM
13 GB hard drive
1.44 MB diskette drive
CD-ROM
1 parallel port
1 Ethernet 10Base-T/100 Base-TX
IBM or equivalent mouse
2 external serial com ports (debug serial cable, external modem)
1 internal com port (internal modem)
17-inch 1280 x 1024 x 256 SVGA monitor
Windows NT 4.0 with Service Pack 6a and higher
Windows 2000 Professional
Internal and External modem compatibility
Analog protocol support: V.90 5 6kb/s ITU Standard, 3Com/US
Robotic/Multi-Tech (international) hardware compatible modems
recommended (do not use Win modem software controlled modems)
Be aware that only Windows operating systems are supported as software
platforms for IN-VSN tools.
Chapter 5. Implementing the INRANGE FC/9000 Fibre Channel Director
579
Running the setup procedures of IN-VSN server and client
Both the IN-VSN server and client require the following two programs to be
started from the installation CD:
 Use j2re1_3_0-win.exe to install the appropriate Java programs.
 Use setup.exe to actually install the IN-VSN server and/or the IN-VSN client
software.
For systems on which the IN-VSN server should run, an additional odbc driver
has to be installed:
 Use odbcinst.exe to accomplish this.
To run the IN-VSN installation, follow these steps:
 From a Windows browser or a command prompt, start D:\setup.exe.
 The install wizard will appear. Click Next to continue the installation as shown
in Figure 5-7.
Figure 5-7 Running the IN-VSN setup: Initial screen
580
IBM SAN Implementation
The setup program then checks whether you have the appropriate level of Java
installed on this system or not, as shown in Figure 5-8.
Figure 5-8 Running the IN-VSN setup: Java VM search
Click I Agree and Next in the Licence Agreement Window.
Chapter 5. Implementing the INRANGE FC/9000 Fibre Channel Director
581
Then you must decide which part of the IN-VSN software should be installed,
server and/or client, as shown in Figure 5-9.
Figure 5-9 Running the IN-VSN setup: Feature selection
After selecting the features that you wish to install, you may either accept the
default installation path or enter a new one. The default installation path for both
client and server is C:\INRANGE\Fc9000. The setup program automatically
creates the folder if you agree to its creation.
582
IBM SAN Implementation
Before actually starting the installation a list of all installation parts is shown in a
list with its needed disk space. Click Install Now to accept these settings, as
shown in Figure 5-10.
Figure 5-10 Running the IN-VSN setup: Verifying all packages to install
After installing these IN-VSN packages, you are given an installation summary
which tells you that all parts were installed successfully.
Running the setup procedure to install the odbc driver
As mentioned before, all systems that should run the IN-VSN server part need to
have an appropriate odbc driver. For IN-VSN clients this part is not needed.
To install it, run odbcinst.exe, which is part of the IN-VSN installation CD.
Chapter 5. Implementing the INRANGE FC/9000 Fibre Channel Director
583
Leave all components selected in the odbc installation window, as shown in
Figure 5-11.
Figure 5-11 Running obdc
5.2.6 Accessing the management tool
Make sure that the IN-VSN server is running either on the local machine or
elsewhere in the network.
Since the IN-VSN management tool is not browser based, it is necessary to have
the client piece of software installed on your workstation.
584
IBM SAN Implementation
We installed the IN-VSN client software on two different workstations in our
target environment, as shown in Figure 5-12.
Management PC
with IN-VSN server
Ethernet-Hub
FC/9000
Corporate network
ITSO Workstation
with IN-VSN client
ITSO Workstation
with IN-VSN client
Figure 5-12 Final IN-VSN software setup
This layout makes it possible to have multiple users logged in to the IN-VSN
software at the same time.
IN-VSN clients do not talk directly to the FC/9000. All communication to the
FC/9000 is done via the IN-VSN server. However, the user interface is the
IN-VSN client.
All director or fabric management related tasks are done using the IN-VSN client
interface. The server interface is only used for initial database backup and Call
Home settings.
Starting the IN-VSN server
Before you can actually start any IN-VSN client sessions, the IN-VSN server
must be up and running.
You can start the IN-VSN server on the management PC by double-clicking the
IN-VSN Enterprise Mgr icon on the desktop or using the Windows Start Menu.
For starting the IN-VSN server, no user login or password is required.
Chapter 5. Implementing the INRANGE FC/9000 Fibre Channel Director
585
Once the IN-VSN server is up and running, an IN-VSN server window should
appear with server running status, as shown in Figure 5-13.
Figure 5-13 IN-VSN server up and running
Another indicator of the running status is the permanent change of colors of the
text in the middle of the IN-VSN server window. Once the IN-VSN server is
running, you can then start multiple IN-VSN client sessions pointing to the
servers IP address or DNS name.
Starting IN-VSN client sessions
The following prerequisites must be fulfilled before being able to start an IN-VSN
client session:
 Have the IN-VSN client code installed.
 On the workstation running the IN-VSN client, have the appropriate Java
Virtual Machine installed.
 Have an IN-VSN server running locally or somewhere else in the network
 Have IP connection from IN-VSN client to IN-VSN server.
To start the IN-VSN client, just double-click the IN-VSN client icon on your
desktop or use the Windows Start menu.
586
IBM SAN Implementation
After starting the client, a login window will appear. Enter user name (default
admin) and password (default admin) as shown in Figure 5-14.
Figure 5-14 Starting an IN-VSN client session
Additionally, you will have to enter the IN-VSN server destination. This is where
the client software should find the IN-VSN server running. If the server is running
on a different machine, then enter the IP address of the IN-VSN server. If both
pieces of software run on the same machine, just select localhost.
Chapter 5. Implementing the INRANGE FC/9000 Fibre Channel Director
587
When logged into the IN-VSN server as the first client ever used, then all settings
are still default values and no specific fabric or director information is available at
all. This is shown in Figure 5-15.
Figure 5-15 Initial screen of an IN-VSN client session
Once you are logged in to an IN-VSN client session, you can then customize and
set up your fabric layout. These tasks include:






Definition of IN-VSN users
Setting up operational parameters
Defining fabrics
Mapping of directors
Naming of directors and ports
Creation of zones
These tasks are described in the following topics.
588
IBM SAN Implementation
5.2.7 Defining users
Different user-levels are provided by INRANGE. You can have multiple users with
different levels defined at a time. Default user names are the same as their level,
and are as shown in Table 5-1.
Table 5-1 User levels and default users
default user
default password
explanation
viewer
viewer
view and monitoring
oper
oper
operations like hard
zoning, naming or port
definitions
admin
admin
any zoning, naming,
definitions,
user-management
maint
won’t tell You
special user for customer
engineer (CE) access
These default users and passwords are, like other products, the same for all
IN-VSN servers. We strongly advise you to change them as soon as you start
with your fabric definition to avoid any unauthorized and unwanted access.
Chapter 5. Implementing the INRANGE FC/9000 Fibre Channel Director
589
Adding users
To enter the user definition screen, click the Users tab as shown in Figure 5-16.
Figure 5-16 Adding an IN-VSN user: Re-enter password
For security reasons, you will have to re-enter your password.
After re-entering the password, the current user definitions are displayed. Initially,
three users should appear as already saved:
 Admin
 Oper
 Viewer
590
IBM SAN Implementation
Click Add to enter the information for a new user as shown in Figure 5-17.
Figure 5-17 Adding an IN-VSN user: Overview
After clicking Add, the Details fields become active and you are able to enter the
data needed to create a new user. You can give all rights to this new user apart
from Maintenance level (maint).
Chapter 5. Implementing the INRANGE FC/9000 Fibre Channel Director
591
In Figure 5-18 we create a new user called itso_1 with admin rights.
Figure 5-18 Adding an IN-VSN user: Creating an admin user
Click Accept to add this newly created user into the list of already known users.
592
IBM SAN Implementation
However, this new user is not saved until you click Save, as shown in
Figure 5-19.
Figure 5-19 Adding an IN-VSN user: Saving new user configuration
You must take into account that the default users will not be deleted after adding
new users. This may be different to other products that you are familiar with. To
delete the default users, you can use the same procedure as for all other users.
How to delete users is described in the topic that follows.
Chapter 5. Implementing the INRANGE FC/9000 Fibre Channel Director
593
Deleting users
Deleting users is done using the same panel as we used for adding users. Note
that you cannot delete the user that you are logged in with.
To remove any user, select the victim in the list of already defined and saved
users. Click Delete and confirm this action as described in Figure 5-20.
Figure 5-20 Deleting an IN-VSN user: Confirmation
594
IBM SAN Implementation
Once you have confirmed this deletion, that particular user is deleted in the
IN-VSN database of the IN-VSN server. It is also removed immediately from the
user list of the IN-VSN client as shown in Figure 5-21.
Figure 5-21 Deleting an IN-VSN user: Updated user list
Changing user definitions
Once you have added users, you can change their attributes. All attributes,
excepting the name, can be changed. These are:
 Password
 User rights
 Description
Chapter 5. Implementing the INRANGE FC/9000 Fibre Channel Director
595
To change a user, first select it in the Users list. Once you have selected a user,
you are automatically in change mode. Change the desired settings and click
Accept as shown in Figure 5-22.
Figure 5-22 Change attributes of an existing IN-VSN user
We have changed the rights of user itso_2 from admin to operator.
After accepting the changes, this modified user will appear with updated status.
You can modify multiple users before actually making these changes effective by
clicking Save.
To be able to change all users, you must be logged in with admin rights. If you
are logged in with only operator rights, then only your own user’s password and
description can be modified. An operator is not allowed to change its own rights
(operator to admin, for example).
596
IBM SAN Implementation
5.2.8 Security considerations
As a SAN may store a great deal of sensitive and often confidential corporate
information, it might be interesting to consider some security issues, such as:
 User management
 Consequences of zoning methods
 Location access
We will describe these issues as they relate to the usage of the INRANGE
FC/9000 director.
User management
As described in 5.2.7, “Defining users” on page 589 INRANGE provides different
types of users.
User settings are saved in the IN-VSN servers database but not on the directors
themselves. To ensure the ability to recover from an IN-VSN server failure, we
advise you to use the Auto-Backup function. This backup setting is done using
the IN-VSN server interface as described in 5.3.1, “Setting up operational
parameters” on page 599.
You can have multiple users defined and also logged into the IN-VSN software at
the same time. Please be aware of these important issues:
 You cannot segment the fabric for different users. So an IN-VSN user always
has access to the whole fabric. It is not possible to limit the user’s access to
NT server ports or AIX ports only. The philosophy behind this is the same as
with Brocade or McDATA’s management tools. A SAN should be managed by
a dedicated storage manager, regardless of which server platforms are
attached to the SAN.
 Different users with the same level (for example, admin) can have access to
the fabric at the same time. This could result in chaos, since both active users
are allowed to make changes. Consequently, we recommend that only a
limited number of people have admin rights to the same fabric.
 The IN-VSN default users (admin, oper, view) are always the same globally,
including their passwords. Consequently, you should not consider them as
secure enough. Therefore, we advise you to delete them after you have
added your own users.
Chapter 5. Implementing the INRANGE FC/9000 Fibre Channel Director
597
Zoning methods
INRANGE provides both these types of zoning:
 Hard zoning
 Name server zoning (often called soft zoning)
Hard zoning makes it impossible to have I/O between different hard zones,
whereas with soft zoning, one port could easily be assigned to any other port in
the fabric.
However, both kinds of zoning are port related. It is the director’s port that is
referred to in both methods. At this time, a WWPN based zoning referring to the
attached server or storage ports is not available. This will become available in
the second half of 2001.
Both kinds of zoning are explained in 5.4.6, “Defining name server zones” on
page 644.
The consequences are different for tape and for disk attachments. Most disk
servers use LUN masking. This prevents the volumes from being used by
another server other than the assigned one. So in an FC/9000 and ESS
environment, unplugging the ESS cables from one zone and putting them into
another zone, it will not be possible to access the ESS volume from servers that
have not been associated with this storage.
However, this is different with tape. Tape drives normally do not support LUN
masking. Therefore, the only access control is provided by the zoning methods of
the director. Using the director-port based zoning concept, this tape drive could
potentially be accessed by other hosts just by changing the cabling.
To limit the physical access to the director, consider some of these possibilities:
 Use the INRANGE cabinet with locked doors to prevent access to the cabling.
 Also limit the access to any patch panels used in your SAN infrastructure.
 Use access control methods for the datacenter facility.
Consequences of leaving the fabric unzoned
When the fabric with all directors and/or switches is in initial mode, then no name
server zone is defined at all.
By default, all ports are in one hard zone called the default zone. Note that you
always have to have all physical ports included in a hard zone. However, when
using only name server table based zoning, you can just leave the hard zone
setting as they are by default.
598
IBM SAN Implementation
When leaving the fabric without any name server zone, the only effective zone is
the all-inclusive hard zone. That means all ports are enabled to communicate
with every other port.
Be aware of this any-to-any connectivity when leaving the fabric unzoned.
Once you have added one name server zone, then the nodes, if they are part of
any zone, have limited access to the name server table.
Name server zone members can communicate with only those nodes that are
part of the same name server zone.
5.3 Management of an INRANGE SAN
To gain access to all the management functions, we logged in to IN-VSN as a
user with admin rights. In the topics that follow, we will explain how to:





Set up operational parameters
Connecting to an INRANGE fabric
Assign names
Define zones
Cascade directors and merge fabrics
5.3.1 Setting up operational parameters
In this topic we describe the parameter setup which can be performed without
having any directors known to the IN-VSN software:
 Manual database backup
 Automatic database backup
 Call Home and Page Home settings (CE’s responsibility)
Database backup
INRANGE provides the ability to backup all director related data to an external
disk. This is called database backup. You can use this backup to restore your
configuration data. Database backup settings are performed using the IN-VSN
server.
Chapter 5. Implementing the INRANGE FC/9000 Fibre Channel Director
599
We will first perform a manual backup. Therefore, we use the IN-VSN server
window to open the backup menu, as shown in Figure 5-23.
Figure 5-23 Manual backup of IN-VSN server: Step 1
Then we specify the name of our IN-VSN database file. We could leave the
default name had we wanted to. However, we choose to have our own specific
file named itso_db2.mdb, as shown in Figure 5-24.
Figure 5-24 Manual backup of IN-VSN server: Choosing the filename
To achieve a higher level of disaster recoverability, we recommend that you place
this database file on a mapped network drive, rather than use the management
PC. By doing this, you can recover from the total destruction of the management
PC. Another way of increasing recoverability is to perform periodic tape backups
using backup software such as Tivoli Storage Manager.
600
IBM SAN Implementation
The database file created by this manual backup could be used for IN-VSN
database restore. However, in real life it may be difficult to perform manual
backups periodically, since you need access to the IN-VSN server interface.
Therefore, it is possible to set up an automatic IN-VSN database backup.
We recommend that you utilize this function, as it saves time, increases our
recoverability, and does not rely on human memory to start the process.
The setup of autobackup is also done using the IN-VSN server interface. From
the configuration menu, select AutoBackUp as shown in Figure 5-25.
Figure 5-25 AutoBackUp settings: Step 1
In the Auto Backup Settings window, activate the AutoBackupUp field as shown
in Figure 5-26.
Figure 5-26 AutoBackUp settings: Enabling AutoBackUp
Again, we recommend placement of the backup file on a network device to
achieve higher recoverability. We have decided to implement a backup interval of
two hours instead of one hour as shown in Figure 5-27.
Chapter 5. Implementing the INRANGE FC/9000 Fibre Channel Director
601
Figure 5-27 AutoBackUp settings: Specifying Filename and backup interval
The IN-VSN server main window then displays “Auto Backup Enabled” status.
Setting up page home/call home
In some environments it may be useful to have INRANGE or IBM automatically
contacted via telephone or pager by the IN-VSN server. This is called Page
Home or Inventory Update Call.
However these parameters should be set up by IBM or INRANGE Customer
Engineers only.
An example of Inventory Update Call parameters is shown in Figure 5-28.
Figure 5-28 Inventory Update Call parameters
602
IBM SAN Implementation
5.3.2 Connecting to an INRANGE fabric
A fabric is made up of one or multiple INRANGE directors and or switches which
are linked via Inter Switch Links (ISLs). Directors that are not linked via ISL are
considered as different fabrics.
Initially, the IN-VSN software is not aware of any fabric components at all, as
shown in Figure 5-29
Figure 5-29 IN-VSN fabric tool without any fabric known to it
To make a specific fabric known to the IN-VSN software, click Add. Then enter
all the required fabric information into the fabric details fields:
 We will call the fabric osvl_fc64.
 We do not give any description at this time.
 Our directors’ IP addresses are 9.113.20.67 and 9.113.20.89.
For each director in the fabric, you must use a dedicated row in the Director IP
Addresses field. In our case, we have one director, and therefore only one row.
After entering all fabric information, we clicked Accept as shown in Figure 5-30.
Chapter 5. Implementing the INRANGE FC/9000 Fibre Channel Director
603
Figure 5-30 IN-VSN: Connecting to a new fabric
It is not necessary that the directors specified with their IP addresses be actually
online or connected at the time of the fabric creation. The actual IP connectivity
to these directors is obtained every time you click the specific Fabric tab in the
IN-VSN client interface.
Furthermore, at the time of fabric creation, it is not checked if the specified
directors are actually connected via ISL or not. Again, this will be obtained when
clicking the specific fabric.
Once the director is actually online and IP connected it will appear by clicking the
fabric icon as shown in Figure 5-31.
604
IBM SAN Implementation
Figure 5-31 IN-VSN: Initial fabric view
The default name of this director is FC64.
If you had multiple directors in one fabric, they would appear as multiple symbols
in the fabric view.
5.3.3 Assigning names and aliases
Our fabric consists of one director with 64 ports. We want to attach four Hewlett
Packard (HP) servers and one Enterprise Storage Server (ESS) to this director.
Using the IN-VSN tool, we are able to assign names to physical director ports
and to the director itself.
The assignment of names is not a requirement. However, we advise doing it
because it will make our zoning and fabric management tasks much easier. This
is especially true in larger environments with multiple directors.
Chapter 5. Implementing the INRANGE FC/9000 Fibre Channel Director
605
To simplify further usage of this environment, we decided to use the names as
shown in Table 5-2.
Table 5-2 Director and port names
Director component
Name to assign
Physical port of director
FC/9000 director
osvl_fc64
N/A
first port for D class server
osplsun2_td0
54
second port for D class
server
osplsun2_td1
55
first port for L class server
(HP1)
osplhp1_a
57
second port for L class
server (HP1)
osplhp1_b
58
first port for L class server
(GEODE)
geode_td0
60
first port for K class server
hewlett_td0
63
second port for K class
server
hewlett_td1
62
ESS Bay1 Port4
ospl5b1p4
40
ESS Bay4 Port4
ospl5b4p4
48
These names belong to the physical ports of the director and not to the ports of
attached devices.
Consequently, when changing the cabling of the director, you should also ensure
that any change to the cable layout reflects the changes, and therefore the
current environment.
606
IBM SAN Implementation
Assigning the directors name
To assign the directors name we enter the director view by clicking the specific
director in the Navigation explorer of the IN-VSN tool as shown in Figure 5-32.
Figure 5-32 IN-VSN: Director view
We enter the new name osvl_fc64 in the Name field in the director view. Click
Apply and confirm this action to make the change effective as shown in
Figure 5-33.
Figure 5-33 IN-VSN: Changing the directors name
Chapter 5. Implementing the INRANGE FC/9000 Fibre Channel Director
607
Assigning port names
To assign names to individual FC ports of our director, we click the specific
director in the IN-VSN navigation tree to have the director view displayed. Then
we click the Ports tab to have a list of all 64 ports. This is shown in Figure 5-34.
Figure 5-34 IN-VSN: Director view with all ports
This list displays all 64 physical ports of our director with their attributes, such as:




Default names
Status: whether you have signal light (Online) or not (Offline)
Device: World Wide Node Name (WWNN) of the attached device or server
Zones which the ports belong to
We can use this list to enter the new names in the Name column, as shown in
Figure 5-35.
608
IBM SAN Implementation
Figure 5-35 IN-VSN: Changing port names
We start with the two ports used for ESS attachment. Therefore, we change the
name of port 40 to ospl5b1p4 and port 48 to ospl5b4p4. Click Apply and confirm
this action to make the new names effective.
Note: Take into account that all the port names you have assigned refer to the
physical port of an INRANGE director. These names are technically
independent of any attached external ports.
However, we advise you to use port names that indicate which external ports
are actually attached or will be attached in the future. The port names can
later on be used for zoning purposes. In case of zoning, using a meaningful
port name will simplify the setup of zones. This is especially true for fabrics
that span multiple director and switch chassis.
Then we repeat this procedure for all remaining server ports.
Chapter 5. Implementing the INRANGE FC/9000 Fibre Channel Director
609
We have now physically attached all server ports and the two ESS ports. That is
why we now have Device information (WWNN) displayed in the port list.
Figure 5-36 shows a port list with all of our desired name changes active and
with the WWNN information displayed for the attached ports.
Figure 5-36 IN-VSN: Director’s updated port view
Once the new names are effective they will be used throughout the whole
IN-VSN fabric management, including zoning, FIO-blade monitoring and name
services.
5.3.4 Setting the director clock
All directors will be delivered with preset time and date settings. However, in
most cases, these clock settings do not match with the local ones.
These clock settings do not affect the fabric functionality at all. However it is
important to set them because this makes reading and understanding the
time-stamped logs much easier.
610
IBM SAN Implementation
To set the director clock, just click the specific director in the navigation tree and
then choose Set Director Clock from the Director menu, as illustrated in
Figure 5-37.
Figure 5-37 IN-VSN: Selecting the director clock menu
Chapter 5. Implementing the INRANGE FC/9000 Fibre Channel Director
611
Enter your desired time settings and apply this by clicking OK as shown in
Figure 5-38.
Figure 5-38 IN-VSN: Setting the director clock
5.3.5 Attaching loop ports
Today, the storage and server industry is moving rapidly towards switched
fabrics. However, there are still a lot of systems that use Loop protocol. For
instance, most tape devices use FC-AL, as well as lots of legacy FC host
adapters.
Of course, some of them could be upgraded or replaced by newer devices to
support native fabric login. However, for financial reasons it might be more
attractive to protect these investments. This can be done using the FC-AL
support features in an INRANGE fabric.
This topic covers:







612
Enabling loop attachment for a specific director port
Enabling loop attachment for the entire director
Disabling loop devices
Understanding differences between private loop and public loop
Using Translative Loop ports to let private loop ports talk to the fabric
Setting up private targets
Setting up private initiators
IBM SAN Implementation
Note: To read the following topics, it is useful to understand the differences
between terms like director port, loop port, loop devices, initiators, targets:
 A director port is an actual physical port of the FC/9000 director.
 Loop ports are the external ports attached to a director port. Loop ports use
loop protocols like private loop or public loop. They are sometimes referred
as loop devices or loop nodes.
 Initiators are ports that actually control the IO flow and give commands.
Typically initiators are FC host adapter ports.
 Targets are ports that get commands. Normally targets are storage devices
such as tape drives or disk arrays.
 Loop devices running public loop are referred as NL-ports.
Enabling loop attachments
To make loop node attachment possible, we have to enable the director ports to
autosense loop devices. We have two ways to make these settings:
 Enable Arbitrated Loop Auto Sense for the entire director
 Enable Arbitrated Loop Auto Sense for a specific director port
Enabling loop attachments for a specific director port
First we will allow loop attachment for the port called hewlett_td0.
In the IN-VSN navigation tree, we select FIO-8, then the specific port named
hewlett_tdo. In the port view we leave the General tab in the foreground.
Here we activate the Auto Sense Arbitrated Loop Enabled field as illustrated in
Figure 5-39.
Chapter 5. Implementing the INRANGE FC/9000 Fibre Channel Director
613
Figure 5-39 IN-VSN: Port View to enable port specific loop attachment
Once the Auto Sense field is activated in the port view, click Apply and confirm
this action to make this change effective, as shown in Figure 5-40.
614
IBM SAN Implementation
Figure 5-40 IN-VSN: Confirming the enabling of loop attachment
Now we are able to use loop attachments on this port. In our case, we have a
Hewlett Packard Tachyon Lite Adapter set to Public Loop. The actual adapter
settings are displayed in Figure 5-41.
Figure 5-41 IN-VSN: FC adapter set to public loop
Chapter 5. Implementing the INRANGE FC/9000 Fibre Channel Director
615
This adapter is set to Public Loop as shown in the Topology row.
By selecting the Loop Devices tab in the IN-VSN port view, we can ensure that
the director actually recognizes this loop attachment as shown in Figure 5-42.
Figure 5-42 IN-VSN: Port Loop Devices View
Enabling loop attachment for the entire director
Instead of individually enabling loop attachment for lots of specific ports, you can
enable this for the entire director as well. This means that all director ports will be
set to Auto Sense Arbitrated Loop.
616
IBM SAN Implementation
To enable all ports to attach loop devices, select the specific director in the
navigation tree of IN-VSN and click Auto Sense Arbitrated Loop Enable in the
Director menu, as shown in Figure 5-43.
Figure 5-43 IN-VSN: Enabling Auto Sense Arbitrated Loop for the entire director
Be aware that this change could interrupt in-progress I/O on ports. Therefore,
use this procedure only if you are sure about the consequences of the warning
given in the confirmation window, as illustrated in Figure 5-44.
Figure 5-44 IN-VSN: Confirming loop enabling for the entire director
Loop ports in a name server table
Once you have a port enabled to sense Arbitrated Loop ports and there is
actually a loop port attached, then you can verify that it has been recognized
correctly by reading the name server table.
Public loop ports are displayed as NL_Ports (Node Loop), whereas private loop
ports are displayed as TL_Ports (translative loop).
Chapter 5. Implementing the INRANGE FC/9000 Fibre Channel Director
617
We show a representation of this in Figure 5-45.
Figure 5-45 IN-VSN: loop port in name server table as NL_Port
Port hewlett_td0 was set to enable AutoSense AL and we actually attached this
port physically. After logging in, this port is displayed as an NL_Port, since this is
a public loop port.
Bypassing loop devices
In cases where you have multiple loop devices attached to one director port, you
can specify which devices should be actually used in the fabric.
618
IBM SAN Implementation
In our example, we have four loop devices attached to one director port. This is
shown in Figure 5-46.
Actually attached Loop Devices
device no: 1
Not in Bypass
device no: 2
Not in Bypass
device no: 3
Bypassed
device no: 4
Not in Bypass
Loop enabled director port
Loop Devices made available to the fabric
Figure 5-46 IN-VSN: Bypassing loop devices
We have decided that device 3 should not be seen in the fabric. To achieve this
kind of filtering, device 3 must be disabled and thereby set to Bypassed. In this
case, it means that a bypassed device is disabled from being used in the fabric.
This does not change the availability of the external Arbitrated Loop itself. For
instance, even if a bypassed device fails it might affect the other external loop
members as well. So, take into account that this kind of bypassing is just a way of
filtering but not necessarily an improvement of the availability.
To disable a particular device select it in the Loop Devices menu of the specific
director port. Click Disable to change its state to Bypassed.
Chapter 5. Implementing the INRANGE FC/9000 Fibre Channel Director
619
To enable a particular device, use the same menu and click Enable as shown in
Figure 5-47.
Figure 5-47 IN-VSN: Enabling and Disabling Loop devices
You should have at least one device per port left that is Not in Bypass. By default,
all attached loop devices are set to Not in Bypass.
Note: Not all loop devices support Bypass. In such cases, even after clicking
the Disable button, they will remain in Not in Bypass mode. That means such
devices are always enabled.
Differences between private loop and public loop
There are two kinds of Arbitrated Loop protocols: private loop and public loop.
For both kinds of loop ports, you have to enable the director ports to be able to
use them as we have described previously.
However, there are some important differences between private loop and public
loop, as discussed in the following topics.
620
IBM SAN Implementation
Private loop
Private loop is the most basic form of Fibre Channel. Private loops are generally
built using hubs, and communication is handled by passing messages around
the loop from one device to the next in order to gain control of the loop and to
communicate on it. Because each device is dependent upon the device next to it
for communication, private loops tend to be unstable.
For example, adding, removing, or even rebooting a device causes other devices
on the loop to pause. This pause forces every device to examine what changed
in the environment and to adjust for that change. This Loop Initialization Primitive
Sequence (LIP) can be extremely disruptive when data is being transferred at the
same time that a change of state takes place on an arbitrated loop.
In a controlled, stable, and consistent environment, private loop can perform
adequately for many applications. The main reason for its initial popularity is its
relative low cost. However, when performance, stability and management are
required, a higher performing Fibre Channel communication mode is necessary.
Importantly, a private loop is only known to itself. In some cases it is not possible,
unless some form of translation takes place, for a private device to see or be
seen by others.
Public loop
Public loop implies Fibre Channel arbitrated loop with hubs, switch or switches in
place. Public loop adds a number of key advantages over private:
 Name server — As described in the Fibre Channel standard, the addition of a
simple name server adds instant control and stability to a loop because each
device registers with the name server on login. The name server then takes
over the need to for devices to pause and pass messages to one another
each a time an event happens on the loop. The switch internally controls the
name server.
 Management — With a name server and switch management software,
devices on a switch can be queried, examined, and brought online and offline.
Errors can be logged and trapped with messages sent to an administrator
who can then take appropriate action.
 Zoning — With zoning, a SAN can be made more secure by separating and
segregating data and devices. Zoning can be done by individual switch ports,
using name server entries, or by each device’s unique world wide name
(WWN).
 Ability to address more than 126 Devices — In a loop only configuration, it is
possible to address a maximum of 126 devices, not including the initiator.
Through connection to a fabric, that range can be increased. This is in
comparison to a private loop's 8-bit address which limit a fabrics size.
Chapter 5. Implementing the INRANGE FC/9000 Fibre Channel Director
621
Usage of public loop and private loop
Since these two loop modes inherit different protocol methods, there are
differences in the actual usage of them with the INRANGE IN-VSN tool.
Usage of public loop
You can attach public loop initiators or targets without any additional settings,
provided that the director port is set to enable AL.
However, attaching a public loop port does not automatically mean that this port
can talk to any other ports in the fabric. This port will be recognized as an
NL_Port and can be zoned in the same way as normal N_Ports can be zoned.
An example of the recognition of a public loop port as an NL_Port in the Name
Service Table of a director is shown in Figure 5-48.
Figure 5-48 IN-VSN: Name server table with NL_Port
622
IBM SAN Implementation
Usage of private loop ports
Normally, private loop ports are not able to talk with other ports outside of their
own loop. Therefore, their addressing is different from normal ports. However,
with the Translative Loop mode of specific director ports, it is possible to let them
talk with other ports in the fabric.
To enable this you have to set the Admin Type of this particular director port to TL
as shown in Figure 5-49.
Figure 5-49 IN-VSN: Setting a port to Translative Loop mode
Each TL port has its own Translation Entries list. This list contains the set of
off-loop devices which can communicate with this TL port. Off-loop devices can
be:
 Any other N-port in the fabric (initiators or targets)
 Any other public loop port in the fabric (NL_Port)
 Any other private loop port in the fabric (TL_Port)
Chapter 5. Implementing the INRANGE FC/9000 Fibre Channel Director
623
The creation and maintenance of this list is different between private targets and
private initiators. Therefore, you have to specify whether a particular TL_Port has
private targets or a private initiator attached to it. Click the TL-CFG button to
open the TL Config window as shown in Figure 5-50.
Figure 5-50 IN-VSN: Selecting target or initiator mode for TL ports
Select Private Target if you have targets attached to this TL_Port which should
be accessed by other private initiators — for instance, private loop JBODs
accessed by another private initiator.
Select Private Initiator if you have private loop initiators attached, such as
elderly FC host adapters. Also, select this option if you want a private target
device on this TL_Port to get accessed by a public initiator.
624
IBM SAN Implementation
Note: The selection of Private Target or Private Initiator for a TL_Port does not
necessarily mean that you have such types attached to it.
The private target option is only useful if a private initiator should access this
particular target port.
If a public initiator should get access to this private target you should actually
set this private target to Private Initiator. Then you should proceed to specify
the WWN of the Public initiator that should have explicit access to this private
target.
In such a scenario, the Private Initiator label for the radio button may be
misleading.
The translation entries list for private target TL_Ports contains all initiators that try
to get access to these targets. An Auto Learning feature enables this translation
entries list to be updated automatically. That is why, for private targets, you
cannot specify any WWNs in the TL-CFG window. However, you should limit the
actual number of initiators trying to communicate with this TL_Port to a maximum
of 31.
An Auto Learning feature for TL_Ports attached to private initiators is not
available. All devices that this private initiator has to communicate with must be
added to the list manually. Once you have selected Private Initiator in the
TL-CFG window, some additional buttons become active. Click Add from List to
add devices that are currently known to the fabric, as illustrated in Figure 5-51.
Chapter 5. Implementing the INRANGE FC/9000 Fibre Channel Director
625
Figure 5-51 IN-VSN: adding possible targets
If you want to add device addresses that are currently not attached to the fabric,
then you can add them by typing in their WWN. Click the Add button and enter
the WWN as shown in Figure 5-52.
Figure 5-52 IN-VSN: Adding WWN targets
626
IBM SAN Implementation
Each TL_Port has its own translation entries list, as shown in Figure 5-53.
Public target: port B
Privat target: port A
Translation entries list:
(Auto Learning)
Node inititiator: port C
- port E
Public inititiator: port D
TL-Port1
FL-Port2
F-Port3
FL-Port4
Privat inititiator: port E
TL-Port5
Zoning in fabric:
(C,B)
(D,B)
= zone_1
= zone_2
Translation entries list:
(specified)
- port A
- port B
Figure 5-53 Translation Entries List with zoning
Only TL_Ports have translation entries lists, in our case port1 and port5.
The list of port5 (initiator) was manually created by adding the WWN of portA and
portB. It means that port5 with its attached portE could have access to the ports
A and B. Since TL-Cfg settings overrule name server zone settings, we do not
need to zone these ports.
Furthermore, portD has access to portB. This is not implemented through a
translation entries list, but by using zoning. Since portD is not a private loop port,
there is no list for this port anyway.
The list for portA is automatically created using the auto learning feature. Once
the initiator portE has actually logged in to portA, then portE will be added to the
list.
Chapter 5. Implementing the INRANGE FC/9000 Fibre Channel Director
627
Note: Even if the translation entries table for private target ports is updated
automatically, you will not see its content. The auto learning feature is always
used in the background. You cannot deactivate it or activate it.
TL_Ports and zoning
Once the translation entries list is created, these TL_Ports can actually talk to
other ports in the fabric.
But the question remains: How does this TL_Port configuration interact with
name server zoning, or with hard zoning?
First, TL_Port configurations cannot cross the boundaries of hard zoning.
Second, name server zoning does not have an impact on TL_Port
communication at all:
 Private Target TL_Ports propagate all their translative device addresses to
the fabric. However, they can just be used by other Private Initiators. To
enable communication between them the TL-CFG list of this private initiator
must include the address of the private target.
 Private initiator devices have only access to devices specified in their TL-CFG
list.
 Even if a TL port is part of a name server zone, it will not see the members of
this name server zone unless they are put into the TL-CFG list.
 On the other hand, the TL-CFG list of a TL_Port is effective even if the name
server layout would imply it otherwise.
Note that this feature of name server zones is limited to TL_Ports only. Normal
public loop ports will be handled as normal director ports with all the normal
consequences of name server zoning.
Impact of LIP in the fabric
Ports in loop networks use a process called Loop Initialization Primitive
sequence (LIP) to establish their port addresses. All members of that loop are
involved in a LIP.
Loop initialization occurs whenever there is a change in the layout of a loop, such
as adding a new node, leaving of a node, or breaks in service in the loop.
The start of a LIP causes data transfers in progress to stop, thereby severely
affecting the performance and availability of Arbitrated Loops.
628
IBM SAN Implementation
However, since INRANGE is using a Translation Entries List, these LIPs will not
be propagated to other fabric members. This is true even if multiple private loop
ports are zoned together. Therefore, all LIP impact is limited only to the external
physical loop (for example, an FC_AL hub).
This feature is a major benefit of using TL_Ports.
5.4 INRANGE zoning
One of the basic purposes of SAN fabric products is to enable or disable
communication between the different ports (devices) attached to them.
In most cases it is helpful to limit the potential access of ports. Zoning provides
an effective tool to limit and control the communication between fabric ports.
There are multiple possible reasons to limit access and include:
 We may want to avoid Windows servers seeing all disks in a fabric. Otherwise
there would be a high risk of getting signatures written on all disks which
would then mean these disks are unusable by other operating systems.
 For security reasons we want to limit the access to disk with confidential data
to only selected servers.
 We would like to get control of the amount of paths a FC host adapter has to a
specific disk. This is because not all environments are flexible in their usage
of multipathing software.
INRANGE provides three kinds of zoning methods:
 Hard zoning
 Name server zoning
 Broadcast zoning
5.4.1 Understanding INRANGE hard zoning
Hard zoning follows physical boundaries within a single-stage switch chassis,
and limits the communication of a port to only other ports in the same hard zone.
Hard zoning, in certain circumstances, is the only way to provide the required
additional level of security, but careful consideration should be applied prior to
activating any hard zones, as it may be possible to isolate devices.
Chapter 5. Implementing the INRANGE FC/9000 Fibre Channel Director
629
 By no means is it possible to have communication over the boundaries of
hard zones. This is also true if malfunctioning fabric initiators try to get around
the name server tables.
 Hard zones take precedence over all other kinds of zoning (for example, over
broadcast and name server zoning).
 If no hard zone is enabled at all then all ports are considered as being part of
one large default hard zone.
 Name server zones and broadcast zones can be implemented within hard
zones. If so, they further limit the connectivity between members of a hard
zone.
 Hard zones can be created spanning multiple directors in one fabric.
Hard zoning rules
There are a number of rules that must be followed to implement hard zoning
successfully:
 You can define a maximum of 16 hard zones in an INRANGE fabric,
independently of how many chassis are used in the fabric.
 When a hard zone is created, it must be in a granularity of four ports.
 There is a fixed segmentation of a director into port groups which each have
four ports. These port groups will be used when setting up hard zones.
 A single director port can only be part of just one hard zone. It cannot be a
part of two hard zones at the same time.
 An all-or-nothing rule applies to hard zoning: Either all director ports are
members of any hard zones, or none of them are members of hard zones.
 Any update to hard zone layouts will cause all members of affected zones
to perform a fabric login. Hard zone changes should be restricted to initial
setup and at maintenance slots.
Fixed placement of port groups
As mentioned before, the granularity to set up hard zones are groups of four
ports. So one hard zone is built up of one or more multiples of these groups.
The location of these groups is fixed, and you cannot change this. A particular
group consists of four ports: two ports on a FIO blade and two ports with the
same location on a neighboring FIO blade as shown in Figure 5-54.
630
IBM SAN Implementation
FIO 1
FIO 2
FIO 3
FIO 4
FIO 5
FIO 6
FIO 7
FIO 8
group of 4 director ports
Inrange FC/9000 Director
Figure 5-54 INRANGE hard zoning: fixed location of port groups
The two ports of one FIO blade being part of such a group are called adjacent
ports.
The entire director is always automatically segmented into such groups.
Consequently, with a fully equipped 64 port director, 16 port groups are
automatically defined.
Chapter 5. Implementing the INRANGE FC/9000 Fibre Channel Director
631
Building hard zones using port groups
Now we know that a hard zone must consist of port groups. In our example, we
have created two hard zones, as illustrated in Figure 5-55.
Figure 5-55 INRANGE hard zoning: basic example with 2 zones
This picture was taken by using the IN-VSN tool.
Hard Zone A consists of only one port group. Hard Zone B consists of the
remaining 15 port groups. Remember the “all-or-nothing” rule: When
implementing hard zoning, all ports must be zoned.
In the example above, the four ports of Zone A are allowed to talk to each other.
All 60 ports of Zone B are allowed to talk to each other. However, any
communication between Zone A and Zone B is blocked.
Remember that hard zoning strictly excludes ports other than those in the same
hard zone from communicating together.
632
IBM SAN Implementation
When creating hard zones, all port groups in a particular hard zone must be
adjoining. In Figure 5-56 we show an example of an incorrect implementation.
Figure 5-56 Violating the adjoining rule
The upper port group of Hard Zone A has no adjoining contact to the remaining
two port groups of Hard Zone A. This is a violation of the hard zoning rules, and
therefore it is not possible to create a hard zone layout such as this.
5.4.2 Understanding INRANGE broadcast zoning
Broadcast zones focus the distribution of broadcast messages to only those
targets that need to receive them. This results in reduced fabric traffic and
eliminates unnecessary message processing. Broadcast zones can overlap and
are also assigned by director ports.
The granularity in which broadcast zones are built is one director port.
However, broadcast zoning is used for IP networking. Storage area networking
environments do not exploit this kind of zoning.
Chapter 5. Implementing the INRANGE FC/9000 Fibre Channel Director
633
5.4.3 Understanding INRANGE name server zoning
In contrast to hard zoning, there is no actual physical segmentation of fabrics with
name server zoning.
Instead, a name server table is used to implement that type of zoning.
Name server tables store information about nodes that have logged into the
fabric. Name server zones restrict the access of affected ports to this information.
All unzoned nodes have full access to the name server table.
This means that zoned ports logging into a fabric will only get name server table
information of other ports which are part of the same name server zone.
Unzoned ports are considered as being part of an orphan zone which is not
visible to users, but allows communication for all unzoned nodes.
Because this kind of zoning relies on the proper usage of FCP protocol
commands, it is also widely called soft zoning.
Name server zoning gives better flexibility then hard zoning:




A particular director port can be part of multiple name server zones.
The granularity of ports to build a name server zone is only one port.
Name server zone members need not be physically adjoining each other.
The change of name server zones does not enforce a port re-login of affected
ports.
However, since name server zoning relies on the correct usage of FCP
commands, there is still a risk that malfunctioning nodes would affect other ports
even if these other ports are not members of the same zone.
Due to its strength and flexibility, name server zoning is widely used in open
systems environment.
Name server zoning rules
There are rules that must be adhered to:
 INRANGE name server zoning refers to physical director ports. A type of
name server zoning pointing to WWNs of attached nodes will be available in
the future.
 Each name server zone needs to get a unique number and a name.
 As many as 256 zones are possible in a fabric.
 Name server zones cannot cross the boundaries of defined hard zones.
 Director ports which have private nodes attached to it need to be set to TL
mode. name server zoning is not effective for TL_Ports.
634
IBM SAN Implementation
5.4.4 Hard zones and name server zones together
Hard zoning can strictly separate port groups, and this can be seen as an
effective security feature.
Name server zoning allows us to further define the communication control on a
per port granularity.
When name server zones and hard zones are used in conjunction, we need to
consider the following principles:
 If you have no hard zone(s) created at all, then all director ports are
considered as being part of one big default hard zone.
 However, if at least one hard zone is implemented then this default hard zone
is not effective anymore. So, be aware of the fact, that if you add just one hard
zone all remaining ports must be added to a hard zone too. For instance you
could create a second hard zone containing all the remaining ports.
 Multiple name server zones can exist within one hard zone.
 Name server zones cannot cross the boundaries of hard zones
 Using INRANGE we do not have to worry about zone sets or active and
inactive zones. Creation of zone sets or creation of passive zones is not
possible in INRANGE environment. Either a zone exists and is thereby active,
or it does not exist.
 All nodes that are not part of any name server zone have unlimited access to
the name server table. This is also true if no name server zone is
implemented at all. Consequently, by default, all attached nodes have access
to the name server table. Only those nodes that are part of name server
zones will have limited access to this information
 The only exception is a TL_Port Config list which explicitly allows access to
the specified TL_Port even if name server zones exist that normally would
imply otherwise.
So, we can see that we have several different ways to control actual node access
with INRANGE:
 Hard zoning
 Name server zoning
 Translation Entries lists for TL_Ports
Chapter 5. Implementing the INRANGE FC/9000 Fibre Channel Director
635
The following rules are enforced with INRANGE directors:
 Both TL-CFG lists as well as name server zones cannot span hard zone
boundaries.
 You can use name server zoning to further limit access between nodes
 TL-CFG lists are for TL_Ports only. They overrule the name server principles.
So, TL_Port attached nodes can only communicate with ports specified in the
TL-CFG lists.
This hierarchy is shown in Figure 5-57.
INRANGE node access enforcements:
Hardzoning boundaries
Name Server Zoning
Translative Loop CFG lists
Figure 5-57 INRANGE access enforcements
636
IBM SAN Implementation
The scenario illustrated in Figure 5-58 describes a possible layout.
All director ports beeing part of any hard zone
Hard Zone A
Hard Zone B
Name Server Zone A_3
Name Server Zone A_1
Name Server Zone A_2
Figure 5-58 INRANGE fabric scenario with hard zoning and name server zoning
In this layout:
 All three defined name server zones are within Hard Zone A. They cannot
span over to Hard Zone B.
 Name server zone A_1 and A_2 are overlapping. Both have an ESS node as
a member.
 All members of name server zones can only access other members within the
same Name server zone.
 All remaining nodes in Hard Zone A which are not part of any name server
zone are part of the orphan zone. This allows communication between these
three nodes.
 There is no name server zone at all in Hard Zone B. All members can have
access to any other member in Hard Zone B since they are put into the
orphan zone. However, this orphan zone is limited to Hard Zone B.
Chapter 5. Implementing the INRANGE FC/9000 Fibre Channel Director
637
5.4.5 Defining hard zoning
In our example shown in Figure 5-59, we want to separate eight director ports for
usage by the finance department only. In no way should it be possible for anyone
else to gain access to their ports. That is why these eight director ports will be put
into one dedicated hard zone (the Finance hard zone).
Finance dept. IT systems
to be attached to the director
hardzone of 8 ports that are
dedicated for the Finance dept.
FIO 1
FIO 2
FIO 3
Other systems attached to the same director
hardzone of 56 ports are
dedicated for all remaining systems
FIO 4
FIO 5
FIO 6
FIO 7
FIO 8
Inrange FC/9000 Director
Figure 5-59 INRANGE hard zoning: Layout scenario
Considering the hard zoning rules that we have already discussed, we will place
all remaining ports into a second zone. This second zone can be used by all
other systems. Name server zoning is possible in both hard zones.
638
IBM SAN Implementation
To start our hard zoning setup, we first select the particular director in the
navigation tree and then click the Hard Zoning tab as shown in Figure 5-60.
Figure 5-60 IN-VSN: Selecting hard zoning in the director view
This window is used for all hard zoning configurations related to the selected
director.
This include actions such as:




Renaming a zone
Adding a zone
Deleting a zone
Change the zone layout
To create a specific hard zone, select one of the colored rows on the rightmost
side of this window and type in a name for this zone. This is illustrated in
Figure 5-61.
Chapter 5. Implementing the INRANGE FC/9000 Fibre Channel Director
639
Figure 5-61 IN-VSN: Specifying a name for a hard zone
We have chosen to name the first zone Finance. However, later on, we could
change the name again.
The remaining ports will be placed in a second zone, which we will call Other.
Note: The used color or number for a dedicated zone does not have any
effect on the actual behavior or performance. These numbers and colors are
solely used to simplify the organization and usage of hard zoning.
Hard zone colors, names or numbers are not visible in any way by attached
nodes.
To include eight ports as members in our first zone, Finance, we click the port
groups we want to use while the Finance zone is still marked in the rightmost
table.
640
IBM SAN Implementation
We have selected the two upper leftmost port groups to be part of hard zone
Finance as illustrated in Figure 5-62.
Figure 5-62 IN-VSN: two ports assigned to a hard zone
To test the integrity of our zone layout, we click the Test button. As you can see,
we got a Test Failed feedback.
This is because we violated a hard zoning rule: Either all ports of a fabric belong
to hard zones or none of them are hard zoned.
Consequently, we will place all remaining director ports in a second zone called
Other, as we have described before.
Chapter 5. Implementing the INRANGE FC/9000 Fibre Channel Director
641
Again we test this layout by clicking the Test button. This time everything looks
fine, as illustrated in Figure 5-63.
Figure 5-63 IN-VSN: Having two hard zones defined
We now have two zones defined: Finance and Other.
The Finance zone consists of two port groups giving a total port count of eight.
The Other zone has the remaining 14 port groups assigned to it having a total
port count of 56.
However, this hard zone setup is not yet active since we have not clicked the
Apply button at this stage.
To demonstrate the adjoining rule, we have added the bottom left port group to
the Finance hard zone.
Remember that the adjoining rule for hard zoning demands that all port groups of
one zone must be adjoining.
642
IBM SAN Implementation
As illustrated in Figure 5-64, when clicking the Test button now we get a violation
message, as expected.
Figure 5-64 Violation of ports
To successfully finish our hard zone setup as planned, we have put the bottom
left port group back into the Other zone.
Chapter 5. Implementing the INRANGE FC/9000 Fibre Channel Director
643
To activate our hard zone layout, we click Apply as illustrated in Figure 5-65.
Figure 5-65 IN-VSN: Applying a hard zone setup
As explained earlier, a director reconfiguration task such as this will affect
in-progress I/O. A warning message is issued to indicate this.
To activate our setup, we click Yes.
After this hard zone setup is activated, there is no communication possible
between the Finance zone and the Other zone.
This is the most secure way to separate nodes in a fabric environment.
5.4.6 Defining name server zones
Our goal is to enable all four HP servers to access the ESS.
To achieve a high level of availability, we have chosen to implement a
multipathing architecture except for one server (GEODE).
644
IBM SAN Implementation
All primary FC ports of these servers will be zoned to ESS Bay 1, Port 4,
and all secondary FC ports of these servers will be zoned to ESS Bay 4, Port 4.
We use pvlinks as multipathing software. Another possibility is to use the IBM
Subsystem Device Driver (SDD).
In Figure 5-66 we show an overview of what we will achieve.
Hewlett Packard servers running HP-UX 11.0
HP L Class 2000
HP L Class 2000
HP D Class 280
64
HP K Class 360
Inrange FC/9000
ShortWave fibre optics (50micron)
ESS 2105 - F20
Figure 5-66 Server setup for soft zoning
Be aware that such a zone-configuration is only advisable in specific
environments.
Be sure to have only host adapters of the same type in a zone. This is true in our
case. Therefore, we just implement two zones instead of dedicated zones for
each server.
Chapter 5. Implementing the INRANGE FC/9000 Fibre Channel Director
645
By implementing two zones, we limit the access of a particular host FC port to
only one ESS FC port. We do this because we like to have only two paths to a
ESS logical volume.
These two paths are created by giving the two host FC ports of one server
access to the particular ESS logical volume using ESS LUN masking.
In Figure 5-67 we show how these ports are physically attached to the INRANGE
director.
osplsun2
FIO 1
FIO 2
FIO 3
FIO 4
FIO 5
FIO 6
FIO 7
FIO 8
osplhp1
geode
hewlett
Inrange FC/9000 Director
ospl5b1p4 and ospl5b4p4
Figure 5-67 Physical cable connection for soft zoning setup
646
IBM SAN Implementation
We shall now explain how our zoning will look logically. As illustrated in
Figure 5-68, we plan to have two zones.
Director Port 54
=
osplsun2_td0
Director Port 55
=
osplsun2_td1
Director Port 57
=
osplhp1_a
Director Port 58
=
osplhp1_b
Director Port 60
=
geode_td1
Director Port 63
=
hewlett_td0
Director Port 62
=
hewlett_td1
Director Port 40
=
ospl5b1p4
Director Port 48
=
ospl5b4p4
ospl5_b4_zone
ospl5_b1_zone
Figure 5-68 Logical view of our two name server zones
Zone ospl5_b1_zone has four director ports as members, including the one ESS
port b1p4 is attached to.
Zone ospl5_b4_zone has 5 director ports as members, including the port that is
used to attach ESS port b4p4.
Chapter 5. Implementing the INRANGE FC/9000 Fibre Channel Director
647
By implementing such a layout, each server is attached to two zones. Since each
zone has a different ESS port as a member, the server will get exactly two paths
to the ESS. Use of pvlinks and ESS based LUN masking will enable sufficient
multipathing.
To actually implement name server zoning, click the specific fabric icon, in our
case osvl_fc64, in the navigation tree, and then select the Zoning tab as shown
in Figure 5-69.
Figure 5-69 IN-VSN: Entering the zone screen in fabric view mode
Initially, there are no zones defined at all. Remember that in such a case, the only
effective zone is the default zone. This enables all ports to communicate with all
other ports (any-to-any). Only zoned ports will have limited but controlled access.
All unzoned ports are considered as being part of the default orphan zone, which
enables them to communicate without any restrictions.
648
IBM SAN Implementation
Leave the Name Server Zone field selected. Click Add to create a new zone.
Enter zone number, zone name, and a description as illustrated in Figure 5-70.
Figure 5-70 IN-VSN: Entering number and name for a new zone
Chapter 5. Implementing the INRANGE FC/9000 Fibre Channel Director
649
From the Ports scroll list, select the ones you want to be a member of that zone
as shown in Figure 5-71.
Figure 5-71 IN-VSN: Selecting the members of a new zone
We added these ports to the zone ospl5_b1_zone:




osplsun2_tdo
osplhp1_a
ospl5b1p4
hewlett_tdo
The effect is that all these server ports will have access only to the ESS port
Bay1Port4.
650
IBM SAN Implementation
After putting all needed ports in the Ports in Zone list, we continue with clicking
Accept. This is shown in Figure 5-72.
Figure 5-72 IN-VSN: Accepting settings for first new zone
Chapter 5. Implementing the INRANGE FC/9000 Fibre Channel Director
651
However, now we are getting an error message, since our previously chosen
zone number of 0 is not valid. This is shown in Figure 5-73.
Figure 5-73 IN-VSN: Zone number 0 is not allowed to use
So we just change this zone number to 1, and click Accept again. Now this
action is accepted.
This zone is now listed in the zone list with a status of Added.
652
IBM SAN Implementation
To make this zone effective, click Save as shown in Figure 5-74.
Figure 5-74 IN-VSN: Saving a newly added zone
Using the same procedure, we now add a second zone called ospl5b4_zone
which has these ports as members:





ospl5b4p1
osplsun2_td1
hewlett_td1
geode_td1
osplhp1_b
Chapter 5. Implementing the INRANGE FC/9000 Fibre Channel Director
653
After saving this second zone, the zone list contains both zones with a status of
Saved as illustrated in Figure 5-75.
Figure 5-75 IN-VSN: Zone list with both zones added and saved
Another way to verify the right zone settings is to have a look at the Ports View of
the director.
654
IBM SAN Implementation
To do this, select the specific director in the navigation tree and then click the
Ports tab. After scrolling down we see the used ports with our given names, the
WWN of the attached ports, and then the zone these ports belong to as shown in
Figure 5-76.
Figure 5-76 IN-VSN: Director Port View showing the port to zone relationship
We now have two zones defined in a fabric consisting of one director.
Since both zones are saved and all specified external ports are actually attached
and online, we can start I/O between these servers and our ESS.
5.5 Cascading of directors
To further increase the amount of available FC ports, we can connect multiple
INRANGE directors using FC links. This kind of FC link will be automatically
discovered. This link is widely called an Inter-Switch Link (ISL).
The process of connecting directors using ISLs is known as cascading.
Chapter 5. Implementing the INRANGE FC/9000 Fibre Channel Director
655
The motivation to use cascaded directors is not limited to increased port counts.
Cascaded directors can be used to create a SAN that spans large distances.
Unique to INRANGE Directors, ports used for Inter Switch Links are called
T_Ports (Trunk ports). Every director port can be used for T_Port operation. No
manual setting is needed since ISL connections are automatically detected and
the affected ports are set to T_Port.
ISLs can be run on either ShortWave GBICs or LongWave GBICs. The usage of
LongWave GBICs enables the creation of long distance fabrics. The actual
supported distance between INRANGE directors can be further expanded by
using channel extenders or multiplexers.
Figure 5-77 shows an example where cascaded directors are used to allow host
based mirroring over long distances:
One fabric made up
of two cascaded directors
Two LongWave connections
used as InterSwitchLink (ISL)
Figure 5-77 One INRANGE fabric consisting of two cascaded directors
Cascading is a very effective and easy to use method to extend distances and
increase maximum port count. However we need to consider some of the
implications which are:
 By connecting multiple directors they will become one fabric inheriting all the
rules for one fabric, including:
– Name server zones are valid fabric-wide.
– Numbers and names of name server zones must be unique fabric-wide.
– Either all or none of the director ports in a fabric are hard zoned.
656
IBM SAN Implementation
– Each director or switch in a fabric must have a unique switch id.
– When having no zoning implemented at all then all nodes have access to
any other node fabric-wide.
 When actually using Inter Switch Links for I/O, there will be a delay called
latency. The actual usage of a ISL is commonly called a hop. Typically up to
three hops are supported for a particular I/O.
 T_Ports cannot be part of name server zones.
 When having hard zones installed that cross chassis boundaries, then both
parts of the hard zone must be directly connected by at least one ISL. You
must have dedicated ISLs for each hard zone spanning multiple chassis.
 Up to eight FC/9000 directors can be cascaded to create one fabric.
All directors and switches being part of one fabric will be displayed with their ISLs
when having the IN-VSN fabric view selected, as illustrated in Figure 5-78.
Figure 5-78 IN-VSN: Fabric view with two cascaded directors
Chapter 5. Implementing the INRANGE FC/9000 Fibre Channel Director
657
5.6 Monitoring and maintenance of an INRANGE SAN
This topic will briefly cover these topics:




Communication protocols to manage an INRANGE SAN
Microcode load information
Monitoring user activities
Using the INRANGE event log
5.6.1 Management communication protocols
Management communication can be done using different physical interfaces:
 Director:
– RS-232 Serial Interface
– Ethernet 10/100 Base T Connector
 Management PC:
–
–
–
–
Modem connectivity
RS-232 Serial Interface
Ethernet 10/100 Base T Connector to directors
Industry standard network interfaces to the corporate network
Using these physical interfaces the following management services can be used:
IN-VSN management software
Client/Server based management tool dedicated for users.
Maintenance interface using the RS-232 serial interface
Terminal based interface to change basic settings like director ID’s or IP settings.
This is dedicated for IBM or INRANGE Customer Engineers.
Simple network management protocol (SNMP)
An interface to integrate INRANGE directors into the corporate systems
management.
Trivial file transfer protocol (TFTP)
TFTP is used to load new firmware to directors and to retrieve and/or change
director management configuration settings (for example, IP, SNMP). This
service is dedicated to IBM or INRANGE Customer Engineers.
658
IBM SAN Implementation
Call home functionality
Call home enables the IN-VSN software to propagate event information and
configurations to INRANGE or IBM systems. This allows better response times in
case of component failures. Call home is disabled by default but can be enabled
by Customer Engineers. A modem connection for the Management PC is
required.
Changing the IP address
The IP settings of INRANGE directors should be done by IBM or INRANGE
Customer Engineers.
The change of the IP settings of an INRANGE FC/9000 director is performed
using a Terminal session via the RS232 Serial Interface.
Each FCM blade has its own IP settings and also its own Serial interface.
You should always keep both IP settings valid to ensure management access in
the event of FCM failures.
To change both addresses, you have to login to both FCM blades one after the
other. So, first you login to one FCM to set its IP settings and then you login to
the other FCM to change its IP settings.
The change process for IP settings involves a booting of the FCM. However this
local FCM boot process does not affect other director parts. Neither the alternate
FCM blade nor the director functions will be disturbed.
This results in a non-disruptive IP change.
5.6.2 Microcode-loads
Microcode-loads can be done non-disruptively using the IN-VSN Enterprise
Manager in conjunction with the TFTP interface. However, this action should be
performed by IBM or INRANGE customer engineers.
5.6.3 Monitoring user activities
IN-VSN management software allows to monitor user activities using an Audit
Trail.
All user levels (admin, oper, viewer) can access the audit trail.
Chapter 5. Implementing the INRANGE FC/9000 Fibre Channel Director
659
All activities are logged and categorized into different types. Following are some
examples of these operation types:






User login
IP address of user login
Fabric definition
User definitions
Name server zoning
Switch name changed
To look at the audit trail, click AuditTrail in the navigation tree as illustrated in
Figure 5-79.
Figure 5-79 IN-VSN: Using the INRANGE Audit-Trail to monitor user activities
660
IBM SAN Implementation
5.6.4 Using the IN-VSN event log
The event log contains all important events that have occurred. This includes
events triggered by users and events caused by other external or internal
influences, such as FRU failures or losing power.
To read the event log, click EventLog in the navigation tree of IN-VSN, as shown
in Figure 5-80.
Figure 5-80 IN-VSN: Accessing the INRANGE event log
This event log is valid for all fabrics managed by this IN-VSN server. It includes
the logs of multiple fabric devices and even multiple fabrics.
To file this log for future usage, you are able to export this log. Two file types can
be used to export the log:
 Comma Separated Value Files (*.csv)
 Text Files (*.txt)
Chapter 5. Implementing the INRANGE FC/9000 Fibre Channel Director
661
5.7 ESS configuration guidelines
In this chapter we have addressed some of more commonly encountered
features of the INRANGE director.
The 2042-001 is designed to provide maximum bandwidth switching from any
port in the system to any other port in the system. There is no mandatory
requirement for attachment of server or device ports to the 2042-001.
There are, however, a few guidelines to system configuration that should be
followed to assure optimum system reliability, availability and serviceability of the
overall SAN environment to which the 2042-001 is installed.
The foremost consideration is to spread critical resources across multiple
Director FRUs. The 2042-001 FRU in this instance is the eight port FI/O module.
Device ports should be distributed over as many director FI/Os as available.
Assignment of device ports to the FI/O is not critical and assignment to the same
port number across adjacent FI/Os for convenience is acceptable. When device
ports are allocated to the director, allocation of additional ports in the same
horizontal row should be considered for future expansion.
Channels from a common server or host image should be allocated over multiple
FI/Os in a manner similar to the way device ports are distributed over multiple
FI/Os as described above. In addition, when a server channel is daisy chained to
multiple devices by IOCP, the channel and device ports may be grouped on an
FI/O.
Critical system resources, such as SYSRES storage, may be assigned as device
and channel pairs to take advantage of port pairs on a FI/O that offer the greatest
autonomy of routing. These port pairs are ports 1&2, 3&4, 5&6, 7&8 on every
FI/O. Selection of these ports offers the highest availability in the most adverse
conditions.
662
IBM SAN Implementation
6
Chapter 6.
Implementing a SAN with
McDATA
Since the early 1990s, McDATA has provided IBM with fiber switches for the
S/390 world, the ESCON directors. They have built up experience in creating the
highly available and reliable equipment necessary to meet the demands of S/390
environment. Any SAN component needs to be as reliable and as available as
the large systems to which they are attached.
With the McDATA Enterprise Director ED-5000 (ED-5000) and its Fibre Channel
interface, McDATA has moved this proven technology towards the open market.
With open systems closing up on S/390 systems, choosing the McDATA switch
allows for enterprise class availability and performance that is usually found in
mission critical data centers.
Now, with their second generation director class FC switch, the 32-port and
16-port switches and the 9-port loop switch, these products are even more
prepared to fulfill the demands of a robust and scalable enterprise-wide SAN.
© Copyright IBM Corp. 2001
663
6.1 Introducing the McDATA products
Attention: Effective September 28, 2001, IBM will withdraw the McDATA
ED-5000 FC Director, IBM machine and model type 2032-001, and associated
field-installed features from marketing. In this redbook we will maintain our
description of it, as there is considerable overlap with the features in the
firmware of its replacement. Additionally, we anticipate that there will be a
number of installations that would still like information associated with the
ED-5000. For these reasons we will honor our commitment to the ED-5000.
After a short introduction of the FC product line and some considerations
regarding the network setup and remote management setup, we go on to
describe the McDATA SAN setup. We do not carry out every task, for example,
setting up for SNMP; nor do we describe every single step in its entirety.
However, we show how we built and managed our McDATA fabric in a
task-oriented way. We want to build a single switch fabric with one ESS and one
Windows NT server. Later on, we will extend the setup with more hosts, for
example, RS/6000. Once this is established, we will build zones and add other
switches to build a cascaded fabric. The hosts are already attached in our
environment and so is the ESS.In the following topics we introduce the McDATA
products that have been selected for inclusion in the IBM portfolio.
6.1.1 ED-6064 Fibre Channel Director
The ED-6064, shown in Figure 6-1, is the new second generation Fibre Channel
director from McDATA.
Figure 6-1 ED-6064
664
IBM SAN Implementation
With its 64 ports (minimum 32) and its high availability features, it is the flagship
of the McDATA product line. It aims at the highly available enterprise computing
environment, where every part of the infrastructure has to meet the same
demands of reliability, availability and serviceability. For instance, when
connecting highly available clustered servers like RS/6000 with HACMP to highly
available enterprise storage like the ESS, the connectivity layer should have
similar characteristics. This is even more important when the SAN is used to
connect many servers to storage. An outage of the SAN could lead to the loss of
access to data of all the connected servers.
Most components of the ED-6064 are hot pluggable field replaceable units
(FRU). It supports features like internal failover to redundant FRUs, and fault
detection. The maintenance firmware loads and the firmware activation can be
done without downtime and without any impact to connected devices. To notify
service personnel in case of a failure, a call-home and an e-mail notification
feature is provided.
Using the ED-6064 in the datacenter it serves as the core device of the backbone
of an enterprise wide SAN. Other McDATA switches, like the ES-3016 and
ES-3032, then serve as edge switches, or, for connectivity to FC-AL capable
devices, the ES-1000 can be attached.
The ED-6064 supports connectivity to S/390 with FICON and to open systems
with FCP. The ports are Generic Ports (G_Port). These ports, when connected to
another McDATA switch or director, act as Expansion Ports (E_Ports) to set up
inter switch links (ISL). Connected to hosts or storage devices, they act as fabric
ports (F_Port). Up to four ED 6064s, together with an 24 port ethernet hub and
the EFC server, can reside in the Fabricenter Equipment Cabinet.
The ED-6064 is managed and monitored through the Enterprise Fabric
Connectivity Manager (EFC Manager) which runs at the Enterprise Fabric
Connectivity Server (EFC Server). The EFC Manager server can be accessed
locally with the EFC Server or through an EFC Manager client installed on
another local or remote workstation. The EFC Manager serves as a central point
of control for up to 36 McDATA products. Also, some management can be done
through a browser pointed to the embedded Web server on the EFC server.
For in-depth information on the ED-6064, also see the McDATA ED-6064
manuals provided with the switch:




McDATA ED-6064 Director Planning Manual, 620-000106
McDATA ED-6064 Director User Manual, 620-000107
McDATA ED-6064 Director Installation and Service Manual, 620-000108)
McDATA ED-6064 Director Fabric Connectivity Manager User Manual,
620-005001
Chapter 6. Implementing a SAN with McDATA
665
6.1.2 ED-5000 Fibre Channel Director
The ED-5000, shown in Figure 6-2, is a Fibre Channel switch with a maximum of
32 ports.
Figure 6-2 ED-5000
Most parts of the switch are hot pluggable field replaceable units (FRU). The
design is geared towards high reliability and availability. The switch supports
features like internal failover to redundant FRUs, and fault detection. The
maintenance firmware loads and upgrades can be done without downtime and a
call-home feature is also provided. The Director is managed through the EFC
Manager which runs on the EFC Server. This PC is shipped as part of the
ED-5000 package.
For in-depth information on the McDATA, also see the McDATA ED-5000
manuals provided with the switch.
666
IBM SAN Implementation
6.1.3 ES-3032 and ES-3016 fabric switches
The ES-3032 and the ES-3016, shown in Figure 6-3, are 32 and 16 Port FC
switches that support FC switched fabric.
Figure 6-3 ES-3032 and ES-3016
They can be used to build up departmental SAN’s or SAN’s that do not need the
high availability of directors. Also, they could serve as edge switches connected
to a director serving at the core of the SAN backbone. The ports are G_Ports that
act as F_Ports when connected to FC nodes or as E_Ports if connected to
another switch.
The switches can be used as desk top units, or they can reside in the Fabricenter
Equipment Cabinet or a standard 19 inch rack. Both switches are managed
through the EFC Manager which runs on the EFC Server. Limited management
is also possible through the embedded web server.
Further information about the switches can be found in the manuals provided
with the switches.
Chapter 6. Implementing a SAN with McDATA
667
6.1.4 The ES-1000 loop switch
The ES-1000, shown in Figure 6-4, is a fabric loop switch.
Figure 6-4 ES-1000
The switch has eight FC-AL ports, which are called Hub Ports (H_Port) to
connect nodes in a loop, and one Bridge Port (B_Port) that is used to connect the
loop switch to other switches (although not other ES-1000s) or directors. This
means it allows for connectivity of FC-AL nodes to the McDATA SAN
This is, for example, necessary for FC tapes that only support FC-AL. Also,
connecting workgroups with less demand on the bandwidth at a lower cost is
possible with the ES-1000.
The ES-1000 can be used standalone, or rack mounted like the other McData
switches. The management is done, as with all the other McDATA FC devices,
through the EFC Manager or with the embedded web server.
Further information about the switches can be found in the manuals provided
with the switch.
668
IBM SAN Implementation
6.1.5 The Fabricenter equipment cabinet
The Fabricenter, shown in Figure 6-5, serves as the central management unit for
the McDATA SAN.
Figure 6-5 Fabricenter
It can take up to four ED-6064, as shown in Figure 6-6, or two ED-5000.
Chapter 6. Implementing a SAN with McDATA
669
Ethernet Hub
ED-6064 Director
EFC Server
ED-6064 Director
Figure 6-6 Fabricenter with four ED-6064
Additionally, the other switches, the ES-3016, ES-3032 and the ES-1000 can be
mounted in the Fabricenter. As well as housing the McDATA switches, the
cabinet also features the following:
 One optional 24 port 10/100 Base-T ethernet hub to connect the switches to
the EFC Server. It can also be used to connect to other cabinets and/or to the
LAN. Refer to “Setting up the network environment” on page 671, for further
information on the network setup.h
 One EFC Server, which is a laptop computer, running Windows NT 4.0 or
higher. It is mounted in a slide out tray in the middle of the cabinet. Up to three
cabinets can be managed with one EFC server, the second and the third
cabinet does not need to have its own EFC Server.
670
IBM SAN Implementation
 One 56 Kb/s modem for service and support of the managed products.
 One Zip drive mounted in the slide out tray. This is used to back up the
configuration information of the SAN. It comes only with cabinets that ship
with the EFC Server.
 Dual AC power strips and dual AC power inputs or redundancy. There is also
one central power switch for all in the cabinet installed components.
For further information on installation and service of the Fabricenter, refer to:
 Fabricenter Equipment Cabinet Installation and Service Manual, 620-000100
6.2 Setting up the environment
The installation of the cabinet with the switches and the EFC server is straight
forward. They ship with all the necessary components. After the physical
installation of the switches we perform the network setup and make sure we can
administer the devices remotely.
6.2.1 Setting up the network environment
First, we need to think about how we want to integrate the McDATA switches into
our network environment. Do we want the EFC server accessible through our
corporate intranet, or do we only want to access it locally? Second, do we want
to establish a dedicated network segment to connect the switches with the EFC
server, or do we want to connect the hub, that connects the switches with the
EFC Server, to the LAN as well?
Network setup with switches configured in the corporate LAN
We want to be able to reach the EFC server through the network, which is also
reachable from remote using IP, so we need to connect the EFC server to the
LAN. Also, we chose to install the McDATA switches in our laboratory network as
well. This configuration is shown in Figure 6-7.
Chapter 6. Implementing a SAN with McDATA
671
Corporate LAN
Ethernet
Ethernet
Ethernet Hub
primary
network
interface
Intranet
EFC Server
Loopswitch
Switch
Director
Remote
EFC Manager client
Cabinet
Figure 6-7 McDATA network setup with ethernet hub part of the LAN
This is achieved using the ethernet hub, which is supplied with the Fabricenter
equipment rack. We connect the EFC Server and the switches to the hub and
hook up the hub to the corporate LAN. The arrows indicate the route for the
remote EFC Manager client to access the EFC server. As we can see, the
McDATA supplied ethernet hub in the cabinet is now part of our LAN.
The switches and the EFC Server could also be connected to another ethernet
hub in the LAN, for instance when the corporate policy does not allow the
installation of more networking equipment. However, there is a possible security
issue when connecting the switches to the corporate LAN, with or without using
the McDATA supplied hub.
To set up the EFC server, we used the following network information:
 IP address: 9.113.25.247
The unique address of the EFC Server in the corporate intranet. We use it
with a Web browser to install the EFC manager on a remote workstation and
to access the EFC Server from the remote workstation.
672
IBM SAN Implementation
 Subnetmask: 255.255.254.0
Our intranet is divided into several subnets. The Subnetmask is used to
distinguish between the net part and the host part of the IP address. The host
needs this information to know how to treat the addresses it uses.
 Domain Name System (DNS) host name: EVT3
Numbers, for example, IP addresses, are sometimes difficult for people to
remember. Therefore, a service called the Domain Name System is used to
assign host names to IP addresses, and it makes the destination transparent
and reachable with an easy to remember host name.
 DNS domain name: sanjose.ibm.com
The name says that the DNS is using a hierarchy of domains for addressing.
The host name itself is not unique; to be able to reach the hosts given, we
need a fully qualified DNS host name which consists of the DNS host name
and the DNS domain it is in.
 Gateway address: 9.113.25.254
This is the default router which has to be known to the IP stack to route to a
destination outside the current LAN using IP.
The director needs to have following information too, to be accessible from the
management software.
For the ED-6064, this is for example:
 IP address: 9.113.25.246
 Subnet mask: 255.255.254.0
 Gateway address: 9.113.25.254
The network information for the ED-6064, ED-3016 and the ES-1000 is done
using a maintenance computer connected to the switch through the serial port.
Refer to the Installation and Service Manual of the switch on how to change the
network information.
To set the network information on an ED-5000, we would use the operator panel.
We can scroll though the information displayed on the panel with the Advance
button. To change specific information, we display it using this button. As we
want to change it, we click the Clear button to get a cursor in the entry field. With
the Detail button, we increment the value of the field we have activated. Clicking
the Clear button again gets us to the next field to change. If all entries are
correct, we use the Entry button to save the changes. This has to be done with
the IP address, the Subnetmask, and the Gateway address.
Chapter 6. Implementing a SAN with McDATA
673
Network setup with switches configured in a dedicated LAN
We suggest, for security and availability reasons, using the optional Ethernet hub
to establish a dedicated Ethernet to connect the EFC server with the switches.
This is illustrated in Figure 6-8.
Private
McDATA LAN
Intranet
Ethernet
Ethernet Hub
secondary
network
interface
Ethernet
Corporate LAN
Remote
EFC Manager client
EFC Server
primary
network
interface
Loopswitch
Switch
Director
Cabinet
Figure 6-8 Suggested McDATA network setup
The arrows indicate the route for the remote EFC Manager client to access the
EFC Server. As we can now see, the McDATA supplied hub is not part of the
corporate LAN. This solution could be used in environments where it is the
corporate policy not to attach additional network devices like hubs to the LAN.
The interface of the EFC Server that the corporate LAN is going to connect to,
has to be the primary interface and has to have a valid corporate network setup.
The secondary network interface does not have to be changed because it only
connects to the private ethernet hub. The network information for the first switch
does not need to be changed as well. Of course, when we add the other
switches, we will change the IP addresses for the new devices to be unique.
674
IBM SAN Implementation
6.2.2 Installing the EFC Manager client on remote workstations
We use the out-of-band management of the McDATA devices using the
corporate intranet. There are two access methods provided. This is the
management with the EFC Manager applications for all McDATA switches and
the management through the embedded web server of the ED-6064, ES-3032,
ES-3016 and the ES-1000.
Why we use the EFC Manager
The web interface does not allow every configuration to be made and also makes
only management of one device possible. Also, to use the web interface the
switch itself must have an IP connection to the computer from where we want to
access the web interface with the web browser, but this is not always what we
want.
We are going to use the EFC Manager to complete our tasks. For example, the
Web interface of the ED-6064 is shown in Figure 6-9.
Figure 6-9 Web interface of the ED-6064, unit view
Chapter 6. Implementing a SAN with McDATA
675
6.2.3 Introduction to the EFC Manager
The EFC Manager is a centralized tool for the McDATA network. It is a Java
based GUI that shows a graphical view of all managed devices and functions as
an entry point for all common management and monitoring tasks. The devices
are to be configured using the specific Product Managers and the fabric
configuration, such as the zoning configuration, is done from the Fabric Manager.
For detailed information about the EFC Manager and how to use it, refer to the
McDATA Enterprise Fabric Connectivity Manager User Manual.
The EFC manager is running correctly, but to use the EFC Manager from a
remote workstation we need to download and install the code on our workstation.
This can be a PC running Windows NT, an AIX, a Solaris, HP-UX or LINUX
workstation. In our case this will be a PC running Windows NT.
Accessing the EFC Manager client installation software
The code is downloaded from the EFC server. The download and installation of
the EFC Manager is done using a Web and Java based installation procedure.
All we need is a Web browser and we will use Netscape Navigator. In the
Uniform Resource Locator field (URL) of the Navigator we point to the address of
the EFC server, 9.113.25.247, to access the initial page on our EFC server.
This takes us to the start page for the remote EFC Manager client installation, as
shown in Figure 6-10, where we can choose the operating system of our remote
workstation.
676
IBM SAN Implementation
Figure 6-10 Start page for remote EFC Manager client installation
Chapter 6. Implementing a SAN with McDATA
677
Figure 6-11 Start page for remote EFC Manager client installation, continued
From here, we can also download the SNMP MIB files later on.
678
IBM SAN Implementation
Downloading and installing the EFC Manager client
We will install the EFC Manager client software on a Microsoft Windows NT
system so we select that option. After doing so, we are taken to the next Web
page to start the download and installation procedure. Immediately, we are
prompted to grant additional privileges to the Java based installation software.
First, we have to grant the right to start programs, and then grant the right to
read, modify, or delete files.
The button to start the download is covered until we grant the rights, as shown in
Figure 6-12.
Figure 6-12 EFC Manager client installation, granting additional rights
This warning message appears because, for security reasons, a Java applet is
not allowed to perform the tasks mentioned above. You should only allow Java
programs to perform like this from trusted sources.
Chapter 6. Implementing a SAN with McDATA
679
If we do not grant the additional privileges, we would have to download the
installer to our local workstation and execute it.
After granting the rights, the button to start the InstallAnywhere Web Installer
appears, and we are able to start the installation, as shown in Figure 6-13.
Figure 6-13 EFC Manager client installation, starting the installation
After clicking the button to start the installation process, the software starts
downloading to our local machine and begins the installation. The same
installation would begin after executing the installer named
mcdataClientInstall.exe.
680
IBM SAN Implementation
We now follow the instructions to install the EFC Manager client. After confirming
the licence agreement, we get information about which version we are going to
install, as shown in Figure 6-14.
Figure 6-14 EFC Manager client installation, EFC Manager version
The final step is to tell the installation program where to put the program files.
6.3 Managing the environment using the EFC Manager
In our environment, we have an ED-6064 and the EFC server installed; both
have valid IP addresses and are accessible through the corporate intranet.
The EFC Manager is used for fabric specific administration of the McDATA SAN.
Also the EFC Manager serves as the entry point to the programs for managing
the McDATA devices as well as the fabric that is built up using these devices.
The configuration programs needed for those tasks, the Product Managers, and
the Fabric Manager are accessed through the EFC Manager.
In the following topics we access the EFC Manager and perform some of the
administration tasks that have to be accomplished using the EFC Manager,
before we move on to the management of the devices and the fabric.
Chapter 6. Implementing a SAN with McDATA
681
6.3.1 Logging in to the EFC Manager
The following administration and configuration steps can be done locally from the
EFC Server or remotely using the workstation where we have just installed the
EFC Manager client code.
Logging in to the EFC Manager on the EFC Server
We logon to Windows NT on the EFC Server with the user ID, Administrator,
and the password, password, both of which are case sensitive. After logging on
to Windows NT, we get the login window for the Enterprise Fabric Connectivity
Manager (EFC Manager) which is installed and operational on the system.
To start the EFC Manager, we log on with the same user ID and password we
used when logging on to Windows NT, Administrator and password. We are
working locally on the EFC server and therefore we specify in the EFC Host
Server entry field localhost, which is shown in Figure 6-15.
Figure 6-15 Logging in to the EFC Manager on the EFC Server
682
IBM SAN Implementation
Remote login to the EFC Manager
After finishing the installation of our client workstation there will be a shortcut to
the EFC Manager on the desktop as shown in Figure 6-16.
Figure 6-16 EFC Manager icon on remote workstation
By double-clicking this icon, we get the login window for the EFC Manager. Now
we use the default username and password and the IP address of the EFC
server to login, as shown in Figure 6-17.
Figure 6-17 Remote login in to the EFC Manager
Chapter 6. Implementing a SAN with McDATA
683
6.3.2 Administering the SAN using the EFC Manager
After a successful login, we can move on to administer the McDATA SAN.
Following are examples of the options that we can configure using the EFC
Manager.
After logging on to the EFC Manager, it opens with the Product View shown in
Figure 6-18.
Figure 6-18 EFC Manager, Product View, no switches defined
To the left, there is a panel that allows us to perform various configuration and
monitoring tasks. The main window is empty because there are no devices
configured on the EFC Manager. The same applies to the Fabric View of the EFC
Manager. We can switch to it by using the View button on the panel as shown in
Figure 6-18.
684
IBM SAN Implementation
6.3.3 Defining users on the EFC Manager
First, we want to define users on the EFC Manager because we do not want the
Administrator user ID to be used remotely, so we will create a new user and use
that for remote access.
We can define up to 16 users for the EFC Manager but only a maximum of four
can log on concurrently. With the user of the EFC Manager running locally on the
EFC server there can be five sessions open concurrently.
To the left there is a panel from where we can access the different management
and monitoring functions.
From the Product View, we go to Configure -> Users...on the button panel on
the left side of the window as shown in Figure 6-19.
Figure 6-19 EFC Manager, Product View
Chapter 6. Implementing a SAN with McDATA
685
We are presented with a list of defined users and the options to add users,
modify existing users, view the rights of a user, and delete users. We will add
another user by clicking the New button and then specifying the name,
password, and description of the new user. Also, this window is used to specify
the rights that the new user should have. This is shown in Figure 6-20.
Figure 6-20 EFC Manager, Configure Users, New User
To assign rights to the user, we click one of the Rights Available choices and
click the Add button. The rights are:





686
System Administrator
Product Administrator
Operator
Maintenance
View
IBM SAN Implementation
The System Administrator right grants access to every control and configuration
task that needs to be performed from within the EFC Manager and can be
viewed as the highest level of authority. It only has ‘view’ rights while operating in
a product manager application. Here we need the Product Administrator right to
perform changes.
All new users initially have view rights and this cannot be removed. For a table of
user rights of product manager functions, refer to the Enterprise Fabric
Connectivity Manager User Manual.
To change the settings for a user, for instance, to change the password, we go to
Configure -> Users. With the Modify button, we are presented with a window
similar to the New window where we can change our password and the user
rights. This is shown in Figure 6-21.
Figure 6-21 EFC Manager, Configuring Users, Modify User
Chapter 6. Implementing a SAN with McDATA
687
Once the new user has been defined, we can login to the EFC server with the
newly created user ID and password.
6.3.4 Identifying devices to the EFC Manager
We have to identify the devices that are going to be configured and monitored
through this EFC Manager. Those devices then cannot be maintained with
another EFC Manager.
After logging on to the EFC server the Product View opens with no devices
installed as shown in Figure 6-22.
Figure 6-22 EFC Manager, Product View, no switches defined
688
IBM SAN Implementation
To identify the ED-6064 to the EFC Manager to be managed we need to tell the
EFC Manager the IP address of the ED-6064. This is accomplished by selecting
Configure -> New product..., as shown in Figure 6-23.
Figure 6-23 EFC Manager, New Product...
Selecting this takes us to the New Product entry field, where we have to fill in the
IP address of the director that we want to add. This is shown in Figure 6-24.
Figure 6-24 Defining new ED-6064 with its IP address
The ED-6064 was correctly installed in the network previously, and now the EFC
server can communicate with it. Therefore, the new director appears as an icon
in the left area of the main window, as shown in Figure 6-25.
Chapter 6. Implementing a SAN with McDATA
689
Figure 6-25 EFC Manager, Product View, new ED-6064 icon
We can also see the IP address of the ED-6064. A green circle indicates that the
switch is up and running with no known problems.
6.3.5 Assigning nicknames to World Wide Port Names
As with IP addresses and the DNS, life can be made easier by defining
nicknames for WWNs. The names can be the DNS host name in the case of
only one adapter in one host. If there are more adapters in one device, we
recommend that the nickname should consist of the hostname and some
extension to distinguish between both of them. This will help later when we have
to identify devices, for instance, when we set up zoning.
This is especially true because the ESS has Emulex adapters built in. We have
other Emulex adapters in our SAN so it would be useful to distinguish between
the ones in workstations and the ones found in the ESS. For the ESS we chose,
as an example RPKA93_C1B2A1. This means the ESS RPKA93 with the FC
port in Cluster one, Bay two, and Adapter one.
We use the information to include specific adapters in a zone. However, this is
not our only means of restricting access to volumes on the ESS.
On the ESS, every ESS logical volume is normally accessible through every FC
port. However, we can restrict the host FC ports that are configured in the ESS to
only see ESS logical volumes through specific ESS FC ports. This means that
those ports can only access the volumes assigned to it through those ESS FC
ports. We explain this in more detail in Chapter 2, “IBM TotalStorage
Enterprise Storage Server configuration” on page 75.
690
IBM SAN Implementation
Including ESS FC adapters within specific zones might be useful when we want
to influence the bandwidth that a specific group of host FC ports (members of a
zone) can get, and through which bay we want the data to go.
For our example, we configure a nickname for one RS/6000 and two for the ESS.
This is done by selecting Configure -> Nicknames..., which opens the window
without any nicknames configured. We use the Add button to add some
nicknames, as shown in Figure 6-26.
Figure 6-26 EFC Manager, Configure Nicknames, Add Nickname
Chapter 6. Implementing a SAN with McDATA
691
After adding some nicknames, the window looks like that shown in Figure 6-27.
Figure 6-27 EFC Manager, Configure Nicknames, nicknames assigned
Doing this is similar to using a hosts file on an IP host.
In our simple case, it might be tempting to work with the WWN and to skip or
ignore the task of assigning nicknames. However, as more devices attach,
maintaining the fabric with names is more convenient and will be easier than
figuring out which WWN belongs to which machine.
After assigning the nicknames, the Node List View of the Product Manager then
shows the names of those that are currently attached. With a growing SAN, it
becomes more and more important to be able to distinguish between the node
ports.
6.4 Managing the devices using the Product Manager
Now we can configure the devices for the McDATA SAN, the ED-6064, the
ED-5000, the ES-3016 and the ES-1000. The Product Manager provides
different options for every device type to be configured which reflect the specific
hardware and the configuration options that the devices provides. For instance,
the switch ES-3016 does not feature all of the high availability features of the
ED-6064 and the ES-1000 has to be configured for FC-AL only options. We only
configure options that are necessary for our SAN, for instance the operating
parameters. We do not cover administration tasks such as configuring SNMP.
692
IBM SAN Implementation
Also, the Product Manager presents the different front and back views of the
devices in the Hardware View. These are interactive views which display the
status of monitored units, for instance if they have failed. Additionally, clicking a
unit opens a window with more information about the unit.
6.4.1 Managing the ED-6064
We click the ED-6064 icon in the Product View to open the Product Manager.
Using the interactive Hardware View
This opens the Product Manager in its own window with the Hardware View, as
shown in Figure 6-28. This illustrates the different types of monitored interactive
parts as they show up when we move the mouse cursor over them.
Figure 6-28 Product Manager ED-6064, Hardware View
Chapter 6. Implementing a SAN with McDATA
693
At the top of the window we see the operational status of the switch itself. The
switch is fully operational and online. The Front View and the Rear View of the
unit show the installed components. The graphics representing the components
of the switch are interactive, which means by selecting them, we are able to view
more information, or to perform configuration or maintenance actions. They are
also monitored so that we have a graphical representation of the failed part in the
front and rear view.
Using the interactive port card view
As we can see, there are 8 port cards installed, which makes a total of 32 ports.
Clicking one of the port cards opens the Port Card View as shown in Figure 6-29.
Figure 6-29 Product Manager ED-6064 port card view and properties
694
IBM SAN Implementation
By moving the mouse over a specific port, we see its port number. By clicking it,
we get detailed port information and this is also shown in Figure 6-29. The port
we selected is used to connect to another switch to build an ISL, as we can see
because of the port type which is an E_Port. Also, we see the parameters that
are currently defined for this port and that the port is online. Using the right
mouse button on a port gives us a context menu as shown in Figure 6-30.
Figure 6-30 ED-6064 port card viewing and configuration options
Chapter 6. Implementing a SAN with McDATA
695
From here, we can perform actions on the port such as resetting the port or
performing diagnosis. To go back to the full Hardware View, we use the field
shown in Figure 6-31.
Figure 6-31 Product Manager ED-6064 back to hardware view
Configuring the director identification
There are fields for the name, description, location and a contact point for the
director in the main window. This is useful to distinguish among a number of
installed directors. This information is not yet configured.
To configure this information, we select Configure -> Identification..., and are
presented with a dialog window with data entry fields, as shown in Figure 6-32.
Figure 6-32 Product Manager ED-6064 Configure Identification
After activation, the display of the main window changes and places the name of
the director in the title bar, and the name, description and location displayed in
the window, as shown in Figure 6-33. This information is used in various
locations of the Product Manager to identify the selected director.
696
IBM SAN Implementation
Figure 6-33 ED-6064 Hardware View changed director information
Configuring the operating mode
The ED-6064 features the capability to change the operating mode. To configure
it, we select Configure -> Operating Mode... and get the Operating Mode
window as shown in Figure 6-34.
Figure 6-34 Product Manager ED-6064 Configure Operating Mode
Chapter 6. Implementing a SAN with McDATA
697
The mode can be set to Open Systems or to S/390. Setting this mode only
affects the operating mode used to manage the director but not its port operation.
This means that both FCP and FICON devices can communicate in each of the
two operating modes.
Note: The mode cannot be changed to Open Systems if the inband FICON
management server is enabled.
McDATA provides with the ED-6064 an Open Systems Interop Mode which can
also be activated using this window, shown in Figure 6-35.
Figure 6-35 Product Manager ED-6064 Configure Operating Mode Open Fabric
If the Interop Mode is configured for Open-Fabric 1.0, any open fabric compliant
switch can be connected. Those are then visible in the EFC Manager and the
Fabric Manager and can be zoned from within the Fabric Manager. However,
these switches cannot be managed through the Product Manager.
In this mode, McDATA Fabric 1.0, the connectivity is restricted to McDATA
switches. Connected non-McDATA switches will be marked as ‘Invalid
Attachment’.
Configuring the FC ports
To configure the options relating to each port, we select Configure -> Ports....
We are now presented with the Configuration Ports window which is shown in
Figure 6-36.
698
IBM SAN Implementation
Figure 6-36 Product Manager ED-6064 Configure Ports
The port number is automatically assigned and cannot be changed. We can
specify a port name here, but this is only useful if the cabling on the port does not
change that often. The port name then appears in the Product Manager to
identify the port, for example in the Port Properties dialog box.
Of more interest here is the ability to block specific ports, or to use extended
distance buffering when connecting remote sites with channel extenders, and to
define the port type. The ports are by default G_Ports, which means they behave
according to the node ports attached to them. For example, a G_Port will act as
an E_Port if connected to another switch port. We can specify here the port type,
as shown in Figure 6-37 so that certain ports can only be used as E_Ports for
ISLs or as F_Ports for connectivity to node ports.
Chapter 6. Implementing a SAN with McDATA
699
Figure 6-37 Product Manager ED-6064 Configure Ports port type
Also, link incident (LIN) alerts can be disabled here. A link incident is a problem
on a link which is visible in the Link Incident Log. It is indicated with a small
yellow triangle next to the port.
To view the LIN log, go to Logs -> Link Incident Log..., as shown in Figure 6-38.
Figure 6-38 Product Manager ED-6064 Link Incident Log
700
IBM SAN Implementation
Using the Port List View
To view all installed ports and their status in a tabular view and see the changes
that have been made, we use the Port List View, as shown in Figure 6-39.
Figure 6-39 Product Manager ED-6064, Port List View Port Properties
Configuring the FC operating parameters
To change the operating parameters, we first have to set the ED-6064 offline.
To set the director offline, which will terminate all FC operations, we select
Maintenance -> Set Online State..., which is shown in Figure 6-40.
Figure 6-40 Product Manager ED-6064 Set Online State
Chapter 6. Implementing a SAN with McDATA
701
Now we can go to the Configure Operating Parameters window by selecting
Configure -> Operating Parameters.... Here we can change some of the Fibre
Channel parameters for the director, for example, the preferred domain ID. This is
shown in Figure 6-41.
Figure 6-41 Product Manager ED-6064 Configure Operating Parameters
The BB_Credit of 60 enables the support for up to 100 km distance between two
ports. The R_A_TOV is a time-out value for operations that depend on the
maximum time that frames can be delayed and still be delivered. The E_D_TOV
defines the time that the director waits for a response before declaring an error
condition. Both time-out values must be the same for all switches in order to build
a multiswitch fabric.
The switch priority is used to define the principal switch in a multiswitch fabric.
The lower the number, the higher the priority. An important setting here is the
Preferred Domain ID. The domain ID has to be unique for each switch or director
within a multiswitch fabric. If we add a switch or director to our SAN, it will
retrieve the domain ID from the principal switch. If the domain ID that is preferred
is already in use by another switch, the switch will get another unused ID.
However, when two fabrics join and they recognize a domain ID conflict, the
fabric build process will fail.
If other switches or directors join the fabric, there will be a rerouting delay. This is
to ensure that frames are delivered in the correct order in a multiswitch fabric.
Also, the routes through the fabric will be recalculated to make sure that the
shortest path is taken first.
Now the director is ready for use in the Fibre Channel network. It can be
connected to devices, such as other switches, storage, or hosts.
702
IBM SAN Implementation
6.4.2 Configuring the ED-5000 with the Product Manager
Clicking an ED-5000 icon in the Product View opens the Product Manager.
Using the interactive Hardware and Port Card View
In the Hardware View shown in Figure 6-42 we are presented with the front and
back views of the director.
Figure 6-42 Product Manager ED-5000 Hardware View
Chapter 6. Implementing a SAN with McDATA
703
Again, the components of the director are interactive and monitored, as
illustrated. Also, as with the ED-6064 we have an interactive Port Card View,
which is accessed by clicking a port card. This view with the Port Properties
window of a specific port is shown in Figure 6-43.
Figure 6-43 Product Manager ED-5000, Port Card View Port Properties
The other options to configure — for example, the operating mode, the operating
parameters, and the ports — are the same as with the ED-6064, so you can refer
to 6.4.1, “Managing the ED-6064” on page 693 for information on how to
configure these.
704
IBM SAN Implementation
6.4.3 Managing the ES-3016
The Hardware View of the ES-3016 looks like that shown in Figure 6-44.
Figure 6-44 Product Manager ES-3016 Hardware View
The other options available to configure, for example the operating mode, the
operating parameters and the ports, are the same as with the ED-6064 and
ED-5000, so refer to 6.4.1, “Managing the ED-6064” on page 693 for information
on how to configure these.
6.4.4 Introduction to the ES-1000 Product Manager
In the topics that follow, we describe the major configuration options that are
necessary, covering those that are different from what we have already seen with
the ED-6064, ED-5000, and ES-3016.
Chapter 6. Implementing a SAN with McDATA
705
As with all the other Hardware Views of McDATA products, the Hardware View of
the ES-1000 loop switch features a Front View and a Rear View of the device.
Using the interactive Hardware View
This view is used to show the state of the monitored components of the switch
and can also be used to gather more information. As we can see, our switch has
four GBICs installed.
Figure 6-45 illustrates the different types of monitored parts of the switch that are
highlighted by the mouse cursor.
Figure 6-45 Product Manager ES-1000 Hardware View
As an example, for a switch with a failed fan, the Hardware View looks like that
shown in Figure 6-46.
706
IBM SAN Implementation
Figure 6-46 Product Manager ES-1000 Hardware View failed fan module
Configuring the FC ports
The ES-1000 features eight H_Ports and one B_Port. To configure the B_Port,
we select Configure -> Ports -> Bridge Port... and get the Configure Bridge
Port window shown in Figure 6-47.
Figure 6-47 Product Manager ED-1000 Configure Bridge Port
Chapter 6. Implementing a SAN with McDATA
707
Here the bridge port can be blocked and named, and the LIN alerts can be
disabled. We already know that the name will show up in the Product Manager to
identify the port. A blocked bridge port just disables the connectivity of anything
to the switch attached device to any fabric attached device.
To configure the hub ports, we select Configure -> Ports -> Hub Ports... and
get the Configure Hub Ports window shown in Figure 6-48.
Figure 6-48 Product Manager ED-1000 Configure Hub Ports
We can name the ports and we can disable LIN alerts here as well.
However, the hub ports have some more options to configure. The Bypassed
checkboxes have the same effect as the blocking of a port with other McDATA
products. A bypassed port is not part of the loop and an attached loop device
cannot communicate with other loop devices or other fabric attached node ports.
Port validation is used to verify that the port has serial technology and can
provide details about the port. The Auto LIP enables loop initialization every time
a loop device enters or leaves the loop. This is used to notify the other loop
devices and the switch of their presence.
Using the Port List View
To see the changes that have been made to the bridge and hub ports, we select
the Port List View (and open the Configure Hub Ports window for illustration) as
shown in Figure 6-49.
708
IBM SAN Implementation
Figure 6-49 Product Manager ED-6064 Port List View Port Properties
We do not have any devices attached to the switch, so no hub port is online at
this moment in time.
Configuring the FC operating parameters
Remember that the domain ID must be unique for each switch in a fabric, so we
will set the preferred domain ID to 4, which is unique in our fabric.
Chapter 6. Implementing a SAN with McDATA
709
To change the operating parameters, we first have to set the ED-1000 offline.
To set the switch offline, which will terminate all FC operations, we select
Maintenance -> Set Online State..., as shown in Figure 6-50.
Figure 6-50 Product Manager ED-1000 Set Online State
Now we can go on and configure the operating parameters by selecting
Configure -> Operating Parameters..., which takes us to the Configure
Operating Parameters window shown in Figure 6-51.
Figure 6-51 Product Manager ED-1000 Configure Operating Parameters
We have already discussed time-out values previously; however, here the
R_A_TOV applies to the bridge port only.
For the ES-1000, we can also change the loop mode the switch is in. In switched
mode, which is the default, the switch enables frame transmission through
multiple port pairs with full bandwidth. Also, if an unmanaged hub is installed, the
looplets that are created operate independently on their connected hub port. This
enables up to eight loops to communicate independently over the bridge port
connected fabric node ports.
710
IBM SAN Implementation
We can also change the behavior of the ES-1000 to act a normal FC-AL hub by
changing the mode to Shared as shown in Figure 6-52.
Figure 6-52 ED-1000 Configure Operating Parameters Loop Mode
This setting sacrifices the capabilities of the ES-1000, and should only be used
when connecting legacy devices which do not support switched mode
operations.
6.5 Understanding the McDATA zoning concepts
The advantage of a SAN, and the accessibility of any storage anywhere, raises
issues which must be solved. For example, do we really want any device to have
the ability to access all storage?
Zoning helps to split the SAN into logical parts by dividing a fabric into groups of
node ports. Members of a zone can only communicate with members in the
same zone through port to port connections.
For instance, zoning is used to separate groups of hosts with different operating
systems from each other to prevent data used by one operating system from
being corrupted by an accidental data transfer from another system.
Zoning is also used to separate part of the fabric for testing, or for separating
user groups for security and management reasons. Another use of zoning could
be the regulation of bandwidth by setting specific sets of node ports aside for use
by tape devices for example.
Chapter 6. Implementing a SAN with McDATA
711
6.5.1 Zoning implementation
There are different ways to implement the zoning for a fabric. One difference is
the enforcement of the zoning definitions. For instance, the enforcement is done
through the name server table and the access to this information about
connected node ports, or through additional frame flow control is enforced
through the route table in the switch.
Name server enforced zoning
McDATA uses name server zoning which is implemented by authorizing or
restricting access to name server information. The name server database on
McDATA switches contains pertinent information about the node ports logged in
to the switch. The main purpose of the name server is to provide this information
to attached node ports about the other node ports in the fabric. The attached
node port does not need to probe every destination for information. Instead it
logs in with the name server and requests information on attached node ports.
With name server zoning established, the port that asks for information will only
get back information about ports from within the same zone. This is also called
soft zoning because the name server enforces the zones but there is no control
of the real data flow.
Route table enforced zoning
In contrast to this, hardware enforced zoning restricts the frame flow to zone
members on a route table based in the switch hardware (ASIC). Route table
zoning is an additional layer of security to protect against node ports that do,
against the accepted methods of communication with switches, probe FC
addresses for information. Future microcode releases of McDATA products will
introduce route table zoning. The definition will be done from within the Fabric
Manager.
6.5.2 Zone member definitions
Zone members are specified either by the switch port numbers (and with it the
node ports connected to it), or by the WWPN of a node port. The WWNNs are
not used for zoning definition.
Zone member definition by WWPN
WWPN based zoning has the advantage that we can rearrange the node ports
on the switch ports without affecting the definition of the zones. This is important,
for instance, if spare ports of switches are used. In case of a switch port failure
the cabling can then be changed without redefining the zone.
712
IBM SAN Implementation
On the other hand, we have to change the zoning definition every time we
change a member in a zone, or if we have to replace an FC HBA or an FC
adapter of another FC node.
Note: The ESS can now be configured to administer the WWPNs of the ESS
FC ports locally, which means, they get WWPN based on the locations in the
ESS interface bays. So with zoning based on WWPNs, even in the case of the
replacement of an ESS FC adapter, the WWPN does not change and
therefore the zoning definitions do not have to be changed.
Zone member definition by switch port number
Switch port number based zoning consists of specifying the domain and the port
number of the switch. It requires us to change the zoning definition every time we
change the cabling to the node ports, but we can change to other node ports, or
exchange node ports without having to redefine the zone.
Mixing the two approaches
The two approaches to define FC node ports as zone members can be mixed.
Also, node ports specified by their WWPN or switch ports specified by their
number, can be members of more than one zone.
6.5.3 Zone management with zone sets
From within the McDATA Fabric Manager we can specify up to 64 zone sets. A
zone set is a group of zones that can be activated and deactivated at the same
time. Each zone set can contain a maximum of 1023 zones and each zone can
contain a maximum of 4096 members. Only one zone set can be active at one
time. Activating an inactive zone will inactivate the currently active zone set.
Node ports that are not configured in a zone within the active zone set are
considered as members of the default zone (this makes up for a maximum of
1024 active zones). The default zone can be disabled independently from the
active zone. Also, if no zone sets are activated all node ports are in the default
zone. If the default zone is disabled while no zone set is active, no node ports
can communicate. With the default zone enabled it is possible for all node ports
in the default zone to communicate with each other in parallel to the currently
active zone set.
Zone sets can be used to save different configurations for different tasks, for
example, if we want to have certain node ports in the same zone for backup, but
not during normal operation.
Chapter 6. Implementing a SAN with McDATA
713
Our zoning example
An example of how zones and zone sets are related is shown in Figure 6-53.
Amount of node ports
purple Default Zone
Active Zone Set:
ITSO_Zone_Set_1
Nonactive
Zone Set
Nonactive
Zone Set
blue AIX_Zone_1
red NT_Zone_1
one or more
ports of a node
Figure 6-53 Relationship of zone sets, zones, the default zone and node ports
The node symbols here (from servers and from the ESS), represent one or more
node ports and not necessarily the whole FC node with all ports. This is because
zones with McDATA are built up with node ports. For example, all three ESS
symbols could be ports of the same ESS.
714
IBM SAN Implementation
The solid (blue, red and purple) areas represent areas where traffic is permitted.
The blue and the red zone represent the AIX and the NT zone to be defined in
this topic. The green dotted line around the zones represents the active zone set.
The purple area is the default zone. In this example the default zone is enabled,
which makes it possible for all node ports, that are not configured in a zone of the
currently active zone set, to communicate with each other.
There might be cases where it is appropriate to disable the default zone. For
example, if for management and security reasons the only communicating node
ports are those that are explicitly allowed to. In this case, connecting node ports
without defining them to a zone would prevent them from accessing other ports.
6.6 Managing the fabric
To view and manage the zones in the McDATA fabric, we must open the EFC
Fabric Manager. The Fabric Manager is accessed by opening the Fabric View of
the EFC Manager with select View -> Fabric, as shown in Figure 6-54, and by
clicking the fabric icons (only one in our case).
Figure 6-54 EFC Manager Fabric View
There is a fabric icon displayed for each independent fabric and which consists
of devices managed by the EFC Server.
Chapter 6. Implementing a SAN with McDATA
715
6.6.1 Using the Fabric Manager views
The EFC Fabric Manager opens as a second window by selecting the Topology
View.
The Topology View
In our case we have one switch installed, and so there is only one switch visible,
as shown in Figure 6-55.
Figure 6-55 Fabric Manager, Topology View with one device
When switches become cascaded the topology view will then show the ISLs as a
line between the switches. We will see in 6.7.3, “Setting up our zoned multiswitch
fabric” on page 739 what this looks like.
The Zoning View
To change to the Zoning View we select the View button as shown in
Figure 6-55.
In Figure 6-56 we show the Zoning View of the Fabric Manager.
716
IBM SAN Implementation
Figure 6-56 Fabric Manager Zoning View no zone set active
The main window will display the active zone set, but at this moment in time,
there are no active zone sets. From here the active zone set can be deactivated,
or saved with another name. Also, we can see if the default zone is enabled or
not.
In the topics that follow, we show how to set up zoning in our environment. For
these tasks it is not important which view we are in.
6.6.2 Zones, zone sets, and zoning
We want to have one ESS and two Netfinity servers defined in a zone which is
shown in Figure 6-57.
Chapter 6. Implementing a SAN with McDATA
717
NT_Zone_1
Netfinity NT Server
ESS
Shortwave fiber
ED-6064
RS6K AIX server default zone
ESS - default zone
Figure 6-57 NT zone with two Netfinity node ports and one ESS node port
There are ESS ports and RS/6000 ports already connected to the switch, but no
Netfinity port. In our case we have only one FC adapter on each host so we only
have to add one port of each host to the zones.
Creating a new zone set
To create a new zone set we select Configure -> Zone Sets. This displays the
zone set library and provides us with options for changing our zone set
definitions, for example, creating new zone sets, deleting zone sets, or modifying
existing zone sets, as shown in Figure 6-58.
718
IBM SAN Implementation
Figure 6-58 Fabric Manager Zone Sets
Because there are no zone sets in the zone library, we will need to create one.
Starting from the Actions button in the Zone Sets window, we select New.
We are presented with a window to define a zone set. From this window we will
assign a zone set name. The Actions button provides us with the different tasks
to maintain the zones in this zone set, as shown in Figure 6-59.
Chapter 6. Implementing a SAN with McDATA
719
Figure 6-59 Fabric Manager Zone Sets and New Zone Set
Creating a new zone
Trying to save the zone set without any zones configured would cause the error
message shown in Figure 6-60. Therefore, we have to go on and create at least
one zone, and in our case, we will create our NT zone.
720
IBM SAN Implementation
Figure 6-60 Error saving empty zone set
So we will add some members to the zone.
Adding members to the zone
Using Actions -> New Zone opens a window where we can define the members
of the zone.
To the right of this window, as shown in Figure 6-61, we are presented with all of
the WWPNs or nicknames of the connected FC ports.
Figure 6-61 Fabric Manager New Zone
Chapter 6. Implementing a SAN with McDATA
721
To the left, we can view all the members currently defined for the zone. There are
two check boxes where we can choose if we want to assign a switch port and all
connected node ports to a zone, or if we want to specify the node ports based on
their WWPN. Here, the nicknames become important. Two Emulex WWPNs
belong to RS/6000 ports, and one to an ESS port. The Netfinity host ports we are
going to define in the zone are currently detached, so they do not show up.
In our example, we chose to add the two detached Netfinity ports and one ESS
port to a zone. Three ESS ports and three RS/6000 ports are already connected
to the switch. To assign one ESS port to the zone, we drag-and-drop the WWPN
associated with the ESS port to the left part of the window.
Adding members by domain and switch port number
We could also add attached or detached node ports to the zone by selecting the
Add by port number button and choosing the domain and switch port they are
connected to, or are going to be connected to. We now illustrate that we could
specify the members in one zone based on the WWPN, and other members
based on the switch port they are connected to, as shown in Figure 6-62.
Figure 6-62 Fabric Manager Add by port number
722
IBM SAN Implementation
Adding detached node ports to the zone
We also define the detached Netfinity host ports to the zone by using this
window. This can be done by specifying the WWPN of the ports and adding them
to the zone.
To perform this task, we use the Actions button and select Add Detached
Node. We get a data entry field where we insert the WWPN of the port, as shown
in Figure 6-63.
Figure 6-63 Fabric Manager Add Detached Node
They become instantly restricted to the zone in which we have defined them
when they are connected. We choose to specify the WWPN to define them to the
zone because we want them to be members of the zone regardless of which
switch port they are going to be connected to. This will also make it easier should
we need to rearrange the cabling at any stage or in the event of a failure.
Chapter 6. Implementing a SAN with McDATA
723
Saving the zone
While trying to save the zone using the Save Zone button, we got an error
message. This is because of the spaces in the zone name, as shown in
Figure 6-64.
Figure 6-64 Fabric Manager incorrect zone name
This is not allowed, so to circumvent this problem we changed it to NT_Zone_1.
After saving the zone, we return to the New Zone Set window where we can view
the zones in the zone library in the right half of the window.
724
IBM SAN Implementation
To view the zone members, highlight the zone in the zone library and then go to
Actions -> View Zone Members as shown in Figure 6-65.
Figure 6-65 Fabric Manager View Zone Members
Assigning the zone to a zone set and saving the zone set
To assign the newly created zone, NT_Zone_1, in the zone set we created
before, we will drag-and-drop the zone from the zone library to the Zones in Set
window on the left hand side of the window. This displays the zones assigned for
this set, as shown in Figure 6-66.
Chapter 6. Implementing a SAN with McDATA
725
Figure 6-66 Fabric Manager assigning zone to zone set
Now we save the zone set as a member in the Zone Set Library with the Save
Zone Set button. The Zone Set Library window now looks like Figure 6-67.
Figure 6-67 One zone set - one zone - three node ports
726
IBM SAN Implementation
We have one zone set (ITSO_Zone_Set_1) with one zone (NT_Zone_1). We
have one ESS port and two Netfinity host ports within the zone, one Netfinity port
with an Emulex adapter, and one with a QLogic adapter.
The ITSO_Zone_Set_1 zone set, with NT_Zone_1 zone, is now saved. However,
it is not active yet, but can be activated to make the fabric zoned. We can now
also define more zones in the zone set or create other zone sets. However the
zone set is not active.
Activating the zone set and making the fabric zoned
To finish our zoning example we will activate the zone set now. This is also done
using the Action button and by clicking Activate. With this action we are
prompted to start or to cancel the activation of the zone set with the Activate
Zone Set window. We Start it and receive a message that the activation is
complete, as shown in Figure 6-68.
Figure 6-68 Fabric Manager zone set activated
Viewing the active zoning configuration
After returning to the Zoning View window and expanding the zone set by clicking
the small symbol to the left of ITSO_Zone_Set_1, and then NT_Zone_1, the
Zoning View of our Fabric Manager looks like that shown in Figure 6-69.
Chapter 6. Implementing a SAN with McDATA
727
Figure 6-69 Fabric Manager Active Zone Set with one zone shown
We can see the zone set and the associated zone by its name and the
configured host ports by their manufacturer’s name and the host adapter port
associated WWPN. Also, we see the nickname for the ESS port which we
configured earlier. If we had not configured a nickname for the ESS port, we
would only see it as another Emulex adapter port as these are used as the Fibre
Channel adapters in the ESS.
Modifying zone sets
From within the Zoning View window we can also manipulate the zone sets, for
example, deactivating a zone set or saving the zone set. As an example, we will
copy the same zone set, but assign it a different name as shown in Figure 6-70,
and we will save it as ITSO_Zone_Set_2.
728
IBM SAN Implementation
Figure 6-70 Fabric Manager save active zone set as
6.6.3 Adding an AIX zone to the existing zone set
We also have AIX hosts, and we want to add a zone with the AIX systems and
another ESS, as shown in Figure 6-71.
NT_Zone_1
Netfinity NT Server
ESS
Shortwave fiber
ED-6064
AIX_Zone_1
RS6K AIX Server
ESS - default zone
Figure 6-71 NT zone with three node ports and AIX zone with four node ports
Chapter 6. Implementing a SAN with McDATA
729
The AIX hosts are already connected to the McDATA, so all we need to do is to
define the zone in the zone set which already includes our NT zone.
To add another zone to the zone set, we basically follow the steps described
previously. We navigate to the zone set library and mark the zone set in which
we want the zone to be added. In our case this is the ‘ITSO_Zone_Set_1’.
Then we use Modify... from the Actions menu, which allows us to change
the content of the zone set as shown in Figure 6-72.
Figure 6-72 Fabric Manager modify selected zone set
730
IBM SAN Implementation
From the Modify Zone Set window, we select Actions -> NewZone..., which
opens the New Zone window. We drag-and-drop the adapters of our AIX hosts to
the Members in zone window, as shown in Figure 6-73.
Figure 6-73 Fabric Manager defining an AIX zone
The last entry to the left of the window is another ESS but which is without a
nickname.
After selecting Save Zone, we assign this zone to our zone set. Just as we
did previously with the NT zone, we drag-and-drop the AIX zone in the Modify
Zone Set window from the Zone Library to the Zones in Set on the left-hand
side of the window, as shown in Figure 6-74.
Chapter 6. Implementing a SAN with McDATA
731
Figure 6-74 Adding AIX zone to zone set
After saving the zone set, we have two zones, NT_Zone_1 and AIX_Zone_1.
Both of these are in our zone set ITSO_Zone_Set_1 as shown in Figure 6-75.
Figure 6-75 Two zones in one zone set
732
IBM SAN Implementation
To apply the changes in the zone set, we must activate it by selecting
Actions -> Activate as shown in Figure 6-75.
By activating or deactivating this zone set, we activate or deactivate both
zones at the same time. After confirming that we want to start the activation
and clicking OK on the resulting message, we now have both zones active.
This is reflected in the Zoning View with an Active Zone Set, which looks like
that shown in Figure 6-76.
Figure 6-76 Fabric Manager with two zones shown
We have now successfully created and activated a zone set with two zones.
Chapter 6. Implementing a SAN with McDATA
733
6.7 Building a multiswitch fabric
The focus of McDATA is highly available connectivity in a data-centric approach
where the director was the core for connectivity of nodes. However, times
changed beginning with the E_Port capability of the McDATA G_Ports ED-5000.
Now, with their new core-to-edge product line of directors and switches, they
have paved the way to a more flexible distributed approach.
6.7.1 Multiswitch fabric considerations
The planning of multiswitch fabrics depends on many things. Are we going to
have a local SAN in one site with up to 64 node ports connected? Then we might
not consider cascading our switches. If we want to build a SAN to connect two
sites together, or if we want to have more ports in a single footprint, cascading
becomes a valued commodity. Also, if we want to extend the SAN to provide
departmental user groups with access to centralized storage devices or to
establish a centralized backup which does not affect the LAN, cascading
becomes a necessity.
Nevertheless, we still might think about whether or not, or to what extent, we
want to cascade switches. The reason for this is that by using E_Ports we will
sacrifice F_Ports. Also, with an extended fabric, the ISLs can possibly become a
bottleneck. This will lead to the use of more ISLs which means even fewer
F_Ports available for the attachment of devices. That which seems easy, in the
first instance, can get more complicated once we add the zoning concept, load
balancing, and any bandwidth issues that may appear.
Examples for multiswitch fabric solutions
There are many solutions which are only possible by using a multiswitch fabric.
For example, disaster tolerant solutions that are using a SAN can be built upon a
McDATA SAN but only when connecting two sites. We need switches at both
sites to back up one site completely.
Disaster tolerance and high availability of the host systems and the storage can
be established together using a multiswitch fabric, and open system hosts using
Logical Volume Manager (LVM) mirroring together with clustering software, such
as HACMP for AIX or Veritas Cluster Server. To further extend the availability two
footprints (parallel independent fabrics) could be used.
734
IBM SAN Implementation
Building upon the disaster tolerant and highly available approach, the SAN can
be extended to become a core-to-edge approach, especially if more hosts in the
company need access to the SAN — for example, for storage consolidation
where there is a need to provide access to distributed hosts to resources in the
data center. For hosts that do not need the RAS or bandwidth provided by
directors, the McDATA switches connected to the directors serve as connectivity
to the SAN backbone.
This is useful if a company wants to get rid of those hundreds of smaller
departmental servers (for example file servers). Disk consolidation which is
possible with a corporate-wide SAN can be seen as the first step for server
consolidation. Of course, just the connectivity of user groups to centralized disk
storage does not replace a file serving solution but with IBM NAS Gateways
which are dedicated file servers with Fibre Channel interface, more options
become available at both ends of the spectrum.
McDATA directors and the 16-port and 32-port switches do not support loop
devices directly, but by extending the fabric with the loop switch, this makes the
attachment of legacy loop only devices and loop only tapes possible.
6.7.2 Solutions for high availability and disaster tolerance
An example of a solution that provides high availability with disaster tolerance is
shown in Figure 6-77.
Chapter 6. Implementing a SAN with McDATA
735
local site
remote site
open systems server
open systems server
heartbeat
ED-6064
ED-6064
LW ISL's
ESS
ESS
Figure 6-77 LVM mirroring using the SAN
This is a setup which consists of the same configuration at both the local and the
remote site. Both sites can be up to 10 km apart when using 9 micron fiber-optic
cable. The open systems server cluster, for example, can consist of two or more
RS/6000 with HACMP. The mirroring can be done with the native LVM on AIX.
Another solution can be SUN servers running, for example, the Veritas Cluster
Server and the Veritas Volume Manager. Due to the high availability of the
McDATA ED-6064, one may be sufficient but only if that leaves enough ports to
accommodate the rest of the environment and its expansion.
When more ports and even higher availability are desired, this solution can be
extended with another director at each site. Even though a director is highly
available, using two independent fabrics (red and blue) removes the director
itself as an single point of failure and may not always be regarded as a paranoia.
736
IBM SAN Implementation
This is shown in Figure 6-78.
local site
remote site
open systems servers
open systems servers
heartbeat
ED-6064
ISL's
ED-6064
ISL's
ESS
ESS
Figure 6-78 Using two independent fabrics for high availability
The arrows indicate a possible route for the data to get to both parts of the
mirrored sets. In this setup there is no single point of failure at a device level, and
even if one site completely fails, the other site will take over operation
immediately.
In our example for a multiswitch fabric, shown in Figure 6-79, we are not focusing
on clustering. What we want to show is how to apply zoning in a multiswitch
fabric.
Chapter 6. Implementing a SAN with McDATA
737
ESS RPKA93_C1B2A1
NT Qlogic-20:00:00:E0:8B:00:52:5E
NT_Zone_1
NT Emulex-10:00:00:00:C9:20:CA:E6
ES-3016
local site
LW ISL's
remote site
ED-6064
ESS Emulex-10:00:00:00:C9:20:E7:F3
RS6K Emulex-10:00:00:00:C9:20:DC:71
RS6K Emulex-10:00:00:00:C9:20:E7:C7
RS6K - KATE_FCS0
AIX_Zone_1
Figure 6-79 Our zoned multiswitch fabric
Our NT zone spans over both sites, with two ESSs and two Netfinity’s. One ESS
is at the local site and the other is at the remote site. Both sites are connected
with three longwave ISLs between one ED-6064 and one ES-3016. At the
remote site are the AIXD zone with three AIX servers and one ESS that is also a
member of the NT zone. This example can be used to establish a mirrored set
from within the Windows NT Disk Administrator, with one local copy of the data
and one remote. Conversely, the AIX zone is limited to the devices at their site.
738
IBM SAN Implementation
Limits for McDATA multiswitch fabrics
The McDATA fabric supports up to 31 interconnected switches managed from
one EFC Server (the domain IDs range is from 1 to 31). Although we can
connect many switches, the hop count supported by McDATA is limited to three,
due to the delay that is applied traversing every switch. The hop count with
McDATA is equal to the number of ISL connections traversed between the
source and the destination.
Note: In IP networking a hop count means the number of connectivity devices
(for instance routers) in between the source and destination. This makes up
the difference of one more hop in IP networking than in FC networks with the
same amount if interconnect devices.
IBM supports with its McDATA products only a homogenous SAN environment.
This means that only McDATA switches are supported as switching elements in a
McDATA SAN.
6.7.3 Setting up our zoned multiswitch fabric
We will use one ED-6064 and one ES-3016 for our zoned cascading example.
We configure both switches as we did before. First, we define the director with its
EFC Server and then we define the switch to the same EFC Server and
configure it with the Product Manager. After defining the switch to the EFC
Server, the Product View now looks like that shown in Figure 6-80.
Figure 6-80 EFC Manager with two managed switches
Chapter 6. Implementing a SAN with McDATA
739
To include the second switch in the fabric of the first, we basically need to
connect the switches with longwave or shortwave Fibre Channel cables. The
fabric building process itself is transparent to us as the switches will recognize
the connection and automatically configure the G_Ports to be used as E_Ports.
However, there are some configuration options that need to be set up or
reviewed before connecting the switches.
Setting the switch priority
In every multiswitch fabric one switch has responsibility for the domain address
manager functionality. This principal switch controls the allocation and
distribution of the domain IDs for all connected switches in the fabric.
The principal switch is the one with the highest switch priority, ranging from 1
(highest priority) to 255 (lowest priority). If switches share the same value for the
priority the one with the WWN lowest numerical value becomes the principal
switch. To change the switch priority we also use the Configure Operating
Parameters window as shown in Figure 6-81.
Figure 6-81 EFC Manager, Configure, Configure Operating Parameters
Setting the domain ID
Each switch itself is recognized in the fabric as a domain and is identified with a
domain ID. Domains are used for the 24 bit FC addresses that identify the switch
ports in a fabric. Every domain ID in the fabric must be unique ranging from 1 to
31.
740
IBM SAN Implementation
To view and to change the domain ID we go to the Configure Operating
Parameters window from within the Product Manager of the specific switch. Then
we select Configure -> Operating Parameters.... In the next window as
previously seen in Figure 6-81, we can change the preferred domain ID and
other Fibre Channel parameters for the director, for instance, the Switch Priority.
The domain ID is requested from the principal switch once the switch becomes
online in the fabric. The preferred domain ID is only used if it does not exist in the
fabric. If it is in use already an unused ID is assigned.
We recommend setting the domain IDs prior to building the multiswitch fabric and
prior to zoning. One reason is that when two switches join they will determine if
there is a Domain ID conflict and if there is a conflict the fabric merging process
will fail.
The second reason is that the domain ID is used to identify switch ports when
zoning is implemented using the Domain and switch port number.
Configuring the ports for the ISLs
The ports for the ISLs can be configured just like the other ports as we described
in “Configuring the FC ports” on page 698. From here we can assign a name
reflecting the usage of the ports, check the checkbox for extended distance
buffering, and verify and change the port definitions. In our example, illustrated in
Figure 6-82, ports 0 and 1 are both able to build ISLs. Port one is already defined
as an E_Port and port 2 is a G_Port that will recognize that it has to act as an
E_Port.
Chapter 6. Implementing a SAN with McDATA
741
Figure 6-82 EFC Manager Configure Ports
Other prerequisites for a multiswitch fabric
To be able to successfully establish a multiswitch fabric other prerequisites apply.
The operating parameters, resource allocation time-out value (R_A_TOV) and
error detection time-out value (E_D_TOV) must be the same and the zoning
configuration must be compatible.
Verifying the compatibility of the zoning configuration
Once the switches are connected with ISLs the adjacent switches exchange their
zoning information and merge it to a single active zone set. This resulting zone
set now applies to every switch of the merged fabric.
Fabrics can be joined when none of them is zoned, when one of them is zoned or
when both of them are zoned. Not zoned means no zone set is active and the
default zone is enabled.
742
IBM SAN Implementation
1. If none of the fabrics are zoned, no zoning information will be exchanged and
the result will be a multiswitch fabric with no zoning.
2. If one of the fabrics is zoned, the active zone set will propagate across the
fabric and the result will be a multiswitch fabric with the zoning information of
the former standalone fabric which was zoned before.
3. If both of the fabrics are zoned, the zoning will only work if the configurations
are compatible. If the zone configurations are not compatible, the E_Ports of
the switches become segmented, which means they cannot carry traffic from
node ports, but they can still carry management traffic. Zoning configurations
are compatible if one of the two requirements are met:
– The active zone names of each fabric to be merged are unique, if the zone
members are not identical.
– The active zone names of each fabric to be merged can be identical, if the
zone members are identical as well.
In our case, the director fabric is zoned, the switch fabric is not. This means that
the active zoning information will propagate across the fabric and the two
independent fabrics will join to form a multiswitch fabric. Prior to connecting the
switches, the Fabric View of the EFC Manager looks like that shown in
Figure 6-83.
Figure 6-83 EFC Manager two independent fabrics
Here we have two independent fabrics which are not connected with ISLs.
Anyway, it would look the same if for instance the ISL’ ports would have been
blocked or would have been configured as an F_Port. Also, the zoning
configuration could be incompatible.
Chapter 6. Implementing a SAN with McDATA
743
Connecting the switches
Now we can connect the two switches with ISLs. We are using two longwave
ISLs between the two switches.
After successfully joining the fabrics, we select View -> Fabric in the EFC
Manager window. The fabric view now looks like that shown in Figure 6-84.
Figure 6-84 EFC Manager, Fabric View, one merged fabric
To see what the topology looks like now we navigate to the Topology View of the
Fabric Manager by clicking the icon that represents the merged fabric in the main
window, as shown in Figure 6-84. The number ‘2’ in the pentagon fabric icon
indicates that we have two switches merged into one fabric.
744
IBM SAN Implementation
Clicking this icon will open the Fabric Manager in a dedicated window with the
Topology View as shown in Figure 6-85.
Figure 6-85 Fabric Manager, Topology View, two switches defined and cascaded
Moving the mouse cursor over the link indicates that the connection of the two
switches consists of two ISLs. Clicking either icon will open the Product Manager
for the associated director. We can also change the description of the icon by
right-clicking the ISL as shown in Figure 6-86.
Figure 6-86 Fabric Manager changing icon text
Chapter 6. Implementing a SAN with McDATA
745
Currently we see the IP address displayed.
If the other connected switch was currently being accessed by means of another
EFC server, or it had not been defined to the EFC Server by its IP address, the
status will not be able to be determined by the our EFC Server. Therefore, the
Topology View would look like that shown in Figure 6-87.
Figure 6-87 Three switches cascaded, one not defined to the EFC Manager
We have put this only in for illustration reasons.
We now see a second ISL, but there is no green circle around the third switch.
This is because the EFC Manager is not able to retrieve any information about
the device. This device cannot be managed using the product manager.
746
IBM SAN Implementation
We disconnected the undefined switch and go back to the Port List View of the
cascaded switches as shown in Figure 6-88.
Figure 6-88 ED-6064 with one E_Port online
We now see that port 0 is online as an E_Port, which shows us that this is the
port that is used for our ISL. We also see the names we assigned to the ISL
ports. By clicking the row of a port, in this case port 0, it returns us detailed
information about this port. Port 1 is not yet used as an ISL port and we can see
that it is not online.
Chapter 6. Implementing a SAN with McDATA
747
After activating the zone set the Zoning View of the merged fabric now looks like
that shown in Figure 6-89. This shows the Active Zone Set of our fabric
corresponding to Figure 6-79 on page 738.
Figure 6-89 Active Zone Set corresponding to Figure 6-79 on page 738
We have now successfully completed all the steps necessary to cascade a
McDATA switches with zoning.
748
IBM SAN Implementation
7
Chapter 7.
Implementing the SAN Data
Gateway
In this chapter, we describe the steps involved in planning and implementing the
IBM Storage Area Network Data Gateway, 2108-G07. The SAN Data Gateway is
a hardware solution to allow connection of Fibre Channel ready host systems to
attach to SCSI storage systems.
© Copyright IBM Corp. 2001
749
7.1 SAN Data Gateway
The IBM Storage Area Network Data Gateway is an essential component of the
SAN infrastructure. It provides several benefits to bridge the legacy gap as
storage products migrate from SCSI based attachments to Fibre Channel.
A diagram to show a SAN Data Gateway configuration using a single host is
shown in Figure 7-1.
Server
Fibre
Channel
Gateway
SCSI
ESS
Figure 7-1 SAN Data Gateway configuration
The IBM Storage Area Network Data Gateway allows you to:
 Protect legacy storage equipment while utilizing the latest host servers with
Fibre Channel support
750
IBM SAN Implementation
 Expand connectivity to storage devices with use of IBM SAN hubs, switches,
and directors
 Perform channel zoning and LUN masking capability to allow access at a
volume level
 Overcome the distance limitations of SCSI based host systems using
longwave ports that support distances up to 10 km
 Utilize the StorWatch SAN Data Gateway Specialist which is an easy to use
interface for managing and controlling access of host systems to storage
devices
The SAN Data Gateway is available as a rack-mount unit or as a stand-alone
tabletop unit. The gateway model provides two shortwave Fibre Channel ports
and four Ultra SCSI Differential ports to attach disk or tape storage devices. One
or two Fibre Channel cards — dual-port, shortwave and/or single port, longwave
— may be added for a maximum of six shortwave ports, or two shortwave and
two longwave ports. If you are using the dual-port shortwave cards, Figure 7-2
depicts the port assignment numbers for the optical interfaces.
Figure 7-2 SAN connection port assignment
7.2 Installation
Before any server or device connection is made to the SAN Data Gateway, you
need to power on the unit and connect a service terminal to the 9-pin Service
port located on the rear right-hand side of the unit. A PC running a terminal
emulation program, such as Windows HyperTerminal or NETTERM, can be
used. The settings of the Service port are:






19200 baud
8 data bits
No parity
1 stop bit
X-on/X-off flow control
VT-100 compatible terminal
Chapter 7. Implementing the SAN Data Gateway
751
If a PC with terminal emulation is used, a 9-pin female to 9-pin female, null
modem cable is required and is provided with the unit.
Once connected, power on the SAN Data Gateway and the start up messages
will appear and scroll across the window. When the power on sequence has
completed, a prompt Gateway> appears on the window, as shown in
Figure 7-3.
Figure 7-3 IBM Storage Area Network Data Gateway startup
If you type in help and then press Enter, a list of available commands is
provided. The commands are case sensitive and must be entered as they
appear.
Issue the initializeBox command to remove any configurations files that
may be present. The unit will restart automatically.
Note: The initializeBox command will erase all configuration files. It should
be used only during initial SAN Data Gateway installation.
752
IBM SAN Implementation
7.2.1 Setting the Ethernet address
Once restarted, the Ethernet port must be configured and attached using
network information provided by the network administrator. To set the IP address,
use the ethAddrSet command. The address must contain the double quotes (“):
Gateway > ethAddrSet “9.111.24.66”
Network not Enabled
Write complete
Host Address set to 9.111.24.66 for Ethernet interface
value = 0 = 0x0
Gateway >
If a subnet is required then add it after the IP address and separate the two
addresses using a comma. For example:
Gateway > ethAddrSet “9.111.24.66”, “255.255.255.0”
If a gateway or standard router is to be specified, then issue the gateAddrGet
command to view if there is one set and the gateAddrSet command to set or
change it. For example:
Gateway > gateAddrGet
No current gateway address set
value = 0 = 0x0
Gateway > gateAddrSet “193.1.1.11”
Write complete
The Ethernet port on the SAN Data Gateway comes from the factory disabled. To
enable it, you must issue the ethEnable command. This will not take effect until
the unit is rebooted. The reboot can occur from a power off, or by issuing the
reboot command. During the reboot, you will see that the IP address is set and
now enabled.
Gateway > ethEnable
Write complete
Ethernet will be enabled on next boot
value = 0 = 0x0
Gateway > _
7.2.2 Using Telnet on the SAN Data Gateway
If a user would prefer to telnet to the SAN Data Gateway rather than by using the
service terminal port after initial setup, this can be done. First you must create a
user from the service terminal by using the userAdd command. Enter the login
name and password using the quotes and comma:
ITSO > userAdd “itso”, “residency”
value = 0 = 0x0
ITSO > _
Chapter 7. Implementing the SAN Data Gateway
753
You cannot telnet to the Gateway and use the service port at the same time.
When you telnet to the Gateway, the service port on the rear of the unit will stop
its communications. After you end the telnet session, then the service port will
become available again.
7.2.3 Startup sequence
You must start up the SAN Data Gateway and the attached host and target
devices in a specific order. When you add or remove SCSI devices or update
firmware, you must restart. The following procedures describe the situations and
order of procedure when you restart the SAN Data Gateway.
Before you restart the SAN Data Gateway, you must stop all input and output
(I/O) activity between the host and SCSI devices.
1. SCSI devices
Turn on the SCSI devices. You must turn on all SCSI devices attached to the
SAN Data Gateway before you initially turn on or restart the SAN Data
Gateway.
2. SAN Data Gateway
The SAN Data Gateway scans the SCSI buses when it starts. If you add or
remove SCSI devices after the Gateway has started, the Gateway will not
detect the changes. You can invoke an SCSI rescan or restart operation from
either the StorWatch SAN Data Gateway Specialist client or the service
terminal.
3. Fibre Channel host
Before you turn on or restart the hosts that are connected with Fibre Channel
to the SAN Data Gateway, you must wait until the SAN Data Gateway has
finished starting. You will know the Gateway has finished starting when the
ready light on the front panel blinks at frequency intervals of one second.
• Some operating systems provide you with software methods that allow
you to add or remove SCSI devices dynamically after the host has started.
To ensure reliable operation, restart the host.
• If you update SAN Data Gateway firmware, you must restart the Gateway
to use the new firmware. To ensure compatibility between the firmware
features or functions and the host, restart the host.
• If you update SCSI device firmware, the SAN Data Gateway Explorer
application does not display the new firmware version until the SAN Data
Gateway has issued an SCSI inquiry. The SCSI inquiry occurs when the
Gateway rescans the SCSI buses. The SCSI inquiry also occurs when the
StorWatch SAN Data Gateway Specialist client application or the service
terminal rescans the SCSI buses.
754
IBM SAN Implementation
Currently, up to eight different hosts can be attached to each Fibre Channel port.
If all six ports are installed, then 48 different hosts can attach to the SAN Data
Gateway.
7.3 StorWatch SAN Data Gateway Specialist
The StorWatch SAN Data Gateway Specialist software provides remote
capability for all management, configuration, and event notification. It is
comprised of three parts:
 Agent
 Server
 Client
Agent
The agent is embedded in the operating system of each SAN Data Gateway to
provide a stand-alone manageable host. The StorWatch SAN Data Gateway
Specialist software uses SNMP to set and retrieve information that controls the
operation of the Agent. The Specialist also uses SCSI over TCP to allow updates
to the Gateway and target device.
Server
The server is a Java application that runs on a host and is used to maintain
communication with the agents and acts as an intermediary between the agent
and the client. The server coordinates the request from multiple clients to
manage multiple gateways or agents. Multiple clients can share data the server
already knows about, and the server receives all traps from the agent and
forwards them to the clients that are registered to receive them.
Client
The client is a Java application that operates from any compatible computer as
long as it has a TCP/IP connection to the server. One or more clients can
connect to a server. The client provides the user interface to allow the
management and configuration of the SAN Data Gateway.
The server and client can be installed on to the same computer.
The StorWatch SAN Data Gateway Specialist supports the following operating
systems:
 Windows 95,98, 2000, and NT 4.0 with SP5 or later
 AIX ver 4.3.3 or later
 Solaris 2.6 or later
Chapter 7. Implementing the SAN Data Gateway
755
7.3.1 Installing StorWatch Specialist
The Specialist software is not bundled with the SAN Data Gateway. The
Specialist software is downloaded using a Web browser by going to the IBM
Storage Area Network Data Gateway Web site:
http://www.storage.ibm.com/hardsoft/products/sangateway/support/form1.htm
This will take you to a registration window. Enter the required information and
select Submit Information. A license agreement window is shown, and once
reviewed, select I agree. The Download Main Page window will load. Then select
the specific operating system platform. Review the readme.txt file for the latest
information and instructions, before installing.
This Web site also contains all the latest firmware for the SAN Data Gateway and
supported host bus adapters.
The StorWatch SAN Data Gateway Specialist software file is a self-extracting file.
Once it has been downloaded, execute or run the file and it will automatically
load onto your computer.
Starting the Specialist
To start the Specialist, the server must be started first, and then the client can be
launched. Figure 7-4 provides an example of the StorWatch SAN Data Gateway
Specialist with server and client loaded onto the same Windows NT computer.
Figure 7-4 StorWatch SAN Data Gateway Specialist startup
Once the server has been launched, you should see a window similar to
Figure 7-5.
756
IBM SAN Implementation
Figure 7-5 StorWatch SAN Data Gateway Specialist server
The client software can now be launched. If the server and client are not on the
same PC, then a dialog box will appear to allow you to enter in the IP address of
the computer that has the server software loaded. If the server and client are on
the same computer you will be automatically connected to this server. After
connection to the server is complete, a dialog box will appear, in which you can
enter in a user name and password.
The IBM Storage Area Network Data Gateway provides a default administrator:
 User Name: StorWatch
 Password: StorWatch
The fields are case sensitive, so they must be entered in as shown above.
A new administrator account should be set up by selecting Admin -> Add User
from the toolbar. After a new administrator account is created, then the default
user StorWatch is deactivated.
Note: If a new administrator account has been created, and the password is
lost, and no other account has administrator access, then you will have to
contact a service representative.
Chapter 7. Implementing the SAN Data Gateway
757
7.3.2 Using the StorWatch SAN Data Gateway Specialist
Once you are logged in to the Specialist, you must now connect to the SAN Data
Gateway. At this point, a dialog box should appear, requesting the IP address of
the SAN Data Gateway. As it connects, it will download the information from the
SAN Data Gateway and be presented on your window.
If a dialog box does not appear automatically, select Tools-> Connect SAN
Data Gateway or SAN Data Gateway Router from the toolbar. This can also
be used to connect to several Gateways or Routers from a single client session.
In Figure 7-6, we show the initial view once a connection to a SAN Data Gateway
is established and the data has been downloaded.
Figure 7-6 StorWatch SAN Data Gateway Specialist initial view
The left side of the window shows the SAN Data Gateway unit we are connected
to, and the right side provides product data information. You will also notice that
the toolbar will have options available that were previously greyed out. You can
now connect to another SAN Data Gateway, disconnect from a SAN Data
Gateway, enable and access the Zoning and VPS features, restart the Gateway,
and also refresh the data to your window by downloading it again.
These options become available when a SAN Data Gateway is highlighted. As
you begin to add SAN Data Gateway systems or drill-down into a particular
Gateway by selecting and highlighting different channels or ports, different
options will become available and other options will become greyed out and
unavailable. Be aware of what system, channel, or port is highlighted as you
move through the toolbar.
758
IBM SAN Implementation
As we can connect to several SAN Data Gateway systems from one client
session, select the particular Gateway you want and it will be highlighted in blue,
as shown in Figure 7-7.
Figure 7-7 Selecting from multiple SAN Data Gateways
On the left-hand side of the highlighted Gateway, there is a small key, and by
selecting this, it expands the view to show you all SCSI ports and installed Fibre
Channel ports. For example, Figure 7-8 shows a Gateway with four SCSI ports
and two Fibre Channel ports.
Figure 7-8 Expanded Gateway view
Chapter 7. Implementing the SAN Data Gateway
759
SCSI channels 1, 2, and 3 and Fibre Channel ports 1 and 4 also have a key on
the left-hand side to depict that there are devices attached. By selecting a key,
you will now expand the tree, as seen in Figure 7-9, and view the different disk
devices attached.
Figure 7-9 SCSI channel expanded view
760
IBM SAN Implementation
You can also select and highlight each SCSI Channel. You will notice that as you
do this, the information window on the right side will provide data that is unique to
that SCSI channel, as shown in Figure 7-10.
Figure 7-10 SCSI channel data
Chapter 7. Implementing the SAN Data Gateway
761
Information pertaining to a particular disk device is shown in Figure 7-11.
Figure 7-11 Disk device data
762
IBM SAN Implementation
You can perform the same drill-down on the Fibre Channel host as we did with
the SCSI channel and disk devices. Select one of the Fibre Channel port
connections, as shown in Figure 7-12, and its data will be shown on the
right-hand view pane.
Figure 7-12 Fibre Channel port data
By selecting the key to the left, you can expand the tree and select the host
system attached to that port. Figure 7-13 shows the detail on the specific host.
Chapter 7. Implementing the SAN Data Gateway
763
Figure 7-13 Fibre Channel host data
As you select and highlight the different ports or devices, there are different
options available from the top toolbar. If an SCSI channel is highlighted, select
Controls from the toolbar. You will notice that all options are grayed out except
for SCSI Channel. Once selected, a dialog box will appear, as shown in
Figure 7-14, and display the settings for the SCSI channel.
Figure 7-14 SCSI channel parameters
Selecting the Advanced Options button displays a dialog box, as shown in
Figure 7-15. These settings are not typically changed and may disrupt normal
operations, so you should consult a service representative before changing any
Advanced Options.
764
IBM SAN Implementation
Figure 7-15 Advanced SCSI parameters
Fibre Channel parameters are displayed in a similar fashion. Highlight a Fibre
Channel port and select Controls from the toolbar, you will notice that now all
options are grayed out except the Fibre Channel option. By selecting this, a
dialog box will display the parameters that can be changed for the Fibre Channel
port selected. If any of the settings, as shown in Figure 7-16, are changed, the
SAN Data Gateway must be restarted.
Figure 7-16 Fibre Channel port parameters
Chapter 7. Implementing the SAN Data Gateway
765
A detailed description of the SCSI and Fibre Channel settings can be found in the
IBM Storage Area Network Data Gateway Installation and User’s Guide,
SC26-7304.
7.3.3 Upgrading the firmware
New versions of the SAN Data Gateway firmware can be downloaded from
http://www.storage.ibm.com/hardsoft/products/sangateway/gatewayspec.htm
This site has a link to a Downloads section from where the latest versions of the
SAN Data Gateway can be downloaded. You will first have to complete a
registration form and then agree to the IBM Terms and Conditions.
Once you have completed this section, you will find a screen similar to that
shown below in Figure 7-17.
Figure 7-17 Downloading the SAN Data Gateway firmware
766
IBM SAN Implementation
From this screen, we selected the Windows NT version, and we will save this into
a directory for downloading into the SAN Data Gateway at a later stage.
From the main screen of the SAN Data Gateway Specialist, you can check the
current Firmware Revision level, as shown in Figure 7-18.
Figure 7-18 SAN Data Gateway Firmware Revision Level
New versions of the SAN Data Gateway can be downloaded, as shown in
Figure 7-19, by selecting the Controls option and then selecting the Update
Firmware option.
Figure 7-19 Updating the SAN Data Gateway firmware
Chapter 7. Implementing the SAN Data Gateway
767
The SAN Data Gateway Specialist will then prompt for the location of the new
firmware as shown in Figure 7-20. This is the file that was downloaded from the
SAN Data Gateway Web site previously.
Figure 7-20 Specifying location of the firmware
Downloading the firmware into the SAN Data Gateway is a disruptive process, so
the Specialist displays a warning message as shown in Figure 7-21.
Figure 7-21 Warning message prior to downloading the firmware
Once all I/O activity is stopped, you can click Yes to continue the process.
768
IBM SAN Implementation
Once the firmware process has been started, the SAN Data Gateway Specialist
displays a message as shown in Figure 7-22.
Figure 7-22 Download in progress
This indicates that the firmware is being downloaded to the SAN Data Gateway.
The Specialist will then give the option to restart the SAN Data Gateway as
shown in Figure 7-23.
Figure 7-23 Message prior to restarting the SAN Data Gateway
Chapter 7. Implementing the SAN Data Gateway
769
As restarting the SAN Data Gateway is a disruptive process, the Specialist
issues a warning as shown below in Figure 7-24.
Figure 7-24 Warning message prior to restarting the SAN Data Gateway
The Specialist will now return to the main screen, and a message is displayed at
the bottom of the screen as shown in Figure 7-25 indicating that the Gateway is
in the process of restarting.
Figure 7-25 SAN Data Gateway now restarting
770
IBM SAN Implementation
Once the restart process is completed, the Specialist displays the prompt shown
in Figure 7-26 before refreshing the display.
Figure 7-26 Restart completed message
Once the Specialist has finished refreshing, we can see that the firmware
revision level has been updated successfully, as shown in Figure 7-27.
Figure 7-27 New firmware revision level
Chapter 7. Implementing the SAN Data Gateway
771
7.4 SCSI devices
The four SCSI ports on the SAN Data Gateway support Differential Ultra Wide
SCSI devices. It will automatically negotiate speed for wide or narrow bus width
devices as well as standard, fast and, ultra speeds. The SAN Data Gateway
provides a termination on each of its SCSI buses. The termination can be
separately disabled if so desired from the StorWatch SAN Data Gateway
Specialist window.
7.4.1 LUN support
The SAN Data Gateway provides support for up to 256 LUNs. Each SCSI
channel supports up to 15 SCSI targets and up to 32 LUN per target. This is
subject to the overall total of 256 available. The first LUN (LUN 0) is used for the
Gateway for control and command purposes. That leaves 255 allowable LUN
addresses to be used for attaching SCSI devices to the four SCSI ports.
Note: Do not attach more than 255 LUNs to the SAN Data Gateway.
Exceeding the 255 limit will cause unpredictable results.
The SCSI devices must be previously set up in your host prior to attaching to the
SAN Data Gateway. For example, if an IBM Enterprise Storage Server is to be
used as the target device, then all the volume or LUN assignments must be
completed. Also, the volumes should be assigned to the appropriate SCSI port in
the ESS. Attach the SCSI cable from the SCSI device to a SCSI port on the
Gateway.
7.4.2 Device discovery
Once attached, the SAN Data Gateway can be restarted or powered on to
perform a discovery of the attached devices. If this was done after the
initalizeBox command from the service terminal, then the initial discovery will
be carried out in a specific order. The buses are scanned in order from 1 to 4 and
each bus is scanned from SCSI target 0 to 15 and LUN 0 to 32 for each ID. As a
device is discovered it is assigned a specific LUN number by the SAN Data
Gateway. This numbering will begin at LUN number 1, zero is reserved for the
SAN Data Gateway control, and continues sequentially as devices are
discovered.
772
IBM SAN Implementation
The SAN Data Gateway must add this extra layer of addressing as the host is no
longer directly attached to the disk devices but will see a single target ID, the
SAN Data Gateway. In a regular SCSI environment with the host attached
directly to the SCSI device, the host is able to recognize the target and LUN ID of
that device. Since we add the SAN Data Gateway in between the host and the
device, the host is no longer directly attached to the SCSI device to recognize its
target or LUN ID.
7.4.3 Assigning LUN IDs
The Gateway assigns LUN IDs to all the attached devices, up to the maximum of
255, and it creates a map of the actual disk device target and LUN ID to its own
assigned LUN ID. This map is stored in nonvolatile memory within the Gateway.
7.4.4 Adding SCSI devices
New SCSI devices can be added at any time. If a new device is added, for
example, another volume in the IBM Enterprise Storage Server has been
assigned to a SCSI port on a San Data Gateway, the SCSI buses must be
re-scanned to detect the new device. This can be done from the service terminal
using the scsiRescan command or from the StorWatch SAN Data Gateway
Specialist. If using the Specialist, select and highlight the SCSI bus that the
device has been assigned to, and select Controls-> SCSI Channel-> Re-Scan
SCSI Bus. As it rescans, the SAN Data Gateway will assign the next available
LUN address to the new device. Refresh the data on your Specialist window by
selecting View-> Refresh SAN Data Gateway.
Once a device has been assigned a LUN ID by the Gateway, it will maintain that
ID since it was written into the device map. This is useful in case the device is
lost or needs to be replaced. Remove the old device, set the new device to the
same SCSI bus target and LUN as the old device and attach it to the same
channel. You must rescan the SAN Data Gateway SCSI bus for it to update its
data. You will notice that the replaced device has kept the same assigned LUN.
If a device is no longer attached or no longer required, then the assigned LUN is
also no longer required. To free up this assigned LUN ID, you can issue the
mapWinnowDatabase command from the service terminal. The existing devices
will maintain their assigned LUN IDs.
If a complete rebuild of the SCSI device map is desired or required, this can be
done from the service terminal only. You would issue the mapRebuildDatabase
command. This command deletes the existing device map and the SAN Data
Gateway will restart. When it is rebooted, a new scan of the SCSI buses is done
as if the system was brand new, and LUN IDs will be assigned as described
earlier.
Chapter 7. Implementing the SAN Data Gateway
773
When this command is issued, you will also be given an option to clear the Virtual
Private SAN (VPS) access settings. Because this allows host access to specific
LUNs and by issuing this command, we may change the assigned LUN ID; it is
recommended that you always say Yes to this option. If not, a host may access a
volume that you do not want it to access and be restricted from a volume that it
had access to previously. The system administrator must rebuild the VPS
settings, if enabled, to allow host access to the desired LUNs.
7.5 SAN Data Gateway access options
The SAN Data Gateway includes two features that are helpful in providing control
and security of host access to SCSI devices:
 Zoning
 Virtual Private SAN (or LUN masking)
7.5.1 Zoning
Channel zoning is a feature included with the IBM Storage Area Network Data
Gateway. Zoning allows you to restrict access between SAN Fibre Channel
connections and SCSI channels. The default settings allow all SAN connections
to access all SCSI channels.
Configuring zoning
To configure zoning, and you must be an administrator, select Control ->
Access Options -> Channel Zoning from the toolbar. Figure 7-28 shows a
zoned SAN Data Gateway.
Figure 7-28 IBM Storage Area Network Data Gateway channel zoning
774
IBM SAN Implementation
A check mark will allow access, and as shown in Figure 7-28, you can see that
SAN connection 1 has access to SCSI channels 3 and 4, but not to SCSI
channels 1 and 2. SAN connection 4 has access to SCSI channels 1 and 2, but
not to SCSI channels 3 and 4. To change the settings, click any box and the
check mark will toggle on and off. All combinations are possible. Once the
desired settings are selected, click OK. For the new zone settings to take effect,
the SAN Data Gateway must be restarted.
7.5.2 Virtual Private SAN
The IBM Storage Area Network Data Gateway also provides LUN masking
through a feature called Virtual Private SAN (VPS). This provides a granular
restriction of host access to specific LUNs while utilizing and sharing the same
connectivity paths through the SAN Data Gateway.
VPS keeps track of Fibre Channel hosts by using their unique World Wide Name.
In this way, if a switch is attached, the Gateway will also keep track of it, because
the switch also has a unique World Wide Name. VPS also includes a host
registration service so that when a host is attached, its unique WWN is registered
to the Gateway to provide information on the host and its status.
Enabling VPS
The Virtual Private SAN feature has to be enabled, because it comes disabled
from the factory. To enable it, make sure the desired SAN Data Gateway is
highlighted, if more than one appears in your Specialist window. Select
Controls -> Feature Enable -> Virtual Private SAN, as shown in Figure 7-29.
Figure 7-29 Enabling Virtual Private SAN
Chapter 7. Implementing the SAN Data Gateway
775
A dialog box appears requesting the entry of a license key number. For units with
serial numbers lower than 1300600 you are required to get a license key that is
matched to the serial number of the SAN Data Gateway. For units with serial
numbers higher than 1300600, the VPS feature is bundled into the product. Type
the word enable and the feature will now be enabled.
Host registration
With VPS enabled, the host registration service is also available. This service is
provided to simplify VPS configurations. It provides the host name, host type,
host connection, and the unique WWN of the Fibre Channel host bus adapter.
Host information is sent over the Fibre Channel connection to the Gateway.
To obtain this information, a program is loaded on each host. This program is
found, and can be downloaded at the same Web site that the StorWatch SAN
Data Gateway Specialist was downloaded from.
http://www.storage.ibm.com/hardsoft/products/sangateway/support/form1.htm
After completing the registration and license agreement, the Download Main
page is displayed. Select the operating system software subheading and look for
HOSTSW. View the read.me file for the latest information. Download the
software and install it onto the host that will be attaching to the SAN Data
Gateway. Follow the instructions provided in the read.me file.
For Windows NT, the file is a self-executing file, so it can be executed or run as
any *.exe file. As it runs through the install, make sure to select SAN Explorer
and VPS Registration Service, as shown in Figure 7-30.
Figure 7-30 Loading VPS Registration software on Windows NT
776
IBM SAN Implementation
Once installed, the service runs automatically and does not require further
administrator interaction.
Communicating with the Gateway
Once the host is attached to the Gateway and restarted, the registration service
will communicate to the Gateway. The data shown on the Gateway will have to
be refreshed by selecting View-> Refresh SAN Data Gateway. This will cause
the updated data to be shown in the Specialist window.
The registration service will re-register the host to the SAN Data Gateway at a
default of 15 minute intervals. This interval can be changed if so desired.
Previous to enabling the VPS feature, you will have seen that the Specialist
displayed a window similar to Figure 7-31. There is no key beside the Fibre
Channel ports, indicating that no host is recognized.
Figure 7-31 Specialist display without VPS enabled
After the VPS is enabled and a host has registered with the Gateway, all its
information will load automatically into the database of the Gateway. Figure 7-32
shows, in the right-hand side view pane, the host name, host type, HBA and
connection information, and the unique WWN that was obtained automatically by
host registration.
Chapter 7. Implementing the SAN Data Gateway
777
Figure 7-32 Specialist after VPS enabled and host registration
If no registration software is loaded on the host, or is not available for a specific
operating system, for example a Fibre Channel switch, only the WWN of the
attached system will register to the VPS database, all other fields will have
unknown. This is shown in Figure 7-33.
Figure 7-33 Host system with no host registration software
A diagram to depict the setup that was described, is shown in Figure 7-34. Note
that as the first dual Fibre Channel port on the Gateway is used, it is numbered
as input 1 and 4. A description on the Fibre Channel port numbering was shown
in Figure 7-2 on page 751.
778
IBM SAN Implementation
Servers
'unknown'
'plymouth'
Fibre
Channel
1
4
Gateway
1
2
3
SCSI
ESS
Figure 7-34 SAN Data Gateway with two hosts
Adding host and connection information
The host name and host type and connection information can be added manually
by selecting the VPS feature and modifying the data. To do this, select the
desired SAN Data Gateway so that it is highlighted. Select Controls -> Access
Options -> Virtual Private SAN, and you will enter into the VPS settings
window. The hosts and their information will appear on the left-hand side.
Chapter 7. Implementing the SAN Data Gateway
779
Select the host to be modified, and the information is transferred to the bottom
part of the window where the modifications can take place, as shown in
Figure 7-35.
Figure 7-35 VPS host settings
The Host information can now be entered in the left-hand column labeled New
Host Data. The Original Host Data column displays the values before any
changes are made. Once completed, select Apply Changes and then Close.
This window can also be used to enter in host information for a host that has not
yet connected to the SAN Data Gateway. Select New Host and then enter in the
WWN and other parameters that are available. You must, at minimum, enter in a
WWN. Also, when entering in the number, a colon ‘:’ must be used to separate
the first four bytes from the last four bytes.
Also, you will notice that the host description in the top can change color. If the
information is in blue, then the host is offline. If the host information is in black,
then it is online.
The VPS feature allows an administrator to quickly view the host information and
status at a central location.
780
IBM SAN Implementation
Setting up a Virtual Private SAN
Remember that the SAN Data Gateway assigns its own LUN numbers, and it
does so in a sequential order. An attached disk device may have a SCSI target of
1 with a LUN ID of 4, but when recognized by the SAN Data Gateway, its LUN
number assigned will be something completely different. An example is shown in
Figure 7-36.
Figure 7-36 SCSI LUN assignment
In this example, the disk device attached has a SCSI target of 6 and LUN ID of 1.
When it was recognized by the SAN Data Gateway, the Gateway assigned LUN
number 38 to this device. This Gateway’s assigned LUN number corresponds to
the assigned LUN number that appears on the top of the VPS settings window,
as shown Figure 7-38 on page 783.
Chapter 7. Implementing the SAN Data Gateway
781
SCSI to LUN map
Prior to setting the LUN masking, it makes sense to prepare a list that has each
LUN and shows which host is allocated to that LUN. To assist in this process the
Gateway has a map that provides a cross reference of the actual SCSI target
and ID to the Gateway’s assigned LUN number. To access this map you must
access the service terminal from the serial port as described earlier in 7.2,
“Installation” on page 751. Once connected, type in the command
mapShowDatabase. The database lists not only devices that are presently
connected, but also devices that have previously been connected. If a previously
attached device is later reattached, it is assigned back to its previous address.
Figure 7-37 shows the output returned to the service terminal.
Figure 7-37 Service terminal display of device map
The numbers on the left are the assigned LUN numbers, and note that number
‘0’ has been assigned to the Gateway. The other columns contain the device
type, the SCSI channel it is connected to on the SAN Data Gateway, and the
actual target and LUN ID.
782
IBM SAN Implementation
Setting host access to LUNs
To view and set host access to particular LUNs, access the Virtual Private SAN
Access Settings by selecting Controls -> Access Options -> Virtual Private
SAN. This window will show all the hosts that have registered to the Gateway.
To allow a host to access a particular LUN, place a check mark in the row that
corresponds to the host. To disable access, the square must be clear, without a
check mark. The check mark is toggled on and off by clicking in each square.
Figure 7-38 provides an example of LUN masking.
Figure 7-38 Setting LUN masking
The host plymouth has access to LUNs 17 to 24 but does not have access to
LUNs 25 to 30. Conversely, the host at the top has access to LUNs 25 to 30, but
does not have access to LUNs 17 to 24. Using the scroll bar on the bottom, we
can scroll through all 255 available LUNs in the SAN Data Gateway, and enable
or disable access by adding or clearing the check mark. The scroll bar on the
right-hand side allows us to scroll through the different hosts. In this example,
there are only two hosts, but there can be several more.
Chapter 7. Implementing the SAN Data Gateway
783
Once completed, select Apply Changes and then Close. The host system may
now have to be restarted or some other method used to rescan the bus for the
host to detect that it now has access to new devices.
Any combination is allowed, so if the same LUN is to be shared by two different
hosts, a check mark for that LUN must be set for both. If this is the case, the host
systems must have a device sharing software installed to control access to the
disk device for data integrity.
As each Fibre Channel port can support up to 8 eight different hosts, there can
be up to 48 hosts attached to the SAN Data Gateway. They can all share the
same four SCSI channels. By using the Virtual Private SAN feature, you can
ensure that only the LUNs you desire a certain host to use will be accessed and
that no other host will access them.
7.5.3 Combining Zoning and Virtual Private SAN
If Virtual Private SAN is enabled and LUNs have been allocated to specific hosts,
then zoning is not necessary or required. The Channel Zoning window can
remain at the default settings with all Fibre Channel ports accessing all SCSI
channels.
However, they can work in combination to add an extra level of control and
security. If zoning is added, then VPS can only control the LUNs that are included
in its access zone. Figure 7-39 shows a zoned SAN Data Gateway.
Figure 7-39 Combining channel zoning and VPS
784
IBM SAN Implementation
SAN connection 1 has access to the LUNs on SCSI channels 2 and 4. VPS will
control access to LUNs on SCSI channels 2 and 4 for SAN connection 1. Since
SAN 1 is not zoned for SCSI channel 1 and 3, it will not reach any LUNs on these
channels. Even, if a LUN on SCSI 3 has been enabled for access to a host on
SAN 1 in the VPS settings window, the host will not see that LUN because of the
zoned settings. The same is true for SAN
connection 4. A host connected here will access LUNs only on SCSI channels 1,
2, and 3, but not channel 4, regardless of whether the VPS settings will allow it.
7.6 Adding Fibre Channel fabric components
The SAN Data Gateway is an integral component in a storage network. As such,
you can also attach other SAN fabric components to the Gateway to increase the
connectivity options in a SAN. Hubs and switches can be easily added, and allow
many more systems, local or remote, to access the SCSI devices on the
Gateway.
As switches provide more flexibility, and hubs are mainly used to extend
distances, the following discussion will focus on switch implementation, rather
than hubs.
7.6.1 Connecting an IBM SAN Fibre Channel Switch
The IBM SAN Fibre Channel Switch provides either an 8 port or 16 port switch
that can also be cascaded.
Allowing fabric connection
Before connecting a switch to the SAN Data Gateway, there is a setting that must
be checked to allow proper fabric connection. From the SAN Data Gateway
Specialist, select the Fibre Channel port that will have the switch connected.
Select Control -> Fibre Channel, and the Set Fibre Channel Parameters
window appears, as shown in Figure 7-40.
Chapter 7. Implementing the SAN Data Gateway
785
Figure 7-40 Fibre Channel port setting for switch attachment
By default, the setting in the Connection Options box will have Loop enabled.
For switch or fabric connection, select Point to Point, and then select OK. The
SAN Data Gateway must be restarted for the change to take effect.
Note: Connection Options box does not appear, the Fibre Channel module
installed will support loop connection only and will not support fabric
connection. The module must be replaced or select a port that will support
fabric connection.
A Fibre Channel cable can be connected from the switch to the port on the
Gateway. The data to the Specialist must be refreshed by selecting and
highlighting the Gateway and then select View -> Refresh SAN Data Gateway.
786
IBM SAN Implementation
Switch registration
With VPS enabled, the switch will register with the database the WWPN of
the port on the IBM SAN Fibre Channel Switch. Figure 7-41 shows a switch
connected to port 4 of the Gateway, and which has registered to the
database. Since we cannot load any host registration software onto the
switch, all other fields are left unknown.
Figure 7-41 Switch registration
By selecting and highlighting the Fibre Channel port, as shown in Figure 7-42,
you will see in the right-hand view pane that the port is now using a point to point,
or N_port, connection that denotes a fabric login rather than a loop login.
Chapter 7. Implementing the SAN Data Gateway
787
Figure 7-42 Switch port login
You can also check the port on the switch, by accessing the switch configuration
from a Web browser, to ensure that the port has registered and is communicating
properly. Figure 7-43 shows that, in this example, port 7 of the switch was used
to connect to the Gateway. Note that the WWPN is the same as in the Specialist
window and that the port type is F_port.
Figure 7-43 IBM SAN Fibre Channel Switch port settings
788
IBM SAN Implementation
Changing the switch information
From the VPS Access Settings window, it is possible to change the unknown
information of the switch. Select Controls -> Virtual Private SAN, and select
the entry that has the WWN of the switch. You can now change the information to
further describe the switch, or other pertinent information if desired. This is
shown in Figure 7-44.
Figure 7-44 Changing switch information
Chapter 7. Implementing the SAN Data Gateway
789
The information on the host plymouth, that was attached using port 4, is still kept
in the VPS database, but it is now shown in blue to indicate that it is offline.
Figure 7-45 is a diagram showing the configuration with the switch.
Servers
'plymouth'
'unknown'
IBM Switch
7
Fibre Channel
4
1
Gateway
1
2
ESS
Figure 7-45 Adding an IBM switch to the Gateway
790
IBM SAN Implementation
3
SCSI
Once changed, as shown in Figure 7-46, the information shown on the main
window will reflect the change, and the icon on the left-hand side of the WWN
changes to depict a switch.
Figure 7-46 Switch port information
Attaching hosts to the switch
Any hosts that will attach to the switch should have the host registration software
loaded and installed. Refer to , “Host registration” on page 776 for details. Plug in
the Fibre Channel cable from their respective adapters and power on, or restart
the host. The registration of the hosts will be completed through the switch.
Figure 7-47 shows a switch installed on port 4 and two hosts connected on the
switch. The host plymouth is now connected through the switch and an NT host
was added.
Figure 7-47 Hosts and a switch on a Gateway port
Chapter 7. Implementing the SAN Data Gateway
791
By selecting and highlighting the new NT host, we can see its information, which
was automatically sent by the host registration process.
The configuration with two different hosts connected to the switch, as described
previously, is shown in Figure 7-48.
Servers
NT
'FIBRE1'
'unknown'
3
AIX
'plymouth'
5
IBM Switch
7
Fibre Channel
4
1
Gateway
1
2
3
SCSI
ESS
Figure 7-48 Adding two heterogeneous hosts to the switch
792
IBM SAN Implementation
Device access
To have the new NT host access some of the devices, you need to set up the
VPS Access parameters by selecting Controls -> Access Options -> Virtual
Private SAN. Figure 7-49 shows the switch and the two hosts in the VPS
database. As plymouth was previously connected direct to the Gateway, its
settings have been maintained, but now that it is reconnected, it is back online.
The NT host does not have any LUN access yet.
Figure 7-49 VPS Access window with switch and two hosts
Chapter 7. Implementing the SAN Data Gateway
793
A check mark in the box allows a host access to a LUN, or clear the box if you
want to restrict access as described in , “Setting up a Virtual Private SAN” on
page 781. Figure 7-50 shows the host plymouth with access to assigned LUNS
17 to 24, and the NT host FIBRE1 is now set with access to LUNs 25 to 30.
Figure 7-50 Setting LUN access for the host FIBRE1
Once you select Apply Changes and then Close, the new settings will be in
effect. For Windows NT to recognize the new devices, it will have to be restarted,
so that it will do a rescan.
The SWITCH entry in the VPS database does not require any check marks to be
set. Because the WWN of the host is known, and the switch WWPN is known,
LUN access is accomplished through the switch as if it was transparent.
Note: LUN access is not only affected by the VPS and Zoning with the SAN
Data Gateway, there is also Zoning within the IBM SAN Fibre Channel Switch.
Be aware of the zone settings within the IBM SAN Fibre Channel Switch
794
IBM SAN Implementation
ESS considerations
As you configure and allow access from host systems to volumes that are in the
ESS through the Gateway, you must consider how the volumes were created
within the ESS.
Volumes in the ESS are assigned to a particular SCSI port in the ESS. As they
are assigned, you also specify the host type that will access these volumes.
Through the SAN Data Gateway it is possible to assign volumes to a specific
operating system in the ESS, but then have a host with a different operating
system access to these volumes.
As an example, look at Figure 7-48 on page 792. There we have a Windows NT
and an AIX host. The ESS was configured and the Gateway attached so that
SCSI 2 was assigned Windows NT volumes and SCSI 3 was assigned AIX
volumes. It would be possible in the SAN Data Gateway to allow the NT host to
access a LUN on SCSI 3 and the AIX host access to volumes on SCSI 2.
Here is where the device map would again be helpful in determining what
Gateway assigned LUNs should be assigned to each host.
Volumes within the ESS assigned to a particular SCSI port should be of the same
host type.
7.6.2 Connecting a McDATA Enterprise Fibre Channel Director
The McDATA Director can be used to attach to the SAN Data Gateway. The
connection of the McDATA Director to the SAN Data Gateway is similar to the
description provided previously in 7.6.1, “Connecting an IBM SAN Fibre Channel
Switch” on page 785.
The difference that can be seen when using the McDATA Director is, that once
connected, the Director does not register the WWPN of the port connected to the
Gateway visually to the VPS database. Figure 7-51 provides an example of
where a McDATA Director was connected to the Gateway on Fibre Channel
port 4.
Chapter 7. Implementing the SAN Data Gateway
795
Figure 7-51 McDATA Director connection to a Gateway
In the right-hand view pane under Port Type, you see that the port is in N_Port
mode to denote a fabric connection. However, in the left-hand view pane there
are no devices listed under the Fibre Channel port 4 description.
As hosts begin to attach to the McDATA Director and are restarted, they will
begin to login their own information to the Gateway’s VPS database. The
McDATA is seen as completely transparent to the SAN Data Gateway.
7.7 High availability considerations
Until now, our discussions of connections from the host to the SAN Data
Gateway and from the Gateway to the ESS, or other SCSI devices, have been
discussed with single host adapters or utilizing single SCSI connections.
However, special considerations must be taken into account in deciding to add
host adapters, or in providing redundant SCSI connections.
796
IBM SAN Implementation
7.7.1 Single host with multiple Fibre Channel adapters
A host can have several adapters installed. If each adapter is assigned to
different LUNs using the SAN Data Gateway, there are no contention issues. As
each adapter is assigned specific LUNs, it cannot see or access any other LUNs
that may be present.
However, there may be situations where the adapters are used to perform load
balancing, and failover much like the SCSI connections from a host to the ESS
that are in place today. As the host in the SCSI situation requires the Subsystem
Device Driver (SDD) on each host, this is also true when using the Fibre Channel
adapters.
Software, similar to SDD, is required in the host for it to recognize that it may
have two or more paths to the same volume. If this was not loaded on the host,
the host would recognize the volumes as being different, and there will be
contention problems, and data corruption.
As SDD is currently only supported on SCSI adapters and not with Fibre Channel
adapters, it is also not supported when using the SAN Data Gateway to connect
to an ESS.
7.7.2 Multiple SCSI connections
The SAN Data Gateway can have all four SCSI channels connected to a single
ESS. A volume in the ESS can be assigned to more than one SCSI port in the
ESS. If these SCSI ports, that have the same volume assigned to it are
connected to a SAN Data Gateway, the Gateway will assign multiple LUN ID
numbers to the same volume. This is because the Gateway, upon discovery, or
scanning of the SCSI buses, will view the volumes on each SCSI channel as
separate volumes. For further explanation on this refer to 7.4.2, “Device
discovery” on page 772.
If each LUN ID was then masked and zoned to different host systems, it is vital
that the hosts have some access sharing software loaded to control access and
avoid data corruption.
If the LUN IDs were assigned to the same host, then again software similar to
SDD is required for the host to recognize that it has multiple paths to the same
volume.
As stated earlier, SDD is not supported on the SAN Data Gateway connection to
an ESS.
Chapter 7. Implementing the SAN Data Gateway
797
7.7.3 Adding Fibre Channel switches
As switches are added to allow for more host attachments, there are
considerations about how many paths the host has to the SAN Data Gateway.
If we refer back to Figure 7-48 on page 792, there is a single path from the switch
to the Gateway.
If another Fibre Channel path from the switch to the Gateway was added, each
host now has two paths to access the same LUNs. Each host will see the
volumes twice. Once again, to prevent the host from recognizing the same
volume twice, software similar to SDD is required.
Another option here is to utilize the zoning and LUN masking capabilities of the
SAN Data Gateway. This would ensure that certain volumes can only be
accessed on one Fibre Channel Gateway port and by a particular host.
Also available is to add zoning within the switch. The switch Fibre Channel ports
can be zoned so that the host only has one path to the SAN Data Gateway. This
would be used in combination with the zoning and LUN masking features of the
SAN Data Gateway.
798
IBM SAN Implementation
8
Chapter 8.
Implementing the Vicom
Fibre Channel SLIC Router
The Vicom Fibre Channel SLIC Router, 7139-111, enables all IBM 7133, 7131,
and 3527 SSA Serial Disk Systems to attach to host systems using Fibre
Channel host adapters and drivers. This allows you to protect your investment in
SSA disk, while being able to create and build a SAN infrastructure.
The Vicom Fibre Channel SLIC Router replicates data across or within serial disk
systems — simultaneously mirroring two or three copies of data without host
involvement. With global hot disk sparing, data is automatically rebuilt if a
mirrored disk fails. In this way, the Vicom Fibre Channel SLIC Router improves
performance and data availability while simplifying storage operations.
In the following sections, we cover these topics:








“SLIC Router features” on page 800
“Installing the SLIC Router” on page 801
“SLIC Manager software” on page 804
“Using SLIC Manager” on page 811
“Composite drive” on page 815
“Mirror drive” on page 820
“Instant Copy drive” on page 825
“Combining composite and mirroring” on page 830
© Copyright IBM Corp. 2001
799
8.1 SLIC Router features
The Instant Copy function can create a separately addressable copy of mirrored
data that can be used for tape backup. After the backup has completed, data is
resynchronized with the primary copy.
The Vicom Fibre Channel SLIC Router also can create composite drives by
concatenating up to 16 physical disks.
Using these functions, physical drives become members of larger or more
complex logical drives.
A diagram to depict a single host to Router configuration is shown in Figure 8-1.
Server
Fibre Channel
Vicom SLIC
Router
A1
A2
SSA Disk Loop
Figure 8-1 SLIC Router with a single host
800
IBM SAN Implementation
8.2 Installing the SLIC Router
To install and establish a SLIC storage system, the Router and all the disks to be
used must be set up in a proper sequence. During this sequence, only a single
SLIC Router must be used to do the configuration. Once configured, other SLIC
Routers can be added to the loop. This sequence is described below.
Note: For information and a description to understand the LED codes that will
be discussed, please refer to the SLIC Router Installation and User’s Guide,
310-605759.
1. Power on SSA disks.
The SSA disks must be powered on to ensure that all disks spin up and pass
the power sequence. Make sure all drive LEDs are on solid to indicate a
functioning device. Any faulty or suspect disk drive should be replaced.
2. Clear Router Node Mapping.
To begin the Router installation, the first step is to clear the Node Mapping
table. This is done by shorting the SSA ports on the rear of the Router. Plug in
an SSA cable from port A1 to A2 on the back of the Router and power it on.
Clearing the table will take only seconds, and when completed, the Status
LED on the front of the Router will flash a code 060. The Router is now
powered off, the SSA shorting cable is removed and the SSA disks are
attached.
3. Connect SSA disks to Router.
All the disks to be used are to be connected together to form a complete SSA
loop with the Router included. All dip switches in SW1 should be in the down
position. On SW2, dip switches 0 and 1 are set in the down position, all other
switches in dip switch 2 should be turned up. This is considered mode 3.
Power on the Router, the Status LED will begin to flash rapidly as it searches
the SSA loop to recognize all the disk drives. This may take approximately 1
minute to complete. Once the Status LED has stopped flashing and is solid,
the process is complete and the Router is powered down.
4. Perform Router Subsystem Diagnostic test.
A Subsystem Diagnostic test is now run on the disk drives called mode 15.
This tests the disk drives for spindle spin up, read tests and nondestructive
write tests. The Router is set for mode 15 by setting switches 0, 1, 2, and 3,
on SW2, to the down position, and the rest turned up. The Router is now
powered on, the Status LED will flash rapidly. The test will be done on each
disk drive in the SSA loop separately and will begin with the drive closest to
the A1 port on the back of the Router. As the test is completed on a drive, the
Chapter 8. Implementing the Vicom Fibre Channel SLIC Router
801
LED on the SSA drive will flash and then it will move to the next drive. This
test should continue until all drives have been tested. The test runs in a
continuous cycle, so once all drives have been tested at least once, the
Router is powered off.
If a drive fails the test, the testing will stop, and the Router’s Status LED will
flash a diagnostic code. A code map with a description of the errors can be
found in the SLIC Router Installation and User’s Guide, 310-605759.
5. Assign Fibre Channel target.
With the Router powered off, you can now assign a Fibre Channel target ID
number to the Router. Any number can be selected, however, this number
must be a unique ID. No other device can have the same Fibre Channel target
ID once it is set on the Router.
This is done by setting selected dip switches in SW1 to the down position.
The switch is set up in binary notation: a switch that is down represents a 1
and a switch up represents a 0. Figure 8-2 shows the switch numbers and
their corresponding value.
128
64
32
16
8
4
2
1
Binary
Value
7
6
5
4
3
2
1
0
Switch
Number
Figure 8-2 SW1 dip switches
For example, by setting switch 2 and 0 down, a value of 5 is represented. All
other switches would be in the up position. By setting a switch down, its value
is added. To change a number that was previously set on a Router, power
must be cycled to the Router for the change to take effect.
6. Map the physical drives.
Before powering on again, SW2 must be set to mode 3 with switch 0 and 1
set down, and all other switches set up. The Router is powered on, the Status
LED will flash rapidly to rediscover the disks and the SSA drive LEDs should
be on solid. Once completed, the status LED will be solid, and the drives are
now considered to be mapped physical drives. The Router is powered off.
802
IBM SAN Implementation
7. Create general spares.
The mode on SW2 is changed to mode 12 to set all drives to be general
spares. Mode 12 is represented by setting switch 2 and 3 down and the rest
turned up. Power on the Router again, the Status LED will flash. After
approximately one minute, the LED will flash code 100 to indicate it has
completed. The Router is again powered off.
8. Format the drives.
The Router is set to mode 14, switch 1, 2, and 3 down on SW2, to format all
disk drives. Power on the Router, depending on the number of drives, the
format process will take anywhere from 30 to 60 minutes. During this time, the
Status LED will flash rapidly and the SSA drive LEDs will flash. When it has
completed, the Status LED will flash code 100. Power off the Router.
9. Clear the node map.
Once completed, the node map must be cleared. This is done as described
earlier by shorting ports A1 and A2 with an SSA cable. Power on, wait for
code 060 to flash and then power off.
The drives are now ready to be assigned and used on a host.
You can also now setup mirror drives or composite drives within the Router.
This is done by setting the switches in SW2 to other modes. For detailed
information on setting the switches and selecting the other modes, please
refer to the SLIC Router Installation and Users Guide, 310-605759.
10.Perform host attach and power up sequence.
For a host to now recognize and use the disks, set the dip switches in SW2
back to mode 3, this is normal host operation mode. The Fibre Channel cable
from the host can be connected to the Router. If the SSA drives are not
powered on, do this now, and this should be done before the Router. Next, the
Router is powered on, wait for the Status LED to stop flashing and remain on
solid. At this point the host can be powered on.
A check can be done to see that the SLIC Router is being recognized by the
host adapter card. On a Windows NT with a QLogic Fibre Channel adapter,
during boot up look for a prompt to enter the QLogic bios by entering in
ALT Q. At the BIOS window, select Scan Fibre Devices. A list of the Fibre
Channel target IDs are presented, scroll down to the ID that you set in SW1.
You will see the WWN of the SLIC Router. Exit the bios and the system will
reboot.
Once the system has started, you use a method to ensure that the host has
access to all the drives. This is different depending on the operating system of
the computer. For Windows NT, select Start -> Programs ->
Administrative Tools -> Disk Administrator. This tool will report that new
disks have been found and will be added to the system.
Chapter 8. Implementing the Vicom Fibre Channel SLIC Router
803
8.3 SLIC Manager software
Rather than using the dip switches to configure the features, another option is to
use the SLIC Manager software. The SLIC Manager also provides configuration,
monitoring and management capabilities of the SLIC Router and the SSA drive
loop. The SLIC Manager can be setup to allow remote access if desired.
The Manager software consists of server and client portions. The server includes
a daemon service and a user interface. The client has the user interface only.
The server portion must be loaded on the host that is directly attached to the
Router, as the daemon service is started from here. The daemon must reside on
the host that is directly connected to the Router. This host can also be used to
run the Manager software for local access.
The client software can be loaded on to any computer, running a supported
operating system, that can communicate to the host with the daemon service
running. It must communicate to the server host using TCP/IP. This allows
remote access to the Router and the storage loop. See Figure 8-3.
Server
Remove Access
SLICManager
TCP/IP
Server
Local Access
SLIC DAEMON
and Manager
Fibre Channel
Vicom SLIC
Router
A1
A2
SSA Disks
Figure 8-3 SLIC Manager access
804
IBM SAN Implementation
The SLIC Manager has a graphical user interface (GUI) and a command line
interface (CLI) available for Windows NT systems. UNIX systems will only have
the command line interface available.
The following installation and configuration examples will detail using the GUI
from a Windows NT platform. To review the commands that are available for
UNIX platforms and installation instructions on other operating systems, please
refer to the SLIC Manager Installation and User Guide, 310-605807.
8.3.1 Installing the SLIC Manager software
The SLIC Manager software can run on many operating systems. The following
discussion will describe an installation on a Netfinity 5500 with Windows NT 4.0.
To install the SLIC Manager server software for local access, the Vicom Utilities
CD-ROM is placed in the CD drive. Select Start -> Run and Browse the CD
drive. Go to slicmgr\i386\server\setup.exe and click OK. Follow the
prompts displayed on the window to install the Manager software. This will
install the daemon service also.
For remote or client access the daemon service is not required. To load the
Manager software only, go to slicmgr\i386\client\setup.exe instead.
8.3.2 Communicating to the Router
For the SLIC Manager server software to communicate to the Router, it requires
space on a disk or several disks that are within the SSA loop. This is referred to
as a SLIC Zone. To create space on a disk, a file or partition — depending on the
operating system used — is created for the Manager software to use. To create
this SLIC Zone, a configuration file must be created or edited.
Chapter 8. Implementing the Vicom Fibre Channel SLIC Router
805
Editing the configuration file
When the software is loaded, a sample configuration file called 7190.cfg is added
in the C:\ibm7190\sdus directory. This is a text file that can be viewed and
edited by simple text editors, such as Windows Wordpad. Open up the 7190.cfg
file and it will contain a sample of how the file should look. Also note that on the
left hand side, the # sign is entered in every line to mark it out as a comment.
This is shown in Figure 8-4.
Figure 8-4 Sample configuration file
806
IBM SAN Implementation
This file can now be edited to be used as the configuration file for your SLIC
system. Begin by deleting the # sign on the lines that contain the sample
configuration. The rest of the information can be entered in, as shown in
Figure 8-5. A description of each entry field is also provided.
Figure 8-5 Edited configuration file
Chapter 8. Implementing the Vicom Fibre Channel SLIC Router
807
Configuration file information
The SLIC_name can be any name that you would like to use to identify the
Router.
Creating a SLIC Zone
The path refers to the SLIC Zone, file or partition, used for the Manager to
communicate to the Router. To edit this option, it requires that a drive on the SSA
loop has been recognized by the host and that the drive has been formatted. In
the example above, a Windows NT host was used. The Windows NT Disk
Administrator was used for the host to recognize the drives, the first drive
assigned the next drive letter, F, and it was formatted.
The file naming for a SLIC Zone depends on the type of operating system
running. For Windows NT, the naming is <drive letter>:\IBM7190.SFA.
You can enter in many SLIC Zones, but only one is required to get access at the
beginning. After the other drives have been configured as mirrors or composite
drives, then SLIC Zones can be created for these drives if desired.
Including many SLIC zones in the path statement will allow the Manager to
access a zone on another drive. This is helpful to protect against when a drive
fails, and that drive has a SLIC zone defined to it. If the Manager cannot access
the first SLIC zone, it would try the next zone in the order it was entered in the
path statement.
For the naming conventions used on other operating systems to create a SLIC
Zone, refer to the SLIC Manager Installation and User Guide, 310-605807.
The userlogfile will define a file with which you can view logged events.
The QueryChangeInterval sets the time in seconds that the daemon will poll the
Router. The recommended time set here is 10.
Ensure that at the end of every line a semi-colon ‘;’ is used, and that, if several
SLIC Zones are created, a comma separates them. Save and exit the file.
808
IBM SAN Implementation
Installing the SLIC Manager daemon
With the configuration file edited and a SLIC Zone created, the daemon service
can be installed and run. To install the service in Windows NT, open a DOS
prompt and go to C:\ibm7190\sdus. Type in slicd -install, and the daemon
will be installed.
Starting the SLIC Manager daemon
To start the daemon service, select Start -> Settings -> Control panel from
Windows NT. Double-click the Services icon. Scroll down until you see Vicom
SLIC Manager; select and highlight it. You will see two columns to the right to
indicate its status.
To start the service, click the Start button and it will take a few moments to
complete. Once it is done, you will see the word Started in the Status column.
If the Startup column contains the word Automatic, no further action is
required. If not, click the Startup button, and change the Startup Type to
Automatic. This will have the daemon service start automatically during a reboot.
This is shown in Figure 8-6.
Figure 8-6 SLIC daemon start up in Windows NT
Chapter 8. Implementing the Vicom Fibre Channel SLIC Router
809
8.3.3 Starting the SLIC Manager
To start the Vicom SLIC Manager software, select Start -> Programs -> Vicom
-> Vicom SLIC Manager. The software will load, and a dialog box will appear. In
the box with the heading Hostname, enter in the name or IP address of the host
the daemon service is running. Enter in the SLIC name you entered in when
editing the 7190.cfg file. An example is shown in Figure 8-7.
Figure 8-7 SLIC connection window
Click OK and the software will begin to communicate to the Router. You will
notice that the top title bar of your window will now include the host name and
SLIC name as in Figure 8-8.
Figure 8-8 SLIC Manager title bar
810
IBM SAN Implementation
8.4 Using SLIC Manager
You can now look to see that all communications are working properly by going to
the toolbar and selecting Tools -> Control Center. A dialog box will appear, as
shown in Figure 8-9.
Figure 8-9 Control Center window
In the Physical Drive box, the drives that are on the SSA loop can be seen. This
window will be useful as you start to create mirrors and composite drives,
because it provides a summary of all drives.
Chapter 8. Implementing the Vicom Fibre Channel SLIC Router
811
8.4.1 Drive properties
You can get detailed information on each drive. Select the drive so that it is
highlighted and then select Properties. A dialog box will appear with the drive’s
information, as shown in Figure 8-10.
Figure 8-10 Disk drive properties
Here you can see its SSA attributes, its Fibre Channel attributes and its model
type and serial number. By clicking the Identify button, the LED on the selected
drive will begin to flash.
8.4.2 Router properties
To view the information on the Router, go to the toolbar and select Properties ->
SLIC Properties. As shown in Figure 8-11, you will see the serial number of the
Router, its ID that was set in SW1, and its supported features.
812
IBM SAN Implementation
Figure 8-11 SLIC Router properties
8.4.3 Setting Router to master
As you move through the toolbar, you may notice that most selections have been
grayed out. This is due to the fact that the Router is currently in a subordinate
role and does not have access to create mirrors or composite drives. This
function is done by a Master Router. There can be only one master in a SLIC
loop. This is used as more Routers and more disks can be added to the loop.
With several Routers in the same loop, there needs to be a requirement where
one system acts as the control, and the others will follow and understand any
configuration changes that may occur.
To set the Router into a master role, select File -> Program Option from the top
toolbar. You will be presented a dialog box, as shown in Figure 8-12.
Figure 8-12 Setting the Router to master
Chapter 8. Implementing the Vicom Fibre Channel SLIC Router
813
Click in the Always Master box so that a check mark appears. Once you click
OK, the Router will then be set as the master. You will notice that now all options
in the toolbar are available and can start to use the features of the SLIC Router.
By placing a check mark in the Auto Start box, the SLIC Manager will
automatically connect to the Router defined in the Connection window, as seen
in Figure 8-7 on page 810.
8.4.4 The SignOn drive
When the SLIC zone was created to be used as the communication path, a disk
file or partition was created on a specific disk within the SSA loop. As you begin
to access the features of the SLIC Router, it should be known which disk was
used to create the SLIC zone. This disk is considered to be the SignOn drive.
In the topics 8.5, “Composite drive” on page 815 and 8.6, “Mirror drive” on
page 820 we describe creating composite and mirror drives, and you will see that
the properties of the individual physical drives may change. As they become part
of a logical drive, they take on the properties of this logical drive.
If the SignOn drive is used to create a logical drive, its attributes may change and
you may lose the communication path that was created in the SLIC zone. When
you select the SignOn drive as a member of a logical drive, a dialog box will be
displayed as in Figure 8-13 to remind you that the attributes of this drive may be
affected.
Figure 8-13 Selecting SignOn drive dialog box
As long as the LUN number of the SignOn drive becomes the LUN of the new
logical drive, the communications from the Manager to the Router will not be
affected.
Another way to be certain that you do not lose your SignOn drive is not to use the
SignOn drive to create logical drives. However, once some logical drives have
been created, a SLIC zone can be created to one or more of the newly created
logical drives. This logical drive can now be used as the SignOn drive and the
previous drive is now available to be configured without any problems.
814
IBM SAN Implementation
8.5 Composite drive
A composite drive is a large drive that consists of two or more smaller drives. The
capacity of the composite drive is an aggregate of the capacities of all the smaller
drives that are used to comprise this one large drive.
8.5.1 Creating a composite drive
To create a composite drive from the SLIC Manager, select Tools ->
Composite Drive Setup Wizard. A dialog box, Composite Drive List, will
appear. Currently, the list will be blank, because there are no composite
drives created. Once there are composite drives created, you will see a list of
the drives. Click the Next button and you will see the Members Selection
window, as shown in Figure 8-14.
Figure 8-14 Composite Drive Member Selection window
Chapter 8. Implementing the Vicom Fibre Channel SLIC Router
815
From the Available Drive Pool list, click a desired drive and then click the Add>>
button. The drive name will be added to the Member window. An asterisk will
appear on the left hand side of the drive that was selected in the Available Drive
window, to denote that the drive has been selected. Each drive is added one at a
time. To remove a drive from the Member window, select the desired drive and
click the Remove<< button.
Below each window there is a Drive Capacity box. As a drive is selected, its
capacity in megabytes is shown. As you add more member drives to the Member
window, the Drive Capacity box will add all drive sizes together to provide a total
capacity in megabytes. This is shown in Figure 8-15.
Figure 8-15 Creating composite drive from available drives
816
IBM SAN Implementation
When all the desired drives are added, click Next>. The Assigning Properties
window opens, as shown in Figure 8-16.
Figure 8-16 Assigning Composite Drive Properties window
The properties that can be changed are the FC LUN and the Drive Name. There
will be a suggested LUN number in this field that can be accepted. If not, simply
type in the desired LUN number. The name can also be defined to the composite
drive for easier identification, with a limit of up to eight characters.
The Initialization Method box refers to whether or not to allow the operating
system to write its signature on the composite drive.
Chapter 8. Implementing the Vicom Fibre Channel SLIC Router
817
Click the Next> button and a dialog box will appear, as shown in Figure 8-17, to
allow you to create another composite drive. Click Yes If you would like to create
another composite drive, and the Composite Drive List window opens and the
steps described above can be repeated.
Figure 8-17 Completing the Composite Drive setup
Click Finish when you have created all the desired composite drives. Up to this
point, the configuration has been kept within the SLIC Manager software. When
the Finish button is clicked, the SLIC Manager will now communicate to the
Router to complete the process and update the Router to control the drives.
The Host system must re-scan for devices, or restart, to be able to see the
composite drive.
818
IBM SAN Implementation
8.5.2 Composite drive properties
If you view the Control Center again, by selecting Tools -> Control Center, as
shown in Figure 8-18, the newly created composite drive is listed in the
Composite Drive box.
Figure 8-18 Control Center with composite drive
Chapter 8. Implementing the Vicom Fibre Channel SLIC Router
819
Select the composite drive and then click the Properties button. The Composite
Drive Properties dialog box opens, as shown in Figure 8-19.
Figure 8-19 Composite Drive Properties
Here you can find information on the Composite Drive about the member drives
that make up the composite, as well as the Composite Drive characteristics.
Clicking on the Identify Composite button will cause the LED on the actual
SSA drives, that belong to the Composite, to flash. If a member drive is selected
and the Identify Member button is chosen, then the LED only on that drive will
flash. In both cases a dialog box will appear to allow you to stop the flashing.
8.6 Mirror drive
A 2-way mirror drive has two drives that contain exactly the same information.
The SLIC Router can also support a 3-way mirror or 1-way mirror. A 3-way mirror
consists of three drives with the same information. A 1-way mirror is a single
drive, or single composite drive, that is used with an Instant Copy Drive that can
attach to the single drive mirror to synchronize the data. The Instant Copy Drive
can then be split off from the mirror to perform a backup or other action.
The Instant Copy Drive feature can be used with 2-way and 3-way mirrors as
well.
820
IBM SAN Implementation
8.6.1 Creating a mirror drive
To create a mirror using physical drives, from the toolbar, select Tools -> Mirror
Drive Setup Wizard. You will see a dialog box, Mirror Drive List, that will be
blank. If there were mirror drives created, then it would display the names of the
drives. Click the Next>> button and the Mirror Drive Members Selection
window opens. The window on the left named Available Drive Pool contains a list
off all drives that are candidates to participate in a mirror drive.
Select a drive by highlighting it and click the Add>> button. The drive name will
be added to the Member window. An asterisk will appear on the left hand side of
the drive just selected in the Available Drive window, to denote that the drive has
been selected. A second or third drive can be added to create a 2-way, or 3-way
mirror, respectively. Each drive is added one at a time. To remove a drive from
the Member window, select the desired drive and click the Remove<< button.
An example of adding two drives to create a 2-way mirror is shown in
Figure 8-20.
Figure 8-20 Mirror drive member selection
Chapter 8. Implementing the Vicom Fibre Channel SLIC Router
821
Below each window there is a Capacity window that will display the size of the
available drive, or of the mirror drive. Each drive that participates in a mirror
should be of equal capacity. If you select a drive that has a greater capacity and
add it to the mirror, the mirror capacity will still be the smaller of the two, and the
rest of the capacity of the larger drive will be unused. For example, if you added
a 18 GB drive to the mirror in Figure 8-20, the Mirror Capacity window would still
show the capacity of 8,696 MB. Approximately half of the 18 GB drive will be
unused.
After all drives have been added, click Next> and you will be able to add a
dedicated spare drive to the mirror if desired. Highlight one of the remaining
available drives, click Add>> and its name will appear in the Mirror Drive
Dedicated Spare window, as shown in Figure 8-21.
Figure 8-21 Adding a dedicated spare
Click the Next> button and the properties of the mirror drive can be changed.
The properties that can be changed are the FC LUN and the Drive Name. There
will be a suggested LUN number in this field that can be accepted. If not, simply
type in the desired LUN number. A name can also be defined to the mirror drive
for easier identification, with a limit of up to eight characters.
The Initialization Method box refers to whether or not to allow the operating
system to write its signature on the Mirror drive.
822
IBM SAN Implementation
The Assigning Mirror Drive Properties window is shown in Figure 8-22.
Figure 8-22 Mirror drive properties
Click the Next> button and a dialog box appears to allow you to create another
mirror drive. Click Yes, if you would like to create another mirror drive, and the
Mirror Drive List window opens, and the steps described above can be repeated.
Click Finish when you have created all the desired mirror drives. Up to this point,
the configuration has been kept within the SLIC Manager software. When the
Finish button is clicked, the SLIC Manager will now communicate to the Router
to complete the process and update the Router to control the drives.
If Quick Initialize in the Initialization Method box was selected, the Router will
take a short period of time to write the host signature and build the mirror. During
this time if you try to communicate to the Router, you may experience a slower
than normal response.
Chapter 8. Implementing the Vicom Fibre Channel SLIC Router
823
8.6.2 Mirror drive properties
If you go to the Control Center window by selecting Tools -> Control Center,
you will see that the mirror drive is now displayed in the Mirror Drive window.
This is shown in Figure 8-23.
Figure 8-23 Control Center with Mirror Drive
824
IBM SAN Implementation
If you select and highlight the mirror drive and then click the Properties button,
the Mirror Properties window opens, and you can see the information in the
mirror drive. Figure 8-24 shows an example of the properties of the mirror drive.
Figure 8-24 Mirror Drive Properties
Clicking on the Identify Mirror button will cause the LED on the actual SSA
drives that belong to the mirror, to flash. If a member drive is selected and the
Identify Member button is chosen, then the LED only on that drive will flash. In
both cases, a dialog box appears to allow you to stop the flashing.
8.7 Instant Copy drive
Instant Copy is a feature that allows a drive to become part of a mirror,
synchronize to the latest data, and then detach from the mirror. The drive can
then be used to back up the data or used elsewhere if desired.
Chapter 8. Implementing the Vicom Fibre Channel SLIC Router
825
8.7.1 Creating an Instant Copy drive
To create an Instant Copy drive, select Tools -> Instant Copy Drive Setup
Wizard. You will see a dialog box, Instant Copy Drive List, that will be blank. If
there were copy drives created, it would display the names of the drives. Click the
Next>> button and the Instant Copy Drive Members Selection window is
displayed. The window on the left named Available Drive Pool contains a list off
all drives that are candidates to become a copy drive.
Select a drive by highlighting it and click the Add>> button. The drive name will
be added to the Member window. An asterisk will appear on the left hand side of
the drive just selected in the Available Drive window to denote that the drive has
been selected. An example is shown in Figure 8-25.
Figure 8-25 Instant Copy Drive Member Selection
To remove a drive from the Member window, select the desired drive and click the
Remove<< button. Below each window there is a Drive Capacity box. As a drive
is selected, its capacity in megabytes is shown. Click the Next> button to
continue to the Assigning Instant Copy Drive Properties window, as shown in
Figure 8-26.
826
IBM SAN Implementation
Figure 8-26 Instant Copy Drive Properties
The properties that can be changed are the FC LUN and the Drive Name. There
will be a suggested LUN number in this field that can be accepted. If not, simply
type in the desired LUN number. A name can also be defined to the copy drive
for easier identification, with a limit of up to eight characters.
Click the Next> button and a dialog box appears to allow you to create another
copy drive. Click Yes if you would like to create another copy drive and the
Instant Copy Drive List window opens, and the steps described above can be
repeated.
Click Finish when you have created all the desired copy drives. Up to this point,
the configuration has been kept within the SLIC Manager software. When the
Finish button is clicked, the SLIC Manager will now communicate to the Router
to complete the process and update the Router to control the drives.
8.7.2 Instant copy drive properties
You can go to the Control Center window by selecting Tools -> Control Center.
The copy drive that was created above can now be seen in the Mirror
Drive/Instant Copy window, as shown in Figure 8-27.
Chapter 8. Implementing the Vicom Fibre Channel SLIC Router
827
Figure 8-27 Control Center with Instant Copy Drive
Notice that in the information provided for the copy drive, there is an IC included
to distinguish between mirror drives and copy drives within this window.
8.7.3 Adding an Instant Copy Drive to a mirror
To add or detach the copy drive from a mirror, you select and highlight the mirror
drive, and then click the Properties button. The Mirror Drive Properties window
opens, as shown in Figure 8-24 on page 825. Click the Add Member button and
the Add Mirror Member window opens, as shown in Figure 8-28.
828
IBM SAN Implementation
Figure 8-28 Add Mirror Member display
Select and highlight the copy drive from the Available Drive Pool window, click
the Add Member button, and the name of the copy drive will appear in the New
Mirror Member window. This is shown in Figure 8-29.
Figure 8-29 Adding drive members to a mirror
Chapter 8. Implementing the Vicom Fibre Channel SLIC Router
829
Click the OK button, and the Mirror Drive Properties will now reflect the change,
as shown in Figure 8-30.
Figure 8-30 Mirror drive properties with copy drive attached
Click OK to complete the process.
8.7.4 Detach Instant Copy Drive from a mirror
To detach, or split off the copy drive from the mirror, the procedure is similar
except at the Mirror Drive Properties window, select Delete Member. A window
will appear that displays all current members of the Mirror. Select the Copy
drive, and then delete it from the Mirror. The Copy drive can now be accessed
by another host.
8.8 Combining composite and mirroring
The SLIC Manager can also be used to combine the two features of the Router.
You can create a mirror drive using composite drives. A mirror can have drive
members of different sizes, but the actual mirror capacity will be the smaller of
the drive sizes.
830
IBM SAN Implementation
8.8.1 Creating a second composite drive
To provide an example of a mirror using only composite drives, another
composite drive is required. The example shown in Figure 8-31 shows that drive
6 and 7 were used to create another composite drive.
Figure 8-31 Creating composite drive to be used in a mirror
Chapter 8. Implementing the Vicom Fibre Channel SLIC Router
831
Follow the steps to create a composite drive as described in 8.5, “Composite
drive” on page 815. Once created, you can view the Control Center window by
selecting Tools -> Control Center from the toolbar. Figure 8-32 shows that
there are now two composite drives.
Figure 8-32 Control Center with two composite drives
832
IBM SAN Implementation
8.8.2 Creating the mirror
The mirror can now be created by selecting Tools -> Mirror Drive Setup
Wizard. When the Member Selection window appears, select the composite
drives as members of a mirror. Figure 8-33 shows where composite drives
‘ITSO1’ and ‘ITSO3’ are selected as members of a mirror.
Figure 8-33 Creating mirror drive from two composite drives
Continue through the Mirror Drive Setup Wizard to complete the process as
described in 8.6, “Mirror drive” on page 820.
Chapter 8. Implementing the Vicom Fibre Channel SLIC Router
833
8.8.3 Viewing mirror drive using composite drives
With the Mirror Drive Setup Wizard completed, you can now view the Control
Center window once again, as shown in Figure 8-34.
Figure 8-34 Control Center with mirror drive using two composite drives
834
IBM SAN Implementation
In the Mirror Drive window, you can see the new mirror drive that was created
above and named CompMir. In the Composite Drive window you can see that
there are still the two composite drives, but instead of having Fibre Channel LUN
numbers assigned to them, they are shown as belonging to a mirror with the
name CompMir.
You can highlight the CompMir drive and click the Properties button. All the
same functions that were described in 8.6.2, “Mirror drive properties” on
page 824 are available.
8.9 Reusing logical drives
At some point the composite, mirror, and instant copy logical drives that have
created may be no longer required. The logical drive can be removed so that the
member drives that made up the logical drive can then be used individually or
reconfigured to make new logical drives.
8.9.1 Remove a logical drive
To remove a logical drive, you access the Control Center by selecting Tools ->
Control Center from the top toolbar. At the Control Center window, select the
logical drive (composite, mirror, or copy) that you want to remove. Select the
Remove Logical Drive button on the right hand side and a dialog box appears
that will ask you to confirm that you want to remove the logical drive.
Once it is removed, the member drives will become general spares and will show
up in the General Spare Drive window of the Control Center. This is shown in
Figure 8-35.
Chapter 8. Implementing the Vicom Fibre Channel SLIC Router
835
Figure 8-35 Removing a logical drive
The logical drive that was created as an Instant Copy Drive in 8.7.1, “Creating an
Instant Copy drive” on page 826, has been removed and is now a general spare.
836
IBM SAN Implementation
8.9.2 Mapping a general spare
You will notice in Figure 8-35 that the general spare does not have a LUN
number assigned to it. To get a new LUN number for this drive, you select the
drive and click the Properties button.
The Drive Properties window appears; select the Change FC button. A dialog
box opens, as shown in Figure 8-36.
Figure 8-36 Mapping a general spare
The Original Mapping box will indicate that no LUN was assigned previously.
Click the Get New Mapping button, and the next sequential available LUN
number will appear in the New Mapping box. Click OK. The drive will now appear
in the Physical Drive window of the Control Center.
This can also be used to modify the LUN number on an existing mapped drive,
as well as remove the LUN number to ‘unmap’ a drive and create a general
spare.
It is not necessary to map a general spare. A general spare can be used to
creating a composite, mirror, or copy drive. Mapping a general spare will create a
drive that has a LUN number that can then be used by the host.
8.9.3 Removing a mirror containing composite drive
The mirror in this case was made from logical drives on their own. Once the
mirror is removed, the composite drives that made up the mirror will return to the
Composite Drive window as viewed from the Control Center.
Chapter 8. Implementing the Vicom Fibre Channel SLIC Router
837
However, since each composite drive had its attributes changed as it became a
member of the mirror, it will no longer be mapped. The composite drives will
show up as UnMapped in the Control Center window. This is shown in
Figure 8-37. The mirror created in 8.8.2, “Creating the mirror” on page 833 was
removed.
Figure 8-37 UnMapped composite drives
The existing composite drives ‘ITSO1’ and ‘ITSO3’ cannot be mapped or given a
new LUN number at this point. Each logical composite drive must be removed as
well. This will cause the composite drive to be removed and its member drives to
become general spares. Once they are general spares, the drives can be used to
recreate the composite drive or to create new logical drives.
838
IBM SAN Implementation
8.10 Expanding the SLIC system
The SLIC storage system can be expanded to add more SSA disks or more SLIC
Routers. Each SLIC storage system can support up to 64 SSA disks and have 16
Routers.
8.10.1 Adding disk
To add disk to an existing SLIC system is very easy, because they are SSA disks
and the rules for SSA disks apply here as well.
If there is a dummy drive in an existing SSA drawer, then it can be replaced by a
real drive. If a new drawer has to be added, the SSA cabling is changed to
include this new drawer.
Because this is SSA, this can be done on the fly. As the SSA loop is broken, the
Router will still access all disks due to the structure of the SSA loop. If possible,
we recommended that you stop host access and power down the loop. In any
case, the rules regarding SSA disks and cabling must be adhered.
As disks are added to an existing loop, the new disks will be recognized. If all
disks in the loop are used as single disks (JBOD) and have LUN numbers
assigned, the new disks added will have LUN numbers assigned to them
automatically. If there are any composite, mirror, instant copy, or spare drives in
the loop, then the new disks will not have LUN numbers assigned and become
general spares.
8.10.2 Adding Routers
By adding Routers we can increase the amount of storage a host can access and
increase throughput. On the rear panel of the Router, there are two Fibre
Channel GBIC ports that are available and act as a mini-hub.
You can add a Fibre Channel cable from the second port on the existing Router
to one of the ports on the second Router. You are basically daisy-chaining the
Routers. But since the ports on the Router act as a hub, an arbitrated loop is
created. However, in this scenario there is only one Fibre Channel cable from the
host to the Router and it is a single point of failure.
Another option is to add a second Fibre Channel host adapter that will connect to
the other Router. This provides a high availability feature, because there are now
two paths to the storage system. Software must be used for automatic failover
and load balancing between the two Fibre Channel host adapters. Failover also
can be done manually if so desired.
Chapter 8. Implementing the Vicom Fibre Channel SLIC Router
839
On the SSA side, there are a few options available. Each Router can have its
own SSA loop so that each one can support 64 SSA disks. In this way, storage
capacity is scalable, because it can be increased by adding more Routers. This
is shown in Figure 8-38.
Server
Fibre Channel
Vicom SLIC
Router
Vicom SLIC
Router
A1
A2
A1
SSA Disks
A2
SSA Disks
Figure 8-38 Increasing storage capacity
The other option is to have each additional Router added to the same SSA loop.
Throughput to the SSA loop will increase, because each Router can access the
disks for multiple simultaneous operations. This configuration is shown in
Figure 8-39.
Server
Fibre Channel
Vicom SLIC
Router
A1
A2
SSA Disks
Figure 8-39 Increasing throughput
840
IBM SAN Implementation
Vicom SLIC
Router
A1
A2
SSA Disks
Installing additional Routers
With the existing Router and storage system powered on:
1. The node map on the new Router must be cleared first.
2. Connect the Router to the existing system with the power off.
3. Set SW2 to mode 3 and set SW1 to an unique Fibre Channel target ID.
4. Power on the new Router.
5. When the Status LED on the new Router is on (solid lit), the install is
complete.
When the new Router is powered on, communication between the two Routers
will occur to query and update the new Router. The new Router will be added as
a subordinate so that the first Router will maintain its master status.
Any configuration changes to the storage system is always done on the master.
As this is done, the changes are also communicated to the subordinate Routers
so that all systems in the loop are aware of what is happening.
Using SLIC Manager on additional Routers
Since the master Router does all the work, it is not necessary to use SLIC
Manager to view the new Router. However, depending on how the new Router is
used this may become a requirement. The same daemon used to connect to the
first Router can be used to connect to several Routers.
The configuration file is edited again and the process to name and create a SLIC
zone on this new Router can be added within the same file. The SLIC Manager
software can now be used to communicate to the new Router.
The SLIC Manager can only communicate to a single Router at a time. Multiple
SLIC Manager sessions can be started to communicate to each Router.
Master failover
If at some time the Router that is designated as the master within the SLIC
storage system fails, the master designation will failover to next nearest Router.
This is accomplished within the communications between the Routers and it is
done automatically.
When the new Router accepts becoming master, it will maintain the master role if
even the failed Router is replaced and rejoins the storage system. The master
role can be changed back to the original Router, or to another Router if desired,
using the SLIC Manager software.
There is no capability to select a specific “failover” Router.
Chapter 8. Implementing the Vicom Fibre Channel SLIC Router
841
8.10.3 Adding hosts
The SLIC storage system can be expanded to include more hosts whether they
are homogeneous or heterogeneous. It is recommended that as hosts are
added, each host is connected to its own and separate SLIC Router.
If more than one host was connected to a single Router, there will be arbitration
and performance issues. Also, it would have a single point of failure with the
possibility of losing data access to many systems.
Homogeneous hosts
If another host of is added and you would like to have both hosts access the
same disks, then some sort of access sharing software must be loaded onto both
hosts.
If other hosts are added to the storage system and they will not share data, but
are connected for storage consolidation, there are a few issues to be considered
as the Router does not provide a LUN masking capability.
In UNIX systems, the hosts will see all disk in the loop. But, if the specific volume
is not mounted there will be no data integrity problems.
For Windows NT, each host will write its own signature on all available disk.
Adding another Windows NT host to the loop will cause problems. To allow a
specific Router, and host attached to that Router, access to a specific disk or set
of disks, you can set Private Attributes on the disks.
Private Attributes is a setting within SLIC manager that can set a disk to only be
accessed by a certain Router and in turn the host attached to that Router.
Note: For more information and operation on the Private Attributes setting,
please refer to the SLIC Manager Installation and User Guide, 310-605807
In all cases, if extra control for disk access is required, a third party software,
such as Tivoli SANergy, must be used.
Heterogeneous hosts
As the Router does not provide for LUN masking, you must use the SLIC
Manager Private Attribute setting or a third party software, such as Tivoli
SANergy, to restrict and control host access to the disk. The Private Attributes
and Tivoli SANergy can be used together for added control.
842
IBM SAN Implementation
Related publications
The publications listed in this section are considered particularly suitable for a
more detailed discussion of the topics covered in this redbook.
IBM Redbooks
For information on ordering these publications, see “How to get IBM Redbooks”
on page 847.
 IBM SAN Survival Guide, SG24-6143
 IBM SAN Survival Guide Featuring the IBM 2109, SG24-6127
 IBM SAN Survival Guide Featuring the INRANGE Portfolio, SG24-6150
 IBM SAN Survival Guide Featuring the McDATA Portfolio, SG24-6149
 Designing an IBM Storage Area Network, SG24-5758
 Planning and Implementing an IBM SAN, SG24-6116
 Introduction to Storage Area Network, SAN, SG24-5470
 IBM Storage Solutions for Server Consolidation, SG24-5355
 Implementing the Enterprise Storage Server in Your Environment,
SG24-5420
 Storage Area Networks: Tape Future In Fabrics, SG24-5474
 IBM Enterprise Storage Server, SG24-5465
Other resources
These publications are also relevant as further information sources:
 Building Storage Networks, ISBN 0072120509
These IBM publications are also relevant as further information sources:
 ESS Web Interface User’s Guide for ESS Specialist and ESS Copy Services,
SC26-7346
 IBM Storage Area Network Data Gateway Installation and User’s Guide,
SC26-7304
 IBM 2109 Model S08 User’s Guide, SC26-7349
© Copyright IBM Corp. 2001
843
 IBM 2109 Model S08 Switch Service Guide, SC26-7350
 IBM 2109 S16 Switch User's Guide, SC26-7351
 IBM 2109 S16 Switch Service Guide, SC26-7352
 IBM Enterprise Storage Server Configuration Planner, SC26-7353
 IBM Enterprise Storage Server Quick Configuration Guide, SC26-7354
 IBM SAN Fibre Channel Managed Hub 3534 Service Guide, SY27-7616
 IBM SAN Fibre Channel Managed Hub 3534 User’s Guide, GC26-7391
 IBM Enterprise Storage Server Introduction and Planning Guide, 2105
Models E10, E20, F10 and F20, GC26-7294
 IBM Enterprise Storage Server User’s Guide, 2105 Models E10, E20, F10
and F20, SC26-7295
 IBM Enterprise Storage Server Host Systems Attachment Guide, 2105
Models E10, E20, F10 and F20, SC26-7296
 IBM Enterprise Storage Server SCSI Command Reference, 2105 Models
E10, E20, F10 and F20, SC26-7297
 IBM Enterprise Storage Server System/390 Command Reference, 2105
Models E10, E20, F10 and F20, SC26-7298
 IBM Storage Solutions Safety Notices, GC26-7229
 Translated External Devices/Safety Information, SA26-7003
 Electrical Safety for IBM Customer Engineers, S229-8124
 SLIC Router Installation and Users Guide, 310-605759
 SLIC Manager Installation and User Guide, 310-605807
These INRANGE publications are also relevant as further information sources:
 IN-VSN FC/9000 Fibre Channel Director Installation Manual, 9110461-102
 FC/9000 Fibre Channel Director Site Planning Guide, 9110460-101
 FC/9000 Fibre Channel Director Maintenance Manual, 9110774-307
 IN-VSN Enterprise Manager (IN-VSN EM) Software Installation and
Operation Guide, 9110509-203
The JNI publications which are also relevant as further information sources are
available on the Web at:
 http://www.jni.com/Support/installguides.cfm
844
IBM SAN Implementation
These McDATA publications are also relevant as further information sources:
 ED-5000 Director Planning Manual, 620-005000
 Enterprise Fabric Connectivity Manager User Manual, 620-005001
 ED-5000 Director User Manual, 620-005002
 ED-5000 Director Service Manual, 620-005004
 ED-6064 Director Planning Manual, 620-000106-100
 ED-6064 Director User Manual, 620-000107
 ED-6064 Director Installation and Service Manual, 620-000108
 Enterprise Fabric Connectivity Manager User Manual, 620-005001
 FC-512 Fabricenter Equipment Cabinet Installation and Service Manual,
620-000100
 ES-3016 Switch Planning Manual, 620-000110-100
 ES-3016 Switch User Manual, 620-000111
 ES-3016 Switch Installation and Service Manual, 620-000112
 ES-3032 Switch Planning Manual, 620-000118-000
 ES-3032 Switch User Manual, 620-000117-000
 ES-3032 Switch Installation and Service Manual, 620-000116-000
 ES-1000 Switch Planning Manual, 620-000102-000
 ES-1000 Switch User Manual, 620-000103
 ES-1000 Switch Installation and Service Manual, 620-000105
These QLogic publications are also relevant as further information sources:
 QLA2200 Hardware Manual, FC0151103-00
 QLA2200 Hardware Manual, FC0151103-00
 QLA2100 Software Manual, FC0153301-00
 QLA2100 Hardware Manual, FC0151102-00
 QMS V1 Installation Guide, FC0051104-00
 QLview for Fibre Operations Guide, FC0051101-00
 QLconfig Operations Guide, FC0051102-00
Related publications
845
Referenced Web sites
These Web sites are also relevant as further information sources:
 www.storage.ibm.com/ibmsan/index.htm
IBM Enterprise SAN
 www.storage.ibm.com/hardsoft/products/fchub/fchub.htm
IBM Fibre Channel Storage HUB
 www.pc.ibm.com/ww/netfinity/san
IBM Storage Area Networks: Nefinity Servers
 www.storage.ibm.com/hardsoft/products/fcswitch/fcswitch.htm
IBM SAN Fibre Channel Switch
 www.storage.ibm.com/hardsoft/products/sangateway/supserver.htm
IBM SAN Data Gateway
 www.storage.ibm.com/hardsoft/products/tape/ro3superserver.htm IBM
SAN Data Gateway Router
 www.storage.ibm.com/hardsoft/products/fcss/fcss.htm
IBM Fibre Channel RAID Storage Server
 www.storage.ibm.com/hardsoft/products/ess/ess.htm
Enterprise Storage Server
 www.brocade.com
Brocade Communications Systems, Inc.
 www.cdp.com
Columbia Data Products, Inc.
 www.emulex.com
Emulex Corporation
 www.fibrechannel.com
Fibre Channel Industry Association
 www.jni.com
JNI Corporation
 www.inrange.com
INRANGE Technologies Corporation
 www.mcdata.com
McDATA Corporation
 www.pathlight.com
Pathlight
 www.qlogic.com
QLogic Corporation
846
IBM SAN Implementation
 www.sanergy.com
Tivoli SANergy
 www.snia.org
Storage Networking Industry Association
 www.tivoli.com
Tivoli
 www.t11.org
Technical Committee T11
 www.vicom.com
Vicom Systems
 www.vixel.com
Vixel
 www.scsita.org
SCSI Trade Association
 www.futureio.org
InfiniBand (SM) Trade Association
 www.nsic.org
National Storage Industry Consortium
 www.ietf.org
Internet Engineering Task Force
 www.ansi.org
American National Standards Institute
 www.standards.ieee.org
Institute of Electrical and Electronics Engineers
 www.pc.ibm.com/us
US Personal Systems Group
How to get IBM Redbooks
Search for additional Redbooks or redpieces, view, download, or order hardcopy
from the Redbooks Web site:
ibm.com/redbooks
Also download additional materials (code samples or diskette/CD-ROM images)
from this Redbooks site.
Related publications
847
Redpieces are Redbooks in progress; not all Redbooks become redpieces and
sometimes just a few chapters will be published this way. The intent is to get the
information out much quicker than the formal publishing process allows.
IBM Redbooks collections
Redbooks are also available on CD-ROMs. Click the CD-ROMs button on the
Redbooks Web site for information about all the CD-ROMs offered, as well as
updates and formats.
848
IBM SAN Implementation
Special notices
References in this publication to IBM products, programs or services do not imply
that IBM intends to make these available in all countries in which IBM operates.
Any reference to an IBM product, program, or service is not intended to state or
imply that only IBM's product, program, or service may be used. Any functionally
equivalent program that does not infringe any of IBM's intellectual property rights
may be used instead of the IBM product, program or service.
Information in this book was developed in conjunction with use of the equipment
specified, and is limited in application to those specific hardware and software
products and levels.
IBM may have patents or pending patent applications covering subject matter in
this document. The furnishing of this document does not give you any license to
these patents. You can send license inquiries, in writing, to the IBM Director of
Licensing, IBM Corporation, North Castle Drive, Armonk, NY 10504-1785.
Licensees of this program who wish to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact IBM Corporation, Dept.
600A, Mail Drop 1329, Somers, NY 10589 USA.
Such information may be available, subject to appropriate terms and conditions,
including in some cases, payment of a fee.
The information contained in this document has not been submitted to any formal
IBM test and is distributed AS IS. The use of this information or the
implementation of any of these techniques is a customer responsibility and
depends on the customer's ability to evaluate and integrate them into the
customer's operational environment. While each item may have been reviewed
by IBM for accuracy in a specific situation, there is no guarantee that the same or
similar results will be obtained elsewhere. Customers attempting to adapt these
techniques to their own environments do so at their own risk.
Any pointers in this publication to external Web sites are provided for
convenience only and do not in any manner serve as an endorsement of these
Web sites.
© Copyright IBM Corp. 2001
849
The following terms are trademarks of other companies:
Tivoli, Manage. Anything. Anywhere.,The Power To Manage., Anything.
Anywhere.,TME, NetView, Cross-Site, Tivoli Ready, Tivoli Certified, Planet Tivoli,
and Tivoli Enterprise are trademarks or registered trademarks of Tivoli Systems
Inc., an IBM company, in the United States, other countries, or both. In
Denmark, Tivoli is a trademark licensed from Kjøbenhavns Sommer - Tivoli A/S.
C-bus is a trademark of Corollary, Inc. in the United States and/or other
countries.
Java and all Java-based trademarks and logos are trademarks or registered
trademarks of Sun Microsystems, Inc. in the United States and/or other
countries.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of
Microsoft Corporation in the United States and/or other countries.
PC Direct is a trademark of Ziff Communications Company in the United States
and/or other countries and is used by IBM Corporation under license.
ActionMedia, LANDesk, MMX, Pentium and ProShare are trademarks of Intel
Corporation in the United States and/or other countries.
UNIX is a registered trademark in the United States and other countries licensed
exclusively through The Open Group.
SET, SET Secure Electronic Transaction, and the SET Logo are trademarks
owned by SET Secure Electronic Transaction LLC.
Other company, product, and service names may be trademarks or service
marks of others.
850
IBM SAN Implementation
Glossary
8B/10B A data encoding scheme developed by
IBM, translating byte-wide data to an encoded
10-bit format. Fibre Channel's FC-1 level defines
this as the method to be used to encode and
decode data transmissions over the Fibre
channel.
Adapter A hardware unit that aggregates other
I/O units, devices or communications links to a
system bus.
ADSM ADSTAR Distributed Storage Manager.
Agent (1) In the client-server model, the part of
the system that performs information preparation
and exchange on behalf of a client or server
application. (2) In SNMP, the word agent refers to
the managed system. See also: Management
Agent
AIT Advanced Intelligent Tape - A magnetic tape
format by Sony that uses 8mm cassettes, but is
only used in specific drives.
AL See Arbitrated Loop
ANSI American National Standards Institute - The
primary organization for fostering the
development of technology standards in the
United States. The ANSI family of Fibre Channel
documents provide the standards basis for the
Fibre Channel architecture and technology. See
FC-PH
Arbitration The process of selecting one
respondent from a collection of several
candidates that request service concurrently.
Arbitrated Loop A Fibre Channel
interconnection technology that allows up to 126
participating node ports and one participating
fabric port to communicate.
ATL Automated Tape Library - Large scale tape
storage system, which uses multiple tape drives
and mechanisms to address 50 or more
cassettes.
© Copyright IBM Corp. 2001
ATM Asynchronous Transfer Mode - A type of
packet switching that transmits fixed-length units
of data.
Backup A copy of computer data that is used to
recreate data that has been lost, mislaid,
corrupted, or erased. The act of creating a copy
of computer data that can be used to recreate
data that has been lost, mislaid, corrupted or
erased.
Bandwidth Measure of the information capacity
of a transmission channel.
Bridge (1) A component used to attach more
than one I/O unit to a port. (2) A data
communications device that connects two or
more networks and forwards packets between
them. The bridge may use similar or dissimilar
media and signaling systems. It operates at the
data link level of the OSI model. Bridges read and
filter data packets and frames.
Bridge/Router A device that can provide the
functions of a bridge, router or both concurrently.
A bridge/router can route one or more protocols,
such as TCP/IP, and bridge all other traffic. See
also: Bridge, Router
Broadcast Sending a transmission to all N_Ports
on a fabric.
Channel A point-to-point link, the main task of
which is to transport data from one point to
another.
Channel I/O A form of I/O where request and
response correlation is maintained through some
form of source, destination and request
identification.
CIFS Common Internet File System
Class of Service A Fibre Channel frame delivery
scheme exhibiting a specified set of delivery
characteristics and attributes.
851
Class-1 A class of service providing dedicated
connection between two ports with confirmed
delivery or notification of non-deliverability.
Class-2 A class of service providing a frame
switching service between two ports with
confirmed delivery or notification of
non-deliverability.
Class-3 A class of service providing frame
switching datagram service between two ports or
a multicast service between a multicast originator
and one or more multicast recipients.
Class-4 A class of service providing a fractional
bandwidth virtual circuit between two ports with
confirmed delivery or notification of
non-deliverability.
Class-6 A class of service providing a multicast
connection between a multicast originator and
one or more multicast recipients with confirmed
delivery or notification of non-deliverability.
Client A software program used to contact and
obtain data from a server software program on
another computer -- often across a great
distance. Each client program is designed to work
specifically with one or more kinds of server
programs and each server requires a specific
kind of client program.
Client/Server The relationship between
machines in a communications network. The
client is the requesting machine, the server the
supplying machine. Also used to describe the
information management relationship between
software components in a processing system.
Cluster A type of parallel or distributed system
that consists of a collection of interconnected
whole computers and is used as a single, unified
computing resource.
Coaxial Cable A transmission media (cable)
used for high speed transmission. It is called
coaxial because it includes one physical channel
that carries the signal surrounded (after a layer of
insulation) by another concentric physical
channel, both of which run along the same axis.
The inner channel carries the signal and the outer
channel serves as a ground.
852
IBM SAN Implementation
Controller A component that attaches to the
system topology through a channel semantic
protocol that includes some form of
request/response identification.
CRC Cyclic Redundancy Check - An
error-correcting code used in Fibre Channel.
DASD Direct Access Storage Device - any
on-line storage device: a disc, drive or CD-ROM.
DAT Digital Audio Tape - A tape media
technology designed for very high quality audio
recording and data backup. DAT cartridges look
like audio cassettes and are often used in
mechanical auto-loaders. typically, a DAT
cartridge provides 2GB of storage. But new DAT
systems have much larger capacities.
Data Sharing A SAN solution in which files on a
storage device are shared between multiple
hosts.
Datagram Refers to the Class 3 Fibre Channel
Service that allows data to be sent rapidly to
multiple devices attached to the fabric, with no
confirmation of delivery.
dB Decibel - a ratio measurement distinguishing
the percentage of signal attenuation between the
input and output power. Attenuation (loss) is
expressed as dB/km
Disk Mirroring A fault-tolerant technique that
writes data simultaneously to two hard disks
using the same hard disk controller.
Disk Pooling A SAN solution in which disk
storage resources are pooled across multiple
hosts rather than be dedicated to a specific host.
DLT Digital Linear Tape - A magnetic tape
technology originally developed by Digital
Equipment Corporation (DEC) and now sold by
Quantum. DLT cartridges provide storage
capacities from 10 to 35GB.
E_Port Expansion Port - a port on a switch used
to link multiple switches together into a Fibre
Channel switch fabric.
ECL Emitter Coupled Logic - The type of
transmitter used to drive copper media such as
Twinax, Shielded Twisted Pair, or Coax.
Enterprise Network A geographically dispersed
network under the auspices of one organization.
Entity In general, a real or existing thing from the
Latin ens, or being, which makes the distinction
between a thing's existence and it qualities. In
programming, engineering and probably many
other contexts, the word is used to identify units,
whether concrete things or abstract ideas, that
have no ready name or label.
ESCON Enterprise System Connection
Exchange A group of sequences which share a
unique identifier. All sequences within a given
exchange use the same protocol. Frames from
multiple sequences can be multiplexed to prevent
a single exchange from consuming all the
bandwidth. See also: Sequence
F_Node Fabric Node - a fabric attached node.
F_Port Fabric Port - a port used to attach a Node
Port (N_Port) to a switch fabric.
Fabric Fibre Channel employs a fabric to connect
devices. A fabric can be as simple as a single
cable connecting two devices. The term is most
often used to describe a more complex network
utilizing hubs, switches and gateways.
Fabric Login Fabric Login (FLOGI) is used by an
N_Port to determine if a fabric is present and, if
so, to initiate a session with the fabric by
exchanging service parameters with the fabric.
Fabric Login is performed by an N_Port following
link initialization and before communication with
other N_Ports is attempted.
FC Fibre Channel
FC-0 Lowest level of the Fibre Channel Physical
standard, covering the physical characteristics of
the interface and media
FC-1 Middle level of the Fibre Channel Physical
standard, defining the 8B/10B encoding/decoding
and transmission protocol.
FC-2 Highest level of the Fibre Channel Physical
standard, defining the rules for signaling protocol
and describing transfer of frame, sequence and
exchanges.
FC-3 The hierarchical level in the Fibre Channel
standard that provides common services such as
striping definition.
FC-4 The hierarchical level in the Fibre Channel
standard that specifies the mapping of
upper-layer protocols to levels below.
FCA Fiber Channel Association.
FC-AL Fibre Channel Arbitrated Loop - A
reference to the Fibre Channel Arbitrated Loop
standard, a shared gigabit media for up to 127
nodes, one of which may be attached to a switch
fabric. See also: Arbitrated Loop.
FC-CT Fibre Channel common transport protocol
FC-FG Fibre Channel Fabric Generic - A
reference to the document (ANSI X3.289-1996)
which defines the concepts, behavior and
characteristics of the Fibre Channel Fabric along
with suggested partitioning of the 24-bit address
space to facilitate the routing of frames.
FC-FP Fibre Channel HIPPI Framing Protocol - A
reference to the document (ANSI X3.254-1994)
defining how the HIPPI framing protocol is
transported via the fibre channel
FC-GS Fibre Channel Generic Services -A
reference to the document (ANSI X3.289-1996)
describing a common transport protocol used to
communicate with the server functions, a full
X500 based directory service, mapping of the
Simple Network Management Protocol (SNMP)
directly to the Fibre Channel, a time server and
an alias server.
FC-LE Fibre Channel Link Encapsulation - A
reference to the document (ANSI X3.287-1996)
which defines how IEEE 802.2 Logical Link
Control (LLC) information is transported via the
Fibre Channel.
FC-PH A reference to the Fibre Channel Physical
and Signaling standard ANSI X3.230, containing
the definition of the three lower levels (FC-0,
FC-1, and FC-2) of the Fibre Channel.
FC-PLDA Fibre Channel Private Loop Direct
Attach - See PLDA.
FC-SB Fibre Channel Single Byte Command
Code Set - A reference to the document (ANSI
Glossary
853
X.271-1996) which defines how the ESCON
command set protocol is transported using the
fibre channel.
FSP Fibre Channel Service Protocol - The
common FC-4 level protocol for all services,
transparent to the fabric type or topology.
FC-SW Fibre Channel Switch Fabric - A
reference to the ANSI standard under
development that further defines the fabric
behavior described in FC-FG and defines the
communications between different fabric
elements required for those elements to
coordinate their operations and management
address assignment.
Full-Duplex A mode of communications allowing
simultaneous transmission and reception of
frames.
G_Port Generic Port - a generic switch port that
is either a Fabric Port (F_Port) or an Expansion
Port (E_Port). The function is automatically
determined during login.
FC Storage Director See SAN Storage Director
Gateway A node on a network that interconnects
two otherwise incompatible networks.
FCA Fibre Channel Association - a Fibre Channel
industry association that works to promote
awareness and understanding of the Fibre
Channel technology and its application and
provides a means for implementers to support the
standards committee activities.
Gb/s Gigabits per second. Also sometimes
referred to as Gbps. In computing terms it is
approximately 1,000,000,000 bits per second.
Most precisely it is 1,073,741,824 (1024 x 1024 x
1024) bits per second.
FCLC Fibre Channel Loop Association - an
independent working group of the Fibre Channel
Association focused on the marketing aspects of
the Fibre Channel Loop technology.
GB/s Gigabytes per second. Also sometimes
referred to as GBps. In computing terms it is
approximately 1,000,000,000 bytes per second.
Most precisely it is 1,073,741,824 (1024 x 1024 x
1024) bytes per second.
FCP Fibre Channel Protocol - the mapping of
SCSI-3 operations to Fibre Channel.
Fiber Optic Refers to the medium and the
technology associated with the transmission of
information along a glass or plastic wire or fiber.
Fibre Channel A technology for transmitting data
between computer devices at a data rate of up to
4 Gb/s. It is especially suited for connecting
computer servers to shared storage devices and
for interconnecting storage controllers and drives.
FICON Fibre Connection - A next-generation I/O
solution for IBM S/390 parallel enterprise server.
FL_Port Fabric Loop Port - the access point of
the fabric for physically connecting the user's
Node Loop Port (NL_Port).
FLOGI See Fabric Log In
Frame A linear set of transmitted bits that define
the basic transport unit. The frame is the most
basic element of a message in Fibre Channel
communications, consisting of a 24-byte header
and zero to 2112 bytes of data. See also:
Sequence
854
IBM SAN Implementation
GBIC GigaBit Interface Converter - Industry
standard transceivers for connection of Fibre
Channel nodes to arbitrated loop hubs and fabric
switches.
Gigabit One billion bits, or one thousand
megabits.
GLM Gigabit Link Module - a generic Fibre
Channel transceiver unit that integrates the key
functions necessary for installation of a Fibre
channel media interface on most systems.
Half-Duplex A mode of communications allowing
either transmission or reception of frames at any
point in time, but not both (other than link control
frames which are always permitted).
Hardware The mechanical, magnetic and
electronic components of a system, e.g.,
computers, telephone switches, terminals and the
like.
HBA Host Bus Adapter
HIPPI High Performance Parallel Interface - An
ANSI standard defining a channel that transfers
data between CPUs and from a CPU to disk
arrays and other peripherals.
HMMP HyperMedia Management Protocol
HMMS HyperMedia Management Schema - the
definition of an implementation-independent,
extensible, common data description/schema
allowing data from a variety of sources to be
described and accessed in real time regardless of
the source of the data. See also: WEBM, HMMP
HSM Hierarchical Storage Management - A
software and hardware system that moves files
from disk to slower, less expensive storage media
based on rules and observation of file activity.
Modern HSM systems move files from magnetic
disk to optical disk to magnetic tape.
HUB A Fibre Channel device that connects nodes
into a logical loop by using a physical star
topology. Hubs will automatically recognize an
active node and insert the node into the loop. A
node that fails or is powered off is automatically
removed from the loop.
HUB Topology see Loop Topology
Hunt Group A set of associated Node Ports
(N_Ports) attached to a single node, assigned a
special identifier that allows any frames
containing this identifier to be routed to any
available Node Port (N_Port) in the set.
In-Band Signaling This is signaling that is
carried in the same channel as the information.
Also referred to as inband.
Information Unit A unit of information defined by
an FC-4 mapping. Information Units are
transferred as a Fibre Channel Sequence.
Intermix A mode of service defined by Fibre
Channel that reserves the full Fibre Channel
bandwidth for a dedicated Class 1 connection,
but also allows connection-less Class 2 traffic to
share the link if the bandwidth is available.
I/O Input/output
IP Internet Protocol
IPI Intelligent Peripheral Interface
requirements. A typical application for
isochronous transmission is a broadcast
environment which needs information to be
delivered at a predictable time.
JBOD Just a bunch of disks.
Jukebox A device that holds multiple optical
disks and one or more disk drives, and can swap
disks in and out of the drive as needed.
L_Port Loop Port - A node or fabric port capable
of performing Arbitrated Loop functions and
protocols. NL_Ports and FL_Ports are
loop-capable ports.
LAN See Local Area Network - A network
covering a relatively small geographic area
(usually not larger than a floor or small building).
Transmissions within a Local Area Network are
mostly digital, carrying data among stations at
rates usually above one megabit/s.
Latency A measurement of the time it takes to
send a frame between two locations.
Link A connection between two Fibre Channel
ports consisting of a transmit fibre and a receive
fibre.
Link_Control_Facility A termination card that
handles the logical and physical control of the
Fibre Channel link for each mode of use.
LIP A Loop Initialization Primitive sequence is a
special fibre channel sequence that is used to
start loop initialization. Allows ports to establish
their port addresses.
Local Area Network (LAN) A network covering a
relatively small geographic area (usually not
larger than a floor or small building).
Transmissions within a Local Area Network are
mostly digital, carrying data among stations at
rates usually above one megabit/s.
Login Server Entity within the Fibre Channel
fabric that receives and responds to login
requests.
Loop Circuit A temporary point-to-point like path
that allows bi-directional communications
between loop-capable ports.
Isochronous Transmission Data transmission
which supports network-wide timing
Glossary
855
Loop Topology An interconnection structure in
which each point has physical links to two
neighbors resulting in a closed circuit. In a loop
topology, the available bandwidth is shared.
LVD Low Voltage Differential
Management Agent A process that exchanges a
managed node's information with a management
station.
Managed Node A managed node is a computer,
a storage system, a gateway, a media device
such as a switch or hub, a control instrument, a
software product such as an operating system or
an accounting package, or a machine on a
factory floor, such as a robot.
Managed Object A variable of a managed node.
This variable contains one piece of information
about the node. Each node can have several
objects.
Management Station A host system that runs
the management software.
Mb/s Megabits per second. Also sometimes
referred to as Mbps. In computing terms it is
approximately 1,000,000 bits per second. Most
precisely it is 1,048,576 (1024 x 1024) bits per
second.
MB/s Megabytes per second. Also sometimes
referred to as MBps. In computing terms it is
approximately 1,000,000 bytes per second. Most
precisely it is 1,048,576 (1024 x 1024) bits per
second.
Meter 39.37 inches, or just slightly larger than a
yard (36 inches)
Media Plural of medium. The physical
environment through which transmission signals
pass. Common media include copper and fiber
optic cable.
Media Access Rules (MAR).
MIA Media Interface Adapter - MIAs enable
optic-based adapters to interface to
copper-based devices, including adapters, hubs,
and switches.
MIB Management Information Block - A formal
description of a set of network objects that can be
856
IBM SAN Implementation
managed using the Simple Network Management
Protocol (SNMP). The format of the MIB is
defined as part of SNMP and is a hierarchical
structure of information relevant to a specific
device, defined in object oriented terminology as
a collection of objects, relations, and operations
among objects.
Mirroring The process of writing data to two
separate physical devices simultaneously.
MM Multi-Mode - See Multi-Mode Fiber
MMF See Multi-Mode Fiber - - In optical fiber
technology, an optical fiber that is designed to
carry multiple light rays or modes concurrently,
each at a slightly different reflection angle within
the optical core. Multi-Mode fiber transmission is
used for relatively short distances because the
modes tend to disperse over longer distances.
See also: Single-Mode Fiber, SMF
Multicast Sending a copy of the same
transmission from a single source device to
multiple destination devices on a fabric. This
includes sending to all N_Ports on a fabric
(broadcast) or to only a subset of the N_Ports on
a fabric (multicast).
Multi-Mode Fiber (MMF) In optical fiber
technology, an optical fiber that is designed to
carry multiple light rays or modes concurrently,
each at a slightly different reflection angle within
the optical core. Multi-Mode fiber transmission is
used for relatively short distances because the
modes tend to disperse over longer distances.
See also: Single-Mode Fiber
Multiplex The ability to intersperse data from
multiple sources and destinations onto a single
transmission medium. Refers to delivering a
single transmission to multiple destination Node
Ports (N_Ports).
N_Port Node Port - A Fibre Channel-defined
hardware entity at the end of a link which
provides the mechanisms necessary to transport
information units to or from another node.
N_Port Login N_Port Login (PLOGI) allows two
N_Ports to establish a session and exchange
identities and service parameters. It is performed
following completion of the fabric login process
and prior to the FC-4 level operations with the
destination port. N_Port Login may be either
explicit or implicit.
Name Server Provides translation from a given
node name to one or more associated N_Port
identifiers.
NAS Network Attached Storage - a term used to
describe a technology where an integrated
storage system is attached to a messaging
network that uses common communications
protocols, such as TCP/IP.
NDMP Network Data Management Protocol
Network An aggregation of interconnected
nodes, workstations, file servers, and/or
peripherals, with its own protocol that supports
interaction.
Network Topology Physical arrangement of
nodes and interconnecting communications links
in networks based on application requirements
and geographical distribution of users.
NFS Network File System - A distributed file
system in UNIX developed by Sun Microsystems
which allows a set of computers to cooperatively
access each other's files in a transparent manner.
NL_Port Node Loop Port - a node port that
supports Arbitrated Loop devices.
NMS Network Management System - A system
responsible for managing at least part of a
network. NMSs communicate with agents to help
keep track of network statistics and resources.
Node An entity with one or more N_Ports or
NL_Ports.
Non-Blocking A term used to indicate that the
capabilities of a switch are such that the total
number of available transmission paths is equal
to the number of ports. Therefore, all ports can
have simultaneous access through the switch.
Non-L_Port A Node or Fabric port that is not
capable of performing the Arbitrated Loop
functions and protocols. N_Ports and F_Ports are
not loop-capable ports.
Operation A term defined in FC-2 that refers to
one of the Fibre Channel building blocks
composed of one or more, possibly concurrent,
exchanges.
Optical Disk A storage device that is written and
read by laser light.
Optical Fiber A medium and the technology
associated with the transmission of information
as light pulses along a glass or plastic wire or
fiber.
Ordered Set A Fibre Channel term referring to
four 10 -bit characters (a combination of data and
special characters) providing low-level link
functions, such as frame demarcation and
signaling between two ends of a link.
Originator A Fibre Channel term referring to the
initiating device.
Out of Band Signaling This is signaling that is
separated from the channel carrying the
information. Also referred to as outband.
Peripheral Any computer device that is not part
of the essential computer (the processor, memory
and data paths) but is situated relatively close by.
A near synonym is input/output (I/O) device.
Petard A device that is small and sometimes
explosive.
PLDA Private Loop Direct Attach - A technical
report which defines a subset of the relevant
standards suitable for the operation of peripheral
devices such as disks and tapes on a private
loop.
PLOGI See N_Port Login
Point-to-Point Topology An interconnection
structure in which each point has physical links to
only one neighbor resulting in a closed circuit. In
point-to-point topology, the available bandwidth is
dedicated.
Port The hardware entity within a node that
performs data communications over the Fibre
Channel.
Port Bypass Circuit A circuit used in hubs and
disk enclosures to automatically open or close
the loop to add or remove nodes on the loop.
Private NL_Port An NL_Port which does not
attempt login with the fabric and only
Glossary
857
communicates with other NL Ports on the same
loop.
infrastructure, which enables any-to-any
interconnection of servers and storage systems.
Protocol A data transmission convention
encompassing timing, control, formatting and
data representation.
SAN System Area Network - term originally used
to describe a particular symmetric
multiprocessing (SMP) architecture in which a
switched interconnect is used in place of a
shared bus. Server Area Network - refers to a
switched interconnect between multiple SMPs.
Public NL_Port An NL_Port that attempts login
with the fabric and can observe the rules of either
public or private loop behavior. A public NL_Port
may communicate with both private and public
NL_Ports.
Quality of Service (QoS) A set of
communications characteristics required by an
application. Each QoS defines a specific
transmission priority, level of route reliability, and
security level.
RAID Redundant Array of Inexpensive or
Independent Disks. A method of configuring
multiple disk drives in a storage subsystem for
high availability and high performance.
Raid 0 Level 0 RAID support - Striping, no
redundancy
Raid 1 Level 1 RAID support - mirroring,
complete redundancy
Raid 5 Level 5 RAID support, Striping with parity
Repeater A device that receives a signal on an
electromagnetic or optical transmission medium,
amplifies the signal, and then retransmits it along
the next leg of the medium.
Responder A Fibre Channel term referring to the
answering device.
Router (1) A device that can decide which of
several paths network traffic will follow based on
some optimal metric. Routers forward packets
from one network to another based on
network-layer information. (2) A dedicated
computer hardware and/or software package
which manages the connection between two or
more networks. See also: Bridge, Bridge/Router
SAF-TE SCSI Accessed Fault-Tolerant
Enclosures
SAN A Storage Area Network (SAN) is a
dedicated, centrally managed, secure information
858
IBM SAN Implementation
SC Connector A fiber optic connector
standardized by ANSI TIA/EIA-568A for use in
structured wiring installations.
Scalability The ability of a computer application
or product (hardware or software) to continue to
function well as it (or its context) is changed in
size or volume. For example, the ability to retain
performance levels when adding additional
processors, memory and/or storage.
SCSI Small Computer System Interface - A set of
evolving ANSI standard electronic interfaces that
allow personal computers to communicate with
peripheral hardware such as disk drives, tape
drives, CD_ROM drives, printers and scanners
faster and more flexibly than previous interfaces.
The table below identifies the major
characteristics of the different SCSI version.
SCSI
Version
SCSI
-1
SCSI
-2
Wide
SCSI
-2
Fast
SCSI
-2
Fast
Wide
SCSI
-2
Ultra
SCSI
Ultra
SCSI
-2
8
M ax.
DTR
(MB/s
)
5
Max.
Num.
Devic
es
7
Max.
Cable
Lengt
h (m)
6
5
8
5
7
6
5
16
10
15
6
10
8
10
7
6
10
16
20
15
6
20
8
20
7
1.5
20
16
40
7
12
Signal
Rate
MHz
5
BusWidth
(bits)
Ultra
2
LVD
SCSI
40
16
80
15
12
SCSI-3 SCSI-3 consists of a set of primary
commands and additional specialized command
sets to meet the needs of specific device types.
The SCSI-3 command sets are used not only for
the SCSI-3 parallel interface but for additional
parallel and serial protocols, including Fibre
Channel, Serial Bus Protocol (used with IEEE
1394 Firewire physical protocol) and the Serial
Storage Protocol (SSP).
SCSI-FCP The term used to refer to the ANSI
Fibre Channel Protocol for SCSI document
(X3.269-199x) that describes the FC-4 protocol
mappings and the definition of how the SCSI
protocol and command set are transported using
a Fibre Channel interface.
Sequence A series of frames strung together in
numbered order which can be transmitted over a
Fibre Channel connection as a single operation.
See also: Exchange
SERDES Serializer Deserializer
Server A computer which is dedicated to one
task.
SES SCSI Enclosure Services - ANSI SCSI-3
proposal that defines a command set for soliciting
basic device status (temperature, fan speed,
power supply status, etc.) from a storage
enclosures.
Single-Mode Fiber In optical fiber technology, an
optical fiber that is designed for the transmission
of a single ray or mode of light as a carrier. It is a
single light path used for long-distance signal
transmission. See also: Multi-Mode Fiber
SMART Self Monitoring and Reporting
Technology
SM Single Mode - See Single-Mode Fiber
SMF Single-Mode Fiber - In optical fiber
technology, an optical fiber that is designed for
the transmission of a single ray or mode of light
as a carrier. It is a single light path used for
long-distance signal transmission. See also:
MMF
SNIA Storage Networking Industry Association. A
non-profit organization comprised of more than
77 companies and individuals in the storage
industry.
SN Storage Network. See also: SAN
SNMP Simple Network Management Protocol The Internet network management protocol which
provides a means to monitor and set network
configuration and run-time parameters.
SNMWG Storage Network Management Working
Group is chartered to identify, define and support
open standards needed to address the increased
management requirements imposed by storage
area network environments.
SSA Serial Storage Architecture - A high speed
serial loop-based interface developed as a high
speed point-to-point connection for peripherals,
particularly high speed storage arrays, RAID and
CD-ROM storage by IBM.
Star The physical configuration used with hubs in
which each user is connected by communications
links radiating out of a central hub that handles all
communications.
StorWatch Expert These are StorWatch
applications that employ a 3 tiered architecture
that includes a management interface, a
StorWatch manager and agents that run on the
storage resource(s) being managed. Expert
products employ a StorWatch data base that can
be used for saving key management data (e.g.
capacity or performance metrics). Expert
products use the agents as well as analysis of
storage data saved in the data base to perform
higher value functions including -- reporting of
capacity, performance, etc. over time (trends),
configuration of multiple devices based on
policies, monitoring of capacity and performance,
automated responses to events or conditions,
and storage related data mining.
StorWatch Specialist A StorWatch interface for
managing an individual fibre Channel device or a
limited number of like devices (that can be
viewed as a single group). StorWatch specialists
Glossary
859
typically provide simple, point-in-time
management functions such as configuration,
reporting on asset and status information, simple
device and event monitoring, and perhaps some
service utilities.
Striping A method for achieving higher
bandwidth using multiple N_Ports in parallel to
transmit a single information unit across multiple
levels.
Topology An interconnection scheme that allows
multiple Fibre Channel ports to communicate. For
example, point-to-point, Arbitrated Loop, and
switched fabric are all Fibre Channel topologies.
T_Port An ISL port more commonly known
as an E_Port , referred to as a Trunk port and
used by INRANGE.
STP Shielded Twisted Pair
TL_Port A private to public bridging of
switches or directors, referred to as
Translative Loop.
Storage Media The physical device itself, onto
which data is recorded. Magnetic tape, optical
disks, floppy disks are all storage media.
Twinax A transmission media (cable) consisting
of two insulated central conducting leads of
coaxial cable.
Switch A component with multiple entry/exit
points (ports) that provides dynamic connection
between any two of these points.
Twisted Pair A transmission media (cable)
consisting of two insulated copper wires twisted
around each other to reduce the induction (thus
interference) from one wire to another. The
twists, or lays, are varied in length to reduce the
potential for signal interference between pairs.
Several sets of twisted pair wires may be
enclosed in a single cable. This is the most
common type of transmission media.
Switch Topology An interconnection structure in
which any entry point can be dynamically
connected to any exit point. In a switch topology,
the available bandwidth is scalable.
T11 A technical committee of the National
Committee for Information Technology Standards,
titled T11 I/O Interfaces. It is tasked with
developing standards for moving data in and out
of computers.
Tape Backup Making magnetic tape copies of
hard disk and optical disc files for disaster
recovery.
Tape Pooling A SAN solution in which tape
resources are pooled and shared across multiple
hosts rather than being dedicated to a specific
host.
TCP Transmission Control Protocol - a reliable,
full duplex, connection-oriented end-to-end
transport protocol running on top of IP.
TCP/IP Transmission Control Protocol/ Internet
Protocol - a set of communications protocols that
support peer-to-peer connectivity functions for
both local and wide area networks.
Time Server A Fibre Channel-defined service
function that allows for the management of all
timers used within a Fibre Channel system.
860
IBM SAN Implementation
ULP Upper Level Protocols
UTC Under-The-Covers, a term used to
characterize a subsystem in which a small
number of hard drives are mounted inside a
higher function unit. The power and cooling are
obtained from the system unit. Connection is by
parallel copper ribbon cable or pluggable
backplane, using IDE or SCSI protocols.
UTP Unshielded Twisted Pair
Virtual Circuit A unidirectional path between two
communicating N_Ports that permits fractional
bandwidth.
WAN Wide Area Network - A network which
encompasses inter-connectivity between devices
over a wide geographic area. A wide area
network may be privately owned or rented, but
the term usually connotes the inclusion of public
(shared) networks.
WDM Wave Division Multiplexing - A technology
that puts data from different sources together on
an optical fiber, with each signal carried on its
own separate light wavelength. Using WDM, up
to 80 (and theoretically more) separate
wavelengths or channels of data can be
multiplexed into a stream of light transmitted on a
single optical fiber.
WEBM Web-Based Enterprise Management - A
consortium working on the development of a
series of standards to enable active management
and monitoring of network-based elements.
Zoning In Fibre Channel environments, the
grouping together of multiple ports to form a
virtual private storage network. Ports that are
members of a group or zone can communicate
with each other but are isolated from ports in
other zones.
Glossary
861
862
IBM SAN Implementation
Index
Numerics
1-way mirror 820
2 Gigabit 443
2042-001 662
2103-H07 175
2109 management functions 465
2109-F16 252, 443
2109-F16 Administrative Interface 529
2109-F16 Configure 544
2109-F16 Extended Fabric 555
2109-F16 Firmware/Configuration File 533
2109-F16 installing 461
2109-F16 License Administration 538
2109-F16 Network Configuration 531
2109-F16 Port Settings 541
2109-F16 QuickLoop 551
2109-F16 Remote Switch 553
2109-F16 Report 540
2109-F16 Routing 548
2109-F16 SNMP tab 536
2109-F16 Switch Settings 530
2109-F16 Trunk Information 550
2109-F16 User Admin 543
2109-F16 zone 466
2109-F16 zone types 466
2109-S08 252
2109-S16 252
2766 adapter 10
2-way mirror 820
3527 799
3534 183
35341RU 175
3-way mirror 820
7131 799
7133 799
A
access control lists 467
access levels 94
access profile 163
Access_Any 163
Access_Restricted 163
activate hard zone layout 644
© Copyright IBM Corp. 2001
active zone sets 717
active zoning configuration 727
adapter types 2
Add Volumes 126
Adding an Instant Copy Drive to a Mirror 828
Adding Disk 839
Adding Hosts 842
Adding Routers 839
Adding SCSI devices 773
addresses assigned 457
adjacent switches 742
administer McDATA SAN 684
administering zoning 469
administrative interface 529
administrator 757
Advanced Options 764
Advanced Performance Monitoring 520, 524
AdvFS 22
Agent 755
aggregate bandwidth 509
AIX host system 15
AL_PA Level Zoning 491
AL_PA monitoring 520
alarm mechanisms 428
alarms 310
alarms config 310
alerts 435
alias 235
All or Nothing 632
anonymous host 163
Arbitrated Loop 620
arbitrated loop 167
archiving 289
areas 303
ASIC 448, 450
ASIC interrupts 458
ASICs 445, 447, 449
Assign Fibre Channel Target 802
Assigned Volumes 104
Assigning LUN IDs 773
ATM network 553
Attaching hosts 791
Auto Learning 625
Auto Sense 614
863
automatic address assignment 454
auto-negotiation 459
autonomy of routing 662
auto-sensing 444, 454
auto-sensing capability 444
auto-sensing speed negotiation 454
B
B_Port 707
bandwidth 143
bandwidth issues 734
baud 264
beaconing 212, 301
Bloom ASIC 447, 448, 456
Bloom ASICs 445
Boot Flash 445
bottlenecks 734
boundaries 307
bridge 16
bridging 860
broadcast 457
broadcast messages 633
broadcast zone 467
buffer pool 448
buffer queuing 449
buffers 448
bus operations 447
bypassed device 619
Compaq Tru64 UNIX 19
compatibility 500
composite drive 815, 830
as members of a mirror 833
properties 819
configDefault 409
configdefault 409
configuration change 406
configure 438
Configure Host Adapter Ports 159
configuredefault 438
connecting to switch 278
Control Center 811
Control Message Interface 449
control panel 262, 264
Copy Services 90
core device 665
corporate LAN 671
CPU 445
CPU subsystem 445
CRC errors 520
Create General Spares 803
create user for telnet to San Data Gateway 753
Creating A Composite Drive 815
Creating A Mirror Drive 820
Creating a SLIC Zone 808
Creating an Instant Copy drive 826
D
C
call home 86
canvas 516
canvas configurations 518
cascaded 399, 452
cascaded directors 656
central memory 448
central memory architecture 448
channel
access mode 162
channel command 5
channel path group 6
classes 303
Client 755
clustering 25
CMI 449
Combining Composite And Mirroring 830
Compaq Alpha server 18
Compaq host FC attachment 18
864
IBM SAN Implementation
daisy chained 662
data entry buttons 265
data packets 510
data signaling rate 459
dedicated LAN 674
default IP address 262
Detach Instant Copy Drive from a Mirror 830
detached node ports 723
Device discovery 772
device identification 688
device level zoning 455
device ports 662
diagnostics 458
DID 455, 521
director 664
director clock 610
director FIOs 662
director identification 696
director offline 701
disabled switch 440
disk group 113
disk groups 115, 132
disk pooling 75
distances 3
distributed fabrics 556
DNS 673, 690
domain 740
domain address manager 740
Domain ID 281
domain ID 740
Domain ID conflict 741
Domain Name System 673
download 189
DRAM 445
E
E_D_TOV 742
E_Port 233, 256, 350, 509, 695, 734
ED-5000 663
ED-6064 7, 664, 665
EFC login 683
EFC Manager 675, 676
EFC Manager client installation 676
EFC Manager Software 679
EFC monitoring 685
EFC operational status 694
EFC port number 699
EFC server 681
embedded applications 453
embedded processor 446
Emulex 46
Emulex LP8000 32, 42, 47, 53, 56, 58, 65, 67
enabling the Ethernet port 753
Enabling VPS 775
End-to-end monitoring 521
Entry Switch Activation 181
error detection time out value (E_D_TOV) 742
ES-1000 665, 668
ES-1000 managing 706
ES-3016 665, 667
ES-3016 managing 705
ES-3032 665, 667
ESCON 5, 104
ESCON directors 663
ESS 795, 797
ESS configuration update 110
ESS configuring 89
ESS Copy Server 90
ESS default user 81
ESS disk group section 100
ESS FC adapters 691
ESS FC port 98
ESS FC port access 123
ESS FC port definitions 116
ESS FC ports config 158
ESS FC ports topology 159
ESS host interfaces 97
ESS interface adapters 160
ESS introduction panel 78
ESS logical volume 130
ESS logical volume assignments 142
ESS logical volumes 126
ESS Open System Storage 104
ESS operating 82
ESS ports 99
ESS site certificate 79
ESS status 83
ESS storage allocation 103
ESS storage configuration 96
ESS Storage Server Attributes 162
ESS to FICON 7
ESS user administration 93
ESS Web Copy Services 91
ESS Web Interface 77
Ethernet port 183
ethernet port 253
Expansion Port 509
Expansion Port (E_Port) 665
extended distance buffering 741
extended fabric 296
F
F_Port 256, 350, 665
F_Ports 734
F16 443
fabric add 603
fabric events 320
fabric exploration 457
fabric login 208
Fabric Manager 715
Fabric OS 445
Fabric OS Version 3.0 452
fabric topology 322
Fabric View 280
Fabric Watch 282, 302
Index
865
fabric zoned 727
Fabricenter 669
factory default settings 409, 451
factory settings 253
Fastboot 218, 276
fault tolerance 348
fault tolerant fabric 349
FC adapters 98
FC operating parameters 701, 709
FC ports 698
FC/9000 7
FC/9000 overview 569
FC_AL 629
FC-2 456
FC-AL 167, 176, 202, 612, 665
FC-GS 456
FC-LS 456
FCM blade 659
FC-PH 456
FC-PP 167
FC-SW 167, 456
feature code 2314 7
feature code 2315 7
feature code 2316 7
feature code 2318 7
feature Code 3019 16
feature code 3021 3
feature code 3022 2
feature code 3023 3
Fibre Channel 765
Fibre Channel adapters 98
Fibre Channel host 763
fibre channel topologies 199
FICON 4, 5, 7
FICON switch cascading 7
field replacable units (FRU) 665, 666
Filter-based monitoring 521
FIO blade 630
firmware 189, 194, 575
firmware level 277
firmware levels 281
firmware upgrade 194
Fixed Block 109
Fixed Block Storage 108, 114
FL_Port 256, 350
Flannel 456
Flash File 445
FlashCopy 77
FLOGI 208
866
IBM SAN Implementation
Format the Drives 803
frame 510
frame filtering 455
frame multiplexing 6
frames 348, 448, 559
FSPF 509
full-duplex 1
G
G_Port 256
G_Ports 350, 734
Gateway address 673
GBIC 177
Generic Port (G_Port) 665
Get New Mapping 837
Gigabit Interface Converter 177
H
H_Ports 707
HACMP 734, 736
hard zone setup 643
Hard Zoning 343
Hard zoning 628
hard zoning 629
hard zoning setup 639
hardware enforced zone 467
hardware enforced zones 467
Hardware Enforced zoning 240
HBA configuration files 41
HBA interoperability 460
Heterogeneous Hosts 842
heterogeneous inter-switch operations 460
Hewlett Packard 9000 23
Hewlett Packard 9000 FC attachment 23
High availability considerations 796
Homogeneous Hosts 842
hop 657
Hop Count 359
hop count 739
host adapter 1
Host Attributes 118
host domain 322
Host information 780
Host registration 776
Hosts Systems 104
HOSTSW 776
hub 176
hub cascading 233
hub firmware upgrade 217
hub port information 225
Hub Specialist 180
hub zoning 208, 233, 234
HyperTerminal 186
I
I/O 6
I2C bus 447
IBM Enterprise Storage Server, 2105-F20 75
IBM SAN Fibre Channel Switch 785, 794
IBM SAN Fibre Channel Switch, 2109-S16 262,
264
IBM Storage Area Network Data Gateway,
2108-G07 749
IBM TotalStorage SAN Switch Specialist 445
Implementing Switch/Port Level Zoning 472
implementing zoning 469
initialization 457
Initialization Method 817
initializeBox 752
in-order delivery 510
INRANGE defining hard zoning 638
INRANGE FC/9000 567
INRANGE hard zoning 629
INRANGE hard zoning rules 630
INRANGE Name Server zoning 634
INRANGE zoning methods 629
InstallAnywhere 680
installed licenses 288
Installing additional Routers 841
installing performance monitoring 522
installing Remote Switch 558
Installing StorWatch Specialist 756
installing the 2109-F16 Switch 461
Installing the SLIC Manager 805
Installing the SLIC Router 801
Instant Copy 800, 825
Instant Copy Drive 820
Instant Copy Drive Properties 827
Inter Switch Link 655
inter switch link (ISL) 348, 350, 665
interconnected directors 7
internal fabric operation 454
Internet Explorer 279
Interop Mode 698
interoperability 460
Inter-Switch Link 398
Inter-Switch Link Trunking 444
Inter-Switch Links 292
inter-switch links 290
IN-VSN event log 661
IOC-0210-54 adapter 17
IOC-0210-54 adapter card 15, 17
IP address 183, 253, 672
setting S16 264
IP address setting 186
IP addressing information 281
IP settings 659
IP versus SCSI traffic 521
iSeries configurations 10
iSeries FC host 8
iSeries host system 8
ISL 359, 398, 440, 455, 509, 655, 695, 734, 738,
746, 860
ISL connections 739
ISL trunking 509
Isolated E_Port 256
ITSO environment 182
installation steps 568
J
Java Plug-In 1.2.2 279
JBOD 109, 115
JNI adapters 45
JNI FC64-1063 42
JNI FCI-1063 42
JNI PCI adapter 35
JNI SBUS 36
Just a Bunch Of Disks 109
L
L_Port 256
LEDs 452
legacy devices 203
legacy FC 612
LIC 88
LIC level 164
license admin 220
Licensed Internal Code 88
link extender 3
link incident 700
LIP 208, 628
load balancing 510
locating WWPN 69
logical drives 800, 835
Index
867
logical subsystems 4
logical unit number 162
Logical Volume Manager (LVM) 734, 736
login 81
logon EFC manager 682
Long Wave Length (LWL) cable 180
long-wave ports 751
Loom 456
Loop 786
loop 176
private 199
public 199
loop attachments 613
loop devices 618
Loop Initialization Primitive 628
loop mode 710
loop ports 617
Loop protocol 612
loop-free 454
looplets 202, 206
lowest-cost routes 454
LP8000 32
LUN 162
LUN access 793
LUN affinity 4
LUN level zoning 455
LUN masking 646, 751, 783, 798, 842
LUN support 772
LUN zoning 460
LUNs 4
N
M
managed hub upgrading 181
managing the hub 208
Mapping a general spare 837
Mapping Physical Drives 802
mapRebuildDatabase 773
mapShowDatabase 782
mapWinnowDatabase 773
Master Failover 841
master port 455
Master Router 813
maximum distance 3
MC/ServiceGuard 25
McDATA 663
McDATA define users 685
McDATA Enterprise Director ED-5000 663
McDATA Enterprise Fibre Channel Director 795
868
McDATA network 676
McDATA zoning 711
McDATA zoning concepts 711
memory 447
memory devices 447
MIB files 678
mini-buffers 448
Mirror Capacity 822
mirror capacity 830
Mirror drive 830
mirror drive 820
Mirror Drive Dedicated Spare 822
Mirror Drive Properties 824
Mixed Level Zoning 500
Mixed Zone 466
mixed zone 503
Modify Host Systems 117
Modify Users 94
monitored element 303
monitoring an INRANGE SAN 658
motherboard 253
multicast 457
multipathing 648
multiple controllers 6
multiple Director FRUs 662
multi-switch fabric 348
multiswitch fabric 734, 737, 742
multiswitch fabric solutions 734
multiswitch fabrics 739
IBM SAN Implementation
N_Port 256
name server 230, 324
Name server enforced zoning 712
name server table 617
Name Server zones 644
Name Server Zoning 630
Name Server zoning rules 634
Name Service Table 622
name serving 444
naming convention 159
Netscape 77, 279, 676
network security 261
new zone 720
new zone set 718
nickname 690, 728
nicknames 122, 692
NL_Port 256
non blocking ports 444
non-blocking architecture 179
non-RAID 109
notification options 85
Novell NetWare FC attachment 26
NUMA-Q 15
O
Open System Storage 104
Open-Fabric 1.0 698
operating mode 697
operating system 456
operating system support 461
optical ports 450
optical transceivers 450
orphan zone 637, 648
OS/400 operating system 11
P
parallel interface 6
partner switch 221
path group 5
Performance Bundle 444
Performance Monitor 513
Performance Monitoring 444
performance monitoring 455
physical security 261
PLDA 202, 203
Point to Point 786
port card view 694
port details 430
port driver 456
port filter statistics 521
port granularity 635
port groups 630
Port Level Zone 466
port level zoning 455
Port List View 701, 708
port numbering 253, 254
Ports 450
POST 218
power supplies 253, 254
power supply 315, 451
power supply control 456
Power-On Self-Test (POST) 262
PPRC 77
preferred domain ID 702
principal switch 457, 740
principal switch selection 460
Private Attributes 842
private host 202
Private Initiator 624
Private loop 621
private loop 200, 621
Private Loop Direct Attach (PLDA) 202, 203
private loop initiators 624
Private Target 624
private target 625
Problem Log 84
Problem Notification 85
Product Manager 692
protocol level zoning 455
pSeries attachment requirements 12
pSeries FC host 11
pseudo-host 163
public fabrics 201
Public loop 621
public loop 200, 621
Q
QLA2100F 26
QLA2200F 26, 27
QLogic QLA2100F 26, 47, 48, 58, 59
QLogic QLA2200F 27, 38, 43, 47, 49, 58, 60
queue depth 24
Quick Initialize 823
Quick Loop 202
QuickLoop 175, 199, 420
QuickLoop admin 221
QuickLoop AL_PAs 419
QuickLoop managing 204
QuickLoop partner 206
QuickLoop Zoning 491
R
R_A_TOV 710, 742
RAID 109
RAID 5 75, 109, 115, 130
range monitoring 303
ranges 303
real-time operating system 456
reboot 409
receive buffer memory 449
receive buffers 448
Redbooks Web site 847
Contact us xxxviii
Index
869
redundant flash file 448
re-enable switch 440
Remote Switch fabric 560
remote workstation 676
Remove logical drive 835
Re-Scan SCSI Bus 773
resource allocation time out value (R_A_TOV) 742
RISC processor 446
RJ-45 253
Route table enforced zoning 712
Router config file 806
Router LED codes 801
Router Node Mapping 801
Router power up sequence 803
Router Properties 812
Router Subsystem Diagnostic test 801
routing path 455
routing table 457
routing tables 457
RPQ 8S0521 203
RS/6000 11
RSH daemon 192
RSH utility 269
RSHD 269
S
SAN Data Gateway 24, 749
SCSI 749, 754, 761, 772, 797
SCSI Channel 764
SCSI commands 525
SCSI device map 773
SCSI read 521
SCSI read/write per port 526
SCSI to LUN map 782
scsiRescan 773
SDD 143, 797
SDRAM 446, 447
security 629
segmentation 630
segmented 743
SERDES 445
serial port 253
serial port settings 264
serial terminal emulator 263
Serializer/Deserializer 445
Server 755
Service port 751
setting a Gateway address 753
870
IBM SAN Implementation
setting a Subnetmask 753
setting switch IP address 263
Setting the Ethernet Address 753
setting the IP address 753
SFP 444, 445, 450, 465
SFP media 449
Short Wave Length (SWL) cable 180
short-wave ports 751
SID 455, 521
SID/DID pair 514
SID/DID performance monitoring 525
SignOn Drive 814
Simple Name Server (SNS) 348
Simple Network Management Protocol 85
SLIC Manager 841
SLIC Manager daemon 804, 809, 841
SLIC Manager software 804
SLIC Zone 805
SLIC zone 814, 841
Small Form-Factor Pluggable 444
SMIT 14
SNMP 85, 219, 260, 452, 458, 658, 678
SNMP MIBs 269
SNMP trap 303, 310
software applications 454
software enforced zone 467
software enforced zones 467
sort criteria 144
spreading volumes 132
SSA 799, 812, 839
SSA loops 115
Starting the SLIC Manager 810
Startup sequence 754
status lights 255
Stitch 456
Storage Allocation 89, 96
Storage Server Attributes 162
storage type 130
StorWatch Enterprise Storage Server Expert 119
StorWatch Fibre Channel Switch Specialist 260,
278
StorWatch launching 278
StorWatch SAN Data Gateway Specialist 755, 758
subclasses 303
Subnet mask 673
subordinate 407
Subsystem Device Driver 44, 143, 797
Sun 24, 45
Sun FC attachment 30
switch
pre-installation 262
switch admin 282
switch alarms 310
switch cascading 8
switch config admin 289
switch configuration file 222
switch controller 447
switch electronics 257
switch enabling configuration 391
Switch Event log 310
switch events log 281
switch firmware upgrade 268, 285
switch information report 290
switch installation verification 268
switch interoperability 459
switch license admin 288
switch management 280
switch name 281
switch performance information 300
switch port 722
switch port information 299
switch priority 740
switch reboot 272
Switch registration 787
switch SNMP admin 287
switch specialist firmware upgrade 272
switch Telnet interface 296
switch view 298
Switch/Port Level Zoning 472
switchdisable 409
switched fabric 667
switchenable 409
T
T_Port 656
T_Ports 656
Target Hosts 144
Technology Pack 17
Telnet 183, 262, 409, 753
Telnet firmware upgrade 270
temperature monitoring 456
temperature threshold 308
TFTP 658
threshold naming conventions 306
threshold settings 433
thresholds tab 306
TimeOutValue 53, 64
Tivoli SANergy 842
TL_Port 627, 635
TL_Ports 627
TL_Ports zoning 628
TL-CFG 636
TL-Cfg 627
topology 167
Track Format 109
track format 108
Translation Entries List 629
translation entries list 628
translative device addresses 628
transmitter negotiation 457
tree structure 306
trigger alert 321
trivial file transfer protocol 658
trunk ports 656
Trunking 444
trunking 455
trunking group 455, 510
trunking groups 510
trunking master 510
Trunking masters 510
trunking ports 455, 510
U
U_Port 256
unicast 457
Uniform Resource Locator 77
unmap 837
UnMapped 838
URL 77, 676
user rights 687
Users 93
using Remote Switch 559
utilities 190
V
Vicom Fibre Channel SLIC Router 799
Virtual Private SAN 775, 781, 784, 793
Virtual Private SAN (VPS) 774
volume assignment 127
volume definitions 131
volume placement 128
volumes sequentially placed 132
VPS 777, 787, 796
VPS Registration Service 776
VxWorks 456
Index
871
W
Windows 2000 FC attachment 58
Windows NT 4.0 FC attachment 47
world wide name zoning 455
World Wide Names 482
worldwide port name 16
WWN 206, 230, 281, 292, 325, 621, 626, 634, 655,
690
WWN Config 489
WWN Level Zoning 482
WWN Zone 466, 485
WWN Zoning 482
WWNN 79, 166
WWPN 4, 97, 118, 122, 159, 163, 230, 292, 325,
722, 723, 728
WWPN naming convention 164
WWPN value 69
X
xSeries FC attachment 15
Z
Zip drive 671
Zone Admin 327
zone administration 469
zone config settings 244
zone configurations 422, 468
zone enforcement 467
zone library 719
Zone management 713
Zone member definition 712
zone objects 468
zone set 718, 725
zone settings 237
zone types 466
Zoning 774, 784, 794
zoning 466, 690, 751, 798
Zoning Configuration Analyze 481
zoning information 398
zoning mode 469
Zoning Scheme Selection 471
872
IBM SAN Implementation
Implementing an
Open IBM SAN
(1.5” spine)
1.5”<-> 1.998”
789 <->1051 pages
Back cover
®
Implementing an
Open IBM SAN
Discover the latest
additions to the IBM
SAN family
Enhance your skills
while using an
easy-to-follow
format
Grow with the new
technology
“Do everything that is necessary and absolutely nothing
that is not.”
In this IBM Redbook, which is an update and major revision of
the previous version, we have tried to consolidate as much of
the critical information as possible while covering procedures
and tasks that are likely to be encountered on a daily basis.
Each of the products described has much, much more
functionality than we could ever hope to cover in just one
redbook. The IBM SAN portfolio is rich in quality products that
bring a vast amount of technicality and vitality to the SAN
world. Their inclusion and selection is based on a thorough
understanding of the storage networking environment that
positions IBM, and therefore its customers and partners, in an
ideal position to take advantage by their deployment.
In this redbook we cover the latest additions to the IBM SAN
family, which includes products from companies such as
Brocade, INRANGE, and McDATA. We show how they can be
implemented in an open systems environment, and we focus
on the Fibre Channel protocol (FCP) environment in particular.
We address some of the key concepts that they bring to the
market, and in each case, we give an overview of those
functions that are essential to building a robust SAN
environment.
INTERNATIONAL
TECHNICAL
SUPPORT
ORGANIZATION
BUILDING TECHNICAL
INFORMATION BASED ON
PRACTICAL EXPERIENCE
IBM Redbooks are developed by
the IBM International Technical
Support Organization. Experts
from IBM, Customers and
Partners from around the world
create timely technical
information based on realistic
scenarios. Specific
recommendations are provided
to help you implement IT
solutions more effectively in
your environment.
For more information:
ibm.com/redbooks
SG24-6116-01
ISBN 0738423017