Pillar Axiom Replication Engine (MaxRep)
 

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

In this Document

Symptoms

Cause

Solution

References

Oracle Confidential PARTNER - Available to partners (SUN).
Reason: Manual manipulation of configuration files in the MaxRep Engine.
Created from <SR 3-10789188731>

Applies to:

Symptoms

 During in initial installation of MaxRep 3.x customers may encounter a condition where the Task Status gets stuck at "In Progress"

Cause

When this occurs, the most probable cause is a timing issue.  For example: Before the process closes out, the network interface is restarted.  And if said process is waiting for a response before continuing, it may never arrive.  This results in the process getting stuck "In Progress".

Solution

There are currently two possible solutions for this issue.  Both involve accessing the MaxRep Engine Console via the network and manually editing files on the MaxRep Engine.  Please be certain to make a backup copy any file before making these edits as in some cases, the original file will be gone after a reboot.

Accessing the MaxRep Engine Console via network

It is assumed that the ILOM network part (NET MGR on the rear) of the MaxRep3 Engine has been properly configured.  Please refer to the Oracle MaxRep 3 Hardware Guide for details.  The Hardware Guide also contains default login/password information needed for this task.

1. Point a browser at the ILOM IP address
2. Log into the ILOM using ILOM default login/password.
3. From the Actions box, launch Remote Console and click through (run/continue) the pop-ups.
   
   
   
   
4. If you get a remote console window, skip to step 7.
5. If you get a Java security error and cannot continue, you will need to add a security exception to Java:
   
   1. From Start, select All Programs, Java, Java Configuration.
   2. In the pop-up window, select the Security tab and then Edit Site List...
   3. In the new pop-up window, add an exception in the following format:https://ILOM_IP_ADDRESS:443" and  then OK.
   4. Confirm entry in the list and click OK again.
   5. In your browser, log out and then log back into the ILOM and relaunch the Remote Console.
      
      
6. If you get a Video Redirection Error message for "No appropriate protocol", please refer to <Document 1968537.1> Cannot Use ILOM Remote Console When SSLv3 is Disabled in Java.
7. Log into the MaxRep3 Engine with the default login/password.

Method #1 (use only if MaxRep Engine has been re-imaged):

1. cd /usr/local/MaxRep
2. cp final_mfg_shutdown_prep.sh final_mfg_shutdown_prep.sh.orig
3. Edit final_mfg_shutdown_prep.sh and update the line of DEFAULT_IP="10.0.0.11" with the new MaxRep3 Engine IP
4. Run the script final_mfg_shutdown_prep.sh
5. Reboot the MaxRep3 Engine: "reboot now"
6. Once MaxRep Engine is back up, ping the new IP address.  If ping works, attempt to access the GUI.
7. If ping does not work or the GUI is still inaccessible, continue to Method #2.

 Method #2 for Single MaxRep Engine configurations:

1. For each of the following files, make a backup copy, then edit to update with the MaxRep3 Engine IP address (IP_ADDRESS):
   
   Pay close attention to character spacing and double quotes!
   
   
   
• FILE: /home/svsystems/etc/amethyst.conf
  Variable: CS_IP = "IP_ADDRESS"
  Variable: PS_CS_IP = "IP_ADDRESS"
  
  
• FILE: /usr/local/InMage/Vx/etc/drscout.conf
  Variable: Hostname = IP_ADDRESS
  
  
• FILE: /usr/local/InMage/Fx/config.ini
  Variable: SVServer = IP_ADDRESS
  
  
• /home/svsystems/etc/pushinstaller.conf
  Variable: Hostname= IP_ADDRESS
  
  
•  /home/svsystems/system/etc/system.conf
  Variable: SYSTEM_IP = "IP_ADDRESS"
  
  
2. Restart the network services by issuing the following command:
   
   # service network restart

Method #2 for Multiple MaxRep Engine configurations:

1. In MaxRep configurations with multiple Engines, there are two IP addresses to consider.  There is the Process Service IP address (PS_IP_ADDRESS) which is the IP address that is unique to that Engine.  There is also the Control Service (CS_IP_ADDRESS) which is the IP address of the MaxRep Engine that is the configuration server of the installation.  For each of the following files, make a backup copy, then edit to update the MaxRep3 Engine IP addresses with the appropriate IP address based on your configuration:
   
   Pay close attention to the character spacing and double quotes!
    
   
   
• FILE: /home/svsystems/etc/amethyst.conf
  Variable: CS_IP = "PS_IP_ADDRESS"
  Variable: PS_CS_IP = "CS_IP_ADDRESS"
  
  
• FILE: /usr/local/InMage/Vx/etc/drscout.conf
  Variable: Hostname = CS_IP_ADDRESS
  
  
• FILE: /usr/local/InMage/Fx/config.ini
  Variable: SVServer = CS_IP_ADDRESS
  
  
• /home/svsystems/etc/pushinstaller.conf
  Variable: Hostname= PS_IP_ADDRESS
  
  
•  /home/svsystems/system/etc/system.conf
  Variable: SYSTEM_IP = "PS_IP_ADDRESS"
  
  
2. Restart the network services
   
   
   1. From the GUI support interface:
      
      Management Tasks -> Shutdown/Restart Services -> Restart Replication Services
      
      
   2. From the command line issue the following commands:
      
      # service network stop
      # service tmanagerd stop
      # service vxagent stop
      # service svagent stop
      # service cxpsctl stop
      # service cxpsctl start
      # service svagent start
      # service vxagent start
      # service tmanagerd start
      # service network start

Once all is working correctly, you can remove the Java security exception created in step 5 of the "Accessing the MaxRep Engine Console via network" section.

References

This solution has no attachment