Specifications

Application View Cisco DLSW Application
Device Management Page 133 Cisco Router
State
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.
Config Ind
The value of ciscoDlswTConnConfigIndex of the
ciscoDlswTConnConfigEntry that governs the
configuration information used by this Dlsw
TConn Operation Table entry. This value is zero if
the corresponding ciscoDlswTConnConfigEntry
was deleted after the creation of this Dlsw TConn
Operation Table entry. If fields in the former were
changed but the conceptual row was not deleted,
some configuration information may not be valid
for this operational transport connection.
Flow Cntl Mode
The flow control mechanism in use on this
transport connection. This value is
undetermined 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). A
value of pacing indicates that the standard RFC
1795 pacing mechanism is in use. A value of
other 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 Partner Version.
Partner Version
This value identifies which version (first octet) and
release (second octet) of the DLSw standard is
supported by this partner DLSw. This information
is obtained from a DLSw capabilities exchange