cancel
Showing results for 
Search instead for 
Did you mean: 

Can a new version of Recommended Code be issued as the existing one dated 31 Aug 2015 is cause for concern

Can a new version of Recommended Code be issued as the existing one dated 31 Aug 2015 is cause for concern

Rod_Robertson2
Contributor
Can a new version of Recommended Code be issued as the existing one dated 31 Aug 2015 is a cause for concern as its 6 months old.
15 REPLIES 15

Ryan_Mathews
Extreme Employee
For those that read this in the future....here's a GTAC Knowledge article that captures where to find the Recommended Releases.

https://gtacknowledge.extremenetworks.com/articles/Q_A/What-Is-The-Recommended-Release-of-EXOS-For-M...

Drew_C
Valued Contributor III
Generally speaking, when the recommended release seems out-of-date, its a safe bet to use the latest patch in the same branch.
For example, EXOS 15.6.3.1-patch1-5 is "recommended" for several products in the matrix. However, EXOS 15.6.3.1-patch1-9 is available - that would be the best choice.
To take it another step, depending on release dates, EXOS 15.6.4.2 might be a better choice. It looks like that was released in December, and based on that, it should include all fixes that were in 15.6.3.1-patch1-9. You'd want to refer to the release notes to confirm this though.

Hope this helps!

Drew, yep that the logic I use..

Christina_Brunk
Extreme Employee
This doc will be updated with the release of 21.1 (2/26/16). The plan is to get all of the legacy Enterasys stuff included in the doc in the May/June timeframe. By the way, the latest and greatest version is 11/11/15, not 8/31/15. Here is the link.

Ok many thanks I find this document very useful , when we are having issues with some of the newer codes ( example X670 stacking , looked ok just would not work.
Reverted to recommended code "bingo it all worked"

It a good baseline to start from basically..

Many thanks for all your comments
GTM-P2G8KFN