Network Management

I did not think about the LSR and SSR difference. From the release notes I saw that I should be able to go from 10.10.1071 to 10.13.1040 since its later then 10.10.0002. What is funky though is that when I go from 10.12.xxxxx to 10.13.xxxx it jumps back to 10.10.xxxx. I have never seen a system automatically do that unless there was an issue with the new version and I requested or approved going back.

It looks like you are booting from secondary partition.

Connect serial/usb console and select primary partition at the bootstrap time.

Or you can use "boot setdefault primary" to set next boot partition.

In any case serial console should give you a clue what it is going on. Maybe the primary partition is faulty and need to be reformated or flash need to be replaced.

Best, Gorazd

I did not think about the LSR and SSR difference. From the release notes I saw that I should be able to go from 10.10.1071 to 10.13.1040 since its later then 10.10.0002. What is funky though is that when I go from 10.12.xxxxx to 10.13.xxxx it jumps back to 10.10.xxxx. I have never seen a system automatically do that unless there was an issue with the new version and I requested or approved going back.

Hi Russ,
i believe Gorazd is on the right track here.

You can check the LOG of the Switch with "show logg -a" to see all information since the last reboot. There could be a record of a broken image on one of the filesystem-partitions.

Also 10.10.x and 10.13.x are both LSR-Releases which should give you a longer lifecycle of the installed software and also features like hot-patching and ISSU (botgh features only on 10.13).

You can check the firmware-image-checksum also via CLI (Command: show images verify primary or show images verify secondary). Then crosscheck the hash to the published hash on HPE/ANW-Webpage.

Also check the images after uploading with "show images" and then set default to the new (and correct) firmware (command by goradz).

Happy troubleshooting

Franz

It looks like you are booting from secondary partition.

Connect serial/usb console and select primary partition at the bootstrap time.

Or you can use "boot setdefault primary" to set next boot partition.

In any case serial console should give you a clue what it is going on. Maybe the primary partition is faulty and need to be reformated or flash need to be replaced.

Best, Gorazd

I did not think about the LSR and SSR difference. From the release notes I saw that I should be able to go from 10.10.1071 to 10.13.1040 since its later then 10.10.0002. What is funky though is that when I go from 10.12.xxxxx to 10.13.xxxx it jumps back to 10.10.xxxx. I have never seen a system automatically do that unless there was an issue with the new version and I requested or approved going back.

Unsure where that LSR-SSR story related to upgrades comes from, but as far as I know that applies to compatibility on AOS8 wireless with mobility conductors.

For switching and Instant, if there are required intermediate steps, these are listed out in the release notes. It also mentions if there is a bootloader/ROM upgrade, which means that the upgrade will take longer (additional reboots).

Still it's strange/unexpected that when you upgrade the firmware that it jumps back to the old firmware.

Russ, were you able to upgrade the firmware already?

Hi Russ,
i believe Gorazd is on the right track here.

You can check the LOG of the Switch with "show logg -a" to see all information since the last reboot. There could be a record of a broken image on one of the filesystem-partitions.

Also 10.10.x and 10.13.x are both LSR-Releases which should give you a longer lifecycle of the installed software and also features like hot-patching and ISSU (botgh features only on 10.13).

You can check the firmware-image-checksum also via CLI (Command: show images verify primary or show images verify secondary). Then crosscheck the hash to the published hash on HPE/ANW-Webpage.

Also check the images after uploading with "show images" and then set default to the new (and correct) firmware (command by goradz).

Happy troubleshooting

Franz

It looks like you are booting from secondary partition.

Connect serial/usb console and select primary partition at the bootstrap time.

Or you can use "boot setdefault primary" to set next boot partition.

In any case serial console should give you a clue what it is going on. Maybe the primary partition is faulty and need to be reformated or flash need to be replaced.

Best, Gorazd

I did not think about the LSR and SSR difference. From the release notes I saw that I should be able to go from 10.10.1071 to 10.13.1040 since its later then 10.10.0002. What is funky though is that when I go from 10.12.xxxxx to 10.13.xxxx it jumps back to 10.10.xxxx. I have never seen a system automatically do that unless there was an issue with the new version and I requested or approved going back.

Hi Herman, I don't understand what reply you were referring to when you wrote:

"Unsure where that LSR-SSR story related to upgrades comes from, but as far as I know that applies to compatibility on AOS8 wireless with mobility conductors."

but, if I'm not mistaken, this thread is focused on AOS-CX software (not particularly on AOS, at least as far as I understand the whole thread) so the references about AOS-CX SSR/LSR make sense (maybe those references don't provide the OP any solution but they add some information about how AOS-CX software jumps from non consecutive Major Software releases could/couldn't be done).

If I remember correctly (that's historical...) the single jump from AOS-CX LSR 10.(x) to LSR 10.(x+3) - e.g. from AOS-CX 10.10 to AOS-CX 10.13 - is admitted by HPE Aruba (no matter that the newer LSR 10.(x+3) is three Major Software releases far from the older LSR 10.(x) one), any other scenario instead - IF this restriction is still true today (as I believe) - involving any SSR/LSR (it doesn't really matter) only a two Major Software releases jump is admitted, example we can go from AOS-CX 10.(x) to 10.(x+2) and so we can skip one intermediate Major Software release but we can't go from 10.(x) to 10.(x+3) if both x or x+3 aren't LSR (so, as example, from 10.11 to 10.13 is OK but from 10.11 to 10.14 is not OK).

Hope the above is still true (AFAIK it was prior to AOS-CX 10.10 era).

Unsure where that LSR-SSR story related to upgrades comes from, but as far as I know that applies to compatibility on AOS8 wireless with mobility conductors.

For switching and Instant, if there are required intermediate steps, these are listed out in the release notes. It also mentions if there is a bootloader/ROM upgrade, which means that the upgrade will take longer (additional reboots).

Still it's strange/unexpected that when you upgrade the firmware that it jumps back to the old firmware.

Russ, were you able to upgrade the firmware already?

Hi Russ,
i believe Gorazd is on the right track here.

You can check the LOG of the Switch with "show logg -a" to see all information since the last reboot. There could be a record of a broken image on one of the filesystem-partitions.

Also 10.10.x and 10.13.x are both LSR-Releases which should give you a longer lifecycle of the installed software and also features like hot-patching and ISSU (botgh features only on 10.13).

You can check the firmware-image-checksum also via CLI (Command: show images verify primary or show images verify secondary). Then crosscheck the hash to the published hash on HPE/ANW-Webpage.

Also check the images after uploading with "show images" and then set default to the new (and correct) firmware (command by goradz).

Happy troubleshooting

Franz

It looks like you are booting from secondary partition.

Connect serial/usb console and select primary partition at the bootstrap time.

Or you can use "boot setdefault primary" to set next boot partition.

In any case serial console should give you a clue what it is going on. Maybe the primary partition is faulty and need to be reformated or flash need to be replaced.

Best, Gorazd

I did not think about the LSR and SSR difference. From the release notes I saw that I should be able to go from 10.10.1071 to 10.13.1040 since its later then 10.10.0002. What is funky though is that when I go from 10.12.xxxxx to 10.13.xxxx it jumps back to 10.10.xxxx. I have never seen a system automatically do that unless there was an issue with the new version and I requested or approved going back.

I'm not aware of such a rule about LSR/SSR upgrades AOS-CX (or ArubaOS-Switch). Unless the release notes mention otherwise, you can do direct upgrades to any version in my understanding.

I've never done any intermediate upgrades on CX or AOS-Switch. So the LSR/SSR status is not relevant for upgrades; unless something is written in the release notes (which normally is not LSR/SSR related). Never heard this related to CX, but I may be wrong, if so, please provide the pointers (I searched but could not find). The +/- 3 versions is valid for ArubaOS 8.x controllers (and maybe AOS10 which can be the source of confusion), but I don't believe it applies anywhere on switching.

As these forums are seen by many people as 'source of truth', it's good to make sure the information is as accurate as possible.

------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
------------------------------


Original Message:
Sent: Sep 23, 2024 08:44 AM
From: parnassus
Subject: 6300 Firmware update issue

Hi Herman, I don't understand what reply you were referring to when you wrote:

"Unsure where that LSR-SSR story related to upgrades comes from, but as far as I know that applies to compatibility on AOS8 wireless with mobility conductors."

but, if I'm not mistaken, this thread is focused on AOS-CX software (not particularly on AOS, at least as far as I understand the whole thread) so the references about AOS-CX SSR/LSR make sense (maybe those references don't provide the OP any solution but they add some information about how AOS-CX software jumps from non consecutive Major Software releases could/couldn't be done).

If I remember correctly (that's historical...) the single jump from AOS-CX LSR 10.(x) to LSR 10.(x+3) - e.g. from AOS-CX 10.10 to AOS-CX 10.13 - is admitted by HPE Aruba (no matter that the newer LSR 10.(x+3) is three Major Software releases far from the older LSR 10.(x) one), any other scenario instead - IF this restriction is still true today (as I believe) - involving any SSR/LSR (it doesn't really matter) only a two Major Software releases jump is admitted, example we can go from AOS-CX 10.(x) to 10.(x+2) and so we can skip one intermediate Major Software release but we can't go from 10.(x) to 10.(x+3) if both x or x+3 aren't LSR (so, as example, from 10.11 to 10.13 is OK but from 10.11 to 10.14 is not OK).

Hope the above is still true (AFAIK it was prior to AOS-CX 10.10 era).

Original Message:
Sent: Sep 23, 2024 06:06 AM
From: Herman Robers
Subject: 6300 Firmware update issue

Unsure where that LSR-SSR story related to upgrades comes from, but as far as I know that applies to compatibility on AOS8 wireless with mobility conductors.

For switching and Instant, if there are required intermediate steps, these are listed out in the release notes. It also mentions if there is a bootloader/ROM upgrade, which means that the upgrade will take longer (additional reboots).

Still it's strange/unexpected that when you upgrade the firmware that it jumps back to the old firmware.

Russ, were you able to upgrade the firmware already?

------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.


Original Message:
Sent: Sep 12, 2024 03:52 AM
From: FHegnauer
Subject: 6300 Firmware update issue

Hi Russ,
i believe Gorazd is on the right track here.

You can check the LOG of the Switch with "show logg -a" to see all information since the last reboot. There could be a record of a broken image on one of the filesystem-partitions.

Also 10.10.x and 10.13.x are both LSR-Releases which should give you a longer lifecycle of the installed software and also features like hot-patching and ISSU (botgh features only on 10.13).

You can check the firmware-image-checksum also via CLI (Command: show images verify primary or show images verify secondary). Then crosscheck the hash to the published hash on HPE/ANW-Webpage.

Also check the images after uploading with "show images" and then set default to the new (and correct) firmware (command by goradz).

Happy troubleshooting

Franz

------------------------------
prefers to not experiment with live customer equipment...


Original Message:
Sent: Sep 12, 2024 02:10 AM
From: GorazdKikelj
Subject: 6300 Firmware update issue

It looks like you are booting from secondary partition.

Connect serial/usb console and select primary partition at the bootstrap time.

Or you can use "boot setdefault primary" to set next boot partition.

In any case serial console should give you a clue what it is going on. Maybe the primary partition is faulty and need to be reformated or flash need to be replaced.

Best, Gorazd

------------------------------
Gorazd Kikelj
MVP Guru 2024


Original Message:
Sent: Sep 11, 2024 12:42 PM
From: Russ_Altorfer
Subject: 6300 Firmware update issue

I did not think about the LSR and SSR difference. From the release notes I saw that I should be able to go from 10.10.1071 to 10.13.1040 since its later then 10.10.0002. What is funky though is that when I go from 10.12.xxxxx to 10.13.xxxx it jumps back to 10.10.xxxx. I have never seen a system automatically do that unless there was an issue with the new version and I requested or approved going back.

Original Message:
Sent: Sep 11, 2024 12:28 PM
From: parnassus
Subject: 6300 Firmware update issue

Hi Russ,
i believe Gorazd is on the right track here.

You can check the LOG of the Switch with "show logg -a" to see all information since the last reboot. There could be a record of a broken image on one of the filesystem-partitions.

Also 10.10.x and 10.13.x are both LSR-Releases which should give you a longer lifecycle of the installed software and also features like hot-patching and ISSU (botgh features only on 10.13).

You can check the firmware-image-checksum also via CLI (Command: show images verify primary or show images verify secondary). Then crosscheck the hash to the published hash on HPE/ANW-Webpage.

Also check the images after uploading with "show images" and then set default to the new (and correct) firmware (command by goradz).

Happy troubleshooting

Franz

It looks like you are booting from secondary partition.

Connect serial/usb console and select primary partition at the bootstrap time.

Or you can use "boot setdefault primary" to set next boot partition.

In any case serial console should give you a clue what it is going on. Maybe the primary partition is faulty and need to be reformated or flash need to be replaced.

Best, Gorazd

I did not think about the LSR and SSR difference. From the release notes I saw that I should be able to go from 10.10.1071 to 10.13.1040 since its later then 10.10.0002. What is funky though is that when I go from 10.12.xxxxx to 10.13.xxxx it jumps back to 10.10.xxxx. I have never seen a system automatically do that unless there was an issue with the new version and I requested or approved going back.

Hi @Russ_Altorfer,

I think that Herman (Robers) is onto something.

I just wanted to Update an old 6300f from 10.08.x to 10.13.1050. I can do that, but only if i allow "unsafe updates". Maybe this is the reason, why your switch was reset to factory-default in the first place while upgrading. When i allowed those updates, it siad, it will rewrite 6 devices instead of 3 (which gives me a clue).

Probably you didn't allow those "unsafe updates" (which basicly allows the switch to rewirte it's boot-block and the recovery-Partition!!!). Those updates are "unsafe", because if you mess up (loose power or something else), the device is bricked (can only be revived by HPE-tech or lots of Serial-Cable-Fun with xmodem...). 

I 'd assume, that if the firmware is to new to be recognized by the boot-loader, than a default-config is beeing loaded to make sure, that the switch is still functional.

But what i can see from your screenshots is, that you didn't reboot the switch while updating. beforehand you need to switch the default boot to the updated image-partition.

If you need those commands, just write me an PN.

Best of Luck to you.

Franz

Hi.

Unsafe updates are necessary when underlying FW for various HW modules inside the switch need to be updated. Switch OS expect certain behavior from underlaying components to function properly. Hence those FWs are provided with it. When upgrading it is vise to check console output to see, if unsafe updates are needed. If you skip to many versions, (jump too far or did not enable unsafe updates in previous versions) then it is possible that latest version upgrade will not succeed until you allow unsafe updates.

Best, Gorazd  

Hi.

Unsafe updates are necessary when underlying FW for various HW modules inside the switch need to be updated. Switch OS expect certain behavior from underlaying components to function properly. Hence those FWs are provided with it. When upgrading it is vise to check console output to see, if unsafe updates are needed. If you skip to many versions, (jump too far or did not enable unsafe updates in previous versions) then it is possible that latest version upgrade will not succeed until you allow unsafe updates.

Best, Gorazd  

Hi @Russ_Altorfer,

I think that Herman (Robers) is onto something.

I just wanted to Update an old 6300f from 10.08.x to 10.13.1050. I can do that, but only if i allow "unsafe updates". Maybe this is the reason, why your switch was reset to factory-default in the first place while upgrading. When i allowed those updates, it siad, it will rewrite 6 devices instead of 3 (which gives me a clue).

Probably you didn't allow those "unsafe updates" (which basicly allows the switch to rewirte it's boot-block and the recovery-Partition!!!). Those updates are "unsafe", because if you mess up (loose power or something else), the device is bricked (can only be revived by HPE-tech or lots of Serial-Cable-Fun with xmodem...). 

I 'd assume, that if the firmware is to new to be recognized by the boot-loader, than a default-config is beeing loaded to make sure, that the switch is still functional.

But what i can see from your screenshots is, that you didn't reboot the switch while updating. beforehand you need to switch the default boot to the updated image-partition.

If you need those commands, just write me an PN.

Best of Luck to you.

Franz

So, an overall update this issue.

I had a support call today with Aruba, and I was able to reproduce the issue on two different switches. While on the call with them I was able to upgrade the partition to 10.13.1050 without any issue. Even though I was able to get to the version I wanted to via the WebUI and USB initially, this issue has not hindered me with putting these switches into production. I hope that I have provided enough evidence and information to Aruba so that they can troubleshoot the issue. 

Thank you everyone for the responses and insight. This whole experience has been interesting, and I look at it as a learning experience.