CISCO-FLOW-MONITOR-MIB
The CISCO-FLOW-MONITOR-MIB enables Cisco devices to monitor traffic flow quality by classifying flows, collecting packet-level statistics, and computing metrics for protocols such as IP, UDP, TCP, and RTP. It facilitates fault management through configurable standing conditions and alarm groups that trigger SNMP traps or syslog messages when flow expiration rates or other thresholds are exceeded.
Imported Objects
Objects
173 total| Object Name |
|---|
ciscoFlowMonitorMIB MODULE-IDENTITY .1.3.6.1.4.1.9.9.692 |
ciscoFlowMonitorMIBNotifs OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.692.0 |
cfmNotifyAlarm NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.692.0.1 |
ciscoFlowMonitorMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.692.1 |
cfmFlowMonitors OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.692.1.1 |
cfmFlowMonitorTable SEQUENCE OF CfmFlowMonitorEntry .1.3.6.1.4.1.9.9.692.1.1.1 |
cfmFlowMonitorEntry CfmFlowMonitorEntry .1.3.6.1.4.1.9.9.692.1.1.1.1 |
cfmFlowMonitorId FlowMonitorIdentifier (CISCO-FLOW-MONITOR-TC-MIB) .1.3.6.1.4.1.9.9.692.1.1.1.1.1 |
cfmFlowMonitorDescrro SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.9.692.1.1.1.1.2 |
cfmFlowMonitorCapsro FlowMetrics (CISCO-FLOW-MONITOR-TC-MIB) .1.3.6.1.4.1.9.9.692.1.1.1.1.3 |
cfmFlowMonitorFlowCountro Gauge32 UNITS "traffic flows" .1.3.6.1.4.1.9.9.692.1.1.1.1.4 |
cfmFlowMonitorConditionsProfilero FlowMonitorConditionsProfileOrZero .1.3.6.1.4.1.9.9.692.1.1.1.1.5 |
cfmFlowMonitorConditionsro FlowMonitorConditions (CISCO-FLOW-MONITOR-TC-MIB) .1.3.6.1.4.1.9.9.692.1.1.1.1.6 |
cfmFlowMonitorAlarmsro FlowMonitorConditions (CISCO-FLOW-MONITOR-TC-MIB) .1.3.6.1.4.1.9.9.692.1.1.1.1.7 |
cfmFlowMonitorAlarmSeverityro CiscoAlarmSeverity (CISCO-TC) .1.3.6.1.4.1.9.9.692.1.1.1.1.8 |
cfmFlowMonitorAlarmCriticalCountro Gauge32 UNITS "alarms" .1.3.6.1.4.1.9.9.692.1.1.1.1.9 |
cfmFlowMonitorAlarmMajorCountro Gauge32 UNITS "alarms" .1.3.6.1.4.1.9.9.692.1.1.1.1.10 |
cfmFlowMonitorAlarmMinorCountro Gauge32 UNITS "alarms" .1.3.6.1.4.1.9.9.692.1.1.1.1.11 |
cfmFlowMonitorAlarmWarningCountro Gauge32 UNITS "alarms" .1.3.6.1.4.1.9.9.692.1.1.1.1.12 |
cfmFlowMonitorAlarmInfoCountro Gauge32 UNITS "alarms" .1.3.6.1.4.1.9.9.692.1.1.1.1.13 |
cfmFlowMonitorTableChangedro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.9.9.692.1.1.2 |
cfmFlows OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.692.1.2 |
cfmFlowTable SEQUENCE OF CfmFlowEntry .1.3.6.1.4.1.9.9.692.1.2.1 |
cfmFlowEntry CfmFlowEntry .1.3.6.1.4.1.9.9.692.1.2.1.1 |
cfmFlowId FlowIdentifier (CISCO-FLOW-MONITOR-TC-MIB) .1.3.6.1.4.1.9.9.692.1.2.1.1.1 |
cfmFlowDescrro SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.9.692.1.2.1.1.2 |
cfmFlowNextro RowPointer (SNMPv2-TC) .1.3.6.1.4.1.9.9.692.1.2.1.1.3 |
cfmFlowCreateTimero TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.9.9.692.1.2.1.1.4 |
cfmFlowDiscontinuityTimero TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.9.9.692.1.2.1.1.5 |
cfmFlowExpirationTimero Unsigned32 .1.3.6.1.4.1.9.9.692.1.2.1.1.6 |
cfmFlowDirectionro Enumeration .1.3.6.1.4.1.9.9.692.1.2.1.1.7 |
cfmFlowAdminStatusrw Enumeration .1.3.6.1.4.1.9.9.692.1.2.1.1.8 |
cfmFlowOperStatusro Enumeration .1.3.6.1.4.1.9.9.692.1.2.1.1.9 |
cfmFlowIngressTypero FlowPointType (CISCO-FLOW-MONITOR-TC-MIB) .1.3.6.1.4.1.9.9.692.1.2.1.1.10 |
cfmFlowIngressro FlowPointIdentifier (CISCO-FLOW-MONITOR-TC-MIB) .1.3.6.1.4.1.9.9.692.1.2.1.1.11 |
cfmFlowEgressTypero FlowPointType (CISCO-FLOW-MONITOR-TC-MIB) .1.3.6.1.4.1.9.9.692.1.2.1.1.12 |
cfmFlowEgressro FlowPointIdentifier (CISCO-FLOW-MONITOR-TC-MIB) .1.3.6.1.4.1.9.9.692.1.2.1.1.13 |
cfmFlowTableChangedro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.9.9.692.1.2.2 |
cfmFlowL2VlanTable SEQUENCE OF CfmFlowL2VlanEntry .1.3.6.1.4.1.9.9.692.1.2.3 |
cfmFlowL2VlanEntry CfmFlowL2VlanEntry .1.3.6.1.4.1.9.9.692.1.2.3.1 |
cfmFlowL2VlanNextro RowPointer (SNMPv2-TC) .1.3.6.1.4.1.9.9.692.1.2.3.1.1 |
cfmFlowL2VlanIdro VlanId (Q-BRIDGE-MIB) .1.3.6.1.4.1.9.9.692.1.2.3.1.2 |
cfmFlowL2VlanCosro Layer2Cos (CISCO-TC) .1.3.6.1.4.1.9.9.692.1.2.3.1.3 |
cfmFlowL2VlanTableChangedro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.9.9.692.1.2.4 |
cfmFlowIpTable SEQUENCE OF CfmFlowIpEntry .1.3.6.1.4.1.9.9.692.1.2.5 |
cfmFlowIpEntry CfmFlowIpEntry .1.3.6.1.4.1.9.9.692.1.2.5.1 |
cfmFlowIpNextro RowPointer (SNMPv2-TC) .1.3.6.1.4.1.9.9.692.1.2.5.1.1 |
cfmFlowIpAddrTypero InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.692.1.2.5.1.2 |
cfmFlowIpAddrSrcro InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.692.1.2.5.1.3 |
cfmFlowIpAddrDstro InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.692.1.2.5.1.4 |
cfmFlowIpValidro Bits .1.3.6.1.4.1.9.9.692.1.2.5.1.5 |
cfmFlowIpTrafficClassro Unsigned32 .1.3.6.1.4.1.9.9.692.1.2.5.1.6 |
cfmFlowIpHopLimitro Unsigned32 .1.3.6.1.4.1.9.9.692.1.2.5.1.7 |
cfmFlowIpTableChangedro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.9.9.692.1.2.6 |
cfmFlowUdpTable SEQUENCE OF CfmFlowUdpEntry .1.3.6.1.4.1.9.9.692.1.2.7 |
cfmFlowUdpEntry CfmFlowUdpEntry .1.3.6.1.4.1.9.9.692.1.2.7.1 |
cfmFlowUdpNextro RowPointer (SNMPv2-TC) .1.3.6.1.4.1.9.9.692.1.2.7.1.1 |
cfmFlowUdpPortSrcro InetPortNumber (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.692.1.2.7.1.2 |
cfmFlowUdpPortDstro InetPortNumber (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.692.1.2.7.1.3 |
cfmFlowUdpTableChangedro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.9.9.692.1.2.8 |
cfmFlowTcpTable SEQUENCE OF CfmFlowTcpEntry .1.3.6.1.4.1.9.9.692.1.2.9 |
cfmFlowTcpEntry CfmFlowTcpEntry .1.3.6.1.4.1.9.9.692.1.2.9.1 |
cfmFlowTcpNextro RowPointer (SNMPv2-TC) .1.3.6.1.4.1.9.9.692.1.2.9.1.1 |
cfmFlowTcpPortSrcro InetPortNumber (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.692.1.2.9.1.2 |
cfmFlowTcpPortDstro InetPortNumber (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.692.1.2.9.1.3 |
cfmFlowTcpTableChangedro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.9.9.692.1.2.10 |
cfmFlowRtpTable SEQUENCE OF CfmFlowRtpEntry .1.3.6.1.4.1.9.9.692.1.2.11 |
cfmFlowRtpEntry CfmFlowRtpEntry .1.3.6.1.4.1.9.9.692.1.2.11.1 |
cfmFlowRtpNextro RowPointer (SNMPv2-TC) .1.3.6.1.4.1.9.9.692.1.2.11.1.1 |
cfmFlowRtpVersionro Unsigned32 .1.3.6.1.4.1.9.9.692.1.2.11.1.2 |
cfmFlowRtpSsrcro Unsigned32 .1.3.6.1.4.1.9.9.692.1.2.11.1.3 |
cfmFlowRtpPayloadTypero Unsigned32 .1.3.6.1.4.1.9.9.692.1.2.11.1.4 |
cfmFlowRtpTableChangedro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.9.9.692.1.2.12 |
cfmFlowMetrics OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.692.1.3 |
cfmFlowMetricsTable SEQUENCE OF CfmFlowMetricsEntry .1.3.6.1.4.1.9.9.692.1.3.1 |
cfmFlowMetricsEntry CfmFlowMetricsEntry .1.3.6.1.4.1.9.9.692.1.3.1.1 |
cfmFlowMetricsCollectedro FlowMetrics (CISCO-FLOW-MONITOR-TC-MIB) .1.3.6.1.4.1.9.9.692.1.3.1.1.1 |
cfmFlowMetricsIntervalTimero Unsigned32 .1.3.6.1.4.1.9.9.692.1.3.1.1.2 |
cfmFlowMetricsMaxIntervalsro Unsigned32 .1.3.6.1.4.1.9.9.692.1.3.1.1.3 |
cfmFlowMetricsElapsedTimero Gauge32 UNITS "seconds" .1.3.6.1.4.1.9.9.692.1.3.1.1.4 |
cfmFlowMetricsIntervalsro Gauge32 UNITS "intervals" .1.3.6.1.4.1.9.9.692.1.3.1.1.5 |
cfmFlowMetricsInvalidIntervalsro Gauge32 UNITS "intervals" .1.3.6.1.4.1.9.9.692.1.3.1.1.6 |
cfmFlowMetricsConditionsProfilero FlowMonitorConditionsProfileOrZero .1.3.6.1.4.1.9.9.692.1.3.1.1.7 |
cfmFlowMetricsConditionsro FlowMonitorConditions (CISCO-FLOW-MONITOR-TC-MIB) .1.3.6.1.4.1.9.9.692.1.3.1.1.8 |
cfmFlowMetricsAlarmsro FlowMonitorConditions (CISCO-FLOW-MONITOR-TC-MIB) .1.3.6.1.4.1.9.9.692.1.3.1.1.9 |
cfmFlowMetricsAlarmSeverityro CiscoAlarmSeverity (CISCO-TC) .1.3.6.1.4.1.9.9.692.1.3.1.1.10 |
cfmFlowMetricsPktsro Counter64 UNITS "packets" .1.3.6.1.4.1.9.9.692.1.3.1.1.11 |
cfmFlowMetricsOctetsro Counter64 UNITS "octets" .1.3.6.1.4.1.9.9.692.1.3.1.1.12 |
cfmFlowMetricsBitRateUnitsro FlowBitRateUnits (CISCO-FLOW-MONITOR-TC-MIB) .1.3.6.1.4.1.9.9.692.1.3.1.1.13 |
cfmFlowMetricsBitRatero Gauge32 .1.3.6.1.4.1.9.9.692.1.3.1.1.14 |
cfmFlowMetricsPktRatero Gauge32 UNITS "packets per second" .1.3.6.1.4.1.9.9.692.1.3.1.1.15 |
cfmFlowMetricsTableChangedro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.9.9.692.1.3.2 |
cfmFlowMetricsIntTable SEQUENCE OF CfmFlowMetricsIntEntry .1.3.6.1.4.1.9.9.692.1.3.3 |
cfmFlowMetricsIntEntry CfmFlowMetricsIntEntry .1.3.6.1.4.1.9.9.692.1.3.3.1 |
cfmFlowMetricsIntNumber Unsigned32 .1.3.6.1.4.1.9.9.692.1.3.3.1.1 |
cfmFlowMetricsIntValidro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.692.1.3.3.1.2 |
cfmFlowMetricsIntTimero TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.9.9.692.1.3.3.1.3 |
cfmFlowMetricsIntConditionsro FlowMonitorConditions (CISCO-FLOW-MONITOR-TC-MIB) .1.3.6.1.4.1.9.9.692.1.3.3.1.4 |
cfmFlowMetricsIntAlarmsro FlowMonitorConditions (CISCO-FLOW-MONITOR-TC-MIB) .1.3.6.1.4.1.9.9.692.1.3.3.1.5 |
cfmFlowMetricsIntAlarmSeverityro CiscoAlarmSeverity (CISCO-TC) .1.3.6.1.4.1.9.9.692.1.3.3.1.6 |
CISCO-FLOW-MONITOR-MIB Technical Reference Overview
The CISCO-FLOW-MONITOR-MIB SNMP MIB module published by Cisco defines 173 managed OID objects, including 123 scalar/column metrics, 13 SNMP tables, and 1 trap/notification events anchored at base OID .1.3.6.1.4.1.9.9.692. Key tabular structures include cfmFlowMonitorTable, cfmFlowTable, cfmFlowL2VlanTable, cfmFlowIpTable, cfmFlowUdpTable, cfmFlowTcpTable. Monitored SNMP traps/notifications include cfmNotifyAlarm.
Key OID Definitions in CISCO-FLOW-MONITOR-MIB
.1.3.6.1.4.1.9.9.692This MIB module defines objects that describe flow monitoring. A typical application of this MIB module will facilitate monitoring media flows, especially flows carrying video streams. However, by no means does the definition of this MIB module prevents other applications from using it. FLOW MONITORS ================= At the top level, this MIB module describes the notion of a flow monitor. A flow monitor is a hardware or software entity that classifies traffic flows, collects data on conforming traffic flows, and periodically computes metrics that reflect the quality of the traffic flows. Because a device can support more than one flow monitor, the MIB module defines the cfmFlowMonitorTable. Consider an edge router that supports a certain line card that has an integrated capability to monitor video flows. In this example, the cfmFlowMonitorTable would contain a row describing each line card installed in the device. TRAFFIC FLOWS ================= At the next level, this MIB module describes the notion of a traffic flow. This MIB module uniquely identifies a traffic flow using an auxiliary variable called cfmFlowId; however, an implementation only has guarantee its uniqueness within the scope of the flow monitor that has the responsibility for monitoring the traffic flow. Thus, we can think of the flow monitor as a container for the traffic flows for which it collects data and periodically computes metrics, as the figure below illustrates. ++ | cfmFlowTable | | | + | cfmFlowMonitorId = 3 ->| ++ | + | | cfmFlowId = 101 | | | ++ | | ++ | | | cfmFlowMonitorId = 3 | | | | cfmFlowId = 102 | | | ++ | | : | | : | | ++ | | | cfmFlowMonitorId = 3 | | | | cfmFlowId = 150 | | | ++ | ++ | | + | cfmFlowMonitorId = 4 ->| ++ | + | | cfmFlowId = 1 | | | ++ | | ++ | | | cfmFlowMonitorId = 4 | | | | cfmFlowId = 2 | | | ++ | | : | | : | | ++ | | | cfmFlowMonitorId = 4 | | | | cfmFlowId = 150 | | | ++ | ++ | | ++ While the identifying of a traffic flow using this auxiliary variable is convenient for the MIB module, it is does suffice for an EMS/NMS trying to isolate faults in a network delivering these traffic flows. To aid an EMS/NMS in this task, this MIB module defines a number of tables that provide layers of data relating to a traffic flow, including: o cfmFlowL2VlanTable - describes L2 VLAN data relating to traffic flows. o cfmFlowIpTable - describes IP data relating to traffic flows. o cfmFlowUdpTable - describes UDP data relating to traffic flows. o cfmFlowTcpTable - describes TCP data relating to traffic flows. o cfmFlowRtpTable - describes RTP data relating to traffic flows. Each of these tables have a sparse dependent relationship on the cfmFlowTable, as there exist situations when the data may not be available for a traffic flow, including: 1) The flow monitor simply may not collect the particular data for the traffic flows that it has the responsibility of monitoring. For example, a flow monitor may not have any concern for L2 VLAN data. 2) The data may not apply to a traffic flow. For example, a TCP and RTP data do not apply for a UDP traffic flow. To help an EMS/NMS navigate the data collected for a traffic flow, the corresponding rows are daisy-chained using 'next objects'. An EMS/NMS starts with cfmFlowNext, which indicates a reference to the row in the next table containing data related to the traffic flow. The first object contained by each of these tables is a 'next object'. Consider a RTP traffic flow for which the flow monitor has collected IP, UDP, and RTP data. The figure below illustrates how this MIB module daisy chains this data through the relevant tables. + | cfmFlowTable | | + | | cfmFlowMonitorId = 3 | | | | cfmFlowId = 42 | | | | cfmFlowNext = cfmFlowIpNext.3.42 | + + | + | cfmFlowIpTable | | | + | | cfmFlowMonitorId = 3 |< | | cfmFlowId = 42 | | | | cfmFlowIpNext = cfmFlowUdpNext.3.42 | + + | + | cfmFlowUdpTable | | | + | | cfmFlowMonitorId = 3 |< | | cfmFlowId = 42 | | | | cfmFlowUdpNext = cfmFlowRtpNext.3.42 | + + | + | cfmFlowRtpTable | | | + | | cfmFlowMonitorId = 3 |< | | cfmFlowId = 42 | | | | cfmFlowRtpNext = zeroDotZero | | | + + Observe that this structure simplifies the task of extending the MIB module to support additional layers of data. For example, if there is a need for a device to collect data relating to the MPEG-TS layer of a flow carrying a video stream, then it is as simple as defining a table containing this data. However, the definition of such a table must comply with the following requirements: 1) The table must have a sparse dependent relationship on the cfmFlowTable. 2) The first object contained by the table must be a 'next object' to support daisy chaining. REPORTING FLOW METRICS ========================== At the next level, the MIB defines two tables that together form the foundation for reporting metrics. The cfmFlowMetricsTable has a one-to-one dependent relationship on the cfmFlowTable, and it contains data aggregate metrics and data relating to the collection of metrics for the corresponding traffic flow. A row in this table also serves as a container for the historic metrics computed by the corresponding flow monitor, as the figure below illustrates. ++ | cfmFlowMetricsIntTable | | | ++ | cfmFlowMetricsEntry |+ | | | | | cfmFlowMonitorId = 3 | | | cfmFlowMonitorId = 3 | | | cfmFlowId = 101 | | | cfmFlowid = 101 | | | cfmFlowMetricsIntNumber = 1 | | ++ | | + | | cfmFlowMonitorId = 3 | | | | cfmFlowId = 101 | | | | cfmFlowMetricsIntNumber = 2 | | | + | : | | : | | + | | cfmFlowMonitorId = 3 | | | | cfmFlowId = 101 | | | | cfmFlowMetricsIntNumber = N | | | + + | | ++ The device collects data for a traffic flow over a configured measurement interval, indicated by cfmFlowMetricsIntervalTime. At the end of a measurement interval, the device computes metrics from this data, generating a report. An EMS/NMS can access this report using the cfmFlowMetricsIntTable. cfmFlowMetricsMaxInterval indicates the maximum number of reports a device will save for the corresponding traffic flow, while cfmFlowMetricsIntervals indicates the number of reports currently saved by the device. The cfmFlowMetricsTable and cfmFlowMetricsIntTable have the intent of providing a foundation for reporting metrics for a traffic flow. Furthermore, it is the intent that additional MIB modules define extensions to these tables describing specific sets of metrics. The following list provides some examples: o CISCO-FLOW-MON-MDI-MIB - this MIB module defines extensions that describe MDI metrics defined by RFC-4445. o CISCO-FLOW-MON-RTP-MIB - this MIB module defines extensions that describe RTP metrics defined by RFC-3550. o CISCO-FLOW-MON-IP-CBR-MIB - this MIB module defines extension that describe IP CBR metrics. The tables defined by these MIB modules have a sparse dependent relationhip on the cfmFlowMetricsTable and cfmFlowMetricsIntTable. An EMS/NMS can determine the metrics collected for a traffic flow from the corresponding instance of cfmFlowMetricsCollected, which is nothing more than a bit string-value for which each bit corresponds to a different set of metrics. FAULT MANAGEMENT ==================== At the next level, this MIB module defines tables that describe standing conditions. A standing condition is a lasting error, fault, or warning resulting from the application of a set of criteria to the state of an entity. For example, a flow monitor ceases monitoring a traffic flow when it has not received any packets for that traffic flow in a configured interval of time. If flow monitor expires a significantly large number of traffic flows during a measurement interval, then this might signal a fault. In this example, the 'set of criteria' is a rising threshold and the 'state of an entity' is the number of traffic flows expired by a flow monitor. The cfmConditionTable describes the criteria applied to entities managed by the device, specifically flow monitors and traffic flows. The table groups these criteria into 'conditions profiles'. The device periodically applies these criteria to an entity and saves the results in a bit string-value associated with the entity. An EMS/NMS can monitor the most recent standing conditions for a flow monitor by retrieving the corresponding instance of cfmFlowMonitorConditions. Likewise, an EMS/NMS can monitor the most recent standing conditions for a traffic flow by retrieving the corresponding instance of cfmFlowMetricsConditions. It goes without saying that monitoring the standing conditions for significantly large numbers of traffic flows becomes problematic. To aid an EMS/NMS in this task, this MIB module defines many mechanisms. The most basic of these mechanisms is the notion of an alarm, which is simply a standing condition for which the device signals changes in state. This MIB module provides for three means of signaling when the device raises or clears an alarm condition: 1) Logging - the device creates a record of the event and saves it in a historical account. 2) syslog - the device generates a syslog message containing details of the event and sends it to one or more configured syslog server. 3) SNMP - the device generates a SNMP notification containing details of the event and sends it to one or more configured targets. An EMS/NMS can monitor the most recent alarm conditions for a flow monitor by retrieving the corresponding instance of cfmFlowMonitorAlarms. Likewise, the EMS/NMS can monitor the most recent alarm conditions for a traffic flow by retrieving the corresponding instance of cfmFlowMetricsAlarms. Additionally, the EMS/NMS can poll a summary of alarm conditions maintained for each flow monitor and the traffic flows that it monitors. The following list summarizes the data contained by this summary: o cfmFlowMonitorAlarmSeverity o cfmFlowMonitorAlarmCriticalCount o cfmFlowMonitorAlarmMajorCount o cfmFlowMonitorAlarmMinorCount o cfmFlowMonitorAlarmWarningCount o cfmFlowMonitorAlarmInfoCount An EMS/NMS can also poll cfmAlarmHistoryLastId, which indicates the value of the identifier assigned to the last record saved to the historical account. When it observes a change in the value of this object, then it can retrieve the new records from the cfmAlarmHistoryTable. The burden of monitoring alarm conditions for sufficiently large numbers of traffic flows can itself become a daunting task. Thus, this MIB module defines the notion of an alarm group, which represents a single alarm condition that aggregates a standing condition for a set of traffic flows. The cfmAlarmGroupTable describes the alarm groups configured for a device, and the cfmAlarmGroupFlowTable describes the sets of flows aggregated by these alarm groups. GLOSSARY ============ Alarm Action - a method used by the device to signal changes in an alarm condition. Alarm Aggregation - a technique used to efficiently monitor the same standing condition for a flow set. Alarm Condition - a standing condition for which the device signals changes in state. Alarm Group - a flow set for which the device monitors a configured standing condition, raising an alarm when a configured number of flows in the flow set assert the standing standing. Alarm Severity - the relative disposition of an alarm condition when raised by the device. For example, a provider may regard a flow stop alarm as having a higher severity than a flow's loss fraction exceeding a configured threshold. Flow Monitor - a hardware or software entity that classifies traffic flows, collects flow data, and periodically computes flow metrics. Flow Metric - a measurement that reflects the quality of a traffic flow. Flow Point - represents the ingress or egress of a traffic flow. Flow Set - a group of traffic flows. Measurement Interval - the length of time over which a flow monitor collects data related to a traffic flow, after which the flow monitor computes flow metrics using the collected data. Standing Condition - represents a lasting error, fault, or warning resulting from the application of a set of criteria to the state of an entity, such as a flow monitor or traffic flow. For example, a flow monitor may assert a standing condition if the number of traffic flows that expire in a measurement interval exceeds a configured threshold. Traffic Flow - a unidirectional stream of packets conforming to a classifier. For example, packets having a particular source IP address, destination IP address, protocol type, source port number, and destination port number.
.1.3.6.1.4.1.9.9.692.1.1.1This table lists the flow monitors contained by the device.
.1.3.6.1.4.1.9.9.692.1.2.1This table lists the traffic flows monitored by each flow monitor supported by the device. This table has an expansion dependent relationship on the cfmFlowMonitorTable, containing zero or more rows for each flow monitor.
.1.3.6.1.4.1.9.9.692.1.2.3This table contains additional data relating to the L2 VLAN carrying traffic flows monitored by flow monitors. This table has a sparse dependent relationship on the cfmFlowTable.
.1.3.6.1.4.1.9.9.692.1.2.5This table contains additional data relating to the IP carrying the corresponding traffic flow. This table has a sparse dependent relationship on the cfmFlowTable.
.1.3.6.1.4.1.9.9.692.1.2.7This table contains additional data relating to the UDP carrying the corresponding traffic flow. This table has a sparse dependent relationship on the cfmFlowTable.
.1.3.6.1.4.1.9.9.692.1.2.9This table contains additional data relating to the TCP carrying the corresponding traffic flow. This table has a sparse dependent relationship on the cfmFlowTable.
.1.3.6.1.4.1.9.9.692.1.2.11This table contains additional data relating to the RTP carrying the corresponding traffic flow. This table has a sparse dependent relationship on the cfmFlowTable.
.1.3.6.1.4.1.9.9.692.1.3.1This table contains aggregate metrics and data relating to the collection of metrics for the traffic flows monitored by each of the flow monitors supported by the device. This table has a sparse dependent relationship on the cfmFlowTable, containing a row for each row in the cfmFlowTable for which the device is actively monitoring.
.1.3.6.1.4.1.9.9.692.1.3.3This table contains historic metrics for the traffic flows monitored by each of the flow monitors supported by the device. This table has an expansion dependent relationship on the cfmFlowMetricsTable, containing zero or more rows for each traffic flow.
.1.3.6.1.4.1.9.9.692.1.4.1This table lists the standing conditions monitored by the device. The table groups descriptions for standing conditions into condition profiles. The figure below illustrates the relationship between a flow monitor and a conditions profile. Observe that a conditions profile can contain the descriptions for the standing conditions monitored for more than one flow monitor. In this case, the instance of cfmFlowMonitorConditionsProfile for each of these flow monitors would reference the same conditions profile. ++ | flow monitor 1 | | | | cfmFlowMonitorConditionsProfile.1 = 42 -+ | | | | | cfmFlowMonitorConditions.1 | | | N 2 1 0 | | | +-+-...-+-+-+-+ | | | | | | | | | | | | +-+-...-+-+-+-+ | | | ^ ^ ^ ^ | | | | | | | | | +-|-|-|+ | | | | | | | | | V | | | | +-+ | | | | | conditions profile 42 | | | | | | +-+ | | | | +-| cfmConditionsDescr.42.0 | | | | | | +-+ | | | | | +-+ | | | + | | | +-+ | | | | +-+ | | +-| cfmConditionsDescr.42.2 | | | | +-+ | | | : | | | : | | | +-+ | +-| cfmConditionsDescr.42.N | | | +-+ | +-+ The figure below illustrates the relationship between a traffic flow and a conditions profile. Observe that a conditions profile can contain the descriptions for the standing conditions monitored for more than one traffic flow. In this case, the instance of cfmFlowMetricsConditionsProfile for each of these traffic flows would reference the same conditions profile. ++ | traffic flow 201 | | | | cfmFlowMetricsConditionsProfile.1.201 = 54 -+ | | | | | cfmFlowMetricsConditions.1.201 | | | N 2 1 0 | | | +-+-...-+-+-+-+ | | | | | | | | | | | | +-+-...-+-+-+-+ | | | ^ ^ ^ ^ | | | | | | | | | +-|-|-|+ | | | | | | | | | V | | | | +-+ | | | | | conditions profile 54 | | | | | | +-+ | | | | +-| cfmConditionsDescr.54.0 | | | | | | +-+ | | | | | +-+ | | | + | | | +-+ | | | | +-+ | | +-| cfmConditionsDescr.54.2 | | | | +-+ | | | : | | | : | | | +-+ | +-| cfmConditionsDescr.54.N | | | +-+ | +-+ The figure below illustrates the relationship between the description of a standing condition and an alarm group if the standing condition indicates that the device aggregates the standing condition into an alarm group (i.e., the corresponding instance of cfmConditionAlarm is 'grouped'). +-+ | conditions profile 42 | | +-+ | | | cfmConditionAlarm.42.9 = 'grouped' |< | | cfmConditionAlarmGroup.42.9 = 4 -+ | | | | ++ |< | | | | | +|+ | | V | | +-+ | | | alarm group 4 | | | | | | | | cfmAlarmGroupConditionsProfile.4 = 42 | cfmAlarmGroupConditionId.4 = 9 + | | +-+
.1.3.6.1.4.1.9.9.692.1.5.1This table lists alarm groups maintained by the device.
.1.3.6.1.4.1.9.9.692.1.5.3This table lists the traffic flows contained by each set of flows configured for the alarm groups contained by the cfmAlarmGroupTable.
.1.3.6.1.4.1.9.9.692.1.6.3This table lists a history of the changes in the state of alarm conditions monitored by the device.
.1.3.6.1.4.1.9.9.692.0.1The device generates this notification when an alarm condition has changed state and the value of cfmNOtifyEnable is 'true'.
.1.3.6.1.4.1.9.9.692.1.1.2This object indicates the value of sysUpTime the last time the device created or destroyed a row in cfmFlowMonitorTable.
.1.3.6.1.4.1.9.9.692.1.2.2This object indicates the value of sysUpTime the last time the device created or destroyed a row in cfmFlowTable.
.1.3.6.1.4.1.9.9.692.1.2.4This object indicates the value of sysUpTime the last time the device changed the cfmFlowL2VlanTable.
.1.3.6.1.4.1.9.9.692.1.2.6This object indicates the value of sysUpTime the last time the device changed the cfmFlowIpTable.
.1.3.6.1.4.1.9.9.692.1.2.8This object indicates the value of sysUpTime the last time the device changed the cfmFlowUdpTable.
.1.3.6.1.4.1.9.9.692.1.2.10This object indicates the value of sysUpTime the last time the device changed the cfmFlowTcpTable.
.1.3.6.1.4.1.9.9.692.1.2.12This object indicates the value of sysUpTime the last time the device changed the cfmFlowRtpTable.
.1.3.6.1.4.1.9.9.692.1.3.2This object indicates the value of sysUpTime the last time the device created or destroyed a row in cfmFlowMetricsTable.
.1.3.6.1.4.1.9.9.692.1.4.2This object indicates the value of sysUpTime the last time the device made a change to the cfmConditionTable.
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.