Brocade TurboIron 24X Series Configuration Guide User Manual
Page 199
Brocade TurboIron 24X Series Configuration Guide
165
53-100305301
Establishing SNMP community strings
NOTE
If you want the software to assume that the value you enter is the clear-text form, and to encrypt
display of that form, do not enter 0 or 1. Instead, omit the encryption option and allow the software
to use the default behavior.
NOTE
If you specify encryption option 1, the software assumes that you are entering the encrypted form
of the community string. In this case, the software decrypts the community string you enter before
using the value for authentication. If you accidentally enter option 1 followed by the clear-text
version of the community string, authentication will fail because the value used by the software will
not match the value you intended to use.
The command in the example above adds the read-write SNMP community string “private”. When
you save the new community string to the startup-config file (using the write memory command),
the software adds the following command to the file.
snmp-server community 1
To add a non-encrypted community string, you must explicitly specify that you do not want the
software to encrypt the string. Here is an example.
TurboIron(config)#snmp-server community 0 private rw
TurboIron(config)#write memory
The command in this example adds the string “private” in the clear, which means the string is
displayed in the clear. When you save the new community string to the startup-config file, the
software adds the following command to the file.
snmp-server community 0 private rw
The view
this community string. Enter up to 32 alphanumeric characters. If no view is specified, access to
the full MIB is granted. The view that you want must exist before you can associate it to a
community string. Here is an example of how to use the view parameter in the community string
command.
TurboIron(config)#snmp-s community myread ro view sysview
The command in this example associates the view “sysview” to the community string named
“myread”. The community string has read-only access to “sysview”. For information on how to
create views, refer to
“SNMP v3 Configuration examples”
The
which ACL group will be used to filter incoming SNMP packets. You can enter either the ACL name
or its ID. Here are some examples.
TurboIron(config)#snmp-s community myread ro view sysview 2
TurboIron(config)#snmp-s community myread ro view sysview myACL
The command in the first example indicates that ACL group 2 will filter incoming SNMP packets;
whereas, the command in the second example uses the ACL group called “myACL” to filter incoming
packets.Refer to
“Using ACLs to restrict SNMP access”
on page 66 for more information.
NOTE
To make configuration changes, including changes involving SNMP community strings, you must
first configure a read-write community string using the CLI. Alternatively, you must configure another
authentication method and log on to the CLI using a valid password for that method.