Submit a ticketCall us

Don’t fall victim to a ransomware attack
Backups are helpful, but sometimes that’s not enough to protect your business against ransomware. At our live webcast we will discuss how to protect against ransomware attacks with SolarWinds® Patch Manager and how to leverage log data to detect ransomware. Register now for our live webcast.

Home > Success Center > Failover Engine (FoE) > Failover Engine 6.4.1 Release Notes

Failover Engine 6.4.1 Release Notes

Created by Beatrix.Turan, last modified by MindTouch on Jun 23, 2016

Views: 9 Votes: 0 Revisions: 3

Updated: 04/20/2011

These release notes provide additional guidance for SolarWinds Orion Failover Engine version 6.4.1

Features

The Orion Failover Engine is a versatile solution providing complete protection for your SolarWinds Orion products. It can be deployed in a LAN for high availability or across a WAN to provide disaster recovery. This flexibility enables the Orion Failover Engine to protect your installation of SolarWinds Orion standalone products and associated SolarWinds Orion modules.

Protection

Orion 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, Orion 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 Orion products and associated modules stay alive on the network.
Performance Protection
Proactively monitors system performance and notifies administrators of problems. The Orion 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.

FIPS Compatibility

SolarWinds Orion Failover Engine version 6.4.1 is now fully compatible with Federal Information Processing Standards (FIPS).

Supported Modules

Orion Failover Engine v6.4.1 supports the following modules:

  • SolarWinds Orion NPM MP v10.0 SP1, v10.1.1 SP1, and v10.1.2
  • SolarWinds Orion IPAM v1.7.1, and v2.0
  • SolarWinds Orion APM v3.5
  • SolarWinds Orion APM MP v4.0.1 and v4.0.2
  • SolarWinds Orion IPSLA Manager v3.5, and v3.5.1
  • SolarWinds Orion NTA v3.6 and v3.7
  • SolarWinds Orion NCM v6.0 and v6.1
  • SolarWinds Orion EOC v1.2 and v1.3

Supported Operating Systems

Orion 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 Standard or Enterprise

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

Supported Server Architectures

  • Physical to Physical (P2P)
    P2P architecture is used in environments where both the primary and secondary servers are physical servers. Using P2P limits installation options as it requires using the Install Clone technique. This architecture requires attention to detail when preparing for installation as both hardware and software must meet specific prerequisites. For more information, see "Physical to Physical (P2P)" in the SolarWinds Orion Failover Engine Installation Guide.
  • Physical to Virtual (P2V)
    The P2V architecture is used when the environment requires a mix of physical and virtual machines. The secondary virtual machine must meet the minimum requirements. For more information, see "Physical to Virtual (P2V)" in the SolarWinds Orion Failover Engine Installation Guide.
  • Virtual to Virtual (V2V)
    The V2V architecture is supported if SolarWinds Orion is already installed on the production (primary) server running on a virtual machine. The secondary virtual machine must meet the minimum requirements. For more information, see "Virtual to Virtual (V2V)" in the SolarWinds Orion Failover Engine Installation Guide.

Installing this Version

Prior to installing the Orion Failover Engine, SolarWinds recommends that you read the SolarWinds Orion Failover Engine Quick Start Guide or SolarWinds Orion Failover Engine Installation Guide and the SolarWinds Orion Failover Engine Administrator Guide for step-by-step guidance on installing and configuring your Orion Failover Engine. You must verify that your server environment meets the minimum requirements for the network option (LAN or WAN) selected. These guides also address minimum hardware and software requirements for this release.

To install the Orion Failover Engine:

  1. Review the installation procedure listed in the SolarWinds Orion Failover Engine Installation Guide.
  2. Ensure the environment meets the minimum requirements outlined in the SolarWinds Orion Failover Engine Installation Guide. Verify that firewalls in use will not prevent communications between the primary and secondary servers via the SolarWinds Channel.
  3. Identify installation options.
  4. Download the software.
  5. Install Orion Failover Engine software on the primary server.
  6. Install Orion Failover Engine software on the secondary server.
  7. Allow the secondary server to reboot and run Plug-n-Play.
  8. Perform the Acceptance Verification testing listed in the SolarWinds Orion Failover Engine Quick Start Guide.

Notes:

  • SolarWinds does not support installing SQL Server on the same host as the Orion Failover Engine. If SQL Server is installed on the same host as Orion Failover Engine, IIS services cannot be stopped or started and therefore switchover and failover processes will fail.
  • Installation time for the Orion Failover Engine can vary depending on the installation technique, architecture, and the volume of data to be protected. SolarWinds recommends that you install Orion Failover Engine after hours or during a scheduled maintenance period.
  • Installing Orion Failover Engine when logged on as a domain user and member of the local machine's Administrator group causes Orion Failover Engine to fail to start on the secondary server. Ensure the user is logged in as the Domain Administrator to prevent this from occurring. For more information, see "Installing Orion Failover Engine when Logged On as a Domain User and Member of the Local Machine's Administrator Group Causes Orion Failover Engine to Fail to Start on the Secondary Server" (SWREFID-2251).
  • The path of the SolarWinds installation folder, Orion Failover Engine, and any protected applications can only contain lower and upper case letters A to Z, digits from 0 to 9, and the following special characters: [space] \ _ - ( ) . :
  • When configuring management IP addressing, ensure that the management IP address is configured in a different subnet than the principal IP address. If configuring management IP addressing on a Windows Server 2003 installation, ensure that the management IP address is listed first in the binding order. For more information about management IP addressing, see "Management IP Address" in the SolarWinds Orion Failover Engine Administrator Guide.
  • If you are installing an Orion Failover Engine on a web server, you must edit the Website Availability and Website Response Time rules located on the SolarWinds Orion Failover Manager > Applications > Rules page to reflect the monitored web site. Ensure that you change the default settings for http://localhost:80 to reflect the IP address and port of the monitored site.
  • In the event that you must repair a SolarWinds Orion NPM module with Orion Failover Engine installed, follow the procedures outlined in "How to Repair a SolarWinds Orion Module with Orion Failover Engine Installed" (SWREFID-2060).

Uninstalling

To uninstall an Orion Failover Engine, use the Uninstall or Modify icon on the desktop to initiate the uninstallation process.

Notes:

  • Windows 2008 users with UAC Enabled may require an administrator account login to initiate an uninstallation. Disabling UAC for the duration of the uninstallation will bypass this.
  • After uninstalling an Orion Failover Engine, some files and folders will remain. These remaining files and folders are logs, and they should not be removed, as they may be required later for support or troubleshooting purposes.

Fixed Issues

The following issues from previous versions of Orion Failover Engine have been fixed.

  • Changes made to the web console port number or IP address are not replicated to the passive server. The Orion Web Console is not accessible from the passive server. You must manually edit the URL to include the correct new port number or IP address.
  • When Orion Failover Engine is installed in an environment with a German version of Microsoft Windows Server 2003, the %ALLUSERSPROFILE%\Application Data\SolarWinds folder is not included in the replication file filters. Manually create an inclusion file filter for %ALLUSERSPROFILE%\Application Data\SolarWinds\** to ensure that the folder is replicated.
  • False Application Warnings in the SolarWinds Failover Manager Event Log are no longer recorded. These Application Warnings provided the following Details:
    Could not retrieve counter name Neverfail Heartbeat Compression Manager\DataVolSinceInit while trying to update counter value.
  • When the SolarWinds Orion Configuration wizard runs, it routinely sets services to Automatic, including protected application services, thereby preventing the Orion Failover Engine from managing the starting and stopping of protected application services. With this release, the Orion Failover Engine resets protected application services to Manual automatically, withot requiring a manual restart of the protected server.
  • False Application Warnings occurring after the switchover of a server running IP Address Manager are no longer recorded. These Application Warnings provided the following Details:
    Rule Triggered Website is not available. Too many automatic redirections were attempted: http://localhost.

Known Issues

The following issues may arise in your installation of an Orion Failover Engine. These are known issues that are being addressed for a future release.

  • Firewalls protecting the SolarWinds Channel must be disabled prior to installing an Orion Failover Engine to allow communication between the primary and secondary servers. For additional information, see "Firewall Connection" in the Troubleshooting chapter of the SolarWinds Orion Failover Engine Administrator Guide.
  • Restarting an Orion Failover Engine server without first shutting down the Orion Failover Engine may cause the server to return in the passive role. You must allow the Orion Failover Engine to shut down gracefully prior to restarting Windows. For more information, see the chapter "Status and Control" in the SolarWinds Orion Failover Engine Administrator Guide.
  • When an Orion Failover Engine is deployed in an environment where the primary server has a different principal IP address than the secondary server, as in a WAN or stretched LAN configuration, the Orion Web Console is unavailable after a switchover or failover. This occurs because the principal IP address of the active server changes as the result of a switchover or failover in a WAN or stretched LAN environment and the web console is not automatically updated to point to the new IP address. For each of the Orion NPM, Orion NCM, and Orion EOC modules that is installed, you must run the corresponding Website Configuration Manager and set the IP Address to (All Unassigned).
  • When starting the Orion Failover Engine, you may safely ignore the following warning:
    Sponsor 'FoE' was not found in the list of ordered sponsors.
  • After a switchover of the Orion Failover Engine, attempting to run a job task may result in the following error message:
    No suitable job engine available for job execution
    Verify that the principal NIC is listed first in the binding order, and then wait 5 minutes before running the job task again. The job task should complete successfully.
  • After a switchover of the Orion Failover Engine, new Orion NCM jobs created before the switchover are disabled on the new active server. To create NCM jobs on the new active server, navigate to the Scheduled Jobs window in Orion NCM, and then specify schedules and add appropriate account information again.
  • SolarWinds Orion Failover Engine Management Client Online Help is only supported on Microsoft Internet Explorer v6.0 and later and Firefox v3.0 and later.
  • Immediately after installation using the Pre-clone install technique or after manually changing the roles of the servers regardless of the installation technique, the SolarWinds Orion Module Engine service fails to stop on the passive server. Reboot the passive server to stop the SolarWinds Orion Module Engine service on the passive server.
  • If a failover or switchover occurs immediately after upgrading the license of any SolarWinds Orion product, license data may not replicate fully from the primary server to the secondary server, resulting in license file corruption. SolarWinds recommends that you wait a number of minutes before performing a switchover after upgrading a SolarWinds Orion product license.
  • After restarting the Primary or Secondary server and using the System Tray on that server to start vCenter Server Heartbeat, the System Tray application may fail.
    Workaround: Restart the System Tray application using the Start System Tray icon on the desktop.
  • Installation/loading of the SystemMonitorNFPlugin.dll fails to an incorrect path.
    Workaround: Remove the SystemMonitorPlugin and reinstall using the steps provided in "During Installation Using the Install Clone Technique the SystemMonitorNFPlugin Fails Due to Incorrect Path" (SWREFID-2245).
  • When IPAM 2.0 Standalone is installed, using SolarWinds Configure wizard resets the Syslog and Trap services to Automatic startup.
    Workaround: Reset the Syslog and Trap services to Manual startup using the procedure provided in "Running SolarWinds Configuration Wizard when IPAM 2.0 Standalone is Installed Causes the Syslog Service and Trap Service to be Protected by Orion Failover Engine" (SWREFID-2249).

Legal

Last modified
19:28, 22 Jun 2016

Tags

Classifications

Public