Importing device drivers

You can import individual device drivers and bundles files into the OS images repository. These files can then be used to customize Linux and Windows images.

About this task

You must ensure that the operating-system image that you intend to deploy includes the appropriate Ethernet, Fibre Channel, and storage adapter device drivers for your hardware. If the I/O adapter device driver is not included in the operating system image or profile, the adapter is not supported for OS deployment. You can create custom OS-image profiles that include the out-of-box device drivers that you need.

Lenovo XClarity Administrator supports in-box device drivers as well as predefined and custom out-of-box device drivers.
  • In-box device drivers. XClarity Administrator does not manage in-box device drivers. Always install the latest operating system to ensure that you have the latest in-box device drivers that you need.

    Note: You can add in-box device drivers to a customized Windows profile by creating a custom WinPE boot file and copying the device-driver files to the host system in the C:\drivers directory. When you create a custom OS-images profile that uses the custom boot-file, the device drivers that are in the C:\drivers directory are included in both WinPE and the final OS. They are treated as though they were inbox. Therefore, you do not need to import these in-box device drivers into XClarity Administrator when you specify device drivers to use in the custom OS-images profile creation.
  • Predefined device drivers. For ThinkSystem servers, XClarity Administrator is preloaded with a set of out-of-box device drivers for Linux to enable the installation of the operating system as well as basic network and storage configuration for the final operating system. You can add these predefined device drivers to your custom OS-image profiles, and then deploy the profiles to your managed servers

    Lenovo also bundles sets of predefined device drivers into a single package that can be downloaded from the Lenovo Windows drivers and WinPE Images Repository webpage and then imported into OS-images repository. Currently, the bundle files are available only for Windows. If the bundle file contains both device drivers and boot files, you can import the bundle file from the Device Driver or Boot Image tab.

    Note:
    • By default, the predefined OS-image profiles include the predefined device drivers.

    • You cannot delete predefined device drivers that were loaded when you installed XClarity Administrator; however, you can delete predefined device drivers that were imported from a Lenovo bundle.

    • XClarity Administrator requires that imported bundle files be signed by Lenovo. When importing a bundle file, an .asc signature file must also be imported.

  • Custom device drivers. You can import out-of-box device drivers into the OS-images repository, and then add those device drivers to a custom OS-image profile.

    You can obtain device drivers from the Lenovo YUM Repository webpage, from the vendor (such as Red Hat), or through a custom device driver that you generated yourself. For some Windows device drivers, you can generate a custom device driver by extracting the device driver from the installation .exe to your local system and creating a .zip archive file.

    The following file types are supported for importing custom device drivers.
    Operating system Supported Device Driver File Types Device Driver
    Microsoft® Windows® Server A .zip file containing the raw device-driver files, which are typically grouping of .inf, .cat, and .dll files. A .zip file containing device-driver files
    Microsoft Windows Hyper-V Server A .zip file containing the raw device-driver files, which are typically grouping of .inf, .cat, and .dll files. A .zip file containing device-driver files
    Red Hat® Enterprise Linux (RHEL) Server Driver update disk (DUD) in either an .rpm or .iso image format
    Note: If you apply a DUD .rpm to the customer profile, the .rpm is installed only to the final operating system. It is not installed in the install environment (initrd). To install a custom device driver to the initrd, import a DUD .iso and apply the .iso to the customer profile.
    Not supported
    SUSE® Linux Enterprise Server (SLES) Driver update disk (DUD) in .rpm or .iso image format
    Note: If you apply a DUD .rpm to the customer profile, the .rpm is installed only to the final operating system. It is not installed in the install environment (initrd). To install a custom device driver to the initrd, import a DUD .iso and apply the .iso to the customer profile.
    Not supported
    VMware vSphere® Hypervisor (ESXi) with Lenovo Customization Device drivers in .vib image format Not supported
    Note: The OS images repository can store an unlimited number of predefined and custom files, if space is available to store the files.

Procedure

What to do next

The device-drive image is listed on the Driver Files tab on the Manage OS Images page.

From this page, you can perform the following actions.