Scribd
Upload
16 views63 pages

Multicast - 1

MULTICAST COURS

Uploaded by

ybouguerroumapro
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
16 views63 pages

Multicast - 1

MULTICAST COURS

Uploaded by

ybouguerroumapro
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 63

Introduction to Multicast

Multicast scalability
Multicast traffic is transmitted using one of three common variations:

• One to Many : Concerts, TV, stock tickers, announcements,


Network time

• Many to Many : AV Conferences, whiteboards, collaboration,


video gaming,

• Many to One : Video surveillance, polling

In all transmission modes, the scalability advantages of Multicast over


Unicast become apparent when comparing the number of hosts
relative to the amount of traffic required:
Network traffic address types
A proper IP address and/or MAC address is required for a packet to reach its intended
destination. When transmitting multicast packets, special address ranges are reserved
specifically for multicast groups.
The table below shows that Class D IP addresses are reserved for the sole purpose of
multicast groups:
Multicast address groupings
• Multicast addresses do not explicitly define a collection of individual devices, instead they define
a multicast group that endpoint devices can listen to and receive traffic from, or transmit traffic
to.

• Multicast groups refer to specific sets of network devices that have requested to receive specific
multicast transmissions.

• Multicast IP addresses differ from other IP addresses because they do not get associated with a
single device, instead they provide a destination-only address which identifies a group of devices.

• The group of devices that is associated with a multicast IP address is dynamic and changes over
time as different devices join and leave the group.

• The address groupings of the Class D IP Multicast range from 224.0.0.0 to 239.255.255.255
is further divided into three multicast address groups:
Locally scoped (reserved link local) addresses
Reserved by the Internet Assigned Numbers Authority (IANA) for
network protocol use.

• Fall in the Address range from 224.0.0.0 through 224.0.0.255


• Multicasts in this range are never forwarded off the local network,
regardless of Time to Live (TTL). Typically, the TTL gets set to 1.
• Some common examples of other network protocols in this address
space include OSPF, EIGRP, RIPv2, VRRP, PIM, which are multicast
protocols specific to routers.
• Note that most multicast applications operating in this link-local
address scope, including routing protocols, do not subscribe into
their multicast groups via IGMP because it is technically not
necessary for link-local multicasts to get forwarded beyond a router.
Globally and Administratively scoped addresses

• Globally scoped addresses fall in the range of 224.0.1.0 through


238.255.255.255.

• The familiar protocol falling in this range is 224.0.1.129 utilized for


the Precision Time Protocol (PTP) which is used to synchronize clocks
on a network.

• Administratively scoped addresses 239.0.0.0 through


239.255.255.255 are reserved for use inside private domains.
Multicast destination MAC Addresses
• While IP addresses are reserved for multicasting at layer 3, getting multicast to
work on layer 2 traffic requires MAC addresses and Ethernet frames.

• Standard Network Interface Cards (NICs) on a LAN segment only receive packets
destined for their burned-in MAC address relying on Address Resolution Protocol
(ARP) to find out the hardware (MAC) address of a device from an IP address.
However, there is no equivalent to the Address Resolution Protocol (ARP) for
multicast address mapping.

• As a result, multicast MAC addresses are derived from the multicast IP address that
is being used. This means that multicast MAC addresses are not hard-coded to a
piece of hardware like typical MAC addresses are.
• All MAC addresses always begin with the organizationally unique identifier (OUI).
For multicast MAC address, the OUI is always 01:00:5e. After the OUI, the
multicast MAC address is padded with a binary 0. The remaining bits of the
multicast MAC address are derived from the multicast IP address.

• When converted to binary, a multicast IP address will always start with a fixed 4-bit
header of binary 1110 (due to the restricted IP address range for multicast). This
leaves 28 bits of significant ipv4 addresses remaining that are used to relate a
multicast IP address with a MAC address. However, after the OUI and the binary 0,
the MAC address only has 23 bits left. So, some of the bits of the IP address are
shaved off to fit within the remaining space of the MAC address. The diagram
below illustrates the derivation of a multicast MAC address.
Since 5 bits of the IP address are lost in this transformation, there is never a
1:1 relationship between an multicast MAC address and a multicast IP
address. In fact, every multicast MAC address has 32 multicast IP addresses
that map to it. This can potentially create confusion and cause multicast
packets to be delivered to devices that don't want them. These unwanted
packets can be filtered out at layer 3, but this filtering can consume CPU
resources, especially if the bandwidth of multicast traffic is high
• To fix the multicast flooding problem created by IGMP, IGMP snooping was implemented as
a feature on switches allowing them ability to act the way an IGMP router operates, using
IGMP messages to determine what switch ports will forward and receive multicast traffic.
Through the snooping mechanism, the receivers' IGMP join and leave messages exist so the
switch can process how many copies to make of the multicast transmissions and decide on
which ports to forward those packets.

• The IGMP version used by the switch must match the sending host in order to be functional,
IGMP v3 is backwards compatible to 2, and 2 to 1. It is best to match the versions so similar
versions but should defer to manufacturer for appropriate version.

• IGMP is the protocol that devices use to send a message to tell the switch they want to
receive a stream; the join request gets sent to the switch and the IGMP snooping table gets
populated and mapped to their respective port identifiers.
IGMP
Multicast routing protocols
IGMP

• Internet Group Management Protocol introduces


the concept of IP multicast groups, raising the
question of "How does a router or switch know
which ports to send each multicast packet to?“

• The answer is IGMP, Internet Group Management


Protocol, which leverages a set of control messages
that IP multicast-enabled devices send to each
other to join and leave multicast groups.
IGMP SNOOPING
IGMP Snooping
• IGMP is a layer 3 protocol, which means that switches (operating at layer 2)
should be unaware of it. However, if switches are unaware of IGMP, how can
they know what ports to send a multicast packet to?

• The answer is: they don't. By default, a switch will treat a multicast packet like
a broadcast packet, and send it to all ports, unless that switch supports IGMP
snooping.

• IGMP snooping is a switch feature designed to reduce multicast flooding,


effectively preventing the switch from broadcasting everything that comes
into the switch to all nodes on the switch.

• Instead IGMP snooping lets the switch listen to the IGMP joining messages to
build a map of what ports actually want to be members of which multicast
groups.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy