An AToM VC advertises its AToM VCCV disposition capabilities in both directions: that is, from the
originating device (PE1) to the destination device (PE2), and from PE2 to PE1.
In some instances, AToM VCs might use different switching types if the two endpoints have different AToM
VCCV capabilities. If PE1 supports Type 1 and Type 2 AToM VCCV switching and PE2 supports only Type
2 AToM VCCV switching, there are two consequences:
•
LSP ping packets sent from PE1 to PE2 are encapsulated with Type 2 switching.
•
LSP ping packets sent from PE2 to PE1 use Type 1 switching.
You can determine the AToM VCCV capabilities advertised to and received from the peer by entering the
show mpls l2transport binding command at the PE device. For example:
Device# show mpls l2transport binding
Destination Address: 10.131.191.252, VC ID: 333
Local Label: 16
Cbit: 1, VC Type: FastEthernet, GroupID: 0
MTU: 1500, Interface Desc: n/a
VCCV Capabilities: Type 1, Type 2
Remote Label: 19
Cbit: 1, VC Type: FastEthernet, GroupID: 0
MTU: 1500, Interface Desc: n/a
VCCV Capabilities: Type 1
Command Options for ping mpls and trace mpls
MPLS LSP Ping and Traceroute command options are specified as keywords and arguments on the ping mpls
and trace mpls commands.
The ping mpls command provides the options displayed in the command syntax below:
ping mpls ipv4{destination-address/destination-mask [destination address-start
address-end increment] [ttl time-to-live] | pseudowire ipv4-address
vc-id vc-id [destination address-start address-end increment] |
traffic-eng tunnel-interface tunnel-number [ttl time-to-live]} [source
source-address] [repeat count] [timeout seconds][{size
packet-size} | {sweep minimum maximum size-Increment}] [pad pattern]
[reply mode {ipv4|router-alert}] [interval msec]
[exp exp-bits] [verbose]
The trace mpls command provides the options displayed in the command syntax below:
trace mpls {ipv4 destination-address/destination-mask [destination
address-start [address-end [address-increment]]] | traffic-eng tunnel tunnel-interface-number}
[source source-address] [timeout seconds] [reply mode reply-mode]
[ttl maximum-time-to-live] [exp exp-bits]
Selection of FECs for Validation
A label switched path (LSP) is formed by labels. Devices learn labels through the Label Distribution Protocol
(LDP), traffic engineering (TE), Any Transport over Multiprotocol Label Switching (AToM), or other MPLS
applications. You can use MPLS LSP Ping and Traceroute to validate an LSP used for forwarding traffic for
a given Forwarding Equivalence Class (FEC). The table below lists the keywords and arguments for the ping
mpls and traceroute mpls commands that allow the selection of an LSP for validation.
MPLS Basic Configuration Guide, Cisco IOS XE Everest 16.5.1 (Cisco ASR 900 Series)
71
MPLS LSP Ping, Traceroute, and AToM VCCV
Command Options for ping mpls and trace mpls