Cluster Move Procedure to New Site - Change Cluster IP Address

This procedure is used to move a cluster to a new site and failover, failback and a change of the Cluster IP address is required at the new site.

Steps need to follow while moving one cluster to a new site:

Shares or exports exist on active cluster (writeable data) and on the read only cluster (Cluster B)
Failover one policy or access zone at a time to the target cluster (Cluster B)

Expected Result: Clients and applications are successfully accessing data from the new active cluster (Cluster B)

Completes without error
Shares and exports now exist on new active cluster (Cluster B) on the new read only cluster (cluster A)

Disable all Eyeglass jobs
Move source (Cluster A) to new site
Change IP address on Cluster A
Bring source (Cluster A) back online
Change source (Cluster A) IP address from Eyeglass inventory view using the below procedure:

How to - Edit PowerScale IP Address in Eyeglass

Eyeglass jobs should all be enabled at this step. Confirm this is the case.

Expected Result: Eyeglass Configuration Replication Jobs are running without error

Note : If Eyeglass Configuration Replication Jobs are in error proceed to Step 11 to reset Eyeglass to pick up IP address changes for Jobs on the new active cluster (Cluster A)

Fallback one policy at a time or access zone to the source (Cluster A)

Expected Result: Clients and applications are successfully accessing data from the new active cluster (Cluster A)

Note : If Eyeglass Replication Jobs are in error proceed to Step 11 to reset Eyeglass to pick up IP address changes for Jobs on the new active cluster (Cluster A)If the Eyeglass Configuration Replication Jobs and Fallback is working successfully on new active cluster (Cluster A) are working then the relocation procedure is complete.
If Eyeglass Replication Jobs are in error reset Eyeglass to pick up IP address changes for Jobs on the new active cluster (Cluster A) with the following procedure:

SSH to Eyeglass appliance using admin: sudo -s enter (must use root) then use admin password (default password: 3y3gl4ss)
Run command <igls appliance rediscover>
Once reset completes, go to the chrome browser and refresh the browser and login with the credentials
Login to jobs window and validate that all jobs are in the correct states, Eyeglass will restore all job status but should be double checked,

Correct any if jobs in user disabled state or not in DFS state that should be DFS enabled.
IMPORTANT: You must enable DFS mode on an job that did not rediscover and shows in the DFS job section of jobs window before enabling the Job to prevent creation of active shares on target cluster. Enable DFS mode first, then enable.

Using Bulk Actions select a policy in jobs window and use Run now.

Using Running jobs tab to watch and verify successful (check mark no red X) on the configuration sync

If using Access Zone failover, verify that failover readiness job is enabled.

Using bulk actions force run the readiness job wait until it completes (running jobs window)

Check DR Dashboard to verify it shows a good DR status