Table of Contents
Advertisement
<Tue Apr 30 10:02:47 2019> WARNING!!!
Please set the boot variables manually before
inserting back Supervisor-1 in standby slot <slot_number>,
continuing migration ...
Action to be performed
Use the migrate sup kickstart <supervisor4-kickstart-image> system
<supervisor4-system-image> command again.
Problem
The copy r s command fails on the active Supervisor-1 Module before the switchover to the
Supervisor-4 Module is initiated. The following syslog is displayed:
<Tue Apr 30 10:02:47 2019> ERROR!!! Failed to save configuration,
aborting migration ...
Action to be performed
Use the migrate sup kickstart <supervisor4-kickstart-image> system
<supervisor4-system-image> command again.
Problem
The switchover fails on the active Supervisor-1 Module before the switchover to the Supervisor-4
Module is initiated. The following syslog is displayed:
<Tue Apr 30 10:02:47 2019> ERROR !!
Switchover failed, aborting migration ...?
Action to be performed
Use the migrate sup kickstart <supervisor4-kickstart-image> system
<supervisor4-system-image> command again.
Problem
In case the Supervisor-4 Module is not inserted within 30 minutes after using the migrate sup
kickstart<supervisor4-kickstart-image> system <supervisor4-system-image>
command, the switch will try to power up the powered down Supervisor-1 Module in the standby
slot on reaching the timeout of 30 minutes. If the standby Supervisor-1 Module fails to power up, the
following syslog message is displayed before aborting migration:
<Tue Apr 30 10:02:47 2019> ERROR !!! Failed to power up
Standby Supervisor, Please power up manually using
"no poweroff module <slot_num>" from config mode
Action to be performed
Use the no poweroff module <slot_number> command on the active Supervisor-4 Module
to bring up the powered down standby Supervisor-4 Module in case the Supervisor-4 Module has
not been inserted within 30minutes after using the migrate sup kickstart<supervisor4-
kickstart-image> system <supervisor4-system-image> command.
Problem
Setting of the boot variable parameters fails after migration when the Supervisor-4 Module becomes
active supervisor. The following syslog is displayed:
BOOTVAR-2- SUP_MIGRATION_CONFIG_ERROR
Setting boot parameters for supervisor migration process returned error.
Please set the boot variables manually using
'boot kickstart <kickstart_image>' and
'boot system <system_image>' and save configs"
Action to be performed
Use the boot kickstart <kickstart_image> and the boot system <system_image> on the
active Supervisor-4 Module when it becomes active after the migration has been completed.
Problem
Migration fails on Supervisor-4 Module because of insufficient boot flash memory on the Supervisor-4
Module. The following syslog is displayed:
2019 Apr 2 08:47:43 switch %FS-STANDBY-DAEMON-2-FSD_ENOSPC_BOOTFLASH:
Due to insufficient space, system image could not be copied to standby boot flash.
system image is not present on standby.
Please copy 'm9700-sf4ek9-mz.8.4.1.bin' manually.
Standby supervisor not yet online. This might take sometime. Please wait ...
108 IBM Storage Networking SAN192C-6, SAN384C-6 and SAN768C-6: SAN192C-6, SAN384C-6 and
SAN768C-6 Installation, Service, and User Guide
Advertisement
Table of Contents
