I would like to see multi-homed Orion servers to monitor on specific interfaces for specific nodes, to account for scenarios were interfaces exist on separate distinct networkl
we have additional pollers for that purpose but I'm guessing you don't want to buy AP if your license is not fully used correct?
Yes that is correct, our current polling engine is only running at 34% utilization, and the segregated network isn't very large(but is important for us to monitor) so another polling engine would be underutilized.
Effectively you want to have a remote poller? i.e. some sort of lightweight application that can give you visibility of other networks?
Not in this case. The segregated network not only resides on a different subnet, but also was physically separate. In this case we tried to physically attach the segregated network through a second NIC. This was when we discovered that Solarwinds binds to the first NIC on a machine and will only poll through the primary NIC.
Yes, a lot of requirements to monitor isolated networks directly attached to Orion server on different NICs. I think this requires Orion engine to support multiple IPs, so it can go out from the right NIC.
As I noted above, this is really easy to do, and something we do with all of our polling engines. All you need to do is create static routes in Windows telling the system how to get to the different isolated networks so that the traffic goes out the correct gateway. Once you do that you can point Orion at the IP of the isolated network and Windows will send the data out the correct interface. What you are asking for is a function of the network stack, not of Orion.
