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:
Pid 3: Process "OSPF Hello" stack 0x63D733F0 savedsp 0x63D75660
Flags: analyze on_old_queue
Status 0x00000000 Orig_ra 0x00000000 Routine 0x00000000 Signal 0
Caller_pc 0x60CDAE84 Callee_pc 0x60806190 Dbg_events 0x00000000 State 1
Totmalloc 548640 Totfree 441612 Totgetbuf 15876
Totretbuf 0 Edisms 0x60CD71A4 Eparm 0x64A91E7C
Elapsed 0xC6E634 Ncalls 0xE09B9AA Ngiveups 0x491E
Priority_q 3 Ticks_5s 2 Cpu_5sec 81 Cpu_1min 40
Cpu_5min 8 Stacksize 0x2328 Lowstack 0x2328
Ttyptr 0x63D55FA8 Mem_holding 0x0 Thrash_count 0
Wakeup_reasons 0x0FFFFFFF Default_wakeup_reasons 0x0FFFFFFF
Direct_wakeup_major 0x00000000 Direct_wakeup_minor 0x00000000
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-
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
