Hello,
Today if we want to set snmp V2 community we can set it in template or host directly but we don’t have a “store” of the different snmp community and for SNMP V3 it’s much harder because you need to know the command line to set it via the EXTRAOPTION.
We have the “store” in the discovery part, can we have it everywhere ? =)
Thank by advance
Yohan
+5Hi,
native snmp v3 support for all plugins without using EXTRAOPTIONS would be fine.
We’ve modified several check commands by our own for a good handling of snmp v3 devices.
+3Hi,
native snmp v3 support for all plugins without using EXTRAOPTIONS would be fine.
We’ve modified several check commands by our own for a good handling of snmp v3 devices.
Same battle =)
+18+5A modified check command does the trick (here for generic snmp check):
$CENTREONPLUGINS$/centreon_generic_snmp.pl --plugin=apps::protocols::snmp::plugin --mode=numeric-value --hostname=$HOSTADDRESS$ --snmp-version 3 --snmp-username='$_HOSTSNMPV3USERNAME$' --authpassphrase='$_HOSTSNMPV3AUTHPASSPHRASE$' --authprotocol='$_HOSTSNMPV3AUTHPROTOCOL$' --privpassphrase='$_HOSTSNMPV3PRIVPASSPHRASE$' --privprotocol='$_HOSTSNMPV3PRIVPROTOCOL$' $_HOSTSNMPEXTRAOPTIONS$ --oid='$_SERVICEOID$' --format='$_SERVICEFORMAT$' --warning=$_SERVICEWARNING$ --critical=$_SERVICECRITICAL$ $_SERVICEEXTRAOPTIONS$
We linked this command linked into the service template and now we can set all parameters via macros.
I agree, as SNMPV3 is more and more used around, having a “simpler” interface also makes a bit more sense than asking users to redo everything through command arguments.
Of course this can be standardized in a host or service template, but i would appreciate a UI.
+14The template basically will end up on the UI so it is a nice start from
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
