Send Snmp Trap Alerts On Resolution; Send Nagios Event Alerts On Resolution - Tripp Lite B092-016 Owner's Manual

Chapter 7: Alerts, Automated Response and Logging

7.2.10 Send SNMP Trap alerts on Resolution

The Administrator can configure the Simple Network Management Protocol (SNMP) agent that resides on the console server to send
SNMP trap alerts to an NMS management application:
• Select Alerts & Logging: SNMP
• Select Primary SNMP Manager tab. The Primary and Secondary SNMP Manager tabs are used to configure where and
how outgoing SNMP alerts and notifications are sent. If you require your console server to send alerts via SNMP then, at a
minimum, a Primary SNMP Manager must be configured. Optionally, a second SNMP Network Manager with its own SNMP
settings can be specified on the Secondary SNMP Manager tab
Note: Console Servers can be configured to provide status information on demand using snmpd. This SNMP agent is
configured using the SNMP Service Detail on Alerts & Logging: SNMP - as described in Chapter 15.
• Select the Manager Protocol. SNMP is generally a UDP-based protocol, though it infrequently uses TCP instead.
• Enter the host address of the SNMP Network Manager into the Manager Address field.
• Enter the TCP/IP port number into the Manager Trap Port field (default =162).
• Select the Version to be used. The console server SNMP agent supports SNMP v1, v2 and v3
• Enter the Community name for SNMP v1 or SNMP v2c. At a minimum, a community needs to be set for either SNMP v1
or v2c traps to work. An SNMP community is the group to which devices and management stations running SNMP belong.
It helps define where information is sent. SNMP default communities are private for Write and public for Read.
• Configure SNMP v3 if required. For SNMP v3 messages, the user's details and security level must match what the
receiving SNMP Network Manager is expecting. SNMP v3 mandates that the message will be rejected unless the SNMPv3
user sending the trap already exists in the user database on the SNMP Manager. The user database in a SNMP v3
application is actually referenced by a combination of the Username and the Engine ID for the given SNMP application you
are talking to.
o Enter the Engine ID for the user sending messages as a hex number (e.g. 0x8000000001020304).
o Specify the Security Level. The level of security has to be compatible with the settings of the remote SNMP Network
Manager.
noAuthNoPriv
authNoPriv
authPriv
o Complete the Username. This is the Security Name of the SNMPv3 user sending the message. This field is
mandatory and must be completed when configuring the console server for SNMPv3.
o An Authentication Protocol (SHA or MD5) and Authentication Password must be given for a Security Level of either
authNoPriv or authPriv. The password must contain at least 8 characters to be valid.
o A Privacy Protocol (DES or AES) must be specified for the authPriv level of security to be used as the encryption
algorithm. AES is recommended for stronger security. A password of at least 8 characters must be provided for
encryption to work.
• Click Apply
Note: Console Servers with V3.0 firmware (and later) embed the net-snmpd daemon which can accept SNMP requests from remote
SNMP management servers and provides information on serial port and device status (refer Chapter 15.5 for more details).
Console servers with firmware earlier than V3.3 could only configure a Primary SNMP server from the Management Console.
Refer Chapter 15.5 for details on configuring the snmptrap daemon to send traps/notifications to multiple remote SNMP servers.

7.2.11 Send Nagios Event alerts on Resolution

To notify the central Nagios server of Alerts, NSCA must be enabled under System: Nagios and Nagios must be enabled for
each applicable host or port under Serial & Network: Network Hosts or Serial & Network: Serial Ports (refer to Chapter 10).
No authentication or encryption.
Authentication only. An authentication protocol (SHA or MD5) and password will be required.
Uses both authentication and encryption. This is the highest level of security and requires an
encryption protocol (DES or AES) and password in addition to the authentication protocol and
password.
120