Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Archive > 2017December15 - Deletes > Orion Failover Engine Channel and Principal (Public) connections to utilize the same subnet

Orion Failover Engine Channel and Principal (Public) connections to utilize the same subnet

Table of contents
Created by Robert Stidman, last modified by Jessica Solis on Dec 15, 2017

Views: 769 Votes: 1 Revisions: 11


This article provides information about configuration considerations for the Orion Failover Engine (FoE) Channel and Principal (Public) connections to utilize the same subnet.


FoE all versions



  • The following information applies to both Local Area Networks (LAN) and Wide Area Networks (WAN).

  • SolarWinds recommends at least two physical NICs on each server to provide hardware redundancy and prevent a single point of failure.


When configuring Principal (Public) and SolarWinds Channel connections, SolarWinds recommends the following: 

  1. SolarWinds Channel Considerations:
    1. If the IP addresses at each end of a SolarWinds Channel connection are in a different subnet from each other, you must add static routes as described in KB 1494 - How to Create a Static Route for the SolarWinds Channel Connection in a WAN Environment regardless of the Principal (Public) IP addresses.
    2. If the subnet used for a SolarWinds Channel IP address is used solely for SolarWinds Channel addressing, then the subnet mask may be relaxed to
    3. If the subnet used for SolarWinds Channel IP addresses is used for any other traffic, then the subnet mask (as mentioned in KB 1494) must be
  2. Dedicated (Separate) NICs in Dedicated (Separate) Subnets:

    When the Principal (Public) connection and the SolarWinds Channel connection(s) are on separate dedicated NICs and separate dedicated subnets, then the only requirement is to ensure that channel traffic is able to be routed across the SolarWinds Channel. Rules 1a and 1b above should be considered and static routes added if required.

  3. Dedicated (Separate) NICs and Same Subnet:

    If the Principal (Public) IP address and SolarWinds Channel IP address(es) are configured on dedicated (separate) NICs, but in the same subnet, then the SolarWinds Channel IP address(es) need to have a subnet mask of as described in item 1 above. Static routes as per KB 1494 will always be required, even if the IP addresses at both ends of the channel link are on the same subnet.

  4. Same NIC and separate (dedicated) Subnet:

    If the Principal (Public) IP address and SolarWinds Channel IP addresses are configured on the same NIC but on different subnets, the rules in item 1 above apply.  

  5. Same NIC and Same Subnet:

    This configuration is not currently supported.

  6. Management IP Addressing:

    1. The Management IP address, if any must not permit access to any domain controllers on the network.

    2. The Management IP address should be configured on a unique subnet, different from the subnet(s) used for the Principal (Public) IP address and SolarWinds Channel IP address.

Note: When Principal (Public) and SolarWinds Channel IP addresses on a server are on different NICs and different subnets, then the existing implementations will work.

Last modified