Release Highlights
11
Release 11.1.0
The MPLS ping feature for egress nodes in point-to-multipoint LSPs is not
supported on ES2 10G LM line modules, although these LMs support MPLS
settings. This restriction occurs because ES2 10G LMs do not forward the
received MPLS LSP ping packets to the SRP module on the router, which
disables a response to be transmitted to the originator of the request.
As part of this feature, the mplsTraffic event log category has been enhanced to
display point-to-multipoint MPLS ping and trace packets received at egress
LSRs of point-to-multipoint LSPs.
Change in existing behavior
: Existing feature extended as described here. In
lower-numbered releases, E Series routers that were egress nodes of
point-to-multipoint RSVP-TE MPLS LSPs could not respond to
point-to-multipoint MPLS ping messages (echo requests) and, therefore, could
not participate in verification of data-plane of point-to-multipoint RSVP-TE
MPLS LSPs.
Support for Troubleshooting MTU Failures in Point-to-Point MPLS LSPs
You can now determine the label-switched router (LSR) in a point-to-point LSP
at which packets are dropped from further transmission, when the size of the
packet exceeds the maximum transmission (MTU) size, and troubleshoot MTU
failures.
You can use the
data-size
keyword with the
trace mpls
command for
point-to-point LSPs in Privileged Exec and User Exec modes to specify the size
of the MPLS ping messages (echo requests) in point-to-point LSPs associated
with an IP or IPv6 address, a Martini circuit, an L3VPN IP or IPv6 prefix, an
RSVP-TE tunnel, or a VPLS instance. You can specify a size in the range 0–6400
bytes; the default size is 100 bytes.
You can use the
data-size
keyword to determine whether MPLS packets with a
particular size can be forwarded over an MPLS point-to-point LSP, when the
size of the packet exceeds the MTU size at any of the LSRs that are nodes on
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. You can use this keyword to enable the pad TLV to be
added to the MPLS LSP ping message (echo request), which results in future
MPLS LSP ping echo requests to be of the same specified number of bytes.
The following commands have been enhanced to support specification of size
of the MPLS ping message (echo request packet) to troubleshoot MTU problems
in point-to-point MPLS LSPs:
Change in existing behavior:
Existing feature extended as described here. In
lower-numbered releases, you could not use the trace function of the MPLS
ping feature to troubleshoot MTU problems in point-to-point MPLS LSPs.
trace mpls ip
trace mpls rsvp tunnel
trace mpls l2transport
trace mpls vpls
trace mpls l3vpn
