Skip Headers
Oracle® Enterprise Manager Framework, Host, and Services Metric Reference Manual
12c Release 1 (12.1.0.2.0)

Part Number E25162-03
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

2 Host

The host metrics provide description, collection statistics, data source, multiple thresholds (where applicable), and user action information for each metric.

Aggregate Resource Usage Statistics (By Project)

This metric provides data on aggregate resource usage on a per project basis. This metric is available only on Solaris version 9 and later.

Cumulative CPU Wait Time (Seconds)

Cumulative number of seconds that this process has spent Waiting for CPU over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Data Page Fault Sleep Time (Seconds)

Cumulative number of seconds that this process has spent sleeping in Data Page Faults over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Major Page Faults

The cumulative number of Major Page Faults engendered by the process over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Minor Page Faults

The cumulative number of Minor Page Faults engendered by the process over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Number Character IO (bytes) Read and Written

The cumulative number of character I/O bytes Read and Written by the process over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Number Of Blocks Read

The cumulative number of blocks Read by the process over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Number Of Blocks Written

The cumulative number of blocks Written by the process over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Number of Involuntary Context Switches

The cumulative number of Involuntary Context Switches made by the process over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Number Of Messages Received

The cumulative number of Messages Received by the process over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Number Of Messages Sent

The cumulative number of Messages Sent by the process over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Number of Signals Received

The cumulative number of Signals taken by the process over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Number of System Calls Made

The cumulative number of system calls made by the process over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Number of Voluntary Context Switches

The cumulative number of Voluntary Context Switches made by the process over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Project Lock-Wait Sleep Time (Seconds)

The cumulative number of seconds that this process has spent sleeping on User Lock Waits over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Project Other Sleep Time (Seconds)

The cumulative number of seconds that this process has spent sleeping in all other ways over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Stop Time (Seconds)

The cumulative number of seconds that this process has spent Stopped over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Swap Operations

The cumulative number of swap operations engendered by the process over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative System Mode Time (seconds)

The cumulative number of seconds that this process has spent in System mode over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative System Page Fault Sleep Time (Seconds)

The cumulative number of seconds that this process has spent sleeping in System Page Faults over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative System Trap Time (seconds)

The cumulative number of seconds that this process has spent in System Traps over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Text Page Fault Sleep Time (Seconds)

The cumulative number of seconds that this process has spent sleeping in Text Page Faults over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative User Mode Time (seconds)

The cumulative number of seconds that this process has spent in User mode over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Number of Processes Owned by Project

The number of processes owned by the project measured in the aggregate. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Project CPU Time (%)

The percent CPU time used by the process. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Project Process Memory Size (%)

The ratio of the process resident set size to physical memory. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Project's Total Process Heap Size (KiloBytes)

The total number of KiloBytes of memory consumed by the process heap at the time that it is sampled. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Project's Total Process Resident Set Size (KiloBytes)

The resident set size of the process in kilobytes. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Project's Total Process Virtual Memory Size (KiloBytes)

The size of the process virtual address space in kilobytes. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Total Number of Threads in Project's Processes

The number of threads active in the current Process. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Aggregate Resource Usage Statistics (By User)

This metric provides data on aggregate resource usage on a per user basis.

This metric is available only on Solaris version 9 and later.

Cumulative CPU Wait Time (Seconds)

The cumulative number of seconds that this process has spent Waiting for CPU over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Data Page Fault Sleep Time (Seconds)

The cumulative number of seconds that this process has spent sleeping in Data Page Faults over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Major Page Faults

The cumulative number of Major Page Faults engendered by the process over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Minor Page Faults

The cumulative number of Minor Page Faults engendered by the process over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Number Character IO (bytes) Read and Written

The cumulative number of character I/O bytes Read and Written by the process over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Number Of Blocks Read

The cumulative number of blocks Read by the process over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Number Of Blocks Written

The cumulative number of blocks Written by the process over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Number of Involuntary Context Switches

The cumulative number of Involuntary Context Switches made by the process over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Number Of Messages Received

The cumulative number of Messages Received by the process over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Number Of Messages Sent

The cumulative number of Messages Sent by the process over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Number of Signals Received

The cumulative number of Signals taken by the process over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Number of System Calls Made

The cumulative number of system calls made by the process over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Number of Voluntary Context Switches

The cumulative number of Voluntary Context Switches made by the process over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Stop Time (Seconds)

The cumulative number of seconds that this process has spent Stopped over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative System Mode Time (seconds)

The cumulative number of seconds that this process has spent in System mode over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative System Page Fault Sleep Time (Seconds)

The cumulative number of seconds that this process has spent sleeping in System Page Faults over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative System Trap Time (seconds)

The cumulative number of seconds that this process has spent in System Traps over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Swap Operations

The cumulative number of Swap Operations engendered by the process over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Text Page Fault Sleep Time (Seconds)

The cumulative number of seconds that this process has spent sleeping in Text Page Faults over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative User Lock-Wait Sleep Time (Seconds)

The cumulative number of seconds that this process has spent sleeping on User Lock Waits over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative User Mode Time (seconds)

The cumulative number of seconds that this process has spent in User mode over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative User Other Sleep Time (Seconds)

The cumulative number of seconds that this process has spent sleeping in all other ways over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Number of Processes Owned by User

The number of processes owned by the user measured in the aggregate. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Total Number of Threads in User's Processes

The number of threads active in the current Process. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

User CPU Time (%)

The percent CPU time used by the process. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

User Process Memory Size (%)

The ratio of the process resident set size to physical memory. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

User's Total Process Heap Size (KiloBytes)

The total number of kilobytes of memory consumed by the process heap at the time that it is sampled. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

User's Total Process Resident Set Size (KiloBytes)

The resident set size of the process in kilobytes. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

User's Total Process Virtual Memory Size (KiloBytes)

The size of the process virtual address space in kilobytes. This metric is available only on Solaris version 9 and later.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Buffer Activity

The Buffer Activity metric provides information about OS memory buffer usage. This metric reports buffer activity for transfers, accesses, and cache (kernel block buffer cache) hit ratios per second.

Buffer Cache Read Hit Ratio (%)

Represents the number of reads from block devices to buffer cache as a percentage of all buffer read

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-1 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

6

Buffer Cache Read Hit Ratio %value%%% , has crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.


Data Source

The data sources for this metric include the following:

Host Data Source
Solaris sar command
HP sar command
Linux not available
HP Tru64 table() system call
IBM AIX sar command
Windows not available

User Action

Specific to your site.

Buffer Cache Reads (per second)

Represents the number of reads performed on the buffer cache per second.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Minutes

Data Source

The data sources for this metric include the following:

Host Data Source
Solaris sar command
HP sar command
Linux not available
HP Tru64 not available
IBM AIX sar command
Windows not available

User Action

Specific to your site.

Buffer Cache Write Hit Ratio (%)

Represents the number of writes from block devices to buffer cache as a percentage of all buffer writes.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-2 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

6

Buffer Cache Read Hit Ratio %value%%% , has crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.


Data Source

The data sources for this metric include the following:

Host Data Source
Solaris sar command
HP sar command
Linux not available
HP Tru64 table() system call
IBM AIX sar command
Windows not available

User Action

Specific to your site.

Buffer Cache Writes (per second)

Represents the number of writes performed on the buffer cache per second.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Minutes

Data Source

The data sources for this metric include the following:

Host Data Source
Solaris sar command
HP sar command
Linux not available
HP Tru64 not available
IBM AIX sar command
Windows not available

User Action

Specific to your site.

Physical I/O Reads (per second)

Represents the number of reads per second from character devices using physical I/O mechanisms.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Minutes

Data Source

The data sources for this metric include the following:

Host Data Source
Solaris sar command
HP sar command
Linux not available
HP Tru64 table() system call
IBM AIX sar command
Windows not available

User Action

An unusually high value may indicate an abnormal situation, so it is important to set thresholds based on the average value observed over a period of time. An abnormally high value may cause performance issues. The user action varies from case to case, observe the running processes to track down any errant process. Placing highly active directories on different disks may help.

Physical I/O Writes (per second)

Represents the number of writes per second from character devices using physical I/O mechanisms.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Minutes

Data Source

The data sources for this metric include the following:

Host Data Source
Solaris sar command
HP sar command
Linux not available
HP Tru64 table() system call
IBM AIX sar command
Windows not available

User Action

An unusually high value may indicate an abnormal situation, so it is important to set thresholds based on the average value observed over a period of time. An abnormally high value may cause performance issues. The user action varies from case to case, observe the running processes to track down any errant process. Placing highly active directories on different disks may help.

Physical Reads (per second)

Represents the number of physical reads per second from block devices to the system buffer cache.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Minutes

Data Source

The data sources for this metric include the following:

Host Data Source
Solaris sar command
HP sar command
Linux not available
HP Tru64 table() system call
IBM AIX sar command
Windows not available

User Action

An unusually high value may indicate an abnormal situation, so it is important to set thresholds based on the average value observed over a period of time. An abnormally high value may cause performance issues. The user action varies from case to case, observe the running processes to track down any errant process. Placing highly active directories on different disks may help.

Physical Writes (per second)

Represents the number of physical writes per second from block devices to the system buffer cache.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Minutes

Data Source

The data sources for this metric include the following:

Host Data Source
Solaris sar command
HP sar command
Linux not available
HP Tru64 table() system call
IBM AIX sar command
Windows not available

User Action

An unusually high value may indicate an abnormal situation, so it is important to set thresholds based on the average value observed over a period of time. An abnormally high value may cause performance issues. The user action varies from case to case, observe the running processes to track down any errant process. Placing highly active directories on different disks may help.

CPU Usage

The CPU Usage metric provides information about the percentage of time the CPU was in various states, for example, idle state and wait state. The metric also provides information about the percentage of CPU time spent in user and system mode. All data is per-CPU in a multi-CPU system.

On HP Tru64, this information is available as the cumulative total for all the CPUs and not for each CPU which is monitored in the Load metric. Hence, this metric is not available on HP Tru64.

CPU Idle Time (%)

Represents the percentage of time that the CPU was idle and the system did not have an outstanding disk I/O request. This metric checks the percentage of processor time in idle mode for the CPU(s) specified by the Host CPU parameter, such as cpu_stat0, CPU0, or * (for all CPUs on the system).

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The data sources for this metric include the following:

Host Data Source
Solaris kernel statistics (class cpu_stat)
HP pstat_getprocessor() system call
Linux /proc/stat
HP Tru64 not available
IBM AIX oracle_kstat() system call
Windows performance data counters

User Action

An abnormally high value (determined on the basis of historical data) indicates an underutilized cpu. The user action varies from case to case.

CPU Interrupt Time (%)

Represents the percentage of time that the CPU receives and services hardware interruptions during representative intervals. This metric checks the percentage of processor time in interrupt mode for the CPU(s) specified by the Host CPU parameter, such as cpu_stat0, CPU0, or * (for all CPUs on the system).

This metric is available only on Windows.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "CPU Number" object.

If warning or critical threshold values are currently set for any "CPU Number" object, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each "CPU Number" object, use the Edit Thresholds page. See the Editing Thresholds topic in the Enterprise Manager online help for information on accessing the Edit Thresholds page.

Data Source

The data sources for this metric are Performance Data counters.

User Action

This indicates the amount of time spent by the processor in handling interrupts. If an unusually high value is observed, there is a possibility of some hardware

CPU System Time (%)

Represents the percentage of time that the CPU is running in system mode (kernel). This metric checks the percentage of processor time in system mode for the CPU(s) specified by the Host CPU parameter, such as cpu_stat0, CPU0, or * (for all CPUs on the system).

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The data sources for this metric include the following:

Host Data Source
Solaris kernel statistics (class cpu_stat)
HP pstat_getprocessor() system call
Linux /proc/stat
HP Tru64 not available
IBM AIX oracle_kstat() system call
Windows performance data counters

User Action

An abnormally high value (determined on the basis of historical data) indicates that the machine is doing a lot of work at the system (kernel) level. The user action varies from case to case.

CPU User Time (%)

Represents the portion of processor time running in user mode. This metric checks the percentage of processor time in user mode for the CPU(s) specified by the Host CPU parameter, such as cpu_stat0, CPU0, or * (for all CPUs on the system).

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The data sources for this metric include the following:

Host Data Source
Solaris kernel statistics (class cpu_stat)
HP pstat_getprocessor() system call
Linux /proc/stat
HP Tru64 not available
IBM AIX oracle_kstat() system call
Windows performance data counters

User Action

An abnormally high value (determined on the basis of historical data) indicates the cpu is doing a lot of work at the user (application) level. An examination of the top processes on the system may help identify problematic processes.

CPU Utilization (%) of a CPU

This figure represents the percentage utilization of a CPU

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The data sources for this metric include the following:

Host Data Source
Solaris kernel statistics (class cpu_stat)
HP pstat_getprocessor() system call
Linux /proc/stat
HP Tru64 not available
IBM AIX oracle_kstat() system call
Windows performance data counters

User Action

An abnormally high value (determined on the basis of historical data) indicates that the system is under heavy load. If the value is consistently high, consider reducing the load on the system.

CPU Wait Time (%)

Represents the percentage of time that the CPU was idle during which the system had an outstanding disk I/O request. This metric checks the percentage of processor time in wait mode for the CPU(s) specified by the Host CPU parameter, such as cpu_stat0, CPU0, or * (for all CPUs on the system).

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The data sources for this metric include the following:

Host Data Source
Solaris not available
HP pstat_getprocessor() system call
Linux not available
HP Tru64 not available
IBM AIX oracle_kstat() system call
Windows performance data counters

User Action

A high value indicates that the cpu spends a lot of time waiting for disk i/o to complete. Examine the disk errors and disk activity metrics to see if there are any problems with disk performance. Consider keeping heavily accessed directories on separate disks.

CPUs Details

The metric provides information on the processors of the host.

ECACHE in MB

This is the size of the Cache memory measured in MB.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

/proc/cpuinfo

User Action

None.

Frequency in MHZ

This is the clock frequency of the processor.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

/proc/cpuinfo

User Action

None.

Is HyperThread Enabled

This tells whether hyper threading is enabled for this processor or not.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

/proc/cpuinfo

User Action

None.

Implementation

Implementation type of processor.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

/proc/cpuinfo

User Action

None.

Number of CPUs

This is the count the number rows having the same information in other columns like vendor_name or num_cores. This is added to make at least one key in table.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

/proc/cpuinfo

User Action

None.

MASK

This is Die used to manufacture the CPU. Solaris prtdiag has CPU mask field. This column stores that information.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

/proc/cpuinfo

User Action

None.

Number of Cores per Physical CPU

This represents number of cores per physical CPU. For example. for dual core processors this count will be two and for quad core processor this count will be four.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

/proc/cpuinfo

User Action

None.

Revision

This is the revision.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

/proc/cpuinfo

User Action

None.

Number Of Threads Per Physical CPU

This effectively represents the number of logical processor per physical processors. For example, for one dual core processor with hyper thread enabled, this value will be four.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

/proc/cpuinfo

User Action

None.

Vendor Name

This is vendor who has manufactured the processors. For example Intel and AMD.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

/proc/cpuinfo

User Action

None.

Disk Activity

The Disk Activity metric monitors the hard disk activity on the target being monitored. For each device on the system, this metric provides information about access to the device. This information includes: device name, disk utilization, write statistics, and read statistics for the device.

Average Disk I/O Service Time (ms)

Represents the sum of average wait time and average run time.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-3 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 15 Minutes

After Every Sample

>

Not Defined

Not Defined

6

Average service time for disk %keyvalue% is %value% ms, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.


Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "Disk Device" object.

If warning or critical threshold values are currently set for any "Disk Device" object, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each "Disk Device" object, use the Edit Thresholds page.

Data Source

The data sources for this metric include the following:

Host Data Source
Solaris kernel statistics (class kstat_io)
HP pstat_getdisk system call
Linux iostat command
HP Tru64 table() system call
IBM AIX oracle_kstat() system call
Windows performance data counters

User Action

This number should be low. A high number can indicate a disk that is slow due to excessive load or hardware issues. See also the CPU in IO-Wait (%) metric.

Average Disk I/O Wait Time (ms)

Represents the average time spent by the command waiting on the queue for getting executed.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "Disk Device" object.

If warning or critical threshold values are currently set for any "Disk Device" object, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each "Disk Device" object, use the Edit Thresholds page.

Data Source

The data sources for this metric include the following:

Host Data Source
Solaris kernel statistics (class kstat_io)
HP pstat_getdisk system call
Linux not available
HP Tru64 table() system call
IBM AIX oracle_kstat() system call
Windows performance data counters

User Action

A high figure indicates a slow disk. Use the OS iostat -xn command to check wait time and service time for local disks and NFS mounted file systems. See also the CPU in IO-Wait (%) metric.

Average Outstanding Disk I/O Requests

Represents the average number of commands waiting for service (queue length).

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The data sources for this metric include the following:

Host Data Source
Solaris kernel statistics (class kstat_io)
HP pstat_getdisk system call
Linux not available
HP Tru64 table() system call
IBM AIX oracle_kstat() system call
Windows performance data counters

User Action

Specific to your site.

Average Run Time (ms)

Represents the average time spent by the command on the active queue waiting for its execution to be completed.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The data sources for this metric include the following:

Host Data Source
Solaris kernel statistics (class kstat_io)
HP pstat_getdisk system call
Linux not available
HP Tru64 table() system call
IBM AIX oracle_kstat() system call
Windows performance data counters

User Action

Specific to your site.

Bulk I/O Ticks

Represents the time spent in Input/Output operations (ms).

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

Linux: /proc/diskstats or /proc/partitions

User Action

Specific to your site.

Difference in Number of Reads

Represents the number of disk reads from the last collection.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

Linux: /proc/diskstats or /proc/partitions

User Action

Specific to your site.

Difference in Number of Writes

Represents the number of disk reads from the last collection.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

Linux: /proc/diskstats or /proc/partitions

User Action

Specific to your site.

Disk Block Writes (per second)

Represents the number of blocks (512 bytes) written per second.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The data sources for this metric include the following:

Host Data Source
Solaris kernel statistics (class kstat_io)
HP not available
Linux iostat command
HP Tru64 table() system call
IBM AIX oracle_kstat() system call
Windows performance data counters

User Action

Specific to your site.

Disk Block Reads (per second)

Represents the number of blocks (512 bytes) read per second.

Note: On HPUNIX, this metric is named Disk Blocks Transferred (per second).

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The data sources for this metric include the following:

Host Data Source
Solaris kernel statistics (class kstat_io)
HP pstat_getdisk system call
Linux iostat command
HP Tru64 table() system call
IBM AIX oracle_kstat() system call
Windows performance data counters

User Action

Specific to your site.

Disk Device Busy (%)

This metric represents disk device busy percentage.

Note: On HPUNIX, this metric is named Device Busy (%).

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-4 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 15 Minutes

After Every Sample

>

80

95

6

Disk Device %keyValue% is %value%%% busy.


Data Source

The data sources for this metric include the following:

Host Data Source
Solaris kernel statistics (class kstat_io)
HP pstat_getdisk system call
Linux iostat command
HP Tru64 table() system call
IBM AIX oracle_kstat() system call
Windows performance data counters

User Action

Specific to your site.

Disk Reads (per second)

Represents the disk reads per second for the specified disk device.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The data sources for this metric include the following:

Host Data Source
Solaris kernel statistics (class kstat_io)
HP not available
Linux iostat command
HP Tru64 table() system call
IBM AIX oracle_kstat() system call
Windows performance data counters

User Action

Specific to your site.

Disk Writes (per second)

Represents the disk writes per second for the specified disk device.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The data sources for this metric include the following:

Host Data Source
Solaris kernel statistics (class kstat_io)
HP not available
Linux iostat command
HP Tru64 table() system call
IBM AIX oracle_kstat() system call
Windows performance data counters

User Action

Specific to your site.

Disk Device Errors

The Disk Device Errors metric provides the number of errors on the disk device.

These metrics are available only on Solaris.

Hard Errors

Represents the error count of hard errors encountered while accessing the disk. Hard errors are considered serious and may be traced to misconfigured or bad disk devices.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 72 Hours

Data Source

The data sources for this metric include the following:

Host Data Source
Solaris iostat -e command
HP not available
Linux not available
HP Tru64 not available
IBM AIX not available
Windows not available

User Action

Specific to your site.

Soft Errors

Represents the error count of soft errors encountered while accessing the disk. Soft errors are synonymous to warnings.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 72 Hours

Data Source

The data sources for this metric include the following:

Host Data Source
Solaris iostat -e command
HP not available
Linux not available
HP Tru64 not available
IBM AIX not available
Windows not available

User Action

Specific to your site.

Total

Represents the sum of all errors on the particular device

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 72 Hours

Data Source

The data sources for this metric include the following:

Host Data Source
Solaris iostat -e command
HP not available
Linux not available
HP Tru64 not available
IBM AIX not available
Windows not available

User Action

Specific to your site.

Transport Errors

Represents the error count of network errors encountered. This generally indicates a problem with the network layer

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 72 Hours

Data Source

The data sources for this metric include the following:

Host Data Source
Solaris iostat -e command
HP not available
Linux not available
HP Tru64 not available
IBM AIX not available
Windows not available

User Action

Specific to your site.

Fans

The Fans metric monitors the status of various fans present in the system.

This metric is available only on Dell Poweredge Linux Systems.

Fan Status

Represents the status of the fan.

This metric is available only on Dell Poweredge Linux Systems.

The following table lists the possible values for this metric and their meaning.

Metric Value Meaning (per SNMP MIB)
1 Other (not one of the following)
2 Unknown
3 Normal
4 Warning
5 Critical
6 Non-Recoverable

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-5 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 15 Minutes

Not Uploaded

>=

4

5

1

Status of Fan at device %FanIndex% in chassis %ChassisIndex% is %value%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.


Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Chassis Index" and "Fan Index" objects.

If warning or critical threshold values are currently set for any unique combination of "Chassis Index" and "Fan Index" objects, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each unique combination of "Chassis Index" and "Fan Index" objects, use the Edit Thresholds page.

Data Source

SNMP MIB object: coolingDeviceStatus (1.3.6.1.4.1.674.10892.1.700.12.1.5)

User Action

None.

Location

Provides a description of the location of the fan. Example values are "CPU Fan", "PCI Fan", and "Memory Fan".

This metric is available only on Dell Poweredge Linux Systems.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

SNMP MIB object: coolingDeviceLocationName (1.3.6.1.4.1.674.10892.1.700.12.1.8)

User Action

None.

File Access System Calls

The File Access System Calls metric provides information about the usage of file access system calls.

This metric is available on Solaris, HP, and IBM AIX.

Blocks Read by Directory Search Routine (per second)

Represents the number of file system blocks read per second performing direct lookup.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Seconds

Data Source

The data sources for this metric include the following:

Host Data Source
Solaris sar command
HP sar command
Linux not available
HP Tru64 not available
IBM AIX sar command
Windows not available

The OS sar command is used to sample cumulative activity counters maintained by the OS. The data is obtained by sampling system counters once in a five-second interval. The results are essentially the number of lookuppn() calls made over this five-second period divided by five.

User Action

None.

iget() Calls (per second)

Represents the number of system iget() calls made per second. iget is a file access system routine.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Seconds

Data Source

The data sources for this metric include the following:

Host Data Source
Solaris kernel memory structure (class cpu_vminfo
HP sar command
Linux not available
HP Tru64 not available
IBM AIX kernel memory structure (class cpu_vminfo
Windows not available

User Action

This data is obtained using the OS sar command, which is used to sample cumulative activity counters maintained by the OS. The data is obtained by sampling system counters once in a five-second interval. The results are essentially the number of iget() calls made over this five-second period divided by five.

lookuppn() Calls (per second)

Represents the number of file system lookuppn() (pathname translation) calls made per second.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Seconds

Data Source

The data sources for this metric include the following:

Host Data Source
Solaris sar command
HP sar command
Linux not available
HP Tru64 not available
IBM AIX sar command
Windows not available

The OS sar command is used to sample cumulative activity counters maintained by the OS. The data is obtained by sampling system counters once in a five-second interval. The results are essentially the number of lookuppn() calls made over this five-second period divided by five.

User Action

None.

File and Directory Monitoring

The File and Directory Monitoring metric monitors various attributes of specific files and directories. Setting of key value specific thresholds triggers the monitoring of files or directories referred to in the given key value. The operator must specify key value specific thresholds to monitor any file or directory.

File or Directory Attribute Not Found

Reports issues encountered in fetching the attributes of the file or directory. Errors encountered in monitoring the files and directories specified by the key value based thresholds are reported.

Note: This metric is not available on IBM AIX.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-6 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 15 Minutes

After Every Sample

!=

Not Defined

0

1

%file_attribute_not_found% .


Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "File or Directory Name" object.

If warning or critical threshold values are currently set for any "File or Directory Name" object, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each "File or Directory Name" object, use the Edit Thresholds page.

Data Source

The data sources for this metric include the following:

Host Data Source
Solaris perl stat command for files; df for directories that are file system mount points; du for directories that are not file system mount points
HP perl stat command for files; df for directories that are file system mount points; du for directories that are not file system mount points
Linux perl stat command for files; df for directories that are file system mount points; du for directories that are not file system mount points
HP Tru64 not available
IBM AIX not available
Windows not available

User Action

Looks for the attributes for file and directories like inode id, user id, and group id. If not found an alert is raised so that user can verify.

File or Directory Permissions

Fetches the octal value of file permissions on the different variations of UNIX operating systems including Linux. Setting a key value specific warning or critical threshold value against this metric would result in the monitoring of a critical file or directory. For example, to monitor the file permissions for file name /etc/passwd, you should set a threshold for /etc/passwd.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-7 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 15 Minutes

After Every Sample

!=

Not Defined

Not Defined

1

Current permissions for %file_name% are %file_permissions%, different from warning (%warning_threshold%) or critical (%critical_threshold%) threshold.


Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "File or Directory Name" object.

If warning or critical threshold values are currently set for any "File or Directory Name" object, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each "File or Directory Name" object, use the Edit Thresholds page.

Data Source

The data sources for this metric include the following:

Host Data Source
Solaris perl stat command for files; df for directories that are file system mount points; du for directories that are not file system mount points
HP perl stat command for files; df for directories that are file system mount points; du for directories that are not file system mount points
Linux perl stat command for files; df for directories that are file system mount points; du for directories that are not file system mount points
HP Tru64 not available
IBM AIX perl stat command for files; df for directories that are file system mount points; du for directories that are not file system mount points
Windows not available

User Action

An alert will be raised if the permissions for a file or directory have changed. User may want to verify the change.

File or Directory Size (MB)

Fetches the current size of the given file or directory in megabytes. Setting a key value specific warning or critical threshold value against this metric would result in monitoring of a critical file or directory. For example, to monitor the file permissions for directory /absolute_directory_path, you should set a threshold for /absolute_directory_path.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-8 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 15 Minutes

After Every Sample

>

Not Defined

Not Defined

1

Size of %file_name% is %file_size% MB, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.


Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "File or Directory Name" object.

If warning or critical threshold values are currently set for any "File or Directory Name" object, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each "File or Directory Name" object, use the Edit Thresholds page.

Data Source

The data sources for this metric include the following:

Host Data Source
Solaris perl stat command for files; df for directories that are file system mount points; du for directories that are not file system mount points
HP perl stat command for files; df for directories that are file system mount points; du for directories that are not file system mount points
Linux perl stat command for files; df for directories that are file system mount points; du for directories that are not file system mount points
HP Tru64 not available
IBM AIX perl stat command for files; df for directories that are file system mount points; du for directories that are not file system mount points
Windows not available

User Action

If a threshold is exceeded, you may need to take action to adjust the file size or the threshold level.

File or Directory Size Change Rate (KB/minute)

Provides the value for the rate at which the file�s size is changing. Setting a key value specific warning or critical threshold value against this metric would result in monitoring of the critical file or directory. For example, to monitor the file change rate for the file name /absolute_file_path, the operator should set a threshold for /absolute_file_path.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-9 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 15 Minutes

After Every Sample

>

Not Defined

Not Defined

1

%file_name% is growing at the rate of %file_sizechangerate% (KB/hour), crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.


Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "File or Directory Name" object.

If warning or critical threshold values are currently set for any "File or Directory Name" object, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each "File or Directory Name" object, use the Edit Thresholds page.

Data Source

The data sources for this metric include the following:

Host Data Source
Solaris perl stat command for files; df for directories that are file system mount points; du for directories that are not file system mount points
HP perl stat command for files; df for directories that are file system mount points; du for directories that are not file system mount points
Linux perl stat command for files; df for directories that are file system mount points; du for directories that are not file system mount points
HP Tru64 not available
IBM AIX perl stat command for files; df for directories that are file system mount points; du for directories that are not file system mount points
Windows not available

User Action

Rate of change of file/directory. An abnormally high value (determined on the basis of historical data) indicates sudden increase in size. Users may want to take some action based on alert.

Filesystems

The Filesystems metrics provide information about local file systems on the computer.

Filesystem

Represents the name of the disk device resource.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The data sources for this metric include the following:

Host Data Source
Solaris /etc/mnttab file entries
HP bdf command
Linux df command
HP Tru64 df command
IBM AIX /etc/mnttab file entries
Windows not available

User Action

None.

Filesystem Size (MB)

Represents the total space (in megabytes) allocated in the file system.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The data sources for this metric include the following:

Host Data Source
Solaris vminfo system
HP bdf command
Linux df command
HP Tru64 df command
IBM AIX stavfs() system call
Windows Windows API

User Action

None.

Filesystem Space Available (%)

Represents the percentage of free space available in the file system.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-10 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 15 Minutes

After Every 24 Samples

<

20

5

1

Filesystem %keyValue% has %value%%% available space, fallen below warning (%warning_threshold%) or critical (%critical_threshold%) threshold.


Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "Mount Point" object.

If warning or critical threshold values are currently set for any "Mount Point" object, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each "Mount Point" object, use the Edit Thresholds page.

Data Source

The data sources for this metric include the following:

Host Data Source
Solaris stavfs() system call
HP bdf command
Linux df command
HP Tru64 df command
IBM AIX stavfs() system call
Windows Windows API

User Action

Use the OS du -k command to check which directories are taking up the most space (du -k|sort -rn).

Filesystem Utilization (MB)

Represents the total space, expressed in megabytes, allocated in the file system.

This metric is available only on Windows.

Data Source

The data source for this metric is GetDiskFreeSpaceEx.

User Action

A high value indicates that the filesystem has very little free space remaining.User might want to manage the free space.

Kernel Memory

The Kernel Memory metric provides information on kernel memory allocation (KMA) activities.

This metric is available only on Solaris. The data source is the sar command. The data is obtained by sampling system counters once in a five-second interval.

Failed Requests for Large Kernel Memory

This metric represents the Number of requests for large memory that failed, that is, requests that were not satisfied.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Seconds

Data Source

The data sources for this metric include the following:

Host Data Source
Solaris sar command

The data is obtained by sampling system counters once in a five-second interval.

HP not available
Linux not available
HP Tru64 not available
IBM AIX not available
Windows not available

User Action

None.

Failed Requests for Oversize Kernel Memory

This metric represents the number of oversized requests made that could not be satisfied. Oversized memory requests are allocated dynamically so there is no pool for such requests.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Seconds

Data Source

The data sources for this metric include the following:

Host Data Source
Solaris sar command

The data is obtained by sampling system counters once in a five-second interval.

HP not available
Linux not available
HP Tru64 not available
IBM AIX not available
Windows not available

User Action

None.

Failed Requests for Small Kernel Memory

This metric represents the number of requests for small memory that failed, that is, requests that were not satisfied.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Seconds

Data Source

The data sources for this metric include the following:

Host Data Source
Solaris sar command

The data is obtained by sampling system counters once in a five-second interval.

HP not available
Linux not available
HP Tru64 not available
IBM AIX not available
Windows not available

User Action

None.

KMA Available for Large Memory Requests (Bytes)

This metric represents the amount of memory, in bytes, the kernel memory allocation (KMA) has for the large pool; the pool used for allocating and reserving large memory requests.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Seconds

Data Source

The data sources for this metric include the following:

Host Data Source
Solaris sar command

The data is obtained by sampling system counters once in a five-second interval.

HP not available
Linux not available
HP Tru64 not available
IBM AIX not available
Windows not available

User Action

None.

KMA for Oversize Memory Requests (Bytes)

This metric represents the amount of memory allocated for oversized memory requests.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Seconds

Data Source

The data sources for this metric include the following:

Host Data Source
Solaris sar command

The data is obtained by sampling system counters once in a five-second interval.

HP not available
Linux not available
HP Tru64 not available
IBM AIX not available
Windows not available

User Action

None.

KMA for Small Memory Requests

This metric represents the amount of memory, in bytes, the Kernel Memory Allocation has for the small pool; the pool used for allocating and reserving small memory requests.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Seconds

Data Source

The data sources for this metric include the following:

Host Data Source
Solaris sar command

The data is obtained by sampling system counters once in a five-second interval.

HP not available
Linux not available
HP Tru64 not available
IBM AIX not available
Windows not available

User Action

None.

Memory Allocated for Large Memory Requests (Bytes)

This metric represents the amount of memory, in bytes, the kernel allocated to satisfy large memory requests.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Seconds

Data Source

The data sources for this metric include the following:

Host Data Source
Solaris sar command

The data is obtained by sampling system counters once in a five-second interval.

HP not available
Linux not available
HP Tru64 not available
IBM AIX not available
Windows not available

User Action

None.

Memory Allocated for Small Memory Requests (Bytes)

This metric represents the amount of memory, in bytes, the kernel allocated to satisfy small memory requests.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Seconds

Data Source

The data sources for this metric include the following:

Host Data Source
Solaris sar command

The data is obtained by sampling system counters once in a five-second interval.

HP not available
Linux not available
HP Tru64 not available
IBM AIX not available
Windows not available

User Action

None.

Load

The Load metric provides information about the number of runnable processes on the system run queue. If this is greater than the number of CPU's on the system, then excess load exists.

CPU in I/O Wait (%)

Represents the average number of jobs waiting for I/O in the last interval.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-11 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

40

80

6

CPU I/O Wait is %value%%%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.


Data Source

Host Data Source
Solaris kernel statistics
HP pstat_getdynamic(), pstat_getprocessor(), pstat_getproc(), pstat_getstatic(), getutent(), pstat_getvminfo() system calls
Linux uptime, free, getconf, ps, iostat, sar, w OS commands; /proc/stat
HP Tru64 table() system call, uptime, vmstat, psrinfo, ps, who, swapon OS commands
IBM AIX oracle_kstat(), getutent(), getproc(), sysconf() system calls
Windows performance data counters

User Action

A high percentage of I/O wait can indicate a hardware problem, a slow NFS server, or poor load-balancing among local file systems and disks. Check the system messages log for any hardware errors. Use the iostat -xn command or the nfsstat -c (NFS client-side statistics) command or both to determine which disks or file systems are slow to respond. Check to see if the problem is with one or more swap partitions, as lack of swap or poor disk load balancing can cause these to become overloaded. Depending on the specific problem, fixes may include: NFS client or server tuning, hardware replacement, moving applications to other file systems, adding swap space, or restructuring a file system for better performance.

CPU in System Mode (%)

For UNIX-based platforms, this metric represents the amount of CPU being used in SYSTEM mode as a percentage of total CPU processing power.

For Windows, this metric represents the percentage of time the process threads spent executing code in privileged mode.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-12 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

not defined

not defined

6

CPU in Kernel Mode, %value%%%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.


Data Source

Host Data Source
Solaris kernel statistics
HP pstat_getdynamic(), pstat_getprocessor(), pstat_getproc(), pstat_getstatic(), getutent(), pstat_getvminfo() system calls
Linux uptime, free, getconf, ps, iostat, sar, w OS commands; /proc/stat
HP Tru64 table() system call, uptime, vmstat, psrinfo, ps, who, swapon OS commands
IBM AIX oracle_kstat(), getutent(), getproc(), sysconf() system calls
Windows performance data counters

User Action

An abnormally high value (determined on the basis of historical data) indicates that the machine is doing a lot of work at the system (kernel) level. The user action varies from case to case.

CPU in User Mode (%)

For UNIX-based platforms, this metric represents the amount of CPU being used in USER mode as a percentage of total CPU processing power.For Windows, this metric represents the percentage of time the processor spends in the user mode. This metric displays the average busy time as a percentage of the sample time.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-13 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

not defined

not defined

6

CPU in User Mode, %value%%%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.


Data Source

Host Data Source
Solaris kernel statistics
HP pstat_getdynamic(), pstat_getprocessor(), pstat_getproc(), pstat_getstatic(), getutent(), pstat_getvminfo() system calls
Linux uptime, free, getconf, ps, iostat, sar, w OS commands; /proc/stat
HP Tru64 table() system call, uptime, vmstat, psrinfo, ps, who, swapon OS commands
IBM AIX oracle_kstat(), getutent(), getproc(), sysconf() system calls
Windows performance data counters

User Action

An abnormally high value (determined on the basis of historical data) indicates the cpu is doing a lot of work at the user (application) level. An examination of the top processes on the system may help identify problematic processes.

CPU Interrupt Time (%)

Represents the percentage of time the processor spends receiving and servicing hardware interrupts during sample intervals. This value is an indirect indicator of the activity of devices that generate interrupts, such as the system clock, the mouse, disk drivers, data communication lines, network interface cards, and other peripheral devices. These devices normally interrupt the processor when they have completed a task or require attention. Normal thread execution is suspended during interrupts. Most system clocks interrupt the processor every 10 milliseconds, creating a background of interrupt activity. Suspends normal thread execution during interrupts.

This metric is available only on Windows.

Data Source

The data sources for this metric are Performance Data counters.

User Action

None.

CPU Queue Length

Processor Queue Length is the number of ready threads in the processor queue. There is a single queue for processor time even on computers with multiple processors. A sustained processor queue of less than 10 threads per processor is normally acceptable, dependent on the workload.

This metric is available only on Windows.

Data Source

The data sources for this metric are Performance Data counters.

User Action

A consistently high value indicates a number of CPU bound tasks. This information should be corelated with other metrics such as Page Transfer Rate. Tuning the system, accompanied with additional memory, should help.

CPU Utilization (%)

For UNIX-based platforms, this metric represents the amount of CPU utilization as a percentage of total CPU processing power available.

For Windows, this metric represents the percentage of time the CPU spends to execute a non-Idle thread. CPU Utilization (%) is the primary indicator of processor activity.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-14 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

80

95

6

CPU Utilization is %value%%%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.


Data Source

Host Data Source
Solaris kernel statistics
HP pstat_getdynamic(), pstat_getprocessor(), pstat_getproc(), pstat_getstatic(), getutent(), pstat_getvminfo() system calls
Linux uptime, free, getconf, ps, iostat, sar, w OS commands; /proc/stat
HP Tru64 table() system call, uptime, vmstat, psrinfo, ps, who, swapon OS commands
IBM AIX oracle_kstat(), getutent(), getproc(), sysconf() system calls
Windows performance data counters

User Action

An abnormally high value (determined on the basis of historical data) indicates that the system is under heavy load. If the value is consistently high, consider reducing the load on the system.

Free Logical Memory (%)

Represents logical free memory in a system (discounting memory used for filesystem buffers). Note that this memory can potentially be freed, and may not be available immediately.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-15 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 5 Minutes

After Every Sample

<

not defined

not defined

6

Logical Free Memory, %value%%%, gone below warning (%warning_threshold%) or critical (%critical_threshold%) threshold.


Data Source

Linux: /proc/meminfo

AIX: libperfstat

User Action

A very low value (determined on the basis of historical data) indicates that the system is running out of RAM and this could be due to one or more of the following reasons. The first is that there is more than the planned number of processes running on the system. The second is that the processes are taking a lot more memory than expected. The third reason is that a specific process is leaking memory consistently.

Free Memory (%)

Represents logical free memory in a system (discounting memory used for filesystem buffers). Note that this memory can potentially be freed, and may not be available immediately.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-16 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 5 Minutes

After Every Sample

<

not defined

not defined

6

Logical Free Memory, %value%%%, gone below warning (%warning_threshold%) or critical (%critical_threshold%) threshold.


Data Source

Host Data Source
Solaris kernel statistics
HP pstat_getdynamic(), pstat_getprocessor(), pstat_getproc(), pstat_getstatic(), getutent(), pstat_getvminfo() system calls
Linux uptime, free, getconf, ps, iostat, sar, w OS commands; /proc/stat
HP Tru64 table() system call, uptime, vmstat, psrinfo, ps, who, swapon OS commands
IBM AIX oracle_kstat(), getutent(), getproc(), sysconf() system calls
Windows Windows API

User Action

On Linux OS this value might always be close to 0%. Please refer Free logical memory (%) for actual free memory that is available for the users. User should not take any action based on the value of this metric

Longest Service Time (ms)

Represents the maximum of the average service time of all disks. Units are represented in milliseconds.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Seconds

Data Source

Host Data Source
Solaris kernel statistics
HP pstat_getdynamic(), pstat_getprocessor(), pstat_getproc(), pstat_getstatic(), getutent(), pstat_getvminfo() system calls
Linux uptime, free, getconf, ps, iostat, sar, w OS commands; /proc/stat
HP Tru64 table() system call, uptime, vmstat, psrinfo, ps, who, swapon OS commands
IBM AIX oracle_kstat(), getutent(), getproc(), sysconf() system calls
Windows Not available

Memory Page Scan Rate (per second)

For UNIX-based systems, this metric represents the number of pages per second scanned by the page stealing daemon.

For Windows, this metric represents the rate at which pages are read from or written to disk to resolve hard page faults. The metric is a primary indicator of the kinds of faults that cause system-wide delays.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-17 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

6

Page scan rate is %value% /sec, crossed warning (%warning_threshold% /sec) or critical (%critical_threshold% /sec) threshold.


Data Source

Host Data Source
Solaris kernel statistics
HP pstat_getdynamic(), pstat_getprocessor(), pstat_getproc(), pstat_getstatic(), getutent(), pstat_getvminfo() system calls
Linux uptime, free, getconf, ps, iostat, sar, w OS commands; /proc/stat
HP Tru64 table() system call, uptime, vmstat, psrinfo, ps, who, swapon OS commands
IBM AIX oracle_kstat(), getutent(), getproc(), sysconf() system calls
Windows performance data counters

User Action

If this number is zero or close to zero, then you can be sure the system has sufficient memory. If scan rate is always high, then adding memory will definitely help.

Memory Utilization (%)

Represents the amount of free memory as a percentage of total memory.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-18 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

80

95

6

Memory Utilization is %value%%%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.


Data Source

Host Data Source
Solaris kernel statistics
HP pstat_getdynamic(), pstat_getprocessor(), pstat_getproc(), pstat_getstatic(), getutent(), pstat_getvminfo() system calls
Linux uptime, free, getconf, ps, iostat, sar, w OS commands; /proc/stat
HP Tru64 table() system call, uptime, vmstat, psrinfo, ps, who, swapon OS commands
IBM AIX oracle_kstat(), getutent(), getproc(), sysconf() system calls
Windows Windows API

User Action

On Linux OS this value might always be close to 100%. Please refer to Free logical memory (%) for actual free memory that is available for the users. User should not take any action based on the value of this metric.

Page Transfers Rate

Indicates the rate at which pages are read from or written to disk to resolve hard page faults. It is a primary indicator of the kinds of faults that cause system wide delays. It is counted in numbers of pages. It includes pages retrieved to satisfy faults in the file system cache (usually requested by applications) non-cached mapped memory files.

This metric is available only on Windows.

Data Source

The data sources for this metric are Windows Performance counters.

User Action

High transfer rates indicate a memory contention. Adding memory would help.

Run Queue Length (1 minute average)

Represents the average number of processes in memory and subject to be run in the last interval. This metric checks the run queue.

This metric is not available on Windows.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-19 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

not defined

not defined

6

CPU Load (Run Queue Length averaged over 1 minute) is %value%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.


Data Source

Host Data Source
Solaris kernel statistics
HP pstat_getdynamic(), pstat_getprocessor(), pstat_getproc(), pstat_getstatic(), getutent(), pstat_getvminfo() system calls
Linux uptime, free, getconf, ps, iostat, sar, w OS commands; /proc/stat
HP Tru64 table() system call, uptime, vmstat, psrinfo, ps, who, swapon OS commands
IBM AIX oracle_kstat(), getutent(), getproc(), sysconf() system calls
Windows not available

User Action

Check the load on the system using the UNIX uptime or top commands. Also, check for processes using too much CPU time by using the top and ps -ef commands. Note that the issue may be a large number of instances of one or more processes, rather than a few processes each taking up a large amount of CPU time. Kill processes using excessive CPU time.

Run Queue Length (5 minute average)

Represents the average number of processes in memory and subject to be run in the last interval. This metric checks the run queue.

This metric is not available on Windows.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-20 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

10

20

6

CPU Load (Run Queue Length averaged over 5 minutes) is %value%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.


Data Source

Host Data Source
Solaris kernel statistics
HP pstat_getdynamic(), pstat_getprocessor(), pstat_getproc(), pstat_getstatic(), getutent(), pstat_getvminfo() system calls
Linux uptime, free, getconf, ps, iostat, sar, w OS commands; /proc/stat
HP Tru64 table() system call, uptime, vmstat, psrinfo, ps, who, swapon OS commands
IBM AIX oracle_kstat(), getutent(), getproc(), sysconf() system calls
Windows not available

User Action

Check the load on the system using the UNIX uptime or top commands. Also, check for processes using too much CPU time by using the top and ps -ef commands. Note that the issue may be a large number of instances of one or more processes, rather than a few processes each taking up a large amount of CPU time. Kill processes using excessive CPU time.

Run Queue Length (15 minute average)

Represents the average number of processes in memory and subject to be run in the last interval. This metric checks the run queue.

This metric is not available on Windows.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-21 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

not defined

not defined

6

CPU Load (Run Queue Length averaged over 5 minutes) is %value%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.


Data Source

Host Data Source
Solaris kernel statistics
HP pstat_getdynamic(), pstat_getprocessor(), pstat_getproc(), pstat_getstatic(), getutent(), pstat_getvminfo() system calls
Linux uptime, free, getconf, ps, iostat, sar, w OS commands; /proc/stat
HP Tru64 table() system call, uptime, vmstat, psrinfo, ps, who, swapon OS commands
IBM AIX oracle_kstat(), getutent(), getproc(), sysconf() system calls
Windows not available

User Action

Check the load on the system using the UNIX uptime or top commands. Also, check for processes using too much CPU time by using the top and ps -ef commands. Note that the issue may be a large number of instances of one or more processes, rather than a few processes each taking up a large amount of CPU time. Kill processes using excessive CPU time.

Swap Utilization (%)

For UNIX-based platforms, this metric represents the percentage of swapped memory in use for the last interval.

For Windows, this metric represents the percentage of page file instance used.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-22 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

80

95

6

Swap Utilization is %value%%%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.


Data Source

Host Data Source
Solaris kernel statistics
HP pstat_getdynamic(), pstat_getprocessor(), pstat_getproc(), pstat_getstatic(), getutent(), pstat_getvminfo() system calls
Linux uptime, free, getconf, ps, iostat, sar, w OS commands; /proc/stat
HP Tru64 table() system call, uptime, vmstat, psrinfo, ps, who, swapon OS commands
IBM AIX oracle_kstat(), getutent(), getproc(), sysconf() system calls
Windows Windows API and Performance data counters

User Action

For UNIX-based platforms, check the swap usage using the UNIX top command or the Solaris swap -l command. Additional swap can be added to an existing file system by creating a swap file and then adding the file to the system swap pool. (See documentation for your UNIX OS). If swap is mounted on /tmp, space can be freed by removing any junk files in /tmp. If it is not possible to add file system swap or free up enough space, additional swap will have to be added by adding a raw disk partition to the swap pool. See UNIX documentation for procedures.

For Windows, check the page file usage and add an additional page file if current limits are insufficient.

Total Disk I/O Per Second

Represents the rate of I/O (read and write) operations, calculated from all disks.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-23 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

not defined

not defined

6

Disk totIO %value%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.


Data Source

Host Data Source
Solaris kernel statistics
HP pstat_getdynamic(), pstat_getprocessor(), pstat_getproc(), pstat_getstatic(), getutent(), pstat_getvminfo() system calls
Linux uptime, free, getconf, ps, iostat, sar, w OS commands; /proc/stat
HP Tru64 table() system call, uptime, vmstat, psrinfo, ps, who, swapon OS commands
IBM AIX oracle_kstat(), getutent(), getproc(), sysconf() system calls
Windows not available

Total Processes

Represents the total number of processes currently running on the system. This metric checks the number of processes running on the system.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-24 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

not defined

not defined

6

Number of processes is %value%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.


Data Source

Host Data Source
Solaris kernel statistics
HP pstat_getdynamic(), pstat_getprocessor(), pstat_getproc(), pstat_getstatic(), getutent(), pstat_getvminfo() system calls
Linux uptime, free, getconf, ps, iostat, sar, w OS commands; /proc/stat
HP Tru64 table() system call, uptime, vmstat, psrinfo, ps, who, swapon OS commands
IBM AIX oracle_kstat(), getutent(), getproc(), sysconf() system calls
Windows performance data counters

User Action

An abnormally high value (determined on the basis of historical data) indicates that the system is under heavy load. If the value is consistently high, consider reducing the load on the system by stopping the number of processes.

Total Swap, Kilobytes

Total amount of page file space available to be allocated by processes. Paging files are shared by all processes and the lack of space in paging files can prevent processes from allocating memory.

This metric is available only on Windows.

Data Source

Performance Data counters and Windows API GlobalMemoryStatusEx

User Action

An abnormally high value (determined on the basis of historical data) indicates that the system is doing a lot of swapping by moving data either to or from the disk. This typically will slow down the system because of the relatively slower access to the disk. The reason for this could be one or more of the following:

  • There are many processes running on the system competing for a limited RAM and this results in more swapping. User can try to reduce the load by stopping some process

  • A process occupying more memory than expected leading to a shortage of available memory

Typically these kinds of problems are solved by adding more RAM.

Total Users

Represents the total number of users currently logged into the system. This metric checks the number of users running on the system.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-25 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

not defined

not defined

6

Number of users is %value%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.


Data Source

Host Data Source
Solaris kernel statistics
HP pstat_getdynamic(), pstat_getprocessor(), pstat_getproc(), pstat_getstatic(), getutent(), pstat_getvminfo() system calls
Linux uptime, free, getconf, ps, iostat, sar, w OS commands; /proc/stat
HP Tru64 table() system call, uptime, vmstat, psrinfo, ps, who, swapon OS commands
IBM AIX oracle_kstat(), getutent(), getproc(), sysconf() system calls
Windows not available

User Action

An abnormally high value (determined on the basis of historical data) indicates that the system is under heavy load. If the value is consistently high, consider reducing the load on the system by restricting or removing active users from the system.

Used Swap, Kilobytes

Represents the size in kilobytes of the page file instance used.

This metric is available only on Windows.

Data Source

Performance Data counters and Windows API GlobalMemoryStatusEx.

User Action

An abnormally high value (determined on the basis of historical data) indicates that the system is doing a lot of swapping by moving data either to or from the disk. This typically will slow down the system because of the relatively slower access to the disk. The reason for this could be one or more of the following:

  • There are many processes running on the system competing for a limited RAM and this results in more swapping. User can try to reduce the load by stopping some process

  • A process occupying more memory than expected leading to a shortage of available memory

Typically these kinds of problems are solved by adding more RAM.

Log File Monitoring

The Log File Monitoring metric allows the operator to monitor one or more log files for the occurrence of one or more perl patterns in the content. In addition, the operator can specify a perl pattern to be ignored for the log file. Periodic scanning will be performed against new content added since the last scan, lines matching the ignore pattern will be ignored first, then lines matching specified match patterns will result in one record being uploaded to the repository for each pattern. The user can set a threshold against the number of lines matching the given pattern. File rotation will be handled within the given file.

Log File Pattern Matched Content

Returns the actual content if the given file has been specifically registered for content uploading, else it will return the count of lines that matched the pattern specified.

The operator can list the names of files or directories to be never monitored in <EMDROOT>/sysman/config/lfm_efiles file. The operator can list the names of the files or directories whose contents can be uploaded into Oracle Management Repository in <EMDROOT>/sysman/config/lfm_ifiles file.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

Oracle provided perl program that scans files for the occurrence of user specified perl patterns.

User Action

None.

Log File Pattern Matched Line Count

Returns the number of lines matching the pattern specified in the given file. Setting warning or critical thresholds against this column for a specific {log file name, match pattern in perl, ignore pattern in perl} triggers the monitoring of specified criteria against the given log file.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-26 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 15 Minutes

After Every Sample

>

0

Not Defined

1*

%log_file_message% Crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.


* Once an alert is triggered for this metric, it must be manually cleared.

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Log File Name", "Match Pattern in Perl", "Ignore Pattern in Perl", and "Time Stamp" objects.

If warning or critical threshold values are currently set for any unique combination of "Log File Name", "Match Pattern in Perl", "Ignore Pattern in Perl", and "Time Stamp" objects, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each unique combination of "Log File Name", "Match Pattern in Perl", "Ignore Pattern in Perl", and "Time Stamp" objects, use the Edit Thresholds page.

Data Source

Oracle supplied perl program monitors the log files for user specified criteria.

User Action

None.

Memory Devices

The Memory Devices metric monitors the status of memory devices configured in the system.

Bank Location

Represents the bank location name of the memory device, when applicable.

This metric is available only on Dell Poweredge Linux Systems.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

SNMP MIB object: memoryDeviceStatus (1.3.6.1.4.1.674.10892.1.1100.50.1.5)

User Action

None.

Location

Represents the location name of the memory device, for example, "DIMM A".

This metric is available only on Dell Poweredge Linux Systems.

Metric Value Meaning (per SNMP MIB)
1 Other (not one of the following)
2 Unknown
3 Normal
4 Warning
5 Critical
6 Non-Recoverable

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

SNMP MIB object: memoryDeviceStatus (1.3.6.1.4.1.674.10892.1.1100.50.1.5)

User Action

None.

Memory Status

Represents the status of the memory device.

This metric is available only on Dell Poweredge Linux Systems.

The following table lists the possible values for this metric and their meaning.

Metric Value Meaning (per SNMP MIB)
1 Other (not one of the following)
2 Unknown
3 Normal
4 Warning
5 Critical
6 Non-Recoverable

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-27 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 15 Minutes

Not Uploaded

>=

4

5

1

Status of Memory at bank location %MemoryBankLocation% and location %MemoryLocation% is %value%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.


Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Chassis" and "Index" objects.

If warning or critical threshold values are currently set for any unique combination of "Chassis" and "Index" objects, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each unique combination of "Chassis" and "Index" objects, use the Edit Thresholds page.

Data Source

SNMP MIB object: memoryDeviceStatus (1.3.6.1.4.1.674.10892.1.1100.50.1.5)

User Action

None.

Size

Represents the size, in kilobytes, of the memory device.

This metric is available only on Dell Poweredge Linux Systems.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

SNMP MIB object: memoryDeviceSize (1.3.6.1.4.1.674.10892.1.1100.50.1.14)

User Action

None.

Type

Represents the type of the memory device.

This metric is available only on Dell Poweredge Linux Systems.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

SNMP MIB object: memoryDeviceSize (1.3.6.1.4.1.674.10892.1.1100.50.1.14)

User Action

None.

Message and Semaphore Activity

The Message and Semaphore Activity metric provides information about the message and semaphore activity of the host system being monitored.

The following table lists the metrics and their descriptions.

msgrcv() System Calls (per second)

Represents the number of msgrcv system calls made per second. The msgrcv system call reads a message from one queue to another user-defined queue.

Data Source

The data sources for this metric include the following:

Host Data Source
Solaris sar command
HP sar command
Linux not available
HP Tru64 ipcs command
IBM AIX sar command
Windows not available

User Action

None.

semop() System Calls (per second)

Represents the number of semop system calls made per second. The semop system call is used to perform semaphore operations on a set of semaphores.

Data Source

The data sources for this metric include the following:

Host Data Source
Solaris sar command
HP sar command
Linux not available
HP Tru64 ipcs command
IBM AIX sar command
Windows not available

User Action

None.

IO Card Details

The metric holds the information about the IO cards in the host, including pci cards and USBs.

Bus Type

This is the bus type of the IO card.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

lspci

User Action

None.

Frequency

The clock frequency of the IO card.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

lspci

User Action

None.

Name

This represents the name of the IO card.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

lspci

User Action

None.

Revision

This represents the IO card revision.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

lspci

User Action

None.

Vendor Name

This represents the manufacturer name of IO card.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

lspci

User Action

None.

Network Interface Count

This metric relates to network interface cards, both unbonded and bonded interface cards. Slave interface cards have the same information as bonded cards.

BroadCast Address

Broadcast address of the local area network.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

ifconfig

User Action

None.

Default Gateway

Default gateway configured for this host.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

ifconfig

User Action

None.

Description

A description of the Network Interface Card.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

ifconfig

User Action

None.

Is DHCP Enabled

Represents whether this Network Interface Card (NIC) is configured for dynamic or static ip addresses

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

ifconfig

User Action

None.

Flags

Network interface card's Flags

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

ifconfig

User Action

None.

Hostname Aliases

This represents the aliases for the host corresponding to this Network Interface Card.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

arp

User Action

None.

IP Address

IP address associated with this Network Interface Card. This is supposed to be an IPV4 address.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

ifconfig

User Action

None.

IPV6 Addresses

This is comma-separated list of IPV6 addresses.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

ifconfig

User Action

None.

MAC Address

Hardware address of the Network Interface Card.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

ifconfig

User Action

None.

NetMask

This is subnet mask inet address.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

ifconfig

User Action

None.

Maximum Transfer Unit

Maximum packet size that to be sent it from this Network Interface Card. This is in bytes.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

ifconfig

User Action

None.

Name

Network interface card name.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

ifconfig

User Action

None.

Network Interface Bonds

This metric relates to bonded network interface cards. Slave interface cards have the same information as bonded cards.

Bond Name

Name of the bond.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Mode of the Bond

Mode of the bonds. This can be balance-alb.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Options of the Bond

Options/properties of the bond. This can be something like "miimon=100 max_bonds=4."

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Primary Slave

Primary slave of the bond. The Network Interface Card which is the primary slave of the bond.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Secondary Slaves

Comma separated list of secondary slaves.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Operating System

This metric contains the operating summary information. There will be one row per host.

Address Length (Bits)

This is the OS address length. This is either 32 bit or 64 bit.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

uname -a

User Action

None.

Base Version

Base version of the OS

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

uname -a

User Action

None.

Is DB Machine Member

When host is member Database Machine, this columns will have a value of 1.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

uname -a

User Action

None.

Default OS Run Level

Default Run level of the OS running on the host. Whenever the OS is booted, it will be booted to this run level.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

uname -a

User Action

None.

Distribution Version

This is only applicable for Linux. Represents OS distributed version

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

uname -a

User Action

None.

Max Swap Space (MB)

This represents Maximum swap space available for the OS.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

uname -a

User Action

None.

Name

Name of the OS

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

/etc/enterprise-release for OEL

/etc/redhat-release for redhat

/etc/UnitedLinux-release

/etc/SuSE-release

User Action

None.

Platform ID

This is the platform id number

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

uname -a

User Action

None.

Update Level

Latest update level of this OS

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

uname -a

User Action

None.

Vendor Name

This represents the OS vendor name.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

/etc/enterprise-release for OEL

/etc/redhat-release for redhat

/etc/UnitedLinux-release

User Action

None.

Operating System Components

This metric stores the information about OS components, including Patches, Bundles, and Packages.

Description

Description of the component

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

/bin/rpm

User Action

None.

Installation Date

Installation date of the component.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

/bin/rpm

User Action

None.

Name

Name of the OS component.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

/bin/rpm

User Action

None.

Type

Type of OS components. This can be Patch, Bundle, Package.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

/bin/rpm

User Action

None.

Version

Version of the component.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

/bin/rpm

User Action

None.

File Systems

This lists all file systems mounted in the host.

Disk Space (GB)

File System capacity in GB.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

/etc/mtab

User Action

None.

Local Drive

Applicable NT only.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

/etc/mtab

User Action

None.

Mount Location

Mount location of the file system.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

/etc/mtab

User Action

None.

Mount Options

This metric contains details about the mount options. These could be similar to "rw,intr,largefiles,logging,xattr,onerror=panic."

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

/etc/mtab

User Action

None.

Resource Name

This is the device path of host. This can be /dev/hd10opt, Local Disk (C:)

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

/etc/mtab

User Action

None.

Type

This is the file system type. Examples include nfs, ntfs, and jfs.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

/etc/mtab

User Action

None.

Operating System Properties

This metric lists some of the OS properties, including OPEN_MAX, Semaphore values, and kernel.pid_max.

Name

Name of configuration variable of the OS, for example OPEN_MAX.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

/bin/getconf, ulimit

Source

This is the source of the property info. This can be similar to /sbin/sysctl or /usr/bin/getconf.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

/bin/getconf , ulimit

Value

This is the value of the property.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

/bin/getconf , ulimit

Operating System Registered Software

This metric contains details of all the OS Registered Software.

Description

Any vendor description for the software.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

/bin/rpm

User Action

Informational only.

ID

ID of Software installed in the host. Only applicable for NT/Windows.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

/bin/rpm

User Action

Informational only.

Installation Date

Installation date of the software.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

/bin/rpm

User Action

Informational only.

Installed Location

The location where the software is installed.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

/bin/rpm

User Action

Informational only.

Media Type

Installation or distribution source of the installed product. For example, the package name, bundling application, or distro.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

/bin/rpm

User Action

Informational only.

Name

Name of installed software.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

/bin/rpm

User Action

Informational only.

Vendor Name

Vendor who provided the software

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

/bin/rpm

User Action

Informational only.

Vendor Specific Information

Anything related to software

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

/bin/rpm

User Action

Informational only.

Version

Any vendor description for the software.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

/bin/rpm

User Action

Informational only.

Virtual Machine

Represents the Solaris zone name in which the product is installed.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

/bin/rpm

User Action

Informational only.

Parent Product Identifier

Parent ID of the installed product. Applicable to the Sun Service Tag product taxonomy

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

/bin/rpm

User Action

Informational only.

Product Parent Name

Descriptive parent name of the installed product. Applicable to the Sun Service Tag product taxonomy

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

/bin/rpm

User Action

Informational only.

Software Architecture

CPU/OS architecture the application is designed to run on e.g., Solaris SPARC (64bit)

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

/bin/rpm

User Action

Informational only.

Operating System ULIMITS

This metric contains details of the operating system ULIMITS.

CoreDump (blocks)

Limits the size of a "core" file left behind when a process encounters a segmentation fault or other unexpected fatal error.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Time (seconds)

Maximum CPU time a process can use before it get terminated. CPU time is the amount of time the CPU actual spends executing processor instructions and is often much less than the total program "runs time".

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data (kbytes)

Limits the amount of memory that a process can allocate on the heap, as with malloc, calloc, C++ "new," and most object creation in higher-level languages. Specified in kilobytes.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

File (blocks)

Maximum size of the file a process can create. Number will be in 512 bytes (one block).

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

NoFiles (descriptors)

This number represents maximum number of files that can be opened at a time.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Stack (kbytes)

Limits the amount of memory a process can allocate on the stack, as in the case of local variables in C, C++, and many other languages.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Virtual Mem (kbytes)

Maximum memory that can be allocated to a process. This includes all types of memory, including the stack, the heap, and memory-mapped files Attempts to allocate memory in excess of this limit will fail with an out-of-memory error.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Network Interfaces

The Network Interfaces metric includes input errors and interface collisions on the network interface. The following network interfaces are supported: le, hme, qfe, ge, and fddi.

Network Interface Collisions (%)

Represents the number of collisions per second. This metric checks the rate of collisions on the network interface specified by the network device names parameter, such as le0 or * (for all network interfaces).

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris kernel memory structures (kstat)
HP netstat, lanscan, and lanadmin commands
Linux netstat command and /proc/net/dev
HP Tru64 netstat command
IBM AIX oracle_kstat() system call
Windows not available

User Action

Use the OS netstat -i command to check the performance of the interface. Also, check the system messages file for messages relating to duplex setting by using the OS grep -i command and searching for the word 'duplex'.

Network Interface Combined Utilization (%)

Represents the percentage of network bandwidth being used by reading and writing from and to the network for full-duplex network connections.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-28 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

6

Network utilization for %keyvalue% is %value%%%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.


Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "Network Interface Name" object.

If warning or critical threshold values are currently set for any "Network Interface Name" object, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each "Network Interface Name" object, use the Edit Thresholds page.

Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris kernel memory structures (kstat)
HP netstat, lanscan, and lanadmin commands
Linux netstat command and /proc/net/dev
HP Tru64 netstat command
IBM AIX oracle_kstat() system call
Windows not available

User Action

Use the OS netstat -i command to check the performance of the interface. Also, check the system messages file for messages relating to duplex setting by using the OS grep -i command and searching for the word 'duplex'.

Network Interface Input Errors (%)

Represents the number of input errors, per second, encountered on the device for unsuccessful reception due to hardware/network errors. This metric checks the rate of input errors on the network interface specified by the network device names parameter, such as le0 or * (for all network interfaces).

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris kernel memory structures (kstat)
HP netstat, lanscan, and lanadmin commands
Linux netstat command and /proc/net/dev
HP Tru64 netstat command
IBM AIX oracle_kstat() system call
Windows not available

User Action

Use the OS netstat -i command to check the performance of the interface. Also, check the system messages file for messages relating to duplex setting by using the OS grep -i command and searching for the word 'duplex'.

Network Interface Output Errors (%)

Represents the number of output errors per second. This metric checks the rate of output errors on the network interface specified by the network device names parameter, such as le0 or * (for all network interfaces).

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris kernel memory structures (kstat)
HP netstat, lanscan, and lanadmin commands
Linux netstat command and /proc/net/dev
HP Tru64 netstat command
IBM AIX oracle_kstat() system call
Windows not available

User Action

Use the OS netstat -i command to check the performance of the interface. Also, check the system messages file for messages relating to duplex setting by using the OS grep -i command and searching for the word 'duplex'.

Network Interface Read (MB/s)

Represents the amount of megabytes per second read from the specific interface.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris kernel memory structures (kstat)
HP netstat, lanscan, and lanadmin commands
Linux netstat command and /proc/net/dev
HP Tru64 not available
IBM AIX perfstat system call
Windows not available

User Action

Use the OS netstat -i command to check the performance of the interface. Also, check the system messages file for messages relating to duplex setting by using the OS grep -i command and searching for the word 'duplex'.

Network Interface Read Utilization (%)

Represents the amount of network bandwidth being used for reading from the network as a percentage of total read capacity.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris kernel memory structures (kstat)
HP netstat, lanscan, and lanadmin commands
Linux netstat command and /proc/net/dev
HP Tru64 not available
IBM AIX perfstat system call
Windows not available

User Action

Use the OS netstat -i command to check the performance of the interface. Also, check the system messages file for messages relating to duplex setting by using the OS grep -i command and searching for the word 'duplex'.

Network Interface Total Error Rate (%)

Represents the number of total errors per second, encountered on the network interface. It is the rate of read and write errors encountered on the network interface.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-29 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

6

Network Error Rate for %keyvalue% is %value%%%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.


Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "Network Interface Name" object.

If warning or critical threshold values are currently set for any "Network Interface Name" object, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each "Network Interface Name" object, use the Edit Thresholds page.

Data Source

It is computed as the sum of Network Interface Input Errors (%) and Network Interface Output Errors (%).

User Action

Use the OS netstat -i command to check the performance of the interface. Also, check the system messages file for messages relating to duplex setting by using the OS grep -i command and searching for the word 'duplex'.

Network Interface Total I/O Rate (MB/sec)

Represents the total I/O rate on the network interface. It is measured as the sum of Network Interface Read (MB/s) and Network Interface Write (MB/s).

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-30 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

6

Network I/O Rate for %keyvalue% is %value%MB/Sec, crossed warning (%warning_threshold%MB/Sec) or critical (%critical_threshold%MB/Sec) threshold.


Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "Network Interface Name" object.

If warning or critical threshold values are currently set for any "Network Interface Name" object, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each "Network Interface Name" object, use the Edit Thresholds page.

Data Source

It is computed as the sum of Network Interface Read (MB/s) and Network Interface Write (MB/s).

User Action

Use the OS netstat -i command to check the performance of the interface. Also, check the system messages file for messages relating to duplex setting by using the OS grep -i command and searching for the word 'duplex'.

Network Interface Write (MB/s)

Represents the amount of megabytes per second written to the specific interface.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Minutes

Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris kernel memory structures (kstat)
HP netstat, lanscan, and lanadmin commands
Linux netstat command and /proc/net/dev
HP Tru64 netstat command
IBM AIX oracle_kstat() system call
Windows not available

User Action

Use the OS netstat -i command to check the performance of the interface. Also, check the system messages file for messages relating to duplex setting by using the OS grep -i command and searching for the word 'duplex'.

Network Interface Write Utilization (%)

Represents the amount of network bandwidth being used for writing to the network as a percentage of total read capacity.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Minutes

Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris kernel memory structures (kstat)
HP netstat, lanscan, and lanadmin commands
Linux netstat command and /proc/net/dev
HP Tru64 not available
IBM AIX perfstat system call
Windows not available

User Action

Use the OS netstat -i command to check the performance of the interface. Also, check the system messages file for messages relating to duplex setting by using the OS grep -i command and searching for the word 'duplex'.

Paging Activity

The Paging Activity metric provides the amount of paging activity on the system.

Address Translation Page Faults (per second)

Represents the minor page faults by way of hat_fault() per second. This metric checks the number of faults for the CPU(s) specified by the Host CPU(s) parameter, such as cpu_stat0 or * (for all CPUs on the system).

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris kernel statistics (class misc cpu_stat)
HP pstat_getvminfo() system call
Linux not available
HP Tru64 table() system call and vmstat command
IBM AIX oracle_kstat() system call
Windows not available

User Action

Informational only.

Cache Faults (per second)

The Cache Faults/sec is the rate at which faults occur when a page sought in the file system cache is not found and must be retrieved from elsewhere in memory (a soft fault) or from disk (a hard fault). The file system cache is an area of physical memory that stores recently used pages of data for applications. Cache activity is a reliable indicator of most application I/O operations. This metric shows the number of faults, without regard for the number of pages faulted in each operation.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris not available
HP not available
Linux not available
HP Tru64 not available
IBM AIX not available
Windows Performance Data counters

User Action

Informational only.

Copy-on-write Faults (per second)

Copy-on-Write faults/sec is the rate at which page faults are caused by attempts to write that have been satisfied by coping of the page from elsewhere in physical memory. This is an economical way of sharing data since pages are only copied when they are written to; otherwise, the page is shared. This metric shows the number of copies, without regard for the number of pages copied in each operation.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris not available
HP not available
Linux not available
HP Tru64 not available
IBM AIX not available
Windows Performance Data counters

User Action

Informational only

Demand Zero Faults (per second)

Demand Zero Faults/sec is the rate at which a zeroed page is required to satisfy the fault. Zeroed pages, pages emptied of previously stored data and filled with zeros, are a security feature of Windows that prevent processes from seeing data stored by earlier processes that used the memory space. Windows maintains a list of zeroed pages to accelerate this process. This metric shows the number of faults, without regard to the number of pages retrieved to satisfy the fault.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris not available
HP not available
Linux not available
HP Tru64 not available
IBM AIX not available
Windows Performance Data counters

User Action

Informational only.

igets with Page Flushes(%)

Represents the percentage of UFS inodes taken off the freelist by iget which had reusable pages associated with them. These pages are flushed and cannot be reclaimed by processes.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris kernel statistics (class misc cpu_stat)
HP pstat_getvminfo system call
Linux not available
HP Tru64 not available
IBM AIX oracle_kstat() system call
Windows not available

User Action

Informational only.

Page Faults (per second)

Page Faults/sec is the average number of pages faulted per second. It is measured in number of pages faulted per second because only one page is faulted in each fault operation, hence this is also equal to the number of page fault operations. This metric includes both hard faults (those that require disk access) and soft faults (where the faulted page is found elsewhere in physical memory.) Most processors can handle large numbers of soft faults without significant consequence. However, hard faults, which require disk access, can cause significant delays.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris not available
HP not available
Linux not available
HP Tru64 not available
IBM AIX not available
Windows Performance Data Counters

User Action

Informational only.

Page Faults from Software Lock Requests

Represents the number of protection faults per second. These faults occur when a program attempts to access memory it should not access, receives a segmentation violation signal, and dumps a core file. This metric checks the number of faults for the CPU(s) specified by the Host CPU(s) parameter, such as cpu_stat0 or * (for all CPUs on the system).

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris kernel statistics (class misc cpu_stat)
HP pstat_getvminfo system call
Linux not available
HP Tru64 table() system call and vmstat command
IBM AIX perfstat system call
Windows not available

User Action

Informational only.

Page-in Requests (per second)

For UNIX-based systems, represents the number of page read ins per second (read from disk to resolve fault memory references) by the virtual memory manager. Along with Page Outs, this statistic represents the amount of real I/O initiated by the virtual memory manager. This metric checks the number of page read ins for the CPU(s) specified by the Host CPU(s) parameter, such as cpu_stat0 or * (for all CPUs on the system).For Windows, this metric is the rate at which the disk was read to resolve hard page faults. It shows the number of reads operations, without regard to the number of pages retrieved in each operation. Hard page faults occur when a process references a page in virtual memory that is not in working set or elsewhere in physical memory, and must be retrieved from disk. This metric is a primary indicator of the kinds of faults that cause system wide delays. It includes read operations to satisfy faults in the file system cache (usually requested by applications) and in non-cached mapped memory files.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris kernel statistics (class misc cpu_stat)
HP pstat_getvminfo system call
Linux not available
HP Tru64 table() system call and vmstat command
IBM AIX oracle_kstat() system call
Windows performance data counters

User Action

Informational only.

Page-Out Requests (per second)

For UNIX-based systems, represents the number of page write outs to disk per second. This metric checks the number of page write outs for the CPU(s) specified by the Host CPU(s) parameter, such as cpu_stat0 or * (for all CPUs on the system).For Windows, this metric is the rate at which pages are written to disk to free up space in physical memory. Pages are written to disk only if they are changed while in physical memory, so they are likely to hold data, not code. This metric shows write operations, without regard to the number of pages written in each operation.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris kernel statistics (class misc cpu_stat)
HP pstat_getvminfo system call
Linux not available
HP Tru64 vmstat command
IBM AIX oracle_kstat() system call
Windows performance data counters

User Action

Informational only.

Pages Paged-in (per second)

For UNIX-based systems, represents the number of pages paged in (read from disk to resolve fault memory references) per second. This metric checks the number of pages paged in for the CPU(s) specified by the Host CPU(s) parameter, such as cpu_stat0 or * (for all CPUs on the system).For Windows, this metric is the rate at which pages are read from disk to resolve hard page faults. Hard page faults occur when a process refers to a page in virtual memory that is not in its working set or elsewhere in physical memory, and must be retrieved from disk. When a page is faulted, the system tries to read multiple contiguous pages into memory to maximize the benefit of the read operation.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris kernel statistics (class misc cpu_stat)
HP pstat_getvminfo system call
Linux sar command
HP Tru64 table() system call and vmstat command
IBM AIX oracle_kstat() system call
Windows performance data counters

User Action

Informational only.

Pages Paged-out (per second)

For UNIX-based systems, represents the number of pages written out (per second) by the virtual memory manager. Along with Page Outs, this statistic represents the amount of real I/O initiated by the virtual memory manager. This metric checks the number of pages paged out for the CPU(s) specified by the Host CPU(s) parameter, such as cpu_stat0 or * (for all CPUs on the system).For Windows, this metric is the rate at which pages are written to disk to free up space in physical memory. Pages are written back to disk only if they are changed in physical memory, so they are likely to hold data, not code. A high rate of pages output might indicate a memory shortage. Windows writes more pages back to disk to free up space when physical memory is in short supply.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-31 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 15 Minutes

After Every Sample

>

Not Defined

Not Defined

6

Pages Paged-out (per second) %value%, has crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.


Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris kernel statistics (class misc cpu_stat)
HP pstat_getvminfo() system call
Linux sar command
HP Tru64 vmstat command
IBM AIX oracle_kstat() system call
Windows performance data counters

User Action

Informational only.

Pages Put on Freelist by Page Stealing Daemon (per second)

Represents the number of pages that are determined unused, by the pageout daemon (also called the page stealing daemon), and put on the list of free pages.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris kernel statistics (class misc cpu_stat)
HP pstat_getvminfo system call
Linux not available
HP Tru64 table() system call and vmstat command
IBM AIX oracle_kstat() system call
Windows not available

User Action

Informational only.

Pages Scanned by Page Stealing Daemon (per second)

Represents the scan rate is the number of pages per second scanned by the page stealing daemon.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-32 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 15 Minutes

After Every Sample

>

Not Defined

Not Defined

6

Pages Paged-In (per second) %value%, has crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.


Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris kernel statistics (class misc cpu_stat)
HP pstat_getvminfo() system call
Linux not available
HP Tru64 table() system call and vmstat command
IBM AIX oracle_kstat() system call
Windows not available

User Action

If this number is zero or closer to zero, then you can be sure the system has sufficient memory. If the number is always high, then adding memory will definitely help.

Transition Faults (per second)

Transition Faults/sec is the rate at which page faults are resolved by recovering pages that were being used by another process sharing the page, or were on the modified page list or the standby list, or were being written to disk at the time of the page fault. The pages were recovered without additional disk activity. Transition faults are counted in numbers of faults; because only one page is faulted in each operation, it is also equal to the number of pages faulted.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris not available
HP not available
Linux not available
HP Tru64 not available
IBM AIX not available
Windows performance data counters

User Action

Informational only.

PCI Devices

The Peripheral Component Interconnect (PCI) Devices metric monitors the status of PCI devices.

Description

Descriptive name of the Dell Peripheral Component Interconnect (PCI) Device

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

SNMP MIB object: pCIDeviceDescriptionName (1.3.6.1.4.1.674.10892.1.1100.80.1.9)

User Action

None.

Manufacturer

Name of the Dell Peripheral Component Interconnect (PCI) Device

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

SNMP MIB object: pCIDeviceManufacturerName (1.3.6.1.4.1.674.10892.1.1100.80.1.8)

User Action

None.

PCI Device Status

Represents the status of the Dell Peripheral Component Interconnect (PCI) Device.

This metric is available only on Dell Poweredge Linux Systems.

The following table lists the possible values for this metric and their meaning.

Metric Value Meaning (per SNMP MIB)
1 Other (not one of the following)
2 Unknown
3 Normal
4 Warning
5 Critical
6 Non-Recoverable

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-33 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 15 Minutes

Not Uploaded

>=

4

5

1

Status of PCIDevice %PCIDeviceIndex% in chassis %ChassisIndex% is %value%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.


Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Chassis Index", "PCI Device Index", and "System Slot Index" objects.

If warning or critical threshold values are currently set for any unique combination of "Chassis Index", "PCI Device Index", and "System Slot Index" objects, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each unique combination of "Chassis Index", "PCI Device Index", and "System Slot Index" objects, use the Edit Thresholds page.

Data Source

SNMP MIB object: pCIDeviceStatus (1.3.6.1.4.1.674.10892.1.1100.80.1.5)

User Action

None.

Power Supplies

The Power Supplies metric monitors the status of various power supplies present in the host system.

This metric is available only on Dell Poweredge Linux Systems.

Location

Represents the location name of the power supply

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

SNMP MIB object: powerSupplyLocationName (1.3.6.1.4.1.674.10892.1.600.12.1.8)

User Action

None.

Output (Tenths of Watts)

Represents the maximum sustained output wattage of the power supply, in tenths of watts.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

SNMP MIB object: powerSupplyOutputWatts (1.3.6.1.4.1.674.10892.1.600.12.1.6)

User Action

None.

Power Supply Status

Represents the status of the power supply.

This metric is available only on Dell Poweredge Linux Systems.

The following table lists the possible values for this metric and their meaning.

Metric Value Meaning (per SNMP MIB)
1 Other (not one of the following)
2 Unknown
3 Normal
4 Warning
5 Critical
6 Non-Recoverable

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-34 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 15 Minutes

Not Uploaded

>=

4

5

1

Status of Power Supply %PSIndex% in chassis %ChassisIndex% is %value%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.


Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Chassis Index" and "Power Supply Index" objects.

If warning or critical threshold values are currently set for any unique combination of "Chassis Index" and "Power Supply Index" objects, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each unique combination of "Chassis Index" and "Power Supply Index" objects, use the Edit Thresholds page.

Data Source

SNMP MIB object: powerSupplyStatus (1.3.6.1.4.1.674.10892.1.600.12.1.5)

User Action

None.

Processes - Top

The Top Processes metric is a listing of (up to) 20 processes that include 10 processes consuming the largest percentage of memory and 10 processes consuming the most percentage of CPU time. The processes are listed in the order of memory consumption.

Command and Arguments

Represents the command and all its arguments.

Data Source

Host Data Source
Solaris ps command, for example, ps -efo args
HP ps command, for example, ps -efo args
Linux ps command, for example, ps -efo args
HP Tru64 ps command, for example, ps -efo args
IBM AIX ps command, for example, ps -efo args
Windows performance data counters

User Action

None.

CPU Time for Top Processes

Represents the CPU utilization time in seconds.

Data Source

Host Data Source
Solaris ps command, for example, ps -efo time
HP ps command, for example, ps -efo time
Linux ps command, for example, ps -efo time
HP Tru64 ps command, for example, ps -efo time
IBM AIX ps command, for example, ps -efo time
Windows performance data counters

User Action

None.

CPU Utilization for Top Processes (%)

Represents the percentage of CPU time consumed by the process.

Data Source

Host Data Source
Solaris ps command, for example, ps -efo pcpu
HP ps command, for example, ps -efo pmem
Linux ps command, for example, ps -efo pcpu
HP Tru64 ps command, for example, ps -efo pcpu
IBM AIX ps command, for example, ps -efo pcpu
Windows performance data counters

User Action

None.

Memory Utilization for Top Processes (%)

Represents the percentage of memory consumed by the process.

Data Source

Host Data Source
Solaris ps command, for example, ps -efo pmem
HP ps command, for example, ps -efo pmem
Linux ps command, for example, ps -efo pmem
HP Tru64 ps command, for example, ps -efo pmem
IBM AIX ps command, for example, ps -efo pmem
Windows performance data counters

User Action

None.

Physical Memory Utilization (KB)

Represents the number of kilobytes of physical memory being used.

Data Source

Host Data Source
Solaris kernel memory structure (class vminfo)
HP ps command
Linux ps command
HP Tru64 ps command
IBM AIX kernel memory structure (struct vminfo)
Windows Windows API

User Action

None.

Process User ID

Represents the user name that owns the process, that is, the user ID of the process being reported on.

Data Source

Host Data Source
Solaris ps command, for example, ps -efo user
HP ps command
Linux ps command, for example, ps -efo user
HP Tru64 ps command, for example, ps -efo user
IBM AIX ps command, for example, ps -efo user
Windows Windows API

User Action

None.

Virtual Memory Utilization (KB)

Represents the total size of the process in virtual memory in kilobytes (KB).

Data Source

Host Data Source
Solaris ps command, for example, ps -efo vsz
HP ps command, for example, ps -efo vsz
Linux ps command, for example, ps -efo vsz
HP Tru64 ps command, for example, ps -efo vsz
IBM AIX ps command, for example, ps -efo vsz
Windows Windows API

User Action

None.

Process, Inode, File Tables Statistics

The Process, Inode, File Tables Stats metric provides information about the process, inode, and file tables status.

File Table Overflow Occurrences

Represents the number of times the system file table overflowed, that is, the number of times that the OS could not find any available entries in the table in the sampling period chosen to collect the data.

Metric Summary

The OS sar command is used to sample cumulative activity counters maintained by the OS. The data is obtained by sampling system counters once in a five-second interval.

Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris sar command
HP sar command
Linux not available
HP Tru64 table() system call
IBM AIX sar command
Windows not available

User Action

None.

Inode Table Overflow Occurrences

Represents the number of times the inode table overflowed, that is, the number of times the OS could not find any available inode table entries.

Metric Summary

The OS sar command is used to sample cumulative activity counters maintained by the OS. The data is obtained by sampling system counters once in a five-second interval.

Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris sar command
HP sar command
Linux not available
HP Tru64 table() system call
IBM AIX sar command
Windows not available

User Action

None.

Maximum Size of Inode Table

Represents the maximum size of the inode table.

Metric Summary

The OS sar command is used to sample cumulative activity counters maintained by the OS. The data is obtained by sampling system counters once in a five-second interval.

Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris sar command
HP sar command
Linux not available
HP Tru64 table() system call
IBM AIX sar command
Windows not available

User Action

None.

Maximum Size of Process Table

Represents the maximum size of the process table.

Metric Summary

The OS sar command is used to sample cumulative activity counters maintained by the OS. The data is obtained by sampling system counters once in a five-second interval.

Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris sar command
HP sar command
Linux not available
HP Tru64 table() system call
IBM AIX sar command
Windows not available

User Action

None.

Maximum Size of System File Table

Represents the maximum size of the system file table.

Metric Summary

The OS sar command is used to sample cumulative activity counters maintained by the OS. The data is obtained by sampling system counters once in a five-second interval.

Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris sar command
HP sar command
Linux not available
HP Tru64 table() system call
IBM AIX sar command
Windows not available

User Action

None.

Number Of Allocated Disk Quota Entries

Represents the number of allocated disk quota entries.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Minutes

Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris not available
HP not available
Linux sar command
HP Tru64 not available
IBM AIX not available
Windows not available

User Action

None.

Number Of Queued RT Signals

Provides the number of queued RT signals.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Minutes

Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris not available
HP not available
Linux sar command
HP Tru64 not available
IBM AIX not available
Windows not available

User Action

None.

Number Of Super Block Handlers Allocated

Provides the number of allocated super block handlers.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Minutes

Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris not available
HP not available
Linux sar command
HP Tru64 not available
IBM AIX not available
Windows not available

User Action

None.

Number Of Used File Handles

Represents the current size of the system file table.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Minutes

Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris not available
HP not available
Linux sar command
HP Tru64 not available
IBM AIX not available
Windows not available

User Action

None.

Percentage Of Allocated Disk Quota Entries

Represents the Percentage Of Allocated Disk Quota Entries against the maximum number of cached disk quota entries that can be allocated.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-35 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 5 Minutes

After every sample

>

not defined

not defined

6

Allocated Disk Quota Entries %value%%% , has crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.


Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris not available
HP not available
Linux sar command
HP Tru64 not available
IBM AIX not available
Windows not available

User Action

None.

Percentage Of Allocated Super Block Handlers

Represents the Percentage Of Allocated Super Block Handlers against the maximum number of super block handlers that Linux can allocate.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-36 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 5 Minutes

After every sample

>

not defined

not defined

6

Queued RT Signals %value%%% , has crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.


Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris not available
HP not available
Linux sar command
HP Tru64 not available
IBM AIX not available
Windows not available

User Action

None.

Percentage Of Queued RT Signals

Represents the percentage of queued RT signals.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-37 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 5 Minutes

After every sample

>

not defined

not defined

6

Queued RT Signals %value%%% , has crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.


Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris not available
HP not available
Linux sar command
HP Tru64 not available
IBM AIX not available
Windows not available

User Action

None.

Percentage Of Used File Handles

Represents the percentage of used file handles against the maximum number of file handles that the Linux kernel can allocate.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-38 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 5 Minutes

After every sample

>

not defined

not defined

6

Used File Handles %value%%%, has crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.


Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris not available
HP not available
Linux sar command
HP Tru64 not available
IBM AIX not available
Windows not available

User Action

None.

Process Table Overflow Occurrences

Represents the number of times the process table overflowed, that is, the number of times the OS could not find any process table entries in a five-second interval.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Minutes

Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris sar command
HP sar command
Linux not available
HP Tru64 table() system call
IBM AIX sar command
Windows not available

User Action

None.

Size of Inode Table

Represents the current size of the inode table.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Minutes

Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris sar command
HP sar command
Linux sar command
HP Tru64 table() system call
IBM AIX sar command
Windows not available

User Action

None.

Size of Process Table

Represents the current size of the process table.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Minutes

Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris sar command
HP sar command
Linux sar command
HP Tru64 table() system call
IBM AIX sar command
Windows not available

Processors

The Processors metric monitors the state of each CPU in the host.

This metric is available only on Dell Poweredge Linux Systems.

Family

Represents the family of the Dell processor devices.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

SNMP MIB object: processorDeviceFamily (1.3.6.1.4.1.674.10892.1.1100.30.1.10)

User Action

None.

Manufacture

Represents the name of the manufacturer of the Dell processor.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

SNMP MIB object: processorDeviceManufacturerName (1.3.6.1.4.1.674.10892.1.1100.30.1.8)

User Action

None.

Processor Status

Represents the status of the Dell processor device.

This metric is available only on Dell Poweredge Linux Systems.

The following table lists the possible values for this metric and their meaning.

Metric Value Meaning (per SNMP MIB)
1 Other (not one of the following)
2 Unknown
3 Normal
4 Warning
5 Critical
6 Non-Recoverable

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-39 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 15 Minutes

Not Uploaded

>=

4

5

1

Status of Processor %ProcessorIndex% in chassis %ChassisIndex% is %value%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.


Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Chassis Index" and "Processor Index" objects.

If warning or critical threshold values are currently set for any unique combination of "Chassis Index" and "Processor Index" objects, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each unique combination of "Chassis Index" and "Processor Index" objects, use the Edit Thresholds page.

Data Source

SNMP MIB object: processorDeviceStatus (1.3.6.1.4.1.674.10892.1.1100.30.1.5)

User Action

None.

Speed (MHz)

Represents the current speed of the Dell processor device in MegaHertz (MHz). A value of zero indicates the speed is unknown.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

SNMP MIB object: processorDeviceCurrentSpeed (1.3.6.1.4.1.674.10892.1.1100.30.1.12)

User Action

None.

Version

Represents the version of the Dell processor.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

SNMP MIB object: processorDeviceVersionName (1.3.6.1.4.1.674.10892.1.1100.30.1.16)

User Action

None.

Program Resource Utilization

The Program Resource Utilization metric provides flexible resource monitoring functionality. The operator must specify the criteria for the programs to be monitored by specifying key value specific thresholds. Values for the key value columns {program name, owner} define the unique criteria to be monitored for resource utilization in the system.

By default, no programs will be tracked by this metric. Key Values entered as part of a key value specific threshold setting define the criteria for monitoring and tracking.

List of PIDs

This metric is only available on Solaris.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Minutes

Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris ps command
HP ps command
Linux ps command
HP Tru64 ps command
IBM AIX ps command
Windows ps command

User Action

None.

Program's Max CPU Time Accumulated (Minutes)

Represents the maximum CPU time accumulated by the most active process matching the {program name, owner} key value criteria.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-40 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

3

%prog_max_cpu_time_pid% process running program %prog_name% has accumulated %prog_max_cpu_time% minutes of cpu time. This duration crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.


Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Program Name" and "Owner" objects.

If warning or critical threshold values are currently set for any unique combination of "Program Name" and "Owner" objects, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each unique combination of "Program Name" and "Owner" objects, use the Edit Thresholds page.

Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris ps command
HP ps command
Linux ps command
HP Tru64 ps command
IBM AIX ps command
Windows not available

User Action

None.

Program's Max CPU Utilization (%)

Represents the maximum percentage of CPU utilized by a single process matching the {program name, owner} key value criteria since last scan.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-41 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

3

Process %prog_max_cpu_util_pid% matched by the program name ''%prog_name%'' and owner ''%owner%'' is utilizing %prog_max_cpu_util%%% of the cpu. It has crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.


Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Program Name" and "Owner" objects.

If warning or critical threshold values are currently set for any unique combination of "Program Name" and "Owner" objects, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each unique combination of "Program Name" and "Owner" objects, use the Edit Thresholds page.

Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris ps command
HP ps command
Linux ps command
HP Tru64 ps command
IBM AIX ps command
Windows not available

User Action

None.

Program's Max Process Count

Fetches the current number of processes matching the {program name, owner} key value criteria. It can be used for setting warning or critical thresholds to monitor for maximum number of processes that a given {program name, owner} key value criteria crosses.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-42 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

3

%prog_max_process_count% processes are matched by the program name ''%prog_name%'' and owner ''%owner%''. They have crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.


Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Program Name" and "Owner" objects.

If warning or critical threshold values are currently set for any unique combination of "Program Name" and "Owner" objects, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each unique combination of "Program Name" and "Owner" objects, use the Edit Thresholds page.

Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris ps command
HP ps command
Linux ps command
HP Tru64 ps command
IBM AIX ps command
Windows not available

User Action

None.

Program's Max Resident Memory (MB)

Represents the maximum resident memory occupied by a single process matching the {program name, owner} key value criteria. It can be used for setting warning or critical thresholds to monitor for maximum value a given {program name, owner} key value criteria crosses.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-43 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

3

Process %prog_max_rss_pid% matched by the program name ''%prog_name%'' and owner ''%owner%'' is utilizing %prog_max_rss% (MB) of resident memory. It has crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.


Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Program Name" and "Owner" objects.

If warning or critical threshold values are currently set for any unique combination of "Program Name" and "Owner" objects, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each unique combination of "Program Name" and "Owner" objects, use the Edit Thresholds page.

Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris ps command
HP ps command
Linux ps command
HP Tru64 ps command
IBM AIX ps command
Windows not available

User Action

None.

Program's Min Process Count

Fetches the current number of processes matching the {program name, owner} key value criteria. It can be used for setting warning or critical thresholds to monitor for minimum number of processes that a given {program name, owner} key value criteria should never go under.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-44 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 5 Minutes

After Every Sample

<

Not Defined

Not Defined

3

%prog_min_process_count% processes are matched by the program name ''%prog_name%'' and owner ''%owner%''. They have fallen below warning (%warning_threshold%) or critical (%critical_threshold%) threshold.


Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Program Name" and "Owner" objects.

If warning or critical threshold values are currently set for any unique combination of "Program Name" and "Owner" objects, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each unique combination of "Program Name" and "Owner" objects, use the Edit Thresholds page.

Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris ps command
HP ps command
Linux ps command
HP Tru64 ps command
IBM AIX ps command
Windows not available

User Action

None.

Program's Total CPU Time Accumulated (Minutes)

Represents the total CPU time accumulated by all active process matching the {program name, owner} key value criteria.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-45 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

3

%prog_max_process_count% processes matched by the program name ''%prog_name%'' and owner ''%owner%'' have accumulated %prog_total_cpu_time% minutes of cpu time. This duration has crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.


Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Program Name" and "Owner" objects.

If warning or critical threshold values are currently set for any unique combination of "Program Name" and "Owner" objects, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each unique combination of "Program Name" and "Owner" objects, use the Edit Thresholds page.

Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris ps command
HP ps command
Linux ps command
HP Tru64 ps command
IBM AIX ps command
Windows not available

User Action

None.

Program's Total CPU Utilization (%)

Represents the percentage of CPU time utilized by all active process matching the {program name, owner} key value criteria since last collection.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-46 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

3

%prog_max_process_count% processes matched by the program name ''%prog_name%'' and owner ''%owner%'' are utilizing %prog_total_cpu_util%%% of the cpu. It has crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.


Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Program Name" and "Owner" objects.

If warning or critical threshold values are currently set for any unique combination of "Program Name" and "Owner" objects, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each unique combination of "Program Name" and "Owner" objects, use the Edit Thresholds page.

Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris ps command
HP ps command
Linux ps command
HP Tru64 ps command
IBM AIX ps command
Windows not available

User Action

None.

Remote Access Card

The Remote Access Card metric monitors the status of the Remote Access Card.

This metric is available only on Dell Poweredge Linux Systems.

DHCP Settings

Determines whether the dynamic host configuration protocol (DHCP) was used to obtain the network interface card (NIC) information.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

SNMP MIB object: remoteAccessNICCurrentInfoFromDHCP (1.3.6.1.4.1.674.10892.1.1700.10.1.33)

User Action

None.

Gateway Address

Represents the IP address for the gateway currently being used by the onboard network interface card (NIC) provided by the remote access (RAC) hardware.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

SNMP MIB object: remoteAccessNICCurrentGatewayAddress (1.3.6.1.4.1.674.10892.1.1700.10.1.32)

User Action

None.

IP Address

Provides the internet protocol (IP) address currently being used by the onboard network interface card (NIC) provided by the remote access (RAC) hardware.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

SNMP MIB object: remoteAccessNICCurrentIPAddress (1.3.6.1.4.1.674.10892.1.1700.10.1.30)

User Action

None.

LAN Settings

Represents the local area network (LAN) settings of the remote access hardware.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

SNMP MIB object: remoteAccessLANSettings (1.3.6.1.4.1.674.10892.1.1700.10.1.15)

User Action

None.

Network Mask Address

Represents the subnet mask currently being used by the onboard network interface card (NIC) provided by the remote access (RAC) hardware.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

SNMP MIB object: remoteAccessLANSettings (1.3.6.1.4.1.674.10892.1.1700.10.1.15)

User Action

None.

Product Name

Represents the name of the product providing the remote access (RAC) functionality.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

SNMP MIB object: remoteAccessProductInfoName (1.3.6.1.4.1.674.10892.1.1700.10.1.7)

User Action

None.

Remote Access Card State

Represents the state of the remote access (RAC) hardware.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

SNMP MIB object: remoteAccessStateSettings (1.3.6.1.4.1.674.10892.1.1700.10.1.5)

User Action

None.

Remote Access Card Status

Represents the status of the remote access (RAC) hardware.

This metric is available only on Dell Poweredge Linux Systems.

The following table lists the possible values for this metric and their meaning.

Metric Value Meaning (per SNMP MIB)
1 Other (not one of the following)
2 Unknown
3 Normal
4 Warning
5 Critical
6 Non-Recoverable

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-47 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 15 Minutes

Not Uploaded

>=

4

5

1

Status of Remote Access Card is %value%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.


Data Source

SNMP MIB object: remoteAccessStatus (1.3.6.1.4.1.674.10892.1.1700.10.1.6)

User Action

None.

Version

Represents the version of the product providing the remote access (RAC) functionality.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

SNMP MIB object: remoteAccessVersionInfoName (1.3.6.1.4.1.674.10892.1.1700.10.1.9)

User Action

None.

Response

This metric provides the status of the host, that is, whether it is up or down.

Status

The metric indicates whether the host is reachable or not. A host could be unreachable due to various reasons. The network is down or the Management Agent on the host is down (which could be because the host itself is shutdown).

Storage Summary Metrics

The Storage Summary metrics collectively represent the summary of storage data on a host target. These metrics are derived from the various metrics collected and uploaded into the Oracle Management Repository by the Management Agent. They are computed every time the Management Agent populates the Management Repository with storage data. This collection is also triggered automatically whenever the user manually refreshes the host storage data from the Storage Details page.

ASM Storage Allocated (GB)

Represents the total storage allocated to Oracle databases from Automatic Storage Management (ASM) instances on the host.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
3.0 and higher Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

ASM Storage Metric Collection Errors

Represents the number of metric collection errors attributed to the storage related metrics of the Automatic Storage Management (ASM) targets on the host.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
3.0 and higher Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

ASM Storage Overhead (GB)

Represents the storage overhead of Automatic Storage Management (ASM) targets on the host.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
3.0 and higher Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

ASM Storage Unallocated (GB)

Represents the storage available in Automatic Storage Management (ASM) targets on the host for allocating to databases.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
3.0 and higher Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

Databases Storage Free (GB)

Represents the total free storage available in the databases on the host.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
3.0 and higher Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

Databases Storage Metric Collection Errors

Represents the metric collection errors of storage related metrics of databases on the host.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
3.0 and higher Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

Databases Storage Used (GB)

Represents the total free storage available in the databases on the host.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
3.0 and higher Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

Disk Storage Allocated (GB)

Represents the storage allocated from the total disk storage available on the host.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
3.0 and higher Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

Disk Storage Unallocated (GB)

Represents the storage that is available for allocation in disks on the host.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
3.0 and higher Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

Host Storage Metric Collection Errors

Represents the total number of storage related metric collection errors of the host target.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
3.0 and higher Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

Hosts Summarized

The possible values for this metric are:

  • 1 (one) if this host storage was computed successfully (sometimes with partial errors)

  • 0 (zero) if the storage computation did not proceed at all due to some reasons (for example, failure to collect critical storage metric data).

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
3.0 and higher Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

Local File Systems Storage Free (GB)

The total free storage in all distinct local file systems on the host.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
3.0 and higher Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

Local File Systems Storage Used (GB)

The total used space in all distinct local file systems on the host.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
3.0 and higher Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

Number of ASM Instances Summarized

Represents the total number of Automatic Storage Management (ASM) instances, the storage data of which was used in computing storage summary of this host.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
3.0 and higher Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

Number of Databases Summarized

Represents the total number of databases, the storage data of which was used in computing storage summary of this host.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
3.0 and higher Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

Other Mapping Errors

Represents the storage metric mapping issues on the host excluding the unmonitored server mapping errors.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
3.0 and higher Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

Total Number of ASM Instances

Represents the total number of Automatic Storage Management (ASM) instances on the host.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
3.0 and higher Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

Total Number of Databases

Represents the total number of databases on the host.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
3.0 and higher Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

Total Storage Allocated (GB)

Represents the total storage allocated from the host-visible storage available on the host.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
3.0 and higher Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

Total Storage Free (GB)

Represents the free storage available from the total allocated storage on the host.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
3.0 and higher Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

Total Storage Overhead (GB)

Represents the overhead associated with storage on the host.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
3.0 and higher Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

Total Storage Unallocated (GB)

Represents the total unallocated storage on the host.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
3.0 and higher Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

Total Storage Used (GB)

Represents the total storage used in the file systems and databases on the host.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
3.0 and higher Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

Unmonitored NFS Server Mapping Errors

Represents the total number of storage mapping issues that result from unmonitored Network File Systems (NFS) servers.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
3.0 and higher Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

Volumes Storage Allocated (GB)

Represents the total storage allocated from the volumes available on the host.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
3.0 and higher Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

Volumes Storage Overhead (GB)

Represents the storage overhead in the volumes on the host.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
3.0 and higher Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

Volumes Storage Unallocated (GB)

Represents the storage available for allocation in the volumes on the host.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
3.0 and higher Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

Writeable NFS Storage Free (GB)

Represents the total free space available in all distinct writeable NFS mounts on the host.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
3.0 and higher Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

Writeable NFS Storage Used (GB)

Represents the storage used in all writeable NFS mounts on the host.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
3.0 and higher Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

Storage Support

This metric is used to decide if the OS being monitored is supported or not. Its also used to inform the user if the number of Storage entities (Disks / FileSystems /Volumes) being monitored is within the applicable limits so as not to affect the performance of the Management Agent.

Supported

The metric is used to enable/disable the collection, depending on the OS supported or the number of storage entities being monitored.

The operating systems supported are Linux, Solaris, AIX, and HPUX.

The maximum number of storage entities monitored is set to 100 in the configuration file located in EMAgent/sysman/emd/emagent_storage.config. The Disks/Files/Volumes to be monitored can be added in the configuration file. If the storage entities are more than 100, the response time of the Management Agent increases.

Data Source

Not available

User Action

Edit the configuration file (emagent/sysman/emd/emagent_storage.config), and add the Disks, Filesystems, and Volumes to be monitored.

Swap Area Status

The Swap Area Status metric provides the status of the swap memory on the system.

Swap Free

Represents the number of 1K blocks in swap area that is not allocated.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-48 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 24 hours

After Every Sample

<

Not Defined

Not Defined

1

Swap Free Size %value% has gone below the warning (%warning_threshold%) or critical (%critical_threshold%) threshold.


Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "Swap File" object.If warning or critical threshold values are currently set for any "Swap File" object, those thresholds can be viewed on the Metric Detail page for this metric.To specify or change warning or critical threshold values for each "Swap File" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris swap
HP swapinfo
Linux /proc/swaps
HP Tru64 swapon
IBM AIX lsps
Windows not available

User Action

Check the swap usage using the UNIX top command or the Solaris swap -l command. Additional swap can be added to an existing file system by creating a swap file and then adding the file to the system swap pool. (See documentation for your UNIX OS). If swap is mounted on /tmp, space can be freed by removing any junk files in /tmp. If it is not possible to add file system swap or free up enough space, additional swap will have to be added by adding a raw disk partition to the swap pool. See UNIX documentation for procedures.

Swap Size

Represents the size of the swap file.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 24 Hours

Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris swap
HP swapinfo
Linux /proc/swaps
HP Tru64 swapon
IBM AIX lsps
Windows not available

User Action

None.

Switch/Swap Activity

The Switch/Swap Activity metric displays the metric reports on the system switching and swapping activity.

Process Context Switches (per second)

Number of process context switches per second

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-49 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 5 minutes

After Every Sample

>

Not Defined

Not Defined

6

Process Context Switches (per second) %value% , has crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.


Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris sar command
HP sar command
Linux not available
HP Tru64 not available
IBM AIX sar command
Windows not available

The OS sar command is used to sample cumulative activity counters maintained by the OS. Also, the data is obtained by sampling system counters once in a five-second interval. The results are essentially the number of processes swapped in over this five-second period divided by five.

User Action

None.

Swapins Transfers (per second)

Represents the number of 512-byte units transferred for swapins per second.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-50 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 5 minutes

After Every Sample

>

Not Defined

Not Defined

6

Swapins Transfers (per second) %value% , has crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.


Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris sar command
HP sar command
Linux sar command
HP Tru64 not available
IBM AIX sar command
Windows not available

The OS sar command is used to sample cumulative activity counters maintained by the OS. Also, the data is obtained by sampling system counters once in a five-second interval. The results are essentially the number of processes swapped in over this five-second period divided by five.

User Action

None.

Swapout Transfers (per second)

Represents the number of 512-byte units transferred for swapouts per second.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-51 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 5 minutes

After Every Sample

>

Not Defined

Not Defined

6

Swapins Transfers (per second) %value% , has crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.


Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris sar command
HP sar command
Linux sar command
HP Tru64 not available
IBM AIX sar command
Windows not available

The OS sar command is used to sample cumulative activity counters maintained by the OS. Also, the data is obtained by sampling system counters once in a five-second interval. The results are essentially the number of processes swapped in over this five-second period divided by five.

User Action

None.

System Swapins (per second)

Represents the number of process swapins per second.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-52 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 5 minutes

After Every Sample

>

Not Defined

Not Defined

6

System Swapins (per second) %value% , has crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.


Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris sar command
HP sar command
Linux sar command
HP Tru64 not available
IBM AIX sar command
Windows not available

The OS sar command is used to sample cumulative activity counters maintained by the OS. Also, the data is obtained by sampling system counters once in a five-second interval. The results are essentially the number of processes swapped in over this five-second period divided by five.

User Action

None.

System Swapouts (per second)

Represents the number of process swapouts per second.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-53 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 5 minutes

After Every Sample

>

Not Defined

Not Defined

6

System Swapouts (per second) %value% , has crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.


Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris sar command
HP sar command
Linux sar command
HP Tru64 not available
IBM AIX sar command
Windows not available

The OS sar command is used to sample cumulative activity counters maintained by the OS. Also, the data is obtained by sampling system counters once in a five-second interval. The results are essentially the number of processes swapped in over this five-second period divided by five.

User Action

None.

System BIOS

The System BIOS (Basic Input/Output System) metric monitors the BIOS status for Dell Poweredge Linux systems.

Manufacturer

Represents the manufacturer's name of the System BIOS (Basic Input/Output System). This metric is available only on Dell Poweredge Linux Systems.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

SNMP MIB object: systemBIOSManufacturerName (1.3.6.1.4.1.674.10892.1.300.50.1.11)

User Action

None.

Size

Represents the image size of the System BIOS (Basic Input/Output System) in kilobytes. A value of zero indicates that the size is unknown. This metric is available only on Dell Poweredge Linux Systems.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

SNMP MIB object: systemBIOSSize (1.3.6.1.4.1.674.10892.1.300.50.1.6)

User Action

None.

System BIOS Status

Represents the status of the System BIOS (Basic Input/Output System) in this chassis.

This metric is available only on Dell Poweredge Linux Systems.

The following table lists the possible values for this metric and their meaning.

Metric Value Meaning (per SNMP MIB)
1 Other (not one of the following)
2 Unknown
3 Normal
4 Warning
5 Critical
6 Non-Recoverable

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-54 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 15 Minutes

Not Uploaded

>=

4

5

1

Status of BIOS %BiosIndex% in chassis %ChassisIndex% is %value%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.


Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Chassis Index" and "System BIOS Index" objects.

If warning or critical threshold values are currently set for any unique combination of "Chassis Index" and "System BIOS Index" objects, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each unique combination of "Chassis Index" and "System BIOS Index" objects, use the Edit Thresholds page.

Data Source

SNMP MIB object: systemBIOSStatus (1.3.6.1.4.1.674.10892.1.300.50.1.5)

User Action

None.

Version

Represents the version name of the System BIOS (Basic Input/Output System). This metric is available only on Dell Poweredge Linux Systems.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

SNMP MIB object: systemBIOSVersionName (1.3.6.1.4.1.674.10892.1.300.50.1.8)

User Action

None.

System Calls

The System Calls metric provides statistics about the system calls made over a five-second interval.

Characters Transferred by Read System Calls (per second)

Represents the number of characters transferred by read system calls (block devices only) per second.

Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris sar command
HP sar command
Linux not available
HP Tru64 table() system call
IBM AIX sar command
Windows not available

The OS sar command is used to sample cumulative activity counters maintained by the OS. Also, the data is obtained by sampling system counters once in a five-second interval. The results are essentially the number of processes swapped in over this five-second period divided by five.

User Action

None.

Characters Transferred by Write System Calls (per second)

Represents the number of characters transferred by write system calls (block devices only) per second.

Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris sar command
HP sar command
Linux not available
HP Tru64 table() system call
IBM AIX sar command
Windows not available

The OS sar command is used to sample cumulative activity counters maintained by the OS. Also, the data is obtained by sampling system counters once in a five-second interval. The results are essentially the number of processes swapped in over this five-second period divided by five.

User Action

None.

exec() System Calls (per second)

Represents the number of exec() system calls made per second.

Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris sar command
HP sar command
Linux not available
HP Tru64 table() system call
IBM AIX sar command
Windows not available

The OS sar command is used to sample cumulative activity counters maintained by the OS. Also, the data is obtained by sampling system counters once in a five-second interval. The results are essentially the number of processes swapped in over this five-second period divided by five.

User Action

None.

fork() System Calls (per second)

Represents the number of fork() system calls made per second.

Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris sar command
HP sar command
Linux not available
HP Tru64 table() system call
IBM AIX sar command
Windows not available

The OS sar command is used to sample cumulative activity counters maintained by the OS. Also, the data is obtained by sampling system counters once in a five-second interval. The results are essentially the number of processes swapped in over this five-second period divided by five.

User Action

None.

read() System Calls (per second)

Represents the number of read() system calls made per second.

Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris sar command
HP sar command
Linux not available
HP Tru64 table() system call
IBM AIX sar command
Windows not available

The OS sar command is used to sample cumulative activity counters maintained by the OS. Also, the data is obtained by sampling system counters once in a five-second interval. The results are essentially the number of processes swapped in over this five-second period divided by five.

User Action

None.

System Calls (per second)

Represents the number of system calls made per second. This includes system calls of all types.

Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris sar command
HP sar command
Linux not available
HP Tru64 table() system call
IBM AIX sar command
Windows not available

The OS sar command is used to sample cumulative activity counters maintained by the OS. Also, the data is obtained by sampling system counters once in a five-second interval. The results are essentially the number of processes swapped in over this five-second period divided by five.

User Action

None.

write() System Calls (per second)

Represents the number of write() system calls made per second.

Data Source

The data sources for the metrics in this category include the following:

Host Data Source
Solaris sar command
HP sar command
Linux not available
HP Tru64 table() system call
IBM AIX sar command
Windows not available

The OS sar command is used to sample cumulative activity counters maintained by the OS. Also, the data is obtained by sampling system counters once in a five-second interval. The results are essentially the number of processes swapped in over this five-second period divided by five.

User Action

None.

Temperature

The Temperature metric monitors the hotness or coldness of the temperature probe.

This metric is available only on Dell Poweredge Linux Systems.

Current Temperature

Represents the current reading of the temperature probe. The value is representing temperature in tenths of degrees Centigrade.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

SNMP MIB object: temperatureProbeReading (1.3.6.1.4.1.674.10892.1.700.20.1.6)

User Action

An abnormally high value indicates that the system is doing a lot of work and getting overheated. The system could be overheated due to inadequate cooling by the Fan.

Location

Provides a description of the location name of the temperature probe. Examples of values are: "CPU Temp" and "System Temp".

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

SNMP MIB object: temperatureProbeLocationName (1.3.6.1.4.1.674.10892.1.700.20.1.8)

User Action

None.

Temperature Probe Status

Represents the status of the temperature probe.

This metric is available only on Dell Poweredge Linux Systems.

The following table lists the possible values for this metric and their meaning.

Metric Value Meaning (per SNMP MIB)
1 Other (not one of the following)
2 Unknown
3 Normal
4 Warning
5 Critical
6 Non-Recoverable

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-55 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 15 Minutes

Not Uploaded

>=

4

5

1

Temperature at probe %ProbeIndex% in chassis %ChassisIndex% is %TemperatureReading% (C). Status is %value%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.


Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Chassis Index" and "Temperature Probe Index" objects.

If warning or critical threshold values are currently set for any unique combination of "Chassis Index" and "Temperature Probe Index" objects, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each unique combination of "Chassis Index" and "Temperature Probe Index" objects, use the Edit Thresholds page.

Data Source

SNMP MIB object: temperatureProbeStatus (1.3.6.1.4.1.674.10892.1.700.20.1.5)

User Action

This describes the status of the temperature probe. A failed probe needs to be physically examined or replaced.

TTY Activity

This metric reports tty device activity.

Incoming Character Interrupts (per second)

Represents the number of received incoming character interrupts per second.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Seconds

Data Source

Host Data Source
Solaris sar command
HP sar command
Linux not available
HP Tru64 table() system call
IBM AIX sar command
Windows not available

The OS sar command is used to sample cumulative activity counters maintained by the OS. The data is obtained by sampling system counters once in a five-second interval.

User Action

None.

Input Characters Processed by canon()

Represents the input characters processed by canon() per second.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Seconds

Data Source

Host Data Source
Solaris sar command
HP sar command
Linux not available
HP Tru64 table() system call
IBM AIX sar command
Windows not available

The OS sar command is used to sample cumulative activity counters maintained by the OS. The data is obtained by sampling system counters once in a five-second interval.

User Action

None.

Modem Interrupt Rate (per second)

Represents the modem interrupt rate.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Seconds

Data Source

Host Data Source
Solaris sar command
HP sar command
Linux not available
HP Tru64 table() system call
IBM AIX sar command
Windows not available

The OS sar command is used to sample cumulative activity counters maintained by the OS. The data is obtained by sampling system counters once in a five-second interval.

User Action

None.

Outgoing Character Interrupts (per second)

Represents the number of transmit outgoing character interrupts per second.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Seconds

Data Source

Host Data Source
Solaris sar command
HP sar command
Linux not available
HP Tru64 table() system call
IBM AIX sar command
Windows not available

The OS sar command is used to sample cumulative activity counters maintained by the OS. The data is obtained by sampling system counters once in a five-second interval.

User Action

None.

TTY Output Characters (per second)

Represents the number of output characters per second.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Seconds

Data Source

Host Data Source
Solaris sar command
HP sar command
Linux not available
HP Tru64 table() system call
IBM AIX sar command
Windows not available

The OS sar command is used to sample cumulative activity counters maintained by the OS. The data is obtained by sampling system counters once in a five-second interval.

User Action

None.

TTY Raw Input (chars/s)

Represents the raw input characters per second.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Seconds

Data Source

Host Data Source
Solaris sar command
HP sar command
Linux not available
HP Tru64 table() system call
IBM AIX sar command
Windows not available

The OS sar command is used to sample cumulative activity counters maintained by the OS. The data is obtained by sampling system counters once in a five-second interval.

User Action

None.

User Defined Metrics

The UDM metric allows you to execute your own scripts. The data returned by these scripts can be compared against thresholds and generate severity alerts similar to alerts in predefined metrics. UDM is similar to the Oracle9i Management Agent's UDE functionality.

User Defined Numeric Metric

Contains a value if the value type is NUMBER. Otherwise, the value is "", if the value is STRING.

Data Source

User defined script.

User Action

None.

User Defined String Metric

Contains a value if the value type is STRING. Otherwise, the value is "", if the value is NUMBER.

Data Source

User defined script.

User Action

None.

Users

The Users metric provides information about the users currently on the system being monitored.

Number of Logons

Represents the number of times a user with a certain user name is logged on to the host target.

Data Source

For Solaris, HP, Linux, HP Tru64, and IBM AIX, the number of times a user is logged on is obtained from the OS w command.

For Windows, the source of information is Windows API.

User Action

None.

Windows Events Log

The purpose of this metric is to collect those entries from all available Windows NT event log files whose type is either Error or Warning. A critical or a warning alert is raised only for System and Security Event log file entries.

Note: Since log files continue to grow, this metric outputs log events which had been written to the log file after the last collection time, that is, only those records are written out whose timeGenerated (time when the event was generated) is after the last collection time until the last record of the log file. If this metric is collected for the first time, only the events generated on the current date are outputted.

This metric is available only on Windows.

Category

List of all categories for the events matching Log Name, Source, and Event ID defined for the monitored object. The actual category of the event can be found in the Windows event log message.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
3.0 and higher Every 15 Minutes

Data Source

Windows Management Instrumentation (WMI)

User Action

None.

Date-Time

This is the time at which point the metric scanned through the event logs. This metric is available only on Windows.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
3.0 and higher Every 15 Minutes

Data Source

Windows Management Instrumentation (WMI)

User Action

None.

Windows Event Log Message

This metric is a digest of all the events that match the Log Name, Source, and Event ID specified for the monitored object. After the above filtering is done, grouping of these events is done on Log Name, Source, Event ID, Category, and User to get the count of error events and warning events. The column has the details of the events in the following format:

[LogName: Source:Event ID:Category:User : :]

Example: [Application:Symantec AntiVirus:2: : :error=2:] [Application:Symantec AntiVirus:3: : ::warning =1 ]

To get the exact message about the events that satisfied the criteria set on the monitored object, the Event viewer provided by Microsoft Windows must be used.

This metric is available only on Windows.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
3.0 and higher Every 15 Minutes

Data Source

Windows Management Instrumentation (WMI)

User Action

None.

Event ID

This is the Perl pattern to match the string defined for the Event ID in the monitored objects. The actual Event ID of the event can be found in the Windows event log message. This metric is available only on Windows.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
3.0 and higher Every 15 Minutes

Data Source

Windows Management Instrumentation (WMI)

User Action

None.

Windows Event Severity

The seriousness of the event. Possible values are: Warning and Error.

This metric is available only on Windows.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-56 Metric Summary Table

Target Version Key Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

logfile: "system"

Every 15 Minutes

After Every Sample

=

warning

error

1*

X1User[%user%]:Category[%categorystring%]:Description[%message%]


* Once an alert is triggered for this metric, it must be manually cleared.

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Log Name", "Source", and "Event ID" objects.

If warning or critical threshold values are currently set for any unique combination of "Log Name", "Source", and "Event ID" objects, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each unique combination of "Log Name", "Source", and "Event ID" objects, use the Edit Thresholds page.

Data Source

WMI Operating System Classes

User Action

None.

Zombie Processes

The Zombie Processes metric monitors the orphaned processes in the different variations of UNIX systems.

% of Processes in Zombie State

Represents the percentage of all processes running on the system that are currently in zombie state.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The data sources for this metric include the following:

Host Data Source
Solaris ps command
HP ps command
Linux ps command
HP Tru64 ps command
IBM AIX ps command
Windows ps command

User Action

None.

Processes in Zombie State (%)

Represents the percentage of all processes running on the system that are currently in zombie state.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-57 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 15 Minutes

After Every 60 Samples

>

35

50

1

%value%%% of all processes are in zombie state, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.


Data Source

The data sources for this metric include the following:

Host Data Source
Solaris ps command
HP ps command
Linux ps command
HP Tru64 not available
IBM AIX not available
Windows not available

User Action

None.

Infiniband Network

These metrics provide details on the throughput performance of each link (port-to-port connection) in the network, an aggregation of performance for Switch-to-Node and Switch-to-Switch link types, and total throughput performance of the network.

Linked Throughput

This is the throughput performance of each link (switch port to node/switch port connection) in the network

Switch GUID

This is the globally unique identifier of the switch in this link (the first switch, if both end points are switches).

Metric Summary for Database Control

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Minutes

Data Source

iblinkinfo.pl, perfquery

User Action

No user action is required.

Port Number

This is the port number of the switch in this link (the first switch, if both end points are switches).

Metric Summary for Database Control

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Minutes

Data Source

iblinkinfo.pl, perfquery

User Action

No user action is required.

Link Type

This is either Switch-to-Switch or Switch-to-Node

Metric Summary for Database Control

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Minutes

Data Source

iblinkinfo.pl, perfquery

User Action

No user action is required.

Throughput

This is the number of GB sent and received over this link in the last collection interval, divided by the duration of the last collection interval (Gbps).

Metric Summary for Database Control

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Minutes

Data Source

iblinkinfo.pl, perfquery

User Action

No user action is required.

Infiniband Switch

These metrics describe the performance of each port of the switch and the aggregation of performance for Switch-to-Node and Switch-to-Switch link types. They also define whether a switch is a subnet manager for the network or not. Switch statistics are also covered.

Port Performance

Performance of each port of the switch

Port Number

This is the port number of this switch in this link

Metric Summary for Database Control

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

No user action is required.

Connected to GUID

This is the globally unique identifier to which this port is connected

Metric Summary for Database Control

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

No user action is required.

Connected to Type

This is the type of the entity to which this port is connected (for example, compute node, cell or switch)

Metric Summary for Database Control

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

No user action is required.

Connected to GUID Type

f the port is connected to a switch, the GUID in "Connected to GUID" column is the switch GUID, else if the port is connected to a node, the GUID is the port GUID of the port on the node.

Metric Summary for Database Control

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

No user action is required.

Connected to Port Number

This is the port number of the entity to which this switch port is connected.

Metric Summary for Database Control

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

No user action is required.

Supported Speed

This is the supported speed of this link (Gbps).

Metric Summary for Database Control

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

No user action is required.

Supported Width

This is the supported width of this link (for example, 1X or 4X)

Metric Summary for Database Control

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

No user action is required.

Enabled Speed

This is the enabled speed of this link (Gbps).

Metric Summary for Database Control

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

No user action is required.

Enabled Width

This is the enabled width of this link (for example, 1X or 4X)

Metric Summary for Database Control

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

No user action is required.

Active Speed

This is the active speed of this link (Gbps)

Metric Summary for Database Control

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

No user action is required.

Active Width

This is the active width of this link (for example, 1X or 4X)

Metric Summary for Database Control

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

No user action is required.

Link Degraded

This is the ink speed or width is less than the enabled speed or width respectively, the link is operating in degraded mode

Metric Summary for Database Control

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

By default, warning alert is issued if the link becomes degraded. User needs to evaluate the impact of this link on the performance of the database machine, and take appropriate steps to restore the link to normal speed/width.

Link State

This shows whether the link is up or down.

Metric Summary for Database Control

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

No user action is required.

Physical Link State

This shows whether the physical link is up or down.

Metric Summary for Database Control

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

No user action is required.

Throughput

This shows the number of GB sent and received over this link in the last collection interval, divided by the duration of the last collection interval (Gbps)

Metric Summary for Database Control

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

No user action is required.

Symbol Errors

This shows the number of errors of this type in the last collection interval.

Metric Summary for Database Control

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

No user action is required.

Link Recovers

This shows the number of errors of this type in the last collection interval

Metric Summary for Database Control

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

No user action is required.

Link Downed

This shows the number of errors of this type in the last collection interval

Metric Summary for Database Control

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

No user action is required.

Received Errors

This shows the number of errors of this type in the last collection interval

Metric Summary for Database Control

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

No user action is required.

Received Remote Physical Errors

This shows the number of errors of this type in the last collection interval

Metric Summary for Database Control

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

No user action is required.

Received Switch Relay Errors

This shows the number of errors of this type in the last collection interval

Metric Summary for Database Control

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

No user action is required.

Transmitted Packets Discarded

This shows the number of errors of this type in the last collection interval

Metric Summary for Database Control

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

No user action is required.

Transmitted Packets Constraint Errors

This shows the number of errors of this type in the last collection interval

Metric Summary for Database Control

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

No user action is required.

Received Constraint Errors

This shows the number of errors of this type in the last collection interval

Metric Summary for Database Control

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

No user action is required.

Link Integrity Errors

This shows the number of errors of this type in the last collection interval

Metric Summary for Database Control

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

No user action is required.

Excess Buffer Overrun Errors

This shows the number of errors of this type in the last collection interval

Metric Summary for Database Control

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

No user action is required.

VL15 Dropped Errors

This shows the number of errors of this type in the last collection interval

Metric Summary for Database Control

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

No user action is required.

Total Errors

This is the total number of errors in the last collection interval

Metric Summary for Database Control

The following table shows how often the metric's value is collected.

Target Version Collection Frequency
All Versions Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

Set some threshold above which the number of errors is deemed high enough to merit scrutiny of potential impact on throughput performance