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

  • 0
  • 2
  • Question
  • Updated 3 years ago
  • Answered
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.
Photo of Rod Robertson

Rod Robertson

  • 2,344 Points 2k badge 2x thumb

Posted 3 years ago

  • 0
  • 2
Photo of David Coglianese

David Coglianese, Embassador

  • 6,504 Points 5k badge 2x thumb
What code version are you running and what type of switches do you have?
Photo of Patrick Voss

Patrick Voss, Alum

  • 11,594 Points 10k badge 2x thumb
Which platform are you looking for a recommended release? Also, the recommended release is more of a guideline considering some protocols being used may change the recommended version.
Photo of Drew C.

Drew C., Community Manager

  • 39,376 Points 20k badge 2x thumb
I've emailed the appropriate teams internally asking if we can get an updated doc published soon.  I'll provide updates here when I know more.
Photo of Christina Brunk

Christina Brunk, Employee

  • 496 Points 250 badge 2x thumb
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.
Photo of Christina Brunk

Christina Brunk, Employee

  • 496 Points 250 badge 2x thumb
I have been told I am wrong - looking into this now...
Photo of Christina Brunk

Christina Brunk, Employee

  • 496 Points 250 badge 2x thumb
I stand corrected. The document was updated on 11/11/15 but the page in question was not – I hate it when that happens.

 This document will be updated on 2/26/16 for the EXOS 16.1.3 release and again in March for the EXOS 21.1 release.

 Apologize for the confusion!
(Edited)
Photo of Ryan Mathews

Ryan Mathews, Alum

  • 8,988 Points 5k badge 2x thumb
Great.....thanks for the update Christina.
Photo of Rod Robertson

Rod Robertson

  • 2,344 Points 2k badge 2x thumb
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
Photo of Drew C.

Drew C., Community Manager

  • 39,376 Points 20k badge 2x thumb
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!
Photo of Rod Robertson

Rod Robertson

  • 2,344 Points 2k badge 2x thumb
Drew, yep that the logic I use..
Photo of Ryan Mathews

Ryan Mathews, Alum

  • 8,988 Points 5k badge 2x thumb
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...
Photo of Rod Robertson

Rod Robertson

  • 2,344 Points 2k badge 2x thumb
Hi , an update !!!! , we are being recommended by the gtac engineers to go to code 15.6.4.2-patch1-3 for 440 and X670 switches .. .

I understood the reason for issuing this document was to give external engineers confidence in the code that was being suggest , for basic switch installation and configurations. ( code used to be relatively stable, this has not been the case in the recent past  )

The link above ( previous comment bu Ryan )still directs us to a page where it was last updated 31 AUG 2015.. with a different version of code suggested.

Can I suggest that the document is updated  ( there was some talk of this happening Feb 2016 )with some sort of "time and date" stamp , or have it removed .

I look forward to your comments.
Photo of Ryan Mathews

Ryan Mathews, Alum

  • 8,988 Points 5k badge 2x thumb
Thanks for the comments on this Rod.  

As you can see, Christina's team is working hard to not only keep the Recommended Release versions up to date going forward, but also expand them to cover the entire Extreme portfolio.

Appreciate your patience as we get organized to establish and maintain an update frequency going forward.  
Photo of Christina Brunk

Christina Brunk, Employee

  • 496 Points 250 badge 2x thumb
This document should be updated very soon (if it doesn't go live today, it will go live tomorrow). I initially quoted a date of February 2016 to coincide with EXOS 21.1 GA but that got pushed out so the publishing of this document got pushed out as well. Note that this revision of this document does not include the latest (recommended) EOS FW added. That information was very outdated so it was removed until it can be comprehensively and accurately included (May timeframe).
 
Photo of Christina Brunk

Christina Brunk, Employee

  • 496 Points 250 badge 2x thumb