cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1106
Views
0
Helpful
1
Replies

Muticast problem with virtual WLC and mesh

chrissw
Level 1
Level 1

I have a problem with vWLC (8.10.151) and multicast. I don't have this problem with a 2504 controller, with which everything works perfectly.

 

At this stage I'd just like to know if it is in fact possible to do what I need or if this is not supported with vWLC.

 

I have a root AP 3702 in flex+bridge mode and 2x 3702 mesh APs also in Flex+Bridge.

 

There is a TV connected to the ethernet port of one of the mesh APs.

 

There is a DLNA server on the wired network that announces itself to 239.255.255.250. The TV needs to see these multicast announcements. IGMP doesn't seem to be involved here; if the TV can see the multicast announcements, then it can stream content from the DLNA server. The TV and server are on the same subnet and unicast traffic works fine over the mesh.

 

Now the vWLC requires FlexConnect and it doesn't support multicast mode. Also there is a guest SSID which maps to a different VLAN. In order to get the two SSIDs working correctly, I had to make a VLAN mapping on the root AP. It seems that this VLAN mapping prevents these multicast announcements from reaching the TV conneced to the Ethernet port of a mesh AP.

 

Without the VLAN mapping on the root AP, the main (non-guest) SSID works fine and so does the TV, but clients on the guest SSID get IP addresses from the main SSID. Clearly that's not a good situation. The root AP is on a trunk switch port with both correct VLANs permitted (the main SSID is the native VLAN of that switch port).

 

So it seems I have a choice between DLNA working or guest working; I can't have both at the same time. But this all works fine with the 2504 WLC, in multicast mode and all APs in bridge mode.

 

Can anyone suggest what I might be doing wrong?

 

Edit: I've discovered that the multicast traffic in question is sent on the relevant SSID on the root AP, and if the TV connects wirelessly to the root AP then everything works. However there's no way to force a client to connect to a certain AP so this is not a viable solution. The multicast just doesn't go over the mesh.

1 Reply 1

TarasF
Level 1
Level 1

Hello, I had the same problem with VLAN segmentation at vWLC. You should check which FlexConnect Group Name at the APs mapped. In my case it is default-flex-group. In your controller go to the WIRELESS->FlexConnect Groups->default-flex-group->WLAN VLAN mapping-> and put a tick at VLAN Support and Override VLAN on APs. Also, the tick should stay enabled at VLAN Support in the field FlexConnect in your APs

Review Cisco Networking for a $25 gift card