Page Comparison

...

...

1. A chassis is offline when it is selected for reboot. To have the reboot process ignore currently offline chassis, add the flag --continueWithOfflineChassis.

2. The reboot process will continue continues if the volumes come up but a node goes into an error state. To have the reboot process stop, add the flag --stopOnNodeError.

3. If the chassis boots with a number of volumes that doesn't match the number present before the chassis was rebooted. A volume is considered up if it has a state of: ok, retiring, retired, or unavailable

4. The chassis does not come back online after 3 hours has passed.

...

Chassis states — The status listing will also show shows the status for each chassis that is processed by the rolling reboot task. Each chassis can have one of the following states:

...

No-wait reboot —  Normally, the rolling reboot process will wait waits up to 3 hours for a rebooted chassis to come back online before proceeds to the next. To force the process to stop waiting and move to the next chassis, use the --skip flag:

...

1. Create a supplemental .cfg file (such as changes.cfg) and specify any new or changed Swarm settings to apply.

2. To upload the configuration changes, use the following CLI command:

   Code Block
   language bash
   platform upload config -c {Path to .cfg}

The CLI will parse parses the uploaded configuration file for changes to make to Platform.

If Swarm was running during the upload, Platform Server attempts to communicate the new configuration to Swarm. Any settings that cannot be communicated to Swarm will require requires a reboot of the Swarm cluster in order to take effect. For each setting contained in the file, the CLI will indicate indicates if the setting was communicated to the Storage cluster and if a reboot is required. The Swarm UI also indicates which settings require rebooting.

...

1. Create a .cfg file (such as changes.cfg) and specify any new or changed node-specific settings to apply.

2. To upload the configuration changes, use the following CLI command:

   Code Block
   language bash
   platform upload config -c {Path to .cfg} -m {mac address}

The CLI will parse parses the uploaded configuration file for changes to make to that chassis.

...

Temporary release — Temporary release of a chassis assumes that the chassis will be is added back into the cluster at a later time. Releasing a chassis allows deallocating the cluster resources, such as IP Addresses, or wipe and reset the configuration.

...

Permanent removal — Permanent removal is for retiring a chassis altogether or changing the chassis' main identifying information, such as changing a NIC. Removing the chassis from management will cause causes the chassis to start the provisioning life cycle as if it were a brand new chassis, if it is powered on again.

...

...

...