I am trying to get OTV up and running through VRF between 2 sites but it seems that the OTV-isis is not forming an adjacency. There is a dark fiber between the sites so no SP interference.
2013 Sep 30 14:37:38.418027 isis_otv default : (Overlay1) : LAN adj L1 8478.ac1f.e944 over Overlay1 - DOWN (Delete All)
2013 Sep 30 14:32:27.591791 isis_otv default : (Overlay1) : LAN adj L1 8478.ac1f.e944 over Overlay1 - DOWN (Hold timer expired)
2013 Sep 30 14:32:27.591782 isis_otv default : (Overlay1) : Hold timer expired for adjacency 8478.ac1f.e944 over interface Overlay1 level 1
2013 Sep 30 14:32:14.019032 isis_otv default : (Overlay1) : Set adjacency 8478.ac1f.e944 over Overlay1 IPv4 address to 10.8.6.241
2013 Sep 30 14:32:14.018975 isis_otv default : (Overlay1) : LAN adj L1 8478.ac1f.e944 over Overlay1 - INIT (New)
2013 Sep 30 14:32:14.018957 isis_otv default : : Initialize adj for L1 MT-0 for iib Overlay1
2013 Sep 30 14:20:57.911859 isis_otv default : (Overlay1) : LAN adj L1 8478.ac1f.e944 over Overlay1 - DOWN (Hold timer expired)
I can ping all join interfaces from the edge devices, and multicast is configured for the VRFs.
I have attached the config for the two locations. Any feedback would be greatly appreciated.
Forgot to mention that ip pim sparse-mode is configured on all interfaces along the path (except for the join interface ofcourse.)
Maybe the config isn't showing it but the OTV join-interface hasn't been put in the VRF context for OTV.
Also can you check the join interfaces you've defined in the config as they appear to be the other sites join interface
Sorry, that is a copy paste fault on my part. You are correct that the interfaces for the other site.
The interfaces for the VRF are on the MPLS VDC which are members of the correct VDC.
If that is the case and it is all correct, I suppose the thing to troubleshoot would be the multicast.
When the adjacency interface is created it should do an ISIS hello - e.g. on Site 1 it should be from 10.8.6.254 to 220.127.116.11
Is this (S,G) entry showing up in the multicast routing table? Does the entry in the OIL make sense?
Yes the route is shown in the mroute table. (it has been up a short time cause I am messing around with it)
H1-MPLS# sh ip mroute vrf OTV
IP Multicast Routing Table for VRF "OTV"
(10.8.6.254/32, 18.104.22.168/32), uptime: 00:01:40, pim mrib ip
Incoming interface: mti21, RPF nbr: 10.8.0.3, internal
Outgoing interface list: (count: 1)
mti21, uptime: 00:00:29, pim, (RPF)
Unable to ping 22.214.171.124. I figured out last night that it must be something with multicast, but am still working on it. Any tips on how to go about troubleshooting?
Well I think you've done it right but I bet that there is some intricacies with VRF-based Multicast Routing on Nexus 7K.
I wonder if it would be possible to test it using the global VRF? Is this still in a development environment?
Yes, we are currently developing/configuring the equipment to be rolled out at a later date.
The odd thing is that I see the pim neighbors in the OTV vrf, indicating that it is setup correctly...I would think. I will test by setting it up in the default/global vrf and get back to you. Will not be able to do this before tomorrow or perhaps Thursday though.