Specifying Trap Managers and Trap Types
Traps indicating status changes are issued by the switch to specified trap managers.
You must specify trap managers so that key events are reported by this switch to
your management station (using network management platforms such as
HP OpenView).
You can specify up to five management stations that will receive
authentication failure messages and other trap messages from the switch.
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 au thenticat ion or encry ption
options (authNoPriv or authPriv), the user name must first be defined in the
SNMPv3 Users page (page 5-9). Otherwise, the authentication password and/or
privacy password will not exist, and the switch will not authorize SNMP ac cess for
the host. However, if you specify a V3 hos t with th e no authen ticatio n (noAut h)
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 mes sages by de fault. Th e recipi ent
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 acknowle dgement 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 ne twor k
traffic. You should consider these effects when deciding w hether to issu e
notifications as traps or informs.
To send an inform to a SNMPv2c host, complete these st eps:
1. Enable the SNMP agent (page 5-2).
2. Enable trap informs as described in the following pages.
3. Create a view with the required notification messages (page 5-1 7).
4. Create a group that includes the required notify view (page 5-13).
To send an inform to a SNMPv3 host, complete these steps:
1. Enable the SNMP agent (page 5-2).
2. Enable trap informs as described in the following pages.
3. Create a view with the required notification messages (page 5-1 7).
4. Create a group that includes the required notify view (page 5-13).
5. Specify a remote engine ID where the user resides (page 5-8).
6. Then configure a remote user (page 5-11).
Command Attributes
• Trap Manager Capability – This swit ch supports up to five trap manager s.
• Current – Displays a list of the trap manager s current ly configu red.
• Trap Manager IP Addre ss – IP address of a new mana gem e nt s tation to receive
notification messages.
• Trap Manager Community String – Specifies a val id commun ity string f or 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 Config uration page ( for

5-4

Simple Network Management Protocol

5