Unsolved

This post is more than 5 years old

1 Rookie

 • 

30 Posts

3469

August 6th, 2011 03:00

VNX5100 system configuration optimization for VMware vSphere 4.1 infrastructure

- As per the information I have gathered from the VMware vSphere Client when verifying the multipathing policy VMware ESXi automatically pre-decided for our VNX5100 upon installation, the SATP Plugin that has been automatically pre-configured based on the array type is “VMW_SATP_CX” and the multipathing policy is “VMW_PSP_MRU”.

11 Legend

 • 

20.4K Posts

 • 

87.4K Points

August 7th, 2011 06:00

1) as long as each HBA is zoned to SPA and SPB, can't think of anything else. Maybe setup "configUpload" script to backup switch configuration ?

3) Take a look at this guide, there is a section for MPIO : EMC Host Connectivity Guide for Windows  -- A45

4) This document gives some guidelines on cache configuration : h8268-vnx-block-best-practices.pdf

1 Rookie

 • 

30 Posts

August 10th, 2011 07:00

Hi dynamox,

thank you for your reply.

What about the best/recommended storage multipathing and failover configuration for VMware ESXi 4.1 Update 1 ?

Thank you again for your contribution to this technical discussion.

Massimiliano

1 Rookie

 • 

30 Posts

August 11th, 2011 05:00

Hi there,


after playing around a little bit more, I believe I have finally managed to configure the best/recommended storage multipathing and failover configuration for VMware ESXi 4.1 hosts connected to a VNX5100 block system.


The steps I have just performed are described below:

1) I have used the Unisphere Failover Setup wizard to set the system failover values for all HBA initiators belonging to the VMware ESXi 4.1 hosts as follows:

- Initiator Type has been set to CLARiiON Open
- Array CommPath has been set to Enabled
- Failover Mode has been set to 4 to support ALUA

2) I have rebooted the VMware ESXi 4.1 hosts for the initiator records to take affect.


After rebooting the VMware ESXi 4.1 hosts, as per the information I have gathered from the VMware vSphere Client when verifying the multipathing policy VMware ESXi decided for our VNX5100 upon reboot after setting the system failover values for all HBA initiators, the SATP Plugin that has been reconfigured to “VMW_SATP_ALUA_CX” as per VMware compatibility list (based on the VNX5100 array now supporting ALUA) and the multipathing policy is “VMW_PSP_FIXED_AP” (see images below).

Is that correct ?

Thanks an Regards,

Massimiliano

==================================================

Immagine.pngImmagine.png

0 events found

No Events found!

Top