Dell OpenManage Deployment Toolkit Version 5.
Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your computer. 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 © 2015 Dell Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws.
Contents 1 Introduction........................................................................................................... 6 What Is New In This Release................................................................................................................. 6 Other Documents You May Need.........................................................................................................7 Other supporting documents you may need..............................................................
Sample scripts for systems running windows....................................................................................28 Sample scripts for systems running Linux..........................................................................................29 RPMs.................................................................................................................................................... 30 Documentation.................................................................................
Deployment using removable boot media with a network connection (media-based) for systems running windows.................................................................................................................. 53 Media-based local deployment for systems running microsoft windows ...................................... 54 Creating and customizing images for Windows PE 3.0.............................................................. 54 Creating and customizing images for Windows PE 4.0 and 5.1......
Introduction 1 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.
– Emulex OCm14102-N5-D DP 10Gb bMezz Ethernet Network Adapter – Intel X710 QP 10Gb KR 4x10Gb Network Daughter Card – Intel I350/X710 2x10Gb BT 2x10Gb SFP+ Network Daughter Card – Intel X710 4x10GE SFP+/DA FH PCIe Ethernet Network Adapter – Intel X710 2x10GE SFP+/DA FH PCIe Ethernet Network Adapter • Support for installation and deployment of SUSE Linux Enterprise Server 12 (64-bit) in BIOS and UEFI mode.
• Operating system documentation to prepare for and execute the unattended installation process. In addition, you should consult the available web-based resources such as: – The Microsoft Tech Net database at microsoft.com/technet – The Red Hat Enterprise Linux support pages at redhat.com – The SUSE Linux Enterprise Server support pages at novell.com • Windows PE 3.0, Windows PE 4.0, Windows PE 5.
Dell provides several online and telephone-based support and service options. Availability varies by country and product, and some services may not be available in your area. To contact Dell for sales, technical support, or customer service issues: 1. Go to dell.com/support. 2. Select your support category. 3. Verify your country or region in the Choose a Country/Region drop-down list at the bottom of the page. 4. Select the appropriate service or support link based on your need.
Prerequisites and deployment 2 The Deployment ToolKit (DTK) is a collection of Windows PE and Linux-based utilities and scripts that assist 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 pre-operating system and post-operating system configuration tasks or to run a scripted deployment in the respective environments.
For Linux, the DTK utilities support deploying the following operating systems in BIOS and UEFI mode: • SUSE Linux Enterprise Server 12 (64-bit) • SUSE Linux Enterprise Server 11 SP3 (64-bit) • Red Hat Enterprise Linux 7.0 (64-bit) • Red Hat Enterprise Linux 6.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 (64-bit) • SUSE Linux Enterprise Server 11 SP3 (64-bit) • Red Hat Enterprise Linux 7.
• Windows Assessment and Deployment Kit (ADK) for Windows Server 2012 to build Windows PE 4.0. • Windows Assessment and Deployment Kit (ADK) for Windows Server 2012 R2 to build Windows PE 5.1. • An unzip utility. • Working knowledge to build Windows PE 3.0, Windows PE 4.0, and Windows PE 5.1 (see the Microsoft documentation to customize Windows PE).
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 1. 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. winpe3.x\WINPE3.0_driverinst.bat Used to install Dell-provided drivers, from \Dell\x32
Table 3. Supporting Tools and System Files for Linux Additional Tools Purpose Source Save in DTK location mkfs.* Formats hard-drive partitions. Any system running the Linux operating system. In the PATH variable. fdisk To create Master Boot Record (MBR) partitions in BIOS mode. Any system running the Linux operating system. In the PATH variable. parted To create GUID Partition Table (GPT) in UEFI mode. Any system running the Linux operating system. In the PATH variable.
operating system specific, and have been enhanced for Dell systems. For information on modifying the sample configuration files, see your operating system documentation. DTK Utilities (SYSCFG and RAIDCFG) and scripts (sample) supports Windows PE 3.0, Windows PE 4.0, and Windows PE 5.1. For Microsoft WinPE and OS deployment limitations, see technet.microsoft.com/en-us/ library/hh824993.aspx.
Deployment matrix for PowerEdge FD332 DTK supports multiple storage sleds (PowerEdge FD332)-to-compute sled (half-width, quarter-width, or full-width sleds, to which the storage sleds are mapped) mapping. The storage sleds and the storage controller modules in a PowerEdge FD332 are mapped to the compute sleds in the enclosure. The enclosures can be in either a split-mode or joint-mode configuration. For more details, see the see the Dell PowerEdge FD332 Owner’s Manual at dell.com/support/home.
Compute sled to PowerEdge FD332 setup Operating system installation support SYSCFG/RAIDCFG Description configuration support Compute sled without PERC + multiple PowerEdge FD332 with a dual PERC mapped to the compute sled (joint mode) + single boot VD Yes Yes PERC controller with boot VD must be the first in the boot order list of the compute sled BIOS.
Compute sled to PowerEdge FD332 setup Operating system installation support SYSCFG/RAIDCFG Description configuration support multiple) with a single PERC mapped to the compute sled + multiple boot VD Deployment matrix Depending on the scope, current business needs, network setup, and process, you can select any of the suggested methods of deployment. The following table provides the configuration complexity and the pros and cons of each deployment method. Table 5.
Deployment Methods Complexity Advantages Disadvantages Deployment solution framework from a third‑party vendor • DTK can be used in context of third-party deployment solution framework. Third-party deployment solution framework is used as the deployment transport mechanism. Tasks and scripts can be pushed to the target systems. Must either acquire and learn to use or have an existing third-party deployment solution framework. Everything is in one place on a network share.
4. Generate a system BIOS, BMC (Baseboard Management Controller), RAID, and/or RAC configuration profile from the optimally configured source system. Copy the generated configuration files to a read/write share onto the workstation. NOTE: You can obtain the system BIOS, BMC, RAID, and/or RAC configuration files from DTK Windows PE ISO image and running the SYSCAP.BAT, RAIDCAP.BAT, and RACCAP.BAT scripts or for Linux from DTK Linux ISO image and running the syscap.sh, raidcap.sh, and raccap.sh scripts.
deployment in the system directory for the target system. Copy all necessary files in the \Toolkit\Systems \ directory (Windows) or /opt/dell/toolkit/systems/
Downloading DTK 3 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 32-bit systems are located in the following directories: • Utilities: \Dell\x32\Toolkit\Tools • Sample scripts: \Dell\x32\Toolkit\Template\Scripts • Sample configuration files:\Dell\x32\Toolkit\Template\Configs DTK utilities for 64-bit systems are located in the following directories: • Utilities: \Dell\x64\Toolkit\Tools • Sample scripts: \Dell\x64\Toolkit\Template\Scripts • Sample configuration files: \Dell\x64\Toolkit\Template\Configs The directory \Dell\x32\Toolkit\Systems o
Directory structure on the target system The following table describes the contents of the directory structure on the target system. Table 7. 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.
Toolkit Components Purpose • • – BIOS settings and options – BMC settings and options – RAC 5 settings and options – IDRAC settings and options Maintains system state between reboots. Reports hardware devices and other system-related information. sysdrmk.exe Used by UPINIT.BAT to patch the boot sector and Master Boot Record (MBR). config.ini Configuration file used by raidcfg.exe. CAUTION: Do not edit this file. Incorrect edits might cause raidcfg.exe to fail. stsvc.
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. NOTE: This feature may not be supported on all systems. racadm7 Configures iDRAC 7. raidcfg Creates and reports RAID information. RaidcfgErrorCodes.txt Lists the error codes and messages for the raidcfg tool. stsvc.
Table 9. Sample Configuration Files for Windows Toolkit Components Purpose Location raccfg.ini Sample configuration file for DRAC 4 remote access controllers. \Toolkit\Systems\ raidcfg.ini Sample output file to enable RAID replication. \Toolkit\Systems\ winbom.ini Sample file used to start the racsvc and mr2kserv services. \Toolkit\Template\Configs winpeoem.sif Sample file to add support for Dell mass storage drivers. \Toolkit\Template\Configs Sample configuration files for L
Toolkit Components Purpose ks_rhel6_uefi.cfg Sample file used with unattended installation of Red Hat Enterprise Linux Server (version 6) operating system in UEFI mode. ks-rhel7.cfg Sample file used with unattended installation of Red Hat Enterprise Linux Server (version 7) operating system in BIOS mode. ks_rhel7_uefi.cfg Sample file used with unattended installation of Red Hat Enterprise Linux Server (version 7) operating system in UEFI mode. raccfg.ini Sample configuration file for DRAC 4 RACs.
Toolkit Components Purpose 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.BAT Captures the RAID settings and saves them to a file. RAIDCFG.BAT Configures the selected RAID controllers on the system. RAIDREP.
Toolkit Components Purpose raccap.sh Captures RAC settings to a file. racrep.sh Applies (replicates) the RAC settings saved in a file to the target system. raidcfg.sh Configures all RAID controllers detected in a system. suseinst.sh Performs an unattended installation of a supported SUSE Linux Enterprise Server operating system. syscap.sh Captures BIOS and BMC configuration settings and saves them to a file. sysdrmk Used by upinit.shto patch the boot sector. sysrep.
Table 14. Documentation Toolkit Components Purpose Dell OpenManage Deployment Toolkit Installation Guide Contains information about installing and deploying DTK on supported Dell systems. README Contains the latest information about supported systems, known issues, and important notes. On systems running the Linux operating system, it is located at /mnt/cdrom as well.
Setting up a directory structure for deployment 4 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.
information. On systems running Linux, the /systems folder acts as a repository for the common files required for the systems. On systems running Windows, you can store all profile configuration files for an optimally configured Dell PowerEdge server in the directory Toolkit\Systems\. These files can then be accessed from this directory when deploying multiple similar PowerEdge servers.
Preparing the script files 5 This chapter describes the steps required to use the Deployment Toolkit (DTK) sample scripts to perform a full deployment on a target system in the Microsoft Windows PE and embedded Linux environment.
::%DT_TOOLS%\syscfg --bootseq=hdd.emb.0 ::call WIN2K8.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 16. 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 18. Replication Scripts for Linux Script Name Description Associated Files racrep.sh Applies the RAC configuration settings saved in a file to the current system. • tkenvset.sh — Used by racrep.sh to inform the task scripts 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. The wrapper script, racadm invokes racadm4 , racadm5 , or racadm6 depending on the system configuration.
Deployment scripts for systems running Linux operating systems The following table lists the deployment scripts for systems running Linux. Table 20. 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.
Script Name Description Associated Files • • • • • NOTE: Both grub and grub2 uses the following images in conjunction with the unattended answer file to perform unattended operations: – initial ramdisk — Available on the SUSE Linux Enterprise Server operating system media – kernel image — Available on the SUSE Linux Enterprise Server operating system media autoinst.xml — Used by suseinst.sh in conjunction with grub to install the operating system files. autoinst-sles11.xml — Used by suseinst.
Script Name Description Associated Files – UPINIT.BAT— Used by PARTCFG.BAT to create and populate the Dell utility partition. – FORMAT.EXE— Provided by Windows to format the partition. Other scripts for systems running Linux operating systems The following table lists the other scripts for Linux. Table 22. Other Scripts for Linux Script Name Description Associated Files tkenvset.sh Sets the path for DTK installation and variables for the system to be deployed and configured.
Script Name Description Associated Files • • • unzip — Used by upinit.sh to populate the Dell utility partition. mke2fs — Used to create a ext2 file system. upimg.bin — Contains the zipped contents of the Dell utility partition. Editing example of TKENVSET and tkenvset The majority of editing required for DTK sample scripts involves the TKENVSET.BAT (for Windows) or tkenvset.sh (for Linux) script. As a result, the scripting discussion focuses on this script.
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)
In raccap.sh: DT_RAC_CAPFILE=$dt_systems/$dt_platform/raccfg.ini To edit the RAC configuration variables, locate the following lines: In RACREP.BAT: :: RAC section set DT_NICCFG=10.98.8.121 set DT_RAC_CAPFILE=%DT_SYSTEMS%\%DT_PLATFORM%\raccfg.ini In racrep.sh: # RAC section DT_NICCFG=10.98.8.121 set DT_RAC_CAPFILE=$dt_systems/$dt_platform/raccfg.
# RAIDCFG section DT_VD_SIZE=10480 # default size for virtual disk CAUTION: DT_MOUNT specifies the mount point of the Dell utility partition. If your RAMDRIVE, hard drive, or other device already owns this designation, mount does not override the setting and the utility partition is not created. In partcfg.
• RAIDCFG.BAT or raidcfg.sh • SYSREP.BAT or sysrep.sh • PARTCFG.BAT or partcfg.sh RACREP.BAT or racrep.sh The RACREP.BAT or racrep.sh sample script applies RAC options to the target system based on configuration information that has been saved in the configuration file. User input is optional, depending on the variables set in the RACREP.BAT or racrep.sh sample script. On systems running Windows, RACREP.BAT script uses RACADM.EXE to configure RAC in the target system.
NOTE: The racrep.sh and sysrep.sh have duplicate functions. If you run racrep.sh followed by sysrep.sh, the latter overwrites the former settings. PARTCFG.BAT or partcfg.sh In BIOS mode, the PARTCFG.BAT or partcfg.sh sample script creates and populates the Dell utility partition using UPINIT.BAT or upinit.sh and creates the deployment partition on a specified disk. In UEFI mode, the partcfg.sh sample script creates the deployment partition on a specified disk. For more information about using the UPINIT.
On systems running Windows: call Z:\Dell\Toolkit\Template\Scripts\SYSCAP.BAT On systems running Linux: /opt/dell/toolkit/template/scripts /syscap.sh 2. Boot the source system into Windows PE or embedded Linux. The script runs and saves the configuration information in the \Toolkit\Systems\ directory in Windows and /opt/dell/toolkit/systems/ directory in Linux. 3. Edit the startnet.
RACCAP.BAT or raccap.sh The RACCAP.BAT or raccap.sh sample script captures RAC configuration settings and saves them to a specified location. An optional user input can be passed as a parameter. You can provide the path or file name as an input to this script. The default variable values used in this script are set to the correct default values to perform a scripted deployment. On systems running Windows, the RACCAP.BAT uses the RACADM.
W2K8INST.BAT and W2K12INST.BAT The W2K8INST.BAT and W2K12INST.BAT sample scripts are used to perform an unattended installation of the Windows Server 2008 and Windows Server 2012 operating systems respectively. The variables and paths must be specified before the operating system can be installed.
various setup options, including how to partition disks and the location of the Windows image you want to install. Before a full deployment can be run, edit all appropriate headings and parameters, as necessary. NOTE: On systems running Windows Server 2012 operating system, save the default answer files as UNATTEND2K12.XML or UNATTEND2K12_UEFI.XML.
dell/toolkit/template/configs directory. The ks-rhel6.cfg/ks-rhel7.cfg files contain the headings 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: The sample file provided to install Red Hat Enterprise Linux Server (version 5) in BIOS mode is named ks-rhel5.cfg. To use the sample ks-rhel5.
External dependencies of suseinst.sh The DT_PLATFORM variable is set during deployment by tkenvset.sh using platform discovery. The suseinst.sh script uses the unattended answer file in conjunction with the grub utility and kernel image and initial ramdisk files to install the operating system files. autoinst.xml or autoinst_uefi.xml for SUSE Linux Enterprise server The autoinst.xml and autoinst_uefi.
Running the deployment scripts 6 This chapter provides best practices, procedures, and scenarios for using the Deployment Toolkit (DTK) to perform pre‑operating system configuration tasks and to install supported operating systems on supported Dell systems. After you have populated the deployment directory structure with all necessary files and carefully edited the deployment scripts and configurations files, you are ready to begin the final stage of the deployment process.
• 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. Any change to the system configuration, for example, requires the creation of a new bootable media. This method does not provide a writable media, making it necessary to use predefined and tested configuration files.
NOTE: The destination folder (C:\winpe_51) is created as part of the process, and must not be an existing directory. The destination path and the path to the Dell drivers must not contain any blank space. Creating a bootable media for Windows PE 3.0 To create a bootable media: 1. Click Start and navigate to All Programs → Microsoft Windows AIK. 2. Click Windows PE Tools Command Prompt to open a command prompt window. 3. Navigate to C:\program files\Windows AIK\Tools\x32 or C:\program files\Windows AIK
This deployment method is easy to assemble and provides great flexibility in changing the scripts and configuration files. Any change to the system configuration, for example, does not require re‑creation of the bootable media. This method also provides access to the remote share as writable media. Hence, the configuration files captured during the deployment automation process can be saved to the remote share.
• Configuration information is read from the media. • The operating system is installed from the media. 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).
PXE-Based deployment The procedure enables you to boot DTK over network and pass parameters (startup script location and name) during boot using the Preboot eXecution Environment (PXE) configuration file. This automatically launches the start-up script off the network share, when DTK is booted. 1. Obtain the ISO image of the embedded Linux available at support.dell.com. 2.
Your ISO image is ready for booting. Media-based deployment The different media-based deployments are as follows: • Deployment Using Custom Scripts • Deployment Using RPMs • Deployment Using USB Deployment using custom scripts 1. Obtain the ISO image of the embedded Linux at support.dell.com. 2. Extract the contents of the ISO image to a folder (for example, isoimage) on your hard drive. 3. Copy the custom scripts into the same folder.
Installing DTK RPMs using YUM To install DTK RPMs using YUM: 1. Install YUM and the dependency RPMs. 2. Mount the DTK iso to /mnt/cdrom. 3. Create a repository file (for example, dtk.repo) for the required operating system in a writable location. The corresponding RPMs for the operating system are located at /mnt/cdrom/RPMs/, where OS can be the supported Linux operating system. For example, to deploy DTK RPMs on RHEL 6.x, you can use the following content in dtk.
3. Install and launch the tool. 4. Select the downloaded ISO image, and select the option to convert the image to a bootable USB format. Deployment using customized embedded Linux Make sure that you have the following basic libraries, Dell toolkit libraries, tools, and utilities required for DTK and integrate them to your embedded Linux deployment environment to proceed with the deployment: • Drivers for all hardware installed in the embedded Linux. These drivers are available at support.dell.com.
7 Running Dell update packages on systems running embedded Linux You can run the Dell Update Packages in embedded Linux environments on supported Dell systems. The common scenarios for running update packages are: • Running Update Packages In Dell-Provided Embedded Linux • Running Update Packages In Customized Embedded Linux Running update packages in Dell-provided embedded Linux 1. Obtain the required update packages from the Dell Server Updates DVD or from support.dell.com. 2.
Update Packages Dependency Dependencies Available On iDRAC Instrumentation drivers /mnt/cdrom/tools Dell 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. For more information, see Running Update Packages In Dell-Provided Embedded Linux.
Known issues and frequently asked questions 8 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.
Q: When I use the sample DTK scripts to deploy multiple systems, do I edit the configuration files to reflect unique information (such as unique system names, IP address, and BIOS asset tags) for each system? A: The sample scripts are provided as examples for users who want to develop their own deployment process. The scripts may work perfectly in your environment. If not, you may need to develop your own scripts entirely from scratch.
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: Do I need to specify RAID type and size when creating virtual disks? A: No. The default RAID type is RAID 0. If RAID size is not provided, the maximum size allowed for virtual disk is created.
A: Ensure that the RAID controllers can be seen in the BIOS during POST. If the BIOS does not detect the controller, then RAIDCFG does not detect it. Also ensure that the controller is set to RAID mode and not any other mode in the controller BIOS. Q: What is span length? A: Span length enables you to select the number of array disks in a span for the nested RAID levels (RAID-10, RAID-50, and RAID-60). The default (minimum permissible) span length value is 2 for RAID-10, 3 for RAID-50, and 4 for RAID-60.
Q: In --solcfgparams, when I set the Serial Over LAN (SOL) character send threshold using solcharsendthreshold to be 225, I get a Hardware subsystem error. Invalid data field in request. What are the valid values? A: The range of valid values for --solcfgparams and --solcharsendthreshold are from 1 to 220. Q: How do I enable console redirection on a modular system? A: Set the --serialcomm option value to enableconred. For example, syscfg -serialcomm=enableconred.
2. Delete the entry: Run efibootmgr -b XYZ –B Windows PE questions Q: My system gets the error Illegal or Missing File Types Specified in Section Files.SCSI.Name during an unattended installation of a supported Windows operating system on supported Dell systems. A: This behavior can occur when the line in the Txtsetup.oem file under the [Files.SCSI. name] heading is not a supported file type. To resolve this behavior, you must remove the line in the Txtsetup.oem file.
