This section explains the software requirements for installation of Resource Orchestrator.
The basic software listed below is required when using Resource Orchestrator.
Required Basic Software
Basic Software (OS) | Remarks |
|---|---|
Microsoft(R) Windows Server(R) 2008 Standard (x64) | The Server Core installation option is not supported. |
Basic Software (OS) | Remarks |
|---|---|
Red Hat(R) Enterprise Linux(R) 6.2 (for x86) | Prepare any required driver kits, update kits, or software. For information about required software, refer to the manual of the server or the Linux installation guide. For required packages, refer to "Table 2.36 Required Packages of Manager [Linux Manager]". The Linux Kernel version depending on the hardware corresponds to the version supported by Fujitsu. |
Basic Software (OS) | Remarks |
|---|---|
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. |
Basic Software (OS) | Remarks |
|---|---|
| The Server Core installation option is not supported. When using dynamic memory and memory weight, Windows Server 2008 R2 Service Pack 1(SP1) or later must be applied to the VM host, and SCVMM must be upgraded to System Center Virtual Machine Manager 2008 R2 Service Pack 1 (SP1) or later. |
Basic Software (OS) | Remarks |
|---|---|
Red Hat(R) Enterprise Linux(R) 6.2 (for x86) | Prepare any required driver kits, update kits, or software. About required packages, refer to "Table 2.37 Required Packages of Agent [Linux]". The Linux Kernel version depending on the hardware corresponds to the version supported by Fujitsu. |
Basic Software (OS) | Remarks |
|---|---|
Solaris(TM) 10 Operating System | Supported after 05/09 (Update7). When using SAN boot, refer to the manual for Fibre Channel card driver, "SPARC Enterprise - ETERNUS SAN Boot Environment Build Guide". |
Basic Software (OS) | Remarks |
|---|---|
| Install Resource Orchestrator on the VMware ESX host. (*) |
* Note: VMware ESXi of VMware vSphere 4.0 or earlier cannot be used for managed servers.
VMware ESXi of the version of VMware vSphere 4.1 or later can be used for managed servers, but there is no need to install Resource Orchestrator on VMware ESXi.
Basic Software (OS) | Remarks |
|---|---|
Red Hat(R) Enterprise Linux(R) 6.2 (for x86) | - |
Basic Software (OS) | Remarks |
|---|---|
Oracle VM 3.0 | - |
Basic Software (OS) | Remarks |
|---|---|
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. |
Microsoft(R) Windows Vista(R) Business | - |
Microsoft(R) Windows(R) XP Professional Edition | SP2 or later supported. |
Microsoft(R) Windows(R) 7 Professional | - |
* Note: This is necessary when creating physical L-Servers using rack mount or tower servers.
Basic Software (OS) | Remarks |
|---|---|
Red Hat(R) Enterprise Linux(R) 6.2 (for x86) | Prepare any required driver kits, update kits, or software. For information about required software, refer to the manual of the server or the Linux installation guide. About Required Packages, refer to "Table 2.38 Required Packages of HBA address rename Setup Service [Linux]". The Linux Kernel version depending on the hardware corresponds to the version supported by Fujitsu. |
* Note: This is necessary when creating physical L-Servers using rack mount or tower servers.
Note
[VMware]
The free version of VMware ESXi cannot be used for managed servers.
When using VMware ESXi for managed servers, purchase the appropriate license.
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.
[Xen]
When using RHEL5-Xen on managed servers, the only supported OS of the admin server is Linux.
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.
[Hyper-V]
VMware ESX and Citrix(R) XenServer(TM) can be managed by SCVMM, but only VM hosts for Hyper-V can be managed when using SCVMM in Resource Orchestrator.
Server Virtualization Software | Functions with no Support of Combined Use |
|---|---|
VMware vSphere 4.0 | Cisco Nexus 1000V virtual switch |
Microsoft(R) System Center Virtual Machine Manager 2008 R2 |
|
Oracle VM Manager | Template |
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 MAK license authentication for activation of Windows Server 2008 image OS, 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 that 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]
Note the following points when collecting cloning images from an L-Server that was created using a cloning image.
As L-Servers which have 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.
[Oracle VM]
The information on the [OS] tab cannot be set when deploying the image.
Required Basic Software: Admin Clients
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. |
Required Patches
Basic Software (OS) | Patch ID/Bundle Update |
|---|---|
Microsoft(R) Windows Server(R) 2003 R2 Standard x64 Edition | Hotfix KB942589 (*) |
Microsoft(R) Windows Server(R) 2003 R2 Enterprise x64 Edition | Hotfix KB942589 (*) |
* Note: Necessary when managing a managed server within a separate subnet to the admin server.
Basic Software (OS) | Patch ID/Bundle Update (*) |
|---|---|
Red Hat(R) Enterprise Linux(R) 5 (for x86) |
|
Red Hat(R) Enterprise Linux(R) 5 (for Intel64) |
|
* Note: Necessary when upgrading.
Basic Software (OS) | Patch ID/Bundle Update |
|---|---|
None | - |
Basic Software (OS) | Patch ID/Bundle Update |
|---|---|
None | - |
Basic Software (OS) | Patch ID/Bundle Update (*) |
|---|---|
Red Hat(R) Enterprise Linux(R) 5 (for x86) | Bundle Update U07121 (5.1 compatible) |
Red Hat(R) Enterprise Linux(R) 5 (for Intel64) | Bundle Update U07121 (5.1 compatible) |
Basic Software (OS) | Patch ID/Bundle Update |
|---|---|
None | - |
Basic Software (OS) | Patch ID/Bundle Update |
|---|---|
None | - |
Basic Software (OS) | Patch ID/Bundle Update |
|---|---|
None | - |
Basic Software (OS) | Patch ID/Bundle Update |
|---|---|
None | - |
Basic Software (OS) | Patch ID/Bundle Update |
|---|---|
None | - |
Basic Software (OS) | Patch ID/Bundle Update (*) |
|---|---|
Red Hat(R) Enterprise Linux(R) 5 (for x86) |
|
Red Hat(R) Enterprise Linux(R) 5 (for Intel64) |
|
* Note: Necessary when upgrading.
[Hyper-V]
For the manager, agents, SCVMM, SCVMM agents, and Windows guest OSs, apply the latest updated program using Microsoft Update.
Installation of the latest integrated service provided by each OS on VM guests is necessary.
Required Packages [Linux]
The packages listed below are required when using Resource Orchestrator.
Install the required packages beforehand, if necessary.
The architecture of the required packages to be installed is shown enclosed by parenthesis "()".
For the items with no architecture to be installed is specified, install the package of the same architecture as the OS.
Basic Software (OS) | Required Packages |
|---|---|
Red Hat(R) Enterprise Linux(R) 6.2 (for x86) | alsa-lib(i686) |
Red Hat(R) Enterprise Linux(R) 5.8 (for x86) | apr(i386) |
*1: Necessary when the OS architecture is Intel64.
*2: Necessary when the OS architecture is x86.
*3: Necessary when managing a managed server within a separate subnet to the admin server.
*4: Install an OS, specifying a package.
Basic Software (OS) | Required Packages |
|---|---|
Red Hat(R) Enterprise Linux(R) 6.2 (for x86) | alsa-lib(i686) |
Red Hat(R) Enterprise Linux(R) 5.8 (for x86) | alsa-lib(i686) |
*1: Necessary when installing an agent (dashboard functions).
*2: Necessary when the OS architecture is Intel64.
*3: Necessary when the OS architecture is x86.
Basic Software (OS) | Required Packages |
|---|---|
Red Hat(R) Enterprise Linux(R) 6.2 (for x86) | alsa-lib(i686) |
Red Hat(R) Enterprise Linux(R) 5.8 (for x86) | alsa-lib(x86_64) |
The software listed below is required when using Resource Orchestrator.
Required Software (Windows Manager)
The required software for Windows manager is as follows:
Unless specified otherwise, install on the same server as the manager.
When the ROR console is started on Windows manager, the required software of the admin client is also necessary.
Required Software | Version | Remarks |
|---|---|---|
ServerView Operations Manager for Windows (*1) | V5.30 - V6.00.09 | Necessary for Single Sign-On. |
Microsoft(R) LAN Manager module | - | Used when performing backup and restore, or cloning for physical servers. |
BACS | - | Necessary when performing redundancy of the admin LAN for admin servers. When using PRIMECLUSTER GLS, the following patches are required.
|
ServerView Virtual-IO Manager | 2.6 or later | Necessary when creating physical L-Servers using blade servers. |
VMware vCenter Server | 4.0 | [VMware] |
SNMP Service | - | Necessary for ServerView Operations Manager. |
SNMP Trap Service (Standard OS service) | - | Necessary for ServerView Operations Manager. |
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 using the storage affinity switchover method for server switchover.
|
15.0 or later | In the following cases, ETERNUS SF Storage Cruiser manager must be version 15.0 or later:
| |
ETERNUS SF AdvancedCopy Manager Copy Control Module | 15.0 or later | Necessary when using dynamic LUN mirroring on ETERNUS storage. |
NavisecCLI | 7.30 or later | Necessary when connecting an EMC CLARiiON LUN to a physical L-Server. |
SymCLI | - | Necessary when connecting an EMC Symmetrix DMX or EMC Symmetrix VMAX device to a physical L-Server. |
Solutions Enabler | 7.1.2 or later | Necessary when connecting an EMC Symmetrix DMX or EMC Symmetrix VMAX device to a physical L-Server. Can be installed on the same admin server as the manager or on another admin server. |
Oracle VM Manager | 3.0 | [Oracle VM] |
BMC BladeLogic Server Automation | 8.2 or later | Necessary when creating an L-Server in a Solaris Container. |
BMC BladeLogic Server Automation Console | 8.2 or later | Necessary when creating an L-Server in a Solaris Container. |
*1: 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 |
Required Software (Linux Manager)
Required Software for Linux Manager is as follows.
Unless specified otherwise, install on the same server as the manager.
Required Software | Version | Remarks |
|---|---|---|
ServerView Operations Manager for Linux | V5.30 - V6.00.09 | Necessary for Single Sign-On. |
Microsoft(R) LAN Manager module | - | Necessary when using backup and restore, or cloning. |
ServerView Virtual-IO Manager | 2.6 or later | Necessary when creating physical L-Servers using blade servers. |
PRIMECLUSTER GLS | - | Necessary when performing redundancy of the admin LAN for admin servers. |
VMware vCenter Server | 4.0 | Necessary for management of VM guest and VM host. |
ETERNUS SF Storage Cruiser Manager | 14.2 or later | Necessary when using the storage affinity switchover method for server switchover.
|
15.0 or later | In the following cases, ETERNUS SF Storage Cruiser manager must be version 15.0 or later:
| |
ETERNUS SF AdvancedCopy Manager Copy Control Module | 15.0 or later | Necessary when using dynamic LUN mirroring on ETERNUS storage. |
NavisecCLI | 7.30 or later | Necessary when connecting an EMC CLARiiON LUN to a physical L-Server. |
SymCLI | - | Necessary when connecting an EMC Symmetrix DMX or EMC Symmetrix VMAX device to a physical L-Server. |
Solutions Enabler | 7.1.2 or later | Necessary when connecting an EMC Symmetrix DMX or EMC Symmetrix VMAX device to a physical L-Server. Can be installed on the same admin server as the manager or on another admin server. |
Oracle VM Manager | 3.0 | [Oracle VM] |
DHCP Server (Standard OS service) | - | Necessary when managing a managed server within a separate subnet to the admin server. |
BMC BladeLogic Server Automation | 8.2 or later | Necessary when creating an L-Server in a Solaris Container. |
BMC BladeLogic Server Automation Console | 8.2 or later | Necessary when creating an L-Server in a Solaris Container. |
* Note: Obtain it from the following Microsoft FTP site.
Microsoft FTP site
URL: ftp://ftp.microsoft.com/bussys/clients/msclient/dsk3-1.exe |
Required Software | Version | Remarks |
|---|---|---|
ServerView Agents for Windows | V4.50.05 or later | Required for collecting and managing server information of PRIMERGY and PRIMEQUEST. |
"setupcl.exe" module | - | Necessary when using backup and restore, or cloning. |
Intel PROSet | - | Necessary when performing redundancy of the admin LAN and public LAN for managed servers. When using PRIMECLUSTER GLS, the following patches are required.
|
ETERNUS Multipath Driver | V2.0L10 or later | Necessary for multipath connections between servers and storage units (ETERNUS). |
Data ONTAP DSM | 3.2R1 or later | Necessary for connection between servers and storage units (NetApp). |
PowerPath | 5.3 or later | Necessary for multipath connections between servers and storage units (EMC CLARiiON, EMC Symmetrix DMX, or EMC Symmetrix VMAX). |
*2: The necessary files vary depending on the CPU architecture (x86, x64) of the target system, and the OS version. Please refer to the Microsoft web site for the module to obtain.
Microsoft download web site
URL(x86): URL(x64): |
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 how to execute it, refer to "2.2.1.1 Software Preparation and Checks" in the "Setup Guide CE".
The module is not necessary after installation of agents.
Required Software | Version | Remarks |
|---|---|---|
ServerView Agents for Linux | V4.90.14 or later | Required for collecting and managing server information of PRIMERGY and PRIMEQUEST. |
ETERNUS Multipath Driver | V2.0L02 or later | Necessary for multipath connections between servers and storage units (ETERNUS). |
PowerPath | 5.3 | Necessary for multipath connections between servers and storage units (EMC CLARiiON, EMC Symmetrix DMX, or EMC Symmetrix VMAX). |
Required Software | Version | Remarks |
|---|---|---|
PRIMECLUSTER GLS | 4.2A00 or later | Necessary when performing redundancy of the admin LAN and public LAN for managed servers. |
Required Software | Version | Remarks |
|---|---|---|
PRIMECLUSTER GLS | 4.2 or later | Necessary when performing redundancy of the admin LAN and public LAN for managed servers. |
ETERNUS SF Storage Cruiser | 14.2 or later | Necessary on the primary server of the managed server when using the storage affinity switchover method for server switchover. |
RSCD Agent | 8.2 or later | Required when using the global zone of Solaris Containers for the agent, and creating an L-Server. |
Required Software | Version | Remarks |
|---|---|---|
ServerView Agents for VMware | V4.30-20 or later | Required for collecting and managing server information of PRIMERGY and PRIMEQUEST. |
ServerView ESXi CIM Provider | 1.10.01 or later | Necessary when using VMware ESXi as a managed server. |
Required Software | Version | Remarks |
|---|---|---|
ServerView Agents for Windows | V4.50.05 or later | Required for collecting and managing server information of PRIMERGY and PRIMEQUEST. |
"setupcl.exe" module | - | Necessary when using backup and restore, or cloning. |
Intel PROSet | 15.6.25.0 or later | Necessary to automatically perform the following configurations using Intel PROSet on blade servers:
This is not necessary when the following applies:
|
PRIMECLUSTER GLS for Windows (*1) | - | After configuring redundancy for blade servers using PRIMECLUSTER GLS, it is necessary to perform the following configurations automatically:
This is not necessary when the following applies:
For details, refer to "2.2.7 Simplifying Networks". |
*2: The necessary files vary depending on the CPU architecture (x86, x64) of the target system, and the OS version. Please refer to the Microsoft web site for the module to obtain.
Microsoft download web site
URL(x86): URL(x64): |
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 how to execute it, refer to "2.2.1.1 Software Preparation and Checks" in the "Setup Guide CE".
The module is not necessary after installation of agents.
Required Software | Version | Remarks |
|---|---|---|
ServerView Agents for Linux | V4.81-14 or later | Necessary when using PRIMEQUEST series servers. |
PRIMECLUSTER GDS | - | Necessary when using RHEL5-Xen servers. |
Required Software | Version | Remarks |
|---|---|---|
ServerView Agents for Linux | V5.1 or later | Required for collecting and managing server information of PRIMERGY and PRIMEQUEST. |
Required Software | Version | Remarks |
|---|---|---|
ServerView Agents for Linux | 5.0 or later | Required for collecting and managing server information of PRIMERGY and PRIMEQUEST. |
Required Software | Version | Remarks |
|---|---|---|
Windows(R) Internet Explorer(R) | 8 | Necessary for displaying the online help. |
Required Software | Version | Remarks |
|---|---|---|
Firefox | 3 | Necessary for displaying the online help. |
Required Software: Admin Clients
The following software is necessary for admin clients.
Required Software | Version | Remarks |
|---|---|---|
Windows(R) Internet Explorer(R) | 8 | Required for display of the ROR console. |
Adobe Flash Player | 10.3.183.5 or higher | Used for displaying the ROR console and the dashboard on admin clients. |
Java(TM) 2 Runtime Environment Standard Edition | (*2) | Necessary for displaying the management window of ServerView Operations Manager, the VM management console, or console window on admin clients. |
VMware vSphere(R) Client | 4.0 | [VMware] |
Hyper-V Manager | - | [Hyper-V] |
Microsoft(R) System Center Virtual Machine Manager 2008 R2 VMM management console or Microsoft(R) System Center 2012 Virtual Machine Manager VMM console | - | [Hyper-V] |
ETERNUS SF Storage Cruiser clients | 14.2 or later | Necessary when checking the detailed information of storage using the admin client. |
*1: When connecting with the ROR Console, use Compatibility View Settings.
*2: To display the management window of ServerView Operations Manager, please refer to the ServerView Operations Manager manual.
To display the VM management console or the console window, version 1.5 or later is necessary.
Resource Orchestrator cannot be used in combination with Resource Coordinator, Cloud Infrastructure Management Software, or the following products.
List of Exclusive Software
Operating System Type | Product Name | Version and Level | Remarks |
|---|---|---|---|
Windows | INTERSTAGE | All versions | Here "INTERSTAGE" includes the following products:
|
Interstage Apcoordinator | All versions | - | |
Interstage Application Server | All versions | Here "Interstage Application Server" includes the following products:
| |
Interstage Apworks | All versions | - | |
Interstage Application Framework Suite | All versions | - | |
Interstage Business Application Server | All versions | Here "Interstage Business Application Server" includes the following products:
| |
Interstage Business Process Manager | All versions | - | |
Interstage Business Process Manager Analytics | All versions | - | |
Interstage BPM Flow | All versions | - | |
Interstage Service Integrator | All versions | - | |
Interstage Security Directory | All versions | - | |
Interstage Shunsaku Data Manager | All versions | - | |
Interstage Studio | All versions | - | |
Interstage Traffic Director | All versions | - | |
INTERSTAGE WEBCOORDINATOR | All versions | - | |
Interstage Web Server | All versions | - | |
ObjectDirectory | All versions | - | |
Systemwalker Centric Manager (x64) | All versions | Here "Systemwalker Centric Manager" includes the following products:
| |
Systemwalker IT Change Manager | All versions | Here "Systemwalker IT Change Manager" includes the following products:
| |
Systemwalker IT Process Master | All versions | - | |
Systemwalker Operation Manager | V13.3 or earlier | Here "Systemwalker Operation Manager" includes the following products:
| |
Systemwalker PKI Manager | All versions | - | |
Securecrypto Library | All versions | - | |
Systemwalker Resource Coordinator | All versions | Here "Systemwalker Resource Coordinator" includes the following products:
| |
Systemwalker Runbook Automation (Admin Server) | 15.0.0 or earlier | - | |
Systemwalker Runbook Automation (Linked Server/Relay Server/Business Server) | All versions | - | |
Systemwalker Service Quality Coordinator | V13.5 or earlier | - | |
Systemwalker Service Catalog Manager | V14g | - | |
Systemwalker Software Configuration Manager | V14.0.0 | - | |
Systemwalker Software Configuration Manager (Admin Server) | V14.1.0 (*1) | - | |
Systemwalker Software Configuration Manager (Linked Server/Public Server) | All versions | - | |
Cloud Infrastructure Management Software | All versions | - | |
SystemcastWizard | All versions | - | |
SystemcastWizard Professional | All versions | - | |
SystemcastWizard Lite | All versions | - | |
ServerView Installation Manager (*3) | All versions | - | |
ServerView Resource Coordinator VE | All versions | - | |
ServerView Resource Orchestrator | All versions | - | |
ServerView Deployment Manager (*4) | All versions | - | |
Premeo Premium Agent | All versions | - | |
TeamWARE Office Server | All versions | - | |
TRADE MASTER | All versions | - | |
Linux | Interstage Application Server | All versions | Here "Interstage Application Server" includes the following products:
|
Interstage Application Framework Suite | All versions | - | |
Interstage Business Application Server | All versions | Here "Interstage Business Application Server" includes the following products:
| |
Interstage BPM Flow | All versions | - | |
Interstage Business Process Manager | All versions | - | |
Interstage Business Process Manager Analytics | All versions | - | |
Interstage Web Server | All versions | - | |
Interstage Service Integrator | All versions | Here "Interstage Service Integrator" includes the following products:
| |
Interstage Shunsaku Data Manager | All versions | - | |
Interstage Traffic Director | All versions | - | |
Server System Manager | All versions | - | |
Systemwalker Centric Manager (Intel 64 version) | All versions | Here "Systemwalker Centric Manager" includes the following products:
| |
Systemwalker IT Process Master | All versions | - | |
Systemwalker IT Change Manager | All versions | Here "Systemwalker IT Change Manager" includes the following products:
| |
Systemwalker Operation Manager | V13.3 or earlier | Here "Systemwalker Operation Manager" includes the following products:
| |
Systemwalker Resource Coordinator | All versions | Here "Systemwalker Resource Coordinator" includes the following products:
| |
Systemwalker Runbook Automation (Admin Server) | 15.0.0 or earlier | - | |
Systemwalker Runbook Automation (Linked Server/Relay Server/Business Server) | All versions | - | |
Systemwalker Service Quality Coordinator | V13.5 or earlier | - | |
Systemwalker Service Catalog Manager | V14g | - | |
Systemwalker Software Configuration Manager (Admin Server) | V14.1.0 (*1) | - | |
Systemwalker Software Configuration Manager (Linked Server/Public Server) | All versions | - | |
Cloud Infrastructure Management Software | All versions | - | |
ServerView Resource Coordinator VE | All versions | - | |
ServerView Resource Orchestrator | All versions | - | |
Premeo Premium Agent | All versions | - |
*1: When the software parameter setting function is used, the media and a license for Systemwalker Software Configuration Manager is necessary.
*2: When Systemwalker Service Quality Coordinator is used, the media and a license for Systemwalker Service Quality Coordinator are necessary.
*3: Because the manager of Resource Orchestrator contains a PXE server, it cannot be used together with the PXE server that is required for the remote installation function of ServerView Installation Manager.
*4: ServerView Deployment Manager can be installed after this product has been installed.
*5: Systemwalker Runbook Automation can be installed after this product has been installed.
Virtual Environment | Product Name | Version and Level | Remarks |
|---|---|---|---|
VMware | ServerView Deployment Manager (*1) | All versions | - |
Hyper-V | Server System Manager | All versions | - |
SystemcastWizard | All versions | - | |
SystemcastWizard Professional | All versions | - | |
SystemcastWizard Lite | All versions | - | |
Systemwalker Service Quality Coordinator | All versions | - | |
Systemwalker Service Catalog Manager | V14g | - | |
Linux | Server System Manager | All versions | - |
SystemcastWizard | All versions | - | |
SystemcastWizard Professional | All versions | - | |
SystemcastWizard Lite | All versions | - | |
ServerView Deployment Manager (*1) | All versions | - | |
Oracle VM | ServerView Deployment Manager (*1) | All versions | - |
Solaris containers | Server System Manager (Manager only) | All versions | - |
Systemwalker Service Quality Coordinator | V13.5 or earlier | - | |
ETERNUS SF Disk Space Monitor | All versions | - |
*1: ServerView Deployment Manager can be installed after this product has been installed.
Operating System Type | Product Name | Version and Level | Remarks |
|---|---|---|---|
Windows | Systemwalker Service Quality Coordinator | V13.5 or earlier | - |
Systemwalker Service Catalog Manager | V14g | - | |
ETERNUS SF Disk Space Monitor | All versions | - | |
Linux | Systemwalker Service Quality Coordinator | V13.5 or earlier | - |
Systemwalker Service Catalog Manager | V14g | - | |
ETERNUS SF Disk Space Monitor | All versions | - | |
Solaris | Server System Manager (Manager only) | All versions | - |
Systemwalker Service Quality Coordinator | V13.5 or earlier | - | |
ETERNUS SF Disk Space Monitor | All versions | - |
*2: When Systemwalker Service Quality Coordinator is used, the media and a license for Systemwalker Service Quality Coordinator are necessary.
Basic Mode
Exclusive software in Basic mode are as follows:
Software | Product Name |
|---|---|
[Windows Manager] | ServerView Installation Manager (*1) |
ServerView Deployment Manager | |
[Linux Manager] | 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) |
Agent [Xen] [KVM] | - |
Agent [Oracle VM] | ServerView Deployment Manager (*2) |
Agent [Solaris Containers] | Server System Manager (Manager only) |
Agent [Solaris] | Server System Manager (Manager only) |
*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 this product has been installed. For details on installation, refer to "2.2 Installing Agents" in the "Setup Guide CE".
Note
Resource Orchestrator managers contain some components of SystemcastWizard Professional. Therefore, they cannot be placed and operated on the same subnet as SystemcastWizard.
Furthermore, take caution regarding the following points when placing SystemcastWizard Professional (hereinafter ScwPro) or SystemcastWizard Lite (hereinafter ScwLite) on the same subnet.
Operate ScwPro and ScwLite in non-aggressive mode on a simple DHCP server. Make sure that the IP address scope allocated to the simple DHCP server does not conflict with the IP addresses for Resource Orchestrator managed servers.
Resource Orchestrator managed servers cannot be managed simultaneously by ScwPro and ScwLite.
Do not register servers already registered with Resource Orchestrator on ScwPro or ScwLite.
To simultaneously operate multiple servers, change the multicast IP address settings for ScwPro so that they do not conflict with the Resource Orchestrator managers.
Resource Orchestrator managers contain some functions of DHCP servers and PXE servers. Do not use products or services that use the functions of other DHCP servers or PXE servers on the admin server. Such products or services can be placed in the same network as Resource Orchestrator managers.
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 (*)
ServerStart (when using the remote installation function)
ServerView Installation Manager
Solaris JumpStart
* Note: 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 on co-existence with ServerView Deployment Manager, refer to "Appendix B Co-Existence with ServerView Deployment Manager" in the "Setup Guide VE".
[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, ensure 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.
[Physical Servers]
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 | Required Disk Space (Unit: MB) |
|---|---|---|
[Windows Manager] | Installation_folder (*) | 4000 |
[Linux Manager] | /opt | 3525 |
/etc/opt | 255 | |
/var/opt | 768 | |
Agent [Windows] [Hyper-V] | Installation_folder (*) | 300 |
Agent [Linux] | /opt | 250 |
/etc/opt | 55 | |
/var/opt | 105 | |
Agent [VMware] [Xen] [KVM] [Oracle VM] | /opt | 95 |
/etc/opt | 5 | |
/var/opt | 5 | |
Agent [Solaris] | /opt | 350 |
/etc/opt | 15 | |
/var/opt | 5 |
* Note: The installation folder name specified when this software is installed.
The default folder name when Windows is installed on C:\ is as follows:
When using a 64-bit (x64) OS
Default value: C:\Program Files (x86)\Resource Orchestrator
When using a 32-bit (x86) OS
Default value: C:\Program Files\Resource Orchestrator
When using Resource Orchestrator, the following disk space is required for each folder, in addition to static disk space.
Software | Folder | Required Disk Space (Unit: MB) |
|---|---|---|
[Windows Manager] | Installation_folder (*1) | 9080 + Number_of_managed_servers * 4 |
Environmental_data_storage_area | ||
Performance_display_information_storage_area(*8) | ||
Metering log_storage_area(*9) | ||
Image_file_storage_folder (*2) | Image_file_storage_area (*3) | |
Backup_storage_folder_for_configuration_definition_information | Backup_storage_area_for_configuration_definition_information (*4) | |
L-Server_restoration_log_storage_folder | L-Server_restoration_log_storage_folder (*4) | |
Network_device_configuration_file_storage_folder (*10) | Network_device_configuration_file_storage_area (*11) | |
[Linux Manager] | /etc | 2 |
/var/opt | 9080 + Number_of_managed_servers * 4 | |
Environmental_data_storage_area | ||
Performance_display_information_storage_area(*8) | ||
Metering log_storage_area(*9) | ||
Image_file_storage_directory (*2) | Image_file_storage_area (*3) | |
Backup_storage_folder_for_configuration_definition_information | Backup_storage_area_for_configuration_definition_information (*4) | |
L-Server_restoration_log_storage_folder | L-Server_restoration_log_storage_folder (*4) | |
Network_device_configuration_file_storage_folder (*10) | Network_device_configuration_file_storage_area (*11) | |
Agent [Windows] | Installation_folder (*1) | 60 |
Log_data(*5) | ||
Agent [Hyper-V] | Installation_folder (*1) | 60 |
Log_data(*6) | ||
Agent [Linux] | /etc | 1 |
/var/opt | 1 | |
Log_data(*7) | ||
Agent [VMware] [Xen] [KVM] [Oracle VM] | /etc | 1 |
/var/opt | 1 | |
Agent [Solaris] | /etc | 1 |
/var/opt | 1 | |
Log_data(*7) | ||
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.
The default folder name when Windows is installed on C:\ is as follows:
When using a 64-bit (x64) OS
Default value: C:\Program Files (x86)\Resource Orchestrator
When using a 32-bit (x86) OS
Default value: C:\Program Files\Resource Orchestrator
*2: The name of the storage folder (directory) specified for image files when this software is installed.
[Windows]
The default folder name when Windows is installed on C:\ is as follows:
When using a 64-bit (x64) OS
Default value: C:\Program Files (x86)\Resource Orchestrator\SVROR\ScwPro\depot
When using a 32-bit (x86) OS
Default value: C:\Program Files\Resource Orchestrator\SVROR\ScwPro\depot
[Linux]
The default is as follows:
/var/opt/FJSVscw-deploysv/depot
*3: The image storage area when using cloning images for cloning of physical servers.
For details on the amount of space for the image storage area, refer to "Image File for Physical Servers Storage Area".
Cloning images of L-Servers are stored in image pools regardless of server types.
*4: The backup storage area for configuration definition information and the L-Server restoration log storage area can be specified in the definition file. Estimate according to the location of the specified disk. For details on the disk capacity and content of the backup storage area for configuration definition information and the L-Server restoration log storage area, refer to "10.1 Backup and Restoration of Admin Servers" in the "Operation Guide CE".
*5: The approximate estimate value is 60 MB.
*6: The approximate estimate value is 60 MB * VM guest number.
*7: The approximate estimate value is 100MB.
The size of log data changes according to L-Server configurations.
When it is necessary to estimate the detailed data, refer to the "How to estimate the amount of space required for the log data ("Troubleshoot" directory)" section in the "Systemwalker Service Quality Coordinator Installation Guide".
*8: For information disk capacity for performance display, there are storage areas for dashboard information and usage condition information. The disk capacity necessary for resources is indicated below.
Target Resource | Required Disk Space |
|---|---|
Dashboard information | The size changes depending on the number of L-Server templates and tenants changed. Disk Space = (67.0 + (55.5 * number of tenants)) * 1.2 (MB) |
Usage condition information | The size will increase and decrease depending on the numbers of VM hosts and VM guests. [VMware] N1 = 2.0, N2 = 16.5 [Hyper-V] N1 = 92.0, N2 = 26.0 [Xen] [KVM] N1 = 102.0, N2 = 7.0 |
*9: The necessary disk capacity for metering logs is indicated as follows:
Metering Logs per day * capacity for one year |
The conditions of the base for the formula for disk space above and the formula of the metering logs per day are indicated as below.
Item | Estimated Value | |
|---|---|---|
Number of operating L-Platforms | 1000 | |
Number of resources per L-Platform | L-Server | 1 |
Expansion disk | 1 | |
Software | 2 | |
Usage status |
| |
Online backup frequency |
| |
|
*10: The name of the storage folder (directory) specified for network device configuration files.
[Windows]
The default folder name when Windows is installed on C:\ is as follows:
When using a 64-bit (x64) OS
C:\Program Files (x86)\Resource Orchestrator\SVROR\Manager\var\netdevice
When using a 32-bit (x86) OS
C:\Program Files\Resource Orchestrator\SVROR\Manager\var\netdevice
[Linux]
The default is as follows:
/var/opt/FJSVrcvmr/netdevice
*11: Size increases or decreases depending on the number of network devices managed by the network device file management function, and the number of generations of the network device configuration file of each network device.
The size required for each network device is equal to the number of generations of the network device configuration file * 512 KB.
The maximum number of network devices that can be managed by the network device configuration file management function is 72.
Environmental_data_storage_area
The environmental data storage area is the area necessary when using power monitoring.
The environmental data storage area is located in the installation folder of the admin server, and is used to store environmental data collected from power monitoring targets and aggregate data.
The amount of space that is necessary for the environmental data storage area can be determined from the number of power monitoring targets being registered, the polling interval, and the period the environmental data is to be stored for.
For details on each setting, refer to "13.1.1 Settings for the Power Monitoring Environment".
Estimate the necessary space using the following formula.
Necessary disk space (MB) = (detail_storage_period_(months) * 6 / polling_interval_(minutes) + 10) * 3 * number_of_power_monitoring_targets |
Image File for Physical Servers Storage Area
The image file storage area for physical servers is necessary when performing backup and cloning.
The image file storage area is secured on an admin server as an area to store the image files (system images and cloning images) collected through the backup and cloning of managed servers.
Note
Create the image file storage area on the local disk of the admin server, or SAN storage. It is not possible to specify folders on network drives, shared folders (NFS, SMB, etc.) on other machines on a network, or UNC format folders.
The space necessary for the image file storage area is the total amount of disk space necessary for the "system image storage area", the "cloning image storage area", and the "temporary work area".
Estimate the necessary space based on the disk space required for each storage area using the following formula.
Estimate the necessary space for the image file storage area using the following procedure.
Calculate the size of image files.
Calculate the image file sizes as base data for estimating the required disk space for A, B, and C indicated above.
The calculation method is given below.
File size of image files = disk_space_per_managed_server * compression_ratio |
When system construction using the same software configuration has been performed before, use the consumed disk space of that system (the sum of the disk space for each partition when dividing one disk into multiple partitions).
Check the consumed disk space using the relevant OS function.
When system construction using the same software configuration has not been performed before, calculate the disk space from the required disk space indicated in the installation guide for each piece of software.
For the OS, refer to "Examples of Calculation".
The compression ratio involved when storing the consumed disk space of managed servers as an image file on the admin server.
Compression ratio is dependent on file content, and usually a compression ratio of around 50% can be expected. When there are many files that have already been compressed (installation media of software, image data, or other media), the overall compression ratio is lower.
For the OS, refer to "Examples of Calculation".
An example of the calculation of disk space and the compression ratio directly after OS installation is given below.
Example
Examples of Calculation
For Windows Server 2003
Used disk space: 1.9 GB -> After compression: 0.9 GB Compression ratio: 0.9/1.9 = 47%
Calculate the space required for the system image storage area.
The system image storage area is the area necessary when performing backup. Secure space for each managed server for which backup system images are made.
This is not necessary when not performing backup.
Calculate the size of the system image storage area based on the image file size of step 1. Estimate the area for each managed server for which system images are backed up using the following formula, and use the total as the estimated size.
Disk space required for the system image storage area = file_size_of_image_files * number_of_versions |
The number of versions of system images. By default, up to three versions of system images can be managed.
Point
By reducing the number of versions of system images saved it is possible to reduce the amount of space required for the system image storage area.
For details of how to change the number of system images saved, refer to "5.9 rcxadm imagemgr" in the "Reference Guide (Command/XML) CE".
The following is an example when three managed servers, A, B, and C are performing backup of system images, and the used disk space and compression ratios are expected to be the following values.
Example
Example of Estimation
Server A - Image_file_size: 3.0 GB (Used disk space: 6.0 GB, Compression ratio 50%)
Server B - Image_file_size: 1.6 GB (Used disk space: 4.0 GB, Compression ratio 40%)
Server C - Image_file_size: 1.6 GB (Used disk space: 4.0 GB, Compression ratio 40%)
(3.0 * 3) + (1.6 * 3) + (1.6 * 3) = 18.6 (GB)
Calculate the space required for the cloning image storage area.
The cloning image storage area is the area necessary when performing cloning. Secure space for each managed server for which cloning images are collected.
This is not necessary when not performing cloning.
Calculate the size of the cloning image storage area based on the image file size of step 1. Estimate the area for each managed server from which cloning images are collected using the following formula, then set the total as the estimated size.
Disk space required for the cloning image storage area = file_size_of_image_files * number_of_versions |
The number of versions of cloning images. By default, up to three versions of cloning images can be managed.
Point
By reducing the number of versions of cloning images saved it is possible to reduce the amount of space required for the cloning image storage area.
For details of how to change the number of cloning images saved, refer to "5.9 rcxadm imagemgr" in the "Reference Guide (Command/XML) CE".
The following is an example when managed servers A and B are used to collect cloning images, and the used disk space and compression ratios are expected to be the following values.
Example
Example of Estimation
Server A - Image_file_size: 3.0 GB (Used disk space: 6.0 GB, Compression ratio 50%)
Server B - Image_file_size: 1.6 GB (Used disk space: 4.0 GB, Compression ratio 40%)
(3.0 * 3) + (1.6 * 3) = 13.8 (GB)
Calculate the space required for the temporary work area.
When collecting system images or cloning images, the temporary work area is necessary to keep the former version of images until collection of new system images or cloning images is completed.
This is not necessary when not performing backup or cloning.
Calculate the size of the temporary work area based on the image file size of step 1.
Estimate the largest size of the image files of all managed servers, and determine the necessary area using the following formula.
Disk space required for the temporary work area = largest_image_file_size * image_file_collection_multiplicity |
Estimate image file collection multiplicity using operational designs in which image file collection (system image backup and cloning image collection) is simultaneously performed at the limit of multiplicity for multiple managed servers under management of an admin server. However, as Resource Orchestrator is designed not to exceed four multiplicities in order to reduce the load on the admin servers, the maximum multiplicity is 4.
The following is an example when three managed servers, A, B, and C are used to collect system images or cloning images, and the file size of each image file is as below. In this example, the image file collection multiplicity is 3.
Example
Example of Estimation
Server A - Image_file_size: 3.0 GB (Used disk space: 6.0 GB, Compression ratio 50%)
Server B - Image_file_size: 1.6 GB (Used disk space: 4.0 GB, Compression ratio 40%)
Server C - Image_file_size: 1.6 GB (Used disk space: 4.0 GB, Compression ratio 40%)
3.0 * 3 = 9.0 (GB)
Calculate the space necessary for the image file storage area based on the disk space calculated in 2. to 4.
Calculate the total amount of required space for A, B, and C calculated in steps 2 to 4. (A: Disk area required for system image storage area, B: Disk area required for cloning image storage area, C: Disk area required for temporary work area).
The memory size listed below is required when using Resource Orchestrator.
Software | Memory Size (Unit: MB) |
|---|---|
[Windows Manager] | 6656 |
[Linux Manager] | 10752 |
Agent [Windows] [Hyper-V] | 512 |
Agent [Linux] | 256 |
Agent [Solaris] | 64 |
Agent [VMware] | 32 |
Agent [Xen] [KVM] | 32 |
Agent [Oracle VM] | 32 |
