If you use the “–checks” option, you will ignore the scan function.
Ooooh, I wasn’t aware of that. Thanks.
Here’s my scan function (directly copy-pasted from the check_info
structure):
'snmp_scan_function': lambda oid:
oid(".1.3.6.1.2.1.1.2.0").startswith(".1.3.6.1.4.1.674") \
and 'me4' in oid(".1.3.6.1.2.1.1.1").lower(),
and after trying both OIDs shown I can easily see my mistake: the second one is too short, should be .1.3.6.1.2.1.1.1.0
. Changed to
'snmp_scan_function': lambda oid:
oid(".1.3.6.1.2.1.1.2.0").startswith(".1.3.6.1.4.1.674") \
and 'me4' in oid(".1.3.6.1.2.1.1.1.0").lower(),
and a “full scan” in WATO instantly starts to work on both hosts.
Thanks a lot! Solved!
For the record:
.1.3.6.1.2.1.1.2.0 = OID: .1.3.6.1.4.1.674
.1.3.6.1.2.1.1.1.0 = STRING: "DELL EMC ME4024"
For the Powervault ME4 i wrote last week a special agent for the well documented REST Api.
Very nice! I’ll gladly give it a try once it’s out. Where should I look for a release announcement?