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 operations
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 a server, 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 the Manager".
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:
Configuration 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.
| 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.
Start the manager.
For details on how to start and stop the manager, refer to "2.1 Starting and Stopping the Manager".
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.
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.
[Windows Manager]
Installation_folder\SVROR\Manager\etc\customize_data
[Linux Manager]
/etc/opt/FJSVrcvmr/customize_data
rcx_base.rcxprop
Describe the definition file in individual lines as below:
Key = Value
Specify the following items.
Item | Key | Value | Remarks |
|---|---|---|---|
Multiplicity | TASK_WORKER_COUNT | Specify the multiplicity from 5 - 30. | The default value is "30". For basic mode, the default value is "5". 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 TASK_WORKER_COUNT values for rcx_base.rcxprop files.
When there is no rcx_base.rcxprop file, create one.
Start 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
Start 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 the Manager".
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 from a value in the table and the memory size required for the manager operations described in "2.4.2.6 Memory Size" in the "Design Guide CE", and then add memory if necessary.
Multiplicity | Increase in Memory Use (Unit: MB) |
|---|---|
5 | - |
6 - 14 | 1080 + (Multiplicity * 40) |
15 - 30 | 2104 + (Multiplicity * 40) |
