Posted on August 8, 2016 3:01 pm
 |  Asked by Jeroen Louwes
 |  1742 views
0
0
Print Friendly, PDF & Email

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 185.62.16.2

B I 185.62.16.2/32 [200/0]
via 2001:7bf:1:2::2, Ethernet1

spine1.lab.bit.nl#show ip

IP Routing : Enabled
VRRP: Configured on 0 interfaces
IP Multicast Routing : Enabled
IPv6 Interfaces Forwarding : Enabled

IPv6 Unicast Routing : Enabled

spine1.lab.bit.nl#show ip int et1

Ethernet1 is up, line protocol is up (connected)
Description: spine2.lab.bit.nl
No Internet protocol address assigned
IPv6 Interface Forwarding : Enabled
IP MTU 1500 bytes

0
Posted by ma
Answered on August 11, 2016 11:35 am

Hi Jeroen,

You *should* be able to ping across the IPv6 infrastructure from the end-hosts. Pinging between the switches is currently not supported, this will come in the future release.

Kind regards

-Michael

0
Posted by Michael Kashin
Answered on September 1, 2016 9:36 pm

Is there any chance this SW release and configuration guides become available for greater audience? I have an unprivileged minimal account (no contracts, no support) but want to play with this feature in my lab.

Post your Answer

You must be logged in to post an answer.