Resource Orchestrator is server management software that improves the usability and availability of server systems. It uniformly manages physical servers as well as virtual servers created using server virtualization software (VMware and others).
The level of functionality provided by Resource Orchestrator differs depending on the managed hardware environment.
For details, refer to "Functions Available for Agents" in "6.2.1 All Editions" in the "Overview".
This section explains some of the features provided by Resource Orchestrator.
Integrated management of physical and virtual servers
Resource Orchestrator provides an integrated management console for environments composed of physical and virtual servers. It helps administrators manage server configurations, monitor hardware failures, and determine the cause and impact of system errors by automatically detecting and displaying the following information.
Resource Orchestrator provides a tree-based view of chassis and server hardware and their operating systems (physical OS, VM host, or VM guest).
This enables easy confirmation and tracking of relationships between chassis, servers, and operating systems.
Resource Orchestrator monitors server hardware and displays icons representative of each server's status.
Resource Orchestrator also allows administrators to manage both physical and virtual servers in a uniform manner. Once registered, resources can be managed uniformly regardless of server models, types of server virtualization software, or differences between physical and virtual servers.
Auto-Recovery of failed servers
The function allows failed applications to automatically be recovered onto an available spare server by pre-allocating spare servers to managed servers.
Depending on the server's boot method, one of the four following switchover methods can be used to recover applications on a spare server:
Backup and restore
This method is used in local boot environments where servers boot from an internal disk. Backing up the system disk of a primary server in advance allows automatic restoration and startup of the spare server when the primary server fails.
HBA address rename
This method is used in SAN boot environments where servers start from boot disks located in SAN storage arrays. If the primary server fails, its World Wide Name (WWN) is inherited by the spare server, which then automatically starts up from the same SAN disk. This is made possible by the I/O virtualization (*) capabilities of the HBA address rename function, which is able to dynamically reconfigure the WWN of an I/O adapter (HBA).
VIOM server profile exchange method
This method is used in environments where servers start from boot disks located in SAN storage arrays or on a storage device connected to the LAN. If the primary server fails, the World Wide Name (WWN) and MAC address, boot configuration, and network configuration set in its server profile are inherited by the spare server, which then automatically starts up from the same boot disk. This is made possible by the I/O virtualization (*) capabilities of the HBA address rename function, which is able to dynamically reconfigure the WWN of an I/O adapter (HBA).
For details on server profiles, refer to the ServerView Virtual-IO Manager manual.
* Note: Refer to "I/O Virtualization".
Storage affinity switchover method
This method is used in SAN boot environments where servers start from boot disks located in SAN storage arrays. If the primary server fails, its switch zoning and host affinity configurations set in the fibre channel switch and the SAN storage using ESC are inherited by the WWN (World Wide Name) of the spare server, which then automatically starts up from the same SAN disk.
The following LAN switch settings can also be exchanged between primary and spare servers during server switchover. This feature supports the backup and restore, HBA address rename, and VIOM server profile exchange methods.
VLAN
Port groups (For PRIMERGY BX900/BX400 LAN switch blades operating in IBP mode)
Several servers can share one or more common spare servers, irrespective of the kind of servers used (physical or virtual), or the applications that are running on them.
Spare servers can also be shared between physical and virtual servers. This is done by combining Auto-Recovery with the high availability feature provided with the server virtualization software used.
Note that the Auto-Recovery function differs from clustering software (such as PRIMECLUSTER) in the following respect:
Server failure detection
The Auto-Recovery function can detect hardware failures using server management software (such as ServerView Agents) and server management devices (management blades, management boards, or remote management controllers). It cannot detect system slowdowns.
Automated server installation and setup
The following three features simplify server installation and setup:
Deploying multiple servers via server cloning
Server cloning is a feature that distributes a cloning image (collected from the system disk of a reference server) to other physical servers.
When a cloning image is created, network-specific settings such as host names and IP addresses are removed from the cloning image. This network-specific configuration is dynamically reconfigured on the servers to which the cloning image is distributed.
This makes it possible to create duplicates of existing servers that will use the same operating system and software.
Simplified server installation using I/O virtualization
I/O virtualization via HBA address rename (*) allows storage devices to be configured independently and prior to the rest of the server installation process. Servers can then be installed and set up without the involvement of storage administrators.
* Note: Refer to "I/O Virtualization".
Multiple server installations using the pre-configuration feature
The pre-configuration feature can be used to configure all settings required for a Resource Orchestrator setup in a system configuration file, which can then be easily imported from the ROR console.
The system configuration file is in CSV format and can be edited easily even in environments where Resource Orchestrator is not installed.
Streamlined server maintenance
The following features help to identify which servers need to be replaced, and assist administrators with maintenance required after replacement of a server:
Automatic maintenance LED activation on failed servers. (*)
* Note: 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".
In SAN boot environments, the I/O virtualization (*) provided by either HBA address rename or VIOM makes it possible to restore a failed server's original WWN definition to the replacement server. Resource Orchestrator is able to quickly reconnect a replaced server to its original volume(s) and start it up from the same operating system without accessing any storage device.
Moreover, with the ability to automatically re-define MAC addresses, boot configuration, and network configuration using VIOM, it is no longer necessary to reconfigure network devices or applications that depend on MAC address values.
* Note: Refer to "I/O Virtualization".
In local boot environments, a system image backed up beforehand can be easily restored to the replaced server to simplify server replacement.
Easy server monitoring
When managing PRIMERGY BX servers, BladeViewer can be used to easily check server statuses and perform other daily operations. In BladeViewer, server statuses are displayed in a format similar to the physical configuration of a blade server system, making server management and operation more intuitive. BladeViewer provides the following features:
Display of the mount statuses of server blades.
An intuitive way to monitor and control the mount statuses of multiple server blades.
Easier visualization of which applications are running on each server blade. This helps to quickly identify any affected applications when a hardware fault occurs on a server blade.
Simple network monitoring
For PRIMERGY BX servers, Resource Orchestrator provides a NetworkViewer function, which helps visualize and relate physical networks (between servers and LAN switches) together with virtualized networks (from VLANs or virtual switches used in server virtualization software). It has the following features.
Automatic detection and display of network connections (topology) and link statuses between heterogeneous network resources.
Facilitates overall network consistency diagnostics and identification of the resources (physical and virtual) affected by a network issue.
Displays comprehensive content that can be used in communication between server and network administrators, thus smoothing out coordination between the two parties.
Monitoring of power consumption
By activating the power monitoring feature, it is possible to monitor trends in power consumption for resources equipped with power monitoring capabilities, or resources connected to a registered power monitoring device (PDU or UPS). The power consumption data regularly collected from the power monitoring environment can be output to a file in CSV format or as a graph.
Relocation of VM guests
By integrating with VM management software (such as VMware vCenter Server or others) and VM hosts (such as Citrix XenServer or others), Resource Orchestrator provides the ability to migrate VM guests between physical servers directly from the ROR console. When used with other Resource Orchestrator functions, this enables the following:
Regrouping of all VM guests to a subset of servers and shut down of any unused servers or chassis to reduce overall power consumption.
When server maintenance becomes necessary, VM guests can be migrated to alternative servers and their applications kept alive during maintenance work.
I/O Virtualization
I/O adapters (HBA) for servers are shipped with an assigned physical address that is unique across the world. This World Wide Name (WWN) is used by the storage network to identify servers. Until now, the WWN settings on storage networks needed to be updated whenever servers were added, replaced, or switched over. Resource Orchestrator uses I/O virtualization technology that makes server-side I/O control possible. It does this by replacing physically-bound WWNs with virtual WWNs assigned to each server based on its role in the system. Resource Orchestrator can handle two different I/O virtualization technologies (HBA address rename and VIOM).
With VIOM, the ability to re-define MAC addresses of network interfaces, boot configuration, and network configuration means that it is no longer necessary to reconfigure network devices or applications that depend on MAC address values.
Note
The "I/O virtualization option" is required when using HBA address rename.
ServerView Virtual-IO Manager should be installed on the admin server when integrating Resource Orchestrator with VIOM.
The following features are unavailable when ServerView Deployment Manager shares the same subnet (admin LAN). In such cases, it is recommended to use ServerView Deployment Manager and ServerView Virtual-IO Manager instead.
Cloning
Backup and restore
HBA address rename
Server switchover (based on the backup-restore and HBA address rename methods)
For details, refer to "B.2 Co-Existence with ServerView Deployment Manager" in the "Setup Guide VE".
