• Tag : ipv6


Prefix-length support for IPv6 attached-host routes

Description This feature supports generation of non-host routes for the IPv6 neighbor entries learnt on an SVI interface. These non-host routes can further be redistributed into BGP protocol to take part in the route selection decision process and to get advertised to the peers. These routes are not installed into the hardware and are only being generated for advertisement purpose. This feature works for both static and dynamic neighbors. Neighbor generated routes are also referred to as ‘attached-host’ routes in the context of this document even though the routes are non necessarily host routes ( /128 ). A neighbor will...
Continue reading →


Description Starting with EOS release 4.22.0F, the EVPN VXLAN L3 Gateway using EVPN IRB supports routing traffic from IPV6 host to another IPV6 host on a stretched Vxlan VLAN. This TOI explains the EOS configuration and show commands. Platform compatibility Platform Supporting ND Proxy and ND Suppression DCS-7280R/7280R2 DCS-7050CX3-32S-F DCS-7050SX3-48YC12-F ( Starting in 4.22.1F ) DCS-7050SX3-48YC8 ( Starting in 4.22.1F ) DCS-7050/7050X/7050X2 ( Starting in 4.22.1F ) DCS-7260X/7260X3 ( Starting in 4.22.1F ) DCS-7060X/7060X2 ( Starting in 4.21.1F ) DCS-7250 ( Starting in 4.22.1F ) DCS-7300/DCS-7320 ( Starting in 4.22.1F ) Platform Compatibility (No ND Proxy, No ND Suppression) DCS-7020R...
Continue reading →

Event Monitor: IPv6 Route and IPv6 Neighbor Support

Description This feature extends the capabilities of event monitor to include IPv6 Route and IPv6 Neighbor event logging. Platform compatibility This feature is platform independent. Configuration Ipv6 Route/Neighbor Event Monitor is configurable with the following: [no] event-monitor {route6, neighbor} Show Commands As with other event-monitors, IPv6 events are displayed through the following command: show event-monitor {route6, neighbor} Event-monitors can also be queried using SQL commands: (config)# show event-monitor sqlite select * from route6 (config)# show event-monitor sqlite select * from route6 WHERE route6.prefix='2001:db8::/32'; Syslog Messages No additional syslog messages.

IPv6 ND Proxy

Description This feature makes a switch act as a neighbor discovery proxy for an IPv6 subnets. It can be used in conjunction with BUM suppression to turn all packet forwarding from switching to routing. Platform compatibility 7050SX3-48YC12 7050CX3-32S On the 7308 and 7304 modular systems this feature is supported with the following line cards: 7300X3-32C-LC 7300X3-48YC4-LC Configuration The feature can be activated on a per-VLAN basis, and is available in both default and non-default VRFs. As an example, consider a topology where two hosts in VLAN 100 are connected to the switch on Ethernet 1 and Ethernet 2, with IPv6...
Continue reading →

ipv6 nd ra experimental network-boot

Description This configuration command features an IPv6 Neighbor Discovery (ND) option (called Boot File URL (BFURL) option) that can be used to provide configuration information for nodes to be booted from the network. Platform Compatibility Platform independent Configuration This feature can be activated per-interface basis and it is supported in default and non default VRF. interface Vlan 100 ipv6 nd ra experimental network-boot <bootfile-url> The existing ND message (RA) is used to carry this network boot information.  Nodes can get the boot file url and parameters through RA messages via BFURL option. Show Commands None Syslog Messages None References https://tools.ietf.org/html/draft-qin-6man-nb-option-03

IPv6 Traffic Engineering in IS-IS

Description This feature implements RFC6119, which allows the extension of IS-IS protocol to carry IPv6 Traffic Engineering attributes. This information enables routers in an IS-IS network to calculate traffic-engineered routes using IPv6 addresses. Note that IS-IS in EOS only acts as a carrier for TE attributes and it is not used by any processing (e.g. SPF). The support for IPv4 Traffic Engineering for IS-IS was added in EOS-4.20.5F and that TOI  is available here. This feature is available with both the multi-agent routing protocol model and the ribd routing protocol model. Platform compatibility This feature is supported on all platforms. Configuration The...
Continue reading →

IPv6 support for PIM source specific multicast

Description This feature adds support for PIM-SSM ( Source Specific Multicast ) for IPv6 Multicast Routing on platforms listed below. The TOI for the support in earlier versions/platforms is available here. Reference TOI for support of IPv6 Multicast Routing support is available here. Basic configuration commands can be found in the aforementioned TOI for enabling Ipv6 multicast routing Platform compatibility The following platforms are supported from software version 4.22.0 DCS-7050QX, DCS-7050SX, DCS-7050TX DCS-7050QX2, DCS-7050SX2, DCS-7050TX2 DCS-7050CX3, DCS-7050SX3 DCS-7060CX, DCS-7060CX2, DCS-7060SX2 DCS-7260CX, DCS-7260CX3, DCS-7260QX DCS-7300X, DCS-7300X3 series Show Commands The below commands can be leveraged in order to view the multicast...
Continue reading →

Introduction to IPv6 Multicast-Routing

Overview IPv6 multicast routing protocols are used to distribute ipv6 datagrams to one or more recipients. IPv6 PIM builds and maintains multicast routing using reverse path forwarding (RPF) based on unicast routing table. IPv6 PIM is protocol-independent and can use routing tables consisting of OSPFv3, IPv6 BGP or static routes, for RPF lookup. MLD is used to discover multicast hosts and maintain group membership on directly attached link. IPv6 multicast-routing has been introduced in the 4.21.0F release and is supported on 7280R and 7500R. Source-specific multicast (SSM) is currently supported on L3 routed port. PIM Sparse Mode In PIM-SM, each...
Continue reading →

TAP agg IPv6 HTTP GET method.

Hi All, Can i implement TAP agg function and filter only http get method on IPv6 traffic ? on this model Arista DCS-7150S-52-CL-F Software image version: 4.18.2F-2GB Regards, Manaschai.

Overlay IPv6 routing over VXLAN

Overlay IPv6 routing over VXLAN Tunnel is simply routing IPv6 packets in and out of VXLAN Tunnels, similar to VXLAN overlay IPv4 routing. Underlay ( Outer IP Header ) in VXLAN still uses IPv4, and common for both overlay IPv4 and IPv6 . Hence VXLAN configuration remains exactly same for both IPv4 and IPv6 overlay routing support. This feature enables IPv6 networks/hosts get connected through VXLAN Tunnels. Following figure illustrates IPv6 routing followed by VXLAN encapsulation to reach a remote host across the VXLAN tunnel.   Following figure illustrates VXLAN decapsulation and routing of an IPv6 packet. Platform compatibility DCS-7050X DCS-7060X DCS7260X DCS-7050X2 DCS-7250X DCS-7304 / DCS-7308 /...
Continue reading →

IPv6 Support for Decap Groups

The document describes an extension of the decap group feature, that allows IPv6 addresses to be configured and used as part of a group. IP-in-IP packets with v6 destination matching a configured decap group IP will be decapsulated and forwarded based on the inner header. That will allow any IP-to-IP packet type to be decapsulated, i.e. v4 in v4, v4 in v6, v6 in v4 and v6 in v6. Platform compatibility DCS-7050X DCS-7500X DCS-7260X DCS-7500R DCS-7500E DCS-7280R DCS-7280E Configuration Configuration is similar to IPv4-only decap group. Additional option of configuring IPv6 address is now available after the “decap-ip” keyword. If...
Continue reading →

FHR / vARP for IPv6?

Hi All,   We have a pair of 7280SE-64’s in MLAG (80G) that act as our (current) L2 core, and we are getting ready to move our L3 services over to it. This is a private org, so not a service provider network. Using VRRP for IPv4 is straight forward and I’ve tested it on a few /24’s and it works great. My question is what is the best way to do First hop redundancy for IPv6? We need to feed a few networks with SLAAC so I’m not sure how vARP and Router Advertisements work. If anyone has any...
Continue reading →

Does Arista EOS support EUI-64?

Quick question does Arista EOS support EUI-64 addressing on interfaces? Something like: Router(config-if)# ipv6 address 2001:db8::/64 eui-64  

IPv6 layer 2 security

hi, can it be that there are no IPv6 layer 2 security features like RA Guard (described in RFC 7113) or dhcpv6 guard (described in RFC 7610) available in current eos versions? I can’t find anything about it in the documentation. How do you handle this?


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

Join other followers: