2.1.1 Preparations

Software preparation and checks are explained in the following sections.

This section explains the preparations and checks required before commencing the installation of Resource Orchestrator.

Host Name Checks

It is necessary to set the host name (FQDN) for the admin server to operate normally. Describe the host name in the hosts file, using 256 characters or less. In the hosts file, for the IP address of the admin server, configure the host name (FQDN) and then the computer name.

hosts File

[Windows]

System_drive\WindowsSystem32\drivers\etc\hosts

[Linux]

/etc/hosts

Note

For the admin client, either configure the hosts file so access to the admin server is possible using the host name (FQDN), or name resolution using a DNS server.

When registering local hosts in the hosts file, take either one of the following actions.

When setting the local host name to "127.0.0.1", ensure that an IP address accessible from remote hosts is described first.
Do not set the local host name to "127.0.0.1".

Example

When configuring the admin server with the IP address "10.10.10.10", the host name (FQDN) "remote1.example.com", and the computer name "remote1"

10.10.10.10 remote1.example.com remote1
127.0.0.1 remote1.example.com localhost. localdomain localhost

SMTP Server Checks

Resource Orchestrator uses e-mail. Configure the SMTP server settings to create an environment where e-mail is available.

System Time Checks

Set the same system time for the admin server and managed servers.

If the system time differs, correct values will not be displayed in the [Usage Condition] tab on the ROR console.

Exclusive Software Checks

Before installing Resource Orchestrator, check that the software listed in "1.4.2.3 Exclusive Software" of the "Setup Guide CE" and the manager of Resource Orchestrator have not been installed on the system.
Use the following procedure to check that exclusive software has not been installed.

[Windows]

Open "Add or Remove Programs" on the Windows Control Panel.
The [Add or Remove Programs] window will be displayed.
Check that none of the software listed in "1.4.2.3 Exclusive Software" of the "Setup Guide CE" or the following software are displayed.
- "ServerView Resource Orchestrator Manager"
If the names of exclusive software have been displayed, uninstall them according to the procedure described in the relevant manual before proceeding.
If managers of an earlier version of Resource Orchestrator have been installed, they can be upgraded. Refer to "4.2 Manager".
When reinstalling a manager on a system on which the same version of Resource Orchestrator has been installed, perform uninstallation referring to "3.1 Manager Uninstallation" and then perform the reinstallation.
Information
For Windows Server 2008, select "Programs and Features" from the Windows Control Panel.

[Linux]

Check that none of the software listed in "1.4.2.3 Exclusive Software" in the "Setup Guide CE" or the following software are displayed.
Execute the following command and check if Resource Orchestrator Manager has been installed.
# rpm -q FJSVrcvmr <RETURN>
If the names of exclusive software have been displayed, uninstall them according to the procedure described in the relevant manual before proceeding.
If managers of an earlier version of Resource Orchestrator have been installed, they can be upgraded. Refer to "4.2 Manager".
When reinstalling a manager on a system on which the same version of Resource Orchestrator has been installed, perform uninstallation referring to "3.1 Manager Uninstallation" and then perform the reinstallation.

Note

When uninstalling exclusive software, there are cases where other system administrators might have installed the software, so check that deleting the software causes no problems before actually doing so.
With the standard settings of Red Hat Enterprise Linux 5 or later, when DVD-ROMs are mounted automatically, execution of programs on the DVD-ROM cannot be performed. Release the automatic mount settings and perform mounting manually, or start installation after copying the contents of the DVD-ROM to the hard disk.
When copying the contents of the DVD-ROM, replace "DVD-ROM_mount_point" with the used directory in the procedures in this manual.

Required Software Preparation and Checks

Before installing Resource Orchestrator, check that the required software given in "1.4.2.2 Required Software" of the "Setup Guide CE" has been installed. If it has not been installed, install it before continuing.

When operating managers in cluster environments, refer to "Appendix B Manager Cluster Operation Settings and Deletion" and "B.2.1 Preparations", and perform preparations and checks in advance.

Note

[Windows]

Microsoft LAN Manager Module
Before installing Resource Orchestrator, obtain the Microsoft LAN Manager module from the following FTP site.
The Microsoft LAN Manager module can be used regardless of the CPU architecture type (x86, x64).
URL: ftp://ftp.microsoft.com/bussys/clients/msclient/dsk3-1.exe (As of February 2012)
When installing Resource Orchestrator to an environment that already has ServerView Deployment Manager installed, it is not necessary to obtain the Microsoft LAN Manager module.
Prepare for the following depending on the architecture of the installation target.
- When installing a manager on Windows 32bit(x86)
  The Microsoft LAN Manager module can be installed without extracting it in advance.
  After obtaining the module, extract it to a work folder (such as C:\temp) on the system for installation.
- When installing a manager on Windows 64bit(x64)
  The obtained module must be extracted using the Expand command on a computer with x86 CPU architecture.
  The obtained module is for x86 CPU architecture, and cannot be extracted on computers with x64 CPU architecture.
  For details on how to extract the module, refer to the following examples:
  Example
  When dsk3-1.exe was deployed on c:\temp
  >cd /d c:\temp <RETURN>
  >dsk3-1.exe <RETURN>
  >Expand c:\temp\protman.do_ /r <RETURN>
  >Expand c:\temp\protman.ex_ /r <RETURN>
  Use the Windows 8.3 format (*1) for the folder name or the file name.
  After manager installation is complete, the extracted Microsoft LAN Manager module is no longer necessary.
  *1: File names are limited to 8 characters and extensions limited to 3 characters.
  After extracting the following modules, deploy them to the folder that has been set for environment_variable%SystemBoot%.
  - PROTMAN.DOS
  - PROTMAN.EXE
  - NETBIND.COM
Settings for ServerView Operations Manager 4.X for Windows
In order for Resource Orchestrator to operate correctly, ensure that when installing ServerView Operations Manager for Windows you do not select "IIS (MS Internet Information Server)" for Select Web Server.
For the settings, refer to the ServerView Operations Manager 4.X for Windows manual.
SNMP Trap Service Settings
In order for Resource Orchestrator to operate correctly, the following settings for the standard Windows SNMP trap service are required.
- Open "Services" from "Administrative Tools" on the Windows Control Panel, and then configure the startup type of SNMP Trap service as "Manual" or "Automatic" on the [Services] window.
Settings for ServerView Virtual-IO Manager
When using VIOM, in order for Resource Orchestrator to operate correctly, ensure that the following settings are made when installing ServerView Virtual-IO Manager for Windows.
- When using the I/O Virtualization Option
  Clear the "Select address ranges for IO Virtualization" checkbox on the virtual I/O address range selection window.
- When not using the I/O Virtualization Option
  Check the "Select address ranges for IO Virtualization" checkbox on the virtual I/O address range selection window, and then select address ranges for the MAC address and the WWN address.
  When there is another manager, select address ranges which do not conflict those of the other manager.
For details, refer to the ServerView Virtual-IO Manager for Windows manual.
DHCP server installation
Installation of the Windows standard DHCP Server is necessary when managed servers belonging to different subnets from the admin server are to be managed.
Depending on the functions used, it may necessary to configure the router settings. For details, refer to "4.2.2.4 Settings for Unmanaged Network Devices" in the "Setup Guide CE".
When registering managed servers that belong to a different subnet from the admin server, they must be registered on the admin LAN subnet in advance.
For details, refer to "2.10 Registering Admin LAN Subnets" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Install the DHCP Server following the procedure below:
1. Add DHCP Server to the server roles.
  Perform binding of the network connections for the NIC to use as the admin LAN.
  For the details on adding and binding, refer to the manual for Windows.
2. Open "Services" from "Administrative Tools" on the Windows Control Panel, and then configure the startup type of DHCP Server service as "Manual" on the [Services] window.
3. From the [Services] window, stop the DHCP Server service.
  When an admin server is a member of a domain, perform 4.
4. Authorize DHCP servers.
  1. Open "DHCP" from "Administrative Tools" on the Windows Control Panel, and select [Action]-[Managed authorized servers] on the [DHCP] window.
    The [Manage Authorized Servers] window will be displayed.
  2. Click <Authorize>.
    The [Authorize DHCP Server] window will be displayed.
  3. Enter the admin IP address of the admin server in "Name or IP address".
  4. Click <OK>.
    The [Confirm Authorization] window will be displayed.
  5. Check the "Name" and "IP Address".
  6. Click <OK>.
    The server will be displayed in the "Authorized DHCP servers" of the [Manage Authorized Servers] window.
ETERNUS SF Storage Cruiser
When using ESC, configure the Fibre Channel switch settings in advance.

[Linux]

Microsoft LAN Manager Module
Before installing Resource Orchestrator, obtain the Microsoft LAN Manager module from the following FTP site.
The Microsoft LAN Manager module can be used regardless of the CPU architecture type (x86, x64).
URL: ftp://ftp.microsoft.com/bussys/clients/msclient/dsk3-1.exe (As of February 2012)
When installing Resource Orchestrator to an environment that already has ServerView Deployment Manager installed, it is not necessary to obtain the Microsoft LAN Manager module.
The obtained module must be extracted using the Expand command on a computer with x86 CPU Windows architecture. For details on how to extract the module, refer to the following examples:
Example
When dsk3-1.exe was deployed on c:\temp
>cd /d c:\temp <RETURN>
>dsk3-1.exe <RETURN>
>Expand c:\temp\protman.do_ /r <RETURN>
>Expand c:\temp\protman.ex_ /r <RETURN>
Use the Windows 8.3 format (*1) for the folder name or the file name.
After manager installation is complete, the extracted Microsoft LAN Manager module is no longer necessary.
*1: File names are limited to 8 characters and extensions limited to 3 characters.
After extracting the following modules, deploy them to a work folder (/tmp) on the system for installation.
- PROTMAN.DOS
- PROTMAN.EXE
- NETBIND.COM
SNMP Trap Daemon
In order for Resource Orchestrator to operate correctly to operate correctly, ensure that the following settings are made for the "/etc/snmp/snmptrapd.conf" file, when installing the net-snmp package. When there is no file, add the following setting after creating the file.
disableAuthorization yes
DHCP server installation
Installation of the Linux standard DHCP server is necessary when managed servers belonging to different subnets from the admin server are to be managed.
Depending on the functions used, it may necessary to configure the router settings. For details, refer to "4.2.2.4 Settings for Unmanaged Network Devices" in the "Setup Guide CE".
When registering managed servers that belong to a different subnet from the admin server, they must be registered on the admin LAN subnet in advance.
For details, refer to "2.10 Registering Admin LAN Subnets" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Install the DHCP server following the procedure below:
1. Install the dhcp package.
2. Execute the following command to modify the setting for automatic startup of the DHCP server service (dhcpd):
  # chkconfig dhcpd off <RETURN>
3. Execute the following command to stop the DHCP server service (dhcpd):
  # /etc/init.d/dhcpd stop <RETURN>
ETERNUS SF Storage Cruiser
When using ESC, configure the Fibre Channel switch settings in advance.

User Account Checks

The OS user account name used for the database connection for Resource Orchestrator is fixed as "rcxdb". When applications using the OS user account "rcxdb" exist, delete them after confirming there is no effect on them.

Single Sign-On Preparation and Checks

Before installing Resource Orchestrator, certificate preparation and user registration with the registration service are required.
For details, refer to "4.5 Installing and Configuring Single Sign-On" of the "Setup Guide CE".

For setting up Resource Orchestrator, it is necessary to establish communication beforehand, since communication between the manager and the directory service requires LDAP (Lightweight Directory Access Protocol) of the TCP/IP protocol protected by SSL.
Use tools or commands to check communications.

When the directory server is Microsoft Active Directory
For details, refer to the Microsoft web site below.
How to enable LDAP over SSL with a third-party certification authority
URL: http://support.microsoft.com/kb/321051/en/ (As of April 2012)

Language Settings

As Resource Orchestrator installs programs that correspond to the supported language, language settings (locale) cannot be changed after installation.

Therefore, set the language (locale) to Japanese or English according to your operational requirements.

The example of language settings (locale) confirmation methods is given below:

Example

For Windows
From the Control Panel, open "Date, Time, Language, and Regional Options" and select [Regional and Language Options].
For Red Hat Enterprise Linux 5
From the desktop screen, select [System]-[Administration]-[Language].

Tuning System Parameters (Admin Server) [Linux Manager]

Before installation, it is necessary to tune up system parameters for the admin server. See the table below for the system parameters that need to be tuned and their values.

Point

Set the values according to the "type" of each parameter as follows:

When the type is "setup value"
Modification is not necessary if already set value (default or previous value) is equal to or larger than the value in the table. If it is smaller than the value in the table, change the value to the one in the table.
When the type is "additional value"
Add the value in the table to already set value. Before adding the value, check the upper limit for the system, and set either the resulting value or the upper limit for the system, whichever is smaller.

For details, refer to the Linux manual.

Shared Memory

Parameter	Description	Value	Type
shmmax	Maximum Segment Size of Shared Memory	2684354560	Setup value
shmall	Total amount of shared memory available for use	655360	Setup value
shmmni	Maximum number of shared memory segments	113	Additional value

Semaphores

To configure semaphores, specify the value for each parameter in the following format:

kernel.sem = para1 para2 para3 para4

Parameter	Description	Value	Type
para1	Maximum number of semaphores for each semaphore identifier	512	Setup value
para2	Total number of semaphores in the system	14862	Additional value
para3	Maximum number of operators for each semaphore call	50	Setup value
para4	Total number of semaphore operators in the system	2208	Additional value

Message Queue

Parameter	Description	Value	Type
msgmax	Maximum size of a message	16384	Setup value
msgmnb	Maximum size of the messages that can be retained in a single message queue	114432	Setup value
msgmni	Maximum number of message queue IDs	1578	Additional value

[Tuning Procedure]

Use the following procedure to perform tuning:

Use the following command to check the values of the corresponding parameters currently configured for the system.

# /sbin/sysctl -a

Example

# /sbin/sysctl -a
...
  (omitted)
...

kernel.sem = 250 32000 32 128
kernel.msgmnb = 65536
kernel.msgmni = 16
kernel.msgmax = 65536
kernel.shmmni = 4096
kernel.shmall = 4294967296
kernel.shmmax = 68719476736

...
  (omitted)
...

For each parameter, compare the current value to that in the above table, and then calculate the appropriate value, based on its value type (setup or additional value).

Edit /etc/sysctl.conf. Edit the content as in the following example:

Example

kernel.sem = 512 13325 50 1358
kernel.msgmnb = 114432
kernel.msgmni = 1041
kernel.shmmni = 4154

Confirm that edited content is reflected in /etc/sysctl.conf, using the following command:
```
# /bin/cat /etc/sysctl.conf
```
Enable the configuration on 4. using one of the following methods:
- Reboot the system to reflect the settings
```
# /sbin/shutdown -r now
```
- Use /sbin/sysctl -p to reflect the settings
```
# /sbin/sysctl -p /etc/sysctl.conf (*)
```
  * Note: When using this command, reboot is not necessary.

Confirm that configured parameters are reflected, using the following command:

# /sbin/sysctl -a

Example

# /sbin/sysctl -a 
...
  (omitted)
...

kernel.sem = 512 13325 50 1358
kernel.msgmnb = 114432
kernel.msgmni = 1041
kernel.msgmax = 65536
kernel.shmmni = 4154
kernel.shmall = 4294967296
kernel.shmmax = 68719476736

...
  (omitted)
...

Before installing Resource Orchestrator, collect required information and check the system status, then determine the information to be specified on the installation window. The information that needs to be prepared is given below.

Installation Folder
Decide the installation folder for Resource Orchestrator.
Note that folders on removable disks cannot be specified.
Check that there are no files or folders in the installation folder.
Check that the necessary disk space can be secured on the drive for installation.
For the amount of disk space necessary for Resource Orchestrator, refer to "1.4.2.4 Static Disk Space" and "1.4.2.5 Dynamic Disk Space" of the "Setup Guide CE".
Image File Storage Folder
The image file storage folder is located in the installation folder.
Check that sufficient disk space can be secured on the drive where the storage folder will be created.
For the necessary disk space, refer to "1.4.2.5 Dynamic Disk Space" of the "Setup Guide CE".
For details of how to change the image file storage folder, refer to "5.5 rcxadm imagemgr" of the "Command Reference".

Port Number

When Resource Orchestrator is installed, the port numbers used by it will automatically be set in the services file of the system. So usually, there is no need to pay attention to port numbers.

If the port numbers used by Resource Orchestrator are being used for other applications, a message indicating that the numbers are in use is displayed when the installer is started, and installation will stop.
In that case, describe the entries for the following port numbers used by Resource Orchestrator in the services file using numbers not used by other software, and then start the installer.

Example

# service name port number/protocol name
nfdomain      23455/tcp
nfagent       23458/tcp
rcxmgr        23460/tcp
rcxweb        23461/tcp
rcxtask       23462/tcp
rcxmongrel1   23463/tcp
rcxmongrel2   23464/tcp
rcxdb         23465/tcp
rcxmongrel3   23466/tcp
rcxmongrel4   23467/tcp
rcxmongrel5   23468/tcp

For details, refer to "3.1.2 Changing Port Numbers" of the "User's Guide for Infrastructure Administrators (Resource Management) CE".

Directory Service Connection Information for Single Sign-On
Check the settings of the directory service used for Single Sign-On.
Refer to the following manual when the OpenDS that is included with ServerView Operations Manager is used.
"ServerView user management via an LDAP directory service" in the "ServerView Suite User Management in ServerView" manual of ServerView Operations Manager

Parameters Used for Installation

The following table contains the parameters used for installation.

[Windows]

No.	Window	Entry	Description
1	Installation Folder Selection	Installation Folder	This is the folder where Resource Orchestrator is installed. (*1) Default value: C:\Fujitsu\ROR The installation folder can contain 14 characters or less including the drive letter and "\". A path starting with "\\" or a relative path cannot be specified. It can contain alphanumeric characters, including hyphens ("-") and underscores ("_").
2	Administrative User Creation	User Account	This is the user account name to be used for logging into Resource Orchestrator as an administrative user. Specifying the administrator account, "administrator", of ServerView Operations Manager enables Single Sign-On coordination with ServerView Operations Manager when the OpenDS that is included with ServerView Operations Manager is used. The name must start with an alphabetic character and can be up to 16 alphanumeric characters long, including underscores ("_"), hyphens ("-"), and periods, ("."). Input is case-sensitive.
		Password	The password of the administrative user. The string must be composed of alphanumeric characters and symbols, and can be up to 16 characters long.
		Retype password
3	Admin LAN Selection	Network to use for the admin LAN	This is the network to be used as the admin LAN. Select it from the list. The maximum value for the subnet mask is 255.255.255.255(32bit mask). The minimum value is 255.255.0.0(16bit mask). However, 255.255.255.254 cannot be specified.
4	Directory Server Information 1/2	IP Address	This is the IP address of the directory server to be connected to.
		Port number	This is the port number of the directory server to be connected to. Check the settings of the directory server to be used. Specify a port number for SSL. "1474" is set as the initial port number for SSL when the OpenDS that is included with ServerView Operations Manager is used.
		Use of SSL for connecting to the Directory Server	Select "SSL Authentication".
		Directory Server Certificates	Specify the folder storing directory server CA certificates. Only server CA certificates are stored in this folder.
5	Directory Server Information 2/2	Base (DN)	This is the base name (DN) of the directory server to be connected to. Check the settings of the directory server to be used. "dc=fujitsu,dc=com" is set as the initial value when the OpenDS that is included with ServerView Operations Manager is used.
		Administrator (DN)	This is the administrator name (DN) of the directory server to be connected to. Check the settings of the directory server to be used. "cn=Directory Manager" is set when the OpenDS that is included with ServerView Operations Manager is used.
		Password	This is the password of the administrator of the directory server to be connected to. Check the settings of the directory server to be used. Refer to the following manual when the OpenDS that is included with ServerView Operations Manager is used. "ServerView user management with OpenDS" in the "ServerView Suite User Management in ServerView" manual of ServerView Operations Manager
6	Port Number Settings	Interstage Management Console	This is the port number of the Interstage management console. Default value: 12000
		Web Server (Interstage HTTP Server)	This is the port number of the Web server. Default value: 80
		CORBA Service	The port number of the CORBA service used by Resource Orchestrator. Default value: 8002
7	CMDB Destination Folder Selection	CMDB Manager's database installation folder	This is the folder to install the CMDB of Resource Orchestrator. The installation folder can contain 64 characters or less including the drive letter and "\". A path starting with "\\" or a relative path cannot be specified. It can contain alphanumeric characters, including hyphens ("-") and underscores ("_").
8	Admin Server Settings	FQDN for the Admin Server	The FQDN of the authentication server used by Resource Orchestrator. The FQDN of the authentication server must be the FQDN of the admin server. The FQDN can be up to 249 characters long and must be supported for name resolution.

*1: Specify an NTFS disk.

[Linux]

No.	Window	Entry	Description
1	Administrative User Creation	User Account	This is the user account name to be used for logging into Resource Orchestrator as an administrative user. Specifying the administrator account, "administrator", of ServerView Operations Manager enables Single Sign-On coordination with ServerView Operations Manager when the OpenDS that is included with ServerView Operations Manager is used. The name must start with an alphabetic character and can be up to 16 alphanumeric characters long, including underscores ("_"), hyphens ("-"), and periods, ("."). Input is case-sensitive.
		Password	The password of the administrative user. The string must be composed of alphanumeric characters and symbols, and can be up to 16 characters long.
		Retype password
2	Admin LAN Selection	Network to use for the admin LAN	This is the network to be used as the admin LAN. Select it from the list. The maximum value for the subnet mask is 255.255.255.255(32bit mask). The minimum value is 255.255.0.0(16bit mask). However, 255.255.255.254 cannot be specified.
3	Directory Server Information	IP Address	This is the IP address of the directory server to be connected to.
		Port number	This is the port number of the directory server to be connected to. Check the settings of the directory server to be used. Specify a port number for SSL. "1474" is set as the initial port number for SSL when the OpenDS that is included with ServerView Operations Manager is used.
		Use of SSL for connecting to the Directory Server	Select "SSL Authentication".
		Directory Server Certificates	Specify the directory used to store directory server CA certificates. Only server CA certificates are stored in this directory.
		Base (DN)	This is the base name (DN) of the directory server to be connected to. Check the settings of the directory server to be used. "dc=fujitsu,dc=com" is set as the initial value when the OpenDS that is included with ServerView Operations Manager is used.
		Administrator (DN)	This is the administrator name (DN) of the directory server to be connected to. Check the settings of the directory server to be used. "cn=Directory Manager" is set when the OpenDS that is included with ServerView Operations Manager is used.
		Password	This is the password of the administrator of the directory server to be connected to. Check the settings of the directory server to be used. Refer to the following manual when the OpenDS that is included with ServerView Operations Manager is used. "ServerView user management with OpenDS" in the "ServerView Suite User Management in ServerView" manual of ServerView Operations Manager
4	Port Number Settings	Interstage Management Console	This is the port number of the Interstage management console. Default value: 12000
		Web Server (Interstage HTTP Server)	This is the port number of the Web server. Default value: 80
		CORBA Service	The port number of the CORBA service used by Resource Orchestrator. Default value: 8002
5	CMDB Destination Folder Selection	CMDB Manager's database installation folder	This is the folder to install the CMDB of Resource Orchestrator. Enter a directory that already exists on the OS, using a maximum of 63 characters.
6	Admin Server Settings	FQDN for the Admin Server	The FQDN of the authentication server used by Resource Orchestrator. The FQDN of the authentication server must be the FQDN of the admin server. The FQDN can be up to 106 characters long and must be supported for name resolution.

2.1.1 Preparations

2.1.1.1 Software Preparation and Checks

2.1.1.2 Collecting and Checking Required Information

2.1.1.3 Configuration Parameter Checks