We're Sorry, Full Content Access is for Members Only...

If you like to keep on reading, Become a Member Now! Here is Why:

  • Learn any CCNA, CCNP and CCIE R&S Topic. Explained As Simple As Possible.
  • Try for Just $1. The Best Dollar You've Ever Spent on Your Cisco Career!
  • Full Access to our 637 Lessons. More Lessons Added Every Week!
  • Content created by Rene Molenaar (CCIE #41726)

 

367 New Members signed up the last 30 days!

satisfaction-guaranteed

100% Satisfaction Guaranteed!
You may cancel your monthly membership at any time.
No Questions Asked!


Forum Replies

  1. Great content so far!
    Please update the topology pic, there the IP adress in 192.168.123.0-network for R2 and R3 must be changed.
    Is pim snooping ever used as it doesn’t seem to be well covered from Cisco’s documentation, too.

    • Why is R2 the DR as R3 has higher IP?
    • Why should one filter traffic to the DR as it break the ability to send join/register messages to the RP and to register sources or receivers? Or does this join/regeister forwarding by an DR only apply when the RP is in another broadcast domain?
      Best regards
      Alex

  2. Hello Alexander

    Looking at the topology pic, I’m not sure where the error is. The 192.168.123.0/24 network is shared between the three routers on interface Ge0/1 with IP addresses of .1, .2 and .3. Please elaborate on what should be corrected.

    As for your other questions:

    Actually, R1 is the DR as is indicated in the PIM debug messages on both R1 and R2. Although you are correct that the higher IP should be chosen as

    ... Continue reading in our forum

  3. Hi. Thanks for your answers, didn’t see the hard-coded RP in the first moment.
    Explanaition for PIM Snooping and DR traffic is sufficient.

    Regarding the topology pic, the IP adresses for R2 and for R3 are wrong/ should be changed.
    R2 has configured 192.168.123. 2 and topology pic shows 192.168.123. 3
    R3 has configured 192.168.123. 3 and topology pic shows 192.168.123. 2

    Best regards
    Alex

Ask a question or join the discussion by visiting our Community Forum