I just received an email from one one of my readers, Mike Laskowski, he wanted to share the following with us:
I have over 100+ LUN’s in my environment. Round Robin is officially supported on ESX4. In the past we had a script that would manually load balance the LUN’s across FAs. ESX4 has a different way to balance the LUN’s to round robin. What you can do is build the ESX server and then in the CLI do:
esxcli nmp satp setdefaultpsp –psp VMW_PSP_RR –satp VMW_SATP_SYMM
Note: You should do this before presenting LUN’s and adding datastore. If you already have LUN’s presented and datastore added, then you do that command and then you’ll have to reboot the ESX server to take effect. This will make Round Robin the default on all LUN’s. It would take forever if you had to manually change each LUN.
THX Mike Laskowski
Please note that this example is specifically for the “SYMM” SATP. SATP stands for Storage Array Type Plugin and Symm stands for EMC DMX Symmetrix. In case you are using a different array find out what the SATP is you are using and change it accordingly.
Jason Boche says
Yeah this is on the VCDX blueprint, but I’m assuming the VI3 version. Study up!
MLaskowski says
Also just to let you know I’ll take credit for sharing this but VMware BCS support team is the one that provided the info.
THX
ML
Ernst says
The statement is true but only if you do not use a multipath pluging from an external HBA manufacturer e.g. EMC
I dont know if its possible to activate both at the same time but I would not recommend this due to the fact that this can have a conflicting effect and can make matters worse instead of better.
Jeffrey Wolfanger says
If you are doing Alua based array I believe the command is:
esxcli nmp satp setdefaultpsp –psp VMW_PSP_RR –satp VMW_SATP_ALUA
Just an FYI…
Domenico Viggiani says
For EMC Clariion:
esxcli nmp satp setdefaultpsp –-psp=VMW_PSP_RR -–satp=VMW_SATP_ALUA_CX
Terry says
in my experience you need to apply this setting prior to mapping any LUNs to your hosts. I ran this command and rebooted the host however the default policy that was in effect when i first mapped the LUN seems to be what it is using. I will have to change these manually but going forward new LUNs should follow the new default policy.