Sunday, January 10, 2016

Multicast task #3. RP configuration.

Topology:



Use configuration from Multicast task #2 as initial configuration for this task.

Requirements: 

1. For this task, use standards based protocol for distributing RP information. 
2. Router R3 should distribute of RP information, and router R2 should serve as a backup. 
3. Routers R4 and R5 should be the RP for range 224.0.0.0 - 239.255.255.255. While both routers are     active, the multicast groups should be equally load balanced between the two RPs.
4. RP information shall not be sent into VLAN 10. 

Solution:

Highlight the text below to reveal the solution.

This task requires understanding of BSR protocol configuration

Requirement #1 - BSR is standards based, vs Auto-RP which is Cisco proprietary

Requirement #2 - Configure R3 and R2 as BSR-candidates, configure R3 with higher priority.                                          Configure hash length to value different from default 32, to allow load balance                                      between the RPs. 
Requirement #3 - Configure R4 and R5 as RP candidates with equal priority. 
Requirement #4 - on R6 and R7, configure BSR-border on VLAN 10 interface. Note that you must                                  alter OSPF metrics, so VLAN 10 is never used as transit. Otherwise it may break a                              BSR information distribution due to RPF failure (log from R7, with R3 router shut                                down): 

*Dec 28 13:05:12.923: PIM-BSR(0): bootstrap (13.0.2.2) on non-RPF path Loopback0 or from non-RPF neighbor 13.0.47.4 discarded





R2:


!
ip pim bsr-candidate Loopback0 24 254
!

R3:


router pim
 address-family ipv4
  ..
  !
  bsr candidate-bsr 13.0.3.3 hash-mask-len 24 priority 255
 !
!


R4:


RP/0/0/CPU0:R4#show run router pim
Mon Dec 28 16:14:48.754 UTC
router pim
 address-family ipv4
..
  bsr candidate-rp 13.0.4.4 priority 1 interval 60
 !
!


R5:


!
ip pim rp-candidate Loopback0 priority 1
!


R6:


!
interface Ethernet0/1
 bandwidth 100
 ip address 13.0.10.6 255.255.255.0
 ip pim bsr-border
 ip pim sparse-mode
 ip igmp query-max-response-time 5
 ip igmp query-interval 10
!


R7:



!
interface Ethernet0/0
 bandwidth 100
 ip address 13.0.10.2 255.255.255.0
 ip pim bsr-border
 ip pim sparse-mode
!

Verification:


R1#sh ip pim rp mapping
PIM Group-to-RP Mappings

Group(s) 224.0.0.0/4
  RP 13.0.4.4 (?), v2
    Info source: 13.0.3.3 (?), via bootstrap, priority 1, holdtime 150
         Uptime: 00:30:59, expires: 00:02:13
  RP 13.0.5.5 (?), v2
    Info source: 13.0.3.3 (?), via bootstrap, priority 1, holdtime 150
         Uptime: 00:31:28, expires: 00:02:13
Group(s): 224.0.0.0/4, Static
    RP: 13.0.3.3 (?)


R1#sh ip pim rp-hash 224.0.0.1
  RP 13.0.5.5 (?), v2
    Info source: 13.0.3.3 (?), via bootstrap, priority 1, holdtime 150
         Uptime: 00:31:53, expires: 00:01:48
  PIMv2 Hash Value (mask 255.255.255.0)
    RP 13.0.4.4, via bootstrap, priority 1, hash value 1563362354
    RP 13.0.5.5, via bootstrap, priority 1, hash value 1639391941
R1#sh ip pim rp-hash 224.0.1.1
  RP 13.0.4.4 (?), v2
    Info source: 13.0.3.3 (?), via bootstrap, priority 1, holdtime 150
         Uptime: 00:31:25, expires: 00:01:46
  PIMv2 Hash Value (mask 255.255.255.0)
    RP 13.0.4.4, via bootstrap, priority 1, hash value 1700136242
    RP 13.0.5.5, via bootstrap, priority 1, hash value 1564559813
R1#sh ip pim rp-hash 224.0.2.1
  RP 13.0.5.5 (?), v2
    Info source: 13.0.3.3 (?), via bootstrap, priority 1, holdtime 150
         Uptime: 00:31:57, expires: 00:01:44
  PIMv2 Hash Value (mask 255.255.255.0)
    RP 13.0.4.4, via bootstrap, priority 1, hash value 1784927794
    RP 13.0.5.5, via bootstrap, priority 1, hash value 1860957381
R1#sh ip pim rp-hash 224.0.3.1
  RP 13.0.4.4 (?), v2
    Info source: 13.0.3.3 (?), via bootstrap, priority 1, holdtime 150
         Uptime: 00:31:29, expires: 00:01:42
  PIMv2 Hash Value (mask 255.255.255.0)
    RP 13.0.4.4, via bootstrap, priority 1, hash value 311088946
    RP 13.0.5.5, via bootstrap, priority 1, hash value 175512517


No comments:

Post a Comment