cancel
Showing results for 
Search instead for 
Did you mean: 
Create Post

Ability to create a Universal Device Poller on a different port that NPM is already using to monitor the node.

Ability to create a Universal Device Poller on a different port that NPM is already using to monitor the node.

I'd like to be able to configure a Universal Device Poller to use any port I wish regardless of how the node is monitored by NPM.  Our servers are monitored by NPM using SNMP on port 161 and WMI but we also want to use NPM to poll for application function and performance values which are available and accessible through the application's SNMP Master Agent service which listens on a port number other than 161. 

Today if my server is being monitored by NPM 10.7 using SNMP port 161, I cannot create a Universal Device Poller using port 7004.  If my server is being monitored using WMI, I can't create a Universal Device Poller for the node at all as it doesn't show up in the Universal Device Poller tool.  The resulting situation is that I must choose between being able to monitor system resources like cpu, memory, disk using port 161 or application performance using port 7004.

I've been exploring the possibility of using SAM's SNMP monitor but I haven't had any success to date.  This particular application monitoring seems easier to set up with Universal Device Pollers which is why I'm submitting this feature request for review.

Thank you!

3 Comments
Level 17

swuzer

As a workaround, see my example of monitoring SNMP data on WMI nodes below.

Dell Servers - Disk Hardware Health via SNMP

Level 7

Had to add all my devices in as ICMP only.. then manually change them to SNMP / set custom port and then attach the UDP... and then bypass the ~"can not verify snmp will correctly work"..... Perhaps this should just be changed to... BE able to FORCE add a node if SNMP cant pull during add node.

Community Manager
Community Manager
Status changed to: Open for Voting