HP 9000 rp5405 Servers - Manual (Page 292)

• If no instance of Critical exists, but one or more instances of Warning exist, the upper level is
labeled Warning
• If no instance of Critical or Warning exists, the upper level is labeled Normal
This ensures that the current status of each level reflects that of the one below. In the example below,
the top (application) level is tagged with an aggregate status of Critical.
Figure 11 Agreggation example (Exchange 2003/2007)
Related topics
• Checking the status of application replicas , page 421
• About data protection status , page 290
• Data protection status example , page 291
Excluding objects from data protection status monitoring
During a maintenance operation, the protection status for a specific object could be intentionally set
to Critical. In this case, aggregating the status would disturb status monitoring. To avoid this situation,
administrators can exclude objects from monitoring by excluding the individual information sources.
Like the aggregation of status, exclusion works from the bottom up: the status of an object is displayed
as Excluded if all its sub-objects are excluded from monitoring.
To exclude an object from monitoring:
1. From the Explorer menu, select Resources, and then Applications.
The Applications subwindow appears.
2. Click on the link for the server.
The server subwindow appears.
System monitoring 292