User guide

Technical white paper | HP Enterprise Virtual Array Storage and VMware vSphere 4.x and 5.x configuration best practices
62
After the upgrade, all Vdisks will return “HSV450” instead of “HSV300” in the standard inquiry page response. This change in
PID creates a mismatch between LVM header metadata and the information coming from the Vdisk.
Note
A similar mismatch would occur if you attempted to use Continuous Access EVA to replicate from the EVA4400 to the
EVA8400.
When such a mismatch occurs, datastores are treated as snapshots and are not exposed to ESX. However, vSphere 4.x
allows you to force-mount or re-signature these snapshots to make them accessible. For more information, refer to the
following VMware Knowledge Base (KB) articles: 1011385 and 1011387.
Appendix E: Configuring VMDirectPath I/O for Command View EVA in a VM
This appendix describes how to configure VMDirectPath I/O in a vSphere environment for use with Command View EVA. An
example is presented.
Note
The configuration described in this appendix is only provided for the purposes of this example.
Sample configuration
Server configuration
Table E-1 summarizes the configuration of the vSphere server used in this example.
Table E-1. vSphere server configuration summary
Component
Description
ESX version
ESX 4.0 Build 164009
Virtual machine
VM2 (Windows Server 2008)
Local datastore
Storage 1
HBA
HBA1 (Q4GB)
QLogic Dual Channel 4 Gb HBA
Port 1: 5006-0B00-0063-A7B4
Port 2: 5006-0B00-0063-A7B6
HBA2 (Q8GB)
QLogic Dual Channel 8 Gb HBA
Port 1: 5001-4380-023C-CA14
Port 2: 5001-4380-023C-CA16
HBA3 (E8GB)
Emulex Dual Channel 8 Gb HBA
Port 1: 1000-0000-C97E-CA72
Port 2: 1000-0000-C97E-CA73