HP

Partition Manager Help

English
  Actions  |  Analyze Complex Health   

Analyze Complex Health

»Table of Contents
»Index
»Assistance
»Overview
»Features & Capabilities
»About Partitioning
»Starting & Stopping
»Complex Scope
»Partition Scope
»Cell Scope
»I/O Chassis Scope
»Actions
»Set Complex Name
Analyze Complex Health
»Clear All LEDs
»Show Complex Details
»Create nPartition
»Assign Cell(s)
»Delete nPartition
»Modify nPartition
»Unassign Cell(s)
»Power On/Off Cell
»Turn On/Off Cell LED
»Power On/Off Chassis
»Turn On/Off Chassis LED
»I/O Slot Actions
»Show Log File
»Status Indicators
»Messages
»Release Notes
»About Partition Manager
»Glossary
»Using Help
» Status Table
» Checks Performed

Use this action to check the complex for potential problems that can affect its operation and performance. To perform this action, select ComplexAnalyze Complex Health from the actions menu. This action is also performed automatically immediately after login to Partition Manager.

Click the [OK] button to dismiss this screen and return to the previous view. If no previous view was selected, the complex scope hardware view will be displayed.

Status Table

At the top of the page is a table showing the status of each category of checks performed on the complex.

Table 1 Fields of the Status Table

Status

An icon represents the result of the checks in each category. If a category contains several individual checks, the result icon indicates the most serious case among all the results in this category. The Legend to the right of the status table explains the meaning of each icon (Table 2).

Check

The categories of checks performed. Each category may consist of several individual checks. Refer to the Checks Performed section below for details about each category.

Notes

This column contains the numbers of any notes that apply to each category of checks. These numbers refer to the Notes section at the bottom of the page, where detailed information about the problems found are presented.

If no problems are found, the Notes section at the bottom of the page does not appear.

 

Table 2 Legend

Check Found No Problems. 

[active/ok status icon]

Check Found Possible Problems.  Partition Manager does not have enough information to determine if the detected condition is a minor problem or a valid configuration. For example, Partition Manager may not be able to determine if the operating system on an nPartition supports the specified memory configuration. Examine the detected condition to determine if it represents an actual problem.

[unknown status icon]

Check Found Minor Problems.  Minor problems might be detected in valid configurations, or might indicate an error condition that can degrade performance of the system. For example, processors may be deconfigured by the iCAP feature, or might be deconfigured due to a hardware error.

[minor problem status icon]

Check Found Serious Problems.  Serious problems should be resolved immediately, in order to avoid data loss or damage to system components.

[failed status icon]

 

Checks Performed

The following categories of checks are performed by this action. Note that the same problem may cause more than one check to fail. For example, a power or cooling domain with multiple faulty units may also be in an N- redundancy state (see high availability). Both problems will be reported.

Check data completeness

Serious Problems Detected:  Any cells, I/O chassis, or nPartitions with an error status or a lock contention problem.

Read and write locks are used to synchronize access to complex and nPartition information. Usually, lock contention is a transient condition that is automatically resolved. When a lock is held for an abnormally long time (for example, when the process that holds the lock terminates abnormally), you can forcibly release it. Stale locks are automatically broken after they have been held for 25 minutes. Refer to the Lock Contention message for more information.

An error status indicates that cell, I/O chassis, or nPartition data cannot be obtained by Partition Manager for a reason other than lock contention. This might be the result of intermittent or faulty communication with the service processor, a system call failure, a service processor failure, or a hardware component failure.

If only one (or a small number) of the components is in an error state, then it probably indicates a problem with individual components. If there are several or many components showing an error status, then it is more likely to be a communication or service processor failure.

Check component status

Minor Problems Detected:  Any cells with deconfigured processors or DIMMs; any inactive or active cells connected to an I/O chassis with an uninitialized system bus adapter; any power or cooling domains with failed power supplies, fans, or blowers.

Check cabinet cabling

Minor Problems Detected:  Symptoms of a cabinet not cabled correctly to the service processor, specifically: any I/O chassis that appears to be in a cabinet that does not appear to be in the complex.

Check for adequate power and cooling

Serious Problems Detected:  Any power or cooling domain in an N- redundancy state (see high availability).

Check cell compatibility

Serious Problems Detected:  Incompatible cells that should not be installed in the same complex. The groups of cells that are mutually compatible with one another will be listed in the Notes section. Only one of these groups should remain in the complex; all of the other cells should be removed.

Minor Problems Detected:  Incompatible cells that should not be assigned to the same nPartition. The groups of cells that are mutually compatible with one another in the same nPartition will be listed in the Notes section. Do not assign cells from different groups to the same nPartition.

Check memory configuration

The following checks only consider the memory on cells that are configured to boot with the nPartition (the “Use On Next Boot” flag is set to “Yes”).

Serious Problems Detected:  Any PA-RISC nPartition in which the requested interleaved memory is insufficient to enable HP-UX to boot. For detailed information about this constraint, refer to this message explanation.

Possible Problems Detected:  Any cell with cell local memory (CLM) configured, when the operating system on the cell's nPartition does not support CLM (or Partition Manager cannot determine if CLM is supported). Cell local memory is only supported on nPartitions running HP-UX 11i v2 (B.11.23), SuSE Linux Enterprise Server 9, or Microsoft® Windows®.

Minor Problems Detected:  Any nPartition with no operational memory; any nPartition where the amount of interleaved memory requested is less than the system-imposed minimum; any nPartition where the total amount of memory is not known; any PA-RISC nPartition where Partition Manager cannot determine if there is sufficient interleaved memory to boot HP-UX.

The Complex Profile defines a minimum amount of interleaved memory that must be provided in each nPartition (0.5 GB). When the nPartition is booted, system firmware will enforce this minimum by adjusting the memory configuration if necessary.

The total amount of memory in an nPartition may not be known if the nPartition contains cells with error status, or if Complex Profile locks prevent Partition Manager from retrieving information about cells in the nPartition.

Check boot configuration

Minor Problems Detected:  Any nPartition containing empty cell slots with the “Use On Next Boot” flag set to true; any active nPartition containing inactive cells with the “Use On Next Boot” flag set to true.

Both of these conditions can cause excessively long boot times as the system firmware waits for a cell to rendezvous in the boot sequence. In the latter case, this is an issue only if the cell was assigned to the nPartition and set to boot before the last boot. In that case, the cell must not have completed its boot, and may be faulty. If the cell was added to the nPartition after the nPartition booted, then no further action needs to be taken.