Study guide
12.5 Troubleshooting Wireless Clients and Network Access
HPE Aruba Networking Certified Associate - Campus Access HPE6-A85
Track your progress as you read
Finished sections get a check mark.
1 Introduction: HPE6-A85 Exam Overview
HPE6-A85 Exam Facts and Current Blueprint
2 Chapter 1: Network Stack Fundamentals
1.1 OSI Reference Model and Encapsulation 1.2 TCP/IP Protocol Suite and IP Headers 1.3 Layer 2 Operation, ARP, and 802.1Q Tagging
3 Chapter 2: Physical Connectivity and Host Addressing
2.1 Ethernet Media and Transceiver Standards 2.2 Power over Ethernet (PoE, PoE+, PoE++) Standards and Budgeting 2.3 LLDP, LLDP-MED, and Voice VLAN Configuration 2.4 Host IP Addressing and DHCP Relay Operations
4 Chapter 3: Network Resiliency and Virtualization
3.1 Virtual Switching Framework (VSF) Architecture and Topologies 3.2 VSF Split Detection, Failover, and Auto-Stacking 3.3 Virtual Switching Extension (VSX) Architecture and Operations 3.4 High-Availability Gateways: VRRP and VSX Active-Gateway
5 Chapter 4: AOS-CX Architecture and Switch Operation
4.1 AOS-CX Hardware Portfolio and State Database Architecture 4.2 Network Analytics Engine (NAE) and Automated Telemetry 4.3 AOS-CX Interface Configuration and Port Control 4.4 Link Aggregation (LAG) and LACP Configuration
6 Chapter 5: Layer 2 Protocols and Spanning Tree
5.1 AOS-CX VLAN Configuration and Native VLAN Handling 5.2 Spanning Tree Protocols: STP, RSTP, and MSTP 5.3 Spanning Tree Protections and Loop Prevention 5.4 MAC Address Table Learning, Aging, and Forwarding
7 Chapter 6: Wireless Fundamentals, Standards, and RF
6.1 IEEE 802.11 Standards and Wi-Fi Generations 6.2 RF Fundamentals, Signal Propagation, and Channel Design 6.3 Aruba Access Point Hardware Portfolio and Suffix Conventions 6.4 WLAN Topologies, BSSID/ESSID, and Roaming Standards
8 Chapter 7: Aruba Wireless Architecture and Management
7.1 AOS 10 Architecture and Aruba Central Integration 7.2 Wireless Forwarding Modes: Bridge vs Tunnel Mode 7.3 Automated RF and Client Optimization: AirMatch and ClientMatch 7.4 Secure Wireless Access: WPA3, SAE, and MPSK Implementation
9 Chapter 8: IP Routing Fundamentals and OSPF
8.1 IP Routing Principles and Packet Forwarding 8.2 OSPFv2 Protocol Mechanics and Adjacency Formation 8.3 OSPF Designated Routers and Multi-Area Deployments 8.4 ECMP, Static Routing, and VRF Isolation
10 Chapter 9: Campus Network Security and Segmentation
9.1 DHCP Snooping and Dynamic ARP Inspection 9.2 Port Security and MAC Address Limiting 9.3 ClearPass Policy Management and RADIUS Change of Authorization 9.4 Dynamic Segmentation, User-Based Tunneling, and Policy Enforcement
11 Chapter 10: Authentication, Authorization, and Accounting
10.1 The AAA Framework and Architecture 10.2 802.1X Authentication and EAP Methods 10.3 MAC Authentication and Captive Portal Onboarding 10.4 Administrative Access Control: RADIUS vs TACACS+
12 Chapter 11: Network Management and Telemetry
11.1 Aruba Central Cloud Architecture and Group Configuration 11.2 Zero-Touch Provisioning (ZTP) and Aruba Activate 11.3 AI Insights and Aruba User Experience Insight (UXI) 11.4 Network Telemetry, Streaming APIs, and SNMP/Syslog
13 Chapter 12: Troubleshooting the Solution
12.1 Structured Troubleshooting Methodologies and Scope Isolation 12.2 AOS-CX Layer 2 and Interface Diagnostic Commands 12.3 Layer 3, IP Services, and End-to-End Diagnostics 12.4 Physical-Layer Troubleshooting 12.5 Troubleshooting Wireless Clients and Network Access
14 Chapter 13: Optimizing Performance: QoS, Baselines, and Comparisons
13.1 Quality of Service (QoS) Classification and Marking 13.2 Queuing Algorithms and Congestion Management 13.3 Traffic Policing, Shaping, and Broadcast Rate Limiting 13.4 Establishing a Performance Baseline 13.5 Comparing Results to the Baseline
15 Chapter 14: Plan the Solution
14.1 Analyzing the Current Environment 14.2 Interpreting an Architect's High-Level Design 14.3 Creating a Low-Level Design 14.4 Preparing for Implementation
16 Chapter 15: Validate and Operate the Solution
15.1 Validating the Solution 15.2 Performing Firmware Updates 15.3 Making Basic Ongoing Configuration Changes 15.4 Maintaining Network Documentation
12.5 Troubleshooting Wireless Clients and Network Access
Key Takeaways Explain This Topic AI
Client problems are isolated by following the connection journey: association, authentication, IP addressing, DNS, and application, then roaming.
On AOS-CX ports, show port-access clients detail and show aaa authentication port-access interface <port> client-status show each client's method, status, and role, and show radius-server confirms RADIUS reachability.
An Access-Reject from ClearPass applies the reject role, an unreachable RADIUS server applies the critical role, and a client over the client limit is never onboarded.
Bridged SSIDs fail when the client VLAN is missing on the AP's switch port or trunks; tunneled SSIDs depend on the gateway cluster and its VLANs instead.
Roaming problems in AOS 10 involve 802.11r/OKC settings and the Key Management Service; Central client views, events, and UXI results show where the journey breaks.
Last updated: October 2026
12.5 Troubleshooting Wireless Clients and Network Access
Quick Summary: "Wi-Fi is down" and "my port doesn't work" are symptoms, not diagnoses. The fastest way to the cause is to follow the connection journey : did the client associate (wireless) or link up (wired), did it authenticate , did it get the right IP address , does DNS work, and does the application work? The first failed step tells you which layer and which system to investigate: the RF, the switch port, the RADIUS server, DHCP, DNS, or the application.
The Connection Journey
Loading diagram...
Failed step Likely causes Where to look
1. Association SSID not offered in that band, client lacks WPA3/6 GHz support, weak signal, AP down Central AP and SSID status; client capabilities; signal strength
2. Authentication Wrong credentials, untrusted server certificate, expired account, RADIUS shared-secret mismatch, switch or gateway not defined as a RADIUS client, RADIUS unreachable ClearPass Access Tracker; show port-access clients detail ; show radius-server
3. Role / VLAN Role name returned by ClearPass not defined locally, VLAN missing on the switch or trunk, wrong gateway cluster VLAN show port-access role ; show vlan ; Central client details
4. DHCP Missing helper on the gateway SVI, exhausted scope, DHCP snooping dropping offers on an untrusted uplink show ip helper-address ; show dhcp-relay ; show dhcp-snooping statistics
- 5. DNS Wrong DNS servers, firewall blocking UDP 53 Ping by IP versus by name (Section 12.3)
- 6. Application Server, firewall, or ACL problem Traceroute, ACL counters, application owners
7. Roaming Fast roaming not enabled, client lacks 802.11r support, sticky clients Central events, ClientMatch steer events, roaming settings
Wired Authentication on AOS-CX
- Command What it tells you
- show port-access clients Each client's MAC address, port, authentication method, status, and role
- show port-access clients detail Detailed per-client information, including the applied role and VLAN
show aaa authentication port-access interface 1/1/14 client-status The authentication state of every client on one port
- show radius-server Configured RADIUS servers and their reachability
- show radius dyn-authorization CoA and Disconnect counters, to confirm role changes from ClearPass arrive
- show port-access role Locally defined roles, to confirm the role name ClearPass returns exists
How the special roles help you read the situation (AOS-CX Security Guide):
Reject role applied: ClearPass is reachable and returned an Access-Reject. Check the reason in ClearPass (wrong password, expired certificate, policy mismatch).
Critical role applied: the RADIUS server was unreachable or timed out. Check routing to the server, the shared secret, and whether the switch is defined as a RADIUS client.
Pre-auth role during onboarding: with concurrent onboarding, the client waits in the pre-auth role until a method succeeds or all fail.
Second device never onboards: the port's client limit ( aaa authentication port-access client-limit , default 1) may be lower than the number of devices, such as a phone plus a PC.
Remember the quiet period: after failed attempts, AOS-CX waits 60 seconds by default before processing that client again, so retries right after a fix may appear to fail.
- Wireless-Specific Checks
- Bridged versus tunneled SSIDs
Bridged: the client's VLAN must be tagged on the AP's switch port and every trunk to its gateway. A missing VLAN gives a client that authenticates but never gets an address.
Tunneled: client VLANs live on the gateway cluster. Check that the cluster is up and that the user VLAN exists there; the access switch only needs the AP management VLAN (Section 7.2).
Security mismatches
A 6 GHz SSID requires WPA3 or Enhanced Open (OWE); clients that support only WPA2 will not join it.
WPA3 requires Protected Management Frames; older clients without PMF support cannot join a WPA3-only SSID.
MPSK Local supports WPA2-PSK-AES and up to 24 passphrases per SSID; a device using the wrong passphrase simply fails the four-way handshake.
Roaming
In AOS 10, fast roaming relies on 802.11r or OKC plus the Key Management Service in Central distributing keys to AirMatch neighbor APs. AP CLI show ap pmkcache shows the cached keys on an AP (AOS 10 TechDocs).
If Central is unreachable, existing clients can still fast-roam to neighbors that already have their keys, but new clients perform full authentication when roaming.
Sticky clients and band problems are ClientMatch's job; Central's ClientMatch steer events show whether steering is happening.
Central and UXI
Central's client view shows each client's status, SSID, band, role, VLAN, and recent events, which usually reveals the failing step immediately.
AI Insights may already have flagged the pattern, for example a spike in 802.1X failures or slow DHCP.
UXI sensors report which journey step failed (Wi-Fi, authentication, DHCP, DNS, or application), separating network faults from service faults (Section 11.3).
A Worked Example
Symptom: New laptops on floor 3 connect to the bridged SSID LAB but show a 169.254.x.x address.
Association and authentication succeed (Central shows the client authenticated with role LAB_USER).
The role assigns VLAN 40. The client gets no DHCP address, so step 4 fails.
Because the SSID is bridged, check VLAN 40 on the AP's switch port and uplinks: show vlan port 1/1/41 shows that VLAN 40 is not tagged on the AP port.
Fix: add VLAN 40 to the AP port trunk, verify with a test client, and update the port map.
Common Exam Traps
Blaming RF for authentication failures. Strong signal with EAP timeouts points to RADIUS, certificates, or the network path to the server.
Confusing reject and critical roles. Reject means the server answered "no"; critical means the server did not answer.
Forgetting that bridged SSIDs need switch VLANs. Tunneled SSIDs do not; bridged SSIDs do.