This section explains the requirements for installation of Resource Coordinator VE.
The basic software listed below is required when using Resource Coordinator VE.
Software | Basic Software (OS) | 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, Standard Edition | SP2 supported. | |
Microsoft(R) Windows Server(R) 2003 R2, Standard Edition | SP2 or later supported. | |
Agent[Hyper-V] | Microsoft(R) Windows Server(R) 2008 Standard (x64) | The Server Core installation option is not 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 [Solaris] | Solaris(TM) 10 Operating System | Supported after 05/09. |
Agent [VMware] | VMware(R) Infrastructure 3 | Install Resource Coordinator VE on the VMware ESX host. Use the VMware Service Console for installation. |
Agent [Xen] | Citrix XenServer(TM) 5.5 | - |
HBA address rename setup service [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. | |
Microsoft(R) Windows Vista(R) Business | - | |
Microsoft(R) Windows(R) XP Professional operating system | SP2 or later supported. | |
Microsoft(R) Windows(R) 7 Professional | - | |
HBA address rename setup service [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. |
It is not necessary to install Resource Coordinator VE 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 | - |
Microsoft(R) Windows(R) XP Professional operating system | SP2 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. |
Software | Basic Software (OS) | Patch ID/Bundle Update |
|---|---|---|
Manager [Windows] | Microsoft(R) Windows Server(R) 2003 R2 Standard x64 Edition | Hotfix KB942589 (*1) |
Microsoft(R) Windows Server(R) 2003 R2 Enterprise x64 Edition | Hotfix KB942589 (*1) | |
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 | None | - |
Agent [Linux] | 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) | |
Red Hat(R) Enterprise Linux(R) AS (v.4 for x86) | Bundle Update U06091 (Update 4 compatible) | |
Red Hat(R) Enterprise Linux(R) ES (v.4 for x86) | Kernel Update kit (Update4/4.5/4.6/4.7/4.8 compatible) | |
Red Hat(R) Enterprise Linux(R) AS (v.4 for EM64T) | Bundle Update U06091 (Update 4 compatible) | |
Red Hat(R) Enterprise Linux(R) ES (v.4 for EM64T) | Kernel Update kit (Update4/4.5/4.6/4.7/4.8 compatible) | |
SUSE Linux Enterprise Server 10 SP2 (for x86) | Kernel-2.6.16.60-0.23 or later | |
SUSE Linux Enterprise Server 10 SP2 (for AMD64, Intel64) | Kernel-2.6.16.60-0.23 or later | |
SUSE Linux Enterprise Server 10 SP3 (for x86) | Kernel-2.6.16.60-0.50.1 or later | |
SUSE Linux Enterprise Server 10 SP3 (for AMD64, Intel64) | Kernel-2.6.16.60-0.50.1 or later | |
SUSE Linux Enterprise Server 11 (for x86) | Kernel-2.6.27.19-5 or later | |
SUSE Linux Enterprise Server 11 (for AMD64, Intel64) | Kernel-2.6.27.19-5 or later | |
Agent [Solaris] | None | - |
Agent [VMware] | None | - |
Agent [Xen] | None | - |
HBA address rename setup service [Windows] | None | - |
HBA address rename setup service [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) |
*1: Required when managed servers belonging to different subnets from the admin server are managed.
The software listed below is required when using Resource Coordinator VE.
Software | Required Software | Version | Remarks |
|---|---|---|---|
Manager [Windows] | ServerView Operations Manager for Windows (*1) | V4.20.25 or later | Necessary when using VIOM coordination or invoking the Web UI of server management software from the RC console. |
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 | 2.0 | Required when using migration of VM guests on VMware. | |
Microsoft(R) System Center Virtual Machine Manager 2008 R2 | - | Required when using migration, or setting or releasing VM maintenance mode of VM guests on Hyper-V. | |
Windows PowerShell | 2.0 | Required when using migration, or setting or releasing VM maintenance mode of VM guests on Hyper-V. | |
SNMP Trap Service | - | - | |
DHCP Server (OS standard service) | - | Required when managed servers belonging to different subnets from the admin server are managed. | |
Manager [Linux] | ServerView Operations Manager for Linux | V4.81.05 or later | Necessary when using invoking the Web UI of server management software from the RC console. |
Microsoft(R) LAN Manager module | - | Necessary when using backup and restore, or cloning. | |
PRIMECLUSTER Enterprise Edition | 4.2A00 or later | When an admin server is in a cluster configuration, one of the following software is necessary. | |
PRIMECLUSTER HA Server | 4.2A00 or later | ||
PRIMECLUSTER GLS | - | Necessary when performing redundancy of the admin LAN for admin servers. | |
net-snmp package | - | Included in OS installation media. | |
Agent [Windows/Hyper-V] | ServerView Agent for Windows (*1) | V4.50.05 or later | - |
"setupcl.exe" module | - | Necessary when using backup and restore, or cloning. Please refer to the Microsoft website and obtain the latest module. (*4) With Windows Server 2008, these modules are configured by default so there is no need to obtain them. | |
BACS | - | Necessary when performing redundancy of the admin LAN or public LAN for managed servers. | |
ServerView RAID (*1) | - | Necessary when a RAID is composed of local disks (*3). | |
Agent [Linux] | ServerView Agents Linux (*1) | V4.90.14 or later | - |
ServerView RAID (*1) | - | Necessary when a RAID is composed of local disks (*3). | |
Agent | PRIMECLUSTER GLS (*1) | 4.2A00 or later | Necessary when performing redundancy of the admin LAN or public LAN for managed servers. |
Agent [Solaris] | PRIMECLUSTER GLS | 4.2 or later | Necessary when performing redundancy of the admin LAN or 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). | |
Agent [Xen] | ServerView Agent for Linux (*1) | V4.81-14 or later | - |
ServerView RAID (*1) | - | Necessary when a RAID is composed of local disks (*3). | |
HBA address rename setup service [Windows] | Microsoft(R) Internet Explorer | 7 | Necessary for displaying the online help. |
HBA address rename setup service [Linux] | Firefox | 3 | Necessary for displaying the online help. |
*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 August 2010) |
*3: Local disks include internal disks of servers and storage blades.
*4: The file to obtain varies depending on the CPU architecture (x86, x64) and OS version of the system installation is to be performed on. Please refer to the Microsoft website for the module to obtain.
Microsoft download website
URL(x86): URL(x64): |
After obtaining the newest module, extract it in a work folder (such as C:\temp) of the system for installation.
Refer to "2.2.1.1 Software Preparation and Checks" for the extraction method.
After agent installation is complete, the module is no longer necessary.
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(R) Virtual Infrastructure Client | 2.0 | Necessary on admin clients when using the functions for coordinating with VMware or the VM management software on managed servers. [VMware] |
VMware vSphere(TM) Client | 4.0 | |
Hyper-V Manager | - | Necessary when using the function for coordinating with Hyper-V on managed servers on admin clients. [Hyper-V] |
Microsoft(R) System Center Virtual Machine Manager 2008 R2 VMM Administrator console | - | Necessary on admin clients when using the function for coordinating with VM management software. [Hyper-V] |
XenCenter | - | Necessary on admin clients when using the function for coordinating with Citrix XenServer on managed servers. [Xen] |
*1: To display the management window of ServerView Operations Manager, please refer to the ServerView Operations Manager manual.
To display the VM management console, 1.5 or later is necessary.
See
Installation of Related ServerView Products
For advisory notes regarding the installation of the manager of "ServerView Operations Manager", refer to "Settings for ServerView Operations Manager for Windows" in "2.1.1.1 Software Preparation and Checks".
Resource Coordinator VE cannot be used in combination with Resource Coordinator or the following products.
Systemwalker Resource Coordinator Virtual server Edition is the name of earlier versions of Resource Coordinator VE. Earlier versions cannot be used in combination with Resource Coordinator VE, but upgrading is possible. For upgrading, refer to "Chapter 4 Upgrading from Earlier Versions".
Software | Product |
|---|---|
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 [Solaris] | Server System Manager (Manager only) |
Agent [VMware] | ServerView Deployment Manager (*2) |
Agent [Xen] | ServerView Deployment Manager (*2) |
HBA address rename setup service [Windows] | ServerView Deployment Manager |
HBA address rename setup service [Linux] | Server System Manager |
*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 VE has been installed. For installation, please refer to "2.2 Agent Installation".
Note
Resource Coordinator VE 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 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 Coordinator VE. For details, refer to "Appendix H Co-Existence with ServerView Deployment Manager" of the "ServerView Resource Coordinator VE Setup Guide".
[Windows]
Depending on the domain type, there may be cases in which backup and restore, cloning, and server switchover using the backup and restore method cannot be used, or additional operations on managed servers are necessary.
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 backup or restore 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 Coordinator VE, 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) |
|---|---|---|
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/Solaris/VMware/Xen] | /opt | 90 |
/etc/opt | 5 | |
/var/opt | 5 | |
HBA address rename setup service [Windows] | Installation_folder (*1) | 75 |
HBA address rename setup service [Linux] | /opt | 90 |
/etc/opt | 1 | |
/var/opt | 3 |
*1: The installation folder name specified when this software is installed.
The default when Windows has been installed in C:\ is as follows:
C:\Program Files\Resource Coordinator VE
When using Resource Coordinator VE, the following dynamic disk space is required.
The following disk space is required for each folder, in addition to static disk space.
Software | Folder | Required Disk Space (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 | |
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 | |
Agent [Windows/Hyper-V] | Installation_folder (*1) | 60 |
Agent [Linux/Solaris/VMware/Xen] | /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.
The default when Windows has been installed in C:\ is as follows:
C:\Program Files\Resource Coordinator VE
*2: The name of the storage folder (directory) specified for image files when this software is installed.
[Windows]
The default when Windows has been installed in C:\ is as follows:
C:\Program Files\Resource Coordinator VE\ScwPro\depot
[Linux]
The default is as follows:
/var/opt/FJSVscw-deploysv/depot
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 the setting values, refer to "3.4.1 Settings for the Power Monitoring Environment" of the "ServerView Resource Coordinator VE Setup Guide".
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 Storage Area
The image file storage area 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_generations |
The number of generations of system images. By default, up to three generations of system images can be managed.
Point
By reducing the number of generations 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 "6.3.1.3 Changing the Maximum Number of System Image Versions" of the "ServerView Resource Coordinator VE Setup Guide".
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_generations |
The number of generations of cloning images. By default, up to three generations of cloning images can be managed.
Point
By reducing the number of generations 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 "6.3.1.3 Changing the Maximum Number of System Image Versions" of the "ServerView Resource Coordinator VE Setup Guide".
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 generation 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 Coordinator VE 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 steps 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).
When using this Resource Coordinator VE, the following memory is required.
Software | Required Memory Capacity (Unit: MB) | Remarks |
|---|---|---|
Manager [Windows] | 3072 | - |
Manager [Linux] | 3072 | - |
Agent [Windows/Hyper-V] | 32 | - |
Agent [Linux] | 32 | - |
Agent [Solaris] | 32 | - |
Agent [VMware] | 32 | - |
Agent [Xen] | 32 | - |
HBA address rename setup service [Windows] | 32 | - |
HBA address rename setup service [Linux] | 128 | - |
The following memory is necessary for admin clients.
Software | Required Memory Capacity (Unit: MB) | Remarks |
|---|---|---|
Microsoft(R) Internet Explorer | 512 | - |
