Dell OpenManage Deployment Toolkit 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. © 2010 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 11 . . . . . . . . . 12 . . . . . . . . . . . . . . . . . . . . . . . 14 Prerequisites and Requirements . . . . . . . . . . . . Supported Operating Systems to Run DTK Utilities . . . . . . . . . . . . . Supported Systems . 14 . . . . . . . 14 . . . . . . . . . . . . . . . . 15 Supported BIOS Firmware Versions . . . . . . . . 15 Installation Prerequisites . . . . . . .
2 Choosing a Microsoft Windows PE-Based Deployment Method . . . . . . . . 25 Choosing a Deployment Method for Microsoft Windows PE . . . . . . . CD-Based Local Deployment . . . . . . . . . . . 25 . . . . . . . . . . . 25 CD-Based Local Deployment With Networking Enabled . . . . . . . . . . . . . . . . 26 . . . . . . . . . . 28 . . . . . . . . . . . 28 Using a Third-Party Deployment Solution Framework . . . . . .
Configuring a Source System RAC Configuration 4 . . . . . . . . . . . . . . 49 . . . . . . . . . . . . . . . . . 50 Preparing the Script Files for Deployment Using Microsoft Windows PE . . . . . . . . . . . . . . 51 Using the Sample DTK Scripts to Run a Full Deployment in Windows PE . . . . . . . . The Master Batch File (DEPLOY.BAT) . . . . . . 52 . . . . . . . 52 Editing the Sample Batch Files to Perform a Complete System Deployment in Windows PE . . . . . 53 . . . . . . . . . . . 53 . . .
5 Running Deployment Scripts Using DTK and Microsoft Windows PE Creating and Customizing Images for Windows PE 2.0 . . . . . . . . . . . 71 . . . . . . . . . . Integration of DTK Directory Structure in Windows PE Build . . . . . . . . . . Creating a Bootable CD . . . . . . 71 . . . . . . . . . . . . . . 72 . . . . . . . . . . 73 . . . . . . . . . . . 73 Running the Windows PE 2.0 Image CD-Based Local Deployment . Creating and Customizing Images for Windows PE 3.0 . . . . . . . . . . . . . . .
Preparing the Directory Structure for Deployment in Embedded Linux Upgrading Your DTK Version . . . . . . . . . . . . 85 . . . . . . . . . . . . . . . . . . . . . . 89 System Utilities and Supporting Files Sample Configuration Files . . . . . . . . 89 . . . . . . . . . . . . 91 . . . . . . . . . . . . . . . . . . . 92 . . . . . . . . . . . . . . . . . . . . . . . . 92 Sample Scripts RPMs Documentation 93 . . . . . . . . . . . . . . . . . . .
Editing the Sample Batch Files to Perform a Complete System Deployment in Embedded Linux . . . . . . . . . . . . . . . . . . . . . 102 Using the Sample Scripts in a Scripted Deployment . . . . . . . . . . . . . . . . 102 Editing the tkenvset.sh Script . . . . . . . . . . . 109 . . . . . . . . . . . . . . . . . . . . . 109 tkenvset.sh Editing DTK Task Scripts . . . . . . . . . . . . . . Using DTK Sample Scripts to Capture Configuration Information in Embedded Linux . . . . .
Using a Third-Party Deployment Solution Framework . . . . . . 129 . . . . . . . . . . 10 Running Dell Update Packages in Embedded Linux . . . . . . . . . . . . . . . . . 131 Running Update Packages in Dell-Provided Embedded Linux . . . . . . . . . . . . . . Running Update Packages in Customized Embedded Linux . . . . . . . . . . . . . . . . . 131 . . . . . 131 11 Known Issues and Frequently Asked Questions Known Issues 135 . . . . . . . . . . . . . . . . . . . . . . General Issues 135 . . . . .
Contents
1 Introduction The Dell OpenManage Deployment Toolkit (DTK) includes a set of utilities for configuring and deploying Dell systems. You can use DTK to build scriptbased and RPM-based installation for deploying large number of systems in a reliable way, without changing their current deployment processes. In addition to the command line utilities used to configure various system features, DTK also provides sample scripts and configuration files to perform common deployment tasks and documentation.
Information Organization in this Guide While DTK is designed to be flexible and expandable, this guide is limited to providing general, best practices procedures that focus on the basic tasks for a successful deployment. You may find other alternative solutions to the best practices guidelines described in this guide and many additional uses for DTK utilities beyond what is covered in this guide or in the Dell OpenManage Deployment Toolkit Command Line Interface Reference Guide.
Table 1-1.
This guide also includes a ""Known Issues and Frequently Asked Questions" on page 135" section. What’s New The new features for this release include: • Support for Red Hat Enterprise Linux Server version 6 (64-bit) • Support for separate DTK RPM package in DTK Linux ISO image Prerequisites and Requirements The DTK is a collection of Windows PE and Linux-based utilities and scripts that assist in performing pre-operating system tasks and deploying Dell systems.
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 on the Dell Support website in the or the Dell Systems Software Support Matrix on the Dell Support website at support.dell.com/manuals.
Before installing DTK components for embedded Linux, ensure 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 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: 16 • Adv
• DTK documentation: – Dell OpenManage Deployment Toolkit Command Line Interface Reference Guide – Dell OpenManage Deployment Toolkit User’s Guide – The Dell Systems Management Tools and Documentation DVD NOTE: You can also obtain the latest drivers from the Dell Support website at support.dell.com.
– Dell OpenManage Deployment Toolkit Command Line Interface Reference Guide – Dell OpenManage Deployment Toolkit User’s Guide – The Dell Systems Management Tools and Documentation DVD NOTE: You can also obtain the latest drivers from the Dell Support website at support.dell.com.
Deployment Methods Dell systems can be deployed using several different methods. The most common method is using the Systems Build and Update Utility 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 and sample scripts, and RPM packages that can be used to automate deployment of large numbers of Dell systems.
5 Generate a system BIOS, BMC, RAID, and/or RAC configuration profile from the optimally configured source system. (This source system will be the master server that will be used to replicate settings onto target servers.) You can obtain the system BIOS, BMC, RAID, and/or RAC configuration files by booting from DTK Windows PE ISO image and running the SYSCAP.BAT, RAIDCAP.BAT, and RACCAP.BAT scripts. Then, copy the generated configuration files to a read/write share onto the workstation.
6 Create an operating system answer file that contains unattended operating system software installation information. Deploying After you have prepared all scripts, files, and utilities, you are ready to proceed with the deployment process. While there are many ways to use DTK utilities to deploy Dell systems, this guide focuses on the two most common methods for Windows PE and embedded Linux: CD-based deployment (local) and network-based deployment (remote).
Deployment Using Removable Boot Media Without a Network Connection (CD-Based) 1 Create a deployment CD containing a bootable image with the appropriate drivers. The CD must also include the complete deployment directory structure, which contains all DTK utilities, scripts, and configuration files, an operating system installation answer file, and the required operating system installation files and drivers. 2 Insert the bootable CD into the CD drive of the system to be deployed (the target system).
• The Dell OpenManage Installation and Security User's Guide provides additional information about performing an unattended installation of Server Administrator on systems running supported Windows, Red Hat Enterprise Linux Server, and SUSE Linux Enterprise Server operating systems.
• 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.txt file, which is available as part of DTK download and on the Dell Support website at support.dell.com, provides the latest available information for the installation and operation of DTK components.
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 CD. This method does not provide a writable media, making it necessary to use predefined and tested configuration files.
Bootable Windows PE CD With Networking Enabled This process includes: • Creating a bootable Windows PE CD 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 a Automated Deployment Services (ADS) booting infrastructure for Windows Deployment Services (WDS) booting infrastructure 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 CD 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 • Setting up an optimally configu
Perform the following steps to extract DTK components to a workstation running Windows: 1 Download the DTK file DTK3.X-WINPE-XX.exe from the Dell Support website at support.dell.com and save it anywhere on your system. 2 After the file downloads, double-click the file. 3 Click OK. 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.
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
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. Incorrect edits might cause RAIDCFG.EXE to fail. mr2kserv.exe Service that needs to be running for RAIDCFG.EXE to function. IDRAC Configures iDRAC6. NOTE: This feature may not be supported on all systems. pci.ids Used with SYSCFG.EXE to report PCI devices. RAC 4 Configures Dell Remote Access Controller (DRAC) 4/P and DRAC 4/I.
Table 3-1. System Utilities and Supporting Files (continued) Toolkit Components Purpose SyscfgErrorCodes.txt Lists the error codes and messages for the SYSCFG.EXE tool. sysdrmk.exe Used by UPINIT.BAT to patch the boot sector and Master Boot Record (MBR). UpinitErrorCodes.txt Lists the error codes and messages for UPINIT.BAT. version.txt Contains the DTK version in use. Sample Configuration Files Table 3-2 describes examples of configuration files used to perform a scripted deployment.
Table 3-2. Sample Configuration Files (continued) Toolkit Components Purpose Location UNATTEND. XML Sample answer file used in Windows setup for unattended installation of Microsoft Windows operating system. Move to the directory \Toolkit\Systems\ after the UNATTEND.XML file is edited. STARTNET. CMD Sample script used by Windows PE 2.0 when it boots up. \Toolkit\template\Configs WINBOM.INI Sample file used to start the racsvc and mr2kserv services. \Toolkit\template\Configs WINPEOEM.
Sample Scripts Table 3-3 lists sample scripts of those 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.
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 a 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 built during the test. 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. 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 CD for Windows PE 2.0. www.microsoft.com Windows AIK for Windows 7 to build Windows PE 3.0 Create a bootable CD for Windows PE 3.0. www.microsoft.com upimg.bin Contains system-specific \Toolkit\Systems, the Dell Dell utility partition Support website at files. support.dell.
The deployment directory structure consists of the following files: • DTK utilities and files • System-specific directories • Operating system installation files directories NOTE: Do not create your DTK directory structure on a NetWare network volume. DTK network-based deployment is not supported from mapped NetWare systems. DTK Utilities and Files All necessary DTK files are provided as part of the initial installation.
Figure 3-2.
Operating System Installation Files 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 extracted WinPE toolkit to os_deploy\Dell on the management station. 4 Copy i386 folder from the Windows Server 2003 operating system CD to os_deploy\W2K3SRC on the management station.
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 in os_deploy\Dell\x32\toolkit\systems\PER515\$OEM$.NET\textmo de folder.
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. 17 Reboot the target system once you are at the command prompt and the system starts booting to the hard drive for operating system installation.
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. X:\Dell\Toolkit\Tools>net use z: \\\W2K8_deploy 10 From your system, run TKENVSET.BAT under \Toolkit\template\scripts. 11 On your system, set the environment variable DT_DRIVE=Z:. 12 Navigate to Toolkit\template\scripts and run W2K8INST.BAT. 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 64" 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 Script Files for Deployment Using Microsoft Windows PE 4 This section describes the steps required to use the Deployment Toolkit (DTK) sample scripts to perform a full deployment of 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.
Using the Sample DTK Scripts to Run a Full Deployment in Windows PE The Master Batch File (DEPLOY.BAT) 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.
***************************************************** :: 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 to a file for DRAC 4. RACCAP.BAT to inform the 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 BMC configuration 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 Performs an • TKENVSET.BAT — Used by unattended installation W2K8INST. of supported Windows BAT to inform the task scripts Server 2003 operating where to find the DTK systems. utilities, scripts, and configuration files. • 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 configuration files. detected in the system. • RAIDCFG.EXE — Used by RAIDCFG.BAT to retrieve RAID information and to configure settings. PARTCFG.BAT Creates and populates • TKENVSET.BAT — Used by PARTCFG.
TKENVSET.BAT Example Editing The majority of the 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 62." 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.
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 should be no need to edit this default setting. If you have made any modifications to the sample scripts or to the suggested directory structure, you must confirm that raccfg.ini is correctly named and that the path is correctly set for your deployment. To edit the RAC configuration variables, locate the following lines in RACCAP.
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. If your RAMDRIVE, hard drive, or other device already owns this designation, mount will not override the setting and the utility partition will not be created.
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. 6 If the DT_PART_UP variable is set to ON, edit the default variable value for the utility partition installation package location (DT_UP_IMAGE=%DT_SYSTEMS%\UPIMG.BIN), if applicable. You should have already copied the UPIMG.BIN file to the proper directory, as instructed in ""Preparing the Directory Structure for Deployment in Microsoft Windows PE" on page 31.
The raccfg.ini file is generated with the RACCAP.BAT sample script. See "RACCAP.BAT" on page 66 for information about using the RACCAP.BAT sample script to capture RAC configuration information. RAIDCFG.BAT The RAIDCFG.BAT sample script configures RAID controllers detected on the system. User input is optional to run this script. The parameter is a name or path to a log file. This parameter is not set to any value by default, and no log file is generated.
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. (See "UPINIT.BAT" on page 67 for more information about using the UPINIT.BAT tool.) 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.
the SYSCFG.EXE utility to retrieve BIOS and BMC configuration settings from the source system and to save the settings in a file named syscfg.ini in the \Toolkit\Systems\ directory. Perform the following steps to run the SYSCAP.BAT 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 to call the SYSCAP.BAT script after the network share with the prebuilt DTK directory structure is mounted.
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 in the script 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. See "UNATTEND.TXT" on page 68 for more information about preparing the UNATTEND.TXT file. 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.
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.XML file is provided as part of the DTK download in the \Toolkit\Template\Configs directory. UNATTEND.XML contains the headings and parameters that instruct Windows Setup to perform various configuration tasks. In UNATTEND.
5 Running Deployment Scripts Using DTK and Microsoft Windows PE This section 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.
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.bat with two required arguments: and . For example: VPE_driverinst.bat Where is the destination path to create the directory structure for Win PE 2.0and is the path to Dell drivers in the extracted DTK toolkit. For example: VPE_driverinst.
You can use any CD burning software to burn the image onto a CD. After burning the ISO image, ensure that it boots from the CD drive for all the supported Dell systems you plan to deploy. After it boots, you are advised to test all the tools and scripts on these systems to ensure that the integration went well and there are no issues with hardware components not being recognized. Running the Windows PE 2.
2 Execute WINPE3.0_driverinst.bat with two required arguments: and . For example: WINVPE3.0_driverinst.bat is the path to Dell drivers in the extracted DTK toolkit. is the destination path to create the directory structure for Windows PE 3.0. For example: WINPE3.0_driverinst.bat C:\winpe_30 C:\DELL\x64\DRIVERS This will pre-install the Dell drivers into winpe.wim.
1 Boot the target system with the bootable deployment CD. 2 Execute the master batch file, which calls individual task scripts and utilities from the network share to complete the deployment process. Using a Third-Party Deployment Solution Framework You can use DTK with any existing third-party deployment solution framework that provides a Automated Deployment Services (ADS) booting infrastructure that can be used as the transport mechanism for DTK utilities.
Running Deployment Scripts Using DTK and Microsoft Windows PE
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.
system—the space on a network share can be very large, and a single set of utilities and scripts can be accessed by many systems, making the deployment process easy to manage. After a network drive is mapped from a target system to a network share, all of the utilities and scripts are available to use. The master deployment script on the network share can be called from the bootable CD to perform a task or multiple tasks on the target server.
This deployment method is the easiest to assemble, but is the least flexible. Any change to the system configuration, for example, requires the creation of a new bootable CD. This method does not provide a writable media making it necessary to use predefined and tested configuration files. Creating a Bootable CD Bootable CDs can be created using any commonly available CD burning software in a two-part process that requires a self-bootable ISO image with drivers that load from system files.
Creating a Customized Bootable CD See "Running Deployment Scripts and RPMs Using DTK and Embedded Linux" for details on how to create a customized version of a single embedded Linux image that can work across all Dell systems. Using DTK Utilities and Scripts From a Customized Bootable CD After the customized bootable embedded Linux CD is created, IT administrators can take advantage of the sample scripts to automate the entire deployment process.
Table 6-1. Deployment Method Matrix (continued) Deployment Methods Complexity Remote Moderate deployment over a network (bootable embedded Linux CD 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.
Choosing an Embedded Linux-Based Deployment Method
7 Preparing the Directory Structure for Deployment in Embedded Linux 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 so
Figure 7-1. CD Directory Structure Table 7-1 describes the files, components, and other contents of the mounted CD. Table 7-1. Mounted CD Contents Contents Details Location dchipm32.ini Configuration file for the instrumentation software. /opt/dell/toolkit/lib/bin docs Contains: /mnt/cdrom/docs • Command Line Interface Reference Guide • User’s Guide LICENSING Contains all the licenses for the open source components used in this CD.
Table 7-1. Mounted CD Contents (continued) Contents Details Location sa.2 Initial RAM disk containing the embedded Linux component and DTK tools. /mnt/cdrom/isolinux RPMs Contains DTK RPMs and dependecy 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.sh Contains the basic setup for raidcfg /mnt/cdrom/tools to work.
Boot the CD onto 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.
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. racadm Wrapper script which invokes racadm4, racadm5, or racadm6 depending on the remote access controller (RAC) on your system. racadm4 Configures DRAC 4/P and DRAC 4/I RACs. racadm5 Configures DRAC 5 RACs. racadm6 Configures iDRAC6 NOTE: This feature may not be supported on all systems. racadmErrorCodes.
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. NOTE: All configuration files are provided as examples only. These sample configuration files must be edited before they can be used in any deployment tasks. Table 7-4. Sample Configuration Files Toolkit Components Purpose autoinst.
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.
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. Documentation Table 7-7 describes documents containing reference information for each DTK utility and instructions for using DTK utilities and sample scripts. Documentation can be found at mnt/cdrom/docs.
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 DTK utilities and its sample scripts. Table 7-8. Supporting Tools and System Files Additional Tools Purpose Source Save in DTK location mkfs.
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 CD or /toolkit /systems NOTE: For legacy operating on the Systems Build 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 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.
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. See "Using DTK Sample Scripts to Capture Configuration Information in Embedded Linux" for instructions on using the sample DTK scripts, syscap.sh and raccap.sh, to generate SYSCFG and RAC configuration files that are used to configure the target system.
How to Obtain Dell Utility Partition Files Obtain the Dell utility partition files from /opt/dell/toolkit/systems, the Dell Support website 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 section describes the steps required to use the Deployment Toolkit (DTK) sample scripts to perform a full deployment of a target system in the embedded Linux environment. There are four main tasks: • Writing the master deployment file and editing the tkenvset.
Editing the Sample Batch Files to Perform a Complete System Deployment in Embedded Linux Using the Sample Scripts in a Scripted Deployment 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 of the target system.
Table 8-1. Capture Scripts Script Name Description Associated Files raccap.sh Captures RAC settings • tkenvset.sh — Used by to a file for Dell raccap.sh to inform the task Remote Access Conscripts where to find the DTK troller (DRAC) 4. utilities, scripts, and 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. racadm is the 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 Performs an unat• tkenvset.sh — Used by tended installation of a lininst.sh to inform the task supported Red Hat scripts where to find the DTK Enterprise Linux utilities, scripts, and Server operating sysconfiguration files. tem. • grub — Used to install the operating system in conjunction with the unattended answer file.
Table 8-3. Deployment Scripts 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 operconfiguration files. ating system. • 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 specified 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 raidcfg.
Table 8-4. Other Scripts 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 configuration files. specified disk. The 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 Script Name Description Associated Files upinit.sh • tkenvset.sh — Used by upinit.sh to inform the task scripts where to find the DTK utilities, scripts, and configuration files. Do not make any modifications to the upinit.sh • fdisk — Used to create partitions on your disk. script. Creates and populates the Dell utility partition. • 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 will be handed by the errhndl.sh scripts. Set the value to TRUE only if you want the deployment to exit on any error. 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 will not override the setting and the utility partition will not be 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. (See "upinit.sh" for more information about using the upinit.sh tool.) 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 Red Hat Enterprise Linux Server Operating Systems The lininst.sh script is used to install supported Red Hat Enterprise Linux Server operating systems. NOTE: While installing Linux, ensure that you install grub in the boot partition. Otherwise, you will not be able to boot to the utility partition by pressing the F10 key during reboot. lininst.sh The lininst.
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.
4 Mount your NFS Share to /tmp/os_src. 5 Copy the file initrd.img for RHEL to the NFS Share. 6 Copy vmlinuz from RHEL 1st CD 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 RHEL 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 available.
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. 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.
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 your deployment media and run your deployment. For instructions on creating deployment media and running a full deployment, see "Running Deployment Scripts and RPMs Using DTK and Embedded Linux.
Preparing the Script Files for Deployment Using Embedded Linux
9 Running Deployment Scripts and RPMs Using DTK and Embedded Linux This section 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.
NOTE: When you create a bootable CD, this image is supplied to the CD burning software along with the complete deployment directory structure, which includes all necessary supporting files to perform the deployment. The CD burning software creates a self-bootable CD when the CD is booted. 3 Set up the Trivial File Transfer Protocol (TFTP) services and the Dynamic Host Configuration Protocol (DHCP) services on your network to boot the target system using Pre-Boot Execution Environment (PXE).
NOTE: When you create a bootable CD, this image is supplied to the CD burning software along with the complete deployment directory structure, which includes all necessary supporting files to perform the deployment. The CD burning software creates an image of the self-bootable ISO image and the deployment files on the CD. 3 Extract the contents of the ISO image to a folder on your hard drive. 4 Copy your custom scripts into the folder you created in step 3.
6 Copy the directory structure created on your work station into the root folder that you created in step 3. This folder contains DTK CD, files necessary for operating system installation, and files required for replication. 7 Burn the contents of the folder you created in step 3 to a CD. (Use the isolinux utility to make the CD bootable.) 8 Your ISO image is ready for booting.
• Drivers for all your hardware installed in your embedded Linux (from the Dell Support website at support.dell.com) • Serial port configuration utilities (setserial and stty) for racadm • Installed and working instrumentation drivers (from /mnt/cdrom/tools) • Point-to-Point Protocol (PPP) tools • Basic libraries and utilities for Linux to execute customized scripts • DTK tools and utilities extracted from the embedded Linux CD ( /mnt/cdrom/tools/dell.tar.gz) • Necessary entries in the ld.so.
Running Deployment Scripts and RPMs Using DTK and Embedded Linux
10 Running Dell Update Packages in Embedded Linux This section 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 the Dell Support website at 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 PERC /etc/dataeng /mnt/cdrom/tools megaraid driver 2.4.2.0 /mnt/cdrom/tools SCSI drivers Kernel Instrumentation drivers /mnt/cdrom/tools racser4.
After ensuring that you have met all the dependencies, run the update packages in your customized embedded Linux environment as follows: 1 Obtain the required update packages from the Dell Server Updates DVD or from the Dell Support website at support.dell.com. 2 Store the update packages on a network share. 3 Mount the network share where you stored the update packages and run the individual packages.
Running Dell Update Packages in Embedded Linux
11 Known Issues and Frequently Asked Questions This section 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.
• 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. If the UA USB ports are not set to All Ports On and you try to configure BIOS setting for the internal USB port using SYSCFG, the configuration will appear to be successful but the changes will not take effect after the next reboot.
the remote access controller (RAC) IP addresses and BIOS asset tags). There are many options available to optimize this process and it is suggested that you conduct an Internet search for available tools. Q: When I change my hard drive controller from SCSI to RAID (or RAID to SCSI), the system prompts me for confirmation during POST. How can I stop this from happening? A: Use the --noraidprompt option with the --embscsiraid option to prevent the system from prompting during POST.
A: The nexus used to display array disks is "channel:target:lun." The Logical Unit Number (LUN) is always "0." The channel and the target IDs are necessary to identify array disks when dealing with SCSI devices. When dealing with SAS devices, the array disk location is displayed as "channel:target:enclosure." It is possible to have the enclosure value as nonzero. If the enclosure has a non-zero value, then all three numbers (channel, target, and enclosure) have to be included on the command line.
For PERC 4 (except PERC 4/IM) controllers: • RAID 0: 10MB • RAID 1: 10MB • RAID 5: 10MB For PERC 5 controllers: • RAID 0: 100MB • RAID 1: 100MB • RAID 5: 100MB For PERC 6 controllers: • RAID 0: 100MB • RAID 1: 100MB • RAID 5: 100MB • RAID 6: 100MB • RAID 60: 100MB Q: Why can’t I see any controllers using RAIDCFG? A: Ensure that the RAID controller(s) can be seen in the BIOS during POST. If the BIOS does not detect the controller, then RAIDCFG will also not detect it.
SYSCFG Questions Q: Can I use the SYSCFG utility to configure Point-to-Point Protocol (PPP) over the serial port to my access my RAC? A: No. The baseboard management controller (BMC) firmware does not support PPP configurations for the serial port. Q: The SYSCFG utility --lancfgparams option has suboptions that configure the IP address, Gateway, and Subnet Mask for the system BMC. There is also a MAC address. Are these the same as the managed system’s operating system network parameters? A: No.
A: Set the --serialcomm option value to enableconred. For example, syscfg -serialcomm=enableconred. Embedded Linux Questions Q: After installing Linux, I am not able to boot to the utility partition by pressing the F10 key during reboot. A: Recreate the utility partition using the upinit.sh script and install grub in the boot partition. Q: When booting DTK through PXE, my system displays error messages, unknown behavior, and also leads to a kernel panic sometimes.
A: Always use initrd for the Red Hat Enterprise Linux Server installation from the Dell Systems Build and Update Utility available on the path server_assistant/drivers on the Dell Systems Management Tools and Documentation DVD. If the initrd is not available for your operating system, try the latest update of Red Hat Enterprise Linux Server. Otherwise, you might need to prepare driver disks for your network or disk controller.
Index C capturing configuration information embedded Linux, 116 Windows PE, 64 capturing the system BIOS & BMC configuration embedded Linux, 116 Windows PE, 64 CD-Based local deployment embedded Linux, 79 Windows PE, 25 CD-Based local deployment, networking enabled embedded Linux, 78 Windows PE, 26 choosing a deployment method embedded Linux, 77 Windows PE, 25 configuration files, 11 configuring an optimally configured source system embedded Linux, 99 contents DTK embedded Linux, 89 DTK Windows PE, 34 creat
embedded Linux contents, 89 installing, 85, 100 O DTK prerequisites and requirements, 14 operating system installation files embedded Linux, 97 Windows PE, 44 E overview deploying, 21 preparing for deployment, 19 editing DTK task scripts embedded Linux, 114 Windows PE, 62 P DTK deployment overview, 19 editing the files embedded Linux, 102 Windows PE, 53 embedded Linux contents DTK, 89 I installation prerequisites embedded Linux, 16 Windows PE, 15 installing DTK, 85, 100 embedded Linux, 85 M Maste
configuring, 50 Running, 131 running a scripted deployment embedded Linux, 131 Windows PE 2005, 71 running a scripted deployment, embedded Linux network-based deployment, 131 third-party deployment solution framework, 129 using customized embedded Linux, 128 using Dell-provided embedded Linux, 125 running a scripted deployment, using Dell-provided embedded Linux CD-based deployment, 126 Network-based deployment, 125 running a scripted deployment, Windows PE burning ISO image on a CD, 73-74 CD-Based local de
embedded Linux, 96 Windows PE, 42 UNATTEND.TXT, 68 UPINIT.BAT, 67 W2K8INST.BAT, 69 WININST.
