4 Replies Latest reply on Aug 1, 2016 1:46 PM by mehmoodakhan

    SolarWinds FOE implementation


      Hi All, We are planning to implement SolarWinds FOE in organization. We shall be using services from Neverfail technologies for SQL failover but i have one query we have constraint  that our HA setup doesn't failover using similar IP subnet at our DR (Disaster Recovery) location. Since SolarWinds polling works on IP which is configured on the devices once we failover using FOE it will failover to DR which will be active on different IP subnet as to what used at DC at present. How would this work setup work or do we need to some tweaking . Is there any other option available to get this setup I would really like to hear . Appreciate your help, Thank you, Mithun

        • Re: SolarWinds FOE implementation

          1. Send your syslog and traps to both the primary and secondary Solarwinds servers; they will only be processed on the server that is actually up.

          2. put both server IP addresses in the ACL lists on your devices so either primary or secondary server can poll it.


          [I run in this configuration, and am currently running a DR test out of our Spokane data center  for a couple of days to fully validate our DR operations]

          • Re: SolarWinds FOE implementation

            Thanks for your thoughts , How are you performing failover on SQL is it through Neverfail or any other technologies being used. Is your polling on both servers located on DC and DR performed simultaneously The huge task we would face here if you use your method is we are monitoring nearly 2000 + devices(which includes Network and Server devices) we might have to reconfigure the IPs of new Server on each devices to achieve smooth failover incase of disaster. Hence we wanted some methodologies to get our plan in place as mentioned in my query about.

            • Re: SolarWinds FOE implementation


              SolarWinds Failover Engine provides the following protection levels:

              Server Protection
              Provides continuous availability to end users should a hardware failure or operating system crash occur. Additionally, SolarWinds Failover Engine protects the network identity of the production server, ensuring users are provided with a replica server with the same server name and IP address in the event of a production server failure.
              Network Protection
              Proactively monitors network availability by polling up to three nodes, ensuring the active server is visible on the principal network.
              Application Protection
              Ensures the applications and services associated with SolarWinds products and associated modules stay alive on the network.
              Performance Protection
              Proactively monitors system performance and notifies administrators of problems. SolarWinds Failover Engine can also take pre-emptive action to prevent an outage.
              Data Protection
              Intercepts all data written by users and applications, and maintains a copy of this data on the passive server to be used in the event of a failover event.

              Supported Modules

              SolarWinds Failover Engine v6.7 supports the following modules:

              • SolarWinds Orion NPM Main and Additional Poller
                • v10.0 SP1
                • v10.1.1 SP1, v10.1.2, and v10.1.3
                • v10.2, v10.2.1, and v10.2.2
                • v10.3 and v10.3.1
                • v10.4
              • SolarWinds Orion IPAM
                • v1.7.1
                • v2.0 and v2.0.1
                • v3.0 and v3.1
              • SolarWinds Orion IPSLA
                • v3.5 and v3.5.1
                • v3.6
              • SolarWinds Orion VNQM 4.0
              • SolarWinds Orion APM
                • v3.5
                • v4.0.2
                • v4.2
              • SolarWinds Orion SAM
                • v5.0 and v5.0.1
                • v5.2 and v5.2 SP1 (Main Poller and Additional Poller)
              • SolarWinds Orion APM MP v4.0.1 and v4.0.2
              • SolarWinds Orion NTA
                • v3.6
                • v3.7
                • v3.8
                • v3.9
                • v3.10
              • SolarWinds Orion NCM
                • v6.0
                • v6.1
                • v7.0, v7.0.1, and v7.0.2
                • v7.1 and v7.1.1 Main and Additional Poller
              • SolarWinds Orion EOC
                • v1.2
                • v1.3
                • v1.4 and v1.4.1

              Supported Operating Systems

              SolarWinds Failover Engine supports the following operating systems:

              • Windows Server 2003 x86 Standard or Enterprise, SP1 and SP2
              • Windows Server 2003 x64 Enterprise SP2
              • Windows Server 2003 R2 x86 Standard or Enterprise
              • Windows Server 2003 R2 x64 Standard or Enterprise
              • Windows Server 2008 x86 or x64, SP1 and SP2 Standard or Enterprise
              • Windows Server 2008 R2 and SP1 Standard or Enterprise
              • Windows Server 2012 x64 Standard and Datacenter

              Note: SolarWinds recommends installing all Microsoft security updates prior to installation.