Limitations When Using HA

To use the High Availability feature, the following limitations will be applied:

LimitationsDescription

Synchronization of the data stored in High Performance Database Collections and Summaries is NOT supported.

High Availability does not include synchronization of the data stored in the High Performance Database Collections or Summaries. Users will have partial data on the High Availability pair and will need to organize the database content to be summarized elsewhere.
Synchronization of Preserving Alert State on Restart is NOT supported.High Availability does not include synchronization of the preserved alerts in the Prognosis product. Alerts will re-trigger when switching the High Availability Pair roles.
High Availability is ONLY supported on the Microsoft Windows platform.Currently, High Availability is only available on the Microsoft Windows platform with no support for other platforms.
Multi-homed Nodes servers are currently NOT supported.High Availability will synchronize the NETWORK Configuration by default when a High Availability pair is linked. When a switchover occurs in this case, the multi-homed node settings will be applied on both servers in the High Availability pair causing connection issues.
The version on a HA Pair must be the same when Linking and Unlinking the HA Pair.The Linking and Unlinking of a High Availability pair can only be performed on Prognosis Servers with the same major.minor version.
Path Insight is NOT supported.
SQL Reporting Solutions is NOT supported.Handling for Store and Forward (SAF) data for a High Availability pair is not covered.

High Availability does not support Store and Forward Facility (SAF) for Database Collections for cross-node Availability monitoring.

Handling for Store and Forward (SAF) data for a High Availability pair is not covered.

Web Application features Navigation Page:

  • Navigation tree change
  • Navigation View settings
  • Customized dashboards
  • Customized background/persistent views
  • Mashup and Key Displays

are NOT supported.

Handling these WebUI settings for a High Availability pair is not covered.

High Availability does not support the Windows Client.

The handling of the Windows client is not covered.

Configuration Item Mapping will need to be setup to ensure Alerts will be sent to top-level nodes for processing.

Following the Configuration Item Mapping documentation, multiple Publishers can be defined in the irautoan.ini file under the configuration folder. The publishers must match the ones configured in the MESSAGING Configuration Syntax.

High Availability is supported for the internal PostgreSQL database only when PostgreSQL is installed on the local server.

PostgreSQL replication changes are only applicable on the local instances. Customers using an external PostgreSQL database cluster when using High Availability feature must manage their database clusters independently of Prognosis.

When monitoring any Cisco Application clusters for High Availability, the High Availability pair MUST be installed with the same <Prognosis_Home> path.

The Cisco Application cluster setup scripts will contain the full Prognosis path.

Changing the Prognosis node name is NOT supported in High Availability.

The Prognosis node name must match the Windows machine name.
High Availability will NOT support long Prognosis node names that have identical first 30 characters.All Prognosis Nodes used in a High Availability Pair must have the first 30 characters of the Prognosis Node name unique, this limitation is across all configured HA Pairs in the system. Prognosis Node names may be longer, however uniqueness must be in the first 30 characters.
High Availability Pairs must be running the latest patch version.Improvements to the High Availability solution will be deployed as patches to supported Prognosis versions. Ensure that all High Availability servers are updated to the latest patch version so the Management Server can monitor and enact changes on the HA Pair.
High Availability does NOT support Offboard Nodes

Monitoring Servers with attached UC configured nodes, called offboard nodes, are not supported with the High Availability solution and may result in UC connectivity issues on Managing Servers. Offboard nodes are non-server nodes as shown in the Nodes Navigator.

For instructions on how to recover in this scenario, please refer to Unplanned Outage Recovery for a HA Pair when Auto-Failover is disabled.

Provide feedback on this article