Dell PowerEdge Expandable RAID Controller 3/Di INSTALLATION GUIDE
Installing on Additional Operating Systems
This chapter explains how to install the controller management software on a Windows NT/Windows 2000 server, workstation, or client; a NetWare server or client; or a Linux system.
Note: If you want to install the controller management software on a boot
container, you must first create a boot container and then install the
PERC 3/Di driver as part of the operating system installation. For more
information, see Installing the Device Driver. For information on creating a boot container, see Using the BIOS Container Configuration Utility. |
See the documentation for the controller management software for instructions on using the software to manage storage.
The following section explains how to install the controller management software on Windows. You can manage a controller using FAST or Array Manager; however, the following instructions assume you will be installing FAST. If you plan to install Array Manager, please consult the Array Manager documentation for installation instructions.
You must first install the Dell PERC 2 API kit followed by the Dell PERC 2 Agent kit. If you install the Dell PERC 2 API kit on Windows 2000, you are required to reboot to complete the installation. Thus, at the end of the installation, you will be prompted to reboot the machine. You are not required to reboot when installing on Windows NT.
The Dell PERC 2 CLI kit has the same requirement to first install the Dell PERC 2 API kit followed by the Dell PERC 2 Agent kit.
Within the limitations described in this section, you can install any or all of the kits separately, depending on the functions you require.
You can install any of these kits on a system that does not have PERC 2 or ROMB hardware or drivers on it. This is sometimes appropriate. For example, if you want to use a workstation as a remote management station, you can install the Dell PERC 2 API and Dell PERC 2 FAST GUI kits. When you do this, you need to realize that any API or management functions that require local hardware will not work correctly.
The default target directory is \Program Files\PERC2\.
The Dell PERC 2 FAST GUI and the Dell PERC 2 CLI both add entries to the following menu:
Start>Programs>Dell PERC2
Each installation records a log file showing the steps and status of the installation. These logs are written to the AFA\Logs subdirectory under the target installation directory. By default, they appear in the following location:
\Program Files\PERC2\AFA\Logs
To begin the installation:
For each kit that you are installing, beginning with the Dell PERC 2 API kit:
Remote Management Software Install, No PERC 2, 2/Si, 3/Si, 3Di Hardware
Otherwise, continue with the default selection.
You must uninstall the Dell PERC 2 API kit last. If you try to uninstall the API kit while the other kits are still installed, the API uninstaller displays an error telling you to uninstall the other kits first.
If you have installed both the Dell PERC 2 Event Snap In kit and Dell PERC 2 Agent kit, you must uninstall the Event Snap In kit before the Agent kit. If you try to uninstall the Agent kit first, the uninstaller displays an error telling you to uninstall the Event Snap In kit first.
You must uninstall the Dell PERC 2 CLI kit and the Dell PERC 2 Event Snap In kit before you can uninstall the Dell PERC 2 Agent kit.
To perform the following procedure, you must be signed on as an administrator or have administrative privileges.
Follow these steps to uninstall the controller management software:
A reboot is required only after removing the Dell PERC 2 API kit from a Windows 2000 machine.
The following section explains how to install the controller management software on NetWare. Note that on NetWare, the controller can only be managed locally with the CLI. However, you can manage a NetWare controller remotely using FAST or Array Manager, if you have FAST or Array Manager installed on a Windows NT or Windows 2000 system, and have established a network connection between the two systems.
Note: Before beginning this installation, ensure that the NetWare server is down and that you are at the DOS prompt. |
To install the controller management software on NetWare:
copy a:\nwappd1.exe c:\[pathname]
where pathname is a directory on a local DOS partition.
Caution: Do not copy the nwappd1.exe file to the nwserver directory, since when the file is uncompressed, you may overwrite files that should not be overwritten. |
Answer Yes to uncompress the files.
load \[pathname]\nwsetup
where pathname is the directory where you extracted the files.
Note: To get to the console on a NetWare system, when the server comes up, go to the Novell icon, select Exit GUI, and confirm your choice. |
The contents of the file sys:system\fsanw5.ncf (for NetWare 5.0 or 5.1 systems), which load the tcpip and spxs modules, as well as the controller management software modules, are then appended to AUTOEXEC.NCF.
Note: Before you attempt to remotely manage the PERC 3/Di controller from a Windows system running FAST or Array Manager, be sure that communication with the server using the network is already established. (See the documentation provided with your TCP/IP software for instructions on establishing communications.) |
The controller management software for Linux consists of the command line interface (CLI) which allows you to manage the controller from a terminal emulator. On a Linux system, without the CLI, you can manage the controller only through the BIOS.
The Linux controller management software may be delivered on CD-ROM, diskette, or may be downloaded from the Dell Web site. The following instructions assume that the controller management software is delivered on CD-ROM.
To install the controller management software on Linux:
rpm -q afaapps
afaapps-VERSION_NUMBER
rpm -e afaapps-VERSION_NUMBER
The operating system may automount the diskette on /mnt/cdrom. If not:
i Create the mount point by entering the following command:
mkdir /mnt/cdrom
ii Mount the CD-ROM on /mnt/cdrom by entering a command like the following, replacing cdrom_LUN with the logical unit number of your CD-ROM device. In most cases, the default LUN is fd0.
mount -t iso9660 /dev/cdrom_LUN /mnt/cdrom
cd /mnt/cdrom
rpm -i afaapps-VERSION_NUMBER.rpm
umount /mnt/cdrom
If you are installing the controller management software on an operating system not listed in this chapter, please refer to the software kit that shipped with your controller for instructions on how to install the controller management software.