Dell™ OpenManage™ Server Administrator Version 6.
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. © 2010 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 . Overview . . . . . . . . . . . . . . . . . . . . . . . 11 . . . . . . . . . . . . . . . . . . . . . . . . 11 Dell OpenManage Systems Management Software . . . . . . . . . . . . . . . . . . . . . . . . . 12 Dell Systems Management Tools and Documentation DVD . . . . . . . . . . . . . . . . 12 . . . . . . . . . . . . . 14 Dell Server Updates DVD . Dell Management Console DVD . . . . . . . . . . 15 . . . . . . . . . . . 15 . . . . . . . . . . . .
3 Setup and Administration Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Requirements . . . . . . . . . . . . . . . . Supported Operating Systems and Web Browsers . . . . . . . . . . System Requirements . 25 26 . . . . . 28 . . . . . . . . . . . . . . . . . 29 . . . . . . . . Viewing Localized Versions of the Web-Based Interface . . . . . . . . . . . . . . . . . . . . 30 . . 30 . . . . . . . . . . . . . 30 . . . . . . . . . . . . . .
Installing Managed System Software on Microsoft Windows Operating Systems . . . . . . . . . . . . . . . Overview . . . 53 . . . . . . . . . . . . . . . . . . . . . . . . 53 . . . . 53 . . . . . 54 . . . . . . . . . . . 55 . . . . . . . . . . . . . . . . . . 55 Unattended and Scripted Silent Installation Installation Procedures Prerequisite Checker Remote Enablement Requirements Installing WinRM Certificate Authority - Signed/Self-Signed Certificate . . . . . . . . . . . . . . . . . .
Windows Installer Logging . . . . . . . . . . . . . . . Performing an Unattended Installation of Managed System Software . . . . . . . . . . . . . . . Creating and Distributing the Typical Unattended Installation Package . . . . . . . . . . . . . . . 70 . . 71 . . . . . . . . . . . 72 Unattended Installation Features . . . . . . . . . . 72 . . . . . . . . . . . . . 75 . . . . . . . . . . . . . . . . . . 76 Customization Parameters MSI Return Code 70 .
Uninstalling Systems Management Software 7 . . . 84 Installing Managed System Software on Supported Linux Operating Systems . . . . 85 Overview . . . . . . . . . . . . . . . . . . . . . . . . . Software License Agreement . . . . . . . . . . . . . . Server Administrator Device Drivers Dynamic Kernel Support . 86 . . . . . . . . . . 87 . . . . . . . . . . . . . . . . 87 Determining the Running Kernel . . . . . . . . . .
Running sfcb and openwsman . . . . . . . . . . 103 Winbind Configuration for openwsman and sfcb for Red Hat Enterprise Linux Operating Systems . . . . . . . . . . . . . . . . 103 Winbind Configuration for openwsman and sfcb for SUSE Linux Enterprise Server Operating Systems . . . . . . . . . . . . . . . . 105 . . . . . . . . . 106 Workaround for the Libssl Issue . . . . . . . 106 Prerequisites for Uninstalling Managed System Software . . . . . . . . . . . . . . . . . . . . .
Enabling CIM OEM Providers Using vSphere CLI (for VMware ESXi 4.0/ESXi 4.1) . . . . . . . . . . Enabling CIM OEM Providers Using vMA (for VMware ESXi 4.0/ESXi 4.1) . . . . . . . 114 . . . . . 115 Configuring the SNMP Agent on Systems Running VMware ESXi 4/ESXi 4.1 . . . . . . . . . . . . . . . Configuring Your System to Send Traps to a Management Station Using the vSphere CLI . 9 Using Microsoft Active Directory Controlling Access to Your Network Using the Dell Schema Extender . 116 . . . . .
Red Hat® Enterprise Linux® or SUSE® Linux Enterprise Server. . . . . . . . . . . . . . . . . . . . . . . . . . 152 A OpenManage Linux Installer Packages . . . . . . . . . . . . . . . . . Index 10 . . . . . . . . . 167 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 Introduction Overview This guide contains information to help you install Dell™ OpenManage™ Server Administrator on managed systems. A managed system has supported instrumentation agents installed that allow the system to be discovered and polled for status through Server Administrator. Server Administrator provides easy-to-use management and administration of local and remote systems through a comprehensive set of integrated management services.
• Using Microsoft Active Directory • Prerequisite Checker • Frequently Asked Questions NOTE: If you install management station and managed system software on the same system, install identical software versions to avoid system conflicts. Dell OpenManage Systems Management Software Dell OpenManage systems management software is a suite of applications for your Dell systems. This software enables you to manage your systems with proactive monitoring, diagnosis, notification, and remote access.
• Active Directory Snap-In • BMC Utilities • DRAC Tools For information about installing these applications, see the Dell OpenManage Management Station Software Installation Guide available on the Dell Systems Management Tools and Documentation DVD or at support.dell.com/support/edocs/software/omswrels/index.htm. This link also contains user documentation on Dell OpenManage applications.
remotely from the Server Administrator Home page. Remotely monitored systems may be accessed by dial-in, LAN, or wireless connections. Server Administrator ensures the security of its management connections through role-based access control (RBAC), authentication, and industry-standard secure socket layer (SSL) encryption.
The Dell Server Updates DVD contains Dell Update Packages (DUPs) and Dell OpenManage Server Update Utility (SUU). DUPs allow administrators to update a wide range of system components simultaneously and apply scripts to similar sets of Dell systems to bring system software components up to the same version levels. SUU is an application that identifies and applies updates to your system. You can use SUU to update your Dell system or to view the updates available for any system supported by SUU.
• The Dell Management Console User’s Guide has information about installing, configuring, and using Dell Management Console. Dell Management Console is a Web-based systems management software that enables you to discover and inventory devices on your network. It also provides advanced functions, such as health and performance monitoring of networked devices and patch management capabilities for Dell systems.
• The Dell OpenManage IT Assistant User’s Guide has information about installing, configuring, and using IT Assistant. IT Assistant provides a central point of access to monitor and manage systems on a local area network (LAN) or wide area network (WAN). By allowing an administrator a comprehensive view across the enterprise, IT Assistant can increase system uptime, automate repetitive tasks, and prevent interruption in critical business operations.
Introduction
Dell OpenManage Security 2 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.
Security Management Dell provides security and access administration through role-based access control (RBAC), authentication, and encryption, or through Active Directory (or through Winbind, Kerberos, LDAP, or NIS on Linux operating systems) for both the Web-based and command line interfaces. RBAC RBAC manages security by determining the operations that can be executed by users in specific roles.
Table 2-1. User Privileges (continued) User Privileges Access Type Power User Administrator X X X X X Admin access allows you to shut down the managed system. Write access allows you to modify or set the values on the managed system. Read access allows you to view the data reported by Server Administrator. Read access does not allow you to change or set the values on the managed system.
Authentication The Server Administrator authentication scheme ensures that the access types are assigned to the correct user privileges. Additionally, when you invoke the CLI, the Server Administrator authentication scheme validates the context within which the current process is running. This authentication scheme ensures that all Server Administrator functions, whether accessed through the Server Administrator home page or CLI, are properly authenticated.
extensions for customers to modify their Active Directory database to support remote management authentication and authorization. IT Assistant, Server Administrator, and Dell Remote Access Controllers can interface with Active Directory to add and control users and privileges from one central database. For information about using Active Directory, see "Using Microsoft Active Directory." Authentication Protocols for Linux Operating Systems Dell OpenManage applications (version 5.
Dell OpenManage Security
Setup and Administration 3 Before You Begin • 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 on the Dell Support website at support.dell.com/support/edocs/software/omswrels/index.htm. These files contain the latest information about software, firmware, and driver versions, in addition to information about known issues.
NOTE: The Dell OpenManage installer offers Multilingual User Interface support on Microsoft Windows Storage Server™ 2003 R2, Microsoft Windows Storage Server 2003 R2, Express x64 Edition with Unified Storage, Microsoft Windows Storage Server 2003 R2, Workgroup x64 Edition with Unified Storage, and Windows Server 2008 (x86 and x64) R2 operating systems.
• The Server Administrator Remote Access Controller service requires that a remote access controller (RAC) be installed on the system to be managed. 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, when installing managed system software, provided that the managed system meets all of the RAC installation prerequisites.
Table 3-1. Availability of Systems Management Protocol by Operating Systems Operating System SNMP CIM/WMI Supported Microsoft Windows operating systems. Available from the operating system installation media. Always installed Supported Red Hat Install the SNMP package provided Enterprise Linux operating with the operating system. systems. Available.
When you launch Server Administrator, it first determines if the Windows Server 2003 R2 IPMI driver is enabled. If the driver is enabled, Server Administrator uses the Windows Server 2003 R2 IPMI driver to provide its IPMI-based functionality. If the Windows Server 2003 R2 IPMI driver is not enabled, Server Administrator uses its own internal IPMI support to provide its IPMI-based functionality.
Configuring a Supported Web Browser For a list of supported Web browsers, see "Supported Operating Systems and Web Browsers." NOTE: Ensure that the Web browser is set to bypass the proxy server for local addresses. Viewing Localized Versions of the Web-Based Interface Use Regional and Language Options in the Windows Control Panel to view localized versions of the Web-based interface, on systems running Windows operating systems.
the appropriate section below for your operating system. For additional guidelines, see the Securing an SNMP Environment article, dated May 2003, in the Dell Power Solutions magazine. This magazine is also available at www.dell.com/powersolutions.
2 Expand the Computer Management icon in the window, if necessary. 3 Expand the Services and Applications icon and click Services. 4 Scroll down the list of services until you find SNMP Service, right-click SNMP Service, and then click Properties. The SNMP Service Properties window appears. 5 Click the Security tab. 6 Select Accept SNMP packets from any host, or add the IT Assistant host to the Accept SNMP packets from these hosts list.
d Edit the community name of the management station in the Community Name text box, and click OK. The SNMP Service Properties window appears. 6 Click OK to save the changes. Enabling SNMP Set Operations Enable SNMP Set operations on the system running Dell OpenManage software, to change Dell OpenManage software attributes using IT Assistant. To enable remote shutdown of a system from IT Assistant, enable SNMP Set operations.
Operations. For more information on enabling or disabling SNMP Set operations in Server Administrator, see the Dell OpenManage Server Administrator User’s Guide or the Dell OpenManage Server Administrator Command Line Interface User's Guide. Configuring Your System to Send SNMP Traps to a Management Station The Dell OpenManage software generates SNMP traps in response to changes in the status of sensors and other monitored parameters.
station. To configure your SNMP agent for proper interaction with management applications such as IT Assistant, perform the procedures described in the following sections. NOTE: See your operating system documentation for additional details about SNMP configuration. SNMP Agent Access Control Configuration The management information base (MIB) branch implemented by Server Administrator is identified by the 1.3.6.1.4.1.674 OID.
These changes to the default SNMP agent configuration give read-only access to the entire MIB tree for the public community. NOTE: To ensure that Server Administrator is able to modify the SNMP agent configuration to provide proper access to systems management data, it is recommended that any other SNMP agent configuration changes be made after installing Server Administrator. Server Administrator SNMP communicates with the SNMP agent using the SNMP Multiplexing (SMUX) protocol.
com2sec notConfigUser default community_name 3 To enable SNMP configuration changes, restart the SNMP agent by typing: service snmpd restart Enabling SNMP Set Operations Enable SNMP Set operations on the system running Server Administrator in order to change Server Administrator software attributes using IT Assistant. To enable remote shutdown of a system from IT Assistant, enable SNMP Set operations. NOTE: Rebooting your system for change management functionality does not require SNMP Set operations.
Configuring Your System to Send Traps to a Management Station Server Administrator generates SNMP traps in response to changes in the status of sensors and other monitored parameters. One or more trap destinations must be configured on the system running Server Administrator for SNMP traps to be sent to a management station. To configure your system running Server Administrator to send traps to a management station, edit the /etc/snmp/snmpd.
NOTE: This command is available only if you have performed a default installation of the operating system. The Choose a Tool menu appears. 2 Select Firewall Configuration using the down arrow and press . The Firewall Configuration screen appears. 3 Select the Security Level. The selected Security Level is indicated by an asterisk. NOTE: Press for more information about the firewall security levels. The default SNMP port number is 161.
Configuring the SNMP Agent on Systems Running Supported SUSE Linux Enterprise Server Operating Systems Server Administrator uses the SNMP services provided by the ucd-snmp or net-snmp agent. You can configure the SNMP agent to enable SNMP access from remote hosts, change the community name, enable Set operations, and send traps to a management station.
To enable SNMP access from a specific remote host to a system running Server Administrator, edit the SNMP agent configuration file, /etc/snmpd.conf or /etc/snmp/snmpd.conf, and perform the following steps: 1 Find the line that reads: rocommunity public 127.0.0.1 2 Edit or copy this line, replacing 127.0.0.1 with the remote host IP address.
To change the default SNMP community name used for retrieving management information from a system running Server Administrator, edit the SNMP agent configuration file, /etc/snmpd.conf or /etc/snmp/snmpd.conf, and perform the following steps: 1 Find the line that reads: rocommunity public 127.0.0.1 2 Edit this line by replacing public with the new SNMP community name. When edited, the new line should read: rocommunity community_name 127.0.0.
Configuring Your System to Send Traps to a Management Station Server Administrator generates SNMP traps in response to changes in the status of sensors and other monitored parameters. One or more trap destinations must be configured on the system running Server Administrator for SNMP traps to be sent to a management station. To configure your system running Server Administrator to send traps to a management station, edit the SNMP agent configuration file, /etc/snmpd.conf or /etc/snmp/snmpd.
3 To add a preselected e-mail recipient, type the e-mail address of your designated service contact in the Mail To: field, and click Apply Changes. NOTE: Clicking Email in any window sends an e-mail message with an attached HTML file of the window to the designated e-mail address. 4 To change the home page appearance, select an alternative value in the skin or scheme fields and click Apply Changes.
• The SMTP Server name and DNS Suffix for SMTP Server fields specify your organization's Simple Mail Transfer Protocol (SMTP) and domain name server (DNS) suffix. To enable Server Administrator to send e-mails, you must type the IP address and DNS suffix for the SMTP server for your organization in the appropriate fields. NOTE: For security reasons, your organization might not allow e-mails to be sent through the SMTP server to outside accounts.
Best Practices for X.509 Certificate Management To ensure that the security of your system is not compromised while using server administrator, you should keep in mind the following: 46 • Unique host name: All systems that have server administrator installed should have unique host names. • Change 'localhost' to unique: All systems with host name set to 'localhost' should be changed to a unique host name.
4 Deployment Scenarios for Server Administrator You can install Dell™ OpenManage™ Server Administrator in the following ways: • Install the Server Administrator Web Server on any system (Dell PowerEdge system, laptop, or desktop) and the Server Instrumentation on another supported Dell PowerEdge™ system In this method, the Server Administrator Web Server performs the function of a central Web Server and you can use it to monitor a number of managed systems.
Table 4-1. Deployment Scenarios (continued) You want to Select View the status of local and remote storage attached to a managed system and obtain storage management information in an integrated graphical view. Storage Management. Remotely access an inoperable system, receive alert notifications when a system is down, and remotely restart a system. Remote Access Controller.
Table 4-2. Component Managed System Software Components (continued) What is Installed Deployment Scenario Systems on Which to be Installed NOTE: If you want to remotely manage multiple systems running on Windows and Linux operating systems, it is recommended that you install the Server Administrator Web Sever on a Windows operating system. Server Server Instrumentation Administrator CLI + Instrumentation Service Install Server Instrumentation to use your system as the managed system.
Table 4-2. Managed System Software Components (continued) Component What is Installed Deployment Scenario Systems on Which to be Installed Storage Management Server Administrator Storage Management Install the Storage Management to implement hardware RAID solutions and configure the storage components attached to your system.
Table 4-2. Managed System Software Components (continued) Component What is Installed Deployment Scenario Systems on Which to be Installed Remote Access Controller Server Administrator CLI + Instrumentation Service + iDRAC or DRAC 5, or DRAC 4 (depending on the type of your Dell PowerEdge system) Install Remote Access Service to receive e-mail alerts for warnings or errors related to voltages, temperatures, and fan speeds.
Table 4-2. Managed System Software Components (continued) Component What is Installed Deployment Scenario Systems on Which to be Installed Broadcom SNMP Agent Broadcom SNMP Agent Install this SNMP agent to enable Server Administrator to obtain information about NICs. This SNMP agent helps identify the NICs. Only on Dell PowerEdge systems on which Server Instrumentation is installed and which are running on the Microsoft Windows operating system.
Installing Managed System Software on Microsoft Windows Operating Systems 5 Overview This section contains the procedure to install managed system software on systems running Microsoft® Windows® operating systems. On Microsoft Windows operating systems, 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.
Installation Procedures Prerequisite Checker NOTE: If you want to use supporting agents for the Simple Network Management Protocol (SNMP), you must install the operating system support for the SNMP standard before or after you install Server Administrator. For more information about installing SNMP, see the installation instructions for the operating system you are running on your system. The setup program (located at \SYSMGMT\srvadmin\windows) starts the Prerequisite Checker program.
Use the RunPreReqChecks.exe /s command (at \SYSMGMT\srvadmin\windows\PreReqChecker) to run the prerequisite check silently. For more information, see "Prerequisite Checker.
3 Click File Add/Remove Snap-in. 4 Select the certificate and shift it to the right side. 5 In the new dialog box, select Computer Account, click Next, and then click Finish. 6 Click OK. 7 Expand Certificates from the newly-added tree. 8 Right-click Personal, select All tasks Request New Certificate. 9 Click Next. 10 Select the appropriate certificate type, Mostly (Computer) and click Enroll. 11 Click Finish.
8 In the Select Features screen, select SelfSSL 1.0 and click Next. 9 Click Next. 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 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.
15 Select Thumbprint. Copy the thumbprint to the clipboard. You can use this parameter while creating the HTTPS listener. 16 Click OK.
4 Provide the appropriate permission(s) to the respective users and click OK. WMI: 1 Click Start and Click Run. 2 Type wmimgmt.msc and click OK. The Windows Management Infrastructure (WMI) screen displays. 3 Right-click on the WMI Control (Local) node in the left pane and click Properties. The WMI Control (Local) Properties screen displays. 4 Click Security and expand the Root node in the namespace tree. 5 Navigate to Root DCIM sysman. 6 Click Security. The Security screen displays.
winrm s winrm/config @{MaxEnvelopeSizekb="4608"} 4 Set the value of MaxTimeoutms to 3 minutes: winrm s winrm/config @{MaxTimeoutms ="180000"} On WinRM version 2.0, enable the compatibility mode for WinRM version 2.0 to use port 443. WinRM version 2.0 uses port 5986 by default.
The setup program invokes the Prerequisite Checker, which uses your system's PCI bus to search for installed hardware such as controller cards. The Dell OpenManage installer features a Typical Setup option and a Custom Setup option for installing Server Administrator and other managed system software. For information on the various components of Server Administrator available in Dell OpenManage and to help you choose the required components to install, see "Deployment Scenarios for Server Administrator.
Custom Installation The sections that follow show how to install Server Administrator and other managed system software using the Custom Setup option. NOTE: Management station and managed system services can be installed in the same or in different directories. You can select the directory for installation. 1 Log on with built-in administrator privileges to the system on which you want to install the system management software. 2 Close all open applications and disable any virus-scanning software.
If you are installing Server Administrator on a non-Dell PowerEdge system, the installer displays only the Server Administrator Web Server option. A selected feature has a hard drive icon depicted next to it. A deselected feature has a red X depicted next to it. By default, if the Prerequisite Checker finds a software feature with no supporting hardware, the checker deselects them. To accept the default directory path to install managed system software, click Next.
Server Administrator Installation With Citrix Application Server Citrix remaps all your hard drive letters when installed. For example, if you install Server Administrator on drive C: and then install Citrix, it may change your drive letter C: to M:. Server Administrator may not work properly because of the remapping. In order to avoid this problem, select one of these options: Option 1: 1 Uninstall Server Administrator. 2 Install Citrix. 3 Reinstall Server Administrator.
Upgrading Guidelines • You cannot upgrade Server Administrator earlier than version 5.0 to version 6.3. You must upgrade to a Server Administrator 5.0 or later version and then upgrade to Server Administrator version 6.3. • If you have installed Server Instrumentation on the managed system, ensure that you install Server Administrator Web Server version 6.1 or later. Installing an earlier version of Server Administrator Web Server may display an error.
Modify If you want to add/remove Server Administrator components: 1 Navigate to the Windows Control Panel. 2 Double-click Add/Remove Programs. 3 Click Dell OpenManage 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 Modify option and click Next. The Custom Setup dialog box appears.
• Yes, reboot my system now. • No, I will reboot my system later. NOTE: If you run the installer from another system and try to add a component using the Modify option, the installer may display an error. This error may be because the source on the system that you ran the installer from is corrupt. You can verify this by checking the following registry entry: HKLM\Software\Classes\Installer\Products\\sourcelist\lastusedsource.
System Recovery on Failed Installation The Microsoft Software Installer (MSI) provides the ability to return a system to its fully working condition after a failed installation. MSI does this by maintaining an undo operation for every Standard Action it performs during an install, upgrade, or uninstall. This operation includes restoration of deleted or overwritten files, registry keys, and other resources.
structure and GUIDs, which break any provided patches or updates. When it is necessary to make any changes to a vendor-provided MSI package, a .mst transform file should always be used to do so. Windows Installer Logging 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
– MgmtSt.log These particular log files are created by default if the Prerequisite Checker user interface (UI) is running. 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. Unattended installation enables you simultaneously to install Server Administrator on multiple systems.
Mapping a Drive to Act as the Typical Unattended Installation Package 1 Share an image of the Dell Systems Management Tools and Documentation DVD with each remote system on which you want to install Server Administrator. You can accomplish this task by directly sharing the DVD or by copying the entire DVD to a drive and sharing the copy. 2 Create a script that maps a drive from the remote systems to the shared drive described in step 1. This script should execute msiexec.exe /i Mapped Drive\SYSMGMT\srvadmi
2 Create a batch script that will execute the installation using the Windows Installer Engine (msiexec.exe). NOTE: For Customized Unattended Installation, each required feature must be included as a command line interface (CLI) parameter for it to be installed. An example is msiexec.exe /i SysMgmt.msi ADDLOCAL= SA,IWS,BRCM /qb. (See "Customization Parameters" for more details and available feature identifications.) 3 Place the batch script in the windows directory on the system hard drive.
• A Prerequisite Checker program that examines the dependency status of selected software features without having to perform an actual installation Optional Command Line Settings Table 5-1 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 full details about all the command line switches for the Windows Installer Tool. Table 5-1.
Table 5-1. 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] missing. /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 NOTE: Type the REINSTALL, and REMOVE CLI parameters in upper case, as they are case-sensitive. REINSTALL and REMOVE customization CLI parameters provide a way to customize the exact software features to install, reinstall, or uninstall when running silently or unattended. With the customization parameters, you can selectively install, reinstall, or uninstall software features for different systems using the same unattended installation package.
msiexec.exe /i SysMgmt.msi REINSTALL=BRCM /qb. This command will run the installation for Dell OpenManage Systems Management and reinstall only the Broadcom agent, in an unattended but not silent mode. You can include the REMOVE customization parameter on the command line and assign the feature ID (or IDs) of the software feature that you would like to uninstall. An example is msiexec.exe /i SysMgmt.msi REMOVE=BRCM /qb.
Table 5-3. 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: See support.microsoft.com for full details on all the error codes returned by the msiexec.exe and InstMsi.exe Windows Installer functions.
4 Select the Remove option and click Next. The Remove the Program dialog box appears. 5 Click Remove. The Uninstalling Dell OpenManage Server Administrator screen appears and provides the status and progress of the software features being uninstalled. When the selected features are uninstalled, the Install Wizard Completed dialog box appears. 6 Click Finish to exit the Server Administrator uninstallation.
Unattended Uninstall Using the Product GUID If you do not have the installation DVD or the MSI package available during an uninstallation, you can use the following command line to uninstall Dell OpenManage systems management software on managed systems or management stations running Windows. For these cases, you can use the package GUIDs to uninstall the product. For managed systems, use this command: msiexec.
Unattended Uninstall Command Line Settings Table 5-1 shows the unattended uninstall command line settings available for unattended uninstallation. Type the optional settings on the command line after msiexec.exe /x SysMgmt.msi with a space between each setting. For example, running msiexec.exe /x SysMgmt.msi /qb runs the unattended uninstallation, and displays the unattended installation status while it is running. Running msiexec.exe /x SysMgmt.
Installing Dell OpenManage Software On Microsoft Windows Server 2008 Core and Microsoft Hyper-V Server 6 Introduction 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 reduces the maintenance and management requirements and the attack surface for those server roles.
Installing Managed System and Management Station Software This section provides instructions on installing managed system and management station software on Windows Server 2008 Core or Hyper-V Server operating system, in the CLI mode. Running PreReqChecker In CLI Mode Run the PreReqChecker before you install Dell OpenManage software. See "Prerequisite Checker" for more information on running Prerequisite Checker in the CLI mode.
• Intel® and Broadcom® agents are selected for a default install only if the corresponding devices are detected on the system. If the corresponding devices are not found, prerequisite checker generates a warning message. • DNS or 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.
Installing Managed System Software In CLI Mode 1 Ensure that all errors or warnings that PreReqChecker detects are corrected before you install managed system components. 2 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.
7 Installing Managed System Software on Supported Linux Operating Systems Overview The Dell™ OpenManage™ installer supports both 32-bit and 64-bit architecture. The following table explains the OS installation matrix for OpenManage. Table 7-1. OS OS Installation Matrix for OpenManage RHEL 4 RHEL 5 SLES 10 SLES 11 ESX 32-bit 64-bit 32-bit 64-bit 32-bit 64-bit 32-bit 64-bit 32-bit 64bit OpenManage UP 6.3 (32-bit) U/UP UP U/UP NS U/UP NS U/UP NS U/U P OpenManage NS 6.
• 32-bit OpenManage that is installed and • other OpenSource components (openwsman-server, openwsmanclient, libwsman1, sblim-sfcb, sblim-sfcc, libcmpiCppImpl0, libsmbios2, smbios-utils-bin) installed as part of 32-bit OpenManage The installation scripts and RPM packages specific to your operating system are provided to install and uninstall Dell OpenManage Server Administrator and other managed system software components.
Server Administrator Device Drivers Server Administrator includes two device drivers for Linux: Systems Management Base Driver (dcdbas) and BIOS Update Driver (dell_rbu). Server Administrator uses these drivers to perform its systems management functions on supported Linux operating systems. Depending on the system, Server Administrator loads one or both of these drivers if required. The device drivers for Linux have been released as open source under the GNU General Public License v2.0.
Dynamic Kernel Support Prerequisites For managed system software to use DKS, the following dependencies must be met before starting Server Administrator. • The running kernel must have loadable module support enabled. • The source for building kernel modules for the running kernel must be available from /lib/modules/`uname –r`/build. On systems running SUSE Linux Enterprise Server, the kernel-source RPM provides the necessary kernel source.
newly built device driver to the /var/omsa/dks/ 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.
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 need to install the IPMI RPM. For more information on supported systems, see the Dell Systems Software Support Matrix available at Dell Support site at support.dell.com/support/edocs/software/omswrels/index.htm.
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 for express installs or custom installs NOTE: If you have downloaded the managed system software installer (available as a .tar.gz file) from the Dell Support site at support.dell.com, the srvadmin-install.sh shell script is present as setup.sh in the root directory.
section for information on any RPMs that you need to manually install prior to installing managed system software. Typically, you may not need to manually install any RPMs. If your system did not have a factory-installed Linux operating system, and you did not install a VMware ESX (version 4 or 4.
• SYSMGMT/srvadmin/linux/custom • SYSMGMT/srvadmin/linux/RPMS • SYSMGMT/srvadmin/linux/supportscripts Express Install Use the provided shell script to perform the express installation. NOTE: On the Red Hat Enterprise Linux 5 operating system, DVDs are auto-mounted with the -noexec mount option. This option does not allow you to run any executable from the DVD. You need to manually mount the DVD and then run executables.
6 Start the Server Administrator services after the installation using the srvadmin-services.sh script by using the sh srvadmin-services start command. Custom Install 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 All RPMs specific to a particular operating system are grouped together as listed in Table 7-2.
Table 7-2.
Table 7-3. Meta RPMs (continued) Meta RPMs Details 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. NOTE: On the Red Hat Enterprise Linux 5 operating system, DVDs are automounted with the -noexec mount option.
NOTE: If you choose to install the Remote Enablement feature, ensure that you install the dependent RPMs before installing this feature. For more information on installing dependent RPMs, see "Dependent RPMs for Remote Enablement". 6 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.
[-u|--update] updates applicable Server Administrator components. [-h|--help] displays this 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 custom installation, the history information on the screen gets cleared off. [-a|--autostart] starts the installed services after components have been installed.
7 Press to exit. You can start the services manually later. Using the Custom Install Script To Run in the Silent Mode The following is an example of a silent custom installation using the srvadmin-install.sh shell script: 1 Log on as root to the system running the supported Red Hat Enterprise Linux or SUSE Linux Enterprise Server 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.
• libcmpiCppImpl0 • libwsman1 • openwsman-server • sblim-sfcb • sblim-sfcc NOTE: In case of SLES 11 SP1, it is recommended that you install the above RPMs from the OS media. Installing Dependent RPMs 1 Check if the dependent RPMs are already installed. If yes, remove the installed RPMs. 2 Ensure that Pegasus RPMs are uninstalled. 3 Check if the openwsmand and sfcbd binaries are already installed using make-install.
Table 7-4. Required Dependencies Packages Red Hat Enterprise Server SUSE Linux Enterprise Server Openwsman • OpenSSL • LibOpenSSL • LibXML • LibXML • Pkgconfig • Pkg-config • CURL • libCURL • Chkconfig • aaa_base • Initscript • aaa_base • SBLIM-SFCC • SBLIM-SFCC SBLIM SFCC CURL LibCURL SBLIM SFCB • zlib • zlib • CURL • LibCURL • PAM • PAM • OpenSSL • LibOpenSSL • Chkconfig • aaa_base • Initscript • aaa_base 6 Install the dependent RPMs.
Post-Installation Configuration for Remote Enablement This section details the steps to configure the dependent RPMs if you have installed the Remote Enablement feature. The post-installation configuration script is available at /opt/dell/srvadmin/etc/ on the server file system. After installing all the dependent RPMs and the Remote Enablement feature, execute the autoconf_cim_component.sh script. Before executing the autoconf_cim_component.sh script, ensure Dell OpenManage is installed.
Configuring CRL for the openwsman Client You need to configure the Certificate Revocation List (CRL) used by Server Administrator Web Server. To do this: 1 Mention a valid CRL file in /etc/openwsman/openwsman_client.conf. 2 If left blank, the CRL check is ignored. NOTE: CRL support is only present on SUSE Linux Enterprise Server version 11 and Red Hat Enterprise Linux Server version 5 update 5.
This file is auto-generated. User changes will be destroyed the next time authconfig is run. auth required /lib/security/$ISA/pam_env.so 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.
session required /lib/security/$ISA/pam_unix.so session optional /lib/security/$ISA/pam_krb5.so Winbind Configuration for openwsman and sfcb for SUSE Linux Enterprise Server Operating Systems 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 Take a backup of the following files: • /etc/pam.d/openwsman • /etc/pam.d/sfcb • /etc/pam.d/system-auth • /etc/pam.
Workaround for the Libssl Issue If the required library needed by openwsman is present on your system, the autoconf_cim_component.sh script tries to resolve the libssl.so issue. However, if the library is not present, then the script will report the same. Check if the latest version of the libssl library is installed on your system and then create a soft link with libssl.so. For example: On a 32-bit OpenManage installation, if you have libssl.so.0.9.8a and libssl.so.0.9.
Custom Uninstallation of Specific Components Some individual components of Dell OpenManage can be uninstalled without uninstalling all of Dell OpenManage. Following are examples: To uninstall only the Server Administrator Web Server, use this command: rpm –e `rpm -qa | grep srvadmin-iws` To uninstall the storage component, use this command: rpm –e `rpm -qa | grep srvadmin-storage` During an uninstallation, files in which user settings are made are preserved with the .rpmsave file extension.
to install other Supplemental Packs. If not, select Skip and press Enter. The XenServer is installed successfully. • On a running system a Burn the Supplemental Pack ISO file to a CD or download the ISO file to your server. b If you are downloading the ISO file, mount it on a temporary directory $ mount -o loop .iso /mnt If you burned the ISO file to a CD, insert it in the optical drive and run $ mount /dev/cdrom /mnt c Install the supplemental pack.
NOTE: If you are connecting to a XenServer™ 5.6 managed node using server administrator web server, use port 5986 in the format Hostname:Port Number, or IP address:Port Number. 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 onto supported Dell servers.
Installing Managed System Software on Supported Linux Operating Systems
8 Dell OpenManage on VMware ESXi VMware ESXi is factory-installed on some Dell™ systems. For a list of these systems, see the latest Dell Systems Software Support Matrix on the Dell Support website at support.dell.com/support/edocs/software/omswrels/index.htm. You can use Server Administrator Web Server version 6.3 to access VMware ESXi 4.0 update 1 and VMware ESXi 4.1 systems. Dell OpenManage on VMware ESXi 4.0 Update 1 and ESXi 4.1 Dell OpenManage Server Administrator is available as a .
vihostupdate.pl --server -i -b 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. In case of a failed update, see "Troubleshooting". 6 Restart the ESXi host system.
You must install the Server Administrator Web Server separately on a management station. For information on installing the Server Administrator Web Server, see "Installing Managed System Software on Microsoft Windows Operating Systems" and "Installing Managed System Software on Supported Linux Operating Systems". NOTE: Ensure that you install only Server Administrator Web Server version 6.1 and later. Server Administrator Web Server version 6.0.3 is not supported on VMware ESXi 4.0 and later.
VMware ESXi system. CIM OEM providers are disabled by default on VMware ESXi. You must enable the CIM OEM providers on the VMware ESXi 4.0/ESXi 4.1 system before accessing it using Server Administrator Web Server. Enabling CIM OEM Providers Using vSphere Client (for VMware ESXi 4.0/ESXi 4.1) To enable CIM OEM providers using VMware vSphere Client, you need to have the vSphere Client tool installed.
vicfg-advcfg.pl --server --username --password --set 1 UserVars.CIMOEMProvidersEnabled NOTE: The .pl extension is not required if you are using vSphere CLI on Linux. 3 For the changes to take effect without restarting the system, use the Restart Management Agents option in the Direct Console User Interface (DCUI) on the local console of the VMware ESXi system.
Server Administrator supports SNMP traps on VMware ESXi but does not support SNMP Get and Set operations because VMware ESXi does not provide the required SNMP support. You can use the VMware vSphere CLI to configure a system running VMware ESXi to send SNMP traps to a management application such as IT Assistant. NOTE: For more information about using the VMware vSphere CLI, see the VMware support site at www.vmware.com/support.
vicfg-snmp.pl --server --username --password -T NOTE: The .pl extension is not required if you are using vSphere CLI on Linux or using vMA.
Dell OpenManage on VMware ESXi
9 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 users or groups to a given set of privileges and to systems (Product Objects) in your network.
Figure 9-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.
For example, 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 an Administrator privilege on both DRAC 4 cards and give user3 a Login privilege on the RAC2 card. Figure 9-2 shows how you set up the Active Directory objects in this scenario. Figure 9-2.
6 Add User3 as Members in Association Object 2 (AO2), Priv2 as Privilege Objects in AO2, and RAC2 as RAC Products in AO2. See "Adding Users and Privileges to Active Directory" for detailed instructions. Figure 9-3 shows how to setup the Active Directory objects in multiple domains for RAC. In this scenario, you have two DRAC 4 cards (RAC1 and RAC2) and three existing Active Directory users (User1, User2, and User3). User1 is in Domain1, but User2 and User3 are 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. 5 Group User1 and User2 into Group1. The group scope of Group1 must be Universal. 6 Add Group1 as Members in Association Object 1 (AO1), Priv1 as Privilege Objects in AO1, and both RAC1 and RAC2 as Products in AO1.
Figure 9-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 or Windows 2003 mode. 2 Create two Association Objects, AO1 and AO2, in any domain. The figure shows the objects in Domain1.
Note that neither of the Association objects needs to be of Universal scope in this case. Configuring Active Directory to Access Your Systems Before you can use Active Directory to access your systems, you must configure both the Active Directory software and the systems. 1 Extend the Active Directory schema (see "Extending the Active Directory Schema.") 2 Extend the Active Directory Users and Computers Snap-in (see "Installing the Dell Extension to the Active Directory Users and Computers SnapIn.
3 Restart the DSM SA Connection Service after saving the omsaoem.ini file. Extending the Active Directory Schema RAC, Server Administrator, and IT Assistant schema extensions 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.
To use the LDIF files, see the instructions in the readme that is in the LDIF files directory. To use the Dell Schema Extender to extend the Active Directory Schema, perform the steps in "Using the Dell Schema Extender." You can copy and run the Schema Extender or LDIF files from any location. Using the Dell Schema Extender CAUTION: The Dell Schema Extender uses the SchemaExtenderOem.ini file.
Table 9-2. Class Definitions for Classes Added to the Active Directory Schema (continued) Class Name Assigned Object Identification Number Class Type (OID) dellOmsa2AuxClass 1.2.840.113556.1.8000.1280.1.2.1.1 Auxiliary Class dellOmsaApplication 1.2.840.113556.1.8000.1280.1.2.1.2 Structural Class dellIta7AuxClass 1.2.840.113556.1.8000.1280.1.3.1.1 Auxiliary Class dellItaApplication 1.2.840.113556.1.8000.1280.1.3.1.2 Structural Class Table 9-3. dellAssociationObject Class OID 1.2.840.113556.1.
Table 9-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 9-6. dellOmsa2AuxClass Class OID 1.2.840.113556.1.8000.1280.1.2.1.1 Description This class is used to define the privileges (Authorization Rights) for Server Administrator.
Table 9-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 9-9. dellItaApplication Class OID 1.2.840.113556.1.8000.1280.1.3.1.2 Description This class represents the IT Assistant application.
Table 9-10. General Attributes Added to the Active Directory Schema (continued) Attribute Name/Description Assigned OID/Syntax Object Identifier Single Valued dellProductMembers 1.2.840.113556.1.8000.1280.1.1.2.2 FALSE List of dellRacDevices Objects that Distinguished Name belong to this role. This attribute is the (LDAPTYPE_DN forward link to the 1.3.6.1.4.1.1466.115.121.1.12) dellAssociationMembers backward link. Link ID: 12070 dellAssociationMembers 1.2.840.113556.1.8000.1280.1.1.2.
Table 9-12. IT Assistant-Specific Attributes Added to the Active Directory Schema Attribute Name/Description Assigned OID/Syntax Object Identifier Single Valued dellItaIsReadWriteUser 1.2.840.113556.1.8000.1280.1.3.2.1 TRUE TRUE if the User has Read-Write rights in IT Assistant Boolean (LDAPTYPE_BOOLEAN 1.3.6.1.4.1.1466.115.121.1.7) dellItaIsAdminUser 1.2.840.113556.1.8000.1280.1.3.2.2 TRUE if the User has Administrator rights in IT Assistant Boolean (LDAPTYPE_BOOLEAN 1.3.6.1.4.1.1466.115.121.1.
NOTE: For more information about the Active Directory Users and Computers snap-in, see your Microsoft documentation. Opening the Active Directory Users and Computers Snap-In NOTE: On Windows 2000 Server, you can extend the schema but will not able to install the Dell extension to the snap-in.
To open the Active Directory Users and Computers snap-in, perform the following steps: 1 If you are on the domain controller, click Start Admin Tools Active Directory Users and Computers. If you are not on the domain controller, you must have the appropriate Microsoft administrator pack installed on your local system. To install this administrator pack, click Start Run, type MMC and press Enter. The Microsoft Management Console (MMC) window appears. 2 Click File in the Console 1 window.
3 Type in a name for the new object. This name must match the Active Directory product name as discussed in "Configuring Active Directory Using CLI on Systems Running Server Administrator". 4 Select the appropriate Product Object. 5 Click OK. Creating a Privilege Object Privilege Objects must be created in the same domain as the Association Object to which they are associated. 1 In the Console Root (MMC) window, right-click a container. 2 Select New.
The New Object window appears. 4 Type in a name for the new object. 5 Select Association Object. 6 Select the scope for the Association Object. 7 Click OK. Adding Objects to an Association Object By using the Association Object Properties window, you can associate users or user groups, privilege objects, systems, RAC devices, and system or device groups. NOTE: RAC users must use Universal Groups to span domains with their users or RAC objects. You can add groups of Users and Products.
2 Type the system, device, or group name and click OK. 3 In the Properties window, click Apply and then OK. Configuring Your Systems or Devices For instructions on how to configure your Server Administrator or IT Assistant systems using CLI commands, see "Configuring Active Directory Using CLI on Systems Running Server Administrator". For DRAC users, see the Dell Remote Access Controller 4 User’s Guide or Dell Remote Access Controller 5 User’s Guide.
Table 9-13. Active Directory Service Configuration Parameters name=value pair Description enable= true: Enables Active Directory service authentication support. false: Disables Active Directory service authentication support adprodname= Specifies the name of the product as defined in the Active Directory service. This name links the product with the Active Directory privilege data for user authentication.
Using Microsoft Active Directory
10 Prerequisite Checker Command Line Operation of the Prerequisite Checker You can run the prerequisite check 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 check, an HTML file (omprereq.htm) is created in the %Temp% directory. This file contains the results of the prerequisite check. The Temp directory is typically not X:\Temp, but X:\Documents and Settings\us
Table 10-1. Return Codes While Running the Prerequisite Check Silently (continued) Return Code Description 3 An error condition, or conditions, is associated with the software. It is required that you resolve the conditions causing the error before proceeding with the installation of that software. If you do not resolve the issues, the software will not be installed. -1 A Microsoft® Windows® Script Host (WSH) error. The Prerequisite Checker will not run. -2 The operating system is not supported.
Table 10-2.
Prerequisite Checker
Frequently Asked Questions 11 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 will get CLI features only. What ports do Dell OpenManage applications use? The default port used by Server Administrator is 1311. The default ports used by Dell OpenManage™ IT Assistant are 2607 (for the connection service) and 2606 (for the network monitoring service). These ports are configurable.
• Find out the version of Server Administrator that was previously installed. • Download the installation package for that version from the Dell Support website at support.dell.com. • Locate SysMgmt.msi from the SYSMGMT\srvadmin\windows\SystemsManagement directory and enter the following command at the command prompt to force a reinstall. msiexec /i SysMgmt.msi REINSTALL=ALL REINSTALLMODE=vomus • Select Custom Setup and choose all the features that were originally installed.
When launching the Dell OpenManage Installer, 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." What do I do? This is most likely due to insufficient COM permissions on the system. See the following article to remedy this situation: support.installshield.com/kb/view.
When I run Dell OpenManage Installer, I see unreadable characters on the Prerequisite check information screen. When you run Dell OpenManage Install in English, German, French, or Spanish and get unreadable characters on the Prerequisite Check Information screen, ensure that your browser encoding has the default character set. Resetting your browser encoding to use the default character set will resolve the problem.
I downloaded the Server Administrator files for Windows from the Dell Support website and copied it to my own media. When I tried to launch the SysMgmt.msi file, it failed. What is wrong? MSI requires all installers to specify the MEDIAPACKAGEPATH property if the MSI file does not reside on the root of the DVD. This property is set to SYSMGMT\srvadmin\windows\SystemsManagement for the managed system software MSI package. If you decide to make your own DVD you must ensure that the DVD layout stays the same.
The Prerequisite Checker is available for Windows. See the readme file at SYSMGMT\srvadmin\windows\PreReqChecker\readme.txt on the Dell Systems Management Tools and Documentation DVD, for detailed information about how to use the Prerequisite Checker. In the Prerequisite Checker screen, I get the message "An error occurred while attempting to execute a Visual Basic Script. Please confirm that Visual Basic files are installed correctly.
Can I launch my installation without running the Prerequisite Checker? How do I do that? Yes, you can. For example, you can run the MSI of the managed system software, directly from the SYSMGMT\srvadmin\Windows\SystemsManagement. In general, it is not a good idea to bypass the prerequisite information as there could be important information that you would not know otherwise.
Table 11-1. Dell OpenManage Features Under Windows (continued) Feature Name in Windows Remote Access Controller Console (DRAC 4) Remote Access Controller 4 (DRAC 4) Red Hat® Enterprise Linux® or SUSE® Linux Enterprise Server After installing Server Administrator, I cannot log on. After installing Server Administrator, log out and then log in again to access the Server Administrator Command Line Interface (CLI).
I have performed a non-default install of your Linux operating system using your Linux operating system media, I see missing RPM file dependencies while installing Server Administrator? Server Administrator is a 32-bit application. When installed on a system running a 64-bit version of Red Hat Enterprise Linux operating system, the Server Administrator remains a 32-bit application, while the device drivers installed by Server Administrator are 64-bit.
When using the rpm -e 'rpm -qa | grep srvadmin' command to remove Dell OpenManage systems management software, some RPM utility versions may schedule an uninstall 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.
rpm --import /mnt/dvdrom/SYSMGMT/srvadmin/linux/RPM-GPG-KEY What are the names of all the Dell OpenManage features under Red Hat Enterprise Linux or SUSE Linux Enterprise Server? The following table lists the names of all Dell OpenManage features and their corresponding init script names under Red Hat Enterprise Linux and SUSE Linux Enterprise Server operating systems: Table 11-2.
Table 11-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. It provides motherboard alerts and contains the CLI that allows for monitoring and control of Server Administrator, for example, omconfig, omdiag, and omreport.
Table 11-3. Names of the Directories Under the srvadmin/linux/custom/ Directory (continued) Name of RPM Description Other Server Administrator RPMs required srvadminomacore Server Administrator — Systems management srvadmin-omilcore managed mode core and CLI. and srvadmin-deng srvadminomhip Server Administrator Instrumentation Service srvadmin-omilcore, Integration Layer — Provides Instrumentation srvadmin-deng, CLI.
Table 11-3. Names of the Directories Under the srvadmin/linux/custom/ Directory (continued) Name of RPM Description Other Server Administrator RPMs required srvadmin-rac4- Remote Access Card Data Populator — components Remote Access Controller components. srvadmin-omilcore, srvadmin-deng, srvadmin-hapi, and srvadmin-racsvc srvadminracadm4 RAC Command Interface — The command line user interface to the Remote Access Controller (RAC).
Table 11-3. Names of the Directories Under the srvadmin/linux/custom/ Directory (continued) Name of RPM Description Other Server Administrator RPMs required srvadminstorage Storage Management — Provides Systems Management Storage Services.
Table 11-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 management of 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 11-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 11-3. Names of the Directories Under the srvadmin/linux/custom/ Directory (continued) Name of RPM Description Other Server Administrator RPMs required srvadminomacore Server Administrator — Systems management srvadmin-omilcore managed mode core and CLI. and srvadmin-deng srvadminomcommon Provides Common Framework required by Server Administrator.
In this case, if you try to install Server Administrator later by running the sh srvadmin-install.sh command, you will get the following message: Server Administrator version X.Y.Z is currently installed. Installed Components are: • srvadmin-omilcore-X.Y.Z-N • srvadmin-hapi-X.Y.Z-N Do you want to upgrade Server Administrator to X.Y.Z? Press (y for yes | Enter to exit): On pressing y, only those Server Administrator packages (in the above example, srvadmin-omilcore-X.Y.Z-N and srvadmin-hapi-X.Y.
Table 11-4. Daemons that run on Red Hat Enterprise Linux and SUSE Linux Enterprise Server once Server Administrator is started (continued) Daemon Name Name in Red Hat Enterprise Linux and SUSE Linux Enterprise Server dsm_sa_datamgr32d DSM SA Data Manager — Server Administrator data manager daemon started by DSM SA Data Engine service. dsm_sa_eventmgr32d DSM SA Event Manager — Server Administrator event and logging daemon started by DSM SA Data Engine service.
Table 11-5.
Frequently Asked Questions
A OpenManage Linux Installer Packages This appendix lists the OpenManage Linux installer pacakages. Table A-1. Meta RPMs RPM Description Dependant packages Required for OM 6.1 OM 6.2 OM 6.
Table A-1. Meta RPMs (continued) RPM Dependant packages Required for srvadmin Meta package for installing webserver the Server Administrator Web Server feature srvadmin-iws srvadminsmcommon srvadminsmweb srvadmin storageser vices srvadminstorage srvadminsmcommon srvadmin-cm srvadminmegalib (only for 32-bit install) srvadmin-fsa (Removed in 6.
Table A-1. Meta RPMs (continued) RPM Description Dependant packages Required for srvadmin Meta rpm for -rac4 RAC4 components srvadminomilcore srvadminracadm4 srvadminracdrsc4 srvadminracsvc srvadmin-rac4populator* srvadmin-raccomponents* srvadminracdrsc* * - 6.3 packages srvadmin- Meta rpm for rac5 RAC5 components srvadminomilcore srvadminracdrsc5 srvadminracadm5 srvadminracdrsc* srvadmin-raccomponents * - 6.3 packages OM 6.1 OM 6.2 OM 6.
Table A-1. Meta RPMs (continued) RPM Description srvadmin- Meta rpm for idrac iDRAC components Dependant packages Required for OM 6.1 srvadminomilcore srvadminidracdrsc srvadminidracadm srvadminracdrsc* srvadmin-raccomponents* srvadminargtable2* * - 6.3 packages iDRAC Y manageme nt using Server Administra tor GUI/CLI, iDRAC tools OM 6.2 OM 6.3 Y Y OM 6.2 OM 6.3 Y Table A-2. Server Instrumentation and SNMP monitoring RPM Description OM Dependant Required packages for OM 6.
Table A-2. Server Instrumentation and SNMP monitoring (continued) RPM Description OM Dependant Required packages for OM 6.1 OM 6.2 OM 6.
Table A-3. Packages needed for local management that are used by GUI and CLI components RPM Description OM Dependant Required packages for srvadmin omcomm on Common framework / libraries for GUI/CLI srvadminomilcore OM 6.2 OM 6.
Table A-3. Packages needed for local management that are used by GUI and CLI components (continued) RPM Description OM Dependant Required packages for srvadmin Change srvadmin-cm Management omacore inventory collector. Feeds s/w inventory data to management station applications like ITA OM 6.1 OM 6.2 OM 6.3 S/W inventory & updates using ITA Table A-4.
Table A-4. Server Administrator web server (GUI) for local and remote management RPM Description Dependant packages Required for openwsm Openwsman an-client client libraries None libwsman Openwsman 1 libraries used by client and server components None OM 6.1 OM 6.2 OM 6.3 Server Y Administra tor GUI to manage remote nodes using WSMAN Y Y Openwsma Y n support library Y Y Table A-5.
Table A-5. Server Administrator Remote Enablement (Standard Agent) (continued) RPM Description OM Dependant Required packages for OM 6.1 OM 6.2 OM 6.3 Y Obsolete Obsolete srvadmin Enables NA -ssa management of the system from a remote system on which Server Administrator Web Server is installed, using WS-Man interfaces. NA srvadmin itunnelpr ovider sblim-sfcb >= 1.3.2 sblim-sfcc >= 2.1.0 openwsmanclient >= 2.1.5 openwsmanserver >= 2.1.5 libwsman1 >= 2.1.5 libcmpiCppIm pl0 >= 2.0.
Table A-5. Server Administrator Remote Enablement (Standard Agent) (continued) RPM Description OM Dependant Required packages for sblimsfcb Small None Footprint CIM Broker (sfcb) CIM server conforming to the CIM OM 6.1 OM 6.2 OM 6.3 Enabling Y remote manageme nt of server Y Y Enabling Y remote manageme nt of server Y Y Enabling N remote manageme nt of server Y Y NA Obsolete Obsolete Operations over HTTP protocol.
Table A-6. Storage Instrumentation, SNMP Monitoring, GUI and CLI Plugins RPM Description OM Dependant Required packages for OM 6.1 OM 6.2 OM 6.
Table A-6. Storage Instrumentation, SNMP Monitoring, GUI and CLI Plugins RPM Description OM Dependant Required packages for srvadmin Provides library None -storelib- for interfacing sysfs with the kernel's sys filesystem. Used by LSI storelib libraries OM 6.1 OM 6.2 OM 6.3 Storage N Instrument ation Y Y *N/A for VmWare ESX srvadmin Provide -sysfsutils utilities for interfacing with sysfs filesystem.
Table A-6. Storage Instrumentation, SNMP Monitoring, GUI and CLI Plugins RPM Description OM Dependant Required packages for srvadmin smcomm on Common framework / libraries for GUI/CLI (for storage management) None srvadmin GUI plugins for srvadmin-smweb storage omcommon management OM 6.1 OM 6.2 OM 6.3 Storage N Manageme nt using Server Administra tor GUI/CLI Y Y Storage N Manageme nt using Server Administra tor GUI Y Y Table A-7.
Table A-7. RAC Instrumentation, SNMP Monitoring, GUI and CLI Plugins (continued) RPM Description OM Dependant Required packages for OM 6.1 OM 6.2 OM 6.3 srvadmin RAC CLI and -racdrsc4 Web Plugin to Server Administrator for DRAC 4 srvadminomilcore srvadmin-deng srvadminomcommon srvadminomacore srvadmin-rac4components DRAC 4 Y manageme nt using Server Administra tor GUI/CLI Y Obsolete.
Table A-7. RAC Instrumentation, SNMP Monitoring, GUI and CLI Plugins (continued) RPM Description OM Dependant Required packages for OM 6.1 OM 6.2 OM 6.3 srvadmin Provides CLI srvadmintools for omilcore idracadm iDRAC srvadmin-hapi administration RAC CLI tools for iDRAC Y Y Y srvadmin RAC CLI and -idracdrsc Web Plugin to Server Administrator for iDRAC iDRAC Y manageme nt using Server Administra tor GUI/CLI Y Obsolete.
Table A-7. RAC Instrumentation, SNMP Monitoring, GUI and CLI Plugins (continued) RPM Description OM 6.2 OM 6.
Table A-8. Enable Software inventory and updates using IT Assistant RPM Description OM Dependant Required packages for srvadmin Change srvadmin-cm Management omacore inventory collector. Feeds s/w inventory data to management station applications like ITA OM 6.1 Software Y inventory & updates using ITA OM 6.2 OM 6.
OpenManage Linux Installer Packages
Index A B access read-only, 20 write, 20 batch script, 72 BIOS, 14 access control, 20 Active Directory, 19-20, 22, 30, 120, 126, 133, 138 object identifiers, 119 objects, 121 schema, 127 schema extender utility, 127-128 schema extensions, 119 C ADDLOCAL, 75 Certification Authority, 45 administrator, 20 CIM, 16, 27, 31 Administrator Pack, 133 Citrix, 64 Administrator privileges, 20 CLI, 16, 22, 75, 145 agent, 38 SNMP, 30 command line, 75 alert log, 16 CA, 45 certificate, 56 certificates Web,
Dell, 53, 119 G Dell base OID, 119 Globally Unique Identifier (GUID), 76 Dell organizational unit, 127 Dell Remote Access Controller, 121 group privileges, 20 GUID, 69 dellIta7AuxClass, 131 dellItaApplication, 131 dellOmsaApplication, 130 dellProduct, 130 dependency check, 106 distribution software, 79 DKS, 87-88 prerequisites, 88 DRAC, 135, 138 DRAC 4, 155 DRAC 5 controller, 17 H help, 17 hot spares, 14 HTTPS, 22 I INI file, 68 inoperable system, 17 installation unattended, 70 Instrumentation, 21
L O LDAP, 130 oem.
software, 27 racadm, 19 LDIF, 127 srvadmin-install, 99 RBAC, 20 SCSI, 14 readme, 17, 25 secure socket layer, 22 read-only access, 20 security administration, 20 Red Hat Enterprise Linux, 34-35, 38, 106, 152 Security Group Type, 136 REINSTALL, 75 remote access, 12 remote access controller, 27 remote enablement installing WinRM, 55 requirements, 55 remote system, 71 REMOVE, 75 Server Administrator, 16, 124, 155 Services, 94, 151 session timeout, 44 setup express, 27 Simple Network Management Protoc
storage management, 21 Storage Management Service, 151 SysMgmt.msi, 149 systems management protocol, 27 Windows Installer Engine, 72 Installer Service, 68 Windows Management Instrumentation, 27 WMI, 27, 31 write access, 20 T TCP/IP, 26 time-out, 19 tools ISV, 71 X X.
Index
