Problems migrating a Sup720 config to a Sup2T

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.

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

Problems migrating a Sup720 config to a Sup2T

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 Shirshin
**Please grade this post if you find it useful.

Re: Problems migrating a Sup720 config to a Sup2T

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?

Re: Problems migrating a Sup720 config to a Sup2T

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.

Re: Problems migrating a Sup720 config to a Sup2T

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

Kind Regards,
Ivan Shirshin
**Please grade this post if you find it useful.

The ProblemEnter EVCsHow It Works (Ingress)How It Works
(Egress)Step-by-Step ExampleFinal Thoughts The ProblemOn traditional
switches whenever we have a trunk interface we use the VLAN tag to
demultiplex the VLANs. The switch needs to determine which MAC ...
view more

The ProblemEnter EVCsHow It Works (Ingress)How It Works
(Egress)Step-by-Step ExampleFinal Thoughts Introduction: Netdr is a tool
available on a RSP720, Sup720 or Sup32 that allows one to capture
packets on the RP or SP inband. The netdr command can be use...
view more

IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...
view more