Guidelines and limitations
This information describes guidelines and limitations for a nondisruptive migration of both the Supervisor-1 Modules to Supervisor-4 Modules.
- The migrate sup kickstart <supervisor4-kickstart-image > system <supervisor4-system-image > command used for initiating the nondisruptive migration process is available only in global config mode.
- Ensure that the Supervisor-4 Module is not inserted in the standby slot before initiating the migrate sup kickstart <supervisor4-kickstart-image > system <supervisor4-system-image > command. If the Supervisor-4 Module is already inserted in the standby slot, the migration process will be aborted and the Supervisor-4 Module will be powered down.
- Insert the standby Supervisor-4 Module into the chassis only when you are prompted to insert theSupervisor-4 Module during the migration by a mes sage on the system console.
- After the Supervisor-4 Module has been inserted during the migration process, do not remove or manually reload the standby Supervisor-4 Module.
- Back up all the licenses, configurations, boot flash files before starting the migration process. In case of any failure or loss of licenses and configuration in the Supervisor-4 Module, disruptive migration has to be done to upgrade to Supervisor-4 Module. In such a scenario, all the configurations and licenses have to be applied or installed again. For more information on how to back up the licenses and configurations, see the Prerequisites.
- Use the show environment power command to display the actual power usage information for the entire switch.
-
Ensure that the current system is running Cisco MDS NX-OS Release 8.4(1) or later on IBM SAN192C-6 or SAN384C-6 Director switches. Ensure that the current system is running Cisco MDS NX-OS Release 8.4(2a) or later on IBM SAN786C-6 Multilayer Director. Use the show version command to view the current image on the system.
- The migration procedure must be performed during a schedule maintenance period only.
- Nondisruptive backward migration procedure (migrating from a Supervisor-4 Module to a Supervisor-1 Module) is not supported. Backward migration is disruptive (power off and power on the switch).
- In a dual supervisor module scenario, ensure that the standby supervisor module is in the HA-standby state. If the standby supervisor does not come up in the HA-standby state, then physically remove the standby supervisor module and initiate the migration on the active supervisor module. Use the show module command to view the active and standby supervisor modules.
- Do not reload or manually insert or remove any I/O or crossbar fabric switching modules after initiating the migrate sup kickstart <supervisor4-kickstart-image> system <supervisor4-system-image> command. Any removal or insertion of I/O or Crossbar Fabric-1 Switching Modules must be done before initiating the migration process or after the migration is completed.
- Configuration mode is blocked during the migration procedure to prevent any changes. You cannot press Control+C to cancel the migration procedure until 45 minutes have elapsed after issuing the migrate sup kickstart <supervisor4-kickstart-image> system<supervisor4-system-image> command.
- Use the show logging onboard migration status command on any management session to display the status of the migration. You can use this command during the migration or after the migration is complete.
- In the system messages (system messages displayed on the console during the migration process) and the show module command output, Supervisor-1 Module and Supervisor - 1E are displayed as Supervisor-3 Module.
-
Perform the Crossbar Fabric-1 to Crossbar Fabric-3 module migration after the Supervisor-1/Supervisor-1E to Supervisor-4 Module migration is completed. A mix of Crossbar Fabric-1 with Supervisor-4 Modules or Crossbar Fabric-3 with Supervisor-1/Supervisor-1E Modules is not supported.
-
Ensure that the switch release version and the targeted migration release version is same. Use the show version command to view the version of the Cisco MDS NX-OS software on the switch.
-
If you are using a Supervisor-4 Module for migration that has been already used in a previous MDS setup, ensure that the Supervisor-4 module has sufficient space on boot flash for copying both the system and kickstart images before the migration.
-
The following table lists the supported release versions for migrating to Supervisor-4 Modules on the IBM SAN c-type family of switches.
-
Product Name Supported MDS NX-OS Release Version Cisco MDS 9718 Director Cisco MDS NX-OS Release 8.4 (2a) and later Cisco MDS 9710 Director Cisco MDS NX-OS Release 8.4 (1) and later Cisco MDS 9710 Director Cisco MDS NX-OS Release 8.4 (1) and later -
The following table lists the supported combinations for supervisor modules with crossbar fabric modules on the IBM c-type family switches in a production environment. In the table:– The term, “Yes” indicates the supported combinations.
-
The “—” symbol indicates the unsupported combinations.
-
Combination Supervisor-1 Module Supervisor-1E Module Supervisor-4 Module Cross Fabric - 1 Switching Module Cross Fabric - 3 Switching Module Supervisor-1 Module Yes — — Yes — Supervisor-1E Module — Yes — Yes — Supervisor-4 Module — — Yes — Yes Cross Fabric - 1 Switching Module Yes Yes — Yes — Cross Fabric - 3 Switching Module — — Yes — Yes - Do not do any of the following actions.
- Insert or remove any transceivers from any modules while the migration is in progress.
- Alter any connections while the migration is in progress.
- Remove any power supply modules or fan modules during the migration process.
- Attempt any configuration changes or network changes while the migration is in progress.
- Copy any configurations using the copy running-config startup-config command while the migration is in progress.
- Trigger any EPLD or BIOS upgrades during the migration.
- Trigger any ISSU during the migration.
- Perform migration from Crossbar Fabric-1 Switching Modules to Crossbar Fabric-3 Switching Modules during the Supervisor-1 Module to Supervisor-4 Module migration.