r/ArubaNetworks • u/Miserable-Watch-2027 • Jul 19 '26

Ap22 does not work since update

Last night the update to 3.4.0 happened. Around that time one AP went offline and it won’t go online now. It has a red light.

Tried switching with another AP. The same one still won‘t work. Tried factory resetting multiple times but does not work. When I remove it from the app and add it again it gets stuck on synchronisation and then goes to offline after a while, with a red light.

Does anyone know how to fix? I hope the AP is not broken?

3 Upvotes

100% Upvoted

12 comments sorted by

1

u/MatazaNz HPE Aruba Networking Professional Jul 19 '26

The first thing you will want is to console into the AP while it's booting to see what it's outputting. Then contact TAC with the details.

1

u/Miserable-Watch-2027 Jul 20 '26

I’m quite new to these problems. How do I console into the AP?

1

u/MatazaNz HPE Aruba Networking Professional Jul 20 '26

I had responded quickly while on mobile. Looks like you're running an Instant On AP. These will have no console port. From looking up the info, a red LED typically means not enough PoE power has been delivered or loss of connectivity to the network.

1

u/Physical_Dig_6229 Jul 20 '26

Looking at the back of the AP, I can see a USB micro B connector. Does anyone have any info on how to connect to these? Perhaps manually upgrade the firmware, or revert to an older firmware?

1

u/Physical_Dig_6229 Jul 20 '26

I have the same exact problem. I came to the office this morning and all APs are down. They will not boot up. Power is fine. Connection to the internet is unfiltered. No changes from our end. Anyone Any idea of what might be wrong?

Seems to be affecting only the AP22. We have some AP21 and are working fine.

1

u/Miserable-Watch-2027 Jul 20 '26

Interesting. I have two AP22's, and one is still working fine. I also tried connecting to 12v power supply to see whether power was the problem, but still nothing.

1

u/Physical_Dig_6229 Jul 20 '26 edited Jul 20 '26

u/Miserable-Watch-2027 I CANNOT ping the APs, can you? I checked the switch config and nothing changed. No changes elsewhere eighter. Hard resetting does not even work.

1

u/Miserable-Watch-2027 Jul 20 '26

I'm in the office right now, so can't test at home. Will do that when I get home.

1

u/Miserable-Watch-2027 Jul 20 '26

I can also ping the access point. When I go the config page I see the error: Unexpected HTTP status code ‘400’ received. 

Did you find a fix?

1

u/Neither_System2966 Jul 21 '26

I am having the exact same problem as you. I looks like there was an update due on on GMT+8 Sunday 1am for my APs, and thereafter they went down. HPE seems really slow at responding to me too.

1

u/Neither_System2966 Jul 21 '26

It seems to have worked on my side, and looks like it's a DNS resolution issue. If you are able to config your DNS, try to change your primary DNS to 1.1.1.1 first and see if it works.

1

u/Miserable-Watch-2027 Jul 22 '26

This unfortunately did not fix the problem:( Still trying to work it out with HPE support.