Microsoft iSCSI Software Initiator BOOT VERSION 2.07 Release Notes ******************************************************************************* Release notes for Microsoft iSCSI Software Initiator 2.07 BOOT VERSION Build version for files updated since version 2.02 Boot is 5.2.3790.3273. Binaries that have not been changed since version 2.02 Boot release are 5.2.3790.1941 Boot initiator Version history: version 2.02 5.2.3790.1941 version 2.03 5.2.3790.3099 version 2.04 5.2.3790.3273 version 2.05 5.2.3790.3392 version 2.06 5.2.3790.3497 version 2.07 5.2.3790.3640 ******************************************************************************* (note: version 2.02 was the first release enabling boot support using the Microsoft iSCSI software initator) This is a dual-mode package. If iSCSI 2.0 or higher is installed, it will update just the files that include fixes which are the following: msiscsi.sys version 5.2.3790.3640 msiscsdsm.sys version 5.2.3790.3640 iscsiprt.sys version 5.2.3790.3640 iscsidsc.dll version 5.2.3790.3640 relnotes.txt version 5.2.3790.3640 mpdev.sys version 1.21.3790.2191 (version 1.21 is the most curre nt version of the Microsoft MPIO binaries as of April 2008) mpio.sys version 1.21.3790.2191 (version 1.21 is the most curre nt version of the Microsoft MPIO binaries as of April 2008) mpdev.inf version 1.21.3790.2191 (version 1.21 is the most versi on of the Microsoft MPIO binaries as of as of April 2008) mpio.inf version 1.21.3790.2191 (version 1.21 is the most versi on of the Microsoft MPIO binaries as of as of April 2008) mpspfltr.sys version 1.21.3790.2191 (version 1.21 is the most versi on of the Microsoft MPIO binaries as of as of April 2008) Please note that the size and date of mpio binaries in the iSCSI initiator packa ge may not appear to be exactly the same as the size of the files released as 1.21. The build date of the 1.21 binaries maps to the build date of the iSCSI initiator package. However, the 1.21 binaries included are the same as binaries released as MS MPIO 1.21. MPIO note: The MPIO version contained in 2.07 is MPIO version 1.21 NOTE: Booting a Windows Server 2003 system using the Microsoft iSCSI Software Initiator will only work in conjunction with a 3rd party solution implementing the Microsoft iSCSI Boot Architecture including the iBFT table. You must have access to a 3rd party solution (hardware or PXE solution) to work in conjunction with the Microsoft iSCSI Software Initiator. http://www.microsoft.com/presspass/press/2006/apr06/04-04SNWPR.mspx contains a list of partners implementing iSCSI boot in their products, either released or in beta version. Please ensure that you have one of these iSCSI boot enabled products prior to installing the Microsoft iSCSI Software Initiator Boot Version. Currently, the Boot version of the Microsoft iSCSI Software initiator is maintained as a separate package from the mainstream Microsoft iSCSI Software Initiator release at at www.microsoft.com/downloads , however the boot version contains all of the same non-boot related fixes (session recovery, etc.) included in the mainstream iSCSI software initiator package. Currently, the Microsoft iSCSI Software Initiator boot version can be obtained from http://connect.microsoft.com/ Invitation Code: ms-8RR8-6K43 Before installing the Microsoft iSCSI Software Initiator with integrated boot support, refer to the relboot.doc accompanying the download files as well as installation notes/guide from the iSCSI vendor providing the pre-boot init implementation. * Please see the iSCSI Initiator User's Guide (uguide.doc) in this package for more information on installation and troubleshooting. * The checked and retail versions of the Microsoft iSCSI Software Initiator will only install on retail version builds of Windows. There is no package that installs on checked builds of Windows. * iSCSI Initiator 2.0x is installed directly to the appropriate locations under the %windir% directory. Documentation is installed under %windir%\iscsi. * Dynamic disks on an iSCSI session are not supported for Windows XP, Windows 2000, and Windows Server 2003. Please see the iSCSI users guide for more information. * Both initiator and target CHAP secrets should be greater than or equal to 12 bytes, and less than or equal to 16 bytes if IPsec is not being used. It should be greater than 1 byte and less than or equal to 16 bytes if IPsec is being used. * Note that the default iSCSI node name is generated from the Windows computer name. If the Windows computer name contains a character that would be invalid within an iSCSI node name, such as '_', then the Microsoft iSCSI Initiator service will convert the invalid character to '-'. * If you have automatic start services that relies upon an iSCSI volume or device, please see the user's guide for information on configuring those devices. * If user requests CHAP for logon authentication, initiator will set AuthMethod to CHAP in logon request. If the target returns None for AuthMethod, initiator will fail the login with status "Authentication Failure". An event will be logged in system event log to indicate that the initiator required CHAP but target did not offer CHAP. If the target returns an authentication method other than CHAP, when the initiator requests CHAP, initiator will fail the login with status "Authentication Failure". An event will be logged in system event log to indicate that the target offered an auth method that the initiator did not understand. * If the target returns CHECK CONDITION for a scsi request, but does not provide sense data, initiator will complete the request with status target error. Initiator does not treat the target behavior as a protocol error. * The Microsoft iSCSI control panel configuration utility includes a Session Detils window that can be accessed by clicking the Details button in the Active Sessions tab. Note that the Path information displayed for each device is only available on Windows 2003 server. * The iSCSI control panel configuration utility does not create an icon in the system tray. If the applet is in the background, you can switch to it by using the ALT-TAB key combination or by double clicking on the icon that launches it. ******************************************************************************* 2.07 Changes (Changes since Microsoft iSCSI Software Initiator 2.06 release) 1. Data written twice when spanning tapes on an iSCSI target virtual tape drive. 2. Bugcheck in iscsiprt on getting storage device ID property. 3. iscsiexe can leak memory on discovering targets. 4. initiator leaks handles when refreshing the list of persistent targets 5. MSISCDSM leaves stale Registrations under certain conditions 6. Persistent Reservation not propergated across paths MPIO 1.21 fixes (included in 2.07) 1. Fix system hang that could occur due to race condition between path recovery and new path arrival. 2. Fix install sample to use the correct MPIO hardware identifier on Windows Ser ver 2008 3. Fix memory leak in MPIO 4. Fix system hang that could occur during total path failure in a Cluster envir onment. 5. Fix MSDSM to update statistics for the correct path 6. Fix MSDSM logic for retrying Persistent Reservation commands ************************************************ For additional information, please see the Microsoft iSCSI Initiator users guide and the following industry specifications: * iSCSI spec - RFC3720 * String Profile for iSCSI Names (http://www.ietf.org/internet-drafts/draft-ietf-ips-iscsi-string-prep-04.txt) * Preparation of Internationalized Strings ("stringprep") (RFC 3454) * UTF-8, a transformation format of Unicode and ISO 10646 (RFC 2044) For additional information, please see the Microsoft iSCSI Initiator users guide, the iSCSI Boot documentation provided separately from the installation package, and the following industry specifications: * iSCSI spec - RFC3720 * String Profile for iSCSI Names (http://www.ietf.org/internet-drafts/draft-ietf-ips-iscsi-string-prep-04.txt) * Preparation of Internationalized Strings ("stringprep") (RFC 3454) * UTF-8, a transformation format of Unicode and ISO 10646 (RFC 2044)