Command View EVA supports a standby configuration whereby an array can be managed by multiple Command View EVA stations simultaneously, with only one of them actively managing a specific array at a time. Discovery will include both the EVA array being actively managed and the array not being actively managed (Standby Command View station). In such cases, there are limitations to the information that can be gathered, based upon whether both the managed and the unmanaged (standby) arrays are discovered by the management server.

If only the unmanaged array is discovered, only the top level array information can be collected.

If both the managed and the unmanaged (standby) arrays are discovered using the required version of Command View EVA with the new built-in provider, both the managed and unmanaged arrays must remain in the same discovery group. They can be moved to a different discovery group, but both must remain together in the same discovery group.

EVA Metrics and Considerations

Be aware of the following considerations relating to the collecting metrics and general usage considerations:

•EVA performance data cannot be collected for EVA arrays that have controller passwords set via the Operator Control Panel (OCP).

•Only EVA volumes that are mapped to a host have associated performance data.

•The management server will not be able to gather host port metrics if the EVA controller has two switches attached to it with the same DomainID and the same switch port number is used in each switch.

EVAPerf Considerations

Be aware of these EVAPerf Data Collector service considerations:

•EVAPerf Data Collector service can sometimes crash, especially in larger environments. This is less likely with EVAPerf 7.0.1. Restarting the service will enable performance data collection to succeed. Consider changing the service startup parameters to “automatic” and “restart on failure”.

•If the total number of vdisks configured on the EVA exceeds 512 using EVAPerf versions prior to v7.0.1, some mapped vdisks may not have any metrics associated with them.

•Occasionally, a physical disk might not have reporting because the EVAPerf Data Collector returns an unknown identifier for it.

•Vdisk and physical disk metric data viewed in the EVAPerf CLI on the Command VIew EVA server might appear inconsistent with the management server’s data. This is due to an EVAPerf CLI situation in which only point-in-time samples are returned for sample intervals greater than 30 seconds (this is for all VCS versions).

•Socket connections between the management server and the EVAPerf Data Collector service on port 860 are not immediately closed after stopping the EVA performance collectors in the management server, or when un-licensing EVA arrays for performance data collection in the management server. However, the connection will eventually time out and be closed after the default idle time for the connection expires. In these situations, although the connections are still open, no I/O occurs over the connection.

HP Storage Essentials SRM 6.0 User Guide 393