This is a question I have that I can’t find the answer.
I would like to know if the SNMP community string has any variable attached for it - for example , if I were to run legacy checks that is based from SNMP, I am able to associate %HOSTADDRESS%, but I am not able to put in the community string that is unique for each server.
That is the most major roadblock in implementing check_mk that I have right now - we have a lot of custom scripts that are based on SNMP.
Could anyone help me please?
Thanks in advance.
···
Best Regards,
Ahmad Siddiq b. Mohd AdnanSenior System Engineer, Xchanging Malaysia Sdn Bhd
International Award for Young People, Gold Award
LPIC-3, Novell CLA, Novell DCTech, CCENT, Microsoft Certified Professional, MCTS Windows Server 2008
Mobile: +60 17 377-5007| Facebook: https://www.facebook.com/my.sidz
We utilize the Nagios/Icinga $USERX$ variables in the resource.cfg file for this.
It would however be really nice if the SNMP string configured in the WATO Host properties could be written out as a custom host variable so you could have different SNMP strings for any number of devices without having to have multiple USER variables and then have to try and keep track of them all.
···
On 14/11/2014 9:16 p.m., Ahmad Siddiq wrote:
Hi all,
This is a question I have that I can't find the answer.
I would like to know if the SNMP community string has any variable attached for it - for example , if I were to run legacy checks that is based from SNMP, I am able to associate %HOSTADDRESS%, but I am not able to put in the community string that is unique for each server.
That is the most major roadblock in implementing check_mk that I have right now - we have a lot of custom scripts that are based on SNMP.
I don’t think there’s any easy to configure SNMP community strings in legacy Nagios, unless you use puppet or chef.
What we did was to switch to Check_MK SNMP checks. The builtin checks cover most of the hardware we monitor, there’s a lot on the Internet, and it’s not that difficult to convert. Adapting Check_MK SNMP makes it so much easier to manage and debug SNMP checks. You can define custom SNMP strings, timeouts etc via check_mk configurations: https://mathias-kettner.de/checkmk_configvars.html#H1:SNMP.
Other than switching, I don’t know any good way to achieve what you wanted to do.
This is a question I have that I can’t find the answer.
I would like to know if the SNMP community string has any variable attached for it - for example , if I were to run legacy checks that is based from SNMP, I am able to associate %HOSTADDRESS%, but I am not able to put in the community string that is unique for each server.
That is the most major roadblock in implementing check_mk that I have right now - we have a lot of custom scripts that are based on SNMP.
Could anyone help me please?
On 14/11/2014 9:16 p.m., Ahmad Siddiq wrote:
We utilize the Nagios/Icinga $USERX$ variables in the resource.cfg file for this.
It would however be really nice if the SNMP string configured in the WATO Host properties could be written out as a custom host variable so you could have different SNMP strings for any number of devices without having to have multiple USER variables and then have to try and keep track of them all.
There are some checks that are not available in the Nagios plugin repository - such as: Cisco special checks (BMA checks, Current checks, etc) or even other checks that are available in SNMP but not picked up by the plugins that we have or Nagios have. These checks needs to be addressed by checking the unique OIDs manually - easiest way is to use check_snmp legacy plugin.
I understand that perhaps writing check_mk’s snmp plugins would be easier in the long term, since the checks can be done passively in one shot - but it will be implemented in the second stage.
It would be easier to have the community string as a variable for us to implement snmp custom checks. Looking forward for the developers to look into it.
Thanks in advance. If you guys happen to come to Kuala Lumpur, I will treat you for lunch.
This is a question I have that I can’t find the answer.
I would like to know if the SNMP community string has any variable attached for it - for example , if I were to run legacy checks that is based from SNMP, I am able to associate %HOSTADDRESS%, but I am not able to put in the community string that is unique for each server.
That is the most major roadblock in implementing check_mk that I have right now - we have a lot of custom scripts that are based on SNMP.
Could anyone help me please?
On 14/11/2014 9:16 p.m., Ahmad Siddiq wrote:
We utilize the Nagios/Icinga $USERX$ variables in the resource.cfg file for this.
It would however be really nice if the SNMP string configured in the WATO Host properties could be written out as a custom host variable so you could have different SNMP strings for any number of devices without having to have multiple USER variables and then have to try and keep track of them all.