SUMMARY
The system can be configured to send system and application-specific alerts to a network management server using the SNMP protocol.
ISSUE
The system can be configured to send system and application-specific alerts to a network management server using the SNMP protocol. This provides network administrators with the ability to quickly respond to hardware or software conditions that require action. Alerts are delivered as incoming trap messages to a network management application. The Administrator Interface remains the primary interface for managing a Unitrends system.
Unitrends systems come configured with a default destination of notifications.unitrends.com. This enables Unitrends to service our customers with proactive resolution of problems, if and when they arise. For example, if a disk drive on the system is failing, a trap is received by the SNMP manager at notifications.unitrends.com, allowing Unitrends to pro-actively dispatch a warranty request on the failed component (if the support contract on the system is up-to-date).
Through the use of the Unitrends SNMP agent and MIB, you can configure alerts to be sent to your own Remote Monitoring and Management (RMM) software.
Notice, with the release of the Satori UI for 9.0 CentOS 6 based systems, this facility has yet to be implemented in the new UI. To access all SNMP and PSA functions of the Unitrends appliances the Legacy UI, accessed from the gear icon in the top right of the browser page is required. All instructions below assume the use of the Legacy UI.
To set up SNMP trap notifications
- Connect to the user interface of the Unitrends appliance and log in
- Select Configure on the left
- Be sure the "Appliances" tab is selected, then select "Edit"
- Select the "Advanced" tab
- Select "SNMP" at the bottom of the "Edit Appliance" dialog
- The "Edit SNMP Configuration (Advanced)" dialog will be displayed:
- Select "Add":
- In the Destination field, enter the hostname, fully-qualified domain name (FQDN), or IP address of the SNMP trap receiver host.
- In the Community field, enter the SNMP community string for the above SNMP trap receiver. Refer to your network administrator for the proper community string, as each organization has its own schema for SNMP notifications.
- Check the box next to "Enabled" to turn on notifications to the above SNMP trap receiver.
- Press "Save"
Test SNMP
On the "Edit SNMP Configuration" dialog, pressing "Test" will cause the Unitrends appliance to send an SNMP notification to all enabled destinations.
Note: SNMP traps to notifications.unitrends.com will have a return IP/destination of 140-130-228-89.static.cloud-ips.com. This is expected behavior, as Unitrends utilized a third-party to host SNMP trap receiver services. Example below:
A packet capture of a sample SNMP trap appears as follows:
0000 b8 70 f4 1c 6f 34 00 1e 4f 08 27 f8 08 00 45 00 .p..o4..O.'...E.
0010 01 3a 00 00 40 00 3f 11 db 35 c0 a8 65 22 c0 a8 .:..@.?..5..e..
0020 79 0a 92 b6 00 a2 01 26 6f 09 30 82 01 1a 02 01 y......&o.0.....
0030 01 04 06 70 75 62 6c 69 63 a7 82 01 0b 02 04 0c ...public.......
0040 2d 2d 9c 02 01 00 02 01 00 30 81 fc 30 10 06 08 --.......0..0...
0050 2b 06 01 02 01 01 03 00 43 04 01 3a d6 0f 30 1b +.......C..:..0.
0060 06 0a 2b 06 01 06 03 01 01 04 01 00 06 0d 2b 06 ..+...........+.
0070 01 04 01 81 aa 69 01 02 64 00 63 30 18 06 0b 2b .....i..d.c0...+
0080 06 01 04 01 81 aa 69 01 01 01 04 09 54 65 73 74 ......i.....Test
0090 20 54 72 61 70 30 13 06 0b 2b 06 01 04 01 81 aa Trap0...+......
00a0 69 01 01 02 04 04 4e 6f 6e 65 30 38 06 0b 2b 06 i.....None08..+.
00b0 01 04 01 81 aa 69 01 01 03 04 29 56 65 72 69 66 .....i....)Verif
00c0 79 20 74 68 61 74 20 53 4e 4d 50 20 63 6f 6e 66 y that SNMP conf
00d0 69 67 75 72 61 74 69 6f 6e 20 69 73 20 77 6f 72 iguration is wor
00e0 6b 69 6e 67 30 10 06 0b 2b 06 01 04 01 81 aa 69 king0...+......i
00f0 01 01 04 02 01 03 30 10 06 0b 2b 06 01 04 01 81 ......0...+.....
0100 aa 69 01 01 05 02 01 00 30 1d 06 0b 2b 06 01 04 .i......0...+...
0110 01 81 aa 69 01 01 06 04 0e 37 32 32 2d 31 30 30 ...i.....722-100
0120 2d 30 30 30 30 35 20 30 1f 06 0b 2b 06 01 04 01 -00005 0...+....
0130 81 aa 69 01 01 07 04 10 52 65 63 6f 76 65 72 79 ..i.....Recovery
0140 2d 37 32 32 20 44 50 55 -722 DPU
Troubleshooting
If SNMP traps are not being received by the intended host, please check the following:
- Confirm that the IP address of the destination is correct and reachable from the appliance.
- Confirm that the hostname or FQDN are correct.
- If the hostname or FQDN is correct, check the hosts file and DNS settings on the backup appliance (Configure > Networking).
- If DNS settings are correct, confirm your DNS server is properly resolving the hostname of your destination host.
- Check any firewall settings between the backup appliance and your destination host including local firewalls (i.e. Windows Firewall for Windows hosts).
- Make sure the proper community name was set.
- Check the SNMP notification software on your destination host to make sure it is configured to accept SNMP traps from your backup appliance and that it is configured for the proper community name.
SNMP trap conditions
The following tables describe the conditions that trigger traps on the Unitrends system, including trap data and the associated Object ID (OID) for each. The complete OID for a trap consists of a prefix followed by a specific trap number in the following format:
The prefix begins with .1.3.6.1.4.1.21865, which expands to iso.org.dod.internet.private.enterprises.21865 in the MIB tree (21865 is the Unitrends enterprise number), followed by 1 for the Unitrends product, then a designation to indicate the trap group (2.100) and finally, the trap number itself.
114
Traps are generated for the conditions described in the table below. IPMI events are only available for physical Recovery-712, 713, 714S and greater systems (note the 713S does not have IPMI). In addition, emails or alerts may be sent for these traps. Be aware that informational emails or alerts exist for which no trap is generated. These are not listed in the table.
Note that for each trap condition, there are multiple messages that may be sent, depending on the exception encountered. If an alert or email is sent for all exceptions within the trap condition, yes displays in the table. If no alert or email is sent for any exception within the trap condition, no displays in the table. If an email or alert is sent for one or more exceptions but not all within the trap condition, some displays in the table.
The member variables (extra information carried in the trap) have a prefix of enterprises.21865.1.1 followed by the ID of the variable. All variables are sent with each trap. This information is useful when configuring the Notifications Manager to filter the traps for a desired set. The following table describes these variables and their values:
SNMP agent
In release 7.2 and higher, Unitrends offers an SNMP agent that can respond to SNMP get requests. When upgrading to 7.2 and higher from older releases, the agent is deployed in a disabled state. The SNMP agent can currently accept SNMP get requests to monitor CPU utilization, memory utilization, network utilization, disk I/O, disk usage, and various other server performance parameters. Unitrends specific data–including backup, schedule, replication, and configuration information–is also available, although the Unitrends interface remains the primary method of accessing this information. For a complete list of all SNMP get requests that the agent responds to, see Unitrends Community KB 3054.
The Unitrends SNMP agent supports SNMP gets with SNMP version 1, 2c, and 3. You can configure the SNMP V3 username and password from the command line as follows:
The script defaults to authorization type MD5 and privacy/encryption of DES.
To enable the Unitrends SNMP agent
- Download the Unitrends MIB by going to Settings > Clients, Networks, and notifications > SNMP and then clicking the Download MIB button at the bottom of the screen.Then install it in your RMM environment. The file is also available at http://<Unitrends system IP>/snmp/.
NOTE: You will also need the Net-SNMP MIBs. These come standard in most RMM software. If you need them, they are available in the same location above.
-
Under the SNMP Agent Information section at the top of the screen, click Modify Entry.
-
Under Community, enter the community name to use for this SNMP node.
-
Check Enabled? if it is not already checked.
- Click Confirm.
NOTE: This opens UDP port 161 (SNMP) in the Unitrends system’s software firewall.