Dell™ OpenManage™ Version 5.4 Installation and Security User’s Guide w w w. d e l l . c o m | s u p p o r t . d e l l .
Notes and Notices NOTE: A NOTE indicates important information that helps you make better use of your computer. NOTICE: A NOTICE indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. ____________________ Information in this document is subject to change without notice. © 2007 Dell Inc. All rights reserved. Reproduction in any manner whatsoever without the written permission of Dell Inc. is strictly forbidden.
Contents 1 Introduction . Overview . . . . . . . . . . . . . . . . . . . . . . 11 . . . . . . . . . . . . . . . . . . . . . . . . 11 . . . . 11 . . . . . . . . . . . . . 12 Systems Management Software Overview What’s New in Version 5.4 Dell OpenManage Systems Management Software Kit Contents . . . . . . . . . . . . . . . . . . . . . . . 13 . . . . . . . 13 . . . . . . . . . . . . . 14 Dell Systems Management Tools and Documentation DVD . . . . . . . . .
Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 . . . . . . . . . . . . . . . . . . . . . . . . 36 Security Management RBAC Microsoft Active Directory . . . . . . . . . . . . . Authentication Protocols for Linux Operating Systems . . . . . . . . . 3 39 . . . . . . . . . . . . 41 . . . . . . . . . . . . . . . . . . . . 41 Installation Requirements . . . . . . . . . . . . . . . . System Requirements . . . . . . . . . . .
Configuring the SNMP Agent on Systems Running Supported Red Hat Enterprise Linux Operating Systems . . . . . . . . . . . . . . . . . . . . . . . 53 Configuring the SNMP Agent on Systems Running Supported SUSE Linux Enterprise Server Operating Systems . . . . . . . . . . . . . . . . . . . . . . . 59 Secure Port Server and Security Setup . . . . . . . . . . . . . . . . 62 . . . . . . . . . . 64 Setting User and Server Preferences X.509 Certificate Management .
Installing and Upgrading Management Station Software . . . . . . . . . . . . 73 . . . . . . . . . 74 . . . . . . . . . . . . . . . . . 75 Typical and Custom Installations . Custom Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Modify . . . . . . . . . . . . . . . . . . . . . . . 78 Repair . . . . . . . . . . . . . . . . . . . . . . . . 79 Upgrade System Recovery on Failed Installation . . . . . .
Before You Begin Installation Requirements . System Requirements 97 . . . . . . . . . . . . . . . . . . . . . 97 . . . . . . . . . . . . . . . 98 Supported Operating System Versions Supported Systems Management Protocol Standards . . . . . . . . 99 . . . . . . . . . Windows Server 2003 R2 and the R2 IPMI Device Driver . . . . . . . . . . . . . . . . . . . . 99 Digital Certificates . . . . . . . . . . . . . . . . . 100 Installation Procedures . . . . . . . . . . . . . . . . .
Installing Management Station Software in CLI Mode . . . . . . . . . . . . . . . . . . Installing Managed System Software In CLI Mode . . . . . . . . . . . . . . . . . . . . 128 . . . . . . 129 Uninstalling Systems Management Software on Windows Server 2008 . . . . . . . . . . . . . . 8 Installing Managed System Software on Supported Linux Operating Systems . . . . . . . . . . . . . . . . . . . . . . . Overview . Before You Begin 129 131 131 . . . . 132 . . . . . . . . . . . . . . . . . . . .
Using Microsoft Active Directory Controlling Access to Your Network 161 . . . . . 161 . . . . . . . . . . . . . . . . . 161 . . . . . . . . 168 . . . . . . . . . 168 Active Directory Schema Extensions Extending the Active Directory Schema Using the Dell Schema Extender . Active Directory Users and Computers Snap-In . . 176 Adding Users and Privileges to Active Directory . 177 . . . . . . . 183 Configuring Your Systems or Devices 10 Prerequisite Checker . . . . . . . . . . . . . .
Contents
Introduction Overview This guide contains information to help you install Dell™ OpenManage™ software on management stations and their managed systems. A managed system is a system that has supported instrumentation or agents installed that allow the system to be discovered and polled for status. A management station is used to remotely manage one or more managed systems from a central location.
Each system managed by the Dell OpenManage systems management software is called a managed system. You can manage a managed system either locally or remotely. Software applications that you can install on the managed systems include Dell OpenManage Server Administrator (which includes the Storage Management Service, and the Server Administrator Web server), SNMP agents for Intel® or Broadcom® network interface cards (NICs), and remote access controller (RAC) software.
• Added support for SUSE® Linux Enterprise Server 9 with SP4 (x86_64). • Added support for Microsoft® Windows Server® 2008 (x86) Web, Standard, and Enterprise editions NOTE: Microsoft Windows Server 2008 is scheduled to be available in the first half of 2008. For the latest information, see http://www.microsoft.com/windowsserver2008/default.mspx.
The Dell Systems Management Tools and Documentation DVD is a bootable DVD and its contents are as follows: • Dell Systems Build and Update Utility: When you boot your system from the Dell Systems Management Tools and Documentation DVD, the Dell Systems Build and Update Utility launches and allows you to install an operating system, configure your managed systems, and discover and configure Dell-provided RAID controllers and network adapters.
Dell OpenManage Systems Management Software Components Deployment Software For managed systems, Dell Systems Build and Update Utility provides streamlined operating system installation, reducing the time required for the installation of Windows, Red Hat Enterprise Linux, and SUSE Linux Enterprise Server operating systems by guiding you through an easy-to-follow, step-by-step process.
• View a graphical presentation of the devices in your network, from which you can launch applications, refresh inventory and status, and perform troubleshooting • Launch the following Dell systems management applications: Server Administrator, Remote Access Controller console, Dell PowerConnect™, Digital keyboard/video/mouse (KVM) console, printers, tapes, storage devices, Intelligent Platform Management Interface (IPMI) devices, and client systems.
Baseboard Management Controller (BMC) Management Utility The BMC Management Utility provides a command line based remote management application to manage all supported BMC functions. Use the BMC Management Utility to manage a BMC from a remote management station, and as a managed system's emergency management console.
Managed System Software Server Administrator Server Administrator provides a comprehensive, one-to-one systems management solution using an integrated Web browser-based GUI or a command line interface (CLI) feature.
The Storage Management Service provides the following features: • Enables you to view the status of local and remote storage attached to a monitored system • Supports SAS, SCSI, SATA, and ATA, but does not support Fibre Channel • Allows you to perform controller and enclosure functions for all supported RAID and non-RAID controllers and enclosures from a single graphical interface or a CLI, without the use of the controller BIOS utilities • Protects your data by configuring data redundancy, assigning
Other Documents You Might Need Besides this guide, you can find the following guides either on the Dell Support website at support.dell.com or on the Dell Systems Management Tools and Documentation DVD: 20 • The Dell Systems Build and Update Utility Quick Reference Guide provides information on using the Build and Update tool.
• The Dell OpenManage Server Administrator Command Line Interface User's Guide documents the complete command line interface for Server Administrator, including an explanation of CLI commands to view system status, access logs, create reports, configure various component parameters, and set critical thresholds. • The Dell OpenManage IT Assistant User’s Guide has information about installing, configuring, and using IT Assistant.
• The Dell Update Packages User's Guide provides information about obtaining and using Dell Update Packages as part of your system update strategy. • The Dell OpenManage Server Update Utility User's Guide provides information on using the Dell OpenManage Server Update Utility. • The Dell Systems Software Support Matrix provides information about the various Dell systems, the operating systems supported by these systems, and the Dell OpenManage components that can be installed on these systems.
Introduction 23
Introduction
Dell OpenManage Security Security Features The 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.
Table 2-1. Port # Dell OpenManage UDP/TCP Ports Default Locations Protocol Port Type Version Maximum Direction Usage Encryption Level Configurable Dell OpenManage Baseboard Management Controller - PowerEdge™ x8xx systems 623 RMCP UDP Power Edge x8xx None In/Out IPMI access No through LAN systems only Dell OpenManage Baseboard Management Utility 623 Telnet TCP 1.x None In/Out Accepts incoming Yes Telnet connections 623 RMCP UDP 1.
Table 2-1. Port # Dell OpenManage UDP/TCP Ports Default Locations (continued) Protocol Port Type Version Maximum Direction Usage Encryption Level Configurable Dell OpenManage Client Instrumentation 20 HTTP and TCP FTP 7.x None In/Out Flash BIOS communication No 21 HTTP and TCP FTP 7.x None In/Out Flash BIOS communication No 80 HTTP and TCP FTP 7.x None In/Out Flash BIOS communication No 135 DCOM TCP/ UDP 7.
Table 2-1. Port # Dell OpenManage UDP/TCP Ports Default Locations (continued) Protocol Port Type Version Maximum Direction Usage Encryption Level Configurable Dell OpenManage IT Assistant 22 SSH TCP 7.x 128-bit In/Out IT Assistant contextual application launch—SSH client Yes Remote software updates to Server Administrator— for systems supporting Linux operating systems Performance monitoring in Linux systems 23 Telnet TCP 7.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Type Version Maximum Direction Usage Encryption Level Configurable 135 RPC TCP 7.x None In/Out Event reception No through CIM from Server Administrator— for systems supporting Windows® operating systems 135 RPC TCP/ UDP 7.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol 2606 Proprietary TCP 7.x None In/Out Network Yes monitoring service communication port 2607 HTTPS TCP 7.x 128-bit SSL In/Out IT Assistant Web Yes GUI 3389 RDP TCP 7.x 128-bit SSL In/Out IT Assistant Yes contextual application launch—Remote desktop to Windows terminal services 443 Proprietary TCP 8.0 None In/Out EMC Storage discovery and inventory No 623 RMCP UDP 8.
Table 2-1. Port # Dell OpenManage UDP/TCP Ports Default Locations (continued) Protocol Port Type Version Maximum Direction Usage Encryption Level Configurable Dell OpenManage Server Administrator 22 SSH TCP 2.0 128-bit In/Out Remote Server Yes Administrator Command Line (for IT Assistant). Remote Software Update feature (for Linux operating systems). 25 SMTP TCP 2.0 None In/Out Optional e-mail alert messages from Server Administrator 135 RPC TCP/ UDP 2.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Type Version Maximum Direction Usage Encryption Level Configurable 161 SNMP UDP 1.x, 2.0 None In/Out SNMP query management No 162 SNMP UDP 1.x, 2.0 None Out SNMP trap event No 445 NetBIOS TCP 2.0 None In/Out Remote software No updates to Server Administrator (for Windows operating systems) 1311 HTTPS TCP 1.x 128-bit SSL In/Out Web GUI 11487 Proprietary UDP 1.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Type Version Maximum Direction Usage Encryption Level Configurable 69 TFTP UDP 1.0 None In/Out Firmware update through Trivial FTP. Remote floppy boot through TFTP No 80 HTTP TCP 1.0 None In/Out Web GUI redirected to HTTPS No 162 SNMP UDP 1.0 None Out SNMP trap event No 443 HTTPS TCP 1.0 128-bit SSL In/Out Web management No GUI 443 HTTPS TCP 3.
Table 2-1. Port # Dell OpenManage UDP/TCP Ports Default Locations (continued) Protocol Port Type Version Maximum Direction Usage Encryption Level Configurable Yes DRAC 4 22 SSHv2 TCP 1.30 128-bit In/Out Optional Secure Shell (SSH) CLI management 23 Telnet TCP 1.0 None In/Out Optional Telnet Yes CLI management 25 SMTP TCP 1.0 None In/Out Optional e-mail alert messages 53 DNS UDP 1.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Type Version Maximum Direction Usage Encryption Level Configurable 636 LDAPS TCP 1.0 128-bit SSL In/Out Optional Active No Directory Services (ADS) authentication 3269 LDAPS TCP 1.0 128-bit SSL In/Out Optional ADS authentication No 3668 Proprietary TCP 1.0 None In/Out CD/diskette virtual media service Yes 5869 Proprietary TCP 1.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Type Version Maximum Direction Usage Encryption Level Configurable 80 HTTP TCP 1.0 None In/Out Web GUI redirected to HTTPS Yes 161 SNMP UDP 1.0 None In/Out SNMP query management No 162 SNMP UDP 1.0 None Out SNMP trap event No 389 LDAP TCP 1.0 None In/Out Optional ADS authentication 443 HTTPS TCP 1.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Type Version Maximum Direction Usage Encryption Level Configurable 69 TFTP UDP 1.0 None In/Out Firmware update through Trivial FTP No 80 HTTP TCP 1.0 None In/Out Web GUI redirected to HTTPS Yes 161 SNMP UDP 1.0 None In/Out SNMP query management No 162 SNMP UDP 1.0 None Out SNMP trap event No 443 HTTPS TCP 1.
Table 2-1. Port # Dell OpenManage UDP/TCP Ports Default Locations (continued) Protocol Port Type Version Maximum Direction Usage Encryption Level Configurable Digital KVM 2068 Proprietary TCP 1.0 128-bit SSL In/Out Video Redirection — Keyboard/Mouse No 3668 Proprietary TCP 1.0 None In/Out Virtual Media No 8192 Proprietary TCP 1.0 None In/Out Video redirection to client viewer No NOTE: CIM ports are dynamic. See the Microsoft knowledge base at support.microsoft.
Power Users can set warning threshold values and configure which alert actions are to be taken when a warning or failure event occurs. Administrators can configure and perform shutdown actions, configure Auto Recovery actions in case a system has a non-responsive operating system, and clear hardware, event, and command logs. Administrators can configure alert actions, including sending e-mail messages when an alert is generated.
Privilege Levels to Access Server Administrator Services Table 2-3 summarizes which user levels have privileges to access and manage Server Administrator Services. Table 2-3. Server Administrator User Privilege Levels Service User Privilege Level Required View Manage Instrumentation U, P, A P, A Remote Access U, P, A A Update U, P, A A Storage Management U, P, A A Table 2-4 defines the user privilege level abbreviations used in Table 2-3. Table 2-4.
Red Hat Enterprise Linux and SUSE Linux Enterprise Server Authentication For supported Red Hat® Enterprise Linux® and SUSE® Linux Enterprise Server operating systems, Server Administrator authentication is based on the Pluggable Authentication Modules (PAM) library. This documented library of functions allows an administrator to determine how individual applications authenticate users.
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 Dell™ OpenManage™ Server Administrator Compatibility Guide. This document contains compatibility information about Dell OpenManage software installation and operation on various hardware platforms (systems) running supported Microsoft® Windows®, Red Hat® Enterprise Linux®, and SUSE® Linux Enterprise Server operating systems.
• Windows Server 2003 x64 SP2 (Standard, Enterprise, and DataCenter Editions) • Windows Server 2003 R2 Gold and SP2 (Standard and Enterprise editions) • Windows Server 2003 R2 x64 Gold and SP2 (Standard, Enterprise, and DataCenter Editions) • Windows SBS 2003 R2 (Standard and Premium editions) NOTE: IT Assistant is not supported on systems running Microsoft Windows Server 2003 x64 and Windows SBS 2003 R2.
System Requirements Dell OpenManage Server Administrator software must be installed on each system to be managed. You can then manage each system running Server Administrator locally or remotely through a supported Web browser.
Remote Management System Requirements • One of the supported Web browsers to manage a system remotely from a graphical user interface (GUI) • A TCP/IP connection on the managed system and the remote system to facilitate remote system management • A minimum screen resolution of 800 x 600. The recommended screen resolution setting is 1024 x 768 Minimum Supported Web Browser Requirements • Internet Explorer version 7.
Table 3-1 shows the availability of the systems management standards for each supported operating system. 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 Enterprise You must install the SNMP package Linux operating systems. provided with the operating system.
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. Assigning User Privileges To ensure critical system component security, you must properly assign user privileges to all Dell OpenManage software users before installing the Dell OpenManage software.
5 Double-click the icon representing the user that you just created. 6 Click the Member of tab. 7 Click Add. 8 Select the appropriate group and click Add. 9 Click OK, and then click OK again. New users can log into the Dell OpenManage software with the user privileges for their assigned group and domain. Creating Users for Supported Red Hat Enterprise Linux and SUSE Linux Enterprise Server Operating Systems Administrator access privileges are assigned to the user logged in as root.
Creating Users With Power User Privileges 1 Run the following command from the command line: useradd -d home-directory -g root username NOTE: You must set root as the primary group. 2 Type passwd username and press . 3 When prompted, enter a password for the new user. NOTICE: You must assign a password to every user account that can access Dell OpenManage software to protect access to your critical system components.
NOTE: The default SNMP agent configuration usually includes an SNMP community name such as public. For security reasons, change the default SNMP community names. For information about changing SNMP community names, see 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.
Configuring the SNMP Agent for Systems Running Supported Windows Operating Systems The Dell OpenManage software uses the SNMP services provided by the Windows SNMP agent. SNMP is one of the two supported ways of connecting to a System Administrator session; the other is CIM/WMI. You can configure the SNMP agent to change the community name, enable Set operations, and send traps to a management station.
Changing the SNMP Community Name Configuring the SNMP community names determines which systems are able to manage your system through SNMP. The SNMP community name used by management station applications must match the SNMP community name configured on the Dell OpenManage software system so that the management applications can retrieve systems management information from the Dell OpenManage software. 1 Open the Computer Management window. 2 Expand the Computer Management icon in the window, if necessary.
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. NOTE: Rebooting your system for change management functionality does not require SNMP Set operations. 1 Open the Computer Management window. 2 Expand the Computer Management icon in the window, if necessary.
5 Click the Traps tab to add a community for traps or to add a trap destination for a trap community. a To add a community for traps, type the community name in the Community Name box and click Add to list, which is located next to the Community Name box. b To add a trap destination for a trap community, select the community name from the Community Name drop-down box and click Add under the Trap Destinations box. The SNMP Service Configuration window appears. c Type the trap destination and click Add.
Server Administrator SNMP Agent Install Actions If Server Administrator detects the default SNMP configuration during installation, it attempts to modify the SNMP agent configuration to give read-only access to the entire MIB tree for the public community. Server Administrator modifies the /etc/snmp/snmpd.conf SNMP agent configuration file in two ways. The first change is to create a view to the entire MIB tree by adding the following line if it does not exist: view all included .
Changing the SNMP Community Name Configuring the SNMP community names determines which systems are able to manage your system through SNMP. The SNMP community name used by systems management applications must match an SNMP community name configured on the Server Administrator software system, so the systems management applications can retrieve management information from Server Administrator.
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. To enable SNMP Set operations on the system running Server Administrator, edit the /etc/snmp/snmpd.
To configure your system running Server Administrator to send traps to a management station, edit the /etc/snmp/snmpd.
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. If you are using the X Windows GUI, pressing may not provide information about firewall security levels on newer versions of the Red Hat Enterprise Linux operating system. a To disable the firewall, select No firewall or Disabled and go to step 7.
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.
Using Systems Build and Update Tools to Install an Operating System Overview The Dell™ Systems Build and Update Utility provides a streamlined and time-saving installation procedure by guiding you through an easy-to-follow, step-by-step process for installing the Microsoft® Windows®, Red Hat® Enterprise Linux®, and SUSE® Linux Enterprise Server operating systems. Systems Build and Update Utility is used to install operating systems for systems being installed as managed systems.
Before You Begin Installation Requirements The following sections describe the managed system general requirements. Operating system-specific installation prerequisites are listed as part of the installation procedures.
Installing Your Operating System Perform the following steps to determine if an operating system has been installed on your system: 1 Ensure that the keyboard, mouse, and monitor are connected to your system, and turn on your system. 2 Read and accept the software license agreement to continue. If a message stating that bootable drives do not exist or that an operating system was not found appears, then an operating system has not been installed on your system.
If you do not want to install Server Administrator, or you want to remove the installation files, you can click the Delete Server Administrator Installation Files icon. After you confirm that you want to continue, all Server Administrator files, including the icons, are removed. NOTE: The Install Server Administrator and Delete Server Administrator Installation Files icons will not be available on Microsoft Windows Server 2008 and SUSE Linux Enterprise Server operating systems.
Installing Management Station Software Overview The Dell Systems Management Tools and Documentation DVD provides a setup program to install, upgrade, and uninstall Dell OpenManage™ management station software on your system. Using the setup program you can install and upgrade the management station software on systems running Microsoft® Windows® operating systems.
Installation Requirements These are general requirements for management stations. Operating systemspecific installation prerequisites are listed below as part of the installation procedures for the respective applications.
• Red Hat Enterprise Linux AS, ES, and WS, (version 4.5) x86 and x86_64, (BMC management utility and DRAC Tools) • Red Hat Enterprise Linux Server (version 5) x86 and x86_64, (BMC management utility and DRAC Tools) • SUSE Linux Enterprise Server (version 9), SP4, x86_64 (BMC management utility and RAC Management Station) • SUSE Linux Enterprise Server (version 10) Gold x86_64 NOTE: The Dell OpenManage 5.
Microsoft SQL Server 2000 Desktop Engine (MSDE 2000), if it is already installed on your system. If you are upgrading from IT Assistant 7.x to 8.x or greater, you can use the existing MSDE 2000. Enabling CIM Discovery and Security in IT Assistant IT Assistant uses the Common Information Model (CIM) protocol. If you use the CIM protocol, ensure that it is installed and enabled. For detailed information on configuring CIM for IT Assistant, see the Dell OpenManage IT Assistant User’s Guide.
The Prerequisite Checker displays three types of messages: informational, warning, and error messages. • An informational message describes a condition, but does not prevent a feature from being installed. • A warning message describes a condition that prevents a software feature from being installed during Typical installation. It is recommended that you resolve the condition causing the warning before proceeding with the installation of the software.
Typical and Custom Installations The management station installer provides two setup options: Typical Setup and Custom Setup. The setup program runs the Prerequisite Checker and provides information about your system’s hardware and software that might affect installation and operation of features. Perform the following steps to install management station software on your system: 1 Launch the management station installation. 2 Click Install, Modify, Repair or Remove Management Station and click Next.
Custom Installation The custom installation path enables you to choose specific software features to install. NOTE: You can install management station and managed system services in the same or different directories. You can select the directory for installation. Installing Management Station On Microsoft Windows operating systems, an autorun utility appears when you insert the Dell Systems Management Tools and Documentation DVD in your system’s DVD drive.
6 Click Next. The Dell Software License Agreement appears. 7 Click Accept if you agree. The Setup Type dialog box appears. 8 Select Custom and click Next. The Custom Setup dialog box appears. To select a specific management station software application, click the drop-down arrow beside the listed feature and select to either install or not to install the application. A selected feature has a hard drive icon next to it. A deselected feature has a red X next to it.
Upgrade The Dell OpenManage installer provides an Upgrade option for upgrading IT Assistant and other management station software. When you insert the Dell Systems Management Tools and Documentation DVD into your system's DVD drive, select Dell OpenManage Management Station from the autorun menu, and click Install. The Prerequisite Checker program checks your system.
Upgrade Using the Windows Installer Patch File You can upgrade your management station software using the Windows Installer Patch (.MSP) file. The MSP file is available on the Dell Support website at support.dell.com. To apply the MSP file, either double-click on the MSP file or type the following command in your command-prompt window: msiexec.exe /p filename.msp NOTE: You can use other msiexec parameters like "/q" for silent upgrades. Modify 1 Navigate to the Windows Control Panel.
Repair 1 Navigate to the Windows Control Panel. 2 Double-click Add/Remove Programs. 3 Click Dell OpenManage Management Station and click Change. The Welcome to the Install Wizard for Dell OpenManage Management Station dialog box appears. 4 Click Next. The Program Maintenance dialog box appears. 5 Select the Repair option and click Next. The Ready to Repair the Program dialog box appears. 6 Click Install to install the selected software features.
An installation cannot be rolled back once it has successfully completed. A transacted installation is intended as a safety net that protects the system during a given installation session. If you want to remove an installed application, for example, you should uninstall that application. When upgrading from Dell OpenManage software version 4.3 to version 5.x, an error will roll back the system to its previous state.
Creating and Distributing the Typical Unattended Installation Package The Typical Setup unattended installation option uses the Dell Systems Management Tools and Documentation DVD as the unattended installation package. The msiexec.exe /i MgmtSt.msi /qb command accesses the DVD to accept the software license agreement and install all required management station software products on selected remote systems. The msiexec.exe /i MgmtSt.
3 Configure your ISV distribution software to distribute and execute the script created in step 2. 4 Distribute this script to the target systems by using your ISV software distribution tools. The msiexec.exe /i MgmtSt.msi /qb command installs management station on each remote system. NOTE: IT Assistant requires a supported database to be installed before IT Assistant can be installed. See DVD drive:\SYSMGMT\ManagementStation\Windows\ManagementStat ion\support\ to find the sample batch file and the necessar
Distributing Custom Unattended Installation Packages NOTE: The MgmtSt.msi installation package for management station used in the Custom Setup unattended installation as described in the previous section is located in the SYSMGMT\ManagementStation\windows\ManagementStation on the Dell Systems Management Tools and Documentation DVD. 1 Configure your ISV distribution software to execute the batch script once your installation package has been distributed.
Table 5-1. Command Line Settings for MSI Installer Setting Result Installs or configures a product. /i Administrator software. Uninstalls a product. /x management station software. /q[n|b|r|f] Sets the User Interface (UI) level. /q or /qn – no UI. This option is used for silent and unattended installation. /qb – basic UI.
Table 5-1. Command Line Settings for MSI Installer (continued) Setting Result /f[p|o|e|d|c|a|u Repairs a product. |m|s|v] /fp – This option reinstalls a product only if a file is 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.
An example command with MSI is msiexec.exe /i MgmtSt.msi /qn. This command installs management station features on each remote system, based on the systems’ hardware and software configuration, silently and without asking for prompts. Uninstalling Management Station Software You can uninstall the management station software by using the Dell Systems Management Tools and Documentation DVD, or your operating system. Additionally, you can perform unattended uninstallations on multiple systems.
5 Click Remove. The Uninstalling Dell OpenManage Management Station screen appears. Messages provide 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 management station uninstallation. All management station features will be uninstalled.
Distributing the Unattended Uninstallation Package The Dell Systems Management Tools and Documentation DVD is preconfigured to act as the unattended uninstallation package. To distribute the package to one or more systems, perform the following steps: 1 Configure your ISV distribution software to execute the msiexec.exe /x DVD Drive\SYSMGMT\ManagementStation\windows\Managemen tStation\MgmtSt.msi /qb command after the unattended uninstallation package has been distributed.
Customization Parameters The ADDLOCAL, REINSTALL, and REMOVE CLI parameters provide a way to specify 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.
The REMOVE customization parameter can be included on the command line and assigned the feature ID (or IDs) of the software feature that you would like to uninstall. An example is msiexec.exe /i MgmtSt.msi REMOVE=RACMS /qb This command runs only the installation for management station and uninstalls Remote Access Controller management station, in an unattended and verbose mode. You can also choose to install, reinstall, and uninstall features with one execution of the msiexec.exe program.
Include Ranges. Click New Include Range to run the New Discovery Wizard, where you can specify the new CIM user name in the CIM Configuration window. See the IT Assistant online help for additional information. Other Known Issues for Microsoft Installations • Directories might be left behind during an uninstall for reasons such as sharing violations or open user interface connections. It is recommended that you close all open interface sessions before you perform an uninstallation.
To install the BMC Management Utility onto a management station, perform the following steps: 1 Log on as root to the system on which you want to install the management station features. 2 If necessary, mount the Dell Systems Management Tools and Documentation DVD to a desired location using the mount command or a similar command.
Upgrading Management Station Software To upgrade the BMC Management Utility onto a management station, perform the following steps: 1 Log on as root to the system on which you want to upgrade the management station features. 2 If necessary, mount the Dell Systems Management Tools and Documentation DVD to a desired location using the mount command or a similar command.
Uninstalling Management Station Software To uninstall the BMC Management Utility onto a management station, perform the following steps: 1 Log on as root to the system where you want to install the management station features. 2 Use the rpm query command to determine which version of the BMC Management Utility is installed. Use the rpm -qa | grep osabmcutil command. 3 Verify the package version to be uninstalled and uninstall the feature by using the rpm -e `rpm -qa | grep osabmcutil` command.
Installing Management Station Software 97
Installing Management Station Software
Installing Managed System Software on Microsoft Windows Operating Systems Overview The Dell Systems Management Tools and Documentation DVD provides a setup program to install, upgrade, and uninstall managed system software components on your managed systems. You can install these software components on multiple systems through an unattended installation across a network.
On Microsoft® Windows® operating systems, an autorun utility appears when you insert the Dell Systems Management Tools and Documentation DVD in your system’s DVD drive. The autorun utility allows you to choose the systems management software you want to install on your system. If the autorun program does not start automatically, you can use the setup program in the SYSMGMT\srvadmin\windows directory on the Dell Systems Management Tools and Documentation DVD, to install and upgrade Server Administrator on sy
Installation Requirements The following sections describe the general requirements for Server Administrator.
System Requirements Server Administrator must be installed on each managed system. You can then manage each system running Server Administrator locally or remotely through a supported Web browser. The setup program invokes the Prerequisite Checker on the DVD to determine if the system requirements are met. (For more information see the section titled "Prerequisite Checker.
• The Server Administrator Storage Management Service requires that Dell OpenManage Storage Management be installed on the system in order to be properly managed. See the Dell OpenManage Server Administrator User's Guide for complete software and hardware requirements. • Microsoft Software Installer (MSI) version 3.1 or later NOTE: Dell OpenManage software detects the MSI version on your system. If the version is lower than 3.1, the Prerequisite Checker prompts you to upgrade to MSI version 3.1.
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.
Installation Procedures This section explains how to install, upgrade, and uninstall Server Administrator on a system that is running a supported Windows operating system. Prerequisites for Installing or Upgrading Server Administrator You must have Administrator privileges. 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.
A warning message describes a condition that prevents a software product from being installed during Typical installation. It is recommended that you resolve the condition causing the warning before proceeding with the installation of that software. If you decide to continue, you can select and install the software using the Custom installation.
NOTE: You can upgrade from Dell OpenManage software version 4.3 through 4.5.1 to 5.4 through a full MSI installation only. NOTE: After you install Server Administrator on PowerEdge 1650, 2650, 4600, 700, 750, 800, 830, 850, and 1800 systems, you may be prompted to reboot your system if you have chosen to install the Storage Management Service.
3 Insert the Dell Systems Management Tools and Documentation DVD into your system's DVD drive. The autorun menu appears. 4 Select Dell OpenManage Server Administrator from the autorun menu and click Install. If the autorun program does not start automatically, go to the SYSMGMT\srvadmin\windows directory on the DVD, and run the setup.exe file. The Dell OpenManage Server Administrator prerequisite status screen appears and runs the prerequisite checks for the managed system.
9 Click Next to accept the selected software features for installation. The Ready to Install the Program dialog box appears. NOTE: You can cancel the installation process by clicking Cancel. The installation rolls back the changes that you made. If you click Cancel after a certain point in the installation process, the installation may not roll back properly, leaving the system with an incomplete installation. See "System Recovery on Failed Installation.
Upgrading Managed System Software The Dell OpenManage installer provides an Upgrade option for upgrading Server Administrator and other managed system software. The setup program runs the Prerequisite Checker, which uses your system's PCI bus to search for installed hardware, such as controller cards. The setup program installs or upgrades all of the managed system software features that are appropriate for your particular system's hardware configuration.
4 Click Next. The Installing Dell OpenManage Server Administrator screen appears. Messages are displayed, stating the status and progress of the software features being installed or upgraded. After the selected features are installed or upgraded, the Install Wizard Completed dialog box appears. 5 Click Finish to exit the Server Administrator installation. If you are prompted to reboot your system, you must reboot your system to make the installed managed system software services available for use.
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.
Repair 1 Navigate to the Windows Control Panel. 2 Double-click Add/Remove Programs. 3 Click Dell Server Administrator and click Change. The Welcome to the Install Wizard for Dell OpenManage Server Administrator dialog box appears. 4 Click Next. The Program Maintenance dialog box appears. 5 Select the Repair option and click Next. The Ready to Repair the Program dialog box appears. 6 Click Install to install the selected software features. The Installing Dell OpenManage Server Administrator screen appears.
In addition to the rollback of MSI Standard Actions, the Dell OpenManage library also has the ability to undo commands listed in the INI file for each application if a rollback occurs. All files that are modified by the Dell OpenManage installation actions will be restored to their original state if a rollback occurs. When the MSI engine is going through the installation sequence, it ignores all actions that are scheduled as rollback actions.
The letters in the value field can be in any order. Each letter turns on a different logging mode. Each letter's actual function is as follows for MSI version 3.
NOTE: Dell OpenManage systems management and management station installers require MSI version 3.1 or later. Update the MSI engine if you are using a system running Windows 2000 Server or Windows XP operating system. If you are using a system running Windows Server 2003 SP1 or Windows Server 2003 x64 operating system, you do not have to update the MSI engine. :retry start /wait msiexec /i SysMgmt.
Creating and Distributing the Typical Unattended Installation Package The Typical Setup unattended installation option uses the Dell Systems Management Tools and Documentation DVD as the unattended installation package. The msiexec.exe /i SysMgmt.msi /qb command accesses the DVD to accept the software license agreement and install all required Server Administrator features on selected remote systems. The msiexec.exe /i SysMgmt.
Distributing the Entire DVD as the Typical Unattended Installation Package 1 Distribute the entire image of the Dell Systems Management Tools and Documentation DVD to your target systems. 2 Configure your ISV distribution software to execute the msiexec.exe /i DVD Drive\SYSMGMT\srvadmin\windows\SystemsManagement\ SysMgmt.msi /qb command from the DVD image. The program executes to install Server Administrator on each remote system. 3 Reboot each remote system to enable Server Administrator.
Distributing Custom Unattended Installation Packages NOTE: The SysMgmt.msi installation package for Server Administrator used in the Custom Setup unattended installation (see "Creating and Distributing Custom Unattended Installation Packages") is located in the SYSMGMT\srvadmin\windows\SystemsManagement directory in the DVD. 1 Configure your ISV distribution software to execute the batch script once your installation package has been distributed.
Table 6-1. Command Line Settings for MSI Installer Setting Result /i This command installs or configures a product. software. /i SysMgmt.msi /qn This command carries out a fresh installation of version 5.4. This command also carries out major upgrades from version 4.3 to 5.4. You have to update your MSI engine before running this command if you are using a system running Windows 2000 Server, or Windows XP operating system.
Table 6-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 ADDLOCAL, REINSTALL, and REMOVE CLI parameters in upper case, as they are case-sensitive. ADDLOCAL, 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.
You can include the REINSTALL customization parameter on the command line and assign the feature ID (or IDs) of the software feature that you would like to reinstall. An example is 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.
MSI Return Code An application event log entry is recorded in the SysMgmt.log file. Table 6-3 shows some of the error codes returned by the msiexec.exe Windows Installer Engine. Table 6-3. Windows Installer Return Codes Error Code Value Description ERROR_SUCCESS 0 The action completed successfully. ERROR_INVALID_PARAMETER 87 One of the parameters was invalid. ERROR_INSTALL_USEREXIT 1602 The user canceled the installation.
Uninstalling Managed System Software Using Dell-provided Media 1 Insert the Dell Systems Management Tools and Documentation DVD into your system's DVD drive. If the setup program does not start automatically, run the setup.exe in the SYSMGMT\srvadmin\windows directory on the DVD. The Dell OpenManage Server Administrator prerequisite status screen appears and runs the prerequisite checks for the managed system. Any relevant informational, warning, or error messages detected during checking are displayed.
Uninstalling Managed System Software Features Using the Operating System 1 Navigate to the Windows Control Panel. 2 Double-click Add/Remove Programs. 3 Click Dell OpenManage Server Administrator and click Remove. The Add or Remove Programs dialog box appears. 4 Click Yes to confirm uninstallation of Server Administrator. The Dell OpenManage Server Administrator screen appears and provides the status and progress of the software features being uninstalled.
Distributing the Unattended Uninstallation Package The Dell Systems Management Tools and Documentation DVD is preconfigured to act as the unattended uninstallation package. To distribute the package to one or more systems, perform the following steps: 1 Configure your ISV distribution software to execute the msiexec.exe /x DVD Drive\SYSMGMT\srvadmin\windows\SystemsManagement\ SysMgmt.msi /qb command, if you are using the DVD, after the unattended uninstallation package has been distributed.
Managed System Software Installation Using Third-Party Deployment Software You can use third-party deployment software, such as Altiris Deployment Solution, to install managed systems software onto supported Dell systems. To distribute and install Server Administrator using Altiris, start your Altiris application and import OpenManage_Jobs.bin located at SYSMGMT\srvadmin\support\Altiris on the Dell Systems Management Tools and Documentation DVD. Specify a job folder into which to import OpenManage_Jobs.bin.
Installing Dell OpenManage Software On Microsoft Windows Server 2008 Core Introduction The Server Core installation option of the Microsoft® Windows Server® 2008 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. A Windows Server 2008 Core installation installs only a subset of the binaries that are required by the supported server roles.
On Windows Server 2008 Core, since a GUI is not available, you need run the pre-requisite checker in the CLI mode. • Managed System Software: Type runprereqchecks.exe /s in the command prompt. The file runprereqchecks.exe is located at SYSMGMT\srvadmin\windows\prereqchecker on the Dell Systems Management Tools and Documentation DVD. • Management Station Software: Type runprereqchecks.exe /s in the command prompt. The file runprereqchecks.exe is located at SYSMGMT\ManagementStation\windows\prereqchecker o
Common causes for a return value of 2 from the prerequisite checker on Windows Server 2008 Core: • One of your storage controllers or drivers has outdated firmware or driver. See firmwaredriverversions_.html (where stands for language) or firmwaredriverversions.txt found in the %TEMP% folder. To find %TEMP%, run the echo %TEMP% command. • RAC component software, versions 3 and 4, are not selected for a default install unless the device is detected on the system.
• Running managed system prereqchecker on the Windows Vista® operating system. Vista is not supported for managed system software. • Running the x64 edition of Windows 2008 Core, since some of the components are disabled from being installed. Ensure that any error or warning situation is corrected before you proceed to install OpenManage software components.
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 Dell OpenManage Software on Windows Server 2008 Core
Installing Managed System Software on Supported Linux Operating Systems Overview The Dell™ OpenManage™ installer provides installation scripts and RPM packages to install, upgrade, and uninstall Dell OpenManage Server Administrator and other managed system software components on your managed system. Additionally, you can install Server Administrator on multiple systems through an unattended installation across a network. The first installation method uses the custom install script srvadmininstall.sh.
Unattended and Scripted Silent Installation You can use the Dell Systems Management Tools and Documentation DVD to perform an unattended and scripted silent installation of managed systems software through the command line (using RPM packages) on systems running supported Red Hat® Enterprise Linux® and SUSE® Linux Enterprise Server operating systems. Before You Begin • Read the installation requirements to ensure that your system meets or exceeds the minimum requirements.
• SUSE Linux Enterprise Server (version 9), SP4 x86_64 • SUSE Linux Enterprise Server (version 10) Gold x86_64 NOTE: For the latest detailed list of the Server Administrator services that are supported on each supported operating system, see the Server Administrator readme file on the Dell Systems Management Tools and Documentation DVD. System Requirements Managed systems software must be installed on each system to be managed.
Supported Systems Management Protocol Standards A supported systems management protocol standard must be installed on the managed system before installing Server Administrator. On supported Red Hat Enterprise Linux and SUSE Linux Enterprise Server operating systems, Server Administrator only supports the SNMP systems management standard. You must install the SNMP package provided with the operating system. CIM and WMI are unsupported.
Software License Agreement The software license for the Red Hat Enterprise Linux and SUSE Linux Enterprise Server version of the Dell OpenManage software is located on the Dell Systems Management Tools and Documentation DVD. Read the license.txt 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.
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 (versions 9 and 10), the kernel-source RPM provides the necessary kernel source.
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.
Forcing Dynamic Kernel Support on Red Hat Enterprise Linux Update Releases When Kernel is Tainted Server Administrator provides precompiled device drivers for the "Gold" releases of supported Red Hat Enterprise Linux operating systems. Red Hat Enterprise Linux supports loading device drivers built for the "Gold" release, on the Update releases.
Forcing Dynamic Kernel Support on Red Hat Enterprise Linux Update Releases After the installation of Server Administrator, perform the following steps to force DKS to be used on Red Hat Enterprise Linux Update releases to build device drivers for the running kernel, if needed, so that they do not taint the kernel: 1 Ensure that the prerequisites of DKS are met. 2 Execute the following command: /etc/init.
Blocking During Custom Installation of Server Administrator Using the srvadmininstall.sh Shell Script During custom installation of Server Administrator using the srvadmininstall.sh shell script, the script automatically calls another shell script called srvadmin-openipmi.
Re-attempt to install the srvadmin-hapi RPM and any other RPMs that failed to install as they depend on the srvadmin-hapi RPM. Perform the following steps: 1 Navigate to the SYSMGMT/srvadmin/linux/custom directory. 2 Run the following command to see which Server Administrator packages were previously successfully installed. rpm –qa | grep srvadmin The query displays a list of all installed Server Administrator packages.
Re-attempt to install the srvadmin-hapi RPM and any RPMs that failed to install as they depend on the srvadmin-hapi RPM. Degradation of Functionality When Server Administrator Instrumentation Service is Started After Server Administrator is installed, the Server Administrator Instrumentation Service will do a run-time check of the OpenIPMI device driver whenever it is started. The Server Administrator Instrumentation Service is started whenever you run either the srvadmin-services.
If you are unsure as to whether or not the OpenIPMI device driver on the system is sufficient, run the srvadmin-openipmi.sh status command instead. Rather than attempting to install or upgrade the OpenIPMI device driver, if necessary, which is what the srvadmin-openipmi.sh install command does, the srvadmin-openipmi.sh status command displays information that informs you whether or not the OpenIPMI device driver on the system is sufficient or not. After running the srvadmin-openipmi.
• The ucd-snmp or net-snmp package that is provided with the operating system must be installed if you use SNMP to manage your server. If you want to use supporting agents for the ucd-snmp or net-snmp agent, you must install the operating system support for the SNMP standard before you install Server Administrator. For more information about installing SNMP, see the installation instructions for the operating system you are running on your system.
Installing Managed System Software Using Dell-Provided Media The Dell OpenManage installer uses RPMs to install each component. The media (DVD) is divided into subdirectories to enable easy Custom Installs. 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.
3 If necessary, use the command line to mount the DVD using a command such as: mount /dev/dvdrom /mnt/dvdrom 4 Navigate to the SYSMGMT/srvadmin/linux/supportscripts if you are using the DVD. 5 Run the srvadmin-install.sh shell script as shown below, which performs a silent and unattended express installation. All of the components, including any applicable remote access controller (DRAC III, DRAC 4, or DRAC 5) software components, will be installed. sh srvadmin-install.sh --express or sh srvadmin-install.
Table 8-1.
The following is an example of custom RPMs-based installation of Server Administrator, including the installation of the Storage Management Service components. NOTE: On the Red Hat Enterprise Linux 5 operating system, DVDs are automounted 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.
This utility will run in interactive mode if you do not specify any options, and it will run silently if you provide one or more options. The options are: [-x|--express] installs all components including RAC. Any other options passed will be ignored. [-b|--base] installs Base components. [-s|--storage] installs Storage components, including Base. [-r|--rac] installs applicable RAC components, including Base. [-w|--web] installs Web Server components, including Base.
5 To install the Storage Management Service components, type the following command. sh srvadmin-install.sh --storage (these are long options) or sh srvadmin-install.sh -s (these are short options) NOTE: Long options can be combined with short options, and vice-versa. NOTE: Just before the Server Administrator RPMs are installed, the srvadmin-install.sh shell script automatically calls the srvadmin-openipmi.
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. • If you press , a message states that the RPMs will be installed in the /opt/dell/srvadmin directory. You can then press to change, or press to use the default installation path. When the installation is completed, the script will have an option for starting the services.
The custom unattended installation package is located in the directory you created as detailed in the section "Using the Shell Script to Perform the Custom Installation in Interactive Mode." This directory contains all the RPMs for the managed system software components for distribution. 1 Configure your ISV software distribution software to execute rpm –i *.rpm after the unattended installation package has been distributed.
NOTE: If a required version of the OpenIPMI driver is currently not installed on your remote systems, the srvadmin-hapi RPM fails to install and displays an error message stating that you must install or upgrade the OpenIPMI driver. In such a case, all RPMs that depend on the srvadmin-hapi RPM also fail to install. In such cases, you should also distribute the OpenIPMI-related RPM files in the SYSMGMT/srvadmin/linux/custom//openipmi directory on the DVD, where is RHEL4 or RHEL5 or SLES9 or SLES10.
Upgrading From Previous Versions If your system is running Dell OpenManage software prior to version 4.2, uninstall the current version before attempting to install the new version. Upgrading From Version 4.3 or Later For Dell OpenManage software versions 4.3 and later, you can upgrade your system using RPM commands or the srvadmin-install.sh shell script. Ensure that all installed components are upgraded when you perform either procedure.
If upgrading from 4.x, use a command like the following: rpm -Uhv openipmi/openipmi*.rpm srvadminipmi*.rpm `rpm -q --queryformat "%{NAME}* " \`rpm -qa | grep srvadmin\`` NOTE: The commands upgrade the existing Server Administrator RPM packages on your system. Starting with version 5.0, the openipmi and srvadmin-ipmi packages are new requirements for Server Administrator. The dkms RPM package under the openipmi sub-directory depends on the openipmi package.
If the OpenIPMI driver is currently not installed on the system, or the version of the OpenIPMI driver installed on the system is less than the minimum version that is required by Server Administrator, the srvadmin-hapi RPM will fail to upgrade and will display an error message stating that you must install/upgrade the OpenIPMI driver. In such a case, any RPMs that depend on the srvadminhapi RPM will also fail to upgrade.
the kernel-source RPM and build the OpenIPMI driver. In such a case, any RPMs that depend on the srvadmin-hapi RPM will also fail to upgrade. You must install the kernel-source RPM, and build and install the OpenIPMI driver modules, by performing the following additional steps: 1 On systems running Red Hat Enterprise Linux (version 4) and SUSE Linux Enterprise Server, the kernel*-devel RPMs provide the necessary source for building kernel modules.
cd /media/dvdrom/SYSMGMT/srvadmin/linux/supportscrip ts 4 Run the following script: sh srvadmin-install.sh The script detects any previous version of Server Administrator. If a previous version is installed, a message appears stating the current version and installed components. For example: Server Administrator version 4.4.0 is currently installed.
NOTE: Just before the Server Administrator RPMs are upgraded, the srvadmininstall.sh shell script automatically calls the srvadmin-openipmi.sh shell script to ensure that a sufficient version of the OpenIPMI driver is currently installed on the system. If a sufficient version is not found, the srvadmin-install.sh shell script calls the srvadmin-openipmi.sh shell script to attempt to install a sufficient version.
Using Dell OpenManage with VMware® ESX Server™ Software NOTE: Dell OpenManage installation with VMware ESX Server software requires special steps. These steps vary depending on the Dell OpenManage version and ESX Server version; only a limited number of combinations are supported. See the VMware Systems Compatibility Guide located in the Resource Center at www.dell.com/vmware to determine the versions of ESX Server software compatible with this release of Dell OpenManage.
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 Dell remote access controllers, 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.
Figure 9-2. Setting Up Active Directory Objects in a Single Domain AO1 Group1 User1 User2 AO2 Priv1 User3 Priv2 RAC1 RAC2 To set up the objects for the single domain scenario, perform the following tasks: 1 Create two Association Objects. 2 Create two RAC Product Objects, RAC1 and RAC2, to represent the two DRAC 4 cards. 3 Create two Privilege Objects, Priv1 and Priv2, in which Priv1 has all privileges (Administrator) and Priv2 has Login privileges. 4 Group User1 and User2 into Group1.
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. You want to give User1 and User2 Administrator privileges on both the RAC1 and the RAC2 card and give User3 a Login privilege on the RAC2 card. Figure 9-3.
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. 7 Add User3 as Members in Association Object 2 (AO2), Priv2 as Privilege Objects in AO2, and RAC2 as a Product in AO2. For Server Administrator or IT Assistant, on the other hand, the users in a single Association can be in separate domains without needing to be added to a universal group.
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. 3 Create two Server Administrator Products, sys1 and sys2, to represent the two systems. Sys1 is in Domain1 and sys2 is in Domain2.
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. Extending your Active Directory schema will add schema classes and attributes, example privileges and association objects, and a Dell organizational unit to the schema.
3 Either select Use Current Log In Credentials or enter a user name and password with schema administrator rights. 4 Click Next to run the Dell Schema Extender. 5 Click Finish. To verify the schema extension, use the Active Directory Schema Snap-in in the Microsoft Management Console (MMC) to verify the existence of the following classes (listed in Table 9-1, Table 9-6, Table 9-7, Table 9-9, Table 9-10, Table 9-11, and Table 9-12) and attributes (listed in Table 9-13, Table 9-14, and Table 9-15).
Table 9-2. dellRacDevice Class OID 1.2.840.113556.1.8000.1280.1.1.1.1 Description This class represents the Dell RAC device. The RAC Device must be configured as dellRacDevice in Active Directory. This configuration enables the DRAC 4 to send LDAP queries to Active Directory. Class Type Structural Class SuperClasses dellProduct Attributes dellSchemaVersion dellRacType Table 9-3. dellAssociationObject Class OID 1.2.840.113556.1.8000.1280.1.1.1.
Table 9-4. dellRAC4Privileges Class (continued) OID 1.2.840.113556.1.8000.1280.1.1.1.3 Attributes dellIsLoginUser dellIsCardConfigAdmin dellIsUserConfigAdmin dellIsLogClearAdmin dellIsServerResetUser dellIsConsoleRedirectUser dellIsVirtualMediaUser dellIsTestAlertUser dellIsDebugCommandAdmin Table 9-5. dellPrivileges Class OID 1.2.840.113556.1.8000.1280.1.1.1.4 Description This class is used as a container Class for the Dell Privileges (Authorization Rights).
Table 9-7. dellRAC3Privileges Class OID 1.2.840.113556.1.8000.1280.1.1.1.6 Description This class is used to define the privileges (Authorization Rights) for the DRAC III, DRAC III/XT, ERA, ERA/O, and ERA/MC devices. Class Type Auxiliary Class SuperClasses None Attributes dellIsLoginUser Table 9-8. 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-10. 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-11. dellItaApplication Class OID 1.2.840.113556.1.8000.1280.1.3.1.2 Description This class represents the IT Assistant application.
Table 9-12. 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.
Table 9-13. RAC-specific Attributes Added to the Active Directory Schema (continued) Attribute Name/Description Assigned OID/Syntax Object Identifier Single Valued dellIsServerResetUser 1.2.840.113556.1.8000.1280.1.1.2.7 TRUE TRUE if the User has Server Reset rights on the device. Boolean (LDAPTYPE_BOOLEAN 1.3.6.1.4.1.1466.115.121.1.7) dellIsConsoleRedirectUser 1.2.840.113556.1.8000.1280.1.1.2.8 TRUE if the User has Console Redirection rights on the device. Boolean (LDAPTYPE_BOOLEAN 1.3.6.1.4.
Table 9-14. Server Administrator-Specific Attributes Added to the Active Directory Schema Attribute Name/Description Assigned OID/Syntax Object Identifier Single Valued dellOMSAIsReadOnlyUser 1.2.840.113556.1.8000.1280.1.2.2.1 TRUE TRUE if the User has Read-Only rights Boolean (LDAPTYPE_BOOLEAN in Server Administrator 1.3.6.1.4.1.1466.115.121.1.7) dellOMSAIsReadWriteUser 1.2.840.113556.1.8000.1280.1.2.2.2 TRUE if the User has Read-Write rights in Server Administrator Boolean (LDAPTYPE_BOOLEAN 1.3.
only need to extend the snap-in once, even if you have added more than one schema extension. You must install the snap-in on each system that you intend to use for managing these objects. The Dell Extension to the Active Directory Users and Computers Snap-In is an option that can be installed when you install your systems management software using the Dell Systems Management Tools and Documentation DVD.
Creating a Product Object NOTE: Server Administrator and IT Assistant users must use Universal-type Product Groups to span domains with their product objects. NOTE: When adding Universal-type Product Groups from separate domains, you have to create an Association object with Universal scope. The default Association objects created by the Dell Schema Extender utility are domain Local Groups and will not work with Universal-type Product Groups from other domains.
7 Right-click the privilege object that you created and select Properties. 8 Click the appropriate Privileges tab and select the privileges that you want the user to have (for more information, see Table 9-1 and Table 9-10). Creating an Association Object The Association Object is derived from a Group and must contain a group Type. The Association Scope specifies the Security Group Type for the Association Object.
To add Users or User Groups: 1 Right-click the Association Object and select Properties. 2 Select the Users tab and click Add. 3 Type the User or User Group name or browse to select one and click OK. Click the Privilege Object tab to add the privilege object to the association that defines the user’s or user group’s privileges when authenticating to a system. NOTE: You can add only one Privilege Object to an association object. To add a privilege: 1 Select the Privileges Object tab and click Add.
2 Enable SSL on each of your domain controllers by installing the SSL certificate for each controller. a Click Start→Administrative Tools→Domain Security Policy. b Expand the Public Key Policies folder, right-click Automatic Certificate Request Settings and click Automatic Certificate Request. c In the Automatic Certificate Request Setup Wizard, click Next and select Domain Controller. d Click Next and click Finish.
14 Click Next and save the certificate to a location of your choice. You will need to upload this certificate to the DRAC 4. To do this, go to the DRAC 4 Web-based interface→Configuration tab→Active Directory page. Or, you can use the racadm CLI commands (see "Configuring DRAC 4 and DRAC 5 Active Directory Settings Using the racadm CLI"). 15 Click Finish and click OK.
Importing the DRAC 5 Firmware SSL Certificate to All Domain Controllers’ Trusted Certificate Lists NOTE: If the DRAC 5 firmware SSL certificate is signed by a well-known CA, you do not need to perform the steps described in this section. NOTE: The following steps may vary slightly if you are using Windows 2000. The DRAC 5 SSL certificate is the same certificate that is used for the DRAC 4 Web server. All DRAC 4 controllers are shipped with a default self-signed certificate.
Configuring Active Directory Using CLI on Systems Running Server Administrator You can use the omconfig preferences dirservice command to configure the Active Directory service. The productoem.ini file is modified to reflect these changes. If the adproductname is not present in the productoem.ini file, a default name will be assigned.
productname=IT Assistant startmenu=Dell OpenManage Applications autdbid=ita accessmask=3 startlink=ITAUIServlet adsupport=true adproductname=mgmtStationITA NOTE: Restart the IT Assistant services after saving the itaoem.ini file to the disk. Configuring the DRAC 4 Using the Web-Based Interface 1 Log in to the Web-based interface using the default user, root, and its password. 2 Click the Configuration tab and select the Active Directory. 3 Select the Enable Active Directory check box.
10 If DRAC 4 NIC DHCP is enabled, place a check next to Use DHCP to obtain DNS server address. If you want to input a DNS server IP address manually, remove the check next to Use DHCP to obtain DNS server address and input your primary and alternate DNS Server IP addresses. 11 Click Apply to complete the DRAC 4 Active Directory feature configuration. Configuring the DRAC 5 Using the Web-Based Interface 1 Open a supported Web browser window. 2 Log in to the DRAC 5 Web-based interface.
13 Upload your domain forest Root CA certificate into the DRAC 5. • Select the Upload Active Directory CA Certificate check box and then click Next. • In the Certificate Upload page, type the file path of the certificate or browse to the certificate file, and click Apply. NOTE: The File Path value displays the relative file path of the certificate you are uploading. You must type the absolute file path, which includes the full path and the complete file name and file extension.
Configuring DRAC 4 and DRAC 5 Active Directory Settings Using the racadm CLI Using the following commands to configure the DRAC 4 Active Directory feature using the racadm CLI instead of the Web-based interface.
Using Active Directory to Log In To the DRAC 5 You can use Active Directory to log in to the DRAC 5 using one of the following methods: • Web-based interface • Remote RACADM • Serial or telnet console. The login syntax is consistent for all three methods: (or) \ (or) / where username is an ASCII string of 1–256 bytes. White space and special characters (such as \, /, or @) cannot be used in the user name or the domain name.
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\ManagementStation\windows\PreReqChecker or SYSMGMT\srvadmin\windows\PreReqChecker directory on the Dell Systems Management Tools and Documentation DVD. After running the prerequisite check, an HTML file will be created in the %Temp% directory. The file is named omprereq.htm, and it contains the results of the prerequisite check.
Table 10-1. Return Codes While Running the Prerequisite Check Silently Return Code Description 0 No condition, or conditions, is associated with the software. 1 An informational condition, or conditions, is associated with the software. It does not prevent a software product from being installed. 2 A warning condition, or conditions, is associated with the software. It is recommended that you resolve the conditions causing the warning before you proceed with the installation of the software.
Table 10-2. Feature IDs for the Management Station Feature ID Description ADS Microsoft Active Directory® Snap-in Utility BMC Baseboard Management Controller Management Utility ITA Dell OpenManage™ IT Assistant RACMS Remote Access Controller Table 10-3.
Prerequisite Checker
Frequently Asked Questions General Where can I find the quick installation instructions? The Quick Installation Guide comes as a small brochure with the DVD kit. Also, you can find the guide on the Dell Support website at support.dell.com and on the Dell Systems Management Tools and Documentation DVD at SYSMGMT\srvadmin\docs\\OpenManage_QIG\ QUICK_INSTALL_GUIDE.htm where is the appropriate language directory for you.
• 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. If you are not sure which features were installed, select all of them and perform the installation.
What is an MSP service pack file? Should I upgrade my Dell OpenManage 4.3 version with the MSP file? A Microsoft Service Pack (MSP) file stores only the differences between an old version and a new version. It is much smaller in size than the upgrade file. You can either use the MSP file or the new MSI file to upgrade your Dell OpenManage 4.3. Using the MSP file is a good idea as it is more efficient. NOTE: You can upgrade from Dell OpenManage software version 4.3 to 5.
What is the best way to use the Prerequisite Checker information? 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.
Why am I getting a warning concerning the RPM package key during installation? The RPM files are signed with a digital signature. To avoid this warning, you should mount the CD or package, and import the key using a command such as the following: rpm --import /mnt/dvdrom/SYSMGMT/srvadmin/linux/RPM-GPG-KEY Why is the Prerequisite Checker not available under Red Hat Enterprise Linux and SUSE Linux Enterprise Server? The Prerequisite Checker is built into the omilcore RPM package.
Table 11-2.
Table 11-3. Names of the Directories Under the srvadmin/linux/custom/ Directory (continued) Name of RPM Description Other Server Administrator RPMs required srvadmin-deng Server Administrator Data Engine — Systems srvadmin-omilcore management provides a data management framework for systems management software.
Table 11-3. Names of the Directories Under the srvadmin/linux/custom/ Directory (continued) Name of RPM Description Other Server Administrator RPMs required srvadmin-odf Server Administrator Online Diagnostic Common Components — Systems management online diagnostics framework. srvadmin-omilcore, srvadmin-deng, and srvadmin-omacore NOTE: The srvadmin-odf RPM, though installed, will not be functional as Diagnostics is no longer available through Server Administrator.
Table 11-3. Names of the Directories Under the srvadmin/linux/custom/ Directory (continued) Name of RPM Description Other Server Administrator RPMs required srvadminracdrsc3 DRAC III Integration Layer — Remote Access srvadmin-omilcore, CLI and Web Plugin to Server Administrator.
Table 11-3. Names of the Directories Under the srvadmin/linux/custom/ Directory (continued) Name of RPM Description Other Server Administrator RPMs required srvadminracsvc Remote Access Card Managed Node — srvadmin-omilcore Remote Access Controller (RAC) services supporting the central administration of server clusters and the remote administration of distributed resources. add-RAC5 — Software for remote management of fifth generation Remote Access Controllers. For example: DRAC 5.
Table 11-3. Names of the Directories Under the srvadmin/linux/custom/ Directory (continued) Name of RPM Description Other Server Administrator RPMs required add-openipmi-RHEL4 — Provides OpenIPMI support for Red Hat Enterprise Linux (version 4) dkms Dynamic Kernel Module Support Framework — This package contains the framework for the Dynamic Kernel Module Support (DKMS) method for installing module RPMS as originally developed by Dell Computer Corporation. openipmi Openipmi XX.Y.
What daemons run on Red Hat Enterprise Linux and SUSE Linux Enterprise Server operating systems after Server Administrator is started? The daemons that run on Red Hat Enterprise Linux and SUSE Linux Enterprise Server operating systems depend on what has been installed and what is enabled to run. The following table displays the daemons that typically run for a full install: Table 11-4.
What kernel modules are loaded when Server Administrator is started? This is dependent on the type of systems instrumentation. The following table displays the kernel modules loaded when Server Administrator is started. Table 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 readwrite, 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.
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. CIM Acronym for Common Information Model, which is a model for describing management information from the DMTF.
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). Others—such as video drivers—must load when you start the program for which they were designed.
DRAC III/XT Acronym for Dell Remote Access Controller III/XT. 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.
FAT Acronym for file allocation table. FAT and FAT32 are file systems that are defined as follows: • FAT — The operating system maintains a table to keep track of the status of various segments of disk space used for file storage. • FAT32 — A derivative of the FAT file system. FAT32 supports smaller cluster sizes than FAT, thus providing more efficient space allocation on FAT32 drives.
GPG Abbreviation for GNU Privacy Guard. GUI Acronym for graphical user interface. GUID Acronym for Globally Unique Identifier. 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.
ICU Abbreviation for ISA Configuration Utility. ID Abbreviation for identification. 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.
IRQ Abbreviation for interrupt request. A signal that data is about to be sent to or received by a peripheral device travels by an IRQ line to the microprocessor. Each peripheral connection must be assigned an IRQ number. For example, the first serial port in your system (COM1) is assigned to IRQ4 by default. Two devices can share the same IRQ assignment, but you cannot operate both devices simultaneously. ISV Abbreviation for independent software vendor.
LDIF Abbreviation for Lightweight Directory Interchange Format. local bus On a system with local-bus expansion capability, certain peripheral devices (such as the video adapter circuitry) can be designed to run much faster than they would with a traditional expansion bus. Some local-bus designs allow peripherals to run at the same speed and with the same width data path as the system's microprocessor. LRA Abbreviation for local response agent.
memory address A specific location, usually expressed as a hexadecimal number, in the system's RAM. MIB Acronym for management information base. The MIB is used to send detailed status or commands from or to an SNMP-managed device. microprocessor The primary computational chip inside the system that controls the interpretation and execution of arithmetic and logic functions. Software written for one microprocessor must usually be revised to run on another microprocessor.
ms Abbreviation for millisecond(s). name The name of an object or variable is the exact string that identifies it in an SNMP Management Information Base (MIB) file or in a CIM Management Object File (MOF). NDS Abbreviation for Novell Directory Service. NIC Acronym for network interface card. NIS Abbreviation for Network Information Services. NIS is a network naming and administration system for smaller networks.
OID Abbreviation for object identifier. An implementation-specific integer or pointer that uniquely identifies an object. online access service A service that typically provides access to the Internet, e-mail, bulletin boards, chat rooms, and file libraries. PAM Acronym for Pluggable Authentication Modules. PAM allows system administrators to set an authentication policy without having to recompile authentication programs.
peripheral device An internal or external device—such as a printer, a disk drive, or a keyboard— connected to a system. physical memory array The physical memory array is the entire physical memory of a system. Variables for physical memory array include maximum size, total number of memory slots on the motherboard, and total number of slots in use. physical memory array mapped The physical memory array mapped refers to the way physical memory is divided.
program diskette set The set of diskettes from which you can perform a complete installation of an operating system or application program. When you reconfigure a program, you often need its program diskette set.
read-only file A read-only file is one that you are prohibited from editing or deleting. A file can have read-only status if: • Its read-only attribute is enabled. • It resides on a physically write-protected diskette or on a diskette in a writeprotected drive. • It is located on a network in a directory to which the system administrator has assigned read-only rights to you.
RPM Abbreviation for Red Hat® Package Manager. SAN Acronym for storage area network. SAS Acronym for serial attached SCSI. SCA Abbreviation for single connector attachment. schema A collection of class definitions that describes managed objects in a particular environment. A CIM schema is a collection of class definitions used to represent managed objects that are common to every management environment, which is why CIM is called the Common Information Model.
settings Settings are conditions of a manageable object help to determine what happens when a certain value is detected in a component. For example, a user can set the upper critical threshold of a temperature probe to 75 degrees Celsius. If the probe reaches that temperature, the setting results in an alert being sent to the management system so that user intervention can be taken. Some settings, when reached, can trigger a system shutdown or other response that can prevent damage to the system.
SRAM Abbreviation for static random-access memory. Because SRAM chips do not require continual refreshing, they are substantially faster than DRAM chips. SSL Abbreviation for secure socket layer. state Refers to the condition of an object that can have more than one condition. For example, an object may be in the "not ready" state. status Refers to the health or functioning of an object. For example, a temperature probe can have the status normal if the probe is measuring acceptable temperatures.
system board As the main circuit board, the system board usually contains most of your system's integral components, such as the following: • Microprocessor • RAM • Controllers for standard peripheral devices, such as the keyboard • Various ROM chips Frequently used synonyms for system board are motherboard and logic board. system configuration information Data stored in memory that tells a system what hardware is installed and how the system should be configured for operation.
TCP/IP Abbreviation for Transmission Control Protocol/Internet Protocol. A system for transferring information over a computer network containing dissimilar systems, such as systems running Windows and UNIX. termination Some devices (such as the last device at each end of a SCSI cable) must be terminated to prevent reflections and spurious signals in the cable.
time-out A specified period of system inactivity that must occur before an energy conservation feature is activated. tpi Abbreviation for tracks per inch. TSR Abbreviation for terminate-and-stay-resident. A TSR program runs "in the background." Most TSR programs implement a predefined key combination (sometimes referred to as a hot key) that allows you to activate the TSR program's interface while running another program.
USB Abbreviation for Universal Serial Bus. A USB connector provides a single connection point for multiple USB-compliant devices, such as mice, keyboards, printers, and computer speakers. USB devices can also be connected and disconnected while the system is running. utility A program used to manage system resources —memory, disk drives, or printers. utility partition A bootable partition on the hard drive that provides utilities and diagnostics for your hardware and software.
video adapter The logical circuitry that provides—in combination with the monitor—your system's video capabilities. A video adapter may support more or fewer features than a specific monitor offers. Typically, a video adapter comes with video drivers for displaying popular application programs and operating systems in a variety of video modes. On some systems, a video adapter is integrated into the system board. Also available are many video adapter cards that plug into an expansion-card connector.
virtual memory A method for increasing addressable RAM by using the hard drive. For example, in a system with 16 MB of RAM and 16 MB of virtual memory set up on the hard drive, the operating system would manage the system as though it had 32 MB of physical RAM. virus A self-starting program designed to inconvenience you. Virus programs have been known to corrupt the files stored on a hard drive or to replicate themselves until a computer system or network runs out of memory.
Web server An application that makes Web pages available for viewing by Web browsers using the HTTP protocol. Winbind A program that allows users in a heterogeneous network to log in using workstations that have either UNIX or Windows operating systems. The program makes workstations using UNIX functional in Windows domains, by making Windows appear like UNIX to each UNIX workstation. win.ini file A start-up file for the Windows operating system. When you start Windows, it consults the win.
XMM Abbreviation for extended memory manager, a utility that allows application programs and operating systems to use extended memory in accordance with the XMS. XMS Abbreviation for eXtended Memory Specification. X Window System The graphical user interface used in the Red Hat® Enterprise Linux® and SUSE® Linux Enterprise Server environments. ZIF Acronym for zero insertion force.
Index A Association Scope, 183 access read-only, 39 write, 39 ATA, 19 access control, 38 Active Directory, 25, 38, 41, 48, 50, 166, 171, 180, 188 object identifiers, 165 objects, 167 schema, 172 schema extender utility, 172 schema extensions, 165 ADDLOCAL, 91, 122 administrator, 39 Administrator Pack, 181 Administrator privileges, 39, 105 agent, 59 SNMP, 50 agents, 18 AGP, 215 alert filters, 15 alert log, 20 Altiris, 128, 164 ASCII, 215 association, 184 Association Object, 166, 183 attribute, 215 authe
C CA, 66, 186-187 Certificate, 189 certificates Web, 66 certification, 22 Certification Authority, 66, 186-187 custom unattended installation, 84 D DAT, 217 data redundancy, 19 dB, 217 chip, 216 DCOM, 26-27, 32 CI/O, 216 Dell, 100, 165 CIM, 20, 38, 46, 52, 103 Dell base OID, 165 CIM protocol, 92 Dell OpenManage, 201 Citrix, 109 Dell organizational unit, 172 CLI, 21, 40, 122, 199 Dell Remote Access Controller, 167 cm, 216 command line, 123 command line interface, 21, 40 Common Information Mode
domain controller, 184, 186-187 G DRAC, 21, 181, 186-187 Globally Unique Identifier (GUID), 123 DRAC 4, 186-187, 189-190, 206 controller, 21 SSL certificate, 186-187 group privileges, 38 GUID, 114 DRAC 5 controller, 21 DRAC III, 21, 205 XT, 21 H DRAC III/XT, 21 hot spares, 19 Dynamic Kernel Support, 44, 138 HTTP, 27-28, 33-34, 36-37 E encryption, 38 ERA, 21 ERA/MC, 21 ERA/O, 21 ESX Server, 164 express setup, 45, 76 Extraction Utility, 19 help, 22 HTTPS, 26, 30, 32-34, 36-37, 41 I In, 185 INI
J Windows Installer Engine, 75 Windows Server 2003, 201 Windows Small Business Server, 44, 68, 101 Java Secure Socket Extension, 41 JSSE, 41 MMC, 182-183, 185 modular system, 21 L modular systems, 18 language, 199 MOF, 20 LDAP, 26, 29, 36, 176 monitored systems, 18 LDAPS, 35-37 monitoring, 11 LDIF script file, 172 Mozilla Firefox, 46 LinkID, 165 MSI, 114, 201 logs, 18 msiexec.
operating systems, 15 R P RAC, 21, 45, 165, 172, 182-183 devices, 166 installation, 45 software, 45, 102 packets SNMP, 52 racadm, 21, 25, 192 PAM, 41 RAID, 69 passwd, 50 RAID controllers, 15 Pluggable Authentication Modules, 41 RBAC, 38 port information, 26 ports, 25-26, 199 power user, 39 RDP, 30 readme, 22, 43 read-only access, 39 Prerequisite Checker, 73, 107, 195, 202 Red Hat Enterprise Linux, 15, 17, 43, 46, 49, 55, 59, 71, 93, 136, 138, 163, 204 prerequisite status, 77 REINSTALL, 91,
authority, 25 Root CA, 184 RPC, 26, 29, 31 RPM, 135, 151, 158, 204 rpms, 161 proxy, 47 Server Administrator, 18, 20, 170, 205 Services, 151, 203 Server Update Utility, 19 session timeout, 65 setup custom, 76 express, 45, 76 S SAS, 19 SATA, 19 SBS, 44, 68, 101 setup.exe, 73, 77, 88 shutdown, 15 schema, 165, 172 Simple Network Management Protocol, 20, 46, 103 SchemaExtenderOem.
SOL Proxy, 17 U SSH, 28, 31 UDP, 28 SSL, 41, 171, 184-185 unattended installation, 82, 116 SSL encryption, 25 unattended uninstallation, 126 standard action, 113 universal groups, 183 storage management, 40 update packages, 22 Storage Management Service, 18, 203 updates, 19 software, 15 Subscription Kit, 14 upgrade, 47, 79, 201 SUU, 19 user, 38 SysMgmt.
Windows Installer Engine, 118 Installer Service, 114 Windows Management Instrumentation, 46, 103 Windows Server 2003, 201 WMI, 46, 52, 103 write access, 39 X X.
