- Notes, cautions, and warnings
- Introduction
- Revision history
- Monitoring system health
- Configuring and viewing alerts
- Managing components with PowerFlex Manager
- Administering the network
- Add a network to a service
- Administering the network outside of PowerFlex Manager
- Optimizing the network
- Monitoring the network
- Measuring the bi-directional bandwidth between VMware ESXi hosts in the PowerFlex node
- Verifying connectivity between storage data servers and storage data clients
- Checking the maximum transmission unit on all switches and servers
- Gathering logs from the Cisco Nexus network for troubleshooting
- Gathering logs from the Dell EMC network for troubleshooting
- Adding a VLAN to the network
- Add a VLAN to a Cisco Nexus production network
- Verify the network configuration
- Identify the Dell EMC PowerSwitch access switches
- Configure the Dell EMC PowerSwitch access switches
- Configure the Dell EMC PowerSwitch aggregation switches
- Configure the PowerFlex rack service port for a Dell EMC PowerSwitch management switch
- Add a network interface card to the service port
- Configure the Windows-based jump server to use the service port
- Configure the embedded operating system-based jump server to use the service port
- Creating a network interface card team for Windows Server 2016 or 2019
- Registering and configuring Cisco Nexus switches on the Cisco Smart Account portal
- Administering the storage
- Considerations
- PowerFlex management controller datastore and virtual machine details
- Viewing PowerFlex gateway details
- Administering the CloudLink Center
- Configure the PowerFlex compute-only nodes outside of PowerFlex Manager
- Administering the storage outside of PowerFlex Manager
- Configuring DNS
- Configure PowerFlex storage-only nodes and PowerFlex hyperconverged nodes with static route for SDC reachability
- Retrieving PowerFlex performance metrics
- Verifying VMware vSphere host settings
- Configuring compression on PowerFlex storage-only nodes with NVDIMMs
- Identify NVDIMM acceleration pool in a protection domain
- Identify NVDIMM acceleration pool in a protection domain using a PowerFlex version prior to 3.5
- Enable fine granularity metadata read cache using the command line
- Create a compression storage pool using the PowerFlex GUI presentation server
- Create a compression storage pool using the PowerFlex GUI
- Create a compression volume using the PowerFlex GUI presentation server
- Create a compression volume using PowerFlex GUI
- Verify the VMware ESXi host recognizes the NVDIMM
- Migrate vCLS VMs for PowerFlex hyperconverged nodes and PowerFlex compute-only nodes
- Set V-Tree compression mode for PowerFlex GUI
- Defining rebuild and rebalance settings for PowerFlex
- Adding a PowerFlex storage-only node to PowerFlex
- Adding a PowerFlex storage-only node with an NVMe disk to PowerFlex
- Configuring replication on PowerFlex storage-only nodes
- Add storage data replication to PowerFlex
- Disable replication on the PowerFlex storage-only nodes
- Freeze the remote consistency group
- Remove the remote consistency group
- Remove a peer system
- Remove replication trust for peer system
- Enter SDS in maintenance mode
- Remove storage data replication from PowerFlex
- Remove a storage data replication RPM
- Clean up network configurations
- Exit SDS in maintenance mode
- Remove journal capacity
- Remove target volumes from the destination system
- Remote asynchronous replication on PowerFlex hyperconverged nodes
- Remote consistency group
- Replication direction and mapping
- Add the replication consistency group
- Modify the recovery point objective
- Add a replication pair to the replication consistency group
- Unpair from the replication consistency group
- Freeze the replication consistency group
- Unfreeze the replication consistency group
- Set the target to consistent mode
- Setting the target to inconsistent mode
- Running a test failover
- Stopping test failover
- Restoring replication
- Reversing replication
- Running a failover
- Creating a snapshot of the remote consistency group (RCG) volume
- Pausing the remote consistency group
- Resuming the remote consistency group
- Pausing the initial copy
- Resuming the initial copy
- Setting priority
- Mapping remote consistency groups to the storage data clients (SDC)
- Unmapping an storage data client (SDC) from the remote consistency group target volumes
- Mounting a VMFS datastore copy on the target VMware ESXi cluster
- Determining and switching the PowerFlex metadata manager
- Rebooting PowerFlex nodes
- Rebooting a PowerFlex node in a hyperconverged deployment using PowerFlex GUI presentation server
- Rebooting a PowerFlex node in a hyperconverged deployment using PowerFlex GUI
- Rebooting a PowerFlex rack storage node in a two-layer deployment using the PowerFlex GUI presentation server
- Rebooting a PowerFlex rack storage node in a two-layer deployment using PowerFlex GUI
- Entering protected maintenance mode using the PowerFlex GUI presentation server
- Exiting protected maintenance mode using the PowerFlex GUI presentation server
- Adding and removing a PowerFlex device for server maintenance
- Unmapping and mapping a volume
- Install and configure a Windows-based compute-only node to PowerFlex
- Updating a PowerFlex device path
- Disabling the PowerFlex RAM read cache
- Configuring PowerFlex for Secure Remote Services
- Preparing to configure PowerFlex for Secure Remote Services
- Licensing PowerFlex for PowerFlex management controller 1.0
- Licensing PowerFlex for PowerFlex management controller 2.0
- Editing the PowerFlex gateway
- Adding PowerFlex metadata manager credentials to lockbox
- Adding PowerFlex SSL certificates to lockbox
- Linking an MDM to the PowerFlex GUI presentation server
- Unlinking an MDM from the PowerFlex GUI presentation server
- Registering the PowerFlex gateway with Secure Remote Services
- Enabling and disabling SDC authentication
- Disabling persistent checksum on medium granularity storage pools
- Modify SVM RAM size to upgrade to PowerFlex 3.5.x
- Backing up and restoring
- Powering on and off
- Powering on
- Power on a Technology Extension with Isilon Storage
- Power on a PowerFlex rack
- Power on the PowerFlex management controller 1.0
- Power on the PowerFlex management controller 2.0
- Power on the VMware NSX-T Edge nodes
- Power on the MDM cluster
- Power on PowerFlex storage-only nodes
- Power on all PowerFlex hyperconverged nodes
- Activate PowerFlex protection domains
- Power on all PowerFlex compute-only nodes
- Complete the powering on of PowerFlex rack
- Verify that asynchronous replication is enabled (optional)
- Powering off
- Verify the cluster health and power off the virtual machine
- Power off PowerFlex compute-only nodes with VMware ESXi
- Power off PowerFlex hyperconverged nodes with VMware ESXi
- Power off PowerFlex compute-only nodes with Windows Server 2016 or 2019
- Deactivate PowerFlex protection domains
- Deactivate PowerFlex protection domains using PowerFlex version prior to 3.5
- Power off non-mdm and non-tiebreaker PowerFlex storage-only nodes
- Power off non-mdm and non-tiebreaker PowerFlex hyperconverged nodes with VMware ESXi
- Power off the MDM cluster
- Power off the VMware NSX-T Edge nodes
- Power off the PowerFlex management controller 1.0
- Power off the PowerFlex management controller 2.0
- Complete the powering off of PowerFlex rack
- Power off a Technology Extension with Isilon Storage
- Powering on
- PowerFlex rack password management
- Updating passwords for system components
- Update a credential in PowerFlex Manager
- Updating passwords outside of PowerFlex Manager
- Compute
- Storage
- Virtualization
- Changing a VMware ESXi host root password
- Modifying the VMware vCenter Server Single Sign On default administrator password
- Changing a VMware vCenter Single Sign On password
- Changing VM operating system administrative passwords
- Changing the administrator password for VMware vCenter Server Appliance
- Resetting the VMware vCenter Server Appliance root password
- Changing CloudLink passwords
- Changing the PowerFlex management controller password
- Managing embedded operating system users and password
- Managing SUSE users and passwords
- Managing Red Hat Enterprise Linux users and passwords
- Changing the IPI appliance password
- Changing a user account password on the IPI appliance
- Installing and configuring PowerFlex Manager
- Installation prerequisites
- Configuring the operating system installation (PXE) network
- Deploy PowerFlex Manager
- Setting up PowerFlex Manager
- Enable remote access to the PowerFlex Manager VM
- Configuring PowerFlex Manager
- Discover resources
- Discover an existing cluster
- Configure the operating system installation (PXE) network in PowerFlex Manager
- Clone a template
- Configuring network settings in PowerFlex Manager templates
- Publish a template
- Add a new compatibility management file
- Deploying the PowerFlex GUI presentation server
- Deploy the PowerFlex gateway
- Deploy the CloudLink Center
- Deploy a service
- Add volumes to a service
- Resize a volume
- Migrate vCLS VMs for PowerFlex hyperconverged nodes and PowerFlex compute-only nodes
- Provide a PowerFlex Manager license key after initial setup
- Configure the alert connector
- Configuring SNMP trap and syslog forwarding
- Deploying Windows-based PowerFlex compute-only nodes with PowerFlex Manager (bare metal deployment)
- Managing users
- Minimum VMware vCenter permissions
- Administering fault sets
- Configure VMware vCenter high availability
Dell PowerFlex Rack with PowerFlex 3.x Administration Guide
Unmapping a volume using a PowerFlex version prior to 3.5
Use this procedure to unmap an existing volume from the PowerFlex cluster, using a PowerFlex version prior to 3.5 in the customer cluster.
Steps
- In the PowerFlex GUI, select .
- Expand the correct storage pool to see the mapped volumes.
- Right-click the volume that you want to unmap and select Unmap.
- Select the nodes from which you want to unmap this volume and click Unmap Volumes.
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: <>()\