Submit a ticketCall us

Training ClassSign up for Network Performance Monitor (NPM) and Scalability instructor-led classes

Attend our instructor-led classes, provided by SolarWinds® Academy, to discuss the more advanced monitoring mechanisms available in NPM as well as how to tune your equipment to optimize its polling capabilities. NPM classes offered:
NPM Custom Monitoring and Polling
Orion Platform Scalability

Reserve your seat.

Home > Success Center > Archive > 2018April16 - Deletes > Failover Engine (FoE) > How to Configure Orion Failover Engine to Use a Different Principal IP Address

How to Configure Orion Failover Engine to Use a Different Principal IP Address

Table of contents
This article is slated for Deletion. Do not update this article. If you have questions please send a message to

Created by Mindy.Kerber, last modified by MindTouch on Jun 23, 2016

Views: 878 Votes: 0 Revisions: 3


This Knowledge Base article provides the procedure to change the Orion Failover Engine principal IP address settings using the Server Configuration wizard.



All FOE versions


To change the principal IP address settings on a Orion Failover Engine server, follow the steps below: 

  1. Shutdown Orion Failover Engine using the SolarWinds Orion Failover Manager. Click on Shutdown.   
  2. Open the Server Configuration wizard by navigating to Start Programs SolarWinds Orion Orion Failover Engine > Configure Server, and then select the Public tab.
  3. The wizard should be run locally on both the primary and secondary servers in order to specify new principal IP addresses on each server so that they can communicate with each other when restarted.

    You can configure your server with one or more principal IP addresses.  These are the addresses by which clients will connect to the protected application. Typically, there will only be one principal IP address. You configure all of the principal IP addresses on both the primary and secondary servers.   On the passive server, all traffic to and from the principal IP addresses is blocked.  On the active server, all traffic is passed through.  When the role of the servers is switched, the IP filtering mode also switches, so client systems always connect to the principal IP addresses on whichever server is currently active.  When the Orion Failover Engine service is shutdown, the filtering remains in place so you do not get IP address conflicts between the two servers.

In the principal IP address table, you list all of the addresses that will be used as principal IP addresses. Add a new row by clicking the Add Row icon to the left of the table and delete unwanted rows by clicking the Delete Row icon. Clicking the Trash can icon will delete the entire contents of the table. Select the Reset button to return to the original settings if required. An address should not appear more than once, and the principal IP addresses listed should not be the same as any of the IP addresses listed in the Channel panel.

  1. Once you have made your changes click Finish to apply the new settings.  
  2. After starting Orion Failover Engine, switchover and perform a client connection test. 

Networking Hint

The principal addresses configured for the primary and the secondary server must be identical. Any other 'private' addresses configured for primary or secondary network cards must be different.   If you configure your network cards with a 'private' address in the same subnet as any of the principal addresses, check the routing tables to ensure the subnet is reachable when the principal IP traffic is blocked. Use the route print command to list the routing tables.  If the principal address appears as the gateway for its subnet, then you may not be able to use other addresses on the same subnet when the IP traffic to the principal address is blocked, for example you may get no response when you ping the 'private' address from another machine.  To fix this, reorder the IP addresses using the system's Network Connections window. The IP address at the top of the list is the one through which all traffic is routed.




Last modified



Internal Use Only