User guide
Technical white paper | HP Enterprise Virtual Array Storage and VMware vSphere 4.x and 5.x configuration best practices
7
Using Command View EVA
Command View EVA can manage an array using one of the following methods:
• Server-based management (SBM) – Command View EVA is deployed on a standalone server that has access to the EVA
storage being managed.
If desired, you can run Command View EVA within a VM, allowing you to clone this VM and use it as a template that can be
quickly redeployed as needed, with minimal reconfiguration required.
When running Command View EVA in a VM, the following modes are supported:
– Virtualized SCSI mode – The Command View EVA instance can only view the active path to LUN 0 on a single controller.
This mode is enabled by default when you install Command View EVA 9.2 or later.
– VMDirectPath mode – The Command View EVA instance bypasses the virtualization layer and can directly manage the
EVA storage. This mode is supported on Command View EVA 9.3 or later.
• Array-based management (ABM) – For supported EVA models, Command View EVA can be deployed on the array’s
management module.
Running Command View EVA within a VM
Your ability to deploy Command View EVA within a VM may be impacted by the following:
• EVA model
• Command View EVA version being used
• Availability of a host bus adapter (HBA) that can be dedicated to the VM
Table 1 compares the options for deploying Command View EVA in a VM.
Table 1. Comparing requirements for Virtualized SCSI and VMDirectPath modes
Requirement
Virtualized SCSI
VMDirectPath
Minimum EVA firmware
XCS 09534000 or later
All
Minimum Command View EVA
software
9.2 or later
9.3 or later
Dedicated HBA required
No
Yes
Compatible EVA models
EVA8400
EVA6400
EVA4400
EVA4400-S
P6300
P6500
EVA4100
EVA6100
EVA8100
EVA8400
EVA6400
EVA4400
EVA4400-S
P6300
P6500
Command View EVAPerf support
No
Yes
SSSU support
Yes
Yes
VMware vMotion support
Yes
No
Caveats for installing Command View EVA in a VM
If you are installing Command View EVA in a VM, take care where you deploy the VMware virtual disk hosting the operating
system on which you plan to install Command View EVA. If you were to deploy this virtual disk on the same array that you
intend to manage with the Command View EVA instance, any issue that causes the EVA array to be inaccessible would also
impact your ability to identify this issue.
In general, when deploying Command View EVA in a VM, use a virtual disk on the vSphere host’s local datastore, if available.
If you must deploy the Command View EVA VM on the SAN, then consider deploying two or more instances on two or more
storage systems to increase availability in the event of an array failure.