Not Receiving traps to Spectrum, but they show in tcpdump/packet trace
search cancel

Not Receiving traps to Spectrum, but they show in tcpdump/packet trace

book

Article ID: 140322

calendar_today

Updated On:

Products

CA eHealth CA Spectrum

Issue/Introduction

We are developoing Southbound Gateway integration with a third party SNMP trap sender - we have confirmed traps are landing on the Linux server via tcpdump on port 162, but we are not seeing the same traps processed on the VNM model within Spectrum. 

Environment

Release : 10.4

Component : Spectrum Core / SpectroSERVER


Linux OS

Cause

- ip tables on the Linux OX blocking traffic on port 162


- the kernel sends traffic to the tcpdump before hitting iptables firewall, so traps will show in tcpdump but are still technically blocked by the internal firewall



Resolution

1.  To disable ip tables, log in as root:  


$ systemctl stop firewalld


# service iptables stop



NOTE: You may need to reference documentation for your version of Linux for proper syntax to disable the internal firewall