The state of this transport connection. The transport
connection enters `connecting' state when DLSw makes
a connection request to the transport layer. Once initial
Capabilities Exchange is sent, the transport connection
enters enters `initCapExchange' state. When partner
capabilities have been determined and the transport
connection is ready for sending CanUReach (CUR) messages,
it moves to the `connected' state. When DLSw is in the
process of bringing down the connection, it is in the
`disconnecting' state. When the transport layer
indicates one of its connections is disconnected, the
transport connection moves to the `disconnected' state.
Whereas all of the values will be returned in response
to a management protocol retrieval operation, only two
values may be specified in a management protocol set
operation: `quiescing' and `disconnecting'. Changing
the value to `quiescing' prevents new circuits from being
established, and will cause a transport disconnect when
the last circuit on the connection goes away. Changing
the value to `disconnecting' will force off all circuits
immediately and bring the connection to `disconnected'
state.
Parsed from file DLSW-MIB.mib
Module: DLSW-MIB
The state of this transport connection. The transport
connection enters `connecting' state when DLSw makes
a connection request to the transport layer. Once initial
Capabilities Exchange is sent, the transport connection
enters enters `initCapExchange' state. When partner
capabilities have been determined and the transport
connection is ready for sending CanUReach (CUR) messages,
it moves to the `connected' state. When DLSw is in the
process of bringing down the connection, it is in the
`disconnecting' state. When the transport layer
indicates one of its connections is disconnected, the
transport connection moves to the `disconnected' state.
Whereas all of the values will be returned in response
to a management protocol retrieval operation, only two
values may be specified in a management protocol set
operation: `quiescing' and `disconnecting'. Changing
the value to `quiescing' prevents new circuits from being
established, and will cause a transport disconnect when
the last circuit on the connection goes away. Changing
the value to `disconnecting' will force off all circuits
immediately and bring the connection to `disconnected'
state.
dlswTConnOperState OBJECT-TYPE
SYNTAX INTEGER {
connecting(1),
initCapExchange(2),
connected(3),
quiescing(4),
disconnecting(5),
disconnected(6)
}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The state of this transport connection. The transport
connection enters `connecting state when DLSw makes
a connection request to the transport layer. Once initial
Capabilities Exchange is sent, the transport connection
enters enters `initCapExchange state. When partner
capabilities have been determined and the transport
connection is ready for sending CanUReach (CUR) messages,
it moves to the `connected state. When DLSw is in the
process of bringing down the connection, it is in the
`disconnecting state. When the transport layer
indicates one of its connections is disconnected, the
transport connection moves to the `disconnected state.
Whereas all of the values will be returned in response
to a management protocol retrieval operation, only two
values may be specified in a management protocol set
operation: `quiescing and `disconnecting. Changing
the value to `quiescing prevents new circuits from being
established, and will cause a transport disconnect when
the last circuit on the connection goes away. Changing
the value to `disconnecting will force off all circuits
immediately and bring the connection to `disconnected
state."
View at oid-info.com
The state of this transport connection. The transport
connection enters `connecting' state when DLSw makes
a connection request to the transport layer. Once initial
Capabilities Exchange is sent, the transport connection
enters enters `initCapExchange' state. When partner
capabilities have been determined and the transport
connection is ready for sending CanUReach (CUR) messages,
it moves to the `connected' state. When DLSw is in the
process of bringing down the connection, it is in the
`disconnecting' state. When the transport layer
indicates one of its connections is disconnected, the
transport connection moves to the `disconnected' state.
Whereas all of the values will be returned in response
to a management protocol retrieval operation, only two
values may be specified in a management protocol set
operation: `quiescing' and `disconnecting'. Changing
the value to `quiescing' prevents new circuits from being
established, and will cause a transport disconnect when
the last circuit on the connection goes away. Changing
the value to `disconnecting' will force off all circuits
immediately and bring the connection to `disconnected'
state.
Parsed from file rfc2024-Data-Link-Switches.mib.txt
Company: None
Module: DLSW-MIB
The state of this transport connection. The transport
connection enters `connecting' state when DLSw makes
a connection request to the transport layer. Once initial
Capabilities Exchange is sent, the transport connection
enters enters `initCapExchange' state. When partner
capabilities have been determined and the transport
connection is ready for sending CanUReach (CUR) messages,
it moves to the `connected' state. When DLSw is in the
process of bringing down the connection, it is in the
`disconnecting' state. When the transport layer
indicates one of its connections is disconnected, the
transport connection moves to the `disconnected' state.
Whereas all of the values will be returned in response
to a management protocol retrieval operation, only two
values may be specified in a management protocol set
operation: `quiescing' and `disconnecting'. Changing
the value to `quiescing' prevents new circuits from being
established, and will cause a transport disconnect when
the last circuit on the connection goes away. Changing
the value to `disconnecting' will force off all circuits
immediately and bring the connection to `disconnected'
state.
dlswTConnOperState OBJECT-TYPE SYNTAX INTEGER { connecting (1), initCapExchange (2), connected (3), quiescing (4), disconnecting (5), disconnected (6) } MAX-ACCESS read-write STATUS current DESCRIPTION "The state of this transport connection. The transport connection enters `connecting' state when DLSw makes a connection request to the transport layer. Once initial Capabilities Exchange is sent, the transport connection enters enters `initCapExchange' state. When partner capabilities have been determined and the transport connection is ready for sending CanUReach (CUR) messages, it moves to the `connected' state. When DLSw is in the process of bringing down the connection, it is in the `disconnecting' state. When the transport layer indicates one of its connections is disconnected, the transport connection moves to the `disconnected' state. Whereas all of the values will be returned in response to a management protocol retrieval operation, only two values may be specified in a management protocol set operation: `quiescing' and `disconnecting'. Changing the value to `quiescing' prevents new circuits from being established, and will cause a transport disconnect when the last circuit on the connection goes away. Changing the value to `disconnecting' will force off all circuits immediately and bring the connection to `disconnected' state." ::= { dlswTConnOperEntry 6 }
dlswTConnOperState OBJECT-TYPE SYNTAX INTEGER { connecting(1), initCapExchange(2), connected(3), quiescing(4), disconnecting(5), disconnected(6) } ACCESS read-write STATUS mandatory DESCRIPTION "The state of this transport connection. The transport connection enters `connecting' state when DLSw makes a connection request to the transport layer. Once initial Capabilities Exchange is sent, the transport connection enters enters `initCapExchange' state. When partner capabilities have been determined and the transport connection is ready for sending CanUReach (CUR) messages, it moves to the `connected' state. When DLSw is in the process of bringing down the connection, it is in the `disconnecting' state. When the transport layer indicates one of its connections is disconnected, the transport connection moves to the `disconnected' state. Whereas all of the values will be returned in response to a management protocol retrieval operation, only two values may be specified in a management protocol set operation: `quiescing' and `disconnecting'. Changing the value to `quiescing' prevents new circuits from being established, and will cause a transport disconnect when the last circuit on the connection goes away. Changing the value to `disconnecting' will force off all circuits immediately and bring the connection to `disconnected' state." ::= { dlswTConnOperEntry 6 }
Automatically extracted from Cisco SNMP v1 MIBs
dlswTConnOperState OBJECT-TYPE SYNTAX INTEGER { connecting (1), initCapExchange (2), connected (3), quiescing (4), disconnecting (5), disconnected (6) } MAX-ACCESS read-write STATUS current DESCRIPTION "The state of this transport connection. The transport connection enters `connecting' state when DLSw makes a connection request to the transport layer. Once initial Capabilities Exchange is sent, the transport connection enters enters `initCapExchange' state. When partner capabilities have been determined and the transport connection is ready for sending CanUReach (CUR) messages, it moves to the `connected' state. When DLSw is in the process of bringing down the connection, it is in the `disconnecting' state. When the transport layer indicates one of its connections is disconnected, the transport connection moves to the `disconnected' state. Whereas all of the values will be returned in response to a management protocol retrieval operation, only two values may be specified in a management protocol set operation: `quiescing' and `disconnecting'. Changing the value to `quiescing' prevents new circuits from being established, and will cause a transport disconnect when the last circuit on the connection goes away. Changing the value to `disconnecting' will force off all circuits immediately and bring the connection to `disconnected' state." ::= { dlswTConnOperEntry 6 }
dlswTConnOperState OBJECT-TYPE SYNTAX INTEGER { connecting (1), initCapExchange (2), connected (3), quiescing (4), disconnecting (5), disconnected (6) } MAX-ACCESS read-write STATUS current DESCRIPTION "The state of this transport connection. The transport connection enters `connecting' state when DLSw makes a connection request to the transport layer. Once initial Capabilities Exchange is sent, the transport connection enters enters `initCapExchange' state. When partner capabilities have been determined and the transport connection is ready for sending CanUReach (CUR) messages, it moves to the `connected' state. When DLSw is in the process of bringing down the connection, it is in the `disconnecting' state. When the transport layer indicates one of its connections is disconnected, the transport connection moves to the `disconnected' state. Whereas all of the values will be returned in response to a management protocol retrieval operation, only two values may be specified in a management protocol set operation: `quiescing' and `disconnecting'. Changing the value to `quiescing' prevents new circuits from being established, and will cause a transport disconnect when the last circuit on the connection goes away. Changing the value to `disconnecting' will force off all circuits immediately and bring the connection to `disconnected' state." ::= { dlswTConnOperEntry 6 }
Internet Assigned Numbers Authority
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.2.1.46.1.2.3.1.1 | dlswTConnOperTDomain | 0 | 0 | The object identifier indicates the transport domain of this transport connection. |
| 1.3.6.1.2.1.46.1.2.3.1.2 | dlswTConnOperLocalTAddr | 0 | 0 | The local transport address for this transport connection. This value could be different from dlswTConnConfigLocalAddr, if the va… |
| 1.3.6.1.2.1.46.1.2.3.1.3 | dlswTConnOperRemoteTAddr | 0 | 0 | The remote transport address of this transport connection. |
| 1.3.6.1.2.1.46.1.2.3.1.4 | dlswTConnOperEntryTime | 0 | 0 | The amount of time (in hundredths of a second) since this transport connection conceptual row was created. |
| 1.3.6.1.2.1.46.1.2.3.1.5 | dlswTConnOperConnectTime | 0 | 0 | The amount of time (in hundredths of a second) since this transport connection last entered the 'connected' state. A value of zer… |
| 1.3.6.1.2.1.46.1.2.3.1.7 | dlswTConnOperConfigIndex | 0 | 0 | The value of dlswTConnConfigIndex of the dlswTConnConfigEntry that governs the configuration information used by this dlswTConnOp… |
| 1.3.6.1.2.1.46.1.2.3.1.8 | dlswTConnOperFlowCntlMode | 0 | 0 | The flow control mechanism in use on this transport connection. This value is undetermined (1) before the mode of flow control ca… |
| 1.3.6.1.2.1.46.1.2.3.1.9 | dlswTConnOperPartnerVersion | 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.2.1.46.1.2.3.1.10 | dlswTConnOperPartnerVendorID | 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.2.1.46.1.2.3.1.11 | dlswTConnOperPartnerVersionStr | 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.2.1.46.1.2.3.1.12 | dlswTConnOperPartnerInitPacingWndw | 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.2.1.46.1.2.3.1.13 | dlswTConnOperPartnerSapList | 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.2.1.46.1.2.3.1.14 | dlswTConnOperPartnerNBExcl | 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.2.1.46.1.2.3.1.15 | dlswTConnOperPartnerMacExcl | 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.2.1.46.1.2.3.1.16 | dlswTConnOperPartnerNBInfo | 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.2.1.46.1.2.3.1.17 | dlswTConnOperPartnerMacInfo | 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.2.1.46.1.2.3.1.18 | dlswTConnOperDiscTime | 0 | 0 | The amount of time (in hundredths of a second) since the dlswTConnOperState last entered `disconnected' state. |
| 1.3.6.1.2.1.46.1.2.3.1.19 | dlswTConnOperDiscReason | 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.2.1.46.1.2.3.1.20 | dlswTConnOperDiscActiveCir | 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.2.1.46.1.2.3.1.21 | dlswTConnOperInDataPkts | 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.2.1.46.1.2.3.1.22 | dlswTConnOperOutDataPkts | 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.2.1.46.1.2.3.1.23 | dlswTConnOperInDataOctets | 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.2.1.46.1.2.3.1.24 | dlswTConnOperOutDataOctets | 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.2.1.46.1.2.3.1.25 | dlswTConnOperInCntlPkts | 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.2.1.46.1.2.3.1.26 | dlswTConnOperOutCntlPkts | 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.2.1.46.1.2.3.1.27 | dlswTConnOperCURexSents | 0 | 0 | The number of CanUReach_ex messages sent on this transport connection. |
| 1.3.6.1.2.1.46.1.2.3.1.28 | dlswTConnOperICRexRcvds | 0 | 0 | The number of ICanReach_ex messages received on this transport connection. |
| 1.3.6.1.2.1.46.1.2.3.1.29 | dlswTConnOperCURexRcvds | 0 | 0 | The number of CanUReach_ex messages received on this transport connection. |
| 1.3.6.1.2.1.46.1.2.3.1.30 | dlswTConnOperICRexSents | 0 | 0 | The number of ICanReach_ex messages sent on this transport connection. |
| 1.3.6.1.2.1.46.1.2.3.1.31 | dlswTConnOperNQexSents | 0 | 0 | The number of NetBIOS_NQ_ex (NetBIOS Name Query-explorer) messages sent on this transport connection. |
| 1.3.6.1.2.1.46.1.2.3.1.32 | dlswTConnOperNRexRcvds | 0 | 0 | The number of NETBIOS_NR_ex (NetBIOS Name Recognized-explorer) messages received on this transport connection. |
| 1.3.6.1.2.1.46.1.2.3.1.33 | dlswTConnOperNQexRcvds | 0 | 0 | The number of NETBIOS_NQ_ex messages received on this transport connection. |
| 1.3.6.1.2.1.46.1.2.3.1.34 | dlswTConnOperNRexSents | 0 | 0 | The number of NETBIOS_NR_ex messages sent on this transport connection. |
| 1.3.6.1.2.1.46.1.2.3.1.35 | dlswTConnOperCirCreates | 0 | 0 | The number of times that circuits entered `circuit_established' state (not counting transitions from `circuit_restart'). |
| 1.3.6.1.2.1.46.1.2.3.1.36 | dlswTConnOperCircuits | 0 | 0 | The number of currently active circuits on this transport connection, where `active' means not in `disconnected' state. |