You are on page 1of 65

Project: M rng mng MAN-E Cisco 2015

IP Multicast Implementation

Ni dung
Module 1 : Multicast Introduction
Module 2: IGMP and Layer 2 Issue

Module 3: Multicast Routing Protocol

Module 4: PIM SM Auto RP Announcement
Module 5: PIM SM and PIM SSM Configuration
Module 6: Introduce IPTV Model for MAN-E

Implement Multicast

Module 1: Multicast Introduction

Why Multicast ?

Multicast & Unicast

Multicast Advantages

Multicast Disadvantages

Type of Multicast Application

IP Multicast Application

IP Multicast Basic Addressing

IP Multicast Basic Addressing (cont.)

Layer 2 Multicast Addressing

Implement Multicast

Module 2: IGMP and Layer 2 Issue

IP Multicast Protocol Suite

Multicast routers use IGMP to maintain information for each router interface
about which multicast group traffic they should forward and which hosts
want to receive it

IGMPv2 Joining a Group

IGMPv2 Maintaining a Group

IGMPv2 Leaving a Group

IGMPv3 Joining a Group

IGMPv3 Changing a Group

Determining IGMP version running

Layer 2 Multicast Frame Switching

Layer 2 Multicast Switching Solution

Layer 2 Multicast Switching Solution - CGMP

Layer 2 Multicast Switching Solution IGMP Snooping

Implement Multicast

Module 3: Multicast Routing


Multicast Protocol Basic

Shortest-Path Tree

Shortest-Path Tree (cont.)

Shared Distribution Tree

Multicast Distribution Tree Identification

Multicast Forwarding

PIM-DM Flood and Prune

PIM-DM Flood and Prune (cont.)

PIM-DM Flood and Prune (cont..)

PIM Sparse Mode

PIM-SM Shared Tree Join

1. The leaf routers knows the IP
address of the RP for group G
and sends a (*,G) Join for this
group towards the RP
2. Building a branch of the Shared
Tree that extends from the RP
to the last-hop router directly
connected to the receiver

PIM-SM Source Registration

1. Source encapsulates
multicast data in Register
Message and unicasts to
2. RP encapsulates the
multicast data packet
inside of the Register
message and forwards it
down the Shared Tree
3. The RP also sends an
(S,G) Join back to the
source network S to
create a branch of an
(S,G) Shortest Path Tree

PIM-SM Source Registration (cont.)

1. As soon as the SPT is
build from teh Source
router to the RP,
multicast traffic begins to
flow natively from the
souce S to the RP
2. Once the RP begins
receiving data natively (ie
down the SPT) from
source S, it sends a
Register Stop to the
source's first hop router
to inform it that it can
stop sending the unicast
Register messages

PIM-SM Source Registration (cont..)

At this point, multicast traffic from the source is flowing down the SPT
to the RP and from there, down the Shared Tree to the receiver

PIM-SM SPT Switchover

The default behavior for the PIMSM leaf routers attached to active
receivers is to immediate join the
SPT to the source as soon as the
first packet arrives via the (*,G)
Shared Tree.
Can change SPT-Threshold
meaning multicast traffic rate
before switchover

Source-Specific Multicast (SSM), defined in RFC 4607, extends this concept to identify a set of
multicast hosts not only by group address but also by source.
IANA has reserved for SSM the IPv4 address
PIM SSM uses PIM SM work with IGMPv3 to
build SPT only toward to Source.
Advantages of PIM SSM
SSM channel is defined by both a source and
a group address, group addresses can be reused by multiple sources while keeping
channels unique.
SSM does not rely on the designation of a
rendezvous point (RP) to establish a
multicast tree.

Implement Multicast

Module 4: PIM SM Auto RP


Auto RP Discovery Overview

Router can use one of the following three methods to learn the IP address of
an RP:
The RP address can be statically configured on all the PIM-SM.
The Cisco-proprietary Auto-RP protocol can be used to designate the RP and advertise
its IP address so that all PIM-SM routers can learn its IP address automatically.
A standard BootStrap Router (BSR) protocol can be used to designate the RP and
advertise its IP address so that all the PIM-SM routers can learn its IP address

Auto-RP Protocol
Step 1:
The RP sends RP-Announce
messages to the reserved
multicast address
stating that the router is an RP.
The RP-Announce message
also allows the router to
advertise the multicast groups for
which it is the RP, thereby
allowing some load-balancing of
the RP workload among different

Auto-RP Protocol
Step 2:
One router be configured as a
mapping agent.
The mapping agent multicasts
another message, called RPDiscovery to informs
the general router population as
to which routers they should use
as RPs.

Simple Auto RP Configuration

BSR Protocol
1. The candidate-RPs send their
candidate-RP advertisements
directly to the elected BSR
2. The bootstrap message sent by
the BSR includes information about
all the candidate-RPs. BSR
message uses PIM Message hopby-hop on each router.
3. Each router uses a common
algorithm to select the same RP
address for a given multicast group

Simple BSR Configuration

On each router:

ip multicast-routing

On each interface:

ip pim sparse-mode

On Router A,C:

ip pim rp-candidate loopback 0

On Router B:

ip pim bsr-candidate loopback 0

Implement Multicast

Module 5: PIM SM & PIM SSM


PIM-SM Configuration Commands

PIM-SM Configuration Commands (cont.)

Auto-RP configuration

BSR configuration

PIM SSM Configuration Commands

Enable PIM SSM

Inspect Multicast Routing Table

Show ip mroute

Finding PIM Neighbor

Show ip pim interface

Show ip pim neighbor

Show ip pim rp


Enable Multicast Routing

Static RP

Auto-RP Configuration

IOS & IOS XR (cont.)

BSR Configuration

Enable PIM SSM

Implement Multicast

Module 6: Introduce IPTV Model


IPTV & VoD Service Model

1. STB unicasts to EPG and VoD
2. U-PE relays STBs DHCP
message to DHCP server
3. User isolation at Metro
switches , DSLAM and
Bridge-domain split horison
1. IP Multicast from BTV server
to STB
2. Using PIM SSM for multicast
routing. U-PE & PE-AGG must
have routes to BTV server in
IP routing table.
3. U-PE must map IGMPv2 to
IGMPv3 in case of STB
doesnt support IGMPv3

PIM SSM Mapping on U-PE

Example of configuring PIM SSM and SSM Mapping on U-PE

Project: M rng mng MAN-E Cisco 2015