This appendix provides important reminders for the operation of Resource Orchestrator.
Redundancy Configurations for the Admin LAN
If communication issues occur on the admin LAN, or one of the network interfaces used by a managed server on the admin LAN fails, the following operations may result in errors. In such cases, restore the admin LAN network as quickly as possible.
Backup and Restore
Collection and deployment of cloning images
Server switchover and failback
HBA address rename
With Resource Orchestrator, the factory-set WWN of a managed server's HBA is overridden when the HBA address rename function is used. The WWN is reset to its factory-set value when the server is deleted from Resource Orchestrator.
Before using HBAs in an environment that is not managed by Resource Orchestrator, first delete the server in which it is mounted using the ROR console.
For details on how to delete servers, refer to "9.2 Deleting Managed Servers" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
The WWN of a managed server is set during startup, using a network boot session to connect to the admin server. Once set up with a proper WWN, the managed server reboots into its own operating system.
Therefore, a managed server may reboot during its startup.
Do not move HBAs whose HBA address rename settings have been set up to different managed servers. If operating HBAs without resetting their WWNs, when the same WWN is configured on multiple servers data may be damaged by same volume access.
Changing the Manager's System Time
When the admin server's system time is reset to a time in the past, the resource monitoring by the manager stops for this period. To reset the system time to more than just a few minutes in the past, return the time and then restart the manager.
For details on how to restart the manager, refer to "2.1 Starting and Stopping Managers".
Restarting Managers
By default, the manager services restart at 3:45 am every day for stable system operation.
The settings for restarting can be changed depending on the authority level. To change the configuration, perform the following:
Settings file
[Windows Manager]
Installation_folder\SVROR\Manager\rails\config\rcx\rcx_manager_params.rb
[Linux Manager]
/opt/FJSVrcvmr/rails/config/rcx/rcx_manager_params.rb
Configuration Parameters
Parameter | Meaning | Initial Value |
|---|---|---|
RESTART_ENABLE | Select the restart operation status. Specify one of the following:
| true |
RESTART_HOUR | Specify the restart time (hour) from 0 to 23. | 3 |
RESTART_MIN | Specify the restart time (minutes) from 0 to 59. | 45 |
RESTART_CYCLE | Specify the restart interval (days) from 1 to 5. | 1 |
Parameter Change Procedure
Stop the manager.
Use an editor and change the parameters of the rcx_manager_params.rb file.
Restart the manager.
For details on how to start and stop the manager, refer to "2.1 Starting and Stopping Managers".
Note
The conditions for restarting are, that more than RESTART_CYCLE * 24 hours have passed since manager was started and it is the time specified for RESTART_HOUR and RESTART_MIN.
For the stable operation of systems, configure the restarting of managers to occur on a daily basis.
When upgrading managers, check the setting details in advance, and re-set them after the upgrade is complete.
Changing Multiple Operations of Managers
When executing multiple operations simultaneously, the upper limit is set for the number of simultaneous operations.
The upper limit of the number of simultaneous operations can be changed depending on the usage environment. To change the configuration, edit the following definition file.
When there is no definition file, create one.
[Linux Manager]
/etc/opt/FJSVrcvmr/customize_data
[Windows Manager]
Installation_folder\SVROR\Manager\etc\customize_data
rcx_base.rcxprop
Describe the definition file in individual lines as below:
Key = Value |
Specify the following items.
Items | Key | Value | Remarks |
|---|---|---|---|
Multiplicity | TASK_WORKER_COUNT | Specify the multiplicity from 5 - 30. | The initial value is "30". Operates by default, when there are no definition files. |
An example definition file is indicated below. In this example, the multiplicity is set to "10".
TASK_WORKER_COUNT=10 |
Changing Procedures of Definition Files
When the manager is operating in a normal environment
Stop the manager.
Change the TASK_WORKER_COUNT value in the rcx_base.rcxprop file.
When there is no rcx_base.rcxprop file, create one.
Restart the manager.
When the manager is operating in a cluster environment
[Windows Manager]
Stop the manager.
Place the shared disk of the manager online. Place other cluster resources offline.
Change the TASK_WORKER_COUNT values for rcx_base.rcxprop files on the shared disk.
When there is no rcx_base.rcxprop file, create one.
Drive_name\Fujitsu\ROR\SVROR\customize_data\rcx_base.rcxprop
Restart the manager.
[Linux Manager]
Stop the manager.
Mount the shared disk of the admin server on the primary node or the secondary node.
Change the TASK_WORKER_COUNT values for rcx_base.rcxprop files in the shared disk.
When there is no rcx_base.rcxprop file, create one.
Destination_to_mount_shared_disk/Fujitsu/ROR/SVROR/etc/opt/FJSVrcvmr/customize_data/rcx_base.rcxprop
Unmount the shared disk for the admin server from the node mounted in step 2.
Restart the manager.
For details on how to start and stop the manager, refer to "2.1 Starting and Stopping Managers".
Note
Advisory Notes for Basic Mode
Memory usage will increase according to the multiplicity.
For details on the memory usage to increase, refer to "Table A.3 Increased Memory Use with Multiple Operations".
Calculate the memory used using the values in the table and the memory size required for the manager operations described in "6.1.2.8 Memory Size" in the "Overview", and then add memory if necessary.
Multiplicity | Increase in Memory Use (in MB) |
|---|---|
5 | - |
6 - 14 | 1080 + (Multiplicity * 40) |
15 - 30 | 2104 + (Multiplicity * 40) |
Modification of Extended Partitioning Mode when Using the PRIMEQUEST 2000 Series
When modifying Extended Partitioning Mode of the partition on which the business server/host operate when using PRIMEQUEST 2000 series, re-register the partition used in the following procedure with Resource Orchestrator.
When the currently used partition is a PPAR partition, and when using an Extended Partition with "Enable" configured for PPAR [Extended Partitioning Mode]
Unregister the relevant managed server in the orchestration tree.
For details on how to unregister resources, refer to "19.4 Unregistration" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Delete the relevant managed server in the server tree.
For details on how to delete managed servers, refer to "9.2 Deleting Managed Servers" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Modify the settings of [Extended Partitioning Mode] from the management console of the PRIMEQUEST MMB.
For details on how to modify Extended Partitioning Mode, refer to the operation management manuals for the PRIMEQUEST 2000 series.
Register the relevant Extended Partition in the server tree.
For details on how to register managed servers, refer to "5.8.2 Registering PRIMEQUEST Servers" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Register the relevant Extended Partition in a resource pool using the orchestration tree.
For details on how to register resource pools, refer to "Chapter 14 Registering Resources in Resource Pools" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
When the currently used partition is an Extended Partition, and when using an Extended Partition with "Disable" configured for PPAR [Extended Partitioning Mode]
Unregister the relevant managed server in the orchestration tree.
For details on how to unregister resources, refer to "19.4 Unregistration" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Delete the relevant managed server in the server tree.
For details on how to delete managed servers, refer to "9.2 Deleting Managed Servers" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Modify the settings of [Extended Partitioning Mode] from the management console of the PRIMEQUEST MMB.
For details on how to modify Extended Partitioning Mode, refer to the operation management manuals for the PRIMEQUEST 2000 series.
Register the relevant PPAR partition in the server tree.
For details on how to register managed servers, refer to "5.8.2 Registering PRIMEQUEST Servers" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Register the relevant Extended Partition in a resource pool using the orchestration tree.
For details on how to register resource pools, refer to "Chapter 14 Registering Resources in Resource Pools" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Modification of PPAR Extended Partition Configurations when Using the PRIMEQUEST 2000 Series
When modifying PPAR Extended Partition configurations of the partition on which the business server/host operate when using PRIMEQUEST 2000 series, re-register the partition used in the following procedure with Resource Orchestrator.
Unregister the relevant managed server in the orchestration tree.
For details on how to unregister resources, refer to "19.4 Unregistration" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Delete the relevant managed server in the server tree.
For details on how to delete managed servers, refer to "9.2 Deleting Managed Servers" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Modify the settings of "Partition Configuration" from the management console of the PRIMEQUEST MMB.
For details on how to modify the PRIMEQUEST 2000 series, refer to the operation management manuals for the PRIMEQUEST 2000 series.
Register the relevant managed server in the server tree.
For details on how to register managed servers, refer to "5.8.2 Registering PRIMEQUEST Servers" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Register the relevant managed server in a resource pool using the orchestration tree.
For details on how to register resource pools, refer to "Chapter 14 Registering Resources in Resource Pools" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Changing Monitoring Timeout Values of Physical Server Power Operations
The time elapsed from the start to finish of a power operation of a physical server may exceed the timeout value for power operations. Therefore, perform power operations using the actual system to estimate the timeout value based on the actual measured values.
In the definition files, timeout values are specified for different server models. As a result, changes in the timeout values for each model of server managed by the manager are reflected on the manager.
When changing a timeout value, create the following definition file.
[Windows Manager]
Installation_folder\SVROR\Manager\etc\customize_data
[Linux Manager]
/etc/opt/FJSVrcvmr/customize_data
power_timeout.rcxprop
In the definition file, each line contains configuration information for a model of server (model name, timeout values for powering the server on, rebooting it, powering it off, etc.), separated using commas (","). Each line is exported in the following format.
model,boot_timeout,shutdown_timeout |
Any blank spaces before or after the commas are ignored.
When adding comments, start the line with a number sign ("#").
Specify the following items.
Describe the model name of the server to modify the timeout value for.
The value is displayed in [General]-[Model name] of the [Resource Details] tab in the [ROR Console]
For Fujitsu M10-4S, enter "M10-4S".
Describe the timeout value of powering on and rebooting the server.
This value is also used for as the timeout value when starting or rebooting a managed server in image operations.
Specify a value in seconds using an integer greater than 0.
If any other value is specified, the default timeout value is used.
Point
A timeout value of less than 5940 seconds is recommended.
Model | Powering On or Rebooting | Image Operation | |
|---|---|---|---|
Start | Reboot | ||
RX4770 M1 or later | 5700 | 5700 | 5700 |
Fujitsu M10-1/M10-4 | 1800 | (*) | (*) |
Fujitsu M10-4S | 2700 | (*) | (*) |
PRIMEQUEST 2000 series | 900 | 3600 | 3600 |
Other models | 900 | 900 | 1800 |
* Note: Image operations of Fujitsu M10 model servers are not supported.
Specify the timeout value for powering off of the server.
Specify a value in seconds using an integer greater than 0.
If any other value is specified, the default timeout value is used.
Model | Power the Server Off |
|---|---|
Fujitsu M10-1/M10-4 | 900 |
Fujitsu M10-4S | 1200 |
Other models | 900 |
Example
RX4770M2,5700,900 |
It is not necessary to restart the manager after creating or modifying a definition file. Changes are reflected on the manager after the definition file is changed.
