search

fusioninventory / sysobject.ids

Repository to store sysobject.ids file, used for snmp network discovery
GNU General Public License v2.0
13 stars 42 forks source link

Invalid device classification (UniFi as computer) #52

Closed WebGregGit closed 3 years ago

WebGregGit commented 3 years ago

Hello.

APs have been discovered but unfortunately, they were assigned to the computer category, and as a result, I cannot use the inventory task, because it only works for printers and network devices.

Is it possible to correct the classification of Unifi access points?

g-bougard commented 3 years ago

Hi @WebGregGit

I think the problem here is your APs are reporting themselves as linux or bsd appliance. If this is right, this is not possible by updating this sysobjectid.ids file. You can report the output of # snmpget -v2c -c public "your AP IP" 1.3.6.1.2.1.1.2.0 so I can confirm.

Finally if this is the case, the only way to support UniFi AP would be to update LinuxAppliance module. Or you can contact the manufacturer to produce a firmware with a better SNMP standard support, at least providing a private sysobjectid.

WebGregGit commented 3 years ago

snmpget returned: iso.3.6.1.2.1.1.2.0 = OID: iso.3.6.1.4.1.8072.3.2.10

g-bougard commented 3 years ago

Hi @g-bougard That's a confirmation so. This OID makes the agent match this line: sysobject.ids#L6532. You can modify your sysobject.ids to something like:

8072.3.2.10 UniFi   NETWORKING  UniFi AP

But any networking appliance detected with this OID will be identified as UniFi AP and this is wrong. The best approach now would be to ask for a LinuxAppliance update attempt providing a snmp walk. To do so, open another issue but for the agent. We won't guaranty that's possible as we need to find some other OIDs which can tell us there's an UniFi AP behind. Then I'm closing the issue as we can't do more here.