Filter
Top Products
S
IMPLE
N
ETWORK
M
ANAGEMENT
P
ROTOCOL
3-55
Command Usage
• If you specify an SNMP Version 3 host, then the “Trap Manager
Community String” is interpreted as an SNMP user name. If you use V3
authentication or encryption options (authNoPriv or authPriv), the user
name must first be defined in the SNMPv3 Users page (page 3-60).
Otherwise, the authentication password and/or privacy password will
not exist, and the switch will not authorize SNMP access for the host.
However, if you specify a V3 host with the no authentication (noAuth)
option, an SNMP user account will be automatically generated, and the
switch will authorize SNMP access for the host.
• Notifications are issued by the switch as trap messages by default. The
recipient of a trap message does not send a response to the switch. Traps
are therefore not as reliable as inform messages, which include a request
for acknowledgement of receipt. Informs can be used to ensure that
critical information is received by the host. However, note that informs
consume more system resources because they must be kept in memory
until a response is received. Informs also add to network traffic. You
should consider these effects when deciding whether to issue
notifications as traps or informs.
To send an inform to a SNMPv2c host, complete these steps:
1. Enable the SNMP agent (page 3-53).
2. Enable trap informs as described in the following pages.
3. Create a view with the required notification messages (page 3-72).
4. Create a group that includes the required notify view (page 3-66).
To send an inform to a SNMPv3 host, complete these steps:
1. Enable the SNMP agent (page 3-53).
2. Enable trap informs as described in the following pages.
3. Create a view with the required notification messages (page 3-72).
4. Create a group that includes the required notify view (page 3-66).
5. Specify a remote engine ID where the user resides (page 3-59).
6. Then configure a remote user (page 3-63).