IBM SAN192C-6 - Page 132

Action to be performed
Remove the standby Supervisor-4 Module and start the migration process again.
Problem
The standby Supervisor-1 Module is not in the HA-standby state. The following syslog message is
displayed:
<Tue Apr 30 10:02:47 2019> ERROR!!! Standby Supervisor-1 is
not yet in ha-standby state, aborting migration ...
<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
Action to be performed
Wait until the standby Supervisor-1 Module comes up in the HA-standby state or remove the standby
Supervisor-1 Module and perform a single supervisor migration.
Problem
In case of a dual supervisor migration, the standby Supervisor-1 Module is powered down by using
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-1 in slot <slot_number>,
aborting migration ...
Action to be performed
Use the migrate sup kickstart <supervisor4-kickstart-image> system
<supervisor4-system-image> command again.
Problem
Unable to lock the configuration. The following syslog message is displayed:
<Tue Apr 30 10:02:47 2019> ERROR!!! Failed to lock config,
aborting migration ...
Action to be performed
Use the migrate sup kickstart <supervisor4-kickstart-image> system
<supervisor4-system-image> command again.
Problem
After powering down the Supervisor-1 module, the switch will check for the presence of a module
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
Action to be performed
None. There is no impact on the migration process.
Problem
A Supervisor-1 Module is inserted instead of a Supervisor-4 Module. The following syslog message is
displayed:
<Tue Apr 30 10:02:47 2019> ERROR!!! Supervisor-1 is
inserted in slot <slot_number> instead of Supervisor-4,
aborting migration ...
Action to be performed
Restart migration and ensure that the newly inserted supervisor module is the Supervisor-4 Module.
Problem
In case the Supervisor-4 Module is not inserted into the standby slot within 30 minutes after the
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 to be inserted in slot <slot_number>,
aborting migration ...
106IBM Storage Networking SAN192C-6, SAN384C-6 and SAN768C-6: SAN192C-6, SAN384C-6 and
SAN768C-6 Installation, Service, and User Guide