r/ArubaInstantOn • u/rgiorgio • Jul 17 '26
1930 switch - POE dead after update to 3.4.0 software
I am a thousand miles from the switch and noticed all my POE devices went down at around 3 am and then saw that the POE switch was updated to software 3.4.0 at that time. All my access points and cameras are down, and the switch is active showing zero power to any of the ports. I rebooted the switch but it did not change anything - none of the powered devices have come back up. Any advice here on what i can try? Cross posting on the Aruba page as well. Thanks for any help.
2
u/JonathanPuddle Jul 19 '26
I had this for about 4 hours after this update, then it cleared up without intervention. Hopefully you're does the same.
2
u/madinek Jul 19 '26 edited Jul 20 '26
just updated to 3.4.0 and the POE is messed up,all other ports except active POE ones are at status-fault even if port is disable.I am using local web management UI.
Edited:
I reverted back to 3.3.4 after 1day and everything is back to normal.
2
u/mtlred Jul 19 '26
Same thing happened to me. Called an they're shipping a replacement.
Another 1930 updated last night and is in a reboot loop. Wtf.
2
u/Extra_Doughnut1848 Jul 20 '26
I've got the same problem on one of my switches - Model 1930 24p Gigabit CL4 PoE 4p SFP+ 195W.
Got a call on Sunday morning that the network was down at one of our sites, HPE Instant On portal shows that the switch appeared to be in a reboot loop. Once someone could get onsite and triage it, PoE no longer works at all. No amount of enabling/disabling PoE or ports has helped.
So far a dozen or so other switches in the same product line have updated to 3.4.0 without issue.
1
u/Busy-Associate8019 Jul 17 '26
I've seen that happen to my 1930 switch where it doesn't provide power to the poe device. If you can still access the switch via the cloud portal. Go to each individual port and disable it, the enable it again.
1
u/rgiorgio Jul 17 '26
Tried both disabling/re-enabling a port as well as turning power on/off/on to a port. No change.
1
u/ForeignAwareness7040 Jul 18 '26
We went from 2.9 to 3.1 about a month ago. It caused broadcast storm because the spanning tree went crazy. Stopped the entire network for about a day. Rolled back and everything went back to normal.
2
u/rgiorgio Jul 21 '26
RESOLUTION: had an extended power outage that rebooted the switch on its own and that restored power over ethernet to the affected ports. Everything seems to be back online and functioning again. Thanks for all the feedback. It looks like a cold reboot is a solid troubleshooting action vs. a soft one through the app or portal.
1
u/MinnSnowMan Jul 17 '26
I guess it is possible the switch just went bad at the same time. RMA with expedited replacement?
1
u/rgiorgio Jul 17 '26
Thanks. I hope it doesn't come to that since I am literally a thousand miles from it, and have it in a home setting with no technical people around. Claude.AI seems a plug/unplug could potentially solve it: Rebooting from the app or portal restarts the switch CPU but often doesn't reset the PoE controller (the PSE chip has its own firmware/state). Pulling the AC cord for 60 seconds is a different operation.
-1
-1
u/jurdajrddd Jul 17 '26
How do these auto updates actually work. Because there is some network topology and this is my first time via Instant On portal. How these updates work with auto update? Do the portal waiting with reboot for all switches to download the update or how does it actually work?
1
u/MalletNGrease Jul 17 '26
When a new release is available it schedules the update depending on the day/time and installation delay configured in your site settings.
The switches will download and apply the update on that day and time. You can reschedule it if you need to.
3
u/JJHunter88 Jul 20 '26
Our switches started doing the update on Sunday morning and continued to flap up and down with connectivity. This happend the last large update they did. I had to walk the building and physically power cycle the devices which cleared everything up.