CloneProfilePointType

• Base type Enumeration

This textual convention represents a point at which a clone profile sends out the cloned flows: 'other' The implementation of the MIB module using this textual convention does not recognize the profile point. 'unknown' The device is unable to ascertain the point at which the clone profile is sending the cloned traffic flow out. 'none' There is no point at which the clone profile can send cloned flows out. 'interface' The profile point is an interface represented by a row in the ifTable (defined by the IF-MIB [RFC2863]. With the exception of the values 'unknown' and 'none', each definition of a concrete CloneProfilePointType value MUST have a corresponding textual convention for use with the particular type of profile point. To support future extensions, a MIB module SHOULD NOT sub-type the CloneProfilePointType textual convention in an object type definition. However, a compliance statement MAY sub-type it in order to require only a subset of the profile point types for a compliant implementation. Implementations must ensure that CloneProfilePointType objects and any dependent objects (e.g., CloneProfilePointIdentifier objects) are consistent. For example, an implementation must respond with an 'inconsistentValue' error if an attempt is made to modify a CloneProfilePointType object without changing the corresponding CloneProfilePointIdentifier object.