Examples
The output of the commands varies, depending on the type of Layer 2 packets being transported over AToM VCs.
The following sample output shows information about interfaces and VCs that have been configured to transport various Layer
2 packets on the router:
Router# show mpls l2transport 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
The table below describes the fields shown in the display.
Table 56. show mpls l2transport vc Field Descriptions
|
Field
|
Description
|
|
Local intf
|
Interface on the local router that has been enabled to transport Layer 2 packets.
|
|
Local circuit
|
Type and number (if applicable) of the local circuit. The output shown in this column varies, depending on the transport
type:
-
For Frame Relay, the output shows the DLCI of the PVC.
-
For ATM cell relay and AAL5, the output shows the VPI or VCI of the PVC.
-
For Ethernet VLANs, the output shows the VLAN number.
-
For PPP and High-Level Data Link Control (HDLC), the output shows the interface number.
|
|
Dest address
|
IP address of the remote router’s interface that is the other end of the VC.
|
|
VC ID
|
Virtual circuit identifier assigned to one of the interfaces on the router.
|
|
Status
|
Status of the VC, which can be one of the following:
-
Admin down—The VC was disabled by a user.
-
Down--The VC is not ready to carry traffic between the two VC endpoints. Use the
detail keyword to determine the reason that the VC is down.
-
Hotstandby—The active pseudowire on a standby Route Processor (RP).
-
Recovering—The VC is recovering from a stateful switchover.
-
Standby—The VC is designated as the backup circuit in a stateful switchover configuration.
-
Up—The VC can carry traffic between the two VC endpoints. A VC is up when both imposition and disposition interfaces are
programmed.
- The disposition interface is programmed if the VC has been configured and the client interface is up.
- The imposition interface is programmed if the disposition interface is programmed and you have a remote VC label and an Interior
Gateway Protocol (IGP) label. The IGP label can be implicit null in a back-to-back configuration. An IGP label means there
is a label switched path (LSP) to the peer.
|
The following sample output shows information about the nonstop forwarding (NSF), stateful switchover (SSO), and graceful
restart capabilities on the AToM VC. The SSO portion indicates whether checkpoint data has been sent (on active) or received
(on standby). When SSO data has not been successfully sent or has been released, the SSO information is not displayed.
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
Default path: active
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
VC statistics:
packet totals: receive 0, send 0
byte totals: receive 0, send 0
packet drops: receive 0, send 0
The table above and the tables below describe the fields shown in the display.
The following sample output shows the information that is displayed when an AToM static pseudowire has been provisioned and
the
show mpls l2transport vc detail command is used to check the configuration. The Signaling protocol field specifies Manual because a directed control protocol
such as Label Distribution Protocol (LDP) cannot be used to exchange parameters on static pseudowires. The remote interface
description field seen for nonstatic pseudowire configurations is not displayed because remote information is exchanged using
signaling between the Provider Edge (PE) routers and this is not done on static pseudowires.
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
Default path: active
Next hop: 10.0.0.2
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
VC statistics:
packet totals: receive 219, send 220
byte totals: receive 20896, send 26694
packet drops: receive 0, send 0
The table above and the tables below describe the fields shown in the display.
The following sample output shows VC statistics, including the number of packets and bytes being sent from the router. The
VC statistics fields include the word “transit” to indicate that the packet totals no longer include packets being sent to
the router.
Router# show mpls l2transport vc detail
Local interface: Et1/0 up, line protocol up, Ethernet up
.
.
.
VC statistics:
transit packet totals: receive 219, send 220
transit byte totals: receive 20896, send 26694
transit packet drops: receive 0, send 0
The table below describes the significant fields shown in the display.
Table 57. show mpls l2transport vc detail Field Descriptions
|
Field
|
Description
|
|
Local interface
|
Interface on the local router that has been enabled to send and receive Layer 2 packets. The interface varies, depending
on the transport type. The output also shows the status of the interface.
|
|
line protocol
|
Status of the line protocol on the edge-facing interface.
|
|
Destination address
|
IP address of the remote router specified for this VC. Specify the destination IP address as part of the
mpls l2transport route command.
|
|
VC ID
|
Virtual circuit identifier assigned to the interface on the router.
|
|
VC status
|
Status of the VC, which can be one of the following:
|
|
Output interface
|
Interface on the remote router that has been enabled to transmit and receive Layer 2 packets.
|
|
imposed label stack
|
Summary of the Multiprotocol Label Switching (MPLS) label stack used to direct the VC to the PE router.
|
|
Preferred path
|
Path that was assigned to the VC and the status of that path. The path can be an MPLS traffic engineering tunnel or an IP
address or hostname of a peer PE router.
|
|
Default path
|
Status of the default path, which can be disabled or active.
By default, if the preferred path fails, the router uses the default path. However, you can disable the router from using
the default path when the preferred path fails by specifying the
disable-fallback keyword with the
preferred-path command.
|
|
Tunnel label
|
IGP label used to route the packet over the MPLS backbone to the destination router. The first part of the output displays
the type of label. The second part of the output displays the route information.
The tunnel label information can display any of the following states:
-
imp-null: Implicit null means that the provider (P) router is absent and the tunnel label will not be used. Alternatively,
imp-null can signify traffic engineering tunnels between the PE routers.
-
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 disabled: The MPLS switching subsystem 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, no route: An IP route for the peer does not exist in the routing table.
-
not ready, not a host table: The route in the routing table for the remote peer router is not a host route.
-
unassigned: The label has not been assigned.
|
|
Create time
|
Time (in hours, minutes, and seconds) when the VC was provisioned.
|
|
last status change time
|
Last time (in hours, minutes, and seconds) the VC state changed.
|
|
Signaling protocol
|
Type of protocol used to send the MPLS labels on dynamically configured connections. The output also shows the status of
the peer router. For AToM statically configured pseudowires, the field indicates Manual because there is no exchange of labels
using a directed control protocol, such as LDP.
|
|
MPLS VC labels
|
Local VC label is a disposition label, which determines the egress interface of an arriving packet from the MPLS backbone.
The remote VC label is a disposition VC label of the remote peer router.
|
|
Group ID
|
Local group ID used to group VCs locally. The remote group ID is used by the peer to group several VCs.
|
|
MTU
|
Maximum transmission unit specified for local and remote interfaces.
|
|
Remote interface description
|
Interface on the remote router that has been enabled to transmit and receive Layer 2 packets.
|
|
Sequencing
|
Indicates whether sequencing of out-of-order packets is enabled or disabled.
|
|
SSO Descriptor
|
Identifies the VC for which the information was checkpointed.
|
|
local label
|
Value of the local label that was checkpointed (that is, sent on the active RP and received on the standby RP).
|
|
SSM segment/switch IDs
|
IDs used for the control plane and data plane for this VC. This data is not for customer use but for Cisco personnel for
troubleshooting purposes. When the Source Specific Multicast (SSM) IDs are followed by the word “used,” the checkpointed data
has been successfully sent.
|
|
PWID
|
Pseudowire ID used in the data plane to correlate the switching context for the segment associated with the MPLS switching
context. This data is not for customer use but for Cisco personnel for troubleshooting purposes.
|
|
packet totals
|
Number of packets sent and received. Received packets are those AToM packets received from the MPLS core. Sent packets are
those AToM packets sent to the MPLS core. This number excludes dropped packets.
| Note
|
If the VC statistics fields include the word “transit,” the output shows the number of packets and bytes being sent from
the router.
|
|
|
byte totals
|
Number of bytes sent and received from the core-facing interface, including the payload, control word if present, and AToM
VC label.
| Note
|
If the VC statistics fields include the word “transit,” the output shows the number of packets and bytes being sent from
the router.
|
|
|
packet drops
|
Number of dropped packets.
| Note
|
If the VC statistics fields include the word “transit,” the output shows the number of packets and bytes being sent from
the router.
|
|
The following is sample output from the
show mpls l2transport vc detail command when the VPLS Autodiscovery feature has been configured on VPLS pseudowires. The output that is specific to VPLS
Autodiscovery is shown in bold.
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
Default path:
Next hop: 10.1.0.2
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
VC statistics:
packet totals: receive 22611, send 22611
byte totals: receive 2346570, send 2853581
packet drops: receive 0, send 0
The table below describes the fields shown in the display.
Table 58. show mpls l2transport vc detail Field Descriptions for VPLS Autodiscovery
|
Field
|
Description
|
|
Next hop PE address
|
IP address of the next hop router.
|
|
AGI
|
Attachment group identifier (AGI).
|
|
Local AII
|
Attachment individual identifier (AII)—the local IP address used for signaling.
|
|
Remote AII
|
Remote IP address used for signaling. This address is the provisioned IP address, which might be different from the LDP peer
IP address.
|
The following is sample output from the
show mpls l2transport vc command when the circuit emulation (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 tables above and the tables below describes the fields shown in the display.
The following sample output displays (in bold) the number of MAC address withdrawal messages sent and received as part of
the H-VPLS N-PE Redundancy for QinQ and MPLS Access feature:
Router# show mpls l2transport vc 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
Default path: active
Next hop: point2point
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
VC statistics:
packet totals: receive 0, send 0
byte totals: receive 0, send 0
packet drops: receive 0, send 0
The tables above and the tables below describe the fields shown in the display.
The following sample output displays (in bold) the status messages for the MPLS Pseudowire Status Signaling feature when
it is enabled on both PE routers:
Router# show mpls l2transport vc 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
Default path: active
Next hop: 10.0.0.1
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 faults)
MPLS VC labels: local 2000, remote 10240
Group ID: local 6, remote 0
MTU: local 1500, remote 1500
Remote interface description:
Sequencing: receive disabled, send disabled
VC statistics:
packet totals: receive 243651, send 243705
byte totals: receive 27768366, send 34109320
packet drops: receive 0, send 0
The table below describes the fields shown in the display.
Table 59. show mpls l2transport vc detail Field Descriptions for the MPLS Pseudowire Signaling Status Feature
|
Field
|
Description
|
|
Status TLV support (local/remote)
|
For the local router, the output indicates whether the MPLS Pseudowire Signaling Status feature is enabled or disabled. For
the remote router, the output indicates whether the MPLS Pseudowire Signaling Status feature is supported.
|
|
Label/status state machine
|
The first value in the output indicates whether label advertisement has been established or not. The second value (LruRru)
indicates the status of the local and remote routers. The following list translates the status codes:
|
|
Last local dataplane status rcvd
|
Last status message received about the dataplane on the local router.
|
|
Last local SSS circuit status rcvd
|
Last status message received about the subscriber service switch (SSS) on the local router.
|
|
Last local SSS circuit status sent
|
Last status message sent about the subscriber service switch on the local router.
|
|
Last local LDP TLV status sent
|
Last status message sent about the type, length, values (TLV) on the local router.
|
|
Last remote LDP TLV status rcvd
|
Last status message received about the TLV on the local router.
|
The following sample output from the
show mpls l2transport vc detail command displays the status of multisegment pseudowires:
Router# show mpls l2transport vc detail
Local interface: Se3/0 up, line protocol up, HDLC up
Destination address: 10.12.1.1, VC ID: 100, VC status: down
Output interface: Se2/0, imposed label stack {23}
Preferred path: not configured
Default path: active
Next hop: point2point
Create time: 00:03:02, last status change time: 00:01:41
Signaling protocol: LDP, peer 10.12.1.1:0 up
Targeted Hello: 10.11.1.1(LDP Id) -> 10.12.1.1, LDP is UP
Status TLV support (local/remote) : enabled/supported
LDP route watch : enabled
Label/status state machine : established, LruRrd
Last local dataplane status rcvd: No fault
Last local SSS circuit status rcvd: No fault
Last local SSS circuit status sent: DOWN(PW-tx-fault)
Last local LDP TLV status sent: No fault
Last remote LDP TLV status rcvd: DOWN(PW-tx-fault)
PW Switching Point:
Fault type Vcid local IP addr remote IP addr Description
PW-tx-fault 101 10.13.1.1 10.12.1.1 S-PE2
Last remote LDP ADJ status rcvd: No fault
MPLS VC labels: local 19, remote 23
Group ID: local 0, remote 0
MTU: local 1500, remote 1500
Remote interface description:
Sequencing: receive disabled, send disabled
VC statistics:
packet totals: receive 16, send 27
byte totals: receive 2506, send 3098
packet drops: receive 0, seq error 0, send 0
The table below describes the significant fields shown in the display.
Table 60. show mpls l2transport vc detail Field Descriptions for the MPLS Multisegment Pseudowire Feature
|
Field
|
Description
|
|
Fault type
|
Type of fault encountered on the switching point.
|
|
Vcid
|
ID of the VC on which the fault occurred.
|
|
local IP addr
|
Local IP address of the pseudowire.
|
|
remote IP addr
|
Remote IP address of the pseudowire.
|
|
Description
|
Descriptions assigned to the segment of the pseudowire.
|
The following sample output from the
show mpls l2transport vc detail command displays the status of the control word when it is not configured (that is, it defaults to autosense):
Router# show mpls l2transport vc 123400 detail
Local interface: Et0/0 up, line protocol up, Ethernet up
Destination address: 10.1.1.2, VC ID: 123400, VC status: down
Output interface: if-?(0), imposed label stack {}
Preferred path: not configured
Default path: no route
No adjacency
Create time: 01:03:48, last status change time: 01:03:48
Signaling protocol: LDP, peer 10.1.1.3:0 up
Targeted Hello: 10.1.1.1(LDP Id) -> 10.1.1.2
Status TLV support (local/remote) : enabled/unknown (no remote binding)
Label/status state machine : local ready, LruRnd
Last local dataplane status rcvd: no fault
Last local SSS circuit status rcvd: no fault
Last local SSS circuit status sent: not sent
Last local LDP TLV status sent: no fault
Last remote LDP TLV status rcvd: unknown (no remote binding)
MPLS VC labels: local 1002, remote unassigned
Group ID: local 0, remote unknown
MTU: local 1500, remote unknown
Remote interface description:
Sequencing: receive disabled, send disabled
Control Word: on (configured: autosense)
If the control word is negotiated by the peer and is different from the configured value, the configured value is shown in
parentheses.
Control Word: off (configured: disabled)
Control Word: off (configured: enabled)
Control Word: on (configured: autosense)
The following sample output from the
show mpls l2transport vc detail command displays load balancing information and shows whether flow labels are added to the MPLS label as part of the L2VPN
Advanced VPLS feature:
Router# show mpls l2transport vc detail
Local interface: VFI dci_vlan_100 VFI up
MPLS VC type is VFI, interworking type is Ethernet
Destination address: 10.2.2.2, VC ID: 100, VC status: up
Output interface: Tu0, imposed label stack {16}
Preferred path: not configured
Default path: active
Next hop: point2point
Load Balance: Flow
Flow Label: enabled
The table below describes the significant fields shown in the display.
Table 61. show mpls l2transport vc detail Field Descriptions for the L2VPN Advanced VPLS Feature
|
Field
|
Description
|
|
Load Balance
|
Displays the type of load-balancing configured. The load-balancing configuration can be either flow-based or port channel-based.
|
|
Flow Label
|
Indicates whether the imposition and disposition of flow labels for the pseudowire is enabled.
|
The following sample output from the
show mpls l2transport vc detail command displays BFD information:
Router# show mpls l2transport vc detail
Local interface: AT1/1/0 up, line protocol up, ATM AAL5 10/101 up
Destination address: 10.1.1.151, VC ID: 1234001, VC status: up
Output interface: Gi1/0/0, imposed label stack {2000}
Preferred path: not configured
Default path: active
Next hop: 10.151.152.1
Create time: 6d03h, last status change time: 6d03h
Signaling protocol: LDP, peer 10.1.1.151:0 up
Targeted Hello: 10.1.1.152(LDP Id) -> 10.1.1.151, LDP is UP
Status TLV support (local/remote) : enabled/supported
LDP route watch : enabled
Label/status state machine : established, LruRru
Last local dataplane status rcvd: No fault
Last local SSS circuit status rcvd: No fault
Last local SSS circuit status sent: No fault
Last local LDP TLV status sent: No fault
Last remote LDP TLV status rcvd: No fault
Last remote LDP ADJ status rcvd: No fault
MPLS VC labels: local 2000, remote 2000
PWID: 20490
Group ID: local 0, remote 0
MTU: local 4470, remote 4470
Remote interface description:
Sequencing: receive disabled, send disabled
Control Word: On (configured: autosense)
VCCV BFD protection active
BFD Template - sampleBFDTemplate
CC Type - 1
CV Type - fault detection only with IP/UDP headers
VC statistics:
transit packet totals: receive 0, send 0
transit byte totals: receive 0, send 0
transit packet drops: receive 0, seq error 0, send 0
The table below describes the significant fields shown in the display.
Table 62. show mpls l2transport vc detail Field Descriptions for the BFD CC over VCCV - Support for ATM Pseudowire Feature
|
Field
|
Description
|
|
VCCV BFD protection active
|
Displays the VCCV BFD protection status.
|
|
BFD Template
|
Displays the BFD template name.
|
|
CC Type
|
Displays the CC type.
|
|
CV Type
|
Displays the Control Verification type.
|
The following is sample output from the
show mpls l2transport vc command when the L2VPN VPLS Inter-AS Option B feature has been configured. The fields in the display are self-explanatory
or described in other tables in this document.
Router# show mpls l2transport vc
Load for five secs: 4%/1%; one minute: 4%; five minutes: 2%
Time source is hardware calendar, *17:26:56.066 GMT Mon Oct 18 2010
Local intf Local circuit Dest address VC ID Status
------------- -------------------------- --------------- ---------- ----------
VFI auto VFI 10.1.1.1 100 UP
The following is sample output from the
show mpls l2transport vc detail command when the L2VPN VPLS Inter-AS Option B feature has been configured. The output that is specific to the L2VPN VPLS
Inter-AS Option B feature is shown in bold.
Router# show mpls l2transport vc detail
Load for five secs: 4%/1%; one minute: 4%; five minutes: 2%
Time source is hardware calendar, *17:27:28.076 GMT Mon Oct 18 2010
Local interface: VFI auto VFI up
Interworking type is Ethernet
Destination address: 192.0.2.1, VC ID: 100, VC status: up
Next hop PE address: 198.51.100.1
Output interface: Et1/0, imposed label stack {2012}
Preferred path: not configured
Default path: active
Next hop: 10.0.0.3
Create time: 00:00:48, last status change time: 00:00:48
Signaling protocol: LDP, peer 192.0.2.3:0 up
Targeted Hello: 192.0.2.6(from BGP) -> 192.0.2.8, LDP is UP
Status TLV support (local/remote) : enabled/supported
LDP route watch : enabled
Label/status state machine : established, LruRru
Last local dataplane status rcvd: No fault
Last local SSS circuit status rcvd: No fault
Last local SSS circuit status sent: No fault
Last local LDP TLV status sent: No fault
Last remote LDP TLV status rcvd: No fault
Last remote LDP ADJ status rcvd: No fault
MPLS VC labels: local 1011, remote 2012
PWID: 4096
AGI: type 1, len 8, 000A 0001 0000 0001
Local AII: type 1, len 4, 0101 0001 (203.0.113.1)
Remote AII: type 1, len 4, 0201 0101 (203.0.113.5)
VPLS-ID: 1:1
Group ID: local n/a, remote n/a
MTU: local 1500, remote 1500
Remote interface description:
Sequencing: receive disabled, send disabled
Control Word: On (configured: autosense)
SSO Descriptor: 203.0.113.5/100, local label: 1011
SSM segment/switch IDs: 16387/8193 (used), PWID: 4096
VC statistics:
transit packet totals: receive 0, send 0
transit byte totals: receive 0, send 0
transit packet drops: receive 0, seq error 0, send 0
The table below describes the feature-specific significant fields shown in the display.
Table 63. show mpls l2transport vc detail Field Descriptions for the L2VPN VPLS Inter-AS Option B
|
Field
|
Description
|
|
PWID
|
Pseudowire identifier.
|
|
VPLS-ID
|
The VPLS identifier associated with the pseudowire.
|
The following is sample output from the
show mpls l2transport vc detail command when there is a remote AC failure and when VCCV BFD status signaling is enabled, that is,
vccv bfd status signaling is configured.
Router# show mpls l2transport vc detail
Load for five secs: 0%/0%; one minute: 0%; five minutes: 0%
Time source is hardware calendar, *03:31:33.136 PST Thu Mar 24 2011
Local interface: Et1/0.1 up, line protocol up, Eth VLAN 1001 up
Destination address: 192.0.2.1, VC ID: 1234000, VC status: down
Output interface: Et0/0, imposed label stack {150}
Preferred path: not configured
Default path: active
Next hop: 198.58.100.2
Create time: 00:03:45, last status change time: 00:00:02
Signaling protocol: Manual
Status TLV support (local/remote) : enabled/N/A
LDP route watch : enabled
Label/status state machine : established, LruRrd
Last local dataplane status rcvd: No fault
Last BFD dataplane status rcvd: No fault
Last local SSS circuit status rcvd: No fault
Last local SSS circuit status sent: DOWN AC(rx/tx faults)
Last local LDP TLV status sent: None
Last remote LDP TLV status rcvd: DOWN AC(rx/tx faults), (UP)
Last remote LDP ADJ status rcvd: No fault
MPLS VC labels: local 100, remote 150
PWID: 4096
Group ID: local 0, remote 0
MTU: local 1500, remote 1500
Sequencing: receive disabled, send disabled
Control Word: On (configured: autosense)
VCCV BFD protection active
BFD Template - t1
CC Type - 1
CV Type - fault detection and status signaling without IP/UDP headers
VC statistics:
transit packet totals: receive 0, send 5
transit byte totals: receive 0, send 580
transit packet drops: receive 0, seq error 0, send 0
The table below describes the significant fields shown in the display.
Table 64. show mpls l2transport vc detail Field Descriptions for Remote AC Failure
|
Field
|
Description
|
|
Last BFD dataplane status rcvd
|
Last status message received about the BFD dataplane on the local router.
|
|
Last local dataplane status rcvd
|
Last status message received about the dataplane on the local router.
|
|
Last local SSS circuit status rcvd
|
Last status message received about the subscriber service switch (SSS) on the local router.
|
|
Last local SSS circuit status sent
|
Last status message sent about the subscriber service switch on the local router.
|
|
Last remote LDP ADJ
|
Last status message received about the ADJ on the local router.
|
|
VCCV BFD protection active
|
Displays the VCCV BFD protection status.
|
|
BFD Template
|
Displays the BFD template name.
|
|
CC Type
|
Displays the CC type.
|
|
CV Type
|
Displays the Control Verification type.
|
Feedback