Installation guide

◦
At least one Domain Controller at the DR site
◦
Refer to the following articles in the SolarWinds Knowledge Base:

Knowledge base article SWREFID-1937 – Configuring DNS with
SolarWinds Failover Engine in a WAN Environment

Knowledge base article SWREFID-1938 – Configuring SolarWinds
Failover Engine to Update BIND9 DNS Servers Deployed in a WAN
Bandwidth
SolarWinds Failover Engine includes automatic bandwidth optimization in WAN
environments. This feature compresses data transferred over the SolarWinds
Channel, optimizing the traffic for low bandwidth connections causing some
additional CPU load on the active server.
Determine the available bandwidth and estimate the required volume of data
throughput to determine acceptable latency for the throughput. Additionally,
the bandwidth can affect the required queue size to accommodate the estimated
volume of data. SolarWinds recommends making a minimum of 1Mbit of spare
bandwidth available to SolarWinds Failover Engine.
Latency
Latency has a direct effect on data throughput. Latency on the link should not
fall below the standard defined for a T1 connection (2-5ms for the first hop).
SolarWinds Failover Engine Diagnostics can assist in determining the available
bandwidth, required bandwidth, and server workload. For more information
about SolarWinds Failover Engine Diagnostics, contact SolarWinds Professional
Services.
Network Interface Card (NIC) Configuration
SolarWinds Failover Engine supports the use of both a single NIC or multiple
NIC configuration on primary and secondary servers. The number of NICs
present will determine how the NICs are configured.
Important: The primary and secondary servers must have the same number
of NICs.
Multi-NIC Configuration
When Using multiple NICs, one NIC functions for client and management access
while a second NIC functions as a dedicated SolarWinds Channel.
Primary Server
The primary server is configured with the following connections:
18 - Implementation
Installation Guide - SolarWinds Failover Engine