CISCO-DLSW-EXT-MIB
AI MIB Summary
The CISCO-DLSW-EXT-MIB monitors Cisco DLSw+ peer connections and circuits to track TCP, FST, Direct-encapsulation, and DLSw Lite transport states, local acknowledgment counters, and dynamic resource discovery metrics for SNA and NetBIOS traffic. It provides visibility into circuit establishment failures, keepalive timeouts, and rerouting events across Token Ring, Ethernet, SDLC, and QLLC media segments.
The MIB module for management of Cisco specific Data Link Switching protocol enhancements. DLSw is described in RFC 1795 and RFC 2024.
DLSw+ Defined
Data link switching Plus (DLSw+) is a means of transporting Systems Network Architecture (SNA) and NetBIOS traffic over an IP network. The end systems can attach to the network over Token Ring, Ethernet, Synchronous Data Link Control (SDLC) protocol, or Qualified Logical Link Control (QLLC). DLSw+ switches between diverse media, and locally terminates the data links, keeping acknowledgments, keepalives, and polling off of the WAN. Local termination of data links also eliminates data link control time-outs that can occur during transient network congestion or when rerouting around failed links. Finally, DLSw+ provides a mechanism for dynamically searching a network for SNA or NetBIOS resources and includes caching algorithms that minimize the broadcast traffic required.
In this document, DLSw+ routers are referred to as peers, or partners. The connection between two DLSw+ routers is referred to as a peer connection. A DLSw circuit is comprised of the data link control connection between the originating end system and the originating router, the connection between the two routers (typically a TCP connection), and the data link control connection between the target router and the target end system. A single peer connection can carry multiple circuits.
The transport connection between DLSw+ routers can vary according to the needs of the network and is not tied to TCP/IP as the DLSw standard is. Cisco supports four different transport protocols between DLSw+ routers:
TCP/IP-for transport of SNA and NetBIOS traffic across WANs where local acknowledgment is required to minimize unnecessary traffic and prevent data-link control timeouts and where non-disruptive rerouting around link failures is critical. This transport option is required when DLSw+ is operating in DLSw standards mode.
FST/IP-for transport across WANs with an arbitrary topology and with sufficient bandwidth to accommodate SNA and NetBIOS traffic. This solution allows for rerouting around link failures, but recovery may be disruptive depending on the time required to find an alternate path. This option does not support local acknowledgment of frames.
Direct-encapsulation for transport across a point-to-point or Frame Relay connection where the benefits of an arbitrary topology are not important and where nondisruptive rerouting around link failures is not required. This option does not support local acknowledgment of frames.
DLSw Lite-also known as Logical Link Control, Type2 (LLC2) encapsulation -for transport across a point-to-point connection (currently only Frame Relay is supported) where local acknowledgment and reliable transport are important, but where nondisruptive rerouting around link failures is not required. DLSw Lite uses RFC 1490 encapsulation of LLC2.
Main OID:
ciscoDlswExtMIB.1.3.6.1.4.1.9.9.74
101
Objects
Active
Status
8
Dependencies
Imported Objects
Objects
101 total| Object Name |
|---|
ciscoDlswExtMIBThe MIB module for management of Cisco specific Data Link
Switching protocol enhancements. DLSw is described in
RFC 1795 and RFC 2024.
DLSw+ Defined
Data link switching Plus (DLSw+) is a means of transporting
Systems Network Architecture (SNA) and NetBIOS traffic over
an IP network. The end systems can attach to the network over
Token Ring, Ethernet, Synchronous Data Link Control
(SDLC) protocol, or Qualified Logical Link Control (QLLC).
DLSw+ switches between diverse media, and locally terminates
the data links, keeping acknowledgments, keepalives, and polling
off of the WAN. Local termination of data links also
eliminates data link control time-outs that can occur during
transient network congestion or when rerouting around failed
links. Finally, DLSw+ provides a mechanism for dynamically
searching a network for SNA or NetBIOS resources and
includes caching algorithms that minimize the broadcast traffic
required.
In this document, DLSw+ routers are referred to as
peers, or partners. The connection between two DLSw+
routers is referred to as a peer connection. A DLSw circuit is
comprised of the data link control connection between the
originating end system and the originating router, the connection
between the two routers (typically a TCP connection), and
the data link control connection between the target router and
the target end system. A single peer connection can carry
multiple circuits.
The transport connection between DLSw+ routers can vary according
to the needs of the network and is not tied to TCP/IP
as the DLSw standard is. Cisco supports four different transport
protocols between DLSw+ routers:
TCP/IP-for transport of SNA and NetBIOS traffic across WANs where
local acknowledgment is required to minimize
unnecessary traffic and prevent data-link control timeouts and
where non-disruptive rerouting around link failures is
critical. This transport option is required when DLSw+ is
operating in DLSw standards mode.
FST/IP-for transport across WANs with an arbitrary topology and
with sufficient bandwidth to accommodate SNA
and NetBIOS traffic. This solution allows for rerouting around
link failures, but recovery may be disruptive depending
on the time required to find an alternate path. This option does
not support local acknowledgment of frames.
Direct-encapsulation for transport across a point-to-point or
Frame Relay connection where the benefits of an
arbitrary topology are not important and where nondisruptive
rerouting around link failures is not required. This option
does not support local acknowledgment of frames.
DLSw Lite-also known as Logical Link Control, Type2 (LLC2)
encapsulation -for transport across a point-to-point
connection (currently only Frame Relay is supported) where
local acknowledgment and reliable transport are
important, but where nondisruptive rerouting around link
failures is not required. DLSw Lite uses RFC 1490
encapsulation of LLC2. MODULE-IDENTITY .1.3.6.1.4.1.9.9.74 |
ciscoDlswExtMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.74.1 |
cdeDomains OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.74.1.1 |
cdeFSTDomain OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.74.1.1.1 |
cdeDirectHdlcDomain OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.74.1.1.2 |
cdeDirectFrameRelayDomain OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.74.1.1.3 |
cdeLlc2Domain OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.74.1.1.4 |
cdeNode OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.74.1.2 |
cdeNodeTAddrThe local peer IP address; required for Fast-Sequenced
Transport (FST) and TCP. If no local peer IP address
is configured then this object will be the empty string.rw TAddress (DLSW-MIB) .1.3.6.1.4.1.9.9.74.1.2.1 |
cdeNodeGroupPeer group number for this router.
Peer groups are arbitrary groups of routers with one or
more designated border peers. Border peers form peer
connections with every router in their group and with
border peers in other groups. The role of a border peer
is to forward explorers on behalf of other routers.
A value of zero means no group has been set and the
DLSw is not a group member.rw INTEGER .1.3.6.1.4.1.9.9.74.1.2.2 |
cdeNodeBorderThis variable indicates if this DLSw is capable of
operating as a border peer. True indicates that it is
capable, false indicates that it is not.
Border peers form peer connections with every router in
their group and with border peers in other groups. The
role of a border peer is to forward explorers on behalf
of other DLSw routers.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.74.1.2.3 |
cdeNodeCostPeer cost advertised to remote peers in the capabilities
exchange. If an end station can be reached through more
than one peer, the cost of each peer will be considered when
a circuit is established.
A lower cost indicates that peer will be the
preferred choice if there is more than one path to the
destination. A value of zero means no cost has been set
and that cost will not be considered during circuit
establishment.rw Cost .1.3.6.1.4.1.9.9.74.1.2.4 |
cdeNodeKeepaliveIntervalDefault remote peer keepalive interval in seconds.
The keepalive parameter refers to how often DLSw peers
send peer keep alives to each other. These periodic messages
allow DLSw to keep track of the state of all peers.
If set to zero, no keepalives are sent.rw KeepaliveInterval UNITS "Seconds" .1.3.6.1.4.1.9.9.74.1.2.5 |
cdeNodePassiveConnectThis variable indicates if DLSw will not initiate
remote peer connections to configured peers. True
indicates that it will not initiate remote peer connections,
false indicates that it will initiate remote peer connections.
In other words a passive peer will wait for the remote peer
to initiate a peer connectionrw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.74.1.2.6 |
cdeNodeBiuSegmentThis variable indicates if DLSw will spoof the maximum
receivable Basic Information Unit (frame) size in XID so that
each end station sends the largest frame it can. True indicates
that it will spoof, false indicates that it will not.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.74.1.2.7 |
cdeNodeInitPacingWindowInitial pacing window size. This is the starting size of the
pacing window. DLSw uses an adaptive pacing
flow control algorithm that automatically adjusts to congestion
levels in the network. Pacing windows are used to control
how many packets may be sent to a peer before acknowlegement.rw INTEGER .1.3.6.1.4.1.9.9.74.1.2.8 |
cdeNodeMaxPacingWindowMaximum pacing window size. This is the largest size that
the pacing window will grow to. DLSw uses an adaptive pacing
flow control algorithm that automatically adjusts to congestion
levels in the network. Pacing windows are used to control
how many packets may be sent to a peer before acknowlegement.rw INTEGER .1.3.6.1.4.1.9.9.74.1.2.9 |
cdeNodePromiscuousThis variable indicates if DLSw will accept connections from
non-configured remote peers. Promiscuous routers will
accept peer connection requests from routers that are
not preconfigured. This feature allows central site routers
to remain unchanged when branch offices are added or deleted.
It also minimizes required coordination of configurations.
True indicates that it will accept connections,
false indicates that it will not.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.74.1.2.10 |
cdeNodePromPeerDefaultsCostThis variable indicates the cost that will be used with
promiscuous peers.
If an end station can be reached through more
than one peer, the cost of each peer will be considered when
a circuit is established.
A lower cost indicates that peer will be the
preferred choice if there is more than one path to the
destination.rw Cost .1.3.6.1.4.1.9.9.74.1.2.11 |
cdeNodePromPeerDefaultsDestMacPermits the promiscuous peer connection to be established
only when there is an explorer frame destined for the
specified 48-bit MAC address. If no default destination mac
is configured then this object will be the empty string.rw MacAddressNC (DLSW-MIB) .1.3.6.1.4.1.9.9.74.1.2.12 |
cdeNodePromPeerDefaultsKeepaliveIntervalDefault promiscuous peer keepalive interval in seconds.
The keepalive parameter refers to how often DLSw peers
send peer keep alives to each other. These periodic messages
allow DLSw to keep track of the state of all peers.
If set to zero, no keepalives are sent.rw KeepaliveInterval UNITS "Seconds" .1.3.6.1.4.1.9.9.74.1.2.13 |
cdeNodePromPeerDefaultsLFSizeThe default Largest Frame Size associated with the
default promiscuous peer transport connection.
In other words its the largest size of the INFO field
(including DLC header, not including any MAC-level or framing
octets).rw LFSize UNITS "bytes" .1.3.6.1.4.1.9.9.74.1.2.14 |
cdeNodePromPeerDefaultsTCPQueueMaxDefault promiscuous peer maximum output TCP queue size.
For DLSw over TCP encapsulation, packets may be queued
due to congestion of the TCP network. This variable
is used to set the output queue maximum of the underlying
TCP connection, by default on a promiscuous
peer transport connection.rw TCPQueueMax UNITS "packets" .1.3.6.1.4.1.9.9.74.1.2.15 |
cdeNodePeerOnDemandDefaultsCostThis variable indicates the cost that will be used with
peer on demand peers.
If an end station can be reached through more
than one peer, the cost of each peer will be considered when
a circuit is established.
A lower cost indicates that peer will be the
preferred choice if there is more than one path to the
destination.rw Cost .1.3.6.1.4.1.9.9.74.1.2.16 |
cdeNodePeerOnDemandDefaultsFstThis variable indicates if Fast-Sequenced Transport (FST)
will be for peer on demand peers. True indicates that
FST will be used, false indicates that it will not.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.74.1.2.17 |
cdeNodePeerOnDemandDefaultsInactivityIntervalThis variable indicates the length of time a peer on demand
connection can be idle before shutting down this peer
on demand connection. If set to zero, the peer on demand
connection will not be closed due to inactivity.rw INTEGER .1.3.6.1.4.1.9.9.74.1.2.18 |
cdeNodePeerOnDemandDefaultsKeepaliveIntervalDefault peer on demand keepalive interval in seconds.
The keepalive parameter refers to how often DLSw peers
send peer keep alives to each other. These periodic messages
allow DLSw to keep track of the state of all peers.
If set to zero, no keepalives are sent.rw KeepaliveInterval UNITS "Seconds" .1.3.6.1.4.1.9.9.74.1.2.19 |
cdeNodePeerOnDemandDefaultsLFSizeThe default Largest Frame Size associated with the
default peer on demand transport connections.
In other words its the largest size of the INFO field
(including DLC header, not including any MAC-level or framing
octets).rw LFSize (DLSW-MIB) .1.3.6.1.4.1.9.9.74.1.2.20 |
cdeNodePeerOnDemandDefaultsPriorityThis variable indicates if circuit prioritization will be used
for peer-on-demand peers. True indicates that circuit
prioritization specified by the dlswCircuitPriority object
in the DLSW-MIB (RFC 2024) will be used, false indicates that
there will be no circuit prioritization.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.74.1.2.21 |
cdeNodePeerOnDemandDefaultsTCPQueueMaxDefault peer-on-demand Maximum output TCP queue size.
For DLSw over TCP encapsulation, packets may be queued
due to congestion of the TCP network. This variable
is used to set the output queue maximum of the underlying
TCP connection, by default on a peer on demand
transport connection.rw TCPQueueMax UNITS "packets" .1.3.6.1.4.1.9.9.74.1.2.22 |
cdeTConn OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.74.1.3 |
cdeTConnConfigTableThis table defines the peer transport connections
that will be initiated or accepted by this
DLSw. Structure of masks allows wildcard
definition for a collection of transport
connections by a conceptual row. For a
specific transport connection, there may
be multiple conceptual rows that match the
transport address. The `best' match will be
the one to determine the characteristics
of the transport connection.
This table augments dlswTConnConfigTable. SEQUENCE OF CdeTConnConfigEntry .1.3.6.1.4.1.9.9.74.1.3.1 |
cdeTConnConfigEntryA list of objects that define specific configuration for
a DLSw peer transport connection. CdeTConnConfigEntry .1.3.6.1.4.1.9.9.74.1.3.1.1 |
cdeTConnConfigTDomainTypeThe type of DLSw encapsulation in use on this peer connection.rw TDomainType .1.3.6.1.4.1.9.9.74.1.3.1.1.1 |
cdeTConnConfigLocalAckReflects whether the peer connection is locally acknowledged.
Locally acknoledgement means terminating the DLC connections
at the router, eliminating the requirement for link-layer
acknowledgements and keepalive messages to flow across the
WAN. In addition because link-layer frames are acknowledged
locally, link-layer time-outs should not occur.
In general ciscoDlswTConnConfigLocalAck will be true when the
domain type is tcp, false when the domain type is fst,
direct-hdlc, or direct-frame-relay.
Configuring the remote-peer as pass-thru, the remote peer
will not use local acknowlegement.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.74.1.3.1.1.2 |
cdeTConnConfigCostThe cost associated with the transport connection,
assigned to this conceptual row representing a peer.
If an end station can be reached through more
than one peer, the cost of each peer will be considered when
a circuit is established.
A lower cost indicates that peer will be the
preferred choice if there is more than one path to the
destination.rw Cost .1.3.6.1.4.1.9.9.74.1.3.1.1.3 |
cdeTConnConfigLFSizeThe Largest Frame Size associated with the transport connection.
In other words its the largest size of the INFO field
(including DLC header, not including any MAC-level or framing
octets).rw LFSize (DLSW-MIB) .1.3.6.1.4.1.9.9.74.1.3.1.1.4 |
cdeTConnConfigKeepaliveIntervalThe amount of time between keepalive messages on a transport
connection.
The keepalive parameter refers to how often DLSw peers
send peer keep alives to each other. These periodic messages
allow DLSw to keep track of the state of all peers.
If set to zero, no keepalives are sent.rw KeepaliveInterval UNITS "Seconds" .1.3.6.1.4.1.9.9.74.1.3.1.1.5 |
cdeTConnConfigBackupThis variable indicates if this peer is defined
as a backup to an existing peer. A backup peer is used
to provide an alternate path in case an existing peer becomes
unavailable. A backup peer will not enter the connected
state until the primary peer that it backs up becomes
disconnected.
True indicates that this conecptual row is a backup peer
to a pre-existing peer, false indicates this peer is not
a backup peer.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.74.1.3.1.1.6 |
cdeTConnConfigBackupTAddrThe primary peer's IP address that this entry backs up.
Valid only when ciscoDlswTConnConfigBackup is true.rw TAddress (DLSW-MIB) .1.3.6.1.4.1.9.9.74.1.3.1.1.7 |
cdeTConnConfigBackupLingerThis variable indicates whether the backup peer will
remain connected after the primary peer connection has
been re-established.
True indicates that the backup peer will remain connected after
the primary peer connection has been re-established, for the
length of time specified in cdeTConnConfigBackupLingerInterval.
False indicates that the backup peer will remain connected until
all circuits on the backup peer connection have been disconnected.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.74.1.3.1.1.8 |
cdeTConnConfigBackupLingerIntervalThis variable indicates the length of time the backup peer
remains connected after the primary peer connection has
been re-established. If this variable is zero, the backup peer
will be disconnected immediately after the primary peer connection
has been re-established. If greater than zero the backup will
stay connected for the number of minutes indicated by this variable,
after the primary peer connection has been re-established.
Note that the linger interval is only used when
cdeTConnConfigBackupLinger is true.rw INTEGER .1.3.6.1.4.1.9.9.74.1.3.1.1.9 |
cdeTConnConfigPriorityIndicator 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.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.74.1.3.1.1.10 |
cdeTConnConfigDestMacPermits the peer connection to be established only when there is an
explorer frame destined for the specified 48-bit MAC address.
If no expolorer traffic with a destination address of
cdeTConnConfigDestMac is received by DLSw,
the peer reprented by this conceptual row will not be connected.rw MacAddressNC (DLSW-MIB) .1.3.6.1.4.1.9.9.74.1.3.1.1.11 |
cdeTConnConfigDynamicIndicates the peer connection is to be established only
when there is DLSw+ data to send.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.74.1.3.1.1.12 |
cdeTConnConfigDynamicNoLlcThis variable indicates the length of time a dynamic peer
remains connected after all LLC2 circuits are gone.rw INTEGER .1.3.6.1.4.1.9.9.74.1.3.1.1.13 |
cdeTConnConfigDynamicInactivityIntervalIndicates the length of time a connection can be idle before
closing the dynamic peer connection. If set to zero, the dynamic
peer connection will not be closed due to inactivity.rw INTEGER .1.3.6.1.4.1.9.9.74.1.3.1.1.14 |
cdeTConnOperTableA list of peer transport connections.
Each connected peer will create a conceptual row in the table.
When the peer disconnects, the row will be deleted from the table.
This table augments dlswTConnOperTable. SEQUENCE OF CdeTConnOperEntry .1.3.6.1.4.1.9.9.74.1.3.2 |
cdeTConnOperEntryA list of objects that contain spefific operational
information for a DLSw peer transport connection. CdeTConnOperEntry .1.3.6.1.4.1.9.9.74.1.3.2.1 |
cdeTConnOperPartnerCostThe partner's cost on this peer connection, as received
through capabilities exchange.
If an end station can be reached through more
than one peer, the cost of each peer will be considered when
a circuit is established.
A lower cost indicates that peer will be the
preferred choice if there is more than one path to the
destination.ro Cost .1.3.6.1.4.1.9.9.74.1.3.2.1.1 |
cdeTConnOperPartnerPriorityThe partner's priority setting on this peer connection,
as received through capabilities exchange.
When priority is enabled 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.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.74.1.3.2.1.2 |
cdeTConnOperPartnerBorderPeerThis variable indicates if the partner DLSw is capable of
operating as a border peer, as received through capabilities
exchange. True indicates that it is
capable, false indicates that it is not.
Border peers form peer connections with every router in
their group and with border peers in other groups. The
role of a border peer is to forward explorers on behalf
of other DLSw routers.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.74.1.3.2.1.3 |
cdeTConnOperPartnerGroupNumThis variable indicates the partner's group number, as
received through capabilities exchange.
Peer groups are arbitrary groups of routers with one or
more designated border peers. Border peers form peer
connections with every router in their group and with
border peers in other groups. The role of a border peer
is to forward explorers on behalf of other routers.
A value of zero means no group has been set and the
DLSw is not a group member.ro INTEGER .1.3.6.1.4.1.9.9.74.1.3.2.1.4 |
cdeTConnOperTDomainTypeThe type of DLSw encapsulation in use on this peer connection.ro TDomainType .1.3.6.1.4.1.9.9.74.1.3.2.1.5 |
cdeTConnSpecific OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.74.1.3.3 |
cdeTConnTcp OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.74.1.3.3.1 |
cdeTConnTcpConfigTableThis table defines the TCP transport connections that
will be either initiated by or accepted by this DSLw.
It augments the entries in dlswTConnConfigTable whose
domain is dlswTCPDomain. In other words for each conceptual row
in the dlswTConnConfigTable, if the dlswTConnConfigTDomain is
dlswTCPDomain, that conceptual row will be augmented by this
table.
dlswTCPDomain, dlswTConnConfigTable, and dlswTConnConfigTDomain
are all imported from DLSW-MIB (RFC 2024).
This table augments dlswTConnTcpConfigTable. SEQUENCE OF CdeTConnTcpConfigEntry .1.3.6.1.4.1.9.9.74.1.3.3.1.1 |
cdeTConnTcpConfigEntryA list of objects that define spefific configuration for
a DLSw peer transport connection within the dlswTCPDomain.
dlswTCPDomain is imported from DLSW-MIB (RFC 2024). CdeTConnTcpConfigEntry .1.3.6.1.4.1.9.9.74.1.3.3.1.1.1 |
cdeTConnTcpConfigQueueMaxMaximum output TCP queue size for this remote peer.
For DLSw over TCP encapsulation, packets may be queued
due to congestion of the TCP network. This variable
is used to set the output queue maximum of the underlying
TCP connection for the peer represented by the conceptual row.rw TCPQueueMax UNITS "packets" .1.3.6.1.4.1.9.9.74.1.3.3.1.1.1.1 |
cdeTConnDirect OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.74.1.3.3.2 |
cdeTConnDirectConfigTableThis table contains direct peer media-specific
configuration information.
An entry is maintained for every peer in the
cdeTConnConfigTable whose domain is either cdeDirectHdlcDomain,
cdeDirectFrameRelayDomain, or cdeLlc2Domain.
In other words, for each conceptual row
in the dlswTConnConfigTable, if the dlswTConnConfigTDomain is
either cdeDirectHdlcDomain, cdeDirectFrameRelayDomain, or
cdeLlc2Domain, there will be an entry in this table.
dlswTConnConfigTable, and dlswTConnConfigTDomain
are imported from DLSW-MIB (RFC 2024). SEQUENCE OF CdeTConnDirectConfigEntry .1.3.6.1.4.1.9.9.74.1.3.3.2.1 |
cdeTConnDirectConfigEntryEach conceptual row defines parameters that are
specific to peer transport connections whose domain is
either cdeDirectHdlcDomain, cdeDirectFrameRelayDomain, or
cdeLlc2Domain. CdeTConnDirectConfigEntry .1.3.6.1.4.1.9.9.74.1.3.3.2.1.1 |
cdeTConnDirectConfigIfIndexThe IfEntry index of the local interface,
on which the direct peer can be reached.rw InterfaceIndex (IF-MIB) .1.3.6.1.4.1.9.9.74.1.3.3.2.1.1.1 |
cdeTConnDirectConfigMediaEncapThe type of media encapsulation to be used on this
peer connection. When using DLSw Direct-encapsulation or
DLSw Lite (Frame Relay) encapsulation, the peer transport
connection is defined as either directHdlc or directFrameRelay,
respectively.
Hdlc peer transport encapsulation does not support
local acknowledgment of frames.
Logical Link Control, Type2 (LLC2) peer transport
encapsulation -for transport across a point-to-point
connection (currently only Frame Relay is supported) provides
local acknowledgment and reliable transport.rw Enumeration .1.3.6.1.4.1.9.9.74.1.3.3.2.1.1.2 |
cdeTConnDirectConfigFrameRelayDlciThe Data Link Connection Identifier for the virtual
circuit on this interface. This object will only
be valid if the value of
cdeTConnDirectConfigMediaEncap is llc2.rw DlciNumber (CISCO-FRAME-RELAY-MIB) .1.3.6.1.4.1.9.9.74.1.3.3.2.1.1.3 |
cdeInterface OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.74.1.4 |
cdeIfTableThe list of interfaces on which DLSw is active.
This table augments dlswIfTable. SEQUENCE OF CdeIfEntry .1.3.6.1.4.1.9.9.74.1.4.1 |
cdeIfEntryEach conceptual row represents an interface. CdeIfEntry .1.3.6.1.4.1.9.9.74.1.4.1.1 |
cdeIfTypeThe DLC protocol in use on this DLSw interface.ro DlcType (DLSW-MIB) .1.3.6.1.4.1.9.9.74.1.4.1.1.1 |
cdeCircuit OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.74.1.5 |
cdeCircuitTableA list of circuits. Each new circuit will create a conceptual row
in the table.
When the circuit disconnects, the row will be deleted from the table.
End station 1 (S1) and End station 2 (S2) are used to
represent the two end stations of the circuit.
S1 is always an end station which is locally attached.
S2 may be locally attached or remote.
This table augments the dlswCircuitTable. SEQUENCE OF CdeCircuitEntry .1.3.6.1.4.1.9.9.74.1.5.1 |
cdeCircuitEntryA list of objects that contain specific
information for a DLSw circuit. CdeCircuitEntry .1.3.6.1.4.1.9.9.74.1.5.1.1 |
cdeCircuitS1NameRepresents the PU Name of End Station 1 (S1), if available.ro DisplayString .1.3.6.1.4.1.9.9.74.1.5.1.1.1 |
cdeCircuitS2NameRepresents the PU Name of End Station 2 (S2), if available.ro DisplayString .1.3.6.1.4.1.9.9.74.1.5.1.1.2 |
cdeCircuitS1IdBlockThe block number is the first three digits of the SNA Node id of
End Station 1 (S1), if available. These 3 hexadecimal digits
identify the product.ro DisplayString .1.3.6.1.4.1.9.9.74.1.5.1.1.3 |
cdeCircuitS1IdNumThe ID number is the last 5 digits of the SNA Node id of End
Station 1 (S1), if available. These 5 hexadecimal digits are
administratively defined and combined with the 3 digit
block number form the Node id. This Node id is used to
identify the local node and is included in SNA XIDs.ro DisplayString .1.3.6.1.4.1.9.9.74.1.5.1.1.4 |
cdeFast OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.74.1.6 |
cdeFastTableA table containing fast cache entries.
The table contains cache information for FST peers or
direct encapsulation peers (without local acknowledgement enabled).
When using these encapsulation types, a fast-switching
cache must be built. The first frame between two end
stations will be process switched, and during this
process an entry will be made in the fast-switching
cache so that subsequent frames between those end
stations may be fast switched.
End station 1 (S1) and End station 2 (S2) are used to
represent the two end stations of the faat cache entry.
S1 is always an end station which is locally attached.
S2 is always an end station which is remote. SEQUENCE OF CdeFastEntry .1.3.6.1.4.1.9.9.74.1.6.1 |
cdeFastEntryA list of objects that define specific information
for a DLSw fast cache entry. CdeFastEntry .1.3.6.1.4.1.9.9.74.1.6.1.1 |
cdeFastS1MacThe MAC Address of End Station 1 (S1) used for this cache entry. MacAddressNC (DLSW-MIB) .1.3.6.1.4.1.9.9.74.1.6.1.1.1 |
cdeFastS1SapThe SAP at End Station 1 (S1) used for this cache entry. SAPType (CISCO-TC) .1.3.6.1.4.1.9.9.74.1.6.1.1.2 |
cdeFastS2MacThe MAC Address of End Station 2 (S2) used for this cache entry. MacAddressNC (DLSW-MIB) .1.3.6.1.4.1.9.9.74.1.6.1.1.3 |
cdeFastS2SapThe SAP at End Station 2 (S2) used for this cache entry. SAPType (CISCO-TC) .1.3.6.1.4.1.9.9.74.1.6.1.1.4 |
cdeFastS1IfIndexThe ifEntry index of the local interface through which S1
can be reached.ro InterfaceIndex (IF-MIB) .1.3.6.1.4.1.9.9.74.1.6.1.1.5 |
cdeFastS1RouteInfoIf source-route bridging is in use between the DLSw
and S1, this is the routing information field
describing the path between the two devices.
Otherwise the value will be an OCTET STRING of
zero length.ro OCTET STRING .1.3.6.1.4.1.9.9.74.1.6.1.1.6 |
cdeFastS1CacheIdThe Cache ID assigned by this DLSw to this fast cache entry.
Every Fast cache entry will have a unique id.
A management station could use this object by periodically
polling this table, and determine whether the same cache
entries were present or absent.ro OCTET STRING .1.3.6.1.4.1.9.9.74.1.6.1.1.7 |
cdeFastS2TDomainThis object contains the transport domain of the peer
transport protocol that the fast cache entry is running
over.ro OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.74.1.6.1.1.8 |
cdeFastS2TAddressThis object contains the transport address of the partner DLSw.ro TAddress (DLSW-MIB) .1.3.6.1.4.1.9.9.74.1.6.1.1.9 |
cdeFastS2CacheIdThe Cache ID assigned to this fast cache entry by the partner
DLSw.
Every Fast cache entry will have a unique id.
A management station could use this object by periodically
polling this table, and determine whether the same cache
entries were present or absent.ro OCTET STRING .1.3.6.1.4.1.9.9.74.1.6.1.1.10 |
cdeFastOriginThis object specifies which of the two end stations
initiated the establishment of this circuit.ro Enumeration .1.3.6.1.4.1.9.9.74.1.6.1.1.11 |
cdeFastTimeToLiveThe amount of time (in hundredths of a second) remaining
before this fast cache entry will be removed from the table.
After 5 minutes of inactivity, the fast cache entry will be
deleted.ro TimeTicks UNITS "hundredths of a second" .1.3.6.1.4.1.9.9.74.1.6.1.1.12 |
cdeTrapControl OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.74.1.7 |
cdeTrapCntlTConnIndicates whether DLSw is permitted to emit transport
connection up and down traps. With the value of `true'
DLSw will emit traps when connections enter `connected'
and `disconnected' states. With the value of `false'
DLSw will not emit traps when connections enter
`connected' and `disconnected' states.
The changes take effect immediately.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.74.1.7.1 |
cdeTrapCntlCircuitIndicates whether the DLSw is permitted to generate
circuit up and down traps. With the value of `true'
the DLSw will emit traps when circuits enter `connected'
and `disconnected' states. With the value of `false'
the DLSw will not emit traps when circuits enter
`connected' and `disconnected' states.
The changes take effect immediately.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.74.1.7.2 |
cdeTrapsPrefix OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.74.2 |
cdeTraps OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.74.2.0 |
cdeTrapTConnUpDownThis trap is sent each time a transport connection
changes state to `connected' or `disconnected'.
The emission of this trap
is controlled by cdeTrapCntlTConn. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.74.2.0.1 |
cdeTrapCircuitUpDownThis trap is sent each time a circuit changes
state to `connected' or `disconnected'.
the emission of this trap is controlled by
cdeTrapCntlCircuit. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.74.2.0.2 |
cdeMIBConformance OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.74.3 |
cdeMIBCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.74.3.1 |
cdeMIBGroups OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.74.3.2 |