Dell EMC OpenManage Deployment Toolkit Version 6.
Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your product. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. Copyright © 2017 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries.
Contents 1 Introduction....................................................................................................................................................6 DTK Deprecation Message............................................................................................................................................... 6 What is new in this release...............................................................................................................................................
Sample scripts for deployment on Linux system....................................................................................................34 RPMs.................................................................................................................................................................................35 Documentation.................................................................................................................................................................
Creating and customizing images for Windows PE 5.1......................................................................................... 60 Integrating DTK directory structure ........................................................................................................................60 Creating a bootable media for Windows PE 5.1...................................................................................................... 61 Running the image...........................................
1 Introduction The Dell OpenManage Deployment Toolkit (DTK) includes a set of utilities, sample scripts, and sample configuration files that you can use to deploy and configure the Dell systems. You can use DTK to build script-based and RPM-based installation for deploying large number of systems on a pre-operating system environment in a reliable way, without changing their current deployment processes.
• • C6420 • R540 • R440 • R6415 • R7415 • R7425 • T440 • M640 • FC640 • T640 • C6400 Added Support for the Precision Rack System: • • PR7920 Added support for below Network Cards: • Intel Ethernet Network Adptr XXV710-DA2 • NetXtreme BCM5719/5720 1Gbps devices • NetXtreme-E BCM574xx 10Gbps/25Gbps devices • Mellanox ConnectX-4 Dual Port 100 GbE QSFP Network Adapter • Intel X550 rNDC • Intel 10GbE 4P X710 NOTE: For the list of supported operating systems and Dell servers,
Table 2. DTKTORACADM Command on Linux Operating System Valid Arguments python dtktoracadm.py or python dtktoracadm.py linux_scripts.lst debug Description On the system running Linux operating system, in the prompt type the command, where linux_scripts.lst is the input which contains the list of path to run the RACADM scripts and debug is an option which list the file status. Applicable Systems All PowerEdge 12 and later systems. The set of converted commands are available in dtktoracadm_dict.map.
Group SYSCFG Commands Equivalent RACADM Commands --solcharaccuminterval iDRAC.IPMISOL.AccumulateInterval --solbitrate iDRAC.IPMISOL.BaudRate --solprivlevel iDRAC.IPMISOL.MinPrivilege --solcharsendthreshold iDRAC.IPMISOL.SendThreshold BIOS Option Settings --HddSeq BIOS.BiosBootSettings.HddSeq Boot Settings --BootMode BIOS.BiosBootSettings.BootMode --BootSeqRetry BIOS.BiosBootSettings.BootSeqRetry --HddFailover BIOS.BiosBootSettings.HddFailover --SetBootOrderFqddn BIOS.BiosBootSettings.
Group SYSCFG Commands Equivalent RACADM Commands Processor Settings --DcuIpPrefetcher BIOS.ProcSettings.DcuIpPrefetcher --DcuStreamerPrefetcher BIOS.ProcSettings.DcuStreamerPrefetcher --LogicalProc BIOS.ProcSettings.LogicalProc --ProcExecuteDisable BIOS.ProcSettings.ProcExecuteDisable --ProcHwPrefetcher BIOS.ProcSettings.ProcHwPrefetcher --ProcVirtualization BIOS.ProcSettings.ProcVirtualization --RtidSetting BIOS.ProcSettings.RtidSetting --ProcX2Apic BIOS.ProcSettings.
Group SYSCFG Commands Equivalent RACADM Commands --sata7 BIOS.SataSettings.SataPortH --sataporta BIOS.SataSettings.SataPortA --sataportb BIOS.SataSettings.SataPortB --sataportc BIOS.SataSettings.SataPortC --sataportd BIOS.SataSettings.SataPortD --sataporte BIOS.SataSettings.SataPortE --sataportf BIOS.SataSettings.SataPortF --sataportg BIOS.SataSettings.SataPortG --sataportgmodel BIOS.SataSettings.SataPortGModel --sataportgdrivetype BIOS.SataSettings.
Group SYSCFG Commands Equivalent RACADM Commands --nmibutton BIOS.SysSecurity.NmiButton --powerbutton BIOS.SysSecurity.PwrButton Other Documents You May Need In addition to this guide, you can access the following guides available at dell.com/openmanage/manuals. See Accessing Documents From The Dell Support Site. • The Dell OpenManage Deployment Toolkit Installation Guide provides information about installing, deploying, and upgrading the DTK on supported Dell systems.
• For Dell EMC OpenManage documents — Dell.com/OpenManageManuals • For Dell EMC Remote Enterprise Systems Management documents — Dell.com/esmmanuals • For iDRAC and Dell EMC Lifecycle Controller documents — Dell.com/idracmanuals • For Dell EMC OpenManage Connections Enterprise Systems Management documents — Dell.com/ OMConnectionsEnterpriseSystemsManagement • For Dell EMC Serviceability Tools documents — Dell.com/ServiceabilityTools • a Go to Dell.com/Support/Home.
2 Pre-requisites and deployment The Deployment Toolkit (DTK) is a collection of Windows PE and Linux-based utilities and scripts that help in performing operating system tasks and deployment on Dell systems. An advanced knowledge of Windows PE and Linux is required for users who want to use the DTK utilities to perform preoperating system and postoperating system configuration tasks or to run a scripted deployment in the respective environments.
• Microsoft Windows Server 2012 Foundation, Essentials, Standard, and Datacenter editions • Microsoft Windows Server 2016 Foundation, Essentials, and Standard editions • Dell’s Precision R7920 Supported operating systems • • Microsoft Windows 8.1 (64-bit) • Microsoft Windows 10 (64-bit) Dell’s Precision R7910 Supported operating systems • Microsoft Windows 7 (32-bit and 64-bit) • Microsoft Windows 8.
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 Assessment and Deployment Kit (ADK) for Windows Server 2012 to build Windows PE 4.0 ISO image. • Windows Assessment and Deployment Kit (ADK) for Windows Server 2012 R2 and Windows 8.1 (64-bit) to build Windows PE 5.1 ISO image. • Windows Assessment and Deployment Kit (ADK) for Windows Server 2016 and Windows 10.
Drivers The following table 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 4. Drivers Required to Build Your Windows PE Environment Drivers Purpose common\hapi Essential files for DTK tools to work. common\raidcfg Essential files for raidcfg to work. winpe5.x\WINPE5.x_driverinst.bat Used to install Dell-provided drivers, from \Dell\x64\
Additional Tools Purpose Source Save in DTK location parted To create GUID Partition Table (GPT) in UEFI mode. Any system running the Linux operating system. In the PATH variable. unzip To unzip files in Linux. Any system running the Linux operating system. In the PATH variable. upimg Contains system-specific Dell utility partition files. /opt/dell/toolkit/systems, or the Dell Systems Build and Update Utility on the Dell Systems Management Tools and Documentation DVD.
Deployment DTK offers a complete set of utilities, sample scripts, and RPM packages that can be used to automate deployment on large numbers of Dell systems. This guide is designed to help you through some of the most basic planning considerations, logistical preparations, and deployment procedures to get you started using DTK to deploy Dell systems.
Deployment Methods Complexity Deployment solution Mixed framework from a third‑party vendor Advantages • • • PXE boot for Linux High • • • • • Disadvantages Must either acquire and learn to DTK can be used in context of use or have an existing third-party third-party deployment deployment solution framework. solution framework. Third-party deployment solution framework is used as the deployment transport mechanism. Tasks and scripts can be pushed to the target systems.
6 Edit the DTK sample script files that read the system configuration files to set up the system BIOS, BMC, RAID, and RAC and then install an operating system on a target system. Deployment After you have prepared all scripts, files, and utilities, you are ready to proceed with the deployment process.
How to obtain Dell utility partition files Obtain the Dell utility partition files from /opt/dell/toolkit/systems, or the Systems Build and Update Utility on the Dell Systems Management Tools and Documentation DVD.
3 Downloading DTK This section describes some of the procedures necessary to begin the deployment process, including: • Downloading and unzipping the Deployment Toolkit (DTK) components, including a comprehensive matrix of DTK components. • Setting up a directory structure to facilitate a successful deployment, including a list of the supporting components that are not included with DTK, but are needed to use DTK. • Setting up an optimally configured source system.
DTK utilities for 64-bit systems are located in the following directories: • Utilities: \Dell\x64\Toolkit\Tools • Sample scripts: \Dell\x64\Toolkit\Template\Scripts • Sample configuration files: \Dell\x64\Toolkit\Template\Configs The directory \Dell\x64\Toolkit\Systems is a placeholder that can be used for all system information that is captured using sample scripts and tools (for example, the system specific BIOS) and Baseboard Management Controller (BMC) configuration files used by the DTK utilities
Table 9. 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 required by the system superuser to perform administrative tasks. /opt The libraries, binaries, and scripts required for the toolkit to function. NOTE: The /opt/dell/srvadmin directory must be writable. /var Any run-time variable data that might be required for embedded Linux and tools to function.
Toolkit Components Purpose config.ini Configuration file used by raidcfg.exe. CAUTION: Do not edit this file. Incorrect edits might cause raidcfg.exe to fail. Configuration file used by raidcfg.exe. stsvc.ini CAUTION: Do not edit this file. Incorrect edits might cause raidcfg.exe to fail. sys.ini Configuration file used by DTK for deployment. IDRAC Configures iDRAC 6. NOTE: This feature may not be supported on all systems. Configures iDRAC7.
the Dell EMC OpenManage Deployment Toolkit Command Line Interface Reference Guide at dell.com/openmanagemanuals for complete information about the capabilities of each DTK utility. Table 11. System Utilities and Supported Files for Windows Toolkit Components Purpose pci.ids Used with syscfg to report PCI devices. racadm Wrapper script, which invokes racadm5, or racadm6 depending on the Remote Access Controller (RAC) on your system. racadm5 Configures DRAC 5 RACs. racadm6 Configures iDRAC 6.
SYSCFG equivalent RACADM commands The DTK SYSCFG deployment scripts are converted to equivalent RACADM scripts, that helps in migration to utilize RACADM in the deployment solution. Starting 12th generation of PowerEdge servers and later, selected set of SYSCFG commands are a part of the DTK sample scripts. The utility has the conversion tool for converting the SYSCFG scripts in both environments Microsoft Windows and Linux operating systems. The list of DTK sample scripts are present in \Toolkit\Tools\CONV
Group SYSCFG Commands Equivalent RACADM Commands --tmcfgnewlineseq iDRAC.IPMISerial.NewLineSeq --solcharaccuminterval iDRAC.IPMISOL.AccumulateInterval --solbitrate iDRAC.IPMISOL.BaudRate --solprivlevel iDRAC.IPMISOL.MinPrivilege --solcharsendthreshold iDRAC.IPMISOL.SendThreshold BIOS Option Settings --HddSeq BIOS.BiosBootSettings.HddSeq Boot Settings --BootMode BIOS.BiosBootSettings.BootMode --BootSeqRetry BIOS.BiosBootSettings.BootSeqRetry --HddFailover BIOS.BiosBootSettings.
Group SATA Settings 30 Downloading DTK SYSCFG Commands Equivalent RACADM Commands --ProcExecuteDisable BIOS.ProcSettings.ProcExecuteDisable --ProcHwPrefetcher BIOS.ProcSettings.ProcHwPrefetcher --ProcVirtualization BIOS.ProcSettings.ProcVirtualization --RtidSetting BIOS.ProcSettings.RtidSetting --ProcX2Apic BIOS.ProcSettings.ProcX2Apic --cpucore BIOS.ProcSettings.ProcCores --cpuspeed BIOS.ProcSettings.ProcCoreSpeed --logicproc BIOS.procsettings.LogicalProc --proc1brand BIOS.
Group SYSCFG Commands Equivalent RACADM Commands --sata7 BIOS.SataSettings.SataPortH --sataporta BIOS.SataSettings.SataPortA --sataportb BIOS.SataSettings.SataPortB --sataportc BIOS.SataSettings.SataPortC --sataportd BIOS.SataSettings.SataPortD --sataporte BIOS.SataSettings.SataPortE --sataportf BIOS.SataSettings.SataPortF --sataportg BIOS.SataSettings.SataPortG --sataportgmodel BIOS.SataSettings.SataPortGModel --sataportgdrivetype BIOS.SataSettings.
Group SYSCFG Commands Equivalent RACADM Commands --minpowercap System.Power.Cap.MinThreshold --capenable System.Power.Cap.Enable Sample scripts for deployment Sample deployment scripts and configuration files for deployment of DTK on Dell systems. Sample deployment configuration files for Windows The following table describes examples of Windows configuration files used to perform a scripted deployment. The Windows files for 64-bit supported systems are located in the following directories: • \Dell
Toolkit Components Purpose autoinst-sles11.xml Sample file used with unattended installation of SUSE Linux Enterprise Server (version 11) operating system in BIOS mode. autoinst_sles11_uefi.xml Sample file used with unattended installation of SUSE Linux Enterprise Server (version 11) operating system in UEFI mode. ks-rhel6.cfg Sample file used with unattended installation of Red Hat Enterprise Linux Server (version 6) operating system in BIOS mode. ks_rhel6_uefi.
Toolkit Components Purpose PARTCFG.BAT Creates and populates the Dell utility partition and creates the operating system partition on a specified hard drive. The script cleans out all existing partitions on your system before creating and populating the partition. RACCAP.BAT Captures Remote Access Controller (RAC) settings to a file for DRAC 4 remote access controllers. RACREP.BAT Applies (replicates) the RAC settings saved in a file to the target system. RAIDCAP.
Toolkit Components Purpose raidcfg.sh Configures all RAID controllers detected in a system. suseinst.sh Performs an unattended installation of a supported SUSE Linux Enterprise Server operating system. syscap.sh Captures BIOS and BMC configuration settings and saves them to a file. sysdrmk Used by upinit.sh to patch the boot sector. sysrep.sh Applies (replicates) BIOS and BMC configuration settings and configures the target system. tkenvset.
Drivers and Dell real mode kernel Hardware application programing interface (HAPI) drivers are essential for DTK tools to work in the embedded Linux environment. Dell Real Mode Kernel (DRMK) contains the mbr file necessary to create a bootable Dell Utility Partition.
4 DTK Seamless package The DTK Seamless package is a single installer package that carries Linux DTK RPMs (RHEL, SLES) and its dependency. Seamless package — Downloading and Installing This section describes the downloading and installing of DTK seamless package. The seamless package auto recognizes the OS type and its respective dependency during the installation and installs SYSCFG, RAIDCFG, and RACADM tools on post Linux operating system.
Non-interactive mode: In the non-interactive mode, all the available tools are installed by default. Any other option is ignored. Type the following command: ./DTKTOOLS__Linux64_.Bin [—f/--force] Once the DTK tools installation is complete, success message is displayed on the screen. To uninstall the DTK tools, run the command ./DTKTOOLS__Linux64_.Bin [-d/--delete] To view the available options, run the following command in the command line: .
5 Setting up a directory structure for deployment To perform a Deployment ToolKit (DTK)-enabled deployment, you must create a deployment directory structure on either a network share or your local workstation hard drive. The deployment directory structure is a central repository for all deployment files that can be used for network deployment and to build a bootable deployment media. It can also be used successively as a testing space.
Operating system installation files For more details on installing Windows Server and Linux operating system using DTK, see the Dell EMC OpenManage Deployment Toolkit Installation Guide available at dell.com/openmanagemanuals.
6 Preparing the script files This chapter describes the steps required to use the Deployment Toolkit (DTK) sample scripts to perform a full deployment on a target system in the Microsoft Windows PE and embedded Linux environment.
::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 WIN2K12.
Table 20. Capture Scripts for Linux Script Name Description Associated Files raccap.sh Captures RAC settings to a file for DRAC • 4. tkenvset.sh — Used by raccap.sh to inform the task scripts where to find the DTK utilities, scripts, and configuration files. racadm — Used by raccap.sh to retrieve RAC information and to configure settings. The wrapper script, racadm, invokes racadm4, racadm5, or racadm6 depending on the system configuration. syscfg— Used by raccap.sh to configure DRAC. • • raidcap.
Table 22. Replication Scripts for Linux Script Name Description Associated Files racrep.sh Applies the RAC configuration settings saved in a file to the current system. • • • sysrep.sh Applies the BIOS and BMC settings saved in a file to the current system. • • tkenvset.sh — Used by racrep.sh to inform the task scripts about where to find the DTK utilities, scripts, and configuration files. racadm — Used by racrep.sh to replicate the RAC information and to configure settings.
Table 24. Deployment Scripts For Linux Script Name Description Associated Files lininst.sh and lininst7.sh Performs an unattended installation of a supported Red • Hat Enterprise Linux operating system in BIOS and • UEFI mode. • • • • • suseinst.sh Performs an unattended • installation of a supported SUSE Linux Enterprise Server • operating system. • • • • tkenvset.sh — Used by lininst.sh to inform the task scripts about where to find the DTK utilities, scripts, and configuration files.
Script Name Description Associated Files and configured. The variables and paths specified in this file must be specified before any of the other supporting scripts can be used. RAIDCFG.BAT Configures the selected RAID controller detected in the system. • • PARTCFG.BAT Creates and populates the Dell utility partition (UP) and the operating system • partition on a specified disk. • TKENVSET.BAT — Used by RAIDCFG.
Script Name Description Associated Files upinit.sh Creates and populates the Dell utility partition in BIOS mode. • NOTE: Do not modify the upinit.sh script. • • • • • • tkenvset.sh — Used by upinit.sh to inform the task scripts about where to find the DTK utilities, scripts, and configuration files. fdisk — Used to create partitions on your disk. mbr — File necessary to create a bootable Dell utility partition. sysdrmk — Used by upinit.sh to patch the boot sector. unzip — Used by upinit.
4 Set the variable that defines the directory containing the configuration files for your Dell systems (DT_SYSTEMS). This variable is set to %DT_PATH%\Systems (Windows) or $dt_path/systems (Linux) by default in the sample script. Edit this path to add a subdirectory for the Dell system you plan to deploy. For example, $dt_path/systems/. 5 Set the variable that defines the directory containing DTK deployment scripts (DT_SCRIPTS). This variable is set to %DT_PATH% \Template\Scripts (Windows) o
In RACREP.BAT: :: RAC section set DT_NICCFG=10.98.8.121 set DT_RAC_CAPFILE=%DT_SYSTEMS%\%DT_PLATFORM%\raccfg.ini In racrep.sh: # RAC section DT_NICCFG=10.98.8.121 set DT_RAC_CAPFILE=$dt_systems/$dt_platform/raccfg.ini Specifying variables used to create disk partitions and install the Dell utility partition NOTE: If the primary deployment state (DT_PARTN) is set to OFF, the partitioning deployment state subsection is skipped. The PARTCFG.BAT (Windows) or partcfg.
In partcfg.sh in UEFI mode: DT_PARTN_UP=OFF # Default Hard Drive DT_HD=/dev/sda # PARTCFG section set DT_DP_SIZE_GPT=125 # RAIDCFG section DT_VD_SIZE=10480 # default size for virtual disk Editing the default partition configuration values Perform the following steps to edit the default partition configuration default values, as necessary: 1 Edit the default utility partitioning variable (DT_PARTN_UP), if necessary. Set this variable f you want to install the Dell utility partition.
used in these scripts are set in the TKENVSET.BAT or tkenvet.sh scripts. You can specify the IP address to configure the RAC as an optional parameter. The raccfg.ini file is generated with the RACCAP.BAT or raccap.sh sample script. For information about using the RACCAP.BATor raccap.sh sample script to capture RAC configuration information, see RACCAP.BAT Or raccap.sh. NOTE: On all PowerEdge systems, racrep.sh and sysrep.sh have duplicate functions. If you run racrep.sh followed by sysrep.
Using DTK sample scripts to capture configuration information The SYSCFG and RACADM utilities can read the source system configuration and duplicate that configuration on a target system using a sample DTK script file. These configuration files are used during a full deployment to configure the BIOS, BMC, and RAC settings on the target system.
Capturing the RAC configuration with the RACCAP or raccap.sh sample script If your system has a RAC, you can replicate the RAC configuration from the RAC of a source Dell system to an identical target Dell system with an identical RAC. NOTE: For the script to complete successfully, the source system must have access to the network share that includes the prebuilt DTK directory structure. Running RACCAP.BAT or raccap.sh To run the RACCAP.BAT or raccap.
UPINIT.BAT or upinit.sh The UPINIT.BAT or upinit.sh is a tool used to create and populate a new Dell utility partition and to upgrade or downgrade an existing 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. Upgrades or downgrades can be made only to existing Dell utility partitions to capture BIOS and BMC settings using the overwrite option.
The DT_DRIVE denotes the network drive letter to the network shared path containing the Windows Server 2012 R2 operating system source and the UNATTEND.XML (in BIOS mode) or UNATTEND_UEFI.XML file (in UEFI mode). The W2K12INST.BAT script uses the UNATTEND2K12.XML file (in BIOS mode) and UNATTEND2K12_UEFI.XML file (in UEFI mode) with SETUP.EXE utility to install the operating system files. The W2K16INST.BAT script uses the UNATTEND2K16.XML file (in BIOS mode) and UNATTEND2K16_UEFI.
The following are the variables used in grub and grub2: • DT_OS_DISK — Sets the disk to deploy the Red Hat Enterprise Linux Server 6 operating system. • DT_OS_NFS_LOC — Sets the disk to deploy the Red Hat Enterprise Linux Server 7 operating system. • DT_OS_SRC — Sets the location from where to copy the kernel image and initial ramdisk files. • DT_HD — Sets the required disk to be configured for partition. External dependencies of lininst.
NOTE: The sample files provided to install CentOS Server (version 7.x) are ks-centos7.cfg (in BIOS mode), and ks_centos7_uefi.cfg (in UEFI mode). To use the sample ks-centos7.cfg file to install CentOS Server (version 7.x) using centinst7.sh, ensure that you rename the file to ks.cfg . To use the sample ks_centos7_uefi.cfg file to install CentOS Server (version 7.x) using centinst7.sh, ensure that you rename the file to ks_uefi.cfg.
and parameters that instruct the installation utility to perform various configuration tasks. Before a full deployment can be run, edit all appropriate headings and parameters, as necessary. NOTE: After installing SUSE Linux Enterprise, change the login password by editing the user node of the root user in autoinst.xml/autoinst_uefi.xml. You can also encrypt the password file by changing false to true in false.
7 Running the deployment scripts 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.
• Windows PE or Linux, as the case may be, is installed from the media. • Network shares are mapped. • The DTK scripts execute the necessary DTK utilities from the network share or the media itself. • Configuration information is read from the network share. • The operating system is installed from a network share. This installation may happen after your system reboots.
Creating a bootable media for Windows PE 5.1 To create a bootable media: 1 Click Start and navigate to All Programs > Microsoft Windows ADK. 2 Click Windows PE Tools Command Prompt to open a command prompt window. 3 Navigate to C:\program files\Windows AIK\Tools\amd64 directory on the system. 4 Execute the script: WINPE5.0_driverinst.
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. NOTE: For more details on how to create a customized version of a single Windows PE bootable media that works across all Dell supported systems and provides an underlying Networking stack, see Running The Deployment Scripts.
Network based deployment for systems running windows For Windows PE environments, deployment using Remote Installation Services (RIS) is recommended. For details, see the Microsoft RIS documentation. You can also use any other deployment tool such as Automated Deployment Services (ADS).
4 Edit the configuration file (isolinux.cfg for BIOS or efidefault for UEFI mode) by providing the following options: • IP address of the network share • Share path of the network share • Name of your startup script The isolinux.cfg/efidefault file is ready for PXE-booting. 5 Copy isolinux.cfg file into the PXE configuration folder. 6 Create your own start-up script and place it in the network share specified in your modified isolinux.cfg/efidefault file.
NOTE: Your scripts must also take care of copying miscellaneous items to unlock the media, so that the media can be mounted and ejected as per the operating system’s installation process. 4 In /mnt/cdrom/isolinux/isolinux.cfg (for BIOS mode) or in /mnt/cdrom/EFI/BOOT/dtk_grub.cfg (for UEFI mode), edit the cd install section to point to your customized start-up script. In other words, add the share_script option and then use mkisofs to create the ISO image as follows: mkisofs -o output.
Installing DTK RPMs using DTK tools To install DTK RPMs using DTK tools: 1 Mount the DTK media at /mnt/cdrom. 2 Navigate to the /mnt/cdrom/SYSMGMT/dtktools/ directory. NOTE: The /mnt/cdrom/SYSMGMT/dtktools directory contains all DTK RPMs and the dependency RPMs. 3 Install the required DTK RPMs using dtktools-setup.sh. NOTE: To resolve the RPM dependency-related issues, install the missing RPMs from the /mnt/cdrom/SYSMGMT/ srvadmin/linux/RPMS directory.
Using a third-party deployment solution framework for systems running Linux You can use DTK with any existing third-party deployment solution framework that provides a PXE booting infrastructure that can be used as transport mechanism for the DTK utilities. Because each third-party deployment framework is unique, these solutions are beyond the scope of this document.
8 Running Dell update packages on systems running embedded Linux You can run the Dell Update Packages in embedded Linux environments on supported Dell systems.
Update Packages Dependency Dependencies Available On SCSI drivers Kernel RAC 5 Instrumentation drivers /mnt/cdrom/tools iDRAC Instrumentation drivers /mnt/cdrom/tools PowerVault 220S SCSI drivers Kernel SAS SAS drivers Kernel Any Update Package RPMs Linux media or any open source website sysvinit grep sed awk less fmt tar.gz compat-libstdc proc-mail libxml2 After you have met all the dependencies, run the update packages in your customized embedded Linux environment.
9 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. Topics: • Known issues • 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.
Frequently asked questions The following questions are organized by DTK utility or other function. General deployment questions Q: While running SYSCFG.EXE on a Windows PE image, the SYSCFG.EXE tool silently fails. A: Ensure that you have built your Windows PE image with the /WMI option. For more details, see Running The Deployment Scripts.
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 non-zero. If the enclosure has a non-zero value, then all three numbers (channel, target, and enclosure) have to be included on the command line.
Q: What is the minimum configuration needed to support BMC Platform Event Filtering? A: You must enable LAN-channel access pefalerting and ensure that you set the BMC IP address and Gateway values for alerting. Q: I installed the factory defaults for the BMC of my system. Then, I enabled BMC user ID 3. What is the username for this user ID? A: The default username for user IDs 3 to 10 is NULL. Q: Can I use this NULL username to remotely log in to a BMC of a system? A: No.
Q:How to delete the Unavailable: RHEL_DTK_UEFI and Unavailable: SLES_DTK_UEFI entries displayed on the F11 UEFI boot manager? A: Do the following to delete the entries: 1 Identify the boot entry number (for example, BootXYZ) of the entry to be deleted: Run efibootmgr from the command line. 2 Delete the entry: Run efibootmgr -b XYZ –B Q: Is Fiber channel cards work with DTK pre-boot environment? A: No, there is no ether-net feature and also firmware update may not work.
