Dell iDRAC7 with Lifecycle Controller Version 2.13.13.12 Manual

Integrated Dell Remote

Access Controller 8

(iDRAC8) and iDRAC7

with Lifecycle

Controller for Dell

PowerEdge Servers

Version 2.13.13.12

Release Notes

Release Notes

Integrated Dell Remote Access Controller (iDRAC)

iDRAC is a systems management hardware and software solution that provides remote management capabilities,
crashed system recovery, and power control funct i ons for Dell PowerEdge sy s t ems.

Lifecycle Controller (LC-GUI)

An out-of-band mechanism for configuring the platform, applying firmware updates, saving or restoring a system
backup, or deploying an operating system, either by using a GUI or a remote scripting language. Lifecycle Controller
GUI provides advance d embedded systems management and is delivered as part of Integrated Dell Remote Access
Controller 8 (iDRAC8). The GUI enables remote systems management in a one-to-one method and is accessible by
pressing F10 during system boot.

Lifecycle Controller Remote Services (LC-RS)

LC-RS provides advanced embedded systems management and is delivered as part of iDRAC8 and iDRAC7. LC-RS
enables remote systems management in a one-to-many method. Remote Services uses WS-Management (WS-MAN)
protocol based Web services interface to remotely provision and manage the servers.

Important Notes for This Release

Support for using a common iDRAC firmware across Dell 12th and 13th generation PowerEdge servers. You can apply
the same (2.13.13.12) version on a 13th generation Pow erEdge server with iDRAC8 and a 12th generation PowerEdge
server with iDRAC7.

• Enables direct upgrade to version 2.13.13.12 from 2.xx.xx.xx and 1.xx.xx.

Note: You cannot downgra de to version 1.xx.xx on a 13th genera tion PowerEdge server . On a 12th generation
PowerEdge system you can downgrade to 1.xx.xx version. However, you must ensure that you downgrade
iDRAC before downgrading Lifecycle Controller.

• Supports features such as SNMPv3 traps, combined functionality of Tech Support Report with iDRAC Service

Module, security enhancements, and code stability are supported on the Dell 12th generation PowerEdge
servers. However, it does not support features that are inherent to the 13th generation of PowerEdge servers
and their system board, such as Easy Restore, optional Quick Sync bezel and so on. For more information on
the features supported, see Licensable Features In iDRAC7 and iDRAC8 in the iDRAC UG or see the related
white paper available at the Dell TechCenter.

---------------------------------------------------------------------------------------------------------------

Version

iDRAC 2.13.13.12 (applies to both iDRAC7 and iDRAC8)
Lifecycle Controller 2.13.13.12

Release Date

June 2015

Previous Version

NA

Importance

RECOMMENDED: Dell recommends applying this update during your next scheduled update cycle. The update
contains feature enhancements or changes that will help keep your system software current and compatible with other
system modules (firmware, BIOS, drivers, and software).

Platform(s) Affected

iDRAC8 and LC is supported on the following 13th generation PowerEdge system:

•

PowerEdge R930

What is Supported?

License Requirements

• Software licensing has replaced hardware licensing. For more information, see the Integrated Dell Remote

Access Controller 8 (iDRAC8) and iDRAC 7 v2.10.10.10 User 's Guide, available at

dell.com/support/manuals.

• Many features in Lifecycle Controller are licensed. You must install the appropriate license to use these

features. For more information, see the Introduction section in the Dell Lifecycle Controller GUI v2.10.10.10

User’s Guide, available at dell.com/support/manuals.

Supported Managed Server Operating Systems for iDRAC7 and iDRAC8

The following operating systems are supported by iDRAC7 and iDRAC8:

•

Windows Server 2008 R2 SP1 Foundation Edition
Windows Server 2008 R2 SP1 Enterprise Edition

•

Windows Server 2008 R2 SP1 Standard Edition

•

Windows Server 2008 R2 SP1 Datacenter Edition

•

Windows Server 2008 R2 SP1 Embedded Systems

•

Windows Server 2008 SP2 x32

•

Windows Server 2008 SP2 x64

•

Windows Server 2012 Foundation Edition

•

Windows Server 2012 Essentials Edition

•

Windows Server 2012 Standard Edition

•

•

Windows Server 2012 Datacenter Edition
Windows Server 2012 R2 Foundation Edition

•

Windows Server 2012 R2 Essentials Edition

•

Windows Server 2012 R2 Standard Edition

•

Windows Server 2012 R2 Datacenter Edition

•

Windows Server 2012 for Embedded Systems (Base and R2 SP1)

•

WinPE 3.0 32 bit

•

WinPE 4.0 32 bit

•

WinPE 4.0 64 bit

•

WinPE 5.0 64 bit

•

Red Hat Enterprise Linux 7.0

•

Red Hat Enterprise Linux 6.6

•

•

SUSE Linux Enterprise Server 12
SUSE Linux Enterprise Server 11 SP3

•

VMware vSphere 5.1 U3

•

VMware vSphere 5.5 U2

•

VMware vSphere 6.0

•

Citrix XenServer 6.2

•

Citrix XenServer 6.5

•

Supported Web Browsers for iDRAC7 and iDRAC8

•

Microsoft Internet Explorer 9
Microsoft Internet Explorer 10

•

•

Microsoft Internet Explorer 11
Safari version 7.1

•

Safari version 8.0

•

Mozilla Firefox version 32

•

Mozilla Firefox version 33

•

Google Chrome version 37

•

Google Chrome version 38

•

What’s New

•

Support for the following PowerEdge system:

o

PowerEdge R930

iDRAC – Fixes

•

VNC password is not retained in iDRAC after an iDRAC reboot.

•

Assertion of PSx-PG-Fail in the SEL will be automatically de-asserted upon recovery of PSU-Good or
removal of related PSU.

iDRAC - Important Notes

•

Lifecycle Controller features such as Auto Discovery and vFlash are now licensed. Install the correct licenses
for Lifecycle Controller Remote Services to work properly.

•

Only if there is one or more network interface cards (NDC or LOM) present on the managed system,

Network Devices

For the virtual console and virtual media to function properly, iDRAC8 web URL must be added to the Local

•

Intranet site list and the security level for the Local Intranet zone must be set to Medium-Low. In addition, if
Virtual Console and Virtual Media are configured to use Java plug-in, disable the
in Internet Explorer. If this is not possible, then in iDRAC8, configure Virtual Console to use the ActiveX
plug-in.

If the instant messenger is launched in the Virtual Console viewer with ActiveX native plug-in and another

•

application is started (example Notepad, WordPad, and so on) without minimizing the Virtual Console, the
instant messenger box also pops-up on other applications. This does not happen with Java plug-in.

•

When a system is in POST, it is not possible to attach a vFlash partition as the first boot device.
Virtual Console Viewer from iDRAC8 Web interface terminates when the managed system is restarted.

•

A pop-up message is not displayed to confirm if test emails are successfully sent or not.

•

•

For iDRAC8 Enterprise, when the Virtual Console is disabled and Virtual Media is disabled and/or detached,
the console port (default: 5900) remains open. For iDRAC8 Express (no Virtual Console or Virtual Media)
the console port is open.

If auto-negotiation is enabled while setting iDRAC8 network, 1 Gbps is not supported and you cannot

•

manually select it.

•

A USB device mounted through Virtual Media in floppy emulation mode for a Linux operating system shows
as a removable volume.

During system power operations, if the video mode changes, the message "Out of range" may appear for a

•

short while on the Virtual Console.

•

When using the Virtual Console in native console mode with
Internet Explorer versions 8 and 9, if an F1/F2 prompt is encountered, pressing F1 displays the Virtual
Console online help pop-up in addition to continuing with the system boot.

appears under

Overview

->

Hardware

section in the iDRAC web interface.

Enhanced Security Mode

Pass all keystrokes to server

disabled in

•

When any of the storage enclosure components are removed, the corresponding details are not displayed.
Only the name and status attributes are displayed.

When certain RAID operations are requested using WS-MAN on non-RAID cards such as, the Dell SAS

•

6Gbs HBA or the Internal Tape Adapter, the operation succeeds, however the job fails with the error message
"Unable to locate device in current configuration".

If the iDRAC8 network is configured to use a shared LOM and the spanning tree is enabled on the LOM port,

•

WS-MAN and remote service commands may time-out in the following scenarios:

- At system reboot

- When CSIOR is running

- While entering SSM
The connectivity lost is variable. In typical cases, it is approximately:

- 40 seconds at system reboot and varies per NIC or link speed

- 20 seconds when CSIOR is running

- 40-60 seconds while entering SSM

•

The reason is that when spanning tree is enabled, the switch does not allow the link to re-establish the
connection after a reset until it completes checking for network loops. Server reboots reset the NIC and
disconnects the link.

Note

: This does not occur while using dedicated NIC because server reboots do not affect the dedicated NIC.

When logging in to iDRAC8 web interface using Internet Explorer 9 and IPv6 address, the co nne c t ion may

•

not succeed. To resolve this, make sure that in

Connections

On PowerEdge systems with cabled power supply units installed (that is, PSUs which do not provide PMBus

•

support), power values may still be displayed in the iDRAC8 web and LCD interfaces. Due to lack of PMBus
support in the PSUs, the power values displayed on the GUI pages, including the

Front Panel

Due to the independent nature of the alert processes (e-mail, SMTP, remote syslog), when changing the

•

licenses that affect alert features (example, email alerts for Express or remote syslog for Enterprise) there is
no guarantee of the timing of the features being activated or deactivated when the license changes.

In the iDRAC web interface, when the

•

minutes for the inventory data to be collected. After the data collection is complete, refresh the page to display
the inventory data.

Make sure to synchronize the iDRAC time with the management station’s time to avoid certificate related

•

issues. If the time is not synchronized, issues such as server certificate expiration may be seen. If this occurs,
re-synchronize iDRAC time with the management station’s time and reboot iDRAC.

On a system running Linux, after launching the Virtual Console, if you click a menu item and it remains open,

•

the Ctrl + Alt + L keystroke sent from iDRAC to the host system does not lock the host system. The behavior
is same as using a local keyboard.

The default time zone value is US Central Time. To make sure Single Sign-On (SSO) and Directory Service

•

TFA (smart card) continue to work properly, the iDRAC time zone must match the time zone where iDRAC
is located, assuming Active Directory server's time zone is already configured to match the Active Directory's
location.
For example, if Active Directory server is located at US Eastern time zone and iDRAC is located at US
Pacific time zone, Active Directory server has to be configured as US Eastern time zone (this is Active
Directory server configuration and is normally configured), and iDRAC must be configured as US Pacific
time zone. For more information to configure the time zone, see the Integrated Dell Remote Access Controller
8 (iDRAC8) and iDRAC7 v2.10.10.10 User's Guide.

If the management station is using MAC operating system, it takes more time to launch the Virtual Console

•

due to the following DNS search issue:

domains

The help page for the Export and Import of Server Profile feature does not provide the correct share name.

•

See the Web Services Interface Guide available at Dell TechCenter for the correct share name.

•

Remote Sys Log settings take effect only if you do the following:

- Enable remote syslog feature

- Specify the server address and port number

- Enable

•

When creating a Virtual Media image from a folder, the output image file size is at least 512 MB.

->

LAN Settings

page, may not be correct.

.

Remote SysLog

, the

Use automatic configuration script

System Inventory

option on the

Internet Explorer

page is accessed for the first time, it takes up to two

http://www.eigenspace.org/2011/07/fixing-osx-lion-dns-search-

Alerts

page

->

Tools

->

option is cleared.

Internet Options

Overview

->

->

Hardware

->

•

To launch Virtual Console using Java plug-in, only JavaWebStart versions 1.5, 1.6, and 1.7 from Sun (Oracle)
is supported. Any other versions or any other installations are not supported.

On a server running RHEL operating system, performing the following steps can create an eth*.bak interface

•

(where * is the interface number). This is visible in the Network Manger interface. This interface can be
safely ignored.

1.

After the operating system (RHEL) is running, enable OS to iDRAC Pass-through channel through
the iDRAC web interface.

2.

Disable OS to iDRAC Pass-through.

3.

Reboot or power cycle the server, and then re-enable OS to iDRAC Pass-through.

•

Any change in VNC server settings disconnects the active VNC session.

•

USB NIC is supported on RHEL 6.5 32-bit and RHEL 6.5 64-bit operating systems. On any Linux operating
system, for https://idrac.local to work, the avahi, nss-mdns, and depen de nt packages must be installed.

CIFS supports both IPv4 and IPv6 addresses but NFS supports only IPv4 address.

•

During POST, if the system displays cable detect message: "CBL0001: Backplane 0 power cable

•

disconnected", you must check all the backplane cables as this message is not limited to Backplane 0 only.

•

Do not reboot the host while RAID rebuild is in-progress. If the host is reset, IDSDM is also reset.

•

On certain iDRAC versions, creating vFlash partition and downloading DUP images may take a little longer
than usual due to updated open source packages.

iDRAC - Know n Issue s

Issue 1:

Description

The 'ipmitool fru' command displays 'PERC2 NA' even if a second PERC controller is installed.

Resolution
View the PCIe slot8 FRU data on the System Inventory page of the iDRAC GUI.

Issue 2:

Description

Intermittent issues with attaching partition on vFlash SD card using the iDRAC GUI.
Resolution

1. Remove the vFlash SD card and install it again.

2. Attach the partition.

You can also try resolving the issue using the following method:

1. Reset iDRAC on the iDRAC Diagnostic web page.

2. Run racadm racreset.

3. Try logging on to the iDRAC web page after a while and attach the partition.

Issue 3:

Description

The NIC link status and link speed properties for Intel Ethernet Controller X540 are displayed incorrectly on the

Network Devices page in the iDRAC GUI.
Resolution

You can use any of the following methods to view the correct information:

• Use the OS Device Manager or Network Adapter Manager to view the link data.

• Use Dell Open Manage products to view the link data.

iDRAC - Limitations

•

If floppy emulation is enabled when a bootable USB key is mounted as a Virtual Media from the Virtual
Console and if you try to delete any file from the mounted USB key (floppy), the blue screen appears
immediately.

Web server session time-out is not exact. It is either 10% more or 15 seconds more, whichever is greater.

•

WinRM and RACADM commands may become unresponsive during BIOS update or when setting BIOS,

•

NIC, or RAID attributes through Lifecycle Controller.

•

If invalid credentials are used for the maximum login attempts, the IP is blocked for the duration of the IP
Blocking Penalty Time and a message is not displayed.

If Internet Explorer (IE) 64-bit browser is used to log in to iDRAC8 Web interface and when viewing the

•

power usage graph, the X and Y axis labels appear too small to read. This is a known limitation for IE 64-bit
only. The labels appear correctly in IE 32-bit browser.

On Linux management stations, if Firefox is launched from the root user, a USB key is mapped in Virtual

•

Media successfully. If Firefox is launched from any user other than the root user, a USB key is not shown for
mapping because the user must have root privileges to access all the low-level drives.

•

Alert notification for battery events does not work.

•

Operating system information on the System Summary page does not display after rebooting iDRAC8 until
the operating system is rebooted.

iDRAC8 users with user names containing a semi-colon (;) cannot log in to iDRAC8 through SSH.

•

•

In the iDRAC8 web interface, the power consumption sensor reading may have a rounding error of up to 13
Watts depending on the actual power reading. This is an IPMI limitation. The power cap, power graphs,
cumulative power, and peak power are not affected by this inaccuracy. However, the power values shown in
the power graphs are average values over a period of time and should not be used to calculate instantaneous
power.

Virtual Console uses self-signed certificates. Due to this, when launching Virtual Console from some

•

management stations with Windows operating systems, a certificate warning appears.

•

Virtual Console in dual monitor mode is not supported and hence the behavior is undefined, especially using
Java plug-in. The primary console is used as the target console.

The email address specified in iDRAC8 web interface ->

•

Generate Certificate Signing Request (CSR)

->
On a Linux management station with Matrox drivers, from the Virtual Console Viewer if you access the

•

iDRAC Chat window, the mouse appears flickering inside the chat window.

•

Work notes can display up to 255 characters. If any of the characters are special characters or non-alpha
numeric characters, then the total number of characters displayed is less than 255 to accommodate overriding
special characters.

Performing a graceful shutdown from the iDRAC8 web interface or updating the BIOS or the firmware using

•

the iDRAC8 update method:

o

For SLES 11 SP2:
A prompt appears for the Super user password in the operating system console. Provide the root
password and proceed with the graceful shutdown or firmware/BIOS update.

o

For Windows OS in screen lock state:
Graceful shutdown does not happen because, Windows operating system has a policy setting to
disable shutdown while in locked state. Make sure that this policy is enabled.
If it is not enabled, then it proceeds with ungraceful shutdown. This is equivalent to losing power.
After the server resets, multiple options are displayed to start Windows. Select

Normally

ungraceful shutdown.

In the iDRAC web interface >

•

nothing found, the
VNC disconnects after host reboot on Wyse PocketCloud.

•

Encrypted VNC does not work through Real VNC client.

•

•

VNC does not work through mobile when encryption is enabled.

•

OS to iDRAC communication through the USB NIC interface is not supported on RHEV – H (hypervisor)
system.

and then check the System Event Log file. You can see that an event is logged in for the

Log Results

Overview

page is not validated.

Overview

section does not display any user-friendly information and it is blank instead.

>

Server

>

Lifecycle Log

->

iDRAC Settings

page, when the filter criteria results in

->

Network

Start Windows

->

SSL

•

USB NIC IP address must always be assigned Link Local address. Assigning IP address other than Link
Local IP address or conflicting IP address of other network interface may cause network related issues.

iDRAC Virtual NIC driver is not loaded when Windows 2008 SP2 (64-bit) installation has completed.

•

•

When Virtual Console is in Lifecycle Controller, if
boots to Lifecycle Controller instead of BIOS Setup.

•

If the http or https service port is set to 1 or 65535, and if you launch the iDRAC8 web interface using the
Google Chrome browser, it does not launch iDRAC8. This is because of a limitation in the Google Chrome
browser. The resolution is to use Internet Explorer or Mozilla Firefox browsers.

You cannot start iDRAC after updating the NIC firmware because the update process resets NDC. To resolve

•

this issue, reset iDRAC after updating the NIC firmware.
When iDRAC NIC is in shared mode and the host system is power cycled, the network connection is lost for a

•

few seconds. During this time, if you perform any action in the active VNC client, the VNC session may
close. You must wait for time out (value configured for the VNC Server settings in the Services page in
iDRAC Web interface) and then re-establish the VNC connection.

The ports 6000-6063 are reserved for x-server display. Hence, any service configured with these ports on

•

iDRAC is unsuccessful. Use ports other than 6000 to 6063 to configure the service.

•

For servers with higher configuration (more enclosures and RAID components), remote racadm may not
provide the output for hwinventory or swinventory commands. In such cases, try using firmware racadm
(SSH).

LC GUI - Fixes

Next Boot

is set to

BIOS Setup

, rebooting the system

None.

LC GUI - Important Notes

•

This release note is the latest and overrides the release note available on the LC GUI.

•

The drivers exposed by Lif ecycle Controller are present in a read-only hard disk drive, labeled OEMDRV,
which are active for 18 hours. During this period:

o You cannot update any DUP.
o Lifecycle Controller cannot invoke CSIOR.

However, if an AC power cycle (cold boot) is performed, the OEMDRV drive is automatically deleted.

•

To log the update events in the Lifecycle Log, make sure that the installed versions of Lifecycle Controller and
iDRAC are from the same release.

If Lifecycle Controller and iDRAC are not from the same r elease, the Lifec ycle Log displays bla nk messages

•

and messages with a “~” character.

•

CPLD firmware update has no impact on Trusted Platform Module enablement.

•

On the basis of virtual storage device type attached through iDRAC, that is, USB drive or CD/.ISO file,
Lifecycle Controller will display Virtual Floppy or Virtual CD respectively.

If Test Network Connection fails for a valid address, try configuring the network settings again. If the issue

•

persists, restart the system and retry the operation.
When you reset or update iDRAC, you must reboot Lifecycle Controller if it is launched already. If you fail

•

to reboot, Lifecycle Controller displ a ys a n un expected behavior.

•

On PowerEdge FC630, PowerEdge FC830, and PowerEdge FC430 systems, part replacement is not supported
if a single PERC (FD332) is replaced with a dual PERC (FD332) or vice versa.

After performing firmware update or rollback operations using Lifecycle Controller the host is rebooted by

•

default, reboot the host server again to display the updated firmware versions in the Hardware Configuration
wizard.

While installing the operating system on the Dell 12th generation PowerEdge servers using Lifecycle

•

Controller, ensure that the virtual media is connected to the server before booting in to the BIOS.

LC GUI - Known Issue s

Issue 1:

Description

If FlexAddress is enabled on Chassis Management Controllers, iDRAC and Lifecycle Controller do not display the
same MAC addresses.

Resolution
To view the chassis-assigned MAC address, use the iDRAC web interface or the CMC web interface. Go to General->

Network Settings.
Versions/Systems Affected

All LC–supported Dell PowerEdge servers.

Issue 2:

Description

While deploying Windo ws Server 2008 R2 SP1 from OS Deployment of Lifecycle Controller, installat i on stops with
the following error:

There is no disk in the drive. Please insert a disk into drive \Device\Harddisk0\DR0.
This issue may occur due to any of the following reasons:

• Virtual Media is in the attached state and a media is not mapped.

• Virtual Media is in the auto-attached state and a media is not mapped.

• Virtual Media being presented by the AVCT SIP and Virtual Media from iDRAC8 in the detached state.

• Due to failure to load drivers for RAID controllers on the system.

Note: It does not occur with Virtual Media in the detached state. It also does not occur without the SIP and with Virtual
Media in the detached from iDRAC8.

Resolution
Retry the operation.

Versions/Systems Affected

All LC–supported Dell PowerEdge servers.

Issue 3:

Description
Some of the supported components are not displayed on the Firmware Update-> View Current Versions page.
Resolution
Restart the server and open View Current Versions page.
Versions/Systems Affected

All LC–supported Dell PowerEdge servers.

Issue 4:

Description

If a Mellanox card is present in the system, then under Network Settings, the port number must be displayed as Port 1
and Port 2, because it is a dual port. But, the port number is displayed as Port 1 for both the ports or the port numbers
are not displayed.

Resolution
To distinguish between the port numbers, see the MAC address or the Device Settings.
You can access Device Settings in the following methods:

• During POST, press <F2>, and then click System Setup.

• On the Lifecycle Controller Home page, click System Setup, and then click Advanced Hardware

Configuration.

Versions/Systems Affected

All LC–supported Dell PowerEdge servers

Issue 5:

Description

After you successfully update the firmware of a CPLD on a modular server, and then perform a firmware update
operation of a component that requires a system restart (such as BIOS), the server is automatically and repeatedly
restarted.

Resolution
Perform a Power Cycle operation on the server.

Versions/Systems Affected

All LC–supported Dell PowerEdge servers.

Issue 6:

Description

Lifecycle Controller may go into an infinite loop when a network operation is tried with an incorrect NFS share name.
Resolution
Restart Lifecycle Controller and retry the operation with the correct NFS share name details.

Versions/Systems Affected

All LC–supported Dell PowerEdge servers.

Issue 7:

Description

In the Firmware Rollback – Select Components page, the iDRAC version is displayed as 2.02.01.00 instead of

2.02.01.01.
Resolution
Issue is with the version number that is displayed and this does not affect the functionality. You can continue with the

rollback operation.

Versions/Systems Affected

All LC–supported Dell PowerEdge servers.

Issue 8:

Description

Intel I350 Gigabit embedded network firmware cannot be updat ed using the LC GUI or any other interfaces using LC­RS.

Resolution
Update the firmware using the Windows (.exe) or Linux (.bin) executable formats.

Versions/Systems Affected

All LC–supported Dell PowerEdge servers.

Issue 9:

Description

On the Dell 12th generation PowerEdge servers, while deploying the operating system by selecting the UEFI boot
mode, an error message is displayed when you click Finish. This error occurs if you try to connect the optical drive or
virtual media after you launch Lifecycle Controller.

Resolution
Reboot the server and ensure that you connect the optical drive or virtual media before launching Lifecycle Controller.

Versions/Systems Affected

All LC–supported Dell PowerEdge servers.

LC GUI - Limitations

•

Lifecycle Controller supports the following characters for user name and password:

o Alphabets (a-z, A-Z)
o

Digits (0-9)

o

Special characters (-, _, .)

While updating iDRAC firmware using a tool other than Lifecycle Controller, Lifec ycle Controller must not

•

be open, or running, because it results in an unknown behavior. Use Lifecycle Controller after the firmware is
successfully updated.

If the iDRAC firmware update is i nterrupted for any reason, wait for 30 minute s before attempting another

•

firmware update.
Only Windows operating system can be deployed on systems with a software RAID controller.

•

Firmware update is supported only for LAN On Motherboards, Network Daughter Cards, and network adapters

•

from Broadcom, QLogic, and Intel, a nd some of the QLogic and Emule x fiber channel cards. For the list of
supported fiber channel cards, see Lifecycle Controller Graphical User Int erface Version 2.0 0.00.00 For 13t h
Generation Dell PowerEdge Servers User’s Guide.

•

After the CPLD firmware is updated on modular servers, on the View Current Versions page, under Firmware
update, the firmware update date is displayed as 2000-01-01, regardless of the actual update date. The updated
date and time is displayed on the basis of time zone that is configured on the server.

•

Rollback is not supported for CPLD.

•

On some modular systems, after a firmware update, the Lifecycle Log di splays the date in the time stamp as
1999-12-31, instead of the date on which Firmware Update was performed.

Some properties related to devices installed in PowerEdge VRTX system are not displayed while viewing the

•

current hardware inventory.
Lifecycle Controller can import and view an iDRAC license, but it cannot export or delete the iDRAC license.

•

•

The iSCSI offload feature can be enabled only on two of the available four ports. If the iSCSI offload attribute
is enabled on a card, and is re placed by another car d whose iSCSI offloa d mode is also enable d on the other
two ports, an error is thrown. The firmware will not allow the attribute to be set, because it is already set on the
other two ports.

•

The unattended OS (operating syste m) instal lation feature is not supp orted for the Mi crosoft Win dows Server
2012 R2.

Windows OS supports both the ma nual installation and unattende d installation features. However, Lifecycle

•

Controller supports the unattended installation feature for Windows and RHEL-7 operating systems only.
VLAN configuration is not supported on all vendor FC cards and the following Emulex cards:

•

o

Emulex OneConnect OCe14102-U1-D 2-port PCIe 10GbE CNA

o Emulex OneConnect OCm14104-U1-D 4-port 10GbE rNDC CNA
o

Emulex OneConnect OCm14102-U5-D 2-port 10GbE Mezz CNA

o

Emulex OneConnect OCm14102-U4-D 2-port 10GbE bNDC CNA

o

Emulex OneConnect OCe14102-N1-D 2-port PCIe 10GbE NIC

o

Emulex OneConnect OCm14104-N1-D 4-port 10GbE rNDC NIC

o

Emulex OneConnect OCm14102-N5-D 2-port 10GbE Mezz NIC

o Emulex OneConnect OCm14102-N6-D 2-port 10GbE bNDC NIC

Lifecycle Controller displays two drive names for some CDs or DVDs such as the one containing operating

•

systems.
Network operations such as Update, Export, or Import may take more time than expected. The delay may occur

•

because the source or destination share is not reachable or does not exist, or due to other network issues.

•

Lifecycle Controller displays a warning message if the operating system selected for installation and the
operating system on the me dia used are different. Howeve r, while installing Windows operatin g systems, the
warning message appears onl y when the bit count (x86 or x64) of th e operating system does not match. For
example, when Windows Server 2008 x64 is selected f or installa tion and Wi ndows Serv er 2003 x64 m edia is
inserted,

•

Lifecycle Controller proceeds with the installation without displaying a warning message.
Lifecycle Controller does not support operating system deployment on Dell Precision workstation R7910.

•

•

When NPAR is enabled, the port numbers displayed on the

Settings->Network Settings

(

System Setup->Advanced Hardware Configuration

(
The word encrypted is incorrectly translated as scripted in the Step 3 OS deployment Spanish help page.

•

•

When you update the firmware on a Broadcom NetXtreme and QLogic BCM57xx and BCM57xxx
(previously known as Broadcom NetXtreme II) adapters the following issue occurs:

o After installing the QLogic-specific firmware update package on the BCM57xx or BCM57xxx

adapter family, the rollback version is not available if the previously installed firmware was provided
by a legacy shared firmware update package. However, if the legacy shared firmware version is
available as a rollback version for the Broadcom NetXtreme adapter, then the same version will be
available for the QLogic BCM57xx and BCM57xxx adapters.

This issue occurs because separate firmware update packages are provided for the Broadcom NetXtreme
adapters and QLogic BCM57xx and BCM57xxx adapters due to the acquisition of the Broadcom NetXtreme II
cards by QLogic. Prior to the acquisition, a common shared firmware update package was provided.

•

The following Intel network cards do not displ ay all port s on the
update and also do not support rollback:

Intel(R) Ethernet Converged Network Adapter X710 - Quad Port

o
o

Intel(R) Ethernet Converged Network Adapter X710 - Dual Port

o

Intel(R) Ethernet 10G 4P X710/I350 rNDC

o

Intel(R) Ethernet 10G 4P X710 SFP+ rNDC

o

Intel(R) Ethernet 10G 4P X710-k bND C

o

Intel(R) Ethernet 10G 2P X710-k bND C

•

Part replacement feature is not supported for PCIe SSD devices.

) do not match with the port numbers dis played on the

Lifecycle Controller Network Settings

->

Device Settings

Comparison

).

page during a firmware

Device Settings

page

page

LC-RS - Fixes

None.

LC-RS - Important Notes

None.

LC-RS - Known Issues

None.

LC-RS - Limitations

•

The drivers exposed by Lifecycle Controller are present in a read-only device labeled OEMDRV, and the
device is active for 18 hours. In a Microsoft(r) Windows(r) and Linux environment, the drivers are
automatically installed and no further action is required. In Red Hat Enterprise Linux version 4.8 only, the
drivers are not automatically installed and you have to install the drivers manually after the OS installation
has been completed.

If the boot mode is set to UEFI in BIOS (F2 setup) and if you launch System Services (FlO) and Deploy OS,

•

the installation may fail or you may not be able to boot to the OS after the installation. Always make sure that
the boot mode is set to BIOS in F2 setup before launching Lifecycle Controller and deploying the OS.

•

You may see a no optical device found error if you have a non-usable DVD/CD in the optical drive. This error
does not mean that there are no optical devices on the system. If you remove the non-usable media, then this
error is resolved.

To maintain compatibility with other iDRAC configuration tools, it is recommended that only digits (0-9),

•

alphanumeric (a-z, A-Z) and hyphen (-) characters be used when entering a “Name” or “Password” string.
When entering a “Domain Name”, such as ‘x123.com’, a period (.) character is also permissible.

When attempting a Platform Update through an FTP server, specifying a valid proxy server but selecting an

•

invalid proxy type causes Lifecycle Controller to halt for a long period (possibly over 30 minutes) before it
returns to normal operation.

If you see this error message “Unable to find a boot device on which to install the operating system. Verify

•

boot disk availability.” and if you have a USB key plugged in to the system after booting to Lifecycle
Controller, remove the USB key before deploying the operating system.

If you are updating iDRAC firmware using a tool other than Lifecycle Controller, do not run Lifecycle

•

Controller during the firmware update because doing this results in an unknown behavior. After the firmware
is successfully updated, you can safely use Lifecycle Controller.

When configuring the FTP server for your repository in the platform update, you may get a message that

•

indicates that a network connection exists with your FTP server; however, it may mean that the validation
process needs some extra time depending on your network setting. Click OK on the message box, and try one
more time to connect to the FTP server.

•

Account access can be disabled only if there is more than one user enabled on the iDRAC. To enable users,

Users

access the iDRAC Web-based GUI. Navigate to the
enable users as needed. Note that at least one more user needs to be enabled to disable the account access in
the Lifecycle Controller. In the iDRAC Configuration Wizard, the DNS Domain Name may contain a
maximum of 64 ASCII characters.

•

When attempting a Platform Rollback, there may be a two minute delay before Rollback tasks are displayed
on the screen.

In the iDRAC Configuration Wizard, there is no a selection for auto-attached on the Virtual Media

•

Configuration page.
During an UEFI based SLES 10 and SLES 11 installation, make sure that no additional USB or block storage

•

devices are connected to the system. If there are one or more USB or block storage devices plugged into the
system, the auto loading of drivers from the embedded storage fails. This fails because the current
implementation of SLES installer reads only from one USB or block storage device.

•

If an invalid SD card is attached to the system, the values shown for “Health” and “Available Space” options
are not applicable.

An “Invalid Update Package” error message is displayed, when

•

− the folder containing the Update Package is not accessible.

− the Update Package is not present on the USB mass storage device.

− name of the Update Package is incorrect.

•

Only Windows operating system can be deployed on systems with software RAID controller.

•

Using Platform Update, you cannot update components such as Complex Programmable Logic Device,
Backplane, and Physical Disk. However, the View Current Versions table displays these components.

The SATA drives and their firmware version are not displayed on the View Current Versions page of

•

Platform Update. To view the SATA drives and their firmware information, use OpenManage Server
Administrator or OpenManage Storage Services.

The PCIe SSD drives and their firmware versions are not displayed on the View Current Versions page of

•

Platform Update.
Collect System Inventory On Reboot (CSIOR) must to be run before enum is successful.

•

BCM57xx /BCM57xxx updates Limitations - When you update the firmware on Broadcom NetXterme I and

•

QLogic BCM57xx/BCM57xxx (previously known as Broadcom NetXtreme II) Ethernet adapters, you may
notice failure or incorrect rollback version displayed based on the firmware update used. This behavior occurs
because separate firmware update packages are provided for the Broadcom NetXtreme adapters and QLogic
BCM57xx and BCM57xxx adapters due to the acquisition of the Broadcom NetXtreme II c a rds by QL ogic.
Prior to the acquisition, a common shared firmware update package was provided.

Limitations on updating firmware on Broadcom and QLogic adapters using iDRAC interfaces such as WS­MAN, RACADM, iDRAC GUI, and Lifecycle Controller UI:

o

Rollback of Broadcom NetXtreme I to 7.10.X and QLogic BCM57xx and BCM57xxx Ethernet
adapters to 7.12.X from the iDRAC GUI may result in failure of rollback to 7.12.X.

section under the

Network/Security

tab and

o Updating Broadcom NetXtreme I to 7.10.X and QLogic BCM57xx and BCM57xxx Ethernet

adapters to 7.12.7 results in updating both Broadcom NetXtreme I and QLogic BCM57xx and
BCM57xxx to 7.10.X.

o

Downgrading to version 7.10.X on a system with Broadcom NetXtreme I 7.10.X and QLogic
BCM57xx and BCM57xxx Ethernet adapters 7.12.X results in displaying the QLogic BCM57xx
and BCM57xxx Ethernet adapters rollback version as NULL even though it is updated to 7.10.X.

o

Repository updates to Broadcom NetXtreme I and QLogic BCM57xx and BCM57xxx Ethernet
adapters works only with iDRAC version 2.10.10.10 or later.

o

QLogic BCM57xx and BCM57xxx adapters may be displayed as Broadcom or QLogic depending
on the interface used such RACADM or WS-MAN.

Part replacement feature is not supported for PCIe SSD devices.

•

iDRAC - Installation

Installation Instructions

•

From the Windows host operating system (managed node), run the Dell Update Package for Windows and
follow the instructions on the update wizard.

•

From the Linux host operating system (managed node), run the Dell Update Package for Linux from the shell
prompt. Follow the instructions displayed on the console.

From the management station, remotely update the firmware using the iDRAC8 web interface:

•

1. Extract the firmware image self-extracting file to the management station.

2. Open the iDRAC8 web interface using a supported web browser.

3. Log in as administrator.

4. Go to Overview -> iDRAC Settings -> Upda t e and Rollback -> Update. The Firmware Update page is

displayed.

5. Click Browse, select the .d7 firmware image file that you extracted (step 1), or the Dell Update Package (DUP)

for Windows, and click Upload.

6. Wait for the upload to complete. After the upload is completed, the Update Details section displays the firmware

file uploaded to iDRAC and the status.

7. Select the firmware file and click Install or Install and Reboot. If it is a DUP, Install dynamically changes to

Install and Reboot and at the same time the Install Next Reboot is activated. When you click Install and
Reboot or Install Next Reboot, the message “Updating Job Queue” is displayed.

8. Click OK. The Job Queue page is displayed, where you can view and manage the firmware update. After the

update is completed, iDRAC8 restarts automatically. For more information, see the iDRAC User's Guide
available at dell.com/esmmanuals.

Upgrade

Not applicable.

Uninstallation

Not applicable.

Lifecycle Controller Remote Services - Client Tools

Use the WinRM and OpenWSMAN CLI client tools to send WS-MAN commands to L ifecycle Controller.

WinRM

WinRM is a Windows native WS-MAN client. It is recommended to use WinRM 2.0 on Windows Management
Stations. WinRM 2.0 is installed by default as a part of Windows 7 and Windows Server 2008 R2. It can also be
installed as a part of the Windows Management Framework Core package on the following systems:

•

Windows Server 2008 SP1
Windows Server 2008 SP2

•

Windows Server 2003 SP2

•

Windows Vista SP1

•

Windows Vista SP2

•

Windows XP SP3

•

For more information on how to install WinRM 2.0 as a part of the Windows Management Framework Core package,
see article 968929 in the Microsoft Knowledge Base at:

http://go.microsoft.com/fwlink/?LinkId=186253
Recommended WinRM Client Configuration:

•

MaxBatchItems = 50
MaxTimeoutms = 60000

•

MaxEnvelopeSizekb = 150

•

NetworkDelayms = 60000

•

Sample WinRM Command (Enumeration Operation):

winrm e cimv2/DCIM_SystemView?__cimnamespace=root/dcim -u:[idrac user]

-p:[idrac password] -r:https://[idrac ip address]/wsman -encoding:utf-8

-a:basic -SkipCNcheck -SkipCAcheck -format:Pretty

Note: Lifecycle Controller uses a self-signed certificate for HTTPS (SSL) communication. Self-signed certificates are
not accepted by the WinRM client and WinRM comm a nds do not work without these options:

SkipCAcheck

-SkipCNcheck and --

OpenWSMAN CLI

OpenWSMAN CLI is an open source Linux WS-MAN client. OpenWSMAN CLI so ur ce code and installation details
are available at:

http://sourceforge.net/projects/openwsman/files/wsmancli
Sample OpenWSMAN CLI Command (Enumeration Operation):

wsman enumerate http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/DCIM_SystemView -h
(idrac ip adddress) -P 443 -u (idrac user) -p (idrac password) -v -j utf-8 -y basic -R -o

-m 256 -N root/dcim -c cert_name.cer -V

Note: Lifecycle Controller uses a self-signed certificate for HTTPS (SSL) communication. Self-signed certificates are
not accepted by the OpenWSMAN CLI client and WS-MAN commands do not work without t he s e options: -c, -v, and
–V. See the OpenWSMAN CLI readme for details on these opt ions.

Contacting Dell

Note: If you do not have an active Internet connection, you can find contact information on your purchase invoice,

packing slip, bill, or Dell product catalog.
Dell provides several online and telephone-based support and service options. Availability varies by country and

product, and some services may not be available in your area. To contact Dell for sales, technical support, or customer
service issues:

1. Visit www.dell.com/support.

2. Select your support category.

3. Verify your country or region in the Choose a Country/Region drop-down menu at the top of page.

4. Select the appropriate service or support link based on your need.

Accessing Documents From Dell Support Site

To access the documents from Dell Support site:

1. Go to dell.com/support/manuals.

2. In the Tell us about your Dell system section, under No, select Choose from a list of all Dell products and click

Continue.

3. In the Select your product type section, click Software and Security.

4. In the Choose your Dell Software section, click the required link from the following:

− Client System Management

− Enterprise System Management

− Remote Enterprise System Management

− Serviceability Tools

5. To view the document, click the required product version.

You can also directly access the documents using the following links:

•

For Remote Enterprise System Management documents —
For Enterprise System Management docum ents —

•

For Serviceability Tools documents —

•

For Client System Management documents —

•

•

For OpenManage Connections Enterprise systems management documents —

dell.com/OMConnectionsEnterpriseSystemsManagement

For OpenManage Connections Client systems management documents —

•

dell.com/serviceabilitytools

dell.com/openmanagemanuals

dell.com/OMConnectionsClient

dell.com/esmmanuals

dell.com/OMConnectionsClient

--------------------------------------------------------------------------

Information in this document is subject to change without notice.
© 2015 Dell Inc. All rights reserved.
Reproduction of these materials in any manner whatsoever without the written permission of Dell Inc. is strictly forbidden. Trademarks used in this

text: Dell(TM), the DELL logo, PowerEdge(TM), PowerVault(TM), Compellent(TM) and OpenManage(TM) are trademarks of Dell Inc. Intel(R) is a
registered trademark of Intel Corporation in the U.S. and other countries. Microsoft(R), Windows(R), Windows Server(R), Internet Explorer(R),
Hyper-V(R), Active Directory(R), ActiveX(R) and Windows Vista(R) are trademarks or registered trademarks of Microsoft Corporation in the
United States and/or other countries. Red Hat Enterprise Linux(R) and Enterprise Linux(R) are registered trademarks of Red Hat, Inc. in the United
States and/or other countries. The term Linux(R) is a registered trademark of Linus Torvalds, the original author of the Linux kernel. SUSE(TM) is a
trademark of Novell Inc. in the United States and other countries. XenServer(R) is a registered trademark of Citrix Systems, Inc. in the United States
and/or other countries. Mozilla(R) and Firefox(R) are registered trademarks of Mozilla Foundation. VMware(R) and ESX(TM) are registered
trademarks or trademarks of VMware, Inc. in the United States and/or other jurisdictions. Java(TM) is a registered trademark of Oracle and/or its
affiliates. Google(R) and Chrome(TM) is a trademark of Google Inc. Mac(R), Macintosh(R), and Mac OS(R), Safari(R), and OS X(R) are trademarks
of Apple Inc., registered in the U.S. and other countries. Matrox(R) is a registered trademark of Matrox. Broadcom(TM) is a trademark of Broadcom
Corporation and/or its affiliates in the United States, certain other countries, and/or the EU. QLogic(R) is a registered trademark of QLogic
Corporation. AMULET(TM) is a trademark of AMULET Development Corp. Brocade(R) is a registered trademark of Brocade Communications
Systems, Inc., in the United States and/or in other countries.

Other trademarks and trade names may be used in this publication 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.