Hi,
the Check_MK discovery fails with error [snmp] argument of type 'NoneType' is not iterable
CMK version: CRE 1.5.0p24
OS: CentOS 7.7
Output of cmk --debug -vvI swat (without traceback)
Discovering services on: swat
swat:
+ FETCHING DATA
[snmp] No persisted sections loaded
[snmp] Not using cache (Does not exist)
[snmp] Execute data source
SNMP scan:
Getting OID .1.3.6.1.2.1.1.1.0: Running 'snmpget -v2c -c public -m "" -M "" -On -OQ -Oe -Ot 192.168.1.1 .1.3.6.1.2.1.1.1.0'
SNMP answer: ==> ["S350 Series 8-Port Gigabit Ethernet Smart Managed Pro Switch, Software Version 1.0.0.9, Boot Version 1.0.0.1"]
S350 Series 8-Port Gigabit Ethernet Smart Managed Pro Switch, Software Version 1.0.0.9, Boot Version 1.0.0.1
Getting OID .1.3.6.1.2.1.1.2.0: Running 'snmpget -v2c -c public -m "" -M "" -On -OQ -Oe -Ot 192.168.1.1 .1.3.6.1.2.1.1.2.0'
SNMP answer: ==> [.1.3.6.1.4.1.4526.100.4.48]
.1.3.6.1.4.1.4526.100.4.48
Using cached OID .1.3.6.1.2.1.1.2.0: .1.3.6.1.4.1.4526.100.4.48
Using cached OID .1.3.6.1.2.1.1.1.0: S350 Series 8-Port Gigabit Ethernet Smart Managed Pro Switch, Software Version 1.0.0.9, Boot Version 1.0.0.1
Using cached OID .1.3.6.1.2.1.1.1.0: S350 Series 8-Port Gigabit Ethernet Smart Managed Pro Switch, Software Version 1.0.0.9, Boot Version 1.0.0.1
Using cached OID .1.3.6.1.2.1.1.1.0: S350 Series 8-Port Gigabit Ethernet Smart Managed Pro Switch, Software Version 1.0.0.9, Boot Version 1.0.0.1
Using cached OID .1.3.6.1.2.1.1.1.0: S350 Series 8-Port Gigabit Ethernet Smart Managed Pro Switch, Software Version 1.0.0.9, Boot Version 1.0.0.1
Getting OID .1.3.6.1.2.1.47.1.1.1.1.12.1: Running 'snmpget -v2c -c public -m "" -M "" -On -OQ -Oe -Ot 192.168.1.1 .1.3.6.1.2.1.47.1.1.1.1.12.1'
SNMP answer: ==> [No Such Instance currently exists at this OID]
failed.
[snmp] ERROR: argument of type 'NoneType' is not iterable
In fact, this device does not present the manufacturer name in entPhysicalMfgName.1
Output of snmpbulkget -v2c -c public -m "" -M "" -On -OQ -Oe -Ot 192.168.1.1 .1.3.6.1.2.1.47.1.1.1.1.12:
.1.3.6.1.2.1.47.1.1.1.1.12.64 = ""
.1.3.6.1.2.1.47.1.1.1.1.12.67108992 = "Netgear"
.1.3.6.1.2.1.47.1.1.1.1.12.68157952 = ""
.1.3.6.1.2.1.47.1.1.1.1.12.68420352 = ""
.1.3.6.1.2.1.47.1.1.1.1.12.68424704 = ""
.1.3.6.1.2.1.47.1.1.1.1.12.68424777 = ""
.1.3.6.1.2.1.47.1.1.1.1.12.68424778 = ""
.1.3.6.1.2.1.47.1.1.1.1.12.68424779 = ""
.1.3.6.1.2.1.47.1.1.1.1.12.68424780 = ""
.1.3.6.1.2.1.47.1.1.1.1.12.68424781 = ""
and snmpbulkget -v2c -c public -m "" -M "" -On -OQ -Oe -Ot 192.168.1.1 .1.3.6.1.2.1.47.1.1.1.1.4 lists the containment tree of the physical/logical entities of this device:
.1.3.6.1.2.1.47.1.1.1.1.4.64 = 0
.1.3.6.1.2.1.47.1.1.1.1.4.67108992 = 64
.1.3.6.1.2.1.47.1.1.1.1.4.68157952 = 67108992
.1.3.6.1.2.1.47.1.1.1.1.4.68420352 = 68157952
.1.3.6.1.2.1.47.1.1.1.1.4.68424704 = 68420352
.1.3.6.1.2.1.47.1.1.1.1.4.68424777 = 68424704
.1.3.6.1.2.1.47.1.1.1.1.4.68424778 = 68424704
.1.3.6.1.2.1.47.1.1.1.1.4.68424779 = 68424704
.1.3.6.1.2.1.47.1.1.1.1.4.68424780 = 68424704
.1.3.6.1.2.1.47.1.1.1.1.4.68424781 = 68424704
I read some of the RFCs (RFC 6933 seems to be the most relevant one), but did not find any hint, that entPhysicalMfgName.1 MUST be present.
Did I miss any configuration option? Any link, which pushes me into the right direction, is welcome as well.
Or is Netgear’s implementation of the SNMP agent the one to blame?
Thanks in advance,
Carsten