[Fusioninventory-devel] network discovery: device identification through sysobjectid

Guillaume Rousse guillomovitch at gmail.com
Mon Oct 14 21:43:20 UTC 2013


Hello.

The master+objsysid branch(1) shows how the sysobjectid(2) object value 
can be used to identify easily both the device manufacturer, but also 
the device model, using additional mapping tables stored in the share 
directory (sysobjectid.vendor.ids files).

Our current test database show than we do have a useful match for 198 
samples on 238. The remaining are either unknown models (I couldn't find 
them in vendors MIBs), or useless matches (all HP printers use the same 
1.3.6.1.4.1.11.2.3.9.1 value, which does not allow to discriminate them).

The current implementation relies on this local database first, and 
fallback on previous behaviour (using the mapping defined in the SNMP 
model) if not match is found. This allows more meaningful values, as 
shown here:
https://github.com/fusinv/fusioninventory-agent/commit/95eb46bcbec0e40dd69510d14bfbbbfedfd4b019

I'm planning to merge this branch for 2.4.x, and to also backport it to 
2.3.3.

-- 
Guillaume

[1] https://github.com/fusinv/fusioninventory-agent/tree/master+objsysid
[2] 
http://tools.cisco.com/Support/SNMP/do/BrowseOID.do?local=en&translate=Translate&objectInput=1.3.6.1.2.1.1.2



More information about the Fusioninventory-devel mailing list