• Embed Doc
  • Copy Link
  • Readcast
  • Collections
  • CommentGo Back
Download
SAN - 2109-M12 Considerations
Abstract
Migrating the 2109-M12 into the SAN fabric
Contents
Migrating the 2109-M12 into a core fabric
In this hint and tip we describe the requirements for migrating the 2109-M12 into a core to edge fabric.
Prerequisites
The fabric we are going to migrate the M12 into must meet the following requirements before any physical fabric
connections are made to the M12.
\u2022
All IBM 2109 S-series switches in your fabric must run Fabric OS version 2.6 or higher.
\u2022
All IBM 3534 and 2109 F-series switches in your fabric must run Fabric OS version 3.0.2c or higher.
\u2022
All edge switches must have the core PID format set, refer to \u201cSetting Core PID format\u201d below.
\u2022
The four IP addresses that you reserve for the two logical switches and the two CPs in each 2109-M12 must
appear in the same subnet.
\u2022
You must remove any hosts that connect to the core and connect them to the edge. You may need to update port-
based zoning for any devices attached directly to the cores, as their port addresses may change.
\u2022
All setup has been performed on the 2109-M12.
Final preparation of the M12
To ensure that the M12 is ready to be migrated into the fabric, we perform the following steps before connecting to the
fabric.
Attention: Connecting the M12 to the fabric, and then performing the following steps will delete all defined zoning
information in your fabric.

1.With the M12 not connected to any fabric, we issue cfgDisable to disable any active configuration.
2.Enter the cfgClear command to remove all configuration data and zoning information from the switch.
3.To ensure that trunking is enabled we type switchCfgTrunkEnable 1.

4. Disable both logical switches by using switchDisable.
Disabling the switches stops constant fabric reconfigurations from occurring while you connect the ISLs.
Verify the current fabric
In this step we will take a snapshot of our current fabric configuration. This will help in verification of the fabric after the
M12 has been migrated in.
1.Use the switchShow, nsShow, fabricShow, and nsAllShow commands to record the total number of devices on
each switch and the number of ISLs that connect to each switch.
2. On every host system ensure that your multipathing is operational. Replace the current switches with the M12.

With our current fabric devices all at the correct firmware levels and the core PID format set, the M12 installed, configured,
cleared, and disabled, and our current fabric configuration saved and documented, we are now ready to perform the swap
of our switches. With correct redundancy built into the fabric this can be accomplished by performing one core switch at a
time, or in a fully redundant Fabric configuration, the entire core of a fabric can be performed, with minimal impact to
system availability.

of 00

Leave a Comment

You must be to leave a comment.
Submit
Characters: ...
You must be to leave a comment.
Submit
Characters: ...