Product and Software: This article applies to all Aruba controllers and ArubaOS versions.
The first step to troubleshoot client device issues in a wireless network is to have a clear understanding of the issue being reported so that the next steps can be efficiently chosen.
This table lists several symptoms and possible causes to help you scope the problem.
Symptom
Possible Cause
Issue is isolated to an individual.
Might be a NIC-, supplicant-, or driver-related issue.
Issue is isolated to a geographical area.
Might be a RF or other physical layer problem.
Issue affects a group of people on a certain SSID.
Might be an access point (AP) configuration problem.
Issue affects a group of people on a common group of APs.
Might be an AP configuration or a Layer 2 or Layer 3 problem.
Issue is isolated to a certain application.
Might be a routing problem or an application layer problem.
Issue is isolated to a particular server.
Might be a routing or server problem.
Issue is isolated to a particular time of day.
Might be a non-802.11 device, firewall, or service issue.
Other things to check:
This flow chart shows you where to start troubleshooting when a problem is reported for a mobile device.
For more information, see the "Troubleshooting for Roaming Devices" chapter in the Virtual Optimizing Aruba WLANs for Roaming Devices document.
© Copyright 2024 Hewlett Packard Enterprise Development LPAll Rights Reserved.