Local Overwrite not working in 1.6.0p20.cee but in 2.0.0p1.cee?

DonHansDampf · July 9, 2021, 4:29pm

Hello everyone,

our storage team upgraded from some Fujitsu DX500S3 to the newer model DX500S5. Sadly the in CheckMK included DX500S3 checks don’t work anymore, since the SNMP address of the S5 changed.

I noticed, that (nearly) all SNMP OIDs stayed the same, they only switched from “xxx.150.xxx” to “xxx.153.xxx”. So I created a testing site running 2.0.0p1.cee, copied all the “fjdarye500_*” files to ~/local/share/check_mk/checks/ and changed the OIDs in every check-file. And indeed: Everything get’s discovered as excepted.

Sadly our productive CheckMK instance is still running 1.6.0p20. And it seems like, the local overwrite doesn’t work there. I also copied the files from ~/share/check_mk/checks/ to ~/local/share/check_mk/checks/, changed the OIDs, did a full scan, but nothing get’s discovered.

Am I missing something? I also created another two testing sites, one 1.6.x and one 2.0.0x. Did the same as described above. The v2.0.0x works, the 1.6.x doesn’t.

Would be great, if somebody has a solution for me.

Thank you very much!

Cheers

andreas-doehler · July 9, 2021, 8:30pm

It must also work in 1.6 if done correctly.
You can test on the command line with “cmk --debug -vvI hostname” if you see any error messages.
They can help your to find the root cause of the not found services.

DonHansDampf · July 13, 2021, 6:36am

Hello @andreas-doehler ,

thank you very much for the input. Indeed something in the underlaying libraries changed, and the I simply had a wrong import in my changed plugins. Your command helped a lot.

Sadly I run in another error now:

Edit: Seems like some Versions of DX60 and DX200 use the old DX500 SNMP OIDs… So this is not a CMK problem. Gonna try to define new DX500S5 Plugins instead of overwriting DX500S3 completely…

The fjdarye500 plugin works now with DX500S5. But also our DX60 (other Fujitsu Storage Systems) try to use our ‘custom DX500 plugin’, and reports 'missing agent section fjdarye500.

As far as I understand these SNMP plugins, the ‘snmp_scan_function’ is used to detect the SNMP device and to decide which plugin to use.

So I simply changed the line from:

'snmp_scan_function': lambda oid: oid(".1.3.6.1.2.1.1.2.0") == ".1.3.6.1.4.1.211.1.21.1.150",

to

'snmp_scan_function': lambda oid: oid(".1.3.6.1.2.1.1.2.0") == ".1.3.6.1.4.1.211.1.21.1.153",

Why does the DX60 try to use this plugin. The DX60 plugin uses:

'snmp_scan_function': lambda oid: oid(".1.3.6.1.2.1.1.2.0") == ".1.3.6.1.4.1.211.1.21.1.60",

So the device doesn’t even respond with ‘.1.3.6.1.4.1.211.1.21.1.153’. Why does CMK try to use it then?

OMD[testing]:~/local/share/check_mk/checks$ cmk --debug -vv dmz-rz1-dx60
[cpu_tracking] Start with phase 'busy'
Check_MK version 1.6.0p20
Try aquire lock on /omd/sites/vnp/tmp/check_mk/counters/dmz-rz1-dx60
Got lock on /omd/sites/vnp/tmp/check_mk/counters/dmz-rz1-dx60
Releasing lock on /omd/sites/vnp/tmp/check_mk/counters/dmz-rz1-dx60
Released lock on /omd/sites/vnp/tmp/check_mk/counters/dmz-rz1-dx60
Loading autochecks from /omd/sites/vnp/var/check_mk/autochecks/dmz-rz1-dx60.mk
+ FETCHING DATA
[cpu_tracking] Push phase 'snmp' (Stack: ['busy'])
 [snmp] No persisted sections loaded
 [snmp] Not using cache (Don't try it)
 [snmp] Execute data source
 [snmp] fjdarye500_ca_ports: Fetching data
Executing BULKWALK of ".1.3.6.1.4.1.211.1.21.1.153.5.5.2.1.1" on dmz-rz1-dx60
Executing SNMP GET of .1.3.6.1.4.1.211.1.21.1.153.5.5.2.1.1 on dmz-rz1-dx60
=> [None] NOSUCHOBJECT
Executing BULKWALK of ".1.3.6.1.4.1.211.1.21.1.153.5.5.2.1.2" on dmz-rz1-dx60
Executing SNMP GET of .1.3.6.1.4.1.211.1.21.1.153.5.5.2.1.2 on dmz-rz1-dx60
=> [None] NOSUCHOBJECT
Executing BULKWALK of ".1.3.6.1.4.1.211.1.21.1.153.5.5.2.1.3" on dmz-rz1-dx60
Executing SNMP GET of .1.3.6.1.4.1.211.1.21.1.153.5.5.2.1.3 on dmz-rz1-dx60
=> [None] NOSUCHOBJECT
Executing BULKWALK of ".1.3.6.1.4.1.211.1.21.1.153.5.5.2.1.4" on dmz-rz1-dx60
Executing SNMP GET of .1.3.6.1.4.1.211.1.21.1.153.5.5.2.1.4 on dmz-rz1-dx60
=> [None] NOSUCHOBJECT
Executing BULKWALK of ".1.3.6.1.4.1.211.1.21.1.153.5.5.2.1.5" on dmz-rz1-dx60
Executing SNMP GET of .1.3.6.1.4.1.211.1.21.1.153.5.5.2.1.5 on dmz-rz1-dx60
=> [None] NOSUCHOBJECT
Executing BULKWALK of ".1.3.6.1.4.1.211.1.21.1.153.5.5.2.1.6" on dmz-rz1-dx60
Executing SNMP GET of .1.3.6.1.4.1.211.1.21.1.153.5.5.2.1.6 on dmz-rz1-dx60
=> [None] NOSUCHOBJECT
 [snmp] fjdarye500_cadaps: Fetching data
Executing BULKWALK of ".1.3.6.1.4.1.211.1.21.1.153.2.3.2.1.1" on dmz-rz1-dx60
Executing SNMP GET of .1.3.6.1.4.1.211.1.21.1.153.2.3.2.1.1 on dmz-rz1-dx60
=> [None] NOSUCHOBJECT
Executing BULKWALK of ".1.3.6.1.4.1.211.1.21.1.153.2.3.2.1.3" on dmz-rz1-dx60
Executing SNMP GET of .1.3.6.1.4.1.211.1.21.1.153.2.3.2.1.3 on dmz-rz1-dx60
=> [None] NOSUCHOBJECT
 [snmp] fjdarye500_cmods: Fetching data
Executing BULKWALK of ".1.3.6.1.4.1.211.1.21.1.153.2.1.2.1.1" on dmz-rz1-dx60
Executing SNMP GET of .1.3.6.1.4.1.211.1.21.1.153.2.1.2.1.1 on dmz-rz1-dx60
=> [None] NOSUCHOBJECT
Executing BULKWALK of ".1.3.6.1.4.1.211.1.21.1.153.2.1.2.1.3" on dmz-rz1-dx60
Executing SNMP GET of .1.3.6.1.4.1.211.1.21.1.153.2.1.2.1.3 on dmz-rz1-dx60
=> [None] NOSUCHOBJECT
 [snmp] fjdarye500_cmods_flash: Fetching data
Executing BULKWALK of ".1.3.6.1.4.1.211.1.21.1.153.2.4.2.1.1" on dmz-rz1-dx60
Executing SNMP GET of .1.3.6.1.4.1.211.1.21.1.153.2.4.2.1.1 on dmz-rz1-dx60
=> [None] NOSUCHOBJECT
Executing BULKWALK of ".1.3.6.1.4.1.211.1.21.1.153.2.4.2.1.3" on dmz-rz1-dx60
Executing SNMP GET of .1.3.6.1.4.1.211.1.21.1.153.2.4.2.1.3 on dmz-rz1-dx60
=> [None] NOSUCHOBJECT
 [snmp] fjdarye500_cmods_mem: Fetching data
Executing BULKWALK of ".1.3.6.1.4.1.211.1.21.1.153.2.4.2.1.1" on dmz-rz1-dx60
Executing SNMP GET of .1.3.6.1.4.1.211.1.21.1.153.2.4.2.1.1 on dmz-rz1-dx60
=> [None] NOSUCHOBJECT
Executing BULKWALK of ".1.3.6.1.4.1.211.1.21.1.153.2.4.2.1.3" on dmz-rz1-dx60
Executing SNMP GET of .1.3.6.1.4.1.211.1.21.1.153.2.4.2.1.3 on dmz-rz1-dx60
=> [None] NOSUCHOBJECT
 [snmp] fjdarye500_conencs: Fetching data
Executing BULKWALK of ".1.3.6.1.4.1.211.1.21.1.153.2.10.2.1.1" on dmz-rz1-dx60
Executing SNMP GET of .1.3.6.1.4.1.211.1.21.1.153.2.10.2.1.1 on dmz-rz1-dx60
=> [None] NOSUCHOBJECT
Executing BULKWALK of ".1.3.6.1.4.1.211.1.21.1.153.2.10.2.1.3" on dmz-rz1-dx60
Executing SNMP GET of .1.3.6.1.4.1.211.1.21.1.153.2.10.2.1.3 on dmz-rz1-dx60
=> [None] NOSUCHOBJECT
 [snmp] fjdarye500_disks: Fetching data
Executing BULKWALK of ".1.3.6.1.4.1.211.1.21.1.153.2.19.2.1.1" on dmz-rz1-dx60
Executing SNMP GET of .1.3.6.1.4.1.211.1.21.1.153.2.19.2.1.1 on dmz-rz1-dx60
=> [None] NOSUCHOBJECT
Executing BULKWALK of ".1.3.6.1.4.1.211.1.21.1.153.2.19.2.1.3" on dmz-rz1-dx60
Executing SNMP GET of .1.3.6.1.4.1.211.1.21.1.153.2.19.2.1.3 on dmz-rz1-dx60
=> [None] NOSUCHOBJECT
 [snmp] fjdarye500_disks.summary: Skip fetching data (section already fetched)
 [snmp] fjdarye500_inletthmls: Fetching data
Executing BULKWALK of ".1.3.6.1.4.1.211.1.21.1.153.2.10.2.1.1" on dmz-rz1-dx60
Executing SNMP GET of .1.3.6.1.4.1.211.1.21.1.153.2.10.2.1.1 on dmz-rz1-dx60
=> [None] NOSUCHOBJECT
Executing BULKWALK of ".1.3.6.1.4.1.211.1.21.1.153.2.10.2.1.3" on dmz-rz1-dx60
Executing SNMP GET of .1.3.6.1.4.1.211.1.21.1.153.2.10.2.1.3 on dmz-rz1-dx60
...

Thank you very much!

Best regards

andreas-doehler · July 13, 2021, 7:41am

What happens for this device with a “cmk --debug -vvII dmz-rz1-dx60”?

This is the best way to minimize impact on existing plugins/checks.

DonHansDampf · July 13, 2021, 9:17am

Yeah, in the end it worked with ‘new’ Plugins. I simply changed all function names in the plugins AND the OIDs. Thank you for your input. While developing SNMP Plugins I am often stumbling in the dark.

Best regards,
Marcel

system · July 13, 2022, 9:17am

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact an admin if you think this should be re-opened.