This section explains how to import a system configuration definition file (saved in CSV format) from the RC 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 Coordinator VE. 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 "D.2 File Format" can be imported. For details on the file format, refer to "Appendix D Format of CSV 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.
For details on upgrading from Systemwalker Resource Coordinator Virtual server Edition V13.2, refer to "Chapter 4 Upgrading from Earlier Versions" in the "ServerView Resource Coordinator VE Installation Guide".
Open and log in to the RC console according to the instructions given in "5.3 RC Console".
In the RC console, select [File]-[Import] from the menu.
The [Import system configuration file] dialog is displayed.
Specify the system configuration file prepared in step 1, then click <OK>. The import process will start. The system configuration file is verified first, 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 is displayed in the Recent Operations area of the RC 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 processing. 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 case that 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.
In cases where the specified server is a VM host.
The physical server which is defined as a spare server must already be registered for the Resource Coordinator VE agent.
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 the Resource Coordinator VE must already be installed in the managed server.
An operating system must be running on the managed server.
The agent of the target physical server must be registered, or the agent registration section is defined in the system configuration file.
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.
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]
Installation_folder\Manager\var\log\config.log
[Linux]
/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 generations.
The system configuration file backup can be stored in the following location.
[Windows]
Installation_folder\Manager\var\config_backup
rcxconf-YYYYMMDDHHMMSS.csv (the date and time are shown in YYYYMMDDHHMMSS)
[Linux]
/opt/FJSVrcvmr/var/config_backup
rcxconf-YYYYMMDDHHMMSS.csv (the date and time are shown in YYYYMMDDHHMMSS)
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 "Deployment service" described in "5.2 Agent".
