Re: IP PIM dense Prune

gd.dhiman · ‎06-19-2022

Hello Everyone,

I am working on PIM Dense ( refer to attached topology )

The source is directly connected to R5 and receiver is connected to R6. and the topology is running OSPF with area 0.

Unicast routing is fine.

The receiver is configured with " IP igmp join-group 231.1.1.1 )

When Source sends the ICMP packets to 231.1.1.1, R5 forwards the packet to S1, however, S1 put outgoing Interface ( VLAN 1) in Prune State ( after some time, say after 3 to 4 ICMP packets ) as a result is not forwarding the packets any further.

Please advise, how this can be fixed. Thank you so much in advance

Refer below outputs

++++++++++++++++

(R5 - Source is directly connected to Interface E0/1)

Router#show run int e0/1
Building configuration...

Current configuration : 102 bytes
!
interface Ethernet0/1
ip address 192.168.170.10 255.255.255.0
ip pim dense-mode
duplex auto
end

Router#show run int e0/0
Building configuration...

Current configuration : 98 bytes
!
interface Ethernet0/0
ip address 10.229.0.1 255.255.255.0
ip pim dense-mode
duplex auto
end

Router#sh clo
*02:10:54.768 UTC Mon Jun 20 2022

Router#show ip mroute
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
L - Local, P - Pruned, R - RP-bit set, F - Register flag,
T - SPT-bit set, J - Join SPT, M - MSDP created entry, E - Extranet,
X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
U - URD, I - Received Source Specific Host Report,
Z - Multicast Tunnel, z - MDT-data group sender,
Y - Joined MDT-data group, y - Sending to MDT-data group,
G - Received BGP C-Mroute, g - Sent BGP C-Mroute,
N - Received BGP Shared-Tree Prune, n - BGP C-Mroute suppressed,
Q - Received BGP S-A Route, q - Sent BGP S-A Route,
V - RD & Vector, v - Vector, p - PIM Joins on route,
x - VxLAN group
Outgoing interface flags: H - Hardware switched, A - Assert winner, p - PIM Join
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode

(*, 231.1.1.1), 00:00:39/stopped, RP 0.0.0.0, flags: D
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Ethernet0/0, Forward/Dense, 00:00:39/stopped

(192.168.170.20, 231.1.1.1), 00:00:39/00:02:20, flags: T
Incoming interface: Ethernet0/1, RPF nbr 0.0.0.0
Outgoing interface list:
Ethernet0/0, Forward/Dense, 00:00:39/stopped, A

(*, 224.0.1.40), 00:00:42/00:02:53, RP 0.0.0.0, flags: DCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Ethernet0/0, Forward/Dense, 00:00:42/stopped

Router#

+++++++++++++++++++++++++++++++++++++++++++++++

S1

Switch#show ip int br | inc Vl
Vlan1 10.229.0.2 YES NVRAM up up
Vlan2 10.229.1.1 YES NVRAM up up
Vlan5 192.168.200.101 YES NVRAM administratively down down
Switch#show run int vlan 1
Building configuration...

Current configuration : 79 bytes
!
interface Vlan1
ip address 10.229.0.2 255.255.255.0
ip pim dense-mode
end

Switch#show run int vlan 2
Building configuration...

Current configuration : 79 bytes
!
interface Vlan2
ip address 10.229.1.1 255.255.255.0
ip pim dense-mode
end

Switch#show ip mroute
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
L - Local, P - Pruned, R - RP-bit set, F - Register flag,
T - SPT-bit set, J - Join SPT, M - MSDP created entry, E - Extranet,
X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
U - URD, I - Received Source Specific Host Report,
Z - Multicast Tunnel, z - MDT-data group sender,
Y - Joined MDT-data group, y - Sending to MDT-data group,
G - Received BGP C-Mroute, g - Sent BGP C-Mroute,
N - Received BGP Shared-Tree Prune, n - BGP C-Mroute suppressed,
Q - Received BGP S-A Route, q - Sent BGP S-A Route,
V - RD & Vector, v - Vector, p - PIM Joins on route,
x - VxLAN group
Outgoing interface flags: H - Hardware switched, A - Assert winner, p - PIM Join
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode

(*, 231.1.1.1), 00:02:20/stopped, RP 0.0.0.0, flags: D
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Vlan2, Forward/Dense, 00:02:20/stopped
Vlan1, Forward/Dense, 00:02:20/stopped

(192.168.170.20, 231.1.1.1), 00:02:20/00:00:39, flags: PT
Incoming interface: Vlan1, RPF nbr 10.229.0.1
Outgoing interface list:
Vlan2, Prune/Dense, 00:00:47/00:02:57

(*, 224.0.1.40), 00:02:04/00:02:55, RP 0.0.0.0, flags: DC
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Vlan2, Forward/Dense, 00:02:04/stopped
Vlan1, Forward/Dense, 00:02:04/stopped

Switch#sh clo
*02:18:00.569 UTC Mon Jun 20 2022
Switch#

R6 ( where receiver is connected directly )

Router#show ip igmp groups
IGMP Connected Group Membership
Group Address Interface Uptime Expires Last Reporter Group Accounted
231.1.1.1 Ethernet0/1 02:04:19 00:02:13 192.168.160.50
224.0.1.40 Ethernet0/0 02:16:52 00:02:07 10.229.0.1
Router#
Router#
Router#sh clo
*02:19:49.747 UTC Mon Jun 20 2022
Router#

paul driver · ‎06-20-2022

Hello

@gd.dhiman wrote:

Unicast routing is fine.

From the look of your topology you should not be incurring any rpf and you state uncast routing is fine, so check the mc packets to see where the failure is.

traceroute 192.168.170.20 numeric
sh ip rpf 192.168.170.20
sh ip pim interface count | B address

Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul

gd.dhiman · ‎06-20-2022

Hi Paul,

I run the requested commands on R6, R5 ( where Source is connected ), and S1, But I couldn't find something fishy.

R6#traceroute 192.168.170.20 numeric
Type escape sequence to abort.
Tracing the route to 192.168.170.20
VRF info: (vrf in name/id, vrf out name/id)
1 10.229.4.2 0 msec 0 msec 0 msec
2 10.229.3.1 0 msec 0 msec 1 msec
3 10.229.2.1 1 msec 1 msec 1 msec
4 10.229.1.1 1 msec 2 msec 1 msec
5 10.229.0.1 2 msec 2 msec 2 msec
6 192.168.170.20 1 msec 2 msec 3 msec
R6#sh ip rpf 192.168.170.2
RPF information for ? (192.168.170.2)
RPF interface: Ethernet0/0
RPF neighbor: ? (10.229.4.2)
RPF route/mask: 192.168.170.0/24
RPF type: unicast (ospf 1)
Doing distance-preferred lookups across tables
RPF topology: ipv4 multicast base, originated from ipv4 unicast base
R6#sh ip pim interface count | B address
R6#sh clo
*13:54:32.643 UTC Mon Jun 20 2022
R6#mtrace 192.168.170.20
Type escape sequence to abort.
Mtrace from 192.168.170.20 to 10.229.4.1 via RPF
From source (?) to destination (?)
Querying full reverse path...
0 10.229.4.1
-1 10.229.4.1 ==> 10.229.4.1 PIM [192.168.170.0/24]
-2 10.229.4.2 ==> 10.229.3.2 PIM [192.168.170.0/24]
-3 10.229.3.1 ==> 10.229.2.2 PIM [192.168.170.0/24]
-4 10.229.2.1 ==> 10.229.1.2 PIM [192.168.170.0/24]
-5 10.229.1.1 ==> 10.229.0.2 PIM [192.168.170.0/24]
-6 10.229.0.1 ==> 192.168.170.10 PIM_MT [192.168.170.0/24]
-7 192.168.170.20
R6#sh clo
*13:58:07.855 UTC Mon Jun 20 2022
R6#

+++++++++++++S1+++++++++++++++++++++

Switch#traceroute 192.168.170.20
Type escape sequence to abort.
Tracing the route to 192.168.170.20
VRF info: (vrf in name/id, vrf out name/id)
1 10.229.0.1 1 msec 1 msec 1 msec
2 192.168.170.20 3 msec 1 msec 1 msec
Switch#sh ip rpf 192.168.170.20
RPF information for ? (192.168.170.20)
RPF interface: Vlan1
RPF neighbor: ? (10.229.0.1)
RPF route/mask: 192.168.170.0/24
RPF type: unicast (ospf 1)
Doing distance-preferred lookups across tables
RPF topology: ipv4 multicast base, originated from ipv4 unicast base

Switch#sh ip pim interface count

For switching state use "show ip mfib interface"
Address Interface Mpackets In/Out
10.229.0.2 Vlan1 341/0
10.229.1.1 Vlan2 110/341
Switch#show ip mfib interface
IPv4 Multicast Forwarding (MFIB) status:
Configuration Status: enabled
Operational Status: running
Initialization State: Running
Total signalling packets queued: 0
Process Status: may enable - 3 - pid 229
Tables 1/1/0 (active/mrib/io)

MFIB interface status CEF-based output
[configured,available]
Loopback0 up [yes ,no ]
Vlan1 up [yes ,yes ]
Vlan2 up [yes ,yes ]
Vlan5 down [yes ,no ]
Switch#

+++++++++++++++++++R5+++++++++++++++

R5#traceroute 192.168.170.20 numeric
Type escape sequence to abort.
Tracing the route to 192.168.170.20
VRF info: (vrf in name/id, vrf out name/id)
1 192.168.170.20 1 msec 0 msec 0 msec
R5#sh ip rpf 192.168.170.20
RPF information for ? (192.168.170.20)
RPF interface: Ethernet0/1
RPF neighbor: ? (192.168.170.20) - directly connected
RPF route/mask: 192.168.170.0/24
RPF type: multicast (connected)
Doing distance-preferred lookups across tables
RPF topology: ipv4 multicast base
R5#
R5#
R5#
R5#
R5#
R5#sh ip pim interface count

For switching state use "show ip mfib interface"
Address Interface Mpackets In/Out
10.229.0.1 Ethernet0/0 338/5
192.168.170.10 Ethernet0/1 5/0
R5#
R5#show ip mfib interface
IPv4 Multicast Forwarding (MFIB) status:
Configuration Status: enabled
Operational Status: running
Initialization State: Running
Total signalling packets queued: 0
Process Status: may enable - 3 - pid 385
Tables 1/1/0 (active/mrib/io)

MFIB interface status CEF-based output
[configured,available]
Ethernet0/0 up [yes ,yes ]
Ethernet0/1 up [yes ,yes ]
R5#

gd.dhiman · ‎06-20-2022

Adding more on to this,

When there is no traffic , muticast traceroute follow R6,S4,S3,S2,S1,R5 and source.
However , when I send traffic from Source, the mutlicast route follow Receiver, R6,R5,Source
It is mutliaccess ethernet network, where all interfaces on switch side are trunks ( except those interaces connected to R5 and R6 )
Every device shows, mutliple neighbours ( indirect neighborships ), Is it Ideal scenario ?

Refer below outputs

+++++++++++++++++++R5+++++++++++++++++++++++++++++++++

R5#mtrace 192.168.170.20 192.168.160.50 231.1.1.1
Type escape sequence to abort.
Mtrace from 192.168.170.20 to 192.168.160.50 via group 231.1.1.1
From source (?) to destination (?)
Querying full reverse path... * switching to hop-by-hop:
0 192.168.160.50
-1 10.229.4.1 ==> 10.229.4.1 PIM [192.168.170.0/24]
-2 10.229.0.1 ==> 192.168.170.10 PIM_MT [192.168.170.0/24]
-3 Route must have changed...try again

R5#mtrace 192.168.170.20 192.168.160.50 231.1.1.1
Type escape sequence to abort.
Mtrace from 192.168.170.20 to 192.168.160.50 via group 231.1.1.1
From source (?) to destination (?)
Querying full reverse path...
0 192.168.160.50
-1 10.229.4.1 ==> 10.229.4.1 PIM [192.168.170.0/24]
-2 10.229.4.2 ==> 10.229.3.2 PIM [192.168.170.0/24]
-3 10.229.3.1 ==> 10.229.2.2 PIM [192.168.170.0/24]
-4 10.229.2.1 ==> 10.229.1.2 PIM [192.168.170.0/24]
-5 10.229.1.1 ==> 10.229.0.2 PIM [192.168.170.0/24]
-6 10.229.0.1 ==> 192.168.170.10 PIM_MT [192.168.170.0/24]
-7 192.168.170.20
R5#
R5#
R5#mtrace 192.168.170.20 192.168.160.50 231.1.1.1
Type escape sequence to abort.
Mtrace from 192.168.170.20 to 192.168.160.50 via group 231.1.1.1
From source (?) to destination (?)
Querying full reverse path...
0 192.168.160.50
-1 10.229.4.1 ==> 10.229.4.1 PIM [192.168.170.0/24]
-2 10.229.0.1 ==> 192.168.170.10 PIM_MT [192.168.170.0/24]
-3 192.168.170.20
R5#

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, G - GenID Capable,
L - DR Load-balancing Capable
Neighbor Interface Uptime/Expires Ver DR
Address Prio/Mode
10.229.4.1 Ethernet0/0 03:57:18/00:01:15 v2 1 / S P G
10.229.2.1 Ethernet0/0 03:57:18/00:01:42 v2 1 / S P G
10.229.2.2 Ethernet0/0 03:57:18/00:01:40 v2 1 / S P G
10.229.4.2 Ethernet0/0 03:57:18/00:01:17 v2 1 / DR S P G
10.229.0.2 Ethernet0/0 03:57:47/00:01:34 v2 1 / S P G
R5#sh clo
*17:24:59.606 UTC Mon Jun 20 2022
R5#

R5#show ip mroute
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
L - Local, P - Pruned, R - RP-bit set, F - Register flag,
T - SPT-bit set, J - Join SPT, M - MSDP created entry, E - Extranet,
X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
U - URD, I - Received Source Specific Host Report,
Z - Multicast Tunnel, z - MDT-data group sender,
Y - Joined MDT-data group, y - Sending to MDT-data group,
G - Received BGP C-Mroute, g - Sent BGP C-Mroute,
N - Received BGP Shared-Tree Prune, n - BGP C-Mroute suppressed,
Q - Received BGP S-A Route, q - Sent BGP S-A Route,
V - RD & Vector, v - Vector, p - PIM Joins on route,
x - VxLAN group
Outgoing interface flags: H - Hardware switched, A - Assert winner, p - PIM Join
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode

(*, 231.1.1.1), 00:00:08/stopped, RP 0.0.0.0, flags: D
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Ethernet0/0, Forward/Dense, 00:00:08/stopped

(192.168.170.20, 231.1.1.1), 00:00:08/00:02:51, flags: T
Incoming interface: Ethernet0/1, RPF nbr 0.0.0.0
Outgoing interface list:
Ethernet0/0, Forward/Dense, 00:00:08/stopped, A

(*, 224.0.1.40), 04:14:44/00:02:16, RP 0.0.0.0, flags: DCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Ethernet0/0, Forward/Dense, 04:14:44/stopped

+++++++++++++++++++++++++++++++S1++++++++++++++++++++++++++++++++++

R5#mtrace 192.168.170.20 192.168.160.50 231.1.1.1

Switch#
Switch#mtrace 192.168.170.20 192.168.160.50 231.1.1.1
Type escape sequence to abort.
Mtrace from 192.168.170.20 to 192.168.160.50 via group 231.1.1.1
From source (?) to destination (?)
Querying full reverse path...
0 192.168.160.50
-1 10.229.4.1 ==> 10.229.4.1 PIM [192.168.170.0/24]
-2 10.229.0.1 ==> 192.168.170.10 PIM_MT [192.168.170.0/24]
-3 192.168.170.20
Switch#sh clo
*17:47:40.623 UTC Mon Jun 20 2022
Switch#

Switch#show ip rpf 192.168.170.20
RPF information for ? (192.168.170.20)
RPF interface: Vlan1
RPF neighbor: ? (10.229.0.1)
RPF route/mask: 192.168.170.0/24
RPF type: unicast (ospf 1)
Doing distance-preferred lookups across tables
RPF topology: ipv4 multicast base, originated from ipv4 unicast base
Switch#

Switch# show ip mroute 231.1.1.1
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
L - Local, P - Pruned, R - RP-bit set, F - Register flag,
T - SPT-bit set, J - Join SPT, M - MSDP created entry, E - Extranet,
X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
U - URD, I - Received Source Specific Host Report,
Z - Multicast Tunnel, z - MDT-data group sender,
Y - Joined MDT-data group, y - Sending to MDT-data group,
G - Received BGP C-Mroute, g - Sent BGP C-Mroute,
N - Received BGP Shared-Tree Prune, n - BGP C-Mroute suppressed,
Q - Received BGP S-A Route, q - Sent BGP S-A Route,
V - RD & Vector, v - Vector, p - PIM Joins on route,
x - VxLAN group
Outgoing interface flags: H - Hardware switched, A - Assert winner, p - PIM Join
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode

(*, 231.1.1.1), 00:11:19/stopped, RP 0.0.0.0, flags: D
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Vlan2, Forward/Dense, 00:11:19/stopped
Vlan1, Forward/Dense, 00:11:19/stopped

(192.168.170.20, 231.1.1.1), 00:00:16/00:02:43, flags: PT
Incoming interface: Vlan1, RPF nbr 10.229.0.1*
Outgoing interface list:
Vlan2, Prune/Dense, 00:00:12/00:02:47, A

Switch#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, G - GenID Capable,
L - DR Load-balancing Capable
Neighbor Interface Uptime/Expires Ver DR
Address Prio/Mode
10.229.4.1 Vlan1 04:44:25/00:01:16 v2 1 / S P G
10.229.2.1 Vlan1 04:44:25/00:01:21 v2 1 / S P G
10.229.2.2 Vlan1 04:44:25/00:01:23 v2 1 / S P G
10.229.4.2 Vlan1 04:44:25/00:01:28 v2 1 / DR S P G
10.229.0.1 Vlan1 04:44:53/00:01:38 v2 1 / S P G
10.229.3.2 Vlan2 04:44:51/00:01:23 v2 1 / DR S P G
10.229.3.1 Vlan2 04:44:51/00:01:42 v2 1 / S P G
10.229.1.2 Vlan2 04:44:51/00:01:19 v2 1 / S P G
Switch#sh clo
*18:12:03.940 UTC Mon Jun 20 2022
Switch#

++++++++++++++++++++++++++++++R6( Receiver is connected ) +++++++++++++++++++++++++++++

R6# show ip rpf 192.168.170.20
RPF information for ? (192.168.170.20)
RPF interface: Ethernet0/0
RPF neighbor: ? (10.229.4.2)
RPF route/mask: 192.168.170.0/24
RPF type: unicast (ospf 1)
Doing distance-preferred lookups across tables
RPF topology: ipv4 multicast base, originated from ipv4 unicast base
R6#

R6#mtrace 192.168.170.20 192.168.160.50 231.1.1.1
Type escape sequence to abort.
Mtrace from 192.168.170.20 to 192.168.160.50 via group 231.1.1.1
From source (?) to destination (?)
Querying full reverse path...
0 192.168.160.50
-1 192.168.160.10 ==> 10.229.4.1 PIM [192.168.170.0/24]
-2 10.229.0.1 ==> 192.168.170.10 PIM_MT [192.168.170.0/24]
-3 192.168.170.20
R6#
R6#

R6#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, G - GenID Capable,
L - DR Load-balancing Capable
Neighbor Interface Uptime/Expires Ver DR
Address Prio/Mode
10.229.0.1 Ethernet0/0 04:45:08/00:01:23 v2 1 / S P G
10.229.0.2 Ethernet0/0 04:45:08/00:01:30 v2 1 / S P G
10.229.2.1 Ethernet0/0 04:45:08/00:01:36 v2 1 / S P G
10.229.2.2 Ethernet0/0 04:45:08/00:01:38 v2 1 / S P G
10.229.4.2 Ethernet0/0 04:45:38/00:01:43 v2 1 / DR S P G
R6#

++++++++++++++++++++++++++S4+++++++++++++++++++++++

PIM Neighbor Table
Mode: B - Bidir Capable, DR - Designated Router, N - Default DR Priority,
P - Proxy Capable, S - State Refresh Capable, G - GenID Capable,
L - DR Load-balancing Capable
Neighbor Interface Uptime/Expires Ver DR
Address Prio/Mode
10.229.0.1 Vlan1 04:45:46/00:01:16 v2 1 / S P G
10.229.0.2 Vlan1 04:45:46/00:01:22 v2 1 / S P G
10.229.2.1 Vlan1 04:45:46/00:01:28 v2 1 / S P G
10.229.2.2 Vlan1 04:45:46/00:01:30 v2 1 / S P G
10.229.4.1 Vlan1 04:46:15/00:01:24 v2 1 / S P G
10.229.1.1 Vlan2 04:46:12/00:01:23 v2 1 / S P G
10.229.3.1 Vlan2 04:46:12/00:01:19 v2 1 / S P G
10.229.1.2 Vlan2 04:46:12/00:01:26 v2 1 / S P G
S4#sh clo
*18:13:24.885 UTC Mon Jun 20 2022
S4#

++++++++++++++++++++++++++++++++S3+++++++++++++++++++

S3#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, G - GenID Capable,
L - DR Load-balancing Capable
Neighbor Interface Uptime/Expires Ver DR
Address Prio/Mode
10.229.0.1 Vlan1 04:46:19/00:01:41 v2 1 / S P G
10.229.0.2 Vlan1 04:46:19/00:01:18 v2 1 / S P G
10.229.4.1 Vlan1 04:46:19/00:01:20 v2 1 / S P G
10.229.2.1 Vlan1 04:46:19/00:01:25 v2 1 / S P G
10.229.4.2 Vlan1 04:46:19/00:01:32 v2 1 / DR S P G
10.229.1.1 Vlan2 04:46:45/00:01:19 v2 1 / S P G
10.229.3.2 Vlan2 04:46:45/00:01:26 v2 1 / DR S P G
10.229.1.2 Vlan2 04:46:45/00:01:23 v2 1 / S P G
S3#sh clo
*18:13:57.680 UTC Mon Jun 20 2022

+++++++++++++++++++++++++S2++++++++++++++++++++++++++++++

Switch#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, G - GenID Capable,
L - DR Load-balancing Capable
Neighbor Interface Uptime/Expires Ver DR
Address Prio/Mode
10.229.4.1 Vlan1 04:46:49/00:01:19 v2 1 / S P G
10.229.0.1 Vlan1 04:46:49/00:01:41 v2 1 / S P G
10.229.0.2 Vlan1 04:46:49/00:01:17 v2 1 / S P G
10.229.2.2 Vlan1 04:46:49/00:01:26 v2 1 / S P G
10.229.4.2 Vlan1 04:46:49/00:01:31 v2 1 / DR S P G
10.229.3.2 Vlan2 04:47:16/00:01:26 v2 1 / DR S P G
10.229.3.1 Vlan2 04:47:16/00:01:15 v2 1 / S P G
10.229.1.1 Vlan2 04:47:16/00:01:18 v2 1 / S P G
Switch# sh clo
*18:14:37.470 UTC Mon Jun 20 2022
Switch#

+++++++++++++++++++++++++S1+++++++++++++++++++++++++++

PIM Neighbor Table
Mode: B - Bidir Capable, DR - Designated Router, N - Default DR Priority,
P - Proxy Capable, S - State Refresh Capable, G - GenID Capable,
L - DR Load-balancing Capable
Neighbor Interface Uptime/Expires Ver DR
Address Prio/Mode
10.229.4.1 Vlan1 05:00:31/00:01:25 v2 1 / S P G
10.229.2.1 Vlan1 05:00:31/00:01:28 v2 1 / S P G
10.229.2.2 Vlan1 05:00:31/00:01:28 v2 1 / S P G
10.229.4.2 Vlan1 05:00:31/00:01:33 v2 1 / DR S P G
10.229.0.1 Vlan1 05:01:00/00:01:17 v2 1 / S P G
10.229.3.2 Vlan2 05:00:58/00:01:28 v2 1 / DR S P G
10.229.3.1 Vlan2 05:00:58/00:01:20 v2 1 / S P G
10.229.1.2 Vlan2 05:00:58/00:01:29 v2 1 / S P G
Switch#

Jon Marshall · ‎06-20-2022

Not sure what you mean by indirect neighbors because your diagram doesn't suggest that, it suggests each device is connected by a L3 link (whether that is using SVIs or L3 ports on the switches).

If S1 is pruning the stream then that suggests it is not receiving a PIM request from S2 etc. but you don't show the intermediate switch configuration or mroute tables so not clear where it is not working.

Personally if you just want to learn multicast I would just have each pair of devices as neighbors to each other.

Jon

gd.dhiman · ‎06-20-2022

Hi Jon,

Thank you for the response. The Topology I shared is as per our design.

For reference, I have included "show run" and " mroute" from all devices involved.

The problem is, as soon as the customer starts the multicast, it is first received on all the devices for some time ( consider this as point 1 ) ( say the first 30 seconds ), but then let's say we stop the multicast stream, and re-start the multicast stream in less than 40 seconds, some devices receive multicast and some do not and then we have to wait almost 3 minutes or near time, in order to accomplish point 1

The topology I shared is exactly the same, Source is connected to R5 and when Source starts the stream, R5 forward to S1, but when I checked, after a couple of packets S1 stops forwarding and multicast traffic gets pruned.)

The same behavior is shown in S2, S3, and S4 ( Multicast traffic Pruned )

However, when I checked R6, it is forwarding the traffic to Receiver. So this behavior makes me confused, I am sure I am missing something here.

So I request Cisco Community help