OpenManage Integration for VMware vCenter Version 4.2

Creating repository profile

  1. On the OpenManage Integration for VMware vCenter page, click Manage > Baseline, expand Baseline Info, and then click Repository Profile.

  2. Click Create
a Hardware Profile..

  3. On the Welcome page, read the instructions, and click Next to add further details:

    1. In the Profile Name box, type the repository profile name.
    2. In the Profile Description field, type a description, which is optional.
    3. Click Next.

  4. In the Profile Settings dialog box, select one of the following repository types:

    • Firmware (By default, this option is selected)
    • Driver
    1. In the Repository Share Location field, type the repository share location (CIFS or NFS).
    2. For CIFS share, type the user name and password. The characters that are not allowed for the password are: &, !, @, %, and <.
      NOTE: OMIVV supports only Server Message Block(SMB) version 1.0 and SMB version 2.0 based CIFS shares.
    3. To validate the access for the given repository path and existence of the catalog file for firmware and driver repository, click Begin Test. This validation is mandatory to continue further.

      Test
connection is successful.: Indicates that the test connection is successful.

      Test
connection is failed.: Indicates that the test connection is failed.

    4. Click Next.
    NOTE: For driver repository, download the offline driver .zip files and save to the shared location and provide the full path of the shared location. OMIVV automatically creates the catalog inside the OMIVV appliance. VIB driver bundles are available at https://my.vmware.com/web/vmware/downloads.

  5. Click Next.

    The Summary page is displayed that provides the information about the repository profile.

  6. Click Finish.

    After creating the catalog, the catalog download and parsing will start and status will be displayed on the home page of the repository profile.

    Successfully parsed repository profiles are available during the cluster profile creation, and during the vSAN firmware update.