This page is updated on a fairly frequent basis with all the latest NetApp P-Releases. I’m also including a section for recommended downloads which includes the latest version of SnapDrive, MPIO Software, Data ONTAP version. These would all be suggested to be upgraded to or for new installs used.

If there’s a software release you don’t see that I check here often, please comment and I’ll check it more often. 

Also note, all links on this site require registration on the NetApp Support site.

Last Checked: 24-MAR-2019

Recommended Software Versions:

cDOT:

• Data ONTAP 9.5P2 (link)
• Multipath I/O 4.1P1 (link)
• SnapDrive for Windows 7.1.5P1 (link)

P-Release Change Log:

NetApp’s Official Software Change Log: http://mysupport.netapp.com/NOW/download/swchangelog.shtml

OnCommand API Services 2.1 (link)

Classification of NetApp Releases

http://mysupport.netapp.com/NOW/products/ontap_releasemodel/PostJul2010.shtml

Patch (P) Release

A patch release delivers timely fixes for bugs that customers encounter. The majority of customer-requested bug fixes are delivered through patch releases rather than debug (D) releases. P releases are not available before the release is classified as GA.

• Fixes for customer-encountered bugs.
• 1-2 months build frequency.
• QA regression testing of fixes.
• Significant fixes in a P release are in all subsequent maintenance releases for that feature release family. P releases that are provided after the maintenance release has gone into final testing phase are added to a subsequent maintenance release. Exceptions are clearly communicated in the public report for the controlling bug.

P releases typically follow the previous major or maintenance release—for example, 8.0.1P1 or 8.0.2P2. However, if there is a revision (R) release or a limited (L) release in the interim, the P release numbering is based on the R or L release instead—for example, 8.0.1R1P1 or 8.0.1R1P2.

Debug (D) Release

A debug release is an exception hot-fix release that is used on an urgent, as-needed basis. These releases are not normally planned and are provided only in case of extraordinary need.

• Provides a specific change for a specific customer.
• Changes do not automatically roll into the next maintenance release.
• May be deployed for customer who can’t wait for a P release or the next maintenance release.
• Not classified as a GA release.
• Provides fixes that are urgent and cannot wait for the next P release.
• Have limited testing.

Revision (R) Release

A revision release is an emergency release that is used when a critical fix needs to be deployed to all customers. NetApp recommends that all customers running the previous release should upgrade to the R release immediately. NetApp provides these releases only when it assesses that there is no alternative way to provide the fix in the short term to a wide range of customers. For instance, an R release might not be provided if a maintenance release is coming out soon.

• Generally triggered by a severe bug that affects a significant number of customers.
• QA regression and explicit testing of fixes.
• All fixes in a revision release are included in the next P release and maintenance release on this release family.