| 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 |
| 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 |
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.
This metric collection is not initiated by the agent. The IB switch pushes information to the agent through SNMP trap mechanism. It works only when the agent subscribes for SNMP traps. Note that this metric is used only for generating alerts. No data is uploaded to repository. The All Metrics page will not show any data for this metric.
Indicates whether severity is set or cleared (Major/Cleared).
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.
No user action is required.
Aggregate sensor is de-asserted (1) or aggregate sensor state is asserted (2).
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.
No user action is required.
Similar to Aggregate sensors, this metric is an SNMP trap based metric.
These values (Critical/Major/Warning) indicate fan speed has exceeded fatal, critical, and non-critical thresholds, respectively. The first two states are shown as Critical alert in Enterprise Manager and the last state is shown as Warning.
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.
No user action is required.
Speed of the fan in revolutions per minute.
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.
No user action is required.
This metric is used to detect whether the Management server on the cell is running.This metric is checked at 1 minute intervals. A one in the status column indicates that the cell is up, otherwise the cell is down.
This metric is checked at 1 minute intervals. A one in the status column indicates that the cell is up, otherwise the cell is 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 1 Minutes |
Not available
No user action is required.
This metric provides overall performance of the ibswitch across all ports.
The average number of bytes received and transmitted per second across all ports in the ibswitch (KBPS).
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 1 Minutes |
Collected through SNMP.
No user action is required.
The maximum number of bytes received and transmitted per second across all ports in ibswitch (KBPS)
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 1 Minutes |
Collected through SNMP.
No user action is required.
The minimum number of bytes received and transmitted per second across all ports in ibswitch (KBPS).
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 1 Minutes |
Collected through SNMP.
No user action is required.
This metric is mainly used for monitoring the connectivity of ports and raising alerts when there is a disconnection.
The IB globally unique identifier (GUID). This is not an Enterprise Manager target GUID of the entity to which the port is connected. This can be switch GUID, if the other end is a switch port, or port GUID if it is an HCA port.
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 1 Minutes |
Collected through SNMP.
No user action is required.
The name of the entity (Switch/Cell/Compute Node) 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 1 Minutes |
Collected through SNMP.
No user action is required.
This can take only two values (switch/port). If the entity type (with GUID provided) in first column is switch then this value is switch, otherwise it is port.
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 1 Minutes |
Collected through SNMP.
No user action is required.
The port number of the peer port.
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 1 Minutes |
Collected through SNMP.
No user action is required.
This can take any of the three values (Switch/Cell/Compute Node) depending on what entity this port is connected to.
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 1 Minutes |
Collected through SNMP.
No user action is required.
If this port is currently disconnected, then this field provides the type of the entity from which disconnection happened. It can take four possible values (Switch/Cell/Node/None). When the port is in connected state then the value is None.
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 1 Minutes |
Collected through SNMP.
No user action is required.
This metric provides statistics obtained from perfquery output on the switch. This metric values provide the delta change in error counters since last collection. Alerts are raised only if there are new errors since last metric collection.
The number of “buffer overruns exceeding the threshold” since last Collection (which is 5 minutes).
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.
No user action is required.
The number of incoming VL 15 packets dropped due to lack of buffers since last metric collection.
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.
No user action is required.
Number of times link error recovery process was completed successfully since last collection.
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.
No user action is required.
Number of packets not transmitted due to constrains since last collection.
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.
No user action is required.
Number of packets discarded due to constraints since last collection.
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.
No user action is required.
The number of packets marked with the EBP delimiter received on the port.
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 1 Minutes |
Collected through SNMP.
No user action is required.
The number of packets received with errors since last collection
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.
No user action is required.
The number of symbols errors detected since last collection.
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.
No user action is required.
This section describes performance metrics at the switch port level.
The number of bytes transmitted and received.
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 1 Minutes |
Collected through SNMP.
No user action is required.
The number of bytes received per second (KBPS).
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 1 Minutes |
Collected through SNMP.
No user action is required.
The number of bytes transmitted per second (KBPS).
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 1 Minutes |
Collected through SNMP.
No user action is required.
The number of packets received per second.
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 1 Minutes |
Collected through SNMP.
No user action is required.
The number of packets transmitted per second.
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 1 Minutes |
Collected through SNMP.
No user action is required.
This section describes the Switch Port state metrics.
If the active speed of a link is less than the enabled speed, then it is considered to be degraded and this column value is set to 1. It is mainly used for raising alerts.
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 1 Minutes |
Collected through SNMP.
No user action is required.
The link is down if the physical link state is 0.
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 1 Minutes |
Collected through SNMP.
No user action is required.
The physical link state is 0 if the port is in polling or disabled state.
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 1 Minutes |
Collected through SNMP.
No user action is required.
The following describes the overall state of switch ports.
The total number of active ports.
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 1 Minutes |
Collected through SNMP.
No user action is required.
The total number of degraded ports.
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 1 Minutes |
Collected through SNMP.
No user action is required.
Number of ports with errors. From 12.1.0.3 Exadata plug-in onwards, degraded ports are counted both in Degraded ports and Error ports categories.
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 1 Minutes |
Collected through SNMP.
No user action is required.
This describes the switch temperature metrics
This is the rear chassis temperature.
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 1 Minutes |
Collected through SNMP.
No user action is required.
This is the front chassis temperature.
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 1 Minutes |
Collected through SNMP.
No user action is required.
This is the I4 chip temperature.
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 1 Minutes |
Collected through SNMP.
No user action is required.
This is management controller temperature.
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 1 Minutes |
Collected through SNMP.
No user action is required.
Similar to other SNMP trap based metrics, this metric is also used only for generating alerts and it is not uploaded to repository.
These values (Critical/Major/Warning) indicate if the temperature has exceeded fatal, critical, and non-critical thresholds, respectively. The first two states are shown as Critical alert in Enterprise Manager and the last state is shown as Warning.
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 1 Minutes |
Collected through SNMP.
No user action is required.
Temperature of rear chassis/front chassis/I4 chip/Management controller.
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 1 Minutes |
Collected through SNMP.
No user action is required.
This describes the voltage sensor metrics.
These values (Critical/Major/Warning) indicate if the temperature has exceeded fatal, critical, and non-critical thresholds, respectively. The first two states are shown as Critical alert in Enterprise Manager and the last state is shown as Warning.
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 1 Minutes |
Collected through SNMP.
No user action is required.
|
 Copyright © 2006, 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
