ServerView Resource Orchestrator Virtual Edition V3.1.0 Setup Guide

2.1.1 Preparations

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

• Host Name Checks

  Refer to "Host Name Checks".

• System Time Checks

  Refer to "System Time Checks".

• Exclusive Software Checks

  Refer to "Exclusive Software Checks".

• Required Software Preparation and Checks

  Refer to "Required Software Preparation and Checks".

• Required Patch Checks

  Refer to "Required Patch Checks".

• Required Package Checks [Linux Manager]

  Refer to "Required Package Checks [Linux Manager]".

• Collection and Checking of Required Information

  Refer to "2.1.1.2 Collecting and Checking Required Information".

• Configuration Parameter Checks

  Refer to "2.1.1.3 Configuration Parameter Checks".

• Checking Used Port Numbers

  Refer to "2.1.1.4 Checking Used Port Numbers".

  
  

2.1.1.1 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

[Windows Manager]

System_drive\Windows\System32\drivers\etc\hosts

[Linux Manager]

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

[Windows Manager]

1. Open [Add or Remove Programs] on the Windows Control Panel.

   The [Add or Remove Programs] window will be displayed.

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

   • "ServerView Resource Orchestrator Manager"

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

   Information

   For Windows Server 2008, select [Programs and Features] from the Windows Control Panel.

[Linux Manager]

1. Check that none of the software listed in "2.4.2.3 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, check that the required software given in "2.4.2.2 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.

Note

[Windows Manager]

• 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

  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 32-bit (x86)

    The Microsoft LAN Manager module can be installed without extracting it in advance.
    Deploy the obtained module to the folder that has been set for environment_variable%SystemRoot%.

  • When installing a manager on Windows 64-bit (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 (*) 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 limited to 3 characters.

    After extracting the following modules, deploy them to the folder that has been set for environment_variable%SystemRoot%.

    • 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 "7.6 Configuring the Network Environment" in the "Design Guide VE".

  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 Manager]

• 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

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

  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 necessary to configure the router settings. For details, refer to "7.6 Configuring the Network Environment" in the "Design Guide VE".

  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.

Required Patch Checks

Before installing Resource Orchestrator, check that the required patches for the manager listed in "2.4.2.1 Required Basic Software" in the "Design Guide VE" have been applied.

If they have not been applied, apply them before continuing.

Required Package Checks [Linux Manager]

Before installing Resource Orchestrator, check that the required packages for the manager [Linux Manager] listed in "2.4.2.1 Required Basic Software" in the "Design Guide VE" have been applied.

If they have not been installed, install them before continuing.

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 (when used)

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

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

• 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 "2.4.2.4 Static Disk Space" and "2.4.2.5 Dynamic Disk Space" in the "Design Guide VE".

• 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 "2.4.2.5 Dynamic Disk Space" in the "Design Guide VE".

  For details of how to change the image file storage folder, refer to 5.8 rcxadm imagemgr" in the "Reference Guide (Command) VE".

• Port Number

  For details on port numbers, refer to "2.1.1.4 Checking Used Port Numbers".

• Directory Service Connection Information for Single Sign-On

  When using Single Sign-On coordination with ServerView Operations Manager, check the settings of the directory service to be used.

  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 Manager]

No.	Window	Entry	Description
1	Installation Folder Selection	Installation Folder	This is the folder where Resource Orchestrator is installed. (*) When using a 64-bit (x64) OS Default value: C:\Program Files (x86)\Resource Orchestrator When using a 32-bit (x86) OS Default value: C:\Program Files\Resource Orchestrator The installation folder can contain 45 characters or less including the drive letter and "\". A path starting with "\\" or a relative path cannot be specified. Alphanumeric characters, underscores ("_"), hyphens ("-"), and blank spaces (" ") can be used.
2	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 administrator account, "administrator", of 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
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.
4	Authentication Method Selection	Authentication Method	Select one of the following options. "Internal Authentication" "ServerView Single sign-on (SSO)"

* Note: Specify an NTFS disk.

[Linux Manager]

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 administrator account, "administrator", of 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.1.3 Configuration Parameter Checks

Check configuration parameters following the procedure below:

[Windows Manager]

1. Log in as the administrator.

2. Start the installer.

   The installer is automatically displayed when the first DVD-ROM is set in the DVD drive. If it is not displayed, execute "RcSetup.exe" to start the installer.

3. Select "Tool" on the window displayed, and then click "Environment setup conditions check tool". Configuration parameter checking will start.

   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 C:\Windows\System32\drivers\etc\services.

   For the port information used by Resource Orchestrator, refer to "Appendix A Port List" in the "Design Guide CE".

   When ports being are used for something other than Resource Orchestrator, change the ports to use.

   For details on how to change ports to use, refer to "Appendix A Port List" in the "Design Guide CE".

4. When configuration parameter checking is completed, the check results will be saved in the following location.

   C:\temp\ror_precheckresult-YYYY-MM-DD-hhmmss.txt

   Refer to the check results, and check that no error is contained. If any error is contained, remove the causes of the error.
   The file of the result confirmation is not automatically deleted in the processing of the installation etc. Please delete it according to the timing that became unnecessary.

[Linux Manager]

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 agent installation command (the RcSetup.sh 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 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.

   For the port information used by Resource Orchestrator, refer to "Appendix A Port List" in the "Design Guide CE".

   When ports being are used for something other than Resource Orchestrator, change the ports to use.

   For details on how to change ports to use, refer to "Appendix A Port List" in the "Design Guide CE".

6. When the check is completed, the result will be sent to standard output.

   
   

2.1.1.4 Checking Used Port Numbers

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

For details on how to change the port number of the manager, refer to the following:

• "8.2 Changing Port Numbers" in the "User's Guide VE"

ephemeral Port [Windows Manager]

When the range of ephemeral port numbers on Windows is changed, the ephemeral port and the port to use conflict. In that case, select a port number which is not included in the range of the ephemeral port numbers.

The range of ephemeral port numbers is as below.

• For Windows 2003

  1025 to 5000

• For Windows 2008 or later

  49152 to 65535