Study guide

15.2 Performing Firmware Updates

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

15.2 Performing Firmware Updates

Key Takeaways Explain This Topic AI

AOS-CX switches keep primary and secondary images; copy <url> primary|secondary loads an image, show images lists versions, and boot system primary|secondary reboots into the chosen image.

VSX pairs can be upgraded with vsx update-software <tftp-url> , which installs the image on both peers and reboots the secondary first, then the primary, so VSX-LAG clients stay connected.

CX 6300 VSF stacks support VSF ISSU ( issu update-software ) for upgrades between minor releases, keeping the data plane forwarding while the control plane upgrades.

In Central, firmware compliance sets the target version for a group; AOS 10 Live Upgrade reboots APs in AirMatch partitions so neighbors stay up, and reloads gateway cluster members one at a time.

Always read the release notes for the supported upgrade path, back up the configuration, and schedule the upgrade in a maintenance window with a rollback plan.

Last updated: October 2026

15.2 Performing Firmware Updates

Quick Summary: Firmware updates are an Operate objective on HPE6-A85. The skills tested are practical: know where AOS-CX keeps its images, how to load and boot a new one, which method keeps traffic flowing for a VSF stack or a VSX pair , and how Central upgrades APs and gateways with firmware compliance and Live Upgrade . Every upgrade starts with the release notes and a backup.

Before Any Upgrade

Read the release notes for the target version: supported upgrade paths, known issues, and changed defaults.

Back up the configuration ( copy running-config <url> cli vrf mgmt ) and create a checkpoint (Section 14.4).

Check the current state so you can compare after the upgrade: show images , show version , show vsf or show vsx status , and key neighbor states.

Schedule a window and tell users; even "hitless" methods can cause brief disruptions.

Plan the rollback: on AOS-CX, the previous image normally stays on the other image slot.

AOS-CX Dual Images

AOS-CX switches store two operating system images, primary and secondary , plus a service OS used for recovery (AOS-CX 10.14 Fundamentals Guide).

  • Task Command
  • List installed images and the default boot image show images

Download an image into a slot copy tftp://10.1.100.20/FL.10.xx.xxxx.swi secondary vrf mgmt (SFTP and SCP URLs are also supported)

  • Copy one slot to the other copy primary secondary or copy secondary primary
  • Reboot into a slot and make it the default boot system secondary
  • Change the default without rebooting boot set-default primary
  • Review previous boots show boot-history

A common pattern is to load the new image into the slot that is not currently running, boot into it, and keep the old image in the other slot as a fallback. If the new version misbehaves, boot system back into the previous slot.

AOS-CX also supports hot patches ( copy <url> hot-patch and the hot-patch command) for some fixes that can be applied without a full image change; whether a hot patch exists depends on the release.

  • Upgrading Redundant Systems
  • VSX pairs

vsx update-software tftp://<server>/<image> vrf mgmt (run on the primary) offers to save the running configuration, downloads the image, installs it to the alternate image of both peers, and then reboots them in sequence: the secondary first, then the primary (AOS-CX 10.14 CLI Guide). Devices dual-homed with VSX-LAGs and gateways using active-gateway keep working on whichever peer is up. Single-homed (orphan) devices lose connectivity while their peer reboots, which is one reason to dual-home important devices.

VSF stacks

A standard upgrade reboots the whole stack. On the CX 6300 , VSF ISSU ( issu update-software ) upgrades the Conductor, Standby, and members while keeping the data plane forwarding, and it is supported for upgrades between minor releases (AOS-CX 10.14 VSF Guide). For a major-release jump, plan a full stack reload in a window.

Standalone switches

Load the new image into the alternate slot and boot system into it during the window. Access-layer devices behind a standalone switch lose connectivity during the reboot, and PoE devices lose power unless always-on PoE keeps them powered during a soft reboot.

Central Firmware Management

In Central, the Firmware area shows the running version of each device and lets you set firmware compliance for a group: the target version, the upgrade type, and when to run it (immediately or scheduled up to one month ahead).

AOS 10 Live Upgrade for APs

HPE's Live Upgrade service (AOS 10 TechDocs, "Live upgrade"):

Asks AirMatch to split the APs into partitions so that APs in the same partition are not RF neighbors. While one partition reboots, clients can roam to neighbors that stay up.

Selects seed APs : only seed APs download the image from Activate, and each serves up to 20 non-seed APs of the same model in the same Layer 2 domain, which saves WAN bandwidth.

Reboots one partition at a time. Before rebooting, an AP disables its radios so clients roam to neighbors, which then synchronize the clients' sessions.

The default upgrade type in Central is Standard , in which all devices in the group download the image and reboot at the same time . Choose Live Upgrade when disruption must be minimized.

Gateway clusters

All gateways in a cluster download the image together but reload one at a time . Users on the reloading gateway move to their standby User Designated Gateway, and a gateway on the new version can rejoin a cluster still running the older version, so users are not disrupted.

AOS-CX switches managed by Central

Central can push AOS-CX upgrades as well. HPE's Central caveats note that upgrading an AOS-CX switch from Central needs a WAN connection of at least 2 Mbps and times out after 60 minutes.

After the Upgrade

Confirm the version: show version and show images , or the firmware view in Central.

Re-run the key validation checks (Section 15.1): VSF or VSX health, LAGs, routing neighbors, clients, and PoE.

Compare against the pre-upgrade state and record the result in the change log (Section 15.4).

Common Exam Traps

Upgrading both VSX peers at once by hand. The supported workflow reboots the secondary first, then the primary.

Assuming VSF ISSU works for every upgrade. It applies to the CX 6300 and to upgrades between minor releases.

Leaving Central compliance on when upgrading manually. If a group has a firmware compliance version set, Central will bring devices back to that version. Set compliance to "None" (Not Set) if you deliberately load firmware from your own server.