10-14-2003 12:41 AM - edited 03-02-2019 10:59 AM
When i reload:
CS-4006-A#reload
Reload to the ROM monitor disallowed from a telnet line.
Set the configuration register boot bits to be non-zero.
... so i change the register
CS-4006-A#conf t
Enter configuration commands, one per line. End with CNTL/Z.
CS-4006-A(config)#con
CS-4006-A(config)#config-register 0x2102
CS-4006-A(config)#exit
CS-4006-A#wr
Building configuration...
Compressed configuration from 13077 bytes to 3733 bytes[OK]
but the sh ver state that register will be 0x0 at next reload !
CS-4006-A#sh ver
Cisco Internetwork Operating System Software
IOS (tm) Catalyst 4000 L3 Switch Software (cat4000-IS-M), Version 12.1(12c)EW, EARLY D
TAC Support: http://www.cisco.com/tac
Copyright (c) 1986-2002 by cisco Systems, Inc.
Compiled Thu 22-Aug-02 19:28 by hqluong
Image text-base: 0x00000000, data-base: 0x00CA7148
CRC32 failed for NVRAM at 0x54000000
Erasing NVRAM area at 0x54000000
ROM:
Dagobah Revision 50, Swamp Revision 16
CS-4006-A uptime is 9 weeks, 4 days, 22 hours, 49 minutes
System returned to ROM by power-on
System image file is "bootflash:cat4000-is-mz.121-12c.EW.bin"
cisco WS-C4006 (MPC8245) processor (revision 7) with 262144K bytes of memory.
Processor board ID FOX064311H1
Last reset from PowerUp
96 FastEthernet/IEEE 802.3 interface(s)
26 Gigabit Ethernet/IEEE 802.3 interface(s)
467K bytes of non-volatile configuration memory.
Configuration register is 0x2102 (will be 0x0 at next reload)
WHhy ??
10-14-2003 01:58 AM
Hi,
it seems to me like you might have problems with your NVRAM
(CRC32 failed for NVRAM at 0x54000000
Erasing NVRAM area at 0x54000000)
So I'd try to
1) backup the running config to tftp server
2) wr erase - clears the NVRAM
3) wr - saves the running config to the start-up config
4) sh start-up - checks if the wr command was successful
5) sh ver
The error message might disappear.
If it remains, I'd reload the switch. It's a little dangerous - if the NVRAM is damaged, you might loose your complete config.
6) confreg .....- set the config reisters to proper value in ROM monitor mode
7) boot ..... - manually from ROM monitor
8) sh ver - check the registers and NVRAM problem
Regards,
Milan
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide