Updating the Universal Unique Identifier (UUID)

The Universal Unique Identifier (UUID) must be updated when the system board is replaced.

The Universal Unique Identifier (UUID) must be updated when the system board is replaced. Use the Advanced Settings Utility (ASU) to update the UUID in the UEFI-based server. The ASU is an online tool that supports several operating systems. Make sure that you download the version for your operating system. You can download the ASU from the IBM Web site. To download the ASU and update the UUID, complete the following steps.

Note: Changes are made periodically to the IBM Web site. The actual procedure might vary slightly from what is described in this document.
  1. Download the Advanced Settings Utility (ASU):
    1. Go to http://www.ibm.com/systems/support/.
    2. Under Product support, select BladeCenter.
    3. Under Popular links, select Tools and utilities.
    4. Scroll down to Configuration; then, select Advanced Settings Utility (ASU).
    5. In the next window under Download, click the Advanced Settings Utility link and download the ASU version for your blade server.
      Note: To view more information about using the Advanced Settings Utility, scroll down to Online Help; then, click User's Guide for the IBM Advanced Settings Utility.
    6. In the next window under File link, click the Advanced Settings Utility link for your operating system to begin downloading the utility.
  2. ASU sets the UUID in the Integrated Management Module (IMM). Select one of the following methods to access the Integrated Management Module (IMM) to set the UUID:
    • Online from the target system (LAN or keyboard console style (KCS) access)
    • Remote access to the target system (LAN based)
    • Bootable media containing ASU (LAN or KCS, depending upon the bootable media)
      Note: IBM provides a method for building a bootable media. You can create a bootable media using the Bootable Media Creator (BoMC) application from the Tools Center Web site. In addition, the Windows and Linux based tool kits are also available to build a bootable media. These tool kits provide an alternate method to creating a Windows Professional Edition or Master Control Program (MCP) based bootable media, which will include the ASU application.
  3. Copy and unpack the ASU package, which also includes other required files, to the server. Make sure that you unpack the ASU and the required files to the same directory. In addition to the application executable (asu or asu64), the following files are required:
    • For Windows based operating systems:
      • ibm_rndis_server_os.inf
      • device.cat
    • For Linux based operating systems:
      • cdc_interface.sh
  4. After you install ASU, use the following command syntax to set the UUID:

    asu set SYSTEM_PROD_DATA.SysInfoUUID <uuid_value> [access_method]

    Where:
    <uuid_value>
    Up to 16-byte hexadecimal value assigned by you.
    [access_method]
    The access method that you selected to use from the following methods:
    • Online authenticated LAN access, type the command:

      [host <imm_internal_ip>] [user <imm_user_id>][password <imm_password>]

      Where:

      imm_internal_ip
      The IMM internal LAN/USB IP address. The default value is 169.254.95.118.
      imm_user_id
      The IMM account (1 of 12 accounts). The default value is USERID.
      imm_password
      The IMM account password (1 of 12 accounts). The default value is PASSW0RD (with a zero 0 not an O).
      Note: If you do not specify any of these parameters, ASU will use the default values. When the default values are used and ASU is unable to access the IMM using the online authenticated LAN access method, ASU will automatically use the unauthenticated KCS access method.
      The following commands are examples of using the userid and password default values and not using the default values:

      Example that does not use the userid and password default values:
      asu set SYSTEM_PROD_DATA.SYsInfoUUID <uuid_value> user <user_id>
      password <password>


      Example that does use the userid and password default values:
      asu set SYSTEM_PROD_DATA.SysInfoUUID <uuid_value>

    • Online KCS access (unauthenticated and user restricted):

      You do not need to specify a value for access_method when you use this access method.

      Example:
      asu set SYSTEM_PROD_DATA.SysInfoUUID <uuid_value>

      The KCS access method uses the IPMI/KCS interface. This method requires that the IPMI driver be installed. Some operating systems have the IPMI driver installed by default. ASU provides the corresponding mapping layer. See the Advanced Settings Utility Users Guide for more details. You can access the ASU Users Guide from the IBM Web site.

    • Remote LAN access, type the command:
      Note: When using the remote LAN access method to access IMM using the LAN from a client, the host and the imm_external_ip address are required parameters.

      host <imm_external_ip> [user <imm_user_id>[[password <imm_password>]

      Where:

      imm_external_ip
      The external IMM LAN IP address. There is no default value. This parameter is required.
      imm_user_id
      The IMM account (1 of 12 accounts). The default value is USERID.
      imm_password
      The IMM account password (1 of 12 accounts). The default value is PASSW0RD (with a zero 0 not an O).
      The following commands are examples of using the userid and password default values and not using the default values:

      Example that does not use the userid and password default values:
      asu set SYSTEM_PROD_DATA.SYsInfoUUID <uuid_value> host <imm_ip>
      user <user_id> password <password>


      Example that does use the userid and password default values:
      asu set SYSTEM_PROD_DATA.SysInfoUUID <uuid_value> host <imm_ip>

    • Bootable media:

      You can also build a bootable media using the applications available through the Tools Center Web site at http://publib.boulder.ibm.com/infocenter/toolsctr/v1r0/index.jsp. From the left pane, click IBM System x and BladeCenter Tools Center, then click Tool reference for the available tools.

  5. Restart the server.