Multicast中有关RP的配置问题（II）
发信人: ietobe(ietobe)
整理人: ietobe
6. Anycast—static—sparse-mode
This is similar to the way we configured static Sparse Mode IP Multicast—the
difference being the IP address we specify is configured in more than
one router in the network. Since the IP address of the RP is configured
with a 32 bit mask, the interior gateway routing protocol will always
point to the nearest instance of the RP provided the IGP supports mask
information.
This is easy to configure and troubleshoot as the same host masked
IP address is used, regardless of which router it is configured on or
moved to. We now no longer have a single point of failure for all groups.
Each group can still have a separate RP, and these addresses can be
structured for ease of use. Anycast RP also adds redundancy and load
balancing. The load balancing can occur because of our use of Multicast
Source Discovery Protocol to ensure that all RP's are aware of the active
sources in their domain.
Here we use the same commands as for Static RP—sparse-mode, but we
also need to configure MSDP on the RP routers.
ip pim rp-address
ip pim sparse-mode
ip msdp peer connect-source
ip msdp mesh-group ip pim rp-address anycast x.x.x.x
ip msdp originator-id
Strength and Weaknesses of Anycast—static—sparse-mode
Convergence:
Excellent
Redundancy:
Excellent
Ease of use:
Very Good
Scoping:
Excellent
Safety:
Excellent
Load balancing:
Excellent
Configurations for Anycast—static—sparse-mode
36a
ip multicast-routing
interface Ethernet0/1
ip address 20.0.7.6 255.255.255.0
ip pim sparse-mode
interface FastEthernet2/0
ip address 20.0.6.6 255.255.255.0
ip pim sparse-mode
ip pim rp-address 20.0.0.1
36b
ip multicast-routing
interface Ethernet0/1
ip address 20.0.7.7 255.255.255.0
ip pim sparse-mode
interface Ethernet1/0
ip address 20.0.10.7 255.255.255.0
ip pim sparse-mode
interface FastEthernet2/0
ip address 20.0.8.7 255.255.255.0
ip pim sparse-mode
ip pim rp-address 20.0.0.1
36c
ip multicast-routing
interface Serial0/0
ip address 20.0.9.10 255.255.255.0
ip pim sparse-mode
interface Ethernet0/1
ip address 20.0.10.10 255.255.255.0
ip pim sparse-mode
interface FastEthernet1/0
ip address 20.0.3.10 255.255.255.0
ip pim sparse-mode
ip pim rp-address 20.0.0.1
36d
ip multicast-routing
interface Serial0/0
ip address 20.0.9.11 255.255.255.0
ip pim sparse-mode
!
interface Ethernet0/1
ip address 20.0.5.11 255.255.255.0
ip pim sparse-mode
ip pim rp-address 20.0.0.1
72a
ip multicast-routing
interface Loopback0
ip address 20.0.0.3 255.255.255.255
ip pim sparse-mode
interface Loopback1
ip address 20.0.0.1 255.255.255.255
ip pim sparse-mode
interface FastEthernet0/0
ip address 20.0.1.3 255.255.255.0
ip pim sparse-mode
interface Ethernet3/1
ip address 20.0.3.3 255.255.255.0
ip pim sparse-mode
interface Ethernet3/2
description test interface
ip address 20.0.2.3 255.255.255.0
ip pim sparse-mode
ip pim rp-address 20.0.0.1
ip msdp peer 20.0.0.2 connect-source Loopback0
ip msdp mesh-group ip pim rp-address anycast 20.0.0.2
ip msdp originator-id Loopback0
75a
ip multicast-routing distributed
interface Loopback0
ip address 20.0.0.2 255.255.255.255
ip pim sparse-mode
interface Loopback1
ip address 20.0.0.1 255.255.255.255
ip pim sparse-mode
interface FastEthernet0/0/0
ip address 20.0.1.2 255.255.255.0
ip pim sparse-mode
ip route-cache distributed
interface FastEthernet0/1/0
ip address 20.0.6.2 255.255.255.0
ip pim sparse-mode
ip route-cache distributed
ip pim rp-address 20.0.0.1
ip msdp peer 20.0.0.3 connect-source Loopback0
ip msdp mesh-group anycast 20.0.0.3
ip msdp originator-id Loopback0
7. Anycast—Auto-RP—sparse-dense
This is similar to scenario 3, except we are using an Anycast address
for the RPs advertised by Auto-RP. We still have only a single RP address,
either per group or as in this configuration for all groups, at any
one time. But because we are using an Anycast address and MSDP, we can
actually be utilizing more than one RP for the same group. Because we
are using PIM Sparse-Dense, in the event we cannot locate an RP we may
revert to PIM Dense mode.
The commands for this are similar to scenario 3, except we have added
the MSDP commands so that the RP are all aware of all sources.
ip pim sparse-dense-mode
ip pim send-rp-announce
ip pim send-rp-discovery
ip msdp peer connect-source
ip msdp mesh-group ip pim rp-address anycast x.x.x.x
ip msdp originator-id
Strength and Weaknesses of Anycast—Auto-RP—sparse-dense
Convergence:
Very Good
Redundancy:
Excellent
Ease of use:
Excellent
Scoping:
Excellent
Safety:
Good
Load balancing:
Excellent
Configurations for Anycast—Auto-RP—sparse-dense
36a
ip multicast-routing
interface Ethernet0/1
ip address 20.0.7.6 255.255.255.0
ip pim sparse-dense-mode
interface FastEthernet2/0
ip address 20.0.6.6 255.255.255.0
ip pim sparse-dense-mode
36b
ip multicast-routing
interface Ethernet0/1
ip address 20.0.7.7 255.255.255.0
ip pim sparse-dense-mode
interface Ethernet1/0
ip address 20.0.10.7 255.255.255.0
ip pim sparse-dense-mode
interface FastEthernet2/0
ip address 20.0.8.7 255.255.255.0
ip pim sparse-dense-mode
36c
ip multicast-routing
interface Serial0/0
ip address 20.0.9.10 255.255.255.0
ip pim sparse-dense-mode
interface Ethernet0/1
ip address 20.0.10.10 255.255.255.0
ip pim sparse-dense-mode
interface FastEthernet1/0
ip address 20.0.3.10 255.255.255.0
ip pim sparse-dense-mode
36d
ip multicast-routing
interface Serial0/0
ip address 20.0.9.11 255.255.255.0
ip pim sparse-dense-mode
!
interface Ethernet0/1
ip address 20.0.5.11 255.255.255.0
ip pim sparse-dense-mode
72a
ip multicast-routing
interface Loopback0
ip address 20.0.0.3 255.255.255.255
ip pim sparse-dense-mode
interface Loopback1
ip address 20.0.0.1 255.255.255.255
ip pim sparse-mode
interface FastEthernet0/0
ip address 20.0.1.3 255.255.255.0
ip pim sparse-dense-mode
interface Ethernet3/1
ip address 20.0.3.3 255.255.255.0
ip pim sparse-dense-mode
interface Ethernet3/2
description test interface
ip address 20.0.2.3 255.255.255.0
ip pim sparse-dense-mode
ip pim send-rp-announce Loopback1 scope 32 group-list 10
ip pim send-rp-discovery Loopback1 scope 32
ip msdp peer 20.0.0.2 connect-source Loopback0
ip msdp mesh-group ip pim rp-address anycast 20.0.0.2
ip msdp originator-id Loopback0
access-list 10 permit 224.0.0.0 15.255.255.255
75a
ip multicast-routing distributed
interface Loopback0
ip address 20.0.0.2 255.255.255.255
ip pim sparse-mode
interface Loopback1
ip address 20.0.0.1 255.255.255.255
ip pim sparse-mode
interface FastEthernet0/0/0
ip address 20.0.1.2 255.255.255.0
ip pim sparse-mode
ip route-cache distributed
interface FastEthernet0/1/0
ip address 20.0.6.2 255.255.255.0
ip pim sparse-mode
ip route-cache distributed
ip pim send-rp-announce Loopback1 scope 32 group-list 10
ip pim send-rp-discovery Loopback1 scope 32
ip msdp peer 20.0.0.3 connect-source Loopback0
ip msdp mesh-group anycast 20.0.0.3
ip msdp originator-id Loopback0
access-list 10 permit 224.0.0.0 15.255.255.255
8. Anycast—BSR- sparse- mode
This is similar to scenario 5, except we are using an Anycast address
for the RP's advertised by BSR. We still have only a single RP address,
either per group or as in this configuration for all groups, at any
one time. But because we are using an Anycast address and MSDP, we can
actually utilize more than 1 RP at a time for the same group. Again
we have no ability to scope.
The same commands are used as per scenario 5 except that the RP interfaces
are configured with a anycast address, and a MSDP configuration is needed
again to ensure all RPs have the same source information.
ip pim bsr-candidate
ip pim rp-candidate
ip msdp peer connect-source
ip msdp mesh-group ip pim rp-address anycast x.x.x.x
ip msdp originator-id
Strength and Weaknesses of Anycast—BSR—sparse-mode
Convergence:
Very Good
Redundancy:
Excellent
Ease of use:
Excellent
Scoping:
Poor
Safety:
Excellent
Load balancing:
Excellent
Configurations for Anycast—BSR—sparse-mode
36a
ip multicast-routing
interface Ethernet0/1
ip address 20.0.7.6 255.255.255.0
ip pim sparse-mode
interface FastEthernet2/0
ip address 20.0.6.6 255.255.255.0
ip pim sparse-mode
36b
ip multicast-routing
interface Ethernet0/1
ip address 20.0.7.7 255.255.255.0
ip pim sparse-mode
interface Ethernet1/0
ip address 20.0.10.7 255.255.255.0
ip pim sparse-mode
interface FastEthernet2/0
ip address 20.0.8.7 255.255.255.0
ip pim sparse-mode
36c
ip multicast-routing
interface Serial0/0
ip address 20.0.9.10 255.255.255.0
ip pim sparse-mode
interface Ethernet0/1
ip address 20.0.10.10 255.255.255.0
ip pim sparse-mode
36d
ip multicast-routing
interface Serial0/0
ip address 20.0.9.11 255.255.255.0
ip pim sparse-mode
interface Ethernet0/1
ip address 20.0.5.11 255.255.255.0
ip pim sparse-mode
72a
ip multicast-routing
interface Loopback0
ip address 20.0.0.3 255.255.255.255
ip pim sparse-mode
interface Loopback1
ip address 20.0.0.1 255.255.255.255
ip pim sparse-mode
interface FastEthernet0/0
ip address 20.0.1.3 255.255.255.0
ip pim sparse-mode
interface Ethernet3/1
ip address 20.0.3.3 255.255.255.0
ip pim sparse-mode
interface Ethernet3/2
ip address 20.0.2.3 255.255.255.0
ip pim sparse-mode
ip pim bsr-candidate Loopback1 1
ip pim rp-candidate Loopback1
ip msdp peer 20.0.0.2 connect-source Loopback0
ip msdp mesh-group anycast 20.0.0.2
ip msdp originator-id Loopback0
75a
ip multicast-routing distributed
interface Loopback0
ip address 20.0.0.2 255.255.255.255
ip pim sparse-dense-mode
interface Loopback1
ip address 20.0.0.1 255.255.255.255
ip pim sparse-mode
interface FastEthernet0/0/0
ip address 20.0.1.2 255.255.255.0
ip pim sparse-mode
interface FastEthernet0/1/0
ip address 20.0.6.2 255.255.255.0
ip pim sparse-dense-mode
ip pim bsr-candidate Loopback1 1
ip pim rp-candidate Loopback1
ip msdp peer 20.0.0.3 connect-source Loopback0
ip msdp mesh-group anycast 20.0.0.3
ip msdp originator-id Loopback0
9. Static—Auto-RP—sparse-mode
This scenario uses a static RP address only for the auto RP groups and
then allows Auto RP to distribute the RP information as usual. This
scenario has the benefit of no risk of reverting to dense mode for any
group, and it also utilizes Auto-RP redundancy. It does, however, have
the limitation of a single point of failure, in that the static RP address
is a single address within the network.
Here we use the following commands to have the static RP address only
work for the well-known Auto-RP groups. The other commands are used
as for regular Auto-RP
ip pim sparse-mode
ip pim rp-address X
ip pim rp-announce-filter group-list X
access-list X
ip pim send-rp-announce
ip pim send-rp-discovery
Strength and Weaknesses of Static—Auto-RP—sparse-mode
Convergence:
Excellent
Redundancy:
Very Good
Ease of use:
Excellent
Scoping:
Excellent
Safety:
Very Good
Load balancing:
Poor
Configurations for Static—Auto-RP—sparse-mode
36a
ip multicast-routing
interface Ethernet0/1
ip address 20.0.7.6 255.255.255.0
ip pim sparse-mode
interface FastEthernet2/0
ip address 20.0.6.6 255.255.255.0
ip pim sparse-mode
ip pim rp-address 20.0.0.2 1
ip pim rp-announce-filter group-list 1
access-list 1 permit 224.0.1.39
access-list 1 permit 224.0.1.40
36b
ip multicast-routing
interface Ethernet0/1
ip address 20.0.7.7 255.255.255.0
ip pim sparse-mode
interface Ethernet1/0
ip address 20.0.10.7 255.255.255.0
ip pim sparse-mode
interface FastEthernet2/0
ip address 20.0.8.7 255.255.255.0
ip pim sparse-mode
ip pim rp-address 20.0.0.2 1
ip pim rp-announce-filter group-list 1
access-list 1 permit 224.0.1.39
access-list 1 permit 224.0.1.40
36c
ip multicast-routing
interface Serial0/0
ip address 20.0.9.10 255.255.255.0
ip pim sparse-mode
interface Ethernet0/1
ip address 20.0.10.10 255.255.255.0
ip pim sparse-mode
interface FastEthernet1/0
ip address 20.0.3.10 255.255.255.0
ip pim sparse-mode
ip pim rp-address 20.0.0.2 1
ip pim rp-announce-filter group-list 1
access-list 1 permit 224.0.1.39
access-list 1 permit 224.0.1.40
36d
ip multicast-routing
interface Serial0/0
ip address 20.0.9.11 255.255.255.0
ip pim sparse-mode
!
interface Ethernet0/1
ip address 20.0.5.11 255.255.255.0
ip pim sparse-mode
ip pim rp-address 20.0.0.2 1
ip pim rp-announce-filter group-list 1
access-list 1 permit 224.0.1.39
access-list 1 permit 224.0.1.40
72a
ip multicast-routing
interface Loopback0
ip address 20.0.0.3 255.255.255.255
ip pim sparse-mode
interface Loopback1
ip address 20.0.0.1 255.255.255.255
ip pim sparse-mode
interface FastEthernet0/0
ip address 20.0.1.3 255.255.255.0
ip pim sparse-mode
interface Ethernet3/1
ip address 20.0.3.3 255.255.255.0
ip pim sparse-mode
interface Ethernet3/2
description test interface
ip address 20.0.2.3 255.255.255.0
ip pim sparse-mode
ip pim rp-address 20.0.0.2 1
ip pim rp-announce-filter group-list 1
access-list 1 permit 224.0.1.39
access-list 1 permit 224.0.1.40
75a
ip multicast-routing distributed
interface Loopback0
ip address 20.0.0.2 255.255.255.255
ip pim sparse-mode
interface Loopback1
ip address 20.0.0.1 255.255.255.255
ip pim sparse-mode
interface FastEthernet0/0/0
ip address 20.0.1.2 255.255.255.0
ip pim sparse-mode
ip route-cache distributed
interface FastEthernet0/1/0
ip address 20.0.6.2 255.255.255.0
ip pim sparse-mode
ip route-cache distributed
ip pim rp-address 20.0.0.2 1
ip pim rp-announce-filter group-list 1
access-list 1 permit 224.0.1.39
access-list 1 permit 224.0.1.40
10. Anycast—Auto-RP—sparse-mode
This scenario has all the benefits of both Anycast and Auto-RP; and
as it utilizes PIM Sparse-Mode, there is no danger of reverting to PIM
Dense-Mode as with Auto-RP using Sparse-Dense. Because Anycast is used
only for the Auto-RP groups 224.0.1.39 and 224.0.1.40 and the other
groups using the normal Auto-RP, it is easier to determine which RP
is in being used by which group. Also because of the announce filter,
we will not register with the RP, unless its address is different than
the addresses of the anycast RP. Because of the way Auto-RP works, I
have chosen the Anycast address to be the lowest of the x.x.x.x/32 range
I have used for the loopback addresses.
Strength and Weaknesses of Anycast—Auto-RP—sparse-mode
Convergence:
Excellent
Redundancy:
Excellent
Ease of use:
Excellent
Scoping:
Excellent
Safety:
Excellent
Load balancing:
Excellent
Configurations for Anycast—Auto-RP—sparse-mode
36a
ip multicast-routing
interface Ethernet0/1
ip address 20.0.7.6 255.255.255.0
ip pim sparse-mode
interface FastEthernet2/0
ip address 20.0.6.6 255.255.255.0
ip pim sparse-mode
ip pim rp-address 20.0.0.1 1
ip pim rp-announce-filter group-list 1
access-list 1 permit 224.0.1.39
access-list 1 permit 224.0.1.40
36b
ip multicast-routing
interface Ethernet0/1
ip address 20.0.7.7 255.255.255.0
ip pim sparse-mode
interface Ethernet1/0
ip address 20.0.10.7 255.255.255.0
ip pim sparse-mode
interface FastEthernet2/0
ip address 20.0.8.7 255.255.255.0
ip pim sparse-mode
ip pim rp-address 20.0.0.1 1
ip pim rp-announce-filter group-list 1
access-list 1 permit 224.0.1.39
access-list 1 permit 224.0.1.40
36c
ip multicast-routing
interface Serial0/0
ip address 20.0.9.10 255.255.255.0
ip pim sparse-mode
interface Ethernet0/1
ip address 20.0.10.10 255.255.255.0
ip pim sparse-mode
interface FastEthernet1/0
ip address 20.0.3.10 255.255.255.0
ip pim sparse-mode
ip pim rp-address 20.0.0.1 1
ip pim rp-announce-filter group-list 1
access-list 1 permit 224.0.1.39
access-list 1 permit 224.0.1.40
36d
ip multicast-routing
interface Serial0/0
ip address 20.0.9.11 255.255.255.0
ip pim sparse-mode
!
interface Ethernet0/1
ip address 20.0.5.11 255.255.255.0
ip pim sparse-mode
ip pim rp-address 20.0.0.1 1
ip pim rp-announce-filter group-list 1
access-list 1 permit 224.0.1.39
access-list 1 permit 224.0.1.40
72a
ip multicast-routing
interface Loopback0
ip address 20.0.0.3 255.255.255.255
ip pim sparse-mode
interface Loopback1
ip address 20.0.0.1 255.255.255.255
ip pim sparse-mode
interface FastEthernet0/0
ip address 20.0.1.3 255.255.255.0
ip pim sparse-mode
interface Ethernet3/1
ip address 20.0.3.3 255.255.255.0
ip pim sparse-mode
interface Ethernet3/2
description test interface
ip address 20.0.2.3 255.255.255.0
ip pim sparse-mode
ip pim rp-address 20.0.0.1 1
ip pim rp-announce-filter group-list 1
access-list 1 permit 224.0.1.39
access-list 1 permit 224.0.1.40
ip pim send-rp-announce Loopback0 scope 32 group-list 10
ip pim send-rp-discovery Loopback0 scope 32
ip msdp peer 20.0.0.2 connect-source Loopback0
ip msdp mesh-group ip pim rp-address anycast 20.0.0.2
ip msdp originator-id Loopback0
access-list 10 permit 224.0.0.0 15.255.255.255
75a
ip multicast-routing distributed
interface Loopback0
ip address 20.0.0.2 255.255.255.255
ip pim sparse-mode
interface Loopback1
ip address 20.0.0.1 255.255.255.255
ip pim sparse-mode
interface FastEthernet0/0/0
ip address 20.0.1.2 255.255.255.0
ip pim sparse-mode
interface FastEthernet0/1/0
ip address 20.0.6.2 255.255.255.0
ip pim sparse-mode
ip pim rp-address 20.0.0.1 1
ip pim rp-announce-filter group-list 1
access-list 1 permit 224.0.1.39
access-list 1 permit 224.0.1.40
ip pim send-rp-announce Loopback0 scope 32 group-list 10
ip pim send-rp-discovery Loopback0 scope 32
ip msdp peer 20.0.0.3 connect-source Loopback0
ip msdp mesh-group anycast 20.0.0.3
ip msdp originator-id Loopback0
access-list 10 permit 224.0.0.0 15.255.255.255
CSCdr67362 Release Note
The hash value used for rendezvous point (RP) selection process in a
bootstrap router (BSR) is calculated with a modulo of 2 to the power
of 32. This modulo might cause inconsistency in the selected RP address
between Cisco and other vendors implementing BSR.
Workaround: Follow these rules to avoid inconsistency between Cisco
Routers when upgrading Cisco IOS software:
If you plan to upgrade routers in your network that use BSR, avoid running
Cisco IOS Release 12.0(10)S, Release 12.0(11)S, Release 12.0(11), or
Release 12.1(2).
When upgrading your routers, always upgrade the candidate BSR routers
first to a release later than Cisco IOS Release 12.0(10)S, Release 12.0(11)S,
Release 12.0(11), or Release 12.1(2). You do not need to upgrade the
rest of your network immediately unless you are running the images in
CSCdp95116 that might cause the routers to choose the RP on the basis
of an incorrect hash value.
CSCdp95116 Release Note
In a Protocol Independent Multicast (PIM) Version 2 router configuration,
if a hash mask is not configured on a Cisco bootstrap router (BSR),
the router takes the first rendezvous point (RP) address from the local
RP-mapping cache. The RP-mapping cache is not sorted, so when RPs are
added and deleted from the cache, there might be inconsistency through
the BSR domain that causes routers to choose different RPs for the same
group.
Workaround: Create a hash mask length of 1 on the BSR router by entering
the
ip pim bsr-candidate Ethernet1/2 1
global configuration command
|
