- Notes, cautions, and warnings
- Introduction
- Revision history
- Install
- Installation overview and prerequisites
- Preparing the PowerFlex Manager environment
- Deploying into a VMware vSphere environment
- PowerFlex management platform virtual machine requirements
- Deploying the PowerFlex management platform
- Deploying and configuring the PowerFlex management platform installer virtual machine
- Deploying and configuring the PowerFlex management platform VMs
- PowerFlex management platform cluster configuration parameters
- Deploy the PowerFlex management platform cluster
- (Optional) Collect PowerFlex management platform support data
- Uninstall the PowerFlex management platform cluster
- Deploying a co-resident management environment onto the boot device of PowerFlex storage nodes
- Deployment workflow
- Co-residency management deployment prerequisites
- Deploy the PowerFlex management platform installer
- PowerFlex management platform cluster configuration parameters
- Deploy the PowerFlex management platform cluster
- Post deployment cleanup
- (Optional) Collect PowerFlex management platform support data
- Uninstall the PowerFlex management platform cluster
- Perform initial configuration
- Deploying into a Linux management environment
- Deploy the PowerFlex management platform installer
- Finalizing firewall configuration
- Deploying into a VMware vSphere environment
- Troubleshooting a PowerFlex management platform deployment
- Configuring PowerFlex Manager
- Deploying PowerFlex storage
- Deployment design for co-residency management
- PowerFlex component layout
- Operating system requirements
- Preparing the storage node
- Deploying a PowerFlex cluster using a CSV topology file
- Prepare the CSV topology file
- CSV file examples for typical configurations
- Configuring performance profile during deployment
- Adding new components or features by editing the existing CSV file
- Deploy a PowerFlex cluster using a CSV topology file from PowerFlex Manager
- Deploy or expand a cluster using REST API commands
- Deployment design for co-residency management
- Deploying PowerFlex file nodes
- Prerequisites for PowerFlex file nodes
- Resource group deployment
- PowerFlex file network enhancement and flexibility
- PowerFlex file node with a single network interface controller (tagged VLAN NAS management)
- Shared network interface for PowerFlex management and NAS management (tagged VLAN) and dedicated interfaces for PowerFlex data and NAS data
- Dedicated interfaces for four types of traffic (NAS management VLAN is untagged or native)
- Dedicated interfaces for four types of traffic (tagged NAS management VLAN)
- Shared interface for PowerFlex management and data and a shared interface for NAS management and data
- Verify connectivity
- Define networks
- (Optional) Edit a network
- (Optional) Deleting a network
- Discover a resource
- Add a template
- Edit a template
- (Optional) Edit template information
- Clone a template
- Build and publish a template
- Component types
- Deploying a resource group
- Verify resource group status
- PowerFlex file network enhancement and flexibility
- Post-installation activities
- Post-installation checklist
- Configuring NVMe initiators
- SDC deployment preparation tasks for SLES, Oracle Linux, and Ubuntu
- Enable OpenSSL FIPS compliance
- Check port usage
- Configure the SDC (scini) driver for SELinux
- Mount a PowerFlex volume
- Associate PowerFlex volumes with physical disks
- Configure the SDS for optimal memory usage
- Configure the SDS for NVDIMM or SDPM health awareness
- Performance tuning post-installation
- PowerFlex system changes
- Optimize Linux
- Optimize VMware ESXi
- Optimize Windows
- Optimizing VM guests
- Optimize Hyper-V
- Optimize AIX
- Configure RAID controller virtual disk settings
- Apply performance profiles to system components
- Configure SDC access to the MDM
- Upgrade
- Upgrading from PowerFlex 4.5.x to 4.6
- Upgrading from PowerFlex 3.6 to 4.6
- Preparing to upgrade
- Upgrade workflow from PowerFlex 3.6 to 4.6
- Upgrade limitations
- Deploying into a VMware vSphere environment
- PowerFlex management platform virtual machine requirements
- Deploying the PowerFlex management platform
- Deploying and configuring the PowerFlex management platform installer virtual machine
- Deploying and configuring the PowerFlex management platform VMs
- PowerFlex management platform cluster configuration parameters
- Deploy the PowerFlex management platform cluster
- (Optional) Collect PowerFlex management platform support data
- Uninstall the PowerFlex management platform cluster
- Configuring PowerFlex Manager
- Upgrading operating systems on PowerFlex nodes
- Post-upgrade activities
- Post-upgrade checklist
- Upgrade SDC on Windows-based server
- Upgrade SDC on Linux and AIX
- Upgrade SDC on VMware ESXi
- Configuring NVMe initiators
- Upgrade PowerFlex file services
- Configuring system data networks, network sets, hosts, host groups, and enabling persistent discovery (Optional)
- (Optional) PowerFlex file multi-tenancy
Dell PowerFlex 4.6.x Install and Upgrade Guide
Dedicated interfaces for four types of traffic (NAS management VLAN is untagged or native)
In this configuration, the four types of traffic: PowerFlex management, PowerFlex data, NAS management (untagged or native), and NAS data have a dedicated physical interface.
Steps
-
Use the following procedure before creating the
PowerFlex file template.
- Run the following command from the
PowerFlex management platform primary node to update the thin deployer service:
#kubectl patch hr thin-deployer -n powerflex -p '{"spec":{"values":{"sdnas_swonly_nas_mgmt_int":"eth2", "sdnas_swonly_nas_data_int":"eth3"}}}' --type=merge
- Run the following command from the
PowerFlex management platform primary node to update the thin deployer service:
-
Modify the following values according to your preferences:
- sdnas_swonly_nas_mgmt_int to eth2 or em2
- sdnas_swonly_nas_data_int to eth3 or em3
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: <>()\