02_6_组播PIM-SM_RP

2019年7月27日 02:08 作者：金淼淋分类：Multicast  599

YES LAB
Placement of Rendezvous-Point
and Distribution of RP Information

RP Performance Considerations (
• Rendezvous-Point memory usage:
YES LAB
Entry
OIL
Memory usage
380 bytes + OIL size
220 bytes + OIL size
150 bytes per entry
The RP contains both (*,G) and (S,G) entries—
memory size increases with:
— Overall number of grouDSW$u
— The number of receiver branches per group
— The number of sources per group

Manual RP Configuration
Note: Only the relevant part of the configuration Is shown.
Router#show running-config
interface FastEthernetO/O
Ip address 192.168.1.1255.255.255.0
ip pim sparse-dense-mode
Interface Serlall/l
ip address 172.16.1.1255.255.255.0
Ip plm sparse-dense-mode
ip pim rp-address 192.168.100.1210
access-list 10 deny 224.1.1.1
access-list 10 permit 224.1.0.0 0.0.255.255
— Exa
YES LAB

YES LAB
Auto-RP Mechanism

Objectives
YES LAB
Upon completion of this lesson, you will be able to
perform the following tasks:
— Explain the Auto-RP mechanism
—Configure the Auto-RP ENHØJRP
—Troubleshoot the Auto-RP

Auto-RP Mechanism
YES LAB
PIMv1 had no mechanisms for automatic distribution
of RP information
Cisco introduced Auto-RP as a solution for dynamic
RP announcement (PIMv1+) - manual configuration
qpmy,ll
is only needed on:
- Candidates for RP (C-RP)
— Mapping Agents (MA)
PIMv2 uses a standardized bootstrap mechanism
(comparable to Auto-RP)

Auto-RP Mechanism (Cont
YES LAB
All PIM enabled Cisco routers join the Cisco-
Discovery (224.0.1.40) group automatically:
— With one of the LAN interfaces
— With one of the WAN interfaces if there is no LAN
RP-Discovery messages collected and stored in RP
mapping caches

Auto-RP—Candidate RPs
Announce
RP-Announcements multicast to the
Cisco Announce (224.0.1.39) group
Announce
Announce
Announce
YES LAB
Announce

Configuring Candidate RPs in Auto-RP
(Cont.)
• Access-list usage in Auto-RP configuration:
YES LAB
— No access-list or non-existing access-list: the RP applies to
all the groups
the RP serves for those groups only; the
— Permit—
remaining groups operate in dense-mode (if sparse-dense
mode is configured)
—the group is forced to always operate in dense-
- Deny
mode; introduced in Cisco IOS 12.0

RP Mapping Agents
RP•Discoveries multicast to e
Cisco Discovery (224.0.1.40) group
YES LAB

RP Mapping Agents—Consist
C-RP
1.1.1.1
tr-A# show ip pim rp mapping
his system is an RP-mapping agent
Initial Cache State in the Mapping Agent
YES LAB
C-RP
2.2.2.2

RP Mapping Agents—Consistenc
(Cont.)
YES LAB
C-RP
C-RP
1.1.1.1
2.2.2.2

RP Mapping Agents—Consistenc
(Cont.)
C-RP
1.1.1.1
YES LAB
C-RP
2.2.2.2
Rtr-Att 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)

RP Mapping Agents—Consistenc
(Cont.)
YES LAB
MA
00
c-tp
C-RP
1.1.1.1
2.2.2.2

RP Mapping Agents—Consistenc
(Cont.)
YES LAB
C-RP with the highest address is selected as RP and stored in cache
C-RP
1.1.1.1
MA
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:
RP 2.2.2.2 (Rtr-D), PIMv1
Info source:
Rtr-D
040
c-tp
2.2.2.2

RP Mapping Agents—Consistenc
(Cont.)
All Mapping Agents Must Have Consistent Data!
YES LAB
MA
172.1
-A# owip pim rp mapping
his system is an RP-mapping age
roup(s) 224.0.0.0/4, uptime: 00:
2.2.2.2 (Rtr-D)
, PIMv1
Info source:
2.2.2.2 (Rtr-D)
MA
72.16.2.2
s WIP pm rpm pptng
is system is an RP-mapping agent
Group(s) 224.0.0.0/4, uptime: 00:00:04, expires:
2.2.2.2 (Rtr-D)
Info source:
2.2.2.2 (Rtr-D)

Configuring RP Mapping Age
router(config)#
ip pim send-rp-discovery [type number] scope ttl
Configures the router to be a rendezvous point
(RP)-mapping agent
type number—interface type and number
(optional) that identify the source of the RP-
discovery messages (the Mapping Agent
address)
• scope tt/—decimal value (hops) that limits the
scope of RP-discovery messages
YES LAB

Sample Auto-RP Configurati
YES LAB
Routers B and C will both act as Candidate RPs and Mapping Agents
On each router:
On each interface:
On routers B and C:
PIM
Sparse Dense Mode
ip multicast-routing
Ip plm sparse-dense-mode
ip pim send-rp-announce loopbackO scope 16
Ip plm send-rp-dlscovery loopbackO scope 16

Discovery
2.2.2.2
Group-Range= 224.0.0.0/4
Holdtime= 180 sec

Auto-RP—Leaf Routers
YES LAB
Local Cache Initiall
Loaded from Router "B"
MA
172.16.2.1
roup(s) 224.0.0.0/4, uptime:
expires: 00:02:56
RP 2.2.2.2 (Rtr-D), PIMv1
source:172.16.2.2 (Rtr-B)
MA
172.16.2.2

Auto-RP—Leaf Routers (Cont"B
• Identical Info Received from Router "A"
roup(s) 224.0.0.0/4, uptime:
xpires:
RP 2.2.2.2 (Rtr-D), PIMv1
172.16.2.1 Rtr-A
o source:
"Info source" will
continue to flip-flop
between routers
A and B

Objectives
YES LAB
Upon completion of this lesson, you will be able to perform
the following tasks:
— Explain the BSR mechanism
— Configure the BSR
— Troubleshoot the BSR

PIMv2 BSR Mechanism
PIMv2
Sparse Mode
BSR Msgs Flooded Hop-by-Hop

•
PIMv2 Candidate RPs
YES LAB
Candidate RP unicasts PIMv2 Candidate RP (C-RP)
messages to the BSR
— Learns IP address of BSR from BSR messages
— Sent every rp-announce-interval (default: 60 seconds)
Candidate RP messages contain:
— Group Range (default 224.0.0.0/4)
— Candidate's RP address
— Holdtime = 3 x <rp-announce-interval>

PIMv2 Bootstrap Router (Conwr'Z
• Candidate bootstrap router (C-BSR) announces its
candidacy in BSR messages
C-BSR with highest priority is elected as BSR—the
highest IP address used as a tie-breaker
fig -B S
The active BSR may be preempted—new candidate
router with higher BSR priority forces new election

PIMv2 BSR and Leaf Router
YES LAB
All PIMv2 routers
— Receive BSR messages
• Stored in local Group-to-RP Mapping Cache
• Information is used to determine the active BSR
address
— Select RP using Hash algorithm
• Selected from local Group-to-RP Mapping Cache
All routers select same RP- using same argöiifhm
• Permits RP-load balancing across group range

Troubleshooting BSR Proble
YES LAB
Check the local RP mapping-cache
Check the BSR information using the show ip pim bsr
command
• Debug BSR information using the debug ip pim bsr
command
• Clear the contents of the RP mapping-cache
• Pay special attention to the:
- BSR
— Candidate RP (group ranges, hash-mask-length)

Work Blog » 02_6_组播PIM-SM_RP

组播

分享到：

赞(0) 打赏

02_6_组播PIM-SM_RP

相关推荐

02_10_MSDP技术介绍

02_9_anycast RP

02_8_在NBMA环境下的组播

02_7_在LAN环境下限制组播流量

02_5_2_组播PIM-SM-SSM

02_5_1_组播PIM-SM-bidir

02_4_2_组播PIM-SM_详细图解

02_4_1_组播PIM-SM_理论部分

评论抢沙发

评论前必须登录！

最新文章

觉得文章有用就打赏一下文章作者

支付宝扫一扫打赏

微信扫一扫打赏