---

Subject:	Can you verify zentraps is
Author:	Jay Stanley
Posted:	2016-09-15 10:40

Can you verify zentraps is running and assigned to the proper IP I think zentraps is off by default.

---

Subject:	zentrap is running
Author:	[Not Specified]
Posted:	2016-09-15 13:06

Hi and thanks.

Yes, zentrapis running and an IP was assigned to its container and port 162seems to be openafaict (docker is new to me).

excerptsfrom the zentrap log:

Application:localhost_snmp_trap Purpose:export
HostID:640a6301 HostIP:10.100.1.199 HostPort:32771 ContainerID:e823e0aa055dc92c2c43995...
ContainerIP:172.17.0.21 ContainerPort:162 Protocol:udp

[root@zenoss~]# nmap -Pn -sU -p162 172.17.0.21

Starting Nmap 6.40 ( http://nmap.org ) at 2016-09-15 13:41 EDT
Nmap scan report for 172.17.0.21
Host is up (0.00017s latency).
PORT STATE SERVICE
162/udp open|filtered snmptrap

Any other things I should be checking or testing

---

Subject:	resolved -- d'oh!
Author:	[Not Specified]
Posted:	2016-11-10 13:52

Thanks for replying Jane! I forgot to upate, I resolved this issue. I overlooked the fact that I had upgraded the kernel to 3.19 when testing out the Intel NVMe SSD. Rebuilt the box using 3.10 and installed 5.1.7 core and everything was up and running correctly by the end of the day.

TL;DR: On 3.19, it was strange because everything else worked (e.g. snmp, syslog)except snmp traps. I could see (via conntrack, zenoss 5.1.5 core) that data was getting forwarded correctly, but anything from snmp traps wouldn't show up in the events. Anyway, since "downgrading" back to kernel 3.10, zenoss 5.1.7 core has been online and in production for about six weeks now.

thanks,

-J.