snmpd ipv6 supports multiple community strings

[qiluo-msft]

- What I did

- How I did it

- How to verify it
Modify the /etc/sonic/snmp.yml

snmp_rocommunity: public
snmp_location: public
snmp_rocommunities: ['public', 'private1']

Then query inside snmp docker container:

root@sonic:/# snmpwalk -v2c -c private1 ::1 iso.3.6.1.2.1.4.24.4.1.1
iso.3.6.1.2.1.4.24.4.1.1.0.0.0.0.0.0.0.0.0.10.0.0.57 = IpAddress: 0.0.0.0
iso.3.6.1.2.1.4.24.4.1.1.0.0.0.0.0.0.0.0.0.10.0.0.59 = IpAddress: 0.0.0.0
iso.3.6.1.2.1.4.24.4.1.1.0.0.0.0.0.0.0.0.0.10.0.0.61 = IpAddress: 0.0.0.0
iso.3.6.1.2.1.4.24.4.1.1.0.0.0.0.0.0.0.0.0.10.0.0.63 = IpAddress: 0.0.0.0
iso.3.6.1.2.1.4.24.4.1.1.0.0.0.0.0.0.0.0.0.10.0.0.65 = IpAddress: 0.0.0.0
iso.3.6.1.2.1.4.24.4.1.1.0.0.0.0.0.0.0.0.0.10.0.0.67 = IpAddress: 0.0.0.0
iso.3.6.1.2.1.4.24.4.1.1.0.0.0.0.0.0.0.0.0.10.0.0.69 = IpAddress: 0.0.0.0
iso.3.6.1.2.1.4.24.4.1.1.0.0.0.0.0.0.0.0.0.10.0.0.71 = IpAddress: 0.0.0.0
iso.3.6.1.2.1.4.24.4.1.1.10.1.0.32.255.255.255.255.0.0.0.0.0 = IpAddress: 10.1.0.32
root@sonic:/# snmpwalk -v2c -c public ::1 iso.3.6.1.2.1.4.24.4.1.1
iso.3.6.1.2.1.4.24.4.1.1.0.0.0.0.0.0.0.0.0.10.0.0.57 = IpAddress: 0.0.0.0
iso.3.6.1.2.1.4.24.4.1.1.0.0.0.0.0.0.0.0.0.10.0.0.59 = IpAddress: 0.0.0.0
iso.3.6.1.2.1.4.24.4.1.1.0.0.0.0.0.0.0.0.0.10.0.0.61 = IpAddress: 0.0.0.0
iso.3.6.1.2.1.4.24.4.1.1.0.0.0.0.0.0.0.0.0.10.0.0.63 = IpAddress: 0.0.0.0
iso.3.6.1.2.1.4.24.4.1.1.0.0.0.0.0.0.0.0.0.10.0.0.65 = IpAddress: 0.0.0.0
iso.3.6.1.2.1.4.24.4.1.1.0.0.0.0.0.0.0.0.0.10.0.0.67 = IpAddress: 0.0.0.0
iso.3.6.1.2.1.4.24.4.1.1.0.0.0.0.0.0.0.0.0.10.0.0.69 = IpAddress: 0.0.0.0
iso.3.6.1.2.1.4.24.4.1.1.0.0.0.0.0.0.0.0.0.10.0.0.71 = IpAddress: 0.0.0.0
iso.3.6.1.2.1.4.24.4.1.1.10.1.0.32.255.255.255.255.0.0.0.0.0 = IpAddress: 10.1.0.32

- Description for the changelog

- A picture of a cute animal (not mandatory but encouraged)

[jleveque]

Per your example,

snmp_rocommunity: public
snmp_location: public
snmp_rocommunities: ['public', 'private1']

You have defined both snmp_rocommunity and snmp_rocommunities. Does one take precedence over the other?

Would it make more sense to deprecate snmp_rocommunity altogether and replace with snmp_rocommunities, where if there is only one community string, the value will be a list with only one value? #Resolved

[qiluo-msft]

snmp_rocommunities takes precedence over snmp_rocommunity.

snmp_rocommunity will be deprecated in future. Currently the design here is to help automation system migrate from old config to new config. Automation could blindly provide both single string and a list of strings, and it will work on both old image and new image, while old image only respect the single string and new image only respect the list.

---

In reply to: 535721416 [](ancestors = 535721416)