Brkipm 2264 PDF

#CLUS
Multicast
Troubleshooting
BRKIPM-2264
Denise “Fish” Fishburne
Solutions Architect, CCIE #2639, CCDE 2009:0014
#CLUS
Agenda
• Quick Review
• Multicast Troubleshooting Methodology
• Troubleshooting ASM
• Troubleshooting SSM
• Final Troubleshooting Takeaways

#CLUS BRKIPM-2264 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 3
Cisco Webex Teams
Questions?
Use Cisco Webex Teams to chat
with the speaker after the session
How
1 Find this session in the Cisco Live Mobile App
2 Click “Join the Discussion”
3 Install Webex Teams or go directly to the team space
4 Enter messages/questions in the team space
Webex Teams will be moderated cs.co/ciscolivebot#BRKIPM-2264

by the speaker until June 16, 2019.
#CLUS © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 4
Housekeeping Items
• Cell Phones
• “Intermediate” Class
Assumes Multicast Operational Experience
• Questions
Quick Review
Quick Review Agenda
• Frequently Used Terms
• Tree Growth
• Sending a (*,G) PIM Join
• Registering a Source
• Designated Routers
Frequently Used Terms
ASM Any Source Multicast FHR First Hop Router
SSM Source Specific Multicast LHR Last Hop Router
MDT Multicast Distribution Tree IR Intermediate Router
RP Rendezvous Point DR Designated Router
IGMP Internet Group Management Protocol
PIM Protocol Independent Multicast
• Any Source Multicast (ASM)
• Original (Classic) PIM-SM
• Supports both Shared and Source Trees
• Source Specific Multicast (SSM)

• a.k.a. Single Source Multicast
• Supports only Source Trees
(*,G) = *,G
= Shared Tree
= RP tree
*,G MDT
RP
LHR
(S,G) = S,G
= Shortest Path Tree
= Source tree
S,G MDT
FHR
LHR
(*,G) = *,G
= Shared Tree
= RP tree
(S,G) = S,G
= Source Tree
= Shortest Path Tree
Q: What is the Root of the (*,G) Tree?

A: RP
Q: What is the Root of the (S,G) Tree?
A: Source
IIF Incoming Interface
Interface towards the root of the tree
OIL Outgoing Interface List
Interfaces that have received PIM Joins or IGMP membership requests
Q: What does the IIF of the (*,G) Tree point towards?

A: RP
Q: What does the IIF of the (S,G) Tree point towards?
A: Source
Tree Growth
Nature’s Way
In Nature, trees grow
• UP and
• OUT
from the ROOT
Tree Growth
Multicast Distribution Tree (MDT)
With Multicast, trees grow
• TOWARD
the ROOT
Sending a (*,G) PIM Join
10.4.5.0
.5 .4
PIM Join
Router A Router B RP
Question:
When Router A sends a PIM (*,G) Join out, what will be the Destination IP?
IP address of the RP? 224.0.0.13? IP of Router B?

(All PIM Routers) (10.4.5.4)
**Assume Router A knows the RP, has the RP in its RIB via an IGP with B and has a PIM
neighbor with Router B
The PIM Header
PIM header common to all PIM messages:
Some PIM Types are:

Message Type Destination
0 = Hello Multicast to ALL-PIM-ROUTERS
1 = Register Unicast to RP
2 = Register-Stop Unicast to source of Register packet
3 = Join/Prune Multicast to ALL-PIM-ROUTERS
4 = Bootstrap Multicast to ALL-PIM-ROUTERS
5 = Assert Multicast to ALL-PIM-ROUTERS
http://www.ietf.org/rfc/rfc4601.txt
10.4.5.0
.5 .4
Router A Router B RP
DIP: 224.0.0.13 PIM Join
Q: When Router A sends a PIM (*,G) Join out, what will be the Destination IP?
IP of the RP?
224.0.0.13? IP of Router B?
(All PIM Routers) (10.4.5.4)
A B
.5 10.4.5.0 .4
DIP: 224.0.0.13 PIM Join RP

.1
C
Question:
If the destination IP address of the Join is 224.0.0.13 (all PIM Routers), then
how do we keep Router B and Router C from BOTH acting on that join?
Sending a (*,G) Join
A B
.5 10.4.5.0 .4
DIP: 224.0.0.13 PIM Join RP

.1
C
Answer:
The address of the upstream neighbor (B or C) is the target of the message
http://www.ietf.org/rfc/rfc4601.txt
A B
.5 10.4.5.0 .4
PIM Join
.1
Destination IP
224.0.0.13
C
IP address of B
10.4.5.4
RP
2.2.2.2
***When a shared MDT is already
active for that group on the RP
Registering a Source*** RP = 2.2.2.2
gig0
FHR
Mcast packet is encapsulated into
Mcast Data unicast PIM packet:
Dest IP=RP PIM Mcast data Destination IP is the RP.
PIM header type is Register
gig0 added to the RP sends PIM (S,G) Join Back Towards Source
OIL for (S,G) if there is an active shared tree for that G
Mcast packets now get sent out twice:
Mcast Data 1. With Register
2. Out (S,G)
Once the RP sees the packets come in
Mcast Data on the (S,G),
Register Stop to the FHR …. it sends a unicast Register Stop
Mcast Data Mcast Data Mcast packets now only out the (S,G) tree
Designated Routers (DRs)
Router A
.3
Q: Which router should register the
Vlan
FHR source with the RP?
.2
A: The FHR that is the DR
Router B
Designated Routers (DRs)
.3
Q: Which router should send the PIM (*,G) Vlan

Join?
A: The LHR that is the DR .2
LHR
Multicast Troubleshooting Methodology
Multicast Troubleshooting Methodology Agenda
• The Plumbing
• Troubleshooting Toolbox
Building the Plumbing:
Unicast
EIGRP EIGRP EIGRP

R1 Subnet
R1 R1 R1
10.1.1.0/24
Ping advertise advertise advertise
10.1.1.0/24 10.1.1.0/24 10.1.1.0/24
10.1.1.1 10.1.1.1
Point A Point B
Building the Plumbing ***In this example, LHR is configured
Multicast*** to not cut over to the S,G tree.
PIM PIM PIM PIM

R1 R1 R1 R1
FHR RP PIM (*,G) PIM (*,G) LHR
Source PIM Unicast Register Join
Join Join
(Tx)
PIM (S,G) PIM (S,G)

Join Join
“In solving a problem of this sort, the grand
thing is to be able to reason backward.
That is a very useful accomplishment, and
a very easy one, but people do not
practice it much.”
Sherlock Holmes
Troubleshooting the ASM Plumbing
LHR
FHR RP
MDTs Built Backwards Towards Root
Traffic
Troubleshooting
Troubleshooting the SSM Plumbing
LHR
FHR
MDTs Built Backwards Towards Root
Traffic
Troubleshooting
Troubleshooting Toolbox
Facts to Remember
• Multicast Routing must be enabled globally
• PIM must be enabled on the interfaces for PIM neighbors to form
• Multicast Trees get built backwards towards the root
• Multicast traffic in ASM and SSM are triggered via a “pull”
• High on the “food chain” dependent on routing working and PIM working
Questions to Remember
 Who is the root?
 Where is the root?
 What is the PIM RPF neighbor towards the root?
Checklist
 IGMP Membership Report Received by LHR (IPv4)

 MLD Membership Report Received by LHR (IPv6)
 “WHO” is the root?
- Knowledge of who the RP is for that multicast group
 “WHERE” is the root?
- Check routing… check routing… check routing
 “WHAT” is the PIM RPF neighbor towards the root?
- Do you have a PIM neighbor?
“Go To” Commands
show ip mroute
show ip mroute count
show ip pim neighbor

show ip pim interface
show ip igmp group
show ip pim rp [group]

show ip pim rp mapping [group]
show ip rpf [address]
Our Environment
R3
NX 9372
R1 R2 R5
R1
C9300 ASR9001 C9300
FHR RP R4 LHR
NX 9372
ASM Troubleshooting
ASM Troubleshooting
R3
R3
R1
R1 R2
R2 R5R5
FHR RP LHR
R4
(*,G) from LHR towards the RP 1

FHR registers source with RP
2
RP sends PIM (S,G) Join
Towards Source
LHR Cutting over 3
to SPT (S,G)
ASM Troubleshooting
Shared Tree
R3
R3
R1
R1 R2
R2 R5R5
FHR RP LHR
R4
ASM Troubleshooting:
Shared Tree
R3
R3
R2
R2 R5R5
RP LHR
R4
1c 1b
1a
R4 (an IR) sends a PIM (*,G) LHR (R5) sends a PIM
to R2 (RP) (*,G) to R4 LHR receives
IGMP Membership Report

Shared Tree
R3
R3
R2
R2 R5R5
RP LHR
R4 1a
LHR receives
 IGMP Membership Report Received by LHR
 “WHO:” R5 (LHR) knows who the RP is for this group
 “WHERE:” R5 (LHR) knows where (RIB) the RP is
 “WHAT:” R5 (LHR) has a PIM Neighbor to send the PIM (*,G) Join to
ASM Troubleshooting: LHR
Shared Tree
R5
1a LHR Receives IGMP Membership Report
Group:
 IGMP Membership Report Received by LHR 239.1.1.1
R5#show ip mroute Is completely empty
R5#show ip igmp group Is completely empty
R5#show ip igmp interface Is completely empty
Shared Tree
R5
Group:
239.1.1.1
• PIM not enable on interface of Receiver
R5#show run interface gig1/0/5 interface GigabitEthernet1/0/5

no switchport
ip address 100.1.1.1 255.255.255.0
ip pim sparse-mode
Shared Tree
R5
Group:
239.1.1.1
R5#show ip mroute
(*, 224.0.1.40), 00:13:27/00:02:38, RP 0.0.0.0, flags: DCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
GigabitEthernet1/0/5, Forward/Sparse, 00:13:25/00:02:38
R5#show ip igmp groups
IGMP Connected Group Membership
Group Address Interface Uptime Expires Last Reporter
224.0.1.40 GigabitEthernet1/0/5 00:06:13 00:02:31 100.1.1.1
Shared Tree
R5
Group:
• PIM not enable on interface of Receiver 239.1.1.1
• Layer 1 issues
• Layer 2 issues
• Access-List
• IGMP membership report not being sent
Shared Tree
R5
Group:
✓
 IGMP Membership Report Received by LHR 239.1.1.1
R5#show ip igmp groups

IGMP Connected Group Membership
Group Address Interface Uptime Expires Last Reporter
R5#show ip mroute 239.1.1.1
(*, 239.1.1.1), 00:00:07/00:02:53, RP 0.0.0.0, flags: SJC
Shared Tree
1b LHR Sends PIM (*,G) Join R3
R3
R2
R2 R5R5
RP LHR
R4
1b
LHR (R5) sends a PIM (*,G)
To R4
 “WHO:” R5 (LHR) knows who the RP is for this group
 “WHERE:” R5 (LHR) knows where (RIB) the RP is
 “WHAT:” R5 (LHR) has a PIM Neighbor to send the PIM (*,G) Join to
Shared Tree R3
R3
1b LHR Sends PIM (*,G) Join

R2
R2 R5R5
RP
?? Who? RP LHR
Where? R4
RPF Nbr?
R5#show ip mroute 239.1.1.1 ?
(*, 239.1.1.1), 00:00:07/00:02:53, RP 0.0.0.0, flags: SJC
R5#show ip pim rp 239.1.1.1 ?
Group: 239.1.1.1, RP: 0.0.0.0
Shared Tree R3
R3

R2
R2 R5R5
Note:
RP information can be shared 3 ways RP LHR
• Static R4
• Auto-RP
• BSR
R5(config)#ip pim rp-address 2.2.2.2 ?
<1-99> Access-list reference for group
<1300-1999> Access-list reference for group (expanded range)
WORD IP Named Standard Access list
override Overrides dynamically learnt RP mappings
<cr>
R5(config)#ip pim rp-address 2.2.2.2 override
Shared Tree R3
R3

R2
R2 R5R5
RP
✓
Who?
RP
R4
LHR
Where?
RPF Nbr?
R5#sh ip pim rp 239.1.1.1

Group: 239.1.1.1, RP: 2.2.2.2, uptime 00:00:39, expires never
R5#sh ip pim rp mapping 239.1.1.1

PIM Group-to-RP Mappings
Group(s): 224.0.0.0/4, Static-Override
RP: 2.2.2.2 (?)
Shared Tree R3
R3

R2
R2 R5R5
RP
✓
?? Who? RP
R4
LHR
Where?
RPF Nbr?
R5#show ip mroute 239.1.1.1 ✓

(*, 239.1.1.1), 00:08:18/00:02:46, RP 2.2.2.2, flags: SJC
Incoming interface: Null, RPF nbr 0.0.0.0 ??
R5#show ip rpf 2.2.2.2 R5#show ip route 2.2.2.2

failed, no route exists % Network not in table
Shared Tree R3
R3

R2
R2 R5R5
RP
✓
Who?
RP LHR
✓
Where?
R4
RPF Nbr?
R5#show ip route 2.2.2.2

Routing entry for 2.2.2.2/32
Known via "ospf 100", distance 110, metric 42, type intra area
Last update from 10.2.5.3 on GigabitEthernet1/0/1, 00:00:06 ago
Routing Descriptor Blocks:
10.4.5.4, from 2.2.2.2, 00:00:09 ago, via GigabitEthernet1/0/2
10.2.5.3, from 2.2.2.2, 00:00:06 ago, via GigabitEthernet1/0/1
Shared Tree R3
R3

R2
R2 R5R5
RP
✓
Who?
RP LHR
✓
Where?
R4
RPF Nbr?

(*, 239.1.1.1), 00:08:18/00:02:46, RP 2.2.2.2, flags: SJC
Shared Tree R3
R3

R2
R2 R5R5
RP
✓
Who?
RP LHR
✓
Where?
R4
?? RPF Nbr?
R5#show ip rpf 2.2.2.2

failed, no route exists
R5#show ip pim neighbor

No PIM neighbors listed
Shared Tree R3
R3

R2
R2 R5R5
RP LHR
R4
R5#show ip pim neighbor

PIM Neighbor Table
Mode: B - Bidir Capable, DR - Designated Router, N - Default DR Priority,
P - Proxy Capable, S - State Refresh Capable
Neighbor Interface Uptime/Expires
10.2.5.3 GigabitEthernet1/0/1 00:00:07/00:01:42
10.4.5.4 GigabitEthernet1/0/2 00:00:07/00:01:39
Shared Tree R3
R3

R2
R2 R5R5
Question:
Why was 10.4.5.4 chosen as the RPF neighbor?
RP LHR
Answer: R4
If ECMP are available, the RPF for the multicast
traffic will be based on highest IP address for
the RPF neighbor
R5#show ip rpf 2.2.2.2

RPF information for ? (2.2.2.2)
RPF interface: GigabitEthernet1/0/2
RPF neighbor: ? (10.4.5.4)
RPF route/mask: 2.2.2.2/32
RPF type: unicast (ospf 100)
Doing distance-preferred lookups across tables
RPF topology: ipv4 multicast base, originated from ipv4 unicast base
Shared Tree R3
R3

R2
R2 R5R5
RP
✓
Note:
LHR now has all the
✓
Who?
information it needs to send
Where? RP LHR
a PIM (*,G) join to its RPF
neighbor. ✓
RPF Nbr?
R4 1b
LHR (R5) sends a PIM
(*,G) To R4
R5#show ip mroute 239.1.1.1 RP flags

*,G (*, 239.1.1.1), 01:33:55/00:02:13, RP 2.2.2.2, flags: SJC
IIF Incoming interface: GigabitEthernet1/0/2, RPF nbr 10.4.5.4
OIL Outgoing interface list: RPF nbr
Shared Tree R3
R3
1c IR Sends PIM (*,G) Join

R2
R2 R5R5
RP LHR
R4
R4 (an IR) sends a PIM (*,G) 1c

To R2 (RP)
 “WHO:” R4 (IR) knows who the RP is for this group

 “WHERE:” R4 (IR) knows where (RIB) the RP is
 “WHAT:” R4 (IR) has a PIM Neighbor to send the PIM (*,G) Join to
Shared Tree R3
R3

R2
R2 R5R5
Note:
Telnetting backwards towards the
root is a good way to troubleshoot. RP LHR
R4

RP
(*, 239.1.1.1), 01:33:55/00:02:13, RP 2.2.2.2, flags: SJC
✓ Who?
✓
Incoming interface: GigabitEthernet1/0/2, RPF nbr 10.4.5.4
Outgoing interface list: Where?
R5#telnet 10.4.5.4
✓ RPF Nbr?
Trying 10.4.5.4 ... Open
(*, 239.1.1.1/32), uptime: 00:00:01, pim ip R5
Incoming interface: Ethernet1/1, RPF nbr: 10.2.4.2, uptime: 00:00:01
Outgoing interface list: (count: 1)
Ethernet1/2, uptime: 00:00:01, pim
Shared Tree R3
R3

R2
R2 R5R5
Note:
R4 had all the information it needed
to send a PIM (*,G) join its RPF RP LHR
neighbor. R4
R4 (an IR)
sent a PIM (*,G) 1c
R4#telnet 10.2.4.2
To R2 (RP)
Trying 10.2.4.2... Open
R2#show mrib route 239.1.1.1
(*,239.1.1.1) RPF nbr: 0.0.0.0 Flags: C RPF
Up: 00:09:19
Outgoing Interface List
GigabitEthernet0/0/0/2 Flags: F NS, Up: 00:09:19
Shared Tree
R3
R3
RP LHR
R2
R2 R5R5
1c 1a
R4
1b LHR receives
R4 (an IR) sends a PIM (*,G)
To R2 (RP) LHR (R5) sends a
PIM (*,G) to R4
(*,G) Between RP and LHR
✓ (*,G) from LHR towards the RP 1

ASM Troubleshooting
R3
R3
R1
R1 R2
R2 R5R5
RP
✓
FHR LHR
R4
(*,G) from LHR towards the RP

1
2 FHR registers source with RP

3
RP sends PIM (S,G) Join Towards Source
LHR Cutting over to SPT (S,G)
ASM Troubleshooting
R3
R3
R1
R1 R2
R2 R5R5
FHR RP LHR
R4

3
Source Tree
R1
R1 R2
R2
2a FHR RP
FHR receives 2b
Multicast Data FHR registers source with RP
2c
RP builds S,G Back Towards Source

2
***When a shared MDT is already active for that group on the RP

Source Tree
R1
R1 R2
R2
2a FHR RP
FHR receives 2b
2c

2

Source Tree
2a FHR Receives Multicast Data
R1
R1 R2
R2
FHR RP
2a
FHR receives
Multicast Data
2a
FHR receives Multicast Data
Source Tree R1
R1 R2
R2
2a FHR Receives Multicast Data S: 200.1.1.100 RP
FHR
G: 239.1.1.1
R2
 FHR Receives Multicast Data 2a
FHR receives
Multicast Data
R1#show ip mroute Has 224.0.1.40 but not 239.1.1.1
R1#sh int gig1/0/5 counters

Port InOctets InUcastPkts InMcastPkts InBcastPkts
Gi1/0/5 34006016 0 66418 0
Port OutOctets OutUcastPkts OutMcastPkts OutBcastPkts

Gi1/0/5 12102 71 49 0
Source Tree R1
R1 R2
R2
2a FHR Receives Multicast Data S: 200.1.1.100 RP
FHR
G: 239.1.1.1
R1 R2
 FHR Receives Multicast Data 2a
FHR receives
Multicast Data
R1# sh run | include access-list
access-list 2239 permit ip any host 239.1.1.1
R1# debug ip packet 2239 detail
IP packet debugging is on (detailed) for access list 2239
May 22 21:17:55.190: FIBipv4-packet-proc: route packet from GigabitEthernet1/0/5
src 200.1.1.100 dst 239.1.1.1
May 22 21:17:55.190: FIBfwd-proc: Default:224.0.0.0/4 multicast entry
May 22 21:17:55.190: FIBipv4-packet-proc: packet routing failed
Source Tree
R1
R1 R2
R2
2a FHR RP
FHR receives 2b
2c

2

Source Tree
2b FHR Receives Source with RP
R1
R1 R2
R2
FHR RP
2b
2b
Source Tree R1
R1 R2
R2
2b FHR Registers Source with RP S: 200.1.1.100
FHR RP
Question: G: 239.1.1.1
RP
Who? Why is there no (S,G) or (*,G)?
Where?
RPF Nbr?
R1#sh ip rpf 200.1.1.100 ✓ R1#sh ip rpf 2.2.2.2 ??

RPF information for ? (200.1.1.100) failed, no route exists
RPF interface: GigabitEthernet1/0/5
RPF neighbor: ? (200.1.1.100) - directly connected
RPF route/mask: 200.1.1.0/24
RPF type: multicast (connected)
Doing distance-preferred lookups across tables
RPF topology: ipv4 multicast base
Source Tree R1
R1 R2
R2
FHR RP
Problem: G: 239.1.1.1
RP
?? Who? FHR does not know who the
Where? RP is for this group.
RPF Nbr?
R1# sh ip pim rp mapping 239.1.1.1

?? PIM Group-to-RP Mappings
R1#
R1#sh ip rpf 2.2.2.2
failed, no route exists
Source Tree R1
R1 R2
R2
FHR RP
Note: G: 239.1.1.1
RP
✓
Who? RP information can be shared 3
Where? ways: • Static
RPF Nbr? • Auto-rp
• BSR
“ip pim rp-address 2.2.2.2 override” R1#sh ip pim rp mapping 239.1.1.1

PIM Group-to-RP Mappings
Group(s): 224.0.0.0/4, Static-Override

RP: 2.2.2.2 (?)
Source Tree R1
R1 R2
R2
FHR RP
G: 239.1.1.1
RP
✓
Who?
Where?
RPF Nbr?

(*, 239.1.1.1), 00:11:09/stopped, RP 2.2.2.2, flags: SPF
Outgoing interface list: Null
(200.1.1.100, 239.1.1.1), 00:02:30/00:00:29, flags: PFT
Incoming interface: GigabitEthernet1/0/5, RPF nbr 0.0.0.0, Registering
Source Tree R1
R1 R2
R2
FHR RP
Problem: G: 239.1.1.1
RP
✓
Who? FHR doesn’t know who the RPF
✓
Where? neighbor is for the shared tree for
this group.
RPF Nbr?
R1#show ip route 2.2.2.2 2.0.0.0/32 is subnetted, 1 subnets

O 2.2.2.2 [110/2] via 10.1.2.2, 01:11:17, Gig1/0/1
R1#show ip rpf 2.2.2.2 ?? RPF information for ? (2.2.2.2) failed, no route exists
R1#show ip pim neighbor No PIM neighbors
Source Tree R1
R1 R2
R2
FHR RP
Note: G: 239.1.1.1
“ip pim sparse-mode” added to
Gig 1/0/1 on FHR (R1)

(200.1.1.100, 239.1.1.1), 00:02:32/00:00:27, flags: PFT
✓
Incoming interface: GigabitEthernet1/0/5, RPF nbr 0.0.0.0, Registering (data-header)
Source Tree
R1
R1 R2
R2
2a FHR RP
FHR receives 2b
2c

2

Source Tree
R1
R1 R2
R2
FHR RP
2c
Source Tree R1
R1 R2
R2
2c RP builds S,G Back S: 200.1.1.100
FHR RP
Towards Source G: 239.1.1.1
Problem:
(S,G) stuck in “registering” on
FHR (R1)

(200.1.1.100, 239.1.1.1), 00:02:32/00:00:27, flags: PFT
Incoming interface: GigabitEthernet1/0/5, RPF nbr 0.0.0.0, Registering (data-header)
Source Tree R1 R2
R2
FHR RP
Question: Note:
Why is the FHR stuck in “registering”? S,G tree will get built backwards from
the RP.
Clue: So troubleshoot backwards from the
RP.
OIL on FHR for (S,G) is null
R2#show pim rpf 200.1.1.100

* 200.1.1.100/32
via Null with rpf neighbor 0.0.0.0
R2#show route 200.1.1.100

% Network not in table
Source Tree R1 R2
R2
Question:
Why is the FHR stuck in “registering”? FHR RP
Mcast packet is encapsulated into

Mcast data unicast PIM packet:
Dest IP=RP PIM Mcast data Destination IP is the RP.
PIM header type is Register
RP sends PIM (S,G) Join Back Towards

Source if there is an active shared tree for
Mcast data that G
Once the RP sees the packets come in on
the (S,G), it sends a unicast Register Stop
Register Stop to the FHR
Source Tree R1 R2
R2
FHR RP
Source Problem:
✓
Who? RP doesn’t know where the
Where? Source is for this group.
RPF Nbr?
Issue:
Source address not in RIB of RP –
routing problem

* 200.1.1.100/32 [-1/-1]
via Null with rpf neighbor 0.0.0.0
R2#show route 200.1.1.100
% Network not in table
Source Tree R1 R2
R2
S: 200.1.1.100 RP
FHR
Source Note: G: 239.1.1.1
✓
Who? Fix routing problem. RP now
✓
Where? has Source in its RIB.
✓
RPF Nbr?

Table: IPv4-Unicast-default
* 200.1.1.100/32 [110/2]
via GigabitEthernet0/0/0/0 with rpf neighbor 10.1.2.1
Source Tree R1 R2
R2
S: 200.1.1.100 RP
FHR
Source Note: G: 239.1.1.1
✓
Who? Fix routing problem. RP now
✓
Where? has Source in its RIB.
✓
RPF Nbr?
R2#show mrib route 239.1.1.1

(*,239.1.1.1) RPF nbr: 2.2.2.2 Flags: C RPF
Up: 00:36:30
Incoming Interface List
Decapstunnel0 Flags: A, Up: 00:36:30
(200.1.1.100,239.1.1.1) RPF nbr: 10.1.2.1 Flags: L RPF
Up: 00:13:06
GigabitEthernet0/0/0/0 Flags: A, Up: 00:02:08
ASM Troubleshooting
Source
Source Tree Tree R1
R1 R2
R2
FHR RP
Note:
Going back to FHR (R1) with this
issue fixed, we now see that the
(S,G) is no longer stuck in registering.
R1#show ip mroute
(200.1.1.100, 239.1.1.1), 00:16:42/00:02:41, flags: FT
Source Tree
FHR RP
S: 200.1.1.100
G: 239.1.1.1
Registering of Source to the RP
Mcast data
RP Wants to Join (S,G)

Potential Reasons for “Black Hole”
1. Source not known in IGP at RP or some IR on the way back to the source (this is
the situation we just covered)
2. Usual suspects for any kind of packet loss (physical, firewall, ACL, etc)
3. Missing PIM Neighbor Relationship
4. Multicast Boundary Configured for this Multicast Group
ASM Troubleshooting
Source Tree
R1
R1 R2
R2
S: 200.1.1.100 FHR RP
G: 239.1.1.1
2 Registering of Source to the RP
RP building S,G Back Towards Source

(S,G) Between RP and FHR
#CLUS BRKIPM-2264
✓
© 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 87
ASM Troubleshooting
R3
R3
R1
R1 R2
R2 R5R5
✓
FHR RP LHR
R4

3
ASM Troubleshooting
R3
R3
R1
R1 R2
R2 R5R5
FHR RP LHR
R4

✓
✓ 2 FHR registers source with RP

3
The default behavior of PIM-SM is that routers
with directly connected members will join the
shortest path tree as soon as they detect a
new multicast source.”
PIM-SM Frequently Forgotten Fact
ASM Troubleshooting
R3
R3
R1
R1 R2
R2 R5R5
FHR RP LHR
R4

3
ASM Troubleshooting
Joining the SPT
R3
R3
R1
R1 R2
R2 R5R5
R4
3
--If SPT Threshold is not infinity (default 0) when the mcast stream comes down
the shared tree and into the LHR,
--then the LHR will try to cutover to the shortest path tree
ASM Troubleshooting
Joining the SPT
3 LHR Cuts over to the SPT R3
R3
R1
R1 R2
R2 R5R5
R4
3
Source
LHR Now must answer 3 questions Who?
before sending PIM (S,G) Join Where?
RPF Nbr?
ASM Troubleshooting
Joining the SPT
3 LHR Cuts over to the SPT R3
R3
R1
R1 R2
R2 R5R5
R4
3
(S,G) Between LHR and FHR
✓ #CLUS BRKIPM-2264 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 94
ASM Designated Routers
Receivers
Last Hop Designated Router Responsibilities
The LH DR is responsible for sending the PIM
(*,G) Join towards the RP
.3
The LH DR will also be responsible for cutting
over to the (S,G) tree Vlan
.2
LHR
ASM Designated Routers
Sources
First Hop Designated Router Responsibilities
The FH DR is responsible for registering the Source/Group with the RP
Router A
.3
Vlan
FHR
.2
Router B
ASM Troubleshooting
R3
R3
R1
R1 R2
R2 R5R5
R4
2 Registering of Source to the RP

3
Troubleshooting the ASM Plumbing
LHR
FHR RP
SSM Specific Troubleshooting
Checklist
 Multicast Group not defined as “SSM” in

some device in the path R3
R3
R1
R1 R2
R2 R5R5
gig1/0/5
R4
 IGMP Version 3 not enabled (IPv4)

 MLD Version 2 not enabled (IPv6)
R3
R3
R1
R1 R2
R2 R5R5
R4
(S,G) from LHR towards Source
LHR receives
IGMPv3 Membership Report
R3
R3
ssm1
R1
R1 R2
R2 R5R5
ssm4
R4 ssm2
R2 (IR) send (S,G) Join to R1(FHR) ssm3
LHR (R5) sends a PIM (S,G)
R4 (IR) send (S,G) Join to R2 To R4
ssm1 LHR Receives IGMPv3 Membership Report
LHR receives
R3
R3
ssm1
R1
R1 R2
R2 R5R5
R4
ssm1 LHR Receives IGMPv3 Membership Report R5
R5
 PIM Enabled ssm1

 IGMP Version 3 enabled LHR receives
R5#show run int gig1/0/5

interface GigabitEthernet1/0/5
no switchport
ip address 100.1.1.1 255.255.255.0
ip pim sparse-mode
ip igmp version 3
ssm1 LHR Receives IGMPv3 Membership Report R5
R5
 PIM Enabled ssm1

 IGMP Version 3 enabled LHR receives

(*, 232.1.1.1), 00:01:11/00:01:59, RP 2.2.2.2, flags: SJC
ssm2 LHR Send (S,G) Join
R3
R3
R1
R1 R2
R2 R5R5
R4
ssm2
LHR (R5) sends a PIM (S,G)

To R4
SSM Specific Troubleshooting R3
R3
Problem:
LHR is configured for this group
R2
R2 R5R5
to be an ASM group, not an
SSM group. LHR
Mode of Group R4
ASM
SSM
R5#show ip mroute ssm Is completely empty

Flags:
R5#show ip mroute D - Dense
?? S - Sparse
(*, 232.1.1.1), 00:01:11/00:01:59, RP 2.2.2.2, flags: SJC
Incoming interface: GigabitEthernet1/0/2, RPF nbr 10.4.5.4 B - Bidir Group
Outgoing interface list: s - SSM Group
R3
Note:
Some platforms (XR) have the
R2
R2 R5R5
232/8 group as SSM by default.
In IOS it must be configured. LHR
Mode of Group If SSM Source R4
ASM Who?
SSM Where?
RPF Nbr?
R5(config)#ip pim ssm ?
default Use 232/8 group range for SSM
range ACL for group range to be used for SSM
R5(config)#ip pim ssm default
“232.0.0.0-232.255.255.255 (232/8) Source-Specific Multicast Block”
-- http://www.iana.org/assignments/multicast-addresses/
R3
R2
R2 R5R5
LHR
R4
Question:
Assuming equal cost paths to the source from the LHR through R3 and R4,
which router will the LHR use as its RPF neighbor?
R3
Note:
With this group now an SSM group, the
R2
R2 R5R5
LHR asks itself where is the Source and
who is the RPF nbr for this source? Then LHR
it sends the (S,G) Join. R4
Mode of Group If SSM Source PIM (S,G)
 ASM ✓
 Where? Join Sent
✓
 SSM ✓
 RPF Nbr?
R5#show ip mroute 232.1.1.1 S - SSM Group
(200.1.1.100, 232.1.1.1), 00:04:44/00:02:19, flags: sTI T - SPT-bit set
I - Received Source
Specific Host Report
ssm3 IR (R4) Sends (S,G) Join
R3
R3
R1
R1 R2
R2 R5R5
ssm3 R4
R4 (IR) send (S,G) Join to R2
R3
Problem:
IR is configured for this group to
R2
R2 R5R5
be an ASM group, not an SSM
group. LHR
Mode of Group R4
ASM
SSM
R4#show ip mroute
(200.1.1.100/32, 232.1.1.1/32), uptime: 00:15:59, pim ip
R4#sh run | include ssm
ip pim ssm range 232.0.0.0/8
R4#
R3
Note:
With this group now an SSM group, the IR
R2
R2 R5R5
(R4) asks itself where is the Source and
who is the RPF nbr for this source. Then LHR
it sends the (S,G) Join. R4
Mode of Group If SSM Source
ASM ✓
Where?
✓SSM ✓
RPF Nbr?
R4#show ip mroute
(200.1.1.100/32, 232.1.1.1/32), uptime: 00:15:59, pim ip
R3
R3
R1
R1 R2
R2 R5R5
ssm4
R4
R2 (IR) send (S,G) join
to R1(FHR)
R3
R1
R2
R2 R5R5
Note:
XR has a very useful
command ”show pim R2 receives R4
group map”
PIM (S,G) Join
R2#show pim group-map
IP PIM Group Mapping Table
(* indicates group mappings being used)
(+ indicates BSR group mappings active in MRIB)
Group Range Proto Client Groups RP address Info
224.0.1.39/32* DM perm 0 0.0.0.0
224.0.1.40/32* DM perm 1 0.0.0.0
224.0.0.0/24* NO perm 0 0.0.0.0
232.0.0.0/8* SSM config 1 0.0.0.0
224.0.0.0/4* SM config 0 2.2.2.2 RPF: De0,2.2.2.2 (us)
224.0.0.0/4 SM static 0 0.0.0.0 RPF: Null,0.0.0.0
R3
Note:
IR (R2) asks itself where is the Source R1 R2 R5
and who is the RPF nbr for this source.
Then it sends the (S,G) Join.
Mode of Group If SSM Source R4
✓ R2 sends
ASM Where?
✓
SSM ✓
RPF Nbr? PIM (S,G) Join
R2#show mrib ipv4 route 232.1.1.1

(200.1.1.100,232.1.1.1) RPF nbr: 10.1.2.1 Flags: RPF
Up: 00:17:34
GigabitEthernet0/0/0/0 Flags: A, Up: 00:17:34
R1 R2 R5
Mode of Group If SSM Source

ASM Where?
R4
R2 sends
SSM RPF Nbr? PIM (S,G) Join
(200.1.1.100, 232.1.1.1), 00:01:17/00:01:42, flags: FT

Incoming interface: GigabitEthernet1/0/5, RPF nbr 0.0.0.0, Registering
Note: R1 R2 R5
(S,G) MDT built all the way from the
LHR to the FHR. But note how no
traffic has yet been sent from the R4
source. R2 sends
PIM (S,G) Join
(200.1.1.100, 232.1.1.1), 00:01:23/00:03:06, flags: sT

Note: R1 R2 R5
(S,G) MDT built all the way from the
LHR to the FHR. But note how no
traffic has yet been sent from the R4
source. R2 sends
PIM (S,G) Join
(200.1.1.100, 232.1.1.1), 00:01:23/00:03:06, flags: sT
R1#show ip mroute 232.1.1.1 count
Group: 232.1.1.1, Source count: 1, Packets forwarded: 0, Packets received: 0
Source: 200.1.1.100/32, Forwarding: 0/0/0/0, Other: 0/0/0
ssm1
R3
R3 LHR receives
R1
R1 R2
R2 R5R5
ssm4 R4
R2 (IR) send (S,G) Join to R1(FHR) ssm2
ssm3
LHR (R5) sends a PIM (*,G)
R4 (IR) send (S,G) Join to R2 To R4
Final Troubleshooting Takeaways
Facts to Remember
• Multicast Trees get built backwards towards the root
• Multicast traffic in ASM and SSM are triggered via a “pull”
• High on the “food chain” dependent on routing working and PIM working
Questions to Remember
• Who is the root?
• Where is the root?
• What is the PIM RPF neighbor towards the root?
Checklist

 “WHO:” is the root?
 “WHERE” is the root?
 “WHAT” is the PIM RPF neighbor towards the root?
NO Receivers Getting Mcast
FHR RP
LHR
Start at RP for this Group
 *,G w/ OIL?
• NO? Pick 1 LHR and start there
 S,G
• NO? Go to FHR
Some Receivers Getting Mcast
FHR RP
LHR
Start at LHR of Broken Receiver

 Pull?
 Who, Where, What
SSM Troubleshooting with Fish LHR
FHR
Start at FHR
 S,G w/ OIL?
• NO? Pick 1 LHR and start there
• YES? Check to see if traffic coming in from Source
Questions?
Complete your
online session • Please complete your session survey
evaluation after each session. Your feedback
is very important.
• Complete a minimum of 4 session
surveys and the Overall Conference
survey (starting on Thursday) to
receive your Cisco Live water bottle.
• All surveys can be taken in the Cisco Live
Mobile App or by logging in to the Session
Catalog on ciscolive.cisco.com/us.
Cisco Live sessions will be available for viewing
on demand after the event at ciscolive.cisco.com.
Continue your education
Demos in the
Walk-in labs
Cisco campus
Meet the engineer

Related sessions
1:1 meetings
#CLUS BRKACI-3456 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 130
Thank you
#CLUS
#CLUS

Brkipm 2264 PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Brkipm 2264 PDF

Hochgeladen von

Copyright:

Verfügbare Formate

#CLUS

• Multicast Troubleshooting Methodology

• Final Troubleshooting Takeaways

Webex Teams will be moderated cs.co/ciscolivebot#BRKIPM-2264

• Sending a (*,G) PIM Join

ASM Any Source Multicast FHR First Hop Router

SSM Source Specific Multicast LHR Last Hop Router

MDT Multicast Distribution Tree IR Intermediate Router

RP Rendezvous Point DR Designated Router

IGMP Internet Group Management Protocol

PIM Protocol Independent Multicast

• Source Specific Multicast (SSM)

Q: What is the Root of the (*,G) Tree?

Interface towards the root of the tree

OIL Outgoing Interface List

Interfaces that have received PIM Joins or IGMP membership requests

Q: What does the IIF of the (*,G) Tree point towards?

In Nature, trees grow

from the ROOT

With Multicast, trees grow

IP address of the RP? 224.0.0.13? IP of Router B?

Some PIM Types are:

DIP: 224.0.0.13 PIM Join RP

DIP: 224.0.0.13 PIM Join RP

Q: Which router should send the PIM (*,G) Vlan

EIGRP EIGRP EIGRP

PIM PIM PIM PIM

PIM (S,G) PIM (S,G)

MDTs Built Backwards Towards Root

MDTs Built Backwards Towards Root

• Multicast Routing must be enabled globally

• PIM must be enabled on the interfaces for PIM neighbors to form

• Multicast Trees get built backwards towards the root

• Multicast traffic in ASM and SSM are triggered via a “pull”

 Who is the root?

 Where is the root?

 What is the PIM RPF neighbor towards the root?

 IGMP Membership Report Received by LHR (IPv4)

show ip pim neighbor

show ip igmp group

show ip pim rp [group]

(*,G) from LHR towards the RP 1

(*,G) from LHR towards the RP 1

(*,G) from LHR towards the RP 1

R5#show ip mroute Is completely empty

R5#show ip igmp group Is completely empty

R5#show ip igmp interface Is completely empty

R5#show run interface gig1/0/5 interface GigabitEthernet1/0/5

R5#show ip igmp groups

1b LHR Sends PIM (*,G) Join

1b LHR Sends PIM (*,G) Join

1b LHR Sends PIM (*,G) Join

R5#sh ip pim rp 239.1.1.1

R5#sh ip pim rp mapping 239.1.1.1

1b LHR Sends PIM (*,G) Join

R5#show ip mroute 239.1.1.1 ✓

R5#show ip rpf 2.2.2.2 R5#show ip route 2.2.2.2

1b LHR Sends PIM (*,G) Join

R5#show ip route 2.2.2.2

1b LHR Sends PIM (*,G) Join

R5#show ip mroute 239.1.1.1

1b LHR Sends PIM (*,G) Join

R5#show ip rpf 2.2.2.2