2920 firmware rollback

[Mark_1351]

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

[-Alex-]

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!

[parnassus]

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?

[Mark_1351]

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

[Mark_1351]

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

[Mark_1351]

Alex, thanks for your information 

is there a way to use the HPE intelligent management centre

[akg7]

Hello @Mark_1351,

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

Thanks!

[parnassus · Accepted solution]

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.