TWSD-1597 : AVX: allows adding "public" as an SNMPv3 user
Review Request #1432 — Created March 10, 2026 and submitted — Latest diff uploaded
| Information | |
|---|---|
| bsrivalli | |
| AVX2 | |
| rel_avx_2_7_5 | |
| TWSD-1597 | |
| Reviewers | |
| ngurunathan, stevenku, wli | |
The system previously allowed the username "public" to be configured as an SNMPv3 user. The term public is a well-known default community string used in SNMPv1 and SNMPv2c, and allowing it as an SNMPv3 username may lead to security concerns and confusion between SNMP versions.
A validation check has been added to prevent the use of the reserved name "public" when creating an SNMPv3 user. If a user attempts to configure public as the SNMPv3 username, the system now rejects the request and displays an appropriate error message.
This change ensures that reserved community names cannot be used as SNMPv3 usernames and improves the security and correctness of SNMPv3 configuration.
AN(config)#snmp v3user public "admin@123" authNopriv
Error: User 'public' is not allowed for SNMPv3.
Please enter valid user name.AN(config)#snmp v3user test "admin@123" authNopriv
AN(config)#sh run snmp
snmp configuration
snmp community "public"
snmp contact ""
snmp location ""
no snmp enable traps
snmp v3user "test" "admin@123" authNopriv
snmp ipcontrol off
snmp off
