WS-C3560-8PC Discovery Issues

Answered Question
Feb 14th, 2008
User Badges:

Hi all,


This one has me scratching my head. We have a number of these devices on our network all configured exactly the same (well apart from the obvious necessary changes). However Cisco LMS does not discover some of the devices whilst it easily discovers others.


The IOS versions are all the same and the SNMP details are all the same. When I enable SNMP debugging on one of the devices that is not found, the log file shows the entries below.


Feb 14 15:47:11: SNMP: Packet received via UDP from xx.xx.xx.14 on Vlan2

Feb 14 15:47:11: SNMP: Get request, reqid 13722, errstat 0, erridx 0

system.2.0 = NULL TYPE/VALUE

system.5.0 = NULL TYPE/VALUE

sysUpTime.0 = NULL TYPE/VALUE

Feb 14 15:47:11: SNMP: Response, reqid 13722, errstat 2, erridx 1

system.2.0 = NULL TYPE/VALUE

system.5.0 = NULL TYPE/VALUE

sysUpTime.0 = NULL TYPE/VALUE

Feb 14 15:47:11: SNMP: Packet sent via UDP to xx.xx.xx.14

Feb 14 15:47:11: SNMP: Packet received via UDP from xx.xx.xx.14 on Vlan2

Feb 14 15:47:11: SNMP: Get request, reqid 13725, errstat 0, erridx 0

system.5.0 = NULL TYPE/VALUE

sysUpTime.0 = NULL TYPE/VALUE

Feb 14 15:47:11: SNMP: Response, reqid 13725, errstat 2, erridx 1

system.5.0 = NULL TYPE/VALUE

sysUpTime.0 = NULL TYPE/VALUE

Feb 14 15:47:11: SNMP: Packet sent via UDP to xx.xx.xx.14


Can anyone give me a clue what is wrong here?

Correct Answer by Joe Clarke about 9 years 2 months ago

I think I see what's going on here. LMS is polling this device with the community string "public". Since public is only defined to be a notify string, every request will get a NO_SUCH_NAME response.


Therefore, you need to adjust your community strings in Discovery SNMP Settings so that the proper string is used to poll this device.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Joe Clarke Thu, 02/14/2008 - 11:01
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

The errstat 2 indicates that the device is reporting that sysObjectID is not a valid object. So either SNMP is completely broken on this device, or there is a view applied to the community string being used with excludes sysObjectID. A full show run and show ver would help narrow down this problem.

Correct Answer
Joe Clarke Fri, 02/15/2008 - 09:28
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

I think I see what's going on here. LMS is polling this device with the community string "public". Since public is only defined to be a notify string, every request will get a NO_SUCH_NAME response.


Therefore, you need to adjust your community strings in Discovery SNMP Settings so that the proper string is used to poll this device.

Actions

This Discussion