Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.

 

 

 

 

Home > Success Center > Network Performance Monitor (NPM) > Migrate Failover Engine LAN Configuration to SolarWinds Orion High Availability

Migrate Failover Engine LAN Configuration to SolarWinds Orion High Availability

Updated: 4-17-2017 | Migration Guide

This guide details how to migrate from a Failover Engine (FoE) LAN configuration for High Availability environment to SolarWinds High Availability (HA).

Migrating from FoE to SolarWinds HA is an easy process. You simply create and manage an HA pool in the Orion Web Console, using a provided installer to sync the secondary server products and configurations with the primary server. You can migrate to SolarWinds HA using your current server pairs or add new servers for HA pools. When migrating, you may need to upgrade your Orion Platform products.

You may need to upgrade your Orion Platform products to access HA. These instructions include upgrade steps as needed.

SolarWinds HA provides a high availability solution for your Orion server in a LAN environment. For disaster recovery (DR) on a WAN environment, you must continue using FoE.

Can I use FOE and SolarWinds HA in the same environment?

Yes, you can continue to use FOE and SolarWinds HA in the same Orion Platform environment. SolarWinds HA supports primary and secondary server pools for the Orion server and Additional Polling Servers. For example, you can install FOE to protect your primary/secondary Orion server, and HA to protect your Additional Polling Engines.

You cannot run FOE and SolarWinds HA to protect the same server. Only use FOE or HA to protect one server pair.

Benefits of SolarWinds HA

  • Access HA as an integrated feature through the Orion Web Console.
  • Easily set up HA through the Orion Web Console for your main polling engine and additional polling engines.

    SolarWinds HA does not support HA for additional web servers or Enterprise Operations Console (EOC).

  • Create and manage HA pools through the Orion Web Console.
  • Download an installer for your secondary server to install products and sync configurations.
  • Leverage servers with different specifications in HA pools.
  • Monitor and manage failovers directly through the Orion Web Console.

System and network requirements

Prior to migrating from FoE to SolarWinds HA, you should verify your systems meet the requirements for the new product versions and HA. SolarWinds HA supports High Availability pools with physical to physical (P2P), physical to virtual (P2V), virtual to physical (V2P), and virtual to virtual (V2V) pairs.

To take advantage of SolarWinds HA, you may need to also upgrade your Orion Platform product modules. HA is available in Orion Platform 2016.2 and supported products versions.

This guide includes upgrade instructions, if needed, for your HA migration.

We highly recommend using a new secondary server. If using VM servers, you can delete and create a new VM server for the secondary server. If using physical servers, prepare a new secondary server. Reusing the same FOE secondary server is not recommended. If you use this server, you will need to completely wipe the server and reinstall the OS.

System requirements

  • Both servers (physical and VM) do not have to be identical in hardware or software. We recommend they match closely in disk space, memory, CPU, and installed OS versions.
  • Both servers must be installed on Windows Server 2008 R2 or later.
  • Both servers must also meet the minimum hardware and software requirements for installed or upgraded Orion Platform product modules.
  • Both servers must be able to connect to your SolarWinds Orion Database.
  • If protecting an NTA environment, both servers must be able to connect to the separate NTA Flow Storage database. SolarWinds HA does not protect the Flow Storage Database. If you wish to provide High Availability for the NTA  Flow Storage Database, follow the steps outlined in this article.
  • SolarWinds does not provide failover support for any database.
  • Some SNMP trap, syslog message, and flow data is lost while waiting for the secondary server to become active.
  • SolarWinds HA does not support IPv6 addresses.

Networking requirements

  • The primary and secondary servers must be on the same subnet.
  • Both pool members must have static IPv4 addresses set on the network adapter. 
  • All pool members must be able to resolve the host names of all  additional pollers, additional websites, and the main Orion server. Pool members must also be able to resolve the host names of members in the same pool.
  • A virtual IP address must be available on the same subnet as the primary and secondary servers.
  • Port 5671 must be open between the primary and secondary servers in your pool.
  • TCP ports 4369 and 25672 must be open between the main and secondary server. They do not have to be open on additional polling engine pools.
  • Devices must be able to accept inbound connections from both pool member's primary IP addresses and VIP addresses.
  • Devices sending syslogs, SNMP traps, and NetFlow information to your main poller may be configured to send the information to the VIP address and receive requests from the pool.

You may need to modify firewall rules to allow traffic from pool members and to the VIP address.

Supported Orion Platform product modules

Supported products include:

  • Network Performance Monitor (NPM) 12.0.1 and later
  • Server & Application Monitor (SAM) 6.3 and later
  • Network Traffic Analyzer (NTA) 4.2.1 and later
  • Network Configuration Manager (NCM) 7.5.1 and later
  • IP Address Manager (IPAM) 4.3.2 and later
  • Engineers Toolset 11.0.3 and later
  • User Device Tracker (UDT) 3.2.4 and later
  • VoIP Network Quality Manager (VNQM) 4.2.4 and later
  • Storage Resource Manager (SRM) 6.3 and later
  • Web Performance Monitor (WPM) 2.2.1 and later

The following products can be integrated with your Orion Platform-based product. The integration module between products is protected by under SolarWinds High Availability, but the standalone product is not supported.

  • Storage Manager (STM) 6.2.3
  • Virtualization Manager (VMan) 6.3.2 and later
  • Firewall Security Manager (FSM) 6.6.8
  • Database Performance Analyzer (DPAO) 10.2 and later
  • Patch Manager 2.1.3 and later

Migrate the main polling engine pair to SolarWinds HA

To migrate to SolarWinds HA, you will uninstall FoE HA from your primary server. You should prepare a new secondary server for HA. SolarWinds HA supports HA servers for your main polling engine and additional polling engines.

 

Before you begin, you need the following:

  • The secondary HA server
  • An available HA pool license
  • An available IP address to use as the Virtual IP (VIP) address on the same subnet as the primary and secondary servers.
  • Open port 5671 (TCP) on the primary (incoming) and secondary (outgoing) servers.
  • Open ports 4369 and 25672 (TCP) on the main polling engine  primary and secondary server. These ports are not required when protecting additional polling engines.

As part of your migration to SolarWinds HA, you may need to upgrade your products. If you upgrade, the upgrade order must follow (1) main polling engine, (2) additional polling engines, and finally (3) additional web servers.

These instructions should be followed for all HA environments: physical to physical, virtual to virtual, and other variations.

1. Stop FoE services on the primary and secondary servers

Uninstall FoE from the primary server

Stop the FoE services on the primary and secondary servers.

Uninstall FoE from the primary server.

You can also remove the interfaces for the second network card. SolarWinds HA does not require or use a second network card for communication between the primary and secondary servers.

If you have an FoE pair for your additional polling engines, also uninstall FOE on that primary server.

2. VM: Delete the VM secondary server

Physical: Prepare a new secondary server

The secondary server should be built on the same subnet as the server you want to protect.

If you have a VM for your secondary server, delete the VM. Create a new VM for the secondary server.

If you have a physical for your secondary server, we recommend preparing a new secondary server. If you intend reusing the server, you must uninstall all Orion Platform products including FoE, wipe the computer, reinstall the OS, and reconfigure the hostname and IP address.

3. If needed: Upgrade Orion Platform product modules

SolarWinds HA is available in Orion Platform 2016.2. If you need to upgrade, complete the upgrades across your environment before creating the HA pool.

You may need to upgrade your Orion Platform products to use SolarWinds HA. Verify your upgrade path with the Product Upgrade Advisor. For full product upgrade steps, see the SolarWinds Upgrade Guide.

  1. Upgrade Orion Platform product modules on the main polling engine, primary server. You will set up the secondary server in step 4.
  2. Upgrade Orion Platform product modules on the additional polling engines.
  3. Upgrade Orion Platform product modules on the additional web server.

    SolarWinds HA does not support HA on additional web servers.

4. Setup the secondary server for HA
  1. Download and install the secondary server software. Click Settings > All Settings > High Availability Deployment Summary.
    Click Setup a new HA server.
  2. Activate your HA pool licenses.
  3. On the Setup a High Availability Server dialog, click Download installer now.
  4. Move the downloaded installer to your secondary server and run it. This software installs all product modules and exact configurations from the primary server to the secondary server.
5. Create the High Availability Pool
  1. In the Orion Web Console, click Settings > All Settings > High Availability Deployment Summary.
  2. Click Setup High Availability pool next to your standby server.
  3. Enter the pool name and the virtual IP (VIP) address.
    The VIP must be unassigned and on the same subnet as the primary and secondary servers.
  4. Click Create Pool to complete the pool setup.

Your main server or additional polling engine is now highly available and can failover to the standby server.
When the pool is created, the High Availability Deployment Summary displays the active and standby servers grouped under the pool name.
You may need to refresh the page to see the correct pool and server status.

You do not need to be online. The secondary server only needs access to the primary server in the LAN.

Learn more...

For additional information on requirements and settings, see the HA documentation.

Last modified
14:06, 17 Apr 2017

Tags

Classifications

Public