User's Manual

Preparing the Script Files for Deployment Using Microsoft Windows PE 63
The raccfg.ini file is generated with the RACCAP.BAT sample script.
See "RACCAP.BAT" on page 66 for information about using the
RACCAP.BAT sample script to capture RAC configuration information.
RAIDCFG.BAT
The RAIDCFG.BAT sample script configures RAID controllers detected on
the system. User input is optional to run this script. The parameter is a name
or path to a log file. This parameter is not set to any value by default, and no
log file is generated. The default variable values used in this script are set in
the TKENVSET.BAT scripts. This script uses the RAIDCFG.EXE utility to
automatically configure the detected controllers on your target system. For
example, for the first controller discovered, if RAIDCFG.EXE discovers only
one attached hard drive, the script tries to create RAID 0; if two hard drives
are discovered, a RAID 1 configuration is enabled; if three or more hard drives
are discovered, a RAID 5 configuration is enabled.
NOTE: On the detected controller, a RAID virtual disk is created only if the array
disks connected to that particular controller have space available and, where
applicable, are not part of already existing array group.
SYSREP.BAT
The SYSREP.BAT sample script applies SYSCFG options to the target
system based on configuration information that has been saved in a
configuration file. User input is optional to run this script, depending on the
variable settings in the SYSREP.BAT scripts. This script uses the
SYSCFG.EXE utility to configure the BIOS and BMC in the target system
using the configuration file, syscfg.ini, passed as the first parameter to this
script. If this parameter is not passed, the default variables values used in this
script are set in the SYSREP.BAT scripts. The syscfg.ini file is generated with
the SYSCAP.BAT sample script. See "SYSCAP.BAT" on page 64 for
information about using the SYSCAP.BAT sample script to capture BIOS and
BMC settings. The second parameter is a name or path to a log file.
This parameter is not set to any value by default, and no log file is generated.
NOTE: If the replication requires a change in the memory redundancy mode,
the target server should be rebooted and the script should be executed again
to complete the replication.