![background image](/i/tripp-lite/128520/tripp-lite-b094-008-2e-m-f-b096-048-b096-016-b094-008-2e-v-b096-032/h/tripp-lite-b094-008-2e-m-f-b096-048-b096-016-b094-008-2e-v-b096-032-131.png)
131
Chapter 7: Alerts, Automated Response and Logging
• 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 No authentication or encryption.
authNoPriv
Authentication only. An authentication protocol (SHA or MD5) and password will be required.
authPriv
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.
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.
Note:
For firmware versions 3.10.2 and above, a new SNMP status and trap MIBS were created to provide more and better
structured SNMP status and traps from
console servers
. There is an option in the SNMP menu to
Use Legacy Notifications
for the SNMP traps. In setting this option, the console server will send SNMP traps that are compatible with those sent from
older firmware versions before new MIBS were added. This ensures that the firmware upgrade will not upset the existing SNMP
management settings already in place.
When upgrading from an old firmware version that does not support newer SNMP MIBs/traps (versions before 3.10.2) to
firmware that does support the new MIBs/traps:
• If the SNMP service was enabled and an SNMP manager was configured before upgrading the firmware, the console
server will be configured to use the legacy traps after upgrading.
• If the SNMP service was not enabled or no SNMP manger was configured before the upgrade, then the console server will
be configured to use the new SNMP traps after the upgrade. Note: this will not have any effect until the SNMP service is
turned on and an SNMP manager is configured.
• When starting up using the new firmware after a config erase, the console server will be configured to use the new SNMP
traps.
• When upgrading from a firmware version that supports the new traps to a newer version that supports the new traps, the
‘use legacy traps’ setting should be kept the same – no checking SNMP service/manager configuration is needed.
7.2.12 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).