FlowPointType

• Base type Enumeration

This 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.