This section explains how to design a system configuration.
L-Server Design
The procedure differs depending on whether the L-Server is physical or virtual.
For details, refer to the following:
For Physical L-Servers
For details, refer to "D.1 System Configuration".
For Virtual L-Servers
[VMware]
For details, refer to "E.1.1 System Configuration".
[Hyper-V]
For details, refer to "E.2.1 System Configuration".
[Xen]
For details, refer to "E.3.1 System Configuration".
[Oracle VM]
For details, refer to "E.4.1 System Configuration".
[KVM]
For details, refer to "E.5.1 System Configuration".
[Solaris Containers]
For details, refer to "E.6.1 System Configuration".
L-Platform Network Design
For details on L-Platform Network design, refer to "9.1 Defining the Network Environment".
Points to Keep in Mind when Setting up a Resource Orchestrator Environment
The maximum of managed servers can be registered in Resource Orchestrator is limited, and depends on the Resource Orchestrator license purchased.
For details on the limit of managed servers, refer to license documentation.
An error will occur when trying to register more managed servers than the above limit. This limit includes the spare servers used by recovery settings. However, it does not include VM guests.
Clustering software can be used on managed servers.
However, the following operations are not supported.
Managed Server Switchover
Backup and Restore
Use of the Windows Server 2008 BitLocker drive encryption function (Windows BitLocker Drive Encryption) is not supported.
If the admin server or managed servers are running under Windows Server 2008, do not encrypt the system disk using the BitLocker drive encryption function.
[Linux]
When installing an operating system on a PRIMEQUEST server, use legacy boot.
