[c-nsp] ouch 7204vxr reloaded

Michael Malitsky malitsky at netabn.com
Wed Apr 28 10:25:06 EDT 2010


In many cases (at least for us), it often makes much more sense to have
a cold/warm/hot spare than to maintain a support contract.
I've also had more than one case when TAC really couldn't help unless I
had a reproducible, "live" problem for them to troubleshoot.

Not trying to steer you away from SmartNet, just suggesting you consider
options.

Sincerely,
Michael Malitsky


> Date: Tue, 27 Apr 2010 14:53:28 -0700
> From: Mike <mike-cisconsplist at tiedyenetworks.com>
> To: "'Cisco-nsp'" <cisco-nsp at puck.nether.net>
> Subject: [c-nsp] ouch 7204vxr reloaded
> 
> Howdy,
> 
>     Well that was fun, I discovered that my trusty 7204vxr reloaded
> unexpectedly and I find myself without a good explanation. Show
version
> gives me 'processor memory pairity error':
> 
> System returned to ROM by processor memory parity error at PC
> 0x60640F70, address 0x0 at 03:09:00 PST Tue Apr 27 2010
> System restarted at 04:10:28 PDT Tue Apr 27 2010
> System image file is "disk0:c7200-is-mz.123-26.bin"
> 
>     and digging thru the 'show tech' gave me:
> 
<snip>
> 
>     So my inexperienced glancing would say it was something to do with
> OSPF. My question tho is, #1, how do I really debug a problem like
> this, and #2, what would the minimum cisco contract be required to
make 
> sure I have access to the cco/bug advisor and possibly updated IOS for
this
> device? Its been a tank with absolutely zero issues in this enviorment
> for more than a year, but this event underscores the fact that we have
> no real support route and probabbly should get on some program even
for
> our little operation.
> 
> 
> Thanks.
> 
> Mike-




More information about the cisco-nsp mailing list