• Tag : RFC5549


RFC 5549: IPv4 unicast NLRI with IPv6 next-hop support

Description This feature provides support for advertising IPv4 unicast Network Layer Reachability Information (NLRI) with IPv6 next-hops over IPv6 peering sessions described as the Extended Next Hop Encoding capability in RFC5549. Extended Next Hop Encoding capability can be supported for IPv4 unicast, IPv4 Labeled Unicast, and IPv4 VPN address and sub-address families (1/1, 1/4, 1/128 respectively). The feature enables: Negotiating Extended Next Hop Encoding capability for IPv4 unicast NLRI advertisements over IPv6 BGP sessions. In multi-agent mode IPv4 iBGP sessions are also supported. Encoding of the next-hop in the UPDATE message that allows determination of the next-hop’s address family. This...
Continue reading →

RFC 5549 and IPv4 connection between loopbacks

I have setup a lab environment with two vEOS 4.17.0F-3277845 switches. With this i’m testing RFC 5549 support. Simple setup with a dual-stack loopback interface on both switches and an ipv6 back-2-back connection over Et1. BGP peering session over ipv6 with address families ipv4 and ipv6 active. I get ipv4 routes with ipv6 nexthops in the routing table. So far so good. But when i try to ping from loopback to loopback i get the message “ping: sendmsg: Network is unreachable“. Is there anything i’m missing here? I have followed the instructions at https://eos.arista.com/eos-4-17-0f/rfc-5549-ipv4-unicast-with-ipv6-next-hop-support/ and https://eos.arista.com/eos-4-17-0f/ip-addressless-forwarding-changes-for-bgp-v6-nexthop-for-v4-routes/ . spine1.lab.bit.nl#show ip route B...
Continue reading →


Get every new post on this blog delivered to your Inbox.

Join other followers: