The following functions are provided by Resource Orchestrator.
Function | Description | Benefits | Target resource | ||
|---|---|---|---|---|---|
Physical OS | VM host (*1) | VM guest (*1) | |||
Monitoring | A function for monitoring resource statuses of servers and displaying if the status is normal or not by using the GUI. | Helps identify the cause of a failure and determine its impact on servers, thereby streamlining hardware maintenance. | Yes (*2) | Yes (*2) | Yes |
Power control | A function for turning servers ON or OFF. | Enables remote control of a managed server's power state without having direct access to it. This simplifies periodic maintenance tasks that involve power control operations. | Yes | Yes | Yes |
Backup and restore (*3, *4) | Creates system image backups of servers that can be easily restored when needed. System images are centrally stored on a disk on the admin server. | Creating backups before any configuration change, OS or software installation, or patch application can drastically reduce the time to restore a server to its original state when hardware or software problems occur. | Yes (*5) | Yes (*5, *6) | No |
Hardware maintenance | Functions to simplify hardware replacement. | Lightens the workload associated with hardware replacement and reduces the risk of operational errors. | Yes | Yes | - |
Server switchover (*4) | Recover applications upon hardware failure by switching over primary servers with pre-assigned spare servers. | Shortens and simplifies the recovery procedure in the event of server failure. | Yes (*7) | Yes (*7) | No |
Cloning (*3, *4) | Creates a cloning image of a reference server and deploys it to other managed servers. Cloning images are centrally stored on a disk on the admin server. | Simplifies OS and software installation when servers are added. Allows servers with identical OS and software configurations to share common backups. | Yes | No | No |
Yes: Supported
No: Not supported
-: Not applicable
*1: For details on the functions available depending on the server virtualization software used for VM hosts and VM guests, refer to "9.1 Deciding Server Virtualization Software" for details.
*2: Depending on the hardware being used, this feature may or may not be available.
For details, refer to "Functions Available for Agents" in "6.2.1 All Editions" in the "Overview".
*3: Not necessary when ServerView Deployment Manager shares the same subnet (admin LAN).
*4: It is necessary to create Windows PE in advance. For details, refer to the "Windows PE Creation Script Guide".
*5: Back up and restoration of managed servers that are in clusters is not supported.
However, it is possible to back up and restore managed servers that have been removed from clusters beforehand.
Back up and restoration of a VM host is possible when both of the following conditions are satisfied:
- The target VM host is not in a cluster.
*6: When backing up a VM host containing VM guests on its own boot disk, behavior differs according to the server virtualization product used. For details, refer to "9.2.2 Functional Differences between Products".
*7: Performing server switchover of managed servers that are in clusters is not supported.
Function | OS (Physical OS, VM Host) | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Windows | Linux | VMware | Solaris | Xen | KVM | ||||||||
Windows | Hyper-V (*1, *2) | Red Hat/Oracle | SUSE (*3) | vSphere 4 (*4, *5, *6) | Infrastructure 3 | Solaris | Solaris Zones | OVM for SPARC | Citrix | Red Hat | Red Hat | ||
Monitoring | Yes | Yes | Yes (*7) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | |
Power control | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | |
Backup and restore (*8) | Yes (*9) | Yes (*9) | Yes (*10) | Yes (*11) | No | Yes | No | No | No | Yes (*11, *12) | Yes (*13) | Yes (*13) | |
Server switchover (*8) | Backup and restore method | Yes (*9) | Yes (*9) | Yes | Yes (*14) | No | Yes | No | No | No | Yes (*15) | Yes | Yes |
HBA address rename method | Yes (*9) | Yes (*9) | Yes | Yes (*14) | Yes | Yes | No | No | No | Yes (*15) | Yes | Yes | |
VIOM server profile switchover method | Yes (*9) | Yes (*9) | Yes | Yes (*14) | Yes | Yes | No | No | No | Yes | Yes | Yes | |
ISM profile switchover method | Yes (*9) | Yes (*9) | Yes | Yes (*14) | Yes | Yes | No | No | No | Yes | Yes | Yes | |
Storage affinity switchover method | No | No | No | No | No | No | Yes (*16, *17, *18, *19, *20) | Yes (*16, *17, *18, *19, *20, *21) | Yes (*17, *19, *20, *21, *22, *23) | No | No | No | |
Ping monitoring (*24) | Yes | Yes | Yes | Yes | Yes (*25) | Yes | Yes (*17) | Yes (*17) | Yes (*17) | Yes | Yes | Yes | |
Cloning (*8) | Yes (*26) | No | Yes (*10) | Yes (*11, *27) | No | No | No | No | No | No | No | No | |
VLAN settings (*28) | Yes | Yes | Yes | Yes | Yes | Yes | No | No | No | Yes | Yes | Yes | |
Pre-configuration | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes (*29) | Yes | Yes | Yes | |
Yes: Supported
No: Not supported
*1: Only supported when the manager is running on Windows.
*2: VM guest migrations and VM maintenance mode settings require Microsoft(R) System Center Virtual Machine Manager 2008 R2 or later. In addition, PowerShell 2.0 or later should be installed on the manager.
*3: Disable the use of persistent network device names.
*4: With BIOS time settings, it is only possible to set UTC (Coordinated Universal Time) for VMware ESX/ESXi of VMware vSphere 4 or later version servers, and local time for Windows servers. Therefore, as the same settings cannot be made, operation with spare servers being shared between VMware ESX/ESXi of VMware vSphere 4 and later versions of servers, and Windows servers is not possible.
*5: When upgrading from VMware Infrastructure 3, system images of VM hosts that were collected prior to the upgrade will be available after the upgrade is complete. However, even if system images from before the upgrade are used for server switchover (using the backup and restore method), the VM hosts will not operate properly. Be sure to release spare server settings for server switchover using the backup and restore method before performing upgrades. It is recommended to delete all system images collected before change, unless those images are specifically needed.
*6: Management of VM guests with VMware Fault Tolerance enabled is not supported by Resource Orchestrator.
*7: Oracle Enterprise Linux is reported as Red Hat Enterprise Linux.
*8: It is necessary to create Windows PE in advance. For details, refer to the "Windows PE Creation Script Guide".
*9: You must have a volume license for the version of Windows to be installed on managed servers by Resource Orchestrator. With Windows Server 2012 or later, OEM license can be applied. However, OEM licenses are also necessary for restoration target servers, spare servers, and servers after replacement.
*10: When performing operations using Resource Orchestrator, ensure that the file system is NTFS, ext3, ext4, or LinuxSwap.
*11: When using the backup and restore functions, ensure that the file system is an ext3 file system.
*12: When performing restoration using Resource Orchestrator, do so using hardware with the same NIC configuration as when the backup was made. When performing restoration after NICs have been replaced or reconfigured, reinstall XenServer referring to the manual for Citrix XenServer.
*13: VM maintenance mode is not supported by this server virtualization product. As a result, system images can be backed up and restored without having to set or release the target VM hosts from VM maintenance mode.
*14: When using the backup and restore method of Resource Orchestrator for server switchover, configure the same SCSI WWID for the source and target.
*15: XenServer 5.7 or later cannot be used. When using the server switchover functions, select a profile switchover method.
*16: When configuring the OS file system using UFS, enable logging in the mount settings for UFS file systems in order to prevent fsck execution at startup. Refer to the Solaris System Administration Guide for details on the UFS logging settings.
*17: Recovery, including server switchover, cannot be performed for PRIMEQUEST, SPARC Enterprise Partition Models with divided areas, or SPARC M10/M12 in Building Block configurations.
*18: When using SPARC M10/M12, perform server switchover in the factory-default configuration using the primary server and the spare server.
*19: When using SPARC M10/M12, the configuration information saved in the XSCF of the spare server may be overwritten with the configuration information saved in the XSCF of the primary server, while performing switchover.
*20: Only MPxIO can be used as the multipath configuration for storage.
*21: In cases where zones are created in ZFS storage pools, server switchover can be performed on Solaris 11.1 or later.
*22: Oracle VM Server for SPARC 3.0/3.1 is supported. However, server switchover is not possible when using Oracle VM Server for SPARC 3.1 and an I/O domain to which physical I/O is allocated for each PCIe end point device.
*23: When using SPARC M10/M12, execute switchover with domain configuration information other than the factory-default saved on the primary server.
*24: For details on how to configure these settings, refer to "Chapter 8 Configuring Monitoring Information" in the "Setup Guide VE".
*25: For VMware ESXi, this function is not supported.
*26: You must have a volume license for the version of Windows to be installed on managed servers by Resource Orchestrator.
*27: Auto-configuration of network parameters cannot be used.
*28: Only supported for blade models.
*29: Agent registration information of guest domains is not supported.
Function | Description | Benefits |
|---|---|---|
Power control | A function for turning chassis ON or OFF. | Enables remote control of a chassis' power state without needing to connect to its management blade. This simplifies periodic maintenance tasks that involve power control operations. |
Function | Description | Benefits |
|---|---|---|
Pre-configuration | Systems made up of multiple servers can be easily configured or modified using the pre-configuration function to import a pre-defined system configuration file. | Prevents setup mistakes by performing numerous setup operations in a single action. |
Backup and restore | Backs up or restores a Resource Orchestrator installation. | Performing backups after configuration changes are made in Resource Orchestrator enables prompt recovery of the admin server in case its internal data is damaged due to administration mistakes or other problems. |
Function | Description | Benefits | LAN Switch Blades (*1) | LAN Switch | |||||
|---|---|---|---|---|---|---|---|---|---|
Switch Mode | IBP Mode | End-Host Mode | Converged Fabric Mode | DCB SW (*2) | FEX Nexus B22 (*3) | ||||
Monitoring | Monitors LAN switches and displays their statuses (normal or error) graphically. | Simplifies identification of the cause and impact of LAN switch failure on servers and speeds up hardware maintenance. | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
NetworkViewer | Helps visualize and relate physical networks (between servers and LAN switch blades) together with virtualized networks (from VLANs or virtual switches used in server virtualization software). | Automatically detects and displays network connections (topology) and link statuses for different kinds of resources (network equipment or server virtualization software). | Yes | Yes | Yes | Yes (*4) | Yes | Yes (*4) | Yes |
VLAN settings | Automates VLAN settings (port VLAN or tagged VLAN) on LAN switches adjacent to servers. | Simplifies the VLAN configuration of LAN switches when adding new servers. During automatic recovery of a failed server, VLANs are automatically reconfigured to preserve connectivity and avoid manual network reconfigurations. | Yes | No | Yes | No | Yes (*5) | No | No |
Port group settings | Automates port group settings on LAN switch blades in IBP mode during server switchover. | Reduces the number of steps necessary to recover the network configuration of a failed server. | No | Yes | No | No | No | No | No |
Restore | Restores a LAN switch to its most recent VLAN configuration. | Restores the VLAN configuration on a replaced LAN switch to the configuration that was active before replacement. | Yes | No | Yes | No | Yes (*5) | No | No |
Yes: Supported
No: Not supported
*1: For PRIMERGY BX600 LAN switches, refer to the "switch mode" column.
*2: DCB SW is recognized as the omitted description indicating when using or not using VCS mode for LAN switch blade PY CB DCB SW 10Gb 18/6/6.
*3: FEX Nexus B22 is recognized as the omitted description indicating LAN switch blade PY CB 10Gb FEX Nexus B22.
*4: Only internal network connections (topology) are displayed.
*5: VLANs can only be configured for the internal ports.
Function | Description | Benefits |
|---|---|---|
Power consumption monitoring (*) | Monitors power consumption trends for resources equipped with power monitoring capabilities, or resources connected to power monitoring devices (PDU or UPS). Collects and outputs power consumption data over a given period. | This function can be used to measure the effectiveness of environmental policies and cost-saving initiatives on power consumption. |
* Note: For details on supported devices, refer to "2.5 Hardware Environment". For VMware ESXi, this function is not supported.
Function (*) | Description | Benefits |
|---|---|---|
Migration of VM guests between servers | Migrates a VM guest from one physical server to another. | Facilitates optimization of VM guest deployments according to server load or planned maintenance. |
VM maintenance mode control | Sets (or releases) VM hosts to (or from) a specific state that allows safe server maintenance. | VM hosts can be easily set out of and back into operation. |
VM Home Position setting, migration and clearing | Functions for setting, migrating, and clearing VM Home Positions. | Even if VM guests are migrated to different locations, they can be easily returned to their original locations. |
* Note: Available functions may vary according to the server virtualization software used. For details, refer to "9.1 Deciding Server Virtualization Software".
