SNMP Traps are sent by the managed devices to the OpManager server for notifying important events. For the received traps to be processed in OpManager , they need suitable SNMP Trap Processors. The SNMP Traps that are processed can be found under Alarms > Trap Alarms.
The SNMP Traps that do not have suitable trap processors will not be processed. These traps are called unsolicited traps and can be found under Alarms > Unsolicited Traps (mouse hover action).
Note: The information about Unsolicited Traps apply only to OpManager build versions before 125201.
Given below is a list of reasons as to why you are unable to view the trap alarms in OpManager and how to troubleshoot them.
Reason #1: The device might not be monitored by OpManager .
Solution: Check if the device is monitored by OpManager . If not, rediscover the device and manage it with updated credentials in OpManager .
Reason #2: Trap destination might be wrong.
Solution: Check the trap destination in your end device. Test the traps from the end device and configure the end device to send the traps to the OpManager server.
Reason #3: Trap port might be occupied in OpManager .
Solution: Check if the port 162 is used by any other service or application. If the port is occupied,
Reason #4:Traps are not received due to inbound firewall rules.
Solution:Firewall policies might be blocking the incoming traffic to the port 162 in OpManager server. Turn off your Windows Firewall and check if OpManager is able to receive traps. If yes, check your inbound firewall rules and modify them accordingly.
Reason #5:There is no SNMP Trap Processor for processing traps.
Solution:Traps that do not have trap processors will not be processed. They can be found under Alarms >
Unsolicited Traps (mouse hover action). To be alerted of these unsolicited traps, you need to create appropriate trap processors.
Reason #6:Trap Processor might have issues with the processing criteria.
Solution:The SNMP Trap Processors created might have a criteria mismatch. This is due to
In the above cases, the SNMP Trap Processor has to be modified accordingly.
If the issue persists, follow the steps below to check whether the traps are received by OpManager :