topic Re: 2920 firmware rollback in Switches, Hubs, and Modems

2920 firmware rollback

Mark_1351 — Sat, 02 Oct 2021 04:19:31 GMT

I got a stack 2920-48g-poe+. I want to downgrade to wb.16.07.002. All other switches are running on wb.16.07.002. What is the best way to do it

Primary Image: wb.16.10.0015

Secondary Image: wb.16.10.0016

all other switches are in using wb.16.07.002

Re: 2920 firmware rollback

-Alex- — Fri, 01 Oct 2021 06:30:25 GMT

HelloMark_1351,

You may use the following procedure as it is explained on the following link for 2920 switch:

https://support.hpe.com/hpesc/public/docDisplay?docId=sf000048711en_us&docLocale=en_US

Hope this helps!

Re: 2920 firmware rollback

parnassus — Fri, 01 Oct 2021 19:16:21 GMT

Hi @Mark_1351, out of curiosity...why you need/want to downgrade your Aruba 2920 Stack from (current running?) WB.16.10.0015 or WB.16.10.0016 to the older WB.16.07.0002?

Re: 2920 firmware rollback

Mark_1351 — Sun, 03 Oct 2021 07:15:50 GMT

I saw this below link, and we are in lockdown. I don't want to have any issues.

https://community.hpe.com/t5/Aruba-ProVision-based/Warning-WB-16-10-0016-will-destroy-your-2920-Stack/m-p/7148527#.YVZMJZpBybg

Re: 2920 firmware rollback

Mark_1351 — Mon, 04 Oct 2021 10:04:13 GMT

Because I saw the below link, and we are in lockdown didn't want to face any issues

https://community.hpe.com/t5/Aruba-ProVision-based/Warning-WB-16-10-0016-will-destroy-your-2920-Stack/m-p/7148527#.YVZMJZpBybg

Re: 2920 firmware rollback

Mark_1351 — Mon, 04 Oct 2021 10:10:08 GMT

Alex, thanks for your information

is there a way to use the HPE intelligent management centre

Re: 2920 firmware rollback

akg7 — Mon, 04 Oct 2021 15:09:06 GMT

Hello @Mark_1351,

You can use IMC for config upgrade or downgrade. If normal process is possible then go with that.

Thanks!

Re: 2920 firmware rollback

parnassus — Tue, 05 Oct 2021 20:59:03 GMT

I hardly believe the issue that you were scaried about is a direct consequence of adopting a newer software version (WB.16.10.0017 is available as of now): IMHO the reported issue you're referencing (here) was probably caused by a incorrect procedure (or a correct procedure but a stack not in an optimal health or properly configured) otherwise Aruba TAC should have withdrawned the offending WB.16.10.0016 as per report by the poster. This didn't happened and WB.16.10.0017 doesn't report anything about solving such abrupt update bug hitting Aruba 2920 Stacks. I'm still curious to understand how the poster did the update procedure step-by-step (I suggested a specific guide which consider a manual update procedure for the whole stack, very simple) but he didn't answered yet.