Diagnostic tests

This section describes:

• The Core Health Check Monitor that checks the health of individual SA components. See Core Health Check Monitor (HCM).
• The System Diagnosis tool that checks the overall health of the SA core. See Running a system diagnosis.

You can use these tools to diagnose the following types of problems you may encounter while maintaining SA:

• Operational problems: processes failing or becoming unresponsive (for example, the Data Access Engine, Command Engine, or Software Repository)
• SA Core Component Failure: which causes other components to fail.

  The following examples describe the effects of some core component failures:

  • If the Data Access Engine fails, the SA Client, the Command Engine, and the Software Repository components will fail.
  • If the Software Repository fails to contact the Data Access Engine, downloads from the Software Repository are impossible.
  • If the Model Repository fails, the Data Access Engine fails.
  • if the Software Repository has neither a functioning DNS, nor a properly-configured
    /etc/hosts file, it fails to contact the Data Access Engine.
  • If unreachable servers exist in the managed environment, communication is disrupted.

System diagnosis can only be run on one facility at a time.