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 > Failover Engine (FoE) > Orion Failover Engine Installation Prerequisites

Orion Failover Engine Installation Prerequisites

Created by Steven Bansil, last modified by Allain M Umalin on Sep 12, 2016

Views: 2 Votes: 1 Revisions: 6

Overview

This article provides hardware and software prerequisites for installing Orion Failover Engine (FoE).

Environment 

  • FoE all versions

Notes

  • The server to be protected by Orion Failover Engine can NOT be configured as a domain controller, global catalog, DHCP or DNS server. These roles and services must be removed before proceeding with installation.
  • SQL Server should not be installed on any protected server. 
  • SolarWinds strongly recommends that you perform your product trial within a test lab environment, as we do not provide installation or product support for trial evaluations. Orion Failover Engine is not responsible for trial software installed in a production environment.

Hardware Requirements

For Primary Server:

  • Must meet Microsoft's requirements for one of the following installed operating systems:
    • Windows Server 2003 x86 and x64 Standard / Enterprise / R2 with SP1 or SP2
    • Windows Server 2008 x 86 and x64 Standard / Enterprise with SP1 or SP2
  • 1 GB RAM minimum, 2 GB RAM recommended
  • 2 GB of available hard disk space
  • Network interface cards: 2 non-teamed NICs required, 3 non-teamed NICs recommended
  • Multiple hard disk drives are recommended as per application vendors' requirements. Avoid locating the operating system, database, and log files on the same disks

 

For Secondary Server:

  • Must meet Microsoft's requirements for one of the following installed operating systems:
    • Windows Server 2003 x86 and x64 Standard / Enterprise / R2 with SP1 or SP2
    • Windows Server 2008 x 86 and x64 Standard / Enterprise with SP1 or SP2
  • 1 GB RAM minimum, 2 GB RAM recommended
  • Total hard disk space should be greater than or equal to the Primary Server
  • Same number of NICs as the Primary Server
  • Hard drive lettering scheme must match the primary server (although underlying hardware may be different)

Software Requirements (for both Primary and Secondary Servers)

  • Installed operating system:
    • Windows Server 2003 x86 and x64 Standard / Enterprise / R2 with SP1 or SP2
      or
    • Windows Server 2008 x 86 and x64 Standard / Enterprise with SP1 or SP2
  • Latest Microsoft security updates
  • Installation of Orion Failover Engine requires local admin rights
  • Operating system version, service pack version and security updates must match the primary server
  • Operating system must be installed to same drive letter and directory as the primary server
  • ACPI compliance must match the primary server
  • Primary and secondary servers must have identical hostnames
  • Setup in a workgroup
  • The same Windows IIS components must be installed as the primary server. Once installed, set each of these component services to have the same startup type as the primary server (automatic, manual or disabled)
  • System date/time and time zone consistent with primary server
  • Additional applications, including the protected application, must NOT be installed on the secondary server (doesn't apply to V2V deployment)
  • SQL Server should not be installed on the same machine as Orion Failover Engine.

Networking Configuration

Primary Server

Principal network connections configured with:

  • Static IP address
  • Correct network mask
  • Correct gateway address
  • Correct DNS server addresses

SolarWinds Channel network connections configured with:

  • Static IP address (in a different subnet from the principal network)
  • Correct network mask
  • No gateway IP address
  • No DNS server addresses
  • In a LAN environment, a cross-over cable should be used to connect the SolarWinds Channel connections on the primary server to the SolarWinds Channel connections on the secondary server
  • In a WAN environment, persistent static route(s) must be configured to the SolarWinds Channel connections on the secondary server. See SWREFID - 1961 for more information. 

 

Secondary Server

SolarWinds Channel network connections configured with:

  • Static IP address (in a different subnet from the principal network)
  • Correct network mask
  • No gateway IP address
  • No DNS server addresses
  • File and Print Sharing enabled
  • In a WAN environment, persistent static route(s) must be configured to the SolarWinds Channel connections on the primary server. See SWREFID - 1961 for more information.

Login Account Privilege Requirements

Administrator privileges required for login accounts vary according to configuration:

  • For installation and normal system administration, a login account with Local Administrator privilege must be used. This account may also be a domain administrator if login with cached credentials is permitted by the security policy.
  • For installation of the secondary server, which is not already a clone of the primary server, a local administrator account is required for installation.
  • For WAN installations, where the principal IP addresses differ between servers, the administrator account used must additionally be a member of the DNSadmin group. Domain Administrator accounts have sufficient privilege to meet this requirement.
Last modified
06:30, 12 Sep 2016

Tags

Classifications

Public