Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Core switch WS-C6509-E reboot issue

Hi,

 

Core switch model WS-C6509-E was got rebooted and then came UP after more than 20 Minutes.

 

Also attaching here show tech-support for this switch captured,

suggests us your finding,

 

Regards,

Akil

4 REPLIES
New Member

Core switch WS-C6509-E reboot issue

HI,

The 6500 suffered a software crash. Please collect the output of the following two crash files and open a SR with TAC for further debugging.

------------------ show bootflash: all ------------------

4    E8DCA73B  179968   34   456656 Jul 29 2011 15:36:42 +05:30 crashinfo_ios-base-20110729-100634

------------------ show sup-bootdisk: all ------------------

27      239996 Jul 29 2011 16:21:48 +05:30 crashinfo_ios-base-20110729-105145

Cisco Employee

Core switch WS-C6509-E reboot issue

There is nothing suspicious in the log.

As requested above please paste the crashinfo results.

Sweta

New Member

Re: Core switch WS-C6509-E reboot issue

Hi,

I have attached crashinfo file for this software crash in this switch.

Regds,

Akil

Cisco Employee

Core switch WS-C6509-E reboot issue

Hi Akil,

Logs show following error messages:

Jul 29 15:34:04 IST: %CPU_MONITOR-SP-6-NOT_HEARD: CPU_MONITOR messages have not been heard for 31 seconds [5/1]

Jul 29 15:34:34 IST: %CPU_MONITOR-SP-6-NOT_HEARD: CPU_MONITOR messages have not been heard for 61 seconds [5/1]

Jul 29 15:34:52 IST: %C6K_PROCMIB-SP-3-IPC_TRANSMIT_FAIL: Failed to send process statistics update : error code = timeout  : ios-base : (PID=12311, TID=4) : -Traceback=(s72033-ipservices_wan-7-dso-b.so+0x3CCE60) ([32:0]+0x3CCED0) ([32:0]+0x3CD1A8) ([32:0]+0x3CD4C8) ([32:0]+0x28A6C8) ([32:0]+0x28A6A0)

Jul 29 15:35:04 IST: %CPU_MONITOR-SP-6-NOT_HEARD: CPU_MONITOR messages have not been heard for 91 seconds [5/1]

Jul 29 15:35:34 IST: %CPU_MONITOR-SP-6-NOT_HEARD: CPU_MONITOR messages have not been heard for 121 seconds [5/1]

Jul 29 15:36:04 IST: %CPU_MONITOR-SP-6-NOT_HEARD: CPU_MONITOR messages have not been heard for 151 seconds [5/1]

Jul 29 15:36:34 IST: %CPU_MONITOR-SP-3-TIMED_OUT: CPU_MONITOR messages have failed, resetting system [5/1]


Explanation:
-------------
%CPU_MONITOR-6-NOT_HEARD: CPU_MONITOR messages have not been heard for %d seconds [%d/%d] CPU monitor messages have not been detected for a significant amount of time. [dec] is the number of seconds. A timeout is likely to occur soon, which will reset the system. This error can be caused by a badly seated module or by high traffic in the EOBC channel. Recommended Action: Verify that all modules are seated properly in the chassis. Pull out the module mentioned in the message and inspect the backplane and module for bent pins or hardware damage. If the message persists after reseating all the modules, a hardware problem may exist, such as a defective module or chassis.

Cheers

Sweta

Please rate the answer if you found the content useful.

1653
Views
6
Helpful
4
Replies