The flow control mechanism in use on this transport connection.
This value is undetermined (1) before the mode of flow control
can be established on a new transport connection (i.e., after
CapEx is sent but before Capex or other SSP control messages
have been received). Pacing (2) indicates that the standard
RFC 1795 pacing mechanism is in use. Other (3) may be either
the RFC 1434+ xBusy mechanism operating to a back-level DLSw,
or a vendor-specific flow control method. Whether it is xBusy
or not can be inferred from ciscoDlswTConnOperPartnerVersion.
Parsed from file CISCO-DLSW-MIB.mib
Module: CISCO-DLSW-MIB
The flow control mechanism in use on this transport connection.
This value is undetermined (1) before the mode of flow control
can be established on a new transport connection (i.e., after
CapEx is sent but before Capex or other SSP control messages
have been received). Pacing (2) indicates that the standard
RFC 1795 pacing mechanism is in use. Other (3) may be either
the RFC 1434+ xBusy mechanism operating to a back-level DLSw,
or a vendor-specific flow control method. Whether it is xBusy
or not can be inferred from ciscoDlswTConnOperPartnerVersion.
The flow control mechanism in use on this transport connection.
This value is undetermined (1) before the mode of flow control
can be established on a new transport connection (i.e., after
CapEx is sent but before Capex or other SSP control messages
have been received). Pacing (2) indicates that the standard
RFC 1795 pacing mechanism is in use. Other (3) may be either
the RFC 1434+ xBusy mechanism operating to a back-level DLSw,
or a vendor-specific flow control method. Whether it is xBusy
or not can be inferred from ciscoDlswTConnOperPartnerVersion.
Parsed from file CISCO-DLSW-MIB.my.txt
Company: None
Module: CISCO-DLSW-MIB
The flow control mechanism in use on this transport connection.
This value is undetermined (1) before the mode of flow control
can be established on a new transport connection (i.e., after
CapEx is sent but before Capex or other SSP control messages
have been received). Pacing (2) indicates that the standard
RFC 1795 pacing mechanism is in use. Other (3) may be either
the RFC 1434+ xBusy mechanism operating to a back-level DLSw,
or a vendor-specific flow control method. Whether it is xBusy
or not can be inferred from ciscoDlswTConnOperPartnerVersion.
ciscoDlswTConnOperFlowCntlMode OBJECT-TYPE SYNTAX INTEGER { undetermined (1), pacing (2), other (3) } MAX-ACCESS read-only STATUS current DESCRIPTION "The flow control mechanism in use on this transport connection. This value is undetermined (1) before the mode of flow control can be established on a new transport connection (i.e., after CapEx is sent but before Capex or other SSP control messages have been received). Pacing (2) indicates that the standard RFC 1795 pacing mechanism is in use. Other (3) may be either the RFC 1434+ xBusy mechanism operating to a back-level DLSw, or a vendor-specific flow control method. Whether it is xBusy or not can be inferred from ciscoDlswTConnOperPartnerVersion." ::= { ciscoDlswTConnOperEntry 8 }
ciscoDlswTConnOperFlowCntlMode OBJECT-TYPE SYNTAX INTEGER { undetermined(1), pacing(2), other(3) } ACCESS read-only STATUS mandatory DESCRIPTION "The flow control mechanism in use on this transport connection. This value is undetermined (1) before the mode of flow control can be established on a new transport connection (i.e., after CapEx is sent but before Capex or other SSP control messages have been received). Pacing (2) indicates that the standard RFC 1795 pacing mechanism is in use. Other (3) may be either the RFC 1434+ xBusy mechanism operating to a back-level DLSw, or a vendor-specific flow control method. Whether it is xBusy or not can be inferred from ciscoDlswTConnOperPartnerVersion." ::= { ciscoDlswTConnOperEntry 8 }
Vendor: Cisco
Module: CISCO-DLSW-MIB
[Automatically extracted from oidview.com]
ciscoDlswTConnOperFlowCntlMode OBJECT-TYPE SYNTAX INTEGER { undetermined (1), pacing (2), other (3) } MAX-ACCESS read-only STATUS current DESCRIPTION "The flow control mechanism in use on this transport connection. This value is undetermined (1) before the mode of flow control can be established on a new transport connection (i.e., after CapEx is sent but before Capex or other SSP control messages have been received). Pacing (2) indicates that the standard RFC 1795 pacing mechanism is in use. Other (3) may be either the RFC 1434+ xBusy mechanism operating to a back-level DLSw, or a vendor-specific flow control method. Whether it is xBusy or not can be inferred from ciscoDlswTConnOperPartnerVersion." ::= { ciscoDlswTConnOperEntry 8 }
ciscoDlswTConnOperFlowCntlMode OBJECT-TYPE SYNTAX INTEGER { undetermined (1), pacing (2), other (3) } MAX-ACCESS read-only STATUS current DESCRIPTION "The flow control mechanism in use on this transport connection. This value is undetermined (1) before the mode of flow control can be established on a new transport connection (i.e., after CapEx is sent but before Capex or other SSP control messages have been received). Pacing (2) indicates that the standard RFC 1795 pacing mechanism is in use. Other (3) may be either the RFC 1434+ xBusy mechanism operating to a back-level DLSw, or a vendor-specific flow control method. Whether it is xBusy or not can be inferred from ciscoDlswTConnOperPartnerVersion." ::= { ciscoDlswTConnOperEntry 8 }
OID | Name | Sub children | Sub Nodes Total | Description |
---|---|---|---|---|
1.3.6.1.4.1.9.10.9.1.2.3.1.1 | ciscoDlswTConnOperTDomain | 0 | 0 | The object identifier indicates the transport domain of this transport connection. |
1.3.6.1.4.1.9.10.9.1.2.3.1.2 | ciscoDlswTConnOperLocalTAddr | 0 | 0 | The local transport address for this transport connection. This value could be different from ciscoDlswTConnConfigLocalAddr, if t… |
1.3.6.1.4.1.9.10.9.1.2.3.1.3 | ciscoDlswTConnOperRemoteTAddr | 0 | 0 | The remote transport address of this transport connection. |
1.3.6.1.4.1.9.10.9.1.2.3.1.4 | ciscoDlswTConnOperEntryTime | 0 | 0 | The value of ciscoDlswUpTime when this transport connection conceptual row was created. |
1.3.6.1.4.1.9.10.9.1.2.3.1.5 | ciscoDlswTConnOperConnectTime | 0 | 0 | The value of ciscoDlswUpTime when this transport connection last entered the 'connected' state. A value of zero means this trans… |
1.3.6.1.4.1.9.10.9.1.2.3.1.6 | ciscoDlswTConnOperState | 0 | 0 | The state of this transport connection. The transport connection enters `connecting' state when DLSw makes a connection request … |
1.3.6.1.4.1.9.10.9.1.2.3.1.7 | ciscoDlswTConnOperConfigIndex | 0 | 0 | The value of ciscoDlswTConnConfigIndex of the ciscoDlswTConnConfigEntry that governs the configuration information used by this c… |
1.3.6.1.4.1.9.10.9.1.2.3.1.9 | ciscoDlswTConnOperPartnerVersion | 0 | 0 | This value identifies which version (first octet) and release (second octet) of the DLSw standard is supported by this partner DL… |
1.3.6.1.4.1.9.10.9.1.2.3.1.10 | ciscoDlswTConnOperPartnerVendorID | 0 | 0 | This value identifies the IEEE-assigned organizationally Unique Identifier (OUI) of the maker of this partner DLSw. This informa… |
1.3.6.1.4.1.9.10.9.1.2.3.1.11 | ciscoDlswTConnOperPartnerVersionStr | 0 | 0 | This value identifies the particular product version (e.g., product name, code level, fix level) of this partner DLSw. The format… |
1.3.6.1.4.1.9.10.9.1.2.3.1.12 | ciscoDlswTConnOperPartnerInitPacingWndw | 0 | 0 | The value of the partner initial receive pacing window. This is our initial send pacing window for all new circuits on this tran… |
1.3.6.1.4.1.9.10.9.1.2.3.1.13 | ciscoDlswTConnOperPartnerSapList | 0 | 0 | The Supported SAP List received in the capabilities exchange message from the partner DLSw. This list has the same format descri… |
1.3.6.1.4.1.9.10.9.1.2.3.1.14 | ciscoDlswTConnOperPartnerNBExcl | 0 | 0 | The value of true signifies that the NetBIOS names received from this partner in the NetBIOS name list in its capabilities exchan… |
1.3.6.1.4.1.9.10.9.1.2.3.1.15 | ciscoDlswTConnOperPartnerMacExcl | 0 | 0 | The value of true signifies that the MAC addresses received from this partner in the MAC address list in its capabilities exchang… |
1.3.6.1.4.1.9.10.9.1.2.3.1.16 | ciscoDlswTConnOperPartnerNBInfo | 0 | 0 | It is up to this DSLw whether to keep either none, some, or all of the NetBIOS name list that was received in the capabilities ex… |
1.3.6.1.4.1.9.10.9.1.2.3.1.17 | ciscoDlswTConnOperPartnerMacInfo | 0 | 0 | It is up to this DLSw whether to keep either none, some, or all of the MAC address list that was received in the capabilities exc… |
1.3.6.1.4.1.9.10.9.1.2.3.1.18 | ciscoDlswTConnOperDiscTime | 0 | 0 | The value of ciscoDlswUpTime when ciscoDlswTConnOperState last entered `disconnected' state. |
1.3.6.1.4.1.9.10.9.1.2.3.1.19 | ciscoDlswTConnOperDiscReason | 0 | 0 | This object signifies the reason that either prevented the transport connection from entering the connected state, or caused the … |
1.3.6.1.4.1.9.10.9.1.2.3.1.20 | ciscoDlswTConnOperDiscActiveCir | 0 | 0 | The number of circuits active (not in DISCONNECTED state) at the time the transport connection was last disconnected. This value … |
1.3.6.1.4.1.9.10.9.1.2.3.1.21 | ciscoDlswTConnOperInDataPkts | 0 | 0 | The number of Switch-to-Switch Protocol (SSP) messages of type DGRMFRAME, DATAFRAME, or INFOFRAME received on this transport conn… |
1.3.6.1.4.1.9.10.9.1.2.3.1.22 | ciscoDlswTConnOperOutDataPkts | 0 | 0 | The number of Switch-to-Switch Protocol (SSP) messages of type DGRMFRAME, DATAFRAME, or INFOFRAME transmitted on this transport c… |
1.3.6.1.4.1.9.10.9.1.2.3.1.23 | ciscoDlswTConnOperInDataOctets | 0 | 0 | The number octets in Switch-to-Switch Protocol (SSP) messages of type DGRMFRAME, DATAFRAME, or INFOFRAME received on this transpo… |
1.3.6.1.4.1.9.10.9.1.2.3.1.24 | ciscoDlswTConnOperOutDataOctets | 0 | 0 | The number octets in Switch-to-Switch Protocol (SSP) messages of type DGRMFRAME, DATAFRAME, or INFOFRAME transmitted on this tran… |
1.3.6.1.4.1.9.10.9.1.2.3.1.25 | ciscoDlswTConnOperInCntlPkts | 0 | 0 | The number of Switch-to-Switch Protocol (SSP) messages received on this transport connection which were not of type DGRMFRAME, DA… |
1.3.6.1.4.1.9.10.9.1.2.3.1.26 | ciscoDlswTConnOperOutCntlPkts | 0 | 0 | The number of Switch-to-Switch Protocol (SSP) messages of transmitted on this transport connection which were not of type DGRMFRA… |
1.3.6.1.4.1.9.10.9.1.2.3.1.27 | ciscoDlswTConnOperCURexSents | 0 | 0 | The number of CanUReach_ex messages sent on this transport connection. |
1.3.6.1.4.1.9.10.9.1.2.3.1.28 | ciscoDlswTConnOperICRexRcvds | 0 | 0 | The number of ICanReach_ex messages received on this transport connection. |
1.3.6.1.4.1.9.10.9.1.2.3.1.29 | ciscoDlswTConnOperCURexRcvds | 0 | 0 | The number of CanUReach_ex messages received on this transport connection. |
1.3.6.1.4.1.9.10.9.1.2.3.1.30 | ciscoDlswTConnOperICRexSents | 0 | 0 | The number of ICanReach_ex messages sent on this transport connection. |
1.3.6.1.4.1.9.10.9.1.2.3.1.31 | ciscoDlswTConnOperNQexSents | 0 | 0 | The number of NetBIOS_NQ_ex (NetBIOS Name Query-explorer) messages sent on this transport connection. |
1.3.6.1.4.1.9.10.9.1.2.3.1.32 | ciscoDlswTConnOperNRexRcvds | 0 | 0 | The number of NETBIOS_NR_ex (NetBIOS Name Recognized-explorer) messages received on this transport connection. |
1.3.6.1.4.1.9.10.9.1.2.3.1.33 | ciscoDlswTConnOperNQexRcvds | 0 | 0 | The number of NETBIOS_NQ_ex messages received on this transport connection. |
1.3.6.1.4.1.9.10.9.1.2.3.1.34 | ciscoDlswTConnOperNRexSents | 0 | 0 | The number of NETBIOS_NR_ex messages sent on this transport connection. |
1.3.6.1.4.1.9.10.9.1.2.3.1.35 | ciscoDlswTConnOperCirCreates | 0 | 0 | The number of times that circuits entered `circuit_established' state (not counting transitions from `circuit_restart'). |
1.3.6.1.4.1.9.10.9.1.2.3.1.36 | ciscoDlswTConnOperCircuits | 0 | 0 | The number of currently active circuits on this transport connection, where `active' means not in `disconnected' state. |