cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
6988
Views
0
Helpful
23
Replies

Multicast does not work between differents VLAN

Hello,

We try to activate multicast here and it does not seems to work properly.

There is our configuration :

Core : 4506 with L3 routing

Distribution : 3750 L2 only

Access: 2950 L2 only

On the 4506 we have those commands configured :

ip multicast routing

ip pim rp-address x.x.x.x      where x.x.x.x=4506 IP address

on each VLAN, we have the command ip pim sparse-dense-mode activated.

We make our test with VLC Media player.

We are able to multicast on the same VLAN...but it does not seems to works between different vlan.

On the same VLAN we see the Networks Stream (SAP) annoucement appears in VLC (on the receiver PC), but on different VLAN, we don't see it. I've also try to force receiving by entering, on the receiver PC, the multicast address entered on VLC in the transmitter PC but that don't work.

For VLC, I've put 10 for TTL to be sure that all VLAN will be reached.

We have no access list configured on the two differents VLAN that we make our tests.

Someone can help?

Thanks,

Martin

23 Replies 23

Hi Jon,

The Source is x.x.12.21

The Receiver is x.x.48.210

There is not ACL on VLAN12 and VLAN48. Only ACL to limit access to VLAN1

I've paste the vlan intercace config only for VLAN12 and 48.

here is the capture requested:

From CoreJ130 x.x.1.2

COREJ130#sh run int vlan 12

Building configuration...

Current configuration : 265 bytes

!

interface Vlan12

ip address x.x.13.2 255.255.252.0

no ip redirects

no ip proxy-arp

ip pim sparse-dense-mode

ip route-cache same-interface

standby 12 ip x.x.12.1

standby 12 ip x.x.13.1 secondary

standby 12 priority 110

standby 12 preempt

end

COREJ130#sh run int vlan 48

Building configuration...

Current configuration : 298 bytes

!

interface Vlan48

ip address x.x.49.2 255.255.252.0

ip helper-address x.x.52.11

no ip redirects

no ip proxy-arp

ip pim sparse-dense-mode

ip route-cache same-interface

standby 48 ip x.x.48.1

standby 48 ip x.x.49.1 secondary

standby 48 priority 110

standby 48 preempt

end

COREJ130#sh ip route

Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP

       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area

       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2

       E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP

       i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2

       ia - IS-IS inter area, * - candidate default, U - per-user static route

       o - ODR, P - periodic downloaded static route

Gateway of last resort is 192.168.115.1 to network 0.0.0.0

     172.16.0.0/23 is subnetted, 2 subnets

S       172.16.8.0 [1/0] via 192.168.252.2

C       172.16.4.0 is directly connected, Vlan164

C   192.168.115.0/24 is directly connected, Vlan777

     10.0.0.0/8 is variably subnetted, 21 subnets, 5 masks

C       10.200.252.32/29 is directly connected, Vlan300

C       10.200.252.4/30 is directly connected, Vlan251

S       10.200.64.0/20 [1/0] via 10.200.252.6

C       10.200.2.0/23 is directly connected, Vlan302

S       10.200.1.0/24 [1/0] via 10.200.252.37

C       10.200.6.0/23 is directly connected, Vlan306

C       10.200.4.0/23 is directly connected, Vlan304

C       10.200.10.0/23 is directly connected, Vlan310

C       10.200.8.0/23 is directly connected, Vlan308

C       10.200.14.0/23 is directly connected, Vlan314

C       10.200.12.0/23 is directly connected, Vlan312

C       10.200.18.0/23 is directly connected, Vlan318

C       10.200.16.0/23 is directly connected, Vlan316

C       10.200.22.0/23 is directly connected, Vlan322

C       10.200.20.0/23 is directly connected, Vlan320

C       10.200.26.0/23 is directly connected, Vlan326

C       10.200.24.0/23 is directly connected, Vlan324

C       10.200.30.0/23 is directly connected, Vlan330

C       10.200.28.0/23 is directly connected, Vlan328

C       10.200.34.0/23 is directly connected, Vlan334

C       10.200.32.0/23 is directly connected, Vlan332

     x.x.0.0/16 is variably subnetted, 25 subnets, 6 masks

S       x.x.64.0/22 [1/0] via 192.168.252.2

S       x.x.68.0/23 [1/0] via 192.168.252.2

S       x.x.72.0/24 [1/0] via 192.168.115.1

C       x.x.16.0/22 is directly connected, Vlan16

C       x.x.20.0/22 is directly connected, Vlan20

C       x.x.26.0/24 is directly connected, Vlan26

C       x.x.25.0/24 is directly connected, Vlan25

C       x.x.24.0/24 is directly connected, Vlan24

S       x.x.28.0/23 [1/0] via 192.168.116.1

S       x.x.2.0/24 [1/0] via 192.168.252.2

C       x.x.1.0/24 is directly connected, Vlan1

C       x.x.11.0/24 is directly connected, Vlan11

C       x.x.10.0/24 is directly connected, Vlan10

C       x.x.12.0/22 is directly connected, Vlan12

C       x.x.48.0/22 is directly connected, Vlan48

C       x.x.52.0/24 is directly connected, Vlan52

S       x.x.60.0/22 [1/0] via 192.168.252.2

C       x.x.33.0/26 is directly connected, Vlan33

C       x.x.32.0/24 is directly connected, Vlan32

C       x.x.41.0/24 is directly connected, Vlan41

C       x.x.40.0/26 is directly connected, Vlan401

C       x.x.44.0/24 is directly connected, Vlan44

C       x.x.40.248/29 is directly connected, Vlan406

C       x.x.40.240/29 is directly connected, Vlan405

C       x.x.40.224/28 is directly connected, Vlan404

C   192.168.2.0/24 is directly connected, Vlan192

C   192.168.252.0/24 is directly connected, Vlan252

C   192.168.116.0/24 is directly connected, Vlan116

S*   0.0.0.0/0 [1/0] via 192.168.115.1


From CoreD003 x.x.1.3

CORED003#sh run int vlan 12

Building configuration...

Current configuration : 220 bytes

!

interface Vlan12

ip address x.x.13.3 255.255.252.0

no ip redirects

no ip proxy-arp

ip pim sparse-dense-mode

ip route-cache same-interface

standby 12 ip x.x.12.1

standby 12 ip x.x.13.1 secondary

end

CORED003#sh run int vlan 48

Building configuration...

Current configuration : 253 bytes

!

interface Vlan48

ip address x.x.49.3 255.255.252.0

ip helper-address x.x.52.11

no ip redirects

no ip proxy-arp

ip pim sparse-dense-mode

ip route-cache same-interface

standby 48 ip x.x.48.1

standby 48 ip x.x.49.1 secondary

end

CORED003#sh ip route

Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP

       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area

       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2

       E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP

      i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2

       ia - IS-IS inter area, * - candidate default, U - per-user static route

       o - ODR, P - periodic downloaded static route

Gateway of last resort is 192.168.115.1 to network 0.0.0.0

     172.16.0.0/23 is subnetted, 1 subnets

C       172.16.4.0 is directly connected, Vlan164

C   192.168.115.0/24 is directly connected, Vlan777

     10.0.0.0/8 is variably subnetted, 19 subnets, 3 masks

C       10.200.252.32/29 is directly connected, Vlan300

C       10.200.2.0/23 is directly connected, Vlan302

S       10.200.1.0/24 [1/0] via x.x.1.2

C       10.200.6.0/23 is directly connected, Vlan306

C       10.200.4.0/23 is directly connected, Vlan304

C       10.200.10.0/23 is directly connected, Vlan310

C       10.200.8.0/23 is directly connected, Vlan308

C       10.200.14.0/23 is directly connected, Vlan314

C       10.200.12.0/23 is directly connected, Vlan312

C       10.200.18.0/23 is directly connected, Vlan318

C       10.200.16.0/23 is directly connected, Vlan316

C       10.200.22.0/23 is directly connected, Vlan322

C       10.200.20.0/23 is directly connected, Vlan320

C       10.200.26.0/23 is directly connected, Vlan326

C       10.200.24.0/23 is directly connected, Vlan324

C       10.200.30.0/23 is directly connected, Vlan330

C       10.200.28.0/23 is directly connected, Vlan328

C       10.200.34.0/23 is directly connected, Vlan334

C       10.200.32.0/23 is directly connected, Vlan332

     x.x.0.0/16 is variably subnetted, 20 subnets, 6 masks

C       x.x.16.0/22 is directly connected, Vlan16

C       x.x.20.0/22 is directly connected, Vlan20

C       x.x.26.0/24 is directly connected, Vlan26

C       x.x.25.0/24 is directly connected, Vlan25

C       x.x.24.0/24 is directly connected, Vlan24

S       x.x.28.0/23 [1/0] via 192.168.116.1

C       x.x.1.0/24 is directly connected, Vlan1

C       x.x.11.0/24 is directly connected, Vlan11

C       x.x.10.0/24 is directly connected, Vlan10

C       x.x.12.0/22 is directly connected, Vlan12

C     x.x.48.0/22 is directly connected, Vlan48

C       x.x.52.0/24 is directly connected, Vlan52

C       x.x.33.0/26 is directly connected, Vlan33

C       x.x.32.0/24 is directly connected, Vlan32

C       x.x.41.0/24 is directly connected, Vlan41

C       x.x.40.0/26 is directly connected, Vlan401

C       x.x.44.0/24 is directly connected, Vlan44

C       x.x.40.248/29 is directly connected, Vlan406

C       x.x.40.240/29 is directly connected, Vlan405

C       x.x.40.224/28 is directly connected, Vlan404

C   192.168.2.0/24 is directly connected, Vlan192

C   192.168.116.0/24 is directly connected, Vlan116

S*   0.0.0.0/0 [1/0] via 192.168.115.1

Martin

What ip address are you actually using for the RP ?

Jon

Jon,

RP address is x.x.1.2. It's configured on the two core switch.

Martin

Is that address assigned to the vlan 1 interface ? You said you had an acl on the vlan 1 interface didn't you ?

If the rp is the address of vlan 1 interface and the acl is applied to the vlan interface could you temporarily remove the acl of both vlan interfaces and retest.

*** Edit - if this does work then can you clarify which switch is HSRP active for vlan 1 ie. is it the same switch that is active for the src/dst multicast vlans.

Jon

Hi Jon,

yes, x.x.1.2 is the VLAN1 interface IP address on the CoreJ130 Switch. This switch is the HSRP Active and it's the same active switch for vlan12 and 48 (src/dst)

I've removed the ACL on VLAN 1 for testing purpose and still not works. There is no acl on vlan 12(src) and 48(dst).

Martin

Have you enabled pim on the vlan 1 interface that is the RP ie.

int vlan 1

ip pim sparse-dense-mode

Jon

Jon, you are the king! It working pretty fine now that I have ip pim sparse-dense-mode activated on VLAN 1 on both Core Switch. I forgot this command on the VLAN1 interface. I set this command on all interfaces, but I had not thought the VLAN1. I understand that it is required because the RP is on that VLAN.

Thank you for your help and patience! It's very appreciated!

Martin Arsenault

Martin

Well, i'm glad we finally got that one sorted, i was running out of ideas

Thanks for the rating.

Jon

runinorte
Level 1
Level 1

Hi,

I have the same problem... https://supportforums.cisco.com/thread/2251574

I need help.

Thanks.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: