AJER-12.a C8 IntroMulticast

Introduction to Multicast
© 2014 Juniper Networks, Inc. All rights reserved. | www.juniper.net | Worldwide Education
Services
Objectives
 After successfully completing this content,
you will be able to:
• Describe basic multicast terminology
• Describe the multicast address space
• Describe how RPF is used in a multicast network
• Describe the basic functionality of IGMP
© 2014 Juniper Networks, Inc. All rights reserved. Worldwide Education Services www.juniper.net | 2
Agenda: Introduction to Multicast
Overview of Multicast
 Multicast Addressing
 RPF
 IGMP
Unicast Versus Multicast Traffic Flow
Unicast—multiple data streams are needed to reach each client
Multiple Data
Streams
Network
Server Clients
ulticast—a single data stream from server is needed to reach all clients
Single Data
Stream Network
Server
Clients
Network devices replicate data stream

toward interested clients
Benefits and Usage of Multicast
 Benefits of multicast
• Load on source servers reduced
• Bandwidth usage within the network is reduced
 Usage of multicast
• Content delivery style of multicast is very similar to
broadcast radio and television
• Multiple subscribers can tune to a particular channel at
the same time to listen to, or watch, a particular
broadcast event (TV show)
• Only a single transmission from the provider (television
station) is necessary
• Companies around the world are moving toward
using multicast as the delivery mechanism for both
audio and video transmissions
Multicast Terms (1 of 2)
10.0.101.2 Network
DR DR
Source Receivers
10.0.101.2224.7.7.7 UDP M-cast
SA DA Data
 Terms
• Source: Originator of multicast IP packets
• Multicast IP Packet: An IP packet destined for a
multicast group address
• Group Address: An IP address in the range of 224/4
• Receivers: IP hosts interested in receiving data destined
for a particular group address (also called group
members)
• DR: Router closest to the source or receiver that
forwards multicast IP packets
Multicast Terms (2 of 2)
Group
Network Membershi
p Protocol
DR DR
Source Receivers
No special
protocol needed Multicast Routing
 Terms (contd.) Protocol
• Group Membership Protocol: Protocol used by receivers

to communicate group membership to the closest
attached router
• IGMP for IPv4 and MLD for IPv6
• Multicast Routing Protocol: Protocol used between routers
in the network to build and maintain the multicast
forwarding trees between sources and receivers
• PIM and DVMRP
Multicast State— (S,G)
 Routers along the forwarding
Source
path maintain (S,G) state 192.168.100.10
• Consists of..
• Known source IP address Multicast Traffic
• Group IP address
• Incoming interface
• Outgoing interface list
B D
C
Receiver R1
(S,G) State for R1
Source: 192.168.100.10
Group: 224.7.7.7
Incoming Interface: A
Outgoing Interface List: Receiver
B,C
Multicast State— (*,G)
 Some routers maintain (*,G) Source
state 192.168.100.10
• Consists of…
Multicast Traffic
• Unknown source IP address (Any)
• Group IP
• Incoming interface
• Outgoing interface list RP
B D
C
Receiver R1
(*,G) State for R1
Source: * (Any)
Group: 224.7.7.7
Incoming Interface: D (RP-facing
interface) Receiver
Outgoing Interface List: B,C
 Overview of Multicast
Multicast Addressing
 RPF
 IGMP
IP Multicast Addressing
 Multicast addresses (224.0.0.0/4) are
identified by coding of the four high-order
address
0 1
bits
2 3 31
1 1 1 0 Multicast Group ID
28 bits
 IANA maintains list of registered IP multicast

groups
• Base address 224.0.0.0 is reserved and cannot be
assigned to any group
• Multicast addresses from 224.0.0.1 through
224.0.0.255 are reserved for local wire use
Reserved Multicast Address Ranges
 Address ranges
• 239.0.0.0/8─Administratively scoped addresses (RFC
2365)
• Only to be used within a locally administered network, similar
to RFC 1918 address space
• 233.0.0.0/8—GLOP addressing (RFC 3180)
• Every AS is statically and automatically assigned 255 globally
usable multicast addresses from this range
233 AS Number Locally Assigned Bits
8 bits 16 bits 8 bits
• 232.0.0.0/8—SSM addressing (RFC 4607)

• A router will ignore a request for group membership (IGMPv3)
in this address range when a specific source is not specifically
requested
• 224.2.0.0/16—SDP/SAP addressing (RFC 2974)
• For use by applications that advertise multicast sessions (SDR)
IP Multicast-to-Ethernet Mapping
IPv4 prefix (32 bits)
First 4 high- 28 bits remain

order 111
bits are 0
stripped 224. 10. 8.
5 remaining high- 5 23 bits remain
order bits are for mapping
stripped
01-00-5e-0A-08-05
25 bits 23 bits
MAC address (48 bits)
IP Multicast-to-Ethernet Mapping
Example
E 0 0 A 0 8 0 5
1 1 1 0 0 0 0 0 0 0 0 0 1 0 1 0 0 0 0 0 1 0 0 0 0 0 0 0 0 1 0 1
Class D Address: 224.10.8.5
Not Used Low Order 23 Bits Mapped
0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 1 0 1 1 1 1 0 0 0 0 0 1 0 1 0 0 0 0 0 1 0 0 0 0 0 0 0 0 1 0 1
0 1 0 0 5 E 0 A 0 8 0 5
Resulting Ethernet Multicast Address
RPF
 IGMP
Multicast Routing Protocol
Characteristics
 Multicast routing differs from unicast routing
• Unicast routing decisions based on destination
• Multicast routing decisions based on sources
 RPF
• Directing traffic away from its source
 Distribution trees
• Shared or source specific
• Each individual router maintains an inbound interface
list and an outbound interface list for each multicast
group that it is aware of
• It is the multicast routing protocol that helps a router learn
when to add or remove an interface from its OIF list (create
and maintain the distribution tree)
RPF
 Multicast uses unicast routes to determine
the path back to the source—this determines
upstream or incoming interface
• RPF check ensures packets do not loop because
they are never flooded back towards their source
• RPF checks can be done using inet.0 and
normal unicast routing protocols (default Junos
OS behavior)
• MBGP can also be used to put unicast routes in inet.2
for RPF
The RPF Check (1 of 2)
RPF Table at R1 Source 1
user@R1> show multicast rpf 192.168.100.10 192.168.100.10
Multicast RPF table: inet.0 , 16 entries
192.168.100.0/24
Protocol: OSPF
Interface: ge-0/0/4.125
Neighbor: 172.18.1.1
172.18.1.1
ge-0/0/4.125
Packet
R1
Packet from Source 1 arrives on
wrong interface: RPF check fails, ge-0/0/1.0
discard the packet!
Multicast Traffic
The RPF Check (2 of 2)
RPF Table at R1
user@R1> show multicast rpf 192.168.100.10 Source 1
Multicast RPF table: inet.0 , 16 entries 192.168.100.10
192.168.100.0/24
Protocol: OSPF
Neighbor: 172.18.1.1
et
ck
172.18.1.1
Pa
ge-0/0/4.125
R1
Packet from Source 1 arrives on correct
interface: forward out all outgoing
interfaces
Multicast Traffic
Dense-Mode Routing Protocols
 Initially, assumes everyone wants to receive
multicasts
• Flood-and-prune mechanism builds distribution tree
• Initially, a router will flood multicast traffic out of all ports
• Routers without receivers must prune back branches
• Considerable overhead because every router must
maintain multicast state for each active source
 Eventually, creates a source-based distribution tree
• Root of this tree is the source host’s designated router
• Guarantees shortest, most efficient, path
 Examples
• DVMRP and PIM-DM
PIM-DM Operation and State
Source
Initial Flood of Multicast Packets 192.168.100.10
1.All routers will receive at least one copy of the
initial flow of traffic
Even routers that have
2.Each router performs an RPF check and packets
no
not passing RPF check are thrown away
receivers maintain an
3.Packets passing RPF are replicated and flooded out
(S,G) state for every
of every other interface. source and group
4.(S,G) state created on every router in the network combination.
Receiver
A
(S,G) State for R1 B

Source: 192.168.100.10 D
C
Group: 224.7.7.7
Incoming Interface: A R1
Outgoing Interface List:
B,C,D
Multicast Traffic
Receiver
Pruning Unwanted Traffic
 A router will send a prune
Source
message upstream if... 192.168.100.10
• There are no attached receivers
• A downstream PIM neighbor
exists and a prune message is
received from that neighbor
Receiver
A
B
D
C
R1
Prune Messages
Multicast Traffic
Receiver
After the Prune…
 Flood-and-prune process happens
Source
every 3 minutes
192.168.100.10
• (S,G) states expires after (S,G) State for R2
3 minutes Source:
• Flood/prune refreshes timer 192.168.100.10 Group:
224.7.7.7
• Needed in the case of adding a Incoming Interface:
receiver that did not previously exist Null
Outgoing Interface List:
Null
A R2
B D
C
Receiver R1
(S,G) State for R1
Source: 192.168.100.10
Multicast Traffic
Group: 224.7.7.7
Outgoing Interface List: Receiver
B,C
An SPT
 A shortest path Source
192.168.100.10
multicast forwarding
tree is the final result of
any multicast routing
protocol (PIM and
DVMRP)
A R2
B D
C
Receiver R1
Multicast Traffic
Receiver
Adding a Branch to the SPT
 Router closest to new Source
interested receiver (learned 192.168.100.10
from IGMP) sends a Join

message toward the source
• How does the router know the
source of multicast traffic?
A R2
B D
C
Receiver R1
R3
Join Messages
Multicast Traffic
Receiver New Receiver
New Branch of SPT Is Used for
Forwarding
 Multicast traffic is Source
192.168.100.10
delivered to the new (S,G) State for R2
receiver Source:
192.168.100.10
• Each router updates its Group: 224.7.7.7
(S,G) state with a non-Null Outgoing Interface
incoming interface and A List: B
outgoing interface list

B
A R2
B D
C
Receiver R1
R3
Multicast Traffic
Receiver New Receiver
 RPF
IGMP
IGMP
 Manages group membership between hosts
and routers
 IGMP message exchange
• Router queries
• Sends query messages to solicit group membership
• Host messages
• Report messages
• Leave-group messages
 The Junos OS supports IGMPv2, by default
• Configurable to v1 and v3
• Automatically enabled on multiprotocol ports
where PIM or DVMRP is configured
• v3 and v2 are backwards compatible with v1
Multicast Groups and Routing
Group Membership Protocol
Multicast Routing Protocol
 IGMP operates between receivers (hosts) and routers

• IGMP is not a routing protocol
IGMP Versions
 Version 1 (RFC 1112)
• Routers periodically transmit host membership query
messages to determine what groups have listeners on directly
attached networks
• Defines procedure for electing the multicast querier on a LAN
• Defines a group-specific query message
• Defines a leave-group message
• Reduces IGMPv1 leave group latency
• Supports group-source report/query messages and
enhancements to leave-group messages
• Provides source-specific multicast
IGMPv2 Join Process
 Report messages establish host membership
for particular multicast groups on a given
network
• Reports are sent to the group address being
reported
• Informs locally connected router that a host wants
to receive traffic
Hostdestined
1 for a particular
multicast group
Report:
DA=224.10.1.1
Group=224.10.1.1
Querier Non-
querier
IGMPv2 Query-Response Process
 Query-response process
1. Querier router sends general query to all-hosts
multicast group (224.0.0.1).
2. Host 2 sends its report for group 224.10.1.1 first.
3. Host 1 hears the response from Host 2 and
suppresses its report.
4. Host 3 sends its report for the group 224.20.1.1.
Host 1 Host 2 Host 3
2 4
3 Report
Report Report
224.10.1.1
224.10.1. 224.20.1.
Suppressed 1 1
General
1 Query
Router A Router B
Querier Non-querier
IGMPv2 Group Leave
 Process for leaving a group
1. Host 2 sends leave message for 224.10.1.1 to all-
routers multicast group address (224.0.0.2).
2. Querier router sends group-specific query for
224.10.1.1.
3. Group 224.10.1.1 times out if no IGMP reports are
received within ~3
Host 2 seconds. Host 3
1
Leave-group
Group=224.10.1
.1
Group-Specific
Query
2 Group=224.10.1
.1
Router A
(Querier)
IGMPv3 and SSM
 Host 1 wants to receive from S=172.16.20.1,
but not from S=192.168.30.1
• Host 1 sends inclusion group-source message for
S=172.16.20.1
• Host 1 sends exclusion group-source message for
S=192.168.30.1
Router A Router B
Source=172.16.20.1 Source=192.168.30.1
Group=224.10.1.1 IGMPv3 group-source report:
Group=224.10.1.1
X D: 224.0.0.22 (All IGMPv3
(Pruned) routers)
Router C
Include 172.16.20.1,
224.10.1.1
Exclude 192.168.30.1,
Host 1 member of 224.10.1.1 224.10.1.1
IGMP Protocol Configuration
 IGMP configured under [edit protocols
igmp]
[edit protocols igmp]
user@router# set ?
Possible completions:
accounting Enable join and leave event notification
+ apply-groups Groups from which to inherit configuration data
+ apply-groups-except Don't inherit configuration data from these groups
> interface Interface options for IGMP
maximum-transmit-rate Maximum transmission rate (packets per second) (1..10000)
query-interval When to send host query messages (1..1024 seconds)
query-last-member-interval When to send group query messages (seconds)
query-response-interval How long to wait for a host query response (seconds)
robust-count Expected packet loss on a subnet (2..10)
> traceoptions Trace options for IGMP
IGMP Interface Configuration
 Configure IGMP properties on an interface by
interface basis
user@router# set interface ge-0/0/4.0 ?
Possible completions:
<[Enter]> Execute this command
accounting Enable join and leave event notification
+ apply-groups Groups from which to inherit configuration data
+ apply-groups-except Don't inherit configuration data from these groups
disable Disable IGMP on this interface
group-limit Maximum number of (source,group) per interface (1..32767)
+ group-policy Group filter applied to incoming IGMP report messages
immediate-leave Group is removed immediately without sending query for last membership
no-accounting Don't enable join and leave event notification
+ oif-map Output interface map
> passive Suppress sending and receiving IGMP messages
promiscuous-mode Accept IGMP messages coming from different subnet
ssm-map Map for SSM translation of IGMPv1 or IGMPv2 messages
+ ssm-map-policy SSM map policy name
> static Static group or source membership
version Set IGMP version number on this interface (1..3)
| Pipe through a command
Sample IGMP Configuration
 IGMP configuration
• Interval settings represent the Junos OS defaults
user@router# show
query-interval 125;
query-response-interval 10;
query-last-member-interval 1;
robust-count 2;
maximum-transmit-rate 500;
interface ge-0/0/8.0 {
version 3;
static {
group 224.8.8.8 {
source 192.168.100.10;
}
}
}
Obtaining IGMP Interface Information
 IGMP interfaces
user@router> show igmp interface
Querier: 192.168.1.1
State: Up Timeout: None Version: 3 Groups: 3
Immediate leave: Off
Promiscuous mode: Off
Passive: Off
Configured Parameters:
IGMP Query Interval: 125.0
IGMP Query Response Interval: 10.0
IGMP Last Member Query Interval: 1.0
IGMP Robustness Count: 2
Derived Parameters:
IGMP Membership Timeout: 260.0
IGMP Other Querier Present Timeout: 255.0
Displaying IGMP Group Information
 Membership reporting by interface and group
user@router> show igmp group
Interface: ge-0/0/8.0, Groups: 3
Group: 224.0.0.251
Source: 0.0.0.0
Last reported by: 192.168.1.10
Timeout: 146 Type: Dynamic
Group: 224.7.7.7
Source: 0.0.0.0
Last reported by: 192.168.1.10
Timeout: 146 Type: Dynamic
Group: 224.8.8.8
Group mode: Include
Source: 192.168.100.10
Last reported by: Local
Timeout: 0 Type: Static
[...]
Displaying IGMP Statistics
 IGMP numbers
user@router> show igmp statistics
IGMP packet statistics for all interfaces
IGMP Message type Received Sent Rx errors
Membership Query 43 62 0
V1 Membership Report 0 0 0
DVMRP 0 0 0
PIM V1 0 0 0
Cisco Trace 0 0 0
Group Leave 0 0 0
Mtrace Response 0 0 0
Mtrace Request 0 0 0
Domain Wide Report 0 0 0
Other Unknown types 0
IGMP v3 unsupported type 0
IGMP v3 source required for SSM 0
IGMP v3 mode not applicable for SSM 0
IGMP Global Statistics

Bad Length 0
Bad Checksum 0
Bad Receive If 36
Rx non-local 11
Timed out 6
Rejected Report 0
Total Interfaces 5
Summary
 In this content, we:
• Described basic multicast terminology
• Described the multicast address space
• Described how RPF is used in a multicast network
• Described the basic functionality of IGMP
Review Questions
1. What are two benefits of using multicast to

deliver IP-based video to interested hosts?
2. What is the name of the router closest to
the source that is responsible for
forwarding multicast traffic into the
network?
3. What is the primary purpose of a multicast
routing protocol?
4. Which version of IGMP can be used by a
host to request multicast traffic from a
particular source?
Worldwide Education
Services

AJER-12.a C8 IntroMulticast

Uploaded by

Copyright:

Available Formats

AJER-12.a C8 IntroMulticast

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

AJER-12.a C8 IntroMulticast

Uploaded by

Copyright:

Available Formats

Introduction to Multicast

Network devices replicate data stream

• Group Membership Protocol: Protocol used by receivers

 IANA maintains list of registered IP multicast

8 bits 16 bits 8 bits

• 232.0.0.0/8—SSM addressing (RFC 4607)

First 4 high- 28 bits remain

Not Used Low Order 23 Bits Mapped

(S,G) State for R1 B

from IGMP) sends a Join

outgoing interface list

Receiver New Receiver

Multicast Routing Protocol

 IGMP operates between receivers (hosts) and routers

IGMP Global Statistics

1. What are two benefits of using multicast to

You might also like