Users Guide

script. On systems running Windows, RACREP.BAT script uses RACADM.EXE to congure RAC in the target system. On systems

running Linux the racrep.sh script uses racadm wrapper script or the syscfg utility (depending on the version of RAC on your

system) to congure RAC in the target system. The raccfg.ini is passed as the rst parameter to these scripts. If this parameter is

not passed, the default variables values used in these scripts are set in the TKENVSET.BAT or tkenvet.sh scripts. You can specify the

IP address to congure the RAC as an optional parameter. The raccfg.ini le is generated with the RACCAP.BAT or raccap.sh sample

script. For information about using the RACCAP.BATor raccap.sh sample script to capture RAC conguration information, see

RACCAP.BAT Or raccap.sh.

NOTE: On all PowerEdge systems, racrep.sh and sysrep.sh have duplicate functions. If you run racrep.sh followed by

sysrep.sh, the latter overwrites the settings of the former.

RAIDCFG.BAT or raidcfg.sh

The RAIDCFG.BAT or raidcfg.sh sample script congures RAID controllers detected on the system. User input is optional to run this

script. The input parameter is a name or path to a log le. This parameter is not set to any value by default, and no log le is

generated. The default variable values used in this script are set in the TKENVSET.BAT or tkenvest.sh scripts. This script uses the

RAIDCFG.EXE or raidcfg.sh utility to automatically congure the detected controllers on your target system. For example, for the

rst controller discovered, if RAIDCFG.EXE or raidcfg.sh discovers only one attached hard drive, the script tries to create RAID 0; if

two hard drives are discovered, a RAID 1 conguration is enabled; if three or more hard drives are discovered, a RAID 5 conguration

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 existing array group.

SYSREP.BAT or sysrep.sh

The SYSREP.BAT or sysrep.sh sample script applies SYSCFG options to the target system based on conguration information that

has been saved in a conguration le. User input is optional to run this script, depending on the variable settings in the SYSREP.BAT

or sysrep.sh scripts. This script uses the SYSCFG utility to congure the BIOS and BMC in the target system using the conguration

le syscfg.in. The syscfg.in is the rst parameter passed to this script. If this parameter is not passed, the default variables values

used in this script are set in the SYSREP.BAT or sysrep.sh scripts. The syscfg.ini le is generated with the SYSCAP.BAT or syscap.sh

sample script. For information about using the SYSCAP.BAT or syscap.sh sample script to capture BIOS and BMC settings, see

SYSCAP.BAT Or syscap.sh. The second parameter is a name or path to a log le. This parameter is not set to any value by default,

and no log le is generated.

NOTE: If the replication requires a change in the memory redundancy mode, reboot the target server and run the script

again to complete the replication.

NOTE: The racrep.sh and sysrep.sh have duplicate functions. If you run racrep.sh after the command sysrep.sh, the latter

overwrites the former settings.

PARTCFG.BAT or partcfg.sh

In BIOS mode, the PARTCFG.BAT or partcfg.sh sample script creates and populates the Dell utility partition using UPINIT.BAT or

upinit.sh and creates the deployment partition on a specied disk. In UEFI mode, the partcfg.sh sample script creates the

deployment partition on a specied disk. For more information about using the UPINIT.BAT or upinit.sh tool, see UPINIT.BAT Or

upinit.sh. User input is not required to run this script. The default variable values used in this script are set in the TKENVSET.BAT or

tkenvset.sh scripts.

NOTE: Ensure that DT_HD is set to the required disk to be congured before you execute the PARTCFG.BAT or

partcfg.sh script.