cluster upgrade

--build-package PACKAGE_FILE_PATH

Specifies the full path to the package file for the target release. The package file must be located in the /vast/bundles directory on the management CNode.

For example: --build-package /vast/bundles/release-3.6.0-123450.vast.tar.gz

--enable-dr

For a cluster that does not have data reduction enabled before upgrade, this option enables data reduction along with the upgrade.

--force

Forces upgrade regardless of version or upgrade state. Use this option if you need to upgrade to the same version as already installed or if a previous upgrade failed without the upgrade state clearing.

--os-upgrade

Upgrades the OS on the CNodes and DNodes in addition to the core platform and VMS software.

--skip-hw-check

Skips those pre-upgrade validations that are related to hardware when pre-upgrade validations are run after bundle upload.

Use with caution since component redundancy is important in NDU.

Do not use with OS upgrade.

--skip-sw-validations

Include this option to proceed even if there is a deny list or if NVRAM RAID state is degraded.

--cnodes-batch-size-percentage PERCENTAGE

Overrides the default percentage of CNodes to upgrade in parallel in one batch. The default batch size is 10%.

Maximum: 50

Example: --cnodes-batch-size-percentage 20

--dnodes-batch-size-percentage PERCENTAGE

Overrides the default percentage of DNodes to upgrade in parallel in one batch.

The default batch size is 20%.

Maximum: 37.5

Example: --dnodes-batch-size-percentage 25

--isolcpus

Resets the configuration of isolated CPUs according to a formula.

--vms-only-upgrade

Upgrades VMS version only.

--fw-upgrade

For CERES, upgrades firmware for BMC, MCU, PCI and Bluefield.

--bmc-upgrade

Upgrades BMC and all relevant components (FPGA, BIOS, UBM, CPLD and so on).