CISCO-FLOW-MONITOR-MIB

FlowMonitorIdentifierThis textual convention denotes an arbitrary integer-value that uniquely identifies a flow monitor. (1..4294967295) · Unsigned32 · hint d

This object indicates an arbitrary integer-value that uniquely identifies the flow monitor. Observe that the value assigned to a flow monitor does not necessarily persist across restarts or the removal-insertion of a physical entity supporting flow monitor(s).

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t

This object indicates a human-readable description for the flow monitor.

FlowMetricsThis textual convention denotes an enumerated integer-value that represents a set of metrics: 'mdi' This set of metrics consists of the Media Delivery Index (MDI) [RFC4445] 'rtp' This set of metrics consists of data similar to that computed and sent by a RTP client in a RTCP receiver report [RFC3550]. 'ipCbr' This set of metrics complements MDI, measuring the notion of Media Rate Variation (MRV).Reference: H. Schulzrinne, S. Casner, R. Fredrick, and V. Jacobson, 'RTP: A Transport Protocol for Real-Time Applications', RFC-3550, July 2003. J. Welch and J. Clark, 'A Proposed Media Delivery Index (MDI)', RFC-4445, APril 2006. · BITS

This object indicates the capabilities of the flow monitor. Specifically, the value of this column indicates a '1' for each set of flow metrics the flow monitor is capable of measuring.

Gauge32 · traffic flows

This object indicates the number of traffic flows currently monitored by the flow monitor.

FlowMonitorConditionsProfileOrZeroThis textual convention serves as an extension of the FlowMonitorConditionsProfile textual convention, which permits the value '0'. The use of the value '0' is specific to an object, thus requiring the descriptive text associated with the object to describe the semantics of its use. · Unsigned32 · hint d

This object indicates the conditions profile that contains the descriptions of the standing conditions monitored for the flow monitor. If the flow monitor does not have an associated conditions profile, then the value of this column must be zero.

FlowMonitorConditionsThis textual convention denotes a octet string-value that represents the standing conditions associated with an entity, such as a flow monitor a traffic flow. Each bit in the string corresponds to a single standing condition. The device should present a description of the standing condition in the cfmConditionTable, which uniquely identifies such a description by the following tuple: [cfmConditionProfile, cfmConditionId] where cfmConditionProfile uniquely identifies the conditions profile containing the description and cfmConditionId corresponds to the bit position within the string. The figure below illustrates a representation of the string containing N octets: Octet 0 Octet N-1 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 +-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+ | |...| | +-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +- Condition 8(n-1) | | | | | | | | | | | | | | +--- Condition 8(n-1)+1 | | | | | | | | | | | | | +----- Condition 8(n-1)+2 | | | | | | | | | | | | +------- Condition 8(n-1)+3 | | | | | | | | | | | +--------- Condition 8(n-1)+4 | | | | | | | | | | +----------- Condition 8(n-1)+5 | | | | | | | | | +------------- Condition 8(n-1)+6 | | | | | | | | +--------------- Condition 8(n-1)+7 | | | | | | | | : | | | | | | | | : | | | | | | | +--------------------- Condition 0 | | | | | | +----------------------- Condition 1 | | | | | +------------------------- Condition 2 | | | | +--------------------------- Condition 3 | | | +----------------------------- Condition 4 | | +------------------------------- Condition 5 | +--------------------------------- Condition 6 +----------------------------------- Condition 7 SIZE (0..255) · OCTET STRING · hint 1x:

This object indicates the current standing conditions for the flow monitor. If the flow monitor does not have an associated conditions profile, then the value of this column must be the null string.

FlowMonitorConditionsThis textual convention denotes a octet string-value that represents the standing conditions associated with an entity, such as a flow monitor a traffic flow. Each bit in the string corresponds to a single standing condition. The device should present a description of the standing condition in the cfmConditionTable, which uniquely identifies such a description by the following tuple: [cfmConditionProfile, cfmConditionId] where cfmConditionProfile uniquely identifies the conditions profile containing the description and cfmConditionId corresponds to the bit position within the string. The figure below illustrates a representation of the string containing N octets: Octet 0 Octet N-1 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 +-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+ | |...| | +-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +- Condition 8(n-1) | | | | | | | | | | | | | | +--- Condition 8(n-1)+1 | | | | | | | | | | | | | +----- Condition 8(n-1)+2 | | | | | | | | | | | | +------- Condition 8(n-1)+3 | | | | | | | | | | | +--------- Condition 8(n-1)+4 | | | | | | | | | | +----------- Condition 8(n-1)+5 | | | | | | | | | +------------- Condition 8(n-1)+6 | | | | | | | | +--------------- Condition 8(n-1)+7 | | | | | | | | : | | | | | | | | : | | | | | | | +--------------------- Condition 0 | | | | | | +----------------------- Condition 1 | | | | | +------------------------- Condition 2 | | | | +--------------------------- Condition 3 | | | +----------------------------- Condition 4 | | +------------------------------- Condition 5 | +--------------------------------- Condition 6 +----------------------------------- Condition 7 SIZE (0..255) · OCTET STRING · hint 1x:

This object indicates the current alarm conditions for the flow monitor. If the flow monitor does not have an associated conditions profile, then the value of this column must be the null string.

CiscoAlarmSeverity1 = cleared2 = indeterminate3 = critical4 = major5 = minor6 = warning7 = infoRepresents the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities, except that info(7) is added. cleared(1) - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate(2) - Indicates that the severity level cannot be determined. critical(3) - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major(4) - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor(5) - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning(6) - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info(7) - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.Reference: ITU-X.733 · Integer32

This object indicates the high severity alarm condition currently raised by the flow monitor and the traffic flows monitored by the flow monitor. If no alarm is raised for the flow monitor and the traffic flows monitored for the flow monitor, then the value of this column is 'cleared'.

Gauge32 · alarms

This object indicates the number of alarm conditions with a critical severity currently raised for traffic flows monitored by the flow monitor.

Gauge32 · alarms

This object indicates the number of alarm conditions with a major severity currently raised for traffic flows monitored by the flow monitor.

Gauge32 · alarms

This object indicates the number of alarm conditions with a minor severity currently raised for traffic flows monitored by the flow monitor.

Gauge32 · alarms

This object indicates the number of alarm conditions with a warning severity currently raised for traffic flows monitored by the flow monitor.

Gauge32 · alarms

This object indicates the number of alarm conditions with a informational severity currently raised for traffic flows monitored by the flow monitor.

FlowIdentifierThis textual convention denotes an arbitrary integer-value that uniquely identifies a traffic flow within the scope of the flow monitor that collects data and periodically computes metrics for the traffic flow. (1..4294967295) · Unsigned32 · hint d

This object indicates an arbitrary integer-value that uniquely identifies a traffic flow in the scope of the flow monitor that learned it. Observe that the value assigned to a flow does not necessarily persist across restarts or the removal-insertion of a physical entity supporting flow monitor(s).

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t

This object indicates a human-readable description of the traffic flow.

RowPointerRepresents a pointer to a conceptual row. The value is the name of the instance of the first accessible columnar object in the conceptual row. For example, ifIndex.3 would point to the 3rd row in the ifTable (note that if ifIndex were not-accessible, then ifDescr.3 would be used instead). · OBJECT IDENTIFIER

This object indicates a reference to a row in another table containing additional data relating to the traffic flow.

TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks

This object indicates the value of sysUpTime when the row was created.

TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks

This object indicates the value of sysUpTime on the most recent occasion at which any one or more of counters associated with the traffic flow suffered a discontinuity (e.g., process restart or failover event).

Unsigned32 · seconds

This object indicates the expiration interval for the traffic flow. If the flow monitor receives no packets for the traffic flow in this interval, then it expires the flow; that is, it stops monitoring the traffic and removes the corresponding row from the cfmFlowTable. If this column is '0', then the traffic flow was statically configured (as opposed to dynamically learned) and it will never expire.

INTEGER1 = unknown2 = ingress3 = egress · Integer32

This object indicates the direction of the traffic flow where the flow monitor collects data: 'unknown' The SNMP entity does not know the direction of the traffic flow at the point the flow monitor collects data. 'ingress' The flow monitor collects data at the point where the traffic flow enters the devices 'egress' The flow monitor collects data at the point where the traffic flow leaves the device.

INTEGER1 = enabled2 = disabled3 = expire · Integer32

This object specifies the desired state of the traffic flow: 'enabled' The corresponding flow monitor is collecting data and computing metrics for the traffic flow. 'disabled' The corresponding flow monitor is not collecting data or computing metrics for the traffic flow. As long as a traffic flow remains in this state, the flow monitor will not expire the traffic flow. 'expire' When this column is set to this value, it forces the traffic flow to expire. It is not possible to return this value in a response to a retrieval operation.

INTEGER1 = enabled2 = disabled · Integer32

This object indicates the operational state of the traffic flow: 'enabled' The corresponding flow monitor is actively monitoring the traffic flow. 'disabled' The corresponding flow monitor is neither collecting data, nor computing metrics for the traffic flow.

FlowPointType1 = other2 = unknown3 = none4 = interface5 = dot1qVlanThis textual convention denotes an enumerated integer-value that represents a point at which a flow monitor collects data for a traffic flow: 'other' The implementation of the MIB module using this textual convention does not recognize the flow point. 'unknown' The device is unable to ascertain the point at which the flow monitor collects data for the traffic flow. 'none' There is no point at which the flow monitor collects data for the traffic flow. 'interface' The flow point is an interface represented by a row in the ifTable (defined by the IF-MIB [RFC2863]. 'dot1qVlan' The flow point is an IEEE 802.1q VLAN represented by a row in the ifTable (defined by the IF-MIB [RFC2863]) and a tag representing the VLAN. With the exception of the values 'unknown' and 'none', each definition of a concrete FlowPointType value MUST have a corresponding textual convention for use with the particular type of flow point. To support future extensions, a MIB module SHOULD NOT sub-type the FlowPointType textual convention in an object type definition. However, a compliance statement MAY sub-type it in order to require only a subset of the flow point types for a compliant implementation. Implementations must ensure that FlowPointType objects and any dependent objects (e.g., FlowPointIdentifier objects) are consistent. For example, an implementation must respond with an 'inconsistentValue' error if an attempt is made to modify a FlowPointType object without changing the corresponding FlowPointIdentifier object.Reference: K. McCloghrie and F. Kastenholz, 'The Interfaces Group MIB', RFC-2863, June 2000. · Integer32

This object indicates the type of port that receives the traffic for this traffic flow.

FlowPointIdentifierThis textual convention denotes an octet string-value that identifies a point at which a flow monitor collects data for a traffic flow. An implementation MUST ALWAYS interpret a FlowPointIdentifier value within the context of a FlowPointType value. Every use of the FlowPointIdentifier textual convention requires the specification of a FlowPointType object to provide the context. A MIB module SHOULD logically register the FlowPointType object before the FlowPointIdentifier object(s). The value of a FlowPointIdentifier object MUST BE the null string if the value of the FlowPointType object providing the context is 'unknown' or 'none'. Implementations must ensure that a FlowPointIdentifier object remains consistent with the FlowPointType object providing the context. For example, an implementation must respond with an 'inconsistentValue' error if an attempt is made to modify a FlowPointIdentifier object without changing the corresponding FlowPointType object. SIZE (0..255) · OCTET STRING · hint 1x:

This object identifies the port that receives the traffic for this traffic flow.

FlowPointType1 = other2 = unknown3 = none4 = interface5 = dot1qVlanThis textual convention denotes an enumerated integer-value that represents a point at which a flow monitor collects data for a traffic flow: 'other' The implementation of the MIB module using this textual convention does not recognize the flow point. 'unknown' The device is unable to ascertain the point at which the flow monitor collects data for the traffic flow. 'none' There is no point at which the flow monitor collects data for the traffic flow. 'interface' The flow point is an interface represented by a row in the ifTable (defined by the IF-MIB [RFC2863]. 'dot1qVlan' The flow point is an IEEE 802.1q VLAN represented by a row in the ifTable (defined by the IF-MIB [RFC2863]) and a tag representing the VLAN. With the exception of the values 'unknown' and 'none', each definition of a concrete FlowPointType value MUST have a corresponding textual convention for use with the particular type of flow point. To support future extensions, a MIB module SHOULD NOT sub-type the FlowPointType textual convention in an object type definition. However, a compliance statement MAY sub-type it in order to require only a subset of the flow point types for a compliant implementation. Implementations must ensure that FlowPointType objects and any dependent objects (e.g., FlowPointIdentifier objects) are consistent. For example, an implementation must respond with an 'inconsistentValue' error if an attempt is made to modify a FlowPointType object without changing the corresponding FlowPointIdentifier object.Reference: K. McCloghrie and F. Kastenholz, 'The Interfaces Group MIB', RFC-2863, June 2000. · Integer32

This object indicates the type of port that transmits the traffic for this traffic flow.

FlowPointIdentifierThis textual convention denotes an octet string-value that identifies a point at which a flow monitor collects data for a traffic flow. An implementation MUST ALWAYS interpret a FlowPointIdentifier value within the context of a FlowPointType value. Every use of the FlowPointIdentifier textual convention requires the specification of a FlowPointType object to provide the context. A MIB module SHOULD logically register the FlowPointType object before the FlowPointIdentifier object(s). The value of a FlowPointIdentifier object MUST BE the null string if the value of the FlowPointType object providing the context is 'unknown' or 'none'. Implementations must ensure that a FlowPointIdentifier object remains consistent with the FlowPointType object providing the context. For example, an implementation must respond with an 'inconsistentValue' error if an attempt is made to modify a FlowPointIdentifier object without changing the corresponding FlowPointType object. SIZE (0..255) · OCTET STRING · hint 1x:

This object identifies the port that transmits the traffic for this traffic flow.

RowPointerRepresents a pointer to a conceptual row. The value is the name of the instance of the first accessible columnar object in the conceptual row. For example, ifIndex.3 would point to the 3rd row in the ifTable (note that if ifIndex were not-accessible, then ifDescr.3 would be used instead). · OBJECT IDENTIFIER

This object indicates a reference to a row in another table containing additional data relating to the corresponding traffic flow.

VlanIdThe VLAN-ID that uniquely identifies a VLAN. This is the 12-bit VLAN-ID used in the VLAN Tag header. The range is defined by the REFERENCEd specification.Reference: IEEE Std 802.1Q 2003 Edition, Virtual Bridged Local Area Networks. (1..4094) · Integer32 · hint d

This object indicates the tag associated with the VLAN carrying the corresponding traffic flow.

Layer2CosAn integer that is in the range of the layer 2 CoS values. It corresponds to the IEEE 802.1P CoS value which defines eight (2^3) user priority levels. Note: the IEEE 802.1P has been merged into IEEE 802.1D.Reference: IEEE 802.1D, 2004 Edition, Annex G User priorities and traffic classes. (0..7) · Integer32

This object indicates the layer 2 COS assigned to the corresponding traffic flow.

RowPointerRepresents a pointer to a conceptual row. The value is the name of the instance of the first accessible columnar object in the conceptual row. For example, ifIndex.3 would point to the 3rd row in the ifTable (note that if ifIndex were not-accessible, then ifDescr.3 would be used instead). · OBJECT IDENTIFIER

This object indicates a reference to a row in another table containing additional data relating to the corresponding traffic flow.

InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address. unknown(0) An unknown address type. This value MUST be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below. ipv4(1) An IPv4 address as defined by the InetAddressIPv4 textual convention. ipv6(2) An IPv6 address as defined by the InetAddressIPv6 textual convention. ipv4z(3) A non-global IPv4 address including a zone index as defined by the InetAddressIPv4z textual convention. ipv6z(4) A non-global IPv6 address including a zone index as defined by the InetAddressIPv6z textual convention. dns(16) A DNS domain name as defined by the InetAddressDNS textual convention. Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType. To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation. Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32

This object indicates the type of IP address indicated by the corresponding instances of cfmFlowIpAddrSrc and cfmFlowIpAddrDst.

InetAddressDenotes a generic Internet address. An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row. The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error. When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING

This object indicates the source IP address of the corresponding traffic flow.

InetAddressDenotes a generic Internet address. An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row. The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error. When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING

This object indicates the destination IP address of the corresponding traffic flow.

BITS

This object indicates whether the corresponding instances of cfmFlowIpTrafficClass and cfmFlowIpHopLimit are valid.

Unsigned32 (0..255)

Reference: J. Postel, 'Internet Protocol', RFC-791, September 1981. J. Deering and R. Hinden, 'Internet Protocol, Version 6 (IPv6) Specification', RFC-2460, December 1998.

This object indicates the traffic class of the corresponding traffic flow. If version 4 of the IP carries the traffic flow, then the value of this column corresponds to the 'Type of Service' field of the IP header contained by packets in the traffic flow. If version 6 of the IP carries the traffic flow, then the value of this column corresponds to the '' field of the IP header contained by packets in the traffic flow. The value of this column is valid only if the 'trafficClass' bit of the corresponding instance of cfmFlowIpValid is '1'.

Unsigned32 (0..255)

Reference: J. Postel, 'Internet Protocol', RFC-791, September 1981. J. Deering and R. Hinden, 'Internet Protocol, Version 6 (IPv6) Specification', RFC-2460, December 1998.

This object indicates the hop limit of the corresponding traffic flow. If version 4 of the IP carries the traffic flow, then the value of this column corresponds to the 'Time to Live' field of the IP header contained by packets in the traffic flow (as observed by the flow monitor). If version 6 of the IP carries the traffic flow, then the value of this column corresponds to the 'Hop Limit' field of the IP header contained by packets in the traffic flow (as observed by the flow monitor). The value of this column is valid only if the 'hopLimit' bit of the corresponding instance of cfmFlowIpValid is '1'.

RowPointerRepresents a pointer to a conceptual row. The value is the name of the instance of the first accessible columnar object in the conceptual row. For example, ifIndex.3 would point to the 3rd row in the ifTable (note that if ifIndex were not-accessible, then ifDescr.3 would be used instead). · OBJECT IDENTIFIER

This object indicates a reference to a row in another table containing additional data relating to the corresponding traffic flow.

InetPortNumberRepresents a 16 bit port number of an Internet transport layer protocol. Port numbers are assigned by IANA. A current list of all assignments is available from <http://www.iana.org/>. The value zero is object-specific and must be defined as part of the description of any object that uses this syntax. Examples of the usage of zero might include situations where a port number is unknown, or when the value zero is used as a wildcard in a filter.Reference: STD 6 (RFC 768), STD 7 (RFC 793) and RFC 2960 (0..65535) · Unsigned32 · hint d

This object indicates the source UDP port number of the corresponding traffic flow.

InetPortNumberRepresents a 16 bit port number of an Internet transport layer protocol. Port numbers are assigned by IANA. A current list of all assignments is available from <http://www.iana.org/>. The value zero is object-specific and must be defined as part of the description of any object that uses this syntax. Examples of the usage of zero might include situations where a port number is unknown, or when the value zero is used as a wildcard in a filter.Reference: STD 6 (RFC 768), STD 7 (RFC 793) and RFC 2960 (0..65535) · Unsigned32 · hint d

This object indicates the destination UDP port number of the corresponding traffic flow.

RowPointerRepresents a pointer to a conceptual row. The value is the name of the instance of the first accessible columnar object in the conceptual row. For example, ifIndex.3 would point to the 3rd row in the ifTable (note that if ifIndex were not-accessible, then ifDescr.3 would be used instead). · OBJECT IDENTIFIER

This object indicates a reference to a row in another table containing additional data relating to the corresponding traffic flow.

InetPortNumberRepresents a 16 bit port number of an Internet transport layer protocol. Port numbers are assigned by IANA. A current list of all assignments is available from <http://www.iana.org/>. The value zero is object-specific and must be defined as part of the description of any object that uses this syntax. Examples of the usage of zero might include situations where a port number is unknown, or when the value zero is used as a wildcard in a filter.Reference: STD 6 (RFC 768), STD 7 (RFC 793) and RFC 2960 (0..65535) · Unsigned32 · hint d

This object indicates the source TCP port number of the corresponding traffic flow.

InetPortNumberRepresents a 16 bit port number of an Internet transport layer protocol. Port numbers are assigned by IANA. A current list of all assignments is available from <http://www.iana.org/>. The value zero is object-specific and must be defined as part of the description of any object that uses this syntax. Examples of the usage of zero might include situations where a port number is unknown, or when the value zero is used as a wildcard in a filter.Reference: STD 6 (RFC 768), STD 7 (RFC 793) and RFC 2960 (0..65535) · Unsigned32 · hint d

This object indicates the destination TCP port number of the corresponding traffic flow.

RowPointerRepresents a pointer to a conceptual row. The value is the name of the instance of the first accessible columnar object in the conceptual row. For example, ifIndex.3 would point to the 3rd row in the ifTable (note that if ifIndex were not-accessible, then ifDescr.3 would be used instead). · OBJECT IDENTIFIER

This object indicates a reference to a row in another table containing additional data relating to the corresponding traffic flow.

Unsigned32 (0..3)

This object indicates the RTP version of the corresponding traffic flow.

Unsigned32

This object indicates the RTP synchronized source (SSRC) of the corresponding traffic flow.

Unsigned32 (0..127)

This object indicates the RTP payload type of the corresponding traffic flow.

FlowMetricsThis textual convention denotes an enumerated integer-value that represents a set of metrics: 'mdi' This set of metrics consists of the Media Delivery Index (MDI) [RFC4445] 'rtp' This set of metrics consists of data similar to that computed and sent by a RTP client in a RTCP receiver report [RFC3550]. 'ipCbr' This set of metrics complements MDI, measuring the notion of Media Rate Variation (MRV).Reference: H. Schulzrinne, S. Casner, R. Fredrick, and V. Jacobson, 'RTP: A Transport Protocol for Real-Time Applications', RFC-3550, July 2003. J. Welch and J. Clark, 'A Proposed Media Delivery Index (MDI)', RFC-4445, APril 2006. · BITS

This object indicates the metrics collected by the corresponding flow monitor for the corresponding traffic flow.

Unsigned32 (1..3600) · seconds

This object indicates the length of the measurement interval for the corresponding traffic flow. The flow monitor computes the collected metrics for the corresponding traffic flow with a frequency equal to the inverse of the value of this column.

Unsigned32 · intervals

This object indicates the maximum number of measurement intervals for which the corresponding flow monitor maintains metrics for the corresponding traffic flow. If the value of this column is '0', then the corresponding flow monitor does not maintain historical metrics for the corresponding traffic flow.

Gauge32 · seconds

This object indicates the time that has elapsed since the beginning of the current measurement interval.

Gauge32 · intervals

This object indicates the number of measurement intervals for which data has been collected.

Gauge32 · intervals

This object indicates the number of measurement intervals in the set of collected measurement intervals that contain invalid data.

FlowMonitorConditionsProfileOrZeroThis textual convention serves as an extension of the FlowMonitorConditionsProfile textual convention, which permits the value '0'. The use of the value '0' is specific to an object, thus requiring the descriptive text associated with the object to describe the semantics of its use. · Unsigned32 · hint d

This object indicates the conditions profile that contains the descriptions of the standing conditions monitored for the traffic flow. If the flow does not have an associated conditions profile, then the value of this column must be zero.

FlowMonitorConditionsThis textual convention denotes a octet string-value that represents the standing conditions associated with an entity, such as a flow monitor a traffic flow. Each bit in the string corresponds to a single standing condition. The device should present a description of the standing condition in the cfmConditionTable, which uniquely identifies such a description by the following tuple: [cfmConditionProfile, cfmConditionId] where cfmConditionProfile uniquely identifies the conditions profile containing the description and cfmConditionId corresponds to the bit position within the string. The figure below illustrates a representation of the string containing N octets: Octet 0 Octet N-1 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 +-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+ | |...| | +-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +- Condition 8(n-1) | | | | | | | | | | | | | | +--- Condition 8(n-1)+1 | | | | | | | | | | | | | +----- Condition 8(n-1)+2 | | | | | | | | | | | | +------- Condition 8(n-1)+3 | | | | | | | | | | | +--------- Condition 8(n-1)+4 | | | | | | | | | | +----------- Condition 8(n-1)+5 | | | | | | | | | +------------- Condition 8(n-1)+6 | | | | | | | | +--------------- Condition 8(n-1)+7 | | | | | | | | : | | | | | | | | : | | | | | | | +--------------------- Condition 0 | | | | | | +----------------------- Condition 1 | | | | | +------------------------- Condition 2 | | | | +--------------------------- Condition 3 | | | +----------------------------- Condition 4 | | +------------------------------- Condition 5 | +--------------------------------- Condition 6 +----------------------------------- Condition 7 SIZE (0..255) · OCTET STRING · hint 1x:

This object indicates the current standing conditions for the corresponding traffic flow. If the flow does not have an associated conditions profile, then the value of this column must be the null string.

FlowMonitorConditionsThis textual convention denotes a octet string-value that represents the standing conditions associated with an entity, such as a flow monitor a traffic flow. Each bit in the string corresponds to a single standing condition. The device should present a description of the standing condition in the cfmConditionTable, which uniquely identifies such a description by the following tuple: [cfmConditionProfile, cfmConditionId] where cfmConditionProfile uniquely identifies the conditions profile containing the description and cfmConditionId corresponds to the bit position within the string. The figure below illustrates a representation of the string containing N octets: Octet 0 Octet N-1 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 +-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+ | |...| | +-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +- Condition 8(n-1) | | | | | | | | | | | | | | +--- Condition 8(n-1)+1 | | | | | | | | | | | | | +----- Condition 8(n-1)+2 | | | | | | | | | | | | +------- Condition 8(n-1)+3 | | | | | | | | | | | +--------- Condition 8(n-1)+4 | | | | | | | | | | +----------- Condition 8(n-1)+5 | | | | | | | | | +------------- Condition 8(n-1)+6 | | | | | | | | +--------------- Condition 8(n-1)+7 | | | | | | | | : | | | | | | | | : | | | | | | | +--------------------- Condition 0 | | | | | | +----------------------- Condition 1 | | | | | +------------------------- Condition 2 | | | | +--------------------------- Condition 3 | | | +----------------------------- Condition 4 | | +------------------------------- Condition 5 | +--------------------------------- Condition 6 +----------------------------------- Condition 7 SIZE (0..255) · OCTET STRING · hint 1x:

This object indicates the current alarm conditions for the corresponding traffic flow. If the flow does not have an associated conditions profile, then the value of this column must be the null string.

CiscoAlarmSeverity1 = cleared2 = indeterminate3 = critical4 = major5 = minor6 = warning7 = infoRepresents the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities, except that info(7) is added. cleared(1) - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate(2) - Indicates that the severity level cannot be determined. critical(3) - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major(4) - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor(5) - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning(6) - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info(7) - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.Reference: ITU-X.733 · Integer32

This object indicates the highest severity alarm currently raised for the corresponding traffic flow. If no alarm is raised for the corresponding traffic flow, then the value of this column is 'cleared'.

Counter64 (0..18446744073709551615) · packets

This object indicates the total number of packets processed by the corresponding flow monitor for the corresponding traffic flow.

Counter64 (0..18446744073709551615) · octets

This object indicates the total number of octets contained by the packets processed by the corresponding flow monitor for the corresponding traffic flow.

FlowBitRateUnits1 = bps2 = kbps3 = mbps4 = gbpsThis textual convention denotes an enumerated integer-value that represents the units used when presenting a bit rate value. 'bps' The device presents the rate of a traffic flow in bits per second (bps). 'kbps' The device presents the rate of a traffic flow in Kbps. 'mbps' The device presents the rate of a traffic flow in Mbps. 'gbps' The device presents the rate of a traffic flow in Gbps. · Integer32

This object indicates the units for the corresponding instance of cfmFlowMetricsBitRate.

Gauge32

This object indicates the average bit rate at which the corresponding flow monitor is processing data for the corresponding traffic flow. This value is cumulative over the lifetime of the traffic flow.

Gauge32 · packets per second

This object indicates the average packet rate at which the corresponding flow monitor is processing data for the corresponding traffic flow. This value is cumulative over the lifetime of the traffic flow.

Unsigned32 (1..4294967295)

This object indicates the interval number identifying the measurement interval. The measurement interval identified by the value '1' represents the most recent measurement interval, and the interval identified by the value (n) represents the interval immediately preceding the interval identified by the value (n-1).

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object indicates whether the data for the measurement interval is valid.

TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks

This object indicates the value of sysUpTime when the measurement interval was captured.

FlowMonitorConditionsThis textual convention denotes a octet string-value that represents the standing conditions associated with an entity, such as a flow monitor a traffic flow. Each bit in the string corresponds to a single standing condition. The device should present a description of the standing condition in the cfmConditionTable, which uniquely identifies such a description by the following tuple: [cfmConditionProfile, cfmConditionId] where cfmConditionProfile uniquely identifies the conditions profile containing the description and cfmConditionId corresponds to the bit position within the string. The figure below illustrates a representation of the string containing N octets: Octet 0 Octet N-1 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 +-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+ | |...| | +-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +- Condition 8(n-1) | | | | | | | | | | | | | | +--- Condition 8(n-1)+1 | | | | | | | | | | | | | +----- Condition 8(n-1)+2 | | | | | | | | | | | | +------- Condition 8(n-1)+3 | | | | | | | | | | | +--------- Condition 8(n-1)+4 | | | | | | | | | | +----------- Condition 8(n-1)+5 | | | | | | | | | +------------- Condition 8(n-1)+6 | | | | | | | | +--------------- Condition 8(n-1)+7 | | | | | | | | : | | | | | | | | : | | | | | | | +--------------------- Condition 0 | | | | | | +----------------------- Condition 1 | | | | | +------------------------- Condition 2 | | | | +--------------------------- Condition 3 | | | +----------------------------- Condition 4 | | +------------------------------- Condition 5 | +--------------------------------- Condition 6 +----------------------------------- Condition 7 SIZE (0..255) · OCTET STRING · hint 1x:

This object indicates which standing conditions were asserted at least once during the measurement interval for the corresponding traffic flow.

FlowMonitorConditionsThis textual convention denotes a octet string-value that represents the standing conditions associated with an entity, such as a flow monitor a traffic flow. Each bit in the string corresponds to a single standing condition. The device should present a description of the standing condition in the cfmConditionTable, which uniquely identifies such a description by the following tuple: [cfmConditionProfile, cfmConditionId] where cfmConditionProfile uniquely identifies the conditions profile containing the description and cfmConditionId corresponds to the bit position within the string. The figure below illustrates a representation of the string containing N octets: Octet 0 Octet N-1 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 +-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+ | |...| | +-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +- Condition 8(n-1) | | | | | | | | | | | | | | +--- Condition 8(n-1)+1 | | | | | | | | | | | | | +----- Condition 8(n-1)+2 | | | | | | | | | | | | +------- Condition 8(n-1)+3 | | | | | | | | | | | +--------- Condition 8(n-1)+4 | | | | | | | | | | +----------- Condition 8(n-1)+5 | | | | | | | | | +------------- Condition 8(n-1)+6 | | | | | | | | +--------------- Condition 8(n-1)+7 | | | | | | | | : | | | | | | | | : | | | | | | | +--------------------- Condition 0 | | | | | | +----------------------- Condition 1 | | | | | +------------------------- Condition 2 | | | | +--------------------------- Condition 3 | | | +----------------------------- Condition 4 | | +------------------------------- Condition 5 | +--------------------------------- Condition 6 +----------------------------------- Condition 7 SIZE (0..255) · OCTET STRING · hint 1x:

This object indicates which alarm conditions were raised at least once during the measurement interval for the corresponding traffic flow.

CiscoAlarmSeverity1 = cleared2 = indeterminate3 = critical4 = major5 = minor6 = warning7 = infoRepresents the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities, except that info(7) is added. cleared(1) - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate(2) - Indicates that the severity level cannot be determined. critical(3) - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major(4) - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor(5) - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning(6) - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info(7) - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.Reference: ITU-X.733 · Integer32

This object indicates the highest severity alarm raised during the measurement interval for the corresponding traffic flow. If no alarm was raised during the measurement interval for the corresponding traffic flow, then the value of this column is 'cleared'.

ReportIntervalCountAn integer-value representing the value of a counter associated with the measurement taken during a previous report interval. An implementation supporting a history of N report intervals with IntervalCount(1) and IntervalCount(N) representing the most and least recent intervals, respectively, the following applies at the end of each report interval: - Discards the value of IntervalCount(N). - The value of IntervalCount(i) becomes that of IntervalCount(i-1) for N >= i > 1. - The value of IntervalCount(1) becomes that of CurrentCount. · Gauge32 · hint d · packets

This object indicates the number of packets processed by the corresponding flow monitor for the corresponding traffic flow during the measurement interval.

ReportIntervalCountAn integer-value representing the value of a counter associated with the measurement taken during a previous report interval. An implementation supporting a history of N report intervals with IntervalCount(1) and IntervalCount(N) representing the most and least recent intervals, respectively, the following applies at the end of each report interval: - Discards the value of IntervalCount(N). - The value of IntervalCount(i) becomes that of IntervalCount(i-1) for N >= i > 1. - The value of IntervalCount(1) becomes that of CurrentCount. · Gauge32 · hint d · octets

This object indicates the number of octets contained by the packets processed by the corresponding flow monitor for the corresponding traffic flow during the measurement interval.

FlowBitRateUnits1 = bps2 = kbps3 = mbps4 = gbpsThis textual convention denotes an enumerated integer-value that represents the units used when presenting a bit rate value. 'bps' The device presents the rate of a traffic flow in bits per second (bps). 'kbps' The device presents the rate of a traffic flow in Kbps. 'mbps' The device presents the rate of a traffic flow in Mbps. 'gbps' The device presents the rate of a traffic flow in Gbps. · Integer32

This object indicates the units for the corresponding instance of cfmFlowMetricsIntBitRate.

ReportIntervalCountAn integer-value representing the value of a counter associated with the measurement taken during a previous report interval. An implementation supporting a history of N report intervals with IntervalCount(1) and IntervalCount(N) representing the most and least recent intervals, respectively, the following applies at the end of each report interval: - Discards the value of IntervalCount(N). - The value of IntervalCount(i) becomes that of IntervalCount(i-1) for N >= i > 1. - The value of IntervalCount(1) becomes that of CurrentCount. · Gauge32 · hint d

This object indicates the bit rate at which the corresponding flow monitor processed data for the corresponding traffic flow during the measurement interval.

ReportIntervalCountAn integer-value representing the value of a counter associated with the measurement taken during a previous report interval. An implementation supporting a history of N report intervals with IntervalCount(1) and IntervalCount(N) representing the most and least recent intervals, respectively, the following applies at the end of each report interval: - Discards the value of IntervalCount(N). - The value of IntervalCount(i) becomes that of IntervalCount(i-1) for N >= i > 1. - The value of IntervalCount(1) becomes that of CurrentCount. · Gauge32 · hint d · packets per second

This object indicates the packet rate at which the corresponding flow monitor processed data for the corresponding traffic flow during the measurement interval.

FlowMonitorConditionsProfileThis textual convention denotes an arbitrary integer-value that uniquely identifies a conditions profile. A conditions profile is a set of descriptions of standing/alarm conditions that can be applied to an entity, such as a flow alarm or a traffic flow. (1..4294967295) · Unsigned32 · hint d

This object indicates an arbitrary integer-value that uniquely identifies the condition profile that contains the standing condition. Observe that the value assigned to a standing condition does not necessarily persist across restars.

FlowMonitorConditionIdentifierThis textual convention denotes an integer-value representing a standing/alarm condition within a conditions profile. It has a direct correspondence to the position of the bit representing the standing/alarm condition in a FlowMonitorConditions object. (0..2039) · Unsigned32 · hint d

This object indicates an arbitrary integer-value that uniquely identifies the condition within the scope of the profile. The value of this column corresponds to the bit position in a binary string-value representing the standing (or alarm) conditions for an entity, such as a flow monitor or traffic flow. Observe that the value assigned to a standing condition does not necessarily persist across restarts.

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t

This object indicates a human-readable description of the condition.

AutonomousTypeRepresents an independently extensible type identification value. It may, for example, indicate a particular sub-tree with further MIB definitions, or define a particular type of protocol or hardware. · OBJECT IDENTIFIER

This object indicates the monitored element used in determining the state of the standing condition.

INTEGER1 = other2 = boolean3 = risingThreshold4 = fallingThreshold5 = risingAndFallingThreshold · Integer32

This object indicates the type of condition: 'other' The implementation of the MIB does not recognize the condition described by this row. 'boolean' The value monitored only can have one of two values: 'false' or 'true'. In this case, the condition itself evaluates to 'true' if the value itself is 'true'. 'risingThreshold' The condition evaluates to 'true' if the current sample of the monitored value is greater than the rising threshold and the last sample is less than or equal to the rising threshold. 'fallingThreshold' The condition evaluates to 'true' if the current sample of the monitored value is less than the falling threshold and the last sample is greater than or equal to the falling threshold. 'risingAndFallingThreshold' The condition evaluates to 'true' if one of the two criteria is satisfied: 1) The current sample of the monitored value is greater than the rising threshold and the last sample is less than or equal to the rising threhsold. 2) The current sample of the monitored value is less than the falling threshold and the last sample is greater than or equal to the falling threshold.

FlowMetricScale1 = yocto2 = zepto3 = atto4 = femto5 = pico6 = nano7 = micro8 = milli9 = units10 = kilo11 = mega12 = giga13 = tera14 = exa15 = peta16 = zetta17 = yottaThis textual convention denotes an enumerated integer-value that represents an International System of Units (SI) prefix used as a scaling factor for fixed-point values: Prefix Scale Factor ========================= 'yocto' 10E-24 'zepto' 10E-21 'atto' 10E-18 'femto' 10E-15 'pico' 10E-12 'nano' 10E-9 'micro' 10E-6 'milli' 10E-3 'units' 10E0 'kilo' 10E3 'mega' 10E6 'giga' 10E9 'tera' 10E12 'exa' 10E15 'peta' 10E18 'zetta' 10E21 'yotta' 10E24 A MIB module may abstract a fixed-point value by defining three objects together: 1) A FlowMetricScale object, which indicates the scale of the value. 2) A FlowMetricPrecision object, which indicates the precision of the value. In the case that the value has a fractional portion, this object indicates the number of digits comprising the fractional portion. 3) A FlowMetricValue object, which indicates the value before scaling. · Integer32

This object indicates the scaling factor for the corresponding instance of cfmConditionThreshRise. This value of this column only has relevance if the corresponding instance of cfmConditionType is 'risingThreshold' or 'risingAndFallingThreshold'.

FlowMetricPrecisionThis textual convention denotes the precision or accuracy of a fixed-point value. A MIB module may abstract a fixed-point value by defining three objects together: 1) A FlowMetricScale object, which indicates the scale of the value. 2) A FlowMetricPrecision object, which indicates the precision of the value. In the case that the value has a fractional portion, this object indicates the number of digits comprising the fractional portion. 3) A FlowMetricValue object, which indicates the value before scaling. If an instance of an object of this type has a value in the range of 1 to 9, then it represents the precision of the associated value; that is, the number of decimal places in the fractional part of the associated value. For example, if the Media Loss Rate (MLR) computed for a traffic flow is 350.9E-6, then the FlowMetricScale object is 'micro', the FlowMetricPrecision object is 1, and the object indicating the value is 3509. If an instance of an object of this type has a value in the range of -8 to -1, then it represents the number of accurate digits in the associated value. For example, if the jitter measured for a traffic flow can range between -100,000 and 100,000 microseconds in 10 microsecond increments, with an accuracy of +/- 5 microseconds, the FlowMetricScale object is 'micro', the FlowMetricPrecision object is -2, and the object indicating the value has range of -100,000 to 100,000. (-8..-1 | 1..9) · Integer32 · hint d

This object indicates the precision for the corresponding instance of cfmConditionThreshRise. This value of this column only has relevance if the corresponding instance of cfmConditionType is 'risingThreshold' or 'risingAndFallingThreshold'.

FlowMetricValueThis textual convention denotes the value of a fixed-point value. A MIB module may abstract a fixed-point value by defining three objects together: 1) A FlowMetricScale object, which indicates the scale of the value. 2) A FlowMetricPrecision object, which indicates the precision of the value. In the case that the value has a fractional portion, this object indicates the number of digits comprising the fractional portion. 3) A FlowMetricValue object, which indicates the value before scaling. (-1000000000..1000000000) · Integer32 · hint d

This object indicates the value of the rising threshold. This value of this column only has relevance if the corresponding instance of cfmConditionType is 'risingThreshold' or 'risingAndFallingThreshold'.

FlowMetricScale1 = yocto2 = zepto3 = atto4 = femto5 = pico6 = nano7 = micro8 = milli9 = units10 = kilo11 = mega12 = giga13 = tera14 = exa15 = peta16 = zetta17 = yottaThis textual convention denotes an enumerated integer-value that represents an International System of Units (SI) prefix used as a scaling factor for fixed-point values: Prefix Scale Factor ========================= 'yocto' 10E-24 'zepto' 10E-21 'atto' 10E-18 'femto' 10E-15 'pico' 10E-12 'nano' 10E-9 'micro' 10E-6 'milli' 10E-3 'units' 10E0 'kilo' 10E3 'mega' 10E6 'giga' 10E9 'tera' 10E12 'exa' 10E15 'peta' 10E18 'zetta' 10E21 'yotta' 10E24 A MIB module may abstract a fixed-point value by defining three objects together: 1) A FlowMetricScale object, which indicates the scale of the value. 2) A FlowMetricPrecision object, which indicates the precision of the value. In the case that the value has a fractional portion, this object indicates the number of digits comprising the fractional portion. 3) A FlowMetricValue object, which indicates the value before scaling. · Integer32

This object indicates the scaling factor for the corresponding instance of cfmConditionThreshFall. The value of this column only has relevance if the corresponding instance of cfmConditionType is 'fallingThreshold' or 'risingAndFallingThreshold'.

FlowMetricPrecisionThis textual convention denotes the precision or accuracy of a fixed-point value. A MIB module may abstract a fixed-point value by defining three objects together: 1) A FlowMetricScale object, which indicates the scale of the value. 2) A FlowMetricPrecision object, which indicates the precision of the value. In the case that the value has a fractional portion, this object indicates the number of digits comprising the fractional portion. 3) A FlowMetricValue object, which indicates the value before scaling. If an instance of an object of this type has a value in the range of 1 to 9, then it represents the precision of the associated value; that is, the number of decimal places in the fractional part of the associated value. For example, if the Media Loss Rate (MLR) computed for a traffic flow is 350.9E-6, then the FlowMetricScale object is 'micro', the FlowMetricPrecision object is 1, and the object indicating the value is 3509. If an instance of an object of this type has a value in the range of -8 to -1, then it represents the number of accurate digits in the associated value. For example, if the jitter measured for a traffic flow can range between -100,000 and 100,000 microseconds in 10 microsecond increments, with an accuracy of +/- 5 microseconds, the FlowMetricScale object is 'micro', the FlowMetricPrecision object is -2, and the object indicating the value has range of -100,000 to 100,000. (-8..-1 | 1..9) · Integer32 · hint d

This object indicates the precision for the corresponding instance of cfmConditionThreshFall. The value of this column only has relevance if the corresponding instance of cfmConditionType is 'fallingThreshold' or 'risingAndFallingThreshold'.

FlowMetricValueThis textual convention denotes the value of a fixed-point value. A MIB module may abstract a fixed-point value by defining three objects together: 1) A FlowMetricScale object, which indicates the scale of the value. 2) A FlowMetricPrecision object, which indicates the precision of the value. In the case that the value has a fractional portion, this object indicates the number of digits comprising the fractional portion. 3) A FlowMetricValue object, which indicates the value before scaling. (-1000000000..1000000000) · Integer32 · hint d

This object indicates the value of the falling threshold. The value of this column only has relevance if the corresponding instance of cfmConditionType is 'fallingThreshold' or 'risingAndFallingThreshold'.

INTEGER1 = other2 = raw3 = slidingWindowAvg4 = expDecayingAvg · Integer32

This object indicates how the device samples the monitored value before determining whether to assert the condition: 'other' The implementation of the MIB does not recognize the how the device samples the monitored value. 'raw' The device samples the monitored value and uses this value to determine whether to assert the condition. 'slidingWindowAvg' The device samples the monitored value and maintains a average over a sliding window. It uses this value of this average to determine whether to assert the condition. The corresponding instance of cfmCOnditionSampleWindow indicates the length of the sliding window. 'slidingWindowAverage' The device samples the monitored value and maintains a exponentially decaying average over a sliding window. It uses this value of this average to determine whether to assert the condition. The corresponding instance of cfmCOnditionSampleWindow indicates the length of the sliding window.

Unsigned32

This object indicates the sample window used by the device to compute an exponentially decaying average in the case that the corresponding instance of cfmConditionSampleType is 'averaged'. The value of this column only has relevance if the corresponding instance of cfmConditionSampleWindow is 'slidingWindowAvg' or 'expDecayingAvg.

INTEGER1 = none2 = discrete3 = grouped · Integer32

This object indicates whether the device treats the standing condition as an alarm condition: 'none' The device does not treat the standing condition as an alarm condition. 'discrete' The device treats the standing condition as an alarm condition. 'grouped' The device aggregates the standing condition into an alarm group.

BITS

This object indicates the actions taken by the device when the alarm condition changes state: 'syslog' The device sends a syslog message. 'snmp' The device sends a cfmNotifyAlarm notification if and only if cfmNotifyEnable is set to 'true'. The value of this column only has relevance if the corresponding instance of cfmConditionAlarm is 'discrete'

CiscoAlarmSeverity1 = cleared2 = indeterminate3 = critical4 = major5 = minor6 = warning7 = infoRepresents the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities, except that info(7) is added. cleared(1) - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate(2) - Indicates that the severity level cannot be determined. critical(3) - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major(4) - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor(5) - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning(6) - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info(7) - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.Reference: ITU-X.733 · Integer32

This object indicates the severity of the alarm condition. The value of this column only have relevance if the corresponding instance of cfmConditionAlarm is 'discrete'.

FlowMonitorAlarmGroupIdentifierThis textual convention denotes an arbitrary integer-value that uniquely identifies an alarm group. An alarm group represents an alarm condition that the device raises if a configured number of traffic flows in a configured set of traffic flows asserts a given standing condition. (1..4294967295) · Unsigned32 · hint d

This object indicates the alarm group the device aggregates the standing condition into. The value of this column only has relevance if the corresponding instance of cfmConditionAlarm is 'grouped'.

FlowMonitorAlarmGroupIdentifierThis textual convention denotes an arbitrary integer-value that uniquely identifies an alarm group. An alarm group represents an alarm condition that the device raises if a configured number of traffic flows in a configured set of traffic flows asserts a given standing condition. (1..4294967295) · Unsigned32 · hint d

This object indicates an arbitrary integer-value that uniquely identifies the alarm group. Observe that the value assigned to an alarm group does not necessarily persist across restarts.

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t

This object indicates a human-readable description of the alarm group.

FlowMonitorConditionsProfileThis textual convention denotes an arbitrary integer-value that uniquely identifies a conditions profile. A conditions profile is a set of descriptions of standing/alarm conditions that can be applied to an entity, such as a flow alarm or a traffic flow. (1..4294967295) · Unsigned32 · hint d

This object indicates the conditions profile that contains the description of the standing profile aggregated by the alarm group.

FlowMonitorConditionIdentifierThis textual convention denotes an integer-value representing a standing/alarm condition within a conditions profile. It has a direct correspondence to the position of the bit representing the standing/alarm condition in a FlowMonitorConditions object. (0..2039) · Unsigned32 · hint d

This object indicates the standing condition aggregated by the alarm group.

FlowSetIdentifierThis textual convention denotes an arbitrary integer-value that uniquely identifies a set of traffic flows. (1..4294967295) · Unsigned32 · hint d

This object indicates the set of traffic flows aggregated by the alarm group.

Gauge32 · traffic flows

This object indicates the number of traffic flows in the set of traffic flows indicated by the corresponding instance of cfmAlarmGroupFlowSet.

INTEGER1 = other2 = flows3 = percent · Integer32

This object indicates the units for the corresponding instance of cfmAlarmGroupThreshold: 'other' The MIB implementation does not recognize the units in which the value of the corresponding instance of cfmAlarmGroupThreshold has been expressed. 'flows' The value of the corresponding instance of cfmAlarmGroupThreshold indicates a number of traffic flows. 'percent' The value of the corresponding instance of cfmAlarmGroupThreshold indicates a percentage of traffic flows.

Unsigned32

This object indicates a number of flows that must assert the standing condition indicated by the corresponding instance of cfmAlarmGroupCondition before raising an alarm. If the corresponding instance of cfmAlarmGroupThresholdUnits is 'percent', then the value of this column must be greater than or equal to zero and less than or equal to '100'.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object indicates whether the alarm group has raised an alarm.

Gauge32 · traffic flows

This object indicates the number of traffic flows currently asserting the standing condition aggregated by the alarm group.

FlowSetIdentifierThis textual convention denotes an arbitrary integer-value that uniquely identifies a set of traffic flows. (1..4294967295) · Unsigned32 · hint d

This object indicates an arbitrary integer-value that uniquely identifies the set of traffic flows that contains the traffic flow represented by the row. Observe that the value assigned to a flow set does not necessarily persist across restarts.

FlowMonitorIdentifierThis textual convention denotes an arbitrary integer-value that uniquely identifies a flow monitor. (1..4294967295) · Unsigned32 · hint d

This object identifies the flow monitor responsible for the traffic flow.

FlowIdentifierThis textual convention denotes an arbitrary integer-value that uniquely identifies a traffic flow within the scope of the flow monitor that collects data and periodically computes metrics for the traffic flow. (1..4294967295) · Unsigned32 · hint d

This object identifies the traffic flow.

Unsigned32 (1..4294967295)

This object indicates an arbitrary integer-value that uniquely identifies the event. Observe that the value assigned to a alarm history entry does not necessarily persist across restarts.

INTEGER1 = cleared2 = raised · Integer32

This object indicates the type of event: 'cleared' The event signaled an alarm condition transitioning to the cleared state. 'raised' The event signalled an alarm condition transitioning to the raised state.

RowPointerRepresents a pointer to a conceptual row. The value is the name of the instance of the first accessible columnar object in the conceptual row. For example, ifIndex.3 would point to the 3rd row in the ifTable (note that if ifIndex were not-accessible, then ifDescr.3 would be used instead). · OBJECT IDENTIFIER

This object indicates the entity that caused the event. If the alarm condition has an association with a flow monitor, then the value of this column is a row in the cfmFlowMonitorTable. If the alarm condition has an association with a traffic flow, then the value of this column is a row in the cfmFlowTable. If the alarm condition has an association with a alarm group, then the value of this column is a row in the cfmAlarmGroupTable.

FlowMonitorConditionsProfileThis textual convention denotes an arbitrary integer-value that uniquely identifies a conditions profile. A conditions profile is a set of descriptions of standing/alarm conditions that can be applied to an entity, such as a flow alarm or a traffic flow. (1..4294967295) · Unsigned32 · hint d

This object indicates the conditions profile containing the description of the alarm condition that changed state.

FlowMonitorConditionIdentifierThis textual convention denotes an integer-value representing a standing/alarm condition within a conditions profile. It has a direct correspondence to the position of the bit representing the standing/alarm condition in a FlowMonitorConditions object. (0..2039) · Unsigned32 · hint d

This object indicates the alarm condition that changed state.

CiscoAlarmSeverity1 = cleared2 = indeterminate3 = critical4 = major5 = minor6 = warning7 = infoRepresents the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities, except that info(7) is added. cleared(1) - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate(2) - Indicates that the severity level cannot be determined. critical(3) - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major(4) - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor(5) - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning(6) - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info(7) - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.Reference: ITU-X.733 · Integer32

This object indicates the severity of the alarm condition that changed state.

TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks

This object indicates the value of sysUpTime when the alarm condition changed state. In the case the device updates standing/alarm conditions at the same time it captures a measurement interval, the value of this column should correlate with the corresponding value of cfmFlowMetricsIntTime. This assures that the EMS/NMS can easily correlate alarms with the metrics captured in the course of a measurement interval.