Table of Contents
Advertisement
Installing, Removing, and Verifying Field Replaceable Units
<Tue Apr 30 10:02:47 2019> Please wait for Standby supervisor in slot <slot_number>
to become ha-standby or physically remove standby and start migration
Solution
Supervisor-1 Module and perform a single supervisor migration.
Problem
the out-of-service < slot-number > command. If the standby Supervisor-1 Module does not power down
after using this command, the following syslog message is displayed:
<Tue Apr 30 10:02:47 2019> ERROR!!! Failed to power down Standby
Supervisor-3 in slot <slot_number>, aborting migration...
Solution
> command again.
Problem
<Tue Apr 30 10:02:47 2019> ERROR!!! Failed to lock config, aborting migration...
Solution
> command again.
Problem
syslog message is displayed:
<Tue Apr 30 10:02:47 2019> ERROR!!! Standby Supervisor config failed, aborting migration...
Solution
> command again.
Problem
in the slot from which the Supervisor-1 Module was removed. This check happens every 30 minutes after the
Supervisor-1 Module has been removed. In case this check to detect the presence of the supervisor module
fails, the following syslog message is displayed:
<Tue Apr 30 10:02:47 2019> ERROR!!! Module information retrieve failed
Solution
Problem
is displayed:
<Tue Apr 30 10:02:47 2019> ERROR!!! Supervisor-1 (DS-X97-SF1-K9) is inserted in slot
<slot_number> instead of
Supervisor-4 (DS-X97-SF4-K9), aborting migration...
Solution
Problem
Supervisor-1 Module has been powered down, the following syslog message is displayed:
module
<Tue Apr 30 10:02:47 2019> ERROR!!! Timeout waiting for Supervisor-4 (DS-X97-SF4-K9)
to be inserted in slot <slot_number>, aborting migration...
Solution
> command again and ensure that the Supervisor-4 Module is inserted into the standby slot within 30 minutes
after the Supervisor-1 Module has been powered down.
Problem
displayed:
Wait until the standby Supervisor-1 Module comes up in the HA-standby state or remove the standby
In case of a dual supervisor migration, the standby Supervisor-1 Module is powered down by using
Use the migrate sup kickstart < supervisor4-kickstart-image > system < supervisor4-system-image
Unable to lock the configuration. The following syslog message is displayed:
Use the migrate sup kickstart < supervisor4-kickstart-image > system < supervisor4-system-image
In case a auto-boot is not disabled before the insertion of the Supervisor-4 Module, the following
Use the migrate sup kickstart < supervisor4-kickstart-image > system < supervisor4-system-image
After powering down the Supervisor-1 Module, the switch will check for the presence of a module
None. There is no impact on the migration process.
A Supervisor-1 Module is inserted instead of a Supervisor-4 Module. The following syslog message
Restart migration and ensure that the newly inserted supervisor module is the Supervisor-4 Module.
In case the Supervisor-4 Module is not inserted into the standby slot within 30 minutes after the
Use the migrate sup kickstart < supervisor4-kickstart-image > system < supervisor4-system-image
Unable to create image links for the Supervisor-4 Module images. The following syslog message is
Cisco MDS 9700 Series Switches Hardware Installation Guide
Troubleshooting
147
Advertisement
Table of Contents
Troubleshooting
