Filter
Top Products
Consult the HP 3PAR Management Console Users Guide and the HP 3PAR Command Line Interface
Reference for complete details on exporting volumes and available options for the HP 3PAR OS
version that is being used on the HP 3PAR StoreServ Storage. These documents are available on
the HP BSC website:
http://www.hp.com/go/bsc
NOTE: The commands and options available for creating a virtual volume may vary for earlier
versions of the HP 3PAR OS.
Discovering LUNs on VMware ESX Hosts
This section provides tips for discovering LUNs that are being utilized by the ESX host.
Once the host is built, the preferred method for configuring and managing the use of the ESX host
is through a VI/vSphere client Management Interface and VMware vCenter Server.
New VLUNs that are exported while the host is running will not be registered until a Bus Rescan
is initiated. This may be performed from the VI/vSphere client Management Interface. If failover
support is utilized (recommended), view all LUNs and their respective paths using the menu from
the ESX (Configuration tab
→
Storage Adapter).
Disks can be added to a virtual machine with the virtual machine powered up. However, to remove
a disk, the virtual machine must be powered off. This is a limitation of ESX.
The maximum number of LUNs on a single ESX HBA port is 256, and 256 total LUNs on the ESX
host. Internal devices, such as local hard drives and CD drives, are counted as a LUN in the ESX
host LUN count.
Removing Volumes
After removing a VLUN exported from the HP 3PAR StoreServ Storage, perform a ESX host bus
adapter rescan. ESX will update the disk inventory upon rescan. This applies to both Fibre Channel
and iSCSI.
It is advisable to remove the disk/LUN from the virtual machine inventory, detach from the ESX
host, and then remove it from the HP 3PAR StoreServ Storage using the removevlun and
removevv HP 3PAR OS CLI commands or using the HP 3PAR Management Console. If a LUN is
not detached but is removed from the HP 3PAR StoreServ Storage, it appears as a device in an
error state, and is cleared after an ESX host reboot.
Discovering LUNs on VMware ESX Hosts 81