Multicast PIM Assert PDF

Download as pdf or txt
Download as pdf or txt
You are on page 1of 16

22.06.2016 Multicast PIM Assert Explained | NetworkLessons.

com

Search...

Table of Contents
CCIE Routing & Switching

Unit 1: Preparation
Unit 2: Switching
Unit 3: IP Routing
Unit 4: RIP
Unit 5: EIGRP
Unit 6: OSPF
Unit 7: BGP
Unit 8: Multicast
Introduction to Multicast

Multicast IP Addresses Overview

Multicast MAC to IP Address mapping

Multicast IGMP Version 1

Multicast IGMP Version 2

Multicast IGMP Version 3

Multicast IGMP Snooping

IGMP Snooping without Router

Multicast IGMP Filtering

Multicast CGMP (Cisco Group Management Protocol)

Multicast Routing

Multicast PIM Dense Mode

Multicast PIM Sparse Mode

Multicast PIM Auto RP

Multicast PIM BSR (Bootstrap)

https://networklessons.com/cisco/ccie­routing­switching/multicast­pim­assert­explained/ 1/16
22.06.2016 Multicast PIM Assert Explained | NetworkLessons.com

RPF (Reverse Path Forwarding)

PIM Designated Router

PIM Assert

Multicast PIM Prune Override

Multicast PIM Register Message

Anycast RP

Multicast Bidirectional PIM

Multicast Stub Routing and IGMP Helper

Source Speci ㈀c Multicast

Multicast PIM Accept RP

Multicast PIM Accept Register

Auto-RP Mapping agent behind Spoke

PIM NBMA Mode

Embedded RP for IPv6

IPv6 Multicast BSR and RP

Unit 9: IPv6
Unit 10: Quality of Service
Unit 11: Security
Unit 12: System Management
Unit 13: Network Services
Unit 14: MPLS

You are here: Home » Cisco » CCIE Routing & Switching

Multicast PIM Assert Explained


4 votes

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:

https://networklessons.com/cisco/ccie­routing­switching/multicast­pim­assert­explained/ 2/16
22.06.2016 Multicast PIM Assert Explained | NetworkLessons.com

Above you see 4 routers that are con ㈀gured to use multicast. R1 is the source and R4 is our
receiver. As you can see R2, R3 and R4 are connected to the same switch.

Now when R1 starts streaming multicast tra瀀攀c towards R2 and R3 they will both forward
multicast packets to R4 resulting in duplicate tra瀀攀c. To stop this PIM will elect one PIM
forwarder for this segment. PIM doesn’t have any routing information itself but relies on other
routing protocols that are con ㈀gured, it will use this information to select the best forwarding
path with the PIM assert mechanism.

Don’t confuse the PIM forwarder with the PIM DR (Designated Router). those are two
di漀椀erent things!
https://networklessons.com/cisco/ccie­routing­switching/multicast­pim­assert­explained/ 3/16
22.06.2016 Multicast PIM Assert Explained | NetworkLessons.com

When R2 and R3 both forward multicast packets to the 192.168.234.0 /24 segment they will see
each others multicast tra瀀攀c, 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 are using two routing protocols or if
you used a static route pointing to the source.
2. If the AD is equal we will compare the unicast routing metric towards 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 tra瀀攀c to the receiver while the loser will prune
its interface.

Now let’s take a look at this in action! First i’ll con ㈀gure a basic PIM Dense mode setup:

R1(config)#ip multicast‐routing

R1(config)#interface loopback 0
R1(config‐if)#ip address 1.1.1.1 255.255.255.255
R1(config‐if)#ip pim dense‐mode

R1(config)#interface fastEthernet 0/0


R1(config‐if)#ip pim dense‐mode

R1(config)#interface fastEthernet 0/1


R1(config‐if)#ip pim dense‐mode

I will use a loopback interface on R1 as the source for our multicast stream.

R2(config)#ip multicast‐routing

R2(config)#interface fastEthernet 0/0


R2(config‐if)#ip pim dense‐mode

R2(config)#interface fastEthernet 0/1


R2(config‐if)#ip pim dense‐mode

https://networklessons.com/cisco/ccie­routing­switching/multicast­pim­assert­explained/ 4/16
22.06.2016 Multicast PIM Assert Explained | NetworkLessons.com

R3(config)#ip multicast‐routing

R3(config)#interface fastEthernet 0/0


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:

R4(config)#ip multicast‐routing

R4(config)#interface fastEthernet 0/0


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 we make it listen to the 239.1.1.1 multicast
group address.

I applied OSPF to all routers, using the quick “shotgun approach” to advertise everything:

router ospf 1
network 0.0.0.0 255.255.255.255 area 0

Now let’s start a multicast stream from R1:

R1#ping 239.1.1.1 source loopback 0 repeat 9999

Type escape sequence to abort.


Sending 9999, 100‐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 0 from 192.168.234.4, 12 ms

You will see replies from R4. Now let’s check who is forwarding this tra瀀攀c:

https://networklessons.com/cisco/ccie­routing­switching/multicast­pim­assert­explained/ 5/16
22.06.2016 Multicast PIM Assert Explained | NetworkLessons.com

R2#show ip mroute 1.1.1.1 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

(1.1.1.1, 239.1.1.1), 00:02:56/00:00:07, flags: PT


Incoming interface: FastEthernet0/0, RPF nbr 192.168.12.1
Outgoing interface list:
FastEthernet0/1, Prune/Dense, 00:02:56/00:00:03

R3#show ip mroute 1.1.1.1 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

(1.1.1.1, 239.1.1.1), 00:02:48/00:02:57, flags: T


Incoming interface: FastEthernet0/0, RPF nbr 192.168.13.1
Outgoing interface list:
FastEthernet0/1, Forward/Dense, 00:02:48/00:00:00, A

https://networklessons.com/cisco/ccie­routing­switching/multicast­pim­assert­explained/ 6/16
22.06.2016 Multicast PIM Assert Explained | NetworkLessons.com

As you can see above R2 has pruned its outgoing interface while R3 is forwarding it. Note that
you also see the “A” indicating that R3 is the assert winner. R3 has won this PIM assert election
because it has the 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 pre ㈀xes 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 source IP
addresses, not destination IP addresses like with unicast routing.

Let’s verify our work:

R2#show ip route | include 1.1.1.1


O 1.1.1.1 [100/11] via 192.168.12.1, 00:01:32, FastEthernet0/0

R3#show ip route | include 1.1.1.1


O 1.1.1.1 [110/11] via 192.168.13.1, 00:01:20, FastEthernet0/0

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.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,

https://networklessons.com/cisco/ccie­routing­switching/multicast­pim­assert­explained/ 7/16
22.06.2016 Multicast PIM Assert Explained | NetworkLessons.com

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

(1.1.1.1, 239.1.1.1), 00:00:11/00:02:53, flags: T


Incoming interface: FastEthernet0/0, RPF nbr 192.168.12.1
Outgoing interface list:
FastEthernet0/1, Forward/Dense, 00: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 it's metric to the source is worse than R2:

R2#show ip ospf interface fa0/0 | include Cost


Process ID 1, Router ID 192.168.234.2, Network Type BROADCAST, Cost: 10

R3#show ip ospf interface fa0/0 | include Cost


Process ID 1, Router ID 192.168.234.3, Network Type BROADCAST, Cost: 10

The default cost of the FastEthernet 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


O 1.1.1.1 [110/11] via 192.168.12.1, 00:06:58, FastEthernet0/0

https://networklessons.com/cisco/ccie­routing­switching/multicast­pim­assert­explained/ 8/16
22.06.2016 Multicast PIM Assert Explained | NetworkLessons.com

R3#show ip route ospf | include 1.1.1.1


O 1.1.1.1 [110/12] via 192.168.13.1, 00:00:44, FastEthernet0/0

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 FastEthernet0/1


FastEthernet0/1, Forward/Dense, 00: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:

R2#debug ip pim
PIM debugging is on

You will see something like this:

Send v2 Assert on FastEthernet0/1 for 239.1.1.1, source 1.1.1.1, metric


[110/11]
PIM(0): Assert metric to source 1.1.1.1 is [110/11]
PIM(0): We win, our metric [110/11]
PIM(0): (1.1.1.1/32, 239.1.1.1) oif FastEthernet0/1 in Forward state
PIM(0): Received v2 Assert on FastEthernet0/1 from 192.168.234.3
PIM(0): Assert metric to source 1.1.1.1 is [110/12] 
PIM(0): We win, our metric [110/11]
PIM(0): (1.1.1.1/32, 239.1.1.1) oif FastEthernet0/1 in Forward state

I hope this explanation and walkthrough help you understand PIM assert. If you have any
questions feel free to leave a comment!

Rate this Lesson:

https://networklessons.com/cisco/ccie­routing­switching/multicast­pim­assert­explained/ 9/16
22.06.2016 Multicast PIM Assert Explained | NetworkLessons.com

« Previous Lesson
PIM Designated Router
Next Lesson
Multicast PIM Prune Override »
Home › Forums › Multicast PIM Assert Explained

This topic contains 18 replies, has 5 voices, and was last updated by Rene Molenaar 1 month,
2 weeks ago.

Viewing 15 posts - 1 through 15 (of 18 total)


12→
Author
Posts | Subscribe
October 28, 2013 at 07:14 #13874 Reply

kkvi1357
i did to change AD , it work

when i try to change metric, and make debugging which tell me is the winner, it is still give
outbound prune

why? 
my scenario is the same as your scenario

October 28, 2013 at 07:17 #13875 Reply

kkvi1357
this is 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(0): Assert metric to source 3.3.3.3 is [110/75]

https://networklessons.com/cisco/ccie­routing­switching/multicast­pim­assert­explained/ 10/16
22.06.2016 Multicast PIM Assert Explained | NetworkLessons.com

*Mar 1 00:53:23.599: PIM(0): We win, our metric [110/6]


*Mar 1 00:53:23.603: PIM(0): Prune Serial1/0/235.1.1.1 from (3.3.3.3/32, 235.1.1.1)
Mar 1 00:53:23.603: PIM(0): Pruning immediately Serial1/0 (p2p)

the serial 1/0 is the outbound interface which goes to receiver

November 11, 2013 at 10:12 #13876 Reply

Rene Molenaar
Keymaster
Do you also have the debug for the other router?

December 10, 2013 at 18:49 #13877 Reply

Tim Roth
Nice Article! Thanks Rene.

December 17, 2013 at 21:55 #13878 Reply

Rene Molenaar
Keymaster
Thanks Tim!

February 5, 2014 at 03:06 #13879 Reply

Doky
Thanks Rene for the article.
So the PIM Assert is only between R2 and R3, there is nothing to do with R4?

March 10, 2014 at 14:15 #13880 Reply

Rene Molenaar
Keymaster

https://networklessons.com/cisco/ccie­routing­switching/multicast­pim­assert­explained/ 11/16
22.06.2016 Multicast PIM Assert Explained | NetworkLessons.com

Hi Doky,

That’s right, basically R4 is just a computer that wants to listen to a certain multicast stream.

Rene

March 27, 2014 at 09:24 #13881 Reply

Paul
Hi Rene,thanks for the explanation

This behavior is the same for sparse mode as well?

April 14, 2014 at 12:00 #13882 Reply

Rene Molenaar
Keymaster
Hi Paul,

Yes this behavior is the same. PIM Assert is used to determine which router will forward
multicast tra瀀攀c…PIM sparse, dense or sparse-dense mode are used for multicast routing.

Rene

September 13, 2014 at 13:22 #13883 Reply 

sergey
Hi Rene, thanks for the article.

I don’t understand one thing , why do we need an assert mechanism if we have RPF?

RPF will prune the unnecessary paths anyway.

Thanks,

September 16, 2014 at 14:41 #13884 Reply

https://networklessons.com/cisco/ccie­routing­switching/multicast­pim­assert­explained/ 12/16
22.06.2016 Multicast PIM Assert Explained | NetworkLessons.com

Rene Molenaar
Keymaster
Hi Sergey,

RPF doesn’t prune, it’s only used to make sure packets won’t loop around.

When a multicast packet is received, the router will check the source IP and checks the outgoing
interface in its routing table. When the incoming interface of the received IP packet is the same
as the outgoing interface in the routing table, it will pass the RPF check. When the incoming
interface and outgoing interface are di漀椀erent, it will be dropped.

In this example, R4 has two upstream routers to reach R1…both will pass the RPF check so R4
won’t drop any multicast packets.

Rene

September 1, 2015 at 16:50 #13885 Reply

rouzbeh t
Participant
Hello Rene, Do we have forwarder in Dense mode? there is no forwarder in Sparse mode?

Thanks,
-Rouzbeh 
September 3, 2015 at 09:22 #13891 Reply

Rene Molenaar
Keymaster
Hi Rouzbeh,

We have a forwarder and we also use PIM Assert messages in sparse mode.

Rene

September 4, 2015 at 15:57 #13892 Reply

https://networklessons.com/cisco/ccie­routing­switching/multicast­pim­assert­explained/ 13/16
22.06.2016 Multicast PIM Assert Explained | NetworkLessons.com

rouzbeh t
Participant
Thank you Rene for the answer.

February 17, 2016 at 15:27 #22184 Reply

mungi b
Participant
Hi,

It’s a good article

if R2, R3 and R4 are not connected to the same switch, R2 is connected to R4 with each other’s
L3 port and R3 is connected to R4 with each other’s L3 port

in this case how does the R4 router work?

which one does the R4 router chose multicast tra瀀攀c for R2 or R3 ?

Author
Posts

Viewing 15 posts - 1 through 15 (of 18 total)


12→ 
Reply To: Multicast PIM Assert Explained
b i link b-quote del img ul ol li code close tags

https://networklessons.com/cisco/ccie­routing­switching/multicast­pim­assert­explained/ 14/16
22.06.2016 Multicast PIM Assert Explained | NetworkLessons.com

Please put code in between `backticks` or use the CODE button.


To place inline images, please use any image share service (such as TinyPic or Imgur) and use
the IMG button!

Notify me of follow-up replies via email

Maximum  ㈀le size allowed is 2048 KB.

Attachments:
Выберите файл Файл не выбран
Add another  ㈀le

Submit

About NetworkLessons.com

Hello There! I'm René Molenaar (CCIE #41726), Your Personal Instructor of
Networklessons.com. I'd like to teach you everything about Cisco, Wireless and
Security. I am here to Help You Master Networking!

Read my story

Social Fans

  
14,267 7,929 1,589
FANS FOLLOWERS SUBSCRIBERS

Highest Rated Lessons


MPLS Layer 3 VPN Con ㈀guration
(25 votes)

VRF Lite Con ㈀guration on Cisco IOS


(23 votes)

Cisco Portfast Con ㈀guration


(20 votes)
https://networklessons.com/cisco/ccie­routing­switching/multicast­pim­assert­explained/ 15/16
22.06.2016 Multicast PIM Assert Explained | NetworkLessons.com

IPv6 Address Types


(18 votes)

EIGRP Stub Explained


(17 votes)

New Lessons

Introduction to Cisco IOS XE


ERSPAN Con ㈀guration on Cisco IOS XE
IGMP Filter
IGMP Snooping without Router
Cisco Group Management Protocol (CGMP)

Disclaimer
Privacy Policy
Support

Multicast PIM Assert Explained written by Rene Molenaar average rating 5/5 - 4 user ratings

https://networklessons.com/cisco/ccie­routing­switching/multicast­pim­assert­explained/ 16/16

You might also like