Top
ServerView Resource Coordinator VE Installation Guide
Chapter 4 Upgrading from Earlier Versions > 4.3 Agent
PreviousNext

4.3 Agent

This section explains the upgrading of agents.
Upgrading of agents is not mandatory even when managers have been upgraded to this version. Perform upgrades if necessary.


Transferred Data

The following agent data is transferred:

Data and work files which are transferred during upgrade installation are stored in the following folder. Ensure that the folder is not deleted until after the upgrade is complete.

[Windows/Hyper-V]
Drive_name\Program Files\RCVE-upgradedata

[Linux/VMware/Xen]
/var/opt/RCVE-upgradedata

[Solaris]
/var/opt/RCVE-upgradedata

Preparations

Perform the following preparations and checks before upgrading:

Upgrade using Upgrade Installation

When performing upgrade installation from V2.1.1 of agents in Windows environments, upgrade installation can be performed using the installer of this version.

Use the following procedure to upgrade agents of earlier versions to agents of this version on all of the managed servers that are being upgraded.

Note

  • Do not perform any other operations with Resource Coordinator VE until the upgrade is completed.

  • Perform upgrading of agents after upgrading of managers is completed.

  • In the event that upgrade installation fails, please resolve the cause of the failure and perform upgrade installation again. If the problem cannot be resolved and upgrade installation fails again, please contact Fujitsu technical staff.

  • When performing an upgrade installation, please do not access the installation folder of the earlier version or any of the files and folders inside it using the command prompt, Explorer, or an editor.
    While it is being accessed, attempts to perform upgrade installation will fail.
    If upgrade installation fails, stop accessing the files or folders and then perform the upgrade installation again.

  • When stopping the upgrade and restoring the earlier version, please re-install the agent of the earlier version and then replace the information that was backed up during the preparations.
    When performing restoration and an agent of this version or an earlier version has been installed, please uninstall it.
    After restoration, please delete the folder containing the backed up assets.

  • Upgrade installation will delete patches that were applied to the earlier version.

    [Linux]
    When the PATH variable has not been configured to enable execution of UpdateAdvisor (Middleware) commands from a user-defined location, performing uninstallation will delete any patches that have been applied to the earlier version of Resource Coordinator VE, but it will not delete product information or component information. Refer to the UpdateAdvisor (Middleware) manual, delete software and component information from the applied modification check list.

  1. Upgrade Installation

    [Windows/Hyper-V]
    Refer to "2.2.2 Installation [Windows/Hyper-V]", and execute the Resource Coordinator VE installer.
    The Resource Coordinator VE setup window will be displayed. Check the contents of the license agreement, etc. and then click <Yes>.
    The setting information that will be taken over from the earlier version will be displayed. Please check it and then click <Install>. Upgrade installation will begin.

    [Linux/VMware/Xen]
    Refer to "2.2.3 Installation [Linux/VMware/Xen]", and execute the Resource Coordinator VE installer.
    Check the contents of the license agreement, etc. and then enter "y".
    The setting information that will be taken over from the earlier version will be displayed. Please check it and then enter "y". Upgrade installation will begin.

    [Solaris]
    Refer to "2.2.4 Installation [Solaris]", and execute the Resource Coordinator VE installer.
    Check the contents of the license agreement, etc. and then enter "y". Upgrade installation will begin.

Note

  • After upgrading agents, use the RC console to check if the upgraded managed servers are being displayed correctly.

  • Updating of system images and cloning images is advised after agents have been upgraded.

  • When upgrade installation is conducted on SUSE Linux Enterprise Server, upgrade installation will be conducted successfully even if the following message is displayed.

    insserv: Warning, current runlevel(s) of script `scwagent' overwrites defaults.


Manual Upgrade

Upgrading of V13.2 or V13.3 agents is performed by exporting and importing system configuration files for pre-configuration.
Use the following procedure to upgrade agents of earlier versions to agents of this version on all of the managed servers that are being upgraded.

Note

  • Do not perform any other operations with Resource Coordinator VE until the upgrade is completed.

  • Perform upgrading of agents after upgrading of managers is completed.

  • When using the network parameter auto-configuration function during deployment of cloning images, specify the same installation folder for agents of the earlier version and those of this version.

  1. Set Maintenance Mode

    When server switchover settings have been performed for managed servers, place them into maintenance mode.
    When managed servers are set as spare servers, place the managed servers set as spare servers into maintenance mode.

  2. Backing up (copying) of Network Parameter Auto-configuration Function Definition Files

    When using the network parameter auto-configuration function during deployment of cloning images, back up (copy) the following folders and files to a location other than the agent installation folder.

    [Windows/Hyper-V]
    Installation_folder\Agent\etc\event_script folder
    Installation_folder\Agent\etc\ipaddr.conf file
    Installation_folder\Agent\etc\FJSVrcx.conf file

    [Linux/VMware/Xen]
    /etc/opt/FJSVrcxat/event_script_directory
    /etc/opt/FJSVnrmp/lan/ipaddr.conf file
    /etc/FJSVrcx.conf file

    [Solaris]
    There is no configuration file to back up.

  3. Uninstallation of Earlier Version Agents

    Refer to the "Systemwalker Resource Coordinator Virtual server Edition Installation Guide", and uninstall the agents.

  4. Installation of Agents of This Version

    Install agents of this version.
    For installation, refer to "2.2 Agent Installation".

  5. Restoration of Network Parameter Auto-configuration Function Definition Files

    When using the network parameter auto-configuration function during deployment of cloning images, restore the definition file that was backed up (copied) in step 2. When step 2. was not performed this step is not necessary.

    1. Stop agents.

      For stopping agents, refer to "5.2 Agent" of the "ServerView Resource Coordinator VE Setup Guide".

    2. Restore the definition file.

      Restore the folders and files backed up (copied) in step 2. to the following locations in the installation folder of this version:

      [Windows/Hyper-V]
      Installation_folder\Agent\etc\event_script folder
      Installation_folder\Agent\etc\ipaddr.conf file
      Installation_folder\Agent\etc\FJSVrcx.conf file

      [Linux/VMware/Xen]
      /etc/opt/FJSVrcxat/event_script_directory
      /etc/opt/FJSVnrmp/lan/ipaddr.conf file
      /etc/FJSVrcx.conf file

      [Solaris]
      There is no configuration file to restore.

    3. Start agents.

      For starting agents, refer to "5.2 Agent" of the "ServerView Resource Coordinator VE Setup Guide".

  6. Release Maintenance Mode

    Release the maintenance mode of managed servers placed into maintenance mode in step 1.

Note

  • After upgrading agents, use the RC console to check that the upgraded managed servers are being displayed correctly.

  • Updating of system images and cloning images is advised after agents have been upgraded.

PreviousNext
Copyright 2007-2010 FUJITSU LIMITED