Manageable storage differs depending on whether a physical server or a virtual machine is used.
For Physical Servers
When using the hardware listed in "Table-Required Hardware Conditions for Agents" in "6.2.1 All Editions" in the "Overview" and in the following cases, servers and storage can be managed. In other cases, only servers can be managed. EMC storage and Storage Servers running FalconStor NSS cannot be managed.
When using the ETERNUS storage or NetApp storage listed in "Table-Storage Units that can be Connected with L-Servers on Physical Servers" in "6.2.3 Cloud Edition" in the "Overview"
When using "Table-Fibre Channel Switches which can be used when Connecting Storage Units with L-Servers on Physical Servers" in "6.2.3 Cloud Edition" in the "Overview"
When storage units are managed using the storage management software listed in "6.1.2.4 Required Software" in the "Overview"
When one AffinityGroup is operated for one physical server
The HBA port for the physical server must be the same as the HBA port that is configured in storage and is accessible to LUNs using that physical server.
For Virtual Machines
Settings differ according to the server virtualization software being used.
Disks shared between two or more VM hosts cannot be managed with Resource Orchestrator.
In the following cases, both servers and storage can be managed.
[VMware]
Virtual machines are managed using VMware and vCenter Server
Datastores are used, and the datastores are displayed in the storage tree as virtual storage
SAN storage or NAS storage supported by VMware, excluding built-in disks on the server and iSCSI storage, is used
The following device paths are used for data disks
SCSI:0:1 - SCSI:0:6
SCSI:0:8 - SCSI:0:14
SCSI:1:0 - SCSI:1:6
SCSI:1:8 - SCSI:1:14
SCSI:2:0 - SCSI:2:6
SCSI:2:8 - SCSI:2:14
SCSI:3:0 - SCSI:3:6
SCSI:3:8 - SCSI:3:14
Note
When using Raw Device Mapping, or when using a device path other than those listed above, only servers can be managed.
For disks using any other device path, assign 56 or higher as the disk number.
When collecting a cloning image for deploying an L-Server, use SCSI:0:0 for the system disk.
[Hyper-V]
Virtual machines are managed using SCVMM
MSFC has been added to VM hosts
Cluster disks are configured as shared cluster volumes, and the shared volumes are displayed in the storage tree as virtual storage
A SAN volume has been configured as a cluster disk
SAN storage supported by Hyper-V, excluding built-in disks on the server and iSCSI storage, is used
The following device paths are used for data disks
SCSI:0:1 - SCSI:0:14
SCSI:1:0 - SCSI:1:14
SCSI:2:0 - SCSI:2:14
SCSI:3:0 - SCSI:3:14
Note
When using pass-through devices or difference disks, or when using a device path other than those listed above, only servers can be managed.
For disks using any other device path, assign 60 or higher as the disk number.
When collecting a cloning image for deploying an L-Server, use IDE:0:0 for the system disk.
Collecting a cloning image from a virtual machine that is not highly available is not supported.
[Solaris Zones (Solaris 11)]
The following device paths or identifier information are used for data disks
/rcx/disk001 - /rcx/disk063
[OVM for SPARC]
The following device paths or identifier information are used for data disks
1 - 63
[Citrix Xen]
The storage repository is used and the storage repository is displayed on the storage tree as virtual storage.
The following device paths or identifier information are used for data disks
1, 4 - 15
Note
When collecting a cloning image for deploying an L-Server, use 0 for the system disk.
[OVM for x86 3.x]
The storage repository is used and the storage repository is displayed on the storage tree as virtual storage.
The following device paths or identifier information are used for data disks
When HVM (Hardware Virtualized Machine) is used: 2-3
When PVM (Para-Virtualized Machine) is used: 2-103
When PVHVM (Para-Virtualized Hardware Virtual Machine) is used: 2 - 106
Note
When collecting a cloning image for deploying an L-Server, use 0 for the system disk.
Note
Disks which are created in virtual storage which is not registered in the storage pool can also be operated. When managing the amount of resources in the virtual storage, register the virtual storage in the storage pool.
