Configuring OSPFv3 over Frame Relay
In IPv4 Frame Relay networks, you are acceptable to be accustomed with mapping IP addresses to DLCI numbers.
The agreement of frame-relay map statements is abundant the aforementioned in IPv6, but there is a twist: It requires
two map statements instead of aloof one. One map account credibility to the link-local address, and the other
points to the unicast abode of the next-hop interface. Alone the link-local mapping account requires the
broadcast keyword (which absolutely permits multicast, as there is no such affair as advertisement in IPv6). In
Example 20-8, the far-end interface’s IPv6 unicast abode is 2001::207:85FF:FE80:7208 and its linklocal
address is FE80::207:85FF:FE80:7208. The DLCI cardinal is 708.
If you configure alone the link-local mapping, OSPFv3 will be happy; the neighbors will appear up,
the routers will become absolutely adjacent, and their acquisition tables will absolutely populate. However, when
you try to accelerate IPv6 cartage to a arrangement beyond the Frame Relay cloud, it will abort because of Frame
Relay encapsulation failures.
Example 20-8 Frame Relay Mapping for IPv6
frame-relay map ipv6 FE80::207:85FF:FE80:7208 708 broadcast
frame-relay map ipv6 2001::207:85FF:FE80:7208 708
Of course, if you are able to use Inverse ARP, this affair does not appulse your configuration. Inverse
ARP works for IPv6 as it does for IPv4 and supports all configured IPv6 addresses on an interface.