Struggling with network SNMP discovery - ID on class/serial number

[cyked]

We are starting to get more traction from the infrastructure teams in managing their inventory solely in CMDB and define/follow an inventory process.   On the network side I've had to create some SNMP classifiers and OID entries to properly classify models on discovery.   The issue I'm having is when serial number becomes available during discovery.   I'm able to skate by in a sense, adding and OID for classification when needed, but not familiar enough with SNMP from a discovery standpoint to ensure Serial Number is returned from a device to be used during identification.   In some cases i've resorted to writing a probe and sensor to populate SN on a CI, but this happens after identification.

This means identification happens on CI name and Class Name because serial number is not yet "known".   This is a problem because normally the asset process works by having a CI created on the target table (network gear, IP router, etc) when an asset is received and loaded where we know class, model, and serial number (so the name of the CI is populated as the model ID).   When discovery occurs a match on the table can be found by class and serial number.

What am I missing?   Thanks!

[A Westervelt]

I've added our network appliances' serial identifiers to the SNMP - Identity probe/sensor to handle these scenarios.

As example, we have Infoblox appliances in our enterprise and I had to go out and find the SNMP string 'iso.org.dod.internet.private.enterprises.infoblox.ibSNMP.ibProduct.ibOne.ibPlatformOne.ibPlatformModule.ibSerialNumber' and define it in the probe and sensor to add the serial numbers to the Serial Number table, which in turn solves the Identification phase.

Check out the SnmpIdentityInfoParser script that handles this and note how the addSerial function is being used for other device types.

[cyked]

Are you talking about the SNMP - Identity multiprobe which triggers the SNMP - Identity Info probe?   SNMP - Identity probe has a sensor to process the info, and SNMP - Identity Info contains the SNMP OIDs.   Given the MIB I have I'd add the below to the SNMP - Identity Info probe.    

Also... SNMP - Identity Info is listed as Stage = Explore.   does that matter?

We have some Aruba devices, so should I add this this to SNMP Identity Info:

iso.org.dod.internet.private.enterprises.aruba.arubaEnterpriseMibModules.switch.wlsxEnterpriseMibModules.wlsxSwitchMIB.wlsxSystemXGroup.wlsxSwitchLicenseSerialNumber

this is all that is in the OotB sensor:

//The ID sensor is an implementation of the multi sensor. In the related list "Responds to Probes", the script will be processed first.
new DiscoveryIDSensor({
       //
       // this sensor uses the common script include class "DiscoveryIDSensor"
       //
       type: "SNMP Identity"
});

[A Westervelt]

Since Aruba products are mostly network switches and routers, you should just associate the product OIDs to the existing Standard Network Switch and Router classifiers. The Identity probe will already be sent to Identification stage.

[cyked · Accepted solution]

The OIDs from the device (looking at XML payload after an unsuccessfuly classification discovery) and the one provided by the MIB and the network team I've added to the SNMP classifiers for switch and router and disabled the stand alone one I created.

1.3.6.1.4.1.14823.1.1.32 and   1.3.6.1.4.1.14823.2.2.1.1.1.2.   I think its the second one that is working on the router classifier, but need to test some more and remove unneeded entries.

I updated the script for SnmpIdentityInfoParser as well and it works given serial is populated.   otherwise it will populate serial and will match and ID on subsequent discoveries.

this.addSerial('aruba',snmp.getOIDText('iso.org.dod.internet.private.enterprises.unk_14823.unk_2.unk_2.unk_1.unk_1.unk_1.unk_12'));

Thanks!!