(Note: These steps were tested with SCS 1.5.1 using the “bigboot” test environment.)
...
Code Block |
---|
Missing setting: platform/network.dnsDomain network.dnsDomain [type: str] (Required. The DNS domain name that will be used.): |
Step 5
Login with valid administrator credentials.
Code Block |
---|
# scsctl auth login --user [administrator user name]:[administrator password] |
Step 6
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
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
8.
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 in the running cluster.
Code Block |
---|
# scsctl platform config set -d admin.userName=[admin user name in the running cluster] --allow-notification-failures |
Note: It is recommended to use the flag, “--allow-notification-failures”, with the scsctl “set” verb in every recovery scenario to ensure that all nodes, including those temporarily offline, have consistent settings.
After changing the administrator user name, you must login again.
Step 7
Login with valid administrator credentials.
Code Block |
---|
# scsctl auth login --user [administrator user name]:[administrator password] |
Step
...
8
Initialize DHCP.
Initialize DHCP using the same reserved range parameters used originally for the storage cluster.
...
Note that at least one of the reserved ranges must be set (lower or upper).
Step
...
9
Reboot the storage cluster.
...