Configuring the iRMC via SCCI and scripted configuration
12.2.1.2 SCCI file format
I
The format of the XML configuration file (.pre) used is taken from the setup configuration help file that is installed together with the ServerView agents on Windows platforms. A copy of this description with iRMC S4specific notes is shown below.
The configuration file is a based on XML syntax:
– Each configuration setting consists of a simple XML fragment starting with a "<CMD>" tag.
– The complete sequence of configuration settings is enclosed in a pair of tags
"<CMDSEQ> and </CMDSEQ>".
The following is an example of a typical command sequence comprising two configuration settings:
<CMDSEQ>
<CMD Context="SCCI" OC="ConfigSpace" OE="3800" OI="0"
Type="SET">
<DATA Type="xsd::hexBinary" Len="1">04</DATA>
<CMD Context="SCCI" OC="ConfigSpace" OE="3801" OI="0"
Type="SET">
<DATA Type="xsd::hexBinary" Len="1">00</DATA> </CMD>
</CMDSEQ>
The Context parameter is used internally to select the provider of the operation.
Currently, SCCI is the only supported provider.
454
iRMC
Configuring the iRMC via SCCI and scripted configuration
Parameters of SCCI provider-specific commands
The following SCCI-provider-specific commands are available:
Operation Code (OC)
Hex value or string specifying the command / operation code.
I
The iRMC only supports a limited set of SCCI commands. For a list of supported commands see
table "SCCI commands supported by the iRMC" on page 460
Operation Code Extension (OE)
Hex value for extended operation code. Default: OE=0
For ConfigSpace Read-/Write operations, this value defines the
ConfigSpace ID.
Object Index (OI)
Hex value selecting an instance of an object. Default:OI=0"
Operation Code Type (Type)
For configuration settings, the values GET (read operation) and SET (write operation) are supported. Default: Type=GET
I
SET operations require data. For specifying the appropriate data type, use the Data (DATA) parameter described below.
Cabinet Identifier (CA)
Allows you to select an extension cabinet and use its cabinet ID number.
I
Do not use this parameter to request for the system cabinet!
Data (DATA)
If a SET parameter (write operation) is specified: Data type (Type parameter), and, in some cases, data length (LEN parameter) are required.
Currently, the following data types are supported:
– xsd::integer
Integer value
Example
<DATA Type="xsd::integer">1234</DATA> iRMC S4
455
Configuring the iRMC via SCCI and scripted configuration
– xsd::hexBinary
Stream of bytes. Each byte is coded in two ASCII characters. Use the
Len
parameter as shown in the example below to specify the length of the stream (i.e. the number of bytes).
I
The data type xsd::hexBinary can be used without any restriction. The number of bytes used is determined by the Len parameter.
Example
A stream of four bytes 0x00 0x01 0x02 0x04 will be coded as the following ASCII stream:
<DATA Type="xsd::hexBinary" Len="4">0001020304</DATA>
– xsd::string
Normally used for the transfer of strings. Additionally, the string type can be used for IPv4 addresses and MD5-based user passwords. In this case, the string data is internally converted to the accepted target format.
Transferring encrypted data
A Fujitsu-proprietary data encryption is supported for some sensitive data such as user or service (LDAP/SMTP) access passwords, or the
AVR license key of the iRMC. You can use the iRMC_PWD.exe
program for encrypting password data (see section "Generating encrypted passwords with iRMC_PWD.exe" on page 464
).
Encrypted="1" must be set in the <DATA> tag to indicate that the data to be written is encrypted.
Examples
Transferring the string "Hello World":
<DATA Type="xsd::string">Hello World</DATA>
Transferring a password as clear (readable) text:
<DATA Type="xsd::string">My Readable Password</DATA>
Transferring an encrypted password:
<DATA Type="xsd::string"
Encrypted="1">TpVlTJwCyHEIsC8tk24ci83JuR9l</DATA>
456
iRMC
Configuring the iRMC via SCCI and scripted configuration
Transferring the IPv4 address "192.23.2.4"
<DATA Type="xsd::string">192.23.2.4</DATA>
V
CAUTION!
The xsd::string data type is restricted to readable strings, IP addresses and MD5-based user passwords.
For all other data, the xsd::hexbinary data type must be used!
I
Do not directly specify the characters ä, ö, ü, etc. in strings
unless they are actually needed by the using application!
Both SCCI and the ConfigSpace interface do not store any character encoding information. Thus, any non-US-ASCIIcharacters will be interpreted internally by the using application and therefore should be avoided.
If you do actually need to specify special characters, make sure that you edit and save your file in UTF-8 format including the correct BOM.
Command Status (Status)
After the configuration settings are transferred, the Status contains the result of the operation. If the operation has completed successfully, the value 0 is returned.
I
For a specification of all public configuration settings (ConfigSpace) see the SCCI_CS.pdf file, which is distributed with the PRIMERGY Scripting
Toolkit.
iRMC S4
457
