
		         RAID Manager 6 readme file
			    /etc/raid/README

=============================================================================

1. ENVIRONMENT


		*****  IMPORTANT  *****


The environment has not been modified by the installation of this
package.  The full path name must be entered when running the 
applications.

The GUI launcher can be executed by entering:
/etc/raid/bin/rm6
from the command line while in the windowing environment.

The executables for this package reside in directory /etc/raid/bin.

Make sure that the sd.conf file located in /kernel/drv supports LUNs 0-7
for each array controller that is attached to the system.

Refer to the RAID Manager 6 documentation for details.


=============================================================================

2. SNMP

RAID Manager 6 can provide remote notification of disk array
subsystem events using SNMP traps.  There are two general activities required
for enabling this notification.  They are described in this section.

 - Compiling the RAID Manager 6 MIB into your network management
   station.
 - Editing the /etc/raid/rmparams file so that RAID Manager 6
   will know where
   to direct the SNMP trap messages when an array event has occurred.

Adding the RAID Manager 6 MIB

To add the MIB
	1) Copy the file /etc/raid/rm6traps.mib to the network management
	   station.

	2) Follow the steps required by your specific NMS to compile the MIB.

NOTE:  The MIB is written to the standard Version 1 SNMP syntax.  It was 
       designed specifically for RAID Manager 6 and is not
       applicable to other vendors' RAID products.

System setup of rmparams file

	1) Make sure the host system is connected to the network.

	2) In the file /etc/raid/rmparams, set the value of
	   SNMP_Target_IP_Address to the dotted notation IP address of the
	   NMS that the MIB has been compiled on.  On most systems, this IP
	   address can also be a dotted notation multicast address or
	   broadcast address.

	3) Change the community name from its default of "NONE".  This
           value can be edited in the rmparams file in the line containing
           SNMP_Community_Name.  The most commonly used community name is
           "public" Your network environment may require another name.

	4) Copy the edited rmparams file to /etc/default/rmparams.  It is 
	   important to have a backup copy of this critical file.

Disabling RAID Manager 6 from sending traps

There are two methods to disable RAID Manager 6 from issuing
traps:

	1) In the rmparams file, change the SNMP_Community_Name to "NONE".

	2) In the rmparams file, delete the line SNMP_Target_IP_Address.


=============================================================================

3. /etc/raid/rmparams

Due to the critical nature of this file, a copy of the rmparams file has
been installed in the /etc/raid directory. If, by some means, the rmparams
file should become corrupted or missing, the user should copy the
/etc/raid/rmparams.install file to /etc/raid/rmparams to resume normal
operation of the RAID Manager 6 utilities.

It is strongly advised that if changes are made to the /etc/raid/rmparams
file, a backup copy of the edited file be saved as /etc/raid/rmparams.install. 



=============================================================================

4. /etc/osa/lunlocks

RAID Manager 6 uses a file (/etc/osa/lunlocks) to hide LUNs
from the RAID Manager 6 utilities when certain functions are
being performed (e.g. creation, format, etc).  If the RAID 
Manager 6 utility holding the LUN lock should come to an abnormal termination
(ie: crash), the LUN would remain hidden from the other RAID 
Manager 6 utilities.  If the user should notice a hang or a missing LUN that
she/he knows is configured, the user should remove the lunlocks file
(rm /etc/osa/lunlocks), exit and then re-enter the RAID 
Manager 6 application that could not see the LUN.


=============================================================================

5. LUN deletion and Veritas

The deletion of LUN's under the configuration application requires obtaining
exclusive access to the LUN(s) being deleted.  If any program has any slice
of a LUN open, exclusive access cannot be aquired. Mounted devices must be
unmounted.  LUN's configured under Veritas must be removed from Veritas
control before they can be deleted.

This is also true of other RAID Manager 6 operations that require
exclusive access.  These include Reset Configuration, fixing multiple drive
failures with the Recovery Guru, formatting a LUN with Options->Manual
Recovery->Logical Units, and Firmware Upgrade->Offline in Maintenance/Tuning.

Removing a LUN from under Veritas control involves the following steps:

1) Remove a LUN from a disk group:
    vxdg [-g groupname] rmdisk <diskname>
	example:  vxdg -g rootdg -k rmdisk disk01

2) Remove the LUN from Volume Manager 6 control
    vxdisk rm <devname>
	example:  vxdisk rm c1t0d0s2

3) Take the physical LUN offline:
    vxdisk offline <devname>
	example:  vxdisk offline c1t0d0s2

Refer to the Veritas man pages for further information.

=============================================================================

6. More than 8 LUN Support

   See the Release Notes on using add16lun.sh.

=============================================================================
