B.2 File Format

The system configuration files (CSV format) used for pre-configuration are comma (",") delimited.
The format of each line is given below:

File Format Definition
The first line of the file must begin with the following:
RCXCSV,V3.4
Point
Resource Orchestrator can import the following system configuration file formats.
- RCXCSV,V1.0
- RCXCSV,V2.0
- RCXCSV,V3.0
- RCXCSV,V3.1
- RCXCSV,V3.2
- RCXCSV,V3.3
- RCXCSV,V3.4
However, system definition files are always exported in the most recent format: importing a file in an older format and re-exporting it will produce a file in the latest format.
Note
Although each RCXCSV version has a different format, those formats are retro-compatible (newer formats include all the information defined in older formats).
As detailed below, some sections (described in "B.3 Resource Definitions") are only available with the latest format(s).
- RCXCSV V2.0 and Later
  "LanSwitchNet", "ServerAgent", "ServerVMHost", "PowerDevice", "Memo"
- RCXCSV V3.0 and Later
  "VMManager"
- RCXCSV V3.1
  "SPARCEnterprise"
- RCXCSV V3.2
  "PRIMERGYPartitionModelChassis", "PRIMERGYPartitionModelServer"
- RCXCSV V3.1
  "Subnet", "SPARCEnterprisePartitionModelChassis", "SPARCEnterprisePartitionModelServer", "MonitorSetting"
- RCXCSV V3.4
  "VIOManager"
Comments
The following lines are assumed to be comments and are skipped:
- Lines that begin with the symbol ("#")
  Example
  #Development environment definition
- Lines that consist of only blank spaces (" "), tab characters, or linefeed code
- Lines that contain only commas (",")
- Unrecognized resource definition
Resource Definitions
Create the resource definition using the following format. Describe the same type of resource in the same section.
- Resource Definition Format
  [Section name]
  Section Header
  Operation column, Parameter [,parameter]...
- Section Name
  This describes the resource type.
- Section Header
  This describes the parameter type unique to the resource.
  Note
  Do not enter any comments between the section name and section header.
- Operation Column
  This describes the operation type for the resource. The following characters can be used in the operation column.
  - new
    Register
  - change
    Modification
  - Hyphens, ("-")
    Do nothing
- Parameter
  This describes the parameter value to be set.
  Note
  The order of operation and parameter columns should follow the order defined in section header under "B.3 Resource Definitions".

Allowed Characters

For details on the characters allowed for each resource definition, refer to "B.3 Resource Definitions". Optional parameters can be omitted by using hyphens ("-").
However, hyphens ("-") are seen as valid characters for user names, passwords, and SNMP communities. Note that if extra commas (",") are added to the end of a line, those will be simply ignored without errors.

Backslashes ("\") and double quotations ( " ) will be displayed differently in the ROR console from how they appear in the system configuration file.
Refer to the following table for details on such differences.

Table B.1 Differences between System Configuration Files' Contents and Display in the ROR Console
Content of a System Configuration File (CSV)	Display in the ROR Console
\\	\
\n	Line break
""	"
, (*1)	,

*1: The whole value must be enclosed by double quotations ( " ).

Example

CSV Content
"a\nb,\\n"
Display in the ROR Console
A
b,\n

Order of Section Definition

Section order and section name are shown below.
Moreover, the section definition order is fixed.

Table B.2 Section Order and Section Names
Order	Section Name
1	Subnet
2	VIOManager
3	Chassis
4	PRIMERGYPartitionModelChassis
5	SPARCEnterprisePartitionModelChassis
6	LanSwitch
7	LanSwitchNet
8	Server
9	SPARCEnterprise
10	PRIMERGYPartitionModelServer
11	ServerNet
12	SPARCEnterprisePartitionModelServer
13	ServerWWNN (*1)
14	SpareServer (*1)
15	VMManager
16	ServerAgent (2, 3)
17	ServerVMHost (2, 3)
18	MonitorSetting
19	PowerDevice
20	Memo (*2)

*1: When loading from the system configuration template in the Excel format, the operation column information will be skipped.
*2: When loading from the system configuration template in the Excel format, the whole section will be skipped.
*3: Do not enter the information of the same physical server both in the "ServerAgent" and "ServerVMHost" section.

System backup information is automatically added to the end of the system configuration file when exporting in the CSV format. The sections after the line below contain the backup information. The backup information is skipped when loading from the system configuration template in the Excel format.

#Do not edit the following information, which is used to recover the manager.

Do not modify the backup information, as it is automatically created. Note that these sections do not have to be defined if the system configuration file is created for new system configuration.

Note

If a system configuration file (CSV format) is imported and then exported, the line order after export may differ from the line order before import.
The following information will also be deleted:
- Comments lines
- Strings enclosed in parenthesis "( )" indicating omitted values
- Extra commas at the end of lines (",")
As with chassis for server blades, and chassis for LAN switch blades, items that need to be registered in advance to enable registration of other should be defined in the system configuration file or registered in advance.

Character Code: The system configuration files (CSV format) used for pre-configuration are saved using ASCII (often referred to as "ANSI" in Windows systems). When files that use a character code other than ASCII are imported, the system may not operate correctly.
When directly editing configuration files using a text editor, please do not save the file using a character code other than ASCII.