The minimum time interval between generation of successive
CDL defect indication 'notification-events' by this agent. A
'notification-event' is the transmission of a single trap or
inform PDU to a list of notification destinations.
If more than one change occurs within a short time span, for
for example if hop-by-hop forward defect indications are
received for multiple interfaces, then notification-events
for these changes should be deferred by the agent so that each
notification-event occurs at least one throttle interval after
the previous notification-event. At the end of each throttle
interval, one notification-event should be generated if the
current defect indication state on any interface is different
from the last state indicated in a notification-event. In such
a case, another throttle interval is started immediately.
Parsed from file CISCO-CDL-MIB.mib
Module: CISCO-CDL-MIB
The minimum time interval between generation of successive
CDL defect indication 'notification-events' by this agent. A
'notification-event' is the transmission of a single trap or
inform PDU to a list of notification destinations.
If more than one change occurs within a short time span, for
for example if hop-by-hop forward defect indications are
received for multiple interfaces, then notification-events
for these changes should be deferred by the agent so that each
notification-event occurs at least one throttle interval after
the previous notification-event. At the end of each throttle
interval, one notification-event should be generated if the
current defect indication state on any interface is different
from the last state indicated in a notification-event. In such
a case, another throttle interval is started immediately.
The minimum time interval between generation of successive
CDL defect indication 'notification-events' by this agent. A
'notification-event' is the transmission of a single trap or
inform PDU to a list of notification destinations.
If more than one change occurs within a short time span, for
for example if hop-by-hop forward defect indications are
received for multiple interfaces, then notification-events
for these changes should be deferred by the agent so that each
notification-event occurs at least one throttle interval after
the previous notification-event. At the end of each throttle
interval, one notification-event should be generated if the
current defect indication state on any interface is different
from the last state indicated in a notification-event. In such
a case, another throttle interval is started immediately.
Parsed from file CISCO-CDL-MIB.my.txt
Company: None
Module: CISCO-CDL-MIB
The minimum time interval between generation of successive
CDL defect indication 'notification-events' by this agent. A
'notification-event' is the transmission of a single trap or
inform PDU to a list of notification destinations.
If more than one change occurs within a short time span, for
for example if hop-by-hop forward defect indications are
received for multiple interfaces, then notification-events
for these changes should be deferred by the agent so that each
notification-event occurs at least one throttle interval after
the previous notification-event. At the end of each throttle
interval, one notification-event should be generated if the
current defect indication state on any interface is different
from the last state indicated in a notification-event. In such
a case, another throttle interval is started immediately.
coCdlDINotifyThrottleInterval OBJECT-TYPE SYNTAX Unsigned32 (100..60000) UNITS "milliseconds" MAX-ACCESS read-write STATUS current DESCRIPTION "The minimum time interval between generation of successive CDL defect indication 'notification-events' by this agent. A 'notification-event' is the transmission of a single trap or inform PDU to a list of notification destinations. If more than one change occurs within a short time span, for for example if hop-by-hop forward defect indications are received for multiple interfaces, then notification-events for these changes should be deferred by the agent so that each notification-event occurs at least one throttle interval after the previous notification-event. At the end of each throttle interval, one notification-event should be generated if the current defect indication state on any interface is different from the last state indicated in a notification-event. In such a case, another throttle interval is started immediately. " DEFVAL { 1000 } ::= { coCdlBaseGroup 5 }
coCdlDINotifyThrottleInterval OBJECT-TYPE SYNTAX Gauge(100..60000) ACCESS read-write STATUS mandatory DESCRIPTION "The minimum time interval between generation of successive CDL defect indication 'notification-events' by this agent. A 'notification-event' is the transmission of a single trap or inform PDU to a list of notification destinations. If more than one change occurs within a short time span, for for example if hop-by-hop forward defect indications are received for multiple interfaces, then notification-events for these changes should be deferred by the agent so that each notification-event occurs at least one throttle interval after the previous notification-event. At the end of each throttle interval, one notification-event should be generated if the current defect indication state on any interface is different from the last state indicated in a notification-event. In such a case, another throttle interval is started immediately." DEFVAL { 1000 } ::= { coCdlBaseGroup 5 }
Vendor: Cisco
Module: CISCO-CDL-MIB
[Automatically extracted from oidview.com]
coCdlDINotifyThrottleInterval OBJECT-TYPE SYNTAX Unsigned32 (100..60000) UNITS "milliseconds" MAX-ACCESS read-write STATUS current DESCRIPTION "The minimum time interval between generation of successive CDL defect indication 'notification-events' by this agent. A 'notification-event' is the transmission of a single trap or inform PDU to a list of notification destinations. If more than one change occurs within a short time span, for for example if hop-by-hop forward defect indications are received for multiple interfaces, then notification-events for these changes should be deferred by the agent so that each notification-event occurs at least one throttle interval after the previous notification-event. At the end of each throttle interval, one notification-event should be generated if the current defect indication state on any interface is different from the last state indicated in a notification-event. In such a case, another throttle interval is started immediately. " DEFVAL { 1000 } ::= { coCdlBaseGroup 5 }
coCdlDINotifyThrottleInterval OBJECT-TYPE SYNTAX Unsigned32 (100..60000) UNITS "milliseconds" MAX-ACCESS read-write STATUS current DESCRIPTION "The minimum time interval between generation of successive CDL defect indication 'notification-events' by this agent. A 'notification-event' is the transmission of a single trap or inform PDU to a list of notification destinations. If more than one change occurs within a short time span, for for example if hop-by-hop forward defect indications are received for multiple interfaces, then notification-events for these changes should be deferred by the agent so that each notification-event occurs at least one throttle interval after the previous notification-event. At the end of each throttle interval, one notification-event should be generated if the current defect indication state on any interface is different from the last state indicated in a notification-event. In such a case, another throttle interval is started immediately. " DEFVAL { 1000 } ::= { coCdlBaseGroup 5 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.10.88.1.1.5.0 | coCdlDINotifyThrottleInterval | 0 | 0 | None |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.10.88.1.1.1 | coCdlIntfTable | 1 | 19 | coCdlIntftable |
| 1.3.6.1.4.1.9.10.88.1.1.2 | coCdlDefectIndNotifyEnable | 1 | 1 | This object indicates whether a change in the received CDL Defect Indications, including the implicit end-to-end path defect indi… |
| 1.3.6.1.4.1.9.10.88.1.1.3 | coCdlDefectIndSetSoakInterval | 1 | 1 | To minimize the probability of prematurely reacting to momentary signal variations, a soak time may be incorporated into the defe… |
| 1.3.6.1.4.1.9.10.88.1.1.4 | coCdlDefectIndClearSoakInterval | 1 | 1 | To minimize the probability of prematurely reacting to momentary signal variations, a soak time may be incorporated into the defe… |