Versions Compared

Old Version 15

changes.mady.by.user Anjali Tyagi

Saved on

compared with

New Version 16

changes.mady.by.user Anjali Tyagi

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Code Block
# scsctl auth login --user [current admin name configured in SCS]:[current password configured in SCS]
logged in
# scsctl platform config set -d admin.userName=[admin user name in the running cluster] --allow-notification-failures
updated and pushed to instances
# scsctl platform config set -d admin.password=[admin password in the running cluster] --allow-notification-failures
updated and pushed to instances
# scsctl auth login --user [admin name]:[admin password]
logged in
Info

Required

In order to To ensure SCS and cluster settings are consistent, always use the “--allow-notification-failures” flag when changing administrator-related settings.

Step 6

Initialize DHCP.

Code Block
Subnet Layout:

   |                 |                                 |                 |
   |     reserve     |                                 |     reserve     |
   | <--  lower  --> | <---  storage pool range  ----> | <--  upper  --> |
   |      range      |                                 |      range      |
   |                 |                                 |                 |
 subnet              | <------ DHCP and Static ------> |             broadcast
 address                                                              address
Info

Note

...

At least one of the reserved ranges must be set (lower or upper).

Some Considerations Relating to Storage Node IP Addresses

...

The IP addresses of storage nodes added to the storage cluster subsequent to the creation of the backup file will not have been recorded in the backup, and those nodes may acquire a different IP address when they are rebooted. (Although IP addresses will come from the same range of the address pool as long as DHCP was is initialized with the same parameters.)