Indicator of whether this peer connection supports priority.
When priority is configured for the remote peer,
DLSw+ will automatically activate four TCP connections to that
remote peer (ports 2065, 1981, 1982, and 1983). Priority only
needs to be configured if you need to prioritize between SNA
and NetBIOS, or within SNA by LOCADDR or MAC/SAP pair
(known as SAP prioritization). In addition, this granular packet
classification is only possible when TCP encapsulation is selected
for a specific remote peer. By default DLSw+ assigns certain
traffic to specific TCP ports.
Parsed from file CISCO-DLSW-EXT-MIB.mib
Module: CISCO-DLSW-EXT-MIB
Indicator of whether this peer connection supports priority.
When priority is configured for the remote peer,
DLSw+ will automatically activate four TCP connections to that
remote peer (ports 2065, 1981, 1982, and 1983). Priority only
needs to be configured if you need to prioritize between SNA
and NetBIOS, or within SNA by LOCADDR or MAC/SAP pair
(known as SAP prioritization). In addition, this granular packet
classification is only possible when TCP encapsulation is selected
for a specific remote peer. By default DLSw+ assigns certain
traffic to specific TCP ports.
cdeTConnConfigPriority OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Indicator of whether this peer connection supports priority.
When priority is configured for the remote peer,
DLSw+ will automatically activate four TCP connections to that
remote peer (ports 2065, 1981, 1982, and 1983). Priority only
needs to be configured if you need to prioritize between SNA
and NetBIOS, or within SNA by LOCADDR or MAC/SAP pair
(known as SAP prioritization). In addition, this granular packet
classification is only possible when TCP encapsulation is selected
for a specific remote peer. By default DLSw+ assigns certain
traffic to specific TCP ports."
DEFVAL { false }
View at oid-info.com
Indicator of whether this peer connection supports priority.
When priority is configured for the remote peer,
DLSw+ will automatically activate four TCP connections to that
remote peer (ports 2065, 1981, 1982, and 1983). Priority only
needs to be configured if you need to prioritize between SNA
and NetBIOS, or within SNA by LOCADDR or MAC/SAP pair
(known as SAP prioritization). In addition, this granular packet
classification is only possible when TCP encapsulation is selected
for a specific remote peer. By default DLSw+ assigns certain
traffic to specific TCP ports.
Parsed from file CISCO-DLSW-EXT-MIB.my.txt
Company: None
Module: CISCO-DLSW-EXT-MIB
Indicator of whether this peer connection supports priority.
When priority is configured for the remote peer,
DLSw+ will automatically activate four TCP connections to that
remote peer (ports 2065, 1981, 1982, and 1983). Priority only
needs to be configured if you need to prioritize between SNA
and NetBIOS, or within SNA by LOCADDR or MAC/SAP pair
(known as SAP prioritization). In addition, this granular packet
classification is only possible when TCP encapsulation is selected
for a specific remote peer. By default DLSw+ assigns certain
traffic to specific TCP ports.
cdeTConnConfigPriority OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "Indicator of whether this peer connection supports priority. When priority is configured for the remote peer, DLSw+ will automatically activate four TCP connections to that remote peer (ports 2065, 1981, 1982, and 1983). Priority only needs to be configured if you need to prioritize between SNA and NetBIOS, or within SNA by LOCADDR or MAC/SAP pair (known as SAP prioritization). In addition, this granular packet classification is only possible when TCP encapsulation is selected for a specific remote peer. By default DLSw+ assigns certain traffic to specific TCP ports." DEFVAL { false } ::= { cdeTConnConfigEntry 10 }
cdeTConnConfigPriority OBJECT-TYPE SYNTAX TruthValue ACCESS read-write STATUS mandatory DESCRIPTION "Indicator of whether this peer connection supports priority. When priority is configured for the remote peer, DLSw+ will automatically activate four TCP connections to that remote peer (ports 2065, 1981, 1982, and 1983). Priority only needs to be configured if you need to prioritize between SNA and NetBIOS, or within SNA by LOCADDR or MAC/SAP pair (known as SAP prioritization). In addition, this granular packet classification is only possible when TCP encapsulation is selected for a specific remote peer. By default DLSw+ assigns certain traffic to specific TCP ports." DEFVAL { false } ::= { cdeTConnConfigEntry 10 }
Automatically extracted from Cisco "SNMP v2 MIBs".
cdeTConnConfigPriority OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "Indicator of whether this peer connection supports priority. When priority is configured for the remote peer, DLSw+ will automatically activate four TCP connections to that remote peer (ports 2065, 1981, 1982, and 1983). Priority only needs to be configured if you need to prioritize between SNA and NetBIOS, or within SNA by LOCADDR or MAC/SAP pair (known as SAP prioritization). In addition, this granular packet classification is only possible when TCP encapsulation is selected for a specific remote peer. By default DLSw+ assigns certain traffic to specific TCP ports." DEFVAL { false } ::= { cdeTConnConfigEntry 10 }
cdeTConnConfigPriority OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "Indicator of whether this peer connection supports priority. When priority is configured for the remote peer, DLSw+ will automatically activate four TCP connections to that remote peer (ports 2065, 1981, 1982, and 1983). Priority only needs to be configured if you need to prioritize between SNA and NetBIOS, or within SNA by LOCADDR or MAC/SAP pair (known as SAP prioritization). In addition, this granular packet classification is only possible when TCP encapsulation is selected for a specific remote peer. By default DLSw+ assigns certain traffic to specific TCP ports." DEFVAL { false } ::= { cdeTConnConfigEntry 10 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.74.1.3.1.1.1 | cdeTConnConfigTDomainType | 0 | 0 | The type of DLSw encapsulation in use on this peer connection. |
| 1.3.6.1.4.1.9.9.74.1.3.1.1.2 | cdeTConnConfigLocalAck | 0 | 0 | Reflects whether the peer connection is locally acknowledged. Locally acknoledgement means terminating the DLC connections at the… |
| 1.3.6.1.4.1.9.9.74.1.3.1.1.3 | cdeTConnConfigCost | 0 | 0 | The cost associated with the transport connection, assigned to this conceptual row representing a peer. If an end station can be … |
| 1.3.6.1.4.1.9.9.74.1.3.1.1.4 | cdeTConnConfigLFSize | 0 | 0 | The Largest Frame Size associated with the transport connection. In other words its the largest size of the INFO field (including… |
| 1.3.6.1.4.1.9.9.74.1.3.1.1.5 | cdeTConnConfigKeepaliveInterval | 0 | 0 | The amount of time between keepalive messages on a transport connection. The keepalive parameter refers to how often DLSw peers se… |
| 1.3.6.1.4.1.9.9.74.1.3.1.1.6 | cdeTConnConfigBackup | 0 | 0 | This variable indicates if this peer is defined as a backup to an existing peer. A backup peer is used to provide an alternate p… |
| 1.3.6.1.4.1.9.9.74.1.3.1.1.7 | cdeTConnConfigBackupTAddr | 0 | 0 | The primary peer's IP address that this entry backs up. Valid only when ciscoDlswTConnConfigBackup is true. |
| 1.3.6.1.4.1.9.9.74.1.3.1.1.8 | cdeTConnConfigBackupLinger | 0 | 0 | This variable indicates whether the backup peer will remain connected after the primary peer connection has been re-established. T… |
| 1.3.6.1.4.1.9.9.74.1.3.1.1.9 | cdeTConnConfigBackupLingerInterval | 0 | 0 | This variable indicates the length of time the backup peer remains connected after the primary peer connection has been re-establ… |
| 1.3.6.1.4.1.9.9.74.1.3.1.1.11 | cdeTConnConfigDestMac | 0 | 0 | Permits the peer connection to be established only when there is an explorer frame destined for the specified 48-bit MAC address… |
| 1.3.6.1.4.1.9.9.74.1.3.1.1.12 | cdeTConnConfigDynamic | 0 | 0 | Indicates the peer connection is to be established only when there is DLSw+ data to send. |
| 1.3.6.1.4.1.9.9.74.1.3.1.1.13 | cdeTConnConfigDynamicNoLlc | 0 | 0 | This variable indicates the length of time a dynamic peer remains connected after all LLC2 circuits are gone. |
| 1.3.6.1.4.1.9.9.74.1.3.1.1.14 | cdeTConnConfigDynamicInactivityInterval | 0 | 0 | Indicates the length of time a connection can be idle before closing the dynamic peer connection. If set to zero, the dynamic pe… |