183
1.877.877.2269
BLACKBOX.COM
NEED HELP?
LEAVE THE TECH TO US
LIVE 24/7
TECHNICAL
SUPPORT
1.877.877.2269
CHAPTER 8: ALERTS, AUTO-RESPONSE AND LOGGING
If required, configure SNMP v3. 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.
Enter the Engine ID for the user sending messages. This is a hex number. For example: 0x8000000001020304.
Specify the Security Level. The security level has to be compatible with the settings of the remote SNMP Network Manager.
TABLE 8-2. SECURITY LEVEL OPTIONS
SECURITY LEVEL
DESCRIPTION
noAuthNoPriv
No authentication or encryption
authNoPriv
Authentication only. An authentication protocol (SHA or MD5) and password are required.
authPriv
Authentication and encryption. Requires an encryption protocol (DES or AES) and an authentication protocol password.
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.
If the required Security Level is authNoPriv or authPrive, select an Authentication Protocol (either SHA or MD5) and an
Authentication Password. The password must contain at least 8 characters.
If the required Security Level is authPriv, select a Privacy Protocol (DES or AES). AES is recommended. A password of at least 8
characters must be provided for encryption to work.
Click Apply.
NOTE: Console servers with firmware v3.0 and later also embed the net-snmpd dæmon. This dæmon can accept SNMP requests
from remote SNMP management servers and provides information on alert status, serial port status and device status
(see Section 16.5 for more details). Console servers with firmware earlier than v3.3 can only configure a Primary SNMP
server from the Management Console. See Section 16.5 for details on configuring the snmptrap daemon to send traps/
notifications to multiple remote SNMP servers.
As of firmware v3.10.2, 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 Alerts & Logging > SNMP to Use Legacy Notifications for the SNMP traps.
Setting this option sets the console server to SNMP traps that are compatible with those sent in older firmware before the new
MIBS were added. Setting this option ensures a firmware upgrade to v3.10.2 or later does not break existing SNMP management.
FIGURE 8-14. SNMP OPTION SCREEN
When upgrading from firmware that does not support the newer SNMP MIBs/traps (firmware versions before 3.10.2) to firmware
that does support the new MIBs/traps:
