HP ProLiant Essentials Rapid Deployment Pack—Windows Edition
`HP ProLiant Essentials Rapid Deployment Pack—Windows Edition
`User Guide
`User Guide
`
`
`
`
`
`
`
`Part Number: 315378-009
`Part Number: 315378-009
`
`Ninth edition: January 2007
`Ninth edition: January 2007
`
`Product version: 3.50
`Product version: 3.50
`
`i nven t
`
`WIZ, Inc. EXHIBIT - 1116
`WIZ, Inc. v. Orca Security LTD.
`
`

`

`Legal notices
`Legal notices
`
`© Copyright 2001–2007 Hewlett-Packard Development Company, L.P.
`© Copyright 2001-2007 Hewlett-Packard Development Company, L.P.
`
`Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212,
`Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212,
`Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S.
`Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S.
`Government under vendor's standard commercial license.
`Government under vendor's standard commercial license.
`
`The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express
`The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express
`warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP
`warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP
`shall not be liable for technical or editorial errors or omissions contained herein.
`shall not be liable for technical or editorial errors or omissions contained herein.
`
`Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation. Windows Server 2003 is a U.S. trademark or Microsoft
`Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation. Windows Server 2003 is a U.S. trademark or Microsoft
`Corporation. Intel is a trademark or registered trademark of Intel Corporation or its subsidiaries in the United States and other countries.
`Corporation. Intel is a trademark or registered trademark of Intel Corporation or its subsidiaries in the United States and other countries.
`
`Part Number: 315378-009
`Part Number: 315378-009
`
`Ninth edition: January 2007
`Ninth edition: January 2007
`
`Product version: 3.50
`Product version: 3.50
`
`
`
`
`
`
`2 2
`
`

`

`Contents
`Contents
`
`1 Configuring your system prior to deployment
`1 Configuring your system prior to deployment
`Configuring HP BladeSystem ..................................................................................................................... 4
`4
`Configuring HP BladeSystem
`Configuring virtual machines ..................................................................................................................... 4
`Configuring virtual machines
`4
`VMware ESX Server virtual machine ...................................................................................................... 5
`VMware ESX Server virtual machine
`5
`Microsoft Virtual Server 2005 R2 virtual machine.................................................................................... 5
`Microsoft Virtual Server 2005 R2 virtual machine
` 5
`Direct-attached storage environment deployments......................................................................................... 5
`Direct-attached storage environment deployments
`5
`Boot from SAN environment deployments.................................................................................................... 6
`Boot from SAN environment deployments
`6
`SAN-attached environment deployments ..................................................................................................... 8
`SAN-attached environment deployments
`8
`Windows deployments ............................................................................................................................. 8
`Windows deployments
` 8
`Linux deployments.................................................................................................................................. 10
`Linux deployments
`10
`Red Hat Enterprise Linux .................................................................................................................... 10
`Red Hat Enterprise Linux
`10
`VMware ESX Server deployments............................................................................................................. 10
`VMware ESX Server deployments
`10
`VMware ESX Server 2.5.3 ................................................................................................................. 10
`VMware ESX Server 2.5.3
`10
`VMware ESX Server 3.0.1 ................................................................................................................. 11
`VMware ESX Server 3.0.1
` 11
`2 Using the Rapid Deployment Pack
`2 Using the Rapid Deployment Pack
`Connecting the server blades................................................................................................................... 12
`12
`Connecting the server blades
`Creating a reference server and image..................................................................................................... 15
`Creating a reference server and image
`15
`Deploying the image to other similar server blades..................................................................................... 18
`Deploying the image to other similar server blades
`18
`Maintaining the servers with rip-and-replace.............................................................................................. 22
`Maintaining the servers with rip-and-replace
`22
`3 Understanding the Deployment Server
`3 Understanding the Deployment Server
`Jobs ..................................................................................................................................................... 23
` 23
`Jobs
`Job Default Settings ................................................................................................................................ 24
`Job Default Settings
` 24
`How a Job is run on a target ................................................................................................................... 26
`How a Job is run on a target
`26
`Automation Environment .................................................................................................................... 27
`Automation Environment
`27
`Deployment Server Directory Structure ...................................................................................................... 30
`Deployment Server Directory Structure
`30
`4 Customizing the ProLiant and Integrity Integration Modules
`4 Customizing the ProLiant and Integrity Integration Modules
`Preparing the Integration Modules for customization................................................................................... 31
` 31
`Preparing the Integration Modules for customization
`Jobs ................................................................................................................................................ 31
`Jobs
` 31
`Files ................................................................................................................................................ 31
`Files
` 31
`Reasons to customize the Integration Modules............................................................................................ 32
`Reasons to customize the Integration Modules
`32
`All operating systems......................................................................................................................... 32
`All operating systems
`32
`Windows unattend text files................................................................................................................ 32
`Windows unattend text files
` 32
`Red Hat Linux kickstart files ................................................................................................................ 32
`Red Hat Linux kickstart files
` 32
`SUSE Linux control files...................................................................................................................... 32
`SUSE Linux control files
` 32
`VMware ESX Server kickstart files........................................................................................................ 32
`VMware ESX Server kickstart files
` 32
`Virtual Machine jobs ......................................................................................................................... 32
`Virtual Machine jobs
`32
`Customization examples ......................................................................................................................... 33
`Customization examples
`33
`Example 1—Using a specific ProLiant Support Pack version.................................................................... 33
`Example 1 —Using a specific ProLiant Support Pack version
` 33
`Example 2—Modifying the Windows unattend text file .......................................................................... 33
` 33
`Example 2—Modifying the Windows unattend text file
`Example 3—Modifying the Red Hat Linux kickstart files.......................................................................... 33
` 33
`Example 3 —Modifying the Red Hat Linux kickstart files
`Example 4—Modifying the Altiris Deployment Agent for Linux ................................................................ 33
` 33
`Example 4 —Modifying the Altiris Deployment Agent for Linux
`Example 5—Creating a Create Virtual Machine job for other operating systems ....................................... 33
`Example 5 —Creating a Create Virtual Machine job for other operating systems
`33
`Example 6—Modifying a Create Virtual Machine job for custom virtual values ......................................... 34
`Example 6—Modifying a Create Virtual Machine job for custom virtual values
`34
`5 HP support and contact information
`5 HP support and contact information
`Related documents ................................................................................................................................. 35
`35
`Related documents
`Online resources.................................................................................................................................... 35
`Online resources
`35
`HP contact information ........................................................................................................................... 35
`HP contact information
`35
`Index
`Index
`
`
`
`Contents 3
`Contents 3
`
`
`
`

`

`
`
`1 Configuring your system prior to deployment
`1 Configuring your system prior to deployment
`
`The following sections detail the configuration steps necessary to deploy an operating system to a server, virtual
`The following sections detail the configuration steps necessary to deploy an operating system to a server, virtual
`machine, or specific platform.
`machine, or specific platform.
`
`pr
`
`
`IMPORTANT: For your deployment, you might need to complete more than one of the procedures in this
`IMPORTANT: For your deployment, you might need to complete more than one of the procedures in this
`section.
`section.
`
`Deployment configuration information is provided for the following platforms and environments:
`Deployment configuration information is provided for the following platforms and environments:
`•
`•
`HP BladeSystem servers
`HP BladeSystem servers
`•
`•
`Virtual machines
`Virtual machines
`•
`•
`Direct-attached storage
`Direct-attached storage
`•
`•
`Boot from storage area network (SAN)
`Boot from storage area network (SAN)
`•
`•
`SAN-attached storage
`SAN-attached storage
`Deployment configuration information is provided for the following operating system:
`Deployment configuration information is provided for the following operating system:
`• Microsoft® Windows®
`• Microsoft® Windows®
`•
`•
`Linux
`Linux
`•
`•
`VMware ESX Server
`VMware ESX Server
`Configuring HP BladeSystem
`Configuring HP BladeSystem
`The Physical Devices view in the Deployment Server Console displays the physical relationship between the racks,
`The Physical Devices view in the Deployment Server Console displays the physical relationship between the racks,
`enclosures, and server blades using the rack name and enclosure name for each HP BladeSystem server. The display
`enclosures, and server blades using the rack name and enclosure name for each HP BladeSystem server. The display
`name for a new server blade is a combination of the rack name, enclosure name, and bay number. Before you
`name for a new server blade is a combination of the rack name, enclosure name, and bay number. Before you
`connect the first server in an enclosure to the Deployment Server, assign the rack, and enclosure with unique names to
`connect the first server in an enclosure to the Deployment Server, assign the rack, and enclosure with unique names to
`prevent conflicting database entries.
`prevent conflicting database entries.
`If the BladeSystem servers are powered up before the rack name and enclosure name have been changed, they are
`If the BladeSystem servers are powered up before the rack name and enclosure name have been changed, they are
`recorded in the Deployment Server database and displayed in the Deployment Server Console. If the names are
`recorded in the Deployment Server database and displayed in the Deployment Server Console. If the names are
`changed after being recorded in the Deployment Server database, then the servers must be rebooted for the new rack
`changed after being recorded in the Deployment Server database, then the servers must be rebooted for the new rack
`name and enclosure name to be discovered. In addition, the original default names for the rack and enclosure must
`name and enclosure name to be discovered. In addition, the original default names for the rack and enclosure must
`be manually deleted from the console.
`be manually deleted from the console.
`To change the rack name and enclosure name, follow the procedure specific to each server type:
`To change the rack name and enclosure name, follow the procedure specific to each server type:
`•
`•
`ProLiant BL p-Class servers—Place at least one server blade in each enclosure, and before powering up the
`ProLiant BL p-Class servers—Place at least one server blade in each enclosure, and before powering up the
`server blade, change the rack and enclosure information using the Integrated Lights-Out (iLO) interface. For
`server blade, change the rack and enclosure information using the Integrated Lights-Out (iLO) interface. For
`details about accessing iLO to change the rack name and enclosure name, see the documentation shipped with
`details about accessing iLO to change the rack name and enclosure name, see the documentation shipped with
`your server blade.
`your server blade.
`HP BladeSystem c-Class servers—To access the Onboard Administrator and change rack name and enclosure
`HP BladeSystem c-Class servers—To access the Onboard Administrator and change rack name and enclosure
`name, see the server documentation.
`name, see the server documentation.
`Configuring virtual machines
`Configuring virtual machines
`The following configuration steps are required to support virtual-machine-scripted installations.
`The following configuration steps are required to support virtual-machine-scripted installations.
`
`•
`•
`
`
`
`
`Configuring your system prior to deployment 4
`Configuring your system prior to deployment 4
`
`

`

`4.
`4.
`
`VMware ESX Server virtual machine
`VMware ESX Server virtual machine
`re NOTE: The following procedure is based on the assumption that VMware ESX Server has been initialized. For
` NOTE: The following procedure is based on the assumption that VMware ESX Server has been initialized. For
`more information, see the "VMware ESX Server deployments" section in this guide.
`more information, see the “VMware ESX Server deployments” section in this guide.
`
`Create a new virtual machine to ensure that the guest operating system is appropriate for the operating system to be
`Create a new virtual machine to ensure that the guest operating system is appropriate for the operating system to be
`installed on the virtual machine. For more information about creating virtual machines, see the VMware
`installed on the virtual machine. For more information about creating virtual machines, see the VMware
`documentation located at
`documentation located at
`http://h18004.www1.hp.com/products/servers/software/vmware/index.html?jumpid=reg_R1002_USEN.
`http://h18004.www1. hp.com/products/servers/software/vmware/index. html?jumpid=reg R1002 USEN.
`Manually creating a virtual machine
`Manually creating a virtual machine
`1.
`1. Power up the virtual machine.
`Power up the virtual machine.
`2. At the VMware Remote Console, press F2 to access the BIOS.
`2. At the VMware Remote Console, press F2 to access the BIOS.
`3.
`3.
`Set the network adapter to be first in the boot order, enabling the virtual machine to Preboot eXecution
`Set the network adapter to be first in the boot order, enabling the virtual machine to Preboot eXecution
`Environment (PXE) boot during the scripted installations.
`Environment (PXE) boot during the scripted installations.
`Save the virtual machine BIOS settings and reboot the virtual machine. The virtual machine appears in the
`Save the virtual machine BIOS settings and reboot the virtual machine. The virtual machine appears in the
`Deployment Server Console as a new computer.
`Deployment Server Console as a new computer.
`Using a job to create a virtual machine
`Using a job to create a virtual machine
`From the Deployment Server console, use the Virtual Machine Deployment Toolbox/1 - Create Virtual Machine jobs.
`From the Deployment Server console, use the Virtual Machine Deployment Toolbox/1 – Create Virtual Machine jobs.
`This job will create the virtual machine, set the network adapter first in the boot order, and start the new virtual
`This job will create the virtual machine, set the network adapter first in the boot order, and start the new virtual
`machine by booting to PXE. The new virtual machine will show up in the Deployment Server console in New
`machine by booting to PXE. The new virtual machine will show up in the Deployment Server console in New
`Computers after the virtual machine has completed the boot process.
`Computers after the virtual machine has completed the boot process.
`Microsoft Virtual Server 2005 R2 virtual machine
`Microsoft Virtual Server 2005 R2 virtual machine
`To create and power up a virtual machine:
`To create and power up a virtual machine:
`1.
`1.
`From the Virtual Server Remote Console, press Delete to access the BIOS.
`From the Virtual Server Remote Console, press Delete to access the BIOS.
`2.
`2.
`Set as first in the boot order the network adapter, enabling the virtual machine to PXE-boot during the
`Set as first in the boot order the network adapter, enabling the virtual machine to PXE-boot during the
`scripted installations.
`scripted installations.
`Save the virtual machine BIOS settings, and reboot the virtual machine. The virtual machine appears in the
`Save the virtual machine BIOS settings, and reboot the virtual machine. The virtual machine appears in the
`Deployment Server Console as a new computer.
`Deployment Server Console as a new computer.
`For more information about creating virtual machines, see the Microsoft Virtual Server documentation located at
`For more information about creating virtual machines, see the Microsoft Virtual Server documentation located at
`http://www.microsoft.com/windowsserversystem/virtualserver/default.mspx.
`http://www.microsoft.com/windowsserversystem/virtualserver/default.mspx.
`Direct-attached storage environment deployments
`Direct-attached storage environment deployments
`For a scripted installation where an NTFS.IMG or GRUB.IMG file is deployed to initiate the operating system
`For a scripted installation where an NTFS.IMG or GRUB.IMG file is deployed to initiate the operating system
`installation or for an image installation, the image file is deployed or captured to or from the drive according to the
`installation or for an image installation, the image file is deployed or captured to or from the drive according to the
`Altiris drive enumeration. If multiple storage drives are enabled on the target server, the job might install or capture
`Altiris drive enumeration. If multiple storage drives are enabled on the target server, the job might install or capture
`the image on the secondary drives instead of the primary drives. The Read Hardware Configuration [server specific]
`the image on the secondary drives instead of the primary drives. The Read Hardware Configuration [server specific]
`job includes output from the Altiris showdisk utility. You can use this output to determine how the drives will be
`job includes output from the Altiris showdisk utility. You can use this output to determine how the drives will be
`enumerated. This allows you to add the appropriate -d# parameters to the Create Disk Image or Distribute Disk Image
`enumerated. This allows you to add the appropriate -d# parameters to the Create Disk Image or Distribute Disk Image
`task. For information on how to read data from the showdisk utility, see the Rapid Deployment Pack Knowledge Base
`task. For information on how to read data from the showdisk utility, see the Rapid Deployment Pack Knowledge Base
`at http://www.hp.com/servers/rdp/kb.
`at http://www.hp.com/servers/rdp/kb.
`
`3.
`3.
`
`ne
`
`
`IMPORTANT: If a USB device is used as the boot media method, a scripted installation or image installation
`IMPORTANT: If a USB device is used as the boot media method, a scripted installation or image installation
`job may deploy or capture the image to or from the USB device. The drive number of the hard drive must be
`job may deploy or capture the image to or from the USB device. The drive number of the hard drive must be
`specified for the Create Disk Image or Distribute Disk Image tasks.
`specified for the Create Disk Image or Distribute Disk Image tasks.
`
`
`Configuring your system prior to deployment 5
`Configuring your system prior to deployment 5
`
`
`
`

`

`
`
`
`
`To specify which drive to use for installation:
`To specify which drive to use for installation:
`1.
`From the Deployment Server Console, copy, rename, and edit the job to be used for this deployment.
`1.
`From the Deployment Server Console, copy, rename, and edit the job to be used for this deployment.
`2. Modify the Create Disk Image or Distribute Disk Image task.
`2. Modify the Create Disk Image or Distribute Disk Image task.
`3.
`3.
`Select Advanced, and click the Additional Options tab.
`Select Advanced, and click the Additional Options tab.
`4.
`4.
`In the Additional command-line switches field, add the -dx switch, where xis an integer which represents the
`In the Additional command-line switches field, add the -dx switch, where x is an integer which represents the
`disk number of the first hard drive in the primary controller.
`disk number of the first hard drive in the primary controller.
` NOTE: For step 4, refer to the Red Hat Enterprise Linux section for special use of –dx for deployments
`NOTE: For step 4, refer to the Red Hat Enterprise Linux section for special use of -dx for deployments
`with LVM images.
`with LVM images.
`
`Boot from SAN environment deployments
`Boot from SAN environment deployments
`The following configuration steps are required before installing an operating system on a server with a QLogic or
`The following configuration steps are required before installing an operating system on a server with a QLogic or
`Emulex Fibre Channel Host Bus Adapter (FC HBA) that boots from an HP StorageWorks SAN.
`Emulex Fibre Channel Host Bus Adapter (FC HBA) that boots from an HP StorageWorks SAN.
`For details about SAN configurations and minimum firmware versions, see the following documents:
`For details about SAN configurations and minimum firmware versions, see the following documents:
`•
`•
`HP StorageWorks Booting Windows Systems from a Storage Area Network Application Notes
`HP StorageWorks Booting Windows Systems from a Storage Area Network Application Notes
`•
`•
`HP StorageWorks Booting Linux Systems from a Storage Area Network Application Notes
`HP StorageWorks Booting Linux Systems from a Storage Area Network Application Notes
`1.
`1.
`Be sure the following prerequisites are met:
`Be sure the following prerequisites are met:
`•
`• The target system is cabled in a single-path configuration (with only one channel active). You can cable
`The target system is cabled in a single-path configuration (with only one channel active). You can cable
`both paths and zone only a single port to have access to the boot. Cabling both paths and only zoning a
`both paths and zone only a single port to have access to the boot. Cabling both paths and only zoning a
`single port can be performed to have access to the boot logical unit number (LUN) until the server operating
`single port can be performed to have access to the boot logical unit number (LUN) until the server operating
`system install is complete and the multipathing software is installed.
`system install is complete and the multipathing software is installed.
`•
`• The server has booted to PXE and is in a waiting state in the Deployment Server Console.
`The server has booted to PXE and is in a waiting state in the Deployment Server Console.
`2. Configure the SAN storage for the target system.
`2. Configure the SAN storage for the target system.
`a. Run the Read ProLiant ML/DL/BL HBA Configuration {LinuxPE} or {WinPE} job from the Server Deployment
`a. Run the Read ProLiant ML/DL/BL HBA Configuration {LinuxPE} or {WinPE} job from the Server Deployment
`Toolbox\ 1 —Hardware Configuration \HBA job folder on the target system. This job creates the
`Toolbox\1—Hardware Configuration\HBA job folder on the target system. This job creates the
`. lib \ hwconf ig \hba \ ID. ini file, where ID is the target system computer ID. The following is an
`.\lib\hwconfig\hba\ID.ini file, where ID is the target system computer ID. The following is an
`example of a generated file:
`example of a generated file:
`[HBA0]
`[HBA0]
`WWID=500508b200713e72
`WWID=500508b200713e72
`HostAdapterBiosEnable=1
`HostAdapterBiosEnable=1
`SelectBootEnable=1
`SelectBootEnable=1
`BootDeviceWWID=
`BootDeviceWWID=
`BootDeviceLUN=
`BootDeviceLUN=
`
`[HBA1]
`[HBAl]
`WWID=500508b200713e73
`WWID=500508b200713e73
`HostAdapterBiosEnable=0
`HostAdapterBiosEnable=0
`SelectBootEnable=0
`SelectBootEnable=0
`BootDeviceWWID=
`BootDeviceWWID=
`BootDeviceLUN=
`BootDeviceLUN=
`
`NOTE: To determine the target system computer ID, right-click the target system and select Properties
` NOTE: To determine the target system computer ID, right-click the target system and select Properties
`from the Deployment Server Console. Click the General tab. The computer ID appears in the ID field.
`from the Deployment Server Console. Click the General tab. The computer ID appears in the ID field.
`
`
`
`b. Create a LUN for the boot volume of the target system. Record the created LUN and the World Wide
`b. Create a LUN for the boot volume of the target system. Record the created LUN and the World Wide
`Identification (WWID) of the boot controller.
`Identification (WWID) of the boot controller.
`c. Using the target system HBA WWID from the file created in step 2a, configure the SAN switches for zoning
`c. Using the target system HBA WWID from the file created in step 2a, configure the SAN switches for zoning
`or Selective Storage Presentation as needed in your environment.
`or Selective Storage Presentation as needed in your environment.
`3. Configure the target system HBA to boot from the configured SAN storage.
`3. Configure the target system HBA to boot from the configured SAN storage.
`a. Edit the ID.ini file created in step 2a, adding the previously recorded boot controller WWID and LUN.
`a. Edit the ID. ini file created in step 2a, adding the previously recorded boot controller WWID and LUN.
`The boot volume must be set up as the first visible LUN. The following is an example of an edited file:
`The boot volume must be set up as the first visible LUN. The following is an example of an edited file:
`[HBA0]
`[HBA0]
`WWID=500508b200713e72
`WWID=500508b200713e72
`HostAdapterBiosEnable=1
`HostAdapterBiosEnable=1
`SelectBootEnable=1
`SelectBootEnable=1
`BootDeviceWWID=395442c135713a41
`BootDeviceWWID=395442c135713a41
`BootDeviceLUN=01
`BootDeviceLUN=01
`
`
`
`
`Configuring your system prior to deployment 6
`Configuring your system prior to deployment 6
`
`

`

`[HBA1]
`[HBAl]
`WWID=500508b200713e73
`WWID=500508b200713e73
`HostAdapterBiosEnable=0
`HostAdapterBiosEnable=0
`SelectBootEnable=0
`SelectBootEnable=0
`BootDeviceWWID=395442c135713a42
`BootDeviceWWID=395442c135713a42
`BootDeviceLUN=01
`BootDeviceLUN=01
`b. Run the Write ProLiant ML/DL/BL HBA Configuration {LinuxPE} or {WinPE} job from the Server Deployment
`b. Run the Write ProLiant ML/DL/BL HBA Configuration {LinuxPE} or {WinPE} job from the Server Deployment
`Toolbox\1—Hardware Configuration\HBA job folder on the target system.
`Toolbox\1 —Hardware Configuration\HBA job folder on the target system.
`c. Run the Deploy ProLiant BL System Configuration (Boot From SAN) {LinuxPE} or {WinPE} job from the Server
`c. Run the Deploy ProLiant BL System Configuration (Boot From SAN) {LinuxPE} or {WinPE} job from the Server
`Deployment Toolbox\l —Hardware Configuration\System job folder on the target system. This job disables
`Deployment Toolbox\1—Hardware Configuration\System job folder on the target system. This job disables
`the embedded array controller and places the HBA controller first in the boot order.
`the embedded array controller and places the HBA controller first in the boot order.
`To deploy a Windows operating system, the system must beset up in a single-path configuration. To enable
`To deploy a Windows operating system, the system must be set up in a single-path configuration. To enable
`access to the LUN only from the first HBA and one array controller port, either set up only one path to the LUN
`access to the LUN only from the first HBA and one array controller port, either set up only one path to the LUN
`or configure the SAN switch zoning to enable access to the LUN from only the first HBA and one array
`or configure the SAN switch zoning to enable access to the LUN from only the first HBA and one array
`controller port. With two paths configured to the LUN (through both HBAs on a server blade, for example), a
`controller port. With two paths configured to the LUN (through both HBAs on a server blade, for example), a
`Windows setup failure message appears stating that a drive is unformatted, damaged, or formatted with a file
`Windows setup failure message appears stating that a drive is unformatted, damaged, or formatted with a file
`system that is incompatible with Windows.
`system that is incompatible with Windows.
`To deploy the Red Hat Linux operating system when multiple LUNs are presented before the operating system
`To deploy the Red Hat Linux operating system when multiple LUNs are presented before the operating system
`installation, modify the job and kickstart file to place the operating system partitions on the first LUN. By default,
`installation, modify the job and kickstart file to place the operating system partitions on the first LUN. By default,
`the deployment installs Linux partitions across the available LUNs. If only one LUN is presented during the
`the deployment installs Linux partitions across the available LUNs. If only one LUN is presented during the
`operating system installation, no changes to the kickstart file or job are necessary.
`operating system installation, no changes to the kickstart file or job are necessary.
`a. On the Deployment Server, copy and rename the kickstart file.
`a. On the Deployment Server, copy and rename the kickstart file.
`b. Modify the new kickstart file by replacing the autopart command with separate part command lines and
`b. Modify the new kickstart file by replacing the autopart command with separate part command lines and
`adding the ---ondisk=XXX option to each, where XXX is the device label.
`adding the --ondisk=XXX option to each, where XXXis the device label.
`For example for non-LVM:
`For example for non-LVM