ESX 3.01 Upgrade in Mixed 2.5.2 Farm

[shakeking]

I upgraded one of our ESX 2.5.2 servers to 3.01 after VMotioning all the servers to the other 2 2.5.x servers. I have been creating new VMFS3 LUN's on our EMC CX300 and copying the .vmdk files one at a time over to the new LUNs and upgrading the VM Hardware and Tools. However, whenever I add another LUN to the ESX storage group, it always shows up as LUN9 when I click add Storage in the VMI client. Then, the ESX 3.x box can no longer see the previous LUN I created. This is the same process for each new LUN I try to allocate, it seems to conflict with the previous one so I can add more than 1 LUN to the ESX 3.x server. Anyone run into this before?

Jonathan

[GBromage]

Hi Jonathan!

If you look at the Storage adapter, can it see the SCSI IDs for the other LUNs?

If it can't the problem is with the SAN configuration.

If it can, the problem might be with the LUN signatures. Try going to Configuration -> Advanced Settings -> LVM and set LVM.DisableSnapshotLun to '0'

Hope that helps,

Greg