[c-nsp] 12.2(33)SXI revisited

[Phil Mayers]

On Tue, Feb 10, 2009 at 12:40:19PM +0000, A.L.M.Buxey at lboro.ac.uk wrote:
>hi,
>
>okay - after fruitful time on the test/devel router and then
>a prolonged period on 2 select routers, we're now SXI across
>the board.... which has finally thrown up an error (of sorts!)
>hurrah! :-)
>
>having exhausted my usual supply of cisco and google (and c-nsp ;-) )
>searches I thought I'd throw this one to the list before
>visiting my TAC friends for the 3rd time this week.
>
>note: so far we only obsrve this error on systems with 2 Sup720's in
>SSO redundancy mode
>
>this is whats being logged:
>
>Feb 10 12:26:38: SP: Critical error processing oif ltl index change event (0100.5b00.073c, XXX, 0xB8B)
>Feb 10 12:30:32: SP: Critical error processing rpf ltl index change event (0100.5b1f.fefd, XXX, 0xBAB)
>Feb 10 12:30:32: SP: Critical error processing oif ltl index change event (0100.5b1f.fefd, XXX, 0xBAB)
>Feb 10 12:30:48: SP: Critical error processing rpf ltl index change event (0100.5b1f.fefa, XXX, 0xBB3)
>Feb 10 12:30:48: SP: Critical error processing oif ltl index change event (0100.5b1f.fefa, XXX, 0xBB3)
>Feb 10 12:31:54: SP: Critical error processing rpf ltl index change event (0100.5b07.0076, XXX, 0xBBF)

I haven't seen that one, but interestingly, I'm getting messages related 
to multicast on SXI too:

%MLSM-6-LC_SCP_FAILURE: NMP encountered internal communication failure 
for (s,g,vlan),  flow will be software switched

We're getting them *very* infrequently, but we are getting them. TAC 
tell me this only happens after an SSO or OIR, however the last SSO/OIR 
was days (in some cases a week or more) before the most recent messages.

We've also got some messages related to ISSU which were triggered by a 
bad chassis, so my perception is the logging verbosity is a bit higher 
in SXI generally.