Table Of Contents
show ip traffic-engineering routes
show ip vrf
show isis database verbose
show isis mpls ldp
show isis mpls traffic-eng adjacency-log
show isis mpls traffic-eng advertisements
show isis mpls traffic-eng tunnel
show issu clients
show issu entities
show issu message types
show issu negotiated
show issu sessions
show mpls atm-ldp bindings
show mpls atm-ldp bindwait
show mpls atm-ldp capability
sshow mpls atm-ldp summary
show mpls cos-map
show mpls flow mappings
show mpls forwarding vrf
show mpls forwarding-table
show mpls interfaces
show mpls ip binding
show mpls ip iprm counters
show mpls ip iprm ldm
show mpls l2 vc detail
show mpls l2transport binding
show mpls l2transport checkpoint
show mpls l2transport hw-capability
show mpls l2transport summary
show mpls l2transport vc
show mpls label range
show mpls ldp backoff
show mpls ldp bindings
show mpls ldp checkpoint
show mpls ldp discovery
show mpls ldp graceful-restart
show mpls ldp igp sync
show mpls ldp neighbor
show mpls ldp neighbor password
show mpls ldp parameters
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
Release
|
Modification
|
11.1CT
|
This command was introduced.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
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 routes
Installed traffic engineering routes:
Codes: T - traffic engineered route
T 43.0.0.1/32 (not override of routing table entry)
is directly connected, 00:06:35, Tunnel7
T 44.0.0.0/8 (override of routing table entry)
is directly connected, 01:12:39, Tunnel5
Table 62 describes the significant fields shown in the display.
Table 62 show ip traffic-engineering routes Field Descriptions
Field
|
Description
|
T
|
Traffic engineering route.
|
43.0.0.1/32 (not override of routing table entry) is directly connected
|
Prefix/mask being routed. The routing table does not contain an entry for this prefix/mask.
|
00:06:35
|
The time since the route was installed (hours:minutes:seconds).
|
Tunnel7
|
The LSP tunnel for the route.
|
Related Commands
Command
|
Description
|
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
brief
|
(Optional) Displays concise information on the VRFs and associated interfaces.
|
detail
|
(Optional) Displays detailed information on the VRFs and associated interfaces.
|
interfaces
|
(Optional) Displays detailed information about all interfaces bound to a particular VRF or any VRF.
|
id
|
(Optional) Displays the VPN IDs that are configured in a PE router for different VPNs.
|
vrf-name
|
(Optional) Name assigned to a VRF.
|
output-modifiers
|
(Optional) For a list of associated keywords and arguments, use context-sensitive help.
|
Defaults
When no keywords or arguments are specified, the command shows concise information about all configured VRFs.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.0(5)T
|
This command was introduced.
|
12.0(17)ST
|
This command was modified to include the id keyword, and VPN ID information was added to the output of the show ip vrf detail command.
|
12.2(4)B
|
This command was integrated into Cisco IOS Release 12.2(4)B.
|
12.2(8)T
|
This command was integrated into Cisco IOS Release 12.2(8)T.
|
12.3(6)
|
This command was integrated into Cisco IOS Release 12.3(6). The command shows the downstream VRF for each associated Virtual access interface (VAI).
|
12.0(22)S
|
Enhanced Interior Gateway Routing Protocol (EIGRP) VRF support was added.
|
12.2(15)T
|
EIGRP VRF support was integrated into Cisco IOS Release 12.2(15)T.
|
12.2(18)S
|
EIGRP VRF support was integrated into Cisco IOS Release 12.2(18)S.
|
12.2(27)SBC
|
This command was integrated into Cisco IOS Release 12.2(27)SBC.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
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.
•
The detail keyword displays all 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.
Name Default RD Interface
Table 63 describes the significant fields shown in the display.
Table 63 show ip vrf Field Descriptions
Field
|
Description
|
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 detail
VRF D; default RD 2:0; default VPNID <not set>
Loopback2 Virtual-Access3 [D] Virtual-Access4 [D]
Connected addresses are not in global routing table
Export VPN route-target communities
Import VPN route-target communities
VRF U; default RD 2:1; default VPNID <not set>
Virtual-Access3 Virtual-Access4
Connected addresses are not in global routing table
No Export VPN route-target communities
Import VPN route-target communities
Table 64 describes the significant fields shown in the display.
Table 64 show ip vrf detail Field Descriptions
Field
|
Description
|
VPNID
|
Specifies the VPN ID assigned to the VRF.
|
Interfaces
|
Specifies the network interfaces.
|
Virtual-Accessn [D]
|
Specifies the downstream VRF.
|
Export
|
Specifies VPN route-target export communities.
|
Import
|
Specifies VPN route-target import communities.
|
The following example shows the interfaces bound to a particular VRF:
Router# show ip vrf interfaces
Interface IP-Address VRF Protocol
Ethernet2 10.22.0.33 vrf1 up
Ethernet4 10.77.0.33 hub up
Table 65 describes the significant fields shown in the display.
Table 65 show ip vrf interfaces Field Descriptions
Field
|
Description
|
Interface
|
Specifies the network interfaces for a VRF.
|
IP-Address
|
Specifies the IP address of a VRF interface.
|
VRF
|
Specifies the VRF name.
|
Protocol
|
Displays the state of the protocol (up or down) for each VRF interface.
|
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):
Table 66 describes the significant fields shown in the display.
Table 66 show ip vrf id Field Descriptions
Field
|
Description
|
VPN Id
|
Specifies the VPN ID assigned to the VRF.
|
Name
|
Specifies the VRF name.
|
RD
|
Specifies the route distinguisher.
|
Related Commands
Command
|
Description
|
import map
|
Configures an import route map for a VRF.
|
ip vrf
|
Configures a VRF routing table.
|
ip vrf forwarding (interface configuration)
|
Associates a VRF with an interface or subinterface.
|
rd
|
Creates routing and forwarding tables for a VRF.
|
route-target
|
Creates a route-target extended community for a VRF.
|
vpn id
|
Assigns a VPN ID to a VRF.
|
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 EXEC
Command History
Release
|
Modification
|
12.0(5)S
|
This command was introduced.
|
12.1(3)T
|
This command was integrated into Cisco IOS Release 12.1(3)T.
|
12.0(10)ST
|
This command was integrated into Cisco IOS Release 12.0(10)ST.
|
12.2(27)SBC
|
This command was integrated into Cisco IOS Release 12.2(27)SBC.
|
12.2(28)SB
|
This command was integrated into Cisco IOS Release 12.2(28)SB.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
Examples
The following is sample output from the show isis database verbose command:
Router# show isis database verbose
IS-IS Level-1 Link State Database
LSPID LSP Seq Num LSP Checksum LSP Holdtime ATT/P/OL
dtp-5.00-00 * 0x000000E6 0xC9BB 1042 0/0/0
Metric:10 IP 172.16.39.0/24
dtp-5.00-01 * 0x000000E7 0xAB36 1065 0/0/0
Metric:10 IS-Extended dtp-5.01
Interface IP Address:172.21.39.5
Physical BW:10000000 bits/sec
Reservable BW:1166000 bits/sec
BW Unreserved[0]: 1166000 bits/sec, BW Unreserved[1]: 1166000 bits/sec
BW Unreserved[2]: 1166000 bits/sec, BW Unreserved[3]: 1166000 bits/sec
BW Unreserved[4]: 1166000 bits/sec, BW Unreserved[5]: 1166000 bits/sec
BW Unreserved[6]: 1166000 bits/sec, BW Unreserved[7]: 1153000 bits/sec
Table 67 describes the significant fields shown in the display.
Table 67 show isis database verbose Field Descriptions
Field
|
Description
|
LSPID
|
Link-state packet (LSP) identifier. The first six octets form the System ID of the router that originated the LSP.
The next octet is the pseudonode ID. When this byte is zero, the LSP describes links from the system. When it is nonzero, the LSP is a pseudonode LSP. This is similar to a router LSA in Open Shortest Path First (OSPF); the LSP describes the state of the originating router. For each LAN, the designated router for that LAN creates and floods a pseudonode LSP that describes all systems attached to that LAN.
The last octet is the LSP number. If all the data cannot fit into a single LSP, the LSP is divided into multiple LSP fragments. Each fragment has a different LSP number. An asterisk (*) indicates that the system issuing this command originated the LSP.
|
LSP Seq Num
|
LSP sequence number that allows other systems to determine if they received the latest information from the source.
|
LSP Checksum
|
Checksum of the entire LSP packet.
|
LSP Holdtime
|
Amount of time that the LSP remains valid (in seconds). An LSP hold time of zero indicates that this LSP was purged and is being removed from all routers' link-state databases (LSDBs). The value indicates how long the purged LSP will stay in the LSDB before it is completely removed.
|
ATT
|
Attach bit. This bit indicates that the router is also a Level 2 router, and it can reach other areas. Level 1 routers use the Attach bit to find the closest Level 2 router. They install a default route to the closest Level 2 router.
|
P
|
P bit. This bit detects if the IS can repair area partitions. Cisco and other vendors do not support area partition repair.
|
OL
|
Overload bit. This bit determines if the IS is congested. If the overload bit is set, other routers do not use this system as a transit router when they calculate routes. Only packets for destinations directly connected to the overloaded router are sent to this router.
|
Area Address
|
Reachable area addresses from the router. For Level 1 LSPs, these are the area addresses configured manually on the originating router. For Level 2 LSPs, these are all the area addresses for the area to which this router belongs.
|
NLPID
|
Network Layer Protocol identifier.
|
Hostname
|
Hostname of the node.
|
Router ID
|
Traffic engineering router identifier for the node.
|
IP Address
|
IPv4 address for the interface.
|
Metric
|
IS-IS metric for the cost of the adjacency between the originating router and the advertised neighbor, or the metric of the cost to get from the advertising router to the advertised destination (which can be an IP address, an end system (ES), or a connectionless network service [CLNS] prefix).
|
Affinity
|
Link attribute flags that are being flooded.
|
Physical BW
|
Link bandwidth capacity (in bits per second).
|
Reservable BW
|
Amount of reservable bandwidth on this link.
|
BW Unreserved
|
Amount of bandwidth that is available for reservation.
|
The following example includes a route tag:
Router# show isis database verbose
IS-IS Level-1 Link State Database:
LSPID LSP Seq Num LSP Checksum LSP Holdtime ATT/P/OL
dasher.00-00 0x000000F8 0xE57B 518 1/0/0
Metric: 10 IP 172.16.170.0/24
Metric: 10 IP 10.0.3.0/24
Metric: 10 IP 10.0.3.3/30
Metric: 10 IS-Extended dasher.02172.19.170.0/24
Metric: 20 IP-Interarea 10.1.1.1/32
Metric: 20 IP-Interarea 192.168.0.6/32
Related Commands
Command
|
Description
|
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 advertisements
|
Displays the last flooded record from MPLS traffic engineering.
|
show isis mpls traffic-eng tunnel
|
Displays information about tunnels considered in the IS-IS next hop calculation.
|
show isis mpls ldp
To display synchronization and autoconfiguration information about interfaces belonging to Intermediate System-to-Intermediate System (IS-IS) processes, use the show isis mpls ldp command in privileged EXEC mode.
show isis [process-tag] mpls ldp [interface interface]
Syntax Description
process-tag
|
(Optional) Process ID. Displays information only for the specified routing process.
|
interface interface
|
(Optional) Defines the interface for which Label Distribution Protocol (LDP)-Interior Gateway Protocol (IGP) synchronization and LDP autoconfiguration information will be displayed.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modifications
|
12.0(32)SY
|
This command was introduced.
|
12.2(33)SRB
|
This command was integrated into Cisco IOS Release 12.2(33)SRB.
|
12.2(33)SB
|
This command was integrated into Cisco IOS Release 12.2(33)SB.
|
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 ldp
Interface: POS0/2; ISIS tag null enabled
This command returns information for interfaces that are configured for IS-IS, which are indicated by the message "ISIS is UP" on the interface.
Table 68 describes the significant fields shown in the display.
Table 68 show isis mpls ldp Field Descriptions
Field
|
Description
|
AUTOCONFIG Information
|
LDP enabled—Indicates whether LDP autoconfiguration is enabled on this interface. Value is YES or NO.
|
SYNC Information
|
Provides synchronization information.
• Required—Indicates whether synchronization is required on the interface.
• Achieved—Indicates whether synchronization was achieved with LDP. If IS-IS was configured on an interface but synchronization is not achieved, the Achieved field indicates NO. The Required field still indicates YES.
• IGP Delay—Indicates whether the IS-IS process must wait for synchronization with LDP before bringing up the interface adjacency.
• Holddown time—Valid values are Finite or Infinite. The finite value is equal to the hold-down delay that you configured using the mpls ldp igp sync holddown command. If this field indicates Infinite, hold-down time was not configured. Therefore, IS-IS waits until synchronization is achieved before bringing adjacency UP.
The Holddown time field is significant only if the IGP Delay field indicates YES.
• State—Indicates information about the state of synchronization on the interface. If synchronization is achieved, the output shows the following:
– SYNC achieved—Synchronization was required and has been achieved.
If synchronization is not achieved, the output shows one of the following:
– Holding down until SYNC—No hold-down timer was configured, so IS-IS continues to hold down adjacency until synchronization is achieved.
– Holding down with timer—A hold-down timer was configured and IS-IS is holding down adjacency until the timer, indicated in the IGP Delay field, expires.
– Maximum metric in effect—Although synchronization was not achieved, the IGP brought up adjacency with the maximum metric.
|
Related Commands
Command
|
Description
|
mpls ldp autoconfig
|
Globally enables LDP autoconfiguration on all interfaces that belong to an OSPF or IS-IS process.
|
mpls ldp sync
|
Enables MPLS LDP-IGP synchronization on interfaces for an OSPF process or an IS-IS process.
|
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 EXEC
Command History
Release
|
Modification
|
12.0(5)S
|
This command was introduced.
|
12.1(3)T
|
This command was integrated into Cisco IOS Release 12.1(3)T.
|
12.0(10)ST
|
This command was integrated into Cisco IOS Release 12.0(10)ST.
|
12.2(28)SB
|
This command was integrated into Cisco IOS Release 12.2(28)SB.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
Examples
The following is sample output from the show isis mpls traffic-eng adjacency-log command:
Router# show isis mpls traffic-eng adjacency-log
When Neighbor ID IP Address Interface Status Level
04:52:52 0000.0024.0004.02 0.0.0.0 Et0/2 Up level-1
04:52:50 0000.0026.0001.00 172.16.1.2 PO1/0/0 Up level-1
04:52:37 0000.0024.0004.02 10.0.0.0 Et0/2 Up level-1
Table 69 describes the significant fields shown in the display.
Table 69 show isis mpls traffic-eng adjacency-log Field Descriptions
Field
|
Description
|
When
|
Amount of time since the entry was recorded in the log.
|
Neighbor ID
|
Identification value of the neighbor.
|
IP Address
|
Neighbor IPv4 address.
|
Interface
|
Interface from which a neighbor is learned.
|
Status
|
Up (active) or Down (disconnected).
|
Level
|
Routing level.
|
Related Commands
Command
|
Description
|
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 EXEC
Command History
Release
|
Modification
|
12.0(5)S
|
This command was introduced.
|
12.1(3)T
|
This command was integrated into Cisco IOS Release 12.1(3)T.
|
12.0(10)ST
|
This command was integrated into Cisco IOS Release 12.0(10)ST.
|
12.2(28)SB
|
This command was integrated into Cisco IOS Release 12.2(28)SB.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
Examples
The following is sample output from the show isis mpls traffic-eng advertisements command:
Router# show isis mpls traffic-eng advertisements
Neighbor System ID:dtp-5.01 (broadcast link)
Interface IP address:172.21.39.5
Neighbor IP Address:0.0.0.0
Physical BW:10000000 bits/sec
Reservable BW:1166000 bits/sec
BW unreserved[0]:1166000 bits/sec, BW unreserved[1]:1166000 bits/sec
BW unreserved[2]:1166000 bits/sec, BW unreserved[3]:1166000 bits/sec
4]:1166000 bits/sec, BW unreserved[5]:1166000 bits/sec
BW unreserved[6]:1166000 bits/sec, BW unreserved[7]:1153000 bits/sec
Table 70 describes the significant fields shown in the display.
Table 70 show isis mpls traffic-eng advertisements Field Descriptions
Field
|
Description
|
System ID
|
Identification value for the local system in the area.
|
Router ID
|
MPLS traffic engineering router ID.
|
Link Count
|
Number of links that MPLS traffic engineering advertised.
|
Neighbor System ID
|
Identification value for the remote system in an area.
|
Interface IP address
|
IPv4 address of the interface.
|
Neighbor IP Address
|
IPv4 address of the neighbor.
|
Admin. Weight
|
Administrative weight associated with this link.
|
Physical BW
|
Link bandwidth capacity (in bits per second).
|
Reservable BW
|
Amount of reservable bandwidth on this link.
|
BW unreserved
|
Amount of bandwidth that is available for reservation.
|
Affinity Bits
|
Link attribute flags being flooded.
|
Related Commands
Command
|
Description
|
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 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
Release
|
Modification
|
12.0(5)S
|
This command was introduced.
|
12.1(3)T
|
This command was integrated into Cisco IOS Release 12.1(3)T.
|
12.0(10)ST
|
This command was integrated into Cisco IOS Release 12.0(10)ST.
|
12.2(28)SB
|
This command was integrated into Cisco IOS Release 12.2(28)SB.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
Examples
The following is sample output from the show isis mpls traffic-eng tunnel command:
Router# show isis mpls traffic-eng tunnel
Station Id Tunnel Name Bandwidth Nexthop Metric Mode
kangpa-router1.00 Tunnel1022 3333 10.2.2.2 -3 Relative
Tunnel1021 10000 10.2.2.2 11 Absolute
tomklong-route.00 Tunnel1031 10000 172.17.3.3 -1 Relative
Tunnel1032 10000 172.17.3.3
Table 71 describes the significant fields shown in the display.
Table 71 show isis mpls traffic-eng tunnel Field Descriptions
Field
|
Description
|
Station Id
|
Name or system ID of the MPLS traffic engineering tailend router.
|
Tunnel Name
|
Name of the MPLS traffic engineering tunnel interface.
|
Bandwidth
|
MPLS traffic engineering specified bandwidth of the tunnel.
|
Nexthop
|
MPLS traffic engineering destination IP address of the tunnel.
|
Metric
|
MPLS traffic engineering metric of the tunnel.
|
Mode
|
MPLS traffic engineering metric mode of the tunnel. It can be relative or absolute.
|
Related Commands
Command
|
Description
|
show mpls traffic-eng autoroute
|
Displays tunnels that are announced to IGP, including interface, destination, and bandwidth.
|
show issu clients
To display a list of the current In Service Software Upgrade (ISSU) clients—that is, the network applications and protocols supported by ISSU—use the 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 EXEC
Command History
Release
|
Modification
|
| |
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 clients
Client_ID = 2, Client_Name = ISSU Proto client, Entity_Count = 1
Client_ID = 3, Client_Name = ISSU RF, Entity_Count = 1
Client_ID = 4, Client_Name = ISSU CF client, Entity_Count = 1
Client_ID = 5, Client_Name = ISSU Network RF client, Entity_Count = 1
Client_ID = 7, Client_Name = ISSU CONFIG SYNC, Entity_Count = 1
Client_ID = 8, Client_Name = ISSU ifIndex sync, Entity_Count = 1
Client_ID = 9, Client_Name = ISSU IPC client, Entity_Count = 1
Client_ID = 10, Client_Name = ISSU IPC Server client, Entity_Count = 1
Client_ID = 11, Client_Name = ISSU Red Mode Client, Entity_Count = 1
Client_ID = 12, Client_Name = ISSU EHSA services client, Entity_Count = 1
Client_ID = 100, Client_Name = ISSU rfs client, Entity_Count = 1
Client_ID = 110, Client_Name = ISSU ifs client, Entity_Count = 1
Client_ID = 1001, Client_Name = OC3POS-6, Entity_Count = 4
Client_ID = 1002, Client_Name = C10K ATM, Entity_Count = 1
Client_ID = 1003, Client_Name = C10K CHSTM1, Entity_Count = 1
Client_ID = 1004, Client_Name = C10K CT3, Entity_Count = 1
Client_ID = 1005, Client_Name = C10K GE, Entity_Count = 1
Client_ID = 1006, Client_Name = C10K ET, Entity_Count = 1
Client_ID = 1007, Client_Name = C10K CHE1T1, Entity_Count = 1
Client_ID = 1009, Client_Name = C10K MFE, Entity_Count = 1
Client_ID = 1010, Client_Name = C10K APS, Entity_Count = 1
Client_ID = 1013, Client_Name = C10K CARD OIR, Entity_Count = 1
Client_ID = 2002, Client_Name = CEF Push ISSU client, Entity_Count = 1
Client_ID = 2003, Client_Name = ISSU XDR client, Entity_Count = 1
Client_ID = 2004, Client_Name = ISSU SNMP client, Entity_Count = 1
Client_ID = 2005, Client_Name = ISSU HDLC Client, Entity_Count = 1
Client_ID = 2006, Client_Name = ISSU QoS client, Entity_Count = 1
Client_ID = 2007, Client_Name = ISSU LSD Label Mgr HA Client, Entity_Count = 1
Client_ID = 2008, Client_Name = ISSU Tableid Client, Entity_Count = 1
Client_ID = 2009, Client_Name = ISSU MPLS VPN Client, Entity_Count = 1
Client_ID = 2010, Client_Name = ARP HA, Entity_Count = 1
Client_ID = 2011, Client_Name = ISSU LDP Client, Entity_Count = 1
Client_ID = 2012, Client_Name = ISSU HSRP Client, Entity_Count = 1
Client_ID = 2013, Client_Name = ISSU ATM Client, Entity_Count = 1
Client_ID = 2014, Client_Name = ISSU FR Client, Entity_Count = 1
Client_ID = 2015, Client_Name = ISSU REDSSOC client, Entity_Count = 1
Client_ID = 2019, Client_Name = ISSU TCP client, Entity_Count = 1
Client_ID = 2020, Client_Name = ISSU BGP client, Entity_Count = 1
Client_ID = 2021, Client_Name = XDR Int Priority ISSU client, Entity_Count = 1
Client_ID = 2022, Client_Name = XDR Proc Priority ISSU client, Entity_Count = 1
Client_ID = 2023, Client_Name = FIB HWIDB ISSU client, Entity_Count = 1
Client_ID = 2024, Client_Name = FIB IDB ISSU client, Entity_Count = 1
Client_ID = 2025, Client_Name = FIB HW subblock ISSU client, Entity_Count = 1
Client_ID = 2026, Client_Name = FIB SW subblock ISSU client, Entity_Count = 1
Client_ID = 2027, Client_Name = Adjacency ISSU client, Entity_Count = 1
Client_ID = 2028, Client_Name = FIB IPV4 ISSU client, Entity_Count = 1
Client_ID = 2030, Client_Name = MFI Pull ISSU client, Entity_Count = 1
Client_ID = 2031, Client_Name = MFI Push ISSU client, Entity_Count = 1
Client_ID = 2051, Client_Name = ISSU CCM Client, Entity_Count = 1
Client_ID = 2052, Client_Name = ISSU PPP SIP CCM Client, Entity_Count = 1
Client_ID = 2054, Client_Name = ISSU process client, Entity_Count = 1
Client_Name = ISSU Proto client
Client_Name = ISSU CF client
Client_Name = ISSU Network RF client
Client_Name = ISSU CONFIG SYNC
Client_Name = ISSU ifIndex sync
Client_Name = ISSU IPC client
Client_Name = ISSU IPC Server client
Client_Name = ISSU Red Mode Client
Client_Name = ISSU EHSA services client
Table 72 describes the significant fields shown in the display.
Table 72 show issu clients Field Descriptions
Field
|
Description
|
Client_ID
|
The identification number used by ISSU for that client.
|
Client_Name
|
A character string describing the client.
"Base Clients" are a subset, which includes:
• Inter-Process Communications (IPC)
• Redundancy Framework (RF)
• Checkpoint Facility (CF)
• Cisco Express Forwarding
• Network RF (for IDB stateful switchover)
• EHSA Services (including ifIndex)
• Configuration Synchronization.
|
Entity_Count
|
The number of entities within this client. An entity is a logical group of sessions with some common attributes.
|
Related Commands
Command
|
Description
|
show issu message types
|
Displays the formats, versions, and size of ISSU messages supported by a particular client.
|
show issu negotiated
|
Displays results of a negotiation that occurred concerning message versions or client capabilities.
|
show issu sessions
|
Displays detailed information about a particular ISSU client, including whether the client status is compatible for the impending software upgrade.
|
show issu entities
To display information about entities within one or more In Service Software Upgrade (ISSU) clients, use the show issu entities command in user EXEC or privileged EXEC mode.
show issu entities [client_id]
Note
An entity is a logical group of sessions that possess some common attributes.
Syntax Description
client_id
|
(Optional) The identification number of a single ISSU client.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
| |
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 2008
Entity_ID = 1, Entity_Name = Tableid Entity :
MsgType MsgGroup CapType CapEntry CapGroup
Count Count Count count Count
Table 73 show issu entities Field Descriptions
Field
|
Description
|
Client_ID
|
The identification number used by ISSU for the specified client.
|
Entity_ID
|
The identification number used by ISSU for each entity within this client.
|
Entity_Name
|
A character string describing the entity.
|
MsgType Count
|
The number of message types within the identified entity.
|
MsgGroup Count
|
The number of message groups within the identified entity. A message group is a list of message types.
|
CapType Count
|
The number of capability types within the identified entity.
|
CapEntry Count
|
The number of capability entries within the identified entity. A capability entry is a list of all mutually dependent capability types within a particular client session and, optionally, other capability types belonging to that client session.
|
CapGroup Count
|
The number of capability groups within the identified entity. A capability group is a list of capability entries given in priority sequence.
|
Related Commands
Command
|
Description
|
show issu clients
|
Lists the current ISSU clients—that is, the applications and protocols on this network supported by ISSU.
|
show issu sessions
|
Displays detailed information about a particular ISSU client—including whether the client status for the impending software upgrade is COMPATIBLE.
|
show issu message types
To display formats ("types"), versions, and maximum packet size of the In Service Software Upgrade (ISSU) messages supported by a particular client, use the show issu message types command in user EXEC or privileged EXEC mode.
show issu message types client-id
Syntax Description
client-id
|
The identification number used by ISSU for a client application.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
| |
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 2009
Client_ID = 2009, Entity_ID = 1 :
Message_Type = 1, Version_Range = 1 ~ 1
Message_Ver = 1, Message_Mtu = 32
Table 74 describes the significant fields shown in the display.
Table 74 show issu message types Field Descriptions
Field
|
Description
|
Client_ID
|
The identification number used by ISSU for this client.
|
Entity_ID
|
The identification number used by ISSU for this entity.
|
Message_Type
|
An identification number that uniquely identifies the format used in the ISSU messages conveyed between the two endpoints.
|
Version_Range
|
The lowest and highest message-version numbers contained in the client application.
|
Message_Ver
|
Message version. Because each client application contains one or more versions of its messages, ISSU needs to discover these versions and negotiate between the new and old system software which version to use in its preparatory communications.
|
Message_Mtu
|
Maximum size (in bytes) of the transmitted message.
A value of 0 means there is no restriction on size; fragmentation and reassembly are therefore being handled in a manner transparent to the ISSU infrastructure.
|
Related Commands
Command
|
Description
|
show issu clients
|
Lists the current ISSU clients—that is, the applications on this network supported by ISSU.
|
show issu negotiated
|
Displays results of a negotiation that occurred concerning message versions or client capabilities.
|
show issu sessions
|
Displays detailed information about a particular ISSU client, including whether the client status is compatible for the impending software upgrade.
|
show issu negotiated
To display details of the session's negotiation about message version or client capabilities, use the show issu negotiated command in user EXEC or privileged EXEC mode.
show issu negotiated {version | capability} session-id
Syntax Description
version
|
Displays results of a negotiation about versions of the messages exchanged during the specified session, between the active and standby endpoints.
|
capability
|
Displays results of a negotiation about the client application's capabilities for the specified session.
|
session-id
|
The number used by In Service Software Upgrade (ISSU) to identify a particular communication session between the active and the standby devices.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
| |
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 39
Message_Type = 1, Negotiated_Version = 1, Message_MTU = 32
Table 75 describes the significant fields shown in the display.
Table 75 show issu negotiated version Field Descriptions
Field
|
Description
|
Session_ID
|
The identification number of the session being reported on.
|
Message_Type
|
An identification number that uniquely identifies the format that was used by the ISSU messages conveyed between the two endpoints.
|
Negotiated_Version
|
The message version that was decided upon, for use during the software upgrade process.
|
Message_Mtu
|
Maximum size (in bytes) of the transmitted message.
A value of 0 means there is no restriction on size. In that case, fragmentation and reassembly are handled in a manner transparent to the ISSU infrastructure.
|
The following example displays the results of a negotiation about the client application's capabilities:
router# show issu negotiated capability 39
Table 76 describes the significant fields shown in the display.
Table 76 show issu negotiated capability Field Descriptions
Field
|
Description
|
Session_ID
|
The identification number of the session being reported on.
|
Negotiated_Cap_Entry
|
A numeral that stands for a list of the negotiated capabilities in the specified client session.
|
Related Commands
Command
|
Description
|
show issu clients
|
Lists the current ISSU clients—that is, the applications on this network supported by ISSU.
|
show issu message types
|
Displays the formats, versions, and maximum packet size of ISSU messages supported by a particular client.
|
show issu sessions
|
Displays detailed information about a particular ISSU client, including whether the client status is compatible for the impending software upgrade.
|
show issu sessions
To display detailed information about a particular In Service Software Upgrade (ISSU) client—including whether the client status for the impending software upgrade is compatible—use the show issu sessions command in user EXEC or privileged EXEC mode.
show issu sessions client-id
Syntax Description
client-id
|
The identification number used by ISSU for the client.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
| |
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 2011
Client_ID = 2011, Entity_ID = 1 :
*** Session_ID = 46, Session_Name = LDP Session :
Peer Peer Negotiate Negotiated Cap Msg Session
UniqueID Sid Role Result GroupID GroupID Signature
4 34 PRIMARY COMPATIBLE 1 1 0
Negotiation Session Info for This Message Session:
Nego_Session_Name = LDP Session
Table 77 describes the significant fields shown in the display.
Table 77 show issu sessions Field Descriptions
Field
|
Description
|
Client_ID
|
The identification number used by ISSU for that client.
|
Entity_ID
|
The identification number used by ISSU for each entity within this client.
|
Session_ID
|
The identification number used by ISSU for this session.
|
Session_Name
|
A character string describing the session.
|
Peer UniqueID
|
An identification number used by ISSU for a particular endpoint, such as a Route Processor or line card (could be a value based on slot number, for example).
The peer that has the smaller unique_ID becomes the Primary (initiating) side in the capability and message version negotiations.
|
Peer Sid
|
Peer session ID.
|
Negotiate Role
|
Negotiation role of the endpoint: either PRIMARY (in which case the device initiates the negotiation) or PASSIVE (in which case the device responds to a negotiation initiated by the other device).
|
Negotiated Result
|
The features ("capabilities") of this client's new software were found to be either COMPATIBLE or INCOMPATIBLE with the intended upgrade process.
("Policy" means that an override of the negotiation result has been allowed by the software. Likewise, "no policy" means that no such override is present to be invoked).
|
Cap GroupID
|
Capability group ID: the identification number used for a list of distinct functionalities that the client application contains.
|
Msg GroupID
|
Message group ID: the identification number used for a list of formats employed when conveying information between the active device and the standby device.
|
Session Signature
|
Session signature: a unique ID to identify a current session in a shared negotiation scenario.
|
Nego_Session_ID
|
Negotiation session ID: the identification number used by ISSU for this negotiation session.
|
Nego_Session_Name
|
Negotiation session name: a character string describing this negotiation session.
|
Transport_Mtu
|
Maximum packet size (in bytes) of the ISSU messages conveyed between the two endpoints.
A value of 0 means there is no restriction on size; in this case, fragmentation and reassembly then are handled in a manner transparent to the ISSU infrastructure.
|
Related Commands
Command
|
Description
|
show issu clients
|
Lists the current ISSU clients—that is, the applications on this network supported by ISSU.
|
show issu message types
|
Displays the formats, versions, and maximum packet size of ISSU messages supported by a particular client.
|
show issu negotiated
|
Displays results of a negotiation that occurred concerning message versions or client capabilities.
|
show mpls atm-ldp bindings
Note
Effective with Cisco IOS Release 12.4(20)T, the show mpls atm-ldp bindings command is not available in Cisco IOS software.
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
network
|
(Optional) Defines the destination network number.
|
mask
|
(Optional) Defines the network mask in the form A.B.C.D (destination prefix).
|
length
|
(Optional) Defines the mask length (1 to 32).
|
local-label vpi vci
|
(Optional) Selects the label values assigned by this router. The virtual path identifier (VPI) range is 0 to 4095. The virtual channel identifier (VCI) range is 0 to 65535.
|
remote-label vpi vci
|
(Optional) Selects the label values assigned by the other router. VPI range is 0 to 4095. VCI range is 0 to 65535.
|
neighbor interface
|
(Optional) Selects the label values assigned by the neighbor on a specified interface.
|
Command Default
The entire ATM label binding database is displayed if no optional arguments or keywords are specified.
Note
To display information about entries in the label binding database for interfaces other than ATM interfaces, use the show mpls ip binding command.
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
11.1CT
|
This command was introduced.
|
12.0(10)ST
|
This command was modified to use Multiprotocol Label Switching (MPLS) Internet Engineering Task Force (IETF) command syntax and terminology.
|
12.0(14)ST
|
This command was integrated into Cisco IOS Release 12.0(14)ST.
|
12.1(2)T
|
This command was integrated into Cisco IOS Release 12.1(2)T.
|
12.1(8a)E
|
This command was integrated into Cisco IOS Release 12.1(8a)E.
|
12.2(2)T
|
This command was integrated into Cisco IOS Release 12.2(2)T.
|
12.2(4)T
|
The VPI range of values for this command was extended to 4095.
|
12.2(8)T
|
This command was integrated into Cisco IOS Release 12.2(8)T.
|
12.0(21)ST
|
This command was integrated into Cisco IOS Release 12.0(21)ST.
|
12.0(22)S
|
This command was integrated into Cisco IOS Release 12.0(22)S.
|
12.0(23)S
|
This command was integrated into Cisco IOS Release 12.0(23)S.
|
12.2(13)T
|
This command was integrated into Cisco IOS Release 12.2(13)T.
|
12.2(14)S
|
This command was integrated into Cisco IOS Release 12.2(14)S.
|
12.2(28)SB
|
This command was integrated into Cisco IOS Release 12.2(28)SB and implemented on the Cisco 10000-PRE2 router.
|
12.4(20)T
|
This command was removed.
|
Usage Guidelines
The ATM label binding database contains entries for label virtual circuits (VCs) on label-controlled (LC)-ATM interfaces. Command output can show a summary of entries from the entire database, or the output can be limited to a subset of entries based on the following:
•
Specific prefix
•
Specific VC label value
•
Specific assigning interface
Note
This command displays ATM label bindings learned by the Label Distribution Protocol (LDP) or Tag Distribution Protocol (TDP). TDP is not supported for LDP features in Cisco IOS 12.0(30)S and later releases, 12.2(27)SBC and later 12.2S releases, and 12.3(14)T and later releases.
Note
The show mpls ip binding command includes the output generated by the show mpls atm-ldp bindings command and information about label bindings for packet interfaces.
Examples
The following is sample output from the show mpls atm-ldp bindings command:
Router# show mpls atm-ldp bindings
Destination: 10.24.0.0/24
Tailend Router ATM1/0.1 1/39 Active, VCD=3
Destination: 10.15.0.15/32
Tailend Router ATM1/0.1 1/33 Active, VCD=4
Headend Router ATM1/0.1 (2 hops) 1/34 Active, VCD=810
The following is sample output from the show mpls atm-ldp bindings command on an ATM switch:
Router# show mpls atm-ldp bindings
Destination: 172.16.0.0/16
Tailend Switch ATM0/0/3 1/35 Active -> Terminating Active
Transit ATM0/0/3 1/33 Active -> ATM0/1/1 1/33 Active
Table 78 describes the significant fields shown in the displays.
Table 78 show mpls atm-ldp bindings Field Descriptions
Field
|
Description
|
Destination
|
Destination (network/mask).
|
Headend Router
Tailend Router
Tailend Switch
Transit
|
Indicates types of VCs. Options are the following:
• Tailend—VC that terminates at this platform
• Headend—VC that originates at this router
• Transit—VC that passes through a switch
|
ATM1/0.1
|
ATM interface.
|
1/35
|
VPI/VCI.
|
Active
|
Indicates VC state. Options include the following:
• Active—Set up and working
• Bindwait—Waiting for a response
• Remote Resource Wait—Waiting for resources (VPI/VCI space) to be available on the downstream device
• Parent Wait—Transit VC input side waiting for output side to become active
|
VCD=3
|
Virtual circuit descriptor number.
|
Related Commands
Command
|
Description
|
show mpls ip binding
|
Displays specified information about label bindings learned by the MPLS LDP.
|
show mpls atm-ldp bindwait
Note
Effective with Cisco IOS Release 12.4(20)T, the show mpls atm-ldp bindwait command is not available in Cisco IOS software.
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
Release
|
Modification
|
12.0(5)T
|
This command was introduced.
|
12.2(4)T
|
This command was modified to use MPLS Internet Engineering Task Force (IETF) command syntax and terminology.
|
12.2(8)T
|
This command was integrated into Cisco IOS Release 12.2(8)T.
|
12.0(21)ST
|
This command was integrated into Cisco IOS Release 12.0(21)ST.
|
12.0(22)S
|
This command was integrated into Cisco IOS Release 12.0(22)S.
|
12.0(23)S
|
This command was integrated into Cisco IOS Release 12.0(23)S.
|
12.2(13)T
|
This command was integrated into Cisco IOS Release 12.2(13)T.
|
12.2(14)S
|
This command was integrated into Cisco IOS Release 12.2(14)S.
|
12.4(20)T
|
This command was removed.
|
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 bindwait
Waiting for bind on ATM1/0.2
10.3.3.1/32 10.3.3.1/32 10.3.3.2/32
10.3.3.2/32 10.3.3.3/32 10.3.3.3/32
10.3.3.4/32 10.3.3.4/32 10.3.3.5/32
10.3.3.5/32 10.3.3.6/32 10.3.3.6/32
10.3.3.7/32 10.3.3.7/32 10.3.3.8/32
10.3.3.8/32 10.3.3.9/32 10.3.3.9/32
If there are no bindings waiting for label assignments from the remote MPLS ATM switch, this command does not display any output.
Related Commands
Command
|
Description
|
show mpls atm-ldp bindings
|
Displays specified entries from the ATM label binding database.
|
show mpls atm-ldp capability
Note
Effective with Cisco IOS Release 12.4(20)T, the show mpls atm-ldp capability command is not available in Cisco IOS software.
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
Release
|
Modification
|
11.1CT
|
This command was introduced.
|
12.0(10)ST
|
This command was modified to use MPLS Internet Engineering Task Force (IETF) command syntax and terminology.
|
12.0(14)ST
|
This command was integrated into Cisco IOS Release 12.0(14)ST.
|
12.1(2)T
|
This command was integrated into Cisco IOS Release 12.1(2)T.
|
12.1(8a)E
|
This command was integrated into Cisco IOS Release 12.1(8a)E.
|
12.2(2)T
|
This command was integrated into Cisco IOS Release 12.2(2)T.
|
12.2(4)T
|
This command was integrated into Cisco IOS Release 12.2(4)T.
|
12.2(8)T
|
This command was integrated into Cisco IOS Release 12.2(8)T.
|
12.0(21)ST
|
This command was integrated into Cisco IOS Release 12.0(21)ST.
|
12.0(22)S
|
This command was integrated into Cisco IOS Release 12.0(22)S.
|
12.0(23)S
|
This command was integrated into Cisco IOS Release 12.0(23)S.
|
12.2(13)T
|
This command was integrated into Cisco IOS Release 12.2(13)T.
|
12.2(14)S
|
This command was integrated into Cisco IOS Release 12.2(14)S.
|
12.2(28)SB
|
This command was integrated into Cisco IOS Release 12.2(28)SB and implemented on the Cisco 10000-PRE2 router.
|
12.4(20)T
|
This command was removed.
|
Usage Guidelines
When two label switch routers (LSRs) establish an LDP session, they negotiate parameters for the session, such as the range of virtual path identifiers (VPIs) and virtual channel identifiers (VCIs) that will be used as labels.
This command displays the MPLS ATM capabilities negotiated by LDP or the Tag Distribution Protocol (TDP).
Note
TDP is not supported for LDP features in Cisco IOS 12.0(30)S and later releases, 12.2(27)SBC and later 12.2S releases, and 12.3(14)T and later releases.
Examples
The following is sample output from the show mpls atm-ldp capability command:
Router# show mpls atm-ldp capability
VPI VCI Alloc Odd/Even VC Merge
ATM0/1/0 Range Range Scheme Scheme IN OUT
Negotiated [100 - 101] [33 - 1023] UNIDIR - -
Local [100 - 101] [33 - 16383] UNIDIR EN EN
Peer [100 - 101] [33 - 1023] UNIDIR - -
VPI VCI Alloc Odd/Even VC Merge
ATM0/1/1 Range Range Scheme Scheme IN OUT
Negotiated [201 - 202] [33 - 1023] BIDIR - -
Local [201 - 202] [33 - 16383] UNIDIR ODD NO NO
Peer [201 - 202] [33 - 1023] BIDIR EVEN - -
Table 79 describes the significant fields shown in the display.
Table 79 show mpls atm-ldp capability Field Descriptions
Field
|
Description
|
VPI Range
|
Minimum and maximum numbers of VPIs supported on this interface.
|
VCI Range
|
Minimum and maximum numbers of VCIs supported on this interface.
|
Alloc Scheme
|
Indicates the applicable allocation scheme, as follows:
• UNIDIR—Unidirectional capability indicates that the peer can, within a single VPI, support binding of the same VCI to different prefixes on different directions of the link.
• BIDIR—Bidirectional capability indicates that within a single VPI, a single VCI can appear in one binding only. In this case, one peer allocates bindings in the even VCI space, and the other in the odd VCI space. The system with the lower LDP identifier assigns even-numbered VCIs.
The negotiated allocation scheme is UNIDIR, only if both peers have UNIDIR capability. Otherwise, the allocation scheme is BIDIR.
Note These definitions for unidirectional and bidirectional are consistent with normal ATM usage of the terms; however, they are exactly opposite from the definitions for them in the IETF LDP specification.
|
Odd/Even Scheme
|
Indicates whether the local device or the peer is assigning an odd- or even-numbered VCI when the negotiated scheme is BIDIR. It does not display any information when the negotiated scheme is UNIDIR.
|
VC Merge
|
Indicates the type of virtual circuit (VC) merge support available on this interface. There are two possibilities, as follows:
• IN—Indicates the input interface merge capability. IN accepts the following values:
– EN—The hardware interface supports VC merge, and VC merge is enabled on the device.
– DIS—The hardware interface supports VC merge and VC merge is disabled on the device.
– NO—The hardware interface does not support VC merge.
• OUT—Indicates the output interface merge capability. OUT accepts the same values as the input merge side.
The VC merge capability is meaningful only on ATM switches. This capability is not negotiated.
|
Negotiated
|
Indicates the set of options that both LDP peers have agreed to share on this interface. For example, the VPI or VCI allocation on either peer remains within the negotiated range.
|
Local
|
Indicates the options supported locally on this interface.
|
Peer
|
Indicates the options supported by the remote LDP peer on this interface.
|
Related Commands
Command
|
Description
|
mpls ldp atm vc-merge
|
Controls whether the vc-merge (multipoint-to-point) is supported for unicast label VCs.
|
sshow mpls atm-ldp summary
Note
Effective with Cisco IOS Release 12.4(20)T, the show mpls atm-ldp summary command is not available in Cisco IOS software.
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
Release
|
Modification
|
11.1CT
|
This command was introduced.
|
12.0(10)ST
|
This command was modified to use Multiprotocol Label Switching (MPLS) Internet Engineering Task Force (IETF) command syntax and terminology.
|
12.0(14)ST
|
This command was integrated into Cisco IOS Release 12.0(14)ST.
|
12.1(2)T
|
This command was integrated into Cisco IOS Release 12.1(2)T.
|
12.1(8a)E
|
This command was integrated into Cisco IOS Release 12.1(8a)E.
|
12.2(2)T
|
This command was integrated into Cisco IOS Release 12.2(2)T.
|
12.2(4)T
|
This command was integrated into Cisco IOS Release 12.2(4)T.
|
12.2(8)T
|
This command was integrated into Cisco IOS Release 12.2(8)T.
|
12.0(21)ST
|
This command was integrated into Cisco IOS Release 12.0(21)ST.
|
12.0(22)S
|
This command was integrated into Cisco IOS Release 12.0(22)S.
|
12.0(23)S
|
This command was integrated into Cisco IOS Release 12.0(23)S.
|
12.2(13)T
|
This command was integrated into Cisco IOS Release 12.2(13)T.
|
12.2(14)S
|
This command was integrated into Cisco IOS Release 12.2(14)S.
|
12.4(20)T
|
This command was removed.
|
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 summary
Total number of destinations: 406
ATM label bindings summary
interface total active local remote Bwait Rwait IFwait
ATM0/0/0 406 406 404 2 0 0 0
ATM0/0/1 406 406 3 403 0 0 0
Table 80 describes the significant fields shown in the display.
Table 80 show mpls atm-ldp summary Field Descriptions
Field
|
Description
|
Total number of destinations:
|
Number of known destination address prefixes.
|
interface
|
Name of an interface with associated ATM label bindings.
|
total
|
Total number of ATM labels on this interface.
|
active
|
Number of ATM labels in an "active" state that are ready to use for data transfer.
|
local
|
Number of ATM labels assigned by this label switch router (LSR) on this interface.
|
remote
|
Number of ATM labels assigned by the neighbor LSR on this interface.
|
Bwait
|
Number of bindings that are waiting for a label assignment from the neighbor LSR.
|
Rwait
|
Number of bindings that are waiting for resources (virtual path identifier [VPI] /virtual channel identifier [VCI] space) to be available on the downstream device.
|
IFwait
|
Number of bindings that are waiting for learned labels to be installed for switching use.
|
Related Commands
Command
|
Description
|
show isis database verbose
|
Displays the requested entries from the ATM LDP label binding database.
|
show mpls cos-map
Note
Effective with Cisco IOS Release 12.4(20)T, the show mpls cos-map command is not available in Cisco IOS software.
To display the quality of service (QoS) map used to assign a quantity of label virtual circuits and the associated class of service (CoS) for those virtual circuits, use the show mpls cos-map command in privileged EXEC mode.
show mpls cos-map [cos-map]
Syntax Description
cos-map
|
(Optional) Number specifying the QoS map to be displayed.
|
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
12.0(5)T
|
This command was introduced.
|
12.0(10)ST
|
This command was modified to match Multiprotocol Label Switching (MPLS) syntax and terminology.
|
12.2(2)T
|
This command was integrated into Cisco IOS Release 12.2(2)T.
|
12.2(25)S
|
The heading in the output was changed from tag-vc to label-vc.
|
12.2(28)SB
|
This command was integrated into Cisco IOS Release 12.2(28)SB.
|
12.4(20)T
|
This command was removed.
|
Usage Guidelines
Not entering a specific QoS number causes all QoS maps to be displayed.
Note
Cisco 10000 series routers do not use the show mpls cos-map command.
Examples
The following is sample output from the show mpls cos-map command:
Router# show mpls cos-map 2
Table 81 describes the significant fields shown in the display.
Table 81 show mpls cos-map Field Descriptions
Field
|
Description
|
cos-map
|
Configures a class map, which specifies how classes map to MPLS virtual circuits when they are combined with a prefix map.
|
class
|
The IP precedence.
|
Label-VC
|
An ATM virtual circuit that is set up through ATM label switch router (LSR) label distribution procedures.
|
Related Commands
Command
|
Description
|
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 EXEC
Command History
Release
|
Modification
|
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 mappings
Label Owner Route-Distinguisher Prefix Allocated
26 LDP 10.32.0.0 00:52:10
27 TE-MIDPT 10.30.0.2 00:52:06
28 LDP 10.33.0.0 00:52:10
In this example, the mpls export vpnv4 prefixes command was not configured. Therefore, the MPLS PAL table did not export a route distinguisher for the Border Gateway Protocol (BGP) application, and the associated prefix is exported as 0.0.0.0.
Table 82 describes the significant fields shown in the display.
Table 82 show mpls flow mappings Field Descriptions
Field
|
Description
|
Label
|
Value given to the MPLS label by the router.
|
Owner
|
MPLS application that allocated the label.
• LDP = Label Distribution Protocol
• BGP = Border Gateway Protocol
• TE-MIDT = Traffic engineering tunnel midpoint
|
Route-Distinguisher
|
Value (8-byte) that is concatenated with an IPv4 prefix to create a unique VPN IPv4 prefix.
|
Prefix
|
Prefix used by the router to route data to the destination address.
|
Allocated
|
System uptime at which the MPLS PAL mapping record was created.
|
The following is sample output from the show mpls flow mappings command if you previously entered the mpls export vpnv4 prefixes command:
# show mpls flow mappings
Label Owner Route-Distinguisher Prefix Allocated
17 LDP 10.33.0.0 00:58:03
19 TE-MIDPT 10.30.0.2 00:58:06
24 LDP 10.32.0.0 00:58:03
27 BGP 100:1 10.34.0.0 00:57:48
31 BGP 100:1 10.0.0.9 00:58:21
32 BGP 100:1 10.3.3.0 00:58:21
The 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 LDP
Label Owner Route-Distinguisher Prefix Allocated
17 LDP 10.33.0.0 00:58:03
24 LDP 10.32.0.0 00:58:03
Related Commands
Command
|
Description
|
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
vrf-name
|
Displays network layer reachability information (NLRI) associated with the named VRF.
|
ip-prefix/length
|
(Optional) IP prefix address (in dotted decimal format) and length of mask (0 to 32).
|
mask
|
(Optional) Destination network mask, in dotted decimal format.
|
detail
|
(Optional) Displays detailed information on the VRF routes.
|
output-modifiers
|
(Optional) For a list of associated keywords and arguments, use context-sensitive help.
|
Command Default
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.0(5)T
|
This command was introduced.
|
12.0(21)ST
|
This command was modified to reflect new Multiprotocol Label Switching (MPLS) Internet Engineering Taskforce (IETF) terminology and CLI command syntax and was integrated into Cisco IOS Release 12.0(21)ST.
|
12.0(22)S
|
This command was integrated into Cisco IOS Release 12.0(22)S.
|
12.0(23)S
|
This command was integrated into Cisco IOS Release 12.0(23)S.
|
12.2(13)T
|
This command was integrated into Cisco IOS Release 12.2(13)T.
|
12.2(14)S
|
This command was integrated into Cisco IOS Release 12.2(14)S.
|
12.2(22)S
|
The command output was modified so that directly connected VRF networks no longer display as aggregate; no label appears instead.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
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 detail
Local Outgoing Prefix Bytes tag Outgoing Next Hop
tag tag or VC or Tunnel Id switched interface
35 24 10.0.0.0/8[V] 0 Et0/0/4 10.0.0.1
MAC/Encaps=14/22, MRU=1496, Tag Stack{24 19}
00D006FEDBE100D0974988048847 0001800000013000
No output feature configured
Related Commands
Command
|
Description
|
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 privileged EXEC mode.
show mpls forwarding-table [network {mask | length} | labels label [- label] | interface interface
| next-hop address | lsp-tunnel [tunnel-id]] [vrf vrf-name] [detail]
Syntax Description
network
|
(Optional) Destination network number.
|
mask
|
IP address of the destination mask whose entry is to be shown.
|
length
|
Number of bits in the mask of the destination.
|
labels label - label
|
(Optional) Displays only entries with the specified local labels.
|
interface interface
|
(Optional) Displays only entries with the specified outgoing interface.
|
next-hop address
|
(Optional) Displays only entries with the specified neighbor as the next hop.
|
lsp-tunnel
|
(Optional) Displays only entries with the specified Label Switched Path (LSP) tunnel, or with all LSP tunnel entries.
|
tunnel-id
|
(Optional) Specifies the LSP tunnel for which to display entries.
|
vrf vrf-name
|
(Optional) Displays only entries with the specified VPN routing and forwarding (VRF) instance.
|
detail
|
(Optional) Displays information in long form (includes length of encapsulation, length of MAC string, maximum transmission unit (MTU), and all labels).
|
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
11.1CT
|
This command was introduced.
|
12.1(3)T
|
This command was updated with MPLS terminology and command syntax.
|
12.2(8)T
|
The command was modified to accommodate use of the MPLS experimental (EXP) level as a selection criterion for packet forwarding. The output display was modified to include a bundle adjacency field and exp (VCD) values when the optional detail keyword is specified.
|
12.0(22)S
|
IPv6 MPLS aggregate label and prefix information was added to the display.
|
12.2(14)S
|
This command was integrated into Cisco IOS Release 12.2(14)S.
|
12.0(27)S
|
The command output was modified to include explicit-null label information.
|
12.2(25)S
|
The output was changed in the following ways:
• The term "tag" was replaced with the term "label."
• The term "untagged" was replaced with the term "no label."
|
12.0(29)S
|
This command was integrated into Cisco IOS Release 12.0(29)S.
|
12.2(28)SB
|
This command was integrated into Cisco IOS Release 12.2(28)SB and implemented on the Cisco 10000 series routers.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2(33)SXH
|
The command output was modified for the Cisco IOS Software Modularity: MPLS Layer 3 VPNs feature to show the status of local labels in holdown. The status indicator showing that traffic is forwarded through an LSP tunnel is moved to the local label.
|
Examples
The following is sample output from the show mpls forwarding-table command:
Router# show mpls forwarding-table
Local Outgoing Prefix Bytes label Outgoing Next Hop
Label Label or VC or Tunnel Id switched interface
26 No Label 10.253.0.0/16 0 Et4/0/0 10.27.32.4
28 1/33 10.15.0.0/16 0 AT0/0.1 point2point
29 Pop Label 10.91.0.0/16 0 Hs5/0 point2point
1/36 10.91.0.0/16 0 AT0/0.1 point2point
30 32 10.250.0.97/32 0 Et4/0/2 10.92.0.7
32 10.250.0.97/32 0 Hs5/0 point2point
34 26 10.77.0.0/24 0 Et4/0/2 10.92.0.7
26 10.77.0.0/24 0 Hs5/0 point2point
35 No Label[T] 10.100.100.101/32 0 Tu301 point2point
36 Pop Label 10.1.0.0/16 0 Hs5/0 point2point
1/37 10.1.0.0/16 0 AT0/0.1 point2point
[T] Forwarding through a TSP tunnel.
View additional labeling info with the 'detail' option
The following is sample output from the show mpls forwarding-table command when the IPv6 Provider Edge Router over MPLS feature is configured to allow IPv6 traffic to be transported across an IPv4 MPLS backbone. The labels are aggregated because there are several prefixes for one local label, and the prefix column contains "IPv6" instead of a target prefix.
Router# show mpls forwarding-table
Local Outgoing Prefix Bytes label Outgoing Next Hop
Label Label or VC or Tunnel Id switched interface
19 Pop Label 192.168.99.64/30 0 Se0/0 point2point
20 Pop Label 192.168.99.70/32 0 Se0/0 point2point
21 Pop Label 192.168.99.200/32 0 Se0/0 point2point
The 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 detail
Local Outgoing Prefix Bytes label Outgoing Next Hop
label label or VC or Tunnel Id switched interface
16 Pop label 10.0.0.6/32 0 AT1/0.1 point2point
Bundle 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{}
No output feature configured
17 18 10.0.0.9/32 0 AT1/0.1 point2point
Bundle 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 00012000
No output feature configured
18 19 10.0.0.10/32 0 AT1/0.1 point2point
Bundle 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 00013000
No output feature configured
19 17 10.0.0.0/8 0 AT1/0.1 point2point
Bundle 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 00011000
No output feature configured
20 20 10.0.0.0/8 0 AT1/0.1 point2point
Bundle 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 00014000
No output feature configured
21 Pop label 10.0.0.0/24 0 AT1/0.1 point2point
Bundle 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{}
No output feature configured
22 Pop label 10.0.0.4/32 0 Et2/3 10.0.0.4
MAC/Encaps=14/14, MTU=1504, label Stack{}
000427AD10430005DDFE043B8847
No output feature configured
The 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 detail
Local Outgoing Prefix Bytes label Outgoing Next Hop
label label or VC or Tunnel Id switched interface
16 Aggregate 10.0.0.0/8[V] 0
MAC/Encaps=0/0, MTU=0, label Stack{}
Per-packet load-sharing, slots: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
17 No label 10.0.0.0/8[V] 0 Et0/0/2 10.0.0.1
MAC/Encaps=0/0, MTU=1500, label Stack{}
Per-packet load-sharing, slots: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
18 No label 10.42.42.42/32[V] 4185 Et0/0/2 10.0.0.1
MAC/Encaps=0/0, MTU=1500, label Stack{}
Per-packet load-sharing, slots: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
19 2/33 10.41.41.41/32 0 AT1/0/0.1 point2point
MAC/Encaps=4/8, MTU=4470, label Stack{2/33(vcd=2)}
No output feature configured
Cisco 10000 Series Examples
The following is sample output from the show mpls forwarding-table command:
Router# show mpls forwarding-table
Local Outgoing Prefix Bytes Label Outgoing Next Hop
Label Label or VC or Tunnel Id Switched interface
16 Pop Label 10.0.0.0/8 0 Fa1/0/0 10.0.0.2
Pop Label 10.0.0.0/8 0 Fa1/1/0 10.0.0.2
17 Aggregate 10.0.0.0/8[V] 570 vpn2
21 Pop Label 10.11.11.11/32 0 Fa1/0/0 10.0.0.2
22 Pop Label 10.12.12.12/32 0 Fa1/1/0 10.0.0.2
23 No Label 10.3.0.0/16[V] 0 Fa4/1/0 10.0.0.2
The following is Cisco 10000 series sample output from the show mpls forwarding-table command when you specify the detail keyword:
Router# show mpls forwarding-table detail
Local Outgoing Prefix Bytes Label Outgoing Next Hop
Label Label or VC or Tunnel Id Switched interface
16 Pop Label 10.0.0.0/8 0 Fa1/0/0 10.0.0.2
MAC/Encaps=14/14, MRU=1500, Label Stack{}
000B45C93889000B45C930218847
No output feature configured
Pop Label 10.0.0.0/8 0 Fa1/1/0 10.0.0.2
MAC/Encaps=14/14, MRU=1500, Label Stack{}
000B45C92881000B45C930288847
No output feature configured
17 Aggregate 10.0.0.0/8[V] 570 vpn2
MAC/Encaps=0/0, MRU=0, Label Stack{}
No output feature configured
21 Pop Label 10.11.11.11/32 0 Fa1/0/0 10.0.0.2
MAC/Encaps=14/14, MRU=1500, Label Stack{}
000B45C93889000B45C930218847
No output feature configured
Table 83 describes the significant fields in the sample output.
Table 83 show mpls forwarding-table Field Descriptions
Field
|
Description
|
Local label
|
Label assigned by this router.
|
Outgoing Label or VC
Note This field is not supported on the Cisco 10000 series routers.
|
Label assigned by the next hop or Virtual Path Identifier (VPI)/Virtual Channel Identifier (VCI) used to get to next hop. The entries in this column are the following:
• [T]—Means forwarding through an LSP tunnel.
• No Label—Means that there is no label for the destination from the next hop or that label switching is not enabled on the outgoing interface.
• Pop Label—Means that the next hop advertised an implicit NULL label for the destination and that the router removed the top label.
• Aggregate—Means there are several prefixes for one local label. This entry is used when IPv6 is configured on edge routers to transport IPv6 traffic over an IPv4 MPLS network.
|
Prefix or Tunnel Id
|
Address or tunnel to which packets with this label are sent.
Note If IPv6 is configured on edge routers to transport IPv6 traffic over an IPv4 MPLS network, "IPv6" is displayed here.
[V]—means that the corresponding prefix is in a VRF.
|
Bytes label switched
|
Number of bytes switched with this incoming label. This includes the outgoing label and Layer 2 header.
|
Outgoing interface
|
Interface through which packets with this label are sent.
|
Next Hop
|
IP address of the neighbor that assigned the outgoing label.
|
Bundle adjacency exp(vcd)
|
Bundle adjacency information. Includes the MPLS EXP value and the corresponding VCD.
|
MAC/Encaps
|
Length in bytes of the Layer 2 header and length in bytes of the packet encapsulation, including the Layer 2 header and label header.
|
MTU
|
MTU of the labeled packet.
|
label Stack
|
All the outgoing labels. If the outgoing interface is transmission convergence (TC)-ATM, the VCD is also shown.
Note TC-ATM is not supported on Cisco 10000 series routers.
|
00010000AAAA030000008847 00013000
|
The actual encapsulation in hexadecimal form. A space is shown between Layer 2 and the label header.
|
Explicit-Null Label Example
The following example shows output, including the explicit-null label = 0 (commented in bold), from the show mpls forwarding-table command on a CSC-PE router:
Router# show mpls forwarding-table
Local Outgoing Prefix Bytes label Outgoing Next Hop
label label or VC or Tunnel Id switched interface
17 Pop label 10.10.0.0/32 0 Et2/0 10.10.0.1
18 Pop label 10.10.10.0/24 0 Et2/0 10.10.0.1
19 Aggregate 10.10.20.0/24[V] 0
20 Pop label 10.10.200.1/32[V] 0 Et2/1 10.10.10.1
21 Aggregate 10.10.1.1/32[V] 0
22 0 192.168.101.101/32[V] \
23 0 192.168.101.100/32[V] \
25 0 192.168.102.125/32[V] 0 Et2/1 192.168.102.125 !outlabel
value 0
Table 84 describes the significant fields in the sample output.
Table 84 show mpls forwarding-table Field Descriptions
Field
|
Description
|
Local label
|
Label assigned by this router.
|
Outgoing label or VC
|
Label assigned by the next hop or VPI/VCI used to get to next hop. The entries this column are the following:
• [T]—Means forwarding through an LSP tunnel.
• No label—Means that there is no label for the destination from the next hop or that label switching is not enabled on the outgoing interface.
• Pop label—Means that the next hop advertised an implicit NULL label for the destination and that this router popped the top label.
• Aggregate—Means there are several prefixes for one local label. This entry is used when IPv6 is configured on edge routers to transport IPv6 traffic over an IPv4 MPLS network.
• 0—Means the explicit null label value = 0.
|
Prefix or Tunnel Id
|
Address or tunnel to which packets with this label are going.
Note If IPv6 is configured on edge routers to transport IPv6 traffic over an IPv4 MPLS network, IPv6 is displayed here.
[V]—means that the corresponding prefix is in a VRF.
|
Bytes label switched
|
Number of bytes switched with this incoming label. This includes the outgoing label and Layer 2 header.
|
Outgoing interface
|
Interface through which packets with this label are sent.
|
Next Hop
|
IP address of the neighbor that assigned the outgoing label.
|
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-table
Local Outgoing Prefix Bytes Label Outgoing Next Hop
Label Label or Tunnel Id Switched interface
16 Pop Label IPv4 VRF[V] 62951000 aggregate/v1
17 [H] No Label 10.1.1.0/24 0 AT1/0/0.1 point2point
No Label 10.1.1.0/24 0 PO3/1/0 point2point
[T] No Label 10.1.1.0/24 0 Tu1 point2point
18 [HT] Pop Label 10.0.0.3/32 0 Tu1 point2point
19 [H] No Label 10.0.0.0/8 0 AT1/0/0.1 point2point
No Label 10.0.0.0/8 0 PO3/1/0 point2point
20 [H] No Label 10.0.0.0/8 0 AT1/0/0.1 point2point
No Label 10.0.0.0/8 0 PO3/1/0 point2point
21 [H] No Label 10.0.0.1/32 812 AT1/0/0.1 point2point
No Label 10.0.0.1/32 0 PO3/1/0 point2point
22 [H] No Label 10.1.14.0/24 0 AT1/0/0.1 point2point
No Label 10.1.14.0/24 0 PO3/1/0 point2point
23 [HT] 16 172.1.1.0/24[V] 0 Tu1 point2point
24 [HT] 24 10.0.0.1/32[V] 0 Tu1 point2point
25 [H] No Label 10.0.0.0/8[V] 0 AT1/1/0.1 point2point
26 [HT] 16 10.0.0.3/32[V] 0 Tu1 point2point
27 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 85 describes the field relating to the Cisco IOS Software Modularity: MPLS Layer 3 VPNs feature as shown in the sample output.
Table 85 show mpls forwarding-table Field Descriptions
Field
|
Description
|
Local label
|
Label assigned by this router.
• [H]—Local labels are in holddown, which means that the application that requested the labels no longer needs them and stops advertising them to its labeling peers.
The label's forwarding-table entry is deleted after a short, application-specific time.
If any application starts advertising a held-down label to its labeling peers, the label could come out of holddown.
Note [H] is not shown if labels are held down globally.
A label enters global holddown after a stateful switchover or a restart of certain processes in a Cisco IOS modularity environment.
• [T]—The label is forwarded through an LSP tunnel.
Note Although [T] is still a property of the outgoing interface, it is shown in the Local label column.
• [HT]—Both conditions apply.
|
Related Commands
Command
|
Description
|
neighbor send-label
|
Enables a BGP router to send MPLS labels with BGP routes to a neighboring BGP router.
|
neighbor send-label explicit-null
|
Enables a BGP router to send MPLS labels with explicit-null information for a CSC-CE router and BGP routes to a neighboring CSC-PE router.
|
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
interface
|
(Optional) Defines the interface about which to display label switching information.
|
vrf vpn-name
|
(Optional) Displays information about the interfaces that have been configured for label switching for the specified Virtual Private Network (VPN) routing and forwarding (VRF) instance (vpn-name).
|
all
|
(Optional) When the all keyword is specified alone in this command, information about the interfaces configured for label switching is displayed for all VPNs, including the VPNs in the default routing domain.
|
detail
|
(Optional) Displays detailed label switching information.
|
internal
|
(Optional) Indicates whether Multiprotocol Label Switching (MPLS) egress NetFlow accounting is enabled.
|
Defaults
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
Release
|
Modification
|
11.1CT
|
This command was introduced.
|
12.1(3)T
|
This command was updated with MPLS command syntax and terminology.
|
12.0(10)ST
|
The internal keyword was added.
|
12.0(14)ST
|
This command was modified to reflect MPLS VPN support for LDP.
|
12.1(2)T
|
This command was integrated into Cisco IOS Release 12.1(2)T.
|
12.1(8a)E
|
This command was integrated into Cisco IOS Release 12.1(8a)E.
|
12.2(2)T
|
This command was integrated into Cisco IOS Release 12.2(2)T.
|
12.2(25)S
|
This command was modified to show Border Gateway Protocol (BGP) and static routing information.
|
12.0(22)S
|
This command was integrated into Cisco IOS Release 12.0(22)S.
|
12.2(28)SB
|
This command was integrated into Cisco IOS Release 12.2(28)SB.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2(33)SRB
|
This command was integrated into Cisco IOS Release 12.2(33)SRB.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
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 interfaces
Interface IP Tunnel Operational
Ethernet1/1/1 Yes (tdp) No No
Ethernet1/1/2 Yes (tdp) Yes No
Ethernet1/1/3 Yes (tdp) Yes Yes
ATM0/0.1 Yes (tdp) No No (ATM labels)
ATM3/0.1 Yes (ldp) No Yes (ATM labels)
ATM0/0.2 Yes (tdp) No Yes
Cisco 10000 Series Example
The following is sample output from the show mpls interfaces command:
Router# show mpls interfaces
Interface IP Tunnel BGP Static Operational
GigabitEthernet1/0/0 Yes No No No No
GigabitEthernet2/0/0 No No No Yes No
GigabitEthernet3/0/0 No Yes No No No
Note
If an interface uses LC-ATM procedures, the associated line in the display is flagged with the notation (ATM labels).
Table 86 describes the significant fields shown in the display.
Table 86 show mpls interfaces Field Descriptions
Field
|
Description
|
Interface
|
Interface name.
|
IP
|
If IP label switching (sometimes called hop-by-hop label switching) is enabled on this interface, the column entry is "Yes." Otherwise, the entry is "No."
|
Tunnel
|
If label switched path (LSP) tunnel labeling is on this interface, the column entry is "Yes." Otherwise, the entry is "No."
|
BGP
|
If BGP has been enabled, the column entry is "Yes." Otherwise, the entry is "No."
|
Static
|
If static routes have been enabled, the column entry is "Yes." Otherwise, the entry is "No."
|
Operational
|
If packets are being labeled, the column entry is "Yes." Otherwise, the entry is "No."
|
The following is sample output from the show mpls interfaces command with the detail keyword:
Router# show mpls interfaces detail
IP labeling enabled (tdp)
LSP Tunnel labeling not enabled
IP labeling enabled (ldp)
LSP Tunnel labeling not enabled
IP labeling enabled (ldp)
LSP Tunnel labeling not enabled
ATM labels: Label VPI = 1
Label VCI range = 33 - 65535
Cisco 10000 Series Example
The following example is sample output of the show mpls interfaces command with the detail keyword:
Router# show mpls interfaces detail
Interface GigabitEthernet1/0/0:
IP labeling enabled (ldp)
LSP Tunnel labeling not enabled
IP labeling enabled (ldp)
LSP Tunnel labeling not enabled
Table 87 describes the significant fields shown in the display.
Table 87 show mpls interfaces detail Field Descriptions
Field
|
Description
|
Interface
|
Interface name.
|
IP labeling
|
If IP label switching is enabled on this interface, the entry is "enabled." Otherwise, the entry is "not enabled." The output also shows whether LDP or TDP is being used.
|
LSP Tunnel labeling
|
If the LSP tunnel labeling is enabled on this interface, the entry is "enabled." Otherwise, the entry is "not enabled."
|
MPLS
|
If packets are labeled, the entry is "operational." Otherwise, the entry is "not operational."
|
BGP
|
If BGP has been enabled, the entry is "enabled." Otherwise, the entry is "not enabled."
|
MTU
|
The setting of the maximum transmission unit, in bytes.
|
ATM labels: Label VPI
|
The virtual path identifier (VPI).
Note This field does not apply to the Cisco 10000 series routers.
|
Label VCI range
|
The range of values used in the VPI field for label VCs.
Note This field does not apply to the Cisco 10000 series routers.
|
Control VC
|
The values assigned to the control VC.
Note This field does not apply to the 10000 series routers.
|
The following is sample output from the show mpls interfaces command with the all keyword:
Router# show mpls interfaces all
Interface IP Tunnel Operational
ATM1/1/0.1 Yes (tdp) No Yes
ATM3/0/0.1 Yes (ldp) No Yes
ATM3/0/0.2 Yes (ldp) No Yes
ATM3/0/0.3 Yes (ldp) No Yes
ATM3/0/0.4 Yes (ldp) No Yes
ATM3/0/0.5 Yes (ldp) No Yes
Interface IP Tunnel Operational
ATM3/0/0.6 Yes (ldp) No Yes
ATM3/0/0.7 Yes (ldp) No Yes
ATM3/0/0.8 Yes (ldp) No Yes
ATM3/0/0.9 Yes (ldp) No Yes
ATM3/0/0.10 Yes (ldp) No Yes
ATM3/0/0.11 Yes (ldp) No Yes
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 internal
IP labeling enabled (tdp)
LSP Tunnel labeling not enabled
IP to Tag Fast Feature Switching Vector
MTU = 1500, status=0x100043, appcount=1
IP labeling enabled (tdp)
LSP Tunnel labeling not enabled
IP to Tag Fast Feature Switching Vector
MTU = 1500, status=0x100043, appcount=1
Related Commands
Command
|
Description
|
mpls ip (global configuration)
|
Enables MPLS forwarding of IPv4 packets along normally routed paths for the platform.
|
mpls ip (interface configuration)
|
Enables MPLS forwarding of IPv4 packets along normally routed paths for a particular interface.
|
mpls label protocol (global configuration)
|
Specifies the default label distribution protocol for a platform.
|
mpls label protocol (interface configuration)
|
Specifies the label distribution protocol to be used on a given interface.
|
mpls traffic-eng tunnels (global configuration)
|
Enables MPLS traffic engineering tunnel signaling on a device.
|
mpls traffic-eng tunnels (interface configuration)
|
Enables MPLS traffic engineering tunnel signaling on an interface.
|
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
vrf vrf-name
|
(Optional) Displays the LDP neighbors for the specified Virtual Private Network (VPN) routing and forwarding (VRF) instance (vrf-name).
Note This keyword and argument pair does not apply to the Cisco 10000 series routers.
|
all
|
(Optional) Displays binding information for all VRFs.
Note This keyword does not apply to the Cisco 10000 series routers.
|
network
|
(Optional) Defines the destination network number.
|
mask
|
Defines the network mask, written as A.B.C.D.
|
length
|
Defines the mask length (1 to 32 characters).
|
longer-prefixes
|
(Optional) Selects any prefix that matches the mask with a length from 1 to 32 characters.
|
neighbor address
|
(Optional) Displays label bindings assigned by the selected neighbor.
|
local
|
(Optional) Displays the local label bindings.
|
local-label atm vpi vci
|
(Optional) Displays the entry with the locally assigned ATM label that matches the specified ATM label value. The virtual path identifier (VPI) range is 0 to 4095. The virtual channel identifier (VCI) range is 0 to 65535.
Note These keywords and arguments do not apply to the Cisco 10000 series routers.
|
local-label label - label
|
(Optional) Displays entries with locally assigned labels that match the specified label values. Use the label - label arguments and keyword to indicate the label range. The hyphen (-) keyword is required for a label range.
|
remote-label atm vpi vci
|
(Optional) Displays entries with remotely assigned ATM label values learned from neighbor routers that match the specified ATM label value. The VPI range is 0 to 4095. The VCI range is 0 to 65535.
Note These keywords and arguments do not apply to the Cisco 10000 series routers.
|
remote-label label - label
|
(Optional) Displays entries with remotely assigned labels learned from neighbor routers that match the specified label values. Use the label - label arguments and keyword to indicate the label range. The hyphen (-) keyword is required for a label range.
|
interface interface
|
(Optional) Displays label bindings associated with the specified interface (for label-controlled (LC)-ATM only).
Note This keyword and argument pair does not apply to the Cisco 10000 series routers.
|
generic
|
(Optional) Displays only generic (non-LC-ATM) label bindings.
|
atm
|
(Optional) Displays only LC-ATM label bindings.
Note This keyword does not apply to the Cisco 10000 series routers.
|
detail
|
(Optional) Displays detailed information about label bindings learned by LDP.
|
summary
|
(Optional) Displays summary information about label bindings learned by LDP.
|
Defaults
All label bindings are displayed when no optional arguments or keywords are specified.
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.0(10)ST
|
This command was introduced.
|
12.0(14)ST
|
This command was modified to reflect MPLS VPN support for LDP.
|
12.1(2)T
|
This command was integrated into Cisco IOS Release 12.1(2)T.
|
12.1(8a)E
|
This command was integrated into Cisco IOS Release 12.1(8a)E.
|
12.2(2)T
|
This command was integrated into Cisco IOS Release 12.2(2)T.
|
12.2(4)T
|
The VPI range of values was extended to 4095.
|
12.2(8)T
|
This command was integrated into Cisco IOS Release 12.2(8)T.
|
12.0(21)ST
|
This command was integrated into Cisco IOS Release 12.0(21)ST.
|
12.0(22)S
|
This command was integrated into Cisco IOS Release 12.0(22)S.
|
12.0(23)S
|
This command was integrated into Cisco IOS Release 12.0(23)S.
|
12.2(13)T
|
This command was integrated into Cisco IOS Release 12.2(13)T.
|
12.2(14)S
|
This command was integrated into Cisco IOS Release 12.2(14)S.
|
12.2(25)S
|
The detail keyword was added to display checkpoint status for local label bindings.
|
12.2(28)SB
|
This command was integrated into Cisco IOS Release 12.2(28)SB and implemented on the Cisco 10000 series routers.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2(33)SXH
|
This command was integrated into Cisco IOS Release 12.2(33)SXH.
|
Usage Guidelines
The show mpls ip binding command displays label bindings learned by LDP or the Tag Distribution Protocol (TDP).
Note
TDP is not supported for LDP features in Cisco IOS 12.0(30)S and later releases, 12.2(27)SBC and later 12.2S releases, and 12.3(14)T and later releases.
To summarize information about label bindings learned by LDP, use the show mpls ip binding summary command in user EXEC or privileged EXEC mode.
A request can specify that the entire database be displayed, that a summary of entries from the database be displayed, or that the display be limited to a subset of entries. The subset can be limited according to any of the following:
•
Prefix
•
Input or output label values or ranges
•
Neighbor advertising the label
•
Interface for label bindings of interest (LC-ATM only)
Note
LC-ATM label binding interface does not apply to the Cisco 10000 series routers.
•
Generic (non-LC-ATM) label bindings
•
LC-ATM label bindings
Note
LC-ATM label binding interface does not apply to the Cisco 10000 series routers.
Examples
The following is sample output from the show mpls ip binding command. The output shows all the label bindings in the database.
Router# show mpls ip binding
out label: 26 lsr: 10.0.0.55:0
out vc label: 1/80 lsr: 10.0.7.7:2 ATM1/0.8
Active ingress 3 hops (vcd 49)
in vc label: 1/36 lsr: 10.0.7.7:2 ATM1/0.8
out label: imp-null lsr: 10.0.0.55:0 inuse
in vc label: 1/39 lsr: 10.0.7.7:2 ATM1/0.8
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 24
in vc label: 1/37 lsr: 10.0.7.7:2 ATM1/0.8
out label: imp-null lsr: 10.0.0.55:0 inuse
In 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 58
out label: imp-null lsr: 10.0.0.55:0 inuse
The following sample output shows the label bindings for the VPN routing and forwarding instance named vpn1:
Router# show mpls ip binding vrf vpn1
out label: imp-null lsr:10.14.14.14:0
out label: 268 lsr:10.14.14.14:0
out label: imp-null lsr:10.14.14.14:0
out label: 266 lsr:10.14.14.14:0
out label: 319 lsr:10.14.14.14:0
out label: 571 lsr:10.14.14.14:0
out label: 267 lsr:10.14.14.14:0
out label: imp-null lsr:10.14.14.14:0
out label: imp-null lsr:10.14.14.14:0
out label: 504 lsr:10.14.14.14:0
out label: imp-null lsr:10.14.14.14:0
out label: 269 lsr:10.14.14.14:0
out label: imp-null lsr:10.14.14.14:0
The following sample output shows label binding information for all VRFs:
Router# show mpls ip binding all
out label: imp-null lsr: 10.131.0.1:0
out label: imp-null lsr: 10.131.0.1:0
out label: imp-null lsr: 10.131.0.1:0
out label: imp-null lsr: 10.131.0.1:0 inuse
out label: 16 lsr: 10.131.0.1:0
out label: imp-null lsr: 10.132.0.1:0
out label: imp-null lsr: 10.132.0.1:0
out label: imp-null lsr: 10.132.0.1:0
out label: imp-null lsr: 10.132.0.1:0
out label: 16 lsr: 10.132.0.1:0
out label: 17 lsr: 10.132.0.1:0
out label: imp-null lsr: 10.132.0.1:0
Cisco 10000 Series Examples Only
The following sample shows binding information for a Cisco 10000 series router:
Router# show mpls ip binding
out label: imp-null lsr: 10.66.66.66:0
out label: imp-null lsr: 10.44.44.44:0
out label: 26 lsr: 10.66.66.66:0
out label: imp-null lsr: 10.44.44.44:0
out label: imp-null lsr: 10.66.66.66:0
out label: 18 lsr: 10.44.44.44:0
out label: 19 lsr: 10.66.66.66:0
out label: 26 lsr: 10.66.66.66:0
out label: imp-null lsr: 10.44.44.44:0
out label: imp-null lsr: 10.66.66.66:0
out label: 18 lsr: 10.44.44.44:0
out label: 19 lsr: 10.66.66.66:0
out label: imp-null lsr: 10.44.44.44:0 inuse
out label: 25 lsr: 10.66.66.66:0
out label: 55 lsr: 10.44.44.44:0
out label: imp-null lsr: 10.66.66.66:0 inuse
out label: 16 lsr: 10.44.44.44:0
out label: 16 lsr: 10.66.66.66:0
out label: 59 lsr: 10.44.44.44:0
In 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 32
out label: 19 lsr: 10.66.66.66:0
out label: imp-null lsr: 10.44.44.44:0 inuse
In 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 21
Table 88 describes the significant fields shown in the displays.
Table 88 show mpls ip binding Field Descriptions
Field
|
Description
|
172.16.44.44/32
|
Destination prefix. Indicates that the following lines are for a particular destination (network/mask).
|
in label
|
Incoming label. This is the local label assigned by the label switch router (LSR) and advertised to other LSRs. The label value imp-null indicates the well-known Implicit NULL label.
|
out label
|
Outgoing label. This is a remote label learned from an LDP neighbor. The neighbor is identified by its LDP ID in the lsr field.
|
inuse
|
Indicates that the outgoing label is in use for Multiprotocol Label Switching (MPLS) forwarding, that is, it is installed in the MPLS forwarding table (the Label Forwarding Information Base [LFIB]).
|
in vc label
|
Incoming MPLS ATM label. This is the local VPI/VCI assigned by the LSR as the incoming label for the destination and advertised to the upstream LSRs.
Note This field applies to the Cisco 7500 series routers only.
|
out vc label
|
Outgoing MPLS ATM label. This is the VPI/VCI learned from the destination next hop as its label for the destination and advertised to this LSR.
Note This field applies to the Cisco 7500 series routers only.
|
ATM1/0.8
|
The ATM interface with which the MPLS ATM label is associated.
Note This field applies to the Cisco 7500 series routers only.
|
Active
|
State of the label VC (LVC) associated with the destination prefix.
Note This field applies to the Cisco 7500 series routers only.
States are the following:
• Active. Established and operational.
• Bindwait. Waiting for a response from the destination next hop.
• Remote Resource Wait. Waiting for resources (VPI/VCI) to become available on the destination next hop.
• Parent Wait. Transit LVC upstream side waiting for downstream side to become active.
• AbortAckWait. Waiting for response to a Label Abort message sent to the destination next hop.
• ReleaseWait. Waiting for response to a Label Withdraw message sent to an upstream neighbor.
|
vcd 49
|
Virtual circuit descriptor number for the LVC.
Note This field applies to the Cisco 7500 series routers only.
|
ingress 3 hops
|
Indicates whether the LSR is an ingress, transit, or egress node for the destination.
Note This field applies to the Cisco 7500 series routers only.
Options include the following:
• Ingress 3 hops. The LSR is an ingress edge router for the MPLS ATM cloud for the destination.
• Egress. The LSR is an egress edge router for the MPLS ATM cloud for the destination.
• Transit. The LSR is a transit LSR within the MPLS ATM cloud for the destination.
|
The following sample output displays detailed information about the label bindings:
Router# show mpls ip binding detail
10.0.0.0/8, rev 2, chkpt: add-skipped
in label: imp-null (owner LDP)
10.60.60.60:0 10.30.30.30:0
out label: imp-null lsr: 10.60.60.60:0
out label: imp-null lsr: 10.30.30.30:0
10.10.10.10/32, rev 18, chkpt: added
10.60.60.60:0 10.30.30.30:0
out label: 142 lsr: 10.60.60.60:0
out label: 19 lsr: 10.30.30.30:0 inuse
10.0.0.1/32, rev 10, chkpt: add-skipped
in label: imp-null (owner LDP)
10.60.60.60:0 10.30.30.30:0
out label: 21 lsr: 10.60.60.60:0
out label: 17 lsr: 10.30.30.30:0
10.30.30.30/32, rev 20, chkpt: added
10.60.60.60:0 10.30.30.30:0
out label: 22 lsr: 10.60.60.60:0
Table 89 describes the significant fields shown in the display.
Table 89 show mpls ip binding detail Field Descriptions
Field
|
Description
|
chkpt
|
The status of the checkpointed entry.
• add-skipped—Means that the local label is a null label and does not need to be checkpointed.
• added— Means that the checkpoints entry was copied to the backup Route Processor (RP)
|
owner
|
The application that created the binding.
• owner LDP—Means that LDP created the binding.
• owner other—Means that another application created the binding, possibly Border Gateway protocol (BGP).
|
Advertised to
|
The LSRs that received the local label binding.
|
inuse or stale
|
The status of the label.
• inuse—Indicates that the outgoing label is in use for MPLS forwarding, that is, it is installed in the MPLS forwarding table (LFIB).
• stale—Indicates a label that is no longer in use. This happens when an LDP session is lost and the routers begin a graceful restart. Then the remote label bindings are marked stale.
|
Cisco 7500 Series Example Only
The following sample output shows summary information about the label bindings learned by LDP:
Router# show mpls ip binding summary
Total number of prefixes: 53
prefixes in labels out labels
ATM label bindings summary
interface total active local remote Bwait Rwait IFwait
ATM1/0.8 47 47 40 7 0 0 0
Table 90 describes the significant fields shown in the display.
Table 90 show mpls ip binding summary Field Descriptions (Cisco 7500 Series Example)
Field
|
Description
|
Total number of prefixes
|
Number of destinations for which the LSR has label bindings.
|
Generic label bindings
|
Indicates the start of summary information for "generic" label bindings. Generic labels are used for MPLS forwarding on all interface types except MPLS ATM interfaces.
|
prefixes
|
Number of destinations for which the LSR has a generic label binding.
|
assigned in labels
|
Number of prefixes for which the LSR has assigned an incoming (local) label.
|
learned out labels
|
Number of prefixes for which the LSR has learned an outgoing (remote) label from an LDP neighbor.
|
ATM label bindings summary
|
Indicates the start of summary information for MPLS ATM label bindings. An ATM label is a VPI/VCI.
|
interface
|
Indicates a row in the ATM label bindings summary table. The summary information in the row is for ATM labels associated with this interface.
|
total
|
Total number of ATM labels associated with the interface.
|
active
|
Number of ATM labels (LVCs) in the active (operational) state.
|
local
|
Number of ATM labels assigned by this LSR for the interfaces. These are incoming labels.
|
remote
|
Number of ATM labels learned from the neighbor LSR for this interface. These are outgoing labels.
|
Bwait
|
Number of bindings (LVCs) waiting for a label assignment from the neighbor LSR for the interface.
|
Rwait
|
Number of bindings (LVCs) waiting for resources (VPI/VCIs) to become available on the neighbor LSR for the interface.
|
IFwait
|
Number of bindings (LVCs) waiting for labels to be installed for switching use.
|
Cisco 10000 Series Example Only
The following sample output displays summary information about the label bindings learned by LDP:
Router# show mpls ip binding summary
Total number of prefixes: 53
prefixes in labels out labels
Table 91 describes the significant fields shown in the display.
Table 91 show mpls ip binding summary Field Descriptions (Cisco 10000 Series Example)
Field
|
Description
|
Total number of prefixes
|
Number of destinations for which the LSR has label bindings.
|
Generic label bindings
|
Indicates the start of summary information for "generic" label bindings. Generic labels are used for MPLS forwarding on all interface types except MPLS ATM interfaces.
|
prefixes
|
Number of destinations for which the LSR has a generic label binding.
|
assigned in labels
|
Number of prefixes for which the LSR has assigned an incoming (local) label.
|
learned out labels
|
Number of prefixes for which the LSR has learned an outgoing (remote) label from an LDP neighbor.
|
Related Commands
Command
|
Description
|
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
Release
|
Modification
|
12.2(25)S
|
This command was introduced.
|
12.2(28)SB
|
This command was integrated into Cisco IOS Release 12.2(28)SB and implemented on the Cisco 10000 series routers.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2(33)SXH
|
This command was integrated into Cisco IOS Release 12.2(33)SXH.
|
12.4(20)T
|
This command was integrated into Cisco IOS Release 12.4(20)T.
|
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 counters
CEF Tree Changes Processed/Ignored: 91/12
CEF Deletes Processed/Ignored: 12/2
Rewrite Create Successes/Failures: 60/0
Rewrite Gets/Deletes: 82/0
Label Announcements: Info/Local/Path: 6/119/80
Walks: Recursion Tree/CEF Full/CEF interface: 78/2/0
Table 92 describes the significant fields shown in the display.
Table 92 show mpls ip iprm counters Command Field Descriptions
Field
|
Description
|
CEF Tree Changes Processed/Ignored
|
Processed—The number of Cisco Express Forwarding tree change announcements that IPRM processed.
Ignored—The number of Cisco Express Forwarding tree change announcements that IPRM ignored.
Typically, IPRM processes tree change announcements only for prefixes in a routing table.
|
CEF Deletes Processed/Ignored
|
Processed—The number of Cisco Express Forwarding delete entry announcements that IPRM processed.
Ignored—The number of Cisco Express Forwarding delete entry announcements that IPRM ignored.
Typically, IPRM processes delete entry announcements only for prefixes in a routing table.
|
Label Discoveries
|
The number of label discoveries performed by IPRM. Label discovery is the process by which IPRM obtains prefix labels from the IP Label Distribution Modules (LDMs).
|
Rewrite Create Successes/Failures
|
Successes—The number of times IPRM successfully updated the MPLS forwarding information.
Failures—The number of times IPRM attempted to update the MPLS forwarding information and failed.
|
Rewrite Gets/Deletes
|
Gets—The number of times IPRM retrieved forwarding information from the MPLS forwarding infrastructure.
Deletes—The number of times IPRM removed prefix forwarding information from the MPLS forwarding infrastructure.
|
Label Announcements: Info/Local/Path
|
Info—The number of times an IP label distribution module informed IPRM that label information for a prefix changed.
Local—The number of times an IP label distribution module specified local labels for a prefix.
Path—The number of times an IP LDM specified outgoing labels for a prefix route.
|
Walks: Recursion Tree/CEF Full/CEF interface
|
Recursion Tree—The number of times IPRM requested Cisco Express Forwarding to walk the recursion (path) tree for a prefix.
CEF Full—The number of times IPRM requested Cisco Express Forwarding to walk a Cisco Express Forwarding table and notify IPRM about each prefix.
CEF interface—The number of times IPRM requested Cisco Express Forwarding to walk a Cisco Express Forwarding table and notify IPRM about each prefix with a path that uses a specific interface.
|
Related Commands
Command
|
Description
|
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
table
|
(Optional) Displays the LDMs for one or more routing tables.
|
all
|
Displays the LDMs for all routing tables.
|
table-id
|
Displays the LDMs for the routing table you specify. Table 0 is the default or global routing table.
|
vrf
|
(Optional) Displays the LDMs for the VPN routing and forwarding (VRF) instance you specify.
|
vrf-name
|
(Optional) The name of the VRF instance. You can find VRF names with the show ip vrf command.
|
ipv4
|
(Optional) Displays IPv4 LDMs.
|
ipv6
|
(Optional) Displays IPv6 LDMs.
Note Applies to Cisco 7500 series routers only.
|
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
Release
|
Modification
|
12.2(25)S
|
This command was introduced.
|
12.2(28)SB
|
This command was integrated into Cisco IOS Release 12.2(28)SB and implemented on the Cisco 10000 series routers.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2(33)SXH
|
This command was integrated into Cisco IOS Release 12.2(33)SSH.
|
12.4(20)T
|
This command was integrated into Cisco IOS Release 12.4(20)T.
|
Usage Guidelines
This command displays the IP LDMs registered with IPRM.
Examples
The command in the following example displays the LDMs for the global routing tables. It shows that two LDMs (lcatm and ldp) are registered for the ipv4 global routing table, and that one LDM (bgp ipv6) is registered for the ipv6 global routing table.
Router# show mpls ip iprm ldm
table (glbl;ipv4); ldms: 2
table (glbl;ipv6); ldms: 1
The command in the following example displays all of the LDMs registered with IPRM. The output shows the following:
•
The LDMs called lcatm and ldp have registered with IPRM for the ipv4 global table.
•
The LDM called bgp ipv6 is registered for the IPv6 global table.
•
The LDM called bgp vpnv4 is registered for all IPv4 vrf routing tables.
Router# show mpls ip iprm ldm table all
table (glbl;ipv4); ldms: 2
table (glbl;ipv6); ldms: 1
table (all-tbls;ipv4); ldms: 1
The command in the following example displays the LDMs registered for the IPv6 routing tables.
Router# show mpls ip iprm ldm ipv6
table (glbl;ipv6); ldms: 1
Cisco 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 ldm
table (glbl;ipv4); ldms: 1
The command in the following example displays all of the LDMs registered with IPRM. The output shows the following:
•
The LDM called ldp has registered with IPRM for the ipv4 global table.
•
The LDM called bgp vpnv4 is registered for all IPv4 vrf routing tables.
Router# show mpls ip iprm ldm table all
table (glbl;ipv4); ldms: 1
table (all-tbls;ipv4); ldms: 1
Related Commands
Command
|
Description
|
show mpls ip iprm counters
|
Displays the number of occurrences of various 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 EXEC
Command History
Release
|
Modification
|
12.2(33)SRA
|
This command was introduced.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
12.2(33)SRE
|
This command was modified. STANDBY and HOTSTANDBY were added as options for the Status column in output displays.
|
Examples
This example shows how to display detailed status for a specific VC:
Router# show mpls l2 vc 1100 detail
Local interface: VFI VPLS-1100 up
MPLS VC type is VFI, internetworking type is Ethernet
Destination address: 1.1.1.1,VC ID:1100, VC status: up
Output interface: Tu0,imposed label stack {27 17}
Preferred path: not configured
Create time:2d23h, last status change time: 2d23h
Signaling protocol: LDP, peer 1.1.1.1:0 up
MPLS VC labels: local 17, remote 17
Group ID: local 0, remote 0
MTU: local 1500, remote 1500
Remote interface description:
Sequencing: receive disabled, send disabled
packet totals: receive 1146978, send 3856011
byte totals: receive 86579172, send 316899920
packet drops: receive 0, send 0
The 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 detail
Local intf Local circuit Dest address VC ID Status
------------- -------------------------- --------------- ---------- ----------
AT0/2/0.1 ATM VPC CELL 50 10.1.1.2 100 UP
AT0/2/0.1 ATM VPC CELL 50 10.1.1.3 100 STANDBY
The 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 detail
Local intf Local circuit Dest address VC ID Status
------------- -------------------------- --------------- ---------- ----------
AT0/2/0.1 ATM VPC CELL 50 10.1.1.2 100 HOTSTANDBY
AT0/2/0.1 ATM VPC CELL 50 10.1.1.3 100 DOWN
During a switchover, the status of the active and backup pseudowires changes:
Router# show mpls l2 vc detail
Local intf Local circuit Dest address VC ID Status
------------- -------------------------- --------------- ---------- ----------
AT0/2/0.1 ATM VPC CELL 50 10.1.1.2 100 RECOVERING
AT0/2/0.1 ATM VPC CELL 50 10.1.1.3 100 DOWN
After the switchover is complete, the recovering pseudowire shows a status of UP:
Router# show mpls l2 vc detail
Local intf Local circuit Dest address VC ID Status
------------- -------------------------- --------------- ---------- ----------
AT0/2/0.1 ATM VPC CELL 50 10.1.1.2 100 UP
AT0/2/0.1 ATM VPC CELL 50 10.1.1.3 100 STANDBY
Related Commands
Command
|
Description
|
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
vc-id
|
(Optional) Displays VC label binding information for the specified VC.
|
ip-address
|
(Optional) Displays VC label binding information for the specified VC destination.
|
local-label number
|
(Optional) Displays VC label binding information for the specified local assigned label.
|
remote-label number
|
(Optional) Displays VC label binding information for the specified remote assigned label.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
12.0(23)S
|
This command was introduced.
|
12.2(14)S
|
This command was integrated into Cisco IOS Release 12.2(14)S.
|
12.2(15)T
|
This command was integrated into Cisco IOS Release 12.2(15)T.
|
12.0(27)S
|
This command was updated to display AToM Virtual Circuit Connection Verification (VCCV) information.
|
12.2(18)SXE
|
This command was integrated into Cisco IOS Release 12.2(18)SXE.
|
12.2(30)S
|
This command was updated to display Connectivity Verification (CV) type capabilities.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2(33)SRB
|
This command was updated to display Circuit Emulation (CEM) information for the Cisco 7600 series router.
|
Cisco IOS XE Release 2.3
|
The command was updated to display information about multisegment pseudowires.
|
12.2(33)SRE
|
This command was modified. This command displays VC label binding information for the control word.
|
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 binding
Destination Address: 10.0.0.203, VC ID: 1
Cbit: 1, VC Type: Ethernet, GroupID: 0
MTU: 1500, Interface Desc: n/a
VCCV Capabilities: Type 1, Type 2
Cbit: 1, VC Type: Ethernet, GroupID: 0
MTU: 1500, Interface Desc: n/a
VCCV Capabilities: Type 1, Type 2
The following examples shows the VC label binding information for Cisco IOS Release 12.2(30)S and later releases:
Router# show mpls l2transport binding
Destination Address: 10.5.5.51, VC ID: 108
Cbit: 1, VC Type: Ethernet, GroupID: 0
MTU: 1500, Interface Desc: n/a
VCCV: CC Type: CW [1], RA [2]
Cbit: 1, VC Type: Ethernet, GroupID: 0
MTU: 1500, Interface Desc: n/a
The output of the command changed between Cisco IOS releases. The following table maps the older output to the new output:
Output in Cisco IOS Releases 12.0(27)S and 12.2(18)SXE
|
Output In Cisco IOS Release 12.2(30)S
|
VCCV Capabilities
|
VCCV: CC Type
|
Type 1
|
CW [1]
|
Type 2
|
RA [2]
|
Table 93 describes the significant fields shown in the display.
Table 93 show mpls l2transport binding Field Descriptions
Field
|
Description
|
Destination Address
|
The IP address of the remote router's interface that is at the other end of the VC.
|
VC ID
|
The virtual circuit identifier assigned to one of the interfaces on the router.
|
Local Label
|
The VC label that a router signals to its peer router, which is used by the peer router during imposition.
|
Remote Label
|
The disposition VC label of the remote peer router.
|
Cbit
|
The control word bit. If it is set, the value is 1.
|
VC Type
|
The type of VC, such as Frame Relay, Ethernet, and ATM.
|
GroupID
|
The group ID assigned to the local or remote VCs.
|
MTU
|
The maximum transmission unit assigned.
|
Interface Desc
|
Interface parameters, if applicable.
|
VCCV Capabilities
|
(Cisco IOS Releases 12.0(27)S and 12.2(18)SXE and later releses) AToM VCCV information. This field displays how an AToM VCCV packet is identified.
• Type 1—The Protocol ID field of the AToM Control Word (CW) is identified in the AToM VCCV packet.
• Type 2—An MPLS Router Alert (RA) Level above the VC label in identified in the AToM VCCV packet. Type 2 is used for VC types that do not support or do not interpret the AToM Control Word.
|
VCCV: CC Type
|
(Cisco IOS Releases 12.2(30)S and later releases) The types of Control Channel (CC) processing that are supported. The number indicates the position of the bit that was set in the received octet. The following values can be displayed:
• CW [1]—Control Word
• RA [2]—Router Alert
• TTL [3]—Time to Live
• Unkn [x]—Unknown
|
CV Type
|
(Cisco IOS Releases 12.2(30)S and later releases) The type of Connectivity Verification (CV) packets that can be processed in the control channel of the MPLS pseudowire. The number indicates the position of the bit that was set in the received octet.
• ICMP [1]—Internet Control Management Protocol (ICMP) is used to verify connectivity.
• LSPV [2]—LSP Ping is used to verify connectivity.
• BFD [3]—Bidirectional Forwarding Detection is used to verify connectivity for more than one pseudowire.
• Unkn [x]—A CV type was received that could not be interpreted.
|
The following sample output shows information about L2VPN multisegment pseudowires (in bold):
Router# show mpls l2transport binding
Destination Address: 10.1.1.1, VC ID: 102
Cbit: 1, VC Type: Ethernet, GroupID: 0
MTU: 1500, Interface Desc: n/a
VCCV: CC Type: CW [1], RA [2], TTL [3]
Cbit: 1, VC Type: Ethernet, GroupID: 0
MTU: 1500, Interface Desc: n/a
VCCV: CC Type: CW [1], RA [2], TTL [3]
Vcid local IP addr remote IP addr Description
101 10.11.11.11 10.20.20.20 PW Switching Point PE3
100 10.20.20.20 10.11.11.11 PW Switching Point PE2
Table 94 describes the significant fields shown in the display.
Table 94 show mpls l2transport binding Field Descriptions for Multisegment Pseudowires
Field
|
Description
|
TTL
|
The Time to Live (TTL) setting of the label.
|
Vcid
|
The virtual circuit identifier.
|
local IP addr
|
The local IP address assigned to the switching point.
|
remote IP addr
|
The remote IP address assigned to the switching point.
|
Description
|
The description assigned to the switching point.
|
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: 100
Cbit: 1, VC Type: CESoPSN BRI, GroupID: 0
MTU: 1500, Interface Desc: n/a
Payload Bytes: 80, Payload Type: 0
SP bits: 11 - Data/Signaling, CAS Type: CAS T1 SF
RTP header in use: Yes, Bitrate (Kbit/s): 64
Differential Timestamp Mode: disabled
Clock Frequency (kHz): 64
Synchronization Source id: 0
Cbit: 1, VC Type: CESoPSN BRI, GroupID: 0
MTU: 1500, Interface Desc: n/a
Payload Bytes: 80, Payload Type: 0
SP bits: 11 - Data/Signaling, CAS Type: CAS T1 SF
RTP header in use: Yes, Bitrate (Kbit/s): 64
Differential Timestamp Mode: disabled
Clock Frequency (kHz): 64
Synchronization Source id: 0
The 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 102
Destination Address: 10.1.1.3, VC ID: 102
Cbit: 0, VC Type: Ethernet, GroupID: 0
MTU: 1500, Interface Desc: n/a
VCCV: CC Type: CW [1], RA [2]
Cbit: 0, VC Type: Ethernet, GroupID: 0
MTU: 1500, Interface Desc: n/a
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 1010
Destination Address: 10.6.1.2, VC ID: 1010
Cbit: 1, VC Type: ATM VCC CELL, GroupID: 0
MTU: n/a, Interface Desc: n/a
Max Concatenated ATM Cells: 10
VCCV: CC Type: CW [1], RA [2]
CV Type: LSPV [2], BFD [3]
Cbit: 1, VC Type: ATM VCC CELL, GroupID: 0
MTU: n/a, Interface Desc: n/a
Max Concatenated ATM Cells: 10
VCCV: CC Type: CW [1], RA [2]
Related Commands
Command
|
Description
|
show mpls l2transport hw-capability
|
Displays the transport types and their supported capabilities.
|
show mpls l2transport vc
|
Displays information about AToM VCs and static pseudowires that have been enabled to route Layer 2 packets on a router.
|
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
Release
|
Modification
|
12.2(25)S
|
This command was introduced.
|
12.2(28)SB
|
This command was integrated into Cisco IOS Release 12.2(28)SB.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
Examples
The 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 checkpoint
AToM Checkpoint info for active RP
Bulk-sync checkpointed state for 1 VC
On the standby RP, the command displays the following output:
Router# show mpls l2transport checkpoint
AToM HA Checkpoint info for standby RP
1 checkpoint information block in use
In general, the output on the active RP shows that checkpointing information was sent to the backup RP. The output on the backup RP shows that checkpointing information was received from the active RP.
Related Commands
Command
|
Description
|
show mpls l2transport vc
|
Displays information about the checkpointed data when checkpointing is enabled.
|
show mpls l2transport hw-capability
To display the transport types supported on an interface, use the show mpls l2transport hw-capability command in privileged EXEC mode.
show mpls l2transport hw-capability interface type number
Syntax Description
interface
|
Displays information for the specified interface.
|
type number
|
The type and number of the interface. For example, serial6/0.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.0(23)S
|
This command was introduced.
|
12.2(14)S
|
This command was integrated into Cisco IOS Release 12.2(14)S.
|
12.2(15)T
|
This command was integrated into Cisco IOS Release 12.2(15)T.
|
12.0(27)S
|
This command was updated to display AToM Virtual Circuit Connection Verification (VCCV) information.
|
12.2(18)SXE
|
This command was integrated into Cisco IOS Release 12.2(18)SXE.
|
12.2(30)S
|
This command was updated to display VCCV type capabilities.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
Usage Guidelines
This command can help you determine the interface to use for the various transport types. Use this command to check that core-facing and edge-facing interfaces can accommodate the different transport types.
Examples
The following is partial sample output from 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 95.
Router# show mpls l2transport hw-capability interface serial5/1
MPLS label disposition supported
Control word processing supported
Sequence number processing not supported
MPLS label imposition supported
Control word processing supported
Sequence number processing not supported
Note
These examples show only a portion of the output. The command displays the the capabilities of every transport type.
The following is partial sample output from 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 95.
MPLS label disposition supported
Control word processing supported
Sequence number processing not supported
VCCV CC Type 1 processing supported
MPLS label imposition supported
Control word processing supported
Sequence number processing not supported
The following is partial sample output from 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 95.
MPLS label disposition supported
Control word processing supported
Sequence number processing not supported
VCCV CC Type CW [1] processing supported
MPLS label imposition supported
Control word processing supported
Sequence number processing not supported
The output of the command changed between Cisco IOS releases. The following table maps the older output to the new output:
Output in Cisco IOS Releases 12.0(27)S and 12.2(18)SXE and later
|
Output In Cisco IOS Release 12.2(30)S
|
VCCV CC processing supported
|
VCCV CC processing supported
|
Type 1
|
Type CW [1]
|
Table 95 describes the significant fields shown in the display.
Table 95 show mpls l2transport hw-capability Field Descriptions
Field
|
Description
|
Transport type
|
Indicates the transport type.
|
Core functionality
|
Displays the functionalities that the core-facing interfaces support, such as label disposition, and control word and sequence number processing.
|
VCCV CC Type processing supported
|
Displays whether the core-facing interfaces support Control Word processing, or Router Alert Processing.
(Cisco IOS Releases 12.0(27)S and 12.2(18)SXE and later)
• Type 1—The Protocol ID field of in the AToM Control Word (CW) identified the AToM VCCV packet.
(Cisco IOS Releases 12.2(30)S and later)
• CW [1]—Control Word
• Unkn [x]—Unknown. The number indicates the position of the bit that was set in the received octet.
|
Edge functionality
|
Displays the functionalities that the edge-facing interfaces support, such as label disposition, and control word and sequence number processing.
|
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
Release
|
Modification
|
12.0(23)S
|
This command was introduced.
|
12.2(14)S
|
This command was integrated into Cisco IOS Release 12.2(14)S.
|
12.2(15)T
|
This command was integrated into Cisco IOS Release 12.2(15)T.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
Examples
The following sample output shows summary information about the VCs that have been enabled to transport Layer 2 packets:
Router# show mpls l2transport summary
Destination address: 10.16.24.12 Total number of VCs: 60
0 unknown, 58 up, 0 down, 2 admin down
5 active vc on MPLS interface PO4/0
Table 96 describes the fields shown in the display.
Table 96 show mpls l2transport summary Field Descriptions
Field
|
Description
|
Destination address
|
The IP address of the remote router to which the VC has been established.
|
Total number of VCs
|
The number of VCs that have been established.
|
unknown
|
The number of VCs that are in an unknown state.
|
up
|
The number of VCs that are operational.
|
down
|
The number of VCs that are not operational.
|
admin down
|
The number of VCs that have been disabled.
|
Related Commands
Command
|
Description
|
show mpls l2transport vc
|
Displays information about AToM VCs that have been enabled to route Layer 2 packets on a router.
|
show mpls l2transport vc
To display information about Any Transport over MPLS (AToM) virtual circuits (VCs) and static pseudowires that have been enabled to route Layer 2 packets on a router, use the show mpls l2transport vc command in privileged EXEC mode.
show mpls l2transport vc [vcid vc-id | vcid vc-id-min vc-id-max] [interface name
[local-circuit-id]] [destination ip-address | name] [detail]
Syntax Description
vcid
|
(Optional) Specifies the VC ID.
|
vc-id
|
(Optional) The VC ID number.
|
vc-id-min vc-id-max
|
(Optional) A range of VCs to display. The range is from 1 to 4294967295.
|
interface
|
(Optional) Specifies the interface or subinterface of the router that has been enabled to transport Layer 2 packets. Use this keyword to display information about the VCs that have been assigned VC IDs on that interface or subinterface.
|
name
|
(Optional) The name of the interface or subinterface.
|
local-circuit-id
|
(Optional) The number assigned to the local circuit. This argument value is supported only with the following transport types:
• For Frame Relay, enter the data-link connection identifier (DLCI) of the permanent virtual circuit (PVC).
• For ATM adaptation layer 5 (AAL5) and cell relay, enter the virtual path identifier (VPI) or virtual channel identifier (VCI) of the PVC.
• For Ethernet VLANs, enter the VLAN number.
|
destination
|
(Optional) Specifies the remote router.
|
ip-address
|
(Optional) The IP address of the remote router.
|
name
|
(Optional) The name assigned to the remote router.
|
detail
|
(Optional) Specifies the detailed information about the VCs.
|
Command Modes
User EXEC (>)
Privileged EXEC (#)
Command History
Release
|
Modification
|
12.1(8a)E
|
This command was introduced.
|
12.0(21)ST
|
This command was integrated into Cisco IOS Release 12.0(21)ST.
|
12.0(22)S
|
This command was implemented on the Cisco 10720 router.
|
12.0(23)S
|
The interface and destination keywords were added.
|
12.2(14)S
|
This command was integrated into Cisco IOS Release 12.2(14)S.
|
12.2(14)SX
|
This command was implemented on the Supervisor Engine 720.
|
12.2(14)SZ
|
This command was integrated into Cisco IOS Release 12.2(14)SZ.
|
12.2(15)T
|
This command was integrated into Cisco IOS Release 12.2(15)T.
|
12.2(18)S
|
This command was implemented on Cisco 7304 routers.
|
12.0(25)S
|
This command was updated with new output and fields to display information about tunnel selection and ATM cell relay port mode.
|
12.2(17d)SXB
|
Support for this command on the Supervisor Engine 2 was extended to Release 12.2(17d)SXB.
|
12.2(25)S
|
This command was updated with new output and fields for nonstop forwarding (NSF), stateful switchover (SSO), and graceful restart (GR) abilities.
|
12.2(28)SB
|
This command was implemented on the Cisco 10000 series routers. Example output was changed for the Cisco 10000 series router, and two fields (SSO Descriptor and SSM segment/switch IDs) were removed from the output, because they are not supported.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2(33)SRB
|
This command was updated to include forwarding equivalence class (FEC) 129 signaling information for pseudowires that are configured through VPLS Autodiscovery, and to support provisioning Any Transport over MPLS (AToM) static pseudowires.
|
12.2(33)SXH
|
This command was integrated into Cisco IOS Release 12.2(33)SXH.
|
12.2(33)SRC
|
This command was updated to display the number of MAC address withdrawal messages sent and received as part of the H-VPLS N-PE Redundancy for QinQ and MPLS Access feature.
This command was updated to display pseudowire status between peer routers that have been configured for the MPLS Pseudowire Status Signaling feature.
|
Cisco IOS XE Release 2.3
|
This command output was updated to display the following information:
• The status of pseudowires before, during, and after a switchover.
• The status of a pseudowire switching point for multisegment pseudowires.
• The number of packets and bytes being sent from the router. The VC statistics fields include the word "transit" to show that the packet totals no longer include packets being sent to the router.
|
12.2(33)SRE
|
This command was modifed. This command displays status information for the control word.
|
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 the AToM VCs.
The following sample output shows information about the interfaces and VCs that have been configured to transport various Layer 2 packets on the router:
Router# show mpls l2transport vc
Local intf Local circuit Dest address VC ID Status
------------- ------------------ --------------- ---------- ----------
Se5/0 FR DLCI 55 10.0.0.1 55 UP
AT4/0 ATM AAL5 0/100 10.0.0.1 100 UP
AT4/0 ATM AAL5 0/200 10.0.0.1 200 UP
AT4/0.300 ATM AAL5 0/300 10.0.0.1 300 UP
Table 97 describes the fields shown in the display.
Table 97 show mpls l2transport vc Field Descriptions
Field
|
Description
|
Local intf
|
The interface on the local router that has been enabled to transport Layer 2 packets.
|
Local circuit
|
The type and number (if applicable) of the local circuit. The output shown in this column varies, depending on the transport type:
• For Frame Relay, the output shows the DLCI of the PVC.
• For ATM cell relay and AAL5, the output shows the VPI or VCI of the PVC.
• For Ethernet VLANs, the output shows the VLAN number.
• For PPP and High-Level Data Link Control (HDLC), the output shows the interface number.
|
Dest address
|
The IP address of the remote router's interface that is the other end of the VC.
|
VC ID
|
The virtual circuit identifier assigned to one of the interfaces on the router.
|
Status
|
The status of the VC. The status can be one of the following:
• ADMIN DOWN—The VC has been disabled by a user.
• DOWN—The VC is not ready to carry traffic between the two VC endpoints. Use the detail keyword to determine the reason that the VC is down.
• HOTSTANDBY—The active pseudowire on a standby route processor.
• RECOVERING—The VC is recovering from a stateful switchover.
• STANDBY—The VC is designated as the backup circuit in a stateful switchover configuration.
• UP—The VC is in a state where it can carry traffic between the two VC endpoints. A VC is up when both imposition and disposition interfaces are programmed.
– The disposition interface is programmed if the VC has been configured and the client interface is up.
– The imposition interface is programmed if the disposition interface is programmed and you have a remote VC label and an Interior Gateway Protocol (IGP) label. The IGP label can be implicit null in a back-to-back configuration. An IGP label means there is a label switched path (LSP) to the peer.
|
The following example shows information about the NSF, SSO, and graceful restart capability. The SSO portion indicates when checkpointing data has either 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 shown.
Router# show mpls l2transport vc detail
Local interface: Fa5/1/1.2 down, line protocol down, Eth VLAN 2 up
Destination address: 10.55.55.2, VC ID: 1002, VC status: down
Output interface: Se4/0/3, imposed label stack {16}
Preferred path: not configured
Tunnel label: imp-null, next hop point2point
Create time: 02:03:29, last status change time: 02:03:26
Signaling protocol: LDP, peer 10.55.55.2:0 down
MPLS VC labels: local 16, remote unassigned
Group ID: local 0, remote unknown
MTU: local 1500, remote unknown
Remote interface description:
Sequencing: receive disabled, send disabled
SSO Descriptor: 10.55.55.2/1002, local label: 16
SSM segment/switch IDs: 12290/8193, PWID: 8193
packet totals: receive 0, send 0
byte totals: receive 0, send 0
packet drops: receive 0, send 0
The following example shows information provided 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 PE routers and this is not done on static pseudowires.
Router# show mpls l2transport vc detail
Local interface: Et1/0 up, line protocol up, Ethernet up
Destination address: 10.1.1.2, VC ID: 100, VC status: up
Output interface: Et2/0, imposed label stack {10003 150}
Preferred path: not configured
Create time: 00:18:57, last status change time: 00:16:10
Signaling protocol: Manual
MPLS VC labels: local 100, remote 150
Group ID: local 0, remote 0
MTU: local 1500, remote 1500
Remote interface description:
Sequencing: receive disabled, send disabled
packet totals: receive 219, send 220
byte totals: receive 20896, send 26694
packet drops: receive 0, send 0
The following example shows the VC statistics displaying the number of packets and bytes being sent from the router. The VC statistics fields include the word "transit" to show that the packet totals no longer include packets being sent to the router.
Router# show mpls l2transport vc detail
Local interface: Et1/0 up, line protocol up, Ethernet up
transit packet totals: receive 219, send 220
transit byte totals: receive 20896, send 26694
transit packet drops: receive 0, send 0
Table 98 describes the significant fields shown in the displays.
Table 98 show mpls l2transport vc detail Field Descriptions
Field
|
Description
|
Local interface
|
Interface on the local router that has been enabled to send and receive Layer 2 packets. The interface varies, depending on the transport type. The output also shows the status of the interface.
|
line protocol
|
Status of the line protocol on the edge-facing interface.
|
Destination address
|
IP address of the remote router specified for this VC. You specify the destination IP address as part of the mpls l2transport route command.
|
VC ID
|
Virtual circuit identifier assigned to the interface on the router.
|
VC status
|
Status of the VC, which is one of the following:
• Admin down—The VC has been disabled by a user.
• Down—The VC is not ready to carry traffic between the two VC endpoints.
• up—The VC is in a state where it can carry traffic between the two VC endpoints. A VC is up when both imposition and disposition interfaces are programmed.
– The disposition interface is programmed if the VC has been configured and the client interface is up.
– The imposition interface is programmed if the disposition interface is programmed and a remote VC label and an IGP label exist. The IGP label can be an implicit null in a back-to-back configuration. (An IGP label means there is an LSP to the peer.)
|
Output interface
|
Interface on the remote router that has been enabled to transmit and receive Layer 2 packets.
|
imposed label stack
|
Summary of the MPLS label stack used to direct the VC to the PE router.
|
Preferred path
|
Path that was assigned to the VC and the status of that path. The path can be a Multiprotocol Label Switching (MPLS) traffic engineering tunnel or an IP address or hostname of a peer PE router.
|
Default path
|
Status of the default path, which can be disabled or active.
By default, if the preferred path fails, the router uses the default path. However, you can disable the router from using the default path when the preferred path fails by specifying the disable-fallback keyword with the preferred-path command.
|
Tunnel label
|
An IGP label used to route the packet over the MPLS backbone to the destination router with the egress interface. The first part of the output displays the type of label. The second part of the output displays the route information.
The tunnel label information can display any of the following states:
• imp-null: Implicit null means that the provider (P) router is absent and the tunnel label will not be used. Alternatively, imp-null can signify traffic engineering tunnels between the PE routers.
• no adjacency: The adjacency for the next hop is missing.
• no route: The label is not in the routing table.
• not ready, Cisco Express Forwarding disabled: Cisco Express Forwarding is disabled.
• not ready, LFIB entry present: The tunnel label exists in the Label Forwarding Information Base (LFIB), but the VC is down.
• not ready, LFIB disabled: The MPLS switching subsystem is disabled.
• not ready, no route: An IP route for the peer does not exist in the routing table.
• not ready, not a host table: The route in the routing table for the remote peer router is not a host route.
• unassigned: The label has not been assigned.
|
Create time
|
The time (in hours, minutes, and seconds) when the VC was provisioned.
|
last status change time
|
Last time (in hours, minutes, and seconds) the VC state changed.
|
Signaling protocol
|
Type of protocol used to send the MPLS labels on dynamically configured connections. The output also shows the status of the peer router. For AToM statically configured pseudowires, the field indicates Manual, because there is no exchange of labels using a directed control protocol such as LDP.
|
MPLS VC labels
|
Local VC label is a disposition label, which determines the egress interface of an arriving packet from the MPLS backbone. The remote VC label is a disposition VC label of the remote peer router.
|
Group ID
|
Local group ID is used to group VCs locally. The remote group ID is used by the peer to group several VCs.
|
MTU
|
Maximum transmission unit specified for the local and remote interfaces.
|
Remote interface description
|
Interface on the remote router that has been enabled to transmit and receive Layer 2 packets.
|
Sequencing
|
Indicates whether sequencing of out-of-order packets is enabled or disabled.
|
SSO Descriptor
|
Identifies the VC for which the information was checkpointed.
|
local label
|
The value of the local label that was checkpointed (that is, sent on the active Route Processor [RP], and received on the standby RP).
|
SSM segment/switch IDs
|
The IDs used to refer to the control plane and data plane for this VC. This data is not for customer use but for Cisco personnel for troubleshooting purposes. When the Source Specific Multicast (SSM) IDs are followed by the word "used," the checkpointed data has been successfully sent and not released.
|
PWID
|
The pseudowire ID used in the data plane to correlate the switching context for the segment mentioned with the MPLS switching context. This data is not for customer use but for Cisco personnel for troubleshooting purposes.
|
packet totals
|
Number of packets sent and received. Received packets are those AToM packets received from the MPLS core. Sent packets are those AToM packets sent to the MPLS core. This does not include dropped packets.
Note If the VC statistics fields include the word "transit," the output shows the number of packets and bytes being sent from the router.
|
byte totals
|
Number of bytes sent and received from the core-facing interface, including the payload, control word if present, and AToM VC label.
Note If the VC statistics fields include the word "transit," the output shows the number of packets and bytes being sent from the router.
|
packet drops
|
Number of dropped packets.
Note If the VC statistics fields include the word "transit," the output shows the number of packets and bytes being sent from the router.
|
The following example shows the command output of the show mpls l2transport vc detail command when the VPLS Autodiscovery feature has configured on the VPLS pseudowires. The output that is specific to VPLS Autodiscovery is show in bold.
Router# show mpls l2transport vc detail
Local interface: VFI my_test VFI up
MPLS VC type is VFI, interworking type is Ethernet
Destination address: 10.3.3.1, VC ID: 123456, VC status: up
Next hop PE address: 10.55.55.2
Output interface: Et3/0, imposed label stack {17 19}
Preferred path: not configured
Create time: 2d05h, last status change time: 2d05h
Signaling protocol: LDP, peer 10.55.55.2:0 up
MPLS VC labels: local 21, remote 19
AGI: type 1, len 8, 0000 3333 4F4E 44C4
Local 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 0
MTU: local 1500, remote 1500
Remote interface description:
Sequencing: receive disabled, send disabled
packet totals: receive 22611, send 22611
byte totals: receive 2346570, send 2853581
packet drops: receive 0, send 0
Table 99 describes the fields shown in the display.
Table 99 show mpls l2transport vc detail Field Descriptions for VPLS Autodiscovery
Field
|
Description
|
Next hop PE address
|
The IP address of the next hop router.
|
AGI
|
The attachment group identifier (AGI).
|
Local AII
|
The attachment individual identifier (AII). The local IP address used for signaling.
|
Remote AII
|
The remote IP address used for signaling. This address is the provisioned IP address, which might not be the same as the LDP peer IP address.
|
The following example shows sample output from the show mpls l2 transport vc command when the CEM interface is specified.
Router# show mpls l2transport vc interface CEM 3/1/1
Local intf Local circuit Dest address VC ID Status
---------- ------------- ------------ ----- ------
CE3/1/1 CESOPSN Basic 10.30.30.3 300 DOWN
The following example 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 detail
Local interface: VFI TEST VFI up
MPLS VC type is VFI, interworking type is Ethernet
Destination address: 10.1.1.1, VC ID: 1000, VC status: up
Output interface: Se2/0, imposed label stack {17}
Preferred path: not configured
Create time: 00:04:34, last status change time: 00:04:15
Signaling protocol: LDP, peer 10.1.1.1:0 up
Targeted Hello: 10.1.1.1(LDP Id) -> 10.1.1.1
MPLS VC labels: local 16, remote 17
Group ID: local 0, remote 0
MTU: local 1500, remote 1500
Remote interface description:
MAC Withdraw: sent 5, received 3
Sequencing: receive disabled, send disabled
packet totals: receive 0, send 0
byte totals: receive 0, send 0
packet drops: receive 0, send 0
The following example 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 detail
Local interface: Et1/0 up, line protocol up, Ethernet up
Destination address: 10.1.1.1, VC ID: 456, VC status: up
Output interface: Et2/0, imposed label stack {10005 10240}
Preferred path: not configured
Create time: 00:39:30, last status change time: 00:26:48
Signaling protocol: LDP, peer 10.1.1.1:0 up
Targeted Hello: 10.1.1.2(LDP Id) -> 10.1.1.1
Status TLV support (local/remote) : enabled/supported
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: PW DOWN(rx,tx fau