Change PowerScale IP Address

Introduction

Changing the IP address of a PowerScale cluster that is managed by Eyeglass requires careful handling to avoid service disruption or configuration mismatch. This guide walks you through the necessary steps to update the IP address in Eyeglass safely.

The process includes disabling configuration replication, updating the SmartConnect Service IP, verifying communication, and restoring normal operations. These actions help ensure that Eyeglass continues managing cluster configuration and failover functionality without interruption.

Change PowerScale IP Address

important

During this procedure, there will be an Eyeglass service interruption. Any configuration items added, updated, or deleted on the source will not be synchronized to the target until the procedure is completed.

1. Prepare Eyeglass for the IP address change by disabling configuration replication.

   Disable from Eyeglass UI

   1. Log into the Eyeglass web page.

   2. Click Jobs to open the Jobs module.

   3. Select all configuration replication jobs. You can use the checkbox at the top of the Job Name column.

   4. Scroll down the job list and confirm that all jobs have the state User Disabled.

      note

      If a job is already in Policy Disabled state because the related SyncIQ policy is disabled, it will remain in this state. Eyeglass also does not run configuration replication for jobs that are Policy Disabled, so this state is acceptable to proceed with the Edit IP address procedure.

   5. Click Select a bulk action.

   6. Select Disable.

   Disable from Command Line

   Alternatively, wait for all running Configuration Replication jobs to finish, then run the following command on the Eyeglass Appliance:

   igls admin schedules set --id Replication --enabled false

2. Change the IP Address on the PowerScale Cluster itself.

3. Update Eyeglass for the new IP Address information.

4. Ensure networking between Eyeglass and the new IP address is set up.

   1. Login to the Eyeglass web page.
   2. Click Inventory View.
   3. Right click your desired cluster.
   4. Click Edit.
   5. Enter the new IP Address in the SmartConnect Service IP field and Submit.
   important

   Once you submit, you cannot edit the IP address again without having run the Eyeglass Replication Task at least once.

5. Enable Eyeglass configuration replication.

   1. Enable one Configuration Replication job.
      1. Select: Select a bulk action, then select: Enable/Disable.
      2. The Job State will be updated to the last known state.
   2. Wait for the next Replication Task to begin (within 5 minutes it will start)
      1. Check the status of the Configuration Replication job from the Jobs → Running Jobs window.
      2. The Job should run without any error related to unknown source or target.
      3. If no errors, enable the remaining Configuration Replication jobs.
   3. Procedure complete.

Move a Cluster to a New Site

This is a distinct scenario from a simple IP address change above: it covers physically relocating a cluster to a new site, where a planned failover and failback is used to move production access off the cluster before the move, and a new IP address is required once the cluster is back online at the new site.

1. Confirm that shares or exports exist on both the active cluster (writable data) and the read-only cluster before starting.

2. Fail over one SyncIQ policy or Access Zone at a time to the cluster that is staying in place (the target).

   Expected result

   Clients and applications successfully access data from the new active cluster, with no errors, and shares/exports now exist on the new active cluster and on the new read-only cluster (the one being relocated).

3. Disable all Eyeglass jobs for the cluster being relocated.

4. Physically move the cluster to the new site.

5. Change the cluster's IP address at the new site.

6. Bring the relocated cluster back online.

7. Update the relocated cluster's IP address in the Eyeglass Inventory view using the Change PowerScale IP Address procedure above.

8. Re-enable all Eyeglass jobs for the relocated cluster.

   Expected result

   Configuration Replication jobs run without error. If jobs report errors instead, proceed to step 11 to reset Eyeglass so it picks up the IP address change.

9. Fail back one policy or Access Zone at a time to the relocated cluster.

   Expected result

   Clients and applications successfully access data from the relocated cluster again.

10. If Configuration Replication jobs and failback are both working without error on the relocated cluster, the relocation is complete. If jobs are still in error, continue to the next step.

11. Reset Eyeglass to pick up the IP address change for jobs on the relocated cluster:

    1. SSH to the Eyeglass appliance as admin, then switch to root with sudo -s.

    2. Run:

       igls appliance rediscover

    3. Once the reset completes, refresh the browser and log back in.

    4. Open the Jobs window and confirm all jobs are in the correct state. Eyeglass restores job status automatically, but double-check it — correct any job left in User Disabled state, or not in DFS state when it should be.

       important

       If a job did not rediscover correctly and shows in the DFS section of the Jobs window, enable DFS type on that job before enabling the job itself, to avoid creating active shares on the target cluster.

    5. Using bulk actions, select a policy in the Jobs window and choose Run Now. Watch the Running Jobs tab to confirm the configuration sync completes successfully (no error indicator).

    6. If you use Access Zone failover, verify the failover readiness job is enabled, then force-run it from bulk actions and wait for it to complete in the Running Jobs window.

    7. Check the DR Dashboard to confirm it reports a healthy DR status.