Study guide
1.1 OSI Reference Model and Encapsulation
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
1.1 OSI Reference Model and Encapsulation
Key Takeaways Explain This Topic AI
The OSI reference model standardizes enterprise network communication into seven functional layers, enabling modular protocol engineering and multi-vendor interoperability.
Each OSI layer wraps upper-layer data into a distinct Protocol Data Unit (PDU): Data (Layers 7-5), Segment (Layer 4), Packet (Layer 3), Frame (Layer 2), and Bits (Layer 1).
Encapsulation prepends protocol headers as data moves down the stack; Layer 2 uniquely appends both a header containing MAC addresses and a trailer containing the Frame Check Sequence (FCS).
Layer 2 access switches forward frames based on MAC address tables without modifying IP headers, whereas Layer 3 routers decrement the IPv4 Time-to-Live (TTL) and rewrite Layer 2 MAC addresses at each routing hop.
The standard Ethernet Maximum Transmission Unit (MTU) of 1500 bytes dictates a default TCP Maximum Segment Size (MSS) of 1460 bytes after accounting for 20-byte IP and 20-byte TCP headers.
Last updated: October 2026
OSI Reference Model and Encapsulation
Quick Summary: The Open Systems Interconnection (OSI) reference model establishes a seven-layer conceptual framework for network communications. As application data travels down the stack, each layer prepends a protocol header—and at Layer 2, appends an error-checking trailer—in a process known as encapsulation . When frames arrive at their destination, the receiving device performs decapsulation , stripping headers layer by layer. Understanding how intermediate devices like Aruba CX Layer 2 switches and Layer 3 core routers interact with these layers is critical for campus network design and troubleshooting.
The Purpose of Layered Architecture
In modern enterprise campus networking, devices manufactured by different vendors must exchange data reliably. Standardized by the International Organization for Standardization (ISO) under standard ISO/IEC 7498-1, the OSI Reference Model divides network communication into seven modular layers.
Layering delivers three primary engineering advantages:
Interoperability: Hardware and software developers can implement protocols at a specific layer without redesigning the entire protocol stack.
Abstraction: Lower physical media details (fiber vs. copper signaling) remain completely transparent to upper-tier software applications.
Structured Troubleshooting: Network administrators can isolate faults systematically, verifying physical link status before diagnosing Layer 3 routing or Layer 7 authentication issues.
The Seven Layers of the OSI Model
The OSI model organizes network functions from high-level user services down to physical transmission media:
Layer Number Layer Name Primary Function Common Protocols & Standards Campus Role
Layer 7 Application User-facing network interfaces and services HTTP, HTTPS, DNS, DHCP, SSH, NTP User applications and Aruba Central management
Layer 6 Presentation Data formatting, character encoding, encryption TLS/SSL, ASCII, JSON, XML Secure CLI sessions and web portal encryption
Layer 5 Session Dialogue control, session setup, sync, teardown RPC, NetBIOS, SQL sessions Client session persistence to authentication servers
Layer 4 Transport End-to-end transport, port multiplexing, reliability TCP, UDP Differentiating web (443), SSH (22), and RADIUS (1812)
Layer 3 Network Logical addressing, path selection, packet routing IPv4, IPv6, ICMP, OSPF Core and aggregation routing across campus subnets
Layer 2 Data Link Physical addressing, media access, framing, error check Ethernet (802.3), Wi-Fi (802.11), 802.1Q Switch MAC address forwarding and VLAN segmentation
Layer 1 Physical Bit transmission, electrical voltages, optical signals 1000BASE-T, 10GBASE-SR, SFP+, RJ-45 Physical cables, transceivers, and switch ports
Layer 2 Sublayers
In IEEE 802 LAN standards, Layer 2 is divided into two distinct sublayers:
Logical Link Control (LLC - IEEE 802.2): Communicates with the Network Layer above, multiplexes network protocols using EtherType values, and manages flow control.
Media Access Control (MAC - IEEE 802.3 / 802.11): Controls physical media access and appends source and destination physical MAC addresses.
Protocol Data Units (PDUs) and Encapsulation Mechanics
As data passes down the protocol stack on a sending host, each layer wraps the payload inside its own protocol control information. This packaged unit is called a Protocol Data Unit (PDU) :
- Layers 7, 6, 5: Data (Application payload, formatted data, session tokens)
- Layer 4: Segment (TCP) or Datagram (UDP)
- Layer 3: Packet (IP header containing logical source and destination IP addresses)
- Layer 2: Frame (MAC header, payload, and Frame Check Sequence trailer)
- Layer 1: Bits (Binary physical signaling across copper, fiber, or RF)
- Header and Trailer Specifics
While Layers 4 and 3 prepend protocol headers, Layer 2 uniquely adds both a header and a trailer :
Layer 2 Header: Contains the 6-byte Destination MAC address, 6-byte Source MAC address, and a 2-byte EtherType field (identifying the encapsulated Layer 3 protocol, such as 0x0800 for IPv4).
Layer 2 Trailer: Contains the 4-byte Frame Check Sequence (FCS) . The sending host runs a Cyclic Redundancy Check (CRC-32) across the frame contents and writes the resulting checksum into the FCS field. When the receiving device reads the frame, it recalculates the CRC. If the values mismatch, the frame was corrupted in transit and is dropped immediately.
MTU and MSS Relationships
Maximum Transmission Unit (MTU): Defines the largest Layer 3 packet that can be transmitted over a Layer 2 frame without fragmentation. Standard Ethernet specifies an MTU of 1500 bytes (excluding the 14-byte Ethernet header and 4-byte FCS trailer).
Maximum Segment Size (MSS): Defines the maximum application payload a host places inside a single TCP segment. In an IPv4 network with standard 1500-byte MTU: MSS = MTU (1500 bytes) − IPv4 Header (20 bytes) − TCP Header (20 bytes) = 1460 bytes \text{MSS} = \text{MTU (1500 bytes)} - \text{IPv4 Header (20 bytes)} - \text{TCP Header (20 bytes)} = 1460\text{ bytes} MSS = MTU (1500 bytes) − IPv4 Header (20 bytes) − TCP Header (20 bytes) = 1460 bytes
Device Processing Across OSI Layers
Campus network devices operate at different tiers of the OSI model:
Layer 2 Switching (e.g., Aruba CX 6000, 6100, or 6200 ports operating at Layer 2)
Receive bits from the physical medium and reconstruct the Layer 2 frame.
Verify the FCS trailer in hardware; corrupted frames are discarded immediately.
Read the Source MAC address to update the local MAC address table (CAM table).
Inspect the Destination MAC address and VLAN ID to forward the frame out the appropriate switch port.
Key Principle: A Layer 2 switch does not alter the Layer 3 IP header, does not decrement the TTL, and does not modify the Layer 4 transport payload.
Layer 3 Switches and Routers (e.g., Aruba CX 6300, 6400, 8325)
When forwarding packets across different IP subnets (inter-VLAN routing):
De-encapsulate the incoming Layer 2 frame by stripping the Layer 2 header and FCS trailer.
Inspect the Layer 3 IPv4 header destination IP address against the routing table.
Decrement the IPv4 Time-to-Live (TTL) field by 1. If TTL reaches 0, the packet is discarded and an ICMP Time Exceeded message is returned.
Recalculate the Layer 3 IPv4 header checksum (since TTL changed).
Encapsulate the packet inside an entirely new Layer 2 frame :
Source MAC: Becomes the MAC address of the router's egress interface.
Destination MAC: Becomes the MAC address of the next-hop router or destination host.
Compute a new CRC-32 checksum, write it into the new FCS trailer, and transmit the frame.
Structured Layered Troubleshooting Methodology
When troubleshooting connectivity issues on Aruba CX campus networks, engineers apply structured models:
Troubleshooting Approach Starting Point Typical Action on Aruba CX Switches
Bottom-Up Layer 1 Check cable seating, verify SFP link lights, run show interface brief , check optical transceiver power ( show interface transceiver ).
Top-Down Layer 7 Check application services, test DNS name resolution, verify HTTP/HTTPS server daemon responsiveness.
Divide-and-Conquer Layer 3 Issue a ping from the client to its default gateway IP. If ping succeeds, Layers 1-3 function properly; focus on Layer 4 ports or Layer 7 services. If ping fails, isolate down to Layer 2 VLAN tagging or Layer 1 cabling.
Common Exam Traps
PDU Terminology Confusions: The exam tests whether you recognize that "Packets" exist strictly at Layer 3 (Network) and "Frames" exist strictly at Layer 2 (Data Link). Never refer to an IP PDU as a frame.
MAC Preservation Misconception: Believing that Layer 2 MAC addresses remain unchanged as a packet traverses multiple routed hops. Source and destination IP addresses remain constant end-to-end (unless NAT is applied), but MAC addresses are rewritten at every Layer 3 boundary.
L2 Switch Header Manipulation: Assuming that a standard Layer 2 access switch decrements the IPv4 TTL. Standard Layer 2 switching operates strictly at the Data Link layer and leaves the IP TTL field unchanged.