What is the concept of Airgroup? How does it work and what are the basic troubleshooting commands that are available?
|Question||What is the concept of Airgroup? How does it work and what are the basic troubleshooting commands that are available?|
|Environment||This article applies to Aruba Mobility Controllers running ArubaOS version 188.8.131.52 with Airgroup enabled.|
How it works:
Once controller receives an mDNS query, controller replies with a unicast response containing relevant mDNS records from its cache table. By default, all AirGroup servers are visible to all AirGroup users.
Basic troubleshooting commands:
Airgroup is enabled by default on controller after upgrading to ArubaOS 184.108.40.206. Below command shows the status of airgroup on the controller:
#show airgroup status
Airgroup feature can be enabled/disabled using the following command in the config mode:
Airgroup service can be enabled/disabled using the following command in the config mode:
(Aruba)(config)#airgroup service <service-name> [enable|disable]
Airgroup is by default disabled for IPv6 clients. It can enabled/disabled with below command in the config mode:
(Aruba)(config)#no airgroup ipv6
Airplay and Airprint services are enabled by default. Status of the airgroup services can be seen using the "show airgroup status" command.
Aigroup, by default is allowed on all vlans. Below command shows if the airgroup is allowed or disallowed on a particular vlan:
AirGroup classifies all mDNS devices as either AirGroup servers or AirGroup users. Devices which advertise at least one Bonjour service are classified as AirGroup Servers whereas devices which do not advertise but query for Bonjour services are classified as AirGroup Users.
List of Airgroup servers that a controller can listen across vlans can be seen using the below command:
#Show airgroup servers
List of Airgroup users that a controller has seen the queries coming from:
#Show airgroup users
List of cache entries on a airgroup controller can be seen from the below command:
#Show airgroup cache entries
Excessive mDNS packets from devices can impact the performance of AirGroup. Throttling mechanism such as "credit values" has been added to rate limit the number of mDNS packets processed by the controller. Controller assigns separate credit values to query and response packets. Credit is decremented by one, when a query or response packet is processed by controller. Controller will drop any query/response packets when the corresponding credit is zero. Credit values are renewed every 15 seconds.
To see the current credit value on a controller user the command "show airgroup global-credits"
On the Airgroup controller, there would be some of the mDNS queries receiving from the users, for which there are no servers offering the service. This list of queries will be displayed under blocked queries.
Below is the command to look at blocked queries:
#Show airgroup blocked-queries
Based on network requirement, some of the aigroup services might be disabled on controller but it might be still receiving queries from users. This count of number of queries is shown using the command "show airgroup blocked-service-id"