Brkipm 1261 PDF

Party Time
BRKIPM-1261 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 3
Introduction and
Troubleshooting IP
Multicast
Kyd Cao Customer Support Engineer

BRKIPM-1261
kycao@cisco.com
Cisco Spark
Questions?
Use Cisco Spark to communicate
with the speaker after the session
How
1. Find this session in the Cisco Live Mobile App
2. Click “Join the Discussion”
3. Install Spark or go directly to the space
4. Enter messages/questions in the space
© 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public
Agenda
• Why?
 Multicast Overview
• What?
 Multicast Fundamental
• How?
 Case Study – Multicast
Deployment
• How to Troubleshoot?
Multicast Overview
Unicast Vs Multicast
Unicast
Receiver
Sender
Receiver
Receiver
Number of streams
Multicast Receiver
Receiver
Receiver
Broadcast Vs Multicast
I don’t I don’t
want this want this
traffic ! traffic !
Broadcast
Receiver
Sender
Receiver
Receiver
Multicast
Receiver
Sender
Receiver
Receiver
Multicast Advantages
• Scalability
Network utilisation is independent of the number of receivers
• Utilisation
Controls network bandwidth and reduces server and router loads
• Performance
Subscriber number 1 and subscriber number 10000 have identical experience
Multicast Uses
• Any applications with multiple • Server/Website replication
receivers
• Reducing network/resource
• One-to-many or many-to-many
overhead
• Live video distribution • More than multiple point-to-point
flows
• Collaborative groupware
• Resource discovery
• Periodic data delivery—“push”
technology • Distributed interactive simulation
• Stock quotes, sports scores, (DIS)
• War games
• Inter Data Centre L2 Underlay
• Virtual reality
• VXLAN, etc. for BUM
Multicast Considerations
Multicast is UDP-based
• “Best effort” delivery
• No congestion avoidance
• Duplicates
• Out of order delivery
Multicast Fundamental
Frequent Use term
• MC – Multicast • FHR - First Hop Router
• IGMP – Internet Group Management Protocol • LHR - Last Hop Router
• ASM – Any source Multicast

• SSM – Source specific Multicast
• PIM – Protocol Independent Multicast
• RPF – Reverse Path Forwarding
• PIM-SM – Protocol Independent Multicast
Sparse Mode
• MDT - Multicast Distribution Tree
• RP –Rendezvous Point
Multicast Service Model Overview
5. Router already receiving stream

‘A’ sends it onto router that
3a. I need requested it
stream ‘A’
7. Now receiving
Stream ‘A’
2b. Host-router 1. Source already sending

2a. I want to receive signalling protocol stream ‘A’
stream ‘A’ 3b. Router-router
signalling protocol
4b. Router-router
signalling protocol
6. Router now receiving stream ‘A’

4a. I need
sends it onto router that
stream ‘A’
requested it
Members Layer 2 Network Layer 3 Network Source
IP Multicast Source
1. Source already sending

stream ‘A’
Unicast Vs Multicast Addressing
Unicast
Receiver
IP: 13.1.1.1
Sender
Receiver IP: 10.1.1.1
IP: 11.1.1.1
Receiver
IP: 12.1.1.1
Multicast
Receiver
Multicast Sender
Group address Receiver IP: 10.1.1.1
224.1.1.1
Receiver
Multicast Addressing
IPv4 Header
Version IHL Type of Service Total Length
Identification Flags Fragment Offset
Time to Live Protocol Header Checksum
Source
Source Always the unique unicast origin address of
SourceAddress
1.0.0.0 - 232.255.255.255 (Class A, B, C) the packet – same as unicast
Destination DestinationAddress
224.0.0.0 - 239.255.255.255 (Class D) Multicast Group Address Range
Options Padding
• Reserved link-local addresses (Never use them)
• 224.0.0.0–224.0.0.255
• Transmitted with TTL = 1
• Examples
• 224.0.0.1 All systems on this subnet
• 224.0.0.2 All routers on this subnet
• 224.0.0.5 OSPF routers
• 224.0.0.13 PIMv2 routers
• 224.0.0.22 IGMPv3
• Other IANA reserved addresses

• 224.0.1.0–224.0.1.255
• Not local in scope (transmitted with TTL > 1)
• Examples
• 224.0.1.1 NTP (Network Time Protocol)
• 224.0.1.32 Mtrace routers
• 224.0.1.78 Tibco Multicast1
• Administratively scoped addresses
• 239.0.0.0–239.255.255.255
• Private address space
• Similar to RFC1918 unicast addresses
• Not used for global Internet traffic—scoped traffic
• SSM (Source Specific Multicast) range

• 232.0.0.0–232.255.255.255
• Primarily targeted for Internet-style broadcast
• Layer 2 Multicast Address

• 0100.5e00.0000 - 0100.5e7f.ffff
• The lower 23 bits of the IP multicast group address
map into the lower 23 bits of the Ethernet address
IP Multicast Source
• Any device that sends an IP packet with a destination address between
224.0.0.0 – 239.255.255.255
• A device can be a multicast sender and a multicast receiver at the same time
• There is no multicast control traffic between the sender and the network, or
between the sender and receiver.
• Source does not need to join the multicast group, they just send.
• Applications controls when source to send multicast data.
Multicast Service Model Overview – Layer 2
2b. Host-router
1. Source already sending
2a. I want to receive signalling protocol
stream ‘A’
stream ‘A’
IGMP
Host-Router Signalling: IGMP
• Internet Group Management Protocol

• Used by a host to notify the local router that it wishes to receive (or stop
receiving) multicast traffic for a given destination address or “group”.
• RFC 2236 specifies version 2 of IGMP (a form of ASM - Any source
Multicast)
Most widely deployed and supported
• RFC 3376 specifies version 3 of IGMP (a form of SSM - source specific
Multicast)
Good network support
IGMPv2 – Joining a Group
No-receiver
Additional
reports for
234.1.1.1
Receiver 1 supressed
Eth0:10.1.1.1
I want to
receiv MC Stream
group
234.1.1.1
First-hop router
Note: The IGMP Eth0:10.1.1.254
message does not
include the identity IGMP Membership Report
of the multicast Requested Group: 234.1.1.1
source Source IP: 10.1.1.1
Destination IP: 234.1.1.1
Non-receiver
IGMP Membership Report Receiver 2

Message on this segment Eth0:10.1.1.2
I also want
Requested Group: 234.1.1.1
to receive
Source IP: 10.1.1.2 Additional IGMP
group Additional
Destination IP: 234.1.1.1 reports for
reports for 234.1.1.1
234.1.1.1 234.1.1.1
Receiver 1
are suppressed by
supressed
Eth0:10.1.1.1 switch
X MC Stream
First-hop router
Eth0:10.1.1.254
Non-receiver
IGMPv2 – Maintaining a Group
Receiver 2
Eth0:10.1.1.2
I don’t
require this
stream any IGMP
IGMP Leave
Leave message
message
more Leave
Leave Group: 234.1.1.1
Group: 234.1.1.1
Source
Source IP:
IP: 10.1.1.2
10.1.1.2
Receiver 1 Destination
Destination IP:
IP: 224.0.0.2
224.0.0.1
Eth0:10.1.1.1 Router
E0:10.1.1.254
I still MC Stream
need Does
234.1.1.1 anyone still
need group
234.1.1.1 ?
IGMP
IGMP Membership Report
Membership Report
IGMP Group
IGMP Membership
Group Membership
Message onthis
message on thissegment
segment Query message
Query message
Requested Group: 234.1.1.1 Membership Group: 234.1.1.1
Source IP: 10.1.1.1 Source IP:
Membership 10.1.1.254
Group: 234.1.1.1
Destination Destination IP: 224.0.0.1
Source IP: IP: 224.0.0.2
10.1.1.1 Source IP: 10.1.1.254
Destination IP: 234.1.1.1 Destination IP: 234.1.1.1
Non-receiver
IGMPv2 – Leaving a Group
Non-receiver
T+3s: No response to Group

Membership Query.
Stop sending to group 234.1.1.1
after 3secs with default timers
Receiver 1
E0:10.1.1.254
I don’t
MC Stream
require this
stream any
more
IGMP Leave message

Source IP: 10.1.1.1
Non-receiver
IGMPv2 – Leaving a Group
Does T+2s
anyone still
Non-receiver need group
Eth0:10.1.1.2 234.1.1.1 ?

Membership Query. Query.
Membership
Stop
Stop sendingtotogroup
sending group234.1.1.1
234.1.1.1
After T+2secs
after withdefault
3secs with defaulttimers
timers
Non-Receiver
T+1s
Eth0: 10.1.1.2 Router
E0:10.1.1.254 Does anyone still
need group
234.1.1.1? MC Stream
Does
anyone still
need group
234.1.1.1 ?
IGMP Group Membership
Membership Group: 234.1.1.1
Query message
Source IP:10.1.1.254
Membership Group: 234.1.1.1 IGMP Group Membership
Destination IP:224.0.0.1
Source IP: 10.1.1.254
Query message
Non-receiver
IGMP Snooping
• By default, switches forward all layer 2 multicast frames to all ports (except the
originating port)
• IGMP snooping eavesdrops on IGMP messaging
• Switch constrains MC to only ports that want it (key point)
• IGMP snooping is on by default in IOS-based switches
• Replaced Cisco Group Management Protocol (CGMP).
Advantages of IGMP Snooping
• Hosts only receive MC traffic that they request

• Report suppression – switch acts as a IGMP middleman, prevents first-hop
router from being flooded with IGMP reports for the same group
• “Fast-leave” functionality – stop sending MC group as soon as switch hears a
“leave” on an interface
Q. When would IGMP snooping fast-leave be a bad idea ?

A. When there is more than 1 receiver attached to an interface
• But.....we have a problem. The receiver just told me the group it wants to join
but didn’t identify the source! So in which direction is the “upstream” router ?
Where can I
joint group
234.1.1.1 ?
I want
234.1.1.1
IGMP
? Source
192.168.1.1
1st IGMP Membership 1. Source already sending
Report message on this stream ‘A’
segment
Note: The IGMP
Source IP: 10.1.1.1 message does not
Destination IP: 224.0.0.1 include the identity
of the multicast
source
Unicast vs. Multicast Routing/Forwarding
Unicast Routing/Forwarding
• Destination IP address directly indicates where to forward packet
• Unicast Routing protocols build a table of destination/interface/next-hop triples
• Unicast Forwarding is hop-by-hop simply based on these entries
• Unicast routing table determines interface and next-hop router to forward packet
Unicast vs. Multicast Routing/Forwarding
Multicast Routing & Forwarding
• Destination Group address doesn’t directly indicate where to forward packet.
Distributing trees are used to describe forwarding path.
• Multicast Routing is Backwards from Unicast Routing
 Multicast Routing builds a Multicast Distribution tree backwards from the receivers to
the source.
 Trees are built via connection requests (Joins) “sent” toward the source.
 Joins follow the unicast routing table backwards toward the source.
 Joins create Multicast tree/forwarding state in the routers along the tree.
 Trees are rebuilt dynamically in case of network topology changes.
 Only when a tree is completely built from receiver backwards to the source can
source traffic flow down the tree to the receivers.
 Multicast routing use separate routing table - mroute
Source Tree
Receiver for
239.194.0.5
• Traffic travels from source (root) to receivers
(leaves), shortest path taken
• Packets replicated at branch point
• Forwarding entry states represented as (S, G)
Receiver for in mroute table
239.194.0.5
(S, G) entry is
(196.7.25.12,
239.194.0.5)
Source 196.7.25.12
transmitting to
group 239.194.0.5
Shared Tree Receiver for
Receiver for 239.194.0.4
239.194.0.5
• Root is a common point
• Rendezvous Point
Source 196.7.25.11
• Receivers join RP
transmitting to
group 239.194.0.4 • To learn of sources
• Sources only transmit to RP

RP forward to receivers
(*, G)
(*,239.194.0.4) • Forwarding represented as (*, G)
(*,239.194.0.5) in mroute table
Rendezvous
Point Source 196.7.25.12
transmitting to
group 239.194.0.5
Multicast Service Model Overview
3a. I need
stream ‘A’
2b. Host-router
2a. I want to receive signalling protocol
stream ‘A’ 3b. Router-router
signalling protocol
IGMP
PIM
Router-Router Signalling: PIM
• Protocol Independent Multicast

• Used by a router to notify an upstream router that it wishes to receive (or stop
receiving) multicast traffic for a given group (G).
• 3 main classifications of PIM
Any Source Multicast (asm-pim) – 3 “submodes”
Legacy Dense, sparse, sparse-dense Cisco Specific
Source-Specific Multicast (pim-ssm)
Bidirectional (pim-bidir) Only for specific-use cases (many senders)
Router-Router Signalling: PIM-SM
• Each PIM router forms neighbour relationship with adjacent PIM routers using
PIM “hello” messages every 30 seconds.
• When a PIM router wants to receive a multicast stream, it sends a PIM “join”
message towards the IP address of the multicast source.
• When a PIM router wants to stop receiving a multicast stream, it sends a PIM
“prune” message towards the IP address of the multicast source.
RPF Mechanism
• Multicast traffic flows are checked from the sender back down the path created
by the PIM messages. This is known as Reverse Path Forwarding (RPF).
• All received multicast traffic is subject to an RPF check
Is the incoming MC traffic being received via the interface on which I have a route to the
source?
RPF check PASS = accept MC traffic and send it on
RPF check FAIL = drop traffic on floor
• Prevents loops and duplicate packets
RPF Mechanism
1. Look up route
to Source in
routing table 10 20
Group
7. RPF check 234.1.1.1
I have hosts
that want to = PASS
5. Send MC stream back
receive
down the path created
234.1.1.1
by PIM messages
10 10
Source
2. PIM “join 234.1.1.1”

message sent towards 4. PIM “join 234.1.1.1”
source message sent towards
source
3. Look up route
6. RPF check
to Source in
= PASS
routing table
Static Multicast Routes
• Static multicast routes can be used to send PIM messages down a different path
than would be selected from the unicast routing table.
• Useful if you want MC traffic to travel over different links to unicast traffic
• Best suited for small networks due to scalability issues managing many static
routes.
• Be careful of creating PIM routing loops !
Static Multicast Routes
10.1.1.2
10 50
Group
234.1.1.1
I have hosts
that want to
receive
234.1.1.1
Source
10 PIM 10
192.168.1.1
Multicast
traffic
Static Multicast Routes 2. Look
up route
to Source
10.1.1.2 in routing
table
1. PIM “join 234.1.1.1”
message sent using
static mroute path
10
LOOP ! 50
Group
234.1.1.1
I have hosts
that want to 2. PIM “join 234.1.1.1”
receive message sent towards
234.1.1.1 source using unicast
routing table
Source
10 10
192.168.1.1
ip mroute 192.168.1.1 255.255.255.255 10.1.1.2
Static Multicast Routes 2. Look
up route
to Source
10.1.1.2 in routing
table 3. PIM “join 234.1.1.1”
1. PIM “join 234.1.1.1” message sent towards
message sent using source using unicast
static mroute path routing table
10 50
10.1.1.6 Group
Multicast 234.1.1.1
I have hosts
that want to traffic
receive
234.1.1.1
Source
10 10
192.168.1.1
ip mroute 192.168.1.1 255.255.255.255 10.1.1.6
PIM-SM: Rendezvous Point (RP)
• PIM-SM uses a router called a Rendezvous Point (RP).

• The sole purpose of the RP is to allow the last-hop router to find out the IP
address of the source for a particular group.
• The receivers don’t know the source address and don’t care - hence the term
“Any Source Multicast”.
• An RP is mandatory for PIM sparse-mode networks.
PIM-SM: Rendezvous Point (RP)
I now know the
RP src IP for
192.168.0.1 234.1.1.1
PIM “join 234.1.1.1” PIM “join 234.1.1.1”

message sent message sent
towards RP towards
Source
10 20
I finally know the
source IP for
234.1.1.1 !
PIM register-stop “234.1.1.1”

message sent FHR
Source
IGMP report for group 10 10
I want to receive 234.1.1.1 10.1.1.1
234.1.1.1
10 IGP metric
PIM-SM: Shortest Path Tree Switch over
Multicast “Shared Tree” RP
Where traffic passes via the RP 192.168.0.1
10 IGP cost = 30 20
Better IGP path

to source exists
via lower links !
Source
IGMP report for group 10 IGP cost = 20 10
I want to receive 234.1.1.1 10.1.1.1
234.1.1.1 PIM “join 234.1.1.1”
PIM “join 234.1.1.1” message sent
message sent towards
towards Source
Source
PIM-SM: Rendezvous Point Discovery
So how does the network know where the RP is ?
• Option 1: Static RP configuration
Configure ALL routers in the network with the IP address of the RP
ip pim rp-address 192.168.0.1
• Option 2: Dynamic RP configuration

Configure the RP to tell all other routers that it is the RP
• Cisco proprietary mechanism is called “Auto-RP”
• IETF standard is known as Bootstrap Router (BSR) – RFC 5059
• Option 3: Anycast RP
Receiver 2
Eth0:10.1.1.2
I also
want 234.1.1.
1 from IGMP Membership Report
source IP Requested Group: 234.1.1.1
192.168.1.1 Group Source: 192.168.1.1
Source IP: 10.1.1.2
Receiver 1
Eth0:10.1.1.1
I want
234.1.1.1
from source
IP 192.168.1.1
234.1.1.1 Source
First-hop router receives 192.168.1.1
IGMP Membership Report ALL IGMPv3 reports (no
Requested Group: 234.1.1.1 report suppression)
Group Source: 192.168.1.1
Source IP: 10.1.1.1
Non-receiver
IGMPv3
Receiver 2
Eth0:10.1.1.2
I don’t
require this
stream any IGMP
IGMP Leave
Leave message
message
more Leave
Group: 234.1.1.1
Source
Source IP:
IP: 10.1.1.2
10.1.1.2
Receiver 1 Destination
Destination IP:
IP: 224.0.0.2
224.0.0.1
E0:10.1.1.254
MC Stream
I still
need Does
234.1.1.1 anyone still
need group
234.1.1.1 ?
IGMP
IGMP Membership Report
Membership Report
IGMP Group
IGMP Membership
Group Membership
Message onthis
message on thissegment
segment Query message
Query message
Requested Group: 234.1.1.1 Membership Group: 234.1.1.1
Source IP: 10.1.1.1 Source IP:
Membership 10.1.1.254
Group: 234.1.1.1
Destination Destination IP: 224.0.0.1
Source IP: IP: 224.0.0.2
10.1.1.1 Source IP: 10.1.1.254
Destination IP: 234.1.1.1 Destination IP: 234.1.1.1
Non-receiver
IGMPv3 – Changing a Group
Source
192.168.1.2
Receiver 1
Eth0:10.1.1.1 234.1.1.2
I now want
234.1.1.2
from source
IP 192.168.1.2
234.1.1.1 Source
192.168.1.1
IGMP Change State
INCLUDE: grp 234.1.1.2, src 192.168.1.2
EXCLUDE: grp 234.1.1.1 src 192.168.1.1
Non-receiver
IGMPv3 Source Discovery
 Q: How does the receiver know the source address for each
group ?
 A: The receiver app is pre-populated with this information.
G’Day. My serial number is 1234567
G’Day 1234567. Please download channel list file CL-1234567.txt
GET CL-1234567.txt
Set Top Box
(STB)
234.1.1.1 192.168.1.1 STB
234.1.1.2 192.168.1.2 Management
234.1.1.3 192.168.1.2 Server
234.1.1.4 192.168.1.1
CL-1234567.txt
Advantages of IGMPv3
• Hosts can join one group and leave another in the same transaction.
IGMPv2 requires separate report/leave messages.
• Reduces the likelyhood of multicast group being spoofed by a rogue
source.
• Eliminates overlapping multicast addresses.
• First-hop router immediately knows the source address, so no need for
Rendezvous Point – can use PIM-SSM.
Router-Router Signalling: PIM-SSM
• SSM = Source Specific Multicast

• PIM-SSM requires the first-hop router to know the address of the MC
source for each group
• PIM-SSM is usually deployed in conjunction with IGMPv3, where the
receiver indicates the source address in the IGMPv3 report packet
• The last-hop router sends a PIM join directly towards the sender using
the unicast routing table. There is no “Shared Tree” via an RP as in PIM-
SM.
PIM-SSM: Operation
Source
192.168.1.2
I want
I want to to receive
receive Group
234.1.1.2 from
232.1.1.2 from 234.1.1.2
192.168.1.2
192.168.1.2
PIM “join 232.1.1.2”
192.168.1.2
232.1.1.2, source Group
Group
192.168.1.2 232.1.1.1
234.1.1.1
Source
I want to receive IGMP report for group 10 10 192.168.1.1
I234.1.1.1
want to receive
from 232.1.1.1, source PIM “join 232.1.1.1”
232.1.1.1
192.168.1.1from
192.168.1.1
192.168.1.1 message sent towards PIM “join 232.1.1.1”
192.168.1.1 message sent towards
192.168.1.1
PIM-SSM Advantages
• Easy to configure and maintain

• No RPs
• No Multicast Source Discovery Protocol (MSDP) between
redundant RPs
• Efficient network usage
• Traffic is not routed temporarily via the RP
• Most direct path from source to receiver is always used
• Enhanced security
• Spoofing of MC stream is more difficult
PIM-SSM Mapping
 The ideal SSM architecture uses IGMPv3 for host-router signalling and
PIM-SSM for router-router signalling
 But...IGMPv3 host support is patchy, whereas IGMPv2 is ubiquitous
Q: Is there a way to use PIM-SSM in the network when I
have hosts that only support IGMPv2 ?
A: Yes – its called PIM-SSM mapping
 PIM-SSM mapping can be used as an interim measure until IGMPv3 is
supported on all hosts
PIM-SSM Static Mapping
Source
192.168.1.2
I want
receive Group
234.1.1.2 from
232.1.1.2 from 234.1.1.2
192.168.1.2
192.168.1.2
PIM “join 232.1.1.2”
192.168.1.2
232.1.1.2 Group
Group
232.1.1.1
234.1.1.1
Source
I234.1.1.1
want to receive
from 232.1.1.1
232.1.1.1
192.168.1.1from
192.168.1.1 PIM “join 232.1.1.1” PIM “join 232.1.1.1”
message sent towards message sent towards
Static ssm-map configured on 192.168.1.1 192.168.1.1
first-hop router
Group Source
232.1.1.1 192.168.1.1
232.1.1.2 192.168.1.2
PIM-SSM Static Mapping
Zone File: 1.1.232.ssm.our.net
Source
192.168.1.2 1 IN A 192.168.1.1
2 IN A 192.168.1.2
I want
receive Group
234.1.1.2 from
232.1.1.2 from 234.1.1.2
192.168.1.2
192.168.1.2
PIM “join 232.1.1.2” DNS
192.168.1.2 192.168.10.1
232.1.1.2, source Group
Group
192.168.1.2 232.1.1.1
234.1.1.1
Source
I234.1.1.1
want to receive
from 232.1.1.1, source
232.1.1.1
192.168.1.1from
192.168.1.1 PIM “join 232.1.1.1” PIM “join 232.1.1.1”
192.168.1.1
message sent towards message sent towards
192.168.1.1 192.168.1.1
Query DNS server 192.168.10.1 for group source
IPv4 vs. IPv6 Multicast
A Quick Qlimpse
IP Service IPv4 Solution IPv6 Solution
Address Range 32-Bit, Class D 128-Bit (112-Bit Group)
Protocol-Independent
Protocol-Independent
Routing All IGPs and BGPv4+
All IGPs and BGPv4+
with IPv6 Mcast SAFI
PIM-DM, PIM-SM:
Forwarding PIM-SM: ASM, SSM, BiDir
ASM, SSM, BiDir
Group Multicast Listener
IGMPv1, v2, v3
Management Discovery MLDv1, v2
Domain Control Boundary/Border Scope Identifier
MSDP Across
Interdomain Source Single RP Within Globally
Independent PIM
Discovery Shared Domains
Domains
Case Study – Multicast Deployment
Case Study - Background
• Company has 1 head office with 200 staff, 1 branch office with 10 staff and
occasional home users
• Management wants to deploy an in-house, always-on video channel that staff
may watch at any time for the latest product releases and Company news
• Important events will require all users to watch the channel at the same time
• The video bitrate is 2 Mbps
Case Study – Network Topology
Head Office Branch Office
192.168.3.2
100 Media 10
PCs Server PCs
2Mbps
Router A Router C
MAN/WAN
P P P
I 10Mbps
Switch A P P Router E Switch E
LAN
1Gbps
P P
P P P
I
Switch B Router B Router D
100 PCs
Home Office
xDSL
8Mbps
Internet 1 PC
I Router F
Case Study – Unicast Bandwidth requirement
192.168.3.2
100 Media 10
PCs Server PCs
20
422 Mbps
200 Router A Mbps
Mbps Router C
MAN/WAN
P P P
I 10Mbps
LAN
1Gbps
200
Mbps P P
P P P
I
100 PCs
Home Office
xDSL
8Mbps
Internet 1 PC
211 Concurrent
I 2 Mbps
Router F
Streams = 422Mbps
Case Study – Multicast Bandwidth requirement
192.168.3.2
100 Media 10
PCs Server PCs
2
2
Mbps
2 Router A Mbps
Router C
Mbps MAN/WAN
P P P
I 10Mbps
LAN
1Gbps
2 P
P
Mbps
P P P
I
100 PCs
Home Office
xDSL
8Mbps
Internet 1 PC
I Router F
2 Mbps
Case Study – Network Support for MC
• Cisco IOS provides broad platform support for PIM (all variants) and IGMPv1/2/3
• Check with WAN provider for MC support
Dark fibre, EoSDH, EoMPLS, Frame relay, ATM, SDH/SONET, leased-line services –
usually no issues
Managed Ethernet, L3VPN, VPLS – check with provider.
SP network generally needs to be configured for MC support
• No native support for multicast across the Internet
• No native IPSec support for multicast
Case Study – Design Options
• Option 1: Any Source Multicast (ASM) design

Hosts run IGMPv2
Network runs PIM-SM with RP
• Option 2: Source Specific Multicast (SSM) design
Hosts run IGMPv3
Network runs PIM-SSM
• Option 3: SSM design with IGMP mapping
Hosts run IGMPv2
Network runs PIM-SSM with source address mapping
Case Study – ASM
 Step 1: Configure IGMP snooping on access switches
• IGMP snooping enabled by default on Cisco devices
• Configure
“ip igmp snooping vlan <x> immediate-leave” for vlans with directly
attached hosts only.
Switch_A#sh ip igmp snooping vlan 10
Vlan 10:
--------
IGMP snooping : Enabled
IGMPv2 immediate leave : Enabled
Multicast router learning mode : pim-dvmrp
CGMP interoperability mode : IGMP_ONLY
Robustness variable : 2
Last member query count : 2
Last member query interval : 1000
Switch_A#
Case Study – ASM
 Step 2: Configure all routers for multicast
• Globally enable multicast routing:
Router_A(config)#ip multicast-routing
Router_A(config)#do show ip multicast global
Multicast Routing: enabled
Multicast Multipath: disabled
Multicast Route limit: No limit
Multicast Triggered RPF check: enabled
Multicast Fallback group mode: Sparse
Router_A(config)#
• Configure PIM on all internal router interfaces:
Router_A(config-if)#int fast 0/3

Router_A(config-if)#ip pim sparse-mode
Router_A(config-if)#
Case Study – ASM
 Step 3: Configure all internal links for PIM-SM, IGMPv2
192.168.3.2
100 Media 10
PCs Server PCs
Router A I P Router C
P MAN/WAN I
PI P PP P P P
I 10Mbps
PP P
P Router E Switch E
Switch A
LAN
1Gbps
P PP
P P PIM not
PI P
P P P configured on
I
Switch B Router B
external
100 PCs interfaces
Router D
Home Office
xDSL
PI
8Mbps
I IGMPv2 P PIM Sparse Mode Internet 1 PC
I Router F
Case Study – ASM
 Step 4: Verify PIM neighbours
Router_A#sh ip pim neighbor
PIM Neighbor Table
Neighbor Interface Uptime/Expires Ver DR
Address Prio/Mode
10.0.0.5 FastEthernet0/3 1d02h/00:01:17 v2 1 / DR S
10.0.0.3 FastEthernet0/2 1d01h/00:01:31 v2 1 / DR
Router_A#
• Note: when PIM is enabled on an interface, IGMPv2 is also automatically

enabled on that interface.
Case Study – ASM
 Step 5: Select RP router
• RP should be in a central location between sender and receivers.
• CPU grunt not critical as RP processing overhead is low.
• Select a router that has high network availability.
• Ensure the RP has a /32 loopback address as the source.
• Recommended to assign loopback address dedicated for RP use only (not used
for router ID etc).
Case Study – ASM
 Step 5: Select RP router
192.168.3.2
100 Media
Server 10
PCs PCs
234.1.1.1
Router A Router C
MAN/WAN
10Mbps
Switch A P Router E Switch E
LAN
1Gbps
P
Rendezvous
P
P P Point
Switch B Router B
Lo4: 4.4.4.4
100 PCs
Router D
Home Office
xDSL
8Mbps
Internet 1 PC
I Router F
Case Study – ASM
 Step 6: Configure static RP on all routers (including the RP)
ip access-list standard MC_Group_1
permit 234.1.1.0 0.0.0.255
Router_C#conf t
Enter configuration commands, one per line. End with CNTL/Z.
Router_C(config)#ip pim rp-address 4.4.4.4 MC_Group_1
Step 7: Verify RP to Group mappings

Router_C#sh ip pim rp mapping
PIM Group-to-RP Mappings

Acl: MC_Group_1, Static
RP: 4.4.4.4 (Router_D)
Router_C#
Case Study – ASM
 Step 8: Enable multicast over non-multicast networks
• Use GRE, L2TPv3 to tunnel MC over non-MC networks
• Need a static mroute for both the RP address and the MC source address for
RPF check to pass.
• http://www.cisco.com/c/en/us/support/docs/ip/ip-multicast/43584-mcast-over-
gre.html
Case Study – ASM
192.168.3.2 Router_F
!
Media interface Tunnel1
Server
description GRE tunnel to Router_D
ip address 10.0.0.14 255.255.255.252
ip pim sparse-mode
Router C tunnel source 192.0.2.2
tunnel destination 10.1.1.4
end
Router_D RP Address
! ip mroute 4.4.4.4 255.255.255.255 Tunnel1
interface Tunnel1 Lo4: 4.4.4.4 Router D
Lo0:10.1.1.4
ip mroute 192.168.3.2 255.255.255.255 Tunnel1
description GRE tunnel to Router_F P
ip address 10.0.0.13 255.255.255.252
ip pim sparse-mode P
tunnel source 10.1.1.4 192.0.2.1 10.0.0.13
Router D
end Home Office
10.0.0.14
Internet GRE
1 PC
192.0.2.2
Router F
I BRKIPM-1261 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 74
Case Study – ASM – IGMP Verification
Head Office
192.168.3.2
Media
Server
192.168.1.2 IGMP
Report 234.1.1.1 @ 2Mbps
Router A Router C
Fa0/2 Fa0/6
10.0.0.2 10.0.0.3
Fa0/12
192.168.1.1 Fa0/3
10.0.0.4
Fa0/2
Router_A#show
Router_A#sh ip igmp
ip igmp membership
membership 10.0.0.5
Flags: A - aggregate, T - tracked
Channel/Group-Flags:
L - Local, S - static, V - virtual, R - Reported through v3
I /- -v3lite,
Filtering
U -entry
Urd, (Exclude mode (S,G),
M - SSM (S,G) channel Include mode (*,G))
Router B Router D
Lo4: 4.4.4.4
1,2,3 - The version of IGMP the group is in
Channel/Group
<snip> Reporter Uptime Exp. Flags Interface
/*,234.1.1.1
Channel/Group 192.168.1.2
Reporter 00:43:29
Uptime stop 3MA
Exp. Flags Fa0/12
Interface
192.168.3.2,234.1.1.1
*,234.1.1.1 192.168.1.2 00:43:29 02:03 RA
00:00:12 02:47 2A Fa0/12
Fa0/12
Router_A#
Router_A#
Case Study – ASM – Mroute Verification
Head Office
192.168.3.2
Media
Router_A#show ip mroute active Server
Active IP Multicast Sources - sending >= 4 kbps 192.168.1.2 IGMP
Group: 234.1.1.1, (Stream_1) Router A
Fa0/2 Fa0/6 Router C
Source: 192.168.3.2 (Media_Server) 10.0.0.2 10.0.0.3
Rate: 245 pps/1967 kbps(1sec), 1968 kbps(last 20 secs), Fa0/12
1966 kbps(life avg) 192.168.1.1 Fa0/3
Router_A# 10.0.0.4
Router_A#show ip mroute Fa0/2

IP Multicast Routing Table 10.0.0.5
<snip>
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode Router B Router D
Lo4: 4.4.4.4
(*, 234.1.1.1), 00:08:40/stopped, RP 4.4.4.4, flags: SJC
Incoming interface: FastEthernet0/3, RPF nbr 10.0.0.5
Outgoing interface list:
FastEthernet0/12, Forward/Sparse, 00:08:40/00:02:11 How Router_A receives MC traffic
via the RP (src IP unknown)
(192.168.3.2, 234.1.1.1), 00:08:40/00:02:56, flags: JT
Outgoing interface list: How Router_A receives MC traffic
FastEthernet0/12, Forward/Sparse, 00:08:40/00:02:11 directly from the source (src IP
known)

Hosts run IGMPv2
Network runs PIM-SM

Hosts run IGMPv3
Hosts run IGMPv2
Case Study – SSM
192.168.3.2
100 Media 10
PCs Server PCs
234.1.1.1
Router A Router C
MAN/WAN
10Mbps
Switch A P Router E Switch E
LAN
1Gbps
P P
P P
Switch B Router B
100 PCs
Router D
Home Office
xDSL
8Mbps
Internet 1 PC
I Router F
Case Study – SSM
 Step 1: Configure all routers for SSM
Globally enable multicast routing:
Router_A(config)#ip multicast-routing
• Configure PIM-SSM ranges:

! Define ACL for SSM ranges (default is 232.0.0.0/8)
Router_A(config)#ip access-list standard SSM-Groups

Router_A(config-std-nacl)#permit 234.0.0.0 0.255.255.255
! Configure SSM range
Router_A(config-std-nacl)#ip pim ssm range SSM-Groups

Router_A(config)#
Case Study – SSM
 Step 2: Configure IGMP
• IGMPv3 snooping enabled by default on Cisco devices
• Need to explicitly configure IGMPv3 on router interface that connects to LAN
Router_A(config)#int fast 0/12 Router_A#sh ip igmp interface fast 0/12

Router_A(config-if)#ip igmp version 3 FastEthernet0/12 is up, line protocol is up
Router_A(config-if)# Internet address is 192.168.1.1/24
IGMP is enabled on interface
Current IGMP host version is 3
Current IGMP router version is 3
IGMP query interval is 60 seconds
IGMP querier timeout is 120 seconds
<snip>
Router_A#
Case Study – ASM
 Step 3: Configure all internal links for PIM-SM
192.168.3.2
100 Media 10
PCs Server PCs
P MAN/WAN I
PI P PP P P P
I 10Mbps
PP P
P Router E Switch E
Switch A
LAN
1Gbps
P PP
P P PIM not
PI P
P P P configured on
I
Switch B Router B
external
100 PCs interfaces
Router D
Home Office
xDSL
PI
8Mbps
I IGMPv3 P PIM Sparse Mode Internet 1 PC
I Router F
Case Study – ASM
192.168.3.2
Router_F
Media !
Server interface Tunnel1
description GRE tunnel to Router_D
ip address 10.0.0.14 255.255.255.252
Router C ip pim sparse-mode
tunnel source 192.0.2.2
end
ip mroute 192.168.3.2 255.255.255.255 Tunnel1

Router_D
!
interface Tunnel1 P
description GRE tunnel to Router_F P
ip address 10.0.0.13 255.255.255.252
ip pim sparse-mode 192.0.2.1 10.0.0.13
tunnel source 10.1.1.4 Router D
tunnel destination 192.0.2.2 Home Office
end
10.0.0.14
Internet GRE
1 PC
192.0.2.2
Router F
I BRKIPM-1261 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 82
Case Study – SSM – IGMP Verification
Head Office
192.168.3.2
Media
Server
192.168.1.2 IGMP
Report 234.1.1.1
Router A Router C
Fa0/2 Fa0/6
10.0.0.2 10.0.0.3
Fa0/12
192.168.1.1 Fa0/3
10.0.0.4
Fa0/2
Router_A#show ip igmp membership 10.0.0.5
Channel/Group-Flags:
/ - Filtering entry (Exclude mode (S,G), Include mode (*,G)) Router D
Router B
Lo4: 4.4.4.4
Channel/Group Reporter Uptime Exp. Flags Interface
/*,234.1.1.1 192.168.1.2 00:43:29 stop 3MA Fa0/12
192.168.3.2,234.1.1.1 00:43:29 02:03 RA Fa0/12
Router_A#
Case Study – SSM – Mroute Verification
Head Office
192.168.3.2
Router_A#show ip mroute active Media

Active IP Multicast Sources - sending >= 4 kbps Server
192.168.1.2 IGMP
Group: 234.1.1.1, (Stream_1) Report 234.1.1.1
Source: 192.168.3.2 (Media_Server) Router A
Fa0/2 Router C
Fa0/6
Rate: 245 pps/1967 kbps(1sec), 1968 kbps(last 20 secs), 10.0.0.2 10.0.0.3
1966 kbps(life avg)
Fa0/12
Router_A# 192.168.1.1 Fa0/3
10.0.0.4
Router_A#show ip mroute
Fa0/2
IP Multicast Routing Table
10.0.0.5
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group
T - SPT-bit set, J - Join SPT, M - MSDP created entry,
U - URD, I - Received Source Specific Host Report,
Router B Router D
Interface state: Interface, Next-Hop or VCD, State/Mode
(192.168.3.2, 234.1.1.1), 00:59:25/00:02:51, flags: sTI Note there is only (S,G) entry
Incoming interface: FastEthernet0/2, RPF nbr 10.0.0.3 and no (*,G) as no RP is present
FastEthernet0/12, Forward/Sparse, 00:59:01/00:02:05

Hosts run IGMPv2
Network runs PIM-SM

Hosts run IGMPv3
Hosts run IGMPv2
Case Study – IGMPv2 + PIM-SSM
• Step 1: Configure IGMPv2 snooping on access switches

• Step 2: Configure all routers for multicast-routing
• Step 3: Enable PIM-SM (even though we are using SSM)
on all internal interfaces)
 Step 4: Configure all routers for SSM
• Configure PIM-SSM ranges:
! Define ACL for SSM ranges (default is 232.0.0.0/8)
Router_A(config)#ip access-list standard SSM-Groups

Router_A(config-std-nacl)#permit 234.0.0.0 0.255.255.255
! Configure SSM range
Router_A(config-std-nacl)#ip pim ssm range SSM-Groups

Router_A(config)#
 Step 5a: Configure static IGMP SSM mapping
• Globally enable IGMP mapping
Router_A(config)#ip igmp ssm-map enable
• Configure static group-to-source mapping usingACL:

Router_A(config)#no ip igmp ssm-map query dns
Router_A(config)#access-list 10 permit host 234.1.1.1
Router_A(config)#ip igmp ssm-map static 10 192.168.3.2
“When I see an IGMPv2 report for

groups defined in ACL 10, assign
the source address 192.168.3.2”
 Step 5b: Configure dynamic IGMP SSM mapping
• Globally enable IGMP mapping
Router_A(config)#ip igmp ssm-map enable
• Configure dynamic group-to-source mapping using DNS:

Router_A(config)#ip igmp ssm-map query dns
Router_A(config)#ip name-server 192.168.3.10
“When I see an IGMPv2 report for

any group, perform a reverse DNS
lookup to obtain the source
address”
 Step 5b: Configure all internal links for PIM-SM

192.168.3.2
100 Media 10
PCs Server PCs
P M MAN/WAN M I
PI P PP P P P
I 10Mbps
PP P
P Router E Switch E
Switch A
LAN
1Gbps
P PP
P P
P
I I M PP P P
Switch B Router B
100 PCs
Router D
Home Office
I IGMPv2 P PIM Sparse Mode xDSL
PI
8Mbps
M IGMP SSM Mapping Internet
M 1 PC
I Router F
Case Study – SSM Mapping Verification
 Step 5: Verify IGMP mapping
• Static mapping
Router_A#sh ip igmp ssm-mapping 234.1.1.1
Group address: 234.1.1.1
Database : Static
Source list : 192.168.3.2
Router_A#
• Dynamic mapping
Router_A#sh ip igmp ssm-mapping 234.1.1.1

Group address: 234.1.1.1
Database : DNS
DNS name : 1.1.1.234.in-addr.arpa
Expire time : 860000
Source list : 192.168.3.2
Router_A#
Case Study – SSM Mapping – Verification
Head Office
192.168.3.2
Router_A#show ip mroute active Media

Server
Active IP Multicast Sources - sending >= 4 kbps
192.168.1.2 IGMPv2
Group: 234.1.1.1, (Stream_1) Router A
Fa0/2 Fa0/6 Router C
Source: 192.168.3.2 (Media_Server)
10.0.0.2 10.0.0.3
Rate: 245 pps/1968 kbps(1sec), 1968 kbps(last 20 secs),
1967 kbps(life avg) Fa0/12
192.168.1.1 Fa0/3
Router_A#
10.0.0.4
Fa0/2
10.0.0.5
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group
T - SPT-bit set, J - Join SPT, M - MSDP created entry,
U - URD, I - Received Source Specific Host Report,
Router B Router D
(192.168.3.2, 234.1.1.1), 01:23:13/00:02:29, flags: sTI

Incoming interface: FastEthernet0/2, RPF nbr 10.0.0.3 IGMP ssm-mapping not evident in
Outgoing interface list: output
Troubleshooting
93
Mimicking a Multicast Source
• Use video streaming software on a PC such as VLC:

vlc --repeat filename.avi --sout '#standard{access=udp,mux=ts,dst=234.1.1.1:1234}
MC_Source#ping
• Use a ping flood or Protocol [ip]:
Target IP address: 234.1.1.1
traffic generator to Repeat count [1]: 100000000000
fake it.... Datagram size [100]: 1300
Timeout in seconds [2]: 0
Extended commands [n]: y
Interface [All]: FastEthernet1/0/24
Source address: 192.168.3.2
Type escape sequence to abort.
Sending 1215752192, 1300-byte ICMP Echos to 234.1.1.1,
timeout is 0 seconds:
Packet sent with a source address of 192.168.3.2
...................................................
Mimicking a Multicast Receiver
• PC running VLC to join MC group

vlc udp:@234.1.1.1 (IGMPv2 report)
or
vlc udp:192.168.3.2@234.1.1.1 (IGMPv3 report)
• Router joins MC group as if it were a receiver

! Send IGMPv2 report for 234.1.1.1
Router(config-if)#ip igmp version 2
Router(config-if)#ip igmp join-group 234.1.1.1
or
! Send IGMPv3 report for 234.1.1.1, source

192.168.3.2 Router(config-if)#ip igmp version 3
Router(config-if)#ip igmp join-group 234.1.1.1 source 192.168.3.2
Mimicking a Multicast Receiver
• Statically join a router interface to a group
Router(config-if)#ip igmp static-group 234.1.1.1
Router(config-if)#ip igmp static-group 234.1.1.1 source 192.168.3.2

Media
Router(config-if)#ip igmp static-group 234.1.1.1 ssm-map Server
192.168.3.2
234.1.1.1 @ 2Mbps
Router A Router C
PIM JOIN
Receivers are not required. Fa0/12

Just send the MC stream 192.168.1.1
onto the LAN regardless. PIM JOIN
Common Causes of Multicast Problems
• Source problem
Is the source sending the MC stream properly ?
• Receiver issue
Is the client asking to receive the stream ?
• Underlying network issue
Is the underlying network OK ?
• MC network misconfiguration
Is the network configured correctly ?
Source Not Sending Stream Correctly
• Verify source is actually sending MC stream

 tcpdump, Wireshark, SNMP
• Verify reachability from source to FHR
• Check first-hop router is receiving MC at correct bit-rate
 compare current rate to baseline and historical rate
Router_C#sh ip mroute active

Active IP Multicast Sources - sending >= 4 kbps
Group: 234.1.1.1, (Stream_1)

Source: 192.168.3.2 (Media_Server)
Rate: 165 pps/1324 kbps(1sec), 1964 kbps(last 30 secs), 1963 kbps(life
avg) Router_C#
Source – Low TTL value
• Incorrect source TTL can cause MC stream to be dropped
<snip>
(192.168.3.2, 234.1.1.1), 1d18h/00:02:35, flags: sTI
FastEthernet0/12, Forward/Sparse, 1d18h/00:02:35
Media
Router_A#show ip mroute active Server
Stream stops at first-hop
Active IP Multicast Sources - sending >= 4 kbps 192.168.3.2 router (TTL=1) or part-way
Router_A# into the network (TTL >1)
234.1.1.1
@ 2Mbps
Router A Router C
mroute is accurate Fa0/12

but no active streams 192.168.1.1
Router_C#sh ip traffic | i bad hop count

0 format errors, 0 checksum errors, 193949 bad hop count
Router_C#sh ip traffic | i bad hop count
0 format errors, 0 checksum errors, 194069 bad hop count
Router_C#
Receiver Issue
• Use “debug ip igmp” to verify IGMP reports are being received

on last hop router.
IGMP(0): Received v2 Report on FastEthernet0/12 from 192.168.1.2 for 234.1.1.1

IGMP(0): Received Group record for group 234.1.1.2, mode 2 from 192.168.1.2 for 0 sources
IGMP(0): WAVL Insert group: 234.1.1.1 interface: FastEthernet0/12 Successful
IGMP(0): MRT Add/Update FastEthernet0/12 for (*,234.1.1.1)
• If not seeing reports come in, then use packet sniffer on receiver.
Multicast Network Misconfiguration
• Verify
 All multicast links have PIM sparse mode configure
 RP is configured / learned on all routers (including
the RP itself)
Router_F#sh ip mroute
IP Multicast Routing Table Missing RP configuration
<snip>

Incoming interface: Null, RPF nbr 0.0.0.0
• Verify
• Network and hosts are running same IGMP version
• Verify RPF check passes. ‘sh ip mroute count | inc RPF failed|Other
Router_F#sh ip mroute
<snip>
Incoming interface: Tunnel1, RPF nbr 10.0.0.13, Mroute
RPF Check OK
(192.168.3.2, 234.1.1.1), 00:04:40/00:02:33, flags: J

Incoming interface: Null, RPF nbr 0.0.0.0, Mroute
Outgoing interface list: RPF Check Failure
FastEthernet0/1, Forward/Sparse, 00:04:40/00:01:19 (should never be 0.0.0.0
Router_F#
• Verify
 LHR has igmpv3 enabled on the link connecting to receiver if that SSM is used
 SSM range / SSM mapping is configured properly on LHR
Underlying Network Issue
• The cause of most multicast problems is not multicast (!)
Q: Why might users report a general network issue as a

multicast problem ?
A: Small amounts of packet loss, excessive latency or jitter,
routing reconvergence are immediately evident to streaming
audio/video users.
Underlying Network Issue
• Verify network reachability from Source to FHR, LHR to RP, RP to
FHR, LHR to FHR
• PIM RFP neighbour status
• Check interface errors
• ACL, Rate limiting
Summary – What have we learnt?
• IPv4 Multicast & Addressing

• Internet Group Management Protocol (IGMP) version 2 and 3
• IGMP Snooping
• Multicast Distribution Tree (Source & Shared)
• Protocol Independent Multicast (PIM)
 Any-Source Multicast (ASM) - PIM Sparse Mode (PIM-SM), Rendezvous Point
(RP)
 Source-Specific Multicast (SSM)
• Case Study
• Troubleshooting
Where to go from here.....
• Rendezvous Point Auto-discovery

• High availability
 Source Redundancy
 RP Redundancy
 Fast convergence
• Multicast Security
• Inter-Domain Multicast
• IPv6 Multicast
Additional Resources
• Cisco Live Virtual Breakout Sessions
 IPv6 from Introduction to Intermediate in 90 Minutes [BRKRST-2116]
 Building Data Centre Networks with VXLAN BGP-EVPN [BRKDCN-3378]
 CCIE R&S - Multicast Technologies Lab [LABCCIE-2016]
 Implementing Multicast Routing in Enterprise Network [LABIPM-1011]
• CCO documentation: http://www.cisco.com/go/multicast
Q&A
Complete Your Online
Session Evaluation
• Give us your feedback and
receive a Cisco Live 2018 Cap
by completing the overall event
evaluation and 5 session
evaluations.
• All evaluations can be completed
via the Cisco Live Mobile App.
Don’t forget: Cisco Live sessions will be
available for viewing on demand after the
event at www.CiscoLive.com/Global.
© 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public
Thank you

Brkipm 1261 PDF

Uploaded by

Copyright:

Available Formats

Brkipm 1261 PDF

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

Brkipm 1261 PDF

Uploaded by

Copyright:

Available Formats

Party Time

Kyd Cao Customer Support Engineer

• Out of order delivery

• IGMP – Internet Group Management Protocol • LHR - Last Hop Router

• ASM – Any source Multicast

5. Router already receiving stream

2b. Host-router 1. Source already sending

6. Router now receiving stream ‘A’

Members Layer 2 Network Layer 3 Network Source

1. Source already sending

Members Layer 2 Network Layer 3 Network Source

Identification Flags Fragment Offset

Time to Live Protocol Header Checksum

• Other IANA reserved addresses

• SSM (Source Specific Multicast) range

• Layer 2 Multicast Address

Members Layer 2 Network Layer 3 Network Source

• Internet Group Management Protocol

IGMP Membership Report Receiver 2

T+3s: No response to Group

IGMP Leave message

T+2s: No response to Group

• Hosts only receive MC traffic that they request

Q. When would IGMP snooping fast-leave be a bad idea ?

• Sources only transmit to RP

Members Layer 2 Network Layer 3 Network Source

• Protocol Independent Multicast

2. PIM “join 234.1.1.1”

• PIM-SM uses a router called a Rendezvous Point (RP).

PIM “join 234.1.1.1” PIM “join 234.1.1.1”

PIM register-stop “234.1.1.1”

Better IGP path

• Option 2: Dynamic RP configuration

G’Day. My serial number is 1234567

G’Day 1234567. Please download channel list file CL-1234567.txt

• SSM = Source Specific Multicast

• Easy to configure and maintain

• Option 1: Any Source Multicast (ASM) design

• Configure PIM on all internal router interfaces:

Router_A(config-if)#int fast 0/3

• Note: when PIM is enabled on an interface, IGMPv2 is also automatically

Router_C(config)#ip pim rp-address 4.4.4.4 MC_Group_1

Step 7: Verify RP to Group mappings

PIM Group-to-RP Mappings

Router_A#show ip mroute Fa0/2

• Option 1: Any Source Multicast (ASM) design

• Option 2: Source Specific Multicast (SSM) design

• Configure PIM-SSM ranges:

Router_A(config)#ip access-list standard SSM-Groups

! Configure SSM range

Router_A(config-std-nacl)#ip pim ssm range SSM-Groups

Router_A(config)#int fast 0/12 Router_A#sh ip igmp interface fast 0/12

ip mroute 192.168.3.2 255.255.255.255 Tunnel1

Router_A#show ip mroute active Media

• Option 1: Any Source Multicast (ASM) design

• Option 2: Source Specific Multicast (SSM) design

• Step 1: Configure IGMPv2 snooping on access switches

! Define ACL for SSM ranges (default is 232.0.0.0/8)

Router_A(config)#ip access-list standard SSM-Groups