Multicast Video Isn't Working on Second Path

[webmike10]

Hi,

I have redundant networks paths for HR-SWI-01, shown in the image attached, the black color (path 1) and green color (path 2) lines.  

When both of the paths are enabled MULTICAST traffic travels from HR-SWI-01 through LA-SWI-02 to F-SWI-01 and continues on to the other two switches (cameras are connected to HR-SWI-01).  How do I set it so the multicast traffic travels from HR-SWI-01 to TO-SWI-01?  I ask because I would like it to use the shortest path to the core switch AND because multicast video does not work for some reason when the interface is CONNECTED from HR-SWI-01 -> LA-SWI-02 -> F-SWI-02 -> F-SWI-01 -> TO-SWI-01.  I have ip pim sparse-mode enabled on all uplink interfaces and I ran show ip mroute on each interfaces to confirm the multicast ip address has the correct incoming/outgoing interface.  

Thank you 

[johnd2310]

Hi,

Which of  those switches layer 2 or layer 3 switches? How is multicast configured? Are you using static RP, auto RP, etc

Thanks

John

[webmike10]

Thanks for the response.  They are layer 3 switches with ip services.  Multicast is configured on each switch with:

ip multicast-routing distributed
ip pim rp-address 10.10.254.34 

And on the core 6509 switch, 10.10.254.34 in a loopback address as a BSR.

I can't see the video if I turn on the interface between HR-SWI-01 and LA-SWI-02 (or any interface along the green path) but if TO-SWI-01 is the only uplink UP,  HR-SWI-01 multicast video is received. Each uplink in the diagram is configured as a point to point with a /30 address. 

[paul driver]

Hello

You mention BSR but your using static rp addressing?

Can you post the mapping fro HR-SW-01 and T-SW-01

Sh ip pim mapping
sh ip pim bsr-router

res
Paul

[webmike10]

TO-SWI-01

TO-SWI-04#show ip pim rp mapping
PIM Group-to-RP Mappings
This system is a candidate RP (v2)
This system is the Bootstrap Router (v2)
Group(s) 239.5.0.0/16
RP 10.10.254.34 (?), v2
Info source: 10.10.254.34 (?), via bootstrap, priority 0, holdtime 150
Uptime: 21w3d, expires: 00:02:26
Group(s) 239.101.0.0/16
RP 10.101.128.1 (?), v2
Info source: 172.27.255.210 (?), via bootstrap, priority 0, holdtime 150
Uptime: 2d07h, expires: 00:02:24
RP 10.101.132.1 (?), v2
Info source: 10.101.227.10 (?), via bootstrap, priority 0, holdtime 150
Uptime: 1d06h, expires: 00:02:22
Group(s): 224.0.0.0/4, Static
RP: 10.10.254.32 (?)

TO-SWI-01#show ip pim bsr-router
PIMv2 Bootstrap information
This system is the Bootstrap Router (BSR)
BSR address: 10.10.254.34 (?)
Uptime: 21w3d, BSR Priority: 255, Hash mask length: 0
Next bootstrap message in 00:00:26
Candidate RP: 10.10.254.34(Loopback2)
Holdtime 150 seconds
Advertisement interval 60 seconds
Next advertisement in 00:00:37
Group acl: 1

HR-SWI-01

HR-SWI-01#show ip pim rp mapping
PIM Group-to-RP Mappings

Group(s) 239.5.0.0/16
RP 10.10.254.34 (?), v2
Info source: 10.10.254.34 (?), via bootstrap, priority 0, holdtime 150
Uptime: 21w3d, expires: 00:01:26
Group(s) 239.101.0.0/16
RP 10.101.128.1 (?), v2
Info source: 10.10.254.34 (?), via bootstrap, priority 0, holdtime 150
Uptime: 2d07h, expires: 00:01:29
RP 10.101.132.1 (?), v2
Info source: 10.10.254.34 (?), via bootstrap, priority 0, holdtime 150
Uptime: 1d06h, expires: 00:01:29
Group(s): 224.0.0.0/4, Static
RP: 10.10.254.34 (?)

HR-SWI-01#show ip pim bsr-router
PIMv2 Bootstrap information
BSR address: 10.10.254.34 (?)
Uptime: 21w3d, BSR Priority: 255, Hash mask length: 0
Expires: 00:02:04

Unicast address is 172.27.112.66 with Multicast address of 239.5.3.65

If there is even a way to tell the switch to route all multicast traffic towards TO-SWI-01 without jumping through 3 switches before it gets to TO-SWI-01 will fix the problem. 

[paul driver]

Hello

If there is even a way to tell the switch to route all multicast traffic towards TO-SWI-01 without jumping through 3 switches before it gets to TO-SWI-01 will fix the problem. 

You could possibly use a static mroute entry however interested in seeing the rpf for the 10.10.254.34 and as to traffic a sub-optimal way instead of direct to the core switch

I see you have 3 C-RP configured with 10.10.254.34 taking both C-RP and BSR roles

Can you share:

sh ip mroute | s 239.5.3.65
sh ip rpf 10.10.254.34
sh ip pim interface count

res
Paul

[webmike10]

I added what I thought was a mroute the other day but It never changed the direction of the traffic.  

This is the output when the interface between HR-SWI-01 and LA-SWI-02 is UP, (streaming video isn't working when interface is not shutdown)

And as the output shows the multicast is making the way from HR-SWI-01 to LA-SWI-02 to the others switches finally to TO-SWI-01 without a problem, so I don't understand why there isn't multicast.

HR-SWI-01#sh ip mroute | s 239.5.3.65
(*, 239.5.3.65), 7w0d/stopped, RP 10.10.254.34, flags: SPF
Incoming interface: GigabitEthernet1/1, RPF nbr 172.27.255.61
Outgoing interface list: Null
(172.27.112.66, 239.5.3.65), 7w0d/00:03:28, flags: FT
Incoming interface: Vlan521, RPF nbr 0.0.0.0
Outgoing interface list:
GigabitEthernet1/3, Forward/Sparse, 00:00:00/00:03:29

HR-SWI-01#sh ip rpf 10.10.254.34
RPF information for ? (10.10.254.34)
RPF interface: GigabitEthernet1/1
RPF neighbor: ? (172.27.255.61)
RPF route/mask: 10.10.0.0/16
RPF type: unicast (eigrp 64512)
Doing distance-preferred lookups across tables
RPF topology: ipv4 multicast base, originated from ipv4 unicast base

HR-SWI-01#sh ip pim interface count

State: * - Fast Switched, D - Distributed Fast Switched
H - Hardware Switching Enabled
Address Interface FS Mpackets In/Out
172.27.255.62 GigabitEthernet1/1 * 473114/5453
172.27.112.65 Vlan521 * 174/429523
172.27.112.129 Vlan526 * 1184/473118
172.27.255.133 GigabitEthernet1/3 * 4236/139

TO-SWI-04#sh ip mroute | s 239.5.3.65
(*, 239.5.3.65), 7w0d/stopped, RP 10.10.254.34, flags: SJC
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Vlan17, Forward/Sparse, 16w0d/00:02:58
(172.27.112.66, 239.5.3.65), 7w0d/00:01:35, flags: T
Incoming interface: GigabitEthernet3/14, RPF nbr 172.27.255.78
Outgoing interface list:
Vlan17, Forward/Sparse, 16w0d/00:02:58
TO-SWI-04#sh ip rpf 10.10.254.34
RPF information for ? (10.10.254.34)
RPF interface: Loopback2
RPF neighbor: ? (10.10.254.34) - directly connected
RPF route/mask: 10.10.254.34/32
RPF type: multicast (connected)
Doing distance-preferred lookups across tables
RPF topology: ipv4 multicast base
TO-SWI-04#sh ip pim interface count

For switching state use "show ip mfib interface"
Address Interface Mpackets In/Out
172.27.255.61 GigabitEthernet3/10 70780/916403 
172.27.255.77 GigabitEthernet3/14 25955571/644167  (other camera's are connected to switches other than HR-SWI-01 that is why there is a Mpackets count.)
10.10.254.34 Loopback2 0/0

[paul driver]

Hello

HR-SWI-01 is receiving general quires for the mc group on one interface but it sending via an alternate path as you have stated,And it seems to suggest it a eigrp advertised routing issue with the longer path taking precedence maybe due to a more specific route..

HR-SWI-01#sh ip mroute | s 239.5.3.65
(*, 239.5.3.65), 7w0d/stopped, RP 10.10.254.34, flags: SPF
Incoming interface: GigabitEthernet1/1, RPF nbr 172.27.255.61
Outgoing interface list: Null

(172.27.112.66, 239.5.3.65), 7w0d/00:03:28, flags: FT
Incoming interface: Vlan521, RPF nbr 0.0.0.0
Outgoing interface list:
GigabitEthernet1/3, Forward/Sparse, 00:00:00/00:03:29

If you do  a rpf check on 172.27.112.66 I am guessing it will also route via the LA, FA switches



On HR-SW can you

1) sh Ip mroute | b Out
2) rpf check on 172.27.112.66
3) Mtrace 172.27.112.66,
4) apply a static  mroute 172.27.112.66 255.255.255.255 <HR-SW next hop towards T0-SW>
3) Perform a Mtrace 172.27.112.66 and ip mroute again, post results

res
Paul

[webmike10]

ip mroute 172.27.112.66 255.255.255.255 172.27.255.61

 The subnet mask for 172.27.112.64 network is 255.255.255.192 however if I try that as a mask it gives an error "%Inconsistent source and mask", so I have left the mask as 255.255.255.255 in the command.  

172.27.255.61 is the IP of interface on TO-SWI-01 connected to HR-SWI-01.

If I add that command it does not do multicast video even from HR-SWI-01 to TO-SWI-01 with the LA-SWI-02 link down. 

(prior to mroute change-connected to LA-SWI-02)

HR-SWI-01#sh Ip mroute 172.27.112.66 239.5.3.65
IP Multicast Routing Table
Interface state: Interface, Next-Hop or VCD, State/Mode

(172.27.112.66, 239.5.3.65), 00:05:00/00:03:29, flags: FT
Incoming interface: Vlan521, RPF nbr 0.0.0.0
Outgoing interface list:
GigabitEthernet1/3, Forward/Sparse, 00:00:56/00:02:33

HRSWI-01#Mtrace 172.27.112.66
Type escape sequence to abort.
Mtrace from 172.27.112.66 to 172.27.112.65 via RPF
From source (?) to destination (?)
Querying full reverse path...

0 172.27.112.65
-1 172.27.112.65 ==> 172.27.112.65 PIM [172.27.112.64/26]
-2 172.27.112.66

HR-SWI-01(config-if)#ip mroute 172.27.112.66 255.255.255.255 172.27.255.61

HR-SWI-01#sh Ip mroute 172.27.112.66 239.5.3.65
IP Multicast Routing Table
Interface state: Interface, Next-Hop or VCD, State/Mode

(172.27.112.66, 239.5.3.65), 00:09:30/00:01:38, flags:
Incoming interface: GigabitEthernet1/1, RPF nbr 172.27.255.61, Mroute
Outgoing interface list:
GigabitEthernet1/3, Forward/Sparse, 00:02:05/00:03:22

No such command as rpf check 

HR-SWI-01#Mtrace 172.27.112.66
Type escape sequence to abort.
Mtrace from 172.27.112.66 to 172.27.112.65 via RPF
From source (?) to destination (?)
Querying full reverse path...
0 172.27.112.65
-1 172.27.112.65 ==> 172.27.255.62 PIM [172.27.112.66/32]
-2 172.27.255.61 ==> 172.27.255.77 None [172.27.112.64/26]
-3 172.27.255.78 ==> 172.27.255.121 None [172.27.112.64/26]
-4 172.27.255.122 ==> 172.27.255.129 None [172.27.112.64/26]
-5 172.27.255.130 ==> 172.27.255.134 PIM [default]
-6 172.27.255.133 ==> 172.27.255.62 PIM [172.27.112.66/32]
-7 172.27.255.61 ==> 172.27.255.77 None [172.27.112.64/26]
-8 172.27.255.78 ==> 172.27.255.121 None [172.27.112.64/26]
-9 172.27.255.122 ==> 172.27.255.129 None [172.27.112.64/26]
-10 172.27.255.130 ==> 172.27.255.134 PIM [default]
-11 172.27.255.133 ==> 172.27.255.62 PIM [172.27.112.66/32]
-12 172.27.255.61 ==> 172.27.255.77 None [172.27.112.64/26]
-13 172.27.255.78 ==> 172.27.255.121 None [172.27.112.64/26]
-14 172.27.255.122 ==> 172.27.255.129 None [172.27.112.64/26]
-15 172.27.255.130 ==> 172.27.255.134 PIM [default]
-16 172.27.255.133 ==> 172.27.255.62 PIM [172.27.112.66/32]
-17 172.27.255.61 ==> 172.27.255.77 None [172.27.112.64/26]
-18 172.27.255.78 ==> 172.27.255.121 None [172.27.112.64/26]
-19 172.27.255.122 ==> 172.27.255.129 None [172.27.112.64/26]
-20 172.27.255.130 ==> 172.27.255.134 PIM [default]
-21 172.27.255.133 ==> 172.27.255.62 PIM [172.27.112.66/32]
-22 172.27.255.61 ==> 172.27.255.77 None [172.27.112.64/26]
-23 172.27.255.78 ==> 172.27.255.121 None [172.27.112.64/26]
-24 172.27.255.122 ==> 172.27.255.129 None [172.27.112.64/26]
-25 172.27.255.130 ==> 172.27.255.134 PIM [default]
-26 172.27.255.133 ==> 172.27.255.62 PIM [172.27.112.66/32]
-27 172.27.255.61 ==> 172.27.255.77 None [172.27.112.64/26]
-28 172.27.255.78 ==> 172.27.255.121 None [172.27.112.64/26]
-29 172.27.255.122 ==> 172.27.255.129 None [172.27.112.64/26]
-30 172.27.255.130 ==> 172.27.255.134 PIM [default]
-31 172.27.255.133 ==> 172.27.255.62 PIM [172.27.112.66/32]
-32 172.27.255.61 ==> 172.27.255.77 None [172.27.112.64/26]
-33 172.27.112.66

Thank you

snippnet config on HR-SWI-01
!
interface GigabitEthernet1/1
description Uplink to TO-SWI-04 (Gi3/10)
no switchport
ip address 172.27.255.62 255.255.255.252
ip authentication mode eigrp 64512 md5
ip authentication key-chain eigrp 64512 eigrp
ip hello-interval eigrp 64512 1
ip hold-time eigrp 64512 3
ip pim sparse-mode
ip summary-address eigrp 64512 172.27.112.0 255.255.252.0
load-interval 30
carrier-delay msec 0
flowcontrol receive desired
!
interface GigabitEthernet1/3
description Uplink to LA-SWI-02 (Gi1/1/3)
no switchport
ip flow ingress
ip flow egress
ip address 172.27.255.133 255.255.255.252
ip authentication mode eigrp 64512 md5
ip authentication key-chain eigrp 64512 eigrp
ip hello-interval eigrp 64512 1
ip hold-time eigrp 64512 3
ip pim sparse-mode
load-interval 30
carrier-delay msec 0
flowcontrol receive desired
!

!
interface Vlan521
description CCTV
ip address 172.27.112.65 255.255.255.192
ip pim sparse-mode

!
router eigrp 64512
network 172.27.0.0
network 172.27.48.0 0.0.7.255
network 172.27.112.0 0.0.0.63
network 172.27.112.64 0.0.0.63
network 172.27.112.128 0.0.0.63
network 172.27.255.60 0.0.0.3
network 172.27.255.132 0.0.0.3
redistribute connected
redistribute static
passive-interface default
no passive-interface GigabitEthernet1/1
no passive-interface GigabitEthernet1/3
nsf

[Jon Marshall · Accepted solution]

I may not be understanding the full layout but you seem to be applying the mroute to the wrong switch ie. it should be applied to the TO-SWI-04 switch.

That aside I think the main problem is that you are advertising a summary route from HR-SWI-01 to TO-SW1-04 that covers the source IP of the multicast stream but you are not advertising the summary to LA-SW1-02 which means TO-SW1-04 sees a more specific route via the long way round.

PIM uses the routing table so when a client connected to TO-SW1-04 wants to receive the stream that switch will send the PIM join request to F-SW1-01 because of the more specific route for the subnet.

So if you want the traffic to go direct to TO-SWI-04 from HR-SWI-01 you need to modify the routing in some way ie. advertise a summary both ways, stop advertising the summary just the one way or use a specific mroute entry for the host sending the stream.

Jon

[webmike10]

Amazing Jon AND PAUL!  Thank you for working through the problem until the end.  I will revisit the eigrp summary routes as you stated.  As of now, you taught me commands to use to troubleshoot, diagnosis and finally give me the solution which was to add the mroute on the core switch, TO-SWI-01 rather than HR-SWI-01.  As much document that exists online, sometimes direct help is still required.  That mistake won't be made again! Thanks again!

[Jon Marshall]

Glad to help although I think Paul deserves most of the credit, I just came in at the end :)

Jon

[paul driver]

Hello

Glad you got it sorted - for some reason I had it in my mind that the mc source was originating on sw4 even though it actually is applied to vlan 521 of Hsw1

apologies for that and kudos to Jon yet again showing the error of my ways!

res

paul