07-10-2017 12:23 PM - edited 03-08-2019 11:16 AM
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
Thank you
Solved! Go to Solution.
07-13-2017 12:47 PM
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
07-10-2017 04:03 PM
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
07-10-2017 07:10 PM
Thanks for the response. They are layer 3 switches with
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,
07-11-2017 12:31 AM
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
07-11-2017 06:23 AM
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
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
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.
07-11-2017 01:14 PM
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
07-12-2017 06:47 AM
I added what I thought was a
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
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
(*, 239.5.3.65), 7w0d/stopped, RP 10.10.254.34, flags: SPF
Incoming interface: GigabitEthernet1/1, RPF
Outgoing interface list: Null
(172.27.112.66, 239.5.3.65), 7w0d/00:03:28, flags: FT
Incoming interface: Vlan521, RPF
Outgoing interface list:
GigabitEthernet1/3, Forward/Sparse, 00:00:00/00:03:29
HR-SWI-01#sh
RPF information
RPF interface: GigabitEthernet1/1
RPF
RPF route/mask: 10.10.0.0/16
RPF type: unicast (
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
(*, 239.5.3.65), 7w0d/stopped, RP 10.10.254.34, flags: SJC
Incoming interface: Null, RPF
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
Outgoing interface list:
Vlan17, Forward/Sparse, 16w0d/00:02:58
TO-SWI-04#sh ip rpf 10.10.254.34
RPF information
RPF interface: Loopback2
RPF
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
Address Interface Mpackets In/Out
172.27.255.61 GigabitEthernet3/10 70780/916403
172.27.255.77 GigabitEthernet3/14 25955571/644167 (other
10.10.254.34 Loopback2 0/0
07-12-2017 02:11 PM
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
07-13-2017 06:36 AM
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
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
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
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.
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
Outgoing interface list:
GigabitEthernet1/3, Forward/Sparse, 00:02:05/00:03:22
No such command as
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
07-13-2017 12:47 PM
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
07-13-2017 12:47 PM
Amazing Jon AND PAUL! Thank you for working through the problem until the end. I will revisit the