04-22-2010 10:24 AM - edited 03-04-2019 08:15 AM
Topology is as follows.
Informacast server --> 3750-->2811-->MPLS-->2811-->3750-->iphone
I have configured ip pim sparse-dense-mode on all interfaces along this path. One item that may be a problem is that the 3750's have the c3750e-universal-mz.122-50.SE image and it only gives me ip pim passive. Since the multicast is going through this switch from the server I think they may be a problem. but here are some output from the switches and routers. Any help would be greatly appreciated. By the way, the multicast to phones off of the first 3750 switch works.
3750
interface Vlan200
description Server
ip address 192.168.200.254 255.255.255.0
ip pim passive
ip igmp helper-address 172.16.12.9
end
interface Vlan253
description :Transit VLAN to WAN Router
ip address 172.16.253.1 255.255.255.0
ip pim passive
ip igmp helper-address 172.16.12.9
end
ip pim rp-address 172.16.12.1
GMI-LF-3750-Stack#sh ip igmp group
IGMP Connected Group Membership
Group Address Interface Uptime Expires Last Reporter Group Accounted
239.255.255.254 Vlan200 02:01:53 00:02:54 192.168.200.5
239.255.255.253 Vlan200 02:01:52 00:02:59 192.168.200.9
239.255.255.250 Vlan200 02:01:53 00:02:52 192.168.200.48
239.255.255.250 Vlan8 03:02:30 00:02:59 192.168.80.7
239.255.255.250 Vlan19 03:28:17 00:02:01 192.168.190.15
239.255.255.250 Vlan13 03:31:44 00:02:59 192.168.130.2
239.255.255.250 Vlan3 03:42:28 00:01:59 192.168.30.6
239.255.255.250 Vlan9 2w1d 00:02:58 192.168.90.1
239.255.255.250 Vlan10 7w1d 00:02:59 192.168.100.5
239.255.255.250 Vlan5 8w4d 00:01:58 192.168.50.5
239.255.255.250 Vlan4 43w4d 00:02:59 192.168.40.7
239.255.255.250 Vlan12 44w5d 00:02:59 192.168.120.3
239.255.255.250 Vlan14 44w5d 00:02:58 192.168.140.2
239.255.255.250 Vlan7 44w5d 00:02:59 192.168.70.3
239.255.255.250 Vlan11 44w5d 00:02:59 192.168.110.11
239.255.255.250 Vlan16 44w5d 00:02:59 192.168.160.1
239.255.255.250 Vlan15 44w5d 00:02:59 192.168.150.4
239.255.255.250 Vlan6 44w5d 00:02:58 192.168.60.1
224.0.1.24 Vlan200 02:01:51 00:02:54 192.168.200.17
224.0.1.60 Vlan5 02:34:10 00:02:05 192.168.50.2
IGMP Connected Group Membership
Group Address Interface Uptime Expires Last Reporter Group Accounted
224.0.1.60 Vlan18 3w4d 00:01:58 192.168.180.133
224.0.1.60 Vlan14 44w4d 00:02:53 192.168.140.202
224.0.1.40 Vlan253 01:57:24 00:02:10 172.16.253.9
GMI-LF-3750-Stack#sh 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,
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
V - RD & Vector, v - Vector
Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 239.255.255.254), 10w4d/00:02:16, RP 172.16.12.1, flags: SJC
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Vlan200, Forward/Sparse-Dense, 02:02:32/00:02:16
(*, 239.255.255.253), 12w5d/00:02:38, RP 172.16.12.1, flags: SJC
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Vlan200, Forward/Sparse-Dense, 02:02:32/00:02:21
(*, 239.255.255.250), 44w5d/stopped, RP 172.16.12.1, flags: SJC
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Vlan200, Forward/Sparse-Dense, 02:02:32/00:02:26
Vlan8, Forward/Sparse-Dense, 03:03:10/00:02:21
Vlan19, Forward/Sparse-Dense, 03:28:57/00:02:23
Vlan13, Forward/Sparse-Dense, 03:32:23/00:02:20
Vlan3, Forward/Sparse-Dense, 03:43:08/00:02:22
Vlan9, Forward/Sparse-Dense, 2w1d/00:02:20
Vlan10, Forward/Sparse-Dense, 7w1d/00:02:16
Vlan5, Forward/Sparse-Dense, 8w4d/00:02:18
Vlan4, Forward/Sparse-Dense, 43w4d/00:02:16
Vlan12, Forward/Sparse-Dense, 44w5d/00:02:16
Vlan14, Forward/Sparse-Dense, 44w5d/00:02:15
Vlan7, Forward/Sparse-Dense, 44w5d/00:02:16
Vlan11, Forward/Sparse-Dense, 44w5d/00:02:16
Vlan16, Forward/Sparse-Dense, 44w5d/00:02:16
Vlan15, Forward/Sparse-Dense, 44w5d/00:02:16
Vlan6, Forward/Sparse-Dense, 44w5d/00:02:15
(192.168.200.44, 239.255.255.250), 00:03:06/00:02:27, flags: T
Incoming interface: Vlan200, RPF nbr 0.0.0.0
Outgoing interface list:
Vlan6, Forward/Sparse-Dense, 00:03:06/00:02:15
Vlan15, Forward/Sparse-Dense, 00:03:06/00:02:16
Vlan16, Forward/Sparse-Dense, 00:03:06/00:02:16
Vlan11, Forward/Sparse-Dense, 00:03:06/00:02:16
Vlan7, Forward/Sparse-Dense, 00:03:06/00:02:16
Vlan14, Forward/Sparse-Dense, 00:03:06/00:02:15
Vlan12, Forward/Sparse-Dense, 00:03:06/00:02:16
Vlan4, Forward/Sparse-Dense, 00:03:06/00:02:16
Vlan5, Forward/Sparse-Dense, 00:03:06/00:02:18
Vlan10, Forward/Sparse-Dense, 00:03:07/00:02:15
Vlan9, Forward/Sparse-Dense, 00:03:07/00:02:14
Vlan3, Forward/Sparse-Dense, 00:03:07/00:02:17
Vlan13, Forward/Sparse-Dense, 00:03:07/00:02:15
Vlan19, Forward/Sparse-Dense, 00:03:07/00:02:17
Vlan8, Forward/Sparse-Dense, 00:03:07/00:02:15
(*, 224.0.1.24), 10w4d/00:02:10, RP 172.16.12.1, flags: SJC
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Vlan200, Forward/Sparse-Dense, 02:02:36/00:02:10
(*, 224.0.1.60), 44w5d/00:02:23, RP 172.16.12.1, flags: SJC
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Vlan5, Forward/Sparse-Dense, 02:34:55/00:02:18
Vlan18, Forward/Sparse-Dense, 3w4d/00:02:23
Vlan14, Forward/Sparse-Dense, 44w4d/00:02:15
(*, 224.0.1.40), 00:36:53/00:02:41, RP 172.16.12.1, flags: SJPC
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list: Null
(*, 224.0.1.41), 01:48:02/stopped, RP 172.16.12.1, flags: SP
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list: Null
(172.16.12.9, 224.0.1.41), 01:45:26/00:01:38, flags: PT
Incoming interface: Vlan112, RPF nbr 0.0.0.0
Outgoing interface list: Null
(172.16.12.10, 224.0.1.41), 01:46:01/00:02:43, flags: PT
Incoming interface: Vlan112, RPF nbr 0.0.0.0
Outgoing interface list: Null
First 2811
GMILF-2811-VG2#sh ip igmp group
IGMP Connected Group Membership
Group Address Interface Uptime Expires Last Reporter Group Accounted
239.255.255.254 FastEthernet0/0.112 00:49:09 00:02:18 172.16.12.1
239.255.255.253 FastEthernet0/0.112 00:49:04 00:02:19 172.16.12.1
239.255.255.250 FastEthernet0/0.112 00:49:10 00:02:30 172.16.12.1
224.0.1.24 FastEthernet0/0.112 00:49:03 00:02:18 172.16.12.1
224.0.1.40 FastEthernet0/0.112 00:48:37 00:02:47 172.16.12.1
224.0.1.40 FastEthernet0/0.253 01:58:55 00:02:47 172.16.253.9
GMILF-2811-VG2#
GMILF-2811-VG2#sh 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,
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
Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 239.255.255.254), 00:37:29/00:02:54, RP 172.16.12.1, flags: SP
Incoming interface: FastEthernet0/0.112, RPF nbr 172.16.12.1
Outgoing interface list: Null
(*, 239.255.255.253), 00:37:24/00:02:53, RP 172.16.12.1, flags: SP
Incoming interface: FastEthernet0/0.112, RPF nbr 172.16.12.1
Outgoing interface list: Null
(*, 239.255.255.250), 00:37:28/00:02:51, RP 172.16.12.1, flags: SP
Incoming interface: FastEthernet0/0.112, RPF nbr 172.16.12.1
Outgoing interface list: Null
(*, 224.0.1.24), 00:37:21/00:02:58, RP 172.16.12.1, flags: SP
Incoming interface: FastEthernet0/0.112, RPF nbr 172.16.12.1
Outgoing interface list: Null
(*, 224.0.1.40), 00:38:11/00:02:21, RP 172.16.12.1, flags: SJPL
Incoming interface: FastEthernet0/0.112, RPF nbr 172.16.12.1
Outgoing interface list: Null
(*, 224.0.1.41), 00:37:50/stopped, RP 172.16.12.1, flags: SP
Incoming interface: FastEthernet0/0.112, RPF nbr 172.16.12.1
Outgoing interface list: Null
(172.16.12.9, 224.0.1.41), 00:37:32/00:02:31, flags: PT
Incoming interface: FastEthernet0/0.112, RPF nbr 0.0.0.0
Outgoing interface list: Null
(172.16.12.10, 224.0.1.41), 00:37:50/00:02:58, flags: PT
Incoming interface: FastEthernet0/0.112, RPF nbr 0.0.0.0
Outgoing interface list: Null
Second 2811
ELECOR-2811-VG1#sh ip igmp group
IGMP Connected Group Membership
Group Address Interface Uptime Expires Last Reporter Group Accounted
224.0.1.40 FastEthernet0/0.112 01:06:05 00:02:30 172.19.12.1
ELECOR-2811-VG1#
ELECOR-2811-VG1#sh 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,
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,
V - RD & Vector, v - Vector
Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 224.0.1.40), 00:38:36/00:02:12, RP 172.16.12.1, flags: SJCL
Incoming interface: FastEthernet0/1, RPF nbr 10.255.255.5
Outgoing interface list:
FastEthernet0/0.112, Forward/Sparse-Dense, 00:38:36/00:02:12
(*, 224.0.1.41), 00:38:11/stopped, RP 172.16.12.1, flags: SPF
Incoming interface: FastEthernet0/1, RPF nbr 10.255.255.5
Outgoing interface list: Null
(172.19.12.1, 224.0.1.41), 00:38:11/00:02:40, flags: PFT
Incoming interface: FastEthernet0/0.112, RPF nbr 0.0.0.0, Registering
Outgoing interface list: Null
04-22-2010 11:43 AM
Hello Vclawson,
some other information is needed, so some questions follows:
a) kind of MPLS service
with MPLS what do you mean?
If you have two sites connected by an MPLS L3 VPN you cannot setup multicast routing without cooperation with ISP unless you setup a point-to-point GRE tunnel between the two C2811
if you have a different type of service like a L2 VPN or simply you have bought a transport service you can go on in this way
b) you are trying to use PIM stub on the C3750 there is at least one interface that is not in passive mode and that connects the C3750 with the C2811.
c) another important point:
even if you are using PIM sparse-dense mode you need to configure a rendezvous-point, then groups served by RP will be treated as sparse and groups not served by RP are treated as dense.
But you still need to configure a RP
see
Hope to help
Giuseppe
04-22-2010 11:57 AM
Thanks for the response. The ISP has opened up the MPLS for multicast. The 3750 is configured with ip pim passive because the ios image only gives me that option. I can't configure sparse-dense-mode as I have on the other devices. The question there is do I need to put a differen image on there so it is not a stub. I have configured an RP on both the 3750 and the 2811 but neither has worked. So the switchport that connects the 2811 needs to have ip pim passive?
04-22-2010 12:19 PM
Hello VcLawson,
but it is an MPLS L3 VPN or not?
if it is, the RP has to be chosen in agreement with the ISP
about C3750:
PIM stub routing moves routed traffic closer to the end user and reduces network traffic. You can also reduce traffic by configuring a stub router (switch) with the IGMP helper feature.
You can configure a stub router (switch) with the igmp helper help-address interface configuration command to enable the switch to send reports to the next-hop interface. Hosts that are not directly connected to a downstream router can then join a multicast group sourced from an upstream network. The IGMP packets from a host wanting to join a multicast stream are forwarded upstream to the next-hop device when this feature is configured. When the upstream central router receives the helper IGMP reports or leaves, it adds or removes the interfaces from its outgoing interface list for that group.
see
>> So the switchport that connects the 2811 needs to have ip pim passive?
the Layer3 interface to router should be configured or for pim (not for passive) if pim is not supported I would not configure igmp helper towards the C2811 but only on client Vlans.
the IGMP helper-address should work for clients that are on Vlans defined on the C3750.
For sure the interface on the C2811 towards the C3750 needs to have pim enabled in order to process relayed IGMP joins and reports (if any)
Hope to help
Giuseppe
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide