mroute table - Page 3

suthomas1 · ‎11-15-2012

We have a 3750 acting as the core. By default IGMP snooping is enabled on cisco 3750 from the documents.

but, when we see the ip mroute table on the switch, it doesnt show any output.

what could be the cause. Thanks in advance!

suthomas1 · ‎12-30-2012

Yes the ping reachability is fine. The unicast support portion has been referred to the respective team to be checked.

Meantime, i wanted to check if there is anything else that needs to be done from network portion for unicast if the ping is fine.

Raju Sekharan · ‎12-30-2012

Hi

If your ping reacahbility is fine, there is no other configuration required on the switch

Thanks

Raju

suthomas1 · ‎01-01-2013

Thanks Again. So in that case with IP base, only ip pim passive is available on the interface for multicast.

So, is it correct if i say , with ip pim passive in ip base the multicast would only server the local network in a site and not be able to be accessible via remote sites.

Raju Sekharan · ‎01-01-2013

Hi

I apologize. There was a mistake in my previous reply

You can route the multi-cast traffc out on your L3 ports( which are not SVI). So your multi-cast routing to the remote sites should work fine via L3 ports. I tested it in my LAB and it is working fine

BGL.T.09-3700-12#sh run int gi 3/0/1

Building configuration...

Current configuration : 118 bytes

!

interface GigabitEthernet3/0/1

no switchport

ip address 192.168.12.2 255.255.255.0

ip pim sparse-dense-mode

end

3700-12#sh ver | inc .bin

System image file is "flash:c3750-ipbasek9-mz.122-55.SE5.bin"

3700-12#sh run int gi 3/0/2

Building configuration...

Current configuration : 118 bytes

!

interface GigabitEthernet3/0/2

no switchport

ip address 192.168.23.2 255.255.255.0

ip pim sparse-dense-mode

end

3700-12#sh ip mroute

IP Multicast Routing Table

(*, 239.0.0.2), 00:01:02/00:03:27, RP 10.0.0.1, flags: SF

Incoming interface: GigabitEthernet3/0/1, RPF nbr 192.168.12.1

Outgoing interface list:

GigabitEthernet3/0/2, Forward/Sparse-Dense, 00:01:02/00:03:27

(192.168.12.1, 239.0.0.2), 00:00:34/00:03:24, flags: FT

Incoming interface: GigabitEthernet3/0/1, RPF nbr 0.0.0.0

Outgoing interface list:

GigabitEthernet3/0/2, Forward/Sparse-Dense, 00:00:35/00:03:26

(*, 224.0.1.40), 00:09:22/00:02:55, RP 10.0.0.1, flags: SJCL

Incoming interface: GigabitEthernet3/0/1, RPF nbr 192.168.12.1

Outgoing interface list:

GigabitEthernet3/0/2, Forward/Sparse-Dense, 00:04:13/00:02:58

Thanks

Raju

suthomas1 · ‎01-02-2013

Thanks again Raju.

Sorry, i am not very conversant with mulitcasting, hence the questions.

In our case the vlan 150(streaming server) & vlan 160(users) are an SVI on the 3750 with ip base version.

Will the above( users in vlan 160 be able to access the video from vlan 150) work in this scenario.

or is an upgraded version required for this to work as this is an SVI. thanks again.

Raju Sekharan · ‎01-03-2013

Hi

I connected multicast source directly on Vlan 160 and a user in Vlan 150 of this switch. Configured multicast-routing and configured this switch itself as RP and multicast worked from Vlan 160 to 150

Here is the output

interface Vlan160

ip address 192.168.23.2 255.255.255.0

ip pim passive

end

BGL.T.09-3700-12#sh run int vlan 150

Building configuration...

Current configuration : 80 bytes

!

interface Vlan150

ip address 192.168.12.2 255.255.255.0

ip pim passive

end

BGL.T.09-3700-12#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.0.0.2), 00:17:31/stopped, RP 10.0.0.2, flags: SJC

Incoming interface: Null, RPF nbr 0.0.0.0

Outgoing interface list:

Vlan150, Forward/Sparse-Dense, 00:01:22/00:02:37

(192.168.23.3, 239.0.0.2), 00:00:12/00:02:47, flags: T

Incoming interface: Vlan160, RPF nbr 0.0.0.0

Outgoing interface list:

Vlan150, Forward/Sparse-Dense, 00:00:12/00:02:47

Thanks

Raju

suthomas1 · ‎01-03-2013

Thanks Raju.

So in essence, we will need ip service only if this stream is to be accessed by remote sites.

for local within same site, base version will be fine.

Raju Sekharan · ‎01-04-2013

It should work for remote users connected via L3 ports too becasue PIM protocol is supported on L3 ports. I have tested it. Traffic connected directly on VLAN 150 and users on remote-router connected Via l3 port Gi 3/0/2

(192.168.12.1, 239.0.0.2), 00:00:09/00:03:26, flags: T

Incoming interface: Vlan150, RPF nbr 0.0.0.0

Outgoing interface list:

GigabitEthernet3/0/2, Forward/Sparse-Dense, 00:00:09/00:03:20

http://www.cisco.com/image/gif/paws/98289/pim_stub.pdf

Thanks

Ra

suthomas1 · ‎01-04-2013

thanks Raju.

Alright, so remote sites over WAN will also work if the ports connecting them are L3 ports with Ip base version.

But if the remote sites are connected using SVI between the core switch and WAN router, it will need ip services?

Is that correct?

Raju Sekharan · ‎01-05-2013

Question : if the remote sites are connected using SVI between the core switch and WAN router, it will need ip services?

Answer:

You can still make it work by using ip igmp helper-address on the remote routes so that the remote routers forward the IGMP requests direclty to the stub-router 3750. This will work like Dense mode ( Flood and prune)

I think it is better to use ip services image if you would like to use SVI bewteen the core switch and WAN router

Thanks

Raju

suthomas1 · ‎01-06-2013

Raju,

two queries on this:-

1.with pim passive, why does it not work on non-L3 interface for transmission across remote sites?

2. i see that you mentioned about the rp being the switch itself, however what happens if the rp address is a router somewhere in the wan network? will pim passive still work?