cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements
Join Customer Connection to register!
351
Views
10
Helpful
6
Replies
Highlighted
Participant

Cisco 7600_Configuration register is 0x2102 (will be 0x0 at next reload)

Hi Frdz,

 

We have CISCO7609-S (M8500) with RSP720, We observed below error with config register value.

 

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

 

------------------ show version ------------------


Cisco IOS Software, c7600rsp72043_rp Software (c7600rsp72043_rp-ADVENTERPRISEK9-M), Version 15.5(3)S5, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2017 by Cisco Systems, Inc.
Compiled Wed 18-Jan-17 06:12 by prod_rel_team

 

 

507024K bytes of Internal ATA PCMCIA card (Sector size 512 bytes).
Configuration register is 0x2102 (will be 0x0 at next reload)

 

 

Current Processor Information :
-------------------------------
               Active Location = slot 5
        Current Software state = ACTIVE
       Uptime in current state = 31 weeks, 4 days, 8 hours, 2 minutes
                 Image Version = Cisco IOS Software, c7600rsp72043_rp Software (c7600rsp72043_rp-ADVENTERPRISEK9-M), Version 15.5(3)S5, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2017 by Cisco Systems, Inc.
Compiled Wed 18-Jan-17 06:12 by prod_rel_team
                          BOOT = disk0:/c7600rsp72043-adventerprisek9-mz.155-3.S5.bin,1;disk0:c7600rsp72043-adventerprisek9-mz.122-33.SRE13.bin,1;
        Configuration register = 0x2102 (will be 0x0 at next reload)

Peer (slot: unavailable) information is not available because it is in 'DISABLED' state

 

Pls suggest.

 

Thanks in advance.

 

Regards,

Vijay

6 REPLIES 6
Highlighted
VIP Mentor

Hi

Please check this link:

https://supportforums.cisco.com/t5/wan-routing-and-switching/config-register-value-changes-automatically/td-p/2048445

 

Hope it is useful

:-)




>> Marcar como útil o contestado, si la respuesta resolvió la duda, esto ayuda a futuras consultas de otros miembros de la comunidad. <<
Highlighted

Thanks Julio.

Highlighted

You are welcome, please keep us posted about the TAC resolution.

 

Thanks 




>> Marcar como útil o contestado, si la respuesta resolvió la duda, esto ayuda a futuras consultas de otros miembros de la comunidad. <<
Highlighted
Hall of Fame Community Legend


@vinayjaiswal wrote:

0x2102 (will be 0x0 at next reload)


Raise a TAC Case.  I think the supervisor card is toast.

Highlighted

Hi Leo,

 

I have raised TAC case with Cisco, I will let you know tac analysis.

Highlighted

Hi Team,

 

Here is TAC update:

 

Problem Description:

Config-register change.

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

 

Analysis:

config-register is a unique config command.  It actually does not require a write mem to take effect.  The config-register is a persistent rommon variable and is used to determine the boot sequence.  It should not change on power cycle or reload.

 
Regarding to the outputs we can see the NVRAM diagnostic test has been passed successfully

 

Apr 19 15:38:42.928 IST: %DIAG-SP-6-TEST_RUNNING: Module 5: Running TestNvramBatteryMonitor{ID=34} ...

Apr 19 15:38:42.928 IST: %DIAG-SP-6-TEST_OK: Module 5: TestNvramBatteryMonitor{ID=34} has completed successfully

 

 And per the fallowing registeres, they confirms that the NVRAM battery is fine.

[FE480050]:                          INTR_STATUS_REG = 0000
[FE480054]:                            INTR_MASK_REG = D000
 

“In the output, look at register values [FE080050] and [FE080054]. If the register value [FE080050] is above 0000 it confirms that SP runs with low NVRAM”

 

 

So since the configuration register has been changed successfully , and you were able to save the configuration , then we can confirm that the device is fine.

 

 

CB-DC-CORE-R02(config)#config 0x2102
CB-DC-CORE-R02(config)#end
CB-DC-CORE-R02#wr
Building configuration...
[OK]

507024K bytes of Internal ATA PCMCIA card (Sector size 512 bytes).
Configuration register is 0x2102 

 

Action Plan:

 

Keep your eye on the device, if the config register has been changed again then we need to check the NVRAM again, for now the NVRAM is fine and is not pointing to any issue.

 

>> We followed below POA.

 

Also we need to proceed with the following action plan

 

1-      Try to change the config register again to the old value 0x2102

2-      Save the configuration  --- > please let me know if you get any error message during the saving process

3-      We need to test the nvram using the following

 

Run the test using the following command

 

diagnostic start module 5 test TestNvramBatteryMonitor

 

then collect the following outputs

 

show diagnostic result module 5 test testNvramBatteryMonitor detail

show logging

show version

 

 

remote  login switch

show platform hardware asicreg naboo all.

 

Regards,

Vijay

 

Content for Community-Ad