It is required to change the strings via a SNMP set command. This may be able to be performed from within your SNMP manager, within a similar tool or from the linux command line as follows. Change the IP address and snmp OID as needed for your device.
# snmpwalk -v2c -c public 192.168.100.100 1.3.6.1.4.1.5454.1.50.1.7
SNMPv2-SMI::enterprises.5454.1.50.1.7.1.0 = STRING: "public"
SNMPv2-SMI::enterprises.5454.1.50.1.7.2.0 = STRING: "private"
# snmpset -v2c -c private 192.168.100.100 1.3.6.1.4.1.5454.1.50.1.7.1.0 s newpublic
SNMPv2-SMI::enterprises.5454.1.50.1.7.1.0 = STRING: "newpublic"
# snmpset -v2c -c private 192.168.100.100 1.3.6.1.4.1.5454.1.50.1.7.2.0 s newprivate
SNMPv2-SMI::enterprises.5454.1.50.1.7.2.0 = STRING: "newprivate"
# snmpwalk -v2c -c public 192.168.100.100 1.3.6.1.4.1.5454.1.50.1.7
SNMPv2-SMI::enterprises.5454.1.50.1.7.1.0 = STRING: "newpublic"
SNMPv2-SMI::enterprises.5454.1.50.1.7.2.0 = STRING: "newprivate"
Even though the community strings report with the new strings, it is required to reboot or restart snmp for the change to become effective as you can see from the last line of the above example when it responds with the old public string.
Note that the read and write community strings should NOT be set the same value as this will result in a conflict between the two strings.
Comments
0 comments
Please sign in to leave a comment.