This section explains installation of Linux managers.
This section explains the preparations and checks required before commencing installation.
Post-uninstallation Procedure
Before installing Resource Orchestrator in an environment from which Resource Orchestrator has been deleted, perform the post-uninstallation procedure.
Refer to "11.1.4 Post-uninstallation Procedure".
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
/etc/hosts
Note
When configuring the hosts file, note the following.
Do not set the host name (FQDN) and the computer name to "127.0.0.1".
Confirm that "127.0.0.1" (IPv4 format) is set to "localhost".
Note that IPv6 format must not be set.
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 localhost.localdomain localhost
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.
This configuration is necessary when Single Sign-On is configured.
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 [System Condition] tab on the ROR console.
Exclusive Software Checks
Uninstall exclusive software before installing Resource Orchestrator.
For details of exclusive software, refer to "6.1.2.5 Exclusive Software" in "Overview".
Note
When uninstalling exclusive software, there are cases where other system operation administrators might have installed the software, so check that deleting the software causes no problems before actually doing so.
Required Software Preparation and Checks
Before installing Resource Orchestrator, perform the following operations.
In addition, check that the required software, such as ServerView Operations Manager, given in "6.1.2.4 Required Software" in the "Overview" has been installed. If it has not been installed, install it before continuing.
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.
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 |
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> |
Use the Windows 8.3 format (*) for the folder name or the file name.
After manager installation is complete, the extracted Microsoft LAN Manager module is no longer necessary.
* Note: File names are limited to 8 characters and extensions are limited to 3 characters.
After extracting the following modules, deploy them to /tmp on the system for installation.
PROTMAN.DOS
PROTMAN.EXE
NETBIND.COM
ServerView Operations Manager Settings
In order to open the console screen of the managed server, register the account of the Remote Management Controller with the ServerView Operations Manager.
For the setting method, refer to the ServerView Operations Manager manual.
Settings for 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 |
It is also necessary to enable the automatic startup setting for the snmptrapd daemon.
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 be necessary to configure the router settings. For details, refer to "9.2.4.2 Admin LAN Settings" in the "Design 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 "5.11 Registering Admin LAN Subnets" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Install the DHCP server following the procedure below:
Install the dhcp package.
Execute the following command to modify the setting so the DHCP server service (dhcpd) is not automatically started.
# chkconfig dhcpd off <RETURN> |
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.
Required Patch Checks
Before installing Resource Orchestrator, check that the required patches for the manager listed in "6.1.2.2 Required Patches" in the "Overview" have been applied.
If they have not been applied, apply them before continuing.
Required Package Checks
Before installing Resource Orchestrator, check that the required packages for the manager [Linux manager] listed in "6.1.2.3 Required Packages" in the "Overview" have been applied.
If they have not been installed, install them before continuing.
User Account Checks
This product automatically creates the user accounts listed below - if an application is using these OS user accounts, ensure there is no impact on the application before deleting them:
rcxdb (for connecting to the database)
rcxctdbbpm (for starting up database services for process management)
rcxctdbchg (for starting up database services for metering)
rcxctdbdsb (for starting up database services for the dashboard (pool status))
Single Sign-On Preparation and Checks (when used)
Before installing Resource Orchestrator, install ServerView Operations Manager.
Configure the directory service at that time.
It is also necessary to prepare certificates and perform registration of an administrator (privileged user) with the directory service.
For details, refer to "Chapter 12 Configuring Single Sign-On" in the "Design Guide CE".
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
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
The installation directory of Resource Orchestrator is as below. It cannot be changed.
/opt
/etc/opt
/var/opt
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 "6.1.2.6 Static Disk Space" and "6.1.2.7 Dynamic Disk Space" in the "Overview".
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 "6.1.2.7 Dynamic Disk Space" in the "Overview".
For details of how to change the image file storage folder, refer to 5.9 rcxadm imagemgr" in the "Reference Guide (Command/XML) CE".
Port number
For details on port numbers, refer to "2.1.2.4 Checking Used Port Numbers".
Directory Service Connection Information for Single Sign-On of ServerView Operations Manager
Confirm that the directory service used for Single Sign-On of ServerView Operations Manager is correctly configured.
This can be performed using either of the following procedures:
Log in to ServerView Operations Manager.
Refer to the following manuals:
Manual for ServerView Operations Manager:
"ServerView user management via an LDAP directory service" in "FUJITSU ServerView Suite User Management in ServerView"
Manual for ServerView Operations Manager:
"Starting ServerView Operations Manager" in "FUJITSU Software ServerView Suite ServerView Operations Manager" (User's guide)
Perform modification installation of ServerView Operations Manager.
When performing modification installation, the settings of directory service can be checked.
Refer to the following manuals:
Manual for ServerView Operations Manager:
"ServerView user management via an LDAP directory service" in "FUJITSU ServerView Suite User Management in ServerView"
Manual for ServerView Operations Manager:
"Installing the Operations Manager software" in "FUJITSU Software ServerView Suite ServerView Operations Manager Installation ServerView Operations Manager Software under Linux"
If the settings of the directory service for ServerView Operations Manager are correct, exit the modification installation without making any changes.
If there are errors in the settings of the directory service for ServerView Operations, perform modification installation of ServerView Operations Manager to correct the errors.
Parameters Used for Installation
The following table contains the parameters used for installation.
No. | Window | Entry | Description |
|---|---|---|---|
1 | 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. |
2 | Authentication Method Selection | Authentication Method | Select one of the following options.
|
3 | Administrative User Creation | User Account | This is the user account name to be used for logging into Resource Orchestrator as an administrative user. The name must start with an alphanumeric 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 the following symbols (excluding blank spaces), and can be 8 - 16 characters long. """, "$", "'", "(",")", "`" If any of the above symbols are specified, change the password of the privileged user after setup is complete. | ||
Retype password | |||
Administrative User Settings | User Account | This is the user account name to be used for logging into Resource Orchestrator as an administrative user. Specify the user registered in the directory service in "Single Sign-On Preparation and Checks (when used)" in "2.1.2.2 Software Preparation and Checks". When using the directory service provided with ServerView Operations Manager, specifying "administrator", which is the administrator account of ServerView Operations Manager, enables Single Sign-On coordination with ServerView Operations Manager. The name must start with an alphanumeric character and can be up to 16 alphanumeric characters long, including underscores ("_"), hyphens ("-"), and periods, ("."). Input is case-sensitive. | |
4 | Language Settings | Language | Select one of the following options.
|
Ports Automatically Set in the services File of the System
When Resource Orchestrator is installed, the port numbers used by it will automatically be set in the services file of the system.
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.
# service name port number/protocol name FJSVctdsb-sqcdcm-dbm 2511/tcp FJSVctdsb-sqcdcm-fcmsys 2512/tcp rcxctext 3500/tcp rcxctext2 3501/tcp rcxctdsb 3502/tcp rcxctrestchg 3550/tcp rcxctint 3551/tcp rcxctdbchg 5441/tcp rcxctdbdsb 5442/tcp rcxcfvsys 8013/tcp rcxcfapi 8014/tcp rcxctacnt 8015/tcp FJSVctdsbCMDBgui 13200/tcp FJSVctdsbCMDBmgr 13201/tcp 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 rcxjeedomainadmin 23851/tcp rcxjeedomaininstance 23852/tcp rcxjeedomainjmx 23853/tcp rcxjeehttpssl 23854/tcp rcxjeejms 23855/tcp rcxjeeorblistener 23856/tcp rcxjeeorbmutualauth 23857/tcp rcxjeeorbssl 23858/tcp rcxmessagebroker 23861/tcp rcxbpmsvasadminlistener 23862/tcp rcxbpmsvhttplistener 23863/tcp rcxbpmsvhttpssllistener 23864/tcp rcxbpmsviioplistener 23865/tcp rcxbpmsviiopssllistener 23866/tcp rcxbpmsviiopsslmutualauth 23867/tcp rcxbpmsvjmxsystemconnector 23868/tcp rcxbpmsvjavadebugger 23869/tcp rcxbpmconasadminlistener 23870/tcp rcxbpmconhttplistener 23871/tcp rcxbpmconhttpssllistener 23872/tcp rcxbpmconiioplistener 23873/tcp rcxbpmconiiopssllistener 23874/tcp rcxbpmconiiopsslmutualauth 23875/tcp rcxbpmconjmxsystemconnector 23876/tcp rcxbpmconjavadebugger 23877/tcp rcxbpmsvdb 23878/tcp FJSVctdsbEFServer 61320/tcp
Checking Port Usage Status
Execute the "Environment setup conditions check tool" in "2.1.2.5 Configuration Parameter Checks" to check the port usage status.
For ports with "is in use" displayed for the result of "Port status", confirm that those ports are used with the purpose of usage for Resource Orchestrator defined in /etc/services.
When ports are being used for something other than Resource Orchestrator, change the ports to use.
For the port information used by Resource Orchestrator, refer to "Appendix A Port List" in the "Design Guide CE".
Changing Port Numbers
To change port numbers after installing the manager, refer to the following:
"6.2 Changing Port Numbers" in the "User's Guide for Infrastructure Administrators (Resource Management) CE"
"8.3 Settings for Port Number of Admin Servers" in the "Operation Guide CE"
Check configuration parameters following the procedure below:
Log in to the system as the OS administrator (root).
Boot the admin server in multi-user mode to check that the server meets requirements for installation, and then log in to the system using root.
Set the first Resource Orchestrator DVD-ROM.
Execute the following command to mount the DVD-ROM. If the auto-mounting daemon (autofs) is used for starting the mounted DVD-ROM, the installer will fail to start due to its "noexec" mount option.
# mount -t iso9660 -r /dev/hdc DVD-ROM_mount_point <RETURN>
Execute the following installation command:
# DVD-ROM_mount_point/RcSetup.sh <RETURN>
Select "Environment setup conditions check tool" from the menu to execute the tool.
For the check items with the edition name displayed in the check results, check only the items corresponding to the edition to be installed.
When the check is completed, the result will be sent to standard output.
The following items are displayed as the items to be checked:
Required Software (LAN Manager module)
Required Software (ETERNUS SF Storage Cruiser)
Disk Space (Express/Virtual Edition)
Disk Space (Cloud Edition)
Memory Size (Express/Virtual Edition)
Memory Size (Cloud Edition)
cpu
SNMP Service
Port Status (Express/Virtual Edition)
Port Status (Cloud Edition)
Confirm that "Warning" or "NG" is not included in the check results. If there are check items that were determined as "Warning" or "NG", resolve the cause of the problem based on the output message. For details of the corrective actions, refer to "2.1.2.1 Preparations" and "6.1 Software Environment" and "6.2 Hardware Environment" in the "Overview".
The procedure for manager installation is given below.
Before installation, check if "2.1.2.1 Preparations" have been performed.
Settings in Single User Mode
In single user mode, X Window System does not start, and one of the following operations is required.
Switching virtual consoles (using the [Ctrl] + [Alt] + [Fn] keys)
Making commands run in the background
Nullifying Firewall Settings for Ports to be used by Resource Orchestrator
When installing Resource Orchestrator on systems with active firewalls, in order to enable correct communication between the manager, agents, and clients, disable the firewall settings for the port numbers to be used for communication.
For the port numbers used by Resource Orchestrator and required software, refer to "Appendix A Port List" in the "Design Guide CE".
However, when port numbers have been changed by editing the services file during installation of Resource Orchestrator, replace the default port numbers listed in "Appendix A Port List" in the "Design Guide CE" with the port numbers changed to during installation.
Installation
The procedure for manager installation is given below.
Log in to the system as the OS administrator (root).
Boot the admin server that the manager is to be installed on in multi-user mode, and then log in to the system using root.
Set the first Resource Orchestrator DVD-ROM.
Execute the following command to mount the DVD-ROM.
# mount -t iso9660 -r /dev/hdc DVD-ROM_mount_point <RETURN>
Note
If the auto-mounting daemon (autofs) is used for DVD-ROM auto-mounting, the installer fails to start due to its "noexec" mount option.
Set the same value for the first and second DVD-ROMs in the DVD mount point.
Execute the following installation command:
Do not set the current directory to the DVD-ROM to allow disk switching.
# DVD-ROM_mount_point/RcSetup.sh <RETURN>
Select "Cloud Edition".
Select "Manager installation".
Perform installation according to the installer's interactive instructions.
Enter the parameters designed and checked in "Parameters Used for Installation" in "2.1.2.3 Collecting and Checking Required Information".
A message for disk switching will be output.
Start a different terminal (such as a GNOME terminal), and then eject the DVD-ROM using the following command.
# eject DVD-ROM_mount_point <RETURN>
Set the second DVD-ROM and wait for the completion of auto-mounting.
Mount the DVD-ROM again.
# umount DVD-ROM_mount_point <RETURN> # mount -t iso9660 -r /dev/hdc DVD-ROM_mount_point <RETURN>
Press the [Enter] key to continue the installation.
Settings when SELinux is Used
When enabling SELinux, it is necessary to perform configuration of SELinux after installing Resource Orchestrator.
For details on configuration, refer to "J.1.1 Manager".
Note
Corrective Action for Installation Failure
In the event of installation failure, restart the OS and then log in as the user that performed the installation, and perform uninstallation following the uninstallation procedure.
After that, remove the cause of the failure referring to the meaning of the output message and the suggested corrective actions, and then perform installation again.
If there are internal inconsistencies detected during installation, the messages "The problem occurred while installing it" or "It failed in the installation" will be displayed and installation will fail. In this case, uninstall the manager and reinstall it. If the problem persists, please contact Fujitsu technical staff.
If installation stopped before the process was complete, perform the following corrective actions.
Forcibly stop the installation.
Perform uninstallation.
Refer to "11.1 Manager Uninstallation".
Execute the post-uninstallation procedure.
Perform installation again.
Post-installation Cautions
The following users are added. When installing Resource Orchestrator, do not delete these accounts.
Account Name | Usage |
|---|---|
rcxdb | rcxdb is used as the OS account for connecting to the database service of Resource Orchestrator. |
rcxctdbbpm | rcxctdbbpm is used as the OS account for starting the database service for process management. |
rcxctdbchg | rcxctdbchg is used as the OS account for starting the database service for metering. |
rcxctdbdsb | rcxctdbdsb is used as an OS account to start the database service for dashboards. |
