VMware Cloud Community
TICTOC201110141
Enthusiast
Enthusiast
Jump to solution

UUID mis-match

hp eva 6300 create simple VMFS 5 - ESXI 5.5 U2 find and add the datastore, (note I shortened this down hoping you already know how to do these parts.)  Add HS to VM by browsing to the VMFS datastore - set to thin and done.

BUT - the VMFS UUID in the HP EVA 6300 (any I have found so far) does not transfer to the VM. So if I do a /dev/disk  cd by-uuid / ls I get nothing close the EVA UUID.

I checked  my ESXI Host and using esxcli storage core path I get

fc.50060b0000c30a01:50060b0000c30a00-fc.50014380025dac20:50014380025dac28-naa.60                                                                    0508b4000d224f00058000013e0000

   UID: fc.50060b0000c30a01:50060b0000c30a00-fc.50014380025dac20:50014380025dac2                                                                    8-naa.600508b4000d224f00058000013e0000

   Runtime Name: vmhba1:C0:T18:L6

   Device: naa.600508b4000d224f00058000013e0000

   Device Display Name: vmfs0006-avenger-nfs-3par0009

   Adapter: vmhba1

   Channel: 0

   Target: 18

   LUN: 6

   Plugin: NMP

   State: active

   Transport: fc

   Adapter Identifier: fc.50060b0000c30a01:50060b0000c30a00

   Target Identifier: fc.50014380025dac20:50014380025dac28

   Adapter Transport Details: WWNN: 50:06:0b:00:00:c3:0a:01 WWPN: 50:06:0b:00:00                                                                    :c3:0a:00

   Target Transport Details: WWNN: 50:01:43:80:02:5d:ac:20 WWPN: 50:01:43:80:02:                                                                    5d:ac:28

   Maximum IO Size: 33553920

You can see the EVA UUID is in the FC line (0508b4000d224f00058000013e0000) but not in the UUID line except where there is a 8-naa.600 - has been added to the front of the UUID, then when you add the drive and check the UUID or in my case try to use it to find the new drive

00152e47-08cc-4ea1-ab52-e3c8d5e08d8c  62256eb0-c48f-4619-a505-995c21580751

0076555b-140a-42d5-9520-79799777667d  a2d016dc-9050-4dd5-b192-7ad2dc262cca

16c4abd9-cf49-4cde-a3b8-3c88b927a1ee  ad82018a-6842-4cde-a1de-5c37f0659afa

28a05ac6-a2e9-48ab-828e-08d1af1e5b02  b80ebba8-46b1-4903-9e4a-da51857138de

299b6638-52ab-4831-9a78-739fd2882c65  eb5de04f-515c-4505-bc5b-a73d7845a7ed

398bd6d9-8438-4bb7-9a05-967513899a04  f1097a8b-dd84-4325-a1ae-e0e06cb9abef

4567bb4f-086e-45d9-ad71-47d9b01761f7  fbca974a-529a-482d-916e-920b044df3e8

So my question is Why is the UUID not being passed through to the VM as it is in the storage??

1 Solution

Accepted Solutions
JarryG
Expert
Expert
Jump to solution

Not sure which UUID-version is ESXi-using, but AFAIK part of every UUID is uniquely generated (i.e. random-bytes, time-stamp, mac-address, fqdn-hash, or whatever). So ESXi can not pass-through the same UUID to VM, because VM will generate its own. Check RFC4122 for more info...

_____________________________________________ If you found my answer useful please do *not* mark it as "correct" or "helpful". It is hard to pretend being noob with all those points! :winking_face:

View solution in original post

2 Replies
JarryG
Expert
Expert
Jump to solution

Not sure which UUID-version is ESXi-using, but AFAIK part of every UUID is uniquely generated (i.e. random-bytes, time-stamp, mac-address, fqdn-hash, or whatever). So ESXi can not pass-through the same UUID to VM, because VM will generate its own. Check RFC4122 for more info...

_____________________________________________ If you found my answer useful please do *not* mark it as "correct" or "helpful". It is hard to pretend being noob with all those points! :winking_face:
TICTOC201110141
Enthusiast
Enthusiast
Jump to solution

Makes sense now thank you. Been fighting a very odd EVA issue and I am done to grasping straws. Here's an outline

RHEL 6.5 / ESXI 5.5 U2 / vCenter 5.5 small farm / EVA's are 6300 to 8400'S

RHEL has 7 datastores attached 8TB each 001 002 003 005 006 007 009 these are attached using the add HD browse to datastore nothing to hard there. But if you notice the numbers are out of sync because 005 and 008 will not add to the RHEL Box. You can add them in as a new HD but even with a reboot they will not show up. Just like now 010 will not show up but as soon as I make 011 it will without reboot. I run a A/B switch with failover and odd luns on B and evens on A. tried swapping them in the fail over switch and still nothing. 

Try wrapping that around in your head for a few days :slightly_smiling_face:

Oh and the 005 008 can be added to any other Linux box, sometime with sometime without a reboot,  or Windows box and pass all of the storage tests I have.

That makes it just freaky.

Again thanks for the heads up!

Reply
0 Kudos