Wireless Access

Reply
Occasional Contributor II

Upgrade from 8.3.0 to 8.2.1.1

I recently upgraded my MM/ MD environment from 8.2.1.0 to 8.3.0.

A few days after the release of 8.3.0, I noticed that there is a new version published, 8.2.1.1.

In release notes of 8.2.1.1 there are a few fixes for problems that arised in 8.3.0.

Are these releases different branches?

Is it safe to uprade to 8.2.1.1 from 8.3.0?

The release numbering confuses me.

 

John

Frequent Contributor II

Re: Upgrade from 8.3.0 to 8.2.1.1

Hi

 

Well, 8.2.1.1 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

 

Roar

Highlighted
Aruba Employee

Re: Upgrade from 8.3.0 to 8.2.1.1


@gvala wrote:

I recently upgraded my MM/ MD environment from 8.2.1.0 to 8.3.0.

A few days after the release of 8.3.0, I noticed that there is a new version published, 8.2.1.1.

In release notes of 8.2.1.1 there are a few fixes for problems that arised in 8.3.0.

Are these releases different branches?

Is it safe to uprade to 8.2.1.1 from 8.3.0?

 


Unless TAC has directed you to 8.2.1.1 for a bug fix, I would probably wait for 8.3.0.1 in your environment. 8.2.1.1 was out before 8.3.0.0, so presumably you went to 8.3 because of AP model support, which would not have been back-ported to 8.2.1.x.


Charlie Clemmer
Aruba Customer Engineering
Occasional Contributor II

Re: Upgrade from 8.3.0 to 8.2.1.1

Thanks for your replies.

8.2.1.1 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 8.2.1.1, where there are fixed problems that were observed at 8.3.0.0.

For example:


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 connected
to a Mobility Master running ArubaOS 8.3.0.0.
AP-345 access points

 

Frequent Contributor II

Re: Upgrade from 8.3.0 to 8.2.1.1

Hi

 

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

 

Roar

Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: