CWLMS 3.X Error log

Unanswered Question
May 19th, 2009
User Badges:

Dear pros,


I am getting the below log from core switch. Any work around ?

EVENT ID = 00012KT

ALERT ID = 00007VF

TIME = Tue 10-May-2009 13:04:52 AST

STATUS = Active

SEVERITY = Critical

MANAGED OBJECT = K-CORE-1

MANAGED OBJECT TYPE = Switches and Hubs

EVENT DESCRIPTION = Unresponsive::Component=10.19.13.3 [K-CORE-1];ComponentClass=IP;ComponentEventCode=1098;InterfaceName=IF-K-CORE-1/81 [Vl513] [10.19.13.1, ...] [DHCP-LMS];InterfaceAdminStatus=UP;Address=10.19.13.3;IPStatus=TIMEDOUT;InterfaceType=PROPVIRTUAL;N

CUSTOMER IDENTIFICATION = k

CUSTOMER REVISION = k

ALERT ID = 00007UC

TIME = Tue 10-May-2009 01:06:28 AST

STATUS = Active

SEVERITY = Critical

MANAGED OBJECT = K-CORE-1

MANAGED OBJECT TYPE = Switches and Hubs

EVENT DESCRIPTION = PORT-K-CORE-1/2.24 [Gi2/24]:HighUtilization;

CUSTOMER IDENTIFICATION = k

CUSTOMER REVISION = k

EVENT ID = 000118I

ALERT ID = 00007HU

TIME = Thu 07-May-2009 22:36:40 AST

STATUS = Active

SEVERITY = Critical

MANAGED OBJECT = K-CORE-1

MANAGED OBJECT TYPE = Switches and Hubs

EVENT DESCRIPTION = Unresponsive::Component=10.19.13.3 [K-CORE-1];ComponentClass=IP;ComponentEventCode=1098;InterfaceName=IF-K-CORE-1/81 [Vl513] [10.19.13.1, ...] [DHCP-LMS];InterfaceAdminStatus=UP;Address=10.19.13.3;IPStatus=TIMEDOUT;InterfaceType=PROPVIRTUAL;N

CUSTOMER IDENTIFICATION = k

CUSTOMER REVISION = k

Thx

swami

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Joe Clarke Tue, 05/19/2009 - 20:24
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

This error means that DFM cannot ping the IP address 10.19.13.3 on this device. If you want DFM to be able to monitor the reachability of this IP address, then fix the network to allow DFM to ping the device.


If you do not want to DFM to ping this interface, then go to DFM > Device Management > Device Details, and launch the Detailed Device View for this device. Go to the IP node in the left-hand tree, and set the managed state to false for this interface. Submit your change, then go to DFM > Configuration > Polling and Thresholds > Apply Changes to apply the change.

arumugasamy Sun, 05/24/2009 - 01:17
User Badges:

Mr.Clarke,


We are able to reach this IP from LMS Server or anywhere in our network.

How to check if DFM is able to ping this IP?

How to prevent all the error messages?

Thx

swami

Joe Clarke Sun, 05/24/2009 - 10:45
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

I already told you how you can stop DFM from trying to ping this address. To check whether DFM can actually reach it, it should be as simple as running:


ping 10.19.13.3


From the DFM server. However, you could also start a sniffer trace on the DFM server, filtering on all ICMP traffic to this IP address. Leave it running for 8 minutes. After that, look at the captured packets, and see if there was any error (or any replies) with the pings DFM sent out.

Actions

This Discussion