Dependency checking

Dependency checking is an integral function of creating a supported configuration before HP SUM deployment. During this process, HP SUM ensures that the requirements for a component or target update are met. These include system requirements (for example, libraries and services) for the component, target, or associated devices of the target have compatible software and firmware revisions. This process is initiated automatically and silently after the HP SUM discovery process and it involves:

  1. Checking the dependencies of component /target/ or devices associated with targets. Examples of dependency checking include:

    • Health component requirement for installation of the SNMP Agents

    • Required operating system libraries

    • Compatibility of OA, VC, and iLO firmware versions

  2. Indicating if there is a dependency failure. Failures are displayed in the HP SUM GUI, and also saved in a log file.

To resolve any dependencies that were indicated during this process, review the logs and correct the failures. After resolving the dependencies, restart the HP SUM application.

[Note]

NOTE: For Superdome 2 servers that do not support online firmware updates, power down all Superdome 2 partitions in the complex. If you do not power down all the partitions, a Failed Dependencies error appears. On the Select Devices screen, click Ignore Warnings, and HP SUM powers down the partitions for you after you begin the installation process.