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.

Nodes with multiple IP's best practice

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.

Thanks,
David

  • Hi David--

    I've marked this for the PM to answer.

    M

  • 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.

    HTH, 

  • Chris,

    Is a ping monitor something provided out of the box on APM 3.5?  I do not see a ping monitor in the list of component monitors.

    Thanks,
    David

  • Sorry, you're right.  You'll need to use the custom script monitor and create a ping vbscript.

  • It would be best if all IP's were located under the node view of a device.  Is this an option that is on Solarwinds radar? 

  • On the NPM roadmap, handling multiple IPs is listed. Not sure what that means.... However,
    What I do a setup all IPs in NPM. I edit the Node Name (caption) of the secondard IPs and give a dash interface name.

    I do network stuff, so some devices have active passive pairs with a virtual IP. I actually manage the interfaces in the virtual IP since is will be the active node and will show all traffic.
    The other two, I manage NO interfaces... Only the node.

    Yes, we need a better way to manage this. The main thing is TO ALERT YOU OF DUPLICATES. I've just spent hours over the past few days trying to clean out duplicates.
  • 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.

  • Right.  By duplicate I mean same device imported with a different IP address.

    I'm with you on a bad import causing havoc. I feel your pain.

  • 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)

  • Hi all--

    Just an update to this thread.  Better handling of devices with multiple IPs is on the road map.  Please see the 3rd bullet on this "What we are working on" post.

    Thanks,
    DH