HPE Aruba switch: trunk port not passing VLANs

By Sai Kiran Pandrala · reviewed by Sai Kiran Pandrala, Editor Last verified: 2026-05-30

What this guide covers

Fix trunk port not passing VLANs on a HPE Aruba switch.

Step-by-step

1. Confirm trunk both sides match, same VLAN list, same native VLAN.
2. Verify VLAN exists in the VLAN database.
3. Confirm trunk encapsulation type.
4. Check CDP / LLDP neighbours to compare both sides.

CLI / commands

show interface brief
show interface 1/1/1
show system

When the issue persists

• Open a Aruba TAC case with the tech-support bundle.
• Provide the timeline + recent changes.

Frequently asked questions

Will this work on my specific ArubaOS-CX version?

The procedure reflects current ArubaOS-CX behaviour. Older releases may need minor syntax adjustments: use the CLI help (? or tab-completion) to verify.

Should I open a Aruba TAC case immediately?

Open one if you suspect hardware failure or the symptom persists after a maintenance-window reload. Make sure your support entitlement is active first.

Where can I find the HPE Aruba official documentation?

https://community.arubanetworks.com/, search the product family + feature name.

Is this procedure safe in production?

Test in a lab or maintenance window first. Capture pre-change state so you can roll back.

Related guides

• All HPE Aruba fix guides → /hpe/
• All vendor guides → /vendors/

Related fixes

Related guides worth a look while you sort this one out:

• HPE Aruba firewall: trunk port not passing VLANs
• HPE Aruba router: trunk port not passing VLANs
• HPE Aruba Switch Port auto-negotiation mismatch (speed / duplex): How to Fix
• HPE Aruba Switch Port negotiates 100 Mbps instead of 1 Gbps: How to Fix
• HPE Aruba Switch Port PoE device not powering on: How to Fix
• HPE Aruba Switch Port stuck disabled by BPDU guard: How to Fix

References

• HPE Aruba support portal: https://www.arubanetworks.com/support-services/
• HPE Aruba knowledge base: https://community.arubanetworks.com/
• HPE Aruba security advisories: https://www.arubanetworks.com/support-services/security-bulletins/
• Open a case: https://asp.arubanetworks.com/

Reference material, not professional advice. Validate against your specific ArubaOS-CX version and test in a non-production environment before applying.

What changed recently?

Fault diagnosis on a HPE device goes faster when you map the symptom to a recent change:

• Did firmware update in the last 7 days?
• Did the network (router, ISP, VPN) change?
• Was the device moved physically?
• Did paired devices (phone, hub, app) update?
• Were any accessories swapped in or out?

The answer narrows the root cause to a manageable subset.

Before you start

A few things to confirm so the HPE device fix goes cleanly:

• Latest firmware downloaded if you're going to update.
• Warranty + support contract status checked. opening sealed parts may void it.
• Backup of current configuration (where applicable) taken.
• Spare parts on hand if you anticipate replacement.
• Adequate workspace, lighting, and time, rushing causes regressions.

How to confirm it's actually fixed

On a HPE device, the test is rarely "reboot and see". Use this list:

• Active reproduction: trigger the original failure path on purpose.
• Indirect reproduction: do an activity that would expose the same subsystem.
• Status indicator review: every LED / display / app status should be green.
• 24-hour soak: leave the device under normal load overnight; check the next morning.
• Telemetry check: review the device or app's diagnostic log for new error entries.

Escalation guide

For a HPE device, the right escalation depends on impact:

• Cosmetic / minor: log a ticket via the HPE app or web portal. Response 1-3 business days.
• Mid-impact: phone support. Have your serial number ready.
• Critical (production down, safety issue): in-person dealer / TAC visit. Bring proof of purchase.
• Out of warranty: third-party repair shop with manufacturer-certified technicians.

More frequently asked questions

How often should I run preventive checks?

Quarterly for most consumer devices; monthly for production / commercial devices. Set a calendar reminder so the device stays healthy between issues.

Are there safer alternatives for non-technical users?

Yes: the manufacturer's self-service troubleshooter (HP Smart, LG ThinQ, Samsung Members, similar) usually walks through the same steps in a guided UI. Use that first if you're not comfortable with menu paths.

Does this affect other devices on my network?

Generally no. The procedure is local to this device. Network-side changes (firmware updates that affect TLS, SMB, or routing) are flagged explicitly in the steps.

Is it safe to apply during business hours?

If the device is in production use, apply during a scheduled maintenance window. Most procedures need 2-15 minutes of downtime. Capture pre-change state so you can roll back if needed.

Can I roll this back if something breaks?

Yes for software-level changes (firmware rollback, config rollback). Hardware changes are usually one-way. Always back up settings before starting.