Lab 158 - BSR with Multiple RPs

Prerequisites: CCNP level skills.

Personal Note!
1:23  in the morning. Full moon makes the mind wander ...

Ying and Yang, day and night, one and zero ... so much of this dichotomy.
Perhaps if you were good in the first half of your life, in the second you should ... find something interesting ... (LOL).

Topology

Pic. 1 - Topology Diagram.

Note!
Routers and switches are already configured as per the topology diagram. All devices use OSPF area 0 as their routing protocol as well as multicast routing.

Task 1

Enable PIM Sparse mode on VLANs: 14, 30, 133, 144. Do not enable PIM protocol on VLAN interfaces of S2 and S4.

Task 2
Configure R1 and R4 as RP candidates for all multicast groups. S3 should disseminate RP-set information. Configure hash-mask-length so that the load on RPs is evenly distributed with groups of four multicast addresses as shown below:

• Group 1: 224.1.1.0, 224.1.1.1, 224.1.1.2, 224.1.1.3 given to one RP.
• Group 2: 224.1.1.4, 224.1.1.5, 224.1.1.6, 224.1.1.7 given to another RP.
• Group 3: 224.1.1.8, 224.1.1.9, 224.1.1.10, 224.1.1.11 given to the first RP.
• etc.

Solution

Task 1

Enable PIM Sparse mode on VLANs: 14, 30, 133, 144. Do not enable PIM protocol on VLAN interfaces of S2 and S4.

R1 Configuration:

!

interface FastEthernet0/0
 ip address 10.1.14.1 255.255.255.0
 ip pim sparse-mode
 speed 100
 full-duplex

!

R3 Configuraiton:

!

interface FastEthernet0/0
 ip address 10.1.30.3 255.255.255.0
 ip pim sparse-mode
 speed 100
 full-duplex

!

interface FastEthernet0/1
 ip address 10.1.133.3 255.255.255.0
 ip pim sparse-mode
 speed 100
 full-duplex

!

R4 Configuration:

!

interface FastEthernet0/0
 ip address 10.1.14.4 255.255.255.0
 ip pim sparse-mode
 speed 100
 full-duplex
!

interface FastEthernet0/1
 ip address 10.1.143.4 255.255.255.0
 ip pim sparse-mode
 speed 100
 full-duplex

!

S3 Configuration:

!

interface Vlan133
 ip address 10.1.133.10 255.255.255.0
 ip pim sparse-mode
!

interface Vlan143
 ip address 10.1.143.10 255.255.255.0
 ip pim sparse-mode

!

Task 2
Configure R1 and R4 as RP candidates for all multicast groups. S3 should disseminate RP-set information. Configure hash-mask-length so that the load on RPs is evenly distributed with groups of four multicast addresses as shown below:

• Group 1: 224.1.1.0, 224.1.1.1, 224.1.1.2, 224.1.1.3 given to one RP.
• Group 2: 224.1.1.4, 224.1.1.5, 224.1.1.6, 224.1.1.7 given to another RP.
• Group 3: 224.1.1.8 224.1.1.9, 224.1.1.10, 224.1.1.11 given to the first RP.
• etc.

S3 Configuration:

!

interface Loopback107
 ip address 172.16.107.1 255.255.255.255
 ip pim sparse-mode 

!

ip pim bsr-candidate Loopback107 30

!

R1 Configuration:

!

interface Loopback101
 ip address 172.16.101.1 255.255.255.255
 ip pim sparse-mode
!

ip pim rp-candidate Loopback101

!

R4 Configuration:

!

interface Loopback104
 ip address 172.16.104.1 255.255.255.255
 ip pim sparse-mode
!

ip pim rp-candidate Loopback104

!

Verification:

S2 Configuration:

!

interface Vlan30
 ip address 10.1.30.12 255.255.255.0
 ip igmp join-group 224.1.1.0
 ip igmp join-group 224.1.1.1
 ip igmp join-group 224.1.1.2
 ip igmp join-group 224.1.1.3

!

S4 Configuration:

!

interface Vlan30
 ip address 10.1.30.14 255.255.255.0
 ip igmp join-group 224.1.1.4
 ip igmp join-group 224.1.1.5
 ip igmp join-group 224.1.1.6
 ip igmp join-group 224.1.1.7

!

Pic. 2 - RP (R1) Mapping.

Pic. 3 - RP (R4) Mapping.

Note!
The highest hash value denotes the RP for the group.

R1 (172.16.101.1) is the RP for groups:

• 224.1.1.0
• 224.1.1.1
• 224.1.1.2
• 224.1.1.3

 R4 is RP for the groups:

• 224.1.1.4
• 224.1.1.5
• 224.1.1.6
• 224.1.1.7