Top
ServerView Resource Orchestrator Cloud Edition V3.2.0 Setup Guide
FUJITSU Software
Chapter 2 Installation > 2.2 Agent Installation > 2.2.1 Preparations
PreviousNext

2.2.1 Preparations

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

2.2.1.1 Software Preparation and Checks

Software preparation and checks are explained in the following sections.


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, check that the required software given in "6.1.2.4 Required Software" in the "Overview" has been installed. If it has not been installed, install it before continuing.

Note

  • ServerView Agents Settings

    To operate Resource Orchestrator correctly on PRIMERGY or PRIMEQUEST series servers, perform the necessary settings for SNMP services during installation of ServerView Agents, and start 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 "6.1.2.4 Required Software" in the "Overview".

    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 "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 [Linux]

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

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


Check the Network Interface Definition File

This configuration is necessary in the following case.

When using the following functions, check the definition files of network interfaces and perform configuration before installing Resource Orchestrator.

When using Red Hat Enterprise Linux 6

Use the following procedure to modify the configuration file:

  1. 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:02:00.0"
Class Device = "eth3"
Device =
"0000:02:00.1"
Class Device = "lo"
Class Device = "sit0"

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

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

  4. After restarting the managed servers, check if communication with the entire network is possible.

When Using SUSE Linux Enterprise Server

Use the following procedure to modify the configuration file:

  1. 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:02:00.0"

  Class Device = "eth3"
    Device = "0000:2:00.1"

  Class Device = "lo"

  Class Device = "sit0"

  2. Confirm the device name which is given after "Class Device =" and PCI bus number which is given after "Device =" in the command output results.

  3. Modify the configuration file.

    When using SUSE Linux Enterprise Server 10

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

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

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

  4. After restarting the managed servers, check if communication with the entire network is possible.

Information

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/


Disabling the NetworkManager Service

  1. Execute the following command to disable the NetworkManager service.

    • When using Red Hat Enterprise Linux 5 and Red Hat Enterprise Linux 6

      # service NetworkManager stop <RETURN>
      # chkconfig NetworkManager off <RETURN>

    • When using Red Hat Enterprise Linux 7

      # systemctl stop NetworkManager <RETURN>
      # systemctl disable NetworkManager <RETURN>

  2. After modifying the "/etc/sysconfig/network-scripts/ifcfg-exxx" file, configure "no" for "NM_CONTROLLED".

    exxx is the configuration file for the Ethernet interface.
    When using Red Hat Enterprise Linux 5 and Red Hat Enterprise Linux 6, "eth0", "eth1", or "eth2" will be used as the file name.
    When using Red Hat Enterprise Linux 7, "enp1s0f1" or "enp5s0f1" will be used as the file name.

    Example

    • Before modifying

      DEVICE="eth0"
      HWADDR="xx:xx:xx:xx:xx:xx"
      NM_CONTROLLED="yes"
      ONBOOT="yes"
      TYPE=Ethernet

    • After modifying

      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.

    • When using Red Hat Enterprise Linux 5 and Red Hat Enterprise Linux 6

      # service network restart <RETURN>

    • When using Red Hat Enterprise Linux 7

      # systemctl restart network <RETURN>


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


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

PreviousNext
Copyright 2010-2016 FUJITSU LIMITED