Dell OpenManage Server Administrator Version 7.
Notes and Cautions NOTE: A NOTE indicates important information that helps you make better use of your computer. CAUTION: A CAUTION indicates potential damage to hardware or loss of data if instructions are not followed. ___________________ Information in this document is subject to change without notice. © 2011 Dell Inc. All rights reserved. Reproduction of these materials in any manner whatsoever without the written permission of Dell Inc. is strictly forbidden.
Contents 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . Dell OpenManage Systems Management Software Security Features . . . . . . . . . . . . . . . . . . . . Other Documents You Might Need 13 13 . . . . . . . . . . . . . 15 . . . . . . . . . . . . . . . 17 . . . . . . . . . . . . . . . . . . 17 Preinstallation Setup . Prerequisite Checker 9 . . . . . . . . . . . Getting Technical Assistance . 2 . . . 9 Installation Requirements . . . . . . . . . . . . . . . .
Installing WinRM . . . . . . . . . . . . . . . . . . 30 Certificate Authority — Signed/Self-Signed Certificate 30 Dependent RPMs for Remote Enablement . . . . . 36 Post-Installation Configuration for Remote Enablement 38 Winbind Configuration for openwsman and sfcb for Red Hat Enterprise Linux Operating Systems . . . . . . . . . . . 40 Winbind Configuration for openwsman and sfcb for SUSE Linux Enterprise Server Operating System . . . . . . . . . . . 42 Workaround for the Libssl Issue . 3 . . . . .
Uninstalling Managed System Software . . . . . . . . 64 Uninstalling Managed System Software Using Dell-Provided Media . . . . . . . . . . . . . . . . . . . . . . . . 65 Uninstalling Managed System Software Features Using the Operating System . . . . . . . . . . . . . . . . . . 66 Unattended Uninstall Using the Product GUID . . . 66 Unattended Uninstallation of Managed System Software 66 4 Installing Managed System Software on Supported Linux and VMware ESX . . . . . 69 Software License Agreement .
5 Installing Managed System Software On Microsoft Windows Server 2008 Core and Microsoft Hyper-V Server . . . . . . . . . . . . 87 Running Prerequisite Checker In CLI Mode . . . . . . . 88 . . . . . 88 Installing Managed System Software in CLI Mode Uninstalling Systems Management Software . 6 87 Installing Dell OpenManage Software on VMware ESXi . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Using the vSphere CLI . . . . . . . . . . . . . . .
8 Using Microsoft Active Directory Controlling Access to Your Network 101 . . . . . 101 . . . . . . . . . . Active Directory Schema Extensions . 101 . . . . . . . . . Overview of the Active Directory Schema Extensions 102 Extending the Active Directory Schema Using the Dell Schema Extender . . . . . . . . . 109 . . . . . . . . . 110 Active Directory Users and Computers Snap-In . . 115 Adding Users and Privileges to Active Directory . 117 . . . . . . .
Contents
1 Introduction This guide provides information on: • Installing Dell OpenManage Server Administrator (OMSA) on managed systems. • Installing and using the Remote Enablement feature. • Managing remote systems using OpenManage Server Administrator Web Server. • Configuring your system before and during a deployment or upgrade. NOTE: If you are installing management station and managed system software on the same system, install identical software versions to avoid system conflicts.
The custom setup option enables you to select the software components you want to install. Table 1-1 lists the various managed system software components that you can install during a custom installation. For more information, see "Custom Installation." Table 1-1.
Table 1-1. Managed System Software Components (continued) Component What is installed Deployment scenario Systems on which to be installed Storage Management Server Administrator Storage Management Install to implement hardware RAID solutions and configure the storage components attached to your system. For more information on Storage Management, see the Dell OpenManage Server Administrator Storage Management User’s Guide in the docs directory or at support.dell.com/support/ edocs/software/omswrels.
Table 1-1. Managed System Software Components (continued) Component What is installed Deployment scenario Systems on which to be installed Remote Access Controller Server Administrator CLI and Instrumentation Service and iDRAC or DRAC 5, or DRAC 4 (depending on the type of your Dell PowerEdge system) Install to receive e-mail alerts for warnings or errors related to voltage, temperature, and fan speed.
Security Features Dell OpenManage systems management software components provide the following security features: • Authentication for users through hardware-stored user IDs and passwords, or by using the optional Microsoft Active Directory. • Support for Network Information Services (NIS), Winbind, Kerberos, and Lightweight Directory Access Protocol (LDAP) authentication protocols for Linux operating systems. • Role-based authority that allows specific privileges to be configured for each user.
• The Dell Systems Build and Update Utility User’s Guide provides information on using the Systems Build and Update Utility. • The Dell Systems Software Support Matrix provides information about the various Dell systems, the operating systems supported by these systems, and the Dell OpenManage components that can be installed on these systems. • The Dell OpenManage Server Administrator User's Guide describes the installation and use of Server Administrator.
• The Dell Update Packages User's Guide provides information about obtaining and using the Dell Update Packages for Windows and Linux as part of your system update strategy. • The Dell OpenManage Server Update Utility User's Guide provides information on using the Dell OpenManage Server Update Utility. • The software kit (DVD) contains readme files for applications found on the media.
Introduction
2 Preinstallation Setup Ensure that you perform the following before installing Server Administrator: • Read the installation instructions for your operating system. • Read the "Installation Requirements" to ensure that your system meets or exceeds the minimum requirements. • Read the applicable Dell OpenManage readme files and the Dell Systems Software Support Matrix located at support.dell.com/support/edocs/software/omswrels.
You can run the prerequisite checker silently by executing runprereqchecks.exe /s from the SYSMGMT\srvadmin\windows\PreReqChecker directory on the Dell Systems Management Tools and Documentation DVD. After running the prerequisite checker, a HTML file (omprereq.htm) is created in the %Temp% directory. This file contains the results of the prerequisite check. The Temp directory is located at X:\Documents and Settings\username\Local Settings\Temp.
Table 2-1. Return Codes While Running the Prerequisite Checker Silently (continued) Return Code Description -3 The user does not have Administrator privileges. The prerequisite checker does not run. -4 Not an implemented return code. -5 The prerequisite checker does not run. The user failed to change the working directory to %TEMP%. -6 The destination directory does not exist. The prerequisite checker does not run. -7 An internal error has occurred. The prerequisite checker does not run.
• Domain Name System (DNS) or Windows Internet Name Service (WINS) server running on your system can cause a warning condition for RAC software. See the relevant section in Server Administrator readme for more information. • Do not install managed system and management station RAC components on the same system. Install only the managed system RAC components, as they offer the required functionality.
Table 2-2.
The MUI Pack is a set of language-specific resource files that can be added to the English version of a supported Windows operating system. Dell OpenManage 7.0 installer supports only six languages: English, German, Spanish, French, Simplified Chinese, and Japanese. NOTE: When MUI is set to non-Unicode languages like Simplified Chinese, set the system locale to Simplified Chinese. This enables the prerequisite checker messages to be displayed.
• The Server Administrator Remote Access Controller service requires remote access controller (RAC) be installed on the managed system. See the relevant Dell Remote Access Controller User’s Guide for complete software and hardware requirements. NOTE: The RAC software is installed as part of the Typical Setup installation option, provided the managed system meets all of the RAC installation prerequisites.
Table 2-3 shows the availability of the systems management standards for each supported operating system. Table 2-3. Availability of Systems Management Protocol by Operating Systems Operating System SNMP CIM/WMI Supported Microsoft Windows operating systems. Available from the Always installed operating system installation media. Supported Red Hat Install the SNMP Enterprise Linux operating package provided systems. with the operating system. Available.
Enabling Windows Installer Logging Service Windows includes a registry-activated logging service to help diagnose Windows Installer issues. To enable this logging service during a silent install, open the registry editor and create the following path and keys: HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Window s\Installer Reg_SZ: Logging Value: voicewarmup The letters in the value field can be in any order. Each letter turns on a different logging mode.
Microsoft Active Directory If you use Active Directory service software, you can configure it to control access to your network. Dell has modified the Active Directory database to support remote management authentication and authorization. Dell OpenManage Server Administrator (OMSA), IT Assistant (ITA), Integrated Dell Remote Access Controller (iDRAC), Dell Chassis Management Controller (CMC), and Dell Remote Access Controllers (RAC), can interface with Active Directory.
Setting User and Server Preferences You can set user and secure port server preferences for Server Administrator and IT Assistant from the respective Preferences web page. Click General Settings and click either the User tab or Web Server tab. NOTE: You must be logged in with administrator privileges to set or reset user or server preferences. To set up your user preferences: 1 Click Preferences on the global navigation bar. The Preferences home page is displayed. 2 Click General Settings.
• IP Address to Bind to — Specifies the IP address(es) for the managed system that Server Administrator binds to when starting a session. Select All to bind to all IP addresses applicable for your system. Select Specific to bind to a specific IP address. NOTE: A user with administrator privileges cannot use Server Administrator when logged into the system remotely.
X.509 Certificate Management Web certificates are necessary to ensure that the identity and information exchanged with a remote system cannot be viewed or changed by others. To ensure system security, it is strongly recommended that you either generate a new X.509 certificate, reuse an existing X.509 certificate, or import a root certificate or certificate chain from a Certificate Authority (CA). Authorized CAs include Verisign, Entrust, and Thawte.
To install the Remote Enablement feature, the following must be configured on your system: • Windows Remote Management (WinRM) • CA/Self-Signed Certificate • WinRM HTTPS Listener Port • Authorization for WinRM and Windows Management Instrumentation (WMI) Servers Installing WinRM On Windows Server 2008 R2 and Windows 7, WinRM 2.0 is installed by default. On Windows Server 2008, WinRM 1.1 is installed by default.
7 Click Close and click OK. 8 On the Console window, expand Certificates (Local Computer) in the left navigation pane. 9 Right-click Personal, select All tasks Request New Certificate. 10 Click Next. 11 Select the appropriate certificate type, Mostly (Computer), and click Enroll. 12 Click Finish. Creating the HTTPS Listener With the Valid CA Signed Certificate Run the installer and click the link on the prerequisite checker to create the HTTPS listener.
10 Click Finish. The SelfSSL is installed. 11 Click Start Programs IIS Resource SelfSSL SelfSSL. 12 Type selfssl /T /N:CN=. Adding a Certificate and Taking a Thumbprint To add a certificate and tae a thumbprint: NOTE: If Internet Information Service (IIS) is already installed on your system, then the value of CertificateThumbprint must be an empty string and you need not perform the steps in this section.
14 Click Details tab. 15 Select Thumbprint. 16 Copy the thumbprint to the clipboard. You can use this parameter while creating the HTTPS listener. 17 Click OK.
WinRM To configure user authorization for WinRM servers: 1 Click Start Run. 2 Type winrm configsddl and click OK. If you are using WinRM 2.0, type winrm configsddl default. 3 Click Add and add the required users or groups (local/domain) to the list. 4 Provide the appropriate permission(s) to the respective users and click OK. WMI To configure user authorization for WMI servers: 1 Click StartRun. 2 Type wmimgmt.msc and click OK. The Windows Management Infrastructure (WMI) screen is displayed.
Configuring the Windows Firewall for WinRM To configure the Windows Firewall for WinRM: 1 Open the Control Panel. 2 Click Windows Firewall. 3 Click the Exceptions tab. 4 Select the Windows Remote Management check box. If you do not see the check box, click Add Program to add Windows Remote Management. Configuring the Envelope Size for WinRM To configure the envelope size for WinRM: 1 Open a command prompt. 2 Type winrm g winrm/config. 3 Check the value of the MaxEnvelopeSizekb attribute.
Dependent RPMs for Remote Enablement If you choose to install the Remote Enablement feature, you have to install certain dependent RPMs and configure these RPMs before installing the feature. Install the following RPMs: • libcmpiCppImpl0 • libwsman1 • openwsman-server • sblim-sfcb • sblim-sfcc The dependent RPMs are available on the Dell Systems Management Tools and Documentation DVD at srvadmin\linux\RPMS\supportRPMS\opensourcecomponents\\.
4 Check for the required dependencies for the openwsman and sfcbd RPMs listed in Table 2-4. Table 2-4.
5 Install the dependent RPMs. You can install the RPMs: • with a single command rpm -ivh rpm1 rpm2 rpm3 rpm4 … rpmN or • individually NOTE: If you are installing RPMs individually, follow the sequence below. rpm -ivh sblim-sfcb-x.x.x.rpm rpm -ivh sblim-sfcc-x.x.x.rpm NOTE: Install the libwsman and openwsman client RPMs simultaneously as they have cyclic dependency. rpm -ivh libwsman1-x.x.x.rpm openwsman-clientx.x.x.rpm rpm -ivh openwsman-server-x.x.x.
Creating Server Certificate for WSMAN You can either create a new certificate for WSMAN or reuse an existing certificate. Creating a New Certificate You can create a new server certificate for WSMAN by executing the owsmangencert.sh script located at /etc/openwsman. This script is provided by the openwsman RPM. Follow the steps in the wizard to create the server certificate.
On Red Hat Enterprise Linux 6, for the sblim-sfcb and openwsman to start automatically after a reboot you need to change the run-levels using the chkconfig utility. For example, if you want to run sblim-sfcb in runlevels 3 and 5, use the following command: #chkconfig sblim-sfcb on --level 35 NOTE: For more information on chkconfig and its usage, see the operating system documentation. The managed system is configured and is ready to be used by the Server Administrator Web Server.
auth sufficient /lib/security/$ISA/pam_unix.so likeauth nullok auth sufficient /lib/security/$ISA/pam_krb5.so use_first_pass auth sufficient /lib/security/$ISA/pam_winbind.so use_first_pass auth required /lib/security/$ISA/pam_deny.so account required /lib/security/$ISA/pam_unix.so broken_shadow account sufficient /lib/security/$ISA/pam_succeed_if.so uid 100 quiet account [default=bad success=ok user_unknown= ignore] /lib/security/$ISA/pam_krb5.
Winbind Configuration for openwsman and sfcb for SUSE Linux Enterprise Server Operating System Follow the instructions mentioned below to configure openwsman and sfcb on 32-bit OMI installation. In case of a 64-bit installation, replace lib with lib64. 1 Back up the following files: • /etc/pam.d/openwsman • /etc/pam.d/sfcb • /etc/pam.d/system-auth • /etc/pam.d/common-account 2 Replace the content of /etc/pam.d/openwsman/ and /etc/pam.d/sfcb with: %PAM-1.
For example: On a 32-bit Dell OpenManage installation, if you have libssl.so.0.9.8a and libssl.so.0.9.8b in /usr/lib, then create soft link with the latest libssl.so.0.9.8b: • ln -sf /usr/lib/libssl.so.0.9.8b /usr/lib/libssl.so • ldconfig On a 64-bit Dell OpenManage installation, if you have libssl.so.0.9.8a and libssl.so.0.9.8b in /usr/lib, then create soft link with the latest libssl.so.0.9.8b: • ln -sf /usr/lib64/libssl.so.0.9.8b /usr/lib64/libssl.
Preinstallation Setup
Installing Managed System Software on Microsoft Windows Operating Systems 3 On Microsoft Windows, an autorun utility appears when you insert the Dell Systems Management Tools and Documentation DVD. This utility allows you to choose the systems management software you want to install on your system. If the autorun program does not start automatically, use the setup program in the SYSMGMT\srvadmin\windows directory on the Dell Systems Management Tools and Documentation DVD.
Table 3-1 lists the deployment scenarios for installing and using Server Administrator and helps you make the right choice while selecting the various installation options: Table 3-1. Deployment Scenarios You want to Select Remotely manage and monitor your entire network of managed systems from your system (laptop, desktop, or server). Server Administrator Web Server. You must then install Server Instrumentation on the managed systems. Manage and monitor your current system.
Installing Server Administrator This section explains how to install the Server Administrator and other managed system software using two installation options: • Using the setup program at \SYSMGMT\srvadmin\windows on the Dell Systems Management Tools and Documentation DVD. • Using the unattended installation method through the Windows Installer Engine msiexec.exe (see Table 3-2). NOTE: SNMP service is stopped and started during Systems Management installation and uninstallation.
• Remote Access Controller • Intel SNMP Agent • Broadcom SNMP Agent During a Typical installation, individual management station services that do not meet the specific hardware and software requirement for that service are not installed on the managed systems. For example, the Dell OpenManage Server Administrator Remote Access Controller service software module is not installed during a Typical installation unless the managed system has a remote access controller installed on it.
4 Select Dell OpenManage Server Administrator from the autorun menu and click Install. If the autorun program does not start automatically, go to the SYSMGMT\srvadmin\windows directory on the DVD, and run the setup.exe file. The Dell OpenManage Server Administrator prerequisite status screen appears and runs the prerequisite checks for the managed system. Any relevant informational, warning, or error messages are displayed. Resolve all error and warning situations, if any.
9 Click Next on the Custom Setup dialog box to accept the selected software features for installation. The Ready to Install the Program dialog box is displayed. NOTE: You can cancel the installation process by clicking Cancel. The installation rolls back the changes that you made. If you click Cancel after a certain point in the installation process, the installation may not roll back properly, leaving the system with an incomplete installation.
In order to avoid this problem, select one of the following options: Option 1: 1 Uninstall Server Administrator. 2 Install Citrix. 3 Reinstall Server Administrator. Option 2: After installing Citrix, type the following command: msiexec.exe /fa SysMgmt.msi Performing an Unattended Installation of Managed System Software The Dell OpenManage installer features a Typical Setup option and a Custom Setup option for the unattended installation procedure.
Creating and Distributing the Typical Unattended Installation Package The Typical Setup unattended installation option uses the Dell Systems Management Tools and Documentation DVD as the unattended installation package. The msiexec.exe /i SysMgmt.msi /qb command accesses the DVD to accept the software license agreement and installs all the required Server Administrator features on selected remote systems. These features are installed on the remote systems based on the system's hardware configuration.
Distributing the Entire DVD as the Typical Unattended Installation Package 1 Distribute the entire image of the Dell Systems Management Tools and Documentation DVD to your target systems. 2 Configure your ISV distribution software to execute the msiexec.exe /i DVD Drive\SYSMGMT\srvadmin\windows\SystemsManagement\ SysMgmt.msi /qb command from the DVD image. The program executes to install Server Administrator on each remote system. 3 Reboot each remote system to enable Server Administrator.
Distributing Custom Unattended Installation Packages For distributing custom unattended installation packages: NOTE: The SysMgmt.msi installation package for Server Administrator used in the Custom Setup unattended installation (For more information, see "Creating and Distributing Custom Unattended Installation Packages") is located in the SYSMGMT\srvadmin\windows\SystemsManagement directory in the DVD.
Optional Command Line Settings Table 3-2 shows the optional settings available for the msiexec.exe MSI installer. Type the optional settings on the command line after msiexec.exe with a space between each setting. NOTE: See support.microsoft.com for details about all the command line switches for the Windows Installer Tool. Table 3-2. Command Line Settings for MSI Installer Setting Result This command installs or configures a product. /i
Table 3-2. Command Line Settings for MSI Installer (continued) Setting Result /f[p|o|e|d|c|a|u This command repairs a product. |m|s|v] /fo – This option reinstalls a product if a file is missing or if an older version of a file is installed. /fe – This option reinstalls a product if a file is missing or an equal or older version of a file is installed.
Customization Parameters REINSTALL and REMOVE customization CLI parameters provide a way to customize the exact software features to install, reinstall, or uninstall when running a silent or unattended installation. With the customization parameters, you can selectively install, reinstall, or uninstall software features for different systems using the same unattended installation package.
You can include the REINSTALL customization parameter on the command line and assign the feature ID (IDs) of the software feature that you want to reinstall. For example, msiexec.exe /i SysMgmt.msi REINSTALL=BRCM /qb This command runs the installation for Dell OpenManage Systems Management and reinstalls only the Broadcom agent, in an unattended but not silent mode.
Table 3-4. Windows Installer Return Codes (continued) Error Code Value Description ERROR_INSTALL_USEREXIT 1602 The user canceled the installation. ERROR_SUCCESS_REBOOT_REQUIRED 3010 A restart is required to complete the installation. This message is indicative of a successful installation. NOTE: For more information on all the error codes returned by the msiexec.exe and InstMsi.exe Windows Installer functions, see support.microsoft.com.
In addition to the rollback of MSI Standard Actions, the Dell OpenManage library also has the ability to undo commands listed in the INI file for each application if a rollback occurs. All files that are modified by the Dell OpenManage installation actions are restored to their original state if a rollback occurs. When the MSI engine is going through the installation sequence, it ignores all actions that are scheduled as rollback actions.
Upgrading Managed System Software The Dell OpenManage installer provides an Upgrade option for upgrading Server Administrator and other managed system software. The setup program runs the prerequisite checker, which uses your system's PCI bus to search for installed hardware, such as controller cards. The setup program installs or upgrades all of the managed system software features that are appropriate for your particular system's hardware configuration.
Upgrade 1 Insert the Dell Systems Management Tools and Documentation DVD into your system's DVD drive. The autorun menu appears. 2 Select Dell OpenManage Server Administrator and click Install. If the autorun program does not start automatically, go to the SYSMGMT\srvadmin\windows directory on the DVD, and run the setup.exe file. The Dell OpenManage Server Administrator prerequisite status screen appears and runs the prerequisite checks for the managed station.
4 Click Next. The Program Maintenance dialog box appears. 5 Select the Modify option and click Next. The Custom Setup dialog box appears. 6 To select a specific managed system software application, click the dropdown arrow beside the listed feature and select either This feature will be installed… to install the feature, or This feature will not be available to ignore the feature. A selected feature has a hard drive icon depicted next to it. A deselected feature has a red X next to it.
Repair If you want to repair an installed Server Administrator component that may be damaged: 1 Navigate to the Windows Control Panel. 2 Click Add/Remove Programs. 3 Click Dell Server Administrator and click Change. The Welcome to the Install Wizard for Dell OpenManage Server Administrator dialog box appears. 4 Click Next. The Program Maintenance dialog box appears. 5 Select the Repair option and click Next. The Ready to Repair the Program dialog box appears.
Uninstalling Managed System Software Using Dell-Provided Media 1 Insert the Dell Systems Management Tools and Documentation DVD into your system's DVD drive. If the setup program does not start automatically, run the setup.exe in the SYSMGMT\srvadmin\windows directory on the DVD. The Dell OpenManage Server Administrator prerequisite status screen appears and runs the prerequisite checks for the managed system. Any relevant informational, warning, or error messages detected during checking are displayed.
Uninstalling Managed System Software Features Using the Operating System 1 Navigate to the Windows Control Panel. 2 Click Add/Remove Programs. 3 Click Dell OpenManage Server Administrator and click Remove. The Add or Remove Programs dialog box appears. 4 Click Yes to confirm uninstallation of Server Administrator. The Dell OpenManage Server Administrator screen appears and provides the status and progress of the software features being uninstalled.
Distributing the Unattended Uninstallation Package The Dell Systems Management Tools and Documentation DVD is pre-configured to act as the unattended uninstallation package. To distribute the package to one or more systems: 1 Configure your ISV distribution software to execute the msiexec.exe /x DVD Drive\SYSMGMT\srvadmin\windows\SystemsManagement\ SysMgmt.msi /qb command, if you are using the DVD, after the unattended uninstallation package has been distributed.
Installing Managed System Software on Microsoft Windows Operating Systems
4 Installing Managed System Software on Supported Linux and VMware ESX The Dell OpenManage installer supports both 32-bit and 64-bit architecture. The following table explains the operating system installation matrix for Dell OpenManage. Table 4-1.
Table 4-1. Operating System Installation Matrix for Dell OpenManage (continued) Operating System Architecture OpenManage 32-bit Architecture OpenManage 64-bit Architecture ESX 4.0 U3 64-bit Install or Upgrade Not supported ESX 4.1 U2 64-bit Install or Upgrade Not supported ESXi 4.0 U3 64-bit Not supported Install ESXi 4.1 U2 64-bit Not supported Install ESXi 5.0 Not supported Install 64-bit Not supported Install ESXi 5.
The install script srvadmin-install.sh allows silent or interactive installation. By including the srvadmin-install.sh script in your Linux scripts, you can install Server Administrator locally or across a network on single or multiple systems. The second install method uses the Server Administrator RPM packages provided in the custom directories and the Linux rpm command. You can write Linux scripts that install Server Administrator locally or across a network on single or multiple systems.
If the Server Administrator drivers are available with the operating system, Server Administrator uses those versions of the drivers. If the Server Administrator drivers are not available with the operating system, Server Administrator uses its Dynamic Kernel Support (DKS) feature to build the drivers when needed. Dynamic Kernel Support Server Administrator includes DKS, a feature that Server Administrator uses to build its device drivers automatically for a running kernel if needed.
kernel source. On systems running Red Hat Enterprise Linux, the kernel-devel RPMs provide the necessary kernel source for building kernel modules. • The GNU make utility must be installed. The make RPM provides this utility. • The GNU C compiler (gcc) must be installed. The gcc RPM provides this compiler. • The GNU linker (ld) must be installed. The binutils RPM provides this linker.
For example, 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: 1 Ensure that the DKS prerequisites are met on system A. 2 Start Server Administrator on system A. Server Administrator builds a device driver for the kernel running on system A during startup.
OpenIPMI Device Driver The Server Instrumentation feature of Server Administrator requires the OpenIPMI device driver that provides IPMI-based information and functionality. All supported Linux systems contain the required version of IPMI module in the default kernel itself. You do not have to install the IPMI RPM. For more information on supported systems, see the Dell Systems Software Support Matrix available at support.dell.com/support/edocs/software/omswrels.
Installing Managed System Software This section explains how to install managed system software using the following installation options: • Using the srvadmin-install.sh shell script NOTE: If you have downloaded the managed system software installer (available as a .tar.gz file) from support.dell.com, the srvadmin-install.sh shell script is present as setup.sh in the root directory.
d From the sub-category, select the Web-based Enterprise Management Optional Packages option. The default selected packages are: • openwsman-client • sblim-sfcb • sblim-wbemcli • wsmancli Deselect the sblim-wbemcli package from the above list. e Select the openwsman-server and click Next.
To review the software before you install it, follow this procedure: 1 Load the Dell Systems Management Tools and Documentation DVD into your system's DVD drive. 2 Mount the DVD, if required. 3 When you have mounted the DVD, navigate to: /SYSMGMT/srvadmin/linux/ The installation script and RPM folder are available under the Linux directory. Express Install Use the provided shell script to perform the express installation on supported Linux and VMware ESX operating systems.
The setup program installs the following managed system software features: • Server Administrator Web Server • Server Instrumentation • Storage Management • Remote Access Controller Remote enablement is not installed and Server Administrator services do not start automatically. NOTE: The 32-bit srvadmin-cm RPM is not installed when OpenManage is installed on a 64-bit operating system.
Where is the supported operating system and is 32-bit (i386) or 64-bit (x86_64). NOTE: In case of SUSE Linux Enterprise Server version 10 and 11: 32-bit Dell OpenManage rpm packages are provided for upgrade from the previous 32-bit installs only. If you do not have an existing installation, then you cannot install a 32-bit version of the software. You must install operating system specific rpms from the 64-bit directory.
Table 4-2. Meta RPMs (continued) Meta RPMs Details srvadmin-rac5 Installs the DRAC 5 component. srvadmin-standardAgent Installs the Remote Enablement component. srvadmin-storageservices Installs the storage services component. srvadmin-webserver Installs the web server component. The following is an example of custom RPMs-based installation of Server Administrator, including the installation of the Remote Enablement feature and the Storage Management Service components.
5 Start the Server Administrator services after the installation by using the command: sh srvadmin-services start NOTE: You can install Server Administrator on any system that meets operating system dependencies. However, after installation, certain Server Administrator services may not be started on unsupported systems. NOTE: When Dell OpenManage Server Administrator is installed on a system, dependency issues related to RPMs may occur.
[-h|--help] — Displays the help text. Options that can be used along with the options above: [-p|--preserve] — Preserves the screen without clearing off. NOTE: If you do not use the [-p | --preserve] option during the installation, the history information on the screen gets cleared off. [-a|--autostart] — Starts the installed services after components have been installed. Using the Shell Script to Perform the Installation in Interactive Mode This installation procedure uses the srvadmin-install.
Using the Install Script To Run in the Silent Mode Perform the following steps for a silent installation using the srvadmin-install.sh shell script: 1 Log on as root to the system running the supported operating system where you want to install the managed system components. 2 Insert the Dell Systems Management Tools and Documentation DVD into the DVD drive. 3 Mount the DVD, if required. 4 Navigate to /SYSMGMT/srvadmin/linux/supportscripts.
Managed System Software Installation Using Third-Party Deployment Software You can use third-party deployment software, such as Altiris Deployment Solution, to install managed system software on supported Dell servers. To distribute and install managed system software using Altiris, start your Altiris application and import OpenManage_Jobs.bin located at SYSMGMT\srvadmin\support\Altiris on the Dell Systems Management Tools and Documentation DVD. Specify a job folder to import OpenManage_Jobs.bin.
Installing Managed System Software on Supported Linux and VMware ESX
Installing Managed System Software On Microsoft Windows Server 2008 Core and Microsoft Hyper-V Server 5 The Server Core installation option of the Microsoft Windows Server 2008 and Hyper-V Server operating system provides a minimal environment for running specific server roles that reduce the maintenance and management requirements and the attack surface for those server roles.
Installing Managed System Software in CLI Mode Launch the MSI file from the command prompt using the command msiexec /i SysMgmt.msi The MSI file SysMgmt.msi is located at SYSMGMT\srvadmin\windows\SystemsManagement on the Dell Systems Management Tools and Documentation DVD. To install the localized version of the managed system software, type msiexec /I SysMgmt.msi TRANSFORMS= .mst in the command prompt. Replace .mst with the appropriate language file: • 1031.
Installing Dell OpenManage Software on VMware ESXi 6 VMware ESXi is factory-installed on some Dell systems. For a list of these systems, see the latest Dell Systems Software Support Matrix at support.dell.com/support/edocs/software/omswrels. You can use Server Administrator Web Server version 7.0 to access VMware ESXi 4.0 U3, VMware ESXi 4.1 U2, VMware ESXi 5.0, and VMware ESXi 5.0 P1 systems. Dell OpenManage Server Administrator is available as a .zip file for installing on systems running VMware ESXi.
4 Execute the following command: For VMware ESXi4.0/ESXi 4.1: vihostupdate.pl --server -i -b For VMware ESXi 5.0/ESXi5.0 P1 esxcli --server software vib install -d /var/log/vmware/ NOTE: The .pl extension is not required if you are using vSphere CLI on Linux. 5 Enter the root username and password of the ESXi host when prompted. The command output displays a successful or a failed update.
5 Enter the root username and password of the ESXi host when prompted. The command output displays a successful or a failed update. In case of a failed update, see "Troubleshooting." 6 Restart the ESXi host system.
Enabling CIM OEM Providers Using vSphere Client (for VMware ESXi4.0/ESXi 4.1) To enable CIM OEM providers using VMware vSphere Client, you must have the vSphere Client tool installed. You can download and install the tool from https:// where is the IP address of the VMware ESXi system. To enable CIM OEM providers on the VMware ESXi system using vSphere Client: 1 Log on to the VMware ESXi host system using vSphere Client. 2 Click the Configuration tab.
Enabling CIM OEM Providers Using vSphere CLI (for VMware ESXi 4.0/ESXi 4.1) 1 If you are using vSphere CLI on Windows, navigate to the directory where you have installed the vSphere CLI utilities. On Linux, proceed to step 2. 2 Execute the following command: vicfg-advcfg.pl --server --username --password --set 1 UserVars.CIMOEMProvidersEnabled NOTE: For ESXi 4.0, use CIMOEMProvidersEnabled and for ESXi 4.1, use CIMoemProviderEnabled. The .
Uninstalling the Existing OpenManage VIB The following command can be used to uninstall the existing OpenManage VIB: vihostupdate.pl --server -r -B Dell_OpenManage_ESXi_OM640 Reboot the system after uninstalling. Configuring the SNMP Agent on Systems Running VMware ESXi Server Administrator generates Simple Network Management Protocol (SNMP) traps in response to changes in the status of sensors and other monitored parameters.
3 Navigate to the directory in which the vSphere CLI is installed. The default location on Linux is /usr/bin and on Windows is C:\Program Files\VMware\VMware vSphere CLI\bin. 4 Configure the SNMP setting using the following command: vicfg-snmp.
Troubleshooting • When attempting to use the vihostupdate command, the following error may be displayed: unpacking c:\OM-SrvAdmin-Dell-Web-7.0.0.VIB-ESXi_.zip metadata.zip.sig does not exist signature mismatch : metadata.zip Unable to unpack update package. This error is displayed if you are using an older version of the Remote CLI. To resolve this issue, download and install the latest vSphere version of the CLI.
Installing Dell OpenManage Software on Citrix XenServer 7 The Dell OpenManage Server Administrator is installed on Citrix XenServer using the Dell OpenManage Supplemental Pack. The OpenManage Supplemental Pack for Citrix XenServer 6.0 can be installed in two ways: • During the installation of XenServer a Start the installation of XenServer as usual and follow the instructions on the screen.
• On a running system a Burn the Supplemental Pack ISO file to a CD/DVD or download the ISO file to your server. If you are downloading the ISO file, mount it on a temporary directory as follows: $ mount -o loop .iso /mnt If you burned the ISO file to a CD/DVD, insert it in the optical drive and run: $ mount /dev/cdrom /mnt b Install the supplemental pack: $ cd /mnt $ ./install.sh OR $ xe-install-supplemental-pack .
If the XenServer image is upgraded to a newer XenServer update or release, the Dell OpenManage Supplemental Pack must be reinstalled since the new XenServer image is placed on a different partition from the original. In this case, follow the same installation instructions as before. However, any Dell OpenManage configuration settings saved on your server is lost. For more information on using Dell OpenManage with Citrix XenServer Dell Edition, see the Citrix XenServer Dell Edition Solution Guide at support.
Installing Dell OpenManage Software on Citrix XenServer
8 Using Microsoft Active Directory Controlling Access to Your Network If you use Active Directory service software, you can configure it to control access to your network. Dell has modified the Active Directory database to support remote management authentication and authorization. Dell OpenManage IT Assistant and Dell OpenManage Server Administrator, as well as Integrated Dell Remote Access Controllers (iDRAC), Dell Remote Access Controllers (DRAC), can now interface with Active Directory.
Overview of the Active Directory Schema Extensions Dell created classes, or groups of objects, that can be configured by the user to meet their unique needs. New classes in the schema include an Association, a Product, and a Privilege class. An association object links the user or group to a given set of privileges and to systems (Product Objects) in your network.
Figure 8-1. Typical Setup for Active Directory Objects Association Object User(s) Group(s) Privilege Object RAC Privilege Object Server Administrator Privilege Object IT Assistant Privilege Object Dell Product(s) RAC Device Object Server Administrator Application Object IT Assistant Application Object In addition, you can set up Active Directory objects in a single domain or in multiple domains.
Figure 8-2 shows the set up of the Active Directory objects in a single domain. In this scenario, you have two DRAC 4 cards (RAC1 and RAC2) and three existing Active Directory users (User1, User2, and User3). You want to give User1 and User2 administrator privilege on both DRAC 4 cards and give User3 login privilege on the RAC2 card. Figure 8-2.
4 Group User1 and User2 into Group1. 5 Add Group1 as Member in Association Object 1 (AO1), Priv1 as Privilege Object in AO1, and both RAC1 and RAC2 as RAC Products in AO1. 6 Add User3 as Member in Association Object 2 (AO2), Priv2 as Privilege Object in AO2, and RAC2 as RAC Product in AO2. For more information, see "Adding Users and Privileges to Active Directory". Figure 8-3 shows the setup of the Active Directory objects in multiple domains for RAC.
To set up the objects for this multiple domain scenario, perform the following tasks: 1 Ensure that the domain forest function is in Native mode. 2 Create two Association Objects, AO1 (of Universal scope) and AO2, in any domain. Figure 8-3 shows the objects in Domain2. 3 Create two RAC Device Objects, RAC1 and RAC2, to represent the two remote systems. 4 Create two Privilege Objects, Priv1 and Priv2, in which Priv1 has all privileges (Administrator) and Priv2 has Login privileges.
Figure 8-4. Setting up Server Administrator Active Directory Objects in Multiple Domains Domain 1 Domain 2 AO1 Group1 User1 User2 AO2 Priv1 User3 Priv2 sys1 Group1 sys2 To set up the objects for this multiple domain scenario, perform the following tasks: 1 Ensure that the domain forest function is in Native mode. 2 Create two Association Objects, AO1 and AO2, in any domain. The figure shows the objects in Domain1.
6 Add User1 and User2 as Members in Association Object 1 (AO1), Priv1 as Privilege Objects in AO1, and both sys1 and Group1 as Products in AO1. 7 Add User3 as a Member in Association Object 2 (AO2), Priv2 as a Privilege object in AO2, and Group1 as a Product in AO2. Note that neither of the Association objects needs to be of Universal scope in this case.
adsupport=true adproductname=omsaApp 3 Restart the Dell Systems Management Server Administrator (DSM SA) Connection Service after saving the omsaoem.ini file. Extending the Active Directory Schema The schema extensions for RAC, Server Administrator, and IT Assistant are available. You only need to extend the schema for software or hardware that you are using. Each extension must be applied individually to receive the benefit of its software-specific settings.
Table 8-1 lists the folder names and . Table 8-1. Folder Names and Installation Types Folder Name Installation Type ITA7 IT Assistant version 8.9 OMSA Dell OpenManage Server Administrator Remote_Management RAC 5, CMC, and iDRAC on xx0x Blade systems Remote_Management_Advanced iDRAC on xx1x systems NOTE: Only iDRAC6 is supported on xx1x systems. To use the LDIF files, see the instructions in the readme that is in the LDIF files directory.
For more information on class definitions for iDRAC, see the Integrated Dell Remote Access Controller User's Guide. Table 8-2. Class Definitions for Classes Added to the Active Directory Schema Class Name Assigned Object Identification Number (OID) Class Type dellAssociationObject 1.2.840.113556.1.8000.1280.1.1.1.2 Structural Class dellPrivileges 1.2.840.113556.1.8000.1280.1.1.1.4 Structural Class dellProduct 1.2.840.113556.1.8000.1280.1.1.1.5 Structural Class dellOmsa2AuxClass 1.2.840.113556.1.
Table 8-4. dellPrivileges Class (continued) OID 1.2.840.113556.1.8000.1280.1.1.1.4 Attributes dellRAC4Privileges dellRAC3Privileges dellOmsaAuxClass dellItaAuxClass Table 8-5. dellProduct Class OID 1.2.840.113556.1.8000.1280.1.1.1.5 Description This is the main class from which all Dell products are derived. Class Type Structural Class SuperClasses Computer Attributes dellAssociationMembers Table 8-6. dellOmsa2AuxClass Class OID 1.2.840.113556.1.8000.1280.1.2.1.
Table 8-7. dellOmsaApplication Class (continued) OID 1.2.840.113556.1.8000.1280.1.2.1.2 Class Type Structural Class SuperClasses dellProduct Attributes dellAssociationMembers Table 8-8. dellIta7AuxClass Class OID 1.2.840.113556.1.8000.1280.1.3.1.1 Description This class is used to define the privileges (Authorization Rights) for IT Assistant. Class Type Auxiliary Class SuperClasses None Attributes dellItaIsReadOnlyUser dellItaIsReadWriteUser dellItaIsAdminUser Table 8-9.
Table 8-10. General Attributes Added to the Active Directory Schema Attribute Name/Description Assigned OID/Syntax Object Identifier Single Valued dellPrivilegeMember 1.2.840.113556.1.8000.1280.1.1.2.1 FALSE List of dellPrivilege Objects that belong to this Attribute. Distinguished Name (LDAPTYPE_DN 1.3.6.1.4.1.1466.115.121.1.12) dellProductMembers 1.2.840.113556.1.8000.1280.1.1.2.2 FALSE List of dellRacDevices Objects that Distinguished Name belong to this role.
Table 8-11. Server Administrator-Specific Attributes Added to the Active Directory Schema (continued) Attribute Name/Description Assigned OID/Syntax Object Identifier Single Valued dellOMSAIsAdminUser 1.2.840.113556.1.8000.1280.1.2.2.3 TRUE TRUE if the User has Administrator rights in Server Administrator Boolean (LDAPTYPE_BOOLEAN 1.3.6.1.4.1.1466.115.121.1.7) Table 8-12.
Installing the Dell Extension to the Active Directory Users and Computers Snap-In When you are installing your systems management software using the Dell Systems Management Tools and Documentation DVD, you can install the Snap-in by selecting the Active Directory Snap-in option. For 64-bit Windows operating systems, the Snap-in installer is located under :\SYSMGMT\ManagementStation\support\ OMActiveDirectory_SnapIn64.
Adding Users and Privileges to Active Directory The Dell-extended Active Directory Users and Computers snap-in allows you to add DRAC, Server Administrator, and IT Assistant users and privileges by creating RAC, Association, and Privilege objects. To add an object, perform the steps in the applicable subsection. Creating a Product Object To create a Product Object: NOTE: Server Administrator and IT Assistant users must use Universal-type Product Groups to span domains with their product objects.
4 Type in a name for the new object. 5 Select the appropriate Privilege Object. 6 Click OK. 7 Right-click the privilege object that you created and select Properties. 8 Click the appropriate Privileges tab and select the privileges that you want the user to have (For more information, see Table 8-2 and Table 8-8). Creating an Association Object The Association Object is derived from a Group and must contain a group Type. The Association Scope specifies the Security Group Type for the Association Object.
To add Users or User Groups: 1 Right-click the Association Object and select Properties. 2 Select the Users tab and click Add. 3 Type the User or User Group name or browse to select and click OK. Click the Privilege Object tab to add the privilege object to the association that defines the user’s or user group’s privileges when authenticating to a system. NOTE: You can add only one Privilege Object to an Association Object. To add a privilege: 1 Select the Privileges Object tab and click Add.
Configuring Active Directory Using CLI on Systems Running Server Administrator You can use the omconfig preferences dirservice command to configure the Active Directory service. The productoem.ini file is modified to reflect these changes. If the adproductname is not present in the productoem.ini file, a default name is assigned.
Frequently Asked Questions 9 General How do I install Dell OpenManage Server Administrator with only the CLI features? By choosing not to install the Server Administrator Web Server, you 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 2607 (for the connection service) and 2606 (for the network monitoring service). These ports are configurable.
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: 1 Find out the version of Server Administrator that was previously installed. 2 Download the installation package for that version from support.dell.com. 3 Locate SysMgmt.
What are the firewall-related configuration that needs to be done for WinRM? With firewall turned ON, WinRM must be added to the firewall exclusion list to allow TCP port 443 for HTTPS traffic. When launching the Dell OpenManage Install, an error message may display, stating a failure to load a specific library, a denial of access, or an initialization error. An example of installation failure during Dell OpenManage Install is "failed to load OMIL32.DLL.
I am getting an error message "An older version of Server Administrator software is detected on this system. You must uninstall all previous versions of Server Administrator applications before installing this version" while launching Dell OpenManage Install? If you see this error when trying to launch Dell OpenManage Install, it is recommended that you run the OMClean.exe program, under the SYSMGMT\srvadmin\support\OMClean directory, to remove an older version of Server Administrator on your system.
I have installed Server Administrator using remote Server Administrator deploy on Windows Server 2008, I do not see Server Administrator icon on the desktop? On an initial Server Administrator install using remote Server Administrator deploy (OMSA push) on a server running Windows Server 2008, the Server Administrator icon is not visible until the desktop is refreshed manually by pressing the key.
No. Dell OpenManage Install does not support Windows Advertised installation - the process of automatically distributing a program to client computers for installation, through the Windows group policies. How do I check the disk space availability during custom installation? In the Custom Setup screen, you must click an active feature to view your hard drive space availability or to change the installation directory.
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 ToolsInternet OptionsSecurityCustom level ScriptingActive scripting is set to Enable. Ensure that ToolsInternet OptionsSecurityCustom level ScriptingScripting 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.
How do I know what version of systems management software is installed on the system? Navigate to the Windows Control Panel and double-click Add/Remove Programs and select Dell OpenManage Server Administrator. Select the link for support information. Do I need to reboot the system after upgrading the Dell OpenManage? Upgrade may require a reboot if the files to be upgraded are in use. This is a typical Windows installer behavior. It is recommended that you reboot the system when prompted.
Red Hat Enterprise Linux or SUSE Linux Enterprise Server 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 Dell OpenManage components on a guest Linux operating system, the warning message may be displayed.
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 file name extension. You may also experience failed shared object files (files with so in the file name extension) dependencies. In this case, you can determine which RPM is needed to install the shared object, by using the RPM --whatprovides switch.
When using the rpm -e 'rpm -qa | grep srvadmin' command to remove Dell OpenManage 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 Dell OpenManage uninstall script, srvadmin-uninstall.sh, provided on the DVD.
Why am I getting a warning concerning the RPM package key during installation? The RPM files are signed with a digital signature.
What do the directories under srvadmin/linux/custom/ contain? The following table lists the names of the directories in the SYSMGMT/srvadmin/linux/custom/ directory. Table 9-3. Names of the Directories Under the srvadmin/linux/custom/ Directory Name of RPM Description Other Server Administrator RPMs required Server-Instrumentation — This is the core code for Server Administrator.
Table 9-3. Names of the Directories Under the srvadmin/linux/custom/ Directory (continued) Name of RPM Description Other Server Administrator RPMs required srvadmin-isvc Server Administrator Instrumentation Service — srvadmin-omilcore, Server Administrator provides a suite of srvadmin-deng, and systems management information for keeping srvadmin-hapi supported systems on your network healthy.
Table 9-3. Names of the Directories Under the srvadmin/linux/custom/ Directory (continued) Name of RPM Description Other Server Administrator RPMs required add-iDRAC — Software for remote management of third generation Remote Access Controllers. For example, iDRAC. srvadminidraccomponents Integrated Dell Remote Access Card Data Populator Remote Access Controller components.
Table 9-3. Names of the Directories Under the srvadmin/linux/custom/ Directory (continued) Name of RPM Description Other Server Administrator RPMs required srvadminracsvc Remote Access Card Managed Node — srvadmin-omilcore Remote Access Controller (RAC) services supporting the central administration of server clusters and the remote administration of distributed resources. add-RAC5 — Software for remote management of fifth generation Remote Access Controllers. For example, DRAC 5.
Table 9-3. Names of the Directories Under the srvadmin/linux/custom/ Directory (continued) Name of RPM Description Other Server Administrator RPMs required 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.
Table 9-3. Names of the Directories Under the srvadmin/linux/custom/ Directory (continued) Name of RPM Description Other Server Administrator RPMs required Remote-Enablement — Manage and monitor your 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.
Table 9-3. Names of the Directories Under the srvadmin/linux/custom/ Directory (continued) Name of RPM Description Other Server Administrator RPMs required srvadminomhip Server Administrator Instrumentation Service srvadmin-omilcore, Integration Layer — Provides Instrumentation srvadmin-deng, CLI.
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 | to exit): On pressing , only those Server Administrator packages (in the above example), srvadmin-omilcore-X.Y.Z-N and srvadmin-hapi-X.Y.
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 9-4.
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 9-5.
Frequently Asked Questions
A Dell OpenManage Linux Installer Packages This appendix lists the Dell OpenManage Linux installer packages. Table A-1. Meta RPMs RPM Description Dependant packages Required for OpenManage 6.3 6.4 6.5 7.
Table A-1.
Table A-1. Meta RPMs (continued) RPM Description Dependant packages Required for OpenManage srvadmin- Meta RPM for rac4 RAC4 components srvadminomilcore, srvadminracadm4, srvadminracdrsc4, srvadminracsvc, srvadmin-rac4populator*, srvadmin-raccomponents*, srvadminracdrsc* * 6.3 packages RAC 4 management Y Y Y Y using Server Administrator GUI/CLI, RAC4 tools srvadmin- Meta RPM for rac5 RAC5 components srvadminomilcore, srvadminracdrsc5, srvadminracadm5, srvadminracdrsc*, srvadmin-raccomponents * 6.
Table A-1. Meta RPMs (continued) RPM Description srvadmin- Meta RPM for idrac iDRAC components Dependant packages Required for srvadminomilcore, srvadminidracdrsc, srvadminidracadm, srvadminracdrsc*, srvadmin-raccomponents*, srvadminargtable2* * 6.3 packages iDRAC management using Server Administrator GUI/CLI, iDRAC tools OpenManage 6.3 6.4 6.5 7.0 Y Y Y Y Table A-2. Server Instrumentation and SNMP monitoring RPM Description OM Dependant packages Required for OpenManage 6.3 6.4 6.5 7.
Table A-2.
Table A-3. Packages needed for local management that are used by GUI and CLI components RPM Description OM Dependant packages Required for srvadminCommon omcommon framework or libraries for GUI/CLI srvadminomilcore srvadminomacore Provides plugins that act as interfaces between back end and GUI/CLI. Also provides OM CLI tools. srvadminomhip srvadminxmlsup OpenManage 6.3 6.4 6.5 7.
Table A-3. Packages needed for local management that are used by GUI and CLI components (continued) RPM Description OM Dependant packages srvadmincm Change srvadminManagement omacore NOTE: On a inventory collector. Feeds scripted software inventory install, srvadmin-cm data to is installed on management 32bit operating station systems only. applications like If required on ITA Required for OpenManage 6.3 Software Y inventory & updates using ITA 6.4 6.5 7.
Table A-4. Server Administrator Web Server (GUI) for Local and Remote Management RPM Description srvadminomauth Dependant packages Provides NA authentication files for GUI Required for OpenManage 6.3 6.4 6.5 7.0 Server Administrator GUI N N N N openwsma Openwsman n-client client libraries None Server Administrator GUI to manage remote nodes using WSMAN Y Y Ya Y libwsman1 Openwsman libraries used by client and server components None Openwsman support library Y Y Yb Y a.
Table A-5. Server Administrator Remote Enablement (Standard Agent) (continued) RPM Description srvadminThe Dell itunnelprovi OpenManage Small der Footprint CIM Broker (SFCB) provider that enables remote management of the server libwsman1 Required for sblim-sfcb >= 1.3.7, sblim-sfcc >= 2.2.1, openwsmanclient >= 2.2.3.9, openwsmanserver >= 2.2.3.9, libwsman1 >= 2.2.3.9, libcmpiCppI mpl0 >= 2.0.
Table A-5. Server Administrator Remote Enablement (Standard Agent) (continued) RPM Description sblim-sfcc OM Dependant packages Required for OpenManage 6.3 6.4 6.5 7.
Table A-6. Storage Instrumentation, SNMP Monitoring, GUI and CLI Plugins RPM Description OM Dependant Required for packages OpenManage 6.3 6.4 6.5 7.
Table A-6. Storage Instrumentation, SNMP Monitoring, GUI and CLI Plugins RPM Description OM Dependant Required for packages OpenManage 6.3 6.4 6.5 7.0 srvadminsysfsutils Provide utilities for None interfacing with sysfs file system. Used by OpenManage storage management libraries Storage Y instrumentation Y Y Y srvadminmegalib LSI utility libraries None for storage management of PERC 4 controllers. *N/A for 64-bit OMSA installation, and VMware ESX.
Table A-7. RAC Instrumentation, SNMP Monitoring, GUI and CLI Plugins RPM srvadminracsvc Description RAC services to manage DRAC 4 OM Dependant packages Required for OpenManage srvadminomilcore DRAC 4 Y instrumentation 6.3 6.4 6.5 7.
Table A-7. RAC Instrumentation, SNMP Monitoring, GUI and CLI Plugins (continued) RPM Description srvadminracdrsc5 RAC CLI and web plugin to Server Administrator for DRAC 5 OM Dependant packages Required for srvadminomilcore, srvadmin-deng, srvadminomcommon, srvadminomacore, srvadmin-rac5components DRAC 5 management using Server Administrator GUI/CLI OpenManage 6.3 6.4 6.5 7.
Table A-7. RAC Instrumentation, SNMP Monitoring, GUI and CLI Plugins (continued) RPM Description OM Dependant packages Required for OpenManage 6.3 6.4 6.5 7.0 srvadminrac4populator- RAC Data populator srvadmin-hapi, DRAC 4 Y for DRAC 4 srvadmin-deng, instrumentation srvadminracadm4 Y Y Y srvadminargtable2 Library for parsing GNU style command line argument.
Table A-8. Enable Software inventory and updates using IT Assistant RPM Description srvadmin-cm Change management inventory collector. Feeds software inventory data to management station applications like ITA 160 OM Dependant packages Required for srvadminomacore Software inventory and updates using ITA Dell OpenManage Linux Installer Packages OpenManage 6.3 6.4 6.5 7.
Index A certificate, 31 Active Directory, 13, 26, 102, 108, 116, 120 object identifiers, 101 objects, 103 schema, 109 schema extender utility, 109-110 schema extensions, 101 certificates Web, 29 ADDLOCAL, 57 command line, 58 Administrator Pack, 116 command line interface, 14 agent SNMP, 26 Common Information Model, 14, 23 alert log, 14 controller ERA/MC, 14 Altiris, 59, 85 Certification Authority, 29 CIM, 14, 23 Citrix, 50 CLI, 14, 57, 121 Association, 119 Association Object, 102, 118 D Asso
distribution software, 67 DKS, 72-73 prerequisites, 72 DRAC, 117, 119 DRAC 4, 133 DRAC 5 controller, 14 IT Assistant, 106, 121 L LDAP, 112 LDIF script file, 109 LinkID, 101 E M ERA ERA/MC, 14 managed system, 23 express setup, 23 management information base, 14 management object format, 14 management objects, 14 F firewall, 13 G GUID, 60 management station, 23 MIB, 14 Microsoft Active Directory, 13, 26, 116 Software Installer, 60 MMC, 117-118 MOF, 14 I MSI, 60, 125 INI file, 60 msiexec.
P S ports, 121 schema, 101, 109-110 Prerequisite Checker, 47, 126 SchemaExtenderOem.
T TCP/IP, 22 time-out, 13 tools ISV, 52 U unattended installation, 51 unattended uninstallation, 66 universal groups, 118 update packages, 15 user ID, 13 utilities schema extender utility, 109-110 W Web certificates, 29 Windows Installer Engine, 53 Installer Service, 60 Windows Management Instrumentation, 23 WMI, 23 X X.
