Problems migrating a Sup720 config to a Sup2T

bgfl-tech · ‎07-05-2012

Hi,

My question relates to the migration of an existing Sup720 configuration to a new Sup2T. At present we have a Sup2T chassis in the lab running 15.0(1)SY1 and a production Sup720 chassis running 12.2(33)SXI5.

I've taken a copy of the production startup-config, renamed it to 'startup-config-BGFL_6509_MBAS-020712' and copied it to the bootdisk (and slave bootdisk) of the new Sup2Ts.

I've then added the command 'boot config bootdisk:startup-config-BGFL_6509_MBAS-020712' in an attempt to boot from that config and have the Sup2T migrate it to the new config standards (particularly from a QoS perspective as mentioned here :- http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/ios/15.0SY/configuration/guide/qos_migration.html)

!

boot-start-marker

boot system flash bootflash:s2t54-advipservicesk9-mz.SPA.150-1.SY1.bin

boot config bootdisk:startup-config-BGFL_6509_MBAS-020712

...

Router#sh bootvar

BOOT variable = bootflash:s2t54-advipservicesk9-mz.SPA.150-1.SY1.bin,1;

CONFIG_FILE variable = bootdisk:startup-config-BGFL_6509_MBAS-020712

BOOTLDR variable =

Configuration register is 0x2102

Standby BOOT variable = bootflash:s2t54-advipservicesk9-mz.SPA.150-1.SY1.bin,1;

Standby CONFIG_FILE variable = bootdisk:startup-config-BGFL_6509_MBAS-020712

Standby BOOTLDR variable =

Standby Configuration register is 0x2102

!

However after I reload the chassis the startup and running-config remains unchanged although I do see the following message in the syslogs but nothing in the 'sh logging system' output:-

*Jul 5 14:29:55.975: %CAT6K_CLI_CONV-6-LOOK_LOG: CLI from legacy configuration has been detected and converted to new format, please look at 'show logging system' output for details on what has been converted

I've also attempt to copy from 'startup-config-BGFL_6509_MBAS-020712' directly into the running config but that was also unsuccessful:-

Router#copy bootdisk:startup-config-BGFL_6509_MBAS-020712 running-config

Destination filename [running-config]?

QM Warning: Policy has reserved Exception classes. applying the exceptions on all protocols

18702 bytes copied in 3.664 secs (5104 bytes/sec)

I also tried the 'config replace' command without any success:-

Router#configure replace bootdisk:startup-config-BGFL_6509_MBAS-020712

This will apply all necessary additions and deletions

to replace the current running configuration with the

contents of the specified configuration file, which is

assumed to be a complete configuration, not a partial

configuration. Enter Y if you are sure you want to proceed. ? [no]: y

*Jul 5 14:50:11.831: Rollback:Acquired Configuration lock.

Total number of passes: 1

Rollback Done

I'm hoping it's something obvious (that I'm not seeing) as to why I can't get this work.

Thanks in advance

Ivan Shirshin · ‎07-05-2012

Hi,

As far as I see, you are receiving a notification/warning messages due to upgrade between different supervisors but not any failure.

QM Warning: Policy has reserved Exception classes. applying the exceptions on all protocols

This warning message you can ignore. By default, there is a set of reserved exception classes which gets applied on the control plane interface. If you remove the service policy from the control-plane interface and apply the service policy which has different class-map names other than the default exception class-map names, this message will not be printed. It get's displayed only if you make use of the default exception classes in the service-policy.

As for the

*Jul 5 14:29:55.975: %CAT6K_CLI_CONV-6-LOOK_LOG: CLI from legacy configuration has been detected and converted to new format, please look at 'show logging system' output for details on what has been converted

it does not show any command in the "show logg system" output, so not mismatching commands. Device just detected the configuration is from older platform and notified you.

Finally, why do you think the "configure replace" has failed? it shows "Rollback Done ".

I suggest you to compare current and original configuration again to make sure there are identical. Then, for the peace of mind, save it and reload once again. I think it won't show you any of the messages you have seen right after upgrade.

Kind Regards,
Ivan

**Please grade this post if you find it useful.

Kind Regards,
Ivan

bgfl-tech · ‎07-05-2012

Hi Ivan,

Thank you for your response but the reason I think the configuration has failed is because none of the 'production' configuration (as held in the 'startup-config-BGFL_6509_MBAS-020712' file) has been added to either the running or startup-config files on the Sup2T after I went through the processes described above, i.e. the default configuration remained unchanged.

What I expected would be required was a one-time boot off the original configuration (boot config bootdisk:startup-config-BGFL_6509_MBAS-020712), a wr mem to save the newly migrated config to nvram and then the removal of the 'boot config' command and then a reload. As it stands it seems like my 'production' config is being ignored when I attempt to either boot directly from it or copy it into the current running config?

Ivan Shirshin · ‎07-05-2012

Hi,

Is the following line in the startup configuration now?

boot config bootdisk:startup-config-BGFL_6509_MBAS-020712

And after "configure replace", were you checking startup or running configuration for changes?

Please post here the outputs of a "dir bootdisk:".

Kind Regards,
Ivan

**Please grade this post if you find it useful.

Kind Regards,
Ivan

bgfl-tech · ‎07-05-2012

Hi,

Yes, 'boot config bootdisk:startup-config-BGFL_6509_MBAS-020712' remains in the running and startup-config. The only changes I've made to the default config (as attached) are the addition of the 'boot config' command and an IP to vlan 1 (and making a single port a switchport) in order to tftp the 'startup-config-BGFL_6509_MBAS-020712' across to the bootdisk(s).

After using the 'configure replace' command I looked at both the running and startup-config of which neither had changed.

Below is the output of 'dir bootdisk:'

Router#dir bootdisk:

Directory of bootdisk:/

1 -rw- 33554432 Jun 8 2012 05:58:10 +00:00 sea_console.dat

2 -rw- 89418128 Jun 8 2012 06:02:22 +00:00 s2t54-advipservicesk9-mz.SPA.150-1.SY1.bin

3 -rw- 33554432 Jun 8 2012 06:05:06 +00:00 sea_log.dat

4 -rw- 18701 Jul 5 2012 16:58:08 +00:00 startup-config-BGFL_6509_MBAS-020712

1024557056 bytes total (867909632 bytes free)

Router#dir slaveboo

Router#dir slavebootdisk:

Directory of slavebootdisk:/

1 -rw- 33554432 Jun 8 2012 05:41:44 +00:00 sea_console.dat

2 -rw- 89418128 Jun 8 2012 05:45:54 +00:00 s2t54-advipservicesk9-mz.SPA.150-1.SY1.bin

3 -rw- 33554432 Jun 8 2012 05:48:42 +00:00 sea_log.dat

5 -rw- 18540 Jul 5 2012 16:58:08 +00:00 startup-config-BGFL_6509_MBAS-020712

1024557056 bytes total (867942400 bytes free)

I've attached the original config also (with a few security related-lines removed).

Ivan Shirshin · ‎07-06-2012

Hi,

I checked for bugs but nothing really matches. If this is a lab device, could you connect to its console with terminal, reboot and collect the boot sequence logs including those when the system should load the config using "boot config" command? There could be some errors reported.

Kind Regards,
Ivan