The functional range available when a configured physical server or virtual machine is linked to an L-Server is as follows:
For the operation method for each function, refer to "Chapter 17 L-Server Operations".
Note
The range of available functions differs according to the role of the user and user group who operate it. For details on roles and available operations, refer to "5.1.2 Roles and Available Operations" in the "Design Guide CE".
When a configured physical server or virtual machine is linked to an L-Server using infrastructure administrator privileges, it is created as a normal L-Server. Create a new L-Server when you want to create an L-Server for infrastructure administrators.
L-Server Function | Type of L-Server | ||
|---|---|---|---|
Physical Server Using VIOM | Physical Server Using HBA address rename | Other Physical Servers | |
Starting | Yes | Yes | Yes |
Stopping | Yes | Yes | Yes |
Restarting | Yes | Yes | Yes |
Modifying specifications | Yes (*1) | Yes (*1) | Yes (*1) |
Modifying the basic information | Yes | Yes | Yes |
Collecting cloning images | Yes | Yes | No |
Backup and Restore | Yes | Yes | No |
Attaching and detaching disks | No | No | No |
Sharing disks between L-Servers | No | No | No |
Changing physical server usage | No | No | No |
Server redundancy | Yes (*2) | Yes (*2) | No |
Spare server configuration checks | Yes | No | No |
Alive monitoring (ping monitoring) | Yes (*3) | Yes (*3) | No |
Deploying the network information | No | No | No |
Admin LAN multiple subnet names | Yes | Yes | Yes |
Network redundancy, tagVLAN | No | No | No |
Modifying network resource settings | No | No | No |
Starting the console | Yes | Yes | No |
Batch power operations | Yes | Yes | Yes |
PXE boot | No | No | No |
iSCSI boot | No | No | No |
Allocating and releasing resources | No | No | No |
Blade chassis high availability | No | No | No |
Storage chassis high availability | No | No | No |
Disaster Recovery | No | No | No |
Deletion | Yes | Yes | Yes |
Releasing an L-Server | Yes | Yes | Yes |
*1: The following items can be modified.
Server redundancy, spare server selection methods, and spare server pools
Startup priority
*2: Configured physical servers for which server switchover has been already set cannot be managed. Enable server redundancy by modifying specifications.
*3: The settings of ping monitoring for physical servers are inherited. However, settings for ping monitoring cannot be configured using XML or the GUI as a physical L-Server.
L-Server Function | Type of L-Server | |
|---|---|---|
L-Server for Server Operation (*1, *2) | L-Server for Server/Storage Operation | |
Starting | Yes | Yes |
Stopping | Yes | Yes |
Restarting | Yes | Yes |
Migration of L-Servers between servers (migration) | Yes (*3) | Yes (*3) |
Modifying specifications | Yes (*4) | Yes (*4) |
Modifying the basic information | Yes | Yes |
Collecting cloning images | Yes (*5, *6, *7) | Yes (*5, *6, *7) |
Attaching and detaching disks | No | Yes (*5) |
Expanding disk size | No | Yes (*5, *7, *8, *9) |
Sharing disks between LServers | No | No |
Snapshot collection and restoration | Yes (*5, *7, *9) | Yes (*5, *7, *9) |
Allocating and releasing resources | Yes | Yes |
Starting the console | Yes (*5, *7, *8, *9 | Yes (*5, *7, *8, *9 |
Batch power operations | Yes | Yes |
Disaster Recovery | Yes | Yes |
Deleting an L-Server | Yes | Yes (*7) |
Releasing an L-Server | Yes | Yes |
*1: For the following cases, it will be the L-Server for server operation.
When disk configurations cannot be supported by an L-Server
When only Raw Device Mapping (RDM), a pass-through disk(Pass-through Disk), and a difference disk are included
When a configuration including device paths which are not described, Raw Device Mapping(RDM), a path through disk (Pass-through Disk), or difference disks are included
When the non-global zone of Solaris containers is not managed using BMC BladeLogic Server Automation [Solaris Zones]
In the case of the non-global zone of Solaris 11 [Solaris Zones]
When the virtual machine of OVM for SPARC is not managed using BMC Blade Logic Server Automation [OVM for SPARC]
For the following cases, it will be the L-Server for server and storage operation.
When using storage listed in "18.3.3 Manageable Storage", and the device paths or identifier information for all disks that have been allocated to the virtual machine are found in the following list
[VMware]
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
For virtual machines on VM host of VMware which is not managed by VM management software, power operations (starting, stopping or restarting) and modification of basic information (label/comment configurations) can be performed.
[Hyper-V]
SCSI:0:1 - SCSI:0:14
SCSI:1:0 - SCSI:1:14
SCSI:2:0 - SCSI:2:14
SCSI:3:0 - SCSI:3:14
[OVM for SPARC]
1 - 63
[Citrix Xen]
1, 4 - 15
[OVM for x86 3.2]
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
*2: In the following cases, only power control (starting, stopping, and restarting) of L-Servers is possible from the ROR console.
When the non-global zone of Solaris Zones is not managed using BMC BladeLogic Server Automation
In the case of a Solaris 11 non-global zone created in Solaris Zones
In the case of OVM for SPARC virtual machines
When the virtual machine of OVM for SPARC is not managed using BMC Blade Logic Server Automation
*3: Datastores or disk must be installed on a shared disk or it is necessary to share the disk resource among VM hosts.
*4: When CPU performance and memory size have been specified, the settings cannot be changed into "Unlimited".
*5: Solaris Zones are not supported.
*6: For a system disk, use the following device path or the thing of identification information:
[VMware]
SCSI:0:0
[Hyper-V]
IDE:0:0
[Citrix Xen] [OVM for x86 3.2]
0
When the above-mentioned thing is not used for the system disk, the L-Server creation process that accompanies cloning image deployment may fail. For Hyper-V, datastore must be installed on a shared disk.
*7: OVM for SPARC is not supported.
*8: Citrix Xen is not supported.
*9: OVM for x86 3.2 is not supported.
