Pillar Axiom Replication Engine (MaxRep)
 

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

In this Document

Goal

Solution

Applies to:

Goal

 To provide detailed instructions on how to gracefully shutdown an Oracle MaxRep3 Engine.  Most often this will be used in preparation for any service activity that must be done offline.

Solution

The shutdown can only be executed from the MaxRep3 Engine that is running the Control Services.  Access to the MaxRep3 User and Support interfaces will use the admin user login.  The factory default password for this user is password and is changeable by the customer.

1. Log into the MaxRep3 User Interface of the MaxRep3 Engine running Control Services or HA Cluster IP  to review the current status
   
   1. Point a browser at the MaxRe3 Engine's fq-name or IP address followed by "/ui":
      10.0.0.10/ui
        
   2. From the Monitor tab, note the status of:
      
      • Protection Plans
      • Control Service
      • Process Service
        
        
        
        Note: this notation is only to establish the status of the MaxRep3 Engine prior to shutdown. Any non-optimal status may be the result of a problem for which the MaxRep3 Engine is being shutdown. If you have doubts please contact Oracle Support.
         
        
   3. Log out of User Interface
      
      
2. Log into the Support Interface of the MaxRep3 Engine running Control Services or HA Cluster IP
   
   1. Point a browser at fq-name/IP address of the MaxRep3 engine followed by /support:
      
      10.0.0.10/support
       
   2. Under Management Tasks, select Shutdown/Restart Services
   3. Using the Host pull-down menu, select the MaxRep3 Engine you want to shutdown
   4. Beside Action, select Shutdown
   5. Save the Task
      
      
      The screen will change to a task list where the shutdown will be in pending and after about 1 minute will update to In Progress. As the shutdown completes, this interface will time out as web services will be shutdown as well.
      
      
      Note: In the Oracle FS System Manager GUI, the Overall System Status will change to Warning because of the MaxRep3 Engine being shutdown.
       
      Service actions may now take place.  Once completed, and power is restored, the MaxRep3 Engine will take 4-5 minutes to reboot.
      
      
3. Once theMaxRep3 Engine is again accessible via the User Interface, check the status:
   
   1. Log back into the User Interface and note any resyncs needed for Protection Plans.
   2. Select the Protect tab and on the left side under Oracle Storage, select Manage Protection Plan.
   3. For each Protection Plan needing a resync, select the Modify link in the Action table.
      
      
      
   4. On the Restart Resync line, select Click Here.
      
      
      
   5. In the Restart Resync screen click on Restart Resync and OK in the pop-up.
   6. Repeat for other Protection Plans needing a resync.
      
      
      
4. Resync progress can be monitored via the Monitor tab and select the Protection Plan.  Once the Status updates to "Resyncing (Step I)", the Resync progress will be displayed in percentage form:
   

This solution has no attachment