LMS 3.2 -DFM alerts

Unanswered Question
Mar 10th, 2010
User Badges:


I'd like to know what can cause this alarm? as when i check on the switch, i found that the vlan is administratively shut down. I'd like to know on how can i fix this in order not to happen in future. Your feedback will be hihgly appreciated.

mdz-te-5-1#sh int vlan20
Vlan20 is administratively down, line protocol is down

mdz-te-5-1#sh ip int br

Vlan20         YES NVRAM  administratively down down

EVENT ID                = 0004EP1
ALERT ID                = 000028Z
TIME                    = Wed 10-Mar-2010 01:40:48 CAT
STATUS                  = Active
SEVERITY                = Critical
MANAGED OBJECT          = mdz-te-5-1

MANAGED OBJECT TYPE     = Switches and Hubs
EVENT DESCRIPTION       = Unresponsive::Component= [mdz-te-5-1];ComponentClass=IP;ComponentEventCode=1098;InterfaceName=IF-mdz-te-5-1/20 [Vl20] [] [uplink_Core2];InterfaceAdminStatus=DOWN;Address=;IPStatus=TIMEDOUT;InterfaceTyp

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Joe Clarke Wed, 03/10/2010 - 10:38
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

This looks like CSCtb87449.  There is a patch on Cisco.com to fix this, but it is getting mixed results.

lucky.sibanyoni Wed, 03/10/2010 - 23:36
User Badges:

HI Joe

Thanks for your feedback.

What do you mean you saying its getting mixed results? does the patch solve the problem? or it does resolve in some instances but not in all instances?

I'd like to download the fix, but first i need to know if it wont make the situation worse.

Thanks a lot for your feedback.



Joe Clarke Thu, 03/11/2010 - 09:35
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

I have heard one user report that patch doesn't work.  That is, the problem remains the same after applying it.  Development is still investigating.  The patch does not make anything worse, though.


This Discussion