[c-nsp] 2611XM problem

Ganbold ganbold at micom.mng.net
Tue Nov 15 20:51:14 EST 2005


Corneliu and Chuck,

Thanks a lot for the help. Write erasing the nvram solved the problem.

Ganbold


At 11:05 PM 11/15/2005, you wrote:
>Try to erase the NVRAM.  If you cannot from prompt, then change first the
>config register to 0x2141 then reload.
>After the reload try to write erase the nvram.  If it works, then change the
>config back to 0x2102, reload and try to write the config to nvram.
>
>Corneliu
>
>-----Original Message-----
>From: cisco-nsp-bounces at puck.nether.net
>[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Church, Chuck
>Sent: Tuesday, November 15, 2005 4:44 PM
>To: Ganbold
>Cc: cisco-nsp at puck.nether.net
>Subject: RE: [c-nsp] 2611XM problem
>
>Can you write the config to flash or tftp?  If so, I'm guessing that
>maybe the NVRAM is bad.  Can you erase the NVRAM without crashing?
>
>
>Chuck Church
>Lead Design Engineer
>CCIE #8776, MCNE, MCSE
>Netco Government Services - Design & Implementation
>1210 N. Parker Rd.
>Greenville, SC 29609
>Home office: 864-335-9473
>Cell: 703-819-3495
>cchurch at netcogov.com
>PGP key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x4371A48D
>
>
>-----Original Message-----
>From: cisco-nsp-bounces at puck.nether.net
>[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Ganbold
>Sent: Tuesday, November 15, 2005 1:37 AM
>To: bep at whack.org
>Cc: cisco-nsp at puck.nether.net
>Subject: Re: [c-nsp] 2611XM problem
>
>Hi,
>
>I upgraded IOS to 12.2.31. But still I can't issue wr command.
>
>Router(config-if)#ip address 192.168.0.239 255.255.255.0
>Router(config-if)#no shut
>Router(config-if)#end
>Router#
>00:01:50: %LINK-3-UPDOWN: Interface FastEthernet0/0, changed state to up
>00:01:50: %SYS-5-CONFIG_I: Configured from console by console
>00:01:51: %LINEPROTO-5-UPDOWN: Line protocol on Interface
>FastEthernet0/0,
>chanp
>Router#wr
>
>
>Unexpected exception to CPUvector 1200, PC = 81118034
>-Traceback= 81118034 80454788 80454EB4 803F83C0 8032F378 8032F2EC
>8035DBA8
>8035C
>
>Writing crashinfo to flash:crashinfo_19930301-000156
>Queued messages:
>*** System received a SegV exception ***
>signal= 0xb, code= 0x1200, context= 0x81a771ac
>PC = 0x81118034, Vector = 0x1200, SP = 0x81e3b300
>
>System Bootstrap, Version 12.2(8r) [cmong 8r], RELEASE SOFTWARE (fc1)
>Copyright (c) 2003 by ci
>
>I don't know yet how to solve this issue.
>
>thanks,
>
>Ganbold
>
>At 08:48 AM 11/15/2005, you wrote:
> >-----BEGIN PGP SIGNED MESSAGE-----
> >Hash: SHA1
> >
> >Ganbold wrote:
> > > Hi,
> > >
> > > I have a problem with Cisco 2611XM. When I try to issue write memory
> > > command system says following error
> > > and reloads.
> > > Is this issue related with physical memory? How can I solve this
>problem?
> > > I appreciate if somebody advise me regarding this issue.
> > >
> >
> >No, this is likely a software bug.
> >
> >
> > > -----------------------------------------------------------------
> > > Mar  1 08:07:30.534 GMT: %SYS-5-CONFIG_I: Configured from console by
>
> > consolewri
> > > te memory
> > >
> > > Unexpected exception to CPUvector 1200, PC = 81117480
> > > -Traceback= 81117480 804542DC 80454A08 803F7E60 8032EFE4 8032EF58
>8035D78C
> > > 80351
> > > 4EC 80360794 803F201C
> > >
> > > Writing crashinfo to flash:crashinfo_19930301-000744
> > > Queued messages:
> > > *** System received a SegV exception ***
> > > signal= 0xb, code= 0x1200, context= 0x81a735b4
> > > PC = 0x81117480, Vector = 0x1200, SP = 0x81e37548
> > >
> > > System Bootstrap, Version 12.2(8r) [cmong 8r], RELEASE SOFTWARE
>(fc1)
> > > Copyright (c) 2003 by cisco Systems, Inc.
> > > C2600 platform with 131072 Kbytes of main memory
> > > -----------------------------------------------------------------
> > >
> >
> >This is the version of the system bootstrap and not the version of the
> >image you are running.  There have been a number of bugs that exhibit
>this
> >behavior, but it would help to know what version you are actually
>running
> >to determine if you are hitting one of them and if it is fixed.
> >
> >At this point, you should probably open a case to research the issue.
> >
> >- --
> >=========
> >bep
> >
> >-----BEGIN PGP SIGNATURE-----
> >Version: GnuPG v1.4.0 (MingW32)
> >
> >iD8DBQFDeTB5E1XcgMgrtyYRAjLoAKCBW2BCozWYbcASFdRyna3t4Dh4sACfXUTA
> >Gr29RjCYqQUyAov9FAVZuRw=
> >=+fx8
> >-----END PGP SIGNATURE-----
>
>_______________________________________________
>cisco-nsp mailing list  cisco-nsp at puck.nether.net
>https://puck.nether.net/mailman/listinfo/cisco-nsp
>archive at http://puck.nether.net/pipermail/cisco-nsp/
>
>_______________________________________________
>cisco-nsp mailing list  cisco-nsp at puck.nether.net
>https://puck.nether.net/mailman/listinfo/cisco-nsp
>archive at http://puck.nether.net/pipermail/cisco-nsp/



More information about the cisco-nsp mailing list