First time in a little while, but another EMC TA bulletin arrived in my inbox last week. The inclusion of “potential data unavailability” in the subject got my attention.
Full release here
This particular bulletin affects only VNX Series 1 Arrays (5300, 5500, 5700 and 7500) that are upgrading to Block OE R32.217 or R32.218. The interesting part is that it also requires there to be a DAE-60/DAE7S Shelf in the system.
The DAE-60 (codenamed “Voyager“) is a 3RU DAE that can be populated with 60 2.5″ or 3.5” drives, making it an very dense and powerful component, only beaten for density by the DAE8S (codenamed “Viking“) that can seat 120 2.5” drives… But I digress!
DAE-60 Front/Rear view, minus bezel ** DAE8S Front/Rear view, minus bezel **
According to the ETA, upgrades to VNX R32 Block OE R32.218 or R32.218 with this configuration, and VNX CDES 8.07 may result in data services going offline, making an NDU actually totally “D” disruptive.
As yet, there’s no published fix, and you’ll need to engage EMC support, and likely engineering to untangle the mess should you find yourself a victim.
You’d be expected to know if you have these DAE’s in your configuration, but here’s two easy ways to check.
Naviseccli; (via PowerShell)
What DAE information can you return ? Use the ‘getresume’ and -‘mp’ operator to return all the available DAE and DPE information. You’ll get the following output for each DAE present;
|
1 |
naviseccli -h arrayspa getresume -mp |
Obviously with lots of DAE’s on a system that’s a lot of data to filter through. To save time, let’s zero in exactly on what this is about and return only the ‘Codename‘ data. Remember we’re looking for “Voyager“. The codename will be in the ‘Assembly Name:’ value, so we’ll filter/grep it using the PowerShell Select-Pattern command.
|
1 |
naviseccli -h arrayspa getresume -mp | select-string -pattern 'Assembly Name:' |
…and it ain’t there, so we’re in the clear !
And of course, you could do this the boring, slow way with Unisphere, looking up each DAE’s properties;
So if you are using a “Voyager” DAE-60/DAE7S, hold off and wait. I suggest you subscribe to the product alerts and keep an eye on the ETA linked above. I’ll be certain to update this post and do my best to spread the word when a fix is published.
** Thanks to David Ring for the images.