Top
ServerView Resource Orchestrator Virtual Edition V3.1.2 Setup Guide
FUJITSU Software
Chapter 2 Installation > 2.1 Manager Installation > 2.1.2 Manager Installation [Linux Manager]
PreviousNext

2.1.2 Manager Installation [Linux Manager]

This section explains installation of Linux managers.

2.1.2.1 Preparations

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

2.1.2.2 Software Preparation and Checks

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

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.


System Time Checks

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


Exclusive Software Checks

Before installing Resource Orchestrator, check that the software listed in "2.4.2.5 Exclusive Software" in the "Design Guide VE" 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.

  1. Check that none of the software listed in "2.4.2.5 Exclusive Software" in the "Design Guide VE" or the following software are displayed.

    Execute the following command and check if Resource Orchestrator Manager has been installed.

    # rpm -q FJSVrcvmr <RETURN>

  2. 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 "E.2 Manager".
    When reinstalling a manager on a system on which the same version of Resource Orchestrator has been installed, perform uninstallation referring to "11.1 Manager Uninstallation", and then perform the reinstallation.

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.

  • 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, perform the following operations.
In addition, check that the required software, such as ServerView Operations Manager, given in "2.4.2.4 Required Software" in the "Design Guide VE" has been installed. If it has not been installed, install it before continuing.

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


Required Patch Checks

Before installing Resource Orchestrator, check that the required patches for the manager listed in "2.4.2.2 Required Patches" in the "Design Guide VE" 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 "2.4.2.3 Required Packages" in the "Design Guide VE" 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:


Single Sign-On Preparation and Checks (when used)

To use Single Sign-On (SSO) coordination, before installing Resource Orchestrator, certificate preparation and user registration of an administrator (privileged user) with the directory service are required.
For details, refer to "Chapter 10 Installing and Defining Single Sign-On" in the "Design Guide VE".


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.

[Tuning Procedure]

Use the following procedure to perform tuning:

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

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

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

    Example

    kernel.sem = 250 33071 32 191
kernel.shmmni = 4097

  4. Confirm that edited content is reflected in /etc/sysctl.conf, using the following command:

    # /bin/cat /etc/sysctl.conf

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

      * When using this command, reboot is not necessary.

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

    # /sbin/sysctl -a

    Example

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

kernel.sem = 250 33071 32 191
kernel.msgmnb = 65536
kernel.msgmni = 16
kernel.msgmax = 65536
kernel.shmmni = 4097
kernel.shmall = 4294967296
kernel.shmmax = 68719476736

...
  (omitted)
...

2.1.2.3 Collecting and Checking Required Information

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.

Parameters Used for Installation

The following table contains the parameters used for installation.

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.

  • When using Single Sign-On

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

    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.

  • When not using Single Sign-On

    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.

Specify when not using Single Sign-On

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.

3

Authentication Method Selection

Authentication Method

Select one of the following options.

  • Internal Authentication

  • ServerView Single sign-on (SSO)

2.1.2.4 Checking Used Port Numbers

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.

Ports Automatically Set in the services File of the System
# 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

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 being are 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 VE".


Changing Port Numbers

To change port numbers after installing the manager, refer to the following:


2.1.2.5 Configuration Parameter Checks

Check configuration parameters following the procedure below:

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

  2. Set the first Resource Orchestrator DVD-ROM.

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

  4. Execute the following installation command:

    # cd DVD-ROM_mount_point <RETURN>
    # ./RcSetup.sh <RETURN>

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

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

  7. 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 "2.4 Software Environment" and "2.5 Hardware Environment" in the "Design Guide VE".

2.1.2.6 Installation

The procedure for manager installation is given below.

Before installation, check if "2.1.2.1 Preparations" have been performed.


Current Directory Setting

Do not set the current directory to the DVD-ROM to allow disk switching.


Settings in Single User Mode

In single user mode, X Window Sytem does not start, and one of the following operations is required.

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

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 VE" with the port numbers changed to during installation.


Installation

The procedure for manager installation is given below.

  1. Log in to the system as the OS administrator (root).

    Boot the admin server that Resource Orchestrator is to be installed on in multi-user mode, and then log in to the system using root.

  2. Set the first Resource Orchestrator DVD-ROM and execute the following command to mount the DVD-ROM. If the auto-mounting daemon (autofs) is used for DVD-ROM auto-mounting, the installer fails to start due to its "noexec" mount option.

    # mount -t iso9660 -r /dev/hdc DVD-ROM_mount_point <RETURN>

  3. Execute the manager installation command (the RcSetup.sh command).

    # DVD-ROM_mount_point/RcSetup.sh <RETURN>

  4. Select "1. Manager(Virtual Edition) installation".

  5. Perform installation according to the installer's interactive instructions.

    Enter the parameters prepared and confirmed in "Parameters Used for Installation" in "2.1.2.3 Collecting and Checking Required Information".

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.

  • Uninstall the Related Services

    When locating ServerView Deployment Manager in the same subnet, it is necessary to uninstall the related services.

    For the method for uninstalling the related services, please refer to "5.1 deployment_service_uninstall" in the "Reference Guide (Command) VE".


PreviousNext
Copyright 2010-2015 FUJITSU LIMITED