BladeSystem - General
cancel
Showing results for 
Search instead for 
Did you mean: 

ESXI 4.1 U2 on BL460c G7, UUID numbers different on datastores

 
bradshr
Frequent Contributor

ESXI 4.1 U2 on BL460c G7, UUID numbers different on datastores

We have a large number of BL460c G6 blades in our vmware infrastructure. I have been asked to add a couple of BL460c G7. The C7000 enclosure has the latest release set 7.1 firmwares, and the blades have a recent SPP applied for the firmwares

 

I installed the HP supplied ISO image for ESXI 4.1 U2 (latest version). I have an issue where the order of the datastores and the UUIDs are different on the G7 hosts. An example is shown below

 

BL460C G7

 

4d2464fc-1dd4b460-bbc7-0017a4770002  DMZ_V7_1TB_PRD_LUN24_D005

4d246558-2ee70331-bfd7-0017a4770002  DMZ_V7_1TB_PRD_LUN29_D006
4d24658d-9ae39c71-b8ba-0017a4770002  DMZ_V7_1TB_PRD_LUN30_D007
4d2465c5-1afa5b21-9969-0017a4770002  DMZ_V7_1TB_PRD_LUN78_D008
4d2b3292-551be347-9f90-00265584a6fa  DMZ_V7_1TB_PRE_LUN21_D002
4d2b32e3-3f1b3464-4bb4-00265584a6fa  DMZ_V7_20GB_LUN28_SCRATCH
4d2b33e3-3d8f1950-119b-00265584a6fa  DMZ_V7_500GB_NPR_LUN18_D012
4d2b341d-8a0fd249-d9a0-00265584a6fa  DMZ_V7_650GB_NPR_LUN108_D011
4d480a01-5fc53e93-554b-002655211af2  Hypervisor1
4d480a3c-5ad48cf0-f3b1-002655211af2  Hypervisor2
4d480a5d-fd12e54f-dbf4-002655211af2  Hypervisor3
4d48214e-5a46672c-2e16-002655211af2  ISO_IMAGES_V7_200GB_LUN27_01
4d77ba14-358a93e5-a64f-002655211af2  TEMPLATE_V7_200GB_LUN25_01
4f0d757e-ee91469f-d507-002655211af2  TEMPLATE_V7_200GB_LUN26_02
4f79baf1-e8472b5e-8f83-f4ce46bb1212  TEMPLATE_V7_200GB_LUN50_03
502bc65f-d350b2b9-e4bd-f4ce46bb1212  TEMPLATE_V7_200GB_LUN51_04
DMZ_V7_1TB_NPR_LUN109_D014           bf983eeb-4996d3e1-c8e7-834f809c0777
DMZ_V7_1TB_PRD_LUN22_D003            c1cdf6e1-a21602ac-a7e0-1c05bef5040e
DMZ_V7_1TB_PRD_LUN23_D004            d10942ef-dd5b6ff5-d16c-56d5a37f5c80
=========================================================================
BL460c G6
3c3693e8-f77a642a-1910-5c6bdcb26d3a  DMZ_V7_1TB_PRD_LUN22_D003
4d2464fc-1dd4b460-bbc7-0017a4770002  DMZ_V7_1TB_PRD_LUN23_D004
4d246558-2ee70331-bfd7-0017a4770002  DMZ_V7_1TB_PRD_LUN24_D005
4d24658d-9ae39c71-b8ba-0017a4770002  DMZ_V7_1TB_PRD_LUN29_D006
4d2465c5-1afa5b21-9969-0017a4770002  DMZ_V7_1TB_PRD_LUN30_D007
4d2b3292-551be347-9f90-00265584a6fa  DMZ_V7_1TB_PRD_LUN78_D008
4d2b32e3-3f1b3464-4bb4-00265584a6fa  DMZ_V7_1TB_PRE_LUN21_D002
4d2b33e3-3d8f1950-119b-00265584a6fa  DMZ_V7_20GB_LUN28_SCRATCH
4d2b341d-8a0fd249-d9a0-00265584a6fa  DMZ_V7_500GB_NPR_LUN18_D012
4d480a01-5fc53e93-554b-002655211af2  DMZ_V7_650GB_NPR_LUN108_D011
4d480a3c-5ad48cf0-f3b1-002655211af2  Hypervisor1
4d480a5d-fd12e54f-dbf4-002655211af2  Hypervisor2
4d48214e-5a46672c-2e16-002655211af2  Hypervisor3
4d77ba14-358a93e5-a64f-002655211af2  ISO_IMAGES_V7_200GB_LUN27_01
4f0d757e-ee91469f-d507-002655211af2  TEMPLATE_V7_200GB_LUN25_01
4f79baf1-e8472b5e-8f83-f4ce46bb1212  TEMPLATE_V7_200GB_LUN26_02
502bc65f-d350b2b9-e4bd-f4ce46bb1212  TEMPLATE_V7_200GB_LUN50_03
65092bef-de8a06b5-22db-2bbbc32dc3d2  TEMPLATE_V7_200GB_LUN51_04
DMZ_V7_1TB_NPR_LUN109_D014           ff060de6-cecc88e5-4d14-8726d7ed0132
 
The storage team say that the way the LUNS are presented is the same, and is showb below
 

G6

 

id name                  SCSI_id vdisk_id vdisk_name                                                            vdisk_UID

0  BE11_B1_RTMDMZ_ESX01P 18      184      DMZ_V7_500GB_NPR_LUN18_D012    6005076802820051C8000000000000F5

0  BE11_B1_RTMDMZ_ESX01P 21      6        DMZ_V7_1TB_LUN21_D002          6005076802820051C800000000000006

0  BE11_B1_RTMDMZ_ESX01P 22      7        DMZ_V7_1TB_LUN22_D003          6005076802820051C800000000000007

0  BE11_B1_RTMDMZ_ESX01P 23      8        DMZ_V7_1TB_LUN23_D004          6005076802820051C800000000000008

0  BE11_B1_RTMDMZ_ESX01P 24      9        DMZ_V7_1TB_LUN24_D005          6005076802820051C800000000000009

0  BE11_B1_RTMDMZ_ESX01P 25      18       TEMPLATE_V7_200GB_LUN25_D001   6005076802820051C800000000000013

0  BE11_B1_RTMDMZ_ESX01P 26      19       TEMPLATE_V7_200GB_LUN26_D002   6005076802820051C800000000000014

0  BE11_B1_RTMDMZ_ESX01P 27      20       ISO_IMAGES_V7_200GB_LUN27_D001 6005076802820051C800000000000015

0  BE11_B1_RTMDMZ_ESX01P 28      21       DMZ_V7_20GB_LUN28_SCRATCH      6005076802820051C800000000000016

0  BE11_B1_RTMDMZ_ESX01P 29      33       DMZ_V7_1TB_LUN29_D006          6005076802820051C80000000000002B

0  BE11_B1_RTMDMZ_ESX01P 30      36       DMZ_V7_1TB_LUN30_D007          6005076802820051C80000000000002E

0  BE11_B1_RTMDMZ_ESX01P 50      34       TEMPLATE_V7_200GB_LUN50_D003   6005076802820051C80000000000002C

0  BE11_B1_RTMDMZ_ESX01P 51      35       TEMPLATE_V7_200GB_LUN51_D004   6005076802820051C80000000000002D

0  BE11_B1_RTMDMZ_ESX01P 78      65       DMZ_V7_1TB_PRD_LUN78_D008      6005076802820051C80000000000004B

0  BE11_B1_RTMDMZ_ESX01P 108     182      DMZ_V7_650GB_NPR_LUN108_D011   6005076802820051C8000000000000F1

0  BE11_B1_RTMDMZ_ESX01P 109     5        DMZ_V7_1TB_NPR_LUN109_D014     6005076802820051C800000000000101

 

G7

 

Below one for RTMDMZ-ESX10P.

 

IBM_2076:Trainline:admin>svcinfo lshostvdiskmap 51

id name          SCSI_id vdisk_id vdisk_name                     vdisk_UID

51 RTMDMZ-ESX10P 18      184      DMZ_V7_500GB_NPR_LUN18_D012    6005076802820051C8000000000000F5

51 RTMDMZ-ESX10P 21      6        DMZ_V7_1TB_LUN21_D002          6005076802820051C800000000000006

51 RTMDMZ-ESX10P 22      7        DMZ_V7_1TB_LUN22_D003          6005076802820051C800000000000007

51 RTMDMZ-ESX10P 23      8        DMZ_V7_1TB_LUN23_D004          6005076802820051C800000000000008

51 RTMDMZ-ESX10P 24      9        DMZ_V7_1TB_LUN24_D005          6005076802820051C800000000000009

51 RTMDMZ-ESX10P 25      18       TEMPLATE_V7_200GB_LUN25_D001   6005076802820051C800000000000013

51 RTMDMZ-ESX10P 26      19       TEMPLATE_V7_200GB_LUN26_D002   6005076802820051C800000000000014

51 RTMDMZ-ESX10P 27      20       ISO_IMAGES_V7_200GB_LUN27_D001 6005076802820051C800000000000015

51 RTMDMZ-ESX10P 28      21       DMZ_V7_20GB_LUN28_SCRATCH      6005076802820051C800000000000016

51 RTMDMZ-ESX10P 29      33       DMZ_V7_1TB_LUN29_D006          6005076802820051C80000000000002B

51 RTMDMZ-ESX10P 30      36       DMZ_V7_1TB_LUN30_D007          6005076802820051C80000000000002E

51 RTMDMZ-ESX10P 50      34       TEMPLATE_V7_200GB_LUN50_D003   6005076802820051C80000000000002C

51 RTMDMZ-ESX10P 51      35       TEMPLATE_V7_200GB_LUN51_D004   6005076802820051C80000000000002D

51 RTMDMZ-ESX10P 78      65       DMZ_V7_1TB_PRD_LUN78_D008      6005076802820051C80000000000004B

51 RTMDMZ-ESX10P 108     182      DMZ_V7_650GB_NPR_LUN108_D011   6005076802820051C8000000000000F1

51 RTMDMZ-ESX10P 109     5        DMZ_V7_1TB_NPR_LUN109_D014     6005076802820051C800000000000101

 

Has anyone seen this issue on ESXI 4.1 U2 on BL460c G7s? The storage is an IBM V7000

1 REPLY
Steven Clementi
Honored Contributor

Re: ESXI 4.1 U2 on BL460c G7, UUID numbers different on datastores

You can check the LUN numbers from the vClient and/or vCenter on the Configuration tab, Storage Adaptors menu link.  Click your HBA and compare between the 2 servers in question.

 

Are he Host profiles on the Storage Array configured the same?

 

Are the G6's running the same version? 4.1 U2...

 

There IS a different HBA in the G7 and thus... could be causing some of the confusion.  make sure the firmware on the FlexAdaptor is up to date, there have been issues (major issues) with the initial releases of the HBA firmware.  Current is/was 4.1.402.20, looks like there is a new version as of 9/4/12 (v. 4.1.450.7

 

Make sure you have the most up to date driver too.

Steven Clementi
HP Master ASE, Storage and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5)
RHCE
NPP3 (Nutanix Platform Professional)