314 0863_04F9_c7
1
© 1999, Cisco Systems, Inc.
Deploying IP Multicast Session 314
314 0863_04F9_c7
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
2
1
Other Related Presentations • Multicast Sessions Session #
Title
303
Introduction to IP Multicast
306
PIM Protocol Concepts
314
Deploying IP Multicast
320
Advances in IP Multicast
• MBGP Related Sessions Session #
314 0863_04F9_c7
Title
309
Deploying BGP
317
Advanced BGP & Troubleshooting
3
© 1999, Cisco Systems, Inc.
Agenda
Geekometer
• Which Mode? Sparse or Dense • Multicast over Campus Networks • Multicast over NBMA Networks • RP Engineering • Multicast Bandwidth Control • Network Convergence 314 0863_04F9_c7
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
4
2
Which Mode— Sparse or Dense • Dense mode Flood and Prune behavior very inefficient Can cause problems in certain network topologies
Creates (S, G) state in EVERY router Even when there are no receivers for the traffic
Traffic engineering nearly impossible Doesn’t scale as well as Sparse mode
314 0863_04F9_c7
5
© 1999, Cisco Systems, Inc.
Which Mode— Sparse or Dense • Sparse mode One additional configuration step Must configure the RP
Very efficient Uses explicit join model Traffic only flows to were it’s needed Router state only created along flow paths
Traffic engineering possible Use shared-trees rooted at different RP’s
Scales better than dense mode
314 0863_04F9_c7
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
6
3
Which Mode— Sparse or Dense • PIMv2 changes the paradigm for defining a group as sparse or dense • The old way was that the router determined the mode • The new way allows for both sparse and dense groups on a router at the same time
314 0863_04F9_c7
7
© 1999, Cisco Systems, Inc.
Which Mode— Sparse or Dense
• Cisco implements this change with the “ip pim sparse-dense-mode” interface command • If a router knows about an RP the group will be sparse • Otherwise the group will be dense
314 0863_04F9_c7
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
8
4
Which Mode— Sparse or Dense
• Under rare situations you may want to specifically configure an interface to be sparse or dense If you are an ISP If you are connecting to another multicast cloud (i.e., two separate PIM clouds)
314 0863_04F9_c7
9
© 1999, Cisco Systems, Inc.
Which Mode— Sparse or Dense
Recommendation: Sparse-Dense • Mode determined dynamically IF RP exists for group, mode = Sparse ELSE mode = Dense
• Use Auto-RP to define RP(s) Avoids configuring RP on every router Allows easy RP assignment/reassignment
314 0863_04F9_c7
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
10
5
Agenda
• Which Mode? Sparse or Dense • Multicast over Campus Networks • Multicast over NBMA Networks • RP Engineering • Multicast Bandwidth Control • Network Convergence 314 0863_04F9_c7
11
© 1999, Cisco Systems, Inc.
L2 Multicast Frame Switching Problem: Layer 2 Flooding of Multicast Frames PIM
• Typical L2 switches treat multicast traffic as unknown or broadcast and must “flood” the frame to every port • Static entries can sometimes be set to specify which ports should receive which group(s) of multicast traffic
Multicast M
• Dynamic configuration of these entries would cut down on user administration
314 0863_04F9_c7
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
12
6
L2 Multicast Frame Switching Solution 1: IGMP Snooping • Switches become “IGMP” aware • IGMP packets intercepted by the NMP or by special hardware ASICs • Switch must examine contents of IGMP messages to determine which ports want what traffic
PIM
IGMP membership reports IGMP leave messages
• Impact on switch: Must process ALL Layer 2 multicast packets Admin. load increases with multicast traffic load Requires special hardware to maintain throughput
314 0863_04F9_c7
IGMP
IGMP
© 1999, Cisco Systems, Inc.
13
IGMP Messages—Key Points
• Sent to the multicast group address IGMP reports IGMP leaves (old host implementations) IGMP group-specific queries
• Have same L2 headers as data flow IGMP traffic is indistinguishable from data at Layer 2 314 0863_04F9_c7
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
14
7
Typical L2 Switch Architecture Router A 1 LAN Switch
Switching 0 Engine
CPU
CAM Table 2 MAC Address 0000.6503.1d0e
Host 1 314 0863_04F9_c7
3
4
5
Port 5
Host 2
Host 3 Host 4 (0000.6503.1d0e) 15
© 1999, Cisco Systems, Inc.
Typical L2 Switch— 1st Join Router A
LAN Switch
IGMP Report 224.1.2.3
1 (IGMP Snooping Enabled)
Switching 0 Engine
CPU
CAM Table 2 MAC Address 0100.5e01.0203
Entry Added 314 0863_04F9_c7
3
4
5
Ports 0,1,2
Host 1
Host 2
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
Host 3
Host 4 16
8
Typical L2 Switch— 2nd Join Router A
LAN Switch
IGMP Report 224.1.2.3
1 (IGMP Snooping Enabled)
Switching CPU
0 Engine
CAM Table 2 MAC Address 0100.5e01.0203
Host 1
Port Added 314 0863_04F9_c7
3
4
5
Ports 0,1,2 ,5
Host 2
Host 3
Host 4 17
© 1999, Cisco Systems, Inc.
Typical L2 Switch Meltdown! 1.5Mbps !!! Choke, Gasp, Wheeze!!
LAN Switch
Router A 1 (IGMP Snooping Enabled)
Switching CPU
0 Engine 1.5Mbps MPEG Video
CAM Table 2 MAC Address 0100.5e01.0203
3
Host 1 Host 2 (MPEG Server) 314 0863_04F9_c7
4
5
Ports 0,1,2 ,5
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
Host 3
Host 4 18
9
L3 Aware Switch Router A
LAN Switch
1 (IGMP Snooping Enabled)
Switching Engine CPU
0 (w/L3 ASICs)
CAM Table 2 MAC Address 0100.5exx. xxxx
L3 IGMP
Host 1
IGMP Processing Entry 314 0863_04F9_c7
3
4
5
Ports 0
Host 2
Host 3
Host 4 19
© 1999, Cisco Systems, Inc.
L3 Aware Switch 1st Join Router A
LAN Switch
1 (IGMP Snooping Enabled)
Switching Engine CPU
0 (w/L3 ASICs) IGMP Report 224.1.2.3
CAM Table 2 MAC Address 0100.5exx. xxxx 0100.5e01.0203
L3 IGMP !IGMP
Host 1 314 0863_04F9_c7
3
4
5
Ports 0 1,2
Host 2
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
Host 3
Host 4 20
10
L3 Aware Switch 2nd Join Router A IGMP Report 224.1.2.3
1 (IGMP Snooping Enabled)
LAN Switch
Switching Engine 0 (w/L3 ASICs)
CPU
CAM Table 2 MAC Address 0100.5exx. xxxx 0100.5e01.0203
L3 IGMP !IGMP
Host 1
Port Added 314 0863_04F9_c7
3
4
5
Ports 0 1,2 ,5
Host 2
Host 3
Host 4 21
© 1999, Cisco Systems, Inc.
L3 Aware Switch Router A
Ahhh, That’s more like it!
LAN Switch
1 (IGMP Snooping Enabled)
Switching Engine CPU
0 (w/L3 ASICs) 1.5Mbps MPEG Video
CAM Table 2 MAC Address 0100.5exx. xxxx 0100.5e01.0203
L3 IGMP !IGMP
Host 1 314 0863_04F9_c7
3
4
5
Ports 0 1,2 ,5
Host 2
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
Host 3
Host 4 22
11
L2 Multicast Frame Switching Solution 2: CGMP—Cisco Group Multicast Protocol PIM
• Runs on both the switches and the router • Router sends CGMP multicast packets to the switches at a well known multicast MAC address: 0100.0cdd.dddd
• CGMP packet contains : Type field—Join or Leave MAC address of the IGMP client Multicast address of the group
CGMP Commands
IGMP
• Switch uses CGMP packet info to add or remove an entry for a particular multicast MAC address 314 0863_04F9_c7
23
© 1999, Cisco Systems, Inc.
CGMP Basics
IGMP Report Dst MAC = 0100.5e01.0203 Src MAC = 0080.c7a2.1093 Dst IP = 224.1.2.3 Src IP = 192.1.1.1 IGMP Group = 224.1.2.3
CGMP Join 1/1
5/1
1/1
5/1
(a) 314 0863_04F9_c7
USA = 0080.c7a2.1093 GDA = 0100.5e01.0203
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
(b) 24
12
CGMP—1st Join Router A
IGMP Report 224.1.2.3
1 Simple LAN Switch
Switching 0 Engine
CPU
CAM Table 2 MAC Address
3
Host 1 314 0863_04F9_c7
4
5
Ports
Host 2
Host 3
Host 4
0080.c7a2.1093 25
© 1999, Cisco Systems, Inc.
CGMP—1st Join Router A 1 Simple LAN Switch
Switching 0 Engine
CPU
CGMP Join USA 0080.c7a2.1093 GSA 0100.5e01.0204
CAM Table 2 MAC Address 0100.5e01.0203
4
5
Ports 1,2
Entry Added 314 0863_04F9_c7
3
Host 1
Host 2
Host 3
Host 4
0080.c7a2.1093
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
26
13
CGMP 2nd Join Router A
IGMP Report 224.1.2.3
1 Simple LAN Switch
Switching 0 Engine
CPU
CAM Table 2 MAC Address 0100.5e01.0203
Host 1 314 0863_04F9_c7
3
4
5
Ports 1,2
Host 2
Host 3
Host 4
0080.c7b3.2174 27
© 1999, Cisco Systems, Inc.
CGMP 2nd Join Router A 1 Simple LAN Switch
Switching 0 Engine
CPU
CGMP Join USA 0080.c7b3.2174 GSA 0100.5e01.0204
CAM Table 2 MAC Address 0100.5e01.0203
Port Added 314 0863_04F9_c7
3
4
5
Ports 1,2,5
Host 1
Host 2
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
Host 3
Host 4
0080.c7b3.2174 28
14
CGMP No Load on Switch Router A 1 Simple LAN Switch
Switching 0 Engine
CPU
1.5Mbps MPEG Video
CAM Table 2 MAC Address 0100.5e01.0203
314 0863_04F9_c7
3
4
5
Ports 1,2,5
Host 1 Host 2 (MPEG Server)
Host 3
Host 4
© 1999, Cisco Systems, Inc.
29
Summary—Frame Switches • IGMP snooping Switches with Layer 3 aware ASICs High-throughput performance maintained Increases cost of switches
Switches without Layer 3 aware ASICs Suffer serious performance degradation
• CGMP Requires Cisco routers and switches Can be implemented in low-cost switches 314 0863_04F9_c7
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
30
15
Design Issue— Server Location
Multicast Traffic Being Dropped!!! Unnecessary Traffic!!! Catalyst 5000 VLAN1
VLAN2
VLAN3
Catalyst 29xx Catalyst 29xx
Catalyst 29xx
Video Server 314 0863_04F9_c7
31
© 1999, Cisco Systems, Inc.
Design Issue— Server Location
Multicast Traffic Still Being Dropped!!! Video Server
Catalyst 5000 VLAN1
Catalyst 29xx
VLAN2
Catalyst 29xx
VLAN3
Catalyst 29xx
• Keep high B/W sources close to router 314 0863_04F9_c7
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
32
16
Design Issue—Core Switch Video Server
Router A
7500 1.5MB MPEG Video Streams
Holy Multicast, Batman!! 3MB of unwanted data! (Choke, gasp, wheeze!)
Unnecessary Multicast Traffic !!!
T1 2500 2500
Catalyst 5000
Router B
7500
314 0863_04F9_c7
7500
Unnecessary Multicast Traffic !!!
Receiver Group 1
WAN
Router D
Router C
Receiver Group 2 33
© 1999, Cisco Systems, Inc.
Design Issue—Core Switch Video Server
Router A
7500
T1
1.5MB MPEG Video Streams
2500 2500
Router-D
Move WAN Router to Another VLAN Segment Inside of Catalyst 5000
Catalyst 5000
Router B
Receiver Group 1 314 0863_04F9_c7
7500
WAN
7500
Unnecessary Multicast Traffic !!!
Router C
Receiver Group 2
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
34
17
Design Issue— 224.0.0.x Flooding Router A
OSPF Hello (224.0.0.5)
1 LAN Switch
Switching 0 Engine
CPU
CAM Table 2 MAC Address
Host 1 314 0863_04F9_c7
3
4
5
Ports
Router B
Router C
Router D 35
© 1999, Cisco Systems, Inc.
Design Issue— 224.0.0.x Flooding Router A
IGMP Report 224.0.0.5
1 LAN Switch
Switching 0 Engine
CPU
CAM Table 2 MAC Address 0100.5e00.0005
Entry Added 314 0863_04F9_c7
3
4
5
Ports 2
Host 1
Router B
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
Router C
Router D 36
18
Design Issue— 224.0.0.x Flooding Router A
OSPF Hello (224.0.0.5)
1 LAN Switch
Switching 0 Engine
CPU
CAM Table 2 MAC Address 0100.5e00.0005
3
Host 1 314 0863_04F9_c7
4
5
Ports 2
Router B
Router C
Router D 37
© 1999, Cisco Systems, Inc.
Design Issue— Address Overlap Layer 3 IPmc Address Mapping to Layer 2 Multicast Address (FDDI and Ethernet) 32 Bits 1110 5 Bits Lost
28 Bits
239.255.0.1
01-00-5e-7f-00-01 25 Bits
23 Bits 48 Bits
Be Aware of the Overlap of Layer 3 Addresses to Layer 2 Addresses 314 0863_04F9_c7
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
38
19
Design Issue— Address Overlap
32 - IP Multicast Addresses 224.1.1.1 224.128.1.1 225.1.1.1 225.128.1.1 . . . 238.1.1.1 238.128.1.1 239.1.1.1 239.128.1.1 314 0863_04F9_c7
1 - Multicast MAC Address
0x0100.5E01.0101
39
© 1999, Cisco Systems, Inc.
Design Issue— Address Overlap Try to Avoid Addresses that Must Be Flooded 32 - IP Multicast Addresses 224.0.0.x 224.128.0.x 225.0.0.x 225.128.0.x . . . 238.0.0.x 238.128.0.x 239.0.0.x 239.128.0.x 314 0863_04F9_c7
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
1 - Multicast MAC Address
0x0100.5E00.00xx
40
20
Summary—Design Issues • Pay attention to campus topology Be aware of unwanted flooding over trunks
• Use IGMP snooping and/or CGMP Neither can solve all L2 flooding issues To solve all problems requires router/switch
• 224.0.0.x flooding Watch out for switches that don’t flood 224.0.0.x traffic
• Address overlap Select group addresses to avoid L2 overlap Avoid x.0.0.x group addresses when possible 314 0863_04F9_c7
41
© 1999, Cisco Systems, Inc.
Multicast over ATM LANE Core
BUS
Unwanted Data!!! Source 314 0863_04F9_c7
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
Member 42
21
Multicast over ATM LANE Core Make Sure Your BUS Device Can Handle the Maximum Expected Load!
BUS
1.5Mbit MPEG Video Source 314 0863_04F9_c7
Make Sure Your ATM Switches Can Replicate Cells at this Rate!
Member 43
© 1999, Cisco Systems, Inc.
Multicast over ATM LANE Core • Avoid using a single device as BUS for multiple ELANs
Why do I have to do all the work?! ELAN 1
ELAN 2
BUS
ELAN 3 314 0863_04F9_c7
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
44
22
Multicast over ATM LANE Core • Design issues BUS horsepower is critical Use separate BUS device per ELAN to reduce load Overloaded BUS = cell/packet loss and jitter/delay Can cause problems on multimedia conferences
ATM switch cell replication rate is critical Switches that replicate cells in hardware are best
Add lots of bandwidth to ATM fabric Traffic will frequently be sent where it’s unwanted ATM core bandwidth will be wasted
• P2MP VCs may be a better solution 314 0863_04F9_c7
45
© 1999, Cisco Systems, Inc.
Agenda
• Which Mode? Sparse or Dense • Multicast over Campus Networks • Multicast over NBMA Networks • RP Engineering • Multicast Bandwidth Control • Network Convergence 314 0863_04F9_c7
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
46
23
How Routers See NBMA at L3 Central Site Router S0
Layer 3 Viewpoint
.1
Interface S0 ip address 192.1.1.1 255.255.255.0 ip pim sparse-dense-mode
192.1.1.0/24
S0
314 0863_04F9_c7
.2
.3
S0
.4
S0
.5
S0
Remote Site Routers
47
© 1999, Cisco Systems, Inc.
How Routers See NBMA at L3 Central Site Router
Interface S0 ip address 192.1.1.1 255.255.255.0 dlci dlci dlci dlci
10 11 12 13
t
lC irc ui t
rc al Ci uit
S0
ua
ui
192.1.1.0/24 rt
314 0863_04F9_c7
.2
a
rc
Layer 2 Reality
.1
Vi
S0
rtu
i lC
S0
Virtu
Vi
broadcast broadcast broadcast broadcast
uit
192.1.1.2 192.1.1.3 192.1.1.4 192.1.1.5
lC irc
map map map map
tua
frame-relay frame-relay frame-relay frame-relay
Vir
ip ip ip ip
.3
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
S0
.4
S0
.5
Remote Site Routers
48
24
How Routers See NBMA at L3 Central Site Router S0 (*, 224.1.1.1), 00:00:12/00:00:00, RP 10.1.1.1, flags: S Incoming interface: Null, RPF nbr 0.0.0.0 Outgoing interface list: Serial0, Forward/Sparse, 00:00:12/00:02:48
(*, G) Join S0
.2
S0
192.1.1.0/24
(*, G) Join
.3
Layer 3 Viewpoint
.1
S0
(*, G) Join
.4
S0
.5
Remote Site Routers
Members 314 0863_04F9_c7
49
© 1999, Cisco Systems, Inc.
How Routers See NBMA at L3 Central Site Router E0
Source
S0
Layer 3 Viewpoint
.1
192.1.1.0/24
S0
.2
S0
.3
S0
.4
S0
.5
Remote Site Routers
Members 314 0863_04F9_c7
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
50
25
How Routers See NBMA at L3 Central Site Router E0
Source
S0
Layer 2 Reality
.1
192.1.1.0/24
• Router has to use pseudo broadcast to replicate packets in Layer 2 code
Unwanted! S0
.2
S0
.3
S0
.4
S0
.5
• Packets go where they are not wanted • Process switched! 314 0863_04F9_c7
Remote Site Routers
Members 51
© 1999, Cisco Systems, Inc.
DM Problem with Partial Mesh Central Site Router E0
Source
S0
Layer 3 Viewpoint
.1
192.1.1.0/24
(S, G) Prune S0
.2
S0
.3
S0
.4
S0
.5
Remote Site Routers
Members 314 0863_04F9_c7
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
52
26
DM Problem with Partial Mesh Central Site Router Not Heard by the Other Remote Site Routers!!!
E0
Source
S0
Layer 2 Reality
.1
192.1.1.0/24 (S, G) Prune
• Other routers will not override the prune
S0
.2
S0
.3
S0
.4
S0
.5
Members 314 0863_04F9_c7
53
© 1999, Cisco Systems, Inc.
DM Problem with Partial Mesh Central Site Router E0
Source
S0
Layer 2 Reality
.1
192.1.1.0/24
S0
.2
S0
.3
S0
.4
S0
.5
• (S, G) traffic is shut off ! Members 314 0863_04F9_c7
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
54
27
NBMA Mode
• Solution: PIM-SM + NBMA mode ip pim nbma-mode
• Requires sparse mode • When router receives join, it puts the interface and joiner in the outgoing interface list (OIL) • When router receives a prune, it removes the interface/joiner from OIL 314 0863_04F9_c7
55
© 1999, Cisco Systems, Inc.
NBMA Mode Avoiding Pseudo Broadcast by Using ‘ip pim nbma-mode’ Central Site Router S0
.1
192.1.1.0/24
Interface S0 ip address 192.1.1.1 255.255.255.0 ip pim sparse-dense-mode ip pim nbma-mode
S0
314 0863_04F9_c7
.2
S0
.3
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
S0
.4
S0
.5
Remote Site Routers
56
28
NBMA Mode Avoiding Pseudo Broadcast by Using ‘ip pim nbma-mode’ Central Site Router S0
.1
192.1.1.0/24
(*, G) Join S0
314 0863_04F9_c7
.2
S0
(*, G) Join (*, G) Join
.3
S0
.4
S0
.5
Remote Site Routers
Members 57
© 1999, Cisco Systems, Inc.
NBMA Mode Avoiding Pseudo Broadcast by Using ‘ip pim nbma-mode’ Central Site Router S0
.1
192.1.1.0/24 (*, 224.1.1.1), 00:03:23/00:00:00, RP 10.1.1.1, flags: S Incoming interface: Ethernet0, RPF nbr 10.1.1.1 Outgoing interface list: Serial0, 192.1.1.2, Forward/Sparse, 00:00:12/00:02:48 Serial0, 192.1.1.3, Forward/Sparse, 00:03:23/00:01:36 Serial0, 192.1.1.4, Forward/Sparse, 00:00:48/00:02:12
S0
314 0863_04F9_c7
.2
S0
.3
S0
.4
S0
.5
Remote Site Routers
Members © 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
58
29
NBMA Mode Avoiding Pseudo Broadcast by Using ‘ip pim nbma-mode’ Central Site Router E0
Source
S0
.1
192.1.1.0/24
• Router can now replicate packets in Layer 3 code • Packets only go where needed
S0
.2
S0
.3
S0
.4
S0
.5
Remote Site Routers
• Fast switched! 314 0863_04F9_c7
Members 59
© 1999, Cisco Systems, Inc.
ATM P2MP Broadcast VCs • What if WAN media could do native multicast ATM can perform the broadcast/multicast packet replication task via p2mp VCs
• Answer: ATM multipoint-signalling One p2mp VC handles any and all outgoing broadcast and multicast traffic Sends N copies to N neighbors out of K interested parties (not optimal) 314 0863_04F9_c7
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
60
30
ATM NBMA Cloud w/P2MP Broadcast VCs • Each PVC is p2p on a multipoint (sub)interface • Router Backbone - p2mp VCs do all broadcast/ multicast replication instead of the router • Use any PIM mode
A A
• Suboptimal multicast solution
ATM NBMA Cloud
B B
• Fast switched! Member
C C
D D
Member Note: Only VCs for Router A shown 314 0863_04F9_c7
© 1999, Cisco Systems, Inc.
61
ATM Multipoint Signalling
• Commands: atm multipoint-signalling
• Requires “broadcast”keyword on all ATM map-list statements atm map-list mumble ip x.x.x.x atm-nsap xxxx.xxxx… broadcast ip y.y.y.y atm-nsap yyyy.yyyy… broadcast
314 0863_04F9_c7
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
62
31
ATM P2MP VC per Group
• What if each group had it’s own p2mp VC NBMA-mode solved sending K copies to K interested parties out of N neighbors A p2mp VC/Group can solve sending one copy to K interested parties out of N neighbors
• Answer: Use PIM multipoint-signalling
314 0863_04F9_c7
63
© 1999, Cisco Systems, Inc.
ATM NBMA Cloud with P2MP VC/Group • One p2mp VC per group performs multicast replication instead of the router
A A
ATM NBMA Cloud
• Broadcast p2mp VC used when # groups > max p2mp VC count • Use PIM sparse mode
B B
C C
• p2mp VCs map group membership • Fast Switched!
Note: Only p2mp multicast VCs for Router A shown for clarity 314 0863_04F9_c7
D D
Member
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
Member
Member
Member 64
32
ATM P2MP VC per Group ( Cont.)
• Algorithm: Similar to NBMA mode Rather than putting interface/joiner in olist, put joiner on multipoint VC Received joins cause UNI signaling ADD-PARTYs Received prunes cause UNI signaling DROP-PARTYs
• Use a VC count threshold to keep down the number of VCs opened Use shared multipoint VC and fanout as tie breaker
314 0863_04F9_c7
© 1999, Cisco Systems, Inc.
65
ATM P2MP VC per Group ( Cont.)
• Commands: ip pim multipoint-signaling ip pim vc-count
ip pim minimum-vc-rate
• Good for ATM networks used as router core LIS ATM Network must support SVC’s Routers must have ATM map statements to all other routers Need the shared broadcast p2mp VC Otherwise uses pseudo-broadcast (ugh!)
314 0863_04F9_c7
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
66
33
Agenda
• Which Mode? Sparse or Dense • Multicast over Campus Networks • Multicast over NBMA Networks • RP Engineering • Multicast Bandwidth Control • Network Convergence 314 0863_04F9_c7
© 1999, Cisco Systems, Inc.
67
Auto-RP Fundamentals
• Candidate RPs Configured via global config command ip pim send-rp-announce scope [group-list acl]
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> 314 0863_04F9_c7
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
68
34
Auto-RP Fundamentals • Mapping agents Configured via global config command ip pim send-rp-discovery scope
Receive RP-Announcements Select highest C-RP IP addr as RP for group range Stored in Group-to-RP Mapping Cache with holdtimes
Multicast RP-Discovery messages Sent to Cisco-Discovery (224.0.1.40) group Sent every 60 seconds or when changes detected
RP-Discovery messages contain: Contents of MA’s Group-to-RP Mapping Cache 314 0863_04F9_c7
© 1999, Cisco Systems, Inc.
69
Auto-RP Fundamentals
• All Cisco routers Join Cisco-Discovery (224.0.1.40) group Automatic No configuration necessary
Receive RP-Discovery messages Stored in local Group-to-RP Mapping Cache Information used to determine RP for group range
314 0863_04F9_c7
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
70
35
Simple Auto-RP Configuration
RP/Mapping Agent A
B
PIM Sparse Mode C RP/Mapping Agent
D
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 16 ip pim send-rp-discovery scope 16 314 0863_04F9_c7
71
© 1999, Cisco Systems, Inc.
C-RP 1.1.1.1
C C
Announce
Announce
Announce
MA B B
Announce
Announce
MA A A
D D Announce
Announce
Auto-RP—From 10,000 Feet
Announce
C-RP 2.2.2.2
RP-Announcements multicast to the Cisco Announce (224.0.1.39) group Announce 314 0863_04F9_c7
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
72
36
Dis cov ery
B B Disc over y
C C
MA
Dis cov ery
Disc ove ry
C-RP 1.1.1.1
Disc ove ry
MA A A
Disc over y
Disc ove ry
Auto-RP—From 10,000 Feet
Disc ove ry
D D
C-RP 2.2.2.2
RP-Discoveries multicast to the Cisco Discovery (224.0.1.40) group Discovery 314 0863_04F9_c7
73
© 1999, Cisco Systems, Inc.
Auto-RP—A Closer Look MA
A
C-RP 1.1.1.1
Rtr-A# show ip pim rp mapping This system is an RP-mapping agent
C
C-RP 2.2.2.2
D
Initial Cache State in the Mapping Agent 314 0863_04F9_c7
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
74
37
Auto-RP—A Closer Look MA
A 4 0/ 0. 0. 4. 2 2 = ec 1 .1. nge 0 s ce n 1.1 a 18 = p-R e = nou RP rou tim An G old H
C-RP 1.1.1.1
C
314 0863_04F9_c7
C-RP 2.2.2.2
Rtr-A# show ip pim rp mapping This system is an RP-mapping agent Group(s) 224.0.0.0/4, uptime: 00:00:15, expires: 00:02:45 RP 1.1.1.1 ( Rtr-C), PIMv1 Info source: 1.1.1.1 ( Rtr-C)
D
75
© 1999, Cisco Systems, Inc.
Auto-RP—A Closer Look MA
A R G P Ho rou = 2. ld p- 2.2 tim R .2 An e = ang no 1 e= un 80 s 22 ce ec 4.0 .0 .0 /4
C-RP 1.1.1.1
C
Rtr-A# show ip pim rp mapping This system is an RP-mapping agent Group(s) 224.0.0.0/4, uptime: 00:00:04, expires: 00:02:56 RP 2.2.2.2 ( Rtr Rtr-D) -D), PIMv1 Info source: 2.2.2.2 ( Rtr Rtr-D) -D)
C-RP 2.2.2.2
D
C-RP with Highest Address Is Selected as RP and Stored in Cache 314 0863_04F9_c7
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
76
38
Auto-RP—A Closer Look All Mapping Agents Must Have Consistent Data !
MA
MA
A
B
172.16.2.1
172.16.2.2 Rtr-B# show ip pim rp mapping This system is an RP-mapping agent
Rtr-A# show ip pim rp mapping This system is an RP-mapping agent
Group(s) 224.0.0.0/4, uptime: 00:00:04, expires: 00:02:56 RP 2.2.2.2 (Rtr-D), (Rtr-D) PIMv1 Info source: 2.2.2.2 (Rtr-D)
Group(s) 224.0.0.0/4, uptime: 00:00:04, expires: 00:02:56 RP 2.2.2.2 (Rtr-D), (Rtr-D) PIMv1 Info source: 2.2.2.2 (Rtr-D)
X 314 0863_04F9_c7
77
© 1999, Cisco Systems, Inc.
Auto-RP—A Closer Look Local Cache Initially Loaded from Router “B” MA
A
Rtr-X# show ip pim rp mapping
MA
Group(s) 224.0.0.0/4, uptime: 00:00:04, expires: 00:02:56 RP 2.2.2.2 ( Rtr-D), PIMv1 Info source: 172.16.2.2 (Rtr-B)
B 172.16.2.2
R D G P = isc Ho rou 2.2. ove ldt p-R 2.2 ry im an e = ge 18 = 2 0 s 24 ec .0. 0.0 /4
172.16.2.1
X 314 0863_04F9_c7
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
78
39
Auto-RP—A Closer Look Identical Info Received from Router “A” Rtr-X# show ip pim rp mapping
MA
MA
Group(s) 224.0.0.0/4, uptime: 00:00:04, expires: 00:02:56 RP 2.2.2.2 ( Rtr-D), PIMv1 Info source: 172.16.2.1 (Rtr- A)
A 172.16.2.1
B 172.16.2.2
y er /4 ov 0.0 sc .0. Di 24 =2 c 2 .2. ge se 2.2 n 0 = -Ra = 18 RP oup ime Gr oldt H
• “Info source” will continue to flip-flop between routers A and B • No performance impact X
314 0863_04F9_c7
79
© 1999, Cisco Systems, Inc.
Auto-RP Announcement Scope RP Announcements Leaking Outside of Network
PIM Sparse Mode Network scope 16
scope 16 C Candidate-RP A Mapping Agent
B Mapping Agent
RP Announcements Not Reaching this Map Agent
314 0863_04F9_c7
Network Diameter = 32 Hops © 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
80
40
Auto-RP Announcement Scope RP Announcements (224.0.1.39) Blocked from Leaving/Entering the Network Using ‘ip multicast boundary’ Commands
scope 32
scope 32
PIM Sparse Mode Network
A Mapping Agent
B Mapping Agent
C Candidate-RP
314 0863_04F9_c7
Both Mapping Agents Are Now Receiving Announcements from the Candidate RP Network Diameter = 32 Hops 81
© 1999, Cisco Systems, Inc.
Auto-RP Discovery Scope RP Discovery Messages Leaking Outside of Network RP Discovery Messages Not Reaching this Router (Assumes All Groups Are Dense Mode) scope 16
D
314 0863_04F9_c7
scope 16 A Mapping Agent
PIM Sparse Mode Network
Network Diameter = 32 Hops © 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
82
41
Auto-RP Discovery Scope RP Discoveries (224.0.1.40) Blocked From Leaving/entering the Network Using ‘ip multicast boundary’ Commands
RP Discovery Messages Now Reaching this Router
scope 32
D
314 0863_04F9_c7
scope 32 A Mapping Agent
PIM Sparse Mode Network
Network Diameter = 32 Hops 83
© 1999, Cisco Systems, Inc.
Constraining Auto-RP Messages Need to Block Auto-RP Discovery (224.0.1.40) and Announcement (224.0.1.39) Messages from Entering/Leaving the Network
Boundary Router scope 32
scope 32
scope 32
C Candidate-RP
314 0863_04F9_c7
S0
scope 32 A Mapping Agent Interface S0 ip multicast boundary 10
PIM Sparse Mode Network
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
access-list 10 deny 224.0.1.39 access-list 10 deny 224.0.1.40 access-list 10 permit any
84
42
PIMv2 BSR Fundamentals • Candidate RPs Configured via global config command ip pim rp-candidate [group-list acl]
Unicast PIMv2 C-RP messages to BSR Learns IP address of BSR from BSR messages Sent every rp-announce-interval (default: 60 sec)
C-RP messages contain: Group Range (default = 224.0.0.0/4) Candidate’s RP address Holdtime = 3 x <rp-announce-interval> 314 0863_04F9_c7
© 1999, Cisco Systems, Inc.
85
PIMv2 BSR Fundamentals • Bootstrap router (BSR) Receive C-RP messages Accepts and stores ALL C-RP messages Stored in Group-to-RP Mapping Cache w/holdtimes
Originates BSR messages Multicast to All-PIM-Routers (224.0.1.13) group (Sent with a TTL = 1)
Sent out all interfaces. Propagate hop-by-hop Sent every 60 seconds or when changes detected
BSR messages contain: Contents of BSR’s Group-to-RP Mapping Cache IP Address of active BSR 314 0863_04F9_c7
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
86
43
PIMv2 BSR Fundamentals • Candidate bootstrap router (C-BSR) Configured via global config command ip pim bsr-candidate [priority <pri>]
Determines IP address
Sets RP selection hash mask length
<pri> Sets the C-BSR priority (default = 0)
C-BSR with highest priority elected BSR C-BSR IP address used as tie-breaker (Highest IP address wins)
The active BSR may be preempted New router w/higher BSR priority forces new election 314 0863_04F9_c7
© 1999, Cisco Systems, Inc.
87
PIMv2 BSR Fundamentals • BSR election mechanism C-BSR’s: Begin in Candidate-BSR state BSR-Timeout timer started (150 seconds) If higher priority (preferred) BSR message received Restart timer and forward BSR message
Copy info to local Group-to-RP mapping cache Otherwise, discard BSR message
If timer expires, transition to Elected-BSR state
While in Elected-BSR state Periodically originate own BSR messages Include local Group-to-RP mapping cache in msg
Return to Candidate-BSR state if preferred BSR message (higher priority) received 314 0863_04F9_c7
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
88
44
PIMv2 BSR Fundamentals
• BSR election mechanism Non C-BSRs (i.e., all other routers): Start in Accept-Any state Accepts first BSR message received Saves BSR info and forwards BSR message Transitions to Accept-Preferred state
While in Accept-Preferred state Starts BSR-Timeout timer Only accept and forward preferred BSR messages (I.e., BSR messages with priority > current BSR priority)
Otherwise, discard BSR message Return to Accept-Any state if timer expires 314 0863_04F9_c7
© 1999, Cisco Systems, Inc.
89
PIMv2 BSR Fundamentals
• All PIMv2 routers Receive BSR messages Stored in local Group-to-RP Mapping Cache Information used to determine active BSR address
Selects RP using Hash algorithm Selected from local Group-to-RP Mapping Cache All routers select same RP using same algorithm Permits RP-load balancing across group range
314 0863_04F9_c7
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
90
45
Basic PIMv2 BSR
G BSR Msgs
PIMv2 Sparse Mode BSR Msgs
BSR
F BSR Msgs
A BSR Msgs
D
nt me se rti ) e t v Ad icas RP (un C-
C-RP
CRP
Ad (u vert ni ca isem st en ) t
B
C
C-RP
E BSR Msgs Flooded Hop-by-Hop 314 0863_04F9_c7
91
© 1999, Cisco Systems, Inc.
Constraining BSR Messages Need to Block All BSR Message from Entering/Leaving Network Border Router S0
Neighboring PIMv2 Domain
A
PIMv2 Sparse Mode Network BSR Msgs
BSR Msgs BSR
Interface S0 . . ip pim border
314 0863_04F9_c7
Need to Block All BSR Message from Entering/Leaving Network
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
Border Router B
S0
Neighboring PIMv2 Domain
Interface S0 . . ip pim border
92
46
Understanding Accept-RP • Accept-RP Command Global configuration command ip pim accept-rp <rp-address> [] ip pim accept-rp Auto-rp [] ip pim accept-rp 0.0.0.0 []
Multiple commands accepted Command list sorted in order shown above Only one Auto-RP and one 0.0.0.0 (wildcard) accepted Omitting ACL implies 224.0.0.0/4 group range
Search Rules Top down search Stop on RP address match—Apply ACL and exit Exception: Auto-RP denies RP/Group Apply 0.0.0.0 (wildcard) entry (if it exists) 314 0863_04F9_c7
© 1999, Cisco Systems, Inc.
93
Understanding Accept-RP
• Accept-RP Command Usage Case 1 — Controlling Group mode Case 2 — Accepting (*, G) joins Case 3 — Accepting PIM registers at the RP
314 0863_04F9_c7
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
94
47
Accept-RP—Case 1 Controlling Group Mode Router Has No State for Group G IGMP Join (G)
Accept-RP Filter List
Search
Group Group Address Address
314 0863_04F9_c7
Groupto-RP Mapping Cache
Group Group Address, Address, RP RP Address Address
State Creation Engine
Permit Permit
Sparse Sparse Mode Mode
95
© 1999, Cisco Systems, Inc.
Accept-RP—Case 2 Accepting (*, G) Joins (*, G) Join Messages Contain the RP Address
A A
(*, G) Join B B
Accept-RP Filter List
Group Group Address Address RP RP Address Address
314 0863_04F9_c7
Join Processing Engine
RP RP Address Address
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
Process Process Join Join
96
48
Accept-RP—Case 3 Accepting PIM Registers at the RP Unicast to One of A’s Interface Addresses
(S, G) Register
Source “S”
B B
A A
Accept-RP Filter List
Group Group Address, Address, Interface Interface Address Address
314 0863_04F9_c7
RP
RP Processing Engine
Permit Permit
RP
Accept Accept the the Register Register
97
© 1999, Cisco Systems, Inc.
RP Placement • Q: “Where do I put the RP?” A: “Generally speaking, it’s not critical”
• SPT’s are normally used by default RP is a place for source and receivers to meet Traffic does not normally flow through the RP RP is therefore not a bottleneck
• Exception: SPT-Threshold = Infinity Traffic stays on the shared tree RP could become a bottleneck 314 0863_04F9_c7
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
98
49
RP Performance Considerations • CPU load factors RP must process Registers RP must process Shared-tree Joins/Prunes RP must send periodic SPT Joins toward source PIM performs RPF recalculation every 5 seconds Watch the total number of mroute table entries in the RP
Shared-tree forwarding Only when spt-threshold = infinity is in use
• Memory load factors (*, G) entry ~ 260 bytes + OIL size (S, G) entry ~ 212 bytes + OIL size Outgoing interface list (OIL) size Each oil entry ~ 80 bytes 314 0863_04F9_c7
© 1999, Cisco Systems, Inc.
99
Dealing with Overloaded RP’s
• Increase CPU horsepower • Increase memory • Use SPTs if not already • Split RP load across several RPs RPs!!
314 0863_04F9_c7
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
100
50
Agenda
• Which Mode? Sparse or Dense • Multicast over Campus Networks • Multicast over NBMA Networks • RP Engineering • Multicast Bandwidth Control • Network Convergence 314 0863_04F9_c7
101
© 1999, Cisco Systems, Inc.
BW Control via Rate-Limiting • Rate limit interface command ip multicast rate-limit in | out { [video] | [whiteboard] } [group-list ] [source-list ] []
Multiple entries may be used per interface
• Brute-force limits Use “out” form of command on WAN links Set to desired percentage usage of link BW Group and/or Source ACLs provide more granularity
• Limiting video or whiteboard streams Add “video” or “whiteboard” keywords Requires ‘ip sdr listen’ to be enabled Streams identified using info from sdr cache 314 0863_04F9_c7
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
102
51
BW Control via Admin-Scoping • Limit high-BW source to local site • Use administratively-scoped zones Simple scoped zone example: 239.255.0.0/16 = Site-Local Scope Zone 239.192.0.0/10 = Org.-Local Scope Zone 224.0.1.0 - 238.255.255.255 = Global scope (Internet) zone
High-BW sources use only site-local zone groups Med.-BW, org-wide sources use org.-local zone Low-Med. BW, Internet-wide sources use global zone 314 0863_04F9_c7
103
© 1999, Cisco Systems, Inc.
BW Control via Admin-Scoping Site A (HQ) AS Border
To Internet S0
Site Local RP/MA
Border A
S1
S0
T1
T1
S0
S0
Border B
Border C
Site Local RP/MA
Site B (LA) 314 0863_04F9_c7
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
Site Local RP/MA
Site C (ATL) 104
52
BW Control via Admin-Scoping Site A (HQ) AS Border
To Internet S0
Site Local RP/MA
Org-Local Boundary
Border A
S0
Site-Local Boundaries
S1
Site-Local Boundaries
T1
T1
S0
S0
Border B
Border C
Site Local RP/MA
Site Local RP/MA
Site B (LA) 314 0863_04F9_c7
Site C (ATL) 105
© 1999, Cisco Systems, Inc.
BW Control via Admin-Scoping Site A (HQ) AS Border
To Internet Interface Serial0 . . . ip multicast ttl-threshold 16 ip multicast boundary 10
S0
Site Local RP/MA
access-list 10 deny 239.255.0.0 0.0.255.255 Border A access-list 10 permit any
access-list 10 deny 239.255.0.0 0.0.255.255 access-list 10 permit any
T1
T1
S1
S0
Interface Serial0 . . . ip multicast ttl-threshold 16 ip multicast boundary 10
S0
S0
Border B
Border C
Site Local RP/MA
Site B (LA) 314 0863_04F9_c7
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
Site Local RP/MA
Site C (ATL) 106
53
BW Control via Admin-Scoping Site A (HQ) AS Border
To Internet S0
Site Local RP/MA
Border A
S1
S0
S0
Interface Serial0 . . . ip multicast ttl-threshold 16 ip multicast boundary 10
T1
T1 S0
Border B
Border C
Interface Serial1 . . . ip multicast ttl-threshold 16 ip multicast boundary Site 10 Local
Site Local RP/MA
RP/MA
access-list 10 deny 239.255.0.0 0.0.255.255 access-list 10 permit any
Site B (LA)
314 0863_04F9_c7
Site C (ATL) 107
© 1999, Cisco Systems, Inc.
BW Control via Admin-Scoping Site A (HQ) AS Border
To Internet S0
interface Loopback0 Site Local ip address 192.168.10.2 255.255.255.255 RP/MA ip pim send-rp-discovery scope 15 ip pim send-rp-announce Loopback0 scope 15 group 20
Border A access-list 20 permit 239.255.0.0 0.0.255.255
S1
S0
T1
T1
S0
S0
Border B
Border C
Site Local RP/MA
Site B (LA) 314 0863_04F9_c7
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
Site Local RP/MA
Site C (ATL) 108
54
BW Control via Admin-Scoping Site A (HQ) AS Border
To Internet S0
Site Local RP/MA
interface Loopback0 ip address 192.168.10.1 255.255.255.255
Border A send-rp-discovery scope 15 ip pim ip pim send-rp-announce Loopback0 scope 15 group 20
S1
S0access-list 20 permit 239.255.0.0 0.0.255.255 T1
T1
S0
S0
Border B
Border C
Site Local RP/MA
Site Local RP/MA
Site B (LA) 314 0863_04F9_c7
Site C (ATL) 109
© 1999, Cisco Systems, Inc.
BW Control via Admin-Scoping Site A (HQ) AS Border
To Internet S0
Site Local RP/MA
Border A
S1
S0
T1
T1
S0
0
S interface Loopback0 Border B 255.255.255.255 Border C ip address 192.168.10.3 ip pim send-rp-discovery scope 15 ip pim send-rp-announce Loopback0 scope 15 group 20 access-list 20 permit 239.255.0.0 0.0.255.255
Site Local RP/MA
Site B (LA) 314 0863_04F9_c7
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
Site Local RP/MA
Site C (ATL) 110
55
BW Control via Admin-Scoping Site A (HQ) AS Border
To Internet S0
Site Local RP/MA
Border A
Main RP (non-Site Local Groups)
S1
S0
T1
T1
S0
S0
interface Loopback0 Border B255.255.255.255 Border C ip address 192.168.1.3 ip pim send-rp -announce Loopback0 scope 64 group 20 access-list 20 permit 239.192.0.0 0.31.255.255 access-list 20 permit 224.0.0.0 0.255.255.255 Site Local 20 permit 225.0.0.0 0.255.255.255 Site Local access-list RP/MA RP/MA . . . access-list 20 permit 238.0.0.0 0.255.255.255
Site B (LA)
314 0863_04F9_c7
Site C (ATL) 111
© 1999, Cisco Systems, Inc.
BW Control via Admin-Scoping Site A (HQ) AS Border
To Internet S0
Site Local RP/MA
Border A
S1
Interface Serial0 . . . S0 ip multicast ttl-threshold 128 ip multicast1 boundary 10
T1
T
S0
access-list 10 deny 239.0.0.0 0.0.0.255 access-list S0 10 permit any
Border B
Border C
Site Local RP/MA
Site B (LA) 314 0863_04F9_c7
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
Site Local RP/MA
Site C (ATL) 112
56
Agenda
• Which Mode? Sparse or Dense • Multicast over Campus Network • Multicast over NBMA Networks • RP Engineering • Multicast Bandwidth Control • Network Convergence 314 0863_04F9_c7
113
© 1999, Cisco Systems, Inc.
RP-Failover
• RP failover time Function of ‘Holdtime’ in RP-Announcement Holdtime = 3 x <rp-announce-interval> Default < rp-announce-interval> = 60 seconds Worst-case (default) Failover ~ 3 minutes
• Minimizing impact of RP failure Use SPTs to reduce impact Traffic on SPTs not affected by RP failure Immediate switch to SPTs is on by default New and/or bursty sources still a problem 314 0863_04F9_c7
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
114
57
Tuning RP-Failover • Tune Candidate RPs • New ‘interval’ clause added for C-RPs ip pim send-rp-announce scope [group-list acl] [interval <seconds>]
• Allows rp-announce-interval to be adjusted • Smaller intervals = Faster RP failover • Smaller intervals increase amount Auto-RP traffic • Increase is usually insignificant • Total RP failover time reduced • Min. failover ~ 3 seconds 314 0863_04F9_c7
115
© 1999, Cisco Systems, Inc.
DR Failover
A .2 (DR)
B
192.168.1.0/24
Rtr-B>show ip pim neighbor PIM Neighbor Table Neighbor Address Interface 192.168.1.2 Ethernet0
Uptime 4d22h
.1
Expires 00:01:18 00:01:18
Mode Sparse-Dense (DR)
• Depends on neighbor expiration time • Expiration Time sent in PIM query messages Expiration time = 3 x Default = 30 seconds DR Failover ~ 90 seconds (worst case) by default 314 0863_04F9_c7
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
116
58
DR Failover
• Tune PIM query interval Use interface configuration command ip pim query-interval <seconds>
Permits DR failover to be adjusted Min. DR failover ~ 3 seconds (worst case) Smaller intervals increase PIM query traffic Increase is usually insignificant
314 0863_04F9_c7
© 1999, Cisco Systems, Inc.
117
Network Topology Changes
• Unicast routing must converge first • PIM converges ~ 5 seconds after unicast • PIM convergence algorithm Entire mroute table scanned every 5 seconds RPF interface recalculated for every (*, G) and (S, G) Joins/prunes/grafts triggered as needed
314 0863_04F9_c7
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
118
59
Documentation and Contact Info
• EFT/Beta Site Web Page: ftp://ftpeng.cisco.com/ipmulticast.html
• EFT/Beta Mailing List: [email protected]
• Customer Support Mailing List: [email protected]
314 0863_04F9_c7
119
© 1999, Cisco Systems, Inc.
Coming Soon
314 0863_04F9_c7
© 1999, Cisco Systems, Inc.
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
120
60
Please Complete Your Evaluation Form Session 314
314 0863_04F9_c7
© 1999, Cisco Systems, Inc.
121
314 0863_04F9_c7
© 1999, Cisco Systems, Inc.
122
Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. 0863_04F9_c2.scr
61
