09/05/2023, 22:43 Muttcast PIM Designated Router Search Q © Multicast PIM Designated Router When we configure PIM on our routers, we will establish PIM neighbor adjacencies, and the PIM hello messages are also used to elect a designated router for each multi-access network. The DR is the router that will forward the PIM join message from the receiver to the RP (rendezvous point) Since the DR is used to forward PIM join messages to the RP, it doesn’t do much good for multicast dense mode where we don't have an RP. The only exception is when you use IGMPv1...in that case, the PIM DR will work as the IGMP query router because IGMPv1 doesn't have a query router election. Don't mix up the PIM DR with the PIM forwarder! To decide which router will forward multicast traffic, we have the PIM Assert mechanism. Let's take a look at the following topology to see how the DR works: sno091052023, 22:43, Muttcast PIM Designated Router ve 8 ” % & S ad o, S w \, S %0, x 5 3 3 2 192.168.234.0 /24.S~ e & S$ A Receiver ‘Above, we See a small network with 4 routers. R1 is our RP, and R4 is the receiver. As you can see R? R2 and R4 are connected to the same multi-access network (switch). When R4 sends a PIM join me (42) Ctrl+M R2 and R3 would receive it and forward it to R1. This would mean that we have 2 multicast streams which results in duplicate packets and wasted bandwidth. hps:inetworklessons.comimulicasUmullicast-pim-designatec-outer09/05/2023, 22:43 Muttcast PIM Designated Router a Let's configure this small network and take a close look at how the DR works: Ri(config)#ip multicast-routing R1(config)#ip pim rp-address 1.1.1.1 R1(config)#interface loopback @ Ri(config-if)#ip pim sparse-mode R1(config)#interface fastEthernet 0/2 R1(config-if)#ip pim sparse-mode R1(config)#interface fastEthernet 0/1 R1(config-if)#ip pim sparse-mode We will use the loopback interface on R1 to advertise as the RP. R2(config)#ip multicast-routing R2(config)#ip pim rp-address 1.1.1.1 R2(config)#interface fastEthernet 0/8 R2(config-if)#ip pim sparse-mode R2(config)#interface fastEthernet 0/1 R2(config-if)#ip pim sparse-mode R3(config)#ip multicast-routing R3(config)#ip pim rp-address 1.1.1.1 R3(config)#interface fastEthernet 0/0 R3(config-if)#ip pim sparse-mode R3(config)#interface fastEthernet 0/1 R3(config-if)#ip pim sparse-mode ano09/05/2023, 22:43 Muttcast PIM Designated Router a R2 and R3 are configured for sparse mode and a static RP, Ré is only a receiver, so we don't need PIM. R2#show ip pim neighbor PIM Neighbor Table Mode: B = Bidir Capable, DR - Designated Router, N - Default DR Priority, S - State Refresh Capable Neighbor Interface Uptine/Expires Ver OR Address Prio/Mode 192.168.12.1 Fastetherneto/o 01:24:25/00:01:28 v2 «1./ 192.168.234.3 _Fastetherneto/1 01:24:29/00:01:26 v2 «1. / ORS RB has been elected as the Designated router on this segment. Why? because by default, the highest IP address will determine who becomes the PIM DR. Now let's enable a debug to see what the designated router really does for us: R2itdebug ip pim PIM debugging is on Ravdebug ip pim PIM debugging is on We will use debug ip pim on R2 and R3. Now we will join a multicast group on R4: R4(config)#interface fastEthernet @/@ R4(config-if)#ip igmp join-group 239.1.1.1 4 will join multicast group 239.1.1.1. Now let's see what R2 and R3 think of this: Rai © Check RP 1.1.1.1 into the (*, 239.1.1.1) entry Above, you see that R2 doesn't do much with it, it does add 1.1.1.1 as the RP for multicast group 239.1.1.1. You can see it here: ano09/05/2023, 22:43 Muttcast PIM Designated Router a Ar muLiicase RUULENy rauLe Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected, - Local, P - Pruned, R - RP-bit set, F - Register flag, - SPT-bit set, J - Join SPT, M - MSDP created entry, - Proxy Join Timer Running, A - Candidate for MSDP Advertisement, L 1 x U - URD, I - Received Source Specific Host Report, Z - Multicast Tunnel, z - MDT-data group sender, Y - Joined mpT-data group, y - Sending to MDT-data group eB 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), @0:11:38/00:02:19, RP 1.1.1.1, flags: SP Incoming interface: FastEthernet@/@, RPF nbr 192.168.12.1 outgoing interface list: Null ‘Above, you see that it created an entry for the 239.1.1.1 group address with 1.1.1.1 as the RP. Now let's take a look at R3:; R3e Check RP 1.1.1.1 into the (+, 239.1.1.1) entry Building Triggered (*,G) Join / (S,6,RP-bit) Prune message for 239.1.1.1 Insert (*,239.1.1.1) join in nbr 192.168.13.1's queue Building Join/Prune packet for nbr 192.168.13.1 Adding v2 (1.1.1.1/32, 239.1.1.1), WC-bit, RPT-bit, S-bit Join Send v2 join/prune to 192.168.13.1 (Fastetherneto/0) This is a more interesting output. First, it adds 1.1.1.1 as the RP for 239.1.1.1, but you can also see that it builds a PIM join message and forwards it to our RP. This is because R3 is our designated router. By default, the highest IP address determines who will become the DR, This is because the default priority 1. Let's change the priority so that R2 becomes the DR: R2(config)#interface fa0/1 R2(config-if)#ip pim dr-priority 100 hitpstnetworklessons.com/mulicasUmulicast-pim-designalec-router sno09/05/2023, 22:43 Muttcast PIM Designated Router a Rai PIM(®): Changing DR for FastEthernet®/1, from 192.168.234.3 to 192.168.234.2 (this system) XPIM-5-DRCHG: DR change from neighbor 192.168.234.3 to 192.168.234.2 on interface FastEthernet@/1 RBH PIM(@): Changing DR for FastEthernet@/1, from 192.168.234.3 to 192.168.234.2 XPIM-5-DRCHG: DR change from neighbor 192.168.234.3 to 192.168.234.2 on interface FastEthernet@/1. ‘As you can see, it’s preemptive, it will take effect immediately. The designated router does something else besides forwarding the PIM join messages. The DR is also responsible for sending PIM register messages to the RP once a source starts sending packets to the multicast group address. Let's send some packets to the multicast group address to see how it works: Rayping 239.1.1.1 repeat 9999 Type escape sequence to abort. Sending 9999, 100-byte ICMP Echos to 239.1.1.1, timeout is 2 second: Reply to request @ from 192.168.234.4, 8 ms Il send some packets to the multicast group address on R4. This will trigger a PIM register message for the source to the RP. Take a look at R2: Rai Send v2 Register to 1.1.1.1 for 192.168.234.4, group 239.1.1.1 © AAs the DR, it's responsible for registering the source at the rendezvous point Last but not least, we have a failover mechanism. Unlike OSPF, there is no BDR (Backup Designated Router) in PIM, When the DR fails, other routers will see this because their PIM neighbor adjacency will go down. A hitpstnetworklessons.com/mulicasUmulicast-pim-designalec-router eno09/05/2023, 22:43 a Muttcast PIM Designated Router This new DR already has the IGMP state for the required multicast groups because it also heard the IGMP membership reports from receivers on the segment. The only thing the new DR has to do is send a PIM join to the RP, and our traffic flow will continue. Want to take a look for yourself? Here you wil find the final configuration of each device, R1 hostname R1 ! ip multicast-routing ip cef interface Loopback@ ip address 1.1.1.1 255.255.255.255 ip pim sparse-mode interface Gigabitethernete/1 ip address 192.168.12.1 255.255.255.0 ip pim sparse-mode interface Gigabitetherneto/2 ip address 192.168.13.1 255.255.2550 ip pim sparse-mode router ospf 1 network 1.1.1.1 0.0.0.0 area @ network 192.168.12.0 .0.0.255 area @ network 192.168.13.0 0.0.0.255 area @ ! ip pim rp-address 1.1.1.1 ! end hitpstnetworklessons.com/mulicasUmulicast-pim-designalec-router m009/05/2023, 22:43 Muttcast PIM Designated Router hostname R2 ! ip multicast-routing ip cef interface Gigabitethernet@/1 ip address 192.168.12.2 255.255.255. ip pim sparse-mode interface Gigabitetherneto/2 ip address 192.168.234.2 255.255.255.0 ip pim dr-priority 100 ip pim sparse-mode ! router ospf 1 network 192.168.12.0 6.0.0.255 area @ network 192.168.234.0 @.0.0.255 area @ ! ip pim rp-address 1.1.1.1 ! end R3 ~ hostname R3 ip multicast-routing ip cef ! interface Gigabitetherneto/1 ip address 192.168,13.3 255.255.255.0 4p pin sparse-node : io) interface Gigabitetherneto/2 ip address 192.168.234.3 255.255.255.0 ip pim sparse-mode hitpstnetworklessans.com/mulicasUmulicast-pim-designalec-router ano09/05/2023, 22:43 Muttcast PIM Designated Router a network 192.168.13.0 .0.0.255 area @ network 192.168.234.0 .0.0.255 area @ ! ip pim rp-address 1.1.1.1 ! end R4 ~ hostname R4 ' ip multicast-routing ip cef ! interface Gigabitethernet@/1 ip address 192.168.234.4 255.255.255.0 ip igmp join-group 239.1.1.1 router ospf 1 network 192.168.234.0 @.0.0.255 area @ ! end hope this has been helpful to you. If you have any more multicast questions, just leave a comment! « Previous Lesson Next Lesson Multicast Tunnel RPF Failure PIM Assert. ® Tags: PIM Forum Replies 8 & ven hitpstnetworklessons.com/mulicasUmulicast-pim-designalec-router snoosiosi2023, 22:43 Muttcast PIM Designated Router a the Rendezvous Point is mapped to the group. Fundamentals of ip pm sparse mode which i am working with. Thank you, QR orematenar You are welcome Kevin, glad to hear you lke it. ope Thank You... & one Very nice explanation - appreciated. gsm Too good. itis very crisp and clear. Answered to the point. Too good. Keep posting similar posts for other multicast technologies as well. Thanks, {2 44 more replies! Ask a question or join the discussion by visiting our Community Forum Disclaimer Privacy Policy Support About © 2013 - 2023 NetworkLessons.com 52189 © ctri+m hps:inetworklessons.comimulicasUmullicast-pim-designatec-outer r010