[c-nsp] TestSPRPInbandPing...?

Phil Mayers p.mayers at imperial.ac.uk
Wed Feb 18 11:23:53 EST 2009


Gert Doering wrote:
> Hi,
> 
> should I be worried...??
> 
> Feb 18 16:44:38: %DIAG-SP-3-TEST_FAIL: Module 5: TestSPRPInbandPing{ID=2} has failed. Error code = 0xC3
> Feb 18 16:45:15: %DIAG-SP-3-TEST_FAIL: Module 5: TestSPRPInbandPing{ID=2} has failed. Error code = 0xC3
> Feb 18 16:45:51: %DIAG-SP-3-TEST_FAIL: Module 5: TestSPRPInbandPing{ID=2} has failed. Error code = 0xC3
> Feb 18 16:46:28: %DIAG-SP-3-TEST_FAIL: Module 5: TestSPRPInbandPing{ID=2} has failed. Error code = 0xC3
> Feb 18 16:47:43: %CONST_DIAG-SP-6-HM_TEST_RECOVERED: Module 5 TestSPRPInbandPing recovered after 9 consecutive failure(s)
> 
> (this is on a 6506, Sup720-10G, SXH3a code)
> 
> Besides the syslog messages, everything seems well-behaved...
> 
> gert
> 

Hmm.

My rule of thumb has been that a diag "fail" is not definitive, but a 
"pass" is. SPRPInband is one of the periodic diags (run, IIRC, every 15 
seconds) so it's actually passed a lot of times since you've seen the error.

Was anything else going on at the time? Maybe the SP or RP were busy and 
thus dropped the pings? What does "remote command switch show log | inc 
Feb 18 16:" show?

However, at least on SXI, 10 consecutive failures is the max permitted, 
and in some redundancy modes that can trigger a SUP failover!


More information about the cisco-nsp mailing list