Two ProLiant servers with same UUID

[alvaroag]

Hi. I'm having a problem with two ProLiant ML110 G6 servers. We are preparing a software licenseing solution which uses the computer UUID. All the servers which we are going to install the software in(30 Proliant ML, 1 IBM x, and 3 compatible PCs) have different UUID, except two of the ProLiant servers. We work with Linux and access the UUID via /sys/class/dmi/id/product_uuid. Here are the values for both servers(all except RAM named after the file name in /sys/class/dmi/id):

Server A:

product_name: ProLiant ML110 G6
product_serial: MX201401CV
product_uuid: 00112233-4455-6677-8899-AABBCCDDEEFF
sys_vendor: HP
board_name: ProLiant ML110 G6
board_serial: 0123456789
board_vendor: Wistron Corporation
chassis_serial: MX201401CV
chassis_type: 7
chassis_vendor: HP
chassis_version: N/A
RAM: 8Gb (More than factory default)

Server B:

product_name: ProLiant ML110 G6
product_serial: 0123456789
product_uuid: 00112233-4455-6677-8899-AABBCCDDEEFF
sys_vendor: HP
board_name: ProLiant ML110 G6
board_serial: 0123456789
board_vendor: Wistron Corporation
chassis_serial: 0123456789ABCDEF
chassis_type: 7
chassis_vendor: HP
chassis_version: N/A
RAM: 3Gb (More than factory default)

As anyone can see, both have the same UUID, which is a problem for the licensing software. The worst is that both computers belong to the same company, so they could use the license of one into another if we block one of the licenses.

Hope some can help me. Thanks in advance. 

[Suman_1978]

Hi,

The UUID looks like it was not at all set on the server.

UUID number can be established by using the Setsys.exe Utility to set the UUID to a random value. The latest Setsys.exe Utility for ProLiant 100 Series servers is available for download.

http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=US&swItem=MTX-1d48ae3f19d945b481c20736d6&prodTypeId=15351&prodSeriesId=3186395

Refer to "Installation Instructions" for help.

[Goutham_Sabala]

The Utility that can resolve the UUID issue can be found here

http://bizsupport1.austin.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=15351&prodSeriesId=3580694&swItem=MTX-1d48ae3f19d945b481c20736d6&prodNameId=3580695&swEnvOID=2081&swLang=8&taskId=135&mode=4&idx=1

(Please check the utility download page ‘Description’ tab- This utility should be used to set and display Serial Number and UUID on ProLiant 100 series G5 and G6 Servers.)

Installation:

1. Download the SoftPaq to a directory on a system running Microsoft Windows 2000, Microsoft Windows Server 2003, Microsoft Windows Server 2008, Microsoft Windows XP, or Microsoft Windows Vista and change to that directory.
The file that is downloaded is SP44052.EXE.

2. From that drive and directory, execute the downloaded SoftPaq file:
SPxxxxx [ENTER]
Select the create a bootable USB key option to create a bootable USB key.

3. After the USB key is created, you may delete the downloaded file if you wish.

4. Boot the USB key and at the DOS prompt refer to the Setsys.TXT file for the SETSYS.EXE command line instructions.

5. SetSys.exe command options are as follows
SETSYS [/S|/U|/A|/M|/K|/?] <string>
/S - Set Serial Number
S/N has a MAX length of 16 chars (16 digits).
(e.g. SETSYS /S=1234567890XYZEFG)
/U - Set UUID
UUID must be exactly 16 Bytes (32 digits) in length.
Digits must be 0-9 and A-F (CAPS) only.
(e.g. SETSYS /U=1234567890ABCDEF1234567890ABCDEF)
/A - Set Chassis Asset Tag
Asset Tag has a MAX length of 16 chars (16 digits).
(e.g. SETSYS /A=MAINSERVER123456)
/M - Set Manufacturer String
Manufacturer string has a MAX length of 16 chars.
(e.g. SETSYS /M=HP)
/K - Set SKU ID String
SKU Number String has a MAX length of 16 chars.
(e.g. SETSYS /K=AG655A)
/? - Help
SETSYS w/o any Args displays current values.

The cause of duplicate/orphans UUID/GUID is -
“Occasionally, this reallocation can happen through simultaneous DHCP address assignment changes and a system rename. Other causes can include a move of the operating system (image cloning) from one blade/Server to another through different virtualization mechanisms such as a physical-to-physical system move or replacement of a system board that has not be configured the same as the original system board.
In HP SIM, you can name orphan systems in the following ways:
<serialNumber> Where <serialNumber> is replaced with the serial number of the system.
• <serialNumber>-<devKey>-<oldName> Where <serialNumber> is replaced with the serial number of the system, <devKey> is replaced with the devKey on the system, and oldName> is replaced with the old system name.
• <devKey> Where <devKey> is replaced with the devKey on the system.”