This section explains the definition file.
When using a physical L-Server, the configuration of the definition file may be necessary.
When using SAN storage
Refer to "6.1.1 Creating Definition Files Combining Ports of SAN Storage".
When using ETERNUS storage
Refer to "Format Selection for the Names of Virtual Storage Resources and Disk Resources Managed by ESC".
When configuring Thin Provisioning attributes on a storage pool
Refer to "Configuring Thin Provisioning Attributes for Storage Pools" in "12.2 Resource Pool Operations" of the "User's Guide for Infrastructure Administrators (Resource Management) CE".
When using configuration of priority for resource selection on Thin Provisioning and Automatic Storage Layering
When using dynamic LUN mirroring
Refer to "Creating Mirroring Definition Files for Dynamic LUN Mirroring".
When using EMC storage
For details, refer to "Definition File for EMC Storage".
When creating a physical L-Server without specifying a model name in the L-Server template
Refer to "Configuration when Creating a Physical L-Server without Specifying a Model Name in the L-Server Template".
When the number of FCs fitted and their position are different depending on the physical server
Refer to "Setting the Number of FCs Fitted and their Position for Each Physical Server".
When using alive monitoring
Refer to "Definition File for Alive Monitoring".
Format Selection for the Names of Virtual Storage Resources and Disk Resources Managed by ESC
The format of the names of virtual storage resources and disk resources managed by ESC can be selected. When the definition file has been edited, restart the manager.
[Windows]
Installation_folder\Manager\etc\customize_data
[Linux]
/etc/opt/FJSVrcvmr/customize_data
storage.rcxprop
In the definition file, the items to set are entered on individual lines. Each line is entered in the following format.
Item_specified = Value_specified |
Select the format of the name of disk resources managed by ESC.
If "true" is specified
The disk resource name is used as the alias name for ESC. If the format of the alias name is unavailable for the format of the disk resource name, Resource Orchestrator automatically sets a disk resource name that conforms to the alias name. Even if "true" has been specified, when ESC does not support the alias name, the combination of the IP address of ETERNUS, the RAID group number, and the volume number will be used as the disk resource name.
If "false" is specified
The combination of the IP address of ETERNUS, the RAID group number, and the volume number will be used as the disk resource name.
If nothing is specified
"false" is set.
Note
If the disk has been separated from the virtual storage and saved, then the ETERNUS LUN alias name is not reflected on the disk resource name even if the value is "true".
Select the format of the name of virtual storage resources managed by ESC.
If "true" is specified
The RAID group name of ESC is used as the disk resource name. If the format of the RAID group name is unavailable for the format of the virtual storage resource name, Resource Orchestrator automatically set a virtual storage resource name that conforms to the RAID group name. Even if "true" has been specified, when ESC does not support the RAID group name, the combination of the IP address of ESC and the RAID group number will be used as the virtual storage resource name.
If "false" is specified
The combination of the IP address of ESC and the RAID group number will be used as the virtual storage resource name.
If nothing is specified
"false" is set.
Example
An example definition file is indicated below.
ETERNUS_VOLUME_NAME_TO_DISK_NAME = true |
Configuration of Priority for Resource Selection on Thin Provisioning on Thin Provisioning and Automatic Storage Layering
The following resources can be registered in a storage pool with thin provisioning attributes set:
FTRP and FTV for Automatic Storage Layering
TPP and TPV for Thin Provisioning
When setting to automatic selection for resource selection while creating L-Server or attaching a disk under the condition that both storage pools with and without the configuration of thin provisioning attributes remain the same priority, either of their resources can be given higher priority.
When the definition file has been edited, restart the manager.
[Windows]
Installation_folder\Manager\etc\customize_data
[Linux]
/etc/opt/FJSVrcvmr/customize_data
storage.rcxprop
In the definition file, the items to set are entered on individual lines. Each line is entered in the following format.
Specified item = Specified value |
When both storage pools with and without the configuration of thin provisioning attributes remain the same priority, either of their resources can be given higher priority for automatic selection of storage resource.
If "true" is specified
A storage pool with thin provisioning attributes will be given priority.
If "false" is specified
A storage pool without thin provisioning attributes will be given priority.
If nothing is specified
"false" is set.
Example
An example definition file is indicated below.
SELECT_THIN_PROVISIONING_POOL_FIRST = true |
Creating Mirroring Definition Files for Dynamic LUN Mirroring
When using dynamic LUN mirroring, create a mirroring definition file and configure the ETERNUS storage to create a copied volume.
[Windows]
Installation_folder\Manager\etc\customize_data
[Linux]
/etc/opt/FJSVrcvmr/customize_data
storage_mirroring.rcxprop
Describe the virtual storage information. Each virtual storage information must be described using a single line, and be in the following format starting from the start of the line. Use of line breaks is not allowed.
local_storage_ipaddr,virtual_storage_type,local_storage_number,remote_storege_boxid,remote_storage_number,copy_group |
Enter the IP address of the local site ETERNUS storage device that will automatically create the disk resource.
Specify the virtual server type.
Specify "RAID" for RAID group.
Specify "TPP" for TPP.
Specify the RAID group or TPP number from which the disk resource will be extracted in the ETERNUS storage on the local site.
Specify 4-digit hexadecimal numbers starting with 0x.
Specify the BOX-ID of ETERNUS storage in the remote side to create the copied volume.
Check the BOX-ID in "Advanced Copy Path Status" which is the Web GUI for ETERNUS.
Specify the RAID group or TPP number that will be used to create the copied volume in the ETERNUS storage on the remote site.
Specify 4-digit hexadecimal numbers starting with 0x.
Specify the name for the copy group created when setting inter-chassis copying.
Example
An example definition file is indicated below.
192.168.1.24,RAID,0x0011,00ETERNUSDXLS2ET092DD#####LN4521132A09##,0x0022,group1 |
Definition File for EMC Storage
When registering EMC Navisphere Manager or EMC Solutions Enabler as storage management software, it is necessary to specify the installation folder of Navisphere CLI or SYMCLI in the definition file for EMC storage.
[Windows]
Installation_folder\Manager\sys\usm\etc
[Linux]
/opt/FJSVrcvmr/sys/usm/etc
emcpath.conf
The format of the definition file for EMC storage is as follows:
When registering EMC Navisphere Manager as storage management software, modify the line beginning with "naviseccli".
naviseccli=Navisphere CLI_installation_folder |
When registering EMC Solutions Enabler for storage management software, modify the line beginning with "symcli".
symcli=SYMCLI_installation_folder |
[Windows]
Use "\\" for the file separator. Do not modify the line beginning with "secfilepath".
Example
[Windows]
naviseccli=C:\\Program Files\\EMC\\Navisphere CLI |
[Linux]
naviseccli=/opt/Navisphere/bin |
Configuration when Creating a Physical L-Server without Specifying a Model Name in the L-Server Template
To create a physical L-Server without specifying a model name in the L-Server template, create the definition file, define the configuration information (CPU core count, CPU clock speed, memory capacity, etc.), and then register the server as a managed server.
In the following cases, create the definition file first, and then register the hardware information with Resource Orchestrator again.
If the target server was registered with Resource Orchestrator before creation of the definition file
When modifying the configuration information (CPU core count, CPU clock speed, memory capacity, etc.) in the definition file of a server that has been registered with Resource Orchestrator
For details, refer to "Chapter 7 Hardware Maintenance" in the "Operation Guide CE".
Note
If the value entered in the definition file differs from the actual configuration information of the server, creation or starting of physical L-Servers may fail, or physical servers may be deployed with incorrect information about CPU and memory.
Be sure to confirm that the values entered in the definition file and the actual configuration information of the server are the same.
[Windows]
Installation_folder\Manager\etc\customize_data
[Linux]
/etc/opt/FJSVrcvmr/customize_data
server_spec.rcxprop
[Windows/Linux]
UTF-8
[Windows]
CR/LF
[Linux]
LF
The following line must be entered in the first line of definition files.
ServerSpec,V1.0 |
In the definition file, enter the configuration information (CPU core count, CPU clock speed, memory capacity, etc.), separated by commas (",").
When defining two or more servers, use line breaks.
Each line is entered in the following format.
physical_server, cpu_core_count, cpu_clock, memory_size[, cpu_type] |
Blank spaces between data and commas (",") are ignored.
If there is duplicated configuration information (CPU core count, CPU clock speed, memory capacity, etc.) for the same physical server, the values that appear first will be used.
When adding comments, start the line with a number sign ("#").
Enter the same physical server name as the one entered when registering a managed server.
Enter a character string beginning with an alphabetical character and containing up to 15 alphanumeric characters and hyphens ("-").
Enter the total number of physical CPU cores.
Enter an integer between 0 and 999.
When entering "0", hyphens ("-") are displayed in the basic information on the resource details screen, and physical L-Servers cannot be created.
Enter the CPU clock speed.
Enter an integer between 0 and 999,999.
Use megahertz for the unit. Enter 1,000 MHz for 1 GHz, for example.
When entering "0", hyphens ("-") are displayed in the basic information on the resource details screen, and physical L-Servers cannot be created.
Enter the total memory size.
Enter an integer between 0 and 999,999,999.
Use megabytes for the unit. Enter 1,024 MB for 1 GB, for example.
When entering "0", hyphens ("-") are displayed in the basic information on the resource details screen, and physical L-Servers cannot be created.
Enter the CPU type.
The string must be composed of alphanumeric characters and symbols (ASCII characters 0x20 to 0x7e), except for commas (","), and can be up to 64 characters long.
When omitted, a hyphen ("-") is displayed.
Example
An example definition file is indicated below.
ServerSpec,V1.0 |
Setting the Number of FCs Fitted and their Position for Each Physical Server
If the number of FCs fitted or their location differs from physical server to physical server, prepare an FC connection pattern and define the number of FCs and their location for each physical server.
This setting can be made when the storage units are the following:
EMC CLARiiON Storage
EMC Symmetrix DMX Storage
EMC Symmetrix VMAX Storage
[Windows]
Installation_folder\Manager\etc\customize_data\fc_connection_pattern
[Linux]
/etc/opt/FJSVrcvmr/customize_data/fc_connection_pattern
Make the file extension .rcxprop and then allocate a file with an arbitrary file name. Specify the file name using the following string:
The file name must start with an alphanumeric character, and can contain up to 64 alphanumeric characters, underscores ("_"), and hyphens ("-").
Create a different FC pattern file for each system that has a different pattern.
NUM_OF_FC=Number_of_FCs_used |
Specify the number of FCs to be used. 1, 2, and 4 can be specified for the number.
Specify the number of HBAs that are actually mounted on the server.
Allocate a sequential number to all of the ports, sorted in the expansion slot order.
By specifying the HBA number, up to two FC ports can be set as Boot paths.
The priority of HBA numbers is set based on the order in which they are listed.
Only numbers under the value specified in NUM_OF_FC can be specified.
NUM_OF_FC value | Valid Range of HBA Numbers |
|---|---|
4 | 0 - 3 |
2 | 0 - 1 |
1 | 0 |
Specify as many as there are connected storage chassis. However, the number in X must be a decimal between 0 and 99, starting from 0 and counting up.
Specify the storage chassis identification number.
Define the FCPort pairing on the server to be used, separating with a colon (:).
Define the FCPort pairing on the storage side, separating with a colon (:).
By specifying separate HBA numbers for each STORAGE_X, logical paths to two storage chassis can be set from each single physical server.
However, if the same storage chassis identification number is defined multiple times, the one defined first will be valid.
Note
The file names of FC connection patterns cannot be changed after performing the following operations:
Import of the L-Server template specifying an FC connection pattern
Turning on of the physical L-Server with a definition specifying an FC connection pattern
Creation of a physical L-Server specifying an FC connection pattern
The details of FC connection pattern files can only be changed in the following cases:
When a physical L-Server with an FC connection pattern specified is in the defined state
Example
An example definition file is indicated below.
If 2 paths (1 boot path)
NUM_OF_FC = "2" |
If 2 paths (2 boot path)
NUM_OF_FC = "2" |
If 4 paths (1 chassis)
NUM_OF_FC = "4" |
If 4 paths (2 chassis)
NUM_OF_FC = "4" |
Definition File for Alive Monitoring
When using alive monitoring, create the definition file and specify the parameters for alive monitoring. The configuration of this parameter must be unique in the system.
When using alive monitoring on a physical L-Server, monitor hang-up of the operating system corresponding to a physical L-Server using the OS Ping response.
For details on Ping monitoring, refer to "8.4 Configuring Monitoring Information" in the "Setup Guide VE".
The file in which the default values are described is located during installation.
[Windows]
Installation_folder\Manager\etc\customize_data\alive_monitoring
[Linux]
/etc/opt/FJSVrcvmr/customize_data/alive_monitoring
Physical.rcxprop
The file name is not case sensitive.
In the definition file, the items to set are entered on individual lines. Each line is entered in the following format.
Item_specified=Value_specified |
When adding comments, start the line with a number sign ("#").
Specify the the number of seconds of time-out for ping monitoring.
Enter an integer between 5 and 3,600. The unit is seconds.
"600" is specified as the default.
Specify recovery operations for when an error is detected.
Specify one of the following:
reboot (reboot)
force_reboot (forced reboot)
switchover (server switchover)
reboot_and_switchover (reboot and switchover)
force_reboot_and_switchover (forced reboot and switchover)
"reboot_and_switchover" is specified as the default.
When specifying "switchover" or "force_reboot_and_switchover" for recovery method, server redundancy need to be configured at Physical L-Server creation.
Specify the number of reboots for recovery operations.
Enter an integer between 1 and 3. The unit is seconds.
"1" is specified as the default.
Example
An example definition file is indicated below.
timeout = "600" |
Note
When applying the modified details to an already created L-Server, execute the rcxadm lserver modify command after changing the definition files.
