Idea ID 2800055
In a rather mixed environment like ours it's not possible to have all the devices setup with the same SNMPv3 encryption methods. This is mostly due to vendor specific limitations.
- Older devices are fixed to Authentication-Encryption with MD5 and Privacy with DES (example Avocent Terminal Servers)
- Newer devices are sometimes fixed, for example to SHA / DES (example: Cisco Meraki)
- Some devices let you freely mix between different possible encryption (for example: Palo Firewalls)
Additionally some devices require you to have the same passwords for authentication and privacy while others allow you to have individual strings.
With the option: <option name="ConnectionMethods/CustomDefault">XXXXXX</option>
in the adjustable options it's possible to set the default communication for a newly discovered device,and there it's possible to set one SNMPv3 encription set. But only one possible combination.
Additionally, there is a setting within the NA-Proxy that allows to add a connection method to password rules via "add authentication -connectionmethods" but this only allows a setting for telnet, ssh or console.
My idea would be:
Make it possible so we can add connection-methods to password rules for SNMPv3, for example by enhancing the "connectionmethods" in the proxy or by adding those options to the GUI.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.