I have fixed my 2620 by replacing the NVRAM chip 28c256N20, on mine it
is U23 located on the mother board next to the BootROM.
It is no more difficult to replace than a BootRom it is a 32 pin PLCC
device and on a hardware 1.2 rev B0 (pn 73-2843-07) it is in a socket.
Check on yours first, on older routers it was soldered to the mother
board and replacement is non-trivial.
You must follow normal antistatic precautions and take care when
removing the chip.
BTW the chip costs about #25 inc. vat and carriage from any of the major
component suppliers in the UK. But make sure that you get an 'N' or 'J'
version. They are 32 pin PLCC others are different form factors.
In article , Peter Whittle
writes
>Check if your NVRAM is ok.
>
>I have a similar problem on a 2620. But in my case it is more obvious as
>whenever you attempt to 'wr' to copy the running to start config you get
>an error diagnostic.
>
>Failed to write environment to NVRAM.
>
>The copy itself seems to work ok. As far as I can see the 28C256N-20
>NVRAM chip is u/s? There are also some known issues with 11.3(2)xa4
>and NVRAM handling.
>
>BTW I also get the same error if I attempt a 'sync' command from rommon
>to save the environment to NVRAM.
>
>Peter
>
>
>
>In article , EA Louie
> writes
>>----- Original Message -----
>>From: John Neiberger
>>To:
>>Sent: Wednesday, June 20, 2001 7:46 AM
>>Subject: Config Register Weirdness, again... [7:9181]
>>
>>
>>> Okay, what's the deal here? Look at this output:
>>>
>>> Configuration register is 0x2102 (will be 0x4000 at next reload)
>>>
>>> RARAP#conf t
>>> Enter configuration commands, one per line. End with CNTL/Z.
>>> RARAP(config)#config-reg 0x2102
>>> RARAP(config)#end
>>> RARAP#sho ver
>>> Cisco Internetwork Operating System Software
>>>
>>> [lotsa trimming]
>>>
>>> Configuration register is 0x2102 (will be 0x3922 at next reload)
>>>
>>> Why is the config register going to reload at 0x3922?? I just set the
>>> darn thing to 0x2102 and you can see that change occurred. I was trying
>>> to get rid of the 'will be 0x4000 at next reload'. I have no idea why
>>> that was there to begin with but it should not be there. Is this
>>> something that I'll have to fix from the console port? I can't reload
>>> the router because it was put into production this morning. Why is it
>>> set to 0x3922?
>>>
>>> I'm guessing that the guy who installed this was playing around with
>>> the confreg utility in rommon and we'll have to go back to rommon to fix
>>> it.
>>>
>>> Any ideas?
>>
>>GREMLINS, or 2102 instead of 0x2102, or it's broken
>>
>>go in and config it *again* for config-reg 0x2102 and see if sh ver gives
>>you yet another value 'at next reload' - maybe the config-reg statement on
>>*your* router is really a random-number generator...
>>
>>:-)
>>
>>-e-
>>
>>>
>>> Thanks,
>>> John
>>html
>>Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
>>
>
--
Peter Whittle
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=9504&t=9181
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
