Dell™ OpenManage™ Version 5.3 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.3 Dell OpenManage Systems Management Software Kit Contents . . . . . . . . . . . . . . . . . . 13 Dell Systems Management Tools and Documentation DVD . . . . . . . . . . . . . . . . 13 . . . . . . . . . . . . . . . . . . . . . . . .
2 Dell™ OpenManage™ Security . Security Features . . . . . . . 23 . . . . . . . . . . . . . . . . . . . . 23 . . . . . . . . . . . . . . . . 23 . . . . . . . . . . . . . . . . . . . . . . . . 23 Built-in Security Features Ports Security Management RBAC . . . . . . . . . . . . . . . . . . 36 . . . . . . . . . . . . . . . . . . . . . . . . 36 Microsoft Active Directory 3 . . . . . . . . . . . . . . . . . . . . . . . . . 39 Setup and Administration . . . . . . . . . . . . 41 . . . . . .
Configuring the SNMP Agent . . . . . . . . . . . . . . . . . . . . . . . 50 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 . . . . . . . . . Setting User and Server Preferences X.509 Certificate Management . 4 62 . . . . . . .
Enabling CIM Discovery and Security in IT Assistant . . . . . . . . . . . . . . . Installing SNMP . . . . . . 72 . . . . . . . . . . . . . . . . . . 72 Installing, Upgrading, and Uninstalling Management Station Software on Systems Running Supported Windows Operating Systems . . . . . . . . . . . . . . . . . . . . 72 Installing and Upgrading Management Station Software . . . . . . . . . . . . . . . . . . . 74 . . . . . . . . . . . . . . . . . 75 Typical and Custom Installations .
6 Installing Managed System Software on Microsoft ® Windows ® Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Overview . . . . . . . . . . . . . . . . . . . . . . . . Dell Systems Console and Agent CD or Dell Systems Management Tools and Documentation DVD . . . . . . . . . . . . . . . . 95 . . . . 96 . . . . . . . . . . . . . . . . . . . . 96 Unattended and Scripted Silent Installation Before You Begin 95 Installation Requirements . . . . . . . . . . . . . . . .
7 Installing Dell™ OpenManage™ Software On Microsoft ® Windows Server ® 2008 Core . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 Introduction . . . . . . . . . . . . . . . . . . . . . . . Installing Managed System and Management Station Software On Server Core . . . . . . . . . . . . . . . Run PreReqChecker In CLI Mode . 125 . . . . . . . . . 125 Installing Management Station Software in CLI Mode . . . . . . . . . . . . . . . . Installing Managed System Software In CLI Mode . . . . . .
Upgrading From Previous Versions Using Dell OpenManage with VMware® ESX Server™ Software . . . . . 159 . . . . . . . . . . . 160 Managed System Software Installation Using Third-Party Deployment Software . . . . . . 9 Controlling Access to Your Network . . 163 . . . . . . . 163 . . . . . . . . 170 . . . . . . . . . 171 . . . . . . . . . . . . 178 Extending the Active Directory Schema Using the Dell Schema Extender . Adding Users and Privileges to Active Directory . . . . . . . . 179 .
11 Frequently Asked Questions General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Microsoft® Windows® . . . . . . . . . . . . . . . . . Red Hat® Enterprise Linux® or SUSE® Linux Enterprise Server . . . . . . . . . . . . . 197 197 198 202 Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 Index 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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 Microsoft Windows Server 2008 Core (x64) Standard and Datacenter editions • Added support for Red Hat® Enterprise Linux® Version 4.5 (x86) and (x86_64) for AS, ES, and WS editions For more information, see the Dell OpenManage website at www.dell.com/openmanage.
• DOCCD: This directory contains documentation for systems, systems management software products, peripherals, and RAID controllers. • SERVICE: The SERVICE directory provides tools to configure your managed systems and delivers the latest diagnostics and Dell-optimized drivers for your managed systems. CD Kit • Dell Systems Build and Update Utility CD — Provides the tools that you need to install an operating system and configure your managed systems.
Dell Server Updates DVD Contains the Server Update Utility (SUU), an application for identifying and applying firmware, BIOS, and driver updates to your system. NOTE: The Dell Server Updates DVD is available only as part of the Subscription Service Kit or from the Dell Support website at support.dell.com.
Using IT Assistant, you can: • Identify the groups of systems that you want to manage remotely • Consolidate your view of all systems, providing a central launch point for systems management applications • Create alert filters and actions that will automatically notify you when system uptime is affected • Create custom enterprise-wide reports that show the status of each system, including switches, storage devices, BIOS, firmware, and driver versions • Create customized tasks that allow you to coor
• Remote system power up and power down • Remote floppy boot operations See the Dell Remote Access Controller 4 User’s Guide, Dell Remote Access Controller 5 User’s Guide, or Integrated Dell Remote Access Controller User’s Guide for more information. Baseboard Management Controller (BMC) Management Utility The BMC Management Utility provides a command line based remote management application to manage all supported BMC functions.
Active Directory Snap-in Utility The Microsoft Active Directory Snap-in utility provides an extension snap-in to the Microsoft Active Directory, which allows you to manage Dell-specific Active Directory objects. You can use this option when you add the Dell-specific schema classes to the Active Directory schema.
You must have Server Administrator on your system to install the Remote Access Service. NOTE: The Server Administrator Remote Access Service and Remote Access Controller management console cannot be installed on a system at the same time. If both Server Administrator and management station are installed at the same time and RAC support is required, install Server Administrator Remote Access Service. It provides all the functionality of the Remote Access Controller management console.
Change Management The Dell Server Updates DVD includes the Server Update Utility (SUU) and is available for both Windows and Linux operating systems. SUU allows you to identify and apply updates to your system. SUU is a dual-purpose application and is easy to use. You can use SUU to update your Dell system or to view the updates available for any system listed in the SUU Repository. SUU facilitates change management by allowing you to update system components.
• The Dell OpenManage Server Administrator SNMP Reference Guide documents the Simple Network Management Protocol (SNMP) management information base (MIB). The SNMP MIB defines variables that extend the standard MIB to cover the capabilities of systems management agents. • The Dell OpenManage Server Administrator CIM Reference Guide documents the Common Information Model (CIM) provider, which is an extension of the standard management object format (MOF) file.
• The Dell Remote Access Controller Installation and Setup Guide provides complete information about installing and configuring a DRAC III, DRAC III/XT, or ERA/O controller, configuring an ERA controller, and using a RAC to remotely access an inoperable system. • The Dell Remote Access Controller Racadm User's Guide provides information about using the racadm command line utility to manage DRAC III, DRAC III/XT, ERA, and ERA/O controllers.
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. Dell OpenManage UDP/TCP Ports Default Locations Port # Protocol Port Type Version Maximum Directi Usage Encryption on Level Configura ble Dell OpenManage Baseboard Management Controller - PowerEdge™ x8xx systems 623 RMCP UDP PowerE None dge x8xx 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. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Type Version Maximum Directi Usage Encryption on Level 1024 - DCOM TCP/ 65535 UDP (Dyna micall y assign ed) 2.0 None Configura ble In/Out Viewing of client Port management data range can be restricted. Dell OpenManage Client Instrumentation 20 HTTP and FTP TCP 7.x None In/Out Flash BIOS communication No 21 HTTP and FTP TCP 7.x None In/Out Flash BIOS communication No 80 HTTP and FTP TCP 7.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Type Version Maximum Directi Usage Encryption on Level Configura ble 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 Directi Usage Encryption on Level Configura ble 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 Port Type Version Maximum Directi Usage Encryption on Level 2606 Propriet TCP ary 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 Propriet TCP ary 8.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Type Version Maximum Directi Usage Encryption on Level Configura ble 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 Directi Usage Encryption on Level Configura ble 161 SNMP UDP 1.x, 2.0 None In/Out SNMP query management No 162 SNMP UDP 1.x, 2.0 None Out 445 NetBIO TCP S 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 Propriet UDP ary 1.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Type Version Maximum Directi Usage Encryption on Level Configura ble 68 DHCP UDP 1.2 None In/Out DHCP assigned IP address No 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 443 HTTPS TCP 1.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Type Version Maximum Directi Usage Encryption on Level Configura ble 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 Directi Usage Encryption on Level Configura ble 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 Propriet TCP ary 1.0 None In/Out CD/diskette virtual media service Yes 5869 Propriet TCP ary 1.0 None In/Out Remote racadm No 5900 Propriet TCP ary 1.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Type Version Maximum Directi Usage Encryption on Level Configura ble 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 389 LDAP TCP 1.0 None In/Out Optional ADS authentication 443 HTTPS TCP 1.0 128-bit SSL In/Out Web management No GUI and remote racadm CLI utility 636 LDAPS TCP 1.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Type Version Maximum Directi Usage Encryption on Level Configura ble 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 443 HTTPS TCP 1.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Type Version Maximum Directi Usage Encryption on Level Configura ble Digital KVM 2068 Propriet TCP ary 1.0 128-bit SSL In/Out Video Redirection No — Keyboard/Mouse 3668 Propriet TCP ary 1.0 None In/Out Virtual Media No 8192 Propriet TCP ary 1.0 None In/Out Video redirection to client viewer No NOTE: CIM ports are dynamic. See the Microsoft knowledge base at support.microsoft.
User Privileges Server Administrator grants different access rights based on the user's assigned group privileges. The three user levels are User, Power User, and Administrator. Users can view most information. Power Users can set warning threshold values and configure which alert actions are to be taken when a warning or failure event occurs.
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. 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. Unavailable Supported SUSE Linux Enterprise Server operating systems.
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.
Supported Operating Systems (Minimum Levels) • Windows 2000 Server SP4 (Server and Advanced Server) • Windows Server® 2003 x86 SP2 (Standard, Enterprise, and Web editions) • 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) • Windows Storage Server 2003 R
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 Console and Agent CD and the Dell Systems Management Tools and Documentation DVD provide 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.
Supported Operating Systems The management station software runs, at a minimum, on each of the following operating systems: • Windows 2000 Server SP4 Server and Advanced Server • Windows Server® 2003 x86 SP2 (Standard, Enterprise, and Web editions) • Windows Server 2003 x64 SP2 (Standard, Enterprise, and DataCenter Editions) • Windows Server 2003 R2 x86 Gold and SP2 (Standard and Enterprise editions) • Windows Server 2003 R2 x64 Gold and SP2 (Standard, Enterprise, and DataCenter Editions) • Wind
• SUSE Linux Enterprise Server (version 9), SP3, x86_64 (BMC management utility and RAC Management Station) • SUSE Linux Enterprise Server (version 10) Gold x86_64 NOTE: The Dell OpenManage 5.3 installer offers Multilingual User Interface support on Windows Storage Server 2003 R2, Windows Storage Server 2003 R2, Express x64 Edition with Unified Storage, Windows Storage Server 2003 R2, Workgroup x64 Edition with Unified Storage, Windows Server 2008 (x86 and x64), and Windows Vista operating systems.
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. Installing SNMP The SNMP service must be installed and running on the IT Assistant system. SNMP (or CIM) must also be installed on the systems that you want to discover and manage.
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 Console and Agent CD or the Dell Systems Management Tools and Documentation DVD in your system’s CD/DVD drive.
5 Click the Install, Modify, Repair or Remove Management Station option. The Welcome to the Install Wizard for Dell OpenManage Management Station screen appears. 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.
13 Click Finish to leave the management station installation. NOTE: You can cancel the installation process by clicking Cancel. The installation rolls back the changes that you made. If you click Cancel at a later 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" for more information.
3 Click Next. The Installing Dell OpenManage Management Station screen appears. Messages provide the status and progress of the software features being installed or upgraded. When the selected features are installed or upgraded, the Install Wizard Completed dialog box appears. 4 Click Finish to leave the management station installation. Upgrade Using the Windows Installer Patch File You can upgrade your management station software using the Windows Installer Patch (.MSP) file.
7 Click Next to accept the selected software features for installation. The Ready to Modify the Program dialog box appears. 8 Click Install to install the selected software features. The Installing Dell OpenManage Management Station screen appears. Messages provide the status and progress of the software features being installed. When the selected features are installed, the Install Wizard Completed dialog box appears. 9 Click Finish to leave the management station installation.
System Recovery on Failed Installation If a software installation utility encounters a fatal error during setup, your system may become unstable. To address this problem, Dell OpenManage installers provide the ability to roll back, or return, the system to its fully-working condition prior to the failed installation.
The unattended installation package is distributed to the remote systems using a software distribution tool from an independent software vendor (ISV). When the package is distributed, the installation script installs the software.
2 Create a script that maps a drive from the remote systems to the shared drive described in step 1. This script should execute the following command after you have mapped the drive: msiexec.exe /i MappedDrive\ManagementStation\windows\ManagementS tation\MgmtSt.msi /qb (if you are using the CD) msiexec.exe /i MappedDrive\SYSMGMT\ManagementStation\windows\Man agementStation\MgmtSt.
Creating and Distributing Custom Unattended Installation Packages To create a custom unattended installation package for distribution, copy the ManagementStation\windows directory from the CD or the SYSMGMT\ManagementStation\windows directory on the DVD onto the system’s hard drive. Create a batch script that will execute the installation using the Windows Installer Engine (msiexec.exe). For example: msiexec.exe /i MgmtSt.
Specifying Log File Locations Run the following command to perform an unattended installation while specifying the log file location: msiexec.exe /i MgmtSt.msi /l*v "C:\openmanage\logs\MgmtSt.log" Optional Command Line Settings Table 5-1 shows the optional command line settings available for the msiexec.exe. Type the optional settings on the command line after msiexec.exe with a space between each setting. NOTE: See support.microsoft.
Table 5-1. Setting Command Line Settings for MSI Installer (continued) 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 /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 Console and Agent CD, Dell Systems Management Tools and Documentation DVD, or your operating system.
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 Console and Agent CD or 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 CD Drive\ManagementStation\windows\ManagementStation \MgmtSt.msi /qb (msiexec.exe /x DVD Drive\SYSMGMT\ManagementStation\windows\Managemen tStati
For management stations, use this command: msiexec.exe /x {DA60872C-9147-4A6E-9AEF-95BAB5EF3A3B} 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.
This command runs the installation for only the management station and reinstalls Remote Access Controller management station, in an unattended and verbose mode. 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.
After an upgrade on a system that has been migrated to Windows Server 2003, systems configured with the CIM protocol might no longer be discovered. If this issue occurs, reset the password for the CIM user. In the IT Assistant user interface, go to Discovery and Monitoring, select Ranges and right-click 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.
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 Console and Agent CD or the Dell Systems Management Tools and Documentation DVD to a desired location using the mount command or a similar command.
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 Console and Agent CD or the Dell Systems Management Tools and Documentation DVD to a desired location using the mount command or a similar command.
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. To uninstall the IPMItool, use rpm -e `rpm -qa | grep ipmitool` for SUSE Linux Enterprise Server operating systems or rpm -e `rpm -qa | grep OpenIPMI-tools` command for Red Hat Enterprise Linux operating systems.
Installing Management Station Software 95
Installing Management Station Software
Installing Managed System Software on Microsoft® Windows® Operating Systems Overview The Dell™ Systems Console and Agent CD and the Dell Systems Management Tools and Documentation DVD provide 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.
Server Administrator on systems running all supported Windows operating systems. On systems running supported Microsoft Windows operating systems, you can uninstall the features through the operating system. NOTE: See the Dell Systems Software Support Matrix document for a list of the systems that are currently supported.
Supported Operating System Versions Server Administrator supports each of the following Windows operating systems: • Windows 2000 Server SP4 (Server and Advanced Server) • Windows Server® 2003 x86 SP2 (Standard, Enterprise, and Web editions) • Windows Server 2003 x64 SP2 (Standard, Enterprise, and DataCenter Editions) • Windows Server 2003 R2 x86 Gold and SP2 (Standard and Enterprise editions) • Windows Server 2003 R2 x64 Gold and SP2 (Standard, Enterprise, and DataCenter Editions) • Windows SBS
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 CD/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.
IPMI support. If your system is running Windows Server 2003 R2 or Windows Storage Server R2, it is recommended that after you install or upgrade Server Administrator, you also install the optional Hardware Management component of R2. To install the Windows Server 2003 R2 IPMI driver on PowerEdge x8xx and PowerVault x00 systems, perform the following additional step: • From a command shell, execute the following command: Rundll32 ipmisetp.
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.3 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 Console and Agent CD or the Dell Systems Management Tools and Documentation DVD into your system's CD 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 srvadmin\windows folder on the CD, and run the setup.exe file. On the DVD, the setup program resides on the SYSMGMT\srvadmin\windows directory.
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.
3 Click the Install, Modify, Repair, or Remove Server Administrator option. The Welcome to the Install Wizard for Dell OpenManage Server Administrator screen appears. The Resuming the Install Wizard for Dell OpenManage Server Administrator screen appears. 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.
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 Console and Agent CD or the Dell Systems Management Tools and Documentation DVD as the unattended installation package. The msiexec.exe /i SysMgmt.msi /qb command accesses the CD (or the DVD) to accept the software license agreement and install all required Server Administrator features on selected remote systems. The msiexec.exe /i SysMgmt.
4 Distribute this script to the target systems by using your ISV software distribution tools. The script executes to install Server Administrator on each remote system. 5 Reboot each remote system to enable Server Administrator. Distributing the Entire CD as the Typical Unattended Installation Package 1 Distribute the entire image of the Dell Systems Console and Agent CD or the Dell Systems Management Tools and Documentation DVD to your target systems.
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 srvadmin\windows\SystemsManagement directory on the CD and in the SYSMGMT\srvadmin\windows\SystemsManagement directory in the DVD.
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.3. This command also carries out major upgrades from version 4.3 to 5.3. 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.
Table 6-3. Windows Installer Return Codes Error Code Value Description ERROR_SUCCESS 0 The action completed successfully. ERROR_INVALID_PARAMETE 87 R One of the parameters was invalid. ERROR_INSTALL_USEREXIT 1602 The user canceled the installation. ERROR_SUCCESS_REBOOT_R 3010 A restart is required to complete the EQUIRED installation. This message is indicative of a successful installation. NOTE: See support.microsoft.com for full details on all the error codes returned by the msiexec.
2 Click the Install, Modify, Repair, or Remove Server Administrator option. The Welcome to the Install Wizard for Dell OpenManage Server Administrator screen appears. 3 Click Next. The Program Maintenance dialog box appears. This dialog enables you to modify, repair, or remove the program. 4 Select the Remove option and click Next. The Remove the Program dialog box appears. 5 Click Remove.
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. If you are prompted to reboot your system, you must do so in order for the uninstallation to be successful. If you are prompted to reboot your system, select a reboot option: • Yes, reboot my system now. • No, I will reboot my system later. All Server Administrator features are uninstalled.
Distributing the Unattended Uninstallation Package The Dell Systems Console and Agent CD or the Dell Systems Management Tools and Documentation DVD is pre-configured to act as the unattended uninstallation package. To distribute the package to one or more systems, perform the following steps: 1 Configure your ISV distribution software to execute the msiexec.exe /x CD Drive\srvadmin\windows\SystemsManagement\SysMgmt. msi /qb command (or msiexec.exe /x CD Drive\SYSMGMT\srvadmin\windows\SystemsManagement\ Sys
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 on the Dell Systems Console and Agent CD at \srvadmin\support\Altiris or at SYSMGMT\srvadmin\support\Altiris on the Dell Systems Management Tools and Document
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 srvadmin\windows\prereqchecker on the Dell Systems Console and Agent CD and 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.
– – 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 srvadmin\windows\SystemsManagement on the Dell Systems Console and Agent CD and at SYSMGMT\srvadmin\windows\SystemsManagement on the Dell Systems Management Tools and Documentation DVD.
130 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 Console and Agent CD or 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.
• SUSE Linux Enterprise Server (version 9), SP3 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 Console and Agent CD or on the Dell Systems Management Tools and Documentation DVD; or, see the Dell OpenManage Server Administrator Compatibility Guide on the Dell Systems Documentation CD.
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 Console and Agent CD and 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.
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 srvadmin/linux/custom/ or SYSMGMT/srvadmin/linux/custom, if you are using the DVD. 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.
2 Navigate to the srvadmin/linux/supportscripts or SYSMGMT/srvadmin/linux/supportscripts if you are using the DVD. 3 Run the srvadmin-openipmi.sh shell script as shown below. This will build and install the OpenIPMI driver modules. sh srvadmin-openipmi.sh install Re-attempt to install the srvadmin-hapi RPM and any RPMs that failed to install as they depend on the srvadmin-hapi RPM.
If you know or suspect that the OpenIPMI device driver on the system is not appropriate, you can run the srvadmin-openipmi.sh shell script on the Dell Systems Console and Agent CD or the Dell Systems Management Tools and Documentation DVD to install an appropriate version by performing the following steps: 1 Navigate to the srvadmin/linux/supportscripts or SYSMGMT/srvadmin/linux/supportscripts if you are using the DVD. 2 Run the srvadmin-openipmi.sh shell script as shown below. sh 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 (CD or DVD) is divided into subdirectories to enable easy Custom Installs. NOTE: On the Red Hat Enterprise Linux 5 operating system, CDs are auto-mounted with the -noexec mount option. This option does not allow you to run any executable from the CD. You need to manually mount the CD-ROM and then run executables.
Express Install Use the provided shell script to perform the express installation in silent and unattended mode. NOTE: On the Red Hat Enterprise Linux 5 operating system, CDs are auto-mounted with the -noexec mount option. This option does not allow you to run any executable from the CD. You need to manually mount the CD-ROM and then run executables.
6 Start the Server Administrator services after the installation using the srvadmin-services.sh script by using the sh srvadmin-services start command. Custom Install Managed system software provides two custom installation paths. One is RPM-based, with pre-configured custom directories, and the other is shell script-based.
Table 8-1.
5 Type the following command. rpm -ihv srvadmin-base/*.rpm srvadminbase/openipmi/*.rpm add-storageservices/*.rpm NOTE: IPMI packages may already be installed on your system and hence may not require re-installation. Server Administrator services do not start automatically.
Using the Custom Install Script To Run in the Silent and Unattended Mode The following is an example of a silent and unattended custom installation using the srvadmin-install.sh shell script. 1 Log on as root to the system running the supported Red Hat Enterprise Linux or SUSE Linux Enterprise Server operating system where you want to install the managed system components. 2 Insert the Dell Systems Console and Agent CD or the Dell Systems Management Tools and Documentation DVD into the CD drive.
Using the Shell Script to Perform the Custom Installation in Interactive Mode This procedure uses the installation shell script to prompt you for the installation of specific components through the installation. 1 Log in as root to the system running the supported Red Hat Enterprise Linux or SUSE Linux Enterprise Server operating system where you want to install the managed system components.
Performing an Unattended Installation of the Managed System Software You can use Dell OpenManage installer’s Express Install and Custom Install options for the unattended installation procedure. Unattended installation allows you simultaneously to install Server Administrator on multiple systems. You can perform an unattended installation by creating an unattended installation package that contains all of the necessary managed system software files.
Distributing the Express-Install subdirectory as the Express Unattended Installation Package 1 Distribute the srvadmin/linux/supportscripts and the srvadmin/linux/RPMS subdirectories of the Dell Systems Console and Agent CD to your target systems. If you are using the Dell Systems Management Tools and Documentation DVD, distribute SYSMGMT/srvadmin/linux/supportscripts and the SYSMGMT/srvadmin/linux/RPMS subdirectories. 2 Configure your ISV software distribution software to execute sh srvadmin-install.
Distributing Unattended Installation Packages The custom unattended installation package is located in the directory you created in the preceding step 6 of the custom installation (see "Custom Install"). This directory contains all of the RPMs for the managed system software components to distribute. 1 Configure your ISV software distribution software to execute rpm –i *.rpm after the unattended installation package has been distributed.
3 After the CD mounts, navigate to the RPMS directory by using a command similar to the following: cd /media/cdrom/srvadmin/linux/RPMS/ or cd /media/cdrom/SYSMGMT/srvadmin/linux/RPMS/ if you are using the DVD. Where is RHEL4 or RHEL5 or SLES9 or SLES10. Enter the appropriate directory name that applies to your system. 4 Upgrade the Red Hat Enterprise Linux or SUSE Linux Enterprise Server system using a single long command or individual RPMs.
To upgrade all the previously installed packages using individual RPMs, perform the following steps: a Query the rpm database for all installed srvadmin packages by typing: rpm -qa | grep srvadmin The query displays a list of all installed packages, including any existing or older versions. For example: srvadmin-omilcore-4.3.0-1.386.rpm srvadmin-hapi-4.3.0-1.386.rpm srvadmin-deng-4.3.0-1.386.rpm srvadmin-isvc-4.3.0-1.386.rpm ...
Reattempt to upgrade the srvadmin-hapi RPM and any other RPMs that failed to upgrade as they depend on the srvadmin-hapi RPM. Perform the following steps: 1 Navigate back to the previous directory that you were at. 2 Run the following commands to see which Server Administrator packages were previously successfully upgraded. rpm -qa | grep srvadmin The query displays a list of all installed Server Administrator packages. Those that have already been upgraded will display the new version number.
3 Run the srvadmin-openipmi.sh shell script as shown below. This will build and install the OpenIPMI driver modules. sh srvadmin-openipmi.sh install Reattempt to upgrade the srvadmin-hapi RPM and any RPMs that failed to upgrade as they depend on the srvadmin-hapi RPM. Perform the steps described on page 156 Using the srvadmin-install Shell Script 1 Log on as root to the system running Red Hat Enterprise Linux that requires the upgrade.
For example: Server Administrator version 4.4.0 is currently installed. Installed components are: - srvadmin-omilcore - srvadmin-hapi - srvadmin-deng - srvadmin-isvc Next, the script prompts you with the following message: Do you want to upgrade Server Administrator to 5.3? Press ('y' for yes | 'Enter' to exit): 5 Select y to upgrade the system. Server Administrator is upgraded to version 5.3. NOTE: Just before the Server Administrator RPMs are upgraded, the srvadmininstall.
Uninstalling Managed System Software From the Red Hat Enterprise Linux or SUSE Linux Enterprise Server Command Line An uninstallation script is installed when Server Administrator is installed. You can execute the script by typing srvadmin-uninstall.sh and then pressing . NOTE: When executed, the srvadmin-uninstall.sh will not attempt to uninstall the OpenIPMI driver even if the OpenIPMI driver was installed or upgraded during previous execution of the srvadmin-install.
Managed System Software Installation Using Third-Party Deployment Software You can use third-party deployment software, such as Altiris Deployment Solution, to install managed system software onto supported Dell servers. To distribute and install managed system software using Altiris, start your Altiris application and import OpenManage_Jobs.bin located on the Dell Systems Console and Agent CD at \srvadmin\support\Altiris; or at SYSMGMT\srvadmin\support\Altiris on the Dell Systems Management Tools and Docum
162 Installing Managed System Software on Supported Linux Operating Systems
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.
The Active Directory OID database maintained by Microsoft can be viewed at msdn.microsoft.com/certification/ADAcctInfo.asp by entering our extension, dell. 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.
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.
To use the LDIF files, see the instructions in the readme that is in the LDIF files directory. To use the Dell Schema Extender to extend the Active Directory Schema, perform the steps in "Using the Dell Schema Extender." You can copy and run the Schema Extender or LDIF files from any location. Using the Dell Schema Extender NOTICE: The Dell Schema Extender uses the SchemaExtenderOem.ini file.
Table 9-1. Class Definitions for Classes Added to the Active Directory Schema (continued) Class Name Assigned Object Identification Number Class Type (OID) dellOmsa2AuxClass 1.2.840.113556.1.8000.1280.1.2.1.1 Auxiliary Class dellOmsaApplication 1.2.840.113556.1.8000.1280.1.2.1.2 Structural Class dellIta7AuxClass 1.2.840.113556.1.8000.1280.1.3.1.1 Auxiliary Class dellItaApplication 1.2.840.113556.1.8000.1280.1.3.1.2 Structural Class Table 9-2. dellRacDevice Class OID 1.2.840.113556.1.8000.
Table 9-4. dellRAC4Privileges Class OID 1.2.840.113556.1.8000.1280.1.1.1.3 Description This class is used to define the privileges (Authorization Rights) for the DRAC 4 device. Class Type Auxiliary Class SuperClasses None 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.
Table 9-6. dellProduct Class OID 1.2.840.113556.1.8000.1280.1.1.1.5 Description This is the main class from which all Dell products are derived. Class Type Structural Class SuperClasses Computer Attributes dellAssociationMembers Table 9-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.
Table 9-9. dellOmsaApplication Class OID 1.2.840.113556.1.8000.1280.1.2.1.2 Description This class represents the Server Administrator application. Server Administrator must be configured as dellOmsaApplication in Active Directory. This configuration enables the Server Administrator application to send LDAP queries to Active Directory. Class Type Structural Class SuperClasses dellProduct Attributes dellAssociationMembers Table 9-10. dellIta7AuxClass Class OID 1.2.840.113556.1.8000.1280.1.3.1.
Table 9-12. General Attributes Added to the Active Directory Schema Attribute Name/Description Assigned OID/Syntax Object Identifier Single Valued dellPrivilegeMember 1.2.840.113556.1.8000.1280.1.1.2.1 FALSE List of dellPrivilege Objects that belong Distinguished Name to this Attribute. (LDAPTYPE_DN 1.3.6.1.4.1.1466.115.121.1.12) dellProductMembers 1.2.840.113556.1.8000.1280.1.1.2.2 FALSE List of dellRacDevices Objects that Distinguished Name belong to this role.
Table 9-13. RAC-specific Attributes Added to the Active Directory Schema (continued) Attribute Name/Description Assigned OID/Syntax Object Identifier Single Valued delIsLogClearAdmin 1.2.840.113556.1.8000.1280.1.1.2.6 TRUE TRUE if the User has Log Clearing Boolean (LDAPTYPE_BOOLEAN rights on the device. 1.3.6.1.4.1.1466.115.121.1.7) dellIsServerResetUser 1.2.840.113556.1.8000.1280.1.1.2.7 TRUE if the User has Server Reset rights on the device. Boolean (LDAPTYPE_BOOLEAN 1.3.6.1.4.1.1466.115.121.1.
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 Console and Agent CD or 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 Your Systems or Devices For instructions on how to configure your Server Administrator or IT Assistant systems using CLI commands, see "Configuring Active Directory Using CLI on Systems Running Server Administrator" and "Configuring Active Directory on Systems Running IT Assistant." For DRAC users, there are two ways to configure DRAC 4. See either "Configuring the DRAC 4 Using the WebBased Interface" or "Configuring DRAC 4 and DRAC 5 Active Directory Settings Using the racadm CLI.
Table 9-16 shows the valid parameters for the command. Table 9-16. Active Directory Service Configuration Parameters name=value pair Description prodname= Specifies the software product to which you want to apply the Active Directory configuration changes. Prodname refers to the name of the product defined in omprv32.ini. For Server Administrator, it is omsa. enable= true: Enables Active Directory service authentication support.
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. 4 Type the DRAC 4 Name. This name must be the same as the common name of the RAC object you created in your Domain Controller (see "Installing the Dell Extension to the Active Directory Users and Computers Snap-In"). 5 Type the Root Domain Name.
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. 3 Expand the System tree and click Remote Access. 4 Click the Configuration tab and select Active Directory. 5 In the Active Directory Main Menu page, select Configure Active Directory and click Next. 6 Select the Enable Active Directory check box. 7 Type the DRAC 5 Name.
14 Log out and then log in to the DRAC 5 to complete the DRAC 5 Active Directory feature configuration. 15 In the System tree, click Remote Access. 16 Click the Configuration tab and then click Network. The Network Configuration page appears. 17 If Use DHCP (for NIC IP Address) is selected under Network Settings, then select Use DHCP to obtain DNS server address.
3 If DHCP is disabled or you want manually to input your DNS IP address, type the following commands: racadm config -g cfgLanNetworking -o cfgDNSServersFromDHCP 0 racadm config -g cfgLanNetworking -o cfgDNSServer1 racadm config -g cfgLanNetworking -o cfgDNSServer2 4 Press to complete the Active Directory feature configuration. See the Dell Remote Access Controller 4 User’s Guide or Dell Remote Access Controller 5 User’s Guide for more information.
192 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 ManagementStation\windows\PreReqChecker or \srvadmin\windows\PreReqChecker directory on the Dell Systems Console and Agent CD. On the Dell Systems Management Tools and Documentation DVD, the executable is available at SYSMGMT\ManagementStation\windows\PreReqChecker or SYSMGMT\srvadmin\windows\PreReqChecker.
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.
196 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 CD kit. Also, you can find the guide on the Dell Support website at support.dell.com and at the following location on the Dell Systems Console and Agent CD, Dell Systems Documentation CD, or the Dell Systems Management Tools and Documentation DVD: \srvadmin\docs\language\OpenManage_QIG\QUICK_INSTALL_GUIDE. htm OR SYSMGMT\srvadmin\docs\language\OpenManage_QI
Microsoft® Windows® How do I fix a faulty installation of Server Administrator? You can fix a faulty installation by forcing a reinstall and then performing an uninstall of Server Administrator. To force a reinstall: • Find out the version of Server Administrator that was previously installed. • Download the installation package for that version from the Dell Support website at support.dell.com. • Locate SysMgmt.msi from the srvadmin\windows\SystemsManagement directory (or from SYSMGMT\srvadmin\windows
How do I prevent the system from rebooting after a silent (unattended) install/uninstall? Use the optional command line switch: Reboot=ReallySuppress Here is an example for the management station: msiexec /i SysMgmt.msi /qb Reboot=ReallySuppress 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.
I cannot upgrade from Dell OpenManage 4.2 to the latest version of Dell OpenManage without uninstalling and losing my managed system software settings. Is there a way to upgrade to the latest version while preserving my managed system software settings? Yes, but you must upgrade from Dell OpenManage version 4.2 to 4.3 first, before upgrading to a later version of Dell OpenManage. If you are working with Windows Server® 2003, do not apply Service Pack 1 until you have completed the Dell OpenManage upgrade.
• • Windows Scripting Host (WSH) has disabled the running of VBS scripts. WSH is installed during operating system installation, by default. WSH can be configured to prevent the running of scripts with a .VBS extension. a Right click My Computer on your desktop and click Open→Tools→ Folder Options→File Types. b Look for the VBS file extension and ensure that File Types is set to VBScript Script File.
Table 11-1.
For Red Hat Enterprise Linux, the dependent RPM files are on the Red Hat Enterprise Linux installation CD.
Table 11-2.
Table 11-3. Names of the Directories Under the srvadmin/linux/custom/ Directory Name of RPM Other Server Administrator RPMs required Description srvadmin-base — This is the core code for Server Administrator. It provides motherboard alerts and contains the CLI that allows for monitoring and control of Server Administrator, for example, omconfig, omdiag, and omreport.
Table 11-3. Names of the Directories Under the srvadmin/linux/custom/ Directory (continued) Other Server Administrator RPMs required Name of RPM Description srvadmin-isvc Server Administrator Instrumentation Service — srvadmin-omilcore, Server Administrator provides a suite of srvadmin-deng, and systems management information for keeping srvadmin-hapi supported systems on your network healthy.
Table 11-3. Names of the Directories Under the srvadmin/linux/custom/ Directory (continued) Other Server Administrator RPMs required Name of RPM Description srvadminomhip Server Administrator Instrumentation Service srvadmin-omilcore, Integration Layer — Provides Instrumentation srvadmin-deng, CLI.
Table 11-3. Names of the Directories Under the srvadmin/linux/custom/ Directory (continued) Name of RPM Description Other Server Administrator RPMs required srvadminracvnc RAC VNC Remote Service and Remote Services Server Agent. srvadmin-omilcore and srvadmin-racser add-RAC4 — Software for remote management of fourth generation Remote Access Controllers. For example: DRAC 4. srvadmin-rac4- Remote Access Card Data Populator — components Remote Access Controller components.
Table 11-3.
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-SLES9 — Provides OpenIPMI support for SUSE Linux Enterprise Server (version 9) 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.
Table 11-4. Daemons that run on Red Hat Enterprise Linux and SUSE Linux Enterprise Server once Server Administrator is started Daemon Name Name in Red Hat Enterprise Linux and SUSE Linux Enterprise Server For RPMs in the srvadmin-base directory dsm_sa_datamgr DSM SA Data Manager — Server Administrator data manager 32d daemon started by DSM SA Data Engine service. dsm_sa_eventmg DSM SA Event Manager — Server Administrator event and r32d logging daemon started by DSM SA Data Engine service.
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.
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, 181 access read-only, 37 write, 37 ATA, 19 access control, 36 Active Directory, 23, 36, 39, 46, 48, 164, 169, 178, 186-187 object identifiers, 163 objects, 165 schema, 170 schema extender utility, 170-171 schema extensions, 163 ADDLOCAL, 89, 118 administrator, 37 Administrator Pack, 179 Administrator privileges, 37, 101 agent, 57 SNMP, 48 agents, 18 AGP, 213 alert filters, 16 alert log, 21 Altiris, 124, 161 ASCII, 213 association, 182 Association Object, 164, 181 attribute, 2
C CA, 64, 184-185 Certificate, 188 certificates Web, 64 certification, 22 Certification Authority, 64, 184-185 custom unattended installation, 83 D DAT, 215 data redundancy, 19 dB, 215 chip, 214 DCOM, 25, 30 CI/O, 214 Dell, 96, 163 CIM, 21, 36, 44, 50, 99 Dell base OID, 163 CIM protocol, 91 Dell OpenManage, 200 Citrix, 105 Dell organizational unit, 170 CLI, 21, 38, 118, 197 Dell Remote Access Controller, 165 cm, 214 command line, 119 command line interface, 21, 38 Common Information Model, 21
domain, 46 G domain controller, 182, 184-185 Globally Unique Identifier (GUID), 119 DRAC, 21, 179, 184-186 DRAC 4, 184, 186, 188-189, 204 controller, 21 SSL certificate, 184-185 DRAC 5 controller, 21 group privileges, 37 GUID, 110 H DRAC III, 22, 204 XT, 22 help, 22 DRAC III/XT, 22 HTTP, 25-26, 31-32, 34-35 drivers, 14 HTTPS, 24, 28, 30-32, 34-35, 39 hot spares, 19 Dynamic Kernel Support, 42, 134 I E encryption, 36 ERA, 22 ERA/MC, 22 ERA/O, 22 ESX Server, 160 express setup, 43, 74 Extraction
J L Microsoft Active Directory, 23, 36, 39, 46, 48, 178 Software Installer, 110 Windows Installer Engine, 73 Windows Server 2003, 200 Windows Small Business Server, 42, 66, 97 language, 197 MMC, 180-181, 183 LDAP, 24, 27, 34, 175 modular system, 22 LDAPS, 33-35 modular systems, 19 LDIF script file, 170 MOF, 21 LinkID, 163 monitored systems, 18 logs, 18 monitoring, 11 Java Secure Socket Extension, 39 JSSE, 39 Mozilla Firefox, 44 MSI, 110, 199 M managed system, 11-12, 44 msiexec.
O Q oem.
RMC, 24, 28 serial console, 17 RMCP, 24 serial port, 17 role-based access control, 36 authority, 23 serial-over-LAN proxy, 17 Root CA, 182 RPC, 24, 27, 29 Server Administrator, 18, 20, 168, 204 Services, 147, 202 RPM, 131, 147, 154, 202 Server Update Utility, 20 rpms, 158 session timeout, 63 S setup custom, 74 express, 43, 74 SAS, 19 setup.
socket connection, 39 U software updates, 16 UDP, 26 SOL, 17 unattended installation, 80, 112 SOL Proxy, 17 unattended uninstallation, 122 SSH, 26, 29 universal groups, 181 SSL, 39, 169, 182-183 update packages, 22 SSL encryption, 23 standard action, 109 updates, 20 software, 16 storage management, 38 upgrade, 45, 77, 200 Storage Management Service, 19, 202 user, 37 Subscription Kit, 15 user levels, 38 SUU, 20 user privileges, 46 SysMgmt.
Windows Installer Engine, 114 Installer Service, 110 Windows Management Instrumentation, 44, 99 Windows Server 2003, 200 WMI, 44, 50, 99 write access, 37 X X.
