

		MEGAMONITOR For Linux (MIMD) - Ver 2.8
		**************************************
			
	           	15th Feb 2002


RELEASED COMPONENTS
*******************
1. Executables: 		- MegaCt32, MegaServ
2. Installation Scripts: 	- raidmon, install
3. Shell Script: 		- deb_rmon: Debian linux specific raidmon  

					
*********************************************************
   	
	FILE DETAILS: (As seen on Linux machine)
	
	-rwxr-xr-x    1 root     root          354392 	Feb  15 07:29 	MegaCt32
	-rwxr-xr-x    1 root     root          452520 	Feb  15 07:29 	MegaServ
	-rwxr-xr-x    1 root     root       	  825 	Feb  15 07:29 	deb_rmon
	-rwxr-xr-x    1 root     root  		 3638 	Feb  15 07:29 	install
	-rwxr-xr-x    1 root     root         	 1229 	Feb  15 07:29 	raidmon


Release Version 2.8 - 15th FEB 2002
***********************************

1. FEATURES:

	1. The MegaServ is compliant to MegaRAID MIMD driver of Linux.

	2. Supports up to 12-adapters in total (8-logical drive + 40-logical
  	   drive cards all inclusive).

	3. Allows running of check consistency on scheduled hour thru specification of "consistency 
           schedule" thru option of "MegaCtrl"

	4. Reports change in state of "logical drive"
		a. In case of "number of logical drive" change detected, it skips the comparison of logical 
		   drive state change during that cycle of polling.

	5. Reports change in state of "Physical drive"
		a. In case of drive detected in "FAILED" state, it reports "reason of such failure", 
		   if information is available from firmware.

	6. Polls SMART failure related events.
		a. Uses new method of extended-sense-information, if available on 40-ld firmware side. 
		   Else uses old commands to get SCSI-DUMP data.

	7. Reports "Media Error + Other Error" counters of a physical drive if any nonzero value found or 
	   the error counter value changes.
		a. These error counters are reset on start of service and also on reaching a threshold value 
		   of "20"(Total of MediaError+OtherErrors).

	8. Logs different events in file "/var/log/megaserv.log" with date & time stamp.

	9. Sends mail to root for different events with date & time stamp.
 

   
2. CHANGES:
	
	1. MegaServ now gives distinctive message for "Consistency checking" and "Background 
	   initialization" ,if firmware supports the command 0xA4/0x13.

	2. "-LogProgXXX" option is supported in ./MegaCt32 to allow user specify consistency 
	   checking progress(%-age) reporting interval for ./MegaServ.
	   XXX=0 .. any +ve integer , implying number of seconds.
	   The default setting for log progress reporting interval is every 15-minutes.

	3. MegaServ program now reports completion of consistency checking process on the 
	   logical drives on fulfillment of any of the following conditions that means 
	   change in consistency state such as
	
	a) Consistency checking progress reached 100%
	b) Consistency checking is aborted (either by this program or by some other program). 
	
	This case cannot be handled differently as the utility does not have any information 	
	otherwise and it tells user that running activity of consistency checking is OVER. 
	It should be considered to be the meaning of COMPLETION.

	4. Allow user to disable the mailing feature if system mailing is not installed in some Linux (such 
	as Debian Linux) to avoid any screen corruption.

	5. Default progress time is changed from 15 minutes to 900 seconds (as per NT monitor).	



3. BUGS FIXED:
 

HOW TO INSTALL
**************
	1. Install the new component as follows
		a. Copy all the files in a temporary directory
		b. Rename file megaserv as MegaServ   and "megact32" as "MegaCt32"
		c. Run "install" script as  "./install"
		d. It will copy the needed files to the respective directory.

	2. Now you can run the MegaServ program thru MegaCtrl -start

	3. For other help, type "MegaCtrl -help"



Known Limitations
*****************
	1. MegaRAID Linux driver must be installed for successful running of this utility.

	2. Service program polls different components one by one and then sleeps for about 10-seconds (or 
	   more). If any event occurs more than once during this 10-seconds period, then it will be able to 
	   report only the last change during its actual polling of data.

	3. At scheduled hour, it runs check consistency on all redundant optimal logical drives on all 
	   adapters. If by any chance the boot drive is one of such drive, then during the running of check
 	   consistency, the machine might be quite slow in response, depending on i/o activities.





