cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1958
Views
0
Helpful
6
Replies

4500x VSS config-register not synced

apache_le
Level 1
Level 1

I have 2 4500x switches operate in VSS.  The current config-register value is 0x2101 and I want to change it to 0x2102.  I changed it on the primary, did a  write mem and the primary chassis says it will be 0x2012 at the next reboot.  However, the config-reigster on the standby chassis still says 0x2101.  I thought the config will be synced but it's not. How do I have the standby chassis to have 0x2102 at the next reboot?

6 Replies 6

Leo Laohoo
Hall of Fame
Hall of Fame

Can you try using the "session switch 2" command?

you can't configure on standby

zarjer
Level 1
Level 1
Have you solved this problem? What's the resolution for this? We are about to reload both core switches and I'm confused if this will not be an issue?
Active: 0x2102 on next reload
Standby: 0x2101

Alan.A
Level 1
Level 1

What is the resolution for this problem?

daniel_boubeta
Level 1
Level 1

It seems that the issue is with the output of the command:

sw#show bootvar
BOOT variable = bootflash:cat4500e-universalk9.SPA.03.11.05.E.152-7.E5.bin,1;
CONFIG_FILE variable does not exist
BOOTLDR variable does not exist
Configuration register is 0x2101 (will be 0x2102 at next reload)

Standby BOOT variable = bootflash:cat4500e-universalk9.SPA.03.11.05.E.152-7.E5.bin,1;
Standby CONFIG_FILE variable does not exist
Standby BOOTLDR variable does not exist
Standby Configuration register is 0x2101
Standby Configuration register is 0x2101
sw#

 

If you connect to the standby switch you can see that the register will change on next reboot:

sw#session module 1
Connecting to standby virtual console
Type "exit" or "quit" to end this session


sw-standby-console#show bootvar

BOOT variable = bootflash:cat4500e-universalk9.SPA.03.11.05.E.152-7.E5.bin,1;
CONFIG_FILE variable does not exist
BOOTLDR variable does not exist
Configuration register is 0x2101 (will be 0x2102 at next reload)

sw-standby-console#

Alan.A
Level 1
Level 1

I also encountered this exact problem with 4500x switch model. Me and TAC decided to reboot the entire chassis and it booted normally to the new image 03.11.04.E