Closed rainmanatee closed 3 years ago
Correct, the current data model and template does not support v1 and v2c for hosts. The current version
key is placed under users
which is not applicable for v1 and v2c. I think we should move the version field to the host-level so implement something like this:
snmp_server:
hosts:
- host: < host IP address or name >
version: < 1 | 2c | 3 >
vrf: < vrf_name >
users:
- username: < username >
authentication_level: < auth | noauth | priv >
communities:
- < community >
If someone would like to have the same host with multiple versions, they can just make multiple entries in the hosts
list.
So I suggest that we rename this issue to a feature request to support snmp v1 & v2c for snmp_server.hosts
.
@ClausHolbechArista So the suggestion is going to be put in a feature branch for this or follow the dev branch and file a PR with the model and j2 templating change? We can do either just let us know.
Thanks for the guidance thus far. Can you assign this to me?
Issue Type
Summary
In eos_cli_config_gen snmp-settings.j2 does not properly render the snmp-server host command. The community string needs to be included in the command when the version is 1 or 2c.
Component Name
eos_cli_config_gen/templates/eos/snmp-settings.j2
Steps to reproduce
In SNMP Settings, under hosts, there is no facility to add communities, but these are a necessary component to the snmp-server host command if the snmp version is 1 or 2c:
Need to have communities referenced as well, so something like this:
And snmp_settings.j2 to something like: