Does Solarwinds have a recommended or best practice way to monitor a node (Windows server) with multiple IP's? It could be multiple IP's on one or more physical adapters, or a single IP's on multiple physical adapters.
We need a single IP that is reachable by the Orion server and allows query for ICMP/SNMP data. This will allow us to check status and retrieve statistics about all NICs, including status. If you want to also ping each specific IP to check response time (let's say the NICs were connected to different switches), you'd want to use APM and set up a ping monitor for each IP.
I am having a similar issue but in my case, I have over 400 nodes with 2 entries. Not duplicates, but more than 1 IP address associated with a node, therefore 2 entries in the database. That means more polling of CPU/Memory, HDD...etc (which I have to cleanup manually).
It would be nice if there was a way of managing this.
The other problem is that when I re-discover, I'll run in to the exact same problem again. I try to keep a clean streamlined database but this last discovery has simply ruined the previous work and I am feeling unwilling to fix it again.
Any update for this topic?
Our Orion (NPM APM NCM) server has direct connections into multiple firewall and restricted networks. Thus can see servers and firewalls with multiple ip addresses.
Doing a network discovery (Discovery Central, Network Sonar) we are left with imported devices (routers, firewalls, servers) that have the same name, services, etc. but with different ip addresses.
What is the best / preferred method of handling systems that have multiple addresses?
Is there a method of selecting which address is preferred for monitoring (Example: for a device having a nat address that may be the preferred address for monitoring, versus the local server address)
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process.