Oracle® Enterprise Manager Oracle Database and Database-Related Metric Reference Manual 12c Release 1 (12.1.0.2.0) Part Number E25160-03 |
|
|
PDF · Mobi · ePub |
This section describes the metrics used to monitor keyboard, video or visual display unit, mouse (KVM) targets The Avocent MergePoint Unity Switch plug-in enables Enterprise Manager Grid Control to monitor KVM targets. The plug-in provides the status of the KVM and event occurrences, such as Factory Defaults Set, Fan Failure, Aggregated Target Device Status, Power Supply Failure, Power Supply Restored, Reboot Started, Temperature Out of Range on the KVM target.
This section provides details of the aggregated target device status changed metrics.
Status 0 indicates that the aggregate server status has changed.
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 |
Collected through SNMP push.
No user action is required.
This the encoded value of the aggregate server status upon change.
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 |
Collected through SNMP push.
No user action is required.
This section provides details on the factory defaults set metrics.
Status 0 indicates that the KVM was commanded to set itself to factory defaults.
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 |
Collected through SNMP push (traps).
No user action is required.
This section provides details on the fan failure metrics.
This section provides details on the power supply metrics.
Status 0 indicates that the KVM's power supply has failed.
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 |
Collected through SNMP push.
No user action is required.
This section describes the reboot started metrics.
Status 0 indicates that the KVM is rebooting.
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 |
Collected using OS line token fetchlet by running the agent provided script osresp.pl
No user action is required.
The name of the user that ordered the KVM to reboot.
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 |
Collected using OS line token fetchlet by running the agent provided script osresp.pl
No user action is required.
This section describes the response metrics.
Indicator of whether OMS on the KVM is running. 1 indicates Up, 0 indicates 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 |
Collected using OS line token fetchlet by running the agent provided script osresp.pl
No user action is required.
This is the KVM ping time, in ms.
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 |
Collected using OS line token fetchlet by running the agent provided script osresp.pl
No user action is required.
This section provides details on the temperature range metrics.
Status 0 indicates that the KVM's temperature is outside operating range.
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 |
Collected through SNMP push
No user action is required.