Dell OpenManage Version 5.1 Installation and Security User's Guide
Using Dell OpenManage with VMware® ESX Server Software
Managed System Software Installation Using Third-Party
Deployment Software
You can install managed systems software by one of two methods. The Dell PowerEdge Installation and Server Management CD provides installation scripts and RPM packages to install, upgrade, and uninstall Dell OpenManage Server Administrator and other managed system software components on your managed system. Additionally, you can install Server Administrator on multiple systems through an unattended installation across a network.
The first install method uses the provided custom install script srvadmin-install.sh. This script allows unattended express installation and custom, unattended, or interactive installation. By including the srvadmin-install.sh script in your Linux scripts you may install Server Administrator on single or multiple systems, in attended or unattended mode, and locally or across a network.
The second install method uses the Server Administrator RPM packages provided in the custom directories and the Linux rpm command. This allows custom interactive installation. You may write Linux scripts that install Server Administrator on a single or multiple systems through an unattended installation locally or across a network.
Using a combination of the two install methods is not recommended and may require that you manually install required Server Administrator RPM packages provided in the custom directories, using the Linux rpm command.
![]() |
NOTE: See the Dell PowerEdge Installation and Server Management CD's readme_ins.txt file for a list of the systems that are currently supported. |
You can use the Dell PowerEdge Installation and Server Management CD to perform an unattended and scripted silent installation of managed systems software through the command line (using RPM packages) on systems running supported Red Hat Enterprise Linux and SUSE Linux Enterprise Server operating systems.
The following sections describe the general requirements for managed systems software.
The managed systems software runs, at a minimum, on each of the following operating systems:
![]() |
NOTE: See the Server Administrator readme file on the Dell PowerEdge Installation and Server Management CD or the Dell OpenManage Server Administrator Compatibility Guide on the Documentation CD for the latest detailed list of the Server Administrator services that are supported on each supported operating system. |
Managed systems software must be installed on each system to be managed. You can then manage each system running the managed systems software locally or remotely through a supported Web browser.
![]() |
NOTE: See the Dell Remote Access Controller 4 User's Guide, the Dell Remote Access Controller 5 User's Guide, or the Dell Embedded Remote Access Controller/MC User's Guide for complete software and hardware requirements. |
A supported systems management protocol standard must be installed on the managed system before installing Server Administrator. On supported Red Hat Enterprise Linux and SUSE Linux Enterprise Server operating systems, Server Administrator only supports the SNMP systems management standard. You must install the SNMP package provided with the operating system. CIM and WMI are unavailable.
![]() |
NOTE: For information about installing a supported system management protocol standard on your managed system, see your operating system documentation. |
This section explains how to install, upgrade, and uninstall Server Administrator on a system that is running a supported Red Hat Enterprise Linux or a supported SUSE Linux Enterprise Server operating system. Server Administrator can be installed and upgraded from the Dell PowerEdge Installation and Server Management CD using scripts or RPM commands.
Additionally, Server Administrator includes Dynamic Kernel Support (DKS), a feature that automatically builds a device driver for a running kernel if Server Administrator detects that none of its prebuilt device drivers support that kernel. This section includes the following topics:
The software license for the Red Hat Enterprise Linux and SUSE Linux Enterprise Server version of the Dell OpenManage software is located on the CD in the root directory. Read the license.txt file. By installing or copying any of the files on this CD, you are agreeing to the terms found in this file. This file is also copied to the root of the software tree where you choose to install the Dell OpenManage software.
Server Administrator provides precompiled device drivers for the precompiled kernels listed in the Server Administrator readme file on the Dell PowerEdge Installation and Server Management CD. If the running kernel is not one of the precompiled kernels listed in the readme file, or if the running kernel is reconfigured and recompiled in such a way that none of the precompiled Server Administrator device drivers support the recompiled kernel, then Server Administrator may need to use its DKS feature to support the running kernel.
If you see the following message during Server Administrator Device Drivers startup, then Server Administrator attempted to use its DKS feature, but was unable to use the feature because certain prerequisites were not met:
Building <driver> using DKS... [FAILED]
where <driver> is dcdbas or dell_rbu
![]() |
NOTE: Server Administrator logs messages to the /var/log/messages log file. |
To use DKS, you should identify which kernel you have running, then check the DKS prerequisites.
uname -r
The system displays a message identifying the running kernel. If it is not one of those listed in the managed system software readme file, then the managed system software may need to use DKS to support it.
For managed system software to use DKS, the following dependencies must be met before starting Server Administrator.
When these prerequisites have been met, DKS will automatically build a device driver when needed during Server Administrator startup.
![]() |
NOTE: Unsupported kernels are kernels that are not supported by a precompiled device driver. If you are running a supported kernel, see "Installing and Upgrading Managed System Software." |
To enable Server Administrator to support a kernel that is not supported by a precompiled device driver and is loaded after Server Administrator has been installed, perform the following steps:
Server Administrator builds a device driver for the kernel running on the system the first time that Server Administrator starts after the kernel is loaded. By default, Server Administrator starts during system startup.
When Server Administrator dynamically builds a device driver for the running kernel, it installs the device driver into the /lib/modules/<kernel>/kernel/drivers/firmware directory, where <kernel> is the kernel name (returned by typing uname -r). If you have a system running the same kernel for which a device driver was built, you can copy the newly built device driver to the /var/omsa/dks/<kernel> directory on the other system for use by Server Administrator. This action allows Server Administrator to use DKS on multiple systems without having to install the kernel source on every system.
An example is the following scenario: System A is running a kernel that is not supported by one of the Server Administrator precompiled device drivers. System B is running the same kernel. Perform the following steps to build a device driver on system A and copy the device driver to system B for use by Server Administrator:
Server Administrator builds a device driver for the kernel running on system A during startup.
![]() |
NOTE: The /lib/modules/<kernel>/kernel/drivers/firmware directory may contain one or more of the following files: dcdbas.* or dell_rbu.* |
![]() |
NOTE: You might have to create the /var/omsa/dks/<kernel> directory on system B. For example, if the kernel name is 1.2.3-4smp, you can create the directory by typing: mkdir -p /var/omsa/dks/1.2.3-4smp |
Server Administrator detects that the device driver you copied to the /var/omsa/dks/<kernel> directory supports the running kernel and uses that device driver.
![]() |
NOTE: You can also use this procedure when upgrading Server Administrator if the new version of Server Administrator does not support the running kernel with a precompiled device driver. |
![]() |
NOTE: When you have uninstalled Server Administrator from system B, the /var/omsa/dks/<kernel>/*. files that you copied to system B are not removed. You must remove the files if they are no longer needed. |
Server Administrator provides precompiled device drivers for the "Gold" releases of supported Red Hat Enterprise Linux operating systems. Red Hat Enterprise Linux supports loading device drivers built for the "Gold" release, on the Update releases. This means Server Administrator does not have to ship precompiled device drivers for every Red Hat Enterprise Linux Update release and users are not forced to use DKS in order to run Server Administrator on every system that is running a Red Hat Enterprise Linux Update release. However, loading a device driver built for the "Gold" release of Red Hat Enterprise Linux (version 3) on an Update release may taint the kernel. If the kernel on a system running a Red Hat Enterprise Linux (version 3) Update release has been tainted by this device driver load process, Server Administrator's init script command restart-forcekernelmatch can be used to force DKS to be used in this situation. DKS will build device drivers that do not taint the running kernel.
After Server Administrator services have been started, perform the following steps on Red Hat Enterprise Linux Update releases to determine if the kernel has been tainted:
lsmod
If you see Tainted: GF in the first line of the output as in the following message, the running kernel is tainted:
Module Size Used by Tainted: GF
The "tainted" status may be caused by the Server Administrator device driver load process.
After the installation of Server Administrator, perform the following steps to force DKS to be used on Red Hat Enterprise Linux Update releases to build device drivers for the running kernel, if needed, so that they do not taint the kernel:
/etc/init.d/instsvcdrv restart-forcekernelmatch
This command will first stop the Server Administrator device drivers. It will then search for precompiled device drivers to load, by checking for precompiled device drivers built for a kernel whose name is an exact match as the name of the running kernel. If it fails to find an exact match, it will use DKS to build device drivers for the running kernel. Finally, the command will restart the Server Administrator device drivers.
![]() |
NOTE: The system must be rebooted to clear the kernel "tainted" status. |
The Server Administrator Instrumentation Service of Server Administrator requires the OpenIPMI device driver in order to provide IPMI-based information and functionality. It also requires a minimum version of the OpenIPMI device driver. The minimum version required is defined based on the Red Hat Enterprise Linux or SUSE Linux Enterprise Server operating system.
This requirement is checked and enforced by Server Administrator at three instances. Two of the instances are during installation, while the third is a run-time step. The instances are:
![]() |
NOTE: SUSE Linux Enterprise Server (version 10) contains the required version of IPMI module in the default kernel itself. You do not need to install the IPMI RPM. |
During custom installation of Server Administrator using the srvadmin-install.sh shell script, the script automatically calls another shell script called srvadmin-openipmi.sh, to ensure that a sufficient version of the OpenIPMI device driver (for example, a version that is equal to or greater than the minimum version of the OpenIPMI device driver that is required by the Server Administrator Instrumentation Service) is currently installed on the system. If a sufficient version is not found, the srvadmin-install.sh shell script calls the srvadmin-openipmi.sh shell script again to attempt to install a sufficient version. If the attempt fails for any reason, an appropriate error message is displayed with instructions describing how to resolve the error. You must resolve errors, if any, before re-running the srvadmin-install.sh shell script to install Server Administrator.
To assist in the correct order of RPM installation, the srvadmin-hapi RPM is dependent on one of the srvadmin-ipmi RPMs. Each srvadmin-ipmi RPM is distribution-specific and depends on a distribution-specific OpenIPMI RPM. The srvadmin-hapi RPM will not install unless the RPM dependencies are met.
During installation of Server Administrator using RPM, the srvadmin-hapi RPM will check if a sufficient version of the OpenIPMI device driver is currently installed on the system. If a sufficient version is not found, the srvadmin-hapi RPM will fail to install and will display an error message stating that you must install/upgrade the OpenIPMI device driver. In such a case, RPMs that depend on the srvadmin-hapi RPM will also fail to install. In such cases, you must install/upgrade the OpenIPMI driver by performing the following additional steps:
sh srvadmin-openipmi.sh install
Re-attempt to install the srvadmin-hapi RPM and any other RPMs that failed to install as they depend on the srvadmin-hapi RPM. Perform the following steps:
rpm qa | grep srvadmin
The query displays a list of all installed Server Administrator packages.
rpm ihv srvadmin-hapi*.rpm srvadmin-isvc*.rpm srvadmin-omhip*.rpm srvadmin-<any-other-packages>*.rpm
Alternately, during installation of the srvadmin-hapi RPM using RPM, if the OpenIPMI RPM for a version of the OpenIPMI driver that meets the minimum version of the OpenIPMI driver that is required by Server Administrator is currently installed on the system, but OpenIPMI driver modules have not yet been built and installed for the given version of the OpenIPMI driver because the kernel-source RPM is required but is not currently installed, the srvadmin-hapi RPM will fail to install and will display an error message. The error message will state that you need to install the kernel-source RPM and build the OpenIPMI driver. In such a case, any RPMs that depend on the srvadmin-hapi RPM will also fail to install. You must then install the kernel-source RPM, and build and install the OpenIPMI driver modules, by performing the following additional steps:
On systems running Red Hat Enterprise Linux (version 4) and SUSE Linux Enterprise Server, the kernel*-devel RPMs provide the necessary source for building kernel modules.
rpm ihv kernel*.rpm
sh srvadmin-openipmi.sh install
Re-attempt to install the srvadmin-hapi RPM and any RPMs that failed to install as they depend on the srvadmin-hapi RPM.
After Server Administrator is installed, the Server Administrator Instrumentation Service will do a run-time check of the OpenIPMI device driver whenever it is started. The Server Administrator Instrumentation Service is started whenever you run either the srvadmin-services.sh start or srvadmin-services.sh restart commands, or you restart the system (during which the Server Administrator Instrumentation Service is started).
While Server Administrator installation will block the installation of Server Administrator if a sufficient version of the OpenIPMI device driver is not currently installed on the system, it is still possible, though not typical, that a user can uninstall or replace a sufficient version of the OpenIPMI device driver after Server Administrator has been installed. Server Administrator cannot prevent this.
To account for a user uninstalling or replacing a sufficient version of the OpenIPMI device driver after Server Administrator has been installed, the Server Administrator Instrumentation Service checks the OpenIPMI device driver version whenever it is started. If a sufficient version of the OpenIPMI device driver is not found, the Server Administrator Instrumentation Service will degrade itself so that it does not provide any of its IPMI-based information or functionality. Primarily, this means that it will not provide any probe data (for example, fans, temperatures, and voltage probe data).
If you know or suspect that the OpenIPMI device driver on the system is not sufficient, you can run the srvadmin-openipmi.sh shell script on the Dell PowerEdge Installation and Server Management CD to install a sufficient version by, again, performing the following steps:
sh srvadmin-openipmi.sh install
If you are unsure as to whether or not the OpenIPMI device driver on the system is sufficient, run the srvadmin-openipmi.sh status command instead. Rather than attempting to install or upgrade the OpenIPMI device driver, if necessary, which is what the srvadmin-openipmi.sh install command does, the srvadmin-openipmi.sh status command displays information that informs you whether or not the OpenIPMI device driver on the system is sufficient or not. After running the srvadmin-openipmi.sh status command, you can then decide whether or not you need and want to run the srvadmin-openipmi.sh install command.
This section explains how to install and upgrade managed system software using the following installation options:
![]() |
NOTE: When installing an RPM package in Red Hat Enterprise Linux or SUSE Linux Enterprise Server, to avoid warnings concerning the RPMGPG key, import the key with a command similar to the following: |
rpm --import /mnt/cdrom/srvadmin/linux/RPM-GPG-KEY
If your system came with a factory installed Red Hat Enterprise Linux (versions 3 and 4) or SUSE Linux Enterprise Server (versions 9 and 10) operating system, see the Server Administrator installation readme file (readme_ins.txt) on the Dell PowerEdge Installation and Server Management CD for information on any RPMs that you need to manually install prior to installing managed system software. In most cases you will not need to manually install any RPMs. See the readme file to be sure.
If your system did not come with a factory installed Linux operating system, and you did not install a Red Hat Enterprise Linux (versions 3 and 4) or SUSE Linux Enterprise Server (version 9 and 10) operating system using Server Assistant, then you need to manually install the prerequisite RPMs prior to installing managed system software. For convenience, these RPM files are provided on the Dell PowerEdge Installation and Server Management CD or package. Navigate to the appropriate /srvadmin/linux/RPMS/supportRPMS/operating-system subfolder for your specific Red Hat Enterprise Linux (versions 3 and 4) or SUSE Linux Enterprise Server (versions 9 and 10) operating system and run
rpm -Uvh * to install these RPM files before installing managed system software.
The Dell PowerEdge Installation and Server Management CD uses RPMs to install each component. The CD is divided into subdirectories to enable easy Custom Installs.
If you would like to review the software before you install it, follow this procedure:
The directories on the CD that pertain to Red Hat Enterprise Linux and SUSE Linux Enterprise Server are the following:
srvadmin/linux
srvadmin/linux/custom
srvadmin/linux/RPMS
srvadmin/linux/supportscripts
Use the provided shell script to perform the express installation in silent and unattended mode.
sh srvadmin-install.sh --express
or
sh srvadmin-install.sh -x
![]() |
NOTE: Just before the Server Administrator RPMs are installed, the srvadmin-install.sh shell script automatically calls the srvadmin-openipmi.sh shell script to ensure that a sufficient version of the OpenIPMI driver is currently installed on the system. If a sufficient version is not found, the srvadmin-install.sh shell script calls the srvadmin-openipmi.sh shell script to attempt to install a sufficient version. If the attempt fails for any reason, an appropriate error message will be displayed with instructions describing how to resolve the error. After resolving any error, you should then re-run the srvadmin-install.sh shell script to install the managed system components. |
Server Administrator services do not start automatically.
Managed system software provides two custom installation paths. One is RPM-based, with pre-configured custom directories, and the other is shell script-based.
Using Pre-configured Custom Directories to Perform the Custom Installation
See Table 7-1 for details about using the RPMs to perform a custom installation using pre-configured custom directories.
Table 7-1. Custom Installation Using Pre-Configured Directories
The following is an example of custom RPMs-based installation of Server Administrator, including the installation of the Storage Management Service components.
rpm -ihv srvadmin-base/*.rpm add-openipmi-RHEL4/srvadmin-ipmi*.rpm add-storageservices/*.rpm
![]() |
NOTE: This command is for the RedHat Enterprise Linux (Version 4) operating system. Apply the operating system specific srvadmin-ipmi RPM corresponding to your system. |
Server Administrator services do not start automatically.
sh srvadmin-services start
Using the Shell Script to Perform the Custom Installation
You can run the Server Administrator Custom Install script in interactive mode or in silent and unattended mode.
The basic usage of the script is:
srvadmin-install.sh [OPTION]...
Server Administrator Custom Installation Utility
This utility will run in interactive mode if you do not specify any options, and it will run silently if you provide one or more options.
The options are:
[-x|--express] installs all components including RAC. Any other options passed will be ignored.
[-b|--base] installs Base components.
[-s|--storage] installs Storage components, including Base.
[-r|--rac] installs applicable RAC components, including Base.
[-w|--web] installs Web Server components, including Base.
[-u|--update] updates applicable components in upgrade of prior versions (same as -x for upgrade).
[-a|--autostart] starts the installed services after components have been installed.
[--prefix PATH] installs the selected components to the specified "PATH". This option does not apply to OpenIPMI RPMs as they are not relocatable.
Using the Custom Install Script To Run in the Silent and Unattended Mode
The following is an example of a silent and unattended custom installation using the srvadmin-install.sh shell script.
sh srvadmin-install.sh --storage (these are long options)
or
sh srvadmin-install.sh -s (these are short options)
![]() |
NOTE: Long options can be combined with short options, and vice-versa. |
![]() |
NOTE: Just before the Server Administrator RPMs are installed, the srvadmin-install.sh shell script automatically calls the srvadmin-openipmi.sh shell script to ensure that a sufficient version of the OpenIPMI driver is currently installed on the system. If a sufficient version is not found, the srvadmin-install.sh shell script calls the srvadmin-openipmi.sh shell script to attempt to install a sufficient version. If the attempt fails for any reason, an appropriate error message will be displayed with instructions describing how to resolve the error. After resolving any error, you should then re-run the srvadmin-install.sh shell script to install the managed system components. |
Server Administrator services do not start automatically.
sh srvadmin-services start
Using the Shell Script to Perform the Custom Installation in Interactive Mode
This procedure uses the installation shell script to prompt you for the installation of specific components through the installation.
When the installation is completed, the script will have an option for starting the services.
![]() |
NOTE: Just before the Server Administrator RPMs are installed, the srvadmin-install.sh shell script automatically calls the srvadmin-openipmi.sh shell script to ensure that a sufficient version of the OpenIPMI driver is currently installed on the system. If a sufficient version is not found, the srvadmin-install.sh shell script calls the srvadmin-openipmi.sh shell script to attempt to install a sufficient version. If the attempt fails for any reason, an appropriate error message will be displayed with instructions describing how to resolve the error. After resolving any error, you should then re-run the srvadmin-install.sh shell script to install the managed system components. |
You can use The Dell PowerEdge Installation and Server Management CD's Express Install and Custom Install options for the unattended installation procedure.
Unattended installation allows you simultaneously to install Server Administrator on multiple systems. You can perform an unattended installation by creating an unattended installation package that contains all of the necessary managed system software files.
The unattended installation package is distributed to the remote systems using a software distribution tool from an ISV. After the package is distributed, RPM installs the software.
The custom unattended installation package is located in the directory you created as detailed in the section "Using the Shell Script to Perform the Custom Installation in Interactive Mode." This directory contains all the RPMs for the managed system software components for distribution.
RPM has a test feature that verifies software dependencies without actually installing any software. To execute this dependency check, type rpm ihv *.rpm -test. This command is valid for all the the types of installation.
![]() |
NOTE: The rpm command's -test feature does not perform any hardware verification. It will only check for RPM software dependencies. |
The Express Install unattended installation option uses the /srvadmin/linux/supportscripts and the /srvadmin/linux/RPMS subdirectories of the Dell PowerEdge Installation and Server Management CD as the unattended installation package. RPM accesses the Dell PowerEdge Installation and Server Management CD to install all required Server Administrator components on selected remote systems.
When the ISV software runs, it executes the RPMs to install Server Administrator on each remote system.
![]() |
NOTE: If a sufficient version of the OpenIPMI driver is currently not installed on your remote systems, the srvadmin-hapi RPM will fail to install and will display an error message stating that you must install/upgrade the OpenIPMI driver. In such a case, any RPMs that depend on the srvadmin-hapi RPM will also fail to install. In such cases, you should also distribute the OpenIPMI-related RPM files in the srvadmin/linux/custom/add-openipmi-operating-system subdirectory that is applicable to your operating system. Copy the RPMs from the applicable OpenIPMI subdirectory to the same directory on your target systems from where you distribute the custom unattended installation package. |
The Custom Install unattended installation option creates an unattended installation package in a directory on your system's hard drive. To create an unattended installation package, use the copy capability described in the section "Using the Shell Script to Perform the Custom Installation in Interactive Mode" to create a custom directory with the RPM's you want to install. This directory will be your unattended installation directory. Copy the RPMs in the applicable OpenIPMI subdirectory to the same directory on your target systems where you distribute the custom unattended installation package.
The custom unattended installation package is located in the directory you created in the preceding step 6 of the custom installation (see "Custom Install"). This directory contains all of the RPMs for the managed system software components to distribute.
If your system is running Dell OpenManage software prior to version 4.2, uninstall the current version before attempting to install the new version.
For Dell OpenManage software versions 4.3 and later, you can upgrade your system using RPM commands or the srvadmin-install.sh shell script. Ensure that all installed components are upgraded when you perform either procedure.
![]() |
NOTE: Use of the install script, srvadmin-install.sh is recommended. |
If the CD does not mount automatically, use a command similar to the following:
mount /dev/cdrom/ mnt/cdrom
mount /dev/cdrom /media/cdrom
cd /media/cdrom/srvadmin/linux/RPMS/<os>
Where <os> is RHEL3 or RHEL4 or SLES9 or SLES10. Enter the appropriate directory name that applies to your system.
Upgrade with the following command if you are upgrading from version 5.0:
rpm -Uhv `rpm -q --queryformat "%{NAME}* " \`rpm -qa | grep srvadmin\``
If upgrading from 4.x, use a command like the following:
rpm -Uhv openipmi/openipmi*.rpm srvadmin-ipmi*.rpm `rpm -q --queryformat "%{NAME}* " \`rpm -qa | grep srvadmin\``
![]() |
NOTE: The commands upgrade the existing Server Administrator RPM packages on your system. Starting with version 5.0, the openipmi and srvadmin-ipmi packages are new requirements for Server Administrator. The dkms RPM package under the openipmi sub-directory depends on the openipmi package. You may have to adjust the commands depending on the status of these packages on your system. |
To upgrade all the previously installed packages using individual RPMs, perform the following steps:
rpm -qa | grep srvadmin
The query displays a list of all installed packages, including any existing or older versions.
For example:
srvadmin-omilcore-4.3.0-1.386.rpm
srvadmin-hapi-4.3.0-1.386.rpm
srvadmin-deng-4.3.0-1.386.rpm
srvadmin-isvc-4.3.0-1.386.rpm
...
For example:
rpm -Uhv srvadmin-omilcore-4.3.0-1.386.rpm srvadmin-hapi-4.3.0-1.386.rpm srvadmin-deng-4.3.0-1.386.rpm srvadmin-isvc-4.3.0-1.386.rpm
If the OpenIPMI driver is currently not installed on the system, or the version of the OpenIPMI driver installed on the system is less than the minimum version that is required by Server Administrator, the srvadmin-hapi RPM will fail to upgrade and will display an error message stating that you must install/upgrade the OpenIPMI driver. In such a case, any RPMs that depend on the srvadmin-hapi RPM will also fail to upgrade. In such cases, you must install/upgrade the OpenIPMI driver by performing the following additional steps:
sh srvadmin-openipmi.sh install
Reattempt to upgrade the srvadmin-hapi RPM and any other RPMs that failed to upgrade as they depend on the srvadmin-hapi RPM. Perform the following steps:
rpm -qa | grep srvadmin
The query displays a list of all installed Server Administrator packages. Those that have already been upgraded will display the new version number. Those that have not yet been upgraded will display the old version number.
rpm -Uhv srvadmin-hapi*.rpm srvadmin-isvc*.rpm srvadmin-omhip*.rpm srvadmin-<any-other-packages>*.rpm
If the OpenIPMI RPM for a version of the OpenIPMI driver that meets the minimum version of the OpenIPMI driver that is required by Server Administrator is currently installed on the system, but the OpenIPMI driver modules have not yet been built and installed for the given version of the OpenIPMI driver because the kernel-source RPM is required but is not currently installed, the srvadmin-hapi RPM will fail to upgrade and will display an error message. The error message will state that you need to install the kernel-source RPM and build the OpenIPMI driver. In such a case, any RPMs that depend on the srvadmin-hapi RPM will also fail to upgrade. You must install the kernel-source RPM, and build and install the OpenIPMI driver modules, by performing the following additional steps:
rpm -ihv kernel*.rpm
sh srvadmin-openipmi.sh install
Reattempt to upgrade the srvadmin-hapi RPM and any RPMs that failed to upgrade as they depend on the srvadmin-hapi RPM. Perform the steps described in page 113.
cd /mnt/cdrom/srvadmin/linux/supportscripts
cd /media/cdrom/srvadmin/linux/supportscripts.
sh srvadmin-install.sh
The script detects any previous version of Server Administrator. If a previous version is installed, a message appears stating the current version and installed components.
For example:
Server Administrator version 4.4.0 is currently installed.
Installed components are:
- srvadmin-omilcore
- srvadmin-hapi
- srvadmin-deng
- srvadmin-isvc
Next, the script prompts you with the following message:
Do you want to upgrade Server Administrator to 5.1?
Press ('y' for yes | 'Enter' to exit):
Server Administrator is upgraded to version 5.1.
![]() |
NOTE: Just before the Server Administrator RPMs are upgraded, the srvadmin-install.sh shell script automatically calls the srvadmin-openipmi.sh shell script to ensure that a sufficient version of the OpenIPMI driver is currently installed on the system. If a sufficient version is not found, the srvadmin-install.sh shell script calls the srvadmin-openipmi.sh shell script to attempt to install a sufficient version. If the attempt fails for any reason, an appropriate error message will be displayed with instructions describing how to resolve the error. After resolving any error, you should then re-run the srvadmin-install.sh shell script to upgrade the managed system components. |
You can uninstall managed system software from the Red Hat Enterprise Linux or SUSE Linux Enterprise Server command line. Additionally, you can perform an unattended uninstallation on multiple systems simultaneously.
You must be logged in as root.
An uninstallation script is installed when Server Administrator is installed. You can execute the script by typing srvadmin-uninstall.sh and then pressing <Enter>.
![]() |
NOTE: When executed, the srvadmin-uninstall.sh will not attempt to uninstall the OpenIPMI driver even if the OpenIPMI driver was installed or upgraded during previous execution of the srvadmin-install.sh script or the srvadmin-openipmi.sh script. |
Some individual components of Dell OpenManage can be uninstalled without uninstalling all of Dell OpenManage. Following are examples:
To uninstall only the Web server, use the command:
rpm e `rpm -qa | grep srvadmin-iws`
To uninstall storage, use the command:
rpm e `rpm -qa | grep srvadmin-storage`
![]() |
NOTE: Dell OpenManage installation with VMware ESX Server software requires special steps. These steps vary depending on the Dell OpenManage version and ESX Server version; only a limited number of combinations are supported. |
See the VMware Systems Compatibility Guide located in the Resource Center at www.dell.com/vmware to determine the versions of ESX Server software compatible with this release of Dell OpenManage. Each ESX Server release from Dell has an associated Dell VMware ESX Server Deployment Guide, also posted at this Web location. Instructions for installing supported versions of Dell OpenManage available at the time of that ESX Server release are found in that ESX Server release's Deployment Guide. Instructions for installing any supported subsequently released versions of Dell OpenManage are posted to the same location in a separate, clearly labeled document.
You can use third-party deployment software, such as Altiris Deployment Solution, to install managed system software onto supported Dell servers. To distribute and install managed system software using Altiris, start your Altiris application and import OpenManage_Jobs.bin located on the Dell PowerEdge Installation and Server Management CD at \srvadmin\support\Altiris. Specify a job folder into which you want to import it. You might need to modify the Run Script and Copy File tasks to match your deployment environment. Once complete, you can then schedule your job to run on the supported Dell systems that are managed from within your Altiris Deployment Solution.