- Notes, cautions, and warnings
- Getting Started
- Post-Deployment Activities
- Post-deployment tasks
- Post-deployment task checklist
- Prepare lockbox files for Java upgrade
- Create the lockbox
- Customer support
- Configure native users
- Configure LDAP users
- Configure SNMP
- Enable OpenSSL FIPS compliance
- Create and map volumes
- Set up replication on peer systems
- Install and configure PowerFlex SRA
- Post-deployment best practice suggestions
- Link PowerFlex presentation server to the MDM cluster
- View MDM certificate details in the PowerFlex GUI
- Configure the SDS for NVDIMM health awareness
- Post-deployment tasks
- PowerFlex Performance Fine-Tuning
- PowerFlex performance fine-tuning
- Tune PowerFlex for best performance
- Performance tuning post-installation
- PowerFlex system changes
- Optimize Linux
- Optimize ESXi
- Optimize SVM settings
- Optimizing VM guests
- Optimize Hyper-V
- Optimize AIX
- Optimize Windows
- PowerFlex Performance Parameters
- RAID controller virtual disk settings
- Apply Performance Profiles to system components
- PowerFlex performance fine-tuning
- Configure and Customize
- Configuration
- Protection Domains
- Fault Sets
- SDS
- Storage Pools
- Configuring acceleration
- Devices
- Volumes
- Configuring SDCs
- Manual SDC configuration/verification
- Update approved SDC IP addresses using the PowerFlex GUI
- Approve SDCs using the PowerFlex GUI
- Restricted SDC mode
- Add an external SDC to an existing PowerFlex system
- SDC operations
- Update the SDC driver with IP address changes
- Detecting new volumes
- Query volumes using drv_cfg
- Query tgt objects using drv_cfg
- Query GUID using drv_cfg
- Query MDMs using drv_cfg
- Loading a configuration file using drv_cfg
- Adding an MDM using drv_cfg
- Modifying an MDM IP address using drv_cfg
- Permanent Device Loss state
- Update the SDC parameters in VMware based HCI or compute node
- Run the SDC driver on RHEL\SLES with multipath enabled
- SDC authentication
- Apply Performance Profiles to system components
- RFcache (xcache) package installation
- Increase SVM memory to accommodate additional SDS device
- Modify an SDS port during I/O
- Configure the PowerFlex presentation server
- Unlink from the MDM cluster
- PowerFlex VASA provider and vVols
- MDM Cluster
- Configuring MDM cluster
- Configure virtual IP addresses using the PowerFlex Installer
- Security
- Approving pending security certificates
- Default self-signed certificate expires on the PowerFlex Gateway
- Default self-signed certificate expires on PowerFlex GUI
- Upgrade the PowerFlex Gateway when a custom certificate is used
- Change the PowerFlex Gateway's keystore password
- Change the PowerFlex presentation server's keystore password
- Change the PowerFlex presentation server's truststore password
- Certificate management for PowerFlex presentation server
- Certificate management for PowerFlex Gateway
- Use SSH authentication for the PowerFlex Gateway
- Configure SSL component authentication
- Configure SDC access to the MDM
- Approved encryption methods
- Login banner overview
- Managing LIA security
- User Management
- Fault reporting features
- Add, Remove or Rename Components
- Logs
- LIA
- Configuration
- Protection
- Snapshots
- Snapshot policies
- Remote Protection
- Add a peer system
- SDR journal capacity
- Restart the replication cluster
- SDR
- Replication Consistency Group
- Replication direction and mapping
- Add a RCG
- Map RCG target volumes to SDC
- Unmap an SDC from RCG target volumes
- Set target to inconsistent mode
- Set target to consistent mode
- Modify RPO
- Add a replication pair to RCG
- Pause RCG
- Create snapshot of RCG volume
- Failover
- Reverse replication
- Restore replication
- Test Failover
- Test failover stop
- Freeze RCG
- Unfreeze RCG
- Activate RCG
- Terminate RCG
- Pause initial copy
- Resume initial copy
- Set priority
- Unpair from RCG
- VMware environment specific tasks
- Operating System Patching
Configure and Customize Dell PowerFlex v3.6.x
Jumbo Frames and the potential impact on performance
When enabling jumbo frames, one can expect approximately 10% improvement in performance if all network components fully support jumbo frames. If some network components do not fully support jumbo frames, it is recommended to use the default setting; mtu 1,500.
Prior to activating mtu settings on the logical level, set Jumbo frames = mtu 9000 on the physical switch ports that are connected to the server. Failure to do so may lead to network “disconnects” and packet drops.
Refer to your relevant vendor guidelines on how to configure jumbo frame support.
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: <>()\