nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Multi-Homed Polling

FormerIdeaCreator

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

Find more posts tagged with

Node

feature_request

network

request

multi_home

npm

orion_npm_features

Status: None

Comments

michal.hrncirik

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?

joshuakrzywicki

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.

ashley.cotter

Effectively you want to have a remote poller? i.e. some sort of lightweight application that can give you visibility of other networks?

joshuakrzywicki

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.

IndoMie

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.

byrona

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.

IndoMie

When i said isolated network, it's actually directly connected network on different NIC. I should not need any static route nor gateway but it should have the same concept if the isolated network goes beyond a gateway.

I know this is about network stack in Windows, but how Orion will handle that.

My question is simple, Orion only has 1 engine IP which probably attached to the first NIC IP in windows. When Orion sending snmp, will I see different source IP sent on different NIC to the respective isolated network nodes?

If the answer is yes, then this is great.

If the answer is no and if the engine IP is used to go out on different NIC, how the snmp response will return to Orion server. It might return on the main NIC.

cheers,

|V| ! ( |-| /\ [- |_ \/\/.

byrona

The source IP seen by the monitored node will be the IP of the NIC that the data was sent from, not the engine IP.

IndoMie

Alright, that's great. I'll be sure to test this out and run some wireshark.

Sent from Windows Mail

From: byrona

Sent: ‎Tuesday‎, ‎July‎ ‎15‎, ‎2014 ‎3‎:‎58‎ ‎AM

To: Michael W

thwack

Multi-Homed Polling

new comment by byrona View all comments on this idea

The source IP seen by the monitored node will be the IP of the NIC that the data was sent from, not the engine IP.

Reply to this email to respond to byrona's comment.