Igp Route Resolution To A Ldp Ipv6 Fec; Oam Support With Ldp Ipv6 - Alcatel-Lucent 7450 Manual

Note that a static route of an IPv6 prefix cannot be resolved to an indirect next-hop using a LDP
IPv4 FEC. An IPv6 prefix can only be resolved to an IPv4 next-hop using the 6-over-4
encapsulation by which the outer IPv4 header uses system IPv4 address as source and the next-hop
as a destination. So the following example will return an error:
A:SRU4>config>router# static-route 3ffe::30/128 indirect 110.20.1.1
tunnel-next-hop resolution-filter ldp
MINOR: CLI LDP not allowed for 6over4.

IGP Route Resolution to a LDP IPv6 FEC

LDP IPv6 shortcut for IGP IPv6 prefix is supported. The following commands allow a user to
select if shortcuts must be enabled for IPv4 prefixes only, for IPv6 prefixes only, or for both.
config>router>ldp-shortcut [ipv4][ipv6]
This CLI command has the following behaviors:
•
•
•

OAM Support with LDP IPv6

MPLS OAM tools lsp-ping and lsp-trace are updated to operate with LDP IPv6 and support the
following:
•
•
•
•
7450 ESS MPLS Guide
ldp-shortcut [ipv4][ipv6]
no ldp-shortcut
When executing a pre-Release 13.0 config file, the existing command is converted as
follows:
config>router>ldp-shortcut changed to config>router>ldp-shortcut ipv4
If the user enters the command without the optional arguments in the Release 13.0 CLI, it
defaults to enabling shortcuts for IPv4 IGP prefixes:
config>router>ldp-shortcut changed to config>router>ldp-shortcut ipv4
When the user enters both IPv4 and IPv6 arguments in the Release 13.0 CLI, shortcuts for
both IPv4 and IPv6 prefixes are enabled:
config>router>ldp-shortcut ipv4 ipv6
use of IPv6 addresses in the echo request and echo reply messages, including in DSMAP
TLV, as per RFC 4379
use of LDP IPv6 prefix target FEC stack TLV as per RFC 4379
use of IPv6 addresses in the DDMAP TLV and FEC stack change sub-TLV, as per
RFC 6424
use of 127/8 IPv4 mapped IPv6 address; that is, in the range ::ffff:127/104, as the
destination address of the echo request message, as per RFC 4379.
Label Distribution Protocol
Page 613