Multicast Overview


Multicast Overview

Thom Bryant

June 2003


Introduction

• Consistent design recommendation

• Simplification and optimization

CLI and code level

• Quality of Cisco IOS® Software

E2E system testing

Financial test lab


• Internet Technologies Division (ITD) – Central IOS Engineering

• Chief Technology Office (CTO) – Corporate Consulting Engineering

• Customer Advocacy (CA) – Advanced Services

• High Speed Switching Business Unit (HSSBU) – Financial Test Labs

• Network Management Business Unit (NMBU) – Network Management

Cisco Representation


Brief Review–Protocol Independent Multicast MDT Types

• Protocol Independent Multicast (PIM) Sparse-ModeAny version IGMP

SPT or RPT

Unidirectional Trees

MSDP for Inter-domain/Redundancy

• PIM SSMIGMP V3

Source-Only Trees

Simplest Multicast Model – No RPs or MSDP

Unidirectional Trees

• Bidirectional PIMAny version IGMP

Bidirectional Trees-Only (*,G) Routing State


Agenda

• Trends and roadmap

• Addressing and scoping

• Interface Configuration Mode/Auto-RP Listener

• RP Redundancy

• PIM scalability/convergence

• Summary

• Open discussion


INNOVATIONINNOVATION

Self-Healing

Adaptive Routing

Storage Awareness

Self-Healing

Adaptive Routing

Storage Awareness

QoS-Based RoutingQoS-Based Routing

MPLS-VPNsMPLS-VPNsMobile IPMobile IPAToMAToM

Multicast IPMulticast IPNetFlowNetFlow

IPsecIPsec

In-Service-Software-UpgradesIn-Service-Software-Upgrades

Intrusion DetectionIntrusion Detection

IP version 6IP version 6 nBARnBAR

Traffic EngineeringTraffic Engineering Cisco IOS FirewallCisco IOS Firewall SAASAA

Integration: Making IP InnovationBusiness Ready

Application Awareness

Integrated Security

Multicast

Application Awareness

Integrated Security

Multicast

Nonstop ForwardingNonstop Forwarding

Mobility

Packet Core

Expanded Addressing

Mobility

Packet Core

Expanded Addressing


Multicast VPN : MVPN Multicast VPN : MVPN

Many-to-Many : PIM – Bi-DirectionalMany-to-Many : PIM – Bi-Directional

One-to-Many : SSM & IGMP v3One-to-Many : SSM & IGMP v3

Inter-Domain Multicast : MBGP , MSDP, Anycast RP, RGMP, BSRInter-Domain Multicast : MBGP , MSDP, Anycast RP, RGMP, BSR

Reliable Multicast : PGMReliable Multicast : PGM

Basic Multicast : PIM SM, DM, Auto RP, IGMP v2, CGMPBasic Multicast : PIM SM, DM, Auto RP, IGMP v2, CGMP

Multicast v6 : PIM SM, SSM, MLD v2Multicast v6 : PIM SM, SSM, MLD v2

MANAGEMENT

MANAGEMENT

INTEGRATION

INTEGRATION

Provisioning / Accounting / Monitoring Provisioning / Accounting / Monitoring

Access Control / Security Access Control / Security

Multicast Automation / SimplificationMulticast Automation / Simplification

Multicast: Components


Multicast: It Begins and Ends with Applications

1 IP/TV® Audio/Video http://www.cisco.com/warp/public/cc/so/neso/cxne/atsln_an.htm

2 Windows Media

Audio/Video http://www.microsoft.com/windows/windowsmedia/serve/multiwp.asp

3 Real Audio/Video http://videocast.nih.gov/McastUpgrade/multicast.html

4Dialer Conferencing

http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/winxppro/proddocs/dialer_conference_overview.asp

5 NetMeeting Conferencing http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/win98/reskit/part4/wrkc20.asp

6 HootNHoller VOIP http://www.cisco.com/warp/public/cc/so/neso/vvda/hthllr/

7 IPblue VOIP http://www.ipblue.com/faq.htm

8 TIBCO Stock ticker http://www.tibco.com/resources/solutions/technology_solutions/messaging.pdf

9 OrbixTalk Messaging http://techrepublictk.cnet.com/enterprise/0-6119584-720-7723923.html

10 Norton Ghost

File Transferhttp://www.symantec.com/sabu/ghost/ghost_personal/

11 Datarunner File Transfer http://www.targetvision.com/distribu.htm


Finance: Trading FloorsRecent Trends

• Many large financial traders are interested in reducing Operational Expenses (OpEx) and are increasingly interested in Hoot ‘n’ Holler for existing IP infrastructure

• Bidirectional PIM is the protocol that enables a scalable solution, and is going to be deployed in many of these networks

Prudential was our beachhead and is very happy with the cost savings

Royal Bank of Canada is also in the process of deploying Hoot ’n Holler

• Increased interest in PGM for reliable Multicast delivery

• Increased interest in faster convergence and lower downtime for all business critical multicast services


IP Multicast Strategy

• Business Strategy

Maintain leadership in the finance market

Increase deployment in enterprise market segment

Drive adoption in the ISP market segment

Facilitate deployment in MXU for new Multicast services

• Technology Strategy

Maintain IP multicast technology leadership

Add hardware acceleration support and achieve consistency on all key Cisco platforms

Integrate Multicast across different technologies like MPLS, IPsec, IPv6, Mobile, NetFlow and content

Simplify, automate, and increase deployment of Multicast

Enhance scalability, manageability, and security


IP Multicast Platform Roadmap Release Plan (Release 12.0S, 12.2T, and 12.2S)

Key Features:

• mVPN support on GSR

•Multicast v6 – Phase 1 SM, SSM, MLD v2

• New dMFIB for v6

• MBGP support for mcast v6

Targeting Cisco IOS Software Release

12.3(1)T

Key Features:

• Multicast v6 - Phase 1 SM, SSM, MLD v2

• New MFIB for v6

• SSM Mapping

• IP-Mroute-STD MIB

• Multicast Netflow

• Bi-Dir support on C7600

Key Features:

• MSDP Spec 14 compliance

• Inter-AS for mVPN

• SSM Mapping

• Auto-RP Enhancements (no Dense mode fallback)


12.0(26)S


12.2(3rd)S


12.0(27)S


12.2(5th)S

Key Features:

• Mcast-v6 Phase 2

• New dMFIB for v6

• Extranet for mVPN

• Inter-AS for mVPN

• PGM Aware VRF •Auto-RP Enhancements (no Dense mode fallback)

• MSDP Spec 14 compliance

• mVPN MIB

Key Features:

• Multicast v6 - Phase 1 SM, SSM, MLD v2

• New MFIB for v6

• SSM Mapping

• IP-Mroute-STD MIB


Jul2004

May2004

Jun2004

Apr2004

Mar2004

Feb2004

Jan2004

Dec2003

Nov2003

Oct2003

Sep2003

Aug2003

Jul2003

Jun2003

May2003

Apr2003

Mar2003

Feb2003

Aug2004

NB. Confirm target releases with Cisco IOS PM – [email protected]


Agenda




• RP Redundancy


• Summary

• Open discussion


Address Allocation Considerations

• Current and future size of the organization

• Organizational structure and relations between Business Units

• Scale of the IP Multicast deployment

• Internal policies on the control and deployment of network applications

• Scope of the applications

• Security policy

• Readiness for future use of new multicast delivery methods (ie: Bi-Dir PIM and SSM)


IP Multicast Address Space

Start Range End Range Description224.0.0.0 - 224.2.255.255 Assigned224.252.0.0 - 224.255.255.255 Assigned225.0.0.0 - 231.255.255.255 RESERVED232.0.0.0 - 232.255.255.255 Source Specific Multicast Block233.0.0.0 - 233.255.255.255 GLOP Block234.0.0.0 - 238.255.255.255 RESERVED239.0.0.0 - 239.255.255.255 Administratively Scoped Block

IP v4 multicast addresses assigned by IANA

239.0.0.0 - 239.255.255.255 Administratively Scoped [IANA,rfc2365] 239.0.0.0 - 239.191.255.255 Reserved [IANA]239.192.0.0 - 239.251.255.255 Organization-Local Scope [Meyer,rfc2365]239.252.0.0 - 239.254.255.255 Site-Local Scope(reserved)[Meyer,rfc2365]239.255.0.0 - 239.255.255.255 Site-Local Scope [Meyer,rfc2365] 239.255.2.2 rasadv [Thaler]

Administratively scoped IP Multicast address recommendations from rfc 2365


Geographical Scoped Addresses Example

Byte 4

Byte3 Byte2 Byte1 Notes

239 * * * * * * * * * * * * * * * * * * * * * * * * Administrative Scope range RFC2365

239 1 1 * * * * * * * * * * * * * * * * * * * * * * Administrative Organization range RFC2365

239 1 1 0 0 0 0 0 0 * * * * * * * * * * * * * * * * Adm Org. Global addresses

239 1 1 0 0 0 0 0 1 * * * * * * * * * * * * * Adm. Org. Regional assignment

239 * * * * * * * * * * * * * Adm. Org. Regional assignment

• Uses three levels of geographical scoping: Site local

Regional by using the Regional bits

Global

239 255 * * * * * * * * * * * * * Adm. Local Range RFC2365

* * *

* * *1 1 1 1 1 1 1 0

* * *


Geographical and Bandwidth Scoped Addresses Example

Byte 4

Byte3 Byte2 Byte1 Notes

239 * * * * * * * * * * * * * * * * * * * * * * * * Administrative Scope range RFC2365

239 1 1 * * * * * * * * * * * * * * * * * * * * * * Administrative Organization range RFC2365

239 1 1 R R R R R R * * * * * * * * * * * * * * * * Adm. Org. Region expansion

239 1 1 R R R R R R B B B * * * * * * * * * * * * * Adm. Org. Region/BW expansion

239 255 * * * * * * * * * * * * * * * * Administrative Local range RFC2365

239 255 B B B * * * * * * * * * * * * * Adm. Local Bandwidth expansion

• Uses three levels of geographical scoping: Site local

Regional by using the Regional bits

Global

• Use bandwidth bits to define bandwidth scoping in the network


Bandwidth Scoping Example

Bandwidth Bits

Bandwidth Level

#3rd Octet range

Access Lists

0 * *Unlimited Bandwidth

0-127ip access-list standard unlimitedbw permit 239.0.0.0 0.255.255.255

1 0 * High Bandwidth

128-191 ip access-list standard highbw permit 239.0.128.0 0.255.127.255

1 1 0Medium

Bandwidth192-223

ip access-list standard mediumbw permit 239.0.192.0 0.255.63.255

1 1 1Low

Bandwidth224-255 ip access-list standard lowbw

permit 239.0.224.0 0.255.31.255


CampusBackbone

Server Farm

Core

To regionalbackbone

To branch offices (T3)

To remote users(DSL/Cable)

Distribution

ip multicast boundary lowbw

ip multicast boundary mediumbw

ip multicast boundary highbw

Bandwidth Scoping


Agenda




• RP Redundancy


• Summary

• Open discussion


Auto-RP Overview

Announce Announce

An

no

un

ceA

nn

ou

nce

Announce Announce

An

no

un

ceA

nn

ou

nce

Announce

RP-Announcements multicast to theCisco Announce (224.0.1.39) group

AA

CC DDCandidate RP

1.1.1.1Candidate-RP

2.2.2.2

BB

MappingAgent

MappingAgent


CC DD

Discovery

RP-Discoveries multicast to theCisco Discovery (224.0.1.40) group

MappingAgent

MappingAgent

Discovery

Discovery

Dis

cove

ry

Dis

cove

ry

AA

Discovery

Discovery

Dis

cove

ry

Dis

cove

ry

BB

Candidate RP1.1.1.1

Candidate-RP2.2.2.2

Auto-RP Overview


PIM Sparse Mode

PIM Sparse Mode

RP/Mapping AgentC D

A B

On each router: ip multicast-routing

On each interface: ip pim sparse-dense-mode

On routers B and C: ip pim send-rp-announce loopback0 scope 16ip pim send-rp-discovery loopback0 scope 16

RP/Mapping Agent

Simple Auto-RP Configuration


Configuring an Interface for IP Multicast

• Interface Mode Configuration CommandEnables multicast forwarding on the interface

Controls the interface’s mode of operation

ip pim sparse-dense-mode

• Interface mode is determined by the Group modeDense: interface operates in Dense mode

Sparse: interface operates in Sparse mode

• Sparse-dense-mode has potential issues

• Multicast data flows can be flooded as Dense mode if the RP information is lost

• Auto-RP has always required sparse-dense-mode – until now


New Command: Auto-RP Listener

• Global Command

ip pim autorp listener

Allows Auto-RP to work over Sparse-mode interfaces

• Enables AutoRP functions on router.

AutoRP groups operate only in DM

Router joins 224.0.1.40

Off by default

Future: may change to “On” by default

• No possibility of Dense mode flooding without multiple failures in network


Coming Soon to a Router Near You….

• No Dense mode fallback

Default behavior.

No new command required

Use current “Last resort RP=0.0.0.0” approach

Provides limited “disabled group” functionality


Future Plans

• ‘ip pim autorp mapping-agent’ command

New “clearer” parser command

Helps standardize AutoRP & BSR commands

• Format

ip pim autorp mapping-agent <interface> scope <ttl>

• No new code required

Same function as old command


Implementation Summary

ip pim autorp listener

ip pim autorp candidate-rp <interface> scope <ttl>

ip pim autorp mapping-agent <interface> scope <ttl>

ip pim bsr listener

ip pim bsr candidate-bsr [priority <pri>] [hash-length]

ip pim bsr candidate-rp <interface> scope <ttl>

ip pim bsr border


Agenda




• RP Redundancy


• Summary

• Open discussion


RP Redundancy Agenda

• Sparse Mode Redundant RPs

• Bidirectional Redundant RPs

• Unified Redundant RPs


Goals

• Topology independent RP redundancy

• Unified model for Sparse mode and Bidirectional RPs

• Simple configuration


Sparse Mode Anycast RP Configuration

ip pim rp-address 10.0.0.1 ip pim rp-address 10.0.0.1

Interface loopback 0 ip address 10.0.0.1 255.255.255.255

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

Interface loopback 0 ip address 10.0.0.1 255.255.255.255

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

MSDPMSDPBB

RP2

AA

RP1

XX YY


Topology Dependant RP Redundancy

A B

Anycast RP(w w/o) MSDP!!

FE0

FE1

+10 +20

+30

• Router ‘A’ is the primary RP, router ‘B’ is failover

• ‘FE0’ is primary network, ‘FE1’ is failover

• Modify link metrics on ‘A’ and ‘B’ to force routing

• Anycast-RP just for failover, not for load-balancing

• Topology dependant, as ‘B’ can’t be on the path to ‘A’


Bidirectional Phantom RP on a LAN

Source Receiver

1.1.1.21.1.1.3

RP: 1.1.1.1

e0/0 e0/0

e1/0 e1/01.1.3.1 1.1.2.2

core1#show ip pim int e1/0 df

Interface RP DF Winner Metric UptimeEthernet1/0 1.1.1.1 1.1.3.3 0 00:06:49core1#

core2#show ip mroute 225.1.2.3

(*, 225.1.2.3), 00:06:43/00:00:00, RP 1.1.1.1, flags: BC Bidir-Upstream: Ethernet0/0, RPF nbr 1.1.1.1 Outgoing interface list: Ethernet1/0, Forward/Sparse, 00:06:43/now Ethernet0/0, Bidir-Upstream/Sparse, 00:06:43/00:00:00

core2#


Bidirectional Floating Route Phantom RP

RP: 1.1.1.1P

ip multicast-routing!interface Loopback0 ip address 11.0.0.1 255.255.255.255 ip pim sparse-mode!router ospf 11 redistribute static subnets network 10.1.1.0 0.0.0.255 area 0 network 10.1.2.0 0.0.0.255 area 0!ip route 1.1.1.1 255.255.255.255 Loopback0ip pim bidir-enableip pim rp-address 1.1.1.1 bidir-grp bidir

S

ip multicast-routing!interface Loopback0 ip address 11.0.0.2 255.255.255.255 ip pim sparse-mode!router ospf 11 redistribute static subnets network 10.1.1.0 0.0.0.255 area 0 network 10.1.2.0 0.0.0.255 area 0!ip route 1.1.1.0 255.255.255.254 Loopback0ip pim bidir-enableip pim rp-address 1.1.1.1 bidir-grp bidir


Unified Floating Route Phantom RP(Netmask Method)

RP: 1.1.1.2

P

ip multicast-routing!interface Loopback0 ip address 1.1.1.1 255.255.255.252 ip pim sparse-mode ip ospf network point-to-point!router ospf 11 network 1.1.1.0 0.0.0.3 area 0 network 10.1.1.0 0.0.0.255 area 0 network 10.1.2.0 0.0.0.255 area 0!ip pim bidir-enableip pim rp-address 1.1.1.1 sm-grpip pim rp-address 1.1.1.2 bidir-grp bidir

S



Unified Floating Route Phantom RP(Conditional Routing Method)

RP: 1.1.1.2

P


S

ip multicast-routing!interface Loopback0 ip address 1.1.1.1 255.255.255.252 ip pim sparse-mode ip ospf network point-to-point [conditional]!router ospf 11 network 1.1.1.0 0.0.0.3 area 0 [conditional] network 10.1.1.0 0.0.0.255 area 0 network 10.1.2.0 0.0.0.255 area 0!ip pim bidir-enableip pim rp-address 1.1.1.1 sm-grpip pim rp-address 1.1.1.2 bidir-grp bidir


Agenda




• RP Redundancy


• Summary

• Open discussion


0

50

100

Multicast Sub-Second Convergence

Multicast convergence

Time

Previous Environment

Multicast Sub-SecondConvergence

Time

12000

10000

6500

7500

25

75

Seconds

Sub-SecondConvergenc

e

Multicast Sub-Second Convergence provides almost instantaneous recovery of Multicast paths following unicast routing recovery

Platforms


Multicast Scalability - Issues

• Maintaining large amount of state

• Dealing with PIM protocol updates

• Periodic updates to refresh state

• Timers to maintain state

Passive timers

Managed timers

Active timers (timer wheel)


Multicast Sub-Second Convergence

• Enhancement: deliver sub-second convergence and world-class reliability for business-critical multicast applications.

• Problem: reduce the time it takes for Multicast routing to converge after a failure in a large network

• Solution

1. Make Triggered RPF Checks

2. Enhance Timer Management

3. Enhance IGMP Capabilities

4. Make Designated Router Failover in 300 msec

5. Decrease Join/Prune Forwarding Handle Times

6. Make Join/Prune Aggregation


• Join/Prune aggregationUsed to send one PIM packet per (S,G) or (*,G) entry after a Rendezvous Point failover

These are now aggregated into a few PIM packets with multiple entries

• New PIM HELLO optionNew option advertises the hold time in milliseconds

Enables sub-second failover of Designated Router (Cisco proprietary)

• Triggered RPF checks Follows unicast convergence

After unicast is converged, it causes an instantaneous start of RPF checks (previous default was five seconds)

ip pim query-interval <interval> [msec] ip pim query-interval <interval> [msec]

Multicast Sub-Second Convergence: CSCdw13674 PIM scalability & convergence


Agenda




• RP Redundancy


• Summary

• Open discussion


Updated Design Guidance - Summary

• Interface Config ModePIM Sparse Mode

Auto-RP Listener

• RP Mapping and DiscoveryStatic for Deterministic/Change-averse Networks

Auto-RP when a dynamic protocol is needed

• Administrative ScopingStatic

IP Multicast Boundary Filter-Autorp

• RP PlacementCore by default

• RPT or SPT


Updated Design/Reference Documents

• Design Guidelines Update

• Bidirectional Design Guide

• Guidelines for Enterprise IP Multicast Address Allocation

• E2E Test Results

• Multicast VPN Design Guide

• Security (coming soon)


Possible Additional Topics

• Multicast VPN


• Multicast v6

• Reliable Multicast - PGM

• Multicast Security

• Multicast Management and tools

• E2E System Test Results for 12.1(13)

• Financial Test Lab Enhancements

Multicast Overview

Documents

Transcript of Multicast Overview