|
|
| Subject: | Configuring trap destination to send to Zenoss 5 |
| Author: | Jane Curry |
| Posted: | 2016-01-21 03:43 |
Any device that is going to send TRAPs to Zenoss needs to setup the trap destination - usually Zenoss server on port UDP/162.
On Zenoss 5, this doesn't work. The Zenoss box listens for TRAPs on a random high port and docker then appears to have a redirect from this
The problem is that whenever Zenoss is restarted, the external high port changes and the internal address changes, so there is no constant mapping.
How should external devices be configured to send TRAPs to Zenoss 5
Cheers,
Jane
Email: jane.curry@skills-1st.co.uk Web: https://www.skills-1st.co.uk
| Subject: | Jane, |
| Author: | Andrew Kirch |
| Posted: | 2016-03-09 20:09 |
Jane,
I would guess that this should be properly documented. Please file it as a documentation bug when you return from Middle Earth (and I hope you enjoy your time off!)
Andrew Kirch
akirch@gvit.com
Need Zenoss support, consulting or custom development Look no further. Email or PM me!
Ready for Distributed Topology (collectors) for Zenoss 5 Coming May 1st from GoVanguard
| < |
Previous Configuring syslog on devices to forward to Zenoss 5 |
Next Error Upgrading 1.06/5.06 to 1.09/5.09 |
> |