Troubleshooting

This information lists error messages that might appear on the console during the migration. This information also suggests actions that you can do to correct the problems.

Problem

Setting boot parameters for supervisor migration process returned error:

switch %BOOTVAR-2-SUP_MIGRATION_CONFIG_ERROR: 
Setting boot parameters for supervisor 
migration process returned error.

Action to be performed

Set the boot variables manually using the boot kickstart <kickstart_image> command and boot system<system_image> on the Supervisor-4 Module

Problem

The kickstart or system image is not present on the bootflash of the active Supervisor-4 Module. The following syslog message is displayed:

switch %BOOTVAR-2-SUP_MIGRATION_IMAGE_DOES_NOT_EXIST: 
System image doesn't exist on bootflash of the supervisor. 
Please clear some space in bootflash, copy the Supervisor-4 
images manually, set the boot variables and save configs before 
replacing Standby Supervisor-1

Action to be performed

Clear space on the bootflash and then copy the Supervisor-4 module images manually, as shown in Step 3 in Scenario 1 of the migration procedures given above. Set the boot variables and save the configuration before replacing the standby Supervisor-1 module. Use the boot kickstart <kickstart_image> command and the boot system <system_image> command on the active Supervisor-4 Module when it becomes active after the migration is completed.

Problem

The newly inserted Supervisor-4 Module cannot take over as the active supervisor. The following syslog message is displayed:

<Tue Apr 30 10:02:47 2019> ERROR!!! Supervisor-4 cannot 
take over as active Supervisor ...

Action to be performed

Wait for the next retry attempt by the switch to bring up the Supervisor-4 Module.

Problem

The migration logging file is already present in the Supervisor-1 Module. The following syslog message is displayed:

<Tue Apr 30 10:02:47 2019> WARNING!!! Migration logging file already 
exists in Supervisor-4, continuing migration ...

Action to be performed

None. The show logging onboard migration status command is used to monitor the migration progress. There is no impact on the migration process

Problem

The switch cannot initiate migration logging due to insufficient file permissions. The following syslog message is displayed:

 <Tue Apr 30 10:02:47 2019> WARING!!! Migration logging cannot be
done due to file permission error, continuing migration ...

Action to be performed

None. The show logging onboard migration status command is used to monitor the migration progress. This error message is displayed if the appropriate file permissions have not been provided.

Problem

The active Supervisor-1 Module is using the redundant secondary EOBC link instead of the primary EOBC link. The following syslog message is displayed:

<Tue Apr 30 10:02:47 2019> ERROR!!! Active Supervisor-4 is using 
Redundant EOBC link, this indicates some problem with Primary EOBC link, 
aborting migration ...

Action to be performed

Replace the active Supervisor-1 Module with another Supervisor-1 Module.

Problem

Unable to extract the image header from the kickstart or system images. The following syslog messages are displayed:

<Tue Apr 30 10:02:47 2019> ERROR!!! Image header extraction failed for 
Kickstart image <kickstart_image> of Supervisor-4, aborting migration ...
<Tue Apr 30 10:02:47 2019> ERROR!!! Image header extraction failed for 
System image <system_image> of Supervisor-4, aborting migration ...

Action to be performed

Use the migrate sup kickstart <supervisor4-kickstart-image> system <supervisor4-system-image> command again.

Problem

Unable to retrieve the kickstart or system image information. The following syslogs are displayed:

<Tue Apr 30 10:02:47 2019> ERROR!!! Failed to get 
Kickstart image info, 
aborting migration...
<Tue Apr 30 10:02:47 2019> ERROR!!! Failed to get System 
image info, aborting migration...

Action to be performed

Use the migrate sup kickstart <supervisor4-kickstart-image> system <supervisor4-system-image> command again.

Problem

The kickstart or system images provided are not valid images for the Supervisor-4 Modules. The following syslog message is displayed:

<Tue Apr 30 10:02:47 2019> ERROR!!! Kickstart image provided 
'<kickstart_image>' is not a valid Supervisor-4 image, 
aborting migration ...
<Tue Apr 30 10:02:47 2019> ERROR!!! System image provided 
'<system_image>' is not a valid Supervisor-4 image, 
aborting migration ...

Action to be performed

Use a valid Supervisor-4 Module image and use the migrate sup kickstart <supervisor4-kickstart-image> system <supervisor4-system-image> command again.

Problem

The release versions of the Supervisor-4 Module kickstart and system images provided are not the same as the existing Supervisor-1 Module kickstart and system images. The following syslog messages are displayed:

<TueApr 30 10:02:47 2019> ERROR!!! Running kickstart version :
<running_version>,?version of kickstart image provided : 
<Supervisor-1_image_version>
<Tue Apr 30 10:02:47 2019> ERROR!!! 
Version of kickstart image provided 
('<sup3_image_version>’) does not match running version, 
aborting migration ...
<Tue Apr 30 10:02:47 2019> ERROR!!! Running System version: 
<running_version>, version of system image provided : 
<Supervisor-1_image_version>
<Tue Apr 30 10:02:47 2019> ERROR!!! Version of system image provided
('<sup1_image_version>’) does not match running version, 
aborting migration ...

Action to be performed

Check the image version. The release versions of the Supervisor-4 Module kickstart and system images provided should be the same as the existing Supervisor-1 Module kickstart and system images.

Problem

Unable to retrieve the chassis information. The following syslog message is displayed:

<Tue Apr 30 10:02:47 2019> ERROR!!! Chassis information retrieve failed, 
aborting migration ...

Action to be performed

Use the migrate sup kickstart <supervisor4-kickstart-image> system <supervisor4-system-image> command again.

Problem

Unable to retrieve the slot number of the supervisor module. The following syslog message is displayed:

<Tue Apr 30 10:02:47 2019> ERROR!!! Supervisor slot 
information retrieve failed, 
aborting migration ...

Action to be performed

Use the migrate sup kickstart <supervisor4-kickstart-image> system <supervisor4-system-image> command again.

Problem

Unable to retrieve the slot number of the standby supervisor module. The following syslog message is displayed:

<Tue Apr 30 10:02:47 2019> ERROR!!! Standby Supervisor slot 
information retrieve 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 migrate sup kickstart <supervisor4-kickstart-image> system <supervisor4-system-image> command cannot read the stored Supervisor-1 Module image links, the migration process fails. The following syslog messages are displayed:

<Tue Apr 30 10:02:47 2019> ERROR!!! Kickstart image link for 
Active Supervisor-1 could not be found, aborting migration ...
<Tue Apr 30 10:02:47 2019> Please set the boot parameters using 
'boot kickstart <kickstart_image>' and 'boot system <system_image>'
<Tue Apr 30 10:02:47 2019> ERROR!!! System image link for 
Active Supervisor-1 could not be found, aborting migration ...
<Tue Apr 30 10:02:47 2019> Please set the boot parameters using 
'boot kickstart <kickstart_image>' and 'boot system <system_image>'

Action to be performed

Set the Supervisor-1 Module image links using the boot kickstart <kickstart_image> command and the boot system <system_image> command before re-inserting the standby Supervisor-4 Module.

Problem

The Supervisor-4 Module is already present in the standby slot before initiating the migration procedure. The following syslog message is displayed:

<Tue Apr 30 10:02:47 2019> ERROR!!! Supervisor-4 is already 
inserted in standby slot <slot_number> before starting migration. 
Please remove Standby supervisor and start single 
Supervisor migration, aborting migration ...

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 ...

Action to be performed

Use the migrate sup kickstart <supervisor4-kickstart-image> system <supervisor4-system-image> 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

Unable to create image links for the supervisor-4 module images. The following syslog message is displayed:

<Tue Apr 30 10:02:47 2019> ERROR!!! Supervisor-4 image 
links could not be created for Standby Supervisor bootup, 
aborting migration ...

Action to be performed

Use the migrate sup kickstart <supervisor4-kickstart-image> system <supervisor4-system-image> command again.

Problem

Unable to reload the Supervisor-4 Module after the Supervisor-4 Module is detected in the switch. The following syslog message is displayed:

<Tue Apr 30 10:02:47 2019> ERROR!!! 
Failed to reload Standby Supervisor-4, 
aborting migration ...

Action to be performed

Remove the Supervisor-4 Module from the standby slot and restart migration by using the migrate sup kickstart <supervisor4-kickstart-image> system <supervisor4-system-image>

Problem

The Supervisor-4 Module is stuck in loader prompt due to a boot failure. The following syslog message is displayed:

<Tue Apr 30 10:02:47 2019> ERROR!!! 
Standby Supervisor-4 is stuck in 
loader prompt due to boot-up failure ...

Action to be performed

None. A retry attempt to bring up the Supervisor-4 Module is initiated by the switch every 15 minutes for 3 times.

Problem

The Supervisor-4 Module is unable to come online. The following syslog message is displayed:

<Tue Apr 30 10:02:47 2019> ERROR!!! 
Standby Supervisor-4 could not come online ...

Action to be performed

None. A retry attempt to bring up the supervisor-4 module is initiated by the switch every 15 minutes.

Problem

The supervisor module fails to come online. The following syslogs are displayed:

<Tue Apr 30 10:02:47 2019> ERROR!!! 
Timeout waiting for Supervisor-4 to come online, 
aborting migration ...
<Tue Apr 30 10:02:47 2019> Powering down 
Supervisor-4 in slot <slot_number>

Action to be performed

Use the migrate sup kickstart <supervisor4-kickstart-image> system <supervisor4-system-image> command again.

Problem

The Supervisor-1 Module image links are not restored on the active Supervisor-1 Module before the switchover to Supervisor-4 Module is initiated. The following syslogs are displayed before saving configuration:

<Tue Apr 30 10:02:47 2019> WARNING!!! 
Error resetting original Supervisor-1
image links, continuing migration ...
<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 ...

Action to be performed: Use the migrate standby_bootup command on the active Supervisor-4 Module when it becomes active and manually copy the image file and boot parameters.