Page Comparison

...

1. Install the new RPM.

   Code Block
   rpm -Uvh swarm-scs-[version].x86_64.rpm

2. If static IP addresses were previously assigned before this migration, skip this step and proceed to the “boot/reboot” step.

   1. Use case #1: Allow DHCP to assign IP addresses
      When the cluster nodes are rebooted, DHCP will assign an IP address to each node. If the nodes have already been booted with manually assigned IPs, the assigned IP addresses will remain the same. If IP addresses were not manually assigned, but existing DHCP leases are still in effect, then currently assigned IP addresses will remain the same. If existing DHCP leases have expired (or this is the first boot of the storage cluster), DHCP will assign IP addresses from the allocated pool in no particular order. When this use case is selected, proceed to the “Boot/reboot” step.

   2. Use case #2: Pre-assign an IP address to each storage node
      In this case, an IP address must be manually assigned to each storage node before it is rebooted. The procedure for manual assignment is fully explained in Configuring Swarm for Static IPs with Swarm Cluster Services (SCS)).
      The summary of the manual assignment procedure is:

      1. Get an instance list that provides a node ID to use in the next step.

         Code Block
         scsctl storage instance list

      2. Assign an IP address to each node.

         Code Block
         scsctl storage config set -d -i {chassis ID} "network.ipV4Address={your.static.address.here}"

3. Run the following command.

   Code Block
   scsctl diagnostics upgrade_check

4. Run the diagnostics check.

   Code Block
   scsctl diagnostics config scan_missing

   It shows the below output:

   Code Block
   Running step [11/11]: Show the next steps after this wizard ******************************************************************************** Congratulations, your Swarm Cluster Services server has been upgraded! Please reboot, then run the following to ensure your system is fully configured:

5. Reboot the system.

6. Re-initialize DHCP:

...