Dell OpenManage Version 4.3 Installation and Security User's Guide
Installing and Upgrading Server Administrator
Server Administrator Installation Using Third-Party
Deployment Software
You can install Server Administrator by using several methods. The Dell Installation and Server Management CD provides installation scripts and RPM packages to install, upgrade, and uninstall 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.
|
NOTE: Server Administrator installation is not supported on Dell PowerEdge 300, 1300, 2300, 4300, 4350, 6300, or 6350 systems; PowerEdge SC1420, SC420, or 400SC SC systems; or, on systems containing a version of systems management software prior to version 3.0. If a previous version of systems management software is detected, you must first uninstall the systems management software on the system. |
You can use the Dell Installation and Server Management CD to perform an unattended and scripted silent installation of Server Administrator through the command line (using RPM packages) on systems running supported Red Hat® Enterprise Linux operating systems.
The following sections describe the Server Administrator general requirements.
Server Administrator runs, at a minimum, on each of the following operating systems:
|
NOTE: See the Server Administrator readme file on the Dell 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. |
Server Administrator must be installed on each system to be managed. You can then manage each system running Server Administrator locally or remotely through a supported Web browser.
A supported systems management protocol standard must be installed on the managed system before installing Server Administrator. On supported Red Hat Enterprise Linux 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 an IA32 system that is running a supported Red Hat Enterprise Linux operating system. Server Administrator can be installed and upgraded from the Dell Installation and Server Management CD using the Red Hat Enterprise Linux command line.
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 Linux version of the Dell OpenManage software is located on the CD in the root directory. Please read the license.htm 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 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 dcd*** device driver using DKS... [FAILED]
|
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.
The system displays a message identifying the running kernel. If it is not one of those listed in the Server Administrator readme file, then Server Administrator may need to use DKS to support it.
For Server Administrator 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 Server Administrator." |
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/misc 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/misc directory will contain two or more of the following files: dcdbas.*, dcdesm.*, dcdipm.*, or dcdtvm.*. |
|
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/dcd*.* files that you copied to system B are not removed. You must remove the files if they are no longer needed. |
This section explains how to install and upgrade Server Administrator using the following installation options:
|
NOTE: When installing an RPM package in Red Hat Enterprise Linux, to avoid warnings concerning the RPMGPG key, import the key with the following command: gpg --import /mnt/cdrom/srvadmin/linux/RPM-GPG-KEY |
If you have version 2.x of Dell OpenManage software installed, then you will have to uninstall the software completely before attempting to install the new version.
If you have versions 3.x to 4.2 of Dell OpenManage software installed, you can upgrade using the srvadmin-install.sh shell script or the preupgrade.sh shell script.
One way to upgrade is by using the srvadmin-install.sh shell script, which automatically upgrades while saving settings. After choosing the components to install, srvadmin-install.sh prompts you for an upgrade if it detects versions 3.x to 4.2.
If you have versions 3.x up to 4.2 of Dell OpenManage software installed, you can use a utility located on the Dell Installation and Server Management CD in the /srvadmin/linux/supportscripts subdirectory to uninstall the older software while saving your settings. To upgrade from these versions, perform the following steps:
This action removes the old version and preserves the settings. Refer to either the "Express Install" or the "Custom Install" section in this guide to proceed with the installation of the new version.
The Dell Installation and Server Management CD uses RPMs to install each component. The CD is divided into subdirectories to enable easy-to-execute Express Install or Custom Install paths.
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 are the following:
srvadmin/linux
srvadmin/linux/express-install-with-RAC3
srvadmin/linux/express-install-with-RAC4
srvadmin/linux/custom
srvadmin/linux/RPMS
srvadmin/linux/supportscripts
You can follow either of two paths for the Express Install. One is using the RPMs yourself to perform the express install, and the other is using a provided shell script to perform the express installation in silent and unattended mode.
or
To perform an express install with Dell Remote Access Controller 4 (DRAC 4), navigate to srvadmin/linux/express-install-with-RAC4 directory.
|
NOTE: If your server belongs to the group of PowerEdge x8xx servers (for example, PowerEdge1850, 2850, and so on), navigate to the express-install-with-RAC4 directory. If your server belongs to a supported group of earlier PowerEdge servers (for example, PowerEdge 1750, 2600, and so on), navigate to the express-install-with-RAC3 directory. |
rpm -ihv *.rpm
Server Administrator services do not start automatically.
sh srvadmin-install.sh --express
or
sh srvadmin-install.sh -x
|
NOTE: If a remote access controller is not present, then RAC software components will not be installed. |
Server Administrator services do not start automatically.
Server Administrator provides two custom installation paths. One is RPM-based, with pre-configured custom directories, and the other is script-based.
To facilitate RPMs-based custom installation, the CD provides a /srvadmin/linux/custom directory. This directory contains the following structure:
/srvadmin/linux/custom
/srvadmin-base (contains base Server Administrator with command-line interface)
/add-diagnostics (contains Online Diagnostics component packages)
/add-RAC3 (contains DRAC III component packages)
/add-RAC4 (contains DRAC 4 component packages)
/add-storageservices (contains Storage Management component packages)
/add-webserver (contains Web Server component packages)
The following is an example of a custom RPMs-based installation of Server Administrator, including the installation of Storage Management and Online Diagnostics components.
rpm -ihv srvadmin-base/*.rpm add-diagnostics/*.rpm add-storageservices/*.rpm
|
NOTE: add-RAC3 and add-RAC4 are mutually exclusive packages. |
Server Administrator services does not start automatically.
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]...
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.
[-d|--diags] installs Diagnostics components, including Base.
[-s|--storage] installs Storage components, including Base.
[-r|--rac] installs applicable RAC components, including Base.
[-w|--web] installs Web Server components, including Base.
The following is an example of a silent and unattended custom installation using the srvadmin-install.sh shell script.
sh srvadmin-install.sh --diags --storage (these are long options)
or
sh srvadmin-install.sh -ds (these are short options)
|
NOTE: Long options can be combined with short options, and vice-versa. |
Server Administrator services does not start automatically.
This procedure uses the installation shell script to prompt you for the installation of specific components through the installation.
When the installation is complete, the script will have an option for starting the services.
You can use The Dell 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 Express Install unattended installation option uses the /srvadmin/linux/express-install-with-RAC3 or /srvadmin/linux/express-install-with-RAC4 subdirectory of the Dell Installation and Server Management CD as the unattended installation package. RPM accesses the Dell 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.
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, see the procedure outlined in "Custom Install."
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.
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 of the installation types.
|
NOTE: RPM's -test feature does not perform any hardware verification. It will only check for RPM software dependencies. |
You can uninstall Server Administrator from the Red Hat Enterprise Linux command line. Additionally, you can perform an unattended uninstallation on multiple systems simultaneously.
You must be logged in as root.
An uninstallation script is located on the CD under the /srvadmin/linux/supportscripts directory. You can execute the script by typing srvadmin-uninstall.sh and then pressing <Return>, or you can follow this procedure to run the RPM itself:
|
NOTE: This RPM command does not prompt for confirmation to uninstall. After you enter this command, the product will be uninstalled. |
rpm e `rpm qa | grep srvadmin`
|
NOTE: The ticks in the previous command must be back-ticks. |
All of the Dell OpenManage software components will be uninstalled.
Some individual components of Dell OpenManage can be uninstalled without uninstalling all of Dell OpenManage. To uninstall a specific component, you can find the RPM files for the component in the corresponding custom directory. For example, in the add-diagnostics directory you can run the rpm -e command to remove all the associated diagnostics files. Following are examples:
To uninstall only the Web server, use the command:
rpm e srvadmin-iws
To uninstall diagnostics, use the command:
rpm e srvadmin-old
To uninstall storage, use the command:
rpm e srvadmin-storage
You can use third-party deployment software, such as Altiris Deployment Solution, to install Server Administrator onto supported Dell servers. To distribute and install Server Administrator using Altiris, start your Altiris application and import OpenManage_Jobs.bin located on the Installation and Server Management CD at \srvadmin\support\Altiris. Specify a job folder into which 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 servers that are managed from within your Altiris Deployment Solution.