Deploying IP

Multicast

BRKIPM-2261

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 1
 Housekeeping

We value your feedback- don't forget to complete your

online session evaluations after each session & complete
the Overall Conference Evaluation which will be available
online from Thursday

Visit the World of Solutions

Please remember this is a 'non-smoking' venue!

Please switch off your mobile phones

Please make use of the recycling bins provided

Please remember to wear your badge at all times
including the Party

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 2
 Session Goals

Provide important guidance on what to
consider when you deploy IP Multicast in
your Enterprise network.

Provide information on how to avoid
common deployment problems and issues.

Session Non Goals

Provide a “One-Size-Fits-All”
configuration that meets all your
Enterprise Multicast needs.

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 33
 Agenda

Which PIM Mode ?

General Configuration Notes

RP Engineering

Controlling Groups, Sources
& Receivers

Market Data Feed Forwarding

High Availability Notes

Controlling App Traffic - QoS,
Scoping

Receiver Tracking

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 4
 Things to Consider

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 5
 Application Details can kill you!

Get to know your Multicast Applications

You must develop an even closer relationship with your users
What multicast applications will they deploy?
What are the multicast applications’ characteristics?
One-to-Many or Many-to-Many?
How many and what Group addresses are used?
Are the Group addresses “hard-coded”  or can they be
configured?
What is the “Scope” of the application?
Link-Local, Building, Campus, Region, Enterprise-wide?
What are the QOS and Bandwidth requirements?

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 6
 Which PIM Mode?

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 7
 PIM Mode Categories

Sparse Mode (PIM-SM)

Original (Classic)
Supports both Shared and Source Trees

Source Specific Multicast (PIM-SSM)

aka Single Source Multicast
Supports only Source Trees
No need for RP’s, RP Failover, etc.

Bidirectional PIM (PIM-Bidir)

Supports only Shared Trees

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 8
 PIM Sparse Mode (PIM-SM)

Classic (original) PIMv2 Sparse Mode

Originally defined in RFC 2117, revised in RFC 2362
Standards Track PIMv2 specification is RFC 4601

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

Generally works well for most typical multicast

applications

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 9
 Source-Specific Multicast (SSM)

Well suited for One-to-Many Model.
Examples: IPTV, Digital Signage

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.
Data and Control Planes are decoupled

Simplifies address allocation.
Different content sources can use same group without fear of
interfering with each other.

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 10
 Bidirectional PIM (Bidir)

Many-to-Many State problem
Examples: HPC, Message Bus, Distributed Processing Apps
Large numbers of sources creates huge (S,G) state problem.
Router performance can begin to suffer

Bidir PIM:
Uses a Bidirectional Shared Trees.
Only (*,G) state is used. No (S,G) state.
Source traffic flows up the Shared Tree to RP and then to
receivers.
Note: Source traffic flows to RP even if there are no
receivers.

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 11
 Which PIM Mode

Use SSM
For One-to-Many applications
Eliminates need for RP Engineering.
Greatly simplifies network.
Data and Control Planes are decoupled

Use Bidir
For Many-to-Many | Few applications
Drastically reduces total (S,G) state in network.
Data and Control Planes are decoupled

Use PIM-SM
For all other general purpose applications
BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 12
 Some Generic
Configuration Notes

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 13
 PIM Configuration Steps

Enable Multicast Routing on every router

Configure every interface for PIM

Configure the RP for PIM-SM or PIM-Bidir
Statically
Using Auto-RP or BSR
Configure certain routers as Candidate RP(s)
All other routers automatically learn elected RP
Anycast RP for PIM-SM
Note: Anycast RP requires MSDP
Phantom RP for PIM-Bidir

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 14
 Configure PIM on Every Interface
Classic Partial Multicast Cloud Mistake
source
10.1.1.1

100 Mbps line has best metric to source

no ip pim sparse-mode 100 Mbps 10 Mbps ip pim sparse-mode

X
e0 e1
We’ll just use
the backup 10 Mbps RPF to disabled link
for the IPmc traffic
and not the
PIM Join never sent !!!
100 Mbps. Network
Engineer

receiver
BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 15
 Configure PIM on Every Interface
Classic Partial Multicast Cloud Mistake
source
10.1.1.1

100 Mbps line has best metric to source

no ip pim sparse-mode 100 Mbps 10 Mbps ip pim sparse-mode

e0 e1
We’ll just use
the backup 10 Mbps
for the IPmc traffic
and not the
100 Mbps. Network ip mroute 10.1.1.0 255.255.255.0 e1
Engineer

receiver
BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 16
 Configure PIM on Every Interface

Static mroutes can be used to force multicast traffic over
particular paths

This approach creates:
High maintenance / High cost of ownership
Error-prone enviroment that leads to unintended results

Don’t try to micro-manange your network !

Its usually not worth the effort

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 17
 Intermittent Source Applications

Definition:
Applications with sources that temporarily stop sending for > 3
minutes.

Impact:
(S,G) state times out within the network.
Initial packets often lost during SPT switchover.

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 18
 Solutions to Intermittent Sources

PIM-Bidir or PIM-SSM

No data driven events

Periodic keepalives or heartbeats

S,G Expiry timer

ip pim sparse sg-expiry-timer <secs>

Available 12.2(18)SXE5, 12.2(18)SXF4, 12.2(35)SE

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 19
 RP Engineering

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 20
 Static RP’s

Hard-coded RP address
When used, must be configured on every router
All routers must have the same RP address (per group)
Anycast RP must be used for Redunancy

Configuration
ip pim rp-address <address> [group-list <acl>] [override]
[bidir]
Optional group list specifies group range
Default: Range = 224.0.0.0/4
Override keyword “overrides” Auto-RP information
Default: Auto-RP and BSR learned info takes precedence
Bidir keyword specifies this group range as PIM-Bidir

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 21
 Auto-RP

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 22
 Why use Auto-RP ?

Auto-RP is a dynamic method for the network to learn RP
to Group mapping information

This helps when:

RP address and group ranges change often

Your network has 100s or 1000s of routers and you want
to simplify the config

There are several RPs for different applications

RPs maintained by different administrative groups

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 23
 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

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 24
 Auto-RP Overview

er y

ry
ove
cov

Disc
Dis
Dis Disc
cov ove
er y
MA ry MA
Dis Disc
A cov B ove
ry
er y er y

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

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 25
 Auto-RP Configuration – Candidate RPs

Candidate RPs
Multicast RP-Announcement messages
Sent to Cisco-Announce (224.0.1.39) group
Sent every rp-announce-interval (default: 60 sec)
RP-Announcements contain:
Group Range (default = 224.0.0.0/4)
Candidate’s RP address
Holdtime = 3 x <rp-announce-interval>
Configured via global config command
ip pim send-rp-announce <intfc> scope <ttl> [group-list acl]
[interval <sec>] [bidir]

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 26
 Auto-RP Configuration – Mapping
Agents

Mapping agents
Receive RP-Announcements
Stored in Group-to-RP Mapping Cache with holdtimes
Elects highest C-RP IP address as RP for group range
Multicast RP-Discovery messages
Sent to Cisco-Discovery (224.0.1.40) group
Sent every rp-discovery-interval (default: 60 secs)
Both rp-announce-interval and rp-discovery-interval must be set to
lower convergence times
Configured via global config command
ip pim send-rp-discovery [<interface>] scope <ttl>
[interval <sec>]
Source address of packets set by <interface>
If not specified, source address = output interface address
Results in the appearance of multiple MA’s. (one/interface)
BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 27
 Auto-RP Configuration - Auto-RP
Listener

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.
Only needed if Auto-RP is to be used.
Available 12.3(4)T, 12.2(28)S, 12.1(13)E7

Use with interface command
ip pim sparse-mode  Recommended
Prevents DM Flooding.

Only reason to use sparse-dense is for DM groups

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 28
 Dense Mode Fallback

Caused by loss of local RP information in older IOS releases.
Entry in Group-to-RP mapping cache times out.

Can happen when:
All C-RP’s fail.
Auto-RP/BSR mechanism fails.
Possibly a result of network congestion.

Group is switched over to Dense mode.
*,G mroute entry changes to Dense mode
Flags of S,G entries change from JT to T
S,G PIM Joins are no longer sent
State times out on upstream router – traffic flow stops
All existing PIM-SM SPT’s are dropped!
Dense mode flooding begins if interfaces configured with
ip pim sparse-dense-mode

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 29
 Avoiding DM Fallback in Auto-RP/BSR

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

Needed Prior to IOS 12.3(4)T, 12.2(33)SXH

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 30
 Avoiding DM Fallback Automatically

New IOS global command

no ip pim dm-fallback

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.
All SPT’s remain active.
Behavior is enabled by default if all interfaces are in sparse
mode

Available 12.3(4)T, 12.2(33)SXH

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 31
 Auto-RP Summary

Use Auto-RP Listener with Sparse Mode interfaces
With newer code you automatically get No Dense Mode Fallback

With older code that doesn’t have:
no ip pim dm-fallback
Use RP of Last Resort to prevent loss of active S,G entries in case
of RP failure

With ancient code that doesn’t have AutoRP Listener
Use sparse-dense interfaces
Use RP of Last Resort
Or Upgrade ;-)

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 33
 Anycast RPs

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 34
 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

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 35
 Anycast RP Overview

Src Src

RP1 RP2
X

A B
10.1.1.1 10.1.1.1

Rec Rec Rec Rec

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 36
 Anycast RP Configuration

RP1 RP2
MSDP
A B
ip pim rp-address 10.0.0.1 ip pim rp-address 10.0.0.1

C D

Interface loopback 0 Interface loopback 0

ip address 10.0.0.1 255.255.255.255 ip address 10.0.0.1 255.255.255.255
ip pim sparse-mode ip pim sparse-mode

Interface loopback 1 Interface loopback 1

ip address 10.0.0.2 255.255.255.255 ip address 10.0.0.3 255.255.255.255
! !
ip msdp peer 10.0.0.3 connect-source loopback 1 ip msdp peer 10.0.0.2 connect-source loopback 1
ip msdp originator-id loopback 1 ip msdp originator-id loopback 1

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 37
 Combining Auto-RP and Anycast-RP

Anycast-RP and Auto-RP may be combined.

Provides advantages of both methods
Rapid RP failover of Anycast RP
No DM Fallback
Configuration flexibility of Auto-RP
Ability to effectively disable undesired groups

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 38
 Anycast RP with Auto-RP Configuration

RP1 RP2
MSDP
A B
ip multicast-routing ip multicast-routing

C D

Interface loopback 0 Interface loopback 0

ip address 10.0.0.1 255.255.255.255 ip address 10.0.0.1 255.255.255.255

Interface loopback 1 Interface loopback 1

ip address 10.0.0.2 255.255.255.255 ip address 10.0.0.3 255.255.255.255
! !
ip pim send-rp-announce loopback 0 scope 32 ip pim send-rp-announce loopback 0 scope 32
ip pim send-rp-discovery loopback 1 scope 32 ip pim send-rp-discovery loopback 1 scope 32
! !
ip msdp peer 10.0.0.3 connect-source loopback 1 ip msdp peer 10.0.0.2 connect-source loopback 1
ip msdp originator-id loopback 1 ip msdp originator-id loopback 1

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 39
 Phantom BiDir RPs

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 40
 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.
BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 41
 Phantom RP on Point-to-Point Core

30 Bit Mask 29 Bit Mask

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-to-point OSPF requires ip ospf network point-to-point
! !
interface Ethernet0/0 P2P interfaces interface Ethernet0/0
ip address 10.1.1.1 255.255.255.0 ip address 10.1.1.2 255.255.255.0
ip pim sparse-mode ip pim sparse-mode
! !
interface Ethernet1/0 interface Ethernet1/0
ip address 10.1.2.1 255.255.255.0 ip address 10.1.2.2 255.255.255.0
ip pim sparse-mode ip pim sparse-mode
! !
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.2 bidir ip pim rp-address 1.1.1.2 bidir

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 42
 Phantom RP with Auto-RP

Previously, Auto-RP could only advertise IP address on
interface (e.g. loopback) as RP

New option has been added – now we can advertise any
address on a directly connected subnet
ip pim send-rp-announce <[int] | [ip-address]> scope [group-list] [bidir]

In example below, Phantom RP address of 1.1.1.2 is

being advertised through Auto-RP. The source of the
Mapping packets are the address on Loopback1
ip pim send-rp-announce 1.1.1.2 scope 32 bidir

ip pim send-rp-discovery Loopback1 scope 32

interface Loopback0
ip address 1.1.1.1 255.255.255.252
ip pim sparse-mode

Available 12.4(7)T, 12.2(18)SXF4

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 43
 Controlling
Groups, Senders
and Receivers

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 44
 Disabling Multicast Groups – Local Loopback

Local Loopback RP Method

Concept:
Only Auto-RP/BSR learned groups are authorized.
All other groups are considered unauthorized.
Implementation:
On each router, define local Loopback as RP for all groups.
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
Use Auto-RP/BSR to override this and enable authorized
groups.

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 45
 Disabling Multicast Groups – Local Loopback

Local Loopback RP Method

Operation:
Each router serves as RP for unauthorized groups.
Collapses PIM-SM domain of unauthorized groups down
to the local router.
Unauthorized group traffic cannot flow beyond local router.
But it can still flow between Senders & Receivers directly
connected to the router.
Effectively “discourages” deployment of unknown, unauthorized
multicast applications.

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 46
 Disabling Multicast Groups – New
Method

New Global Command Extension

ip multicast-routing [group-range <acl>]
Router drops all Control packets (PIM, IGMP) for denied groups.
Router drops all Data packets for denied groups.
No IGMP or PIM state created for denied groups.
Same behavior as placing a multicast boundary on every interface

Available in 12.2(33)SXI

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 47
 Disabling Auto-RP with group-range

There is no direct way to turn off Auto-RP from creating
state and accepting reports

The group-range command could be used to disable
Auto-RP

In this example, state will never be created for
224.0.1.[39|40] but all other 224/4 groups will operate
ip multicast group-range 1
access-list 1 deny 224.0.1.39 0.0.0.0
access-list 1 deny 224.0.1.40 0.0.0.0
access-list 1 permit any any

In example below, 239/8 is allowed for multicast. All other

groups will be disabled
ip multicast group-range 1
access-list 1 permit 239.0.0.0 0.255.255.255

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 48
 Controlling Senders

Global command
ip pim accept-register [list <acl>] | [route-map <map>]

Used on RP to filter incoming Register messages

Filter on Source address alone (Simple ACL)
Filter on (S, G) pair (Extended ACL)

Helps prevents unwanted sources from sending
First hop router blocks traffic from reaching net
Note: Traffic can still flow under certain situations

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 49
 Controlling Senders

RP configured to only accept

RP Registers from specific source.

192.16.2.1

192.16.1.1
ip pim accept-register list 10

(S, G) Register (unicast) access-list 10 permit 192.16.1.1

(S, G) Register-Stop (unicast)

Receiver Receiver

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 50
 Market Data Feed
Forwarding

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 51
 Market Data Distribution - Interface

Content Content Content

Provider Provider Provider

Financial
Service
Provider

Brokerage Brokerage Brokerage

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 52
 Provisioning Options
• Static Forwarding
• Static Service Levels – Cable Model
• Dynamic Forwarding
• Hybrid Design

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 53
 Traditional MD Interface Requirements
• Customers and providers prefer lowest common
denominator – least coordination
Providers are under contract to deliver stream
Each side wants to limit organizational liability and coordination – KISS
Ideal Scenario: Provider and Customer have separate multicast domains
Therefore:
Traffic is statically nailed up
No PIM Neighbors
No DR on edge
No PIM Joins
No shared RP
No MSDP

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 54
 MD Distribution – Virtual RP
• MD feed is statically nailed up
interface
interface Ethernet0
Ethernet0
ip
ip address 10.1.2.1
address 10.1.2.1 255.255.255.0
255.255.255.0 Source Destination
ip pim sparse-mode
ip pim sparse-mode 10.2.2.2 224.0.2.64
ip
ip igmp
igmp static-group
static-group 224.0.2.64
224.0.2.64

• Customer Edge router advertises RP

address from upstream interface Market Data
Source Network
interface
interface Ethernet1
Ethernet1
ip
ip address
address 10.1.2.2
10.1.2.2 255.255.255.0
255.255.255.0
ip
ip pim
pim sparse-mode
sparse-mode
Virtual RP e0
ip
ip pim
pim rp-address
rp-address 10.1.1.1
10.1.1.1

ip
ip route
route 10.1.1.1
10.1.1.1 255.255.255.255
255.255.255.255 10.1.2.5
10.1.2.5 e1
router
router ospf
ospf 11
11
network
network 10.1.0.0
10.1.0.0 0.0.255.255
0.0.255.255 area
area 00
redistribute static subnets
redistribute static subnets
Customer

• Every router in customer network

needs to know about the RP
ip
ip pim
pim rp-address
rp-address 10.1.1.1
10.1.1.1

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 55
 MD Distribution – Edge router is RP
• MD feed is statically nailed up Source Destination
interface 10.2.2.2 224.0.2.64
interface Ethernet0
Ethernet0
ip
ip address 10.1.2.1
address 10.1.2.1 255.255.255.0
255.255.255.0
ip pim sparse-mode
ip pim sparse-mode
ip
ip igmp
igmp static-group
static-group 224.0.2.64
224.0.2.64
Market Data
• Customer Edge router is RP – so that Source Network
it will accept a non-connected source
interface
interface Ethernet1
Ethernet1
ip
ip address
address 10.1.2.2
10.1.2.2 255.255.255.0
255.255.255.0 e0
ip
ip pim
pim sparse-mode
sparse-mode
e1
interface
interface Loopback0
Loopback0
ip
ip address
address 10.1.1.1
10.1.1.1 255.255.255.255
255.255.255.255 RP
ip
ip pim
pim sparse-mode
sparse-mode

ip
ip pim
pim rp-address
rp-address 10.1.1.1
10.1.1.1 Customer

• Every router in customer network

needs to be know about the RP
ip
ip pim
pim rp-address
rp-address 10.1.1.1
10.1.1.1

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 56
 MD Distribution – Edge router is RP
• MD feed is statically nailed up Source Destination
interface 10.2.2.2 224.0.2.64
interface Ethernet0
Ethernet0
ip
ip address 10.1.2.1
address 10.1.2.1 255.255.255.0
255.255.255.0
ip pim sparse-mode
ip pim sparse-mode
ip
ip igmp
igmp static-group
static-group 224.0.2.64
224.0.2.64
Market Data
• Customer Edge router is RP – so that Source Network
it will accept a non-connected source
This method will NOT work
interface
interface Ethernet1
Ethernet1
e0
with future versions of IOS
ip
ip address
ip
address 10.1.2.2
ip pim
10.1.2.2 255.255.255.0
pim sparse-mode
sparse-mode
255.255.255.0

e1
interface
interface Loopback0
Loopback0
ip
ip address
address 10.1.1.1
10.1.1.1 255.255.255.255
255.255.255.255 RP
ip
ip pim
pim sparse-mode
sparse-mode

ip
ip pim
pim rp-address
rp-address 10.1.1.1
10.1.1.1 Customer

• Every router in customer network

needs to be know about the RP
ip
ip pim
pim rp-address
rp-address 10.1.1.1
10.1.1.1

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 57
 MD Distribution –
Edge router proxy registers to RP
• MD feed is statically nailed up Source Destination
interface 10.2.2.2 224.0.2.64
interface Ethernet0
Ethernet0
ip
ip address 10.1.2.1
address 10.1.2.1 255.255.255.0
255.255.255.0
ip pim sparse-mode
ip pim sparse-mode
ip
ip igmp
igmp static-group
static-group 224.0.2.64
224.0.2.64
Market Data
• Customer Edge router has dense- Source Network
mode on IIF and proxy registers to RP
interface
interface Ethernet1
Ethernet1
ip
ip address 10.1.2.2
address 10.1.2.2 255.255.255.0
255.255.255.0 e0
ip
ip pim dense-mode proxy-register list
pim dense-mode proxy-register list 100
100
access-list
access-list 100
100 permit
permit ip
ip any
any any
any e1
ip
ip pim
pim rp-address
rp-address 10.1.1.1
10.1.1.1

• RP is configured inside customer Customer

network
RP
interface
interface Loopback0
Loopback0
ip
ip address 10.1.1.1
address 10.1.1.1 255.255.255.255
255.255.255.255
ip pim sparse-mode
ip pim sparse-mode

ip
ip pim
pim rp-address
rp-address 10.1.1.1
10.1.1.1

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 58
 MD Distribution –
Edge router is RP and MSDP peer
• Customer Edge router is RP and Source Destination
MSDP peer of main customer RP 10.2.2.2 224.0.2.64

interface
interface Ethernet1
Ethernet1
ip
ip address
address 10.1.2.2
10.1.2.2 255.255.255.0
255.255.255.0
ip
ip pim
pim dense-mode
dense-mode
Market Data
interface
interface Loopback0
Loopback0 Source Network
ip
ip address 10.1.1.1
address 10.1.1.1 255.255.255.255
255.255.255.255
interface
interface Loopback1
Loopback1
ip
ip address
address 10.1.3.2
10.1.3.2 255.255.255.255
255.255.255.255 e0
ip
ip pim
pim rp-address
rp-address 10.1.1.1
10.1.1.1
e1
ip
ip msdp
msdp peer
peer 10.1.3.1
10.1.3.1 connect-source
connect-source Loopback1
Loopback1
ip
ip msdp
msdp originator-id
originator-id Loopback1
Loopback1 RP

interface
interface Loopback0
Loopback0
ip
ip address
address 10.1.1.1
10.1.1.1 255.255.255.255
255.255.255.255 Customer
interface
interface Loopback1
Loopback1 RP
ip
ip address 10.1.3.1
address 10.1.3.1 255.255.255.255
255.255.255.255
ip
ip pim
pim rp-address
rp-address 10.1.1.1
10.1.1.1
ip
ip msdp
msdp peer
peer 10.1.3.2
10.1.3.2 connect-source
connect-source Loopback1
Loopback1
ip
ip msdp
msdp originator-id
originator-id Loopback1
Loopback1

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 59
 MD Distribution –
Edge router is RP and MSDP peer
• Customer Edge router is RP and Source Destination
MSDP peer of main customer RP 10.2.2.2 224.0.2.64

interface
interface Ethernet1
Ethernet1
ip
ip address
address 10.1.2.2
10.1.2.2 255.255.255.0
255.255.255.0
ip
ip pim
pim dense-mode
dense-mode
Market Data
interface
interface Loopback0
Loopback0 Source Network
ip
ip address 10.1.1.1
address 10.1.1.1 255.255.255.255
255.255.255.255
Dense
interface
interfacemode is required on the IIF so
Loopback1
Loopback1
thatipthe
ip A flag
address
address will be
10.1.3.2
10.1.3.2 set and MSDP
255.255.255.255
255.255.255.255 e0
will
ip forward
ip pim
pim an SA
rp-address
rp-address 10.1.1.1
10.1.1.1
e1
ip
ip msdp
msdp peer
peer 10.1.3.1
10.1.3.1 connect-source
connect-source Loopback1
Loopback1
ip
ip msdp
msdp originator-id
originator-id Loopback1
Loopback1 RP

interface
interface Loopback0
Loopback0
ip
ip address
address 10.1.1.1
10.1.1.1 255.255.255.255
255.255.255.255 Customer
interface
interface Loopback1
Loopback1 RP
ip
ip address 10.1.3.1
address 10.1.3.1 255.255.255.255
255.255.255.255
ip
ip pim
pim rp-address
rp-address 10.1.1.1
10.1.1.1
ip
ip msdp
msdp peer
peer 10.1.3.2
10.1.3.2 connect-source
connect-source Loopback1
Loopback1
ip
ip msdp
msdp originator-id
originator-id Loopback1
Loopback1

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 60
 Static Forwarding – Cable Model
Adapt cable model of provisioning for Market Data
Basic Service
ip access-list standard basic-service
permit 239.192.1.0 0.0.0.255 ! Basic service channels

Premium Service
ip access-list standard premium-service
permit 239.192.1.0 0.0.0.255 ! Basic service channels
permit 239.192.2.0 0.0.0.255 ! Premium service channels

Premium Plus Service

ip access-list standard premium-plus-service
permit 239.192.1.0 0.0.0.255 ! Basic service channels
permit 239.192.2.0 0.0.0.255 ! Premium service channels
permit 239.192.3.0 0.0.0.255 ! Premium Plus service channels

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 61
 Static Forwarding – group range command
Subscribing dozens or hundreds of groups can be
cumbersome with the static-group command:
interface Vlan6
ip igmp static-group 224.0.2.64
ip igmp static-group 224.0.2.65
ip igmp static-group 224.0.2.66
...
ip igmp static-group 224.0.2.80

class-map type multicast-flows

market-data group 224.0.2.64 to 224.0.2.80
interface Vlan6
ip igmp static-group class-map market-data

The static group range command simplifies the config:

Available in 12.2(18)SXF5
BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 62
 Advantages of Static Forwarding
• Provider and customer have separate multicast domains
Each is free to use any forwarding model
e.g. PIM-SM, PIM-SSM, PIM-Bidir, PIM-DM
Each is responsible for their portion of the delivery model – clear
demarcation
Simple, straight-forward
Has traditionally been first choice for FSP

Main Disadvantage
Customer is not able to control subscriptions and
bandwidth usage of last mile dynamically.

As data rates climb this is more of a issue.

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 63
 Dynamic Forwarding
Rising data rates and 24 hour trading are driving the
requirement for dynamic subscriptions.
Methods:
• IGMP Membership Reports
• PIM Joins - *,G for PIM-SM and PIM-Bidir
• PIM Joins - S,G for PIM-SSM

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 64
 Dynamic Service – Static Subscriptions with
IGMP
Customers want ability to nail up service
Existing Issues
• ip igmp join-group <group>
Sends an IGMP report out the interface
Traffic gets punted to CPU
• ip igmp static-group <group>
Adds interface to OIL
Does not send IGMP report out the interface
Workarounds
• Separate router - Put IGMP join group on a dedicated router
Need Better Solution
• ip igmp join-group <group> passive - under consideration
IGMP report will be sent but traffic will not be punted to CPU
IGMP host code on router will respond to queries
L flag will not be set ?

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 65
 MD Distribution – Provider wants IGMP Report
Source Destination
• Assumes that hosts sit on edge of customer
10.2.2.2 224.0.31.20
network or breaks multicast delivery model
• Stretches the original design and purpose of
IGMP
Market Data
• CME is doing this today in USA Source Network
• We can make this work dynamically today with a
cumbersome combination of:
e0
ip igmp helper
ip igmp proxy-service IGMP e1
ip igmp mroute-proxy
• Industry may want to recommend this model
PIM
going forward Customer

IGMP

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 66
 MD Distribution – igmp mroute-proxy
• igmp proxy service and helper are Market Data
configured on loopback Source Network
interface
interface Loopback1
Loopback1
ip
ip address 10.3.3.3
address 10.3.3.3 255.255.255.0
255.255.255.0
ip pim sparse-mode
ip pim sparse-mode
ip
ip igmp
igmp helper-address
helper-address 10.4.4.4
10.4.4.4 10.4.4.0/24 e0
ip igmp proxy-service
ip igmp proxy-service IGMP
ip
ip igmp
igmp access-group
access-group filter-igmp-helper
filter-igmp-helper e1
ip
ip igmp query-interval 99
igmp query-interval

• Downstream interface is configured loopback1

e0
with igmp mroute-proxy
interface
interface Ethernet0
Ethernet0 PIM
ip
ip address 10.2.2.2
address 10.2.2.2 255.255.255.0
255.255.255.0 Customer
ip
ip pim
pim sparse-mode
sparse-mode
ip
ip igmp
igmp mroute-proxy
mroute-proxy Loopback1
Loopback1

• Every router in customer network

needs to be know about the virtual RP IGMP
ip
ip pim
pim rp-address
rp-address 20.20.20.20
20.20.20.20
ip
ip route 20.20.20.20 255.255.255.255
route 20.20.20.20 255.255.255.255 10.4.4.4
10.4.4.4

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 67
 MD Distribution – igmp mroute-proxy detail
4. The first PIM *,G Join on e0 triggers Market Data
an unsolicited IGMP report to be Source Network
generated on the loopback1
interface
10.4.4.0/24 e0

3. PIM *,G Join message is received on e1

e0 interface and mroute state is
created. The igmp mroute-proxy
loopback1
command on interface causes e0
special internal flag to be added to
mroute
PIM
Customer
2. PIM *,G Join message filters up
towards virtual RP

1. Host sends IGMP report and creates

mroute state IGMP
(*,
(*, 239.254.1.0),
239.254.1.0), 00:00:01/00:02:55,
00:00:01/00:02:55, RP
RP 20.20.20.20,
20.20.20.20, flags:
flags: SC
SC
Incoming
Incoming interface:
interface: FastEthernet1/15,
FastEthernet1/15, RPF
RPF nbr
nbr 10.2.2.2,
10.2.2.2, RPF-MFD
RPF-MFD
Outgoing
Outgoing interface
interface list:
list:
Vlan194,
Vlan194, Forward/Sparse,
Forward/Sparse, 00:00:01/00:02:55,
00:00:01/00:02:55, HH
BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 68
 MD Distribution – igmp mroute-proxy detail
6. When the periodic IGMP query is run on
loopback1 the igmp proxy-service command Market Data
initiates a walk through the mroute table Source Network
looking for the mroute-proxy flag. An IGMP
report is generated for each mroute with the
mroute-proxy flag set.
As long as the mroute is kept alive 10.4.4.0/24 e0
with PIM joins the IGMP reports will be IGMP
forwarded. e1

5. The igmp helper command directs the loopback1

IGMP report out the e1 interface e0

IGMP reports are dynamic – they are

only sent when there is interest in the PIM
customer domain. Customer
However, the edge router does not
respond to queries from provider
router.
Two problems: IGMP
• 7 times more IGMP messages than needed
• Cumbersome config
BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 69
 Dynamic Service – Dynamic Subscriptions
with IGMP
Better Solution: IGMP Host Proxy Coming
Global command: Soon
ip igmp host-proxy <group acl>
Functionality:
1. When mroute state is created for any group defined by <acl>
The mroute-proxy flag will be set
An IGMP report is generated for the mroute and set out the IIF of the
mroute
2. When an IGMP Query is received for a group defined by <acl>
If mroute state exists, generate IGMP report
3. When a PIM Prune is received for a group defined by <acl>
An IGMP leave message is generated
4. All modes of PIM should be supported – PIM-SM, PIM-Bidir and PIM-SSM.
The groups must be defined on the router and the behavior will work
appropriately. This solution should be compliant with RFC4605 and EDCS-
623893.

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 70
 MD Distribution – Other options
• Provider accepts PIM join Source Destination
10.2.2.2 224.0.2.64
– Sparse Mode
Provider must supply RP addr
Requires PIM Neighbor relationship Market Data
No RP on customer Side Source Network

One multicast domain RP

e0
– Source Specific Multicast
e1
Provider must supply S,G info RP
Requires PIM Neighbor relationship
Customer
• MSDP
RP
Standard Interdomain Multicast
Requires peering relationship

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 71
 Dynamic Forwarding - *,G PIM Joins
• Requires more coordination than static joins or IGMP
PIM Neighbors
RP Info
MSDP ?

• Redundancy is up to server side

Standby server can monitor the stream and begin

forwarding when traffic stops for a defined interval

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 72
 Dynamic Forwarding – S,G PIM Joins
• Works in situations that are ideal for SSM
• No need to share RP info or use MSDP
Redundancy options:
Host side
Host can join both primary and secondary servers
– for both A and B streams
Host will need to arbitrate between primary and standby
Network/Server side
Anycast Source - Hosts only join one server and network tracks
server and forwards active stream

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 73
 Market Data Design Whitepapers

A set of 4 docs that cover all aspects of network and application design for
Market Data distribution

Market Data Network Architecture (MDNA)

Trading Floor Architecture

Design Best Practices for Latency Optimization

IP Multicast Best Practices for Enterprise Customers

http://www.cisco.com/go/financial

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 74
 High Availability
Notes

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 75
 PIM Query Interval Tuning
Corp. Intranet

A B
.2 (DR) 192.168.1.0/24 .1

router-b#show
router-b#show ip
ip pim
pim neighbor
neighbor
PIM Neighbor Table
PIM Neighbor Table
Neighbor
Neighbor Interface
Interface Uptime/Expires
Uptime/Expires Ver
Ver DR
DR
Address
Address Prio/Mode
Prio/Mode
192.168.1.2
192.168.1.2 GigabitEthernet3/13
GigabitEthernet3/13 14w5d/00:01:32
14w5d/00:01:32 v2
v2 11 // DR
DR BB SS

• DR Failover is triggered by neighbor expiration time

• Expiration Time sent in PIM query messages
Expiration time = 3 x <query-interval>
Default <query-interval> = 30 seconds
DR Failover = 90 seconds (worst case) by default
• Use interface configuration command:
ip pim query-interval <period> [msec]
• Setting period to 1 sec has a failover of 3 sec
• 500 ms lowest recommended setting
BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 76
 Market Data Distribution – Path Diversity
Data
Center
• A and B Traffic
will take two
different physical
paths
cost 3
RP RP
• Edge routers on cost
2 cost
2

cost 1
trading room floor
have alternating cost 1
DRs cost 3

cost 2
• PIM Joins will be 2 cost
cost 1

cost 1
forwarded by the
DR towards the
cost 3
RP or source
• Different link
costs will create Trading
different
Room
forwarding state
Floor

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 77
 Controlling
Application Traffic
with QoS and
Scoping

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 78
 Application Traffic – Approach

Video distribution often has well defined characteristics

IPTV providers know how many channels they have and which groups they
are using
Depending on Codec we can make assumptions about expected bandwidth

Financial App traffic has different characteristics
Finance App data rate can surge on emotion of market
Financial Apps (inside Brokerage) are better controlled and understood than
MD feeds

Challenge: Apps are distributed – many servers sending in
uncoordinated fashion

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 79
 Application Traffic – Network approach

• Addressing plan that sets aside ranges for different BW limits

• Multicast boundary command to limit high BW streams
• QoS can use both DSCP and Mcast Address for policing, queuing
• Microflow policing to limit streams of certain apps (6500/7600)
• mCAC - limit the number of flows a branch can subscribe

Microflow policing and mCAC assume that BW requirements for

certain applications are known and fairly static.

WRED does not differentiate between TCP and UDP traffic.

This also affects VoIP traffic.
BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 80
 Application Traffic – Addressing Plan
A multicast addressing plan is crucial for deploying global
applications. It will help with:

• Troubleshooting
• QoS Policies
• Scoping

Example Address plan by bandwidth:

1 Mbps streams – 239.1.1.0/24
2 Mbps streams – 239.1.2.0/24
4 Mbps streams – 239.1.4.0/24

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 81
 Deploying Multicast Boundaries
Corp HQ

Multicast boundaries block

239.1.4.0/24 high BW traffic from going
to remote sites

Border A
Multicast Multicast
S0

S1
Boundaries Boundaries

Site A S0

S0
Site B
Border B Border C

239.1.4.0/24 239.1.4.0.0/24

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 82
 Deploying Multicast Boundaries
! Access list on all routers Corp HQ
access-list 10 deny 239.1.4.0 0.0.0.255
access-list 10 permit any

Multicast boundaries block

239.1.4.0/24 high BW traffic from going
to remote sites

interface Serial0
Border A interface Serial0
ip multicast boundary 10
ip multicast boundary 10
S0

S1
interface Serial1
ip multicast boundary 10

Site A S0

S0
Site B
Border B Border C

239.1.4.0/24 239.1.4.0.0/24

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 83
 QoS with Multicast

QoS protection necessary for remote
users and WAN aggregation

Apps can be classified by group
(239.1.QOS.x )

Protect latency sensitive Finance Apps
with LLQ

Core
Use MQC to allocate bandwidth to

Data Center Finance Apps

access-list 101 permit ip any 239.1.1.0 0.0.0.63

class-map match-all finance-apps

match access-group 101

policy-map app-llq
WAN Aggregation class finance-apps
prority 1024
class default
fair-queue

interface serial 0
service-policy output app-llq
BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 84
 6500/7600 QoS
Types of Policers - Aggregate
The effect of the Aggregate is that all traffic coming into the ports associated
with the aggregate are policed down the stated rate

Total amount of output

Ingress Aggregate traffic is limited to the
Traffic Policer rate specified in the
Egress Aggregate
Traffic

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 85
 6500/7600 QoS
Types of Policers - Microflow
The effect of the Microflow is that all flows coming into the ports associated
with the Microflow policer are policed down the stated rate

Each flow is limited

Ingress Microflow to the rate specified
Traffic Policer in the Microflow

Egress
Traffic

NOTE:
NOTE:AAflow
flowisisdefined
definedby
bythe
the
Flow
FlowMask
Maskin inuse
useby
bythe
thesystem
system
BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 86
 Microflow policing with multicast
mls qos
access-list 101 permit ip any 239.1.1.0 0.0.0.7
class-map match-all mcast-flows
match access-group 101
policy-map police-mcast-flows
class mcast-flows
police flow mask dest-only 1000000 31250
conform-action transmit exceed-action drop
interface Vlan302
service-policy input police-mcast-flows

All traffic sent to 239.1.1.0 rate limited to 1 Mbps

All traffic sent to 239.1.1.1 rate limited to 1 Mbps
All traffic sent to 239.1.1.2 rate limited to 1 Mbps
All traffic sent to 239.1.1.3 rate limited to 1 Mbps
All traffic sent to 239.1.1.4 rate limited to 1 Mbps
All traffic sent to 239.1.1.5 rate limited to 1 Mbps
All traffic sent to 239.1.1.6 rate limited to 1 Mbps
All traffic sent to 239.1.1.7 rate limited to 1 Mbps
Maximum of 8 Mbps traffic forwarded
BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 87
 Microflow policing with multicast (cont)
mls qos
access-list 101 permit ip any 239.1.1.0 0.0.0.7
class-map match-all mcast-flows
match access-group 101
policy-map police-mcast-flows
class mcast-flows
police flow mask dest-only 1000000 31250
conform-action transmit exceed-action drop
interface Vlan302
service-policy input police-mcast-flows

Micro-flow policers can only be applied to

ingress traffic

NOTE:
Maximum of 63 microflow policers on Sup720
– 63 different policing rates

Only two flow masks are supported per system

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 88
 Multicast Call Admission Control (mCAC)
Define the group ranges:
ip access-list standard one-mb-streams
permit 239.1.1.0 0.0.0.255
ip access-list standard two-mb-streams
permit 239.1.2.0 0.0.0.255
ip access-list standard four-mb-streams
permit 239.1.4.0 0.0.0.255

1 Mbps
4 Mbps
1 Mbps

Set the costs: 1 Mbps

1 Mbps 4 Mbps
1 Mbps 40 Mbps
ip multicast limit cost one-mb-streams 1
ip multicast limit cost two-mb-streams 2
1 Mbps Total
1 Mbps 2 Mbps
ip multicast limit cost four-mb-streams 4
1 Mbps2 Mbps
1 Mbps
2 Mbps
1 Mbps
Work out the allocation:
20 groups X 1 Mbps = 20 Mbps
6 groups X 2 Mbps = 12 Mbps Available:
2 groups X 4 Mbps = 8 Mbps 12.4(15)T4
12.2(33)SXI
40 Mbps 12.2(33)SB
BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 89
 Deploying Multicast CAC
ip multicast limit cost one-mb-streams 1 Corp HQ
ip multicast limit cost two-mb-streams 2
ip multicast limit cost four-mb-streams 4

s0

interface s0

1 Mbps 2 Mbps
1 Mbps 2 Mbps
1 Mbps 4 Mbps
ip multicast limit out one-mb-streams 20

1 Mbps
1 Mbps
ip multicast limit out two-mb-streams 6

1 Mbps
ip multicast limit out four-mb-streams 2

interface s0 40 Mbps
ip multicast limit rpf one-mb-streams 20
ip multicast limit rpf two-mb-streams 6
Total
ip multicast limit rpf four-mb-streams 2
s0

The number of streams at each data rate are

limited by the allocation. Site A

NOTE *,G and S,G will both be accounted

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 90
 Application Traffic – Network approach

Summary
• Addressing plan
• Multicast boundary
• QoS – LLQ and Shaping
• Microflow policing (6500/7600)
• mCAC

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 91
 Receiver
Tracking

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 92
 New
IGMP Explicit Tracking
Displays receiver IP address and interface for IGMPv2 hosts

es1-7606-c3#show ip igmp snooping explicit-tracking vlan 301

Source/Group Interface Reporter Filter_mode

---------------------------------------------------------------------------
0.0.0.0/224.0.1.39 Vl301: 126.1.99.15 EXCLUDE
0.0.0.0/239.254.1.1 Vl301:Gi3/1 126.1.99.36 EXCLUDE
0.0.0.0/239.254.1.4 Vl301:Gi3/1 126.1.99.36 EXCLUDE
0.0.0.0/239.254.1.3 Vl301:Gi3/1 126.1.99.36 EXCLUDE
0.0.0.0/239.254.1.2 Vl301:Gi3/1 126.1.99.36 EXCLUDE
0.0.0.0/239.254.1.5 Vl301:Gi3/1 126.1.99.36 EXCLUDE
0.0.0.0/239.254.1.2 Vl301:Gi3/2 126.1.99.41 EXCLUDE
0.0.0.0/239.254.1.5 Vl301:Gi3/2 126.1.99.41 EXCLUDE
0.0.0.0/239.254.1.3 Vl301:Gi3/2 126.1.99.41 EXCLUDE
0.0.0.0/239.254.1.4 Vl301:Gi3/2 126.1.99.41 EXCLUDE

Available on 6500 in 12.2(33)SXH

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 93
 New
IGMP Explicit Tracking
Displays receiver IP address and interface for IGMPv2 hosts
Host IP Addr
es1-7606-c3#show ip igmp snooping explicit-tracking vlan 301

Source/Group Interface Reporter Filter_mode

---------------------------------------------------------------------------
0.0.0.0/224.0.1.39 Vl301: 126.1.99.15 EXCLUDE
0.0.0.0/239.254.1.1 Vl301:Gi3/1 126.1.99.36 EXCLUDE
0.0.0.0/239.254.1.4 Vl301:Gi3/1 126.1.99.36 EXCLUDE
0.0.0.0/239.254.1.3 Vl301:Gi3/1 126.1.99.36 EXCLUDE
0.0.0.0/239.254.1.2 Vl301:Gi3/1 126.1.99.36 EXCLUDE
0.0.0.0/239.254.1.5 Vl301:Gi3/1 126.1.99.36 EXCLUDE
0.0.0.0/239.254.1.2 Vl301:Gi3/2 126.1.99.41 EXCLUDE
0.0.0.0/239.254.1.5 Vl301:Gi3/2 126.1.99.41 EXCLUDE
0.0.0.0/239.254.1.3 Vl301:Gi3/2 126.1.99.41 EXCLUDE
0.0.0.0/239.254.1.4 Vl301:Gi3/2 126.1.99.41 EXCLUDE

Available on 6500 in 12.2(33)SXH

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 94
 New
IGMP Explicit Tracking
Displays receiver IP address and interface for IGMPv2 hosts
VLAN 301 Physical Int / Switchport
es1-7606-c3#show ip igmp snooping explicit-tracking vlan 301

Source/Group Interface Reporter Filter_mode

---------------------------------------------------------------------------
0.0.0.0/224.0.1.39 Vl301: 126.1.99.15 EXCLUDE
0.0.0.0/239.254.1.1 Vl301:Gi3/1 126.1.99.36 EXCLUDE
0.0.0.0/239.254.1.4 Vl301:Gi3/1 126.1.99.36 EXCLUDE
0.0.0.0/239.254.1.3 Vl301:Gi3/1 126.1.99.36 EXCLUDE
0.0.0.0/239.254.1.2 Vl301:Gi3/1 126.1.99.36 EXCLUDE
0.0.0.0/239.254.1.5 Vl301:Gi3/1 126.1.99.36 EXCLUDE
0.0.0.0/239.254.1.2 Vl301:Gi3/2 126.1.99.41 EXCLUDE
0.0.0.0/239.254.1.5 Vl301:Gi3/2 126.1.99.41 EXCLUDE
0.0.0.0/239.254.1.3 Vl301:Gi3/2 126.1.99.41 EXCLUDE
0.0.0.0/239.254.1.4 Vl301:Gi3/2 126.1.99.41 EXCLUDE

Available on 6500 in 12.2(33)SXH

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 95
 New
User Subscriber rates
Displays total traffic subscribed from one user

Combines information from:

show ip igmp snooping explicit-tracking vlan [vlan]
show ip mroute [group] active

es1-7606-c3#show ip igmp snooping subscriber-rate 126.1.99.37

0.0.0.0/239.254.1.2 Vl301:Gi3/1 126.1.99.37 996 pps/366 kbps (1 sec)
0.0.0.0/239.254.1.1 Vl301:Gi3/1 126.1.99.37 996 pps/366 kbps (1 sec)
0.0.0.0/239.254.1.5 Vl301:Gi3/1 126.1.99.37 1000 pps/368 kbps (1 sec)
0.0.0.0/239.254.1.4 Vl301:Gi3/1 126.1.99.37 1000 pps/368 kbps (1 sec)
0.0.0.0/239.254.1.3 Vl301:Gi3/1 126.1.99.37 1000 pps/368 kbps (1 sec)

--------------------------
Total = 4992 pps/1836 kbps (1 sec)

Available on 6500 in 12.2(33)SXI

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 96
 Agenda

Which PIM Mode ?

General Configuration Notes

RP Engineering

Controlling Groups, Sources &
Receivers

Market Data Feed Forwarding

High Availability Notes

Controlling App Traffic – QoS, Scoping

Receiver Tracking

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 97
 Q and A

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 98
 Meet The Expert

To make the most of your time at Cisco Networkers 2009,

schedule a Face-to-Face Meeting with a top Cisco Expert.

Designed to provide a "big picture" perspective as well as

"in-depth" technology discussions, these face-to-face
meetings will provide fascinating dialogue and a wealth of
valuable insights and ideas.

Visit the Meeting Centre reception desk located in the

Meeting Centre in World of Solutions

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 99
 Recommended Reading
BRKIPM-2261

Source: Cisco Press

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 100
 Multicast at Networkers:

BRKIPM-2261 Deploying IP Multicast

BRKIPM-3010 Advances in Multicast

BRKSEC-2015 Multicast Security

BoF-01 - Multicast BoF

BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 101
BRKIPM-2261 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 102