How to test if Site24x7 On-Premise Poller is receiving traps?

How to test if Site24x7 On-Premise Poller is receiving traps?

Testing using Wireshark

You can verify if SNMP traps are received by Site24x7 On-Premise Poller using the steps below:
  1. Install the latest version of Wireshark.
    For Windows, you can download from Wireshark's official website.
    For Linux, you can install using the following commands:
    apt install wireshark
  2. Run Wireshark with admin/root privileges.
  3. Select the required interfaces and Start Capture (double click, press Enter, or right-click to Start Capture).

  4. Filter the flows from UDP port 162 by entering udp.port == 162. Click Enter.

    Testing using Wireshark command line 

    If the MIB browser is inaccessible or fails to work,  use the given command line tool to check if the traps are received.

    Execute this command for it will list all the traps that have been received as shown below:
    >tshark -f "udp port 162"
    Output
    Capturing on 'eth0'

        1 0.000000000   10.10.10.1 → 10.10.10.100 SNMP 156 snmpV2-trap 1.3.6.1.2.1.1.3.0 1.3.6.1.6.3.1.1.4.1.0 1.3.6.1.2.1.2.1.0 1.3.6.1.2.1.2.1.0

        2 1.494270279   10.10.10.1 → 10.10.10.100 SNMP 156 snmpV2-trap 1.3.6.1.2.1.1.3.0 1.3.6.1.6.3.1.1.4.1.0 1.3.6.1.2.1.2.1.0 1.3.6.1.2.1.2.1.0

        3 1.924597683   10.10.10.1 → 10.10.10.100 SNMP 125 trap iso.3.6.1.2.1.11 1.3.6.1.2.1.4.5.0 1.3.6.1.2.1.2.1.0

        4 8.265532838   10.10.10.1 → 10.10.10.100 SNMP 173 snmpV2-trap 1.3.6.1.2.1.1.3.0 1.3.6.1.6.3.1.1.4.1.0 1.3.6.1.2.1.2.1.0 1.3.6.1.2.1.2.1.0 1.3.6.1.2.1.11.10.0

    If you're not receiving the traps yet, then zip the On-Premise Poller logs folder and contact support@site24x7.com.
    Troubleshooting steps if the traps are not received:
    1. If you receive the error message "Not Listening for Traps, Port(s) already in use." in the TrapViewer, your port might be occupied by another process. Please free the port and try again.
    2. Check if the device is added to Site24x7 for monitoring and is in an active state.
    3. Verify the configuration in your network device.
    4. Make sure that the port 162 is not blocked by a firewall.