Hi Matteo,

The settings habe changed in 5.5. You need to disable PDL AUtoRemove on each Host (set Advanced Setting "/Disk/AutoremoveOnPDL" to "0").

See also here;

• http://www.yellow-bricks.com/2013/11/08/disable-disk-autoremoveonpdl-vmsc-environment/
• http://kb.vmware.com/kb/2059622
• http://longwhiteclouds.com/2013/11/08/vsphere-metro-stretched-cluster-with-vsphere-5-5-and-pdl-autoremove/

Also VPLEX devices might be recognized as SSD, which is wrong. I have created a custom nmp rule on each host, that also enables RR by default for VPlex Devices:

esxcli storage nmp satp rule add –satp VMW_SATP_INV –vendor “EMC” –model “Invista” –option “disable_ssd” –description “VPLEX custom” –psp “VMW_PSP_RR”

Oliver

Hi

your DRS setting can prevent VM automatically restarting on another host. If your DRS setting ties the VM to that host then HA won't override. Need to set DRS to should run on, rather than must.

Hi Oliver,

In a cross site configuration with vmware 5.5 witch is the correct multipath configuration ..RR or fixed?

thanks

Matteo

As Steve mentioned

Non cross connected configurations recommend to use adaptive pathing policy in all cases. Round robin should be avoided especially for dual and quad systems.

For cross connected configurations, fixed pathing should be used and preferred paths set per Datastore to the local VPLEX path only taking care to alternate and balance over the whole VPLEX front end (i.e. so that all datastores are not all sending IO to a single VPLEX director).

MT

Hi MT

We've configured Fixed policy for VPLEX's datastores, I've asked about the correct mp policy after reading Oliver's post with esxcli's command.

Matteo

Hi Intech..

thanks for your reply, but the Oliver's post tells to configure mp is this way

esxcli storage nmp satp rule add –satp VMW_SATP_INV –vendor “EMC” –model “Invista” –option “disable_ssd” –description “VPLEX custom” –psp “VMW_PSP_RR”

But the rule is applied for VMW_SPS_RR, do I have to use VMW_PSP_FIXED?

thanks

Matteo

Fixed. Set preferred path to local cluster

Steve Aldous

Sent from my iPhone

Hi matteo,

For cross-connected sites (uniform host access) use either VMware Fixed Path Policy, or PowerPath with auto-standby. For non-cross connected use VMware RoundRobin.

With ESX Hosts and VPLEX residing in the same failure domain I see no good reason for using cross-connect. In that case, if VPLEX fails, your hosts fail, too.

Oliver

Isn't the default PSP for Invista already Fixed? If so, only "disable_ssd" is needed. But: If you use Fixed you need to define the preferred Path on Each Host to each LUN!

I have made a quick check with

# esxcli storage nmp satp list

I suggest to update the proposed string to

esxcli storage nmp satp rule add –satp VMW_SATP_INV –vendor “EMC” –model “Invista” –option “disable_ssd” –description “VPLEX custom” –psp “VMW_PSP_FIXED”

Can somebody confirm this proposal?

Thank you!