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!

[bharath10]

Hi Folks,

i am trying to discover NetBotz Devices(OOTB not supported) with custom probe-sensor.

i have created classifier, oid and added mib but i am struggling with retrieving serial number.

what will be the oid path if i want to add it into probe- with walk. and i tried to get from internet but no luck.

Example- (

iso.org.dod.internet.private.enterprises.fireeye.feCommon.feSystem.feSystemInfo.feSerialNumber';

)

can anyone help here.

thanks in advance.

[ggarcia1]

I've been adding the Serial OID to the SNMP - Identity Info probe, then updating the SnmpIdentityInfoParser script include.

The probe is pretty straight forward, but the script include has two things;

a pile of variablized OIDs

and a chain of serial number checks

Depending on your instance version, your script may have a different layout, but both sections still exist.

In the the pile of var OIDs, enter something like this: (copied three so you can see its pretty much the same each time)

var oid_blueCoat = 'iso.org.dod.internet.private.enterprises.blueCoat.';
var oid_gigamon = 'iso.org.dod.internet.private.enterprises.gigamonSnmp.';
var oid_infoblox = 'iso.org.dod.internet.private.enterprises.infoblox.';

Then in the chain of serial number checks, add an appropriate check. This requires knowing the rest of the path to the serial number location, so have the OID from the probe ready. In my instance version, this series of serial checks ends at an APC check, so I just started my checks right after that.

//2-12-19 check for BlueCoat Serial Number...
this.addSerial('blueCoatProxy', snmp.getOIDText('iso.org.dod.internet.private.enterprises.blueCoat.blueCoatMgmt.bluecoatSGProxyMIB.sgProxyConfig.sgProxySerialNumber'));

//2-13-19 check for Gigamon Serial Number...
this.addSerial('gigamon', snmp.getOIDText(oid_gigamon + 'gigamonSystem.serialNumber'));

//2-20-19 check for InfoBlox Serial Number...
this.addSerial('infoblox', snmp.getOIDText(oid_infoblox + 'ibSNMP.ibProduct.ibOne.ibPlatformOne.ibPlatformModule.ibSerialNumber'));

We're preparing to move to the New York version, which uses patterns more heavily, so we'll see what sorts of adjustments we'll have to make there to keep life consistent.

Let me know if you need a hand.