CISCO-CDL-MIB

        This MIB module defines objects to manage Converged Data Link
(CDL).
        
CDL provides OAM&P (Operation, Administration, Maintenance and
Provisioning) in Ethernet packet-based optical networks without
a SONET/SDH layer.
        
The CDL functionality can be divided into the following
categories:
        
APS/Defect Indications:
   The CDL frame carries defect indication bits and provides
   signalling mechanism support for automatic protection
   switching.
        
Message Channel:
   The message channel is used to carry control (e.g. routing,
   signalling) and management traffic.
        
Packet-by-packet multiplexing of multiple data flows:
   CDL uses one or two octets to identify the elementary 
   packet stream that this packet belongs to. This allows 
   more than one elementary packet stream to share the 
   bandwidth on a CDL enabled interface.
        
This MIB defines objects to manage Defect Indications and the
Packet-by-packet Multiplexing feature.
        
The CDL Message channel is modeled as a separate interface and
should be controlled using the IF-MIB and other MIBs for
managing IP. This MIB does not provide a mechanism to manage
the CDL message channel.
        
APS configuration and monitoring can be done using the
CISCO-APS-MIB and CISCO-APS-EXT-MIB.
    
Source file
CISCO-CDL-MIB
Last revised
Identity
ciscoCdlMIB
Base OID
1.3.6.1.4.1.9.10.88
Imported Objects
CISCO-SMI ciscoExperiment
IF-MIB ifIndex
SNMPv2-CONF MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI Counter32 Counter64 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) Unsigned32
SNMPv2-TC TEXTUAL-CONVENTION (no object page) TimeStamp TruthValue
Net-SNMP examples using the cisco MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'CISCO-CDL-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-CDL-MIB::ciscoCdlMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-CDL-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-CDL-MIB::ciscoCdlMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (43)
.1.3.6.1.4.1.9.10.88
.1.3.6.1.4.1.9.10.88.0
.1.3.6.1.4.1.9.10.88.1
.1.3.6.1.4.1.9.10.88.1.1
.1.3.6.1.4.1.9.10.88.1.1.1
.1.3.6.1.4.1.9.10.88.1.1.1.1
.1.3.6.1.4.1.9.10.88.1.1.1.1.1
.1.3.6.1.4.1.9.10.88.1.1.1.1.10
.1.3.6.1.4.1.9.10.88.1.1.1.1.11
.1.3.6.1.4.1.9.10.88.1.1.1.1.12
.1.3.6.1.4.1.9.10.88.1.1.1.1.13
.1.3.6.1.4.1.9.10.88.1.1.1.1.14
.1.3.6.1.4.1.9.10.88.1.1.1.1.15
.1.3.6.1.4.1.9.10.88.1.1.1.1.16
.1.3.6.1.4.1.9.10.88.1.1.1.1.17
.1.3.6.1.4.1.9.10.88.1.1.1.1.18
.1.3.6.1.4.1.9.10.88.1.1.1.1.2
.1.3.6.1.4.1.9.10.88.1.1.1.1.3
.1.3.6.1.4.1.9.10.88.1.1.1.1.4
.1.3.6.1.4.1.9.10.88.1.1.1.1.5
.1.3.6.1.4.1.9.10.88.1.1.1.1.6
.1.3.6.1.4.1.9.10.88.1.1.1.1.7
.1.3.6.1.4.1.9.10.88.1.1.1.1.8
.1.3.6.1.4.1.9.10.88.1.1.1.1.9
Enumeration
.1.3.6.1.4.1.9.10.88.1.1.2
millisecondsUnsigned32
.1.3.6.1.4.1.9.10.88.1.1.3
millisecondsUnsigned32
.1.3.6.1.4.1.9.10.88.1.1.4
millisecondsUnsigned32
.1.3.6.1.4.1.9.10.88.1.1.5
.1.3.6.1.4.1.9.10.88.1.2
.1.3.6.1.4.1.9.10.88.1.2.1
.1.3.6.1.4.1.9.10.88.1.2.1.1
.1.3.6.1.4.1.9.10.88.1.2.1.1.1
.1.3.6.1.4.1.9.10.88.1.2.1.1.2
.1.3.6.1.4.1.9.10.88.1.2.1.1.3
.1.3.6.1.4.1.9.10.88.1.2.1.1.4
.1.3.6.1.4.1.9.10.88.1.2.1.1.5
.1.3.6.1.4.1.9.10.88.1.2.1.1.6
.1.3.6.1.4.1.9.10.88.1.2.1.1.7
.1.3.6.1.4.1.9.10.88.1.2.1.1.8
.1.3.6.1.4.1.9.10.88.1.2.1.1.9
.1.3.6.1.4.1.9.10.88.3
.1.3.6.1.4.1.9.10.88.3.1
.1.3.6.1.4.1.9.10.88.3.2
Dependencies (7) 5 direct · 2 transitive Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Dependency-first compile order
  1. SNMPv2-SMIrfc
  2. CISCO-SMIcisco
  3. SNMPv2-TCrfc
  4. IANAifType-MIBrfc
  5. SNMPv2-CONFrfc
  6. SNMPv2-MIBrfc
  7. IF-MIBrfc
  8. CISCO-CDL-MIBciscoselected
Type Definitions (4)
Bits
hopByHopForwardDefect(0)
hopByHopBackwardDefect(1)
endToEndAggPathForwardDefect(2)
Bits
endToEndPathImplicitFwdDefect(0)
endToEndPathBackwardDefect(1)
Unsigned32 range: 0..65535
Enumeration
endOfAggPath(1)
endOfHop(2)
cdlRegenerator(3)
Conformance Groups (8)
A collection of objects used to control and monitor CDL on an
Ethernet interface.
.1.3.6.1.4.1.9.10.88.3.2.1
A collection of objects used to manage packet-by-packet
multiplexing on a CDL enabled interface.
.1.3.6.1.4.1.9.10.88.3.2.2
A collection of objects to configure and monitor the status of
elementary packet streams at path terminating interfaces.
.1.3.6.1.4.1.9.10.88.3.2.3
A collection of objects to configure CDL aggregate defect
indication behavior.
.1.3.6.1.4.1.9.10.88.3.2.4
A collection of objects to monitor CDL aggregate defect
indications.
.1.3.6.1.4.1.9.10.88.3.2.5
A collection of notifications for CDL aggregate defect
indications.
.1.3.6.1.4.1.9.10.88.3.2.6
A collection of notifications for CDL flow defect indications.
.1.3.6.1.4.1.9.10.88.3.2.7
A collection of objects to configure and monitor the status of
elementary packet streams at path terminating interfaces.
.1.3.6.1.4.1.9.10.88.3.2.8
Compliance Statements (2)

OID .1.3.6.1.4.1.9.10.88.3.1.1
The Compliance statement for the Cisco CDL MIB.
Required groups
mandatory coCdlMIBBaseGroup
mandatory coCdlDIAggMandatoryGroup
mandatory coCdlDIAggNotifGroup
optional coCdlDIConfigGroup This group is required when CDL defect indication behavior
is configurable.
optional coCdlMIBFlowIdGroup This group is required when the network element supports
transport of CDL aggregate packet streams consisting of
multiple elementary packet streams.
optional coCdlMIBFlowTermGroup This group is required when the network element supports
termination of CDL packet-by-packet multiplexing, i.e.,
either the network element supports CDL packet-by-packet
multiplexing and can apply/remove the CDL Ethernet
encapsulation, or the network element contains interfaces
that support packet-by-packet multiplexing as well as
interfaces that do not support packet-by-packet
multiplexing.
optional coCdlDIFlowNotifGroup This group is required when the network element supports
termination of CDL packet-by-packet multiplexing, i.e.,
either the network element supports CDL packet-by-packet
multiplexing and can apply/remove the CDL Ethernet
encapsulation, or the network element contains interfaces
that support packet-by-packet multiplexing as well as
interfaces that do not support packet-by-packet
multiplexing.
Object refinements
ObjectAccessSyntaxDescription
coCdlAdminStatus readonly
Write access is required only when the presence of CDL is
configurable on an Ethernet interface.
coCdlDINotifyThrottleInterval readonly
Write access is required only when the notify throttle
interval is configurable.
coCdlDefectIndSetSoakInterval readonly
Write access is required only when the set soak interval
is configurable.
coCdlDefectIndClearSoakInterval readonly
Write access is required only when the clear soak interval
is configurable.
coCdlForceEndOfHop readonly
Write access is required only when the node behavior is
configurable.
coCdlTransmitMaxFlowIdentifier readonly
Write access is required only when the maximum transmitted
flow identifier value is configurable.
coCdlReceiveMaxFlowIdentifier readonly
Write access is required only when the maximum received
flow identifier value is configurable.
coCdlToCdlNetFlowIdentifier readonly
Write access is required only when the interface supports
configuration of the flow identifier value progressed
towards the CDL network.
coCdlFromCdlNetFlowIdentifier readonly
Write access is required only when the interface supports
configuration of the flow identifier value received from
the CDL network.

OID .1.3.6.1.4.1.9.10.88.3.1.2
The Compliance statement for the Cisco CDL MIB.
Required groups
mandatory coCdlMIBBaseGroup
mandatory coCdlDIAggMandatoryGroup
mandatory coCdlDIAggNotifGroup
optional coCdlDIConfigGroup This group is required when CDL defect indication behavior
is configurable.
optional coCdlMIBFlowIdGroup This group is required when the network element supports
transport of CDL aggregate packet streams consisting of
multiple elementary packet streams.
optional coCdlMIBFlowTerm2Group This group is required when the network element supports
termination of CDL packet-by-packet multiplexing, i.e.,
either the network element supports CDL packet-by-packet
multiplexing and can apply/remove the CDL Ethernet
encapsulation, or the network element contains interfaces
that support packet-by-packet multiplexing as well as
interfaces that do not support packet-by-packet
multiplexing.
optional coCdlDIFlowNotifGroup This group is required when the network element supports
termination of CDL packet-by-packet multiplexing, i.e.,
either the network element supports CDL packet-by-packet
multiplexing and can apply/remove the CDL Ethernet
encapsulation, or the network element contains interfaces
that support packet-by-packet multiplexing as well as
interfaces that do not support packet-by-packet
multiplexing.
Object refinements
ObjectAccessSyntaxDescription
coCdlAdminStatus readonly
Write access is required only when the presence of CDL is
configurable on an Ethernet interface.
coCdlDINotifyThrottleInterval readonly
Write access is required only when the notify throttle
interval is configurable.
coCdlDefectIndSetSoakInterval readonly
Write access is required only when the set soak interval
is configurable.
coCdlDefectIndClearSoakInterval readonly
Write access is required only when the clear soak interval
is configurable.
coCdlForceEndOfHop readonly
Write access is required only when the node behavior is
configurable.
coCdlTransmitMaxFlowIdentifier readonly
Write access is required only when the maximum transmitted
flow identifier value is configurable.
coCdlReceiveMaxFlowIdentifier readonly
Write access is required only when the maximum received
flow identifier value is configurable.
coCdlToCdlNetFlowIdentifier readonly
Write access is required only when the interface supports
configuration of the flow identifier value progressed
towards the CDL network.
coCdlFromCdlNetFlowIdentifier readonly
Write access is required only when the interface supports
configuration of the flow identifier value received from
the CDL network.
Notifications / Traps (2)
NameOIDDescription
.1.3.6.1.4.1.9.10.88.0.1
This notification is sent when the value of the hop-by-hop
forward defect indication (FDI-H), hop-by-hop backward defect
indication (BDI-H), or end-to-end (aggregate path) forward
defect indication (FDI-E) bit received on an interface changes.

To minimize the probability of prematurely reacting to
momentary signal variations, a soak time may be incorporated
into the notification in the following manner. A notification
is generated after a defect is first detected, when the defect
persists for a period of time that exceeds the set soak
interval specified by coCdlDefectIndSetSoakInterval. A
notification is generated after a defect stops being detected,
when the defect does not appear over a period of time that
exceeds the clear soak interval specified by
coCdlDefectIndClearSoakInterval.

When changes in CDL defect indications are received for
multiple interfaces within a short time span, notifications
should be deferred so that each notification is generated at
least one coCdlDINotifyThrottleInterval after the previous
notification.
.1.3.6.1.4.1.9.10.88.0.2
This notification is sent when the value of the received
end-to-end path forward defect indication or the received
end-to-end path backward defect indication changes.

Note that the end-to-end path forward defect indication is
implicit, i.e. it is not signalled using a bit. An end-to-end
path forward defect is inferred when no CDL Ethernet or Idle
packets are received over a pre-determined length of time.

To minimize the probability of prematurely reacting to
momentary signal variations, a soak time may be incorporated
into the notification in the following manner. A notification
is generated after a defect is first detected, when the defect
persists for a period of time that exceeds the set soak
interval specified by coCdlDefectIndSetSoakInterval. A
notification is generated after a defect stops being detected,
when the defect does not appear over a period of time that
exceeds the clear soak interval specified by
coCdlDefectIndClearSoakInterval.

When changes in CDL defect indications are received for
multiple interfaces within a short time span, notifications
should be deferred so that each notification is generated at
least one coCdlDINotifyThrottleInterval after the previous
notification.