Installation guide

The firewall rules must be recreated to allow traffic to pass through for the Client
Connection port and the Default Channel port. SolarWinds recommends that
the firewall be configured to allow the Client to connect to the Client Connection
port by process, nfgui.exe, rather than by a specific port. To enable Channel
communications between servers, change the Network List Manager Policy so
that the SolarWinds Channel network is identified as a Private Network, and
not the default Unidentified Network, and configure the firewall to allow traffic
to pass through on Port 57348, the Default Channel port.
Anti-Malware Recommendations
Consult with and implement the advice of your anti-malware provider, as
SolarWinds guidelines often follow these recommendations. Consult the
SolarWinds Knowledge Base for up to date information on specific anti-malware
products.
Do not use file level anti-malware to protect application server databases, such
as MS SQL Server databases. The nature of database contents can cause
false positives in malware detection, leading to failed database applications,
data integrity errors, and performance degradation.
SolarWinds recommends that when implementing SolarWinds Failover Engine,
you do not replicate file level anti-malware temp files using SolarWinds Failover
Engine.
The file level anti-malware software running on the primary server must be the
same as the software that runs on the secondary server. In addition, the same
file level anti-malware must run during both active and passive roles.
Configure file level anti-malware to use the Management IP address on the
passive server for malware definition updates. If this is not possible, manually
update malware definitions on the passive server.
Exclude the following SolarWinds directories from file level anti-malware scans
( C:\Program Files\SolarWinds\FoE\ is the default installation directory):
C:\Program Files\SolarWinds\FoE\r2\logs
C:\Program Files\SolarWinds\FoE\r2\log
Any configuration changes made to a file level anti-malware product on one
server (such as exclusions) must be made on the other server as well.
SolarWinds Failover Engine does not replicate this information.
Implementation - 21
SolarWinds Failover Engine - Installation Guide