This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.

You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Universal Device Poller and Firewall Rules

klc2009 over 9 years ago

Hi,

I am moving all of our devices from one monitoring server to another on a new network. From the old server, I could reach most internal devices without passing through a firewall. On the new server, however, there are one or more firewalls involved. I am not a network technician, so each time I run into connectivity issues, I have to get my network team to investigate what is blocking my requests.

I've finally got almost everything talking again (it's been a challenge!) but I'm running into a problem with Universal Device Pollers. I presumed that having SNMP open on the firewall, and successfully polling devices would be enough, but apparently it's not, as my pollers still work from the old server but tell me "OID is not supported" when testing from the new server.

What am I missing? Is there a specific port that needs to be opened to allow requests from the UDP?

Thanks for any help.

0 HolyGuacamole over 9 years ago

Universal Device Pollers use the same SNMP credentials that are assigned to the node. If the node polling like CPU, Memory, etc are working the custom pollers also should work. The SNMP agents on all your monitored nodes run on port 161.
Cancel
Vote Up 0 Vote Down

Cancel
0 mharvey over 9 years ago

Make sure they aren't allowing both TCP and UDP traffic on that port. I've seen issues where the TCP exception can cause issues. Just need UDP. Also make sure the new server doesn't have a Windows Firewall that is needed or there are any access control lists (ACLs) setup that were allowing SNMP from the old server by its IP.
Cancel
Vote Up 0 Vote Down

Cancel
0 klc2009 over 9 years ago in reply to mharvey

I can successfully poll the device via SNMP from both servers, but can only get the custom poller to work from the old one. I'll have the network team check the firewall rule and remove UDP if it's there. Thanks!
Cancel
Vote Up 0 Vote Down

Cancel
0 klc2009 over 9 years ago in reply to klc2009

Correction, remove TCP...
Cancel
Vote Up 0 Vote Down

Cancel
0 HolyGuacamole over 9 years ago in reply to klc2009

If you assign an existing custom poller to a new node, or if you create a custom poller from scratch and assign to a node, does it make any difference?
Cancel
Vote Up 0 Vote Down

Cancel