Troubleshooting AirGroup

This topic describes the procedures to troubleshoot AirGroup.

Check AirGroup Status

To check the status of AirGroup, complete the following steps:

1. In the WebUI, set the filter to Global.
2. Under Analyze, click Tools.
3. Click Commands.
4. Use the Commands filter to select the show airgroup status command.
5. Click Add.
6. Click Run.
7. Analyze the output of the command.

The following sample highlights words or lines of relevance:

Check AirGroup Service

To check the status of AirGroup services, complete the following steps:

1. In the WebUI, set the filter to Global.
2. Under Analyze, click Tools.
3. Click Commands.
4. Use the Commands filter to select the show airgroup service command.
5. Click Add.
6. Click Run.

Check Cloud Configuration Received on AP

To check the cloud configuration received on an AP, complete the following steps:

1. In the WebUI, set the filter to Global.
2. Under Analyze, click Tools.
3. Click Commands.
4. Use the Commands filter to select the show ap debug cloud-config-received command.
5. Click Add.
6. Click Run.

Check AirGroup Discover Cache Entries

To check the Air Pass discover cache entries, complete the following steps:

1. In the WebUI, set the filter to Global.
2. Under Analyze, click Tools.
3. Click Commands.
4. Use the Commands filter to select the show airgroup discover-cache entries command.
5. Click Add.
6. Click Run.

Check AirGroup Central Cache Entries

To check the AirGroup Central cache entries, complete the following steps:

1. In the WebUI, set the filter to Global.
2. Under Analyze, click Tools.
3. Click Commands.
4. Use the Commands filter to select the show airgroup central cache-entries command.
5. Click Add.
6. Click Run.

Check AirGroup Debug Log

To check the AirGroup debug log, complete the following steps:

1. In the WebUI, set the filter to Global.
2. Under Analyze, click Tools.
3. Click Commands.
4. Use the Commands filter to select the show airgroup debug-log command.
5. Click Add.
6. Click Run.

Check AirGroup Debug Statistics

The AirGroup debug statistics counters record the number of forwarded or dropped mDNS Multicast Domain Name System. mDNS provides the ability to perform DNS-like operations on the local link in the absence of any conventional unicast DNS server. The mDNS protocol uses IP multicast User Datagram Protocol (UDP) packets, and is implemented by the Apple Bonjour and Linux NSS-mDNS services. mDNS works in conjunction with DNS Service Discovery (DNS-SD), a companion zero-configuration technique specified. See RFC 6763. or SSDP packets. Response and query packets are maintained separately. The counters for the packet filtering statistics are:

• mdns_query_pkt_dropped_count
• ssdp_query_pkt_dropped_count
• mdns_query_pkt_forwarded_count
• ssdp_query_pkt_forwarded_count
• mdns_response_pkt_forwarded_count
• ssdp_response_pkt_forwarded_count
• mdns_papi_send_to_ofa_failure

To check the AirGroup debug statistics, complete the following steps:

1. In the WebUI, set the filter to a group that has HPE Aruba Networking APs running AOS-10.
2. Under Analyze, click Tools.
3. Click the Commands.
4. Use Commands filter to select the show airgroup debug statistics command.
5. Click Add.
6. Click Run.
7. Analyze the output of the command.
   The following sample highlights words or lines of relevance:

   (host) #show airgroup debug statistics

   My ip address :x.x.x.x

   AirGroup Debug Statistics

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

   Key Value

   --- -----

   network cache init counter 1(0)

   mdns apdb init counter 1(0)

   airgroup restore count 1(0)

   unsupported mdns query pkt dropped count 169(159)

   unsupported ssdp query pkt dropped count 178(124)

   supported mdns query pkt forwarded count 379(239)

   supported ssdp query pkt forwarded count 270(178)

   mdns response pkt forwarded count 635(371)

   ssdp response/notify pkt forwarded count 94(40)

   dropped as init not done rx 13(0)

   mdns recieved bonjour pkt from device 1183(769)

   mdns recieved dlna pkt from device 542(342)

Check mDNS Trace Logs

Use the mDNS trace logs to:

• Analyze the packet type or content and how mDNS processes it in the AP.
• See if the packet is forwarded to Classic Central based on the allowed service filtering.

To enable the mDNS trace logs, complete the following steps:

1. In the WebUI, set the filter to a group that has HPE Aruba Networking APs running AOS-10.
2. Under Analyze, click Tools.
3. Click Commands.
4. Use the Commands filter to select the trace component mdns sub-component all command.
5. Click Add.
6. Click Run.

Capture mDNS Packets

To capture the mDNS query and response packets to and from the AP, use the following commands:

Capture SSDP Packets

To capture the SSDP query and response packets to and from the AP, use the following commands:

Check Audit Trail

To check the audit trail, complete the following steps:

1. In the WebUI, set the filter to Global.
2. Under Analyze, click Audit Trail.

Check Server Visibility for Client

To check which servers are available for the client to connect, complete the following steps:

1. In the WebUI, set the filter to a group that has HPE Aruba Networking APs running AOS-10.
2. Under Manage, click Applications > AirGroup.
3. Click List.
4. In the Summary Bar, click Clients.
5. Click the MAC Media Access Control. A MAC address is a unique identifier assigned to network interfaces for communications on a network. address corresponding to the client for which you want to check the available servers.

Figure 1  Available Servers for the Client