Configuring OTV - Site Redundancy - Multiple AEDs

In this blogtorial we are going to expand on my previous blogtorial "Configuring OTV - OTV Configuration and Verification" and configure an extra AED on the West Site to achieve site redundancy.

Here is the topology.

Since the underlay network configurations are the same, please see my previous blogtorial for that part of the configuration.

Configuring OTV - Unicast Transport Mode - OTV Adjacency Server

In this blogtorial, we will be configuring OTV using unicast-only transport mode as opposed to using multicast to discover neighbors etc. In order to use unicast-only transport, we have to enable and configure OTV Adjacency Server feature. Please see previous blogtorial (Configuring OTV - OTV Configuration and Verification) if you want more information on configuring OTV using multicast.

This topology is the same as my previous blogtorial.

What is an OTV Adjacency Server?

"Overlay Transport Virtualization (OTV) provides support for nonmulticast-capable, unicast-only core networks through the OTV Adjacency Server feature. An edge device is configured as an adjacency server (primary or secondary). All other edge devices are configured with the IPv4 addresses of the primary and secondary adjacency servers, after which the edge devices communicate their reachability and capability information to the primary and secondary adjacency servers. Wide-Area Networking Configuration Guide: Overlay Transport Virtualization, Cisco IOS XE Release 3S 2 OTV Adjacency Server Restrictions for OTV Adjacency Server You can configure more than one adjacency server per VPN. An adjacency server can serve multiple VPNs. An adjacency server can also connect an OTV site to one or more VPNs." - Cisco.com

First let's get the IP and the transport layer or the underlay network configured.

We will start with the East site.