- Notes, cautions, and warnings
- Introduction
- Automated Upgrade
- Automated Upgrade of Linux-based Nodes
- Automated Upgrade of ESXi-based Nodes
- Upgrading ESXi-based configurations
- Download installation packages
- Preparing to upgrade ESXi configurations
- Upgrade the PowerFlex Gateway with Stateless ESXi IP addresses
- Upgrading PowerFlex—ESXi-based nodes
- Upgrade the PowerFlex presentation server (PowerFlex GUI) from v3.5 or later
- Upgrade the PowerFlex GUI from versions earlier than v3.5
- After upgrading an ESXi-based system
- Automated Upgrade of Nodes in a Two-Layer Configuration
- Preparing to upgrade two-layer configuration—Linux and ESX-based
- Upgrading two-layer configurations (Linux-based and ESX-based)
- Upgrade the PowerFlex presentation server (PowerFlex GUI) from v3.5 or later
- Upgrade the PowerFlex GUI from versions earlier than v3.5
- Prepare server operating systems for support of large-scale systems (up to 2048 SDCs)
- After upgrading a two-layer system
- Manual Upgrade
- Manual Upgrade of Linux-based Nodes
- Manual upgrade of physical Linux-based configurations
- Non-default certificate use before and after a PowerFlex Gateway upgrade
- Upgrade the PowerFlex GUI from versions earlier than v3.5
- Upgrade the PowerFlex presentation server (PowerFlex GUI) from v3.5 or later
- Manual upgrade of Linux-based nodes—3-node MDM cluster
- Manual upgrade of Linux-based nodes—5-node MDM cluster
- Prepare server operating systems for support of large-scale systems (up to 2048 SDCs)
- Manual Upgrades in the ESXi Environment
- Manually upgrade an ESXi-based PowerFlex system
- Collect and record PowerFlex information
- Prerequisites for manual upgrades in ESXi environments
- Upgrade the PowerFlex GUI from versions earlier than v3.5
- Upgrade the PowerFlex presentation server (PowerFlex GUI) from v3.5 or later
- Unregister the old PowerFlex system
- Unregister the current PowerFlex plug-in
- Register the new PowerFlex plug-in
- PowerFlex component overview
- Upgrade the PowerFlex system
- Upgrade the SDC on an ESXi host
- Upgrade the CentOS operating system on SVMs
- Upgrade the PowerFlex Gateway operating system
- After upgrading an ESXi system
- Miscellaneous topics for manual upgrades in ESXi environments
- Manually upgrade an ESXi-based PowerFlex system
- Manual Upgrade of Linux-based Nodes
- Firmware Upgrade
- Upgrade of LSI RAID Controller Firmware and Driver
- VxFlex Ready Node Server Firmware Upgrades
- Reference Topics
- Post-Upgrade and Other Common Tasks
- Shutdown or restart a node gracefully
- Disabling IPMI
- Check NVDIMM capacity compatibility for future upgrades
- Configure the SDS for NVDIMM health awareness
- Extracting PowerFlex packages
- Upgrading the PowerFlex Gateway when a custom certificate is used
- Troubleshoot PowerFlex plug-in registration issues
- Unregister the PowerFlex plug-in
- Register the PowerFlex plug-in manually
- Store Tomcat's keystore password in the lockbox
- Prepare lockbox files for Java upgrade
- Updating the SDC parameters
- Switching to secured authentication mode
- Configure Secure Remote Services or email notifications after upgrading
- Upgrade a VMware-based PowerFlex system that contains CloudLink-encrypted devices
- Manually upgrade an ESXi-based PowerFlex system with CloudLink
- Collect and record PowerFlex information
- Prerequisites for manual upgrades in ESXi environments
- Upgrade the PowerFlex GUI from versions earlier than v3.5
- Upgrade the PowerFlex GUI from v3.5 or later
- Unregister the old PowerFlex system
- Unregister the current PowerFlex plug-in
- Register the new PowerFlex plug-in
- PowerFlex component upgrade overview
- Upgrade the PowerFlex system
- Upgrade the SDC on an ESXi host
- Upgrade the CentOS operating system on SVMs
- Upgrade the PowerFlex Gateway operating system
- Upgrade CloudLink
- After upgrading an ESXi system
- Manually upgrade an ESXi-based PowerFlex system with CloudLink
- Upgrade the operating system to a major ESXi version
- DTK - Hardware Update Bootable ISO
- Dell OpenManage DRAC Tools (RACADM)
- Update the SATADOM firmware (VxFlex Ready Node R630/R730xd only)
- Recommended BIOS and firmware settings
- Troubleshooting the Hardware ISO
- Additional resources
- Set up the iDRAC IP address and BIOS
- Verify the status of the system hardware, storage controller, and disks - R630/R730xd servers
- Verify the status of the system hardware, storage controller, and disks - R640/R740xd servers
- Increasing SVM system disk size
- Upgrading systems with more than 512 SDCs, and configuring LIA LDAP in large systems
- Post-Upgrade and Other Common Tasks
Upgrade Dell PowerFlex to v3.6.x
Upgrade the CentOS operating system on SVMs
Use the PowerFlex Installer to upgrade the SVM's CentOS operating system to the latest security level of operating system security patching. This procedure only upgrades the operating system on the SVM. It does not upgrade PowerFlex.
NOTE:SVM operating system patching is applicable even if the SVM replacement procedure was performed. The latest patch bundle has the latest security patches that were released after the latest version of
PowerFlex was officially launched (the refresh of the package is done on a monthly basis based on continuous security scans and input from customers).
Use the PowerFlex Installer to upgrade the CentOS operating system on multiple SVMs. This procedure is required when upgrading an ESXi-based PowerFlex system where SVMs are currently running on CentOS 7.5. (PowerFlex v3.0, or v3.0.0.x)
Ensure that you have the latest SVM operating system upgrade ZIP file. It is available from the support site. You can opt to download the latest file from https://www.dell.com/support/home/en-in/product-support/product/scaleio/drivers.
The patch_script file that you require is part of the VMware complete software package (which is in the Complete SW download ZIP) and also as a separate artifact that is refreshed from time to time (usually once a month). The ZIP file name is: SVM_OS_Patching_package_MMDDYYYY.zip
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\