Server Administrator Version 7.4 Installation Guide

After installing Server Administrator, I cannot log in.

Log out and then log in again to access the Server Administrator Command Line Interface (CLI).

I see the following message when I try to install Server Administrator on a guest Linux operating system.

./srvadmin-install.sh: line 2295 : [: ==: unary operator expected.

When installing Systems Management components on a guest Linux operating system, the warning message may be displayed. However, the installation continues and completes without any loss of functionality.

I manually installed my Red Hat Enterprise Linux 4 64-bit operating system and can see RPM dependencies while installing Server Administrator. Where can I find these dependent RPM files?

For Red Hat Enterprise Linux, the dependent RPM files are on the Red Hat Enterprise Linux installation media. All other RPMs are available in the /SYSMGMT/srvadmin/linux/RPMS/supportRPMS\opensource-components directory. To install or update all the dependent RPM files execute the following command:

rpm –ivh /SYSMGMT/srvadmin/linux/RPMS/ supportRPMS/opensource-components

You can then continue with the Server Administrator installation.

I have performed a non-default install of the Linux operating system using the Linux operating system media, I see missing RPM file dependencies while installing Server Administrator?

Server Administrator is a 32-bit application. When installed on a system running a 64-bit version of Red Hat Enterprise Linux operating system, the Server Administrator remains a 32-bit application, while the device drivers installed by Server Administrator are 64-bit. If you attempt to install Server Administrator on Red Hat Enterprise Linux (versions 5 and version 6) for Intel EM64T, ensure that you install the applicable 32-bit versions of the missing RPM file dependencies. The 32-bit RPM versions always have i386 in the filename extension. You may also experience failed shared object files (files with so in the filename extension) dependencies. In this case, you can determine which RPM is needed to install the shared object, by using the RPM --whatprovides switch. For example: rpm -q --whatprovides libpam.so.0

An RPM name such as pam-0.75-64 could be returned, so obtain and install the pam-0.75-64.i386.rpm. When Server Administrator is installed on a system running a 64-bit version of Linux operating system, ensure that the compat-libstdc++-<version>.i386.rpm RPM package is installed. You need to resolve the dependencies manually by installing the missing RPM files from the Linux operating system media.

NOTE: If you are using later versions of supported Linux operating systems and the RPM files available in the directory SYSMGMT/srvadmin/linux/RPMS/supportRPMS on the DVD are incompatible, use the latest RPMs from the operating system media.

Where can I find the source packages for Open Source RPMs?

Source packages for Open Source RPMs are available on an orderable DVD image.

What do I do when management station RAC utility installation fails due to missing RPM file?

During the installation of the management station RAC utility ( mgmtst-racadm RPM under /SYSMGMT/ManagementStation/linux/rac directory on the Systems Management Tools and Documentation DVD), the installation may fail due to missing RPM file dependencies on libstdc++.so libraries. Install the compat-libstdc++ RPM provided in the same directory to resolve the dependency and retry the installation.

When using the rpm -e 'rpm -qa | grep srvadmin' command to remove systems management software, some RPM utility versions may schedule an uninstallation in an incorrect order, which results in users encountering misleading warning or error messages. What is the solution?

The solution is to use the systems management uninstall script srvadmin-uninstall.sh, provided on the DVD.

What do I do when I am asked to authenticate using the root user account?

Systems Build and Update Utility adds a script to the root user's .bash_profile file that prompts for the installation of systems management software. This script may interfere with remote client applications that authenticate using the root user account on the system, but do not have a means to handle user prompts. To remedy this limitation, edit the .bash_profile file and comment the line [ ${SHLVL}....

During uninstallation, error: %preun(srvadmin-NAME-X.Y.Z-N.i386) scriptlet failed, exit status 1 error message is displayed.

There may be problems uninstalling Server Administrator after an unsuccessful upgrade during a manual RPM upgrade. The following error message is displayed:

error: %preun(srvadmin-NAME-X.Y.Z-N.i386) scriptlet failed, exit status 1

In this case, NAME is a feature name, for example omacore. X.Y.Z-N is the version and build number of the feature. Some possible solutions to rectify this problem:

Attempt to uninstall again. For example, use the following command:
```
 rpm -e srvadmin-NAME-X.Y.Z-N.i386
```
Delete the upgrade.relocation=bad line if present in the /etc/omreg.cfg file and attempt to uninstall again.

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 media or package, and import the key using a command such as the following:

 rpm --import /mnt/dvdrom/SYSMGMT/srvadmin/linux/RPM-GPG-KEY

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

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

Table 1. Systems Management Features — VMware ESX, Red Hat Enterprise Linux, and SUSE Linux Enterprise Server
Feature	Name in VMware ESX, 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
Integrated Remote Access Controller (iDRAC)	None
Remote Access Controller (DRAC 4)	racsvc
Remote Access Controller (DRAC 5)	None

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

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

Table 2. Names of the Directories Under the srvadmin/linux/custom/<operating system> directory
Name of RPM	Description	Other Server Administrator RPMs required
Server-Instrumentation — This is the core code for Server Administrator. It provides motherboard alerts and contains the CLI that allows to monitor and control Server Administrator, for example, `omconfig`, `omdiag`, and `omreport`. All peripheral packages, except the standalone DRAC support, require all or most of the RPMs in this directory to be installed. NOTE: You may need to install IPMI drivers for proper functionality.
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
srvadmin-isvc	Server Administrator Instrumentation Service — Server Administrator provides a suite of systems management information for keeping supported systems on the 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-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 RPMs require this RPM.
srvadmin-syscheck	Package that checks the level of systems management support.	srvadmin-omilcore
add-iDRAC — Software for remote management of third-generation Remote Access Controllers. For example, iDRAC.
srvadmin-idrac-components	Integrated Remote Access Card Data Populator Remote Access Controller components.	srvadmin-omilcore, srvadmin-deng, srvadmin-hapi, and srvadmin-racser
srvadmin-idracadm	iDRAC Command Interface — The command-line user interface to the Integrated Remote Access Controller.	srvadmin-omilcore
srvadmin-idracdrsc	iDRAC Integration Layer — Integrated Remote Access CLI and Web Plug-in to Server Administrator.	srvadmin-omilcore, srvadmin-deng, srvadmin-rac4 components, and srvadmin-omacore
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-StorageManagement — Storage Management RAID configuration utility and storage alert software.
srvadmin-storage	Storage Management — Provides Systems Management Storage Services.	srvadmin-omilcore, srvadmin-deng, and srvadmin-omacore
SA-WebServer — Provides web access to manage the server.
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
srvadmin-tomcat	Secure Port Server — Systems Management Managed Node Web Server package.	srvadmin-omilcore, srvadmin-deng, srvadmin-omacore, and srvadmin-jre
srvadmin-jre	Server Administrator Sun Java Runtime Environment — Systems management managed node Java runtime.	srvadmin-omilcore, srvadmin-deng, and srvadmin-omacore
srvadmin-omauth	Provides the authentication files.	srvadmin-omilcore
srvadmin-omcommon	Provides the common framework required by Server Administrator.	srvdamin-omilcore
srvadmin-omilcore	Server Administrator Web Server Install Core — This is the core install package. All Server Administrator Web Server RPMs require this RPM.
srvadmin-wsmanclient	Operating system-specific WSMan client package.	srvadmin-omcommon and srvadmin-omauth
Remote-Enablement — Manage and monitor the current system using some other remote system.
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
srvadmin-isvc	Server Administrator Instrumentation Service — Server Administrator provides a suite of systems management information for keeping supported systems on the 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-omacore	Server Administrator — Systems management managed mode core and CLI.	srvadmin-omilcore and srvadmin-deng
srvadmin-omcommon	Provides Common Framework required by Server Administrator.	srvadmin-omilcore
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 RPMs require this RPM.
srvadmin-ssa	Enables management of the system from a remote system on which Server Administrator Web Server is installed, using WS-Man interfaces.	srvadmin-omacore, srvadmin-omhip, and srvadmin-isvc.
srvadmin-syscheck	Package that checks the level of systems management support.	srvadmin-omilcore

What are the additional components that can be installed on a system that already has Server Administrator installed?

There are a few additional components that can be installed on a system that already has Server Administrator installed. For example, you can install Online Diagnostics on a system that has previously been installed with managed system software. On such a system, while uninstalling Server Administrator, only those RPM packages that are not required by any of the newly installed components are uninstalled. In the above example, Online Diagnostics requires packages such as - srvadmin-omilcore-X.Y.Z-N and srvadmin-hapi-X.Y.Z-N. These packages are not uninstalled during an uninstallation of Server Administrator.

In this case, if you try to install Server Administrator later by running the sh srvadmin-install.sh command, the following message is displayed:

Server Administrator version X.Y.Z is currently installed.

Installed components are:

srvadmin-omilcore-X.Y.Z-N
srvadmin-hapi-X.Y.Z-N

Do you want to upgrade Server Administrator to X.Y.Z? Press (y for yes| <Enter> to exit):

On pressing <y>, only those Server Administrator packages (in the above example), srvadmin-omilcore-X.Y.Z-N and srvadmin-hapi-X.Y.Z-N residing on the system are upgraded.

If you have to install other systems management components as well, the sh srvadmin-install.sh command has to be run once again.

What happens if I install the RPM package on an unsupported system or on an unsupported operating system?

If you try to install the RPM packages on an unsupported system or an unsupported operating system, you may see unpredictable behavior during the install, uninstall, or during use of the RPM package. Most of the RPM packages have been written and tested for supported systems and the Linux versions listed in the readme.

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 is installed and what is enabled to run. The following table displays the daemons that typically run for a full install:

Table 3. 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 SA-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.

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 4. Kernel Modules Loaded When Server Administrator Services are Started
Driver Name	Description
For a system with IPMI
dell_rbu	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 or SUSE Linux Enterprise Server
For a TVM system
dcdbas	Systems Management Base Driver
dell_rbu	BIOS Update Driver
For an ESM system
dcdbas	Systems Management Base Driver
dell_rbu	BIOS Update Driver
For support of Server Administrator Storage Systems
mptctl	Device driver for LSI RAID

When I run srvadmin-cm (Server Administrator Inventory Collector) it displays error messages. What do I do?

If you are using a system prior to 11G running on a supported 64-bit Linux operating system, the srvadmin-cm RPM installs only the 32-bit dependent RPMs. This is why the srvadmin-cm RPM displays error messages when it is run on a 64-bit operating system. To ensure srvadmin-cm functions as expected, the following RPMs must be preinstalled on servers prior to 11G running supported 64-bit Linux operating system.

glibc.i686

compat-libstdc++.i686

libstdc++.i686

zlib.i686

libxml2.i686

Emulex Network Adpater is not detected on Red Hat Enterprise Linux operating system. What do I do?

If you are using a system that is running Red Hat Enterprise Linux 5.9 (32-bit) operating system, the system experiences issues in detecting the Emulex Network Adapters if any of the following RPMs are missing,.

kernel-headers-2.6.18-346.el5.i386.rpm
glibc-headers-2.5-107.i386.rpm
glibc-devel-2.5-107.i386.rpm
gcc-4.1.2-54.el5.i386.rpm

For more information on Emulex Network Adapters, see the relevant Emulex Network Adapter or driver documentation.

Bienvenue

Bienvenue dans l’univers Dell

Red Hat Enterprise Linux or SUSE Linux Enterprise Server