DIFFERENT LUN ID ALLOCATION TO ESX HOSTs
I’ve seen twice this week vMotion operation failed for some VMs with RDM due to ESX hosts unable to find the path for RDM vdisk. Though all 4x ESX hosts able to to see the LUNs when I rescanned it, but still I’m inexplicably failed to vMotion the VMs. So, what are the things causing this actually?.
Fact-Finding
- Both issue happened on ESX 3.5 and ESX 4.0 environment
- ESX 3.5 environment with Falconstor NSS as target storage while
- ESX 4.0 environment with HP Eva as target storage
- All ESX hosts able to see a bunch of LUNs without problem
Initial investigation for ESX 4.0 environment (HP Eva) with small number of LUNs (6) I found out, this is due to different LUN ID presented to 4x ESX hosts. Strangely, all ESX hosts able to see all LUNs and I even can browse the datastore without any issue except for vMotion. Read more
1 comment
