Study guide

12.4 Physical-Layer Troubleshooting

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.4 Physical-Layer Troubleshooting

Key Takeaways Explain This Topic AI

Physical-layer faults show up as links that stay down, flap, run at a lower speed than planned, log CRC/FCS errors, or deliver too little PoE.

diag cable-diagnostic test <port> runs a cable test on supported copper ports (it briefly drops the link) and diag cable-diagnostic show <port> reports each pair's status and approximate distance.

For fiber, show interface dom and show interface <port> transceiver detail compare receive power with alarm and warning thresholds to separate dirty or damaged fiber from configuration faults.

An unsupported transceiver stays disabled unless allow-unsupported-transceiver is configured, and a multimode optic on single-mode fiber (or the reverse) will not link reliably.

PoE problems are checked with show power-over-ethernet <port> : budget exhaustion, low priority during oversubscription, or a class limit can leave a device unpowered or restricted.

Last updated: October 2026

12.4 Physical-Layer Troubleshooting

Quick Summary: Layer 1 is where the bottom-up method starts and where many campus problems end: a damaged patch cord, a cable that is too long for multi-gigabit speed, a dirty fiber connector, the wrong optic, or a switch that has run out of PoE. AOS-CX gives you direct evidence for each of these: interface state and counters, transceiver diagnostics, cable tests, PoE status, and hardware health.

Symptoms That Point to Layer 1

Symptom Likely physical causes

Link never comes up Unplugged or broken cable, wrong port, far-end device off, wrong or unsupported optic, fiber strands swapped

Link flaps up and down Marginal cable or connector, optical power near the receiver threshold, failing NIC or optic

Link up at a lower speed than planned (for example 1 Gbps instead of 2.5 Gbps) Cable category or length not good enough for the multi-gigabit rate, one bad pair, or the far end not capable

CRC/FCS errors increase Damaged copper, interference, dirty or bent fiber, failing transceiver

Late collisions Duplex mismatch from a hard-coded speed on one end (Section 12.2), or an over-length copper run

Device has no power or runs restricted PoE budget exhausted, low PoE priority, class limit, cabling fault, or the PD needs 802.3bt but receives 802.3at

  • Copper Diagnostics
  • Interface state and counters

Start with show interface <port> : admin state, link state, speed and duplex, and the error counters. Clear expectations help: an access port to a Wi-Fi 6E AP planned at 2.5 Gbps that shows 1 Gbps is a Layer 1 finding, even though "the link is up".

Cable test

AOS-CX includes a time-domain reflectometer (TDR) style cable test on supported copper ports (AOS-CX 10.14 CLI Guide): switch# diag cable-diagnostic test 1/1/14

This command will cause a loss of link on the port under test and will take

several seconds to complete.

  • Continue (y/n)? y
  • switch# diag cable-diagnostic show 1/1/14

The result lists each wire pair with its status, impedance, approximate distance, and MDI mode. Use it to find an open or shorted pair or a cable much longer than the 100 m channel limit. Because the test drops the link, run it only when the port can be disrupted. Some ports, such as fiber ports, do not support it.

Speed and duplex

Leave copper ports on auto-negotiation at both ends. If one end is forced (for example speed 100-full ) and the other is on auto, the auto end falls back to half duplex, and late collisions and CRC errors follow.

Fiber and Transceiver Diagnostics

Is the optic recognized? show interface transceiver lists the installed transceivers. AOS-CX does not enable unsupported (non-HPE) optics unless allow-unsupported-transceiver is configured, so an unexpected "unsupported" message explains a dark port.

Is the optic right for the fiber? SR optics need multimode fiber; LR optics need single-mode. Both ends must use compatible types and wavelengths.

Is light arriving? show interface dom or show interface <port> transceiver detail shows transmit and receive power against alarm and warning thresholds. Very low receive power on one end usually means a dirty connector, a bad patch cord, an over-long run, or swapped transmit and receive strands. Receive power that is fine on one end and missing on the other points to a single strand.

Fix and retest: clean both connectors with proper tools, replace the patch cord with a known-good one, and check DOM again.

PoE Diagnostics

show power-over-ethernet shows the switch budget and how much is allocated and drawn; show power-over-ethernet <port> shows a port's status, class, priority, and power. Typical findings:

Budget exhausted: total allocation has reached the available power, so new devices are not powered. Check whether the port uses allocate-by class , which reserves full class power when a device does not negotiate through LLDP (Section 2.2).

Priority: during oversubscription, low-priority ports lose power first, and among equal priorities the higher-numbered ports go first.

Class limit: power-over-ethernet assigned-class may cap the port below what the device needs.

Restricted AP: an AP that needs 802.3bt but receives 802.3at may boot with features disabled (for example its USB port). Check the AP's QuickSpecs power table.

Always-on PoE keeps devices powered through a soft reboot; quick PoE speeds power-up after a cold boot. Neither helps if the budget itself is too small.

Hardware and Environment

show environment reports fans, power supplies, and temperatures; show events shows hardware and link events with timestamps. A failing power supply in a non-redundant switch can shrink the PoE budget and drop low-priority devices.

Isolation Technique: Swap and Compare

Compare the failing port with a working port of the same type: configuration ( show running-config interface <port> ), speed, and counters.

Swap one component at a time: patch cord, then optic, then switch port, then the far-end device. If the problem moves with the component, the component is at fault. If it stays, look at the infrastructure behind it (horizontal cable or far end).

Check both ends: many Layer 1 faults are visible only from the far side, such as missing receive light.

Record what you changed and the result, because the same evidence supports the RMA or cabling repair request.

Wireless Physical Layer

For APs, Layer 1 also includes placement and the RF path: an AP mounted above a metal duct, an external antenna pointed the wrong way, or new construction (glass, concrete, metal shelving) that changed coverage. These show up as poor signal strength and SNR at the client (Section 6.2) rather than switch-side errors.

Common Exam Traps

"The link is up, so Layer 1 is fine." A link at the wrong speed or with climbing CRC errors is still a physical problem.

Running a cable test during production. The test drops the link on the tested port.

Blaming configuration for a dark fiber port. Check that the optic is supported and correct for the fiber, and that light is arriving.