###################################################################### DELL OPENMANAGE(TM) SERVER ADMINISTRATOR 1.8.1 README ###################################################################### NOTE: This readme provides information for Dell OpenManage Server Administrator version 1.8.1. This file contains updated information for your "Dell OpenManage Server Administrator User's Guide" and any other technical documentation included with Server Administrator. NOTE: See the Dell OpenManage 4.0.1 Application CD install readme (readme_ins.txt) on the "Systems Management" CD for the latest installation information and issues specifically related to Server Administrator. NOTE: See the Dell OpenManage Array Manager readme (located in the "am3xx" directory on the "Systems Management" CD) for supplemental information regarding the Storage Management Service. The Server Administrator documentation includes the "User's Guide", "Messages Reference Guide", "CIM Reference Guide", "Command Line Interface (CLI) User's Guide", "SNMP Reference Guide", and "Compatibility Guide". You can access all the documentation from the product documentation CD or from the Dell Support website at "support.dell.com". This file contains the following sections: * Criticality * Minimum Requirements * Release Highlights * Installation * User Notes * Known Issues ###################################################################### CRITICALITY ###################################################################### 3 - Optional Dell recommends that you review specifics about the update to determine if it applies to your system. The update contains changes that impact only certain configurations, or provides new features that may/may not apply to your environment. ###################################################################### MINIMUM REQUIREMENTS ###################################################################### This section provides information about the minimum requirements for installing and using Server Administrator. ====================================================================== "SYSTEMS MANAGEMENT" CD VERSION 4.0.1 SUPPORTED SYSTEMS ====================================================================== Server Administrator 1.8.1 is supported on "Systems Management" CD version 4.0.1. The following Dell(TM) PowerEdge(TM) systems are supported for "Systems Management" CD version 4.0.1: 1850, 2800, 2850. ====================================================================== SUPPORTED WEB BROWSERS ====================================================================== * Microsoft(R) Internet Explorer 6.0 on Microsoft Windows(R) Server 2003, Windows 2000, and Windows XP PRO * Netscape Navigator 7.02 and 7.1 on Windows 2000, Windows Server 2003, and Windows XP and on Red Hat(R) Enterprise Linux AS, version 2.1 and Red Hat Enterprise Linux (AS, ES, WS) version 3.0 * Mozilla 1.4.1, 1.5, and 1.6 on Red Hat Enterprise Linux AS, version 2.1 and Red Hat Enterprise Linux (AS, ES, WS) version 3.0 NOTE: When using Internet Explorer or Netscape Navigator on systems running Microsoft Windows to view localized versions of the Remote Access Controller's (RAC's) Web-based remote access interface: 1. Open the Windows "Control Panel." 2. Double-click the "Regional Options" icon. 3. Select the desired locale from the "Your locale (location)" drop-down menu. ====================================================================== SUPPORTED RAC FIRMWARE ====================================================================== * On systems with a RAC installed, DRAC 4 firmware version 1.0 or later is required. ###################################################################### RELEASE HIGHLIGHTS ###################################################################### * Added support for Baseboard Management Controller (BMC) * Added support for Platform Event Filtering (PEF) * Added support for Platform Event Destinations ###################################################################### INSTALLATION ###################################################################### For complete installation instructions, see the Server Administrator User's Guide. ###################################################################### USER NOTES ###################################################################### This section provides information to help enhance your experience with Server Administrator in particular implementations and environments. * Server Administrator does not display information related to teaming of NICs. For information on NIC teaming, see the network controller documentation. * If you run a security scanner tool (such as Nessus) against the Server Administrator Web server, certain security warnings against port 1311 running the Server Administrator Web server may be displayed. The following warnings have been investigated by Dell engineering and determined to be "false positives" (invalid security warnings) that you can safely ignore: * "The web server on 1311 allows scripts to read sensitive configuration and / or XML files." Dell has determined that this warning is a false positive. * "The web server on 1311 "allows to delete " / " which implies that the web server will allow a remote user to delete the files in root on the server." Dell has determined that this warning is a false positive. * "The web server on 1311 might be susceptible to a 'WWW Infinite Request' attack." Dell has determined that this warning is a false positive. * "It is possible to make the remote thttpd server execute arbitrary code by sending a request like: GET If-Modified-Since:AAA[...]AAAA Solution: If you are using thttpd, upgrade to version 2.05. If you are not, then contact your vendor and ask for a patch, or change your web server. CVE on this one is CAN-2000-0359". Dell has determined that this warning is a false positive. ====================================================================== NOTES FOR THE INSTRUMENTATION SERVICE ====================================================================== * When modifying the warning threshold settings, the values are stored in the firmware as discrete integer values and scaled for display. Not all values exist, causing the values to change when saved. * Dell MIB Files for PowerEdge Systems: Dell MIB files for PowerEdge systems allow customers to obtain and verify information provided by supported software agents. The current MIB files supported by PowerEdge software agents are located at "\support\dcpemibs" on the "Systems Management" CD. NOTE: A MIB-II-compliant, SNMP-supported network management station is required to compile and browse the MIB files. * Precompiled Kernels Supported by Server Administrator With Prebuilt Device Drivers ----------------------------------------------------- | Operating System | Kernel | ----------------------------------------------------- | Red Hat Enterprise | 2.4.9-e.3 | | Linux 2.1 | 2.4.9-e.3smp | | | 2.4.9-e.3enterprise | | | | ----------------------------------------------------- | Red Hat Enterprise | 2.4.21-4.EL | | Linux 3 | 2.4.21-4.ELsmp | | | 2.4.21-4.ELhugemem | ----------------------------------------------------- ====================================================================== NOTES FOR THE UPDATE SERVICE ====================================================================== * Administrative access is required to carry out a complete inventory of all devices on the system using 'omreport' CLI command. * After starting the Update Service update process, do not navigate to other pages or close the browser. Wait until you see a successful update message before you navigate or close the browser. * The Update Service is currently available only for the Microsoft Windows operating systems supported by Server Administrator. * PERC Device Types: PERC firmware and driver updates from the command line require you to provide a "device" parameter (for example, device=PERC3). Also, administrative access is required to carry out complete inventory of all PERC devices on the system using 'omreport' CLI command. The table below lists the device type that you should use for the various PERC devices. ----------------------------------------- |Device | Device Type | ----------------------------------------- |PERC 3/DC | PERC3 | |PERC 3/DCL | | |PERC 3/QC | | |PERC 3/SC | | ----------------------------------------- |PERC 4/Di | PERC4Di | |PERC 4/SC | PERC4 | |PERC 4/DC | | |PERC 4/IM | | ----------------------------------------- |CERC | CERC | ----------------------------------------- |PERC 2 | PERC2 | |PERC 2/SC | | |PERC 2/DC | | ----------------------------------------- |PERC 2/Si | ROMB | |PERC 3/Si | | |PERC 3/Di | | ----------------------------------------- ======================================================================= NOTES FOR THE DIAGNOSTIC SERVICE ======================================================================= * Do not schedule diagnostics to run in parallel on multiple tape devices. You should also not run diagnostic tests in parallel with SCSI communication tests. For example: if you run diagnostic tests simultaneously for a PV122T autoloader and a VS80 tape drive, one of the tests will fail with the following message: “The DLL required to run the diagnostic is currently being used by another device. Retry the diagnostic after ensuring that the DLL is not being used by other devices.” * The Diagnostic Service supports tests for Remote Access Controllers (RACs). * For a complete list of hardware devices that Server Administrator diagnostics specifically supports, see the "Server Administrator Compatibility Guide". * Array Manager 3.5 or later is required to diagnose RAID attached hard drives when using the Server Administrator Diagnostic Service. If Array Manager 3.5 is not installed, the Elite RAID attached hard-drive tests may not operate properly. * Tape diagnostics should not be run while the system is performing a tape backup. * The Intel management agent is required for the Intel network adapter diagnostics. If this is not installed (or partially installed), only default network diagnostics are available. You can access the Intel PROSet from either the Server Assistant CD (version 8.x or later) or from "support.dell.com". The Intel PROSet is listed under the Intel PRO Family of Adapters. * The Broadcom Management Program (Control Suite) is required for the Broadcom network adapter diagnostics. If this is not installed (or partially installed), only default network diagnostics are available. Use the Server Assistant CD (version 8.x or later) to install the Broadcom Management Program or download the Broadcom drivers from "support.dell.com". If a version of the management program is already installed on your system, you can use the Server Assistant CD to reinstall the program or to update the program to the most current version. * The tg3 driver is not supported by Broadcom NIC vendor diagnostics. Install bcm5700 if Dell Server Assistant CD (version 8.x or later) was not used to install the operating system. * Broadcom Modem diagnostics are not supported on systems running Red Hat Linux operating systems. * The Diagnostic Service does not support the PERC 2/SC and may act unpredictably when a PERC 2/SC is present. * Dell strongly recommends that you maintain RAID controller driver and firmware at their latest versions. Otherwise, you may see unpredictable behavior. For example, when the PERC 3/DI RAID controller firmware is below version 2.7, on a system running Windows, the "Secure PortServer" may fail to start and prevent proper operation of Server Administrator. ====================================================================== NOTES FOR THE REMOTE ACCESS SERVICE ====================================================================== * This service is supported on PowerEdge 1850, 2800, and 2850 systems only. It enables remote access to a server that has lost its network connection or that has become unresponsive. In this release of Server Administrator, the Remote Access Service uses one of the following remote access controllers (RACs): DRAC 4/I. ###################################################################### KNOWN ISSUES ###################################################################### This section provides information on open issues with this release of Server Administrator. ====================================================================== ISSUES FOR SERVER ADMINISTRATOR RUNNING ON ALL SUPPORTED OPERATING SYSTEMS ====================================================================== * On Chinese and Japanese (double-byte) language systems, these elements may appear garbled: * Multibyte user names * Page title * Column headers * Button text on the “Alert Log” page * When running Server Administrator on a system with a Traditional Chinese operating system, the Server Administrator pages are displayed in Simplified Chinese. To view Server Administrator in English, go to your browser language preference page and change the language to English. * When running Server Administrator on a system with a Simplified Chinese or Japanese operating system, the e-mail attachments or update packages must reside in a path containing non-localized characters. * In Server Administrator, you must not open any saved log file (with .zip extension) with the Windows Server 2003 or Windows XP embedded "Compressed (zipped) Folder" utility. Open the file using WinZip or a similar tool to view the complete content (text and images). * On Mozilla version 1.2.1, after you configure Server Administrator to send e-mail and when you click "Email" on any page, the 'To”, 'Subject”, and “Message” fields appear blank even though they are populated with the correct text. The Server Administrator e-mail function works correctly. This issue was not observed on Mozilla 1.0.x browsers. * On the Server Administrator "Update" tab, if you select a package to update, the "Select update package from:" field is blank. The update function works correctly. * After upgrading Red Hat Enterprise Linux 2.1 to Red Hat Enterprise Linux 3, you must uninstall and reinstall Server Administrator to make it work. * On Mozilla or Netscape browsers, if you go to the "System-> Auto Recovery" page of Server Administrator, you must click anywhere on the page before setting the "System Reset Timer (in Seconds)" value. * On Mozilla browsers, the "Close Browser" button on the Server Administrator logout page does not work. Use the browser window "exit" option to exit the browser. * Server Administrator does not support Novell(R) NetWare(R) version 5.1 running with JVM version 1.2.2. If you are using Novell JVM version 1.2.2 for NetWare, you must upgrade to version 1.3.1. Go to the Novell website at "www.novell.com" to get the appropriate version of Novell JVM. * After installation of Server Administrator on certain systems, a second reboot may be required for updated BIOS settings to be properly displayed by Server Administrator. * If you import an invalid root certificate into Server Administrator using "Preferences--> General Settings--> Web Server--> X.509 Certificate" and try to log in to Server Administrator after restarting the Web server, you get a blank page. To correct this issue, you must restore your original "keystore.db" file before importing a valid root certificate. To restore the "keystore.db" file, you must use both the basic operating system commands and the Server Administrator Command Line Interface (CLI). Perform the following steps from your operating system command line: 1. Type: omconfig system webserver action=stop This command stops the Server Administrator Web Server. 2. Locate the "keystore.db.bak" file. The default path is "C:\program files\dell\openmanage\iws\config". 3. Rename "keystore.db.bak" to "keystore.db". 4. Type: omconfig system webserver action=start This command starts the Server Administrator Web Server. * A temperature that drops below a minimum failure threshold does not cause a system reset even if this alert action is set. * Clicking the browser "Back" and "Refresh" buttons may not display the correct page with respect to the Server Administrator component tree, tabs, or tab menus. Example: 1. Click "Main System Chassis" under "System Component Tree". 2. Click "Fans" under "Main System Chassis". 3. Click "Alert Actions" on the tab menu bar. 4. Click the "Back" button on the browser. This action takes you to the "Fan Probes" page, leaving the tab menu bar unchanged. This action places the "Fan Probes" page under "Alert Actions" on the tab menu bar instead of under "Fan Probes". * Selecting the boot sequence under the BIOS "Setup" tab does not re-enable boot devices that have been previously disabled in the System Setup Program. * The links on the Server Administrator home page might lock up after repeated random clicking. To resolve this situation, refresh the browser by pressing or by clicking the browser "Refresh" button. * All unsecure HTTP requests to Server Administrator receive an invalid response. Server Administrator runs only one instance of the Web server, which is secure. Make all connections through https://:. 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". * When setting dates in the "Asset Information" section of the Server Administrator home page, the current time is appended to the date. When setting dates with the Command Line Interface, the appended time is noon. * If Network Adapter Teaming is installed and enabled on your system, Server Administrator does not display the IP address or other connection-related data for the individual network adapters. The connection status and IP address belong to the virtual adapter created by the teaming software. The virtual adapter is not currently displayed in Server Administrator. * For systems running a supported Red Hat Linux operating system, kernel driver messages such as "AAC_ChardevOpen" are sometimes displayed in the console at the log in prompt. These messages are displayed in the console when the driver initialization is delayed by the installation of Server Administrator services and can be safely ignored. * Server Administrator uses port 1311 as default port. 1311 is a registered port number by Dell Inc. If another application is configured to run on port 1311 before Server Administrator is installed, the "secure port server" won't be able to start when the installation completes. Make sure that port 1311 is not being used before installing Server Administrator. * On some systems temperature probe values and settings are only supported for whole degrees, not tenths of a degree. On these systems, setting a fractional value for the minimum warning temperature threshold results in the set value being rounded down to the next whole number value. This behavior may cause the minimum warning threshold to have the same value as the minimum failure threshold. ====================================================================== ISSUES FOR SERVER ADMINISTRATOR RUNNING ON ALL MICROSOFT WINDOWS OPERATING SYSTEMS ====================================================================== * On a Japanese or Chinese Windows system, the path name of a file must not contain any double-byte characters when attaching a file to an e-mail or when validating an update package. * If you change the browser's theme when using Netscape 7.1, some HTML elements, such as radio buttons, may not appear correctly. * Execute all Server Administrator CLI commands from a 32-bit Windows command prompt. Acceptable ways to access the 32-bit command prompt are by clicking "Start-> Programs-> Accessories-> Command Prompt" or by clicking "Start-> Run" and then typing "cmd.exe". Attempts to run the CLI commands from the DOS command "command.com" may produce unpredictable results. * After installing Server Administrator from the command prompt, issuing an "omreport" or "omconfig" command from the same prompt causes an error. You must open a new command prompt and issue commands from the new window. * If the system running Server Administrator is also running the Dell|EMC(R) Navisphere(R) SAN Management application, you may experience problems while using the Navisphere application. If this happens, upgrade the version of Java on the system to JRE 1.4.2. * The secure port server might hang on system startup if both Oracle and VERITAS(R) Backup Exec(TM) are installed on the system. To manually start the secure port server on a system running Windows, click "Start-> Programs-> Administrative Tools-> Service", and then right-click "Secure Port Server" and select "Start". ====================================================================== ISSUES FOR SERVER ADMINISTRATOR RUNNING ON ALL NOVELL NETWARE OPERATING SYSTEMS ====================================================================== * If multiple users pull a large Command / Alert log (over 500 KB) at the same time, the Server Administrator Web connection may time out. You must then log on again to Server Administrator. * If you upgrade the NetWare operating system to a newer version, you must then re-install Server Administrator. * Perform the following steps before applying Service Packs to Novell NetWare operating systems on systems with Server Administrator installed: NOTICE: Stop the Server Administrator Web server before applying Service Packs. Stopping the Server Administrator Web server unloads Java and stops all running Java applications. 1. Unload Java. 2. From the Novell NetWare command console, stop the Server Administrator Web Server. Type: DELL/OMANAGE/IWS/BIN/NETWARE/OMASTOP * If you shut down Server Administrator on a system running NetWare using the "sys:\system\dell\omanage\iws\bin\netware\omastop.ncf" command, the shutdown script unloads the Java Virtual Machine on the NetWare system. As a result, all applications using the Java NetWare Loadable Modules (NLMs) are also shut down. * When Server Administrator executes a "power cycle system" or "reboot system" action, it sets the NetWare 6.5 power management setting, "server power down options" to "off" so that these features behave properly. To set this setting back to "on", you can execute the command "set server power down options = on" on the system console or add this command to "startup.ncf." * When stopping Server Administrator by using OMSTOP at the command line, error messages appear on the screen stating that some NLMs could not be unloaded. ====================================================================== ISSUES FOR SERVER ADMINISTRATOR RUNNING ON THE NOVELL NETWARE 5.1 OPERATING SYSTEM ====================================================================== * When you log into Server Administrator for the first time on a system running NetWare 5.1, the information displayed on the Server Administrator home page might be incomplete. If this occurs, press to refresh the browser window. Complete information for your managed system should now be visible on the Server Administrator home page. * If you receive an "NDSComponentException" message while starting Server Administrator, perform one of the following procedures: - If the default certificate is corrupt or does not exist, see the "Web Server and Security Setup" section of the "Server Administrator User's Guide" to create a new certificate. - If the hostname 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 "hostname" to your system name on the line "nssl.keystore = certificate name - hostname". 3. Open the "server_properties.ini" file in "SYS:\system\dell\OpenManage\IWS\config". 4. Change "certificate name" and "hostname" to your system name on the line "nssl.keystore = certificate name - hostname". * If you receive an "SSLComponentException" message while starting Server Administrator, perform the following steps (not setting "classpath" correctly to "SYS:\java\lib\nssl1.1_exp.jar" might be a reason for this exception): 1. Ensure that "nssl1.1_exp.jar" or "nssl1.1_dom.jar" exists in the "SYS:\java\lib" directory. 2. Set "classpath" to "SYS:\java\lib\nssl1.1_exp.jar" or "SYS:\java\lib\nssl1.1_dom.jar" by typing one of the following commands: envset classpath=$classpath;SYS:\java\lib\nssl1.1_exp.jar envset classpath=$classpath;SYS:\java\lib\nssl1.1_dom.jar NOTE: If the previous solutions do not match your configuration, see the Java SSL FAQ at "developer.novell.com" for solutions that might match your configuration. * When installing Server Administrator on Novell NetWare 5.1 with Java Virtual Machine (JVM) 1.1.7B and Support Pack 3, you might receive a "java.io" exception after you finish the installation and restart the managed system. To correct this issue, go to the Novell support website at "support.novell.com" and download the latest version of JVM 1.1.7B dated after 07/23/2001. The TID number for this incident on the Novell website is 10066646. * If you are using the NOVONYX Web server in NetWare 5.1 with Server Administrator, the Server Administrator Web server may stop responding after some time. To avoid this behavior, ensure that the NOVONYX Web server starts after the Server Administrator Web server by performing the following steps: 1. Find the following line in the "AUTOEXEC.NCF" file: NSWEB This line starts the NOVONYX Web server. 2. Move this line to either the end of the "AUTOEXEC.NCF" file or to another location that is after (below) the following line: SYS:\SYSTEM\DELL\OMANAGE\IWS\BIN\NETWARE\OMASTART.NCF This line starts the Server Administrator Web server. * If you install Server Administrator on a system running NetWare 5.1 and Java 1.1.7B, the Server Administrator pages do not display correctly in Netscape 6.1 or 6.2. * If you install Server Administrator on a system running NetWare 5.1 and Java 1.1.7B, the Server Administrator service may hang if you load ConsoleOne on the NetWare system. You must run the following commands at the NetWare command prompt to restart the server after you have exited from ConsoleOne: SYS:\SYSTEM\DELL\OMANAGE\IWS\BIN\NETWARE\OMASTOP SYS:\SYSTEM\DELL\OMANAGE\IWS\BIN\NETWARE\OMASTART Server Administrator does not support Novell NetWare 5.1 running with JVM version 1.2.2. If you are using Novell JVM version 1.2.2 for NetWare, you must upgrade to version 1.3.1. Go to the Novell website at "www.novell.com" to download the appropriate version of Novell JVM. ====================================================================== ISSUES FOR SERVER ADMINISTRATOR RUNNING ON RED HAT LINUX OPERATING SYSTEMS ====================================================================== * When starting Server Administrator from the Red Hat Linux console, kernel log messages appear. To suppress these messages, perform the following steps: 1. Edit the "/etc/sysconfig/syslog" file and modify KLOGD_OPTIONS to KLOGD_OPTIONS="-c 4". 2. Restart "syslog" by executing "/etc/init.d/syslog restart". * When using the Mozilla browser on Red Hat Linux operating systems, the font and type size on the Server Administrator global navigation bar appear different from the default font and type size that Server Administrator uses. ====================================================================== ISSUES FOR COMMAND LINE INTERFACE ====================================================================== The following are the open issues regarding the Command Line Interface. ---------------------------------------------------------------------- CLI ISSUES FOR ALL OPERATING SYSTEMS ---------------------------------------------------------------------- * For complex "omconfig" CLI commands that contain multiple commands in one command line, the CLI may report a success status for the command even if part of the command failed. The current settings can be confirmed by performing the corresponding "omreport" command. To avoid this issue, run only one command per command line. ====================================================================== ISSUES FOR INSTRUMENTATION ====================================================================== The following are open issues and workarounds, where available, for Server Administrator on systems running Windows 2000, Windows Server 2003, Red Hat Linux, or Novell NetWare operating systems. ---------------------------------------------------------------------- INSTRUMENTATION ISSUES FOR ALL OPERATING SYSTEMS ---------------------------------------------------------------------- * Automatic System Recovery (OS Watchdog) actions may not execute exactly per the set time out period (n seconds) when the watchdog reflects a hung system. The action execution time ranges from n-h+1 to n+1 seconds, where n is the set time out period and h is the heart beat interval. The value of the heart beat interval is 7 seconds when n <= 30 and 15 seconds otherwise. * The functionality of the watchdog timer feature cannot be guaranteed in a case where a multi-bit error occurs in system DRAM Bank_1. If an multi-bit error occurs in this location, it is possible for the BIOS code resident in this space to become corrupted. Because the watchdog feature utilizes a call to BIOS to effect the shutdown or reboot behavior, it is conceivable that the feature will not work properly in this instance. If this occurs, you must manually reboot the system. * The NIC configuration information within the Server Administrator "BIOS Setup" screen may be inaccurate for embedded NICs. Using the Server Administrator "BIOS Setup" screen to enable or disable NICs might produce unexpected results. It is recommended that you perform all configurations for embedded NICs through the actual System Setup screen that is available by pressing while a system is booting. This issue is present in the CLI interface and in IT Assistant. * If a system with spare bank memory enabled enters a "redundancy lost" state, it may not be apparent which memory module is the cause. If you cannot determine which DIMM to replace, see the "switch to spare memory bank detected" log entry in the ESM system log to find which memory module failed. * Warning thresholds that are modified on the following systems are reset to their default values if the system is power cycled or loses AC power: PowerEdge 1850, 2800, and 2850 systems. If you change the warning threshold values and notice that they have been reset to default values after a reboot, then you must add the relevant "omconfig" commands to your system startup sequence. For example, if you want to set the warning thresholds for fan zero to a minimum of 1000 and a maximum of 5300, add the following command to your startup sequence: omconfig chassis fans index=0 minwarnthresh=1000 maxwarnthresh=5300 Ensure that the "omconfig" command is invoked after system services have started. See the "Command Line Interface User's Guide" for more information. * When assigning probe threshold values, Server Administrator sometimes rounds the minimum or maximum values you enter to the closest assignable value. ---------------------------------------------------------------------- INSTRUMENTATION ISSUES FOR WINDOWS 2000 AND WINDOWS SERVER 2003 OPERATING SYSTEMS ---------------------------------------------------------------------- * To use the Instrumentation Service SNMP Subagent with HP OpenView Network Node Manager (NNM) Version 6.1, you must install the HP OpenView consolidated patch that contains the NNM_00496 patch on your system. To download the patch, go to the Hewlett-Packard website at "www.hp.com." * In some circumstances the Server Administrator CIM interface may not be properly registered with the operating system and may not function. To resolve this situation, perform the following steps: 1. Open a command prompt window. 2. Change to the installation directory, which is typically "C:\Program Files\Dell\OpenManage\OMSA\bin." 3. Run the command "regsvr32 dccim32.dll." ---------------------------------------------------------------------- INSTRUMENTATION ISSUES FOR RED HAT LINUX OPERATING SYSTEMS ---------------------------------------------------------------------- * When the OS install mode is on in the BIOS setup, the memory available to the operating system, shown in OMSA GUI or IT Assistant, is the total memory present in the system and not the actual BIOS reported memory. * "Current Speed" and "Minimum Failure" are the only valid fan threshold values for storage systems attached to managed systems running a Red Hat Linux operating system. All other values are displayed as "unknown". * PowerVault 20xS, 21xS, and 22xS storage systems attached to managed systems running a Red Hat Linux operating system cannot be managed by Server Administrator using the following RAID controllers: - PERC 2 - PERC 2/Di - PERC 2/Si - PERC 3/Di - PERC 3/Si ---------------------------------------------------------------------- INSTRUMENTATION ISSUES FOR NOVELL NETWARE OPERATING SYSTEMS ---------------------------------------------------------------------- * When the OS install mode is on in the BIOS setup, the memory available to the operating system, shown in OMSA GUI or IT Assistant, is the total memory present in the system and not the actual BIOS reported memory. * If the storage management service, Array Manager, is installed on a system with NetWare, enter a value of 60 seconds or greater in the System Reset Timer field in System->Properties->Auto Recovery. Choosing a lower value may cause the watchdog to trigger and execute the specified recovery action, which may cause the system to become non-responsive when Array Manager scans for array disks. If Array Manager is not installed, lower values should work. * On managed systems running a Novell NetWare operating system, users must manually disable the watchdog timer feature prior to issuing a "restart server" or "down" command. Otherwise, the watchdog will timeout, resulting in a reboot or power down, depending on the watchdog's selected behavior. * The Instrumentation Service might incorrectly report NetWare version 5.1 as version 5.0. * On managed systems running a Novell NetWare operating system, the Instrumentation Service loads multiple NLMs at system startup. Some NLMs are automatically uninstalled because they are not required on a particular system. The process for uninstalling the NLMs occurs approximately 2 minutes after you boot the system. During this uninstallation process, a module unloading message appears on the Novell NetWare system console. * After installing the Instrumentation Service, the user reboots the system to make the newly installed managed system services available for use. While rebooting, the system might hang if Adaptec CI/O management software is installed. To avoid a hung system during reboot, perform the following steps: 1. Remove "dcstart.ncf" from "autoexec.ncf". 2. After the system reboots, run "dcstart.ncf" from the NetWare command line. NOTE: Adaptec CI/O is not supported on NetWare 6.0. When upgrading a system from NetWare 5.x to NetWare 6.0, uninstall Adaptec CI/O before upgrading the operating system. ====================================================================== ISSUES FOR DIAGNOSTICS ====================================================================== The following subsections list the currently known issues regarding implementation and operation of the diagnostic tests offered in Server Administrator. ---------------------------------------------------------------------- ISSUES FOR ALL OPERATING SYSTEMS ---------------------------------------------------------------------- * When running tests, do not update the NIC drivers. If you do, tests may give unexpected results. * The RAC POST Result test resets the RAC and temporarily disconnects any active sessions or RAC services. As a result, if you run other RAC tests together with this test in multiple passes, some of the passes may fail. * If you are using Server Administrator on a system that is completely isolated on a network (cannot ping any other systems), you may experience performance problems and may receive inconsistent results from the Diagnostics Service if the "Automatically detect settings" checkbox is selected in the Local Area Network proxy settings page of Internet Explorer version 5.5 or earlier. To correct this issue, deselect the "Automatically detect settings" checkbox. * After running a diagnostic test that requires a high percentage of processor resources, you may experience slow browser response time in Netscape 6.2.x. To restore normal browser response time, you must end the Netscape 6.2.x browser process. On systems running Red Hat Linux, locate the process ID for "netstat" and type the "kill -9" command followed by the process ID number. On systems running a Windows operating system, open the "Task Manager" by pressing , select "Netscp6.exe", and click "End Task". * The "Diagnostic Service" tab is not available in Server Administrator and is not listed on the "Health" page at startup. The Diagnostic Service waits for the Server Administrator service to start completely before enumerating (scanning system for available devices to diagnose). If you press to refresh, the "Diagnostic Service" tab displays when enumeration is complete. This process can take several minutes on some systems. The "Diagnostic Service Link" does not work until the "Diagnostic Service" tab is displayed. * If your hard drive becomes full (no space left) and you run diagnostics on the managed system, Server Administrator does not show progress for the running diagnostics; instead, you see a blank page. You cannot cancel the tests because the blank page is shown instead of the progress page with the "Abort" button. To correct this issue, you must free up some space on your hard drive, reboot the system, and run the diagnostics again. * You cannot use Ctrl-C to cancel a CLI session from the console. * When setting the time (hours:minutes) on the scheduler pages, remember that the diagnostic test will run according to the clock on the Server Administrator server, not the clock on your local system. * Scheduled diagnostics are initiated only if the Web server is up and running. Any tasks scheduled in the past, will not run until the next run time. * If the secure web server is shut down when tests are executing (from the UI or CLI), the tests might not complete, since the jvm in which they were executing shuts down along with the server. This behavior is undefined. * Running Intel and Broadcom vendor specific tests interrupts the network connection. After the selected tasks are completed, there is a small delay before the connection resumes. Because of this, the NIC Communication test might return an unusual status when run along with Intel or Broadcom NIC tests. To correct this issue, select the Communication test first or run it separately. * Spare bank memory is not supported on some systems (such as a PowerEdge 2550). As a result, the spare bank fail-over state can not be enabled. On such systems, the Instrumentation Service doesn’t provide a way to check the fail-over state. The Memory Pattern test may pass on such systems because of ECC corrections. * Disconnecting the USB cable when running a diskette test on a USB diskette drive may produce unexpected results. On systems running Red Hat Linux, this may cause the operating system to stop responding. On systems running Windows, the test may never complete. * Port 8000 is the default RMI Registry port used by the Diagnostic Service. Setting this to another port number, which is already in use, does not give a warning. If port 8000 is already used by another application, the Diagnostic Service might not start. To correct this issue, make sure that port 8000 is free, or modify the RMI_PORT value in DiagnosticSettings.properties (installed in /openmanage/oldiags/lib) and restart the "Secure Port Server". * Diagnostics does not prompt you to restart "Secure Port Server" after changing RMI Registry Port in "Diagnostic Application Settings" page (Preference -> Diagnostics). Restart "Secure Port Server" for the changes to take effect. * Parallel port diagnostics support only base address 0x378h. * Diagnostics may report a write-failure, when you run the Format Diagnostic Tape test with new media. If this error occurs, run the test again. ---------------------------------------------------------------------- ISSUES FOR WINDOWS OPERATING SYSTEMS ---------------------------------------------------------------------- * If the Yosemite Tapeware application is installed on your system, the Diagnostic Service cannot discover and run diagnostics on IDE tape drives. To correct this problem, perform the following steps: 1. Locate the TapeWare configuration file. The default location is "C:\Program Files\TapeWare\TapeWare.ini". 2. Find the section in the file called "Configuration". 3. Add the following line to the "Configuration" section. releaseWhenUnused=Yes 4. Save the "TapeWare.ini" file, and reboot the system. * After installing the Server Administrator Diagnostic Service or restarting the Secure Port Server service, the following errors are logged in the Event Viewer System Log by the Removable Storage Service. "Type: Error, Source: DCOM" "Type: Error, Source: Removable Storage Service" These entries are logged because the Diagnostic Service must stop the Removable Storage Service to be able to scan the system for tape devices on which to perform diagnostics. After performing the scan, the Removable Storage Service is restarted. * ATI video tests should not be run from the full screen mode ( or properties) of the Windows command interpreter (cmd.exe). * Diagnostics may display PERC cards and any attached devices even if Array Manager is not installed. When this occurs, it displays some valid and some invalid messages when you run tests on the RAID-attached device. ---------------------------------------------------------------------- ISSUES FOR RED HAT LINUX OPERATING SYSTEMS ---------------------------------------------------------------------- * For Intel network adapters, the "Additional Information" device attribute field listed in the "Configuration" tab may display invalid PCI slot information. * When re-enumeration is in progress, do not restart the Secure Port Server. If you restart the Secure Port Server during re-enumeration, it may not respond properly, and you will need to restart it again. * In console mode (without X-Windows), text appears faint after running ATI video diagnostics from the command line, with the command "omdiag system video". You can restore normal text brightness by running the "clear" command from command line. * After running ATI video diagnostics in the X-Windows environment, a solid black square appears on the screen in the place of the mouse pointer icon. You can clear this by moving the mouse pointer. ====================================================================== ISSUES FOR REMOTE ACCESS ====================================================================== NOTE: The Remote Access Service is supported on PowerEdge 1850, 2800, and 2850 systems only. The following subsections list the currently known issues regarding implementation and operation of your RAC and the Remote Access Service in Server Administrator. ====================================================================== ISSUES FOR UPDATE SERVICE ====================================================================== * When performing a RAC firmware update, make sure that you launch the update process from a single browser instance. If an update is performed from two different browsers at the same time, the update will fail. * Do not close your browser during an update process. If you close your browser while an update process is in progress, the update will fail. You must reboot your system before starting the update again, or the update process will continue to fail. ###################################################################### Information in this document is subject to change without notice. (C) 2004 Dell Inc. All rights reserved. Reproduction in any manner whatsoever without the written permission of Dell Inc. is strictly forbidden. Trademarks used in this text: "Dell", "PowerEdge", "PowerVault", and "Dell OpenManage" are trademarks of Dell Inc.; "Microsoft", "Windows", and "Windows NT" are registered trademarks of Microsoft Corporation; "Novell" and "NetWare" are registered trademarks of Novell, Inc.; "Red Hat" is a registered trademark of Red Hat, Inc. "EMC" and "Navisphere" are registered trademarks of EMC Corporation; "VERITAS" is a registered trademark and "Backup Exec" is a trademark of VERITAS Software Corporation. Server Administrator uses the OverLIB JavaScript library. This library can be obtained from www.bosrup.com. Other trademarks and trade names may be used in this document to refer to either the entities claiming the marks and names or their products. Dell Computer Corporation disclaims any proprietary interest in trademarks and trade names other than its own. July 2004