Top
ServerView Resource Orchestrator V3.2.0 Overview
FUJITSU Software

6.1.2 Software Requirements (Cloud Edition)

This section explains the software requirements for installation of Resource Orchestrator.


6.1.2.1 Required Basic Software

The basic software listed below is required when using Resource Orchestrator.

Required Basic Software

Table 6.48 [Windows Manager] (*1) (*2)

Basic Software (OS)

Remarks

Microsoft(R) Windows Server(R) 2008 R2 Standard
Microsoft(R) Windows Server(R) 2008 R2 Enterprise
Microsoft(R) Windows Server(R) 2008 R2 Datacenter

The Server Core installation option is not supported. In clustered manager configurations on physical servers, as Microsoft Failover Cluster (MSFC) is used, Enterprise or Datacenter is required.

Microsoft(R) Windows Server(R) 2012 Standard
Microsoft(R) Windows Server(R) 2012 Datacenter
Microsoft(R) Windows Server(R) 2012 R2 Standard
Microsoft(R) Windows Server(R) 2012 R2 Datacenter

The Server Core installation option is not supported.

Physical L-Servers do not support the following OSs.

  • Microsoft(R) Windows Server(R) 2012 R2 Standard

  • Microsoft(R) Windows Server(R) 2012 R2 Datacenter

*1: This service also can be run on a VM guest OS as virtualization software.

*2: To use the Chinese display of the ROR console, use the English version OS.

Table 6.49 [Linux Manager] (*1)

Basic Software (OS)

Remarks

Red Hat(R) Enterprise Linux(R) 5.3 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.4 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.5 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.6 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.7 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.8 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.9 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.10 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.11 (for Intel64)
Red Hat(R) Enterprise Linux(R) 6.2 (for Intel64)
Red Hat(R) Enterprise Linux(R) 6.3 (for Intel64)
Red Hat(R) Enterprise Linux(R) 6.4 (for Intel64)
Red Hat(R) Enterprise Linux(R) 6.5 (for Intel64)
Red Hat(R) Enterprise Linux(R) 6.6 (for Intel64)
Red Hat(R) Enterprise Linux(R) 6.7 (for Intel64) (*2)

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 "6.1.2.3 Required Packages".

The Linux Kernel version for each hardware model corresponds to the version supported by Fujitsu.

*1: This service also can be run on a VM guest OS as virtualization software.
*2: Use the internal authentication function.

Table 6.50 Agent [Windows]

Basic Software (OS)

Remarks

Microsoft(R) Windows Server(R) 2003 R2, Standard Edition
Microsoft(R) Windows Server(R) 2003 R2, Enterprise Edition
Microsoft(R) Windows Server(R) 2003 R2, Standard x64 Edition
Microsoft(R) Windows Server(R) 2003 R2, Enterprise x64 Edition

SP2 or later supported.

Microsoft(R) Windows Server(R) 2008 Standard (x86, x64)
Microsoft(R) Windows Server(R) 2008 Enterprise (x86, x64)
Microsoft(R) Windows Server(R) 2008 R2 Standard
Microsoft(R) Windows Server(R) 2008 R2 Enterprise
Microsoft(R) Windows Server(R) 2008 R2 Datacenter

The Server Core installation option is not supported.

Microsoft(R) Windows Server(R) 2012 Standard
Microsoft(R) Windows Server(R) 2012 Datacenter
Microsoft(R) Windows Server(R) 2012 R2 Standard
Microsoft(R) Windows Server(R) 2012 R2 Datacenter

The Server Core installation option is not supported.

Table 6.51 Agent [Hyper-V]

Basic Software (OS)

Remarks

Microsoft(R) Windows Server(R) 2008 R2 Enterprise
Microsoft(R) Windows Server(R) 2008 R2 Datacenter
Microsoft(R) Windows Server(R) 2012 Standard
Microsoft(R) Windows Server(R) 2012 Datacenter
Microsoft(R) Windows Server(R) 2012 R2 Standard
Microsoft(R) Windows Server(R) 2012 R2 Datacenter

The Server Core installation option is not supported.
Switch on the role of Hyper-V.
Add MSFC.
Only Windows managers are 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.
Dynamic memory and memory weight function cannot be used in Windows Server 2008 R2 without applying any Service Packs.

Table 6.52 Agent [Linux]

Basic Software (OS)

Remarks

Red Hat(R) Enterprise Linux(R) 5 (for x86)
Red Hat(R) Enterprise Linux(R) 5 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.1 (for x86)
Red Hat(R) Enterprise Linux(R) 5.1 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.2 (for x86)
Red Hat(R) Enterprise Linux(R) 5.2 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.3 (for x86)
Red Hat(R) Enterprise Linux(R) 5.3 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.4 (for x86)
Red Hat(R) Enterprise Linux(R) 5.4 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.5 (for x86)
Red Hat(R) Enterprise Linux(R) 5.5 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.6 (for x86)
Red Hat(R) Enterprise Linux(R) 5.6 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.7 (for x86)
Red Hat(R) Enterprise Linux(R) 5.7 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.8 (for x86)
Red Hat(R) Enterprise Linux(R) 5.8 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.9 (for x86)
Red Hat(R) Enterprise Linux(R) 5.9 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.10 (for x86)
Red Hat(R) Enterprise Linux(R) 5.10 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.11 (for x86)
Red Hat(R) Enterprise Linux(R) 5.11 (for Intel64)
Red Hat(R) Enterprise Linux(R) 6.2 (for x86)
Red Hat(R) Enterprise Linux(R) 6.2 (for Intel64)
Red Hat(R) Enterprise Linux(R) 6.3 (for x86)
Red Hat(R) Enterprise Linux(R) 6.3 (for Intel64)
Red Hat(R) Enterprise Linux(R) 6.4 (for x86)
Red Hat(R) Enterprise Linux(R) 6.4 (for Intel64)
Red Hat(R) Enterprise Linux(R) 6.5 (for x86)
Red Hat(R) Enterprise Linux(R) 6.5 (for Intel64)
Red Hat(R) Enterprise Linux(R) 6.6 (for x86)
Red Hat(R) Enterprise Linux(R) 6.6 (for Intel64)
Red Hat(R) Enterprise Linux(R) 6.7 (for x86)
Red Hat(R) Enterprise Linux(R) 6.7 (for Intel64)
Red Hat(R) Enterprise Linux(R) 6.8 (for x86)
Red Hat(R) Enterprise Linux(R) 6.8 (for Intel64)
Red Hat(R) Enterprise Linux(R) 7.0 (for Intel64) (*)
SUSE(R) Linux Enterprise Server 11 for x86
SUSE(R) Linux Enterprise Server 11 for EM64T

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 "6.1.2.3 Required Packages".

The Linux Kernel version for each hardware model corresponds to the version supported by Fujitsu.

* Note: When using the PRIMEQUEST series, RHEL7 is not supported.

Table 6.53 Agent [Solaris] [Solaris Zones]

Basic Software (OS)

Remarks

Solaris(TM) 10 Operating System
Solaris(TM) 11 Operating System (*1)

  • Solaris(TM) 10 Operating System

    05/09 (Update7) or later versions are supported.

  • Solaris(TM) 11 Operating System

    11/11 or later versions are supported. (*2)
    For some functions, only 11/11.1 or later versions are supported.

    For details, refer to "11.1 Deciding Server Virtualization Software" in the "Design Guide CE".

When using SAN boot, refer to the manual for Fibre Channel card driver, "SPARC Enterprise - ETERNUS SAN Boot Environment Build Guide".

About required packages, refer to "6.1.2.3 Required Packages".

*1: [Solaris Zones]
Availability of features varies according to the version of the VM host. When operating a VM host directly, even if an L-Server is migrated between VM hosts of different versions, management of the L-Server can be continued, but the available functions will differ depending on the VM host versions.
*2: Management using the following functions of Solaris 11.2 is not possible.

Table 6.54 Agent [OVM for SPARC]

Basic Software (OS)

Remarks

Solaris(TM) 11 Operating System

When using SAN boot, refer to the manual for Fibre Channel card driver, "SPARC Enterprise - ETERNUS SAN Boot Environment Build Guide".

When a guest domain on OVM for SPARC is registered as a VM Host, it is necessary to install an agent in that guest domain.

Table 6.55 Agent [VMware]

Basic Software (OS)

Remarks

VMware vSphere 4.0
VMware vSphere 4.1
VMware vSphere 5.0
VMware vSphere 5.1
VMware vSphere 5.5
VMware vSphere 6.0

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 VMware vSphere 4.1 or later can be used for managed servers.
There is no need to install Resource Orchestrator on VMware ESXi, but agents must be registered.

Note

When using Windows Server 2012 as a guest OS, the following issue, as described by VMware, Inc., may cause the OS to not operate correctly.

URL:
https://kb.vmware.com/selfservice/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=2059549

When using Windows Server 2012 as a guest OS, configure the OS in advance, referring to the following.

"SCSI Controller Definition File" in "8.2.1 Creating Definition Files" in the "Setup Guide CE"

Table 6.56 Agent [Xen]

Basic Software (OS)

Remarks

Red Hat(R) Enterprise Linux(R) 5.4 (for x86)
Red Hat(R) Enterprise Linux(R) 5.4 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.5 (for x86)
Red Hat(R) Enterprise Linux(R) 5.5 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.6 (for x86)
Red Hat(R) Enterprise Linux(R) 5.6 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.7 (for x86)
Red Hat(R) Enterprise Linux(R) 5.7 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.8 (for x86)
Red Hat(R) Enterprise Linux(R) 5.8 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.9 (for x86)
Red Hat(R) Enterprise Linux(R) 5.9 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.10 (for x86)
Red Hat(R) Enterprise Linux(R) 5.10 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.11 (for x86)
Red Hat(R) Enterprise Linux(R) 5.11 (for Intel64)

-

Table 6.57 Agent [KVM]

Basic Software (OS)

Remarks

Red Hat(R) Enterprise Linux(R) 6.2 (for Intel64)
Red Hat(R) Enterprise Linux(R) 6.3 (for Intel64)
Red Hat(R) Enterprise Linux(R) 6.4 (for Intel64)
Red Hat(R) Enterprise Linux(R) 6.5 (for Intel64)
Red Hat(R) Enterprise Linux(R) 6.6 (for Intel64)
Red Hat(R) Enterprise Linux(R) 6.7 (for Intel64)
Red Hat(R) Enterprise Linux(R) 6.8 (for Intel64)

Intel64 and AMD64 are supported. (*)

* Note: For details, refer to the following section in the "Red Hat Enterprise Linux 6 Virtualization Host Configuration and Guest Installation Guide".

The manuals for Red Hat Enterprise Linux can be referred to from the following URL.

URL:
https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/index.html
Table 6.58 Agent [OVM for x86 2.2]

Basic Software (OS)

Remarks

Oracle VM Server for x86 v2.2

-

Table 6.59 Agent [OVM for x86 3.x]

Basic Software (OS)

Remarks

Oracle VM Server for x86 v3.2.1
Oracle VM Server for x86 v3.2.2
Oracle VM Server for x86 v3.2.3
Oracle VM Server for x86 v3.2.4
Oracle VM Server for x86 v3.2.6
Oracle VM Server for x86 v3.2.7
Oracle VM Server for x86 v3.2.8
Oracle VM Server for x86 v3.3.1
Oracle VM Server for x86 v3.3.2
Oracle VM Server for x86 v3.3.3
Oracle VM Server for x86 v3.3.4

-

Table 6.60 Agent [Citrix Xen]

Basic Software (OS)

Remarks

Citrix(R) XenServer(R) 5.5
Citrix Essentials(TM) for XenServer 5.5, Enterprise Edition
Citrix(R) XenServer(R) 5.6
Citrix(R) XenServer(R) 5.6 SP2
Citrix(R) XenServer(R) 6.0
Citrix Essentials(TM) for XenServer 6.0, Enterprise Edition
Citrix(R) XenServer(R) 6.0.2
Citrix(R) XenServer(R) 6.1.0
Citrix(R) XenServer(R) 6.2.0

Citrix(R) XenServer(R) 6.0 or earlier versions of software support the same scope as ROR VE.

Table 6.61 HBA address rename Setup Service [Windows] (*)

Basic Software (OS)

Remarks

Microsoft(R) Windows Server(R) 2003 R2, Standard Edition
Microsoft(R) Windows Server(R) 2003 R2, Enterprise Edition
Microsoft(R) Windows Server(R) 2003 R2, Standard x64 Edition
Microsoft(R) Windows Server(R) 2003 R2, Enterprise x64 Edition

SP2 or later supported.

Microsoft(R) Windows Server(R) 2008 Standard (x86, x64)
Microsoft(R) Windows Server(R) 2008 Enterprise (x86, x64)
Microsoft(R) Windows Server(R) 2008 R2 Standard
Microsoft(R) Windows Server(R) 2008 R2 Enterprise
Microsoft(R) Windows Server(R) 2008 R2 Datacenter

The Server Core installation option is not supported.

Microsoft(R) Windows Server(R) 2012 Standard
Microsoft(R) Windows Server(R) 2012 Datacenter
Microsoft(R) Windows Server(R) 2012 R2 Standard
Microsoft(R) Windows Server(R) 2012 R2 Datacenter

The Server Core installation option is not supported.

Microsoft(R) Windows Vista(R) Business
Microsoft(R) Windows Vista(R) Enterprise
Microsoft(R) Windows Vista(R) Ultimate

-

Microsoft(R) Windows(R) 7 Professional
Microsoft(R) Windows(R) 7 Ultimate

-

Windows(R) 8 Pro
Windows(R) 8 Enterprise
Windows(R) 8.1 Pro
Windows(R) 8.1 Enterprise

-

* Note: This is necessary when creating physical L-Servers using rack mount or tower servers.
When using rack mount servers that are supported by VIOM, target servers can be managed using VIOM.
This service also can be run on a VM guest OS as virtualization software.

Table 6.62 HBA address rename Setup Service [Linux] (*)

Basic Software (OS)

Remarks

Red Hat(R) Enterprise Linux(R) 5.4 (for x86)
Red Hat(R) Enterprise Linux(R) 5.4 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.5 (for x86)
Red Hat(R) Enterprise Linux(R) 5.5 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.6 (for x86)
Red Hat(R) Enterprise Linux(R) 5.6 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.7 (for x86)
Red Hat(R) Enterprise Linux(R) 5.7 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.8 (for x86)
Red Hat(R) Enterprise Linux(R) 5.8 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.9 (for x86)
Red Hat(R) Enterprise Linux(R) 5.9 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.10 (for x86)
Red Hat(R) Enterprise Linux(R) 5.10 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.11 (for x86)
Red Hat(R) Enterprise Linux(R) 5.11 (for Intel64)
Red Hat(R) Enterprise Linux(R) 6.2 (for x86)
Red Hat(R) Enterprise Linux(R) 6.2 (for Intel64)
Red Hat(R) Enterprise Linux(R) 6.3 (for x86)
Red Hat(R) Enterprise Linux(R) 6.3 (for Intel64)
Red Hat(R) Enterprise Linux(R) 6.4 (for x86)
Red Hat(R) Enterprise Linux(R) 6.4 (for Intel64)
Red Hat(R) Enterprise Linux(R) 6.5 (for x86)
Red Hat(R) Enterprise Linux(R) 6.5 (for Intel64)
Red Hat(R) Enterprise Linux(R) 6.6 (for x86)
Red Hat(R) Enterprise Linux(R) 6.6 (for Intel64)
Red Hat(R) Enterprise Linux(R) 6.7 (for x86)
Red Hat(R) Enterprise Linux(R) 6.7 (for Intel64)
Red Hat(R) Enterprise Linux(R) 6.8 (for x86)
Red Hat(R) Enterprise Linux(R) 6.8 (for Intel64)

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 "6.1.2.3 Required Packages".

The Linux Kernel version for each hardware model corresponds to the version supported by Fujitsu.

* Note: This is necessary when creating physical L-Servers using rack mount or tower servers.
When using rack mount servers that are supported by VIOM, target servers can be managed using VIOM.
This service also can be run on a VM guest OS as virtualization software.

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.

Certain functions of server virtualization software cannot be used when that software is managed using Resource Orchestrator.

[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.

Table 6.63 List of Functions Not Supported by Resource Orchestrator

Server Virtualization Software

Function that Is not Supported

VMware vSphere 4.0
VMware vSphere 4.1
VMware vSphere 5.0
VMware vSphere 5.1
VMware vSphere 5.5
VMware vSphere 6.0

Cisco Nexus 1000V virtual switch

VMware vSphere 5.5
VMware vSphere 6.0

vSphere Flash Read Cache

Microsoft(R) System Center Virtual Machine Manager 2008 R2
Microsoft(R) System Center 2012 Virtual Machine Manager
Microsoft(R) System Center 2012 R2 Virtual Machine Manager

Saving in the virtual machine library

The following functions can be used together on Microsoft(R) System Center Virtual Machine Manager 2008 R2 SP1 or later.

  • Movement of storage areas

  • Movement changing the virtual machine storage destination

Oracle VM Manager

Template

Windows Server 2012
Windows Server 2012 R2

Hyper-V replica

Note

  • If an L-Server is created with a specified Windows image, when deploying the image use Sysprep, provided by Microsoft, to reconfigure 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, Sysprep can be executed a maximum of three times on the following OSs.

    • Microsoft(R) Windows Server(R) 2008 R2

    • Microsoft(R) Windows Server(R) 2008

    • Microsoft(R) Windows(R) 7

    • Microsoft(R) Windows Vista(R)

    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.

[OVM for x86 2.2]
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.

Table 6.64 Required Basic Software: Admin Clients

Basic Software (OS)

Remarks

Microsoft(R) Windows Vista(R) Business
Microsoft(R) Windows Vista(R) Enterprise
Microsoft(R) Windows Vista(R) Ultimate

SP1 or later supported.

Microsoft(R) Windows(R) 7 Professional
Microsoft(R) Windows(R) 7 Ultimate

-

Windows(R) 8 Pro
Windows(R) 8 Enterprise
Windows(R) 8.1 Pro
Windows(R) 8.1 Enterprise

-

Windows(R) 10 Pro
Windows(R) 10 Enterprise

-

Microsoft(R) Windows Server(R) 2003 R2, Standard Edition
Microsoft(R) Windows Server(R) 2003 R2, Enterprise Edition
Microsoft(R) Windows Server(R) 2003 R2, Standard x64 Edition
Microsoft(R) Windows Server(R) 2003 R2, Enterprise x64 Edition

SP2 or later supported.

Microsoft(R) Windows Server(R) 2008 Standard (x86, x64)
Microsoft(R) Windows Server(R) 2008 Enterprise (x86, x64)
Microsoft(R) Windows Server(R) 2008 R2 Standard
Microsoft(R) Windows Server(R) 2008 R2 Enterprise
Microsoft(R) Windows Server(R) 2008 R2 Datacenter

The Server Core installation option is not supported.

Microsoft(R) Windows Server(R) 2012 Standard
Microsoft(R) Windows Server(R) 2012 Datacenter
Microsoft(R) Windows Server(R) 2012 R2 Standard
Microsoft(R) Windows Server(R) 2012 R2 Datacenter

-


6.1.2.2 Required Patches

When using Resource Orchestrator, the following patches are required.

Table 6.65 [Windows Manager]

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.

Table 6.66 [Linux Manager]

Basic Software (OS)

Patch ID/Bundle Update (*)

Red Hat(R) Enterprise Linux(R) 5 (for x86)

Bundle Update U09091 (5.4 compatible)
Bundle Update U10041 (5.5 compatible)

Red Hat(R) Enterprise Linux(R) 5 (for Intel64)

Bundle Update U09091 (5.4 compatible)
Bundle Update U10041 (5.5 compatible)

* Note: Necessary when upgrading.

Table 6.67 Agent [Windows]

Basic Software (OS)

Patch ID/Bundle Update

Microsoft(R) Windows Server(R) 2008

Hotfix KB2487376 (*)

Microsoft(R) Windows Server(R) 2008 R2

Hotfix KB2344941 (*)

Microsoft(R) Windows Server(R) 2008 R2 SP1

Hotfix KB2550978 (*)

Necessary when using server switchover to a spare server on a managed server that is one of the following models:

Table 6.68 Agent [Hyper-V]

Basic Software (OS)

Patch ID/Bundle Update

None

-

Table 6.69 Agent [Linux]

Basic Software (OS)

Patch ID/Bundle Update (*)

Red Hat(R) Enterprise Linux(R) 5 (for x86)

Bundle Update U07121 (5.1 compatible)
Bundle Update U08071 (5.2 compatible)
Bundle Update U09031 (5.3 compatible)
Bundle Update U09091 (5.4 compatible)
Bundle Update U10041 (5.5 compatible)

Red Hat(R) Enterprise Linux(R) 5 (for Intel64)

Bundle Update U07121 (5.1 compatible)
Bundle Update U08071 (5.2 compatible)
Bundle Update U09031 (5.3 compatible)
Bundle Update U09091 (5.4 compatible)
Bundle Update U10041 (5.5 compatible)

Table 6.70 Agent [Solaris] [Solaris Zones] [OVM for SPARC]

Basic Software (OS)

Patch ID/Bundle Update

Solaris(TM) 11 Operating System

SRU12111(SRU1.4) or later (*)

* Note: Required when using OVM for SPARC for a managed server.

Table 6.71 Agent [VMware]

Basic Software (OS)

Patch ID/Bundle Update

None

-

Table 6.72 Agent [Xen] [Citrix Xen] [KVM]

Basic Software (OS)

Patch ID/Bundle Update

None

-

Table 6.73 Agent [OVM for x86 2.2] [OVM for x86 3.x]

Basic Software (OS)

Patch ID/Bundle Update

None

-

Table 6.74 HBA address rename setup service [Windows]

Basic Software (OS)

Patch ID/Bundle Update

None

-

Table 6.75 HBA address rename Setup Service [Linux]

Basic Software (OS)

Patch ID/Bundle Update (*)

Red Hat(R) Enterprise Linux(R) 5 (for x86)

Bundle Update U09091 (5.4 compatible)
Bundle Update U10041 (5.5 compatible)

Red Hat(R) Enterprise Linux(R) 5 (for Intel64)

Bundle Update U09091 (5.4 compatible)
Bundle Update U10041 (5.5 compatible)

* 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.


6.1.2.3 Required Packages

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 packages followed by "(32bit)", install either the i386 or i686 package.
For the items with no architecture to be installed is specified, install the package of the same architecture as the OS.

Table 6.76 Required Packages of Manager for Red Hat Enterprise Linux 6 [Linux Manager]

Conditions

Required Packages

Always required

alsa-lib(32bit)
apr(32bit)
apr-util(32bit)
audit
audit-libs(32bit)
cloog-ppl
compat-expat1(32bit)
compat-libtermcap(32bit)
compat-openldap(32bit)
compat-readline5(32bit)
cpp
cracklib(32bit)
cyrus-sasl-lib(32bit)
db4(32bit)
elfutils-libelf(32bit)
expat(32bit)
file
gcc
gcc-c++
glibc(32bit)
glibc-devel(32bit)
glibc-headers
kernel-headers
keyutils-libs(32bit)
krb5-libs(32bit)
libattr(32bit)
libcap(32bit)
libcom_err(32bit)
libgcc(32bit)
libgomp
libICE(32bit)
libselinux(32bit)
libSM(32bit)
libstdc++(32bit)
libstdc++-devel
libtool-ltdl(32bit)
libuuid(32bit)
libX11(32bit)
libX11-common(noarch)
libXau(32bit)
libxcb(32bit)
libXext(32bit)
libXi(32bit)
libxml2(32bit)
libXp(32bit)
libXt(32bit)
libXtst(32bit)
make
mpfr
ncurses-libs(32bit)
net-snmp
net-snmp-utils
nspr
nss
nss-util
nss-softokn-freebl(32bit)
openssl(32bit) (*1)
openssl098e(32bit) (*1)
pam(32bit)
perl
perl-libs
perl-Module-Pluggable
perl-Pod-Escapes
perl-Pod-Simple
perl-version
policycoreutils
policycoreutils-python
ppl
readline(32bit)
redhat-lsb
sqlite(32bit)
sysstat
tcsh
unixODBC(32bit)
unzip
X-Window (*2)
zlib(32bit)

Necessary when managing a managed server within a separate subnet to the admin server

openldap

*1: For openssl(32bit) and openssl098e(32bit), install the latest package.
*2: Install an OS, specifying a package.

Table 6.77 Required Packages of Manager for Red Hat Enterprise Linux 5 [Linux Manager]

Conditions

Required Packages

Always required

apr(32bit)
apr-util(32bit)
elfutils-libelf(32bit)
glibc(32bit)
libtermcap(32bit)
libxml2(32bit)
libXp(32bit)
libxslt(32bit)
net-snmp
net-snmp-utils
openssl(32bit) (*1)
postgresql-libs(32bit)
readline(32bit)
redhat-lsb
sysstat
unzip
X-Window (*2)
zlib(32bit)

*1: For openssl(32bit), install the latest package.
*2: Install an OS, specifying a package.

Table 6.78 Required Packages of Agent for Red Hat Enterprise Linux 7 [Linux]

Conditions

Required Packages

Always required

alsa-lib(32bit)
audit
glibc(32bit)
libgcc(32bit)
libICE(32bit)
libSM(32bit)
libstdc++(32bit)
libtool-ltdl(32bit)
libuuid(32bit)
libX11(32bit)
libXau(32bit)
libxcb(32bit)
libXext(32bit)
libXi(32bit)
libXt(32bit)
libXtst(32bit)
ncurses-libs(32bit)
net-snmp-utils
policycoreutils
policycoreutils-python
readline(32bit)
sqlite(32bit)
sysfsutils
unixODBC(32bit)

Table 6.79 Required Packages of Agent for Red Hat Enterprise Linux 6 [Linux] [KVM]

Conditions

Required Packages

Always required

alsa-lib(32bit)
audit
glibc(32bit)
libgcc(32bit)
libICE(32bit)
libSM(32bit)
libstdc++(32bit)
libtool-ltdl(32bit)
libuuid(32bit)
libX11(32bit)
libXau(32bit)
libxcb(32bit)
libXext(32bit)
libXi(32bit)
libXt(32bit)
libXtst(32bit)
ncurses-libs(32bit)
net-snmp-utils
policycoreutils
policycoreutils-python
readline(32bit)
sqlite(32bit)
sysfsutils
unixODBC(32bit)

Necessary when installing an agent (dashboard functions)

Necessary when the OS architecture is Intel64 or x86

redhat-lsb
sysstat

Necessary when the OS architecture is Intel64

libxml2(32bit)

Necessary when the OS architecture is x86

ncurses

[KVM]
Necessary when either of the following conditions is met:

  • The OS architecture is Intel64 and a Linux (SELinux) cloning image is being used

  • The OS architecture is Intel64, the OS type is Linux, and a cloning image with "Virtual Disk" configured for the storage location is being used

fuse.x86_64

  • For RHEL6.2

    libguestfs-mount.x86_64

  • For RHEL6.3 or later

    libguestfs-tools-c.x86_64

[KVM]
Necessary when all of the following conditions are met:

  • The OS architecture is Intel64

  • When using a Windows cloning image

libguestfs-tools.x86_64
libguestfs-tools-c.x86_64
libguestfs-winsupport.x86_64 (*)
perl-libintl.x86_64
perl-Sys-Guestfs.x86_64
perl-Sys-Virt.x86_64
perl-XML-Parser.x86_64
perl-XML-Writer.noarch
perl-XML-XPath.noarch


For RHEL6.2, the following packages are necessary.

guestfish.x86_64
libguestfs-mount.x86_64

* Note: Obtain libguestfs-winsupport from the "RHEL V2VWIN (v. 6 for 64-bit x86_64)" channel for Red Hat Network.
For details, refer to the following section in the "Virtualization Administration Guide".

The manuals for Red Hat Enterprise Linux can be referred to from the following URL.

URL: 
https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/index.html
Table 6.80 Required Packages of Agent for Red Hat Enterprise Linux 5 [Linux] [Xen]

Conditions

Required Packages

Always required

alsa-lib(32bit)
glibc(32bit)
libgcc(32bit)
libICE(32bit)
libselinux(32bit)
libsepol
libSM(32bit)
libstdc++(32bit)
libX11(32bit)
libXau(32bit)
libXdmcp
libXext(32bit)
libXi(32bit)
libXt(32bit)
libXtst(32bit)
net-snmp-utils
readline(32bit)
sqlite(32bit)

Necessary when installing an agent (dashboard functions)

redhat-lsb
sysstat

Table 6.81 Required Packages of HBA address rename Setup Service for Red Hat Enterprise Linux 6 [Linux]

Conditions

Required Packages

Always required

alsa-lib(32bit)
audit
Desktop (*)
glibc(32bit)
libgcc(32bit)
libICE(32bit)
libSM(32bit)
libstdc++(32bit)
libtool-ltdl(32bit)
libuuid(32bit)
libX11(32bit)
libXau(32bit)
libxcb(32bit)
libXext(32bit)
libXi(32bit)
libXt(32bit)
libXtst(32bit)
ncurses-libs(32bit)
policycoreutils
policycoreutils-python
readline(32bit)
sqlite(32bit)
unixODBC(32bit)
X-Window (*)

* Note: Install an OS, specifying a package.

Table 6.82 Required Packages of HBA address rename Setup Service for Red Hat Enterprise Linux 5 [Linux] [Xen]

Conditions

Required Packages

Always required

alsa-lib(32bit)
Desktop (*)
e2fsprogs-libs
glibc(32bit)
libgcc(32bit)
libICE(32bit)
libSM(32bit)
libstdc++(32bit)
libX11(32bit)
libXau(32bit)
libXdmcp
libXext(32bit)
libXi(32bit)
libXt(32bit)
libXtst(32bit)
ncurses(32bit)
readline(32bit)
sqlite(32bit)
X-Window (*)

* Note: Install an OS, specifying a package.

Table 6.83 Required Packages of Agent [Solaris][Solaris Zones][OVM for SPARC][OVM for x86 3.x]

Basic Software (OS)

Required Packages

[Solaris][Solaris Zones][OVM for SPARC]

Solaris 11

compatibility/ucb
system/accounting/legacy-accounting

[OVM for x86 3.x]

Always required

redhat-lsb
sysstat


6.1.2.4 Required Software

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.

Table 6.84 [Windows Manager]

Required Software

Version

Remarks

ServerView Operations Manager

V5.30 - V7.02
V7.11.07

Necessary to use the following functions:

  • Single Sign-On

  • VIOM coordination

  • Calling of the Web UI of server management software from the ROR console

  • Using VMware ESXi as a managed server on PRIMERGY series or PRIMEQUEST servers

  • Starting the console window of a physical server

V6.21 - V7.02
V7.11.07

This is necessary when viewing the ServerView Fabric Manager Web UI from the ROR console.

Microsoft(R) LAN Manager module

-

Used when performing backup and restore, or cloning for physical servers.
Obtain it from the Microsoft FTP site. (*1)

For how to install it, refer to "Microsoft LAN Manager Module" in "2.1.1.2 Software Preparation and Checks" in the "Setup Guide CE".

BACS
or
Intel PROSet
or
PRIMECLUSTER GLS for Windows
or
OneCommand NIC Teaming and
Multiple VLAN Manager

-

Necessary when performing redundancy of the admin LAN for admin servers.

When using PRIMECLUSTER GLS, also apply the latest patches for GLS.

ServerView Virtual-IO Manager

2.6 or later

Necessary when creating physical L-Servers using blade servers.
Refer to the README of VIOM for the servers supported by VIOM.

VMware vCenter Server

4.0
4.1
5.0
5.1
5.5
6.0

[VMware]
Necessary for management of VM guests and VM hosts.
Can be placed on the same admin server as the manager or on another server.

SNMP Service

-

This is used to monitor events that occur on managed servers.
It is used by ServerView Operations Manager.

SNMP Trap Service (Standard OS service)

-

This is used to monitor events that occur on managed servers.
It is used by ServerView Operations Manager.
This is necessary when receiving SNMP Trap from the server.

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
or
Microsoft(R) System Center 2012 Virtual Machine Manager
or
Microsoft(R) System Center 2012 R2 Virtual Machine Manager

-

[Hyper-V]
Necessary for management of VM guests and VM hosts.
Can be placed on the same admin server as the manager or on another server.
Multiple library servers can be configured.
Configure control settings for a maximum of 31 sessions, referring to "SCVMM Server Web Services for Management Settings" in "E.2.5 Pre-setup Preparations in Hyper-V Environments" in the "Design Guide CE".
It is necessary to install Microsoft(R) SQL Server, Windows AIK, or Windows ADK beforehand, when using Microsoft(R) System Center 2012 Virtual Machine Manager.
It is necessary to install Microsoft(R) SQL Server and Windows ADK beforehand, when using Microsoft(R) System Center 2012 R2 Virtual Machine Manager.
For details, confirm the system requirements for the relevant product.
When only using Microsoft(R) System Center 2012 Virtual Machine Manager or later, the content of disks deleted from virtual L-Servers can be saved.

Windows PowerShell

2.0 or later

[Hyper-V]
Necessary for management of VM guests and VM hosts.

ETERNUS SF Storage Cruiser Manager

14.2/14.2A

  • Necessary on the managed server (Fujitsu M10/SPARC Enterprise) when using the storage affinity switchover method for server switchover.

  • Necessary on the managed server (PRIMERGY) when creating a physical L-Server with an ETERNUS LUN connected.

  • Apply one of the following:

    • Patch T004615WP-08 or later for ETERNUS SF Storage Cruiser14.2 manager

    • Patch T005766WP-01 or later for ETERNUS SF Storage Cruiser14.2A manager

15.0 or later

  • Necessary on the managed server (Fujitsu M10/SPARC Enterprise) when using the storage affinity switchover method for server switchover.

  • Necessary on the managed server (PRIMERGY) when creating a physical L-Server with an ETERNUS LUN connected.

    For ETERNMUS LUN connected to a physical L-Server, the following functions of ETERNUS are supported in addition to the ones supported by 14.2/14.2A:

    • Thin Provisioning

    • Dynamic LUN Mirroring

    • Automatic Storage Layering

  • Necessary when using the Disaster Recovery function of DR Option and ETERNUS storage.

16.0 or later

  • Necessary on the managed server (Fujitsu M10/SPARC Enterprise) when using the storage affinity switchover method for server switchover.

  • Necessary on the managed server (PRIMERGY) when creating a physical L-Server with an ETERNUS LUN connected.

    For ETERNMUS LUN connected to a physical L-Server, the following functions of ETERNUS are supported in addition to the ones supported by 14.2/14.2A:

    • Thin Provisioning

    • Dynamic LUN Mirroring

    • Automatic Storage Layering

  • Necessary when using the Disaster Recovery function of DR Option and ETERNUS storage.

  • Apply the following patches:

    • Patch T009283WP-03 or later for ETERNUS SF Storage Cruiser 16.0 manager

  • When managing ETERNUS DX200 S3/DX500 S3/DX600 S3 using ETERNUS SF Storage Cruiser 16.1 or later, note the following points:

    • Do not use the CA port that is a target of CA port pairing performed using the Storage Cluster function, on physical L-Servers. For how to specify the CA ports used by physical L-Servers, refer to "7.1.1 Creating Definition Files Combining Ports of SAN Storage" in the "Setup Guide CE".

    • Do not connect a managed server (Fujitsu M10/SPARC Enterprise) which uses the storage affinity switchover method for server switchover, to the CA port that is a target of CA port pairing performed using the Storage Cluster function.

    • Do not specify the CA port used by an already created physical L-Server or a managed server (Fujitsu M10/SPARC Enterprise) which uses using the storage affinity switchover method for server switchover, as the target of CA port pairing performed using the Storage Cluster function.

  • When installing ETERNUS SF Storage Cruiser only to use VVOL as a disk for virtual L-Servers, it is not necessary to install it on the same server as the manager.

ETERNUS SF AdvancedCopy Manager Copy Control Module

15.0 or later

  • Necessary on managed servers (PRIMERGY) when creating physical L-Servers with ETERNUS LUNs connected and using the following ETERNUS functions on ETERNUS LUNs connected to physical L-Servers:

    • Dynamic LUN Mirroring

  • Necessary when using the Disaster Recovery function of DR Option and ETERNUS storage.

  • Necessary when using high availability for storage chassis on physical L-Servers with ETERNUS LUNs connected.

16.0 or later

  • Necessary on managed servers (PRIMERGY) when creating physical L-Servers with ETERNUS LUNs connected and using the following ETERNUS functions on ETERNUS LUNs connected to physical L-Servers:

    • Dynamic LUN Mirroring

  • Necessary when using the Disaster Recovery function of DR Option and ETERNUS storage.

  • Necessary when using high availability for storage chassis on physical L-Servers with ETERNUS LUNs connected.

  • Apply the following patches:

    • Patch T009283WP-03 or later for ETERNUS SF Storage Cruiser 16.0 manager

NaviSphere Manager

6.29

Necessary when connecting an EMC CLARiiON LUN to a physical L-Server.

NavisecCLI

7.30 or later

Necessary when connecting an EMC CLARiiON LUN or EMC VNX 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.
Necessary to connect the server on which Solutions Enabler is operated to storage using a Fibre Channel connection.

Can be installed on the same admin server as the manager or on another admin server.

Oracle VM Manager

2.2

[OVM for x86 2.2]
Necessary for management of VM guests and VM hosts.
Oracle VM Manager cannot be installed in Windows environments.
For details on the installation environment, refer to the Oracle manuals. (*2)

3.2.1 or later

[OVM for x86 3.x]
Necessary for management of VM guests and VM hosts.
Oracle VM Manager cannot be installed in Windows environments.
For details on the installation environment, refer to the Oracle manuals. (*2)

BMC BladeLogic Server Automation

8.3 (*3)

Necessary when using coordination of registration and deletion of managed servers, cloning, and software deployment in PRIMERGY and PRIMEQUEST.

[Solaris Zones] [OVM for SPARC]
Necessary when using the functions with "Yes (*)" described in "Table: Functional Differences Depending on Server Virtualization Software" in "11.1 Deciding Server Virtualization Software" in the "Design Guide CE".
Can be placed on the same server as the manager (recommended) or on another server.
When operating managers in clusters, place it on a different server.

BMC BladeLogic Server Automation Console

8.3

Necessary when using coordination of registration and deletion of managed servers, cloning, and software deployment in PRIMERGY and PRIMEQUEST.

[Solaris Zones] [OVM for SPARC]
Necessary when using the functions with "Yes (*)" described in "Table: Functional Differences Depending on Server Virtualization Software" in "11.1 Deciding Server Virtualization Software" in the "Design Guide CE".
Install it on the same server as the manager.

SAN Client CLI

7.00

Necessary when connecting a Virtual Device of FalconStor NSS to a physical L-Server.
Download this software from the FalconStor customer support portal.

ServerView Fabric Manager

V2.00.40 or later

Necessary when registering ServerView Fabric Manager as Converged Fabric management software.

VMware Horizon View

5.2.x
5.3.x
6.0.x

Necessary for using the VDI coordination function.

Microsoft Visual C++ 2008 Redistributable Package (x86)

-

Necessary to use V3.2.0 (T011582WP-01) or later.

*1: Obtain it from the following Microsoft FTP site.

Microsoft FTP site

URL: ftp://ftp.microsoft.com/bussys/clients/msclient/dsk3-1.exe

*2: Check the following Oracle manuals:

URL: http://www.oracle.com/technetwork/documentation/vm-096300.html

*3 [OVM for SPARC]
When using a Solaris 11.2 AI server and creating a virtual L-Server, it is necessary to apply a Hotfix.
Contact Fujitsu technical staff, and obtain the following Hotfix.


Required Software (Linux Manager)

Required Software for Linux Manager is as follows.

Unless specified otherwise, install on the same server as the manager.

Table 6.85 [Linux Manager]

Required Software

Version

Remarks

ServerView Operations Manager

V5.30 - V7.00
V7.02

Necessary to use the following functions:

  • Single Sign-On

  • VIOM coordination

  • Calling of the Web UI of server management software from the ROR console

  • Using VMware ESXi as a managed server on PRIMERGY series or PRIMEQUEST servers

  • Starting the console window of a physical server

Microsoft(R) LAN Manager module

-

Necessary when using backup and restore, or cloning.
Obtain it from the Microsoft FTP site. (*1)

For how to install it, refer to "Microsoft LAN Manager Module" in "2.1.2.2 Software Preparation and Checks" in the "Setup Guide CE".

ServerView Virtual-IO Manager

2.6 or later

Necessary when creating physical L-Servers using blade servers.
Refer to the README of VIOM for the servers supported by VIOM.

PRIMECLUSTER GLS

-

Necessary when performing redundancy of the admin LAN for admin servers.

VMware vCenter Server

4.0
4.1
5.0
5.1
5.5
6.0

[VMware]
Necessary for management of VM guests and VM hosts.
VMware vCenter Server cannot be installed in Linux environments.
For details on the installation environment, refer to the VMware manuals. (*2)

ETERNUS SF Storage Cruiser Manager

14.2/14.2A

  • Necessary on the managed server (Fujitsu M10/SPARC Enterprise) when using the storage affinity switchover method for server switchover.

  • Necessary on the managed server (PRIMERGY) when creating a physical L-Server with an ETERNUS LUN connected.

  • Apply one of the following:

    • Patch T004706LP-08 or later (x86), T004617LP-08 (Intel64) or later for ETERNUS SF Storage Cruiser14.2 manager

    • Patch T005768LP-01 or later (x86), T005769LP-01 (Intel64) or later for ETERNUS SF Storage Cruiser14.2A manager

15.0 or later

  • Necessary on the managed server (Fujitsu M10/SPARC Enterprise) when using the storage affinity switchover method for server switchover.

  • Necessary on the managed server (PRIMERGY) when creating a physical L-Server with an ETERNUS LUN connected.

    For ETERNMUS LUN connected to a physical L-Server, the following functions of ETERNUS are supported in addition to the ones supported by 14.2/14.2A:

    • Thin Provisioning

    • Dynamic LUN Mirroring

    • Automatic Storage Layering

16.0 or later

  • Necessary on the managed server (Fujitsu M10/SPARC Enterprise) when using the storage affinity switchover method for server switchover.

  • Necessary on the managed server (PRIMERGY) when creating a physical L-Server with an ETERNUS LUN connected.

    For ETERNMUS LUN connected to a physical L-Server, the following functions of ETERNUS are supported in addition to the ones supported by 14.2/14.2A:

    • Thin Provisioning

    • Dynamic LUN Mirroring

    • Automatic Storage Layering

  • Apply the following patches:

    • Patch T009286LP-03 or later for ETERNUS SF Storage Cruiser 16.0 manager

  • When managing ETERNUS DX200 S3/DX500 S3/DX600 S3 using ETERNUS SF Storage Cruiser 16.1 or later, note the following points:

    • Do not use the CA port that is a target of CA port pairing performed using the Storage Cluster function, on physical L-Servers. For how to specify the CA ports used by physical L-Servers, refer to "7.1.1 Creating Definition Files Combining Ports of SAN Storage" in the "Setup Guide CE".

    • Do not connect a managed server (Fujitsu M10/SPARC Enterprise) which uses the storage affinity switchover method for server switchover, to the CA port that is a target of CA port pairing performed using the Storage Cluster function.

    • Do not specify the CA port used by an already created physical L-Server or a managed server (Fujitsu M10/SPARC Enterprise) which uses using the storage affinity switchover method for server switchover, as the target of CA port pairing performed using the Storage Cluster function.

ETERNUS SF AdvancedCopy Manager Copy Control Module

15.0 or later

  • Necessary on managed servers (PRIMERGY) when creating physical L-Servers with ETERNUS LUNs connected and using the following ETERNUS functions on ETERNUS LUNs connected to physical L-Servers:

    • Dynamic LUN Mirroring

  • Necessary when using high availability for storage chassis on physical L-Servers with ETERNUS LUNs connected.

16.0 or later

  • Necessary on managed servers (PRIMERGY) when creating physical L-Servers with ETERNUS LUNs connected and using the following ETERNUS functions on ETERNUS LUNs connected to physical L-Servers:

    • Dynamic LUN Mirroring

  • Necessary when using high availability for storage chassis on physical L-Servers with ETERNUS LUNs connected.

  • Apply the following patches:

    • Patch T009286LP-03 or later for ETERNUS SF AdvancedCopy Manager 16.0 manager

NaviSphere Manager

6.29

Necessary when connecting an EMC CLARiiON LUN to a physical L-Server.

NavisecCLI

7.30 or later

Necessary when connecting an EMC CLARiiON LUN or EMC VNX 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.
Necessary to connect the server on which Solutions Enabler is operated to storage using a Fibre Channel connection.

Can be installed on the same admin server as the manager or on another admin server.

Oracle VM Manager

2.2

[OVM for x86 2.2]
Necessary for management of VM guests and VM hosts.
Oracle VM Manager may not be able to be installed in the same environment as the manager of Resource Orchestrator.
For details on the installation environment, refer to the Oracle manuals. (*3)

3.2.1 or later

[OVM for x86 3.x]
Necessary for management of VM guests and VM hosts.
Oracle VM Manager may not be able to be installed in the same environment as the manager of Resource Orchestrator.
For details on the installation environment, refer to the Oracle manuals. (*3)

DHCP Server (Standard OS service)

-

Necessary when managing a managed server within a separate subnet to the admin server.

BMC BladeLogic Server Automation

8.3

Necessary when using coordination of registration and deletion of managed servers, cloning, and software deployment in PRIMERGY and PRIMEQUEST.

[Solaris Zones] [OVM for SPARC]
Necessary when using the functions with "Yes (*)" described in "Table: Functional Differences Depending on Server Virtualization Software" in "11.1 Deciding Server Virtualization Software" in the "Design Guide CE".
Can be placed on the same server as the manager (recommended) or on another server.
When operating managers in clusters, place it on a different server.

BMC BladeLogic Server Automation Console

8.3

Necessary when using coordination of registration and deletion of managed servers, cloning, and software deployment in PRIMERGY and PRIMEQUEST.

[Solaris Zones] [OVM for SPARC]
Necessary when using the functions with "Yes (*)" described in "Table: Functional Differences Depending on Server Virtualization Software" in "11.1 Deciding Server Virtualization Software" in the "Design Guide CE".
Install it on the same server as the manager.

SAN Client CLI

7.00

Necessary when connecting a Virtual Device of FalconStor NSS to a physical L-Server.
Download this software from the FalconStor customer support portal.

*1: Obtain it from the following Microsoft FTP site.

Microsoft FTP site

URL: ftp://ftp.microsoft.com/bussys/clients/msclient/dsk3-1.exe

*2: Check the following VMware manuals:

URL: https://www.vmware.com/jp/support/support-resources/pubs/

*3: Check the following Oracle manuals:

URL: http://www.oracle.com/technetwork/documentation/vm-096300.html

*4: For Linux manager, registering ServerView Fabric Manager as Converged Fabric management software is not possible.
To register ServerView Fabric Manager as Converged Fabric management software, use Windows manager.


Required Software (Agent)

Table 6.86 Agent [Windows]

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
"sysprep.exe" module

-

Necessary when using backup and restore, or cloning.
Please refer to the Microsoft web site and obtain the latest module. (*)
When using Windows Server 2008 or later, the modules are already configured in the OS so there is no need to obtain new modules.

Intel PROSet
or
PRIMECLUSTER GLS for Windows
or
OneCommand NIC Teaming and
Multiple VLAN Manager

-

Necessary when performing redundancy of the admin LAN and public LAN for managed servers.

When using PRIMECLUSTER GLS, also apply the latest patches for GLS.

ETERNUS Multipath Driver

V2.0L10 or later

Necessary for multipath connections between servers and storage units (ETERNUS).
Versions differ depending on the OS and storage types. Refer to ETERNUS Multipath Driver support information.

Data ONTAP DSM

3.2R1 or later

Necessary for connection between servers and storage units (NetApp).
Versions differ depending on the OS and storage types. Refer to Data ONTAP DSM support information.

PowerPath

5.3 or later

Necessary for multipath connections between servers and storage units (EMC CLARiiON, EMC VNX, EMC Symmetrix DMX, or EMC Symmetrix VMAX).
Versions differ depending on the OS and storage types. Refer to PowerPath support information.

DynaPath

v6.00 b1018 or later
(For Windows Server 2008 R2)

v5.01 b936 or later
(For Windows Server 2003 R2)

Necessary for multipath connections between physical L-Servers and storage servers on which FalconStor NSS operates.
Versions differ depending on the OS and storage types.
Refer to DynaPath support information.

*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):
http://www.microsoft.com/downloads/details.aspx?familyid=93F20BB1-97AA-4356-8B43-9584B7E72556&displaylang=en

URL(x64):
http://www.microsoft.com/downloads/details.aspx?familyid=C2684C95-6864-4091-BC9A-52AEC5491AF7&displaylang=en

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.1.1.2 Software Preparation and Checks" in the "Setup Guide CE".
The module is not necessary after installation of agents.

Table 6.87 Agent [Linux]

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).
Versions differ depending on the OS and storage types. Refer to ETERNUS Multipath Driver support information.

PowerPath

5.3

Necessary for multipath connections between servers and storage units (EMC CLARiiON, EMC VNX, EMC Symmetrix DMX, or EMC Symmetrix VMAX).
Versions differ depending on the OS and storage types. Refer to PowerPath support information.

DM-Multipath

OS standard

Necessary for multipath connections between physical L-Servers and storage servers on which FalconStor NSS operates.

Table 6.88 Agent [Red Hat Enterprise Linux]

Required Software

Version

Remarks

PRIMECLUSTER GLS

4.2A00 or later

Necessary when performing redundancy of the admin LAN and public LAN for managed servers.

Table 6.89 Agent [Solaris] [Solaris Zones] [OVM for SPARC]

Required Software

Version

Remarks

PRIMECLUSTER GLS

4.2 or later

Necessary when performing redundancy of the admin LAN and public LAN for managed servers.

BMC BladeLogic RSCD Agent

8.3

[Solaris Zones] [OVM for SPARC]
Necessary when using the functions with "Yes (*)" described in "Table: Functional Differences Depending on Server Virtualization Software" in "11.1 Deciding Server Virtualization Software" in the "Design Guide CE".

Oracle VM Server for SPARC Software

3.0 or later

Required when using the control domain of OVM for SPARC for an agent.

Table 6.90 Agent [VMware]

Required Software

Version

Remarks

ServerView Agents for VMware

V4.30-20 or later

Required for collecting and managing server information of PRIMERGY and PRIMEQUEST.
Not necessary when using VMware ESXi for the agent.

ServerView ESXi CIM Provider

1.10.01 or later

Necessary when using VMware ESXi as a managed server.
The compatible version varies depending on the version of ESXi you use.
For details, refer to the operating environment conditions for ServerView ESXi CIM Provider.

Table 6.91 Agent [Hyper-V]

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
"sysprep.exe" module

-

Necessary when using backup and restore, or cloning.
Please refer to the Microsoft web site and obtain the latest module. (*)
When using Windows Server 2008 or later, the modules are already configured in the OS so there is no need to obtain new modules.

Intel PROSet

15.6.25.0 or later

Necessary to automatically perform the following configurations using Intel PROSet on blade servers:

  • Virtual network creation and NIC connection

  • Configuration of the server blade connection ports of LAN switch blades

  • Connection of the server blade ports and uplink ports

This is not necessary when the following applies:

  • When not performing network redundancy for L-Servers using blade servers

  • When using servers other than blade servers

PRIMECLUSTER GLS for Windows

-

After configuring redundancy for blade servers using PRIMECLUSTER GLS, it is necessary to perform the following configurations automatically:

  • Virtual network creation and NIC connection

  • Configuration of the server blade connection ports of LAN switch blades

  • Connection of the server blade ports and uplink ports

This is not necessary when the following applies:

  • When not performing network redundancy for L-Servers using blade servers

  • When using servers other than blade servers

For details, refer to "2.2.7 Simplifying Networks" in the "Design Guide CE".

*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):
http://www.microsoft.com/downloads/details.aspx?familyid=93F20BB1-97AA-4356-8B43-9584B7E72556&displaylang=en

URL(x64):
http://www.microsoft.com/downloads/details.aspx?familyid=C2684C95-6864-4091-BC9A-52AEC5491AF7&displaylang=en

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.1.1.2 Software Preparation and Checks" in the "Setup Guide CE".
The module is not necessary after installation of agents.

Table 6.92 Agent [Xen]

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.

Table 6.93 Agent [KVM]

Required Software

Version

Remarks

ServerView Agents for Linux

V5.1 or later

Required for collecting and managing server information of PRIMERGY and PRIMEQUEST.

Table 6.94 Agent [Citrix Xen]

Required Software

Version

Remarks

ServerView Agents for Citrix XenServer

4.92.66 or later

Required for managing server information of PRIMERGY and PRIMEQUEST.

Table 6.95 Agent [OVM for x86 2.2] [OVM for x86 3.x]

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 (HBA address rename Setup Service)

Table 6.96 HBA address rename setup service [Windows]

Required Software

Version

Remarks

Internet Explorer

8
9
10
11

Necessary for displaying the online help.

Table 6.97 HBA address rename Setup Service [Linux]

Required Software

Version

Remarks

Firefox

3

Necessary for displaying the online help.


Required Software: Admin Clients

The following software is necessary for admin clients.

Table 6.98 List of Required Software for Admin Clients

Required Software

Version

Remarks

Internet Explorer

8 (*1)
9 (*2)
10 (*2, *3)
11 (*2, *3, *4)

Internet Explorer or Firefox is required to display the ROR console.

Microsoft(R) Edge cannot be used in Windows 10.

Firefox

ESR17 (*5)
ESR24
ESR31
ESR38

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

(*6)

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
4.1
5.0
5.1
5.5
6.0

[VMware]
Necessary on admin clients when using the functions for coordinating with VMware or the VM management software on managed servers.

Hyper-V Manager

-

[Hyper-V]
Necessary on admin clients when using the functions for coordinating with Hyper-V on managed servers.
Operation on Windows Server 2003 is not supported.

Microsoft(R) System Center Virtual Machine Manager 2008 R2 VMM Admin Console
or
Microsoft(R) System Center 2012 Virtual Machine Manager console (*1)
or
Microsoft(R) System Center 2012 R2 Virtual Machine Manager console (*1)

-

[Hyper-V]
Necessary on admin clients when using the functions for coordinating with VM management software and connecting with the L-Server console. Prepare the same version as VM management software for registration in Resource Orchestrator.

ETERNUS SF Storage Cruiser clients

14.2 or later

Necessary when checking the detailed information of storage using the admin client.
Operation on Windows Server 2003 x64 Edition is not supported.

VMware Remote Console Plug-in

5.1 (*7)

[VMware]
Necessary on admin clients when using the VMware vSphere functions for connecting with the virtual L-Server console. Obtain it from the VMware web site. (*8)

*1: Cannot be used by the NetworkViewer. Use another browser.
*2: When connecting with the ROR Console, use Compatibility View Settings.
*3: Only Internet Explorer (Desktop version) is supported.
*4: Set the resolution of the browser window as 100%.
*5: 17.0.8 or later is required.
*6: 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.
*7: Only 32-bit versions of web browsers are supported. When using the VMware vSphere functions for connecting with the L-Server console in the following environments, use a 32-bit version web browser.

*8: VMware Remote Console Plug-in is provided with the VMware Remote Console SDK. Obtain the VMware Remote Console SDK 5.1 at the following VMware web site:

VMware web site

URL: http://www.vmware.com/support/developer/vmrc/index.html


6.1.2.5 Exclusive Software

Resource Orchestrator cannot be used in combination with the following products. When performing a new installation of Resource Orchestrator, do not use it on the same server as the following products. For exclusive software when upgrading from earlier versions, refer to "Table 6.100 [Admin Server] (Upgrade Installation)".

List of Exclusive Software

Table 6.99 [Admin Server] (New Installation)

Operating System Type

Product Name

Version and Level

Remarks

Windows

Systemwalker Resource Coordinator

All versions

Here "Systemwalker Resource Coordinator" includes the following products:

  • Systemwalker Resource Coordinator

  • Systemwalker Resource Coordinator Base
    Edition

  • Systemwalker Resource Coordinator Virtual
    server Edition

Systemwalker Runbook Automation (Admin Server)

V15.1.1 or earlier
V15.1.2 or later (*1)

-

Systemwalker Runbook Automation (Linked Server/Relay Server/Business Server)

All versions

-

Systemwalker Service Catalog Manager

V14g

-

Systemwalker Software Configuration Manager

V14.0.0

-

Systemwalker Software Configuration Manager (Admin Server)

V14.1.0 or later
V15.4.0 or earlier

-

Systemwalker Software Configuration Manager (Linked Server/Public Server)

V15.4.0 or earlier

-

Cloud Infrastructure Management Software

All versions

-

SystemcastWizard

All versions

-

SystemcastWizard Professional

All versions

-

SystemcastWizard Lite

All versions

-

ServerView Installation Manager (*2)

All versions

-

ServerView Resource Coordinator VE

All versions

-

FUJITSU Software ServerView Resource Orchestrator

All versions

-

ServerView Deployment Manager (*3)

All versions

-

Premeo Premium Agent

All versions

-

TeamWARE Office Server

All versions

-

TRADE MASTER

All versions

-

Linux

Server System Manager

All versions

-

Systemwalker Resource Coordinator

All versions

Here "Systemwalker Resource Coordinator" includes the following products:

  • Systemwalker Resource Coordinator

  • Systemwalker Resource Coordinator Base Edition

Systemwalker Resource Coordinator Virtual server Edition

Systemwalker Runbook Automation (Admin Server)

V15.1.1 or earlier
V15.1.2 or later (*1)

-

Systemwalker Runbook Automation (Linked Server/Relay Server/Business Server)

All versions

-

Systemwalker Service Catalog Manager

V14g

-

Systemwalker Software Configuration Manager (Admin Server)

V15.4.0 or earlier

-

Systemwalker Software Configuration Manager (Linked Server/Public Server)

V15.4.0 or earlier

-

Cloud Infrastructure Management Software

All versions

-

ServerView Resource Coordinator VE

All versions

-

FUJITSU Software ServerView Resource Orchestrator

All versions

-

Premeo Premium Agent

All versions

-

Server System Manager

All versions

-

*1: This can be installed with this version. Contact Fujitsu technical staff for information on how to install it along with Resource Orchestrator.
*2: 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.
*3: ServerView Deployment Manager can be installed after this product has been installed.

Note

  • It is not possible to upgrade the manager environment of this product configured using Systemwalker Runbook Automation.

  • It is not possible to upgrade the manager environment of this product configured using Systemwalker Software Configuration Manager (Admin Server).

Table 6.100 [Admin Server] (Upgrade Installation)

Operating System Type

Product Name

Version and Level

Remarks

Windows

INTERSTAGE

All versions

Here "INTERSTAGE" includes the following products:

  • INTERSTAGE

  • INTERSTAGE Standard Edition

  • INTERSTAGE Enterprise Edition

Interstage Apcoordinator

All versions

-

Interstage Application Server

All versions

Here "Interstage Application Server" includes the following products:

  • INTERSTAGE Application Server Standard Edition

  • INTERSTAGE Application Server Enterprise Edition

  • INTERSTAGE Application Server Web-J Edition

  • Interstage Application Server Standard Edition

  • Interstage Application Server Standard-J Edition

  • Interstage Application Server Enterprise Edition

  • Interstage Application Server Plus

  • Interstage Application Server Plus Developer

  • Interstage Application Server Web-J Edition

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 Application Server
    Standard Edition

  • Interstage Business Application Server
    Enterprise Edition

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

-

ObjectDirector

All versions

-

Systemwalker Centric Manager
(Operation Management Server/Section Management Server/Job Server)

All versions
(*1)

Here "Systemwalker Centric Manager" includes the following products:

  • SystemWalker/CentricMGR

  • SystemWalker/CentricMGR-M

  • SystemWalker/CentricMGR GEE

  • SystemWalker/CentricMGR EE

  • SystemWalker/CentricMGR SE

  • Systemwalker Centric Manager Global Enterprise Edition

  • Systemwalker Centric Manager Enterprise Edition

  • Systemwalker Centric Manager Standard Edition

Systemwalker IT Change Manager

All versions

Here "Systemwalker IT Change Manager" includes the following products:

  • Systemwalker IT Change Manager Enterprise Edition

  • Systemwalker IT Change Manager Standard Edition

Systemwalker IT Process Master

All versions

-

Systemwalker PKI Manager

All versions

-

Securecrypto Library

All versions

-

Systemwalker Resource Coordinator

All versions

Here "Systemwalker Resource Coordinator" includes the following products:

  • Systemwalker Resource Coordinator

  • Systemwalker Resource Coordinator Base
    Edition

  • Systemwalker Resource Coordinator Virtual
    server Edition

Systemwalker Runbook Automation (Admin Server)

V15.1.1 or earlier
V15.1.2 or later (*2)

-

Systemwalker Runbook Automation (Linked Server/Relay Server/Business Server)

All versions

-

Systemwalker Service Quality Coordinator

All versions (*3)

-

Systemwalker Service Catalog Manager

V14g

-

Systemwalker Software Configuration Manager

V14.0.0

-

Systemwalker Software Configuration Manager (Admin Server)

V14.1.0 or later
V15.4.0 or earlier

-

Systemwalker Software Configuration Manager (Linked Server/Public Server)

V15.4.0 or earlier

-

Cloud Infrastructure Management Software

All versions

-

SystemcastWizard

All versions

-

SystemcastWizard Professional

All versions

-

SystemcastWizard Lite

All versions

-

ServerView Installation Manager (*4)

All versions

-

ServerView Resource Coordinator VE

All versions

-

FUJITSU Software ServerView Resource Orchestrator

All versions

-

ServerView Deployment Manager (*5)

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 Server Standard Edition

  • INTERSTAGE Application Server Enterprise Edition

  • INTERSTAGE Application Server Web-J Edition

  • Interstage Application Server Standard Edition

  • Interstage Application Server Standard-J Edition

  • Interstage Application Server Enterprise Edition

  • Interstage Application Server Plus

  • Interstage Application Server Plus Developer

  • Interstage Application Server Web-J Edition

Interstage Application Framework Suite

All versions

-

Interstage Business Application Server

All versions

Here "Interstage Business Application Server" includes the following products:

  • Interstage Business Application Server Standard Edition

  • Interstage Business Application Server Enterprise Edition

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 Service Integrator Enterprise Edition

  • Interstage Service Integrator Standard Edition

Interstage Shunsaku Data Manager

All versions

-

Interstage Traffic Director

All versions

-

Server System Manager

All versions

-

Systemwalker Centric Manager
(Operation Management Server/Section Management Server/Job Server)

All versions
(*1)

Here "Systemwalker Centric Manager" includes the following products:

  • SystemWalker/CentricMGR

  • SystemWalker/CentricMGR-M

  • SystemWalker/CentricMGR GEE

  • SystemWalker/CentricMGR EE

  • SystemWalker/CentricMGR SE

  • Systemwalker Centric Manager Global Enterprise Edition

  • Systemwalker Centric Manager Enterprise Edition

  • Systemwalker Centric Manager Standard Edition

Systemwalker IT Process Master

All versions

-

Systemwalker IT Change Manager

All versions

Here "Systemwalker IT Change Manager" includes the following products:

  • Systemwalker IT Change Manager Enterprise Edition

  • Systemwalker IT Change Manager Standard Edition

Systemwalker Resource Coordinator

All versions

Here "Systemwalker Resource Coordinator" includes the following products:

  • Systemwalker Resource Coordinator

  • Systemwalker Resource Coordinator Base Edition

  • Systemwalker Resource Coordinator Virtual server Edition

Systemwalker Runbook Automation (Admin Server)

V15.1.1 or earlier
V15.1.2 or later (*2)

-

Systemwalker Runbook Automation (Linked Server/Relay Server/Business Server)

All versions

-

Systemwalker Service Quality Coordinator

All versions (*3)

-

Systemwalker Service Catalog Manager

V14g

-

Systemwalker Software Configuration Manager (Admin Server)

V15.4.0 or earlier

-

Systemwalker Software Configuration Manager (Linked Server/Public Server)

V15.4.0 or earlier

-

Cloud Infrastructure Management Software

All versions

-

ServerView Resource Coordinator VE

All versions

-

FUJITSU Software ServerView Resource Orchestrator

All versions

-

Premeo Premium Agent

All versions

-

*1: This can be installed with Systemwalker Centric Manager Enterprise Edition V10.0L21 or later (x86 version) or Systemwalker Centric Manager Standard Edition V10.0L21 or later (x86 version). Contact Fujitsu technical staff for information on how to install it along with these products.
*2: This can be installed with this version. Contact Fujitsu technical staff for information on how to install it along with Resource Orchestrator.
*3: This can only be installed with Systemwalker Service Quality Coordinator V15.0.1 (x86 version). When installing Resource Orchestrator along with Systemwalker Service Quality Coordinator, refer to "Appendix C Upgrading from Earlier Versions" in the "Setup Guide CE".
*4: 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.
*5: ServerView Deployment Manager can be installed after this product has been installed.

Table 6.101 [Managed Server Resource Agent]

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

-

OVM for x86 2.2

ServerView Deployment Manager (*1)

All versions

-

Solaris Zones

OVM for SPARC

Server System Manager (Manager only)

All versions

-

Systemwalker Service Quality Coordinator

V15.0.0 or earlier
V15.0.1 (*2)

-

ETERNUS SF Disk Space Monitor

All versions

-

Citrix Xen

ServerView Deployment Manager (*1)

All versions

-

OVM for x86 3.x

ServerView Deployment Manager (*1)

All versions

-

*1: ServerView Deployment Manager can be installed after Resource Orchestrator has been installed.

Operating System Type

Product Name

Version and Level

Remarks

Windows

Systemwalker Service Quality Coordinator

V15.0.0 or earlier
V15.0.1 (*2)

-

Systemwalker Service Catalog Manager

V14g

-

ETERNUS SF Disk Space Monitor

All versions

-

Linux

Systemwalker Service Quality Coordinator

V15.0.0 or earlier
V15.0.1 (*2)

-

Systemwalker Service Catalog Manager

V14g

-

ETERNUS SF Disk Space Monitor

All versions

-

Solaris

Server System Manager (Manager only)

All versions

-

Systemwalker Service Quality Coordinator

V15.0.0 or earlier
V15.0.1 (*2)

-

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:

Table 6.102 List of Exclusive Software

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] [Citrix Xen] [KVM]

-

Agent [OVM for x86 2.2]

ServerView Deployment Manager (*2)

Agent [Solaris] [Solaris Zones] [OVM for SPARC]

Server System Manager (Manager only)

*1: As managers of Resource Orchestrator 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 Orchestrator has been installed. For details on installation, refer to "2.2 Agent Installation" in the "Setup Guide CE".

Note

  • 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.
    However, such products or services can be placed in the same network as Resource Orchestrator managers. In this case, configure the managed server for Resource Orchestrator to be excluded from being managed by any other DHCP server.

    Examples of Products Including DHCP Servers and PXE Servers

    • The Windows Server 2003 "Remote Installation Service", and the Windows Server 2012/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 FUJITSU Software ServerView Resource Orchestrator. For details on co-existence with ServerView Deployment Manager, refer to "I.2 Co-Existence with ServerView Deployment Manager" in the "Setup Guide CE".

  • Resource Orchestrator managers cannot be installed on domain controllers of Active Directory.

[Physical Servers]

  • Contact Fujitsu technical staff for information about ServerView Deployment Manager.


6.1.2.6 Static Disk Space

The size of the required static disk space does not increase even after Resource Orchestrator is operated.

When using Resource Orchestrator, the disk space described in "6.1.2.7 Dynamic Disk Space" is required for each folder, in addition to the static disk space.
The amount of disk space may vary slightly depending on the environment in question.

Table 6.103 Static Disk Space

Software

Folder

Disk Space (Unit: MB)

[Windows Manager]

Installation_folder (*)

7600

[Linux Manager]

/opt

3200

/etc/opt

50

/var/opt

3600

Agent [Windows] [Hyper-V]

Installation_folder (*)

490

Agent [Linux]

/opt

400

/etc/opt

20

/var/opt

5

Agent [VMware] [Xen] [KVM] [OVM for x86 2.2] [Citrix Xen] [OVM for x86 3.x]

/opt

110

/etc/opt

5

/var/opt

5

Agent [Solaris] [Solaris Zones] [OVM for SPARC]

/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:
Default value: C:\Program Files (x86)\Resource Orchestrator


6.1.2.7 Dynamic Disk Space

The size of the required dynamic disk space changes dynamically when Resource Orchestrator is operated.

When using Resource Orchestrator, the following disk space is required for each folder, in addition to static disk space.

Table 6.104 Dynamic Disk Space

Software

Folder

Disk Space (Unit: MB)

[Windows Manager]

Installation_folder (*1)

9080 + Number_of_managed_servers * 4

Environmental_data_storage_area (*2)

Performance_display_information_storage_area(*3)

Metering log_storage_area(*4)

Image_file_storage_folder (*5)

Image_file_storage_area (*6)

Backup_storage_folder_for_configuration_definition_information

Backup_storage_area_for_configuration_definition_information (*4)

Network_device_configuration_file_storage_folder (*7)

Network_device_configuration_file_storage_area (*8)

[Linux Manager]

/etc

2

/var/opt

9080 + Number_of_managed_servers * 4

Environmental_data_storage_area (*2)

Performance_display_information_storage_area(*3)

Metering log_storage_area(*4)

Image_file_storage_directory (*5)

Image_file_storage_area (*6)

Backup_storage_folder_for_configuration_definition_information

Backup_storage_area_for_configuration_definition_information (*4)

Network_device_configuration_file_storage_folder (*7)

Network_device_configuration_file_storage_area (*8)

Agent [Windows]

Installation_folder (*9)

60

Log_data(*10)

Agent [Hyper-V]

Installation_folder (*9)

60

Log_data(*11)

Agent [Linux]

/etc

1

/var/opt

1

Log_data(*12)

Agent [VMware] [Xen] [KVM] [OVM for x86 2.2] [Citrix Xen] [OVM for x86 3.x]

/etc

1

/var/opt

1

Agent [Solaris] [Solaris Zones] [OVM for SPARC]

/etc

1

/var/opt

1

Log_data(*12)

HBA address rename setup service [Windows]

Installation_folder (*9)

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:
Default value: C:\Program Files (x86)\Resource Orchestrator

*2: Necessary when using power monitoring. For details, refer to "Environmental Data Storage Area".

*3: For information disk capacity for performance display, there are storage areas for pool condition information and system condition information. The disk capacity necessary for resources is indicated below.

*4: The necessary disk capacity for metering logs is indicated as follows:

Table 6.105 Formula of Disk Space Necessary for Metering Logs

Metering Logs per day * capacity for one year
3.5 MB * 365 = 1.3 GB

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.

Table 6.106 Required Conditions for Metering Information Backup

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

  • The following operations are executed every day

    • Return and deployment of 10 L-Platforms

    • Starting of 1,000 L-Servers when starting operations

    • Stopping of 1,000 L-Servers when finishing operations

  • Obtain regular logs every day

  • Keep metering logs for one year

Online backup frequency

  • Execute monthly base backup (every 30 days)

  • Execute hourly difference backup.

Table 6.107 Formula for Metering Logs per Day
  • Target capacity for metering logs

    • Event Logs for an L-Platform : 2.3 KB/each time (A)

    • Event Logs for other than an L-Platform : 0.6 KB/each time (B)

    • Regular logs : 2.3 * number of L-Platforms (KB) (C)

  • Metering logs per day

    (A) * operation number for L-Platforms per day
    + (B) * operation number for other than L-Platforms per day
    + (C) * number of operating L-Platforms

    = 2.3 KB * 20 + 0.6 KB * 2000 + 2.3 KB * 1000
    = 3.5MB

*5: The name of the storage folder (directory) specified for image files when this software is installed.

[Windows Manager]
The default folder name when Windows is installed on C:\ is as follows:
Default value: C:\Program Files (x86)\Resource Orchestrator\SVROR\ScwPro\depot

[Linux Manager]
The default is as follows:
/var/opt/FJSVscw-deploysv/depot

*6: The image storage area when using cloning images for cloning of physical servers.
For details on the amount of space necessary 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.
*7: 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:
C:\Program Files (x86)\Resource Orchestrator\SVROR\Manager\var\netdevice

[Linux]
The default is as follows:
/var/opt/FJSVrcvmr/netdevice

*8: 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.

*9: The installation folder name specified when this software is installed.
The default folder name when Windows is installed on C:\ is as follows:

*10: The approximate estimate value is 60 MB.
*11: The approximate estimate value is 60 MB * VM guest number.
*12: 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".


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 of the settings, refer to "13.1.1 Settings for the Power Monitoring Environment" in the "Design Guide CE".
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.

  1. 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

    Disk_space_per_managed_server

    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".

    Compression_ratio

    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%

  2. 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

    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 versions 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)

  3. 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

    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 versions 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)

  4. 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)

  5. 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).


6.1.2.8 Memory Size

The memory size listed below is the minimum amount required when using Resource Orchestrator.

Consider the amount of memory necessary for required software as well as the amount of memory necessary for Resource Orchestrator.

Table 6.108 Memory Size

Software

Memory Size (Unit: MB)

[Windows Manager]

12000

[Linux Manager]

16000

Agent [Windows] [Hyper-V]

500

Agent [Linux]

700

Agent [Solaris] [Solaris Zones] [OVM for SPARC]

400

Agent [VMware]

700

Agent [Xen] [KVM]

700

Agent [Citrix Xen]

700

Agent [OVM for x86 2.2] [OVM for x86 3.x]

700

HBA address rename setup service [Windows]

300

HBA address rename Setup Service [Linux]

600