Arista EOS Central - Tag

Hybrid cloud connectivity with Arista’s Extensible Operating System (EOS) and Amazon Web Services (AWS)

Posted on November 8, 2019 by Dominik Rappaport | 124 Views

Motivation The term Hybrid Cloud is not clearly defined but the most common definition is a scenario where a customer wants to combine resources in their own data centre (the private cloud) with resources in the public cloud. To allow these services to communicate, a connection between the two cloud environments needs to be established. Most cloud providers offer two options: An Internet Protocol Security (IPsec)-based Virtual Private Network (VPN) connection using the Internet as a transport media and a private link using dedicated lines or equivalent technology. In this article, we cover the VPN based approach using EOS-based services...
Continue reading →

ClearPass TACACS+ Authorization with CVP

Posted on January 15, 2019 by Tamas Plugor | 1028 Views

ClearPass TACACS+ Authorization with CVP Introduction The purpose of this article is to learn how to correctly set up the TACACS+ service in Aruba ClearPass in order to successfully authenticate on the CVP GUI as a network admin. Our goal is to configure ClearPass Policy Manager [CPPM] to send us the cvp-roles=network-admin attribute in the TACACS+ Authorization reply packet. By default this does not happen, because cvp-roles is a custom attribute that has to be added to the TACACS+ dictionary on any type of TACACS+ implementation. Without this, the default role of network-operator will be allocated to the user, that...
Continue reading →

Candidate Configuration and Active Configuration type features?

Posted on June 4, 2018 by Nicholas Sheridan | 0 Views

Hi Forum, In the linux world I work with text files, I edit then (submit to source control on occasion, I might even write an ansible role), then hang up a process and I have a new personality of the device. Is there an existing feature within EOS or a planned features that supports this type of action? Or is the view that with effective out of band management it’s all a bit unnecessary? My own practical experience is, sadly, I get a load of blockers for out of band (security, cost etc) and I have to “get on with...
Continue reading →

Arista Any Cloud Platform – Security Use Case

Posted on January 9, 2018 by Tom Ferranti | 458 Views

Introduction In this document we will demonstrate how to effectively leverage Arista’s vEOS Router in a Transit – Edge VPC model to satisfy a common security use case. As most companies look to move into the public cloud space, security vulnerabilities have gained more focus than ever before. Objective Provide a centralized security model within an AWS region, which will allow for ease of visibility and control. Deploying separate AWS Internet Gateways in every VPC, increases complexity and vulnerabilities in the public cloud space. Prerequisites This document assumes that you have the following architecture deployed: A Transit – Edge VPC topology deployed...
Continue reading →

Arista 7280R Series 40G/100G systems Multi-Speed Port Configuration

Posted on October 19, 2017 by Raju | 1455 Views

Overview In high performance leaf and spine networks the Arista 7280R Series enables a high level of flexibility with a common consistent architecture, with a choice of 1RU and 2RU fixed systems, 10G to 100G interface speeds and port density up to 72 ports of 40G and 60 ports of 100G. The 7280R Series include the ability for enabling multiple speeds on QSFP ports, with a per interface configuration that is optimized for the maximum overall system flexibility. On some members of the 7280R Series to maximise the total system port count, and at the same time facilitate the most...
Continue reading →

Changing the switchport default mode

Posted on April 25, 2017 by Colin MacGiollaEain | 1765 Views

By default all ports on an Arista switch are configured to be switch ports, as you would expect. If you are mostly dealing with routed ports, this behaviour may not be totally desirable. Starting in EOS-4.18.0, this behaviour is configurable e.g. we can have all interfaces in routed mode by default. switch1...11:10:56(config)#show run int et 1-4interface Ethernet1interface Ethernet2interface Ethernet3interface Ethernet4switch1...11:11:00(config)#show interface Et1-4 switchport | i Name|Switchport:Name: Et1Switchport: EnabledName: Et2Switchport: EnabledName: Et3Switchport: EnabledName: Et4Switchport: Enabled To change the default, simply issue the configuration command switchport default mode routed As you can see, all interfaces are now in routed mode by default:...
Continue reading →

VM Tracer configuration on a layer 2 switch

Posted on April 18, 2017 by Tom Ferranti | 528 Views

Introduction There are many network architectures, which include a separate network for out-of-band management. All Arista switches come with at least one designated management interface that is VRF-aware. When VM Tracer is configured on an Arista switch, by default, vCenter communication will be sourced from the management interface. There are situations where a layer 2 switch has the management interface configured in a separate VRF, not reachable from the vCenter network segment. Objective Create reachability to vCenter from layer 2 switches that have the management interface configured in a separate VRF, not reachable from the vCenter network segment. Prerequisites Proper VM Tracer configuration...
Continue reading →

Arista 7280QR-C36 Load Balancing Optimization for Dual Homed Systems and Networks

Posted on December 21, 2016 by Martin | 1634 Views

Arista 7280QR-C36 The Arista DCS-7280QR-C36 switch is a purpose built flexible fixed configuration 1RU system capable of supporting a wide range of interface choices. Its designed for the highest performance environments such as IP Storage, Content Delivery Networks, Data Center Interconnect and IP Peering. The 7280QR-C36 is optimized for environments with dual connected nodes such as storage and for spine applications with dual homed leaf switches. This technical application note describes the internal optimized load-balancing mechanism used within the switch and how network architects can best deploy this system to maximize overall system performance. The internal architecture of the DCS-7280QR-C36...
Continue reading →

Enabling Passive/Transparent Devices for PTP Multicast Routing

Posted on December 8, 2016 by Kelsey Skemp | 771 Views

MLAG ISSU

Posted on June 28, 2016 by Upasana Dangi | 8217 Views

Overview MLAG ISSU (In-Service Software Upgrade) upgrades EOS software on one MLAG peer with minimal traffic disruptions on active MLAG interfaces and without changing the network topology. Note: Traffic impact could be seen for orphan links, active partial links and packets in flight MLAG considerations before upgrade I. Check for configuration inconsistencies Following features should be configured consistently on each switch: VLANs Switchport configuration on port channel interfaces that are configured with an MLAG ID STP configuration (global) In EOS versions 4.15.2F onwards, we can use MLAG configuration check feature: https://eos.arista.com/eos-4-15-2f/mlag-config-check/ II. Resolve ISSU warnings Resolve the following warnings before...
Continue reading →

Config Sessions Tips

Posted on March 16, 2016 by Alexei Agueev | 12903 Views

Description: This article shows how to implement 4-eyes-principle, task separation and delegation in your network. In this particular example, you can delegate configuration preparation to the operators team, retaining the control to commit the submitted changes, and having a delayed roll-back as a safety network in case something went wrong. Please also refer to the article “How to keep last X startup configs” for further tips on config handling and versioning. Since this article has been published, there have been quite a few improvements to the way EOS handles configurations sessions. Please refer to “Config Checkpoint” and “Config Session Commit...
Continue reading →

How to keep last X startup configs

Posted on April 24, 2015 by Alexei Agueev | 7066 Views

If you would like to keep track of last 10 (or more, or less) configuration changes, here’s the event-handler code to do that: event-handler config-versioning trigger on-startup-config action bash FN=/mnt/flash/startup-config; LFN="`ls -1 $FN.*-* | tail -n 1`"; if [ -z "$LFN" -o -n "`diff -I 'last modified' $FN $LFN`" ]; then cp $FN $FN.`date +%Y%m%d-%H%M%S`; ls -1r $FN.*-* | tail -n +11 | xargs -I % rm %; fi delay 0 Description: Every time the startup config gets changed, this event handler will be executed (“trigger on-startup-config”). You could increase the delay, if you wish, but now it’s engaged immediately...
Continue reading →

VMTracer ESX port configurations

Posted on March 12, 2015 by Peter | 0 Views

I am configuring a pair of new Arista 7050T switches in MLAG. My question relates to port configurations for the ports that will connect to the 6 x ESX hosts. Each host has 2 dual port NICS and 2 vDS (1 for VM and 1 for IPStorage). Each vDS has a single uplink to each NIC(2 in total) and each NIC is connected to both switches. 1. When using vmtracer is the only config I need on the port “vmtracer vmware-esx” and this implements best practices regarding spanning-tree, switchport mode, flow control etc on each port or is this command...
Continue reading →

Intelligent Bootstrap with Arista EOS and ZTPServer

Posted on August 25, 2014 by Peter Sprygada | 7406 Views

Many customers inquire about how to get started with automation into their operational networks. These conversations tend to revolve around how to reduce the operational expense and risk associated with managing data center networks. In most cases, the general consensus leads to starting automation around the bootstrap process or, in other words, how to find a better way to introduce consistency and agility into the deployment process. Arista’s early heritage grew from solving real world operational problems that enhance our customers ability to deliver massively scalable data center networks efficiently. Throughout the development process EOS has provided innovative solutions that...
Continue reading →

Introducing Arista EOS Roles for Ansible

Posted on August 19, 2014 by Peter Sprygada | 14819 Views

This article introduces the newly released Arista EOS role for Ansible. The Arista EOS role provides a set of Ansible modules that can used in playbooks for automating the configuration of network resources contained in Arista EOS nodes. The EOS role replaces the existing arista_* modules that are currently available in the Ansible distribution. The base code that comprises the EOS role has been re-worked from the beginning, influenced by lessons learned from the first generation modules. In addition, the EOS role now takes advantage of Ansible Galaxy to provide a streamlined distribution mechanism to make getting started with...
Continue reading →

Configuring Port Channel LACP Fallback on Arista Switches

Posted on July 9, 2014 by coreyhines | 17940 Views

The Port-Channel Fallback mode in Arista switches allows an active LACP interface to establish a Port Channel/LAG before it receives LACP PDU’s from its peer. This feature is useful in environments where customers have Preboot Execution Environment (PXE) Servers connected with a LACP Port Channel to the Ethernet switch. Since PXE images are very small, many operating systems are unable to leverage LACP during the preboot process. The Server NICs do not have the capability to run LACP without the assistance of a fully functional OS, and during the PXE process they are independent and have no knowledge of the...
Continue reading →

Running vEOS on ESXi 5.5

Posted on July 9, 2014 by coreyhines | 40378 Views

What is vEOS? Arista Networks vEOS is a software only version of the EOS network operating system. vEOS is meant to be run in a virtual machine environment. vEOS is useful for feature testing and especially for development of scripts and extensions. vEOS can be run on many different virtualization platforms like Virtual Box, VMware Fusion or Workstation as well as ESXi. Arista Networks has previously published how to documentation for running vEOS on other virtualization platforms and this document will extend that documentation to ESXi. What is ESXi? VMware ESXi is a server virtualization platform that supports hypervisor clustering,...
Continue reading →

DANZ TAP Aggregation Configuration: Quick Start

Posted on May 12, 2014 by Teren Sapp | 22407 Views

TAP Aggregation Overview TAP Aggregation enables N:M packet replication, unlike SPAN/mirror ports, which have limited filtering capability and only a few ports with which to mirror to. Besides that, Arista’s TAP aggregation offering enables users to leverage the extensibility of EOS – click here for a more in depth overview of TAP aggregation or contact your local account team for an in depth overview of DANZ. Enabling Tap Aggregation By default, Arista switches operate in normal switching mode. To place the switch into TAP aggregation mode, the following configuration must be added: tap aggregation mode exclusive This configuration disables all ports...
Continue reading →

TCPDUMP on an Arista switch and redirect or send output via email, SCP and TFTP

Posted on February 18, 2014 by coreyhines | 11352 Views

Sending TCPDUMP output to external servers Objective Perform tcpdump on switch to help with troubleshooting control-plane traffic e.g.m STP, OSPF, BGP, NTP etc. directed to CPU of the switch without impacting performance. Then redirect the output to email/tftp/ftp server. Prerequisites Email server SSH server TFTP server DNS Resolution Arista switch configured to send email: (read all about it here) Email example Security Considerations Arista Networks EOS supports TLS and SMTP Authentication for email. It is important to understand that this provides security, but does not guarantee security end-to-end. For example, if you send an email from a switch with TLS...
Continue reading →

Configuring LACP Fallback Individual Ports on Arista Switches

Posted on February 18, 2014 by coreyhines | 20886 Views

LACP Fallback Individual Ports Feature Overview LACP Fallback Individual Ports is a feature introduced in EOS 4.13.0 that allows all ports in a port- channel to fallback to individual switch ports when negotiation fails The feature is applied to the port-channel interface and consists of two configuration elements which will be described in the following sections Setting the port-channel to individual fallback Setting the fallback timeout Feature Operation LACP Fallback Individual Ports use cases This feature is useful for servers with multiple NICs where it is difficult to predict which NIC the server might use for PXE boot. Summary of...
Continue reading →

Tag : configuration