To suspend the LDP protocol, use the shutdown command. Configuration parameters are not affected.
The no form of the command deletes the LDP protocol instance, removing all associated configuration parameters. The LDP instance must first be disabled with the
shutdown command before being deleted.
When an IPv4 packet is received on an ingress network interface, a subscriber IES interface, or a regular IES interface, the lookup of the packet by the ingress forwarding engine will result in the packet being sent labeled with the label stack corresponding to the NHLFE of the LDP LSP when the preferred RTM entry corresponds to an LDP shortcut.
The no form of this command disables the resolution of IGP routes using LDP shortcuts.
The no form of this command administratively enables an entity.
The no form of the command places an entity in an administratively enabled state.
The no version of this command reverts LDP to the default behaviour of advertising all local interfaces.
The no form of this command disables the use by LDP of the aggregate prefix procedures and deletes the configuration. LDP resumes performing exact prefix match for FEC elements.
The no form of this command removes all policies from the configuration.
The no form of this command disables the statistics in the egress data path and removes the accounting policy association from the LDP FEC.
The no form of this command removes the accounting policy association.
When the no collect-stats command is issued the statistics are still accumulated by the forwarding engine. However, the CPU will not obtain the results and write them to the billing file. If a subsequent
collect-stats command is issued then the counters written to the billing file include all the traffic while the
no collect-stats command was in effect.
The no form of the command removes all policies from the configuration.
no export — No export route policies specified.
The tunnel-down-dump-time option or the
label-withdrawal-delay option, when enabled, does not cause the corresponding timer to be activated for a FEC as long as a backup NHLFE is still available.
The no form of this command disables LDP FRR.
The user adds LDP FEC prefixes with the statement ‘from protocol ldp’ in the configuration of the existing BGP export policy at the global level, the peer-group level, or at the peer level using the commands:
To indicate to BGP to evaluate the entries with the ‘from protocol ldp’ statement in the export policy when applied to a specific BGP neighbor, a new argument is added to the existing advertise-label command:
Without the new include-ldp-prefix argument, only core IPv4 routes learned from RTM are advertised as BGP labeled routes to the neighbor. No stitching of LDP FEC to the BGP labeled route will be performed for this neighbor even if the same prefix was learned from LDP.
The user can add BGP labeled route prefixes with the statement ‘from protocol bgp’ in the configuration of the LDP tunnel table export policy. Note that the ‘
from protocol’ statement has an effect only when the protocol value is ldp. Policy entries with protocol values of rsvp, bgp, or any value other than ldp are ignored at the time the policy is applied to LDP.
The no form of the command removes the policy from the configuration.
no export-tunnel-table — no tunnel table export route policy is specified.
The no form of the command disables graceful restart.
no graceful-restart (
disabled) — Graceful-restart must be explicitely enabled.
The no form of this command disables the signaling of the implicit null label.
The no form of the command returns the default value.
The no form of the command returns the default value.
The no form of the command removes all policies from the configuration.
no import — No import route policies specified.
The no form of this command disables the fast upstream switchover for mLDP FECs.
The no form of this command then tunnel down events are not damped.
The no form of the command at the interface-parameters and targeted-session levels sets the
keepalive timeout and the
keepalive factor to the default value.
The no form of the command, at the interface level, sets the
keepalive timeout and the
keepalive factor to the value defined under the
interface-parameters level.
The no form of the command, at the peer level, will set the
keepalive timeout and the
keepalive factor to the value defined under the
targeted-session level.
If the user changes the LSR-ID value on the fly between system,
interface, and
interface-name while the LDP session is up, LDP will immediately tear down all sessions using this LSR-ID and will attempt to re-establish them using the new LSR-ID.
The no form of the command returns to the default behavior in which case the system interface address is used as the LSR-ID.
The no form of this command returns to the default behavior in which case the system interface address is used as the LSR-ID.
The no form of the command disables tunneling.
The no form of this command disables BFD on the LDP interface.
The no form of the command at theinterface-parameters and targeted-session level sets the
hello timeout and the
hello factor to the default values.
The no form of the command, at the interface level, will set the
hello timeout and the
hello factor to the value defined under the interface-parameters level.
The no form of the command, at the peer level, will set the
hello timeout and the
hello factor to the value defined under the targeted-session level.
When this feature is enabled, the target Hello adjacency is brought up by advertising the Hold-Time value the user configured in the “hello timeout” parameter for the targeted session. The LSR node will then start advertising an exponentially increasing Hold-Time value in the Hello message as soon as the targeted LDP session to the peer is up. Each new incremented Hold-Time value is sent in a number of Hello messages equal to the value of the argument
factor, which represents the dampening factor, before the next exponential value is advertised. This provides time for the two peers to settle on the new value. When the Hold-Time reaches the maximum value of 0xffff (binary 65535), the two peers will stop sending Hello messages for the lifetime of the targeted LDP session.
The no form of this command disables the hello reduction feature.
The no form of the command deletes the LDP interface and all configuration information associated with the LDP interface.
This command configures the transport address to be used when setting up the LDP TCP sessions. The transport address can be configured as interface or
system. The transport address can be configured globally (applies to all LDP interfaces) or per interface. The most specific value is used.
Note that the transport-address value should not be
interface if multiple interfaces exist between two LDP neighbors. Depending on the first adjacency to be formed, the TCP endpoint is chosen. In other words, if one LDP interface is set up as
transport-address interface and another for
transport-address system, then, depending on which adjacency was set up first, the TCP endpoint addresses are determined. After that, because the hello contains the LSR ID, the LDP session can be checked to verify that it is set up and then match the adjacency to the session.
Note that for any given ILDP interface, as the local-lsr-id parameters is changed to
interface, the
transport-address configuration loses effectiveness. Since it will be ignored and the ILDP session will
always use the relevant interface IP address as transport-address even though system is chosen.
The no form of the command, at the global level, sets the transport address to the default value.
The
no form of the command, at the interface level, sets the transport address to the value defined under the global level.
system — The system IP address is used.
The no form of command disables P2MP LDP multicast traffic on the interface. P2MP tree branching out on the interface would not withdraw label map from the peer session on interface shutdown or multicast traffic is disabled. Session may exist on multiple parallel interfaces. Only forwarding entry is changed when interface is shutdown or multicast traffic support is disabled.
The no form of command should configure the default timer of 3 seconds.
The no form of this command disables authentication.
Specifies the key is entered in a more complex encrypted form. If the
hash2 parameter is not used, the less encrypted
hash form is assumed.
The no form of this command disables the DoD label distribution with an LDP neighbor.
Policies are configured in the config>router>policy-options context. A maximum of five policy names can be specified. Peer address has to be the peer LSR-ID address.
The no form of the command removes the policy from the configuration.
The no form of the command returns the default .
Policies are configured in the config>router>policy-options context. A maximum of five policy names can be specified. Peer address has to be the peer LSR-ID address.
The no form of the command removes the policy from the configuration.
This command configures TTL security parameters for incoming packets. When the feature is enabled, BGP/LDP will accept incoming IP packets from a peer only if the TTL value in the packet is greater than or equal to the minimum TTL value configured for that peer. Peer address has to be the TCP session transport address.
The no form of the command disables TTL security.
When the no form of the command is enabled, TTL propagation is disabled on all transit IP packets received on any IES interface and destined to a route that is resolved to the LSP shortcut. In this case, a TTL of 255 is programmed onto the pushed label stack. This is referred to as Pipe mode.
When the no form of the above command is enabled, TTL propagation is disabled on all locally generated IP packets, including ICMP Ping, traceroute, and OAM packets, that are destined to a route that is resolved to the LSP shortcut. In this case, a TTL of 255 is programmed onto the pushed label stack. This is referred to as Pipe mode.
The no form of this command removes the TLDP session operational state binding to the central BFD session one.
The no form of the command enables the set up of any targeted sessions.
The template comes up in the no shutdown state and assuch it takes effect immediately. Once a template is in use, the user can change any of the parameters on the fly without shutting down the template. In this case, all targeted Hello adjacencies are updated.
Finally, the value of any LDP parameter which is specific to the LDP/TCP session to a peer is inherited from the config>router>ldp>peer-parameters>peer context. This includes MD5 authentication, LDP prefix per-peer policies, label distribution mode (DU or DOD), etc.
The no form of command deletes the peer template. A peer template cannot be deleted if it is bound to a peer prefix list.
Policies are configured in the config>router>policy-options context. A maximum of five policy names can be specified.
The no form of the command removes the policy from the configuration.
Policies are configured in the config>router>policy-options context. A maximum of five policy names can be specified.
The no form of the command removes the policy from the configuration.
