An entry describing a match clause PfR uses.
A peer SNMP entity may create a match criterion by setting an
instance of cpfrMatchStatus to 'createAndWait' or 'createAndGo'.
Observe that an implementation that does not support these
option must specify these limitations in an agent capability
statement.
Other management entities (e.g., the local console) may create a
match criterion. In these cases, the system must automatically
create a row in the cpfrMatchTable.
A peer SNMP entity may destroy a match criterion by setting the
corresponding instance of cpfrMatchStatus to 'destroy'.
Observe that an implementation that does not support this
option must specify this limitation in an agent capability
statement.
Other management entities may destroy a match criterion. In
these cases, the system must automatically destroy the
corresponding row in the cpfrMatchTable.
The system automatically destroys a row when the system or
EMS/NMS destroys the corresponding entries in the cpfrMapTable.
An entry describing a match clause PfR uses.
A peer SNMP entity may create a match criterion by setting an
instance of cpfrMatchStatus to 'createAndWait' or 'createAndGo'.
Observe that an implementation that does not support these
option must specify these limitations in an agent capability
statement.
Other management entities (e.g., the local console) may create a
match criterion. In these cases, the system must automatically
create a row in the cpfrMatchTable.
A peer SNMP entity may destroy a match criterion by setting the
corresponding instance of cpfrMatchStatus to 'destroy'.
Observe that an implementation that does not support this
option must specify this limitation in an agent capability
statement.
Other management entities may destroy a match criterion. In
these cases, the system must automatically destroy the
corresponding row in the cpfrMatchTable.
The system automatically destroys a row when the system or
EMS/NMS destroys the corresponding entries in the cpfrMapTable.
cpfrMatchEntry OBJECT-TYPE SYNTAX CpfrMatchEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "An entry describing a match clause PfR uses. A peer SNMP entity may create a match criterion by setting an instance of cpfrMatchStatus to 'createAndWait' or 'createAndGo'. Observe that an implementation that does not support these option must specify these limitations in an agent capability statement. Other management entities (e.g., the local console) may create a match criterion. In these cases, the system must automatically create a row in the cpfrMatchTable. A peer SNMP entity may destroy a match criterion by setting the corresponding instance of cpfrMatchStatus to 'destroy'. Observe that an implementation that does not support this option must specify this limitation in an agent capability statement. Other management entities may destroy a match criterion. In these cases, the system must automatically destroy the corresponding row in the cpfrMatchTable. The system automatically destroys a row when the system or EMS/NMS destroys the corresponding entries in the cpfrMapTable." INDEX { cpfrMapIndex, cpfrMapPolicyIndex } ::= { cpfrMatchTable 1 }
cpfrMatchEntry OBJECT-TYPE SYNTAX CpfrMatchEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry describing a match clause PfR uses. A peer SNMP entity may create a match criterion by setting an instance of cpfrMatchStatus to 'createAndWait' or 'createAndGo'. Observe that an implementation that does not support these option must specify these limitations in an agent capability statement. Other management entities (e.g., the local console) may create a match criterion. In these cases, the system must automatically create a row in the cpfrMatchTable. A peer SNMP entity may destroy a match criterion by setting the corresponding instance of cpfrMatchStatus to 'destroy'. Observe that an implementation that does not support this option must specify this limitation in an agent capability statement. Other management entities may destroy a match criterion. In these cases, the system must automatically destroy the corresponding row in the cpfrMatchTable. The system automatically destroys a row when the system or EMS/NMS destroys the corresponding entries in the cpfrMapTable." INDEX { cpfrMapIndex, cpfrMapPolicyIndex } ::= { cpfrMatchTable 1 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.772.1.3.1.1 | cpfrMatchValid | 0 | 0 | This object specifies which of those objects are valid. When a user is configuring a match clause, the corresponding bit should … |
| 1.3.6.1.4.1.9.9.772.1.3.1.2 | cpfrMatchAddrAccessList | 0 | 0 | This object specifies the access list used to manually configure a traffic class that matches destination prefixes in an access l… |
| 1.3.6.1.4.1.9.9.772.1.3.1.3 | cpfrMatchAddrPrefixList | 0 | 0 | This object specifies the prefix list used to manually configure a traffic class that matches destination prefixes in a prefix li… |
| 1.3.6.1.4.1.9.9.772.1.3.1.4 | cpfrMatchAddrPrefixInside | 0 | 0 | This object specifies whether or not the prefixes learned by PfR are within the internal network. |
| 1.3.6.1.4.1.9.9.772.1.3.1.5 | cpfrMatchLearnMode | 0 | 0 | This object specifies the mode by which PfR should learn prefixes. 'Delay' PfR learns prefixes based on the highest delay. 'Inside'… |
| 1.3.6.1.4.1.9.9.772.1.3.1.6 | cpfrMatchLearnListName | 0 | 0 | This object specifies the learn list name used by PfR for learning prefixes. This object is valid when the corresponding cpfrMat… |
| 1.3.6.1.4.1.9.9.772.1.3.1.7 | cpfrMatchTCNbarListName | 0 | 0 | This object specifies that PfR is to profile traffic destined for prefixes defined in an IP prefix list that match one or more NB… |
| 1.3.6.1.4.1.9.9.772.1.3.1.8 | cpfrMatchTCNbarApplPfxList | 0 | 0 | This object specifies the prefix list to be used by PfR to filter traffic that is learned based on NBAR applications. |
| 1.3.6.1.4.1.9.9.772.1.3.1.9 | cpfrMatchTCPfxInside | 0 | 0 | This object specifies whether or not the prefixes filtered by the prefix list is inside the internal network. |