Closed

Closed due to inactivity. Received 32 votes with last vote on 19 Nov 2019.

Multi-Homed Polling

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

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

  • We have/had picky auditors. And I am not sure if the 'feeling' about that setup has changed since the consultant regarding this issue/setup has found himself elsewhere.

    But I will take this solution of a setup back to those involved sometime soon.

  • Our PCI auditors said that as long as it was justified; restricted to only necessary ports and documented then it wasn't a problem.  It also goes through NAT so technically is not on the same network.  Your situation sounds like it may be a bit different thought.

  • That creates an issue for us, because there must be a physical connection and our compliance see's the connection, as being 'On' the network... or at least accessible from the main production network.

  • The poller then communicates back to our primary Orion system.

  • So your poller then communicated to your normal network Orion web server?  - Or another poller/web engine license stand alone entity that isn't at all connected to your production environment?

  • Yeah, that is problematic.  We got around that with PCI by getting an additional poller just dedicated to the PCI environment; it was an expensive pill to swallow.

  • Is there a way to set this up, so that compliance is kept when dealing with PCI networks?

      * I am having a hard time seeing the possibility when there is a 'physical' connection *

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

  • 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| ! ( |-| /\ [- |_ \/\/.