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

DELL(TM) REMOTE ACCESS CONTROLLERS (RACs)

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

This document contains updated information about the Dell(TM) RACs (Dell
Remote Access Card III [DRAC III], DRAC III/XT, Embedded Remote 
Access [ERA], and Embedded Remote Access Option [ERA/O]). 

For more information about Dell RACs, including installation and
configuration information, see the "Dell Remote Access Controller 
Installation and Setup Guide" and the "Dell OpenManage Server Administrator 
User's Guide." These documents are located on your documentation CD.

======================================================================
SUPPORTED SYSTEMS
======================================================================

DRAC III is supported on the following Dell PowerEdge(TM) systems:

* PowerEdge 1650
* PowerEdge 4600
* PowerEdge 6600
* PowerEdge 6650
* PowerEdge 7150

DRAC III/XT is supported on PowerEdge 1600SC and PowerEdge 650 systems.

ERA is supported on PowerEdge 2650 systems.

ERA/O is supported on PowerEdge 1650, PowerEdge 1750, 
and PowerEdge 2600 systems.


======================================================================
SUPPORTED OPERATING SYSTEMS
======================================================================

The RACs (DRAC III, DRAC III/XT, ERA, and ERA/O) are supported by the 
following operating systems:

* Microsoft(R) Windows NT(R) 4.0 Server family (Service Pack 6 or
  later)

  The Windows NT 4.0 Server family includes Windows NT 4.0 Server,
  Windows NT 4.0 Server Enterprise, and Windows NT 4.0 Terminal Server.

* Microsoft Windows(R) 2000 Server family

  The Windows 2000 Server family includes Windows 2000 Server,
  Windows 2000 Advanced Server, and for PowerEdge 7150 systems,
  Windows Advanced Server Limited Edition.

* Red Hat Linux, version 7.3 (with the 2.4.18-4errata kernel)

* Red Hat Linux, version 8.0

* Red Hat Linux Advanced Server, version 2.1

* Novell(R) NetWare(R), version 5.1 (Service Pack 3 or later) and 
  version 6.0 (Service Pack 1 or later)

NOTE:  MS-DOS(R) version 6.22 supports the RAC Remote Floppy Boot
       feature (32-bit systems only).

======================================================================
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, 8.0 and Advanced Server, 
  version 2.1

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

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.

======================================================================
CORRECTED ISSUES IN THIS RELEASE
======================================================================

* Corrected the issue with resetting the RAC after deleting one or 
  more users from the RAC users' database.

======================================================================
NEW FEATURES IN THIS RELEASE
======================================================================

* None

######################################################################
KNOWN ISSUES FOR RACs
######################################################################

The following subsections list the known issues regarding the
implementation and operation of the remote access service and RACs.


* When performing a certificate upload, the certificate must reside 
  on the RAC's host server. You must enter the absolute path to the 
  certificate on the server.

* After uploading the certificate you must reset the RAC. Use one of 
  the following three methods to reset the RAC:

  - Use the "omconfig rac reset" command.

  OR

  - Use the "racadm racreset" command.

  OR

  - Use the RAC Web-based interface.

    Go to the "Debug" tab, click "Status Check", and then click "Reset RAC".

* The version 2.0 firmware does not support passwords with special characters 
  (nonalphanumeric) only for RAC user IDs logging in using the Web-based 
  interface (with LocalRAC Authentication). If you created 
  RAC user IDs using previous versions of the firmware or if you created 
  user IDs using Server Administrator that is running version 2.0 firmware 
  on the managed system, you cannot log in to the RAC.

  Use one of the following four methods to correct this issue:

  - Change your passwords prior to updating the firmware.

  OR 

  - Use the CLI command to change the password.   

    Enter: omconfig rac users username=xx userpassword=yy

    Where: "xx" is the original userid, and "yy" is the new password.

  OR

  - Change the password through Server Administrator using the "User" tab. Ensure 
    that the check box to change the password is checked. Enter a new 
    password, and then enter it again to validate the change.

  OR

  - Use the racadm utility to change the password.

    Enter: 
   
    racadm config -g cfgUserAdmin -o cfgUserAdminPassword -i 
     <usr_index> <new_pwd>

    where:
   
    <usr_index> is the index of the user database entry to be modified and
    <new_pwd> is the new password.

  This issue will be corrected in a later release of the firmware.

* Informational SNMP traps are not displayed when sensor readings return to
  normal values;  however, you can use the RAC Web-based interface to view this
  information in the System Event Log.

* When using Internet Explorer to access the RAC on systems running Windows 2000 
  and Windows NT, you must use the Microsoft Java Virtual Machine (JVM). 

  NOTE: RACs do not support Internet Explorer with Sun's JVM. You must disable 
  Sun's JVM to access the RAC using Microsoft's JVM.

  To disable Sun's JVM, launch Internet Explorer, perform the following steps:

  1. Go to "Tools"--> "Advanced Options".

  2. Click the "Advanced" tab.
  
  3. Scroll down to the list to "Java (Sun)".

  4. Deselect the box next to "Java 2...".

  5. Click "Apply" and then click "OK".

  6. Close the browser and then relaunch the browser.

* Applications that use InstallShield 3.x to install software may take longer to
  install software if RAC Services are running. To reduce the software installation
  time, stop RAC Services before performing the installation. You must restart
  RAC Services after the installation is complete.        
   
* Depending on your network and proxy configurations, and if you are using 
  Netscape Navigator or a Mozilla browser, you may need to enter the exact IP address 
  of the RAC controller you are trying to access in the "No Proxy for" field of your browser. 

  Perform the following steps:

  1. Open your Netscape Navigator or Mozilla browser.

  2. Click "Edit."

  3. Click "Preferences ...".

  4. Click "Advanced" in the left sidebar.

  5. Click "Proxies" in the left sidebar.

  6. Enter the RAC IP address in the "No Proxy for:" field.

  7. Click "OK" and then close the browser.

* Continuous Video is not supported in this release, but will be supported
  in a later release.

* After two invalid log-in attempts, you must wait at least one minute
  before attempting to log-in again.

* Console Redirection supports up to four sessions. It is strongly recommended
  that you do not open all four sessions simultaneously because doing so can greatly
  degrade system and memory performance.

* The RAC Help file incorrectly states that the "Last Crash Screen" file is located
  under the "Remote Access" tab. The "Last Crash Screen" file is actually located
  under the "Logs" tab.

* All RAC console redirection sessions lose their connection to the 
  RAC if a user performs an update of the firmware. To reconnect,
  log out, allow the RAC update to finish, and then log in again.

* Entering an invalid RAC user name may prevent the 
  Server Administrator command log from being displayed.

  To resolve this condition, use the following command:

  omconfig system cmdlog action=clear

* Attempting to remove a user whose name is invalid (that is, the name
  either uses invalid characters or does not exist) returns the
  following error message:
 
  "Error! Hardware subsystem reports command failed."

  This error message is a generic Server Administrator message that
  indicates an error.

* Adding a RAC user from the Server Administrator interface overwrites 
  an existing user if the new user has same user name or index as
  the existing user. 

* RAC console redirection text mode does not support the <Ctrl><Break>
  key combination. Instead, use <Ctrl><C>.

* The hardware log, accessible from the RAC Web-based interface,
  displays text-only log entries (date, time, and description). The log
  does not display color-coded icons to indicate severity levels. If
  you prefer to view the log with color-coded icons, use Server
  Administrator to access it.

* The reading precision for server sensors is 0.25 percent.

* When using the RAC Remote Floppy Boot feature to start DOS
  network interfaces, add the following commands to the "autoexec.bat"
  file: 

   NET INITIALIZE /dynamic
   NET START basic

* 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 "Dell OpenManage Server
  Administrator User's Guide" or the "Dell OpenManage IT Assistant
  User's Guide."

  The last crash screen is not available when the watchdog recovery action
  is set to "Shutdown" or "Power Cycle" if the managed system is 
  powered off.

* The last crash screen time stamp might not be the actual time but normalized
  to GMT.

* Due to functional details that are specific to Windows Dynamic DNS
  servers, the RAC internal PPP IP address is broadcast to the Dynamic 
  DNS service on servers running Windows 2000. The Dynamic DNS service 
  stores that particular IP address in its DNS lookup table and associates 
  it with the name of the system that hosts the RAC. This action causes 
  problems with Active Directory under Windows. The default value for a 
  RAC's internal PPP IP address is 192.168.234.235, but the address can 
  be changed by the user. This issue is a known problem, and there is an 
  article and a hot fix available from Microsoft. The article is Q292822. 
  Downloading the fix and implementing the steps in the article solves 
  the problem. 

* When using the RAC out-of-band UI with Netscape 6.2.x or Mozilla 1.x, you must
  have Java 2 Runtime Environment (J2RE) 1.4.0, 1.4.0_01, 1.4.0_02, or
  1.4.0_03 installed. You can find information for installing J2RE for
  Netscape on Sun's website at "java.sun.com". Installation instructions for 
  installing J2RE for Mozilla 1.x are in the next readme entry.
 
* You must install JRE to use the Mozilla Web browser. To install JRE,
  perform the following steps:

  1. Launch the installation script by using the following commands from 
     the directory in which the script is located: 

     chmod a+x j2re-1_4_<version number>-linux-i586-rpm.bin
     ./j2re-1_4_<version number>-linux-i586-rpm.bin

     The script displays a binary license agreement, which you are prompted 
     to accept before continuing the installation. After you have accepted 
     the license agreement, the installation script creates the file 
     "j2re-1_4_<version number>-linux-i586.rpm" in the current directory. 
	
  2. To become the root user, run the "su" command and enter the power-user 
     password. 

  3. Run the following rpm command to install the packages. This command installs 
     the packages comprising the Java 2 Runtime Environment (J2RE): 
     
     rpm -iv j2re-1_4<version number>-linux-i586.rpm

     Only one Java plug-in can be registered at a time. If you have never 
     registered a Java plug-in, go to the next step; otherwise, go to step 5.
     
     Most Mozilla installations use symbolic links to where the Java plug-in is 
     located. The name of the symbolic link is "libjavaplugin_oji.so" and it can 
     be found in the "/plugins" subdirectory of Mozilla.
  
     For example:

	cd /usr/lib/mozilla<version number>/plugins
	rm libjavaplugin_oji.so
		
  4. Register the Java plug-in. Locate the "libjavaplugin_oji.so" file in the
     "j2re1.4<version number>" directory. Usually it is located in the  
     /i386/ns600 or /i386/ns610 subdirectory. You need to use the "create a 
     symbolic link" feature in Mozilla that points to the "libjavaplugin_oji.so" 
     file in the "/i386/ns610" subdirectory.
	
     For example:

	cd <Mozilla>/plugins
	ln -s j2re1.4<version number>/plugin/i386/ns610/libjavaplugin_oji.so libjavaplugin_oji.so

     NOTE: Create the link using the "/plugins" subdirectory of Mozilla. You cannot 
     create the link from <JRE> directory. 
	
  5. Start Mozilla and go to "Tools"-> "Web Development"-> "Java Console". 

     The version of JRE is displayed at the top of the Java Console window. If the 
     version that is shown is not the same as the one you downloaded, then registering 
     did not work. The same is true if the Java Console menu option is grayed out.

* The RAC may be inaccessible to remote users when the controller is 
  bombarded with 65 K "ping" packets every second or less. The processor is busy
  processing the "ping" and cannot accept other connections. After the pings stop, 
  the controller becomes accessible again. Pings received with a longer duration
  between the packets are not an issue.

* If you plan to use the racadm to remotely update the RAC firmware, you must 
  use the TFTP option (-g). The FTP option (-p) is not supported remotely. Dell 
  recommends using the following syntax: 

  racadm -r <RAC_IP> -u <USER> -p <PASSWD> fwupdate -g -u -a <TFTP_IP> -d <TFTP_DIR_PATH>

* MS-DOS version 6.22 is required for the DOS racadm CLI feature. To limit DOS 
  racadm CLI output to a single screen, use the MS-DOS "more.com" utility. Type 
  the following command at the prompt:

  a: racadm help | more

* Using the RAC default certificate for SSL generates a Host Mismatch warning in 
  Netscape. A CA-generated SSL certificate must be downloaded to the RAC for proper 
  security. 

* After uploading a new SSL CA certificate to the RAC, the new certificate cannot 
  be viewed from the Server Administrator GUI or racadm until you reset the RAC.

* Assigning a predefined IP address to the RAC using a DHCP server:
  Most DHCP servers require a client identifier token to be stored in the 
  server's reservations table. The client (RAC, for example) has to provide that 
  token during the DHCP negotiation phase. In the case of RACs, the RAC supplies 
  the client identifier option as follows: a one-byte interface number (0, 1, or 
  2) followed by a six-byte MAC address. The interface number for the NIC may be 
  0, 1, or 2, depending on whether DHCP for PPP is currently enabled, PPP DHCP 
  has been enabled in the past, or PPP DHCP has never been enabled. If PPP DHCP 
  has never been enabled and is not currently enabled, the NIC interface number
  should be 0. 

* Using the "racadm setrac" command remotely from the management station
  sets information such as time and system name for the 
  management station, not the managed system.

* If you are using a version of HyperTerminal earlier than version 6.3 as 
  the RAC VT-100 terminal, you cannot resize the bottom of your screen 
  to view up to 26 lines of text. For HyperTerminal 6.3 or later, change 
  the screen size to view 26 lines from the "Properties" box.

* If you are using Minicom as the RAC VT-100 terminal, resize the window 
  to 80 x 26. Resizing allows for 26 lines of text and one line of Minicom
  status. The Minicom command key is <Ctrl><A>. If you need to use 
  <Ctrl><A> to enter the SCSI BIOS setup screen, redefine the Minicom control 
  key from the screen and Keyboard settings menu.

* During the first 40 seconds after a RAC reset, the RAC
  is synchronizing with the system ESM and managed system 
  service. If an alert is generated during this time, some of 
  the values may be reported as "unknown". The time field will contain 
  the number of seconds since RAC startup.  After synchronization 
  has completed, all values will report correctly.

* Clicking the browser's "Refresh" button logs out the RAC. 
  To refresh the GUI screens, use the "Refresh" buttons on the page.

* When generating a certificate request, the following fields must adhere to the
  following input:

  - Common Name (CN) - No spaces allowed.
  
  - Organizational Unit (OU) - Use only alphanumeric characters, hyphens, under-
    scores, and spaces.

  - Locality - Use only alphanumeric characters and spaces.

  - State (ST) - Use only alphanumeric characters and spaces.

* After performing a software upgrade, clear the Web browser's cache to ensure 
  that all new GUI pages are loaded.

  For Internet Explorer:

  1. From the pull-down menu, select "Tools"--> "Internet Options".

  2. In the "Internet Options" window under "Temporary Internet Files", click
     "Delete Files...".

  3. Click the "Delete all offline content" box.

  4. Click "OK" twice.

  5. Close and restart the browser.

  For Netscape Navigator:

  1. From the pull-down menu, select "Edit"--> "Preferences".

  2. In the "Preferences" window, select "Advance"--> "Cache".

  3. Click "Clear Disk Cache".

  4. Click "Clear Memory Cache".

  5. Click "OK".

  6. Close and restart the browser.

====================
Server Sensor Issues
====================

*  When trying to view the Hardware Log with the system turned Off, 
   the system might display a RAC error message, such as

   "BMCxx,..sensor #..." 

   if you are trying to view data about the crash immediately after the ESM Log 
   displayed. It is recommended that you wait at least two minutes after initially rebooting 
   your system to allow the server sensors to be gathered so that the ESM log can be
   formatted.

   - On the PowerEdge 1750 system only, the system might display a RAC error
     message, such as:

     "BMCxx,watchdogsensor#"

     even when the system is powered on. This problem will be corrected in a later release
     of the firmware. 

*  When viewing server sensors, a difference might occur between the number of sensors 
   displayed when the system is turned on and the number of sensors displayed when the 
   system is turned off. Also, if the system is turned off, then the data that is last 
   displayed are the values just before you shut off the system. The system does not 
   reset itself; therefore, the data is not lost. When the system is restarted, the data
   will be altered because the ESM firmware is obtaining new sensors.

* Attempting to remove a nonexistent dial-in user returns
  "successful."
  
  For example:  omconfig- rac-rmdialinuser=<invalid index>

* The RAC remote access interface supports 16 concurrent users. The
  17th connection attempt to the RAC does not appear in the "Session
  Information" page.
  
######################################################################
KNOWN RAC-SPECIFIC ISSUES
######################################################################

The following sections provide specific issues, if any, for DRAC III,
DRAC III/XT, ERA, and ERA/O controllers.

======================================================================
DRAC III-SPECIFIC ISSUES
======================================================================

* It is recommended that you configure the DRAC III VT-100 interface 
  screen using HyperTerminal to a window size of 80 x 24 when displaying 
  text console redirection.

======================================================================
DRAC III/XT—SPECIFIC ISSUES
======================================================================

The DRAC III/XT Web-based interface does not display "Post Log" or 
"Boot Path Analysis" if the DRAC III/XT is reset.

======================================================================
ERA—SPECIFIC ISSUES
======================================================================

* The ERA Web-based remote access interface does not display
  "POST log" or "Boot Path Analysis" if the ERA is reset. 

* When starting a system with an ERA controller installed, the ERA POST
  log may not capture POST codes and errors. Reboot your system to correct
  this condition.

======================================================================
ERA/O-SPECIFIC ISSUES
======================================================================

None

######################################################################
KNOWN OPERATING SYSTEM ISSUES
######################################################################

The following sections provide additional information about known issues 
with operating systems.

======================================================================
Windows Operating System Issues
======================================================================

* To enable the "Disable Local Console" in the console redirection session
  using Windows 2000, you must use the following racadm command:

  racadm allowEnDisRem TRUE

  NOTE:  The "Disable Local Console" button is only supported on Windows 2000.

* To launch the RAC Web console from IT Assistant, you must run one of 
  the patches located on the "Dell OpenManage Systems Management" CD 
  in the "\support\Windows\RAC" directory. If you are 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 previously mentioned and double-click the 
  filename. Click "Yes" and "OK" in the next two message boxes. The patch 
  enables the Java Console in Internet Explorer.

* On systems running Windows, the RAC installation process requires a
  virtual modem connection named RACPORT to communicate between the
  operating system and the RAC controller.  When any modem is added to
  the system, the operating system automatically creates a virtual fax 
  device icon in the printers folder. The fax icon is not used by the 
  RAC and can be deleted or ignored.

* To take full advantage of the RAC interface on systems running
  Windows NT or Windows 2000 it is highly recommended that you use the
  "Dell OpenManage Server Assistant" CD that came with your system to
  install the RAC drivers. If you do not use the CD, you may need to
  manually install the RAC drivers. 

* 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.

* Resizing the Windows desktop to a resolution of 640 x 480 causes
  some information to not be visible in the browser when using the
  RAC Web-based interface. This issue occurs in both Netscape 
  Navigator and Internet Explorer. To view a screen in its entirety 
  when using a resolution of 640 x 480, you must enlarge the browser 
  window.

* If you uninstall the RAC managed system software from a system 
  running the Microsoft 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.

======================================================================
NETWARE OPERATING SYSTEM ISSUES
======================================================================

* When a remote "Reset", "Power Off", or "Power Cycle" is issued through
  the RAC on NetWare, some NetWare applications may require user 
  interaction to close application windows. If this is necessary, you 
  should use the RAC console redirection to manually close the 
  application windows to allow NetWare to shutdown.

* During normal operation of the DRAC III 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 RAC3. 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 (the connection
  may be unavailable when the card is reconfigured or new users are
  added). The PPP connection is automatically reestablished, and no
  user action is required. Therefore, the user should not attempt to
  manually re-establish the connection.

* To take full advantage of the RAC interface on servers running
  NetWare 6.0 or later, it is highly recommended that you install the
  latest service pack available from Novell.

=======================================
RED HAT LINUX OPERATING SYSTEM ISSUES
=======================================

* When using Console Redirection on a managed system running Red Hat Linux,
  the focus (cursor moved back over an object) follows the cursor. Occasionally, 
  the text windows in Console Redirection loses focus. Before attempting to
  type in a text window in a Console Redirection window, click the mouse in the text 
  window's space bar or top menu bar to ensure that your target text window 
  has the focus on the correct window or application that you are attempting to use. 

* The RACADM utility can be installed on a management station running
  Red Hat Linux so that the remote RACADM functions can be used. 
  To install the RACADM utility, insert the "Systems Management" CD 
  in the management station's CD drive and issues the following commands 
  from a command prompt:

  - mount /mnt/cdrom
  - cd /mnt/cdrom/rac20/linux
  - rpm -ivh racadm-2.0-1.i386.rpm

 For help with the RACADM command, issue the "man racadm" or "racadm help" 
 command after issuing the previous commands. For more information about 
 RACADM features, see the "Remote Access Controller RACADM User's 
 Guide".

 You can uninstall the RACADM utility by issuing the following command 
 from a command prompt:

 - rpm -e racadm

######################################################################
ADDITIONAL INFORMATION
######################################################################

The following sections provide additional information about RACs.

======================================================================
USING THE "RACRAS.INI" FILE TO CONFIGURE DIAL-UP NETWORKING USED BY
IT ASSISTANT
======================================================================

The "racras.ini" file is used by DRAC III remote access DLL functions
and the proxy server to provide user-specified configuration.
Generally, the contents of the "racras.ini" file do not have to be
modified.

NOTE: You must reboot the system for modifications to the "racras.ini"
      file to take effect.

The following entries are included in the "racras.ini" file:

* "Enable Proxy Routing"

  This entry allows a user to disable proxy routing. If disabled, only
  users with browsers running on the IT Assistant services host system
  are able to connect to the DRAC III. The connections do not require
  the DRAC III remote access service proxy server, so the proxy server
  is disabled. The proxy server should be enabled when users' browsers
  are running on managed systems other than the IT Assistant services
  host system.

  True  = Enabled  =  Browser running on a system other than the IT 
                      Assistant services host.

  False = Disabled =  Browser running on the IT Assistant services
                      host.

* "DRAC III Web Server Port (specified port number)"

  This entry is the port number that the DRAC III Web server monitors
  for new Web connections. When the proxy server connects to a DRAC
  III, it uses this port.

  NOTE: The default port is 80. Change the default only if it is
        modified on the DRAC III.

* "Max Number of Routes to Proxy"

  This variable identifies the maximum number of users that can be
  routed by the remote access service proxy server at one time.


* "Base Port Number for UI-side Ports"

  This entry is the starting port number that the remote access
  service proxy server uses for incoming port connections from the
  DRAC III Web-based interface. Two ports are used per route.
  Therefore, the remote access service proxy may use the ports
  ranging from this base number up to the "Max Number of Routes to
  Proxy". 
     
* "Max Number of Routes to Proxy" + Base Port Number
  
  NOTE: The default port is 0. This default means that available ports 
        are identified by the operating system. Change the default only 
        if specific ports are already in use.

* "Proxy IP Address"

  If you need to use a different IP address on the incoming IT
  Assistant services host system than the one currently used by
  the standard services host, then enter that address. 
 
  NOTE: Set this entry to 0 if it is not being used. Use the entry
        only if the managed system has multiple IP addresses.

* The following six commands from the current "Racadm User’s Guide" are applicable 
  only to PowerEdge 1655MC systems: "getraclog", "clrraclog", "getractime", 
  "clrractime", "getsel", and "clrsel". 

* It is no longer recommended to use the "-f" option when using the
  racadm "fwupdate" command. Use the -d option instead. If using the
  -f option, specify the proper filename for the installed RAC such 
  as "firmimg.bin" for DRAC III, "firmimg.bm1" for ERA and DRAC III/XT, 
  and "firmimg.rm1" for ERA/O.

===============================================================
CONNECTING TO THE INTERNET WHEN 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 running
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 
situation 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 the Microsoft 
Knowledge Base located at "support.microsoft.com", article Q236920 
entitled, "Connections No Longer Use LAN Automatic Configuration
and Proxy (Q236920)."

To correct this issue, perform the following steps:

1. If you are using Internet Explorer 5.0, 5.01 or 5.5 (SP1), update your 
   browser to Internet Explorer 5.5 (SP2). To run the update, 
   stop RAC Services. 

   The update is available at "windowsupdate.com". 

2. For Windows NT 4.0 Terminal Server or Windows 2000 Terminal Services, 
   perform the following steps to install "lanpatch.reg":
  
   a. Right-click the "Start" button.

   b. Click "Open All Users".

   c. In the "Start Menu" dialogue box, double-click "Programs".

   d. Double-click "Start-up".

   e. Right-click "New"--> "Shortcut".

   f. Browse to the "lanPatch.reg" file.

   NOTE:  The default location for the file is:  
          "C:\Program Files\Dell\OpenManage\RAC\MN\Lanpatch.reg".

   g. Click "Next".
  
   h. Click "Properties" created Shortcut.

   i. Add the following to the beginning of the target field:

      regedit.exe /s      


   The new field should be similar to the following:

     regedit.exe /s "C:\Program Files\Dell\OpenManage\RAC\MN\Lanpatch.reg"


   NOTE: " " are needed around the absolute path.


3. If you used the "Systems Management" CD, version 3.3 to install your systems 
   management software, the "lanpatch.reg" file does not always automatically 
   install even though the interface states that the patch did automatically install.
   If this situation occurs, perform the following steps to manually install the
   patch:
   
   a. If you are using Internet Explorer version 5.5 (SP2) or later (this situation
      might also occur when using Internet Explorer, version 6.0),
      double-click the "lanpatch.reg" file. 

      The patch is copied to the managed system during the installation of the RAC 
      managed system software in the default directory <INSTALLATION PATH>\RAC\MN. 

   b. Apply the patch for each user account on the system running Internet Explorer.
 

4. Restart RAC Services.

======================================================================
POWEREDGE 7150 SYSTEM ISSUES
======================================================================

* On PowerEdge 7150 systems, the DRAC III may display text-only
  console redirection instead of graphical redirection. For graphical
  console redirection support, you must update the ATI video driver
  from the Dell Support website at "support.dell.com" or from the
  "Server Management" CD. The installation instructions for updating
  the driver are included in a "readme.txt" file included with the
  driver.

  The driver required to support DRAC III graphical console
  redirection is ATI Rage XL, version 5.0.2462.6000.

* The "racadm" command-line utility is supported on PowerEdge 7150
  managed systems. However, when using the utility on these systems,
  the primary command is "drscadm" instead of "racadm." For more
  information on using the "drscadm" utility on PowerEdge 7150
  systems, see the "Dell OpenManage Remote Service Card User's Guide"
  on your documentation CD.

* The DRAC III does not display the correct sensor values if the
  PowerEdge 7150 loses power while the DRAC III sensor window is open.

  If the PowerEdge 7150 loses power while the DRAC III sensors are
  being displayed, you must log out and log back in to the DRAC III to
  refresh the DRAC III sensor values.

* 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 DRAC III
  over a local area network (LAN) or the Internet.

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

Information in this document is subject to change without notice.
(C) 2003 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", and "Dell OpenManage"
are trademarks of Dell Computer Corporation; "Microsoft", "Windows", 
"Windows NT", and "MS-DOS" are registered trademarks of Microsoft 
Corporation; "Novell" and "NetWare" are registered trademarks of Novell,
Inc.

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.

February 2003