TITLE: BL870c System, BMC, iLO-2 MP and FPGA Firmware VERSION: System FW BMC FW iLO-2 MP FW PDH FW UCIO FW PIC

FW : : : : : : 04.31 05.38 T.03.18 50.07 03.0b 00.05

DESCRIPTION: This package contains EFI applications to update the System, BMC, iLO-2 MP and F PGA firmware and contains the firmware images. UPDATE RECOMMENDATION:Critical HP recommends systems used in Mission Critical environments update to this revis ion of firmware during the next system maintenance period in order to improve sy stem reliability. [X] Critical [X] Panic, [ ] Hang, [ ] Abort, [ ] Corruption, [ ] Memory Leak, [ ] Other _Security_ [ ] Hardware Enablement, [ ] Software Enablement [ ] Required [ ] Recommended [ ] Optional [ ] Hardware Enablement, [X] Software Enablement, [X] non-critical [ ] Initial Customer Release SUPERSEDES: System FW BMC FW iLO-2 MP FW PDH FW UCIO FW PIC FW : : : : : : 04.26 05.38 T.03.18 50.07 03.0b 00.05

PRODUCT MODEL(S): HP Integrity BL870c Server OPERATING SYSTEMS: HP-UX 11i v2 HP-UX 11i v3 Windows Server 2003 64-bit Enterprise Edition Microsoft Windows Server 2008 Itanium Red Hat Enterprise Linux AS 4 Red Hat Enterprise Linux AS 5 SUSE Linux Enterprise Server 10 SUSE Linux Enterprise Server 11 OpenVMS V8.3-1H1 OpenVMS V8.4 LANGUAGES: International English ENHANCEMENTS:

None FIXES: System FW 04.31 In rare circumstances, an attempt to set system boot path information on a runni ng OS (including HP-UX setboot, Service Guard TOC (Transfer Of Control)) may cau se a panic or MCA if system is reset at the same time. This is now fixed. Hewlett-Packard continually strives to provide customers with the highest qualit y of products. To meet this goal, several minor performance and reliability impr ovements have been identified that Hewlett-Packard has included in this firmware release. PREREQUISITES: The iLO-2 MP firmware update will fail if the "Allow MP firmware upgrade via PCI" option is disabled in the iLO-2 MP submenu under Security Options menu. To update the firmware using this package, enable this option in the Security Opti ons sub-menu of the iLO-2 MP Security Options menu. For Flex-10 & Virtual IDs to work properly: Requires OA firmware version 2.60 Pass 13 or newer Requires firmware version VC 2.31 Pass 2 or newer Requires firmware version BMC 5.38 or newer Note: It is recommended to use the latest OA and VC versions for the blade syste m enclosure documented in the Bladesystem Release Sets for Integrity matrix at http://h18004.www1.hp.com/products/blades/integrity-release-sets.html INSTALLATION INSTRUCTIONS: Before installing this package, review all instructions and the "Hewlett-Packard Support Tool License Terms" or your Hewlett-Packard support terms and condition s for the following information: Precautions Scope of license Restrictions and limitation of liability and warranties It is important that you read and understand these instructions completely befor e you begin. This can determine your success in completing the firmware update. WARNING Do not disconnect power during the upgrade process or the ROM will be corrupted. Prior to Installation: Clear the system event logs. Establish a telnet session with the iLO-2 MP. Logon to the iLO-2 MP using the Admin password. Type "SL" to enter the Show Logs menu. At the "Enter menu item or [Ctrl-B] to Quit:" prompt, type "C". At the "Are you sure you want to clear all logs? (Y/[N]):" prompt, type "Y". The following should be displayed: -> Logs have been cleared. Instalation Instructions: HP-UX -Loading Firmware files onto EFI partition

You may need superuser privileges. Download "PF_CBORASYS0431EFI.tar.gz" and then FTP to an empty directory on the server requiring the firmware update. Use "gunzip" to unzip the file: # gunzip PF_CBORASYS0431EFI.tar.gz Use the "tar" command to extract the firmware files "update_SFW.nsh", "fweup date_1p95.efi": # tar -xvf PF_CBORASYS0431EFI.tar Determine the character-special device file for the EFI partition on your di sk. Depending upon the volume manager installed, the path may vary.Check the "bd f" output. # bdf Filesystem %used Mounted on /dev/vx/dsk/rootdg/rootvol 1048576 409432 634296 39% / /dev/vx/dsk/rootdg/standvol 1835008 309536 1513632 17% /stan /dev/vx/dsk/rootdg/varvol /dev/vx/dsk/rootdg/usrvol /dev/vx/dsk/rootdg/tmpvol /dev/vx/dsk/rootdg/optvol /dev/vx/dsk/rootdg/homevol 4718592 596480 4093712 4539568 3054808 1473224 4194304 21288 4140424 7599584 4810176 2767680 102400 5792 95864 13% 67% 1% 63% 6% /var /usr /tmp /opt /home kbytes used avail

If the disk path is of the format /dev/vx/dsk/* then VxVM is installed. Howe ver if the disk path is of the format /dev/vg* then LVM is installed.Depending o n the volume manager installed, proceed to the correct section below. For VxVM users: Type "vxdisk list" to get the list of disks. The file wi ll be /dev/vx/dmp/*s1. (i.e./dev/vx/dmp/c2t1d0s1) # vxdisk list DEVICE TYPE DISK GROUP c2t0d0s2 auto:LVM c2t1d0s2 auto:hpdisk rootdisk01 rootdg STATUS LVM online

Do a "vxprint" command on the disk belonging to the group "rootdg".In th e above output, the disk would be "rootdisk01" # vxprint -l rootdisk01 Disk group: rootdg Disk: rootdisk01 info: diskid=1201226032.5.hpdst167 assoc: device=c2t1d0s2 type=auto flags: autoconfig device: path=/dev/vx/dmp/c2t1d0s2 devinfo: publen=34640800 privlen=1024 timeout: 30 Note the device file of the disk. In this example the disk device file w ould be "c2t1d0" and the device file for the EFI partition would be "/dev/vx/dmp /c2t1d0s1". For LVM users: Check "bdf" output to identify the name of the disk assoc iated with the root "/" directory # bdf Filesystem /dev/vg00/lvol3 kbytes used avail %used Mounted on 409600 191592 216336 47% /

/dev/vg00/lvol1 /dev/vg00/lvol8 /dev/vg00/lvol7 /dev/vg00/lvol4 /dev/vg00/lvol6 /dev/vg00/lvol5

311296 69296 240160 2613248 1087200 1515664 4390912 2515064 1861224 204800 8544 194728 3465216 1982064 1471600 24576 8432 16032

22% 42% 57% 4% 57% 34%

/stand /var /usr /tmp /opt /home

In the above output, the disk would be lvol3. Depending on the operating system installed, the device file for the EFI partition may vary. For HP-UX 11i v2: The file will be /dev/rdsk/*s1. (i.e. /dev/rdsk/c2 t1d0s1) For more information, type "man vgdisplay" and " man 4 efi". Do a lvdisp lay command with the name of the disk associated with the root "/" directory obt ained from the output of "bdf". # lvdisplay -v /dev/vg00/lvol3 | more --- Distribution of logical volume --PV Name LE on PV PE on PV /dev/dsk/c2t1d0s2 50 50 Note the device file of the disk. In this example the disk device fi le would be "c2t1d0" and the device file for the EFI partition would be "/dev/rd sk/c2t1d0s1". For HP-UX 11i v3: The file will be /dev/rdisk/*p1. (i.e. /dev/rdisk/ disk2_p1) For more information, type "man vgdisplay" and "man 4 efi".Do a lvdisp lay command with the name of the disk associated with the root "/" directory obt ained from the output of "bdf". # lvdisplay -v /dev/vg00/lvol3 | more --- Distribution of logical volume --PV Name LE on PV PE on PV /dev/disk/disk2_p2 256 256 Note the device file of the disk. In this example the disk device fi le would be "disk2" and the device file for the EFI partition would be "/dev/rdi sk/disk2_p1". Type the following command to create the /efi/hp/firmware folder in the EFI partition using the character-special device file determined in step 4 in place of "/dev/rdsk/c2t1d0s1": # /usr/sbin/efi_mkdir -d /dev/rdsk/c2t1d0s1 /efi/hp/firmware Type the following command to copy the "update_SFW.nsh" file to the folder c reated in EFI partition in the above step. # /usr/sbin/efi_cp -d /dev/rdsk/c2t1d0s1 update_SFW.nsh /efi/hp/fir mware/update_SFW.nsh Type the following command to copy the "fweupdate_1p95.efi" file to EFI: # /usr/sbin/efi_cp -d /dev/rdsk/c2t1d0s1 fweupdate_1p95.efi /efi/hp /firmware/fweupdate_1p95.efi Verify that the files were successfully copied to the EFI partition using th e following command: # /usr/sbin/efi_ls -d /dev/rdsk/c2t1d0s1 /efi/hp/firmware Type:

# /usr/sbin/shutdown -ry now to reboot the system to the "EFI Boot Manager". When the "EFI Boot Manager" menu appears, use the arrow keys to highlight th e entry "EFI Shell [Built-in]", then press ENTER to select it. The selection mus t be made within the timeout period displayed on the screen. The "Device mapping table" will be displayed. Proceed to "OS Independent - Updating Firmware from EFI shell", shown below. HP-UX - Cleaning up the EFI partition (after firmware has been updated) Type the following command to remove the "update_SFW.nsh" file in the EFI pa rtition using the character-special device file determined in step 4 of the abov e section in place of "/dev/rdsk/c2t1d0s1": # /usr/sbin/efi_rm -d /dev/rdsk/c2t1d0s1 /efi/hp/firmware/update_SF W.nsh Type the following command to remove the "fweupdate_1p95.efi" file from EFI partition. # /usr/sbin/efi_rm -d /dev/rdsk/c2t1d0s1 /efi/hp/firmware/fweupdate _1p95.efi Linux - Loading Firmware files onto EFI partition You may need superuser privileges. Download "PF_CBORASYS0431EFI.tar.gz" and then FTP to an empty directory on the server requiring the firmware update. Type: # mkdir -p /boot/efi/hp/firmware Use "gunzip" to unzip the file: # gunzip PF_CBORASYS0431EFI.tar.gz Use the "tar" command to extract the firmware files - "update_SFW.nsh","fweu pdate_1p95.efi": # tar -xvf PF_CBORASYS0431EFI.tar Type: # cp update_SFW.nsh /boot/efi/hp/firmware/update_SFW.nsh Type: # cp fweupdate_1p95.efi /boot/efi/hp/firmware/fweupdate_1p95.efi Type: # reboot to reboot the system to "EFI Boot Manager". When the "EFI Boot Manager" menu appears, use the arrow keys to highlight th e entry "EFI Shell [Built-in]", then press ENTER to select it. The selection mus t be made within the timeout period displayed on the screen.

The "Device mapping table" will be displayed. Proceed to "OS Independent - Updating Firmware from EFI shell", shown below.

Linux - Cleaning up the EFI partition (after firmware has been updated) Type # rm /boot/efi/hp/firmware/update_SFW.nsh to remove the "update_SFW.nsh" file from the EFI partition. Type the following command to remove the "fweupdate_1p95.efi" file from EFI partition # rm /boot/efi/hp/firmware/fweupdate_1p95.efi Windows - Loading Firmware files onto EFI partition Click "Start" on the taskbar, then click "Run..." . Type "cmd", then press ENTER. A command prompt window opens. Type "mountvol z: /s", then press ENTER. "z" can be replaced with any availa ble drive letter in your system. Type: "mkdir \efi\hp\firmware". Download the firmware update package "PF_CBORASYS0431EFI.tar.gz" and unpack it to obtain "update_SFW.nsh", "fweupdate_1p95.efi". Save "update_SFW.nsh", "fwe update_1p95.efi"in z:\ . Reboot the system to "EFI Boot Manager"; see next step. When the "EFI Boot Manager" menu appears, use the arrow keys to highlight th e entry "EFI Shell [Built-in]", then press ENTER to select it. The selection mus t be made within the timeout period displayed on the screen. The "Device mapping table" will be displayed. Proceed to "OS Independent - Updating Firmware from EFI shell", shown below.

Windows - Cleaning up the EFI partition (after firmware has been updated) Click "Start" on the taskbar, then click "Run..." . Type "cmd", then press ENTER. A command prompt window opens. Type "mountvol z: /s", then press ENTER. "z" can be replaced with any availa ble drive letter in your system. Type "z:" . Type "del update_SFW.nsh" and "del fweupdate_1p95.efi" to remove the firmwar e update files from the EFI partition. Type "mountvol z: /D" to unassign the drive letter z: used. Type "exit" to close the command prompt window. OS Independent - Updating Firmware from EFI Shell For general information about using EFI, refer to the "Operation and Maintenance Guide". At the shell prompt, type "fs0:", replacing "fs0:" with each "fs" entry in t he table until you find the volume containing the "update_SFW.nsh" file that was copied to the EFI partition in the previous instructions. We will assume this v olume is labeled fs0 for the remainder of these instructions. Type "fs0:", then press ENTER.

Locate the file "update_SFW.nsh" and type "update_SFW.nsh", then press ENTER . The MP connection will be lost. Wait for a few minutes and then reconnect to the MP. The server will reset after completing the flash. Boot to your operating sys tem. Clean up any resulting firmware update files from the EFI partition by follo wing your operating system specific instructions. COMPATIBILITY/INTEROPERABILITY: WARNING: Minimum Onboard Administrator (OA) firmware version of 2.10 is required on t he C7000 and the C3000 Blade System enclosures in order to support the HP Integr ity BL870c Server. WARNING: After this firmware upgrade, Users of Operating Systems other than Windows S erver 2003(HPUX/Linux/VMS/Windows Server 2008) should set the MPS optimization s witch ON at the EFI shell to improve the IO performance.This setting defaults to OFF, because of an incompatibility with Windows Server 2003. shell> ioconfig mps_optimize on WARNING Minimum Virtual Connect (VC) firmware version of 2.31 is required to support this release of System firmware for HP Integrity BL870c Server. For Flex-10 & Virtual IDs to work properly: Requires OA firmware version 2.60 Pass 13 or newer Requires firmware version VC 2.31 Pass 2 or newer Requires firmware version BMC 5.38 or newer Note: It is recommended to use the latest OA and VC versions for the blade syste m enclosure documented in the Bladesystem Release Sets for I ntegrity matrix at http://h18004.www1.hp.com/products/blades/integrity-release-sets.html DETERMINING CURRENT VERSION: Establish a telnet session with the iLO-2 MP. Logon to the iLO-2 MP using the Admin password. Type "CM" to enter the Command Menu. Type "SYSREV" to display system revision information. The following should b e displayed if the current firmware is installed: Current firmware revisions MP FW BMC FW EFI FW System FW PDH FW UCIO FW PRS FW PIC FW : : : : : : : : T.03.18 05.38 ROM A 07.15, ROM B 07.15 ROM A 04.31, ROM B 04.26, Boot ROM A 50.07 03.0b 00.08 UpSeqRev: 03, DownSeqRev: 01 00.05

NOTE: Only one of the System FW ROMs will be upgraded in the firmware update process, therefore the two ROMs may show different firmware revisions. The Boot ROM should contain the latest firmware. If the System firmware revision in the current Boot ROM, or any other firmwa

re component is less than those listed above, then firmware should be updated. KNOWN ISSUES: System firmware versions 04.03 and later require the following HP-UX package s be installed in order for HP-UX to respond to power policy changes made via iL O-2 Power Regulator and HP Insight Power Manager The packages are available from the HP IT Resource Center (ITRC) website at: http://itrc.hp.com. For systems with 0709 HP-UX 11i v3 OE, you must install the following pa tches: PHKL_36654,PHKL_36477,PHKL_36478, PHKL_37724,PHKL_37032 For systems with 0803 HP-UX 11i v3 HWE, you must install the following p atches: PHKL_37724 The vMedia USB key can be connected to the server even if the local client h as current open access. This can lead to files being unexpectedly overwritten. T he user should verify that all local USB key access is closed prior to connectin g to the server. The iLO-2 MP Web Console size is adjustable by zoom out, then clicking and d ragging the corner to desired size. After changes to the Emulation configuration , the Web Console may require a click in the text space or click of the Reset bu tton to start working properly. Restricting iLO-2 MP access using Time Restriction settings in the e-Directo ry does not work correctly with 1/2 time zones. Cookies must be enabled on the web browser in order to successfully login to the iLO-2 MP WEBGUI. When attaching the dongle cable to a BL870c in a C3000 enclosure, care shoul d be taken to ensure that as much weight/tugging as possible on the cable be rem oved. If the connector is at all bent, there could be connectivity problems that would result in a number of communication errors. Users who cannot connect to Fiber Channel drives in Linux (particularly duri ng a Linux install) when using a Virtual Connect interconnect must change the EF I drivers settings for the Qlogic Fiber Channel EFI driver to use "Point to Poin t" mode instead of "Loop Preferred". iLO-2 Virtual Media installation of this firmware package via remote MP conn ection to an ISO image file is not supported. The ISO image must be burnt to CD/ DVD media and mounted on a physical drive connected to the target system. The new enhancement "vFlash beyond 2 GB support" will not work properly, if the target is remote. DISCLAIMER: The information in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this material, incl uding, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contai ned herein or for incidental or consequential damages in connection with the fur nishing, performance, or use of this material. This document contains proprietary information that is protected by copyright. A ll rights are reserved. No part of this document may be reproduced, photocopied, or translated to another language without the prior written consent of HewlettPackard Company. (C) Copyright 1994-2012 Hewlett-Packard Development Company, L.P. ADDITIONAL COPYRIGHT NOTICE: Copyright (C) 2004, Intel Corporation All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, th is list of conditions and the following disclaimer in the documentation and/or o ther materials provided with the distribution. Neither the name of the Intel Corporation nor the names of its contributors may be used to endorse or promote products derived from this software without sp ecific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WA RRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DA TA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LI ABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. SUPERSEDES HISTORY: System FW 4.26 ENHANCEMENTS: Enables building a profile on a bl8x0c i2 system with FC boot options and move t he profile to a bl870c. The device paths of the boot options will get adjusted f or the different bl870c topology and still be able to boot. Virtual MAC addresse s that have been set for LOMs or an Ethernet card in the profile will be applied to the corresponding LAN device on the bl870c and it can then be lanbooted from the same BOOTP server that handled the bl8x0c i2. FIXES: None ENHANCEMENTS: None. FIXES: System FW 4.25 Fixed random MCAs with XPN and zx2 logging rope forward progress timeouts, W ith an MCA signature not otherwise easily traceable to a hardware, firmware, or software problem. iLO-2 FW T.03.18 Fixed problem that prevented the entry of "|", "/" and "_" characters from a Japanese keyboard connected through the iLO Virtual Keyboard feature. ILO reset from Web will now log XD_MP_RESET or other events in the event log like ILO reset from SSH connection does. Fixed an issue with Telnet NOP, where iLO would hang and stop the boot proce ss when iLO console is connected via telnet Fixed an issue where HP-SIM operation would cause the iLO to reset.

Fixed an issue where executing the nMap command for scanning ports on iLO co uld lead to a iLO reset Corrected the display of IP address as 0.0.0.0 in the iLO event log for ssh exec commands including SMASH Fixed a condition that prevented SSH Login in the format "cn=Username,USC". Fixed an issue in which IMPI Power Request command could return incorrect po wer values Fixed an issue that prevented LDAP authentication for user@domain.com and do main/user format to work Fixed an issue where some Virtual Media connection request could cause iLO t o hang Fixed the issue of Auto-login from OA not working ENHANCEMENTS: System FW 04.21 Updated system ID policy to support BL870c front panel replacement. Added support for updating CLP support level version in FRUs for Virtual Con nect FlexFC-capable mezzanine cards. Updated Virtual Connect EFI boot entry re-ordering to support multiple boot targets per port. System FW 04.05 Added support for Microsoft Windows Server 2008 Itanium. Updated SMBIOS to version 2.4. Added extended EFI NVM area. Added support for 64-bit CLP LUN values. Added support for reading blade enclosure serial number. Implemented support for hardware error record EFI variables. Added support for display of virtual serial number and UUID. Implemented support for Virtual Connect management of SAN boot settings. 8GB DIMM enhancement - have the monarch check in every so often while retest ing memory when an error occurs. iLO-2 FW T.03.12 Added an IPMI handler to set the iLO-2 LAN parameters, if the command is sen t from BMC. This will enable using the ilosetup.efi utility to set the iLO-2 LAN parameters from EFI. iLO-2 FW T.03.10 Added new log "iLO-2 Event Log" which contains events corresponding to Login /Logout actions to iLO-2 and execution of selected iLO-2 commands. Added the license installation date as part of the license information ("lm" command). Status Summary page in iLO-2 WEBGUI will now refer "Virtual Serial- Number" as "Logical Serial Number" and "Virtual UUID" as "Logical UUID". Support for vFlash is extended beyond 2 GB. A user with "M" configuration rights will now be able to use the "PM" comman d. FIXES: System FW 04.11 Fixed the issue wherein the VC Flex-10 MAC address assignment was failing.

Changed the output of INFO SYS to denote virtual UUID, virtual S/N as "Logic al". Changed output of PDT to not display "SBE" or "MBE". System FW 04.05 During extensive lab testing, HP observed a general exception fault occurrin g with a Machine Check Abort (MCA) on Dual Core Intel(R) Itanium(R) 9000 series (Montecito) and 9100 series (Montvale) processors. An MCA arriving during a call to PAL_MC_ERROR_INFO will cause corruption of the stacked registers for MCAs, w hich are not PAL corrected, resulting in undefined behavior. This has not been o bserved outside extreme stress testing in the lab environment. Fixed an issue where SFW not sending any notification to OS when lowest powe r is required. Previously, When VC SAN boot mode is enabled, an MCA occurs at EFI after dis playing the banner for the first core FC EFI driver instance. PXE/network boot will no longer fail to try to connect to all DHCP servers i n the domain. All USB flash drives are now accessible at EFI using the iLO-2 vMedia. Fixed an issue where wrong CPU frequency value of Dual core Intel(R) Itanium (R) 9100 series (Montvale) processors were being displayed. EFI shell "FTP" Put Operation will no longer fail with new Intel(R) EFI Driv ers. BMC FW 05.38 Corrected a problem that occurred after upgrading the Onboard Administrator firmware from version 2.30 to 2.32 pass 1 (or later). The Virtual/Logical Serial Number and Virtual UUID would be truncated, or no longer appear in the OA Web, OA CLI, or BL870c EFI 'info sys' Interfaces. Corrected issue for enclosures with VC installed and profiles applied that d o not have Virtual UUID and Serial Numbers enabled (i.e. Synergy Mode). The blad e erroneously indicated that Synergy mode was still enabled. This causes the Vir tual IDs to be propagated up to the OS which could cause licensing issues for so me OS applications. BMC FW 05.36 Virtual ID information now visible on BL870c after upgrading/resetting the O A. BMC FW 05.35 Fixed the MP-BMC Communication problem after an OS installation. Fixed the issue wherein the power calculation was wrong after the blade is r emoved and memory configuration is either increased or decreased. Fixed the issue of serial number being returned with FF's sometimes. BMC FW 05.32 Fixed a failure to write some variables if the user has set a user/admin pas sword. This was seen while using EBSU DVD 6.0. iLO-2 FW T.03.15

Introduced a check to only permit only users with console access rights to v iew the console logs. Otherwise the message "The user does not have sufficient p rivileges to execute this command." will be displayed. Corrected an issue were the iLO was not sending out all the SNMP traps to it s destinations when there were multiple SNMP packets to be sent out. When the SNMP trap destination is enabled and is on for more than 3 to 4 day s, the iLO would send false SNMP traps (power on and power off) to the recipient s. This has been corrected. If upgrading from an iLO version T.02.17 or earlier using the iLO FW command on an enclosure with OA FW that does support the eFuse request, the system powe r could be turned off automatically if the iLO was not reset after it was update d. This rare upgrade scenario is now properly addressed. Corrected a momentary timing issues were the temperature values for the OA c ommand 'show server temp status' would not be displayed if the MP was booting. N ow if the command is sent before the MP is ready the MP returns an error. Fixed a condition that could occur when a valid profile is applied and Logic al UUID/SN are not enabled. There was a possibility that even though the OA retu rns the synergy state as ON, the logical serial number and logical UUID may not be set or a profile may not be applied. In such cases the iLO could display inac curate Logical serial & UUID values in both the web page and the XML output. iLO-2 FW T.03.12 When the user enters the https URL in the browser address bar, the iLO-2 con tinues to use the same access method the user has entered for their browser sess ion, be it IP, domain name, or the fully qualified domain name. The address bar in the browser no longer switches to the iLO-2's IP address when a DNS/FQDN name is given in the browser. NAT issue has been resolved for Remote Serial Console and Virtual Media Appl et in iLO-2 GUI. iLO-2 reset requires "MP" configuration rights to be executed. The Delete/Backspace key of the Remote Serial Console feature in iLO-2 GUI i s now set when "checked" and also works as per the expected functionality when t he emulation is set to vt100+. Fixed the issue in LDAP-lite iLO feature, wherein anonymous logon is needed to be enabled at Microsoft Active Directory for LDAP-lite to work. Now an anonym ous logon setting at the directory is no longer required. The issue of vUUID and vSN corruption when blade is reseated, has been fixed . iLO-2 FW T.03.10 The blade will now try continuously to power on until it is successful. Additional note is now added requesting user to close all open files on USB key before launching the vMedia/vUSB. A long push button reset of MP is provided as a workaround for the issue whe re "MP is not responding while login, if LDAP is enabled with Novell e-Directory ".This push button reset will disable LDAP and allow local user login. On the "blades" in iLO-2 WEBGUI, the "Rack UID" is now correctly referred to as "Rack UUID". Memory leak via SSH connection has been resolved. INITIAL RELEASE: System FW : 03.11 BMC FW : 05.04 iLO-2 MP FW : T.02.17

PDH FW UCIO FW PRS FW PIC FW

: : : :

50.07 03.0b 00.08 00.05

FEEDBACK As we are continuing to improve the firmware management process we welcome your feedback on this document and on the firmware update process. TEAM-FWupdateFeedback@external.groups.hp.com