######################################################################
DELL OPENMANAGE(TM) SERVER ADMINISTRATOR VERSION 1.9.2 README
######################################################################
NOTE: This readme provides information for Dell OpenManage Server
Administrator version 1.9.2.
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 Install 4.2 readme ("readme_ins.txt"),
which is located under the "readme" folder 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
"am" directory on the "Systems Management" CD) for supplemental
information regarding the basic Storage Management Service.
See the Release Highlights section below for more information on
the basic Storage Management Service.
NOTE: See the Dell OpenManage Storage Management readme (located in
the "sm" directory on the "Systems Management" CD) for
supplemental information regarding the enhanced Storage
Management Service. See the Release Highlights section below for
more information on the enhanced 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
* History
######################################################################
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.2 SUPPORTED SYSTEMS
======================================================================
Server Administrator 1.9.2 is supported on "Systems Management" CD
version 4.2.
The following Dell(TM) PowerEdge(TM) systems are supported for
"Systems Management" CD version 4.2: 350, 500SC, 600SC, 650, 700, 750,
800, 1400, 1400SC, 1500SC, 1550, 1600SC, 1650, 1655MC, 1750, 1800,
1850, 2400, 2450, 2500, 2550, 2600, 2650, 2800, 2850, 4400, 4600,
6400, 6450, 6600, 6650, and 8450.
The following Dell PowerVault(TM) systems are supported for "Systems
Management" CD version 1.2: 750N, 755N, 770N, and 775N. "Systems
Management" CD version 1.2 is preinstalled on version 2.3.7.0 of the
PowerVault NAS operating system.
======================================================================
SUPPORTED OPERATING SYSTEMS
======================================================================
* Microsoft Windows 2000 Server family (includes Windows
2000 Server, Windows 2000 Advanced Server, and Windows
2000 Small Business Server [SBS])
* Microsoft Windows Server 2003 family (includes Web,
Standard, and Enterprise editions) and Windows Server
2003 SBS
* Red Hat Enterprise Linux (AS, ES, and WS), version 2.1
Update 3)
* Red Hat(R) Enterprise Linux AS (version 2.1 Gold)
* Red Hat Enterprise Linux (AS and ES), version 3
* Novell NetWare, version 5.1 (with Service Pack 5 or later)
* Novell NetWare, version 6.5
======================================================================
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
======================================================================
SUPPORTED RAC FIRMWARE
======================================================================
* On systems installed with a DRAC 4/I and DRAC 4/P firmware version
1.0 or greater, RAC firmware version 3.20 or greater is required
for DRAC III, DRAC III/XT, ERA, and ERA/O.
######################################################################
RELEASE HIGHLIGHTS
######################################################################
* The following Diagnostic issues have been fixed in this release:
- Diagnostics reported a write-failure when the Format
Diagnostic Tape test was run with new media.
- Running Intel(R) and Broadcom vendor-specific tests interrupted
the network connection.
######################################################################
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 might 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.
* 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.
======================================================================
NOTES FOR THE INSTRUMENTATION SERVICE
======================================================================
* User-defined thresholds for backplane probes are reset to their
default values every time a reboot occurs on these PowerEdge
systems: 2400, 2450, 2500, 2550, and 4400. Main board probes on
these systems retain the last user-defined values every time a
reboot occurs.
* User-defined thresholds set under Server Administrator 1.1 become
the default thresholds after installing subsequent versions.
After you change the threshold value of a probe on a system running
Server Administrator 1.1 or earlier and then upgrade to Server
Administrator 1.2 or later, the changed threshold value becomes the
default threshold value.
* 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.
* 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 |
-----------------------------------------------------
The prebuilt device drivers for the Red Hat Enterprise Linux kernels
listed in the table typically support the kernels with the
corresponding kernel configuration in the Red Hat Enterprise Linux
updates that are released by Red Hat.
======================================================================
NOTES FOR THE UPDATE SERVICE
======================================================================
* Administrative access is required to perform a complete inventory
of all devices on the system using the "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). 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 | PERC4IM |
-----------------------------------------
|CERC | CERC |
-----------------------------------------
|CERCSATA2 | CERCSATA2 |
-----------------------------------------
|PERC 2 | PERC2 |
|PERC 2/SC | |
|PERC 2/DC | |
-----------------------------------------
|PERC 2/Si | ROMB |
|PERC 3/Si | |
|PERC 3/Di | PERC3DI |
-----------------------------------------
|PERC 4e/DC | PERC4E |
|PERC 4e/Si | |
|PERC 4e/Di | |
-----------------------------------------
=======================================================================
NOTES FOR THE DIAGNOSTIC SERVICE
=======================================================================
* See the Dell OpenManage Storage Management readme (located in the
"sm" directory on the "Systems Management" CD) for minimum controller
firmware and driver requirements.
* The memory diagnostic is not supported on PowerEdge "x8xx" systems
running Red Hat Enterprise Linux 3.0 (kernel version 2.4.21 or
above).
* The memory diagnostic test uses a lot of system resources. As a
result, the system might become unresponsive when the memory
diagnostic test is run under stress for an extended period of time.
It is strongly recommended that these diagnostics are run after
closing all other applications, and in a nonproduction environment.
If possible, the target system should also be brought off the
critical load.
* Any previously scheduled tasks, hardware changes history, or result
history from Server Administrator 1.8 or earlier will not be
preserved when Diagnostic Service is upgraded from an earlier
release to the current release (Server Administrator 1.9.2).
* Do not schedule diagnostics to run in parallel on multiple tape
devices. Also, do not run diagnostic tests in parallel with
SCSI communication tests.
For example, if you run diagnostic tests simultaneously for a
PowerVault 122T 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."
* For a complete list of hardware devices that Server Administrator
diagnostics specifically supports, see the "Server Administrator
Compatibility Guide".
* On PowerEdge systems running Windows, Array Manager 3.6 or later or
the enhanced Storage Management Service is required to diagnose
Adaptec RAID-attached hard drives when using the Diagnostics Service.
If neither Array Manager nor the Storage Management Service is
installed, the Adaptec RAID-attached hard-drive tests may not
function properly.
* Ensure that all tape backup services are stopped before executing
tape diagnostics. Having tape backup services running while
executing tape diagnostics may cause unpredictable behavior. The
device may show unknown status when enumerated.
* The Intel management agent is required for the Intel network adapter
diagnostics. If this agent 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.
* Broadcom Modem diagnostics are not supported on systems running
Red Hat Enterprise Linux operating systems.
* The Diagnostic Service does not support the PERC 2/SC and may behave
unpredictably when a PERC 2/SC is present.
* Dell strongly recommends that you maintain RAID controller drivers
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.
* You cannot use <Ctrl-C> to cancel a CLI session from the console.
However, tests started from the CLI can be aborted using the "Abort"
link in the "Diagnostic Status" page in the GUI.
* 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.
======================================================================
NOTES FOR THE STORAGE MANAGEMENT SERVICE
======================================================================
* When using the enhanced Storage Management Service, the Systems
Management Data Manager must first be stopped before any Adaptec
controllers are updated.
* Detailed information on the Storage Management Service log is
available in the online help, which is accessed by clicking "Help"
on the global navigation bar. The enhanced Storage Management
Service provides additional help, which is available when the
Storage or lower-level tree object is selected.
======================================================================
NOTES FOR THE REMOTE ACCESS SERVICE
======================================================================
* This service is supported on PowerEdge 650,700, 750, 800, 1600SC,
1650, 1750, 1800, 1850, 2600, 2650, 2800, 2850, 4600, 6600, and 6650
systems only. It enables remote access to a server that has lost its
network connection or that has become unresponsive. In this release
of Server Administrator, the Remote Access Service uses the
following remote access controllers (RACs): Dell Remote Access Card
(DRAC) 4/I, DRAC 4/P, DRAC III, DRAC III/XT, Embedded Remote Access
(ERA), or Embedded Remote Access Option (ERA/O).
* RACs also have their own CLI that is accessed through the "racadm"
command. You can add racadm commands to a batch or script file to
automate various user tasks. To limit the stress load on the managed
system and RAC, you should add "sleep" or "delay" commands of one or
two seconds between the individual racadm commands.
* DRAC 4 is not supported by the Server Administrator 4.1 CLI. For CLI
DRAC 4 reporting and configuration, use the "racadm" command.
* Server Administrator 4.2 does not include software for DRAC II.
However, the DRAC II software can be installed by either installing
Server Administrator 3.8 or earlier and then upgrading to Server
Administrator 4.1, or by installing Server Administrator 4.2 and
then installing the DRAC II software separately from Server
Administrator 3.8 or earlier.
To install the DRAC II software for the managed system, run
"setup.exe" from the "drac25\server" directory on the "Systems
Management" CD (previously called the "Dell OpenManage Applications"
CD.
To install the DRAC II software for the management station, run
"setup.exe" from the "drac25\clientms" directory on the "Systems
Management" CD (previously called the "Dell OpenManage Applications"
CD.
Note: The DRAC II stand-alone installer does not prompt the user
to reboot the system. A manual reboot must be performed after
installing the DRAC II software.
* After installing Internet Explorer 5.0 or later, you may notice that
the automatic configuration and proxy setting information for each
connection is separate from the same information used for the LAN
connection. If you have both a dial-up and a LAN connection at the
same time, Internet Explorer may block your access to the Internet.
This blocking occurs because each connection in Internet Explorer
5.0 uses its own automatic configuration and proxy settings. When
this occurs and a user tries to establish any kind of PPP
connection, Internet Explorer attempts to use the dial-up
connection settings to access the Internet.
You can find additional information about this issue in article
Q236920, "Connections No Longer Use LAN Automatic Configuration
and Proxy (Q236920)" in the Microsoft Knowledge Base at
"support.microsoft.com".
To correct this problem, you must apply Microsoft IE HotFix
Q818060 or KB839571 to either Internet Explorer 5.01 SP2 or
6.0 SP1. HotFix Q818060 and KB839571 are available on the
"Systems Management" CD in the "\support\Windows\HotFix" directory.
Refer to the following Microsoft support articles for further
instructions for applying this HotFix:
(Windows 2000 Server) http://support.microsoft.com?kbid=818060
(Windows 2003 Server) http://support.microsoft.com/kb/839571
As explained in the Microsoft KB article, use the Registry
Editor ("regedit.exe") to browse to the following key:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion
\Internet Settings\
If not present, create a registry item called
"DialupUseLanSettings" and set a value of "1". Make sure the value
type is "DWORD".
Note: HotFix Q818060 may still fail to install on Internet Explorer
6.0 SP1. If the error "This update requires Internet Explorer 6.0
SP1 to be installed" occurs, follow these instructions:
1. Unzip "Q818060-Eng-IE6.zip".
2. From a Windows command shell, enter "Q818060.exe /C" to
extract the HotFix files to a directory.
3. In the command shell, switch to the directory and then enter
"ieupdate.exe Q818060".
4. Launch Internet Explorer, open the "Help" menu, and select
"About Internet Explorer". Verify that "Q818060" appears in
the "Update Versions" field.
######################################################################
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
======================================================================
* When entering an IP address with 255 in the 4th term you
will receive an "invalid IP address" error even if the address
is valid. The error is correctly reported for class-C IP
addresses. A popup will incorrectly occur on some valid
class-A and class-B IP addresses ending in 255. To avoid this
issue, choose another valid address that does not end with 255.
* If the command log page in the Server Administrator GUI
displays an error message indicating that the XML is
malformed, you must clear the command log from the
CLI using the command "omconfig system cmdlog action=clear".
* While browsing through ITA when the SNMP protocol
is disabled and the CIM protocol is enabled, the redundancy
status is shown as lost even though the system has full
redundancy. To confirm the correct state of the system, use
the Server Administrator user interface.
* Onselect PowerEdge x400 generation systems running Red Hat
Linux, issuing a host control command to shut down and power
off the system may not shut down the system properly. This
occurs when there are hung processes in the system that prevent
the operating system from cleanly shutting down the system
before powering off. On a subsequent boot, you can safely
ignore the following message if it appears on the system
console: "Your server appears to have shut down unclearly,
press Y within 'n' seconds to force file system integrity check".
* If you have a RAID 1 virtual disk on a CERC SATA1.5/6ch
controller, performing a Format or Split Mirror operation
may fail. Dell is working to resolve this problem.
* On the "Server Preferences" page in the Server Administrator
user interface, the "IP addresses to Bind to" option can either
be set to bind all IP addressed or only one IP address.
* When issuing the Server Administrator command line "ompreport
system version –outc <filename>", be sure to specify an absolute
path name for the output file, for example, "c:\out.txt" otherwise
the output file will be empty.
* Attempting to modify the BIOS setting ROMB (RAID on Motherboard) to
"RAID" or to "SCSI" may cause the Systems Management
Data Manager to stop running. Setting to "Off" is not affected.
The workaround is to modify the file "dctkst32.ini" under the
directory "<OpenManageInstallPath>\omsa\ini" by changing
the entries "BSETP.ROMBChannel.1" to
"BSETP.ROMBChannel.2" and "BSETP.ROMBChannel.0"
to "BSETP.ROMBChannel.1". Ensure that the change is done
in this order to avoid confusion. Reboot the system for the
changes to take effect.
* The online help for "Network Interface Cards" incorrectly states
that "Disabled" is a valid state for "Connection Status". However,
the message display in the GUI will be "Driver not installed or
is not functioning" since the NIC driver is not active.
* A Server Administrator Command Log entry is not created when
You perform a "BMC Reset to Defaults" in Server Administrator.
However, a BMC reset is usually followed by other BMC
configurations, which are logged.
* When trying to create a new BMC user having a duplicate
username, an error message "Error! This function is not supported
on this system." is displayed instead of indicating that a
duplicate username already exists
* The following four hyperlinks on the "System->System Summary" page
of Server Administrator may not work under certain conditions on
systems using Mozilla or Netscape browsers: "System", "Main system
chassis", "Network Data", and "Software Profile".
* When reinstalling or upgrading Server Administrator, all currently
installed services including Array Manager will be replaced with
the service version qualified with the Server Administrator product
being installed. This behavior is generic across supported
operating systems. A warning on the screen is not provided for
Novell(R) Netware(R) users during the installation process.
* 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.
* 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 non-English
operating system, the e-mail attachments, applications to be
executed for alert management, or update packages must reside in
a path containing nonlocalized 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 NetWare 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 installing Server Administrator on certain systems, a second
reboot may be required for updated BIOS settings to be properly
displayed by Server Administrator.
* PowerEdge 4600 systems with BIOS revisions A08 or higher cannot
be downgraded using the Server Administrator Update Service. To
downgrade to an earlier BIOS version, you must use the diskette
method. BIOS updates in diskette format are available from the Dell
Support website at "support.dell.com".
* 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 CLI. Perform the following
steps from your operating system command line:
1. Type:
omconfig system webserver action=stop
2. Locate the "keystore.db.bak" file. The default path is
"C:\program files\dell\openmanage\iws\config".
3. Copy "keystore.db.bak" to "keystore.db".
4. Type:
omconfig system webserver action=start
* A temperature that drops below a minimum failure threshold does not
cause a system reset even if this alert action is set.
* A reporting error for the amount of memory enabled may exist for the
Level 2 (L2) cache memory when you view "Processors" for PowerEdge
6600 and 6650 systems. When you use the "Server Administrator System
--> Main System Chassis--> Processor interface" and click the
connector name for "Proc_n", where "n" can be from 1 to 4, depending
on the number of processors installed, the L2 cache may be displayed
incorrectly as 256 KB.
If you purchased more than 256 K of L2 cache with your system, all
of the L2 cache you have installed is fully enabled. The reporting
error will be corrected in a future BIOS release for PowerEdge 6600
and 6650 systems.
* Clicking the browser "Back" and "Refresh" buttons may not display
the correct page with respect to the Server Administrator component
tree, tabs, tab menus, or help. Server Administrator has been
designed with limited functionality to reduce overhead. Full feature
capabilities of the Web browser such as "Back", "Refresh", and
"Open in New Window" may not be supported.
Example:
1. Click "Main System Chassis" under "System Component Tree".
2. Click "Fans" under "Main System Chassis".
3. Click "Alert Actions" on the tab menu bar.
4. Click the "Back" button on the browser.
This action takes you to the "Fan Probes" page, leaving the tab
menu bar unchanged. This action places the "Fan Probes" page
under "Alert Actions" on the tab menu bar instead of under
"Fan Probes".
* Selecting the boot sequence under the BIOS "Setup" tab does not
re-enable boot devices that have been previously disabled in
the System Setup Program.
* The links on the Server Administrator home page might lock up after
repeated random clicking. To resolve this situation, refresh the
browser by pressing <F5> or by clicking the browser "Refresh"
button.
* All unsecure HTTP requests to Server Administrator receive an
invalid response. Server Administrator runs only one instance of
the Web server, which is secure. Make all connections through
https://<ip address> : <port number>. Any http://<ip address> :
<port number> request for connection with the server receives an
invalid response.
* If the browser used with Server Administrator indicates that it
cannot display a page or perform an action, ensure that the browser
is in online mode. To go online, perform one of the following steps:
- If you are using Netscape Navigator, click "File" on the menu
bar, point to "Offline", and select "Work Online".
OR
- If you are using Internet Explorer, click "File" on the
menu bar and deselect the "Work Offline" option. When "Work
Offline" is selected, a check displays to the left of the option
on the "File" menu.
* If you are using Netscape Navigator and you receive the error
message "Netscape was unable to connect to the network because you
are offline...", Server Administrator is in offline mode. Go online
to avoid this message.
* If Internet Explorer prompts you to "Work Offline", "Connect", or
"Try Again", always select "Connect" or "Try Again". Do not select
"Work Offline".
* 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 CLI, 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 Enterprise Linux operating
system, kernel driver messages such as "AAC_ChardevOpen" are
sometimes displayed in the console at the login prompt. These
messages are displayed in the console when the driver initialization
is delayed by the installation of Server Administrator services and
can be safely ignored.
* Server Administrator uses port 1311 as the default port. 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 MICROSOFT WINDOWS 2003
OPERATING SYSTEMS
======================================================================
* When running Server Administrator on Windows 2003 Small Business
Server Edition, the "Export" function will display the export file
in the browser window, instead of prompting the user to "open" or
"save" the export file.
* When running Server Administrator, crypt32.dll errors may be written
to the OS Application Event log. This issue occurs due to the
"Update Root Certificates" component, which is installed by default
as part of Windows Server 2003 installation. For more information
on this component and why the errors are generated, see the
following articles on the Microsoft website:
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/
technologies/security/ws03mngd/04_s3cer.mspx
http://support.microsoft.com/default.aspx?scid=kb;en-us;317541
There are two options to avoid these errors from being written to
the Event log:
* Uninstall the "Update Root certificates" component as detailed
in the first knowledge base article mentioned above.
Note: This procedure may affect other programs as discussed in
the article.
* Install the Server Administrator certificate as a trusted
certificate.
Note: This procedure may still prompt you to accept the
certificate when you log on to Server Administrator, but
will prevent the crypt32 errors from being logged to the
Event log.
======================================================================
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 reinstall 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 NetWare command console, stop the Server Administrator
Web Server by typing the following command:
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 issue occurs,
press <F5> to refresh the browser window. Complete information for
your managed system should now be visible on the Server
Administrator home page.
* If you receive an "NDSComponentException" message while starting
Server Administrator, perform one of the following procedures:
- If the default certificate is corrupt or does not exist, see the
"Web Server and Security Setup" section of the "Server
Administrator User's Guide" to create a new certificate.
- If the host name is not present in "client_properties.ini" and
"server_properties.ini", perform the following steps:
1. Open the "client_properties.ini" file in
"SYS:\system\dell\OpenManage\IWS\config".
2. Change "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 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 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 ENTERPRISE LINUX
OPERATING SYSTEMS
======================================================================
* For Red Hat Linux 2.1 installations, Server Assistant
supports the following two options for Firewall settings:
none and enabled.
* The tg3 driver is not supported by Broadcom NIC vendor diagnostics.
Hence, Server Administrator will not run on a Linux system having
a tg3 driver. Install bcm5700 if the "Server Assistant" CD (version
8.x or later) was not used to install the operating system.
* The Server Administrator may not start if a feature of the product
is being executed while at the same time Server Administrator
installation/upgrade is taking place.
* When starting Server Administrator from the Red Hat Enterprise 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 Enterprise 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 STORAGE MANAGEMENT SERVICE
======================================================================
The following are the open issues regarding the Storage Management
Service.
----------------------------------------------------------------------
STORAGE MANAGEMENT SERVICE ISSUES FOR ALL OPERATING SYSTEMS
----------------------------------------------------------------------
* When issuing certain "omconfig storage" CLI commands with "Power
User" privileges, the message "Error! User has insufficient privileges
to run command: omconfig" may occur. You must be logged in with an
Administrator account to perform these actions.
* Invalid "Format and Check Consistency" options are displayed
for a regenerating virtual disk. When an array disk in a virtual
disk is rebuilding, the virtual disk changes to a "Regenerating"
state. The Format and Check Consistency operations should not
be performed on a virtual disk that is in a Regenerating state.
However, the task drop-down menu for a Regenerating
RAID 1-concatenated virtual disk may display the "Format and
Check Consistency" options. Dell is working to resolve this
problem.
* On a system running Red Hat Enterprise Linux 2.1, the Storage
Management Service may incorrectly generate alert 2168
even though the aic7xxx non-RAID SCSI driver is not
loaded nor required. Alert 2168 states the following: "The
non-RAID SCSI driver version is older than the minimum
required level. See the "readme.txt" file for the validated
driver version." You can disregard alert 2168. Dell is
working to resolve this problem
* If an array disk in a RAID 1-concatenated virtual disk fails,
the virtual disk is in a "Degraded" state. Rebooting the system
may cause the virtual disk to change to a "Failed" state yet the
virtual disk is still fully operational and can be restored to "OK"
status once a functional array disk is added back to the RAID-1 set.
Dell is working to resolve this problem
* Using the Storage Management Service Advanced Create VDisk Wizard
may occasionally result in a vertical scrollbar of less than normal
width. If this occurs, resizing the Server Administrator window will
cause the vertical scrollbar to be redrawn correctly.
* When renaming a virtual disk using the GUI, if a name contains
multiple consecutive blank spaces, they are truncated to a single
space after "Apply" is clicked. This issue is due to browser
rendering.
* When the "Open in a New Window" option is selected in the Storage
Management Service Advanced Create VDisk Wizard, the current page
is opened in a new window, rather than launching the selected
option. The web browser has been designed with limited functionality
to reduce overhead.
----------------------------------------------------------------------
STORAGE MANAGEMENT SERVICE ISSUES FOR RED HAT ENTERPRISE LINUX
OPERATING SYSTEMS
----------------------------------------------------------------------
* If an array disk in a RAID 1-concatenated virtual disk fails,
the virtual disk is in a Degraded state. The Check Consistency
operation should not be performed on a virtual disk while it
is in a Degraded state. However, the task drop-down menu
for a Degraded RAID 1-concatenated virtual disk may
display the "Check Consistency" option. Do not perform a consistency
check until after appropriate actions are performed to restore the
virtual disk. Dell is working to resolve this problem.
* With Chinese or Japanese language browser settings, using the
Storage Management Service Advanced Create VDisk Wizard may
occasionally result in text overflowing the bottom of the
side-by-side blue text boxes.
======================================================================
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 Enterprise Linux, or NetWare operating systems.
----------------------------------------------------------------------
INSTRUMENTATION ISSUES FOR ALL OPERATING SYSTEMS
----------------------------------------------------------------------
* There is no Server Administrator Command Log entry when performing
a BMC Reset to Defaults in Server Administrator. However, a BMC
reset is usually followed by other BMC configurations, which are
logged.
* On systems with an onboard LSI 1030 Ultra 320 SCSI Controller,
Server Administrator may report this device as a "Dell PERC 4
Controller" in the Slots information page. The workaround is to
modify the file "dcpcidev.txt" under the directory
"<OpenManageInstallPath>\omsa\ini" by adding a line with the value
"S0183 LSI Logic 1030 Ultra320 SCSI Adapter" before the line
containing the value "S018A PERC 4/im". Restart the Systems
Management Data Manager service for the changes to take effect.
* Attempting to modify the BIOS setting onboard ROMB to "RAID" or to
"SCSI" may cause the Systems Management Data Manager to stop running.
Setting to "Off" is not affected. The workaround is to modify
the file "dctkst32.ini" under the directory "<OpenManageInstallPath>
\omsa\ini" by changing the entries "BSETP.ROMBChannel.1" to
"BSETP.ROMBChannel.2" and "BSETP.ROMBChannel.0" to
"BSETP.ROMBChannel.1". Ensure that the change is done in this order
to avoid confusion. Reboot the system for the changes to take
effect.
* 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
heartbeat interval. The value of the heartbeat 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 multibit error occurs in system DRAM Bank_1. If
a multibit 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 <F2> while a
system is booting. This issue is present in the CLI interface and
in IT Assistant.
* When assigning probe threshold values, Server Administrator
sometimes rounds the minimum or maximum values you enter to the
closest assignable value.
* The "Slots Information" pages in Server Administrator and IT
Assistant sometimes do not include the PERC 3/Di for the PowerEdge
system even when the PERC 3/Di is present on the system. The RAID
controller is still functional and working properly.
* If a system with spare bank memory enabled enters a "redundancy
lost" state, it may not be apparent which memory module is the
cause. If you cannot determine which DIMM to replace, see the
"switch to spare memory bank detected" log entry in the ESM system
log to find which memory module failed.
* Setting any warning threshold to a default value is not supported
on PowerEdge 1650, 2600, 2650, 4600, 6600, and 6650 systems.
Attempting to do so results in an error message.
* Warning thresholds that are modified on the following systems are
reset to their default values if the system is power cycled or loses
AC power: PowerEdge 1650, 2600, 2650, 4600, 6600, and 6650 systems.
If you change the warning threshold values and notice that they have
been reset to default values after a reboot, then you must add the
relevant "omconfig" commands to your system startup sequence. For
example, if you want to set the warning thresholds for fan zero to a
minimum of 1000 and a maximum of 5300, add the following command to
your startup sequence:
omconfig chassis fans index=0 minwarnthresh=1000 maxwarnthresh=5300
Ensure that the "omconfig" command is invoked after system services
have started. See the "Command Line Interface User's Guide" for more
information.
----------------------------------------------------------------------
INSTRUMENTATION ISSUES FOR WINDOWS 2000 AND WINDOWS SERVER 2003
OPERATING SYSTEMS
----------------------------------------------------------------------
* While browsing through ITA when the SNMP protocol is disabled and
the CIM protocol is enabled, the redundancy status is shown as lost
even though the system has full redundancy. To confirm the correct
state of the system, use the Server Administrator User Interface.
* When specifying alert actions, Visual Basic scripts are not
automatically interpreted by the Execute Application feature,
although you can run a ".exe", ".com", ".bat", or ".cmd" file by
only specifying the file as the alert action.
To resolve this issue, first call the command processor "cmd.exe" to
start your script. For example, the alert action value to execute an
application can be set as follows:
c:\winnt\system32\cmd.exe /c d:\example\example1.vbs
where d:\example\example1.vbs is the full path to the script file.
Note: The full path to both the "cmd.exe" file and your script file
should be specified.
* 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 ENTERPRISE LINUX OPERATING SYSTEMS
----------------------------------------------------------------------
* On ESM2 and TVM platforms, issuing a host control command to
shut down and power off the system may not shut down the system
properly. This occurs only when there are hung processes in the
system - hence, the OS cannot cleanly shut down the system before
powering off. In this situation, on a subsequent OS boot, ignore the
following message that may appear on the system console: "Your
server appears to have shut down unclearly, press Y within 'n'
seconds to force file system integrity check."
* When the OS install mode is on in the BIOS setup, the memory
available to the operating system, shown in Server Administrator GUI
or IT Assistant, is the total memory present in the system and not
the actual BIOS reported memory.
----------------------------------------------------------------------
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 Server Administrator 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
nonresponsive when Array Manager scans for array disks. If Array
Manager is not installed, lower values should work.
* On managed systems running a NetWare operating system, users must
manually disable the watchdog timer feature before issuing a
"restart server" or "down" command. Otherwise, the watchdog will
time out, 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 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
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 "omstart.ncf" from "autoexec.ncf".
2. After the system reboots, run "omstart.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
----------------------------------------------------------------------
* Running an array disk test on a hard drive designated as a "hot
spare" when the array virtual disk set goes into a degraded state
and allocates the hot spare may generate the event message "Test was
aborted by the user". If this event is generated, wait until the hot
spare finishes rebuilding its data and then run the array disk test
again on the hot spare.
* When running tests, do not update the NIC drivers. If you do, tests
may produce unexpected results.
* The RAC POST Result test resets the RAC, temporarily disconnecting
any active sessions or RAC services. Because the RAC does not
immediately come back to its original state after a reset, when other
RAC tests are run 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"
check box 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" check box.
* 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
<Ctrl><Alt><Del>, 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 <F5> 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.
* Scheduled diagnostics are only initiated 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 Port Server" is shut down when tests are executing
(from the GUI or CLI), the tests might not complete because the jvm
in which they were executing shuts down along with the server. This
behavior is undefined.
* Spare bank memory is not supported on some systems (such as a
PowerEdge 2550). As a result, the spare bank fail-over state cannot
be enabled. On such systems, the Instrumentation Service does not
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 Enterprise Linux, the operating system may 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 produce 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 <installation dir>/openmanage/oldiags/lib) and restart the Secure
Port Server.
* Parallel port diagnostics only support base address 0x378h.
* When a device is removed from the system or disabled from BIOS and
a re-enumerate is performed, or when the system comes up, the
device name and description of the removed hardware on the
"Diagnostic Hardware Change History" page may display incomplete
information.
* If the RMI port is changed in the "Diagnostic Application Settings"
page ("Preference -->Diagnostics"), the change does not take effect
until the Secure Port Server is restarted. However, there is no
option to restart the Secure Port Server from the "Diagnostics
Application Settings" page.
To correct this issue, restart the Secure Port Server manually
using the Windows Services or the "service omawsd restart" command
on systems running Red Hat Enterprise Linux.
----------------------------------------------------------------------
ISSUES FOR WINDOWS OPERATING SYSTEMS
----------------------------------------------------------------------
* When the RAC In-Band Access test and the RAC Post Result test are
run at the same time, the In-Band Access test may fail
intermittently as there is not enough time for the Remote Access
Service to recover from the Post Result test. Hence, it is
recommended that the In-Band Access test be run after the Post
Result test is complete.
* Performing a hard-drive blink test fails under the following
configuration:
- PERC4DC - Cluster mode
To correct this issue, click "Re-enumerate" in the "Diagnostics
Selection" page and then run the test again.
* 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.
* Diagnostics may display PERC cards and any attached devices even if
Array Manager is not installed. When this issue occurs, it displays
some valid and some invalid messages when you run tests on the
RAID-attached device.
* If a network adapter is disabled and enabled, or diagnostics are run
and the Secure Port Server is restarted, the NICs may not be
available in the "Diagnostic Selection" page, as approximately 30
seconds are needed for the adapter to come back to the active state.
Therefore, diagnostic tests won’t be listed if enumerated
immediately.
To resolve this issue, wait approximately 30 seconds before
starting the Secure Port Server or re-enumerating from the
"Diagnostic Selection" page.
----------------------------------------------------------------------
ISSUES FOR RED HAT ENTERPRISE LINUX OPERATING SYSTEMS
----------------------------------------------------------------------
* On PowerEdge 6400 systems, the onboard Intel NIC is incorrectly
displayed as "Dell Computer Corporation PowerEdge 2550" on the
Diagnostic Selection and other pages. However, this does not
impact any functionalities of the NIC.
* Running the CD/DVD diagnostics on an audio CD in a bus-powered USB
CD drive will cause the system to hang. This is caused by a known
issue with the USB driver that is installed with Red Hat Enterprise
Linux 2.1 as well as Red Hat Enterprise Linux 3 Gold. This issue has
been resolved in the Red Hat Enterprise Linux 3 Update 2.
* When running the Floppy Extremity test on a USB floppy device, the
test will pass in certain conditions when there is no medium present
in the drive.
* For Intel network adapters, the "Additional Hardware Information"
under "Device Information" listed in the "Diagnostic Result History –
Result Details" or "Diagnostic Review Selection Details" page 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.
* Running the CD/DVD Read Exerciser test on a bad CD medium may cause
the test to run for a longer than normal duration. To shorten the
test duration, run the test with the "Halt Execution of Test on
First Error" option selected or in "Quick Test" mode from the
"Diagnostic Test Execution Settings" page. The test can also be
aborted by clicking the "Abort" link in the "Diagnostic Status"
page.
======================================================================
ISSUES FOR REMOTE ACCESS
======================================================================
NOTE: The Remote Access Service is supported on PowerEdge 650, 700,
750, 800, 1600SC, 1650, 1750, 1800, 1850, 2600, 2650, 2800,
2850, 4600, 6600, and 6650 systems only.
The following subsections list the currently known issues regarding
implementation and operation of your RAC and the Remote Access Service
in Server Administrator.
----------------------------------------------------------------------
ISSUES FOR THE DRAC 4
----------------------------------------------------------------------
* If you installed Server Administrator on a system with a
DRAC 4, but you do not see the "Remote Access Controller"
properties tab in the Server Administrator user interface,
perform the following steps:
1. Make sure that the "Remote Access" service is running.
2. Refresh the Server Administrator user interface.
If the "Remote Access Controller" properties tab still
does not appear:
- Close the Server Administrator user interface.
- Restart the "Systems Management Data Manager" service.
- Restart the "Secure Port Server" service.
- Open the Server Administrator user interface and log in.
* When connecting to a remote DRAC 4 using a Mozilla Web browser,
the Virtual Media feature may not be available with the error
"Virtual Media Plug-in is not installed or running. This is
caused by new Java applet security features of Mozilla 1.7.3
and newer. Perform the following steps to permanently authorize
the applet for that specific browser:
1. Log in to DRAC4 and stay at the "Properties" page.
2. Overtype the URL in the browser window from
"https://<DRAC4-IP-address>/cgi/main" to
"https://<DRAC4-IP-address>/rac4vm.xpi", and press Enter.
3. Mozilla prompts you with an "Opening rac4vm.xpi" dialog,
allowing you to save the file to your local filesystem.
Click "OK" and save the file to a temporary location (should
be your home directory, by default).
4. After saving the file, close the browser.
5. Restart the browser, and specify the URL of the rac4vm.xpi
file (for example: file:///root/rac4vm.xpi)
6. Mozilla presents you with the "Software Installation" dialog:
press the "Install" button to continue.
7. After the installation completes, close the browser and
restart it once more.
8. Now, log in to DRAC4, and navigate to the Virtual Media link.
The plug-in is installed and ready to use.
9. At this point, the saved ~/rac4vm.xpi file should be deleted
----------------------------------------------------------------------
ISSUES FOR DRAC III, DRAC III/XT, ERA, AND ERA/O
----------------------------------------------------------------------
----------------------------------------------------------------------
Remote Access Dial-Up Settings
----------------------------------------------------------------------
* If you change a DRAC III modem "Dial Mode" setting to "Tone" or
"Pulse" using Server Administrator, IT Assistant displays the
opposite setting.
----------------------------------------------------------------------
ISSUES FOR ALL OPERATING SYSTEMS
----------------------------------------------------------------------
* Server Administrator user interface and commands related to "local
authentication enable" are not applicable for RAC firmware 3.20.
The Active Directory authentication feature replaces "local
operating system authentication" feature in this version of
firmware. Due to this change, the following commands will return
errors:
racadm localauthenable
omconfig rac authentication
* Due to the fluctuations in the watchdog timer, the "Last Crash
Screen" may not be captured when the Automatic System Recovery is
set to a value less than 30 seconds. To ensure the proper
functioning of the Last Crash Screen feature, set the System Reset
Timer to at least 30 seconds.
* The remote access controller uses FTP protocol to perform some of
the OpenManage commands. If a firewall is installed in the system,
it may cause these commands to fail.
The following Server Administrator CLI commands use FTP protocol to
communicate with the RAC:
omconfig rac uploadcert
omconfig rac generatecert
omupdate racfwupdate
The following racadm commands use FTP protocol to communicate with
the RAC:
racadm sslcertupload
racadm sslcsrgen
raccadm fwupdate
* If the RAC configuration is reset to factory defaults using the
"racadm racresetcfg" command, the RAC configuration tab in Server
Administrator does not reflect the reset configuration settings
until the system is rebooted. Also, the RAC configuration page in
Server Administrator cannot be used to make any configuration
changes until the system reboots.
* The RAC does not support local RAC user IDs with special
characters. When adding a local RAC user, use only alphanumeric
characters for the user name.
* While the RAC is resetting, the Instrumentation Service cannot
read sensor data for certain systems. As a result, the voltage,
temperature, and other probes may not be visible on the Server
Administrator home page until the RAC has completed resetting.
* The RAC may not send traps when your system is locked up. To enable
traps to be sent when the system is locked up, you must configure
the watchdog timer using the Server Administrator GUI. In the Server
Administrator GUI, click the "Properties" tab and ensure that
"Auto Recovery" is selected. The default value of the "Action On
Hung Operating System Detection" setting is "None". "None" indicates
that detection will not be performed.
* RAC firmware 2.0 and higher do not support passwords with special
characters (nonalphanumeric) only for RAC user IDs logging in using
the Web-based interface (with Local RAC Authentication). If you
created RAC user IDs using previous versions of the firmware or if
you created user IDs using Server Administrator that is running
version 2.0 firmware on the managed system, you cannot log into the
RAC.
Use one of the following four methods to correct this issue:
- Change your passwords before updating the firmware.
OR
- Use the following CLI command to change the password:
omconfig rac users username=xx userpassword=yy
where "xx" is the original userid and "yy" is the new password
OR
- Change the password through Server Administrator using the "User"
tab. Ensure that the check box to change the password is checked.
Enter a new password, and then enter it again to validate the
change.
OR
- Use the racadm utility to change the password:
racadm config -g cfgUserAdmin -o cfgUserAdminPassword
-i <usr_index> <new_pwd>
where <usr_index> is the index of the user database entry to be
modified and <new_pwd> is the new password
* Depending on your network and proxy configurations and whether you
are using Netscape Navigator or a Mozilla browser, you may need to
enter the exact IP address of the RAC controller you are trying to
access in the "No Proxy for" field of your browser.
Perform the following steps:
1. Open your Netscape Navigator or Mozilla browser.
2. Click "Edit".
3. Click "Preferences ...".
4. Click "Advanced" in the left sidebar.
5. Click "Proxies" in the left sidebar.
6. Enter the RAC IP address in the "No Proxy for:" field.
7. Click "OK" and then close the browser.
* If the out-of-band RAC user interface was spawned off from the
Server Administrator home page with a Mozilla browser, strings with
extended ASCII characters may not display correctly in certain
languages. This is because the browser is set to the UTF-8 character
set by Server Administrator. To correct this issue, change the
browser character coding to ISO-8859-1. For Japanese and Chinese,
UTF-8 is the correct encoding for RAC pages.
* When using Mozilla 1.6 to view the RAC Web user interface, you must
adjust your cookie settings to "Enable all cookies", by going to
the menu options "Edit -> Preferences -> Privacy & Security ->
Cookies", then selecting "Enable all cookies". If you do not make
this adjustment, you will not be able to log in to the Web
interface, and you will receive a message indicating that your
username and password are incorrect.
----------------------------------------------------------------------
ISSUES FOR WINDOWS OPERATING SYSTEMS
----------------------------------------------------------------------
* A dial-up network connection to the remote access controller is
established by the RAC managed node software installer. The RAC
software will not work properly if this dial-up connection is
deleted or if a proxy is set up in the Internet settings. An
InstallPPP utility is provided with the RAC software to restore the
RAC PPP connection. This utility can also correct issues with
Internet connection problems with proxy server settings when using
the Windows 2003 operating system. The utility can be run from the
Windows command prompt with the argument "CreateRACConnection" as
given below:
c:\>installPPP CreateRACConnection
* Applications that use InstallShield 3.x to install software may take
longer to install if RAC Services are running. To reduce the
software installation time, stop RAC Services before performing the
installation. You must restart RAC Services after the installation
is complete.
* Due to functional details that are specific to Windows Dynamic DNS
servers, the RAC internal PPP IP address is broadcast to the Dynamic
DNS service on servers running Windows. The Dynamic DNS service
stores that particular IP address in its DNS look-up table and
associates it with the name of the system that hosts the RAC. This
action causes problems with Active Directory under Windows. The
default value for a RAC's internal PPP IP address is
192.168.234.235, but the address can be changed by the user. This
issue is a known problem, and there is an article and a hot fix
available from Microsoft. The Knowledge Base article number is
Q292822. Downloading the hot fix and implementing the steps in the
article solve the problem.
* 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, and applies to the Remote Access
Service running on Microsoft Windows operating systems only.
* If you used the "Systems Management" CD version 3.1 or earlier to
install RAC management station software on any system running a
Windows operating system, you must remove any previous versions of
the RAC management station software before installing a later
version of the RAC management station software.
To remove the RAC management station software on Windows, perform
the following steps:
1. Insert the "Systems Management" CD into the CD drive.
2. When the installation application starts, click "Exit".
3. Open a command shell window:
a. Click the "Start" button, and then click "Run".
b. In the "Run" dialog box, type the following command and then
press <Enter>:
cmd
4. Start the Install Shield uninstallation program to remove
software:
a. In the command shell window, type the following line
(replacing x: with the actual drive letter of your CD drive,
such as d:):
x:\rac20\mtpkg\setup.exe
b. Select "Remove", and then click "Next".
c. Click "OK".
d. Click "Finish".
5. Close the command shell window.
* To launch the RAC Web console from IT Assistant, you must run one
of the patches located on the "Systems Management" CD in the
"\support\Windows\RAC" directory. For systems running IT Assistant
on any Windows operating system, use the "Win2KPatch.reg" file.
To apply the patch, browse to the CD directory mentioned above and
double-click the file name. Click "YES" and "OK" in the next two
message boxes. The patch enables the Java Console in Internet
Explorer.
* The Internet Explorer application embedded in the Windows Advanced
Server Limited Edition operating system does not support Java
applets; therefore, it is not possible to use the Advanced Server
Limited Edition's Internet Explorer browser to connect to a RAC
over a local area network (LAN) or the Internet.
* CONNECTING TO THE INTERNET IF THE RAC PPP SERVICE IS RUNNING
After installing Internet Explorer 5.0 or later, you may notice that
the automatic configuration and proxy setting information for each
connection is separate from the same information used for the LAN
connection. If you have both a dial-up and a LAN connection at the
same time, Internet Explorer may block your access to the Internet.
This blocking occurs because each connection in Internet Explorer
5.0 uses its own automatic configuration and proxy settings. When
this occurs and a user tries to establish any kind of PPP
connection, Internet Explorer attempts to use the dial-up connection
settings to access the Internet.
You can find additional information about this issue in article
Q236920, "Connections No Longer Use LAN Automatic Configuration and
Proxy" (Q236920) in the Microsoft Knowledge Base at
"support.microsoft.com".
- To correct this problem, you must apply Microsoft IE HotFix 818060
to either Internet Explorer 5.01 SP2 or 6.0 SP1. HotFix 818060 is
available on the "Systems Management" CD in the "\support\Windows\
HotFix" directory. Refer to the following Microsoft support
article for further instructions with applying this HotFix:
http://support.microsoft.com?kbid=818060
* To launch the RAC Web console from IT Assistant, you must run one of
the patches located on the "Dell OpenManage Systems Management" CD
in the "\support\Windows\RAC" directory. If you are running IT
Assistant on any Windows operating system (Windows NT(TM) is not
supported), use the "Win2KPatch.reg" file. To apply the patch,
browse to the CD directory previously mentioned and double-click the
filename. Click "Yes" and "OK" in the next two message boxes. The
patch enables the Java Console in Internet Explorer.
* On systems running Windows, the RAC installation process requires a
virtual modem connection named RACPORT to communicate between the
operating system and the RAC controller. When any modem is added to
the system, the operating system automatically creates a virtual fax
device icon in the printers folder. The fax icon is not used by the
RAC and can be deleted or ignored.
* The mouse movement on a local system may appear jerky and erratic
during console redirection. This behavior is evident especially when
using menus or opening windows.
* Resizing the Windows desktop to a resolution of 640 x 480 causes
some information to not be visible in the browser window when using
the RAC Web-based interface. This issue occurs in both Netscape
Navigator and Internet Explorer. To view a screen in its entirety
when using a resolution of 640 x 480, you must enlarge the browser
window.
----------------------------------------------------------------------
ISSUES FOR RED HAT ENTERPRISE LINUX OPERATING SYSTEMS
----------------------------------------------------------------------
* When installing the Dell OpenManage systems management applications
through the Nautilus File Manager, you must use the "Run" button and
not the "Run In Terminal" button after choosing the "start.sh"
script from the File Manager's file list. Use the "Run In Terminal"
button for applications that do not open a window of their own (the
"start.sh" script opens its own window). If you choose "Run In
Terminal", you must restart the racvnc service after installing
Dell OpenManage systems management applications by typing the
following command:
"service racvnc restart"
* When using Console Redirection on a managed system running Red Hat
Linux, the focus (cursor moved back over an object) follows the
cursor. Occasionally, the text windows in Console Redirection lose
focus. Before attempting to type in a text window in a Console
Redirection window, click the mouse in the text window's spacebar or
top menu bar to ensure that your target text window has the focus on
the correct window or application that you are attempting to use.
----------------------------------------------------------------------
ISSUES FOR NOVELL NETWARE OPERATING SYSTEMS
----------------------------------------------------------------------
* When a remote "Reset", "Power Off", or "Power Cycle" is issued
through the RAC on NetWare, some NetWare applications may require
user interaction to close application windows. If this is necessary,
you should use the RAC console redirection to manually close the
application windows to allow NetWare to shut down.
* During normal operation of the DRAC III managed system under
NetWare 5.1 and NetWare 6.0, the operating system periodically
displays the following messages:
"LCP is down: **PPP did not receive a response from peer for several
Echo-Requests sent**"
"Call disconnection for protocol IP to destination RAC3. The event
occurred due to a link failure."
These messages do not indicate errors. They are generated when the
RAC PPP connection is temporarily unavailable (the connection
may be unavailable when the card is reconfigured or new users are
added). The PPP connection is automatically re-established, and no
user action is required. Therefore, the user should not attempt to
manually re-establish the connection.
* Some RACADM commands intermittently fail when executing locally on a
system with Netware.
======================================================================
ISSUES FOR UPDATE SERVICE
======================================================================
* The Update tab in the Server Administrator interface does not list
certain CERC SATA RAID cards for driver updating with an appropriate
Dell Update Package. Dell will address this in a future release.
* 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.
* On systems equipped with a DRAC III/XT, make sure you have installed
the Remote Access Service software before attempting to perform a
firmware update. To carry out updates on these systems, navigate to
the "Update" tab and proceed from there.
* Update Service allows the DRAC III firmware update package for a
PowerEdge 4600 to be applied to a PowerEdge 6600/6650, which should
not be allowed. It is recommended to use the appropriate firmware
update package specifically for PowerEdge 6600/6650.
######################################################################
HISTORY
######################################################################
This section provides historical information about the new features
and fixes that were implemented in previous versions of Server
Administrator.
**********************************************************************
SERVER ADMINISTRATOR, VERSION 1.9
**********************************************************************
======================================================================
RELEASE HIGHLIGHTS
======================================================================
This release of Server Administrator provided both a basic and an
enhanced Storage Management Service. The basic Storage Management
Service was the same service as provided with previous releases.
Array Manager was installed with the basic Storage Management
Service. The enhanced Storage Management Service replaced the
storage management and configuration features provided by Array
Manager. Unlike the basic Storage Management Service and Array
Manager, the enhanced Storage Management Service features were
accessible from the Server Administrator graphical and command line
interfaces.
**********************************************************************
SERVER ADMINISTRATOR, VERSION 1.8.1
**********************************************************************
======================================================================
RELEASE HIGHLIGHTS
======================================================================
* Added support for Baseboard Management Controller (BMC)
* Added support for Platform Event Filtering (PEF)
* Added support for Platform Event Destinations
**********************************************************************
SERVER ADMINISTRATOR, VERSION 1.8
**********************************************************************
======================================================================
WHAT WAS NEW IN VERSION 1.8 OF SERVER ADMINISTRATOR?
======================================================================
* Added support for Citrix installation
* Added the ability to update the following devices by using the
Update Service:
* PERC 4/IM driver
* CERC SATA 6 Channel firmware and driver
* Intel NIC
* Broadcom NIC
* Added support for the Dell PowerEdge 700 and 750 systems
======================================================================
WHAT WAS FIXED IN VERSION 1.8 OF SERVER ADMINISTRATOR?
======================================================================
* Corrected an issue in which certain RACADM and OMCONFIG commands
were not working properly with Red Hat Enterprise Linux AS 2.1
Update 3.
**********************************************************************
SERVER ADMINISTRATOR, VERSION 1.7
**********************************************************************
======================================================================
WHAT WAS NEW IN VERSION 1.7 OF SERVER ADMINISTRATOR?
======================================================================
* Added support for a new operating system: Red Hat Enterprise Linux
(AS, ES, and WS), version 3.0.
* Added support for the following browsers for systems running Red Hat
Linux, version 9 or Red Hat Enterprise Linux AS, version 2.1:
*Mozilla 1.5
*Netscape Navigator 7.1
* Added the ability to update the following devices by using the
Update Service:
*PERC 2/SC driver
*PERC 2/DC driver
*PERC 4/SC firmware and driver
*PERC 4/DC firmware and driver
======================================================================
WHAT WAS FIXED IN VERSION 1.7 OF SERVER ADMINISTRATOR?
======================================================================
----------------------------------------------------------------------
DIAGNOSTICS SERVICE
----------------------------------------------------------------------
* On Red Hat Enterprise Linux operating systems, the floppy drive
diagnostic was still listed even though the floppy device was
removed from the system. The diagnostic would fail with the
following message:
"DriveTest_12=Error reading:
Insert different formatted media and run this test again."
If this error still occurs, it may indicate a hardware problem.
* On Red Hat Enterprise Linux operating systems, the memory diagnostic
would fail with the following message after being run several times
consecutively: "The test could not allocate enough memory to run:
Verify the Virtual Memory Paging file is larger than the total
physical memory installed in the system."
**********************************************************************
SERVER ADMINISTRATOR, VERSION 1.6
**********************************************************************
======================================================================
WHAT WAS NEW IN VERSION 1.6 OF SERVER ADMINISTRATOR?
======================================================================
* Added Novell Netware 6.5 as a supported operating system.
* Discontinued Novell Netware 6.0 as a supported operating system.
* Added the "Export" feature, which generates a text file that lists
the values for each data field on the open Server Administrator
window, separated by a delimiter you can customize, and saved to a
location you specify.
======================================================================
WHAT WAS FIXED IN VERSION 1.6 OF SERVER ADMINISTRATOR?
======================================================================
----------------------------------------------------------------------
DIAGNOSTIC SERVICE
----------------------------------------------------------------------
* On the Dell PowerEdge 2600 with Windows, running Tape Drive
diagnostics on the DLT VS160 tape drive failed in the previous
release.
* On the Traditional Chinese and Japanese versions of the Windows
Server 2003 operating system, an error would appear after rebooting
the system or restarting the secure port server. The error
originated from "EliteDiag.exe", which is part of the Diagnostic
Service. However, the functionality of the diagnostics was not
affected by this error.
* The option to format the CLI omdiag output in custom delimited
format (cdv) did not function properly.
* For PowerEdge 8450 systems with eight processors installed and for
PowerEdge 6400, 6450, 6600, and 6650 systems with four processors
installed and running with hyper-threading ON, the CPU Math Register
Test would fail with "Test process exited abnormally".
----------------------------------------------------------------------
REMOTE ACCESS SERVICE
----------------------------------------------------------------------
* The RAC Managed Node version was not showing up in NetWare on the
"System Summary" page.
* On systems running a supported Red Hat Enterprise Linux operating
system, some folders and log files relating to the Remote Access
Service were left on the system’s hard drive after an uninstall of
Dell OpenManage software.
* Some of the racadm CLI options for "getraclog" were not working
correctly.
* The racadm CLI command "omconfig rac snmptraps" was not allowing the
same IP address to be entered multiple times for SNMP traps.
* On systems running a supported Windows operating system, some
temporary files were remaining in the system after a RAC firmware
update using Dell Update Packages.
* Incorrect help pages were linked to some Remote Access Service
pages.
**********************************************************************
SERVER ADMINISTRATOR, VERSION 1.5
**********************************************************************
======================================================================
WHAT WAS NEW IN VERSION 1.5 OF SERVER ADMINISTRATOR?
======================================================================
This release adds operating system support for Windows 2000
Service Pack 4.
======================================================================
WHAT WAS FIXED IN VERSION 1.5 OF SERVER ADMINISTRATOR?
======================================================================
----------------------------------------------------------------------
DIAGNOSTIC SERVICE ON WINDOWS OPERATING SYSTEMS
----------------------------------------------------------------------
* On PowerEdge 350 systems, issues with the Serial Port Data Send
and Receive test and the CD diagnostics have been corrected.
* Running Tape Drive diagnostics on the DLT VS160 tape failed in the
previous release.
----------------------------------------------------------------------
DIAGNOSTIC SERVICE ON RED HAT ENTERPRISE LINUX OPERATING SYSTEMS
----------------------------------------------------------------------
* The CD-RW Read Write test failed in the previous release
when running the diagnostic with a CD-RW that was not blank. The
following error was generated: "Error erasing the disc - SCSI Error
2900."
* USB diskette and USB CD drives were not identified properly by the
diagnostics.
* Running the USB Status test in "Run Simultaneously" mode produced
a failed result and sometimes caused the online diagnostics to hang.
----------------------------------------------------------------------
REMOTE ACCESS SERVICE
----------------------------------------------------------------------
* Corrected an issue in which the Server Administrator CLI did not
allow you to set the country code for a RAC modem. The "Country
Code" field has been added.
* Corrected an issue in which you were unable to use the input field
or "Browse" button to upload a security certificate in
Mozilla 1.2.1.
* Corrected an issue in which the Server Administrator CLI output an
incorrect error message when creating a "dialinuser" with a user
name longer than 15 characters.
* Corrected an issue in which the Upload Certificate feature for the
"Security" tab in the ERA/O controller may result in the following
error when running NetWare 6.0: "Error! File does not exist in the
path specified." If the signed certificate file exists in the path
specified, it can now be uploaded. If the file does not exist in the
path, an error message displays.
* Corrected an issue found when viewing the details of the RAC SSL
server certificate in Server Administrator or the CLI, in which a
RAC SSL server certificate is falsely identified as a Certificate
Authority (CA) certificate. This correction fixed the following two
issues: "View Server Certificate" links you to the wrong type of
certificate; and in the Server Administrator CLI, the "omreport rac
viewcertificate type" command output the wrong value for "type".
* Corrected an issue in the Server Administrator GUI in which setting
"Severity Configuration" on SNMP traps caused JavaScript errors.
* Corrected an issue that caused an error stating that the page could
not be displayed when uploading a RAC SSL certificate in Server
Administrator using Internet Explorer on systems running Windows
Server 2003.
* Corrected an issue in which the Server Administrator "RAC Users"
page allowed only 8-character passwords in the text field. The
maximum number of characters allowed in the user password has been
increased from 8 to 63 characters when adding or configuring RAC
users in Server Administrator.
* Corrected an issue in which you were unable to retain a custom
message in the "Alpha-Numeric Paging" settings. The custom message
for alphanumeric pages was limited to 31 characters when adding or
configuring RAC users in Server Administrator.
* Corrected an issue in which the RAC "Generate a New CSR" function of
the Server Administrator Web-based interface did not work when Red
Hat Linux 9 runs on the managed system.
* Corrected an issue in which adding a RAC user from the Server
Administrator interface overwrote an existing user if the new user
had the same user name or index as the existing user.
----------------------------------------------------------------------
UPDATE SERVICE ON WINDOWS 2003 OPERATING SYSTEM
----------------------------------------------------------------------
* Corrected an issue that occurred when attempting to validate any
update package. A message indicated that the page could not be
displayed. The message no longer appears, and the validation
process continues properly. If you observe a similar issue, see the
Microsoft Knowledge Base article 822753 for more information.
######################################################################
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.; "Intel" is a registered
trademark of Intel Corporation; "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 Inc. disclaims any proprietary interest in
trademarks and trade names other than its own.
October 2004
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.