When using a Virtual Volume, set the VVOL access path (access path for Virtual Volume) between VM hosts and the ETERNUS Disk storage system.
Regardless of whether the access path is set or not, be sure to set the VVOL access path.
The VVOL access path operations are as follows:
Note
Operate the VVOL access path from Web Console. The "storageadm" command cannot be used for operation.
Point
Advanced knowledge is required to use the VMware vSphere Virtual Volumes function with the ETERNUS Disk storage system in which the maximum pool capacity has been changed. For this reason, when using the VMware vSphere Virtual Volumes function, it is recommended that you operate the system without changing the configuration for the maximum pool capacity of the ETERNUS Disk storage system.
If you use the VMware vSphere Virtual Volumes function with the ETERNUS Disk storage system in which the maximum pool capacity has been changed, enable the VMware vSphere Virtual Volumes function using ETERNUS CLI before creating a VVOL access path. Refer to the ETERNUS Disk storage system manual for information on the command names and syntax of ETERNUS CLI.
The icons and meanings used for the access path are also used for the VVOL access path state. For icon states and their meanings, refer to "Access Path Status Display" in the Storage Cruiser Operation Guide.
Creation of VVOL Access Path
Refer to "VVOL Access Path Setting" in the Web Console Guide for creation of a VVOL access path.
In the Fibre Channel environment, you can set the ETERNUS Disk storage system host affinity and FC switch zoning. In the iSCSI environment, you can set the ETERNUS Disk storage system host affinity.
Point
As the Virtual Volume does not use the affinity group, the affinity group does not need to be created in advance. The affinity group is required when setting the access path.
When booting the VM host from a SAN or when allocating a volume that configures VMFS datastore, set both the access path and VVOL access path.
In an environment where both the access path and VVOL access path are set, if only one of the access paths is deleted, FC switch zoning is not deleted.
When setting multiple VVOL access paths between one VM host and one ETERNUS Disk storage system, they are set automatically as multipath.
The use of a host group varies depending on the firmware version of the ETERNUS Disk storage system as shown below:
If the storage device is an ETERNUS DX S3 series, an ETERNUS AF S2 series, an ETERNUS AF series, or an ETERNUS DX200F with a firmware version V10L50 or later, or an ETERNUS DX S5/S4 series, an ETERNUS AF S3 series
A VVOL access path can be configured for the ports of an ETERNUS Disk storage system that are registered in a host group. However, the ports are removed from the host group for the ETERNUS Disk storage system that is connected to the VM host for which the access path is set.
If the storage device is an ETERNUS DX S3 series, an ETERNUS AF S2 series, an ETERNUS AF series, or an ETERNUS DX200F with a firmware version earlier than V10L50
A VVOL access path can be configured for the ports of an ETERNUS Disk storage system that are not registered in a host group. When configuring a VVOL access path for the ports of an ETERNUS Disk storage system that are registered in a host group, remove the settings that are registered for the ports of an ETERNUS Disk storage system from the host group in advance.
Display of VVOL Access Path Usage State
The statuses of VVOL access path are as follows. The status is displayed in the VVOL Function column on the Web Console Access Path List screen.
Character String Displayed in VVOL Function column | Meaning |
|---|---|
Enable(Used) | VVOL access path in use (path that the virtual machine is operating) |
Enable(Unused) | VVOL access path not in use (path that the virtual machine is stopping) |
Disable | Non VVOL access path |
Point
A Virtual Volume does not use an affinity group. For this reason, when only the VVOL access path is set, a hyphen (-) is displayed for the Affinity Group column on the Web Console Host Affinity List screen.
Inheritance of VVOL Access Path
In the Fibre Channel environment, when exchanging the VM host HBA, access path inheritance work is necessary after replacement.
After replacing the HBA, perform work according to the HBA state after performing the Reload Conf. operation on the target VM host.
Note
In the case of iSCSI environment, set the IP address and iSCSI name that were used prior to replacement in the HBA after replacement is completed. Access path inheritance work is not required.
With the access path inheritance work, both the access path and VVOL access path can be inherited.
See
Refer to "Post-replaced HBA State Is "Changed"" in "Replacing Supported Device Components" in the Storage Cruiser Operation Guide for procedures.
VVOL access path is inherited using the following procedure:
Delete the VVOL access path, referring to "Delete VVOL Access Path" in the Web Console Guide.
Change the access path if the access path is set, referring to "Post-replaced HBA State Is "Unknown"" in "Replacing Supported Device Components" in the Storage Cruiser Operation Guide.
Recreate the VVOL access path, referring to "VVOL Access Path Setting" in the Web Console Guide.
Deletion of VVOL Access Path
Refer to "Delete VVOL Access Path" in the Web Console Guide for VVOL access path deletion procedures.
Point
In environments in which multipath is not configured, the VVOL access path in use (path that the virtual machine is operating) cannot be deleted.
In environments in which multipath is configured, VVOL access paths can be deleted until there is only one VVOL access path remaining.
In an environment in which both a access path and a VVOL access path are set, if only one of the access paths is deleted, FC switch zoning is not deleted. In both the access path and the VVOL access path are deleted, zoning is deleted.
