Netware Drivers for MegaRAID Controllers
Version: 7.00i
OEM: LSI
Release date: 04/22/03

Component names and version #s:
==============================

Current release:
===============
MEGA4_xx.ddi
   Device Driver Initialization file required to install MEGA4_xx.ham driver

MEGA4_xx.ham version 7.00i
   HAM Driver for Netware 5.1 and 6.0

MEGAMGR.NLM version 5.12
   MegaRAID utility for Netware

MEGAMMIO.NLM version 1.02e
   Media manager interface module for Mega4_xx.ham driver

MEGAMON.NLM version 1.29
   Monitor program for Netware 


Previous release:
================
MEGA4_xx.ddi
   Device Driver Initialization file required to install MEGA4_xx.ham driver

MEGA4_xx.ham version 7.00g
   HAM Driver for Netware 5.1 and 6.0

MEGAMGR.NLM version 5.12
   MegaRAID utility for Netware

MEGAMMIO.NLM version 1.02e
   Media manager interface module for Mega4_xx.ham driver

MEGAMON.NLM version 1.29
   Monitor program for Netware 


NOTE:
-----
	You can get latest MegaRAID Firmware images and Drivers and Utilities from LSI Logic web Site 
	http://www.megaraid.lsilogic.com.


Important Notes:
===========
1. Use latest Novell Service packs for the Netware version you are using.
2. MegaRAID drivers: Mega4_xx.ham, 
   
   Mega4_xx.ham works with:
      a. NWPAUPGRADE package
      b. Netware v4.2
   Only Mega4_xx.ham works with:
      a. Netware v5
3. Use the MEGA4_xx.ham driver whenever possible. The other drivers are provided for older versions of Netware.
4. The driver will load and display all possible slots where it finds a supporting device. (Ex. If there are 2 
   438's in the system in slot 2 & 7), the driver will display slots 2 & 7 and prompt the user to choose a slot number.  
   If the driver is loaded a second time, it will only display the last unused slot.    
5. Virtual Sizing
   Prerequisites:  
     - CTRL-M Objects->Logical Drives->Virtual Sizing set to ENABLED.
   Features: 
     - /VS option can be specified on the command-line 
       for the driver, e.g. load mega4xx.ham /vs=288 to change the default size recognized by the driver. 
     - Default "Virtual Size" is 80GB, the minimum
     - Mask write and read from last cylinder - 64K for a 64K region only.
   Limitations:
     - NSS Partitions are not supported.
   Advantage:
     - Allows online capacity expansion limited by available drives in an array.

6. Dynamic Volume Expansion
   Prerequisites:  
     - CTRL-M Objects->Logical Drives->Virtual Sizing set to DISABLED.
   Features: 
     - Standard Media Manager functions supported
   Limitations:
     - Four (4) NetWare Partitions are possible, so only 4 OCE (Online Capacity Expansion) will 
       be possible per logical drive.
     - Requires MEGAMGR Utility to activate.
     - Cannot delete a partition created unless you restart the server or unload/reload driver instance.
   Advantage:
     - No preset Virtual Size or option needs to be provided for this feature
     - NSS Partitions supported


Changes:
======

Bug Fix:

1.  Mega4_xx.ham: Improved performance by enhancing the ISR (Interrupt Service Routine).
2.  Mega4_xx.ham: Driver had problem with error handling that happen on drive failure which causes the system to hang                           or abend.  This driver has been fixed to handle drive failure HACB requests abort properly. 
3.  Mega4_xx.ham: Monitor service locks up NW6 server on some systems.
4.  Mega4_xx.ham: NW 5.1 installation fails some systems.
		  This has been fixed. 
5.  Mega4_xx.ham: Memory corruption on device scanning will cause the system hang and/or crash.
                  This has been fixed.
6.  Mega4_xx.ham: Logical drive information was displayed incorrectly on screen.
                  This has been fixed.
7.  Megamgr.nlm:  If background init was going on one logical drive; then if the user tried 
		  to start check consistency/Init on some other logical drive, it was failing.
8.  Megamgr.nlm:  Disallow the spanning of R0 configuration.
9.  Megamgr.nlm:  Disallow the spanning of partial arrays.
10. Megamgr.nlm:  Modified the code to improve predictive failure detection.
11. Megamgr.nlm:  Cosmetic change:
        
		  The utility gives the option to the user to view ongoing Init/BI-CC by pressing 
		  F6/F7 keys respectively. If no BI-CC is going on any logical drive, 
 		  then earlier the utility was giving the message

        	  "No Logical Drive Is Currently In Check Consistency State" now the message is changed to "No 		   Logical Drive is Currently In Check Consistency or Background Init State".


Enhancement:
-----------

1. Mega4_xx.ham: Added PCI PnP ID for MegaRAID SATA 150-4D controller support.
2. Mega4_xx.ham: Added feature to support IO mapped I/O controller, like 428 controller.
3. Mega4_xx.ham: Changed the version numbering scheme to Novell standard industrial version method. All future                  releases will include only numeric values (no alphabets).
3. Mega4_xx.ham: Support added for 523 controllers.
4. Mega4_xx.ham: Queue freezes mechanism modified according to the NWPA specification.
5. Mega4_xx.ddi: VID and SS VID has been changed from 101E to 1000.
6. Megamgr.nlm:  Allow the user to view ongoing REBUILD on all physical drive(s).
     		 
		 Earlier, user had to select the physical drive in the menu and then
     		 select the view rebuild option to see ongoing rebuild (if any) on that
    		 physical drive.

    		 Now the utility gives the option to the user to view ongoing REBUILD of
    		 ALL physical drive(s) on which REBUILD is progress.

Restrictions:
=============

1. Usage of megamgr or megamon on systems with more than 2GB of memory, is possible ONLY AFTER
   the support pack 2, (Nw51sp2) for Netware 5.1 is applied, and the Server is restarted.

2. After the Random Logical driver deletion, the user needs to scan the bus through:
	-- For Netware 5.1 "list devices" on the system console.
	-- For Netware 6.0 "list devices" on the system console or scan for devices from the Novell console            one (GUI).

   Failed to scan the bus cause some delay between the megamgr invokes.

4. There is a defect that NetWare 5.1 has When using any kind of test suite that includes file system module    of kernel for I/O, if I/O requests are accumulated on buffer cache, system may go to CPU hog detected by    timer abend if drive failure in the middle of I/O test. Please exclude file system module for heavy I/O    test on driver. To achieve this, use dpmeterm module and pick up raw I/O option that exclude file    system out of I/O request packet path.


File Listing
------------
File Name           	   Size    	  Date      	 Time
MEGA4_XX DDI        	  15,450  	03-03-03  	 2:55p 
MEGA4_XX HAM	    	  59,021  	04-04-03  	 3:19p 
MEGAMGR  NLM        	 310,858  	02-06-03 	 9:25a 
MEGAMMIO NLM        	  27,463  	12-13-02  	 4:08p 
MEGAMON  NLM         	 426,244  	12-11-02  	12:45p 
NW700i   TXT         	   7,122  	05-08-03 	 6:42p 	   

