An entry describing a NBAR application configured in PfR.
A peer SNMP entity may create an NBAR application entry by
setting an instance of cpfrNbarApplListRowStatus 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
NBAR application. In these cases, the system must
automatically create a row in the cpfrNbarApplListTable.
A peer SNMP entity may destroy a NBAR application by setting the
corresponding instance of cpfrNbarApplListRow Status 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 an NBAR application. In
these cases, the system must automatically destroy the
corresponding row in the cpfrNbarApplListTable.
The system automatically destroys rows when the system or
EMS/NMS destroys the corresponding entry in cpfrMatchEntry and
cpfrLearnListEntry.
An entry describing a NBAR application configured in PfR.
A peer SNMP entity may create an NBAR application entry by
setting an instance of cpfrNbarApplListRowStatus 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
NBAR application. In these cases, the system must
automatically create a row in the cpfrNbarApplListTable.
A peer SNMP entity may destroy a NBAR application by setting the
corresponding instance of cpfrNbarApplListRow Status 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 an NBAR application. In
these cases, the system must automatically destroy the
corresponding row in the cpfrNbarApplListTable.
The system automatically destroys rows when the system or
EMS/NMS destroys the corresponding entry in cpfrMatchEntry and
cpfrLearnListEntry.
cpfrNbarApplListEntry OBJECT-TYPE SYNTAX CpfrNbarApplListEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "An entry describing a NBAR application configured in PfR. A peer SNMP entity may create an NBAR application entry by setting an instance of cpfrNbarApplListRowStatus 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 NBAR application. In these cases, the system must automatically create a row in the cpfrNbarApplListTable. A peer SNMP entity may destroy a NBAR application by setting the corresponding instance of cpfrNbarApplListRow Status 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 an NBAR application. In these cases, the system must automatically destroy the corresponding row in the cpfrNbarApplListTable. The system automatically destroys rows when the system or EMS/NMS destroys the corresponding entry in cpfrMatchEntry and cpfrLearnListEntry." INDEX { cpfrNbarApplListName, cpfrNbarApplIndex } ::= { cpfrNbarApplListTable 1 }
cpfrNbarApplListEntry OBJECT-TYPE SYNTAX CpfrNbarApplListEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry describing a NBAR application configured in PfR. A peer SNMP entity may create an NBAR application entry by setting an instance of cpfrNbarApplListRowStatus 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 NBAR application. In these cases, the system must automatically create a row in the cpfrNbarApplListTable. A peer SNMP entity may destroy a NBAR application by setting the corresponding instance of cpfrNbarApplListRow Status 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 an NBAR application. In these cases, the system must automatically destroy the corresponding row in the cpfrNbarApplListTable. The system automatically destroys rows when the system or EMS/NMS destroys the corresponding entry in cpfrMatchEntry and cpfrLearnListEntry." INDEX { cpfrNbarApplListName, cpfrNbarApplIndex } ::= { cpfrNbarApplListTable 1 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.772.1.15.1.1 | cpfrNbarApplListName | 0 | 0 | This object indicates the name of a NBAR application list. |
| 1.3.6.1.4.1.9.9.772.1.15.1.2 | cpfrNbarApplIndex | 0 | 0 | This object indicates a unique arbitrary number identifying a specific protocol in a PfR NBAR Application List. |
| 1.3.6.1.4.1.9.9.772.1.15.1.3 | cpfrNbarApplListStorageType | 0 | 0 | This object specifies the memory realization of the row. The following columnar objects are allowed to be writable when the stora… |
| 1.3.6.1.4.1.9.9.772.1.15.1.4 | cpfrNbarApplListRowStatus | 0 | 0 | This object specifies the status of a NBAR application list. The following columnar objects must be valid in order to transition … |
| 1.3.6.1.4.1.9.9.772.1.15.1.5 | cpfrNbarApplPdIndex | 0 | 0 | This object indicates the application or protocol recognized by NBAR. The value of this object points to an entry in cnpdSupporte… |