This section explains the software requirements for installation of Resource Orchestrator.
The basic software listed below is required when using Resource Orchestrator.
Software | Basic Software | Remarks |
|---|---|---|
Manager [Windows] | Microsoft(R) Windows Server(R) 2008 Standard (x86, x64) | The Server Core installation option is not supported. |
Microsoft(R) Windows Server(R) 2003 R2, Standard Edition | SP2 or later supported. | |
Manager [Linux] | Red Hat(R) Enterprise Linux(R) 5.5 (for x86) | In the event that there are required pieces of software, such as driver kits and update kits, prepare them. For information about required software, refer to the manual of the server or the Linux installation guide. |
Agent [Windows] | Microsoft(R) Windows Server(R) 2008 Standard (x86, x64) | The Server Core installation option is not supported. |
Microsoft(R) Windows Server(R) 2003 R2, Standard Edition | SP2 or later supported. | |
Agent [Linux] | Red Hat(R) Enterprise Linux(R) 5.5 (for x86) | In the event that there are required pieces of software, such as driver kits and update kits, prepare them. |
Agent [VMware] | VMware vSphere(TM) 4 | Install Resource Orchestrator on the VMware ESX host. |
Agent [Hyper-V] | Microsoft(R) Windows Server(R) 2008 R2 Enterprise | The Server Core installation option is not supported. |
Note
Installation will fail when a Resource Orchestrator agent is installed on an unsupported OS.
[Hyper-V]
When using Hyper-V on managed servers, the only supported OS of the admin server is Windows.
The operating system parameters can be set when deploying the image. For details on the parameters that can be set, refer to "D.5 [OS] Tab".
[VMware] [Hyper-V]
Depending on the server virtualization software used, some restrictions may apply to the operating systems that parameters can be set for and the prerequisites for performing the settings. For details, refer to the server virtualization software manual.
Basic software (OS) that can be used on an L-Server is limited to software supported by the server virtualization software.
The image to deploy can be specified when creating an L-Server. Image deployment for Resource Orchestrator uses the following functions of the server virtualization software:
Server Virtualization Software | Function |
|---|---|
VMware vSphere(TM) 4 | Template, guest OS customization |
Microsoft(R) System Center Virtual Machine Manager 2008 R2 | Template, guest OS operating system profile |
Use of some functions used in the server virtualization software for Resource Orchestrator at the same time with this product is not supported. Please do not use these functions.
Server Virtualization Software | Functions with no Support of Combined Use |
|---|---|
VMware vSphere(TM) 4 | VMware Storage VMotion |
Microsoft(R) System Center Virtual Machine Manager 2008 R2 |
|
[Hyper-V]
VMware ESX can be managed by SCVMM using VMware vCenter Server. In Resource Orchestrator, VMware ESX cannot be managed through SCVMM. When managing VMware ESX in the above configuration, register VMware vCenter Server in Resource Orchestrator.
Note
If an L-Server is created with a specified Windows image, when deploying the image use Sysprep, provided by Microsoft, to re-configure the properties unique to the server. By executing Sysprep, the user information and OS setting information are reset.
For details on Sysprep, refer to the information provided by Microsoft.
If stopping or restarting of the manager is performed during execution of Sysprep, the operation being executed will be performed after the manager is started.
Until the process being executed is completed, do not operate the target resource.
When using MAC license authentication for activation of Windows Server 2008 images, Sysprep can be executed a maximum of three times. Since Sysprep is executed when creating L-Server with images specified or when collecting cloning images, collection of cloning images and creation of L-Servers with images specified cannot be performed more than four times. Therefore it is recommended not to collect cloning images from L-Servers which have had cloning images deployed, but to collect them from a dedicated master server. When customization of a guest OS is performed using the template function in VMware or when the template is created using SCVMM, Sysprep is executed and the number is included in the count.
[Windows] [VMware]
If an L-Server is created with a Windows image specified, use Sysprep to set the server specific information again, when starting for the first time after creating the L-Server. After startup and resetting the server specific information, it is recommended that you log off once, otherwise when the L-Server console is opened from the server virtualization software management window you will be logged on with Administrator status.
Note the following points when collecting cloning images from an L-Server that was created using a cloning image.
As L-Servers which has not been used even once after creation do not have server specific information set, creation of L-Servers using cloning images collected from an L-Server may fail. When collecting cloning images, set the server specific information on L-Server, after starting the target L-Server.
It is not necessary to install Resource Orchestrator on admin clients, but the following basic software is required.
Basic Software (OS) | Remarks |
|---|---|
Microsoft(R) Windows(R) 7 Professional | - |
Microsoft(R) Windows Vista(R) Business | SP1 or later supported. |
Microsoft(R) Windows(R) XP Professional operating system | SP3 or later supported. |
Microsoft(R) Windows Server(R) 2008 Standard (x86, x64) | The Server Core installation option is not supported. |
Microsoft(R) Windows Server(R) 2003 R2, Standard Edition | SP2 or later supported. |
The software listed below is required when using Resource Orchestrator.
Software | Basic Software (OS) | Patch ID/Bundle Update |
|---|---|---|
Manager [Windows] | None | - |
Manager [Linux] | Red Hat(R) Enterprise Linux(R) 5 (for x86) | Bundle Update U09031 (5.3 compatible) |
Red Hat(R) Enterprise Linux(R) 5 (for Intel64) | Bundle Update U09031 (5.3 compatible) | |
Agent [VMware] | None | - |
Agent [Hyper-V] | None | - |
The software listed below is required when using Resource Orchestrator.
Software | Required Software | Version | Remarks |
|---|---|---|---|
Manager [Windows] | ServerView Operations Manager for Windows (*1) | V4.20.25 or later | Refer to "See Installation of Related ServerView Products". |
Microsoft(R) LAN Manager module | - | Necessary when using backup and restore, or cloning. | |
BACS | - | Necessary when performing redundancy of the admin LAN for admin servers. | |
ServerView RAID (*1) | - | Necessary when a RAID is composed of local disks (*3). | |
ServerView Virtual-IO Manager | 2.1 or later | Necessary when using VIOM's Virtual I/O. | |
VMware vCenter Server (previously VMware VirtualCenter) | 4.0 | [VMware] | |
SNMP Trap Service | - | - | |
DHCP Server (Standard OS service) | - | Necessary when managing a managed server within a separate subnet to the admin server. | |
Microsoft(R) System Center Virtual Machine Manager 2008 R2 | - | [Hyper-V] | |
Windows PowerShell | 2.0 | [Hyper-V] | |
ETERNUS SF Storage Cruiser Manager | 14.2 or later | Necessary when connecting an ETERNUS LUN with an L-Server operating on the physical server. | |
Manager [Linux] | ServerView Operations Manager for Linux | V4.81.05 or later | Refer to "See Installation of Related ServerView Products". |
Microsoft(R) LAN Manager module | - | Necessary when using backup and restore, or cloning. | |
PRIMECLUSTER Enterprise Edition | 4.3A00 or later | When an admin server is in a cluster configuration, one of the following software is necessary. | |
PRIMECLUSTER HA Server | 4.3A00 or later | ||
PRIMECLUSTER GLS | - | Necessary when performing redundancy of the admin LAN for admin servers. | |
VMware vCenter Server (previously VMware VirtualCenter) | 4.0 | Necessary for management of VM guest and VM host. | |
net-snmp package | - | Included in operating system installation media. | |
ETERNUS SF Storage Cruiser Manager | 14.2 or later | Necessary when connecting an ETERNUS LUN with an L-Server operating on the physical server. | |
Agent [Windows] | ServerView Agent for Windows (*1) | V4.50.05 or later | - |
"setupcl.exe" module | - | Necessary when using backup and restore, or cloning. Refer to the Microsoft web site and obtain the latest modules. (*4) When using Windows Server 2008, the modules are already configured in the OS so there is no need to obtain new modules. | |
BACS | - | Necessary when performing redundancy of the admin LAN and public LAN for managed servers. | |
ServerView RAID (*1) | - | Necessary when a RAID is composed of local disks (*3). | |
ETERNUS Multipath Driver | V2.0L10 or later | Necessary for multipath connections between servers and ETERNUS storage units. | |
Data ONTAP DSM | 3.2R1 or later | Necessary for connection between servers and NetApp storage units. | |
Agent [Linux] | ServerView Agent for Linux (*1) | V4.90.14 or later | - |
ServerView RAID (*1) | - | Necessary when a RAID is composed of local disks (*3). | |
ETERNUS Multipath Driver | V2.0L02 or later | Necessary for multipath connections between servers and ETERNUS storage units. | |
Agent [Red Hat Enterprise Linux] | PRIMECLUSTER GLS (*1) | 4.2A00 or later | Necessary when performing redundancy of the admin LAN and public LAN for managed servers. |
Agent [VMware] | ServerView Agent for VMware (*1) | V4.30-20 or later | - |
ServerView RAID (*1) | - | Necessary when a RAID is composed of local disks (*3). |
*1: Necessary when using PRIMERGY series servers.
When installing managers in cluster environments, installation on both the primary and secondary nodes is necessary.
*2: Obtain it from the following Microsoft FTP site.
Microsoft FTP site
URL: ftp://ftp.microsoft.com/bussys/clients/msclient/dsk3-1.exe (As of November 2010) |
*3: A local disk refers either to a server's internal disk, or to one stored in a storage blade.
*4: The necessary files vary depending on the CPU architecture (x86, x64) of the target system, and the OS version. Check the Microsoft web site for the modules to obtain.
Microsoft web site
URL(x86): http://www.microsoft.com/downloads/details.aspx?familyid=93F20BB1-97AA-4356-8B43-9584B7E72556&displaylang=en (As of November 2010) URL(x64): http://www.microsoft.com/downloads/details.aspx?familyid=C2684C95-6864-4091-BC9A-52AEC5491AF7&displaylang=en (As of November 2010) |
After obtaining the latest version of module, place it in a work folder (such as C:\temp) of the system for installation and execute it.
For details on execution, refer to "Software Preparation and Checks" in the "ServerView Resource Coordinator VE Installation Guide".
The module is not necessary after installation of agents.
The following software is necessary for admin clients.
Required Software | Version | Remarks |
|---|---|---|
Microsoft(R) Internet Explorer | 7 | - |
Java(TM) 2 Runtime Environment Standard Edition | (*1) | Necessary for displaying the management window of ServerView Operations Manager or the VM management console, on admin clients. |
VMware vSphere(TM) Client | 4.0 | Necessary on admin clients when using the functions for coordinating with VMware or the VM management software on managed servers. [VMware] |
Hyper-V Manager | - | Necessary on admin clients when using the functions for coordinating with Hyper-V on managed servers. |
Microsoft(R) System Center Virtual Machine Manager 2008 R2 VMM management console | - | Necessary on admin clients when using the functions for coordinating with VM management software. [Hyper-V] |
ETERNUS SF Storage Cruiser clients | 14.2 or later | Necessary when checking the detailed information of storage using the admin client. |
*1: To display the management window of ServerView Operations Manager, please refer to the ServerView Operations Manager manual.
To display the VM management console, version 1.5 or later is necessary.
See
Installation of Related ServerView Products
There are advisory notes regarding the installation of ServerView Operations Manager.
For details on advisory notes, refer to the specific description of the settings for ServerView Operations Manager for Windows in the "ServerView Resource Coordinator VE Installation Guide".
SCVMM Server MaxShellPerUser Settings [Hyper-V]
Resource Orchestrator controls SCVMM using PowerShell Web Services for Management (hereinafter WS-Management).
With standard Windows settings, the maximum number of processes which can start shell operations per user (MaxShellsPerUser) is set to five. For Resource Orchestrator, it is necessary to change settings to enable a maximum of six sessions.
Since WS-Management is used for Windows administrator tools as well as Resource Orchestrator, set a number six or larger than MaxShellsPerUser, giving consideration to operating needs.
Change the MaxShellsPerUser settings using the following procedure:
Execute Windows PowerShell as an administrator.
Change the current directory using the Set-Location commandlet.
PS> Set-Location -Path WSMan:\localhost\Shell <RETURN> |
Check the current MaxShellsPerUser configuration information using the Get-ChildItem commandlet.
The content displayed in MaxShellsPerUser is the current setting.
PS WSMan:\localhost\Shell> Get-ChildItem <RETURN> |
Example
PS WSMan:\localhost\Shell> Get-ChildItem
WSManConfig: Microsoft.WSMan.Management\WSMan::localhost\Shell
Name Value Type
---- ----- ----
AllowRemoteShellAccess true System.String
IdleTimeout 180000 System.String
MaxConcurrentUsers 5 System.String
MaxShellRunTime 2147483647 System.String
MaxProcessesPerShell 15 System.String
MaxMemoryPerShellMB 150 System.String
MaxShellsPerUser 5 System.String |
Configure MaxShellsPerUser using the Set-Item commandlet.
Example
When setting MaxShellsPerUser 10
PS WSMan:\localhost\Shell> Set-Item .\MaxShellsPerUser 10 <RETURN> |
Resource Orchestrator cannot be used in combination with Resource Coordinator or the following products.
Software | Product Name |
|---|---|
Manager [Windows] | ServerView Deployment Manager |
ServerView Installation Manager (*1) | |
Manager [Linux] | Server System Manager |
Agent [Windows/Hyper-V] | Server System Manager |
ServerView Deployment Manager (*2) | |
Agent [Linux] | Server System Manager |
ServerView Deployment Manager (*2) | |
Agent [VMware] | ServerView Deployment Manager (*2) |
*1: As managers of this product include PXE server, use in combination with the PXE server required for remote installation of ServerView Installation Manager is not possible.
*2: ServerView Deployment manager can be installed after Resource Coordinator has been installed. For details on the installation method, refer to the "ServerView Resource Coordinator VE Installation Guide".
Note
The admin server of Resource Orchestrator can manage the ServerView Resource Coordinator VE V2.2 agent. In such cases, the agent can be used within the function range for ServerView Resource Coordinator VE.
The same resource cannot be managed by the Resource Orchestrator admin server and the ServerView Resource Coordinator VE admin server.
Resource Orchestrator managers contain some functions of DHCP servers and PXE servers. Therefore, do not place products or services with other DHCP server or PXE server functions on the admin LAN.
Examples of Products Including DHCP Servers and PXE Servers
The Windows Server 2003 "Remote Installation Service", and the Windows Server 2008/Windows Server 2003 "Windows Deployment Service"
ADS (Automated Deployment Services) of Windows Server 2003
Boot Information Negotiation Layer(BINLSVC)
ServerView Deployment Manager (*1)
ServerStart (when using the remote installation function)
*1: As PXE server is included, the use of some functions is restricted when it is used on the same admin LAN as ServerView Resource Orchestrator. For details, refer to the "ServerView Resource Coordinator VE Setup Guide".
[Windows]
Depending on the Windows Server domain type, the available functions differ as indicated in the table below.
Domain Type | Backup and Restore | Cloning | Server Switchover Using Backup and Restore |
|---|---|---|---|
Domain controller | No | No | No |
Member server (*1) | Yes (*2) | Yes (*2, *3) | Yes (*2, *4) |
Workgroup | Yes | Yes | Yes |
Yes: Use possible.
No: Use not possible.
*1: Member servers of Windows NT domains or Active Directory.
*2: After performing operations it is necessary to join Windows NT domains or Active Directory again.
*3: Before obtaining cloning images, make sure that the server is not a member of a Windows NT domain or Active Directory.
*4: When switchover has been performed using Auto-Recovery, join Windows NT domains or Active Directory again before starting operations.
[Windows/Linux]
Contact Fujitsu technical staff for information about ServerView Deployment Manager.
For new installations of Resource Orchestrator, the following static disk space is required. The amount of disk space may vary slightly depending on the environment in question.
Software | Folder | Disk Capacity (Unit: MB) |
|---|---|---|
Manager [Windows] | Installation_folder (*1) | 800 |
Manager [Linux] | /opt | 570 |
/etc/opt | 4 | |
/var/opt | 120 | |
Agent [Windows/Hyper-V] | Installation_folder (*1) | 100 |
Agent [Linux] | /opt | 90 |
/etc/opt | 5 | |
/var/opt | 5 | |
Agent [VMware] | /opt | 90 |
/etc/opt | 5 | |
/var/opt | 5 |
*1: The installation folder name specified when this software is installed.
When using Resource Orchestrator, the following disk space is required for each folder, in addition to static disk space. For details on each item, refer to the dynamic disk space section in the "ServerView Resource Coordinator VE Installation Guide".
Software | Folder | Disk Capacity (Unit: MB) |
|---|---|---|
Manager [Windows] | Installation_folder (*1) | 2400 + Number_of_managed_servers * 4 |
Environmental_data_storage_area | ||
Image_file_storage_folder (*2) | Image_file_storage_area (*3) | |
Manager [Linux] | /etc | 2 |
/var/opt | 2400 + Number_of_managed_servers * 4 | |
Environmental_data_storage_area | ||
Image_file_storage_directory (*2) | Image_file_storage_area (*3) | |
Agent [Windows/Hyper-V] | Installation_folder (*1) | 60 |
Agent [Linux] | /etc | 1 |
/var/opt | 1 | |
Agent [VMware] | /etc | 1 |
/var/opt | 1 | |
HBA address rename setup service [Windows] | Installation_folder (*1) | 60 |
HBA address rename setup service [Linux] | /etc | 1 |
/var/opt | 60 |
*1: The installation folder name specified when this software is installed.
*2: The name of the storage folder (directory) specified for image files when this software is installed.
*3: The image storage area when using cloning images for cloning of physical servers using RCVE.
The memory size listed below is required when using Resource Orchestrator.
Software | Memory Size (Unit: MB) |
|---|---|
Manager [Windows] | 3072 |
Manager [Linux] | 3072 |
Agent [Windows/Hyper-V] | 32 |
Agent [Linux] | 32 |
Agent [VMware] | 32 |
