Ch07 IP Multicast

Cisco Networking Academy Program
CCNP SWITCH: Implementing IP Switching
Chapter 7: Preparing the Campus for Advanced Services
2006, Cisco Systems, Inc. All rights reserved.

Presentation_ID.scr
The demand is increasing for Internet, intranet, and multimedia applications in which one
sender transmits to a group of receivers simultaneously. Examples of these applications
include the following:
Transmitting a corporate message to all employees
Broadcasting video and audio, including interactive video for distance learning and
IPTV
Transmitting data from a centralized data warehouse to multiple departments
Communicating stock quotes to brokers
Computing collaboratively
Algorithmic trading floor applications using cloud computing
Subsequently, using IP multicast instead of unicast to distribute this information reduces
the overall network load and bandwidth consumption. This is a result of IP multicasts
simultaneous distribution of an IP data frame to a host group that is defined by a single
multicast IP address, or flow. To accomplish this same distribution with unicast would
require the source to send a unicast frame to each host independently.
Note: Multicast reduces overall network load and bandwidth by distributing traffic to
multiple end users simultaneously.
The following slides discuss IP multicast routing and its inherent advantages, functionality,
and configuration in campus network. We begin with an introduction to multicast and then
discuss the fundamentals of the IP multicast. We also discuss the important Layer 3 and
Layer 2 multicast protocols and the design recommendations for deploying multicast in
multilayer switched networks.

Presentation_ID.scr

Presentation_ID.scr

Presentation_ID.scr

Presentation_ID.scr

Presentation_ID.scr

Presentation_ID.scr

Presentation_ID.scr

Presentation_ID.scr

Presentation_ID.scr
10

Presentation_ID.scr
11
IP multicast addresses specify a set of IP hosts that have joined a group

and are interested in receiving multicast traffic designated for that
particular group. The table outlines the IP multicast address conventions.
Applications allocate multicast addresses dynamically or statically.
Dynamic multicast addressing provides applications with a group address
on demand. Because dynamic multicast addresses have a specific
lifetime, applications must request this type of address only for as long as
the address is needed.
Statically allocated multicast addresses are reserved for specific protocols
that require well-known addresses, such as Open Shortest Path First
(OSPF). IANA assigns these well-known addresses, which are called
permanent host groups and are similar in concept to the well-known TCP
and UDP port numbers. The following slides discuss the details of the
multicast addresses listed in the table.

Presentation_ID.scr
12
IANA has reserved addresses in the range 224.0.0.0 to 224.0.0.255

(link local destination addresses) to be used by network protocols on
a local network segment. Routers do not forward packets in this
address range, because these packets are typically sent with a TimeTo-Live (TTL) value of 1. Network protocols use these addresses for
automatic router discovery and to communicate important routing
information. For example, OSPF uses the IP addresses 224.0.0.5
and 224.0.0.6 to exchange link-state information. Address 224.0.0.1
identifies the all-hosts group. Every multicast-capable host must join
this group when initializing its IP stack. If you send an ICMP echo
request to this address, all multicast-capable hosts on the network
answer the request with an ICMP echo reply. Address 224.0.0.2
identifies the all-routers group. Multicast routers join this group on all
multicast-enabled interfaces.

Presentation_ID.scr
13

Presentation_ID.scr
14

Presentation_ID.scr
15
Addresses in the 232.0.0.0 to 232.255.255.255 range are reserved for

Source-Specific Multicast (SSM), an extension of the Protocol
Independent Multicast (PIM) protocol that allows for an efficient datadelivery mechanism in one-to-many communications. In SSM, forwarding
decisions are based on both group and source addresses, which is
referred to as (S,G). The special notation of (S,G), pronounced S comma
G, uses S as the IP address of the source and G as the multicast group
address. This unique (S,G) is known within SSM as a channel. SSM also
removes address allocation problems because the source address makes
each channel unique. SSM requires that the host be aware of the source
and the group it wants data from and a method to signal this (S,G)
requirement to the router.

Presentation_ID.scr
16
RFC 3180, GLOP Addressing in 233/8, proposes that the 233.0.0.0 to

233.255.255.255 address range be reserved for statically defined
addresses by organizations that already have an autonomous system
number reserved. This practice is called GLOP addressing and the term is
not an acronym. The autonomous system number of the domain is
embedded into the second and third octets of the 233.0.0.0 to
233.255.255.255 address range. For example, the autonomous system
62010 is written in hexadecimal format as F23A. Separating the two
octets F2 and 3A results in 242 and 58 in decimal format, respectively.
These values result in a subnet of 233.242.58.0/24 that is globally
reserved for autonomous system 62010 to use.

Presentation_ID.scr
17

Presentation_ID.scr
18

Presentation_ID.scr
19

Presentation_ID.scr
20

Presentation_ID.scr
21

Presentation_ID.scr
22

Presentation_ID.scr
23

Presentation_ID.scr
24

Presentation_ID.scr
25

Presentation_ID.scr
26

Presentation_ID.scr
27

Presentation_ID.scr
28

Presentation_ID.scr
29

Presentation_ID.scr
30

Presentation_ID.scr
31

Presentation_ID.scr
32
Multicast-capable routers and multilayer switches create distribution trees that control the
path that IP multicast traffic takes through the network to achieve loop-free forwarding.
Reverse Path Forwarding (RPF) is the mechanism that performs an incoming interface
check to determine whether to forward or drop an incoming multicast frame. RPF is a key
concept in multicast forwarding. This RPF check helps to guarantee that the distribution
tree for multicast is loop-free. In addition, RPF enables routers to correctly forward
multicast traffic down the distribution tree.
In unicast routing, traffic is routed through the network along the path from the single
source to the single destination host. A router that is forwarding unicast packets does not
consider the source address, by default; the router considers only the destination address
and how to forward the traffic toward the destination with the exception of specialized
CEF features. Upon receipt of unicast packets, the router scans through its routing table
for the destination address and then forwards a single copy of the unicast packet out the
correct interface to the destination.
In multicast forwarding, the source is sending traffic to an arbitrary group of hosts that is
represented by a single multicast group address. When a multicast router receives a
multicast packet, it determines which direction is the upstream direction (toward the
source) and which one is the downstream direction (toward the receivers). A router
forwards a multicast packet only if the packet is received on the correct upstream
interface determined by the RPF process.
Note, although routers build a separate IP multicast routing table, the RFP check is
dependent on the unicast IP routing table for determining the correct upstream and
downstream interfaces.

Presentation_ID.scr
33

Presentation_ID.scr
34

Presentation_ID.scr
35

Presentation_ID.scr
36

Presentation_ID.scr
37

Presentation_ID.scr
38

Presentation_ID.scr
39
The simplest form of a multicast distribution tree is a source tree with

its root at the source and its branches forming a tree through the
network to the receivers. Because this tree uses the shortest path
through the network, it is also referred to as a shortest path tree
(SPT). The figure shows an example of an SPT for group 224.1.1.1
rooted at the source, Host A, and connecting two receivers, Hosts B
and C.
Using the (S,G) notation, the SPT for the example shown in the figure
is (192.168.1.1, 224.1.1.1).
The (S,G) notation implies that a separate SPT exists for each
source sending to each group. For example, if host B is also sending
traffic to group 224.1.1.1 and Hosts A and C are receivers, a separate
(S,G) SPT would exist with a notation of (192.168.2.2, 224.1.1.1).

Presentation_ID.scr
40

Presentation_ID.scr
41
Unlike source trees, which have their root at the source, shared trees
use a single common root placed at some chosen point in the
network. This shared root is called a rendezvous point (RP). The
figure shows a shared unidirectional tree for the group 224.1.1.1 with
the root located at Router D. Source traffic is sent toward the RP on a
shared tree. The traffic is then forwarded down the shared tree from
the RP to reach all the receivers unless the receiver is located
between the source and the RP, in which case the multicast traffic is
serviced directly.
In the figure, multicast traffic from the sources, Hosts A and D, travels
to the root (Router D) and then down the shared tree to the two
receivers, Hosts B and C. Because all sources in the multicast group
use a common shared tree, a wildcard notation written as (*,G),
pronounced star comma G, represents the tree. In this case, *
means all sources, and G represents the multicast group. Therefore,
the shared tree shown in the figure is written as (*, 224.1.1.1).

Presentation_ID.scr
42

Presentation_ID.scr
43
Both source trees and shared trees avoid multicast traffic loops.
Routing devices replicate the multicast packets only where the tree
branches.
Members of multicast groups join or leave at any time; as a result,
the distribution trees update dynamically. When all the active
receivers on a particular branch stop requesting traffic for a particular
multicast group, the routers prune that branch from the tree and stop
forwarding traffic down it. If one receiver on that branch becomes
active and requests the multicast traffic, the router dynamically
modifies the distribution tree and starts forwarding traffic again.
Source trees have the advantage of creating the optimal path
between the source and the receivers. This advantage guarantees
the minimum amount of network latency for forwarding multicast
traffic. However, this optimization requires additional overhead
because the routers maintain path information for each source. In a
network that has thousands of sources and thousands of groups, this
overhead quickly becomes a resource issue on routers or multilayer
switches. Memory consumption and troubleshooting complexity from
the size of the multicast routing table are factors that network
designers need to take into consideration when designing multicast
networks.
Shared trees have the advantage of requiring the minimum amount
of state information in each router. This advantage lowers the overall
memory requirements and complexity for a network that allows only

Presentation_ID.scr
44
shared trees. The disadvantage of shared trees is that, under certain

circumstances, the paths between the source and receivers might not be
the optimal paths, which can introduce additional latency in packet delivery.
As a result, shared trees might overuse some links and leave others
unused, whereas source-based trees (where sources are distributed)
usually distribute traffic across a set of links. For example, in the figure on
the right, the shortest path between Host A (Source 1) and Host B (a
receiver) is between Router A and Router C. Because Router D is the root
for a shared tree, the traffic traverses Routers A, B, D, and then C. Network
designers need to carefully consider the placement of the RP when
implementing a shared treeonly environment.

Presentation_ID.scr
44

Presentation_ID.scr
45

Presentation_ID.scr
46

Presentation_ID.scr
47
PIM dense mode (PIM-DM) multicast routing protocols rely on

periodic flooding of the network with multicast traffic to set up and
maintain the distribution tree. PIM relies on its neighbor information to
form the distribution tree. PIM-DM uses a source distribution tree to
forward multicast traffic, which is built by respective routers as soon
as any multicast source begins transmitting. The figure illustrates an
example of PIM-DM.
PIM Dense Mode is obsolete and no longer deployed in campus
networks. This discussion is included for the purposes of historical
completeness.
PIM-DM assumes that the multicast group members are densely
distributed throughout the network and that bandwidth is plentiful,
meaning that almost all hosts on the network belong to the group.
When a router configured for PIM-DM receives a multicast packet,
the router performs the RPF check to validate the correct interface for
the source and then forwards the packet to all the interfaces
configured for multicasting until pruning and truncating occurs. All
downstream routers receive the multicast packet until the multicast
traffic times out. PIM-DM sends a pruning message upstream only
under the following conditions:
Traffic arrives on a non-RPF, point-to-point interface; this is the
next-hop router interface that does not have a best route toward
the multicast source.
A leaf router without receivers sends a prune message, as

Presentation_ID.scr
48
shown in the figure, and the router, which does not have members or
receivers, sends the prune message to the upstream router.
A non-leaf router receives a prune message from all of its neighbors.
In summary, PIM-DM works best when numerous members belong to each
multimedia group. PIM floods the multimedia packet to all routers in the
network and then prunes routers that do not service members of that
particular multicast group.
Consider when planning multicast in the campus network that PIM-DM is
most useful in the following cases:
Senders and receivers are in close proximity to one another.
PIM-SM goes through a dense-mode flooding phase before fully
relying on the RP for multicast forwarding.
There are few senders and many receivers.
The volume of multicast traffic is high.
The stream of multicast traffic is constant.
Nevertheless, PIM-DM is not the method of choice for most campus
networks enterprise because of its scalability limitations and flooding
properties.

Presentation_ID.scr
48

Presentation_ID.scr
49

Presentation_ID.scr
50

Presentation_ID.scr
51

Presentation_ID.scr
52
The second approach to multicast routing, PIM sparse mode (PIMSM), is based on the assumptions that the multicast group members
are sparsely distributed throughout the network and that bandwidth is
limited.
It is important to note that PIM-SM does not imply that the group has
few members, just that they are widely dispersed. In this case,
flooding would unnecessarily waste network bandwidth and could
cause serious performance problems. Therefore, PIM-SM multicast
routing protocols rely on more selective techniques to set up and
maintain multicast trees.
PIM-SM protocols begin with an empty distribution tree and add
branches only as the result of explicit requests to join the distribution.
The figure illustrates a sample of PIM sparse mode.
With PIM-SM, each data stream goes to a relatively small number of
segments in the campus network. Instead of flooding the network to
determine the status of multicast members, PIM-SM defines an RP.
When a sender wants to send data, it first does so to the RP. When a
receiver wants to receive data, it registers with the RP, as shown in
the figure. When the data stream begins to flow from sender to RP to
receiver, the routers in the path automatically optimize the path to
remove unnecessary hops. PIM-SM assumes that no hosts want the
multicast traffic unless they specifically ask for it. In PIM-SM, the
shared tree mode can be switched to a source tree after a certain
threshold to have the best route to the source. All Cisco IOS routers

Presentation_ID.scr
53
and switches, by default, have the SPT threshold set to 0, such that the lasthop router switches to SPT mode as soon as the host starts receiving the
multicast, to take advantage of the best route for the multicast traffic.
Note: To clarify a common confusion, sparse-mode only uses the RP as a
initial point to forward multicast by default; configuration options exist to
foreword all traffic to the RP.
PIM-SM is optimized for environments where there are many multipoint data
streams. When planning for multicast deployments in the campus network,
choose PIM-SM with IP under the following scenarios:
There are many multipoint data streams.
At any moment, there are few receivers in a group.
The type of traffic is intermittent or busty.

Presentation_ID.scr
53

Presentation_ID.scr
54
PIM can simultaneously support dense mode operation for some

multicast groups and sparse mode operation for others. Cisco has
implemented an alternative to choosing just dense mode or just
sparse mode on a router interface, however. This was necessitated
by a change in the paradigm for forwarding multicast traffic via PIM
that became apparent during its development. It turned out that it was
more efficient to choose sparse or dense mode on a per-group basis
rather than a per-router interface basis. Sparse-dense mode
facilitates this ability.
PIM sparse-dense mode enables individual groups to use either
sparse or dense mode depending on whether RP information is
available for that group. If the router learns RP information for a
particular group, sparse mode is used; otherwise, dense mode is
used. Note, PIM spare-dense mode is seldom used in campus
networks.

Presentation_ID.scr
55

Presentation_ID.scr
56
PIM version 2 is a standards-based multicast protocol in the Internet Engineering Task Force (IETF). Cisco highly
recommends using PIM version 2 in the entire multilayer switched network. The Cisco PIM version 2 implementation
enables interoperability and transition between version 1 and version 2, although there are a few caveats. For example,
if a PIM version 2 router detects a PIM version 1 router, the version 2 router downgrades itself to version 1 until all
version 1 routers have been shut down or upgraded.
PIM version 2 uses the BSR to discover and announce RP-to-group mapping information for each group prefix to all the
routers in a PIM domain. This is the same function accomplished by Auto-RP. However, the BSR feature is part of the
PIM version 2 specifications because bootstrap messages are sent on a hop-by-hop basis, and a PIM version 1 router
prevents these messages from reaching all routers in a network. Therefore, if a network has a PIM version 1 router with
Cisco routers, it is best to use Auto-RP rather than the bootstrap mechanism. Nevertheless, Auto-RP is a standalone
protocol, separate from PIM version 1, and is Cisco proprietary. The BSR mechanism interoperates with Auto-RP on
Cisco routers.
A PIM version 2 BSR that is also an Auto-RP mapping agent automatically advertises the RP elected by Auto-RP. That
is, Auto-RP prevails in its imposition of a single RP on every router in the group.
In summary, PIM version 2 includes the following improvements over PIM version 1:
A single, active RP exists per multicast group, with multiple backup RPs. This single RP compares to multiple
active RPs for the same group in PIM version 1.
A BSR provides a fault-tolerant, automated RP discovery and distribution mechanism. Thus, routers dynamically
learn the group-to-RP mappings.
Sparse mode and dense mode are properties of a group, as opposed to an interface. Cisco strongly
recommends sparse-dense mode configurations.
PIM join and prune messages have more flexible encodings for multiple address families.
A more flexible hello packet format replaces the query packet to encode current and future capability options.
Register messages to an RP indicate whether they were sent by a border router or a designated router.
PIM no longer uses the IGMP protocol for transport; PIM version 2 uses standalone packets.
When planning for PIM deployments in the campus network, prefer to use PIM version 2 over PIM version 1.
Note: Several newer versions of PIM sparse-mode protocols are gaining popularity in campus networks. These
versions are outside the scope of this course:
Any Source Multicast (ASM), which uses RPs with either shortest path tree or shared tree.
Source Specific Multicast (SSM), which does not use RP and is designed using only shortest path tree.
Bidirectional PIM (Bi-dir PIM), which is based on shared trees only.

Presentation_ID.scr
57

Presentation_ID.scr
58

Presentation_ID.scr
59

Presentation_ID.scr
60

Presentation_ID.scr
61

Presentation_ID.scr
62

Presentation_ID.scr
63

Presentation_ID.scr
64

Presentation_ID.scr
65

Presentation_ID.scr
66

Presentation_ID.scr
67

Presentation_ID.scr
68

Presentation_ID.scr
69

Presentation_ID.scr
70

Presentation_ID.scr
71

Presentation_ID.scr
72

Presentation_ID.scr
73

Presentation_ID.scr
74

Presentation_ID.scr
75

Presentation_ID.scr
76

Presentation_ID.scr
77

Presentation_ID.scr
78

Presentation_ID.scr
79

Presentation_ID.scr
80

Presentation_ID.scr
81
In addition to the preceding commands, every Cisco switch supports

additional multicast tuning features such as rate limiting and altering the
protocol timers.

Presentation_ID.scr
82

Presentation_ID.scr
83

Presentation_ID.scr
84

Presentation_ID.scr
85

Ch07 IP Multicast

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Ch07 IP Multicast

Hochgeladen von

Copyright:

Verfügbare Formate

Cisco Networking Academy Program

CCNP SWITCH: Implementing IP Switching

Chapter 7: Preparing the Campus for Advanced Services

2006, Cisco Systems, Inc. All rights reserved.

2006, Cisco Systems, Inc. All rights reserved.

2006, Cisco Systems, Inc. All rights reserved.

2006, Cisco Systems, Inc. All rights reserved.

2006, Cisco Systems, Inc. All rights reserved.

2006, Cisco Systems, Inc. All rights reserved.

2006, Cisco Systems, Inc. All rights reserved.

2006, Cisco Systems, Inc. All rights reserved.

2006, Cisco Systems, Inc. All rights reserved.

2006, Cisco Systems, Inc. All rights reserved.

2006, Cisco Systems, Inc. All rights reserved.

IP multicast addresses specify a set of IP hosts that have joined a group

2006, Cisco Systems, Inc. All rights reserved.

IANA has reserved addresses in the range 224.0.0.0 to 224.0.0.255

2006, Cisco Systems, Inc. All rights reserved.

2006, Cisco Systems, Inc. All rights reserved.

2006, Cisco Systems, Inc. All rights reserved.

Addresses in the 232.0.0.0 to 232.255.255.255 range are reserved for

2006, Cisco Systems, Inc. All rights reserved.

RFC 3180, GLOP Addressing in 233/8, proposes that the 233.0.0.0 to

2006, Cisco Systems, Inc. All rights reserved.

2006, Cisco Systems, Inc. All rights reserved.

2006, Cisco Systems, Inc. All rights reserved.

2006, Cisco Systems, Inc. All rights reserved.

2006, Cisco Systems, Inc. All rights reserved.

2006, Cisco Systems, Inc. All rights reserved.

2006, Cisco Systems, Inc. All rights reserved.

2006, Cisco Systems, Inc. All rights reserved.

2006, Cisco Systems, Inc. All rights reserved.

2006, Cisco Systems, Inc. All rights reserved.

2006, Cisco Systems, Inc. All rights reserved.

2006, Cisco Systems, Inc. All rights reserved.

2006, Cisco Systems, Inc. All rights reserved.

2006, Cisco Systems, Inc. All rights reserved.

2006, Cisco Systems, Inc. All rights reserved.

2006, Cisco Systems, Inc. All rights reserved.

2006, Cisco Systems, Inc. All rights reserved.

2006, Cisco Systems, Inc. All rights reserved.

2006, Cisco Systems, Inc. All rights reserved.

2006, Cisco Systems, Inc. All rights reserved.

2006, Cisco Systems, Inc. All rights reserved.

2006, Cisco Systems, Inc. All rights reserved.

2006, Cisco Systems, Inc. All rights reserved.

The simplest form of a multicast distribution tree is a source tree with

2006, Cisco Systems, Inc. All rights reserved.

2006, Cisco Systems, Inc. All rights reserved.

2006, Cisco Systems, Inc. All rights reserved.

2006, Cisco Systems, Inc. All rights reserved.

2006, Cisco Systems, Inc. All rights reserved.

shared trees. The disadvantage of shared trees is that, under certain

2006, Cisco Systems, Inc. All rights reserved.

2006, Cisco Systems, Inc. All rights reserved.

2006, Cisco Systems, Inc. All rights reserved.

2006, Cisco Systems, Inc. All rights reserved.

PIM dense mode (PIM-DM) multicast routing protocols rely on

2006, Cisco Systems, Inc. All rights reserved.

2006, Cisco Systems, Inc. All rights reserved.

2006, Cisco Systems, Inc. All rights reserved.

2006, Cisco Systems, Inc. All rights reserved.

2006, Cisco Systems, Inc. All rights reserved.

2006, Cisco Systems, Inc. All rights reserved.