Cisco uBR10000 Series Universal Broadband Routers

February 23, 2007

NOTICE:

THIS FIELD NOTICE IS PROVIDED ON AN "AS IS" BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTY OF MERCHANTABILITY. YOUR USE OF THE INFORMATION ON THE FIELD NOTICE OR MATERIALS LINKED FROM THE FIELD NOTICE IS AT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE THIS FIELD NOTICE AT ANY TIME.

Products Affected

Problem Description

When upgrading to an image that has the fix for CSCsc61630, a corrupted pointer in NVRAM may be detected, causing the configuration to be ignored.

Background

When upgrading to the 12.3(21)BC image from an older release, an invalid NVRAM private pointer may be detected due to more stringent checks added to ensure validity of nvram contents.

The router will boot and display the error message:

NV: Invalid Pointer value(6357F3CC) in private configuration structure showing that the nvram has a stale, unerased private-configuration pointer in NVRAM.

It will then enter the system configuration dialog.

Answer "no" and you will see following errors:

--- System Configuration Dialog --- 

Would you like to enter the initial configuration dialog? [yes/no]: no 



Press RETURN to get started! 



*Dec 19 05:38:46.743: Downloading Microcode: file=system:pxf/c10k-15-ucode.101.0.0.0, version=101.0.0.0, description=Experimental Software created Mon 27-Nov-06 21:44 by aiding in view aiding-clipper_ucode_pcha 

*Dec 19 05:38:47.395: NV: Invalid Pointer value(201A9BC4) in private configuration structure 

*Dec 19 05:38:47.403: NV: Invalid Pointer value(201A9BC4) in private configuration structure 

*Dec 19 05:38:47.407: %SYS-4-NV_BLOCK_INITFAIL: Unable to initialize the geometry of nvram 

Router#dir nvram: 

Directory of nvram:/ 

No files in directory 

No space information available 

Router# 

Problem Symptoms

The router boots and displays the error message:

NV: Invalid Pointer value(6357F3CC) in private configuration structure

then goes into the system configuration dialog.

Workaround/Solution

Before upgrading to 12.3(21)BC, with a 12.3(17)BC or older release image :

1. copy {startup|running}-config disk0:saved-config

2. erase /all nvram:

3. write memory

4. (optional) copy disk0:saved-config startup-config

5. Reload with 12.3(21)BC image.

Note: erase nvram: is inadequate and may leave a stale pointer in private-config in nvram. Hence the need to use erase /all nvram: to clean nvram completely.

DDTS

To follow the bug ID link below and see detailed bug information, you must be a registered user and you must be logged in.

Revision History

For More Information

If you require further assistance, or if you have any further questions regarding this field notice, please contact the Cisco Systems Technical Assistance Center (TAC) by one of the following methods:

• Open a service request on Cisco.com
• By email
• By telephone

Receive Email Notification For New Field Notices

Product Alert Tool - Set up a profile to receive email updates about reliability, safety, network security, and end-of-sale issues for the Cisco products you specify.