CI not populating for Meraki devices

[Peter Farr]

There are a number of questions open on this issue in the forums but no resolutions I can see. Discovery is able to query our Meraki devices via SNMP and s getting a MIB II response. The sysObjectId is from the probe results is:

<sysObjectID oid="1.3.6.1.2.1.1.2" type="SnmpObjectId">.1.3.6.1.4.1.29671.2.109</sysObjectID>

I have added a matching OID entry and the classifier is selecting the correct class, but it will not create a CI. I get:

• Discovery started
• Active, now classifying
• Classified, now identifying
• Discovery completed

... that is it. The probe response seems to contain everything necessary to create a CI. Has anyone made this work? There is a Meraki MIB, which I have loaded just in case, but it is not used by the devices. They only provide data for the following standard MIBs, confirmed by the probe response.

• SNMPv2-MIB .1.3.6.1.2.1.1
• IF-MIB .1.3.6.1.2.1

[AndyB5000]

Came across this post:

https://community.servicenow.com/community?id=community_article&sys_id=f651921edb4b17c45129a851ca96198f

[Peter Farr]

Yup. I saw that one and a number of others. I intend to do that, but right now I am working on the device end. Discovery finds the appliances since they have IP addresses, recognizes them as SNMP then fails to create the CI. I find this peculiar since they are straight MIB 2 with very basic information: only the system and ifTable data. This should be enough to create a CI.

[Peter Farr · Accepted solution]

I have figured it out - I did not have an identify probe associated with the OID. Once SNMP - Identity was added the CI was created.

[smfoister]

Are you getting serial numbers and model information returned by your SNMP probes and populated on your CI's?

I'm noticing some missing entPhysicalDescr is missing from our SNMP input coming from the MX devices.