[Contents]
[Prev]
[Next]
[Index]
[Report an Error]
Supported TLVs
Table 59 lists the TLVs
supported by the MPLS LSP ping feature. Table 60 lists the sub-TLVs supported for the Target FEC Stack TLV.
Table 59: TLVs Supported
by MPLS LSP ping
|
Type Number
|
Value
|
Comments
|
|
1
|
Target FEC Stack
|
Multiple FEC stack sub-TLVs are not supported. A single LSP
ping message cannot have more than one target FEC stack TLV.
|
|
2
|
Downstream Mapping
|
Only the IPv4 (numbered or unnumbered) downstream address type
is supported.
Flag I for the Interface and Label Stack object is supported.
Flag N, to treat the packet as a non-IP packet, is not supported.
An MPLS LSP trace echo request includes this TLV. This TLV contains
the downstream address all-routers-multicast; that is the well-known
IP address 224.0.0.2. Validation of the downstream address is not
performed.
Verification of the downstream address is not performed on receipt
of an MPLS echo request that contains this TLV.
In an MPLS echo reply, multipath information is not supported
in this TLV; the multipath type is always set to 0 in the reply. However,
the reply includes one downstream mapping TLV for each downstream
path.
|
|
3
|
Pad
|
This TLV is included in the MPLS echo request packet. The TLV
can specify either “ Do not reply” or “ Reply via
an IPv4/IPv6 UDP packet.”
|
|
7
|
Interface and Label Stack
|
This TLV is generated if requested by the received downstream
mapping TLV.
|
|
9
|
Errored TLVs
|
This TLV is generated if an error is encountered while parsing
one of the received TLVs.
|
|
10
|
Reply TOS Byte
|
–
|
Table 60: Sub-TLVs
Supported for the Target FEC Stack TLV
|
Subtype Number
|
Value
|
Comments
|
|
1
|
LDP IPv4 prefix
|
–
|
|
2
|
LDP IPv6 prefix
|
–
|
|
3
|
RSVP IPv4 LSP
|
–
|
|
6
|
VPN IPv4 prefix
|
–
|
|
7
|
VPN IPv6 prefix
|
–
|
|
8
|
L2 VPN endpoint
|
For VPLS and VPWS
|
|
10
|
FEC 128 pseudowire
|
For Martini encapsulation
|
To send an MPLS echo request packet to the specified
IP or IPv6 address:
- Issue the ping mpls command.
- host1:pe1#ping mpls ip 10.2.2.2/32
To send MPLS echo request packets to discover and
examine the path MPLS packets follow to the specified IP or IPv6 address:
- Issue the trace mpls ip command.
- host1:pe1#trace mpls ip 192.168.25.1/32
To send an MPLS echo request packet to the specified
layer 2 cross-connect virtual (Martini) circuit:
- Issue the ping mpls l2transport command.
- host1:pe1#ping mpls l2transport FastEthernet1/0.1
detail
To send MPLS echo request packets to discover and
examine the path MPLS packets follow to the specified layer 2 cross-connect
virtual (Martini pseudowire) circuit:
- Issue the trace mpls l2transport command.
- host1:pe1#trace mpls l2transport FastEthernet1/0.1
detail
To send an MPLS echo request packet to the specified
L3VPN IP or IPv6 prefix:
- Issue the ping mpls l3vpn command.:
- host1:pe1#ping mpls l3vpn vrf pe11 10.32.45.21/32
To send MPLS echo request packets to discover and
examine the path MPLS packets follow to the L3VPN IP or IPv6 prefix:
- Issue the trace mpls l3vpn command.
- host1:pe1#trace mpls l3vpn vrf pe11 10.2.3.21/32
To send an MPLS echo request packet to the specified
RSVP-TE tunnel:
- Issue the ping mpls rsvp command.
- host1:pe1#ping mpls rsvp tunnel west1
To send MPLS echo request packets to discover and
examine the path MPLS packets follow to the specified RSVP-TE tunnel:
- Issue the trace mpls rsvp tunnel command.
- host1:pe1:pe11#trace mpls rsvp tunnel west1
detail
To send an MPLS echo request packet to the specified
VPLS instance:
- Issue the ping mpls vpls command.
- host1:pe1#ping mpls vpls vrf pe11 vplsA remote-site-id
2
To send MPLS echo request packets to discover and
examine the path MPLS packets follow to the specified VPLS instance:
- Issue the trace mpls vpls command.
- host1:pe1#trace mpls vpls vrf pe11 vplsA remote-site-id
2 detail
Related Topics
[Contents]
[Prev]
[Next]
[Index]
[Report an Error]
