VeloCloud VCE OIDs

[RRolling]

Hello Community,

I'm looking for knowledge on discovering our VeloCloud VCE router correctly. I have a SNMPv3 creational that validates on the IP when testing. Im running a quick discovery on a single IP at the moment but it returns "Active, couldn't classify, now finished".

Ive added a lot of different OIDs from the payload to try and help with classifying but it still ends the same way. What am I doing wrong?

[doug_schulze]

Does the sysoid come back in the snmp classify return? We need that to match to continue classification

[RRolling]

Ive tried creating OIDs in ServiceNow based on a few of these with no luck:

This XML file does not appear to have any style information associated with it. The document tree is shown below.
<results probe_time="18484" result_code="0">
<result source="10.70.38.1">
<snmp host="10.70.38.1" ip="10.70.38.1" timed_out="false">
<iso oid="1">
<org oid="1.3">
<dod oid="1.3.6">
<internet oid="1.3.6.1">
<mgmt oid="1.3.6.1.2">
<mib-2 oid="1.3.6.1.2.1">
<system oid="1.3.6.1.2.1.1">
<sysName oid="1.3.6.1.2.1.1.5" type="SnmpOctetString">San_Mateo_CA_540</sysName>
<sysDescr oid="1.3.6.1.2.1.1.1" type="SnmpOctetString">VeloCloud EDGE5X0</sysDescr>

[RRolling]

Currently I have this: 

[doug_schulze]

You arent pulling the SysOID back in the payload then there will be nothing to match in the snmp SysOID table, thus no classification.  What you are trying to do is use a OID 'question' (1.3.6.1.2.1.5) of name to match the return, SNMP SysOIDs dont work that way.

1. You can contact the manufacturer and have them help you understand why their systems do not reply to that OID query.

2. Add a different classification criteria in the router classifier or create your own that has something like sysdescr contains VeloCloud.  I show you how here and explain how to properly use the snmpsysOID table.

https://www.servicenow.com/community/itom-articles/create-a-simple-snmp-classifier-the-patterns-edit...