We have OTV working on our ASR1Ks in a lab environment. We mocked up two data centers and a simulated ISP core that supports multicast. Everything works fine. We can move hosts between data centers, drop a few pings and see the OTV table updates and connectivity restore. But that is when we're using the default VRF. When we try to put the WAN interface into a VRF (VRF-Lite) the OTV breaks. I've read in a few places that 'virtualization is supported'.
I've tried several changes relative to the use of the VRF including:
- put only the join interface in the new VRF (ELANVRF)
- instead of just using 'ip pim ssm default' I've added 'ip pim vrf ELANVRF ssm default'
- instead of just using 'ip multicast-routing distributed' I've added 'ip multicast-routing vrf ELANVRF distributed'
- I've also tried adding the 'vrf forwarding ELANVRF' to not only the join-interface (the WAN/ELAN ISP facing interface), but I've also incrementally tried adding and removing it from the overlay interface as well. But no luck. All 4 routers involved end up in the same failed OTV state.
Worthington-ASR1K-R02#sh otv
Overlay Interface Overlay1
VPN name : overlay1
VPN ID : 1
State : UP
AED Capable : No, overlay DIS not elected
IPv4 control group : 239.1.1.1
Mcast data group range(s): 232.0.0.0/8
Join interface(s) : GigabitEthernet0/0/0
Join IPv4 address : 10.99.99.2
Tunnel interface(s) : Tunnel0
Encapsulation format : GRE/IPv4
Site Bridge-Domain : 401
Capability : Multicast-reachable
Is Adjacency Server : No
Adj Server Configured : No
Prim/Sec Adj Svr(s) : None
Is the use of VRF-Lite really supported on the ASR1K and if so, what configuration elements may I be missing? I'm running 9.03.06.00.S.152-2.S on all routers involved.
Thanks,
-chris
