show ip traffic-engineering routes through show mpls memory
Available Languages
Table Of Contents
show ip traffic-engineering routes
show isis mpls traffic-eng adjacency-log
show isis mpls traffic-eng advertisements
show isis mpls traffic-eng downstream-tree
show isis mpls traffic-eng tunnel
show mpls l2transport checkpoint
show mpls l2transport hw-capability
show mpls l2transport static-oam
show mpls ldp graceful-restart
show mpls ldp neighbor password
show ip traffic-engineering routes
To display information about the requested filters configured for traffic engineering, use the show ip traffic-engineering routes command in privileged EXEC mode.
show ip traffic-engineering routes [filter-number] [detail]
Syntax Description
filter-number
(Optional) A decimal value representing the number of the filter to display.
detail
(Optional) Display of command output in long form.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Requests can be limited to a specific filter.
Examples
The following is sample output from the show ip traffic-engineering routes command:
Router# show ip traffic-engineering routesInstalled traffic engineering routes:Codes: T - traffic engineered routeT 43.0.0.1/32 (not override of routing table entry)is directly connected, 00:06:35, Tunnel7T 44.0.0.0/8 (override of routing table entry)is directly connected, 01:12:39, Tunnel5Table 63 describes the significant fields shown in the display.
Related Commands
show ip traffic-engineering configuration
Displays information about configured traffic engineering filters and routes.
show ip vrf
To display the set of defined Virtual Private Network (VPN) routing and forwarding (VRF) instances and associated interfaces, use the show ip vrf command in privileged EXEC mode.
show ip vrf [brief | detail | interfaces | id] [vrf-name] [output-modifiers]
Syntax Description
Defaults
When no keywords or arguments are specified, the command shows concise information about all configured VRFs.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to display information about VRFs. Two levels of detail are available:
•
The brief keyword (or no keyword) displays concise information.
•
To display information about all interfaces bound to a particular VRF, or to any VRF, use the interfaces keyword. To display information about VPN IDs assigned to a PE router, use the id keyword.
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.
Router# show ip vrfName Default RD InterfaceD 2:0 Loopback2Virtual-Access3 [D]Virtual-Access4 [D]U 2:1 Virtual-Access3Virtual-Access4Table 64 describes the significant fields shown in the display.
Table 64 show ip vrf Field Descriptions
Name
Specifies the VRF name.
Default RD
Specifies the default route distinguisher.
Interface
Specifies the network interface.
The following example displays detailed information about all of the VRFs configured on the router, including all of the VAIs associated with each VRF:
Router# show ip vrf detailVRF D; default RD 2:0; default VPNID <not set>Interfaces:Loopback2 Virtual-Access3 [D] Virtual-Access4 [D]Connected addresses are not in global routing tableExport VPN route-target communitiesRT:2:0Import VPN route-target communitiesRT:2:1No import route-mapNo export route-mapVRF U; default RD 2:1; default VPNID <not set>Interfaces:Virtual-Access3 Virtual-Access4Connected addresses are not in global routing tableNo Export VPN route-target communitiesImport VPN route-target communitiesRT:2:1No import route-mapNo export route-mapTable 65 describes the significant fields shown in the display.
The following example shows the interfaces bound to a particular VRF:
Router# show ip vrf interfacesInterface IP-Address VRF ProtocolEthernet2 10.22.0.33 vrf1 upEthernet4 10.77.0.33 hub upRouter#Table 66 describes the significant fields shown in the display.
The following is sample output that shows all the VPN IDs that are configured in the router and their associated VRF names and VRF route distinguishers (RDs):
Router# show ip vrf idVPN Id Name RD2:3 vpn2 <not set>A1:3F6C vpn1 100:1Table 67 describes the significant fields shown in the display.
Table 67 show ip vrf id Field Descriptions
VPN Id
Specifies the VPN ID assigned to the VRF.
Name
Specifies the VRF name.
RD
Specifies the route distinguisher.
Related Commands
show isis database verbose
To display additional information about the Intermediate System-to-Intermediate System (IS-IS) database, use the show isis database verbose command in user EXEC or privileged EXEC mode.
show isis database verbose
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC
Privileged EXECCommand History
Examples
The following is sample output from the show isis database verbose command:
Router# show isis database verboseIS-IS Level-1 Link State DatabaseLSPID LSP Seq Num LSP Checksum LSP Holdtime ATT/P/OLdtp-5.00-00 * 0x000000E6 0xC9BB 1042 0/0/0Area Address:49.0001NLPID: 0xCCHostname:dtp-5Router ID: 10.5.5.5IP Address: 172.16.39.5Metric:10 IP 172.16.39.0/24dtp-5.00-01 * 0x000000E7 0xAB36 1065 0/0/0Metric:10 IS-Extended dtp-5.01Affinity:0x00000000Interface IP Address:172.21.39.5Physical BW:10000000 bits/secReservable BW:1166000 bits/secBW Unreserved[0]: 1166000 bits/sec, BW Unreserved[1]: 1166000 bits/secBW Unreserved[2]: 1166000 bits/sec, BW Unreserved[3]: 1166000 bits/secBW Unreserved[4]: 1166000 bits/sec, BW Unreserved[5]: 1166000 bits/secBW Unreserved[6]: 1166000 bits/sec, BW Unreserved[7]: 1153000 bits/secMetric:0 ES dtp-5Table 68 describes the significant fields shown in the display.
The following example includes a route tag:
Router# show isis database verboseIS-IS Level-1 Link State Database:LSPID LSP Seq Num LSP Checksum LSP Holdtime ATT/P/OLdasher.00-00 0x000000F8 0xE57B 518 1/0/0Area Address: 49.0002NSPID: 0xCCHostname: dasherIP Address: 10.3.0.1Metric: 10 IP 172.16.170.0/24Metric: 10 IP 10.0.3.0/24Metric: 10 IP 10.0.3.3/30Metric: 10 IS-Extended dasher.02172.19.170.0/24Metric: 20 IP-Interarea 10.1.1.1/32Route Admin Tag: 60Metric: 20 IP-Interarea 192.168.0.6/32Route Admin Tag: 50Related Commands
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.
show isis [process-tag] mpls ldp [interface interface]
Syntax Description
Command Modes
Privileged EXEC
Command History
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.
Router# show isis mpls ldpInterface: POS0/2; ISIS tag null enabledISIS is UP on interfaceAUTOCONFIG Information :LDP enabled: YESSYNC Information :Required: YESAchieved: YESIGP Delay: NOHolddown time: InfiniteState: SYNC achievedThis command returns information for interfaces that are configured for IS-IS, which are indicated by the message "ISIS is UP" on the interface.
Table 69 describes the significant fields shown in the display.
Related Commands
show isis mpls traffic-eng adjacency-log
To display a log of 20 entries of Multiprotocol Label Switching (MPLS) traffic engineering Intermediate System-to-Intermediate System (IS-IS) adjacency changes, use the show isis mpls traffic-eng adjacency-log command in user EXEC or privileged EXEC mode.
show isis mpls traffic-eng adjacency-log
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC
Privileged EXECCommand History
Examples
The following is sample output from the show isis mpls traffic-eng adjacency-log command:
Router# show isis mpls traffic-eng adjacency-logIS-IS RRR logWhen Neighbor ID IP Address Interface Status Level04:52:52 0000.0024.0004.02 0.0.0.0 Et0/2 Up level-104:52:50 0000.0026.0001.00 172.16.1.2 PO1/0/0 Up level-104:52:37 0000.0024.0004.02 10.0.0.0 Et0/2 Up level-1Table 70 describes the significant fields shown in the display.
Related Commands
show isis mpls traffic-eng advertisements
Displays the last flooded record from MPLS traffic engineering.
show isis mpls traffic-eng advertisements
To display the last flooded record from Multiprotocol Label Switching (MPLS) traffic engineering, use the show isis mpls traffic-eng advertisements command in user EXEC or privileged EXEC mode.
show isis mpls traffic-eng advertisements
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC
Privileged EXECCommand History
Examples
The following is sample output from the show isis mpls traffic-eng advertisements command:
Router# show isis mpls traffic-eng advertisementsSystem ID:dtp-5.00Router ID:10.5.5.5Link Count:1Link[1]Neighbor System ID:dtp-5.01 (broadcast link)Interface IP address:172.21.39.5Neighbor IP Address:0.0.0.0Admin. Weight:10Physical BW:10000000 bits/secReservable BW:1166000 bits/secBW unreserved[0]:1166000 bits/sec, BW unreserved[1]:1166000 bits/secBW unreserved[2]:1166000 bits/sec, BW unreserved[3]:1166000 bits/secBW unreserved[4]:1166000 bits/sec, BW unreserved[5]:1166000 bits/secBW unreserved[6]:1166000 bits/sec, BW unreserved[7]:1153000 bits/secAffinity Bits:0x00000000Table 71 describes the significant fields shown in the display.
Related Commands
show isis mpls traffic-eng adjacency-log
Displays a log of 20 entries of MPLS traffic engineering IS-IS adjacency changes.
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.
show isis mpls traffic-eng downstream-tree system-id [level-1 | level-2]
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
Examples
The following is sample output from the show isis mpls traffic-eng downstream-tree command. The fields are self-explanatory.
Router# show isis mpls traffic-eng downstream-tree cr2.amsterdam1System cr2.amsterdam1.00 with metric 5MPLS TE-tunnel Children List15 ar5.hilversum1.0015 ar5.zwolle1.0015 ar5.tilburg1.0015 ar5.wageningen.0015 ar5.groningen1.0015 ar5.enschede1.0015 ar5.nijmegen1.0015 cr1.amsterdam1.001 cr1.amsterdam1.0025 ar5.denhaag1.0025 ar5.delft1.0025 ar5.leiden1.0025 ar5.rotterdam1.0025 ar5.amsterdam1.0025 ar5.eindhoven1.0025 ar5.maastricht.00Related Commands
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.
show isis mpls traffic-eng tunnel
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the show isis mpls traffic-eng tunnel command:
Router# show isis mpls traffic-eng tunnelStation Id Tunnel Name Bandwidth Nexthop Metric Modekangpa-router1.00 Tunnel1022 3333 10.2.2.2 -3 RelativeTunnel1021 10000 10.2.2.2 11 Absolutetomklong-route.00 Tunnel1031 10000 172.17.3.3 -1 RelativeTunnel1032 10000 172.17.3.3Table 72 describes the significant fields shown in the display.
Related Commands
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 show issu clients command in user EXEC or privileged EXEC mode.
show issu clients
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC
Privileged EXECCommand History
This command was introduced.
12.2(33)SRB1
ISSU is supported on the Cisco 7600 series routers in Cisco IOS Release 12.2(33)SRB.
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 issu runversion 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:
Router# show issu clientsClient_ID = 2, Client_Name = ISSU Proto client, Entity_Count = 1Client_ID = 3, Client_Name = ISSU RF, Entity_Count = 1Client_ID = 4, Client_Name = ISSU CF client, Entity_Count = 1Client_ID = 5, Client_Name = ISSU Network RF client, Entity_Count = 1Client_ID = 7, Client_Name = ISSU CONFIG SYNC, Entity_Count = 1Client_ID = 8, Client_Name = ISSU ifIndex sync, Entity_Count = 1Client_ID = 9, Client_Name = ISSU IPC client, Entity_Count = 1Client_ID = 10, Client_Name = ISSU IPC Server client, Entity_Count = 1Client_ID = 11, Client_Name = ISSU Red Mode Client, Entity_Count = 1Client_ID = 12, Client_Name = ISSU EHSA services client, Entity_Count = 1Client_ID = 100, Client_Name = ISSU rfs client, Entity_Count = 1Client_ID = 110, Client_Name = ISSU ifs client, Entity_Count = 1Client_ID = 1001, Client_Name = OC3POS-6, Entity_Count = 4Client_ID = 1002, Client_Name = C10K ATM, Entity_Count = 1Client_ID = 1003, Client_Name = C10K CHSTM1, Entity_Count = 1Client_ID = 1004, Client_Name = C10K CT3, Entity_Count = 1Client_ID = 1005, Client_Name = C10K GE, Entity_Count = 1Client_ID = 1006, Client_Name = C10K ET, Entity_Count = 1Client_ID = 1007, Client_Name = C10K CHE1T1, Entity_Count = 1Client_ID = 1009, Client_Name = C10K MFE, Entity_Count = 1Client_ID = 1010, Client_Name = C10K APS, Entity_Count = 1Client_ID = 1013, Client_Name = C10K CARD OIR, Entity_Count = 1Client_ID = 2002, Client_Name = CEF Push ISSU client, Entity_Count = 1Client_ID = 2003, Client_Name = ISSU XDR client, Entity_Count = 1Client_ID = 2004, Client_Name = ISSU SNMP client, Entity_Count = 1Client_ID = 2005, Client_Name = ISSU HDLC Client, Entity_Count = 1Client_ID = 2006, Client_Name = ISSU QoS client, Entity_Count = 1Client_ID = 2007, Client_Name = ISSU LSD Label Mgr HA Client, Entity_Count = 1Client_ID = 2008, Client_Name = ISSU Tableid Client, Entity_Count = 1Client_ID = 2009, Client_Name = ISSU MPLS VPN Client, Entity_Count = 1Client_ID = 2010, Client_Name = ARP HA, Entity_Count = 1Client_ID = 2011, Client_Name = ISSU LDP Client, Entity_Count = 1Client_ID = 2012, Client_Name = ISSU HSRP Client, Entity_Count = 1Client_ID = 2013, Client_Name = ISSU ATM Client, Entity_Count = 1Client_ID = 2014, Client_Name = ISSU FR Client, Entity_Count = 1Client_ID = 2015, Client_Name = ISSU REDSSOC client, Entity_Count = 1Client_ID = 2019, Client_Name = ISSU TCP client, Entity_Count = 1Client_ID = 2020, Client_Name = ISSU BGP client, Entity_Count = 1Client_ID = 2021, Client_Name = XDR Int Priority ISSU client, Entity_Count = 1Client_ID = 2022, Client_Name = XDR Proc Priority ISSU client, Entity_Count = 1Client_ID = 2023, Client_Name = FIB HWIDB ISSU client, Entity_Count = 1Client_ID = 2024, Client_Name = FIB IDB ISSU client, Entity_Count = 1Client_ID = 2025, Client_Name = FIB HW subblock ISSU client, Entity_Count = 1Client_ID = 2026, Client_Name = FIB SW subblock ISSU client, Entity_Count = 1Client_ID = 2027, Client_Name = Adjacency ISSU client, Entity_Count = 1Client_ID = 2028, Client_Name = FIB IPV4 ISSU client, Entity_Count = 1Client_ID = 2030, Client_Name = MFI Pull ISSU client, Entity_Count = 1Client_ID = 2031, Client_Name = MFI Push ISSU client, Entity_Count = 1Client_ID = 2051, Client_Name = ISSU CCM Client, Entity_Count = 1Client_ID = 2052, Client_Name = ISSU PPP SIP CCM Client, Entity_Count = 1Client_ID = 2054, Client_Name = ISSU process client, Entity_Count = 1Base Clients:Client_Name = ISSU Proto clientClient_Name = ISSU RFClient_Name = ISSU CF clientClient_Name = ISSU Network RF clientClient_Name = ISSU CONFIG SYNCClient_Name = ISSU ifIndex syncClient_Name = ISSU IPC clientClient_Name = ISSU IPC Server clientClient_Name = ISSU Red Mode ClientClient_Name = ISSU EHSA services clientTable 73 describes the significant fields shown in the display.
Related Commands
show issu entities
To display information about entities within one or more In Service Software Upgrade (ISSU) clients, use the show issu entities command in user EXEC or privileged EXEC mode.
show issu entities [client_id]
Note
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
This command was introduced.
12.2(33)SRB1
ISSU is supported on the Cisco 7600 series routers in Cisco IOS Release 12.2(33)SRB.
Usage Guidelines
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 show issu clients 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:
Router# show issu entities 2008Client_ID = 2008 :Entity_ID = 1, Entity_Name = Tableid Entity :MsgType MsgGroup CapType CapEntry CapGroupCount Count Count count Count2 2 1 2 2
Related Commands
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 show issu message types command in user EXEC or privileged EXEC mode.
show issu message types client-id
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
This command was introduced.
12.2(33)SRB1
ISSU is supported on the Cisco 7600 series routers in Cisco IOS Release 12.2(33)SRB.
Usage Guidelines
If you are not sure of the Client_ID number to enter into this command, use the show issu clients command. It displays the current list of clients, along with their names and ID numbers.
Examples
The following example displays the message type, version, and maximum message size supported by the Multiprotocol Label Switching (MPLS) Virtual Private Network (VPN) client:
Router# show issu message types 2009Client_ID = 2009, Entity_ID = 1 :Message_Type = 1, Version_Range = 1 ~ 1Message_Ver = 1, Message_Mtu = 32Table 75 describes the significant fields shown in the display.
Related Commands
show issu negotiated
To display details of the session's negotiation about message version or client capabilities, use the show issu negotiated command in user EXEC or privileged EXEC mode.
show issu negotiated {version | capability} session-id
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
This command was introduced.
12.2(33)SRB1
ISSU is supported on the Cisco 7600 series routers in Cisco IOS Release 12.2(33)SRB.
Usage Guidelines
If you are not sure of the session_ID number to enter into this command, enter the show issu sessions command. It will display the session_ID.
Examples
The following example displays the results of a negotiation about message versions:
router# show issu negotiated version 39Session_ID = 39 :Message_Type = 1, Negotiated_Version = 1, Message_MTU = 32Table 76 describes the significant fields shown in the display.
The following example displays the results of a negotiation about the client application's capabilities:
router# show issu negotiated capability 39Session_ID = 39 :Negotiated_Cap_Entry = 1Table 77 describes the significant fields shown in the display.
Related Commands
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 show issu sessions command in user EXEC or privileged EXEC mode.
show issu sessions client-id
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
This command was introduced.
12.2(33)SRB1
ISSU is supported on the Cisco 7600 series routers in Cisco IOS Release 12.2(33)SRB.
Usage Guidelines
If you are not sure of the Client_ID number to enter into this command, use the show issu clients 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:
Router# show issu sessions 2011Client_ID = 2011, Entity_ID = 1 :*** Session_ID = 46, Session_Name = LDP Session :Peer Peer Negotiate Negotiated Cap Msg SessionUniqueID Sid Role Result GroupID GroupID Signature4 34 PRIMARY COMPATIBLE 1 1 0(no policy)Negotiation Session Info for This Message Session:Nego_Session_ID = 46Nego_Session_Name = LDP SessionTransport_Mtu = 3948Table 78 describes the significant fields shown in the display.
Related Commands
show mpls atm-ldp bindings
Note
To display specified entries from the ATM label binding database, use the show mpls atm-ldp bindings command in privileged EXEC mode.
show mpls atm-ldp bindings [network {mask | length}] [local-label vpi vci] [remote-label vpi vci] [neighbor interface]
Syntax Description
Command Default
The entire ATM label binding database is displayed if no optional arguments or keywords are specified.
Note
Command Modes
Privileged EXEC (#)
Command History
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:
•
•
•
Note
Note
Examples
The following is sample output from the show mpls atm-ldp bindings command:
Router# show mpls atm-ldp bindingsDestination: 10.24.0.0/24Tailend Router ATM1/0.1 1/39 Active, VCD=3Destination: 10.15.0.15/32Tailend Router ATM1/0.1 1/33 Active, VCD=4Destination: 10.0.7.7/32Headend Router ATM1/0.1 (2 hops) 1/34 Active, VCD=810The following is sample output from the show mpls atm-ldp bindings command on an ATM switch:
Router# show mpls atm-ldp bindingsDestination: 172.16.0.0/16Tailend Switch ATM0/0/3 1/35 Active -> Terminating ActiveDestination: 10.4.4.4/32Transit ATM0/0/3 1/33 Active -> ATM0/1/1 1/33 ActiveTable 79 describes the significant fields shown in the displays.
Related Commands
show mpls ip binding
Displays specified information about label bindings learned by the MPLS LDP.
show mpls atm-ldp bindwait
Note
To display the number of bindings waiting for label assignments from a remote Multiprotocol Label Switching (MPLS) ATM switch, use the show mpls atm-ldp bindwait command in privileged EXEC mode.
show mpls atm-ldp bindwait
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Use this command to display information about virtual circuits (VCs) in the bindwait state.
Examples
The following is sample output from the show mpls atm-ldp bindwait command:
Router# show mpls atm-ldp bindwaitWaiting for bind on ATM1/0.210.3.3.1/32 10.3.3.1/32 10.3.3.2/3210.3.3.2/32 10.3.3.3/32 10.3.3.3/3210.3.3.4/32 10.3.3.4/32 10.3.3.5/3210.3.3.5/32 10.3.3.6/32 10.3.3.6/3210.3.3.7/32 10.3.3.7/32 10.3.3.8/3210.3.3.8/32 10.3.3.9/32 10.3.3.9/32...endIf there are no bindings waiting for label assignments from the remote MPLS ATM switch, this command does not display any output.
Related Commands
show mpls atm-ldp bindings
Displays specified entries from the ATM label binding database.
show mpls atm-ldp capability
Note
To display the Multiprotocol Label Switching (MPLS) ATM capabilities negotiated with Label Distribution Protocol (LDP) neighbors for label-controlled (LC)-ATM interfaces, use the show mpls atm-ldp capability command in privileged EXEC mode.
show mpls atm-ldp capability
Syntax Description
This command has no arguments or keywords.
Command Default
This command always displays all the MPLS ATM capabilities negotiated with all the LDP neighbors.
Command Modes
Privileged EXEC (#)
Command History
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
Examples
The following is sample output from the show mpls atm-ldp capability command:
Router# show mpls atm-ldp capabilityVPI VCI Alloc Odd/Even VC MergeATM0/1/0 Range Range Scheme Scheme IN OUTNegotiated [100 - 101] [33 - 1023] UNIDIR - -Local [100 - 101] [33 - 16383] UNIDIR EN ENPeer [100 - 101] [33 - 1023] UNIDIR - -VPI VCI Alloc Odd/Even VC MergeATM0/1/1 Range Range Scheme Scheme IN OUTNegotiated [201 - 202] [33 - 1023] BIDIR - -Local [201 - 202] [33 - 16383] UNIDIR ODD NO NOPeer [201 - 202] [33 - 1023] BIDIR EVEN - -Table 80 describes the significant fields shown in the display.
Related Commands
mpls ldp atm vc-merge
Controls whether the vc-merge (multipoint-to-point) is supported for unicast label VCs.
show mpls atm-ldp summary
Note
To display summary information about all the entries in the ATM label binding database, use the show mpls atm-ldp summary command in privileged EXEC mode.
show mpls atm-ldp summary
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Use this command to display dynamic ATM accounting information.
Examples
The following is sample output from the show mpls atm-ldp summary command:
Router# show mpls atm-ldp summaryTotal number of destinations: 406ATM label bindings summaryinterface total active local remote Bwait Rwait IFwaitATM0/0/0 406 406 404 2 0 0 0ATM0/0/1 406 406 3 403 0 0 0Table 81 describes the significant fields shown in the display.
Related Commands
show isis database verbose
Displays the requested entries from the ATM LDP label binding database.
show mls cef mpls exact-route
To display the Multiprotocol Label Switching (MPLS) hardware load-sharing results from the Multilayer Switching (MLS) hardware Layer 3 switching table, use the show mls cef mpls exact-route command in user EXEC or privileged EXEC mode.
show mls cef mpls exact-route {dst-address src-address label-stack-depth value label outer-most-value | label outer-most-value} [label inner-most-value]
Syntax Description
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
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
You must configure the appropriate parameters based on the control word in the incoming packets as follows:
•
Note
•
Note
Examples
The following is sample output from the show mls cef mpls exact-route command. Fields in the display are self-explanatory.
Router# show mls cef mpls exact-route 192.0.2.1 192.0.2.2 label-stack-depth 2 label 19For EOS [0] choice Adjancency details are:Interface: Gi3/3/0, Next Hop: 192.168.3.1, Vlan: 1019, DestinationMac: 0006.5248.a400For EOS [1] choice Adjancency details are:Interface: Gi3/3/0, Next Hop: 192.168.3.1, Vlan: 1019, DestinationMac: 0006.5248.a400The following is sample output from the show mls cef mpls exact-route command when the source and destination IP address are not specified. Fields in the display are self-explanatory.
Router# show mls cef mpls exact-route label 18 label 20For EOS [0] choice Adjancency details are:Interface: Te1/0/0, Next Hop: 10.0.0.1, Vlan: 1023, DestinationMac: 000b.fc1c.ee40For EOS [1] choice Adjancency details are:Interface: Te1/0/0, Next Hop: 10.0.0.1, Vlan: 1023, DestinationMac: 000b.fc1c.ee40Related Commands
show mpls cos-map
Note
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 command in privileged EXEC mode.
show mpls cos-map [cos-map]
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Not entering a specific QoS number causes all QoS maps to be displayed.
Note
Examples
The following is sample output from the show mpls cos-map command:
Router# show mpls cos-map 2cos-map 2 class Label-VC3 control2 control1 available0 availableTable 82 describes the significant fields shown in the display.
Related Commands
mpls cos-map
Creates a class map specifying how classes map to label virtual circuits when they are combined with a prefix map.
show mpls flow mappings
To display all entries in the Multiprotocol Label Switching (MPLS) Prefix/Application/Label (PAL) table, use the show mpls flow mappings command in user EXEC mode or privileged EXEC mode.
show mpls flow mappings
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC
Privileged EXECCommand History
12.2(28)SB
This command was introduced.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Usage Guidelines
If you are interested in only a certain type of MPLS label and do not want to display the entire MPLS PAL table, you can use the show mpls flow mappings | include label-type command.
Examples
The following sample output from the show mpls flow mappings command displays all entries in the MPLS PAL table:
Router# show mpls flow mappingsLabel Owner Route-Distinguisher Prefix Allocated18 LDP 10.0.0.5 00:52:1021 BGP 0.0.0.0 00:52:1822 BGP 0.0.0.0 00:52:1825 BGP 0.0.0.0 00:51:4426 LDP 10.32.0.0 00:52:1027 TE-MIDPT 10.30.0.2 00:52:0628 LDP 10.33.0.0 00:52:1029 LDP 10.0.0.1 00:52:1030 LDP 10.0.0.3 00:52:10In 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.
Table 83 describes the significant fields shown in the display.
The following is sample output from the show mpls flow mappings command if you previously entered the mpls export vpnv4 prefixes command:
# show mpls flow mappingsLabel Owner Route-Distinguisher Prefix Allocated16 LDP 10.0.0.3 00:58:0317 LDP 10.33.0.0 00:58:0319 TE-MIDPT 10.30.0.2 00:58:0620 LDP 10.0.0.5 00:58:0323 LDP 10.0.0.1 00:58:0324 LDP 10.32.0.0 00:58:0327 BGP 100:1 10.34.0.0 00:57:4831 BGP 100:1 10.0.0.9 00:58:2132 BGP 100:1 10.3.3.0 00:58:21The following sample output from the show mpls flow mappings | include LDP command displays only MPLS PAL entries that were allocated by LDP:
Router# show mpls flow mappings | include LDPLabel Owner Route-Distinguisher Prefix Allocated16 LDP 10.0.0.3 00:58:0317 LDP 10.33.0.0 00:58:0320 LDP 10.0.0.5 00:58:0323 LDP 10.0.0.1 00:58:0324 LDP 10.32.0.0 00:58:03Related Commands
show ip cache verbose flow
Displays a detailed summary of NetFlow statistics.
show ip flow export
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.
show mpls forwarding vrf vrf-name [ip-prefix/length [mask]] [detail] [output-modifiers]
no show mpls forwarding vrf vrf-name [ip-prefix/length [mask]] [detail] [output-modifiers]
Syntax Description
Command Default
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to display label forwarding entries associated with a particular VRF or IP prefix.
Examples
The following example shows label forwarding entries that correspond to the VRF called vpn1:
Router# show mpls forwarding vrf vpn1 detailLocal Outgoing Prefix Bytes tag Outgoing Next Hoptag tag or VC or Tunnel Id switched interface35 24 10.0.0.0/8[V] 0 Et0/0/4 10.0.0.1MAC/Encaps=14/22, MRU=1496, Tag Stack{24 19}00D006FEDBE100D0974988048847 0001800000013000VPN route: vpn1No output feature configuredPer-packet load-sharingRelated Commands
show ip cef vrf
Displays VRFs and associated interfaces.
show mpls forwarding-table
Displays the contents of the LFIB.
show mpls forwarding-table
To display the contents of the Multiprotocol Label Switching (MPLS) Label Forwarding Information Base (LFIB), use the show mpls forwarding-table command in user EXEC or privileged EXEC mode.
show mpls forwarding-table [network {mask | length} | interface interface | labels label [- label] | lcatm atm atm-interface-number | next-hop address | lsp-tunnel [tunnel-id]] [vrf vrf-name] [detail slot slot-number]
Syntax Description
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
Examples
The following is sample output from the show mpls forwarding-table command:
Router# show mpls forwarding-tableLocal Outgoing Prefix Bytes label Outgoing Next HopLabel Label or VC or Tunnel Id switched interface26 No Label 10.253.0.0/16 0 Et4/0/0 10.27.32.428 1/33 10.15.0.0/16 0 AT0/0.1 point2point29 Pop Label 10.91.0.0/16 0 Hs5/0 point2point1/36 10.91.0.0/16 0 AT0/0.1 point2point30 32 10.250.0.97/32 0 Et4/0/2 10.92.0.732 10.250.0.97/32 0 Hs5/0 point2point34 26 10.77.0.0/24 0 Et4/0/2 10.92.0.726 10.77.0.0/24 0 Hs5/0 point2point35 No Label[T] 10.100.100.101/32 0 Tu301 point2point36 Pop Label 10.1.0.0/16 0 Hs5/0 point2point1/37 10.1.0.0/16 0 AT0/0.1 point2point[T] Forwarding through a TSP tunnel.View additional labeling info with the 'detail' optionThe 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.
Router# show mpls forwarding-tableLocal Outgoing Prefix Bytes label Outgoing Next HopLabel Label or VC or Tunnel Id switched interface16 Aggregate IPv6 017 Aggregate IPv6 018 Aggregate IPv6 019 Pop Label 192.168.99.64/30 0 Se0/0 point2point20 Pop Label 192.168.99.70/32 0 Se0/0 point2point21 Pop Label 192.168.99.200/32 0 Se0/0 point2point22 Aggregate IPv6 542423 Aggregate IPv6 357624 Aggregate IPv6 2600The following is sample output from the show mpls forwarding-table command when you specify the detail keyword. 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.
Router# show mpls forwarding-table detailLocal Outgoing Prefix Bytes label Outgoing Next Hoplabel label or VC or Tunnel Id switched interface16 Pop label 10.0.0.6/32 0 AT1/0.1 point2pointBundle adjacency exp(vcd)0(1) 1(1) 2(1) 3(1) 4(1) 5(1) 6(1) 7(1)MAC/Encaps=12/12, MTU=4474, label Stack{}00010000AAAA030000008847No output feature configured17 18 10.0.0.9/32 0 AT1/0.1 point2pointBundle adjacency exp(vcd)0(1) 1(1) 2(1) 3(1) 4(1) 5(1) 6(1) 7(1)MAC/Encaps=12/16, MTU=4470, label Stack{18}00010000AAAA030000008847 00012000No output feature configured18 19 10.0.0.10/32 0 AT1/0.1 point2pointBundle adjacency exp(vcd)0(1) 1(1) 2(1) 3(1) 4(1) 5(1) 6(1) 7(1)MAC/Encaps=12/16, MTU=4470, label Stack{19}00010000AAAA030000008847 00013000No output feature configured19 17 10.0.0.0/8 0 AT1/0.1 point2pointBundle adjacency exp(vcd)0(1) 1(1) 2(1) 3(1) 4(1) 5(1) 6(1) 7(1)MAC/Encaps=12/16, MTU=4470, label Stack{17}00010000AAAA030000008847 00011000No output feature configured20 20 10.0.0.0/8 0 AT1/0.1 point2pointBundle adjacency exp(vcd)0(1) 1(1) 2(1) 3(1) 4(1) 5(1) 6(1) 7(1)MAC/Encaps=12/16, MTU=4470, label Stack{20}00010000AAAA030000008847 00014000No output feature configured21 Pop label 10.0.0.0/24 0 AT1/0.1 point2pointBundle adjacency exp(vcd)0(1) 1(1) 2(1) 3(1) 4(1) 5(1) 6(1) 7(1)MAC/Encaps=12/12, MTU=4474, label Stack{}00010000AAAA030000008847No output feature configured22 Pop label 10.0.0.4/32 0 Et2/3 10.0.0.4MAC/Encaps=14/14, MTU=1504, label Stack{}000427AD10430005DDFE043B8847No output feature configuredThe following is sample output from the show mpls forwarding-table command when you use the detail keyword. 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."
Router# show mpls forwarding-table detailLocal Outgoing Prefix Bytes label Outgoing Next Hoplabel label or VC or Tunnel Id switched interface16 Aggregate 10.0.0.0/8[V] 0MAC/Encaps=0/0, MTU=0, label Stack{}VPN route: vpn1Feature Quick flag setPer-packet load-sharing, slots: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 1517 No label 10.0.0.0/8[V] 0 Et0/0/2 10.0.0.1MAC/Encaps=0/0, MTU=1500, label Stack{}VPN route: vpn1Feature Quick flag setPer-packet load-sharing, slots: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 1518 No label 10.42.42.42/32[V] 4185 Et0/0/2 10.0.0.1MAC/Encaps=0/0, MTU=1500, label Stack{}VPN route: vpn1Feature Quick flag setPer-packet load-sharing, slots: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 1519 2/33 10.41.41.41/32 0 AT1/0/0.1 point2pointMAC/Encaps=4/8, MTU=4470, label Stack{2/33(vcd=2)}00028847 00002000No output feature configuredCisco 10000 Series Examples
The following is sample output from the show mpls forwarding-table command for Cisco 10000 series routers:
Router# show mpls forwarding-tableLocal Outgoing Prefix Bytes Label Outgoing Next HopLabel Label or VC or Tunnel Id Switched interface16 Pop Label 10.0.0.0/8 0 Fa1/0/0 10.0.0.2Pop Label 10.0.0.0/8 0 Fa1/1/0 10.0.0.217 Aggregate 10.0.0.0/8[V] 570 vpn221 Pop Label 10.11.11.11/32 0 Fa1/0/0 10.0.0.222 Pop Label 10.12.12.12/32 0 Fa1/1/0 10.0.0.223 No Label 10.3.0.0/16[V] 0 Fa4/1/0 10.0.0.2The following is sample output from the show mpls forwarding-table command when you specify the detail keyword for Cisco 10000 series routers:
Router# show mpls forwarding-table detailLocal Outgoing Prefix Bytes Label Outgoing Next HopLabel Label or VC or Tunnel Id Switched interface16 Pop Label 10.0.0.0/8 0 Fa1/0/0 10.0.0.2MAC/Encaps=14/14, MRU=1500, Label Stack{}000B45C93889000B45C930218847No output feature configuredPop Label 10.0.0.0/8 0 Fa1/1/0 10.0.0.2MAC/Encaps=14/14, MRU=1500, Label Stack{}000B45C92881000B45C930288847No output feature configured17 Aggregate 10.0.0.0/8[V] 570 vpn2MAC/Encaps=0/0, MRU=0, Label Stack{}VPN route: vpn2No output feature configured21 Pop Label 10.11.11.11/32 0 Fa1/0/0 10.0.0.2MAC/Encaps=14/14, MRU=1500, Label Stack{}000B45C93889000B45C930218847No output feature configuredTable 84 describes the significant fields shown in the displays.
Explicit-Null Label Example
The following is sample output, including the explicit-null label = 0 (commented in bold), for the show mpls forwarding-table command on a CSC-PE router:
Router# show mpls forwarding-tableLocal Outgoing Prefix Bytes label Outgoing Next Hoplabel label or VC or Tunnel Id switched interface17 Pop label 10.10.0.0/32 0 Et2/0 10.10.0.118 Pop label 10.10.10.0/24 0 Et2/0 10.10.0.119 Aggregate 10.10.20.0/24[V] 020 Pop label 10.10.200.1/32[V] 0 Et2/1 10.10.10.121 Aggregate 10.10.1.1/32[V] 022 0 192.168.101.101/32[V] \0 Et2/1 192.168.101.10123 0 192.168.101.100/32[V] \0 Et2/1 192.168.101.10025 0 192.168.102.125/32[V] 0 Et2/1 192.168.102.125 !outlabel value 0Table 85 describes the significant fields shown in the display.
Cisco IOS Software Modularity: MPLS Layer 3 VPNs Example
The following is sample output from the show mpls forwarding-table command:
Router# show mpls forwarding-tableLocal Outgoing Prefix Bytes Label Outgoing Next HopLabel Label or Tunnel Id Switched interface16 Pop Label IPv4 VRF[V] 62951000 aggregate/v117 [H] No Label 10.1.1.0/24 0 AT1/0/0.1 point2pointNo Label 10.1.1.0/24 0 PO3/1/0 point2point[T] No Label 10.1.1.0/24 0 Tu1 point2point18 [HT] Pop Label 10.0.0.3/32 0 Tu1 point2point19 [H] No Label 10.0.0.0/8 0 AT1/0/0.1 point2pointNo Label 10.0.0.0/8 0 PO3/1/0 point2point20 [H] No Label 10.0.0.0/8 0 AT1/0/0.1 point2pointNo Label 10.0.0.0/8 0 PO3/1/0 point2point21 [H] No Label 10.0.0.1/32 812 AT1/0/0.1 point2pointNo Label 10.0.0.1/32 0 PO3/1/0 point2point22 [H] No Label 10.1.14.0/24 0 AT1/0/0.1 point2pointNo Label 10.1.14.0/24 0 PO3/1/0 point2point23 [HT] 16 172.1.1.0/24[V] 0 Tu1 point2point24 [HT] 24 10.0.0.1/32[V] 0 Tu1 point2point25 [H] No Label 10.0.0.0/8[V] 0 AT1/1/0.1 point2point26 [HT] 16 10.0.0.3/32[V] 0 Tu1 point2point27 No Label 10.0.0.1/32[V] 0 AT1/1/0.1 point2point[T] Forwarding through a TSP tunnel.View additional labelling info with the 'detail' option[H] Local label is being held down temporarily.Table 86 describes the Local Label fields relating to the Cisco IOS Software Modularity: MPLS Layer 3 VPNs feature.
L2VPN Inter-AS Option B: Example
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 Tunel Id column. The show mpls l2transport vc detail command can be used to obtain more information about the specific pseudowire displayed.
Router# show mpls forwarding-tableLocal Outgoing Prefix Bytes Label Outgoing Next HopLabel Label or Tunnel Id Switched interface1011 No Label l2ckt(4096) 0 none point2pointTable 87 describes the fields shown in the display.
Related Commands
show mpls interfaces
To display information about one or more or all interfaces that are configured for label switching, use the show mpls interfaces command in user EXEC or privileged EXEC mode.
show mpls interfaces [interface | vrf vpn-name] [all] [detail] [internal]
Syntax Description
Command Default
If no optional keyword or argument is specified in this command, summary information is displayed for each interface that has been configured for label switching in the default routing domain.
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
Usage Guidelines
This command shows MPLS information about the specified interface, or about all the interfaces for which MPLS has been configured.
If no optional keyword or argument is specified in this command, summary information is displayed for each interface configured for label switching.
Examples
The following is sample output from the show mpls interfaces command:
Router# show mpls interfacesInterface IP Tunnel OperationalEthernet1/1/1 Yes (tdp) No NoEthernet1/1/2 Yes (tdp) Yes NoEthernet1/1/3 Yes (tdp) Yes YesPOS2/0/0 Yes (tdp) No NoATM0/0.1 Yes (tdp) No No (ATM labels)ATM3/0.1 Yes (ldp) No Yes (ATM labels)ATM0/0.2 Yes (tdp) No YesCisco 10000 Series Example
The following is sample output from the show mpls interfaces command:
Router# show mpls interfacesInterface IP Tunnel BGP Static OperationalGigabitEthernet1/0/0 Yes No No No NoGigabitEthernet2/0/0 No No No Yes NoGigabitEthernet3/0/0 No Yes No No No
Note
Table 88 describes the significant fields shown in the display.
The following is sample output from the show mpls interfaces command with the detail keyword:
Router# show mpls interfaces detailInterface Ethernet1/1/1:IP labeling enabled (tdp)LSP Tunnel labeling not enabledMPLS operationalMPLS turbo vectorMTU = 1500Interface POS2/0/0:IP labeling enabled (ldp)LSP Tunnel labeling not enabledMPLS not operationalMPLS turbo vectorMTU = 4470Interface ATM3/0.1:IP labeling enabled (ldp)LSP Tunnel labeling not enabledMPLS operationalMPLS turbo vectorMTU = 4470ATM labels: Label VPI = 1Label VCI range = 33 - 65535Control VC = 0/32Cisco 10000 Series Example
The following example is sample output of the show mpls interfaces command with the detail keyword:
Router# show mpls interfaces detailInterface GigabitEthernet1/0/0:IP labeling enabled (ldp)LSP Tunnel labeling not enabledMPLS operationalMTU = 1500Interface POS2/0/0:IP labeling enabled (ldp)LSP Tunnel labeling not enabledMPLS not operationalMTU = 4470Table 89 describes the significant fields shown in the display.
The following is sample output from the show mpls interfaces command with the all keyword:
Router# show mpls interfaces allInterface IP Tunnel OperationalATM1/1/0.1 Yes (tdp) No YesVRF vpn1:ATM3/0/0.1 Yes (ldp) No YesVRF vpn2:ATM3/0/0.2 Yes (ldp) No YesVRF vpn3:ATM3/0/0.3 Yes (ldp) No YesVRF vpn4:ATM3/0/0.4 Yes (ldp) No YesVRF vpn5:ATM3/0/0.5 Yes (ldp) No YesVRF vpn6:Interface IP Tunnel OperationalATM3/0/0.6 Yes (ldp) No YesVRF vpn7:ATM3/0/0.7 Yes (ldp) No YesVRF vpn8:ATM3/0/0.8 Yes (ldp) No YesVRF vpn9:ATM3/0/0.9 Yes (ldp) No YesVRF vpn10:ATM3/0/0.10 Yes (ldp) No YesVRF vpn11:ATM3/0/0.11 Yes (ldp) No YesVRF vpn12:ATM3/0/0.12 Yes (ldp) No Yes...The following is sample output from the show mpls interfaces command with the internal keyword. 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.
Router# show mpls interfaces internalInterface Ethernet0/0/1:IP labeling enabled (tdp)LSP Tunnel labeling not enabledMPLS operationalIP to Tag Fast Feature Switching VectorMPLS turbo vectorMTU = 1500, status=0x100043, appcount=1Output_feature_state=0x0Interface Ethernet0/0/2:IP labeling enabled (tdp)LSP Tunnel labeling not enabledMPLS operationalIP to Tag Fast Feature Switching VectorMPLS turbo vectorMTU = 1500, status=0x100043, appcount=1Output_feature_state=0x1Related Commands
show mpls ip binding
To display specified information about label bindings learned by the Multiprotocol Label Switching (MPLS) Label Distribution Protocol (LDP), use the show mpls ip binding command in user EXEC or privileged EXEC mode.
show mpls ip binding [vrf vrf-name | all] [network {mask | length} [longer-prefixes]]
[neighbor address | local] [local-label {atm vpi vci | label [- label]}]
[remote-label {atm vpi vci | label [- label]}] [interface interface] [generic | atm]show mpls ip binding [vrf vrf-name | all] [detail | summary]
Cisco 10000 Series Routers
show mpls ip binding [network {mask | length} [longer-prefixes]] [neighbor address | local] [local-label label [- label]] [remote-label label [- label]] [generic]
show mpls ip binding [detail | summary]
Syntax Description
Defaults
All label bindings are displayed when no optional arguments or keywords are specified.
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
The show mpls ip binding command displays label bindings learned by LDP or the Tag Distribution Protocol (TDP).
Note
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:
•
•
•
•
Note
•
•
Note
Examples
The following is sample output from the show mpls ip binding command. The output shows all the label bindings in the database.
Router# show mpls ip binding10.0.0.0/8in label: 20out label: 26 lsr: 10.0.0.55:0out vc label: 1/80 lsr: 10.0.7.7:2 ATM1/0.8Active ingress 3 hops (vcd 49)172.16.0.0/8in label: 25in vc label: 1/36 lsr: 10.0.7.7:2 ATM1/0.8Active egress (vcd 55)out label: imp-null lsr: 10.0.0.55:0 inuse192.168.0.66/32in label: 26in vc label: 1/39 lsr: 10.0.7.7:2 ATM1/0.8Active egress (vcd 58)out label: 16 lsr: 10.0.0.55:0 inuse...In the following example, a request is made for the display of the label binding information for prefix 192.168.44.0/24:
Router# show mpls ip binding 192.168.44.0 24192.168.44.0/24in label: 24in vc label: 1/37 lsr: 10.0.7.7:2 ATM1/0.8Active egress (vcd 56)out label: imp-null lsr: 10.0.0.55:0 inuseIn the following example, the local-label keyword is used to request that label binding information be displayed for the prefix with local label 58:
Router# show mpls ip binding local-label 58192.168.0.0/16in label: 58out label: imp-null lsr: 10.0.0.55:0 inuseThe following sample output shows the label bindings for the VPN routing and forwarding instance named vpn1:
Router# show mpls ip binding vrf vpn110.3.0.0/16in label: 117out label: imp-null lsr:10.14.14.14:010.13.13.13/32in label: 1372out label: 268 lsr:10.14.14.14:010.14.14.14/32in label: 118out label: imp-null lsr:10.14.14.14:010.15.15.15/32in label: 1370out label: 266 lsr:10.14.14.14:010.16.16.16/32in label: 8370out label: 319 lsr:10.14.14.14:010.18.18.18/32in label: 21817out label: 571 lsr:10.14.14.14:030.2.0.0/16in label: 6943out label: 267 lsr:10.14.14.14:010.30.3.0/16in label: 2383out label: imp-null lsr:10.14.14.14:010.30.4.0/16in label: 77out label: imp-null lsr:10.14.14.14:010.30.5.0/16in label: 20715out label: 504 lsr:10.14.14.14:010.30.7.0/16in label: 17out label: imp-null lsr:10.14.14.14:010.30.10.0/16in label: 5016out label: 269 lsr:10.14.14.14:010.30.13.0/16in label: 76out label: imp-null lsr:10.14.14.14:0The following sample output shows label binding information for all VRFs:
Router# show mpls ip binding all10.0.0.0/24in label: imp-nullout label: imp-null lsr: 10.131.0.1:010.11.0.0/24in label: imp-nullout label: imp-null lsr: 10.131.0.1:010.101.0.1/32out label: imp-null lsr: 10.131.0.1:010.131.0.1/32in label: 20out label: imp-null lsr: 10.131.0.1:0 inuse10.134.0.1/32in label: imp-nullout label: 16 lsr: 10.131.0.1:0VRF vrf1:10.0.0.0/24out label: imp-null lsr: 10.132.0.1:010.11.0.0/24out label: imp-null lsr: 10.132.0.1:010.12.0.0/24in label: 17out label: imp-null lsr: 10.132.0.1:010.132.0.1/32out label: imp-null lsr: 10.132.0.1:010.134.0.2/32in label: 18out label: 16 lsr: 10.132.0.1:010.134.0.4/32in label: 19out label: 17 lsr: 10.132.0.1:010.138.0.1/32out label: imp-null lsr: 10.132.0.1:0Cisco 10000 Series Examples Only
The following sample shows binding information for a Cisco 10000 series router:
Router# show mpls ip binding0.0.0.0/0in label: imp-null10.29.0.0/16in label: imp-nullout label: imp-null lsr: 10.66.66.66:0out label: imp-null lsr: 10.44.44.44:010.20.0.0/24in label: imp-nullout label: 26 lsr: 10.66.66.66:0out label: imp-null lsr: 10.44.44.44:010.30.0.0/24in label: imp-nullout label: imp-null lsr: 10.66.66.66:0out label: 18 lsr: 10.44.44.44:010.44.44.44/32in label: 21out label: 19 lsr: 10.66.66.66:0in label: imp-nullout label: 26 lsr: 10.66.66.66:0out label: imp-null lsr: 10.44.44.44:010.30.0.0/24in label: imp-nullout label: imp-null lsr: 10.66.66.66:0out label: 18 lsr: 10.44.44.44:010.44.44.44/32in label: 21out label: 19 lsr: 10.66.66.66:0out label: imp-null lsr: 10.44.44.44:0 inuse10.55.55.55/32in label: imp-nullout label: 25 lsr: 10.66.66.66:0out label: 55 lsr: 10.44.44.44:010.66.66.66/32in label: 18out label: imp-null lsr: 10.66.66.66:0 inuseout label: 16 lsr: 10.44.44.44:010.255.254.244/32in label: 24out label: 16 lsr: 10.66.66.66:0out label: 59 lsr: 10.44.44.44:0In the following example on a Cisco 10000 series router, a request is made for the display of the label binding information for prefix 172.16.44.44/32:
Router# show mpls ip binding 172.16.44.44 32172.16.44.44/32in label: 21out label: 19 lsr: 10.66.66.66:0out label: imp-null lsr: 10.44.44.44:0 inuseIn the following example on a Cisco 10000 series router, the local-label keyword is used to request that label binding information be displayed for the prefix with local label 21:
Router# show mpls ip binding local-label 2110.44.44.44/32in label: 21Table 90 describes the significant fields shown in the displays.
The following sample output displays detailed information about the label bindings:
Router# show mpls ip binding detail10.0.0.0/8, rev 2, chkpt: add-skippedin label: imp-null (owner LDP)Advertised to:10.60.60.60:0 10.30.30.30:0out label: imp-null lsr: 10.60.60.60:0out label: imp-null lsr: 10.30.30.30:010.10.10.10/32, rev 18, chkpt: addedin label: 17 (owner LDP)Advertised to:10.60.60.60:0 10.30.30.30:0out label: 142 lsr: 10.60.60.60:0out label: 19 lsr: 10.30.30.30:0 inuse10.0.0.1/32, rev 10, chkpt: add-skippedin label: imp-null (owner LDP)Advertised to:10.60.60.60:0 10.30.30.30:0out label: 21 lsr: 10.60.60.60:0out label: 17 lsr: 10.30.30.30:010.30.30.30/32, rev 20, chkpt: addedin label: 18 (owner LDP)Advertised to:10.60.60.60:0 10.30.30.30:0out label: 22 lsr: 10.60.60.60:0Table 91 describes the significant fields shown in the display.
Cisco 7500 Series Example Only
The following sample output shows summary information about the label bindings learned by LDP:
Router# show mpls ip binding summaryTotal number of prefixes: 53Generic label bindingsassigned learnedprefixes in labels out labels53 53 51ATM label bindings summaryinterface total active local remote Bwait Rwait IFwaitATM1/0.8 47 47 40 7 0 0 0Router#Table 92 describes the significant fields shown in the display.
Cisco 10000 Series Example Only
The following sample output displays summary information about the label bindings learned by LDP:
Router# show mpls ip binding summaryTotal number of prefixes: 53Generic label bindingsassigned learnedprefixes in labels out labels53 53 51Table 93 describes the significant fields shown in the display.
Related Commands
show mpls atm-ldp bindings
Displays specified entries from the ATM label binding database.
show mpls ldp bindings
Displays the contents of the LIB.
show mpls ip iprm counters
To display the number of occurrences of various Multiprotocol Label Switching (MPLS) IP Rewrite Manager (IPRM) events, use the show mpls ip iprm counters command in privileged EXEC mode.
show mpls ip iprm counters
Syntax Description
This command has no arguments or keywords.
Defaults
No default behaviors or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command reports the occurrences of IPRM events.
Examples
The command in the following example displays the events that the IPRM logs:
Router# show mpls ip iprm countersCEF Tree Changes Processed/Ignored: 91/12CEF Deletes Processed/Ignored: 12/2Label Discoveries: 74Rewrite Create Successes/Failures: 60/0Rewrite Gets/Deletes: 82/0Label Announcements: Info/Local/Path: 6/119/80Walks: Recursion Tree/CEF Full/CEF interface: 78/2/0Table 94 describes the significant fields shown in the display.
Related Commands
clear mpls ip iprm counters
Clears the IPRM counters.
show mpls ip iprm ldm
Displays information about the IP LDMs that have registered with the IPRM.
show mpls ip iprm ldm
To display information about the IP Label Distribution Modules (LDMs) that have registered with the IP Rewrite Manager (IPRM), use the show mpls ip iprm ldm command in privileged EXEC mode.
show mpls ip iprm ldm [table {all | table-id} | vrf vrf-name] [ipv4 | ipv6]
Cisco 10000 Series Routers
show mpls ip iprm ldm [table {all | table-id} | vrf vrf-name] [ipv4]
Syntax Description
Defaults
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
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.
Router# show mpls ip iprm ldmtable (glbl;ipv4); ldms: 2lcatm, ldptable (glbl;ipv6); ldms: 1bgp ipv6The command in the following example displays all of the LDMs registered with IPRM. The output shows the following:
•
•
•
Router# show mpls ip iprm ldm table alltable (glbl;ipv4); ldms: 2lcatm, ldptable (glbl;ipv6); ldms: 1bgp ipv6table (all-tbls;ipv4); ldms: 1bgp vpnv4The command in the following example displays the LDMs registered for the IPv6 routing tables.
Router# show mpls ip iprm ldm ipv6table (glbl;ipv6); ldms: 1bgp ipv6Cisco 10000 Series Examples Only
The command in the following example displays the LDMs for the global routing tables. It shows that one LDM (ldp) is registered for the ipv4 global routing table.
Router# show mpls ip iprm ldmtable (glbl;ipv4); ldms: 1ldpThe command in the following example displays all of the LDMs registered with IPRM. The output shows the following:
•
•
Router# show mpls ip iprm ldm table alltable (glbl;ipv4); ldms: 1ldptable (all-tbls;ipv4); ldms: 1bgp vpnv4Related Commands
show mpls ip iprm counters
Displays the number of occurrences of various IPRM events.
show mpls ip iprm statistics
To display information about the IP Rewrite Manager (IPRM) statistics, use the show mpls ip iprm statistics command in privileged EXEC mode.
show mpls ip iprm statistics
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
Examples
The following is sample output from the show ip iprm statistics command:
Router# show mpls ip iprm statisticsChunk cache size: IPv4 pfx/path: 1/2Chunk cache size: outinfo: 2Table 95 describes the significant fields shown in the display.
Table 95 show mpls ip iprm statistics Field Descriptions
Chunk cache size
Displays the size of the cache.
Related Commands
show mpls ip iprm counters
Displays the number of occurrences of various MPLS IPRM events.
show mpls l2 vc detail
To display detailed information related to the virtual connection (VC), use the show mpls l2 vc detail command in user EXEC or privileged EXEC mode.
show mpls l2 vc vc-id detail
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
Examples
This example shows how to display detailed status for a specific VC:
Router# show mpls l2 vc 1100 detailLocal interface: VFI VPLS-1100 upMPLS VC type is VFI, internetworking type is EthernetDestination address: 1.1.1.1,VC ID:1100, VC status: upOutput interface: Tu0,imposed label stack {27 17}Preferred path: not configuredDefault path: activeNext hop:point2pointCreate time:2d23h, last status change time: 2d23hSignaling protocol: LDP, peer 1.1.1.1:0 upMPLS VC labels: local 17, remote 17Group ID: local 0, remote 0MTU: local 1500, remote 1500Remote interface description:Sequencing: receive disabled, send disabledVC statisticspacket totals: receive 1146978, send 3856011byte totals: receive 86579172, send 316899920packet drops: receive 0, send 0The following examples show the status of the active and backup pseudowires before, during, and after a switchover.
The show mpls l2 vc detail command on the active PE router displays the status of the pseudowires.
Router# show mpls l2 vc detailLocal intf Local circuit Dest address VC ID Status------------- -------------------------- --------------- ---------- ----------AT0/2/0.1 ATM VPC CELL 50 10.1.1.2 100 UPAT0/2/0.1 ATM VPC CELL 50 10.1.1.3 100 STANDBYThe show mpls l2 vc detail command on the backup PE router displays the status of the pseudowires. The active pseudowire on the backup PE router has the HOTSTANDBY status.
Router-standby# show mpls l2 vc detailLocal intf Local circuit Dest address VC ID Status------------- -------------------------- --------------- ---------- ----------AT0/2/0.1 ATM VPC CELL 50 10.1.1.2 100 HOTSTANDBYAT0/2/0.1 ATM VPC CELL 50 10.1.1.3 100 DOWNDuring a switchover, the status of the active and backup pseudowires changes:
Router# show mpls l2 vc detailLocal intf Local circuit Dest address VC ID Status------------- -------------------------- --------------- ---------- ----------AT0/2/0.1 ATM VPC CELL 50 10.1.1.2 100 RECOVERINGAT0/2/0.1 ATM VPC CELL 50 10.1.1.3 100 DOWNAfter the switchover is complete, the recovering pseudowire shows a status of UP:
Router# show mpls l2 vc detailLocal intf Local circuit Dest address VC ID Status------------- -------------------------- --------------- ---------- ----------AT0/2/0.1 ATM VPC CELL 50 10.1.1.2 100 UPAT0/2/0.1 ATM VPC CELL 50 10.1.1.3 100 STANDBYRelated Commands
show xconnect
Displays information about xconnect attachment circuits and pseudowires.
show mpls l2transport binding
To display virtual circuit (VC) label binding information, use the show mpls l2transport binding command in EXEC mode.
show mpls l2transport binding [vc-id | ip-address | local-label number | remote-label number}
Syntax Description
Command Modes
EXEC
Command History
Examples
The following example shows the VC label binding information for Cisco IOS Releases 12.0(27)S and 12.2(18)SXE and later releases:
Router# show mpls l2transport bindingDestination Address: 10.0.0.203, VC ID: 1Local Label: 16Cbit: 1, VC Type: Ethernet, GroupID: 0MTU: 1500, Interface Desc: n/aVCCV Capabilities: Type 1, Type 2Remote Label: 16Cbit: 1, VC Type: Ethernet, GroupID: 0MTU: 1500, Interface Desc: n/aVCCV Capabilities: Type 1, Type 2The following examples shows the VC label binding information for Cisco IOS Release 12.2(30)S and later releases:
Router# show mpls l2transport bindingDestination Address: 10.5.5.51, VC ID: 108Local Label: 16Cbit: 1, VC Type: Ethernet, GroupID: 0MTU: 1500, Interface Desc: n/aVCCV: CC Type: CW [1], RA [2]CV Type: LSPV [2]Remote Label: 16Cbit: 1, VC Type: Ethernet, GroupID: 0MTU: 1500, Interface Desc: n/aVCCV: CC Type: RA [2]CV Type: LSPV [2]The output of the command changed between Cisco IOS releases. The following table maps the older output to the new output:
VCCV Capabilities
VCCV: CC Type
Type 1
CW [1]
Type 2
RA [2]
The following example is a sample output of the show mpls l2transport binding command that shows the VC label binding information on a Cisco uBR10012 router:
Router# show mpls l2transport bindingDestination Address: 10.76.1.1, VC ID: 2002Local Label: 42Cbit: 1, VC Type: Ethernet, GroupID: 0MTU: 1500, Interface Desc: n/aVCCV: CC Type: CW [1], RA [2]CV Type: LSPV [2]Remote Label: 60Cbit: 1, VC Type: Ethernet, GroupID: 0MTU: 1500, Interface Desc: n/aVCCV: CC Type: RA [2]CV Type: LSPV [2]Destination Address: 10.76.1.1, VC ID: 2003Local Label: 46Cbit: 1, VC Type: Ethernet, GroupID: 0MTU: 1500, Interface Desc: n/aVCCV: CC Type: CW [1], RA [2]CV Type: LSPV [2]Remote Label: 27Cbit: 1, VC Type: Ethernet, GroupID: 0MTU: 1500, Interface Desc: n/aVCCV: CC Type: RA [2]CV Type: LSPV [2]Destination Address: 10.76.1.1, VC ID: 2004Local Label: unassigned.Remote Label: 111Cbit: 1, VC Type: Ethernet, GroupID: 0MTU: 1500, Interface Desc: n/aVCCV: CC Type: RA [2]CV Type: LSPV [2]Destination Address: 10.76.1.1, VC ID: 2017Local Label: 43Cbit: 1, VC Type: Ethernet, GroupID: 0MTU: 1500, Interface Desc: n/aVCCV: CC Type: CW [1], RA [2]CV Type: LSPV [2]Remote Label: 110Cbit: 1, VC Type: Ethernet, GroupID: 0MTU: 1500, Interface Desc: n/aVCCV: CC Type: RA [2]CV Type: LSPV [2]Destination Address: 10.76.1.1, VC ID: 2018Local Label: 45Cbit: 1, VC Type: Ethernet, GroupID: 0MTU: 1500, Interface Desc: n/aVCCV: CC Type: CW [1], RA [2]CV Type: LSPV [2]Remote Label: 88Cbit: 1, VC Type: Ethernet, GroupID: 0MTU: 1500, Interface Desc: n/aVCCV: CC Type: RA [2]CV Type: LSPV [2]Destination Address: 10.76.1.1, VC ID: 2019Local Label: 44Cbit: 1, VC Type: Ethernet, GroupID: 0MTU: 1500, Interface Desc: n/aVCCV: CC Type: CW [1], RA [2]CV Type: LSPV [2]Remote Label: 16Cbit: 1, VC Type: Ethernet, GroupID: 0MTU: 1500, Interface Desc: n/aVCCV: CC Type: RA [2]CV Type: LSPV [2]Table 96 describes the significant fields shown in the display.
The following sample output shows information about L2VPN multisegment pseudowires (in bold):
Router# show mpls l2transport bindingDestination Address: 10.1.1.1, VC ID: 102Local Label: 17Cbit: 1, VC Type: Ethernet, GroupID: 0MTU: 1500, Interface Desc: n/aVCCV: CC Type: CW [1], RA [2], TTL [3]CV Type: LSPV [2]Remote Label: 16Cbit: 1, VC Type: Ethernet, GroupID: 0MTU: 1500, Interface Desc: n/aVCCV: CC Type: CW [1], RA [2], TTL [3]CV Type: LSPV [2]PW Switching Point:Vcid local IP addr remote IP addr Description101 10.11.11.11 10.20.20.20 PW Switching Point PE3100 10.20.20.20 10.11.11.11 PW Switching Point PE2Table 97 describes the significant fields shown in the display.
CEM circuits are supported on the Cisco 7600 series router transport time-division multiplexing (TDM) traffic. The following example displays AToM VCs and the applicable local and remote CEM settings as exchanged over LDP label mapping messages.
Router# show mpls l2transport binding
Destination Address: 10.7.1.1, VC ID: 100Local Label: 18Cbit: 1, VC Type: CESoPSN BRI, GroupID: 0MTU: 1500, Interface Desc: n/aVCCV: CC Type: RA [2]CV Type: LSPV [2]CEM/TDM OptionsPayload Bytes: 80, Payload Type: 0SP bits: 11 - Data/Signaling, CAS Type: CAS T1 SFRTP header in use: Yes, Bitrate (Kbit/s): 64Differential Timestamp Mode: disabledClock Frequency (kHz): 64Synchronization Source id: 0Remote Label: 19Cbit: 1, VC Type: CESoPSN BRI, GroupID: 0MTU: 1500, Interface Desc: n/aVCCV: CC Type: RA [2]CV Type: LSPV [2]CEM/TDM OptionsPayload Bytes: 80, Payload Type: 0SP bits: 11 - Data/Signaling, CAS Type: CAS T1 SFRTP header in use: Yes, Bitrate (Kbit/s): 64Differential Timestamp Mode: disabledClock Frequency (kHz): 64Synchronization Source id: 0The following example shows the VC label binding information for the control word, which in this case is set to 0, meaning that it is disabled:
Router# show mpls l2transport binding 102Destination Address: 10.1.1.3, VC ID: 102Local Label: 1004Cbit: 0, VC Type: Ethernet, GroupID: 0MTU: 1500, Interface Desc: n/aVCCV: CC Type: CW [1], RA [2]CV Type: LSPV [2]Remote Label: 1005Cbit: 0, VC Type: Ethernet, GroupID: 0MTU: 1500, Interface Desc: n/aVCCV: CC Type: RA [2]CV Type: LSPV [2]The following example shows the maximum number of cells that can be packed (in bold) for both provider edge routers, as specified by the cell-packing command:Router# show mpls l2transport binding 1010Destination Address: 10.6.1.2, VC ID: 1010Local Label: 20008Cbit: 1, VC Type: ATM VCC CELL, GroupID: 0MTU: n/a, Interface Desc: n/aMax Concatenated ATM Cells: 10VCCV: CC Type: CW [1], RA [2]CV Type: LSPV [2], BFD [3]Remote Label: 47Cbit: 1, VC Type: ATM VCC CELL, GroupID: 0MTU: n/a, Interface Desc: n/aMax Concatenated ATM Cells: 10VCCV: CC Type: CW [1], RA [2]CV Type: LSPV [2]Related Commands
show mpls l2transport checkpoint
To display checkpointing information about Any Transport over MPLS (AToM) virtual circuits (VCs), use the show mpls l2transport checkpoint command in privileged EXEC mode.
show mpls l2transport checkpoint
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
Examples
The output of the commands varies, depending on whether the output reflects the active or standby Route Processor (RP).
On the active RP, the command displays the following output:
Router# show mpls l2transport checkpointAToM Checkpoint info for active RPCheckpointing is allowedBulk-sync checkpointed state for 1 VCOn the standby RP, the command displays the following output:
Router# show mpls l2transport checkpointAToM HA Checkpoint info for standby RP1 checkpoint information block in useIn 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
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.
show mpls l2transport hw-capability interface type number
Syntax Description
interface
Displays information for the specified interface.
type number
Type and number of the interface. For example, serial6/0.
Command Modes
Privileged EXEC (#)
Command History
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 Table 98.
Router# show mpls l2transport hw-capability interface serial5/1Interface Serial5/1Transport type FR DLCICore functionality:MPLS label disposition supportedControl word processing supportedSequence number processing not supportedEdge functionality:MPLS label imposition supportedControl word processing supportedSequence number processing not supported...
Note
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 Table 98.
Transport type FR DLCICore functionality:MPLS label disposition supportedControl word processing supportedSequence number processing not supportedVCCV CC Type 1 processing supportedEdge functionality:MPLS label imposition supportedControl word processing supportedSequence number processing not supported.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 Table 98.
Transport type FR DLCICore functionality:MPLS label disposition supportedControl word processing supportedSequence number processing not supportedVCCV CC Type CW [1] processing supportedEdge functionality:MPLS label imposition supportedControl word processing supportedSequence number processing not supported.The following is a sample output of the show mpls l2transport hw-capability command that displays the transport types supported on the Gigabit Ethernet interface 3/0/0 on a Cisco uBR10012 router:
Router# show mpls l2transport hw-capability interface gigabitethernet 3/0/0Interface GigabitEthernet3/0/0Transport type DOCSISCore functionality:MPLS label disposition supportedControl word processing supportedSequence number processing not supportedVCCV CC Type CW [1] processing not supportedEdge functionality:Not supportedTransport type DOCSIS VLANCore functionality:MPLS label disposition supportedControl word processing supportedSequence number processing not supportedVCCV CC Type CW [1] processing not supportedEdge functionality:Not supportedThe output of the command changed between Cisco IOS releases. The following table maps the older output to the newer output:
VCCV CC processing supported
VCCV CC processing supported
Type 1
Type CW [1]
Table 98 describes the fields shown in the show mpls l2transport hw-capability command display.
Related Commands
show mpls l2transport static-oam
To display the status of Multiprotocol Label Switching (MPLS) Transport Profile (TP) static pseudowires, use the show mpls l2transport static-oam command in privileged EXEC mode.
show mpls l2transport static-oam [fault [inbound |outbound]] [ip-address vc-id]
Syntax Description
Command Default
Status messages are not displayed.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
This command is for MPLS-TP static pseudowires.
Examples
The following example enables the display of status messages for the static pseudowire with the peer IP address of 10.10.10.10 and the VC ID of 4:
Router# show mpls l2transport static-oam 10.10.10.10 4Related Commands
debug mpls l2transport static-oam
Enables the display of messages related to static pseudowire operations administrative and management (OAM).
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.
show mpls l2transport summary
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
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:
Router# show mpls l2transport summaryDestination address: 10.16.24.12 Total number of VCs: 600 unknown, 58 up, 0 down, 2 admin down5 active vc on MPLS interface PO4/0The 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:
Router# show mpls l2transport summaryDestination address: 10.76.1.1, total number of vc: 60 unknown, 5 up, 1 down, 0 admin down, 0 recovering, 0 standby5 active vc on MPLS interface Gi3/0/0Table 99 describes the fields shown in the show mpls l2transport summary command display.
Related Commands
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.
show mpls l2transport vc [[vcid] vc-id-min] [vc-id-max] [interface type number [local-circuit-id]] [destination {ip-address | hostname}] [detail] [pwid pw-identifier] [vpls-id vpls-identifier] [stitch endpoint endpoint]
Syntax Description
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
Usage Guidelines
If you do not specify any keywords or arguments, the command displays a summary of all the VCs.
Examples
The output of the commands varies, depending on the type of Layer 2 packets being transported over AToM VCs.
The following sample output shows information about interfaces and VCs that have been configured to transport various Layer 2 packets on the router:
Router# show mpls l2transport vcLocal intf Local circuit Dest address VC ID Status------------- ------------------ --------------- ---------- ----------Se5/0 FR DLCI 55 10.0.0.1 55 UPAT4/0 ATM AAL5 0/100 10.0.0.1 100 UPAT4/0 ATM AAL5 0/200 10.0.0.1 200 UPAT4/0.300 ATM AAL5 0/300 10.0.0.1 300 UPTable 100 describes the fields shown in the display.
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.
Router# show mpls l2transport vc detailLocal interface: Fa5/1/1.2 down, line protocol down, Eth VLAN 2 upDestination address: 10.55.55.2, VC ID: 1002, VC status: downOutput interface: Se4/0/3, imposed label stack {16}Preferred path: not configuredDefault path: activeTunnel label: imp-null, next hop point2pointCreate time: 02:03:29, last status change time: 02:03:26Signaling protocol: LDP, peer 10.55.55.2:0 downMPLS VC labels: local 16, remote unassignedGroup ID: local 0, remote unknownMTU: local 1500, remote unknownRemote interface description:Sequencing: receive disabled, send disabledSSO Descriptor: 10.55.55.2/1002, local label: 16SSM segment/switch IDs: 12290/8193, PWID: 8193VC statistics:packet totals: receive 0, send 0byte totals: receive 0, send 0packet drops: receive 0, send 0Table 100 to Table 104 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.
Router# show mpls l2transport vc detailLocal interface: Et1/0 up, line protocol up, Ethernet upDestination address: 10.1.1.2, VC ID: 100, VC status: upOutput interface: Et2/0, imposed label stack {10003 150}Preferred path: not configuredDefault path: activeNext hop: 10.0.0.2Create time: 00:18:57, last status change time: 00:16:10Signaling protocol: ManualMPLS VC labels: local 100, remote 150Group ID: local 0, remote 0MTU: local 1500, remote 1500Remote interface description:Sequencing: receive disabled, send disabledVC statistics:packet totals: receive 219, send 220byte totals: receive 20896, send 26694packet drops: receive 0, send 0Table 100 to Table 104 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.
Router# show mpls l2transport vc detailLocal interface: Et1/0 up, line protocol up, Ethernet up...VC statistics:transit packet totals: receive 219, send 220transit byte totals: receive 20896, send 26694transit packet drops: receive 0, send 0Table 101 describes the significant fields shown in the display.
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.
Router# show mpls l2transport vc detailLocal interface: VFI my_test VFI upMPLS VC type is VFI, interworking type is EthernetDestination address: 10.3.3.1, VC ID: 123456, VC status: upNext hop PE address: 10.55.55.2Output interface: Et3/0, imposed label stack {17 19}Preferred path: not configuredDefault path:Next hop: 10.1.0.2Create time: 2d05h, last status change time: 2d05hSignaling protocol: LDP, peer 10.55.55.2:0 upMPLS VC labels: local 21, remote 19AGI: type 1, len 8, 0000 3333 4F4E 44C4Local AII: type 1, len 4, 0909 0909 (10.9.9.9)Remote AII: type 1, len 4, 0303 0301 (10.3.3.3)Group ID: local 0, remote 0MTU: local 1500, remote 1500Remote interface description:Sequencing: receive disabled, send disabledVC statistics:packet totals: receive 22611, send 22611byte totals: receive 2346570, send 2853581packet drops: receive 0, send 0Table 102 describes the fields shown in the display.
The following is sample output from the show mpls l2 transport vc command when the circuit emulation (CEM) interface is specified:
Router# show mpls l2transport vc interface CEM 3/1/1Local intf Local circuit Dest address VC ID Status---------- ------------- ------------ ----- ------CE3/1/1 CESOPSN Basic 10.30.30.3 300 DOWNTable 100 describes the fields shown in the display.
The following sample output displays (in bold) 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:
Router# show mpls l2transport vc detailLocal interface: VFI TEST VFI upMPLS VC type is VFI, interworking type is EthernetDestination address: 10.1.1.1, VC ID: 1000, VC status: upOutput interface: Se2/0, imposed label stack {17}Preferred path: not configuredDefault path: activeNext hop: point2pointCreate time: 00:04:34, last status change time: 00:04:15Signaling protocol: LDP, peer 10.1.1.1:0 upTargeted Hello: 10.1.1.1(LDP Id) -> 10.1.1.1MPLS VC labels: local 16, remote 17Group ID: local 0, remote 0MTU: local 1500, remote 1500Remote interface description:MAC Withdraw: sent 5, received 3Sequencing: receive disabled, send disabledVC statistics:packet totals: receive 0, send 0byte totals: receive 0, send 0packet drops: receive 0, send 0Table 100 to Table 104 describe the fields shown in the display.
The following sample output displays (in bold) the status messages for the MPLS Pseudowire Status Signaling feature when it is enabled on both PE routers:
Router# show mpls l2transport vc detailLocal interface: Et1/0 up, line protocol up, Ethernet upDestination address: 10.1.1.1, VC ID: 456, VC status: upOutput interface: Et2/0, imposed label stack {10005 10240}Preferred path: not configuredDefault path: activeNext hop: 10.0.0.1Create time: 00:39:30, last status change time: 00:26:48Signaling protocol: LDP, peer 10.1.1.1:0 upTargeted Hello: 10.1.1.2(LDP Id) -> 10.1.1.1Status TLV support (local/remote) : enabled/supportedLabel/status state machine : established, LruRruLast local dataplane status rcvd: no faultLast local SSS circuit status rcvd: no faultLast local SSS circuit status sent: no faultLast local LDP TLV status sent: no faultLast remote LDP TLV status rcvd: PW DOWN(rx,tx faults)MPLS VC labels: local 2000, remote 10240Group ID: local 6, remote 0MTU: local 1500, remote 1500Remote interface description:Sequencing: receive disabled, send disabledVC statistics:packet totals: receive 243651, send 243705byte totals: receive 27768366, send 34109320packet drops: receive 0, send 0Table 103 describes the fields shown in the display.
The following sample output from the show mpls l2 transport vc detail command displays the status of multisegment pseudowires:
Router# show mpls l2transport vc detailLocal interface: Se3/0 up, line protocol up, HDLC upDestination address: 10.12.1.1, VC ID: 100, VC status: downOutput interface: Se2/0, imposed label stack {23}Preferred path: not configuredDefault path: activeNext hop: point2pointCreate time: 00:03:02, last status change time: 00:01:41Signaling protocol: LDP, peer 10.12.1.1:0 upTargeted Hello: 10.11.1.1(LDP Id) -> 10.12.1.1, LDP is UPStatus TLV support (local/remote) : enabled/supportedLDP route watch : enabledLabel/status state machine : established, LruRrdLast local dataplane status rcvd: No faultLast local SSS circuit status rcvd: No faultLast local SSS circuit status sent: DOWN(PW-tx-fault)Last local LDP TLV status sent: No faultLast remote LDP TLV status rcvd: DOWN(PW-tx-fault)PW Switching Point:Fault type Vcid local IP addr remote IP addr DescriptionPW-tx-fault 101 10.13.1.1 10.12.1.1 S-PE2Last remote LDP ADJ status rcvd: No faultMPLS VC labels: local 19, remote 23Group ID: local 0, remote 0MTU: local 1500, remote 1500Remote interface description:Sequencing: receive disabled, send disabledVC statistics:packet totals: receive 16, send 27byte totals: receive 2506, send 3098packet drops: receive 0, seq error 0, send 0Table 104 describes the significant fields shown in the display.
The following sample output from the show mpls l2 transport vc command displays the status of the control word when it is not configured (that is, it defaults to autosense):
Router# show mpls l2transport vc 123400 detailLocal interface: Et0/0 up, line protocol up, Ethernet upDestination address: 10.1.1.2, VC ID: 123400, VC status: downOutput interface: if-?(0), imposed label stack {}Preferred path: not configuredDefault path: no routeNo adjacencyCreate time: 01:03:48, last status change time: 01:03:48Signaling protocol: LDP, peer 10.1.1.3:0 upTargeted Hello: 10.1.1.1(LDP Id) -> 10.1.1.2Status TLV support (local/remote) : enabled/unknown (no remote binding)Label/status state machine : local ready, LruRndLast local dataplane status rcvd: no faultLast local SSS circuit status rcvd: no faultLast local SSS circuit status sent: not sentLast local LDP TLV status sent: no faultLast remote LDP TLV status rcvd: unknown (no remote binding)MPLS VC labels: local 1002, remote unassignedGroup ID: local 0, remote unknownMTU: local 1500, remote unknownRemote interface description:Sequencing: receive disabled, send disabledControl Word: on (configured: autosense)If the control word is negotiated by the peer and is different from the configured value, the configured value is shown in parentheses.
•
Control Word: off (configured: disabled)•
Control Word: off (configured: enabled)•
Control Word: on (configured: autosense)The following sample output from the show mpls l2 transport 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:
Router# show mpls l2transport vc detailLocal interface: VFI dci_vlan_100 VFI upMPLS VC type is VFI, interworking type is EthernetDestination address: 10.2.2.2, VC ID: 100, VC status: upOutput interface: Tu0, imposed label stack {16}Preferred path: not configuredDefault path: activeNext hop: point2pointLoad Balance: FlowFlow Label: enabledTable 105 describes the significant fields shown in the display.
The following sample output from the show mpls l2 transport vc detail command displays BFD information:
Router# show mpls l2transport vc detailLocal interface: AT1/1/0 up, line protocol up, ATM AAL5 10/101 up Destination address: 10.1.1.151, VC ID: 1234001, VC status: up Output interface: Gi1/0/0, imposed label stack {2000} Preferred path: not configured Default path: active Next hop: 10.151.152.1 Create time: 6d03h, last status change time: 6d03h Signaling protocol: LDP, peer 10.1.1.151:0 up Targeted Hello: 10.1.1.152(LDP Id) -> 10.1.1.151, LDP is UP Status TLV support (local/remote) : enabled/supported LDP route watch : enabled Label/status state machine : established, LruRru Last local dataplane status rcvd: No fault Last local SSS circuit status rcvd: No fault Last local SSS circuit status sent: No fault Last local LDP TLV status sent: No fault Last remote LDP TLV status rcvd: No fault Last remote LDP ADJ status rcvd: No fault MPLS VC labels: local 2000, remote 2000 PWID: 20490 Group ID: local 0, remote 0 MTU: local 4470, remote 4470 Remote interface description: Sequencing: receive disabled, send disabled Control Word: On (configured: autosense) VCCV BFD protection active BFD Template - sampleBFDTemplate CC Type - 1 CV Type - fault detection only with IP/UDP headers VC statistics: transit packet totals: receive 0, send 0 transit byte totals: receive 0, send 0 transit packet drops: receive 0, seq error 0, send 0Table 106 describes the significant fields shown in the display.
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.
Router# show mpls l2transport vcLoad for five secs: 4%/1%; one minute: 4%; five minutes: 2%Time source is hardware calendar, *17:26:56.066 GMT Mon Oct 18 2010Local intf Local circuit Dest address VC ID Status------------- -------------------------- --------------- ---------- ----------VFI auto VFI 10.1.1.1 100 UPThe 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.
Router# show mpls l2transport vc detailLoad for five secs: 4%/1%; one minute: 4%; five minutes: 2%Time source is hardware calendar, *17:27:28.076 GMT Mon Oct 18 2010Local interface: VFI auto VFI upInterworking type is EthernetDestination address: 192.0.2.1, VC ID: 100, VC status: upNext hop PE address: 198.51.100.1Output interface: Et1/0, imposed label stack {2012}Preferred path: not configuredDefault path: activeNext hop: 10.0.0.3Create time: 00:00:48, last status change time: 00:00:48Signaling protocol: LDP, peer 192.0.2.3:0 upTargeted Hello: 192.0.2.6(from BGP) -> 192.0.2.8, LDP is UPStatus TLV support (local/remote) : enabled/supportedLDP route watch : enabledLabel/status state machine : established, LruRruLast local dataplane status rcvd: No faultLast local SSS circuit status rcvd: No faultLast local SSS circuit status sent: No faultLast local LDP TLV status sent: No faultLast remote LDP TLV status rcvd: No faultLast remote LDP ADJ status rcvd: No faultMPLS VC labels: local 1011, remote 2012PWID: 4096AGI: type 1, len 8, 000A 0001 0000 0001Local AII: type 1, len 4, 0101 0001 (203.0.113.1)Remote AII: type 1, len 4, 0201 0101 (203.0.113.5)VPLS-ID: 1:1Group ID: local n/a, remote n/aMTU: local 1500, remote 1500Remote interface description:Sequencing: receive disabled, send disabledControl Word: On (configured: autosense)SSO Descriptor: 203.0.113.5/100, local label: 1011SSM segment/switch IDs: 16387/8193 (used), PWID: 4096VC statistics:transit packet totals: receive 0, send 0transit byte totals: receive 0, send 0transit packet drops: receive 0, seq error 0, send 0Table 107 describes the feature-specific significant fields shown in the display.
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.
Router# show mpls l2transport vc detailLoad for five secs: 0%/0%; one minute: 0%; five minutes: 0%Time source is hardware calendar, *03:31:33.136 PST Thu Mar 24 2011Local interface: Et1/0.1 up, line protocol up, Eth VLAN 1001 upDestination address: 192.0.2.1, VC ID: 1234000, VC status: downOutput interface: Et0/0, imposed label stack {150}Preferred path: not configuredDefault path: activeNext hop: 198.58.100.2Create time: 00:03:45, last status change time: 00:00:02Signaling protocol: ManualStatus TLV support (local/remote) : enabled/N/ALDP route watch : enabledLabel/status state machine : established, LruRrdLast local dataplane status rcvd: No faultLast BFD dataplane status rcvd: No faultLast local SSS circuit status rcvd: No faultLast local SSS circuit status sent: DOWN AC(rx/tx faults)Last local LDP TLV status sent: NoneLast remote LDP TLV status rcvd: DOWN AC(rx/tx faults), (UP)Last remote LDP ADJ status rcvd: No faultMPLS VC labels: local 100, remote 150PWID: 4096Group ID: local 0, remote 0MTU: local 1500, remote 1500Sequencing: receive disabled, send disabledControl Word: On (configured: autosense)VCCV BFD protection activeBFD Template - t1CC Type - 1CV Type - fault detection and status signaling without IP/UDP headersVC statistics:transit packet totals: receive 0, send 5transit byte totals: receive 0, send 580transit packet drops: receive 0, seq error 0, send 0Table 108 describes the significant fields shown in the display.
Sample Output for show mpls l2transport vc Command on a Cisco uBR10012 Router in the Brief Display Format in Cisco IOS Release 12.2(33)SCF
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:
Router# show mpls l2transport vcLocal intf Local circuit Dest address VC ID Status------------- -------------------------- --------------- ---------- ----------Bu254 DOCSIS 55 10.2.3.4 55 DOWNBu254 DOCSIS 1000 10.2.3.4 1000 UPBu254 DOCSIS 400 10.76.2.1 400 UPBu254 DOCSIS 600 10.76.2.1 600 DOWNBu254 DOCSIS 1800 10.76.2.1 1800 UPBu254 DOCSIS 45454 10.76.2.1 45454 DOWNRelated Commands
show mpls label range
To display the range of local labels available for use on packet interfaces, use the show mpls label range command in privileged EXEC mode.
show mpls label range
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
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:
Router# show mpls label rangeDownstream label pool: Min/Max label: 16/100000Router# configure terminalRouter(config)# mpls label range 200 120000Router(config)# exitRouter# show mpls label rangeDownstream label pool: Min/Max label: 200/120000Related Commands
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.
show mpls ldp backoff [vrf vrf-name | all]
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
Examples
The following is sample output from the show mpls ldp backoff command:
Router# show mpls ldp backoffLDP initial/maximum backoff: 30/240 secBackoff table: 2 entriesLDP Id Backoff(sec) Waiting(sec)10.144.0.44:0 60 3010.155.0.55:0 120 90Table 109 describes the significant fields shown in the display.
The following is sample output from the show mpls ldp backoff vrf vrf-name command that shows one entry in the Backoff table for VRF vrf1:
Router# show mpls ldp backoff vrf vrf1LDP initial/maximum backoff: 15/120 secVRF vrf1 Backoff table: 1 entriesLDP Id Backoff(sec) Waiting(sec)10.12.0.2:0 120 30The following is sample output from a form of the show mpls ldp backoff command using the all keyword:
Router# show mpls ldp backoff allLDP initial/maximum backoff: 15/120 secBackoff table: 2 entriesLDP Id Backoff(sec) Waiting(sec)10.155.0.55:0 120 3010.144.0.44:0 60 60VRF vrf1 Backoff table: 1 entriesLDP Id Backoff(sec) Waiting(sec)10.12.0.2:0 120 45VRF vrf2 Backoff table: 1 entriesLDP Id Backoff(sec) Waiting(sec)10.13.0.1:0 120 30See Table 109 for a description of the significant fields shown in the displays.
Related Commands
mpls ldp backoff
Configures session setup delay parameters for the LDP backoff mechanism.
show mpls ldp bindings
To display the contents of the Label Information Base (LIB), use the show mpls ldp bindings command in user EXEC or privileged EXEC mode.
show mpls ldp bindings [vrf vrf-name | all] [network {mask | length} [longer-prefixes]]
[local-label label [- label]] [remote-label label [- label]] [neighbor address | local] [detail]Syntax Description
Defaults
If no optional keywords or arguments are entered, the command displays the LIB for the default routing domain only.
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
The show mpls ldp bindings command displays label bindings learned by the LDP or Tag Distribution Protocol (TDP).
Note
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:
•
•
•
Note
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.
Router# show mpls ldp bindings10.0.0.0/8, rev 9local binding: label: imp-nullremote binding: lsr: 10.10.0.55:0, label: 17remote binding: lsr: 10.66.0.66:0, label: 18remote binding: lsr: 10.0.0.44:0, label: imp-null172.16.0.0/8, rev 17local binding: label: 19remote binding: lsr: 10.0.0.55:0, label: imp-nullremote binding: lsr: 10.66.0.66:0, label: 16remote binding: lsr: 10.0.0.44:0, label: imp-null192.168.0.66/32, rev 19local binding: label: 20remote binding: lsr: 10.0.0.55:0, label: 19remote binding: lsr: 10.66.0.66:0, label: imp-nullremote binding: lsr: 10.0.0.44:0, label: 18...The following is sample output from the show mpls ldp bindings network length longer-prefixes neighbor address 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.
Router# show mpls ldp bindings 10.166.0.0 8 longer-prefixes neighbor 10.144.0.4410.166.44.0/16, rev 31remote binding: lsr: 10.144.0.44:0, label: 2510.166.45.0/16, rev 33remote binding: lsr: 10.144.0.44:0, label: 2610.166.245.0/16, rev 71remote binding: lsr: 10.144.0.44:0, label: 4510.166.246.0/16, rev 73remote binding: lsr: 10.144.0.44:0, label: 46...The following is sample output from the show mpls ldp bindings vrf vpn1 command, which displays the label bindings for the specified VPN routing and forwarding instance named vpn1:
Router# show mpls ldp bindings vrf vpn110.3.3.0/16, rev 164local binding: label:117remote binding:lsr:10.14.14.14:0, label:imp-null10.13.13.13/32, rev 1650local binding: label:1372remote binding:lsr:10.14.14.14:0, label:26810.14.14.14/32, rev 165local binding: label:118remote binding:lsr:10.14.14.14:0, label:imp-null10.15.15.15/32, rev 1683local binding: label:1370remote binding:lsr:10.14.14.14:0, label:26610.16.16.16/32, rev 775local binding: label:8370remote binding:lsr:10.14.14.14:0, label:31910.18.18.18/32, rev 1655local binding: label:21817remote binding:lsr:10.14.14.14:0, label:57110.30.2.0/16, rev 1653local binding: label:6943remote binding:lsr:10.14.14.14:0, label:26710.30.3.0/16, rev 413local binding: label:2383remote binding:lsr:10.14.14.14:0, label:imp-null10.30.4.0/16, rev 166local binding: label:77remote binding:lsr:10.14.14.14:0, label:imp-null10.30.5.0/16, rev 1429local binding: label:20715remote binding:lsr:10.14.14.14:0, label:50410.30.7.0/16, rev 4local binding: label:17remote binding:lsr:10.14.14.14:0, label:imp-null10.30.10.0/16, rev 422local binding: label:5016remote binding:lsr:10.14.14.14:0, label:269...The following is sample output from the show mpls ldp bindings all command, which displays the label bindings for all VRFs:
Router# show mpls ldp bindings alllib entry: 10.0.0.0/24, rev 4local binding: label: imp-nullremote binding: lsr: 10.131.0.1:0, label: imp-nulllib entry: 10.11.0.0/24, rev 15local binding: label: imp-nullremote binding: lsr: 10.131.0.1:0, label: imp-nulllib entry: 10.101.0.1/32, rev 18remote binding: lsr: 10.131.0.1:0, label: imp-nulllib entry: 10.131.0.1/32, rev 17local binding: label: 20remote binding: lsr: 10.131.0.1:0, label: imp-nulllib entry: 10.134.0.1/32, rev 6local binding: label: imp-nullremote binding: lsr: 10.131.0.1:0, label: 16VRF vrf1:lib entry: 10.0.0.0/24, rev 6remote binding: lsr: 10.132.0.1:0, label: imp-nulllib entry: 10.11.0.0/24, rev 7remote binding: lsr: 10.132.0.1:0, label: imp-nulllib entry: 10.12.0.0/24, rev 8local binding: label: 17remote binding: lsr: 10.132.0.1:0, label: imp-nulllib entry: 10.132.0.1/32, rev 4remote binding: lsr: 10.132.0.1:0, label: imp-nulllib entry: 10.134.0.2/32, rev 9local binding: label: 18remote binding: lsr: 10.132.0.1:0, label: 16lib entry: 10.134.0.4/32, rev 10local binding: label: 19remote binding: lsr: 10.132.0.1:0, label: 17lib entry: 10.138.0.1/32, rev 5remote binding: lsr: 10.132.0.1:0, label: imp-nullThe following is sample output from the show mpls ldp bindings detail command:
Router# show mpls ldp bindings detaillib entry: 10.3.3.0/16, rev 2,local binding: label: imp-nullAdvertised to:10.20.20.20:0 10.25.25.25:0remote binding: lsr: 10.20.20.20:0, label: imp-null staleremote binding: lsr: 10.25.25.25:0, label: imp-null stalelib entry: 10.13.1.0/24, rev 4,local binding: label: imp-nullAdvertised to:10.20.20.20:0 10.25.25.25:0remote binding: lsr: 10.20.20.20:0, label: imp-null staleremote binding: lsr: 10.25.25.25:0, label: 16 stalelib entry: 10.13.2.0/24, rev 6,local binding: label: imp-nullAdvertised to:10.20.20.20:0 10.25.25.25:0remote binding: lsr: 10.20.20.20:0, label: 16 staleremote binding: lsr: 10.25.25.25:0, label: imp-null stalelib entry: 10.6.1.0/24, rev 22,local binding: label: 21Advertised to:10.20.20.20:0 10.25.25.25:0remote binding: lsr: 10.20.20.20:0, label: 19 staleremote binding: lsr: 10.25.25.25:0, label: imp-null staleThe following is sample output from the show mpls ldp bindings detail command when LDP local label allocation filtering is configured:
Router# show mpls ldp bindings detailAdvertisement spec:Prefix acl = barLocal label filtering spec: host routes.lib entry: 10.1.1.1/32, rev 9lib entry: 10.10.7.0/24, rev 10lib entry: 10.10.8.0/24, rev 11lib entry: 10.10.9.0/24, rev 12lib entry: 10.41.41.41/32, rev 17lib entry: 10.50.50.50/32, rev 15lib entry: 10.60.60.60/32, rev 18lib entry: 10.70.70.70/32, rev 16lib entry: 10.80.80.80/32, rev 14Table 110 describes the significant fields shown in the displays.
Related Commandst
show mpls ip binding
Displays specified information about label bindings learned by the MPLS LDP.
show mpls ldp neighbor
Displays the status of LDP sessions.
show mpls ldp capabilities
To display the Label Distribution Protocol (LDP) capability information, use the show mpls ldp capabilities command in user EXEC or privileged EXEC mode.
show mpls ldp capabilities [vrf vrf-name | all]
Syntax Description
Defaults
Displays information about LDP capability for the default routing domain if you do not specify the optional vrf or all keyword.
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
Usage Guidelines
The show mpls ldp capabilities command can provide information about the capabilities that will be advertised through LDP sessions associated to a particular routing domain.
Examples
The following is sample output from the show mpls ldp capabilities command, which shows the router's capabilities associated with the default routing domain.
Router# show mpls ldp capabilitiesLDP Capabilities - [<description> (<type>)]---------------------------------------------------------[Dynamic Announcement (0x0506)][Typed Wildcard (0x050B)]The following is sample output from the show mpls ldp capabilities all command, which shows the router's capabilities associated with all VRF routing domains including the default routing domain.
Router# show mpls ldp capabilities allLDP Capabilities - [<description> (<type>)]---------------------------------------------------------[Dynamic Announcement (0x0506)][Typed Wildcard (0x050B)]VRF vpn1:[Dynamic Announcement (0x0506)][Typed Wildcard (0x050B)]VRF vpn2:[Dynamic Announcement (0x0506)][Typed Wildcard (0x050B)]The following is sample output from the show mpls ldp capabilities vrf command, which shows the router's capabilities associated with the VRF routing domain named vpn1:
Router# show mpls ldp capabilities vrf vpn1LDP Capabilities - [<description> (<type>)]---------------------------------------------------------[Dynamic Announcement (0x0506)][Typed Wildcard (0x050B)]Table 111 describes the significant fields shown in the displays.
Table 111 show mpls ldp neighbor Field Descriptions
LDP Capabilities
LDP capability information.
VRF
LDP capability information for the specified VRF.
Related Commands
show mpls ldp checkpoint
To display information about the Label Distribution Protocol (LDP) checkpoint system on the active route processor, use the show mpls ldp checkpoint command in user EXEC or privileged EXEC mode.
show mpls ldp checkpoint
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
This command shows the following LDP checkpointing information:
•
•
•
This command displays checkpoint status information only for the active route processor.
Examples
The following example shows the LDP checkpoint settings and configuration:
Router# show mpls ldp checkpointCheckpoint status: dynamic-syncCheckpoint resend timer: not running5 local bindings in add-skipped9 local bindings in added1 of 15+ local bindings in noneTable 112 describes the significant fields shown in the display.
Related Commands
show mpls ldp graceful-restart
Displays a summary of the LDP Graceful Restart status.
show mpls ldp discovery
To display the status of the Label Distribution Protocol (LDP) discovery process, use the show mpls ldp discovery command in user EXEC or privileged EXEC mode.
show mpls ldp discovery [vrf vrf-name | all] [detail]
Syntax Description
Defaults
This command displays neighbor discovery information for the default routing domain if an optional vrf keyword is not specified.
Command Modes
User EXEC
Privileged EXECCommand History
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:
Router# show mpls ldp discoveryLocal LDP Identifier:10.1.1.1:0Discovery Sources:Interfaces:Ethernet1/1/3 (ldp): xmit/recvLDP Id: 172.23.0.77:0LDP Id: 10.144.0.44:0LDP Id: 10.155.0.55:0ATM3/0.1 (ldp): xmit/recvLDP Id: 10.203.0.7:2ATM0/0.2 (tdp): xmit/recvTDP Id: 10.119.0.1:1Targeted Hellos:10.8.1.1 -> 10.133.0.33 (ldp): active, xmit/recvLDP Id: 10.133.0.33:010.8.1.1 -> 192.168.7.16 (tdp): passive, xmit/recvTDP Id: 10.133.0.33:0Router#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.
Router# show mpls ldp discovery allLocal LDP Identifier:10.12.12.12:0Discovery Sources:Interfaces:ATM1/1/0.1 (tdp):xmit/recvTDP Id:10.11.11.11:0VRF vpn1:Local LDP Identifier:172.30.7.2:0Discovery Sources:Interfaces:ATM3/0/0.1 (ldp):xmit/recvLDP Id:10.14.14.14:0VRF vpn2:Local LDP Identifier:172.30.13.2:0Discovery Sources:Interfaces:ATM3/0/0.2 (ldp):xmit/recvLDP Id:10.14.14.14:0VRF vpn3:Local LDP Identifier:172.30.15.2:0Discovery Sources:Interfaces:ATM3/0/0.3 (ldp):xmit/recvLDP Id:10.14.14.14:0VRF vpn4:Local LDP Identifier:172.30.17.2:0Discovery Sources:Interfaces:ATM3/0/0.4 (ldp):xmit/recvLDP Id:10.14.14.14:0VRF vpn5:Local LDP Identifier:172.30.19.2:0Discovery Sources:Interfaces:ATM3/0/0.5 (ldp):xmit/recvLDP Id:10.14.14.14:0VRF vpn6:Local LDP Identifier:172.30.21.2:0Discovery Sources:Interfaces:ATM3/0/0.6 (ldp):xmit/recvLDP Id:10.14.14.14:0VRF vpn7:Local LDP Identifier:172.23.2:0Discovery Sources:Interfaces:ATM3/0/0.7 (ldp):xmit/recvLDP Id:10.14.14.14:0VRF vpn8:Local LDP Identifier:172.30.25.2:0Discovery Sources:Interfaces:ATM3/0/0.8 (ldp):xmit/recvLDP Id:10.14.14.14:0VRF vpn9:Local LDP Identifier:172.30.27.2:0Discovery Sources:Interfaces:ATM3/0/0.9 (ldp):xmit/recvLDP Id:10.14.14.14:0VRF vpn10:Local LDP Identifier:172.30.29.2:0Discovery Sources:Interfaces:ATM3/0/0.10 (ldp):xmit/recvLDP Id:10.14.14.14:0VRF vpn11:Local LDP Identifier:172.30.31.2:0Discovery Sources:Interfaces:ATM3/0/0.11 (ldp):xmit/recvLDP Id:10.14.14.14:0VRF vpn12:Local LDP Identifier:172.30.33.2:0Discovery Sources:Interfaces:ATM3/0/0.12 (ldp):xmit/recvLDP Id:10.14.14.14:0VRF vpn13:Local LDP Identifier:Router#Table 113 describes the significant fields shown in the display.
The following is sample output from the show mpls ldp discovery detail command showing that LDP was enabled by the mpls ip command and the mpls ldp autoconfig command:
Router# show mpls ldp discovery detailLocal LDP Identifier:10.11.11.11:0Discovery Sources:Interfaces:Serial2/0 (ldp): xmit/recvEnabled: Interface config, IGP config;Hello interval: 5000 ms; Transport IP addr: 10.11.11.11LDP Id: 10.10.10.10:0Src IP addr: 172.140.0.1; Transport IP addr: 10.10.10.10Hold time: 15 sec; Proposed local/peer: 15/15 secTable 114 describes the significant fields shown in the display.
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.
Router# show mpls ldp discovery detailLocal LDP Identifier:10.10.10.10:0Discovery Sources:Interfaces:Ethernet1/0 (ldp): xmit/recvHello interval: 5000 ms; Transport IP addr: 10.10.10.10LDP Id: 10.4.4.4:0Src IP addr: 10.0.20.4; Transport IP addr: 10.4.4.4Hold time: 15 sec; Proposed local/peer: 15/15 secPassword: not required, none, stale <-- LDP MD5 password informationTargeted Hellos:10.10.10.10 -> 10.3.3.3 (ldp): passive, xmit/recvHello interval: 10000 ms; Transport IP addr: 10.10.10.10LDP Id: 10.3.3.3:0Src IP addr: 10.3.3.3; Transport IP addr: 10.3.3.3Hold time: 90 sec; Proposed local/peer: 90/90 secPassword: required, neighbor, in use <-- LDP MD5 password informationPassword information displayed by this command includes:
•
•
–
–
–
–
•
Related Commands
show mpls ldp graceful-restart
To display a summary of the Label Distribution Protocol (LDP) Graceful Restart status, use the show mpls ldp graceful-restart command in user EXEC or privileged EXEC mode.
show mpls ldp graceful-restart
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
This command shows the following information about LDP sessions:
•
•
•
Examples
The following example shows a summary of the LDP Graceful Restart settings and configuration:
Router# show mpls ldp graceful-restartLDP Graceful Restart is enabledNeighbor Liveness Timer: 5 secondsMax Recovery Time: 200 secondsDown Neighbor Database (0 records):Graceful Restart-enabled Sessions:VRF default:Peer LDP Ident: 10.18.18.18:0, State: estabPeer LDP Ident: 10.17.17.17:0, State: estabTable 115 describes the significant fields shown in the display.
Related Commands
show mpls ldp igp sync
To display the status of the Multiprotocol Label Switching (MPLS) Label Distribution Protocol (LDP)-Interior Gateway Protocol (IGP) synchronization process, use the show mpls ldp igp sync command in user EXEC or privileged EXEC mode.
show mpls ldp igp sync [all | interface type-number | vrf vrf-name]
Syntax Description
Command Default
If an optional argument is not specified, this command displays LDP synchronization for all interfaces enabled for MPLS LDP-IGP synchronization.
Command Modes
User EXEC(>)
Privileged EXEC(#)Command History
Examples
The following is sample output from the show mpls ldp igp sync command when LDP-IGP synchronization is not enabled on an interface:
Router# show mpls ldp igp syncEthernet0/0:LDP configured; SYNC enabled.SYNC status: sync achieved; peer reachable.IGP holddown time: infinite.Peer LDP Ident: 10.130.0.1:0IGP enabled: OSPF 1Table 116 describes the significant fields shown in the display.
If LDP-IGP synchronization is not enabled on an interface, the output looks like the following:
Router# show mpls ldp igp syncEthernet5/1:LDP configured; LDP-IGP Synchronization not enabled.The following is sample output from the show mpls ldp igp sync command when you configured a time delay for MPLS LDP-IGP synchronization:
Router# show mpls ldp igp syncEthernet0/0:LDP configured; LDP-IGP Synchronization enabled.Sync status: sync achieved; peer reachable.Sync delay time: 20 seconds (10 seconds left)IGP holddown time: infinite.IGP enabled: OSPF 1Related Commands
show mpls ldp neighbor
To display the status of Label Distribution Protocol (LDP) sessions, use the show mpls ldp neighbor command in user EXEC or privileged EXEC mode.
show mpls ldp neighbor [vrf vrf-name | all] [address | interface] [detail] [graceful-restart] [capabilities]
Syntax Description
Command Default
This command displays information about LDP neighbors for the default routing domain if you do not specify the optional vrf keyword.
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
Usage Guidelines
The show mpls ldp neighbor command can provide information about all LDP neighbors, or the information can be limited to the following:
•
•
Note
Examples
The following is sample output from the show mpls ldp neighbor command:
Router# show mpls ldp neighborPeer LDP Ident: 10.0.7.7:2; Local LDP Ident 10.1.1.1:1TCP connection: 10.0.7.7.11032 - 10.1.1.1.646State: Oper; Msgs sent/rcvd: 5855/6371; Downstream on demandUp time: 13:15:09LDP discovery sources:ATM3/0.1Peer LDP Ident: 10.1.1.1:0; Local LDP Ident 10.1.1.1:0TCP connection: 10.1.1.1.646 - 10.1.1.1.11006State: Oper; Msgs sent/rcvd: 4/411; DownstreamUp time: 00:00:52LDP discovery sources:Ethernet1/0/0Addresses bound to peer LDP Ident:10.0.0.29 10.1.1.1 10.0.0.199 10.10.1.110.205.0.9The following is sample output from the show mpls ldp neighbor command, in which duplicate addresses are detected. They indicate an error because a given address should be bound to only one peer.
Router# show mpls ldp neighborPeer LDP Ident: 10.0.7.7:2; Local LDP Ident 10.1.1.1:1TCP connection: 10.0.7.7.11032 - 10.1.1.1.646State: Oper; Msgs sent/rcvd: 5855/6371; Downstream on demandUp time: 13:15:09LDP discovery sources:ATM3/0.1Peer LDP Ident: 10.1.1.1:0; Local LDP Ident 10.1.1.1:0TCP connection: 10.1.1.1.646 - 10.1.1.1.11006State: Oper; Msgs sent/rcvd: 4/411; DownstreamUp time: 00:00:52LDP discovery sources:Ethernet1/0/0Addresses bound to peer LDP Ident:10.0.0.29 10.1.1.1 10.0.0.199 10.10.1.110.205.0.9Duplicate Addresses advertised by peer:10.10.8.111The following is sample output from the show mpls ldp neighbor vrf vpn10 command, which displays the LDP neighbor information for the specified VPN routing and forwarding instance named vpn10:
Router# show mpls ldp neighbor vrf vpn10Peer LDP Ident:10.14.14.14:0; Local LDP Ident 10.29.0.2:0TCP connection:10.14.14.14.646 - 10.29.0.2.11384State:Oper; Msgs sent/rcvd:1423/800; DownstreamUp time:02:38:11LDP discovery sources:ATM3/0/0.10Addresses bound to peer LDP Ident:10.3.36.9 10.7.0.1 10.14.14.14 10.13.0.110.15.0.1 10.17.0.1 10.19.0.1 10.21.0.110.23.0.1 10.25.0.1 10.27.0.1 10.29.0.110.31.0.1 10.33.0.1 10.35.0.1 10.37.0.110.39.0.1 10.41.0.1 10.43.0.1 10.45.0.110.47.0.1 10.49.0.1 10.51.0.1 10.53.0.110.55.0.1 10.57.0.1 10.59.0.1 10.61.0.110.63.0.1 10.65.0.1 10.67.0.1 10.69.0.110.71.0.1 10.73.0.1 10.75.0.1 10.77.0.110.79.0.1 10.81.0.1 10.83.0.1 10.85.0.110.87.0.1 10.89.0.1 10.91.0.1 10.93.0.110.95.0.1 10.97.0.1 10.99.0.1 10.101.0.110.103.0.1 10.105.0.1 10.107.0.1 10.109.0.110.4.0.2 10.3.0.2The following is sample output from the show mpls ldp neighbor detail command, which displays information about inbound filtering:
Router# show mpls ldp neighbor vrf vpn1 detailPeer LDP Ident: 10.13.13.13:0; Local LDP Ident 10.33.0.2:0TCP connection: 10.13.13.13.646 - 10.33.0.2.31581State: Oper; Msgs sent/rcvd: 11/10; Downstream; Last TIB rev sent 13Up time: 00:02:25; UID: 26; Peer Id 0;LDP discovery sources:Ethernet1/0/2; Src IP addr: 10.33.0.1holdtime: 15000 ms, hello interval: 5000 msAddresses bound to peer LDP Ident:10.3.105.1 10.13.13.13 10.33.0..1Peer holdtime: 180000 ms; KA interval: 60000 ms; Peer state: estabLDP inbound filtering accept acl:1Peer LDP Ident: 10.14.14.14:0; Local LDP Ident 10.33.0.2:0TCP connection: 10.14.14.14.646 - 10.33.0.2.31601State: Oper; Msgs sent/rcvd: 10/9; Downstream; Last TIB rev sent 13Up time: 00:01:17; UID: 29; Peer Id 3;LDP discovery sources:Ethernet1/0/3; Src IP addr: 10.33.0.1holdtime: 15000 ms, hello interval: 5000 msAddresses bound to peer LDP Ident:10.3.104.1 10.14.14.14 10.32.0.1Peer holdtime: 180000 ms; KA interval: 60000 ms; Peer state: estabLDP inbound filtering accept acl:1Capabilities Sent:[Dynamic Announcement (0x0506)][Typed Wildcard (0x050B)]Capabilities Received:[Dynamic Announcement (0x0506)][Typed Wildcard (0x050B)]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.
Router# show mpls ldp neighbor allPeer TDP Ident:10.11.11.11:0; Local TDP Ident 10.12.12.12:0TCP connection:10.11.11.11.711 - 10.12.12.12.11003State:Oper; PIEs sent/rcvd:185/187; DownstreamUp time:02:40:02TDP discovery sources:ATM1/1/0.1Addresses bound to peer TDP Ident:10.3.38.3 10.1.0.2 10.11.11.11VRF vpn1:Peer LDP Ident:10.14.14.14:0; Local LDP Ident 10.7.0.2:0TCP connection:10.14.14.14.646 - 10.7.0.2.11359State:Oper; Msgs sent/rcvd:952/801; DownstreamUp time:02:38:49LDP discovery sources:ATM3/0/0.1Addresses bound to peer LDP Ident:10.3.36.9 10.7.0.1 10.14.14.14 10.13.0.110.15.0.1 10.17.0.1 10.19.0.1 10.21.0.110.23.0.1 10.25.0.1 10.27.0.1 10.29.0.110.31.0.1 10.33.0.1 10.35.0.1 10.37.0.110.39.0.1 10.41.0.1 10.43.0.1 10.45.0.110.47.0.1 10.49.0.1 10.51.0.1 10.53.0.110.55.0.1 10.57.0.1 10.59.0.1 10.61.0.110.63.0.1 10.65.0.1 10.67.0.1 10.69.0.110.71.0.1 10.73.0.1 10.75.0.1 10.77.0.110.79.0.1 10.81.0.1 10.83.0.1 10.85.0.110.87.0.1 10.89.0.1 10.91.0.1 10.93.0.110.95.0.1 10.97.0.1 10.99.0.1 10.101.0.110.103.0.1 10.105.0.1 10.107.0.1 10.109.0.110.4.0.2 10.3.0.2VRF vpn2:Peer LDP Ident:10.14.14.14:0; Local LDP Ident 10.13.0.2:0TCP connection:10.14.14.14.646 - 10.13.0.2.11361State:Oper; Msgs sent/rcvd:964/803; DownstreamUp time:02:38:50LDP discovery sources:ATM3/0/0.2Addresses bound to peer LDP Ident:10.3.36.9 10.7.0.1 10.14.14.14 10.13.0.110.15.0.1 10.17.0.1 10.19.0.1 10.21.0.110.23.0.1 10.25.0.1 10.27.0.1 10.29.0.110.31.0.1 10.33.0.1 10.35.0.1 10.37.0.110.39.0.1 10.41.0.1 10.43.0.1 10.45.0.110.47.0.1 10.49.0.1 10.51.0.1 10.53.0.110.55.0.1 10.57.0.1 10.59.0.1 10.61.0.110.63.0.1 10.65.0.1 10.67.0.1 10.69.0.110.71.0.1 10.73.0.1 10.75.0.1 10.77.0.110.79.0.1 10.81.0.1 10.83.0.1 10.85.0.110.87.0.1 10.89.0.1 10.91.0.1 10.93.0.110.95.0.1 10.97.0.1 10.99.0.1 10.101.0.110.103.0.1 10.105.0.1 10.107.0.1 10.109.0.110.4.0.2 10.3.0.2VRF vpn3:Peer LDP Ident:10.14.14.14:0; Local LDP Ident 10.15.0.2:0TCP connection:10.14.14.14.646 - 10.15.0.2.11364State:Oper; Msgs sent/rcvd:1069/800; DownstreamUp time:02:38:52LDP discovery sources:ATM3/0/0.3Addresses bound to peer LDP Ident:10.3.36.9 10.17.0.1 10.14.14.14 10.13.0.110.15.0.1 10.17.0.1 10.19.0.1 10.21.0.110.23.0.1 10.25.0.1 10.27.0.1 10.29.0.110.31.0.1 10.33.0.1 10.35.0.1 10.37.0.110.39.0.1 10.41.0.1 10.43.0.1 10.45.0.110.47.0.1 10.49.0.1 10.51.0.1 10.53.0.110.55.0.1 10.57.0.1 10.59.0.1 10.61.0.110.63.0.1 10.65.0.1 10.67.0.1 10.69.0.110.71.0.1 10.73.0.1 10.75.0.1 10.77.0.110.79.0.1 10.81.0.1 10.83.0.1 10.85.0.110.87.0.1 10.89.0.1 10.91.0.1 10.93.0.110.95.0.1 10.97.0.1 10.99.0.1 10.101.0.110.103.0.1 10.105.0.1 10.107.0.1 10.109.0.110.4.0.2 10.3.0.2VRF vpn4:Peer LDP Ident:10.14.14.14:0; Local LDP Ident 10.17.0.2:0TCP connection:10.14.14.14.646 - 10.17.0.2.11366State:Oper; Msgs sent/rcvd:1199/802; DownstreamThe following is sample output from the show mpls ldp neighbor graceful-restart command, which shows the Graceful Restart status of the LDP neighbors:
Router# show mpls ldp neighbor graceful-restartPeer LDP Ident: 10.20.20.20:0; Local LDP Ident 10.17.17.17:0TCP connection: 10.20.20.20.16510 - 10.17.17.17.646State: Oper; Msgs sent/rcvd: 8/18; DownstreamUp time: 00:04:39Graceful Restart enabled; Peer reconnect time (msecs): 120000Peer LDP Ident: 10.19.19.19:0; Local LDP Ident 10.17.17.17:0TCP connection: 10.19.19.19.11007 - 10.17.17.17.646State: Oper; Msgs sent/rcvd: 8/38; DownstreamUp time: 00:04:30Graceful Restart enabled; Peer reconnect time (msecs): 120000The following sample output from the show mpls ldp neighbor detail command, which displays information about the MD5 password configuration:
Router# show mpls ldp neighbor detailPeer LDP Ident: 10.3.3:0; Local LDP Ident 10.1.1.1:0TCP connection: 10.3.3.3.11018 - 10.1.1.1.646Password: required, neighbor, in useState: Oper; Msgs sent/rcvd: 167/167; Downstream; Last TIB rev sent 9Up time: 02:24:02; UID: 5; Peer Id 3;LDP discovery sources:Targeted Hello 10.1.1.1 -> 10.3.3.3, passive;holdtime: 90000 ms, hello interval: 10000 msAddresses bound to peer LDP Ident:10.3.3.3 10.0.30.3Peer holdtime: 180000 ms; KA interval: 60000 ms; Peer state: estabPeer LDP Ident: 10.4.4.4:0; Local LDP Ident 10.1.1.1:0TCP connection: 10.4.4.4.11017 - 10.1.1.1.646Password: not required, none, staleState: Oper; Msgs sent/rcvd: 9/9; Downstream; Last TIB rev sent 9Up time: 00:05:35; UID: 6; Peer Id 1;LDP discovery sources:Ethernet1/0; Src IP addr: 10.0.20.4holdtime: 15000 ms, hello interval: 5000 msAddresses bound to peer LDP Ident:10.0.40.4 10.4.4.4 10.0.20.4Peer holdtime: 180000 ms; KA interval: 60000 ms; Peer state: estabTable 117 describes the significant fields shown in the displays.
Related Commands
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.
show mpls ldp neighbor [vrf vrf-name] [ip-address | interface] password [pending | current] [all]
Syntax Description
Defaults
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 EXECCommand History
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:
Router# show mpls ldp neighbor passwordPeer LDP Ident: 10.4.4.4:0; Local LDP Ident 10.1.1.1:0TCP connection: 10.4.4.4.11017 - 10.10.01.10.646Password: not required, none, staleState: Oper; Msgs sent/rcvd: 57/57Peer LDP Ident: 10.3.3.3:0; Local LDP Ident 10.1.1.1:0TCP connection: 10.3.3.3.11018 - 10.1.1.1.646Password: required, neighbor, in useState: Oper; Msgs sent/rcvd: 216/215The 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:
Router# show mpls ldp neighbor password pendingPeer LDP Ident: 10.4.4.4:0; Local LDP Ident 10.1.1.1:0TCP connection: 10.4.4.4.11017 - 10.1.1.1.646Password: not required, none, staleState: Oper; Msgs sent/rcvd: 57/57The following is sample output from the show mpls ldp neighbor password current command, which displays information for LDP sessions whose passwords are the same as those in the current configuration:
Router# show mpls ldp neighbor password currentPeer LDP Ident: 10.3.3.3:0; Local LDP Ident 10.1.1.1:0TCP connection: 10.3.3.3.11018 - 10.1.1.1.646Password: required, neighbor, in useState: Oper; Msgs sent/rcvd: 216/215Table 118 describes the significant fields shown in the displays.
Related Commands
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.
show mpls ldp parameters
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
User EXEC
Privileged EXECCommand History
Examples
The following is sample output from the show mpls ldp parameters command:
Router# show mpls ldp parametersProtocol version: 1Downstream label pool: min label 16; max label 100000Session hold time: 180 sec; keep alive interval: 60 secDiscovery hello: holdtime: 15 sec; interval: 5 secDiscovery targeted hello: holdtime: 180 sec; interval: 5 secLDP for targeted sessions; peer acl: 1LDP initial/maximum backoff: 30/240 secRouter#Table 119 describes the significant fields shown in the display.
Related Commands
mpls ldp holdtime
Changes the time for which an LDP session is maintained in the absence of LDP messages from the session peer.
show mpls memory
To display information about the Multiprotocol Label Switching (MPLS) Label Distribution Protocol memory usage, use the show mpls memory command in user EXEC or privileged EXEC mode.
show mpls memory [all] [component string | detailed]
Syntax Description
Command Modes
User EXEC(>)
Privileged EXEC(#)Command History
Examples
The following is sample output from the show mpls memory command:
Router: show mpls memoryAllocator-Name In-use/Allocated Count----------------------------------------------------------------------------LFD: AToM pwid : 0/67232 ( 0%) [ 0] ChunkLFD: FPI LBL : 144/22424 ( 0%) [ 4] ChunkLFD: LTE : 192/35704 ( 0%) [ 4] ChunkLFD: MOI DEAG : 96/22704 ( 0%) [ 3] ChunkLFD: MOI DROP : 20/24208 ( 0%) [ 1] ChunkLFD: RW NONE : 160/36248 ( 0%) [ 4] ChunkLSD: FPI FRR : 22312/22424 ( 99%) [ 2]LSD: FPI LBL : 22312/22424 ( 99%) [ 2]LSD: MOI DEAG : 23424/23536 ( 99%) [ 2]LSD: MOI DROP : 13424/13536 ( 99%) [ 2]LSD: RW NONE : 36136/36248 ( 99%) [ 2]LSD: intf : 33512/33624 ( 99%) [ 2]LSD: label tbl : 22704/35952 ( 63%) [ 516] ChunkLSD: label tbl : 64/1800 ( 3%) [ 1] ChunkMFI: Clnt CMsg : 0/65592 ( 0%) [ 0] ChunkMFI: Clnt SMsg : 71200/131184 ( 54%) [ 4] ChunkMFI: InfoReq : 0/808 ( 0%) [ 0] ChunkMFI: InfoRply : 0/65592 ( 0%) [ 0] ChunkTotal allocated: 0.629 Mb, 645 Kb, 661240 bytesTable 120 describes the significant fields shown in the display.
Related Commands
Feedback