Manageable storage differs depending on whether a physical server or a virtual machine is used.
For physical servers
Servers and storage can be managed when using the hardware listed in "Table 2.64 Required Hardware" in "2.5 Hardware Environment" in the "Design Guide CE", and in the following cases. In other cases, only servers can be managed.
When using the ETERNUS storage or NetApp storage listed in "Table 2.67 Storage Units that can be Connected with L-Servers on Physical Servers" in "2.5 Hardware Environment" in the "Design Guide CE"
When using "Table 2.68 Fibre Channel Switches which can be used when Connecting ETERNUS Storage, NetApp Storage, EMC CLARiiON Storage, EMC Symmetrix DMX Storage, and EMC Symmetrix VMAX Storage with L-Servers on Physical Servers" in "2.5 Hardware Environment" in the "Design Guide CE"
When storage units are managed using the storage management software listed in "2.4.2.2 Required Software" in the "Design Guide CE"
When one AffinityGroup is operated for one physical server
The HBA port for Physical server need to be the same as the HBA port that is configured in Storage and with which can be accessible to LUNs using by that Physical server.
For Virtual Machines
Settings differ according to the server virtualization software being used.
In the following cases, both servers and storage can be managed.
[VMware]
Virtual machines are managed using VMware and vCenter Server
Datastores are used
SAN storage supported by VMware, excluding built-in disks on the server and iSCSI storage, is used
SCSI:0:0 is used for the system disk
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 AM
SCSI:2:0 - SCSI:2:6
SCSI:2:8 - SCSI:2:14 AM
SCSI:3:0 - SCSI:3:6
SCSI:3:8 - SCSI:3:14 AM
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
A cluster disk has been configured as a shared cluster volume
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
IDE:0:0 is used for the system disk
The following device paths are used for data disks
SCSI:0:1 - SCSI:0:14
SCSI:1:0 - SCSI:1:14 AM
SCSI:2:0 - SCSI:2:14 AM
SCSI:3:0 - SCSI:3:14 AM
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.
