CISCO-DLSW-EXT-MIB

File: CISCO-DLSW-EXT-MIB.mib (63782 bytes)

Imported modules

SNMPv2-SMI SNMPv2-CONF SNMPv2-TC
IF-MIB DLSW-MIB CISCO-FRAME-RELAY-MIB
CISCO-TC CISCO-SMI

Imported symbols

MODULE-IDENTITY OBJECT-TYPE NOTIFICATION-TYPE
TimeTicks MODULE-COMPLIANCE OBJECT-GROUP
TruthValue TEXTUAL-CONVENTION DisplayString
InterfaceIndex dlswTConnConfigEntry dlswTConnOperEntry
dlswTConnTcpConfigEntry dlswIfEntry dlswCircuitEntry
dlswTConnConfigIndex DlcType TAddress
MacAddressNC LFSize dlswTConnOperState
dlswCircuitState DlciNumber SAPType
ciscoMgmt

Defined Types

TDomainType  
The type of DLSw encapsulation in use on this peer connection.
TEXTUAL-CONVENTION    
  INTEGER tcp(1), fst(2), directHdlc(3), directFrameRelay(4), llc2(5)  

Cost  
Allows a cost to be assigned to 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.
TEXTUAL-CONVENTION    
  INTEGER 1..5  

KeepaliveInterval  
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. The keepalive interval is measured in seconds. If set to zero, no keepalives are sent.
TEXTUAL-CONVENTION    
  INTEGER 0..1200  

TCPQueueMax  
For DLSw over TCP encapsulation, packets may be queued due to congestion of the TCP network. The TCPQueueMax is used to set the output queue maximum of the underlying TCP connection.
TEXTUAL-CONVENTION    
  INTEGER 25..2000  

CdeTConnConfigEntry  
SEQUENCE    
  cdeTConnConfigTDomainType TDomainType
  cdeTConnConfigLocalAck TruthValue
  cdeTConnConfigCost Cost
  cdeTConnConfigLFSize LFSize
  cdeTConnConfigKeepaliveInterval KeepaliveInterval
  cdeTConnConfigBackup TruthValue
  cdeTConnConfigBackupTAddr TAddress
  cdeTConnConfigBackupLinger TruthValue
  cdeTConnConfigBackupLingerInterval INTEGER
  cdeTConnConfigPriority TruthValue
  cdeTConnConfigDestMac MacAddressNC
  cdeTConnConfigDynamic TruthValue
  cdeTConnConfigDynamicNoLlc INTEGER
  cdeTConnConfigDynamicInactivityInterval INTEGER

CdeTConnOperEntry  
SEQUENCE    
  cdeTConnOperPartnerCost Cost
  cdeTConnOperPartnerPriority TruthValue
  cdeTConnOperPartnerBorderPeer TruthValue
  cdeTConnOperPartnerGroupNum INTEGER
  cdeTConnOperTDomainType TDomainType

CdeTConnTcpConfigEntry  
SEQUENCE    
  cdeTConnTcpConfigQueueMax TCPQueueMax

CdeTConnDirectConfigEntry  
SEQUENCE    
  cdeTConnDirectConfigIfIndex InterfaceIndex
  cdeTConnDirectConfigMediaEncap INTEGER
  cdeTConnDirectConfigFrameRelayDlci DlciNumber

CdeIfEntry  
SEQUENCE    
  cdeIfType DlcType

CdeCircuitEntry  
SEQUENCE    
  cdeCircuitS1Name DisplayString Size(0..17)
  cdeCircuitS2Name DisplayString Size(0..17)
  cdeCircuitS1IdBlock DisplayString Size(0..3)
  cdeCircuitS1IdNum DisplayString Size(0..5)

CdeFastEntry  
SEQUENCE    
  cdeFastS1Mac MacAddressNC
  cdeFastS1Sap SAPType
  cdeFastS2Mac MacAddressNC
  cdeFastS2Sap SAPType
  cdeFastS1IfIndex InterfaceIndex
  cdeFastS1RouteInfo OCTET STRING
  cdeFastS1CacheId OCTET STRING
  cdeFastS2TDomain OBJECT IDENTIFIER
  cdeFastS2TAddress TAddress
  cdeFastS2CacheId OCTET STRING
  cdeFastOrigin INTEGER
  cdeFastTimeToLive TimeTicks

Defined Values

ciscoDlswExtMIB 2.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.
MODULE-IDENTITY    

ciscoDlswExtMIBObjects 2.9.74.1
OBJECT IDENTIFIER    

cdeDomains 2.9.74.1.1
OBJECT IDENTIFIER    

cdeNode 2.9.74.1.2
OBJECT IDENTIFIER    

cdeTConn 2.9.74.1.3
OBJECT IDENTIFIER    

cdeInterface 2.9.74.1.4
OBJECT IDENTIFIER    

cdeCircuit 2.9.74.1.5
OBJECT IDENTIFIER    

cdeFast 2.9.74.1.6
OBJECT IDENTIFIER    

cdeTrapControl 2.9.74.1.7
OBJECT IDENTIFIER    

cdeFSTDomain 2.9.74.1.1.1
OBJECT IDENTIFIER    

cdeDirectHdlcDomain 2.9.74.1.1.2
OBJECT IDENTIFIER    

cdeDirectFrameRelayDomain 2.9.74.1.1.3
OBJECT IDENTIFIER    

cdeLlc2Domain 2.9.74.1.1.4
OBJECT IDENTIFIER    

cdeNodeTAddr 2.9.74.1.2.1
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.
OBJECT-TYPE    
  TAddress  

cdeNodeGroup 2.9.74.1.2.2
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.
OBJECT-TYPE    
  INTEGER 0..255  

cdeNodeBorder 2.9.74.1.2.3
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.
OBJECT-TYPE    
  TruthValue  

cdeNodeCost 2.9.74.1.2.4
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.
OBJECT-TYPE    
  Cost  

cdeNodeKeepaliveInterval 2.9.74.1.2.5
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.
OBJECT-TYPE    
  KeepaliveInterval  

cdeNodePassiveConnect 2.9.74.1.2.6
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
OBJECT-TYPE    
  TruthValue  

cdeNodeBiuSegment 2.9.74.1.2.7
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.
OBJECT-TYPE    
  TruthValue  

cdeNodeInitPacingWindow 2.9.74.1.2.8
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.
OBJECT-TYPE    
  INTEGER 1..2000  

cdeNodeMaxPacingWindow 2.9.74.1.2.9
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.
OBJECT-TYPE    
  INTEGER 1..2000  

cdeNodePromiscuous 2.9.74.1.2.10
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.
OBJECT-TYPE    
  TruthValue  

cdeNodePromPeerDefaultsCost 2.9.74.1.2.11
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.
OBJECT-TYPE    
  Cost  

cdeNodePromPeerDefaultsDestMac 2.9.74.1.2.12
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.
OBJECT-TYPE    
  MacAddressNC  

cdeNodePromPeerDefaultsKeepaliveInterval 2.9.74.1.2.13
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.
OBJECT-TYPE    
  KeepaliveInterval  

cdeNodePromPeerDefaultsLFSize 2.9.74.1.2.14
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).
OBJECT-TYPE    
  LFSize  

cdeNodePromPeerDefaultsTCPQueueMax 2.9.74.1.2.15
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.
OBJECT-TYPE    
  TCPQueueMax  

cdeNodePeerOnDemandDefaultsCost 2.9.74.1.2.16
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.
OBJECT-TYPE    
  Cost  

cdeNodePeerOnDemandDefaultsFst 2.9.74.1.2.17
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.
OBJECT-TYPE    
  TruthValue  

cdeNodePeerOnDemandDefaultsInactivityInterval 2.9.74.1.2.18
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.
OBJECT-TYPE    
  INTEGER 0..1440  

cdeNodePeerOnDemandDefaultsKeepaliveInterval 2.9.74.1.2.19
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.
OBJECT-TYPE    
  KeepaliveInterval  

cdeNodePeerOnDemandDefaultsLFSize 2.9.74.1.2.20
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).
OBJECT-TYPE    
  LFSize  

cdeNodePeerOnDemandDefaultsPriority 2.9.74.1.2.21
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.
OBJECT-TYPE    
  TruthValue  

cdeNodePeerOnDemandDefaultsTCPQueueMax 2.9.74.1.2.22
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.
OBJECT-TYPE    
  TCPQueueMax  

cdeTConnConfigTable 2.9.74.1.3.1
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.
OBJECT-TYPE    
  SEQUENCE OF  
    CdeTConnConfigEntry

cdeTConnConfigEntry 2.9.74.1.3.1.1
A list of objects that define specific configuration for a DLSw peer transport connection.
OBJECT-TYPE    
  CdeTConnConfigEntry  

cdeTConnConfigTDomainType 2.9.74.1.3.1.1.1
The type of DLSw encapsulation in use on this peer connection.
OBJECT-TYPE    
  TDomainType  

cdeTConnConfigLocalAck 2.9.74.1.3.1.1.2
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.
OBJECT-TYPE    
  TruthValue  

cdeTConnConfigCost 2.9.74.1.3.1.1.3
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.
OBJECT-TYPE    
  Cost  

cdeTConnConfigLFSize 2.9.74.1.3.1.1.4
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).
OBJECT-TYPE    
  LFSize  

cdeTConnConfigKeepaliveInterval 2.9.74.1.3.1.1.5
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.
OBJECT-TYPE    
  KeepaliveInterval  

cdeTConnConfigBackup 2.9.74.1.3.1.1.6
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.
OBJECT-TYPE    
  TruthValue  

cdeTConnConfigBackupTAddr 2.9.74.1.3.1.1.7
The primary peer's IP address that this entry backs up. Valid only when ciscoDlswTConnConfigBackup is true.
OBJECT-TYPE    
  TAddress  

cdeTConnConfigBackupLinger 2.9.74.1.3.1.1.8
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.
OBJECT-TYPE    
  TruthValue  

cdeTConnConfigBackupLingerInterval 2.9.74.1.3.1.1.9
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.
OBJECT-TYPE    
  INTEGER 0..1440  

cdeTConnConfigPriority 2.9.74.1.3.1.1.10
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.
OBJECT-TYPE    
  TruthValue  

cdeTConnConfigDestMac 2.9.74.1.3.1.1.11
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.
OBJECT-TYPE    
  MacAddressNC  

cdeTConnConfigDynamic 2.9.74.1.3.1.1.12
Indicates the peer connection is to be established only when there is DLSw+ data to send.
OBJECT-TYPE    
  TruthValue  

cdeTConnConfigDynamicNoLlc 2.9.74.1.3.1.1.13
This variable indicates the length of time a dynamic peer remains connected after all LLC2 circuits are gone.
OBJECT-TYPE    
  INTEGER 1..300  

cdeTConnConfigDynamicInactivityInterval 2.9.74.1.3.1.1.14
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.
OBJECT-TYPE    
  INTEGER 0..300  

cdeTConnOperTable 2.9.74.1.3.2
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.
OBJECT-TYPE    
  SEQUENCE OF  
    CdeTConnOperEntry

cdeTConnOperEntry 2.9.74.1.3.2.1
A list of objects that contain spefific operational information for a DLSw peer transport connection.
OBJECT-TYPE    
  CdeTConnOperEntry  

cdeTConnOperPartnerCost 2.9.74.1.3.2.1.1
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.
OBJECT-TYPE    
  Cost  

cdeTConnOperPartnerPriority 2.9.74.1.3.2.1.2
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.
OBJECT-TYPE    
  TruthValue  

cdeTConnOperPartnerBorderPeer 2.9.74.1.3.2.1.3
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.
OBJECT-TYPE    
  TruthValue  

cdeTConnOperPartnerGroupNum 2.9.74.1.3.2.1.4
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.
OBJECT-TYPE    
  INTEGER 0..255  

cdeTConnOperTDomainType 2.9.74.1.3.2.1.5
The type of DLSw encapsulation in use on this peer connection.
OBJECT-TYPE    
  TDomainType  

cdeTConnSpecific 2.9.74.1.3.3
OBJECT IDENTIFIER    

cdeTConnTcp 2.9.74.1.3.3.1
OBJECT IDENTIFIER    

cdeTConnDirect 2.9.74.1.3.3.2
OBJECT IDENTIFIER    

cdeTConnTcpConfigTable 2.9.74.1.3.3.1.1
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.
OBJECT-TYPE    
  SEQUENCE OF  
    CdeTConnTcpConfigEntry

cdeTConnTcpConfigEntry 2.9.74.1.3.3.1.1.1
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).
OBJECT-TYPE    
  CdeTConnTcpConfigEntry  

cdeTConnTcpConfigQueueMax 2.9.74.1.3.3.1.1.1.1
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.
OBJECT-TYPE    
  TCPQueueMax  

cdeTConnDirectConfigTable 2.9.74.1.3.3.2.1
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).
OBJECT-TYPE    
  SEQUENCE OF  
    CdeTConnDirectConfigEntry

cdeTConnDirectConfigEntry 2.9.74.1.3.3.2.1.1
Each conceptual row defines parameters that are specific to peer transport connections whose domain is either cdeDirectHdlcDomain, cdeDirectFrameRelayDomain, or cdeLlc2Domain.
OBJECT-TYPE    
  CdeTConnDirectConfigEntry  

cdeTConnDirectConfigIfIndex 2.9.74.1.3.3.2.1.1.1
The IfEntry index of the local interface, on which the direct peer can be reached.
OBJECT-TYPE    
  InterfaceIndex  

cdeTConnDirectConfigMediaEncap 2.9.74.1.3.3.2.1.1.2
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.
OBJECT-TYPE    
  INTEGER directHdlc(1), directFrameRelay(2), llc2(3)  

cdeTConnDirectConfigFrameRelayDlci 2.9.74.1.3.3.2.1.1.3
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.
OBJECT-TYPE    
  DlciNumber  

cdeIfTable 2.9.74.1.4.1
The list of interfaces on which DLSw is active. This table augments dlswIfTable.
OBJECT-TYPE    
  SEQUENCE OF  
    CdeIfEntry

cdeIfEntry 2.9.74.1.4.1.1
Each conceptual row represents an interface.
OBJECT-TYPE    
  CdeIfEntry  

cdeIfType 2.9.74.1.4.1.1.1
The DLC protocol in use on this DLSw interface.
OBJECT-TYPE    
  DlcType  

cdeCircuitTable 2.9.74.1.5.1
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.
OBJECT-TYPE    
  SEQUENCE OF  
    CdeCircuitEntry

cdeCircuitEntry 2.9.74.1.5.1.1
A list of objects that contain specific information for a DLSw circuit.
OBJECT-TYPE    
  CdeCircuitEntry  

cdeCircuitS1Name 2.9.74.1.5.1.1.1
Represents the PU Name of End Station 1 (S1), if available.
OBJECT-TYPE    
  DisplayString Size(0..17)  

cdeCircuitS2Name 2.9.74.1.5.1.1.2
Represents the PU Name of End Station 2 (S2), if available.
OBJECT-TYPE    
  DisplayString Size(0..17)  

cdeCircuitS1IdBlock 2.9.74.1.5.1.1.3
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.
OBJECT-TYPE    
  DisplayString Size(0..3)  

cdeCircuitS1IdNum 2.9.74.1.5.1.1.4
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.
OBJECT-TYPE    
  DisplayString Size(0..5)  

cdeFastTable 2.9.74.1.6.1
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.
OBJECT-TYPE    
  SEQUENCE OF  
    CdeFastEntry

cdeFastEntry 2.9.74.1.6.1.1
A list of objects that define specific information for a DLSw fast cache entry.
OBJECT-TYPE    
  CdeFastEntry  

cdeFastS1Mac 2.9.74.1.6.1.1.1
The MAC Address of End Station 1 (S1) used for this cache entry.
OBJECT-TYPE    
  MacAddressNC  

cdeFastS1Sap 2.9.74.1.6.1.1.2
The SAP at End Station 1 (S1) used for this cache entry.
OBJECT-TYPE    
  SAPType  

cdeFastS2Mac 2.9.74.1.6.1.1.3
The MAC Address of End Station 2 (S2) used for this cache entry.
OBJECT-TYPE    
  MacAddressNC  

cdeFastS2Sap 2.9.74.1.6.1.1.4
The SAP at End Station 2 (S2) used for this cache entry.
OBJECT-TYPE    
  SAPType  

cdeFastS1IfIndex 2.9.74.1.6.1.1.5
The ifEntry index of the local interface through which S1 can be reached.
OBJECT-TYPE    
  InterfaceIndex  

cdeFastS1RouteInfo 2.9.74.1.6.1.1.6
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.
OBJECT-TYPE    
  OCTET STRING Size(0..30)  

cdeFastS1CacheId 2.9.74.1.6.1.1.7
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.
OBJECT-TYPE    
  OCTET STRING Size(8)  

cdeFastS2TDomain 2.9.74.1.6.1.1.8
This object contains the transport domain of the peer transport protocol that the fast cache entry is running over.
OBJECT-TYPE    
  OBJECT IDENTIFIER  

cdeFastS2TAddress 2.9.74.1.6.1.1.9
This object contains the transport address of the partner DLSw.
OBJECT-TYPE    
  TAddress  

cdeFastS2CacheId 2.9.74.1.6.1.1.10
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.
OBJECT-TYPE    
  OCTET STRING Size(8)  

cdeFastOrigin 2.9.74.1.6.1.1.11
This object specifies which of the two end stations initiated the establishment of this circuit.
OBJECT-TYPE    
  INTEGER s1(1), s2(2)  

cdeFastTimeToLive 2.9.74.1.6.1.1.12
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.
OBJECT-TYPE    
  TimeTicks  

cdeTrapCntlTConn 2.9.74.1.7.1
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.
OBJECT-TYPE    
  TruthValue  

cdeTrapCntlCircuit 2.9.74.1.7.2
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.
OBJECT-TYPE    
  TruthValue  

cdeTrapsPrefix 2.9.74.2
OBJECT IDENTIFIER    

cdeTraps 2.9.74.2.0
OBJECT IDENTIFIER    

cdeTrapTConnUpDown 2.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.
NOTIFICATION-TYPE    

cdeTrapCircuitUpDown 2.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.
NOTIFICATION-TYPE    

cdeMIBConformance 2.9.74.3
OBJECT IDENTIFIER    

cdeMIBCompliances 2.9.74.3.1
OBJECT IDENTIFIER    

cdeMIBGroups 2.9.74.3.2
OBJECT IDENTIFIER    

cdeMIBCompliance 2.9.74.3.1.1
The compliance statement for all Cisco DLSw+ implementations.
MODULE-COMPLIANCE    

cdeMIBNodeGroup 2.9.74.3.2.1
Conformance group for DLSw Node general information.
OBJECT-GROUP    

cdeMIBTConnConfigGroup 2.9.74.3.2.2
Conformance group for the configuration of transport connections.
OBJECT-GROUP    

cdeMIBTConnOperGroup 2.9.74.3.2.3
Conformance group for operation information for transport connections.
OBJECT-GROUP    

cdeMIBTConnTcpConfigGroup 2.9.74.3.2.4
Conformance group for configuration information for transport connections using TCP.
OBJECT-GROUP    

cdeMIBTConnDirectConfigGroup 2.9.74.3.2.5
Conformance group for configuration information for transport connections using Direct or FST.
OBJECT-GROUP    

cdeMIBInterfaceGroup 2.9.74.3.2.6
Conformance group for DLSw interfaces.
OBJECT-GROUP    

cdeMIBCircuitGroup 2.9.74.3.2.7
Conformance group for DLSw circuits.
OBJECT-GROUP    

cdeMIBFastGroup 2.9.74.3.2.8
Conformance group for DLSw Fast Cache entries.
OBJECT-GROUP    

cdeTrapControlGroup 2.9.74.3.2.9
Conformance group for DLSw Trap Control.
OBJECT-GROUP