Dell iDRAC7 with Lifecycle Controller Version 2.15.10.10 Manual
Integrated Dell Remote
Access Controller 8
(iDRAC8) and iDRAC7
with Lifecycle
Controller for Dell
PowerEdge Servers
Version 2.15.10.10
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.15.10.10) version on a 13th generation PowerEdge se r ver with iDRAC8 and a 12th generation PowerEdge
server with iDRAC7.
• Enables direct upgrade to version 2.15.10.10 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.15.10.10 (applies to both iDRAC7 and iDRAC8)
Lifecycle Controller 2.10.10.10
Release Date
June 2015
Previous Version
2.10.10.10 (iDRAC8 with Lifecycle Controller)
1.66.65 (iDRAC7)
1.4.8 (Lifecycle Controller fo r 12th generation PowerEdge systems)
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 systems:
•
PowerEdge R430
PowerEdge R530
•
PowerEdge R630
•
PowerEdge R730
•
PowerEdge R730XD
•
PowerEdge M630
•
•
PowerEdge FC630
PowerEdge FC430
•
PowerEdge FD332
•
PowerEdge T430
•
PowerEdge T630
•
PowerEdge C4130
•
Precision Rack 7910
•
PowerEdge FM120x4
•
iDRAC7 and LC is supported on the fol lowing 12th generation PowerEdge systems:
•
PowerEdge R220
PowerEdge R320
•
PowerEdge R420
•
PowerEdge R520
•
PowerEdge R620
•
PowerEdge R720
•
PowerEdge R720XD
•
PowerEdge R820
•
PowerEdge R920
•
PowerEdge M420
•
•
PowerEdge M520
PowerEdge M620
•
PowerEdge M820
•
PowerEdge S120
•
PowerEdge S420
•
PowerEdge S620
•
PowerEdge T320
•
PowerEdge T420
•
PowerEdge T620
•
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 Graphical User
Interface v2.10.10.10 For Dell 12
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
•
th
and 13th Generation Dell PowerEdge Servers User’s Guide, available at
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 systems:
o
PowerEdge FC430
o PowerEdge FD332
•
Support for using single iDRAC firmware across Dell 12th and 13th generation PowerEdge servers.
Support to switch the controller mode from RAID to HBA and back on PERC 9.1 and later controllers.
•
Enables SSL encryption between client and server using 256 bit or higher.
•
•
Added racadm proxy support for PowerEdge FX2 chassis. Allows an iDRAC administrator utilizing Chassis
Management at Server (CMAS) to issue a racadm command to CMC using iDRAC.
Added event proxy support for PowerEdge FX2 chassis. Allows an iDRAC managing a PowerEdge FX2
•
CMC utilizing CMAS to display CMC events.
Added support for iDRAC Shared LOM on PowerEdge FX2 chassis.
•
Upgraded OpenSSL v1.0.1j; response to CVE-2014-3566 for the "POODLE" issue.
•
Upgraded OpenSSH v6.6; response to CVE-2010-5107, CVE-2014-2532.
•
Added support for QLogic BCM57xx and BCM57xxx NIC cards.
•
Added support for Intel Ethernet Network Adapters X710.
•
Added support for the following Emulex network 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
iDRAC – Fixes
•
VNC password is not retained in iDRAC after an iDRAC reboot.
•
Assertion of PSx-PG-Fail in the SEL is automatically de-asserted upon recovery of PSU-Good or removal of
related PSU.
The BIOS configuration job completes with errors when the Virtualization Technology setting is changed.
•
The job status displays an error though the settings are successfully applied.
The WS-MAN interface stops functioning when running several WS-MAN sessions simultaneously.
•
•
Auto Config may not apply the XML configuration changes if the host system is turned on or while using the
Enable Once After Reset
DHCP provisioning option.
•
iDRAC network access issues after iDRAC configuration is reset to the factory defaults.
iDRAC network access issues using shared LOM on PowerEdge FC430 servers.
•
•
Reset to default on Dell PowerEdge M820 results in an unexpected behavior. The IP on the system displays as
IP on the system is 192.168.0.120 instead of 0.0.0.0.
On a system with an ID module installed, the ID module network settings are not configured properly during
•
the initial ID module installation and after performing a reset to default.
•
Fans run at full speed on systems with mixed PERC cards — one PERC card with battery and another card
without battery.
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.
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
appears under
Overview
->
Hardware
section in the iDRAC web interface.
Enhanced Security Mode
Pass all keystrokes to server
disabled in
•
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 connection 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.
•
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.
2. Disable OS to iDRAC Pass-through.
3.
•
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 dependent packages must be installed.
•
CIFS supports both IPv4 and IPv6 addresses but NFS supports only IPv4 address.
->
LAN Settings
page, may not be correct.
.
Remote SysLog
After the operating system (RHEL) is running, enable OS to iDRAC Pass-through channel through
the iDRAC web interface.
Reboot or power cycle the server, and then re-enable OS to iDRAC Pass-through.
, 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
->
•
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.
•
When using Auto Config, the config XML filename must be specified in the DHCP server using the -f
<filename> flag.
iDRAC - Know n Issue s
Issue 1:
Description
In Chinese locale on Windows operating syste m, while launching the Virtual Console using Java plug-in, occasionally
you may see a Java compilation error.
Resolution
1. Open the Java control panel.
2. Go to General -> Network Settings.
3. Select Direct Connection and click OK.
Versions/Systems Affected
All Dell PowerEdge systems with iDRAC8.
Issue 2:
Description
If the management station is using Linux operating system with the Pass all keystrokes to server option enabled, you
cannot resize the Virtual Console viewer window by dragging the corners or frame. This is a limitation of X-Windows.
Resolution
Do any of the following:
• Disable the Pass all keystrokes to server option.
• With Pass all keystrokes to server option enabled, open any menu in the Virtual Console viewer window title
bar, and then re-size the window.
Versions/Systems Affected
All Dell PowerEdge systems with iDRAC8.
Issue 3:
Description
Relevant error message is not displayed when you apply the Minimum Fan Speed in PWM (% of Max) with custom or
blank value.
Resolution
Enter the value in the range displayed next to the Custom field.
Versions/Systems Affected
All Dell PowerEdge systems with iDRAC8.
Issue 4:
Description
Relevant error message is not displayed when OS to iDRAC pass-through is disabled or changed to LOM state even if
iDRAC Service Module is installed in the host OS.
Resolution
None.
Versions/Systems Affected
All Dell PowerEdge systems with iDRAC8.
Issue 5:
Description
Cannot set VNC password with quotes.
Resolution
Do not use double quotes for the VNC password.
Versions/Systems Affected
All Dell PowerEdge systems with iDRAC8.
Issue 6:
Description
In some scenarios, typically for state change events occurring within a span of few seconds, the sequence of events
reported in the Lifecycle Log (or corresponding SNMP traps) for storage devices may not exactly match the sequence
in which they occurred.
Resolution
Check the current state or attribute of the storage device using any of the iDRAC8 interfaces (example, iDRAC8 web
interface, RACADM, and so on).
Versions/Systems Affected
All Dell PowerEdge systems with iDRAC8 and out-of-band enabled PERC storage controllers.
Issue 7:
Description
When enclosures connected in the redundant path are re-wired (connections are switched) to result in a non-redundant
path, the reported connected port value of the enclosures may not be accurate.
Resolution
Power cycle the server.
Versions/Systems Affected
All Dell PowerEdge systems with iDRAC8 and out-of-band enabled PERC storage controllers.
Issue 8:
Description
When a storage enclosure is disconnected or accidentally removed, the corresponding status of its components (that is,
EMM, PSU, fan, and temperature sensors) is reported as critical.
Resolution
If the storage enclosure is disconnected accidentally, reconnect it to get back to normal state. If it is intentional, perform
iDRAC8 reboot or server power cycle to remove the enclosure entries from the consoles.
Versions/Systems Affected
All Dell PowerEdge systems with iDRAC8 and out-of-band enabled PERC storage controllers.
Issue 9:
Description
After performing storage operations on PERC through Option-ROM (CTRL-R) or before a system reset (warm boot),
the corresponding events are not recorded in Lifecycle log. SNMP traps are generated and the corresponding inventory
changes are not reflected in the iDRAC8 web interface or RACADM.
Loading...