Dell EMC OpenManage Deployment Toolkit Version 6.1.
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. © 2018 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....................................................................................................33 RPMs.................................................................................................................................................................................34 Documentation.................................................................................................................................................................
Creating and customizing images for Windows PE 5.1......................................................................................... 59 Integrating DTK directory structure ........................................................................................................................59 Creating a bootable media for Windows PE 5.1..................................................................................................... 59 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.
– Mellanox 2port 25GE MEZZ Yondu • Support Matrix for the controller card: Table 1.
Table 4. SYSCFG equivalent RACADM commands Group SYSCFG Commands Equivalent RACADM Commands iDRAC Settings lcp --dnsdhcp iDRAC.IPv4.DNSFromDHCP lcp --domainname iDRAC.NIC.DNSDomainName lcp --dnsracname iDRAC.NIC.DNSRacName lcp --dnsregisterrac iDRAC.NIC.DNSRegister --idractype iDRAC.Info.Type -z legacy --autoneg iDRAC.NIC.Autoneg --gateway iDRAC.IPv4.Gateway --ipaddress iDRAC.IPv4.Address --macaddress iDRAC.NIC.MACAddres --nicselectionfailover iDRAC.NIC.Failover --subnetmask iDRAC.
Group Integrated Devices Memory Settings Miscellaneous Settings Processor Settings SYSCFG Commands Equivalent RACADM Commands --SetBootOrderFqddn BIOS.BiosBootSettings.SetBootOrderFqddn --SetLegacyHddOrderFqddn BIOS.BiosBootSettings.SetLegacyHddOrderFqddn --EmbVideo BIOS.IntegratedDevices.EmbVideo --IoatEngine BIOS.IntegratedDevices.IoatEngine --IntegratedNetwork1 BIOS.IntegratedDevices.IntegratedNetwork1 --IntegratedNetwork2 BIOS.IntegratedDevices.
Group SATA Settings 10 Introduction SYSCFG Commands Equivalent RACADM Commands --cpuspeed BIOS.ProcSettings.ProcCoreSpeed --logicproc BIOS.procsettings.LogicalProc --proc1brand BIOS.procsettings.Proc1Brand --proc1id BIOS.procsettings.Proc1Id --proc1l2cache BIOS.procsettings.Proc1L2Cache --proc1l3cache BIOS.procsettings.Proc1L3Cache --proc1numcores BIOS.procsettings.Proc1NumCores --proc2brand BIOS.procsettings.Proc2Brand --proc2id BIOS.procsettings.Proc2Id --proc2l2cache BIOS.
Group SYSCFG Commands Equivalent RACADM Commands --sataportgdrivetype BIOS.SataSettings.SataPortGDriveType --sataportgcapacity BIOS.SataSettings.SataPortGCapacity --sataporth BIOS.SataSettings.SataPortH --sataporthmodel BIOS.SataSettings.SataPortHModel --sataporthdrivetype BIOS.SataSettings.SataPortHDriveType --sataporthcapacity BIOS.SataSettings.SataPortHCapacity --sataporti BIOS.SataSettings.SataPortI --sataportimodel BIOS.SataSettings.SataPortIModel --sataportidrivetype BIOS.
• TheDell OpenManage Installation Guides provides additional information about performing an unattended installation of Server Administrator on systems running supported Windows, Red Hat Enterprise Linux Server, SUSE Linux Enterprise Server, and Citrix Xen Sever operating systems. • The Dell Systems Software Support Matrix provides information about the various Dell systems and the operating systems supported by these systems.
– Serviceability Tools – Dell Client Command Suite – Connections Client Systems Management d • To view a document, click the required product version. Using search engines: – Type the name and version of the document in the search box. Contacting Dell NOTE: If you do not have an active Internet connection, you can find contact information on your purchase invoice, packing slip, bill, or Dell product catalog. Dell provides several online and telephone-based support and service options.
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 2016 Foundation, Essentials, and Standard editions For Linux, the DTK utilities support deploying the following operating systems in BIOS and UEFI mode: • SUSE Linux Enterprise Server 12 SP3 (64-bit) • Red Hat Enterprise Linux 7.5 (64-bit) You can install the DTK Linux RPM utilities on the following operating systems in BIOS and UEFI mode: • SUSE Linux Enterprise Server 12 SP3 (64-bit) • Red Hat Enterprise Linux 7.
• Working knowledge of Microsoft Remote Installation Services (RIS) and Automated Deployment Services (ADS) (including setting up of RIS and ADS environments) or any other third-party deployment system or tool for Windows PE. • Working knowledge of Windows Deployment Services (WDS) or any other third-party deployment system or tool for Windows PE.
Drivers Purpose winpe5.x\WINPE5.x_driverinst.bat Used to install Dell-provided drivers, from \Dell\x64\Drivers, into the customized Windows PE 5.1 image. winpe10.x\WINPE10.x_driverinst.bat Used to install Dell-provided drivers, from \Dell\x64\Drivers, into the customized Windows PE 10.0 image.
Additional Tools Purpose Source Save in DTK location kernel image Used during a Linux unattended installation. Available on the Linux media. /opt/dell /toolkit /systems/linux initial ramdisk Used during a Linux unattended installation. Available on the Linux operating system media or on the Systems Build and Update Utility on the Dell Systems Management Tools and Documentation DVD. /opt/dell /toolkit /systems NOTE: For legacy operating systems, you may need to use the driver disk.
Deployment matrix Depending on the scope, current business needs, network setup, and process, you can select any of the suggested methods of deployment. Table 8. Deployment Method Matrix Deployment Methods Complexity Local deployment (bootable media) Relatively simple Advantages Disadvantages • • • • Necessary if a network connection is not available or is too slow. Can install supported Windows operating systems. Can install to support for the Linux operating systems.
After you have determined which deployment method best suits the needs of your organization, you are ready to begin building the DTK deployment directory structure on a network volume. For instructions on installing the DTK components and populating the deployment directory structure, see Preparing The Script Files. DTK deployment overview The deployment process can be separated into two main tasks: preparation and the actual deployment. For more details, see Preparing For Deployment and Deploying.
SBUU is replaced with Lifecycle Controller on Dell 13G server onwards. iDRAC with Lifecycle Controller is an Embedded Systems Management application for operating system deployment and lifecycle management of PowerEdge servers. You can access Dell Lifecycle Controller by pressing during system boot up.
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 10. 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.
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. stsvc.ini Configuration file used by raidcfg.exe. 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. IDRAC7 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 12. 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 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.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 --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.
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.
::new hdd device number. :: This is calling Windows installer scripts. ***************************************************** ::%DT_TOOLS%\syscfg --bootseq=hdd.emb.0 ::call WIN2K12.BAT Editing the sample batch files to perform a complete system 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 on the target system.
Table 21. 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 23. 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 25. 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 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.BAT to inform the task scripts about where to find the DTK utilities, scripts, and configuration files. 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.
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.sh, the latter overwrites the settings of the former. RAIDCFG.BAT or raidcfg.sh The RAIDCFG.BAT or raidcfg.
• Capturing The RAC Configuration With The RACCAP Or raccap Sample Script Capturing the system BIOS and BMC configuration with the SYSCAP or syscap.sh sample script You can replicate the system BIOS and BMC configurations from a source Dell system to an identical target Dell system. NOTE: For the script to complete successfully, the source system must have access to the network share that includes the prebuilt DTK directory structure. SYSCAP.BAT or syscap.sh The SYSCAP.BAT or syscap.
Running RACCAP.BAT or raccap.sh To run the RACCAP.BAT or raccap.sh sample script to capture the RAC configuration information in the raccfg.ini file: 1 Edit the startnet.cmd file (on your Windows PE image) or start-up script file (on your embedded Linux image) to call the RACCAP.BAT or raccap.sh script after the network share with the pre-built DTK directory structure is mounted. For example, add: On systems running Windows: Z:\Dell\x64\Toolkit\Template\Scripts\RACCAP.BAT Z:\raccfg.
Preparing the operating system installation scripts The W2K12INST.BAT script (on systems running supported Windows operating systems), the linux scripts (on systems running supported Red Hat Enterprise Linux Server operating system), and suseinst.sh sample script (on systems running supported SUSE Linux Enterprise Server operating system) are used to perform an installation. The variables and paths must be specified before the operating system can be installed.
UNATTEND.XML aND UNATTEND_UEFI.XML The UNATTEND.XML (in BIOS mode) and UNATTEND_UEFI.XML file (in UEFI mode) are the default name of the answer files for automating the Windows setup during an unattended installation. A sample copy of the UNATTEND.XML and UNATTEND_UEFI.XML file is provided as part of the DTK download in the \Toolkit\Template\Configs directory. UNATTEND.XML and UNATTEND_UEFI.XML contains the headings and parameters that instruct Windows setup to perform various configuration tasks.
Answer files Depending on the version of the Red Hat Enterprise Linux Server operating system, the ks-rhel6.cfg and ks-rhel7.cfg, ks_rhel6_uefi.cfg (only in UEFI mode), or ks_rhel7_uefi.cfg (only in UEFI mode) files are the default names of the answer files to automate an unattended Red Hat Enterprise Linux Server installation. A sample copy of the ks-rhel6.cfg/ks-rhel7.cfg file is provided as part of the DTK download in the /opt/dell/toolkit/template/configs directory. The ks-rhel6.cfg/ks-rhel7.
suseinst The suseinst.sh sample script is used to perform an unattended installation of a supported SUSE Linux Enterprise Server operating system. The variables and paths must be specified before the operating system can be installed.
When you have completed all necessary modifications of the autoinst.xml/ autoinst_uefi.xml file, save the completed file in the /opt/dell/ toolkit/systems/ directory. After you have successfully edited your deployment scripts, you are ready to create the deployment media and run the deployment. For instructions on creating the deployment media and running a full deployment, see Deployment Using Dell Provided Embedded Linux .
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.
• 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. Media-based local deployment for systems running Microsoft Windows This deployment method is easy to assemble, but is the least flexible.
3 Navigate to C:\program files\Windows AIK\Tools\amd64 directory on the system. 4 Execute the script: WINPE5.0_driverinst.bat where is the destination path to create the directory structure for Windows PE and is the path for the Dell drivers in the extracted DTK toolkit. For example, WINPE5.0_driverinst.bat C:\winpe_50 C:\DELL\x64\DRIVERS. This pre-installs the Dell drivers into Windows PE image.
Preparing and populating the network share This process includes: • Creating a network share on a system that is always available over the network for the target systems to be deployed. • Ensuring that a large amount of space is available for storing operating system installation files. • Ensuring that proper permissions are assigned to this share so that the target systems can read files from and write files to the share.
Using Windows Pre-installation Environment driver CAB files for systems running Windows DTK boot-critical drivers are now available in the Windows Preinstallation Environment (WinPE) driver Cabinet (CAB) files at dell.com/ support. You can use the WinPE driver CAB files with deployment tools such as Dell Server Deployment Pack and System Center Virtual Machine Manager for OS deployment.
Network file system or SMBFS file system based deployment The procedure enables you to boot DTK and launch the start-up script automatically from a network share (NFS or SMBFS). 1 Obtain the ISO image of the embedded Linux available at www.dell.com/support. 2 Extract the contents of the ISO image to a folder (for example, isoimage) on your hard drive. 3 Copy the custom script to a share (nfs/smbfs). 4 In UEFI mode, modify the corresponding shared section (nfs/smbfs) in EFI/BOOT/dtk_grub.
5 Burn the ISO contents to a media. 6 Your ISO image is ready for booting. Using RPMs You can install DTK using Red Hat Package Manger (RPM), Yellowdog Updater, Modified (YUM) or any other RPM Installation Manager, or using DTK tools. Installing DTK RPMs using RPM To install DTK RPMs using RPM: 1 Mount the DTK media at /mnt/cdrom. 2 Navigate to the /mnt/cdrom/RPMs directory. 3 Install the required DTK RPMs. NOTE: The /mnt/cdrom/RPMs directory contains all DTK RPMs and the dependency RPMs.
Post installation of RPMs After installing the RPMs, perform the following: 1 For the binaries syscfg and raidcfg, export the PATH environment variable /opt/dell/toolkit/bin. 2 To start the services, navigate to /opt/dell/srvadmin/sbin, and type: srvadmin-services.sh start NOTE: If the services are already running, restart the services.
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 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.
