Using the Pre-configuration function, it is possible to create system definition files that can be later used to setup a Resource Orchestrator environment. Importing system configuration files makes it easy to perform various registration settings in one operation. This prevents the operating mistakes induced by sequences of individual, manual configuration steps.
The pre-configuration function can be used in the following situations.
New Installation
From a traditional work office (or another off-site location), define the various parameters required for Resource Orchestrator and record them in a system configuration file. Next, send this definition file to your actual system location (machine room), and import the file into Resource Orchestrator using the import functionality of the ROR console. This single operation automates the registration of all the servers defined in the system configuration file.
Backing up a System Configuration
Using the export function of the ROR console, the current Resource Orchestrator configuration can be exported to a system configuration file.
Batch Re-configuration
The registration settings of already registered resources can be modified easily by exporting the current configuration to a system configuration file and editing the desired configuration items before re-importing that configuration file. The actual re-configuration is then performed as a single import operation.
Re-use of Existing Configurations
Once a system has been fully setup, its configuration can be exported and re-used as a basis for the design of other systems. This makes it easy to design various systems located in different sites.
Figure 10.1 Examples of Use
Only system configuration files in CSV format can be imported or exported. For details on the system configuration file's format, refer to "Appendix B Format of CSV System Configuration Files".
Resource Orchestrator provides a sample in CSV format. To obtain a copy of the Excel template (hereafter system configuration template), please contact Fujitsu technical staff. This system configuration template makes it easy to create system configuration files in CSV format.
When loading a system configuration template from a CSV file, or importing a system configuration file from the ROR console
Use the format described in "B.2 File Format" for the system configuration file.
When saving a file in CSV format from the system configuration template, or exporting a system configuration file from the ROR console
Export will be performed using the latest file format given in "B.2 File Format".
The following operations, usually performed from the ROR console, can be equally performed using the pre-configuration function.
Registration
"Chapter 8 Configuring Monitoring Information" in the "Setup Guide VE"
"Chapter 18 Server Switchover Settings" in the "User's Guide VE"
Modification
"7.1.5 Changing Server Management Unit Configuration Settings"
"18.3 Changing Server Switchover Settings" of the "User's Guide VE"
*1: To start collecting environment data, the collection settings should be manually set from the ROR console's option dialog.
*2: Restart all the managed servers that were either registered or modified following an import operation.
*3: The pre-configuration's scope of configuration is the same as that of the ROR console.
Moreover, the pre-configuration function can perform the same labels and comments settings as those available in BladeViewer. Those settings are described in "Chapter 4 BladeViewer" and "4.5.1 Listing and Editing of Labels and Comments".
Note
The following operations cannot be performed by the pre-configuration function, and should be performed from the ROR console.
Deleting registered resources from Resource Orchestrator
Changing the name of a registered chassis, physical server (only for servers other than PRIMERGY BX servers) or a power monitoring device
Deleting registered admin LAN subnets
Discovering, registering, or changing registration settings of a LAN switch
Detecting physical link information from a LAN switch
Canceling VIOM Integration
Registration and deletion of SNMP trap destinations
Configuration and change of WWN information using ETERNUS SF Storage Cruiser integration
The following operations cannot be performed by the pre-configuration function, and should be performed using commands.
Registration and deletion of ETERNUS SF Storage Cruiser integration
Make sure that less than 200 resources are specified for registration or changing in the system configuration file specified for import.
If it is necessary to specify more than 200 resources for registration or changing, do by importing multiple system configuration files.
When using ServerView Deployment Manager on the admin LAN, the following settings cannot be defined using the pre-configuration function. For details on co-existence with ServerView Deployment Manager, refer to "Appendix B Co-Existence with ServerView Deployment Manager" in the "Setup Guide VE".
Spare server settings (using the backup and restore or HBA address rename method)
HBA address rename Settings
