Thanks Ben, but that actually isn't the case. I was able to run a continuous ping without problem.
You're partly right though... I wasn't looking at the shared tree... For that the RPF was correct and R1 was expecting to receive traffic on FastEthernet0/0.12. It's as if it wasn't chaning over to the source tree... I did not modify the threshold. Jason On Sun, Jan 8, 2012 at 3:48 PM, Ben Hughes <[email protected]> wrote: > Hi Jason, > > I haven't looked up Lab10 but the first ping packet will get sent to the > RP and forwarded from there to the receiver. Then the following packets > should go direct assuming you haven't changed the threshold. If you try a > ping with more than one packet you will probably find that subsequent pings > fail. > > Cheers, > Ben. > > From: J D'Silva <[email protected]<mailto:[email protected]>> > Date: Sat, 7 Jan 2012 21:48:58 -0700 > To: OSL Routing and Switching <[email protected]<mailto: > [email protected]>> > Subject: [OSL | CCIE_RS] Vol3 Lab 10 Multicast > > HI All, > > I'm sure I'm just missing something basic, but I'm at a complete loss as to > what it is. > > Like the subject says, Vol3 Lab 10. Multicast section. I have it up and > working... But it shouldn't be working. My confusion is on R1. > > R1#sh ip pim int > > Address Interface Ver/ Nbr > Query DR DR > Mode > Count Intvl Prior > 163.144.12.1 FastEthernet0/0.12 v2/S 1 30 > 1 163.144.12.2 > 163.144.131.1 FastEthernet0/0.131 v2/S 1 30 > 1 163.144.131.13 > 163.144.121.1 FastEthernet0/0.121 v2/S 1 30 > 1 163.144.121.12 > > > (163.144.245.4, 239.14.14.14), 00:03:21/00:00:08, flags: > Incoming interface: Null, RPF nbr 163.144.15.5 > Outgoing interface list: > FastEthernet0/0.121, Forward/Sparse, 00:03:22/00:03:06 > FastEthernet0/0.131, Forward/Sparse, 00:03:22/00:03:19 > > R1#sh ip rpf 163.144.245.4 > RPF information for ? (163.144.245.4) failed, no route exists > > Jan 8 04:32:51.606: IP(0): s=163.144.245.4 (FastEthernet0/0.12) > d=239.14.14.14 (FastEthernet0/0.131) id=127, ttl=253, prot=1, len=100(100), > mforward > > > The mroute looks off to me... There's no flags and there's no incoming > interface... The RPF neighour is R5 (task disallows multicast enabled on > that link). You can also see the RPF if failing for the multicast source > required to complete the task. Yet, with debug IP mpacket you can see the > mpacket is received, and forwarded, even though it should be failing the > RPF check. > > Why the heck is R1 forwarding an mpacket that is failing RPF? > > I've managed to get all 7 points since I haven't added any mroutes.... But > I also haven't used MBGP, which is likely what the task was getting at for > the bonus points... > > R4#ping 239.14.14.14 > > Type escape sequence to abort. > Sending 1, 100-byte ICMP Echos to 239.14.14.14, timeout is 2 seconds: > > Reply to request 0 from 163.144.43.14, 76 ms > Reply to request 0 from 163.144.43.14, 100 ms > R4# > > > Jason > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com > > Are you a CCNP or CCIE and looking for a job? Check out > www.PlatinumPlacement.com > > http://onlinestudylist.com/mailman/listinfo/ccie_rs > > _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com Are you a CCNP or CCIE and looking for a job? Check out www.PlatinumPlacement.com http://onlinestudylist.com/mailman/listinfo/ccie_rs
