If you are a customer, partner, or EMC employee and you are subscribed to the ETA notifications list, you probably got a heads up about potential incompatibility between the VNX, RecoverPoint, and VAAI under certain conditions. For those of you who are not subscribed, fellow blogger Cormac Hogan wrote a quick little post about the issue.
I’m proud to announce that there is a fix available for this and it can be found in VNX Block OE 05.32.000.5.206 (released this week). Simply apply this fix (you can do it yourself using USM). For those of you with a FILE front end, make sure you update to 220.127.116.11 as well.
If you are an EMC Customer (with support zone credentials), you can read the full description of solution emc327099 (now stored on the new knowledgebase solution powered by Salesforce). If the direct link is not working, simply login to http://support.emc.com and search for “emc327099” and your first result should be the solution.
To state it right off the bat, this code does not include the features I talked about here and here but this is still a very important update. Yesterday marked the release of the latest update to the VNX with the general availability of VNX OE File 18.104.22.168 and OE Block 05.31.000.5.720 (both of which are available on the VNX product support page or by using the Unisphere Service Manager (USM) tool.
So you may be asking yourself, if this doesn’t come with all those cool features Sean talked about last week, why should I bother upgrading? Well I’m glad you asked that question. In addition to the many bug fixes incorporated in this service pack, this release contains 3 very important updates.
The first is support for the latest VMAX Enginuity code version 5876.82.57 that was released recently as well. The 2nd enhancement covers those using iSCSI. Anyone actively using iSCSI on their VNX should read ETA emc291837. The 3rd and final fix eliminate the erroneous over temperature alerts that were reporting on some power supplies that was previously covered in Primus emc278973.
As with all new code releases, I encourage everyone to upgrade as soon as possible and to not fall too far behind the latest code levels. I have started a discussion here on ECN incase you have questions about this release and the fixes contained within.