I85PREP
⌘ K
Aruba ACSA study materials
Aruba ACSA study resources

Aruba ACSA: Switching Fundamentals: ArubaOS-CX and ArubaOS-Switch

Aruba ACSA · Work through your exam, one topic at a time.

All guide sections

Switching Fundamentals: ArubaOS-CX and ArubaOS-Switch

What you must understand

Aruba sells two distinct switch operating systems, and questions test whether you know which platform a feature belongs to. ArubaOS-CX is the modern, Linux-based OS (CX 6000/6100/6300/6400/8xxx/9xxx/10000 series) with a configuration database, candidate/running/startup config model, and the Network Analytics Engine (NAE). ArubaOS-Switch is the legacy ProVision/ProCurve lineage (2530, 2930, 3810, 5400, etc.) with a single running config and write memory persistence.

Core concepts: the CLI hierarchy (CX uses config, interface, and explicit no forms; AOS-S uses configure terminal and interface contexts), boot and image management (CX uses boot and image profiles; AOS-S uses primary/secondary flash images), and the difference between the management interface (out-of-band, dedicated VRF in CX) and in-band SVI management.

Traps

  • CX does not auto-save: copy running-config startup-config (or write memory) is required. AOS-S likewise needs write memory. Questions love to ask whether a change survives a reboot.
  • On CX, the management interface is in the mgmt VRF; routes and services bound there behave differently from the default VRF.
  • AOS-S "stacking" is VSF/backplane stacking; CX uses VSF as well, but the command syntax differs - don't mix them.
  • show running-config vs show configuration (CX candidate) confusion.

Rule of thumb

If the question mentions candidate config, NAE, or vsx, it's CX. If it mentions write memory, menu, or ProVision-era model numbers, it's AOS-S. When in doubt, save the config - unsaved changes are the single most common trap.