Hi Guys,
Long time reader first time poster. I'v just upgraded to vCentre 4.0 and upgraded our test host to vSphere. The upgrade went fine but I was curious when to run the esxcli corestorage claimrule convert command. Our test server is all local storage so when i run this command I get the following error message, which I assume is due to the local storage:
root@nexvmhp01 ~# esxcli corestorage claimrule convert
Errors:
No /adv/Disk/MaskLUNs config entry to convert!
root@nexvmhp01 ~# root@nexvmhp01 ~# esxcli corestorage claimrule convert
-bash: [root@nexvmhp01: command not found
When i come to upgrading our Blades (Dell PowerEdge M600's which are connected to a dell EMC CX240 SAN) I'm assuming the command will work. But do I run this command after each host upgrade or wait until all hosts are running vSphere before running the command? The vSphere upgrade guide doesn't really explain too much about the command, it basically just says that you need to run it, so:
When do I run the command, after all hosts have been upgraded or after each upgrade?
What exactly does this command do? and is it necessary?
Thanks
Michael
Claim rules determine which multipathing module should claim paths to a particular device and manage the device.
You only need to do this if you've used the advanced options to mask certain LUN paths prior to vSphere which would need to get converted into the new PSA (Pluggable Storage Arch) setup
Here is a doc that has more information: http://pubs.vmware.com/vsp40/wwhelp/wwhimpl/js/html/wwhelp.htm#href=fc_san_config/t_mask_paths.html
=========================================================================
William Lam
VMware vExpert 2009
VMware ESX/ESXi scripts and resources at:
VMware Code Central - Scripts/Sample code for Developers and Administrators
If you find this information useful, please award points for "correct" or "helpful".
Claim rules determine which multipathing module should claim paths to a particular device and manage the device.
You only need to do this if you've used the advanced options to mask certain LUN paths prior to vSphere which would need to get converted into the new PSA (Pluggable Storage Arch) setup
Here is a doc that has more information: http://pubs.vmware.com/vsp40/wwhelp/wwhimpl/js/html/wwhelp.htm#href=fc_san_config/t_mask_paths.html
=========================================================================
William Lam
VMware vExpert 2009
VMware ESX/ESXi scripts and resources at:
VMware Code Central - Scripts/Sample code for Developers and Administrators
If you find this information useful, please award points for "correct" or "helpful".
William,
Thanks very much for the information, much appreciated.
We had Dell implement the solution and I dont think they masked any LUNs but this was needed if we needed to fail over to a DR site. This will hopefully be taken away when we look to implement SRM.
Will it cause any issues if I run the command anyway or is it best not to?
Thanks
Michael