Submit a ticketCall us

Announcing NCM 7.7
With NCM 7.7, you can examine the rules that make up an access control list for a Cisco ASA device. Then you can apply filters to display only rules that meet the specified criteria, order the rules by line number or by the hit count, and much more.
See new features and improvements.

Home > Success Center > Failover Engine (FoE) > Failover Engine installation while there are outstanding issues with existing modules

Failover Engine installation while there are outstanding issues with existing modules

Table of contents
Created by Daniel Polaske, last modified by MindTouch on Jun 23, 2016

Views: 8 Votes: 0 Revisions: 3

Overview

This article discusses how to handle SolarWinds Failover Engine installations when there are outstanding issues with other modules in the environment. 

Environment

All FOE versions

Detail

In most cases, it is highly advised to resolve any outstanding issues with other modules before continuing with a Failover Engine installation. As in most cases, it is likely that the problem will be replicated to the secondary Failvoer Engine.  Exceptions to this would include an issue solely with the Orion database, or other very specific exceptions. However, SolarWinds highly recommends you to inform your Solarwinds Support agent of any outstanding issues. They will be able to advise you whether the issue can be temporarily ignored or if the Failover Engine installation should be postponed.

 

Last modified
19:27, 22 Jun 2016

Tags

Classifications

Public