2.2.1 Preparations

Software preparation and checks are explained in the following sections.

Exclusive Software Checks
Refer to "Exclusive Software Checks".
Required Software Checks
Refer to "Required Software Preparation and Checks".
Required Patch Checks
Refer to "Required Patch Checks".
Required Package Checks
Refer to "Required Package Checks [Linux]".

Exclusive Software Checks

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

[Windows] [Hyper-V]

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 "2.4.2.5 Exclusive Software" in the "Design Guide CE" has been installed on the system, and there is no information which shows a Resource Orchestrator agent has been installed.
- "ServerView Resource Orchestrator Agent"
When any of the exclusive software is displayed on the [Add or Remove Programs] window, uninstall it according to the procedure described in the relevant manual before installing Resource Orchestrator.
If agents of an earlier version of Resource Orchestrator have been installed, they can be upgraded. Refer to "F.3 Agent".
When reinstalling an agent on a system on which an agent of the same version of Resource Orchestrator has been installed, perform uninstallation referring to "20.2.1 Uninstallation [Windows] [Hyper-V]", and then perform installation.
Information
For Windows Server 2008 or later, select [Programs and Features] from the Windows Control Panel.

[Linux]

Check that none of the software listed in "2.4.2.5 Exclusive Software" in the "Design Guide CE" are displayed. Execute the following command and check if Resource Orchestrator Agent has been installed.
# rpm -q FJSVssagt <RETURN>
If the names of exclusive software have been displayed, uninstall them according to the procedure described in the relevant manual before proceeding.
If agents of an earlier version of Resource Orchestrator have been installed, they can be upgraded. Refer to "F.3 Agent".
When reinstalling an agent on a system on which an agent of the same version of Resource Orchestrator has been installed, perform uninstallation referring to "20.2.2 Uninstallation [Linux] [VMware] [Xen] [KVM] [OVM for x86 2.2]" and then perform installation.
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.

[Solaris] [Solaris Zones]

Check that none of the software listed in "2.4.2.5 Exclusive Software" in the "Design Guide CE" are displayed. Execute the following command and check if Resource Orchestrator Agent has been installed.
# pkginfo FJSVrcvat <RETURN>
If the names of exclusive software have been displayed, uninstall them according to the procedure described in the relevant manual before proceeding.
If agents of an earlier version of Resource Orchestrator have been installed, they can be upgraded. Refer to "F.3 Agent".
When reinstalling an agent on a system on which an agent of the same version of Resource Orchestrator has been installed, perform uninstallation referring to "20.2.3 Uninstallation [Solaris] [Solaris Zones] [OVM for SPARC]" and then perform installation.
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, check that the required software given in "2.4.2.4 Required Software" in the "Design Guide CE" has been installed. If it has not been installed, install it before continuing.

Note

ServerView Agents Settings
To operate Resource Orchestrator correctly on PRIMERGY series servers, perform the necessary settings for SNMP services during installation of ServerView Agents.
For how to perform SNMP service settings, refer to the ServerView Agents manual.
- For the SNMP community name, specify the same value as the SNMP community name set for the management blade.
- For the SNMP community name, set Read (reference) or Write (reference and updating) authority.
- For the host that receives SNMP packets, select [Accept SNMP packets from any host] or [Accept SNMP packets from these hosts] and set the admin LAN IP address of the admin server.
- For the SNMP trap target, set the IP address of the admin server.
  When an admin server with multiple NICs is set as the SNMP trap target, specify the IP address of the admin LAN used for communication with the managed server.
The "setupcl.exe" and "sysprep.exe" Modules
For Windows OSs other than Windows Server 2008 and Windows Server 2012, it is necessary to specify storage locations for the "setupcl.exe" and "sysprep.exe" modules during installation. Obtain the newest modules before starting installation of Resource Orchestrator.
For the method of obtaining the modules, refer to "2.4.2.4 Required Software" in the "Design Guide CE".
Extract the obtained module using the following method:
Example
When WindowsServer2003-KB926028-v2-x86-JPN.exe has been placed in c:\temp
>cd /d c:\temp <RETURN>
>WindowsServer2003-KB926028-v2-x86-JPN.exe /x <RETURN>
During installation, specify the cabinet file "deploy.cab" in the extracted folder, or the "setupcl.exe" and "sysprep.exe" modules contained in "deploy.cab".
After agent installation is complete, the extracted module is no longer necessary.

Required Patch Checks

Before installing Resource Orchestrator, check that the required patches for the agent listed in "2.4.2.2 Required Patches" in the "Design Guide CE" have been applied.

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

Required Package Checks [Linux]

Before installing Resource Orchestrator, check that the required packages [Linux] for the agent listed in "2.4.2.3 Required Packages" in the "Design Guide CE" have been applied.

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

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

Red Hat Enterprise Linux 6 Preconfiguration

Only perform this when using Red Hat Enterprise Linux 6 as the basic software of a server.

When using cloning and server switchover, perform the following procedure to modify the configuration file.

Execute the following command.

# systool -c net <RETURN>

Example

# systool -c net <RETURN>
Class = "net"
Class Device = "eth0"
Device =
"0000:01:00.0"
Class Device = "eth1"
Device =
"0000:01:00.1"
Class Device = "eth2"
Device =
"0000:2:00 AM.0"
Class Device = "eth3"
Device =
"0000:2:00 AM.1"
Class Device = "lo"
Class Device = "sit0"

Confirm the device name which is displayed after "Class Device =" and the PCI bus number which is displayed after "Device =" in the command output results.
Correct the configuration file.
After confirming support for device name and MAC address in the following configuration file, change ATTR{address}=="MAC_address" to KERNELS=="PCI_bus_number".
All corresponding lines should be corrected.
Configuration File Storage Location
/etc/udev/rules.d/70-persistent-net.rules
Example
- Before changing
  SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
  ATTR{address}=="MAC_address", ATTR{type}=="1", KERNEL=="eth*",
  NAME="Device_name"
- After changing
  SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
  KERNELS=="PCI_bus_number", ATTR{type}=="1", KERNEL=="eth*",
  NAME="Device_name"
After restarting the managed servers, check if communication with the entire network is possible.

Disable NetworkManager service
1. Execute the following commands to disable the NetworkManager service.
  # service NetworkManager stop <RETURN>
  # chkconfig NetworkManager off <RETURN>
2. Edit the "/etc/sysconfig/network-scripts/ifcfg-ethX" files(ethX is the interface name of eth0, eth1, etc.) to change the value for NM_CONTROLLED to "no".
  Example
  - Before changing
    DEVICE="eth0"
    HWADDR="xx:xx:xx:xx:xx:xx"
    NM_CONTROLLED="yes"
    ONBOOT="yes"
    TYPE=Ethernet
  - After changing
    DEVICE="eth0"
    HWADDR="xx:xx:xx:xx:xx:xx"
    NM_CONTROLLED="no"
    ONBOOT="yes"
    TYPE=Ethernet
3. Execute the following command to restart the network service.
  # service network restart <RETURN>

Configuration File Check

When using Red Hat Enterprise Linux
When using the following functions, check the configuration files of network interfaces before installing Resource Orchestrator, and release any settings made to bind MAC addresses.
- Server switchover
- Cloning
Only perform this when using Red Hat Enterprise Linux 4 AS/ES as the basic software of a server.
Refer to the /etc/sysconfig/network-scripts/ifcfg-ethX file (ethX is an interface name such as eth0 or eth1), and check that there is no line starting with "HWADDR=" in the file.
If there is a line starting with "HWADDR=", this is because the network interface is bound to a MAC address. In that case, comment out the line.
Example
When the admin LAN interface is eth0
DEVICE=eth0
#HWADDR=xx:xx:xx:xx:xx:xx <- If this line exists, comment it out.
ONBOOT=yes
TYPE=Ethernet

When using SUSE Linux Enterprise Server

When using cloning and server switchover, perform the following procedure to modify the configuration file.

Execute the following command.

# systool -c net <RETURN>

Example

# systool -c net <RETURN>
Class = "net"

  Class Device = "eth0"
    Device = "0000:01:00.0"

  Class Device = "eth1"
    Device = "0000:01:00.1"

  Class Device = "eth2"
    Device = "0000:2:00 AM.0"

  Class Device = "eth3"
    Device = "0000:2:00 AM.1"

  Class Device = "lo"

  Class Device = "sit0"

Confirm the device name which is given after "Class Device =" and PCI bus number which is given after "Device =" in the command output results.
Modify the configuration file.
When using SUSE Linux Enterprise Server 10
a. After confirming support for device name and MAC address in the following configuration file, change SYSFS{address}=="MAC_address" to ID=="PCI_bus_number".
All corresponding lines should be corrected.
Support of the device name and MAC address will be used after step b.
/etc/udev/rules.d/30-net_persistent_names.rules
Before changing
SUBSYSTEM=="net", ACTION=="add", SYSFS{address}=="MAC_address", IMPORT="/lib/udev/rename_netiface %k device_name"
After changing
SUBSYSTEM=="net", ACTION=="add", ID=="PCI_bus_number", IMPORT="/lib/udev/rename_netiface %k device_name"
b. Based on the results of step 1 and a in step 3, change the name of the following file will be to a name that includes the PCI bus number.
Before changing
/etc/sysconfig/network/ifcfg-eth-id-MAC address
After changing
/etc/sysconfig/network/ifcfg-eth-bus-pci-PCI bus number
When using SUSE Linux Enterprise Server 11
Change ATTR{address}=="MAC address" to KERNELS=="PCI_bus_number" in the following configuration file.
All corresponding lines should be corrected.
/etc/udev/rules.d/70-persistent-net.rules
Before changing
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="MAC_address", ATTR{type}=="1", KERNEL=="eth*", NAME="device_name"
After changing
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", KERNELS=="PCI_bus_number", ATTR{type}=="1", KERNEL=="eth*", NAME="device_name"
After restarting the managed servers, check if communication with the entire network is possible.

When using cloning or the backup and restore method for server switchover, during installation perform partition settings so that names of device paths are defined using the "Device Name" format (for example: /dev/sda1) in the /etc/fstab file.
When installation is already complete, change the names of device paths defined in the boot configuration files /boot/efi/SuSE/elilo.conf and /boot/grub/menu.lst, and the /etc/fstab file so they use the "Device Name" format (for example: /dev/sda1).For specific details about the mount definition, please refer to the following URL and search for the Document ID:3580082.
http://www.suse.com/documentation/

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 and available disk space
Decide the installation folder for Resource Orchestrator. 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.6 Static Disk Space" and "2.4.2.7 Dynamic Disk Space" in the "Design Guide CE".
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 port numbers used by Resource Orchestrator in the services file using numbers not used by other software, and then start the installer.
For details, refer to "7.1.6 Changing Port Numbers" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Check the status of the admin LAN and NIC
Decide the network (IP addresses) to be used for the admin LAN.
Check that the NIC used for communication with the admin LAN is enabled.
For details on admin LANs, refer to "9.1.1 Admin LAN Network Design" in the "Design Guide CE".
[Linux] [Xen] [KVM]
Make the numeral of the managed server's network interface name (ethX) one of a consecutive sequence starting from 0. For the settings, refer to the manual for the OS.
Check the target disk of image operations
For backup and restoration of system images to disks, refer to "16.1 Overview" in the "User's Guide VE".
For details on disks for cloning, refer to "12.1 Overview" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".

Windows Volume License Information [Windows]

When using the following functions, you must have a volume license for the version of Windows to be installed on managed servers by Resource Orchestrator.
Check whether the Windows license you have purchased is a volume license.

Server switchover (HBA address rename method/ VIOM server profile switchover method)
Cloning
Restoration after server replacement
Server replacement using HBA address rename

When using cloning, you must enter volume license information when installing Resource Orchestrator.
Depending on the version of Windows being used, check the following information prior to installation.

For Windows Server 2003
Check the product key.
Generally, the product key is provided with the DVD-ROM of the Windows OS purchased.

For Windows Server 2008 or Later

Check the information necessary for license authentication (activation).
The two activation methods are Key Management Service (KMS) and Multiple Activation Key (MAK). Check which method you will use.

Check the following information required for activation depending on the method you will use.

Activation Information

Table 2.2 Activation Information Methods and Information to Check
Method	Information to Check
KMS (*1)	The KMS host name (FQDN) or the computer name or IP address Port number (Default 1688) (*2)
MAK	The MAK key

*1: When using Domain Name Service (DNS) to automatically find the KMS host, checking is not necessary.
*2: When changing the port number from the default (1688), correct the definition file after installing agents. Refer to "12.2 Collecting" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".

Proxy Server Information
When using a proxy server to connect to the KMS host (KMS method) or the Volume Activation Management Tool (VAMT) to authenticate a proxy license (MAK method), check the host name or IP address, and the port number of the proxy server.
Administrator's Password
Check the password as it is necessary for performing activation.

Windows Administrator accounts
When using Windows Server 2008 or later, check whether Administrator accounts have been changed (renamed).
Environments which have been changed (renamed) are not supported.

2.2.1 Preparations

2.2.1.1 Software Preparation and Checks

2.2.1.2 Collecting and Checking Required Information