Deploying IP Multicast

Session RST-2261

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 1
 Geekometer

Agenda

• Basic Multicast Engineering

– Which Mode: ASM, SSM, Bidir?
– PIM Configuration Steps
– RP Engineering
– QoS Notes
• Advanced Multicast Engineering
– Addressing for Admin. Scoped Zones
– Scoping Using Auto-RP, Listener, and
Boundaries
– Load Balance via RP
– SSM Mapping

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 2
 Basic
Multicast Engineering

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 3
 Which Mode: ASM, SSM, Bidir?

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 4
 PIM Sparse Mode Categories

• Any Source Multicast (ASM)

– Original (Classic) PIM-SM
– Supports both Shared and Source Trees
• Single Source Multicast (SSM)
aka Source Specific Multicast
– Supports only Source Trees
•No need for RP’s, RP Failover, etc.
• Bidirectional PIM (Bidir)
– Supports only Shared Trees

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 5
 Any Source Multicast (ASM)

• Classic (original) PIMv2 Sparse Mode

– Defined in RFC 2362
• Requires a Rendezvous Point (RP)
– RP and Shared Tree used for Source Discovery
– Need some form of RP Failover mechanism
– Shared to Source Tree switchover complexities
• General Purpose Multicast
– Generally works well for most limited multicast
applications.

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 6
 Source-Specific Multicast (SSM)
• Well suited for One-to-Many Model.
– Examples: IPTV, Stock Tickers
• Hosts responsible for learning (S,G) information.
– Host uses IGMPv3 to join specific (S,G) instead of (*,G).
• Last-hop router sends (S,G) join toward source
– No RPs or Shared Trees.
• Eliminates possibility of Capt. Midnight Content Jammers.
• Only specified (S,G) flow is delivered to host.
• Eliminates need for MSDP.
• Simplifies address allocation.
– Different content sources can use same group without fear
of interfering with each other.
RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 7
 SSM Example

Source Host learns of source, group/port

Last-hop learns of source, group/port
Last-hop send PIM (S,G) Join

A B C D
Out-of-band
PIM (S, G) Join source directory,
example: web server

IGMPv3 (S, G) Join E F

Receiver 1

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 8
 SSM Example

Source Result: Shortest path tree rooted

at the source, with no shared tree.

A B C D
Out-of-band
source directory,
example: web server

E F

Receiver 1

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 9
 SSM – Summary
• Uses Source Trees only.
– Hosts are responsible for source & group discovery.
– Hosts must use IGMPv3 to signal which (S,G) to join.
• Solves multicast address allocation problems.
– Flows differentiated by both source and group.
– Content providers can use same group ranges.
• Since each (S,G) flow is unique.
• Helps prevent certain DoS attacks
– “Bogus” source traffic:
• Can’t consume network bandwidth.
• Not received by host application.

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 10
 So where is SSM?

• Dependant on IGMPv3
– Microsoft supports IGMPv3 in Windows XP
natively
– Many IPTV STB’s are adding support.
• Workaround
– Static Source Mapping
•Router maps IGMPv2 Joins in SSM range to well-
known sources via DNS or static configuration

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 11
 SSM Mapping

• Allows only for one, or more, sources per

Group
• Router maps group to source (sources)
– Uses either DNS or static internal database
•DNS method allows content providers to provide the
mapping
•DNS Method independent from network operators

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 12
 SSM Mapping – DNS Example

DNS Record Format:

3.2.1.232 IN A 172.23.20.70

Reverse DNS
lookup for
PIM (S,G) join group G

PIM (S,G) join

DNS response:
IGMPv2 join Group G -> Source S

Set Top
Box (STB)
RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 13
 Bidirectional (Bidir) PIM

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 14
 Bidirectional PIM (Bidir)
• Many-to-Any State problem.
– Large number of sources creates huge (S,G) state problem.
• Bidir PIM:
– Use a bidirectional Shared Tree to deliver traffic from
sources to the RP and all other receivers.
• Benefits:
– Data and Control Planes decoupled
– Less state in routers
• Only (*, G) state is used. (No Source Trees.)
• Source traffic follows the Shared Tree.
» Flows up the Shared Tree to reach the RP.
» Flows down the Shared Tree to reach all other receivers.

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 15
 Bidirectional PIM (Bidir)

• Bidirectional Shared-Trees
– Contrary to SM (*,G) RPF rules
•Traffic often accepted on outgoing interfaces.
•Care must be taken to avoid multicast loops
– Requires a Designated Forwarder (DF)
•Election based on the routing metric to the RP
•1 DF per RP per vlan
•Responsible for forwarding traffic up Shared Tree
» DF’s will accept data on the interfaces in their OIL.
» Then send it out all other interfaces. (Including the IIF.)

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 16
 Bidir PIM – Example

RP Sender/
Receiver Receiver

Shared Tree

Receiver
RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 17
 Bidir PIM – Example

RP Sender/
Receiver Receiver

Source Traffic forwarded

bidirectionally using (*,G) state.

Shared Tree
Source Traffic
Receiver
RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 18
 Bidir PIM – Summary

• Drastically reduces network mroute state

– Eliminates ALL (S,G) state in the network
•SPT’s between sources to RP eliminated.
•Source traffic flows both up and down
Shared Tree.
– Allows Many-to-Any applications to scale.
•Permits virtually an unlimited number of sources.
• Reduces protocol complexity.
– No Source Registration.
– No SPT-Switchover.
RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 19
 Which Mode – ASM, SSM, Bidir

• Use SSM
– For One-to-Many applications
•Eliminates need for RP Engineering.
•Greatly simplifies network.
• Use Bidir
– For Many-to-Many | Few applications
•Drastically reduces total (S,G) state in network.
• Use ASM (Classic PIM-SM)
– For all other general purpose applications

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 20
 Some Generic Configuration Notes

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 21
 PIM Configuration Steps

• Enable Multicast Routing on every router

• Configure every interface for PIM
• Highly consider Anycast-RP & MSDP
• Configure the RP for ASM/Bidir Groups
– Using Auto-RP or BSR
•Configure certain routers as Candidate RP(s)
•All other routers automatically learn elected RP
– Static RP addressing
•RP address must be configured on every router

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 22
 Configure PIM on Every Interface
Classic Partial Multicast Cloud Mistake #1
src

T1/E1 line has best metric to source

no ip pim sparse-mode T1/E1 56K/64K ip pim sparse-mode

We’ll just use X

the spare 56K line
for the IP Multicast
Failure!!!!!
traffic and not No RPF interface
the T1. Network
rcvr
Engineer
RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 23
 Configure PIM on Every Router
Classic Partial Multicast Cloud Mistake #2
src

Highest next-hop IP address used for

RPF when equal cost paths exist.

RPF Failure!!!!! Multicast Disabled

Multicast Enabled
A B
.1 192.168.1.0/24 .2
X

E0

We’ll just keep

multicast traffic off C
of certain routers in E1

the network.
Network rcvr
Engineer
RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 24
 Group Mode vs. Interface Mode

• Group & Interface mode are independent.

– Interface Mode
•Determines how the interface operates when
sending/receiving multicast traffic.
– Group Mode
•Determines whether the group is Sparse or Dense.

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 25
 Group Mode

• Group mode is controlled by local RP info

– Local RP Information
•Stored in the Group-to-RP Mapping Cache
•May be statically configured or learned via
Auto-RP or BSR
– If RP info exists, Group = Sparse
– If RP info does not exist, Group = Dense
•Trivia moment; if dm-fallback is enabled there will be
a default 0.0.0.0 RP address
– Mode Changes are automatic.
•i.e. if RP info is lost, Group falls back to Dense.
RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 26
 Configuring Interface Mode
• Interface Mode Configuration Commands
– Enables multicast forwarding on the interface.
– Controls the interface’s mode of operation.
ip pim sparse-mode
•Interface mode is set to Sparse mode operation.
» Auto-RP groups can be an exception.
ip pim sparse-dense-mode
•Interface mode is determined by the Group mode.
» If Group is Dense, interface operates in Dense mode.
» If Group is Sparse, interface operates in Sparse mode.
ip pim dense-mode
•Interface mode is set to Dense mode operation.
RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 27
 IGMP “static-join” vs. “join-group”
ip igmp join-group <group-address>
– Populates IGMP cache
– Sends IGMP report
– Results in
•PIM RPT join from the DR (may not be this router)
•CPU receives data, usually a bad thing
ip igmp static-group <group-address>
– Populates IGMP cache
– Results in
•PIM RPT join ONLY IF configured on the DR
•No CPU impact, usually a good thing
RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 28
 IGMP join-group
ip igmp join-group on DR ip igmp join-group on non-DR
PIM RPT join for 239.1.1.1 PIM RPT join for 239.1.1.1

Routers A & B
RP have IGMP cache RP
with the interface’s 3
IP address as the source
3
239.1.1.1 data
packets
hit the CPU

239.1.1.1 data
4
4
packets
A B hit the CPU
A B
DR DR
1 1

2 2

IGMP report for 239.1.1.1 IGMP report for 239.1.1.1

ip igmp join-group 239.1.1.1 ip igmp join-group 239.1.1.1

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 29
 IGMP static-group
ip igmp static-group on DR ip igmp static-group on non-DR
PIM RPT join for 239.1.1.1

Only the configured

RP DR router will have
RP
IGMP cache and the
2 Source IP address is Opps . . .
0.0.0.0 This is the non-DR
It is configured and
NO CPU hit from nothing happens
the 239.1.1.1
data packets
3
A B A B
DR DR
1 1

ip igmp static-group 239.1.1.1 ip igmp static-group 239.1.1.1

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 30
 RP Engineering –
RP Configuration Methods

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 31
 RP Configuration Methods

• Anycast-RP’s
• Static
• Auto-RP
• BSR

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 32
 Anycast RP—Overview

Src Src

RP1 RP2
MSDP
X

A B
SA SA
10.1.1.1 10.1.1.1

Rec Rec Rec Rec

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 33
 Anycast RP—Overview

Src Src

RP1 RP2
X

A B
10.1.1.1 10.1.1.1

Rec Rec Rec Rec

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 34
 Static RP’s

• Hard-coded RP address
– When used, must be configured on every router
– All routers must have the same RP configuration
– RP fail-over not possible
•Exception: If Anycast RPs are used. Group can never
fall back into Dense mode.

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 35
 Static RP’s
• RP selection behavior when using static RP
– Static RPs match on the highest IP address, not longest
match of the ACL
– If a dynamically learnt Group/RP and a static RP entry
match, the dynamically learnt RP will be selected.
– If a dynamically learnt Group/RP and static RP entry(s) with
override match, the highest IP addressed static RP will be
selected.
• Easy to avoid conflicts, do not engineer overlapped
Group/RP ranges, exception being Anycast-RPs.

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 36
 Auto-RP Overview

MA MA

Announce
Announce

A B

Announce Announce Announce Announce

C D
C-RP C-RP
1.1.1.1 2.2.2.2

Announce
Announce

RP-Announcements multicast to the

Cisco Announce (224.0.1.39) group
Announce

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 37
 Auto-RP Overview

ry
ery

ove
cov

Disc
Dis
Dis Disc
cov ove
ery
MA ry MA
Dis Disc
A cov B ove
ry
ery
ery

ry
ove
cov

Disc
C D
Dis

C-RP C-RP
1.1.1.1 2.2.2.2

RP-Discoveries multicast to the

Cisco Discovery (224.0.1.40) group
Discovery
RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 38
 BSR Overview

BSR Election Process

Msg

Msg
Msg

BSR

BSR
BSR
BSR

BSR
Msg C-BSR BSR
Msg C-BSR Msg C-BSR
A BSR
Msg F
D BSR BSR
Msg Msg

Msg

Msg
Msg

BSR

BSR
BSR

B C

BSR Msgs
E
BSR Msgs Flooded Hop-by-Hop

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 39
 BSR Overview
Highest Priority C-BSR
is elected as BSR

BSR
A
D F

B C

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 40
 BSR Overview

BSR
A
D t C- F
en RP
em Ad
tis ve
ver t) (u
ni rtise
Ad icas ca
R P n st men
C- (u ) t

C-RP C-RP
B C

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 41
 BSR Overview

Msg
BSR
BSR
Msg
BSR
A BSR
D Msg F

Msg
BSR

C-RP C-RP
B C

BSR Msgs
E
BSR Msgs containing RP-set
Flooded Hop-by-Hop
RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 42
 RP Engineering –
Avoiding Dense Mode Fallback

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 43
 Avoiding DM Flooding

• Use global command

ip pim autorp listener Æ Recommended
– Added support for Auto-RP Environments.
•Modifies interface behavior.
» Forces interfaces to always use DM for Auto-RP groups.
» Use only if Auto-RP is to be used.
– Available 12.3(4)T, 12.2(28)S, 12.1(26)E
• Use with interface command.
ip pim sparse-mode Æ Recommended
•Prevents DM Flooding.
•Does not prevent DM Fallback!
Fallback
RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 44
 Avoiding DM Flooding
• Prior to “listener” in IOS 12.3(4)T, 12.2(28)S,
12.1(26)E
– Must use ip pim sparse-dense mode interface
command to support Auto-RP.
• Use RP-of-last-resort
•Assign local Loopback as RP-of-last-resort on each
router.
•Example*
ip pim rp-address <local_loopback> 10
access-list 10 deny 224.0.1.39
access-list 10 deny 224.0.1.40
access-list 10 permit any
* see Static RP slides for notes on selection of RP with Static RPs

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 45
 Avoiding DM Fallback

• New IOS global command

no ip pim dm-fallback Æ Recommended

• Totally prevents DM Fallback!!

– No DM Flooding since all state remains in SM
• Default RP Address = 0.0.0.0 [nonexistent]
– Used if all RP’s fail.
•Results in loss of Shared Tree.
•All SPT’s remain active.
• Available 12.3(4)T, 12.2(28)S (not available on 6500/7600)

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 46
 RP Engineering –
General RP Recommendations

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 47 47
 General RP Recommendations
• Use combined Anycast-RP & Auto-RP with autorp
listener:
– When rapid RP failover is critical
– When dynamic Group/RP cache required
– When Admin scoping is required
• Pros
– Fastest RP Convergence
– Most flexible and easy to maintain
• Cons
– No Group/RP cache until a MA packet is received
– Admin scoping can greatly increase complexity
– Requires use of MSDP between RP’s

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 48
 General RP Recommendations
• Use combined Anycast-RP with Static:
– When rapid RP failover is critical
– When valid Group/RP cache is critical at all times
– No requirement for dynamic Group/RP cache
• Pros
– Fastest RP Convergence method
– With override option, Group/RP cache can not be impacted
via Auto-RP or BSR
– Required when connecting to Internet
• Cons
– Manual Group/RP configuration change on routers
– Requires use of MSDP between RP’s

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 49
 General RP Recommendations

• Use Auto-RP with autorp listener

– When minimum configuration is desired and/or
– When maximum flexibility is desired
• Pros
– Most flexible method
– Easiest to maintain
• Cons
– Increased RP Failover times vs Anycast-RP
inclusive configurations
– No Group/RP cache until a MA packet is received
RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 50
 General RP Recommendations

• Use BSR:
– When dynamic Group/RP cache is required and
– When maximum interoperability is needed
• Pros
– Interoperates with all Vendors
• Cons
– Some methods greatly increase configuration
– Does not support Admin. Scoping

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 51
 QoS Notes

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 52
 QoS Notes
• IP Multicast is UDP
– Turn off WRED or minimize the window
•no congestion control
• Jitter
– Sensitive for real time streams; i.e. audio, video
• Financial data
– Data can be retransmitted however it quickly
becomes “stale”
• Requires knowledge of the traffic
– UDP Multicast needs to be in separate threshold
or queue
RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 53
 Advanced Multicast Engineering

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 54
 Admin. Scoped Zones

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 55
 Administratively-Scoped Zones Example

Australia
North
ASIAPAC
China America

East Coast
Canada
India US

Japan
West Coast
US

Core

North EMEA
Region

Eastern
Region
Internet
South Region

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 56
 Administratively-Scoped Zones Example
Level1: Campus Scope
RP
RP
Australia
North
ASIAPAC
RP China America
RP
RP
RP East Coast
Canada
India US
RP
RP
RP
RP
Japan
West Coast
RP US
RP
Core RP
RP

RP
RP North EMEA
Region

RP
EasternRP
Region
Internet
South Region

RP
RP

• Campus Scope: 239.193.x.x/16

• RP per Campus

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 57
 Administratively-Scoped Zones Example
Level2: Regional Scope
Australia
North
ASIAPAC
China America

East Coast
Canada
India US
RP
RP

Japan
West Coast
RP US
RP
Core

North EMEA
Region

Eastern
Region
Internet
South Region

RP
RP
• Regional Scope : 239.194.x.x/16
• RP per Region

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 58
 Administratively-Scoped Zones Example
Level3: Enterprise Scope
Australia
North
ASIAPAC
China America

East Coast
Canada
India US

Japan
West Coast
RP
RP US
RP
RP
Core

North EMEA
Region

Eastern
Region
Internet
South Region
• Enterprise Scope: 239.195.x.x/16
RP
RP
• Multiple Enterprise RPs
(via MSDP full mesh)

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 59
 Administratively-Scoped Zones Example
Level 4: Internet Global Scope
Australia
North
ASIAPAC
China America

East Coast
Canada
India US

Japan
West Coast
RP
RP US
RP
RP
Core

North EMEA
Region

Eastern
Region
Internet
South Region

• Global Scope: 224.0.[2-255].x – 238.255.255.255 RP

RP

• Multiple Global RPs (via MSDP full mesh)

• MSDP connectivity to SP network
RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 60
 Administratively-Scoped Zones
• Used to limit:
– High-BW sources to local site
– Control sensitive multicast traffic
• Simple scoped zone example:
– 239.193.0.0/16 = Campus Scope
– 239.194.0.0/16 = Region Scope
– 239.195.0.0/16 = Organization-Local (Enterprise) Scope
– 224.1.0.0 - 238.255.255.255 = Global scope (Internet) zone
• High-BW sources use Site-Local scope
• Low-Med. BW sources use Org.-Local scope
• Internet-wide sources use Global scope

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 61
 Administratively Scoped Address Range
239.0.0.0
• Address Range: 239.0.0.0/8
RFC 2365 • Private multicast address space.
Org.-Local
Expansion • Similar to RFC1918 private unicast
address space.
239.192.0.0
• RFC 2365 Administratively Scoped Zones.
• Organization-Local Scope (239.192/14)
RFC 2365
Org-Local – Largest scope within the Enterprise
Scope network (i.e. Enterprise-wide).
– Expands downward in address range.
239.196.0.0 • Local Scope (239.255/16)
Unassigned
– Expands downward in address range.
239.255.253.0 RFC 2365
Local Scope – Smallest possible scope within the
Expansion Enterprise network.
239.255.0.0 RFC 2365
Local
– Other scopes may be equal but not
Scope smaller.
239.255.255.255
RST-2261
(Not to scale.)
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 62
 Scope Relative Addresses – RFC 2365

Top 256 Addresses of every Admin. Scope Range.

Last
Offset Description
Octet
.255 0 SAP Session Announcement Protocol (SDR)
.254 1 MADCAP Protocol
.253 2 SLPv2 Protocol
.252 3 MZAP Protocol
.251 4 Multicast Discovery of DNS Services
.250 5 SSDP
.249 6 DHCPv4
.248 7 AAP
.247 8 MBUS
9 - 255 Unassigned

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 63
 Scope Relative Example – Local Scope
239.0.0.0

Address Description
239.255.255.255 SAP Session Announcement Protocol (SDR)
239.255.255.254 MADCAP Protocol
239.255.0.0
239.255.255.253 SLPv2 Protocol
239.255.255.252 MZAP Protocol
239.255.255.251 Multicast Discovery of DNS Services
239.255.255.250 SSDP
Local Scope 239.255.255.249 DHCPv4
239.255.255.248 AAP
239.255.255.247 MBUS

239.254.255.255
239.255.255.0 Local Scope
239.255.255.255 Scope Relative
RST-2261
(Not to scale.)
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 64
 Example Scope Address Assignments
239.0.0.0
• Allocate all ranges from the Org-Local
Org.-Local
space.
Expansion • Keep Local space separate.
239.191.0.0
– Avoids moving applications when smaller
239.192.0.0 scopes are added later.

239.193.0.0 Campus
Scope (/16) RFC
RFC2365
2365
239.194.0.0 Region Organization-Local
Organization-LocalScope
Scope
Scope (/16)
239.195.0.0 Enterprise
Scope (/16)
239.196.0.0

Local
Expansion

239.255.0.0 RFC 2365

Local
239.255.255.255 Scope
RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 65
 Adding a Additional Scopes
239.0.0.0
• Additional scope ranges are allocated
downward into Org-Local Expansion.
Org.-Local
Expansion – Not necessary to keep ranges in scope
239.191.0.0 size order.
Sub-Region
Scope (/16) – (i.e. “Sub-Region” scope is a larger
239.192.0.0 Building physical scope than the “Building” and
Scope (/16) “Campus” scopes).
239.193.0.0 Campus
Scope (/16) RFC
RFC2365
2365
239.194.0.0 Region Organization-Local
Organization-LocalScope
Scope
Scope (/16)
239.195.0.0 Enterprise
Scope (/16)
239.196.0.0

Local
Expansion

239.255.0.0 RFC 2365

Local
239.255.255.255 Scope
RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 66
 Address Ranges to Avoid
239.0.0.0 239.0.0.0/24

Org.-Local
Scope 239.128.0.0/24
Expansion
239.191.0.0 Sub-Region
Scope (/16) • Avoid ranges that map to a MAC address
239.192.0.0 Building
Scope (/16) of 0x0100-5E00-00xx!
239.193.0.0 Campus – i.e. 239.128.0/24 & 239.0.0/24
Scope (/16)
239.194.0.0 Region – These addresses are always flooded by
Scope (/16) Layer 2 switches!
239.195.0.0 Enterprise
Scope (/16)
239.196.0.0

Local Scope
Expansion

239.255.0.0 RFC 2365

Local
239.255.255.255 Scope
RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 67
 Enterprise Scope Relative Range
239.192.0.0
• Be sure to place Enterprise Scope at the
high end of the Org-Local range.
– Keeps Org-Local and Enterprise Scope
Relative ranges identical.
– Insures applications that use Org-Local
Scope Relative addresses work correctly.

Organization-Local
Organization-LocalScope
Scope
239.195.0.0 239.192.0.0/14
239.192.0.0/14

Enterprise
(239.195.0.0 -
239.195.254.255) Enterprise
EnterpriseScope
Scope
239.195.0.0/16
239.195.0.0/16

239.195.254.255
239.195.255.0 Organization-Local
Organization-Local
Enterprise
Scope
ScopeRelative
Relative
239.195.255.255 Scope-Relative
239.195.255.0/24
239.195.255.0/24
RST-2261
(Not to scale.)
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 68
 Adding Bidir Ranges to each Scope
239.194.0.0

Region Bidir • Subdivide each scope’s address range

(239.194.0/17)
Region into Bidir and ASM ranges.
239.194.128.0
(239.194.0.0 - – Keep ASM range at the upper end of the
239.194.254.255)
Region
address range.
(239.194.128/17) – Keeps Scope-Relative multicast in ASM
mode.
239.194.255.0
Region
Scope-Relative
239.195.0.0

Enterprise Bidir
(239.195.0/17)
Enterprise
239.195.128.0
(239.195.0.0 -
239.195.254.255)
Enterprise
(239.195.128/17)

239.195.255.0 Enterprise
239.195.255.255 Scope-Relative
RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 69
 Adding Private SSM Space
239.0.0.0
• Allocate 239.232/16 from Local Scope
Org.-Local
Scope
Expansion range for private SSM space.
Expansion – Subdivide SSM space into scoped zones.

239.192.0.0

239.193.0.0 Campus
Scope (/16) 239.232.0.0
239.194.0.0 Region
Scope (/16) Expansion
239.195.0.0 Enterprise
Scope (/16)
239.196.0.0

239.232.0.0 Private SSM 239.232.252.255

239.232.255.255 (/16) Campus SSM 239.232.253.0
Local Scope Scope (/24) 239.232.253.255
Expansion
Region SSM 239.232.254.0
239.255.0.0 RFC 2365
Scope (/24) 239.232.254.255
Local
Enterprise SSM 239.232.255.0
239.255.255.255 Scope
Scope (/24) 239.232.255.255
RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 70
 Avoid Overlapping Group Ranges

• Avoiding Overlapping Group Ranges

– Can’t use “deny” clause in C-RP ACL’s
•Implies “Dense-mode Override”
ip pim send-rp-announce loopback0 scope 16 group-list 10
access-list 10 deny 239.0.0.0 0.255.255.255
access-list 10 permit 224.0.0.0 15.255.255.255

– Must only use “permit” clauses

ip pim send-rp-announce loopback0 scope 16 group-list 10
access-list 10 permit 224.0.0.0 0.255.255.255
access-list 10 permit 225.0.0.0 0.255.255.255
.
.
.
access-list 10 permit 238.0.0.0 0.255.255.255

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 71
 Avoid Overlapping Group Ranges
239.255.255.255
access-list 10 permit 239.255.0.0 0.0.255.255 Local Scope
239.255.0.0/16
239.255.0.0

239.252.255.255
access-list 20 permit 239.195.0.0 0.0.255.255
Enterprise Scope
239.195.0.0/16
239.192.0.0
Use non-overlapping group
ranges when using Admin.
Scoping.
238.255.255.255 Global Scope
224.0.0.0/8
access-list 30 permit 224.0.0.0 0.0.255.255
access-list 30 permit 225.0.0.0 0.0.255.255 225.0.0.0/8
access-list 30 permit 226.0.0.0 0.0.255.255 226.0.0.0/8
. .
.
. .
access-list 30 permit 236.0.0.0 0.0.255.255 .
access-list 30 permit 237.0.0.0 0.0.255.255
access-list 30 permit 238.0.0.0 0.0.255.255 236.0.0.0/8
237.0.0.0/8
224.0.0.0 238.0.0.0/8
RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 72
 Admin Scoping using Anycast-RP
with Static RP Configuration

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 73
 Anycast-RP with Static RPs
• Concept:
•One set of Anycast RP’s per physical zone.
•MSDP peer only between a zone’s RP’s
•Static RP to populate Group/RP cache
• Advantages:
•Fast RP failure over
•Never lose Group/RP cache
•No need for special C-RP filters at boundaries
• Disadvantages:
•Changing address range allocation is a configuration
change on all routers within the zone

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 74
 Anycast-RP with Static RPs

• These Zones typically are defined as:

– Enterprise
– Region
– Campus

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 75
 Zones

• Enterprise
– IP Multicast streams needed to be sourced at any
Enterprise Site for receivers located across the
enterprise.
•Enterprise traffic does not exit the Enterprise
boundary
•Regions and Campuses receive Enterprise traffic

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 76
 Anycast-RP with Static RPs

• Region
– IP Multicast streams that have sources/receivers
only within that region.
•Region traffic does not exit the Region boundary
•Campuses within this Region receives this Region’s
traffic

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 77
 Anycast-RP with Static RPs

• Campus
•Local source/receivers only
» Campus traffic does not exit this Campus boundary

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 78
 The role of Group/RP cache

• Why is control of Group/RP cache so

Important?
– Group mode is determined by Group/RP cache
•Did we have a hit for the Group in Group/RP cache?
•Is the Group Dense or Sparse?
•Given the group Mode
» What operations are supported by the interfaces?

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 79
 The role of Group/RP cache
– If the interfaces are Sparse operation . . .
•Dense mode groups’ traffic have no way out of the
router
» Exception – IGMP report will populate the OIL
– In PIM-SM, control of IP Multicast traffic flows
depends on Group/RP cache hits.
•If no Group/RP cache hit, then group mode is Dense.
Thus no PIM joins/registers and no flow outside of
the router.
•“no Group/RP cache hit” . . . you can not use what
you don’t know!

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 80
 Anycast-RP with Static RPs
Internet with a capital “I”
Enterprise

Enterprise RP Enterprise RP

Campus RPs Campus RPs

Campus 1A Campus 2A

Region 1 Region 2

Regional RPs Regional RPs

Campus RPs Campus RPs
Campus 1B Campus 2B
MSDP Peering

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 81
 Anycast-RP with Static RPs
Internet with a capital “I”
Enterprise Enterprise:
Campus 1A: ip pim rp-address 100.100.300.1 30
ip pim rp-address 100.100.100.1 10 access-list 30 permit 239.195.0.0 0.0.255.255
access-list 10 permit 239.193.0.0 0.0.255.255

Enterprise RP Enterprise RP

Campus RPs Campus RPs

Campus 1A Campus 2A

Region 1 Region 1: Region 2

ip pim rp-address 100.100.200.1 20
access-list 20 permit 239.194.0.0 0.0.255.255
Regional RPs Regional RPs
Campus RPs Campus RPs
Campus 1B Campus 2B
Campus 1B: MSDP Peering
ip pim rp-address 100.100.111.1 10
access-list 10 permit 239.193.0.0 0.0.255.255
MSDP Peering (common to all)
ip msdp peer <remote-peer> connect-source Loopback0
ip msdp description <remote-peer> ** My Peer **
ip msdp originator-id Loopback0
RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 82
 Anycast-RP with Static RPs
Internet with a capital “I”
Enterprise

Enterprise RP Enterprise RP

Campus RPs Campus RPs

All routers will be in a Campus, in
Campus 1A a Region, and the EnterpriseCampus
Domain.2A

Region 1 Region 2
Thus each router in Campus 1A will have this configuration:
ip pim rp-address 100.100.100.1 10
ip pim rp-address 100.100.200.1 20
ip pim rp-address 100.100.300.1 30
Regional RPs Regional RPs
access-list 10 permit 239.193.0.0 0.0.255.255
Campus RPs access-list 20 permit 239.194.0.0 0.0.255.255 Campus RPs
Campus 1B access-list 30 permit 239.195.0.0 0.0.255.255
Campus 2B
MSDP Peering
And RPs will have:
ip msdp peer <remote-peer> connect-source Loopback0
ip msdp description <remote-peer> ** My Peer **
ip msdp originator-id Loopback0

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 83
 Anycast-RP with Static RPs
• Summary configuration points
– Boundary statements
•In a perfect world, not needed
•However, use boundary commands for catching mis-
configurations
– MSDP filters
•Must use MSDP filters when the router is the RP for
more than one scope.
•In a perfect world of separate RPs (routers) for each
different scope, not needed
– No special Dense mode group handling
•Interfaces are in Sparse mode operation
RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 84
 Implementing Scoping using
Auto-RP, Autorp listener, and
Boundary Configuration

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 85
 Implementing Administratively-Scoped Zones
Anycast-RP with Auto-RP

• Concept:
•One set of Anycast RP’s per physical zone.
•MSDP peer only between a zone’s RP’s
•Auto-RP to populate Group/RP cache
•Control Auto-RP packets to control Group/RP cache
ip multicast boundary access-list [filter-autorp | in | out]
» Match access-list ACEs to C-RP ACEs
» Interface command

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 86
 Implementing Administratively-Scoped Zones
Anycast-RP with Auto-RP

• Advantages:
•Fast RP failure over
•Less configuration to modify the group range
» Change ACL on C-RP routers
» Change ACL on Boundary routers

• Disadvantages:
•Can lose Group/RP cache, must wait for MA packet
» Mitigated by using the “interval” option in the rp-send-
discovery command
•Need for special boundary filtering at scope
boundaries

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 87
 Implementing Administratively-Scoped Zones
Anycast-RP with Auto-RP

• By using:
– Auto-RP/autorp listener
– Anycast-RP (including MSDP)
– Sparse Mode interface configuration
• We can achieve a relatively fast convergence.

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 88
 Implementing Administratively-Scoped Zones
Anycast-RP with Auto-RP

• Multicast Boundary Command

ip multicast boundary <acl> [filter-autorp]
– New ‘filter-autorp’ option
•Filters contents of Auto-RP packets
» Filters both Announcement and Discovery messages
» C-RP/MA entries that match “deny” ACE are removed from
packet
•Prevents C-RP/MA information from crossing the
edge of a scoped zone.
•Greatly simplifies Administratively-Scoped Zone
support using Auto-RP.
•Available in 12.0(22)S, 12.1(26)E, 12.2(18)SXD
12.2(12).
RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 89
 Implementing Administratively-Scoped Zones
Anycast-RP with Auto-RP

• How ‘filter-autorp’ option works:

– For each RP Entry in Auto-RP packet:
• If group-range in RP-Entry ‘intersects’
intersects any ‘denied’ group-range
in the Multicast Boundary ACL,
• Delete the RP Entry from Auto-RP packet.
– If resulting Auto-RP packet is non-empty,
• Forward across multicast boundary.
• Usually the MA packet is non-empty
• Simple method to ensure success
– Always match Auto-RP Group-Range ACLs to Multicast
Boundary ACLs.
– Never use overlapping Auto-RP group ranges.

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 90
 Implementing Administratively-Scoped Zones
Anycast-RP with Auto-RP
Internet with a capital “I”
Enterprise
Boundary to contain
Enterprise traffic

Enterprise RP Enterprise RP
Boundary to contain
Campus RPs Campus RPs
Regional traffic
Campus 1A Campus 2A

Region 1 Region 2

Regional RPs Regional RPs

Campus RPs Campus RPs
Campus 1B Campus 2B
MSDP Peering

Boundary to contain
Campus traffic

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 91
 Implementing Administratively-Scoped Zones
Anycast-RP with Auto-RP
Internet with a capital “I”
ip pim send-rp-announceEnterprise
Loopback1 scope 12 group-list 10
ip pim send-rp-discovery Loopback0 scope 12 interval 10
access-list 10 permit 239.193.0.0 0.0.255.255

239.193.0.0 239.193.0.0

Enterprise RP
Boundary to contain Enterprise RP
Campus traffic
Campus RPs Campus RPs
Campus 1A Campus 2A

Region 1 Region 2
Routers on the Campus boundary
239.193.0.0 ip multicast boundary 11 filter-autorp 239.193.0.0

Regional RPs access-list 11 deny 239.193.0.0 0.0.255.255 Regional RPs

access-list 11 permit any
Campus RPs Campus RPs
Campus 1B Campus 2B
MSDP Peering

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 92
 Implementing Administratively-Scoped Zones
Anycast-RP with Auto-RP
Internet with a capital “I”
Enterprise
239.194.0.0 239.194.0.0

Enterprise RP Enterprise RP

Campus RPs Campus RPs

Campus 1A ip pim send-rp-announce Loopback1 scope Campus 2A 20
22 group-list
ip pim send-rp-discovery Loopback0 scope 22 interval 10
Region 1 access-list 20 permit 239.194.0.0 0.0.255.255 Region 2

Regional RPs Regional RPs

Campus RPs Campus RPs
Campus 1B Campus 2B
Routers on the Regional boundary
MSDP Peering
ip multicast boundary 21 filter-autorp
access-list 21 deny 239.194.0.0 0.0.255.255
access-list 21 permit any
Boundary to contain
Regional traffic

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 93
 Implementing Administratively-Scoped Zones
Anycast-RP with Auto-RP
Internet with a capital “I”
Enterprise 239.195.0.0
Boundary to contain
Enterprise traffic

Enterprise RP Enterprise RP

Campus RPs Campus RPs

Campus 1A Campus 2A

Region 1 ip pim send-rp-announce Loopback1 scope 32 group-list 30 Region 2

ip pim send-rp-discovery Loopback0 scope 32 interval 10
access-list 30 permit 239.195.0.0 0.0.255.255

Regional RPs Regional RPs

Campus RPs Campus RPs
Campus 1B Campus 2B
Routers on the Enterprise boundary
MSDP Peering
ip multicast boundary 31 filter-autorp
access-list 31 deny 239.195.0.0 0.0.255.255
access-list 31 permit any

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 94
 Load Splitting via Group Range

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 95
 Load Splitting via BiDir RPs

Utilize bandwidth on both Wan links

1 Gigbit Servers 1 Gigbit Wan Links 1 Gigbit Servers

Wan Links

Data Center A Data Center B

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 96
 Load Splitting via BiDir RPs

• A Solution
– Configure Bidir PIM
– Use 2 RP sets, one set for each Data Center
– Use Phantom RP
– Engineer LAN’s DF and “best metric” RP on
same router
• A simple configuration
– Easy to support
– Easy to troubleshoot

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 97
 Load Splitting via BiDir RPs

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 98
 Load Splitting via BiDir RPs

Common configuration to all routers

ip multicast-routing

ip pim bidir-enable
ip pim rp-address 88.88.88.1 IPmcGrpA bidir
ip pim rp-address 77.77.77.1 IPmcGrpB bidir
!
ip access-list standard IPmcGrpA
permit 239.1.1.0 0.0.0.255
deny any
ip access-list standard IPmcGrpB
permit 239.1.2.0 0.0.0.255
deny any
RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 99
 Load Splitting via BiDir RPs
interface Loopback1
description *** Anycast-RP Grp B ***
ip address 77.77.77.1 255.255.255.248
DF a ip pim sparse-mode
ip ospf network point-to-point

RP b interface Ethernet0/0
ip address 8.8.8.1 255.255.255.0
ip pim query-interval 1
ip pim sparse-mode

interface Loopback1
description *** Anycast-RP Grp B ***
ip address 77.77.77.1 255.255.255.252
ip pim sparse-mode
ip ospf network point-to-point
!
RP b interface Ethernet0/0
DF b ip address 8.8.8.2 255.255.255.0
ip pim query-interval 1
ip pim sparse-mode

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 100
 Load Splitting via BiDir RPs
interface Loopback1
description *** Anycast-RP Grp A ***
ip address 88.88.88.1 255.255.255.252
ip pim sparse-mode DF a
ip ospf network point-to-point
!
interface Ethernet0/0
ip address 9.9.9.1 255.255.255.0 RP a
ip pim query-interval 1
ip pim sparse-mode

interface Loopback1
description *** Anycast-RP Grp A ***
ip address 88.88.88.1 255.255.255.248
ip pim sparse-mode
ip ospf network point-to-point
!
interface Ethernet0/0
RP a
ip address 9.9.9.2 255.255.255.0
ip pim query-interval 1 DF b
ip pim sparse-mode

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 101
 Load Splitting via BiDir RPs
Interface RP DF Winner Interface RP DF Winner
Ethernet0/0 88.88.88.1 8.8.8.1 Ethernet0/0 88.88.88.1 9.9.9.1

Grp a Grp a
Souce/ Souce/
Receiver Receiver

Grp b Grp b
Souce/ Souce/
Receiver Receiver

Interface RP DF Winner Interface RP DF Winner

Ethernet0/0 77.77.77.1 8.8.8.2 Ethernet0/0 77.77.77.1 9.9.9.2
RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 102
 SSM mapping for MoH

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 103
 SSM mapping for MoH

• Used when the Corporate Standard is SSM

globally
– Provides interim configuration for non-IGMPv3
hosts
• No RPs to configure
– Simplifies control plane across routers
• Simple configuration on LHRs
– SSM mapping is configured only on the LHRs
– Same configurations on all LHRs
• SSM mapping was first introduced in 12.3(2)T
RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 104
 SSM mapping for MoH

FHR receives PIM join

and MoH is flowing 5

IGMPv2 report is mapped

to the MoH source
3

Phone is signaled to
4
join MoH group and
sends IGMPv2 report 2
PIM S,G join is sent
toward Source

1
Router receives IGMPv2
report and caches it

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 105
 SSM mapping for MoH
• Enable SSM range
ip pim [vrf vrf-name] ssm {default | range All configurations are
done on the Last
access-list} Hop Router
• Enable SSM mapping
ip igmp [vrf vrf-name] ssm-map enable

• Disable DNS option:

no ip igmp [vrf vrf-name] ssm-map query dns

• Create map and ACL

ip igmp ssm-map [vrf vrf-name] static
access-control-list source-address
access-list access-list-number {deny | permit}
source [source-wildcard] [log]

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 106
 SSM mapping for MoH
Configuration on all routers

ip pim ssm range 64

access-list 64 permit 239.232.0.0 0.0.255.255

SSM mapping configurations on LHR

ip igmp ssm-map enable
no ip igmp ssm-map query dns
ip igmp ssm-map static 12 33.11.1.106
access-list 12 permit 239.232.1.1

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 107
 SSM mapping for MoH

Router# sh ip igmp ssm-mapping 239.232.1.1

Group address : 239.232.1.1
Database : Static
Source list : 33.11.1.106

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 108
 SSM mapping for MoH
Router# show ip igmp group 239.232.1.1 detail
Interface: Vlan20
Group: 239.232.1.1
Flags: SSM MoH
Uptime: 00:25:52 CCM

Group mode: INCLUDE

Last reporter: 0.0.0.0
CSR Grp Exp: 00:02:56
Group source list: (C - Cisco Src Report, U - URD, R –
Remote, S - Static, V - Virtual, M - SSM Mapping)
Source Address Uptime v3 Exp CSR Exp Fwd Flags SSM only WAN
33.11.1.106 00:25:52 stopped 00:02:56 Yes CM

Router# show ip mroute 239.232.1.1

(33.11.1.106, 239.232.1.1), 00:07:37/00:02:34, flags: sTI

Incoming interface: Ethernet0/0, RPF nbr 11.11.2.1
Outgoing interface list:
Ethernet1/0, Forward/Sparse, 00:07:37/00:02:34

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 109
 Summary - SSM mapping for MoH

• Advantages
– SSM Mapping provides compliance for IGMPv2
hosts in a SSM environment
– SSM Mapping avoids more complex solutions for
IP Multicast, i.e. GRE tunnels, RP configurations,
etc.
• Disadvantages
– SSM Mapping is static
– Configuration on the LHRs
RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 110
 More Information

• White Papers

• Web and Mailers

• Cisco Press

CCO Multicast page:

http://www.cisco.com/go/ipmulticast
Questions:
cs-ipmulticast@cisco.com
Customer Support Mailing List:
tac@cisco.com RTFB = “Read the Fine Book”
RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 111
 Multicast Bedtime Stories

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 112
 Recommended Reading

• Continue your Cisco

Networkers learning
experience with further
reading from Cisco Press
• Check the Recommended
Reading flyer for suggested
books

Available Onsite at the

Cisco Company Store

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 113
 Complete Your Online Session Evaluation
• Win fabulous prizes; Give us your
feedback
• Receive ten Passport Points for each
session evaluation you complete
• Go to the Internet stations located
throughout the Convention Center to
complete your session evaluation
• Drawings will be held in the
World of Solutions
– Tuesday, June 20 at 12:15 p.m.
– Wednesday, June 21 at 12:15 p.m.
– Thursday, June 22 at 12:15 p.m. and 2:00
p.m.

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 114
RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 115
 Appendix
• Configuring SSM
• Configuring SSM Mapping
• Configuring Bidir
• Configuring Combined Auto-RP & Anycast-RP
• Administrative Scoping Example
• Configuring Admin. Scoping with Auto-RP
• Configuring Admin. Scoping with Anycast-RP

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 116
 Configuring SSM

• Global command
ip pim ssm {default | <acl>}
– Defines SSM address range
•Default range = 232.0.0.0/8
•Use ACL for other ranges
– Prevents Shared Tree Creation
•(*, G) Joins never sent or processed
•PIM Registers never sent or processed
– Available in IOS versions
•12.1(5)T, 12.2, 12.0(15)S, 12.1(8)E

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 117
 SSM Mapping Configuration
Enabling SSM mapping on the router
ip igmp ssm-map enable
For static mapping:
ip igmp ssm-map static <acl-1> <source-1 IP address>
ip igmp ssm-map static <acl-2> <source-2 IP address>
For DNS mapping (existing commands):
ip domain-server <ip address>
ip domain-name <domain.com>
To disable DNS mapping
no ip igmp ssm-map query dns

DNS Record Format: 3.2.1.232 IN A 172.23.20.70

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 118
 Configuring Bidir PIM
(Auto-RP Example)

• Define Candidate RP and groups / modes it is

willing to serve
ip pim send-rp-announce Loopback0 scope 10 group-list 45 bidir
ip pim send-rp-announce Loopback1 scope 10 group-list 46
! Two loopbacks needed due to a nature of ACLs (permit, deny)
ip pim send-rp-discovery scope 10

access-list 45 permit 224.0.0.0 0.255.255.255

access-list 45 permit 227.0.0.0 0.255.255.255
! 224/8 and 227/8 will be PIM Bidir groups
access-list 45 deny 225.0.0.0 0.255.255.255
! 225/8 will be a PIM Dense Mode group

access-list 46 permit 226.0.0.0 0.255.255.255

! 226/8 will be a PIM Sparse Mode group

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 119
 Bidir PIM – Phantom RP

RP
E0 (DF)

E0 E0

E F
E1 (DF) E1 (DF)

E0 E0 E0 E0

A B C D
E1 (DF) E1 (DF) E1 (DF) E1 (DF)

Source Receiver 2 Receiver 1

Question: Does a Bidir RP even have to physically exist?

Answer: No. It can just be a phantom address.
RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 120
 Bidir PIM – Phantom RP

E0 (DF)

E0 E0

E F
E1 (DF) E1 (DF)

E0 E0 E0 E0

A B C D
E1 (DF) E1 (DF) E1 (DF) E1 (DF)

(*, 224.1.1.1), 00:32:20/00:02:59, RP 172.16.21.1, flags: BP

Bidir-Upstream: Ethernet0, RPF nbr 172.16.7.1
Source Outgoing Receiver
interface2 list: Receiver 1
Ethernet0, Bidir-Upstream/Sparse-Dense, 00:32:20/00:00:00
Ethernet1, Forward/Sparse-Dense, 00:00:49/00:02:41

Router “E” forwards traffic onto core LAN segment.

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 121
 Bidir PIM – Phantom RP

E0 (DF)

E0 E0

E F
E1 (DF) E1 (DF)

E0 E0 E0 E0

A B C D
E1 (DF) E1 (DF) E1 (DF) E1 (DF)

(*, 224.1.1.1), 00:00:49/00:02:41, RP 172.16.21.1, flags: B

Bidir-Upstream: Ethernet0, RPF nbr 172.16.1.1
Outgoing interface list:
Source Receiver
Ethernet0, 2
Bidir-Upstream/Sparse-Dense, 00:00:49/00:00:00 Receiver 1
Ethernet1, Forward/Sparse-Dense, 00:00:49/00:02:41

Router “F” forwards traffic on down the Shared Tree ala normal PIM-SM.
RP doesn’t even have to physically exist.
RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 122
 Phantom RP on Point-to-Point Core
Static Route Method

P S
RP: 1.1.1.1

ip multicast-routing ip multicast-routing

interface Loopback0 interface Loopback0

ip address 11.0.0.1 255.255.255.255 ip address 11.0.0.2 255.255.255.255
ip pim sparse-mode ip pim sparse-mode

router ospf 11 router ospf 11

redistribute static subnets redistribute static subnets

ip route 1.1.1.1 255.255.255.255 Loopback0 ip route 1.1.1.0 255.255.255.254 Loopback0

ip pim bidir-enable ip pim bidir-enable

ip pim rp-address 1.1.1.1 bidir ip pim rp-address 1.1.1.1 bidir

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 123
 Phantom RP on Point-to-Point Core
Netmask Method

P S
RP: 1.1.1.2

ip multicast-routing ip multicast-routing
! !
interface Loopback0 interface Loopback0
ip address 1.1.1.1 255.255.255.252 ip address 1.1.1.1 255.255.255.248
ip pim sparse-mode ip pim sparse-mode
ip ospf network point-
point-to-
to-point ip ospf network point-
point-to-
to-point
! !
router ospf 11 router ospf 11
network 1.1.1.0 0.0.0.3 area 0 network 1.1.1.0 0.0.0.7 area 0
network 10.1.1.0 0.0.0.255 area 0 network 10.1.1.0 0.0.0.255 area 0
network 10.1.2.0 0.0.0.255 area 0 network 10.1.2.0 0.0.0.255 area 0
! !
ip pim bidir-enable ip pim bidir-enable
ip pim rp-address 1.1.1.1 ip pim rp-address 1.1.1.1
ip pim rp-address 1.1.1.2 bidir ip pim rp-address 1.1.1.2 bidir
RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 124
 Combining Auto-RP and Anycast-RP
Configuration Steps
1. Enable Auto-RP
– Newer IOS images
» Use ip pim autorp listener global command and
configure ip pim sparse-mode on all interfaces.
– Older IOS images
» Configure ip pim sparse-dense-mode on all interfaces.
2. Configure Auto-RP Mapping Agents
ip pim send-rp-discovery interface Loopback0 scope 32

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 125
 Combining Auto-RP and Anycast-RP
Configuration Steps
3. Block DM Fallback
– Newer IOS images
» Use no ip pim dm-fallback
– Older IOS images
» Configure RP-of-last-Resort
ip pim rp-address <local_loopback> 10
access-list 10 deny 224.0.1.39
access-list 10 deny 224.0.1.40
access-list 10 permit any

4. Configure Anycast RP’s for desired group range.

5. Configure Anycast RP’s as Auto-RP C-RP’s
ip pim send-rp-discovery Loopback0 scope 32 group-list 10
– Loopback0 = Anycast RP Address
RST-2261
12735_05_2006_X2
» Anycast-RP’s will announce Anycast-RP address via Auto-RP
© 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 126
 Example Auto-RP and Anycast-RP

RP1 RP2
C-RP/MA
MSDP C-RP/MA
A B
10.1.1.1 10.1.1.1

Older IOS Newer IOS

X Y

interface Loopback 0 ip pim autorp-listener

ip address 10.2.1.1 255.255.255.255 no ip pim dm-fallback
interface Ethernet0/0 interface Ethernet0/0
ip pim sparse-dense-mode ip pim sparse-mode
ip pim rp-address 10.2.1.1 10
access-list 10 deny 224.0.1.39
access-list 10 deny 224.0.1.40
access-list 10 permit any

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 127
 Example Auto-RP and Anycast-RP

RP1 RP2
C-RP/MA
MSDP C-RP/MA
A B
10.1.1.1 10.1.1.1

Older IOS Newer IOS

X Y

interface Loopback 0
ip address 10.1.1.1 ;Anycast RP Address
ip pim send-rp-announce loopback0 scope 32 group-list 20
ip pim send-rp-discovery loopback0 scope 32
access-list 20 permit 239.192.0.0 0.0.255.255

interface Loopback 0
ip address 10.1.1.1 ; Anycast RP Address
ip pim send-rp-announce loopback0 scope 32 group-list 20
ip pim send-rp-discovery loopback0 scope 32
access-list 20 permit 239.192.0.0 0.0.255.255

RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 128
RST-2261
12735_05_2006_X2 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 129