Quick notes on OTV. I have not put this on lab gear yet so there may be typos. It does require licensing so make sure you have that budgeted, if not its a 20kish surprise which sucks.
|
1 2 3 4 5 6 7 |
#enable the feature</br> feature otv</br> #create site Vlan</br> vlan 200</br> name otv-overlay-vlan |
#The Overlay interface ID (int overlay1) must match at both sites. A Vlan can only be assigned to one overlay.
|
1 2 3 |
otv site-identifier 250 |
#Join-interface. From what I see this interface has to be physical or a subint on a physical. I would have thought that we could use a loopback or SVI but everything I see has only physical interfaces. I saw mention of loopback support in future SW releases. I would like to have that interface in an MPLS/VPN vrf but need to lab if that is able. If not it would need to route in the IGP.
|
1 2 3 4 5 6 7 8 |
int fas 4/1</br> desc ovlay-phy-int-to-DCI</br> no switch</br> mtu 9216</br> ip add 192.168.200.1/24</br> ip igmp version 3 |
#Create the logical Overlay interface. The site identifier needs to be unique per location. If two nodes at one site are in the same DC it should match. Each data center needs to be unique.
|
1 2 3 4 5 6 7 8 9 |
interface Overlay1</br> descrip Overlay-virt-interface</br> otv control-group 239.1.1.1</br> otv data-group 232.1.1.0/28</br> otv join-interface ethernet 4/1</br> #Extend the Vlan</br> otv extend-vlan 50-55 |
I will add FHRP once I lab it up. Looks a bit cumbersome with VACLs.
