For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Joe_Pena_46781's avatar
Joe_Pena_46781
Icon for Nimbostratus rankNimbostratus
Feb 04, 2009

SNMP Problem

I've been using SNMP traps for about 15 months on my F5 unti v9.4.2. I had it sending traps to my WUG server, so I always knew when a node/pool member/logins fail/config sync etc, via an email alert f...
management
monitoring
dennypayne's avatar
dennypayne
Icon for Employee rankEmployee
Feb 04, 2009
You can run a tcpdump on whichever vlan the unit should be sending traps out on looking for the SNMP port (162 unless you've changed it). 

 
 tcpdump -ni  port 162

If you are using the mgmt port to send to the SNMP destination then use eth0 instead of the vlan name.

This should at least show whether the unit is trying to send traffic out.

Denny