IP / Network Issue

HPE Aruba switch: DHCP relay not forwarding

Q: Where can I find the HPE Aruba official documentation?

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

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

⚡ At a glance

Vendor	HPE Aruba
Operating system	ArubaOS-CX
Category	IP / Network Issue
Skill level	Intermediate to advanced
DIY-able?	Yes with CLI access; some scenarios need Aruba TAC + RMA.

What this guide covers

Fix DHCP relay not forwarding on a HPE Aruba switch.

Step-by-step

Confirm the helper-address / relay-IP is configured.
Ensure the DHCP server IS reachable from the relay.
Verify no ACL is blocking UDP 67/68.
Capture relay traffic to confirm where it stops.

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.

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

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

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.

Safety + preconditions

Before any work on a HPE device:

Unplug from mains for any internal-access procedure.
Discharge stored energy (capacitors in PSUs, residual battery charge) per manufacturer guidance.
Use ESD-safe handling for boards and modules, no carpet, no wool sleeves.
Avoid moisture; never apply liquids near vents or connectors.
If you smell smoke, see scorch marks, or feel uneven heat, stop and escalate.

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.

When to call HPE support instead

Escalate if:

The same symptom returns within 24 hours of a clean fix.
You see physical damage (burn marks, swollen battery, cracked PCB).
The device is in warranty and a hardware replacement is the cheaper outcome.
Repair requires specialised tools you don't own (alignment jigs, calibration software).
Following the official path keeps the warranty intact, which matters more than the time spent.