[c-nsp] ssa_get_reg messages from 6500/sup720-3b + 6748sfp/dfc3b

Phil Mayers p.mayers at imperial.ac.uk
Tue Aug 8 08:55:33 EDT 2006


All,

After some maintenance this morning, a few final minor cleanup were made 
on one of our core routers. Immediately after that and for the next few 
hours until the CPU spike finally affected the Sup and monitoring saw 
it, we got *lots* of the following messages in the log buffer:

12:50:19.107 FW[Mod 08]: ssa_get_reg: ssa=1: reg=0x77 rc=0x80
12:50:19.107 FW[Mod 08]: ssa_get_reg: ssa=1: reg=0x7C rc=0x80
12:50:19.107 FW[Mod 08]: ssa_get_reg: ssa=1: reg=0x78 rc=0x80
12:50:19.111 FW[Mod 08]: ssa_get_reg: ssa=1: reg=0x7E rc=0x80
12:50:19.111 FW[Mod 08]: ssa_get_reg: ssa=1: reg=0x7A rc=0x80
12:50:19.111 FW[Mod 08]: ssa_get_reg: ssa=1: reg=0x27 rc=0x80
12:50:19.111 FW[Mod 08]: ssa_get_reg: ssa=1: reg=0x2C rc=0x80
12:50:19.111 FW[Mod 08]: ssa_get_reg: ssa=1: reg=0x28 rc=0x80
12:50:19.111 FW[Mod 08]: ssa_get_reg: ssa=1: reg=0x2E rc=0x80
12:50:19.115 FW[Mod 08]: ssa_get_reg: ssa=1: reg=0x2A rc=0x80

...many many thousands a second.

I finally got worried, moved the non-resilient links to another linecard 
and did a "hw-module module 8 reset", which seemed to clear things up.

I'm going to open a TAC case but at the same time, if anyone has seen 
this and knows the cause (the cleanup changes were completely unrelated 
and it is hard to see how they could have caused it) I'd love to hear.

Software is native IOS, 12.2(18)SXF2 advanced IP services.


More information about the cisco-nsp mailing list