The FOE/Solarwinds channel adapter MUST be different from the adapter you use for polling.
The servers uses the FOE/Channel adapter to synchronize configuration and log-files to the passive server.
The FOE will disable the adapter you use for polling on the passive [backup] server (the Neverfail packet driver performs this function)
Therefore, they have to be separate adapters.
I've not done this, but see no reason why it would not work:
If you have VLANs available on the server(s) then you could try creating two VLAN adapters. Now you'll have two logical network adapters available one for the FOE channel and the other for the polling channel. FOE can disable the polling channel on the passive server without killing the FOE channel being used for replication.
Also: note that if you are in a WAN scenario make sure your syslog and traps are being sent to both the primary and secondary servers.FOE will ensure only the currently active server receives the packets and processes them into the database.
Hope this helps
I'll give this a shot. So the adapters for the FOE/SolarWinds channel would be routable, then?
1 of 1 people found this helpful
I don't know what your network infrastructure is like to answer that. Here I have MPLS routers running VRFs so in my case 'Yes'
I have a pair of 'backdoor' subnets that are routed between the datacenters (in our backdoor network) that carry the FOE and SQL traffic
I have a pair of 'frontdoor' subnets that are globally routed in the network (in our management network) that carry polling, syslog, and trap traffic.
I ended up with what we have by sending Visio diagrams to our SolarWinds sales folks and asking them if that would work.