It needs to be segregated if you compare the EMC storage with HP and IBM. We have to identify the reliability of the fiber channel ports. If this can be improved, it will be better for the end-user. There are issues if you manage through the sensory in the fiber channel.

We want to be able to manage things like storage, hosting, details about the mount point, and how much IOP is collapsed to which host in any single console. In addition, it will help us to identify and segregate the issues blocks.

Technical support needs improvement, as well as the engineering resources, who do the upgrades.

The graphic interface could be improved to be comparable with StorageWorks. 

Technical support is inadequate. 

I would like to see third-party storage management.

By the time they rolled out its predecessor SMC and Unisphere, the old ECC was trying to do too much within a large enterprise environment.

We were unhappy as no one from EMC heard our plea for assistance and it became expensive in terms of the license and the amount of resources it took.

Simply put, in the past the vendor support model was not broad enough to ensure every aspect of the ECC product worked efficiently.

After a few years of waiting for EMC to apply the fixes we wanted they were finally all addressed.

It needed improvement with its stability. Also, since it was agent-based communication, we always had to ensure that the agents were running on the servers all the time.

The support needs to be improved because I have found that even simple issues take a long time to be solved. It takes a very long time to close a case.

This product has sandbox capabilities and it works in some cases, but we would like to be able to apply it from the production environment.

The use of agents is not easy. The architectural design of using every single agent for every type of storage can be reviewed with the use of general proxies.

The general proxies also discover other vendors’ storage. This can be done with custom made scripts.