CISCO-REPORT-INTERVAL-TC-MIB
The CISCO-REPORT-INTERVAL-TC-MIB defines textual conventions for Cisco SNMP agents to standardize the configuration and tracking of performance history data across configurable reporting intervals. It enables the monitoring of elapsed time, total collected intervals, and data availability gaps for metrics such as interface throughput or CPU utilization, while managing the retention of historical data points up to a defined maximum limit.
Imported Objects
Objects
1 total| Object Name |
|---|
ciscoReportIntervalTcMIB MODULE-IDENTITY .1.3.6.1.4.1.9.9.670 |
CISCO-REPORT-INTERVAL-TC-MIB Technical Reference Overview
The CISCO-REPORT-INTERVAL-TC-MIB SNMP MIB module published by Cisco defines 1 managed OID objects, including 0 scalar/column metrics, 0 SNMP tables, and 0 trap/notification events anchored at base OID .1.3.6.1.4.1.9.9.670.
Key OID Definitions in CISCO-REPORT-INTERVAL-TC-MIB
.1.3.6.1.4.1.9.9.670This MIB module defines textual conventions used by MIB modules that define objects describing performance history data based on a configurable reporting interval. Use of these textual conventions assumes the following: - The SNMP entity supports performance history data collection based on a configurable interval. - The SNMP entity is capable of maintaining a history of N report intervals. A MIB module using these textual conventions defines the value of N, which may be configurable. - The SNMP entity may optionally support aggregation of performance data maintained by historic report intervals. - A MIB module using these textual conventions may define separate tables for the current interval, historic intervals, and the aggregation of historic performance data. - A MIB module using these textual conventions must define the following objects: xxxReportInterval OBJECT-TYPE SYNTAX Unsigned32 (0..4294967295) UNITS 'xxx-units' MAX-ACCESS read-only STATUS current DESCRIPTION 'This object indicates the duration of a report interval.' ::= { xxx } xxxReportMaxIntervals OBJECT-TYPE SYNTAX Unsigned32 (0..4294967295) UNITS 'report intervals' MAX-ACCESS read-only STATUS current DESCRIPTION 'This object indicates the maximum number of report intervals.' ::= { xxx } xxxReportElapsedTime OBJECT-TYPE SYNTAX Gauge32 UNITS 'xxx-units' MAX-ACCESS read-only STATUS current DESCRIPTION 'This object indicates the time that has elapsed since the beginning of the current report interval.' ::= { xxx } xxxReportIntervals OBJECT-TYPE SYNTAX Gauge32 UNITS 'report intervals' MAX-ACCESS read-only STATUS current DESCRIPTION 'This object indicates the number of report intervals for which data has been collected. The value of this column starts at 0 and increments at the end of each report interval until the number of report intervals is equal to the corresponding value of xxxReportMaxIntervals.' ::= { xxx } xxxReportInvalidIntervals OBJECT-TYPE SYNTAX Gauge32 UNITS 'report intervals' MAX-ACCESS read-only STATUS current DESCRIPTION 'This object indicates the number of report intervals, in the range of 0 to the value of the corresponding instance of xxxReportValidIntervals, for which no data is available. The value of this column will typically be 0, except in certain circumstances when some intervals are not available. ::= { xxx } Observe that if the MIB module defines tables that maintain performance data for multiple instances of a measured entity (e.g., an interface), then the definition of these objects need to allow for the maintenance of these objects per instance of the measured entity. A MIB module may choose to provide the write-access to xxxReportInterval and xxxReportMaxIntervals. In this case, the MIB module must consider the following: - The MIB module may want to refine the data type to something more concise. Alternatively, an implementation may specify variations in an agent capabilities. - If the definition of either of these objects specifies '0' as an acceptable value, then the descriptive text should describe the semantics of this value. - The descriptive text of xxxReportInterval must explain, 'When this value changes, the SNMP entity should discard any previously collected report interval data.' - The descriptive text of xxxReportMaxIntervals must explain, 'When this value changes to a value less than its current value, the SNMP entity should discard older report intervals to comply with the new value.'
More MIBs from Cisco
Browse all CiscoMIBs →The CISCO-UNIFIED-COMPUTING-COMPUTE-MIB provides SNMP-based monitoring and management of Cisco UCS compute blades, servers, and chassis components, exposing critical metrics such as CPU utilization, memory usage, thermal sensor readings, power supply status, and interface operational states. This module enables granular visibility into the health and performance of the Cisco Unified Computing System's compute subsystems for capacity planning and fault isolation.
The CISCO-UNIFIED-COMPUTING-STORAGE-MIB facilitates SNMP-based monitoring and management of storage subsystems, including Fibre Channel and iSCSI interfaces, within the Cisco Unified Computing System (UCS) fabric interconnects and blade servers. It exposes critical operational metrics such as port status, error counters, throughput statistics, and storage controller health states to enable granular visibility into the storage infrastructure.
The CISCO-UNIFIED-COMPUTING-VNIC-MIB enables SNMP-based monitoring and management of Virtual Network Interface Card (vNIC) attributes, including operational status, traffic counters, and binding configurations, within the Cisco Unified Computing System (UCS) fabric interconnects and server blades.
SNMP MIB module
The CISCO-UNIFIED-COMPUTING-BIOS-MIB enables SNMP-based monitoring and configuration of BIOS-level parameters, firmware versions, and hardware initialization states within Cisco Unified Computing System (UCS) servers. It provides visibility into critical server boot diagnostics, BIOS settings, and hardware readiness indicators to facilitate low-level infrastructure management and troubleshooting.
The CISCO-UNIFIED-COMPUTING-ETHER-MIB provides SNMP management interfaces for monitoring Ethernet interface statistics, link states, and error counters on Cisco Unified Computing System (UCS) fabric interconnects and blade server line cards. This module enables the tracking of physical layer connectivity, port throughput, and packet error rates within the UCS Ethernet switching infrastructure.