Integrated Dell Remote Access Controller 7 (iDRAC7) Version 1.50.50 and Lifecycle Controller 2 Remote Services Version 1.3.
Release Notes Integrated Dell Remote Access Controller 7 (iDRAC7) iDRAC7 is a systems management hardware and software solution that provides remote management capabilities, crashed system recovery, and power control functions for Dell PowerEdge systems. Lifecycle Controller 2 Remote Services (LC2-RS) LC2-RS provides advanced embedded systems management and is delivered as part of iDRAC7. LC2-RS enables remote systems management in a one-to-many method.
What is Supported? Supported Managed Server Operating Systems for iDRAC7 The following operating systems support iDRAC7: • Windows Server 2008 SP2 (32-bit) • Windows Server 2008 SP2 (64-bit) • Windows Server 2008 SP2 R2 (64-bit) • Microsoft Server 2012 Essentials • Microsoft Server 2012 R2 • Red Hat Enterprise Linux (RHEL) version 5.9 • Red Hat Enterprise Linux (RHEL) version 6.4 • Red Hat Enterprise Virtualization (RHEV) Hypervisor 5.
• Configure VNC Server to view remote desktop using mobile devices • Configure LOM or USB NIC as the OS to iDRAC Pass-through channel • Enable or disable I/O Optimization • Enabling events to be logged into OS log • Export the Lifecycle log entries to a network share or to the local system. • Improved Virtual Media menu options: o Connect or disconnect Virtual Media session from Virtual Media menu. o Specify the location of the image file that is created from the folder.
• Drives that cannot be accessed may be displayed in the Virtual Media configuration menu when using the Java plug-in. This occurs if inaccessible network shares or storage devices are configured on the management station (for example, by the IT department). • On 12th generation PowerEdge blade servers, in the iDRAC Web Interface, the WWN/MAC page does not correctly report the chassis-assigned MAC addresses for the Intel i350 mezzanine card.
• If the iDRAC7 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.
• Remote Sys Log settings take effect only if you do the following: − Enable remote syslog feature − Specify the server address and port number − Enable Remote SysLog option on the Alerts page • When IVYBRIDGE CPU is installed on PowerEdge R720, R720xD, R620, T620, or M620 systems, the iDRAC7 firmware update from 1.45.45 to an earlier version is not allowed (example, from 1.45.45 to 1.40.40 or to 1.37.35, and so on).
Resolution (only for logging in to iDRAC7 Web interface): 1. 2. 3. 4. Register iDRAC7 to DNS. Make sure the client system also has this DNS in its DNS list. Enable IPv6 and disable IPv4. Log in to iDRAC7 using the Fully Qualified Domain Name (FQDN). For launching Virtual Console with IPv6 in Firefox 4.0 or later versions, from Windows management system, run ipconfig /flushdns in the command prompt. Versions/Systems Affected All iDRAC7 supported Dell PowerEdge systems.
Resolution You must manually enable or disable the vFlash functionality after the firmware update as required. To do this, select or clear the vFlash Enabled option in the iDRAC7 Web interface, or use RACADM or WinRM remote service commands. Versions/Systems Affected All iDRAC7 supported Dell PowerEdge(TM) systems.
Versions/Systems Affected All Dell PowerEdge systems with iDRAC7. Issue 11: Description On Microsoft Windows7 operating system, while launching Virtual Console in native mode using Internet Explorer, the iDRAC7 Login page is displayed. Virtual Console uses plug-ins and due to insufficient privileges plug-in does not load and iDRAC7 Login page is displayed. Resolution Reboot operating system and log in to iDRAC7 Web interface. Versions/Systems Affected All Dell PowerEdge systems with iDRAC7.
as RACADM or the Web interface. Remote RACADM can be used in a script to batch-enable Active Directory. If a local iDRAC7 user is not enabled or is not configured for remote access, the administrative user must use local RACADM or OpenManage Server Administrator to configure a local user. Versions/Systems Affected All Dell PowerEdge systems with iDRAC7.
Issue 19: Description In the iDRAC7 Web interface -> Overview -> Server -> Power/Thermal -> Power Monitoring tab -> Power section, the Power Unit selector only changes the unit of measure. Due to the oscillating nature of power, the Present Reading cannot be displayed as units for Current (Amps). Resolution None. Versions/Systems Affected All Dell PowerEdge systems with iDRAC7.
Versions/Systems Affected All Dell PowerEdge systems with iDRAC7 and out-of-band enabled PERC storage controllers. Issue 24: Description If a NIC card, with partitioning enabled, is replaced with a similar type of card, without partitioning enabled, the configurations from the previous card are not applied to the new card. Resolution: After the previous card is replaced with a new card and the system is powered on, go to OptionROM (CTRL-R) and enable partitioning. Save, exit, and reboot the system.
Issue 28: Description: When running the Virtual Media client on Windows 7 or Windows Server 2008 R2, the Virtual Media client may not be able to access a floppy disk in read-write mode because of a problem with the client workstation operating system. Resolution: Apply the operating system update to the Windows 7 or Windows Server 2008 R2 client workstation operating system as specified in the following link: http://support.microsoft.com/kb/2496290.
Resolution: Obtain an appropriate license then try again. If the problem persists, contact the technical support. See the product documentation to choose the contact method that is convenient for you. Versions/Systems Affected: All Dell PowerEdge systems with iDRAC7. Issue 33: Description: If you try to upload any other certificate other than a valid PKCS#12 format file, the iDRAC Web interface displays an incorrect error message. Resolution: Upload a valid PKCS#12 format certificate file.
Versions/Systems Affected Dell PowerEdge M520 Issue 37: Description Sometimes invalid characters are displayed on the server console screen after exiting iDRAC Virtual Console. Resolution Launch virtual console and clear the Automatic System Lock option. Versions/Systems Affected All Dell PowerEdge systems with iDRAC7. Issue 38: After an iDRAC7 firmware update, some of the iDRAC7 Web interface panels or navigation menu items may contain incorrect or invalid entries.
If you want to update the firmware to an earlier version (example, from 1.45.45 to 1.40.40 or to 1.37.35, and so on), use the iDRAC7 Web interface instead of a DUP package. If you have to use a DUP, then before running the DUP, make sure there are no active Virtual Media sessions on iDRAC. Versions/Systems Affected: All 12th generation Dell PowerEdge servers with Windows Server 2012 R2 operating system.
Issue 46: Description Full export of Lifecycle Controller logs in Mac OS through Safari browser generates Log.xml file instead of Log.xml.gz file and the Log.xml contains partial content. Resolution 1. 2. 3. Open Safari in Mac. Go to Safari > Preferences > General. Clear the Open 'safe' files after downloading option. Versions/Systems Affected All iDRAC7 supported Dell PowerEdge systems.
Resolution To enable OS to iDRAC pass-through in shared mode: 1. 2. 3. 4. 5. Set the static IP address on the host system using the Network Manger GUI or edit the /etc/sysconfig/network-scripts/ifcfg-eth0 file. Set the static IP address for the iDRAC in the same subnet Enable OS to iDRAC pass-through feature. For the steps, see iDRAC7 User’s Guide at www.dell.com/esmmanuals. Reboot the host system. After restarting the host system, connect to the iDRAC using the static iDRAC IP address.
iDRAC7 - 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.
− 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. − 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.
LC2-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.
• 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.
Uninstallation Use the rollback feature to return to the previous installed version of iDRAC7 firmware. For more information, see the iDRAC7 User's Guide available at http://www.dell.com/support/Manuals/us/en/555/Product/integrated-dell-remote-access-cntrllr-7v1.50.50. Lifecycle Controller 2 Remote Services - Client Tools Use the WinRM and OpenWSMAN CLI client tools to send WS-MAN commands to Lifecycle Controller. WinRM WinRM is a Windows native WS-MAN client. It is recommended to use WinRM 2.
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 these options: -c, -v, and –V. See the OpenWSMAN CLI readme for details on these options. 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.
-----------------------------------------------------------------------------Information in this document is subject to change without notice. © 2013 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.
