You are not logged in.

Announcement

 Téléchargez la dernière version stable de GLPI      -     Et vous, que pouvez vous faire pour le projet GLPI ? :  Contribuer
 Download last stable version of GLPI                      -     What can you do for GLPI ? :  Contribute

#1 2024-01-24 13:53:51

vanmaelst
Member
Registered: 2024-01-24
Posts: 1

Working with a broken sysobject ID

I'm not sure if this is possible, but I'd like to import a device via netinventory that has an erroneous SNMP configuration. Retrieving the sysobject id through SNMPwalk gives the following:

snmpget -v 2c -c public 192.168.41.196 sysObjectID.0
SNMPv2-MIB::sysObjectID.0 = Wrong Type (should be OBJECT IDENTIFIER): STRING: "1.3.6.1.4.1.27928.101"

(A correct sysObjectID looks like:
snmpwalk -v 2c -c zabbix_v2c -On 192.168.55.82 sysObjectID.0
.1.3.6.1.2.1.1.2.0 = OID: .1.3.6.1.4.1.2011.2.23.889)

Though I have added .27828.101 to the sysobject.ids file, running a netdiscovery task still doesn't recognize the sysObjectID:

[debug] #1, invalid sysobjectID 1.3.6.1.4.1.27928.101: no manufacturer ID

Is there some way to manually say what the sysobjectID is when running a netdiscovery task, or is it possible to somehow overwrite the device's SNMP configuration to fix the OID?

Offline

Board footer

Powered by FluxBB