netdisco / snmp-info

Other
35 stars 31 forks source link

Issue with FortiAP SNMP information #472

Open drpixel972 opened 1 year ago

drpixel972 commented 1 year ago

The fortinet fortiAP are not discovered properly in netdisco.

Expected Behavior

The fortigate fortiAP should be discovered with the correct information found in another OID.

Current Behavior

Well the software does it job, the device is not "compliant". However it may be easier to implement a workaround than asking the vendor to be compliant.

Possible Solution

When the sysobject is detected with the string FORTINET-FORTIAP-MIB, then the relevant value S/N, version ... should be picked from the vendor OID.

Context

I'm trying to discover the FortiAP in netdisco. The device discovery is partial due to the device.

image

It would be nice for this device to get the proper information from the vendor MIB.

SNMPv2-MIB::sysDescr.0 = STRING: REDACTED SNMPv2-MIB::sysObjectID.0 = OID: FORTINET-FORTIAP-MIB::fap221e DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (2552465809) 295 days, 10:10:58.09 SNMPv2-MIB::sysContact.0 = STRING: REDACTED SNMPv2-MIB::sysName.0 = STRING: REDACTED SNMPv2-MIB::sysLocation.0 = STRING: N/A

In this device, the relevant information are in the vendor specific mib (FORTINET-FORTIAP-MIB)

here is a snmpwalk of the OID : .1.3.6.1.4.1.12356.120.1 FORTINET-FORTIAP-MIB::fapVersion.0 = STRING: FP221E-v7.0-build0033 FORTINET-FORTIAP-MIB::fapSerialNum.0 = STRING: REDACTED FORTINET-FORTIAP-MIB::fapHostName.0 = STRING: REDACTED FORTINET-FORTIAP-MIB::fapRegionCode.0 = STRING: E FORTINET-FORTIAP-MIB::fapBaseMacAddr.0 = STRING: aa:bb:cc:dd:ee:ff (redacted) FORTINET-FORTIAP-MIB::fapBiosVer.0 = STRING: 04000002 FORTINET-FORTIAP-MIB::fapBiosDataVer.0 = INTEGER: 3 FORTINET-FORTIAP-MIB::fapSysPartNum.0 = STRING: 20830-03

Best Regards,