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 (RS3DC080, RS3DC040, RS3WC080, RMS25PB080, RMS25PB040, RMT3PB080, RMS25CB080, RMS25CB040, RMT3CB080, RMS25CB080N, RMS25PB080N, RS25AB080, RS25SB008, RS25DB080, RS25NB008, RS2VB080, RS2VB040, RT3WB080, RS2WC040, RS2WC080, RS2SG244, RS2WG160, RMS2MH080, RMS2AF080, RMS2AF040, RS2MB044, RS2BL080, RS2BL080DE, RS2BL040, RS2PI008DE, RS2PI008, SRCSASJV, SRCSASRB, SRCSATAWB, SROMBSASFC, SROMBSASMP2, SROMBSASMR, SRCSASPH16I, SRCSASBB8I, SRCSASLS4I, SRCSAS18E*, SRCSAS144E*, SROMBSAS18E*), 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://support.intel.com. *These older controllers should work but have not been tested. =================== Package Information =================== Driver Version = 6.601.55.00-1vmw OS supported = VMWare ESXi* 5.* Supported Kernels : released build ESXi 5.* ========= Attention ========= N/A ================== Known Restrictions ================== This release supports the released ESXi* 5.x release build. Pre-release builds (beta) are not supported. ======================= Contents on the package ======================= The following files are included in this package: Name Description ir3_Vmware_ESXi5_drv_v6.601.55.00_readme.txt This file megaraid_sas.zip VMWare ESXi* 5.* Driver Offline bundle scsi-megaraid-sas-6.601.55.00-1vmw.500.0.0.472560.x86_64.vib VMWare ESXi* 5.* driver VIB file License_v2.pdf License Agreement ========================= Installation Instructions ========================= VMware uses a file package called a VIB (VMware Installation Bundle) as the mechanism for installing or upgrading software packages on an ESX server. The file may be installed directly on an ESX server from the command line, or through the VMware Update Manager (VUM). COMMAND LINE INSTALLATION New Installation ---------------- For new installs, you should perform the following steps: 1. Copy the VIB to the ESX server. Technically, you can place the file anywhere that is accessible to the ESX console shell, but for these instructions, we'll assume the location is in '/tmp'. Here's an example of using the Linux 'scp' utility to copy the file from a local system to an ESX server located at 10.10.10.10: scp scsi-megaraid-sas--1vmw.500.0.0.472560.x86_64.vib root@10.10.10.10:/tmp 2. Issue the following command (full path to the VIB must be specified): esxcli software vib install -v {VIBFILE} In the example above, this would be: esxcli software vib install -v /tmp/scsi-megaraid-sas--1vmw.500.0.0.472560.x86_64.vib --maintenance-mode Note: Depending on the certificate used to sign the VIB, you may need to change the host acceptance level. To do this, use the following command: esxcli software acceptance set --level= Also, depending on the type of VIB being installed, you may have to put ESX into maintenance mode. This can be done through the VI Client, or by adding the '--maintenance-mode' option to the above esxcli command. Upgrade Installation -------------------- The upgrade process is similar to a new install, except the command that should be issued is the following: esxcli software vib upgrade -v {VIBFILE} --maintenance-mode VUM INSTALLATION The VMware Update Manager (VUM) is a plugin for the Virtual Center Server (vCenter Server). You can use the VUM UI to install a VIB by importing the associated offline bundle package (a ZIP file that contains the VIB and metadata). You can then create an add-on baseline and remediate the host(s) with this baseline. Please see the vCenter Server documentation for more details on VUM. ================== Component Features ================== N/A ============ Known Issues ============ N/A ============= Fixes/Updates ============= version 6.601.55.00-1vmw SCGCQ00456161 - System timeout value need to be set for SysPD devices SCGCQ00457058 - MR 6.1 : Port all changes from MR 6.0 to MR 6.1 version 6.600.60.00.1vmw - Deadlock while attempting to lock hba_lock twice for legacy MR controllers - Fixed core dump problem by changing last argument of vmklnx_scsi_register_poll_handler() call. - Supporting extendte MSI-X vectors in ESXi 5 driver - Loaded request_desc->DevHandle so SystemPD FastPath will work - Add SCSI residual bytes support to the megaraid_sas VMware 5 driver - Functionality in driver is added to differentiate between iMR and MR at firmware initialization time. - feature to support uneven span is implemented - Add OEM support - mfi_capabilities.support_additional_msix settings from "megasas_ioc_init_fusion". - VMware Driver 6.504.51.00 fails WorkBench 2.1 CoreDump Test - Driver crash when msix_disable=1 is pass to the boot time parameter - IO Command timeout value for TAPE devices need to be set from OS instead of default RAIDcontext timeout value - Debugging info is printed on varlog message by default - Update the bulletin.xml file included with the Vmware 5.x driver IOVP release for certification submission - Incorrect comparison of return values from get_arm_from_strip() function - Load balancing: Make balance count to be in sync with firmware on FP enabled version 6.506.51.00 - Deadlock while attempting to lock hba_lock twice for legacy MR controllers - Missing ESXi 5.x driver installation instructions - VMware Driver 6.504.51.00 fails WorkBench 2.1 CoreDump Test *Third-party trademarks are the property of their respective owners.