091052023, 22:45 Muticast PIM Assert Explaines Search Q © Multicast PIM Assert Explained Multicast PIM Assert is one of those important multicast topics that most people don't really think about. Let’s take a look at the following topology: hitpstnetworklessons.com/mulicastmulicast-pim-asser-explained neosiosi2023, 22:45 Muticast PIM Assert Explained 2 38 %, 192.168.234.0/24_.9) oe. Receiver Above, you see four routers that are configured to use multicast. R1 is the source, and Ré is our receiver. AS you can see, R2, R3, and R4 are connected to the same switch. Now when R1 starts streaming multicast traffic towards R2 and R3, they will both forward multicast packet ~ to R4, resulting in duplicate traffic. To stop this, PIM will elect one PIM forwarder for this segment. PIM. Q doesn't have any routing information itself but relies on other routing protocols that are configured, it will use this information to select the best forwarding path with the PIM assert mechanism. hnps:inetworklessons.commulicasLmulicast-pim-assert-explained ana091052023, 22:45 Muticast PIM Assert Explaines a things! When R2 and R3 both forward multicast packets to the 192.168.234.0 /24 segment, they will see each other's multicast traffic, this will trigger the PIM assert mechanism. We will elect a PIM forwarder based on the following rules: 1. The router with the lowest administrative distance to the source of the multicast stream will be the elected PIM forwarder. This only happens if you use two routing protocols or when you use a static route pointing to the source. 2, Ifthe AD is equal, we will compare the unicast routing metric toward the source, 3. If the AD and metric are both the same, we will elect the PIM forwarded based on the highest IP address. The elected PIM forwarder will keep forwarding traffic to the receiver, while the loser will prune its interface Now let's take a look at this in action! First, Ill configure a basic PIM Dense mode setup: Ri(config)#ip multicast-routing R1(config)#interface loopback @ R1(config-if)#ip address 1.1.1.1 255.255.255.255 Ri(config-if)#ip pim dense-mode Ri (config)#interface fastethernet 0/2 R1(config-if)#ip pim dense-mode R1(config)#interface fastEthernet 0/1 R1(config-if)#ip pim dense-mode | will use a loopback interface on R1 as the source for our multicast stream. ra(contieip mttteast-rvting © R2(config)#interface fastEthernet 0/2 R2(config-if)#ip pim dense-mode hitpstnetworklessons.com/mulicastmulicast-pim-asser-explained ana091052023, 22:45 Muticast PIM Assert Explaines a R2(config-if)#ip pim dense-mode R3(config)#ip multicast-routing R3(config)#interface fastEthernet 0/2 R3(config-if)#ip pim dense-mode R3(config)#interface fastEthernet 0/1 R3(config-if)#ip pim dense-mode R2 and R3 are simple, Just enable multicast routing and PIM Dense mode on the interfaces. Only R4 left: Ra(config)#ip multicast-routing R4(config)#interface fastEthernet 0/2 R4(config-if)#ip pim dense-mode R4(config-if)#ip igmp join-group 239.1.1.1 On R4, we will also enable PIM dense mode and make it listen to the 239.1.1.1 multicast group address. | applied OSPF to all routers, using the quick “shotgun approach” to advertise everything: router ospf 1 network @.0.0.0 255.255.255.255 area 0 Now let's start a multicast stream from R1: Ri#ping 239.1.1.1 source loopback @ repeat 9999 Type escape sequence to abort. © Sending 9999, 10@-byte ICMP Echos to 239.1.1.1, timeout is 2 seconds: Packet sent with a source address of 1.1.1.1 Reply to request @ from 192.168.234.4, 12 ms hitpstnetworklessons.com/mulicastmulicast-pim-asser-explained ana091052023, 22:45 Muticast PIM Assert Explaines a R2itshow ip mroute 1.1.1.1 239.1.1.1 IP Multicast Routing Table Flags: D - Dense, S = Sparse, 8 - 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 (1.1.1.1, 239,1.1.2), @ 6/06 Incoming interface: FastEthernet@/@, RPF nbr 192.168.12.1 outgoing interface list: Fastethernet@/1, Prune/Dense, 00: 7, flags: PT 156/00:00:03 R3#show ip mroute 1.1.1.1 239.1.1.2 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, = SPT-bit set, J - Join SPT, M - MSDP created entry, - Proxy Join Timer Running, A - Candidate for MSDP Advertisement, = URD, I - Received Source Specific Host Report, - Joined MDT-data group, y - Sending to MDT-data group 1 x u Z - Multicast Tunnel, z - MDT-data group sender, Y eB Outgoing interface flags: H - Hardware switched, A - Assert winner Timers: Uptime/Expires Interface state: Interface, Next-Hop or VCD, State/Mode (4.1.1.1, 2391.11), 00:02:48/00:02:57, flags: T @ Incoming interface: FastEthernet@/@, RPF nbr 192.168.13.1 Outgoing interface list: FastEtherneto/1, Forward/Dense, @0:02:48/00:00:00, A hitpstnetworklessons.com/mulicastmulicast-pim-asser-explained siz091052023, 22:45 Muticast PIM Assert Explaines a highest IP address. Let's change the AD on R2 to see if it becomes the new assert winner: R2(config)#router ospf 1 R2(config-router)#distance 100 0.0.0.0 255.255.255.255 1 R2(config)#access-list 1 permit host 1.1.1.1 We will change the AD on R2 to 100 for all prefixes matching access-list 1. Access-list 1 matches 1.1.1.1, which is the source of our multicast stream, Keep in mind that when we work with multicast, we are concerned about the source IP addresses, not destination IP addresses like with unicast routing Let’s verify our work: R2Hshow ip route | include 1.1.2.1 ° 1.1.1.1 [100/11] via 192.168.12.1, 00:01:32, FastEtherneto/a R3#show ip route | include 1.1.1.1 ° 1.1.1.1 [110/11] via 192.168.13.1, 00:01:28, Fastetherneto/e R2 now has a better administrative distance, so it should win the PIM assert election; let's see if this is true: R2#show ip mroute 1.1.1.1 239.1.1.2 IP Multicast Routing Table Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected, Le T. x u z- Y a 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 Advertisenent, © URD, I - Received Source Specific Host Report, Multicast Tunnel, z - MDT-data group sender, Joined MDT-data group, y - Sending to MOT-data group utgoing interface flags: H - Hardware switched, A - Assert winner hitpstnetworklessons.com/mulicastmulicast-pim-asser-explained ena091052023, 22:45 Muticast PIM Assert Explaines a (1.1.1.1, 239.1.1.1), 0 1/06 3, flags: T Incoming interface: FastEthernet@/@, RPF nbr 192.168.12.1 Outgoing interface list: FastEthernet@/1, Forward/Dense, 0:00:11/00:00:00, A There we have it. The “A” tells us that R2 is now the PIM assert winner. Let's remove the lowered AD to play with the metric: R2(config)#router ospf 1 R2(config-router)#no distance 100 0.0.0.0 255.255.255.255 1 This will make R3 the forwarder again. We will now increase the cost on the FastEthernet0/0 link of R3 so that its metric to the source is worse than R2: R2#show ip ospf interface #a0/@ | include Cost Process ID 1, Router ID 192.168.234.2, Network Type BROADCAST, Cost: 1@ R3itshow ip ospf interface fa0/@ | include Cost Process ID 1, Router ID 192.168.234.3, Network Type BROADCAST, Cost: 10 The default cost of the Fastéthernet links is 10 on R2 and R3. Let's increase it on R3: R3(config)#interface fastEthernet 0/0 R3(config-if)#ip ospf cost 11 This is now the metric for R2 and R3 to reach the loopback0 interface of R1: R2#show ip route ospf | include 1.1.1.1 0.4.4.1 [120/21] via 192.268.12.1, 00:06:58, Fastethemeto/e © R3ishow ip route ospf | include 1.1.1.1 hitpstnetworklessons.com/mulicastmulicast-pim-asser-explained me091052023, 22:45 Muticast PIM Assert Explaines a R2 has a lower metric to reach the source of the multicast stream so it will be the PIM assert winner: R2#show ip mroute 1.1.1.1 239.1.1.1 | begin FastEtherneto/1 FastEtherneto/1, Forward/Dense, 60:01:41/00:00:00, A ‘And you can see this in the output above. If you want to see what it looks like behind the scenes, you can also enable a debug R2idebug ip pim PIM debugging is on You will see something like this: Send v2 Assert on FastEthernet@/1 for 239.1.1.1, source 1.1.1.1, metric [110/11] PIM(@): Assert metric to source 1.1.1.1 is [110/11] PIM(@): We win, our metric [110/11] PIM(®): (1.1.1.1/32, 239.1.1.1) oif FastEthernet@/1 in Forward state PIM(@): Received v2 Assert on FastEthernet@/1 from 192.168.234.3 PIM(@): Assert metric to source 1.1.1.1 is [110/12] PIM(@): We win, our metric [110/11] PIM(@): (1.1.1.1/32, 239.1.1.1) oif FastEthernet@/1 in Forward state Want to take a look for yourself? Here you wil find the final configuration of each device. R1 ~ hostname R1. ! a cef e ip multicast-routing ! hitpstnetworklessons.com/mulicastmulicast-pim-asser-explained ana091052023, 22:45 Muticast PIM Assert Explaines a ip pim dense-node interface Fastethernet@/@ ip address 192.168.12.1 255.255.255.0 ip pim dense-node interface FastEthernet@/1 ip address 192.168.13.1 255.255.255.0 ip pim dense-node router ospf 1 network 0.0.0.0 255.255.255.255 area @ ! end R2 hostname R2 ' ip cef ' ip multicast-routing ' interface Fastéthernet@/e ip address 192.168.12.2 255.255.255.0 ip pim dense-node ' interface Fastetherneto/1 ip address 192.168.234.2 255.255.255.0 ip pim dense-node ' router ospf 1 network 0.0.0.8 255.255.255.255 area @ access-list 1 permit 1.1.1.1 end hitpstnetworklessons.com/mulicastmulicast-pim-asser-explained one091052023, 22:45 hostname R3 ! ip cef ! ip multicast-routing ! interface Fastethernet@/e ip address 192.168.13.3 255.255.255.0 ip pim dense-node ip ospf cost 11 interface Fastethernet@/1 ip address 192.168.234.3 255.255.255.0 ip pim dense-node router ospf 1 network 0.0.0.8 255.255.255.255 area @ ! end R4 hostname Ra ip cef ip multicast-routing 1 interface FastEtherneto/a ip address 192.168.234.4 255.255.2550 ip pim dense-node ip ignp join-group 239.1.1.1 ! router ospf 2 network 0.0.0.0 255.255.255.255 area 0 hitpstnetworklessons.com/mulicastmulicast-pim-asser-explained Muticast PIM Assert Explaines soneosiosi2023, 22:45 Muticast PIM Assert Explained a hope this explanation and walkthrough help you understand PIM assert. If you have any questions feel free to leave a comment! K Previous Lesson Next Lesson) PIM Designated Router Multicast PIM Prune Override © Tags: PIM Forum Replies stem i did to change AD, it work when i try to change metri and make debugging which tell me is the winner, itis still give outbound prune why? my scenario is the same as your scenario & sem thisis the result of the debug FULL, Loading Done ‘*Mar 1 00:53:23,595: PIM(0): Received v2 Assert on Serial1/0 from 155.1.24.4 ‘*Mar 1 00:53:23,595: PIM(O): Assert metric to source 3.3.3.3 is (110/75) “*Mar 1 00:53:23,599: PIM(0): We win, our metric [110/6] ‘*Mar 1 00:53:23,603: PIM(Q): Prune Serial1/0/235.1.1.1 from (3.3.3.3/32, 235.1.1.1) Mar + 00:59:23 603 PIN(O}Prning mediately Seria 0 (526) © the serial 1/0 is the outbound interface which goes ta receiver hnps:inetworklessons.commulicasLmulicast-pim-assert-explained wineosiosi2023, 22:45 Muticast PIM Assert Explained a Do you also have the debug for the other router? & oxen Nice Article! Thanks Rene. QR Fovematenaar Thanks Tim! {% 47 more replies! Ask a question or join the discussion by visiting our Community Forum Disclaimer Privacy Policy Support About © 2013 - 2023 NetworkLessons.com 52189 rane hnps:inetworklessons.commulicasLmulicast-pim-assert-explained