1. am25plus.zip Driver
2. README.TXT File Contents

README.TXT Driver File Contents (am25plus.zip)

Dell OpenManage(TM) Array Manager 2.5 Readme

This readme file contains updated information for your "Dell
OpenManage Array Manager User's Guide" and any other
technical documentation included with this product.

Always refer to the Dell Web site at http://support.dell.com
for the most current information.

The following sections contain updated requirements and open issues
for the Dell OpenManage Array Manager 2.5 software product.

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

Notes, Notices, Cautions, and Warnings

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

Throughout this guide, blocks of text are used to draw your attention
to important information about your system. These blocks are notes, 
notices, and warnings, and they are used as follows:

NOTE - A NOTE indicates important information that helps you make 
better use of your system.

NOTICE - A NOTICE indicates either potential damage to hardware or
loss of data and tells you how to avoid the problem.

WARNING - A WARNING indicates the potential for bodily harm and tells
you how to avoid the problem.

Some warnings may appear in alternate formats. In such cases, the
specific presentation of the warning is mandated by regulatory
authority.


######################################################################

Dell OpenManage Array Manager 2.5

######################################################################


======================================================================
SYSTEM REQUIREMENTS
======================================================================

The following subsections contain general system and software
requirements and specific Microsoft(R) Windows(R) and Novell(R) 
NetWare(R) software requirements.

---------------------------------------------------
General Requirements
---------------------------------------------------

* 64 megabytes (MB) of random-access memory (RAM)

* Dell(TM) PowerEdge(TM) Expandable RAID Controller 2 (PERC 2) 
  PERC 2/Single Channel (SC)
  PERC 2/Dual Channel (DC)
  PERC 2/Single Integrated (Si)
  PERC 3/Single Integrated (Si)
  PERC 3/Dual Integrated (Di)
    and/or
  PERC 3/Dual Channel Lite (DCL)

* Simple Network Management Protocol (SNMP) services for SNMP support
  (optional)

---------------------------------------------------
Windows Specific Requirements
---------------------------------------------------

* 40 MB of free hard-disk drive space

* Microsoft Windows NT(R) Version 4.0 with Service Pack 5 or later
    OR
  Microsoft Windows 2000 with Service Pack 1

* Administrator riqhts

* Transmission Control Protocol/Internet protocol (TCP/IP) connection
  on the console and server when attempting remote node management

* Microsoft Internet Explorer version 4.0 or later for online
  help

* Microsoft Management Console (MMC) version 1.1 or later for
  snap-in support (optional)

---------------------------------------------------
NetWare Specific Requirements:
---------------------------------------------------

* 15 MB of free hard-disk drive space

* Novell NetWare version 4.2 with Support Pack 8 or later; in addition,
  WinSock 2 support needs to be enabled after installing Support 
  Pack 8.

  OR
 
  Novell NetWare version 5.0 with Support Pack 4 or later

  OR
 
  Novell NetWare version 5.1

* Novell NetWare Client version 4.6 or later

* TCP/IP required for connection to management console

* Long filename support

======================================================================
WARNINGS
======================================================================
* Dell PowerEdge 2200, 4200, and 6100 servers are not 
  supported by this software.

* Clustered PERCs are not supported by this software.

* Array Manager 2.5 is not backward compatible with previous versions
  of Array Manager. You must uninstall the previous version before 
  installing version 2.5.

* When importing a foreign disk that contains a dynamic volume created
  previously by Array Manager, you must import all of the disks at the
  same time. Failure to do so results in data loss.

* Do not remove a hard-disk drive from its enclosure while the hard-
  disk drive's individual activity light emitting diode (LED) is 
  blinking. This action is likely to cause severe data loss.

* PERCs have a feature called "PowerFail" that uses up to two assigned
  hot spares during reconfiguration of a virtual disk (Transform Type,
  Add Member). While this reconfiguration is in progress, do not remove
  the hot spares that are part of the reconfiguration.

* You should be logged into the local machine with Administrator access
  rights when you launch the Array Manager Console.

======================================================================
CD DIRECTORY STRUCTURE
======================================================================

\DOCUMENTATION - Contains the Array Manager documentation
\DRIVERS\NT40\PERC2 2.1 - Contains PERC 2 2.1 drivers for Windows NT
\DRIVERS\NT40\PERC2SC - Contains PERC 2/SC drivers for Windows NT
\DRIVERS\NT40\PERC2DC - Contains PERC 2/DC drivers for Windows NT
\DRIVERS\NT40\PERC2SI - Contains PERC 2/Si drivers for Windows NT
\DRIVERS\NT40\PERC3SI - Contains PERC 3/Si drivers for Windows NT
\DRIVERS\NT40\PERC3DI - Contains PERC 3/Di drivers for Windows NT
\DRIVERS\W2k\PERC2 2.1 - Contains PERC 2 2.1 drivers for Windows 2000
\DRIVERS\W2k\PERC2SC - Contains PERC 2/SC drivers for Windows 2000
\DRIVERS\W2k\PERC2DC - Contains PERC 2/DC drivers for Windows 2000
\DRIVERS\W2k\PERC2SI - Contains PERC 2/Si drivers for Windows 2000
\DRIVERS\W2k\PERC3SI - Contains PERC 3/Si drivers for Windows 2000
\DRIVERS\W2k\PERC3DI - Contains PERC 3/Di drivers for Windows 2000
\DRIVERS\NETWARE\PERC2 - Contains PERC 2 2.1 drivers for NetWare
\DRIVERS\NETWARE\PERC2SC - Contains PERC 2/SC drivers for NetWare
\DRIVERS\NETWARE\PERC2DC - Contains PERC 2/DC drivers for NetWare
\DRIVERS\NETWARE\PERC2SI - Contains PERC 2/Si drivers for NetWare
\DRIVERS\NETWARE\PERC3SI - Contains PERC 3/Si drivers for NetWare
\DRIVERS\NETWARE\PERC3DI - Contains PERC 3/Di drivers for NetWare
\FIRMWARE\PERC2 2.1 - Contains PERC 2 2.1 firmware
\FIRMWARE\PERC2SC - Contains PERC 2/SC firmware
\FIRMWARE\PERC2DC - Contains PERC 2/DC firmware
\FIRMWARE\PERC2SI - Contains PERC 2/Si firmware
\FIRMWARE\PERC3SI - Contains PERC 3/Si firmware
\FIRMWARE\PERC3DI - Contains PERC 3/Di firmware
\SETUP - Contains the Array Manager setup files
\UPDATE - Contains the HTML Help Viewer update package

======================================================================
REQUIRED DRIVER AND FIRMWARE REVISIONS
======================================================================

* PERC
  - Not supported on any operating system
  - Supported by Array Manager version 2.0 for Windows NT and NetWare

* PERC 2/SC
  - Windows NT driver version 2.32
  - Windows 2000 driver version 2.62
  - NetWare driver version 2.06
  - Firmware version 3.13

* PERC 2/DC
  - Windows NT driver version 2.32
  - Windows 2000 driver version 2.62
  - NetWare driver version 2.06
  - Firmware version 1.01

* PERC 3/DCL
  - Windows NT driver (not supported)
  - Windows 2000 driver version 5.16
  - NetWare driver (not supported)
  - Firmware version 1.48

* PERC 2 (1.1)
  - Not supported on any operating system
  - Upgrade your firmware and driver to PERC 2 
    version 2.1

* PERC 2 (2.1)
  - Windows NT driver, build 2938
  - Windows 2000 driver, build 2947
  - NetWare driver, build 2956
  - Firmware, build 2957

* PERC 2/Si
  - Windows NT driver build 2938
  - Windows 2000 driver build 2947
  - NetWare driver build 2956
  - Firmware build 2939

* PERC 3/Si
  - Windows NT driver build 2938
  - Windows 2000 driver build 2947
  - NetWare driver build 2956
  - Firmware build 2951

* PERC 3/Di
  - Windows NT driver build 2938
  - Windows 2000 driver build 2947
  - NetWare driver build 2956
  - Firmware build 2951

======================================================================
COMPATIBILITY ISSUES
======================================================================

---------------------------------------------------
Compatibility Issues with the Flexible Array 
Storage Tool (FAST) on Windows NT and Windows 2000
---------------------------------------------------

You can install both Array Manager and FAST on the same Windows NT
or Windows 2000 server. You can use only one program at a time to
actively configure PERC 2, PERC 2/Si, PERC 3/Si, or PERC 3/Di
controllers. The interface supports two different access rights:
read-only and read-write.
 
To maintain the integrity of the storage device configuration, the
interface grants read-write access to one application only and
read-only access to others. When Array Manager is launched, it first
attempts read-write access. If read-write access is denied, Array
Manager grants read-only access to the controller. When Array 
Manager is launched in read-only mode, you can view storage devices
and storage device properties, but you cannot configure controllers
or devices on them.
  
If you want to launch Array Manager in read-write access mode, make
sure that FAST is not running.

NOTE: If FAST is launched while the Array Manager Disk Management
Service is stopped, FAST is given read-write access to any
controllers it opens. You must close FAST and then restart the
Disk Management Service (from the Array Manager Service Manager)
to manage PERC 2, PERC 2/Si, PERC 3/Si, or PERC 3/Di controllers with
Array Manager. The same NOTE applies to the command-line interface
(CLI) utility for the PERC 2, 2/Si, 3/Si, and 3/Di controllers.

Note for Windows 2000: Uninstalling FAST after installing 
Array Manager breaks the Array Manager install. At this
point, it is necessary to reinstall Array Manager to 
manage your PERC 2, 2/Si, 3/Si, and 3/Di controllers. 
To avoid this problem, Dell recommends that FAST be 
uninstalled before installing Array Manager.

---------------------------------------------------
Compatibility Issues With FAST on NetWare
---------------------------------------------------

Array Manager and FAST might cause problems if they are installed
on the same NetWare server. FAST installs all of its files to 
the system directory on the NetWare server, so the FAST files 
are loaded before Array Manager's files. Array Manager and FAST
use some of the same files; therefore, if the files in the system
folder are older than the files on the Array Manager CD, Array
Manager will not work properly. The installation program detects
this and forces you to disable the conflicting files before
continuing the installation. Disabling the files renames the 
"fsamutex.nlm" and "partapl.nlm" extensions to ".bak." If you
want to change the files back to their original extensions,
simply rename the files with the ".nlm" extension.

---------------------------------------------------
Compatibility Issues With the PERC Console
---------------------------------------------------

You can install both Array Manager and the PERC Console on the 
same server. However, you can use only one program at a time to 
configure PERC 2/SC, 2/DC, and 3/DCL controllers. To maintain the
integrity of the storage device configuration, simultaneous use of
Array Manager and PERC Console is not supported. Dell recommends 
that Array Manager and PERC Console not be used at the same time 
on the same server after the Array Manager installation is
complete.

---------------------------------------------------
Compatibility Issues With Disk Administrator
---------------------------------------------------

Never use Disk Administrator while Array Manager is running, 
particularly if tasks are running on the controller at the same 
time. Data loss can occur if both applications are running
simultaneously.

---------------------------------------------------
Disabling the Array Manager Service
---------------------------------------------------

If you do not want the Array Manager service to start automatically
each time you boot your machine, perform the following steps:
  
1. Point to Start --> Settings --> Control Panel.

2. Click Services, and then click Disk Management Service.

3. Click Startup.

4. Under Startup Type, select Manual

The Disk Management Service automatically starts any time the
console is opened, and it can also be started from Service Manager.

NOTICE: If the Disk Management Service is not started, you will not
receive any alerts or warnings in the case of failure.

======================================================================
KNOWN ISSUES
======================================================================

* When attempting to connect to a remote server, an "amconsole.exe"
  application error message pops up.

  Problem: This occurs on a console-only installation on Windows 2000
  when not logged in as an administrator.

  Solution 1: Log in as an administrator.

  Solution 2: Re-install Array Manager and install both the console
  and the managed node.

  Solution 3: Launch Array Manager from the Computer Management window.
  To do this, right click the "My Computer" icon and select "Manage".
  Under "Storage", click "Disk Management (Dell OpenManage Array Manager)".

* The installation fails and displays an error message referring to 
  an error with "iKernel.exe" at the beginning of the installation.
  
  Problem: This is a problem in the Installshield installation engine
  that occurs when running the installation without administrator rights.

  Solution: Log in with administrator rights and run the install again.

* The Split Mirror and Restore Dead Disk Segment operations are missing
  on NetWare.

  Problem: The Split Mirror and Restore Dead Disk Segment operations
  are not available when managing a NetWare server.

  Solution: This is working as designed; these options are available
  only on Windows NT.

* Multiple simultaneous operations on NetWare cause strange or 
  slow console behavior.

  Problem: Controllers on a NetWare server that are performing
  multiple simultaneous operations might cause the remote
  console to appear "frozen."

  Solution: The console returns to normal operation when the
  operations are complete.

  Dell recommends that you do not perform more than two simultaneous 
  controller operations on a NetWare server.

* A NetWare server abends when performing Add Member or Transform
  Type functions with PERC 2/SC or PERC 2/DC RAID controllers.
  
  Problem: When performing either an Add Member or Transform Type 
  function with a virtual disk smaller than 1 gigabyte (GB) might
  abend the NetWare server containing the virtual disk.

  Solution: For NetWare, this function is unstable with virtual
  disks smaller than 1 GB. Do not use these functions with virtual 
  disks unless they are 1 GB or larger.

* Distributed Component Object Model (DCOM)

  Problem: A large number of DCOM messages appear in the Event
  Viewer, resulting in the following message:

  "DCOM was unable to communicate with the computer ...
  using any of the configured protocols."

  Solution: Run "dcocnfg.exe" and click the Default Protocols tab.
  Remove all of the protocols EXCEPT "Connection-oriented TCP/IP."

  NOTICE: If other applications reside on a server and they require
  DCOM to use protocols other than TCP/IP, they will no longer 
  function correctly. If this is the case, the suggested course of
  action is to leave the DCOM configuration as it is.

* PercRAID.Log Events in the Windows NT Event Log

  Problem: The PERC Console (a legacy Dell RAID configuration
  utility) installs a service called "PercRAID" that monitors
  the status of PERC 2/SC, 2/DC, and 3/DCL RAID controllers.
  When unassigning a hot spare from within the Array Manager
  console, the PercRAID service logs an event to the system
  log warning you that a disk has failed.

  Solution: This error message is incorrect; the disk is ready for
  use immediately after unassigning it.

* NetWare version 4.2 is missing various NetWare Loadable Modules
  (NLMs) required by Array Manager.
 
  Problem: When attempting to start Array Manager on NetWare version
  4.2, the console may report that a number of NLMs (such as
  "cdbe.nlm," "ws2_32.nlm," and so on) are not loaded.

  Solution: Array Manager requires the WinSock 2 update on NetWare
  version 4.2 servers. This update is available from the Novell Web
  site at http://www.novell.com/download/index.html. See "Winsock 2
  on Novell NetWare Version 4.2," found later in this document for
  instructions about how to enable WinSock 2 support after installing
  Support Pack 8.

* Array Manager does not protect a system disk from deletion in
  NetWare.

  Problem: Depending on the RAID controller, there are various
  methods to completely remove the RAID configuration from
  your controller. The Windows NT version of Array Manager
  does not allow you to delete any virtual disk that
  contains a system volume. However, the NetWare version
  of Array Manager does not protect you from deleting these
  virtual disks.

  Solution: No solution is available at this time. Be very careful
  when deleting virtual disks or performing an operation that removes
  all of the virtual disks from a controller. Make sure you know
  what data is on any volumes created on them.

* A drive letter is unavailable for use.
  
  Problem: After deleting a basic disk, the drive letter used by that
  disk is no longer available.

  Solution: Reboot the server and the drive letter will be available
  again.

* A volume created from a RAID policy does not display label.

  Problem: The volume created from a RAID policy (the last volume of
  a multiple volume set) does not have a label after completion of
  the RAID policy.

  Solution: After completion of the RAID policy, manually refresh the
  console.

* PowerEdge RAID controller 2/SC or 2/DC cannot be seen on Windows 2000.

  Problem: Arrays are not visible on the console when there is a
  PowerEdge RAID controller 2/SC or 2/DC on Windows 2000.

  Solution: Create the first virtual disk using the controller BIOS
  accessed by pressing the <Ctrl><M> keys at system startup.

* Problems deleting the last virtual disk on PowerEdge RAID controllers
  2/SC, 2/DC on Windows 2000

  Problem: The message "Enquiry Error" pops up when attempting to delete
  the last virtual disk on a PERC 2/SC or 2/DC controller on Windows
  2000.

  Solution: Do not attempt to delete the last virtual disk on an array
  controlled by a PERC 2/SC or 2/DC controller on Windows 2000.

* Reconfiguration on a PERC 2, 2/Si, 3/Si, or 3/Di on NetWare does not
  behave as expected.

  Problem: Reconfiguring a concatenated virtual disk with NetWare on 
  a PERC 2, 2/Si, 3/Si, or 3/Di RAID controller might cause the Array
  Manager service to hang.

  Solution: This will be addressed in a future version of Array Manager.
  Dell recommends that you do not reconfigure a concatenated virtual disk
  with NetWare on one of these controllers at this time.

* Problems using the Express Mode to create a Raid 10 virtual disk

  Problem: Using the Express Mode in the Create Virtual disk Wizard to
  create a Raid 10 virtual disk may result in the creation of a Raid 1
  instead, on the PERC 2/DCL PERC 2/DC and the PERC 2/SC Raid controllers.

  Solution: Use the Custom mode in the Create Virtual disk Wizard to create
  the Raid 10 virtual disk.

* Problems with the display of virtual disks in the disk folder on Windows
  2000 for the PERC 2/SC or 2/DC controllers

  Problem: Virtual disks are not associated with the correct disk in the
  disk folder on Windows 2000 for the PERC 2/SC or PERC 2/DC controllers.

  Solution: Make sure that at an enclosure or disk array is attached to each
  PERC 2/SC and PERC 2/DC controller.

* "Specified Object no longer exists" popup messages

  Problem: "Specified Object no longer exists" popup message appears when
  upgrading a basic disk to a dynamic disk on Windows 2000.

  Solution: Perform a rescan operation, then try the upgrade to dynamic
  disk operation again.

* NetWare server abends when a NetWare virtual disk that contains a
  NetWare partition is deleted.

  Problem: Attempting to delete a NetWare virtual disk that contains a 
  NetWare partition may cause your server to abend.

  Solution:  Dell recommends that you delete all NetWare partitions from
  a virtual disk before you attempt to delete it.  This issue will be
  addressed in future versions of Array Manager.

* Two Array Manager consoles can not simultaneously be connected and
  managing the same server.

  Problem: Array Manager does not support having two consoles connected to
  the same server and running concurrent operations.  This can cause
  unexpected results such as NetWare abends or data corruption.

  Solution: Be sure to only have one Array Manager console connected to a
  particular server.  

* Array Manager MMC Snapin may not work on Windows NT

  Problem: After installation and setup, Array Manager may not be able to be
  launched from MMC.

  Solution: This is being investigated by Dell and is planned to be resolved
  in the next release of Array Manager.

* Array Manager displays/logs deleted virtual disk messages on Windows 2000
  servers after a virtual disk is created.

  Problem: When creating a virtual disk, Array Manager will log three
  messages that it receives from Windows 2000.  One of these messages
  indicates that a virtual disk has been deleted and is displayed in a pop
  up dialog window on the server containing the virtual disk.

  Solution:  Disregard the deleted virtual disk message.  No virtual disk has
  been deleted in a create virtual disk operation.  This is a side effect of
  creating virtual storage on a Windows 2000 system.  Dell is working to
  resolve this inconvenience.  

======================================================================
WINSOCK 2 ON NOVELL NETWARE VERSION 4.2, SUPPORT PACK 8
======================================================================

After installing Support Pack 8, manually copy the files in the
extracted SP8 directory (nw4sp8\tools\coredump) to somewhere in
the server's search path, (for example,  sys:\system; Novell
documentation recommends copying these files to c:\nwserver on
the boot partition).

======================================================================
VIEWING TRAPS WITH HP OPENVIEW NETWORK NODE MANAGER SPECIAL
EDITION (NNM SE)
======================================================================

The "arymgr.cfg" and "arymgr.mib" files are in the Management
Information Base (MIB) directory of your installation directory.

To view trap events with strings inserted, perform the following steps:

1. Load the Dell Array Manager MIB "arymgr.mib." When prompted to
   "Load a TRAP-TYPE/NOTIFICATION-TYPE macro," select Cancel.

2. Run the "xnmevents-replace arymgr.cfg" command.

3. Stop and start the HP OpenView NNM services. Under the
   HP OpenView folder, select "NNM Services-Stop" and then 
   select "NNM Services Start."

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

Copyright (c) 1998 Chris Maunder

Some cryptographic code in this product is derived from the SSLeay
library, copyright (c) 1995-97 by Eric Young (eay@cryptsoft.com). All
rights reserved.

Trademarks used in this text: Dell, Dell OpenManage, and PowerEdge
are trademarks of Dell Computer Corporation; Microsoft, Windows, and
Windows NT are registered trademarks of Microsoft Corporation;
Novell and Netware are registered trademarks of Novell Incorporated;
Adobe is a trademark of Adobe Systems Incorporated. OpenVIew is a
trademark of the Hewlett-Packard Company. Other trademarks
and trade names may be used in this document to refer to either the
entities claiming the marks and names or their products. Dell Computer
Corporation disclaims any proprietary interest in trademarks and trade
names other than its own.

November 2000