Sun Microsystems, Inc.  Sun System Handbook - ISO 4.1 October 2012 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-1476948.1
Update Date:2012-09-24
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  


Related Items
  • Pillar Axiom Replication Engine
  •  
Related Categories
  • PLA-Support>Sun Systems>DISK>Pillar Axiom>SN-DK: MaxRep
  •  




In this Document
Symptoms
Changes
Cause
Solution


Created from <SR 3-5975712038>

Applies to:

Pillar Axiom Replication Engine - Version Not Applicable to Not Applicable [Release N/A]
Information in this document applies to any platform.

Symptoms

 Warning status presented but nothing is indicated in the Event or Hardware.

Changes

 A recent upgrade to 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 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
  Copyright © 2012 Sun Microsystems, Inc.  All rights reserved.
 Feedback