- 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
Discovery overview
You can discover new resources or existing resources that are already configured within your environment. After discovery, you can deploy resource groups on these resources from a template. Only administrator-level users can discover resources.
By default, the operational state for all discovered nodes is Unmanaged. If you want to perform firmware updates or deployments on a discovered node, select the node and change the operational state to Managed.
If you have not yet uploaded a license, PowerFlex Manager is configured for monitoring and alerting only. In this case, all the resources are restricted to the Unmanaged resource state, and you cannot change the state to Managed or Reserved.
For some resources such as nodes, the default credentials are prepopulated in PowerFlex Manager. If the credentials are changed from the defaults, add the credential to PowerFlex Manager with the new login information.
Element Manager discovery
The IPI cabinet is discovered as an element manager. Once PowerFlex Manager discovers the IPI cabinet, you can view cabinet details or you can open the IPI appliance management application to view more details.
The CloudLink Center is discovered as an element manager. If you create your own username in CloudLink Center, you need the SecAdmin access role and the local user type for the new user to complete discovery. The client user type does not work for discovery in PowerFlex Manager. If one member of a cluster of CloudLink Center is shut down, the inventory still succeeds because PowerFlex Manager falls back to inventorying the other CloudLink Center members if the first one is down.
Node discovery
PowerFlex Manager supports PowerFlex node discovery and allows you to onboard nodes by configuring the initial management IP address and iDRAC credentials. To perform initial discovery and configuration, verify that the management IP address is set on the node and that PowerFlex Manager can access the IP address through the network. While configuring IP addresses on the node, verify that PowerFlex Manager can access any final IP address in a range used for hardware management, to complete discovery of these nodes.
PowerFlex Manager also allows you to use name-based searches to discover a range of nodes that were assigned IP addresses by DHCP to iDRAC. You can search for a range of DNS hostnames or a single hostname within the Discovery Wizard. After you perform a name-based discovery, PowerFlex Manager operations to the IDRAC continue to use name-based IP resolution, since DHCP may assign alternate addresses.
Switch discovery
If you attempt to discover a Cisco switch with terminal color configured, the discovery fails. To discover the switch successfully, disable the terminal color option by running configure no terminal color persist.
VM manager discovery
A VMware vCenter is discovered as a VM manager.
PowerFlex Manager users with the administrator role can discover a vCenter in
PowerFlex Manager. A vCenter read-only user can discover a vCenter in
PowerFlex Manager only after the following requirements are met:
- The vCenter user who is specified in the vCenter credential is granted the VirtualMachine.Provisioning.ReadCustSpecs and StorageProfie.View privileges.
- The permission containing these privileges is granted to that user on the root vCenter object and the Propogate to children property is set to True.
PowerFlex Manager allows you to deploy new hyperconverged and compute-only resource groups and add existing resource groups to a vCenter that has an Enhanced Linked Mode (ELM) configuration. ELM connects multiple vCenter servers, allowing you to search across servers and perform other vCenter management functions. ELM does not provide clustering or redundancy.
If you are working with a vCenter that has an enhanced linked mode configuration, you must discover only the vCenter to which you want to deploy or add an existing resource group. You do not need to discover the other vCenters that are connected through the enhanced linked mode configuration.
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: <>()\