MDT peering works like a champ, except wireshark cannot even decode the new AFIs yet :)
R5#sho ip rpf vrf VPNA 10.1.1.1 RPF information for ? (10.1.1.1) RPF interface: Tunnel0 RPF neighbor: ? (100.0.0.2) <---- R2 in other AS RPF route/mask: 10.1.1.1/32 RPF type: unicast (bgp 200) RPF recursion count: 0 Doing distance-preferred lookups across tables BGP originator: 100.0.0.2 R1#ping 224.6.6.6 so lo 0 Type escape sequence to abort. Sending 1, 100-byte ICMP Echos to 224.6.6.6, timeout is 2 seconds: Packet sent with a source address of 10.1.1.1 Reply to request 0 from 200.5.6.6, 280 ms Reply to request 0 from 200.5.6.6, 284 ms On Wed, Sep 9, 2009 at 12:11 PM, Bryan Bartik <[email protected]> wrote: > Looks like I need MDT AFI support which is in 12.4T...going to upgrade... > > > On Wed, Sep 9, 2009 at 11:47 AM, Bryan Bartik <[email protected]>wrote: > >> I have an inter-AS multicast VPN set up and everything appears good except >> on the egress PE (R5) where RPF check is failing. >> >> R1(CE-sender)----R2---R3------inter-as >> link------R4---R5s1/0---R6(CE-receiver) >> >> Inter-AS VPN is working, R1 and R6 can ping each other's loopbacks. >> Sparse-Mode inside the clouds, MSDP between R3 and R4 (The RPs for each >> AS) >> I have an MDT for 224.25.25.25 which is working (I can tell because the >> mroute count for the MDT is increasing with each ping). >> R1 is sending to 224.6.6.6 from its loopback 10.1.1.1 >> Packets get forwarded from R2 all the way to R5, where the R5 RPF check >> fails for 10.1.1.1. >> Not sure why the RPF check fails because the route exists. >> >> Here are the route, mroute and rpf entries: >> >> R5#sho ip mroute vrf VPNA 224.6.6.6 | be \( >> (*, 224.6.6.6), 00:06:05/stopped, RP 0.0.0.0, flags: D >> Incoming interface: Null, RPF nbr 0.0.0.0 >> Outgoing interface list: >> Serial1/0, Forward/Dense, 00:06:05/00:00:00 >> Tunnel0, Forward/Sparse-Dense, 00:06:05/00:00:00 >> >> (10.1.1.1, 224.6.6.6), 00:00:01/00:02:58, flags: >> Incoming interface: Null, RPF nbr 200.0.0.4 <---- RPF neighbor >> Outgoing interface list: >> Serial1/0, Forward/Dense, 00:00:01/00:00:00 <---- Interface toward R6 >> Tunnel0, Forward/Sparse-Dense, 00:00:01/00:00:00 >> >> R5#sho ip route vrf VPNA 10.1.1.1 >> Routing entry for 10.1.1.1/32 >> Known via "bgp 200", distance 200, metric 0 >> Tag 100, type internal >> Redistributing via ospf 1 >> Advertised by ospf 1 subnets >> Last update from 200.0.0.4 00:26:44 ago >> Routing Descriptor Blocks: >> * 200.0.0.4 (Default-IP-Routing-Table), from 200.0.0.4, 00:26:44 ago >> <---- Next hop >> Route metric is 0, traffic share count is 1 >> AS Hops 1 >> Route tag 100 >> >> R5#sho ip rpf vrf VPNA 10.1.1.1 >> RPF information for ? (10.1.1.1) failed, no route exists <---- How? >> R5# >> >> Here you can see the MDT packets being forwarded out of R5 (decapsulation) >> but the RPF check incrementing to the group 224.6.6.6: >> >> R5#sho ip mroute 224.25.25.25 count >> Group: 224.25.25.25, Source count: 1, Packets forwarded: 15, Packets >> received: 15 >> RP-tree: Forwarding: 0/0/0/0, Other: 0/0/0 >> Source: 100.0.0.2/32, Forwarding: 15/1/120/0, Other: 15/0/0 <--- >> Forwarding >> >> R5#sho ip mroute vrf VPNA 224.6.6.6 count >> Group: 224.6.6.6, Source count: 1, Packets forwarded: 0, Packets received: >> 15 >> Source: 10.1.1.1/32, Forwarding: 0/0/0/0, Other: 15/15/0 <---- RPF >> failures >> R5# >> >> I tried setting an mroute in the VRF, but it doesn't seem to work. Any >> ideas? >> If I do an mroute inthe VRF, who should my next hop be (R4 global or R1 in >> the VRF)? >> Btw, the network has no multi-paths or redundant links. >> >> Thanks, >> >> -- >> Bryan Bartik >> CCIE #23707 (R&S), CCNP >> Sr. Support Engineer - IPexpert, Inc. >> URL: http://www.IPexpert.com >> > > > > -- > Bryan Bartik > CCIE #23707 (R&S), CCNP > Sr. Support Engineer - IPexpert, Inc. > URL: http://www.IPexpert.com > -- Bryan Bartik CCIE #23707 (R&S), CCNP Sr. Support Engineer - IPexpert, Inc. URL: http://www.IPexpert.com
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
