I recently upgraded my MM/ MD environment from 220.127.116.11 to 8.3.0.
A few days after the release of 8.3.0, I noticed that there is a new version published, 18.104.22.168.
In release notes of 22.214.171.124 there are a few fixes for problems that arised in 8.3.0.
Are these releases different branches?
Is it safe to uprade to 126.96.36.199 from 8.3.0?
The release numbering confuses me.
Well, 188.8.131.52 is a LOWER version than 8.3.
So this will be a downgrade.
The reason for versions of 8.2 coming out after 8.3 is because of patches and bugfixes.
If you already are on 8.3 you will have newer features than 8.2.x.x, but maybe not the same bugfixes. These bugfixes will arrive on 8.3 later.
If you don't have a specific problem you can relate to a certain bugfix, don't bother changing anything
@gvala wrote:I recently upgraded my MM/ MD environment from 184.108.40.206 to 8.3.0.A few days after the release of 8.3.0, I noticed that there is a new version published, 220.127.116.11.In release notes of 18.104.22.168 there are a few fixes for problems that arised in 8.3.0.Are these releases different branches?Is it safe to uprade to 22.214.171.124 from 8.3.0?
Unless TAC has directed you to 126.96.36.199 for a bug fix, I would probably wait for 188.8.131.52 in your environment. 184.108.40.206 was out before 220.127.116.11, so presumably you went to 8.3 because of AP model support, which would not have been back-ported to 8.2.1.x.
Thanks for your replies.
18.104.22.168 was released (or maybe published) at 10/06/2018 and 8.3.0 at 29/4/2018
And what seems to be obvious according to version numnering, becomes less obvious when you read the release notes for 22.214.171.124, where there are fixed problems that were observed at 126.96.36.199.
168814 Symptom: The Mobility Master WebUI displayed incorrect channel bandwidth and dual-5 GHz mode information. This issue is resolved by adding GSM support for AP channels.Scenario: This issue was observed in AP-345 access points connectedto a Mobility Master running ArubaOS 188.8.131.52.AP-345 access points
Well, this is not hard to comprehend.
Each major version like 8.1, 8.2 and 8.3 has it's own timeframe on when patches are released.
Finding a bug in 8.3, this has to be implemented into both 8.1, 8,2 and 8.3. At this point the release date for patch on 8.2 was earlier than 8.3.
As mentioned earlier, if TAC has not given you a specific release to upgrade to because of a bug or if you are experiencing some strange resulst, just wait for the same patch to be released for 8.3, no biggie
At Aruba, we believe that the most dynamic customer experiences happen at the Edge. Our mission is to deliver innovative solutions that harness data at the Edge to drive powerful business outcomes.
© Copyright 2021 Hewlett Packard Enterprise Development LPAll Rights Reserved.