SNMP Trap Configuration

You can specify the device(s) that receive the SNMP traps generated by PowerChute for UPS critical and lost communication events.

To configure a Trap Receiver, select Add Trap Receiver and configure:

1. Enable: Select the checkbox to enable the Trap Receiver.
2. NMS IP/Host Name: The IP address, Host Name or Fully Qualified Domain Name of the NMS.
3. Port: The port on which the NMS will listen for incoming traps. The default port number is 162.
4. SNMPv1: Select this if you want to send the traps via SNMPv1.
   • Community Name: Enter the Community Name of the SNMPv1 user profile to be used as an identifier when SNMPv1 traps are sent to this receiver.
5. SNMPv3: Select this if you want to send the traps via SNMPv3.

   • User Name: Select the user name of the SNMPv3 user profile to be used as an identifier when SNMPv3 traps are sent to this receiver.

Click the SNMP Trap Receiver Test to send a test trap to the configured Trap Receiver. Check the Trap Receiver to ensure that the test trap was received.

To edit an existing SNMP Trap Receiver, click the   button. To delete an SNMP Trap Receiver, click the button.

UPS Critical Events

PowerChute sends SNMP traps to the configured Trap Receiver(s) upon the following events:

• PowerChute Critical Event triggers a Shutdown
  When a critical event (such as On Battery) occurs and a Shutdown is triggered, PowerChute sends an SNMP trap detailing the Event Name,  UPS Setup (for advanced configurations), and Affected Virtual Hosts (if Virtualization support is enabled).
  
• PowerChute Critical Event Resolved
  If the option to Send Trap when condition is cleared is enabled, when a PowerChute Critical Event which triggered a Shutdown is resolved, PowerChute sends an SNMP trap to the configured NMS.

Lost Communication Events

PowerChute sends SNMP traps to the configured Trap Receiver(s) upon the following events:

• Network Communications Lost
  If PowerChute cannot communicate with the Network Management Card of the UPS, a trap is sent to the configured Trap Receiver.
  
• UPS Communications Lost
  If the Network Management Card cannot communicate with the UPS, a trap is sent to the configured Trap Receiver.
  

If the option to Send Trap when condition is cleared is enabled, the following traps are sent:

• Network Communications Lost Resolved
  If PowerChute regains communication with the Network Management Card of the UPS, a trap is sent to the configured Trap Receiver.
  
• UPS Communications Lost Resolved
  If communication is regained between the NMC and the UPS, a trap is sent to the configured Trap Receiver.

Other Events

• Software Update Available Trap
  When the PowerChute Auto Update functionality detects that there is a new update available; a trap is sent to the configured Trap Receiver.
  
• PowerChute Test Trap
  When configuring a Trap Receiver, a test trap can be sent to determine if the Trap Receiver is receiving the traps. See SNMP Trap Receiver Test.

See SNMP Data Points > PowerChute Traps for more information on PowerChute SNMP Trap OIDs.

Configuring SNMP Trap Notification Settings

To configure the settings for UPS Critical Event or Lost Communication traps:

1. Go to SNMP Settings > SNMP Traps
2. Click on the icon next to UPS Critical Events or Lost Communication Events
3. Select the Enable checkbox to enable traps for critical events.
4. Delay: Specify the length of time that Event must persist before a trap is sent. If the Event is cleared before this time, no trap is sent.
5. Repeat Interval: Specify the time interval in seconds that the trap is re-sent.
6. Select:
   • Repeat until condition clears if you want the trap to be sent at the repeat interval until the Event is cleared.
   • Repeat X times to specify the number of times the trap will be sent when the Event occurs.
7. Select Send Trap when condition is cleared to be notified when the Event is cleared.
   Note: If the PowerChute server is shut down due to a UPS Critical Event, no clearing Trap will be sent to the NMS.