Dell OpenManage Deployment Toolkit Version 4.
Notes and Cautions NOTE: A NOTE indicates important information that helps you make better use of your computer. CAUTION: A CAUTION indicates potential damage to hardware or loss of data if instructions are not followed. ____________________ Information in this publication is subject to change without notice. © 2012 Dell Inc. All rights reserved. Reproduction of these materials in any manner whatsoever without the written permission of Dell Inc. is strictly forbidden.
Contents 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . What’s New in This Release . . . . . . . . . . . . . . . Other Documents You May Need . . . . . . . . . . . . Other Supporting Documents You May Need . Contacting Dell 2 9 9 10 . . . . . 12 . . . . . . . . . . . . . . . . . . . . . 12 Prerequisites and Deployment Supported Systems . . . . . . . . 13 . . . . . . . . . . . . . . . . . . . 13 Supported Operating Systems . . . . . . . . . . . . . . 14 . . . . . . . . .
Deploying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 . . . . . . . . . . . . . . . . . 25 Configuring a Source System RAC Configuration How to Obtain Dell Utility Partition Files 3 . . . . . . 26 . . . . . . . . . . . . . . . . . . 27 . . . . . . . . . . . . . . . . . . . . . . 27 Downloading DTK For Windows . . . . . . . . . . . . . . . . . . . . 30 . . . . . . . . . . . . . . . . . . . . . .
Editing Example of TKENVSET.BAT and tkenvset.sh . . . . . . . . . . . . . . . Editing DTK Task Scripts . . . . . . 64 . . . . . . . . . . . . . . 70 Using DTK Sample Scripts to Capture Configuration Information . . . . . . . . . . . . . . . . Capturing the System BIOS and BMC Configuration With the SYSCAP.BAT or syscap.sh Sample Script . . . . . . . . . . . . . . Capturing the RAC Configuration With the RACCAP.BAT or raccap.sh Sample Script Preparing the Operating System Installation Scripts . . .
Network-Based Deployment (Remote) for Windows . . . . . . . . . . . . . . . . . . . . . . . Using a Third-Party Deployment Solution Framework for Windows . . . . . . . . . . . . . . . . Deployment Using Dell-Provided Embedded Linux . 89 . . . . . . . . . . . . 90 . . . . . . . . . . . . . 91 Deployment Using Customized Embedded Linux Using a Third-Party Deployment Solution Framework for Linux . . . . . . . . . . . 7 . . . . 93 . . . . . . . 94 Running Dell Update Packages in Embedded Linux .
Windows PE Questions Index 105 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents
1 Introduction The Dell OpenManage Deployment Toolkit (DTK) includes a set of utilities, sample scripts, and sample configuration files that you need to deploy and configure the Dell system. You can use DTK to build script-based and RPMbased installation for deploying large number of systems on a pre-operating system environment in a reliable way, without changing their current deployment processes.
• RAIDCFG extends support to Dell PERC 8 controllers (H310, H710, H710P, and H810) and software RAID S110 controller. • Support for configuring iDRAC7 through RACADM. NOTE: For more information on new SYSCFG features, see Dell OpenManage Deployment Toolkit Command Line Interface Reference Guide available at support.dell.com Other Documents You May Need In addition to this guide, you can access the following guides available at support.dell.com/manuals.
• The Dell Systems Build and Update Utility Quick Reference Guide is an introduction to the Dell Systems Build and Update Utility, and provides tips on how to make the product effective in helping you streamline your deployment and update procedures for Dell systems. • The Dell Remote Access Controller 5 User's Guide provides comprehensive information about using the RACADM command line utility to configure a DRAC 5.
Other Supporting Documents You May Need Besides the Dell-provided documentation, there are numerous other resources to aid you in planning and executing a DTK-assisted deployment: • Operating system documentation to prepare for and execute the unattended installation process. In addition, you should consult the available Web-based resources such as: – The Microsoft Tech Net database at microsoft.com/technet – The Red Hat Enterprise Linux support pages at redhat.
Prerequisites and Deployment 2 DTK is a collection of Windows PE and Linux-based utilities and scripts that assist in performing pre-operating system tasks and deployment on Dell systems. An advanced knowledge of Windows PE and Linux is required for Users who want to use the DTK utilities to perform pre-operating system configuration tasks or to run a scripted deployment in the respective environments, require an advanced knowledge of Windows PE and Linux..
Supported Operating Systems For Windows, DTK utilities support Windows PE 2.0 (32-bit and 64-bit) and Windows PE 3.0 (32-bit and 64-bit). Using DTK utilities we can deploy the following Windows operating systems: • Windows Server 2008 SP2 (32-bit and 64-bit) • Windows Server 2008 R2 SP1 For Linux, DTK utilities support Red Hat Enterprise Linux Server version 5.5, update 4 (32-bit). Using DTK utilities we can deploy the following Linux operating systems: • Red Hat Enterprise Linux 6.
Before installing DTK components for embedded Linux, make sure that you have the following: • The DTK ISO image, which contains the utilities, sample scripts, sample configuration files, RPMs, and documentation you need to deploy your Dell system. • A Linux workstation that has at least 200 MB of free hard-drive space.
For embedded Linux, make sure that you have all of the following tools, software, and information ready to use or consult: • Advanced knowledge of Linux and Linux scripting (bash), Linux networking, installing and working with RPM Package Managers (RPMs), and creating and modifying loop file systems. • Any third party deployment system or tool.
Table 2-1. Drivers Drivers Purpose common\hapi Essential drivers for DTK tools to work. common\raidcfg Essential drivers for raidcfg to work. winpe2.x\chipset Essential chipset drivers. winpe2.x\massstorage Essential drivers for mass storage controllers to work. winpe2.x\nic Recommended drivers for NICs. winpe2.x\buildwim Used to create the ISO image using Windows AIK. winpe2.
Table 2-2. Supporting Tools and System Files for Windows (continued) Additional Tools Purpose Source upimg.bin Contains system-specific Dell utility partition files. \Toolkit\Systems at support.dell.com, or the Dell Systems Build and Update Utility on the Dell NOTE: In the previous releases, each Dell system required a unique upimg.bin file. Starting DTK 2.3, the upimg.bin file is common for all Dell systems.
Table 2-3. Supporting Tools and System Files for Linux (continued) Additional Tools Purpose initial ramdisk Used during a Linux unattended installation. Source Save in DTK location Available on the Linux /opt/dell operating system media /toolkit NOTE: For legacy operating or on the Systems Build /systems and Update Utility on systems, you may need to the Dell Systems load the driver disk. At the Management Tools and end of the Red Hat Enterprise Linux Server installation, you Documentation DVD.
Deployment Dell systems can be deployed using several methods. The most common method is using the Systems Build and Update Utility (SBUU) on the Dell Systems Management Tools and Documentation DVD that is shipped with your system. Currently, this method is used to deploy a single system at a time with the installation wizard. DTK, on the other hand, offers a complete set of utilities, sample scripts, and RPM packages that can be used to automate deployment on large numbers of Dell systems.
Table 2-4. Deployment Method Matrix Deployment Methods Complexity Local deployment Relatively (bootable media) simple Advantages Disadvantages • Necessary if a network connection is not available or is too slow. • Any change requires the creation of a new bootable media. • Limited space on media for some operating system installation files. • Can install supported • Deployment tasks must Windows be performed at the operating systems. individual target system.
Table 2-4. Deployment Method Matrix (continued) Deployment Methods Complexity Deployment Mixed solution framework from a third-party vendor Advantages Disadvantages • The DTK can be used in the context of thirdparty deployment solution framework. Must either acquire and learn to use or have an existing third-party deployment solution framework. • Third-party deployment solution framework is used as the deployment transport mechanism. • Tasks and scripts can be pushed to the target systems.
After you have determined which deployment method best suits the needs of your organization, you are ready to begin building the DTK deployment directory structure on a network volume. For instructions on installing the DTK components and populating the deployment directory structure, see "Preparing the Script Files" on page 51. DTK Deployment Overview The deployment process can be separated into two main tasks: preparation and the actual deployment.
4 Generate a system BIOS, BMC, RAID, and/or RAC configuration profile from the optimally configured source system. Copy the generated configuration files to a read/write share onto the workstation. NOTE: You can obtain the system BIOS, BMC, RAID, and/or RAC configuration files by booting for Windows from DTK Windows PE ISO image and running the SYSCAP.BAT, RAIDCAP.BAT, and RACCAP.BAT scripts. For Linux, you can obtain the configuration from DTK Linux ISO image and running the syscap.sh, raidcap.
You can use the Systems Build and Update Utility and Systems Service and Diagnostics Tools available on the Dell Systems Management Tools and Documentation DVD supplied with your system to: • Streamline the operating system installation. • Setup and configure your system, including automatic discovery and configuration of Dell-provided RAID controllers and network adapters. • Access and load the latest utilities, drivers, and diagnostics for your system.
How to Obtain Dell Utility Partition Files Obtain the Dell utility partition files from /opt/dell/toolkit/systems at support.dell.com, or the Systems Build and Update Utility on the Dell Systems Management Tools and Documentation DVD.
3 Downloading DTK This section describes some of the procedures necessary to begin the deployment process, including: • Downloading and unzipping the Deployment Toolkit (DTK) components, including a comprehensive matrix of DTK components. • Setting up a directory structure to facilitate a successful deployment, including a list of the supporting components that are not included with DTK, but are needed to use DTK. • Setting up an optimally configured source system.
4 Click Unzip. By default, files are unzipped to C:\. You can unzip the DTK components to your local hard drive and then copy them later to a network volume, or you can change the installation path to an available network share. For example, you can unzip the files directly to the network share (for example, Z:\) that you plan to use in the deployment process. NOTE: Do not copy the DTK components to a Novell NetWare network volume.
Figure 3-1. Sample DTK Default File Structure Workstation is the system on which the DTK components are extracted. Source system is an optimally configured system from which the system settings are captured. Target system is the system on which the settings captured from the source system are replicated.
DTK utilities for 32-bit systems are located in the following directories: • Utilities: \Dell\x32\Toolkit\Tools • Sample scripts: \Dell\x32\Toolkit\Template\Scripts • Sample configuration files: \Dell\x32\Toolkit\Template\Configs DTK utilities for 64-bit systems are located in the following directories: • Utilities: \Dell\x64\Toolkit\Tools • Sample scripts: \Dell\x64\Toolkit\Template\Scripts • Sample configuration files: \Dell\x64\Toolkit\Template\Configs The directory \Dell\x32\Toolkit\Systems
Figure 3-2. Media Directory Structure Table 3-1 describes the files, components, and other contents of the mounted media. Table 3-1. Mounted Media Contents Contents Details Location dchipm32.ini Configuration file for the instrumentation software. /opt/dell/toolkit/lib/b in docs Contains Quick Installation Guide. /mnt/cdrom/docs LICENSING Contains all the licenses for the open /mnt/cdrom/ source components used in this media. LICENSING README Provides the latest product information.
Table 3-1. Mounted Media Contents (continued) Contents Details Location RPMs Contains DTK RPMs and dependency /mnt/cdrom/RPMs RPMs start-stage3.sh The startup script used by the toolkit ISO image to boot. /mnt/cdrom/tools start-hapi.sh The startup script to load and configure the HAPI drivers. /mnt/cdrom/tools start-raid.sh Contains the basic setup for raidcfg to /mnt/cdrom/tools work. Boot the media on to a target system. Figure 3-3 shows the directory structure on the target system.
Table 3-2 describes the contents of the directory structure on the target system. Table 3-2. Target System Directory Structure Contents Contents Details /lib The libraries and drivers required for embedded Linux to function. /bin Basic utilities (ls, chmod, and so on) /sbin Utilities that are required by the system superuser to perform administrative tasks. /opt The libraries, binaries, and scripts required for the toolkit to function, which are available at: /mnt/cdrom/tools/dell.tar.gz.
System Utilities and Supporting Files Table 3-3 describes the files located in Toolkit\Tools on systems running the Windows operating system and Table 3-4 describes the files, located at /opt/dell/toolkit/bin and the supporting libraries located in /opt/dell/toolkit/lib on systems running the Linux operating system. These are the core tools (utilities) that perform pre-operating system configuration and deployment tasks.
Table 3-3. System Utilities and Supporting Files for Windows (continued) Toolkit Components Purpose IDRAC Configures iDRAC6. NOTE: This feature may not be supported on all systems. IDRAC7 Configures iDRAC7. NOTE: This feature may not be supported on all systems. RAC 4 Configures Dell Remote Access Controller (DRAC) 4/P and DRAC 4/I. RAC 5 Configures DRAC 5/iDRAC. pci.ids Reports PCI devices when used with syscfg.exe. disclaimer.txt Displays the disclaimer for the tools. racadmErrorCodes.
Table 3-4. System Utilities and Supporting Files for Linux (continued) Toolkit Components Purpose raidcfg Creates and reports RAID information. RaidcfgErrorCodes.txt Lists the error codes and messages for the raidcfg tool. stsvc.ini Configuration file used by raidcfg. syscfg • Reports and configures: – Basic Input/Output System (BIOS) settings and options – Baseboard Management Controller (BMC) settings and options – DRAC • Maintains system state between reboots.
Table 3-5. Sample Configuration Files for Windows Toolkit Components Purpose Location raccfg.ini Sample configuration file Move to the directory for DRAC 4 remote access \Toolkit\Systems\. controllers. raidcfg.ini Sample output file to enable RAID replication. Move to the directory \Toolkit\Systems\. syscfg.ini Sample configuration file for SYSCFG utility to configure the BIOS and BMC settings. Move to the directory \Toolkit\Systems\. winbom.
Table 3-6. Sample Configuration Files for Linux (continued) Toolkit Components Purpose ks-rhel5.cfg Sample file used with unattended installation of Red Hat Enterprise Linux Server (version 5) operating system. ks-rhel6.cfg Sample file used with unattended installation of Red Hat Enterprise Linux Server (version 6) operating system. raccfg.ini Sample configuration file for DRAC 4 RACs. raidcfg.ini Sample output file to enable RAID replication. syscfg.
Table 3-7. Sample Scripts for Windows (continued) Toolkit Components Purpose PARTCFG.BAT Creates and populates the Dell utility partition and creates the operating system partition on a specified hard drive. Before doing so, however, this script cleans out all existing partitions in your system. RACCAP.BAT Captures Remote Access Controller (RAC) settings to a file for DRAC 4 remote access controllers. RACREP.BAT Applies (replicates) the RAC settings saved in a file to the target system. RAIDCAP.
Table 3-8. Sample Scripts for Linux (continued) Toolkit Components Purpose racrep.sh Applies (replicates) the RAC settings saved in a file to the target system. raidcfg.sh Configures all RAID controllers detected in a system. suseinst.sh Performs an unattended installation of a supported SUSE Linux Enterprise Server operating system. syscap.sh Captures BIOS and BMC configuration settings and saves them to a file. sysdrmk Used by upinit.sh to patch the boot sector. sysrep.
Documentation Table 3-10 describes documents containing reference information for each DTK utility and instructions for using DTK utilities and sample scripts. On systems running the Windows operating system, documentation is available at \Dell\Docs. On systems running the Linux operating system, documentation is available at mnt/cdrom/docs. Table 3-10.
Downloading DTK
4 Setting Up a Directory Structure for Deployment To perform a DTK-enabled deployment, you must create a deployment directory structure on either a network share or your local workstation hard drive. The deployment directory structure is a central repository for all deployment files and can be used successively as a testing space, a repository for a network deployment, and a repository to build a bootable deployment media.
DTK Utilities and Files All necessary DTK files are provided as part of the initial installation. It is strongly suggested that you use the default directory structure created in the initial installation of DTK components. The sample scripts provided with DTK are set up to use these default paths. See Figure 4-1 for Windows operating system.
Figure 4-1.
Operating System Installation Files The operating system file structure for Windows Server 2008 is shown in Figure 4-2. Figure 4-2. Sample Operating System-Specific File Structure (Windows Server 2008) Creating Operating System Installation Directories for Windows Server 2008 Operating Systems NOTE: The following procedures are provided as best practice guidelines for creating operating system distribution folders compatible with DTK sample scripts.
To deploy on Windows Server 2008 operating systems: 1 Create an operating system-specific directory in the root directory of the network share. For example, W2K8_deploy. 2 Create two directories under the W2K8_deploy directory: sources and , for example, PE2950. Copy the contents of the operating system media to sources. NOTE: The platform name must be a DTK standard name. To know the platform name, run TKENVSET.
Creating Operating System Installation Directories for Supported Linux Operating Systems NOTE: The following procedures are provided as a best practices guideline for creating operating system distribution folders compatible with DTK sample scripts. For complete instructions on setting up an installation directory structure for an unattended installation, see your operating system documentation.
Figure 4-3.
Setting Up a Directory Structure for Deployment
Preparing the Script Files 5 This chapter describes the steps required to use the Deployment Toolkit (DTK) sample scripts to perform a full deployment on a target system in the Microsoft Windows PE and embedded Linux environment.
:: ***************************************************** ***************************************************** :: Replicate the system settings to the current SUT!. CALL SYSREP.BAT or DTKRUNALL.BAT. :: ***************************************************** ***************************************************** ::Partitioning the system hard disk. call PARTCFG.BAT.
You can edit and customize the sample scripts provided with DTK using any ASCII text editor that conforms to the hardware available on the target systems. While it is recommended that you use DTK sample scripts to automate your deployment tasks, you can create your own system deployment batch files using any ASCII text editor by incorporating the various DTK utilities and commands in the batch file.
Scripts for Deployment Table 5-1, lists the scripts you may need for deployment. Table 5-1. Capture Scripts for Windows Script Name Description Associated Files RACCAP.BAT Captures RAC settings • TKENVSET.BAT — Used by RACCAP.BAT to inform the to a file for DRAC 4. task scripts where to find the DTK utilities, scripts, and configuration files. • RACADM.EXE — Used by RACCAP.BAT to retrieve RAC information and to configure settings. SYSCAP.BAT Captures BIOS and • TKENVSET.BAT — Used by SYSCAP.
Table 5-2. Capture Scripts for Linux Script Name Description Associated Files raccap.sh Captures RAC settings • tkenvset.sh — Used by raccap.sh to inform the task to a file for Dell scripts where to find the DTK Remote Access Conutilities, scripts, and troller (DRAC) 4. configuration files. • racadm — Used by raccap.sh to retrieve RAC information and to configure settings. The wrapper script, racadm, calls racadm4, racadm5, or racadm6 depending on the system configuration. • syscfg — Used by raccap.
Table 5-3. Replication Scripts for Windows Script Name Description Associated Files RACREP.BAT Applies the RAC configuration settings saved in a file to the current system. • TKENVSET.BAT — Used by RACREP.BAT to inform the task scripts where to find the DTK utilities, scripts, and configuration files. • RACADM.EXE — Used by RACREP.BAT to replicate RAC information and to configure settings. RAIDREP.BAT Applies the RAID • RAIDCFG.EXE — Used by RAIDREP.
Table 5-4. Replication Scripts for Linux Script Name Description Associated Files racrep.sh Applies the RAC configuration settings saved in a file to the current system. • tkenvset.sh — Used by racrep.sh to inform the task scripts where to find the DTK utilities, scripts, and configuration files. • racadm — Used by racrep.sh to replicate RAC information and to configure settings. The racadm is a wrapper script which calls racadm4, racadm5, or racadm6 depending on the system configuration.
Table 5-5. Deployment Scripts for Windows Script Name Description Associated Files W2K8INST.BAT • TKENVSET.BAT — Used by Performs an W2K8INST.BAT to inform unattended installation the task scripts where to find of supported Windows the DTK utilities, scripts, and Server 2008 operating configuration files. systems. • SETUP.EXE — Used by W2K8INST.BAT to install the operating system in conjunction with the UNATTEND.XML answer file. • UNATTEND.XML — Used by W2K8INST.BAT in conjunction with SETUP.
Table 5-6. Deployment Scripts for Linux Script Name Description Associated Files lininst.sh • tkenvset.sh — Used by Performs an unatlininst.sh to inform the task tended installation of a scripts where to find the DTK supported Red Hat utilities, scripts, and Enterprise Linux configuration files. Server operating system. • grub — Used to install the operating system in conjunction with the unattended answer file.
Table 5-6. Deployment Scripts for Linux (continued) Script Name Description Associated Files suseinst.sh Performs an unat• tkenvset.sh — Used by suseinst.sh to inform the task tended installation of a scripts where to find the DTK supported SUSE Linux utilities, scripts, and Enterprise Server operating system. configuration files. • grub — Used to install the operating system in conjunction with the unattended answer file.
Table 5-7. Other Scripts for Windows Script Name Description Associated Files TKENVSET.BAT • SYSCFG.EXE — Used by Sets the path of DTK TKENVSET.BAT to discover installation and the system type. variables for the system to be deployed and configured. The variables and paths specified in this file must be specified before any of the other supporting scripts can be used. RAIDCFG.BAT Configures the selected • TKENVSET.BAT — Used by RAIDCFG.
Table 5-7. Other Scripts for Windows (continued) Script Name Description Associated Files PARTCFG.BAT Creates and populates • TKENVSET.BAT — Used by PARTCFG.BAT to inform the the Dell utility task scripts where to find the partition (UP) and the DTK utilities, scripts, and operating system partition on a specified configuration files. disk. • DISKPART.EXE — Provided by Windows; this script is used to create partitions on your disk. When creating a Windows PE image, make sure that DISKPART.
Table 5-8. Other Scripts for Linux (continued) Script Name Description Associated Files raidcfg.sh Configures the selected • tkenvset.sh — Used by raidcfg.sh to inform the task RAID controller scripts where to find the DTK detected in the system. utilities, scripts, and configuration files. • raidcfg — Used by raidcfg.sh to retrieve RAID information and to configure settings. partcfg.sh Creates and populates • tkenvset.sh — Used by partcfg.
Table 5-8. Other Scripts for Linux (continued) Script Name Description upinit.sh Creates and populates the Dell utility partition. Associated Files • tkenvset.sh — Used by upinit.sh to inform the task scripts where to find the DTK utilities, scripts, and configuration files. NOTE: Do not make any modifications to the • fdisk — Used to create partitions on your disk. upinit.sh script. • mbr — File necessary to create a bootable Dell utility partition. • sysdrmk — Used by upinit.
In Windows: set DT_DRIVE=X: set DT_PATH=%DT_DRIVE%\Dell\Toolkit set DT_TOOLS=%DT_PATH%\Tools set DT_SYSTEMS=%DT_PATH%\Systems set DT_SCRIPTS=%DT_PATH%\Template\Scripts set DT_STOP_ON_ERROR=FALSE In Linux: DT_PATH=$dt_drive/opt/dell/toolkit DT_TOOLS=$dt_path/bin DT_SYSTEMS=$dt_path/systems DT_SCRIPTS=$dt_path/template/scripts DT_STOP_ON_ERROR=FALSE DT_DRMK=$dt_path/opt/dell/drmk Perform the following steps to confirm and/or edit the installation path variables: 1 For Windows, set the variable that represents
3 Set the variable that defines the directory containing DTK utilities (DT_TOOLS). This variable is set to %DT_PATH%\Tools (Windows) or $dt_path/bin (Linux) by default in the sample script. Edit this path to reflect the actual location of DTK utilities, if necessary. 4 Set the variable that defines the directory containing the configuration files for your Dell systems (DT_SYSTEMS). This variable is set to %DT_PATH%\Systems (Windows) or $dt_path/systems (Linux) by default in the sample script.
To edit the SYSCFG capture variables (for Windows), locate the following lines: In SYSCAP.BAT: set DT_SYS_CAPFILE= %DT_SYSTEMS%\%DT_PLATFORM%\syscfg.ini In syscap.sh: set DT_SYS_CAPFILE= $dt_systems/$dt_platform/syscfg.ini To edit the SYSCFG replication variables (for Linux), locate the following lines: In SYSREP.BAT: set DT_SYS_REPFILE= %DT_SYSTEMS%\%DT_PLATFORM%\syscfg.ini In syscap.sh: DT_SYS_REPFILE=$dt_systems/$dt_platform/syscfg.
In raccap.sh: DT_RAC_CAPFILE=$dt_systems/$dt_platform/raccfg.ini To edit the RAC configuration variables, locate the following lines: In RACREP.BAT: :: RAC section set DT_NICCFG=10.98.8.121 set DT_RAC_CAPFILE= %DT_SYSTEMS%\%DT_PLATFORM%\raccfg.ini In racrep.sh: # RAC section DT_NICCFG=10.98.8.121 set DT_RAC_CAPFILE= $dt_systems/$dt_platform/raccfg.
:: DELLUP section set DT_UP_SIZE=32 set DT_UP_IMAGE=%DT_SYSTEMS%\UPIMG.BIN :: RAIDCFG section set DT_VD_SIZE=10480 :: default size for virtual disk In partcfg.sh: DT_PARTN_UP=on DT_MOUNT=/tmp/up # Default Hard Drive DT_HD=/dev/sda # PARTCFG section set DT_OS_SIZE=4000 # DELLUP section set DT_UP_SIZE=32 set DT_UP_IMAGE=$dt_systems/upimg.bin # RAIDCFG section DT_VD_SIZE=10480 # default size for virtual disk CAUTION: DT_MOUNT specifies the mount point of the Dell utility partition.
3 Edit the default variable value (in MB) for the primary operating system partition (DT_OS_SIZE=4000), if applicable. 4 Edit the default variable value for file system type (DT_OS_FSTYPE= FAT32), if applicable. NOTE: The valid values are FAT32 and NTFS. 5 If the DT_PART_UP variable is set to ON, edit the default variable value (in MB) for the utility partition (DT_UP_SIZE=32), if applicable.
variables set in the RACREP.BAT or racrep.sh sample script. This script uses the RACADM.EXE for Windows and the racadm wrapper script or the syscfg utility for Linux (depending on the version of RAC on your system) to configure the RAC in the target system using the RAC configuration file, raccfg.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 TKENVSET.BAT or tkenvet.sh scripts.
SYSREP.BAT or sysrep.sh The SYSREP.BAT or sysrep.sh 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 or sysrep.sh scripts. This script uses the SYSCFG 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.
Using DTK Sample Scripts to Capture Configuration Information The SYSCFG and RACADM utilities can read the source system configuration and duplicate that configuration on a target system using a sample DTK script file. These configuration files are used during a full deployment to configure the target system’s BIOS, BMC, and RAC settings. The following sections provide instructions for: • Capturing the System BIOS and BMC Configuration With the SYSCAP.BAT or syscap.
Perform the following steps to run the SYSCAP.BAT or syscap.sh sample script to capture BIOS and BMC configuration information in the syscfg.ini file: 1 Edit the startnet.cmd file (on your Windows PE image) or start-up script file (on your embedded Linux image) to call the SYSCAP.BAT or syscap.sh script after the network share with the pre-built DTK directory structure is mounted. For example, add: In Windows: call Z:\Dell\x32\Toolkit\Template\Scripts\SYSCAP.
RACCAP.BAT or raccap.sh The RACCAP.BAT or raccap.sh sample script captures RAC configuration settings and saves them to a specified location. An optional user input can be passed as a parameter. You can provide the path or file name as an input to this script. The default variable values used in this script are set to the correct default values to perform a scripted deployment. The RACCAP.BAT or raccap.sh script uses the RACADM.
3 Edit the startnet.cmd (Windows PE image) or start-up script (embedded Linux) file to remove the text you added in step 1. NOTE: The RAC configuration file is referred to as the .cfg file in the Integrated Dell Remote Access Controller 7(iDRAC7) Enterprise for Blade Servers User Guide and the Dell Remote Access Controller 4 User’s Guide. See these guides for additional information about manually creating a RAC configuration file. NOTE: Do not replicate the RAC IP address when creating a .cfg file.
The W2K8INST.BAT and W2K8INST.BAT scripts (on supported Windows operating systems), lininst.sh sample script (on supported Red Hat Enterprise Linux Server operating system) and suseinst.sh sample script (on supported SUSE Linux Enterprise Server operating system) are used to perform an installation. The variables and paths must be specified before the operating system can be installed. NOTE: While installing Linux, make sure that you install grub in the boot partition.
The W2K8INST.BAT script uses the UNATTEND.XML file in conjunction with SETUP.EXE utility to install the operating system files. For more information about preparing the UNATTEND.XML file, see "UNATTEND.XML" on page 78. Specifying the Windows Installation Variables and Installation Paths To edit the Windows operating system installation variables, locate the following lines in W2K8INST.BAT: :: Location of Unattend.xml file set DT_UNATTEND= %DT_SYSTEMS%\%DT_PLATFORM%\unattend.xml UNATTEND.XML The UNATTEND.
lininst.sh The lininst.sh sample script is used to perform an unattended installation of a supported Red Hat Enterprise Linux Server operating system. The variables and paths must be specified before the operating system can be installed. Utilities Used grub — Used in conjunction with the kernel image and initial ramdisk files, along with the unattended answer file to install the operating system.
NOTE: See your operating system documentation for instructions on modifying the options in the ks.cfg/ks-rhel5.cfg/ks-rhel6.cfg file to customize the scripted installation of your operating system. When you have completed all necessary modifications of the ks.cfg/ksrhel5.cfg/ks-rhel6.cfg file, save the completed file in the /opt/dell/toolkit/systems/ directory. Install Linux Using lininst.sh On a Linux system, edit the /etc/exports file.
12 From /opt/dell/toolkit/template/scripts, run /lininst.sh script. 13 After 20 seconds, the server reboots and boots to the grub prompt. The Red Hat Enterprise Linux operating system unattended installation proceeds. suseinst.sh NOTE: While installing Linux, make sure that you install grub in the boot partition. Otherwise, you cannot boot to the utility partition by pressing the F10 key during reboot. The suseinst.
External Dependencies The DT_PLATFORM variable is set during deployment by tkenvset.sh using platform discovery. The suseinst.sh script uses the unattended answer file in conjunction with the grub utility and kernel image and initial ramdisk files to install the operating system files. For more information about preparing the unattended answer file, see "autoinst.xml for SUSE Linux Enterprise Server" on page 82. autoinst.xml for SUSE Linux Enterprise Server The autoinst.
Running the Deployment Scripts 6 This chapter provides best practices, procedures, and scenarios for using the Deployment Toolkit (DTK) to perform pre-operating system configuration tasks and to install supported operating systems on supported Dell systems. After you have populated the deployment directory structure with all necessary files and carefully edited the deployment scripts and configurations files, you are ready to begin the final stage of the deployment process.
• Integration of DTK Directory Structure • Creating a Bootable Media • Running the Image Creating and Customizing Images If you are using Windows PE 2.0 or Windows PE 3.0, download Windows Automated Installation Kit (Windows AIK) from the Microsoft website at microsoft.com. By default, Windows AIK is copied to the C:\Program Files\Windows AIK directory. You must include Dell-customized drivers and instrumentation drivers into your Windows PE media-based operating system. NOTE: DTK 3.
2 Execute the script. On Windows PE 2.0: VPE_driverinst.bat On Windows PE 3.0: WINPE3.0_driverinst.bat Where and is the destination path to create the directory structure for Windows PE 2.0 and Windows PE 3.0 respectively and is the path to Dell drivers in the extracted DTK toolkit. For example: On Windows PE 2.0: VPE_driverinst.bat C:\vistaPE_x86 C:\DELL\x32\DRIVERS This pre-installs the Dell drivers into winpe.wim. On Windows PE 3.
4 Run the following command: On Windows PE 2.0 oscdimg -n -bc:\vistaPE_x86\etfsboot.com c:\vistaPE_x86\ISO c:\vistaPE_x86\WinPE2.0.iso On Windows PE 3.0 oscdimg -n -bc:\winpe_30\etfsboot.com c:\winpe_30\ISO c:\winpe_30\WinPE3.0.iso This command creates a media bootable ISO image: WinPE2.0.iso.(Windows PE 2.0) or WinPE3.0.iso (Windows PE 3.0). You can use any CD/DVD burning software to burn the image onto a CD/DVD.
This deployment method is also easy to assemble. In addition, it provides greater flexibility in terms of making changes to the scripts and configuration files. Any change to the system configuration, for example, does not require re-creation of the bootable media. This method also provides access to the remote share as writable media. Hence, the configuration files captured during the deployment automation process can be saved to this remote share.
Deployment Using Removable Boot Media With a Network Connection (Media-Based) for Windows For media-based deployment with a network connection: 1 Create a deployment media containing a bootable image with the appropriate media and network drivers, along with any utilities needed to connect to a network share. The deployment media initiates the deployment process by mapping to the network share where the deployment directory structure resides.
2 Insert the bootable media into the media drive of the system to be deployed (the target system). 3 Boot or reboot the target system. The deployment process begins and the following tasks are completed: • Windows PE or embedded Linux, as the case maybe, is loaded from the media. • DTK scripts execute the necessary DTK utilities from the media. • Configuration information is read from the media. • The operating system is installed from the media.
Network-Based Deployment The procedure below enables you to boot DTK over network and pass parameters (startup script location and name) during boot using the Pre-boot eXecution Environment (PXE) configuration file. This automatically launches the start-up script off the network share, when DTK is booted. 1 Obtain the ISO image of the embedded Linux available at support.dell.com. 2 Burn the ISO image using any commonly available CD/DVD burning software.
8 The modified script is picked up and executed during the boot process. NOTE: The network share on which you have the scripts and DTK files are mounted to /opt/dell/toolkit/systems. NOTE: Make sure to specify the correct RAMDISK size in the pxe config file before booting through PXE. (A sample pxe config file is provided in /mnt/cdrom/isolinux/isolinux.cfg.
5 In /mnt/cdrom/isolinux.cfg, edit the cd install section to point to your customized start-up script. In other words, add the share_script option; for example: label 1 kernel SA.1 append initrd=SA.2 ramdisk_size=55321 Stage3_type=cdrom DEBUG=0 quiet share_type=cdrom share_script=dracupdate.sh Then, use mkisofs to make your customized media image; for example: mkisofs -o usaf.iso -b isolinux/isolinux.bin -c isolinux/boot.
Using RPMs 1 Mount the media and navigate to /mnt/cdrom/RPMs directory. NOTE: The /mnt/cdrom/RPMs directory contains all DTK RPMs and the dependency RPMs. 2 Install the required DTK RPMs. For more information about DTK RPMs, see Table 3-9. NOTE: To resolve the RPM dependency related issues, install the missing RPMs from /mnt/cdrom/RPMs directory. If the RPMs are not available in this directory, install these RPMs from the operating system media.
• DTK tools and utilities extracted from the embedded Linux media from /mnt/cdrom/tools/dell.tar.gz • Necessary entries in the ld.so.config file so that the libraries get loaded Integrate all the above mentioned libraries, Dell toolkit libraries, tools, and utilities into your embedded Linux environment and proceed with deployment. NOTE: Make sure that the raidcfg executable in the /bin directory is a symbolic link to the raidcfg in the Dell-provided /lib folder. NOTE: Refer to start-stage3.
A Running Dell Update Packages in Embedded Linux This chapter provides best practice procedures and scenarios for running Dell Update Packages in the embedded Linux environment on supported Dell systems. The common scenarios for running Update Packages are: Running Update Packages in Dell-Provided Embedded Linux 1 Obtain the required update packages from the Dell Server Updates DVD or from support.dell.com. 2 Save the update packages on a network share.
Table A-1. Dependencies for Dell Update Packages to Run in Customized Embedded Linux (continued) Update Packages Dependency Dependencies Available On /etc/dataeng /mnt/cdrom/tools megaraid driver 2.4.2.0 /mnt/cdrom/tools SCSI drivers Kernel Instrumentation drivers /mnt/cdrom/tools racser4.
Known Issues and Frequently Asked Questions B This chapter describes known issues with the Deployment Toolkit (DTK) utilities and scripts, including answers to some frequently asked questions. Known Issues The following issues are organized by DTK utility or other function. General Issues • Virtual disk creation and/or deletion takes a long time on Microsoft Windows PE.
SYSCFG Issues • On systems prior to PowerEdge yx2x systems, DTK cannot clear setup passwords and system passwords. • On PowerEdge 1950 and 2950 systems with internal USB, you can configure BIOS settings for internal USB Port only if the User Accessible/external (UA) USB ports are set to All Ports On.
Q: When I use the sample DTK scripts to deploy multiple systems, do I need to edit the configuration files to reflect unique information (such as unique system names, IP address, and BIOS asset tags) for each system? A: The sample scripts are provided as examples for users who want to develop their own deployment process. You may find that the scripts work perfectly in your environment, or you may need to develop your own scripts entirely from scratch.
Q: When I execute RAIDCFG with the RAID level of "01," RAIDCFG creates RAID 1, not RAID 01. A: This behavior occurs because the RAIDCFG CLI parser ignores zeros preceding any parameter value. For example, -r=01 is parsed as -r=1. Q: What is strict creation? A: Strict creation is an optional flag that has been added to the create virtual disk command. It allows you to create virtual disks only if the array disks (that is, hard drives) are within a specified percentage of disk space of each other.
Features that have been removed from the DOS version include: • The --name and --wait options in the create command • The --runlocation and the --scratchlocation options • The --getpercentcomplete environment variables Q: What is the minimum virtual disk size that I can create? A: For CERC-SATA 1.
Q: What is span length? A: Span length is the field needed when you try to create a RAID 50. The number represents the span size of the RAID 5. Q: What pre-operating system environments are CERC SATA 1.5/6ch, and CERC SATA 1.5/2s controllers supported on? A: They are supported only on embedded Linux. Q: PARTCFG cannot enumerate the virtual disk(s) created by RAIDCFG. What must be done? A: A reboot is required for PARTCFG to enumerate virtual disks after creating a virtual disk using the RAIDCFG command.
Q: Are duplicate usernames allowed in the BMC? A: No. If you enter a username value that already exists, the SYSCFG utility returns an error code of 89, which means This username is already in use. Enter a unique username. Q: In --solcfgparams, when I set the Serial Over LAN (SOL) character send threshold using solcharsendthreshold to be 225, I get a Hardware subsystem error. Invalid data field in request.
Q: Can we use the same sample scripts that we have from earlier versions of DTK? A: The scripts written for the previous versions (2.x) of DTK does not work in DTK 3.x or later versions for embedded Linux. See the directory /opt/dell/toolkit/template/scripts for the sample scripts. Q: After I install a legacy operating system on a newer Dell system, the Linux kernel does not boot and panics.
Windows PE Questions Q: My system gets the error Illegal or Missing File Types Specified in Section Files.SCSI.Name during an unattended installation of a supported Windows operating system on supported Dell systems. A: This behavior can occur when the line in the Txtsetup.oem file under the [Files.SCSI.name] heading is not a supported file type. To resolve this behavior, you must remove the line in the Txtsetup.oem file.
Known Issues and Frequently Asked Questions
Index C network-based, 88 capturing configuration information Windows PE, 73 deployment prerequisites embedded Linux, 16 Windows PE, 15 capturing the system BIOS & BMC configuration Windows PE, 73 drivers embedded Linux, 41 Windows PE, 16 configuration files, 9 DTK installing, 30 contents DTK Windows PE, 33 creating a master file master batch file in Windows PE, 52 creating deployment directory structure Windows PE, 43 creating disk partitions Windows PE, 68 DTK deployment overview, 23 DTK prerequi
M R Master Batch File sample, 51 what is, 51 RAC configuring, 25 Media-Based local deployment embedded Linux, 83 Running, 95 O operating system installation files embedded Linux, 48 Windows PE, 46 overview deploying, 24 P performing a scripted deployment Windows PE, 52 preparing operating system installation scripts Red Hat Enterprise Linux Server, 77 Windows PE, 76 prerequisites for deployment embedded Linux, 16 Windows PE, 15 prerequisites for installation embedded Linux, 15 Windows PE, 14 108 In
Dell-provided embedded linux, 95 S sample scripts Windows PE, 38 scripted deployment in embedded Linux autoinst.xml, 82 ks.cfg, 79 lininst.sh, 59 raidcfg.sh, 63 upinit.sh, 64 scripted deployment in Red Hat Enterprise Linux lininst.shT, 79 scripted deployment in Windows PE capturing the RAC configuration, 74 PARTCFG.BAT, 72 RACCAP.BAT, 75 RACREP.BAT, 70 RAIDCFG.BAT, 71 SYSCAP.BAT, 73 SYSREP.BAT, 56, 72 TKENVSET.BAT, 61 UPINIT.BAT, 76 W2K8INST.BAT, 77 WININST.
Index
