This alarm becomes active when a process is sustaining a high CPU load.
When this alarm is active, you may need to:
This alarm becomes active when the length of the processor thread queue reaches a threshold for sustained activity.
A long sustained queue length indicates a processor bottleneck - leading to overall system degradation.
To rectify this, you should look at:
This alarm is activated when the proportion of file read requests that can be sourced from memory cache rather than disk drops below a threshold.
When this alarm is current you should:
Look at the NBT page of the Network drilldown.
If there is a large number of read requests coming from the network clients, the cache can be inundated and temporarily of little use.
This alarm is activated when the system up time exceeds the value specified in the related threshold.