CiscoWorks LMS 2.6 / DFM 2.0.10 Not Showing CPU Util

Answered Question

Hi,


The DFM 2.0.10 Device Details for C6509 switch shows CPU as managed, however shows utilization as unavailable. We want to set up alerts for CPU spike and it is not working as data is not being captured.


Any idea or pointers in the right direction is highly appreciated.


Thank you in advance.

Correct Answer by Joe Clarke about 7 years 7 months ago

Something is wrong with your SNMPv3 config. Reconfigure SNMPv3 with something like:


snmp-server group cwpriv v3 auth read v1default notify *tv.FFFFFFFF.FFFFFFFF.FFFFFFFF.0000000F


snmp-server user nwadmin cwpriv v3 auth ALGO PASSWORD


Where ALGO is one of md5 or sha and PASSWORD is the SNMPv3 authNoPriv password. That should allow you to poll this device.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Joe Clarke Fri, 10/23/2009 - 13:48
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

Start a sniffer trace filtering on udp/161 traffic to this switch, and let it run for at least eight minutes. That should capture two polling cycles. Post the capture file.

Joe Clarke Fri, 10/23/2009 - 18:24
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

There was no filter applied. What is the IP address of the switch in question?

Joe Clarke Sat, 10/24/2009 - 07:17
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

It appears you have misconfigured this device as all of the SNMP responses are coming back as noSuchObject. Post the show run from this switch.

Joe Clarke Sat, 10/24/2009 - 15:56
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

Remove this line:


snmp-server view v1default ciscoFlashMIB excluded


Then rediscover the device in DFM, and see if the CPU data is found after four minutes.

Thank you.


I removed the line and did a rediscovery for the CORE devices in DFM, but it is still showing the CPU Util as unavailable.


If I remember correct, I had similar issue for ASA with DFM 2.0.10 last year and TAC had a patch from DEV group applied to oid2type_Cisco.conf file, which I was asked to replace the one in \objects\smarts\conf\discovery\oid2type_Cisco.conf


Thanks again for looking into this.


Joe Clarke Mon, 10/26/2009 - 09:43
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

Post the new sniffer trace.

Joe Clarke Mon, 10/26/2009 - 14:37
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

The device is still replying with noSuchObject. Post the output of "show snmp user", "show snmp group", and "show snmp view" from this switch.

Correct Answer
Joe Clarke Mon, 10/26/2009 - 19:47
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

Something is wrong with your SNMPv3 config. Reconfigure SNMPv3 with something like:


snmp-server group cwpriv v3 auth read v1default notify *tv.FFFFFFFF.FFFFFFFF.FFFFFFFF.0000000F


snmp-server user nwadmin cwpriv v3 auth ALGO PASSWORD


Where ALGO is one of md5 or sha and PASSWORD is the SNMPv3 authNoPriv password. That should allow you to poll this device.

Actions

This Discussion