Aruba & ProVision-based
cancel
Showing results for 
Search instead for 
Did you mean: 

end of support logiciel YA.15.17.0013 & WB.15.17.0013

 
SOLVED
Go to solution
zkadri
Occasional Visitor

end of support logiciel YA.15.17.0013 & WB.15.17.0013

Hello

Could you please provide me the date of "end of support" for these software versions by your carrier?

YA.15.17.0013
WB.15.17.0013

Thank you in advance,

4 REPLIES 4
parnassus
Honored Contributor

Re: end of support logiciel YA.15.17.0013 & WB.15.17.0013

Your question seems a little bit unclear (to me): Are you asking what is the software release cycle for the YA.15.17 and WB.15.17 software branches (in other terms: When the YA.15.17/WB.15.17 software development will eventually end) *or* are you asking when the Switches which are running those software versions will be eventually declared EoS/EoL?

zkadri
Occasional Visitor

Re: end of support logiciel YA.15.17.0013 & WB.15.17.0013

Hello thank you for your return In fact i ask the twos questions

When the YA.15.17/WB.15.17 software development will eventually end) *and* when the Switches which are running those software versions will be eventually declared EoS/EoL?

parnassus
Honored Contributor
Solution

Re: end of support logiciel YA.15.17.0013 & WB.15.17.0013

Hard to say, to answer to my own two questions...here my personal speculations:

YA = Aruba 2530 (HP ProCurve/HPE 2530)

WB = Aruba 2920 (HP ProCurve/HPE 2920)

I think that CPE - Current Production Engineering - branch (now called Software GA) should normally live for approximately between 12 months and 18 months (so, speaking about branches YA.15.17 and WB.15.17 they should have a life expectancy between 12 and 18 months)...after that (or yet during it) a software development creates a new GA milestone (as example, YA.15.18 and WB.15.18 branches...and then so on)...this cycle, AFAIK, repeats approximately every 18 months [*] (or less, see the case between the introducton of 16.01 branch and the next 16.02)...Sofware branches generally may overlap (a AA.xx.yy+1 branch starts during the previous one AA.xx.yy is still developing)...and without considering possible Maintenance branches (m)...but the Product EoS, in the end, has the definitive word on such software development roadmap.

For HPE Switch EoS start looking here.

AFAIK neither the Aruba 2530 nor the Aruba 2920 are actually on the EoL list...so their Software Roadmaps should follow, from what I've understood, what I've written above (in terms of Software GA release cycles).

So questions:

  1. When the YA.15.17/WB.15.17 software development will eventually end?
  2. When the Switches which are running those software versions (YA/WB) will be eventually declared EoS?

My take:

  1. Probably after 12/18 months after their respective 15.17 branch started.
  2. I don't know (only HPE knows that and publishes that on the HPE EoS portal, see link above).

[*] As example, for YB.15.17 the very first release officially published was the YB.15.17.0007 on June 2015 (it has it roots on YB.15.17.0003 - never published - and on the older YB.15.16.0004), the latest release was posted on June 2016...so, you see, there are about 12 months among the two...probably in the next 6 months we will see that YB.15.17 branch will end its cycle in favour of newer (actual or future) Software GA releases.

zkadri
Occasional Visitor

Re: end of support logiciel YA.15.17.0013 & WB.15.17.0013

Thank you a lot for your help on this topic