Dell Lifecycle Controller 1.2 User guide

LC1_2.book Page 1 Wednesday, November 18, 2009 9:42 AM

Dell™ Lifecycle Controller

Version 1.2

User Guide


Notes and Cautions

NOTE:

A NOTE indicates important information that helps you make better use of your computer.

CAUTION:

A CAUTION indicates potential damage to hardware or loss of data if instructions are not followed.

__________________

Information in this document is subject to change without notice.

© 2009 Dell Inc. All rights reserved.

Reproduction of these material in any manner whatsoever without the written permission of Dell Inc. is strictly forbidden.

Trademarks used in this text: Dell and the DELL logo are trademarks of Dell Inc.; Microsoft, Windows, and Windows Server are registered trademarks of Microsoft Corporation in the United States and/or other countries; Red Hat, Red Hat Linux, and Red Hat Enterprise Linux are registered trademarks of

Red Hat, Inc. in the United States and other countries; SUSE is a registered trademark of Novell, Inc. in the United States and other countries.

Other trademarks and trade names may be used in this document to refer to either the entities claiming the marks and names or their products. Dell Inc. disclaims any proprietary interest in trademarks and trade names other than its own.

August 2009


Contents

1

Overview . . . . . . . . . . . . . . . . . . . . . . . . . .

7

Remote Services . . . . . . . . . . . . . . . . . . .

7

Unified Server Configurator (USC) . . . . . . . . . .

8

2

Unified Server Configurator and Unified Server Configurator -

Lifecycle Controller Enabled

. . . . . . . . . 11

Common Features . . . . . . . . . . . . . . . . . . . .

11

Launching the Product . . . . . . . . . . . . . . .

12

Using the Wizards . . . . . . . . . . . . . . . . .

13

Accessing Help . . . . . . . . . . . . . . . . . . .

15

Viewing Readme . . . . . . . . . . . . . . . . . .

15

Updating USC - LCE . . . . . . . . . . . . . . . . .

15

Disabling the Product . . . . . . . . . . . . . . . .

15

Canceling a Request to

Enter System Services . . . . . . . . . . . . . . .

16

Using USC Settings Wizard . . . . . . . . . . . . .

16

Deploying the Operating System

Using the OS Deployment Wizard . . . . . . . . .

17

Hardware Diagnostics . . . . . . . . . . . . . . .

25

Repairing USC . . . . . . . . . . . . . . . . . . .

26

Repairing USC - LCE . . . . . . . . . . . . . . . .

26

Contents

3


How to Upgrade to an iDRAC6 Express Card . . . . . .

27

Installing the iDRAC6 Express Card . . . . . . . . .

27

Transferring an iDRAC6 Express Card from an Existing System to a Different System . . .

28

Uninstalling the iDRAC6 Express Card . . . . . . .

28

Unified Server Configurator -

Lifecycle Controller Enabled Unique Features . . . . .

29

Updating the Platform using the Platform Update Wizard . . . . . . . . . . . .

29

Rolling Back to Previous BIOS and Firmware Versions . . . . . . . . . . . . . . .

32

Updating Devices That Affect Trusted

Platform Module Settings . . . . . . . . . . . . . .

33

Hardware Configuration . . . . . . . . . . . . . .

34

Configuring a Local FTP Server . . . . . . . . . . . . .

54

Requirements for a Local FTP Server . . . . . . . .

54

Creating the Local FTP Server

Using Dell Server Updates DVD . . . . . . . . . .

55

Accessing Updates on a Local FTP Server . . . . .

55

Configuring a Local USB Device . . . . . . . . . . . . .

55

Creating the Local USB Repository

Using Dell Server Updates DVD . . . . . . . . . .

56

3

Remote Service Features . . . . . . . . . . .

57

Web Services for Management . . . . . . . . . . . . .

57

Auto-Discovery . . . . . . . . . . . . . . . . . . . . . .

60

Configuring DHCP/DNS . . . . . . . . . . . . . . .

61

Enable and Disable Auto-Discovery Feature . . . .

61

Auto-Discovery Workflow . . . . . . . . . . . . .

62

4

Contents


Remote Operating System Deployment . . . . . . . . .

63

Remote Operating System

Deployment Main Features . . . . . . . . . . . . .

63

Remote Operating System

Deployment Interface . . . . . . . . . . . . . . .

63

Operating System Deployment

Typical Use Case Scenario . . . . . . . . . . . . .

66

A

Troubleshooting and

Frequently Asked Questions

. . . . . . . . . . 69

Error Messages . . . . . . . . . . . . . . . . . . . . .

69

Frequently Asked Questions . . . . . . . . . . . . . . .

82

Glossary

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Index

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Contents

5


6

Contents


Overview

In order to provide new and robust server management capabilities, the Unified Server Configurator/Unified Server Configurator - Lifecycle

Controller Enabled (USC/USC-LCE) software product has been enhanced to include additional remote services functionality. Since this addition allows for a comprehensive approach to server management, the entire set of software components is now called Lifecycle Controller 1.2 (LC 1.2).

The LC 1.2 software components are built upon the integrated Dell Remote

Access Controller 6 (iDRAC6) Express card and the Unified Extensible

Firmware Infrastructure (UEFI) system firmware. The iDRAC6 works together with the UEFI firmware to access and manage every aspect of the hardware, including component and subsystem management that is beyond the traditional BMC (Baseboard Management Controller) capabilities.

Remote server management is accomplished using the network for programmatic web services, while command line (CLI) and graphical user interfaces (GUI) are provided by the iDRAC6 card in an operating system-and system-power-state independent manner. The UEFI environment provides the local console interface, and the infrastructure for locally and remotely managing system components.

The remote services functionality enables consoles, such as the Dell Management

Console (DMC) and partner consoles, to access LC 1.2 features in a pre-operating system environment. USC/USC-LCE provides an embedded solution on the local server to assist with provisioning in a pre-operating system environment.

Remote Services

Remote services are accessible over the network using a secured web services interface and can be programmatically utilized by applications and scripts.

Remote services enables existing consoles to perform one-to-many bare metal server provisioning. The combination of a new Auto-discovery feature to identify and authenticate the attached Dell system to the network and integration with one-to-many management consoles reduces the manual steps required for server provisioning. Additionally, remote services provides remotely accessible operating system deployment related features that

Overview

7

LC1_2.book Page 8 Wednesday, November 18, 2009 9:42 AM simplifies the tasks involved in operating system and driver installation.

For more information on the features supported by the remote services

provisioning solution, see "Remote Service Features."

Unified Server Configurator (USC)

Unified Server Configurator (USC): Base-level product that uses BMC and provides operating system deployment, hardware diagnostics, and USC settings capabilities.

Unified Server Configurator - Lifecycle Controller Enabled (USC - LCE):

Full-featured product that uses iDRAC6 Express and Enterprise cards, and provides platform updates, hardware configuration, operating system deployment, hardware diagnostics, USC settings, dedicated NIC port, virtual KVM, and virtual media capabilities. Dell systems series 200-500 can be upgraded to USC-LCE. For more information, see your

Hardware Owner’s Manual.

For information on the supported sytems and operating systems, see the Dell

Systems Software Support Matrix.

Depending on your system configuration, USC or USC - LCE will display the

features that are supported by the system. See "Table 1-1" for more details.

8

Overview


Table 1-1.

Product Classification

Dell

System Options

Series

Available Remote

System Management

Device

USC or

USC-LCE

Available Features

100 No Options Embedded BMC USC

BMC - Operating System

Deployment, Diagnostics,

Settings

200 to

500

Standard

Optional

Embedded BMC

Embedded BMC + iDRAC6 Express

Card

Embedded BMC + iDRAC6 Express card + iDRAC6 Enterprise card

USC



Settings

USC-LCE



Settings iDRAC6 Express - adds

Platform Update,

Hardware Configuration,

Driver Repository

USC-LCE



Settings iDRAC6 Express - adds

Platform Update,


Driver Repository iDRAC6 Enterprise - adds

Full Remote Management,

Dedicated NIC port,

Virtual KVM, Virtual Media,

Virtual Flash

Overview

9


Table 1-1.

Product Classification (continued)

Dell

System Options

Series

Available Remote

System Management

Device

USC or

USC-LCE

Available Features

600 to

900

Standard

Optional*

Embedded BMC with iDRAC6

Express card

Embedded BMC with iDRAC6

Express card + iDRAC6

Enterprise card

USC-LCE

BMC with iDRAC6

Express -Operating System


Settings, Platform Update,


Driver Repository

USC-LCE

BMC with iDRAC6

Express - Operating System


Settings, Platform Update,


Driver Repository iDRAC6 Enterprise - adds

Full Remote Management,

Dedicated NIC port,

Virtual KVM, Virtual Media,

Virtual Flash

* For Dell modular systems — BMC, iDRAC6 Express card, and iDRAC6 Enterprise card are included as standard configurations.

10

Overview


Unified Server Configurator and

Unified Server Configurator - Lifecycle

Controller Enabled

Unified Server Configurator (USC) and Unified Server

Configurator-Lifecycle Controller Enabled (USC - LCE) reside on an embedded flash memory card and are embedded configuration utilities that enable systems and storage management tasks from an embedded environment throughout your system’s life cycle. USC and USC - LCE are similar to a BIOS utility in that they can be started during the boot sequence

and can function in a pre-operating system environment. "Table 1-1"

details the Dell system series, remote system management device options, USC or

USC-LCE, and available features.

Using USC, you can download drivers for operating system installation from the

Dell FTP website at ftp.dell.com or using local devices such as a USB device or the Dell Systems Management Tools and Documentation or the Dell Server

Updates DVD. You can also deploy an operating system, or run Hardware

Diagnostics to validate the system and attached hardware. Depending on your system, you can upgrade from a Baseboard Management Controller (BMC) to an iDRAC6 Express or an iDRAC6 Enterprise card; this hardware upgrade will also

upgrade USC to USC - LCE. See "How to Upgrade to an iDRAC6 Express Card"

and the Hardware Owner’s Manual for your system for more information on how to upgrade. Using USC - LCE, you can quickly identify, download, and apply system updates without searching the Dell Support site at support.dell.com.

You can also configure BIOS and system devices (such as NIC, RAID, and iDRAC), deploy an operating system, and run Hardware Diagnostics to validate the system and attached hardware.

Common Features

This section contains the features that are common to both USC and

USC - LCE. Any additional steps or information required for USC - LCE tasks are noted and provided.

USC and USC - LCE

11


Launching the Product

To launch either USC or USC - LCE, boot the system and press the <F10> key within 10 seconds of the Dell logo being displayed during the system boot process to enter System Services.

If the system is in one of the following states, pressing <F10> will not allow you to enter System Services:

• System Services disabled — If you power on or restart your system while iDRAC is initializing, the message System Services disabled will display during the system boot process. This situation happens if you power on your system immediately after AC is applied to the system, or if you restart the system immediately after resetting iDRAC. To avoid this issue, wait about a minute after resetting iDRAC to restart your system, thus allowing enough time for iDRAC to complete initialization.

If the message System Services disabled still displays, then the

product may have been manually disabled. See "Disabling the Product" for

information on how to enable USC or USC - LCE.

• System Services update required — If the message System Services update required appears when you boot your system, the embedded device that stores the product may contain corrupted data.

To resolve the issue, update the product by executing USC or USC - LCE

Dell Update Package (DUP). See the Dell Update Packages User’s Guide at support.dell.com/manuals for more information.

If an operating system is not installed on the system or if executing the

DUP does not fix the problem, run USC or USC - LCE repair package.

See "Repairing USC" or "Repairing USC - LCE" for more information.

• System Services not available — Another process is currently using iDRAC. Dell recommends waiting 30 minutes for the current process to complete; then, reboot your system and try to enter USC or

USC - LCE again.

NOTE:

If you believe the system is in an error condition or if you cannot

wait the recommended 30-minute time period, see "Canceling a Request to

Enter System Services." After rebooting, try to enter USC or USC - LCE again.

12

USC and USC - LCE


The first time you launch USC or USC - LCE, it displays USC Settings wizard that allows you to configure your preferred language and network

settings. See "Using USC Settings Wizard" for more information.

Using the Wizards

Wizard Description

USC and USC - LCE provide the following wizards based on your system’s configuration:

• OS Deployment — Enables you to install an operating system. See

"Deploying the Operating System Using the OS Deployment Wizard" for

more information.

• Hardware Diagnostics — Enables you to perform diagnostics to validate the memory, I/O devices, CPU, physical disks, and other peripherals.

See "Hardware Diagnostics" for more information.

• USC Settings — Enables you to specify the language, keyboard layout,

and network settings to be used with USC or USC-LCE. See "Using USC

Settings Wizard" for more information.

USC - LCE provides the following additional wizards based on your system’s configuration:

• Platform Update — Enables you to download and apply updates for your system. You can access the updates from ftp.dell.com or a

USB device attached to your system. See "Updating the Platform using the

Platform Update Wizard" and "Configuring a Local USB Device" for

more information.

• Hardware Configuration — Enables you to configure system devices.

See "Hardware Configuration" for more information.

Along with the above mentioned wizards, USC-LCE provides following options:

• Home — Enables you to navigate back to Home screen.

• About — Enables you to view the version information of USC-LCE and

UEFI. Click View Readme in the About wizard to view USC-LCE readme.

USC and USC - LCE

13


Launching a Wizard

USC and USC - LCE display the available wizards in the left pane. Click the wizard you want to launch, and then follow the instructions displayed in the right pane.

Wizard Task Flow USC

When using USC for the first time, Dell recommends you run the following wizards listed in order:

• USC Settings — You do not need to run this wizard again unless you want to change the language, keyboard, or network settings.

• OS Deployment — Run this wizard to install operating system.

• Hardware Diagnostics — Ensure that you maintain your system by running diagnostics on a regular basis.

Wizard Task Flow USC - LCE

When using USC - LCE for the first time, Dell recommends you run the following wizards listed in order:

• USC Settings — You do not need to run this wizard again unless you want to change the language, keyboard, or network settings.

• Platform Update — Download and apply any updates. Ensure that you run the Platform Update wizard regularly so that your system is up to date.

• Hardware Configuration — Run this wizard to configure your system devices.

• OS Deployment — Run this wizard to install operating system.

• Hardware Diagnostics — Ensure that you maintain your system by running diagnostics on a regular basis.

14

USC and USC - LCE


Accessing Help

Each USC or USC - LCE screen has a Help button in the upper-right corner.

Click Help to display help for the current screen.

Viewing Readme

Click About → View Readme to display the Readme file.

Updating USC - LCE

You can update to the latest version of USC - LCE using the Platform

Update wizard. Dell recommends running the Platform Update wizard on a

regular basis to access updates as they become available. See "Updating the

Platform using the Platform Update Wizard" for more information.

Disabling the Product

You can disable USC or USC - LCE to prevent your system from entering it on start-up:

1 Press <Ctrl><e> when prompted during system start-up.

NOTE:

You must press <Ctrl><e> within 5 seconds of when the message displays.

The iDRAC6 Configuration Utility page displays.

2 Navigate to System Services.

3 Select Disable System Services.

4 Save your changes and exit the iDRAC6 Configuration Utility page menu. The system reboots automatically.

To enable the product, repeat "step 1" and "step 2", and then select Enable

System Services.

USC and USC - LCE

15


16

Canceling a Request to Enter System Services

If USC or USC - LCE causes the system to repeatedly reboot, you can cancel a request to enter System Services.

CAUTION:

This action cancels all tasks USC or USC - LCE is in the process of executing. Dell strongly recommends that you cancel the request to enter System

Services only when absolutely necessary.


NOTE:



2 Navigate to System Services.

3 Select Cancel System Services.

Save your changes and exit the iDRAC6 Configuration Utility page.

The system reboots automatically.

Using USC Settings Wizard

USC Settings wizard enables you to specify the language, keyboard layout, and network settings for USC or USC - LCE.

NOTE:

USC settings apply only to USC or USC - LCE and do not apply to the system or any other application running on the system.

1 Launch USC Settings Wizard: a Boot your system and press the <F10> key within 10 seconds of the

Dell logo being displayed.

b Wait until USC Home screen is displayed then, click USC Settings in the left pane.

2 Click Language and Keyboard in the right pane.

NOTE:

Use the up-arrow and down-arrow keys to access all options on the

Language and Keyboard Type drop-down menus. a b c

Select the language from the Language drop-down menu.

Select the type of keyboard you are using from the Keyboard Type drop-down menu.

Click Finish.

USC and USC - LCE


3 Click Network Settings in the right pane.

a Use the NIC Card drop-down menu to select the NIC card you want to configure on your system.

b Use the IP Address Source drop-down menu to select either No

Configuration, DHCP, or Static IP.

NOTE:

The IP Address Source function only supports IPv4.

• No Configuration - Select if you do not want to configure your

NIC.

• DHCP - Select to obtain an IP address from a DHCP server.

• Static IP - Select to use a static IP address. Specify the following

IP address properties. If you do not have this information, see your network administrator.

– IP Address

– Subnet Mask

– Default Gateway

– DNS Address c Click Finish.

NOTE:

If USC settings are not configured correctly, an error message is displayed.

Deploying the Operating System Using the OS Deployment Wizard

The OS Deployment wizard assists you in installing an operating system on your system.

USC does not provide a local operating system drivers repository that may be required for operating system installation. You have to download the operating system drivers from the Dell FTP website at ftp.dell.com or use a local source that has drivers on it — for example, Dell Systems Management

Tools and Documentation DVD or a local USB device.

USC - LCE provides a local repository for drivers that may be required for operating system installation, depending on which operating system you are installing. The OS Deployment wizard extracts these drivers and copies them to a staging directory. For supported Microsoft

®

Windows

® operating systems, these extracted drivers are installed during the operating system installation. For supported Linux operating systems,

USC and USC - LCE

17

LC1_2.book Page 18 Wednesday, November 18, 2009 9:42 AM such as Red Hat

®

Enterprise Linux

®

versions 4.7, 4.8, 5.2, and 5.3 and

SUSE

®

Linux Enterprise Server version 10 SP2, you must manually install the extracted drivers after the operating system installation is completed.

However, starting with Red Hat Enterprise Linux version 5.4, SUSE Linux

Enterprise Server version 10 SP3, 11 and later installs, the extracted drivers

are during the operating system installation. See "Deploy the Operating

System" for more information.

NOTE:

Although USC - LCE comes with embedded drivers that are factory installed, there may be more current drivers available. You should run the Platform Update wizard to ensure that you have the most current drivers before installing the operating system.

Before installing the operating system, the OS Deployment wizard detects if a boot device is available. A boot device is a physical disk, virtual disk, or other storage device on which the operating system can be installed.

If your system has a RAID controller, you can configure a virtual disk and choose to use the virtual disk as the boot device.

If your system does not have a RAID controller or if you choose to bypass the optional RAID configuration, the OS Deployment wizard installs the operating system to a default location, which is typically the disk identified as

Disk 0 in the BIOS utility.

Launch the Operating System Deployment Wizard

1 To launch USC, boot your system and press the <F10> key within 10 seconds of the Dell logo being displayed.

2 Click OS Deployment in the left pane.

3 Click Deploy OS in the right pane.

4 For USC, continue with the "Select the Operating System Driver Source

Location (for USC only)" procedure that follows.

5 For USC - LCE, if your system has a RAID controller, continue with

"Optional RAID Configuration." If your system does not have a RAID

controller, continue with "Select an Operating System."

18

USC and USC - LCE


Select the Operating System Driver Source Location

(for USC only)

Use this screen to select the driver required for operating system installation.

You can download operating system drivers from an online repository or from a local drive.

NOTE:

The text boxes or drop-down menus under Online Repository and Local

Drive do not become active until you select the corresponding Online Repository or

Local Drive check box.

1 Select either Online Repository or Local Drive.

Online Repository

Select Online Repository to download drivers from an FTP server.

Enter the appropriate information according to the method you are using to access the FTP server.

NOTE:

If you use a firewall, you should configure it to allow outgoing FTP traffic on port 21. The firewall must also be configured to accept incoming FTP response traffic.

NOTE:

Currently, USC supports only anonymous FTP login.

• To download drivers from the online repository (Dell FTP server), you must enter ftp.dell.com in the Address field. or

To download drivers from a locally-configured online repository, in the

Address field you must specify the server host name or the IP address of the server on which the drivers reside. For information on setting

up local FTP server, see "Configuring a Local FTP Server."

• To download drivers by using a proxy server to access an FTP server, you must specify:

• Proxy Server — The server host name or the IP address of the proxy server

• Proxy Port — The port number of the proxy server

USC and USC - LCE

19


• Proxy Type — The type of proxy server

NOTE:

HTTP and SOCKS 4 proxy types are supported by USC.

• Proxy User Name — The user name required for authentication on the proxy server

• Proxy Password — The password required for authentication on the proxy server

2 Select Save Locally to save the drivers locally from the online repository.

From the Save Locally drop-down menu, select the USB drive to save the system drivers.

Local Drive

Select Local Drive if the drivers are available from a USB device or

Dell Systems Management Tools and Documentation DVD. For

information on setting up a USB device for updates see "Configuring a

Local USB Device."

3 Click Next.

If your system has a RAID controller, continue with "Optional RAID

Configuration." If your system does not have a RAID controller, continue

with "Select an Operating System."

Optional RAID Configuration

If your system has a RAID controller, you have the option of launching the

RAID Configuration wizard and configuring a virtual disk as the boot device.

NOTE:

If your system does not have a RAID controller, the OS Deployment

wizard bypasses the RAID configuration option and goes directly to "Select an

Operating System."

NOTE:

For S100 /S300 controllers, virtual disks cannot be created using the

RAID Configuration Wizard in USC - LCE. To create RAID, use the controller utilities by pressing <Ctrl><R> when prompted during system start-up.

20

USC and USC - LCE


To configure RAID:

• Select Configure RAID Now and click Next. This option launches the RAID Configuration wizard. After RAID configuration is complete, you will return to the OS Deployment wizard.

To bypass RAID configuration:

• Select Go Directly to OS Deployment and click Next. This option launches the OS Deployment wizard. If you select this option, the operating system will be installed on the default boot device identified

in the BIOS utility. Continue with "Select an Operating System."

Deploy the Operating System

The drivers required by the operating system, or recommended for updating your system after installation, are extracted to a temporary location.

These files are deleted after an 18-hour period or when you press the <F10> key to either cancel operating system installation or re-enter

USC after rebooting.

NOTE:

During the 18-hour period when the drivers are extracted to the temporary location, you cannot update USC or USC-LCE, drivers, or hardware diagnostics using a DUP after the operating system is installed, or the DUP will display a message that another session is open.

Select an Operating System

Use the following steps to select an operating system:

1 Select the operating system you want to install and click Next.

2 USC or USC - LCE extracts the drivers required by the operating system you selected. The drivers are extracted to an internal USB drive named OEMDRV.

3 After the drivers are extracted, USC or USC - LCE prompts you to insert the operating system installation media.

NOTE:

For Red Hat Enterprise Linux 4.

x server and Red Hat Enterprise Linux 5.x server, the drivers are extracted to OEMDRV under /oemdrv/*.rpm

.

For SUSE Linux Enterprise Server 10 SP2, the drivers are extracted under

/linux/suse/x86_64-sles10/install/*.rpm

.

USC and USC - LCE

21


22

NOTE:

When installing the Microsoft Windows operating system, the extracted drivers are automatically installed during the operating system installation. When installing the Red Hat Enterprise Linux 4.x operating system, the operating system installation uses native drivers. After the Linux installation is complete, you need to

manually install the drivers extracted by USC or USC-LCE. See "Update Drivers for

Linux Systems Only" for more information.

Kickstart Installation for the Linux Operating System

If you are using a kickstart installation for the Linux operating system, provide the following information in the post-installation script:

• Command to mount the USB device containing the operating system drivers labeled OEMDRV. For example: mkdir OEMDRV mount /dev/sdc1 /mnt/OEMDRV

• Path to the operating system drivers on the OEMDRV drive:

For Red Hat Enterprise Linux: /oemdrv/*.rpm

For SUSE Linux Enterprise Server:


• Command to install the drivers: rpm -Uvh *.rpm

Insert the Operating System Media

To insert the operating system media:

1 Insert the operating system installation media when prompted and click Next.

NOTE:

USC supports internal SATA optical drives and USB optical drives and

USC - LCE supports internal SATA optical drives, USB optical drives, and virtual media devices. If the installation media is corrupt or not readable, then USC and

USC-LCE may be unable to detect the presence of a supported optical drive. In this case, you may receive an error message stating that no optical drive is available.

If the media is not valid (if it is the incorrect CD or DVD, for example), a message displays requesting that you insert the correct installation media.

NOTE:

FOR USC - LCE ONLY: Virtual media is supported through iDRAC. See the

User Guide for your system’s iDRAC device for more information on setting up virtual media through iDRAC.

USC and USC - LCE


Reboot the System

Use the following steps to reboot the system:

1 Click Finish to reboot the system and continue with the operating system installation. Upon reboot, the system boots to the operating system installation media.

CAUTION:

During Red Hat 5.x installation, you will receive a warning that a read-only file system was detected; Linux has detected the temporary storage area of USC and USC-LCE that stores updates for your system. Click OK, and a second warning will appear indicating that the read-only file system has a loop partition layout and that it needs to be formatted. Click the Ignore drive button. You may see both warnings several times during the course of Red Hat 5.x installation.

CAUTION:

During the beginning of Windows Server

®

2003 installation, the installer will automatically detect and possibly assign the default drive letter C to USC and USC-LCE temporary storage device OEMDRV. Creating a new

Windows-bootable system partition on the hard-disk will assign the partition to a drive letter other than C; this is standard Windows installer behavior. To assign

the new partition to C, see "Assign a Windows-Bootable System Partition to the C:

Drive" for more information.

NOTE:

When the system reboots after you click Finish, you may be prompted to press a key before booting to the operating system installation media. If you do not press a key, the system boots to the hard-disk and not the operating system installation media.

NOTE:

In the event that the operating system installation is interrupted and the system reboots before installation completes, you may be prompted to press a key in order to boot from the operating system installation media.

NOTE:

You can cancel the operating system installation by pressing the <F10> key.

Pressing the <F10> key at any point during the installation process or while rebooting causes any drivers provided by the OS Deployment wizard to be removed.

NOTE:

Microsoft Windows Server 2008 UEFI operating system installations are not currently supported.

NOTE:

After the operating system is installed, you cannot update USC or USC-LCE by running a DUP in the operating system environment for the next 18 hours.

USC and USC - LCE

23


Update Drivers for Linux Systems Only

On the following operating systems, Dell recommends that you update your system with the extracted drivers after installation. The drivers are extracted to a drive (or device) named OEMDRV.

• Red Hat Enterprise Linux 4.8 server — The location of the drivers on the

OEMDRV

drive after installation is:

/oemdrv/*.rpm

• Red Hat Enterprise Linux 5.3 server — The location of the drivers on the

OEMDRV

drive after installation is:

/oemdrv/*.rpm

• SUSE Linux Enterprise Server 10 with Service Pack 2 — The location of the drivers on the OEMDRV drive after installation is:


Use the following command to install the drivers: rpm -Uvh *.rpm

Assign a Windows-Bootable System Partition to the C: Drive

After you have completed USC or USC - LCE portion of Windows Server

2003 installation, your server will reboot and begin the text-mode portion of the installation. During this phase, you may need to perform the following steps to ensure Windows installs to your C: drive.

NOTE:

Following these instructions after Windows Server 2003 setup presents you with a list of existing drive partitions and/or unpartitioned space available on your computer.

1 Select the unpartitioned space, and then press <c> to create a hard-disk partition. Follow the on-screen instructions to create a partition.

NOTE:

The partition may not be enumerated as a C: drive.

2 Select the newly-created partition, and then press <d> to delete the partition. Follow the on-screen instructions to delete the partition.

24

USC and USC - LCE


3 Select the unpartitioned space again, and then press <c> to create a primary hard-disk partition.

NOTE:

The partition will now be enumerated as C: drive.

4 Follow the on-screen instructions to create a partition. Windows will now install on the C: drive.

See http://support.microsoft.com/kb/896536 for more information on assigning the Windows-bootable system partition to the C: drive.

Hardware Diagnostics

Utilizing the Hardware Diagnostics utility, Dell recommends that you run diagnostics as part of a regular maintenance regimen to validate that the system and attached hardware are functioning properly. Because the diagnostics utility has a physical (as opposed to logical) view of attached hardware, this utility may be able to identify hardware problems that the operating system and other online tools cannot. You can use the hardware diagnostics utility to validate the memory, I/O devices, CPU, physical disks, and other peripherals.

Performing Hardware Diagnostics

To start the hardware diagnostics utility, click Hardware Diagnostics in the left pane and click Run Hardware Diagnostics in the right pane. When the diagnostics utility launches, follow the instructions on the screen.

NOTE:

You must reboot your system to exit the Hardware Diagnostics utility and press <F10> to re-enter USC or USC-LCE.

The results of the diagnostics tests are displayed on the screen when the tests complete. The test results describe the problems found. You can use this information to search the Dell Support website at support.dell.com for details on resolving the problem.

If you want to exit the Hardware Diagnostics utility, press the <Esc> key.

Pressing the <Esc> key causes the system to reboot.

USC and USC - LCE

25


26

Updating the Hardware Diagnostics Utility

For Systems Supporting USC

Download the required Dell Update Package (DUP) from Dell Support site at support.dell.com. Run the DUP as an executable in the installed operating system.

For Systems Supporting USC - LCE

Use the Platform Update wizard to update the hardware diagnostics utility.

See "Updating the Platform using the Platform Update Wizard" for more

information. Alternatively, you can also download the required Dell Update

Package (DUP) from Dell Support site at support.dell.com and run the DUP as an executable in the installed operating system.

Repairing USC

If the message System Services update required appears when you boot up, the embedded device that stores USC may contain corrupted data. To resolve the issue, you must first attempt to update USC by executing

USC Dell Update Package (DUP). See the Dell Update Packages User’s Guide available at support.dell.com/manuals for more information.

Repairing USC - LCE

If the message System Services update required appears when you boot up, the embedded device that stores USC - LCE may contain corrupted data. To resolve the issue, you must first attempt to update

USC - LCE by executing USC - LCE Dell Update Package (DUP). See the

Dell Update Packages User’s Guide available at support.dell.com/manuals for more information. If running the DUP does not solve the problem, use USC - LCE repair package:

1 Go to ftp.dell.com → LifecycleController and download the file named

USC_1.1.0_Rep_A00.usc (or newer version) to a temporary location.

2 Connect to iDRAC on your system using the iDRAC Web interface.

For more information on iDRAC, see the Integrated Dell Remote Access

Controller 6 (iDRAC6) User’s Guide.

3 From the iDRAC Web interface, click Remote Access.

4 Select the Update tab, and then browse to USC - LCE Repair Package you downloaded from ftp.dell.com.

USC and USC - LCE


5 Click Next, and then click OK to confirm the upload. Allow the process to

complete before you continue to "step 6."

6 Reboot your system, and then press the <F10> key to enter USC - LCE.

7 Complete the installation of all recommended updates. See "Updating the

Platform using the Platform Update Wizard" for more information.

When updates are complete, your system automatically reboots.

8 While the system reboots, press the <F10> key again to enter

USC - LCE.

If a warning message appears on the initial USC - LCE screen, you must

repeat "step 7" until the server is in a fully-recovered state.

NOTE:

Updates that are required for a complete system recovery are pre-selected by USC - LCE. Dell highly recommends running all selected updates on your system.

How to Upgrade to an iDRAC6 Express Card

This section provides information about installing an iDRAC6 Express card, transferring the iDRAC6 Express card from one system to another system, and Uninstalling iDRAC6 Express card. This hardware upgrade will also upgrade USC to USC - LCE.

NOTE:

This is applicable only on Dell System Series 200-500.

Installing the iDRAC6 Express Card

1 Turn off the system, including any attached peripherals, and disconnect the system from the electrical outlet.

NOTE:

To discharge the residual power in the system, press the power button once.

2 Insert the iDRAC6 Express card into the iDRAC6 Express slot.

See the Hardware Owner’s Manual for your system for more information on Installing iDRAC6 Express Card.

USC and USC - LCE

27


28

3 Reconnect the system and peripherals to their power sources.

iDRAC automatically starts. Wait one minute, before switching on the system, to allow the iDRAC to fully start.

4 Switch on the system, and then press <F10> to enter USC.

USC automatically detects the iDRAC6 Express card installed on the system and completes the upgrade process.

If the installation is successful, you are able to boot to Unified Server

Configurator — Lifecycle Controller Enabled.

NOTE:

If the installation fails, you must upgrade iDRAC. See the Integrated

Dell Remote Access Controller User Guide for more information. After you have upgraded iDRAC, repeat the above instructions.

Transferring an iDRAC6 Express Card from an Existing System to a

Different System

If the iDRAC6 Express card is transferred from one system to another:

•

The rollback feature is unavailable on the new system. See "Rolling Back to

Previous BIOS and Firmware Versions" for more information.

• All pending USC-LCE tasks that are in the process of execution are deleted on the new system.

• Run Platform Update wizard to download the appropriate driver pack for the new system.

NOTE:

The driver pack is deleted if the iDRAC6 Express card is transferred to a different Dell system. For example, if you move the iDRAC6 Express card from

Dell R410 system to Dell T410 system, the driver pack is deleted.

Uninstalling the iDRAC6 Express Card

1 Turn off the system, including any attached peripherals, and disconnect the system from the electrical outlet.

NOTE:

To discharge the residual power in the system, press the power button once.

2 Remove the iDRAC6 Express card from the iDRAC6 Express slot. See the

Hardware Owner’s Manual for your system for more information on

Installing iDRAC6 Express Card.

USC and USC - LCE


3 Reconnect the system and peripherals to their power sources.

4 Switch on the system, and then press <F10> to enter USC.

Unified Server Configurator - Lifecycle Controller

Enabled Unique Features

This section contains the features that are only available in USC - LCE.

For information on features common to USC and USC - LCE

see "Common Features."

Updating the Platform using the Platform Update Wizard

Use the Platform Update wizard to view the current versions of the installed applications and firmware information. You can use the Platform Update

Wizard to display a list of available updates for your system. After you select the updates you want to apply, USC - LCE downloads and applies the updates.

NOTE:

To ensure optimal system performance and avoid system problems,

Dell recommends that you download and apply updates on a regular basis.

To run the Platform Update wizard, you need access to the Dell File Transfer

Protocol (FTP) server at ftp.dell.com. Alternatively, your system administrator may provide the updates on a local USB device or on a

Dell Server Update Utility DVD. Contact your system administrator to find out the preferred method for accessing updates in your organization.

See "Configuring a Local FTP Server" for more information.

NOTE:

If you are using FTP as your update method, you must configure the network card using USC - LCE USC Settings wizard before accessing the updates. See

"Using USC Settings Wizard" for more information.

View Current Version Information

1 Boot your system and press the <F10> key within 10 seconds of the Dell logo being displayed.

2 Click Platform Update in the left pane.

3 Click View Current Versions in the right pane.

USC and USC - LCE

29


Launch the Platform Update Wizard

1 Boot your system and press the <F10> key within 10 seconds of the

Dell logo being displayed.


3 Click Launch Platform Update in the right pane.

Select Download Method

You can download updates from Dell’s FTP server at ftp.dell.com using the

Platform Update wizard or from a local FTP server or from a local USB device or Dell Server Updates DVD.

NOTE:

To enable the text boxes and drop-down menus under local FTP server or

Dell FTP Server and USB Device, select the corresponding FTP Server or

Local Drive check box.

1 Select either FTP Server or Local Drive.

FTP Server

Select FTP Server to download updates from the configured FTP server using the Platform Update wizard. Enter the appropriate information according to the method you are using to access the FTP server.

NOTE:

If you use a firewall, you should configure it to allow outgoing

FTP traffic on port 21. The firewall must also be configured to accept incoming

FTP response traffic.

To download updates by using a proxy server to access the FTP server, you must specify:

• Address — The IP address of the local FTP server or ftp.dell.com.

• Proxy Server — The server host name of the proxy server

• Proxy Port — The port number of the proxy server

• Proxy Type — The type of proxy server

NOTE:

HTTP and SOCKS 4 proxy types are supported by USC - LCE.

30

USC and USC - LCE


• Proxy User Name — The user name required for authentication on the proxy server

• Proxy Password — The password required for authentication on the proxy server

Local Drive

Select Local Drive if you are accessing the updates from a local USB device or Dell Server Updates DVD. Select the appropriate volume label from the Local Drive drop-down menu.

See "Configuring a Local USB Device" for more information.

2 Click Next.

Select and Apply Updates

The Select Updates screen displays a list of available updates.

1 Select the check box for each update that you want to apply to your system. The components for which a more current update is available are selected by default.

If you want to compare the version of the update with the version currently installed on the system, compare the versions in the

Current and Available fields.

NOTE:

An ellipsis (...) appearing at the end of the displayed field indicates that the full value is not displayed. To view more detailed information, select the field; the information appears below the comparison report.

• Component — Displays the available updates. Select the check box for each update you want to apply.

• Current — Displays the component version currently installed on the system.

• Available — Displays the version of the available update.

USC and USC - LCE

31


2 Click Apply.

NOTE:

The system reboots after the update process is complete. When applying more than one update, the system may need to reboot between updates. In this case, the system boots directly into USC - LCE and continues the update process.

No action on your part is required when the system reboots to complete the update process.

NOTE:

If the iDRAC firmware update is interrupted for any reason, you may need to wait for up to 30 minutes before attempting another firmware update.

NOTE:

USC-LCE does not support the update or rollback of PERC 5/E Adapter for external storage, SAS 5i/R Adapter for tape, PERC S100 and PERC S300 Adapters, and Intel™ NIC Adapters.

Rolling Back to Previous BIOS and Firmware Versions

USC - LCE enables you to roll back to a previously-installed version of

BIOS or firmware. Dell recommends that you use this feature if you have a problem with the currently-installed version and want to revert to the previously-installed version.

NOTE:

Only BIOS and firmware can be rolled back. USC - LCE, the hardware diagnostics application, and drivers needed for operating system (OS) installation cannot be rolled back to earlier versions.

This feature is available only if you have used the USC - LCE update feature to update BIOS and firmware, or if you have updated the system BIOS or firmware using a post-operating system Dell Update Package. If you have used other update methods, this feature is not available.

NOTE:

Power supply firmware does not support creation of a rollback image if it is updated using a post-operating system Dell Update Package.

NOTE:

If you have updated your system’s BIOS or firmware only once, the rollback feature offers the option of reverting to the factory-installed BIOS or firmware images. If you have updated your BIOS or firmware more than once, the factory-installed images are overwritten and you cannot revert to them.

32

Launch the Rollback Wizard

1 Boot your system to launch USC - LCE. When the Dell logo displays, press the <F10> key within 10 seconds.


3 Click Launch Platform Rollback in the right pane.

USC and USC - LCE


Select and Apply Rollbacks

The Platform Rollback screen displays a list of available rollback components.

1 Select the check box of each rollback image that you want to apply to the system.

To compare the version of the rollback image with the version currently installed on the system, compare the versions in the Current and

Previous fields.

NOTE:

An ellipsis (...) appearing at the end of the displayed field indicates that the full value is not displayed. To view more detailed information, select the field; the information appears below the comparison report.

• Component — Displays the available updates; select the check box of each update you want to apply.

• Current — Displays the component version currently installed on the system.

• Previous — Displays the version of the rollback image.

2 Click Apply.

NOTE:

The system reboots after the update process is complete.

When applying more than one update, the system may need to reboot between updates. In this case, the system boots directly into USC - LCE and continues the update process. This is an unattended update process.

Updating Devices That Affect Trusted Platform Module Settings

If BitLocker protection is enabled on your system, updating certain components requires you to enter a recovery password or insert a USB flash drive containing a recovery key during the next system boot. This situation occurs only if the Trusted Platform Module (TPM) security setting is set to

On with Pre-boot Measurements.

NOTE:

For information on how to set TPM settings, see the BIOS User Guide available at support.dell.com/manuals.

When USC - LCE detects that TPM security is set to On with Pre-boot

Measurements, a warning message displays indicating that certain updates require the recovery password or USB flash drive with the recovery key.

The warning message also indicates which components affect the BitLocker.

You can choose either not to update or to roll back those components by navigating to the Select Updates screen and deselecting the check boxes for the components.

USC and USC - LCE

33


Hardware Configuration

USC - LCE provides two different methods for configuring your hardware, both of which are available from the main Hardware Configuration screen:

• Configuration Wizards guide you through setting up system devices.

The Configuration Wizards include: Physical Security Configuration,

System Date/Time Configuration, iDRAC Configuration, and RAID Configuration.

• Advanced Configuration allows you to configure certain devices, such as

Network Interface Controllers (NICs) and the BIOS, using Human

Interface Infrastructure (HII).

NOTE:

Ensure that you understand the implications of HII before using the

Advanced Configuration feature. HII is part of the UEFI standard; USC - LCE

complies to UEFI version 2.1. See "Advanced Configuration" for more information.

Physical Security Configuration

Use the Physical Security Configuration Wizard to control access to the system control panel.

To launch the Physical Security Configuration Wizard:

1 Click Hardware Configuration in the left pane.

2 Click Configuration Wizards in the right pane.

3 Click Physical Security Configuration to launch the wizard.

4 Set System Control Panel Access to one of the following options:

• Disabled — You do not have access to information or control, other than the information displayed by the management controller, and you cannot specify actions.

• View Only — You can move through the data screens to obtain information using the system control panel interface.

• View and Modify — You can obtain information and make changes using the system control panel interface.

5 Click Finish to apply the changes.

To return to the Configuration Wizards screen, click Back.

To exit the wizard, click Cancel.

34

USC and USC - LCE


System Date/Time Configuration

Use the System Date/Time Configuration Wizard to set the date and time for the system.

To launch the System Date/Time Configuration Wizard:



3 Click System Date/Time Configuration to launch the wizard.

The default system date and system time shown in USC - LCE is the date and time reported by the system BIOS.

4 Modify the System Date and Time (HH:MM:SS AM/PM) values, as required.

5 Click Finish to apply the changes.

To return to the Configuration Wizards screen, click Back.

To exit the wizard, click Cancel. iDRAC Configuration

Use the iDRAC Configuration Wizard to configure and manage iDRAC parameters.

This wizard is similar to the iDRAC Configuration Utility in the legacy

BIOS operation. You can use the wizard to configure iDRAC parameters applicable to the system, such as LAN, common IP settings, IPv4, IPv6, virtual media, and LAN user configuration.

To launch the iDRAC Configuration Wizard:



3 Click iDRAC Configuration to launch the wizard.

The following steps will walk you through the iDRAC Configuration Wizard: a

"LAN Configuration"

b c d

"Advanced LAN Configuration"

"Common IP Configuration"

"IPv4 Configuration"

USC and USC - LCE

35


36 g h f e

"IPv6 Configuration"

"Virtual Media Configuration"

"LAN User Configuration"

"Confirmation"

LAN Configuration

View or configure iDRAC LAN, IPMI over LAN, MAC address, and NIC selection.

• iDRAC LAN — Enables or disables the iDRAC NIC. Disabling iDRAC LAN deactivates the remaining controls.

• IPMI Over LAN — Enables or disables Intelligent Platform

Management Interface (IPMI) commands on the iDRAC

Local Area Network (LAN) channel.

• MAC Address — Enables you to view the Media Access Control (MAC) address that uniquely identifies each node in a network (read-only).

• NIC Selection — Enables you to view or edit the NIC mode using the following mode options:

– Dedicated — This option enables remote access to utilize the dedicated network interface available on the Dell Remote Access

Controller (DRAC). Because the DRAC interface is not shared with the host operating system and routes management traffic to a separate physical network, it can be separated from the application traffic.

NOTE:

This option is available only if an iDRAC6 Enterprise controller is present in the system.

– Shared with failover — Select this option to share the network interface with the host operating system. The remote access device network interface is fully functional when the host operating system is configured for NIC teaming. The remote access device receives data through the LAN on motherboard LOM 1 and LOM 2, but it transmits data only through LOM 1. If LOM 1 fails, the remote access device fails over to LOM 2 for all data transmission. The remote access device continues to use LOM 2 for data transmission.

If LOM 2 fails, the remote access device fails over all data transmission back to LOM 1.

USC and USC - LCE


– Shared with failover - LOM 2 — Select this option to share the network interface with the host operating system. The remote access device network interface is fully functional when the host operating system is configured for NIC teaming. The remote access device receives data through the LAN on Motherboard LOM 1 and LOM 2, but transmits data only through LOM 2. If LOM 2 fails, the remote access device fails over to LOM 1 for all data transmission.

The remote access device continues to use LOM 1 for data transmission. If LOM 1 fails, the remote access device fails over all data transmission back to LOM 2.

NOTE:

If one LOM fails but is later restored, you can manually revert back to the original LOM settings by editing the NIC selection through the iDRAC

Hardware Configuration wizard.

– Shared with failover - All LOMS — Select this option to share the network interface with the host operating system. The remote access device network interface is fully functional when the host operating system is configured for NIC teaming. The remote access device receives data through NIC 1, NIC 2, NIC 3, and NIC 4; but it transmits data only through NIC 1. If NIC 1 fails, the remote access device will transmit data on NIC 2. If NIC 2 fails, the remote access device will transmit data on NIC 3. If NIC 3 fails, the remote access device will transmit data on NIC 4. If NIC 4 fails the remote access device fails over all data transmission back to NIC 1, but only if the original NIC 1 failure has been corrected.

NOTE:

Shared with failover - All LOMS option may not be available on iDRAC6 Enterprise controller.

Advanced LAN Configuration

1 Set additional attributes for VLAN, VLAN ID, VLAN priority,

Auto Negotiate, LAN speed, and LAN duplex.

• VLAN — Enables or disables the VLAN mode of operation and parameters. When VLAN is enabled, only matched VLAN ID traffic is accepted. When disabled, VLAN ID and VLAN Priority are not available, and any values present for those parameters are ignored.

• VLAN ID — Sets the VLAN ID value. Legal values fall in the range of

1 to 4094, as defined by IEEE 801.1g specification.

USC and USC - LCE

37


• VLAN Priority — Sets the VLAN ID priority value. Legal values fall in the range of 0 to 7, as defined by IEEE 801.11g specification.

• Auto Negotiate — Turns the auto-negotiate feature on or off. When auto-negotiate is on, it determines whether iDRAC automatically sets the Duplex Mode and Network Speed values by communicating with the nearest router or hub. When auto-negotiate is off, you must set the Duplex Mode and Network Speed values manually.

• LAN Speed — Configures the network speed to 100 Mb or 10 Mb to match the user's network environment.

NOTE:

This option is not available if Auto-Negotiate is set to On.

• LAN Duplex — Configures the duplex mode to Full or Half to match the user's network environment.

NOTE:

This option is not available if Auto-Negotiate is set to On.

2 Click OK to save your settings and return to the LAN Configuration menu.

3 Click Next to proceed to "Common IP Configuration."

Common IP Configuration

Register the iDRAC name, set the domain name from DHCP, and specify the domain name and host name string.

• Register iDRAC Name — If set to Yes, the iDRAC name is registered with the Domain Name System (DNS). If set to No, no registration takes place.

• iDRAC Name — Enables you to view or edit the iDRAC name to be used when registering with DNS. The iDRAC Name string can contain up to 63 printable ASCII characters. You can edit the iDRAC Name string when Register iDRAC Name is No. The information in this field is erased after updating the iDRAC firmware.

• Domain Name from DHCP — If set to Yes, iDRAC acquires the domain name from the Dynamic Host Configuration Protocol (DHCP) server.

If set to No, you must enter the domain name manually.

38

USC and USC - LCE


• Domain Name — Enables you to view or edit the iDRAC domain name to be used if it is not acquired from DHCP. You can specify a domain name when Domain Name from DHCP is set to No. The information in this field is erased after updating the iDRAC firmware.

• Host Name String — Enables you to specify or edit the host name associated with iDRAC. The information in this field is erased if iDRAC is reset to the original defaults or if the iDRAC firmware is updated.

The Host Name string can contain up to 62 ASCII printable characters.

Click Next to proceed to "IPv4 Configuration."

IPv4 Configuration

Enable or disable IPv4, and set the RMCP+ encryption key, IP address source, subnet mask, default gateway, and DNS server values.

• IPv4 — Enables or disables iDRAC NIC IPv4 protocol support.

Disabling IPv4 deactivates the remaining controls.

• RMCP+Encryption Key — Configures the RMCP+ encryption key using 0 to 40 hexadecimal digits (no blanks allowed). The default setting is all zeros (0).

• IP Address Source — Enables or disables the ability of the iDRAC NIC to acquire an IPv4 address from the DHCP server; deactivate or activate the Ethernet IP Address, Subnet Mask, and Default Gateway controls.

• Ethernet IP Address — Enables you to specify or edit a static IPv4 address for the iDRAC NIC. The IP address you enter in the Ethernet IP Address field is reserved, and used only when DHCP fails to resolve and assign an available IP address. The Ethernet IP Address field is limited to a maximum value of 255.255.255.255.

• Subnet Mask — Enables you to specify or edit the static subnet mask for the iDRAC NIC. The subnet mask defines the significant bit positions in the IPv4 address. The Subnet Mask string should be in the form of a netmask, where the more significant bits are all ones (1) with a single transition to all zeros (0) in the lower-order bits. For example:

255.255.255.0. The Subnet Mask field is limited to a maximum value of

255.255.255.255.

USC and USC - LCE

39


• Default Gateway — Enables you to specify or edit the static IPv4 default gateway for the iDRAC NIC. Requests that cannot be resolved locally are routed to this address. The Default Gateway field is limited to a maximum value of 255.255.255.255.

• Get DNS Servers from DHCP — If set to Yes, the iDRAC NIC acquires the Domain Name System (DNS) server information from the DHCP server, and deactivates the DNS Server 1 and DNS Server 2 controls. If set to No, the iDRAC NIC does not acquire the DNS Server information from the DHCP server, and you must manually define the DNS Server 1 and

DNS Server 2 fields.

• DNS Server 1 — Enables you to specify or edit the static IPv4 address for a primary DNS server. This IPv4 address is that of a DNS server utilized for name-to-IPv4 address resolution. The DNS Server 1 field is limited to a maximum value of 255.255.255.255.

• DNS Server 2 — Enables you to specify or edit the static IPv4 address for a secondary DNS server. In the event that DNS Server 1 does not produce results, the DNS Server 2 IPv4 address serves as a backup utilized for name-to-IPv4 address resolution. This field is limited to a maximum value of 255.255.255.255.

Click Next to proceed to "IPv6 Configuration."

IPv6 Configuration

Set IPv6, IP address source, ethernet IP address, IPv6 address, prefix length, default gateway, and DNS server values.

• IPv6 — Enables or disables the iDRAC NIC IPv6 protocol support.

Disabling IPv6 deactivates the remaining controls.

• IP Address Source — Enables or disables the ability of the iDRAC NIC to acquire an IPv6 address from the DHCP server. Disabling IP Address

Source deactivates the Ethernet IP Address, Prefix Length, and Default

Gateway controls.

40

USC and USC - LCE


• Ethernet IP Address — Enables you to specify or edit the static

IPv6 address for the iDRAC NIC when not provided by DHCP.

This field is limited to a maximum value of

FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF. The multi-cast (ff00:/8) and loopback (::1/128) values are not valid addresses for the Ethernet

IP address and/or the other address related fields described in this section.

IPv6 Address forms supported:

– X:X:X:X:X:X:X:X — In this preferred form, X represents the hexadecimal values of the eight 16-bit pieces of the address. You can omit leading zeros in individual fields, but you must include at least one numeral in every field.

– :: (two colons) — Using this form, you can represent a string of contiguous zero fields in the preferred form. The :: can only appear once in the address. You can also use this form to represent unspecified addresses (0:0:0:0:0:0:0:0).

– x:x:x:x:x:x:d.d.d.d — This form is sometimes more convenient when dealing with a mixed environment of IPv4 and IPv6 nodes. In this form, x represents the hexadecimal values of the six high-order 16-bit pieces of the address, and d represents the decimal values of the four low-order 8-bit pieces of the address (standard IPv4 representation).

• Prefix Length — Enables you to specify or edit the number of significant bits in the IPv6 address to be used as a prefix, up to a maximum of 128.

The prefix length number of bits in the Ethernet IP address is the netmask for the IPv6 network to which the iDRAC NIC belongs. The more significant bits that are defined, the fewer IPv6 addresses will be available on the network with the specified prefix.

• Default Gateway — Enables you to specify or edit the static IPv6 default gateway for the iDRAC NIC when not provided by DHCP. This is the address that will be used to route requests when they cannot be resolved locally. The Default Gateway field is limited to a maximum value of

FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF.

USC and USC - LCE

41


42

• Get DNS Servers from DHCP — If set to Yes, the iDRAC NIC acquires the Domain Name System (DNS) server information from the

DHCP server and deactivates the DNS Server 1 and DNS Server 2 controls. If set to No, the iDRAC NIC does not acquire the DNS server information from the DHCP server, and you must manually specify the

DNS Server 1 and DNS Server 2 fields.

• DNS Server 1 — Enables you to specify or edit the static IPv6 address for a primary DNS server when not provided by DHCP. The DNS Server 1 field is limited to a maximum value of

FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF. The iPv6 address is that of a DNS server utilized for name-to-IPv6 address resolution.

• DNS Server 2 — Enables you to specify or edit the static IPv6 address for a secondary DNS server when not provided by DHCP. In the event that

DNS Server 1 does not produce results, the DNS Server 2 iPv6 address serves as a backup DNS server utilized for name-to-IPv6 address resolution. The DNS Server 2 field is limited to a maximum value of

FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF.

Click Next to proceed to "Virtual Media Configuration."

Virtual Media Configuration

Set Virtual Media and Virtual Flash parameters.

NOTE:

The Virtual Media and Virtual Flash features are available only if the system includes iDRAC 6 Enterprise. The Virtual Flash feature is only available if an SD card is installed and enabled in the iDRAC.

• Virtual Media — Select attached, auto-attached, or detached mode. If set to Attach, the virtual media devices are available for use in the current operating environment. Virtual Media enables a floppy image, floppy drive, or CD/DVD drive from your system to be available on the managed systems console, as if the floppy image or drive were present (attached or connected) on the local system. If set to Detach, you cannot access virtual media devices. If set to Auto-Attach, the virtual media device is automatically mapped to the server every time the user physically connects a media.

NOTE:

For more information on supported virtual media devices, see the

Integrated Dell Remote Access Controller 6 (iDRAC6) User’s Guide available at support.dell.com/manuals.

USC and USC - LCE


• Virtual Flash — Enable or disable the use of flash memory that resides in the iDRAC file system. This memory can be used for persistent storage and accessed by the system. If set to Enabled, the virtual flash card is configured as a virtual drive; it appears in the boot order, allowing you to boot from the virtual flash card. If set to Disabled, virtual flash is not accessible.

NOTE:

To boot from the virtual flash, the virtual flash image must be bootable.

The virtual flash feature of iDRAC requires a formatted secure digital (SD) card that is 256 MB or greater. This feature can be enabled only if a valid image is present on the SD card. S ee the User Guide for your system’s iDRAC device for more information.

NOTE:

Dell-branded vFlash media is required for the virtual flash partition.

Click Next to proceed to "LAN User Configuration."

LAN User Configuration

Set account access, account-related attributes, and smart card authentication.

• Account Access — Enables or disables account access. Disabling account access deactivates all other fields on the LAN User Configuration screen.

• Account Username — Enables the modification of an iDRAC username.

The Account Username field accepts a maximum of 16 printable

ASCII characters.

• Password — Enables an administrator to specify or edit the iDRAC user's password. The Password string is encrypted and cannot be seen or displayed after this property is set. The Password field accepts a maximum of 20 characters.

• Confirm Password — Re-enter the iDRAC user's password to confirm.

USC and USC - LCE

43


• Account Privilege — Assigns the user's maximum privilege on the IPMI

LAN channel to one of the following user groups: Admin, Operator, User, or No Access.

– Admin — Privileges: Login to iDRAC, Configure iDRAC, Configure

Users, Clear Logs, Execute Server Control Commands, Access

Console Redirection, Access Virtual Media, Test Alerts, Execute

Diagnostic Commands

– Operator — Privileges: Login to iDRAC, Configure iDRAC,

Configure Users, Execute Server Control Commands, Access Console

Redirection, Access Virtual Media, Test Alerts, Execute Diagnostic

Commands

– User — Privileges: Login to iDRAC

– No Access — No assigned privileges

• Smart Card Authentication — Enables or disables Smart Card

Authentication for iDRAC log in. If enabled, a Smart Card must be installed to access the iDRAC.

– Enabled — Enabling Smart Card login disables all command-line out-of-band interfaces including SSM, Telnet, Serial, remote RACADM, and IPMI over LAN.

– Disabled — On subsequent logins from the graphical user interface

(GUI), the regular login page displays. All command-line out-of-band interfaces—including Secure Shell (SSH), Telnet, Serial, and

RACADM—are set to their default states.

– Enabled with RACADM — Enabling smart card login with

RACADM disables all command-line out-of-band interfaces— including SSM, Telnet, Serial, remote RACADM, and IPMI over

LAN—while still allowing RACADM access.

Click Next to proceed to "Summary."

Summary

Displays the summary of the iDRAC configuration changes.

Click Apply to proceed to "Confirmation."

44

USC and USC - LCE


Confirmation

Confirm the changes you made by viewing the Summary screen. You can apply the changes, or cancel all changes and exit the iDRAC Configuration

Wizard. If you apply the changes, a Please Wait message displays while your changes are saved. When the operation is complete, a final

Confirmation screen displays indicating whether the changes were applied successfully, left unchanged, or failed.

Click Finish to save your settings and return to the main wizards screen.

RAID Configuration

If your system has one or more supported PERC RAID controller(s) with

PERC 6.1 firmware or greater or SAS RAID controller(s), you have the option of using the RAID Configuration wizard to configure a virtual disk as the boot device.

To launch the RAID Configuration Wizard:



3 Click RAID Configuration to launch the wizard.

The following steps will walk you through the RAID Configuration wizard: a

"View Current Configuration"

b c

"Select RAID Controller"

"Foreign Configuration Found"

j i f d e g h

"Select the Express or Advanced Wizard"

"Select Basic Settings"

"Express Wizard Only - Assign a Hot Spare"

"Express Wizard Only - Review Summary"

"Advanced Wizard Only - Select Physical Disks"

"Advanced Wizard Only - Additional Settings"

"Advanced Wizard Only - Review Summary"

USC and USC - LCE

45


View Current Configuration

The View Current Configuration screen displays the attributes of any virtual disks already configured on the supported RAID controllers attached to the system. You have two options:

• Accept the existing virtual disks without making changes. To select this option, click Back.

NOTE:

If you intend to install the operating system on an existing virtual disk, ensure that the virtual disk size and RAID level are appropriate.

• Delete all existing virtual disks and use the RAID configuration wizard to create a single, new virtual disk to be used as the new boot device.

To select this option, click Next.

NOTE:

RAID 0 does not provide data redundancy. Other RAID levels provide data redundancy and may enable you to reconstruct data in the event of a disk failure.

Select RAID Controller

The Select RAID Controller screen displays all supported RAID controllers attached to the system. Select the RAID controller on which you want to create the virtual disk, and then click Next.

Foreign Configuration Found

The Foreign Configuration Found screen displays only if a foreign configuration resides on the selected RAID controller.

A foreign configuration is a set of physical disks containing a RAID configuration that has been introduced to the system but is not yet managed by the RAID controller to which it is attached. You may have a foreign configuration if physical disks have been moved from a RAID controller on another system to a RAID controller on the current system.

46

USC and USC - LCE


You have two options: Ignore Foreign Configuration and Clear Foreign

Configuration.

• If the foreign configuration contains data that you want to keep, select Ignore Foreign Configuration. If you select this option, the disk space containing the foreign configuration is not available for use in a new virtual disk.

• To delete all data on the physical disks containing the foreign configuration, select Clear Foreign Configuration. This option frees the disk space containing the foreign configuration and makes it available for use in a new virtual disk.

Click Next after making your selection.

Select the Express or Advanced Wizard

• Create a virtual disk using either the Express Wizard or the

Advanced Wizard.

• The Express Wizard enables you to select the RAID level only.

The Express Wizard then selects a virtual disk configuration for the user which implements the selected RAID level and optionally enables you to assign a hot spare. Select Express Wizard to quickly create a virtual disk using recommended settings.

NOTE:

Express Wizard is not available on all controllers.

NOTE:

If the available physical disks are using both Serial Attached

SCSI (SAS) and Serial ATA (SATA) protocols, Dell recommends that you use the Advanced Wizard.

• The Advanced Wizard enables you to specify which protocol is used when creating the disk pool for the virtual disks. A disk pool is a logical grouping of disks attached to a RAID controller on which one or more virtual disks can be created. In addition to the RAID level, the Advanced Wizard allows more flexibility with physical disk selection, span configuration, cache policy, and other virtual disk attributes. Select Advanced Wizard to specify all virtual disk settings.

NOTE:

Dell recommends a good knowledge of RAID and your hardware configuration to use the Advanced Wizard.


USC and USC - LCE

47


48

Select Basic Settings

Select the RAID type for the virtual disk from the RAID Level drop-down menu:

• RAID 0 — Stripes data across the physical disks. RAID 0 does not maintain redundant data. When a physical disk fails in a RAID 0 virtual disk, there is no method for rebuilding the data. RAID 0 offers good read and write performance with 0 data redundancy.

• RAID 1 — Mirrors or duplicates data from one physical disk to another.

If a physical disk fails, data can be rebuilt using the data from the other side of the mirror. RAID 1 offers good read performance and average write performance with good data redundancy.

• RAID 5 — Stripes data across the physical disks, and uses parity information to maintain redundant data. If a physical disk fails, the data can be rebuilt using the parity information. RAID 5 offers good read performance and slower write performance with good data redundancy.

• RAID 6 — Stripes data across the physical disks, and uses two sets of parity information for additional data redundancy. If one or two physical disks fail, the data can be rebuilt using the parity information. RAID 6 offers better data redundancy and read performance but slower write performance with very good data redundancy.

• RAID 10 — Combines mirrored physical disks with data striping. If a physical disk fails, data can be rebuilt using the mirrored data. RAID 10 offers good read and write performance with good data redundancy.

• RAID 50 — A dual-level array that uses multiple RAID 5 sets in a single array. A single physical disk failure can occur in each of the RAID 5 without any loss of data on the entire array. Although the RAID 50 has increased write performance, when a physical disk fails and reconstruction takes place, performance decreases, data/program access is slower, and transfer speeds on the array are affected.

• RAID 60 — Combines the straight block level striping of RAID 0 with the distributed double parity of RAID 6. Your system must have at least eight physical disk to use RAID 60. Because RAID 60 is based on RAID 6, two physical disk from each of the RAID 6 sets could fail without loss of data. Failures while a single physical disk is rebuilding in one RAID 6 set do not lead to data loss. RAID 60 has improved fault tolerance because more than half the number of total physical disk must fail for data loss to occur.

USC and USC - LCE


NOTE:

The virtual disk size is automatically calculated and displayed in the Size field.

You cannot change the virtual disk size.

If you are using the Express Wizard, proceed to "Express Wizard Only -

Assign a Hot Spare."

If you are using the Advanced Wizard, click Next and proceed to "Advanced

Wizard Only - Select Physical Disks."

Express Wizard Only - Assign a Hot Spare

To assign a hot spare to the virtual disk, select the Assign a Hot Spare Disk check box; otherwise, leave the check box clear.

NOTE:

A hot spare is an unused backup physical disk that can be used to rebuild data from a redundant virtual disk. A hot spare can be used only with a redundant

RAID level. Hot spares also have requirements for physical disk size. The hot spare must be as big as or bigger than the smallest physical disk included in the virtual disk. If the RAID level and physical disk availability do not meet these requirements, a hot spare will not be assigned.

Click Next to continue with "Express Wizard Only - Review Summary."

Express Wizard Only - Review Summary

Review the virtual disk attributes you selected before creating a virtual disk.

CAUTION:

Clicking the Finish button deletes all existing virtual disks except for any foreign configurations that you specified should be kept. All data residing on the deleted virtual disks will be lost.

Click Finish to create a virtual disk with the displayed attributes.

OR

To return to a previous screen to review or change selections, click Back.

To exit the Wizard without making changes, click Cancel.

NOTE:

For more control over the virtual disk attributes, click Cancel and use the

Advanced Wizard to create the virtual disk.

Advanced Wizard Only - Select Physical Disks

Use the Select Physical Disks screen to select the physical disks to be used for the virtual disk. The number of physical disks required for the virtual disk varies depending on the RAID level. The minimum and maximum numbers of physical disks required for the RAID level are displayed on the screen.

USC and USC - LCE

49


• Select the protocol for the disk pool from the Protocol drop-down menu:

Serial Attached SCSI (SAS) or Serial ATA (SATA). SAS drives are used for high performance, and SATA drives provide a more cost-effective solution.

NOTE:

A disk pool is a logical grouping of physical disks on which one or more virtual disks can be created. The protocol is the type of technology used to implement RAID.

• Select the media type for the disk pool from the Media Type drop-down menu: Hard Disk Drives (HDD) or Solid State Disks (SSD). HDDs use traditional rotational magnetic media for data storage, and SSDs implement flash memory for data storage.

• Select the span length from the Select Span Length drop-down menu.

The span length value refers to the number of physical disks included in each span.

NOTE:

Span length applies only to RAID 10, RAID 50, and RAID 60. The Select

Span Length drop-down menu is active only if the user has selected RAID-10,

RAID-50, or RAID 60.

• Select the physical disks using the check boxes at the bottom of the screen.

Your physical disk selection must meet the requirements of the RAID level and span length. To select all of the physical disks, click Select All.

Click Next after making your selections.

Advanced Wizard Only - Additional Settings

Use the Additional Settings screen to specify cache policies and stripe element size. You can also assign a hot spare to the virtual disk.

NOTE:

The virtual disk size is automatically calculated and displayed in the Size field. The user cannot change the virtual disk size.

• Select the stripe element size from the Stripe Element Size drop-down menu. The stripe element size is the amount of disk space a stripe consumes on each physical disk in the stripe.

NOTE:

The Stripe Element Size drop-down menu may contain more options than initially displayed on the screen. Use the up-arrow and down-arrow keys to display all options.

50

USC and USC - LCE


• Select the read policy from the Read Policy drop-down menu.

– Read Ahead — The controller reads sequential sectors of the virtual disk when seeking data. The Read Ahead policy may improve system performance if the data is written to sequential sectors of the virtual disk.

– No Read Ahead — The controller does not use the Read Ahead policy.

The No Read Ahead policy may improve system performance if the data is random and not written to sequential sectors.

– Adaptive Read Ahead — The controller initiates the Read Ahead policy only if the most recent read requests accessed sequential sectors of the disk. If the recent read requests accessed random sectors of the disk, then the controller uses the No Read Ahead policy.

• Select the write policy from the Write Policy drop-down menu.

– Write Through — The controller sends a write-request completion signal only after the data is written to the disk. The Write Through policy provides better data security than the Write Back policy since the system assumes the data is available only after it has been written to the disk.

– Write Back — The controller sends a write-request completion signal as soon as the data is in the controller cache but has not yet been written to disk. The Write Back policy may provide faster write performance, but it also provides less data security since a system failure could prevent the data from being written to disk.

– Force Write Back — The write cache is enabled regardless of whether the controller has an operational battery. If the controller does not have an operational battery, data loss may occur in the event of a power failure.

USC and USC - LCE

51


• To assign a hot spare to the virtual disk, select the Assign a Hot Spare Disk check box. A hot spare is an unused backup physical disk that can be used to rebuild data from a redundant virtual disk.

• Select the physical disk to be used as the hot spare from the Hot Spare

Disk drop-down menu.

NOTE:

A hot spare can be used only with a redundant RAID level. Hot spares also have requirements for physical disk size. The hot spare cannot be smaller than the smallest physical disk included in the virtual disk. If the RAID level and physical disk availability do not meet these requirements, the Assign a

Hot Spare Disk check box is disabled.


Advanced Wizard Only - Review Summary

The Summary screen displays the virtual disk attributes based on your selections.

CAUTION:

Clicking the Finish button deletes all existing virtual disks except for any foreign configurations that you specified should be kept. All data residing on the deleted virtual disks will be lost.

Click Finish to create a virtual disk with the displayed attributes.

OR

To return to a previous screen to review or change selections, click Back. To exit the Wizard without making changes, click Cancel.

Advanced Configuration

Use Advanced Configuration to modify advanced settings.

1 Select Hardware Configuration from the left menu

2 Click Advanced Configuration in the right panel.

3 Select the device you want to configure.

NOTE:

Depending on the configuration setting changes, the following message may be displayed: One or more of the settings requires a reboot to be saved and activated. Do you want to reboot now?. You can select No and continue making additional configuration changes or perform other tasks such as operating system deployment. All changes will be applied during the next system boot.

52

USC and USC - LCE


USC - LCE Hardware Configuration allows you to configure other devices through Human Interface Infrastructure (HII). HII is a UEFI-standard method for viewing and setting a device's configuration. You can utilize a single utility to configure multiple devices that had different pre-boot configuration utilities in the past. HII also provides localization, meaning that utilities that were previously English-only, such as the BIOS <F2> setup, may now have a localized HII equivalent.

As of the current release of USC - LCE, your server's default configuration contains setups for two device types that are supported in the Hardware

Configuration Advanced Configuration: the system BIOS and NIC.

• The BIOS setup is very similar to the current setup utility (press the <F2> key during system startup); however, HII can access only a subset of the utilities available in system startup.

• The NIC setup reflects various NIC attributes, some of which were visible in the controller option read-only memory (ROM). However, many of these attributes were previously only modifiable in Operating System utilities.

Depending on your system configuration, other device types may also appear in Advanced Configuration, if they support the HII configuration standard.

Advanced Configuration wizard allows you to configure the following:

• System BIOS Settings

• Intel Pro/1000 PT Server Adapter

• Intel Pro/1000 PT Dual Port Server Adapter

• Intel Gigabit VT Quad Port Server Adapter

• Intel 10 Gigabit AF DA Dual Port Server Adapter

• Intel 10 Gigabit AT Port Server Adapter

• Intel 10 Gigabit XF SR Port Server Adapter

• Broadcom (Dual Port) 10G KX4

• Broadcom (Quad Port) GBE

• Intel (Quad Port) GBE

• Intel (Dual Port) 10G KX4

• Broadcom (Dual Port) 10G SFP+

• Broadcom (Quad Port) 10/100/1000 BASET

• Intel (Quad Port) 10/100/1000 BASET

USC and USC - LCE

53


• Intel (Dual Port) 10/100/1000 BASET

• Broadcom NetXtreme Gigabit Ethernet

• Broadcom 5709C NetXtreme II GigE

• Broadcom 5709C NetXtreme II GigE

• Broadcom 57710 NetXtreme II 10GigE

NOTE:

Integrated Broadcom NICs are controlled both by the BIOS and by settings stored on the device itself. As a result, the Boot Protocol field in the HII of integrated NICs has no effect; this setting is instead controlled by the BIOS on the

Integrated Devices screen. To set integrated NICs to an iSCSI or PXE boot mode, select System BIOS Settings, then select Integrated Devices. On this screen, you will see a list of each embedded NIC—select the appropriate value: Enabled for no boot capability, Enabled with PXE to use the NIC for PXE boot, or Enabled with iSCSI to use the NIC to boot from an iSCSI target.

Configuring a Local FTP Server

If your organization’s users are on a private network that does not have access to external sites, specifically ftp.dell.com, you can provide platform updates from a locally-configured FTP server. The users in your organization can access updates or drivers for their Dell server from the local FTP server instead of ftp.dell.com.

NOTE:

A local FTP server is not required for users who have access to ftp.dell.com through a proxy server.

NOTE:

Check ftp.dell.com frequently to make sure your local FTP server has the most recent updates.

Requirements for a Local FTP Server

The following requirements apply when configuring a local FTP server.

• The local FTP server must support anonymous user access. That is, the local FTP server cannot require user authentication.

• The local FTP server must use the default port (21).

• You must use USC Settings wizard to configure the network card on your

system before accessing updates from the local FTP server. See "Using

USC Settings Wizard" for more information.

54

USC and USC - LCE


Creating the Local FTP Server Using Dell Server Updates DVD

1 Download the Dell Server Updates ISO to your system from Dell Support site at support.dell.com, and burn it to a DVD.

2 Copy all files in the repository folder of the DVD you just created to the root directory of the local FTP server.

3 Create a folder named catalog in the root directory of the local FTP server and move the files catalog.xml.gz and catalog.xml.gz.sign from the root directory of the FTP server to the catalog folder you just created.

4 Use this local FTP server for Platform Update.

Accessing Updates on a Local FTP Server

The users in your organization need to know the IP address of the local FTP server in order to specify the online repository when using the

OS Deployment wizard.

If your users are accessing the local FTP server through a proxy server, then they need to know the following information for the proxy server:

• The proxy server host name or IP address

• The port number of the proxy server

• The user name required for authentication on the proxy server

• The password required for authentication on the proxy server

• The type of proxy server

Configuring a Local USB Device

If your organization’s users are on a private network that does not have access to external sites like ftp.dell.com, you can provide updates from a locally-configured USB device.

The USB device you use as a repository must be able to hold at least 3 GB of content.

A USB device is not required for users that have access to ftp.dell.com through a proxy server.

For the latest updates, download the most recent Dell Server Updates ISO for your system from the Dell Support website at support.dell.com.

USC and USC - LCE

55


Creating the Local USB Repository Using Dell Server Updates DVD

To create a repository on a local USB device using Dell Server Updates DVD:

1 Download the Dell Server Updates ISO to your system from the Dell

Support site at support.dell.com, and burn it to a DVD.

2 Copy all files in the repository folder of the DVD you just created to the root directory of the USB device.

3 Create a folder named catalog in the root directory of the USB device and move the files catalog.xml.gz and catalog.xml.gz.sign from the root directory of the USB device to the catalog folder you just created.

4 Use this USB device for Platform Update

56

USC and USC - LCE


Remote Service Features

The Dell™ Lifecycle Controller Remote Services are a set of features focused on enabling automated system discovery by the remote consoles and enhancing remote operating system deployment capabilities. These capabilities use the web services based hardware management interface provided by the Lifecycle

Controller firmware. Remote Services are aimed at simplifying operating system deployment and automating the setup and configuration of new

Dell systems remotely.

Web Services for Management

Web Services for Management (WS-MAN) is a Simple Object Access

Protocol (SOAP)-based protocol designed for systems management.

WS-MAN is published by the Distributed Management Task Force (DMTF) and provides a interoperable protocol for devices to share and exchange data across networks. Dell Lifecycle Controller - Remote Services uses WS-MAN to convey DMTF Common Information Model (CIM)-based management information; the CIM information defines the semantics and information types that can be manipulated in a managed system. The Dell-embedded server platform management interfaces are organized into profiles, where each profile defines the specific interfaces for a particular management domain or area of functionality. Additionally, Dell has defined a number of model and profile extensions that provide interfaces for additional capabilities.

The data and methods available through WS-MAN are provided by the

Lifecycle Controller - Remote Services’ instrumentation interface mapped to the following DMTF profiles and Dell extension profiles:


57


58

Standard DMTF

• Base Server — defines CIM classes for representing the host server.

• Base Metrics — defines CIM classes for providing the ability to model and control metrics captured for managed elements.

• Host LAN Network Port — defines CIM classes for representing a network port that provides a LAN interface to a host system, its associated controller, and network interfaces.

• Service Processor — defines CIM classes for modeling service processors.

• USB Redirection — defines CIM classes for describing information about

USB redirections. For keyboard, video, and mouse devices, this profile should be used if the devices are to be managed as USB devices.

• Physical Asset — defines CIM classes for representing the physical aspect of the managed elements.

• SM CLP Admin Domain — defines CIM classes for representing

CLP’s configuration.

• Power State Management — defines CIM classes for power control operations.

• Command Line Protocol Service — defines CIM classes for representing


• IP Interface — defines CIM classes for representing an IP interface of a managed system.

• DHCP Client — defines CIM classes for representing a DHCP client and its associated capabilities and configuration.

• DNS Client — defines CIM classes for representing a DNS client in a managed system.

• Record Log — defines CIM classes for representing different type of logs.

• Software Inventory — defines CIM classes for inventory of installed or available software.

• Role Based Authorization — defines CIM classes for representing roles.

• Software Update — defines CIM classes for inventory of available software updates.

• SMASH Collections — defines CIM classes for representing




• Profile Registration — defines CIM classes for advertising the profile implementations.

• Simple Identity Management — defines CIM classes for representing identities.

• SSH Service — defines CIM classes for extending the management capability of referencing profiles by adding the capability to represent an

SSH service and its associated sessions in a managed system.

• Battery — defines CIM classes for describing and setting the logical properties of the battery. Such properties include the description of the battery’s charge status and the time it takes for the battery charge to be depleted. The profile also describes operations such as recharging the battery.

Dell Extensions

• Dell Active Directory Client Version 2.0.0 — defines CIM and

Dell extension classes for configuring the Active Directory client and the local privileges for Active Directory groups.

• Dell Virtual Media — defines CIM and Dell extension classes for configuring Virtual Media. Extends the USB Redirection Profile.

• Dell Ethernet Port — defines CIM and Dell extension classes for configuring NIC Side-Band interface for the NIC. Extends the

Ethernet Port Profile.

• Dell Power Utilization Management — defines CIM and Dell extension classes for representing the host server’s power budget and for configuring/monitoring the host server’s power budget.

• Dell OS Deployment — defines CIM and Dell extension classes for representing the configuration of operating system deployment features.

It extends the management capability of referencing profiles by adding the capability to support operating system deployment activities by manipulating operating system deployment features provided by the service processor. For more information on Dell OS Deployment

functions, see "Remote Operating System Deployment Interface."

NOTE:

The WS-MAN implementation complies with the DMTF WS-MAN specification version 1.0.0.


59


The Lifecycle Controller - Remote Services WS-MAN implementation uses

SSL on port 443 for transport security, and supports basic and digest authentication. Web services interfaces can be utilized by leveraging client infrastructure such as Windows

®

WinRM and Powershell CLI, open source utilities like WSMANCLI, and application programming environments like

Microsoft

®

.NET

®

.

There are additional implementation guides, white papers, profile specifications, class definition (.mof) files, and code samples available in the Dell Tech Center at www.delltechcenter.com. For more information, also see the following:

• DTMF Web site: www.dmtf.org/standards/profiles/

• WS-MAN release notes or Readme file.

Auto-Discovery

The auto-discovery feature enables automated discovery of unprovisioned systems on the network by management consoles that have integrated the

Dell provisioning server. The management console provides user credentials to the iDRAC to create an admin account with these credentials so that the discovered systems can be managed.

With auto-discovery enabled, the iDRAC6 requests an IP address from

DHCP and either acquires the name of the system where the management console or provisioning server is located and/or subsequently resolves the address through DNS. After acquiring the address of the management console the iDRAC6 securely handshakes to acquire account credentials.

The iDRAC can now be managed through its newly acquired credentials to perform operations, such as remote operating system deployment.

If you explicitly ordered a Dell system with the Auto-Discovery feature

Enabled (factory default setting is Disabled), then the iDRAC will be delivered DHCP enabled and no user accounts are enabled. If the auto-discovery feature is set to Disabled, you can manually enable this feature from the iDRAC6 Configuration Utility when booting your system.

For more information on Enabling and Disabling auto-discovery feature,

see "Enable and Disable Auto-Discovery Feature."

60



Configuring DHCP/DNS

Before adding your Dell system to the network and using the Auto-Discovery feature, ensure that Dynamic Host Configuration Protocol (DHCP) server/Domain Name System (DNS) are configured with added support for auto-discovery. There are several alternatives for enabling the network environment to support management console discovery by newly installed servers. Ensure that one of the following prerequisites is met for the

Auto-Discovery feature to work properly:

• The DHCP server specifies the IP address and port of the management console in vendor specific option (option 43) data in response to the

DHCP REQUEST sent out by default by the iDRAC. Ensure the

LifecycleController vendor class is created. The DHCP server will resolve hostname of the management console to an IP address with a DNS lookup.

• The DNS server specifies a service option _dcimprovsrv._tcp that will resolve to an IP address.

• The DNS server specifies an IP address for a server with the known name

DCIMCredentialServer .

For more information on configuring DHCP and DNS, see Lifecycle

Controller Auto Discovery Network Setup Specification on the Dell Enterprise

Technology Center at www.delltechcenter.com.

Enable and Disable Auto-Discovery Feature

Before enabling the Auto-Discovery feature, do the following:


NOTE:



2 Enable NIC (for modular system only)

3 Enable DHCP.

4 Select Account Access.


61


5 Select Disabled.

6 Navigate to LAN Parameters.

7 Select Domain Name from DHCP.

8 Select On.

9 Select DNS Server from DHCP.

10 Select On.

11 Save and exit iDRAC6 Configuration Utility.

12 Restart the system.

To enable the auto-discovery feature:


NOTE:



2 Navigate to LAN User Configuration.

3 Select Auto-Discovery.

4 Select Enable to enable the Auto-Discovery feature.

To disable the auto-discovery feature, repeat "step 1," "step 2," and "step 3"

and select Disable.

NOTE:

Auto-discovery feature will not run if any admin accounts are enabled.

Auto-Discovery Workflow

1 Plug in your new Dell system to your network

2 Plug-in the power cables to turn on the system.

3 iDRAC starts, acquires the management console/provisioning server address from DHCP/DNS and announces itself to the management console.

4 The management console validates and optionally accepts the secure handshake session from the iDRAC.

62



5 The management console provides creates user credentials with admin privileges and sends the login credentials to iDRAC.

6 iDRAC receives and completes the secure handshake.

Remote Operating System Deployment

The remote operating system deployment capabilities enable deployment of an operating system remotely using WS-Man web services protocols and

CIFS and NFS network file sharing protocols.

Remote Operating System Deployment Main Features

Following are the main capabilities of remote operating system deployment:

• Remote activation of local exposure of embedded drivers as a USB device

• Remote acquisition of embedded drivers per selected operating system.

• Boot to an ISO image located on a network share.

Remote Operating System Deployment Interface

Dell OS Deployment web services interface provides the capability to support operating system deployment activities by manipulating operating system deployment features provided by the iDRAC service processor. Detailed interface specifications and class definition (.mof) files can be found at the

Lifecycle Controller area on the Dell Enterprise Technology Center at www.delltechcenter.com. Using CIM and Dell extension classes using the web services protocols WS-MAN, Dell OS Deployment feature provides the following capabilities:

• Get the embedded driver pack (a package of all supported operating system drivers for all supported operating systems for the platform) version:

Remote management consoles, applications, and scripts request driver pack version and list of supported operating systems from iDRAC through

WS-MAN.

The GetDriverPackInfo() method on the DCIM_OSDeploymentService class returns the embedded driver pack version and the list of operating systems supported by the driver pack.


63


64

• After determining which operating system the drivers are needed for, one the following methods can be invoked via WS-MAN to unpack the appropriate drivers and expose them locally or acquire them remotely.

a The UnpackAndAttach() method on the

DCIM_OSDeploymentService class extracts the drivers for the requested operating system and places them on a internal USB device labeled OEMDRV. The OEMDRV appears as a locally attached USB device to the system. The method takes the operating system name and an expose duration time as input parameters and returns a job identification that can be subsequently checked for the status of the unpack and attach activity.

NOTE:

The drivers unpacked and attached are removed after the time specified in ExposeDuration parameter or if no time is specified in the method invocation then by default the OEMDRV USB device will be removed after 18 hours.

NOTE:

Ensure that ISO images attached during the process are detached before you use system services.

b

The UnpackAndShare() method on the DCIM_OSDeploymentService class extracts the drivers for the requested operating system and copies them to a network share. The method takes the operating system name and network share information as input parameters and returns a job identification that can be subsequently checked for the status of the unpack and share activity. Network share information includes the IP address of the share, the share name, share type, and username, password and workgroup data for secure shares.

• The following methods can be used to boot the system from an ISO image on a network share or to initiate PXE boot mechanisms: a The BootToNetworkISO() method on the

DCIM_OSDeploymentService class will boot the system using an

ISO image that has been made available on a CIFS or NFS network share.

The method takes the ISO image name, network share information, and exposure duration as input parameters and returns a job identification that can be subsequently checked for the status of the unpack and share activity. Network share information includes the IP address of the share, the share name, share type, and username, password and workgroup data for secure shares. For additional security a hash value can be calculated using well known hash algorithms and this value along with the type of the hash used can be provided as input parameters.



NOTE:

The drivers unpacked and attached are removed after the time specified in ExposeDuration parameter. If no time is specified in the method invocation, then by default the OEMDRV USB device will be removed after 18 hours.

NOTE:

Ensure that ISO images attached during the process are detached before you use system services.

b

The BootToPXE() method on the DCIM_OSDeploymentService class initiates a Pre-Boot Execution Environment (PXE) boot of the system. The method requires no input parameters.

• The following methods are used to directly detach the local OEMDRV device or the network ISO image. These can be used before the previously set exposure durations time out: a

The DetachDrivers() method on the DCIM_OSDeploymentService class detaches and removes the OEMDRV device that had been previously attached by an invocation of the UnpackAndAttach() method. b The DetachISOImage() method on the

DCIM_OSDeploymentService class detaches and removes the network share based ISO image that had been previously attached by an invocation of the BootToNetworkISO() method.

• Several methods described in this document return job identifications as output parameters. The jobs provide a means of keeping track of a requested action that cannot be performed immediately and, because of underlying technology constraints, will take longer than standard web service request response timeouts. The returned job identification can subsequently be used in WS-MAN Enumerate or Get requests to retrieve job object instances. Job object instances contain a job status property that can be checked to see what state the job is in and whether it completed successfully or encountered a problem and failed. If a job failure occurs, the job instance also contains an error message property that provides detailed information on the nature of the failure. Other properties contain other error identification information that can be used to localize the error message to the supported languages and get more detailed error descriptions and recommended response action descriptions.

• The GetHostMACInfo() method on the DCIM_OSDeploymentService class returns an array of physical network port MAC addresses representing all the LAN on Motherboard (LOM) ports in the system. The method requires no input parameters.


65


• All the DCIM_OSDeploymentService methods described in this document return error codes indicating whether the method successfully executed, an error occurred, or a job was created. Job creation occurs if the action being performed in the method cannot be completed immediately.

Additionally, if an error occurs, the methods will also return output parameters that include an error message (in English) and other error identifiers that can be used to localize the error to languages supported by the Unified Server Configurator. The other error identifiers can be used to index into and process Dell Message Registry XML files. The Dell Message

Registry files are available in the six supported languages, one file per language. In addition to translated error messages, the Message Registry files contain additional detailed error descriptions and recommended response actions for each error returned by the Lifecycle Controller

Remote Services web service interface. For more information on methodologies for localizing web services error messages, see Localizing

Dell Web Services Error Message white paper at the Lifecycle Controller area on the Dell Enterprise Technology Center at www.delltechcenter.com.

Operating System Deployment Typical Use Case Scenario

This section contains a typical scenario to deploy an operating system remotely. You need to perform the following steps in order to deploy operating systems remotely.

Prerequisites and Dependencies

The following are the prerequisites and dependencies for deploying the operating system remotely:

• Boot disk is available to install operating system or the operating system

ISO image on the network share

• It is recommended that the latest driver pack is installed and available in

USC-LCE

• Provisioning console, application or appropriate scripts that utilize are capable of sending WS-MAN web services requests and method invocations.

66



Workflow

The following is a typical workflow for remote operating system deployment:

• Create the custom pre-operating system/operating system image and share it on the network or create the desired operating system media ISO image.

• Get the list of supported operating system and driver pack version information.

• Stage the operating system drivers by unpacking and attaching drivers for operating system deployment. These drivers will be installed during the operating system deployment process.

• Remotely boot to the custom pre-operating system/operating system image to initiate the operating system deployment process.

• Run Detach commands to detach the ISO media and driver device.

For more information on the Lifecycle Controller Remote Operating Systems

Deployment feature including the Lifecycle Controller 1.2 Web Services

Interface Guideline, white papers, the Dell OS Deployment Profile data model specification, class definition (.mof) files, sample code and scripts, see the Lifecycle Controller area on the Dell Enterprise Technology Center at www.delltechcenter.com.


67


68



Troubleshooting and Frequently

Asked Questions

This section describes the error messages commonly generated by USC and

USC - LCE, and provides suggestions for resolving the errors. It also answers questions that are frequently asked by USC and USC - LCE users.

Error Messages

"Table A-1" describes the error messages commonly generated by USC and

USC - LCE, and provides suggestions for resolving the errors. "Table A-2"

describes the error messages commonly generated by USC, and provides

suggestions for resolving the errors. "Table A-3" describes the error messages

commonly generated by USC - LCE, and provides suggestions for resolving

the errors. "Table A-4" describes the error messages commonly generated by

Lifecycle Controller, and provides suggestions for resolving the errors

Table A-1.

USC and USC - LCE Error Messages and Resolutions

Error Message

Unable to find a boot device on which to install the operating system

Unable to copy driver files

Resolution

USC or USC - LCE does not detect a device on which an operating system can be installed. One of the following situations is probably causing the error:

• The drives are not properly connected.

• There are no recognized storage controllers on the system.

• The on-board SATA controller is disabled in the BIOS.

To resolve this issue, click Exit and Reboot and shut down the system. Then, make sure you have at least one device on which to install an operating system before launching

USC or USC - LCE again.

The drivers required to install the operating system are corrupted. To resolve this issue, perform a platform update

(see "Updating the Platform using the Platform

Update Wizard.")

Troubleshooting and Frequently Asked Questions

69


70

Table A-1.

USC and USC - LCE Error Messages and Resolutions (continued)

Error Message Resolution

The inserted OS media is invalid

The updates you are trying to apply are not

Dell-authorized updates

The operating system media is damaged or corrupted, or the optical device used to read the media is not functioning correctly.

USC or USC - LCE has detected that one or more of the

DUPs used to update your system are not Dell authorized.

If you are using a local USB device for your update repository and this problem persists, create it again using DUPs from the Server Update Utility DVD

(see "Configuring a Local USB Device") or provide an

alternate repository.

Fatal error launching

USC has occurred.

The system will reboot.

Network is not configured

Unable to set new date and time

A fatal error occurred when launching USC or USC - LCE.

The system will automatically reboot and attempt to enter

USC or USC - LCE again. If the problem persists after

rebooting, see "Repairing USC" or "Repairing USC - LCE."

Network settings must be configured for USC or USC -

LCE to work correctly. See "Using USC Settings Wizard"

for information on configuring USC or USC - LCE network settings from the Network Settings page.

USC or USC - LCE was unable to change the system date and time. To resolve this issue:

1 Reboot the system.

2 Re-enter USC or USC - LCE by pressing the <F10> key.

3 Change the date and time settings again.

Invalid Proxy Server

Please enter a valid

Encryption Key of up to 40 Hex digits


IPv4 Address for this iDRAC


Subnet Mask

The proxy server specified to access the FTP server

is invalid. See "Select Download Method" for

more information.

Enter a valid encryption key that contains not more than 40 hex digits. Valid characters are within the ranges of 0–9, a–f, and A–F.

Enter a valid IPv4 protocol address for iDRAC that is between 0.0.0.0 and 255.255.255.255.

Enter a valid Subnet Mask that is between 0.0.0.0 and

255.255.255.255.



Table A-1.

USC and USC - LCE Error Messages and Resolutions (continued)



Default Gateway

Address

Enter a valid default gateway address that is between

0.0.0.0 and 255.255.255.255.

Please enter a valid IPv4

DNS Server 1 Address

Enter a valid IPv4 DNS Server1 address that is between

0.0.0.0 and 255.255.255.255.



Enter a valid IPv4 DNS Server2 address that is between

0.0.0.0 and 255.255.255.255.

Account access change failed. Multiple user accounts required. See help for details.


Username

You must create another user account. Click the Help button in the upper-right corner of the screen for more information.

You must enter a valid user name. To maintain compatibility with other iDRAC configuration tools,

Dell recommends using only digits (0–9), alphanumeric characters (a–z, A–Z), and hyphens (–) in the user name string.


Password


Confirmation password

You must enter a valid password. To maintain compatibility with other iDRAC configuration tools, Dell recommends using only digits (0–9), alphanumeric characters

(a–z, A–Z), and hyphens (–) in the password string.

You must re-enter the new password and the confirmation password. Be certain that both passwords are exactly the same.


71


Table A-2.

USC Error Messages and Resolutions


Unable to find a device capable of reading the OS install media

USC cannot detect a device to read the operating system media. One of the following situations is probably causing the error:

• No optical device is available on the system. Shut down the system and add a SATA optical device or

USB optical device.

• If an optical device is present, it may not be properly connected. Check to ensure the device cables are adequately seated.

• If an optical device is present, it is disabled in the BIOS.

Reboot the system, enter the BIOS setup utility, and enable the SATA ports for the optical device.

The repository you selected as a source for the updates has failed an integrity check

This error may be caused by temporary network problems; try again later to connect to the update repository.

If you are using a local FTP server for your update repository and this problem persists, create the

repository again (see "Configuring a Local FTP Server")

or provide an alternate repository.

72



Table A-3.

USC - LCE Error Messages and Resolutions


Drivers pack not found

OR

Error populating OS list

USC - LCE cannot find the drivers required to install the operating system. To resolve this issue, perform a platform

update (see "Updating the Platform using the Platform

Update Wizard.)"

Unable to find a device capable of reading the

OS install media

USC - LCE cannot detect a device to read the operating system media. One of the following situations is probably causing the error:

• No optical device is available on the system. Shut down the system and add a SATA optical device or

USB optical device.

• If an optical device is present, it may not be properly connected. Check to ensure the device cables are adequately seated.

• If an optical device is present, it is disabled in the BIOS.

Reboot the system, enter the BIOS setup utility, and enable the SATA ports for the optical device.

• iDRAC virtual media is disabled. See the Integrated

Dell Remote Access Controller 6 (iDRAC6) User’s Guide for your system available at support.dell.com/manuals.

The repository you selected as a source for the updates has failed an integrity check

Decompression of the catalog file failed

This error may be caused by temporary network problems; try again later to connect to the update repository. If you are using a local USB device for your update repository and this problem persists, create the repository again (see

"Configuring a Local USB Device") or provide an alternate

repository.

The catalog downloaded to compare currently installed versions with the latest available versions cannot be decompressed. This error may be caused by temporary network problems; try again later to connect to the update repository. If you are using a local USB device for your update repository and this problem persists, create the

repository again (see "Configuring a Local USB Device")

or provide an alternate repository.


73


Table A-3.

USC - LCE Error Messages and Resolutions (continued)

Error Message

File seek of catalog archive failed

FTP download of catalog sign file failed

Unable to resolve host name

DUP corrupted


IPv6 Address for this iDRAC

Please specify the

IPv6 network address prefix length in the range of 1 to 128

Resolution

The catalog downloaded to compare currently installed versions with the latest available versions is corrupt.

This error may be caused by temporary network problems; try again later to connect to the update repository. If you are using a local USB device for your update repository and this problem persists, create the repository again (see

"Configuring a Local USB Device") or provide an alternate

repository.

The catalog downloaded to compare currently installed versions with the latest available versions has failed the digital signature verification check. This error may be caused by temporary network problems; try again later to connect to the update repository. If you are using a local USB device for your update repository and this problem persists, create the

repository again (see "Configuring a Local USB Device") or

provide an alternate repository.

This error is probably caused by one of the following:

• You have specified an invalid name for the platform update

FTP server. See "Select Download Method."

• The Domain Name Server (DNS) specified in the Network

Settings page is invalid. See "Using USC Settings Wizard."

USC - LCE has detected that one or more of the DUPs used to update your system is corrupted. If you are using a local

USB device for your update repository and this problem

persists, create the repository again (see "Configuring a

Local USB Device") or provide an alternate repository.

Enter a valid IPv6 network address for iDRAC.

See "IPv6 Configuration."

Enter the number of significant bits in the IPv6 address prefix for your network. The prefix length should be

between 1 and 128. See "IPv6 Configuration."

74



Table A-3.



Please enter the IPv6

Default Gateway address

Enter the IPv6 default gateway address.




Enter a valid IPv6 DNS Server1 address.




Enter a valid IPv6 DNS Server2 address.


Please enter a valid iDRAC Name of up to 63 characters


Domain Name of up to 64 characters

Enter a valid iDRAC name that is less than or equal to 63 characters.

Enter a valid domain name that is less than or equal to 64 characters.

Please enter a valid Host

Name of up to

62 characters

Enter a valid host name that is less than or equal to 62 characters.

Please enter a value in the range of 1 to 4094

Please enter a value in the range of 0 to 7

Enter a VLAN ID between 1 and 4094. See "Advanced LAN

Configuration."

Enter a VLAN ID priority value between 0 and 7.

See "Advanced LAN Configuration."

iDRAC communication failure. Please power down, unplug the system, wait 5 seconds, apply power and power on

Communication with iDRAC has failed. To resolve this issue:

1 Turn off the system, and then unplug it.

2 Wait 5 seconds.

3 Plug the system back in, and then turn it on.

iDRAC hard failure.

Please power down, unplug the system, wait

5 seconds, apply power and power on

Connection with iDRAC has failed. To resolve this issue:

1 Turn off the system, and then unplug it.

2 Wait 5 seconds.

3 Plug the system back in, and then turn it on.


75


Table A-3.



RAID configuration failed

Generic Failure

USC - LCE failed when creating the RAID configuration.

To resolve this issue:


2 Re-enter USC - LCE by pressing the <F10> key.

3 Try again to create the RAID configuration.

USC - LCE experienced an unidentified error when creating the RAID configuration. To resolve this issue:



3 Try again to create the RAID configuration.

Sufficient physical disks not available on any supported RAID controller. The wizard will exit.

You do not have a sufficient number of disks to support

RAID configuration—you must attach more physical disks and start the RAID Configuration wizard again.

Please select required number of physical disk(s) for current span

No physical disk has been selected for this virtual disk

The number of physical disks you selected for the current

RAID span is incorrect. Review your span selections, and enter the correct number.

The number of physical disks you selected for the virtual disk is insufficient. Review the minimum number of physical disks required for the current RAID level, and select at least that number of physical disks.

No controller is present in the system

No RAID controller is present in your system. To resolve this issue:

1 Add a supported RAID controller that includes two or more physical disks.


3 Restart the RAID Configuration wizard.

No valid RAID level found

The number of physical disks attached to your system is insufficient for the RAID level you selected. Attach more physical disks and try again.

76



Table A-3.



An error occurred. One or more settings may not be saved.

An error occurred. One or more settings may not be restored.

This feature is not supported in this configuration

An error occurred when changing Hardware Advanced

Configuration settings. To resolve this issue:



3 Change the settings again.

An error occurred when restoring Hardware Advanced

Configuration settings. To resolve this issue:



3 Re-open the Advanced Configuration screen.

Your modular system does not support the feature you selected.

Table A-4.

Lifecycle Controller Error Messages and Resolutions

Error Message

General failure

Lifecycle Controller is being used by another process

Resolution

An error has occurred. No other details are available at this time.

1 Run the command again.

2 Reset iDRAC and run the command.

Lifecycle Controller is currently locked by another process.

Ensure that the process is completed before attempting to run another command.

1 Run the command again after sometime.

2 Ensure that USC or DUP is not running.

3 Reset iDRAC and run the command


77


Table A-4.

Lifecycle Controller Error Messages and Resolutions (continued)


Cannot access Driver

Pack partition in

Lifecycle Controller.

Driver Pack partition in Lifecycle Controller is not accessible. The Lifecycle Controller might be corrupted.


Driver Pack not found in

Lifecycle Controller

No Driver Pack in Lifecycle Controller.

1 Update the Driver Pack using USC or DUP and then run the command again.

Cannot allocate memory Unable to dynamically allocate memory to perform the task.


Driver Pack does not have drivers for the selected operating system.

Cannot create

USB device to copy drivers for the selected operating system.

Lifecycle Controller does not have any drivers for the selected operating system. The installation will have to use the native drivers present on the operating system media.

Unable to create USB device to copy drivers for selected operating system. iDRAC may not be operating normally

1 Reset iDRAC and run the command again.

Cannot mount

USB device to copy drivers for the selected operating system.

Unable to expose

USB device containing operating system drivers to host system.

Unable to expose the newly created USB device (with drivers for selected operating system) to the host server.

IDRAC may not be operating normally.


Mount network share failed - incorrect username or password.

Unable to access the newly created USB device to copy drivers for selected operating system. IDRAC may not be operating normally

1 Reset iDRAC and run the command again

Unable to mount the network share using the credentials specified in the command. Either username or password is incorrect.

1 Run the command again with correct username and password.

78



Table A-4.



Mount network share failed - incorrect

IP address or share name.

Exposing ISO image as internal device to the host system failed.

Unable to mount the network share using the credentials specified in the command. Either IP address or share name is incorrect.

1 Run the command again with correct IP address and share name.

Unable to expose the ISO image as internal CD device to the host system. The ISO file is no longer present, network errors are preventing access to the ISO file, or IDRAC may not be operating normally.


Unable to locate the

ISO image on the network share point.

The fork() command for a child process to do the task failed

Unable to get size or label from Driver Pack for selected operating system.

Unable to find the ISO file specified in the network share.

Ensure that you have specified the correct path to the

ISO file in the command and all other user credentials are correct.

1 Run the command again with correct path to ISO file.

Failed to execute fork() system call to perform the task in a child process. IDRAC may not be operating normally.


Unable to get the size or label for selected operating system from the Driver Pack present in Lifecycle

Controller. The driver pack may be corrupt.

1 Update the driver pack using USC or DUP and run the command again

Unable to boot to ISO image

Booting to ISO has failed. Either BIOS was unable to boot to the ISO image or provider did not get a response in 5 minutes from BIOS on successful boot to ISO image.

1 Ensure there is no POST error that resulted in user interaction (Press F1 to continue or F2 to run setup).


Unable to detach

ISO image from the host

Unable to detach ISO image from the host. Either the image may have already detached or IDRAC may not be operating normally.

1 Reset iDRAC to automatically detach the ISO image.


79


80

Table A-4.



Unable to continue with DetachISOImage - another command is in the process of exposing

ISO Image and booting to it.

Cannot continue with DetachISOImage because another command is in the process of exposing ISO image and booting to it.

1 See ConcreteJob status to ensure that the current running process is complete and then run DetachISOImage.

Unable to continue with DetachDrivers -

UnPackAndAttach is in progress

1 Wait until UnpackAndAttach finishes and then run

DetachDrivers.

Unable to detach

USB device containing operating system drivers.

Detaching the USB device (that contains drivers for the operating system installation) from the host has failed.

The device may have been detached already or

IDRAC may not be operating normally.

1 Reset iDRAC to detach this device automatically.

Unable to continue with

BootToPXE - another command is running.

Unable to continue with BootToPXE command because another process is using Lifecycle Controller.

1 See ConcreteJob status to ensure that the current running process is complete and then run BootToPXE.

Copying drivers for selected operating system failed.

Hash verification on the ISO image failed.

Driver Pack config file not found in Lifecycle

Controller. Driver Pack might be corrupt.

Copying drivers for selected operating system failed.

The Driver Pack may be corrupt.


Hash verification on the ISO image has failed. The hash value specified in the command is either not correct or the

ISO image has been changed.

1 Verify that the hash value specified in the command is correct.

2 Ensure that the ISO has not been changed - replace the

ISO image on the share and run the command again.

Driver Pack config file not found in Lifecycle Controller.

Driver Pack may be corrupt.




Table A-4.



Invalid value for

ExposeDuration - must be 60-65535 seconds

Copying operating system drivers to network share failed

Unable to detach ISO image from the system

Installed BIOS version does not support this method.

The value specified for ExposeDuration is out of range.

It must be 60-65535 seconds

1 Run the command again with ExposeDuration value 60 to 65535 seconds.

Copying drivers for selected operating system to network share failed. The share may be read-only or the driver pack present in Lifecycle Controller may be corrupt.

1 Ensure that the network share has write permission.


Cannot continue with DetachISOImage because system does not have attached ISO image.

1 Do not run DetachISOImage command.

The system has an older version of BIOS that does not support this method. Install the latest version of BIOS to use this method.

1 Update the BIOS to version 1.2 or later and then run the command again.

Unable to continue with

BootToPXE - ISO image is attached to the system.

Unable to continue with BootToPXE command because system has an ISO image attached. Detach the ISO image before continuing with BootToPXE.

1 Run DetachISOImage command and then run

BootToPXE.

Lifecycle Controller is disabled

Boot to ISO Image has been cancelled by user using CTLR+E option on the server

Lifecycle Controller is disabled on the system, so none of the remote enablement OSD commands will work.

Ensure Lifecycle Controller is enabled before running any command

1 Reboot the system and enable System Services using

CTLR+E option in the POST

User has cancelled system services by using CTLR+E option during POST. This has effectively cancelled the

WSMAN request to boot to ISO

1 Do not cancel system services using CTLR+E during

POST when system is rebooting to the ISO


81


Frequently Asked Questions

When USC - LCE downloads updates, where are the files stored?

The files are stored in non-volatile memory, located on the main system board. This memory is not removable and is not accessible through the operating system.

Is a virtual media device or vFlash card required to store data for updates?

No. The files are stored in memory on the main system board.

What is virtual media?

Virtual media is remote media—like CDs, DVDs, and USB keys—that a server identifies as local media.

What should I do if an update fails?

If an update fails, USC-LCE will reboot and then attempt all the remaining pending updates selected. After the final reboot, the system returns to the

USC-LCE Home page. Launch Platform Updates again and then re-select the update that had failed and click Apply.

What is vFlash or virtual flash? vFlash is a formatted SD (Secure Digital) card that plugs into iDRAC6

Enterprise. vFlash can be formatted and enabled via iDRAC to make it accessible as a USB key for data storage. Virtual flash is a partition on vFlash to which you can remotely write an ISO. See the Integrated Dell Remote

Access Controller 6 (iDRAC6) User’s Guide available at support.dell.com/manuals for more information.

Can I add my own drivers to use for operating system installation?

No. You cannot add your own drivers for operating system installation.

See "Updating the Platform using the Platform Update Wizard" for

more information on updating the drivers that are used for operating system installation.

82



Can I update the drivers used by an installed operating system through USC or USC - LCE?

No. USC or USC - LCE only provides drivers that are required for operating system installation. To update the drivers used by an installed operating system, see your operating system’s help documentation.

Can I add my own drivers and firmware for updating USC or USC - LCE to a local

USB device?

No. Only drivers and firmware downloaded from the Server Update Utility

DVD’s are supported. See "Configuring a Local USB Device" for more

information.

Can I delete USC or USC - LCE?

No.

Can I use virtual media for the operating system media source during installation?

Yes. See the Integrated Dell Remote Access Controller 6 (iDRAC6) User’s Guide for your system’s iDRAC device for more information (available at support.dell.com/manuals).

Can I use a virtual USB for my update repository?

Yes. See the Integrated Dell Remote Access Controller 6 (iDRAC6) User’s Guide for your system’s iDRAC device for more information (available at support.dell.com/manuals).

What is UEFI? With which version does USC or USC - LCE comply?

UEFI (Unified Extensible Firmware Interface) is a specification that details an interface for transitioning control from the pre-boot environment to the operating system. USC or USC - LCE complies with UEFI version 2.1. See www.uefi.org for more information.


83


Within Hardware Configuration, what is the difference between the Configuration

Wizards and Advanced Configuration?

USC - LCE offers two ways to configure hardware: Configuration Wizards and

Advanced Configuration.

Configuration Wizards guide you through a sequence of steps to configure your system devices. The Configuration Wizards include iDRAC, RAID,

System Date/Time, and Physical Security. See "Hardware Configuration"

for more information.

Advanced Configuration allows you to configure Human Interface

Infrastructure (HII) enabled devices (for example, NICs and BIOS).

See "Advanced Configuration" for more information.

Does USC or USC - LCE support configuration of all RAID levels and all RAID cards for xx1x systems?

USC or USC - LCE supports RAID levels 0, 1, 5, 6, 10, 50, and 60 on

PERC 6 cards running PERC 6.1 firmware. RAID 0 and 1 are supported on the SAS 6/iR.

Does USC - LCE support rollback of BIOS and firmware?

Yes. See "Rolling Back to Previous BIOS and Firmware Versions" for more

information.

Which devices support system updates?

USC - LCE currently supports updates to the BIOS, iDRAC firmware, power supply firmware, and certain RAID and NIC controller firmware.

See "Updating the Platform using the Platform Update Wizard" for

more information.

Which devices are supported in Advanced Configuration within Hardware

Configuration?

Advanced Configuration is available for the BIOS and NIC. Depending on your system configuration, other devices may also appear in Advanced

Configuration if they support the HII configuration standard. See "Hardware

Configuration" for more information.

84



What should I do if my system crashes while using USC or USC - LCE?

If your system crashes while using USC or USC - LCE, a black screen with red text will appear. To resolve this problem, first try rebooting your system and re-entering USC or USC - LCE. If that does not resolve the problem,

perform the steps in "Repairing USC" of "Repairing USC - LCE." If that does

not resolve the problem, contact Dell for technical assistance.

How do I find out the current installed version details of the USC-LCE product?

Click About on the left navigation pane.

What should I do if I have an issue with mouse synchronization when I access

USC LCE over the iDRAC KVM?

Ensure that the Single Cursor option under Tools in the iDRAC KVM menu is selected on the iDRAC KVM client. See the Integrated Dell Remote Access

Controller 6 (iDRAC6) User’s Guide available on the Dell Support site at support.dell.com/manuals for more information.


85


86



Glossary

BitLocker

A full disk encryption feature included with the Microsoft

2008 operating system that encrypts entire volumes.

®

Windows Server

®

Controller

A chip that controls the transfer of data between the microprocessor and memory or between the microprocessor and a peripheral device, such as a disk drive or the keyboard. RAID controllers perform RAID functions, such as striping and mirroring to provide data protection.

disk pool

A logical grouping of disks attached to a RAID controller on which one or more virtual disks can be created.

DUP

Dell Update Package. A self-contained executable in a standard package format.

Each Update Package is designed to update a single software component on your system.

HII

Human Interface Infrastructure. HII is a UEFI-standard method for viewing and setting a device's configuration. hot spare

A physical disk that is available to aid in recovery of a logical drive.

logical drive

See virtual disk.

physical disk

A non-volatile, randomly addressable device for storing data. Physical disks are rewritable and commonly referred to as disk drives.

RACADM

A command-line utility that provides a scriptable interface that allows you to locally or remotely configure a remote access controller (RAC).

Glossary

87


88

RAID

Redundant Array of Independent Disks

SAS

Serial Attached SCSI

SATA

Serial ATA

SBUU

Systems Build and Update Utility. An integrated tool for your Dell systems that enables you to update BIOS and firmware in the pre-operating system environment, apply these settings on the current system or on multiple systems, and install the operating system.

SCSI

Small Computer Systems Interface

SD card

Secure Digital card. A solid-state memory card.

span

A span is a RAID technique used to combine storage space from groups of physical disks into a RAID-10 virtual disk.

SSD

Solid state disk

SSM

System Service Manager. The SSM performs USC or USC - LCE functions, such as downloading updates, as a background task. stripe

See striping.

stripe element

A stripe element is the portion of a stripe that resides on a single physical disk.

See also striping.

stripe element size

The amount of disk space consumed by a stripe element.

Glossary

LC1_2.book Page 89 Wednesday, November 18, 2009 9:42 AM stripe size

The total disk space consumed by a stripe, not including a parity disk. striping

Disk striping writes data across all physical disks in a virtual disk. Each stripe consists of consecutive virtual disk data addresses that are mapped in fixed-size units to each physical disk in the virtual disk using a sequential pattern.

For example, if the virtual disk includes five physical disks, the stripe writes data to physical disks one through five without repeating any of the physical disks.

The amount of space consumed by a stripe is the same on each physical disk.

The portion of a stripe that resides on a physical disk is a stripe element. Striping by itself does not provide data redundancy. Striping in combination with parity does provide data redundancy.

TPM

Trusted Platform Module. TPM is a secure cryptoprocessor that stores cryptographic keys used to protect data.

UEFI

Unified Extensible Firmware Interface. UEFI is a specification that details an interface for transitioning control from the pre-boot environment to the operating system. See www.uefi.org for more information.

virtual disk

A virtual disk refers to storage created by a RAID controller from one or more physical disks. Although a virtual disk may be created from several physical disks, it is seen by the operating system as a single disk. Depending on the RAID level used, the virtual disk may retain redundant data in case of a disk failure.

Glossary

89


90

Glossary


Index

A

auto-discovery, 60

disable, 62

enable, 61

B

BIOS

configuring with HII, 53

rolling back, 32

BitLocker, 33

C

CLI, 7

D

deployment interfaces, 60

DHCP/DNS

configure, 61

DUP, 12, 21, 26, 87

E

error messages, 69

F

FAQs, 82

firmware

adding custom, 83

interrupting install, 32 rolling back, 32

FTP

configuring a local server for updates, 54-55

H hardware

advanced configuration, 52

configuration wizards, 34 configuring, 34

hardware diagnostics

updating the utility, 26

HII, 53

I iDRAC

configuring, 35

Enterprise, 36, 42, 82

Index

91


L

LAN

advanced configuration, 37

Linux

driver location, 21, 24

read-only file system, 23

updating drivers, 24

O operating system

adding custom drivers, 82

deploying, 17, 19

launching the wizard, 18

using virtual media for installation, 83

P physical security

configuring, 34

platform

updating from local FTP

server, 54-55

R

RAID

configuration wizard, 20

configuring, 45

remote operating system deployment, 63 deployment interface, 63 main features, 63

prerequisites and dependencies, 66 use case, 66

workflow, 66

remote services, 7, 57

S

SUSE

driver location, 21

system crashes, 85

system date/time, 35

system services

canceling request to enter, 16

disabled, 12 not available, 12

systems services

update required, 12

T

TPM, 33

troubleshooting, 69

92

Index


U

UEFI, 53, 83

USC

deleting, 83

disabling, 15

repair package, 26

storing update files, 82

updating, 15

wizards, 13

V

vFlash, 82

virtual disk

configuring as a boot device, 20

virtual media

using for operating system installation, 83

W

web services for management, 57

Windows

drivers, 22

installing to C drive, 24

wizards

Diagnostics, 13

Hardware Configuration, 13

OS Deployment, 13

Platform Update, 13

Settings, 13

WS-MAN, 57

Index

93


94

Index

Dell Lifecycle Controller 1.2 User guide

Dell™ Lifecycle Controller

Version 1.2

User Guide

Notes and Cautions

Contents

Overview

Remote Services

Unified Server Configurator (USC)

Unified Server Configurator and

Unified Server Configurator - Lifecycle

Controller Enabled

Common Features

Launching the Product

Using the Wizards

Accessing Help

Viewing Readme

Updating USC - LCE

Disabling the Product

Canceling a Request to Enter System Services

Using USC Settings Wizard

Deploying the Operating System Using the OS Deployment Wizard

Hardware Diagnostics

Repairing USC

Repairing USC - LCE

How to Upgrade to an iDRAC6 Express Card

Installing the iDRAC6 Express Card

Transferring an iDRAC6 Express Card from an Existing System to a

Different System

Uninstalling the iDRAC6 Express Card

Unified Server Configurator - Lifecycle Controller

Enabled Unique Features

Updating the Platform using the Platform Update Wizard

Rolling Back to Previous BIOS and Firmware Versions

Updating Devices That Affect Trusted Platform Module Settings

Hardware Configuration

Configuring a Local FTP Server

Requirements for a Local FTP Server

Creating the Local FTP Server Using Dell Server Updates DVD

Accessing Updates on a Local FTP Server

Configuring a Local USB Device

Creating the Local USB Repository Using Dell Server Updates DVD

Remote Service Features

Web Services for Management

Auto-Discovery

Configuring DHCP/DNS

Enable and Disable Auto-Discovery Feature

Auto-Discovery Workflow

Remote Operating System Deployment

Remote Operating System Deployment Main Features

Remote Operating System Deployment Interface

Operating System Deployment Typical Use Case Scenario

Troubleshooting and Frequently

Asked Questions

Error Messages

Frequently Asked Questions

Glossary

Index

Related manuals

Dell

Lifecycle Controller 1.5

Dell

DX6000G

Dell

Lifecycle Controller 1.6.5

Dell

Lifecycle Controller 1.5

Dell

Lifecycle Controller 1.4

Dell

IDRAC6

Dell

iDRAC6 for Blade Servers Version 2.1

Dell

Lifecycle Controller 1.5.5

Dell

iDRAC6 for Blade Servers Version 2.2

Dell

iDRAC6 for Monolithic Servers Version 1.2

Dell