SUM Baseline Library screen

The Baseline Library screen displays the baselines and additional packages you will use to update your nodes. Baselines include an SPP, or custom baseline that includes updates that you select from other baselines or additional packages. Additional packages are directories that hold updates that are not included in a named update package, for example a Hot Fix. SUM saves baseline information between sessions.

SUM displays each added baseline in the left pane. Select a baseline, and SUM displays the following information for each baseline and additional package.

• Languages

• Operating systems

• Enhancements

• Components—SUM includes a search box for finding updates that meet the search parameters. You can search on file name, description, and update type. Double-click an update to view its details.

• Component errors—Components that are specified in the baseline but are missing, and components that are present but fail signature validation.

  The Baseline inventory checks for the component signature and if the signature is invalid or not signed, the component is marked as an invalid component and an error message is displayed.

  The following table displays the signature error messages and compsig file error messages for various components.

  Component type	Signature error messages	Compsig file error messages
  Gen10 Windows exe	Component not signed Component signature invalid	Component signature file missing. [Warning]
  Gen10 RPMs	Component not signed Component signature invalid	Component signature file missing. [Warning]
  Gen10 VMware component		Component signature file missing. [Error] Failed to verify component signature file.
  Gen9 and below Windows exe	Component not signed Component signature invalid
  Gen9 and below RPMs	Component not signed Component signature invalid
  Gen9 and below VMware components		Component signature file missing. [Error] Failed to verify component signature file.

• Component Warnings—Components that are present but are missing optional signature files used with iLO Repository.

• Component configuration—Some components support optional configuration parameters that can be set before deployment.