To replace the OH_RCT5023_SERVER modules in an APPolo Server Cluster, you will need a spare Rack i.e RFR 5018 with Rack Controller i.e RCT 5023-G and follow the steps below.

Primary Server:

 

  1.  Place the first replacement OH_RCT5023_SERVER module in the RCT 5023-G.
  2.  Insert the RCT5023 in to the Spare Rack Frame, i.e., RFR 5018.
  3.  Connect the RCT5023 to a PC or Notebook running the latest GUI software.
  4.  Replace the default IP, Subnet Mask and Standard gateway of the new OH_RCT5023_SERVER with that of the primary/master server from the cluster under Settings TAB. 
  5.  In case the login credentials of Admin for the cluster are changed or different as per default, open a browser, type in the IP of the server and login using:
  6. User: admin | Password: lynx$admin under User Management.
  7.  Change the admin's password as in cluster.
  8.  Remove the OH_RCT5023_SERVER module from RCT 5023-G in the spare Rack.
  9.  Insert the OH_RCT5023_SERVER in the appropriate RCT 5023-G in the cluster.
  10.  Open the Connection Manager in GUI and right-click on the cluster (showing cluster error in red).
  11.  Click on Repair Cluster.
  12.  The Secondary Server will now become the Primary Server.


Secondary Server:


  1.  Place the second replacement OH_RCT5023_SERVER in the RCT 5023-G.
  2.  Insert the RCT5023 in to the Spare Rack Frame, i.e., RFR 5018. 
  3.  Connect the RCT5023 to a PC or Notebook running the latest GUI software. 
  4.  Replace the default IP, Subnet Mask and Standard gateway of the new OH_RCT5023_SERVER with that of the slave/secondary server from the cluster under Settings TAB. 
  5.   In case the login credentials of Admin for the cluster are changed or different as per default, open a browser, type in the IP of the server and login using:
  6. User: admin | Password: lynx$admin under User Management. 
  7.   Change the admin's password as in cluster.
  8.   Remove the OH_RCT5023_SERVER from RCT 5023-G in the spare Rack.
  9.   Insert the OH_RCT5023_SERVER in the appropriate RCT in the cluster.
  10.   Open the Connection Manager in GUI and right-click on the cluster (showing cluster error in red).
  11.   Click on Repair Cluster.
  12.   The Primary Server is now (again) the Secondary Server and vice versa.


 After the last step, the cluster must show the correct status in green.