Arista vEOS, Configuration Manual, Page: 14 / 128

Figure 1: Cloud high availability network topology with vEOS router instances
In the diagram above, a virtual network is a collection of resources that are in the same cloud region. Within this
virtual network, the resources, including vEOS routers, deploy into two cloud high availability zones (Availability
Zones for AWS and Fault Domain for Azure) for fault tolerance reasons.
Note: For ease of discussion, we will use availability zone 1 and 2 to reference the high availability design
in different clouds going forward.
Within each availability zone, the hosts/VMs and vEOS interfaces are connected to their corresponding subnets
when the network is operating normally. Each subnet associates to a route table within the cloud infrastructure.
Static routes are configured in the cloud route tables so the traffic from the hosts/VMs are routed to vEOS Routers
in the corresponding availability zone as gateway or next-hop to reach certain destinations. For example, configure
a default route (0.0.0.0/0) in the cloud route table with the next-hop as vEOS Router's cloud interface ID or IP
(varies depending on the cloud). The routing policy or protocol, such as BGP, on the vEOS Routers, are user
configurable based on user's network design.
vEOS Router Configuration Guide 14