Pillar Axiom: Two Axioms Exhibit Warning Status but no Indications of Root Cause in Events or Hardware Monitor

Asset ID:	1-72-1476948.1
Update Date:	2017-04-01
Keywords:

Solution Type Problem Resolution Sure

Solution 1476948.1 : Pillar Axiom: Two Axioms Exhibit Warning Status but no Indications of Root Cause in Events or Hardware Monitor

Applies to:

Pillar Axiom Replication Engine (MaxRep) - Version 2.0 to 2.0 [Release 2.0]
Information in this document applies to any platform.

Symptoms

Warning status presented but nothing is indicated in the Event log or hardware Status Summary.

Changes

A recent upgrade of the MaxRep engine to version 2.04.

Cause

Heartbeat was lost to the replication engine.

Solution

Troubleshoot the communication link to re-establish the heartbeat communication.

There is a Readme reference for the MaxRep engine: 3.2.4 Heartbeat Monitoring

The Replication Engine registers Pillar Axiom systems using the Management Interface URL, which communicates directly with the Axiom Pilot. This communication link allows the Pillar Axiom MaxRep to use a system heartbeat to collect Replication Engine status, coordinate active and standby Replication Engine logs, and generate exception alerts.

If a heartbeat to a Replication Engine is lost, the status of the Pillar Axiom system changes to a Warning state.

Attachments

This solution has no attachment