No, the 9k’s global loopback is not being originated locally on the 9k. I mentioned that in the initial post. Sorry if that wasn’t clear.
All the docs I’ve read suggest that my configuration is complete, but obviously it’s not :) I have a TAC SR open, but they have been pretty much useless so far. > On Dec 3, 2014, at 8:57 AM, Vitkovský Adam <[email protected]> wrote: > > Oh and if you have the loopback in BGP -do you also see it being advertised > to the ME please? cmd: sh bgp ipv4 mdt vrf iptv advertised neighbor x.x.x.x > -looopback of the ME. > > If yes then you should debug on ME why it is not accepting the route. > > adam >> -----Original Message----- >> From: Vitkovský Adam >> Sent: Wednesday, December 03, 2014 2:53 PM >> To: 'Jason Lixfeld' >> Cc: <[email protected]> >> Subject: RE: [c-nsp] ME3600/A9K MVPN PIM VRF neighbour issues >> >> And do you see the 9k's global loopback in bgp right? cmd: "sh bgp ipv4 mdt >> vrf iptv x.x.x.x". >> -that's basically the source (s,g) info for the ME so that it knows who are >> the >> sources for the default MDT group so that it can send join towards the >> sources building the default MDT. >> >> Once that is done you should see the the (s,g) states for the default tree >> group cmd: "sh mrib route". >> >> Once the default tree is built ME and A9k should form PIM neighborship >> (within the VRF context) -they should see each other over the tunnel like >> over a LAN. >> >> >> adam >>> -----Original Message----- >>> From: Jason Lixfeld [mailto:[email protected]] >>> Sent: Wednesday, December 03, 2014 2:27 PM >>> To: Vitkovský Adam >>> Cc: <[email protected]> >>> Subject: Re: [c-nsp] ME3600/A9K MVPN PIM VRF neighbour issues >>> >>> No. The 9K sees ME3600 global loopback in the VRF over the MDT SAFI, >>> but not the other way around. I think that's where the issue is, but >>> I can't seem to pinpoint why. >>> >>> Sent from my iPhone >>> >>>> On Dec 3, 2014, at 4:32 AM, Vitkovský Adam <[email protected]> >>> wrote: >>>> >>>> Hi Jason, >>>> >>>> Have you been able to force the BGP to advertise its information via >>>> the >>> MDT SAFI? >>>> >>>> adam >>>>> -----Original Message----- >>>>> From: Jason Lixfeld [mailto:[email protected]] >>>>> Sent: Monday, December 01, 2014 9:19 PM >>>>> To: Vitkovský Adam >>>>> Cc: <[email protected]> >>>>> Subject: Re: [c-nsp] ME3600/A9K MVPN PIM VRF neighbour issues >>>>> >>>>> Hi Adam, >>>>> >>>>> - Global space loopback is lo0. This is the SIP for the MP-BGP bits. >>>>> - VRF TV loopback is lo2022 >>>>> - Adding the PIM join TLV bits didn’t seem to help at all, but >>>>> thankfully it didn’t blow apart what was already working, so that’s >>>>> good, I guess :) >>>>> - VRF TV already has the mvpn AF configured. >>>>> >>>>> ! >>>>> router bgp 21949 >>>>> vrf tv >>>>> rd 21949:2022 >>>>> address-family ipv4 unicast >>>>> redistribute connected route-policy SOURCE--INTERNAL-CONNECTED >>>>> redistribute static route-policy SOURCE--INTERNAL-STATIC >>>>> redistribute eigrp 21949 route-policy SOURCE--INTERNAL-EIGRP ! >>>>> address-family ipv4 mvpn >>>>> ! >>>>> ! >>>>> ! >>>>> multicast-routing >>>>> address-family ipv4 >>>>> interface Loopback0 >>>>> enable >>>>> ! >>>>> nsf >>>>> mdt source Loopback0 >>>>> rate-per-route >>>>> interface all enable >>>>> accounting per-prefix >>>>> ! >>>>> vrf tv >>>>> address-family ipv4 >>>>> mdt data 232.0.2.0/23 >>>>> mdt default ipv4 232.0.0.1 >>>>> mdt partitioned mldp ipv4 mp2mp >>>>> rate-per-route >>>>> interface all enable >>>>> bgp auto-discovery mldp >>>>> ! >>>>> accounting per-prefix >>>>> ! >>>>> ! >>>>> ! >>>>> router pim >>>>> address-family ipv4 >>>>> interface Loopback0 >>>>> enable >>>>> ! >>>>> interface TenGigE0/2/0/2 >>>>> enable >>>>> dr-priority 100 >>>>> ! >>>>> ! >>>>> vrf tv >>>>> address-family ipv4 >>>>> rpf topology route-policy MLDP-TV >>>>> mdt c-multicast-routing pim >>>>> announce-pim-join-tlv >>>>> ! >>>>> interface Loopback2022 >>>>> enable >>>>> ! >>>>> interface TenGigE0/0/0/15 >>>>> enable >>>>> ! >>>>> interface TenGigE0/0/0/1.4006 >>>>> enable >>>>> dr-priority 100 >>>>> ! >>>>> interface TenGigE0/2/0/5.4006 >>>>> enable >>>>> dr-priority 100 >>>>> ! >>>>> interface TenGigE0/0/0/11.4006 >>>>> enable >>>>> dr-priority 100 >>>>> ! >>>>> interface GigabitEthernet0/1/0/0.958 >>>>> enable >>>>> dr-priority 100 >>>>> ! >>>>> ! >>>>> ! >>>>> ! >>>>> >>>>> >>>>> >>>>>>> On Nov 28, 2014, at 8:10 PM, Vitkovský Adam >>>>>>> <[email protected]> >>>>>> wrote: >>>>>> >>>>>> Hi Jason, >>>>>> >>>>>> Do you have the PE loopback enabled under the router pim and >>>>>> multicast >>>>> routing (global IPv4 AF) please? >>>>>> Do you have "mdt source Loopback0" under the multicast routing >>> please? >>>>>> >>>>>> >>>>>> Also once you have that working these helped in my case to get the >>>>>> mLDP >>>>> and mGRE Rosens to live next to each other. >>>>>> >>>>>> router pim >>>>>> vrf iptv >>>>>> address-family ipv4 >>>>>> mdt c-multicast-routing pim >>>>>> announce-pim-join-tlv <---that is on 4.3.4 >>>>>> >>>>>> Prior to 4.3.0 there was a bug causing the PIM Join TLV not to be >>>>>> sent with >>>>> dual scenario. >>>>>> >>>>>> >>>>>> Also I'd like to ask did you have to enable mvpn AF under the VRF >>>>>> to get >>>>> the mLDP mVPN working (to get the type 1 routes advertised)? >>>>>> router bgp 65000 >>>>>> vrf iptv >>>>>> address-family ipv4 mvpn >>>>>> >>>>>> >>>>>> adam >>>>>>> -----Original Message----- >>>>>>> From: cisco-nsp [mailto:[email protected]] On >>>>>>> Behalf Of Jason Lixfeld >>>>>>> Sent: Friday, November 28, 2014 10:57 PM >>>>>>> To: <[email protected]> >>>>>>> Subject: [c-nsp] ME3600/A9K MVPN PIM VRF neighbour issues >>>>>>> >>>>>>> I’m trying to turn up MVPN between a 9K and an ME3600. >>>>>>> >>>>>>> - My default MDT seems OK; tunnel0 and mdt tunnels are up on the >>>>>>> ME3600 and A9K, respectively. >>>>>>> - Each box sees the correct PIM interfaces in the VRF, but only >>>>>>> the 9K sees the ME3600 as a PIM neighbour over the tunnel, the >>>>>>> ME3600 doesn’t see a PIM adjacency over the tunnel. >>>>>>> - The ME3600 (me3600-1) with the MVPN config is an MP-BGP >>> neighbour >>>>>>> of the A9K (a9k-1), but there are two other ME3600s in the middle >>>>>>> that are not a part of the MVPN. That said, each ME3600 is a PIM >>>>>>> neighbor of the other in the global table, all the way along to >>>>>>> the 9K. That >>>>> should be all I need. >>>>>>> Everything else should happen over BGP and the non-MVPN >> ME3600s >>>>>>> should be agnostic to any of that. >>>>>>> - The BGP adjacency in the MDT SAFI between me3600-1 and a9k-1 is >>>>>>> up, but what I think might be contributing to this is that the >>>>>>> A9K sees a prefix in the MDT SAFI from me3600-1, but me3600-1 >>>>>>> doesn’t see a prefix from the A9K over the MDT SAFI; there >>>>>>> doesn’t seem to be a locally originated prefix on the A9K. On >>>>>>> the ME3600, that locally sourced prefix is actually the loopback >>>>>>> in the global table is the update-source and remote peering IP >>>>>>> for the MP- BGP >>> infrastructure. >>>>> This seems fine to me, because this link: >>>>>>> >>>>>>> >> http://www.cisco.com/c/en/us/td/docs/routers/crs/software/crs_r4- >>>>> >>> 2/multicast/configuration/guide/b_mcast_cg42crs/b_mcast_cg42crs_chapt >>>>>>> er >>>>>>> _00.html#task_2665897 >>>>>>> >>>>>>> Suggests that the default behaviour in XR is the same as what I’m >>>>>>> seeing on the me3600-1, which is why the global loopback shows up >>>>>>> as an BGP-MDT learned prefix. >>>>>>> >>>>>>> It’s probably something dumb, but I’m having a hard time finding >>>>>>> any troubleshooting docs that relate to A9K/IOS intermix for this >>>>>>> sort of >>>>> topology. >>>>>>> >>>>>>> I’ve already got LSM working across my A9K backbone; I just hope >>>>>>> it’s not some odd interop thing that makes LSM and MVPN >>>>>>> interoperability in the same VRF a problem there. >>>>>>> >>>>>>> Can anyone see something I may have missed? >>>>>>> >>>>>>> Topo: >>>>>>> >>>>>>> ME3600 1 (MVPN) —— ME3600 2 (PIM) —— ME3600 3 (PIM) —— >> A9K >>> 1 >>>>>>> (MVPN) >>>>>>> >>>>>>> me3600-1#show ip pim neigh >>>>>>> PIM Neighbor Table >>>>>>> Mode: B - Bidir Capable, DR - Designated Router, N - Default DR >> Priority, >>>>>>> P - Proxy Capable, S - State Refresh Capable, G - GenID Capable >>>>>>> Neighbor Interface Uptime/Expires Ver DR >>>>>>> Address >>>>>>> Prio/Mode >>>>>>> 72.15.51.236 TenGigabitEthernet0/1 01:09:45/00:01:27 v2 1 / >>>>>>> S P >> G >>>>>>> me3600-1#sh ip pim vrf tv neighbor PIM Neighbor Table >>>>>>> Mode: B - Bidir Capable, DR - Designated Router, N - Default DR >> Priority, >>>>>>> P - Proxy Capable, S - State Refresh Capable, G - GenID Capable >>>>>>> Neighbor Interface Uptime/Expires Ver DR >>>>>>> Address >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> Prio/Mode >>>>>>> me3600-2sh ip pim neigh PIM Neighbor Table >>>>>>> Mode: B - Bidir Capable, DR - Designated Router, N - Default DR >> Priority, >>>>>>> P - Proxy Capable, S - State Refresh Capable, G - GenID Capable >>>>>>> Neighbor Interface Uptime/Expires Ver DR >>>>>>> Address >>>>>>> Prio/Mode >>>>>>> 72.15.51.6 TenGigabitEthernet0/1 00:55:06/00:01:41 v2 1 / >>>>>>> S P G >>>>>>> 72.15.51.237 TenGigabitEthernet0/2 01:11:45/00:01:20 v2 1 / >>>>>>> DR >> S >>> P G >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> me3600-3#show ip pim neigh >>>>>>> PIM Neighbor Table >>>>>>> Mode: B - Bidir Capable, DR - Designated Router, N - Default DR >> Priority, >>>>>>> P - Proxy Capable, S - State Refresh Capable, G - GenID Capable >>>>>>> Neighbor Interface Uptime/Expires Ver DR >>>>>>> Address >>>>>>> Prio/Mode >>>>>>> 72.15.51.2 TenGigabitEthernet0/1 00:55:26/00:01:39 v2 100/ >>>>>>> DR >> P >>> G >>>>>>> 72.15.51.7 TenGigabitEthernet0/2 00:55:26/00:01:23 v2 1 / >>>>>>> DR S >> P >>> G >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> a9k-1#show pim neighbor te0/2/0/2 >>>>>>> Fri Nov 28 16:23:16.113 EST >>>>>>> >>>>>>> PIM neighbors in VRF default >>>>>>> Flag: B - Bidir capable, P - Proxy capable, DR - Designated Router, >>>>>>> E - ECMP Redirect capable >>>>>>> * indicates the neighbor created for this router >>>>>>> >>>>>>> Neighbor Address Interface Uptime Expires >>>>>>> DR pri >> Flags >>>>>>> >>>>>>> 72.15.51.2* TenGigE0/2/0/2 2d01h 00:01:29 >>>>>>> 100 (DR) B P >> E >>>>>>> 72.15.51.3 TenGigE0/2/0/2 00:56:08 00:01:42 >>>>>>> 1 P >>>>>>> a9k-1#show pim vrf tv neighbor | i mdt Fri Nov 28 16:24:54.797 EST >>>>>>> 72.15.48.4* Lmdttv 46w1d 00:01:40 >>>>>>> 1 (DR) P E >>>>>>> 72.15.48.4* mdttv 2d02h 00:01:25 >>>>>>> 1 P E >>>>>>> 72.15.50.152 mdttv 00:57:36 00:01:40 >>>>>>> 1 (DR) P >>>>>>> a9k-1#show pim vrf tv interface >>>>>>> Fri Nov 28 16:27:37.663 EST >>>>>>> >>>>>>> PIM interfaces in VRF tv >>>>>>> Address Interface PIM Nbr Hello >>>>>>> DR DR >>>>>>> Count Intvl >>>>>>> Prior >>>>>>> >>>>>>> 72.15.48.4 mdttv on 2 30 1 >>>>>>> 72.15.50.152 >>>>>>> 72.15.48.4 Lmdttv on 1 30 1 >>>>>>> this system >>>>>>> 172.16.0.32 Loopback2022 on 1 30 1 >>>>>>> this system >>>>>>> _______________________________________________ >>>>>>> cisco-nsp mailing list [email protected] >>>>>>> https://puck.nether.net/mailman/listinfo/cisco-nsp >>>>>>> archive at http://puck.nether.net/pipermail/cisco-nsp/ >>>> _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
