|
40.269 bytes |
Service Hints & Tips |
Document ID: GCOR-3EGDUJ |
PC Server 704 - IBM PC ServeRAID administration and monitoring utilities
Applicable to: World-Wide
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 NT 4.x
1.3 Installation Steps for Windows NT 4.x from CD-ROM Using CD-ROM Boot Support.
1.4 Installation Steps for NetWare 4.1x
1.5 Installation Steps for NetWare 3.1x
1.5.1 Administration and Monitoring in NetWare
1.6 Installation Steps for SCO OpenServer 5.0
1.7 Installing DOS Driver for CD-ROM Access
2.0 IBM PC 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 Using the IBM PC ServeRAID Adapter with the IBM PC Server 704:
4.0 Logical Drive Migration Operating System Specific Instructions:
4.1 Introduction
4.2 Change RAID Levels
4.3 Increase Free Space
4.4 Increase Logical Drive Size
5.0 Trademarks and Service Marks
1.0 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 the hard disk.
1.1 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 driver 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
SET COPYFROMFLOPPY=1
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 the 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
5. Edit the CONFIG.SYS file and verify that only one "BASEDEV=IPSRAID.ADD" statement appears in this file.
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.
6. 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
SET COPYFROMFLOPPY=1
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.
1.2 Installation Steps for Windows NT 3.51 and NT 4.x
1. Prepare the hard disk drives of your server according to the instructions in the Windows NT 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. Select either "Express" or "Custom Setup" on the "Windows NT Setup" screen.
4. 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".
5. Select Others from the list of SCSI adapters.
6. When prompted to insert "Manufacturer-supplied support disk" insert the IBM PC ServeRAID Adapter Device Driver/Utils Diskette into drive A:
7. Select "IBM PC ServeRAID Adapter" and press <Enter>.
8. Continue with the normal installation process according to the instructions in the Windows NT manual.
9. After completing the install of NT, apply any ServicePacks required.
10. Once installed, the administration and monitoring function can be installed by inserting the ServeRAID Remote Administration diskette and running setup.
1.3 Installation Steps for Windows NT 4.x from CD-ROM using CD-ROM Boot Support.
1. Press <Ctrl + I> at PC Server 704 BIOS message.
2. Select Advanced Function from the MiniConfigurator Menu.
3. Select Boot-CDROM and Int13 Extensions.
4. Select BIOS Support for Bootable CD_ROM if it is not set to Yes.
5. Exit from MiniConfigurator and restart the system
6. Insert IBM PC ServeRAID Device Driver Diskette in the default diskette drive and NT boot CD-ROM in the CD ROM drive.
7. Press <F6> at the NT setup message, Setup is inspecting your computer's hardware configurations...
8. 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".
9. Select Others from the list of SCSI adapters.
10. When prompted to insert "Manufacturer-supplied support disk" insert the IBM PC ServeRAID Adapter Device Driver/Utils Diskette into drive A:
11. Select "IBM PC ServeRAID Adapter" and press <Enter>.
12. Continue with the normal installation process.
1.4 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 to choose the Server Drivers - Disk Driver
Note: If device driver supplied in the NetWare install CD is selected by the install program, deselect the default driver and continue with install step 2.
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 <Enter> 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 <Enter> 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.
1.5 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.
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.
Note: When a rebuild, synchronization, or logical drive migration is in process, IPSRADM.NLM cannot be terminated by pressing the <Esc>. To terminate during one of these operations, unload IPSRADM.NLM.
1.6 Installation Steps for SCO OpenServer 5.0
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.
4. At the "Boot:" prompt type "link" and press <Enter>
5. When asked for the name of the package to load, type "ipsraid"
6. 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 <Enter> 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
7. 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?" Press <Y>.
The system backs up the old kernel by moving /unix to /unix.old. When the system asks for kernel environment to be rebuilt, press <Y>. The system will respond with a successful message.
6. Use "shutdown" to bring down the system and then reboot it.
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 IBM PC ServeRAID Configuration diskette into the diskette drive and type: CD DOS 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 PC 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, and Novell NetWare** 3.x/4.x.
These programs are located on the diskette in the following locations:
IBM OS/2 \OS2\IPSRADM.EXE Diskette 2
Microsoft Window NT \IPSRAIDM.EXE Diskette 3
Novell NetWare \NETWARE\IPSRADM.NLM Diskette 2
Follow the instructions above for installation and operation.
2.3 Client/Server Version Requirements
The client/server implementation requires a Microsoft Windows 32-bit workstation as the client with TCP/IP installed. This includes: Windows NT Server, Windows NT Workstation, and Windows 95.
The server application is currently supported on IBM OS/2, Microsoft NT Server/Workstation 3.51/4.x, 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 ServeRAID Remote Administration Diskette
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 SCO BTLD diskette
Note: The client and the server systems must be on a network supporting TCP/IP.
2.4 Client/Server Installation Instructions
To install the client from a command prompt run a:\setup.
To install the IBM OS/2 Server Utility :
1. Create an 'IPSRAID' directory on the hard disk:
2. Type: MD C:\IPSRAID
3. Copy file 'A:\REMOTE\SERVERS\OS2\IPSADM.EXE' into the directory:
4. Type: COPY A:\REMOTE\SERVERS\OS2\IPSADM.EXE C:\IPSRAID\IPSADM.EXE
5. Copy icon 'A:\REMOTE\SERVERS\OS2\IPSADM.ICO' into the directory:
6. Type: COPY A:\REMOTE\SERVERS\OS2\IPSADM.ICO C:\IPSRAID\IPSADM.ICO
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 Utility:
1. Create an 'IPSRAID' directory on the hard disk.
2. Type MD C:\IPSRAID
3. Copy the file 'A:\REMOTE\SERVERS\NT\IPSADM.EXE' into the directory.
4. Type COPY A:\REMOTE\SERVERS\NT\IPSADM.EXE C:\IPSRAID\IPSADM.EXE
5. Copy the icon file 'A:\REMOTE\SERVERS\NT\IPSADM.ICO' into the directory
6. Type: COPY A:\REMOTE\SERVERS\NT\IPSADM.ICO C:\IPSRAID\IPSADM.ICO
7. NT 3.5x - 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Æ
8. NT 3.5x - Open the File menu and choose New...
9. NT 3.5x - Click 'OK' making sure 'Personal Item' is selected
10. NT 3.5x - Enter the following:
Description: IPSRAID Admin/Monitor Server
Command Line: C:\IPSRAID\IPSADM.EXE
Working Dir: C:\IPSRAID
11. NT 4.x - 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Æ
12. NT 4.x - In the æCreate ShortcutÆ window.
13. Type: C:\IPSRAID\IPSADM.EXE or Click the æBrowseÆ button and Open the IPSADM.EXE file
14. NT 4.x - Click æNextÆ
15. NT 4.x - In the æSelect a Title for the ProgramÆ window.
16. Type IPSRAID Admin/Monitor Server
17. NT 4.x - Click æFinishÆ
18. NT 4.x - Open the properties for the shortcut. Right-click on the icon and select æPropertiesÆ
19. NT 4.x - Click on the æShortcutÆ notetab
20. Click on 'Change Icon'
21. Click 'OK' in the information window
22. In the 'Change Icon' window
23. Type: C:\IPSADM\IPSADM.ICO or Click browse and select C:\IPSADM\IPSADM.ICO
24. Click 'OK' for the icon
25. Click 'OK' for the program properties
26. Double-Click the new icon to access the administrator
To install the Novell NetWare 3.x/4.x 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.NLMC:\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 install the SCO OpenServer 5.X Server Utility
Note: The SCO server utility 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 &
2.5 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:<number> specifies the port number on which the server will listen for client connections
-f:<filename> 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:<filename> 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 unecrypted passwords, therefore the file must 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.
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 initialize/synchronize the drive. Click on a physical device button to access information on the physical device or to set its device state.
3.0 Using the IBM PC ServeRAID Adapter with the IBM PC Server 704:
The 704's internal drive bays are managed directly over the SCSI bus (rather than through a separate DASD status cable) via an intelligent SCSI processor device embedded in each internal hot-swap backplane.
All devices on a single SCSI channel must be assigned a unique ID. Since the 704's internal backplanes are themselves SCSI devices, one of the SCSI IDs on each of the ServeRAID adapter's internal channels will be assigned to each backplane. The PC Server 704 assigns each internal hot-swap backplane to SCSI ID 6 (which corresponds to bay 7).
To view the ServeRAID's current SCSI device ID assignments, please use one of the ServeRAID utilities (such as the Configuration Diskette, or the Monitor utility, or the BIOS-based <Ctrl + I> Mini-Config Utility). The bay/ID assigned to the backplane will appear as a SBY ("standby") or PRC ("processor") device.
4.0 Logical Drive Migration Operating System Specific Instructions:
4.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 Log Drive Size | |
|
OS/2 |
Yes |
Yes |
Yes |
|
Windows NT |
Yes |
Yes |
Yes |
|
Netware |
Yes |
Yes |
No |
|
OpenServer |
Yes |
Yes |
No |
4.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.
4.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 your 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 your 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
* Reinvoke the 'mkdev' utility; type 'mkdev hd'
* Create and install your new disk partition(s)
* Invoke 'mkdev fs' to mount the new filesystem.
4.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.
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
5.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:
--------------------------------------------------------------
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.
--------------------------------------------------------------
|
Search Keywords |
| |
|
Hint Category |
RAID, Hardware Maintenance Information | |
|
Date Created |
20-02-97 | |
|
Last Updated |
11-02-99 | |
|
Revision Date |
11-02-2000 | |
|
Brand |
IBM PC Server | |
|
Product Family |
PC Server 704, ServeRAID | |
|
Machine Type |
8650, Various | |
|
Model |
| |
|
TypeModel |
| |
|
Retain Tip (if applicable) |
| |
|
Reverse Doclinks |