There have been some drive type of issues where we have to apply a new code level. Storage nodes kick certain drives until they act as though they have failed when really they haven't. You just have to reinsert them, then they go on about their happy way. It is a bug fixed in 11.0 of the code for Element OS/Solidfire. The option to pull in a config/text file to be used as input to the NDE process; rather than going through a lot of screens. The manual effort there is error-prone. This something NetApp engineering has been made aware of as a request and they say they're looking at that as a future enhancement. As far as SolidFire, if you use the GUI, you can only create one line at a time or device at a time. That's ludicrous. I referenced earlier today to the NetApp feedback panel that this needs to be fixed. They said, "Yep. I understand that." In terms of bandwidth and IOPS along with availability - we have not managed this environment long enough to put TIER1 environments under this umbrella; yet don't see why it couldn't handle the aforementioned especially if you create dedicated pods for those 'heavy hitters' (I'll just call it that.) Thus, in time we'll look for more deployments upon the converged infrastructure of NetApp.