Pillar Axiom Replication Engine (MaxRep)
 

PLA-Support>Sun Systems>DISK>Axiom>SN-DK: MaxRep-2x
 

In this Document

Symptoms

Changes

Cause

Solution

References

Oracle Confidential PARTNER - Available to partners (SUN).
Reason: Interna/Partnerl only how to
Created from <SR 3-13017645831>

Applies to:

Symptoms

User receives email alerts about an agent that is no longer configured for MaxRep and cannot be stopped.

Example:

Subject: Replication Engine Alert - [xx.x.x.x ( mr1-maxrep ) ]
File Agent down: <FlashStorageSystem.Company.COM>:
No communication from File Agent on <FlashStorageSystem.Company.COM>
since more than 900 seconds. No Jobs Affected.
Number of occurrences: 46842 time(s) between 2016-01-27 20:09:47 and
2016-07-14 15:14:29

When logging into the MaxRep3 Engine, the following Alert will be seen:

Changes

MaxRep configuration changes to host agent.

Cause

A Host Agent that was pointed to one MaxRep Engine is now pointing to another MaxRep Engine.

Solution

1.  Log into the MaxRep User Interface (UI), which has the stale host entries: http://<IP_Address>/ui
2.  Click on "Monitor" tab and then "Agent Heartbeat" under Protection Status in the navigation tree on the left.
3.  Locate the FS1 that was logging the messages:
   
   
   
4.  Using the hidden URL of http://<IP_Address>/ui/unregister_host.php, delete the stale host entry by selecting the radio button on the far left and then Unregister:
   
   
   
   
   Note: This will delete the entries from the MaxRep database. Any deletion which involves DB updating needs to be handled by engineering ONLY in order to avoid further issues.
   
   
   
   Note: Do not attempt to use Document 1473445.1 Pillar Axiom: How to Remove a "Stale" MaxRep Host Agent Record.  This document is specific to the MaxRep2 Engine.

References

This solution has no attachment