Been banging my head against this for a little while, figured I'd take a shot here before the bruise gets too bad...
Network Details:
-IAP-315 cluster running 6.5.4.8
-Airgroup enabled (airplay + custom service mirrorop2s added)
-Broadcast filter disabled
-
-CPPM 6.7.3 (registration enforced)
-Aruba 2930M Switching running 16.04
-Wireless client VLAN is 25
-Clickshare base unit VLAN is 26 (VLAN is trunked to APs).
-Currently firewall rules between the 2 VLANs is completely open. Firewalls are PA.
Clickshare base units are in network integrated mode. This means the internal APs are turned off, and all services work over the ethernet port. The buttons use EAP-PEAP with an AD service account to connect to the secure WiFi and then find their base unit. This all works great.
The base unit also has options to enable services over the wired port. Airplay as well as sharing via the Clickshare mobile app (which uses mirrorop2s) are enabled.
I'll stick to Airplay for simplicity's sake. When I enable Airplay on the base units, Airgroup picks them up, they register to CPPM, the location sharing works great (done by Office floor), devices can Airplay and everything is happy.
After I go away for the weekend, or even after a day, I'll come back to check the IAP cluster and Airgroup shows *nothing*. It's completely blank. I can get the devies to re-register into Airgroup using one of the following methods:
-toggling support for Airplay on the base units Off and then On.
-restarting/power cycling a base unit.
-connecting my Mac laptop (wired) into the same VLAN as the base units - Mac sends mDNS discovery, the replies are all picked up by the APs and we're good again.
The way I understand Airgroup to work is that it's pretty passive in the whole process; it basically just relays the multicast discover/advertisement messages between the VLANs, like a Bonjour gateway (ie. Avahi) would. So what's happening that the services would disappear? All power management features are turned off on the base units.
I'm not familiar enough with mDNS records aging, and how they are renewed. Should these devices not advertise their services again once mDNS cache record times out? I've packet captured the wireless client side and I see the mDNS service discovery messages when the client connects, but I don't see replies coming back from the AP. None of the documentation I've scoured mentions any specific role settings to allow this type of traffic. It all looks pretty straightforward.
Any suggestions? Happy to provide more info if needed.
Tim