IBM* PC ServeRAID Adapter Device Driver and Administration Utility Installation Diskette 1 - RAID Configuration Diskette 2 - Device Driver and RAID Administration and Monitoring under OS/2*, Windows NT 3.5** Novell NetWare 3.12 and 4.10** Diskette 2 - SCO OpenServer 5.0 BTLD and** Administration and Monitoring Server Service OPERATING SYSTEM INSTALLATION AND RAID ADMINISTRATION NOTE - When installing onto a logical drive whose write policy is set to write-back (WB), wait for 10 seconds after being prompted to press Ctrl+Alt+Del before actually pressing these keys. This gives the RAID Controller enough time to flush out all dirty cache pages to hard disk. INSTALLATION STEPS FOR OS/2 1. Follow instructions in the OS/2 Installation manual to install OS/2 into the hard disk drive. To load the drive during installation, copy the driver IPSRAID.ADD from the OS2 subdirectory of the Device Driver/Administration and Monitor diskette to the copy of the OS/2 Diskette 1 and add the following: BASEDEV=IPSRAID.ADD to the CONFIG.SYS in OS/2 DIskette 1. If diskette 1 does not have enough diskette space to copy the driver, delete device drivers from diskette 1 that are not being used to make space for IPSRAID.ADD. (Make sure that you make a copy of diskette 1 before deleting any files.) To make space in Diskette 1 delete the following file(s) from the copy of OS/2 Diskette 1: AHA152X.ADD, AHA154X.ADD. You also need to remove corresponding basedev statements from the CONFIG.SYS file. (Refer to OS/2 technical documentation for a detailed explanation of the basedev statements in the CONFIG.SYS ). 2. Once OS/2 is installed, put IBM PC ServeRAID Adapter Device Driver/Administration and Monitor Diskette in drive A. 3. Type: DDINSTAL from any OS/2 command prompt. 4. Select "IBM PC 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 NOTE: If you have an Adaptec** SCSI adapter in your system make sure that IPSRAID.ADD BASEDEV statement appears after the Adaptec BASEDEV statement in the CONFIG.SYS. 5. After restarting your system, IBM PC 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. NOTE: OS/2 CD-ROM INSTALLATION Make a copy of the OS/2 Diskette 1 and use the copy of Diskette 1 to install OS/2. Copy IPSRAID.ADD from the OS2 subdirectory of the ServeRAID option diskette to copy of Diskette 1 and add: BASEDEV=IPSRAID.ADD to the CONFIG.SYS file in Diskette 1. If diskette 1 does not have enough diskette space to copy the driver, delete device drivers from Diskette 1 that are not being used to make space for IBMRAID.ADD. Make sure that you make a copy of diskette 1 before deleting any files). The CD-ROM can be connected to any channel and can have SCSI-IDs 0 to 6 as long as it does not conflict with other SCSI device IDs or bays (equivalent SCSI-ID) that is currently connected to the ServeRAID Adapter. INSTALLATION STEPS FOR Windows NT 3.5 1. Prepare the hard disk drives of your server according to the instructions in Windows NT 3.5 manual. 2. Boot to a DOS Disk and run FDISK to create an active partition the size of the logical drive that was defined to install NT. You don't need to format the partition, the NT install will do this. 3. If you do not have NT ServicePack 3, then download it from the Microsoft ftp site. The ServicePack 3 is 7 diskettes and a README disk. a. ftp to ftp.microsoft.com b. login as anonymous c. cd to 'bussys/winnt/winnt-public/fixes/usa/nt351/ussp3/i386/disks.35' d. type 'bin' e. type 'prompt' to disable interactive prompting f. You may wish to specify a local directory by typing 'lcd c:\path' g. type 'mget .' On the NT ServicePack Disk 1, there is a file named NTKRNLMP.EX_. Use the expand command to expand the file to NTKRNLMP.EXE. Then, copy this file onto the original NT 3.51 Install Disk 1. The new NTKRNLMP.EXE file is dated 10-7-95 and size 515,234. NOTE: If you have a NT ServicePack which is later than ServicePack 3 use that instead of ServicePack 3. 4. Boot the NT 3.51 modified install disk 1. 5. Select either "Express" or "Custom Setup" on the "Windows NT Setup" screen. 6. 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". 7. Select Others from the list of SCSI adapters. 8. When prompted to insert "Manufacturer-supplied support disk" insert the IBM PC ServeRAID Adapter Device Driver/Utils Diskette into drive A: 9. Select "IBM PC ServeRAID Adapter" and press Enter. 10. Continue with the normal installation process according to the instructions in the Windows NT 3.5 manual. 11. After completing the install of NT, apply ServicePack3 BEFORE running any of the applications, especially Disk Administrator. 12. Once installed, the administration and monitoring function can be started by starting the IPSRAIDM.EXE from any command prompt. IPSRAIDM.EXE is supplied in the REMOTE directory in the IBM PC ServeRAID Adapter Device Driver/Utils Diskette. INSTALLATION STEPS FOR NetWare 4.1X Follow the instructions in the NetWare 4.1X manual. The IBM PC ServeRAID driver IPSRAID.HAM is supplied in the NetWare directory. Make sure that you have the latest NWPA.NLM loaded. The latest NWPA.NLM and other NLM and CDM available at the time of this diskette release is supplied in the NetWare directory. 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 Device Driver/Administration and Monitor diskette, press the Ins (Insert) key. A message will appear reminding that INSTALL.NLM will search the root directory of path A:. At this time modify the path to A:\NETWARE using the F3 key. Press the Enter key to continue. 3. You will be provided with a list of available drivers found on the floppy disk. 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 Device Driver/Administration and Monitor diskette, press the Ins (Insert) key. A message will appear reminding that INSTALL.NLM will search the root directory of path A:. At this time modify the path to A:\NETWARE using the F3 key. Press the Enter key to continue. 6. You will be provided with a list of available drivers found on the floppy disk. Select the driver IPSRAID.HAM. As a result of this process, INSTALL.NLM will also update the STARTUP.NCF file as needed to automatically load the IPSRAID.HAM subsequent load of the server. INSTALLATION STEPS FOR NetWare 3.1X Follow the instructions in the NetWare 3.1X manual. The IBM PC 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 the changes in to the STARTUP.NCF file to load necessary NetWare modules. You can install NetWare 3.1X 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 Device Driver/Administration and Monitor diskette at the DOS command prompt and type A:\NETWARE\INSTALL 4. Follow the NetWare 3.1X 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.1X 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 Device Driver/Administration and Monitor diskette at the DOS command prompt and 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.1X 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. 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 If you load NWASPI.CDM you may have to power cycle the server when you unload NWASPI.CDM. 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. INSTALLATION STEPS FOR SCO OpenServer 5.0 Notes: 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. Note: 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 PC ServeRAID Adapter Support diskette" for SCO. 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 floppy 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 floppy drive from which to install 4. Insert the "IBM PC ServeRAID Adapter Support Diskette" for SCO 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. 6. Use "shutdown" to bring down the system and then reboot it. 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 IBM PC 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. IBM PC ServeRAID Adapter Remote Administration/Monitor Function Introduction The utilities contained on this diskette are to be used with the IBM PC ServeRAID adapter. They assist in the configuration, administration, and monitoring of the adapter. There are versions for local administration (administering a system containing the adapter from that system) as well as a version for remote administration (administering a system containing the adapter from another system on a network). Local Version Requirements The local 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 - Novell NetWare 3.x/4.x These programs are located on the diskette in the following locations: IBM OS/2 \OS2\IPSRADM.EXE Microsoft Window NT \REMOTE\IPSRAIDM.EXE Novell NetWare \NETWARE\IPSRADM.NLM Follow the instructions below for installation and operation. Client/Server Requirements The client/server (remote) implementation requires a Microsoft Windows 32-bit workstation as the client with TCP/IP installed. This includes: - Windows NT Server - Windows NT Workstation - Windows 95 The server application is currently supported on IBM OS/2, Microsoft NT Server/Workstation 3.51+, Novell NetWare 3.x/4.x and SCO OpenServer 5.x platforms. These programs are located on the diskette in the following locations: Windows Client \REMOTE\IPSRAIDM.EXE IBM OS/2 Server \REMOTE\SERVER\OS2\IPSADM.EXE Microsoft Window NT Server \REMOTE\SERVER\NT\IPSADM.EXE Novell NetWare Server \REMOTE\SERVER\NETWARE\IPSADM.NLM SCO OpenServer (located on the SCO BTLD diskette) NOTE: The client and the server systems must be on a network supporting TCP/IP. Client/Server Installation Instructions To install the client --> 1) Create an 'IPSRAID' directory on the hard disk: type: MD C:\IPSRAID 2) Copy the file 'A:\REMOTE\IPSRAIDM.EXE' into the directory: type: COPY A:\REMOTE\IPSRAIDM.EXE C:\IPSRAID\IPSRAIDM.EXE 3) Create an icon for the application: From the Program Manager, open the group you want this application in (for example, Applications), or create a new group 1) Select the 'File' menu 2) Select the 'New Item' option and click on 'OK' 3) For 'Description', enter 'IPSRAID Admin/Monitor' 4) For 'Command Line', enter 'C:\IPSRAID\IPSRAIDM.EXE' 5) Select 'Change Icon' to select an appropriate icon 6) Click on 'OK' 4) Double-Click on the new icon to access the administrator. To install the IBM OS/2 Server Executable --> 1) Create an 'IPSRAID' directory on the hard disk: type: MD C:\IPSRAID 2) Copy file 'A:\REMOTE\SERVERS\OS2\IPSADM.EXE' into the directory: type: COPY A:\REMOTE\SERVERS\OS2\IPSADM.EXE C:\IPSRAID\IPSADM.EXE 3) Copy icon 'A:\REMOTE\SERVERS\OS2\IPSADM.ICO' into the directory: type: COPY A:\REMOTE\SERVERS\OS2\IPSADM.ICO C:\IPSRAID\IPSADM.ICO 4) Create an icon for the application: 1) Open the Templates Folder 2) Drag a 'Program Template' onto the Desktop 3) At the Program Tab, enter: Path and file name: C:\IPSRAID\IPSADM.EXE 4) At the General Tab, enter: Title: IPSRAID Admin/Monitor Find Current Icon: IPSADM.ICO 5) Double-Click the new icon to access the administrator To install the Microsoft Windows NT Server/Workstation Server Executable --> 1) Create an 'IPSRAID' directory on the hard disk: type: MD C:\IPSRAID 2) Copy file 'A:\REMOTE\SERVERS\NT\IPSADM.EXE' into the directory: type: COPY A:\REMOTE\SERVERS\NT\IPSADM.EXE C:\IPSRAID\IPSADM.EXE 3) Copy icon 'A:\REMOTE\SERVERS\NT\IPSADM.ICO' into the directory: type: COPY A:\REMOTE\SERVERS\NT\IPSADM.ICO C:\IPSRAID\IPSADM.ICO 4) Create an icon for the application: a) Choose a group or create a new group to put the new icon: for example, Administrative Tools or IPSADM Admin/Monitor b) Open the File menu and choose New... c) Click 'OK' making sure 'Personal Item' is selected d) Enter the following: Description: IPSRAID Admin/Monitor Command Line: C:\IPSRAID\IPSADM.EXE Working Dir: C:\IPSRAID e) Click on 'Change Icon' f) Click 'OK' in the information window g) In the 'Change Icon' window, type C:\IPSADM\IPSADM.ICO or click browse and select C:\IPSADM\IPSADM.ICO h) Click 'OK' for the icon i) Click 'OK' for the program item j) Double-Click the new icon to access the administrator To install the Novell NetWare 3.x/4.x Server NLM --> 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 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\IPSADMNLM 2) From the system console, load the NLM, type: LOAD C:\NWSERVER\IPSADM.NLM or LOAD \SYSTEM\IPSADM.NLM To install the SCO OpenServer 5.X daemon --> Note: The SCO server daemon is installed from the BTLD disk during installation of the IBM PC ServeRAID adapter device driver. The file is installed into the '/usr/bin' directory. If the program does not run by entering 'ipsadm &', follow the directions below: 1) Insert the IBM PC ServeRAID adapter BTLD into the SCO system 2) Create a directory for the server daemon mkdir /ipsraid 3) Mount the floppy drive 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 floppy drive umount /mnt 6) Start the server daemon to run in the background ./ipsadm & Using the Server Application The server programs for all platforms (OS/2, Windows NT) are very similar in functionality. They accept optional command-line parameters to tune your system. They are as follows: -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 standard output, usually the active window -? 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 or to a text file on the system using the -f parameter. The default is to log messages to a text file named 'ipsadm.log' in the current directory. Logged messages are startup information, connecting and disconnecting clients, and error messages. 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. Using the Application 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 'Hostname' from the 'Options' menu. A window appears prompting for 'This Host' or a 'Remote Host', select the 'Remote Host' radio button. Fill in the hostname of the server in the edit box and click 'OK'. Once the interface is initialized, you can select a variety of buttons to investigate adapter information. Click on an adapter button to retrieve information about the adapter or to retrieve adapter error logs. Click on a logical drive button to access information about the logical drive or to delete/sync the drive. Click on a physical device button to access information on the physical device or to set its device state. 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: -------------------------------------------------------------- Adaptec Adaptec, Inc. -------------------------------------------------------------- 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. --------------------------------------------------------------