Description

This article describes the issue of Network Monitoring unable to receive traps from devices. Under Events, the traps for some devices cannot be seen.

Symptoms

A few probable causes for this issue are as follows:

 

  • Due to incorrect SNMP community string
  • An issue with the device configuration

Solution

 

  • Verify that you can poll the device via Junos Space CLI. You can do so by using the following command.
     
  • For SNMP V2, the snmpwalk command will be:
                    
  snmpwalk -v2c -c <community-string> <target-device-ip>

  Example: snmpwalk -v2c -c public 2.2.2.2

  If this fails with a timeout error:

   Timeout: No Response from 2.2.2.2

     
  • For SNMP V3, the snmpwalk command will be:

snmpwalk -v3 -l authPriv -u <UserID> -a <Authentication_Type>  -A "<Authentication_Key>" -x <Privacy_Type>  -X <"Privacy_Key"> <target-device-ip>
            

Example:

snmpwalk -v3 -l authPriv -u Space -a MD5 -A juniper1 -x AES -X juniper1 3.3.3.3

     

 

  • If the SNMP response is timeout, it indicates an issue in polling the device. Successful execution will display a list of OID. You need to validate that the community string is defined correctly on Junos Space and on the device end.
 
  • If the SNMP response is fine and still you cannot see the traps in Network Monitoring UI, then please check if Junos Space is getting traffic from the device by running the following command on Space CLI.
  
  • tcpdump -nn -i any port 162 and host <Device IP>

Example:

tcpdump -nn -i any port 162 and host 10.137.193.10

tcpdump: verbose output suppressed, use -v or -vv for full protocol decode

listening on any, link-type LINUX_SLL (Linux cooked), capture size 262144 bytes

11:17:15.025526 IP 10.137.193.10.64016 > 10.0.5.213.162: C="space" Trap(298) .1.3.6.1.4.1.2636.4.1 10.137.193.10 enterpriseSpecific s=2 65587870 .1.3.6.1.4.1.2636.3.1.8.1.1.1073741824.1073741823.1073741823.1073741823=1073741824 .1.3.6.1.4.1.2636.3.1.8.1.2.1073741824.1073741823.1073741823.1073741823=1073741823 .1.3.6.1.4.1.2636.3.1.8.1.3.1073741824.1073741823.1073741823.1073741823=1073741823 .1.3.6.1.4.1.2636.3.1.8.1.4.1073741824.1073741823.1073741823.1073741823=1073741823 .1.3.6.1.4.1.2636.3.1.8.1.6.1073741824.1073741823.1073741823.1073741823="abcdefghijklmnopqrst" .1.3.6.1.4.1.2636.3.1.13.1.6.1073741824.1073741823.1073741823.1073741823=7

 

  • If the traps are not received in tcpdump, then there could be an issue with the device configuration. Please contact the concerned device team to review the device configuration.
     
  • If the traps are received in tcpdump, However not displayed in Network Monitoring UI.  Then we have to check trapd.log for further investigation. Hence, please contact JTAC support for further assistance

 

 

Modification History

2024-03-13 : Article Created