Do you really need passive clients using multicast in the first place? While this might not seem complicated, without any multicast experience could give yourself some headache.
Basically if you follow this config you will be able to cover most of the WLC part. As multicast packets will travel inside the same VLAN (if anyone else can correct me), I don't see any config needed on your ASA.
Only on switches, you could add the global command: ip igmp snooping.
The customer WLAN network is composed of groups of equipements:
For each group there is an AXIS wireless modem which is in bridge mode.
It do association & authentication with WPA2 key, then 802.1x MSCHAPv2 credentials.
Behind the AXIS, there are 4 equipements in static IP adress, which have to contact 4 different servers.
Currently, authentication with radius server are good only for 30% of groups, and for us, only one equipement have connectivity on the network, the 3 others cannot contact their servers located on wired network.
IntroductionHow to use the Wireless LAN Controller Configuration Analyzer (WLCCA)
Javier Contreras is a Senior Tech Lead for the Wireless Business Unit in Cisco, with over 2 decades of experi...
< PRE >
(#)For this reason being that : - application that doesn't use multicast, sends one copy of each packet ( data unit of traffic at layer 3 ) to each client (" who seeks the traffic ).- application that does use multicast, sends ...
Transferring Crash file from standby:
Login to the Active WLC in HA.
(Cisco Controller) >transfer upload datatype crash
(Cisco Controller) >transfer upload filename <Desired filename>
(Cisco Controller) >transfer up...