Wireless Access

Reading the Airgroups deployment guide talks about support for wired AirGroup servers by using the AP's uplink port to aggergate the multicast packets from the same L3 switch which the AP is connected to as the wired mDNS server.  I attempted to configure this in the lab but I have some questions the guide doesn't exactly explain.  Also does the AP wired port have to be configured for a trunk, or can it be a standard access port like any typical AP deployed in our network. 

The AP system profile have to enable 

AP multicast aggregation: Enable

AP multicast aggregation allowed VLANs:  <Is this the vlan which the ports are configured on the L3 switch, or vlan want the Mcast packets to be sent to like WLAN vlan of the user>  

---

@kell490 wrote:

The AP system profile have to enable 

AP multicast aggregation: Enable

AP multicast aggregation allowed VLANs:  <Is this the vlan which the ports are configured on the L3 switch, or vlan want the Mcast packets to be sent to like WLAN vlan of the user>  

---

The AP multicast aggregation allowed VLANs parameter defines which VLANs the AP will listen for mDNS on. That learned mDNS information is passed up to the controller via the AP's tunnel.

Does the multicast aggregation vlan have to exist on the controller? Can it only be on the L3 switch which where the AP and mDNS wired server plug into? 

No, the vlan does not have to exist on the controller. If the vlan does exist on the controller, then the ap multicast aggregation feature is not needed.