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

DELL OPENMANAGE(TM) SERVER ADMINISTRATOR 1.3 README

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

This file contains updated information for your "Dell OpenManage
Server Administrator User's Guide" and any other technical
documentation included with Server Administrator. 

NOTE: See the Dell OpenManage Array Manager "readme" file (located 
      in the "am3xx" directory on the "Systems Management" CD) 
      for supplemental information regarding the Storage Management 
      Service.

The Server Administrator documentation includes the "User's Guide", 
the "Messages Reference Guide", the "CIM Reference Guide", the 
"Command Line Interface (CLI) User's Guide", the "SNMP Reference 
Guide", and the "Compatibility Guide". You can access all the 
documentation from the product documentation CD or from the Dell 
Support website at "support.dell.com".
 
See the Dell Support website ("support.dell.com") for the most
current information.

This document is organized into the following sections:

* Server Administrator User Notes
* Known issues for Server Administrator


######################################################################
WHAT'S NEW IN THIS RELEASE OF SERVER ADMINISTRATOR?
######################################################################

Server Administrator adds Red Hat Linux 8.0 to the list of supported 
operating systems. In addition to maintaining support for Microsoft(R) 
Internet Explorer and Netscape, Server Administrator 1.3 adds support 
for the Mozilla 1.0 open-source Web browser. 

You can perform several new tasks using the Sever Administrator 
interface. Under "Preferences" in both the GUI and the command line 
interface (CLI), you can configure user access and the SNMP root 
password. User access configuration allows the Administrator to 
determine whether any user below the level of Administrator has
access to Server Administrator's systems management software. 
SNMP configuration allows the root user to reset the SNMP root 
password. In the CLI, root password reset cannot be accomplished 
interactively, adding to the security of the system.

The Server Administrator 1.3 Remote Access Service features new 
capabilities for adding a Certificate Signature Request (CSR). The 
Remote Access Controller (RAC) that comes with your system has a default 
certificate of authenticity issued by Dell. You can replace the 
default certificate with a certificate unique to your own business 
by generating a CSR, sending the CSR to a certificate authority (CA), 
and uploading the certificate you receive from the CA to the RAC. 

The Server Administrator 1.3 Update Service features the ability to 
update DRAC II firmware remotely. 

######################################################################
"SYSTEMS MANAGEMENT" CD VERSION 3.3 SUPPORTED SYSTEMS
######################################################################

Dell OpenManage Server Administrator 1.3 on "Systems Management" CD 
version 3.3. 

The following Dell(TM) PowerEdge(TM) systems are supported for "Systems 
Management" CD version 3.3: 300, 350, 500SC, 600SC, 1300, 1400, 1500SC, 
1550, 1600SC, 1650, 2300, 2400, 2450, 2500, 2550, 2600, 2650, 4300, 
4350, 4400, 4600, 6300, 6350, 6400, 6450, 6600, 6650, and 8450.

######################################################################
SUPPORTED WEB BROWSERS
######################################################################

* Microsoft Internet Explorer 5.0 or later on Microsoft Windows NT 4.0, 
  Windows 2000, and Windows XP PRO

* Mozilla 1.0.x running with Red Hat Linux 7.2, 7.3 and 8.0

* Netscape Navigator 6.2.x on Microsoft Windows NT 4.0, Windows 2000,
  and Windows XP and Red Hat Linux 7.2, 7.3 and 8.0

NOTE: When using Internet Explorer or Netscape Navigator on systems
      running Microsoft Windows, to view localized versions of the RAC's 
      Web-based remote access interface, open the Windows "Control Panel", 
      double-click the "Regional Options" icon, and select the desired 
      locale from the "Your locale (location)" drop-down menu.

######################################################################
SERVER ADMINISTRATOR USER NOTES
######################################################################

This section provides information to help enhance your experience with
Server Administrator in particular implementations and environments.


======================================================================
NOTES FOR INSTALLATION AND UNINSTALLATION
======================================================================

* See the file "qig.txt" in the root directory on the "Systems 
  Management" CD for basic installation instructions for all supported 
  operating systems.

* Before you install Server Administrator, it is recommended that you
  uninstall any previous installations of Resolution Assistant. 

* If you are running IT Assistant or any other application on the 
  Systems Management CD, close the application before installing
  Server Administrator.

* Array Manager has both a Managed System and a Management 
  Station (console) component. The managed system portion of Array 
  Manager replaces the Windows Disk Management Service. To view 
  the Disk Management page, install the Management Station portion 
  of Array Manager on the same system as the managed system portion.  

  During a custom installation of Array Manager, if you select Storage 
  Management and choose not to install the Storage Management Console, 
  the Server Administrator installation program installs only the 
  managed system portion of Array Manager. Array Manager does not allow 
  the Disk Management page to load unless the Management Station
  portion is also installed. 

* You cannot deselect specific services during the custom installation
  and then install older versions of other service components such as
  the Instrumentation Service, Storage Management Service, or the
  Diagnostic Service.

* For PowerEdge 8450 systems, allow the system to run for
  approximately 30 minutes before upgrading from a previous Dell
  OpenManage product release to this current release.

* Novell(R) NetWare(R) software for RAID controllers is available
  in the "\support\Netware\RAID" directory on the "Systems 
  Management" CD.
  
* Red Hat Linux software for RAID controllers is available in the
  "/support/Linux/RAID" directory on the "Systems Management" CD.

* LSI Logic offers a CIM solution application for monitoring 
  1020/1030-based PCI SCSI controllers, which includes the 
  Dell PERC 4/im controller. This application is available for Red Hat
  Linux operating system versions 7x as supported by the system. The 
  application and installation instructions are located on the "Systems 
  Management" CD in the "\ihv\cim_linux" directory.

======================================================================
NOTES FOR THE INSTRUMENTATION SERVICE
======================================================================
* CMOS Clear Operations for PowerEdge 2450 Systems:

  For PowerEdge 2450 systems that are new or have undergone a CMOS 
  clear operation, the "Primary SCSI" setting is reported as "unknown" 
  or "off" even after setting the onboard SCSI controller to "ON" in 
  the BIOS setup. To ensure that value is reported correctly, click 
  "Primary SCSI", set the state appropriately, and then click "Apply".
  
* Dell MIB Files for PowerEdge Systems: 

  Dell MIB files for PowerEdge systems allow customers to obtain 
  and verify information provided by supported software agents.  
  The current MIB files supported by PowerEdge software agents are
  located at "\support\dcpemibs" on the "Systems Management" CD.

  NOTE: A MIB-II-compliant, SNMP-supported network management
        station is required to compile and browse the MIB files.


* Precompiled Kernels Supported by Server Administrator
  With Prebuilt Device Drivers
  -----------------------------------------------------
  | Operating System        | Kernel                  |
  -----------------------------------------------------
  | Red Hat Linux 7.2       | 2.4.7-10                |
  |                         | 2.4.7-10smp             |
  |                         | 2.4.7-10enterprise      |
  -----------------------------------------------------
  | Red Hat Linux           | 2.4.9-e.3               |
  | Advanced Server 2.1     | 2.4.9-e.3smp            |
  |                         | 2.4.9-e.3enterprise     |
  -----------------------------------------------------
  | Red Hat Linux 7.3       | 2.4.18-4                |
  |                         | 2.4.18-4smp             |
  |                         | 2.4.18-4bigmem          |
  -----------------------------------------------------
  -----------------------------------------------------
  | Red Hat Linux 8.0       | 2.4.18-14                |
  |                         | 2.4.18-14smp             |
  |                         | 2.4.18-14bigmem          |
  -----------------------------------------------------

======================================================================
NOTES FOR THE UPDATE SERVICE
======================================================================

* BIOS updates are currently available only for Microsoft Windows
  operating systems supported by Server Administrator. Red Hat Linux 
  and Novell NetWare operating systems do not currently support BIOS 
  updates from Server Administrator.


=======================================================================
NOTES FOR THE DIAGNOSTIC SERVICE
=======================================================================

* For a full list of hardware devices supported by Server Administrator
  diagnostics, see the "Server Administrator Compatibility Guide".
	
======================================================================
NOTES FOR THE REMOTE ACCESS SERVICE
======================================================================

This service is supported on PowerEdge 1600SC, 1650, 2600, 2650, 
4600, 6600, and 6650 systems only. It enables remote access to a 
server that has lost its network connection or that has become 
unresponsive. In this release of Server Administrator, the Remote 
Access Service uses one of the following remote access controllers 
(RACs): Dell Remote Access Card (DRAC) III, DRAC III/XT, Embedded 
Remote Access (ERA), or Embedded Remote Access Option (ERA/O).

RACs also have their own command line interface that is accessed
through the racadm command. You can add racadm commands to a
batch or script file to automate various user tasks. To limit the
stress load on the managed system and RAC, you should add "sleep"
or "delay" commands of one or two seconds between the individual
racadm commands.

For systems running supported Red Hat Linux operating systems, 
the Remote Access Service supports Netscape Navigator.


######################################################################
KNOWN ISSUES FOR SERVER ADMINISTRATOR
######################################################################

This section provides information on open issues with this release of
Server Administrator.

======================================================================
ISSUES FOR SERVER ADMINISTRATOR RUNNING ON ALL SUPPORTED OPERATING
SYSTEMS
======================================================================

* There may be a reporting error for the amount of memory enabled 
  for the Level 2 (L2) cache memory when you view "Processors" for 
  PowerEdge 6600 and 6650 systems. When you use the Server 
  Administrator System --> Main System Chassis--> Processor interface 
  and click on the connector name for "Proc_n", where n can be from 1 
  to 4, depending on the number of processors installed, the L2 cache 
  may be displayed incorrectly as 256 K.

  If you purchased more than 256 K of L2 cache with your system, all of 
  the L2 cache you have installed is fully enabled. The reporting error 
  will be corrected in a future BIOS release for the PowerEdge 6600 and 
  6650 systems.

* If you are using Internet Explorer 5.0 to operate Server Administrator 
  and you have the "Automatically Detect Settings" checkbox selected 
  on in the Local Area Network proxy settings page of Internet Explorer, 
  you may experience performance problems and inconsistent results from 
  Server Administrator pages. Upgrade to Internet Explorer 5.5 or later.

* Clicking the browser "Back" button may not display the correct page
  with respect to the Server Administrator component tree, tabs, or
  tab menus.

  Example:

  1. Click "Main System Chassis" under "System Component Tree".

  2. Click "Fans" under "Main System Chassis".

  3. Click "Alert Actions" on the tab menu bar.

  4. Click the "Back" button on the browser.

     This action takes you to the "Fan Probes" page, leaving the tab
     menu bar unchanged. This action places the "Fan Probes" page
     under "Alert Actions" on the tab menu bar instead of under
     "Fan Probes".

* Selecting the boot sequence under the BIOS "Setup" tab does not 
  re-enable boot devices that have been previously disabled in 
  the System Setup Program.

* The links on the Server Administrator home page might lock up after 
  repeated random clicking. To resolve this situation, refresh the 
  browser by pressing <F5> or by clicking the browser refresh button. 

* All unsecure HTTP requests to Server Administrator receive an
  invalid response. Server Administrator runs only one instance 
  of the Web server, which is secure. Make all connections 
  through https://<ip address>:<port number>. Any 
  http://<ip address>:<port number> request for connection 
  with the server receives an invalid response.

* If the browser used with Server Administrator indicates that it
  cannot display a page or perform an action, ensure that the
  browser is in online mode. To go online, perform one of the
  following steps:

  -  If you are using Netscape Navigator, click "File" on the menu
     bar, point to "Offline", and select "Work Online".

     OR

  -  If you are using Internet Explorer, click "File" on the 
     menu bar and deselect the "Work Offline" option. When "Work
     Offline" is selected, a check displays to the left of the option
     on the "File" menu.

* If you are using Netscape Navigator and you receive the error
  message "Netscape was unable to connect to the network because you
  are offline...", Server Administrator is in offline mode. Go online
  to avoid this message.

* If Internet Explorer prompts you to "Work Offline", "Connect", or
  "Try Again", always select "Connect" or "Try Again". Do not select
  "Work Offline".

* For PowerEdge 8450 systems running Array Manager, allow the 
  system to run for approximately 30 minutes before logging in to the 
  Server Administrator Web server. If you do not wait 30 minutes,
  Array Manager might not be displayed on the Server Administrator 
  home  page or Server Administrator might hang.

* When setting dates in the "Asset Information" section of the Server 
  Administrator home page, the current time is appended to the date. 
  When setting dates with the Command Line Interface, the appended 
  time is noon.

* If Network Adapter Teaming is installed and enabled on your system, 
  Server Administrator does not display the IP address or other 
  connection-related data for the individual network adapters. The 
  connection status and IP address belong to the virtual adapter 
  created by the teaming software. The virtual adapter is not 
  currently displayed in Server Administrator.

* For systems running a supported Red Hat Linux operating system, 
  kernel driver messages such as "AAC_ChardevOpen" or "Attached scs 
  CD-ROM sr0 at scsi0" are sometimes displayed in the console at the 
  login prompt. These messages are displayed in the console when the 
  driver initialization is delayed by the installation of Server 
  Administrator services and can be safely ignored.

======================================================================
ISSUES FOR SERVER ADMINISTRATOR RUNNING ON ALL MICROSOFT WINDOWS
OPERATING SYSTEMS
======================================================================
* Execute all Server Administrator CLI commands from a 32-bit Windows 
  command prompt. Acceptable ways to access the 32-bit command prompt 
  are through the Start-> Programs-> Accessories-> Command prompt and 
  through Start-> Run "cmd.exe". Attempts to run the CLI commands from 
  the DOS command "command.com" may produce unpredictable results.

======================================================================
ISSUES FOR SERVER ADMINISTRATOR RUNNING ON ALL NOVELL NETWARE
OPERATING SYSTEMS
======================================================================

* If you shut down Server Administrator on a system running NetWare 
  using the "sys:\system\dell\omanage\iws\bin\netware\omastop.ncf" 
  command, the shutdown script unloads the Java Virtual Machine on 
  the NetWare system. As a result, all applications using the Java 
  NLM are also shut down.

* Under "Network information", the IP address is displayed as 
  "Not Obtained".

======================================================================
ISSUES FOR SERVER ADMINISTRATOR RUNNING ON THE NOVELL NETWARE 5.1
OPERATING SYSTEM
======================================================================


* When you log into Server Administrator for the first time on a 
  system running NetWare 5.1, the information displayed on the Server 
  Administrator home page might be incomplete. If this occurs, press 
  <F5> to refresh the browser window. Complete information for your 
  managed system should now be visible on the Server Administrator 
  home page.

* If you receive an "NDSComponentException" message while starting 
  Server Administrator, perform one of the following procedures:

  - If the default certificate is corrupt or does not exist, see the
    "Web Server and Security Setup" section of the "Server Administrator 
    User's Guide" to create a new certificate.

  - If the host name is not present in "client_properties.ini" and
    "server_properties.ini", perform the following steps:

    1. Open the "client_properties.ini" file in
       "SYS:\system\dell\OpenManage\IWS\config".

    2. Change "host name" to your system name on the line
       "nssl.keystore = certificate name - hostname".

    3. Open the "server_properties.ini" file in
       "SYS:\system\dell\OpenManage\IWS\config".

    4. Change "certificate name" and "host name" to your system
       name on the line "nssl.keystore = certificate name - hostname".

* If you receive an "SSLComponentException" message while starting 
  Server Administrator, perform the following steps (not setting
  "classpath" correctly to "SYS:\java\lib\nssl1.1_exp.jar" might be
  a reason for this exception):

  1. Ensure that "nssl1.1_exp.jar" or "nssl1.1_dom.jar" exists in the
     "SYS:\java\lib" directory.

  2. Set "classpath" to "SYS:\java\lib\nssl1.1_exp.jar" or
     "SYS:\java\lib\nssl1.1_dom.jar" by typing one of the
     following commands:
		       
     envset classpath=$classpath;SYS:\java\lib\nssl1.1_exp.jar

     envset classpath=$classpath;SYS:\java\lib\nssl1.1_dom.jar
    
  NOTE: If the previous solutions do not match your configuration, 
        see the Java SSL FAQ at "developer.novell.com" for solutions
        that might match your configuration.

* When installing Server Administrator on Novell NetWare 5.1 with Java 
  Virtual Machine (JVM) 1.1.7B and Support Pack 3, you might receive a 
  "java.io" exception after you finish the installation and restart 
  the managed system. To correct this issue, go to the Novell support 
  website at "support.novell.com" and download the latest version of 
  JVM 1.1.7B dated after 07/23/2001. The TID number for this incident 
  on the Novell website is 10066646.

* If you are using the NOVONYX Web server in NetWare 5.1 with Server
  Administrator, the Server Administrator Web server may stop
  responding after some time. To avoid this behavior, ensure that
  the NOVONYX Web server starts after the Server Administrator Web
  server by performing the following steps:

  1. Find the following line in the "AUTOEXEC.NCF" file:

     NSWEB

     This line starts the NOVONYX Web server.

  2. Move this line to either the end of the "AUTOEXEC.NCF" file
     or to another location that is after (below) the following line:

     SYS:\SYSTEM\DELL\OMANAGE\IWS\BIN\NETWARE\OMASTART.NCF

     This line starts the Server Administrator Web server.

* If you install Server Administrator on a system running NetWare 5.1
  and Java 1.1.7B, the Server Administrator pages do not display
  correctly in Netscape 6.1 or 6.2. 

* If you install Server Administrator on a system running NetWare 5.1
  and Java 1.1.7B, the Server Administrator service may hang if you
  load ConsoleOne on the NetWare system. You must run the following 
  commands at the NetWare command prompt to restart the server after 
  you have exited from ConsoleOne:

	SYS:\SYSTEM\DELL\OMANAGE\IWS\BIN\NETWARE\OMASTOP
	SYS:\SYSTEM\DELL\OMANAGE\IWS\BIN\NETWARE\OMASTART


======================================================================
ISSUES FOR SERVER ADMINISTRATOR RUNNING ON THE NOVELL NETWARE 6.0
OPERATING SYSTEM
======================================================================

* This version of Server Administrator does not support Adaptec CI/O
  on systems running Novell NetWare 6.0.


  NOTE: Although the Adaptec CI/O option is available from the main
        installation menu for systems running NetWare 6.0, the
        installation program blocks this component. This menu item
        is intended to accommodate future versions of the software.

======================================================================
ISSUES FOR SERVER ADMINISTRATOR RUNNING ON RED HAT LINUX OPERATING 
SYSTEMS
======================================================================

* When using the Mozilla browser on Red Hat Linux, the font and type 
  size on the Server Administrator global navigation bar appear different
  from the default font and type size that Server Administrator uses.

======================================================================
ISSUES FOR INSTALLATION AND UNINSTALLATION
======================================================================

The following are open issues and workarounds, where available, for
Server Administrator on systems running Windows NT, Windows 2000, 
Red Hat Linux, or Novell NetWare operating systems.

----------------------------------------------------------------------
INSTALLATION AND UNINSTALLATION ISSUES FOR ALL SUPPORTED 
OPERATING SYSTEMS
----------------------------------------------------------------------

* See the file "qig.txt" in the root directory on the "Systems 
  Management" CD for basic installation instructions for all supported 
  operating systems.

* Versions of Array Manager that were installed from the "Dell OpenManage 
  Applications" CD version 1.6 must be uninstalled through the operating 
  system (such as "Add/Remove Program" in Windows) before upgrading to 
  the current version of Array Manager using the "Systems Management" CD 
  version 3.3.

* For systems running a supported Windows or Red Hat Linux operating 
  system, some managed system components cannot be uninstalled using 
  the Systems Management CD. These components must be uninstalled using 
  the operating system (using "Add/Remove Program" for Windows, or running 
  the appropriate RPM command for Red Hat Linux).

* If you already have Adaptec Fast Console installed on your 
  system, you must uninstall this application before installing 
  the Storage Management Service.

* If you have Dell OpenManage Resolution Assistant installed on your
  system, you must manually uninstall it before installing any systems
  management applications.

----------------------------------------------------------------------
INSTALLATION AND UNINSTALLATION ISSUES FOR SUPPORTED WINDOWS
OPERATING SYSTEMS
----------------------------------------------------------------------

* On systems running a Windows operating system, when you uninstall 
  all the management station components using the "Add/Remove Program" 
  function, an empty folder named "Dell OpenManage Applications"  
  might be left in the "Start" menu under "Programs". It is safe to
  manually remove this folder.

* When performing an unattended uninstall of managed system components 
  via the "setup.exe /u" command, it is strongly recommended that you 
  reboot your system after the uninstall. Without the reboot, the 
  Windows Disk Management tool may not function.

* Before installing Citrix Metaframe (all versions), you must 
  uninstall any previous versions of Server Administrator. Errors may 
  exist in the registry after a Citrix Metaframe installation.

----------------------------------------------------------------------
INSTALLATION AND UNINSTALLATION ISSUES FOR SUPPORTED WINDOWS NT
OPERATING SYSTEMS
----------------------------------------------------------------------

* Due to a Windows security policy issue, you can only uninstall 
  Dell OpenManage Server Agent if you are logged in with the same 
  user ID that was originally used when Server Agent was installed. 
  To upgrade to Server Administrator from any version of Server Agent, 
  you must log into the system to be managed with the same user ID 
  that was used when Server Agent was installed. If this user 
  account is not available, you must reinstall your current version 
  of Server Agent and then upgrade to Server Administrator.

* The Windows installer service does not allow installation using 
  Terminal Services when mapping to a remote CD drive.

  Because the Windows installer service runs as a system service, when 
  an administrator performs an installation from a remote session on 
  Windows 2000, the installation must use a universal naming convention 
  (UNC) path and not a mapped drive letter. In this case, drive letters 
  mapped in a remote session may not be visible to the Windows installer 
  service.

* If you install Intel(R) Client Instrumentation for DMI and SNMP from
  the "Systems Management" CD version 3.0 on a system running 
  Windows NT 4.0 and then upgrade the operating system to Windows 
  2000, you see the following error message in the event log:

  "Intel Client Instrumentation for DMI and SNMP hung on starting."
   
  Intel Client Instrumentation for DMI and SNMP is not supported on
  Windows 2000.

* When you install the Adaptec CI/O Management package, the following
  warning appears in the Windows event log:

  "The SNMP Service is ignoring extension agent key
  SOFTWARE\...\SNMPAgent\CurrentVersion because it is missing or
  misconfigured."

  You can safely ignore this message.


* During installation, the installation procedure may appear to hang 
  at around 40 percent complete. The installation module is waiting 
  for the SNMP service to stop before proceeding. This waiting period
  can last up to 3 minutes.

----------------------------------------------------------------------
INSTALLATION AND UNINSTALLATION ISSUES FOR SUPPORTED RED HAT LINUX 
OPERATING SYSTEMS
----------------------------------------------------------------------

* Installing Server Administrator on systems running supported
  Red Hat Linux operating systems does not require that you 
  reboot the system to complete installation.

* When "/var" is full, you may receive the error message "Operating 
  system support for SNMP is not installed....". This message may or 
  may not be correct. Regardless, the instrumentation installation
  fails. Free space in "/var" is required for the installation to 
  function properly. Free up space in "/var" and reinstall.

----------------------------------------------------------------------
INSTALLATION AND UNINSTALLATION ISSUES FOR SUPPORTED NOVELL NETWARE 
OPERATING SYSTEMS
----------------------------------------------------------------------

* Installing Server Administrator on systems running supported 
  Novell NetWare operating systems requires that you run the 
  "restart server" command to complete the installation.

* For NetWare systems running Adaptec CI/O:

  When the Adaptec CI/O Administrator is uninstalled from a system
  running NetWare 5.x, the following message appears on the
  System Console:

  "Unloading CI/O Management Service (IOMGR) is not recommended.
   Unload module anyway? n"

  When the Instrumentation Service uninstallation program detects the
  Adaptec CI/O Administrator on your system, the program switches to
  the System Console to provide this message to the user. To unload
  the Adaptec CI/O Administrator and allow the uninstallation program
  to continue, press <y>.


* For managed systems running NetWare 5.1 or 6.0:
  
  Before running the Server Administrator installation in silent mode,
  ensure that the NWconfig utility is not running. The Server
  Administrator installation depends on the NWconfig utility; if
  the NWconfig utility is already running when you start a silent
  installation, the NWconfig utility aborts and displays the
  message "This module is already loaded and cannot be loaded more
  than once." 


======================================================================
ISSUES FOR INSTRUMENTATION
======================================================================

The following are open issues and workarounds, where available, for
Server Administrator on systems running Windows NT, Windows 2000, Red 
Hat Linux, or Novell NetWare operating systems.

----------------------------------------------------------------------
INSTRUMENTATION ISSUES FOR ALL OPERATING SYSTEMS
----------------------------------------------------------------------

* The NIC configuration information within the Server Administrator
  "BIOS Setup" screen may be inaccurate for embedded NICs. Using the
  Server Administrator "BIOS Setup" screen to enable or disable 
  NICs might produce unexpected results. It is recommended that you
  perform all NIC configurations through the actual System Setup
  screen that is available by pressing <F2> while a system is booting.
  This issue is present in the CLI interface and in IT Assistant.

* If a system with spare bank memory enabled enters a "redundancy 
  lost" state, it may not be apparent which memory module is the cause. 
  If you cannot determine which DIMM to replace, see the "switch to 
  spare memory bank detected" log entry in the ESM system log to find 
  which memory module failed.

* Setting any warning threshold to a default value is not supported on 
  PowerEdge 1650, 2600, 2650, 4600, 6600, and 6650 systems. Attempting 
  to do so results in an error message.

* Warning thresholds that are modified on the following systems are 
  reset to their default values if the system is power cycled or loses 
  AC power: PowerEdge 1650, 2600, 2650, 4600, 6600, and 6650 systems.

  If you change the warning threshold values and notice that
  they have been reset to default values after a reboot, then you must
  add the relevant "omconfig" commands to your system startup
  sequence. For example, if you want to set the warning thresholds for
  fan zero to a minimum of 1000 and a maximum of 5300, add the
  following command to your startup sequence:

  omconfig chassis fans index=0 minwarnthresh=1000 maxwarnthresh=5300

  Ensure that the "omconfig" command is invoked after system services
  have started. See the "Command Line Interface User's Guide" for more 
  information.

----------------------------------------------------------------------
INSTRUMENTATION ISSUES FOR WINDOWS NT AND WINDOWS 2000 OPERATING
SYSTEMS
----------------------------------------------------------------------

* To use the Instrumentation Service SNMP Subagent with HP OpenView
  Network Node Manager (NNM) Version 6.1, you must install the 
  HP OpenView consolidated patch that contains the NNM_00496 patch on
  your system. To download the patch, go to the Hewlett-Packard
  website at "www.hp.com".

* In some circumstances the Server Administrator CIM interface may 
  not be properly registered with the operating system and may not
  function. To resolve this situation, perform the following steps:
	
  1. Open a command prompt window.
	
  2. Change to the installation directory, which is typically 
     "C:\Program Files\Dell\OpenManage\OMSA\bin".
	
  3. Run the command "regsvr32 dccim32.dll".

----------------------------------------------------------------------
INSTRUMENTATION ISSUES FOR RED HAT LINUX OPERATING SYSTEMS
----------------------------------------------------------------------

* Server Administrator does not show the IP address and connection
  status for PowerEdge systems if the system has a Broadcom Gigabit 
  Ethernet card installed and is running the Red Hat Linux 7.3 operating 
  system. To correct this issue you must install the bcm5700 driver on 
  your system.
 
  1. Place the "Dell OpenManage Server Assistant" CD in a system
     running a Windows operating system.

  2. Locate "Broadcom: NetXtreme Family of Adapters (Driver) 6.0"
     for Red Hat Linux 7.3 for your PowerEdge system and copy the
     files to a diskette.

NOTE: The "Dell OpenManage Server Assistant" CD contains a precompiled 
      version of the bcm5700 driver for the 2.4.18-4 Red Hat Linux kernel. 
      The CD also contains the source files if you have updated your 
      operating system to a later kernel. Use the ".src.rpm" file for the 
      NIC to compile the driver for your version of the kernel. Instructions 
      for compiling the driver for a different kernel version are included 
      with the driver source.

3. Using the directions that come with the driver, install the
   bcm5700 driver.

4. View the "/etc/modules.conf" file. Substitute all occurrences of "tg3" 
   with "bcm5700". For example, edit the following line:

   "alias eth1 tg3"

   to read:

   "alias eth1 bcm5700"

5. Edit the "modules.pcimap" file to replace all occurrences of "tg3"
   with "bcm5700".

* "Current Speed" and "Minimum Failure" are the only valid fan 
  threshold values for storage systems attached to managed systems 
  running a Red Hat Linux operating system. All other values are 
  displayed as "unknown". 

* PowerVault 20xS, 21xS, and 22xS storage systems attached to 
  managed systems running a Red Hat Linux operating system cannot 
  be managed by Server Administrator using the following RAID 
  controllers:

  - PERC 2
  - PERC 2/Di
  - PERC 2/Si
  - PERC 3/Di
  - PERC 3/Si

* The following information replaces the section "Copying a 
  Dynamically Built Device Driver to Systems Running the Same Kernel" 
  in the "Server Administrator User's Guide":

  Copying a Dynamically Built Device Driver to Systems Running the 
  Same Kernel

  When Server Administrator dynamically builds a device driver for the 
  running kernel, it installs the device driver into the directory 
  "/lib/modules/<kernel>/misc", where <kernel> is the kernel name 
  returned by typing "uname -r". If you have a system running the same 
  kernel for which a device driver was built, you can copy the newly 
  built device driver to the directory "/var/omsa/dks/<kernel>" on the 
  other system for use by Server Administrator. This action allows 
  Server Administrator to use its Dynamic Kernel Support feature on 
  multiple systems without having to install the kernel source on 
  every system.

  For example: System A is running a kernel that is not supported by 
  one of the Server Administrator prebuilt device drivers. System B is 
  running the same kernel. Perform the following steps to build a 
  device driver on system A and copy the device driver to system B for 
  use by Server Administrator:

  1. Ensure that the Dynamic Kernel Support prerequisites are met on 
     system A.

  2. Install Server Administrator on system A.

     Server Administrator builds a device driver for the kernel 
     running on system A during installation.

  3. Type "uname -r" on system A to determine the name of the 
     running kernel.

  4. Copy the file "/lib/modules/<kernel>/misc/esm.o" from system A 
     to the directory "/var/omsa/dks/<kernel>" on system B, where 
     <kernel> is the kernel name returned by typing "uname -r" in 
     step 3.

     NOTE: You might have to create the directory 
     "/var/omsa/dks/<kernel>" on system B. For example, if the kernel 
     name is "1.2.3-4smp", you can create the directory by typing 
     "mkdir -p /var/omsa/dks/1.2.3-4smp".

  5. Install Server Administrator on system B.

     Server Administrator detects that the device driver you copied to 
     the directory "/var/omsa/dks/<kernel>" supports the running 
     kernel and uses that device driver.

  NOTE: If this procedure is used to install Server Administrator, 
  this procedure must be used to upgrade Server Administrator if the 
  new version of Server Administrator does not support the running 
  kernel with a prebuilt device driver.

  NOTE: When Server Administrator is uninstalled from system B, the 
  "/var/omsa/dks/<kernel>/esm.o" file that you copied to system B is 
  not removed. You must remove the file if it is no longer needed.

----------------------------------------------------------------------
INSTRUMENTATION ISSUES FOR NOVELL NETWARE OPERATING SYSTEMS
----------------------------------------------------------------------

* The Instrumentation Service might incorrectly report NetWare version
  5.1 as version 5.0.

* On managed systems running a Novell NetWare operating system, the
  Instrumentation Service loads multiple NetWare Loadable Modules
  (NLMs) at system startup. Some NLMs are automatically uninstalled
  because they are not required on a particular system. The NLM
  uninstallation process occurs approximately 2 minutes after you 
  boot the system. During this uninstall process, a module unloading
  message appears on the Novell NetWare system console. 

* After installing the Instrumentation Service, the user reboots the
  system to make the newly installed managed system services available
  for use. While rebooting, the system might hang if Adaptec CI/O
  management software is installed.

  To avoid a hung system during reboot, perform the following 
  steps:

  1. Remove "dcstart.ncf" from "autoexec.ncf".

  2. After the system reboots, run "dcstart.ncf" from the 
     NetWare command line.

  NOTE: Adaptec CI/O is not supported on NetWare 6.0. When upgrading a
        system from NetWare 5.x to NetWare 6.0, uninstall Adaptec CI/O
        before upgrading the operating system.

======================================================================
ISSUES FOR DIAGNOSTICS
======================================================================

The following subsections list the currently known issues regarding
implementation and operation of the diagnostic tests offered in
Server Administrator.

----------------------------------------------------------------------
ISSUES FOR ALL OPERATING SYSTEMS
----------------------------------------------------------------------

* For a list of Dell-supplied hardware devices that Server 
  Administrator diagnostics specifically supports, see to the Server 
  Administrator Compatibility Guide.

* When you upgrade from Server Diagnostics version 1.1 to the Server 
  Administrator Diagnostic Service, the history file is saved in the 
  "result.xml" file in the "\bak" directory located in the root 
  installation directory.

* If you are using Server Administrator on a system that is completely 
  isolated on a network (cannot ping any other systems), you may 
  experience performance problems and may receive inconsistent results 
  from the Diagnostics Service if the "Automatically detect settings" 
  checkbox is selected in the Local Area Network proxy settings page of 
  Internet Explorer, and your version of Internet Explorer is earlier 
  than 5.5. 

  To correct this issue, deselect the "Automatically detect settings" 
  checkbox.

* After running a diagnostic test that requires a high percentage of 
  CPU resources, you may experience slow browser response time in 
  Netscape 6.2.x. To restore normal browser response time, you must 
  end the Netscape 6.2.x browser process. In Red Hat Linux, locate 
  the process ID for "netstat" and type the "kill -9" command followed 
  by the process ID number. In a Windows operating system, open the 
  "Task Manager" by pressing <Ctrl><Alt><Del>, select "Netscp6.exe", 
  and click "End Task". 

* When multiple diagnostics have been selected to run, the "Diagnostic 
  Progress" page may show 0 percent completed for all tests. However, 
  the diagnostics are running. Wait for the diagnostics to complete to 
  view the results.

* If the "Diagnostic Progress" page  shows 100 percent complete, 
  but the "View Results" button does not appear in the upper- 
  left corner and the diagnostics do not stop, try logging into
  Server Administrator again. You might see the following message 
  after you log in: "Another user is currently running the 
  diagnostics denoted by the progress bar below. When these 
  diagnostics complete, click "Run Tests" to begin the tests 
  you have selected". If you see this message, you must restart 
  the Server Administrator service and run the diagnostics again.

* The "Diagnostic Service" tab is not available in Server Administrator
  and is not listed on the "Health" page at startup. The Diagnostic 
  Service waits for the Server Administrator service to start completely
  before enumerating (scanning system for available devices to
  diagnose). If you press <F5> to refresh, the "Diagnostic Service" tab 
  shows up when enumeration is complete. This process can take several 
  minutes on some systems.

* When you select "Run Tests" on the "Diagnostic Selection" page or
  the "Diagnostic Scheduler" page, only some of the selected tests
  display in the progress page. This event occurs if you click the
  button too quickly. This event occurs because the data you selected
  is being posted to the server at the same time that the page is
  being updated; sometimes, the interface does not update all of the
  user changes.

* If the managed system has a statically assigned IP address and 
  no gateway is assigned to the system, then the network diagnostic
  communications test returns the message "The network device
  must be configured to use TCP/IP and the IP address for the 
  network card must be obtained through a DHCP server or you must 
  assign a static IP address. If the IP address is assigned 
  statically, a gateway must be present. Configure the network 
  accordingly and run this test again."

  This configuration is currently not supported.

* If you log in and select tests to run while tests are already
  running, you receive the message "Another user is currently
  running the diagnostics denoted by the progress bar below. When
  these diagnostics complete, click "Run Tests" to begin the tests
  you have selected". If you leave the "Progress" page and return
  to the page by clicking the "View" tab, the Diagnostic Service 
  runs the newly selected tests automatically after the scheduled 
  tests have completed, even though you have not yet selected "Run 
  Tests". The only way to stop the newly selected tests is to select 
  "Abort" after they have started to run.  

* Tests scheduled through the test scheduler or executed through the
  command line interface (CLI) cannot be cancelled

* Canceling a diagnostic test while it is being conducted might not 
  succeed immediately if the diagnostic is performing critical operations. 
  The test is cancelled only after critical operations are complete. 
  Diagnostics that may exhibit this behavior are the RAID Controller 
  and Memory diagnostic tests.

* If your hard drive becomes full (no space left) and you run
  diagnostics on the managed system, Server Administrator does not
  show progress for the running diagnostics; instead, you see a blank
  page. You cannot cancel the tests because the blank page is shown
  instead of the Progress page with the "Abort" button. To correct
  this issue, you must free up some space on your hard drive, reboot
  the server, and run the diagnostics again.

* If you open multiple command prompt windows and run "omdiag" CLI
  commands from several different windows, the "omdiag" command
  might complete but display no output or results in the command
  prompt window. If this occurs, log into the Web-based GUI,
  select the "Diagnostics" tab, and then select the "View Progress"
  link on the "Diagnostic Warning" screen. 

* If you run the video memory diagnostic and you press a key while the 
  diagnostic is running, the test stops but the result displayed is 
  "Failed". Clicking the "Details" button on the Server Administrator 
  home page displays a blank message box.

* The memory diagnostic allocates only 2 GB of memory to perform
  the Memory Pattern Test on systems running Windows NT, Windows 
  2000, and Red Hat Linux. ECC events are still detected on all 
  memory modules.

* On the scheduler page, entering a date later than the year 2039 in 
  the calendar is not  supported.

* If the Network Communication Test returns the failed result "Invalid 
  Device Reference: Cannot determine the configuration of the device. 
  Verify the device driver is installed properly and the device is enabled 
  in the Operating System. The test cannot continue", check the "Network 
  Properties" tab. If the "IP address" value is "Not obtained" and an IP 
  address is assigned when running ifconfig in Windows or ifconfig in 
  Linux, then the driver is not the latest available. You must install 
  the latest driver for the NIC from the "Server Assistant" CD before 
  you can run diagnostics on this NIC.

* The Diagnostics Service does not support network teaming. If you set 
  up your NICs as a team, the communications test fails when run on these 
  NICs and the following message is displayed:

  "The network device is set up as part of a network team. You cannot run 
  the test on this network adapter."

* The RAID controller diagnostic tests integrated RAID controllers. 
  The SCSI controller diagnostic test is not listed when the integrated 
  controller is configured in the BIOS in RAID mode or in SCSI/RAID 
  mode. The RAID controller diagnostic test is used in these
  configurations. This applies to the PERC 2/Si, PERC 3/Di, and 
  PERC 3/Si controllers.

----------------------------------------------------------------------
ISSUES FOR WINDOWS OPERATING SYSTEMS
----------------------------------------------------------------------

* If the Yosemite Tapeware application is installed on your system, 
  the Diagnostic Service cannot discover and run diagnostics 
  on IDE tape drives. To correct this problem, perform the following 
  steps:

  1. Locate the TapeWare configuration file. The default location is
     "C:\Program Files\TapeWare\TapeWare.ini". 

  2. Find the section in the file called "Configuration".

  3. Add the following line to the "Configuration" section.
     
     releaseWhenUnused=Yes

  4. Save the "TapeWare.ini" file, and reboot the system.


* The hard-drive diagnostics are designed to run as a low-priority 
  background task to limit the effect of its activity on other disk I/O 
  activity. Because of this, it is recommended that you limit drive 
  activity while running the hard-drive diagnostics. The diagnostics may 
  run slowly or even halt while other drive I/O activity is running 
  simultaneously. The diagnostics resumes when the drive I/O activity 
  has decreased.

  The hard drive may also fail and display the following message: 
  "Device failed a send diagnostic Command: Check SCSI cable connections 
  and termination and run this test again. If this error still occurs, 
  it may indicate a hardware problem." To avoid this message, run the 
  diagnostic again when the system is not running heavy disk I/O activity. 

* When logged into the Server Administrator home page using Microsoft 
  Internet Explorer on a system running a supported Windows operating 
  system, the browser might shut down unexpectedly during lengthy diagnostics 
  tests. If this happens, press <Ctrl><Alt><Delete>, click "Task Manager", 
  select the browser item, and click "End Task". Log back into Server 
  Administrator to continue the diagnostics tests.

* Array Manager 3.3 or later is required to diagnose RAID attached 
  hard drives with the Diagnostic Service. If Array Manager is not 
  installed, the Elite RAID attached hard drive tests are not visible 
  in the Diagnostic Service. 

* In some configurations, IDE hard drives may not be able to be tested.
  If the IDE hard drive is connected as a slave on the IDE bus and the
  master is a non-Self Monitoring and Reporting Technology (SMART) 
  device (such as a CD drive), both the standard and extended tests 
  fail and display the following message: "The test could not be executed 
  because the master device on the same channel as this device is not 
  SMART-enabled. See the readme for instructions on applying fix for 
  this issue." This issue is corrected with Service Pack 3 for 
  Windows 2000. See the Microsoft Knowledge Base Article ID: Q304572 
  at "support.microsoft.com" to get a hotfix for this issue. The hotfix 
  is also located on the "Systems Management" CD in the 
  "support\Windows\Hotfix" directory. The hotfix is in two zip files, 
  one for Windows NT and one for Windows 2000. The files are named 
  "MSFT_q304572_NT_SP7.zip" and "MSFT_q304572_win2k.zip".

* The operating system's diskette format application and the Diagnostic 
  Service Floppy Drive test are permitted to run simultaneously under 
  Windows 2000. However, false diagnostic errors might occur.

* If any hard drive fails the SCSI_INQUIRY test, then it is
  likely that the hard drive is not connected properly. Check the
  cables to ensure that the hard drive is properly connected to the 
  controller.

* If you run the Adaptec RAID controller diagnostic test or the Hard 
  Disk diagnostic test on hard drives that are connected to an Adaptec 
  RAID controller with an application that reserves the controller, the 
  diagnostic reports a failure with the following message:
  
  "An application or service that manipulates RAID such as Array
  Manager, FAST, or PERC Console has the controller reserved and must
  be stopped in order to run this test. See the readme for further
  information."
  
  To stop the Array Manager service, go to the Control Panel, select
  "Services", right-click the "Disk Management Service", and select 
  stop. To stop FAST or the PERC Console, exit the application.

* For managed systems with hard drives attached to a Dell-supported 
  RAID controller, if the diagnostics CLI does not list the RAID hard-
  drive diagnostics ("raidhd" or  "ideraidhd") when the Server 
  Administrator Web server is stopped, start the Web server using the 
  "net start Secure Port Server" command; this action enables the 
  "raidhd" or "ideraidhd" diagnostics.

* When upgrading from Windows NT 4.0 to Windows 2000, you receive the
  following message when you install the Diagnostic Service:

  "Report System Compatibility: Setup checks your computer for
  compatibility with Windows 2000. The following items are not
  compatible with Windows 2000. If you continue, you may not be able
  to use these items, even after Setup is complete."

  Contrary to this message, if you continue with the upgrade, the
  Diagnostic Service operates properly when the upgrade is
  finished.

* Hard drives, RAID controllers, and memory devices are sometimes 
  incorrectly listed in the "Hardware Configuration Changed" window 
  as being removed and then added. If the time stamp entry for both 
  the removal and addition are identical and you have recently 
  upgraded the Diagnostic Service to version 2.2 or later, then the 
  Diagnostic Service is detecting that additional information about 
  these devices has been added to the hardware/software description.

----------------------------------------------------------------------
ISSUES FOR RED HAT LINUX OPERATING SYSTEMS
----------------------------------------------------------------------

* The SMART tests are not supported on RAID configured systems.

* Red Hat Linux operating systems may lock up when running the 
  CD/DVD/CDRW diagnostics on IDE drives. When running the diagnostic 
  through CLI you may see the following message "Serverworks OSB4 in 
  impossible state. Disable UDMA...". Direct Memory Access (DMA) must 
  be disabled to run the diagnostics successfully. Refer to the Red Hat 
  documentation for instructions on disabling DMA.

* Running the command "omdiag [system | chassis] x" (where x is a 
  diagnostics test) while the Server Administrator Web server is 
  running can cause the CLI JVM to stop and return a log file after 
  successful completion of the diagnostic. This issue is under 
  investigation and will be fixed in a future release.

  The diagnostic test completes without problems before the JVM stops; 
  when the JVM stops, it produces a log file. The Web server JVM is 
  unaffected by this event, so you can subsequently 
  run the "omdiag" CLI command without encountering problems.  

* The "omreport chassis" CLI command does not list the health status 
  of the Diagnostic Service.  Diagnostic Service health can be viewed 
  on the "Properties" page for the "Main System Chassis" object on the 
  Server Administrator home page.

* The Diagnostic Service uses the operating system to determine the 
  number of CPUs in the system. Only CPUs that are visible to the 
  operating system can be diagnosed. The number of CPUs listed by the 
  Diagnostic Service equals the number of CPUs listed in the 
  "/proc/cpuinfo" file.

* The Diagnostic Service lists twice the number of physical 
  microprocessors installed in a system if that system has Hyper-Threading 
  enabled. The Diagnostic Service utilizes the operating system to 
  diagnose the microprocessor. The "Processors Information Page" on the 
  Server Administrator home page lists actual the number of physical 
  microprocessors present on the system. If your system has Hyper-Threading 
  Technology enabled when you test all microprocessors, the Diagnostic 
  Service runs diagnostics on each microprocessor twice.

* Under certain combinations of conditions, you must restart the
  omawsd service by typing "omawsd restart" at the command prompt.

  The conditions are as follows:

    a) After running a diagnostic test, the result that displays is
       a red X, indicating failure for that test.
    b) When you click the details link the "Test Result:" field is 
       blank.
    c) The "Result Details:" field displays "The test operation completed
       successfully."

  If you see any combination of these conditions, restart the omawsd 
  service.

======================================================================
ISSUES FOR REMOTE ACCESS
======================================================================

NOTE: The Remote Access Service is supported on PowerEdge 1600SC, 
      1650, 2600, 2650, 4600, 6600, and 6650 systems only.

The following subsections list the currently known issues regarding
implementation and operation of your RAC and the Remote Access Service
in Server Administrator.

----------------------------------------------------------------------
Remote Access Dial-Up Settings
----------------------------------------------------------------------

If you change a DRAC III modem "Dial Mode" setting to "Tone" or 
"Pulse" using Server Administrator, IT Assistant displays the opposite 
setting.

----------------------------------------------------------------------
ISSUES FOR ALL OPERATING SYSTEMS
----------------------------------------------------------------------

* For the RAC to capture the last crash screen, you must enable
  the watchdog timer on the RAC managed system and set the watchdog 
  recovery action to "Reset", "Power Off", or "Power Cycle". Configure 
  the watchdog timer using Server Administrator or IT Assistant. For 
  more information, see the "Server Administrator User's Guide" or the 
  "IT Assistant User's Guide."

* The mouse movement on a local system may appear jerky and erratic
  during console redirection. This behavior is evident especially when
  using menus or opening windows.

* During normal operation of the RAC managed system under NetWare 5.1 
  and NetWare 6.0, the operating system periodically displays the 
  following messages:

  "LCP is down: **PPP did not receive a response from peer for several
   Echo-Requests sent**"

  "Call disconnection for protocol IP to destination RAC. The event
   occurred due to a link failure"

  These messages do not indicate errors. They are generated when the
  RAC PPP connection is temporarily unavailable (this may happen
  when the card is reconfigured or new users are added). The PPP
  connection is automatically re-established, and no user action is
  required. Therefore, the user should not attempt to manually
  re-establish the connection.

----------------------------------------------------------------------
ISSUES FOR WINDOWS OPERATING SYSTEMS
----------------------------------------------------------------------

* If you used the "Systems Management" CD version 3.1 or earlier to 
  install RAC management station software on any system running a Windows 
  operating system, you must remove any previous versions of the RAC 
  management station software before installing a later version of the 
  RAC management station software.
 
  To remove the RAC management station software on Windows, 
  perform the following steps:

  1. Insert the "Systems Management" CD into the CD drive. 
     
  2. When the installation application starts, click "Exit".

  3. Open a command shell window:

     a. Click the "Start" button, and then click "Run".

     b. In the "Run" dialog box, type the following command and 
        then press <Enter>:

        cmd

  4. Start the Install Shield uninstallation program to remove 
     software:

     a. In the command shell window, type the following line 
        (replacing x: with the actual drive letter of your CD 
        drive, such as d:):

        x:\rac13\mtpkg\setup.exe

     b. Select "Remove", and then click "Next".
 
     c. Click "OK".

     d. Click "Finish".

  5. Close the command shell window.


* In order to launch the RAC Web console from IT Assistant, you must 
  run one of the patches located on the "Systems Management" CD in 
  the "\support\Windows\RAC" directory. For systems running IT 
  Assistant on any Windows operating system except Windows NT, use the 
  "Win2KPatch.reg" file. For Windows NT, use the "WinNTPatch.reg" file. 
  To apply the patch, browse to the CD directory mentioned above and 
  double-click the filename. Click "YES" and "OK" on the next two 
  message boxes. The patch enables the Java Console in Internet Explorer.

* If you are using Dell OpenManage Remote Install 3.1 or earlier on 
  systems running Windows, you must remove any previous installation 
  of the RAC management station software before installing a newer version.

* Resizing the Windows desktop to resolution of 640 x 480 causes some
  loss of displayed information in the browser when viewing the Server 
  Administrator RAC home page in both Netscape Navigator and Internet 
  Explorer. Enlarge the browser window to view all the displayed 
  information.

* The Internet Explorer application embedded in the Windows Advanced
  Server Limited Edition operating system does not support Java
  applets; therefore, it is not possible to use the Advanced Server
  Limited Edition's Internet Explorer browser to connect to a RAC
  over a local area network (LAN) or the Internet.

* If you uninstall the RAC managed system software from a system 
  running a Windows NT operating system, remove the "RAC PPP Connection 
  Using RACPORT" modem connection that was added during setup. Otherwise, 
  the system displays an error message each time it reboots.

* CONNECTING TO THE INTERNET IF THE RAC PPP SERVICE IS RUNNING 
  
  After installing Internet Explorer 5.0 or later, you may notice that
  the automatic configuration and proxy setting information for each
  connection is separate from the same information used for the LAN
  connection. If you have both a dial-up and a LAN connection at the
  same time, Internet Explorer may block your access to the Internet. 

  This blocking occurs because each connection in Internet Explorer 
  5.0 uses its own automatic configuration and proxy settings. When 
  this occurs and a user tries to establish any kind of PPP 
  connection, Internet Explorer attempts to use the dial-up connection 
  settings to access the Internet.

  You can find additional information about this issue in article 
  Q236920, "Connections No Longer Use LAN Automatic Configuration
  and Proxy (Q236920)in the Microsoft Knowledge Base at 
  "support.microsoft.com".

  To correct this problem, you must update your browser to Internet 
  Explorer 5.5 (SP2). To run the update, you need to stop the RAC 
  service. The update is available at "windowsupdate.com". 

----------------------------------------------------------------------
ISSUES FOR LINUX OPERATING SYSTEMS
----------------------------------------------------------------------

When installing the Dell OpenManage systems management applications on
a system running the Linux 8.0 operating system and the GNOME File
Manager, you must use the "Run" button and not the "Run In Terminal"
button after choosing the "start.sh" script from the File Manager's
file list. Use the "Run In Terminal" button for applications that do
not open a window of their own ("start.sh" opens its own window). If
you choose "Run In Terminal," you must restart the "racvnc" service
after installing Dell OpenManage systems management applications by
typing the following command: "service racvnc restart".

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

ISSUES FOR SERVER ADMINISTRATOR VERSION 1.3 DOCUMENTATION
====================================================================

The following subsections provide corrections for the Server 
Administrator version 1.3 documentation set.

--------------------------------------------------------------------
ISSUES THAT AFFECT MORE THAN ONE DOCUMENT
--------------------------------------------------------------------

* In both the "User's Guide" and the Server Administrator Online Help,
  the left pane of the application as it displays in the browser is 
  the "System Tree". Primary objects falling under "System 
  Tree" include "Main System Chassis", "Software", and "Storage".
  In the top right corner of the Server Administrator GUI, the
  following buttons appear: "Preferences", "Support", "Help", "About",
  and "Log Out". Under the "Preferences" button, the GUI is not properly
  called the "System Tree". The "Preferences" interface consists of
  two primary objects: "General Settings" and "System Administrator".

* The Server Administrator Online Help and other documents may refer
  to directory locations generically using the back slash (\) to offset 
  different subdirectories. For systems running a Red Hat Linux operating 
  system, the correct convention for path names uses the forward
  slash (/). 

* To stop or start Server Administrator services in Windows 2000, go to 
  Start--> Settings--> Control Panel--> Administrative Tools, and select 
  "Services". In the list of services, Server Administrator is listed as 
  "Secure Port Server".  Double-click "Secure Port Server" and click the 
  service status button that you want (for example, "Start" or "Stop").

 * In both the "User's Guide" and the "Compatibility Guide," the 
   following statement is made about the availability of the SNMP 
   systems management protocol on Red Hat Linux operating systems:
   "You must install the ucd-snmp package provided with the operating 
   system." This package name is valid for versions of Red Hat Linux 
   earlier than version 8.0. The name of the SNMP package that you must 
   install for Red Hat Linux version 8.0 is "net-snmp".

-------------------------------------------------------------------
ISSUES FOR SERVER ADMINISTRATOR ONLINE HELP
-------------------------------------------------------------------

* The Online Help states that "Fan control" is listed under External 
  Chassis--> Fans--> Power Supplies --> Temperatures. However, there 
  is no fan control for an external chassis. There is fan control for 
  the Main System Chassis. 

* Under System--> Main System Chassis--> Remote Access Controller, 
  click the "Help" button. Under User Privileges, the Help 
  states that only an Administrator (A) can view the Remote 
  Access information. This is incorrect. A User (U), Power User (P),
  and Administrator (A) can all view Remote Access Information. 
  However, only an Administrator (A) can manage or modify RAC 
  settings.

* Under System--> Main System Chassis--> Remote Access Controller, 
  click the "Security" tab. Select the "Certificate Management" subtab. 

  The purpose of this page is to allow users who want to replace the 
  Dell-installed certificate on their RAC with their own company's 
  unique certificate signed by a certificate authority (CA). This process 
  begins by generating a Certificate Signing Request (CSR) and sending 
  it to a CA. The CA examines your CSR, and if it passes strict criteria, 
  the CA returns a signed certificate based on your CSR. You can upload 
  the signed certificate to your RAC, overwriting the Dell-installed 
  certificate. 

  The Online Help does not contain sufficient information about the CSR
  fields to allow you to generate a successful CSR. If you do not fill 
  in the fields correctly, your CSR is rejected by the CA. This section 
  provides more information on the fields.

  To generate a certificate request, You must enter a value for the 
  following required fields:

  - Common Name
  - Organizational Unit
  - Organization Name
  - Country Code
  - Filename

  Common Name (CN) is the name being certified (usually the Web 
  server's domain name; for example, www.xyzcompany.com). 
  Spaces are allowed.

  Organization Unit (OU) is the name associated with an organizational 
  unit, such as a department (for example, Enterprise Server Group). 

  Organization Name (O) is the name associated with this organization 
  (for example, XYZ Corporation). Spaces are allowed.

  Country Code (C) is the name of the country where the entity applying 
  for certification is located. Use the drop-down menu to select the 
  country.

  Filename is the fully qualified directory and filename of the CSR file 
  you are generating. For example, "C:\remote\csr.txt".

  The following fields are optional when generating a certificate request.
  Your company may want to include values for these fields to ensure 
  uniqueness for your CSR.

  - Locality
  - State
  - Email address
  
  Locality (L) is the city or other location of the entity being 
  certified (for example, Round_Rock). Spaces are not allowed, but 
  you can separate words using an underscore or some other character.

  State (ST) is the state or province where the entity applying for 
  certifications located (for example, Texas). Spaces are allowed.

  Email address (E) is your company's email address. You are free
  to enter any email address you want to have associated with the 
  CSR.
  
------------------------------------------------------------------
ISSUES FOR THE SERVER ADMINISTRATOR USER'S GUIDE
------------------------------------------------------------------

* In "Installing Server Administrator", there is a subsection 
  titled "Creating and Distributing the Express Unattended 
  Installation Package". This section fails to mention several 
  unattended installation options. You can create a package 
  and use a .sil file to customize that package. You can also 
  create a package and perform an express installation from the 
  package. 
   
* In "Installing Server Administrator", Table 8, "Command Line 
  Settings", shows the optional command line settings and 
  subcommands available for unattended installation. The 
  "-logfile=log.file" command does not work on systems running 
  Red Hat Linux. The correct Linux command is 
  "start.sh -log <filename>.log".

* In "Installing Server Administrator", it states that "Two log 
  files are generated in a temp folder during an unattended 
  installation, ominstal.log and omstatus.log. The temp folder 
  is typically located at c:\temp." For systems running a Red 
  Hat Linux operating system, all temporary files are located 
  in a /tmp directory.

------------------------------------------------------------------
ISSUES FOR THE SERVER ADMINISTRATOR COMMAND LINE INTERFACE 
USER'S GUIDE
------------------------------------------------------------------

* Chapter 1 of the "Server Administator Compatibility Guide" 
  incorrectly explains what the "omconfig" command does. The purpose 
  of the "omconfig" command is to change or configure your systems 
  management information or management settings.

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

Information in this document is subject to change without notice.
(C) 2002 Dell Computer Corporation. All rights reserved.

Reproduction in any manner whatsoever without the written
permission of Dell Computer Corporation is strictly forbidden.

Trademarks used in this text: "Dell", "PowerEdge", "PowerVault", 
and "Dell OpenManage" 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, Inc.; "Intel" is a registered 
trademark of Intel Corporation. 

Server Administrator uses the OverLIB JavaScript library. This 
library can be obtained from www.bosrup.com.

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.

January 2003
