Reference Guide

Brocade Fabric OS Command Reference 1023
53-1004112-02
snmpConfig
The SNMPv3 configuration supports sending inform requests as an alternative to trap requests. Traps are
unreliable because the receiver does not send any acknowledgment when it receives a trap. The sender cannot
determine if the trap was received. However, an SNMP manager that receives an inform request acknowledges the
message with an SNMP response protocol data unit (PDU). If the manager does not receive an inform request, it
does not send a response. If the sender never receives a response, the inform request can be sent again. For this
reason, informs are more likely to reach their intended destination.
All values successfully changed by this command take effect immediately and are persistent across power cycles
and reboots.
SNMPv1 Configuration Parameters
The agent supports six communities and their associated trap recipients and trap recipient severity levels. The first
three communities are for read-write (rw) access and the last three are for read-only (ro) access. The default value
for the trap recipient of each community is 0.0.0.0. The length of the community string should be in the range of 2
to 16 characters. The default values for the community strings include the following:
• Community 1: Secret Code
• Community 2: OrigEquipMfr
• Community 3: private
• Community 4: public
• Community 5: common
• Community 6: FibreChannel
For an SNMP management station to receive a trap generated by the agent, the administrator must configure a
trap recipient to correspond to the IP address of the management station. In addition, the trap recipient must be
able to pass the access control list (ACL) check as described in the Access Control category.
SNMPv3 Configuration Parameters
Two user roles, snmpadmin and snmpuser are supported. The snmpadmin role provides read-write access and
the snmpuser role provides read-only access. Entries are added to the USM table corresponding to each role. A
total of three entries for snmpadmin and snmpuser respectively are supported. Separate default passwords are
provided for creation of authKey and privKey for each entry. The default set of passwords is published and the
default algorithm (MD5/SHA) is used to create the initial set of authentication keys. You can change these
passwords using this option. You can select the authentication protocol MD5/SHA or no authentication for each
entry.
When new passwords are entered for any user entry, a new authKey and privKey are generated. The new
passwords must be updated on the client (e.g., MIB browser) as well. AuthKey and privKey can also be updated
with the delta key mechanism provided by the SNMPv3 protocol.
The system prompts for password confirmation if a protocol other than NoAuth/NoPriv is selected. Protocol
passwords must be between 1 and 20 characters.
In order for an SNMP management station to receive SNMPv3 traps generated by the agent, the administrator
must configure a trap recipient value to correspond to the IP address of the management station. In addition, the
trap recipient must pass the ACL check as described in the Access Control section. The trap recipient must be
associated with one of the six users of SNMPv3 and trap severity level. The factory default value for the SNMPv3
trap recipient of each user is 0.0.0.0.