Wired Intelligent Edge

As the title suggests I ask the experts to help me shed some light about a comparison between ArubaOS-CX 10.01.0050 and ArubaOS-CX 10.02.0010 (both latest released at time of writing this post).

 

 

Since ArubaOS-CX 10.02.0001 was forked directly from ArubaOS-CX 10.01.0001 I'm trying to figure out if the entire ArubaOS-CX 10.02 software branch embeds (backport?) some or all [*] of the fixes released during the whole ArubaOS-CX 10.01 software release cycle (so between ArubaOS-CX 10.01.001 and ArubaOS-CX 10.01.0050).

 

[*] ...only if they were really necessary on the new ArubaOS-CX 10.02 code.

 

The above question will help me to figure out what is the most solid path [**] to follow in upgrading a running Aruba 8320 VSX actually based on ArubaOS-CX 10.01.0030: should I stay on ArubaOS-CX 10.01 branch and update to 10.01.0050 or move on and do the jump by updating to 10.02.0010?

 

Is it reasonable to stay on ArubaOS-CX 10.01 during 2019 considering that actual ArubaOS-CX software branches can't be concurrently developed too long [***]?

 

[**] purely from the VSX, System Stability and Layer 2 features (VSX LAGs, Port MTU, etc.) standpoint, my scenario actually doesn't involve particular Layer 3 features...also I can sacrifice new features like (so much desired) orchestrated VSX software update in the name of software code proven maturity.

 

[***] see here.

From my experience I can confirm that bugs that were fixed in 10.01.0050 were already removed in 10.02.0001. I do not know if this is true for all bugs.

---

@v0tti wrote:
From my experience I can confirm that bugs that were fixed in 10.01.0050 were already removed in 10.02.0001.

---

Is the opposite valid too?

 

Suppose on ArubaOS-CX 10.02 software branch a new VSX bug is found and then fixed...and suppose this very new VSX bug is also affecting the ArubaOS-CX 10.01 software branch...can we expect that bug fix on ArubaOS-CX 10.02 will be backported to ArubaOS-CX 10.01?

 

I'm pretty much sure this is what is currently happening (I hope!)...the point is...up to which ArubaOS-CX release this will happen for the "older" software branch?

 

It's to understand how long one can safely stay on ArubaOS-CX 10.01 before being forced by development to move to ArubaOS-CX 10.02 (generically is a discussion relate to ArubaOS-CX 10.n branch versus ArubaOS-CX 10.m branch, where m > n).

hi parnassus,

 

you should work with your local SE to get this answered. The answer will include strategies of rolling bug fixes in different software trees and I'm certain, we will not share this information here in the forum but I'm very sure, you local SE is able to get that information and share them with you directly. 

Hello Florian,

 

Thank you for your answer!

 

I perfectly understand what you said...but I really don't need to go too deep at level of Aruba internal software development processes (e.g. what particular bug fix "is/is not backported to different software branches")...I'm more interested - as ArubaOS-CX user - to understand if the general rule is "to backport or not" and consequently to learn how long an ArubaOS-CX software branch could exist concurrently to others softwre branches.

 

It's like having a document like this one (it refers to old good HP ProVision days and it is public domain) but related to ArubaOS-CX.

Hi parnassus,

 

Ok, fully agree, this could be something we can share. Unfortunately, I do not have this information but let see if someone from the devs shows up here and can help. 

 

BR

Florian

Your point is considered and I hope you'll get an answer in a appropriate timeline.

From my experience I can confirm that bugs that were fixed in 10.01.0050 were already removed in 10.02.0001. I do not know if this is true for all bugs.