LAB GUIDE

PIM-SM Troubleshooting
IMPORTANT! THIS GUIDE ASSUMES THAT THE AOS-CX OVA HAS BEEN INSTALLED AND WORKS IN GNS3 OR EVE-NG. PLEASE
REFER TO GNS3/EVE-NG INITIAL SETUP LABS IF REQUIRED.
https://www.eve-ng.net/index.php/documentation/howtos/howto-add-aruba-cx-switch/

TABLE OF CONTENTS
Lab Objective .............................................................................................................................................. 1
Lab Overview .............................................................................................................................................. 1
Lab Network Layout .................................................................................................................................... 2
Lab Tasks ................................................................................................................................................... 2
Task 1 – Lab setup ..................................................................................................................................... 2
Task 2 – Configure Multicast Source .......................................................................................................... 3
Task 3 – Check PIM on LHR....................................................................................................................... 4
Task 4 – Check BSR/RP............................................................................................................................. 4
Task 5 – Check PIM on LHR again ............................................................................................................. 6
Task 6 – Check mroutes on LHR and FHR ................................................................................................. 6
Task 7 – Check PIM on FHR ...................................................................................................................... 6
Task 8 – Check Unicast Routing on FHR/LHR ............................................................................................ 7
Task 9 – Verify mroutes on all switches ...................................................................................................... 9
Appendix – Complete Configurations ........................................................................................................ 10

Lab Objective
This lab will enable the reader to gain hands on experience with PIM-SM troubleshooting. This lab as shown in Figure 1 is
preconfigured with 2 problems, you will use the troubleshooting flowchart to perform verification steps to identify and fix the
problems.

Lab Overview
This lab as shown in Figure 1 will allow you to send multicast traffic from the multicast source connected to First Hop Router
(FHR) towards multicast receiver connected to Last Hop Router (LHR) after the 2 problems are identified and fixed.

/24 subnets are used as source/receiver subnets, /32 loopbacks are used on switches and /31 subnets are used between the
switches.

1
 Lab Guide
PIM-SM Troubleshooting

Notes:

- Importing EVE-NG lab will not import the configs, you will need to copy and paste the configs from the appendix into your
switches before attempting this lab.

- Simulating a multicast source on a CX VM is not supported, so a Virtual PC Simulator (VPCS) is used.

- Simulating a multicast receiver using VPCS is also not supported as it doesn't send IGMP joins, a static IGMP join is used on
LHR instead

Lab Network Layout

Figure 1. Lab topology and addresses

Lab Tasks
Task 1 – Lab setup
For this lab refer to Figure 1 for topology and IP address details.

• Start all the devices, including VPCS hosts

2
 Lab Guide
PIM-SM Troubleshooting

• Open each switch console and log in with user “admin” and hit enter, so that no password is applied
• Configs are not transferred in the .unl/.zip files, copy and paste in configs for all devices from the appendix section
Always troubleshoot from receivers towards the source as shown in Figure 1.

Here are some recommended checks and suggested next steps from the bottom up approach shown in Figure 1.

Check IGMP joins on LHR using “sh ip igmp groups”

• Joins seen, check PIM next

• No joins seen, check receivers

• IGMP/PIM are required on receiver subnet

Check PIM on LHR

• RP known, check multicast routing for “Incoming Interface”, “Outgoing Interface List”

• No RP known, check BSR/C-RP, check PIM neighbor establishment

Check BSR/RP

• Check PIM neighbor establishment

• Check multicast routing for “Incoming Interface”, “Outgoing Interface List”

Check FHR

• Check PIM neighbor establishment

• Check RPs are known

• PIM required on source subnet

• Check multicast routing for “Incoming Interface”, “Outgoing Interface List”

Always remember multicast routing depends on unicast routing, if receivers are unable to connect to source via unicast, multicast
will not work.

Task 2 – Configure Multicast Source

• Configure the Source VPCS with your desired IP and default gateway
VPCS> ip 10.0.110.1/24 10.0.110.254
Checking for duplicate address...
PC1 : 10.0.110.1 255.255.255.0 gateway 10.0.110.254
• Generate multicast traffic on the source VPCS and leave it running (it has to be running to validate mroute later on)
VPCS> ping 239.10.10.10 -c 10000

239.10.10.10 icmp_seq=1 timeout

239.10.10.10 icmp_seq=2 timeout
239.10.10.10 icmp_seq=3 timeout
239.10.10.10 icmp_seq=4 timeout
239.10.10.10 icmp_seq=5 timeout
239.10.10.10 icmp_seq=6 timeout
239.10.10.10 icmp_seq=7 timeout
239.10.10.10 icmp_seq=8 timeout
239.10.10.10 icmp_seq=9 timeout

3
 Lab Guide
PIM-SM Troubleshooting

Task 3 – Check PIM on LHR

• Since VPCS is unable to function as multicast receiver, you will not be able to check IGMP joins (this step should be
performed when real switches are used)

• Start with LHR, check if PIM neighbors are seen.

LHR# sh ip pim nei

PIM Neighbor

VRF : default
Total number of neighbors : 1

IP Address : 192.168.4.4
Interface : 1/1/2
Up Time (HH:MM:SS) : 00:00:58
Expire Time (HH:MM:SS) : 00:01:23
DR Priority : 1
Hold Time (HH:MM:SS) : 00:01:45
• Above looks good, check RP/BSR info next
LHR# sh ip pim bsr
Status and Counters- PIM-SM Bootstrap Router Information

VRF : default
E-BSR Address :
E-BSR Priority : 0
E-BSR Hash Mask Length : 0
E-BSR Up Time : 0 secs
Next Bootstrap Message : 0 secs

C-BSR Admin Status : This system is not a Candidate-BSR

C-RP Admin Status : This system is not a Candidate-RP

LHR# sh ip pim rp-set

• It doesn’t looks good, both RP/BSR are not learnt, you will need to check the RP/BSR next

Task 4 – Check BSR/RP

• Check RP/BSR info
RP-BSR# sh ip pim bsr
Status and Counters- PIM-SM Bootstrap Router Information

VRF : default
E-BSR Address :
E-BSR Priority : 0
E-BSR Hash Mask Length : 0
E-BSR Up Time : 0 secs
Next Bootstrap Message : 0 secs

C-BSR Admin Status : This system is not a Candidate-BSR

C-RP Admin Status : This system is a Candidate-RP

C-RP Address : 192.168.2.2
C-RP Hold Time : 150

4
 Lab Guide
PIM-SM Troubleshooting

C-RP Advertise Period : 60

C-RP Priority : 192
C-RP Source IP Interface : loopback0

Group Address Group Mask

--------------- ---------------
224.0.0.0 240.0.0.0

RP-BSR# sh ip pim rp-set

• It doesn’t look good as there is no BSR stated

• Review the PIM config

router pim
enable
rp-candidate source-ip-interface loopback0 group-prefix 224.0.0.0/4

• You will see BSR config is missing (that is the problem)

• Configure BSR correctly

RP-BSR# conf
RP-BSR(config)# router pim
RP-BSR(config-pim)# bsr-candidate source-ip-interface loopback0
• Verify BSR/RP is now correct
RP-BSR(config)# sh ip pim bsr
Status and Counters- PIM-SM Bootstrap Router Information

VRF : default
E-BSR Address : 192.168.2.2
E-BSR Priority : 0
E-BSR Hash Mask Length : 30
E-BSR Up Time : 1 mins 11 secs
Next Bootstrap Message : 49 secs

C-BSR Admin Status : This system is a Candidate-BSR

C-BSR Address : 192.168.2.2
C-BSR Priority : 0
C-BSR Hash Mask Length : 30
C-BSR Message Interval : 60
C-BSR Source IP Interface : loopback0

C-RP Admin Status : This system is a Candidate-RP

C-RP Address : 192.168.2.2
C-RP Hold Time : 150
C-RP Advertise Period : 60
C-RP Priority : 192
C-RP Source IP Interface : loopback0

Group Address Group Mask

--------------- ---------------
224.0.0.0 240.0.0.0

RP-BSR(config)# sh ip pim rp-set

VRF: default

Status and Counters - PIM-SM Learned RP-Set Information

5
 Lab Guide
PIM-SM Troubleshooting

Group Address Group Mask RP Address Hold Time Expire Time

--------------- --------------- --------------- --------- -----------
224.0.0.0 240.0.0.0 192.168.2.2 150 134

Task 5 – Check PIM on LHR again

• Verify BSR/RP info is learnt on LHR
LHR# sh ip pim bsr
Status and Counters- PIM-SM Bootstrap Router Information

VRF : default
E-BSR Address : 192.168.2.2
E-BSR Priority : 0
E-BSR Hash Mask Length : 30
E-BSR Up Time : 1 mins 26 secs
Next Bootstrap Message : 1 mins 44 secs

C-BSR Admin Status : This system is not a Candidate-BSR

C-RP Admin Status : This system is not a Candidate-RP

LHR# sh ip pim rp-set

VRF: default

Status and Counters - PIM-SM Learned RP-Set Information

Group Address Group Mask RP Address Hold Time Expire Time
--------------- --------------- --------------- --------- -----------
224.0.0.0 240.0.0.0 192.168.2.2 150 115

Task 6 – Check mroutes on LHR and FHR

• Check mroutes on LHR
LHR# sh ip mroute

FHR# sh ip mroute
• It doesn’t look good as nothing is seen

Task 7 – Check PIM on FHR

• Verify BSR/RP info is learnt on FHR
FHR# sh ip pim bsr
Status and Counters- PIM-SM Bootstrap Router Information

VRF : default
E-BSR Address : 192.168.2.2
E-BSR Priority : 0
E-BSR Hash Mask Length : 30
E-BSR Up Time : 11 mins 25 secs
Next Bootstrap Message : 1 mins 45 secs

6
 Lab Guide
PIM-SM Troubleshooting

C-BSR Admin Status : This system is not a Candidate-BSR

C-RP Admin Status : This system is not a Candidate-RP

FHR# sh ip pim rp-set

VRF: default

Status and Counters - PIM-SM Learned RP-Set Information

Group Address Group Mask RP Address Hold Time Expire Time
--------------- --------------- --------------- --------- -----------
224.0.0.0 240.0.0.0 192.168.2.2 150 121

• Verify PIM is enabled correctly on FHR interfaces

FHR# sh ip pim int

PIM Interfaces

VRF: default
Total Number of interfaces : 2

Interface : 1/1/2
Neighbor count : 1
IP Address : 192.168.4.0/31
Mode : sparse
Designated Router : 192.168.4.1
Proxy DR : false
Hello Interval (sec) : 30
Hello Delay (sec) : 5
Override Interval (msec) : 2500 Lan Prune Delay : Yes
Propagation Delay (msec) : 500 Configured DR Priority : 1
Operational DR Priority : 1
Neighbor Timeout : 103

Interface : vlan110
Neighbor count : 0
IP Address : 10.0.110.254/24
Mode : sparse
Designated Router : 10.0.110.254
Proxy DR : false
Hello Interval (sec) : 30
Hello Delay (sec) : 5
Override Interval (msec) : 2500 Lan Prune Delay : Yes
Propagation Delay (msec) : 500 Configured DR Priority : 1
Operational DR Priority : 1
Neighbor Timeout : 0

• Above verifications look good

Task 8 – Check Unicast Routing on FHR/LHR

• Referring to the troubleshooting flow and checks stated on page 3, let’s verify unicast connectivity between the
source/receiver subnets
FHR# sh ip ro

Displaying ipv4 routes selected for forwarding

Origin Codes: C - connected, S - static, L - local

7
 Lab Guide
PIM-SM Troubleshooting

R - RIP, B - BGP, O - OSPF

Type Codes: E - External BGP, I - Internal BGP, V - VPN, EV - EVPN
IA - OSPF internal area, E1 - OSPF external type 1
E2 - OSPF external type 2

VRF: default

Prefix Nexthop Interface VRF(egress)

Origin/ Distance/ Age
Type Metric
----------------------------------------------------------------------------------------------
10.0.110.0/24 - vlan110 - C [0/0] -
10.0.110.254/32 - vlan110 - L [0/0] -
10.0.111.0/24 192.168.4.1 1/1/2 - O [110/300] 03h:32m:28s
192.168.2.1/32 - loopback0 - L [0/0] -
192.168.2.2/32 192.168.4.1 1/1/2 - O [110/100] 03h:32m:28s
192.168.2.4/32 192.168.4.1 1/1/2 - O [110/200] 03h:29m:58s
192.168.4.0/31 - 1/1/2 - C [0/0] -
192.168.4.0/32 - 1/1/2 - L [0/0] -
192.168.4.4/31 192.168.4.1 1/1/2 - O [110/200] 03h:32m:23s

Total Route Count : 9

• Good, FHR sees the receiver subnet (10.0.111.0/24)

• Check if LHR sees the source subnet

LHR# sh ip route

Displaying ipv4 routes selected for forwarding

Origin Codes: C - connected, S - static, L - local

R - RIP, B - BGP, O - OSPF
Type Codes: E - External BGP, I - Internal BGP, V - VPN, EV - EVPN
IA - OSPF internal area, E1 - OSPF external type 1
E2 - OSPF external type 2

VRF: default

Prefix Nexthop Interface VRF(egress)

Origin/ Distance/ Age
Type Metric
----------------------------------------------------------------------------------------------
10.0.111.0/24 - vlan111 - C [0/0] -
10.0.111.254/32 - vlan111 - L [0/0] -
192.168.2.1/32 192.168.4.4 1/1/2 - O [110/200] 03h:33m:32s
192.168.2.2/32 192.168.4.4 1/1/2 - O [110/100] 03h:33m:32s
192.168.2.4/32 - loopback0 - L [0/0] -
192.168.4.0/31 192.168.4.4 1/1/2 - O [110/200] 03h:33m:32s
192.168.4.4/31 - 1/1/2 - C [0/0] -
192.168.4.5/32 - 1/1/2 - L [0/0] -

Total Route Count : 8

• Looks bad, FHR does not have the 10.0.110.0/24 route, it does not have connectivity to the source subnet (that is the
problem)

• Checking FHR source subnet, you will see that OSPF is not enabled
interface vlan 110
ip address 10.0.110.254/24
ip pim-sparse enable

• Enable OSPF within Int VLAN 110

FHR(config)# int vlan 110
FHR(config-if-vlan)# ip ospf 1 area 0

8
 Lab Guide
PIM-SM Troubleshooting

Task 9 – Verify mroutes on all switches

• On FHR
FHR(config)# sh ip mr
IP Multicast Route Entries

VRF : default
Total number of entries : 1

Group Address : 239.10.10.10

Source Address : 10.0.110.1
Neighbor :
Incoming interface : vlan110
Outgoing Interface List :
Interface State
----------- ----------
1/1/2 forwarding

• On BSR/RP
RP-BSR(config)# sh ip mr
IP Multicast Route Entries

VRF : default
Total number of entries : 2

Group Address : 239.10.10.10

Source Address : 10.0.110.1
Neighbor : 192.168.4.0
Incoming interface : loopback0

Group Address : 239.10.10.10

Source Address : 10.0.110.1
Neighbor : 192.168.4.0
Incoming interface : 1/1/1
Outgoing Interface List :
Interface State
----------- ----------
1/1/2 forwarding

• On LHR
LHR# sh ip mr
IP Multicast Route Entries

VRF : default
Total number of entries : 1

Group Address : 239.10.10.10

Source Address : 10.0.110.1
Neighbor : 192.168.4.4
Incoming interface : 1/1/2
Outgoing Interface List :
Interface State
----------- ----------
vlan111 forwarding

• Congratulations, you have validated multicast forwarding works as expected across the switches

9
 Lab Guide
PIM-SM Troubleshooting

Appendix – Complete Configurations

• Configs with problems are provided below

FHR
!Version ArubaOS-CX Virtual.10.07.0010
hostname FHR
led locator on
ntp server pool.ntp.org minpoll 4 maxpoll 4 iburst
ntp enable
!
!
!
!
!
!
ssh server vrf mgmt
vlan 1,110
interface mgmt
no shutdown
ip dhcp
interface 1/1/1
no shutdown
no routing
vlan access 110
interface 1/1/2
no shutdown
ip address 192.168.4.0/31
ip ospf 1 area 0.0.0.0
ip pim-sparse enable
interface 1/1/3
no shutdown
interface 1/1/4
no shutdown
interface 1/1/5
no shutdown
interface 1/1/6
no shutdown
interface loopback 0
ip address 192.168.2.1/32
ip ospf 1 area 0.0.0.0
interface vlan 110
ip address 10.0.110.254/24
ip pim-sparse enable
router ospf 1
area 0.0.0.0
router pim
enable
https-server vrf mgmt

RP-BSR
!Version ArubaOS-CX Virtual.10.07.0010
hostname RP-BSR
led locator on
ntp server pool.ntp.org minpoll 4 maxpoll 4 iburst
ntp enable
!
!
!
!

10
 Lab Guide
PIM-SM Troubleshooting

!
!
ssh server vrf mgmt
vlan 1
interface mgmt
no shutdown
ip dhcp
interface 1/1/1
no shutdown
ip address 192.168.4.1/31
ip ospf 1 area 0.0.0.0
ip pim-sparse enable
interface 1/1/2
no shutdown
ip address 192.168.4.4/31
ip ospf 1 area 0.0.0.0
ip pim-sparse enable
interface 1/1/3
no shutdown
interface 1/1/4
no shutdown
interface 1/1/5
no shutdown
interface 1/1/6
no shutdown
interface loopback 0
ip address 192.168.2.2/32
ip ospf 1 area 0.0.0.0
ip pim-sparse enable
!
!
!
!
!
router ospf 1
area 0.0.0.0
router pim
enable
rp-candidate source-ip-interface loopback0 group-prefix 224.0.0.0/4
https-server vrf mgmt

LHR
!Version ArubaOS-CX Virtual.10.07.0010
hostname LHR
led locator on
ntp server pool.ntp.org minpoll 4 maxpoll 4 iburst
ntp enable
!
!
!
!
!
!
ssh server vrf mgmt
vlan 1,111
interface mgmt
no shutdown
ip dhcp
interface 1/1/1
no shutdown
no routing
vlan access 111
interface 1/1/2

11
 Lab Guide
PIM-SM Troubleshooting

no shutdown
ip address 192.168.4.5/31
ip ospf 1 area 0.0.0.0
ip pim-sparse enable
interface 1/1/3
no shutdown
interface 1/1/4
no shutdown
interface 1/1/5
no shutdown
interface 1/1/6
no shutdown
interface loopback 0
ip address 192.168.2.4/32
ip ospf 1 area 0.0.0.0
interface vlan 111
ip address 10.0.111.254/24
ip ospf 1 area 0.0.0.0
ip igmp enable
ip igmp static-group 239.10.10.10
ip pim-sparse enable
!
!
!
!
!
router ospf 1
area 0.0.0.0
router pim
enable
https-server vrf mgmt

12
www.arubanetworks.com
3333 Scott Blvd. Santa Clara, CA 95054
1.844.472.2782 | T: 1.408.227.4500 | FAX: 1.408.227.4550 | info@arubanetworks.com
13