Study guide
14.1 Analyzing the Current Environment
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
14.1 Analyzing the Current Environment
Key Takeaways Explain This Topic AI
Analyzing the current environment means documenting what exists today (cabling, closets, power, switches, APs, VLANs, IP services, AAA, and management tools) before anything new is installed.
AOS-CX commands such as show system , show images , show interface brief , show lldp neighbor-info , show power-over-ethernet , and show vlan turn an existing switch into a self-documenting inventory source.
PoE planning compares the worst-case class power of every powered device with the switch PoE budget; for example 20 Class 4 APs at 30 W each already need 600 W at the PSE.
Copper cabling grade limits multi-gigabit speeds: Cat5e supports 2.5GBASE-T and Cat6 supports 5GBASE-T to 100 m, while 10GBASE-T at 100 m needs Cat6A.
Cloud management readiness requires DHCP, DNS, NTP, and outbound HTTPS from management networks before APs and switches can reach Activate and Central.
Last updated: October 2026
14.1 Analyzing the Current Environment
Quick Summary: The first Plan objective on HPE6-A85 is to analyze the current environment . Before anyone configures a switch or mounts an AP, someone has to document what is already there: the cabling and closets, the existing switches and their firmware, VLANs and subnets, PoE demand, the RF environment, the clients, and the services (DHCP, DNS, NTP, RADIUS, firewall rules) the new solution will depend on. Most failed deployments trace back to an assumption nobody checked at this stage.
Why This Step Matters
An architect's design assumes certain facts: that the closet has enough power, that the cabling supports the planned speeds, that DHCP can serve the new subnets, or that the firewall allows the new APs to reach the cloud. The person doing the site work is often the first to discover that one of these assumptions is false. Catching it during analysis costs a conversation; catching it during the cutover costs an outage.
At associate level you are not expected to make design decisions, but you are expected to collect accurate facts, flag gaps, and hand them to the architect .
- What to Collect
- 1. Physical Plant
Wiring closets: rack space, power circuits, UPS capacity and runtime, cooling, and grounding.
Copper cabling: category and installed length of each horizontal run. The ANSI/TIA channel limit is 100 m. Cat5e supports 2.5GBASE-T and Cat6 supports 5GBASE-T to 100 m (IEEE 802.3bz); 10GBASE-T at 100 m needs Cat6A.
Fiber between closets and buildings: multimode grade (OM3/OM4) or single-mode, strand counts, and lengths, because they decide which optics will work (Section 2.1).
Labeling quality: if patch panels and cables are not labeled, the implementation will be slow and error-prone.
2. Existing Wired Network
Inventory: switch models, serial numbers, and firmware. On AOS-CX, show system and show version give the platform and software, and show images lists the primary and secondary images.
Topology: show lldp neighbor-info shows which device is connected to which port, the quickest way to rebuild a missing diagram.
Port utilization: show interface brief shows which ports are up, their speed, and their mode. Count free ports and ports that will need multi-gigabit speeds.
VLANs and Layer 2: show vlan , show spanning-tree , and show lag capture VLAN IDs, the current root bridge, and existing link aggregation.
Layer 3: show ip interface and show ip route show where default gateways and routing live today.
PoE: show power-over-ethernet shows the available, allocated, and drawn power per switch.
3. Wireless Environment
Existing APs: models, mounting locations, current operating system (AOS 8 controller-based, Instant, or AOS 10), and SSIDs.
RF conditions: coverage problems, interference sources, and DFS (radar) events in 5 GHz. A site survey confirms what the RF environment really looks like: a predictive survey models it from floor plans and wall types; a passive survey listens to existing signals; an active survey connects a test client and measures throughput.
Client mix: how many clients per area, which support 5 GHz and 6 GHz, and which need special handling (voice handsets, scanners, medical devices, headless IoT).
4. Clients and Endpoints
Desktop PCs and laptops that can run 802.1X.
IP phones that need a voice VLAN and PoE.
Headless devices (printers, cameras, sensors) that will need MAC authentication or MPSK.
Devices with unusual power needs, such as PTZ cameras or tri-radio APs that need 802.3bt.
5. Supporting Services
DHCP scopes and relay ( ip helper-address ) for every VLAN that will exist.
DNS and NTP : cloud-managed devices validate TLS certificates, so a wrong clock or blocked NTP breaks onboarding (Section 11.2).
Internet access from management networks: outbound HTTPS (TCP 443) to Activate and Central.
AAA: RADIUS servers (for example ClearPass), the network device entries they will need, and existing role names.
Firewall rules between management, user, and server networks.
A PoE Budget Example
A closet will receive 20 APs that request Class 4 , 30 IP phones at Class 2 , and 6 fixed cameras at Class 3 . Using the PSE-side class maximums (Section 2.2):
- Device Count Class power at the PSE Worst case
- Access points 20 30 W 600 W
- IP phones 30 7 W 210 W
- Cameras 6 15.4 W 92.4 W
- Total 902.4 W
If the planned switch provides a 740 W PoE budget, the closet is oversubscribed in the worst case. Options include adding a second PoE switch or VSF member, using a model or power supply with a larger budget, or relying on AOS-CX allocate-by usage with PoE priorities so that critical devices keep power. That choice belongs to the designer, but the analyst must bring the numbers.
Recording the Findings
Turn the raw data into a current-state report :
A topology diagram rebuilt from LLDP data.
An inventory table (device, model, serial, firmware, location).
A cabling and power summary per closet.
A VLAN, subnet, and service table.
A gap list : anything that blocks or changes the planned design, such as Cat5e runs where 5 Gbps uplinks are planned, a UPS that cannot carry the new PoE load, or a firewall that blocks outbound HTTPS.
If the environment is already managed by Central, its device inventory, topology view, and reports provide much of this information directly.
Common Exam Traps
Skipping services. A perfect switch configuration still fails if DHCP has no scope for the new VLAN or NTP is unreachable.
Planning speeds from cable category alone. Length and installation quality matter; confirm with certification test results where possible.
Using drawn power instead of class power for worst-case planning. Actual draw is useful for operations, but planning should account for what devices may request.