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 > Network Performance Monitor (NPM) > Orion DB on SQL AlwaysOn Cluster does not reconnect after failover

Orion DB on SQL AlwaysOn Cluster does not reconnect after failover

Created by Robert Stidman, last modified by Aileen de Lara_ret on Sep 06, 2016

Views: 226 Votes: 0 Revisions: 3

Overview

Some users have an AlwaysOn cluster with the Orion DB as a resident DB. Everything works on Node A of the AlwaysOn cluster, but when users failover to Node B SolarWinds reports an error.
If users re-run the Configuration Wizard, they can get Node B of the AlwaysOn cluster to work, but then failover back to Node A fails.

Environment

All Orion Core products

Cause 

Limitations in how we deal with SQL AlwaysOn.

Resolution

User can try to bypass Orion limitation by setting up DNS alias which points to the currently active SQL instance.
This way DNS alias will be passed to Config Wizard rather than physical instance or Availability Group listener.

 

 

 

 

Last modified
20:37, 5 Sep 2016

Tags

Classifications

Public