****************************************************************
| |
| Tape LTO 6 firmware update |
| |
| |
| (C) Copyright International Business Machines Corporation |
| 2000-2012 . All rights reserved. |
| |
| US Government Users Restricted Rights -- Use, duplication |
| or disclosure restricted by GSA ADP Schedule Contract with |
| IBM Corp. |
| |
| Note: Before using this information and the product it |
| supports, read the general information under "NOTICES AND |
| TRADEMARKS" in this document. |
| |
| Updated: 10/29/2012 |
| |
****************************************************************

Change History

ver 1.0

Initial Release of LTO 6 firmware update.
This firmware update will change the firmware of your LTO 6 tape drive to the latest
available, unless it is already at the latest level.

- IBM HH LTO 6 SAS drive (35P0994) @ C9T5
ibm_fw_tape_lto6-1_0_windows_32-64_chg

===============================================================================
Emulex 8Gb Fibre Channel Firmware Package
===============================================================================

Firmware Version: 2.02x11
Boot Code Version: 5.30a6
Supported On: System x, BladeCenter and Flex

Problems Fixed:
- SAN boot stopped working after firmware/boot BIOS upgrade

Incremental Interoperability:
- Grantley based ITE

Known Issues:
- To disable BFS after BOFM or IFM have been enabled, it must be done by
setting BFS manually in the EFIBoot config utility or sending a BOFM default
command to the port. This is working as expected and we are documenting it
here.(159225)

===============================================================================

Firmware Version: 2.02x11
Boot Code Version: 5.30a3
Supported On: System x and BladeCenter

Problems Fixed:
- Roll boot code version number to avoid conflict with IBM UXSPi updates

Incremental Interoperability:
- Inventory support for the System x xHMC (Chassis Hardware Management
Console) for IBM Rack FC HBAs
- Grantley Rack Servers

Known Issues:
- To disable BFS after BOFM or IFM have been enabled, it must be done by
setting BFS manually in the EFIBoot config utility or sending a BOFM default
command to the port. This is working as expected and we are documenting it
here.(159225)

===============================================================================

Firmware Version: 2.02x11
Boot Code Version: 5.13x4
Supported On: IBM System x, BladeCenter, and Flex

Problems Fixed:
- Server intermittently fails to boot during rolling SANboot (any OS)
- Fixed a boot hang associated with server BIOS change

Incremental Interoperability:
- Inventory support for the Flex xHMC (Chassis Hardware Management Console)

Known Issues:
- To disable BFS after BOFM or IFM have been enabled, it must be done by
setting BFS manually in the EFIBoot config utility or sending a BOFM default
command to the port. This is working as expected and we are documenting it
here.(159225)

===============================================================================

Firmware Version: 2.01a11
Boot Code Version: 5.13a0
Supported On: IBM System x

Problems Fixed:
- None

Incremental Interoperability:
- UEFI 2.3.1 Compatibility

Known Issues:
- None

===============================================================================

Firmware Version: 2.01a11
Boot Code Version: 5.12a15
Supported On: IBM System x, BladeCenter, and Flex)

Problems Fixed:
- System hang when attempting to enter BIOS screen on AMI BIOS based servers

Incremental Interoperability:
- SLES 11.3 on IBM System x and BladeCenter

Known Issues:
- None

===============================================================================

Firmware Version: 2.01a11
Boot Code Version: 5.12a13
Supported On: IBM System x and BladeCenter

Problems Fixed:
- Emulex FC Adapter does not auto-enable SAN boot mode when boot target
configuration is made via IFM (BOFM)
- Emulex FC configuration utility is in the wrong F1 setup screen
- IBM CIOv adapter connected to Brocade 8 Gig FC BladeCenter switch
intermittently Links up at less than 8 Gig

Incremental Interoperability:
- None

Known Issues:
- None

===============================================================================

Firmware Version: 2.01a9
Boot Code Version: 5.12a11
Supported On: IBM System x and BladeCenter

Incremental Interoperability:
- None

Problems Fixed:
- SANboot problem in IBM BladeCenter

Known Issues:
- None

===============================================================================

Firmware Version: 2.01a9
Boot Code Version: 5.12a10
Supported On: IBM System x, BladeCenter, and Flex

Incremental Interoperability:
- UEFI 2.3.1 compatibility

Problems Fixed:
- Utility in adapter selection screen shows PCIe2.5Gb/s X 4
- Miscellaneous issues with boot BIOS
- Emulex 8gb ciov Port2 does not accept BOFM Boot-order "both"
- Rhel 6.2 UEFI San boot failed w/ Emulex 8Gb FC
- Fix potential I2C bus contention

Known Issues:
- None

===============================================================================

Firmware Version 2.01a3
Boot Code Version: 5.12a5
Supported On: IBM System x and BladeCenter

Incremental Interoperability:
- Enhanced timeout notifications for processing abort failures.

Problems Fixed:
- All multi-abort I/Os are returned on the same ring from which the ABORT_MXRI
command was received.
- Changed the TRCV response in the abort state to CMD RJT to enable the
TRSP to be processed.
- Corrected an issue with blocked TSEND operations.
- Corrected a buffer leak issue with RRQ exchanges.
- Corrected an issue where the TRCV IOCB was de-queued improperly causing a
XFR_RDY flood.
- Corrected an issue where the OXID field was not loaded in the XRI_ABORTED
IOCB.
- Corrected an issue in recognizing whether an EEPROM is present.

Known Issues:
- None

===============================================================================

Firmware Version 2.00a4
Boot Code Version: 5.12a5
Supported On: IBM System x and BladeCenter

- Initial Release

===============================================================================
elx_fw_fc_14a-2_02x11-8_windows_32-64_chg

===============================================================================
Emulex FCoE Device Driver for Windows
===============================================================================

Device Driver Version: 10.2.370.8
Supported On: System x, BladeCenter and Flex

Problems Fixed:
- None

Incremental Interoperability
- Grantley based ITE

Known Issues:
- None

===============================================================================

Device Driver Version: 10.2.370.8
Supported On: System x and BladeCenter

Problems Fixed:
- Failed to enumerate target after zoning change
- UEFI FCoE SANboot Failed with specific targets

Incremental Interoperability
- Grantley Rack Servers

Known Issues:
- None

===============================================================================

Device Driver Version: 10.2.261.4
Supported On: IBM System x, BladeCenter, and Flex

Problems Fixed:
- ABTS sent by tape device ignored by HBA
- BSOD issue during CPU Hot replace test
- XE102/XE104 - OCManager reports link down on both ports

Incremental Interoperability:
- None

Known Issues:
- None

===============================================================================

Device Driver Version: 10.0.720.0
Supported On: IBM System x

Problems Fixed:
- Concurrent Hardware and Operating System (CHAOS) Test fails in XE-10x 10G
- Windows FC driver bug with Data Domain virtual tape library

Incremental Interoperability:
- Emulex Dual port 10Gb SFP+ Ethernet Adapter Card (XE-102/XE-104 based)

Known Issues:
- None

===============================================================================

Device Driver Version: 2.74.016.001
Supported On: IBM System x, BladeCenter, and Flex

Problems Fixed:
- Cleaned up a variety of corner case issues to avoid BSODs
- Fixed IOCTL encounter bug-chk on BE3 during NPIV tests
- Fixed reporting incorrect error code when creating vport on a switch without
NPIV supported
- Updated the default model name for 10Gb CNAs and 16G HBAs

Incremental Interoperability:
- None

Known Issues:
- None

===============================================================================

Device Driver Version: 2.74.014.001
Supported On: IBM System x and BladeCenter

Problems Fixed:
- None

Incremental Interoperability:
- PCI-IDs added for XE4310R controller applications

Known Issues:
- No known issues

===============================================================================

Device Driver Version: 2.74.009.001
Supported On: IBM System x, BladeCenter, and Flex

Problems Fixed:
- Clean up non-critical legacy FC and uCNA incompatibilities
- LUN masking doesn't persist after reboot
- Emulex GUI crashes when closing a running Upgrade utility and re-open it in
802.3 configuration with IP or MAC
- Several bugs related to creation or deletion of vports

Incremental Interoperability:
- Windows 2012
- Improved debug capabilities
- Tighter integration with MS Windows Design Kit

Known Issues:
- None

===============================================================================

Device Driver Version: 2.70.018
Supported On: IBM System x, BladeCenter, and Flex

Problems Fixed:
- Fixed sending ABTS continuously to Flogi issue
- Fixed reset and link bounce issues for SLI4 FC public loop
- Added support for ABTS timeout handling for both SLI3 and SLI4
- Fixed loopback test incorrectly dropping the loopback frame in SLI4
- Fixed exchange management issue in SLI4 CT receive path causing array
overflow
- Fixed firmware version update issue following download in link up state
- Fixed problem in init_vfi completion handler that stalled fabric login on BE
FCoE FW
- Fixed problem that caused OCM ELS Echo Test to fail
- Fixed the loopback test issue in recovering from error condition
- Add persistent link down support for SLI4 FC
- Fix DFC_IssueDumpMBox to manage request type 3 which includes link select
option
- Modified reinitialization sequence following reset to fix discovery failure
post type 1 or type 3 reset
- Fixed new firmware dump issue

===============================================================================

Device Driver Version: 2.41.002
Supported On: IBM System x and BladeCenter

- Initial Release

===============================================================================
elx_dd_cna_14a-10_2_370_8-3_windows_32-64_chg

IBM HBA/LSI 6Gb SAS/SATA/SSD Driver for Windows 2012 R2/2012/2008 R2/2008/2003

Supported Controllers:
- IBM N2125 SAS/SATA Controller (46C9011)
- IBM N2115 SAS/SATA Controller (46C8989)
- ServeRAID H1135 Controller for IBM Flex System and BladeCenter (90Y4750)
- ServeRAID H1110 SAS/SATA Controller for IBM System x (81Y4492)
- IBM 6Gb SAS HBA (46M0907)
- IBM 6Gb SSD HBA (68Y7362)
- Onboard LSI 2004 SAS


NOTE TO SERVICE - Reference RETAIN #N/A

2.00.75.00 - Low Probability of Occurrence/Special Case
------------------

Enhancements:
- Generate a fault/alert when junction temperature approaches max spec (SCGCQ00559883)

- Added timer to prevent ATA commands from hanging. (Needed as part of SCGCQ00694282 fix) (SCGCQ00751758)

Fixes:
- New drive failed to be recognized after replacing a failed SATA HDD (SCGCQ00694282)


Version 2.00.69.01 - Suggested
------------------
Enhancement(s):
- Added driver configuration parameter to control MaxDevices during crash dump
mode.
Fixes:
- Fixed an issue where a blue screen could occur with driver fault AD010042.
- Fixed an issue where PFA LED is not turning off after the PFA drive is removed
from the back plane.

Version 2.00.60.03 - Suggested
------------------
Enhancements(s):
- Added support for Windows 2012 R2

Version 2.00.60.00 - Suggested
------------------
Enhancements(s):\
- Added support for 8MB+ IO's
- Modified sense data processing code to check for an ATA Passthrough command
(either 12 or 16 byte).
- Added RTTrace hooks to increase logging coverage within driver.
- Implemented Extended SRB support (StorPort enhancement) in driver.
- Added checks to catch physical DMAable memory allocations outside a single 4GB
block as required by the adapter hardware.

Fixes:.
- Fixed an issue where cable break between enclosures causes the adapter to reset.
- Fixed an issue where MSM sends input/output control causing BSOD in Windows 2012
Extended SRB driver.
- Fixed an issue where SAS2FLASH sends input/output control causing BSOD in Windows
2012 Extended SRB driver.
- Fixed data alignment issue which could result in corrupt sense data under Windows
2012.
- Changed RTTRACE version to match record structure used by driver.
- Fixed an issue in Windows Server 2003 where executing LSIutil 1.65 Option 65
virtual serial port causes a bluescreen if memory has been severely fragmented.


Version 2.00.45.00 - Suggested
------------------
Ehancement(s):
- Add support for ServeRAID H1110 SAS/SATA Controller for IBM System x
- Add conversion of sense data descriptor format to fixed format, so drives 2.1TB in
size and greater can return descriptor format sense data. For these drives to work
properly under Windows, the miniport needs to convert the descriptor format sense
data to fixed format before returning the sense data up the stack.

Fixes:
- Add check for sense data type (fixed vs. descriptor) in CheckSmartInfo where large
physical drives 2TB in size and greater use the descriptor format for sense data in
order to pass back 64-bit LBA addresses. Most drives use the fixed format sense data,
is the only format the upper layers of the Windows stack supports

Version 2.00.17.30 - Initial release
------------------
ibm_dd_mpt2sas_2_00_75_00_windows_32-64_chg

Matrox G200eR (Renesas) Display Only Driver for Windows Server 2012 R2


Rev. 4.01.01.005
- Compiled using Visual Studio 2012 RC.
- Using the Release Preview SDK/WDK Build 8400.


KNOWN ISSUES
------------
- None


HISTORY
-------
Rev. 4.00.01.003
- Beta version
mtrox_dd_video_4_01_01_005_winsrvr_64_chg

Fibre Channel Adapter STOR Miniport Driver for Windows
Release Notes
August 24, 2014

QLogic Driver Release Notes

QLogic Corporation
All rights reserved
Package Version 9.1.11.28
Driver Version 9.1.11.28

Table of Contents

1. Change History
2. Known Issues
3. Notices
4. Contacting Support


1. Change History


The following changes have been made to the Fibre Channel Adapter
STOR miniport driver version 9.1.11.28.


Version 9.1.11.28

* [ER111983]: Unable to do backups at 256K block transfer size limit
Scope : 2500 and 2600 Series Adapters
Resolution: Fixed number of physical break with corresponding maximum transfer length
* [ER132635]: Certain tape device reboot causes I/O quiescence
Scope : 2500 and 2600 Series Adapters
Resolution: Fixed timing issue in device re-login after logout
* Firmware version: 7.03.00 (2400/2500 Series 4Gb and 8Gb Fibre Channel Adapters)
* API version 1.28.0.115 (QLSDM)


****************************************************************************************
Version 9.1.11.26

* API version 1.28.0.112 (QLSDM)
* [ER115248]: Read NVRAM fails after write
Resolution: Added delay between write and read in api
Scope : 8200 Series Adapters
* [ER115315]: Unable to update EDC
Resolution: Fixed wrong lengh in built-in FLT
Scope : 2500 Series Adapters
* [ER114713]: Poor read write performance at certain large block sizes
Resolution: Fixed delay in handling SRB queue
Scope : 2600 Series Adapters
* Firmware version: 7.01.00 (2400/2500 Series 4Gb and 8Gb Fibre Channel Adapters)
* [ER114741]: Login to tape device times out
Scope : All FC and FCOE Adapter
Resolution: Retry Relogin once
* [ER113510]: Maximum number of GNNFT entries is limited to 128
Scope : All Adapters
Resolution: Increased maximum number of GNNFT entries
* [ER113482]: Failover on EMC storage not working when zoning is deactivated on switch
Resolution: Fixed for not relogin after timeout
* [ER112112]: SnapDrive cannot see luns through the QLE10K
Scope : 10000 series adapter
Resolution: Change the number of ports in AdapterAttributes to 1
* [ER112725]: Issue with processing certain response entry during stop HBA operation
Resolution: Added check for HBA stop state before response queue processing
* [ER112726]: Multi-queue debug trace feature
Scope : 2500 and 2600 Series Adapters
Resolution: Added per-queue debug information trace
* Added support for the following devices (supported platforms):
- PCI\VEN_1077&DEV_2532&SUBSYS_02841077 (x86, x64)


****************************************************************************************
Version 9.1.11.24

* Firmware version: 5.09.00 (2400/2500 Series 4Gb and 8Gb Fibre Channel Adapters)
* API version 1.28.0.105 (QLSDM)
* Fix MailboxPassthru by removing restriction on writing mbx8 register [ER104361]
* Added support for Skip 4G FC [ER104575]
* Allow application modify "Execution Throttle" field in nvram for 2600 series adapters [ER103297]
* Add Service Pack number to OSName [ER104204]
* Added api to read 2600 series adapters ASIC temperature [ER102430]
* Added mailbox passthru api [ER102988]
* Added reading ASIC temperature for Ninja and Sensei [ER103001]
* Removed Advanced tab from Device Manager properties
* Added support support for full 64 bit physical addressing [ER101742]
* Added support for QLE10000 series adapters


****************************************************************************************
Version 9.1.10.28

* Firmware version: 5.07.02 (2400/2500 Series 4Gb and 8Gb Fibre Channel Adapters)
* API version 1.28.0.101 (QLSDM)
* Removed support for 2Gb speed in port supported speed for 16Gb FC in 2600 series adapters [ER100053]
* Added get/set I2V registers and get/set serdes registers - OEM Adapter [ER99727]
* Added support to address OEM adapter Re-design I2C access issue [ER99562]
* Added adapter disable state check on timer routine re-init state handling [ER96662]
* External loopback support OEM adapter when in loop mode [ER98834]
* Fixed skipping OEM adapter vpd update [ER100458]
* Fixed Ext Loopback test fails with Loopback connector (8Gb loop mode) [ER99702]
* Fixed crash in fwdump routine [ER101039]
* Limit support to node-interleaving configurations


****************************************************************************************
Version 9.1.10.27

* Fixed event Viewer Error 154 (Disk I/O error) occurs when running
Diskercise on FC LUN [ER97809]


****************************************************************************************
Version 9.1.10.26
* API version 1.28.0.97 (QLSDM)
* Added series adapters temperature handling [ER94159]
* Removed driver family version support [ER95755]
* Removed flash FLT error logging for 24xx/25xx [ER96144]
* Returned NOT_SUPPORTED for SDForceFcMctpDump in api [ER96352]
* Fixed memory access error [part of ER96188]
* Fixed extra 4K in variable transfer sizes (64K, 128K) [ER94081]
* Added support to relogin if the device logs out [ER93867]
* Removed event logging for fw dump event [ER98897]


****************************************************************************************
Version 9.1.10.25

* Added Windows Server 2012 support [ER92249]
* Not to update i2c vpd if Sensei in api [ER93800]
* Fixed Flash Layout Table memory usage [ER93668]
* API version 1.28.0.96 (QLSDM)
* Code cleanup [ER92250]
* Added support for Set Driver version for OCBB and family
driver version [ER92243]
* Issue with LB connector attached after it was in point-to-point mode,
driver was still issuing echo instead of loopback command [ER93050]
* Fixed Adapter Port type in P2P mode [ER92357]
* Process completed PRLI [ER89053]
* Fixed multiple request single response queue initialization issue [ER95259]


****************************************************************************************
Version 9.1.9.48

* Firmware version: 5.06.05 (2400/2500 Series 4Gb and 8Gb Fibre Channel Adapters)


****************************************************************************************
Version 9.1.9.47

* Firmware version: 5.06.04 (2400/2500 Series 4Gb and 8Gb Fibre Channel Adapters)


****************************************************************************************
Version 9.1.9.46

* Firmware version: 5.06.03 (2400/2500 Series 4Gb and 8Gb Fibre Channel Adapters)
* API version 1.28.0.92 (QLSDM)
* LUN disappearance after tape reboot [ER84117]
* Failed to reissue some i/o's after controller failover (8Gb)
[ER86660]


****************************************************************************************
Version 9.1.9.29

* Firmware version: 5.06.02 (2400/2500 Series 4Gb and 8Gb Fibre Channel Adapters)

****************************************************************************************
Version 9.1.9.28

* Firmware version: 5.05.05 (2400/2500 Series 4Gb and 8Gb Fibre Channel Adapters)
* API version 1.28.0.87 (QLSDM)


****************************************************************************************
Version 9.1.9.27

* Updated firmware version: 5.04.04 (2400/2500 Series 4Gb and 8Gb Fibre Channel Adapters)
* API version 1.28.0.85 (QLSDM)
* Fixed an issue where drives were not detected in direct connect
topology [ER81138]


****************************************************************************************
Version 9.1.9.25

* No fixes in this driver release.

Version 9.1.8.25

* Closed WMI mapping interoperability with HBAAPI.DLL issue.

Version 9.1.8.19

* Driver restores 4G Fibre Channel PCIe Device Control and Link
Control registers based on saved value.
* In multi-processor systems, the clustering driver timer
popped as a result of unrecovered I/O through a LUN reset.
[ER0000000067688 closed]

Version 9.1.8.17

* Firmware versions: 5.01.02 (4Gb and 8Gb)
* API version 1.28.0.73 (QLSDM)
* Driver restores 4G Fibre Channel PCIe Device Control and Link
Control registers based on saved value.

Version 9.1.7.18

* Firmware versions: 3.03.25 (2Gb), 4.04.00 (4Gb and 8Gb).
* API version 1.28.0.63 (QLSDM).

Version 9.1.7.17

* Added support for the following devices (supported platforms)
(2.3m):
- PCI\VEN_1077&DEV_8432&SUBSYS_010E1077 (x86, x64)
- PCI\VEN_1077&DEV_2432&SUBSYS_014B1077 (x86, x64)
- PCI\VEN_1077&DEV_2532&SUBSYS_01701077 (x86, ia64, x64)
- PCI\VEN_1077&DEV_2532&SUBSYS_01711077 (x86, ia64, x64)
- PCI\VEN_1077&DEV_2532&SUBSYS_01721077 (x86, ia64, x64)
- PCI\VEN_1077&DEV_2532&SUBSYS_01731077 (x86, ia64, x64)
- PCI\VEN_1077&DEV_2532&SUBSYS_01741077 (x86, ia64, x64)
- PCI\VEN_1077&DEV_2532&SUBSYS_01751077 (x86, ia64, x64)
- PCI\VEN_1077&DEV_2432&SUBSYS_004A1137 (x86, ia64, x64)
* Removed support for the following devices (supported platforms):
- PCI\VEN_1077&DEV_2432&SUBSYS_011C1077 (x86, x64)
NOTE: Microsoft requires x86 and x64 support for all Fibre Channel
Adapters.
* Firmware versions: 3.03.25 (2Gb), 4.03.02 (4Gb).
* API version 1.28.0.63 (QLSDM).
* Added support for 64-bit QLSDM DLLs.
* Enabled FDMI by default.
* Added support for Atmel flash AT26DF081A.
* Removed support for obsolete qd parameter.
* Changed the driver to not log events caused by I/O completion
errors.

Version 9.1.7.16 QL

* Added support for the Windows Server 2008 operating system.
* Applied a fix to handle logout in the loop environment.

Version 9.1.7.15 QL

* Added support for the following devices (supported platforms):
- PCI\VEN_1077&DEV_2432&SUBSYS_01081077 (x86, IA64, x64)
- PCI\VEN_1077&DEV_2532&SUBSYS_015C1077 (x86, IA64, x64)
- PCI\VEN_1077&DEV_2532&SUBSYS_015D1077 (x86, IA64, x64)
- PCI\VEN_1077&DEV_2532&SUBSYS_015E1077 (x86, IA64, x64)
- PCI\VEN_1077&DEV_2532&SUBSYS_015F1077 (x86, IA64, x64)
- PCI\VEN_1077&DEV_2532&SUBSYS_01601077 (x86, IA64, x64)
- PCI\VEN_1077&DEV_2532&SUBSYS_01611077 (x86, IA64, x64)
- PCI\VEN_1077&DEV_2532&SUBSYS_01621077 (x86, IA64, x64)
- PCI\VEN_1077&DEV_2532&SUBSYS_01631077 (x86, IA64, x64)
- PCI\VEN_1077&DEV_2532&SUBSYS_01641077 (x86, IA64, x64)
- PCI\VEN_1077&DEV_2532&SUBSYS_3261103C (x86, IA64, x64)
- PCI\VEN_1077&DEV_2532&SUBSYS_3262103C (x86, IA64, x64)
- PCI\VEN_1077&DEV_2532&SUBSYS_3263103C (x86, IA64, x64)
- PCI\VEN_1077&DEV_2532&SUBSYS_3264103C (x86, IA64, x64)
NOTE: Microsoft requires x86 and x64 support for all Fibre Channel
Adapters.
* Firmware versions: 3.03.25 (2Gb), 4.02.00 (4Gb).
* API version: 1.28.0.50 (QLSDM).
* Unique assignment of management server N_Port handle values to be
for each virtual port.
* NPIV (N_Port ID virtualization).
* Target link speed (iiDMA).
* PcieLinkCap/Stat to HbaDeviceChipProperty.
* Flash layout regions for 4Gb and returned flash layout table from
flash if it is valid.
* Three Alternate Boot Devices and OOFR (out-of-order
frame receive).
* Removed QL2XHAI2: IHVs are required to use Host Bus Adapter API
provided by Microsoft.
* Preserved BIOS defaults when updating multi-boot image whose BIOS
locations can be anywhere in the image.
* Fixed checksum calculation in QLSDM when two-bios image
is flashed.
* Initiator discovery problem caused a large burst of
RSCN activity when the NetApp does its failover. A failed GPNID
command occurring during ports discovery must not cause the
termination of the discovery process.
[ER50975 fixed]
* Handled the case where the GNNFT command was failing due to
incorrectly calculated the maximum data response length.
* Setting the alternate WWN and enabling it in the NVRAM did not
propagate through to the Host Bus Adapter. Reading the NVRAM and
reinitializing the Host Bus Adapter will handle this case.

Version 9.1.4.16 QL 3.03.21 4.00.26

* Adhered to Subsystem Id document v2.2m+.
* Firmware versions: 3.03.21 (2Gb), 4.00.26 (4Gb).
* API versions: 1.28.0.37 (QLSDM), 2.0.0.14 (QL2XHAI2).
* Initiator discovery problem caused a large burst of
RSCN activity when the NetApp does its failover. A failed GPNID
command occurring during ports discovery must not cause the
termination of the discovery process. [ER50975]

Version 9.1.4.15 QL 3.03.21 4.00.26

* Firmware versions: 3.03.21 (2Gb), 4.00.26 (4Gb).
* API versions: 1.28.0.37 (QLSDM), 2.0.0.14 (QL2XHAI2).
* Adhered to Subsystem Id document v2.2m+.
NOTE: Microsoft requires both x86 and x64 support all Host Bus
Adapters.
* Added support for the following devices (supported platforms):
- PCI\VEN_1077&DEV_2322&SUBSYS_01151077 (x86, IA64, x64)
- PCI\VEN_1077&DEV_2322&SUBSYS_01161077 (x86, IA64, x64)
- PCI\VEN_1077&DEV_2422&SUBSYS_1336103C (x86, IA64, x64)
- PCI\VEN_1077&DEV_2432&SUBSYS_015B1077 (x86, IA64, x64)
- PCI\VEN_1077&DEV_5432&SUBSYS_01551077 (x86, x64)
- PCI\VEN_1077&DEV_5432&SUBSYS_01561077 (x86, x64)
- PCI\VEN_1077&DEV_2422&SUBSYS_014A1077 (IA64)
- PCI\VEN_1077&DEV_2432&SUBSYS_014B1077 (IA64)
* Removed support for the following devices:
- PCI\VEN_1077&DEV_6312&SUBSYS_01301077 (x86, x64)
- PCI\VEN_1077&DEV_2422&SUBSYS_01471077 (IA64)
- PCI\VEN_1077&DEV_2432&SUBSYS_01451077 (IA64)
* Conformed QLSDM and the driver to the revised for "Get/Set Target
Link Speed".
* Increased loopback test buffer size to 2048 bytes in QLSDM.
* Loopback test always failed when the NVRAM frame
size is set to 512 or 1024 (Windows). Pass in transfer size
instead of hard-coded value in QLSDM. [ER50975 fixed]
* Handled the case where the device becomes not ready in the
StartIO routine.
* Fixed in SANsurfer 5.0.0 Build 4 – Driver 9.1.3.10b2—Windows
IA64 SP1—HP. The Host Bus Adapter model numbers do not show up on
Information page. [ER48374]
* Fixed Long Erase (0x019) issues with DLT S4 and QLE2462.
Error occurs (most likely a bus reset) when running a long erase
that takes longer than 110 minutes on the Quantum DLT-S4
(firmware:0808) drive, which exceeds the built in 4Gb firmware
timeout limit. [ER48117 (AR 48907, SR70415 [REF:609618455])]

Version 9.1.3.16 QL 3.03.21 4.00.23

* This version replaced the invalid release 9.1.3.15.
* Firmware versions: 3.03.21 (2Gb), 4.00.23 (4Gb).
* API versions: 1.28.0.35 (QLSDM), 2.0.0.14 (QL2XHAI2).
* Removed I/O Reduction support for the 4G Host Bus Adapter.

Version 9.1.3.15 QL 3.03.21 4.00.23

* Firmware versions: 3.03.21 (2Gb), 4.00.23 (4Gb).
* API versions: 1.28.0.35 (QLSDM), 2.0.0.14 (QL2XHAI2).
* Added OEM specific support for assigning a virtual world wide port
name via registry key.
* Added "Get/Set" target link speed support.
* Changed the INF to enable the I/O Reduction for the 4Gb Host Bus
Adapter for the IA64 platform based on Microsoft document.
* Added multiple BIOS support in QLSDM.
* Initialized debug file name variable during DLL load (QL2XHAI2).
* Closed EMC OPT23605: x64 Server hangs during boot at the “Applying
Computer Settings.”
* Cleaned up code related to get Object text for OS Device Name
(QL2XHAI2).
* Attached target devices not visible to OS after server reboot
(QLE220) [ER47338 closed].
* Driver not Login into Target Devices (QLE220) [ER47436 closed]
* Topology diagram is not displaying properly when LIP issued on
QLA2462 port. [ER47530 closed]

Version 9.1.2.19 QL 3.03.19 4.00.23

* Firmware versions: 3.03.19 (2Gb), 4.00.23 (4Gb).
* Bus Resets Under Heavy I/O Load. [ER46891 closed]
* API Versions: 1.28.0.33 (QLSDM), 2.0.0.12 (QL2XHAI2).
* SANsurfer FC HBA Manager B83 showed only one port see the storage
even though no zoning. [ER47166 closed]
* Port failure after disconnecting and reconnecting ISL port
used by MirrorView. [Closed OPT 235681]
* SANsurfer FC HBA Manager does not display the topology view
correctly when the Host Bus Adapters are set to loop only until
the system is rebooted. [ER47235 closed]

Version 9.1.2.18 QL 3.03.19 4.00.22

* Firmware versions: 3.03.19 (2Gb), 4.00.22 (4Gb).
* API Versions: 1.28.0.33 (QLSDM), 2.0.0.12 (QL2XHAI2).
* Added VPD update support for 2432 4-port adapter in 1.28.0.33
(QLSDM).
* Recognized Asynchronous Event 8048h as a valid AEN.
* Modified timer task to handle the case when Host Bus Adapter
is in a stopped state.
* 24xx only: Added support for NVRAM Nodename option bit.
* 4Gb only: Added support for reading data from SFP (small
form-factor pluggable) optical transceivers via QLSDM.
* Adhered to Subsystem Id document v2.2g.
* Added support for the following devices (supported platforms):
- PCI\VEN_1077&DEV_2422&SUBSYS_014D1077 (x86, IA64, x64)
- PCI\VEN_1077&DEV_2432&SUBSYS_014C1077 (x86, IA64, x64)
- PCI\VEN_1077&DEV_2432&SUBSYS_01521077 (x86, IA64, x64)
- PCI\VEN_1077&DEV_2432&SUBSYS_01531077 (x86, IA64, x64)
- PCI\VEN_1077&DEV_2432&SUBSYS_01541077 (x86, IA64, x64)
- PCI\VEN_1077&DEV_5432&SUBSYS_014E1077 (x86, x64)
* Adhered to firmware dump procedure per 2400 Series Firmware
Interface Specification version C.
* RX2600 fails to boot Windows after 1MB bin flash—SANsurfer
2.0.30b84_windows. [ER47113 closed]
* Fixed: LUNs disappeared after DS4000 controller firmware download
in direct attach.
* "Bind By Port ID + Present Targets that are persistently bound
only" is not working (in loop environment). [ER46586 closed]
* Changed to perform the full firmware dump when firmware error
occurs.
* JBOD disks turn offline in SANsurfer FC HBA Manager and SANsurfer
FC HBA CLI when settings are Present targets that are
persistently bound + Bind by Port ID (in loop environment).
[ER46141 closed]
* Corrected firmware region size in option ROM layout, that is,
firmware size in flash.
* GPN_ID has wrong payload length after unplug and re-plug.
[ER45035 closed]
* When using the QLSDM to retrieve the transceiver data, you may get
SDMGT_CANNOT_GET_SFP_DATA error on system platforms using specific
models of Supermicro motherboard such as P3TDL3 and P3TDLE. The
QLSDM retrieves the transceiver data using underlying 4Gb firmware
(v4.00.21) that reports an error code of 4005 for this operation.
* Verified support for Atmel flash chip AT26DF081A.

Version 9.1.2.16 QL 3.03.19 4.00.18

* Firmware versions: 3.03.19 (2Gb), 4.00.18 (4Gb).
* Adhered to Subsystem Id document v2.2f.
* Added support for the following devices (supported platforms):
- PCI\VEN_1077&DEV_6312&SUBSYS_01191077 (x86, x64)
- PCI\VEN_1077&DEV_6312&SUBSYS_011C1077 (x86, x64)
- PCI\VEN_1077&DEV_6312&SUBSYS_01301077 (x86, x64)
- PCI\VEN_1077&DEV_6322&SUBSYS_012F1077 (x86, x64)
* Set additional firmware option bit 10 for 2Gb Host Bus Adapter so
the firmware waits for the task management command, (such as reset
LUN to complete.)
* Host Bus Adapter does not re-login to target after target sends
LOGO to Host Bus Adapter. [Closed OPT226506]
* The link status behaves differently between QLE2460 and QLA2342.
[ER44735 closed]
* Incorrect HwVersion string is reported by QLogic
IHV HBA_GetAdapterAttributes call. [ER45228 closed]
* Event Id 11 entries logged by ql2300 at offset x10
and offset x34 do not match the Error Codes published on the Web.
Because the miniport uses Microsoft's Storport.sys driver to
actually log the error event, and it has been confirmed that the
storport.sys driver logs the event incorrectly. A bug has been
reported to Microsoft on this: SRX041110604850 (STORport—Incorrect
event data is logged when storport's storportlogerror). Meanwhile,
the Miniport driver is changed to log the event code at offset x10
by default. This workaround is controlled by the registry
parameter mevtwrkaround. For details on this parameter, please
see the readme file. [ER45230 closed]
* Use memory map mechanism in the driver. [ER45232 closed]

Version 9.1.2.15 QL 3.03.19 4.00.17

* Firmware versions: 3.03.19 (2Gb), 4.00.17 (4Gb).
* Adhered to Subsystem Id document v2.2e.
* Added support for the following devices (supported platforms):
- PCI\VEN_1077&DEV_5432&SUBSYS_013E1077 (x86, IA64, x64)
- PCI\VEN_1077&DEV_5432&SUBSYS_013F1077 (x86, IA64, x64)
- PCI\VEN_1077&DEV_2422&SUBSYS_014A1077 (x86, IA64, x64)
- PCI\VEN_1077&DEV_2432&SUBSYS_014B1077 (x86, IA64, x64)
* Added support to use combined 2Gb IPX firmware.
* Added support for SST25VF080B flash part.
* Added option for not to dump code section for 24xx firmware dump.
* Serial number for the 4Gb Host Bus Adapter should
be obtained from the VPD. [ER44270 closed]
* Windows 2000/qla2340/Veritas tape backup long cable pull failed
error message ERROR_DEVICE_NOT_CONNECTED. [ER38787 closed]

Version 9.1.1.15 QL 3.03.18 4.00.12

* Firmware versions: 3.03.18 (2Gb), 4.00.12 (4Gb).
* QLogic 4Gb driver returns selection timeout
immediately after cable pull in an OEM special dual loop
configuration. [Closed PTR 90818]
* QLogic Driver returns a selection timeout when
rebooting a controller in an OEM special dual loop configuration.
[Closed PTR 90652]

Version 9.1.0.18 QL 3.03.18 4.00.12

* Firmware versions: 3.03.18 (2Gb), 4.00.12 (4Gb).
* Adhered to Subsystem Id document v2.2d.
* Added support for the following devices (supported platforms):
- PCI\VEN_1077&DEV_2422&SUBSYS_12D7103C (x86, IA64, x64)
- PCI\VEN_1077&DEV_2312&SUBSYS_01491077 (x86, IA64, x64)

Version 9.1.0.17 QL 3.03.18 4.00.12

* Firmware versions: 3.03.18 (2Gb), 4.00.12 (4Gb).

Version 9.1.0.16 QL 3.03.16 4.00.12

* Firmware versions: 3.03.16 (2Gb), 4.00.12 (4Gb).
* Embedded 24xx firmware in the driver.
* New driver could not detect any device to install as BOOT from
SAN on one specific setup. [ER43175 closed]

Version 9.1.0.15 QL 3.03.16

* Firmware versions: 3.03.16 (2Gb), (Use onboard 4Gb firmware.)
* Added 24xx support.
* Need to change bit used to control LED mode. [ER42601 closed]

Version 9.0.2.17 QL 3.03.13

* Firmware versions: 3.03.16 (2Gb).

Firmware (Embedded in Driver)
-----------------------------

The following lists show the changes and bug fixes to the firmware
that is embedded in the drivers for the 4Gb Fibre Channel Adapters
and 8Gb Fibre Channel Adapters from versions 4.03.01 to 5.04.04.

From Version 5.04.02 to 5.04.04

Changes
-------
* 2500 Series. Ensured that correct slot-specific SerDes settings
will be used for specific mezzanine cards. [ER78047]

Bug Fixes
---------
None

From Version 5.04.01 to 5.04.02

Changes
-------
* Current Fibre Channel Adapter firmware supports maximum frame
sizes of 512, 1024, and 2048 in the received PLOGI or PLOGI-ACC.
This change provides an option to disable this restriction by
setting bit 6 of Firmware Options 2 through Set Additional
Firmware Options Mailbox Command (038h). Note that this option
bypasses the Maximum Transmit Data Frame Size set by the Set
Transmit Parameters Mailbox Command (019h). [ER76448]

Bug Fixes
---------
None

From Version 5.04.00 to 5.04.01

Changes
-------
* Option to Disable Automatic FDISC:
Currently, the firmware automatically performs FDISC for enabled
virtual ports (VPs) upon receiving an FLOGI_ACC. This procedure
does not mesh well with driver architectures, which typically
control the FDISCs.
A new option bit allows you to suppress the automatic FDISCs. This
option bit is available in both the ISP25xx and ISP81xx firmware.
Older firmware ignores this option bit.
Functional Description:
The Disable FDISC bit (multi-ID initialize firmware control block,
Global VP Options field, bit 4) disables the automatic FDISCs.
If this bit is set, any VPs enabled in the multi-ID initialize
firmware control block remain enabled, but the ID is not in the
acquired state. The driver must issue a Modify Virtual Port
Configuration IOCB (with the Command field set to 3h) to instruct
the firmware to transmit the FDISC after it receives the report
ID acquisition (RIDA) for VP0.
When Disable FDISC is set, no FDISC is transmitted for the enabled
VPs on any event, which results in a FLOGI. The driver should
issue a Modify Virtual Port Configuration IOCB (with the Command
field set to 3h) to instruct the firmware to transmit the FDISC
for a specific VP (after receiving the RIDA for VP0). The driver
must instruct the firmware to transmit an FDISC for all enabled
VPs. After all the FDISC is completed, the firmware state changes
to ready. In addition, a Port Database Changed AEN (8014h), with
the Outgoing Mailbox 1 register set to FFFFh and Outgoing
Mailbox 2 register set to 6h, is generated and passed to the
driver. If the driver does not transmit FDISC for a VP, the
driver must disable that specific VP using Virtual Port Control
IOCB (Entry Type field 30h). This step is needed because a VP
is enabled, but the ID is not in the acquired state, which can
prevent the firmware state from changing to ready, and prevent
generation of the Port Database AEN as previously stated.
The option applies only to fabric point-to-point topology and
NPIV environments. [ER74448]

* Added option to disable PRLI REC_SUPPORT bit. To disable the PRLI
REC_SUPPORT bit (PRLI REC_SUPPORT bit is set by default), set
bit 6 of the additional firmware option 3 of the Set Additional
Firmware Options (38h) Mailbox Commands). This option has to be
set prior to Initialize Firmware mailbox command (60h or 48h).
[ER74764]

Bug Fixes
---------
* Customer-specific fix. [ER74764]

* 24xx/25xx MID. Fixes potential drops of PRLI request or firmware
incorrectly assigning multiple N_Port Handles for same Port_id.
[ER73958]

From Version 5.03.00 to 5.04.00

Changes
-------
* Customer-specific changes.[ER69516, ER70666, ER71711, ER71936,
ER69589, ER70279, ER69620, ER71031, ER72037, ER73006]

* 81xx only. Added Additional Firmware Options 2, bit 9 to improve
NIC bandwidth when NIC and FCoE receive traffic are running
concurrently. [ER69565]

* 81xx/25xx MIDQ only. Provide capability in Queue Management (1Fh)
mailbox command to move a queue base address. For details, refer
to the Multiple Queue Support for 2500 Series Fibre Channel and
8100 Series Converged Network Adapter Controllers Applications
Note. [ER69606]

* 81xx only. Added support for LR Optics. Requires MPI FW 1.39.00
or later with proper configuration files. [ER69613]

* Added an Additional Firmware Options 3 bit to discard any frames
received out of order unless the Initialize Firmware Options 3
bit 6 (Enable Receive Out-of-Order Data Frame Handling) is set
to 1. Changes to Set Additional Firmware Options (38h) Mailbox
Command interface:
- Add to Additional Firmware Option 3 Bits (Incoming mailbox 3
register) Table: Bit 15 Do not transfer received out of
order data for an exchange to host memory (except during
SRR recovery).
- Replace bit_15 description with:
Bit 15 (Do not transfer received out of order data for an
exchange to host memory). When this bit is set to 1, the ISP
firmware does not transfer received out-of-order data for an
exchange to host memory, except during SRR recovery. A frame
is considered "out-of-order" after a previously-received frame
is dropped due to an error, as well as a true out-of-order
frame receipt condition.
NOTE: Bit 15 is ignored when Initialize Firmware Options 3 bit 6
(Enable Receive Out-of-Order Data Frame Handling) is set
to 1.
[ER70311]

* 24xx/25xx only. Bit 8 of State Flags field in Status IOCB Type has
been changed from Reserved to "Unable to send OPN to Destination."
This bit is set when the destination device sends an immediate
CLS in response to an OPN from ISP. [ER71132]

* Add option to disable the firmware automatic port login (PLOGI)
to the simple name server (SNS). To enable this feature, set
Bit 15 of Additional Firmware Options 2 when issuing Set
Additional Firmware Options Mailbox Command 0038h. [ER71742]

* 24xx SB2 only. Return the lower 16-bit of current RBC count in
Receive IU and Add Buffer IOCBs. This extends the scope of
ER68875 to include 24xx.
- For IOCB type 0x4D, the lower 16-bit of the counter is stored
at offset 0x3E to 0x3F.
- For IOCB type 0x4C, the lower 16-bit is stored at offset 0x1C
to 0x1D.
[ER71764]

* 81xx only. Added an Additional Firmware Options 2 bit to post all
Asynchronous IOCBs to the ATIO queue when target mode is enabled.
Changes to Set Additional Firmware Options (38h) mailbox command
interface:
- Add to Additional Firmware Option 2 Bits (Incoming mailbox 2
register) Table:
Bit 11 Enable Asynchronous IOCBs to ATIO queue.
- Replace bit 11 description with:
Bit 11 (Enable Asynchronous IOCBs to ATIO queue). When this
bit is set to 1, the firmware posts all asynchronous IOCBs
(PUREX, ABTS Received, and Report ID Acquisition) to the ATIO
queue when target operation is enabled. Additionally, if a
login-affecting ELS command (PLOGI, PRLI, PRLO, LOGO, ADISC,
PDISC, or TPRLO) is passed up to the target driver, an
Immediate Notify IOCB with Status Code 46h, Login affecting
ELS command received, shall not be sent. Initialize Firmware
Options 3 bit 26 (Enable Ethernet Header Receive IOCB for ATIO
Queue) is used to request the firmware place an Ethernet Header
Receive IOCB on the ATIO queue before each PUREX and ABTS
Received IOCB. Initialize Firmware Options 3 bit 27
(Enable Ethernet Header Receive IOCB for Response Queue) shall
be ignored. When bit 11 is set to 0, the firmware posts
asynchronous IOCBs to queues specified in the ISP81xx firmware
specification.
Changes to Initialize Firmware, Firmware Options 3:
- Bit 27 (Enable Ethernet Header Receive IOCB for Response Queue).
When Additional Firmware Option 2 bit 11 (Enable Asynchronous
IOCBs to ATIO queue) is set, this bit is ignored.
- Bit 26 (Enable Ethernet Header Receive IOCB for ATIO Queue).
When Additional Firmware Option 2 bit 11 (Enable Asynchronous
IOCBs to ATIO queue) is set, and this bit is set, the firmware
places an Ethernet Header Receive IOCB on the ATIO queue before
each PUREX and ABTS Received IOCB.
[ER71877]

* MID only. Send LOGO if an FDISC is rejected with error/explanation
code 03/0D. After LOGO ACC is received, the firmware retries the
FDISC. [ER72460]

Bug Fixes
---------
* 81xx only. Corrected FCP-2 processing during a link disruption
until re-discovery is complete. [ER66337]

* MIDQ builds. Corrected N_Port-N_Port FLOGI Dest ID of 0.
[ER67952]

* 2532-based adapter only. Corrected an issue that could prevent
the link from being established when connected to specific targets
operating at 8Gb link speed in a loop topology. [ER68658]

* Correct abort handling of a Command Type 6 IO that could result
in fatal firmware error or I/O timeout. [ER68965]

* 81xx only. Set a Buffer Credit value of 16 in FLOGI/FDISC for
interoperability with FCFs that incorrectly use the field.
[ER69182]

* 81xx only. Correct handling of received stale frames forwarded
by an FCF after the link is re-established. [ER69245]

* 81xx only. Corrected an issue that would prevent the link from
being re-established after a cable pull. [ER69291]

* Correctly set the "sequence initiative transferred bit" (F_CTL)
for transmission of status mode 2 FCP_RSP with confirmation
request. [ER69336]

* 81xx only. Added support to detect MPI pause during heartbeat
processing. [ER69457]

* Disk CRC only. Correct firmware reported residual Byte Count for
CRC (T10) Read commands. [ER69564]

* 81xx only. Corrected CTIO handling when the link was down.
[ER69683]

* 81xx only. Corrected an issue with Internal Loopback failure
reported when link is up to an FCF. [ER69685]

* 24xx CRC only. Resolve 8002 system error during DIF error
processing. [ER69922]

* 25xx and 81xx only. Corrected possible memory leak during
clean-up of T10 CRC IOs with DIF Bundling enabled. [ER70018]

* 25xx and 81xx only. Corrected false DIF error reported during
T10 CRC transmit IO with DIF Bundling. [ER70038]

* Corrected Target XCB count returned by Get Resource Counts
Mailbox Command (0042h). [ER70149]

* Corrected a RISC pause condition after the Diagnostic Echo
Test (44h) mailbox command completed with an error status.
[ER70166]

* 25xx and 81xx only. Corrected a potential I/O timeout of T10 CRC
IO when using DIF bundling. [ER70319]

* 25xx and 81xx only. Corrected potential invalid PCIe access when
aborting a T10 CRC IO when using DIF bundling. [ER70558]

* Corrected N_Port Handle assignment by firmware when Purex is
enabled. [ER70575]

* 81xx only. The firmware could incorrectly set bit 15 of N_Port
Handle returned by the Get Port/Node Name List (75h) mailbox
command. [ER70664]

* 81xx only. Corrected a problem where the values supplied in the
Set Timeout Parameters (32h) mailbox command were not honored.
[ER70708]

* Prevent 8002 system error when processing a severely malformed
IOCB. [ER70910]

* Corrected a RISC pause condition during SRR received notify ACK
processing. [ER70921]

* Customer-specific issues. [ER70970, ER71426, ER72657, ER71475]

* 24xx only: Improved link init time when using Inline Credit
Extender in an N_Port-N_Port configuration. [ER71034]

* Fixed Loopback mailbox command timeout when Fibre Channel event
(FCE) extended tracing is enabled. [ER71269]

* Corrected a problem that could result in a Task Management
command timeout. [ER72100]

* Corrected handling of frames received with DID = 000000h.
[ER72270]

* 81xx only. Fix CTIO with terminate exchange bit returned good
completion status (01h) after the CTIO is already completed.
The CTIO with a terminate exchange bit should instead return an
invalid receive exchange address (08h) completion status.
[ER72491]

* MID builds only. Fix CTIO with terminate exchange bit failed with
completion status=29h. [ER72571]

* 81xx only. Corrected a problem that caused FDISC not generated by
the firmware when Virtual Port Control IOCB (type=30h) is used to
enable VP. [ER72921]

* MID only. Correct the cleanup of outstanding ELS requests during
VP disable. [ER73048]

* MID only. Resolve RISC pause after cable pull or link event.
[ER73090]

From Version 5.02.00 to 5.03.00

Changes
-------
* Added feature to return LOGIN info via Mailbox Command 5Ah - Get
Params, using type 7.
Entry Parameters (Incoming):
Mailbox0 - opcode (005ah)
Mailbox1 - Type<15:8>, reserved<7:0>
Mailbox2 - buffer addr<31:16>
Mailbox3 - buffer addr<15:0>
Mailbox6 - buffer addr<63:48>
Mailbox7 - buffer addr<47:32>
Mailbox8 - DW Xfr Length (only valid for Type 7)
Exit Parameters (Outgoing):
Mailbox0 - (4000h) normal completion
- (4002h) DMA error
- (4005h) error during command execution
- (4006h) if unsupported type or DW Xfr requested
is too small ( 28DW <.. ) data got truncated
Mailbox1 - If Outgoing Mailbox 0 is 4005h, then Outgoing
Mailbox 1 will have the following sub-code:
0002h - No IOCB
Mailbox8 - DW Xfr Data (should be 28 for typical PLOGI, only
valid for Type 7)

The format returned is according to FC-LS-2 (Fibre Channel - Link
Services - 2), rev.2.00 - FLOGI/PLOGI payload minus ELS
command code. [ER66811]

* 8100 only. Added support for MPI heartbeat feature. Contact QLogic
for details. [ER67656]

* 8100 only. Changes to support additional MPI mailbox commands in
the range 136h to 150h. [ER67716]

* 2532/8100 CRC. Implemented CTIO Type CRC_2 and support DIF
bundling on CTIO CRC IOCBs.[ER67727]

* 2532 SB2 only. Return the lower 16-bit of current RBC count in
Receive IU and Add Buffer IOCBs.
- For IOCB type 0x4D, the lower 16-bit of the counter is stored at
offset 0x3E to 0x3F.
- For IOCB type 0x4C, the lower 16-bit is stored at offset 0x1C to
0x1D.
NOTE: This feature will be documented in the upcoming SB-4 spec.
[ER68875]

Bug Fixes
---------
* MID only. Do not report RSCN for VPs that have been disabled.
Previously, the firmware generated 8015 AEN with an invalid
vpindex. [ER62856]

* 2532/8100 CRC T10. Resolved bad FCP_DATA sequence due to incorrect
re-initialization of the CRC context for Header mode. This
affected T10 write commands with multiple FCP_XFER_RDYs. [ER67220]

* Removed zeroed optional association headers from RRQ payload.
[ER67210]

* 24xx/2532 only. Corrected a problem in PLOGI ACC processing that
could result in failure to respond to a subsequent PRLI.
[ER67333]

* 8100 only. Changed login/logout IOCB processing to correctly
format a LOGO sent to the fabric controller. [ER69214]

* Resolved a Fatal Firmware Error (8002h) due to a race condition
when the exchange timer expires at the same time FCP_XFER_RDY
is received. [ER69068]

* 8100 only. Changed link down handling to prevent a stall in
received FCoE frame processing. [ER68914]

* Prevented Fatal Firmware Error (8002h) when processing an invalid
ELS response type. This problem could occur if a switch sent an
erroneous ELS response to a CT pass-thru request. [ER68488]

* 8100 only. Fixed a hang that could occur when processing a new
request for an FCP2 capable device after a link status change.
[ER68339]

* 2532/8100 only. Resolved intermittent Fatal Firmware Error (8002h)
and FKA failures during Flash access. [ER68257]

* Modified RNID processing to correctly handle a response with a
"Specific Identification Data Length" field of zero. [ER67623]

* 2532/8100 CRC T10. Changed buffer pointer validation to prevent
erroneous 8002 system errors. [ER67568]

* 24xx/2532 only. Fixed a Fatal Firmware Error (8002h) caused by a
problem cleaning up after a port discovery timeout. [ER67345]

* 8100 only. Prevented accidental overwrite of the PortName within a
port descriptor data structure. Problem could occur during the
execution of mailbox commands 30h, 31h, 51h, or 60h. [ER67181]

* Fixed 200ms delay for Command Type 6 IOCBs when residual underrun
occurs, and FCP_RSP DMA is enabled. [ER67159]

* 8100 only. Resolved intermittent resource allocation failures in
Read SFP mailbox command (31h). Improved failure sub code
reporting in mailbox 1 for both Read(31h) and Write(30h) mailbox
commands. [ER69146]

* Corrected ADISC ELS check for ELS passup and fixed potential bad
pointer when building ELS frame. [ER67799]

* Fixed mailbox command Diagnostic Loop Back failures with Status
4005 and Subcode 0x17. [ER67690 8100 only]

* Fix erroneous discard of a valid FIP VLAN Notification frame
when the frame does not have an IEEE 801.2 Q Tag and the FIP
descriptor list length is greater than 8 (words).
[ER67062 8100 only]

* 24xx/2532 only. Improved firmware handling of I2C SFP interface
to better support some SFPs. [ER67479]

From Version 5.01.00 to 5.02.00

Changes
-------
* Customer-specific changes. [ER55377, ER65196, ER66011, ER65528]

* 8100 only. Report NIC driver attached status in Get firmware State
Mailbox Command (069h). For details, see the 8100 Series Fibre
Channel Firmware Interface Specification, rev C. [ER65051]

* 8100 only. Firmware will return parameter error (4006h) if the
Initialize Firmware Mailbox Command (060h) or Initialize Firmware
Multiple IDs Mailbox Command (048h) specifies use of the optional
Extended Initialization Control Block and provide a length of zero
bytes. [ER65184]

* 8100 only. Changed the Perform Implicit LOGO Mailbox Command
(072h) to allow the Perform Logout for All Ports across All
FCFs option (bit 1 of incoming Mailbox Register 1) in single FCF
configurations. [ER65220]

* 8100 only. Added FIP Version 1 support.
[ER65589, ER65593, ER65595, ER65605, ER65805]

* Added a feature to reject PRLI from Fabric Control (FFFCxx) when
target mode is disabled. To enable this option, set bit 7 of
Mailbox 2 in the Set Additional Firmware Options Mailbox Command
(0038h). [ER66061]

* 8100 only. Changed Get Link Status/Read Port Status Mailbox
Command (06Bh) and Get Link Statistics and Private Data Mailbox
Command (06Dh) to return counters consistent with the FCoE Link
Error Status Block (LESB). Figure 3-4 of the 8100 Series Fibre
Channel Firmware Interface Specification now contains the
following counters: Link Failure Count, Virtual Link Failure
Count, Missing FIP Keep Alive or Discovery Advertisement Count,
Symbol Error During Carrier Count, Error'd Block Count,
and Frame Check Sequence Error Count. [ER66125]

Bug Fixes
---------
* MID only. Fixed an issue to prevent invalid VP misconfigurations
that can result in a Fatal Firmware Error 8002h. [ER63706]

* Corrected DMA Error checking logic during Loopback Mailbox Command
(0045h). [ER64335]

* 8100 MID only. Prevent transmission of ELS requests before receipt
of FLOGI accept. [ER64498]

* Fixed potential hang due to mishandling of completer aborts during
transmit DMA. [ER64513]

* 8100 only. Enhanced FIP, CVL, FLOGI/FDISC, SCR, SNS PLOGI retry
error handling. [ER65077, ER65585, ER65759, ER65780, ER65962,
ER66186]

* 8100 only. Corrected ELS and BLS timeout units conversion when
processing Mailbox Commands Get Timeout Parameters (0022h) and
Set Timeout Parameters (0032h). [ER65155]

* 8100 only. Corrected an issue after External Loopback was
performed that prevented FIP from completing. [ER65165]

* SB2 only. Corrected a condition in RRQ processing that could
result in a Fatal Firmware Error (8002h) after receipt of an ABTS.
[ER65232]

* Fixed an issue that caused a rediscovery of FCFs
if FIP FLOGI timed out. [ER65757]

* Corrected a problem in target mode operation during confirmation processing that could result in a
Fatal Firmware Error 8002h. [ER65415 8100 only]

* 24xx and 2532 only. Corrected auto-negotiation algorithm that
would restore the link at the previous speed instead of the
maximum speed. [ER65802]

* 8100 non MID only. Corrected a condition where the firmware state
would not become Ready after switch port was shutdown and
restored. [ER65980]

* Retry FIP VLAN Discovery after FIP Discovery
Solicitation fails to find a primary FCF. [ER65980]

* Return LoginState in IO Parameter 1 when Login/Logout IOCB PRLI
IO Parameter 0 = 4 (Command Failed). [ER66045]

* 2532 and 8100 MID only. Corrected VP Index range checking during
processing of VP Control IOCB. [ER66068]

* Corrected Firmware Error reported during Purex IOCB processing if
the Port Database for the target device had been initialized.
[ER66082]

* 8100 only. Fixed detection of EP device. [ER66204]

* MID only. Corrected a problem which could result in LOGO sent with
SID=000000 or incorrect reporting of VP status after a VP is
disabled. [ER66553]

* 2532/8100 MIDQ only. Resolved a long delay in processing Command
Type 6 IOCBs after link level fault injection. [ER66755]

* Fixed RISC pause condition when using T10 CRC with DIF_bundling.
[ER66803]

From Version 5.00.00 to 5.01.00

Changes
-------
* Customer-specific changes. [ER61070, ER62265, ER62894, ER63194,
ER63873]

* 2532 and 8100 only. Add DSD chaining support to command CRC type
IOCBs. [ER62531]

* 8100 only. Updated Immediate Notify to reflect format described in
the firmware spec. For details, see the 8100 Series Fibre Channel
Firmware Interface Specification Rev C. [ER63872, ER64455]

* 8100 only. Implement FIP VLAN Discovery. [ER64026]

* 8100 only. When detected, report MPI configuration error and
reason code in Get Firmware State Mailbox Command (069h).
For details, see the 8100 Series Fibre Channel Firmware Interface
Specification Rev C. [ER64342]

* 8100 only. Added new error completion codes to Restart MPI Mailbox
Command (03Dh). For details, see the 8100 Series Fibre Channel
Firmware Interface Specification Rev C. [ER64391]

* 8100 only. Implement SFP Read/Write Mailbox Commands
(031h and 030h). For details, see the 8100 Series Fibre Channel
Firmware Interface Specification Rev C. [ER64406]

* 8100 only. Modify Report ID Acquisition IOCB to return subcode for
status 0x01, Unable to acquire ID, for FDISC. The subcode is
returned at offset 10h. [ER64497]

* 8100 only. Update Get DCBX Parameters Mailbox Command (051h) to
match latest spec. For details, see the 8100 Series Fibre Channel
Firmware Interface Specification Rev C. [ER64672]

* 8100 only. Implement Get XGMAC Statistics Mailbox Command (07Ah).
For details, see the 8100 Series Fibre Channel Firmware Interface
Specification Rev C. [ER64673]

* 8100 only. Return SFP status information. See Asynchronous Event
8012h and Mailbox Commands 05Dh, 048h, 060h, and 069h. For
details, see the 8100 Series Fibre Channel Firmware Interface
Specification Rev C. [ER64732]

Bug Fixes
---------
* 8100 only. Corrected handling of FLOGI Timeout and Reject
processing by using Retry Count and Timeout as specified in
Initialize Firmware Control Block. [ER63856]

* Corrected a condition where an Immediate Notify could be sent
to the system driver when a VP is not configured for Target Mode
operation. [ER64176]

* Corrected cleanup of pending Transmit Data requests across fault
injection. [ER64251]

* 8100 only. Corrected a potential firmware hang condition after
processing an ELS timeout or recovering from an internal error.
[ER64265]

* SB2 only. Corrected a condition where the System Defined 1 field
of an IOCB being returned to the system driver may be overwritten.
[ER64315]

* 8100 only. Correct an issue with Flash Access Mailbox Command
(003Eh). [ER64377]

* 8100 only. Corrected potential FCoE traffic stall after Port Reset
completes. [ER64435]

* 8100 only. Fix FIP Failure to find FCF after a number of cable
pulls/insertions into different FCF ports. [ER64454]

* 8100 only. Get FCF List Mailbox Command (050h) may fail to find
valid FCF Index. [ER64507]

* 8100 only. Corrected false Loopback errors reported during
internal and external tests. [ER64520]

* Corrected potential RISC pause when PUREX
is enabled. [ER64520]

* 8100 only. Fixed incorrect Destination MAC address in FIP FLOGI
request after an FCF Fabric name change. [ER64585]

* 8100 only. Allow primary port to be discovered via FDISC after it
received a Clear Virtual Link or Fabric LOGO and another Virtual
Port becomes the master. [ER64590]

* 2400/2532 only. Corrected a condition where a FCP RSP could be
transmitted across a LIP and before the discovery timer expires
in private loop topology. [ER64705]

* 8100 only. Corrected Firmware hang condition after receiving an
ABTS. [ER64902]

From Version 4.06.00 to 5.00.00

Changes
-------
* MID only. The firmware now returns a Port Unavailable (28h)
Completion Status if the VP Index fails validation during a
SCSI Task Management request. [ER62857]

* MID only. The firmware now allows Get VP Database Mailbox
Command (49h) regardless of VP Status. [ER62858]

* SB2 only. The firmware now allows Get Link Status Mailbox
Command (06bh) to complete even though Process Login has not
completed. [ER63650]

Bug Fixes
---------
* Fixed an issue to prevent initiating an LR upon a Transmit timeout
while the firmware services other requests. [ER61666]

* Fixed an issue that delayed starting new Transmit requests if a
Transmit error is pending. [ER61682]

* Corrected the auto-negotiation algorithm that could prevent the
link from establishing when connected to a switch.
[ER62000, ER62172]

* Corrected CTIO handling when link is down and CTIO received with
an Exchange Address of FFFFFFFFh. [ER62715]

* MID only. Corrected various issues relating to VF support.
[ER62798]

* Corrected issues found with VF and Fabric LOGO processing. Also
corrected the valid VP Count range to 1-254. [ER62826]

* MID only. Corrected Source and Destination Address on an
SCR retry. [ER62886]

* Completed various FCE tracing fixes. [ER62952, ER63400]

* Customer-specific fix. [ER63104]

* Corrected IDLE character to ArbFF when connected at 8Gb rate.
[ER63488]

* Corrected an issue where a Mailbox or Mailbox IOCB request would
not complete if a Fabric LOGO occurred. [ER63563]

* DISK CRC only. Corrected a RISC Pause condition reported during
cable pull testing.[ER63564]

* Fixed an incorrect Response In Pointer reported in the RISC to
Host Status Register when running in ZIO mode. [ER63790]

* 2532 MID multiple queue only. Corrected a link credit issue that
resulted in decreased performance. [ER63913]

From Version 4.05.00 to 4.06.00

Changes
-------
* 2532 only. Added support for Virtual Fabrics. Contact QLogic for
API changes to support VFs. [ER60036, ER60250]

* Customer-specific change. [ER61654, ER61694, ER61837, ER62184]

* MID only. Added feature to allow the firmware to perform SNS Login
and SCR registration for virtual ports. This feature is enabled
by setting bit 6 of the Options field during Initialize Firmware -
Multiple IDs Mailbox Command (048h). Added the following status/
substatus values to Report ID Acquired IOCB:

VP Status Description
--------- -----------
3 SNS Timeout. See byte offsets 23:20 for Sub-status.
4 SNS LS_RJT (Reason/Explanation/Vendor Unique in IOCB
byte offsets 23:20).
5 SCR Timeout. See byte offset 23:20 for Sub-status.
6 SCR LS_RJT (Reason/Explanation/Vendor Unique in IOCB
byte offsets 23:20).[ER61930]

Bug Fixes
---------
* MID only. Process received LOGO from F_Port. The associated Port
Database Changed (8014h) asynchronous event will differ from a
LOGO received from an N_Port as follows:

Outgoing Mailbox N_Port F_Port
---------------- ------ ------
0 8014h 8014h
1 N_Port Handle 7FEh
2 0007 0007
3 0Bh/VPIndex 1Ah/VPIndex [ER60623]


* MID only. Corrected validation of VP Index received in a CT Pass-
Through request. [ER61522]

* Corrected verification of RX_ID in received ABTS frame. [ER61591]

* Disk CRC only. Corrected inadvertent drop of received XFER_RDY.
This problem was introduced as a result of ER60318. [ER61659]

* Corrected Fatal Firmware Error 8002h when firmware received
back-to-back SRRs for the same exchange. [ER61757]

* Corrected Fatal Firmware Error 8002h when an invalid FAN is
received and Disable Automatic PLOGI option is selected.
[ER61763]

* Populate hard address field in ADISC when previous address bit
is set when the ISP is operating in a loop topology.
[ER61765]

* 24xx only. Improved link recovery after LR/LRR when using Inline
Credit Extender. [ER61775]

* Mercury Converged Network Adapter only. De-Register MAC address
associated with a logged out Virtual Port. [ER61890]

* Corrected upper 16 bits of receive exchange address when CTIO
Error completion status is returned. [ER62084]

* Corrected Fatal Firmware Error 8002h during target mode operation
when attempting to transmit a FCP RSP after fault injection.
[ER62118]

* A Command Parameter Error will be returned for a Login/Logout IOCB
received with a non reserved N_Port Handle with a reserved Port
ID. [ER62321]

* MID only. Corrected potential issue with sending a frame with
incorrect Port/Node Name. [ER62348]

From Version 4.04.00 to 4.05.00

Changes
-------
* Customer-specific change. [ER60313, ER60909, ER61325, ER61654]

* 2532 only. Added the ability to specify a maximum Fibre Channel
Link speed to be negotiated. This feature is enabled by bit 12 of
the Initialize Firmware Control Block’s Firmware Option 3. When
this bit is set to 1, firmware will negotiate the FC data rate
from the given max speed specified by driver in bits 15-13 of the
Initialize Firmware Control Block’s Firmware Options 3 field to
two speeds down to what the SFP allowed.
This option can also be set in the Data Rate Mailbox Command
(05dh). When incoming mailbox 1 is set to 03h, firmware forces
a loss of sync, restarts link initialization, and negotiates the
FC data rate from the given max speed specified by driver in
incoming mailbox 2 to two speeds down to what the SFP allowed.
[ER60321]

* Allow system driver to send LOGO ELS via ELS Pass-Through IOCB
using an N_Port Handle of FFFFh. [ER60400]

* MID only. Return Command Parameter Error (4006h) if the number
of requested VP’s exceeds the limit when issuing Initialize
Firmware – Multiple-IDs Mailbox Command (048h).

* 2432 only. Disable PCIe Completion Timeout. PCIe Completion
Timeout has been disabled to address issues seen on certain
systems where PCIe completion could take over 50ms. [ER61461]

Bug Fixes
---------
* MID only. Corrected problems related to fault injection.
[ER59740, ER60612]

* MID only. Various fixes to improve detection and processing
of topology changes. [ER60127, ER60326, ER60610, ER60633]

* Corrected timing of when RRQ is issued after ABTS ACC is received.
[ER60248]

* Corrected Out-of-Order handling of overlapped or repeating
received XFR_RDY frames. [ER60318]

* 2532 Disk CRC only. Various Disk CRC changes to remove Fatal
Firmware errors (8002h) being reported. [ER60336, ER61222,
ER61223]

* MID only. Corrected a problem where a LOGO ELS could be sent
to a port that was not logged in. [ER60565]

* MID only. Corrected a problem where a FLOGI/FDISC would not be
sent to the switch after a previous FLOGI/FDISC completed with
an ELS RJT. [ER60566]

* MID only. A PLOGI could be rejected for a Virtual Port even though
the Primary Port parameters have not changed. [ER60568]

* MID only. Corrected a problem where an incorrect number of
acquired AL_PAs could be reported during the LIRP and LILP
phases of loop initialization. [ER60569]


* MID only. Login/Logout IOCB completion status was incorrect when
no FLOGI ACC ELS had been received. [ER60571]

* Corrected a Fatal Firmware Error (8002h) when a CTIO IOCB with
Confirmation Satisfied is received when the FCP_RSP has not been
sent yet. The CTIO will be returned with a completion status of
Invalid Request (06h). [ER60572]

* MID only. Corrected handling of incoming frames while waiting for
LOGI ACC ELS for the primary port. [ER60576]

* Corrected a problem when attempting to abort an ELS Pass-Through
operation when a PLOGI is received that changes the ports D_ID.
[ER60637]

* Class 2 only. Corrected Fatal Firmware Error (8002h) reported when
attempting to abort transmit operations. [ER60698]

* Corrected timer values used with link recovery. [ER60877]

* Improved handling of receiving an ABTS for a CT Pass-Through
exchange. [ER61007]

* Corrected a problem with aborting IOs for the incorrect LUN
when a LUN Level Task Management Function is active.
[ER61155]

* MID only. Ensure that Buffer-Buffer Credits are not modified
when processing FDISC or FDISC-ACC. [ER61187, ER61216]

* MID only. Correctly track changing of local 24-bit ID during
cleanup. [ER61200]

* Handle race condition of completing transmit of PLOGI-ACC and
receiving PRLI. [ER61465]

From Version 4.03.02 to 4.04.00

Changes
-------
* Customer-specific change. [ER56370, ER58608, ER59978]

* Corrected failures reported by Loopback Mailbox Command (45h)
and Echo Mailbox Command (44h). Added sub-error codes to
Outgoing Mailbox 3 of the Echo Command to match the Loopback
Command. [ER59630, ER59631]

Bug Fixes
---------
* Disk CRC only. Corrected handling of frames received out of order
in target mode. [ER58251, ER58760, ER58761]

* 2532 Disk CRC only. Corrected condition where the firmware would
overwrite the IOCB Entry Status field when the device receives
invalid IOCBs. [ER58532]

* 2532 Disk CRC only. Fixed a condition that could result in false
DIF Errors when receiving runt block data. [ER58533]

* Disk CRC and 2532 only. Corrected an issue with multi-sequence
DIF Remove functionality. [ER58752]

* 2532 only. Corrected a RISC pause that occurred when optional
external memory is present. [ER58783]

* Corrected endianess of RNID user defined data field.
[ER58802]

* Set correct Immediate Notify IOCB sub-code during fault
injection. [ER58897]

* Improved handling of switches that transition link from F-FL-F
when the device is directly connected to a switch port.
[ER59100]

* Corrected issues relating to the EHAFT feature.
[ER59279, ER59431]

* Corrected a target mode issue where an ATIO Queue update
interrupt would not be posted when using a small ATIO queue.
[ER59385]

* Corrected a Fatal Firmware Error (8002h) reported when ISP
receives FCP_RSP with a payload length greater than 240 bytes.
This problem would occur when Command Type 6 IOCB is used with
the option to DMA the FCP_RSP payload to the host is enabled.
[ER59503]

* 2532 only. Corrected the ending memory address reported by About
Firmware Mailbox Command (08h) when external memory is present.
[ER59793]

* 2532 only. Corrected the Report Link Statistics information
for Loop topology. [ER59989]

* SB2 only. Corrected a problem where the firmware was clearing
the N_Port Handle field of a SB2 Send IU IOCB. [ER60017]

* Disk CRC and 2532 only. Corrected false DMA error reported when
using CTIO Type 7 IOCB (Target Mode) with Status Mode 2 selected.
[ER60067]

* Fixed a problem that may cause a target level Task Management
Function to fail while a LUN Level Task Management Function is
outstanding. [ER60126]

* MID and 2532 only. Corrected a Fatal Firmware Error (8002h)
reported after adapter side fault injection. [ER60256]

* Corrected a condition where the local loop would not recover
after a transmit error was encountered.[ER60301]

From Version 4.03.01 to 4.03.02

Changes
-------
* 2532 only. Enabled additional FC SerDes parameters to be set
via Flash for mezzanine cards. [ER59755]

Bug Fixes
---------
None

From Version 4.03.00 to 4.03.01

Changes
-------
* 2532 only. Added support for mezzanine adapters Added a new bit,
Embedded HBA, in Flash to indicate an adapter that does not use
SFP+, and transmits FC signal over a copper backplane
or mid-plane. [ER58635]

Bug Fixes
---------
* 2432 only. Corrected a condition where Mailbox Commands
issued to Function 1 would not complete after issuing Stop
Firmware Mailbox Command (14h) to Function 0. [ER58617]


2. Known Issues

None.


3. Notices

Information furnished in this document is believed to be accurate and
reliable. However, QLogic Corporation assumes no responsibility for
its use, nor for any infringements of patents or other rights of
third parties which may result from its use. QLogic Corporation
reserves the right to change product specifications at any time
without notice. Applications described in this document for any of
these products are only for illustrative purposes. QLogic Corporation
makes no representation nor warranty that such applications are
suitable for the specified use without further testing or
modification. QLogic Corporation assumes no responsibility for any
errors that may appear in this document.


4. Contacting Support

For further assisance, contact QLogic Technical Support at:
http://support.qlogic.com


Trademarks

Accelera, Accelerating Cluster Performance, InfiniCon Systems,
InfiniNIC, InfiniPath, InfiniView, QLA, QLogic, the QLogic logo,
ReadyPath, SANdoctor, SANsurfer, and SilverStorm are registered
trademarks of QLogic Corporation. All other brand and product names
are trademarks or registered trademarks of their respective owners.


(c) Copyright 2013. All rights reserved worldwide. QLogic and the
QLogic logo are registered trademarks of QLogic Corporation.
All other brand and product names are trademarks or registered
trademarks of their respective owners.
qlgc_dd_fc_9_1_11_28_windows_32-64_chg

QLogic 10 GbE Converged Network Adapter MultiFlash Update for System x
IBM P3P Firmware Change History
QLogic Corporation.
All rights reserved.

Package Version 2.20.22

Updated QCCCLI

Release Version: 2.20.22

Table of Contents
1. Version
2. Changes
3. Limitations
4. Known Issues
5. Additional Information
6. Trademarks
7. Notices
8. Contacting Support


1. Version

The files contained in this Flash image package are zipped into a file that
will expand to provide the following versions for the 3200/8200 Series Adapters.


* Flash Image Version 2.20.22

P3P22022.BIN contains:
----------------------
* NIC PXE (3200/8200 Series)
PXE 3.0 version 2.0.2.37
PXE EFi version 2.6.19 signed
* FCoE BIOS (8200 Series only)
BIOS 3.0 version 3.27
uEFI version 6.09 Signed
* iSCSI BIOS (8200 Series only)
BIOS 3.0 version 2.19
uEFI version 2.04.12 signed
* Firmware - v4.16.151
* Pegtune - v4.16.32
* Bootloader - v4.16.05
* CRBinit - v4.12.07

* QLflash version 1.0.0.14


***********************************************


* Flash Image Version 2.20.18

P3P22018.BIN contains:
----------------------
* NIC PXE (3200/8200 Series)
PXE 3.0 version 2.0.2.37
PXE EFi version 2.06.19 A4
* FCoE BIOS (8200 Series only)
BIOS 3.0 version 3.25
uEFI version 6.08
* iSCSI BIOS (8200 Series only)
BIOS 3.0 version 2.19
uEFI version 2.04.11
* Firmware - v4.16.150
* Pegtune - v4.16.32
* Bootloader - v4.16.05
* CRBinit - v4.12.07

* QLflash version 1.0.0.14 (clean)


****************************************************

* Flash Image Version 2.20.09

P3P22009.BIN contains:
----------------------
* NIC PXE (3200/8200 Series)
PXE 3.0 version 2.0.2.37
PXE EFi version 2.6.16
* FCoE BIOS (8200 Series only)
BIOS 3.0 version 3.25 beta 1
uEFI version 6.08
* iSCSI BIOS (8200 Series only)
BIOS 3.0 version 2.19
uEFI version 2.04.11
* Firmware - v4.16.150
* Pegtune - v4.16.32
* Bootloader - v4.16.05
* CRBinit - v4.12.07

* QLflash version 1.0.0.14


****************************************************


* Flash Image Version 2.20.07

P3P22007.BIN contains:
----------------------
* NIC PXE (3200/8200 Series)
PXE 3.0 version 2.0.2.37
PXE EFi version 2.6.14
* FCoE BIOS (8200 Series only)
BIOS 3.0 version 3.25 beta 1
uEFI version 6.08
* iSCSI BIOS (8200 Series only)
BIOS 3.0 version 2.19
uEFI version 2.04.11
* Firmware - v4.16.150
* Pegtune - v4.16.32
* Bootloader - v4.16.05
* CRBinit - v4.12.07

* QLflash version 1.0.0.14

****************************************************




* Flash Image Version 2.20.04

P3P22004.BIN contains:
----------------------
* NIC PXE (3200/8200 Series)
PXE 3.0 version 2.0.2.31
PXE EFi version 2.6.13
* FCoE BIOS (8200 Series only)
BIOS 3.0 version 3.24
uEFI version 6.07
* iSCSI BIOS (8200 Series only)
BIOS 3.0 version 2.19
uEFI version 2.04.03
* Firmware - v4.16.34
* Pegtune - v4.16.32
* Bootloader - v4.16.05
* CRBinit - v4.12.07

* QLflash version 1.0.0.14

****************************************************


* Flash Image Version 1.12.21

P3P11221.BIN contains:
----------------------
* NIC PXE (3200/8200 Series)
PXE 3.0 version 2.0.2.31
PXE EFi version 2.06.11
* FCoE BIOS (8200 Series only)
BIOS 3.0 version 3.13
uEFI version 4.55
* iSCSI BIOS (8200 Series only)
BIOS 3.0 version 2.13
uEFI version 2.04.02
* Firmware - v4.12.13
* Pegtune - v4.12.07
* Bootloader - v4.12.06
* CRBinit - v4.12.07

* QLflash version 2.0.0.4



*****************************************************

* Flash Image Version 1.11.71

P3P11171.BIN contains:
----------------------
* NIC PXE (3200/8200 Series)
PXE 3.0 version 2.0.0.24
PXE EFi version 2.06.04
* FCoE BIOS (8200 Series only)
BIOS 3.0 version 3.13
uEFI version 4.55
* iSCSI BIOS (8200 Series only)
BIOS 3.0 version 2.13
uEFI version 2.04.01
* Firmware - v4.12.13
* Pegtune - v4.12.07
* Bootloader - v4.12.06
* CRBinit - v4.12.07

* QLflash version 1.0.0.10



*****************************************************
* Flash Image Version 1.11.33

P3P11133.BIN contains:
----------------------
* NIC PXE (3200/8200 Series)
PXE 3.0 version 2.0.0.24
PXE EFi version 2.0.6.02
* FCoE BIOS (8200 Series only)
BIOS 3.0 version 3.06
uEFI version 4.55
* iSCSI BIOS (8200 Series only)
BIOS 3.0 version 2.13
uEFI version 2.31
* Firmware - v4.12.10
* Pegtune - v4.12.07
* Bootloader - v4.12.06
* CRBinit - v4.12.07

* QLflash version 1.0.0.10


******************************************************
Initial Release

2. Changes

Updated QCCCCLI to support windows WS2K8 R2;

Hardware Support
Standard Servers with PCIe 1.1 and 2.0 x8

3. Limitations

None

Industry Standards Compliance
N/A


4. Known Issues



5. Additional Information
None


6. Trademarks
Accelera, Accelerating Cluster Performance, InfiniCon Systems,
InfiniNIC, InfiniPath, InfiniView, QLA, QLogic, the QLogic logo,
ReadyPath, SANdoctor, SANsurfer, and SilverStorm are registered
trademarks of QLogic Corporation. All other brand and product names
are trademarks or registered trademarks of their respective owners.


7. Notices
Information furnished in this document is believed to be accurate and
reliable. However, QLogic Corporation assumes no responsibility for
its use, nor for any infringements of patents or other rights of third
parties which may result from its use. QLogic Corporation reserves the
right to change product specifications at any time without notice.
Applications described in this document for any of these products are
only for illustrative purposes. QLogic Corporation makes no
representation nor warranty that such applications are suitable for
the specified use without further testing or modification. QLogic
Corporation assumes no responsibility for any errors that may appear
in this document.


8. Contacting Support
Please feel free to contact your QLogic Technical Support at any phase
of integration for assistance. QLogic Technical Support can be reached
at:

Gary Stift gary.stift@qlogic.com


(c) Copyright 2014. All rights reserved worldwide. QLogic, the QLogic
logo, and the Powered by QLogic logo are registered trademarks of
QLogic Corporation. All other brand and product names are trademarks
or registered trademarks of their respective owners.

qlgc_fw_cna_sysx-2_20_22_windows_32-64_chg

===============================================================================
Emulex OCe11xxx UCNA Firmware Package
===============================================================================

Firmware Version: 10.2.377.29
Supported On: System x and BladeCenter

Problems Fixed:
- iSCSI SAN Boot failed after OS installation completed in UFP and vNIC1 mode
with OCe12000 adapter

Incremental Interoperability:
- None

Known Issues:
- Server hangs at "Scan for Fibre Devices", when port disable/enable performed
on the Brocade Converged 10 Gb Ethernet Switch Module for IBM BladeCenter.
Do not force the link down after POST has completed and then attempt a
discovery of the SAN. If you do a reboot is needed.(159125)

- To disable BFS after BOFM or IFM have been enabled, it must be done by
setting BFS manually in the EFIBoot config utility or sending a BOFM default
command to the port. This is working as expected and we are documenting it
here.(159505)

- Intermittently, 255 vPorts can not be created successfully in Windows with
the error "ERROR: <127>: Not enough HBA or fabric resources. VPort not
created!". There is no known workaround other than to reduce the number
of configured vPorts.(155807)

- Target login will fail if you dynamically reconfigure the SAN after POST has
executed. If you do, then reboot the system.(159121)

- IFM Boot target is consumed on a particular port even though the target is
not accessible to that port. IFM/BOFM boot target configuration is not
supported. This limitation has existed for several code releases and we are
now documenting it here.(159226)

- The server may hang at "Connecting Boot Devices and Adapters" if both FCoE
ports have boot targets configured when using a 10Gb Ethernet Pass-Thru
Module for IBM BladeCenter. The server will not hang if only a single port
is configured with a boot target.(157137)

- In FCoE configurations with BE3 in UFP mode on System x3690 X5 servers, a
UEFI rescan is required to boot to the OS. This renders UFP not supportable
in UFP/FCoE configurations(158669)

- After making changes to any options in the sub-menus under 'controller
configuration' in the Emulex UEFI NIC configuration utility and escaping
to the prior menu, there is no prompt to save the changes. Be sure to
select 'Save' before exiting the configuration menu. Applies to some
legacy rack and blade servers.

- Intermittently, when changing the multichannel mode, the system will not
auto-reboot after exiting F1 UEFI setup and will continue through POST.
Manually reboot the server to ensure all changes are applied. Applies to
some legacy rack and blade servers.

- When using a Cisco Nexus 4001i Switch Module, intermittently the 10Gb link
may come up as 1Gb link speed. An internal switch port bounce will typically
establish a 10Gb link. Setting the switch port speed to fixed 10000 will
also allow a guaranteed 10Gb connection. More info available in the Cisco
Nexus 4001i Switch Module firmware release notes.

===============================================================================

Firmware Version: 10.2.377.18 & 10.2.377.23
Supported On: Flex

Problems Fixed:
- PXESelect showing incorrect MAC address, bandwidth & SVID values. This bug
is a cosmetic issue and only impacts PXESelect. The values which are not
displayed correctly in PXESelect can be viewed in UEFI, OCM, and on the
switch.(151140)
- "Configurations have changed" message seen in UEFI setup screen when no
changes were made. This pop-up can be ignored and will be fixed in a future
code release.(159086)
- FCoE VLAN ID is being displayed incorrectly as hexadecimal in UEFI menu.
This is a cosmetic issue only. The correct VLAN is properly assigned, so
there is no functional impact. The actual VLAN ID can be observed elsewhere.
(159561)
- UE seen while booting the system after a CoreDump
- When NIC traffic has run on all the 8 vNICs of an ASIC, the vnics of first
port are not honoring the assigned BW
- SRIOV performance & Fairness for 16VMs is low on Linux and VMware
- ML2 VFA5 device name is show "N/A" under IMM web and CLI of
server management>Adapters
- BW changes not getting updated with vNIC1 mode
- Enable 100M/10M speed in set speed for SGMII interface
- UCM/vNIC2, Ports/PCI functions supporting FCoE need to be differentiated to
make it easier for the user
- UCM/vNIC2 ability to program VirtWWN/WWPN independent of BFS Enable
- iSCSI boot not working on higher order PCI functions (PF8 11)on 4 port
controllers on ARI enabled systems
- Can't install Windows2012 onto the iSCSI LUN whose LUN ID is not 0
- Fixed several issues related to IBM Agentless inventory management

Incremental Interoperability:
- Grantley Rack Servers

Known Issues:
- Server hangs at "Scan for Fibre Devices", when port disable/enable performed
on the Brocade Converged 10 Gb Ethernet Switch Module for IBM BladeCenter.
Do not force the link down after POST has completed and then attempt a
discovery of the SAN. If you do a reboot is needed.(159125)

- To disable BFS after BOFM or IFM have been enabled, it must be done by
setting BFS manually in the EFIBoot config utility or sending a BOFM default
command to the port. This is working as expected and we are documenting it
here.(159505)

- Intermittently, 255 vPorts can not be created successfully in Windows with
the error "ERROR: <127>: Not enough HBA or fabric resources. VPort not
created!". There is no known workaround other than to reduce the number
of configured vPorts.(155807)

- Target login will fail if you dynamically reconfigure the SAN after POST has
executed. If you do, then reboot the system.(159121)

- IFM Boot target is consumed on a particular port even though the target is
not accessible to that port. IFM/BOFM boot target configuration is not
supported. This limitation has existed for several code releases and we are
now documenting it here.(159226)

- The server may hang at "Connecting Boot Devices and Adapters" if both FCoE
ports have boot targets configured when using a 10Gb Ethernet Pass-Thru
Module for IBM BladeCenter. The server will not hang if only a single port
is configured with a boot target.(157137)

- In FCoE configurations with BE3 in UFP mode on System x3690 X5 servers, a
UEFI rescan is required to boot to the OS. This renders UFP not supportable
in UFP/FCoE configurations(158669)

- After making changes to any options in the sub-menus under 'controller
configuration' in the Emulex UEFI NIC configuration utility and escaping
to the prior menu, there is no prompt to save the changes. Be sure to
select 'Save' before exiting the configuration menu. Applies to some
legacy rack and blade servers.

- Intermittently, when changing the multichannel mode, the system will not
auto-reboot after exiting F1 UEFI setup and will continue through POST.
Manually reboot the server to ensure all changes are applied. Applies to
some legacy rack and blade servers.

- When using a Cisco Nexus 4001i Switch Module, intermittently the 10Gb link
may come up as 1Gb link speed. An internal switch port bounce will typically
establish a 10Gb link. Setting the switch port speed to fixed 10000 will
also allow a guaranteed 10Gb connection. More info available in the Cisco
Nexus 4001i Switch Module firmware release notes.

===============================================================================

Firmware Version: 10.2.261.41
Supported On: IBM System x

Problems Fixed:
- Hit BSOD during VMQ overnight traffic test with cpu affinity change
- IBM VFA5 Adapter causing software panic on IBM G8246 Switch in UFP mode
- LPVIDs are not getting saved in vNIC2 mode if we change mode from vNIC1
mode to vNIC2
- In MC VINC1, VNIC2, UFP modes, user should see only 4 functions per port
for 2 port card

Incremental Interoperability:
- Emulex VFA5 2x10 GbE SFP+ Adapter and FCoE/iSCSI SW for IBM System x
- Emulex VFA5 2x10 GbE SFP+ PCIe Adapter for IBM System x
- Emulex VFA5 2x10 GbE SFP+ Integrated Adapter for IBM System x

Known Issues:
- Server hangs at "Scan for Fibre Devices", when port disable/enable performed
on the Brocade Converged 10 Gb Ethernet Switch Module for IBM BladeCenter.
Do not force the link down after POST has completed and then attempt a
discovery of the SAN. If you do a reboot is needed.(159125)

- To disable BFS after BOFM or IFM have been enabled, it must be done by
setting BFS manually in the EFIBoot config utility or sending a BOFM default
command to the port. This is working as expected and we are documenting it
here.(159505)

- Intermittently, 255 vPorts can not be created successfully in Windows with
the error "ERROR: <127>: Not enough HBA or fabric resources. VPort not
created!". There is no known workaround other than to reduce the number
of configured vPorts.(155807)

- Target login will fail if you dynamically reconfigure the SAN after POST has
executed. If you do, then reboot the system.(159121)

- PXESelect showing incorrect MAC address, bandwidth & SVID values. This bug
is a cosmetic issue and only impacts PXESelect. The values which are not
displayed correctly in PXESelect can be viewed in UEFI, OCM, and on the
switch.(151140)

- IFM Boot target is consumed on a particular port even though the target is
not accessible to that port. IFM/BOFM boot target configuration is not
supported. This limitation has existed for several code releases and we are
now documenting it here.(159226)

- "Configurations have changed" message seen in UEFI setup screen when no
changes were made. This pop-up can be ignored and will be fixed in a future
code release.(159086)

- The server may hang at "Connecting Boot Devices and Adapters" if both FCoE
ports have boot targets configured when using a 10Gb Ethernet Pass-Thru
Module for IBM BladeCenter. The server will not hang if only a single port
is configured with a boot target.(157137)

- FCoE VLAN ID is being displayed incorrectly as hexadecimal in UEFI menu.
This is a cosmetic issue only. The correct VLAN is properly assigned, so
there is no functional impact. The actual VLAN ID can be observed elsewhere.
(159561)

- In FCoE configurations with BE3 in UFP mode on System x3690 X5 servers, a
UEFI rescan is required to boot to the OS. This renders UFP not supportable
in UFP/FCoE configurations(158669)

- After making changes to any options in the sub-menus under 'controller
configuration' in the Emulex UEFI NIC configuration utility and escaping
to the prior menu, there is no prompt to save the changes. Be sure to
select 'Save' before exiting the configuration menu. Applies to some
legacy rack and blade servers.

- Intermittently, when changing the multichannel mode, the system will not
auto-reboot after exiting F1 UEFI setup and will continue through POST.
Manually reboot the server to ensure all changes are applied. Applies to
some legacy rack and blade servers.

- When using a Cisco Nexus 4001i Switch Module, intermittently the 10Gb link
may come up as 1Gb link speed. An internal switch port bounce will typically
establish a 10Gb link. Setting the switch port speed to fixed 10000 will
also allow a guaranteed 10Gb connection. More info available in the Cisco
Nexus 4001i Switch Module firmware release notes.

===============================================================================

Firmware Version: 10.2.261.36
Supported On: IBM System x, BladeCenter, and Flex

Problems Fixed:
- FRU VPD fields are now properly populated on CN4054 and CN4054R
- Fixed UE resulting slow boot at UEFI splash screen and NIC devices removed
- When using VMQ with Windows Server 2012 or 2012R2, the user may experience
VM connectivity loss, packet drops, system hangs, inability to shutdown VMs
and possible system crashes on shutdown. The complete solution also
requires 10.2 based Windows NIC driver.

Incremental Interoperability:
- Inventory support for the Flex xHMC (Chassis Hardware Management Console)

Known Issues:
- Server hangs at "Scan for Fibre Devices", when port disable/enable performed
on the Brocade Converged 10 Gb Ethernet Switch Module for IBM BladeCenter.
Do not force the link down after POST has completed and then attempt a
discovery of the SAN. If you do a reboot is needed.(159125)

- To disable BFS after BOFM or IFM have been enabled, it must be done by
setting BFS manually in the EFIBoot config utility or sending a BOFM default
command to the port. This is working as expected and we are documenting it
here.(159505)

- Intermittently, 255 vPorts can not be created successfully in Windows with
the error "ERROR: <127>: Not enough HBA or fabric resources. VPort not
created!". There is no known workaround other than to reduce the number
of configured vPorts.(155807)

- Target login will fail if you dynamically reconfigure the SAN after POST has
executed. If you do, then reboot the system.(159121)

- PXESelect showing incorrect MAC address, bandwidth & SVID values. This bug
is a cosmetic issue and only impacts PXESelect. The values which are not
displayed correctly in PXESelect can be viewed in UEFI, OCM, and on the
switch.(151140)

- IFM Boot target is consumed on a particular port even though the target is
not accessible to that port. IFM/BOFM boot target configuration is not
supported. This limitation has existed for several code releases and we are
now documenting it here.(159226)

- "Configurations have changed" message seen in UEFI setup screen when no
changes were made. This pop-up can be ignored and will be fixed in a future
code release.(159086)

- The server may hang at "Connecting Boot Devices and Adapters" if both FCoE
ports have boot targets configured when using a 10Gb Ethernet Pass-Thru
Module for IBM BladeCenter. The server will not hang if only a single port
is configured with a boot target.(157137)

- FCoE VLAN ID is being displayed incorrectly as hexadecimal in UEFI menu.
This is a cosmetic issue only. The correct VLAN is properly assigned, so
there is no functional impact. The actual VLAN ID can be observed elsewhere.
(159561)

- In FCoE configurations with BE3 in UFP mode on System x3690 X5 servers, a
UEFI rescan is required to boot to the OS. This renders UFP not supportable
in UFP/FCoE configurations(158669)

- After making changes to any options in the sub-menus under 'controller
configuration' in the Emulex UEFI NIC configuration utility and escaping
to the prior menu, there is no prompt to save the changes. Be sure to
select 'Save' before exiting the configuration menu. Applies to some
legacy rack and blade servers.

- Intermittently, when changing the multichannel mode, the system will not
auto-reboot after exiting F1 UEFI setup and will continue through POST.
Manually reboot the server to ensure all changes are applied. Applies to
some legacy rack and blade servers.

- When using a Cisco Nexus 4001i Switch Module, intermittently the 10Gb link
may come up as 1Gb link speed. An internal switch port bounce will typically
establish a 10Gb link. Setting the switch port speed to fixed 10000 will
also allow a guaranteed 10Gb connection. More info available in the Cisco
Nexus 4001i Switch Module firmware release notes.

===============================================================================

Firmware Version: 10.0.803.13
Supported On: IBM System x

Problems Fixed:
- IBM Feature on Demand for storage keys now works with Optimized Boot enabled
- Link detection time improved from ~70 secs on DAC cable insertion/removal

Incremental Interoperability:
- Unified Fabric Protocol on IBM System x Servers

Known Issues:
- After making changes to any options in the sub-menus under 'controller
configuration' in the Emulex UEFI NIC configuration utility and escaping
to the prior menu, there is no prompt to save the changes. Be sure to
select 'Save' before exiting the configuration menu. Applies to some
legacy rack and blade servers.

- Intermittently, when changing the multichannel mode, the system will not
auto-reboot after exiting F1 UEFI setup and will continue through POST.
Manually reboot the server to ensure all changes are applied. Applies to
some legacy rack and blade servers.

- When using a Cisco Nexus 4001i Switch Module, intermittently the 10Gb link
may come up as 1Gb link speed. An internal switch port bounce will typically
establish a 10Gb link. Setting the switch port speed to fixed 10000 will
also allow a guaranteed 10Gb connection. More info available in the Cisco
Nexus 4001i Switch Module firmware release notes.

===============================================================================

Firmware version: 4.6.281.26 (supported on IBM System x, BladeCenter and Flex)

Problems Fixed:
- CN4054 VPD is not valid during/after IMM flash
- Links go down after 497 to 498 days in VMWare
- Send 'link down' to switch if UE occurs on ASIC

Incremental Interoperability:
- Emulex Dual Port 10GbE SFP+ VFA IIIr for IBM System x
- Emulex Dual Port 10GbE SFP+ Embedded VFA IIIr for IBM System x

Known Issues:
- After making changes to any options in the sub-menus under 'controller
configuration' in the Emulex UEFI NIC configuration utility and escaping
to the prior menu, there is no prompt to save the changes. Be sure to
select 'Save' before exiting the configuration menu. Applies to some
legacy rack and blade servers.

- Intermittently, when changing the multichannel mode, the system will not
auto-reboot after exiting F1 UEFI setup and will continue through POST.
Manually reboot the server to ensure all changes are applied. Applies to
some legacy rack and blade servers.

- When using a Cisco Nexus 4001i Switch Module, intermittently the 10Gb link
may come up as 1Gb link speed. An internal switch port bounce will typically
establish a 10Gb link. Setting the switch port speed to fixed 10000 will
also allow a guaranteed 10Gb connection. More info available in the Cisco
Nexus 4001i Switch Module firmware release notes.

===============================================================================

Firmware version: 4.6.281.21 (supported on IBM System x, BladeCenter and Flex)

Problems Fixed:
- OCe10 VFA CNAs stuck in "Switch Independent Mode"
- Port Identification fails on Port 1 under uEFI menu for PCIe rack VFA

Incremental Interoperability:
- IBM Flex System CN4054R 10Gb Virtual Fabric Adapter
- IBM Ivy Bridge CPU Based Servers

Known Issues:
- After making changes to any options in the sub-menus under 'controller
configuration' in the Emulex UEFI NIC configuration utility and escaping
to the prior menu, there is no prompt to save the changes. Be sure to
select 'Save' before exiting the configuration menu. Applies to some
legacy rack and blade servers.

- Intermittently, when changing the multichannel mode, the system will not
auto-reboot after exiting F1 UEFI setup and will continue through POST.
Manually reboot the server to ensure all changes are applied. Applies to
some legacy rack and blade servers.

- When using a Cisco Nexus 4001i Switch Module, intermittently the 10Gb link
may come up as 1Gb link speed. An internal switch port bounce will typically
establish a 10Gb link. Setting the switch port speed to fixed 10000 will
also allow a guaranteed 10Gb connection. More info available in the Cisco
Nexus 4001i Switch Module firmware release notes.

===============================================================================

Firmware version: 4.6.281.8
Supported On: IBM System x, BladeCenter, and Flex

Problems Fixed:
- HW iSCSI offload is now supported in UFP Mode (UFP limited to IBM Flex)
- Server may hang during boot with multichannel disabled with switch default
settings. The IBM 10Gb Virtual Fabric Switch has trunking enabled and the
Brocade Converged 10Gbe Switch Module has ports in "Access" mode. If the
Brocade Converged 10Gbe Switch Module ports are switched to trunking mode,
the hang no longer occurs.
- When using Config Patterns with virtual MACs the bandwidth settings are
are intermittently reset after some number of server reboots.

Incremental Interoperability:
- IBM Flex System Fabric SI4093 System Interconnect Module
- IBM Flex System EN6131 40Gb Ethernet Switch
- IBM Flex System x222 10Gb Virtual Fabric LOM
- SLES 11.3 on IBM System x and BladeCenter
- Complete NIC/iSCSI/FCoE support for ASU/Config Patterns for Flex and ASU
for IBM System x & BladeCenter

Known Issues:
- After making changes to any options in the sub-menus under 'controller
configuration' in the Emulex UEFI NIC configuration utility and escaping
to the prior menu, there is no prompt to save the changes. Be sure to
select 'Save' before exiting the configuration menu. Applies to some
legacy rack and blade servers.
- Intermittently, when changing the multichannel mode, the system will not
auto-reboot after exiting F1 UEFI setup and will continue through POST.
Manually reboot the server to ensure all changes are applied. Applies to
some legacy rack and blade servers.
- When using a Cisco Nexus 4001i Switch Module, intermittently the 10Gb link
may come up as 1Gb link speed. An internal switch port bounce will typically
establish a 10Gb link. Setting the switch port speed to fixed 10000 will
also allow a guaranteed 10Gb connection. More info available in the Cisco
Nexus 4001i Switch Module firmware release notes.

===============================================================================

Firmware version: 4.6.166.7
Supported On: IBM System x and BladeCenter

Problems Fixed:
- When connected to Cisco Nexus 4k and 5k switches, the virtual link may not
recover on a switch port bounce (shut/no shut) in an ESXi environment. A
switch port re-bounce will recover the link.
- When connected to Cisco Nexus 4k and 5k switches, OneCommand Manager reports
CRC's and there is poor network performance in an ESXi environment

Incremental Interoperability:
- ASU/Config Pattern configuration for iSCSI and FCoE (BE3)
- UFP for iSCSI (BE3)
- Support for using 10Gb ports with legacy 1Gb switches installed in a
BladeCenter-S chassis or MSIM/MSIM-T expansion units in a BladeCenter-H or
-HT chassis
- Update Express System Packs now support Linux errata kernels
- ESXi 5.1

Known Issues:
- After making changes to any options in the sub-menus under 'controller
configuration' in the Emulex UEFI NIC configuration utility and escaping
to the prior menu, there is no prompt to save the changes. Be sure to
select 'Save' before exiting the configuration menu. Applies to some
legacy rack and blade servers.
- Intermittently, when changing the multichannel mode, the system will not
auto-reboot after exiting F1 UEFI setup and will continue through POST.
Manually reboot the server to ensure all changes are applied. Applies to
some legacy rack and blade servers.
- Server may hang during boot with multichannel disabled with switch default
settings. The IBM 10Gb Virtual Fabric Switch has trunking enabled and the
Brocade Converged 10Gbe Switch Module has ports in "Access" mode. If the
Brocade Converged 10Gbe Switch Module ports are switched to trunking mode,
the hang no longer occurs.
- When using a Cisco Nexus 4001i Switch Module, intermittently the 10Gb link
may come up as 1Gb link speed. An internal switch port bounce will typically
establish a 10Gb link. Setting the switch port speed to fixed 10000 will
also allow a guaranteed 10Gb connection. More info available in the Cisco
Nexus 4001i Switch Module firmware release notes.

===============================================================================

Firmware Version: 4.4.180.3
Supported On: IBM Flex

Problems Fixed:
- 10Gb ports intermittenly linking at 1Gb speed with the IBM Flex System
Fabric EN4093/EN4093R 10Gb Scalable Switch.
- Switch Configuration after an erase configuration is not reflected after
reboot
- 'Logical Admin Link' not enabled after applying BOFM in Switch Agnostic mode
- IBM pre-boot Diagnostics NIC physical loopback test fails in Command and GUI
mode
- Multiple cosmetic issues with iSCSI UEFI BIOS
- 10Gb ports do not detect 'Link Down' with some switches
- When adding an iSCSI hardware target in UEFI through discovery login, the
boot target setting is ignored.

Interoperability since previous release:
- UEFI 2.3.1 Compliance
- Increased VF count in SR-IOV (was 16 VFs per port, is now 32 VFs per port)
- Support for next generation 10GbaseT PHY
- Expose IBM Feature On Demand licensing information in UEFI configuration
utility
- IBM Universal Configuration Manager for Ethernet
- IBM Unified Fabric Protocol
- Ability to assign Switch Agnostic VLAN IDs without intermediate reboot
- Changes to Personality or Multichannel in PXESelect allows further changes
to be made w/o reboot
- Support for IBM Flex System Fabric CN4093 10Gb Converged Scalable Switch

Known Issues:
- HW iSCSI offload is not currently supported in UFP mode

===============================================================================

Firmware Version: 4.1.422.8
Supported On: IBM Flex

Problems Fixed:
- PHY Loopback fails on 10G ports
- RH 6.2 and W2k8 servers crashed after shut/no shut the switch port with FCoE
connection and 50 vlans configured
- DSA: NIC physical loopback test fails in Command and GUI mode
- Firmware update fails to update all VPD Code Level fields
- DCBX does not converge with FW 4.1.422 on Cicso 5k.

Interoperability Since Previous Release:
- Support for IBM Flex System x440 10Gb Virtual Fabric LOM

===============================================================================

Firmware Version: 4.1.422.0
Supported On: IBM Flex

Problems Fixed:
- SR IOV: Unable to ping IPV6 from DUT VF to Peer VF
- Reading VPD from BE3 timesout making SR IOV fail in newer kernels
- 1Gb devices are being suppressed by kernel during the PCI probe in
SLES11 SP2
- MAC Loopback fails when Mgmt Adapter Creation fails
- Failure of MAC loopback test after firmware update and warm reboot
- Suppress efat dump mailbox commands in the efat dump log
- Running ethtool with BE3 takes longer than expected after cable pull
- Out of Order CQEs
- TRACE_LOG function not printing the messages for some of the VF's
- esx4/5 issue. svc target cannot be configured properly
- RSCN is not generated by switch when a driver restarts
- Port Link stays up even after switch removed

Interoperability Since Previous Release:
- Support for IBM Flex System EN4054 4-port 10Gb Ethernet Adapter
- Support for IBM Flex System CN4054 10Gb Virtual Fabric Adapter
- Support for IBM Flex System x240 10Gb Virtual Fabric LOM
- Support for IBM Flex System Manager 10Gb Virtual Fabric LOM

===============================================================================

Firmware Version: 4.2.433.3
Supported On: IBM System x and BladeCenter

Problems Fixed:
- Intermittent link status with IBM Virtual Fabric Switch when set to IBM
Virtual Fabric Mode
- The option to enable/disable SRIOV on HS23 LOM Port 0 is missing from
OneCommand Manager. This selection is available in UEFI F1 setup.
- Under high network stress, NMI errors can be seen with x3690 X5 and x3850 X5
- 10GbE ports running at 1GbE speed 10% below wirespeed at certain block sizes.
- Unable to perform PXE boot with LPVID assigned to vNIC interface
- 1Gb ports of HS23 do not handle tagging properly if multichannel mode
enabled (pnic ok). Note: ESX driver patch also required.
- Port flapping link after FW upgrade and "reboot" when connected to 10Gb PTM
module (DAC)

Interoperability Since Previous Release:
- Support for Emulex Virtual Fabric Adapter Advanced (BE2) for IBM
BladeCenter
- Support for Emulex Virtual Fabric Adapter (BE2) for IBM BladeCenter
- Support for Emulex Virtual Fabric Adapter (BE2) for IBM System X

Known Issues:
- All 10Gb KX4 ports must be used with 10Gb switches. They will not link at
1Gb. This applies to HS23 LOM and IBM BladeCenter VFA adapters only.
- IPv6 IP address not visible via IMM GUI for IBM Option 90Y6456

===============================================================================

Firmware Version: 4.2.412.0
Supported On: IBM System x and BladeCenter

Problems Fixed:
- All VFS on Port 1 on optional Card unreachable from outside the host (x3750
M4)
- 'Logical Admin Link' not enabled after applying BOFM in Switch Agnostic mode
- IBM pre-boot Diagnostics NIC physical loopback test fails in Command and
GUI mode
- Multiple cosmetic issues with iSCSI UEFI BIOS
- 10Gb ports do not detect 'Link Down' with some switches
- 1Gb ports on HS23 LOM not able link up with IBM ICPM (FRU part 44W4486) in
BCS chassis
- Performance issues with specific DAC cables and SND top of rack switch

Interoperability Since Previous Release:
- UEFI 2.3.1 Compliance
- Increased VF count in SR-IOV (was 16 VFs per port, is now 32 VFs per port)
- Support for next generation 10GbaseT PHY
- Expose IBM Feature On Demand licensing information in UEFI configuration
utility

Known Issues:
- All 10Gb ports must be used with 10Gb switches. They will not link at 1Gb.
- IPv6 IP address not visible via IMM GUI for IBM Option 90Y6456
- Intermittent link status with IBM Virtual Fabric Switch when set to IBM
Virtual Fabric Mode
- The option to enable/disable SRIOV on HS23 LOM Port 0 is missing from
OneCommand Manager. This selection is available in UEFI F1 setup.

===============================================================================

Firmware Version: 4.1.455.6
Supported On: IBM System x and BladeCenter

Problems Fixed:
- Fixed an issue where ASIC randomly hangs losing network connectivity
when certain commands are sent from the host. Resulting behavior
varies between OS's (Yellow bangs in Windows, PSOD in VMWare)
- PHY Loopback fails on 10G ports
- UE and hang on LOM or Robalo when powering off Janice in UEFI or PXESelect
- Loopback on HS23 now functional in DSAp
- DCBX does not converge with firmware on a FCoE fabric
- Control C Broken on BE2
- 7 second delay in GET_CARD_ATTRIBUTES command
- Emulex VF adapter FCoE link lost on VMware 5.0
- flow control set for 10G Base T phys for autonegotiation
- Dynamic link update is not working with NIC UEFI driver
- Remove unused definitions in UEFI NIC
- Emulex driver expects that the Login Options field be zero
- "map r" displays a iSCSI BLK device when no LUNs presented
- "X/x Exit without save" does not work as expected
- Display proper description as part of EFI Driver Model Related Information
- Intermittent "Configuration changed. reset to apply it now?"
- Garbled output being displayed at the LUN configuration section.
- All Emulex Configuration settings get lost after a reset
- Perform additional checks when no Luns are mapped to the target
- CHAP name only accepts 6 to 10 characters
- Hii ???iSCSI Initiator Configuration??? showing old version screen
- iSCSI name is case sensitive
- iSCSI HII allows user to select first 8 LUNs as bootable.
- iSCSI Boot Enable/Disable option should be port specific
- LUN Configuration shows LUN 0, even if no LUNs presented to initiator.

Interoperability Since Previous Release:
- Support for Emulex Virtual Fabric Adapter Advanced (CFFh, 2+2) for IBM
BladeCenter

===============================================================================

Firmware Version: 4.1.334.47
Supported On: IBM System x and BladeCenter

Problems Fixed:
- NCSI transmit workaround for IBM
- Issues with data reporting when BOFM enabled
- Improved network performance throughput
- Issues with IBM Management network performance
- Logical link status for IBM mezz card shown as 'N/A'
- Serial Over LAN fails when more than one blade installed with a single
switch
- Removed UEFI menu items for unsupported functions on a port
- Issues with diagnositics in virtual NIC/UMC mode
- Issues with MAC and PHY loopback on OneConnect devices
- Several issues with FCoE on some OEM fabric switches

Interoperability Since Previous Release:
- Support for HS23 Virtual Fabric LAN on Motherboard
- Support for VFA III (95Y3762, 95Y3768), 90Y6456
- Support for IBM's Features on Demand (FOD)
- Formal support for SR-IOV

===============================================================================

Firmware Version: 4.0.1062.0
Supported On: IBM System x and BladeCenter

Problems Fixed:
- iLab Tucson - lpfc Device Resets and path failures continue after error
inject.
- Writes do not complete when running LIP test on BE3 port 2
- IPV6 implementations no longer experience an unrecognized routing type
error.
- VLAN tagging is now disabled on the OneConnect UCNA when multichannel is
disabled.
- UEFI/BIOS-assigned LPVIDs now function properly on the OneConnect
10102-based UCNA.
- OneConnect UCNAs no longer send and receive only double-tagged packets
and discard all other packets.
- PHY, MAC, and External loopback tests no longer fail on all platforms.
- Firmware now returns the proper OneConnect UCNA model number.
- IPV6 implementations no longer experience an unrecognized routing type
error.
- Installing Windows 2008 or Windows 2008 R2 on remote iSCSI disks no
longer causes the system to hang.
- Issues no longer occur when resetting a server configured for multipathing
on VMware ESX systems.
- VLAN tagging is now disabled on the OneConnect UCNA when multichannel is
disabled.
- UEFI/BIOS-assigned LPVIDs now function properly on the OneConnect
10102-based UCNA.
- OneConnect UCNAs no longer send and receive only double-tagged packets and
discard all other packets.
- An adapter hardware error no longer occurs when running I/O with LUNs on
x86 platforms.
- Changing from Convergence Enhanced Ethernet (CEE) to Chassis Internal
Network (CIN) and then rebooting no longer fails to link-flap (CIN Fabric
Login (FLOGI) now occurs).
- PHY, MAC, and External loopback tests no longer fail on all platforms.
- Firmware now returns the proper OneConnect UCNA model number.
- DCB settings can now be configured.
- (iSCSISelect) When enabling DHCP for an iSCSI initiator, the Emulex iSCSI
Network Configuration utility now waits approximately 20 seconds to make a
DHCP connection before returning control.
- (FCoE BootBIOS) FCF CEE parameters for Boot from SAN configuration are now
saved properly.

Interoperability Since Previous Release:
- Added support for switch-independent multichannel mode.
- Added support for IBM Virtual Fabric 10Gb RackSwitch firmware 6.8.1.0.
- Added support for IBM Virtual Fabric 10G Switch Module firmware 6.8.1.0.
- Added support for Fibre Channel over Ethernet (FCoE) on rack systems.
- Added support for iSCSI hardware offload on rack systems.
- Added support for Cisco Nexus 5000-series switches.

===============================================================================

Firmware Version: 2.103.397.3806 (IBM BladeCenter)
Firmware Version: 2.103.269.31 (IBM System x)

- Initial Release

===============================================================================
elx_fw_cna_14a-oc11-10_2_377_29-3_windows_32-64_chg

BladeCenter HS23 UEFI Flash Update
Version 2.00 (Build ID TKE152B)
Change History

Version 2.00 - Build ID: TKE152B - Suggested
--------------------------------
Problem(s) Fixed:
- Fix incorrect Emulex 10GbE VFA II MAC address status after Multichannel mode is disabled in UEFI F1 setup
Enhancements: N/A
Limitations:
- When flashing UEFI from version 1.30 or later to a version earlier
than 1.30, a "Boot Configuration Error" message will be logged into the
UEFI error log. This error does has no impact on the system
configuration or operation. No errors are logged when flashing from an
earlier version to version 1.30 or newer.
Dependencies:
- The IMM firmware must be at BUILDID: 1AOO34Z Version: 1.85
(ibm_fw_imm2_1aoo34z-1.85_anyos_noarch) or higher prior to installing
UEFI version 1.30. If the IMM level is lower, the UEFI update module
will be rejected as invalid because of additional security features
features implemented in this release.

Version 1.90 - Build ID: TKE150B - Critical
--------------------------------
Problem(s) Fixed:
- Fix CVE-2015-1789, CVE-2015-1790, CVE-2015-1792, CVE-2015-1793, CVE-2015-0288 by updating to OpenSSL 1.0.2d
Enhancements: N/A
Limitations:
- When flashing UEFI from version 1.30 or later to a version earlier
than 1.30, a "Boot Configuration Error" message will be logged into the
UEFI error log. This error does has no impact on the system
configuration or operation. No errors are logged when flashing from an
earlier version to version 1.30 or newer.
Dependencies:
- The IMM firmware must be at BUILDID: 1AOO34Z Version: 1.85
(ibm_fw_imm2_1aoo34z-1.85_anyos_noarch) or higher prior to installing
UEFI version 1.30. If the IMM level is lower, the UEFI update module
will be rejected as invalid because of additional security features
features implemented in this release.

Version 1.80 - Build ID: TKE148B
--------------------------------
Problem(s) Fixed:
- Fix CVE-2015-0286, CVE-2015-0287, CVE-2015-0289, CVE-2015-0209, CVE-2015-0288 by updating to OpenSSL 0.9.8zf
Enhancements: N/A
Limitations:
- When flashing UEFI from version 1.30 or later to a version earlier
than 1.30, a "Boot Configuration Error" message will be logged into the
UEFI error log. This error does has no impact on the system
configuration or operation. No errors are logged when flashing from an
earlier version to version 1.30 or newer.
Dependencies:
- The IMM firmware must be at BUILDID: 1AOO34Z Version: 1.85
(ibm_fw_imm2_1aoo34z-1.85_anyos_noarch) or higher prior to installing
UEFI version 1.30. If the IMM level is lower, the UEFI update module
will be rejected as invalid because of additional security features
features implemented in this release.

Version 1.70 - Build ID: TKE146B
--------------------------------
Problem(s) Fixed:
- LGA1:[BLK 6] UCM overwriting configuration changes made via 3rd party utilities
- TPM PCR[5] Changes in unexpected ways, making it unusable
- OemSPD Logic Does not populate OemSPD log if invalid System MT or Serial of 0xFF are found
- OpenSSL update required to close PSIRT security issue Open SSL X-Force
Enhancements:

Limitations:
- When flashing UEFI from version 1.30 or later to a version earlier
than 1.30, a "Boot Configuration Error" message will be logged into the
UEFI error log. This error does has no impact on the system
configuration or operation. No errors are logged when flashing from an
earlier version to version 1.30 or newer.
Dependencies:
- The IMM firmware must be at BUILDID: 1AOO34Z Version: 1.85
(ibm_fw_imm2_1aoo34z-1.85_anyos_noarch) or higher prior to installing
UEFI version 1.30. If the IMM level is lower, the UEFI update module
will be rejected as invalid because of additional security features
features implemented in this release.

Version 1.60 - Build ID: TKEG40Y - Critical
--------------------------------
Problem(s) Fixed:
- Fixed the system boot failure due to low PCI memory-mapped resource for a VGA device
- Incorporated Intel Microcode Update (MCU) MED 306E4_00000427 to address Intel Erratum

Enhancements:
- Enhanced memory SPD logging for Intel E5-2600 v2 processors
- Enhanced error logging for memory-mirroring mode configurations
- Support Memory Reference Code Release version 2.0.0.3
- Support AES enable/disable by ASU
- Enhanced IBM boot manager
- Enhanced TPM Physical Presence lock algorithm

Limitations:
- When flashing UEFI from version 1.30 or later to a version earlier
than 1.30, a "Boot Configuration Error" message will be logged into the
UEFI error log. This error does has no impact on the system
configuration or operation. No errors are logged when flashing from an
earlier version to version 1.30 or newer.
Dependencies:
- The IMM firmware must be at BUILDID: 1AOE34Z Version: 1.85
(ibm_fw_imm2_1aoe34z-1.85_anyos_noarch) or higher prior to installing
UEFI version 1.30. If the IMM level is lower, the UEFI update module
will be rejected as invalid because of additional security features
features implemented in this release.

Version 1.51 - Build ID: TKE136V
--------------------------------
Problem(s) Fixed:
- Refined the warning message when mismatched processor types are installed
- Treat Turbo mode change as a hardware event
- Fix the loss of personality change from iSCSI to FCoE via OCM (Emulex OneCommand Manager)

Enhancements:
- Enhanced memory logging during POST for memory training errors
- Enhanced memory logging for memory fail over events when using memory Mirroring Mode

Limitations:
- When flashing UEFI from version 1.30 or later to a version earlier
than 1.30, a "Boot Configuration Error" message will be logged into the
UEFI error log. This error does has no impact on the system
configuration or operation. No errors are logged when flashing from an
earlier version to version 1.30 or newer.
Dependencies:
- The IMM firmware must be at BUILDID: 1AOO34Z Version: 1.85
(ibm_fw_imm2_1aoo34z-1.85_anyos_noarch) or higher prior to installing
UEFI version 1.30. If the IMM level is lower, the UEFI update module
will be rejected as invalid because of additional security features
features implemented in this release.

Version 1.50 - Build ID: TKE136T
--------------------------------
Problem(s) Fixed:
- Fix CPU frequence lockdown when UEFI recalibrates the power levels during first cold boot
Enhancements:
- Power off the server after N boot attempts without locating a boot device.
- Enable help string scroll when the help text cannot show all at current page.
- Reboot to UEFI setup by using ASU or Windows 2012
- Add notification and recovery option when UEFI detects GPT corruption during POST.
- Variable store self-healing
- Support Intel Xeon processor E5-2600 V2 product family
Limitations:
- When flashing UEFI from version 1.30 or later to a version earlier
than 1.30, a "Boot Configuration Error" message will be logged into the
UEFI error log. This error does has no impact on the system
configuration or operation. No errors are logged when flashing from an
earlier version to version 1.30 or newer.
Dependencies:
- The IMM firmware must be at BUILDID: 1AOO34Z Version: 1.85
(ibm_fw_imm2_1aoo34z-1.85_anyos_noarch) or higher prior to installing
UEFI version 1.30. If the IMM level is lower, the UEFI update module
will be rejected as invalid because of additional security features
features implemented in this release.

Version 1.42 - Build ID: TKE130D
--------------------------------
Problem(s) Fixed:
- Added code workaround for VRD master soft shutdown issue
Enhancements:
- None
Limitations:
- When flashing UEFI from version 1.30 or later to a version earlier
than 1.30, a "Boot Configuration Error" message will be logged into the
UEFI error log. This error does has no impact on the system
configuration or operation. No errors are logged when flashing from an
earlier version to version 1.30 or newer.
Dependencies:
- The IMM firmware must be at BUILDID: 1AOO34Z Version: 1.85
(ibm_fw_imm2_1aoo34z-1.85_anyos_noarch) or higher prior to installing
UEFI version 1.30. If the IMM level is lower, the UEFI update module
will be rejected as invalid because of additional security features
features implemented in this release.

Version 1.41 - Build ID: TKE130C
--------------------------------
Problem(s) Fixed:
- Incorporated Microcode Update (MCU) M6D206D7_00000710 to address Intel Erratum
BT248 for System Resets with 32-bit (PAE Enabled) Guest OS and VT FlexPriority
enabled. For more information, refer to IBM RETAIN Tip H21370.
Enhancements:
- None
Limitations:
- When flashing UEFI from version 1.30 or later to a version earlier
than 1.30, a "Boot Configuration Error" message will be logged into the
UEFI error log. This error does has no impact on the system
configuration or operation. No errors are logged when flashing from an
earlier version to version 1.30 or newer.
Dependencies:
- The IMM firmware must be at BUILDID: 1AOO34Z Version: 1.85
(ibm_fw_imm2_1aoo34z-1.85_anyos_noarch) or higher prior to installing
UEFI version 1.30. If the IMM level is lower, the UEFI update module
will be rejected as invalid because of additional security features
features implemented in this release.

Version 1.40 - Build ID: TKE128R
--------------------------------
Problem(s) Fixed:
- Improved handling of missing values for iSCSI initiator name
- Corrected handling of pre-boot serial port redirection settings
- Corrected garbled SOL output strings during early phases of UEFI booting
- Clarified actions required to effect changes to Trusted Platform Module (TPM) setup
- Corrected failure to load some default settings on CMOS battery failure
- Improved wording for progress codes and messages
- Corrected the order in which UEFI configures Ethernet ports
- Improved handling of USB configuration changes
- Corrected boot configuration problem
Enhancements:
- Updated DMI Type 17 support for for new memory devices
- Improved support for 32GB memory
- Improved general Reliability/Availability/Serviceability support
- Added ability to resize PCIE IO base address registers dynamically
- Improved handling of memory in high stress application/usage
- Added ACPI Firmware First logging support
- Added setup capability to select PCIE Config Base below 4GB
- Added informational messages when exiting UEFI F1 Setup
Limitations:
- When flashing UEFI from version 1.30 or later to a version earlier
than 1.30, a "Boot Configuration Error" message will be logged into the
UEFI error log. This error does has no impact on the system
configuration or operation. No errors are logged when flashing from an
earlier version to version 1.30 or newer.
Dependencies:
- The IMM firmware must be at BUILDID: 1AOO34Z Version: 1.85
(ibm_fw_imm2_1aoo34z-1.85_anyos_noarch) or higher prior to installing
UEFI version 1.30. If the IMM level is lower, the UEFI update module
will be rejected as invalid because of additional security features
features implemented in this release.

Version 1.32 - Build ID: TKE124P
--------------------------------
Problem(s) Fixed:
Enhancements:
- Improve the reliability of the CPU and/or memory VRDs. This improvement
lowers the occurrence of CPU & memory VRD failures.
Limitations:
- When flashing UEFI from version 1.30 or later to a version earlier
than 1.30, a "Boot Configuration Error" message will be logged into the
UEFI error log. This error does has no impact on the system
configuration or operation. No errors are logged when flashing from an
earlier version to version 1.30 or newer.
Dependencies:
- The IMM firmware must be at BUILDID: 1AOO34Z Version: 1.85
(ibm_fw_imm2_1aoo34z-1.85_anyos_noarch) or higher prior to installing
UEFI version 1.30. If the IMM level is lower, the UEFI update module
will be rejected as invalid because of additional security features
features implemented in this release.

Version 1.31 - Build ID: TKE124O
--------------------------------
Problem(s) Fixed:
Enhancements:
- Improved fan speed algorithm to reduce acoustic noise for high-power
processors
Limitations:
- When flashing UEFI from version 1.30 or later to a version earlier
than 1.30, a "Boot Configuration Error" message will be logged into the
UEFI error log. This error does has no impact on the system
configuration or operation. No errors are logged when flashing from an
earlier version to version 1.30 or newer.
Dependencies:
- The IMM firmware must be at BUILDID: 1AOO34Z Version: 1.85
(ibm_fw_imm2_1aoo34z-1.85_anyos_noarch) or higher prior to installing
UEFI version 1.30. If the IMM level is lower, the UEFI update module
will be rejected as invalid because of additional security features
features implemented in this release.

Version 1.30 - Build ID: TKE124M
--------------------------------
Problem(s) Fixed:
- Corrected BOFM Configuration errors
- Corrected iSCSI setup/configuration problems
- Corrected SMBIOS table entry problems
- Corrected memory error handling problems
- Corrected FOD state transition problems
- Corrected ACPI problems
- Corrected I/O problems
- Corrected Security errors
- Corrected Configuration errors
- Corrected errors in Setup operations
- Corrected RAS problems
Enhancements:
- Add support for ACPI S3 state
- Add support for automatic ROM recovery
- Add support for dynamic debug capability
- Improve Update Security
- Improve Configuration Support
- Add common support for OS-4690
Limitations:
- When flashing UEFI from version 1.30 or later to a version earlier
than 1.30, a "Boot Configuration Error" message will be logged into the
UEFI error log. This error does has no impact on the system
configuration or operation. No errors are logged when flashing from an
earlier version to version 1.30 or newer.
Dependencies:
- The IMM firmware must be at BUILDID: 1AOO34Z Version: 1.85
(ibm_fw_imm2_1aoo34z-1.85_anyos_noarch) or higher prior to installing
UEFI version 1.30. If the IMM level is lower, the UEFI update module
will be rejected as invalid because of additional security features
features implemented in this release.

Version 1.21 - Build ID: TKE120M
--------------------------------
Problem(s) Fixed:
- BOFM Cfg error with no BOFM license installed
Enhancements:
Limitations:
Dependencies:

Version 1.20 - Build ID: TKE120A
--------------------------------
Problem(s) Fixed:
- Further updates to the fatal error handler to report QPI errors during
runtime
- [AS] Disable device of BPE4 and BGE4 is useless.
- [Q2ESW]_iSCSI Attempt will disapper when system reboot several times.
- Fails to report logging limit errors on spared DIMM
- Remove unnecessary warm reset
- Changing IMM settings After Resetting IMM to Defaults Requires
- Intel SPS ME FW Hotfix 11 [02.01.05.095] operational image for
- Properly update property "PXE.NicPortPxeProtocol" when updated remotely
Enhancements:
- Support the Trusted Computing Group's Memory Overwrite Request function
- Improve PCIe Slot# for WidgetGetDeviceLocation procedure
- Improve messages while booting up
- Update PXE DHCP to support Option 43
- Update LOGO for generic OEM versions
Limitations:
Dependencies:

Version 1.10 - Build ID: TKE116O
--------------------------------
Problem(s) Fixed:
- Removed extraneous characters that displayed on the serial console
redirection when the UEFI splash screen appears
- Updated the fatal error handler to correctly report:
- multi-bit errors when mirroring mode is enabled
- multi-bit errors on spared DIMMs during runtime
- QPI errors during runtime
- Fixed issue that caused the ASU tool to occasionally fail to update the
Processors.CoresinCPUPackage value
- Provided more descriptive messages for severity of warnings vs errors
- Fixed issue where removing an OS-created boot option using the ASU tool
or SNMP caused that boot option to be lost until the OS re-creates it
- Fixed issue that caused remote mounted USB keys to not appear in the
UEFI Boot From Device menu
- Fixed issue where Emulex UEFI FCoE LOM utility hangs in "Change Boot
Device Order" menu
- Resolved resource issue that caused one port of a CIOv card to not be
configured when 4 BGE expansions and a CFFh card were also installed
- Fixed issue that caused media tray USB ports to not appear when the AMM
in slot 2 was active
- Updated BPE4 fault path that caused incorrectly reported PCIe errors
- Fixed issue to allow PXE/iSCSI to be configured out-of-band
- Fixed several issues with BOFM interaction between LOM and CFFh cards
- Fixed Serial-Over-LAN issues
Enhancements:
- Added support for using Features On Demand with Optimized Boot enabled
- Updated thermal threshold values for DIMMs
Limitations:
Dependencies:

Version 1.02 - Build ID: TKE112P
-------------------------------------------------
Problem(s) Fixed:
- Fixed issue where AMM HW VPD was not showing WWN for the LOM and the
Robalo card in FCoE personality
Enhancements:
Limitations:
Dependencies:

Version 1.01 - Build ID: TKE112N
-------------------------------------------------
Problem(s) Fixed:
Enhancements:
- Enable field upgrade of Trusted Platform Module (TPM) firmware on parts
that are capable of field upgrade.
Limitations:
Dependencies:

Version 1.00 - Build ID: TKE112K (Initial Release)
-------------------------------------------------
Problem(s) Fixed:
Enhancements:
Limitations:
Dependencies:

ibm_fw_uefi_tke152b-2_00_anyos_32-64_chg

===============================================================================
Emulex FC Device Driver for Windows
===============================================================================

Device Driver Version: 10.2.370.8
Supported On: System x, BladeCenter and Flex

Problems Fixed:
- None

Incremental Interoperability
- Grantley based ITE

Known Issues:
- None

===============================================================================

Device Driver Version: 10.2.370.8
Supported On: System x and BladeCenter

Problems Fixed:
- Failed to enumerate target after zoning change
- UEFI FCoE SANboot Failed with specific targets

Incremental Interoperability
- Grantley Rack Servers

Known Issues:
- None

===============================================================================

Device Driver Version: 10.2.261.4
Supported On: IBM System x, BladeCenter, and Flex

Problems Fixed:
- ABTS sent by tape device ignored by HBA
- BSOD issue during CPU Hot replace test
- XE102/XE104 - OCManager reports link down on both ports

Incremental Interoperability:
- Crosslink & Express Lane on LPe16k based solutions

Known Issues:
- None

===============================================================================

Device Driver Version: 10.0.720.0
Supported On: IBM System x

Problems Fixed:
- Concurrent Hardware and Operating System (CHAOS) Test fails in XE-10x 10G
- Extloopback command not supported with LPe16000 adapters with 16Gb link speed
- Windows FC driver bug with Data Domain virtual tape library

Incremental Interoperability:
- Emulex Dual port 10Gb SFP+ Ethernet Adapter Card (XE-102/XE-104 based)

Known Issues:
- None

===============================================================================

Device Driver Version: 2.74.016.001
Supported On: IBM System x, BladeCenter, and Flex

Problems Fixed:
- Cleaned up a variety of corner case issues to avoid BSODs
- Fixed IOCTL encounter bug-chk on BE3 during NPIV tests
- Fixed reporting incorrect error code when creating vport on a switch without
NPIV supported
- Updated the default model name for 16G HBAs

Incremental Interoperability:
- None

Known Issues:
- None

===============================================================================

Device Driver Version: 2.74.014.001
Supported On: IBM System x and BladeCenter

Problems Fixed:
- None

Incremental Interoperability:
- PCI-IDs added for XE4310R controller applications

Known Issues:
- No known issues

===============================================================================

Device Driver version: 2.74.009.001
Supported On: IBM System x, BladeCenter, and Flex

Problems Fixed:
- Clean up non-critical legacy FC and uCNA incompatibilities
- LUN masking doesn't persist after reboot
- Emulex GUI crashes when closing a running Upgrade utility and re-open it in
802.3 configuration with IP or MAC
- Several bugs related to creation or deletion of vports

Incremental Interoperability:
- Windows 2012
- Improved debug capabilities
- Tighter integration with MS Windows Design Kit

Known Issues:
- None

===============================================================================

Device Driver Version: 2.70.018
Supported On: IBM System x, BladeCenter, and Flex

Problems Fixed:
- Fixed sending ABTS continuously to Flogi issue
- Fixed reset and link bounce issues for SLI4 FC public loop
- Added support for ABTS timeout handling for both SLI3 and SLI4
- Fixed loopback test incorrectly dropping the loopback frame in SLI4
- Fixed exchange management issue in SLI4 CT receive path causing array
overflow
- Fixed firmware version update issue following download in link up state
- Fixed problem in init_vfi completion handler that stalled fabric login on BE
FCoE FW
- Fixed problem that caused OCM ELS Echo Test to fail
- Fixed the loopback test issue in recovering from error condition
- Add persistent link down support for SLI4 FC
- Fix DFC_IssueDumpMBox to manage request type 3 which includes link select
option
- Modified reinitialization sequence following reset to fix discovery failure
post type 1 or type 3 reset
- Fixed new firmware dump issue

===============================================================================

Device Driver Version: 2.41.002
Supported On: IBM System x and BladeCenter

- Initial Release

===============================================================================
elx_dd_fc_14a-10_2_370_8-3_windows_32-64_chg

QLogic Driver Release Notes

QLogic Corporation
All rights reserved

Table of Contents

1. Change History
2. Known Issues
3. Notices
4. Contacting Support


1. Change History

The following changes have been made to the Converged Network
Adapter STOR miniport driver between versions 9.1.11.12 and 9.1.11.16.

* [ER132969]: Unable to create virtual SAN from Hyper-v
Resolution: Fixed Win2012 compilation issue
Scope : All FCoE Adapters
* [ER131634]: Lost path caused by timeout abort shortly after certain command sent
Resolution: Fixed command timeout value adjustment issue to avoid sending abort too early
Scope : 8200 Series Adapters
* API version 1.28.0.112 (QLSDM)
* [ER115248]: Read NVRAM fails after write
Resolution: Added delay between write and read in api
Scope : 8200 Series Adapters
* [ER114713]: Poor read write performance at certain large block sizes
Resolution: Fixed delay in handling SRB queue
Scope : 8300 Series Adapters
* [ER116206]: FCoE driver does not capture minidump after three peg halts
Resolution: Reset firmware dump limit counter on firmware dump retrieval
Scope : All FCOE Adapters
* [ER116177]: Win2k12 R2 crashes during SNAP6 online update with baseline added.
Resolution: Fixed certain IOCTL pass-through command sense data pointer on W12 extended Srb
Scope : 8200 Series Adapters
* [ER131902]: FDMI-2 support
Resolution: Added FDMI-2 support
Scope : 8300 Series Adapters
* [ER113510]: Maximum number of GNNFT entries is limited to 128
Scope : All Adapters
Resolution: Increased maximum number of GNNFT entries
* [ER113482]: Failover on EMC storage not working when zoning is deactivated on switch
Resolution: Fixed for not relogin after timeout
* [ER111553]: Failed to push driver version in OCBB space
Scope : 8200 Series Adapter
Resolution: Skipped issuing get param mbx
* [ER114741]: Login to tape device times out
Scope : All FC and FCOE Adapter
Resolution: Retry Relogin once


Change History
*****************************************************************************************
Version 9.1.11.12

* API version 1.28.0.111 (QLSDM)
* [ER110756]: Incorrect sense data debug message during certain check condition status response
Scope : All FCOE Adapters
Resolution: Fixed debug message output with data based on sense error code
* [ER108790]: FCoE Internal Loopback does not complete
Scope : 8300 Series adapter
Resolution: Wait for IDC to complete loopback ioctl
* [ER111292]: Incorrect CDB pointer type used on Windows Server 2012 extended SRB
Resolution: Fixed CDB pointer type declaration for extended SRB
* [ER111432]: Unable to create Vports when Microsoft vFC's are existing
Scope : All FCOE Adapters
Resolution: Check the active VP count in the first half of VP database
* [ER111645]: Update nvram fails read-back verify
Scope : 8200 Series adapter
Resolution: Added delay before read in QLSDM


Version 9.1.11.11

* API version 1.28.0.110 (QLSDM)
* HotFwLoad is no longer supported because it causes whql chaos failure witb mb error [ER109340]
* Added support for user configurability of maximum number of NPIVs per adapter port [ER 109407]
* Fixed issue with device init timeout value on 8200 Series adapter [ER108082]
* Added device state check before hardware access for 8200 Series adapter [ER107969]
* Added 8200 Series adapter IO timeout handling for pass-through command [ER107784]
* Fixed number of IOCB entries required for large transfer [ER107785]
* Added more registry changes to set number of vps and number of targets per vp [ER107100]
* Enabled force fw dump support in api [ER107301]
* Fixed io completion and blocking issue during quiscent state for 8200 Series adapter [ER107135]
* Fixed io completion issue on reset failure for 8200 Series adapter [ER107148]
* Fixed rom lock issue during firmware minidump for 8200 Series adapter [ER107368]
* Removed invalid mailbox command error detection for 8200 Series adapter [ER107368]
* Change OCBB implementation to use mailbox register method for 8200 Series adapter [ER106341]
* Added delay before writing flash sector to address flash corruption [ER106427]
* Added delay before reset to address firmware hang [ER106427]
* Added registry strings to set number of vps and number of targets per vp [ER107100]
* Fixed empty firmware image version due to 8200 Series adapter (based on latest controller revision) not regconized by driver [ER105290]
* Fixed unpack macro warning in QLSDM [ER105492]
* Fixed VP creation failure because of dup wwpn in the switch [bug 25373]
* Added support in qlsdm to support new name of inbox driver [ER105740]
* Added support for Long Range [ER0000000110404]


Version 9.1.11.10

* API version 1.28.0.106 (QLSDM)
* Fixed beaconing for 8300 Series adapter according to the new firmware spec [ER101442]
* Added api to read Hilda ASIC temperature [ER102430]
* Added mailbox passthru api [ER102988]
* Added reading ASIC temperature for Ninja and Sensei [ER103001]
* Allow application modify "Execution Throttle" field in nvram for 8300 series adapters [ER103297]
* Add Service Pack number to OSName [ER104204]
* Removed Advanced tab from Device Manager properties
* Fix MailboxPassthru by removing restriction on writing mbx8 register [ER104361]


Version 9.1.10.17

* API version 1.28.0.101 (QLSDM)
* Added 8300 series Adapter temperature handling [ER94159]
* Added support for 8300 series Adapter (IDC, minidumps (as applicable), loopback, MCTP, mngt api) [ER92242]
* Driver needs to determine, depending on the config,
if it needs to send echo or external (8300 series Adapter FCoE) loopback command[ER94711]
* Added 8300 series Adapter FCoE IDC driver presence bit support [ER95252]
* Added 8300 series Adapter FCoE IDC driver reset/quiescent ack support [ER95250]
* Returned NOT_SUPPORTED for SDForceFcMctpDump in api [ER96352]
* Removed unnecessary mailbox retry on 8300 series Adapter NIC init state [ER96652]
* Added adapter disable check on timer routine re-init state handling [ER96662]
* Fixed NIC init state issue on 8300 series Adapter NIC Firmware State Change AEN [ER97159]
* Fixed BSOD running FCoE Internal loopback when mailbox set config fails [ER97406]
* Changed 8300 series Adapter FCoE NIC init state handling on 0x8200 AEN [ER97159 ]
* Added registry to control IO timeout event log/sense data report for Win12 [ER98501]
* Ported MPS patch from 8100 to 8300 series Adapter to fix BFS win12 installation BSOD [ER96750]
* Removed event logging for fw dump event [ER98897]
* Limit MSI-X resources to 2 for P3P [ER97967]
* Use macros to access SRB and SRB_EXT for W12 [ER097387][ER98974]
* Fixed crash in fwdump routine when 8100 series Adapter dumps fwdump [ER101039]
* Fixed api to reload firmware on second port after firmware is flashed on first port for 8100 series Adapter [ER101118]


Version 9.1.10.16

* API version 1.28.0.97 (QLSDM)
* Fixed extra 4K in variable transfer sizes (64K, 128K) [ER94081]
* Fixed memory access error [part of ER96188]
* Added support to relogin if the device logs out [ER93867]


Version 9.1.10.15

* Added Windows Server 2012 support [ER92249]
* Fixed Flash Layout Table memory usage [ER93668]
* API version 1.28.0.96 (QLSDM)
* Add SDGetHbaDeviceNodePropertyResync in QLSDM [ER92842]
* Add cached FLT support [ER93468]
* FCoE driver doesn't refresh FW versions when flash is
updated through NIC on 82xx [ER85860]
* Code cleanup [ER92250]
* Added support for Set Driver version for OCBB and family
driver version [ER92243]
* Issue with LB connector attached after it was in point-to-point mode,
driver was still issuing echo instead of loopback command [ER93050]
* Fixed Adapter Port type in P2P mode [ER92357]
* Process completed PRLI [ER89053]
* Fixed multiple request single response queue initialization issue [ER95259]
* P3+ Minidump buffer pointer issue [ER95253]
* FCoE driver doesn't refresh FW versions when flash is
updated through NIC on 82xx [ER91115]


Version 9.1.9.39

* Let NIC driver perform reset if NIC driver is present
* FCoE driver stuck in DPC for too long causing
assertion during peghalt testing [ER89373]
* Updating Qlogic Firmware gives Read only
Filesystem Error [ER86864]


Version 9.1.9.38

* Addressed issue related to peg halt tests


Version 9.1.9.37

* System unresponsive after FW hang [ER85860]
* API version 1.28.0.90 (QLSDM)


Version 9.1.9.36

* Log halt events and event 800267xy for ipe
* Default to disable minidump
* Improved sem5 polling for reset
* QCC CLI hung after making personality change on QLE8242 [ER83352]
* Cleaned up accumulated io completion properly when link down
occurs
* CNA 81xx can not load the driver after hot plug in OEM system
[ER83352]
* Assertion failures and system hang when peg halt is done in loop
with NIC and FCoE driver running. [ER83352]
* API version 1.28.0.90 (QLSDM)


Version 9.1.9.19

* Added support and retry logic code to track down io failure during
link down.


Version 9.1.9.18

* Made compatible with OEM DSM that handles only path failure
by deferring io error when link/port down timeout exceeds.


Version 9.1.9.17

* Added new cold reset when loaded before nic driver during IBFT.
* Synchronized vp's rscn handling with vp 0.

Version 9.1.9.16

* Target discovery not completed within port down timeout would
cause driver to logout the first discovered target. [ER78315]
* Target discovery was initiated prior to firmware ready. [ER78316]
* The firmware version in QCC is not updated correctly after
flashing using NIC interface. [ER78827]
* API version 1.28.0.83 (QLSDM)
* Firmware v5.04.04


Version 9.1.9.15

* Added support for the 82xx family of Converged Network Adapters
* API version 1.28.0.80 (QLSDM)
* Firmware v5.04.01


Version 9.1.8.27

* Degraded write performance with large file and Windows Server
2008 R2 file system [ER71241]
* API version 1.28.0.73 (QLSDM)
* Firmware v5.03.02


Version 9.1.8.26

* Added LR Converged Network Adapter Adapter support (QLE81xx)
* Updated embedded firmware to v5.3.2 (QLE8042)
* Addressed virtual link down issue reported by HDS (ER68836)
* API version 1.28.0.73 (QLSDM)
* Firmware v5.03.02


Version 9.1.8.19

* System freezes after active BNT CEE switch is rebooted
* Adapter management utility fails to delete Virtual ports
* API version 1.28.0.73 (QLSDM)
* Firmware v5.02.01


Version 9.1.8.17

* API version 1.28.0.73 (QLSDM)
* Firmware v5.01.03


2. Known Issues

None


3. Notices

Information furnished in this document is believed to be accurate and
reliable. However, QLogic Corporation assumes no responsibility for
its use, nor for any infringements of patents or other rights of
third parties which may result from its use. QLogic Corporation
reserves the right to change product specifications at any time
without notice. Applications described in this document for any of
these products are only for illustrative purposes. QLogic Corporation
makes no representation nor warranty that such applications are
suitable for the specified use without further testing or
modification. QLogic Corporation assumes no responsibility for any
errors that may appear in this document.


4. Contacting Support

For further assistance, contact QLogic Technical Support at:
http://support.qlogic.com


Trademarks

Accelera, Accelerating Cluster Performance, InfiniCon Systems,
InfiniNIC, InfiniPath, InfiniView, QLA, QLogic, the QLogic logo,
ReadyPath, SANdoctor, SANsurfer, and SilverStorm are registered
trademarks of QLogic Corporation. All other brand and product names
are trademarks or registered trademarks of their respective owners.


(c) Copyright 2014. All rights reserved worldwide. QLogic and the
QLogic logo are registered trademarks of QLogic Corporation.
All other brand and product names are trademarks or registered
trademarks of their respective owners.
qlgc_dd_fc_cna-9_1_11_16_windows_32-64_chg

Broadcom Firmware Update Utility for IBM servers and options using the Broadcom
NetXtreme and NetXtreme II ethernet adapter.

Version 2.3.1e, March 06, 2014



This package updates the Broadcom firmware for the following items:

NetXtreme Servers/Workstations
Product Previous Release Current Release Change History File
---------------------------------------------------------------------
1879 Boot code 3.29a Boot code 3.65 BCM5721.chg
IPMI code 6.08 IPMI code 6.25 IPMI-BCM5721.chg

1880 Boot code 3.29a Boot code 3.65 BCM5721.chg
IPMI code 6.08 IPMI code 6.25 IPMI-BCM5721.chg

1883 Boot code 3.21 Boot code 3.38 BCM5704s.chg
IPMI code 2.28 IPMI code 2.49 IPMI-BCM5704_5704s.chg

1884 Boot code 3.38 Boot code 3.38 BCM5704s.chg
IPMI code 2.42 IPMI code 2.49 IPMI-BCM5704_5704s.chg

1887 Boot code 3.49 Boot code 3.65 BCM5721.chg
IPMI code 6.14 IPMI code 6.25 IPMI-BCM5721.chg

1916 Boot code 3.29 Boot code 3.29 BCM5714s.chg
IPMI code 6.21 IPMI code 6.24 IPMI-BCM5780_5780s_5714s_5715s.chg
UMP code 1.21 UMP code 1.21 UMP-BCM5714s.chg

4190 Boot code 3.09 Boot code 3.09 BCM5722.chg
IPMI code 6.03 IPMI code 6.03 IPMI-BCM5722.chg
Boot code 2.43 Boot code 2.43 BCM5703.chg

4191 Boot code 3.09 Boot code 3.09 BCM5722.chg
IPMI code 6.03 IPMI code 6.03 IPMI-BCM5722.chg
Boot code 2.43 Boot code 2.43 BCM5703.chg

4192 Boot code 3.09 Boot code 3.09 BCM5722.chg
IPMI code 6.03 IPMI code 6.03 IPMI-BCM5722.chg

4193 Boot code 3.09 Boot code 3.09 BCM5722.chg
IPMI code 6.03 IPMI code 6.03 IPMI-BCM5722.chg

4194 Boot code 3.09 Boot code 3.09 BCM5722.chg
IPMI code 6.03 IPMI code 6.03 IPMI-BCM5722.chg
Boot code 2.43 Boot code 2.43 BCM5703.chg

4347 Boot code 3.61 Boot code 3.65 BCM5721.chg

4348 Boot code 3.61 Boot code 3.65 BCM5721.chg

4362 Boot code 3.61 Boot code 3.65 BCM5721.chg
IPMI code 6.20 IPMI code 6.25 IPMI-BCM5721.chg

4363 Boot code 3.61 Boot code 3.65 BCM5721.chg
IPMI code 6.20 IPMI code 6.25 IPMI-BCM5721.chg

4364 Boot code 3.61 Boot code 3.65 BCM5721.chg
IPMI code 6.20 IPMI code 6.25 IPMI-BCM5721.chg

4365 Boot code 3.61 Boot code 3.65 BCM5721.chg
IPMI code 6.20 IPMI code 6.25 IPMI-BCM5721.chg

4366 Boot code 3.61 Boot code 3.65 BCM5721.chg
IPMI code 6.20 IPMI code 6.25 IPMI-BCM5721.chg

4367 Boot code 3.09 Boot code 3.09 BCM5722.chg
IPMI code 6.03 IPMI code 6.03 IPMI-BCM5722.chg

4368 Boot code 3.09 Boot code 3.09 BCM5722.chg
IPMI code 6.03 IPMI code 6.03 IPMI-BCM5722.chg

6216 Boot code 2.28 Boot code 2.43 BCM5702.chg
ASF code 2.02I ASF code 2.02I ASF1.chg

6217 Boot code 2.35 Boot code 2.43 BCM5703.chg
ASF code 2.02I ASF code 2.02I ASF1.chg

6218 Boot code 3.40 Boot code 3.65 BCM5721.chg
ASF code 6.26 ASF code 7.20 ASF2.chg

6219 Boot code 2.28 Boot code 2.43 BCM5702.chg
ASF code 2.02I ASF code 2.02I ASF1.chg

6221 Boot code 2.25 Boot code 2.43 BCM5703.chg
ASF code 2.02I ASF code 2.02I ASF1.chg

6223 Boot code 3.40 Boot code 3.65 BCM5721.chg
ASF code 6.22 ASF code 7.20 ASF2.chg

6224 Boot code 2.25 Boot code 2.43 BCM5703.chg
ASF code 2.02I ASF code 2.02I ASF1.chg

6225 Boot code 3.40 Boot code 3.65 BCM5721.chg
ASF code 6.22 ASF code 7.20 ASF2.chg

6226 Boot code 2.28 Boot code 2.43 BCM5702.chg
ASF code 2.02I ASF code 2.02I ASF1.chg

6227 Boot code 3.40 Boot code 3.65 BCM5721.chg
ASF code 6.22 ASF code 7.20 ASF2.chg

6228 Boot code 3.40 Boot code 3.65 BCM5721.chg
ASF code 6.22 ASF code 7.20 ASF2.chg

6388 Boot code 3.09 Boot code 3.09 BCM5722.chg
IPMI code 6.03 IPMI code 6.03 IPMI-BCM5722.chg

7362 Boot code 3.41 Boot code 3.41 BCM5704.chg
IPMI code 2.45 IPMI code 2.49 IPMI-BCM5704_5704s.chg

7364 Boot code 3.41 Boot code 3.41 BCM5704.chg
IPMI code 2.45 IPMI code 2.49 IPMI-BCM5704_5704s.chg

7365 Boot code 3.41 Boot code 3.41 BCM5704.chg
IPMI code 2.45 IPMI code 2.49 IPMI-BCM5704_5704s.chg

7367 Boot code 3.41 Boot code 3.41 BCM5704.chg
IPMI code 2.45 IPMI code 2.49 IPMI-BCM5704_5704s.chg

7942 Boot code 3.09 Boot code 3.09 BCM5722.chg
IPMI code 6.03 IPMI code 6.03 IPMI-BCM5722.chg

7969 Boot code 3.13 Boot code 3.29 BCM5780.chg
IPMI code 6.06 IPMI code 6.21 IPMI-BCM5780_5780s_5714s_5715s.chg

7973 Boot code 3.56 Boot code 3.65 BCM5721.chg
IPMI code 6.17 IPMI code 6.25 IPMI-BCM5721.chg

7974 Boot code 3.56 Boot code 3.65 BCM5721.chg
IPMI code 6.17 IPMI code 6.25 IPMI-BCM5721.chg

7975 Boot code 3.56 Boot code 3.65 BCM5721.chg
IPMI code 6.17 IPMI code 6.25 IPMI-BCM5721.chg

7976 Boot code 3.56 Boot code 3.65 BCM5721.chg
IPMI code 6.17 IPMI code 6.25 IPMI-BCM5721.chg

7977 Boot code 3.56 Boot code 3.65 BCM5721.chg
IPMI code 6.17 IPMI code 6.25 IPMI-BCM5721.chg

7981 Boot code 3.38 Boot code 3.38 BCM5704s.chg
IPMI code 2.42 IPMI code 2.49 IPMI-BCM5704_5704s.chg

7984 Boot code 3.41 Boot code 3.41 BCM5704.chg
IPMI code 2.45 IPMI code 2.49 IPMI-BCM5704_5704s.chg

7986 Boot code 3.41 Boot code 3.41 BCM5704.chg
IPMI code 2.45 IPMI code 2.49 IPMI-BCM5704_5704s.chg

7992 Boot code 3.13 Boot code 3.29 BCM5780.chg
IPMI code 6.06 IPMI code 6.21 IPMI-BCM5780_5780s_5714s_5715s.chg

8014 Boot code 3.29 Boot code 3.29 BCM5714s.chg
IPMI code 6.21 IPMI code 6.24 IPMI-BCM5780_5780s_5714s_5715s.chg
UMP code 1.21 UMP code 1.21 UMP-BCM5714s.chg

8028 Boot code 3.29 Boot code 3.29 BCM5714s.chg
IPMI code 6.21 IPMI code 6.24 IPMI-BCM5780_5780s_5714s_5715s.chg
UMP code 1.21 UMP code 1.21 UMP-BCM5714s.chg

8480 Boot code 2.28 Boot code 2.43 BCM5702.chg
ASF code 2.02I ASF code 2.02I ASF1.chg

8485 Boot code 3.49 Boot code 3.65 BCM5721.chg
IPMI code 6.14 IPMI code 6.25 IPMI-BCM5721.chg

8486 Boot code 3.49 Boot code 3.65 BCM5721.chg

8488 Boot code 3.40 Boot code 3.65 BCM5721.chg
ASF code 6.22 ASF code 7.20 ASF2.chg

8490 Boot code 3.49 Boot code 3.65 BCM5721.chg
IPMI code 6.14 IPMI code 6.25 IPMI-BCM5721.chg

8491 Boot code 3.49 Boot code 3.65 BCM5721.chg
IPMI code 6.14 IPMI code 6.25 IPMI-BCM5721.chg

8647 Boot code 2.25 Boot code 2.43 BCM5703.chg
ASF code 2.02I ASF code 2.02I ASF1.chg

8648 Boot code 3.40 Boot code 3.65 BCM5721.chg
ASF code 6.22 ASF code 7.20 ASF2.chg

8649 Boot code 2.25 Boot code 2.43 BCM5703.chg
ASF code 2.02I ASF code 2.02I ASF1.chg

8671 Boot code 2.25 Boot code 2.43 BCM5703.chg
ASF code 2.02I ASF code 2.02I ASF1.chg

8673 Boot code 2.25 Boot code 2.43 BCM5703.chg
ASF code 2.02I ASF code 2.02I ASF1.chg

8676 Boot code 2.25 Boot code 2.43 BCM5703.chg
ASF code 2.02I ASF code 2.02I ASF1.chg

8678 Boot code 2.30 Boot code 2.43 BCM5703s.chg
ASF code 2.02I ASF code 2.02I ASF1.chg

8685 Boot code 2.25 Boot code 2.43 BCM5703.chg
ASF code 2.02I ASF code 2.02I ASF1.chg

8687 Boot code 2.14 Boot code 2.16 BCM5700.chg

8830 Boot code 2.25 Boot code 2.43 BCM5703.chg
ASF code 2.02I ASF code 2.02I ASF1.chg

8832 Boot code 3.21 Boot code 3.38 BCM5704s.chg
IPMI code 2.20 IPMI code 2.49 IPMI-BCM5704_5704s.chg

8835 Boot code 3.19 Boot code 3.41 BCM5704.chg
IPMI code 2.16 IPMI code 2.49 IPMI-BCM5704_5704s.chg

8837 Boot code 3.29a Boot code 3.65 BCM5721.chg
IPMI code 6.08 IPMI code 6.25 IPMI-BCM5721.chg

8840 Boot code 3.29a Boot code 3.65 BCM5721.chg
IPMI code 6.08 IPMI code 6.25 IPMI-BCM5721.chg

8841 Boot code 3.29a Boot code 3.65 BCM5721.chg
IPMI code 6.08 IPMI code 6.25 IPMI-BCM5721.chg

8843 Boot code 3.21 Boot code 3.38 BCM5704s.chg
IPMI code 2.28 IPMI code 2.49 IPMI-BCM5704_5704s.chg

8848 Boot code 3.27 Boot code 3.41 BCM5704.chg
IPMI code 2.33 IPMI code 2.49 IPMI-BCM5704_5704s.chg

8849 Boot code 3.49 Boot code 3.65 BCM5721.chg
IPMI code 6.14 IPMI code 6.25 IPMI-BCM5721.chg

8850 Boot code 3.36 Boot code 3.38 BCM5704s.chg
IPMI code 2.36 IPMI code 2.49 IPMI-BCM5704_5704s.chg

8861 Boot code 3.19 Boot code 3.41 BCM5704.chg

8862 Boot code 3.19 Boot code 3.41 BCM5704.chg

8863 Boot code 3.36 Boot code 3.41 BCM5704.chg
IPMI code 2.36 IPMI code 2.49 IPMI-BCM5704_5704s.chg

8864 Boot code 3.36 Boot code 3.41 BCM5704.chg
IPMI code 2.36 IPMI code 2.49 IPMI-BCM5704_5704s.chg

8865 Boot code 3.36 Boot code 3.41 BCM5704.chg
IPMI code 2.41 IPMI code 2.49 IPMI-BCM5704_5704s.chg

8866 Boot code 3.41 Boot code 3.41 BCM5704.chg
IPMI code 2.45 IPMI code 2.49 IPMI-BCM5704_5704s.chg

8870 Boot code 3.19 Boot code 3.41 BCM5704.chg

8872 Boot code 3.36 Boot code 3.41 BCM5704.chg
IPMI code 2.41 IPMI code 2.49 IPMI-BCM5704_5704s.chg

8874 Boot code 3.36 Boot code 3.41 BCM5704.chg
IPMI code 2.41 IPMI code 2.49 IPMI-BCM5704_5704s.chg

8878 Boot code 3.41 Boot code 3.41 BCM5704.chg
IPMI code 2.45 IPMI code 2.49 IPMI-BCM5704_5704s.chg

8879 Boot code 3.41 Boot code 3.41 BCM5704.chg
IPMI code 2.45 IPMI code 2.49 IPMI-BCM5704_5704s.chg

9228 Boot code 3.24 Boot code 3.30 BCM5752.chg
ASF code 7.04 ASF code 7.20 ASF2.chg

9229 Boot code 3.24 Boot code 3.30 BCM5752.chg
ASF code 7.04 ASF code 7.20 ASF2.chg

9230 Boot code 3.27 Boot code 3.30 BCM5752.chg
ASF code 7.16 ASF code 7.20 ASF2.chg

9233 Boot code 3.09 Boot code 3.09 BCM5722.chg
IPMI code 6.03 IPMI code 6.03 IPMI-BCM5722.chg


NetXtreme II Servers
Product Previous Release Current Release Change History File
---------------------------------------------------------------------
1885 Boot code 4.6.1 Boot code 7.4.0 BCM5708s.chg
IPMI code 1.06.0 IPMI code 1.06.0 IPMI-BCM5706_5706s_5708_5708s.chg
UMP code 1.1.4 UMP code 1.1.9 UMP-BCM5706s_5708_5708s.chg

1909 Boot code 6.2.0 Boot code 7.4.0 BCM5709s.chg
NCSI code 2.0.6 NCSI code 2.0.11 NCSI-NX2.chg

1910 Boot code 6.2.0 Boot code 7.4.0 BCM5709s.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg

1911 Boot code 6.2.0 Boot code 7.4.0 BCM5709s.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg

1913 Boot code 4.6.1 Boot code 7.4.0 BCM5708.chg
IPMI code 1.06.0 IPMI code 1.06.0 IPMI-BCM5706_5706s_5708_5708s.chg

1914 Boot code 4.6.1 Boot code 7.4.0 BCM5708.chg
IPMI code 1.06.0 IPMI code 1.06.0 IPMI-BCM5706_5706s_5708_5708s.chg

1915 Boot code 4.6.1 Boot code 7.4.0 BCM5708s.chg
IPMI code 1.06.0 IPMI code 1.06.0 IPMI-BCM5706_5706s_5708_5708s.chg
UMP code 1.1.7 UMP code 1.1.9 UMP-BCM5706s_5708_5708s.chg

1936 Boot code 6.2.0 Boot code 7.4.0 BCM5709s.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg

1949 Boot code 6.2.0 Boot code 7.4.0 BCM5709s.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg

2582 Boot code 6.2.0 Boot code 7.4.0 BCM5709.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg

2583 Boot code 6.2.0 Boot code 7.4.0 BCM5709.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg

2586 Boot code 6.2.0 Boot code 7.4.0 BCM5709.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg

2587 Boot code 6.2.0 Boot code 7.4.0 BCM5709.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg

3808 Boot code 6.2.0 Boot code 7.4.0 BCM5709.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg

3809 Boot code 6.2.0 Boot code 7.4.0 BCM5709.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg

3815 Boot code 6.2.0 Boot code 7.4.0 BCM5709.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg

3817 Boot code 6.2.0 Boot code 7.4.0 BCM5709.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg

3821 Boot code 6.2.0 Boot code 7.4.0 BCM5709.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg

3822 Boot code 6.2.0 Boot code 7.4.0 BCM5709.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg

4195 Boot code 6.2.0 Boot code 7.4.0 BCM5709s.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg

4198 Boot code 6.2.0 Boot code 7.4.0 BCM5709.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg

4199 Boot code 6.2.0 Boot code 7.4.0 BCM5709.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg

4254 Boot code 6.2.0 Boot code 7.4.0 BCM5709.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg

4255 Boot code 6.2.0 Boot code 7.4.0 BCM5709.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg

7141 Boot code 6.2.0 Boot code 7.4.0 BCM5709.chg
IPMI code 1.0.1 IPMI code 1.0.1 IPMI-BCM5709_5709s.chg

7143 Boot code 6.2.0 Boot code 7.4.0 BCM5709.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg

7144 Boot code 6.2.0 Boot code 7.4.0 BCM5709.chg
IPMI code 1.0.1 IPMI code 1.0.1 IPMI-BCM5709_5709s.chg

7145 Boot code 6.2.0 Boot code 7.4.0 BCM5709.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg

7146 Boot code 6.2.0 Boot code 7.4.0 BCM5709.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg

7147 Boot code 6.2.0 Boot code 7.4.0 BCM5709.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg

7148 Boot code 6.2.0 Boot code 7.4.0 BCM5709.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg

7149 Boot code 6.2.0 Boot code 7.4.0 BCM5709.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg

7163 Boot code 4.6.1 Boot code 7.4.0 BCM5708.chg
IPMI code 1.06.0 IPMI code 1.06.0 IPMI-BCM5706_5706s_5708_5708s.chg

7164 Boot code 6.2.0 Boot code 7.4.0 BCM5709.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg

7191 Boot code 6.2.0 Boot code 7.4.0 BCM5709.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg

7192 Boot code 6.2.0 Boot code 7.4.0 BCM5709.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg

7233 Boot code 6.2.0 Boot code 7.4.0 BCM5709.chg
IPMI code 1.0.1 IPMI code 1.0.1 IPMI-BCM5709_5709s.chg

7234 Boot code 6.2.0 Boot code 7.4.0 BCM5709.chg
IPMI code 1.0.1 IPMI code 1.0.1 IPMI-BCM5709_5709s.chg

7378 Boot code 6.2.0 Boot code 7.4.0 BCM5716.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg

7379 Boot code 6.2.0 Boot code 7.4.0 BCM5716.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg

7380 Boot code 6.2.0 Boot code 7.4.0 BCM5709.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg

7809 Boot code 6.2.0 Boot code 7.4.0 BCM5709s.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg

7836 Boot code 6.2.0 Boot code 7.4.0 BCM5709s.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg

7837 Boot code 6.2.0 Boot code 7.4.0 BCM5709.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg

7839 Boot code 6.2.0 Boot code 7.4.0 BCM5709.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg

7870 Boot code 6.2.0 Boot code 7.4.0 BCM5709s.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg

7871 Boot code 6.2.0 Boot code 7.4.0 BCM5709s.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg

7872 Boot code 6.2.0 Boot code 7.4.0 BCM5709s.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg

7873 Boot code 6.2.0 Boot code 7.4.0 BCM5709s.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg

7901 Boot code 6.2.0 Boot code 7.4.0 BCM5709s.chg
IPMI code 1.0.1 IPMI code 1.0.1 IPMI-BCM5709_5709s.chg
UMP code 1.0.4 UMP code 1.0.6 UMP-BCM5709s.chg

7902 Boot code 4.4.14 Boot code 6.2.0 BCM5709s.chg
IPMI code 0.1.17 IPMI code 1.0.1 IPMI-BCM5709_5709s.chg
UMP code 1.0.4 UMP code 1.0.6 UMP-BCM5709s.chg

7940 Boot code 4.6.1 Boot code 4.6.1 BCM5706.chg
IPMI code 1.06.0 IPMI code 1.06.0 IPMI-BCM5706_5706s_5708_5708s.chg

7941 Boot code 4.6.1 Boot code 4.6.1 BCM5706.chg
IPMI code 1.06.0 IPMI code 1.06.0 IPMI-BCM5706_5706s_5708_5708s.chg

7943 Boot code 4.6.1 Boot code 4.6.1 BCM5706.chg
IPMI code 1.06.0 IPMI code 1.06.0 IPMI-BCM5706_5706s_5708_5708s.chg

7944 Boot code 6.2.0 Boot code 7.4.0 BCM5709.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg

7945 Boot code 6.2.0 Boot code 7.4.0 BCM5709.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg

7946 Boot code 6.2.0 Boot code 7.4.0 BCM5709.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg

7947 Boot code 6.2.0 Boot code 7.4.0 BCM5709.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg

7971 Boot code 4.6.1 Boot code 4.6.1 BCM5706s.chg
IPMI code 1.06.0 IPMI code 1.06.0 IPMI-BCM5706_5706s_5708_5708s.chg
UMP code 1.1.9 UMP code 1.1.9 UMP-BCM5706s_5708_5708s.chg
MPE Boot code 1.9.3 MPE Boot code 4.6.1 BCM5708s.chg

7972 Boot code 4.6.1 Boot code 4.6.1 BCM5706s.chg
IPMI code 1.06.0 IPMI code 1.06.0 IPMI-BCM5706_5706s_5708_5708s.chg
UMP code 1.1.9 UMP code 1.1.9 UMP-BCM5706s_5708_5708s.chg
MPE Boot code 1.9.3 MPE Boot code 4.6.1 BCM5708s.chg

7978 Boot code 4.6.1 Boot code 7.4.0 BCM5708.chg
IPMI code 1.06.0 IPMI code 1.06.0 IPMI-BCM5706_5706s_5708_5708s.chg

7979 Boot code 4.6.1 Boot code 7.4.0 BCM5708.chg
IPMI code 1.06.0 IPMI code 1.06.0 IPMI-BCM5706_5706s_5708_5708s.chg

7985 Boot code 4.6.1 Boot code 4.6.1 BCM5706.chg
IPMI code 1.06.0 IPMI code 1.06.0 IPMI-BCM5706_5706s_5708_5708s.chg

7995 Boot code 4.6.1 Boot code 7.4.0 BCM5708s.chg
IPMI code 1.06.0 IPMI code 1.06.0 IPMI-BCM5706_5706s_5708_5708s.chg
UMP code 1.1.7 UMP code 1.1.9 UMP-BCM5706s_5708_5708s.chg

7996 Boot code 4.6.1 Boot code 7.4.0 BCM5708.chg
IPMI code 1.06.0 IPMI code 1.06.0 IPMI-BCM5706_5706s_5708_5708s.chg

7997 Boot code 4.6.1 Boot code 7.4.0 BCM5708.chg
IPMI code 1.06.0 IPMI code 1.06.0 IPMI-BCM5706_5706s_5708_5708s.chg

8853 Boot code 4.6.1 Boot code 7.4.0 BCM5708s.chg
IPMI code 1.06.0 IPMI code 1.06.0 IPMI-BCM5706_5706s_5708_5708s.chg
UMP code 1.1.9 UMP code 1.1.9 UMP-BCM5706s_5708_5708s.chg

8877 Boot code 4.6.1 Boot code 7.4.0 BCM5708.chg
IPMI code 1.06.0 IPMI code 1.06.0 IPMI-BCM5706_5706s_5708_5708s.chg


NetXtreme and NetXtreme II Add-in Options for Blades
Product Initial Release Current Release Change History File
---------------------------------------------------------------------
26K4842 Boot code 3.21 Boot code 3.38 BCM5704s.chg
PXE code 7.6.6 PXE code 12.2.2 PXE-NX.chg

39R8624 Boot code 3.21 Boot code 3.38 BCM5704s.chg
PXE code 7.6.6 PXE code 12.2.2 PXE-NX.chg

39Y9306 Boot code 3.28 Boot code 3.29 BCM5715s.chg
PXE code 9.7.10 PXE code 12.2.2 PXE-NX.chg

39Y9310 Boot code 3.38 Boot code 3.38 BCM5704s.chg
PXE code 9.7.10 PXE code 12.2.2 PXE-NX.chg

42C1600 Boot code 3.24 Boot code 3.29 BCM5714s.chg
PXE code 9.0.12 PXE code 12.2.2 PXE-NX.chg

42C1632 Boot code 3.24 Boot code 3.29 BCM5714s.chg
PXE code 9.0.12 PXE code 12.2.2 PXE-NX.chg

46M6164 Boot code 6.2.22 Boot code 6.2.25 BCM57711.chg
NCSI code 6.2.7 NCSI code 6.2.7 NCSI-BCM57711.chg
PXE code 7.0.49 PXE code 7.2.29 PXE-NX2-ev.chg
UEFI code 7.0.41 UEFI code 7.8.53 UEFI-NX2-ev.chg

46M6168 Boot code 6.2.22 Boot code 6.2.25 BCM57711.chg
NCSI code 6.2.7 NCSI code 6.2.7 NCSI-BCM57711.chg
PXE code 7.0.49 PXE code 7.2.29 PXE-NX2-ev.chg
UEFI code 7.0.41 UEFI code 7.8.53 UEFI-NX2-ev.chg

44W4465 Boot code 5.2.71 Boot code 5.2.71 BCM57710.chg
NCSI code 0.5.8 NCSI code 2.0.7 NCSI-BCM57710.chg
PXE code 7.0.49 PXE code 7.2.29 PXE-NX2-ev.chg
UEFI code 7.0.41 UEFI code 7.8.53 UEFI-NX2-ev.chg

44W4466 Boot code 5.2.71 Boot code 5.2.71 BCM57710.chg
NCSI code 0.5.8 NCSI code 2.0.7 NCSI-BCM57710.chg
PXE code 7.0.49 PXE code 7.2.29 PXE-NX2-ev.chg
UEFI code 7.0.41 UEFI code 7.8.53 UEFI-NX2-ev.chg

44W4475 Boot code 6.2.0 Boot code 7.4.0 BCM5709s.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg
PXE code 7.0.6 PXE code 7.8.2 PXE-NX2.chg
UEFI code 7.6.51 UEFI code 7.6.51 UEFI-NX2.chg

44W4479 Boot code 6.2.0 Boot code 7.4.0 BCM5709s.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg
PXE code 7.0.6 PXE code 7.8.2 PXE-NX2.chg
UEFI code 7.6.51 UEFI code 7.6.51 UEFI-NX2.chg

44X1940 Boot code 6.2.0 Boot code 7.4.0 BCM5709s.chg
PXE code 7.0.6 PXE code 7.8.2 PXE-NX2.chg
UEFI code 7.6.51 UEFI code 7.6.51 UEFI-NX2.chg

73P9030 Boot code 3.21 Boot code 3.38 BCM5704s.chg
PXE code 7.6.6 PXE code 12.2.2 PXE-NX.chg

81Y3133 Boot code 6.2.22 Boot code 6.2.25 BCM57712.chg
NCSI code 6.2.7 NCSI code 6.2.7 NCSI-BCM57712.chg
PXE code 7.0.49 PXE code 7.0.49 PXE-NX2-ev.chg
UEFI code 7.8.53 UEFI code 7.8.53 UEFI-NX2-ev.chg


NetXtreme and NetXtreme II Add-in Options for Servers/Workstations
Product Initial Release Current Release Change History File
---------------------------------------------------------------------
22P7801 Boot code 2.25 Boot code 2.43 BCM5703s.chg
PXE code 7.6.6 PXE code 12.2.2 PXE-NX.chg

31P6301 Boot code 2.25 Boot code 2.43 BCM5703.chg
PXE code 7.6.6 PXE code 12.2.2 PXE-NX.chg

31P6401 Boot code 3.19 Boot code 3.41 BCM5704.chg
PXE code 7.6.6 PXE code 12.2.2 PXE-NX.chg

39Y6066 Boot code 4.6.1 Boot code 7.4.0 BCM5708.chg
PXE code 7.0.6 PXE code 7.6.50 PXE-NX2.chg
UMP code 1.1.9 UMP code 1.1.9 UMP-BCM5706s_5708_5708s.chg

39Y6079 Boot code 2.25 Boot code 2.43 BCM5703.chg
PXE code 7.6.6 PXE code 12.2.2 PXE-NX.chg

39Y6088 Boot code 2.25 Boot code 2.43 BCM5703s.chg
PXE code 7.6.6 PXE code 12.2.2 PXE-NX.chg

39Y6093 Boot code 3.19 Boot code 3.41 BCM5704.chg
PXE code 7.6.6 PXE code 12.2.2 PXE-NX.chg

39Y6098 Boot code 3.29a Boot code 3.65 BCM5721.chg
PXE code 7.6.6 PXE code 12.2.2 PXE-NX.chg

42C1780 Boot code 7.4.0 Boot code 7.4.0 BCM5709.chg
ISCSI code 7.6.50 ISCSI code 7.8.51 ISCSI-NX2.chg
PXE code 7.6.50 PXE code 7.8.2 PXE-NX2.chg
UEFI code 7.6.51 UEFI code 7.6.51 UEFI-NX2.chg

42C1781 Boot code 7.4.0 Boot code 7.4.0 BCM5709.chg
ISCSI code 7.6.50 ISCSI code 7.8.51 ISCSI-NX2.chg
PXE code 7.6.50 PXE code 7.8.2 PXE-NX2.chg
UEFI code 7.6.51 UEFI code 7.6.51 UEFI-NX2.chg

42C1790 Boot code 5.2.71 Boot code 5.2.71 BCM57710.chg
NCSI code 2.0.7 NCSI code 2.0.7 NCSI-BCM57710.chg
PXE code 7.0.49 PXE code 7.2.29 PXE-NX2-ev.chg
UEFI code 7.0.41 UEFI code 7.8.53 UEFI-NX2-ev.chg

42C1791 Boot code 5.2.71 Boot code 5.2.71 BCM57710.chg
NCSI code 2.0.7 NCSI code 2.0.7 NCSI-BCM57710.chg
PXE code 7.0.49 PXE code 7.2.29 PXE-NX2-ev.chg
UEFI code 7.0.41 UEFI code 7.8.53 UEFI-NX2-ev.chg

49Y4220 Boot code 7.4.0 Boot code 7.4.0 BCM5709.chg
ISCSI code 7.6.50 ISCSI code 7.8.51 ISCSI-NX2.chg
PXE code 7.6.50 PXE code 7.8.2 PXE-NX2.chg
UEFI code 7.6.51 UEFI code 7.6.51 UEFI-NX2.chg

49Y7910 Boot code 6.2.25 Boot code 6.2.25 BCM57712.chg
ISCSI code 7.6.50 ISCSI code 7.8.51 ISCSI-NX2.chg
PXE code 7.0.49 PXE code 7.6.53 PXE-NX2-ev.chg
UEFI code 7.0.41 UEFI code 7.6.58 UEFI-NX2-ev.chg

73P3501 Boot code 3.29a Boot code 3.65 BCM5721.chg
PXE code 7.6.6 PXE code 12.2.2 PXE-NX.chg

73P4001 Boot code 2.25 Boot code 2.43 BCM5703s.chg
PXE code 7.6.6 PXE code 12.2.2 PXE-NX.chg

73P4101 Boot code 2.25 Boot code 2.43 BCM5703.chg
PXE code 7.6.6 PXE code 12.2.2 PXE-NX.chg

73P4201 Boot code 3.19 Boot code 3.41 BCM5704.chg
PXE code 7.6.6 PXE code 12.2.2 PXE-NX.chg

90Y9352 Boot code 1.33 Boot code 1.35 BCM5719.chg
iSCSI code 7.6.50 iSCSI code 7.8.51 ISCSI-NX.chg
EFI code 15.6.53 EFI code 16.2.2 UEFI-NX.chg
PXE code 15.6.50 PXE code 15.4.2 PXE-NX.chg

90Y9370 Boot code 1.31 Boot code 1.32 BCM5720.chg
iSCSI code 7.6.50 iSCSI code 7.6.50* ISCSI-NX.chg
EFI code 15.6.53 EFI code 15.6.53* UEFI-NX.chg
PXE code 15.6.50 PXE code 15.6.50* PXE-NX.chg


NetXtreme and NetXtreme II Add-in Options for Flex Chassis
Product Previous Release Current Release
----------------------------------------------------------
49Y7900 Boot code 1.55 Boot code 1.58* BCM5718.chg
NCSI code 1.0.80 NCSI code 1.01.19* NCSI-NX.chg
IMFW code 1.05 IMFW code 1.06 IMFW-NX.chg
fcode 5.0.1 fcode 7.0.1*
iSCSI code 7.4.2 iSCSI code 7.6.50* ISCSI-NX.chg
EFI code 15.4.4 EFI code 15.6.53* UEFI-NX.chg
PXE code 15.4.2 PXE code 15.6.5* PXE-NX.chg



NetXtreme II 57XX Series Add-in Options
Product Previous Release Current Release
-----------------------------------------------
88Y5921 - MFW 7.8.55 BCM57840
- L2 7.8.5
- iSCSI code 7.8.51
- EFI 7.10.1
- PXE code 7.8.51

94Y5230 - MFW 7.8.55 BCM57810
- L2 7.8.5
- iSCSI code 7.8.51
- EFI 7.8.53
- PXE code 7.8.51

94Y5232 - MFW 7.8.55 BCM57810
- L2 7.8.5
- iSCSI code 7.8.51
- EFI 7.8.53
- PXE code 7.8.51

94Y5181 - MFW 7.8.55 BCM57810
- L2 7.8.5
- iSCSI code 7.8.51
- EFI 7.8.53
- PXE code 7.8.51

44T1361 - MFW 7.8.55 BCM57810
- L2 7.8.5
- iSCSI code 7.8.51
- EFI 7.8.53
- PXE code 7.8.51

00D9700 - MFW 7.8.55 BCM57811
- L2 7.8.5
- iSCSI code 7.8.51
- EFI 7.8.93
- PXE code 7.8.51


Package Version 2.3.1e
======================
There is no fw level change between 2.3.1d and 2.3.1e. 2.3.1e build has been created just to fix a firmware update tool applicaton extention file issue.


Package Version 2.3.1d
======================
UEFI code has been changed for 00D9700. This is the only change between 2.3.1c and 2.3.1d.


package version 2.3.1c
======================
Changes have been applied to only NX2 devices. Please refer to table above for each firmware code change. First firmware update tool is for 578xx series.(88Y5921,
94Y5230, 94Y5232, 94Y5181, 44T1361)


package version 2.2.1b
======================
-Changes were made to 44W4475,44W4479 devices to pick new level of UEFI v7.6.52. This UEFI code change
for 5709/5709s devices is the only change betweeen 2.2.1b and 2.2.1a.


package version 2.2.1a
======================
-Changes were made to the 42C1781, 90Y9370, 90Y9352, 39Y6066, 49Y4220, 49Y7910, 49Y7900.
(See above list for the firmware levels in your Broadcom Device.)


package version 2.1.9a
============================================================================================
-Changes made to the 5718, 5719 and 5720 firmware levels. (90Y9352, 90Y9370, 49Y7900. See above list
for current firmware levels.)
-No change for NX2 products in this package.


package version 2.1.8e
======================
Problems Fixed:
- Changes were made to the UEFI code to fix 49Y7910(BCM57712/Cobia) issues.

package version 2.1.8d (See brcm_fw_nic_2.1.8d-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changes were made to the boot code for the 46M6164, 46M6168, 49Y7910 and 81Y3133.
- Changes were mande to the PXE code for the 39Y6066, 42C1780, 42C1781, 42C1790, 42C1791,
44W4466, 44W4475, 44W4479, 44X1940, 46M6164, 46M6168, 49Y4220, 49Y7910 and 81Y3133.
- Changes were made to the UEFI code for the 42C1780, 42C1781, 42C1790, 42C1791,
44W4466, 44W4475, 44W4479, 44X1940, 46M6164, 46M6168, 49Y4220, 49Y7910 and 81Y3133.
- Changes were made to the iSCSI code for the 42C1780, 42C1781, 49Y4220 and 49Y7910.

package version 2.1.7e (See brcm_fw_nic_2.1.7e-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changes were made to the UEFI code for the 42C1780, 42C1781, 44W4475
, 44W4479
, 44X1940

and 49Y4220.
- Added support for the 49Y7910.

package version 2.1.7d (See brcm_fw_nic_2.1.7d-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changes were made to the UEFI code for the 42C1780, 42C1781, 42C1790, 42C1791,
44W4465
, 44W4466
, 44W4475
, 44W4479
, 44X1940
, 46M6164
, 46M6168, 49Y4220 and 81Y3133.
- Fixed a problem where the MAC addresses for the HS22/HS22V LOM were incorrectly set to zero.


package version 2.1.7c (See brcm_fw_nic_2.1.7c-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changes were made to the boot code for the 46M6164 and 46M6168.
- Changes were made to the NCSI code for the 46M6164 and 46M6168.
- Changes were made to the PXE code for the 42C1790, 42C1791, 46M6164, 46M6168, 44W4465 and 44W4466.
- Changes were made to the UEFI code for the 42C1790, 42C1791, 46M6164, 46M6168, 44W4465 and 44W4466.
- Changes were made to the iSCSI code for the 42C1780, 42C1781 and 49Y4220.

package version 2.1.7b (See brcm_fw_nic_2.1.7b-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Fixed problem running the PPC firmware update tool on some PPC systems.

package version 2.1.7a (See brcm_fw_nic_2.1.7a-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changes were made to the boot code for the 1909, 1936, 1949, 3808, 3809, 3815, 3817, 3821, 3822,
4195, 4198, 4199, 4254, 4255, 7141, 7144, 7145, 7146, 7148, 7149, 7164, 7233, 7234, 7378, 7379,
7380, 7809, 7836, 7837, 7839, 7870, 7871, 7901, 7902, 7944, 7945, 7946, 7947, 42C1780, 42C1781,
42C1790, 42C1791, 44W4475, 44W4479, 44X1940, 46M6164, 46M6168 and 49Y4220
- Changes were made to the NCSI code for the 1909, 1936, 1949, 3808, 3809, 3815, 3817,
3821, 3822, 4195, 4198, 4199, 4254, 4255, 7145, 7146, 7148, 7149, 7164, 7378, 7379,
7380, 7809, 7836, 7837, 7839, 7870, 7871, 7872, 7944, 7945, 7946, 7947, 44W4475, 44W4479,
46M6164 and 46M6168.
- Changes were made to the iSCSI code for the 42C1780, 42C1781 and 49Y4220.
- Changes were made to the UEFI code for the 46M6164, 46M6168, 44W4465, 44W4466, 44W4475,
44W4479, 44X1940, 42C1780, 42C1781, 42C1790, 42C1791 and 49Y4220.
- Changes were made to the PXE code for the 39Y6066, 42C1780, 42C1781, 42C1790, 42C1791,
44W4465, 44W4466, 44W4475, 44W4479, 44X1940, 46M6164, 46M6168 and 49Y4220.

package version 2.1.6b (See brcm_fw_nic_2.1.6b-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- The update tool was modified to fix a problem updating the firmware when certain option
cards are installed in the system.

package version 2.1.6a (See brcm_fw_nic_2.1.6a-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changes were made to the boot code for the 1909, 1936, 1949, 3808, 3809, 3815, 3817, 3821, 3822,
4195, 4198, 4199, 4254, 4255, 7141, 7144, 7145, 7146, 7148, 7149, 7164, 7233, 7234, 7378, 7379,
7380, 7809, 7836, 7837, 7839, 7870, 7871, 7901, 7902, 7944, 7945, 7946, 7947, 42C1780, 42C1781,
44W4475, 44W4479, 44X1940, 46M6164, 46M6168 and 49Y4220
- Changes were made to the NCSI code for the 46M6164, 46M6168, 44W4465, 44W4466, 42C1790,
and 42C1791.
- Changes were made to the iSCSI code for the 42C1780, 42C1781 and 49Y4220.
- Changes were made to the UEFI code for the 46M6164, 46M6168, 44W4465, 44W4466, 44W4475,
44W4479, 44X1940, 42C1780, 42C1781, 42C1790, 42C1791 and 49Y4220.
- Changes were made to the PXE code for the 39Y6066, 42C1780, 42C1781, 42C1790, 42C1791,
44W4465, 44W4466, 44W4475, 44W4479, 44X1940, 46M6164, 46M6168 and 49Y4220.

package version 2.1.5b (See brcm_fw_nic_2.1.5b-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Added iSCSI config update support for mfg.

package version 2.1.5a (See brcm_fw_nic_2.1.5a-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changes were made to the NCSI code for the 1909, 1936, 1949, 3808, 3809, 3815, 3817,
3821, 3822, 4195, 4198, 4199, 4254, 4255, 7145, 7146, 7148, 7149, 7164, 7378, 7379,
7380, 7809, 7836, 7837, 7839, 7870, 7871, 7872, 7944, 7945, 7946, 7947, 44W4475, 44W4479,
42C1790 and 42C1791
- Changes were made to the UEFI code for the 46M6164, 46M6168, 44W4465, 44W4466, 44W4475,
44W4479, 44X1940, 42C1780, 42C1781, 42C1790, 42C1791 and 49Y4220.
- Changes were made to the IPMI code for the 7141, 7144, 7233, 7234, 7901 and 7902.

package version 2.1.4a (See brcm_fw_nic_2.1.4a-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changes were made to the PXE code for the 39Y6066, 42C1780, 42C1781, 42C1790, 42C1791,
44W4465, 44W4466, 44W4475, 44W4479, 44X1940, 46M6164 and 46M6168.
- Changes were made to the UEFI code for the 42C1780, 42C1781, 42C1790, 42C1791, 44W4465,
44W4466, 44W4475, 44W4479, 44X1940, 46M6164 and 46M6168.

package version 2.1.3c (See brcm_fw_nic_2.1.3c-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changes were made to the iSCSI code for the 42C1780 and 42C1781.
- Changes were made to the UEFI code for the 42C1780, 42C1781, 42C1790, 42C1791, 44W4465,
44W4466, 44W4475, 44W4479, 44X1940, 46M6164 and 46M6168.
- Changes were made to the boot code for the 46M6164 and 46M6168.

Enhancements:
- Added version check to prevent firmware updates of code that is not newer than already
installed code.
- Added "-force" command line option to allow forcing the firmware update.

package version 2.1.3b (See brcm_fw_nic_2.1.3b-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changes were made to the boot code for the 1936, 1949, 3808, 3809, 3815, 3817, 3821, 3822,
4198, 4199, 4254, 4255, 7141, 7144, 7145, 7146, 7233, 7234, 7378, 7379, 7380, 7836, 7837,
7839, 7870, 7871, 7901, 7902, 7944, 7945, 7946, 7947, 42C1780, 42C1781, 44W4475, 44W4479
and 44X1940.
- Changes were made to the NCSI code for the 1936, 1949, 3808, 3809, 3815, 3817, 3821, 3822,
4198, 4199, 4254, 4255, 7145, 7146, 7378, 7379, 7380, 7836, 7837, 7839, 7870, 7871, 7944,
7945, 7946, 7947, 44W4475 and 44W4479.
- Changes were made to the PXE code for the 39Y6066, 42C1780, 42C1781, 44W4475, 44W4479 and
44X1940.
- Changes were made to the UEFI code for the 42C1780, 42C1781, 44W4475, 44W4479 and 44X1940.
- Changes were made to the iSCSI code for the 42C1780 and 42C1781.

package version 2.1.3a (See brcm_fw_nic_2.1.3a-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changes were made to the PXE code for the 26K4842, 39R8624, 39Y9306, 39Y9310, 42C1600,
42C1632, 46M6164, 46M6168, 44W4465, 44W4466, 73P9030, 22P7801, 31P6301, 31P6401, 39Y6079,
39Y6088, 39Y6093, 39Y6098, 42C1790, 42C1791, 73P3501, 73P4001, 73P4101 and 73P4201.
- Changes were made to the UEFI code for the 46M6164, 46M6168, 44W4465, 44W4466, 42C1790,
and 42C1791.
- Changes were made to the NCSI code for the 46M6164, 46M6168, 44W4465, 44W4466, 42C1790,
and 42C1791.
- Changes were made to the boot code for the 46M6164, 46M6168, 44W4465, 44W4466, 42C1790,
and 42C1791.

package version 2.1.1c (See brcm_fw_nic_2.1.1c-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- none.

Enhancements:
- Added support for the 1949, 4254, 4255, 7378, 7379, 7380, 7871, 7944 and 7945.

package version 2.1.1b (See brcm_fw_nic_2.1.1b-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Fixed problem where the firmware update failed to run correctly on RHEL5u4-XEN.

package version 2.1.1a (See brcm_fw_nic_2.1.1a-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changes were made to the boot code for the 1885, 1913, 1914, 1915, 1936, 3808, 3809, 3815,
3817, 3821, 3822, 4198, 4199, 7141, 7144, 7163, 7233, 7234, 7809, 7836, 7837, 7839, 7870,
7901, 7902, 7946, 7947, 7978, 7979, 7995, 7996, 7997, 8853, 8877, 44W4465, 44W4466, 44W4475,
44W4479, 44X1940, 39Y6066, 42C1780, 42C1781, 42C1790 and 42C1791.
- Changes were made to the NCSI code for the 1936, 3808, 3809, 3815, 3817, 3821, 3822, 4198,
4199, 7809, 7836, 7837, 7839, 7870, 7946, 7947, 44W4465, 44W4466, 44W4475, 44W4479, 42C1790
and 42C1791.
- Changes were made to the PXE code for the 44W4465, 44W4466, 44W4475, 44W4479, 44X1940,
39Y6066, 42C1780, 42C1781, 42C1790 and 42C1791.
- Changes were made to the UEFI code for the 44W4465, 44W4466, 44W4475, 44W4479, 44X1940,
42C1780, 42C1781, 42C1790 and 42C1791.
- Changes were made to the iSCSI code for the 42C1780 and 42C1781.

Enhancements:
- Added support for the 46M6164 and 46M6168.

package version 2.1.0a (See brcm_fw_nic_2.1.0a-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changes were made to the boot code for the 1936, 3808, 3809, 3815, 3817, 3821, 3822,
4198, 4199, 7141, 7144, 7233, 7234, 7836, 7837, 7839, 7870, 7901, 7902, 7946, 7947,
42C1780, 42C1781, 42C1790, 42C1791, 44W4465, 44W4466, 44W4475, 44W4479 and 44X1940.
- Changes were made to the PXE code for the 39Y6066, 42C1780, 42C1781, 42C1790, 42C1791,
44W4465, 44W4466, 44W4475, 44W4479 and 44X1940.
- Changes were made to the ISCSI code for the 42C1780 and 42C1781.

package version 2.0.9h (See brcm_fw_nic_2.0.9h-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Removed the minimum boot code level check for the 44W4465 and 44W4466.

Enhancements:
- Added support for the 3808, 3809, 3815, 3817, 3821, 3822, 4198, 4199, 7836, 7837, 7839
and 9233.

package version 2.0.9g (See brcm_fw_nic_2.0.9g-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changes were made to the UEFI code for 42C1780, 42C1781, 42C1790, 42C1791, 44W4465
44W4466, 44W4475, 44W4479 and 44X1940.
- Fixed the problem where the PXE code for the 44W4465 and 44W4466 failed to update
under 64bit Linux.

Enhancements:
- Added support for the 7946 and 7947.

package version 2.0.9f (See brcm_fw_nic_2.0.9f-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changes were made to the boot code for the 1885, 1913, 1914, 1915, 7141, 7144, 7233, 7234,

7940,
7941,
7971,
7972,
7978,
7979,
7985,
7995,
7996,
7997,
8853,
8877, 39Y6066, 42C1780,
42C1781, 42C1790, 42C1791, 44W4465, 44W4466 and 44W4479.
- Changes were made to the NCSI code for the 42C1790, 42C1791, 44W4465, 44W4466 and 44W4479.
- Changes were made to the PXE code for 42C1790, 42C1791, 44W4465, 44W4466 and 44W4479.

Enhancements:
- Added support for the 1936, 7870 and 44W4475.
- Added UEFI code for 42C1790, 42C1791, 44W4465, 44W4466, 44W4479 and 44X1940.

package version 2.0.9e (See brcm_fw_nic_2.0.9e-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Added a bnx2 device driver version check for version 1.6.6b or greater.

package version 2.0.9c (See brcm_fw_nic_2.0.9c-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changes were made to the boot code for the 1885, 1915, 7901, 7902, 7971, 7972, 7995,
8853 and 44W4479.
- Changes were made to the PXE code for the 39Y6066, 42C1780, 42C1781 and 44W4479.
- Changes were made to the iSCSI code for the 42C1780 and 42C1781
- Changes were made to the NCSI code for the 44W4479.

Enhancements:
- Added support for the 44X1940.

package version 2.0.8f (See brcm_fw_nic_2.0.8f-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Fcode support was removed for the PXE code for the 44W4465 and 44W4466. This change
does not result in a change in the PXE code version number.
- Changes were made to the PXE code for the 39Y6066, 42C1780 and 42C1781 to fix a
problem where some systems hang when loading PXE code.

package version 2.0.8e (See brcm_fw_nic_2.0.8e-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changes were made to the PXE code for the 39Y6066, 42C1780, 42C1781 and 44W4479.
- Changes were made to the IPMI code for the 7141, 7144, 7233 and 7234.
- Changes were made to the UMP code for the 7901 and 7902.

Enhancements:
- Added support for the 6388, 7942, 44W4465 and 44W4466.

package version 2.0.8d (See brcm_fw_nic_2.0.8d-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changes were made to the boot code for the 7141, 7144, 7233 and 7234.

Enhancements:
- Added support for the 42C1780 and 42C1781.

package version 2.0.8c (See brcm_fw_nic_2.0.8c-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- None.

Enhancements:
- Added support for the 7901 and 7902

package version 2.0.8b (See brcm_fw_nic_2.0.8b-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changes were made to the PXE code for the 39Y6066.

Enhancements:
- Added support for the 44W4479.

package version 2.0.8a (See brcm_fw_nic_2.0.8a-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changes were made to the boot code for the 1885, 1913, 1914, 1915, 7141, 7144, 7971,
7972, 7978, 7979, 7985, 7995, 7996, 7997, 8853, 8877, 9228, 9229, 9230 and 39Y6066.
- Changes were made to the ASF code for the 6218, 6223, 6225, 6227, 6228, 8488,
8648, 9228, 9229, 9230.
- Changes were made to the UMP code for the 39Y6066.
- Changes were made to the PXE code for the 22P7801, 26K4842, 31P6301, 31P6401,
39R8624, 39Y6066, 39Y6079, 39Y6088, 39Y6093, 39Y6098, 39Y9306, 39Y9310, 42C1600,
42C1632, 73P3501, 73P4001, 73P4101, 73P4201, 73P9030.
- Changes were made to the IPMI code for the 1916, 8014 and 8028.

Enhancements:
- Added support for the 7233, 7234, 7940 and 7941.

package version 2.0.7 (See brcm_fw_nic_2.0.7-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changes were made to the PXE code for the 22P7801, 26K4842, 31P6301, 31P6401,
39R8624, 39Y6066, 39Y6079, 39Y6088, 39Y6093, 39Y6098, 39Y9306, 39Y9310, 42C1600,
42C1632, 73P3501, 73P4001, 73P4101, 73P4201, 73P9030.

Enhancements:
- Added support for the 1916, 8014 and 8028.

package version 2.0.6 (See brcm_fw_nic_2.0.6-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changes were made to the boot code for the 1913, 1914, 7141, 7143, 7144, 7978,
7979, 7996, 7997, 8877 and 39Y6066.
- Changes were made to the UMP code for the 39Y6066.
- Changes were made to the PXE code for the 39Y6066.

package version 2.0.5 (See brcm_fw_nic_2.0.5-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- None

Enhancements:
- Added support for the 4190, 4191, 4192, 4193, 4194, 4367 and 4368.

package version 2.0.4 (See brcm_fw_nic_2.0.4-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- None

Enhancements:
- Added support for the 7141, 7143 and 7144.

package version 2.0.3 (See brcm_fw_nic_2.0.3-lin-win-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changes were made to the boot code for the 1885, 1913, 1914, 1915, 7971, 7972,
7978, 7979, 7985, 7995, 8853, 8877, 39Y6066.
- Changes were made to the IPMI code for the 1879, 1880, 1883, 1884, 1887, 4362,
4363, 4364, 4365, 4366, 7362, 7364, 7365, 7367, 7973, 7974, 7975, 7976, 7977,
7981, 7984, 7986, 8485, 8490, 8491, 8832, 8835, 8837, 8840, 8841, 8843, 8848,
8849, 8850, 8863, 8864, 8865, 8866, 8872, 8874, 8878, 8879.
- Changes were made to the ASF code for the 6218, 6223, 6225, 6227, 6228, 8488,
8648, 9228, 9229, 9230.
- Changes were made to the PXE code for the 22P7801, 26K4842, 31P6301, 31P6401,
39R8624, 39Y6066, 39Y6079, 39Y6088, 39Y6093, 39Y6098, 39Y9306, 39Y9310, 42C1600,
42C1632, 73P3501, 73P4001, 73P4101, 73P4201, 73P9030.

package version 2.0.0b (See brcm_fw_nic_2.0.0b-nx-nx2-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changed the firmware update process to NOT reset the ethernet devices during the
firmware update process.

package version 2.0.0 (See brcm_fw_nic_2.0.0-nx-nx2-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changes were made to the UMP (Universal Management Port) code for the 1885,
7971, 7972, 7995 and 8853.

package version 1.1.1 (See brcm_fw_nic_1.1.1-nx-nx2-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changes were made to the boot code for the 1879, 1880, 1887, 4347, 4348, 4362,
4363, 4364, 4365, 4366, 6218, 6223, 6225, 6227, 6228, 7969, 7973, 7974, 7975,
7976, 7977, 7992, 8485, 8486, 8488, 8490, 8491, 8648, 8837, 8840, 8841, 8849,
39Y6098, 39Y9306, 42C1600, 42C1632 and 73P3501.
- Changes were made to the IPMI code for the 1879, 1880, 1887, 4362, 4363, 4364,
4365, 4366, 7969, 7973, 7974, 7975, 7976, 7977, 7992, 8485, 8490, 8491, 8837,
8840, 8841 and 8849.
- Changes were made to the PXE code for the 22P7801, 26K4842, 31P6301, 31P6401,
39R8624, 39Y6079, 39Y6088, 39Y6093, 39Y6098, 39Y9306, 39Y9310, 42C1600, 42C1632,
73P3501, 73P4001, 73P4101, 73P4201 and 73P9030.

package version 1.1.0 (See brcm_fw_nic_1.1.0-nx-nx2-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changes were made to the Boot Code for the 1913, 1914, 4347, 6218, 6223, 6225,
6227, 6228, 7969, 7971, 7972, 7978, 7979, 7985, 7995, 8486, 8648, 8853, 8877,
9228 and 9229.
- Changes were made to the ASF code for 6218, 6223, 6225, 6227, 6228, 8648,
9228 and 9229.
- Changes were made to the PXE code for the 39Y6066.
- Changes were made to the

Enhancements:
- Added support for the 1879, 1880, 1883, 1884, 1887, 1913, 22P7801, 31P6301,
31P6401, 39Y9306, 39Y6066, 39Y6079, 39Y6088, 39Y6093, 39Y6098, 39Y9310, 4348,
4366, 7362, 7364, 7365, 73P3501, 73P4001, 73P4101, 73P4201, 7992, 7995, 8488
and 9230.

package version 1.0.0 (See brcm_fw_nic_1.0.0-nx-nx2-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changes were made to the boot code for the 8832, 1914, 7971, 7972, 7978, 7979
7985, 8853 and 8877.
- Changes were made to the UMP (Universal Management Port) code for the 7971,
7972 and 8853.
brcm_fw_nic_2_3_1f_windows_32-64_chg

===============================================================================
Emulex NIC Device Driver for Windows
===============================================================================

Device Driver Version: 10.2.413.1
Supported On: System x, BladeCenter and Flex

Problems Fixed:
- Packet loss observed during affinity changes. During the change, a 'pause'
occurs, packets will get dropped, bandwidth utilization will drop because
of the stall, and overall performance will be inconsistent.

- When using multi-channel in a vSwitch environment, map one PF to the
hyper-visor vSwitch and then use the other PF’s/vNICs for live migration
network, FCoE/iSCSI, Management network and the like in order to get the best
performance.

Incremental Interoperability:
- Grantley based ITE

Known Issues:
- RoCE support is limited to named applications. Contact your local IBM Sales
Support for more information.

- There is no benefit from using NVGRE on more than one vNIC attached to the
same physical port. As such, only one vSwitch should be attached to a
physical port. Attaching more than one vSwitch to a physical port could
cause a dramatic decrease in performance. This is a permanent limitation

===============================================================================

Device Driver Version: 10.2.370.18
Supported On: System x and BladeCenter

Problems Fixed:
- Network connectivity is getting lost for VMQ interfaces during VMQ CPU
affinity stress test

Incremental Interoperability:
- None

Known Issues:
- RoCE support is limited to named applications. Contact your local IBM Sales
Support for more information.
- Packet loss observed during affinity changes. During the change, a 'pause'
occurs, packets will get dropped, bandwidth utilization will drop because
of the stall, and overall performance will be inconsistent.
- When using multi-channel in a vSwitch environment, map one PF to the
hyper-visor vSwitch and then use the other PF’s/vNICs for live migration
network, FCoE/iSCSI, Management network and the like in order to get the best
performance.
- There is no benefit from using NVGRE on more than one vNIC attached to the
same physical port. As such, only one vSwitch should be attached to a
physical port. Attaching more than one vSwitch to a physical port could
cause a dramatic decrease in performance.

===============================================================================

Device Driver Version: 10.2.348.2
Supported On: IBM System x

Problems Fixed:
- BSOD after running IO's using NVGRE offload for 16VM's, also affects VMQ and
SRIOV
- Option to enable/disable RSS not visible in NIC advanced properties
- Network connectivity is getting lost for VMQ interfaces
- Performance and Fairness for 16VM's is uneven on Windows 2012 R2

Incremental Interoperability:
- Grantley Rack Servers

Known Issues:
- RoCE support is limited to named applications. Contact your local IBM Sales
Support for more information
- Packet loss observed during affinity changes. During the change, a 'pause'
occurs, packets will get dropped, bandwidth utilization will drop because
of the stall, and overall performance will be inconsistent.
- When using multi-channel in a vSwitch environment, map one PF to the
hyper-visor vSwitch and then use the other PF’s/vNICs for live migration
network, FCoE/iSCSI, Management network and the lie in order to get the best
performance.
- There is no benefit from using NVGRE on more than one vNIC attached to the
same physical port. As such, only one vSwitch should be attached to a
physical port. Attaching more than one vSwitch to a physical port could
cause a dramatic decrease in performance.

===============================================================================

Device Driver Version: 10.2.261.11
Supported On: IBM System x, BladeCenter, and Flex

Problems Fixed:
- When MAC learning is enabled, driver should not drop internally switched
packets
- Incorrect Port numbering in nic multichannel tab
- No link down on UMC 0 bw min and max
- BE3: very low throughput transmit on SR IOV Guest OS (netperf less than
100Mbps although 10Gb link)
- BE3 Win2k12R2 Hyper v server crashed during the creation of virtual
switch using the LACP teamed adapter
- NIC Teaming (failover/failback) fails on HS23 LOM

Incremental Interoperability:
- ARI (PCI-SIG specification)
- RDMA over CEE (RoCE)

Known Issues:
- RoCE support is limited to named applications. Contact your local IBM Sales
Support for more information
- When using VMQ with Windows Server 2012 or 2012R2, the user may experience
VM connectivity loss, packet drops, system hangs, inability to shutdown VMs
and possible system crashes on shutdown.

===============================================================================

Device Driver Version: 10.0.718.26
Supported On: IBM System x

Problems Fixed:
- VMQ driver option incorrectly available for 1Gb ports of BE3
- BE2 and BE3: Hitting Nic initialization failure after updating driver
- Update custom property page display for BE3R
- Windows NIC driver always reports initial link status as UP

Incremental Interoperability:
- Emulex Dual port 10Gb SFP+ Ethernet Adapter Card (XE-102/XE-104 based)

Known Issues:
- None

===============================================================================

Device Driver Version: 4.6.203.1
Supported On: IBM System x, BladeCenter, and Flex

Problems Fixed:
- HyperV VM's tagged VLAN's did not get an IP Address
- NIC Function Properties > Status for PCI Express Link Speed says Invalid
Link Speed detected.
- iSCSI ports of CNA card in ESXi 4.1u3 OCM GUI (vCenter plug in) is not
getting displayed

Incremental Interoperability:
- None

Known Issues:
- None

===============================================================================

Device Driver Version: 4.6.142.8
Supported On: IBM System x and BladeCenter

Problems Fixed:
- None

Incremental Interoperability:
- PCI-IDs added for XE4310R controller applications
- Hyper-V with Switch Independent Mode enabled

Known Issues:
- No known issues

===============================================================================

Device Driver Version: 4.4.176.2
Supported On: IBM Flex

Device Driver Version: 4.2.390.6
Supported On: IBM System x and BladeCenter

Problems Fixed:
- Cleaned up inf file
- TOE Offload Fails when the same neighbor is added more than once

Incremental Interoperability:
- Windows 2012

Known Issues:
- Switch Independent Mode not supported in a HyperV environment
- Default values vary between inbox and out of box drivers. For example:
Configuration section
- Wake On LAN
- Inbox default is ‘Disabled’
– out-of-box default is ‘Enabled’
Performance section
- Maximum Number of RSS Queues
- Inbox default is ‘4’
- out-of-box default is ‘8’
- Virtual Machine Queues
- Inbox default is ‘Disabled’
– out-of-box default is ‘Enabled’
You may select the button to reset all driver settings to defaults after
any installation.

===============================================================================

Device Driver Version: 4.1.370.0
Supported On: IBM System x, BladeCenter, and Flex

Incremental Interoperability:
- Initial release for IBM Flex

Problems Fixed:
- HS23 - Sleep Stress test failed with bugcheck C4 during driver verify
- TOE with RSC enabled causes Network to go down
- Augmented WOL Capabilities
- Driver parameter query failures
- BSOD 9F during shutdown if device stops responding
- RSS queues may change port during MPRestart and MPPause

===============================================================================

Device Driver Version: 4.1.334.25
Supported On: IBM System x and BladeCenter

Problems Fixed:
- Emulex: Large Receive Offload support needed in Windows NIC driver
- Win WoL: Need to report WoL based on ARM reported capabilities
- update the driver strings for existing cards
- RSS code may access PerMessage beyond end of array
- 16 queue RSS for BE3 on Windows 2008 R2
- fix unverified mode of occfg to allow customer workarounds
- 16 queue RSS lockup if SRIOV enabled in registry
- Standard Property Page for 1 port Windows Azure card
- Timeout RQ flush to avoid bugcheck during shutdown
- Change receive buffer alignment to use Windows 2008 R2 TCPIP fast path
- Emulex: BSOD - Replacing BE3 card with a BE2 card after installation of new
kit driver and firmware on Win 2k3 SP2 R2x64 (vNIC enabled IBM machine)
- be2nd62.inf failed ChkInf
- VMQ registry keys displayed in Windows 2008
- be_function_prepare_nonembedded_ioctl overwrites version field
- autoi reboot fails on Win2K8 x64 when verifier enabled
- PCI ID: Updates for Endeavor 2 for IBM- PCI IDs Rev 1.22
- Emulex NIC driver causes BSoD during shutdown whenever disable firewall
or join domain network
- Sleep Stress test failed with bugcheck C4 during driver verify
- Disable TOE by default for IBM
- BSOD 9F during shutdown if device stops responding

===============================================================================

Device Driver Version: 2.103.389.0

Supported On: IBM System x and BladeCenter

- Initial Release

===============================================================================
elx_dd_nic_14a-10_2_413_1-3_windows_32-64_chg

===============================================================================
Emulex iSCSI Device Driver for Windows
===============================================================================

Device Driver Version: 10.2.421.0
Supported On: System x, BladeCenter and Flex

Problems Fixed:
- OCe14 iSCSI: Performance IOPs read @ 512B does not meet requirement
- Fix BSOD in WLK Hot-Add CPU test

Incremental Interoperability:
- Grantley based ITE

Known Issues:
- None

===============================================================================

Device Driver Version: 10.2.370.9
Supported On: System x and BladeCenter

Problems Fixed:
- "DrvLoad fails on iSCSI x86 Win8.1 Error = 3" occurs on setupElxAll x86.exe
on WinPE 5.0 x86

Incremental Interoperability:
- Grantley Rack Servers

Known Issues:
- None

===============================================================================

Device Driver Version: 10.2.254.0
Supported On: IBM System x, BladeCenter, and Flex

Problems Fixed:
- Cleaned up PCI ids in the inf file
- iSCSI driver's usage of EQ/CQ/RQ doorbell formats for XE-102 and XE-104
- Mis-match in product version between NIC and iSCSI drivers
- Lun Reset/Target Reset can hang under some errors in Windows iSCSI driver
- Random crashes while load/unload surf driver

Incremental Interoperability:
- None

Known Issues:
- None

===============================================================================

Device Driver Version: 10.0.732.0
Supported On: IBM System x

Problems Fixed:
- Windows2012 blue screen dpc_watchdog_violation 256 targets during driver
disable/enable
- Gracefully Handle insufficient buffer ioctl response
- Support logging into as many iSCSI targets as the firmware will report
- Remove link speed on properties page iSCSI driver
- DVL log creation fails for iSCSI driver


Incremental Interoperability:
- Emulex Dual port 10Gb SFP+ Ethernet Adapter Card (XE-102/XE-104 based)

Known Issues:
- None

===============================================================================

Device Driver Version: 4.6.279.0
Supported On: IBM System x and Flex

Problems Fixed:
- None

Incremental Interoperability:
- Windows 2012 R2

Known Issues:
- None

===============================================================================

Device Driver Version: 4.6.130.0
Supported On: IBM System x, BladeCenter, and Flex

Problems Fixed:
- Cleaned up PCI ids in the inf file

Incremental Interoperability:
- None

Known Issues:
- None

===============================================================================

Device Driver Version: 4.4.165.0
Supported On: IBM Flex

Device Driver Version: 4.2.281.0
Supported On: IBM System x and BladeCenter

Problems Fixed:
- Documentation: Cleaned up inf file to remove unused device ID's

Incremental Interoperability:
- Windows 2012
- support Full 64-bit address in Dma64BitAddress member of
PORT_CONFIGURATION_INFORMATION structure

Known Issues:
- None

===============================================================================

Device Driver Version: 4.1.334.0
Supported On: IBM System x, BladeCenter, and Flex

Incremental Interoperability:
- Initial release for IBM Flex

Problems Fixed:
- Logout handling on boot session when multiple sessions exists to the same
boot target
- Add PCI ID as per Rev 1.18 for Windows iSCSI Driver
- Multipath IO fails producing a BSOD
- Persistent login to Max targets + 1 from WMI causes a hang
- Update Nomad Device Name as per 1.19 for Windows iSCSI drivers
- PCI ID: Updates for Endeavor 2 - PCI IDs Rev 1.22

===============================================================================

Device Driver Version: 2.103.386.0
Supported On: IBM System x and BladeCenter

- Initial Release

===============================================================================
elx_dd_iscsi_14a-10_2_421_0-3_windows_32-64_chg

IBM High IOPS Modular Adapter Driver for Windows 2012/2008 R2/2008

Controller Supported:
- IBM 300 GB High IOPS MLC Modular Adapter (90Y4361)
- IBM 600 GB High IOPS MLC Modular Adapter (90Y4365)
- IBM 800 GB High IOPS MLC Modular Adapter (90Y4369)
- IBM 300 GB High IOPS SLC Modular Adapter (90Y4373)

NOTE TO SERVICE - Reference RETAIN #N/A


Version 2.10.60-1 - Non Critical
------------------
- Fixed an issue in Windows 2012 where a false failure return code
given after successful execution of the update.
Note: No change the device driver. Version is 2.10.60

Version 2.10.60 - Initial release
------------------
ibm_dd_mptsss_2_10_60-1_windows_x86-64_chg

LSI 2004 SAS Controller BIOS and Firmware Update for IBM BladeCenter HS23

System Supported: IBM BladeCenter HS23 (7875, 1929)

NOTE TO SERVICE - Reference RETAIN #N/A
Version 1.20.02
-------------
Contains:
BIOS Firmware UEFI Driver
7.39.00.00 20.00.05.00 7.27.04.00

Enhancements:
- Added System X Agentless support
- Indicate support for the ATA Device Server Password security protocol
(SCGCQ00465302)
- Allow UEFI and BIOS to be Enabled/Disabled individually (SCGCQ00574358)
- Added ConnectorName and EnclosureLevel fields to SAS Device Page 0 to
help identify physical location of a target device (SCGCQ00523879)
- Set SATA HOLD threshold to be configurable in NVDATA (SCGCQ00712525)
- If HW can gets into a stuck state, clear that state upon break received.
(SCGCQ00631031)
- Added a new HII option to disable legacy BIOS (SCGCQ00568594)
- The sector size of drives with 4096 bytes physical sector size and 512 bytes
logical sector size will be displayed as 512e.(SCGCQ00568598)

Fixes:
- Fixed SMP passthrough command failure due to smp back off interrupt.
Appears in system log as 0x311c0030. (SCGCQ00889925)
- Fixed issue where host boot fails in the presence of blank flash/corrupt
firmware in flash (SCGCQ00894439)
- Fixed issue where SATA drive errors, bad performance, or boot failure may
appear after update to 20.00.02.00 firmware (SCGCQ00859226)(Retain Tip# H015210)
- Fixed an issue seen with RAID 10 array where during a warm OS boot, drive
models with a long spin up delay may get marked as failed for being
unresponsive. Delay ultimately triggers a rebuild of the array.(SCGCQ00836017)
- Set SAS drives to track bad blocks using a bad block table rather than
using a SCSI Write Long.
- Fixed DMAGroup performance issue.(SCGCQ00632433)
- Fixed issue with Phase 18 IR FW where booting a RAID volume (such as raid 10),
hangs at OROM "Initializing.." and fault 8803 seen. (SCGCQ00641950)
- Fixed issue where Report Luns command to a SATA drive fails with
CheckCondition/Invalid Field in CDB when allocation length set to Zero.
(SCGCQ00615518)
- Fixed issue where Raid Accelerator IOs can hang if the stream of IOs
suddenly stops. (SCGCQ00599997)
- Fixed issue where an invalid frame sent during a PIO-mode SATA
passthrough command results in resetting the drive. (SCGCQ00600001)
- Fixed issue where lots of NCQ I/O error messages were reported.
Appear as: "mpt2sas0: log_info(0x31080000)" (SCGCQ00802848)
- Fixed issue where if certain PCIe timeouts occur in the presence of Link
Unavailable, a hang condition or data corruption can occur.(SCGCQ00787001)
- Fixed issue where system hangs after adapter reset with heavy IO load.
(SCGCQ00681098)
- Fixed issue where access to Last Logical Block Address (LBA) of SATA drive
is Prevented and LBA out Of range by one block is missed. (SCGCQ00747711)
- Made change to deal with link getting stuck and causing missing drives.
(difficult to reproduce)(SCGCQ00747288)
- Fixed IR issue where page header information is not filled in when RAID
PHYS DISK PAGE 0 is returned for a non-RAID Disk drive. (SCGCQ00756932)
- Fixed issue where controller hits 0x265d fault while creating volume
when there is an inactive volume.(SCGCQ00733218)
- DID_SOFT_ERRORs are seen when hot plug is performed on the RAID1 volume
along with IOs.(SCGCQ00733219)
- Fixed issue where system gets hung and reboots while running IO's along with
diag reset on the Controller which has active and inactive volumes.
(SCGCQ00733220)
- Fixed latency spikes seen during performance testing (SCGCQ00736663)
- MPI 2.5: distribute target command buffers received across multiple
reply queues. (SCGCQ00685820)
- Fixed issue where command sas2flash -dflash results in a non-functional
system. (SCGCQ00557354)
- Fixed issue where internal device reset storm occurs after controller reset
using long CDB. (SCGCQ00643892)
- Fixed 0x6003 fault due to task management of lost IO (SCGCQ00677741)
- Fixed 0x58A1 fault occurring on partner controller while issuing MUR to a
target mode controller with outstanding IOs. (SCGCQ00681099)
- Fixed issue where IO error occurred when hot plug a HDD from RAID1
(SCGCQ00697505)
- Fixed issue where fault 8901 is seen when the volume is roamed.(SCGCQ00726300)

BIOS
- Fixed issue where Legacy BIOS failed to detect certain large capacity SAS drives
(SCGCQ00696485)
- Fixed issue where system boot hangs when Legacy BIOS is disabled (using HII)
on certain UEFI systems. (SCGCQ00643917)
- Fixed issue where drives that use Descriptor Sense Data were returning format
complete immediately even though format still in progress. (SCGCQ00630498)

UEFI
- Fixed issue with RAID1E in HII where drive selection for 4th drive is not getting
disabled when using check all option (SCGCQ00582185)


Version 1.20.01 - Moderate Impact/Low Probablility of Occurrence
-------------
Contains:
BIOS Firmware UEFI Driver
7.39.00.00 20.00.03.00 7.27.04.00

- Fixed an issue seen with RAID 10 array where during a warm OS boot, certain drive models
with a long spin up delay may get marked as failed for being unresponsive. This delay
ultimately triggers a rebuild of the array.

Version 1.20 - Non-Critical
-------------
Contains:
BIOS Firmware UEFI Driver
7.39.00.00 20.00.02.00.00 7.27.04.01

Version 1.18.01 - Non-Critical
-------------
Contains:
BIOS Firmware UEFI Driver
7.35.01.00 18.00.00.00 7.25.04.01

Fixes:
- Fixed an issue where 4k sector size drives with 512e reporting enabled show
wrong physical size when running a read capacity 16 command.
- Fixed an issue where speed negotiation for 3Gig SATA drives is not handled
properly.
- Added Support for Report Luns Command
- Fixed an issue where OS hang during install of Linux system to a SSD
- Fixed an issue where SAS device page 0 may still be present for Initiator
devices that have been removed from the topology.
- Fixed an issue where RHEL 6.3 hangs during boot with IBM 600GB High IOPS MLC
Modular Adapter
- Fixed an issue where a non-PI volume made up of all PI capable drives, may
come up as PI enabled after a controller reset.
- Fixed an issue where a fault 0X8808 occurs when a reset is issued to the
controller that has max number of active/inactive volumes
- Fixed an issue where "Device Present" Flag of SAS device page0 is not set for
initiator controller in then target controller when two controllers are
connected to each other in initiator/target mode.
- Fixed an issue where extended tags and PCIe upconfigure capability are
disabled in SAS2208 and SAS2308.
- Fixed an issue where force full discovery does not trigger rediscovery of an
expander after the initial expander discovery fails.
- Fixed an issue where single RAID0 volume activation was succeeding, even
though controller does not support single drive RAID0.
- Fixed an issue where RAID1 volume of Non-PI drives moves to optimal state
when a PI drive is hotplugged and 'Enable PI mixing' not enabled.
- Fixed an issue where Locate LED's stop automatically after 3-4 minutes before
user issues command to turn off the Locate LED's.
- Fixed an issue where fault 0x8618 is seen when a new volume is created in
the presence of another volume which is undergoing resync along with IO.
- Fixed an issue background initialization does not start on RAID0 volume with
PI drives, after removing and reinserting a volume member.

BIOS
- Fixed an issue where core BIOS displays warning message when it fails to add
all of the drives connected to int13 chain, then waits for user to press any
key to continue further, rather than continuing after 3 seconds.
- Fixed an issue where incorrect adapter is being tagged as the first adapter
found.
- Fixed an issue where the save or discard changes prompt appears after a
failed attempt to set volume as the boot device in BIOS CU.
- Fixed an issue where BIOS CU provides incorrect device pointer when checking
for raid disk to allow/disallow setting boot device.
- Fixed an issue where device properties screen is invoked from a direct attach
device using Alt+D in SAS topology screen, device traversing [Alt+N & Alt+P]
is restricted within the direct attach device and expander attach devices are
not traversed.
- Fixed an issue where the drive status field does not show 'Max dsks' when
trying to select 11th drive for RAID10 volume.
- Fixed an issue maximum Int13 devices settings does not get honored, when the
value is set as 0 in BIOS CU
- Fixed an issue where drive size of 1.088GiB was showing as 1.880GiB.
- Fixed an issue current boot device set to device at slot 4" message Not
displaying for Adaptors with boot order other than 0.
- Fixed an issue where the BIOS CU navigates to create new volume screen
instead of back to raid properties screen.
- Fixed an issue where BIOS banner showed 'FF' for slot information.
- Fixed an issue where the drive's SMART status is always shown as no
irrespective of drive's SMART status, under Pred Fail column of the manage
hot spare screen and create new volume screen.
- Fixed an issue where SAS2 BIOS: volume size shows inconsistent value in the
create new volume' screen after selecting the last volume member.
- Fixed an issue where a disabled adapter causes the second adapter status to
show as unavailable even though the second adapter is enabled.
Uefi
Enhancement 1/2
- Added capability to create an IR RAID volume in non-PI mode, even when all
member drives are PI Capable.
- Added PI info and ability to control creation of PI Volume in UCM of BSD HII.
- Added new form manage PHY settings to support enabling or disabling of a
controller PH
Fixes:
- Fixed an issue view foreign volume option is disabled with a foreign volume
in the configuration.


Version 1.15 - Suggested
-------------
Contains:
BIOS Firmware UEFI Driver
7.29.01.00 15.00.00.00 7.22.04.00

BIOS Changes
Enhancement(s):
- Core BIOS and BIOS configuration utility will display "FF" as the PCI slot
number when proper slot information is not available.
- Increased the disk drive spin-up timeout value to accommodate disk drives
having larger spin up times.

Fix(es):
- Fixed an issue where the adapter order does not get written to NVM and
"Updating Adapter Order" displays on every reboot.
- Fixed issue where zero sized volume was showing "4. 0 GiB."
- Fixed issue where devices, which are not attached to adapter 0, could not be
promoted to positions in the boot order when they were selected in the
configuration utility.
- Fixed an issue where IOS Banner(POST) not showing SAS Discovery error
when more than one HBA is connected to the host system.
- Fixed an issue where the SMART status is not correctly displayed for bare
drives.
- Fixed an issue in SAS topology where a RAID disk is highlighted and attempted
to set as preferred boot device or alternate boot device, the configuration
utility displays a SAVE/DISCARD prompt.
- Fixed an issue where the firmware was showing a large elapsed time when a
format operation crosses midnight in the system clock.

Firmware Changes
Enhancement(s):
- Added support for 4GB DIMM
- Added the ability for user the enable/disable of the drive write cache
during the BIOS start up.

Fix(es):
- Fixed an issue where a request sense command, which is executed after a
SATA drive is in active state is moved to idle power condition state, has no 'Additional Sense' information set.
- Fixed an issue where protected information error "Logical block reference
tag check failed" is received when an IR volume is deleted.
- Fixed an issue Self-Test Results log page where values for update parameter
code, format and linking, and parameter length are not recorded.
- Fixed an issue sending vital product data inquiry with vital product data
page set as invalid (0xFF) while diagnostic is running on a SATA drive
results in segmentation fault 0x1901.
- Fixed an issue where input/output is sent to SATA drives before the drives
are ready.
- Fixed an issue where fault 8405 was being hit while disabling and enabling
the phy to which secondary drive is connected with IOs active.
- Fixed an issue where subsequent commands sent to a SATA drive fail after a
write same command failure until NCQ error handling is triggered or the device
is reset.
- Fixed an issue where Report Luns command sent to SATA drive fails if the
drive is spun down.
- Fixed an issue where hotspare does not resynch with second raid volume when
both volumes are in degraded state.
- Fixed an issue where incorrect sense data is populated when Security
Protocol IN/OUT command is sent to supported drive.
- Fixed an issue where allocation length for inquiry SCSI Command is not
handled Properly during SATA Drive Format.
- Fixed an issue during SATA drive format where vital product data inquiry
command is executed for SATA drive with invalid page code, and the command is passed with no data instead for failing with CC and sense data.
- Fixed an issue where the host will not indicate the existence of the
expander attached drives if the direct attached device re-ordering feature is enabled.
- Fixed an issue where protected information errors are observed on a RAID 1
volume its BGI is not completed, and its member physical disks are removed and inserted.
- Fixed an issue where the TM response was set to failed if the device is
missing due to the DO NOT SEND TASK IU flag being enabled.
- Fixed an issue where DMD (Device Missing Delay) timer is not set to the
default time when the total Report Device Missing Delay is greater than 0x7F
seconds.
- Fixed an issue where RAID1 volume fails to resynch when a new compatible
bare drive is available in the primary drive slot.
- Fixed an issue where error handling for errors, that cause the DMA engines
to halt, are not handled properly and multithreaded IOs can hang if the same
control block is used too soon.
- Fixed an issue where a third hotspare is created even if the number of
hotspares currently present in the RAID Configuration is 2.
- Fixed an issue where inactive foreign volume information cannot be seen in
SASBIOS when a native volume is deleted.

UEFI Changes
Enhancement(s)
- Additional information such as vendor id and product id added to
the HII Create Configuration Screen.
- Added ability to check to detect missing hotspares to HII.
- Modified to be obtained PCI Slot Number information from the
system firmware protected information.
- Additional character "M" will be displayed as part of the device
display identifier of a multipathed disk.
- Ability in HII to detect missing hotspares and provide a facility
to delete the missing hotspares.
- Implemented Configuration Summary and Simple Virtual Disk
Creation Support for Unified Configuration Management.
- Modified UEFI driver to wait for a maximum of 10 seconds for
the controller to become ready, so controller gets discovered in
the OS.

Fix(es):
- Fixed an issue where Enable/Disable write cache does not work for
SAS drives.
- Fixed an issue where HII Configuration utility does not allow
the user to create a RAID0 with single disk present in the topology.
- Fixed an issue in Create Configuration menu where additional drive
information is not getting updated appropriately in HELP area.
- Modified to prevent Write Cache settings options from appearing
for the IR firmware.
- Fixed an issue where SATA volume members and hotspare drives are
labeled as 'M' in a multipathed environment.
- Fixed an issue to prevent HII from allowing the option to
enable/disable write cache for SATA drives.
- Fixed an issue where multipathing is disabled in Manufacturing
page settings, but volume members and hotspare drives are
labeled as "M."
- UEFI driver modified to check BIOS Options in order to determine
if is should manage the controller.

Version 1.10.12 - Suggested
-------------
Contains:
BIOS Firmware UEFI Driver
7.19.00.00 10.00.11.00 7.18.04.04

Enhancement
- Add support for single drive RAID 0

Fixes
- Fixed an issue where PFA alerts are not seen in the IMM or CMM

Version 1.10.11 - Suggested
-------------
Contains:
BIOS Firmware UEFI Driver
7.19.00.00 10.00.08.00 7.18.04.04

UEFI Driver Fixes:
- Fixed a issue where the controller may not be seen in Linux operating
systems.
- Fixed issue where HII do not report Multi-LUN devices from external
RAID enclosure.
- Do not show external RAID LUNs in HII RAID configuration page.
- Report NVDATA version consistently in Hex or Decimal.

Version 1.10.09 - Suggested
-------------
Contains:
BIOS Firmware UEFI Driver
7.19.00.00 10.00.08.00 7.18.04.02

- Fixed an issue where BoFM will not function.
- Fixed an issue where external storage will not be seen by the LSI2004
controller.
- Fixed an issue where the user cannot create volumes with HII browser.
- Fixed an issue where the HII browser hangs while navigating forms.

Version 1.10.06 - Initial release
-------------
Contains:
BIOS Firmware UEFI Driver
7.19.00.00 10.00.08.00 7.18.01.11
ibm_fw_mpt2sas_hs23-1_20_02_windows_32-64_chg

Firmware Update for IBM High IOPS Modular Adapter

Controller Supported:
- IBM 300 GB High IOPS MLC Modular Adapter (90Y4361)
- IBM 600 GB High IOPS MLC Modular Adapter (90Y4365)
- IBM 800 GB High IOPS MLC Modular Adapter (90Y4369)
- IBM 300 GB High IOPS SLC Modular Adapter (90Y4373)


Version 7.30.05.00-1 - Non Critical
--------------------
- Package version number change. All code levels are the same as 7.30.05.00 package.

Version 7.30.05.00 - Initial release
------------------
ibm_fw_mptsss_hiop-7_30_05_00-1_windows_x86-64_chg

Intel® Chipset Device Software

Production Version 9.4.0.1026

Release Notes



August 8, 2013



Microsoft Windows* 2000

Microsoft Windows XP*

Microsoft Windows XP* Professional x64 Edition

Microsoft Windows Server* 2003

Microsoft Windows Server* 2003 x64 Edition

Microsoft Windows Vista* RTM and SP’s

Microsoft Windows Server* 2008 R2

Microsoft Windows Server* 2008 R2 x64 Edition

Microsoft Windows* 7

Microsoft Windows* 7 x64

Microsoft Windows* 8

Microsoft Windows* 8 x64

Microsoft Windows Server 2012

Microsoft Windows Server 2012 x64

Microsoft Windows* 8.1

Microsoft Windows* 8.1 x64

Microsoft Windows Server 2012 R2

Microsoft Windows Server 2012 R2 x64





INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT AS PROVIDED IN INTEL'S TERMS AND CONDITIONS OF SALE FOR SUCH PRODUCTS, INTEL ASSUMES NO LIABILITY WHATSOEVER AND INTEL DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF INTEL PRODUCTS INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR OTHER INTELLECTUAL PROPERTY RIGHT.

A "Mission Critical Application" is any application in which failure of the Intel Product could result, directly or indirectly, in personal injury or death. SHOULD YOU PURCHASE OR USE INTEL'S PRODUCTS FOR ANY SUCH MISSION CRITICAL APPLICATION, YOU SHALL INDEMNIFY AND HOLD INTEL AND ITS SUBSIDIARIES, SUBCONTRACTORS AND AFFILIATES, AND THE DIRECTORS, OFFICERS, AND EMPLOYEES OF EACH, HARMLESS AGAINST ALL CLAIMS COSTS, DAMAGES, AND EXPENSES AND REASONABLE ATTORNEYS' FEES ARISING OUT OF, DIRECTLY OR INDIRECTLY, ANY CLAIM OF PRODUCT LIABILITY, PERSONAL INJURY, OR DEATH ARISING IN ANY WAY OUT OF SUCH MISSION CRITICAL APPLICATION, WHETHER OR NOT INTEL OR ITS SUBCONTRACTOR WAS NEGLIGENT IN THE DESIGN, MANUFACTURE, OR WARNING OF THE INTEL PRODUCT OR ANY OF ITS PARTS.

Intel may make changes to specifications and product descriptions at any time, without notice. Designers must not rely on the absence or characteristics of any features or instructions marked "reserved" or "undefined". Intel reserves these for future definition and shall have no responsibility whatsoever for conflicts or incompatibilities arising from future changes to them. The information here is subject to change without notice. Do not finalize a design with this information.

The products described in this document may contain design defects or errors known as errata which may cause the product to deviate from published specifications. Current characterized errata are available on request.

Contact your local Intel sales office or your distributor to obtain the latest specifications and before placing your product order.

Code names featured are used internally within Intel to identify products that are in development and not yet publicly announced for release. Customers, licensees and other third parties are not authorized by Intel to use code names in advertising, promotion

The Intel® Chipset Device Software may contain design defects or errors described as “known issues” which may cause the product to deviate from expected performance. Current characterized known issues are documented in this update.

Intel and the Intel logo are trademarks of Intel Corporation in the U.S. and other countries.

*Other names and brands may be claimed as the property of others.

Copyright © 2013, Intel Corporation. All rights reserved.



Revision History

Date


Driver Revision


Description


Build Number

August 8,2013


9.4.0.1026


Production Version Build; fully validated


1026

July 29, 2013


9.4.0.1022


Production Version Build; fully validated


1022

February 27, 2013


9.4.0.1017


Production Version Build; fully validated


1017

January 16, 2013


9.4.0.1016


Production Version Build; fully validated


1016

January 11, 2013


9.4.0.1014


Production Version Build; fully validated


1014

December 14, 2012


9.4.0.1012


Beta Engineering Build; not fully validated


1012

October 23, 2012


9.4.0.1011


Beta Engineering Build; not fully validated


1011

September 11, 2012


9.4.0.1010


Beta Engineering Build; not fully validated


1010

June 27, 2012


9.4.0.1007


Alpha Engineering Build; not fully validated


1007

February 10, 2012


9.4.0.1003


Alpha Engineering Build; not fully validated


1003

September 23, 2011


9.4.0.1002


Pre-Alpha Engineering Build; not fully validated


1002





Intel® Chipset Device Software Support

The Intel® Chipset Device Software contains support for the following:

· Intel® 8 Series Chipset Family

· Intel® 7 Series Express Chipset

· Intel® 6 Series Express Chipsets

· Intel® 5 Series Chipsets

· Intel® 4 Series Chipsets

· Intel® 3400 Series Chipsets

· Intel® 3 Series Chipsets

· Intel® 900 Series Chipsets

· Intel® 800 Series Chipsets

· Intel® Server/Workstation Chipsets

· Intel® Xeon® Processor 5500/3500 series

· 4th Generation Intel® Core™ processor family

· 3rd Generation Intel® Core™ processor family

· 2nd Generation Intel® Core™ processor family



New Features



Features Added in Baseline 9.4.0.1026




No New feature added.




Features Added in Baseline 9.4.0.1022




ID


Description




1


Certified for Windows 8.1 support.


Added Intel Sensor Solution HWIDs duplicate for VEN_INT&DEV_33D1.

2


Added Intel Sensor Solution HWIDs duplicate for VEN_INT&DEV_33D1.




3


Added support for MUP specification 2.4.1.




Features Added in Baseline 9.4.0.1017




ID


Description




1


Updated Branding for devices 0c08, 8C56, 8C52, 8C54




Features Added in Baseline Production Version 9.4.0.1016




ID


Description




1


Fixed missing cat file lxptusb.cat, Ivytown.cat




Features Added in Baseline Production Version 9.4.0.1014




ID


Description




1


Updated Installer with new INFs for extract driver switch




2


Added device information for Intel sensor solution for Intel® 8 Series chipset family (previously code named Lynx Point-LP)




3


Fixed readme.txt




Features Added in Baseline Beta 9.4.0.1012




ID


Description




1


Added Crystal Well DID




2


Updated Branding for Intel® 8 Series chipset family devices (previously code named Lynx Point-LP)




Features Added in Baseline Beta 9.4.0.1010




ID


Description




1


Updated Readme with Windows 8 and Windows Server 2012 instructions




2


Updated all 4th Generation Intel® Core™ processor family and Intel® 8 Series chipset family devices with correct branding




3


Signed with HCK




Features Added in Baseline Alpha 9.4.0.1007




ID


Description




1


Updated Intel® 8 Series chipset family (previously code named Lynx Point-LP) Device IDs




Features Added in Baseline Alpha 9.4.0.1003




ID


Description




1


Updated 4th Generation Intel® Core™ processor family Devices




2


Added Intel Corporation Signing to all installation on Windows 8






Known Issues

Known Issues in Build 1026

ID


Description

1


When running the Chipset INF installer on Windows 8, Windows 8.1, Windows Server 2012, or Windows Server 2012 R2, there is a delay before any UI is displayed. This delay is usually approximately 2 minutes, but can be much more.

Known Issues in Build 1022

ID


Description

1


When running the Chipset INF installer on Windows 8, Windows 8.1, Windows Server 2012, or Windows Server 2012 R2, there is a delay before any UI is displayed. This delay is usually approximately 2 minutes, but can be much more.

Known Issues in Build 1017

ID


Description

1


Centerton files are 0 bytes




Issues Resolved

Issues Resolved in Build 1026

ID


Description

1


Fixed USB INF files contain errors

2


Various string fixes

3


Updated "PDH" to "PCH" in readme.

4


Updated section names

Issues Resolved in Build 1022

ID


Description

1


Fixed missing newline after branding string.

2


Fixed Chipset INF files not signed issue.

3


Fixed device 33D1 display string.

Issues Resolved in Build 1017

ID


Description

1


Fixed AHCI bug filed in MSFT Database [REG:113011610144431] Intel CCG: BSOD 0x7B after uninstalling Intel RST software.

2


Fixed Sensor Co-Installer issue (Sensor hub is not working because of incorrectly installed by Intel chipset software)

Issues Resolved in Build 1016

ID


Description

1


Fixed the error message “This computer currently contains software version … which is newer than the version you are about to install”

Issues Resolved in Build 1011

ID


Description

1


Fixes the error message “This computer does not meet the minimum requirement “ on double install/update chipset software

Issues Resolved in Build 1003

ID


Description

1


None


intc_dd_inteldp_9_4_0_1026_windows_32-64_chg

Dynamic System Analysis (DSA) Preboot Change History

Version 9.54, Build ID DSYTD8G
o Enhancement:
1. Embedded DSAp Simplification by removing Low-Value Functionality
- Inventory: BIST,PMC
- Diags: RSARST Diags, Tape Drive Diags, Optical Drive Diags,Check point (LED) Panel Diags
2. Heartbeat for F2 standalone memory test.
3. IBM High IOPS Adapter Raw Data Collection.
4. pDSA Simplification for FoD Function & GUI Client.
5. Add warning & report in client for nonsupport systems.
6. Change sFTP as the default protocol for transfer log to IBM Service.
7. Get standalone memory test results & SOL support for DSAp(for security efi boot).
8. Update openssl to 1.0.1h from 1.0.1g.
o Limitations:
1. After finish run all diagnostics in 25 loop with Emulex 10G options, DSA log will show abnormal,
it only record Diags log one time on DSA Diagnostics Completion Log.
2. On GUI, when two ports of the machine want to connect the Extranet at the same time, the machine could not send dsa log to IBM server.
you can click test internet connection to solve the problem.
3. System not show event log item in chassis event log & ipmi event log page when trigger SBE in standalone mode.
o Special usage:
- 2014 IMMV2 2QLFC Product Build

Version 9.43, Build ID DSYTC8E
o Enhancement:
1. Preboot GUI redesign and enhancement--refine GUI into more customer friendly style.
2. FoD Support--FoD key re-activation.
3. pDSA proxy auto-config retrieve.
o Limitations:
1. DSA Does not support "VMware ESXi" page report for ESXi 5.x key due to "vmvisor-offline-query" limitaion .
o Special usage:
- 2013 IMMV2 4QLFC

Version 9.33, Build ID DSYTB6E
o Limitations:
When we want to flash from B5E to B6E, we should level down to AA3 or AA4 first.


Version 9.30, Build ID DSYTB27
o New System Support:
Flex System x440 Compute Node (7917, 2584)
IBM System x3300 M4 (7382)
o Problem(s) Fixed:
1. PMR - 05766,YL2,760
Aenservice appeared after running UpdateXpress & DSA.
2. PMR - 05193,W01,000
7147 - Intermittent random PSOD in vmware. multiple

o Enhancement: None
o Limitations:
- FIFO test of NIC diagnostics is not supported on the Intel I350 Quad Port GbE.
Powerville has shared FIFO and shared FIFO registers making a test impossible
if four ports are running at once.
- For more limitations please refer to readme.
o Special usage:
- 2012 ToolsCenter 12D

Version 9.29, Build ID DSYTAB6
o New System Support:
Flex System x440 Compute Node (7917, 2584)
o Problem(s) Fixed: None
o Enhancement: None
o Limitations:
- DSA implemented signature in product build. Please update IMM to 1AOO34V or later before updating pDSA,
or flash failure will occur;
- The user can not flash Embedded Preboot on VMware ESX3.5 prior to U4.
- When flashing DSA Preboot using wflash/lflash, if you notice a
build mismatch error, please make sure IMM firmware level is
minimum 29B. Once you upgrade the IMM firmware to 29B or higher,
DSA Preboot will continue to flash without error;
- For more limitations please refer to readme.
o Special usage:
- NGP-4Q(12B+ FixPack3)

Version 9.28, Build ID DSYTAA4
o New System Support:
x3630 M4 (7519)
x3550 M4 (7383)
o Problem(s) Fixed: None
o Enhancement: None
o Limitations:
- DSA implemented signature in product build. Please update IMM to 1AOO34V or later before updating pDSA,
or flash failure will occur;
- The user can not flash Embedded Preboot on VMware ESX3.5 prior to U4.
- When flashing DSA Preboot using wflash/lflash, if you notice a
build mismatch error, please make sure IMM firmware level is
minimum 29B. Once you upgrade the IMM firmware to 29B or higher,
DSA Preboot will continue to flash without error;
- For more limitations please refer to readme.
o Special usage:
- IMMV2 system 2012 4Q-LFC

Version 9.27, Build ID DSYTA7F
o New System Support: None
o Problem(s) Fixed: None
o Enhancement: None
o Limitations:
Refer to readme
o Special usage:
- IMMv1 system 2012 4Q-LFC

Version 9.26, Build ID DSYTA6G
o New System Support: None
o Problem(s) Fixed: None
o Enhancement:
DSA Performance Optimization
o Limitations:
Refer to readme
o Special usage:
- 2012 ToolsCenter 12C

Version 9.21, Build ID DSYTA1U
o New System Support: None
o Problem(s) Fixed:
1.Recovered LSI Rawdata: "MegaCli -FwTermLog -Dsply -aALL"
o Enhancement: None
o Limitations:
Refer to readme
o Special usage:
- 2012 ToolsCenter 12B Plus

Version 9.20, Build ID DSYTA0R
o New System Support:
x3530 M4 (7160)
x3630 M4 (7158)
x3750 M4 (8722, 8733)
HS23E (8038, 8039)
Flex System x220 Compute Node (7906, 2585)
o Problem(s) Fixed:
1. PMR 05819,YL2,760
An error occured during the execution of DSA on Windows,
DSA exits with an error at the eventlog plugin.
o Enhancement:
1. Add HW remote presence key collection for High volume systems.
o Limitations:
Refer to readme
o Special usage:
- 2012 ToolsCenter 12B

Version 9.07, Build ID DSYT9CA
o New System Support:
x3750 M4 (8722, 8733)
o Problem(s) Fixed: None
o Enhancement: None
o Limitations: None
o Special usage: None

Version 9.06, Build ID DSYT9BC
o New System Support:
Flex System x220 Compute Node (7906)
o Problem(s) Fixed: None
o Enhancement: None
o Limitations: None
o Special usage: None

Version 9.05, Build ID DSYT9AA
o New System Support:
x3630 M4 (7158)
x3530 M4 (7160)
x3100 M4 Refresh1 (2582)
x3250 M4 Refresh1 (2583)
o Problem(s) Fixed: None
o Enhancement: None
o Limitations: None
o Special usage: None

Version 9.04, Build ID DSYT99E
o New System Support:
Flex System x240 Compute Node (8737, 8738, 7863)
o Problem(s) Fixed: None
o Enhancement: None
o Limitations: None
o Special usage: None

Version 9.03, Build ID DSYT98I
o New System Support:
HS23E (8038, 8039)
o Problem(s) Fixed: None
o Enhancement: None
o Limitations: None
o Special usage: None

Version 9.02, Build ID DSYT97C
o New System Support:
iDataPlex dx360 M4 server/2U chassis (7912/7913)
o Problem(s) Fixed: None
o Enhancement: None
o Limitations: None
o Special usage: None

Version 9.01, Build ID DSYT96D
o New System Support:
x3500 M4 (7383)
x3550 M4 (7914)
x3650 M4 (7915)
o Problem(s) Fixed:
o Enhancement: None
o Limitations: None
o Special usage: None

Version 9.00, Build ID DSYT95W
o New System Support:
BladeCenter HS23 (7875)
BladeCenter HX5 (7873, 1910)
Flex System x240 Compute Node (8737, 8738, 7863)
Flex System Manager Node (8735)
x3500 M4 (7383)
x3550 M4 (7914)
x3630 M4 (7158)
x3650 M4 (7915)
x3690 X5 (7192, 7147)
x3850 X5 / x3950 X5 (7143, 7191)
o Problem(s) Fixed:
1. PMR 24817,8QG,000, PMR 30680,499,000
After kicking off DSA on one of the management nodes (x3650 M2) of
SONAS 1.2(RHEL5 based), the node became unresponsive and dropped
out of the cluster.

2. PMR 53575,000,834, PMR 05961,YL4,760
After running DSA, when using linux dump command on a DDS5 usb internal
tape drive attached in x3650M2 backup speed becomes very slowly or failed.

3. PMR 26905,095,866
Running DSA 4.0 as well as DSA 3.4 on x3850 X5 the server is freezing,
users have to reboot the server.

4. DSA 4.00 and previous version segmentation fault issue

5. PMR 05148,6M4,760
DSA v4 unexpectedly create IMM virtual switch

6. PMR 15086,OTH,760
DSA 9.00 with --no-imm-lan option does not work correctly
on RHEL5.3. The USB port state is changed during the execution of DSA.

o Enhancement:
1. Add GUI and CLI menu for Features on Demand (FoD) Activation Key Management
o Limitations:
Refer to readme.
o Special usage: None

Version 4.02, Build ID DSYT92I
o New System Support:
iDataPlex Direct Water Cooled dx360 M4 server
o Problem(s) Fixed: None
o Enhancement: None
o Limitations:
Refer to readme.
o Special usage: None

Version 4.01, Build ID DSYT92H
o New System Support: None
o Problem(s) Fixed: None
o Enhancement: None
o Limitations:
Refer to readme.
o Special usage:
- 2011 4Q lifecycle

Version 4.00, Build ID DSYT91S
o New System Support: None
o New server options support: None
o Problem(s) Fixed:
1. PMR 15065,OTR,760
On Unisys ES7000 or x3850 X5, the Memory Card number with failed DIMM
can not be reported in IPMI Eventlog if the Memory Card is bigger than 4.

o Enhancement:
1. Added > 1TB memory test support
o Limitations:
Refer to readme.
o Special usage:
- 2011 ToolsCenter 11D

Version 3.48, Build ID DSYT89PUS
o New System Support: None
o Problem(s) Fixed: None
o Enhancement: None
o Limitations:
Refer to readme.
o Special usage:
- 2011 3Q lifecycle

Version 3.47, Build ID DSYT89LUS
o New System Support:
x3100 M4 (2582)
x3250 M4 (2583)
o Problem(s) Fixed: None
o Enhancement: None
o Limitations:
Refer to readme.
o Special usage: None

Version 3.46, Build ID DSYT89GUS
o New System Support:
System x iDataPlex dx360 M3 (6391)
o Problem(s) Fixed: None
o Enhancement: None
o Limitations:
Refer to readme.
o Special usage: None

Version 3.45, Build ID DSYT89EUS
o New System Support: None
o Problem(s) Fixed: None
o Enhancement: None
o Limitations:
Refer to readme.
o Special usage:
- x3850 X5 / x3950 X5 (7143, 7191) EXA scaling

Version 3.43, Build ID DSYT87HUS
o New System Support:
BladeCenter HX5 (7873,1910)
o Problem(s) Fixed: None
o Enhancement: None
o Limitations:
Refer to readme.
o Special usage: None

Version 3.43, Build ID DSYT87FUS
o New System Support:
x3850 X5 / x3950 X5 (7143, 7191)
x3690 X5 (7192, 7147)
o Problem(s) Fixed:
o Enhancement: None
o Limitations:
Refer to readme.
o Special usage: None

Version 3.40, Build ID DSYT85T
o New System Support:
BladeCenter HS22 (1911)
x3650 M3 (5454)
o Problem(s) Fixed: None
o Enhancement: None
o Limitations:
Refer to readme.
o Special usage: None

Version 3.30, Build ID DSYT80S
o New System Support: None
o Problem(s) Fixed: None
o Enhancement:
1. Correct a problem with LSI MegaRAID reporting for IBM Service
o Limitations:
Refer to readme.
o Special usage: None

Version 3.20, Build ID DSYT75X
o New System Support:
x3630 M3 (7377)
x3690 X5 (7148, 7149)
o Problem(s) Fixed: None
o Enhancement:
1. Add LSI Hard Disk Drive (HDD) diagnostic back for both the onboard SAS chip and ServeRAID
o Limitations:
- If you have ServeRAID (M1015) SAS/SATA Controller, 46M0831
installed, you will need one of the following:
- uEFI GYE133A or greater for x3200 M3 and x3250 M3
- uEFI Y4E145B or greater for x3400 M2, x3400 M3, x3500 M2 and x3500 M3
- uEFI D6E145C or greater for x3550 M2, x3550 M3, x3650 M2 and x3650 M3
- For more limitations please refer to readme
o Special usage: None

Verion 3.20, Build ID DSYT75U
o New System Support:
x3755 M3 (7164)
o Problem(s) Fixed: None
o Enhancement: None
o Limitations: None
o Special usage: None

Verion 3.10, Build ID DSYT70X
o New System Support:
x3400 M3(7378, 7379)
x3500 M3(7380)
x3550 M3 (7944, 4254)
x3620 M3 (7376)
x3650 M3 (7945, 4255)
x3690 X5 (7148, 7149)
x3850 X5 Standard Single-node and Multi-node models(7145, 7146)
x3950 X5 Specially configured Database Engine models (7145, 7146)
iDataplex dx360 M3 (6391)
HS22V (7871,1949)
HX5 (7872, 1909)
o Problem(s) Fixed: None
o Enhancement:
1. Added ServeRAID data collection
o Limitations:
- The following function has been temporarily removed from DSA
Preboot for both the onboard SAS chip and ServeRAID:
- LSI Hard Disk Drive (HDD) diagnostic
- If you have ServeRAID (M1015) SAS/SATA Controller, 46M0831
installed, you will need one of the following:
- uEFI GYE133A or greater for x3200 M3 and x3250 M3
- uEFI Y4E145B or greater for x3400 M2, x3400 M3, x3500 M2 and x3500 M3
- uEFI D6E145C or greater for x3550 M2, x3550 M3, x3650 M2 and x3650 M3
- For more limitations please refer to readme
o Special usage: None

Version 3.02.56, Build ID DSYT56e
o New System Support: None
o Problem(s) Fixed: None
o Enhancement:
- The following systems are supported when BoMC downloads the
corresponding system enablement pack:
HS22V (7871,1949)
x3550 M3 (7944,4254)
x3650 M3 (7945,4255)
x3400 M3 (7378,7379)
x3500 M3 (7839)
dx360 M3 (6391)
o Limitations:
- No HDD diagnostics available
- To ensure quality and stability of the DSA code, we have
reverted some display functionality of RAID information to
what was shown in previous versions of DSA. This affects RAID
display on the following adapters:
Megaraid 8480
Serveraid MR10i
Serveraid MR10is
Serveraid MR10m
Serveraid MR10k
Serveraid M1015
Serveraid M5014
Serveraid M5015
On these adapters, the RAID information is generated from the
output of separate command line tools and the format may not
match other output in DSA.
- For more limitations please refer to readme
o Special usage: None

Version 3.00, Build ID: DSYT55a
o New System Support: None
o Problem(s) Fixed: None
o Enhancement:
- Added support for Machine Types 7327, 7328, 4251, 4252, 4261
o Limitations:
- No HDD diagnostics available
- For more limitations please refer to readme
o Special usage: None

Version 1.16, Y4YT19AUS
o New System Support: None
o Problem(s) Fixed: None
o Enhancement:
- Added support for Machine Types 7839, 7836, 7837
o Limitations: None
o Special usage: None

Version 1.15, TMYT20AUS
o New System Support: None
o Problem(s) Fixed: None
o Enhancement:
- Added support for Machine Types 7321, 6380, 7323
o Limitations: None
o Special usage: None

Version 1.14, D6YT37AUS
o New System Support: None
o Problem(s) Fixed: None
o Enhancement:
- Added support for Machine Types 7946, 4198, 7947, 4199
o Limitations: None
o Special usage: None

Version 1.13, P9YT48AUS
o New System Support: None
o Problem(s) Fixed: None
o Enhancement:
- Added support for Machine Types 7870, 1936, 7809
o Limitations: None
o Special usage: None

Version 1.00
- Initial release

(C) Copyright International Business Machines Corporation 2008 - 2014.
All rights reserved.
ibm_fw_dsa_dsytd8g-9_54_anyos_anycpu_chg

Integrated Management Module II (IMM2) Firmware Update
Change History

Version 5.60, 1AOO72H - NonCritical
- Supports systems:
HS23, HS23E, x3100 M4, x3100 M5, x3250 M4, x3250 M5, x3300 M4, x3500 M4,
x3530 M4, x3550 M4, x3630 M4, x3650 M4, x3650 M4 BD, x3650 M4 HD, x3750 M4,
x3850 X6, x3950 X6, dx360 M4, nx360 M4, x220, x222, x240, x440, x280, x480,
x880
- Firmware changes to address security vulnerabilities:
CVE-2015-5219, CVE-2015-5300, CVE-2016-0778, CVE-2015-3194, CVE-2015-3195,
CVE-2015-3196, CVE-2015-7981, CVE-2015-8126, CVE-2016-0705, CVE-2016-0797,
CVE-2016-0799, CVE-2015-8472, CVE-2015-8126, CVE-2015-8710, CVE-2016-0755
- Added support to filter out invalid drive information from the RAID controller
- Fixed a problem on the x3750 M4 that causes the IMM to report a power supply mismatch fault
- Fixed a problem that causes the IMM to unexpectedly reset on the x3850 X6 and x3950 X6
- Fixed a problem with the power capping settings that causes the x3850 x6 to power off
- Fixed a problem that causes the configuration restore operation to fail when the
system has 12 network ports.
- Fixed a problem where the IMM reports a system volume fault and the x3550 M4 cannot be powered on
- Added changes to make the firmware more robust and avoid hang conditions.
- Added changes to enhance DSA/OneCLI IPMI-LAN access.

Version 5.41, 1AOO70I - Critical
- Supports systems:
x3550 M4
- Firmware improvement to address a potential reliability issue for a voltage regulator.
Not updating to this level could lead to a failed system board. Please refer to tip HT 118532.

Version 5.40, 1AOO70H - Critical
- Supports systems:
HS23, HS23E, x3100 M4, x3100 M5, x3250 M4, x3250 M5, x3300 M4, x3500 M4,
x3530 M4, x3550 M4, x3630 M4, x3650 M4, x3650 M4 BD, x3650 M4 HD, x3750 M4,
x3850 X6, x3950 X6, dx360 M4, nx360 M4, x220, x222, x240, x440, x280, x480,
x880
- Firmware changes to address security vulnerabilities:
CVE-2015-7575, CVE-2016-0777, CVE-2016-0778
- Corrected a problem that prevented Lenovo XClarity Administrator from
authenticating with the IMM2
- Fixed a problem on the x3850 X6 where the server unexpectedly reboots after
an IMM2 reset
- Fixed a problem on the x480 X6 that causes the CMM to report an 'unknown' IO
connectivity status
- Fixed a problem on the x3650 M4 that causes fan3 and fan4 to run at incorrect
speeds
- Fixed a problem that prevented the IMM2 gateway setting from being changed on
the IMM2 web and in the UEFI menu.
- Fixed a problem on the x3650 M4 where LDAP authentication does not work

Version 5.20, 1AOO68L - Critical
- Supports systems:
HS23, HS23E, x3100 M4, x3100 M5, x3250 M4, x3250 M5, x3300 M4, x3500 M4,
x3530 M4, x3550 M4, x3630 M4, x3650 M4, x3650 M4 BD, x3650 M4 HD, x3750 M4,
x3850 X6, x3950 X6, dx360 M4, nx360 M4, x240, x440, x280, x480, x880
- Firmware changes to address security vulnerabilities:
CVE-2013-2207, CVE-2013-4508, CVE-2013-4559, CVE-2013-4560, CVE-2014-5352,
CVE-2014-5353, CVE-2014-5355, CVE-2014-8121, CVE-2014-8176, CVE-2014-9421,
CVE-2014-9422, CVE-2015-1349, CVE-2015-1781, CVE-2015-1788, CVE-2015-1789,
CVE-2015-1790, CVE-2015-1791, CVE-2015-1792, CVE-2015-1799, CVE-2015-3216,
CVE-2015-3405, CVE-2015-4000, CVE-2015-4171, CVE-2015-4620, CVE-2015-5477,
CVE-2015-5600, CVE-2015-5722
- Re-enabled the EDH cipher for the LDAP client
- Fixed a problem on x3550 M4 where MSM connectivity issue on X3650 M4 and
X3550 M4 with ESXi 5.5 u2 on IMM v4.97
- Fixed a problem where setting NIST800-131A mode on the web, CLI, and SNMP is
inconsistent
- Fixed a problem where the signed certificate status on the web and the CLI
does not match
- Fixed a problem on x3650 M4 where the "NvDIMM Status & Cables" sensor does
not de-assert
- Fixed a problem where the DIMM's Manufacturer ID information is not displayed
- Fixed a problem where the password is not changed after setting the password
via OneCLI
- Fixed a problem where a user cannot log using LDAP Active Directory
Application Mode
- Fixed a problem on x3850 X6 where the IMM2 does not detect power supply
faults and over-temperature conditions
- Fixed a problem on x3500 M4/x3550 M4/x3650 M4/x3650 M4 HD where the IMM2
reports power supply configuration mismatch assertion and deassertion events
within seconds
- Re-enabled TLS1.0/TSL1.1 support for the web and WS-MAN interfaces when the
IMM2 is in NIST mode
- Fixed a problem on x3100 M4/x3250 M4 where there is no alert message logged
when AC power is lost

Version 4.97, 1AOO66M - NonCritical
- Supported Platforms:
HS23, HS23E, x3100 M4, x3100 M5, x3250 M4, x3250 M5, x3300 M4, x3500 M4,
x3530 M4, x3550 M4, x3630 M4, x3650 M4, x3650 M4 BD, x3650 M4 HD, x3750 M4,
x3850 X6, x3950 X6, dx360 M4, nx360 M4
- NOTE: To avoid possible exploits of the vulnerabilities discovered with SSLv3
encryption, support for SSLv3 has been removed from the IMM2 firmware. To
access the IMM2 web interface using https, users must make use of client
browser versions that support TLS1.2 encryption.
Refer to RETAIN Tip H214507 for details.
- After applying this firmware update all subsequent self-signed certificates
are generated using SHA-2 cryptographic hashes. Certificate signing requests
are also generated using SHA-2 cryptographic hashes if the IMM2 is configured
to run in NIST SP 800-131A Compliance mode.
- Critical Fix for x3750 M4
-- Fixed issue on missing power supply redundancy lost event
- Firmware changes to address security vulnerabilities:
CVE-2013-2566, CVE-2013-2877, CVE-2013-4332, CVE-2013-4854, CVE-2013-6435,
CVE-2014-0191, CVE-2014-3505, CVE-2014-3506, CVE-2014-3507, CVE-2014-3508,
CVE-2014-3509, CVE-2014-3510, CVE-2014-3511, CVE-2014-3513, CVE-2014-3566,
CVE-2014-3567, CVE-2014-3568, CVE-2014-3569, CVE-2014-3570, CVE-2014-3571,
CVE-2014-3572, CVE-2014-3634, CVE-2014-3660, CVE-2014-3683, CVE-2014-8118,
CVE-2014-8275, CVE-2014-8500, CVE-2014-9293, CVE-2014-9294, CVE-2014-9295,
CVE-2014-9297, CVE-2014-9298, CVE-2015-0204, CVE-2015-0205, CVE-2015-0206,
CVE-2015-0235, CVE-2015-2808, CVE-2013-7423, CVE-2014-5352, CVE-2014-7817,
CVE-2014-9402, CVE-2014-9421, CVE-2014-9422, CVE-2014-9423, CVE-2015-0209,
CVE-2015-0286, CVE-2015-0287, CVE-2015-0288, CVE-2015-0289, CVE-2015-0292,
CVE-2015-0293, CVE-2015-1472
- Fixed a problem that IMM2 unable to detect event from redundant PSU
on x3250 M4
- Fixed a problem that PSU 1 and PSU 2 will show changed after hot swap
on x3250 M4
- Fixed a problem that FAN will rotate in high speed when booting on 3100 M4
- Fixed a problem that IMM2 LDAP connects to AD server three time simultaneously
for each login attempts with wrong password
- Fixed a problem that Fan operates abnormally in S5 mode after rebooting system
on x3550 M4
- Fixed a problem that "ipmitool chassis status" reporting false drive fault on
System x3650 M4
- Fixed a problem that IMM firmware version 4.56 display as 4.55 in DSA log and
UEFI data
- Fixed a problem that IMM2 cannot log events on x3550 M4
- Fixed a problem that IMM2 may reset due to potential memory leakage
- Fixed a problem that failure to send the alert of IMM2 via e-mail
- Fixed a problem on IBM NeXtScale nx360 M4 for where the IMM may intermittently
report an incorrect DC value to IBM NeXtScale n1200 Fan and Power Control (FPC)
- Fixed a problem on NI152 x3650M4 where the IMM may report a power supply
configuration mismatch error message in the system event log

Version 4.90, 1AOO66O - NonCritical
- Firmware changes to address security vulnerabilities:
CVE-2013-2566, CVE-2013-2877, CVE-2013-4332, CVE-2013-4854, CVE-2013-6435,
CVE-2014-0191, CVE-2014-3505, CVE-2014-3506, CVE-2014-3507, CVE-2014-3508,
CVE-2014-3509, CVE-2014-3510, CVE-2014-3511, CVE-2014-3513, CVE-2014-3566,
CVE-2014-3567, CVE-2014-3568, CVE-2014-3569, CVE-2014-3570, CVE-2014-3571,
CVE-2014-3572, CVE-2014-3634, CVE-2014-3660, CVE-2014-3683, CVE-2014-8118,
CVE-2014-8275, CVE-2014-8500, CVE-2014-9293, CVE-2014-9294, CVE-2014-9295,
CVE-2014-9297, CVE-2014-9298, CVE-2015-0204, CVE-2015-0205, CVE-2015-0206,
CVE-2015-0235, CVE-2015-2808
- Fixed a problem that IMM firmware version 4.56 displays as 4.55 in DSA log and
UEFI data.
- Fixed a problem that IMM2 may reset due to a potential memory leakage.
- Fixed a cooling issue when the Fusion IO adapter is present
- Fixed a problem where the IMM2 LDAP authentication attempts to connect to an
AD server three times simultaneously for each login attempt with a
wrong password.
- Fixed a problem that may cause the IMM2 to fail to send an alert via e-mail.
- To support new security requirements the IMM firmware now requires the Java
remote presence client to be at version 1.8 or newer

Version 4.80, 1AOO64T - NonCritical
- Supports IBM System x3850/x3950 X6, Machine Type: 3837, 3839
- Fixed potential problem where Service Advisor not functional when routing
through a proxy server

Version 4.61, 1AOO64Y - NonCritical
- Fixed a problem on IBM NeXtScale nx360 M4 for intermittent IPMB IO error
and ME error.
- Fixed a problem on IBM NeXtScale nx360 M4 for unexpected shutdown due to
CPU over temperature

Version 4.60, 1AOO64P - NonCritical
- Firmware changes to address security vulnerabilities:
CVE-2014-3508 CVE-2014-3509 CVE-2014-3505 CVE-2014-3506 CVE-2014-3507
CVE-2014-3510 CVE-2014-3511 CVE-2013-2174 CVE-2013-4545 CVE-2014-0015
CVE-2014-0138 CVE-2014-0139 CVE-2014-2653 CVE-2014-2532
- Closed network port 121.

Version 4.58, 1AOO64V - Critical
- Critical Fix for x3630 M4, x3530 M4, x3300 M4, x3650 M4 BD
-- Removed an incorrect error message sometimes displayed when certain
RAID adapters are installed in certain PCIe slots

Version 4.56, 1AOO64S - Critical
- Critical Fix for x3650 M4, x3650 M4 HD, x3650 M4 BD, x3500 M4, x3630 M4,
x3530 M4, x3300 M4
-- Fixed issue on missing power supply redundancy lost event

Version 4.55, 1AOO64N - NonCritical
- Firmware changes to address security vulnerabilities:
CVE-2014-3508, CVE-2014-3509, CVE-2014-3505, CVE-2014-3506, CVE-2014-3507,
CVE-2014-3510, CVE-2014-3511, CVE-2013-2174, CVE-2013-4545, CVE-2014-0015,
CVE-2014-0138, CVE-2014-0139, CVE-2014-2653, CVE-2014-2532
- Closed network port 121.
- Fixed a problem of I2C error on x3500 M4 systems with use of Fairmont Raid
card with FW version 23.22.0-0024 and IMM 1AOO58T
- Thermal behavior enhancement on System x iDataPlex dx360 M4
- Fixed a problem that Call Home function was not working with a Proxy server

Version 4.50, 1AOO64L - NonCritical
- Updated the firmware with patches to address the OpenSSL vulnerabilities
listed in CVE-2014-3509, CVE-2014-3506, CVE-2014-3507, CVE-2014-3505,
CVE-2014-3508, CVE-2014-3510, CVE-2014-3511, CVE-2013-2174, CVE-2013-4545,
CVE-2014-0015, CVE-2014-0138, CVE-2014-0139, CVE-2014-2653, CVE-2014-2532
- Fixed a problem where an erroneous event could be logged for an expansion
card that would be followed by a recovery message several seconds later.
- Fixed an issue with the web interface that could show a firmware update has
failed if the user leaves the web interface inactive for over 20 minutes
after downloading the update file.
- Corrected an issue that might cause erroneous faults to be reported for the
ServeRAID M5115 SAS/SATA when the server power is off.
- Fixed an issue for multinode partition capable systems where when switching
between partition and stand-alone modes repeatedly while also powering the
nodes on and off, the IMM2 mode information could get out of sync with the
server.

Version 4.35, 1AOO62W - Refresh Release
- Support for refresh of the System x3650 M4 BD, Machine Type: 5466

Version 4.31, 1AOO58T - Critical
- Critical Fix for x3650M4, x3550M4, x3500M4, dx360M4, x3100 M4, x3250m4,
x3750M4, x3650M4 HD, x3630M4, x3530M4, x3300M4, x3250M5
-- Updated the firmware with patches to address the OpenSSL vulnerabilities
listed in CVE-2014-0224, CVE-2014-0221, CVE-2014-0195, CVE-2014-3470,
CVE-2010-5298, CVE-2014-0198
- Added option to export the certificate signing request in PEM format
- Various Remote Presence enhancements including:
-- Support for a MAC OS-x client
-- Scaled video viewer window
-- ASU set up of Remote Presence hot keys
-- Virtual media mounting via URL
- Removed potentially sensitive information from the service data file
- Fixed a problem on x3650 M4, x3550 M4, x3500 M4, x3650 M4 HD where the
IMM2 may not detect a loss of power supply redundancy
- Fixed a problem where the LDAP group filter does not support a full DN
- Fixed a problem where the syslog alert fields "Msg Type" and "Severity"
did not follow RFC 5424
- Fixed a problem where the IMM2 only supported the default network port
for syslog notifications
- Fixed a problem where the SNMP "sysName" query always returns the string
"SNMP Service" instead of the system name
- Fixed a problem where the Global Login Settings changes were lost after
an IMM2 restart

Important: Before you flash the IMM2 firmware back to version 3.82 or older, set
the IMM2 Security option to use the Basic Compatibility Mode. This will prevent a
possible loss of access to the IMM2.

Version 4.23, 1AOO62Z - Initial Release
- Adds support for System x880 X6, Machine Type: 4259, 7903

Version 4.21, 1AOO58U - NonCritical
- Updated the firmware with patches to address the OpenSSL vulnerabilities
listed in CVE-2014-0224, CVE-2014-0221, CVE-2014-0195, CVE-2014-3470,
CVE-2010-5298, CVE-2014-0198

Version 4.20, 1AOO58R - NonCritical
- Fixed an issue in I2C communications that could cause CMM to
report, "FPGA Host 2 Communication is offline"
- Fixed a problem that required the browser cache to be cleared
before accessing IMM2 web page.
- Corrected a problem that caused the CMM to reporting an I/O
connectivity problem with the FSM
- Enhanced the IMM2 service and support data to better aid in the
diagnosis of VPD issues
- Added support for the S3 system sleep state
- Added support for agentless monitoring of PCIe devices
- Enabled a Flex compute node to be powered on sooner after installation
in the chassis
- Added RFC compliance checking for user input
- Ensured consistency in Daylight Savings Time setting between the CMM
and IMM2
- Added support for enhanced hard drive monitoring and status
- Corrected an issue that caused false reports of
incorrect / missing / corrupt VPD events.

Version 4.15, 1AOO58K - Suggested
- Added support for the BIE (Blade IO Expansion Board) on the HS23, HS23E
- Fixed a problem that prevented the AMM from controlling power when local
power control is disabled on the HS23, HS23E

Version 4.10, 1AOO58F - Initial Release
- Supports System x3100 M5, Machine Type: 5457

Version 4.04, 1AOO64E - NonCritical
- Supports IBM System x3850/x3950 X6, Machine Type: 3837, 3839
- Fixed potential problem where Memory Details on Critical DIMM points to a
different location
- Fixed potential problem for power state mismatching when one node transitions
from AC disconnected to AC connected while the other node is powered up

Version 4.02, 1AOO58S - NonCritical
- Supports IBM System x3850/x3950 X6, Machine Type: 3837, 3839
- Fixed a potential problem where a single CPU and single Power Supply model may
show a configuration error
- Fixed a potential problem where fans running at high speed under normal
operation may erroneously log a fan failure
- Updated the firmware with patches to address the OpenSSL vulnerabilities
listed in CVE-2014-0224, CVE-2014-0221, CVE-2014-0195, CVE-2014-3470,
CVE-2010-5298, CVE-2014-0198
- Fixed a power state change problem when removing a Compute book with an
I/O book attached
- Fixed a problem where PCIE adapters in I/O books may not show up after an
OS reboot

Version 4.00, 1AOO58I - NonCritical
- Supports IBM System x3850/x3950 X6, Machine Type: 3837, 3839
- Add Scalable support.
- x3950 X6 initial GA support level
- Add support for enhanced hard drive monitoring and status
- Fixed a potential problem that may cause the IMM to reboot in a configuration
with multiple single port network cards.

Version 3.91, 1AOO58G - Critical
- Supports System x3750 M4, Machine Type: 8752, 8718
- Add a feature to allow users to block power control from the power button
on the x3750M4

Version 3.90, 1AOO54X - NonCritical
- Added support for the IBM NeXtScale PCIe Native Expansion
(NeX) Tray for IBM NeXtScale nx360 M4

Version 3.86, 1AOO56V - Critical
- Critical Fix for x3500 M4
-- Updated the firmware with patches to address the OpenSSL vulnerabilities
listed in CVE-2014-0224, CVE-2014-0221, CVE-2014-0195, CVE-2014-3470,
CVE-2010-5298, CVE-2014-0198

Version 3.85, 1AOO56U - Critical
- Critical Fix for x220, x222, x240, x440, Flex System Manager Node
-- Updated the firmware with patches to address the OpenSSL vulnerabilities
listed in CVE-2014-0224, CVE-2014-0221, CVE-2014-0195, CVE-2014-3470,
CVE-2010-5298, CVE-2014-0198

Version 3.84, 1AOO56J - Critical
- Critical Fix for x3300 M4
-- Updated the firmware with patches to address the 'Heartbleed'
OpenSSL bug (CVE-2014-0160)

Version 3.83, 1AOO56I - Critical
- Critical Fix for x3250 M5, nx360 M4
-- Updated the firmware with patches to address the 'Heartbleed'
OpenSSL bug (CVE-2014-0160)

Version 3.82, 1AOO56E - Critical
- Critical Fix for x3850 X6 / x3950 X6
-- Updated the firmware with patches to address the 'Heartbleed'
OpenSSL bug (CVE-2014-0160)

Version 3.81, 1AOO52Z - Critical
- Critical fix:
-- Corrected the x3850/x3950 x6 server to turn off
power from the power supplies when a power fault occurs

Version 3.80, 1AOO52U - Initial Release
- Supports IBM System x3850/x3950 X6, Machine Type: 3837, 3839
- up to 4 CPU in one system
- x3850 X6 initial GA support level

Version 3.79, 1AOO56G - Critical
- Critical Fix for x240, x222, x440, x220, Flex System Manager Node
-- Updated the firmware with patches to address the 'Heartbleed'
OpenSSL bug (CVE-2014-0160)

Version 3.78, 1AOO52Y - Critical
- Critical Fixes:
-- Fixed a potential security vulnerability with information contained
in service data (refer to security bulletin CVE-2014-0882)
-- Fixed a potential security vulnerability with Trusted Platform
Module (TPM) initialization settings (refer to security bulletin
CVE-2014-0881)

Version 3.77, 1AOO56H - Critical
- Critical Fix for x3630 M4, x3530 M4
-- Updated the firmware with patches to address the 'Heartbleed'
OpenSSL bug (CVE-2014-0160)

Version 3.76, 1AOO56Q - Critical
- Critical Fix for x3650 M4 BD
-- Updated the firmware with patches to address the OpenSSL vulnerabilities
listed in CVE-2014-0224, CVE-2014-0221, CVE-2014-0195, CVE-2014-3470,
CVE-2010-5298, CVE-2014-0198

Version 3.75, 1AOO56F - Critical
- Critical Fix for x3650 M4 BD
-- Updated the firmware with patches to address the 'Heartbleed'
OpenSSL bug (CVE-2014-0160)

Version 3.74, 1AOO52R - Critical
- Critical Fix:
-- Fixed a potential security vulnerability with information contained
in service data (refer to security bulletin CVE-2014-0882)
- Supports System x3650 M4 BD, Machine Type: 5466

Version 3.73, 1AOO56D - Critical
- Critical Fix for:
dx360 M4, x3650 M4, x3550 M4, x3500 M4, x3100 M4, x3250 M4, x3750 M4
-- Updated the firmware with patches to address the 'Heartbleed'
OpenSSL bug (CVE-2014-0160)

Version 3.71, 1AOO52W - Critical
- Critical Fix for x3550 M4:
-- Fixed a potential security vulnerability with information contained
in service data (refer to security bulletin CVE-2014-0882)
-- Fixed a problem system may shut down with new Mezz card installed

Version 3.70, 1AOO52Q - Critical
- Critical Fix:
-- Fixed a potential security vulnerability with information contained
in service data (refer to security bulletin CVE-2014-0882)

Version 3.67, 1AOO50G - Initial Release
- Supports System x3650 M4 BD, Machine Type: 5466

Version 3.65, 1AOO50D - Suggested
NOTE: If you have a System x3550 M4 with the "Emulex VFA Mezz card" and a
==== single processor, don't update the IMM2 with this firmware
- Critical Fix:
-- Fixed a problem on the System x3650 M4 server where the system
shuts down due to a false temperature event from the ambient temperature
sensor
- Fixed a problem where the IMM2 may erroneously report a fan fault in the
x3630 M4 when the system is powering on. See RETAIN tip H207461 for the
description of the original problem
- Fixed a screen refresh problem where it occurs after resetting IMM2
- Fixed a firmware problem that may cause the IMM2 to reset unexpectedly
- Fixed a problem where the IMM2 SNMP interface may intermittently be
unavailable if the system is running VMWARE ESXi 5.x
- Fixed a problem where the CPU may potentially throttle in the x3650 M4
system with two 550 watt power supplies and one hard drive backplane

Version 3.60, 1AOO50C - Suggested
- Added support for the Intel IvyBridge-EP CPU on the HS23 blade
- Fixed a problem where the HS23 hard drive number reported in the AMM
event did not match the drive number on the physical blade enclosure
- Fixed an intermittent problem where the UXSPI update utility may
erroneously report that the firmware image is not meant for the
HS23 system
- Fixed a problem that causes the AMM web interface to not display
properly when drives are removed or inserted
- Fixed a problem where the IMM2 may not detect an over temperature
condition for a DIMM
- Corrected a problem that caused the IMM to report an
"Unsupported blade/blower combination" error on HS23

Version 3.56, 1AOO50K - Critical
- Fixed a Flex Systems Manager (FSM) Configuration Patterns problem
where configuration deployments would fail with an activation job
error message:
ERROR: LDAP failed with rc=102
ERROR: LDAP failure: SYSPROF_LDAP_BIND_FAIL INFO

Version 3.55, 1AOO50E - Suggested
- Fixed an issue so a fully qualified domain name can be used for a
syslog collector in addition to an IP address
- Fixed an issue to allow a user the ability to specify the port to
use for syslog notifications, rather than only supporting the default
port

Version 3.50, 1AOO50B - Suggested
- Fixed an issue where the default static IPv4 address was assigned to
the IMM2 management interface instead of the user configured static
IPv4 address in DHCP fallback to static mode, if the DHCP server
was not available
- Prevent a VLAN from being configured on the IMM2 management interface
for Flex nodes
- Fixed a problem where the CPU throttling state recovery indication to
the FSM might not be properly reported
- Corrected an issue with the launch of the IMM2 Remote Console operation
that required a restart of the IMM2
- Corrected the firmware to apply the inactivity timeout to web pages
that automatically refresh
- Updated the web browser support. The following web browsers are supported:
Firefox 3.6-20
Chrome 13-26
Internet Explorer 8-10
- Added support for the S3 Sleeping State to the IMM2 user interfaces
on those servers that include the S3 feature
- Added changes to use the minimum TLS version setting that is provisioned
by the CMM in Flex for encrypted communication
- Enhanced the content of the service data file to assist in problem
determination
- Added a option to have the IMM2 automatically copy the firmware from
its primary bank into the backup bank after the firmware has been run
for a period of time and proven itself to be stable
- Enhanced the IMM2 firmware to automatically restore itself without
the need for user intervention if the firmware becomes corrupted
- Added new commands on the command line interface to stop a serial
redirection operation that is currently in progress, and to report
the user names that have a serial redirection operation started
- Added changes to use the DNS settings that are provisioned by the CMM
in Flex to support use of an LDAP hostname for authentication
- Updated the firmware to log hardware inventory change informational
messages
- Added support for the Service Advisor feature on stand alone rack
servers to automatically call for service when a repair is needed
- Added support to configure the Ethernet-over-USB IP address using ASU
- Added changes to support the thermal requirements for new Solid State
Drives used with the ServeRAID M5100 Series IBM Flex System Flash Kit v2
- Updated the IMM2 date and time web page on Flex nodes to only display
the current date and time
- Updated the SSH firmware to address various OpenSSH vulnerabilities that
have been identified by security community
- Added changes to support the Web Services-Management protocol

Version 3.40, 1AOO48M - Initial Release
- Supports System x3250 M5, Machine Type: 5458

Version 3.37, 1AOO48P - Suggested
- Added support for the IBM NeXtScale Storage Native Expansion
(NeX) Tray for IBM NeXtScale nx360 M4

Version 3.36, 1AOO48Q - Critical
- Fixed a problem on System x iDataPlex dx360M4 where a CIM client
cannot get needed event information for asserted events

Version 3.35, 1AOO48N - Critical
- Critical Fix:
-- Corrected a problem on the System x3650 M4 and x3650 M4 HD servers
causing the system to shut down due to an erroneous critical
temperature event reported by the ambient temperature sensor

Version 3.30, 1AOO48L - NonCritical
- Fixed a problem on System x iDataPlex dx360M4 where nodes shutdown
due to a critical temperature event from the Ambient Temp sensor

Version 3.20, 1AOO48K - Initial Release
- Supports System NeXtScale nx360 M4, Machine Type: 5455

Version 3.10, 1AOO48H - NonCritical
- Added support for System x3650 M4 HD, Machine Type 5460
- Added support for newer CPUs in the System x iDataPlex dx360M4,
x3500M4, x3550M4, and x3650M4 servers
- Added a feature on the System x3550 M4 and x3650 M4 to fail over
from the dedicated systems management network port to the shared
port when the dedicated network link is not available
- Fixed a problem where an NTP update message is logged every 1440
minutes
- Fixed a problem where the IMM2 web interface won't accept an NTP
hostname string that starts with a numeric character
- Fixed a problem where the LDAP Group Filter authentication does
not work as expected
- Fixed a problem where the IMM2 reports 0 Watts when the System x
iDataPlex dx360M4 is DC cycled or resumes from the S3 sleep state
- Fixed an Ethernet problem that may cause an IMM2 failure to establish
a link when the Ethernet speed and duplex settings are not configured
to use auto-negotiation

Version 2.62, 1AOO56T - Critical
- Critical Fix for x220, x222, x240, x440, Flex System Manager Node
-- Updated the firmware with patches to address the OpenSSL vulnerabilities
listed in CVE-2014-0224, CVE-2014-0221, CVE-2014-0195, CVE-2014-3470,
CVE-2010-5298, CVE-2014-0198

Version 2.61, 1AOO44V - Critical
- Critical Fix for x240, x220, x440, x222, Flex System Manager Node
-- Updated the firmware with patches to address the 'Heartbleed'
OpenSSL bug (CVE-2014-0160)

Version 2.60, 1AOO42Y - NonCritical
NOTE: For increased security, only high strength ciphers are now
supported when using https.

==== Your browser must support one of the following cipher suites:
|
DHE-RSA-AES256-SHA256 TLSv1.2 Kx=DH Au=RSA Enc=AES(256) Mac=SHA256
DHE-RSA-AES256-SHA SSLv3 Kx=DH Au=RSA Enc=AES(256) Mac=SHA1
AES256-SHA256 TLSv1.2 Kx=RSA Au=RSA Enc=AES(256) Mac=SHA256
AES256-SHA SSLv3 Kx=RSA Au=RSA Enc=AES(256) Mac=SHA1
DHE-RSA-AES128-SHA256 TLSv1.2 Kx=DH Au=RSA Enc=AES(128) Mac=SHA256
DHE-RSA-AES128-SHA SSLv3 Kx=DH Au=RSA Enc=AES(128) Mac=SHA1
AES128-SHA256 TLSv1.2 Kx=RSA Au=RSA Enc=AES(128) Mac=SHA256
AES128-SHA SSLv3 Kx=RSA Au=RSA Enc=AES(128) Mac=SHA1

- Added support for the IBM Flex System x222 Compute Node
- Improved Remote Presence (keyboard, mouse and virtual media)and
in-band management (LAN-over-USB) performance
- Changed the default file name for the Service Data file (First
Failure Data Capture or FFDC) on the web interface to incorporate
the machine type, serial number and a timestamp
- Updated the IMM2 PCIe Bridge Firmware to support Windows 2012
Certification
- Improved IMM2 Reliability, Availability, Serviceability (RAS)
Features:
- Added component and system VPD integrity checking & reporting
- Enhanced Service Data collection (FFDC)

- Enhanced the configuration of UEFI settings via the CIM interface
for applications like IBM Systems Director
- Added Sub-manufacturer inventory support for mezz card and
Sub-manufacturer inventory support for the system for IBM Systems
Director
- Added the UUID for the PCIe Expansion Node and the Storage
Expansion Node to the SLP attributes reported by the IMM2
- Added the number of enabled CPU core and the Static power savings
mode support for IBM Systems Director
- Enhanced the alert recipient email notification, firmware update,
event log, log out, and hardware information web pages to improve
usability
- Added support for IPMI & SNMPv3 accounts to be centrally managed
by the Flex Chassis Management Module
- Fixed a problem where an invalid configuration was erroneously
reported for an unpopulated CPU socket in the IBM Flex System
x440
- Enabled users to configure a longer trespass message
- Increased the length of the LDAP group filter field to 511
characters
- Corrected a problem with ServeRAID M5115 SAS/SATA Controller
for IBM Flex Systems energy pack monitoring
- Corrected a problem with ServeRAID M5115 SAS/SATA Controller
for IBM Flex Systems LED management
- Added IPMI command to configure the LAN-over-USB IP address

Version 2.52, 1AOO42E - Critical
- Critical Fix:
-- Fixed a problem on the System x3300 M4 servers causing the system
to shut down due to a critical temperature event reported by the
ambient temperature sensor

Version 2.50, 1AOO40Z - Suggested
- Added support for the Solarflare SFN5162F MR Dual Port 10GbE SFP+
Adapter, and Solarflare SFN6122F LL Dual Port 10GbE SFP+ Adapter
for System x3550 M4 and x3650 M4
NOTE: UEFI also needs to be upgraded to D7E128B (v 1.40 or newer,
for the x3550 M4) or VVE128B (v1.40 or newer, for the x3650 M4) to
support these cards
- Added support for the Mellanox ConnectX-3 Dual Port QDR/FDR10
mezzanine card and Mellanox ConnectX-3 VPI Single-port QSFsorry.P
FDR14/40GbE HCA on System x3550 M4, and x3650 M4
- Added optional Fan Zone support for single CPU systems (x3550 M4
and x3650 M4) with an installed with Qlogic Dual Port 10GbE SFP+
Embedded VFA
- Fixed an intermittent problem where a Gratuitous ARP is not sent
successfully
- Fixed a problem where after the IMM2 firmware is flashed, there is
a slight chance that the IMM2 web server can't be accessed when AC
power is reapplied
- Disabled the weak cipher suit used in the SSL/TLS firmware with the
https protocol to avoid potential security vulnerabilities
- Fixed a problem on the System x3750 M4 where the IMM2 shared mode
network connection will be lost after upgrading the firmware of the
onboard Emulex BE3 controller
- Fixed a problem on the HS23 where the OS watchdog timer doesn't work
- Fixed a problem on the HS23 where the Fault LED occasionally lights
when the chassis is powered on with the BPE4
- Fixed a problem on the HS23 where the server may shut down after
resetting the IMM2
- Enhanced the messaging mechanism between the BladeCenter AMM and
the IMM2
- Added power management capability in the IMM2 web interface

Version 2.06, 1AOO42B - Critical
- Corrected the firmware to prevent users from disabling the IPv6 interface
- Fixed a problem that caused the IMM2 to reset itself after running for a
period of time
- Corrected the SNMP request to disable the IMM2 IPv4 interface so that it
disables only IPV4, instead of both IPv4 and IPv6
- Fixed a problem that occasionally caused the server to shut down when the
IMM2 is reset
- Fixed a problem where the IMM2 incorrectly reported a battery voltage error
- Corrected a problem where repeated frequent IMM2 resets causes the IMM2 to
run the firmware in its backup partition
- Corrected a problem report where the IMM2 did not report a failure to the
system profiles script when the chassis UUID is unavailable

Version 2.00, 1AOO40E - Critical
- Critical Fix:
-- Improves the reliability of the CPU and/or memory VRDs. This improvement
lowers the occurrence of CPU & memory VRD failures on the x3300 M4 and
x3750 M4
-- IMM2 improved error reporting for missing/down CPU in invalid CPU
configuration for x4440 M4
- Corrected a problem that caused 3.3V and 5V faults to be reported by IMM2
firmware level 1AOO34Z(1.85) on the HS23E blade
- Eagle Ray SAS controller LED fault support improvements added for all ITE
platforms

Version 1.97, 1AOO36R - Critical
- Critical Fix:
-- Improves the reliability of the CPU and/or memory VRDs. This improvement
lowers the occurrence of CPU & memory VRD failures on x3650 M4, x3550 M4
and x3500 M4
- Thermal behavior enhancement on System x iDataPlex dx360 M4

Version 1.95, 1AOO36P (for System x iDataPlex servers) - Suggested
- Added support for NVIDIA K1,K2,K20,K20x GPUs on System x iDataPlex dx360 M4

Version 1.88, 1AOO40A (for PureFlex System Compute Nodes) - Critical
- Critical Fix:
-- Fixed a potential security vulnerability with node management user
accounts (Reference to Security Bulletin CVE-2012-4838)
- Fixed a problem on Flex Systems where the SNMP get and set authority levels
did not work
- Fixed a problem on Flex Systems where mounting of remote media in a Linux
environment showed a USB error
- Fixed a problem on Flex Systems that caused the Remote Control Video Viewer
window on a RHEL5.8 client to move when the arrow key is pressed
- Fixed a problem on Flex Systems where the SMTP "Test Connection" button did
not work when the SMTP port is changed
- Fixed a problem on Flex Systems where the SNMP get and set authority levels
did not work
- Fixed a problem on Flex Systems where mounting of remote media in a Linux
environment showed a USB error
- Fixed a problem on Flex Systems that caused the Remote Control Video Viewer
window on a RHEL5.8 client to move when the arrow key is pressed
- Fixed a problem on Flex Systems where the SMTP "Test Connection" button did
not work when the SMTP port is changed
- Corrected the Mezzanine card power fault monitoring on the Flex System x440
Compute Node
- Corrected a problem with IBM Fabric Manager configuration from the Flex
Chassis Management Module
- Added support to retrieve configuration settings from an LDAP server
- Added support for the Flex Storage Expansion Node
- Added support for CIM indications over https
- Added fingerprint checking for SFTP transfers
- Added automatic recovery of corrupted UEFI firmware
- Added support for authenticated SMTP alerts
- Added a display of the users who have a Remote Control session in progress
- Provided a request to a Remote Control client to disconnect the session
- Added support for the server S3 (sleep) state
- Changed the default NTP sync interval from 3 minutes to 24 hours
- Fixed a problem where the ambient temperature is only displayed in degrees
Fahrenheit
- Fixed a problem on the web interface where 'local' is not accepted as a top
level domain name in the email format when configuring event recipients
- Corrected an IMM2 SNMP trap OID to match the prior IMM format
- Fixed a problem that prevented an external USB device from being remotely
mounted as a floppy drive in Windows Server 2003
- Changed the blue Location led behavior to not blink when a firmware update is
in progress

IMPORTANT NOTICE:
For X3300 M4, it is required to upgrade both the primary and backup IMM2
firmware to Version 1.86, 1AOO40D or later. After the IMM2 is successfully
updated, it is highly recommended to run the following IPMI command:
Get device id (ipmitool raw 6 1)
If the last two bytes returned show 0x2A 0x41 even after a reset of the IMM2,
please refer to TDR-H207183 or MIGR-5092140 for more information.

Version 1.86, 1AOO40D - Critical
- Critical Fix:
-- Fixed a problem where the X3300 M4 system configured with a M5110/M5120
RAID card plus the "IBM ServeRAID M5100 Series 512MB/1 gigabytes (GB)
Flash/RAID 5 Upgrade for IBM System x" option might have problem if
AC power is removed while the system is running

Version 1.85, 1AOO34Z (for BladeCenter blades and System x Servers) - Critical
- Critical Fix:
-- Fixed a potential security vulnerability with node management user
accounts (Reference to Security Bulletin CVE-2012-4838)
- Fixed a problem where a Blade Open Fabric Manager uncorrectable error can
occur when booting the HS23
- Fixed a problem that IMM IPMI command periodically timed out when using HS23
in Chassis with the management network being disabled in some special
configurations
- Added support for the HS23 to recognize NEBS/Enterprise Mode for Telco
chassis (this feature needs Advanced Management Module Firmware BPET62U or
later)
- Fixed a problem where the ambient temperature is only displayed in degrees
Fahrenheit
- Fixed a problem where on rack systems that have 2 power supplies installed,
the 'Redundancy Power unit has been restored' event is logged every time
that the IMM2 is reset
- Fixed a problem where a Fan Tach going low (lower critical) event is
intermittently asserted when configuring the IMM2 to use an NTP server
- Fixed a problem on the web interface where 'local' is not accepted as a top
level domain name in the email format when configuring event recipients
- Corrected an IMM2 SNMP trap OID to match the prior IMM format
- Fixed a problem that prevented an external USB device from being remotely
mounted as a floppy drive in Windows Server 2003
- Changed the blue Location led behavior to not blink when a firmware update is
in progress
- Fixed a problem on the HS23E that causes Preboot DSA to hang in CLI mode when
a user accesses it using Serial over LAN
- Fixed a problem on rack servers where ASU cannot set IMM.GRP_GroupName.1
and IMM.GRP_GroupName.2 if the string length is 16 characters or longer.
The firmware was corrected to allow a maximum length of 64 characters
- Added support for CIM indications over https
- Added fingerprint checking for SFTP transfers
- Added automatic recovery of corrupted UEFI firmware
- Added support for authenticated SMTP alerts
- Added a display of the users who have a Remote Control session in progress
- Provided a request to a Remote Control client to disconnect the session
- Added support for the server S3 (sleep) state

Version 1.85, 1AOO34Y (for PureFlex System V7000 Storage Node) - Initial Release
- Added support for Flex System V7000 Storage Node

Version 1.79, 1AOO36F - Suggested
- Thermal behavior enhancement on System x iDataPlex dx360 M4

Version 1.78, 1AOO36E - Suggested
- Thermal behavior enhancement for 115W & 95W CPU on System x iDataPlex dx360 M4
- Added support for the Intel KNC 5110p card

Version 1.77, 1AOO32X - Critical
- Thermal behavior enhancement for 115W CPU on System x iDataPlex dx360 M4

Version 1.75, 1AOO32S - Suggested
- Fixed a problem that a PCI uncorrectable error occurs when using HS23 with
CFFh card (44W4479) in the BCS chassis
- Fixed a problem where an "Unsupported blade/blower combination" error is
reported when using the HS23 in the BCHT chassis configured in Enterprise mode
- Fixed a problem in System x3530 M4, where the reported Active Energy Manager
input/output power readings are inaccurate
- Fixed a problem in System x3530 M4, x3630 M4, where an LDAP account can not
login using the AD_CrossDomain tree
- Fixed a problem in System x3530 M4, x3630 M4, where a user cannot use the "DNS
to Find LDAP server/Extract search domain from login ID" setting from the IMM2
web to access an eDirectory server
- Added support for Common Form Factor power supplies Oversubscription in System
x3750 M4, Machine Types: 8722, 8733

Version 1.65, 1AOO32O - Suggested
- Support the power supply Over-Subscription feature
- Support the 750 Watt DC power supply for System x3650 M4,x3550 M4
- Support IBM 1.2TB High IOPS MLC Mono Adapter, IBM 2.4TB High IOPS MLC Duo
Adapter for System x3650 M4, x3550 M4
- Support IBM LLM-SM Dual Port 10GbE SFP+ Adapter for System x3650 M4
- Fixed an abnormal Fan Zone recovery problem
- Fixed a problem that IMM2 Email notification doesn't support an e-mail address
with the underscore '_' character
- Fixed a power policy "Restore" problem
- Fixed a problem where the LDAP hostname can't be changed by ASU
- Fixed a problem that the length of email address (for SNMP notification) is
limited to 32 characters

Version 1.60, 1AOO32P - Suggested
- Fixed a problem where the Chassis Management Module cannot correctly
get the Mezzanine card information for the Flex System x220 Compute Node
- Fixed a problem where the PreBoot DSA firmware could not be updated under
VMWare ESXi 5 through the Flex System Manager's Update Manager
- Fixed a problem where an IMM2 communications error can occur if an unexpected
response causes VMware to spawn multiple processes when it does not receive
the data it expects from the IMM2

Version 1.59, 1AOO32K - Initial Release
- Supports System x3300 M4, Machine Types: 7382

Version 1.53, 1AOO30Z - Critical
- Included an update to the FPGA that fixes an intermittent issue
where the CPUs do not show up in a system with a RAID card installed,
when the AC is removed and reapplied from the server without allowing
sufficient time for the system hardware to completely discharge

Version 1.52, 1AOO34A - Suggested
- Added redundant power supply and hot swap hard drive support in
System x3100 M4

Version 1.51, 1AOO30Y - Critical
- Support for NVIDIA Tesla K10, M2070Q, M2090 GPU cards on System x
iDataPlex dx360 M4
- Fixed a problem in System x iDataPlex dx360 M4 where the password expires
after creating a new user in the IMM2 web interface
- Fixed a problem in System x iDataPlex dx360 M4, when the memory sensor changes
from 'critical' to 'warning,' but the severity is not updated in the syslog or
the email notification

Version 1.50, 1AOO30W - Suggested
- Supports System HS23, Machine Types: 7875,1929
- Supports System x3650 M4, Machine Types: 7915
- Supports System x3550 M4, Machine Types: 7914
- Supports System x3500 M4, Machine Types: 7383
- Added support for the Intel Xeon E5-2643 processor on the HS23 in
BCH-R3, BCS and BCHT chassis
- Fixed a problem where the IMM2 incorrectly logged an "Unsupported
blade/blower combination" on the HS23 in the BC-E 8677 chassis
- Fixed a power restore problem on systems that have 2 Delta power
supplies installed
- Fixed a problem in System x3650 M4, x3550 M4, x3500 M4, where OpenLDAP
Group Authentication filtering function doesn't work
- Fixed a problem in System x3650 M4, x3550 M4, x3500 M4, where LDAP
account can not login using the AD_CrossDomain tree

Version 1.45, 1AOO28S - NonCritical
- Fixed a problem in Flex System x220 where the Chassis Management
Module (CMM) Command Line Interface can't display the Mezzanine
card information
- Fixed a problem in Flex System x220 and x240 where the prebootDSA
firmware cannot be updated through Flex System Manager's Update
Manager

Version 1.40, 1AOO30T - Initial Release
- Supports System x3750 M4, Machine Types: 8722, 8733

Version 1.38, 1AOO30D - Initial Release
- Supports System x3630 M4, Machine Type: 7158
- Supports System x3530 M4, Machine Type: 7160

Version 1.36, 1AOO30P - Initial Release
- Fixed an intermittent remote media failure in system HS23E
- Fixed a problem in system HS23E where remote media does not work
when two or more users have concurrent remote control sessions

Version 1.34, 1AOO28Q - Initial Release
- Supports Flex System Manager Node, Machine Type: 8731
- Supports Flex System x240 Compute Node, Machine Types: 7863, 8737, 8738
- Supports Flex System x220 Compute Node, Machine Types: 2585, 7906

Version 1.32, 1AOO28N - Critical
- Supports System x3630 M4, Machine Type: 7158
- Supports System x3530 M4, Machine Type: 7160
- Fixed a problem that may see unexpected fan events after power on
in x3100 M4 and x3250 M4 systems
- Enhanced robustness on I2C bus test

Version 1.26, 1AOO26N - Initial Release
- Supports System x3650 M4, Machine Types: 7915

Version 1.25, 1AOO26K - Initial Release
- Supports System x3550 M4, Machine Types: 7914
- Supports System x3500 M4, Machine Types: 7383
- Supports System x iDataPlex dx360 M4, Machine Types: 7912,7913

Version 1.22, 1AOO26O - Suggested
- Supports System HS23, Machine Types: 7875,1929
Problems Fixed:
- Fixed a problem where the BOFM configuration may be lost after a
blade power cycle
- Fixed an LED error indication that occurs on the BPE4
- Fixed a problem where the Info LED lights during the discovery stage
- Fixed a problem where an ABR event is not logged
- Fixed an intermittent communication problem between the AMM and IMM2
- Fixed a problem that causes the remote media function to hang when a
second user attempts to mount remote media
- Fixed a problem where the 'break' keyboard function doesn't work with
Serial Over LAN

Version 1.21, 1AOO26L - Initial Release
- Supports System HS23, Machine Types: 7875,1929

Version 1.05, 1AOO10K - Initial Release
- Fixed the false alert issue in redundant PSU model

Version 1.00, 1AOO10I - Initial Release
- Initial Release
- Supports System x3250 M4, Machine Types: 2583,2587
- Supports System x3100 M4, Machine Types: 2582,2586


(C) Copyright International Business Machines Corporation 2008 - 2016.
All rights reserved.

ibm_fw_imm2_1aoo72h-5_60_bc-anyos_noarch_chg