Creating a VeloCloud CI from Discovery

[RRolling]

Hello Community,

I've been struggling for a while and headed down many paths but still need help with creating a CI of a VeloCloud device that is being discovered by IP with SNMP.

When running Discovery, the IP will respond with the DNS name but is unable to configure a CI. Below is the payload which doesn't include a sysObjectID oid. 

<results probe_time="18099" result_code="0">
<result source="XX.XX.XX.XX">
<snmp host="XX.XX.XX.XX" ip="XX.XX.XX.XX" 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">Kansas_City_MO</sysName>
<sysDescr oid="1.3.6.1.2.1.1.1" type="SnmpOctetString">VeloCloud EDGE5X0</sysDescr>
</system>

I've played around with making a Discovery Pattern that fails, I added MID server MIB files, SNMP OID Classifications, and a SNMP Classification which has a classification criteria for sysDescr contains VeloCloud.

I'll be happy to share/post any other information if anyone help me step back and start over so I can create a CI for these devices.

Thanks

[alexandrede]

Ola, bom dia ! voces conseguiram adicionar equipamentos VeloCloud através do Discovery sem o sysObjectID ?

Obrigado

[Shaun Brachmann]

In the SNMP Classify probe if you disable the SNMP field for "mgmt.mib-2.ip.ipForwDatagrams" the VeloCloud will respond slightly better.  That particular OID is deprecated anyway so most devices wont provide an answer but I have found some devices to "go silent" if you ask them about it.

YMMV