Wireless Access

I use a program named Airserver on our computers, to emulate both chromecast and appleTV. My devices kan se the programs broadcast in the network, but cant connect to it. I dont understand why this problem is there.

Our setup:

On our MobilityMaster OS8.4.0.2, with a cluster of 72XX controllers, we have enabled Airgroup in centralized mode. Its enabled for the cluster, and not for the node "managed network".

I am running an airgroup profile, using the following services:

default-airplay

default-airprint

default-googlecast

default-dial

In the CLI, i run the #show airgroup blocked-queries, to see what gets blocked. Here i see alot of lines with _googlecast._tcp, and some lines Apple in the text. Why are these blocked, when i use the above named services?

(7205-190) #show airgroup blocked-queries

AirGroup dropped Query IDs
--------------------------
Service ID #query-hits Thread Num
---------- ----------- ----------
_674A0243._sub._googlecast._tcp 30 1
_companion-link._tcp 1235 1
_homekit._tcp 959 1
_\0379E5E7C8F47989526C9BCD95D24084F6F0B27C5ED._sub._googlecast._tcp 111 1
_8E6C866D._sub._googlecast._tcp 30 1
_00000000-3253-657e-91a3-fb6414664c72._sub._home-sharing._tcp 42 1
_airport._tcp 1 1
_sleep-proxy._udp 1622 1
_googlecast._tcp 114 1
_233637DE._sub._googlecast._tcp 58 1
_dcimprovsrv._tcp 4 1
_674A0243._sub._googlecast._tcp 39 2
_companion-link._tcp 1667 2
_fb._tcp 14 2
_homekit._tcp 1252 2
_\0379E5E7C8F47989526C9BCD95D24084F6F0B27C5ED._sub._googlecast._tcp 154 2
_8E6C866D._sub._googlecast._tcp 39 2
_69844D9A._sub._googlecast._tcp 90 2
_atc._tcp 3 2
_airport._tcp 1 2
_sleep-proxy._udp 2175 2
_hap._tcp 21 2
_googlecast._tcp 250 2
_hearing._tcp 84 2
_dcimprovsrv._tcp 2 2
_companion-link._tcp 1562 3
_spotify-connect._tcp 21 3
_homekit._tcp 1137 3
_\0379E5E7C8F47989526C9BCD95D24084F6F0B27C5ED._sub._googlecast._tcp 87 3
_atc._tcp 6 3
_sleep-proxy._udp 2146 3
_hap._tcp 31 3

AirGroup dropped Query IDs
--------------------------
Service ID #query-hits Thread Num
---------- ----------- ----------
_googlecast._tcp 93 3
_00000003-d794-eff0-e5b0-995f240246df._sub._home-sharing._tcp 1 3
_CC32E753._sub._googlecast._tcp 6 3
_dcimprovsrv._tcp 1 3
_674A0243._sub._googlecast._tcp 12 4
_companion-link._tcp 1631 4
_spotify-connect._tcp 29 4
_fb._tcp 52 4
_homekit._tcp 1235 4
_\0379E5E7C8F47989526C9BCD95D24084F6F0B27C5ED._sub._googlecast._tcp 42 4
_8E6C866D._sub._googlecast._tcp 12 4
_37F83649._sub._googlecast._tcp 3 4
_69844D9A._sub._googlecast._tcp 114 4
_sleep-proxy._udp 2171 4
_googlecast._tcp 168 4
_dcimprovsrv._tcp 3 4
_674A0243._sub._googlecast._tcp 34 5
_companion-link._tcp 1627 5
_CC1AD845._sub._googlecast._tcp 19 5
_fb._tcp 33 5
_homekit._tcp 1107 5
_805741C9._sub._googlecast._tcp 6 5
_\0379E5E7C8F47989526C9BCD95D24084F6F0B27C5ED._sub._googlecast._tcp 47 5
_00000002-782d-05b2-7067-0e582a044c2a._sub._home-sharing._tcp 207 5
_8E6C866D._sub._googlecast._tcp 34 5
_apple-mobdev._tcp 1 5
_atc._tcp 6 5
47a60559._sub._apple-mobdev2._tcp 1 5
_sleep-proxy._udp 2041 5
_D3112633._sub._googlecast._tcp 19 5
_hap._tcp 13 5
_googlecast._tcp 85 5

AirGroup dropped Query IDs
--------------------------
Service ID #query-hits Thread Num
---------- ----------- ----------
_dcimprovsrv._tcp 1 5
Num dropped Query IDs:65

You need to enable airgroup at the node hierarchy of your cluster/controllers. You've probably found documentation that suggests you enable it at the managed network level... .This is outdated and does not apply to 8.4

Depending on the size of the network, you might want to enforce registration, and then use airgroup policies to manually add each airserver MAC address and define which APs or AP groups you users need to be on to discover the server.

If you specify an airgroup server is available on a specific AP note that by default there's a "neighborhood" of one hop, so you can discover the server from further away than you might expect.

Tnx for you answer.

Just to be shure, to understand it right. Right now i have activatet it at number 2 on the photo. And you state, that it has to be activated at number 1. Is that correct?

Yes, that's correct. 

After activating Airgroup as adviced, the problem is til there.

Via SSH to my MM IP, i wrote this command in CLI.

----------------------

(udcarubamm) [mynode] #show airgroup status

AirGroup not activated at this node

----------------------

Why is the MM saying,´the Airgroup is not activated?

When i do this CLI command, on same SHH connection. It tell me, that allot has been blocked.

------------------------------------------------------------------------

(udcarubamm) [mynode] #show airgroup blocked-queries

Text from this command, can be seen on this link, hense it is to long to be put in this textbox.

https://docs.google.com/document/d/1893ozyCcYEKPuTghSKDILFvqyN2RiT3iWpASUxqQSCc/edit?usp=sharing

Hope you can help. Tnx ind advanced.

That's the wrong node hierarchy again. Airgroup is never active on the Mobility Master mynode.

You should have enabled airgroup at the node hierarchy of your managed devices/cluster.

cd /md/<wherever your MDs are>

then try the same command.

@ MatthewSeymour,

I may have the wrong terminology as well, so I'm just looking to clarify.

I'm having massive AirGroup issues and I'm looking for a fix.

So you enable AirGroup at the actual Managed Device level or the MD level? At 1, 2, or 3 in my picture attached?

I'm doing Centralized AirGroup.

It used to work great, but now its very inconsistent.

You should activate airgroups at level 2