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. © 2009 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 . . 12 Dell OpenManage Systems Management Software Dell Systems Management Tools and Documentation DVD 12 Dell Server Updates DVD . . . . . . . . . . . . . . 14 . . . . . . . . . . 15 . . . . . . . . . . . 15 . . . . . . . . . . . .
. . . . . . . . . . . . . . . . 25 Supported Operating Systems and Web Browsers. 25 System Requirements . 26 Installation Requirements . . . . . . . . . . . . . . . Windows Server 2003 R2 and the R2 IPMI Device Driver 28 Digital Certificates . . . . . . . . . . . . . . . . . Configuring a Supported Web Browser . . . . . . . . . 29 30 Viewing Localized Versions of the Web-Based Interface 30 . . . . . . . . . . . . . 30 . . . . . . . . . . . . . .
. . . . . . . . . . . 55 . . . . . . . . . . . . . . . . . . 55 Remote Enablement Requirements Installing WinRM Certificate Authority - Signed/Self-Signed Certificate 55 Using a Certificate Signed by the CA . . . . . . . . 55 Using the SelfSSL Tool to Generate Self-signed Certificates 56 Configuring User Authorization for WinRM and WMI Servers 58 . . 59 Configuring the Envelope Size for WinRM . Configuring the Windows Firewall for WinRM . . . . .
Uninstalling Managed System Software . . . . . . . . 77 Uninstalling Managed System Software Using Dell-provided Media . . . . . . . . . . . . . . . . . . . . . . . . 77 Uninstalling Managed System Software Features Using the Operating System . . . . . . . . . . . . . . . . . . 78 Unattended Uninstall Using the Product GUID . . . 79 Performing an Unattended Uninstallation of Managed System Software . . . . . . . . . . . . . . . . . . . . . .
Using Dynamic Kernel Support After Server Administrator Installation . . . . . . . . . . . . . . . . . . . . . 87 Copying a Dynamically Built Device Driver to Systems Running the Same Kernel . . . . . . . . . . . . . . . . . . 88 OpenIPMI Device Driver . . . . . . . . . . . . . . . . . 89 Degradation of Functionality When the Server Administrator Instrumentation Service is Started . . . . . . . . . 89 Installing Managed System Software . . . . . . . . . .
Dell OpenManage on VMware ESXi . . . 107 Dell OpenManage on VMware ESXi 3.5 Update 5 . . . 107 Dell OpenManage on VMware ESXi 4.0 Update 1 . . . 107 . . . . . . . . . . . . . . 108 Using the vSphere CLI Using the VMware vSphere Management Assistant 108 Troubleshooting . . . . . . . . . . . . . . . . . . 109 Enabling Server Administrator Services on the Managed System 110 Enabling CIM OEM Providers Using VMware Infrastructure Client (for VMware ESXi 3.5) . . . . . . . . . . . . . . .
10 Prerequisite Checker . . . . . . . . . . . . . . 137 Command Line Operation of the Prerequisite Checker . 137 11 Frequently Asked Questions General . . . . . . . . . . 141 . . . . . . . . . . . . . . . . . . . . . . . . . Microsoft® Windows® 141 . . . . . . . . . . . . . . . . . 141 Red Hat® Enterprise Linux® or SUSE® Linux Enterprise Server 148 Glossary Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents
Introduction Overview This guide contains information to help you install Dell™ OpenManage™ Server Administrator on managed systems. A managed system is a system that 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.
• 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.
• 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 http://support.dell.com/support/edocs/software/omswrels/index.htm. This link also contains user documentation on Dell OpenManage applications.
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. For information on installing Server Administrator, see "Installing Managed System Software on Microsoft Windows Operating Systems" or "Installing Managed System Software on Supported Linux Operating Systems".
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 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 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 http://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 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 Multilingual User Interface Pack is a set of language specific resource files that can be added to the English version of a supported Windows operating system.
• 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.
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.
Deployment Scenarios for Server Administrator
Installing Managed System Software on Microsoft Windows Operating Systems 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.
This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests." is logged in Windows Event Log. You can safely ignore this message and continue with installation. 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:.
Upgrading Guidelines • You cannot upgrade Server Administrator earlier than version 5.0 to version 6.2. You must upgrade to a Server Administrator version later than 5.0 and then upgrade to Server Administrator version 6.2. • 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.
This dialog enables you to modify, repair, or remove the program. 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.
All Server Administrator features are uninstalled. 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 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.
Installing Managed System Software on Supported Linux Operating Systems Overview The Dell™ OpenManage™ installer provides installation scripts and RPM packages specific to your operating system to install and uninstall Dell OpenManage Server Administrator and other managed system software components. These installation scripts and RPMs are located in the SYSMGMT/srvadmin/linux/RPMS/ directory. The custom install script srvadmin-install.sh allows custom and interactive installation.
file. By installing or copying any of the files on the Dell-provided media, you are agreeing to the terms found in this file. This file is also copied to the root of the software tree where you choose to install the Dell OpenManage software. Server Administrator Device Drivers Server Administrator includes two device drivers for Linux: Systems Management Base Driver (dcdbas) and BIOS Update Driver (dell_rbu).
Determining the Running Kernel 1 Log in as root. 2 Type the following command at a console and press : uname -r The system displays a message identifying the running kernel. 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.
Copying a Dynamically Built Device Driver to Systems Running the Same Kernel When Server Administrator dynamically builds a device driver for the running kernel, it installs the device driver into the /lib/modules//kernel/drivers/firmware directory, where is the kernel name (returned by typing uname -r).
NOTE: When you have uninstalled Server Administrator from system B, the /var/omsa/dks//*. files that you copied to system B are not removed. You must remove the files if they are no longer needed. 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.
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, in interactive mode 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 3.
• 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-1.
Table 7-1.
NOTE: Ensure that you install Server Administrator Web Server or Remote Enablement, or Server Instrumentation before installing Remote Access Controller or Storage Management. 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".
[-r|--rac] installs applicable RAC components, including Server Instrumentation. [-w|--web] installs Server Administrator Web Server. [-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.
6 Press to copy, to install, to reset and start over, or to quit. If you press , you are prompted to enter the absolute destination path. When the installation is complete, the script will have an option for starting the services. 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.
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. The dependent RPMs are available on the Dell Systems Management Tools and Documentation DVD at srvadmin\linux\RPMS\supportRPMS\opensourcecomponents. Install the following RPMs: • libcmpiCppImpl0-2.0.0Dell-x.x.rhel5.i386.rpm • libwsman1-2.1.5Dell-x.x.rhel5.i386.rpm • openwsman-client-2.1.5Dell-x.x.rhel5.i386.
sfcbd or You can check the existence of the above binaries in the /usr/local/sbin directory. 4 If the binaries are installed, uninstall these binaries. 5 Check for the required dependencies for the openwsman and sfcbd RPMs listed in Table 7-2. Table 7-2.
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.rpm Post-Installation Configuration for Remote Enablement This section details the steps to configure the dependent RPMs if you have installed the Remote Enablement feature.
Reusing an Existing Certificate If you have a self-signed or CA-signed certificate, you can use the same certificate for the openwsman server by updating the ssl_cert_file and ssl_key_file values, grouped under [server] tag, in /etc/openwsman/openwsman.conf with your existing certificate values. Configuring CRL for the openwsman Client You need to configure the Certificate Revocation List (CRL) used by Server Administrator Web Server.
3 Replace the content of /etc/pam.d/system-auth with: %PAM-1.0 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.
password required /lib/security/$ISA/pam_deny.so session required /lib/security/$ISA/pam_limits.so 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 1 Take a backup of 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.
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: 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.
During an uninstallation, files in which user settings are made are preserved with the .rpmsave file extension. Log files are also preserved after the uninstallation. Using Dell OpenManage with Citrix XenServer Dell Edition™ Dell OpenManage Server Administrator is pre-installed in Citrix® XenServer Dell Edition, hence no installation steps are required. See the Citrix XenServer Dell Edition Solution Guide at http://support.dell.
Installing Managed System Software on Supported Linux Operating Systems
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 http://support.dell.com/support/edocs/software/omswrels/index.htm. You can use Server Administrator Web Server version 6.2 to access VMware ESXi 3.5 update 5 and VMware ESXi 4.0 update 1 systems. Dell OpenManage on VMware ESXi 3.
Download VMware vSphere Command Line Interface (vSphere CLI) from http://www.vmware.com and install on your Microsoft Windows or Linux system. Alternately, you can import VMware vSphere Management Assistant (vMA) into your ESXi 4 host. Using the vSphere CLI 1 Copy the oem-dell-openmanage-esxi_6.2.0-A00.zip file to a directory on your system. 2 If you are using Microsoft Windows, navigate to the directory in which you have installed the vSphere CLI utilities to execute the command mentioned in step 4.
3 Shut down all guest operating systems on the ESXi 4.0 host and put the ESXi 4.0 host in maintenance mode. 4 In the vMA, execute the following command: vihostupdate --server -i -b 5 Enter the root username and password of the ESXi 4.0 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 4.0 host system.
signature mismatch : metadata.zip Unable to unpack update package. This error is displayed if you are using an older version of the Remote CLI. Download and install the vSphere version of the CLI. • When attempting to use the vihostupdate command, the following error may be displayed: Unable to create, write or read a file as expected.I/O Error (28) on file : [Errno 28] No space left on device. See the VMware KB article 1012640 at http://kb.vmware.com to fix this error.
5 Change the value of the Enable OEM Provider field to 1. 6 Click OK. 7 For the change 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. If the changes are not effective and you cannot connect to the VMware ESXi host using Server Administrator, restart the VMware ESXi system. Enabling CIM OEM Providers using VMware Infrastructure Remote CLI (for VMware ESXi 3.
Enabling CIM OEM Providers Using vSphere Client (for VMware ESXi 4.0) To enable CIM OEM providers using VMware vSphere Client, you need to have the vSphere Client tool installed. You can download and install the tool from https:// where is the IP address of the VMware ESXi 4 system. To enable CIM OEM providers on the VMware ESXi 4 system using vSphere Client: 1 Log on to the VMware ESXi 4 host system using vSphere Client. 2 Click the Configuration tab.
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. If the changes are not effective and you cannot connect to the VMware ESXi host using Server Administrator, restart the VMware ESXi 4 host system. Enabling CIM OEM Providers Using vMA (for VMware ESXi 4.0) 1 Log on to the vMA as an administrator and provide the password when prompted.
Configuring Your System to Send Traps to a Management Station Using the vSphere CLI 1 Install the VMware vSphere CLI. 2 Open a command prompt on the system in which the vSphere CLI is installed. 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.
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.
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
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\usernam
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 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: http://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
Glossary The following list defines technical terms, abbreviations, and acronyms used in your system documents. attribute As it relates to an attribute is a piece of information related to a component. Attributes can be combined to form groups. If an attribute is defined as read-write, it may be defined by a management application. beep code A diagnostic message in the form of a pattern of beeps from your system's speaker.
press . Use this bootable diskette if your system will not boot from the hard drive. bus An information pathway between the components of a system. Your system contains an expansion bus that allows the microprocessor to communicate with controllers for all the various peripheral devices connected to the system. Your system also contains an address bus and a data bus for communications between the microprocessor and RAM. CA Abbreviation for certification authority.
control panel The part of the system that contains indicators and controls, such as the power switch, hard drive access indicator, and power indicator. device driver A program that allows the operating system or some other program to interface correctly with a peripheral device, such as a printer. Some device drivers—such as network drivers—must be loaded from the config.sys file (with a device= statement) or as memory-resident programs (usually, from the autoexec.bat file).
DRAM Acronym for dynamic random-access memory. A system's RAM is usually made up entirely of DRAM chips. Because DRAM chips cannot store an electrical charge indefinitely, your system continually refreshes each DRAM chip in the system. ERA Abbreviation for embedded remote access. ERA/MC Abbreviation for embedded remote access modular computer. See modular system. ERA/O Abbreviation for embedded remote access option.
Fibre Channel A data transfer interface technology that allows for high-speed I/O and networking functionality in a single connectivity technology. The Fibre Channel Standard supports several topologies, including Fibre Channel Point-to-Point, Fibre Channel Fabric (generic switching topology), and Fibre Channel Arbitrated Loop (FC_AL). firmware Software (programs or data) that has been written onto read-only memory (ROM). Firmware can boot and operate a device.
h Abbreviation for hexadecimal. A base-16 numbering system, often used in programming to identify addresses in the system's RAM and I/O memory addresses for devices. The sequence of decimal numbers from 0 through 16, for example, is expressed in hexadecimal notation as: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, A, B, C, D, E, F, 10. In text, hexadecimal numbers are often followed by h. HBA Abbreviation for host bus adapter.
IDE Abbreviation for Integrated Drive Electronics. IDE is a computer system interface, used primarily for hard drives and CDs. I/O Abbreviation for input/output. The keyboard is an input device, and a printer is an output device. In general, I/O activity can be differentiated from computational activity. For example, when a program sends a document to the printer, it is engaging in output activity; when the program sorts a list of terms, it is engaging in computational activity.
ITE Abbreviation for information technology equipment. Java A cross-platform programming language developed by Sun Microsystems. JSSE Abbreviation for Java Secure Socket Extension. K Abbreviation for kilo-, indicating 1000. Kerberos A network authentication protocol. It is designed to provide strong authentication for client/server applications by using secret-key cryptography. key combination A command requiring you to press multiple keys at the same time.
managed system A managed system is any system that is monitored and managed using Dell OpenManage™ Server Administrator. Systems running Server Administrator can be managed locally or remotely through a supported Web browser. See remote management system. management station A system used to remotely manage one or more managed systems from a central location. math coprocessor See coprocessor. Mb Abbreviation for megabit. MB Abbreviation for megabyte(s).
mm Abbreviation for millimeter(s). MMC Abbreviation for Microsoft Management Console. modular system A system that can include multiple server modules. Each server module functions as an individual system. To function as a system, a server module is inserted into a chassis which includes power supplies, fans, a system management module, and at least one network switch module.
NIS Abbreviation for Network Information Services. NIS is a network naming and administration system for smaller networks. A user at any host can get access to files or applications on any host in the network with a single user identification and password. noninterlaced A technique for decreasing screen flicker by sequentially refreshing each horizontal line on the screen. ns Abbreviation for nanosecond(s), one billionth of a second.
parallel port An I/O port used most often to connect a parallel printer to your system. You can usually identify a parallel port on your system by its 25-hole connector. parameter A value or option that you specify to a program. A parameter is sometimes called a switch or an argument. partition You can divide a hard drive into multiple physical sections called partitions with the fdisk command. Each partition can contain multiple logical drives.
physical memory array mapped The physical memory array mapped refers to the way physical memory is divided. For example, one mapped area may have 640 KB and the other mapped area may have between 1 MB and 127 MB. pixel A single point on a video display. Pixels are arranged in rows and columns to create an image. A video resolution, such as 640 x 480, is expressed as the number of pixels across by the number of pixels up and down.
• Multitasking • Virtual memory, a method for increasing addressable memory by using the hard drive provider A provider is an extension of a CIM schema that communicates with managed objects and accesses data and event notifications from a variety of sources. Providers forward this information to the CIM Object Manager for integration and interpretation. RAC Acronym for remote access controller. RAID Acronym for redundant array of independent drives. RAM Acronym for random-access memory.
known problems or other things you need to be aware of as you use the software or hardware. real mode An operating mode supported by 80286 or higher microprocessors, real mode imitates the architecture of an 8086 microprocessor. refresh rate The rate at which the monitor redraws the video image on the monitor screen. More precisely, the refresh rate is the frequency, measured in Hz, at which the screen's horizontal lines are recharged (sometimes also referred to as its vertical frequency).
managed objects that are common to every management environment, which is why CIM is called the Common Information Model. SCSI Acronym for small computer system interface. An I/O bus interface with faster data transmission rates than standard ports. You can connect up to seven devices (15 for some newer SCSI types) to one SCSI interface. SEL Acronym for system event log. sec Abbreviation for second(s).
service tag number A bar code label that identifies each system in the event that you need to call for customer or technical support. shadowing A computer's system and video BIOS code is usually stored on ROM chips. Shadowing refers to the performance-enhancement technique that copies BIOS code to faster RAM chips in the upper memory area (above 640 KB) during the boot routine. SIMM Acronym for single in-line memory module. A small circuit board containing DRAM chips that connects to the system board.
SVGA Abbreviation for super video graphics array. VGA and SVGA are video standards for video adapters with greater resolution and color display capabilities than previous standards. To display a program at a specific resolution, you must install the appropriate video drivers and your monitor must support the resolution. Similarly, the number of colors that a program can display depends on the capabilities of the monitor, the video driver, and the amount of video memory installed in the system.
System Setup program A BIOS-based program that allows you to configure your system's hardware and customize the system's operation by setting such features as password protection and energy management. Some options in the System Setup program require that you reboot the system (or the system may reboot automatically) in order to make a hardware configuration change. Because the System Setup program is stored in NVRAM, any settings remain in effect until you change them again. system.
TFTP Abbreviation for Trivial File Transfer Protocol. TFTP is a version of the TCP/IP FTP protocol that has no directory or password capability. text mode A video mode that can be defined as x columns by y rows of characters. threshold values Systems are normally equipped with various sensors that monitor temperature, voltage, current, and fan speed.
TSOP Abbreviation for thin small outline package. A very thin, plastic, rectangular surface mount chip package with gull-wing pins on its two short sides. UDP Abbreviation for user datagram protocol. UMB Abbreviation for upper memory blocks. unicode A fixed width, 16-bit world wide character encoding, developed and maintained by the Unicode Consortium. upper memory area The 384 KB of RAM located between 640 KB and 1MB.
the formula for specifying a unique identifier for the objects defined in that enterprise's MIB. variable A component of a managed object. A temperature probe, for example, has a variable to describe its capabilities, its health or status, and certain indexes that you can use to help you in locating the right temperature probe. VGA Abbreviation for video graphics array. VGA and SVGA are video standards for video adapters with greater resolution and color display capabilities than previous standards.
package may include some "generic" video drivers. Any additional video drivers may need to match the video adapter installed in the system. video memory Most VGA and SVGA video adapters include memory chips in addition to your system's RAM. The amount of video memory installed primarily influences the number of colors that a program can display (with the appropriate video drivers and monitor capabilities). video mode Video adapters normally support multiple text and graphics display modes.
VNC Acronym for Virtual Network Computing. In a VNC system, servers provide applications, data, and the desktop environment, all of which may be accessed through the Internet. VRAM Acronym for video random-access memory. Some video adapters use VRAM chips (or a combination of VRAM and DRAM) to improve video performance. VRAM is dual-ported, allowing the video adapter to update the screen and receive new image data at the same time. W Abbreviation for watt(s).
Windows NT High-performance server and workstation operating system software developed by Microsoft that is intended for technical, engineering, and financial applications. WinRM WinRM (Windows remote management) is the Microsoft implementation of the WS-Management protocol built in the operating system. write-protected Read-only files are said to be write-protected. You can write-protect a 3.
Glossary
Index A attribute, 163 access read-only, 20 write, 20 authentication, 19, 22, 116 access control, 20 Active Directory, 19-20, 22, 30, 116, 122, 129, 134 object identifiers, 115 objects, 117 schema, 123 schema extender utility, 123-124 schema extensions, 115 ADDLOCAL, 75 administrator, 20 Administrator Pack, 129 authorization, 116 B batch script, 72 baud rate, 163 beep code, 163 binary, 163 BIOS, 14 bootable diskette, 163 bpi, 164 BTU, 164 Administrator privileges, 20 agent, 38 SNMP, 30 C AGP, 163
Citrix, 64 dependency check, 104 CLI, 16, 22, 75, 141 distribution software, 79 cm, 164 command line, 75 DKS, 86-87 prerequisites, 87 command line interface, 16, 22 DRAC, 131, 134 Common Information Model, 16, 27 DRAC 4, 151 configuration, 38 controller ERA/MC, 17 CRC, 165 CSR, 165 cursor, 165 DRAC 5 controller, 17 E encryption, 20 ERA ERA/MC, 17 express setup, 27 D DAT, 165 data redundancy, 14 F firewall, 19, 38 dB, 165 Dell, 53, 115 Dell base OID, 115 Dell organizational unit, 123 Dell Remo
HTTPS, 22 management object format, 16 management objects, 16 I INI file, 68 management station, 27, 34 MIB, 16, 35 installation unattended, 70 Microsoft Active Directory, 19-20, 22, 30, 129 Software Installer, 68 Instrumentation, 21 MMC, 131-132 instrumentation service, 151 MOF, 16 ISV, 71, 79 monitoring, 12 IT Assistant, 120, 141 MSI, 68, 144-145 inoperable system, 17 msiexec.exe, 60, 64, 70, 72 J Java Secure Socket Extension, 22 N notification, 12 JSSE, 22 L O oem.
installing WinRM, 55 requirements, 55 Pluggable Authentication Modules, 22 ports, 141 remote system, 71 power user, 20 REMOVE, 75 Prerequisite Checker, 61, 137, 145-146 restoration, 68 privilege object, 133 privileges group, 20 role-based access control, 20 authority, 19 RPM, 85, 93, 148 prodname, 134 product object, 116 protocol systems management, 27 S SAS, 14 SATA, 14 schema, 115, 123-124 R RAC, 27, 123, 131-132 devices, 116 installation, 27 software, 27 SchemaExtenderOem.
express, 27 Simple Network Management Protocol, 16, 27 tools ISV, 71 training, 17 snap-in, 129 SNMP, 16, 27, 30-31 agent, 30 agent configuration, 36 agent configuration file, 38 community name, 32, 36 net-snmp, 90 packets, 31 port, 38 services, 34 Set operations, 33, 37 traps, 34 ucd-snmp, 90 socket connection, 22 U unattended installation, 70 unattended uninstallation, 79 universal groups, 133 update packages, 17 user, 20 user ID, 19 user levels, 21 utilities schema extender utility, 123-124 SSL, 22, 1
X X.
