One should simply remove the SNMP v1/v2 strings from the config, thereafter the controller will only answer configured SNMP v3
queries.
While one can configure v1, v2c, and v3 specific trap/informs, there is no method to distinguish between SNMP v1 and v2, and thereby disable v1 without disabling v2, since one is disabling the community string relevant to both v1 and v2c
Lab Example, the controller is running ArubaOS 6.1.3.2, and has SNMP v1, v2, and v3 configured, and working. We will remove SNMP v1 and v2 communities and trap servers, leaving only V3 active.
Simply remove the "snmp-server community" line, and if desired, the v1 and v2c relevant trap/inform lines
Show startup-config
snmp-server community public
snmp-server user "netadmin_inform" auth-prot sha 02ed21af0879f7xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx124d007fb6 priv-prot aes 74bb638ef6079ffac4bea2d66c66aa84b2ddd904da7029d3
snmp-server user "netadmin_ro" auth-prot sha c879b2dd6cfa6ed3018xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx3da0 priv-prot aes 9688c46d682c8c8d5xxxxxxxxxx1ef93652123ff60327c18
snmp-server enable trap
snmp-server host 192.168.17.14 version 1 public udp-port 162
snmp-server host 192.168.17.30 version 2c public udp-port 162
snmp-server inform queue-length 150
snmp-server host 192.168.17.30 version 3 netadmin_inform inform engine-id 80001f8880f21224107f0df4 udp-port 162
conf t
no snmp-server community public
no snmp-server host 192.168.17.14 version 1 public
no snmp-server host 192.168.17.30 version 2c public
show run
snmp-server user "netadmin_inform" auth-prot sha ****** priv-prot aes ******
snmp-server user "netadmin_ro" auth-prot sha ****** priv-prot aes ******
snmp-server enable trap
snmp-server inform queue-length 150
snmp-server host 192.168.17.30 version 3 netadmin_inform inform engine-id 80001f8880f21224107f0df4 udp-port 162
This information is covered in the ArubaOS Command Line Reference Guide version 6.1, Page 1240.
Hope this is helpful.