This release note and the software that accompanies it are copyright (c) 2013, 
Intel Corporation or its suppliers, and may only be installed and used in accordance 
with the license that accompanies the software.

This Software is furnished under license and may only be used or copied in accordance with 
the terms of that license. No license, express or implied, by estoppel or otherwise, 
to any intellectual property rights is granted by this document. The Software is subject to 
change without notice, and should not be construed as a commitment by Intel Corporation or its suppliers to market, 
license, sell or support any product or technology. Unless otherwise provided for in the license under which 
this Software is provided, the Software is provided AS IS, with no warranties of any kind, express or implied. 
Except as expressly permitted by the Software license, neither Intel Corporation nor its suppliers assumes any 
responsibility or liability for any errors or inaccuracies that may appear herein. Except as expressly permitted by 
the Software license, no part of the Software may be reproduced, stored in a retrieval system, transmitted in any form, 
or distributed by any means without the express written consent of Intel Corporation.

==========================
Supported RAID Controllers
==========================
This download supports Intel(R) RAID controllers using SAS software stack (RS25SB008, RS25NB008), please verify that this utility has been tested with the RAID card you have chosen to use by checking the drivers web page for your controller at http://www.intel.com/support/.

===================
Package Information
===================
Flash package = v23.6.1-0018 (firmware version 3.330.05-2793)

==========
Attention!
==========
Intel recommends to loading Factory Default setting after the firmware upgrade which will not affect data on any existing array. 
To do so:
1. Reboot the system and login to the RAID BIOS Console. 
2. Select the controller and select 'Adapter Properties'->'Next'
3. Set the 'Set Factory Defaults' setting to 'Yes' and submit the change.
4. Reboot the system (the default settings are applied).
5. Re-configure to the desired settings in RAID Web Console2.

==================
Known Restrictions
==================
1) This download does NOT support EFI v1.1 environment. Please use the EFI shell commander which will display the EFI version, 
to identify the EFI version.
2) When 2 or more VDs are created, VD cache settings must be the same.


=======================
Contents on the package 
=======================
The following files are included in this zip:

Name:								Description:
ir3_2208-HADAS_FWPKG-v23.6.1-0018_readme.txt			This file
2208cs11.rom							Firmware binary
update.bat							DOS firmware update batch file
update.nsh							UEFI firmware update batch file
CmdTool2\DOS\*							DOS update utility and support files 
CmdTool2\FreeBSD\*						FreeBSD update utility and support files
CmdTool2\Linux\*						Linux update utility and support files
CmdTool2\Solaris\*						Solaris update utility and support files
CmdTool2\UEFI\*							UEFI update utility and support files
CmdTool2\Windows\*						Windows update utility and support files
License_v2.pdf							License Agreement
COPYING.NEWLIB.txt						License Agreement


==========================
Installation instructions:
==========================

UEFI (EFI 2.0) instructions for updating RAID Firmware:
-----------------
   1. Download and extract all files to a local drive.
   2. Boot the target system to EFI shell. 
   3. Change directory to the local drive and directory containing the flash update files and the firmware image file.
   4. Type "update.nsh" or "efi\cmdtool2 -adpfwflash -f 2208cs11.rom -noverchk -aall"
   5. Wait for the flash to complete. Do NOT reboot the system during the update.

Windows and Linux instructions for updating RAID Firmware:
-----------------
The firmware update may be run from Within Windows or Linux using the appropriate versions of CmdTool2.
  In Windows, unzip the utility into the same directory as the rom file by typing 
      "cmdtool2 -adpfwflash -f 2208cs11.rom -aall". 
  The Linux CmdTool2 by running the rpm and then calling the utility from /opt/MegaRAID/CmdTool2 as 
      "./CmdTool2 -AdpFwFlash -f 2208cs11.rom -aall"

DOS instructions for updating RAID Firmware:
-----------------
   1. Download and extract all files to a local drive.
   2. Boot the target system to DOS. 
   3. Change directory to the local drive and directory containing the flash update files and the firmware image file.
   4. Type "update.bat" or "dos\cmdtool2 -adpfwflash -f 2208cs11.rom -aall"
   5. Wait for the flash to complete. Do NOT reboot the system during the update.

You can also use RAID Web Console 2 to update the RAID firmware. For more detail, please refer to the Intel(R) RAID Software User's Guide.


=============
Fixes/Updates 
=============
Package v23.6.1-0018 - (HADAS 1.1)
	Firmware Package: 23.6.1-0018
	WebBIOS 6.1-67-e_67-Rel 
	Firmware 3.330.05-2793
	ROMENV 1.08
	PCLI 05.06.03
	BootBlock 2.05.00.00-0009
	NVDATA 2.1210.03-0116
	BootBlockCommon 07.26.26.219
	UEFI_Driver 0x06000500
	HII 04.00.01.00
	BIOS 5.43.00

Fixed Firmware Issues
- Disable adding PD FailHistory entries into DDF when maintain PD FailHistory is FALSE
- Shared Raid5 virtual drive became foreign configuration when owner node was rebooted.
- Cleanup Patrol Read debug prints
- Backing out the changes associated to the original defect CQ 475243 because data corruption was found, and will be reworked using CQ 480315.
- Firmware asserts when delete the reconstruction Logical drive (LD)
- Insert removed pds with maintain PD failhistory enabled and still see PD rebuilding
- Changing unconfigured bad drive to unconfigured good did not reflect on the peer nodeSCGCQ00437514 
- Firmware hits ASSERT when running I/O from client and move group every five minutes.
- The failover is skipped and take the error path when doing single path failover.
- cache version increment is not working
- Firmware hits kill adapter when the user issues online firmware update command to the controller
- Firmware faults when Turn OFF/ON Enclosure
- Unsupported SAS drive only show in one node
- Fimware hits ASSERT when reboot peer node
- Target mode error handling print improvements for debugging and minor bug fixes
- Some configured drives were not imported during failover when shutting down a node.
- In Linux* one node can't boot back to OS after shutting down both nodes.
- The receiving node (peer) found ACCESS BLOCK after cable pull and reconnect with IOs running on client
- MegaRAID firmware hit fault code 0xd05 after failover and Turn OFF/ON enclosure
- HA firmware fails to unregister a non-target MegaRAID initiator when it goes into safe mode
- PD fail history entries get cleared when CRC errors occur
- Unnecessary rebuild initiated during a Logical Drive(LD) Failover creating dummy foreign configurations.
- With PD Fail History enabled, unconfigured bad drives that have been marked unconfigured good may be remarked unconfigured bad
- Pinned cache reported only on one node after reboot (expected behavour is both nodes)
- In Linux - After initiating a Planned Failover from Debugger, found foreign configuration
- HII Browser did not update after pull online drives
- Firmware hits an ASSERT when internal utility is used to crash one node
- Boot target Id is inconsistent across Nvram and Disk Data Format (DDF)
- During the recovery of IO Shipped request the device driver is sending firmware a OCR(online controller reset)SCGCQ00464888 - (Closed) - Internal firmware error encountered if a virtual disk (VD) goes to offline state during failover
- Firmware faults when updating enclosure firmware using StorCli .
- ACCESS BLOCK after a peer discovery generated planned failover due to cache version mismatch
- Code Cleanup - Peer Arb not granted during Unplanned Failover
- Data Miscompare found while running i/o overnight with degraded virtual drives
- Write-policy of non-shared volume changes to write-through by failover
- Firmware messages keep rolling when a node enters safe mode.
- Pinned cache is reported when booting a server while the other server is performing reconstruction operations
- Firmware faults when releasing peer block
- Enclosure Hotplug not releasing drive reservations making drives to appear only on one node
- Firmware faults when shutting down one node
- Firmware faults when starting reconstruction
- Firmware asserts when the disk is owned by peer
- Misleading Fail/Offline Virtual Disk (VD) alert from MSM when reboot a node followed by logging into Windows
- Inconsistent reporting of pinned cache
- Global Hot Spare is marked as UNCONFIG_BAD when node reboots and gets failed over to peer
- Foreign configuration present on the owner node even after clearing the foreign configuration on the peer node
- Rebuilding did not resume where it left off on the peer when the (owner) failover happened
- Firmware faults when reboot with unsupport drive and SATA drive
- I/O's fail and VD becomes failed during planned failover of owner node w/ SMB I/O


============================
Previous Releases
============================
Package v23.6.0-0086 - Initial release (HADAS 1.0)
 Firmware 3.170.05-2458
 BIOS 5.41.00
 HII 03.02.03.00
 PCLI 05.06-03
 WebBIOS 6.1-63-e_63-Rel
 NVDATA 2.1210.03-0112
 BootBlock 2.05.00.00-0009
 Common Bootblock 07.26.13.219


*Third-party trademarks are the property of their respective owners.

