[c-nsp] Mysterious 7513 reboot

[Chris Cappuccio]

You're running out of memory, you should move back to 12.0 if you aren't already
there

And, from your last post, the RSP clearly gave a memory parity error

It could be a blip or it could be bad RAM.  RSP4s are so cheap you should
at least have one redundant module with sso turned on.  And the ram is so cheap
that you should replace it when you get a parity error.  Yuo can find the
sticks of 128MB 168-pin EDO ECC for less than $20 each, brand new, on the web.

If you want to take full advantage of ECC (single bit error correction, double
bit error failure) vs Parity (single bit error failure) then you need some
RSP4+ which are not expensive either

This 7500 stuff is junk so don't put too much time into it unless you have
very low demands from it.  I'd seriously think about upgrading to something
a little newer

Jeff Chan [cisco-nsp at jeffchan.com] wrote:
> Taking a closer look at our graphs showed a CPU spike
> earlier in the day, and the logs show:
> 
> Apr 25 07:15:36 mdsnwi-router-01 325: Apr 25 07:15:32: %LINK-3-UPDOWN: Interface Hssi12/0/0, changed state to down
> Apr 25 07:15:36 mdsnwi-router-01 326: Apr 25 07:15:33: %LINEPROTO-5-UPDOWN: Line protocol on Interface Hssi12/0/0, changed state to down
> Apr 25 07:15:36 mdsnwi-router-01 327: Apr 25 07:15:34: %BGP-5-ADJCHANGE: neighbor 144.228.52.181 Down Interface flap
> Apr 25 07:16:04 mdsnwi-router-01 328: Apr 25 07:16:00: %SYS-2-MALLOCFAIL: Memory allocation of 65536 bytes failed from 0x40478848, alignment 0
> Apr 25 07:16:04 mdsnwi-router-01 329: Pool: Processor  Free: 1038084  Cause: Memory fragmentation
> Apr 25 07:16:04 mdsnwi-router-01 330: Alternate Pool: None  Free: 0  Cause: No Alternate pool
> Apr 25 07:16:04 mdsnwi-router-01 331:
> Apr 25 07:16:04 mdsnwi-router-01 332: -Process= "IP RIB Update", ipl= 0, pid= 73
> Apr 25 07:16:04 mdsnwi-router-01 333: -Traceback= 4047D90C 4047F9F0 40478850 415E72A0 415E74A4 402DB9FC 407974D8 4076EFE0 40471AFC 40471AE0
> Apr 25 07:19:17 mdsnwi-router-01 334: Apr 25 07:19:16: %LINK-3-UPDOWN: Interface Hssi12/0/0, changed state to up
> Apr 25 07:19:17 mdsnwi-router-01 335: Apr 25 07:19:17: %LINEPROTO-5-UPDOWN: Line protocol on Interface Hssi12/0/0, changed state to up
> Apr 25 07:19:20 mdsnwi-router-01 336: Apr 25 07:19:19: %LINK-3-UPDOWN: Interface Hssi12/0/0, changed state to down
> Apr 25 07:19:20 mdsnwi-router-01 337: Apr 25 07:19:20: %LINEPROTO-5-UPDOWN: Line protocol on Interface Hssi12/0/0, changed state to down
> Apr 25 07:20:00 mdsnwi-router-01 338: Apr 25 07:19:59: %LINK-3-UPDOWN: Interface Hssi12/0/0, changed state to up
> Apr 25 07:20:00 mdsnwi-router-01 339: Apr 25 07:20:00: %LINEPROTO-5-UPDOWN: Line protocol on Interface Hssi12/0/0, changed state to up
> Apr 25 07:20:04 mdsnwi-router-01 340: Apr 25 07:20:03: %LINK-3-UPDOWN: Interface Hssi12/0/0, changed state to down
> Apr 25 07:20:04 mdsnwi-router-01 341: Apr 25 07:20:04: %LINEPROTO-5-UPDOWN: Line protocol on Interface Hssi12/0/0, changed state to down
> Apr 25 07:20:12 mdsnwi-router-01 342: Apr 25 07:20:11: %LINK-3-UPDOWN: Interface Hssi12/0/0, changed state to up
> Apr 25 07:20:12 mdsnwi-router-01 343: Apr 25 07:20:12: %LINEPROTO-5-UPDOWN: Line protocol on Interface Hssi12/0/0, changed state to up
> Apr 25 07:20:20 mdsnwi-router-01 344: Apr 25 07:20:19: %BGP-5-ADJCHANGE: neighbor 144.228.52.181 Up
> 
> Are we running out of BGP table space?  Hit a bad spot of memory?
> 
> Did anyone else lose a connection with Sprint Tuesday morning?
> It was not announced maintenance.
> 
> Jeff C.
> -- 
> Jeff Chan
> mailto:cisco-nsp at jeffchan.com
> http://www.supranet.net/
> 
> _______________________________________________
> 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/

-- 
"The map is not the territory; the word is not the thing defined."