*********************************************************************** * * * IBM ServeRAID and IBM ServeRAID II Configuration Diskette * * Version 2.70 * * * *********************************************************************** IBM* ServeRAID Adapter Installation Instructions Diskette 1 - ServeRAID Configuration Diskette Diskette 2 - ServeRAID Device Drivers and Utilities Diskette Administration and Monitoring for IBM OS/2*, Administration and Monitoring for Novell NetWare** 3.12 and 4.1X Administration and Monitoring Server Services for OS/2, NT, NetWare, and OpenServer Diskette 3 - ServeRAID Administration and Monitoring Utility Diskette for Microsoft NT/Win95** Diskette 4 - ServeRAID SCO** OpenServer** Boot-Time Loadable Diskette (BTLD) NOTE: The latest version of these diskettes can be found at http://www.pc.ibm.com/servers on the World Wide Web. CONTENTS ======== 1.0 Operating System Installation and RAID Administration 1.1 Installation steps for OS/2 1.2 Installation steps for Windows NT 3.51 and 4.0 1.3 Installation steps for Windows NT 4.0 from CD-ROM using CD-ROM boot support. 1.4 Installation steps for NetWare 4.1X 1.5 Installation steps for NetWare 3.12 1.5.1 Administration and Monitoring in NetWare 1.6 Installation steps for SCO OpenServer 5.0.X 1.7 Installing DOS Driver for CD-ROM access: 2.0 IBM ServeRAID Adapter Administration and Monitoring Utilities 2.1 Introduction 2.2 Stand-alone Version Requirements 2.3 Client/Server Version Requirements 2.4 Client/Server Installation Instructions 2.5 Using the Server Application 2.6 Using the Administration and Monitoring Utility 3.0 Logical Drive Migration operating system specific instructions: 3.1 Introduction 3.2 Change RAID Levels 3.3 Increase Free Space 3.4 Increase Logical Drive Size 4.0 Trademarks and Notices: 1.0 Operating System Installation and RAID Administration 1.1 Installation steps for OS/2 NOTE: If any logical drives have been set to write-back (WB) mode, they must be changed to write-through (WT) mode during the OS/2 installation. After the installation is completed, the logical drives can be changed to write-back (WB) mode. 1. Follow the instructions in the OS/2 Installation manual to install OS/2. To load the ServeRAID device driver during installation, copy the file IPSRAID.ADD from the OS2 subdirectory of the "ServeRAID Device Drivers and Utilities diskette" to OS/2 Diskette 1 and add the following line to the CONFIG.SYS file found on OS/2 Diskette 1. BASEDEV=IPSRAID.ADD If diskette 1 does not have enough space to copy the IPSRAID.ADD driver, delete device drivers that are not being used to make space. (Make sure to create a backup copy of diskette 1 before deleting any files.) When deleting a driver, make sure to remove the corresponding basedev statements from the CONFIG.SYS file. 2. Once OS/2 is installed, put the "ServeRAID Device Driver and Utilities Diskette" in the diskette drive. 3. Type: DDINSTAL from any OS/2 command prompt. 4. Select "IBM ServeRAID Adapter ADD installation" from the menu. DDINSTALL will insert "BASEDEV=IPSRAID.ADD" into the CONFIG.SYS file and will copy following files to OS2 subdirectory: IPSRAID.ADD - device driver IPSRADM.EXE - RAID Administration and Monitoring The following file will be copied the \OS2\HELP directory: IPSRADM.HLP - Help file for RAIDADM.EXE 5. Edit the CONFIG.SYS file and verify that only one "BASEDEV=IPSRAID.ADD" statement appears in this file. Also check the path where the IPSRAID.ADD driver is being loaded and verify the correct driver is installed. NOTE: If you have more than one RAID or SCSI adapter in your system make sure that the BASEDEV statement of the adapter that has the boot device appear before the BASEDEV statements of other RAID or SCSI adapters in the CONFIG.SYS. Also, after any service pack is installed, check the path where the IPSRAID.ADD driver is being loaded and verify the correct driver is installed. 6. After restarting your system, IBM ServeRAID administration can be started by entering: Type: IPSRADM [/lf=d:\path\logfile] at the OS/2 subdirectory. where d: is the drive where you wish to create the logfile. logfile is the filename where IPSRADM message will be logged. NOTE: If /lf is omitted, a default logfile IPSRADM.LOG is created in the OS2 subdirectory. When /lf switch is used, make sure that the d: drive and path \path exists. IPSRADM will not create a subdirectory if one does not exist. You can define IPSRADM to OS/2 by dragging a Program icon from the Templates Folder to the Desktop. In the Program - Settings notebook, on the Program page, enter the following: o Path and file name: C:\OS2\IPSRADM.EXE o Parameters: /lf=d:\path\logfile In the General page, enter ServeRAID as the title and remove the tick mark from Template. 1.2 Installation Steps for Windows NT 3.51 and 4.0 1. Prepare the hard disk drives of your server according to the instructions in the Windows NT manual. 2. Select either "Express" or "Custom Setup" on the "Windows NT Setup" screen. 3. The installation program scans the system for SCSI adapters installed in the system. Once this scan is complete, select "S" to "Configure Additional SCSI Adapters". 4. Select Other from the list of SCSI adapters. 5. When prompted to insert "Manufacturer-supplied support disk" insert the "ServeRAID Device Driver and Utilities Diskette" into the diskette drive. 6. Select "IBM ServeRAID Adapter" and press Enter. 7. Continue with the normal installation process according to the instructions in the Windows NT manual. 8. After completing the install of NT, apply the latest Service Pack. 9. The administration and monitoring function can be installed by inserting the "ServeRAID Administration and Monitoring Utility Diskette" and running setup. 1.3 Installation Steps for Windows NT 4.0 from CD-ROM using CD-ROM Boot Support. 1. Power on the server 2. Press Ctrl+I when the ServeRAID BIOS message appears. 3. Select Advanced Function from the Mini-Configurator Menu. 4. Select Boot-CDROM and Int13 Extensions. 5. Select BIOS Support for Bootable CD_ROM if it is not set to Yes. 6. Exit from Mini-Configurator and restart the system 7. Insert the NT 4.0 CD-ROM in the CD-ROM drive. 8. Press F6 at the NT setup message Setup is inspecting your computer's hardware configurations... 9. The installation program scans the system for SCSI adapters installed in the system. Once this scan is complete, select "S" to "Configure Additional SCSI Adapters". 10. Select Others from the list of SCSI adapters. 11. When prompted to insert "Manufacturer-supplied support disk" insert the "ServeRAID Device Driver and Utilities Diskette" into the diskette drive. 12. Select "IBM ServeRAID Adapter" and press Enter. 13. Continue with the normal installation process. 1.4 Installation Step for NetWare 4.1X Follow the instructions in the NetWare 4.1X manual. Make sure to use the latest NWPA modules and IPSRAID.HAM driver during the installation. The latest NWPA and IPSRAID.HAM driver available at the time of this diskette release is supplied in the NetWare directory on the ServeRAID Device Driver and Utilities Diskette. NOTE: Non-disk devices (e.g., CD-ROM, Tape) connected to a ServeRAID adapter must have unique SCSI-IDs even if they are connected to different SCSI channels. For example if you have a CD-ROM with SCSI-ID 6 connected to channel 1 and a tape drive connected to channel 2, the tape drive cannot have the same SCSI-ID 6. NetWare 4.1X Install: ===================== 1. As a part of the install process, NetWare will load and display the NetWare Server Installation screen and will prompt you Choose the Server Drivers - Disk Driver 2. To install drivers from the "ServeRAID Device Driver and Utilities Diskette", press the Ins (Insert) key. A message will appear that INSTALL.NLM will search the root directory of path A:. Press the Enter key to continue. 3. You will be provided with a list of available drivers found on the Diskette. Select the driver IPSRAID.HAM. 4. Follow NetWare instructions to complete the install. Install ServeRAID HAM to an existing NetWare 4.1X: ================================================== 1. At the server console prompt, type LOAD INSTALL This will load INSTALL.NLM and display the NetWare Server Installation screen with Installation Options shown. 2. At the Installation Options screen choose "Driver options". 3. At the Driver Options screen, choose "Configure disk and storage device drivers". 4. At the Selected Disk Drivers screen, under Additional Driver Actions, choose "Select an additional driver". 5. To install drivers from the "ServeRAID Device Driver and Utilities Diskette", press the Ins (Insert) key. A message will appear that INSTALL.NLM will search the root directory of path A:. Press the Enter key to continue. 6. You will be provided with a list of available drivers found on the Diskette. Select the driver IPSRAID.HAM. 1.5 Installation Steps for NetWare 3.12 Follow the instructions in the NetWare 3.12 manual. The IBM ServeRAID driver IPSRAID.HAM is supplied in the NetWare directory. You can use the INSTALL.BAT supplied in the NetWare directory to copy all necessary files to your server directory. INSTALL.BAT will also make changes in the STARTUP.NCF file to load necessary NetWare modules. You can install NetWare 3.12 one of two ways: METHOD 1 1. Type following at the command prompt to manually create the directory where you wish to install NetWare. MD SERVER.312 where SERVER.312 is directory (default for NetWare 3.12) where server software will be installed. If you use a different path make sure that you specify the same path during installation of NetWare software. 2. Change directory to the new server directory created in step 1. Using example of step 1 type CD SERVER.312 3. Insert the "ServeRAID Device Driver and Utilities Diskette". At the DOS command prompt type A:\NETWARE\INSTALL 4. Follow the NetWare 3.12 instructions until the first NetWare prompt. Type DOWN EXIT to down and exit the server. 5. If you are not in the server directory created in Step 1, change to the server directory. Start server by typing SERVER at the command prompt. Type LOAD INSTALL at the NetWare prompt and continue to install NetWare according to the NetWare instructions. METHOD 2 1. Follow the NetWare 3.12 instructions until the first NetWare prompt. Type DOWN EXIT to down and exit the server. 2. Change directory to the server directory by typing CD SERVER.312 If your server path name is different than SERVER.312 type CD path_name. Where path_name is your server directory. 3. Insert the "ServeRAID Device Driver and Utilities Diskette". At the DOS command prompt type A:\NETWARE\INSTALL 4. Start server by typing SERVER at the command prompt. Type LOAD INSTALL at the NetWare prompt and continue to install NetWare according to the NetWare instructions. NOTE: Use INSTALL.BAT for NetWare 3.12 only. The following NetWare patches must be loaded before loading IPSRAID.HAM. If you do not have them loaded by the STARTUP.NCF (STARTUP.NCF is updated by the INSTALL.BAT described in step 3 above). you can load them manually as follows: LOAD NPAPATCH.NLM LOAD NWPALOAD.NLM LOAD IPSRAID.HAM The necessary patches and other support files are included in the NetWare directory in the diskette. The NetWare directory also contains NWASPI.CDM, Novell's generic ASPI support CDM. This CDM intercepts ASPI calls and allows them to work under the NWPA architecture. If Novell's ASPI support is required, this file should be loaded by typing LOAD NWASPI.CDM 1.5.1 Administration and Monitoring in NetWare To load the NetWare Administration program type: LOAD IPSRADM.NLM at the server console. IPSRADM.NLM is supplied in the NetWare directory in the diskette. To load the Netware Administration program with Netware SFT III installed, load IPSRADM.NLM in the mirrored server engine. The ServeRAID adapters in the primary and backup server will be visible to the Netware Administration program as if they were in one server. NOTE: When a rebuild, synchronization, or logical drive migration is in process, IPSRADM.NLM cannot be terminated by pressing the ESC key. To terminate during one of these operations, unload IPSRADM.NLM. 1.6 Installation Steps for SCO OpenServer 5.0.X 1. Logical drives must be installed as bus number 0 when using the 'mkdev' utility, regardless of channels the physical drives are on. 2. Non-disk devices (such as, CD-ROM's and Tape Drives) must be installed as bus numbers 1, 2, or 3, depending upon the channel the physical device is on. The external channel 1 connector and the internal channel 1 connector (located closest to the external connector) is bus number 1. The next internal channel connector is bus number 2, and the last internal channel connector is bus number 3. You cannot use the internal channel 1 connector and the external channel 1 connector at the same time. 3. To configure the default non-disk devices during the initial install: a. The default tape drive must be redefined in the initial bootstring, For example, to install the ipsraid BTLD and redefine the tape drive, enter: link Stp=ips(0, 1, 2, 0) at the "Boot:" prompt. The numbers are: the host adapter number, the bus number, the SCSI ID, and the lun respectively. b. When prompted for the location of the installation CD, change the bus number and SCSI ID as appropriate. Adding BTLD at boot time. NOTE: Refer to 'Using Boot-Time Loadable Drivers' in the SCO OpenServer Handbook. 1. At the "Boot:" prompt type "link" and press 2. When asked for the name of the package to load, type "ipsraid" 3. After kernel loads but before it runs, "link" prompts you to insert the "IBM ServeRAID SCO OpenServer Diskette". NOTE: While installation is copying files from the CD, the following two messages (a and b) may appear. Message a) requires no user action. Message b) when prompted, press to continue installation. a) Extracting BTLD distribution for ipsraid... /etc/uadmin getdev b ips: No such device (error 19) b) dynamic linker: dlvr_audit: Cannot open /dev/zero for file /lib/libprot.so.1 4. Retain the BTLD diskette for use later in the installation. You will need it to configure the driver into the link kit. Adding BTLD after initial installation. 1. Start the server in system maintenance mode, and login as root 2. Type "installpkg" 3. If prompted, select the diskette drive from which to install 4. Insert the "ServeRAID SCO OpenServer Diskette" when prompted. 5. When asked for the name of the package, type "ipsraid" 6. Re-link the kernel (as described in "Relinking the kernel" in the SCO OpenServer Handbook) by entering the following commands: cd /etc/conf/cf.d ./link_unix Once the kernel has been rebuilt you will see the following message: "The UNIX kernel has been rebuilt. Do you want this kernel be boot by default?" enter "y". The system backs up the old kernel by moving /unix to /unix.old. When the system asks for kernel environment to be rebuilt, enter "y". The system will respond with a successful message. 7. Use "shutdown" to bring down the system and then reboot it. Installing SCO OpenServer Using an IDE CD-ROM device. SCO OpenServer Version 5.00: Type the following at the BOOT prompt: restart ahslink="ATAPI ipsraid" Srom=wd(0,0,0,0) Insert the ATAPI BTLD diskette when prompted. Press "r" to replace the wd driver. The fields for the ATAPI CDROM are: Srom=wd(c,d,l,b) where c = primary (0) or secondary (1) IDE/EIDE controller d = master (0) or slave (1) device l = LUN of device (always 0 with ATAPI or wd driver) b = BUS of device (always 0 with ATAPI or wd driver) SCO OpenServer Version 5.02 and 5.04 Type the following at the BOOT prompt: restart link=ipsraid Srom=wd(0,0,0,0) Note: The ATAPI BTLD (which includes the "wd" driver) is included on OpenServer 5.0.2 and 5.0.4. The fields for the ATAPI CDROM are: Srom=wd(c,d,l,b) where c = primary (0) or secondary (1) IDE/EIDE controller d = master (0) or slave (1) device l = LUN of device (always 0 with ATAPI or wd driver) b = BUS of device (always 0 with ATAPI or wd driver) Let the system Boot normally until it comes to the select Media options. For OpenServer 5.0.2: Select Adapter type as WD Select Media Type as SCSI CDROM Select ID, BUS & LUN as 0 For OpenServer 5.0.4: Select Media Type as IDE CDROM Drive Select Primary Adpater and Master Device 1.7 Installing DOS Driver For CD-ROM Access: 1. If DOS is not already installed, first install DOS in the boot drive connected to the ServeRAID Adapter. 2. Insert the "ServeRAID Configuration Diskette" into the diskette drive and type: CD DOS Then, press Enter. 3. Type UINSTALL and follow the instructions to complete the installation of necessary drivers and support programs for CD-ROM support. 2.0 IBM ServeRAID Adapter Administration and Monitoring Utilities 2.1 Introduction The Administration and Monitoring Utilities assists in the configuration, administration, and monitoring of an adapter. There are versions for stand-alone administration (administering a system containing the adapter from that system) as well as a version for client/server administration (administering a system containing an adapter from another system on a network). 2.2 Stand-alone Version Requirements The stand-alone implementation consists of operating system specific programs that are installed on the system containing the ServeRAID adapter. The currently supported platforms are: - IBM OS/2* - Microsoft Window NT Server/Workstation** 3.51/4.0 - Novell NetWare** 3.12/4.1X 2.3 Client/Server Version Requirements The client/server implementation requires a Microsoft Windows 32-bit workstation as the client with TCP/IP installed on both the client and server. This client runs on the following platforms: - Windows NT Server - Windows NT Workstation - Windows 95 The server application is currently supported on IBM OS/2, Microsoft NT Server/Workstation 3.51/4.0, Novell NetWare 3.12/4.1X, and SCO OpenServer 5.0.X platforms. The server applications are located on the "ServeRAID Device Drivers and Utilities Diskette" in the following directories: IBM OS/2 Server \remote\server\os2\ipsadm.exe Microsoft Window NT Server \remote\server\nt\ipsadmn.exe Novell NetWare Server \remote\server\netware\ipsadm.nlm SCO OpenServer (located on the ServeRAID SCO OpenServer Diskette) The client is located on the "ServeRAID Administration and Monitoring Utility Diskette". 2.4 Client/Server Installation Instructions To install the client: 1) From a command prompt run A:\SETUP To install the IBM OS/2 Server Utility: 1) Create an 'IPSRAID' directory on the hard disk: type: MD C:\IPSRAID 2) To copy the server program: COPY A:\REMOTE\SERVERS\OS2\IPSADM.EXE to C:\IPSRAID\IPSADM.EXE 3) To copy the icon: COPY A:\REMOTE\SERVERS\OS2\IPSADM.ICO to C:\IPSRAID\IPSADM.ICO 4) Create an icon for the application: a) Open the Templates Folder b) Drag a 'Program Template' onto the Desktop c) At the Program Tab, enter: Path and file name: C:\IPSRAID\IPSADM.EXE d) At the General Tab, enter: Title: IPSRAID Admin/Monitor Find Current Icon: IPSADM.ICO e) Double-Click the new icon to access the administrator To install the Microsoft Windows NT Server/Workstation Server Utility 1) Create an 'IPSRAID' directory on the hard disk: type: MD C:\IPSRAID 2) To copy the server program: COPY A:\REMOTE\SERVERS\NT\IPSADM.EXE to C:\IPSRAID\IPSADM.EXE 3) To copy the icon file COPY A:\REMOTE\SERVERS\NT\IPSADM.ICO to C:\IPSRAID\IPSADM.ICO 4) NT 3.51 - Choose a group or create a new group to put the utility: Open the Administrative Tools Group or Create a New Program Group named 'IPSADM Admin/Monitor' 5) NT 3.51 - Open the File menu and choose New... 6) NT 3.51 - Click 'OK' making sure 'Personal Item' is selected 7) NT 3.51 - Enter the following: Description: IPSRAID Admin/Monitor Server Command Line: C:\IPSRAID\IPSADM.EXE Working Dir: C:\IPSRAID 8) NT 4.0 - Create a new shortcut for the utility: Right-click on the Desktop and Select 'New', 'Shortcut' or In Explorer, highlight the IPSRAID directory and select the 'File' menu, then 'New', 'Shortcut' 9) NT 4.0 - In the 'Create Shortcut' window: type: C:\IPSRAID\IPSADM.EXE or Click the 'Browse' button and Open the ipsadm.exe file 10) NT 4.0 - Click 'Next' 11) NT 4.0 - In the 'Select a Title for the Program' window: type: IPSRAID Admin/Monitor Server 12) NT 4.0 - Click 'Finish' 13) NT 4.0 - Open the properties for the shortcut: Right-click on the icon and select 'Properties' 14) NT 4.0 - Click on the 'Shortcut' notetab 15) Click on 'Change Icon' 16) Click 'OK' in the information window 17) In the 'Change Icon' window: type: C:\IPSADM\IPSADM.ICO or Click browse and select C:\IPSADM\IPSADM.ICO 18) Click 'OK' for the icon 19) Click 'OK' for the program properties 20) Double-Click the new icon to access the administrator To install the Novell NetWare 3.12/4.1X Server Utility 1) Copy the file 'A:\REMOTE\SERVERS\NETWARE\IPSADM.NLM' onto the NetWare Server using one of the following methods: - From the DOS prompt, use the copy command to put the NLM on the server, type: COPY A:\REMOTE\SERVERS\NETWARE\IPSADM.NLM to C:\NWSERVER\IPSADM.NLM - From a client on the network, copy the NLM into one of the NetWare directories, type: COPY A:\REMOTE\SERVERS\NETWARE\IPSADM.NLM \\SERVER\SYSTEM\IPSADM.NLM 2) From the system console, load the NLM, type: LOAD C:\NWSERVER\IPSADM.NLM or LOAD \SYSTEM\IPSADM.NLM To load the Server Utility with Netware SFT III installed, load IPSADM.NLM in the mirrored server engine. The ServeRAID adapters will be visible to the IPSRAID Administrator/Monitor as if they were on one server. Ensure TCP/IP is properly installed under SFT III. Consult the Netware installation manual for additional information on installing TCP/IP. To install the SCO OpenServer 5.0.X Server Utility NOTE: The SCO server utility is installed from the BTLD disk during installation of the ServeRAID BTLD driver. The file is installed into the '/usr/bin' directory. To install ipsadm manually follow the directions below: 1) Insert the ServeRAID SCO OpenServer Diskette into the SCO OpenServer system 2) Create a directory for the server daemon mkdir /ipsraid 3) Mount the diskette mount /dev/fd0 /mnt 4) Copy the file '/mnt/ipsraid/new/usr/bin/ipsadm' onto the system cp /mnt/ipsraid/new/usr/bin/ipsadm /ipsraid/ipsadm 5) Unmount the diskette umount /mnt 6) Start the server daemon to run in the background ./ipsadm & 2.5 Using the Server Application The server programs for all platforms are very similar in functionality. The server programs accept the following optional command-line parameters: -p: specifies the port number on which the server will listen for client connections -f: specifies the filename in which to log messages -f specifies to log messages to the default filename, ipsadm.log -d disables logging of messages to the display -s: specifies the filename containing security information -? displays the help for the valid parameters The port number is a parameter used in TCP/IP to distinguish between different services on a single machine. The default for IPSADM is port number 1087. This number can be changed on the command-line if another service on the system occupies 1087. Messages can be logged to the screen and/or to a text file on the system. The default is to log messages to the standard output (usually the display), but can be disabled by using the '-d' parameter. The '-f' parameter enables logging messages to a file. Messages consist of startup information, connecting and disconnecting clients, and error messages. Security is maintained in an optional text file on the server system. The file stores unencrypted usernames and unencrypted passwords and should be kept in a secure directory. When username and passwords are entered on the client side, they are encrypted for delivery to the server. The server decrypts the username and password to verify proper access to the ServeRAID Adapter. If successful, the adapter will receive and execute commands from the client. If no security file is present in the default directory, or the directory specified by the '-s' parameter, security will be disabled and the server utility will accept commands from any client connection. The security file is formatted with one username:password combination Per line with the strings separated by a colon (:) and each string being a maximum of eight characters. IPSADM relies on name resolution to determine the hostname from the client that is trying to connect. When a client is trying to access a remote server, the server tries to look up the name of the client connecting. The method used to look up the name is determined by the configuration of the server. Some possible methods for this are Domain Name Servers and/or 'HOSTS' files. With certain configurations, some timing delays may occur due to mis-configuration or inability to access the DNS. If problems persist, check your network configuration. 2.6 Using the Administration and Monitoring Utility Double-click on the 'IPSRAID Administrator/Monitor' icon on the Windows client to access the adapter(s). The main window will initialize the interface. If you are running standalone with an adapter installed in your system, you will see the current settings of the adapter(s) installed in your system. If you are running client/server, the application will report that there are no adapters installed in your system. To access a server containing an adapter, simply select 'Network Settings' from the 'Options' menu. A window appears prompting for 'Stand-alone' or a 'Client/Server', select the 'Client/Server' radio button. Fill in the hostname of the server in the edit box and click 'OK'. If security is enabled on the server, you will have to enter a valid UserName and Password. 3.0 Logical Drive Migration Operating System Specific Instructions: 3.1 Introduction Logical Drive Migration (LDM) dynamically changes the properties of logical drives. LDM can be used to change the RAID level, increase the free space in an array or change the size of a logical drive. All logical drives within a chosen array will be migrated. All of the logical drives in the array must be in the OKY state for an LDM to start. LDM supports concurrent I/O during operation. Following is a table summarizing the support of logical drive migration within each operating system: Change RAID Level Increase Free Space Increase Drive Size OS/2 Yes Yes Yes Windows NT Yes Yes Yes Netware Yes Yes No OpenServer Yes Yes No NOTE: You must use the ServeRAID Administration and Monitoring Utility for Windows NT/Windows 95 to execute Logical Drive Migration. 3.2 Change RAID Levels The 'Change RAID Level' feature migrates all logical drives in an array of one RAID level to a different RAID level by either adding or removing a drive. All logical drives within the array must be the same RAID level. The supported configurations are as follows: * migrate a two or more drive array with RAID level 0 logical drives to RAID level 5 by adding one drive * migrate a two drive array with RAID level 1 logical drives to RAID level 5 by adding one drive * migrate a three or more drive array with RAID level 5 logical drives to RAID level 0 by removing one drive For example, if you have a two drive array with three RAID level 1 logical drives, you can migrate this to three RAID level 5 logical drives by adding one hard disk drive. The 'Change RAID Level' function is independent of the operating system and does not require any action after the logical drive migration completes. 3.3 Increase Free Space 'Increase Free Space' expands the amount of free space within an array without adjusting the size of the logical drive(s). This is useful when you need to add more logical drives to your array. This function works for all operating systems, but may require a reboot for the operating system to recognize the new logical drive. After increasing the free space in your array with LDM, use the Administration and Monitoring Utility to create a new logical drive. Remember to initialize and synchronize your new logical drive if necessary. To use the new logical drive in the operating system environment, do the following: For IBM OS/2: * Reboot the system * Run 'fdiskpm' * Select the new drive and create a partition * Save the changes * Reboot the system * Format the new partition For Microsoft Windows NT: * Run the NT Disk Administrator * Write the signature to the new logical drive * Create a partition in the new free space * Commit and save the changes * Format the new drive For Novell NetWare: * Type 'LOAD INSTALL' from the system console * Select 'Disk Options' from the main menu * Select 'Scan for Additional Devices' * Select 'Modify disk partitions and Hot Fix' and create your new partition * Escape back to the main menu * Select 'Volume Options' * You can create a new volume or add the new partition to an existing volume * Mount the new volume For SCO OpenServer: * Type 'mkdev hd' * Input the requested information for the 'mkdev' utility. NOTE: When asked for the SCSI ID, use the corresponding logical drive number associated with the adapter. * Relink the kernel * Reboot the system * Invoke the 'mkdev' utility; type 'mkdev hd' * Create and install your new disk partition(s) * Invoke 'mkdev fs' to mount the new filesystem. 3.4 Increase Logical Drive Size 'Increase Logical Drive Size' expands the size of all logical drives proportionally in an array. This is useful when you need to increase the size of currently defined logical drives. This function only works on operating systems that support resizing of an existing logical drive definition. After increasing the logical drive size with LDM do the following: For IBM OS/2: * Reboot the system * Run 'fdiskpm' * Define a partition in the increased space of the logical drive * Save the changes * Reboot the system * Format the new partition For Microsoft Windows NT: * Although the disk space is increased, NT Disk Administrator does not recognize the increased space until the system is restarted. Reboot the system. * The increased space can be defined as a new partition or can be added to an NTFS partition already defined as follows: * Start NT Disk Administrator. * Click on the increased space. * Press Ctrl and click the left button on the NTFS partition the increased space to be added. * Click on the Partition pull down menu and select "Extended Volume Set..." * Select "OK" from dialog box. * Disk Administrator will prompt you to restart the system. For Novell Netware: Not Supported For SCO OpenServer: Not Supported 4.0 Trademarks and Service Marks The following terms, denoted by an asterisk (*) in this README, are trademarks or registered trademarks of the IBM Corporation in the United States or other countries: ------------------------------------------ IBM ------------------------------------------ OS/2 ------------------------------------------ NetFinity ------------------------------------------ The following terms, denoted by a double asterisk (**) in this README, are trademarks of other companies as follows: Trademark: Owner: -------------------------------------------------------------- NetWare Novell, Inc. -------------------------------------------------------------- OpenServer The Santa Cruz Operation, Inc. -------------------------------------------------------------- SCO The Santa Cruz Operation, Inc. -------------------------------------------------------------- Microsoft Windows and Windows NT are trademarks or registered trademarks of the Microsoft Corporation. -------------------------------------------------------------- UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Limited. -------------------------------------------------------------- THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE AND MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY PATENTS OR COPYRIGHTS. Note to U.S. Government Users -- Documentation related to restricted rights -- Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp.