Aruba CX VLAN Configuration: Access Ports, Trunks and Native VLANs
Build a simple AOS-CX VLAN configuration, understand native and allowed VLANs, and troubleshoot the path from an endpoint to its upstream gateway.
Key Points
- Access ports serve a single endpoint VLAN; trunks carry the selected VLANs between devices.
- Native VLAN and allowed VLAN settings must agree with the neighboring device.
- Creating VLANs does not automatically provide routing or DHCP.
- Use AOS-CX instructions for the exact switch and release, not older ArubaOS-Switch syntax.
On Aruba AOS-CX, assign an endpoint VLAN with vlan access and select uplink VLANs with vlan trunk allowed. The native VLAN controls the treatment of untagged traffic on the trunk. Getting those three choices right is more useful than copying a long switch configuration without checking the upstream device.
This guide uses a small Layer 2 example based on the AOS-CX 10.15 CLI guide for 6000 and 6100 switches. Confirm commands and interface names against your model and installed release. It is not an ArubaOS-Switch or Instant On configuration recipe.
1. Plan the VLAN path before editing ports
Our example uses VLAN 10 for staff, VLAN 20 for guests and VLAN 99 as the uplink's native VLAN. Port 1/1/1 connects an untagged staff endpoint; port 1/1/24 connects a neighboring switch or router. These are sample assignments, not a recommendation to replace your current management VLAN.
| Interface | Role | Expected behavior |
|---|---|---|
| 1/1/1 | Staff endpoint | Untagged endpoint traffic belongs to VLAN 10 |
| 1/1/24 | Uplink | Tagged VLANs 10 and 20; untagged native VLAN 99 |
| Upstream peer | Matching trunk | Same VLAN IDs and native VLAN behavior |
Record how you currently reach the switch. Use a console or another verified recovery path before editing that management path. For centrally managed devices, make the change in the authoritative configuration system so a later synchronization does not overwrite it.
2. Create the VLANs and assign an access port
For a lab switch with the illustrated free ports, the configuration is:
configure terminal
vlan 10
name STAFF
exit
vlan 20
name GUEST
exit
vlan 99
name NATIVE
exit
interface 1/1/1
no shutdown
vlan access 10
exit
This example assumes Layer 2 interfaces. On platforms where the selected interface is routed, the applicable guide may require no routing before VLAN assignment. Do not convert a working routed uplink without redesigning its IP connectivity. An access port is appropriate for our untagged endpoint; an access point carrying multiple locally bridged SSIDs may need a trunk instead.
3. Set the native VLAN, then the allowed list
interface 1/1/24
no shutdown
vlan trunk native 99
vlan trunk allowed 10,20,99
exit
end
HPE documents that setting a native VLAN can automatically apply an all-VLAN allowed list. Therefore, set the native VLAN first and apply your explicit allowed list afterward. Recheck the effective configuration whenever you change the native VLAN later.
The AOS-CX trunk-interface guide explains that untagged ingress traffic is dropped if the native VLAN is absent from the allowed list. Our example includes VLAN 99 deliberately. Configure the neighboring end with equivalent behavior; a matching cable does not imply matching VLAN settings.
4. Verify the path before saving
show vlan
show running-config interface 1/1/1
show running-config interface 1/1/24
show interface brief
Check VLAN existence, port assignments and link status. Then test from the endpoint: obtain the intended address, reach its gateway and exercise an approved application. Repeat from each VLAN that should cross the uplink. A successful switch login alone does not validate the user traffic path.
Once the intended behavior is verified, save the running configuration using the supported command:
copy running-config startup-config
5. Separate VLAN problems from IP-service problems
- No link: check cable, transceiver, peer port and administrative state first.
- Link works but no DHCP lease: trace the endpoint VLAN across both ends of every uplink, then check the DHCP server or relay.
- Only untagged traffic fails: compare the native VLAN and whether it is allowed on both ends.
- Same-VLAN traffic works but another subnet fails: inspect the gateway, routing and policy. VLAN creation alone does not create those services.
- Changes disappear: check saved configuration and the management platform's intended state.
Keep a small test matrix listing source VLAN, destination, expected result and observed result. This makes a partial failure easier to locate than changing several ports at once.
Choose the switch around the complete design
VLAN commands are only one part of a hardware decision. Count endpoint ports, PoE demand, uplink speeds, routing requirements and operational support. Our CX 6100 vs 6200 comparison and CX switch series guide help turn those requirements into a shortlist.
Use the HPE Aruba price list to compare exact switch and accessory part numbers. Include optics, power supplies and any required management subscriptions in the quote; a catalog list price is not a complete installed cost.
Official documentation
- HPE: AOS-CX 10.15 CLI guide, 6000/6100
- HPE: trunk interfaces and untagged traffic
- HPE: native VLAN command behavior
Examples were checked against documentation, not executed on physical switches. The cover is an illustrative networking image.
FAQ
What is the difference between an access port and a trunk on Aruba CX?
An access port assigns the endpoint to one VLAN. A trunk carries an allowed set of VLANs and has a native VLAN setting for untagged traffic.
Why is the native VLAN included in the allowed list?
AOS-CX documents that untagged ingress traffic is dropped when the native VLAN is excluded from the trunk allowed list.
Does creating a VLAN enable routing or DHCP?
No. The design also needs the appropriate gateway, routing, policy and DHCP server or relay. These are separate from Layer 2 VLAN membership.
Can I use these commands on Aruba Instant On?
This example is for AOS-CX. Use the documentation and management interface for your exact Instant On or ArubaOS-Switch product instead.
Check Current HPE Aruba Pricing
Browse the full, daily-updated HPE Aruba GPL on GlobalPriceList.com.
View HPE Aruba Price List See HPE Aruba Price History