###################################################################### DELL OPENMANAGE(TM) SERVER ADMINISTRATOR RELEASE NOTES ###################################################################### Dell OpenManage Server Administrator is a secure Web tool for managing individual Dell(TM) PowerEdge(TM) servers. Using this tool, an administrator with an Internet/intranet connection can manage the server from any location using either a graphical user interface (GUI) that runs in a Web browser or a command line interface (CLI) that is accessed through the command prompt. This new tool allows an administrator to do more than obtain status information. The administrator can also run diagnostics, configure BIOS and system settings, and perform system updates, which are management tasks that have traditionally been possible only from a central console or at the server itself. Integrated security leverages the server's operating system security infrastructure and uses the Secure Sockets Layer (SSL) encryption protocol. This file contains updated information for your "Dell OpenManage Server Administrator User's Guide" and any other technical documentation included with Dell OpenManage Server Administrator. NOTE: See the Array Manager "readme" file (located in the "am312" directory on the "Systems Management" CD) for supplemental information regarding the Storage Management Service. The online Server Administrator documentation includes the "User's Guide," the "Messages Reference Guide," the "CIM Reference Guide," the "Command Line Interface (CLI) Reference Guide," and the "SNMP Reference Guide." You can access 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: * General Server Administrator Information * Server Administrator User Notes * Known Issues for Server Administrator * Historical Release Information for Legacy Users ###################################################################### GENERAL SERVER ADMINISTRATOR INFORMATION ###################################################################### This section provides the latest general update information about Server Administrator. ====================================================================== SUPPORTED SYSTEMS ====================================================================== Server Administrator operates with each of the following Dell systems: Dell PowerEdge 300, 350, 500SC, 1300, 1400, 1500SC, 1550, 1650, 2300, 2400, 2450, 2500, 2550, 4300, 4350, 4400, 4600, 6300, 6350, 6400, 6450, and 8450 ====================================================================== SUPPORTED OPERATING SYSTEMS ====================================================================== Server Administrator operates with each of the following operating systems: * Microsoft(R) Windows NT(R) 4.0 Server Family (Service Pack 6 or higher) These operating systems include Windows NT 4.0 Server, Windows NT 4.0 Server Enterprise, Windows NT Small Business Server (SBS) 4.5, and Windows NT 4.0 Terminal Server. * Microsoft Windows(R) 2000 Server Family These operating systems include Windows 2000 Server, Windows 2000 Advanced Server, and Windows SBS 2000. * Red Hat Linux, version 7.1 or later * Novell(R) NetWare(R), version 5.1 (Service Pack 3 or higher) or 6.0 or later The following matrix shows the operating system support for each Server Administrator service; abbreviations used are Instrumentation Service (I), Storage Management Service (SM), Diagnostic Service (D), Update Service (U), and Remote Access Service (RA). NOTE: Some services may be supported only on certain servers, regardless of the operating system. For example, the Remote Access Service (RA) is supported on the PowerEdge 4600 only. To avoid attempts to run unsupported features, the Server Administrator GUI presents only those services available on your server. SUPPORTED OPERATING SYSTEMS SUPPORTED SERVICES   Microsoft Windows NT 4.0 Server Family I, SM, D, U, RA (Service Pack 6 or higher) Microsoft Windows 2000 Server Family I, SM, D, U, RA Red Hat Linux, version 7.1 or later I, D, RA Novell NetWare, version 5.1 I, RA (Service Pack 3 or higher) Novell NetWare version 6.0 or later I, RA Server Administrator supports the following major systems management protocols: - Common Information Model (CIM) - Simple Network Management Protocol (SNMP) - Hyper Text Transfer Protocol Secure (HTTPS) Support for CIM and SNMP is operating system-dependent and, in some cases, operating system-version dependent. The following matrix shows the operating system support for each protocol: SUPPORTED OPERATING SYSTEMS SNMP CIM Windows NT 4.0 Server Family Yes Yes (with CIMOM service pack) Windows 2000 Server Family Yes Yes NetWare Yes No Red Hat Linux Yes No ====================================================================== SUPPORTED WEB BROWSERS ====================================================================== * Internet Explorer 5.0 or later * Netscape Navigator 6.1 or later ===================================================================== SUPPORTED RAID CONTROLLERS AND REQUIRED DRIVER/FIRMWARE REVISION LEVELS FOR STORAGE MANAGEMENT AND DIAGNOSTICS ===================================================================== Server Administrator enables you to manage attached SCSI/RAID storage devices and to run diagnostics on these devices. The following are the required driver and firmware revision levels for the supported RAID controllers. NOTES: The driver and firmware revision levels shown are the minimum required for the corresponding RAID controller. Revision levels later than those shown are most likely also acceptable. NetWare information is provided for the Server Administrator Storage Management Service only; diagnostics are not currently supported on NetWare. * PERC 2/SC on a PowerEdge 8450 only - Windows NT driver: 4.11 - Windows 2000 driver: 2.68 - NetWare 4.2 driver: 3.11a - NetWare 5.x driver: 3.11a - Firmware: 3.13 * PERC 2/SC on supported systems other than the 8450 - Windows NT driver: 2.32 - Windows 2000 driver: 2.68 - NetWare 4.2 driver: 2.06 - NetWare 5.x driver: 2.06 - Firmware: 3.13 * PERC 3/SC - Windows NT driver: 4.11 - Windows 2000 driver: 5.22.1 - NetWare 4.2 driver: 3.11a - NetWare 5.x driver: 3.11a - Firmware: 1.63 * PERC 2/DC on x300 servers - Windows NT driver: 2.32 - Windows 2000 driver: 2.68 - NetWare 4.2 driver: 2.06 - NetWare 5.x driver: 2.06 - Firmware: 1.06 * PERC 2/DC on x400 servers - Windows NT driver: 4.11 - Windows 2000 driver: 2.68 - NetWare 4.2 driver: 3.11a - NetWare 5.x driver: 3.11a - Firmware: 1.06 * PERC 3/QC - Windows NT driver: 4.11 - Windows NT-64 driver: 6.19 - Windows 2000 driver: 5.22.1 - NetWare 4.2 driver: 3.11a - NetWare 5.x driver: 3.11a - Firmware: 1.61j * PERC 3/DC - Windows NT driver: 4.11 - Windows 2000 driver: 5.22.1 - NetWare 4.2 driver: 3.11a - NetWare 5.x driver: 3.11a - Firmware: 1.61j * PERC 3/DCL - Windows NT Driver: 4.11 - Windows 2000 Driver: 5.22.1 - NetWare 4.2 driver: 3.11a - NetWare 5.x driver: 3.11a - Firmware: 1.61j * PERC 2/QC (PERC 2) - Windows NT driver: 4933 - Windows 2000 driver: 4933 - NetWare 4.2 driver: NA - NetWare 5.x driver: 3546 - Firmware: 2.7.0.3153 * PERC 2/Si - Windows NT driver: 4933 - Windows 2000 driver: 4933 - NetWare 4.2 driver: NA - NetWare 5.x driver: 3546 - Firmware: 2.7.0.3546 * PERC 3/Si - Windows NT driver: 4933 - Windows 2000 driver: 4933 - NetWare 4.2 driver: NA - NetWare 5.x driver: 3546 - Firmware: 2.7.0.3546 * PERC 3/Di (for PowerEdge 1650, 2500, and 4600) - Windows NT driver: 4933 - Windows 2000 driver: 4933 - NetWare 4.2 driver: NA - NetWare 5.x driver: 3546 - Firmware: 2.7.0.3153 * PERC 3/Di (for systems other than PowerEdge 1650, 2500, and 4600) - Windows NT driver: 4933 - Windows 2000 driver: 4933 - NetWare 4.2 driver: NA - NetWare 5.x driver: 3546 - Firmware: 2.7.0.3546 * PowerVault(TM) 660F Windows NT or 2000: - Host bus adapter: QL2100 - Firmware: 1.35 - Windows NT or 2000 driver: QL2100.SYS 7.05.08 OR - Host bus adapter: QL2200 - Firmware: 1.45 - Windows NT or 2000 driver: QL2200.SYS 7.05.08 ###################################################################### SERVER ADMINISTRATOR USER NOTES ###################################################################### This section provides information to help enhance your experience with Server Administrator in particular implementations and environments. ====================================================================== NOTES ON INSTALLATION AND UNINSTALLATION ====================================================================== * You can find general installation information in the "Dell OpenManage Systems Management Software Quick Installation Guide". You can find detailed installation information, including unattended installation, in the "Dell OpenManage Server Administrator User's Guide". Both of these documents are located on the "Product Documentation" CD. * Microsoft Internet Explorer Version 5.5 is available in the "\support\Windows\IE5.5" directory on the "Dell OpenManage Systems Management" CD. * BroadCom NIC utilities and agents are available in the "\ihv\BroadCom" directory on the "Systems Management" CD. * Before you install Server Administrator, it is recommended that you uninstall any previous installations of Resolution Assistant. * 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 Red Hat Linux, the SNMP agent package that ships with Red Hat Linux must be installed before Server Administrator is installed. The name of that SNMP agent package starts with "ucd-snmp". * 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. * NetWare command line interface utilities for the Dell PERC 2, PERC 2/Si, PERC 3/Si, and PERC 3/Di controllers are available in the "\support\Netware\RAID\adaptec" directory on the "Systems Management" CD. These utilities support both NetWare 5.1 and NetWare 6.0. * NetWare application utilities for the PERC 3/QC, PERC 3/DC, PERC 3/DCL, and PERC 3/SC controllers are available in the "\support\NetWare\RAID\ami" directory on the "Systems Management" CD. These utilities support both NetWare 5.1 and NetWare 6.0. * A Linux management application for the PERC 2, PERC 2/Si, PERC 3/Si, and PERC 3/Di controllers is available in the "\support\Linux\RAID\adaptec" directory on the "Systems Management" CD. These utilities support both Red Hat Linux 7.2 and Red Hat Linux 7.1 SBE. * Linux RAID management tools for the PERC 3/QC, PERC 3/DC, PERC 3/DCL, and PERC 3/SC controllers are available in the "\support\Linux\RAID\ami" directory on the "Systems Management" CD. These utilities support both Red Hat Linux 7.2 and Red Hat Linux 7.1 SBE. * The Managed Node portion of Array Manager replaces the Windows Disk Management Service. To view the "Disk Management" page in the Server Administrator GUI, install the Management Station portion of Array Manager on the same system as the Managed Node portion. If, during installation, you select "Storage Management" only, the Server Administrator installation program installs only the Managed Node portion of Array Manager. Server Administrator GUI does not allow the "Disk Management" page to load unless the Management Station portion is also installed. ====================================================================== NOTES ON INSTRUMENTATION ====================================================================== * Redundant memory is a new feature supported on the PowerEdge 4600 only. It enables the use of reserve memory in the event of significant memory failure within the main memory modules. Server Administrator currently supports a type of redundant memory called "spare bank." Spare bank is a redundant memory implementation in which the contents of a memory module that is experiencing sufficient failures is copied into a spare module of the same type and capacity. The system then uses this spare bank module until the next reboot. The operating system does not "see" nor report the memory capacity allocated to the spare bank. * Nonpersistant memory error counts is a new feature supported on the PowerEdge 1650 and 4600. It eliminates the persistence of memory error counts across restarts, which includes reboots and manual restarts of Server Administrator. This feature will be implemented for all other platforms in a future release. * 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. * You must configure SNMP for use with the Instrumentation Service. The Instrumentation Service uses the SNMP services provided by the operating system on the managed system. The SNMP community name used by management applications such as IT Assistant must match the SNMP community name configured on the managed system. The SNMP services must be configured to allow SNMP get/set operations and SNMP trap generation. Failure to configure these features may result in the inability to manage or monitor your system. If your system is not configured properly, you might not receive asynchronous notification (SNMP traps). Review the SNMP configuration information contained within the "Dell OpenManage Server Administrator User's Guide" and information included with your operating system. * Dynamic kernel support on Red Hat Linux: Table 1. Precompiled Kernels Supported by Server Administrator With Prebuilt Device Drivers ----------------------------------------------------- | Operating System | Kernel | ----------------------------------------------------- | Red Hat Linux 7.1 | 2.4.3-6 | | | 2.4.3-6smp | | | 2.4.3-6enterprise | | | | | | 2.4.3-12 | | | 2.4.3-12smp | | | 2.4.3-12enterprise | ----------------------------------------------------- | Red Hat Linux 7.2 | 2.4.7-10 | | | 2.4.7-10smp | | | 2.4.7-10enterprise | ----------------------------------------------------- The Instrumentation Service provides prebuilt device drivers for the precompiled kernels listed above in Table 1. When the Instrumentation Service detects that none of its prebuilt device drivers supports the running kernel, it attempts to build a device driver for that kernel. This feature of Server Administrator is called dynamic kernel support. Server Administrator's dynamic kernel support builds a device driver when needed during the Instrumentation Service installation or startup. If the running kernel is not one of those listed in Table 1 or has been reconfigured and recompiled in such a way that none of the prebuilt device drivers support the kernel, dynamic kernel support must be used to support the running kernel. For Dynamic Kernel Support to be used, certain prerequisites must be met. See the "Dell OpenManage Server Administrator User's Guide" for more information about dynamic kernel support. * SNMP access control configuration on Red Hat Linux: The MIB branch implemented by the Instrumentation Service is identified by the OID "1.3.6.1.4.1.674.10892.1". Management applications must have access to this branch of the MIB tree to manage systems running the Instrumentation Service. The default SNMP configuration installed by the ucd-snmp package provides read-only access only to the MIB-II "system" branch (identified by the OID 1.3.6.1.2.1.1) of the MIB tree for the "public" community. This configuration does not allow management applications to retrieve or change Instrumentation Service information. If the Instrumentation Service detects this configuration during installation, it attempts to modify the SNMP configuration to provide read-only access to the entire MIB tree for the "public" community. * Firewall Configuration on Red Hat Linux: If you select High or Medium firewall security when installing Red Hat Linux 7.1 or later, the SNMP port on all external network interfaces is closed by default. To enable management applications to retrieve information from the Instrumentation Service, the SNMP port on at least one external network interface must be open. If the Instrumentation Service detects that the SNMP port is not open in the firewall for any external network interface, the Instrumentation Service displays a warning message and logs a message to the system log. You can open the SNMP port by disabling the firewall, opening an entire external network interface in the firewall, or opening the SNMP port for at least one external network interface in the firewall. You can perform this action before or after the Instrumentation Service is started. To open the SNMP port using one of the previously described methods, perform the following steps: 1. At the Linux command prompt, type "setup" and press to start the Text Mode Setup Utility. The "Choose a Tool" menu appears. 2. Select "Firewall Configuration" using the down arrow and press . The "Firewall Configuration" screen appears. 3. Select the desired Security Level by tabbing to it and pressing the spacebar. The selected Security Level is indicated by an asterisk. NOTE: Press for more information about the firewall security levels. The default SNMP port number is 161. a. To disable the firewall, select "No firewall" and go to step 7. b. To open an entire network interface or the SNMP port, select "High" or "Medium" and continue with step 4. 4. Tab to "Customize" and press . The "Firewall Configuration - Customize" screen appears. 5. Select whether to open an entire network interface or just the SNMP port on all network interfaces. a. To open an entire network interface, tab to one of the Trusted Devices and press the spacebar. An asterisk in the box to the left of the device name indicates that the entire interface will be opened. b. To open just the SNMP port on all network interfaces, tab to "Other ports" and type "snmp:udp". 6. Tab to "OK" and press . The "Firewall Configuration" screen appears. 7. Tab to "OK" and press . The "Choose a Tool" menu appears. 8. Tab to "Quit" and press . ====================================================================== NOTES ON BIOS AND FIRMWARE UPDATES ====================================================================== * BIOS updates are not supported for PowerEdge 350, 500SC, and 8450 systems. * Firmware updates are not supported for PowerEdge 1500SC, 1550, and 8450 systems. NOTE: PowerEdge 2550 BIOS updates are supported if the BIOS revision is later than or equal to A06. NOTE: The "Last Update Date" field indicates the date that the BIOS was flashed through Server Administrator or other Dell OpenManage products. This date does not reflect the last BIOS update that occurred using a diskette. ====================================================================== NOTES ON DIAGNOSTICS ====================================================================== * Server Administrator diagnostics specifically support the following Dell-supplied hardware devices: - CD drives - DVD drives - Diskette and LS drives - IDE attached hard drives - SCSI attached hard drives - Intel network interface cards - Modems - Tape drives - Video controllers on Windows 2000 and Linux operating system platforms - SCSI controllers - The following RAID controllers: For Windows: PERC 2/DC, PERC 2/QC (PERC 2), PERC 2/Si, PERC 3/Si, PERC 3/Di, PERC 3/QC, PERC 3/DC, PERC 3/DCL, PERC 3/SC (See firmware requirements in the section "General Server Administrator Information.") For Linux: PERC 2/DC, PERC 2/QC (PERC 2), PERC 2/Si, PERC 3/Si, PERC 3/Di, PERC 3/QC, PERC 3/DC, PERC 3/DCL (See firmware requirements in the section "General Server Administrator Information.") - Hard drives attached to the following RAID Controllers (Windows only): PERC 2/DC, PERC 2/QC (PERC 2), PERC 2/Si, PERC 3/Si, PERC 3/Di, PERC 3/QC, PERC 3/DC, PERC 3/DCL, PERC 3/SC (See firmware requirements in the section "General Server Administrator Information.") - All hard drives attached to RAID controllers (Linux) * When upgrading from Server Diagnostics 1.1 to the Diagnostic Service, the history file is saved in the "\bak" directory located in the root installation directory. The filename of this history log is "result.xml". * When e-mailing from the "Diagnostic Result" or "Diagnostic Result History" page, you must expand the tabs to incorporate all of the detail information into the e-mail. Clicking "Email" sends a screen snapshot of the page, so if you do not expand the tabs, the support technician does not receive complete data. * For Linux systems only, this version of the "Systems Management" CD installs a patch for the Diagnostic Service on systems other than the PowerEdge 1650 and 4600, which do not require it. The patch addresses an issue that existed in earlier versions of the Diagnostic Service in which a diagnostic could time out and appear to hang during execution. In the Server Administrator GUI, the diagnostic would not progress to 100%, and in the CLI, no results would display. ====================================================================== NOTES ON REMOTE ACCESS ====================================================================== This feature is supported on the PowerEdge 1650 and 4600 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 the Dell OpenManage Remote Access Card (DRAC) III, which is an optional card installed in a server. The following are some of the features offered by DRAC III: * In-band configuration of DRAC III users and features * Out-of-band server management capabilities * Console redirection of the managed server's console in either text or graphical mode * Access to system event log (SEL) and power-on self test (POST) log * Alert notification when system is down; full access to the down system * Embedded Web Server * System health monitoring * Operation from peripheral component interconnect (PCI) power, external AC power, and/or battery power * Remote update of DRAC III firmware * Ability to perform server power management actions * Password-level security management The DRAC III also has its own command line interface that is accessed through the "racadm" command. You can add the "racadm" commands to a batch or script file to automate various user tasks. To limit the stress load on the managed system and DRAC III, you should add "sleep" or "delay" commands of one or two seconds between the individual "racadm" commands. ###################################################################### 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. ====================================================================== * 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 "Fan Probes" on the tab menu bar. * 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://:. Any http://: 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, allow the system to run for approximately 30 minutes before starting the Server Administrator Web server. ====================================================================== ISSUES FOR SERVER ADMINISTRATOR RUNNING ON RED HAT LINUX ====================================================================== * When you set Alert Actions for any component, you can specify the action to be an application launch. Do not specify an application that requires X Windows because Server Administrator running on a Linux system cannot launch such applications. * If you are running X windows under Linux, the Linux system console is not active and the user won't be able to receive the Server Administrator alert if the "alert on console" option is specified. ====================================================================== ISSUES FOR SERVER ADMINISTRATOR RUNNING ON ALL NOVELL NETWARE OPERATING SYSTEMS ====================================================================== * This version of Server Administrator does not support the Storage Management Service on systems running Novell NetWare. * Under "Network information," the IP address displays as "Not Obtained." ====================================================================== ISSUES FOR SERVER ADMINISTRATOR RUNNING ON THE NOVELL NETWARE 5.1 OPERATING SYSTEM ====================================================================== * If you get an NDSComponentException message while starting Server Administrator, perform one of the following steps: - If the default certificate is corrupt or does not exist, see the "Web Server and Security Setup" section of the 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 the 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 the and to your system's name on the line "nssl.keystore = certificate name - hostname". * If you receive an SSLComponentException message while starting the 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 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 JVM 1.1.7B dated after 07/23/2001. 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, then 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 is the line that 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. ====================================================================== ISSUES FOR SERVER ADMINISTRATOR RUNNING ON NOVELL NETWARE 6.0 OPERATING SYSTEMS. ====================================================================== * This version of Server Administrator does not support Adaptec CI/O on systems running Novell NetWare 6.0. NOTE: Although 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 INSTALLATION AND UNINSTALLATION ====================================================================== * If you already have Adaptec Fast Console installed on your system, you must uninstall this application before installing the Storage Management service. * The Windows installer service does not allow installation using Terminal Services when mapping to a remote CD drive. Because the Windows Installer runs as a system service, when an administrator installs 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. * 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 uninstall 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 uninstall program to continue, press . * If you have Dell OpenManage Resolution Assistant installed on your system, you must manually uninstall it before installing any systems management applications. * 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." * If you install Intel Client Instrumentation for DMI and SNMP from the "Dell OpenManage Application" CD 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. * If you upgrade from Server Agent 4.x to Server Administrator 1.0, the advanced installation settings for Server Administrator may not be available at the time of installation. This event occurs only when you upgrade the management station components first and then upgrade the managed system components. If the advanced settings are unavailable, you can set them when the installation finishes. ====================================================================== ISSUES FOR INSTRUMENTATION ====================================================================== The following are open issues and workarounds, where available, for Server Administrator on systems that are running Windows NT, Windows 2000, Red Hat Linux, or the Novell NetWare operating system. ---------------------------------------------------------------------- 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 the NIC might produce unexpected results. It is recommended that you perform all NIC configurations through the actual System Setup screen that is available by pressing while a system is booting. This problem is present in the CLI interface and in IT Assistant. * A PowerEdge 2450 with BIOS version X03 or X07 returns the value "Unknown" for the primary SCSI state. To cause the BIOS to report the correct value, set the value to "ON" (as appropriate) using Server Administrator. * Setting any warning threshold to a default value on the PowerEdge 1650 and 4600 is not supported. Attempting to do so results in an error message. * Warning thresholds that are modified on the PowerEdge 1650 and 4600 are reset to their default values if the system is power cycled or loses AC power. If you change your default 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 Dell OpenManage Command Line Interface (CLI) User's Guide for more information. ---------------------------------------------------------------------- INSTRUMENTATION ISSUES FOR THE RED HAT LINUX OPERATING SYSTEM ---------------------------------------------------------------------- * PowerVault(TM) 20xS and 21xS storage systems attached to managed systems running the Red Hat Linux operating system cannot be managed by Server Administrator using the following RAID controllers: - PERC 2/QC - PERC 2/Di - PERC 2/Si - PERC 3/Di - PERC 3/Si * If you plan to perform a remote flash BIOS update on a PowerEdge 1500SC, 1550, 1650, 2500, or 2550 system that is running Red Hat Linux with a kernel that includes Symmetrical Multi-Processing (SMP) support, you must perform one of the following series of steps for the update to occur properly. - If you are using the Linux Loader (LILO), perform the following steps: 1. Edit the LILO configuration file "/etc/lilo.conf". 2. Add the following line after the "image" line for any kernels that include SMP support: append="reboot=bios" For example, suppose the following line is in the configuration file: image=/boot/vmlinuz-2.4.3-6smp You would add the second line indented below the first: image=/boot/vmlinuz-2.4.3-6smp append="reboot=bios" 3. After updating the LILO configuration file, run the following command for the change to take effect: lilo 4. Reboot the system. 5. Perform the remote flash BIOS update. - If you are using the GNU Grand Unified Bootloader (GRUB), perform the following steps: 1. Edit the GRUB configuration file "/etc/grub.conf". 2. Append "reboot=bios" to the "kernel" line for any kernels that include SMP support. For example, suppose the following line is in the configuration file: kernel /vmlinuz-2.4.7-10enterprise ro root=/dev/sda3 You would append "reboot=bios" to the end: kernel /vmlinuz-2.4.7-10enterprise ro root=/dev/sda3 reboot=bios 3. Reboot the system. 4. Perform the remote flash BIOS update. * Some data might not be reported for NIC adapters on the Linux operating system. The information varies according to the NIC vendor, driver version, and Linux version. It is recommended that you use the Server Assistant CD to install the Linux operating system to ensure that the system uses drivers with the maximum amount of available data. ---------------------------------------------------------------------- INSTRUMENTATION ISSUE FOR THE 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 a patch on your system. To download the patch, go to the Hewlett Packard website located at www.hp.com. * In some circumstances the Server Administrator CIM interface may not be properly registered with the operating system and will 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 THE NOVELL NETWARE OPERATING SYSTEM ---------------------------------------------------------------------- * The Instrumentation Service might incorrectly report NetWare version 5.1 as version 5.0. * On managed systems running the Novell NetWare operating system, the Instrumentation Service loads multiple NetWare Loadable Modules (NLMs) at system startup. Some NLMs will automatically uninstall because they are not required on a particular system. The NLM uninstall process occurs approximately two 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 prior to 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 ---------------------------------------------------------------------- * The Diagnostic Service tab is not available in Server Administrator and is not listed on the Health page at startup. Diagnostic Service waits for the Server Administrator service to start completely before enumerating (scanning system for available devices to diagnose). If you press to refresh the tab will show up when enumeration is complete. This process can take several minutes on some systems. * When you select "Run Tests" in the Diagnostic Selection page or in the Diagnostic Scheduler page, only some of the selected tests display in the progress page. This event occurs if you click the button very fast. 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 the user changes. * If the managed system has a statically assigned IP address, 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 for the network card must be obtained via a DHCP server. Configure the network card 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 "Progess" page and return to the page by clicking the "View" tab, the Diagnostic Service continues to run 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 begun to run. * Tests scheduled through the test scheduler or executed through the command line interface (CLI) cannot be aborted. * Aborting a diagnostic while it is being conducted might not succeed immediately if the diagnostic is performing critical operations. Abort takes place only after critical operations complete. * If you see a warning icon notifying you that diagnostics are currently being run by another user, or if you see a blank page when attempting to access the "View" tab, you may have performed these steps: 1. Logged in to Server Administrator. 2. Navigated to the "Diagnostics" --> "View" tab. 3. Opened a command window. 4. Run diagnostics through the CLI. 5. Navigated to the "Properties" --> "Health" tab. These actions launch the "Diagnostic Service" page with the warning icon notifying you that diagnostics are currently being run by another user. If you then click the "Diagnostic Service" link or navigate to the "Diagnostics" --> "View" tab (while the diagnostics are still running), in Netscape 6.1, you see a blank page. In Internet Explorer, if you click the "Diagnostic Service" link, you do not receive the warning that states the diagnostics are currently being run by another user. ---------------------------------------------------------------------- * 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 abort 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 yet display no output or results in the command prompt window. If this event 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 through the CLI and you press a key while the diagnostic is running, the test aborts, but the result displayed is "Failed". * When a diagnostic returns "Failed" after you run it through the CLI, you can find the details of the failure by starting the Server Administrator GUI, clicking the "Diagnostic" tab, and selecting "Result History". * The memory diagnostic allocates only 2 GB of memory to perform the Memory Pattern Test on Windows NT, Windows 2000, and Linux. ECC events are still detected on all DIMMs. * For PowerEdge 1300, 1400, 1500SC, 2300, 4300, 4350, 6300, and 6350 systems: The following error may occur on certain specific models of Quantum Viking II 4-GB and 9.1-GB hard drives when running the SCSI elite hard drive test from Server Administrator: "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." Certain 4-GB and 9.1-GB drives on these systems do not properly support the SCSI elite hard drive tests when run from Server Administrator. Solution: The error is incorrect and should be ignored. Run 32-bit diagnostics from either a diskette or the utility partition to properly test the drive. ---------------------------------------------------------------------- ISSUES FOR WINDOWS OPERATING SYSTEMS ---------------------------------------------------------------------- * Array Manager 3.1 or later is a requirement to diagnose RAID attached hard drives. If Array Manager is not installed, the Elite RAID attached hard drive tests are not visible in the Diagnostic Service. * It is recommended that no other drive activity be underway while you are running the hard drive diagnostics. The diagnostics may run slowly if other drive activity is running simultaneously. * On an integrated drive electronics (IDE) system that is configured with a non-Self Monitoring and Reporting Technology (SMART) device as the master (on either channel) and a SMART-enabled hard drive as the slave on the same channel, the SMART self-test command cannot run and returns a failure message. See the Microsoft Knowledge Base Article ID: Q304572 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. * 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 device other than a hard drive (such as a CD drive), both the standard and extended test indicate that the hard drive does not support the self-test. This problem should be eliminated with Service Pack 3 for Windows 2000. For more information, see support.microsoft.com/support/kb/articles/q304/5/72.asp. * The operating system's diskette format application and the Diagnostic Service Floppy Drive test are permitted to run simultaneously under Windows 2000. However, if you run this scenario, false diagnostic errors might occur. * If any hard drive is failing on 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 well connected to the controller. * If you run the Adaptec RAID controller diagnostic with an application that reserves the controller, the diagnostic reports 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 the Services application, locate the Disk Management Service, right-click your mouse, and select stop. To stop the FAST or PERC Console, exit the application. * For managed systems with SCSI hard drives attached to a Dell- supported RAID controller: If the diagnostics CLI does not list the RAID hard drive diagnostics ("raidhd") when the Server Administrator Web server is stopped, start the Web server using the "net start Server Administrator" command; this action enables the "raidhd" diagnostic. * 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 will operate properly when the upgrade is finished. ---------------------------------------------------------------------- ISSUES FOR LINUX OPERATING SYSTEMS ---------------------------------------------------------------------- * If a Dell-supported NIC is not listed by the Diagnostic Service, the currently installed NIC driver might be out-of-date. Check the "Network Properties" tab; if the "IP address" value is "Not obtained", 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. * Periodically, running the command "omdiag [system | chassis] cmos" 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 CMOS test completes without problems before the JVM stops; when the JVM does stop, it produces a log file. The Web server JVM is unaffected by such an event, so you can subsequently run the "omdiag" CLI command without encountering problems. * The PCI diagnostic is not supported on PowerEdge 4600. Support will be added in a future release. ====================================================================== ISSUES FOR REMOTE ACCESS ====================================================================== NOTE: The Remote Access Service is supported on the PowerEdge 1650 and 4600 only. The following subsections list the currently known issues regarding implementation and operation of the Remote Access Service and DRAC III in Server Administrator. ---------------------------------------------------------------------- ISSUES FOR ALL OPERATING SYSTEMS ---------------------------------------------------------------------- * The mouse moves erratically on the screen during console redirection. 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 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 DRAC III 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. * You have trouble connecting to the Internet if the DRAC III 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 has occurred 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. To correct this problem, perform the following steps: 1. If you are using Internet Explorer 5.0, 5.01, or 5.5 (SP1), you must update your browser to Internet Explorer 5.5 (SP2). The update is available at windowsupdate.com. If you are using Internet Explorer version 5.5 (SP2) or later, skip to step 2. 2. Apply the "lanpatch.reg" registry patch. The patch is copied to the managed system during the installation of the DRAC III managed system software. The patch should be applied for each user account on the system running Internet Explorer. ---------------------------------------------------------------------- ISSUES FOR WINDOWS OPERATING SYSTEMS ---------------------------------------------------------------------- * Resizing the Windows desktop to 640 x 480 resolution causes some loss of displayed information in the browser when viewing the DRAC III graphical user interface (GUI). The behavior is the same 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 DRAC III over a local area network (LAN) or the Internet. HISTORICAL RELEASE INFORMATION FOR LEGACY USERS ###################################################################### The following section contains historical information from releases of the Dell OpenManage Server Agent running on supported Microsoft Windows, Red Hat Linux, and Novell NetWare operating systems. Server Agent preceded Server Administrator. These excerpts from previous readme.txt files show a record of features and resolved issues. ################################################################ DELL OPENMANAGE SERVER AGENT 4.5 ################################################################ This readme file contains updated information for your "Dell OpenManage Server Agent User's Guide" and any other technical documentation included with Dell OpenManage Server Agent 4.5 for 32-bit systems. See the Dell | Support website (support.dell.com) for the most current information. The following sections contain requirements, features, and open issues for Server Agent version 4.5. ================================================================ REQUIREMENTS ================================================================ Release date: October 2001 Supported systems: Dell PowerEdge 1500SC Operating systems: Microsoft Windows NT Server 4.x with SP 4 or later Microsoft Windows 2000 Server family (includes Windows 2000 Server and Windows 2000 Advanced Server) Novell NetWare 5.x Red Hat Linux 7.1 or later (See "Dynamic Kernel Support" section below for more information.) NOTE: Server Agent is not supported on the PowerEdge 1500SC running the Red Hat Linux 7.0 operating system or the Novell NetWare 4.x operating system. ================================================================ WHAT IS NEW OR CHANGED IN THIS RELEASE ================================================================ Support was added for the PowerEdge 1500SC system. ################################################################ DELL OPENMANAGE SERVER AGENT 4.4.1 ################################################################ This readme file contains updated information for your "Dell OpenManage Server Agent User's Guide" and any other technical documentation included with Dell OpenManage Server Agent 4.4.1 for 32-bit systems. See the Dell support website (support.dell.com) for the most current information. The following sections contain requirements, features, and open issues for Server Agent Version 4.4.1. ================================================================ REQUIREMENTS ================================================================ Release date: September 2001 Supported systems: Dell PowerEdge 300, 350, 500SC, 1300, 1400, 1550, 2300, 2400, 2450, 2500, 2550, 4300, 4350, 4400, 6300, 6350, 6400, 6450, 8450 Operating systems: Microsoft Windows NT Server 4.x with Service Pack (SP) 4 or later Microsoft Windows 2000 Server family (includes Windows 2000 Server and Windows 2000 Advanced Server) Novell NetWare 4.x or 5.x Red Hat Linux 7.0 or later (See "Dynamic Kernel Support" section below for more information.) NOTE: Server Agent is not supported on the PowerEdge 500SC running the Red Hat Linux 7.0 operating system. ================================================================ WHAT IS NEW OR CHANGED IN THIS RELEASE ================================================================ This release contains the following new features and changes: * Support for Red Hat Linux 7.1 SBE (Kernels 2.4.3-6 and 2.4.3-12) with prebuilt device drivers. * Dynamic Kernel Support for Red Hat Linux. * Support for the DMI management protocol has been removed. * In the Server Agent MIB file "10892.mib", "Dell" has been replaced by "Server" in the annotation TYPE field for each trap. * In the Server Agent event configuration file "10892evt.cfg", the OID_ALIAS value has been changed from "Dell_Server3_Baseboard_Agent" to "Server_Agent", and "Dell" has been replaced by "Server" in the Short Descr. field for each event. ################################################################ DELL OPENMANAGE SERVER AGENT 4.4.0 ################################################################ This readme file contains updated information for your "Dell OpenManage Server Agent User's Guide" and any other technical documentation included with Dell OpenManage Server Agent 4.4.0 for 32-bit systems. ================================================================ REQUIREMENTS ================================================================ Release Date: July 2001 Supported systems: Dell PowerEdge 350, 500SC, 1550 Operating systems: Microsoft Windows NT Server 4.x with Service Pack (SP) 4 or later Microsoft Windows 2000 Server family (includes Windows 2000 Server and Windows 2000 Advanced Server) Novell NetWare 4.x or 5.x Red Hat Linux 7.0 (Kernel version: 2.2.16) Red Hat Linux SNMP agent: UCD-SNMP version 4.1.2-8smux ================================================================ WHAT'S NEW IN THIS RELEASE ================================================================ This release adds support for the following Dell systems and features: * PowerEdge 500SC * PowerEdge 1550 with the Intel Pentium III microprocessor * PowerEdge 350 watchdog support ################################################################ DELL OPENMANAGE SERVER AGENT 4.3.0 ################################################################ This readme file contains updated information for your "Dell OpenManage Server Agent User's Guide" and any other technical documentation included with Dell OpenManage Server Agent 4.3.0. There is separate history_readme.txt file that documents features and issues for previous versions of the Server Agent on supported operating systems. Version 4.3 is the first release of Server Agent that combines supported operating systems for Microsoft Windows, Novell NetWare, and Red Hat Linux. All of these supported operating systems are documented in this readme. ========================================================= REQUIREMENTS ========================================================= Release Date: March, 2001 Supported systems: Dell PowerEdge 300, 350, 1300, 1400, 1550, 2300, 2400, 2450, 2500, 2550, 4300, 4350, 4400, 6300, 6350, 6400, 6450, 8450 Operating systems: Microsoft Windows NT Server 4.x with Service Pack (SP) 4 or later Microsoft Windows 2000 Server family (includes Windows 2000 Server and Windows 2000 Advanced Server) Novell NetWare 4.x or 5.x Red Hat Linux 7.0 (Kernel version: 2.2.16) Red Hat Linux SNMP agent: UCD-SNMP version 4.1.2-8smux ========================================================= WHAT'S NEW IN THIS RELEASE ========================================================= This release adds support for the following Dell systems: * PowerEdge 2500 * PowerEdge 2550 --------------- RESOLVED ISSUES --------------- SUPPORTED SETTING OF HUNG SERVER ALERTS FOR POWEREDGE 8450 SYSTEMS ------------------------------------------------------------------ When you configure the hung server action for a Dell PowerEdge 8450 system, the system either performs a "system reset" or a "recycle system power" action. POWEREDGE 350 ISSUES -------------------- This release addresses the following Dell PowerEdge 350 issues that were originally addressed by Dell OpenManage Server Agent 4.2.0 Update 1: * Changes thresholds for the -12 volt (V) voltage probe on the system board. These new thresholds prevent erroneous probe failures and warnings. * Corrects erroneous fan failure reports in the event log. * Corrects system crashes at startup caused by incorrect event log record length. * Disables the chassis identification feature. POWERVAULT 2xxS SCSI DISK SYSTEMS AND SNMP ------------------------------------------ This release addresses the following Dell PowerVault 2xxS SCSI disk system issues that were originally addressed by Dell OpenManage Server Agent 4.2.0 Update 1: * Allows Dell PowerEdge systems attached to the Dell PowerVault 2xxS SCSI disk system to respond to simple network management protocol (SNMP) requests for information. Under certain rare circumstances, some Dell systems with PowerVault 2xxS attached were not responding to SNMP requests. ###################################################################### DELL OPENMANAGE SERVER AGENT 4.2.2 ###################################################################### ====================================================================== REQUIREMENTS ====================================================================== DELL OPENMANAGE SERVER AGENT Version: 4.2.2 Release date: February 2001 Supported systems: Dell PowerEdge 300, 350, 1300, 1400, 1550, 2300, 2400, 2450, 4300, 4350, 4400, 6300, 6350, 6400, 6450, 8450 Operating systems: Microsoft Windows NT Server 4.x with Service Pack (SP) 4 or later, Microsoft Windows 2000 Server Family (includes Windows 2000 Server and Windows 2000 Advanced Server), Novell NetWare 4.x or 5.x ======================================================================= NEW FEATURES AND RESOLVED ISSUES IN DELL OPENMANAGE SERVER AGENT 4.2.2 ======================================================================= Dell OpenManage Server Agent 4.2.2 now supports the Dell PowerEdge 350. In addition, Dell OpenManage Server Agent 4.2.2 resolves the following issues. ----------------------------- INCORRECT CURRENT SENSOR DATA ----------------------------- In rare circumstances Dell OpenManage Server Agent incorrectly reported data for current (amperage) sensors. Incorrect amperage readings may have been reported for the following PowerEdge systems: 4300, 4350, 4400, 6300, 6350, 6400, and 6450. ---------------------------------------------------- SNMP TIMEOUTS WITH POWERVAULT 2xxS SCSI DISK SYSTEMS ---------------------------------------------------- In rare circumstances the Dell OpenManage Server Agent SNMP interface stops responding when a Dell PowerVault 2xxS storage system is attached to a system. The DMI and CIM interfaces may also stop responding. ################################################################### DELL OPENMANAGE SERVER AGENT 4.2.1 ################################################################### ====================================================================== REQUIREMENTS ====================================================================== Dell OpenManage Server Agent version: 4.2.1 Release date: December 2000 Supported systems: Dell PowerEdge 1300, 1400, 1550, 2300, 2400, 2450, 4300, 4350, 4400, 6300, 6350, 6400, 6450, 8450 Operating systems: Microsoft Windows NT Server 4.x with Service Pack (SP) 4 or later Microsoft Windows 2000 Server family (includes Windows 2000 Server and Windows 2000 Advanced Server) Novell NetWare 4.x or 5.x ====================================================================== NEW FEATURES FOR 4.2.1 ====================================================================== ----------------------- SUPPORT FOR NEW SYSTEMS ----------------------- Dell OpenManage Server Agent 4.2.1 has added support for the Dell PowerEdge 1550 ====================================================================== RESOLVED ISSUES ====================================================================== ------------------------------------------------------------------- DELL OPENMANAGE IT ASSISTANT UNABLE TO PERFORM REMOTE FLASH BIOS FOR POWEREDGE 300 SERVER ------------------------------------------------------------------- Dell OpenManage Server Agent 4.2.1 enables IT Assistant to perform a remote flash BIOS for the PowerEdge 300 system. ------------------------------------------------------------------- ERROR REPORTING CPU VOLTAGE THRESHOLD VALUES FOR POWEREDGE 8450 SYSTEM WITH CPU SPEED 700 MHZ AND UP ------------------------------------------------------------------- Dell OpenManage Server Agent 4.2.1 reports correct CPU voltage threshold values. ------------------------------------------------------------------- DELL OPENMANAGE SERVER AGENT 4.0 DID NOT IMPLEMENT THE %ALERT PARAMETER CORRECTLY IN LOCAL RESPONSE AGENT ------------------------------------------------------------------- Dell OpenManage Server Agent 4.2.1 correctly parses the %ALERT parameter. The %ALERT parameter can now be located anywhere in the command line and can optionally be enclosed in double quotes when the user wants to pass the alert message to the command line as a single string. ------------------------------------------------------------------- INTERMITTENT INCORRECT FAN PROBE READINGS OF ZERO RPMS CAUSE FAULTY ALERTS TO BE GENERATED. INVALID FAN PROBE READINGS ALSO COMPROMISE USABILITY OF DELL OPENMANAGE SERVER AGENT. ------------------------------------------------------------------- Dell OpenManage Server Agent 4.2.1 prevents false alerts for fan probes based on incorrect readings of fan RPM values. This update also addresses usability issues caused by these incorrect fan RPM values. The incorrect fan RPM readings originate on PowerEdge systems that report systems management information to the management console using the Dell OpenManage Server Agent version 4.0. ------------------------------------------------------------------- SEVEN-CHARACTER SERVICE TAGS DISPLAY INCORRECTLY ------------------------------------------------------------------- Formerly, certain combinations of characters and numbers in the seven-character service tag for your Dell system either did not display correctly or did not display at all. Dell OpenManage Server Agent 4.2.1 displays service tags correctly. ------------------------------------------------------------------- FALSE POWER SUPPLY FAN READINGS. DELL OPENMANAGE SERVER AGENT REPORTS HIGH POWER SUPPLY FAN RPM READINGS. THE READINGS EXCEED THE UPPER FAILURE THRESHOLD AND ARE REPORTED AS FAILURES. ------------------------------------------------------------------- Dell OpenManage Server Agent 4.2.1 corrects the problem of false fan- probe alerts. ################################################################ DELL OPENMANAGE SERVER AGENT 4.2.0 ################################################################ This readme file contains updated information for your "Dell OpenManage Server Agent User's Guide" and any other technical documentation included with this product. ------------ REQUIREMENTS ------------ Release Date: December, 2000 Supported systems: Dell PowerEdge 300, 1300, 1400, 1550, 2300, 2400, 2450, 4300, 4350, 4400, 6300, 6350, 6400, 6450, 8450 Operating systems: Red Hat Linux 7.0 (Kernel version: 2.2.16) SNMP agent: UCD-SNMP version 4.1.2-8smux or later ====================================================================== NEW FEATURES FOR 4.2.0 ====================================================================== Initial release to support Linux. ###################################################################### DELL OPENMANAGE SERVER AGENT 4.1 ###################################################################### ====================================================================== REQUIREMENTS ====================================================================== Dell OpenManage Server Agent version: 4.1 Release date: December 2000 Supported systems: Dell PowerEdge 300 Operating systems: Microsoft Windows NT Server 4.x with Service Pack (SP) 4 or later Microsoft Windows 2000 Server family (includes Windows 2000 Server and Windows 2000 Advanced Server) Novell NetWare 4.x or 5.x ====================================================================== NEW FEATURES FOR 4.1 ====================================================================== ------------------------ SUPPORT FOR NEW SYSTEMS ------------------------ Dell OpenManage Server Agent 4.1 has added support for the Dell PowerEdge 300 ###################################################################### DELL OPENMANAGE SERVER AGENT 4.0 ###################################################################### ====================================================================== REQUIREMENTS ====================================================================== Dell OpenManage Server Agent version: 4.0 Release date: August 2000 Supported systems: Dell PowerEdge 1300, 1400, 2300, 2400, 2450, 4300, 4350, 4400, 6300, 6350, 6400, 6450, 8450 Operating systems: Microsoft Windows NT Server 4.x with Service Pack (SP) 4 or later Microsoft Windows 2000 Server family (includes Windows 2000 Server and Windows 2000 Advanced Server) Novell NetWare 4.x or 5.x ------------------------------------------------------ ====================================================================== NEW FEATURES FOR 4.0 ====================================================================== Initial release of Dell OpenManage Server Agent ======================================================================= 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" and "Pentium" are registered trademarks of Intel Corporation. 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 2002