Dell OpenManage Deployment Toolkit Version 3.
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. © 2011 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 . . . . . . . . . . . . . . . . . . . . . . . Information Organization in this Guide What’s New in This Release . . . . . . . . . 11 . . . . . . . . . . . . . . 14 Prerequisites and Requirements . . . . . . . . . . . . Supported Operating Systems to Run DTK Utilities . . . . . . . . . Supported Systems . 11 14 . . . . . . . . . 15 . . . . . . . . . . . . . . . . 15 Supported BIOS Firmware Versions . . . . . . . . 15 Installation Prerequisites . . . . . . . . . .
2 Choosing a Microsoft Windows PE-Based Deployment Method . . . . . . . . Choosing a Deployment Method for Microsoft Windows PE . . . . . . . . . . . . . . . . . . Media-Based Local Deployment . . . . . 25 . . . . . . . . . . 25 Media-Based Local Deployment With Networking Enabled . . . . . . . . . . . . . . . . 26 . . . . . . . . . . 28 . . . . . . . . . . . 28 Using a Third-Party Deployment Solution Framework . . . . . .
Configuring a Source System RAC Configuration 4 . . . . . . . . . . . . . . 50 . . . . . . . . . . . . . . . . . 51 Preparing the Script Files for Deployment Using Microsoft Windows PE . . . . . . . . . . . . . . . . . . . . . . Using the Sample DTK Scripts to Run a Full Deployment in Windows PE . . . . . . . . . . . . . . Editing the Sample Batch Files to Perform a Complete System Deployment in Windows PE Scripts for Deployment . 54 . . . . . 55 . . . . . . . . . . . . . . 56 TKENVSET.
5 Running Deployment Scripts Using DTK and Microsoft Windows PE . . . Creating and Customizing Images for Windows PE 2.0 . . . . . . . . . . . . . . . 75 . . . . . . . . . . 75 Integration of DTK Directory Structure in Windows PE Build . . . . . . . . . . . . Creating a Bootable Media . . . . . . 76 . . . . . . . . . . . . 77 . . . . . . . . . . 77 Media-Based Local Deployment . . . . . . . . . . 77 Creating and Customizing Images for Windows PE 3.0 . . . . . . . . . . . . . . . . . . . . .
Preparing the Directory Structure for Deployment in Embedded Linux . . . . . . . . . Upgrading Your DTK Version . . . . . . . . . . 89 . . . . . . . . . . . . . . 89 Installation for Embedded Linux DTK Contents . . . . . . . . . . . . 89 . . . . . . . . . . . . . . . . . . . . . . 93 System Utilities and Supporting Files Sample Configuration Files . 94 . . . . . . . . . . . . 95 . . . . . . . . . . . . . . . . . . . 96 . . . . . . . . . . . . . . . . . . . . . . . .
Editing the Sample Batch Files to Perform a Complete System Deployment in Embedded Linux . . . 106 . . . . . . . . . . . 113 . . . . . . . . . . . . . . . . . . . . . 113 Editing the tkenvset.sh Script tkenvset.sh Editing DTK Task Scripts . . . . . . . . . . . . . . Using DTK Sample Scripts to Capture Configuration Information in Embedded Linux Capturing the System BIOS and BMC Configuration With the syscap.sh Sample Script . . . . . . . . . . . . . . . . . . 120 . . . . . . .
10 Running Dell Update Packages in Embedded Linux . . . . . . . . . . . . . . . . . . Running Update Packages in Dell-Provided Embedded Linux . . . . . . . . . . . . . . Running Update Packages in Customized Embedded Linux . . . . . . . . . . . . . 11 Known Issues and Frequently Asked Questions . . . . . . . . . . . Known Issues . . . . 135 . . . . . 135 . . . . . . . 137 137 . . . . . . . . . . . . . . . . . . . . . . General Issues 137 . . . . . . . . . . . . . . . . . . .
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 your 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.
This enables the user to read only those sections that are relevant. Content in this User’s Guide is organized as documented in Table 1-1. Table 1-1.
Table 1-1. Information Organization in This Guide (continued) Topics Section for Windows PE Section for Embedded Linux Preparing the deployment script files, that includes best practices for: "Preparing the Script Files for Deployment Using Microsoft Windows PE" on page 53 "Preparing the Script Files for Deployment Using Embedded Linux" on page 105 • Editing and modifying sample scripts.
What’s New in This Release The new features for this release include: • Support for Microsoft Windows Server 2008 R2 with SP1. • Support for following BIOS options: coreperformanceboost, memdynamicpower, memprefailurenotify, and inteltxt. For more information, see Dell OpenManage Deployment Toolkit Command Line Interface Reference Guide. • Support for the following Dell Power Edge systems: R210 II, T110 II, M915, R910, R810, and M910. NOTE: From DTK 3.
Supported Operating Systems to Run DTK Utilities For Windows PE, DTK utilities support Windows PE 2.0 (32-bit and 64-bit) and Windows PE 3.0 (32-bit and 64-bit). For embedded Linux, DTK utilities support Red Hat Enterprise Linux Server version 4, update 4 (32-bit). Supported Systems For the list of Dell systems supported for this version of DTK, see the readme.txt which is available as part of the DTK download or Dell Systems Software Support Matrix at support.dell.com/manuals.
Deployment Prerequisites Before beginning the deployment process for Windows PE, ensure that you have all of the following tools, software, and information ready to use or consult: • Windows Automated Installation Kit (AIK) 1.1 released with Microsoft Windows Vista SP1 and Windows Server 2008 to build Windows PE 2.0. • Windows AIK for Windows 7 to build Windows PE 3.0. • An unzip utility. • Working knowledge to build Windows PE 2.0 and Windows PE 3.
• A workstation with the following capabilities: – A writable media drive – Network access • A target system with a media drive, if performing a local deployment. • A target system with a media drive and network access, if performing a network deployment. • All DTK utilities, sample scripts, sample configuration files, and RPM packages. • All operating system RPM packages that DTK RPMs require.
For Windows PE, the sample configuration files contain examples to deploy the following operating systems: • Windows Server 2008 R2 with SP1 • Windows Server 2008 R2 • Windows Server 2008 SP2 (32-bit and 64-bit) • Windows Server 2003 R2 with SP2 (32-bit and 64-bit) NOTE: For the latest supported operating systems, see the Windows PE documentation.
DTK Deployment Overview The deployment process can be separated into two main tasks: preparation and the actual deployment. Preparing for Deployment For using DTK utilities and scripts to deploy to a target system in the Windows PE environment: 1 Copy or extract DTK utilities, sample scripts, sample configuration files, and drivers provided (in the zip file) to the Windows PE image.
For using DTK utilities and scripts to deploy to a target system in the embedded Linux environment: 1 Obtain the DTK Linux ISO image, which is a self-contained bootable ISO image. 2 Use and customize the sample scripts per your requirements. 3 Set up an optimally configured source system by using the Systems Build and Update Utility on the Dell Systems Management Tools and Documentation DVD (to install your operating system) and the Systems Service and Diagnostics Tools (to load drivers).
Deployment Using Removable Boot Media With a Network Connection (MediaBased) 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.
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 (Remote) For Windows PE environments, deployment using RIS is recommended. (For details, see the Microsoft RIS documentation.
• The Dell OpenManage Legacy Compatibility Guide provides compatibility information about Server Administrator installation and operation on various hardware platforms (or systems) running supported Windows, Red Hat Enterprise Linux Server, and SUSE Linux Enterprise Server operating systems. • The Dell Systems Software Support Matrix provides information about the various Dell systems, the operating systems supported by these systems.
• The Dell Baseboard Management Controller Utilities User's Guide provides information about configuring a managed system to use the BMC Management Utility to manage your system through its BMC. • The Dell Update Packages User's Guide provides information about obtaining and using Dell Update Packages as part of your system update strategy. • The Glossary provides information about the terms used in this document. Additionally, the Deployment Toolkit readme.
Choosing a Microsoft Windows PE-Based Deployment Method 2 A well-thought-out deployment plan is critical to the success of your deployment effort and includes the following considerations: • Assessing your existing IT environment • Selecting an operating system • Selecting the optimum Dell OpenManage systems management software configuration for your system • Choosing a deployment method The Deployment Toolkit (DTK) is designed to be flexible enough to fit into almost any deployment plan.
This deployment method is easy to assemble, but is the least flexible. Any change to the system configuration, for example, requires the creation of a new bootable media. This method does not provide a writable media, making it necessary to use predefined and tested configuration files.
Bootable Windows PE Media With Networking Enabled This process includes: • Creating a bootable Windows PE media with the appropriate network drivers. This step enables networking services to start, get an IP address, and bring the target system into a functioning network.
Using a Third-Party Deployment Solution Framework You can use DTK with any existing third-party deployment solution framework that provides an Automated Deployment Services (ADS) booting infrastructure for Windows Deployment Services (WDS) on Windows PE 2.0 that can be used as the transport mechanism for DTK utilities. Because each third-party deployment framework is unique, however, these solutions fall outside the scope of this document.
Table 2-1. Deployment Method Matrix (continued) Deployment Methods Complexity Remote Moderate deployment over a network (bootable Windows PE media with network stack loaded) Advantages • Everything is in one place • Must have in a network share. network connection. • Easy to manage— changes have to be made • Deployment tasks in only one place. must be performed at the • Data captured (profiles) individual target can be stored in a system. network share. • Data can be replicated from a network share.
Choosing a Microsoft Windows PE-Based Deployment Method
3 Preparing the Directory Structure for Deployment in Microsoft Windows PE 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.
Perform the following steps to extract DTK components to a workstation running Windows: 1 Download the DTK file DTK3.X-WINPE-XX.exe from support.dell.com and save it on your system. 2 After the file downloads, double-click the file. Dell OpenManage Deployment Toolkit for WindowsPE screen containing the product and download information appears. Click OK. 3 Click Unzip. By default, files are unzipped to C:\.
The files are unzipped in the directory structure shown in Figure 3-1. 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: Z:\Dell\x32\Toolkit\Tools • Sample scripts: Z:\Dell\x32\Toolkit\template\scripts • Sample configuration files: Z:\Dell\x32\Toolkit\template\Configs DTK utilities for 64-bit systems are located in the following directories: • Utilities: Z:\Dell\x64\Toolkit\Tools • Sample scripts: Z:\Dell\x64\Toolkit\template\scripts • Sample configuration files: Z:\Dell\x64\Toolkit\template\Configs The directory Z:\Dell\x32\To
System Utilities and Supporting Files Table 3-1 describes the files located in Toolkit\Tools. These are the core tools (utilities) that perform pre-operating system configuration and deployment tasks. See the Dell OpenManage Deployment Toolkit Command Line Interface Reference Guide for complete information about the capabilities of each DTK utility. Table 3-1. System Utilities and Supporting Files Toolkit Components Purpose config.ini Configuration file used by RAIDCFG.EXE. NOTE: Do not edit this file.
Table 3-1. System Utilities and Supporting Files (continued) Toolkit Components Purpose SYSCFG.EXE • Reports and configures: – BIOS settings and options – BMC settings and options – RAC 5 settings and options – IDRAC settings and options – IDRAC 6 settings and options • Maintains system state between reboots. • Reports hardware devices and other system-related information. SyscfgErrorCodes.txt Lists the error codes and messages for the SYSCFG.EXE tool. sysdrmk.exe Used by UPINIT.
Table 3-2. Sample Configuration Files 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\. UNATTEND.
Sample Scripts Table 3-3 lists sample scripts necessary to perform a scripted deployment. The sample scripts are located in Toolkit\template\scripts. NOTE: All DTK scripts are provided as examples only. The batch scripts and configuration files must be modified to reflect the unique information for each deployed system. Table 3-3. Sample Scripts Toolkit Components Purpose createup.cfg This file is used by UPINIT.BAT. DISKPARTCLR.CFG Used by PARTCFG.BAT to clear the partitions on the selected disks.
Table 3-3. Sample Scripts (continued) Toolkit Components Purpose UMOUNTUP.CFG This file is used by UPINIT.BAT. UPINIT.BAT Creates and populates the Dell utility partition. WININST.BAT Performs an unattended installation of supported Windows Server 2003 operating systems. W2K8INST.BAT Performs an unattended installation of supported Microsoft Windows Server 2008 operating system. DTKRUNALL.BAT Applies BIOS, BMC, RAC, and RAID settings saved in the files to the current system.
Drivers Table 3-5 describes the essential and optional drivers required for Dell-supported hardware to build your Windows PE environment. NOTE: The drivers provided have been tested successfully in the Windows PE environment. Table 3-5. Drivers Drivers Purpose winpe2.x\ Used to install Dell-provided drivers, from VPE_DRIVERINST.BAT Z:\Dell\x32\Drivers or Z:\Dell\x64\Drivers, into the customized Windows PE 2.0 image. winpe3.x\ Used to install Dell-provided drivers, from WINPE3.
Table 3-6 lists the system files and other tools for you to be able to use DTK utilities and its sample scripts. Table 3-6. Supporting Tools and System Files Additional Tools Purpose Source Windows AIK 1.1 released with Vista SP1 and Windows 2008 to build Windows PE 2.0 Create a bootable media microsoft.com for Windows PE 2.0. Windows AIK for Windows 7 to build Windows PE 3.0 Create a bootable media microsoft.com for Windows PE 3.0. upimg.
If you plan to run a scripted deployment from DTK sample scripts, make sure that the following files are correctly structured in the deployment directory. DTK sample scripts use this structure to set the default paths for deployment. If you make changes to the directory structure, you must also make changes to the sample scripts.
Figure 3-2.
Operating System Installation Files The operating system file structure for Windows server 2003 is shown in Figure 3-3. Figure 3-3.
Creating Operating System Installation Directories for Windows Server 2003 Operating Systems To deploy Windows Server 2003 operating systems: 1 On a management station, create a network sharable folder, for example os_deploy. 2 Create two folders os_deploy\Dell and os_deploy\W2K3SRC. 3 Copy the Dell folder from the extracted WinPE toolkit to os_deploy\Dell on the management station. 4 Copy i386 folder from the Windows Server 2003 operating system media to os_deploy\W2K3SRC on the management station.
9 In the unattend.txt file, modify the following mandatory fields as in Table 3-7. Table 3-7. Mandatory Fields in unattend.txt Field Example OEMBootFiles For a R515 system that has H700 controller, you must retain the following entries and remove the rest of the entries under the field OEMBootFiles. percsas2.sys oemsetup.inf percsas2.cat txtsetup.oem NOTE: These are the files located in the os_deploy\Dell\x32\toolkit\systems\PER515\$OEM$.NET\textmo de folder.
13 On the target system, set the following environment variables: DT_OSSRC=z:\W2K3SRC\I386 DT_UNATTEND=z:\dell\x32\toolkit\systems\PER515 \unattend.txt DT_OEM= z:\dell\x32\toolkit\systems\PER515\$OEM$.NET 14 Navigate to the mount point z:\dell\x32\toolkit\template\scripts. 15 Run the partcfg.bat script to create the partition. 16 Run wininst.bat to install the operating system.
6 If required, modify the unattend.xml for DiskID under the tags DiskConfiguration and ImageInstall. Default value is 0 for DiskID. 7 Make sure that DiskID specified in the unattend.xml is actually available to install the operating system. You can run the DiskPart utility to check disk details. 8 Boot your system with DTK Windows PE image. 9 Run the following command to connect the target system to the shared folder W2K8_deploy.
The operating system file structure for Windows Server 2008 is shown in Figure 3-4. Figure 3-4.
Configuring a Source System You need an optimally configured system, both for testing purposes and as the source for the SYSCFG and RAC configuration files, to be used in the deployment process. See "Using DTK Sample Scripts to Capture Configuration Information in Windows PE" on page 67 for instructions on using the sample DTK scripts, SYSCAP.BAT and RACCAP.BAT, to generate SYSCFG and RAC configuration files that are used to configure the target system.
RAC Configuration Configure the RAC on your source system using the RACADM.EXE utility, if applicable. See the Integrated Dell Remote Access Controller 6 (iDRAC6) Enterprise for Blade Servers User Guide or the Integrated Dell Remote Access Controller 6 (iDRAC6) User Guide for comprehensive information about using the RACADM.EXE utility to configure the RAC on your source system.
Preparing the Directory Structure for Deployment in Microsoft Windows PE
Preparing the Script Files for Deployment Using Microsoft Windows PE 4 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 environment. There are four main tasks: • Writing the deployment master batch file (as an example, referred to as DEPLOY.BAT in this document) or deployment script, editing the TKENVSET.BAT script, to set the variable values used in the deployment scripts.
Using the Sample DTK Scripts to Run a Full Deployment in Windows PE A scripted DTK deployment relies on the master batch file (DEPLOY.BAT) to integrate all the applicable DTK task scripts and utilities and perform pre-operating system configuration tasks before launching the operating system installation files. DEPLOY.BAT, along with the TKENVSET.BAT scripts, makes up the master set of instructions that drives the deployment process. This file is not provided with the sample scripts. A sample DEPLOY.
***************************************************** :: Put hdd as first in boot sequence (1-removable, 2cdrom, 3-hdd) :: If the system configuration has changed (i.e. a ::boot device was added, removed, or enabled in BIOS) ::the following line should be modified to reflect the ::new hdd device number. :: This is calling Windows installer scripts. ***************************************************** ::%DT_TOOLS%\syscfg --bootseq=hdd.emb.0 ::call WININST.
Scripts for Deployment Table 4-1 lists the scripts you may need for deployment. Table 4-1. Capture Scripts 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 4-2. Replication Scripts 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 4-3. Deployment Scripts Script Name Description Associated Files WININST.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 2003 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 4-4. Others (continued) Script Name Description Associated Files RAIDCFG.BAT Configures the selected • TKENVSET.BAT — Used by RAIDCFG.BAT to inform the Redundant Array of task scripts where to find the Independent Disks DTK utilities, scripts, and (RAID) controller detected in the system. configuration files. • RAIDCFG.EXE — Used by RAIDCFG.BAT to retrieve RAID information and to configure settings. PARTCFG.BAT Creates and populates • TKENVSET.BAT — Used by the Dell utility PARTCFG.
TKENVSET.BAT Example Editing The majority of editing required for DTK sample scripts involves the TKENVSET.BAT script. As a result, the scripting discussion focuses on this script. Other task scripts may require edits in certain situations. These optional edits are discussed in "Editing DTK Task Scripts" on page 65. The TKENVSET.BAT script sets the path of DTK installation and variables for the system to be deployed and configured.
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 by default in the sample script. 5 Set the variable that defines the directory containing DTK deployment scripts (DT_SCRIPTS). This variable is set to %DT_PATH%\Template\Scripts by default in the sample script. Edit this path to reflect the actual location of DTK deployment scripts, if necessary.
Specifying the RAC Configuration Variables The IP address for your target system RAC is set in the sample script to 10.98.8.121 by default. Edit this value to reflect the actual IP address of your target system RAC, if applicable. Additionally, the RAC configuration file used to configure your RAC is set by default to raccfg.ini. If you use the RACCAP.BAT sample script to generate the raccfg.ini file, there is no need to edit this default setting.
set DT_PARTN_UP=ON set DT_MOUNT=H :: Default Hard Drive set DT_HD=0 :: PARTCFG section set DT_OS_SIZE=4000 set DT_OS_FSTYPE=FAT32 if not "%DT_PARTN_UP%"=="ON" goto ospart :: 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 CAUTION: DT_MOUNT specifies the mount point of the Dell utility partition.
Perform the following steps to edit the default partition configuration default values, as necessary: 1 Edit the default utility partitioning variable (DT_PARTN_UP=ON), if necessary. This variable sets whether you want to install the Dell utility partition. NOTE: Dell recommends that you install the Dell utility partition. 2 Edit the default variable value for the default hard drive (DT_HD=0), if applicable.
Editing DTK Task Scripts The task scripts called by the master batch file do not require any edits (with the following exceptions) if the default variable values are utilized in the TKENVSET.BAT scripts. However, if you make any changes to the default values set by the TKENVSET.BAT, you must make the same edits to the matching default values set in the appropriate task scripts. Locate the USER MODIFICATION REQUIRED heading in the task scripts to find the variable values you might need to edit.
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.
PARTCFG.BAT The PARTCFG.BAT sample script creates and populates the Dell utility partition using UPINIT.BAT and creates the operating system partition on a specified disk. For more information about using the UPINIT.BAT tool, see "UPINIT.BAT" on page 70. User input is not required to run this script. The default variable values used in this script are set in the TKENVSET.BAT scripts. NOTE: Ensure that DT_HD is set to the required disk to be configured before you execute the PARTCFG.BAT script.
SYSCAP.BAT The SYSCAP.BAT sample script captures BIOS and BMC 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 filename 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 SYSCAP.BAT script uses the SYSCFG.
RACCAP.BAT The RACCAP.BAT 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 script uses the RACADM.
UPINIT.BAT UPINIT.BAT is a tool used to create and populate the Dell utility partition. NOTE: You can use this script to create a new Dell utility partition only if there are no existing partitions on your hard disk. You can also use this script to upgrade or downgrade an existing Dell utility partition. Upgrades or downgrades can be made only to existing Dell utility partitions using the overwrite option. CAUTION: The existing Dell utility partition should be the first primary partition on the hard disk.
External Dependencies The DT_PLATFORM variable is set by TKENVSET.BAT using platform discovery. The WININST.BAT script uses the UNATTEND.TXT file in conjunction with WINNT32.EXE utility to install the operating system files. For more information about preparing the UNATTEND.TXT file, see "UNATTEND.TXT" on page 71. Specifying the Windows Installation Variables and Installation Paths To edit the Windows operating system installation variables, locate the following lines in WININST.
W2K8INST.BAT The W2K8INST.BAT sample script is used to perform an unattended installation of Windows Server 2008 operating system. The variables and paths must be specified before the operating system can be installed. CAUTION: It is strongly recommended that you consult your Windows operating system documentation and unattended deployment documentation to develop a thorough understanding of the Windows unattended installation process before attempting to perform a full scripted deployment.
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.XML file is the default name of the answer file that you use to automate Windows setup during an unattended installation. A sample copy of the UNATTEND.
Preparing the Script Files for Deployment Using Microsoft Windows PE
5 Running Deployment Scripts Using DTK and Microsoft Windows PE 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 in Windows PE Build DTK provides a script, VPE_driverinst.bat, to pre-install the Dell drivers into a base Windows PE 2.0 image (winpe.wim). To execute this script in 32-bit or 64-bit supported systems: 1 At the command prompt, change the directory to the location of VPE_driverinst.bat. Example for 64-bit supported systems: cd C:\Dell\x64\Drivers\winpe2.x Example for 32-bit supported systems: cd C:\Dell\x32\Drivers\winpe2.x 2 Execute VPE_driverinst.
Creating a Bootable Media To create a bootable media: 1 Click Start, navigate to All ProgramsMicrosoft Windows AIK. 2 Click Windows PE Tools Command Prompt to open a command prompt window. 3 Run the following command: oscdimg -n -bc:\vistaPE_x86\etfsboot.com c:\vistaPE_x86\ISO c:\vistaPE_x86\WinPE2.0.iso This command creates a media bootable ISO image called WinPE2.0.iso. You can use any CD/DVD burning software to burn the image onto a CD/DVD.
Integration of DTK Directory Structure in Windows PE 3.0 Build DTK provides a script, WINPE3.0_driverinst.bat, to pre-install the Dell drivers into a base Windows PE 3.0 image (winpe.wim). To execute this script on a 32-bit or 64-bit supported systems: 1 At the command prompt, change the directory to the location of WINPE3.0_driverinst.bat. Example for 64-bit supported systems: cd C:\Dell\x64\Drivers\winpe3.x Example for 32-bit supported systems: cd C:\Dell\x32\Drivers\winpe3.x 2 Execute WINPE3.
Creating a Bootable Media To create bootable media: 1 Click Start, navigate to All ProgramsMicrosoft Windows AIK. 2 Click Windows PE Tools Command Prompt to open a command prompt window. 3 Move to the C:\program files\Windows AIK\Tools\x32 or C:\program files\Windows AIK\Tools\amd64 directory based on the system. 4 Run the following command: 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 called WinPE3.0.iso.
Using a Third-Party Deployment Solution Framework You can use DTK with any existing third-party deployment solution framework that provides an Automated Deployment Services (ADS) booting infrastructure that can be used as the transport mechanism for DTK utilities. Because each third-party deployment framework is unique, however, these solutions fall outside the scope of this document.
Choosing an Embedded LinuxBased Deployment Method 6 A well-thought-out deployment plan is critical to the success of your deployment effort and includes the following considerations: • Assessing your existing IT environment • Selecting an operating system • Selecting the optimum Dell OpenManage systems management software configuration for your system • Choosing a deployment method The Deployment Toolkit (DTK) is designed to be flexible enough to fit into almost any deployment plan.
Network-Based Deployment NOTE: DTK network-based deployment is not supported from mapped Novell NetWare systems. The general network-based deployment process includes the following steps: 1 Modify the appropriate section in pxe config file. 2 Boot the target server from PXE. DTK start-up phase mounts the network share specified in the pxe config file. DTK start-up phase runs the script (name specified in the pxe config file) from the network.
Creating a Bootable Media With Network Stack For a remote deployment, you need a bootable media. This bootable media must have the embedded Linux network stack with specific network drivers to facilitate networking. After you have a network share created and populated with all the necessary DTK components and supporting files, you can access all required files by mounting a network share from the target system. You can perform all of these tasks automatically.
Media-Based Local Deployment for Embedded Linux The general media-based deployment process includes the following steps: 1 Copy the DTK ISO image into a share. 2 Modify the appropriate section in the isolinux/isolinux.cfg file. 3 Reburn the contents into a CD/DVD (master CD/DVD). 4 Boot the target server from the master CD/DVD. The DTK startup phase mounts the CD/DVD. The DTK startup phase runs the script (name specified in the isolinux.cfg file) from the CD/DVD.
Using DTK Utilities and Scripts From a Bootable Media The bootable media can be configured to start and execute the master deployment file during the booting process. The master deployment file performs all necessary pre-operating system configuration tasks and then installs the operating system from the files in the deployment directory structure on the media. NOTE: You must write the master deployment file. This file is not provided with the sample scripts.
Deployment Matrix (Embedded Linux) Depending on the scope, current business needs, network setup, and process, you might select any of the suggested methods of deployment. Table 6-1 outlines four typical methods of deployment and the environment most suitable for each. Table 6-1. 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.
Table 6-1. Deployment Method Matrix (continued) Deployment Methods Complexity Remote Moderate deployment over a network (bootable embedded Linux media with network stack loaded) Advantages Disadvantages • Everything is in one place in a network share. • Must have network connection. • Deployment tasks must • Easy to manage— be performed at the changes have to individual target system. be made in only • Must locate the one place. appropriate embedded • Data captured Linux network drivers.
Table 6-1. Deployment Method Matrix (continued) Deployment Methods Complexity Advantages Disadvantages PXE boot High • Everything is in one place on a network share. • Must have high-speed connectivity to network (LAN). • Easy to manage— • Set up time is longer. changes have to be made in only in one place. • High flexibility for remote deployment. • No media required. • Faster deployment.
7 Preparing the Directory Structure for Deployment in Embedded Linux This chapter 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.
The directory structure on the CD/DVD (after it is mounted) is shown in Figure 7-1. Figure 7-1. Media Directory Structure Table 7-1 describes the files, components, and other contents of the mounted media. Table 7-1. Mounted Media Contents Contents Details Location dchipm32.ini Configuration file for the instrumentation software. /opt/dell/toolkit/lib/bin docs Contains Quick Installation Guide. /mnt/cdrom/docs LICENSING Contains all the licenses for the open source components used in this media.
Table 7-1. Mounted Media Contents (continued) Contents Details Location sa.1 Contains the Linux kernel images. /mnt/cdrom/isolinux sa.2 Initial RAM disk containing the embedded Linux component and DTK tools. /mnt/cdrom/isolinux RPMs Contains DTK RPMs and dependency RPMs /mnt/cdrom/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.
Boot the media on to a target system. Figure 7-2 shows the directory structure on the target system. Figure 7-2.
Table 7-2 describes the contents of the directory structure on the target system. Table 7-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 7-3 describes the files, located at /opt/dell/toolkit/bin and the supporting libraries located in /opt/dell/toolkit/lib. For complete information about the capabilities of each DTK utility, see the Command Line Interface Reference Guide. Table 7-3. System Utilities and Supporting Files Toolkit Components Purpose config.ini Configuration file used by raidcfg. pci.ids Used with syscfg to report PCI devices.
Table 7-3. System Utilities and Supporting Files (continued) Toolkit Components Purpose SyscfgErrorCodes.txt Lists the error codes and messages for the syscfg tool. sys.ini A .ini file used with syscfg. UpinitErrorCodes.txt Lists the error codes and messages for upinit.sh. Sample Configuration Files Table 7-4 describes examples of configuration files used to perform a scripted deployment. These files are located at opt/dell/toolkit/template/configs.
Sample Scripts Table 7-5 lists sample scripts necessary to perform a scripted deployment. NOTE: All DTK scripts are provided as examples only. The batch scripts and configuration files must be modified to reflect the unique information for each deployed system. Table 7-5. Sample Scripts Toolkit Purpose Components errhndl.sh Handles errors returned in DTK scripts. lininst.sh Performs an unattended installation of a supported Red Hat Enterprise Linux Server operating system. partcfg.
RPMs Table 7-6 describes all DTK RPMs located at mnt/cdrom/RPMs. Table 7-6. RPMs RPMs Purpose syscfg Configure server BIOS, BMC/DRAC settings, DTK state settings, PCI device detection, and so on raidcfg Configures all supported RAID controllers racadm Configures RAC NOTE: Besides the listed RPMs, a set of dependency RPMs are also available in this location.
Other Supporting Tools and System Files While DTK provides all the necessary utilities and scripts for deploying Dell systems, additional applications, utilities, and system files are needed to create the pre-operating system environment in which this toolkit is used. Table 7-8 is a matrix of system files and other tools that you need to use with DTK utilities and its sample scripts. Table 7-8. Supporting Tools and System Files Additional Tools Purpose Source mkfs.* To format hard-drive partitions.
Table 7-8. Supporting Tools and System Files (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.
DTK Utilities and Files All necessary DTK files are provided on the ISO image. The sample scripts provided with DTK are set up to use the default paths. NOTE: If you choose to create a directory structure for DTK components that is different from the one provided in the initial installation, carefully review and edit each sample script (where necessary) to reflect the different directory structure. NOTE: The unzip utility is needed to create the Dell utility partition.
Figure 7-3. DTK System-Specific File Structure 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.
For a sample directory structure for deployment on a supported Linux operating system, see Figure 7-4. NOTE: If you choose to create a directory structure for the Linux installation files that is different from the one suggested in this guide, be sure to carefully review and edit each sample script (where necessary) to reflect the different directory structure. Figure 7-4.
Configuring a Source System You need an optimally configured system both for testing purposes and as the source for the SYSCFG and RAC configuration files to be used in the deployment process. For instructions on using the sample DTK scripts, syscap.sh and raccap.
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. RAC Configuration Configure the RAC on your source system using the racadm utility, if applicable.
8 Preparing the Script Files for Deployment Using Embedded Linux 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 embedded Linux environment. There are four main tasks: • Writing the master deployment file and editing the tkenvset.sh script to set the variable values used in the deployment scripts. • Editing the supporting task scripts, as necessary.
Editing the Sample Batch Files to Perform a Complete System Deployment in Embedded Linux The sample scripts utilize DTK utilities, the additional supporting utilities, the source system configuration files, the target system hardware drivers, and the operating system installation files to perform a full deployment on the target system. The sample scripts provided with DTK can be edited and customized using any ASCII text editor that conforms to the hardware available on the target systems.
Table 8-1. Capture Scripts 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 8-2. Replication Scripts 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 8-3. Deployment Scripts 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 8-3. Deployment Scripts (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 8-4. Other Scripts Script Name Description Associated Files tkenvset.sh Sets the path of DTK installation and variables for the system to be deployed and configured. The variables and paths in this file must be specified before any of the other supporting scripts can be used. • syscfg — Used by tkenvset.sh to discover the system type. raidcfg.sh Configures the selected • tkenvset.sh — Used by RAID controller raidcfg.sh to inform the task detected in the system.
Table 8-4. Other Scripts (continued) Script Name Description Associated Files partcfg.sh Creates and populates • tkenvset.sh — Used by partcfg.sh to inform the task the Dell utility partiscripts where to find the DTK tion and the deployutilities, scripts, and ment partition on a specified disk. The configuration files. partcfg.sh script uses a • fdisk — Used to create /tmp folder to store a partitions on your disk. When few temporary files criticreating an embedded Linux cal to its execution.
Table 8-4. Other Scripts (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.sh to patch the boot sector.
Specifying DTK Installation Paths The tkenvset.sh sample script is provided with the following default values. These values must be confirmed in some cases, and modified in other cases, before a deployment.
5 Set the variable that indicates whether you want the deployment process to exit when any error is returned (DT_STOP_ON_ERROR). This variable is set to FALSE by default in the sample script, indicating that errors are handled by the errhndl.sh scripts. Set the value to TRUE only if you want the deployment to exit when any error occurs. 6 Set the variable that defines the directory containing the DRMK system files necessary to create a Dell utility partition (DT_DRMK).
To edit the RAC configuration variables, locate the following lines in raccap.sh: DT_RAC_CAPFILE=$dt_systems/$dt_platform/raccfg.ini To edit the RAC configuration variables, locate the following lines in racrep.sh: # RAC section DT_NICCFG=10.98.8.121 set DT_RAC_CAPFILE= $dt_systems/$dt_platform/raccfg.
# RAIDCFG section DT_VD_SIZE=10480 # default size for virtual disk CAUTION: DT_MOUNT specifies the mount point of the Dell utility partition. If your RAMDRIVE, hard drive, or other device already owns this designation, mount does not override the setting and the utility partition is not created. Perform the following steps to edit the default partition configuration default values, as necessary: 1 Edit the default utility partitioning variable (DT_PARTN_UP=on), if necessary.
Editing DTK Task Scripts The task scripts called by the master batch file do not require any edits (with the following exceptions) if the default variable values are utilized in the tkenvset.sh scripts. However, if you make any changes to the default values set by the tkenvset.sh, you must make the same edits to the matching default values set in the appropriate task scripts. Locate the USER MODIFICATION REQUIRED heading in the task scripts to find the variable values you might need to edit.
raidcfg.sh The raidcfg.sh 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.sh scripts. This script uses the raidcfg.sh utility to automatically configure the detected controllers on your target system.
partcfg.sh The partcfg.sh sample script creates and populates the Dell utility partition using upinit.sh and creates the deployment partition on a specified disk. For more information about using the upinit.sh tool, See "upinit.sh" on page 122. User input is not required to run this script. The default variable values used in this script are set in the tkenvset.sh scripts. NOTE: Ensure that DT_HD is set to the required disk to be configured before you execute the partcfg.sh script.
Perform the following steps to run the syscap.sh sample script to capture BIOS and BMC configuration information in the syscfg.ini file: 1 Edit the start-up script file on your embedded Linux image to call the syscap.sh script after the network share with the prebuilt DTK directory structure is mounted. For example, add: source/opt/dell/toolkit/template/scripts /syscap.sh 2 Boot the source system into embedded Linux.
Perform the following steps to run the raccap.sh sample script to capture RAC configuration information in the raccfg.ini file: 1 Edit the start-up script file on your embedded Linux image to call the raccap.sh script after the network share with the prebuilt DTK directory structure is mounted. For example, add: source/dell/toolkit/template/scripts/raccap.sh 2 Boot the source system into embedded Linux.
Preparing the Operating System Installation Scripts NOTE: While installing Linux, ensure that you install grub in the boot partition. Otherwise, you cannot boot to the utility partition by pressing the F10 key during reboot. 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.
ks.cfg, ks-rhel5.cfg, and ks-rhel6.cfg Depending on the version of the Red Hat Enterprise Linux Server operating system, the ks.cfg, ks-rhel5.cfg, or ks-rhel6.cfg files are the default names of the answer files that you use to automate an unattended Red Hat Enterprise Linux Server installation. A sample copy of the ks.cfg/ks-rhel5.cfg/ks-rhel6.cfg files are provided as part of DTK download in the /opt/dell/toolkit/template/configs directory. The ks.cfg/ks-rhel5.cfg/ks-rhel6.
6 Copy vmlinuz from Red Hat Enterprise Linux media to the NFS Share. 7 Copy the ks.cfg file from /opt/dell/toolkit/template/configs to the NFS Share. 8 Edit the file ks.cfg. Set the NFS IP Address where Red Hat Enterprise Linux images are available and the NFS share path. 9 Run export DT_OS_DISK=/dev/sda, the disk device on which the Dell Utility partition was created. 10 Run export DT_OS_SRC=/tmp/os_src, where vmlinuz, initrd.img, and ks.cfg are available. 11 Run export DT_HD=/dev/sda.
Variables Used • DT_OS_DISK— Sets the disk on which to deploy the SUSE Linux Enterprise Server operating system. • DT_OS_SRC— Sets the location from where to copy the kernel image and initial ramdisk files. • DT_OS_PART— Sets the valid partition to install the grub files. • DT_OS_IMG_PATH— Sets the network share where the operating system files are located. • DT_SUSE_AUTOINST— Sets the network share from where the autoinst.xml file can be picked up.
When you have completed all necessary modifications of the autoinst.xml file, save the completed file in the /opt/dell/toolkit/systems/ directory. After you have successfully edited your deployment scripts, you are ready to create the deployment media and run the deployment. For instructions on creating deployment media and running a full deployment, see "Running Deployment Scripts and RPMs Using DTK and Embedded Linux" on page 129.
Preparing the Script Files for Deployment Using Embedded Linux
9 Running Deployment Scripts and RPMs Using DTK and Embedded Linux 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.
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.
6 The isolinux.cfg file is ready for PXE-booting. Copy this isolinux.cfg file into the PXE configuration folder. 7 Create your own start-up script and place it in the network share specified in your modified isolinux.cfg file. 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.
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.
For RPM-based deployment: 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 7-6. 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.
• Basic libraries and utilities for Linux to execute customized scripts • 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.
10 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 10-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.
11 Known Issues and Frequently Asked Questions 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 • Setup passwords and system passwords cannot be cleared using DTK. • The Demand-based Power Management (DBPM) option does not work on PowerEdge 1855 systems with BIOS versions earlier than A05. • 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 should 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 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 D capturing configuration information embedded Linux, 120 Windows PE, 67 deployment directory structure embedded Linux, 100 overview, 31, 89 Windows PE, 42 capturing the system BIOS & BMC configuration embedded Linux, 120 Windows PE, 67 deployment matrix embedded Linux, 86 Windows PE, 28 choosing a deployment method embedded Linux, 81 Windows PE, 25 configuration files, 11 configuring an optimally configured source system embedded Linux, 103 contents DTK embedded Linux, 93 DTK Windows PE, 34 c
E O editing DTK task scripts embedded Linux, 118 Windows PE, 65 operating system installation files embedded Linux, 101 Windows PE, 44 editing the files embedded Linux, 106 Windows PE, 55 embedded Linux contents DTK, 93 I installation prerequisites embedded Linux, 15 Windows PE, 15 installing DTK, 89, 104 embedded Linux, 89 M Master Batch File sample, 54 what is, 54 Media-Based local deployment embedded Linux, 84 Windows PE, 25 Media-Based local deployment, networking enabled embedded Linux, 82 Window
Running, 135 S running a scripted deployment embedded Linux, 135 Windows PE 2005, 75 sample configuration files embedded Linux, 95 running a scripted deployment, embedded Linux network-based deployment, 135 third-party deployment solution framework, 134 using customized embedded Linux, 133 using Dell-provided embedded Linux, 129 running a scripted deployment, using Dell-provided embedded Linux Media-based deployment, 131 Network-based deployment, 130 running a scripted deployment, Windows PE burning ISO
Windows PE, 42 UPINIT.BAT, 70 W2K8INST.BAT, 72 WININST.
