CPU_MONITOR-6-NOT_HEARD

From: Georg Pauwen (pauwen@hotmail.com)
Date: Wed Feb 12 2003 - 09:35:52 GMT-3

• Next message: Doug Calton: "Re: Problem getting local mobility to work"
• Previous message: Doug Calton: "Re: Problem getting local mobility to work"
• Next in thread: Chuck Church: "Re: CPU_MONITOR-6-NOT_HEARD"
• Maybe reply: Chuck Church: "Re: CPU_MONITOR-6-NOT_HEARD"
• Maybe reply: Georg Pauwen: "Re: CPU_MONITOR-6-NOT_HEARD"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

Hello colleagues,

I have a Supervisor II for a 6509 which keeps generating the above error
message (CPU_MONITOR-6-NOT_HEARD). After 150 seconds the system reboots into
ROMMON. The Cisco website says:

Error Message

%CPU_MONITOR-6-NOT_HEARD
: CPU_MONITOR messages have not been heard for [dec] seconds [[dec]/[dec]]
Explanation CPU monitor messages have not been heard for a significant
amount of time. A timeout is likely to occur soon which will reset the
system.

Recommended Action No action is required.

If the recommended action is no action, how can I get the Supervisor to boot
properly and not to reset itself constantly ? Has anybody ever seen this
before ?

Regards,

Georg

• Next message: Doug Calton: "Re: Problem getting local mobility to work"
• Previous message: Doug Calton: "Re: Problem getting local mobility to work"
• Next in thread: Chuck Church: "Re: CPU_MONITOR-6-NOT_HEARD"
• Maybe reply: Chuck Church: "Re: CPU_MONITOR-6-NOT_HEARD"
• Maybe reply: Georg Pauwen: "Re: CPU_MONITOR-6-NOT_HEARD"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

This archive was generated by hypermail 2.1.4 : Sat Mar 01 2003 - 11:06:19 GMT-3