Examples

The following example displays information about all the VRFs configured on the router, including the downstream VRF for each associated VAI. The lines that are highlighted (for documentation purposes only) indicate the downstream VRF.

The table below describes the significant fields shown in the display.

Table 3 show ip vrf detail Field Descriptions

Field

Description

default VPNID

Specifies the VPN ID that uniquely identifies every VPN in the network.

VRF Table ID

Uniquely identifies the VRF routing table.

Interfaces

Specifies the network interfaces.

Export VPN route-target communities

Specifies VPN route-target export communities.

Import VPN route-target communities

Specifies VPN route-target import communities.

VRF label distribution protocol

MPLS label distribution protocol in the VRF context. This is required when VRF is configured for Carrier Supporting Carrier (CSC). This could be LDP (enabled via the mpls ip command on the VRF interface) or BGP (enabled via the send-label command in the router bgp VRF address-family configuration mode).

This command was integrated into Cisco IOS Release 15.2(2)S. The tag keyword and the tag-value, tag-value-dotted-decimal, and mask arguments were added to enable the display of route tags as plain decimals or dotted decimals in the command output.

Cisco IOS XE Release 3.6S

This command was integrated into Cisco IOS XE Release 3.6S. The tag keyword and the tag-value, tag-value-dotted-decimal, and mask arguments were added to enable the display of route tags as plain decimals or dotted decimals in the command output.

15.2(4)M

This command was integrated into Cisco IOS Release 15.2(4)M.

15.2(2)SNI

This command was implemented on the Cisco ASR 901 Series Aggregation Services Routers.

Examples

The following sample output from the show ipv6 route vrf command displays information about the IPv6 routing table associated with VRF1:

The table below describes the significant fields shown in the display.

Table 8 show isis database verbose Field Descriptions

Field

Description

LSPID

Link-state packet (LSP) identifier. The first six octets form the System ID of the router that originated the LSP.

The next octet is the pseudonode ID. When this byte is zero, the LSP describes links from the system. When it is nonzero, the LSP is a pseudonode LSP. This is similar to a router LSA in Open Shortest Path First (OSPF); the LSP describes the state of the originating router. For each LAN, the designated router for that LAN creates and floods a pseudonode LSP that describes all systems attached to that LAN.

The last octet is the LSP number. If all the data cannot fit into a single LSP, the LSP is divided into multiple LSP fragments. Each fragment has a different LSP number. An asterisk (*) indicates that the system issuing this command originated the LSP.

LSP Seq Num

LSP sequence number that allows other systems to determine if they received the latest information from the source.

LSP Checksum

Checksum of the entire LSP packet.

LSP Holdtime

Amount of time that the LSP remains valid (in seconds). An LSP hold time of zero indicates that this LSP was purged and is being removed from all routers’ link-state databases (LSDBs). The value indicates how long the purged LSP will stay in the LSDB before it is completely removed.

ATT

Attach bit. This bit indicates that the router is also a Level 2 router, and it can reach other areas. Level 1 routers use the Attach bit to find the closest Level 2 router. They install a default route to the closest Level 2 router.

P

P bit. This bit detects if the IS can repair area partitions. Cisco and other vendors do not support area partition repair.

OL

Overload bit. This bit determines if the IS is congested. If the overload bit is set, other routers do not use this system as a transit router when they calculate routes. Only packets for destinations directly connected to the overloaded router are sent to this router.

Area Address

Reachable area addresses from the router. For Level 1 LSPs, these are the area addresses configured manually on the originating router. For Level 2 LSPs, these are all the area addresses for the area to which this router belongs.

NLPID

Network Layer Protocol identifier.

Hostname

Hostname of the node.

Router ID

Traffic engineering router identifier for the node.

IP Address

IPv4 address for the interface.

Metric

IS-IS metric for the cost of the adjacency between the originating router and the advertised neighbor, or the metric of the cost to get from the advertising router to the advertised destination (which can be an IP address, an end system (ES), or a Connectionless Network Service [CLNS] prefix).

Displays information about tunnels considered in the IS-IS next hop calculation.

show isis mpls ldp

To display synchronization and autoconfiguration information about interfaces belonging to Intermediate System-to-Intermediate System (IS-IS) processes, use the show isis mpls ldp command in privileged EXEC mode.

Usage Guidelines

This command shows Multiprotocol Label Switching (MPLS) LDP synchronization and autoconfiguration information for interfaces that are running IS-IS processes. If you do not specify a keyword or argument, information appears for each interface that is configured for MPLS LDP synchronization and autoconfiguration. MPLS LDP synchronization and autoconfiguration for IS-IS is supported only in Cisco IOS Release 12.0(32)SY.

Examples

In the following example, interface POS0/2 is running IS-IS. Autoconfiguration is enabled. Synchronization is configured.

This command returns information for interfaces that are configured for IS-IS, which are indicated by the message “ISIS is UP” on the interface.

The table below describes the significant fields shown in the display.

Table 9 show isis mpls ldp Field Descriptions

Field

Description

AUTOCONFIG Information

LDP enabled--Indicates whether LDP autoconfiguration is enabled on this interface. Value is YES or NO.

SYNC Information

Provides synchronization information.

Required--Indicates whether synchronization is required on the interface.

Achieved--Indicates whether synchronization was achieved with LDP. If IS-IS was configured on an interface but synchronization is not achieved, the Achieved field indicates NO. The Required field still indicates YES.

IGP Delay--Indicates whether the IS-IS process must wait for synchronization with LDP before bringing up the interface adjacency.

Holddown time--Valid values are Finite or Infinite. The finite value is equal to the hold-down delay that you configured using the mpls ldp igp sync holddown command. If this field indicates Infinite, hold-down time was not configured. Therefore, IS-IS waits until synchronization is achieved before bringing adjacency UP.

The Holddown time field is significant only if the IGP Delay field indicates YES.

State--Indicates information about the state of synchronization on the interface. If synchronization is achieved, the output shows the following:

SYNC achieved--Synchronization was required and has been achieved.

If synchronization is not achieved, the output shows one of the following:

Holding down until SYNC--No hold-down timer was configured, so IS-IS continues to hold down adjacency until synchronization is achieved.

Holding down with timer--A hold-down timer was configured and IS-IS is holding down adjacency until the timer, indicated in the IGP Delay field, expires.

Maximum metric in effect--Although synchronization was not achieved, the IGP brought up adjacency with the maximum metric.

Related Commands

Command

Description

mpls ldp autoconfig

Globally enables LDP autoconfiguration on all interfaces that belong to an OSPF or IS-IS process.

mpls ldp sync

Enables MPLS LDP-IGP synchronization on interfaces for an OSPF process or an IS-IS process.

Related Commands

show isis mpls traffic-eng downstream-tree

To display the Multiprotocol Label Switching (MPLS) traffic engineering Intermediate System-to-Intermediate System (IS-IS) children list for a specific node, use the show isis mpls traffic-eng downstream-tree command in privileged EXEC mode.

showisismplstraffic-engdownstream-treesystem-id
[ level-1 | level-2 ]

Syntax Description

system-id

Displays the traffic engineering downstream tree information for the specified system ID as either a hostname or in the MAC address format.

Displays information about tunnels considered in the IS-IS next hop calculation.

show isis mpls traffic-eng tunnel

To display information about tunnels considered in the Intermediate System-to-Intermediate System (IS-IS) next hop calculation, use the show isis mpls traffic-eng tunnel command in privileged EXEC mode.

showisismplstraffic-engtunnel

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(5)S

This command was introduced.

12.1(3)T

This command was integrated into Cisco IOS Release 12.1(3)T.

12.0(10)ST

This command was integrated into Cisco IOS Release 12.0(10)ST.

12.2(28)SB

This command was integrated into Cisco IOS Release 12.2(28)SB.

12.2(33)SRA

This command was integrated into Cisco IOS Release 12.2(33)SRA.

12.2SX

This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

Examples

The following is sample output from the show isis mpls traffic-eng tunnel command:

The table below describes the significant fields shown in the display.

Table 12 show isis mpls traffic-eng tunnel Field Descriptions

Field

Description

Station Id

Name or system ID of the MPLS traffic engineering tailend router.

Tunnel Name

Name of the MPLS traffic engineering tunnel interface.

Bandwidth

MPLS traffic engineering specified bandwidth of the tunnel.

Nexthop

MPLS traffic engineering destination IP address of the tunnel.

Metric

MPLS traffic engineering metric of the tunnel.

Mode

MPLS traffic engineering metric mode of the tunnel. It can be relative or absolute.

Related Commands

Command

Description

show mpls traffic-eng autoroute

Displays tunnels that are announced to IGP, including interface, destination, and bandwidth.

show issu clients

To display a list of the current In Service Software Upgrade (ISSU) clients--that is, the network applications and protocols supported by ISSU--use the showissuclientscommand in user EXEC or privileged EXEC mode.

showissuclients

Syntax Description

This command has no arguments or keywords.

Command Modes

User EXEC (>) Privileged EXEC (#)

Command History

Release

Modification

12.2(28)SB

This command was introduced.

12.2(33)SRB1

ISSU is supported on the Cisco 7600 series routers in Cisco IOS Release 12.2(33)SRB1.

12.2(33)SRE

This command was integrated into Cisco IOS Release 12.2(33)SRE.

Usage Guidelines

This command lists all ISSU clients currently operating in the network, along with their Client ID numbers and the number of entities each client contains.

You should enter this command before you enter the issurunversion command, because if a client (application or protocol) that needs to continue operating in the network does not appear in the displayed list, you will know not to continue the software upgrade (because proceeding further with ISSU would then halt the operation of that application or protocol).

Examples

The following example shows a client list displayed by entering this command:

The table below describes the significant fields shown in the display.

Table 13 show issu clients Field Descriptions

Field

Description

Client_ID

The identification number used by ISSU for that client.

Client_Name

A character string describing the client.

“Base Clients” are a subset, which includes:

Inter-Process Communications (IPC)

Redundancy Framework (RF)

Checkpoint Facility (CF)

Cisco Express Forwarding

Network RF (for IDB stateful switchover)

EHSA Services (including ifIndex)

Configuration Synchronization.

Entity_Count

The number of entities within this client. An entity is a logical group of sessions with some common attributes.

Related Commands

Command

Description

showissumessagetypes

Displays the formats, versions, and size of ISSU messages supported by a particular client.

showissunegotiated

Displays results of a negotiation that occurred concerning message versions or client capabilities.

showissusessions

Displays detailed information about a particular ISSU client, including whether the client status is compatible for the impending software upgrade.

show issu entities

To display information about entities within one or more In Service Software Upgrade (ISSU) clients, use the showissuentitiescommand in user EXEC or privileged EXEC mode.

showissuentities [client-id]

Syntax Description

client-id

(Optional) The identification number of a single ISSU client.

Command Modes

User EXEC Privileged EXEC

Command History

Release

Modification

12.2(28)SB

This command was introduced.

12.2(33)SRB1

ISSU is supported on the Cisco 7600 series routers in Cisco IOS Release 12.2(33)SRB1.

Usage Guidelines

An entity is a logical group of sessions that possess some common attributes. Enter a Client_ID if you are interested in seeing information only about one client’s entities. If a Client_ID is not specified, the command will display all ISSU clients’ entities known to the device.

If you are not sure of the precise Client_ID number to enter for the client you are interested in, use the showissuclients command to display the current list of clients with their names and ID numbers.

Examples

The following example shows detailed information about the entities within the virtual routing and forwarding (VRF) (“Table ID”) client:

The identification number used by ISSU for each entity within this client.

Entity_Name

A character string describing the entity.

MsgType Count

The number of message types within the identified entity.

MsgGroup Count

The number of message groups within the identified entity. A message group is a list of message types.

CapType Count

The number of capability types within the identified entity.

CapEntry Count

The number of capability entries within the identified entity. A capability entry is a list of all mutually dependent capability types within a particular client session and, optionally, other capability types belonging to that client session.

CapGroup Count

The number of capability groups within the identified entity. A capability group is a list of capability entries given in priority sequence.

Related Commands

Command

Description

showissuclients

Lists the current ISSU clients--that is, the applications and protocols on this network supported by ISSU.

showissusessions

Displays detailed information about a particular ISSU client--including whether the client status for the impending software upgrade is COMPATIBLE.

show issu message types

To display formats (“types”), versions, and maximum packet size of the In Service Software Upgrade (ISSU) messages supported by a particular client, use the showissumessagetypescommand in user EXEC or privileged EXEC mode.

showissumessagetypesclient-id

Syntax Description

client-id

The identification number used by ISSU for a client application.

Command Modes

User EXEC Privileged EXEC

Command History

Release

Modification

12.2(28)SB

This command was introduced.

12.2(33)SRB1

ISSU is supported on the Cisco 7600 series routers in Cisco IOS Release 12.2(33)SRB1.

Usage Guidelines

If you are not sure of the Client_ID number to enter into this command, use the showissuclients command. It displays the current list of clients, along with their names and ID numbers.

The table below describes the significant fields shown in the display.

Table 15 show issu message types Field Descriptions

Field

Description

Client_ID

The identification number used by ISSU for this client.

Entity_ID

The identification number used by ISSU for this entity.

Message_Type

An identification number that uniquely identifies the format used in the ISSU messages conveyed between the two endpoints.

Version_Range

The lowest and highest message-version numbers contained in the client application.

Message_Ver

Message version. Because each client application contains one or more versions of its messages, ISSU needs to discover these versions and negotiate between the new and old system software which version to use in its preparatory communications.

Message_Mtu

Maximum size (in bytes) of the transmitted message.

A value of 0 means there is no restriction on size; fragmentation and reassembly are therefore being handled in a manner transparent to the ISSU infrastructure.

Related Commands

Command

Description

showissuclients

Lists the current ISSU clients--that is, the applications on this network supported by ISSU.

showissunegotiated

Displays results of a negotiation that occurred concerning message versions or client capabilities.

showissusessions

Displays detailed information about a particular ISSU client, including whether the client status is compatible for the impending software upgrade.

show issu negotiated

To display details of the session’s negotiation about message version or client capabilities, use the showissunegotiatedcommand in user EXEC or privileged EXEC mode.

showissunegotiated
{ version | capability }
session-id

Syntax Description

version

Displays results of a negotiation about versions of the messages exchanged during the specified session, between the active and standby endpoints.

capability

Displays results of a negotiation about the client application’s capabilities for the specified session.

session-id

The number used by In Service Software Upgrade (ISSU) to identify a particular communication session between the active and the standby devices.

Command Modes

User EXEC Privileged EXEC

Command History

Release

Modification

12.2(28)SB

This command was introduced.

12.2(33)SRB1

ISSU is supported on the Cisco 7600 series routers in Cisco IOS Release 12.2(33)SRB1.

Usage Guidelines

If you are not sure of the session_ID number to enter into this command, enter the showissusessions command. It will display the session_ID.

Examples

The following example displays the results of a negotiation about message versions:

The table below describes the significant fields shown in the display.

Table 17 show issu negotiated capability Field Descriptions

Field

Description

Session_ID

The identification number of the session being reported on.

Negotiated_Cap_Entry

A numeral that stands for a list of the negotiated capabilities in the specified client session.

Related Commands

Command

Description

showissuclients

Lists the current ISSU clients--that is, the applications on this network supported by ISSU.

showissumessagetypes

Displays the formats, versions, and maximum packet size of ISSU messages supported by a particular client.

showissusessions

Displays detailed information about a particular ISSU client, including whether the client status is compatible for the impending software upgrade.

show issu sessions

To display detailed information about a particular In Service Software Upgrade (ISSU) client--including whether the client status for the impending software upgrade is compatible--use the showissusessionscommand in user EXEC or privileged EXEC mode.

showissusessionsclient-id

Syntax Description

client-id

The identification number used by ISSU for the client.

Command Modes

User EXEC (>) Privileged EXEC (#)

Command History

Release

Modification

12.2(28)SB

This command was introduced.

12.2(33)SRB1

ISSU is supported on the Cisco 7600 series routers in Cisco IOS Release 12.2(33)SRB1.

12.2(33)SRE

This command was integrated into Cisco IOS Release 12.2(33)SRE.

Usage Guidelines

If you are not sure of the Client_ID number to enter into this command, use the showissuclients command to display the current list of clients with their names and ID numbers.

Examples

The following example shows detailed information about the LDP Client:

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

Cisco IOS XE Release 3.7S

This command was introduced as part of the Multiprotocol Label Switching (MPLS)-based Layer 2 VPN (L2VPN) command modifications for cross-OS support. This command will replace the show mpls l2transport binding command in future releases.

Type 1—The Protocol ID field of the AToM Control Word (CW) is identified in the AToM VCCV packet.

Type 2—An MPLS Router Alert (RA) Level above the VC label identified in the AToM VCCV packet. Type 2 is used for VC types that do not support or do not interpret the AToM Control Word.

VCCV: CC Type

Type of Control Channel (CC) processing that are supported. The number indicates the position of the bit that was set in the received octet. The following values can be displayed:

CW [1]—Control Word

RA [2]—Router Alert

TTL [3]—Time to Live

Unkn [x]—Unknown

CV Type

Type of Connectivity Verification (CV) packets that can be processed in the control channel of the MPLS pseudowire. The following are the CV packets that can be processed. The number following the CV type indicates the position of the bit that was set in the received octet.

ICMP [1]—Internet Control Management Protocol (ICMP) is used to verify connectivity.

LSPV [2]—Link-state packet (LSP) ping is used to verify connectivity.

BFD [3]—Bidirectional Forwarding Detection (BFD) is used to verify connectivity for more than one pseudowire.

Unkn [x]—A CV type was received that could not be interpreted.

The following sample output shows information about L2VPN multisegment pseudowires:

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

Cisco IOS XE Release 3.7S

This command was introduced as part of the Multiprotocol Label Switching (MPLS)-based Layer 2 VPN (L2VPN) command modifications for cross-OS support. This command will replace the show mpls l2transport checkpoint command in future releases.

15.3(1)S

This command was integrated in Cisco IOS Release 15.3(1)S.

Usage Guidelines

The output of the commands varies, depending on whether the output reflects the active or standby Route Processor (RP). In general, the output on the active RP shows that checkpointing information is sent to the backup RP. The output on the backup RP shows that checkpointing information is received from the active RP.

show l2vpn atom hw-capability

To display the transport types supported on an interface, use the show l2vpn atom hw-capability command in privileged EXEC mode.

showl2vpnatomhw-capabilityinterfacetypenumber

Syntax Description

interface

Displays information for the specified interface.

typenumber

Type and number of the interface.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

Cisco IOS XE Release 3.7S

This command was introduced as part of the Multiprotocol Label Switching (MPLS)-based Layer 2 VPN (L2VPN) command modifications for cross-OS support. This command will replace the show mpls l2transport hw-capability command in future releases.

15.3(1)S

This command was integrated in Cisco IOS Release 15.3(1)S.

Usage Guidelines

Use the show l2vpn atom hw-capability command to determine the interface to use for the various transport types. Use this command to check if core-facing and edge-facing interfaces can accommodate different transport types.

Examples

The following is sample output from the show l2vpn atom hw-capability command:

These examples show only a portion of the output. The command displays the capabilities of every transport type.

The table below describes the fields shown in the command display.

Table 21 show l2vpn atom hw-capability Field Descriptions

Field

Description

Transport type

Indicates the transport type.

Core functionality

Displays the functionalities that the core-facing interfaces support, such as label disposition, control word, and sequence number processing.

Edge functionality

Displays the functionalities that the edge-facing interfaces support, such as label disposition, control word, and sequence number processing.

Related Commands

Command

Description

show l2vpn atom binding

Displays VC label binding information.

show l2vpn atom checkpoint

Displays the checkpoint information about AToM VCs.

show l2vpn atom summary

Displays summary information about VCs.

show l2vpn atom vc

Displays information about AToM VCs and static pseudowires that have been enabled to route Layer 2 packets on a device.

show mpls l2transport hw-capability

Displays the transport types supported on an interface.

show l2vpn atom memory

To display the Layer 2 VPN (L2VPN) Any Transport over MPLS (AToM) memory usage information, use the show l2vpn atom memory command in privileged EXEC mode.

show l2vpn atom memory
[ detail ]

Syntax Description

detail

(Optional) Displays detailed information for L2VPN AToM memory usage.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

Cisco IOS XE Release 3.7S

This command was introduced as part of the Multiprotocol Label Switching (MPLS)-based L2VPN command modifications for cross-OS support. This command will replace the show mpls l2transport memory command in future releases.

Examples

The following is sample output from the show l2vpn atom memory detail command:

show l2vpn atom pwid

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

Cisco IOS XE Release 3.7S

This command wasS introduced as part of the Multiprotocol Label Switching (MPLS)-based L2VPN command modifications for cross-OS support.. This command will replace the show mpls l2transport pwid command in future releases.

15.3(1)S

This command was integrated in Cisco IOS Release 15.3(1)S.

Examples

The following is sample output from the show l2vpn atom pwid command. The output fields are self-explanatory.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

Cisco IOS XE Release 3.7S

This command was introduced as part of the Multiprotocol Label Switching (MPLS)-based L2VPN command modifications for cross-OS support. This command will replace the show mpls l2transport static-oam command in future releases.

15.3(1)S

This command was integrated in Cisco IOS Release 15.3(1)S.

Examples

The following example shows how to enable the display of status messages for the static pseudowire with peer IP address of 10.10.10.10 and VC ID of 4:

Related Commands

show l2vpn atom summary

To display summary information about virtual circuits (VCs) that have been enabled to route Any Transport over MPLS (AToM) Layer 2 packets on a device, use the show l2vpn atom summary command in privileged EXEC mode.

showl2vpnatomsummary

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

Cisco IOS XE Release 3.7S

This command was introduced as part of the Multiprotocol Label Switching (MPLS)-based Layer 2 VPN (L2VPN) command modifications for cross-OS support. This command will replace the show mpls l2transport summary command in future releases.

15.3(1)S

This command was integrated in Cisco IOS Release 15.3(1)S.

Usage Guidelines

This command will replace the show mpls l2transport summary command in future releases.

Examples

The following is sample output from the command that shows summary information about the VCs that have been enabled to transport Layer 2 packets:

Displays information about AToM VCs that have been enabled to route Layer 2 packets on a device.

show mpls l2transport summary

Displays summary information about VCs that have been enabled to route AToM Layer 2 packets on a device.

show l2vpn atom vc

To display information about Any Transport over MPLS (AToM) virtual circuits (VCs) and static pseudowires that have been enabled to route Layer 2 packets on a device, use the show l2vpn atom vc command in user EXEC or privileged EXEC mode.

Syntax Description

vcid

(Optional) Displays the VC ID.

vc-id-min

(Optional) Minimum VC ID value. The range is from 1 to 4294967295.

vc-id-max

(Optional) Maximum VC ID value. The range is from 1 to 4294967295.

interface

(Optional) Displays the interface or subinterface of the device that has been enabled to transport Layer 2 packets. Use this keyword to display information about the VCs that have been assigned VC IDs on that interface or subinterface.

type

(Optional) Interface type. For more information about the interface type, use the question mark (?) online help function.

number

(Optional) Interface or subinterface number. For more information about the numbering syntax for your networking device, use the question mark (?) online help function.

local-circuit-id

(Optional) The number assigned to the local circuit. This argument value is supported only with the following transport types:

(Optional) Displays information about dynamically stitched pseudowires between specified endpoints. The endpoints are the Source Attachment Individual Identifier (SAII) and the Target Attachment Individual Identifier (TAII). When the stitch keyword is used with the vpls-id keyword, a single pair of stitched VCs is displayed.

Command Default

The command displays a summary of all the VCs.

Command Modes

User EXEC (>)

Privileged EXEC (#)

Command History

Release

Modification

Cisco IOS XE Release 3.7S

This command was introduced as part of the Multiprotocol Label Switching (MPLS)-based L2VPN command modifications for cross-OS support. This command will replace the show mpls l2transport vc command in future releases.

15.3(1)S

This command was integrated in Cisco IOS Release 15.3(1)S.

Usage Guidelines

The output of the commands varies based on the type of Layer 2 packets being transported over AToM VCs.

Examples

The following is sample output from the show l2vpn atom vc command, which displays information about interfaces and VCs that are configured to transport various Layer 2 packets on the device:

Interface on the local device that is enabled to transport Layer 2 packets.

Local circuit

Type and number (if applicable) of the local circuit. The output shown in this column varies, depending on the transport type:

For Frame Relay, the output shows the DLCI of the PVC.

For ATM cell relay and AAL5, the output shows the VPI or VCI of the PVC.

For Ethernet VLANs, the output shows the VLAN number.

For PPP and High-Level Data Link Control (HDLC), the output shows the interface number.

Dest address

IP address of the remote device’s interface that is the other end of the VC.

VC ID

VC identifier assigned to one of the interfaces on the device.

Status

Status of the VC, which can be one of the following:

Admin down—The VC is disabled by a user.

Down—The VC is not ready to carry traffic between the two VC endpoints. Use the detail keyword to determine the reason that the VC is down.

Hotstandby—The active pseudowire on a standby Route Processor (RP).

Recovering—The VC is recovering from a stateful switchover.

Standby—The VC is designated as the backup circuit in a stateful switchover configuration.

Up—The VC can carry traffic between the two VC endpoints. A VC is up when both imposition and disposition interfaces are programmed.

The disposition interface is programmed if the VC is configured and the client interface is up.

The imposition interface is programmed if the disposition interface is also programmed, and a remote VC label and an Interior Gateway Protocol (IGP) label are configured. The IGP label can be implicit null in a back-to-back configuration. The IGP label implies that there is a label switched path (LSP) to the peer.

The following is sample output from the show l2vpn atom vc detail command and shows information about the nonstop forwarding (NSF), stateful switchover (SSO), and graceful restart capabilities on the AToM VC. The SSO portion indicates whether checkpoint data is sent (on active) or received (on standby). When SSO data is successfully sent or is released, the SSO information is not displayed.

The following is sample output from the show l2vpn atom vc detail command and shows the information that is displayed when an AToM static pseudowire is provisioned and the command is used to check the configuration. The Signaling protocol field specifies “Manual” because a directed control protocol such as Label Distribution Protocol (LDP) cannot be used to exchange parameters on static pseudowires. The remote interface description field seen for nonstatic pseudowire configurations is not displayed because remote information is exchanged using signaling between the provider edge (PE) devices and not on static pseudowires.

The following is sample output from the show l2vpn atom vc detail command and shows VC statistics, including the number of packets and bytes being sent from the device. The VC statistics fields include the word “transit” to indicate that the packet totals no longer include packets being sent to the device.

The table below describes the significant fields shown in the display.

Table 24 show l2vpn atom vc detail Field Descriptions

Field

Description

Local interface

Interface on the local device that has been enabled to send and receive Layer 2 packets. The interface varies, depending on the transport type. The output also shows the status of the interface.

line protocol

Status of the line protocol on the edge-facing interface.

Destination address

IP address of the remote device specified for the VC. Specify the destination IP address as part of the mpls l2transport route command.

VC ID

VC identifier assigned to the interface on the device.

VC status

Status of the VC, which can be one of the following:

Admin down—The VC was disabled by a user.

Down—The VC is not ready to carry traffic between the two VC endpoints.

up—The VC is in a state where it can carry traffic between the two VC endpoints. A VC is up when both imposition and disposition interfaces are enabled.

The disposition interface is enabled if the VC is configured and the client interface is up.

The imposition interface is enabled if the disposition interface is enabled and a remote VC label and an IGP label exist. The IGP label can be an implicit null in a back-to-back configuration. (An IGP label implies that there is an LSP to the peer.)

Output interface

Interface on the remote device that has been enabled to transmit and receive Layer 2 packets.

imposed label stack

Summary of the Multiprotocol Label Switching (MPLS) label stack used to direct the VC to the PE device.

Preferred path

Path that was assigned to the VC and the status of that path. The path can be an MPLS traffic engineering tunnel or an IP address or hostname of a peer PE device.

Default path

Status of the default path, which can be disabled or active.

By default, if the preferred path fails, the device uses the default path. However, you can disable the device from using the default path when the preferred path fails by specifying the disable-fallback keyword with the preferred-path command.

Tunnel label

IGP label used to route the packet over the MPLS backbone to the destination device. The first part of the output displays the type of label. The second part of the output displays the route information.

The tunnel label information can display any of the following states:

imp-null—Implicit null means that the provider device is absent and the tunnel label will not be used. Alternatively, imp-null can signify traffic engineering tunnels between the PE devices.

not ready, LFIB entry present—The tunnel label exists in the Label Forwarding Information Base (LFIB), but the VC is down.

not ready, no route—An IP route for the peer does not exist in the routing table.

not ready, not a host table—The route in the routing table for the remote peer device is not a host route.

unassigned—The label has not been assigned.

Create time

Time (in hours, minutes, and seconds) when the VC is provisioned.

last status change time

Last time (in hours, minutes, and seconds) when the VC state change occurred.

Signaling protocol

Type of protocol used to send the MPLS labels on dynamically configured connections. The output also shows the status of the peer device. For AToM statically configured pseudowires, the field indicates Manual because there is no exchange of labels using a directed control protocol, such as LDP.

MPLS VC labels

Local VC label is a disposition label, which identifies the egress interface of an arriving packet from the MPLS backbone. The remote VC label is a disposition VC label of the remote peer device.

Group ID

Local group ID used to group VCs locally. The remote group ID is used by the peer to group several VCs.

MTU

Maximum transmission unit (MTU) specified for local and remote interfaces.

Remote interface description

Interface on the remote device that is enabled to transmit and receive Layer 2 packets.

Sequencing

Indicates whether sequencing of out-of-order packets is enabled or disabled.

SSO Descriptor

Identifies the VC for which the information is checkpointed.

local label

Value of the local label that is checkpointed (that is, sent on the active RP and received on the standby RP).

SSM segment/switch IDs

IDs used for the control plane and data plane for this VC. This data is not for customer use but for Cisco personnel for troubleshooting purposes. When the Source Specific Multicast (SSM) IDs are followed by the word “used,” the checkpointed data has been successfully sent.

PWID

Pseudowire ID used in the data plane to correlate the switching context for the segment associated with the MPLS switching context. This data is not for customer use but for Cisco personnel for troubleshooting purposes.

packet totals

Number of packets sent and received. Received packets are those AToM packets received from the MPLS core. Sent packets are those AToM packets sent to the MPLS core. This number excludes dropped packets.

Note

If the VC statistics fields include the word “transit,” the output shows the number of packets and bytes being sent from the device.

byte totals

Number of bytes sent and received from the core-facing interface, including the payload, control word if present, and AToM VC label.

Note

If the VC statistics fields include the word “transit,” the output shows the number of packets and bytes being sent from the device.

packet drops

Number of dropped packets.

Note

If the VC statistics fields include the word “transit,” the output shows the number of packets and bytes being sent from the device.

The following is sample output from the show l2vpn atom vc detail command when the VPLS Autodiscovery feature has been configured on VPLS pseudowires.

For the local device, the output indicates whether the MPLS Pseudowire Signaling Status feature is enabled or disabled. For the remote device, the output indicates whether the MPLS Pseudowire Signaling Status feature is supported.

Label/status state machine

The first value in the output indicates whether label advertisement has been established or not. The second value (LruRru) indicates the status of the local and remote devices. The following list translates the status codes:

D—Dataplane

L—local device

r or n—ready (r) or not ready (n)

R—remote device

S—Local shutdown

u or d—up (u) or down (d) status

Last local dataplane status rcvd

Last status message received about the dataplane on the local device.

Last local SSS circuit status rcvd

Last status message received about the subscriber service switch (SSS) on the local device.

Last local SSS circuit status sent

Last status message sent about the subscriber service switch on the local device.

Last local LDP TLV status sent

Last status message sent about the type, length, values (TLV) on the local device.

Last remote LDP TLV status rcvd

Last status message received about the TLV on the local device.

The following sample output from the show l2vpn atom vc detail command displays the status of multisegment pseudowires:

If the control word is negotiated by the peer and is different from the configured value, the configured value is shown in parentheses.

If the control word is configured to be disabled, the displayed value is as follows:

Control Word: off (configured: disabled)

If the control word is configured to be enabled but negotiated by the peer to be off, the displayed value is as follows:

Control Word: off (configured: enabled)

If the control word is not configured, the displayed value is as follows:

Control Word: on (configured: autosense)

The following sample output from the show l2vpn atom vc detail command displays load balancing information and shows whether flow labels are added to the MPLS label as part of the L2VPN Advanced VPLS feature:

The following is sample output from the show l2vpn atom vc command when the L2VPN VPLS Inter-AS Option B feature has been configured. The fields in the display are self-explanatory or described in other tables in this document:

The following is sample output from the show l2vpn atom vc detail command when there is a remote AC failure and when VCCV BFD status signaling is enabled, that is, vccv bfd status signaling is configured:

Command Default

Information about the L2VPN pseudowire MIB for all peers is displayed.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

Cisco IOS XE Release 3.7S

This command was introduced as part of the Multiprotocol Label Switching (MPLS)-based L2VPN command modifications for cross-OS support. This command will replace the pwmib keyword in the show xconnect command in future releases.

15.3(1)S

This command was integrated in Cisco IOS Release 15.3(1)S.

Usage Guidelines

Use the show l2vpn pwmib command to display information about the L2VPN pseudowire MIB. You can specify the peer IP address and the virtual circuit (VC) ID value to display information associated with the specified peer IP address and the specified VC ID.

Examples

The following is sample output from the show l2vpn pwmib command for a peer with IP address is 10.3.2.1 and a VC ID value of 4000:

(Optional) IP address and network number or autonomous system number (ASN) and network number of the VPLS.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

Cisco IOS XE Release 3.7S

This command was introduced as part of the Multiprotocol Label Switching (MPLS)-based L2VPN command modifications for cross-OS support. This command will replace the rib keyword in the show xconnect command in future releases.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

Cisco IOS XE Release 3.7S

This command was introduced as part of the Multiprotocol Label Switching (MPLS)-based L2VPN command modifications for cross-OS support. This command will replace the show vfi command in future releases.

15.3(1)S

This command was integrated in Cisco IOS Release 15.3(1)S.

Examples

The following is sample output from the show l2vpn vfi command when Label Distribution Protocol (LDP) signaling is used. The output fields are self-explanatory.

This command was integrated into Cisco IOS Release 12.2(28)SB and implemented on the Cisco 10000-PRE2 router.

12.4(20)T

This command was removed.

Usage Guidelines

The ATM label binding database contains entries for label virtual circuits (VCs) on label-controlled (LC)-ATM interfaces. Command output can show a summary of entries from the entire database, or the output can be limited to a subset of entries based on the following:

Specific prefix

Specific VC label value

Specific assigning interface

Note

This command displays ATM label bindings learned by the Label Distribution Protocol (LDP) or Tag Distribution Protocol (TDP). TDP is not supported for LDP features in Cisco IOS 12.0(30)S and later releases, 12.2(27)SBC and later 12.2S releases, and 12.3(14)T and later releases.

Note

The show mpls ip binding command includes the output generated by the show mpls atm-ldp bindings command and information about label bindings for packet interfaces.

Examples

The following is sample output from the show mpls atm-ldp bindings command:

Syntax Description

Command Default

This command always displays all the MPLS ATM capabilities negotiated with all the LDP neighbors.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

11.1CT

This command was introduced.

12.0(10)ST

This command was modified to use MPLS Internet Engineering Task Force (IETF) command syntax and terminology.

12.0(14)ST

This command was integrated into Cisco IOS Release 12.0(14)ST.

12.1(2)T

This command was integrated into Cisco IOS Release 12.1(2)T.

12.1(8a)E

This command was integrated into Cisco IOS Release 12.1(8a)E.

12.2(2)T

This command was integrated into Cisco IOS Release 12.2(2)T.

12.2(4)T

This command was integrated into Cisco IOS Release 12.2(4)T.

12.2(8)T

This command was integrated into Cisco IOS Release 12.2(8)T.

12.0(21)ST

This command was integrated into Cisco IOS Release 12.0(21)ST.

12.0(22)S

This command was integrated into Cisco IOS Release 12.0(22)S.

12.0(23)S

This command was integrated into Cisco IOS Release 12.0(23)S.

12.2(13)T

This command was integrated into Cisco IOS Release 12.2(13)T.

12.2(14)S

This command was integrated into Cisco IOS Release 12.2(14)S.

12.2(28)SB

This command was integrated into Cisco IOS Release 12.2(28)SB and implemented on the Cisco 10000-PRE2 router.

12.4(20)T

This command was removed.

Usage Guidelines

When two label switch routers (LSRs) establish an LDP session, they negotiate parameters for the session, such as the range of virtual path identifiers (VPIs) and virtual channel identifiers (VCIs) that will be used as labels.

This command displays the MPLS ATM capabilities negotiated by LDP or the Tag Distribution Protocol (TDP).

Note

TDP is not supported for LDP features in Cisco IOS 12.0(30)S and later releases, 12.2(27)SBC and later 12.2S releases, and 12.3(14)T and later releases.

Examples

The following is sample output from the show mpls atm-ldp capability command:

The table below describes the significant fields shown in the display.

Table 36 show mpls atm-ldp capability Field Descriptions

Field

Description

VPI Range

Minimum and maximum numbers of VPIs supported on this interface.

VCI Range

Minimum and maximum numbers of VCIs supported on this interface.

Alloc Scheme

Indicates the applicable allocation scheme, as follows:

UNIDIR--Unidirectional capability indicates that the peer can, within a single VPI, support binding of the same VCI to different prefixes on different directions of the link.

BIDIR--Bidirectional capability indicates that within a single VPI, a single VCI can appear in one binding only. In this case, one peer allocates bindings in the even VCI space, and the other in the odd VCI space. The system with the lower LDP identifier assigns even-numbered VCIs.

The negotiated allocation scheme is UNIDIR, only if both peers have UNIDIR capability. Otherwise, the allocation scheme is BIDIR.

Note

These definitions for unidirectional and bidirectional are consistent with normal ATM usage of the terms; however, they are exactly opposite from the definitions for them in the IETF LDP specification.

Odd/Even Scheme

Indicates whether the local device or the peer is assigning an odd- or even-numbered VCI when the negotiated scheme is BIDIR. It does not display any information when the negotiated scheme is UNIDIR.

VC Merge

Indicates the type of virtual circuit (VC) merge support available on this interface. There are two possibilities, as follows:

IN--Indicates the input interface merge capability. IN accepts the following values:

Syntax Description

Specifies the depth of the label stack. The range is from 1 to 1048575. The default value is zero.

labelouter-most-value

Specifies the top-most label in the incoming packet. The range is from 16 to 1048575. The default value is zero.

labelinner-most-value

(Optional) Specifies the bottom-most label in the incoming packet. The range is from 16 to 1048575. The default value is zero.

Command Modes

User EXEC (>) Privileged EXEC (#)

Command History

Release

Modification

15.1(2)S

This command was introduced on Cisco 7600 series routers.

Usage Guidelines

You can use the show mls cef mpls exact-route command to find the actual path used by the label traffic in an Equal Cost Multipath (ECMP). This command helps in debugging Layer 2 VPN (L2VPN) ) and Layer 3 VPN (L3VPN) load balancing.

Note

The show mls cef mpls exact-route command is supported only for L2VPN and L3VPN.

You must configure the appropriate parameters based on the control word in the incoming packets as follows:

If the incoming packet contains the control word, you need not provide the source and destination address along with the label stack depth value.

Note

You must configure the inner label value if you do not specify the source and destination IP address.

If the incoming packet does not have the control word, you must provide all the attributes applicable for the packet; that is, source address, destination address, and label stack depth value.

Note

The show mls cef mpls exact-route command may not display valid results when you use the command on provider edge (PE) routers for L2 and L3 VPNs. Hence, Cisco does not recommend using the command on PE routers for L2 and L3 VPNs.

Examples

The following is sample output from the show mls cef mpls exact-route command. Fields in the display are self-explanatory.

Related Commands

show mpls cos-map

Note

Effective with Cisco IOS Release 12.4(20)T, the show mpls cos-map command is not available in Cisco IOS software.

To display the quality of service (QoS) map used to assign a quantity of label virtual circuits and the associated class of service (CoS) for those virtual circuits, use the show mpls cos-map in privileged EXEC mode.

showmplscos-map [cos-map]

Syntax Description

cos-map

(Optional) Number specifying the QoS map to be displayed.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

12.0(5)T

This command was introduced.

12.0(10)ST

This command was modified to match Multiprotocol Label Switching (MPLS) syntax and terminology.

12.2(2)T

This command was integrated into Cisco IOS Release 12.2(2)T.

12.2(25)S

The heading in the output was changed from tag-vc to label-vc.

12.2(28)SB

This command was integrated into Cisco IOS Release 12.2(28)SB.

12.4(20)T

This command was removed.

Usage Guidelines

Not entering a specific QoS number causes all QoS maps to be displayed.

In this example, the mpls export vpnv4 prefixes command was not configured. Therefore, the MPLS PAL table did not export a route distinguisher for the Border Gateway Protocol (BGP) application, and the associated prefix is exported as 0.0.0.0.

The table below describes the significant fields shown in the display.

Table 39 show mpls flow mappings Field Descriptions

Field

Description

Label

Value given to the MPLS label by the router.

Owner

MPLS application that allocated the label.

LDP = Label Distribution Protocol

BGP = Border Gateway Protocol

TE-MIDT = Traffic engineering tunnel midpoint

Route-Distinguisher

Value (8-byte) that is concatenated with an IPv4 prefix to create a unique VPN IPv4 prefix.

Prefix

Prefix used by the router to route data to the destination address.

Allocated

System uptime at which the MPLS PAL mapping record was created.

The following is sample output from the show mpls flow mappings command if you previously entered the mpls export vpnv4 prefixes command:

Related Commands

Displays the status and the statistics for NetFlow accounting data export.

show mpls forwarding vrf

To display label forwarding information for advertised Virtual Private Network (VPN) routing and forwarding (VRF) instance routes, use the show mpls forwarding vrf command in privileged EXEC mode. To disable the display of label forwarding information, use the no form of this command.

(Optional) Displays information in long form (includes length of encapsulation, length of MAC string, maximum transmission unit [MTU], and all labels).

slotslot-number

(Optional) Specifies the slot number, which is always 0.

Command Modes

User EXEC (>) Privileged EXEC (#)

Command History

Release

Modification

11.1CT

This command was introduced.

12.1(3)T

This command was integrated into Cisco IOS Release 12.1(3)T. The command was updated with MPLS terminology and command syntax.

12.2(8)T

This command was integrated into Cisco IOS Release 12.2(8)T. The command was modified to accommodate use of the MPLS experimental (EXP) level as a selection criterion for packet forwarding. The output display was modified to include a bundle adjacency field and exp (vcd) values when the optional detail keyword is specified.

12.0(22)S

This command was integrated into Cisco IOS Release 12.0(22)S. The IPv6 MPLS aggregate label and prefix information was added to the display.

12.2(14)S

This command was integrated into Cisco IOS Release 12.2(14)S.

12.0(27)S

This command was integrated into Cisco IOS Release 12.0(27)S. The command output was modified to include explicit-null label information.

12.2(25)S

This command was integrated into Cisco IOS Release 12.2(25)S. The output was changed in the following ways:

The term “tag” was replaced with the term “label.”

The term “untagged” was replaced with the term “no label.”

12.2(28)SB

This command was integrated into Cisco IOS Release 12.2(28)SB and implemented on the Cisco 10000 series routers.

12.2(33)SRA

This command was integrated into Cisco IOS Release 12.2(33)SRA. This command was modified to remove the lsp-tunnel keyword.

12.2(33)SXH

This command was modified. The command output shows the status of local labels in holddown for the Cisco IOS Software Modularity: MPLS Layer 3 VPNs feature. The status indicator showing that traffic is forwarded through an LSP tunnel is moved to the local label and the lsp-tunnel keyword was removed.

Cisco IOS XE Release 3.1S

This command was integrated into Cisco IOS XE Release 3.1S.

15.1(1)S

This command was integrated into Cisco IOS Release 15.1(1)S. The output was modified to display the pseudowire identifier when the interface keyword is used.

15.1(2)SNG

This command was integrated into Cisco ASR 901 Series Aggregation Services Routers.

Examples

The following is sample output from the show mpls forwarding-table command:

The following is sample output from the show mpls forwarding-table command when the IPv6 Provider Edge Router over MPLS feature is configured to allow IPv6 traffic to be transported across an IPv4 MPLS backbone. The labels are aggregated because there are several prefixes for one local label, and the prefix column contains “IPv6” instead of a target prefix.

The following is sample output from the show mpls forwarding-table detail command. If the MPLS EXP level is used as a selection criterion for packet forwarding, a bundle adjacency exp (vcd) field is included in the display. This field includes the EXP value and the corresponding virtual circuit descriptor (VCD) in parentheses. The line in the output that reads “No output feature configured” indicates that the MPLS egress NetFlow accounting feature is not enabled on the outgoing interface for this prefix.

The following is sample output from the show mpls forwarding-table detail command. In this example, the MPLS egress NetFlow accounting feature is enabled on the first three prefixes, as indicated by the line in the output that reads “Feature Quick flag set.”

[H]--Local labels are in holddown, which means that the application that requested the labels no longer needs them and stops advertising them to its labeling peers.

The label’s forwarding-table entry is deleted after a short, application-specific time.

If any application starts advertising a held-down label to its labeling peers, the label could come out of holddown.

Note

[H] is not shown if labels are held down globally.

A label enters global holddown after a stateful switchover or a restart of certain processes in a Cisco IOS modularity environment.

[T]--The label is forwarded through an LSP tunnel.

Note

Although [T] is still a property of the outgoing interface, it is shown in the Local Label column.

[HT]--Both conditions apply.

Examples

The following is sample output from the show mpls forwarding-table interface command. In this example, the pseudowire identifier (that is, 4096) is displayed in the Prefix or Tunnel Id column. The show mpls l2transport vc detail command can be used to obtain more information about the specific pseudowire displayed.

Syntax Description

(Optional) Defines the interface about which to display label switching information.

vrfvpn-name

(Optional) Displays information about the interfaces that have been configured for label switching for the specified Virtual Private Network (VPN) routing and forwarding (VRF) instance (vpn-name).

all

(Optional) When the all keyword is specified alone in this command, information about the interfaces configured for label switching is displayed for all VPNs, including the VPNs in the default routing domain.

The following is sample output from the show mpls interfaces internal command. The output shows whether MPLS egress NetFlow accounting is enabled on the interface. If MPLS egress NetFlow accounting is disabled, the Output_feature_state field displays 0x0. If MPLS egress Netflow accounting is enabled, the Output_feature_state field is any number, except 0x0.

These keywords and arguments do not apply to the Cisco 10000 series routers.

local-labellabel-label

(Optional) Displays entries with locally assigned labels that match the specified label values. Use the arguments and keyword to indicate the label range. The hyphen (-) keyword is required for a label range.

These keywords and arguments do not apply to the Cisco 10000 series routers.

remote-labellabel-label

(Optional) Displays entries with remotely assigned labels learned from neighbor routers that match the specified label values. Use the arguments to indicate the label range. The hyphen (-) keyword is required for a label range.

Usage Guidelines

TDP is not supported for LDP features in Cisco IOS 12.0(30)S and later releases, 12.2(27)SBC and later 12.2S releases, and 12.3(14)T and later releases.

To summarize information about label bindings learned by LDP, use the show mpls ip binding summary command in user EXEC or privileged EXEC mode.

A request can specify that the entire database be displayed, that a summary of entries from the database be displayed, or that the display be limited to a subset of entries. The subset can be limited according to any of the following:

Prefix

Input or output label values or ranges

Neighbor advertising the label

Interface for label bindings of interest (LC-ATM only)

Note

LC-ATM label binding interface does not apply to the Cisco 10000 series routers.

Generic (non-LC-ATM) label bindings

LC-ATM label bindings

Note

LC-ATM label binding interface does not apply to the Cisco 10000 series routers.

Examples

The following is sample output from the show mpls ip binding command. The output shows all the label bindings in the database.

Syntax Description

Displays the LDMs for the routing table you specify. Table 0 is the default or global routing table.

vrf

(Optional) Displays the LDMs for the VPN routing and forwarding (VRF) instance you specify.

vrf-name

(Optional) The name of the VRF instance. You can find VRF names with the show ip vrf command.

ipv4

(Optional) Displays IPv4 LDMs.

ipv6

(Optional) Displays IPv6 LDMs.

Note

Applies to Cisco 7500 series routers only.

Command Default

If you do not specify any keywords or parameters, the command displays the LDMs for the global routing table (the default).

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(25)S

This command was introduced.

12.2(28)SB

This command was integrated into Cisco IOS Release 12.2(28)SB and implemented on the Cisco 10000 series routers.

12.2(33)SRA

This command was integrated into Cisco IOS Release 12.2(33)SRA.

12.2(33)SXH

This command was integrated into Cisco IOS Release 12.2(33)SSH.

12.4(20)T

This command was integrated into Cisco IOS Release 12.4(20)T.

Usage Guidelines

This command displays the IP LDMs registered with IPRM.

Examples

The command in the following example displays the LDMs for the global routing tables. It shows that two LDMs (lcatm and ldp) are registered for the ipv4 global routing table, and that one LDM (bgp ipv6) is registered for the ipv6 global routing table.

The table below describes the significant fields shown in the display.

Table 52 show mpls l2transport binding Field Descriptions

Field

Description

Destination Address

The IP address of the remote router’s interface that is at the other end of the VC.

VC ID

The virtual circuit identifier assigned to one of the interfaces on the router.

Local Label

The VC label that a router signals to its peer router, which is used by the peer router during imposition.

Remote Label

The disposition VC label of the remote peer router.

Cbit

The control word bit. If it is set, the value is 1.

VC Type

The type of VC, such as Frame Relay, Ethernet, and ATM.

GroupID

The group ID assigned to the local or remote VCs.

MTU

The maximum transmission unit assigned.

Interface Desc

Interface parameters, if applicable.

VCCV Capabilities

(Cisco IOS Releases 12.0(27)S and 12.2(18)SXE and later releases) AToM VCCV information. This field displays how an AToM VCCV packet is identified.

Type 1--The Protocol ID field of the AToM Control Word (CW) is identified in the AToM VCCV packet.

Type 2--An MPLS Router Alert (RA) Level above the VC label in identified in the AToM VCCV packet. Type 2 is used for VC types that do not support or do not interpret the AToM Control Word.

VCCV: CC Type

(Cisco IOS Releases 12.2(30)S and later releases) The types of Control Channel (CC) processing that are supported. The number indicates the position of the bit that was set in the received octet. The following values can be displayed:

CW [1]--Control Word

RA [2]--Router Alert

TTL [3]--Time to Live

Unkn [x]--Unknown

CV Type

(Cisco IOS Releases 12.2(30)S and later releases) The type of Connectivity Verification (CV) packets that can be processed in the control channel of the MPLS pseudowire. The number indicates the position of the bit that was set in the received octet.

ICMP [1]--Internet Control Management Protocol (ICMP) is used to verify connectivity.

LSPV [2]--LSP Ping is used to verify connectivity.

BFD [3]--Bidirectional Forwarding Detection is used to verify connectivity for more than one pseudowire.

CEM circuits are supported on the Cisco 7600 series router transport time-division multiplexing (TDM) traffic. The following sample output displays AToM VCs and the applicable local and remote CEM settings as exchanged over LDP label mapping messages.

In general, the output on the active RP shows that checkpointing information was sent to the backup RP. The output on the backup RP shows that checkpointing information was received from the active RP.

Related Commands

Command

Description

show mpls l2transport vc

Displays information about the checkpointed data when checkpointing is enabled.

show mpls l2transport hw-capability

To display the transport types supported on an interface, use the show mpls l2transport hw-capability command in privileged EXEC mode.

Usage Guidelines

This command can help you determine the interface to use for the various transport types. Use this command to check if core-facing and edge-facing interfaces can accommodate different transport types.

Examples

The following is partial sample output of the show mpls l2transport hw-capability command for Cisco IOS Releases 12.0(23)S, 12.2(14)S, and 12.2(15)T and later. For more information on the fields, see the table below.

These examples show only a portion of the output. The command displays the capabilities of every transport type.

The following is partial sample output of the show mpls l2transport hw-capability command for Cisco IOS Releases 12.0(27)S and 12.2(18)SXE and later releases. This output shows VCCV data under the Core Functionality section. Type 1 means that the AToM Control Word identified the AToM VCCV packet. For more information on the fields, see the table below.

The following is partial sample output of the show mpls l2transport hw-capability command for Cisco IOS Releases 12.2(30)S and later releases. The VCCV output shows that AToM Control Word (CW) identified the AToM VCCV packet. For more information on the fields, see the table below.

Related Commands

show mpls l2transport summary

To display summary information about virtual circuits (VCs) that have been enabled to route Any Transport over MPLS (AToM) Layer 2 packets on a router, use the show mpls l2transport summary command in privileged EXEC mode.

showmplsl2transportsummary

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

12.0(23)S

This command was introduced.

12.2(14)S

This command was integrated into Cisco IOS Release 12.2(14)S.

12.2(15)T

This command was integrated into Cisco IOS Release 12.2(15)T.

12.2(33)SRA

This command was integrated into Cisco IOS Release 12.2(33)SRA.

12.2SX

This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

12.2(33)SCC

This command was integrated into Cisco IOS Release 12.2(33)SCC.

Examples

The following is a sample output of the show mpls l2transport summary command that shows summary information about the VCs that have been enabled to transport Layer 2 packets:

The following is a sample output of the show mpls l2transport summary command that shows summary information about the VCs that have been enabled to transport Layer 2 packets on a Cisco uBR10012 router:

The table below describes the fields shown in the show mpls l2transport summary command display.

Table 55 show mpls l2transport summary Field Descriptions

Field

Description

Destination address

IP address of the remote router to which the VC has been established.

Total number of VCs

Number of VCs that have been established.

unknown

Number of VCs that are in an unknown state.

up

Number of VCs that are operational.

down

Number of VCs that are not operational.

admin down

Number of VCs that have been disabled.

Related Commands

Command

Description

show mpls l2transport binding

Displays virtual circuit (VC) label binding information.

show mpls l2transport checkpoint

Displays the checkpoint information about Any Transport over MPLS (AToM) virtual circuits.

show mpls l2transport hw-capability

Displays the transport types and their supported capabilities.

show mpls l2transport vc

Displays information about AToM VCs that have been enabled to route Layer 2 packets on a router.

show mpls l2transport vc

To display information about Any Transport over MPLS (AToM) virtual circuits (VCs) and static pseudowires that have been enabled to route Layer 2 packets on a router, use the show mpls l2transport vc command in user EXEC or privileged EXEC mode.

Syntax Description

vcid

(Optional) Specifies the VC ID.

vc-id-min

(Optional) Minimum VC ID value. The range is 1 to 4294967295.

vc-id-max

(Optional) Maximum VC ID value. The range is 1 to 4294967295.

interface

(Optional) Specifies the interface or subinterface of the router that has been enabled to transport Layer 2 packets. Use this keyword to display information about the VCs that have been assigned VC IDs on that interface or subinterface.

type

(Optional) Interface type. For more information about the interface type, use the question mark (?) online help function.

number

(Optional) Interface or subinterface number. For more information about the numbering syntax for your networking device, use the question mark (?) online help function.

local-circuit-id

(Optional) The number assigned to the local circuit. This argument value is supported only with the following transport types:

(Optional) Specifies dynamically stitched pseudowires between specified endpoints. The endpoints are the Source Attachment Individual Identifier (SAII) and the Target Attachment Individual Identifier (TAII). When the stitch keyword is used with the vpls-id keyword, a single pair of stitched VCs is displayed.

Command Modes

User EXEC (>) Privileged EXEC (#)

Command History

Release

Modification

12.1(8a)E

This command was introduced.

12.0(21)ST

This command was integrated into Cisco IOS Release 12.0(21)ST.

12.0(22)S

This command was integrated into Cisco IOS Release 12.0(22)S and implemented on the Cisco 10720 router.

12.0(23)S

This command was modified. The interface and destination keywords were added.

12.2(14)SX

This command was integrated into Cisco IOS Release 12.2(14)SX and was implemented on the Supervisor Engine 720.

12.2(14)SZ

This command was integrated into Cisco IOS Release 12.2(14)SZ.

12.2(15)T

This command was integrated into Cisco IOS Release 12.2(15)T.

12.2(28)SB

This command was integrated into Cisco IOS Release 12.2(28)SB and was implemented on the Cisco 10000 series routers. The example output was changed for the Cisco 10000 series router, and two fields (SSO Descriptor and SSM segment/switch IDs) were removed from the output.

12.2(33)SRA

This command was integrated into Cisco IOS Release 12.2(33)SRA.

12.2(33)SRB

This command was modified. This command was updated to include forwarding equivalence class (FEC) 129 signaling information for pseudowires configured through VPLS Autodiscovery, and to support provisioning Any Transport over MPLS (AToM) static pseudowires.

12.2(33)SXH

This command was integrated into Cisco IOS Release 12.2(33)SXH.

12.2(33)SRC

This command was modified. This command was updated to display the number of MAC address withdrawal messages sent and received as part of the H-VPLS N-PE Redundancy for QinQ and MPLS Access feature.

This command was updated to display pseudowire status between peer routers that have been configured for the MPLS Pseudowire Status Signaling feature.

Cisco IOS XE Release 2.1

This command was implemented on the Cisco ASR 1000 Series Aggregation Services Routers.

Cisco IOS XE Release 2.3

This command was modified. This command output was updated to display the following information:

The status of pseudowires before, during, and after a switchover.

The status of a pseudowire switching point for multisegment pseudowires.

The number of packets and bytes being sent from the router. The VC statistics fields include the word “transit” to show that the packet totals no longer include packets being sent to the router.

12.2(33)SCC

This command was integrated into Cisco IOS Release 12.2(33)SCC.

12.2(33)SXI4

This command was modified. The command output was updated to display information about load balancing and the imposition and disposition of flow labels for the L2VPN Advanced VPLS feature.

15.0(1)S

This command was modified. The command output was updated to display information about Bidirectional Forwarding Detection (BFD).

15.1(1)S

This command was modified. Support for the L2VPN VPLS Inter-AS Option B feature was provided, and the pwid, stitch, and vpls-id keywords were added.

Interface on the local router that has been enabled to transport Layer 2 packets.

Local circuit

Type and number (if applicable) of the local circuit. The output shown in this column varies, depending on the transport type:

For Frame Relay, the output shows the DLCI of the PVC.

For ATM cell relay and AAL5, the output shows the VPI or VCI of the PVC.

For Ethernet VLANs, the output shows the VLAN number.

For PPP and High-Level Data Link Control (HDLC), the output shows the interface number.

Dest address

IP address of the remote router’s interface that is the other end of the VC.

VC ID

Virtual circuit identifier assigned to one of the interfaces on the router.

Status

Status of the VC, which can be one of the following:

Admin down—The VC was disabled by a user.

Down--The VC is not ready to carry traffic between the two VC endpoints. Use the detail keyword to determine the reason that the VC is down.

Hotstandby—The active pseudowire on a standby Route Processor (RP).

Recovering—The VC is recovering from a stateful switchover.

Standby—The VC is designated as the backup circuit in a stateful switchover configuration.

Up—The VC can carry traffic between the two VC endpoints. A VC is up when both imposition and disposition interfaces are programmed.

The disposition interface is programmed if the VC has been configured and the client interface is up.

The imposition interface is programmed if the disposition interface is programmed and you have a remote VC label and an Interior Gateway Protocol (IGP) label. The IGP label can be implicit null in a back-to-back configuration. An IGP label means there is a label switched path (LSP) to the peer.

The following sample output shows information about the nonstop forwarding (NSF), stateful switchover (SSO), and graceful restart capabilities on the AToM VC. The SSO portion indicates whether checkpoint data has been sent (on active) or received (on standby). When SSO data has not been successfully sent or has been released, the SSO information is not displayed.

The table above and the tables below describe the fields shown in the display.

The following sample output shows the information that is displayed when an AToM static pseudowire has been provisioned and the show mpls l2transport vc detail command is used to check the configuration. The Signaling protocol field specifies Manual because a directed control protocol such as Label Distribution Protocol (LDP) cannot be used to exchange parameters on static pseudowires. The remote interface description field seen for nonstatic pseudowire configurations is not displayed because remote information is exchanged using signaling between the Provider Edge (PE) routers and this is not done on static pseudowires.

The table above and the tables below describe the fields shown in the display.

The following sample output shows VC statistics, including the number of packets and bytes being sent from the router. The VC statistics fields include the word “transit” to indicate that the packet totals no longer include packets being sent to the router.

The table below describes the significant fields shown in the display.

Table 57 show mpls l2transport vc detail Field Descriptions

Field

Description

Local interface

Interface on the local router that has been enabled to send and receive Layer 2 packets. The interface varies, depending on the transport type. The output also shows the status of the interface.

line protocol

Status of the line protocol on the edge-facing interface.

Destination address

IP address of the remote router specified for this VC. Specify the destination IP address as part of the mpls l2transport route command.

VC ID

Virtual circuit identifier assigned to the interface on the router.

VC status

Status of the VC, which can be one of the following:

Admin down—The VC was disabled by a user.

Down—The VC is not ready to carry traffic between the two VC endpoints.

up—The VC is in a state where it can carry traffic between the two VC endpoints. A VC is up when both imposition and disposition interfaces are enabled.

The disposition interface is enabled if the VC has been configured and the client interface is up.

The imposition interface is enabled if the disposition interface is enabled and a remote VC label and an IGP label exist. The IGP label can be an implicit null in a back-to-back configuration. (An IGP label means there is an LSP to the peer.)

Output interface

Interface on the remote router that has been enabled to transmit and receive Layer 2 packets.

imposed label stack

Summary of the Multiprotocol Label Switching (MPLS) label stack used to direct the VC to the PE router.

Preferred path

Path that was assigned to the VC and the status of that path. The path can be an MPLS traffic engineering tunnel or an IP address or hostname of a peer PE router.

Default path

Status of the default path, which can be disabled or active.

By default, if the preferred path fails, the router uses the default path. However, you can disable the router from using the default path when the preferred path fails by specifying the disable-fallback keyword with the preferred-path command.

Tunnel label

IGP label used to route the packet over the MPLS backbone to the destination router. The first part of the output displays the type of label. The second part of the output displays the route information.

The tunnel label information can display any of the following states:

imp-null: Implicit null means that the provider (P) router is absent and the tunnel label will not be used. Alternatively, imp-null can signify traffic engineering tunnels between the PE routers.

not ready, LFIB entry present: The tunnel label exists in the Label Forwarding Information Base (LFIB), but the VC is down.

not ready, no route: An IP route for the peer does not exist in the routing table.

not ready, not a host table: The route in the routing table for the remote peer router is not a host route.

unassigned: The label has not been assigned.

Create time

Time (in hours, minutes, and seconds) when the VC was provisioned.

last status change time

Last time (in hours, minutes, and seconds) the VC state changed.

Signaling protocol

Type of protocol used to send the MPLS labels on dynamically configured connections. The output also shows the status of the peer router. For AToM statically configured pseudowires, the field indicates Manual because there is no exchange of labels using a directed control protocol, such as LDP.

MPLS VC labels

Local VC label is a disposition label, which determines the egress interface of an arriving packet from the MPLS backbone. The remote VC label is a disposition VC label of the remote peer router.

Group ID

Local group ID used to group VCs locally. The remote group ID is used by the peer to group several VCs.

MTU

Maximum transmission unit specified for local and remote interfaces.

Remote interface description

Interface on the remote router that has been enabled to transmit and receive Layer 2 packets.

Sequencing

Indicates whether sequencing of out-of-order packets is enabled or disabled.

SSO Descriptor

Identifies the VC for which the information was checkpointed.

local label

Value of the local label that was checkpointed (that is, sent on the active RP and received on the standby RP).

SSM segment/switch IDs

IDs used for the control plane and data plane for this VC. This data is not for customer use but for Cisco personnel for troubleshooting purposes. When the Source Specific Multicast (SSM) IDs are followed by the word “used,” the checkpointed data has been successfully sent.

PWID

Pseudowire ID used in the data plane to correlate the switching context for the segment associated with the MPLS switching context. This data is not for customer use but for Cisco personnel for troubleshooting purposes.

packet totals

Number of packets sent and received. Received packets are those AToM packets received from the MPLS core. Sent packets are those AToM packets sent to the MPLS core. This number excludes dropped packets.

Note

If the VC statistics fields include the word “transit,” the output shows the number of packets and bytes being sent from the router.

byte totals

Number of bytes sent and received from the core-facing interface, including the payload, control word if present, and AToM VC label.

Note

If the VC statistics fields include the word “transit,” the output shows the number of packets and bytes being sent from the router.

packet drops

Number of dropped packets.

Note

If the VC statistics fields include the word “transit,” the output shows the number of packets and bytes being sent from the router.

The following is sample output from the show mpls l2transport vc detail command when the VPLS Autodiscovery feature has been configured on VPLS pseudowires. The output that is specific to VPLS Autodiscovery is shown in bold.

For the local router, the output indicates whether the MPLS Pseudowire Signaling Status feature is enabled or disabled. For the remote router, the output indicates whether the MPLS Pseudowire Signaling Status feature is supported.

Label/status state machine

The first value in the output indicates whether label advertisement has been established or not. The second value (LruRru) indicates the status of the local and remote routers. The following list translates the status codes:

D—Dataplane

L—local router

r or n—ready (r) or not ready (n)

R—remote router

S—Local shutdown

u or d—up (u) or down (d) status

Last local dataplane status rcvd

Last status message received about the dataplane on the local router.

Last local SSS circuit status rcvd

Last status message received about the subscriber service switch (SSS) on the local router.

Last local SSS circuit status sent

Last status message sent about the subscriber service switch on the local router.

Last local LDP TLV status sent

Last status message sent about the type, length, values (TLV) on the local router.

Last remote LDP TLV status rcvd

Last status message received about the TLV on the local router.

The following sample output from the show mpls l2transport vc detail command displays the status of multisegment pseudowires:

If the control word is negotiated by the peer and is different from the configured value, the configured value is shown in parentheses.

If the control word is configured to be disabled, the displayed value is as follows:

Control Word: off (configured: disabled)

If the control word is configured to be enabled but negotiated by the peer to be off, the displayed value is as follows:

Control Word: off (configured: enabled)

If the control word is not configured, the displayed value is as follows:

Control Word: on (configured: autosense)

The following sample output from the show mpls l2transport vc detail command displays load balancing information and shows whether flow labels are added to the MPLS label as part of the L2VPN Advanced VPLS feature:

The table below describes the significant fields shown in the display.

Table 62 show mpls l2transport vc detail Field Descriptions for the BFD CC over VCCV - Support for ATM Pseudowire Feature

Field

Description

VCCV BFD protection active

Displays the VCCV BFD protection status.

BFD Template

Displays the BFD template name.

CC Type

Displays the CC type.

Type 1: control word.

Type 2: MPLS router alert label.

Type 3: MPLS pseudowire label with TTL.

CV Type

Displays the Control Verification type.

The following is sample output from the show mpls l2transport vc command when the L2VPN VPLS Inter-AS Option B feature has been configured. The fields in the display are self-explanatory or described in other tables in this document.

The following is sample output from the show mpls l2transport vc detail command when the L2VPN VPLS Inter-AS Option B feature has been configured. The output that is specific to the L2VPN VPLS Inter-AS Option B feature is shown in bold.

The following is sample output from the show mpls l2transport vc detail command when there is a remote AC failure and when VCCV BFD status signaling is enabled, that is, vccv bfd status signaling is configured.

Last status message received about the BFD dataplane on the local router.

Last local dataplane status rcvd

Last status message received about the dataplane on the local router.

Last local SSS circuit status rcvd

Last status message received about the subscriber service switch (SSS) on the local router.

Last local SSS circuit status sent

Last status message sent about the subscriber service switch on the local router.

Last remote LDP ADJ

Last status message received about the ADJ on the local router.

VCCV BFD protection active

Displays the VCCV BFD protection status.

BFD Template

Displays the BFD template name.

CC Type

Displays the CC type.

Type 1: control word.

Type 2: MPLS router alert label.

Type 3: MPLS pseudowire label with TTL.

CV Type

Displays the Control Verification type.

Examples

The following is sample output from the show mpls l2transport vc command when the L2VPN Pseudowire Redundancy feature has been configured. The fields in the display are self-explantory or described in other tables in this document:

show mpls label range

To display the range of local labels available for use on packet interfaces, use the show show mpls label range command in privileged EXEC mode.

showmplslabelrange

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(9)ST

This command was introduced.

12.2(33)SRA

This command was integrated into Cisco IOS Release 12.2(33)SRA.

12.2(33)SXH

This command was integrated into Cisco IOS Release 12.2(33)SXH.

12.2(33)SB

This command was integrated into Cisco IOS Release 12.2(33)SB.

XE Release 2.2

This command was integrated into Cisco IOS XE Release 2.2. The “Usage Guidelines” and the sample command output changed.

Usage Guidelines

You can use the mpls label range command to configure a range for local labels that is different from the default range. The show mpls label range command displays both the label range currently in use and the label range that will be in use following the next router reload.

Examples

In the following example, the use of the show mpls label range command is shown before and after the mpls label range command is used to configure a label range that does not overlap the starting label range:

Related Commands

Command

Description

mpls label range

Configures a range of values for use as local labels.

show mpls ldp backoff

To display information about the configured session setup backoff parameters and any potential Label Distribution Protocol (LDP) peers with which session setup attempts are being throttled, use the show mpls ldp backoff command in user EXEC or privileged EXEC mode.

The table below describes the significant fields shown in the display.

Table 65 show mpls ldp backoff Field Descriptions

Field

Description

LDP initial/maximum backoff

Indicates the configured backoff parameters (initial and maximum) in seconds.

Backoff table

Contains a list of discovered LDP neighbors for which session setup is being delayed because of previous failures to establish a session due to incompatible configuration. The backoff table incorporates the following information:

LDP Id--Identifies the LDP neighbors.

Backoff(sec)--Shows the amount of time that session setup is being delayed.

Waiting(sec)--Shows the approximate amount of time that session setup has been delayed.

The following is sample output from the show mpls ldp backoff vrfvrf-name command that shows one entry in the Backoff table for VRF vrf1:

(Optional) Selects any prefix that matches the value in the mask argument with a length from 1 to 32 characters.

local-labellabel-label

(Optional) Display entries matching local label values. Use the label-label arguments and keyword to indicate the label range. The hyphen (-) keyword is required for a label range.

remote-labellabel-label

(Optional) Displays entries matching the label values assigned by a neighbor router. Use the label-label arguments and keyword to indicate the label range. The hyphen (-) keyword is required for a label range.

neighboraddress

(Optional) Displays the label bindings assigned by the selected neighbor.

local

(Optional) Displays the local label bindings.

detail

(Optional) Displays the checkpoint status of the local label bindings.

Command Default

If no optional keywords or arguments are entered, the command displays the LIB for the default routing domain only.

Usage Guidelines

TDP is not supported for LDP features in Cisco IOS 12.0(30)S and later releases, 12.2(28)SB and later 12.2S releases, and 12.3(14)T and later releases.

A request can specify that the entire database be displayed, or that the display be limited to a subset of entries according to the following:

Prefix

Input or output label values or ranges

Neighbor advertising the label

Note

The show mpls ip bindings command includes the output generated by the show mpls ldp bindings command. On the Cisco 7000 series router, this command displays information about label bindings for LC-ATM interfaces.

Examples

The following is sample output from the show mpls ldp bindings command. This form of the command displays the contents of the LIB for the default routing domain.

The following is sample output from the show mpls ldp bindingsnetwork lengthlonger-prefixes neighboraddress variant of the command; it displays labels learned from label switch router (LSR) 10.144.0.44 for network 10.166.0.0 and any of its subnets. The use of the neighbor keyword suppresses the output of local labels and labels learned from other neighbors.

The table below describes the significant fields shown in the displays.

Table 66 show mpls ldp bindings Field Descriptions

Field

Description

10.3.3.0/16 10.1.1.1/32

IP prefix and mask for a particular destination (network/mask).

rev 9

Revision number that is used internally to manage label distribution for this destination.

Advertised to

The LSRs that received the label binding.

local binding

Labels assigned by the local LSR.

remote binding

List of outgoing labels for this destination learned from other LSRs. Each item in this list identifies the LSR from which the outgoing label was learned and the label itself. The LSR is identified by its LDP identifier.

stale

After an LDP session is lost and the routers begin a graceful restart, the remote label bindings are marked stale.

This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

12.0(33)S

This command was integrated into Cisco IOS Release 12.0(33)S and LDP MD5 password rollover information displays in the command output when the detail keyword is used with the show mpls ldp discovery command.

Cisco IOS XE Release 2.5

This command was integrated into Cisco IOS XE Release 2.5.

Cisco IOS XE Release 3.6S

This command was implemented on the Cisco ASR 903 series routers.

Usage Guidelines

This command displays neighbor discovery information for LDP or Tag Distribution Protocol (TDP). It generates a list of interfaces over which the LDP discovery process is running.

Examples

The following is sample output from the show mpls ldp discovery command:

The following is sample output from the show mpls ldp discovery all command, which shows the interfaces engaged in LDP discovery activity for all the VPN routing and forwarding instances, including those in the default routing domain. In this example, note that the same neighbor LDP ID (10.14.14.14) appears in all the listed VRF interfaces, highlighting the fact that the same IP address can coexist in different VPN routing and forwarding instances.

Period of time (in milliseconds) between the sending of consecutive hello messages.

Transport IP addr

Specifies that the interface address should be advertised as the transport address in the LDP discovery hello messages.

LDP Id

LDP ID of the peer router.

Src IP addr

Source IP address of the local router.

Transport IP addr

Specifies that the named IP address should be advertised as the transport address in the LDP discovery hello messages sent on an interface.

Hold time

Period of time (in seconds) a discovered LDP neighbor is remembered without receipt of an LDP hello message from the neighbor.

Proposed local/peer

Hold times (in seconds) proposed for LDP hello timer by the local router and the peer router. LDP uses the lower of these two values as the hold time.

The following is sample output from the show mpls ldp discovery detail command, which displays information related to LDP MD5 passwords. Information related to MD5 passwords is pointed out in bold text in the output.

Password source in the current configuration. The source is described by one of the following:

neighbor--The password for the neighbor is retrieved from thempls ldp neighbor [vrfvrf-name] ip-addresspassword [0 | 7] password command. The ip-address argument is the router ID of the neighbor.

num--The password for the neighbor is retrieved from mpls ldp [vrfvrf-name] password optionnumberforacl [0 | 7] password command. The number argument is a number from 1 to 32767. The acl argument is the name or number of an IP standard access list that permits the neighbor router ID.

The following is sample output from the show mpls ldp neighbor all command, which displays the LDP neighbor information for all VPN routing and forwarding instances, including those in the default routing domain. In this example, note that the same neighbor LDP ID (10.14.14.14) appears in all the listed VRF interfaces, highlighting the fact that the same IP address can coexist in different VPN routing and forwarding instances.

The table below describes the significant fields shown in the displays.

Table 73 show mpls ldp neighbor Field Descriptions

Field

Description

Peer LDP Ident

LDP (or TDP) identifier of the neighbor (peer) for this session.

Local LDP Ident

LDP (or TDP) identifier for the local label switch router (LSR) for this session.

TCP connection

TCP connection used to support the LDP session, shown in the following format:

peer IP address.peer port

local IP address.local port

Password

Indicates if password protection is being used. Password status is as follows:

Required or not required—Indicates whether password configuration is required.

Neighbor, none, option #, or fallback—Indicates the password source when the password was configured.

In use (current) or stale (previous)—Indicates the current LDP session password usage status.

State

State of the LDP session. Generally, this is Oper (operational), but transient is another possible state.

Msgs sent/rcvd

Number of LDP messages sent to and received from the session peer. The count includes the transmission and receipt of periodic keepalive messages, which are required for maintenance of the LDP session.

Downstream on demand

Indicates that the Downstream on Demand method of label distribution is being used for this LDP session. When the Downstream on Demand method is used, an LSR advertises its locally assigned (incoming) labels to its LDP peer only when the peer requests them.

Downstream

Indicates that the downstream method of label distribution is being used for this LDP session. When the downstream method is used, an LSR advertises all of its locally assigned (incoming) labels to its LDP peer (subject to any configured access list restrictions).

Up time

Length of time (in hours, minutes, seconds) the LDP session has existed.

Graceful Restart enabled

Indicates whether the LDP session has Graceful Restart enabled.

Peer reconnect time

The length of time, in milliseconds (ms), the peer device waits for a device to reconnect.

LDP discovery sources

Sources of LDP discovery activity that led to the establishment of this LDP session.

Targeted Hello

Lists the platforms to which targeted hello messages are being sent:

The active field indicates that this LSR has initiated targeted hello messages.

The passive field indicates that the neighbor LSR has initiated targeted hello messages and that this LSR is configured to respond to the targeted hello messages from the neighbor.

holdtime

Period of time, in milliseconds (ms), a discovered LDP neighbor is remembered without receipt of an LDP hello message from the neighbor.

hello interval

Period of time, in milliseconds (ms), between the sending of consecutive hello messages.

Addresses bound to peer LDP Ident

Known interface addresses of the LDP session peer. These are addresses that might appear as “next hop” addresses in the local routing table. They are used to maintain the Label Forwarding Information Base (LFIB).

Duplicate Addresses advertised by peer

IP addresses that are bound to another peer. They indicate an error because a given address should be bound to only one peer.

Peer holdtime

The time, in milliseconds (ms), that the neighbor session is retained without the receipt of an LDP message from the neighbor.

KA Interval

Keepalive interval. The amount of time, in milliseconds (ms), that a device lets pass without sending an LDP message to its neighbor. If this time elapses and the device has nothing to send, it sends a keepalive message.

Peer state

State of the peer; estab means established.

NSR: Ready/Not ready

Nonstop routing (NSR) state for each neighbor.

LDP inbound filtering accept acl:1

Access list that is permitted for inbound label-binding filtering.

Related Commands

Command

Description

mpls ldp neighbor password

Configures a password key for computing MD5 checksums for the session TCP connection with the specified neighbor.

mpls ldp neighbor password fallback

Configures an MD5 password for LDP sessions with peers.

mpls ldp neighbor password option

Configures an MD5 password for LDP sessions with neighbors whose LDP device IDs are permitted by a specified access list.

mpls ldp neighbor password required

Specifies that LDP must use a password when establishing a session between LDP peers.

mpls ldp neighbor password rollover duration

Configures the duration before the new password takes effect on an MPLS LSR.

mpls ldp nsr

Enables or disables NSR for LDP.

show mpls interfaces

Displays information about one or more interfaces that have been configured for label switching.

show mpls ldp discovery

Displays the status of the LDP discovery process.

show mpls ldp neighbor password

Displays password information used in established LDP sessions.

show mpls ldp neighbor password

To display password information used in established Label Distribution Protocol (LDP) sessions, use the show mpls ldp neighbor password command in user EXEC mode or privileged EXEC mode.

(Optional) Identifies the LDP neighbors accessible over this interface.

pending

(Optional) Displays LDP sessions whose password is different from that in the current configuration.

current

(Optional) Displays LDP sessions whose password is the same as that in the current configuration.

all

(Optional) When the all keyword is specified alone in this command, the command displays LDP password information for all neighbors in all VPNs, including those in the global routing table.

Command Default

If you do not specify an optional keyword for this command, password information for all established LDP sessions is displayed.

Command Modes

User EXEC Privileged EXEC

Command History

Release

Modification

12.2(28)SB

This command was introduced.

12.0(32)SY

This command was integrated into Cisco IOS Release 12.0(32)SY.

12.2(33)SRB

This command was integrated into Cisco IOS Release 12.2(33)SRB.

12.0(33)S

This command was integrated into Cisco IOS Release 12.0(33)S.

12.4(20)T

This command was integrated into Cisco IOS Release 12.4(20)T.

Usage Guidelines

Use this command to display password information for established LDP sessions. If you do not specify an option, password information for all established LDP sessions is displayed. To display LDP sessions whose password is the same as that in the current configuration, use the current keyword with the command. To display LDP sessions whose password is different from that in the current configuration, use the pending keyword with the command.

Examples

The following is sample output from the show mpls ldp neighbor password command, which displays information for all established LDP sessions:

The following is sample output from the show mpls ldp neighbor password pending command, which displays information for LDP sessions whose passwords are different from those in the current configuration:

The table below describes the significant fields shown in the display.

Table 76 show mpls ldp nsr pending neighbor Field Descriptions

Field

Description

Pending Label-Request responses: Prefix, msg_id, label

Prefix, message ID, and label encoded in the label request message.

Pending Label-Withdraw responses: Prefix, Label

Prefix and label encoded in the label withdraw message.

Pending Local Address Withdraw Acks: Address:

Address encoded in the local address withdraw message.

The LDP messages (label request, label withdraw, and local address withdraw) must be maintained in a database waiting for a TCP-level ACK. If a switchover occurs prior to the acknowledgements/responses being received, the newly active Route Processor (RP) must retransmit these messages. When the acknowledgement/response is received, the message is removed from the pending database.

The following is sample output from the show mpls ldp nsr statistics neighbor 10.1.1.1 command:

Device# show mpls ldp nsr statistics neighbor 10.1.1.1
!!!output on active RP
Peer: 10.1.1.1:0
In label Request Records created: 0, freed: 0
In label Withdraw Records created: 0, freed: 0
Local Address Withdraw Records created: 3, freed: 3
Transmit contexts enqueued: 3, dequeued: 3
Peer: 10.2.2.2:0
In label Request Records created: 0, freed: 0
In label Withdraw Records created: 6, freed: 6
Local Address Withdraw Records created: 3, freed: 3
Transmit contexts enqueued: 9, dequeued: 9
Total In label Request Records created: 0, freed: 0
Total In label Withdraw Records created: 6, freed: 6
Total Local Address Withdraw Records created: 3, freed: 3
Label Request Acks:
Number of chkpt msg sent: 0
Number of chkpt msg in queue: 0
Number of chkpt msg in state none: 0
Number of chkpt msg in state send: 0
Number of chkpt msg in state wait: 0
Label Withdraw Acks:
Number of chkpt msg sent: 6
Number of chkpt msg in queue: 0
Number of chkpt msg in state none: 0
Number of chkpt msg in state send: 0
Number of chkpt msg in state wait: 0
Address Withdraw Acks:
Number of chkpt msg sent: 3
Number of chkpt msg in queue: 0
Number of chkpt msg in state none: 0
Number of chkpt msg in state send: 0
Number of chkpt msg in state wait: 0
Session Sync:
Number of session-sync msg sent: 1
Number of address records created: 1
Number of address records freed: 1
Number of dup-address records created: 1
Number of dup-address records freed: 1
Number of remote binding records created: 1
Number of remote binding records freed: 1
Number of capability records created: 1
Number of capability records freed: 1
Number of addr msg in state none: 0
Number of dup-addr msg in state none: 0
Number of remote binding msg in state none: 0
Number of capability msg in state none: 0
Number of addr msg in state send: 0
Number of dup-addr msg in state send: 0
Number of remote binding msg in state send: 0
Number of capability msg in state send: 0
Number of addr msg in state wait: 0
Number of dup-addr msg in state wait: 0
Number of remote binding msg in state wait: 0
Number of capability msg in state wait: 0
Number of sync-done msg sent: 1
!!!output on standby RP
Peer: 10.1.1.1:0
In label Request Records created: 0, freed: 0
In label Withdraw Records created: 0, freed: 0
Local Address Withdraw Records created: 2, freed: 1
Transmit contexts enqueued: 0, dequeued: 0
Peer: 10.2.2.2:0
In label Request Records created: 0, freed: 0
In label Withdraw Records created: 6, freed: 6
Local Address Withdraw Records created: 2, freed: 1
Transmit contexts enqueued: 0, dequeued: 0
Total In label Request Records created: 0, freed: 0
Total In label Withdraw Records created: 6, freed: 6
Total Local Address Withdraw Records created: 2, freed: 1
Number of Label Request Acks rcvd: 0
Number of Label Withdraw Acks rcvd: 6
Number of Address Withdraw Acks rcvd: 3

The table below describes the significant fields shown in the display.

Table 77 show mpls ldp nsr statistics neighbor Field Descriptions

Field

Description

In label Request Records created: freed:

Number of label request messages received. The created counter is incremented when the record is created. The freed counter is incremented when the ACK is received, and the record is destroyed.

In label Withdraw Records created: freed:

Number of label withdraw messages received. The created counter is incremented when the record is created. The freed counter is incremented when the ACK is received, and the record is destroyed.

Local Address Withdraw Records created: freed:

Number of local address withdraw messages sent. The created counter is incremented when the record is created. The freed counter is incremented when the ACK is received, and the record is destroyed.

Transmit contexts enqueued: dequeued:

Records that are created when the messages in the pending list that need TCP ACK (because they do not have protocol acknowledgements) are sent to the peer. These context records store information about the pending records and the TCP sequence number used to send the message to the peer. The transmit context records are de-queued when a TCP ACKfor the sequence number is received and are used to free the records from the pending lists.

Related Commands

Command

Description

clear mpls ldp nsr statistics

Clears NSR statistics and counters for LDP sessions.

mpls ldp nsr

Enables or disables NSR for LDP sessions.

show mpls ldp parameters

To display current Label Distribution Protocol (LDP) parameters, use the show mpls ldp parameters command in user EXEC or privileged EXEC mode.