• Author : Tom Ferranti


Arista Any Cloud Platform – vEOS Router in Azure Deployment Guide

Introduction In this document, we will demonstrate the deployment of Arista’s vEOS Router in Microsoft Azure. A vEOS Router can be leveraged to implement various Azure architectures such as the transit-edge or hub-spoke architecture. This particular document provides a step-by-step guide to deploy vEOS Router in a transit-edge architecture in the Azure public cloud. Overview Arista’s private and public cloud infrastructure both offer significant efficiencies that make it a compelling option for workload placement.   We have proven this in the private cloud with a simple yet scalable Spine/Leaf topology utilizing industry standard protocols across all of Arista switches. With...
Continue reading →

Arista Any Cloud Platform – VM Migration

Introduction In many scenarios, resources are provisioned in the public cloud as a service, without a need to connect to a private on-prem environment. Situations will arise where connectivity is required between a public and private environment that conflict in IP space. This article will showcase how to leverage vEOS Router in AWS to establish connectivity between a VPC and a private on-prem datacenter that conflict in IP space. In this particular example, there are a hand-full of VMs that need to be migrated from AWS to a private environment. Objective Establish connectivity between the AWS VPC and the private environment. Once connectivity is established,...
Continue reading →

Arista Any Cloud Platform – Security Use Case

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 →

VM Tracer configuration on a layer 2 switch

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 →


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

Join other followers: