Error

Answered Question
Mar 22nd, 2007

hI GUYS,

I got an error in my 6500 and my MSFC had a switchover .

The error is given below from log.

What does this error means ? and is this anywhere related to MSFC switchover.

ERROR:

35. 3/12/2007,10:33:27: titan_intr_hdlr: Main Intr 0x0; Module 0x0, value 0x0; fatal intrs since last read 0, Last DBus Src Index 0x0

36. 3/12/2007,10:33:41: CentauriInterrupt:L3 parity Error 56177 1103aa 8000026b

37. 3/12/2007,10:33:41: titan_intr_hdlr:Last titan interrupt occurred at 00:00:00.0

38. 3/12/2007,10:33:41: titan_intr_hdlr: Main Intr 0x0; Module 0x0, value 0x0; fatal intrs since last read 0, Last DBus Src Index 0x0

pls guide.

Rgrds

Rajeev.S

I have this problem too.
0 votes
Correct Answer by ankbhasi about 9 years 8 months ago

Hi Rajeev,

Here is an explaination

1) Centauri is a L3 Forwarding ASIC (Cat 6k)

2) Titan is used for MCAST replication (Cat 6k)

1. titan_intr_hdlr: Main Intr 0x0; Module 0x0, value 0x0; fatal intrs since last read 0

What it means is that the system is recovering after an error and only a message is being displayed. It is not possible to read any register when this happens as the system recovers automatically.

2. CentauriInterrupt:L3 parity Error

The above L3 table parity errors may show up on some SUP1 cards. This is a non-fatal error (packets would still get forwarded in sw) so is not a cause of alarm unless it is seen on a large percentage of packets. The

problem is seen in 5.5.x, 6.x and 7.x

Here are the bug ID's regarding the messages.

http://www.cisco.com/cgi-bin/bugtool/onebug.pl?bugid=CSCdy41174

The recommended workaround will be to reseat the supervisor engines if possible after arranging the downtime or you can try upgrading to the release mentioned in bugs which has this bug resolved.

HTH

Ankur

*Pls rate all helpfull post

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
ankbhasi Thu, 03/22/2007 - 04:30

Hi Rajeev,

Can you post the output of "sh mod"

Regards,

Ankur

rajivrajan1 Thu, 03/22/2007 - 05:07

Mod Slot Ports Module-Type Model Sub Status

--- ---- ----- ------------------------- ------------------- --- --------

1 1 2 1000BaseX Supervisor WS-X6K-SUP1A-2GE yes ok

15 1 1 Multilayer Switch Feature WS-F6K-MSFC2 no standby

2 2 2 1000BaseX Supervisor WS-X6K-SUP1A-2GE yes standby

16 2 1 Multilayer Switch Feature WS-F6K-MSFC2 no ok

3 3 48 10/100BaseTX Ethernet WS-X6148-RJ-45 no ok

4 4 48 10/100BaseTX Ethernet WS-X6148-RJ-45 no ok

ankbhasi Thu, 03/22/2007 - 05:22

Hi Rajiv,

Sorry I missed this question in my first post, can you please confirm which CATOS you are running on your box?

Regards,

Ankur

rajivrajan1 Thu, 03/22/2007 - 05:25

WS-C6509 Software, Version NmpSW: 7.5(1)

Copyright (c) 1995-2002 by Cisco Systems

NMP S/W compiled on Dec 30 2002, 22:56:53

Correct Answer
ankbhasi Thu, 03/22/2007 - 05:59

Hi Rajeev,

Here is an explaination

1) Centauri is a L3 Forwarding ASIC (Cat 6k)

2) Titan is used for MCAST replication (Cat 6k)

1. titan_intr_hdlr: Main Intr 0x0; Module 0x0, value 0x0; fatal intrs since last read 0

What it means is that the system is recovering after an error and only a message is being displayed. It is not possible to read any register when this happens as the system recovers automatically.

2. CentauriInterrupt:L3 parity Error

The above L3 table parity errors may show up on some SUP1 cards. This is a non-fatal error (packets would still get forwarded in sw) so is not a cause of alarm unless it is seen on a large percentage of packets. The

problem is seen in 5.5.x, 6.x and 7.x

Here are the bug ID's regarding the messages.

http://www.cisco.com/cgi-bin/bugtool/onebug.pl?bugid=CSCdy41174

The recommended workaround will be to reseat the supervisor engines if possible after arranging the downtime or you can try upgrading to the release mentioned in bugs which has this bug resolved.

HTH

Ankur

*Pls rate all helpfull post

rajivrajan1 Thu, 03/22/2007 - 22:46

Dear Ankur,

Thanx a ton .. it was very useful.Please let me know if there is a possiblity of sup switchover if this error is more.

ankbhasi Thu, 03/22/2007 - 23:15

Hi Rajiv,

Till the time this error is coming in huge percentage I do not think this could cause supervisor switchover. Even if we see this erorr packets still get routed in sw via msfc.

But huge percentage of same error is a concern.

HTH

Ankur

Actions

This Discussion