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. |
ciscoExperiment | CISCO-SMI |
ifIndex | IF-MIB |
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP | SNMPv2-CONF |
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Counter32, Counter64, Unsigned32 | SNMPv2-SMI |
TEXTUAL-CONVENTION, TimeStamp, TruthValue | SNMPv2-TC |
Name | Base Type | Values/Constraints |
---|---|---|
Bits | hopByHopForwardDefect(0), hopByHopBackwardDefect(1), endToEndAggPathForwardDefect(2) | |
Bits | endToEndPathImplicitFwdDefect(0), endToEndPathBackwardDefect(1) | |
Unsigned32 | range: 0..65535 | |
Enumeration | endOfAggPath(1), endOfHop(2), cdlRegenerator(3) |
![]() | .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 | |
![]() | .1.3.6.1.4.1.9.10.88.1.1.2 | |
![]() | .1.3.6.1.4.1.9.10.88.1.1.3 | |
![]() | .1.3.6.1.4.1.9.10.88.1.1.4 | |
![]() | .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 |
Name | OID | Description |
---|---|---|
.1.3.6.1.4.1.9.10.88.0.1 | ication 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 | ication 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. |