Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

This is extracted from the Vsphere upgrade guide ch 12 (attached):

"After the ESX/ESXi upgrade, you must convert LUN masking to the claim rule format. To do this, run the esxcli corestorage claimrule convert command in the vSphere Command-Line Interface. This command converts the /adv/Disk/MaskLUNs advanced configuration entry in esx.conf to claim rules with MASK_PATH as the plug-in. See the vSphere Command-Line Interface Installation and Reference Guide."

We have iSCSI SAN. So do we really need to do this? If so, how? And what will happen if we don't do this?

share|improve this question
add comment

3 Answers

This isn't something that you have to do unless you have implemented LUN Masking at the ESX host level. That's a relatively uncommon technique - LUN presentation should be handled at the array level and in my experience it almost always is. I can't see why it would ever be used in an iSCSI environment but there might be some odd hardware out there that required it. If you are concerned then check to see if LUN masking is configured on your hosts before you upgrade.

The risk is that you might have an environment where your SAN presents all, or some, of it's LUNs\Volumes in an uncontrolled fashion and relies on the hosts to be selective about the volumes they will actually interact with. For example, if you have a scenario where an NTFS volume that technically belongs to a Windows host is also visible to an ESX host then you could use LUN masking to prevent the ESX host corrupting that volume. This is a fairly fragile setup and that is why it is generally avoided.

Even if you have to do this that doesn't mean you will need to use the VMA. The vSphere CLI can be installed on Windows XP\2K3\2K8-64\Vista and RHEL 5.1, SLES 10\11 & Ubuntu 9.04 to allow access to most of the commands that would need to be run directly on the Service Console in older ESX versions. The VMA is handy because it's a fully self contained and preconfigured CentOS Virtual Appliance that includes the vSphere CLI, amongst other things. As JakeRobinson pointed out the Busybox CLI on ESX 4.1 can be used because it supports the ESXCLI commands so you don't actually need to install anything else if you have to do this.

share|improve this answer
add comment

You only need to apply that if you are using Fiber Channel SAN.

Here is some more info about the command, and here is an interesting thread.

If you did need to do it for some reason, you would do it from the ESX/ESXi CLI. ESXi 4.1 allows you to enter the CLI with ALT-F1.

share|improve this answer
add comment

We converted over 2000 3.5 hosts to 4, all on FC, and didn't need to do that at all.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.