Tags:


Notable 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 filter: none, route-map: none
      SA-Requests: 
        Input filter: none
      Peer ttl threshold: 0
      SAs learned from this peer: 0
      Input queue size: 0, Output queue size: 0
    

    -

    R3#sh ip msdp peer 
    MSDP Peer 2.2.2.2 (?), AS ?
      Connection status:
        State: Up, Resets: 0, Connection source: Loopback1 (3.3.3.3)
        Uptime(Downtime): 00:02:35, Messages sent/received: 3/4
        Output messages discarded: 0
        Connection and counters cleared 00:08:35 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 filter: none, route-map: none
      SA-Requests: 
        Input filter: none
      Peer ttl threshold: 0
      SAs learned from this peer: 1
      Input queue size: 0, Output queue size: 0
  3. Did you use IGMP join group on R4? As soon as you do this, R3 should show the outgoing interface for the group that you joined.

  4. 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 picture is showing
      R2 loopback 0 = 2.2.2.2 instead 23.23.23.23
      R3 loopback 0 = 3.3.3.3 instead 23.23.23.23
      so normally 2.2.2.2 and 3.3.3.3 should be configured in loopack 1 as loopback 0 has already its IP address.

    I think we can guess it easely as your show command is correct meaning the original configuration is correct.

    thank you again for this article that is very instructive

  5. Hi Réné,
    Sometile I saw ip igmp join-group or ip igmp join simply. Same effect or different?

    Thank.
    Ulrich

Continue the discussion forum.networklessons.com

37 more replies!

Participants