- Notes, cautions, and warnings
- Introduction
- Revision history
- PowerFlex overview
- System requirements and product limits
- Architecture
- System
- MDM cluster
- Virtual IP addresses
- Storage definitions
- Storage pools
- Acceleration pools
- Data layout
- Volumes
- Naming PowerFlex objects
- NVMe over TCP overview
- PowerFlex file services
- Replication
- Replication peer systems
- Storage data replicator
- Journal
- Replication consistency group
- Replication pairs
- Recovery point objective
- Replication I/O flow
- Replication auto-provision
- Replication initial copy
- Activating or terminating a replication consistency group
- Pausing replication
- Using replicated volumes
- Accessing target volumes
- Setting up replication
- Dell APEX Block Storage
- Protection and load balancing
- Cache
- Networking requirements and limitations
- SDC connection monitoring
- SMART hardware monitoring
- Snapshots
- Performance
- Migrating volumes
- Implementing PowerFlex
- Additional functions
- Maintenance
- PowerFlex management
- Configure direct attached storage
Dell PowerFlex 4.6.x Technical Overview
Networking limitation
When deployed on VMware, PowerFlex, the same IP Subnet can be configured on different VM kernel interfaces\virtual switches.
For more information, see the VMware ESXi limitation.
PowerFlex only supports the following network configurations when deployed on VMware:
- A single data storage network
- Two or more data networks, each on separate IP subnets
- A single IP address data network using several NIC-bonding configurations, or vSwitch load-balancing
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: <>()\