cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
674
Views
0
Helpful
2
Replies
lni1
Beginner

NVRAM problem on routeprocessor SUP720 after conversion to hybrid mode

Hi,

Recently we converted several Sup720 from native IOS to hybrid mode (CatOS/IOS) without problems, but on two of them we can't access the NVRAM on the routeprocessor (wich means we can't save our configs, so these routeprocessors become pretty useless) :

******

Router#dir all-

Directory of flash:/

2 -rwx 36 Aug 28 2004 18:03:42 nv_hdr

4 -rwx 387 Jan 23 2004 13:34:23 config.text

1792000 bytes total (1789952 bytes free)

Directory of microcode:/

1 -r-- 2647926 <no date> CWPA_version_10.10

2 -r-- 4143806 <no date> CWTLC_version_10.10

Directory of nvram:/

%Error calling getdents for nvram:/ (Unknown error 89)

524288 bytes total (524236 bytes free)

Router#sh start

Router#

5w4d: NVRAM: WARNING- The device is not present

Router#wr

startup-config file open failed (Not enough space)

*****

On the Cisco website I didn't find any useful info on these errors. Does anyone has an idea if this could be a hardware problem on these sup720's, or can we fix this with a software command or upgrade ?

Thanks in advance,

Philippe

1 ACCEPTED SOLUTION

Accepted Solutions
Prashanth Krishnappa
Cisco Employee

I think you are seeing bug CSCeb74183 on the MSFC3.

Description:

When the user loads an MSFC3 with the CONFIG_FILE= set in the rommon, the user is unable to save

the running config to startup-config. The show startup config also fails with an error code 89.

The workaround for this issue is to unset the CONFIG_FILE variable in the MSFC rommon.

The user will run into this situation when he migrates from Native IOS to CatOs or if he

intentionally removes the value of the CONFIG_FILE variable in the MSFC rommon.

The error message displayed is "startup-config file open failed (Not enough space)" when doing a wr

mem and when viewing nvram using dir nvram:, the error message displayed is "%Error calling getdents

for nvram:/ (Unknown error 89)"

It is observed that if the CONFIG_FILE variable is unset in the MSFC3 rommon then user is able to

"wr mem" and display the contents of the nvram.

The following procedure should resolve this issue:

With the sup booted up, switch console into the MSFC3, put it into ROMMON and do the following:

rommon 1 > priv

You now have access to the full set of monitor commands.

Warning: some commands will allow you to destroy your

configuration and/or system images and could render

the machine unbootable.

rommon 2 > nvram_erase

Enter in hex the start address [0xbe020000]: be000000

Enter in hex the test size or length in bytes [0x100]: 200000

3) reset the system

rommon 3 > reset

Do NOT make a mistake with this, or it will destroy the MSFC NVRAM.

After that, set the config register to 0x2102 and set the boot variable by typing in the following:

rommon 1 >confreg 0x2102

rommon 2 >BOOT=bootflash:MSFC-image.bin <-Make sure this is the exact filename-please verify!

rommon 3 >sync

rommon 4 >reset

If it comes back up to ROMMON, just type "boot", but it should boot up.

Once booted up, change the hostname and test if you can write the change. You should be able to.

View solution in original post

2 REPLIES 2
Prashanth Krishnappa
Cisco Employee

I think you are seeing bug CSCeb74183 on the MSFC3.

Description:

When the user loads an MSFC3 with the CONFIG_FILE= set in the rommon, the user is unable to save

the running config to startup-config. The show startup config also fails with an error code 89.

The workaround for this issue is to unset the CONFIG_FILE variable in the MSFC rommon.

The user will run into this situation when he migrates from Native IOS to CatOs or if he

intentionally removes the value of the CONFIG_FILE variable in the MSFC rommon.

The error message displayed is "startup-config file open failed (Not enough space)" when doing a wr

mem and when viewing nvram using dir nvram:, the error message displayed is "%Error calling getdents

for nvram:/ (Unknown error 89)"

It is observed that if the CONFIG_FILE variable is unset in the MSFC3 rommon then user is able to

"wr mem" and display the contents of the nvram.

The following procedure should resolve this issue:

With the sup booted up, switch console into the MSFC3, put it into ROMMON and do the following:

rommon 1 > priv

You now have access to the full set of monitor commands.

Warning: some commands will allow you to destroy your

configuration and/or system images and could render

the machine unbootable.

rommon 2 > nvram_erase

Enter in hex the start address [0xbe020000]: be000000

Enter in hex the test size or length in bytes [0x100]: 200000

3) reset the system

rommon 3 > reset

Do NOT make a mistake with this, or it will destroy the MSFC NVRAM.

After that, set the config register to 0x2102 and set the boot variable by typing in the following:

rommon 1 >confreg 0x2102

rommon 2 >BOOT=bootflash:MSFC-image.bin <-Make sure this is the exact filename-please verify!

rommon 3 >sync

rommon 4 >reset

If it comes back up to ROMMON, just type "boot", but it should boot up.

Once booted up, change the hostname and test if you can write the change. You should be able to.

Hello,

Your info solved our NVRAM problem.

Thanks a lot for your help,

Philippe