Application Notes hp StorageWorks Fabric Interoperability: Merging Fabrics Based on C-Series and B-Series Fibre Channel Switches Eleventh Edition (December 2007) Part Number: AA-RV1ZL-TE This document summarizes.
© Copyright 2004, 2007 Hewlett-Packard Development Company, L.P. Hewlett-Packard Company makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.
About this document About this document This section describes the content reflected in this document, including: ■ Application notes information, page 3 ■ Intended audience, page 3 ■ Other SAN interoperability documentation, page 3 Application notes information These Application Notes cover the following major topics: ■ Introduction, page 4 ■ How to read this document, page 4 ■ Check list for merging fabrics, page 5 ■ B-Series configuration steps, page 6 ■ C-Series configuration steps, page
Introduction Introduction This application notes discusses the details on how to configure and merge HP C-series and B-series switches into a single standards based interoperable fabric. This document also provides information on supported configurations, expected behavior and any exceptions in the interoperability mode.
Check list for merging fabrics Check list for merging fabrics B-Series Complete the following steps before merging the fabrics: Step B1: verify switch firmware versions, page 6 Steps B2, B3: verify/configure switch domain IDs & verify switch/fabric default settings, page 6 Step B4: disable management server, page 8 Step B5: verify/configure fabric operating mode, page 8 Step B6: verify proper zoning configuration is in place, page 9 C-Series Complete the following steps before merging the fabrics: Step C1
B-Series configuration steps B-Series configuration steps The following steps provide information on how to verify, configure B-series switches for Interoperability. While it is possible to accomplish this by using either the Fabric Manager or the embedded Web Tools or the CLI, the following steps use only CLI (telnet) for demonstrating this. Step B1: verify switch firmware versions Before merging the fabrics, make sure all the B-Series switches in the fabric have the right firmware version.
B-Series configuration steps Fabric parameters (yes, y, no, n): [no] y Domain: (1..239) [97] Å Select the domain ID in the range 97-127, if change is required BB credit: (1..27) [16] R_A_TOV: (4000..120000) [10000] Å Ensure this value is 10000, should be same for all switches in the fabric E_D_TOV: (1000..5000) [2000] Å Ensure this value is 2000, should be same for all switches in the fabric WAN_TOV: (1000..120000) [0] Data field size: (256..2112) [2112] Sequence Level Switching: (0..
B-Series configuration steps Step B4: disable management server It is required to disable platform management services fabric wide before enabling the interopmode and merging the fabrics. The following command when executed will deactivate the Platform Database Management Service of each switch in the fabric. Switch:admin> msPlMgmtDeactivate This will erase all Platform entries. Are you sure? no, n): [no] y (yes, y, Committing configuration...done.
B-Series configuration steps cfgDisable: no EFFECTIVE configuration interopMode is 1 NOTE: It is required that you boot this switch to make this change take effect Switch:admin> fastboot Å reboots the switch quicker, bypassing POST Step B6: verify proper zoning configuration is in place Check for Duplicate Zone Sets (zones): To ensure proper zoning merge and operation, verify there are no duplicate active ZoneSets or Zones across the two fabrics that need to be merged.
C-Series configuration steps C-Series configuration steps The following steps provide information on how to verify, configure C-series switches for Interoperability. While it is possible to accomplish this by using either the Fabric Manager or the CLI, the following steps use only CLI (telnet) for demonstrating this. Step C1: verify switch firmware versions Verify all C-series switches are configured with the correct firmware version as shown in Table 3.
C-Series configuration steps MDS9509# config t MDS9509(config)# vsan database MDS9509(config-vsan-db)# vsan 1 suspend MDS9509# config t MDS9509(config)# fctimer e_d_tov 2000 <1000-100000> E_D_TOV in milliseconds(1000-100000) MDS9509(config)# fctimer r_a_tov 10000 <5000-100000> R_A_TOV in milliseconds(5000-100000) Step C3: verify the fabrics are in proper operating mode To enable interoperability mode on C-series switches, the first step is to place the VSAN of the E_Ports(s) that connect to the B-serie
C-Series configuration steps MDS9509# show zoneset active zoneset name mdscore vsan 1 zone name vz1 vsan 1 * fcid 0x630500 [pwwn 50:06:01:60:88:02:90:cb] * fcid 0x610400 [pwwn 10:00:00:00:c9:24:3d:90] zone name vz2 vsan 1 * fcid 0x630400 [pwwn 10:00:00:00:c9:24:3f:75] * fcid 0x6514e2 [pwwn 21:00:00:20:37:a7:ca:b7] * fcid 0x6514e4 [pwwn 21:00:00:20:37:a7:c7:e0] * fcid 0x6514e8 [pwwn 21:00:00:20:37:a7:c7:df] zone name vz3 vsan 1 * fcid 0x651500 [pwwn 10:00:00:e0:69:f0:43:9f] * fcid 0x6105dc [pwwn 21:00:00:20
Merging fabrics and verification Merging fabrics and verification After configuring both the fabrics individually as described above, now the identified E-ports from both sides can be connected to merge them. The fabric should now reconfigure and merge itself into a single fabric. To verify the fabric has merged properly, run the following commands on both B-series and C-series switch and ensure they are no segmentations or other errors.
Merging fabrics and verification On the C-series MDS9509# show vsan 1 vsan 1 information name:VSAN0001 state:active interoperability mode:yes Å verify mode loadbalancing:src-id/dst-id/oxid operational state:up MDS9509# show fcdomain vsan 1 The local switch is a Subordinated Switch.
Expected behavior from Fibre Channel services Expected behavior from Fibre Channel services While in “Interoperability mode”, all the fibre channel services from each of the switch types may not work the same as in Native Mode. However, the following behavior is expected in an interoperating fabric. ■ Zoning: All zones will be done with PWWNs only. Thus each switch type will implement zoning in its native form as if only PWWNs were used. Other types of zoning definition are not supported.
Interoperability mode behavior summary by switch type Interoperability mode behavior summary by switch type The following is a summary of interoperability mode behavior on C-Series switches. C-Series The MDS series of switches are limited in the following areas when interoperating with other non-MDS switches: ■ “Interop Mode” only affects the specified vsan. The MDS-9000 can still operate with full functionality in other non-interop mode vsans.
Interoperability mode behavior summary by switch type Table 1: C-Series interoperability mode summary (Continued) Fabric Manager and Element Manager Can still be used to fully manage the MDS-9000, and create zones to be distributed to the non-MDS platforms. FM can still view the entire mixed topology. Security Ssh, telnet, snmp-v3 are supported. Device Support Fabric pt2pt F-mode B-Series The following is a summary of interoperability mode behavior on B-series switches.
Merging zones-examples Merging zones-examples In this example, we first create three zones vz1, vz2 and vz3 on one of the C-series switches and verify these zones propagate to all the C-series and B-series switches in the interoperating fabric. MDS9509# conf t Enter configuration commands, one per line. End with CNTL/Z.
Merging zones-examples At this point we have created 3 zones, vz1, vz2 and vz3. We have also created a “zoneset” titled “mdscore”. Now we will activate the zoneset MDSCORE MDS9509(config)# zoneset activate name mdscore vsan 1 Zoneset Activation initiated. check zone status MDS9509(config)# MDS9509(config)# MDS9509(config)# exit Now we will view each switch in the fabric to verify the zoning we defined is in place.
Merging zones-examples B-series switches Using the telnet on B-series switches verify that the zoning information has propagated properly. On B-series you will see the active configuration as well as any defined configurations that are not part of active configuration.
Merging zones-examples Now let us create three new zones vz11, vz22, and vz33.
Merging zones-examples Effective configuration: cfg: mdscore1 zone: vz11 10:00:00:00:c9:24:3d:90 50:06:01:60:88:02:90:cb zone: vz22 10:00:00:00:c9:24:3f:75 21:00:00:20:37:a7:ca:b7 21:00:00:20:37:a7:c7:e0 21:00:00:20:37:a7:c7:df zone: vz33 10:00:00:e0:69:f0:43:9f 21:00:00:20:37:28:31:6d 21:00:00:20:37:28:24:7b 21:00:00:20:37:28:22:ea 21:00:00:20:37:28:2e:65 21:00:00:20:37:28:26:0d This is correct. The new configuration is effective and defined. Now let us have a look at the other switches in the fabric.
Merging zones-examples MDS9509# show zone vsan 1 zone name vz1 vsan 1 pwwn 50:06:01:60:88:02:90:cb pwwn 10:00:00:00:c9:24:3d:90 zone name vz2 vsan 1 pwwn 10:00:00:00:c9:24:3f:75 pwwn 21:00:00:20:37:a7:ca:b7 pwwn 21:00:00:20:37:a7:c7:e0 pwwn 21:00:00:20:37:a7:c7:df zone name vz3 vsan 1 pwwn 10:00:00:e0:69:f0:43:9f pwwn 21:00:00:20:37:28:31:6d pwwn 21:00:00:20:37:28:24:7b pwwn 21:00:00:20:37:28:22:ea pwwn 21:00:00:20:37:28:2e:65 pwwn 21:00:00:20:37:28:26:0d Fabric Interoperability: Merging Fabrics Based on
Supported configuration rules and guidelines Supported configuration rules and guidelines The following fabric configuration rules apply when mixing the two fabrics: ■ Switches listed in Table 2 and Table 3 may be used together in a fabric. ■ Only the standards-based interoperability mode, Mode-1, is supported on MDS switches. ■ Use the C-Series Fabric Manager for all zoning administration. This includes creating, modifying, enabling, and disabling zones in the combined fabric.
Supported configuration rules and guidelines targets hosts hosts Brocade 4Gb SAN Switch for HP p-Class BladeSystem targets targets hosts B-Series/ C-Series targets hosts B-Series/ C-Series B-Series/ C-Series Brocade 4Gb SAN Switch for HP c-Class BladeSystem hosts hosts C-Series C-Series Director Director targets targets B-Series/ C-Series hosts targets hosts targets B-Series/ C-Series B-Series/ C-Series B-Series/ C-Series hosts targets hosts targets Recommended IOP configurati
Supported configuration rules and guidelines Table 2: Supported B-Series product line switches (Continued) Firmware Version HP StorageWorks Switch Name Number of Ports HP Brocade 2400 (HP reseller) Compaq StorageWorks SAN Switch 8 8 N/A Compaq StorageWorks SAN Switch 8-EL 8 HP Brocade 2800 (HP reseller) Compaq StorageWorks SAN Switch 16 16 N/A Compaq StorageWorks SAN Switch 16-EL HP Surestore FC Switch 6164 (64 ISL Ports) Compaq StorageWorks SAN Switch Integrated/32 (64 ISL Ports) 32 (count
Supported configuration rules and guidelines Table 4: Supported operating system versions OS OS Version Multi Path Software HBA Driver/ Firmware/BIOS (minimum required) Windows 2000 AS SP3 Secure Path 4.0c QLA 2342, LP8000 8.2.0.71 / 1.33 5-4.82a16 / 3.91a1 / 1.63a1 Windows 2003 AS SP2 Secure Path 4.0c LP952 5-4.82a16 / 3.91a1 / 1.63a1 HP-UX 11.00/11.11 Auto Path 2.01.02 A6795A 11.00.10 PHSS_26798 11.11.09 PHKL_26799 PDC 42.19 HP-UX 11.23 N/A A6795A B11.23.03 OVMS 7.
Troubleshooting Table 7: HP BladeSystem Support (c-Class) HP BladeSystem c-class BL460c, BL465c, and BL480c Operating System Microsoft Windows 2003, Windows 2000 Red Hat Enterprise Linux 3 and 4 (X86) SLES 8 (X86) SLES 9 (X86) Fibre Channel interface Emulex LPe1105 QLogic QMH2462 Embedded switch Brocade 4 Gb SAN switch for HP c-Class BladeSystem (Switch Mode or AG Mode) Cisco MDS 9124e Fabric Switch for HP c-Class BladeSystem (Switch Mode or NPV Mode) Storage XP, EVA, MSA Troubleshooting 1.
