Hi Niels, your question is really interesting (about your doubt I really can say: me too).
The point is that ArubaOS-CX documentation doesn't give us a way to easily recognize what is the
software development chain that connect different ArubaOS-CX series (such as 10.0 -> 10.1 -> 10.2 -> 10.3 -> 10.4 -> 10.5 -> 10.6).
I tried to figure it out but it was not an easy task: a raw way to infer/argue some information would be to analyze the stamped build dates, but this method is reasonable only
to exclude that the very first build of a newer series - say the 10.06.0001 - could be related to a particular later build of the previous series - say the 10.05.0021 or the 10.05.0030 to name the latest - clearly if this/these one(s) has/have a build time that is falling AFTER the newer one released.
It says nothing about the relationship between consecutive AOS-CX series (10.n -> 10.n+1): for sure we all know (or imply) that - within a specific AOS-CX series - builds should be consecutively deployed one after the other (sometime some builds are not even released but, in any case, the software development within a particular series should be "serialized")...but this is not always exactly true...look, as example, at what happened on AOS-CX 10.4 with 10.4.00xx software builds and 10.4.x000 software builds both concurrently published to serve/support different product lines waiting for a unification - this is my view - then happened on AOS-CX 10.5).
In other terms - currently - there isn't an official matrix/list explaining what a particular AOS-CX software build is based on. At least I wasn't able to find it.
All post-AOS-CX 10.2 Release Notes -we are speaking of early 2019 - don't report any information that could help about that...and also the various
ArubaOS-CX Release Documentation documents (the latest one of three - here linked - was published on November 5th 2020) skips totally the point although it has a promising "Software Release Strategy" paragraph.
On the other hands the matrix/list I cited above initially existed: Yes, until ArubaOS-CX 10.02.0010 the "Version history" table on each Release Notes had a nice "Based on" column. After ArubaOS-CX 10.02.0010 software build that column suddenly disappeared forever.
------------------------------
Davide Poletto
------------------------------
Original Message:
Sent: Dec 10, 2020 03:25 AM
From: Niels Mejan
Subject: ArubaOS-CX 10.06.0002 is here!
Hello Parnassus,
I have a question regarding the "Version history" information and ArubaOS-CX. I'm trying to get an understanding how initial releases work, so basically what they are based upon.
My reference for this is ProCurve/Provision updates on the 5400/5400R-zl2 platforms. When there's a new train (just as an example let's say KB.15.10.xxxx) it usually said "the initial release it was based upon KB.15.08.xxxx". For me this meant that if there were specific features or bug-fixes in 15.08.xxxx trainn, I knew they would be implemented in the new 15.10.xxxx train as well.
My question is: The ArubaOS-CX 10.06.0001 is the initial release, but is this a complete new firmware? Or can I assume a new initial release is always based on the latest release from the previous train (so that would be 10.05.0030 in this case)?
Kind regards,
Niels Mejan,
University of Twente
------------------------------
Niels Mejan
Original Message:
Sent: Dec 08, 2020 05:36 PM
From: Davide Poletto
Subject: ArubaOS-CX 10.06.0002 is here!
Hi all,
ArubaOS-CX 10.06.0002 Software Images for Aruba 8400, Aruba 8360, Aruba 8325, Aruba 8320, Aruba 6400, Aruba 6300 and Aruba 6200 Switch series have been published.
References:
Please refer to Release Notes provided on above links for a complete view of new features, enhancements and bug fixes introduced with this ArubaOS-CX software release.
As always, Software Images listed above can be found on ASP Aruba Support Portal (Software and Documents).
------------------------------
Davide Poletto
------------------------------