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:
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.
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 255.255.255.255 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.
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.
Same NIC and Same Subnet:
This configuration is not currently supported.
Management IP Addressing:
The Management IP address, if any must not permit access to any domain controllers on the network.
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.