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
Before upgrading, note that the following agent resources are transferred:
Definition files of the network parameter auto-configuration function (when the network parameter auto-configuration function is being used)
[Windows] [Hyper-V]
Installation_folder\Agent\etc\event_script folder
Installation_folder\Agent\etc\ipaddr.conf file
Installation_folder\Agent\etc\ipaddr.conf file
[Linux] [VMware] [Xen] [KVM]
/etc/opt/FJSVrcxat/event_script directory
/etc/opt/FJSVnrmp/lan/ipaddr.conf file
/etc/FJSVrcx.conf file
[Solaris]
There is no resource to transfer.
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]
32-bit (x86) OS
Drive_name\Program Files\RCVE-upgradedata
64-bit (x64) OS
Drive_name\Program Files (x86)\RCVE-upgradedata
[Linux] [VMware] [Xen] [KVM]
/var/opt/RCVE-upgradedata
[Solaris]
/var/opt/RCVE-upgradedata
Preparations
Perform the following preparations and checks before upgrading:
Check that the environment is one in which agents of this version can be operated.
For the operational environment, refer to "2.4 Software Environment" and "2.5 Hardware Environment" in the "Design Guide CE".
To enable recovery in case there is unexpected trouble during the upgrade process, back up the folders and files listed in "Transferred Data" to a folder other than the agent installation folder.
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.
On the managed server on which the agent (Dashboard Function) is installed, the agent (Dashboard Function) is also upgraded when performing upgrade installation of the agent.
Note
Do not perform any other operations with Resource Orchestrator 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 upgrade installation will delete any patches that have been applied to the old version, but it will not delete product information or component information. Refer to the UpdateAdvisor (Middleware) manual and delete software and component information from the applied modification checklist.
Upgrade Installation
[Windows] [Hyper-V]
Refer to "2.2.2 Installation [Windows] [Hyper-V]", and execute the Resource Orchestrator installer.
The Resource Orchestrator 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] [KVM]
Refer to "2.2.3 Installation [Linux] [VMware] [Xen] [KVM] [OVM for x86 2.2]", and execute the Resource Orchestrator 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.
Note
After upgrading agents, use the ROR 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. |
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.
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\ipaddr.conf file
[Linux] [VMware] [Xen] [KVM]
/etc/opt/FJSVrcxat/event_script directory
/etc/opt/FJSVnrmp/lan/ipaddr.conf file
/etc/FJSVrcx.conf file
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 files that were backed up (copied) in 3. When 3 was not performed, this step is not necessary.
Stop agents.
For the method for stopping agents, refer to "2.2 Starting and Stopping Agents" in the "Operation Guide CE".
Restore the definition file.
Restore the folders and files backed up (copied) in 3 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\ipaddr.conf file
[Linux] [VMware] [Xen] [KVM]
/etc/opt/FJSVrcxat/event_script directory
/etc/opt/FJSVnrmp/lan/ipaddr.conf file
/etc/FJSVrcx.conf file
Start agents.
For the method for starting agents, refer to "2.2 Starting and Stopping Agents" in the "Operation Guide CE".
Setup agents (Dashboard Function)
Execute the command below.
[Windows] [Hyper-V]
> Installation_folder\RCXCTMGA\setup\dsbsetup.bat IP_address <RETURN>
[Linux]
# /opt/FJSVssqc/setup/dsbsetup.sh IP_address <RETURN>
Specify the admin LAN IP address of the managed server for IP address. It takes a few minutes to complete the command.
[Solaris]
The command does not have to be executed.
Release Maintenance Mode
Release the maintenance mode of managed servers placed into maintenance mode in 2.
Note
After upgrading agents, use the ROR 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.
Transfer of Agents Using Re-installation or the Pre-configuration Function
Use the following procedure to perform transfer from agents of earlier versions to agents on this version on all managed servers for which transfer using the pre-configuration function will be performed.
Note
Do not perform any other operations with Resource Orchestrator until the transfer using the pre-configuration function is completed.
Perform transfer of agents after transfer of the manager using the pre-configuration function 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.
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.
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\ipaddr.conf file
[Linux] [VMware] [Xen] [KVM]
/etc/opt/FJSVrcxat/event_script directory
/etc/opt/FJSVnrmp/lan/ipaddr.conf file
/etc/FJSVrcx.conf file
Uninstall Earlier Version ROR Agents
Refer to the "ServerView Resource Orchestrator User's Guide", and uninstall the agents.
Install ROR CE Agents
Install ROR CE agents.
For installation, refer to "2.2 Agent Installation".
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 files that were backed up (copied) in 2. When 2 was not performed, this step is not necessary.
Stop agents.
For the method for stopping agents, refer to "2.2 Starting and Stopping Agents" in the "Operation Guide CE".
Restore the definition file.
Restore the folders and files backed up (copied) in 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\ipaddr.conf file
[Linux] [VMware] [Xen] [KVM]
/etc/opt/FJSVrcxat/event_script directory
/etc/opt/FJSVnrmp/lan/ipaddr.conf file
/etc/FJSVrcx.conf file
Start agents.
For the method for starting agents, refer to "2.2 Starting and Stopping Agents" in the "Operation Guide CE".
Setup agents (Dashboard Function)
Execute the command below.
[Windows] [Hyper-V]
> Installation_folder\RCXCTMGA\setup\dsbsetup.bat IP_address <RETURN>
[Linux]
# /opt/FJSVssqc/setup/dsbsetup.sh IP_address <RETURN>
Specify the admin LAN IP address of the managed server for IP address. It takes a few minutes to complete the command.
[Solaris]
The command does not have to be executed.
Release Maintenance Mode
Release the maintenance mode of managed servers placed into maintenance mode in 1.
Note
After transferring agents, use the ROR 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 transferred.
Upgrading with ServerView Update Manager or ServerView Update Manager Express
Upgrade installation can be performed with ServerView Update Manager or ServerView Update Manager Express when upgrading to this version from RCVE V2.2.2 or later.
Refer to the manual of ServerView Update Manager or ServerView Update Manager Express for the procedure.
Note
To upgrade with ServerView Update Manager, the server to be upgrade must be managed by ServerView Operations Manager.
OSs and hardware supported by ServerView Update Manager or ServerView Update Manager Express can be updated.
For Linux or VMware, the installed ServerView Agents must be at least V5.01.08.
Do not perform any other operations with Resource Orchestrator 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, Windows 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 upgrade installation will delete any patches that have been applied to the old version, but it will not delete product information or component information. Refer to the UpdateAdvisor (Middleware) manual and delete software and component information from the applied modification checklist.
After upgrading agents, use the ROR 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.
