VMware Cloud Community
TheDonMiguel
Contributor
Contributor
Jump to solution

Using RAW LUN with Cluster

Hello together

I've a Windows Cluster which is using RAW LUNs. The first Node is physical and the second one is installed on VMware ESX. It worked very well on ESX 2.5.3. For the v3 migration VC needs to remove the RAW LUNs from the VM HW Config. Since I've the VM is ont VMFS3, it's not possible to add the RAW LUNs again. On 95% I'll get "Operation failed due to concurrent modification by another operation". What do I've to do, that I can add the harddisks?

Thanks,

Miguel

0 Kudos
1 Solution

Accepted Solutions
martin_schmidt
Enthusiast
Enthusiast
Jump to solution

Although that can be done when active node is in production (according to http://kb.vmware.com/kb/1862), I would do this during an uncritical time.

vmkfstools –L lunreset /vmfs/devices/disks/vmhba.vmdk

This sets a pointer to the RDM disk.

"-L lunreset" is necessary to unlock the RDM temporarily from the active cluster node.

This is uncritical since the active cluster node makes another SCSI reservation after three seconds.

vmkfstools –z creates the passthrough devices. This can be stored anywhere on the VMFS.

I would recommend the VMs home folder.

Add the VMDKs to the VM, either directly in the vmx file or from within the VMs settings.

View solution in original post

0 Kudos
4 Replies
Texiwill
Leadership
Leadership
Jump to solution

Hello,

First make sure that the LUNs are presented to the ESX Host. They appear to be.

Make sure the VM is powered off and then add the LUNs to the VM.

If that does not work, then edit the VM configuration file and add the appropriate lines. They will be in the origianl VMX configuration file.

You should then be able to boot the VM.

Best regards,

Edward

--
Edward L. Haletky
vExpert XIV: 2009-2023,
VMTN Community Moderator
vSphere Upgrade Saga: https://www.astroarch.com/blogs
GitHub Repo: https://github.com/Texiwill
TheDonMiguel
Contributor
Contributor
Jump to solution

Hello Edward

Thanks for answering! Yes, the LUNs are presented to all ESX Hosts and the VM ist powered off when I'm trying the hw-changes. Because I do not have to org. VMX anymore can you help me what I should add to the config file? I know that it should be physically and on SCSI ID 1. I know all the original SCSI Numbers for the needed LUNs.

Thanks

Miguel

0 Kudos
TheDonMiguel
Contributor
Contributor
Jump to solution

Ta ta, it works now. This KB does describe the solution: http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&externalId=1862

0 Kudos
martin_schmidt
Enthusiast
Enthusiast
Jump to solution

Although that can be done when active node is in production (according to http://kb.vmware.com/kb/1862), I would do this during an uncritical time.

vmkfstools –L lunreset /vmfs/devices/disks/vmhba.vmdk

This sets a pointer to the RDM disk.

"-L lunreset" is necessary to unlock the RDM temporarily from the active cluster node.

This is uncritical since the active cluster node makes another SCSI reservation after three seconds.

vmkfstools –z creates the passthrough devices. This can be stored anywhere on the VMFS.

I would recommend the VMs home folder.

Add the VMDKs to the VM, either directly in the vmx file or from within the VMs settings.

0 Kudos