Scribd
Upload
131 views12 pages

Multicast CCIE

This document discusses multicast addressing and routing protocols. It covers the ranges for permanent and private multicast addresses. It also summarizes PIM dense mode, PIM sparse mode, considerations for dense and sparse core networks, and how to configure and verify PIM in each case. MSDP, multicast BGP, anycast RP, and their purposes are briefly outlined as well.

Uploaded by

Franz Mejorada Ccie
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
131 views12 pages

Multicast CCIE

This document discusses multicast addressing and routing protocols. It covers the ranges for permanent and private multicast addresses. It also summarizes PIM dense mode, PIM sparse mode, considerations for dense and sparse core networks, and how to configure and verify PIM in each case. MSDP, multicast BGP, anycast RP, and their purposes are briefly outlined as well.

Uploaded by

Franz Mejorada Ccie
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 12

Multicast Addressing

Permanent

multicast groups, in the


range 224.0.0.0224.0.1.255
Addresses used with Source-Specific
Multicast (SSM), in the range 232.0.0.0
232.255.255.255
GLOP addressing, in the range
233.0.0.0233.255.255.255
Private multicast addresses, in the
range 239.0.0.0239.255.255.255

PIM Multicast Routing


Protocols
PIM Dense Mode
PIM Sparse Mode

PIM Dense Core Considerations


RPF failure
Incoming interface for multicast must
match outgoing interface for unicast
NBMA mode problem
Unlikely in SP networks, links
typically P2P

Configuring PIM Dense Core


Enable

multicast
ip multicast-routing
Enable PIM on interfaces
ip pim dense-mode

Verifying PIM Dense Core


Verify Adjacencies
show ip pim neighbor
Simulate client joins
ip igmp join
ip igmp static
Simulate source
Ping
IP SLA
Verify transport
show ip mroute count
debug ip mpacket
no ip mroute-cache

PIM Sparse Core Considerations


How is the RP assigned?
Static
Auto-RP
a.Sparse-dense mode
b. Sparse mode only
Default RP assignment
Auto-RP listener
c. RPF failure from mapping agent or candidate RP
BSR
Anycast (more later)
RPF failure
NBMA mode problem

Verifying PIM Sparse Core


Verify Adjacencies
show ip pim neighbor
Verify PIM joins
ip igmp join
ip igmp static
debug ip pim on RP
Verify source registration
Ping
IP SLA
debug ip pim on RP
Verify transport
show ip mroute count
debug ip mpacket
no ip mroute-cache

Configuring PIM Sparse Core


Enable

multicast
ip multicast-routing
Enable PIM on interfaces
ip pim sparse-mode
ip pim sparse-dense-mode
Configure RP assignment
Static
Auto-RP
BSR

MSDP
RPs

in different ASes peer via MSDP


TCP transport required
When a source registers with the RP it
generates Source Active (SA) messages
to MSDP peers
Allows other ASes to know what senders
there are in the Internet
If local RP has a (*,G) entry for a client it
forwards PIM join up RPF tree towards
remote RP

Multicast BGP
Multicast BGP propagates source
advertisements solely for purpose of RPF
check
Like static mroutes but dynamic
Multicast BGP preferred over Unicast BGP
for RPF
Enabled through MP-BGP addressfamily
ipv4 multicast

Multicast BGP Configuration


Configure

BGP peers
Activate multicast address family
Advertise multicast sources
Verify new RPF
show ip rpf w.x.y.z

Anycast RP
Goal:
Distribute RP load to multiple devices
Simplify failover and reduce convergence
time
when an RP fails
How:
Multiple RPs share the same IP address
Typically /32 Loopback
Join and register messages sent to closest
RP based on IGP metric

You might also like