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 639 Lessons. More Lessons Added Every Week!
  • Content created by Rene Molenaar (CCIE #41726)

 

351 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!

Tags:


Forum Replies

  1. Thanks a lot Rene for your very easy to understand explanations. I just stumbled on your website and I use it as reference for my ccie study. Thanks for sharing.

  2. Hi Rene,

    I am not able to ping the mcast address 239.1.1.1 from R1 after all configs are done.
    Below are the o/p for msdp

    R2#sh ip msdp peer 
    MSDP Peer 3.3.3.3 (?), AS ?
      Connection status:
        State: Up, Resets: 0, Connection source: Loopback1 (2.2.2.2)
        Uptime(Downtime): 00:02:30, Messages sent/received: 4/3
        Output messages discarded: 0
        Connection and counters cleared 00:08:30 ago
      SA Filtering:
        Input (S,G) filter: none, route-map: none
        Input RP filter: none, route-map: none
        Output (S,G) filter: none, route-map: none
        Output RP fil
    ... Continue reading in our forum

  3. Hi rene,

    good article, i just noticed some mismatch :

    1. your show msdp peer is
    R2#show ip msdp peer 
    MSDP Peer 3.3.3.3 (?), AS ?
      Connection status:
        State: Up, Resets: 0, Connection source: Loopback1 (2.2.2.2)
    

    and your config is

    R2(config)#ip msdp originator-id Loopback 0
    R2(config)#ip msdp peer 3.3.3.3 connect-source Loopback 0
    

    it should be

    R2(config)#ip msdp originator-id Loopback 0
    R2(config)#ip msdp peer 3.3.3.3 connect-source Loopback 1
    

    I think you forgot to mention that ip pim sparse-mode should be enabled in the interface loopback0

    1. your pict
    ... Continue reading in our forum

  4. Hi all,

    Just edited this post. The MSDP peering should be between the loopback 1 interfaces of R2/R3, not loopback 0.

    Rene

  5. Anycast RP means all our IPs are advertising the same IP address. The problem with this, is that some sources might join RP1 or RP2, and your receives also join RP1 or RP2. No single RP has information about all sources/receivers.

    To fix this, we use the MSDP protocol to “sync” the information between RPs.

33 more replies! Ask a question or join the discussion by visiting our Community Forum