Is there any way to pass SNMPv3 information via placeholders for custom EXE's or scripts? I've found placeholders for SNMPv2 information, such as community, as well as Windows username/password and linux username/password, but I can't seem to find any information that would allow for SNMPv3 user, auth method, auth password, priv method and priv password. I'd prefer not to have to pass them as plaintext in the sensor or hardcode them in the script.
Article Comments
Thank you for that response! When you say system variable, are you meaning defining these as environment variables at the Windows level? And do you know if there might be any intent to add snmpv3 placeholders in the future?
Dec, 2017 - Permalink
Hello,
thank you for your reply.
| Thank you for that response! When you say system variable, are you meaning defining these as environment variables at the Windows level? |
Yes, that's what I meant. It's one way to have it accessible by all scripts when they run on the host. The other option would be to include/import a file that contains this data when the script runs/starts.
| And do you know if there might be any intent to add snmpv3 placeholders in the future? |
Currently there are no plans to do so, as SNMP V3 is not really widely use by our customers at the present time. I wouldn't rule it out completely since it makes a lot of sense, but there are currently no concrete plans to do it.
Best Regards,
Luciano Lingnau [Paessler Support]
Dec, 2017 - Permalink
Hello there, thank you very much for your contact.
The documentation is correct, at this time placeholders for SNMP v3 are not implemented/available yet. The reason for this is very little feedback/requests for this at this time.
Consider using a system variable on the probe system, hard-coding the credentials in the script or re-entering these details in the Parameters Field (e.g. -auth sha -user user -password mypassword -encryption aes )
For any further questions or issues, we're glad to help.
Dec, 2017 - Permalink