Unanswered Question
Mar 5th, 2009
User Badges:

This error occurs 8000 times about every two hours. We know it's an IP phone that gets stuck in discovery mode so we simply reboot the phone or remove the phone. Also, according to Cisco online, these errors waste cpu cycles.

Our 4500 series has rebooted 2 times the last month without any indication or warning.

My question is, can this error eat up so much cpu time that it would cause a 4500 to reboot?

Another question is, "does this error eat up available memory?"

Thanks in advance.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Leo Laohoo Fri, 03/06/2009 - 16:19
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    The Hall of Fame designation is a lifetime achievement award based on significant overall achievements in the community. 

  • Cisco Designated VIP,

    2017 LAN, Wireless

Depends if the IOS you are currently using, yes. If it's an IP Phone and only one phone, why not get it off the network are replace it with another unit?

Do "sh proce cpu history" and look at the graph.

jm7197afi Fri, 03/06/2009 - 16:35
User Badges:

Thank you for the reply leolaohoo.

We are on:

Cisco IOS Software, Catalyst 4000 L3 Switch Software (cat4000-I9K91S-M), Version 12.2(25)EWA7, RELEASE SOFTWARE (fc1)

We remove the faulty phones when this error occurs. We have over 200 IP phones.

What we want to determine is if the errors caused by faulty phones is a contributing causal factor or is the root cause.


This Discussion