11-29-2016 08:26 PM - last edited on 03-25-2019 01:30 PM by ciscomoderator
Hi,
I have two data centers, and i try to configuration OTV between Cisco ASR routers on this data centres.
So, i use ASR1002 as unicast otv adjacency-server , and extend vlan 990 between sites. On С6506 and N7k i configured SVI interfaces vlan990.
Now, overlay is up, sites is up, but svi interfaces on switches do not ping each other.
DC1
gw-amur-go#sh otv isis neighbors
Tag Overlay1:
System Id Type Interface IP Address State Holdtime Circuit Id
gw-bel-cod02 L1 Ov1 10.230.152.6 UP 26 gw-amur-go.01
Tag Site:
System Id Type Interface IP Address State Holdtime Circuit Id
DC2
Tag Overlay1:
System Id Type Interface IP Address State Holdtime Circuit Id
gw-amur-go L1 Ov1 10.230.152.5 UP 8 gw-amur-go.01
Tag Site:
System Id Type Interface IP Address State Holdtime Circuit Id
so, in need help)
all configurations in attachment
12-06-2016 10:13 PM
Before activating the internal interface , it is recommended to enable the Join interface and the OTV Overlay interface. Once it is verified that the edge device discovered the other OTV edge devices and established control plane adjacencies via the Overlay interface, it is possible to enable the internal interface
12-27-2016 01:41 AM
Hello, Sergey!
For such a kind of the DCI, don't use OTV - it's a point-to-point link, you'll be fine even with L2TPv3. One more reason not to run OTV is that you won't be able to make this DCI secure - config with an IPSec tunnel as underlay is still pretty unstable.
So, my assumption would be to move away from OTV in a such topology and stick to L2TPv3+IPSec.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide