Re: Branches not receiving Multicast stream over DMVPN

corycandia · ‎11-15-2020

Experts,

After all reading, Googling, and trial/error I can take, I still can't get a DLNA multicast announcement to stream to a branch office DLNA receiver.

Goal: DLNA TV receivers at branch offices receive a DLNA multicast announcement from a DLNA media server at HQ/Hub.

Topology:

-The branches are connected to the HQ/Hub via a DMVPN tunnel and EIGRP. One branch is currently being NAT'd so it's spoke to spoke gets routed through hub.

The HQ/HUB router is the RP for the multicast sparse/Dense and the DR for each segment.

Connectivity looks like:

SERVER->C3560G <--L3--> 2921 <(DMVPN TUNNEL)> 1921 (Branch 1) / 819 (Branch 2)

The C3560G is acting as a core switch doing L3.

The 2921 is the HQ FW and DMVPN Hub.

The branches use 2921s or 819s.

The media server is 172.20.16.201

(Config pieces attached)

The stream *seems* to show up on the 2921 HQ/HUB router:

HQ/HUB# show ip mroute 239.255.255.250

(*, 239.255.255.250), 15:24:19/00:03:24, RP 172.20.19.246, flags: S
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Tunnel0, Forward/Sparse-Dense, 02:24:01/00:03:24
GigabitEthernet0/0, Forward/Sparse-Dense, 13:48:56/00:03:03

(172.20.42.5, 239.255.255.250), 00:00:05/00:03:24, flags: T
Incoming interface: Tunnel0, RPF nbr 172.20.254.3
Outgoing interface list:
GigabitEthernet0/0, Forward/Sparse-Dense, 00:00:05/00:03:24

(172.20.16.201, 239.255.255.250), 15:24:19/00:02:41, flags:
Incoming interface: GigabitEthernet0/0, RPF nbr 172.20.19.249
Outgoing interface list:
Tunnel0, Forward/Sparse-Dense, 02:24:01/00:03:24

* I say seems because I still don't totally understand the multicast routing even from all the reading about it.

This makes me think there is no problem between the server/core switch and the HQ/Hub router. Not sure. It looks like the stream is being sent out the tunnel interfaces towards the branches.

The steam not showing up on the branches:

BRANCH 1 819# show ip mroute 239.255.255.250

(*, 239.255.255.250), 20:04:19/00:02:53, RP 172.20.19.246, flags: SJCL
Incoming interface: Tunnel0, RPF nbr 172.20.254.2
Outgoing interface list:
GigabitEthernet0/0, Forward/Sparse-Dense, 13:51:13/00:02:53

BRANCH 2 2921# show ip mroute 239.255.255.250

(*, 239.255.255.250), 13:26:28/stopped, RP 172.20.19.246, flags: SJCLF
Incoming interface: Tunnel0, RPF nbr 172.20.254.2
Outgoing interface list:
Vlan420, 172.20.42.254, Forward/Sparse-Dense, 00:08:50/00:02:08
Vlan420, 172.20.42.5, Forward/Sparse-Dense, 00:33:10/00:01:01
Vlan320, Forward/Sparse-Dense, 13:26:28/00:02:00

(172.20.42.5, 239.255.255.250), 00:00:49/00:02:40, flags: LFT
Incoming interface: Vlan420, RPF nbr 0.0.0.0
Outgoing interface list:
Tunnel0, Forward/Sparse-Dense, 00:00:49/00:02:40
Vlan320, Forward/Sparse-Dense, 00:00:49/00:02:10
Vlan420, 172.20.42.5, Forward/Sparse-Dense, 00:00:49/00:02:10
Vlan420, 172.20.42.254, Forward/Sparse-Dense, 00:00:49/00:02:10

Brach 2 has a device also broadcasting announcements. In both cases, the announcement from the media server never seems to make it, and is not detected by the receiver. If the receiver is connected to the HQ subnet of the media server, it's naturally immediately detected.

I've tried everything I could think of to make this work.

Question 1: Do I need to create a mapping on the RP? If so, how?

Question 2: What am I doing wrong or missing?

Thanks much!

Georg Pauwen · ‎11-15-2020

Hello,

did you configure the mapping agent on the hub router, something like below ?

interface loopback 0
ip pim sparse-dense-mode
ip pim send-rp-discovery loopback 0 scope 10

corycandia · ‎11-15-2020

Yes sir,

HQ/HUB:

interface Loopback0
description ** ROUTER ID **
ip address 172.20.19.246 255.255.255.255
ip pim sparse-dense-mode
ip nat inside
ip virtual-reassembly in
zone-member security LAN
end

My RP Commands are only available in Global:

ip pim bidir-enable
ip pim autorp listener
ip pim send-rp-announce Loopback0 scope 10
ip pim send-rp-discovery Loopback0 scope 10

Georg Pauwen · ‎11-15-2020

Hello,

that part looks good. I somewhere remember that you have to put the command 'ip pim nbma-mode' on the tunnel interface of the hub router, can you give that a try ?

corycandia · ‎11-15-2020

I tested it, doesn't seem to make a difference.

corycandia · ‎11-15-2020

Config Info:

!==============================
! CORE SWITCH WITH MEDIA SERVER
!==============================

interface Vlan165
description ** GATEWAY of Media Server **
ip address 172.20.16.254 255.255.255.128
ip helper-address 172.20.16.1
ip pim sparse-dense-mode
ip igmp version 3


interface GigabitEthernet0/48
description ** ROUTER UPLINK to 2921/HQ HUB Router **
no switchport
ip address 172.20.19.249 255.255.255.248
ip pim sparse-dense-mode
mls qos trust dscp
flowcontrol receive desired
spanning-tree portfast
spanning-tree bpdufilter enable

ip multicast-routing distributed
ip pim bidir-enable
ip pim autorp listener

!====================
! HQ/HUB ROUTER 2921
!====================

interface GigabitEthernet0/0
description ** Downlink to Core Switch **
ip address 172.20.19.254 255.255.255.248
ip pim dr-priority 10
ip pim sparse-dense-mode
ip nat inside
ip virtual-reassembly in
zone-member security LAN
ip traffic-export apply TRAFFIC_EXPORT
duplex auto
speed auto
service-policy output POLICYMAP_WAN-EGRESS-QUEUING
end

interface Tunnel0
description DMVPN
bandwidth 100000
bandwidth qos-reference 100000
ip address 172.20.254.2 255.255.255.0
no ip redirects
ip mtu 1400
no ip next-hop-self eigrp 1
no ip split-horizon eigrp 1
ip pim dr-priority 10
ip pim sparse-dense-mode
ip nat inside
ip nhrp authentication CNDMNTCS
ip nhrp network-id 1
ip nhrp holdtime 300
ip virtual-reassembly in
zone-member security LAN
ip summary-address eigrp 1 172.20.16.0 255.255.248.0
ip tcp adjust-mss 1360
delay 100
nhrp group DMVPN-QOS_100MBPS
nhrp map group DMVPN-QOS_100MBPS service-policy output POLICYMAP_DMVPN-100MBPS-LINE-RATE
nhrp map group DMVPN-QOS_60MBPS service-policy output POLICYMAP_DMVPN-60MBPS-LINE-RATE
qos pre-classify
tunnel source GigabitEthernet0/1
tunnel mode gre multipoint
tunnel key 1
tunnel path-mtu-discovery
tunnel protection ipsec profile IPSEC-PROFILE_DMVPN
end

ip multicast-routing
ip pim bidir-enable
ip pim autorp listener
ip pim send-rp-announce Loopback0 scope 10
ip pim send-rp-discovery Loopback0 scope 10

!===============
! Branch 1 - 819
!===============

interface Vlan420
description Default gateway for Germany LAN
ip address 172.20.42.254 255.255.255.0
no ip proxy-arp
ip pim sparse-dense-mode
ip nat inside
ip virtual-reassembly in
zone-member security LAN
ip policy route-map ROUTEMAP_TV-SUBNET
ip igmp join-group 239.255.255.250 ! Attempting to get stream
end

interface Tunnel0
description DMVPN
bandwidth 100000
bandwidth qos-reference 100000
ip address 172.20.254.3 255.255.255.0
no ip redirects
ip mtu 1400
ip pim sparse-dense-mode
ip nhrp authentication CNDMNTCS
ip nhrp group DMVPN-QOS_100MBPS
ip nhrp map group DMVPN-QOS_100MBPS service-policy output POLICYMAP_DMVPN-100MBPS-LINE-RATE
ip nhrp map group DMVPN-QOS_60MBPS service-policy output POLICYMAP_DMVPN-60MBPS-LINE-RATE
ip nhrp network-id 1
ip nhrp holdtime 300
ip nhrp nhs dynamic nbma gateway.FQDN.com multicast
zone-member security LAN
ip summary-address eigrp 1 172.20.32.0 255.255.248.0
ip tcp adjust-mss 1360
delay 100
qos pre-classify
tunnel source Dialer1
tunnel mode gre multipoint
tunnel key 1
tunnel path-mtu-discovery
tunnel protection ipsec profile IPSEC-PROFILE_DMVPN
end

ip multicast-routing
ip pim bidir-enable
ip pim autorp listener

!===============
! Branch 2 - 2921
!===============

interface GigabitEthernet0/0
ip address 172.20.48.254 255.255.255.128
ip pim sparse-dense-mode
ip nat inside
ip virtual-reassembly in
zone-member security LAN
ip igmp join-group 239.255.255.250 ! Attempting to get stream
ip igmp version 3
duplex auto
speed auto
end

interface Tunnel0
description DMVPN
bandwidth 60000
bandwidth qos-reference 60000
ip address 172.20.254.4 255.255.255.0
no ip redirects
ip mtu 1400
ip pim sparse-dense-mode
ip nhrp authentication CNDMNTCS
ip nhrp group DMVPN-QOS_60MBPS
ip nhrp map group DMVPN-QOS_100MBPS service-policy output POLICYMAP_DMVPN-100MBPS-LINE-RATE
ip nhrp map group DMVPN-QOS_60MBPS service-policy output POLICYMAP_DMVPN-60MBPS-LINE-RATE
ip nhrp network-id 1
ip nhrp holdtime 300
ip nhrp nhs dynamic nbma gateway.FQDN.com multicast
zone-member security LAN
ip summary-address eigrp 1 172.20.48.0 255.255.255.0
ip tcp adjust-mss 1322
delay 100
tunnel source GigabitEthernet0/1
tunnel mode gre multipoint
tunnel key 1
tunnel path-mtu-discovery
tunnel protection ipsec profile IPSEC-PROFILE_DMVPN
end

ip multicast-routing
ip pim autorp listener
ip pim bidir-enable

Show Output

!==============================
! CORE SWITCH WITH MEDIA SERVER
!==============================

show ip pim neighbor

172.20.19.254 GigabitEthernet0/48 16:53:54/00:01:16 v2 10/ DR B S P G


show ip pim rp

Group: 239.255.255.251, RP: 172.20.19.246, v2, uptime 16:37:19, expires 00:02:21
Group: 239.255.255.250, RP: 172.20.19.246, v2, uptime 16:37:19, expires 00:02:21
Group: 239.255.3.22, RP: 172.20.19.246, v2, uptime 16:37:19, expires 00:02:21
Group: 224.0.1.178, RP: 172.20.19.246, v2, uptime 16:37:19, expires 00:02:21


show ip pim rp mapping

Group(s) 224.0.0.0/4
RP 172.20.19.246 (?), v2v1
Info source: 172.20.19.246 (?), elected via Auto-RP
Uptime: 16:37:44, expires: 00:02:54

show ip mroute

(*, 239.255.255.251), 16:01:04/stopped, RP 172.20.19.246, flags: SJCF
Incoming interface: GigabitEthernet0/48, RPF nbr 172.20.19.254
Outgoing interface list:
Vlan165, Forward/Sparse-Dense, 16:01:04/00:02:51

(172.20.16.207, 239.255.255.251), 16:01:04/00:02:58, flags: PFT
Incoming interface: Vlan165, RPF nbr 0.0.0.0
Outgoing interface list: Null

(*, 239.255.255.250), 16:01:02/stopped, RP 172.20.19.246, flags: SJCF
Incoming interface: GigabitEthernet0/48, RPF nbr 172.20.19.254
Outgoing interface list:
Vlan165, Forward/Sparse-Dense, 14:25:39/00:02:52

(172.20.16.156, 239.255.255.250), 03:25:24/00:02:18, flags: PFT
Incoming interface: Vlan165, RPF nbr 0.0.0.0, Registering
Outgoing interface list: Null

(172.20.16.131, 239.255.255.250), 15:24:08/00:01:48, flags: PFT
Incoming interface: Vlan165, RPF nbr 0.0.0.0, Registering
Outgoing interface list: Null

(172.20.16.201, 239.255.255.250), 16:01:02/00:02:57, flags: FT
Incoming interface: Vlan165, RPF nbr 0.0.0.0
Outgoing interface list:
GigabitEthernet0/48, Forward/Sparse-Dense, 03:00:45/00:02:57

(*, 239.255.3.22), 16:00:39/00:02:51, RP 172.20.19.246, flags: SJC
Incoming interface: GigabitEthernet0/48, RPF nbr 172.20.19.254
Outgoing interface list:
Vlan165, Forward/Sparse-Dense, 16:00:39/00:02:51

(*, 224.0.1.39), 16:40:28/stopped, RP 0.0.0.0, flags: DC
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
GigabitEthernet0/48, Forward/Sparse-Dense, 16:40:28/stopped

(172.20.19.246, 224.0.1.39), 00:00:06/00:02:53, flags: PT
Incoming interface: GigabitEthernet0/48, RPF nbr 172.20.19.254
Outgoing interface list: Null

(*, 224.0.1.40), 16:42:30/stopped, RP 0.0.0.0, flags: DCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
GigabitEthernet0/48, Forward/Sparse-Dense, 16:42:30/stopped
Loopback0, Forward/Sparse-Dense, 16:42:30/stopped

(172.20.19.246, 224.0.1.40), 16:38:28/00:02:17, flags: LT
Incoming interface: GigabitEthernet0/48, RPF nbr 172.20.19.254
Outgoing interface list:
Loopback0, Forward/Sparse-Dense, 16:38:28/stopped

(*, 224.0.1.178), 16:00:38/00:02:48, RP 172.20.19.246, flags: SJC
Incoming interface: GigabitEthernet0/48, RPF nbr 172.20.19.254
Outgoing interface list:
Vlan165, Forward/Sparse-Dense, 16:00:38/00:02:48


show ip igmp groups

239.255.255.251 Vlan165 16:55:23 00:02:08 172.20.16.162
239.255.255.250 Vlan165 14:26:23 00:02:09 172.20.16.152
239.255.3.22 Vlan165 16:55:23 00:02:08 172.20.16.162
224.0.1.39 GigabitEthernet0/48 16:40:05 00:02:57 172.20.19.254
224.0.1.40 Loopback0 16:57:20 00:02:48 172.20.19.244
224.0.1.178 Vlan165 16:55:23 00:02:05 172.20.16.251

!====================
! HQ/HUB ROUTER 2921
!====================

show ip pim neighbor

172.20.19.249 GigabitEthernet0/0 16:58:07/00:01:15 v2 1 / B S P G
172.20.254.3 Tunnel0 13:49:17/00:01:21 v2 1 / B S P G
172.20.254.4 Tunnel0 1d14h/00:01:36 v2 1 / B S P G


show ip pim rp

Group: 239.255.255.251, RP: 172.20.19.246, next RP-reachable never
Group: 239.255.255.250, RP: 172.20.19.246, next RP-reachable never
Group: 239.255.3.22, RP: 172.20.19.246, next RP-reachable never
Group: 224.0.1.178, RP: 172.20.19.246, next RP-reachable never

show ip pim rp mapping

Group(s) 224.0.0.0/4
RP 172.20.19.246 (?), v2v1
Info source: 172.20.19.246 (?), elected via Auto-RP
Uptime: 16:41:28, expires: 00:02:55

show ip mroute

(*, 239.255.255.251), 16:04:15/00:02:35, RP 172.20.19.246, flags: S
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
GigabitEthernet0/0, Forward/Sparse-Dense, 16:03:16/00:02:35

(172.20.16.207, 239.255.255.251), 16:04:15/00:02:02, flags: P
Incoming interface: GigabitEthernet0/0, RPF nbr 172.20.19.249
Outgoing interface list: Null

(*, 239.255.255.250), 16:04:13/00:02:43, RP 172.20.19.246, flags: S
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Tunnel0, Forward/Sparse-Dense, 03:03:55/00:02:43
GigabitEthernet0/0, Forward/Sparse-Dense, 14:28:50/00:02:35

(172.20.42.5, 239.255.255.250), 00:00:46/00:02:43, flags: T
Incoming interface: Tunnel0, RPF nbr 172.20.254.3
Outgoing interface list:
GigabitEthernet0/0, Forward/Sparse-Dense, 00:00:46/00:02:43

(172.20.32.32, 239.255.255.250), 00:01:29/00:02:06, flags: T
Incoming interface: Tunnel0, RPF nbr 172.20.254.3
Outgoing interface list:
GigabitEthernet0/0, Forward/Sparse-Dense, 00:01:29/00:03:01

(172.20.16.201, 239.255.255.250), 16:04:13/00:01:47, flags:
Incoming interface: GigabitEthernet0/0, RPF nbr 172.20.19.249
Outgoing interface list:
Tunnel0, Forward/Sparse-Dense, 03:03:55/00:02:43

(*, 239.255.3.22), 16:03:50/00:02:59, RP 172.20.19.246, flags: S
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
GigabitEthernet0/0, Forward/Sparse-Dense, 16:03:50/00:02:59

(*, 224.0.1.39), 16:43:39/stopped, RP 0.0.0.0, flags: DCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Loopback0, Forward/Sparse, 16:42:33/stopped
Tunnel0, Forward/Sparse-Dense, 16:43:39/stopped
GigabitEthernet0/0, Forward/Sparse-Dense, 16:43:39/stopped

(172.20.19.246, 224.0.1.39), 16:43:39/00:02:43, flags: LT
Incoming interface: Loopback0, RPF nbr 0.0.0.0
Outgoing interface list:
Tunnel0, Forward/Sparse-Dense, 03:44:05/stopped
GigabitEthernet0/0, Forward/Sparse-Dense, 16:42:33/stopped

(*, 224.0.1.40), 3d10h/stopped, RP 0.0.0.0, flags: DCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Loopback0, Forward/Sparse, 21:11:38/stopped
Tunnel0, Forward/Sparse-Dense, 1d14h/stopped
GigabitEthernet0/0, Forward/Sparse-Dense, 16:59:45/stopped

(172.20.19.246, 224.0.1.40), 16:41:39/00:02:02, flags: LT
Incoming interface: Loopback0, RPF nbr 0.0.0.0
Outgoing interface list:
Tunnel0, Forward/Sparse-Dense, 16:41:39/stopped
GigabitEthernet0/0, Forward/Sparse-Dense, 16:41:39/stopped

(*, 224.0.1.178), 16:03:49/00:03:20, RP 172.20.19.246, flags: S
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
GigabitEthernet0/0, Forward/Sparse-Dense, 16:03:49/00:03:20




!===============
! Branch 1 - 819
!===============

show ip pim rp

Group: 239.255.255.250, RP: 172.20.19.246, uptime 13:51:42, expires 00:02:34


show ip pim rp mapping

Group(s) 224.0.0.0/4
RP 172.20.19.246 (?), v2v1
Info source: 172.20.19.246 (?), elected via Auto-RP
Uptime: 13:52:01, expires: 00:02:16

show ip mroute

(*, 239.255.255.250), 13:58:00/stopped, RP 172.20.19.246, flags: SJCLF
Incoming interface: Tunnel0, RPF nbr 172.20.254.2
Outgoing interface list:
Vlan420, Forward/Sparse-Dense, 00:12:27/00:02:31
Vlan420, Forward/Sparse-Dense, 00:13:25/00:02:31
Vlan420, Forward/Sparse-Dense, 00:21:24/00:02:31
Vlan320, Forward/Sparse-Dense, 13:58:00/00:02:33

(172.20.42.5, 239.255.255.250), 00:02:39/00:00:50, flags: LFT
Incoming interface: Vlan420, RPF nbr 0.0.0.0
Outgoing interface list:
Tunnel0, Forward/Sparse-Dense, 00:02:39/00:02:47
Vlan320, Forward/Sparse-Dense, 00:02:39/00:02:33

(172.20.32.32, 239.255.255.250), 00:03:22/00:00:13, flags: LFT
Incoming interface: Vlan320, RPF nbr 0.0.0.0, Registering
Outgoing interface list:
Tunnel0, Forward/Sparse-Dense, 00:03:22/00:03:08
Vlan420, Forward/Sparse-Dense, 00:03:22/00:02:31

(*, 224.0.1.39), 14:01:37/stopped, RP 0.0.0.0, flags: DC
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Tunnel0, Forward/Sparse-Dense, 14:01:37/stopped

(172.20.19.246, 224.0.1.39), 13:54:13/00:01:44, flags: PT
Incoming interface: Tunnel0, RPF nbr 172.20.254.2
Outgoing interface list: Null

(*, 224.0.1.40), 3d09h/stopped, RP 0.0.0.0, flags: DCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Tunnel0, Forward/Sparse-Dense, 3d09h/stopped

(172.20.19.246, 224.0.1.40), 13:53:11/00:02:07, flags: PLT
Incoming interface: Tunnel0, RPF nbr 172.20.254.2
Outgoing interface list: Null




show ip igmp groups

239.255.255.250 Vlan420 09:10:59 00:02:06 172.20.42.5
239.255.255.250 Vlan320 3d10h 00:02:08 172.20.32.32
224.0.1.39 Tunnel0 14:02:02 00:02:07 172.20.254.2
224.0.1.40 Tunnel0 3d09h 00:02:04 172.20.254.3

!===============
! Branch 2 - 2921
!===============

show ip pim rp

Group: 239.255.255.250, RP: 172.20.19.246, uptime 16:42:03, expires 00:02:35


show ip pim rp mapping

Group(s) 224.0.0.0/4
RP 172.20.19.246 (?), v2v1
Info source: 172.20.19.246 (?), elected via Auto-RP
Uptime: 16:42:14, expires: 00:02:24

show ip mroute

(*, 239.255.255.250), 20:36:06/00:02:08, RP 172.20.19.246, flags: SJCL
Incoming interface: Tunnel0, RPF nbr 172.20.254.2
Outgoing interface list:
GigabitEthernet0/0, Forward/Sparse-Dense, 14:23:00/00:02:08

(*, 224.0.1.39), 16:43:16/stopped, RP 0.0.0.0, flags: DC
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Tunnel0, Forward/Sparse-Dense, 16:43:16/stopped

(172.20.19.246, 224.0.1.39), 16:42:23/00:01:47, flags: PT
Incoming interface: Tunnel0, RPF nbr 172.20.254.2
Outgoing interface list: Null

(*, 224.0.1.40), 3d03h/stopped, RP 0.0.0.0, flags: DCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Tunnel0, Forward/Sparse-Dense, 1d14h/stopped

(172.20.19.246, 224.0.1.40), 16:42:23/00:02:17, flags: PLT
Incoming interface: Tunnel0, RPF nbr 172.20.254.2
Outgoing interface list: Null


show ip igmp groups

239.255.255.250 GigabitEthernet0/0 14:23:13 00:02:57 172.20.48.138
224.0.1.39 Tunnel0 16:43:29 00:02:27 172.20.254.2
224.0.1.40 Tunnel0 1d14h 00:02:26 172.20.254.4

corycandia · ‎11-15-2020

Debug on the HUB

deb ip pim 239.255.255.250
Nov 15 18:23:20.155: PIM(0): Received v2 Join/Prune on Tunnel0 from 172.20.254.3, to us
Nov 15 18:23:20.155: PIM(0): Join-list: (*, 239.255.255.250), RPT-bit set, WC-bit set, S-bit set
Nov 15 18:23:20.155: PIM(0): Update Tunnel0/172.20.254.3 to (*, 239.255.255.250), Forward state, by PIM *G Join
Nov 15 18:23:20.159: PIM(0): Update Tunnel0/172.20.254.3 to (172.20.16.201, 239.255.255.250), Forward state, by PIM *G Join
CARM-GATEWAY#
Nov 15 18:23:21.527: PIM(0): Received v2 Join/Prune on Tunnel0 from 172.20.254.4, to us
Nov 15 18:23:21.527: PIM(0): Join-list: (*, 239.255.255.250), RPT-bit set, WC-bit set, S-bit set
Nov 15 18:23:21.527: PIM(0): Update Tunnel0/172.20.254.4 to (*, 239.255.255.250), Forward state, by PIM *G Join
Nov 15 18:23:21.527: PIM(0): Update Tunnel0/172.20.254.4 to (172.20.16.201, 239.255.255.250), Forward state, by PIM *G Join
CARM-GATEWAY#
Nov 15 18:23:23.223: PIM(0): Building Periodic (*,G) Join / (S,G,RP-bit) Prune message for 239.255.255.250
CARM-GATEWAY#
Nov 15 18:23:25.223: PIM(0): Insert (172.20.16.201,239.255.255.250) join in nbr 172.20.19.249's queue
Nov 15 18:23:25.223: PIM(0): Building Join/Prune packet for nbr 172.20.19.249
Nov 15 18:23:25.223: PIM(0): Adding v2 (172.20.16.201/32, 239.255.255.250), S-bit Join
Nov 15 18:23:25.223: PIM(0): Send v2 join/prune to 172.20.19.249 (GigabitEthernet0/0)
CARM-GATEWAY#
Nov 15 18:23:26.607: PIM(0): Received v2 Register on GigabitEthernet0/0 from 172.20.19.249
Nov 15 18:23:26.607: (Data-header) for 172.20.16.201, group 239.255.255.250
Nov 15 18:23:26.607: PIM(0): Send v2 Register-Stop to 172.20.19.249 for 172.20.16.201, group 239.255.255.250
Nov 15 18:23:26.623: PIM(0): Insert (172.20.16.201,239.255.255.250) join in nbr 172.20.19.249's queue
Nov 15 18:23:26.623: PIM(0): Building Join/Prune packet for nbr 172.20.19.249
Nov 15 18:23:26.623: PIM(0): Adding v2 (172.20.16.201/32, 239.255.255.250), S-bit Join
Nov 15 18:23:26.623: PIM(0): Send v2 join/prune to 172.20.19.249 (GigabitEthernet0/0)

MHM Cisco World · ‎11-15-2020

config this command under Hub only.
ip pim nbma-mode

corycandia · ‎11-15-2020

I added it to the tunnel interface, here's some output from deb pim on HQ/HUB:

Nov 15 20:40:07.615: PIM(0): Received v2 Register on GigabitEthernet0/0 from 172.20.19.249
Nov 15 20:40:07.615: for 172.20.16.201, group 239.255.255.250
Nov 15 20:40:07.683: PIM(0): Insert (172.20.16.201,239.255.255.250) join in nbr 172.20.19.249's queue
Nov 15 20:40:07.683: PIM(0): Building Join/Prune packet for nbr 172.20.19.249
Nov 15 20:40:07.683: PIM(0): Adding v2 (172.20.16.201/32, 239.255.255.250), S-bit Join
Nov 15 20:40:07.683: PIM(0): Send v2 join/prune to 172.20.19.249 (GigabitEthernet0/0)
CARM-GATEWAY(config-if)#
Nov 15 20:40:10.483: PIM(0): Building Periodic (*,G) Join / (S,G,RP-bit) Prune message for 239.255.255.250
CARM-GATEWAY(config-if)#
Nov 15 20:40:12.795: %FW-6-DROP_PKT: Dropping tcp session 13.66.5.76:50624 199.27.251.53:22 on zone-pair ZP_INTERNET-TO-SELF class class-default due to DROP action found in policy-map with ip ident 59217
CARM-GATEWAY(config-if)#
Nov 15 20:40:20.175: PIM(0): Received v2 Join/Prune on GigabitEthernet0/0 from 172.20.19.249, to us
Nov 15 20:40:20.175: PIM(0): Join-list: (*, 239.255.255.250), RPT-bit set, WC-bit set, S-bit set
Nov 15 20:40:20.175: PIM(0): Update GigabitEthernet0/0/172.20.19.249 to (*, 239.255.255.250), Forward state, by PIM *G Join
Nov 15 20:40:20.175: PIM(0): Prune-list: (172.20.16.131/32, 239.255.255.250) RPT-bit set
Nov 15 20:40:20.175: PIM(0): Prune-list: (172.20.16.201/32, 239.255.255.250) RPT-bit set
CARM-GATEWAY(config-if)#
Nov 15 20:40:27.479: PIM(0): Received v2 Join/Prune on Tunnel0 from 172.20.254.4, to us
Nov 15 20:40:27.479: PIM(0): Join-list: (*, 239.255.255.250), RPT-bit set, WC-bit set, S-bit set
Nov 15 20:40:27.479: PIM(0): Update Tunnel0/172.20.254.4 to (*, 239.255.255.250), Forward state, by PIM *G Join
Nov 15 20:40:27.479: PIM(0): Update Tunnel0/172.20.254.4 to (172.20.16.201, 239.255.255.250), Forward state, by PIM *G Join

In the end, this is still the mroute table for the referenced branch 2 :

 show ip mroute 239.255.255.250

(*, 239.255.255.250), 02:02:59/stopped, RP 172.20.19.246, flags: SJCL
Incoming interface: Tunnel0, RPF nbr 172.20.254.2
Outgoing interface list:
GigabitEthernet0/0, Forward/Sparse-Dense, 01:56:31/00:02:30

(172.20.32.32, 239.255.255.250), 00:00:16/00:02:43, flags: LJT
Incoming interface: Tunnel0, RPF nbr 172.20.254.3
Outgoing interface list:
GigabitEthernet0/0, Forward/Sparse-Dense, 00:00:16/00:02:43

(172.20.32.37, 239.255.255.250), 00:00:19/00:02:40, flags: LJT
Incoming interface: Tunnel0, RPF nbr 172.20.254.3
Outgoing interface list:
GigabitEthernet0/0, Forward/Sparse-Dense, 00:00:19/00:02:40

(172.20.42.5, 239.255.255.250), 00:00:20/00:02:39, flags: LJT
Incoming interface: Tunnel0, RPF nbr 172.20.254.3
Outgoing interface list:
GigabitEthernet0/0, Forward/Sparse-Dense, 00:00:20/00:02:39

It annoys me that the two branches seems to be sharing multicast, but not the stream from the HQ/HUB

Georg Pauwen · ‎11-16-2020

Hello,

I have a feeling that the ZBF might be the culprit.

Did you configure the spoke tunnels with 'ip pim dr-priority 0' ?

MHM Cisco World · ‎11-17-2020

HUB

ip nhrp nhs multicast dynamic
ip pim nbma-mode

this dual need in Hub to make multicast work.

paul driver · ‎11-17-2020

Hello
As your using sparse-dense mode remove the following and test again

ip pim bidir-enable
ip pim autorp listener

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