HP EVA P6000 Guia do Utilizador descarregar pdf (Página 22)

Figure 8 shows a typical multi-pathing implementation using vSphere 4.x/5.

Figure 8. EVA connectivity with vSphere 4.x/5

All I/Os to Vdisks 1 – 4 are routed through one or more ports on Controller 1 and through Paths 

and/or , regardless of the HBA that originates the I/O. Similarly, all I/Os to Vdisks 5 – 7 are

routed to Controller 2 through Paths  and/, regardless of the originating HBA.

The vSphere 4.x/5 implementation yields much higher system resource utilization and throughput

and, most importantly, delivers a balanced system out of the box, with no intricate configuration

required.

Note

From the perspective of Vdisk access, you can easily balance vSphere 4.x

with an EVA array. However, it may be desirable to capture performance

metrics at the EVA and assess data access to/from each controller to

ensure that the workload is truly balanced between the two controllers.

Using Fixed_AP I/O path policy

Because it is ALUA-aware, Fixed_AP I/O path policy can extend the functionality of Fixed I/O path

policy to active-passive and ALUA-aware arrays. In addition, Fixed_AP can identify the preferred

controller for a Vdisk.

Despite being ALUA aware, Fixed_AP’s primary path selection attribute is the preferred controller

setting of a Vdisk and not just its access state.

1 2 ... 17 18 19 20 21 22 23 24 25 26 27 ... 73 74

Sem comentários

HP EVA P6000 Guia do Utilizador Página 22