This value, most generally, is derived from a WWID of some kind especially for LUNs from SAN, or VSCSI. There is a second attribute 'unique_id' that may also be used. The primary means to identify a disk (volume) is to use the PVID - which is an ID that AIX assigns when the disk (aka volume) is first assigned to a volume group. Is there a way of changing the serial number of a virtual disk or configure the serial number for a virtual disk when you add it to a VM Current virtual serial number is: A8C0-FA81.

* A related question (that you did not pose) is how does AIX keep track of a disk - is it new, or just moved within the system? I've virtualised a server that has an application installed which is license bound to the original physical hard disk serial number.

Please bind your phone number to obtain invitation bonus. ** So, who is responsible? The device driver would be my simple answer. I need to know how to find out the LUN WWN/Volume Serial on the Linux host side in CLI. What I also recall is when VPD status is changed (e.g., a new disk drive firmware) the VPD is updated. On Linux, the device used as the server host ID must reside on eth0. as a workaround, I get the output of 'uname -a' and hash it down to a 32-bit quantity and use that. * The VPD (or ODM file CuVPD (for Cu(rrent) VPD is primarily, perhaps solely, as a way to determine the firmware of a device without actually querying the device. You cannot use a volume serial number as the host ID for a Windows license server. * What I recall is that VPD is provided by the device (driver) via queries - as agent.kgb suggested.

Change volume serial number linux