(Note: These steps were tested with SCS 1.5.1 using the “bigboot” test environment.)
Prerequisites:
The network interface was originally used for the private network which the running cluster uses. (Note that the SCS instance will become the network gateway for the running storage cluster. Thus the need for consistency between network settings for the recreated SCS instance and the running cluster.)
The static IP for that network interface
The netmask for that network interface
The Swarm storage administrator user name for the running storage cluster.
The Swarm storage administrator password for the running storage cluster.
The cluster name for the running storage cluster.
The DSN server(s) used by the running cluster.
The network domain name used for the running cluster.
The IP address pool reserved ranges used when booting the running cluster.
Step 1
Install SCS
Follow the instructions to install SCS found here.
Step 2
Initialize SCS.
Run the SCS initialization wizard, following the instructions here.
When prompted, use network settings (interface, IP address, and netmask) that are consistent with the running storage cluster.
Step 3
Install the Swarm storage component bundle.
Add the Swarm storage component to the SCS repo:
# scsctl repo component add -f [storage software bundle file name]
When asked whether to use encryption-at-rest, use the same mode that is consistent with the running cluster.
Missing setting: storage/disk.encryptNewVolumes The following setting(s) require a default value: disk.encryptNewVolumes [type: bool] (Whether to encrypt new Swarm volumes. Enabling encryptNewVolumes means that any newly-formatted Swarm volume will be encrypted) True False
When asked whether to enable multicast, be consistent with the multicast mode currently used in the running cluster:
The following setting(s) require a default value: Missing setting: storage/cip.multicastEnabled cip.multicastEnabled [type: bool] (Whether multicast should be used for communication within Swarm.) True False
When asked for the name of the storage cluster, it is important to enter the same string that as the name of the running cluster.
added: storage - 15.3.0 (15.3.0) [debug] Please enter a name for the group (FQDN format encouraged) - Required to be able to boot instances of "storage":
Step 4
Add additional settings.
# scsctl diagnostics config scan_missing
In every case when prompted, enter a value that is consistent with settings in the running cluster.
DNS servers:
---------------------------------------------- Name: network.dnsServers Type: array[str] Description: Required. DNS servers to be used. ---------------------------------------------- Missing setting: network_boot/network.dnsServers network.dnsServers [type: array[str]] (Required. DNS servers to be used.):
Storage cluster administrator password. Enter the password being used in the running storage cluster:
Missing setting: platform/admin.password admin.password [type: str ***SECURE***] (Administrative user password):
DNS domain:
Missing setting: platform/network.dnsDomain network.dnsDomain [type: str] (Required. The DNS domain name that will be used.):
Step 5
Storage cluster administrator user name.
If the Swarm storage administrator user name in the running cluster is the default value of “admin”, proceed to step 6.
NOTE: It will not be possible to rename the storage cluster administrator user name until SCSL-360 - Getting issue details... STATUS has been done.
If the Swarm storage administrator user name in the running cluster is not the default value of “admin”, change the administrator user name in SCS to the correct value.
# scsctl platform config set -d admin.userName=[admin user name in the running cluster]
Step 6
Initialize DHCP.
Initialize DHCP using the same reserved range parameters used originally for the storage cluster.
Subnet Layout: | | | | | reserve | | reserve | | <-- lower --> | <--- storage pool range ----> | <-- upper --> | | range | | range | | | | | subnet | <------ DHCP and Static ------> | broadcast address address
Note that at least one of the reserved ranges must be set (lower or upper).
Step 7
Reboot the storage cluster.
The storage cluster must be rebooted in order for SCS to record the IP addresses of the storage cluster nodes (chassis).