Packet Flows To L3Vpn Ipv6 Prefixes; Troubleshooting Mtu Problems In Point-To-Point Lsps - Juniper JUNOSE 11.2.X BGP AND MPLS Configuration Manual

Packet Flows to L3VPN IPv6 Prefixes

Related Topics

Troubleshooting MTU Problems in Point-to-Point LSPs

Copyright © 2010, Juniper Networks, Inc.
Packet flow for an MPLS ping and trace to an L3VPN IPv6 prefix is the same as for an
IPv4 prefix except that the echo request packets and echo reply packets contain the VPN
IPv6 sub-TLV instead of the VPN IPv4 sub-TLV.
Verifying and Troubleshooting MPLS Connectivity on page 370
ping mpls ip
ping mpls l2transport
ping mpls l3vpn
ping mpls rsvp tunnel
ping mpls vpls
trace mpls ip
trace mpls l2transport
trace mpls l3vpn
trace mpls rsvp tunnel
trace mpls vpls
In an MPLS-enabled network with point-to-point LSPs, you can use the data-size keyword
with the ping mpls command to detect MTU failures in different types of MPLS
applications and network topologies. You can use the data-size keyword to troubleshoot
MTU problems in point-to-point MPLS LSPs to determine whether MPLS packets with
a particular size can be forwarded over an MPLS point-to-point LSP, when the size of
the packets exceeds the MTU size at any of the LSRs that are nodes of the LSP. If you
specify the packet size for MPLS echo requests, you can determine the exact LSR where
the MTU size is exceeded and the MPLS packets are discarded.
Tasks to verify and troubleshoot MTU problems in point-to-point LSPs are:
Troubleshooting MTU Problems in a Point-to-Point MPLS LSP Associated with an IP
or IPv6 Address on page 380
Troubleshooting MTU Problems in a Point-to-Point MPLS LSP Associated with an
L3VPN IP or IPv6 Prefix on page 380
Troubleshooting MTU Problems in a Point-to-Point MPLS LSP Associated with a Martini
Circuit on page 380
Troubleshooting MTU Problems in a Point-to-Point MPLS LSP Associated with an
RSVP-TE Tunnel on page 380
Troubleshooting MTU Problems in a Point-to-Point MPLS LSP Associated with a VPLS
Instance on page 380
Chapter 5: Monitoring MPLS
379