Discovery issue with classification, sysObjectID is not returned
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-02-2014 11:29 AM
Discovery issue with classification, sysObjectID is not returned with SNMP Classify OIDs.
I have an issue where I am not able to classify a network Switch (Message: Active, couldn't classify). Usually when I have classification issue with the network related device, I add the "sysObjectID" (Oid) to the "Discovery Defination-> SNMP OID" which generally resolves the issue.
However, here I am not getting the "sysObjectID" in the OIDs returned from the switch? I loaded the mibs as well (Mid Server ->SNMP MIBS) to no avail.
The device I am trying to discover is HP 12518AC (HP 12500 Switch; oid = 1.3.6.1.4.1.25506.11.1.112)
Just wondering anyone else has experienced this issue and how you resolved it.
Thanks, Faisal
- Labels:
-
Service Mapping
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-11-2014 11:32 AM
Yes, simply unable to discover the devices.
I'm having two issues. One is: 'SSH Authentication or connection failure'
The other issue is: MID WPVServiceNow discovering range null
Those are the final entries for two different CIs.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-11-2014 11:43 AM
After a bit more digging I learned these 2 devices are 'Alive, not classified'

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-17-2014 02:45 AM
Alive, not classified means that its refusing connection.
I would check these:
1) MID server is added in the ACL
2) Community string is configured on the device.
If the above are in place, you should run snmpwalk from MID to the device to verify indeed that these settings are good. Then run the discovery!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-11-2014 12:56 PM
Mark,
Do you by chance know the devices you are trying to discover are network devices, Unix based server or something else?
If it is a Unix based Server, I am thinking you dont have the correct credentials.
If it is storage device, it will not discover with SSH unless there is some customization you have done. Storage uses CIM model for discovery.
Regarding the error: MID WPVServiceNow discovering range null
I don't believe that is an issue. I am thinking you are likely doing "quick discovery" and seeing that message. The message is confusing:-)
Hope the information helps. You can also try to post ECC message payload and maybe we can further assist you. Just make sure you dont have password such as community string.
Faisal
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-17-2014 05:23 AM