CISCO-DLSW-EXT-MIB

All MIBs › CISCO-DLSW-EXT-MIB

Organization: Cisco IBU Engineering Working Group

Last Updated: 1997-03-11

Category: Cisco Devices, SNA and Legacy Protocols

Description: Extends DLSw management with Cisco-specific objects for SNA/NetBIOS-over-IP circuit configuration and performance tuning.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is CISCO-DLSW-EXT-MIB?

CISCO-DLSW-EXT-MIB is a Cisco Systems (IBU Engineering Working Group) proprietary MIB extending the standard DLSW-MIB (RFC 1795/2024) with Cisco-specific DLSw+ (Data Link Switching Plus) objects for transporting SNA/NetBIOS traffic over IP. Its node-level objects cover transport address, group, border-peer flag, cost, keepalive interval, passive-connect, BIU-segment support, initial/max pacing window, promiscuous mode with promiscuous-peer defaults (cost, destination MAC, keepalive, largest-frame size, TCP queue max) and peer-on-demand defaults (cost, fast-switching, inactivity interval, keepalive, largest-frame size, priority, TCP queue max), alongside a TCP-connection-configuration table. As a configuration MIB it lets an administrator confirm DLSw+ peer cost and pacing-window settings when troubleshooting a slow SNA/NetBIOS-over-IP session. It is deployed on Cisco routers running DLSw+. Engineers can download the CISCO-DLSW-EXT-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in CISCO-DLSW-EXT-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Cisco routers (DLSw+ SNA/NetBIOS over IP)

Monitoring Examples

An administrator checks cdeNodeMaxPacingWindow and cdeNodeCost to confirm DLSw+ peer preference and flow-control settings when diagnosing a slow SNA session tunneled over a Cisco router.

What Can Be Monitored

DLSw+ peer cost, pacing window, and connection configuration

Imported Objects

From CISCO-FRAME-RELAY-MIB

DlciNumber

From CISCO-SMI

ciscoMgmt

OBJECT-IDENTITY

From CISCO-TC

SAPType

From DLSW-MIB

DlcType
LFSize
MacAddressNC
TAddress
dlswCircuitEntry	OBJECT-TYPE
dlswCircuitState	OBJECT-TYPE
dlswIfEntry	OBJECT-TYPE
dlswTConnConfigEntry	OBJECT-TYPE
dlswTConnConfigIndex	OBJECT-TYPE
dlswTConnOperEntry	OBJECT-TYPE
dlswTConnOperState	OBJECT-TYPE
dlswTConnTcpConfigEntry	OBJECT-TYPE

From IF-MIB

InterfaceIndex

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
TimeTicks

From SNMPv2-TC

DisplayString
TEXTUAL-CONVENTION
TruthValue

OIDs

OID symbolic	OID numeric	Type	Access	Description
cdeCircuit	1.3.6.1.4.1.9.9.74.1.5
cdeCircuitEntry	1.3.6.1.4.1.9.9.74.1.5.1.1		not-accessible	A list of objects that contain specific information for a DLSw circuit.
STR cdeCircuitS1IdBlock	1.3.6.1.4.1.9.9.74.1.5.1.1.3	DisplayString	read-only	The 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.
STR cdeCircuitS1IdNum	1.3.6.1.4.1.9.9.74.1.5.1.1.4	DisplayString	read-only	The 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.
STR cdeCircuitS1Name	1.3.6.1.4.1.9.9.74.1.5.1.1.1	DisplayString	read-only	Represents the PU Name of End Station 1 (S1), if available.
STR cdeCircuitS2Name	1.3.6.1.4.1.9.9.74.1.5.1.1.2	DisplayString	read-only	Represents the PU Name of End Station 2 (S2), if available.
cdeCircuitTable	1.3.6.1.4.1.9.9.74.1.5.1		not-accessible	A 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.
cdeDirectFrameRelayDomain	1.3.6.1.4.1.9.9.74.1.1.3
cdeDirectHdlcDomain	1.3.6.1.4.1.9.9.74.1.1.2
cdeDomains	1.3.6.1.4.1.9.9.74.1.1
cdeFast	1.3.6.1.4.1.9.9.74.1.6
cdeFastEntry	1.3.6.1.4.1.9.9.74.1.6.1.1		not-accessible	A list of objects that define specific information for a DLSw fast cache entry.
INT cdeFastOrigin	1.3.6.1.4.1.9.9.74.1.6.1.1.11	INTEGER	read-only	This object specifies which of the two end stations initiated the establishment of this circuit.
OCT cdeFastS1CacheId	1.3.6.1.4.1.9.9.74.1.6.1.1.7	OCTET STRING	read-only	The 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.
NUM cdeFastS1IfIndex	1.3.6.1.4.1.9.9.74.1.6.1.1.5	InterfaceIndex	read-only	The ifEntry index of the local interface through which S1 can be reached.
ADR cdeFastS1Mac	1.3.6.1.4.1.9.9.74.1.6.1.1.1	MacAddressNC	not-accessible	The MAC Address of End Station 1 (S1) used for this cache entry.
OCT cdeFastS1RouteInfo	1.3.6.1.4.1.9.9.74.1.6.1.1.6	OCTET STRING	read-only	If 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.
SAP cdeFastS1Sap	1.3.6.1.4.1.9.9.74.1.6.1.1.2	SAPType	not-accessible	The SAP at End Station 1 (S1) used for this cache entry.
OCT cdeFastS2CacheId	1.3.6.1.4.1.9.9.74.1.6.1.1.10	OCTET STRING	read-only	The 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.
ADR cdeFastS2Mac	1.3.6.1.4.1.9.9.74.1.6.1.1.3	MacAddressNC	not-accessible	The MAC Address of End Station 2 (S2) used for this cache entry.
SAP cdeFastS2Sap	1.3.6.1.4.1.9.9.74.1.6.1.1.4	SAPType	not-accessible	The SAP at End Station 2 (S2) used for this cache entry.
ADR cdeFastS2TAddress	1.3.6.1.4.1.9.9.74.1.6.1.1.9	TAddress	read-only	This object contains the transport address of the partner DLSw.
OID cdeFastS2TDomain	1.3.6.1.4.1.9.9.74.1.6.1.1.8	OBJECT IDENTIFIER	read-only	This object contains the transport domain of the peer transport protocol that the fast cache entry is running over.
cdeFastTable	1.3.6.1.4.1.9.9.74.1.6.1		not-accessible	A 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.
TIK cdeFastTimeToLive	1.3.6.1.4.1.9.9.74.1.6.1.1.12	TimeTicks	read-only	The 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.
cdeFSTDomain	1.3.6.1.4.1.9.9.74.1.1.1
cdeIfEntry	1.3.6.1.4.1.9.9.74.1.4.1.1		not-accessible	Each conceptual row represents an interface.
cdeIfTable	1.3.6.1.4.1.9.9.74.1.4.1		not-accessible	The list of interfaces on which DLSw is active. This table augments dlswIfTable.
DLC cdeIfType	1.3.6.1.4.1.9.9.74.1.4.1.1.1	DlcType	read-only	The DLC protocol in use on this DLSw interface.
cdeInterface	1.3.6.1.4.1.9.9.74.1.4
cdeLlc2Domain	1.3.6.1.4.1.9.9.74.1.1.4
cdeMIBCircuitGroup	1.3.6.1.4.1.9.9.74.3.2.7			Conformance group for DLSw circuits.
cdeMIBCompliance	1.3.6.1.4.1.9.9.74.3.1.1			The compliance statement for all Cisco DLSw+ implementations.
cdeMIBCompliances	1.3.6.1.4.1.9.9.74.3.1
cdeMIBConformance	1.3.6.1.4.1.9.9.74.3
cdeMIBFastGroup	1.3.6.1.4.1.9.9.74.3.2.8			Conformance group for DLSw Fast Cache entries.
cdeMIBGroups	1.3.6.1.4.1.9.9.74.3.2
cdeMIBInterfaceGroup	1.3.6.1.4.1.9.9.74.3.2.6			Conformance group for DLSw interfaces.
cdeMIBNodeGroup	1.3.6.1.4.1.9.9.74.3.2.1			Conformance group for DLSw Node general information.
cdeMIBTConnConfigGroup	1.3.6.1.4.1.9.9.74.3.2.2			Conformance group for the configuration of transport connections.
cdeMIBTConnDirectConfigGroup	1.3.6.1.4.1.9.9.74.3.2.5			Conformance group for configuration information for transport connections using Direct or FST.
cdeMIBTConnOperGroup	1.3.6.1.4.1.9.9.74.3.2.3			Conformance group for operation information for transport connections.
cdeMIBTConnTcpConfigGroup	1.3.6.1.4.1.9.9.74.3.2.4			Conformance group for configuration information for transport connections using TCP.
cdeNode	1.3.6.1.4.1.9.9.74.1.2
T/F cdeNodeBiuSegment	1.3.6.1.4.1.9.9.74.1.2.7	TruthValue	read-write	This 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.
T/F cdeNodeBorder	1.3.6.1.4.1.9.9.74.1.2.3	TruthValue	read-write	This 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.
COS cdeNodeCost	1.3.6.1.4.1.9.9.74.1.2.4	Cost	read-write	Peer 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.
INT cdeNodeGroup	1.3.6.1.4.1.9.9.74.1.2.2	INTEGER	read-write	Peer 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.
INT cdeNodeInitPacingWindow	1.3.6.1.4.1.9.9.74.1.2.8	INTEGER	read-write	Initial 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.
NUM cdeNodeKeepaliveInterval	1.3.6.1.4.1.9.9.74.1.2.5	KeepaliveInterval	read-write	Default 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.
INT cdeNodeMaxPacingWindow	1.3.6.1.4.1.9.9.74.1.2.9	INTEGER	read-write	Maximum 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.
T/F cdeNodePassiveConnect	1.3.6.1.4.1.9.9.74.1.2.6	TruthValue	read-write	This 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 connection
COS cdeNodePeerOnDemandDefaultsCost	1.3.6.1.4.1.9.9.74.1.2.16	Cost	read-write	This 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.
T/F cdeNodePeerOnDemandDefaultsFst	1.3.6.1.4.1.9.9.74.1.2.17	TruthValue	read-write	This 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.
INT cdeNodePeerOnDemandDefaultsInactivityInterval	1.3.6.1.4.1.9.9.74.1.2.18	INTEGER	read-write	This 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.
NUM cdeNodePeerOnDemandDefaultsKeepaliveInterval	1.3.6.1.4.1.9.9.74.1.2.19	KeepaliveInterval	read-write	Default 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.
LFS cdeNodePeerOnDemandDefaultsLFSize	1.3.6.1.4.1.9.9.74.1.2.20	LFSize	read-write	The 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).
T/F cdeNodePeerOnDemandDefaultsPriority	1.3.6.1.4.1.9.9.74.1.2.21	TruthValue	read-write	This 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.
TCP cdeNodePeerOnDemandDefaultsTCPQueueMax	1.3.6.1.4.1.9.9.74.1.2.22	TCPQueueMax	read-write	Default 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.
T/F cdeNodePromiscuous	1.3.6.1.4.1.9.9.74.1.2.10	TruthValue	read-write	This 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.
COS cdeNodePromPeerDefaultsCost	1.3.6.1.4.1.9.9.74.1.2.11	Cost	read-write	This 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.
ADR cdeNodePromPeerDefaultsDestMac	1.3.6.1.4.1.9.9.74.1.2.12	MacAddressNC	read-write	Permits 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.
NUM cdeNodePromPeerDefaultsKeepaliveInterval	1.3.6.1.4.1.9.9.74.1.2.13	KeepaliveInterval	read-write	Default 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.
LFS cdeNodePromPeerDefaultsLFSize	1.3.6.1.4.1.9.9.74.1.2.14	LFSize	read-write	The 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).
TCP cdeNodePromPeerDefaultsTCPQueueMax	1.3.6.1.4.1.9.9.74.1.2.15	TCPQueueMax	read-write	Default 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.
ADR cdeNodeTAddr	1.3.6.1.4.1.9.9.74.1.2.1	TAddress	read-write	The 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.
cdeTConn	1.3.6.1.4.1.9.9.74.1.3
T/F cdeTConnConfigBackup	1.3.6.1.4.1.9.9.74.1.3.1.1.6	TruthValue	read-create	This 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.
T/F cdeTConnConfigBackupLinger	1.3.6.1.4.1.9.9.74.1.3.1.1.8	TruthValue	read-create	This 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.
INT cdeTConnConfigBackupLingerInterval	1.3.6.1.4.1.9.9.74.1.3.1.1.9	INTEGER	read-create	This 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.
ADR cdeTConnConfigBackupTAddr	1.3.6.1.4.1.9.9.74.1.3.1.1.7	TAddress	read-create	The primary peer's IP address that this entry backs up. Valid only when ciscoDlswTConnConfigBackup is true.
COS cdeTConnConfigCost	1.3.6.1.4.1.9.9.74.1.3.1.1.3	Cost	read-create	The 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.
ADR cdeTConnConfigDestMac	1.3.6.1.4.1.9.9.74.1.3.1.1.11	MacAddressNC	read-create	Permits 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.
T/F cdeTConnConfigDynamic	1.3.6.1.4.1.9.9.74.1.3.1.1.12	TruthValue	read-create	Indicates the peer connection is to be established only when there is DLSw+ data to send.
INT cdeTConnConfigDynamicInactivityInterval	1.3.6.1.4.1.9.9.74.1.3.1.1.14	INTEGER	read-create	Indicates 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.
INT cdeTConnConfigDynamicNoLlc	1.3.6.1.4.1.9.9.74.1.3.1.1.13	INTEGER	read-create	This variable indicates the length of time a dynamic peer remains connected after all LLC2 circuits are gone.
cdeTConnConfigEntry	1.3.6.1.4.1.9.9.74.1.3.1.1		not-accessible	A list of objects that define specific configuration for a DLSw peer transport connection.
NUM cdeTConnConfigKeepaliveInterval	1.3.6.1.4.1.9.9.74.1.3.1.1.5	KeepaliveInterval	read-create	The 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.
LFS cdeTConnConfigLFSize	1.3.6.1.4.1.9.9.74.1.3.1.1.4	LFSize	read-create	The 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).
T/F cdeTConnConfigLocalAck	1.3.6.1.4.1.9.9.74.1.3.1.1.2	TruthValue	read-create	Reflects 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.
T/F cdeTConnConfigPriority	1.3.6.1.4.1.9.9.74.1.3.1.1.10	TruthValue	read-create	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.
cdeTConnConfigTable	1.3.6.1.4.1.9.9.74.1.3.1		not-accessible	This 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.
NUM cdeTConnConfigTDomainType	1.3.6.1.4.1.9.9.74.1.3.1.1.1	TDomainType	read-create	The type of DLSw encapsulation in use on this peer connection.
cdeTConnDirect	1.3.6.1.4.1.9.9.74.1.3.3.2
cdeTConnDirectConfigEntry	1.3.6.1.4.1.9.9.74.1.3.3.2.1.1		not-accessible	Each conceptual row defines parameters that are specific to peer transport connections whose domain is either cdeDirectHdlcDomain, cdeDirectFrameRelayDomain, or cdeLlc2Domain.
DLC cdeTConnDirectConfigFrameRelayDlci	1.3.6.1.4.1.9.9.74.1.3.3.2.1.1.3	DlciNumber	read-create	The Data Link Connection Identifier for the virtual circuit on this interface. This object will only be valid if the value of cdeTConnDirectConfigMediaEncap is llc2.
NUM cdeTConnDirectConfigIfIndex	1.3.6.1.4.1.9.9.74.1.3.3.2.1.1.1	InterfaceIndex	read-create	The IfEntry index of the local interface, on which the direct peer can be reached.
INT cdeTConnDirectConfigMediaEncap	1.3.6.1.4.1.9.9.74.1.3.3.2.1.1.2	INTEGER	read-create	The 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.
cdeTConnDirectConfigTable	1.3.6.1.4.1.9.9.74.1.3.3.2.1		not-accessible	This 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).
cdeTConnOperEntry	1.3.6.1.4.1.9.9.74.1.3.2.1		not-accessible	A list of objects that contain spefific operational information for a DLSw peer transport connection.
T/F cdeTConnOperPartnerBorderPeer	1.3.6.1.4.1.9.9.74.1.3.2.1.3	TruthValue	read-only	This 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.
COS cdeTConnOperPartnerCost	1.3.6.1.4.1.9.9.74.1.3.2.1.1	Cost	read-only	The 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.
INT cdeTConnOperPartnerGroupNum	1.3.6.1.4.1.9.9.74.1.3.2.1.4	INTEGER	read-only	This 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.
T/F cdeTConnOperPartnerPriority	1.3.6.1.4.1.9.9.74.1.3.2.1.2	TruthValue	read-only	The 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.
cdeTConnOperTable	1.3.6.1.4.1.9.9.74.1.3.2		not-accessible	A 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.
NUM cdeTConnOperTDomainType	1.3.6.1.4.1.9.9.74.1.3.2.1.5	TDomainType	read-only	The type of DLSw encapsulation in use on this peer connection.
cdeTConnSpecific	1.3.6.1.4.1.9.9.74.1.3.3
cdeTConnTcp	1.3.6.1.4.1.9.9.74.1.3.3.1
cdeTConnTcpConfigEntry	1.3.6.1.4.1.9.9.74.1.3.3.1.1.1		not-accessible	A list of objects that define spefific configuration for a DLSw peer transport connection within the dlswTCPDomain. dlswTCPDomain is imported from DLSW-MIB (RFC 2024).
TCP cdeTConnTcpConfigQueueMax	1.3.6.1.4.1.9.9.74.1.3.3.1.1.1.1	TCPQueueMax	read-create	Maximum 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.
cdeTConnTcpConfigTable	1.3.6.1.4.1.9.9.74.1.3.3.1.1		not-accessible	This 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.
NTF cdeTrapCircuitUpDown	1.3.6.1.4.1.9.9.74.2.0.2			This trap is sent each time a circuit changes state to `connected' or `disconnected'. the emission of this trap is controlled by cdeTrapCntlCircuit.
T/F cdeTrapCntlCircuit	1.3.6.1.4.1.9.9.74.1.7.2	TruthValue	read-write	Indicates 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.
T/F cdeTrapCntlTConn	1.3.6.1.4.1.9.9.74.1.7.1	TruthValue	read-write	Indicates 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.
cdeTrapControl	1.3.6.1.4.1.9.9.74.1.7
cdeTrapControlGroup	1.3.6.1.4.1.9.9.74.3.2.9			Conformance group for DLSw Trap Control.
cdeTraps	1.3.6.1.4.1.9.9.74.2.0
cdeTrapsPrefix	1.3.6.1.4.1.9.9.74.2
NTF cdeTrapTConnUpDown	1.3.6.1.4.1.9.9.74.2.0.1			This trap is sent each time a transport connection changes state to `connected' or `disconnected'. The emission of this trap is controlled by cdeTrapCntlTConn.
ciscoDlswExtMIB	1.3.6.1.4.1.9.9.74			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.
ciscoDlswExtMIBObjects	1.3.6.1.4.1.9.9.74.1

RFC description

Cisco Data Link Switching Plus extensions for SNA and NetBIOS traffic over IP networks.

Start monitoring Cisco routers (DLSw+ SNA/NetBIOS over IP, legacy) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download CISCO-DLSW-EXT-MIB

What Is CISCO-DLSW-EXT-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description