To provision the operating system on a bare-metal blade, you create a system package for the operating system that you want to provision on the blade. Depending on the operating system and chipset combination that you are provisioning, you might need to include UCS-specific configuration settings in the system package. For more general information about creating a system package, see Creating-a-system-package.
The following table presents special guidelines for UCS-specific configuration that you must perform, depending on the specific operating system for which you are creating the system package:
| System package panel or tab | |
|---|
| | - Check Use script for disk partitioning.
In the script text box, you can use the following script (recommended), or provide a custom script. select disk 0
clean
create partition primary align=1024
select partition 1
active
format fs=NTFS LABEL="DISK_VOL" QUICK For SAN provisioning, in the Disk Drive field specify to which disk the actual SAN disk is mapped. For example, on Windows, the SAN disk might be mapped to disk-1 or disk-2.
For SAP provisioning, you can use the following script in the script text box: select disk 0
clean
select disk 2
clean
create partition primary
select partition 1
active
format FS=NTFS LABEL=”SAN_VOL” QUICK - Check Reboot after the script is executed.
|
| Include the following lines: X:\Windows\System32\BladeLogic\bootsect.exe /nt52 c:
MKDIR C:\BLPROV |
| | - Click the browse
 icon next to Mass storage drivers. - Navigate to the directory that contains the first driver that you want to add, and then click the txtsetup.oem file for that directory.
The mass storage drivers appear in the right pane. In the right pane, click the driver(s) that you want to add. Warning Delete any comma-separated entries that appear in the right pane after the driver names.
|
| | - In the Generated Unattend area, navigate to the ImageInstall component by expanding settings[@pass=WindowsPE] and component[@language=neutral].
- Under OSImage, select DiskID.
- In the Add/Replace XML Component box, select Replace selected node. Then type this entry in the box:
<DiskID>2</DiskID>
|
| | The Intel NIC (Intel 82598EB 10 Gigabit AF Dual Port Network Connection) available with UCS hardware requires the IXGBE driver. This driver is available by default with Redhat 5.3. However, IXGBE has a defect that can cause provisioning to fail, and Red Hat recommends a workaround. Note By default, the IXGBE driver compiles with the LRO (Large Receive Offload) feature enabled. This option offers the lowest CPU utilization for receives, but is completely incompatible with routing/IP forwarding and bridging. If enabling IP forwarding or bridging is a requirement, you must disable LRO using compile time options. If you do not disable LRO and then enable IP forwarding or bridging, you may experience low throughput or even a kernel PANIC. As the first step in the IXGBE workaround:
To cause the NIC to use legacy interrupts, in the Boot Kernel Parameters field, specify the following boot kernel parameter: pci=nomsi |
| As the second step in the IXGBE workaround:
Contact Red Hat support and obtain updated driver RPMs, and place the updated RPMs in the data store.
Then, in the kickstart file text box, type the following under the %post section: rpm -ivh url_to_RPMs Edit the kickstart entries by typing the following lines in the kickstart file text box. The second line disables IPV6, as the BMC Server Automation provisioning system does not support the IPV6 protocol. url --url
http://??DATA_STORE_IP??/??DATA_STORE.VIRTUAL_DIR??/??PATHTO ACTUAL DIRECTORY??
network --bootproto dhcp --device ??NET_DEVICE?? --noipv6 --nodns --hostname ??HOST_NAME??
|
| For SAN provisioning, in the Disk Drive field specify to which disk the actual SAN disk is mapped. The SAN disk might be mapped to sdb or sdc. |
| | For SAN provisioning, in the Disk Drive field specify to which disk the actual SAN disk is mapped. The SAN disk might be mapped to sdb or sdc. |