TCP Port Monitor for FQDNs on external nodes?

I need to monitor a port on an external node via FQDN and not the IP address. What are my options other than using a script?

For the record, Solarwinds SAM and NPM don't support dynamic hostnames on external nodes and thus the regular TCP Monitor template can't be used: Polling IP on external nodes with dynamic IP not updating

Thanks!

Find more posts tagged with

external node

tcp_port_monitor

Accepted answers

All comments

aLTeReGo

Properly updating the IP address for dynamic external node types is a bug we are tracking internally under CORE-341. If the port you are monitoring is a Web Server or similar web service, you could use Web Performance Monitor, as WPM is not impacted by this defect. Similarly, if you have IPSLA capable Cisco devices in your environment, you could use Voice & Network Quality Manager to create and monitor a TCP Connect operation. It too is not impacted by this issue.

akhasheni

If the port you are monitoring is a Web Server or similar web service, you could use Web Performance Monitor, as WPM is not impacted by this defect. Similarly, if you have IPSLA capable Cisco devices in your environment, you could use Voice & Network Quality Manager to create and monitor a TCP Connect operation. It too is not impacted by this issue.

The external nodes aren't web servers - they're Aspera, FTP, SFTP servers. We only need to check if a port is open. So a small modification on the standard monitor to include a field where I could run a check on the DNS name vs. IP would do it.
Have neither the WPM nor the VNQM and not planning on getting them: no need.

Properly updating the IP address for dynamic external node types is a bug we are tracking internally under CORE-341.

Any ETAs?

P.S. Thanks for confirming that this is an issue and a bug and not a "feature" or "as designed" behavior as Solarwinds support maintained. That's a relief - I was starting to think I was crazy. (The jury is out on that one, still.)

aLTeReGo

As is typically the case, we are unfortunately not permitted to discuss timeframes.