problem of "show bootvar" result

Unanswered Question
Jan 23rd, 2008

Hi,

I have one Catalyst 6509 with 2 SUP1. When execute "show bootvar", the two supervisor engine have different parameter. Even I change "boot system" & "config-register" again, the boot parameter between two supervisor engine still different. Please also gove me some help to solve this problem.

Show Version :

Cisco Internetwork Operating System Software

IOS (tm) c6sup2_rp Software (c6sup2_rp-PSV-M), Version 12.1(13)E17, RELEASE SOFTWARE (fc1)

Technical Support: http://www.cisco.com/techsupport

Copyright (c) 1986-2005 by cisco Systems, Inc.

Compiled Thu 25-Aug-05 07:56 by tinhuang

Image text-base: 0x40008C00, data-base: 0x417A8000

ROM: System Bootstrap, Version 12.1(4r)E, RELEASE SOFTWARE (fc1)

BOOTLDR: c6sup2_rp Software (c6sup2_rp-PSV-M), Version 12.1(13)E17, RELEASE SOFTWARE (fc1)

Core-01 uptime is 1 week, 1 day, 4 hours, 54 minutes

Time since Core-01 switched to active is 1 week, 1 day, 4 hours, 53 minutes

System returned to ROM by power-on (SP by power-on)

System restarted at 10:50:51 TWN Sun Jan 13 2008

System image file is "sup-bootflash:c6sup12-psv-mz.121-13.E17.bin"

cisco Catalyst 6000 (R7000) processor with 112640K/18432K bytes of memory.

Processor board ID SAL0551FG7W

R7000 CPU at 300Mhz, Implementation 39, Rev 3.3, 256KB L2, 1024KB L3 Cache

Last reset from power-on

X.25 software, Version 3.0.0.

Bridging software.

1 FlexWAN controller (1 ATM).

16 Virtual Ethernet/IEEE 802.3 interface(s)

48 FastEthernet/IEEE 802.3 interface(s)

22 Gigabit Ethernet/IEEE 802.3 interface(s)

1 ATM network interface(s)

381K bytes of non-volatile configuration memory.

16384K bytes of Flash internal SIMM (Sector size 512K).

Standby is up

Standby has 112640K/18432K bytes of memory.

Configuration register is 0x0

Show Bootvar :

BOOT variable = sup-bootflash:c6sup12-psv-mz.121-13.E17.bin,1

CONFIG_FILE variable does not exist

BOOTLDR variable = bootflash:c6msfc2-boot-mz.121-11b.E.bin

Configuration register is 0x0

Standby is up

Standby has 112640K/18432K bytes of memory.

Standby BOOT variable = bootflash:c6sup12-psv-mz.121-13.E17.bin,1

Standby CONFIG_FILE variable =

Standby BOOTLDR variable = bootflash:c6msfc2-boot-mz.121-11b.E.bin

Standby Configuration register is 0x2102

Show Redund states :

sh red states

my state = 13 -ACTIVE

peer state = 8 -STANDBY HOT

Mode = Duplex

Unit = Primary

Unit ID = 1

Redundancy Mode (Operational) = Route Processor Redundancy Plus

Redundancy Mode (Configured) = Route Processor Redundancy Plus

Split Mode = Disabled

Manual Swact = Enabled

Communications = Up

client count = 11

client_notification_TMR = 30000 milliseconds

keep_alive TMR = 9000 milliseconds

keep_alive count = 0

keep_alive threshold = 18

RF debug mask = 0x0

Best Regards,

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
ankbhasi Wed, 01/23/2008 - 23:07

Hi Jack,

There is no harm here and that is an expected behavior. If you are on RP (route processor) console the bootvar is referring to sup-bootflash.

If you do 'remote command switch show bootvar', it shows bootflash i.e. it is local to the supervisor.

Now, you do 'sh bootvar' on the RP what supposed show you settings for the active and standby supervisor. For the active - no

problem, we just read it on RP and get sup-bootflash. To get the same for the standby, we need ask standby *supervisor* for it. It returns bootflash that is local to the supervisor.

So, to summarize. The output you've sent doesn't show any problem and is an expected behavior.

Now coming to the config register settings it is fine on standby but on your active it is showing 0x0 which is the settings on RP of active sup. Just go ahead and change the config register as 0x2102 on the active RP and you will be good to go.

HTH

Ankur

*Pls rate all helpfull post

jackson.ku Wed, 01/23/2008 - 23:57

Hi,

I tried to modified config-register and write mem, then executed show ver again, the config-register still 0x0 :

Core-01#config t

Enter configuration commands, one per line. End with CNTL/Z.

Core-01(config)#config-reg

Core-01(config)#config-register 0x2102

Core-01(config)#^Z

Core-01#

Core-01#

Core-01#

Core-01#

Core-01#wri mem

Warning: Attempting to overwrite an NVRAM configuration previously written

by a different version of the system image.

Overwrite the previous NVRAM configuration?[confirm]y

Building configuration...

[OK]

Core-01#sh bootvar

BOOT variable = sup-bootflash:c6sup12-psv-mz.121-13.E17.bin,1

CONFIG_FILE variable does not exist

BOOTLDR variable = bootflash:c6msfc2-boot-mz.121-11b.E.bin

Configuration register is 0x0

Standby is up

Standby has 112640K/18432K bytes of memory.

Standby BOOT variable = bootflash:c6sup12-psv-mz.121-13.E17.bin,1

Standby CONFIG_FILE variable =

Standby BOOTLDR variable = bootflash:c6msfc2-boot-mz.121-11b.E.bin

Standby Configuration register is 0x2102

Core-01#remote command switch show bootvar

Core-01-sp#

BOOT variable = bootflash:c6sup12-psv-mz.121-13.E17.bin,1

CONFIG_FILE variable =

BOOTLDR variable = bootflash:c6msfc2-boot-mz.121-11b.E.bin

Configuration register is 0x10F (will be 0x2102 at next reload)

Core-01#

Maybe I must reboot this switch, break into ROMMON during RP booting, then modify confreg, not modify config-register 0x2102 in running-config?

The reason why I asked this question is I have FlexWAN & PA-A3-OC3 module installed at slot 3. Last week this switch reloaded. All configuration back exceptd ATM module configuration. The ATM module configuration still exist at "show start", but not exist at "show runn". I copy ATM module configuration from startup-config to running-config, It work again. I an afraid this problem related with different bootvar symptom. Can you please help to identify tese problem?

Best Regards,

ankbhasi Thu, 01/24/2008 - 06:33

Hi Jack,

The problem you described does not seem to be related with boot variable settings. For config register part as you said to take in rommon and change the settings there should work and if you can arrange some change window then only go ahead with the step.

Regards,

Ankur

*Pls rate all helpfull post

jackson.ku Thu, 01/24/2008 - 06:45

Hi Ankur,

Many thanks. Do you have any suggestion how to troubleshoot the FlexWan & PA-A3-OC3 module failed to execute startup-config problem?

Best Regards,

ankbhasi Thu, 01/24/2008 - 06:53

Hi Jack,

I am sorry but I do not have much experience on Flexwan card and PA-A3-OC3 card. May be some other experts can throw more light on the same.

Regards,

Ankur

*Pls rate all helpfull post

jackson.ku Thu, 01/24/2008 - 07:18

Hi Ankur,

Thanks a lot. I will start new conversation for my another problem.

Best Regards,

PS. I tried to rated your posts, but not succeeded. But rated to another people's posts succeeded .... >_< Why???

Actions

This Discussion