All,
We have three separate AVP 5.1 SP 1 environments. All are configured identically, with the exception of available ports.
Two of the 3 VPMS servers are set up to send SNMP traps to a third-party NMS (technically, they are Inform messages, just in case that matters). This works, and tickets are generated from the traps as we anticipate.
We are working on configuring the third VPMS to do the same. The third VPMS is behind a firewall in a "secure" environment. We have configured the SNMP settings in VPMS identically to the settings on the other two servers. When we go to "Test" the alarm, we get a failure message in the logs.
Now, the default answer will be "it's the firewall, dummy"...and while you may be right, we're confused.
We have worked with the group that maintains our firewalls, and they are actively watching the logs on the FW's when we perform the test. There's no evidence that the request ever makes it to the FW.
I've also run a tcpdump against eth0 (unfiltered, and filtered) while performing a test, and there's no traffic being offered to the NMS.
We do have a FW rule to allow traffic from the VPMS to the NMS on port 162, so the FW shouldn't be the issue, regardless, though we're open to the possibility if we're missing something.
Any thoughts?
Thanks!
We have three separate AVP 5.1 SP 1 environments. All are configured identically, with the exception of available ports.
Two of the 3 VPMS servers are set up to send SNMP traps to a third-party NMS (technically, they are Inform messages, just in case that matters). This works, and tickets are generated from the traps as we anticipate.
We are working on configuring the third VPMS to do the same. The third VPMS is behind a firewall in a "secure" environment. We have configured the SNMP settings in VPMS identically to the settings on the other two servers. When we go to "Test" the alarm, we get a failure message in the logs.
Now, the default answer will be "it's the firewall, dummy"...and while you may be right, we're confused.
We have worked with the group that maintains our firewalls, and they are actively watching the logs on the FW's when we perform the test. There's no evidence that the request ever makes it to the FW.
I've also run a tcpdump against eth0 (unfiltered, and filtered) while performing a test, and there's no traffic being offered to the NMS.
We do have a FW rule to allow traffic from the VPMS to the NMS on port 162, so the FW shouldn't be the issue, regardless, though we're open to the possibility if we're missing something.
Any thoughts?
Thanks!
Comment