- 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
Compliance versions
PowerFlex Manager displays the following information about the compliance versions:
| Field | Description |
|---|---|
| State | Displays an icon indicating one of the following states:
|
| Version | Displays the compliance version. If one or many components in the RCM are modified, a wrench icon and the text, "Modified" is displayed next to the name of the RCM. But, if the file is deleted from the file share after a component is updated, the wrench ion with the text, "Modified | Needs Attention", is displayed. |
| Source | Displays the share path of the compliance version in a file share. |
| Signature | Displays whether the digital signature on the compliance file is signed or unsigned. |
| File Size | Displays the size of the compliance file in GB. |
| Type | Displays Minimal if the compliance file only contains firmware updates, or Full if it contains firmware and software updates. |
| View bundles | Displays details about any bundles added for the compliance version. |
| Available Actions | Select an option if the compliance file is in an
Error or
Needs Approval state:
|
Select the compliance version to view the following information about the firmware package:
- Bundles—Displays the number of bundles available in the firmware package.
- Components—Displays the number of software components available in the firmware package.
- Created On—Displays the date when the compliance version was created.
- Last Updated—Displays the date when the compliance version was last updated.
- Resource Groups Affected—Displays the resource groups in which the firmware is used.
From this page, you can:
- Add a compliance file.
A compliance file can be large and take some time to download and unpack. To help you monitor the progress of the downloading and unpacking operations, PowerFlex Manager provides percentage complete information for these operations in the State column on the Compliance Versions tab.
- Select Default Version and choose a version from the drop-down list to set it as the default for compliance.
- Select a compliance version from the list, and click the delete icon in the same row to remove the version.
If you remove a compliance version, the version is deleted from the appliance not from the file share.
- Select a version from the list, and, in the right pane, click View Bundles to view the firmware and software bundles available in the compliance version.
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: <>()\