DC-CR-LDP-MIB Table View

The index of this dccrldpSigEntry. This is the
HAF entity index passed on the product create
parameters.

The index of the Path Manager instance to which this
instance of Signaling is to join. See dccrldpPmTable.

The index of the DC-LMGR product instance to which this
DC-CR-LDP Signaling is to join as its LDB interface provider.
See dclmgrLsrEntityTable.

Management assigned interface identifier for the IP Sockets
component interface to DC-CR-LDP Signalling.

The number of pre-reserved buffers available for sending
sockets and LDI messages for each LDP session. This is used
to pace the sockets and LDI data flows for each LDP session.

The number of pre-reserved buffers available for sending
sockets, LDBI, NHR and I3 messages within Entity Manager
This is used to pace Entity Manager's sockets, LDBI, NHR
and I3 data flows.

The number of pre-reserved buffers available for sending
sockets messages within Adjacency Manager. This is used
to pace Adjacency Manager's sockets data flows.

This object is used to activate the DC-CR-LDP Signaling instance.

The current operational status of this instance of
DC-CR-LDP Signaling.

Used to create and delete a DC-CR-LDP Signaling Table entry.
When this object is set to 'active', only the
dccrldpSigAdminStatus object in the row may be modified.

Used to indicate whether this DC-CR-LDP Signaling instance
should use the I3 interface or the IPR interface to determine
information regarding local interface configuration. Use of
the IPR interface is deprecated, but …

Flags specifying how DC-LDP Session Controller should
behave in situations either where the interpretation of
strict conformance is debatable, or where strictly
conformant behavior contradicts the general IETF principle…

Used to indicate whether the DC-CR-LDP signaling is to use
IPv6 transport where possible.

Note that if DC-LDP is configured with an IPv4 transport
address, IPv4 transport will be used for multicast and
IP…

If this object is true, then it enables the generation of
mplsLdpSessionUp and mplsLdpSessionDown traps, otherwise
these traps are not generated.

If this object is true, then it enables the generation of
mplsLdpInitSessionThresholdExceeded traps, otherwise these
traps are not generated.

If this object is true, then it enables the generation of
mplsLdpPathVectorLimitMismatch traps, otherwise these
traps are not generated.

The index of the BFDI provider instance to which this
DC-LDP Signaling is to join as its BFD interface provider.
See bfdEntityTable.

Zero indicates that no BFDI provider is available, or that
DC-LDP Signa…

The index of this dccrldpPmEntry. This is the
HAF entity index passed on the product create
parameters.

The index of the DC-LMGR product instance to which this
DC-CR-LDP Path Manager is to join as its LDB interface provider.
See dclmgrLsrEntityTable.

When set to 'true', the Entity Manager component of DC-CR-LDP
creates Entities automatically based on interfaces known to
Entity Manager. When set to 'false' Entities are not
automatically created.

When set to 'true', the Entity Manager component of DC-CR-LDP
automatically starts Entities. Both configured and automatically
created Entities are automatically started. When set to 'false'
Entities are not automatic…

When set to 'true', the same Entity can be used for multiple
interfaces. That is, the per-platform label space behaves as
a per-interface label space. When set to 'false', the same
entity cannot be used for multiple i…

An indication of the LDP version supported.

When set to 'true', DC-CR-LDP implements fault tolerance
procedures for LDP and CR-LDP. When set to 'false', fault
tolerance procedures are not used.

The number identifying the autonomous system (AS) to which
this node belongs.

The size of the buffer pool used for sending either
(deprecated) IPRI messages or for sending NHR and I3
messages. This is used to pace IPR/NHR+I3 data flows from
PM.

When set to 'true', DC-CR-LDP implements LDP
functionality. When set to 'false' received LDP requests
are rejected.
Note that at least one of dccrldpPmLdpSupported and
dccrldpPmCrLdpSupported must be set to 'true' befo…

When set to 'true', DC-CR-LDP implements CR-LDP
functionality. When set to 'false' received CR-LDP requests
are rejected.
Note that at least one of dccrldpPmLdpSupported and
dccrldpPmCrLdpSupported must be set to 'true…

When set to 'true', DC-CR-LDP queries the routing stub
when a label mapping for an unrecognized FEC is received
to determine whether the FEC should be recognized and the
corresponding switch programming performed or not…

This object is used to activate the DC-CR-LDP Path Manager instance.

The current operational status of this instance of
DC-CR-LDP Path Manager.

Used to create and delete a DC-CR-LDP Path Manager Table entry.
When this object is set to 'active', only the
dccrldpPmAdminStatus object in the row may be modified.

A flag to indicate whether the local node should advertise
itself as LDP restart capable if the Label Switch
Controller or Label Data Forwarder is capable of
supporting the required procedures.

The time that the local node takes to restart LDP and bring up
the LDP sessions. This is advertised to neighbors in the FT
Session TLV in Initialization messages.

The value chosen should be large enough f…

The period of time that the local node is willing to retain its
MPLS forwarding state, if any, that it preserved across the
restart.

The time is from the end of the restart time configured
above.
…

The maximum period of time that LDP should wait for a restart
capable neighbor to restore an LDP session.

LDP waits for the minimum of this time and the
Reconnect Timeout advertised in the FT Session TLV …

The maximum period of time that LDP should wait for a restart
capable neighbor to refresh Label Mappings previously received
from that neighbor before deleting the stale bindings.

LDP waits for the minimu…

The time to hold a failed LDP Hello adjacency to distinguish
between LDP peer failure and interface failure.

This field is used to ensure that LDP retains adjacency
multi-link LSPs during peer restart rec…

This determines the order in which LDP connects and
releases out segments.

default: This will release all out-segments on a session
before programming new out-segments on the same session.
No ordering for…

This field indicates whether LDP Path Manager supports
IPv6 addresses, FECs and routes.

If this field is set to false then no IPv6 addresses will
be accepted over the NHR and I3 interfaces and all LDP
pro…

This field contains bit flags which indicate whether
DC-LDP supports LDP Policy and if per FEC policy
optimization is to be used.

The supported bit flags are
- policySupported
- perFecOptimizationSu…

This field indicates whether LDP Path Manager makes the
programming of each out segment conditional on the status
of the interface where the out segment is programmed.

When set to false, LDP Path Manager …

When set to 'true', LDP Path Manager creates joins to the
NHR stub and Label Manager as part of activation.

This field cannot be changed when the row is active.

When set to 'true', LDP Path Manager creates a PSI join to an
instance of DC-TPM as part of activation.

This field cannot be changed when the row is active.

The time interval that DC-MPLS will use in pseudowire
redundancy when attempting a switchover, before it determines
that switchover has failed.

The time interval during which Label Withdraws
will not be sent upstream after an event occurs that would
otherwise cause Label Withdraws to be sent.

The only events to which this does not apply are
- FEC…

Whether to use implicit XCs for VC FECs. This feature is
deprecated.

Implicit XCs are required for ECMP FECs, and are enabled
automatically if support for them is advertised over the
LDBI, which is depen…

DC-LDP sends label mappings to all upstream peers.
Sometimes, due to a change of next hop from IP Routing or
a new address from the peer, a peer may change from being
upstream to being a downstream peer. This results i…

Whether to use the dccrldpPmLabelWithdrawDelay timer to
also prevent immediate switch deprogramming at ingress.

Whether to release upstream programmed PW state
immediately when DC-LDP sends a Label Withdraw, instead of
waiting for a Label Release / session-down event.