- Notes, cautions, and warnings
- Introduction
- Revision history
- Initial configuration and setup
- Performing common tasks
- Displaying system information at a glance
- Managing block storage
- Protection domains
- Fault sets
- Storage data servers
- Storage pools
- Acceleration pools
- Devices
- Volumes
- NVMe targets
- Hosts
- Managing file storage
- Overview of configuring NAS servers
- About file system storage
- File protection
- Create a protection policy
- Create snapshot rules
- Create a snapshot
- Assign a protection policy to a file system
- Unassign a protection policy
- Modify a protection policy
- Delete a protection policy
- Modify a snapshot rule
- Delete a snapshot rule
- Refresh a file system using snapshot
- Restore a file system from a snapshot
- Protecting a block storage environment
- Snapshots
- Create snapshots
- Overwrite volume content from a snapshot
- Set bandwidth and IOPS limits for snapshots
- Lock and unlock snapshots
- Delete snapshots
- Map snapshots
- Unmap snapshots
- Increase the size of a snapshot
- Migrate a snapshot vTree
- Pause snapshot vTree migration
- Roll back snapshot vTree migration
- Set snapshot vTree migration priority
- Snapshot policies
- Remote protection
- Extract and upload certificates
- Journal capacity
- Add a peer system
- Restart the replication cluster
- SDRs
- Replication consistency group
- Replication direction and mapping
- Create an RCG
- Map RCG target volumes to hosts
- Unmap a host from RCG target volumes
- Set the target to inconsistent mode
- Set the target to consistent mode
- Modify RPO
- Add a replication pair to an RCG
- Pause replication for an RCG
- Resume replication for an RCG
- Create a snapshot of an RCG volume
- Add an RCG snapshot policy
- Perform a failover
- Reverse replication
- Restore replication
- Test Failover
- Stop a failover test
- Freeze an RCG
- Unfreeze an RCG
- Activate an RCG
- Terminate replication in an RCG
- Delete an RCG
- Pause creation of an initial copy
- Resume creation of initial copy
- Set copying priority
- Unpair from RCG
- Snapshots
- Performing lifecycle operations for a resource group
- Deploying a resource configuration in a resource group
- Basic tasks
- Deploying a resource group
- Adding an existing resource group
- Updating a resource group with new firmware and software
- Viewing a compliance report
- Entering and exiting service mode
- Replacing a drive
- Replacing NVDIMM node or battery
- Reconfiguring MDM roles
- Migrating vCLS VMs to shared storage
- Adding components to a resource group
- Resize a volume
- Removing resources from a resource group
- Adding NVMe/TCP storage access
- Additional resource group management tasks
- Basic tasks
- Preparing a template for a resource group deployment
- Basic tasks
- Additional template management tasks
- Deploying a resource configuration in a resource group
- Managing resources
- Basic tasks
- Additional resource management tasks
- Monitoring events and alerts
- Configuring system settings
- User management
- Repositories
- Getting started
- Networking
- Events and alerts
- License management
- Security
- Serviceability
- Software upgrade
- PowerFlex Manager user interface reference
- Additional administration activities
- Retrieving logs for the PowerFlex nodes
- Retrieving logs for PowerFlex components
- Retrieving additional PowerFlex logs
- Enabling audit logging
- Managing storage devices using CloudLink
- Understanding NVMe over TCP load balancing
- Managing NAS server configuration
- Migrating to NVMe/TCP on ESXi
Dell PowerFlex 4.5.x Administration Guide
Upgrading PowerFlex Manager from a local repository path
You can upgrade the management software from a .TGZ file on a local repository path.
Prerequisites
Before you begin, ensure that you:
- Take a backup of PowerFlex Manager settings.
- Upload the latest compatibility matrix file to ensure that PowerFlex Manager has access to the latest upgrade information.
About this task
When you attempt an upgrade, PowerFlex Manager warns you if the current version of the software is incompatible with the target version, or if any of the RCM or IC versions that are currently loaded on the management software are incompatible with the target compliance versions. To determine which paths are valid and which are not, PowerFlex Manager uses information that is provided in the compatibility matrix file. The compatibility matrix file maps all the known valid and invalid paths for all previous releases of the software. Before proceeding with an upgrade, PowerFlex Manager notifies you if any of the following situations is detected:
- No upgrade is required. This situation occurs when the current and target versions are the same. You still can force an upgrade, if needed.
- The upgrade path that you are attempting to perform is a valid path. The source version of PowerFlex Manager is compatible with the target version and the source version of the RCM or IC is also compatible with the target version.
- The source version of PowerFlex Manager is compatible with the target version. However, the source version of the RCM or IC is not compatible with the target version. Your resource groups may go into lifecycle mode until you perform an RCM or IC upgrade. PowerFlex Manager puts a resource group in lifecycle mode if the resource group’s RCM or IC is not within a year of the target PowerFlex Manager launch. You can mitigate a resource group that is in lifecycle mode by upgrading to a compliance version that is within a year of the current PowerFlex Manager launch.
- The upgrade path that you are attempting to perform is not supported.
The compatibility matrix file is required for all upgrades. When you first install PowerFlex Manager, the software does not have the compatibility matrix file, so you must upload the file before performing any upgrades.
Steps
- If you are using PowerFlex rack, log in to Dell Technologies Download Center. Then, go to the section for PowerFlex Manager.
- If you are using PowerFlex appliance, log in to Dell Technologies Support. Then, enter your service tag to be taken to available downloads.
- Download the PowerFlex management platform .TGZ file.
- Copy the PowerFlex management platform .TGZ file to a share drive location.
- On the menu bar, click Settings, and then click Software Upgrade.
- Click Management Software Upgrade.
- On the Management Software Upgrade page, you can see the Current Management Software Version and check the Available Management Software Version field to see if a newer version of PowerFlex Manager is available.
-
Click
Edit Settings.
- To upgrade from a specific version on a local repository path, select Update Software from local repository path, and enter the path in the Repository Path box.
- Enter the username and password.
- Click Save.
-
At the top of the
Management Software Upgrade page, click
Upgrade Now.
After you click Upgrade Now, a dialog box displays with a warning message indicating whether the upgrade path is valid.
- Under Management Credentials, optionally override the default username and password for the nodes hosting PowerFlex Manager. The upgrade requires access to the nodes hosting PowerFlex Manager. Provide a single user that has superuser privileges for all nodes. You can enter the username for the first row in the table, and the changes you make will be applied to all the nodes. Enter the password for each of the nodes.
- Type UPDATE POWERFLEX MANAGER if you want to proceed with the update. If you want to perform an update even if none is required, type FORCE UPDATE.
-
Click
Yes to update
PowerFlex Manager.
The update process displays messages indicating the progress of the update. Depending on which services were upgraded, you may be required to login once again, after the upgrade process is complete.
Next steps
If you do not want to upgrade the resource groups, you do not need to perform the upgrade.
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: <>()\