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, upgrades between MRs Major Releases (say from 10.10 to 10.13) - which are both LSRs - should work (doing one single jump without restrictions), upgrades between Major Releases NOT being both two consecutive LSRs admit instead one jump every two MRs at maximum, say an upgrade path admits a jump from 10.11 (SSR) to 10.13 (LSR) - thus avoiding the 10.12 (SSR) - but it does not from 10.11 (SSR) to 10.14 (SSR) since that jump would involve three MRs.
Never tried the GUI way and never had a single issue updating/upgrading via CLI (since 10.0!)
Original Message:
Sent: 9/10/2024 5:05:00 PM
From: Russ_Altorfer
Subject: 6300 Firmware update issue
Hello,
I am bringing up an issue that I have been having with my 6300s and updating their firmware. If other people have seen this issue let me know. This is probably an issue I need to put a ticket in with support on, but I wanted to get some feedback from here first.
I am updating some 6300s before I put them into a production environment. The current version that they were on is FL.10.10.1070 and I need to get them to FL.10.13.1040. Per the documentation I need to run the command below. After figuring out the tftp issue in my environment I was able to run this command and not get any errors.
ArubaOS-CX 10.05 Fundamentals Guide 6300, 6400 Switch Series - copy {primary | secondary} <REMOTE-URL> (arubanetworks.com)
I run this command, and the firmware does not update. It stays at version 10.10.1070. Per the release notes for the version, I should be able to go directly to 10.13.1040. Just to eliminate the possible need to step up the versions I download and run the command to bring the version up to 10.12.1050. Here is a screenshot of the result. This was successful
My next step is to run the command again but upgrade the version to 10.13.1040. After running the command successfully, the version returns back to 10.10.1070 in this screenshot.
This is the head scratcher. My next step is to log into the WebUI and update the firmware this way. I did that and the version updated without an issue. As you can see here from the WebUI.
QUESTION:
This leads me to think that the 10.13.1040 version is setup to only be applied through the web and not able to be applied through the CLI. Is this true? Has anybody else run across this scenario as well?