This section explains how to import a system configuration definition file (saved in CSV format) from the ROR console.
Use the following procedure to import a system configuration definition file.
Prepare a system configuration file in CSV format.
Point
System configuration templates in Excel format cannot be directly imported into Resource Orchestrator. Use the template's save to CSV function to produce a system configuration file in CSV format before importing.
Only system configuration files conforming to the format described in "B.2 File Format" can be imported. For details on the file format, refer to "Appendix B Format of CSV System Configuration Files".
Make sure that less than 200 resources are specified for registration or changing in the system configuration file.
If it is necessary to specify more than 200 resources for registration or changing, do by importing multiple system configuration files.
When importing system configuration files which begins with "RCXCSV,V1.0" in the first line, the agent cannot automatically be registered. Moreover, the registration fails in cases where a spare server is defined to a VM host in the system configuration file.
Open and log in to the ROR console according to "Chapter 2 Login and Logout" in the "User's Guide for Infrastructure Administrators CE".
In the ROR console, select [File]-[System Configuration File]-[Import] from the menu.
The [Import System Configuration File] dialog is displayed.
Specify a configuration file prepared in 1.
Click <OK>.
The import process starts. The system configuration file is verified first, and then resources are imported one by one, following the order defined by the system configuration file.
The processing of resource registration or change is executed after the verification.
The process status can be checked in the Recent Operations area of the ROR console.
Clicking <Cancel> in the Recent Operations area displays a confirmation dialog and stops the import process. The <Cancel> button interrupts the import process after completing the current process. Note that the processing performed up to the error point is effective in the system.
Point
The "SpareServer", "ServerAgent" and "ServerVMHost" sections must meet the conditions below when performing pre-configuration.
Spare server section ("SpareServer")
In cases where the specified spare server has no operating system installed
The physical server which is defined as a spare server must not be defined in "ServerWWNN", "ServerAgent", or "ServerVMHost" sections.
When configuring a server using I/O virtualization as a spare server
The server must meet one of the following conditions:
- HBA address rename information must already be configured on the physical server in which a spare server is defined
- A VIOM server profile must already be configured on the physical server in which a spare server is defined
In cases where the specified spare server is a VM host
The physical server which is defined as a spare server must already be registered for the Resource Orchestrator agent.
When configuring a server using WWN information coordinating with ESC as a spare server
WWN information must already be configured on the primary server and the spare server.
If the above conditions are not meet, divide the section as different CSV files, and import them one by one.
Agent section ("ServerAgent" or "ServerVMHost")
To register an agent, it must fulfill all of the following conditions. Please import agents only if they meet all these conditions.
The agent of Resource Orchestrator must already be installed on the managed server.
An OS must be running on the managed server.
The agent of the target physical server must be registered, or the agent registration section defined in the system configuration file.
In the "Server" section, when registering or changing managed servers in different subnets than the admin server, one of the following conditions must be fulfilled:
The target subnet information is registered.
The target subnet's information is defined in the "Subnet" section of the CSV format system configuration file.
Note
When registering a new server with the registered primary server, and configuring it as a spare server, import the "Server" section and "SpareServer" section separately.
When changing physical server names during pre-configuration, it cannot be performed at the same time as other pre-configuration operations. Import the "Server" section separately from other sections.
When the import is completed successfully, a message is displayed in the Recent Operations area.
Point
Error handling
The processing of resource registration or change is executed after the verification of the system configuration file during import.
If an error occurs during the verification process, which means an invalid value exists in the system configuration file, an error message is displayed only in the event log. Correct the system configuration file, and import it again.
Invalid content also includes invalid section headers.
If there is an error message displayed, but the values in the specified line are all correct, check whether the section header is correct or not.
If an error occurs during registration and change process, an error message is displayed in both the recent operations area and the event log. In this case, the process is finished up to the previous line setting, that is, before the system configuration file line number which message is displayed. Correct the system configuration file and rectify the problem, then import it again. The process will resume from the position where it stopped.
Import log file
The import log is saved in the following location on the manager.
In cases where an error occurs in the verification step, which means the processing of registration or changing the resource has not started yet, no log file is created.
[Windows Manager]
Installation_folder\SVROR\Manager\var\log\config.log
[Linux Manager]
/var/opt/FJSVrcvmr/log/config.log
Backing up the manager prior to import automatically
When importing is performed by a user, exporting is also automatically executed. The export file is saved as the backup of the manager configuration. Use this file to return to the previous values if there is an input error in the system configuration file.
Note that the backup can store the latest five versions.
The system configuration file backup can be stored in the following folder on the manager.
[Windows Manager]
Installation_folder\SVROR\Manager\var\config_backup
rcxconf-YYYYMMDDHHMMSS.csv (the date and time are shown in YYYYMMDDHHMMSS)
[Linux Manager]
/opt/FJSVrcvmr/var/config_backup
rcxconf-YYYYMMDDHHMMSS.csv (the date and time are shown in YYYYMMDDHHMMSS)
Perform post-setting operations.
If the import is completed successfully, perform the following procedures if required.
If HBA address rename is set, then restart the relevant managed server.
If the agent is registered, perform either one of the following to enable further backup or cloning operations.
Restart the managed server.
Restart the Related Service described in "2.2 Starting and Stopping the Agent" in the "Operation Guide CE".
