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:
Primary Server:
- Place the first replacement OH_RCT5023_SERVER module in the RCT 5023-G.
- Instert the RCT5023 in to the Spare Rack Frame i.e RFR 5018.
- Connect the RCT5023 via USB to a PC or Notebook running the latest APPolo GUI software.
- Replace the default IP, SubnetMask and Standardgateway of the new OH_RCT5023_SERVER server with that of the primary server from the cluster under Settings TAB.
- 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
User: admin Password: lynx$admin under User Management. - Change the admin's password as in cluster.
- Remove the OH_RCT5023_SERVER module from RCT 5023-G in the spare Rack.
- Instert the OH_RCT5023_SERVER in to the appropriate RCT 5023-G in cluster.
- Open the Connection Manager in APPolo GUI and right - click on the cluster (showing cluster error in red).
- Click on Repair Cluster.
- The Secondary Server will now become the Primary Server.
Secondary Server:
- Place the second replacement OH_RCT5023_SERVER in the RCT 5023-G.
- Instert the RCT 5023-G in to the Spare Rack Frame i.e RFR 5018.
- Connect the RCT 5023-G via USB to a PC or Notebook running the latest APPolo GUI software.
- Replace the default IP, SubnetMask and Standardgateway of the new OH_RCT5023_SERVER with that of the primary server from the cluster under Settings TAB.
- 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
User: admin Password: lynx$admin under User Management. - Change the admin's password as in cluster.
- Remove the OH_RCT5023_SERVER from RCT 5023-G in the spare Rack.
- Instert the OH_RCT5023_SERVER in to the appropriate RCT in cluster.
- Open the Connection Manager in APPolo GUI and right - click on the cluster (showing cluster error in red).
- Click on Repair Cluster.
- 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.