Several examples are shown in this section to help you understand MPIO path behavior given a Microsoft failover cluster or Hyper-V cluster configured locally, or over metro distance.
The examples show Fibre Channel (FC) connectivity with two fabrics for redundancy. Use of iSCSI is also supported. The architecture and MPIO path behavior is similar regardless of the transport.
Single site with co-located PowerStore systems
This example shows a path configuration example when you choose Metro Connectivity - Co-located with both systems.
Figure 78. PowerStore Manager Metro Connectivity – Co-located with both systems option
See Figure 79 as you review the following configuration example:
- Node A on each PowerStore system owns a Metro Volume and presents AO paths to each cluster server node.
- Node B on each PowerStore system presents AU paths.
- Dual storage fabrics (or networks) increases resilience.
- Two Windows failover cluster nodes or Hyper-V cluster nodes are uniformly mapped as co-located hosts.
- Each server node has a two-port FC HBA with one port connected to each fabric.
- Four FC ports are connected from each PowerStore system: two from Node A, and two from Node B.
- The configuration presents eight paths to each host. Four paths are AO, and four paths are AU.
Figure 79. AO and AU paths in a co-located Metro Volume configuration
Multisite with non-uniform server mappings
This example shows a path configuration when you have a stretched cluster that is not uniformly mapped to both PowerStore systems. Choose the Local Connectivity option in PowerStore Manager for this configuration.
Figure 80. Use the PowerStore Manager Local Connectivity option for non-uniform mappings
See Figure 81 as you review the following configuration example:
- Node A on each PowerStore system owns a Metro Volume and presents AO paths to each local cluster server node.
- Node B on each PowerStore presents AU paths.
- Dual fabrics (or networks) increases resilience.
- Two Windows failover cluster or Hyper-V cluster nodes are non-uniformly mapped as local hosts.
- Each server node has a two-port FC HBA with one port connected to each fabric.
- Four FC ports are connected from each PowerStore system: two from Node A, and two from Node B.
- The configuration presents four paths to each host. Two paths are AO, and two paths are AU.
Figure 81. Non-uniform server mappings path example
Multisite with uniform server mappings
This example shows a path configuration when you have a stretched cluster that is uniformly mapped to both PowerStore systems. Choose the correct Host Connectivity option in PowerStore Manager based on the location of the host server.
- Host is co-located with this system (with the “local” PowerStore system)
- Host is co-located with the remote system (with the “remote” PowerStore system)
Figure 82. Choose the correct Metro Connectivity option: co-located with the local system, or co-located with the remote system
See Figure 83 as you review the following configuration example:
- Node A on each PowerStore system owns a Metro Volume and presents AO paths to each fabric.
- The Host Configuration option selected in Figure 82 determines how the server nodes detect the paths.
- Node B on each PowerStore presents AU paths.
- Dual fabrics (or networks) increases resilience.
- Two Windows failover cluster or Hyper-V cluster nodes are uniformly mapped.
- Each server node has a two-port FC HBA with one port connected to each fabric.
- Four FC ports are connected from each PowerStore system: two from Node A, and two from Node B.
- The configuration presents eight paths to each server node. Two paths are AO, and six paths are AU.
Figure 83. Uniform server mappings path example