This command administratively disables an entity. When disabled, an entity does not change, reset, or remove any configuration settings or statistics.
The operational state of the entity is disabled as well as the operational state of any entities contained within. Many objects must be shut down before they can be deleted.
The no form of this command administratively enables an entity.
Unlike other commands and parameters where the default state is not indicated in the configuration file, the shutdown and no shutdown states are always indicated in system-generated configuration files.
no shutdown
This command creates the context to configure an LDP protocol instance.
When an LDP instance is created, the protocol is enabled (in the no shutdown state). 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.
n/a — LDP must be explicitly enabled
This command enables LDP to use the aggregate prefix match function rather than requiring an exact prefix match.
When this command is enabled and an LSR receives a FEC-label binding from an LDP neighbor for a prefix-address FEC element, FEC1, it will install the binding in the LDP FIB if:
When the FEC-label binding has been installed in the LDP FIB, LDP programs an NHLFE entry in the egress data path to forward packets to FEC1. LDP also advertises a new FEC-label binding for FEC1 to all its LDP neighbors.
When a new prefix appears in the RIB, LDP checks the LDP FIB to determine if this prefix is a closer match for any of the installed FEC elements. If a closer match is found, this may mean that the LSR used as the next hop will change; if so, the NHLFE entry for that FEC must be changed.
When a prefix is removed from the RIB, LDP checks the LDP FIB for all FEC elements that matched this prefix to determine if another match exists in the routing table. If another match exists, LDP must use it. This may mean that the LSR used as the next hop will change; if so, the NHLFE entry for that FEC must be changed. If another match does not exist, the LSR removes the FEC binding and sends a label withdraw message to its LDP neighbors.
If the next hop for a routing prefix changes, LDP updates the LDP FIB entry for the FEC elements that matched this prefix. It also updates the NHLFE entry for the FEC elements.
The no form of this command disables the use of the aggregate prefix match function. LDP then only performs an exact prefix match for FEC elements.
no aggregate-prefix-match
This command specifies the policy name containing the prefixes to be excluded from the aggregate prefix match function. Against each excluded prefix, LDP performs an exact match of a specific FEC element prefix, rather than a longest prefix match of one or more LDP FEC element prefixes, when it receives a FEC-label binding or when a change to the prefix occurs in the routing table.
The no form of this command removes all policies from the configuration; therefore, no prefixes are excluded.
no prefix-exclude
This command specifies export route policies that determine which routes are exported to LDP neighbors. Configuring an export policy allows the LSR (Label Switch Router) to advertise addresses other than the system IP address. Policies are configured in the config>router>policy-options context. Refer to the “Route Policies” section in the 7705 SAR OS Router Configuration Guide.
If no export policy is specified, non-LDP routes will not be exported from the routing table manager to LDP, and only LDP-learned routes will be exported to LDP neighbors.
If multiple policy names are specified, the policies are evaluated in the order they are specified. The first policy that matches is applied. If multiple export commands are issued, the last command entered will override the previous command. A maximum of five policy names can be specified. The specified name(s) must already be defined.
The no form of the command removes all policies from the configuration.
no export
This command enables graceful restart helper.
The no form of the command disables graceful restart.
graceful-restart
This command configures the local maximum recovery time, which is the time (in seconds) that the sender of the TLV would like the receiver to wait, after detecting the failure of LDP communication with the sender.
The no form of the command returns the default value.
120
This command configures the neighbor liveness time, which is the time (in seconds) that the LSR is willing to retain its MPLS forwarding state. The time should be long enough to allow the neighboring LSRs to resynchronize all the LSPs in a graceful manner, without creating congestion in the LDP control plane.
The no form of the command returns the default value.
120
This command specifies import route policies that determine which routes are accepted from LDP neighbors. Policies are configured in the config>router>policy-options context. Refer to the “Route Policies” section in the 7705 SAR OS Router Configuration Guide.
If no import policy is specified, LDP accepts all routes from configured LDP neighbors. Import policies can be used to limit or modify the routes accepted and their corresponding parameters and metrics.
If multiple policy names are specified, the policies are evaluated in the order they are specified. The first policy that matches is applied. If multiple import commands are issued, the last command entered will override the previous command. A maximum of five policy names can be specified. The specified name(s) must already be defined.
The no form of the command removes all policies from the configuration.
no import
This command configures the hold time. This is the time interval to wait before declaring a neighbor down. The factor parameter derives the hello interval.
Hold time is local to the system and is sent in the hello messages to the neighbor. Hold time cannot be less than three times the hello interval. The hold time can be configured globally (applies to all LDP interfaces) or per interface. The most specific value is used.
When an LDP session is being set up, the hold time is negotiated to the lower of the two peers. Once an operational value is agreed upon, the hello factor is used to derive the value of the hello interval.
The no form of the command:
The default value is dependent upon the CLI context. Table 27 lists the hello timeout factor default values.
Context | Timeout | Factor |
config>router>ldp>interface-parameters | 15 | 3 |
config>router>ldp>targeted-session | 45 | 3 |
config>router>ldp>if-params>interface | Inherits values from interface-parameters context | |
config>router>ldp>targ-session>peer | Inherits values from targeted-session context |
This command configures the time interval, in seconds, that LDP waits before tearing down the session. The factor parameter derives the keepalive interval.
If no LDP messages are exchanged for the configured time interval, the LDP session is torn down. Keepalive timeout is usually three times the keepalive interval. To maintain the session permanently, regardless of the activity, set the value to zero.
When an LDP session is being set up, the keepalive timeout is negotiated to the lower of the two peers. Once a operational value is agreed upon, the keepalive factor is used to derive the value of the keepalive interval.
The no form of the command:
The default value is dependent upon the CLI context. Table 28 lists the keepalive timeout factor default values.
Context | Timeout | Factor |
config>router>ldp>interface-parameters | 30 | 3 |
config>router>ldp>targeted-session | 40 | 4 |
config>router>ldp>if-params>interface | Inherits values from interface-parameters context | |
config>router>ldp>targ-session>peer | Inherits values from targeted-session context |
This command specifies the time interval, in seconds, that LDP waits before posting a tunnel down event to the Tunnel Table Manager (TTM).
When LDP can no longer resolve a FEC and deactivates it, it deprograms the NHLFE in the data path. It will, however, delay deleting the LDP tunnel entry in the TTM until the tunnel-down-damp-time timer expires. This means that users of the LDP tunnel, such as SDPs (for all services) and BGP (for Layer 3 VPNs), will not be notified immediately. Traffic is still blackholed because the NHLFE has been deprogrammed.
If the FEC gets resolved before the tunnel-down-damp-time timer expires, LDP programs the IOM with the new NHLFE and posts a tunnel modify event to the TTM, updating the dampened entry in the TTM with the new NHLFE information.
If the FEC does not get resolved and the tunnel-down-damp-time timer expires, LDP posts a tunnel down event to the TTM, which deletes the LDP tunnel.
The no form of the command reverts the damp timer value back to the default value of 3. If the timer value is set to 0, tunnel down events are not dampened but are reported immediately.
3
This command enables the context to configure LDP interfaces and parameters applied to LDP interfaces.
This command enables LDP on the specified IP interface.
The no form of the command deletes the LDP interface and all configuration information associated with the LDP interface.
The LDP interface must be disabled using the shutdown command before it can be deleted.
This command enables the use of the address of the link LDP interface as the LSR ID in order to establish an LDP adjacency and session with a directly connected LDP peer.
By default, the LDP session uses the system interface address as the LSR ID. This means that targeted LDP (T-LDP) and interface LDP share a common LDP TCP session and therefore a common LDP label space. The system interface must be configured on the router or the LDP protocol will not come up on the node. At initial configuration, the LDP session to the peer remains down while the interface is down. If the user changes the LSR ID while the LDP session is up, LDP immediately tears down the session and attempts to re-establish it using the new LSR ID. If the interface used for the local LSR ID goes down, then the LDP session will also go down.
The interface option is the recommended setting when static route-LDP synchronization is enabled.
When the interface option is selected, the transport connection (TCP) for the link LDP session configured by the transport-address command is automatically set to interface. Having both the local-lsr-id and transport address set to the local interface creates two TCP sessions to the peer and therefore two different LDP label spaces: one to the interface IP address for link LDP (L-LDP) and one to the system IP address for T-LDP.
The no form of the command resets the local-lsr-id to the default value.
system
This command configures the transport address to be used when setting up the LDP TCP sessions. The transport address can be configured globally (applies to all LDP interfaces) or per interface. The most specific value is used.
With the transport-address command, you can set up the LDP interface to the connection that can be set to the interface address or the system address. However, there can be an issue of which address to use when there are parallel adjacencies. This address selection situation can also occur when there is a link and a targeted adjacency, since targeted adjacencies request the session to be set up only to the system IP address.
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 as 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 the adjacency can be matched to the session.
The no form of the command:
system
This command configures targeted LDP sessions. Targeted sessions are LDP sessions between non-directly-connected peers. Hello messages are sent directly to the peer platform instead of to all the routers on this subnet multicast address.
The discovery messages for an indirect LDP session are addressed to the specified peer and not to the multicast address.
n/a
This command disables support for targeted sessions. Targeted sessions are LDP sessions between non-directly-connected peers. The discovery messages for an indirect LDP session are addressed to the specified peer and not to the multicast address.
The no form of the command enables the setup of any targeted sessions.
no disable-targeted-session
This command configures parameters for an LDP peer.
n/a
This command enables the use of bidirectional forwarding detection to control the state of the associated T-LDP session.
The no form of this command removes BFD from the associated T-LDP protocol adjacency.
n/a
This command enables the use of the address of a specific interface as the LSR ID in order to establish a targeted LDP (T-LDP) adjacency and session with an LDP peer. The interface can be a regular interface or a loopback interface, including the system interface.
By default, a T-LDP session uses the system interface address as the LSR ID. This means that T-LDP and interface LDP share a common LDP TCP session and therefore a common LDP label space. The system interface must be configured on the router or the LDP protocol will not come up on the node. At initial configuration, the LDP session to the peer remains down while the interface is down. If the user changes the LSR ID while the LDP session is up, LDP immediately tears down the session and attempts to re-establish it using the new LSR ID. If the interface used for the local LSR ID goes down, then the LDP session will also go down.
The user-configured LSR ID is used for extended peer discovery to establish the T-LDP hello adjacency. It is also used as the transport address for the LDP TCP session when it is bootstrapped by the T-LDP hello adjacency. The user-configured LSR ID is not used in basic peer discovery to establish a link-level LDP hello adjacency.
The no form of the command resets the local-lsr-id to the default value, which means that the system interface address is used as the LSR ID.
no local-lsr-id
This command enables the context to configure peer specific parameters.
This command configures parameters for an LDP peer.
n/a
This command specifies the authentication key to be used between LDP peers before establishing sessions. Authentication uses the MD5 message-based digest.
The no form of this command disables authentication.
n/a
This is useful when a user must configure the parameter; however, for security purposes, the actual unencrypted key value is not provided.
Note:
If neither the hash or hash2 keyword is specified, the key is entered in clear text. However, for security purposes, the key is stored on the node using hash encryption. |
This command displays LDP sessions using a particular authentication key chain.
The following output is an example of LDP sessions using an authentication key chain.
This command displays the contents of the label information base.
The following output is an example of LDP bindings information, and Table 29 describes the fields. Following the table are output examples for:
Label | Description | |
Legend | U: Label In Use N: Label Not In Use W: Label Withdrawn S: Status Signaled Up D: Status Signaled Down | E: Epipe service A: Apipe service C: Cpipe service P: Ipipe service TLV: (Type, Length: Value) |
Type | The service type exchanging labels in the SDP. The possible types displayed are Epipe, Spoke, and Unknown. | |
VCId | The value used by each end of an SDP tunnel to identify the VC | |
SvcID | Identifies the service in the service domain | |
SDPId | Identifies the SDP in the service domain | |
Peer | The IP address of the peer | |
IngLbl | The ingress LDP label | |
U — indicates that the label is in use | ||
R — indicates that the label has been released | ||
EgrLbl | The egress LDP label | |
LMTU | The local MTU value | |
RMTU | The remote MTU value | |
No. of Prefix Bindings | The total number of LDP bindings on the router | |
EgrIntf/LspId | The egress interface LSP ID | |
EgrNextHop | The egress next-hop address | |
No. of VC Labels | The total number of VC labels | |
No. of Service Bindings | The total number of service bindings | |
AGI Type | The address group identifier (AGI) | |
SAII Peer | The source attachment individual identifier (SAII) | |
TAII EgrLbl | The target attachment individual identifier (TAII) | |
Vc-switching | Not applicable – always indicates no | |
Egr. Flags | Specifies egress flag, if any | |
Egr. Ctl Word | Indicates whether egress control words are used | |
Egr. Status Bits | Indicates whether egress status bits are supported | |
Igr. Flags | Specifies ingress flag, if any | |
Igr. Ctl Word | Indicates whether ingress control words are used | |
Igr. Status Bits | Indicates whether ingress status bits are supported | |
Op | The operation performed on the ingress or egress label in the LDP stack (push or pop) |
This command displays the status of the interfaces participating in LDP discovery.
The following outputs are examples of LDP discovery information, and Table 30 describes the fields.
Label | Description |
Interface Name | The name of the interface |
Local Addr | The IP address of the originating (local) router |
Peer Addr | The IP address of the peer |
Adj Type | The adjacency type between the LDP peer and LDP session |
State | Established — indicates that the adjacency is established |
Trying — indicates that the adjacency is not yet established | |
No. of Hello Adjacencies | The total number of hello adjacencies discovered |
Up Time | The amount of time the adjacency has been enabled |
Hold-Time Remaining | The time left before a neighbor is declared to be down |
Hello Mesg Recv | The number of Hello messages received for this adjacency |
Hello Mesg Sent | The number of Hello messages that have been sent for this adjacency |
Remote Cfg Seq No | The configuration sequence number that was in the Hello message received when this adjacency started up. This configuration sequence number changes when there is a change of configuration. |
Remote IP Address | The IP address used on the remote end for the LDP session |
Local Cfg Seq No | The configuration sequence number that was used in the Hello message sent when this adjacency started up. This configuration sequence number changes when there is a change of configuration. |
Local IP Address | The IP address used locally for the LDP session |
This command displays configuration information about LDP interfaces.
The following output is an example of LDP interface information, and Table 31 describes the fields.
Label | Description |
Interface | The interface associated with the LDP instance |
Adm | Up — indicates that the LDP is administratively enabled |
Down — indicates that the LDP is administratively disabled | |
Opr | Up — indicates that the LDP is operationally enabled |
Down — indicates that the LDP is operationally disabled | |
Hello Factor | The value by which the hello timeout should be divided to give the hello time; that is, the time interval, in seconds, between LDP Hello messages. LDP uses hello messages to discover neighbors and to detect loss of connectivity with its neighbors. |
Hold Time | The time interval, in seconds, that LDP waits before declaring a neighbor to be down. Hold time (also known as Hello time) is local to the system and is sent in the hello messages to a neighbor. |
KA Factor | The value by which the keepalive timeout should be divided to give the keepalive time; that is, the time interval, in seconds, between LDP keepalive messages. LDP keepalive messages are sent to keep the LDP session from timing out when no other LDP traffic is being sent between the neighbors. |
KA Timeout | The time interval, in seconds, that LDP waits before tearing down a session. If no LDP messages are exchanged during this time interval, the LDP session is torn down. Generally the value is configured to be three times the keepalive time (the time interval between successive LDP keepalive messages). |
Transport Address | The transport address entity |
No. of Interfaces | The total number of LDP interfaces |
Oper Down Reason | The reason for the LSP being in the down state |
Active Adjacencies | The number of active adjacencies |
Last Modified | The time of the last modification to the LDP interface |
Lsp Name | The LSP name |
This command displays configuration information about LDP parameters.
The following output is an example of LDP parameters information, and Table 32 describes the fields.
Label | Description |
Graceful Restart Parameters | |
Nbor Liveliness Time | The neighbor liveliness time |
Max Recovery Time | The local maximum recovery time |
Interface Parameters | |
Keepalive Timeout | The time interval, in seconds, that LDP waits before tearing down a session. If no LDP messages are exchanged during this time interval, the LDP session is torn down. Generally the value is configured to be three times the keepalive time (the time interval between successive LDP keepalive messages). |
Keepalive Factor | The value by which the keepalive timeout should be divided to give the keepalive time; that is, the time interval, in seconds, between LDP keepalive messages. LDP keepalive messages are sent to keep the LDP session from timing out when no other LDP traffic is being sent between the neighbors. |
Hold Time | The time interval, in seconds, that LDP waits before declaring a neighbor to be down. Hold time (also known as Hello time) is local to the system and is sent in the hello messages to a neighbor. |
Hello Factor | The value by which the hello timeout should be divided to give the hello time; that is, the time interval, in seconds, between LDP Hello messages. LDP uses hello messages to discover neighbors and to detect loss of connectivity with its neighbors. |
Propagate Policy | Specifies whether the LSR should generate FECs and which FECs it should generate |
system — indicates that the LDP will distribute label bindings only for the router’s system IP address | |
interface — indicates that the LDP will distribute label bindings for all LDP interfaces | |
all — indicates that the LDP will distribute label bindings for all prefixes in the routing table | |
none — indicates that the LDP will not distribute any label bindings | |
Transport Address | interface — the interface IP address is used to set up the LDP session between neighbors. If multiple interfaces exist between two neighbors, the interface mode cannot be used since only one LDP session is actually set up between the two neighbors. |
system — the system IP address is used to set up the LDP session between neighbors | |
Label-Distribution | The label distribution method |
Label-Retention | liberal — all advertised label mappings are retained whether they are from a valid next hop or not. When the label distribution value is downstream unsolicited, a router may receive label bindings for the same destination for all its neighbors. Labels for the non-next-hops for the FECs are retained in the software but not used. When a network topology change occurs where a non-next-hop becomes a true next hop, the label received earlier is then used. |
conservative — advertised label mappings are retained only if they will be used to forward packets; for example if the label came from a valid next hop. Label bindings received from non-next-hops for each FEC are discarded. | |
Control Mode | ordered — label bindings are not distributed in response to a label request until a label binding has been received from the next hop for the destination |
independent — label bindings are distributed immediately in response to a label request even if a label binding has not yet been received from the next hop for the destination | |
Route Preference | The route preference assigned to LDP routes. When multiple routes are available to a destination, the route with the lowest preference will be used. This value is only applicable to LDP interfaces and not for targeted sessions. |
Targeted Session Parameters | |
Keepalive Timeout | The factor used to derive the keepalive interval |
Keepalive Factor | The time interval, in seconds, that LDP waits before tearing down the session |
Hold Time | The time left before a neighbor is declared to be down |
Hello Factor | The value by which the hello timeout should be divided to give the hello time; that is, the time interval, in seconds, between LDP Hello messages. LDP uses hello messages to discover neighbors and to detect loss of connectivity with its neighbors. |
Disable — indicates that no authentication is being used | |
Passive Mode | True — indicates that LDP responds only when it gets a connect request from a peer and will not attempt to actively connect to its neighbors |
False — indicates that LDP actively tries to connect to its peers | |
Targeted Sessions | Enabled — indicates that targeted sessions are enabled |
Disabled — indicates that targeted sessions are disabled |
This command displays configuration information about LDP peers.
The following output is an example of LDP peer information, and Table 33 describes the fields.
Label | Description |
Peer | The IP address of the peer |
Adm | Up — indicates that LDP is administratively enabled |
Down — indicates that LDP is administratively disabled | |
Opr | Up — indicates that LDP is operationally enabled |
Down — indicates that LDP is operationally disabled | |
Hello Factor | The value by which the hello timeout should be divided to give the hello time; that is, the time interval, in seconds, between LDP Hello messages. LDP uses hello messages to discover neighbors and to detect loss of connectivity with its neighbors. |
Hold Time | The time interval, in seconds, that LDP waits before declaring a neighbor to be down. Hold time (also known as Hello time) is local to the system and is sent in the hello messages to a neighbor. |
KA Factor | The value by which the keepalive timeout should be divided to give the keepalive time; that is, the time interval, in seconds, between LDP keepalive messages. LDP keepalive messages are sent to keep the LDP session from timing out when no other LDP traffic is being sent between the neighbors. |
KA Timeout | The time interval, in seconds, that LDP waits before tearing down a session. If no LDP messages are exchanged during this time interval, the LDP session is torn down. Generally the value is configured to be three times the keepalive time (the time interval between successive LDP keepalive messages). |
Passive Mode | The mode used to set up LDP sessions. This value is only applicable to targeted sessions and not to LDP interfaces. This mode is always set to False. |
True — indicates that LDP responds only when it gets a connect request from a peer and will not attempt to actively connect to its neighbors | |
False — indicates that LDP actively tries to connect to its peers | |
Auto Create | Specifies whether or not a targeted peer was automatically created through a Service Manager. For an LDP interface, this value is always false. |
No. of Peers | The total number of LDP peers |
LSP | The LSP name |
This command displays LDP peer information.
The following output is an example of LDP peer-parameters information, and Table 34 describes the fields.
Label | Description |
Peer | The IP address of the peer |
Authentication | Enabled — authentication using MD5 message-based digest protocol is enabled |
Disabled — no authentication is used |
This command displays configuration information about LDP sessions.
The following output is an example of LDP session information, and Table 35 describes the fields.
Label | Description |
Peer LDP Id | The IP address of the LDP peer |
Adj Type | The adjacency type between the LDP peer and LDP session that is targeted |
Link — specifies that this adjacency is a result of a Link Hello | |
Targeted — specifies that this adjacency is a result of a Targeted Hello | |
State | Established — the adjacency is established |
Trying — the adjacency is not yet established | |
Msg Sent | The number of messages sent |
Msg Rcvd | The number of messages received |
Up Time | The amount of time the adjacency has been enabled |
This command displays LDP status information.
The following output is an example of LDP status information, and Table 36 describes the fields.
Label | Description |
Admin State | Up — indicates that LDP is administratively enabled |
Down — indicates that LDP is administratively disabled | |
Oper State | Up — indicates that LDP is operationally enabled |
Down — indicates that LDP is operationally disabled | |
Created at | The date and time that the LDP instance was created |
Up Time | The time, in hundredths of seconds, that the LDP instance has been operationally up |
Oper Down Time | The time, in hundredths of seconds, that the LDP instance has been operationally down |
Oper Down Events | The number of times the LDP instance has gone operationally down since the instance was created |
Last Change | The date and time that the LDP instance was last modified |
Import Policies | The import policy associated with the LDP instance |
Active Adjacencies | The number of active adjacencies (established sessions) associated with the LDP instance |
Active Sessions | The number of active sessions (session in some form of creation) associated with the LDP instance |
Active Interfaces | The number of active (operationally up) interfaces associated with the LDP instance |
Inactive Interfaces | The number of inactive (operationally down) interfaces associated with the LDP instance |
Active Peers | The number of active LDP peers |
Inactive Peers | The number of inactive LDP peers |
Addr FECs Sent | The number of labels that have been sent to the peer associated with this FEC |
Addr FECs Recv | The number of labels that have been received from the peer associated with this FEC |
Serv FECs Sent | The number of labels that have been sent to the peer associated with this FEC |
Serv FECs Recv | The number of labels that have been received from the peer associated with this FEC |
Attempted Sessions | The total number of attempted sessions for this LDP instance |
No Hello Err | The total number of “Session Rejected” or “No Hello Error” notification messages sent or received by this LDP instance |
Param Adv Err | The total number of “Session Rejected” or “Parameters Advertisement Mode Error” notification messages sent or received by this LDP instance |
Max PDU Err | The total number of “Session Rejected” or “Parameters Max PDU Length Error” notification messages sent or received by this LDP instance |
Label Range Err | The total number of “Session Rejected” or “Parameters Label Range Error” notification messages sent or received by this LDP instance |
Bad LDP Id Err | The number of bad LDP identifier fatal errors detected for sessions associated with this LDP instance |
Bad PDU Len Err | The number of bad PDU length fatal errors detected for sessions associated with this LDP instance |
Bad Mesg Len Err | The number of bad message length fatal errors detected for sessions associated with this LDP instance |
Bad TLV Len Err | The number of bad TLV length fatal errors detected for sessions associated with this LDP instance |
Malformed TLV Err | The number of malformed TLV value fatal errors detected for sessions associated with this LDP instance |
Keepalive Expired Err | The number of session keepalive timer expired errors detected for sessions associated with this LDP instance |
Shutdown Notif Sent | The number of shutdown notifications sent related to sessions associated with this LDP instance |
Shutdown Notif Recv | The number of shutdown notifications received related to sessions associated with this LDP instance |
This command resets the LDP instance.
This command restarts or clears statistics for LDP interfaces.
This command restarts or clears statistics for LDP targeted peers.
This command restarts or clears statistics for LDP sessions.
This command clears LDP instance statistics.
The following output shows debug LDP configurations discussed in this section.
This command configures LDP debugging.
This command configures debugging for a specific LDP interface.
This command configures debugging for a specific LDP peer.
This command configures debugging for specific LDP events.
This command displays debugging information about addresses and label bindings learned from LDP peers for LDP bindings.
The no form of the command disables the debugging output.
This command displays specific information (for example, message type, source, and destination) regarding LDP messages sent to and received from LDP peers.
The no form of the command disables debugging output for LDP messages.
This command enables debugging for specific LDP packets.
The no form of the command disables the debugging output.
This command enables debugging for sent and received LDP Hello packets.
The no form of the command disables the debugging output.
This command enables debugging for LDP Init packets. The detail option displays detailed information on the type length value (TLV) included in mac-flush packets.
The no form of the command disables the debugging output.
This command enables debugging for LDP keepalive packets.
The no form of the command disables the debugging output.
This command enables debugging for LDP label packets.
The no form of the command disables the debugging output.