OcNOS®

Open Compute
Network Operating System
for Service Providers
Version 4.0

Multicast Quick
Configuration Guide
January 2021

IP Infusion Inc. Proprietary

© 2021 IP Infusion Inc. All Rights Reserved.

This documentation is subject to change without notice. The software described in this document and this documentation
are furnished under a license agreement or nondisclosure agreement. The software and documentation may be used or
copied only in accordance with the terms of the applicable agreement. No part of this publication may be reproduced, stored
in a retrieval system, or transmitted in any form or any means electronic or mechanical, including photocopying and
recording for any purpose other than the purchaser's internal use without the written permission of IP Infusion Inc.

IP Infusion Inc.
3965 Freedom Circle, Suite 200
Santa Clara, CA 95054
+1 408-400-1900
http://www.ipinfusion.com/

For support, questions, or comments via E-mail, contact:

[email protected]

Trademarks:
IP Infusion, OcNOS, VirNOS, ZebM, and ZebOS-XP are trademarks or registered trademarks of IP Infusion. All other
trademarks, service marks, registered trademarks, or registered service marks are the property of their respective owners.

Use of certain software included in this equipment is subject to the IP Infusion, Inc. End User License Agreement at http://
www.ipinfusion.com/license. By using the equipment, you accept the terms of the End User License Agreement.

ii IP Infusion Inc. Proprietary

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv

CHAPTER 1 Understanding IGMP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
Router1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

CHAPTER 2 Understanding PIM Sparse Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
Static Rendezvous Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
Router1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
Router2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
Router3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
Dynamic Rendezvous Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
Router1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
Router2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
Router3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14

CHAPTER 3 Understanding PIM Dense Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
Router1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
Router2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
Router3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

© 2021 IP Infusion Inc. Proprietary iii

Contents

iv © 2021 IP Infusion Inc. Proprietary

Preface

This guide describes how to configure multicast protocols in OcNOS.

Audience
This guide is intended for network administrators and other engineering professionals who configure multicast
protocols.

Conventions
Table P-1 shows the conventions used in this guide.

Table P-1: Conventions

Convention Description

Italics Emphasized terms; titles of books

Note: Special instructions, suggestions, or warnings

monospaced type Code elements such as commands, functions, parameters, files, and directories

Contents
This document contains these chapters:
• Chapter 1, Understanding IGMP
• Chapter 2, Understanding PIM Sparse Mode
• Chapter 3, Understanding PIM Dense Mode

Related Documents
See the following documents for details about the commands used in example configurations.
• Protocol Independent Multicasting Command Reference
• Multicast Configuration Guide

Support
For support-related questions, contact [email protected].

© 2021 IP Infusion Inc. Proprietary iii

Preface

Comments
If you have comments, or need to report a problem with the content, contact [email protected].

iv © 2021 IP Infusion Inc. Proprietary

CHAPTER 1 Understanding IGMP

Overview
The Internet Group Management Protocol (IGMP) is used by IP hosts to report their multicast group memberships to
any immediately-neighboring multicast routers. Using the information obtained through IGMP, the router maintains a list
of multicast groups on a per-interface basis. The routers that receive these IGMP packets send multicast data that they
receive for requested groups out the network segment of the known receivers. By default, when PIM is enabled on an
interface, IGMP version 3 is enabled. IGMP can be enabled on an interface explicitly.

Topology
Figure 1-1shows a sample IGMP topology.

Figure 1-1: Routers using IGMP

Configuration

Router1

Router1#configure terminal Enter configure mode.

Router1(config)#ip multicast-routing Enable IP multicast routing.
Router1(config)#interface eth1 Specify the interface (eth1)to be configured.
Router1(config-if)#ip address 9.9.9.1/24 Configure IP address for the interface.
Router1(config-if)#ip igmp version 2 Enable IGMP version 2 on the interface.

© 2021 IP Infusion Inc. Proprietary 5

Understanding IGMP

Router1(config-if)#exit Exit interface mode.

Router1(config)#exit Exit configure mode.

Validation
Use the following show commands to validate the configuration above.
Router1#show ip igmp interface
Interface eth1 (Index 3)
IGMP Enabled, Active, Querier, Configured for version 2
Internet address is 9.9.9.1
IGMP interface has 1 group-record states
IGMP Interface statistics:
v1-reports: 0
v2-reports: 1, v2-leaves: 0
v3-reports: 0
IGMP query interval is 125 seconds
IGMP Startup query interval is 31 seconds
IGMP Startup query count is 2
IGMP querier timeout is 255 seconds
IGMP max query response time is 10 seconds
Group Membership interval is 260 seconds
IGMP Last member query count is 2
Last member query response interval is 1000 milliseconds

When Router1 receives a IGMP report from Receiver on an interface , it populates the IGMP groups table.
Router1#show ip igmp groups
IGMP Connected Group Membership
Group Address Interface Uptime Expires State Last Reporter
224.1.1.1 eth1 00:00:02 00:04:17 Active 9.9.9.2

Router1#show ip igmp groups detail

IGMP Connected Group Membership Details
Flags: (M - SSM Mapping, R - Remote, L - Local,
SG - Static Group, SS - Static Source)
Interface: eth1
Group: 224.1.1.1
Flags: R
Uptime: 00:00:04
Group mode: Exclude (Expires: 00:04:16)
State: Active
Last reporter: 9.9.9.2
Source list is empty

6 © 2021 IP Infusion Inc. Proprietary

CHAPTER 2 Understanding PIM Sparse Mode

Overview
The Protocol Independent Multicasting-Sparse Mode (PIM-SM) is a multicast routing protocol designed to operate
efficiently across Wide Area Networks (WANs) with sparsely distributed groups. It helps geographically dispersed
network nodes to conserve bandwidth and reduce traffic by simultaneously delivering a single stream of information to
multiple locations. PIM-SM uses the IP multicast model of receiver-initiated membership, supporting both shared and
shortest-path trees, and uses soft-state mechanisms to adapt to changing network conditions. It relies on a topology-
gathering protocol to populate a multicast routing Routertable with routes.

Data Flow from Source to Receivers in PIM-SM Network Domain

1. Sending out hello messages PIM routers periodically send hello messages to discover neighboring PIM routers.
Hello messages are multicast using the address, 224.0.0.13 (ALL-PIM-ROUTERS group). Routers do not send
any acknowledgement that a hello message was received. A holdtime value determines the length of time for
which the information is valid. In PIM-SM, a downstream receiver must join a group before traffic is forwarded on
the interface.

2. Electing a Designated Router in a multi-access network with multiple routers connected, one of the routers is
selected to act as a designated router (DR) for a given period. The DR is responsible for sending Join/Prune
messages to the RP for local members.

3. Determining the Rendezvous Point PIM-SM uses a BSR to originate bootstrap messages, and to disseminate RP
information. The messages are multicast to the group on each link. If the BSR is not apparent, the routers flood the
domain with advertisements. The router with the highest priority (if priorities are same, the higher IP address
applies) is selected to be the RP. Routers receive and store bootstrap messages originated by the BSR. When a
DR gets a membership indication from IGMP for (or a data packet from) a directly connected host, for a group for
which it has no entry, the designated router (DR) maps the group address to one of the candidate RPs that can
service that group. The DR then sends a Join/Prune message towards that RP. In a small domain, the RP can also
be configured statically.

4. Joining the Shared Tree To join a multicast group, a host sends an IGMP message to its upstream router, after
which the router can accept multicast traffic for that group. The router sends a Join message to its upstream PIM
neighbor in the direction of the RP. When a router receives a Join message from a downstream router, it checks to
see if a state exists for the group in its multicast routing table. If a state already exists, the Join message has
reached the shared tree, and the interface from which the message was received is entered in the Outgoing
Interface list. If no state exists, an entry is created, the interface is entered in the outgoing Interface list, and the
Join message is again sent towards the RP.

5. Registering with the RP a DR can begin receiving traffic from a source without having a Source or a Group state for
that source. In this case, the DR has no information on how to get multicast traffic to the RP through a tree. When
the source DR receives the initial multicast packet, it encapsulates it in a Register message, and unicasts it to the
RP for that group. The RP de-encapsulates each Register message, and forwards the extracted data packet to
downstream members on the RPT. Once the path is established from the source to the RP, the DR begins sending
traffic to the RP as standard IP multicast packets, as well as encapsulated within Register messages. The RP
temporarily receives packets twice. When the RP detects the normal multicast packets, it sends a Register-Stop
message to the source DR, meaning it should stop sending register packets.

© 2021 IP Infusion Inc. Proprietary 7

Understanding PIM Sparse Mode

6. Sending Register-Stop messages when the RP begins receiving traffic from the source, both as Register
messages and as unencapsulated IP packets, it sends a Register-Stop message to the DR. This notifies the DR
that the traffic is now being received as standard IP multicast packets on the SPT. When the DR receives this
message, it stops encapsulating traffic in Register messages.

7. Pruning the Interface Routers attached to receivers send Prune messages to the RP to disassociate the source
from the RP. When an RP receives a Prune message, it no longer forwards traffic from the source indicated in the
Prune message. If all members of a multicast group are pruned, the IGMP state of the DR is deleted, and the
interface is removed from the Source and Group lists of the group.

8. Forwarding Multicast Packets PIM-SM routers forward multicast traffic onto all interfaces that lead to receivers that
have explicitly joined a multicast group. Messages are sent to a group address in the local subnetwork, and have a
Time to Live (TTL) of 1. The router performs an RPF check, and forwards the packet. If a downstream router has
sent a join to this router or is a member of this group, then traffic that arrives on the correct interface is sent to all
outgoing interfaces that lead to downstream receivers.

Topology
Figure 2-2 shows a sample PIM-SM topology.

Figure 2-2: PIM Sparse Mode Topology

8 © 2021 IP Infusion Inc. Proprietary

 Understanding PIM Sparse Mode

Static Rendezvous Point

In this example, Router2 is the RP. Static RP configuration requires that all routers in the PIM domain have the same IP
PIM RP address commands configured.

Router1

Router1#configure terminal Enter configure mode.

Router1(config)#ip multicast-routing Enable IP multicast routing
Router1(config)#interface eth1 Specify the interface (eth1)to be configured
Router1(config-if)#ip address 10.10.10.1/24 Configure IP address for the interface
Router1(config-if)#ip pim sparse-mode Enable PIM sparse mode on the interface
Router1(config-if)#exit Exit interface mode
Router1(config)#ip pim rp-address 12.12.12.2 Configure static RP address (Router2 interface eth2 as the
RP)
Router1(config)#interface eth2 Specify the interface (eth2)to be configured
Router1(config-if)#ip address 11.11.11.1/24 Configure IP address for the interface
Router1(config-if)#ip pim sparse-mode Enable PIM sparse mode on the interface
Router1(config-if)#exit Exit interface mode
Router1(config)#interface eth3 Specify the interface (eth3)to be configured
Router1(config-if)#ip address 9.9.9.1/24 Configure IP address for the interface
Router1(config-if)#ip pim sparse-mode Enable PIM sparse mode on the interface
Router1(config-if)#exit Exit interface mode
Router1(config)#ip pim spt-threshold Configure IP PIM threshold.
Router1(config)#router ospf 100 Configure the routing process and specify the Process ID
(100)
Router1(config-router)#network 10.10.10.0/24 Define the interface on which OSPF runs and associate the
area 0 area ID (0) with the interface
Router1(config-router)#network 11.11.11.0/24 Define the interface on which OSPF runs and associate the
area 0 area ID (0) with the interface
Router1(config-router)#network 9.9.9.0/24 Define the interface on which OSPF runs and associate the
area 0 area ID (0) with the interface

Router2

Router2#configure terminal Enter configure mode.

Router2(config)#ip multicast-routing Enable IP multicast routing
Router2(config)#interface eth1 Specify the interface (eth1)to be configured
Router2(config-if)#ip address 10.10.10.2/24 Configure IP address for the interface
Router2(config-if)#ip pim sparse-mode Enable PIM sparse mode on the interface
Router2(config-if)#exit Exit interface mode

© 2021 IP Infusion Inc. Proprietary 9

Understanding PIM Sparse Mode

Router2(config)#ip pim rp-address 12.12.12.2 Configure static RP address (Router2 interface eth2 as
the RP)
Router2(config)#interface eth2 Specify the interface (eth2)to be configured
Router2(config-if)#ip address 12.12.12.2/24 Configure IP address for the interface
Router2(config-if)#ip pim sparse-mode Enable PIM sparse mode on the interface
Router2(config-if)#exit Exit interface mode
Router2(config)#router ospf 100 Configure the routing process and specify the Process ID
(100)
Router2(config-router)#network 10.10.10.0/24 Define the interface on which OSPF runs and associate
area 0 the area ID (0) with the interface
Router2(config-router)#network 12.12.12.0/24 Define the interface on which OSPF runs and associate
area 0 the area ID (0) with the interface

Router3

Router3#configure terminal Enter configure mode.

Router3(config)#ip multicast-routing Enable IP multicast routing

Router3(config)#interface eth1 Specify the interface (eth1)to be configured

Router3(config-if)#ip address 12.12.12.3/24 Configure IP address for the interface

Router3(config-if)#ip pim sparse-mode Enable PIM sparse mode on the interface

Router3(config-if)#exit Exit interface mode

Router3(config)#ip pim rp-address 12.12.12.2 Configure static RP address (Router2 interface eth2 as
the RP)
Router3(config)#interface eth2 Specify the interface (eth2)to be configured

Router3(config-if)#ip address 11.11.11.3/24 Configure IP address for the interface

Router3(config-if)#ip pim sparse-mode Enable PIM sparse mode on the interface

Router3(config-if)#exit Exit interface mode

Router3(config)#router ospf 100 Configure the routing process and specify the Process
ID (100)
Router3(config-router)#network 11.11.11.0/24 Define the interface on which OSPF runs and associate
area 0 the area ID (0) with the interface

Router3(config-router)#network 12.12.12.0/24 Define the interface on which OSPF runs and associate
area 0 the area ID (0) with the interface

Validation
Use the following show commands to validate the configuration above.
Router1#show ip pim neighbor
Neighbor Interface Uptime/Expires Ver DR
Address Priority/Mode
10.10.10.2 eth1 00:14:33/00:01:34 v2 1 / DR
11.11.11.3 eth2 00:09:27/00:01:18 v2 1 / DR

10 © 2021 IP Infusion Inc. Proprietary

 Understanding PIM Sparse Mode

Router1#show ip pim interface

Address Interface VIFindex Ver/ Nbr DR DR
Mode Count Prior
10.10.10.1 eth1 0 v2/S 1 1 10.10.10.2
11.11.11.1 eth2 2 v2/S 1 1 11.11.11.3

Router1#show ip pim rp mapping

PIM Group-to-RP Mappings
Override RP cnt: 0
Group(s): 224.0.0.0/4, Static
RP: 12.12.12.2
Uptime: 00:23:41

Router1s#how ip pim rp-hash 224.1.1.1

RP: 12.12.12.2

Note: For the validation of the below commands, An IGMP report to be sent from receiver towards Router1 for the
desired group and source should send multicast traffic for the desired group in order to populate PIM mroute
and mroute entries.For IGMP report generation refer IGMP-Section.
When Source starts sending multicast traffic for group 224.1.1.1, PIM mroute entry gets populated.
Router1#show ip pim mroute
IP Multicast Routing Table
(*,*,RP) Entries: 0
(*,G) Entries: 1
(S,G) Entries: 1
(S,G,rpt) Entries: 1
FCR Entries: 0
(*, 224.1.1.1)
RP: 12.12.12.2
RPF nbr: 10.10.10.2
RPF idx: eth1
Upstream State: JOINED
Local ...i............................
Joined ................................
Asserted ................................
FCR:
(14.14.14.2, 224.1.1.1)
RPF nbr: 11.11.11.3
RPF idx: eth2
SPT bit: 1
Upstream State: JOINED
Local ................................
Joined ................................
Asserted ................................
Outgoing ...o............................
(14.14.14.2, 224.1.1.1, rpt)

© 2021 IP Infusion Inc. Proprietary 11

Understanding PIM Sparse Mode

RP: 12.12.12.2
RPF nbr: 10.10.10.2
RPF idx: eth1
Upstream State: PRUNED
Local ................................
Pruned ................................
Outgoing ...o...........................

When Source starts sending multicast traffic for group 224.1.1.1, mroute entry gets populated with Olist gets formed.
Router1#show ip mroute
IP Multicast Routing Table
Flags: I - Immediate Stat, T - Timed Stat, F - Forwarder installed
B - BIDIR
Timers: Uptime/Stat Expiry
Interface State: Interface (TTL)
(14.14.14.2, 224.1.1.1), uptime 00:00:43, stat expires 00:02:47
Owner PIM, Flags: TF
Incoming interface: eth2
Outgoing interface list:
eth3 (1)

Dynamic Rendezvous Point

In this example, Router2 is the RP elected dynamically by BSR protocol. Router2 is configured as both candidate-RP
and candidate-BSR. All routers in the PIM domain learn the RP dynamically.

Router1

Router1#configure terminal Enter configure mode.

Router1(config)#ip multicast-routing Enable IP multicast routing

Router1(config)#interface eth1 Specify the interface (eth1)to be configured

Router1(config-if)#ip address 10.10.10.1/24 Configure IP address for the interface.

Router1(config-if)#ip pim sparse-mode Enable PIM sparse mode on the interface.

Router1(config-if)#exit Exit interface mode.

Router1(config)#interface eth2 Specify the interface (eth2)to be configured.

Router1(config-if)#ip address 11.11.11.1/24 Configure IP address for the interface.

Router1(config-if)#ip pim sparse-mode Enable PIM sparse mode on the interface.

Router1(config-if)#exit Exit interface mode.

Router1(config)#interface eth3 Specify the interface (eth3)to be configured.

Router1(config-if)#ip address 9.9.9.1/24 Configure IP address for the interface.

Router1(config-if)#ip pim sparse-mode Enable PIM sparse mode on the interface.

12 © 2021 IP Infusion Inc. Proprietary

 Understanding PIM Sparse Mode

Router1(config-if)#exit Exit interface mode.

Router1(config)#ip pim spt-threshold Confogure IP PIM threshold.

Router1(config)#router ospf 100 Configure the routing process and specify the
Process ID (100).
Router1(config-router)#network 10.10.10.0/24 Define the interface on which OSPF runs and
area 0 associate the area ID (0) with the interface.

Router1(config-router)#network 11.11.11.0/24 Define the interface on which OSPF runs and

area 0 associate the area ID (0) with the interface.

Router1(config-router)#network 9.9.9.0/24 area Define the interface on which OSPF runs and
0 associate the area ID (0)with the interface.

Router2

Router2#configure terminal Enter configure mode.

Router2(config)#ip multicast-routing Enable IP multicast routing.
Router2(config)#interface eth1 Specify the interface (eth1)to be configured.
Router2(config-if)#ip address 10.10.10.2/24 Configure IP address for the interface.
Router2(config-if)#ip pim sparse-mode Enable PIM sparse mode on the interface.
Router2(config-if)#exit Exit interface mode.
Router2(config)#ip pim bsr-candidate eth2 Configure bsr candidate (Router2 interface eth2 as BSR
candidate)
Router2(config)#ip pim rp-candidate eth2 Configure rp candidate (Router2 interface eth2 as RP
candidate)
Router2(config)#interface eth2 Specify the interface (eth2)to be configured.
Router2(config-if)#ip address 12.12.12.2/24 Configure IP address for the interface.
Router2(config-if)#ip pim sparse-mode Enable PIM sparse mode on the interface.
Router2(config-if)#exit Exit interface mode.
Router2(config)#router ospf 100 Configure the routing process and specify the Process ID
(100).
Router2(config-router)#network 10.10.10.0/24 Define the interface on which OSPF runs and associate
area 0 the area ID (0) with the interface.
Router2(config-router)#network 12.12.12.0/24 Define the interface on which OSPF runs and associate
area 0 the area ID (0) with the interface.

Router3

Router3#configure terminal Enter configure mode.

Router3(config)#ip multicast-routing Enable IP multicast routing.
Router3(config)#interface eth1 Specify the interface (eth1)to be configured.
Router3(config-if)#ip address 12.12.12.3/24 Configure IP address for the interface.
Router3(config-if)#ip pim sparse-mode Enable PIM sparse mode on the interface.
Router3(config-if)#exit Exit interface mode.

© 2021 IP Infusion Inc. Proprietary 13

Understanding PIM Sparse Mode

Router3(config)#interface eth2 Specify the interface (eth2)to be configured.

Router3(config-if)#ip address 11.11.11.3/24 Configure IP address for the interface.
Router3(config-if)#ip pim sparse-mode Enable PIM sparse mode on the interface.
Router3(config-if)#exit Exit interface mode.
Router3(config)#router ospf 100 Configure the routing process and specify the Process
ID (1#00).
Router3(config-router)#network 11.11.11.0/24 Define the interface on which OSPF runs and
area 0 associate the area ID (0) with the interface.
Router3(config-router)#network 12.12.12.0/24 Define the interface on which OSPF runs and
area 0 associate the area ID (0) with the interface.

Validation
Use the following show commands to validate the configuration above.
Router1#show ip pim neighbor
Neighbor Interface Uptime/Expires Ver DR
Address Priority/Mode
10.10.10.2 eth1 00:14:33/00:01:34 v2 1 / DR
11.11.11.3 eth2 00:09:27/00:01:18 v2 1 / DR

Router1#show ip pim interface

Address Interface VIFindex Ver/ Nbr DR DR
Mode Count Prior
10.10.10.1 eth1 0 v2/S 1 1 10.10.10.2
11.11.11.1 eth2 2 v2/S 1 1 11.11.11.3

Router1#show ip pim rp mapping

PIM Group-to-RP Mappings
Group(s): 224.0.0.0/4
RP: 12.12.12.2
Info source: 12.12.12.2, via bootstrap, priority 192
Uptime: 00:03:24, expires: 00:02:06
Override RP cnt: 0

Router1#show ip pim rp-hash 224.1.1.1

RP: 12.12.12.2
Info source: 12.12.12.2, via bootstrap

Note: For the validation of the below commands, An IGMP report to be sent from receiver towards Router1 for the
desired group and Source should send multicast traffic for the desired group in order to populate PIM mroute
and mroute entries.For IGMP report generation refer IGMP-Section.
When Source starts sending multicast traffic for group 224.1.1.1, PIM mroute entry gets populated.
Router1#show ip pim mroute
IP Multicast Routing Table
(*,*,RP) Entries: 0
(*,G) Entries: 1
(S,G) Entries: 1
(S,G,rpt) Entries: 1

14 © 2021 IP Infusion Inc. Proprietary

 Understanding PIM Sparse Mode

FCR Entries: 0
(*, 224.1.1.1)
RP: 12.12.12.2
RPF nbr: 10.10.10.2
RPF idx: eth1
Upstream State: JOINED
Local ...i............................
Joined ................................
Asserted ................................
FCR:
(14.14.14.2, 224.1.1.1)
RPF nbr: 11.11.11.3
RPF idx: eth2
SPT bit: 1
Upstream State: JOINED
Local ................................
Joined ................................
Asserted ................................
Outgoing ...o............................
(14.14.14.2, 224.1.1.1, rpt)
RP: 12.12.12.2
RPF nbr: 10.10.10.2
RPF idx: eth1
Upstream State: PRUNED
Local ................................
Pruned ................................
Outgoing ...o............................

When Source starts sending multicast traffic for group 224.1.1.1, mroute entry gets populated with Olist gets formed.
Router1#show ip mroute
IP Multicast Routing Table
Flags: I - Immediate Stat, T - Timed Stat, F - Forwarder installed
B - BIDIR
Timers: Uptime/Stat Expiry
Interface State: Interface (TTL)
(14.14.14.2, 224.1.1.1), uptime 00:00:43, stat expires 00:02:47
Owner PIM, Flags: TF
Incoming interface: eth2
Outgoing interface list:
eth3 (1)

© 2021 IP Infusion Inc. Proprietary 15

Understanding PIM Sparse Mode

16 © 2021 IP Infusion Inc. Proprietary

CHAPTER 3 Understanding PIM Dense Mode

Overview
Dense Mode (PIM-DM) is a data-driven multicast routing protocol that builds source-based multicast distribution trees
that operate on the flood-and-prune principle. PIM-DM requires unicast reach-ability information, but it does not depend
on a specific unicast routing protocol.

Topology
Figure 3-3 shows a topology of three routers in PIM Dense Mode.

Figure 3-3: PIM Dense Mode Topology

© 2021 IP Infusion Inc. Proprietary 17

Understanding PIM Dense Mode

Configuration

Router1

Router1#configure terminal Enter configure mode.

Router1(config)#ip multicast-routing Enable IP multicast routing
Router1(config)#interface eth1 Specify the interface (eth1)to be configured
Router1(config-if)#ip address 10.10.10.1/24 Configure IP address for the interface
Router1(config-if)#ip pim dense-mode Enable PIM dense mode on the interface
Router1(config-if)#exit Exit interface mode
Router1(config)#interface eth2 Specify the interface (eth2)to be configured
Router1(config-if)#ip address 9.9.9.1/24 Configure IP address for the interface
Router1(config-if)#ip pim dense-mode Enable PIM dense mode on the interface
Router1(config-if)#exit Exit interface mode
Router1(config)#router ospf 100 Configure the routing process and specify the Process
ID (100)
Router1(config-router)#network 10.10.10.0/24 Define the interface on which OSPF runs and associate
area 0 the area ID (0) with the interface
Router1(config-router)#network 9.9.9.0/24 area Define the interface on which OSPF runs and associate
0 the area ID (0) with the interface

Router2

Router2#configure terminal Enter configure mode.

Router2(config)#ip multicast-routing Enable IP multicast routing
Router2(config)#interface eth1 Specify the interface (eth1)to be configured
Router2(config-if)#ip address 10.10.10.2/24 Configure IP address for the interface
Router2(config-if)#ip pim dense-mode Enable PIM dense mode on the interface
Router2(config-if)#exit Exit interface mode
Router2(config)#interface eth2 Specify the interface (eth2)to be configured
Router2(config-if)#ip address 12.12.12.2/24 Configure IP address for the interface
Router2(config-if)#ip pim dense-mode Enable PIM dense mode on the interface
Router2(config-if)#exit Exit interface mode
Router2(config)#router ospf 100 Configure the routing process and specify the Process
ID (100)
Router2(config-router)#network 10.10.10.0/24 Define the interface on which OSPF runs and associate
area 0 the area ID (0) with the interface
Router2(config-router)#network 12.12.12.0/24 Define the interface on which OSPF runs and associate
area 0 the area ID (0) with the interface

18 © 2021 IP Infusion Inc. Proprietary

 Understanding PIM Dense Mode

Router3

Router3#configure terminal Enter configure mode.

Router3(config)#ip multicast-routing Enable IP multicast routing
Router3(config)#interface eth1 Specify the interface (eth1)to be configured
Router3(config-if)#ip address 13.13.13.3/24 Configure IP address for the interface
Router3(config-if)#ip pim dense-mode Enable PIM dense mode on the interface
Router3(config-if)#exit Exit interface mode
Router3(config)#interface eth2 Specify the interface (eth2) to be configured.
Router3(config-if)#ip address 12.12.12.3/24 Configure IP address for the interface.
Router3(config-if)#ip pim dense-mode Enable PIM dense mode on the interface.
Router3(config-if)#exit Exit interface mode
Router3(config)#router ospf 100 Configure the routing process and specify the Process ID
(100)
Router3(config-router)#network 12.12.12.0/ Define the interface on which OSPF runs and associate the
24 area 0 area ID (0) with the interface
Router3(config-router)#network 13.13.13.0/ Define the interface on which OSPF runs and associate the
24 area 0 area ID (0) with the interface

Validation
Use the following show commands to validate the configuration above.
Router1#show ip pim neighbor
Neighbor Interface Uptime/Expires Ver DR
Address Priority/Mode
10.10.10.2 eth1 00:03:00/00:01:22 v2 N /

Router1#show ip pim interface

Address Interface VIFindex Ver/ Nbr DR DR
Mode Count Prior
10.10.10.1 eth1 0 v2/D 1 1
9.9.9.1 eth2 1 v2/D 0 1

Note: For the validation of the below commands, An IGMP report to be sent from receiver towards Router1 for the
desired group and source should send multicast traffic for the desired group in order to populate PIM mroute
and mroute entries.For IGMP report generation refer IGMP-Section.
When Source starts sending multicast traffic for group 224.1.1.1, PIM mroute entry gets populated with Olist gets
formed.
Router1#show ip pim mroute
PIM-DM Multicast Routing Table
(13.13.13.2, 224.1.1.1)
RPF Neighbor: 10.10.10.2, Nexthop: 10.10.10.2
Upstream IF: eth1
Upstream State: Forwarding

© 2021 IP Infusion Inc. Proprietary 19

Understanding PIM Dense Mode

Upstream Prune Limit Timer Expiry: 0 secs

Assert State: NoInfo
Source Active Timer Expiry: 5 secs
State Refresh Timer Expiry: 0 secs
Downstream IF List:
eth2:, in 'olist'
Downstream State: NoInfo
Assert State: NoInfo

When Source starts sending multicast traffic for group 224.1.1.1, mroute entry gets populated with Olist gets formed.
Router1#show ip mroute
IP Multicast Routing Table
Flags: I - Immediate Stat, T - Timed Stat, F - Forwarder installed
B - BIDIR
Timers: Uptime/Stat Expiry
Interface State: Interface (TTL)
(13.13.13.2, 224.1.1.1), uptime 00:00:19
Owner PIM, Flags: F
Incoming interface: eth1
Outgoing interface list:
eth2 (1)

20 © 2021 IP Infusion Inc. Proprietary

Index

A S
Audience iii show ip igmp groups 6
show ip igmp groups detail 6
B show ip igmp interface 6
show ip mroute 12, 15
BSR 7 show ip pim interface 11, 19
show ip pim mroute 11, 14, 19
show ip pim neighbor 10, 14, 19
C show ip pim rp mapping 11, 14
Comments iv show ip pim rp-hash 11
Contents iii source-based multicast 17
Conventions iii Sparse Mode 7
Static Rendezvous Point 8
Support iii
D
Designated Router 7 V
DR 7
Dynamic Rendezvous Point 12 Validation 6, 10, 19
version 3 5
F
flood-and-prune 17

H
Hello Messages 7

I
IGMP 5
IGMP message 7
IGMP multicasting 5
Internet Group Management Protocol 5
ip pim rp-hash 14

P
PIM 7
PIM routers 7
PIM-DM 17
PIM-SM 7
Preface iii
Protocol Independent Multicasting 7

R
Related Documents iii
Rendezvous Point 7
RP 7

© 2021 IP Infusion Inc. Proprietary 21

Index

22 © 2021 IP Infusion Inc. Proprietary