Frequently Asked Questions

Dell™ OpenManage™ Version 5.2 Installation and Security User's Guide

Red Hat® Enterprise Linux® or SUSE® Linux Enterprise Server

General

Is the Dell™ PowerEdge™ Installation and Server Management CD a bootable CD?

Yes, the CD is bootable. It boots into the Dell OpenManage™ Server Assistant operating system setup mode by default. After installing managed system software, if an operating system was previously installed, you will be given the option to boot from the operating system. It is recommended that you eject the CD to avoid booting into Server Assistant setup mode.

Where can I find the quick installation instructions?

The Quick Installation Guide comes as a small brochure with the CD kit. Also, you can find the guide on the Dell Support website at support.dell.com and at the following location on the Dell PowerEdge Installation and Server Management CD:

\srvadmin\docs\language\OpenManage_QIG\QUICK_INSTALL_GUIDE.htm

where language is the appropriate language directory for you.

How do I install Dell OpenManage Server Administrator with only the CLI features?

By choosing not to install the Server Administrator Web server, you will get CLI features only.

What ports do Dell OpenManage applications use?

The default port used by Server Administrator is 1311. The default ports used by Dell OpenManage IT Assistant are 2606 (for the connection service) and 2607 (for the network monitoring service). These ports are configurable. See Table 2-1 in this guide for additional details.

Microsoft® Windows®

How do I fix a faulty installation of Server Administrator?

You can fix a faulty installation by forcing a reinstall and then performing an uninstall of Server Administrator. To force a reinstall:

Find out the version of Server Administrator that was previously installed.
Download the installation package for that version from the Dell Support website at support.dell.com.
Locate SysMgmt.msi from the srvadmin\windows\SystemsManagement directory and enter the following command at the command prompt to force a reinstall.

msiexec /i SysMgmt.msi REINSTALL=ALL REINSTALLMODE=vomus

Select Custom Setup and choose all the features that were originally installed. If you are not sure which features were installed, select all of them and perform the installation.

NOTE: If you installed Server Administrator in a non-default directory, make sure to change it in Custom Setup as well.

Once the application is installed, you can uninstall it from Add/Remove Programs.

How do I perform a silent (unattended) upgrade from Dell OpenManage 4.x (where x is >=3) to Dell OpenManage 5.2?

Use the following commands for a Management Station:

msiexec /i MgmtSt.msi/qn (for fresh installs or major upgrades. For example, upgrading from Dell OpenManage version 4.3 to version 5.2.)

Use the following commands for a managed system:

msiexec /i SysMgmt.msi/qn (for fresh installs or major upgrades. For example, upgrading from Dell OpenManage version 4.3 to version 5.2.)

msiexec /i SysMgmt.msi REINSTALL=ALL REINSTALLMODE=vomus /qn (for minor upgrades. For example, upgrading from Dell OpenManage version 5.0 to version 5.2.)

How do I prevent the system from rebooting after a silent (unattended) install/uninstall?

Use the optional command line switch:

Reboot=ReallySuppress

Here is an example for the Management Station:

msiexec /i SysMgmt.msi /qb Reboot=ReallySuppress

What is an MSP service pack file? Should I upgrade my Dell OpenManage 4.3 version with the MSP file?

A Microsoft Service Pack (MSP) file stores only the differences between an old version and a new version. It is much smaller in size than the upgrade file. You can either use the MSP file or the new MSI file to upgrade your Dell OpenManage 4.3. Using the MSP file is a good idea as it is more efficient.

NOTE: You can upgrade from Dell OpenManage software version 4.3 to 5.2 through a full MSI Installation only. You cannot upgrade using a MSP service pack file.

Where can I find the MSI log files?

By default, the MSI log files are stored in the path defined by the %TEMP% environment variable.

I downloaded the Server Administrator files for Windows from the Dell Support website and copied it to my own CD. When I tried to launch the SysMgmt.msi file, it failed. What is wrong?

MSI requires all installers to specify the MEDIAPACKAGEPATH property if the MSI file does not reside on the root of the CD.

This property is set to \srvadmin\windows\SystemsManagement for the managed system software MSI package. If you decide to make your own CD you must ensure that the CD layout stays the same. The SysMgmt.msi file must be located in the \srvadmin\windows\SystemsManagement directory on the CD. For more detailed information, go to http://msdn.microsoft.com and search for: MEDIAPACKAGEPATH Property.

I cannot upgrade from Dell OpenManage 4.2 to the latest version of Dell OpenManage without uninstalling and losing my managed system software settings. Is there a way to upgrade to the latest version while preserving my managed system software settings?

Yes, but you must upgrade from Dell OpenManage version 4.2 to 4.3 first, before upgrading to a later version of Dell OpenManage. If you are working with Windows Server® 2003, do not apply
Service Pack 1 until you have completed the Dell OpenManage upgrade.

How do I perform an unattended operating system installation with the Installation and Server Management CD?

You can install a Windows operating system on many systems using identical settings, which allows consistent configurations across all systems. To use this feature, it is necessary that the target Dell PowerEdge systems be configured identically, with the same hardware and operating system components. Any difference in configuration makes the replication feature unusable.

To perform unattended installations, do the following:

On the first system that is set up, ensure that the system's BIOS is set to boot from the CD. Insert the Dell PowerEdge Installation and Server Management CD and reboot your system. Follow the installation interview, which includes setting the date and time, configuring the RAID controllers, selecting the operating system and specifying its settings, configuring the hard drive, entering the network settings, and configuring Windows. If any information is omitted, an unattended installation can still be accomplished, but the system will prompt you for the missing information.
In the Installation Summary window, select Save Unattended Installation Script at C:\unattended.txt, C:\txtsetup.oem and select Save Profile for Replication at C:\replication. Click the Continue button.
Insert the appropriate operating system CD and follow the instructions to complete the installation. Reboot the system to complete the installation.
When the installation is completed on the first server, copy the files from the C:\replication directory to a diskette.
For each subsequent unattended installation, insert the disk containing the replication files into the diskette drive and boot the system. The installation interview will be done automatically. Then, insert the operating system CD to install the operating system, and reboot the system to complete the installation.

What is the best way to use the Prerequisite Checker information?

The Prerequisite Checker is available for Windows. See the readme file \srvadmin\windows\PreReqChecker\readme.txt on the Dell PowerEdge Installation and Server Management CD for detailed information about how to use the Prerequisite Checker.

In the Prerequisite Checker screen, I get the message "An error occurred while attempting to execute a Visual Basic Script. Please confirm that Visual Basic files are installed correctly." What can I do to resolve this problem?

This error occurs when the Prerequisite Checker calls the Dell OpenManage script, vbstest.vbs (a visual basic script), to verify the installation environment, and the script fails.

The possible causes are:

Incorrect Internet Explorer Security Settings.

Ensure that Tools® Internet Options® Security® Custom Level® Scripting® Active Scripting is set to Enable

Ensure that Tools® Internet Options® Security® Custom Level® Scripting® Scripting of Java Applets is set to Enable.

Windows Scripting Host (WSH) has disabled the running of VBS scripts. WSH is installed during operating system installation, by default. WSH can be configured to prevent the running of scripts with a .VBS extension.

Right click My Computer on your desktop and click Open® Tools® Folder Options® File Types.
Look for the VBS file extension and ensure that File Types is set to VBScript Script File.
If not, click Change and choose Microsoft Windows Based Script Host as the application that gets invoked to run the script.

WSH is the wrong version, corrupted, or not installed. WSH is installed during operating system installation, by default. Go to the following location for the current WSH to download: http://msdn.microsoft.com/downloads/list/webdev.asp

Can I launch my installation without running the Prerequisite Checker? How do I do that?

Yes, you can. You can run the MSI directly from the \Windows\SystemsManagement folder. In general, it is not a good idea to bypass the prerequisite information as there could be important information that you would not know otherwise.

How do I know what version of systems management software is installed on the system?

Go to Start® Settings® Control Panel® Add/Remove programs and select Dell OpenManage Server Administrator. Select the link for support information.

What are the names of all the Dell OpenManage features under Windows?

The following table lists the names of all Dell OpenManage features and their corresponding names in Windows.

Table 10-1. Dell OpenManage Features Under Windows

Feature	Name in Windows
Managed System Services
Server Administrator Instrumentation Service	DSM SA Data Manager DSM SA Event Manager
Server Administrator	DSM SA Connection Service DSM SA Shared Services
Server Administrator Storage Management Service	Mr2kserv
Remote Access Controller Console (DRAC III)	Remote Access Controller (RAC) Service RAC Win VNC
Remote Access Controller Console (DRAC 4)	Remote Access Controller 4 (DRAC 4)
Remote Access Controller Console (DRAC 5)	Remote Access Controller 5 (DRAC 5)
Management Station Services
IT Assistant	DSM IT Assistant Network Monitor DSM IT Assistant Connection Service DSM IT Assistant Common Services
Baseboard Management Controller (BMC)	DSM BMU SOL Proxy

Red Hat® Enterprise Linux® or SUSE® Linux Enterprise Server

How do I perform an unattended operating system installation with the Installation and Server Management CD?

You can install a Red Hat Enterprise Linux or SUSE Linux Enterprise Server operating system on many systems using identical settings, which is called a kickstart, and allow consistent configurations across all systems. To use this feature, the PowerEdge systems must be configured identically with the same hardware and operating system installed. Any difference in configuration makes the replication feature unusable.

To perform unattended installations, do the following:

On the first server being set up, ensure that the server's BIOS is set to boot from the CD. Insert the Installation and Server Management CD and reboot your server. Follow the installation interview, which includes setting the date and time, configuring the RAID controllers, selecting the operating system and specifying its settings, configuring the hard drive, entering the network settings, and configuring Red Hat Enterprise Linux or SUSE Linux Enterprise Server. If any information is omitted, an unattended installation can still be accomplished, but the system will prompt you for the missing information.
In the Installation Summary window, select Save Unattended Installation Script at /root/install-ks.cfg and select Save Profile for Replication at /root/replication. Click the Continue button.
Insert the Red Hat Enterprise Linux or SUSE Linux Enterprise Server installation CD and follow the instructions to complete the installation. Reboot the system to complete the installation.
When the installation is completed on the first system, copy the files from the /root/replication directory to a diskette.
For each subsequent unattended installation, insert the disk containing the replication files into the diskette drive and boot the system. The installation interview will be done automatically. Then, insert the Red Hat Enterprise Linux or SUSE Linux Enterprise Server installation CD to install the operating system, and reboot the system to complete the installation.

I manually installed my Red Hat Enterprise Linux 4 - x86_64 or SUSE Linux Enterprise Server 9 x86_64 operating system and am seeing RPM dependencies when trying to install Server Administrator. Where could I find these dependent RPM files?

For Red Hat Enterprise Linux, the dependent RPM files are on the Red Hat Enterprise Linux installation CD. For convenience, they are captured in one of the following directories corresponding to a supported Red Hat Enterprise Linux operating system:

/srvadmin/linux/RPMS/supportRPMS/RH4_i386

/srvadmin/linux/RPMS/supportRPMS/RH4_x86_64

/srvadmin/linux/RPMS/supportRPMS/RH5_i386

/srvadmin/linux/RPMS/supportRPMS/RH5_x86_64

For SUSE Linux Enterprise Server, the dependent RPM files are captured in the following directory:

/srvadmin/linux/RPMS/supportRPMS/SUSE9_x86_64

/srvadmin/linux/RPMS/supportRPMS/SUSE10_x86_64

For instance, in the RH4_x86_64 subdirectory, execute the following command to install or update all the dependent RPM files:

rpm –ivh /srvadmin/linux/RPMS/supportRPMS/RH4_x86_64

You will then be able to continue with the Server Administrator installation.

Why am I getting a warning concerning the RPM package key during installation?

The RPM files are signed with a digital signature. To avoid this warning, you should mount the CD or package, and import the key using a command such as the following:

rpm --import /mnt/cdrom/srvadmin/linux/RPM-GPG-KEY

Why is the Prerequisite Checker not available under Red Hat Enterprise Linux and SUSE Linux Enterprise Server?

The Prerequisite Checker is built into the omilcore RPM package. The checker uses a combination of RPM dependency checks and Dell hardware checks.

What are the names of all the Dell OpenManage features under Red Hat Enterprise Linux or SUSE Linux Enterprise Server?

The following table lists the names of all Dell OpenManage features and their corresponding init script names under Red Hat Enterprise Linux and SUSE Linux Enterprise Server operating systems:

Table 10-2. Dell OpenManage Features Under Red Hat Enterprise Linux
and SUSE Linux Enterprise Server

Feature	Name in Red Hat Enterprise Linux and SUSE Linux Enterprise Server
Managed System Services Feature	Feature init Script Name
DSM SA Device Drivers DSM SA Data Engine Service	instsvcdrv dataeng
DSM SA Shared Service DSM SA Connection Service	dsm_om_shrsvc dsm_om_connsvc
DSM SM LSI Manager	mptctl
Remote Access Controller (DRAC III)
RAC3 Event Service	racsrvc
RAC3 ppp Daemon	racser
RAC3 VNC X Server	racvnc
Remote Access Controller (DRAC 4)	racsvc
Remote Access Controller (DRAC 5)	None
Management Station Services	Feature init Script Name
Baseboard Management Controller (BMC)	dsm_bmu_sol_proxy
Non-Dell OpenManage Features	Feature init Script Name
OpenIPMI	ipmi (if not present, dsm_sa_ipmi)

What do the directories under srvadmin/linux/custom/<operating system> contain?

The following table lists the names of the directories in the srvadmin/linux/custom/<operating system> directory.

Table 10-3. Names of the Directories Under the srvadmin/linux/custom/<operating system> Directory

Name of RPM

Description

Other Server Administrator RPMs required

srvadmin-base — This is the core code for Server Administrator. It provides motherboard alerts and contains the CLI that allows for monitoring and control of Server Administrator, for example, omconfig, omdiag, and omreport. All peripheral packages, except the standalone DRAC support, require all or most of the RPM's in this directory to be installed.

NOTE: You may need to install IPMI drivers for proper functionality.

instsvc-drivers

Server Administrator Device Drivers — The systems management package, srvadmin-hapi, now provides the device drivers and libraries. This RPM is needed for legacy Server Administrator applications.

srvadmin-cm

Server Administrator Inventory Collector — Systems management change management inventory collector.

srvadmin-omilcore, srvadmin-deng, and srvadmin-omacore.

srvadmin-deng

Server Administrator Data Engine — Systems management provides a data management framework for systems management software.

srvadmin-omilcore

srvadmin-hapi

Server Administrator Hardware Application Programming Interface — This systems management package provides the device drivers and libraries needed by systems management software to access information about the hardware on supported systems.

srvadmin-omilcore and srvadmin-ipmi

srvadmin-isvc

Server Administrator Instrumentation Service — Server Administrator provides a suite of systems management information for keeping supported systems on your network healthy. Server Administrator Instrumentation Service provides fault management information, prefailure information, and asset and inventory information to management applications. The Instrumentation Service monitors the health of the system and provides rapid access to detailed fault and performance information about the hardware on supported systems. The Instrumentation Service requires installation of systems management device drivers.

srvadmin-omilcore, srvadmin-deng, and srvadmin-hapi

srvadmin-jre

Server Administrator Sun Java Runtime Environment — Systems management managed node Java runtime.

srvadmin-omilcore, srvadmin-deng, and srvadmin-omacore

srvadmin-odf

Server Administrator Online Diagnostic Common Components — Systems management online diagnostics framework.

NOTE: The srvadmin-odf RPM, though installed, will not be functional as Diagnostics is no longer available through Server Administrator. To run diagnostics on your system, install Dell PowerEdge Diagnostics from your Dell PowerEdge Service and Diagnostic Utilities CD or download and install Dell PowerEdge Diagnostics from the Dell Support website at support.dell.com. Dell PowerEdge Diagnostics is a stand-alone application that can be run without installing Server Administrator.

srvadmin-omilcore, srvadmin-deng, and srvadmin-omacore

srvadmin-omacore

Server Administrator — Systems management managed mode core and CLI.

srvadmin-omilcore and srvadmin-deng

srvadmin-omhip

Server Administrator Instrumentation Service Integration Layer — Provides Instrumentation CLI.

srvadmin-omilcore, srvadmin-deng, srvadmin-hapi, srvadmin-isvc, and srvadmin-omacore

srvadmin-omilcore

Server Administrator Install Core — This is the core install package that provides the tools necessary for the rest of the Systems management install packages. All Server Administrator RPM's require this RPM.

add-RAC3 — Software for remote management of third generation Remote Access Controllers.
For example: DRAC III.

srvadmin-rac3-components

Remote Access Card Data Populator Remote Access Controller components.

srvadmin-omilcore, srvadmin-deng, srvadmin-hapi, and srvadmin-racser

srvadmin-racdrsc3

DRAC III Integration Layer — Remote Access CLI and Web Plugin to Server Administrator.

srvadmin-omilcore, srvadmin-deng, srvadmin-omacore, and srvadmin-rac3 components

srvadmin-racser

Remote Access Card Managed Node — Remote Access Controller (RAC) services for the central administration of server clusters and remote administration of distributed resources.

srvadmin-omilcore

srvadmin-racser-devel

Remote Access Card Tools — The tools and libraries necessary to interface with the RAC board. This includes a managed node server daemon, a CLI tool named racadm, and the shared library these components require.

srvadmin-omilcore and srvadmin-racser

srvadmin-racvnc

RAC VNC Remote Service and Remote Services Server Agent.

srvadmin-omilcore and srvadmin-racser

add-RAC4 — Software for remote management of fourth generation Remote Access Controllers.
For example: DRAC 4.

srvadmin-rac4-components

Remote Access Card Data Populator — Remote Access Controller components.

srvadmin-omilcore, srvadmin-deng, srvadmin-hapi, and srvadmin-racsvc

srvadmin-racadm4

RAC Command Interface — The command line user interface to the Remote Access Controller (RAC).

srvadmin-omilcore

srvadmin-racdrsc4

DRAC 4 Integration Layer — Remote Access CLI and Web Plugin to Server Administrator

srvadmin-omilcore, srvadmin-deng, srvadmin-rac4 components, and srvadmin-omacore

srvadmin-racsvc

Remote Access Card Managed Node — Remote Access Controller (RAC) services supporting the central administration of server clusters and the remote administration of distributed resources.

srvadmin-omilcore

add-RAC5 — Software for remote management of fifth generation Remote Access Controllers.
For example: DRAC 5.

srvadmin-rac5-components

Remote Access Card Data Populator, DRAC 5 and Remote Access Controller components, DRAC 5.

srvadmin-omilcore, srvadmin-deng, and srvadmin-hapi

srvadmin-racadm5

RAC Command Interface — The command line user interface to the Remote Access Controller (RAC).

srvadmin-omilcore and srvadmin-hapi

srvadmin-racdrsc5

DRAC 5 Integration Layer — Remote Access CLI and Web Plug-in to Server Administrator

srvadmin-omilcore, srvadmin-deng, srvadmin-omacore, and srvadmin-rac5 components

add-storageservices — Storage Management RAID configuration utility and storage alert software

srvadmin-storage

Storage Management — Provides Systems Management Storage Services.

srvadmin-omilcore, srvadmin-deng, srvadmin-omacore, and srvadmin-odf

add-webserver — Provides Web access to management of the server

srvadmin-iws

Secure Port Server — Systems Management Managed Node Web Server package.

srvadmin-omilcore, srvadmin-deng, srvadmin-omacore, and srvadmin-jre

add-openipmi-RHEL4 — Provides OpenIPMI support for Red Hat Enterprise Linux (version 4)

dkms

Dynamic Kernel Module Support Framework — This package contains the framework for the Dynamic Kernel Module Support (DKMS) method for installing module RPMS as originally developed by Dell Computer Corporation.

openipmi

Openipmi XX.Y.RHEL4 dkms package — Kernel modules for openipmi XX.Y.RHEL4 in a DKMS wrapper.

dkms

srvadmin-ipmi

This RPM forces the proper install sequence for the DKMS, openipmi XX.Y.RHEL4, and srvadmin-hapi RPMS.

openipmi XX.Y.RHEL4

add-openipmi-SLES9 — Provides OpenIPMI support for SUSE Linux Enterprise Server (version 9)

dkms

openipmi

Openipmi XX.Y.SLES9 dkms package — Kernel modules for openipmi XX.Y.SLES9 in a DKMS wrapper.

dkms

srvadmin-ipmi

This RPM forces the proper install sequence for the DKMS, openipmi XX.Y.SLES9, and srvadmin-hapi RPMS.

openipmi XX.Y.SLES9

add-openipmi-SLES10 — Provides OpenIPMI support for SUSE Linux Enterprise Server (version 10)

srvadmin-ipmi

This RPM is used to address the RPM dependency of srvadmin-hapi package.

openipmi XX.Y.SLES10

What daemons run on Red Hat Enterprise Linux and SUSE Linux Enterprise Server operating systems after Server Administrator is started?

The daemons that run on Red Hat Enterprise Linux and SUSE Linux Enterprise Server operating systems depend on what has been installed and what is enabled to run. The following table displays the daemons that typically run for a full install:

Table 10-4. Daemons that run on Red Hat Enterprise Linux and SUSE Linux Enterprise Server once Server Administrator is started

Daemon Name	Name in Red Hat Enterprise Linux and SUSE Linux Enterprise Server
For RPMs in the srvadmin-base directory
dsm_sa_datamgr32d	DSM SA Data Manager — Server Administrator data manager daemon started by DSM SA Data Engine service.
dsm_sa_eventmgr32d	DSM SA Event Manager — Server Administrator event and logging daemon started by DSM SA Data Engine service.
dsm_sa_snmp32d	DSM SA SNMP daemon — Server Administrator SNMP daemon started by DSM SA Data Engine service.
dsm_om_shrsvc32d	DSM SA Shared Services — Server Administrator core daemon.
For RPMs in the add-webserver directory
dsm_om_connsvc32d	DSM SA Connection Services — Server Administrator Web server daemon.
For systems that support DRAC 4: add-RAC4
racsvc	DRAC 4 Administrator daemon
For systems that support DRAC III: add-RAC3
racser	DRAC III Administrator daemon
racvnc	DRAC III virtual network daemon
racsrvc	DRAC III VNC X server

What kernel modules are loaded when Server Administrator is started?

This is dependent on the type of systems instrumentation. The following table displays the kernel modules loaded when Server Administrator is started.

Table 10-5. Kernel Modules Loaded when Server Administrator Services are Started

Driver Name	Description
For a system with IPMI
dell_rbu	Dell BIOS Update Driver
ipmi_devintf	IPMI device driver
ipmi_msghandler	IPMI device driver
ipmi_si	IPMI device driver — For systems running Red Hat Enterprise Linux (version 4) or SUSE Linux Enterprise Server (version 9 and 10)
For a TVM system
dcdbas	Dell Systems Management Base Driver
dell_rbu	Dell BIOS Update Driver
For an ESM system
dcdbas	Dell Systems Management Base Driver
dell_rbu	Dell BIOS Update Driver
For support of Server Administrator Storage Systems
mptctl	Device driver for LSI RAID

Back to Contents Page