Displaying the snmp community strings, Using the user-based security mode – Brocade Virtual ADX Administration Guide (Supporting ADX v03.1.00) User Manual
Page 126

114
Brocade Virtual ADX Administration Guide
53-1003249-01
Using the user-based security mode
4
The string variable specifies the community string name. The string can be up to 32 characters
long.
The ro | rw parameter specifies whether the string is read-only (ro) or read-write (rw).
The view viewstring parameter is optional. It allows you to associate a view to the members of 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:
Virtual ADX(config)#snmp-server 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”.
Displaying the SNMP community strings
To display the community strings in the CLI, first use the enable-password-display command and
then use the show snmp server command. This will display both the read-only and read-write
community strings in the clear.
To display the configured community strings, enter the following command at any CLI level:
NOTE
If display of the strings is encrypted, the strings are not displayed. Encryption is enabled by default.
Using the user-based security mode
SNMP version 3 (RFC 2570 through 2575) introduces a User-Based Security model (RFC 2574) for
authentication and privacy services.
SNMP version 1 and version 2 use community strings to authenticate SNMP access to
management processes. This method can still be used for authentication. In SNMP version 3, the
User-Based Security model of SNMP can be used to secure against the following threats:
•
Modification of information
•
Masquerading the identity of an authorized entity
Virtual ADX(config)#show snmp server
Contact:
Location:
Community(ro): .....
Traps
Cold start: Enable
Link up: Enable
Link down: Enable
Authentication: Enable
Locked address violation: Enable
Redundant module state change: Enable
L4 maximum session limit: Enable
L4 TCP SYN limit: Enable
L4 server max connection: Enable
L4 server up: Enable
L4 server down: Enable