Prerequisites for Storage when Creating a Physical L-Server
L-Servers support SAN boot and iSCSI boot configurations.
When using a physical server as an L-Server, it is necessary that connection using VIOM or HBA address rename is supported. For details on connection using VIOM or HBA address rename, refer to "10.1 Deciding the Storage Environment" and "10.2 Configuring the Storage Environment".
Usage methods of VIOM and HBA address rename differ depending on the hardware of managed servers used to configure a physical L-Server.
Blade Servers
Use VIOM.
Rack Mount Servers
Use HBA address rename.
For L-Server SAN storage paths and iSCSI storage paths, multipaths (two paths) are supported.
Configurations with two or less HBA ports on managed servers are supported.
When using the MMB firmware for which Fibre Channel card information cannot be obtained by blade servers, only configurations where Fibre Channel cards are mounted in expansion slot 2 are supported. The servers for which the information of Fibre Channel cards can be obtained are as follows:
PRIMERGY BX900 series servers
4.70 or later
PRIMERGY BX400 series servers
6.22 or later
In the case of blade servers, please do not set the following parameters during setup of VIOM.
WWN Address Range
MAC Address Range
Regarding Storage Configuration
Decide the storage configuration necessary for the system.
The storage configuration when creating a physical L-Server is indicated below.
When using a Fibre Channel connection, multiple storage units can be connected to a single L-Server (when VIOM connections are not supported, only one storage unit can be connected). When using an iSCSI connection, one storage unit can be connected to a single L-Server.
Sharing of storage between multiple L-Servers is supported.
Note
Local disks are not supported. Do not connect local disks.
For details on required VM management software and storage management software, refer to "2.4.2.2 Required Software".
For details on supported storage units and Fibre Channel switches, refer to "2.5 Hardware Environment".
The disk configurations supported by Resource Orchestrator are as follow:
L-Server System Disk | L-Server Data Disk |
|---|---|
SAN storage | SAN storage |
iSCSI storage (*1, *2) | iSCSI storage (*1, *3) |
*1: Available when ETERNUS storage and NetApp storage are used.
*2: When using Linux for a physical L-Server, and iSCSI storage for a system disk, it is not possible to create an L-Server using a cloning image.
*3: When creating an L-Server, iSCSI storage is not allocated to the L-Server as a data disk. Manually allocate the iSCSI storage to the L-Server, after starting the L-Server. Attaching or detaching iSCSI storage to or from an L-Server cannot be performed using Resource Orchestrator. Perform those operations manually. For details on data disk allocation for iSCSI storage, refer to "Information- Physical L-Server Data Disk for iSCSI Boot".
Information
Physical L-Server Data Disk for iSCSI Boot
When Using ETERNUS Storage (Excluding ETERNUS VX700 series)
Using storage management software, the data disk can be accessed from managed servers by defining LUNs of the iSCSI boot disk and of the data disk in the same Affinity group.
When Using NetApp Storage
Using storage management software, the data disk can be accessed from managed servers by defining LUNs of iSCSI boot disk and of the data disk in the same igroup.
Configure iSCSI Storage Environments
When using iSCSI boot on physical L-Servers, create LUNs that can be connected to L-Servers in advance.
For details, refer to "D.3.3 When Using ETERNUS Storage" and "D.3.4 When Using NetApp FAS Storage".
Dynamic LUN Mirroring Settings
For storage units that support dynamic LUN mirroring, refer to "Table 2.67 Storage Units that can be Connected with L-Servers on Physical Servers".
If dynamic LUN mirroring is to be used on the physical L-Server, make settings so that copying between ETERNUS storage machines is made possible.
For details on the configuration method, refer to the "ETERNUS SF AdvancedCopy Manager Operator's Guide for Copy Control Module".
