Add Trap Recipients - Sun Microsystems StorageTek SL500 User Manual

SNMP Configuration and Usage Tasks

Add Trap Recipients

▼
A recipient is a location on a manager where the SNMP agent sends traps. This location
is defined by the combination of either the IP address or DNS name and the port
number.
Use this procedure to add a trap recipient.
1. Select Tools > System Detail.
2. Select the Library folder from the device tree.
3. Select SNMP > Add Trap Recipient and enter the following details:
Host
TrapLevel
Version
Community (v2c
only)
TrapName (v3 only)
Auth (v3 only)
AuthPass (v3 only)
Priv (v3 only)
PrivPass (v3 only)
EngineID (v3 only)
4. Click Apply.
The indexed trap recipients list is displayed at the bottom of the screen. This list
supports up to 20 recipients with no duplicate entries. Users must add themselves to
the recipients list to receive traps.
304 SL500 User's Guide • July 2008
Server name where the SNMP software application resides.
See "Trap Levels" on page 299
Version of the SNMP standard. The SL500 library supports:
SNMPv2c of the simple network management protocol for
■
machine status queries. With this version, any information
transmitted is not secure.
SNMPv3 of the simple network management protocol is
■
reserved for proprietary information. Because this version
supports encryption and stronger user identification it is
the preferred protocol for proprietary data.
Agent community string. When set to public, requests coming
from any community string will be accepted.
Name of the trap recipient.
Authentication protocol type (MD5 or SHA) string for users
and hosts receiving traps. One of the two primary SNMPv3
security protocols designed to reliably identify the integrity
of the originating party.
Authentication password of the user.
Privacy protocol type (DES or AES): The other two primary
SNMPv3 security protocols are designed to protect
information within the message from disclosure.
Encryption Password that is the private key for encryption.
Engine Id is an administratively unique identifier of an
SNMP v3 engine used for identification, not for addressing
(Source: The Internet Society, RFC 3411). SNMP v3
authentication and encryption keys are generated based upon
the associated passwords and the engine ID. The engine ID is
a string of at most 31 hexadecimal characters, preceded with
0x.
for details.
Revision: KA • 96116