Tags:


Notable Replies

  1. While labbing the same topology, i found something diff from ur configuration. Here it is:

    1. “ip pim bidir-enable” should be enable on R4 & R5 as well.
    2. “ip pim rp-address 1.1.1.1 bidir” should be configured on R4 & R5 as well.

    Then only i am getting the same output as u mention in your most. Let me know i have done mistakes anywhere ya i understood it wrongly.

  2. Hi Rene,

    I really enjoy the way you teach and the content is very well organized.
    I have a question regarding PIM Bidirectional.
    For have in all Pim enabled Router the *,G to the RP on downstream Router, we need to enable globally the pim bidirectional.
    What if i have on third party router that doesnt’ support pim bidirectional? is it will be enable to from *,G to the RP?

  3. Hi Rene,

    I do not understand based on the last output shown below
    (Now we see FastEthenet0/0 as the Bidir-Upstream interface and FastEthernet0/1 in the outgoing list. This is something different than what you have seen before right?)

    Isn’t your earlier output already showing FastEthenet0/0 as the Bidir-Upstream interface and FastEthernet0/1 in the outgoing list?

    R3#show ip mroute 239.1.1.1    
    (*, 239.1.1.1), 00:09:39/00:03:10, RP 1.1.1.1, flags: BC
      **Bidir-Upstream: FastEthernet0/0**, RPF nbr 192.168.13.1
      **Outgoing interface list:**
         **FastEthernet0/0, Bidir-Upstream/Sparse**, 00:09:39/00:00:00
        **FastEthernet0/1, Forward/Sparse**, 00:09:39/00:02:42
    

    Thanks,
    Kent

  4. Earlier output below:

    R3#show ip mroute 239.1.1.1
    IP Multicast Routing Table
    Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
           L - Local, P - Pruned, R - RP-bit set, F - Register flag,
           T - SPT-bit set, J - Join SPT, M - MSDP created entry,
           X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
           U - URD, I - Received Source Specific Host Report,
           Z - Multicast Tunnel, z - MDT-data group sender,
           Y - Joined MDT-data group, y - Sending to MDT-data group
    Outgoing interface flags: H - Hardware switched, A - Assert winner
     Timers: Uptime/Expires
     Interface state: Interface, Next-Hop or VCD, State/Mode
    
    (*, 239.1.1.1), 00:04:07/00:03:19, RP 1.1.1.1, flags: BC
      **Bidir-Upstream: FastEthernet0/0**, RPF nbr 192.168.13.1
      **Outgoing interface list**:
        **FastEthernet0/0, Bidir-Upstream/Sparse**, 00:04:07/00:00:00
        **FastEthernet0/1, Forward/Sparse**, 00:04:07/00:03:19
    

    Above you see that the FastEthernet0/0 interface is the upstream (towards the RP) and FastEthernet0/1 is the outgoing interface (towards R5). Now we will configure R4 to join the 239.1.1.1 multicast group as well so that they can communicate with each other:

  5. Hello Kenneth

    You are correct in that the output was the same as that shown earlier in the lab. Of course, this is indeed different from the output shown in R2 which is shown just previously. I will ask Rene to clarify his statement.

    Thanks for the heads up!

    Laz

Continue the discussion forum.networklessons.com

8 more replies!

Participants