Administer > SA Provisioning > SA Provisioning common use cases > HPE ProLiant Driver Update Disk (DUD)

HPE ProLiant Driver Update Disk (DUD)

The HPE ProLiant Driver Update Disk APX ensures that the ProLiant drivers for the network boot Service OS can be updated outside of an SA release. The APX should be requested from HPE if there is indication that the service OS does not support the hardware in use, like network devices or hard disks are not visible.

Steps for importing and running the HPE ProLiant DUD APX:

  1. Unzip the APX zip to a custom directory on SA Core, eg. "/tmp/dud".
  2. Import it with the following command:

    $ apxtool import -f /<path/to/destination> -c <path/to/apx>

    Eg.: $ apxtool import -f /APXs -c /tmp/dud

  3. Log in to the SA Client as a user who belongs to the Advanced Users group.

  4. Find and open the APX by using one of the 2 methods below:

    1. In the navigation pane, select Library, then By Type. Open the Extensions node and select the Program node. This displays all the program APXs in the SA Library. The imported APX should be there. If "ProLiant Driver update for PXE based Linux Service OS" is not listed, make sure that the user has the necessary permissions. For APX related permission settings, please refer to the SA Developer section. Select "ProLiant Driver update for PXE based Linux Service OS" APX.
    2. In the navigation pane, select the Library tab, then the By Folder tab, and finally select the path <path/to/destination> used above. Select "ProLiant Driver update for PXE based Linux Service OS" APX.

  5. Select Actions > Run menu item. This displays the Run Program Extension wizard.

  6. Select Next.
  7. Select Start Job.

  8. When the APX finishes, select the status indicator to display details.
  9. Select Close.

Note The APX contains the original Service OS files with the latest drivers, so in case there was a hotfix applied to Service OS files, it should be reapplied after each DUD APX run.

For more information about APX import and apxtool, refer to the SA Developer section.