Filter
Top Products
S
PECIFYING
T
RAP
M
ANAGERS
AND
T
RAP
T
YPES
5-7
To send an inform to a SNMPv3 host, complete these steps:
1. Enable the SNMP agent (page 5-4).
2. Enable trap informs as described in the following pages.
3. Create a view with the required notification messages (page 5-24).
4. Create a group that includes the required notify view (page 5-18).
5. Specify a remote engine ID where the user resides (page 5-11).
6. Then configure a remote user (page 5-15).
Command Attributes
• Trap Manager Capability – This switch supports up to five trap
managers.
• Current – Displays a list of the trap managers currently configured.
• Trap Manager IP Address – IP address of a new management station
to receive notification messages.
• Trap Manager Community String – Specifies a valid community
string for the new trap manager entry. Though you can set this string in
the Trap Managers table, we recommend that you define this string in the
SNMP Configuration page (for Version 1 or 2c clients), or define a
corresponding “User Name” in the SNMPv3 Users page (for Version 3
clients). (Range: 1-32 characters, case sensitive)
• Trap UDP Port – Specifies the UDP port number used by the trap
manager.
• Trap Version – Indicates if the user is running SNMP v1, v2c, or v3.
(Default: v1)
• Trap Security Level – When trap version 3 is selected, you must specify
one of the following security levels. (Default: noAuthNoPriv)
- noAuthNoPriv – There is no authentication or encryption used in
SNMP communications.
- AuthNoPriv – SNMP communications use authentication, but the
data is not encrypted (only available for the SNMPv3 security model).
- AuthPriv – SNMP communications use both authentication and
encryption (only available for the SNMPv3 security model).