- 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
Deployment checklist for software management
There are compute, storage, and networking deployment requirements that must be met to deploy a software management node.
| Item | Checked | |||
|---|---|---|---|---|
| 1 | There is a supported operating system that is installed on any hardware, for example, a VM or a server. | |||
| 2 | There is at least one free 100 GB drive with no partitions (required for PowerFlex storage-only nodes and PowerFlex hyperconverged nodes only). | |||
| 3 | There are no PowerFlex packages preinstalled. | |||
| 4 | The networks are configured including any static routes. | |||
| 5 | Any repository that is configured should be functional. | |||
| 6 | The firewall is enabled and the SSH port is open. | |||
| 7 | The root user is configured in the software management node operating system, and the OS Admin user with root credentials are configured in PowerFlex Manager. | |||
| 8 | There must be at least one network that is configured in the software management node operating system that
PowerFlex Manager can reach. In addition, there is a minimum of one PowerFlex data type network that must be configured in
PowerFlex Manager, and added to a software management template.
NOTE:When creating a PowerFlex data network to be used with a software management node and resource group, the VLAN is optional, but is still a required parameter to create the network. If no VLAN is configured on the network, then enter
1 for this value.
|
|||
| 9 | The software management node requires access to the
PowerFlex Manager HTTP share:
https://[external_loadbalancer_ip_address]/httpshare/download/ |
|||
| 10 | The following operating system dependent packages are already installed: | |||
| Operating system | Package type | Package name | ||
|
Normal |
|
||
| With compression | ndctl | |||
| SUSE Linux Enterprise Server (SLES) | Normal |
|
||
| With compression | ndctl | |||
| Ubuntu | Normal |
|
||
| With compression | ndctl | |||
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: <>()\