Dell™ OpenManage™ Version 5.5 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. © 2008 Dell Inc. All rights reserved. Reproduction of these materials in any manner whatsoever without the written permission of Dell Inc. is strictly forbidden.
Contents 1 Introduction . Overview . . . . . . . . . . . . . . . . . . . . . . 11 . . . . . . . . . . . . . . . . . . . . . . . . 11 . . . . 12 . . . . . . . . . . . . . 12 . . . . . . . . . . . . . . . 13 Systems Management Software Overview What’s New in Version 5.5 Dell OpenManage Systems Management Software . . Dell Systems Management Tools and Documentation DVD . . . . . Dell Server Updates DVD . . . . . . . . . 13 . . . . . . . . . . . . .
2 Dell OpenManage Security . . . . . . . . . . . 23 . . . . . . . . . . . . . . . . . . . . 23 . . . . . . . . . . . . . . . . 23 . . . . . . . . . . . . . . . . . . . . . . . . 23 . . . . . . . . . . . . . . . . . . 38 . . . . . . . . . . . . . . . . . . . . . . . . 38 . . . . . . . . . . . . . 40 Security Features Built-in Security Features Ports Security Management RBAC Microsoft Active Directory Authentication Protocols for Linux Operating Systems . . 3 . . . . . . . . . . . .
Configuring the SNMP Agent . . . . . . . . . . . . . . Configuring the SNMP Agent for Systems Running Supported Windows Operating Systems . . . . . . . . . . . . . . . . . 51 . . . . . . . 55 . . . . . . . . . 61 Configuring the SNMP Agent on Systems Running Supported Red Hat Enterprise Linux Operating Systems . Configuring the SNMP Agent on Systems Running Supported SUSE Linux Enterprise Server Operating Systems . . . . . . . . Secure Port Server and Security Setup . . . . . . . . . 64 . . . .
Enabling CIM Discovery and Security in IT Assistant . . . . . . . . . . . . Installing SNMP . . . . . . . 72 . . . . . . . . . . . . . . . . . . 73 Installing, Upgrading, and Uninstalling Management Station Software on Systems Running Supported Windows Operating Systems . . . . . . . . . . . . . . . . . . . . 73 Installing and Upgrading Management Station Software . . . . . . . . . . . . Typical and Custom Installations . . . . . . . 74 . . . . . . . . . 74 . . . . . . . . . . . . . . . . .
Installing, Upgrading, and Uninstalling Management Station Software on Systems Running Supported Red Hat Enterprise Linux and SUSE Linux Enterprise Server Operating Systems . . . . . . . . . . . . . . . . 92 Installing Management Station Software . . . . . . . . . . . . . . . . . . 92 Upgrading Management Station Software . . . . . . . . . . . . . . . . . . 94 Uninstalling Management Station Software . . . . . 6 . . . . . . . . . . . . .
Installation Procedures . . . . . . . . . . . . . . . . . Prerequisites for Installing or Upgrading Server Administrator . . . . . . . . . . . Installing and Upgrading Server Administrator . . . . . . . 102 . . . . . . . . . . . . . . 104 . . . . . . 111 . . . . . . . . . . . . . . . . . . . 112 Windows Installer Logging . . . . . . . . . . . . . 112 Upgrading the MSI Engine . . . . . . . . . . . . .
8 Installing Managed System Software on Supported Linux Operating Systems . . Overview . . . . . . . . . 133 . . . . . . . . . . . . . . . . . . . . . . . . Unattended and Scripted Silent Installation . . . . . . . . . . . Before You Begin 133 . . . . . . . . . . 134 . . . . . . . . . . . . . . . . . . . . 134 Installation Requirements . . . . . . . . . . . . . . . . 134 . . . . . . . . . . . 134 . . . . . . . . . . . . . . . 135 . . . . . . . . . . . . . . . . . 136 . . . . . . . . . .
9 Using Microsoft Active Directory 163 . . . . . . . 163 . . . . . . . . 170 . . . . . . . . . . 171 . . . . . . . . . . . . 178 Active Directory Schema Extensions Extending the Active Directory Schema Using the Dell Schema Extender Adding Users and Privileges to Active Directory . . . . . . . . . . . . . . . . . . 179 . . . . . . . 185 Configuring Your Systems or Devices 10 Prerequisite Checker . . . . . . . . . . . . . . Command Line Operation of the Prerequisite Checker . . . . . . .
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.
Systems Management Software Overview Dell OpenManage systems management software is a suite of applications for your Dell systems. This software enables you to manage your systems with proactive monitoring, diagnosis, notification, and remote access. 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.
• Added support for Citrix® XenServer 4.2 Dell Edition . • Added support for Microsoft Hyper-V™ and Hyper-V Server. • Added support for the following Dell systems: M805, M905, T100, and DL2000. For more information, see the Dell OpenManage website at www.dell.com/openmanage. Dell OpenManage Systems Management Software The Dell OpenManage systems management software kit is available in the form of the Dell Systems Management Tools and Documentation DVD.
• docs: 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. NOTE: The Dell Systems Management Tools and Documentation DVD contains version 5.5 of the Dell OpenManage systems management software kit and version 1.0.7 of the Dell Systems Build and Update Utility.
Management Station Software IT Assistant IT Assistant is a browser-based, graphical user interface (GUI) that provides a central point of access to monitor and manage systems on a local area network (LAN) or a wide area network (WAN). By providing a comprehensive view across the enterprise, IT Assistant can increase system uptime, reduce repetitive tasks, and prevent interruption during critical business operations.
Dell Remote Access Controller Console The Dell Remote Access Controller (DRAC) console is a management station software designed to provide remote management capabilities for your Dell systems.
• Text console redirection for system setup, text-based utilities, and operating system consoles • Access to Red Hat Enterprise Linux and SUSE Linux Enterprise Server serial console interfaces using SOL • IPMItool: The ipmitool program provides a simple command-line interface to BMC and features the ability to read the sensor data repository (SDR) and print sensor values, display the contents of the System Event Log (SEL), print Field Replaceable Unit (FRU) inventory information, read and set LAN confi
Remote Access Service The Remote Access Service provides the following features: • Remote access to an unresponsive system, allowing you to shut down, restart, and get the system up and running as quickly as possible • Alert notification when a system is down • System crash logs that record the probable cause of system crashes and saves the most recent crash screen You must have Server Administrator on your system to install the Remote Access Service.
Diagnostics Dell Online Diagnostics is a suite of diagnostic programs, or test modules, that run locally on your system. Using Online Diagnostics, you can select the appropriate diagnostics tests to run on the hardware that Online Diagnostics discovers on your system. Drivers The Extraction Utility enables you to view and create Dell software driver and diagnostic floppy disks.
• The Dell OpenManage Server Administrator User's Guide describes the installation and use of Server Administrator. Server Administrator provides easy-to-use management and administration of local and remote systems through a comprehensive set of integrated management services.
• The Dell Remote Access Controller 4 User’s Guide provides complete information about installing and configuring a DRAC 4 controller and using DRAC 4 to remotely access an inoperable system. • The Dell Remote Access Controller 5 User’s Guide provides complete information about installing and configuring a DRAC 5 controller and using DRAC 5 to remotely access an inoperable system.
Obtaining Technical Assistance If at any time you do not understand a procedure described in this guide, or if your product does not perform as expected, different types of help are available. For more information, see "Getting Help" in your system's Hardware Owner’s Manual. Additionally, Dell Enterprise Training and Certification is available; see www.dell.com/training for more information. This service might not be offered in all locations.
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 Direction Usage Encryption Level Configurable 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 Yes incoming Telnet connections 623 RMCP UDP 1.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Type 1024 65535 (Dynamically assigned) DCOM Version Maximum Direction Usage Encryption Level TCP/ 2.0 UDP None In/Out Viewing of client management data Configurable Port range can be restricted. Dell OpenManage Client Instrumentation 20 HTTP TCP 7.x and FTP None In/Out Flash BIOS No communication 21 HTTP TCP 7.x and FTP None In/Out Flash BIOS No communication 80 HTTP TCP 7.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Type Version Maximum Direction Usage Encryption Level Configurable Dell OpenManage IT Assistant 22 SSH TCP 7.x 128-bit In/Out IT Assistant contextual application launch—SSH client Yes Remote software updates to Server Administrator— for systems supporting Linux operating systems Performance monitoring in Linux systems 23 Telnet TCP 7.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Type 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/ 7.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Type 389 LDAP 1433 Version Maximum Direction Usage Encryption Level 128-bit In/Out Domain No authentication for IT Assistant log on Proprieta TCP 7.x ry None In/Out Optional remote Yes SQL server access 2606 Proprieta TCP 7.x ry None In/Out Network Yes monitoring service communication port 2607 HTTPS TCP 7.x 128-bit SSL In/Out IT Assistant Web GUI 3389 RDP TCP 7.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Type 6389 Proprieta TCP 8.0 ry Version Maximum Direction Usage Encryption Level None Configurable In/Out Enables No communication between a host system (through NaviCLI/NaviSe cCLI or Navisphere Host Agent) and a Navisphere Array Agent on a Storage system. Dell OpenManage Server Administrator 22 SSH TCP 2.0 128-bit In/Out Remote Server Yes Administrator Command Line (for IT Assistant).
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Type 135 RPC TCP/ 2.0 UDP None In/Out Remote Server No Administrator Command Line (for IT Assistant). Remote software update feature (for Windows operating systems). 139 NetBIOS TCP 2.0 None In/Out Remote Server No Administrator Command Line (for IT Assistant). Remote Software Update (for Windows operating systems). 161 SNMP UDP 1.x, 2.0 None In/Out SNMP query management No 162 SNMP UDP 1.x, 2.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Type 1311 HTTPS TCP 1.x 128-bit SSL In/Out Web GUI Yes 11487 Proprietary UDP 1.x None In Remote Flash BIOS update initiation from IT Assistant Yes 11489 Proprietary TCP 1.x None In Remote Flash BIOS update file transfer from IT Assistant Yes 1024 65535 DCOM TCP/ 2.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Type 69 TFTP UDP 1.0 None In/Out Firmware No update through Trivial FTP. Remote floppy boot through TFTP 80 HTTP TCP 1.0 None In/Out Web GUI redirected to HTTPS No 162 SNMP UDP 1.0 None Out SNMP trap event No 443 HTTPS TCP 1.0 128-bit SSL In/Out Web management GUI No 443 HTTPS TCP 3.2 128-bit SSL In/Out Remote racadm No CLI utility 5869 Proprieta TCP 1.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Type Version Maximum Direction Usage Encryption Level Configurable DRAC 4 22 SSHv2 TCP 1.30 128-bit In/Out Optional Secure Yes 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 No alert messages 53 DNS UDP 1.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Type 443 HTTPS TCP 1.0 128-bit SSL In/Out Web Yes management GUI and remote racadm CLI utility 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 Proprieta TCP 1.0 ry None In/Out CD/diskette virtual media service Yes 5869 Proprieta TCP 1.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Type 68 DHCP UDP 1.0 None In/Out DHCP assigned No IP address 69 TFTP UDP 1.0 None In/Out Firmware No update through Trivial FTP 80 HTTP TCP 1.0 None In/Out Web GUI redirected to HTTPS Yes 161 SNMP UDP 1.0 None In/Out SNMP query management No 162 SNMP UDP 1.0 None Out SNMP trap event No 389 LDAP TCP 1.0 None In/Out Optional ADS authentication No 443 HTTPS TCP 1.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Type 25 SMTP TCP 1.0 None In/Out Optional e-mail No alert messages 53 DNS UDP 1.0 None In/Out Dynamic DNS No registration of host name assigned within DRAC 68 DHCP UDP 1.0 None In/Out DHCP assigned No IP address 69 TFTP UDP 1.0 None In/Out Firmware No update through Trivial FTP 80 HTTP TCP 1.0 None In/Out Web GUI redirected to HTTPS Yes 161 SNMP UDP 1.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Type 3669 Proprietary Version Maximum Direction Usage Encryption Level Configurable TCP 1.0 128-bit SSL In/Out Virtual Media Secure Service Yes 5900 TCP 1.0 128-bit SSL Out Console Redirection: Video Yes 5901 TCP 1.0 128-bit SSL In Console Yes Redirection: keyboard/mouse Digital KVM 2068 Proprietary TCP 1.
Security Management Dell provides security and access administration through role-based access control (RBAC), authentication, and encryption, or through Active Directory (or through Winbind, Kerberos, LDAP, or NIS on Linux operating systems) for both the Web-based and command line interfaces. RBAC RBAC manages security by determining the operations that can be executed by users in specific roles.
Table 2-2. User Privileges User Privileges Access Type Admin Write Read User X Power User Administrator X X X X X Admin access allows you to shut down the managed system. Write access allows you to modify or set the values on the managed system. Read access allows you to view the data reported by Server Administrator. Read access does not allow you to change or set the values on the managed system.
Authentication The Server Administrator authentication scheme ensures that the access types are assigned to the correct user privileges. Additionally, when you invoke the CLI, the Server Administrator authentication scheme validates the context within which the current process is running. This authentication scheme ensures that all Server Administrator functions, whether accessed through the Server Administrator home page or CLI, are properly authenticated.
remote management authentication and authorization. IT Assistant, Server Administrator, and Dell remote access controllers can interface with Active Directory to add and control users and privileges from one central database. For information about using Active Directory, see "Using Microsoft Active Directory." Authentication Protocols for Linux Operating Systems Dell OpenManage applications (version 5.
Dell OpenManage Security
Setup and Administration Before You Begin • Read the Installation Requirements to ensure that your system meets or exceeds the minimum requirements. • Read the 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.
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.
Supported Web Browser Requirements For supported web browser requirements, see the Dell Systems Software Support Matrix located at docs directory on the Dell-provided media or on the Dell support website at support.dell.com. Supported Systems Management Protocol Standards A supported systems management protocol must be installed on the managed system before installing your management station or managed system software.
Dependencies and Prerequisites Upgrading Dell OpenManage Software Versions 1.x through 4.2 Upgrades from Dell OpenManage software versions 1.x through 4.2 are not supported. You must manually uninstall Dell OpenManage software versions 1.x through 4.2 before launching the latest Dell OpenManage software installation. The installer will notify you if it detects Dell OpenManage software versions 1.x through 4.2 on the system. Another way of upgrading from these versions is to upgrade to version 4.
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. New users can log into the Dell OpenManage software using their operating system user privileges. NOTICE: To protect access to your critical system components, you must assign a password to every user account that can access the Dell OpenManage software.
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. To create users with User and Power User privileges, perform the following steps.
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.
You can configure the SNMP agent to change the community name, enable Set operations, and send traps to a management station. To configure your SNMP agent for proper interaction with management applications such as IT Assistant, perform the procedures described in the following sections. NOTE: The default SNMP agent configuration usually includes an SNMP community name such as public. For security reasons, change the default SNMP community names.
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.
Configuring Your System to Send SNMP Traps to a Management Station The Dell OpenManage software generates SNMP traps in response to changes in the status of sensors and other monitored parameters. You must configure one or more trap destinations on the Dell OpenManage software system for SNMP traps to be sent to a management station. 1 Open the Computer Management window. 2 Expand the Computer Management icon in the window, if necessary. 3 Expand the Services and Applications icon and click Services.
Configuring the SNMP Agent on Systems Running Supported Red Hat Enterprise Linux Operating Systems Server Administrator uses the SNMP services provided by the ucd-snmp or net-snmp agent. You can configure the SNMP agent to change the community name, enable Set operations, and send traps to a management station. To configure your SNMP agent for proper interaction with management applications such as IT Assistant, perform the procedures described in the following sections.
The second change is to modify the default access line to give read-only access to the entire MIB tree for the public community. Server Administrator looks for the following line: access notConfigGroup "" any noauth exact systemview none none If Server Administrator encounters this line, it modifies the line as follows: access notConfigGroup "" any noauth exact all none none These changes to the default SNMP agent configuration give read-only access to the entire MIB tree for the public community.
To change the SNMP community name used for retrieving management information from a system running Server Administrator, edit the SNMP agent configuration file, /etc/snmp/snmpd.conf, and perform the following steps: 1 Find the line that reads: com2sec publicsec default public or com2sec notConfigUser default public 2 Edit this line, replacing public with the new SNMP community name.
To enable SNMP Set operations on the system running Server Administrator, edit the /etc/snmp/snmpd.conf SNMP agent configuration file and perform the following steps: 1 Find the line that reads: access publicgroup "" any noauth exact all none none or access notConfigGroup "" any noauth exact all none none 2 Edit this line, replacing the first none with all.
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.
Best Practices for X.509 Certificate Management To ensure that the security of your system is not compromised while using server administrator, you should keep in mind the following: • Unique host name: All systems that have server administrator installed should have unique host names. • Change 'localhost' to unique: All systems with host name set to 'localhost' should be changed to a unique host name.
Setup and Administration
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.
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.
Installing Management Station Software Overview The Dell Systems Management Tools and Documentation DVD provides a setup program to install, upgrade, and uninstall Dell™ OpenManage™ management station software on your system. Using the setup program you can install and upgrade the management station software on systems running Microsoft® Windows® operating systems.
Supported Operating Systems For a list of the operating systems that the Systems Build and Update Utility supports, see the Dell Systems Software Support Matrix located at docs directory on the Dell-provided media or on the Dell support website at support.dell.com. For more application-specific operating systems requirements, see the documentation for that application. System Requirements On Windows systems, the setup program (setup.
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. If you attempt to install the IT Assistant on a system without SNMP, the installation program stops and prompts you to install SNMP. In addition, if you stop the SNMP service, the IT Assistant services also stop.
• An error message describes a condition that prevents the software feature from being installed. You must resolve the condition causing the error before proceeding with the installation of that software feature. If you do not resolve the issue, the software feature will not be installed. Execute the command RunPreReqChecks.exe /s if you want to run the prerequisite check in silent mode. For more information see "Prerequisite Checker.
If the prerequisites are met, IT Assistant, the DRAC Tools, and BMC Utilities are installed by default. The Active Directory Snap-in Utility is not selected by default and can be installed using the Custom Setup option. For more information about how to perform a Typical Setup, see the Software Quick Installation Guide, which you can access by clicking Info on the task bar within the setup program.
Installing Management Station On Microsoft Windows operating systems, an autorun utility appears when you insert the Dell Systems Management Tools and Documentation DVD in your system’s DVD drive. The autorun utility allows you to choose the systems management software you want to install on your system. NOTE: IT Assistant requires a default instance of a database to be installed on the system. IT Assistant cannot use a named instance of a database.
8 Select Custom and click Next. The Custom Setup dialog box appears. To select a specific management station software application, click the drop-down arrow beside the listed feature and select to either install or not to install the application. A selected feature has a hard drive icon next to it. A deselected feature has a red X next to it. By default, if the Prerequisite Checker finds software features with no supporting hardware or software, the Checker deselects them.
Upgrade The Dell OpenManage installer provides an Upgrade option for upgrading IT Assistant and other management station software. When you insert the Dell Systems Management Tools and Documentation DVD into your system's DVD drive, select Dell OpenManage Management Station from the autorun menu, and click Install. The Prerequisite Checker program checks your system.
Upgrade Using the Windows Installer Patch File You can upgrade your management station software using the Windows Installer Patch (.MSP) file. The MSP file is available on the Dell Support website at support.dell.com. To apply the MSP file, either double-click on the MSP file or type the following command in your command-prompt window: msiexec.exe /p filename.msp NOTE: You can use other msiexec parameters like "/q" for silent upgrades. Modify 1 Navigate to the Windows Control Panel.
Repair 1 Navigate to the Windows Control Panel. 2 Double-click Add/Remove Programs. 3 Click Dell OpenManage Management Station and click Change. The Welcome to the Install Wizard for Dell OpenManage Management Station dialog box appears. 4 Click Next. The Program Maintenance dialog box appears. 5 Select the Repair option and click Next. The Ready to Repair the Program dialog box appears. 6 Click Install to install the selected software features.
An installation cannot be rolled back once it has successfully completed. A transacted installation is intended as a safety net that protects the system during a given installation session. If you want to remove an installed application, for example, you should uninstall that application. When upgrading from Dell OpenManage software version 4.3 to version 5.x, an error will roll back the system to its previous state.
Creating and Distributing the Typical Unattended Installation Package The Typical Setup unattended installation option uses the Dell Systems Management Tools and Documentation DVD as the unattended installation package. The msiexec.exe /i MgmtSt.msi /qb command accesses the DVD to accept the software license agreement and install all required management station software products on selected remote systems. The msiexec.exe /i MgmtSt.
3 Configure your ISV distribution software to distribute and execute the script created in step 2. 4 Distribute this script to the target systems by using your ISV software distribution tools. The msiexec.exe /i MgmtSt.msi /qb command installs management station on each remote system. NOTE: IT Assistant requires a supported database to be installed before IT Assistant can be installed. See DVD drive:\SYSMGMT\ManagementStation\Windows\ManagementStat ion\support\ to find the sample batch file and the necessar
Distributing Custom Unattended Installation Packages NOTE: The MgmtSt.msi installation package for management station used in the Custom Setup unattended installation as described in the previous section is located in the SYSMGMT\ManagementStation\windows\ManagementStation on the Dell Systems Management Tools and Documentation DVD. 1 Configure your ISV distribution software to execute the batch script once your installation package has been distributed.
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.com for full details of all the Microsoft Windows Installer command line switches. Table 5-1. Command Line Settings for MSI Installer Setting Result Installs or configures a product. /i
Table 5-1. Command Line Settings for MSI Installer (continued) Setting Result /f[p|o|e|d|c|a|u Repairs a product. |m|s|v] /fp – This option reinstalls a product only if a file is /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.
Uninstalling Management Station Software You can uninstall the management station software by using the Dell Systems Management Tools and Documentation DVD, or your operating system. Additionally, you can perform unattended uninstallations on multiple systems. Uninstall Management Station Software Using the Dell-provided Media To uninstall the management station software using the DVD, perform the following steps: 1 Insert the DVD into your system's DVD drive.
Uninstalling Management Station Software Features Using Add/Remove Programs To uninstall the management station software features using Windows, perform the following steps: 1 Navigate to the Windows Control Panel. 2 Double-click Add/Remove Programs. 3 Click Dell OpenManage Management Station and click Remove. The Add or Remove Programs question box appears. 4 Click Yes to confirm uninstallation of management station. The Uninstall Summary screen appears.
Distributing the Unattended Uninstallation Package The Dell Systems Management Tools and Documentation DVD is preconfigured to act as the unattended uninstallation package. To distribute the package to one or more systems, perform the following steps: 1 Configure your ISV distribution software to execute the msiexec.exe /x DVD Drive\SYSMGMT\ManagementStation\windows\Managemen tStation\MgmtSt.msi /qb command after the unattended uninstallation package has been distributed.
Customization Parameters The ADDLOCAL, REINSTALL, and REMOVE CLI parameters provide a way to specify the exact software features to install, reinstall, or uninstall when running silently or unattended. With the customization parameters, you can selectively install, reinstall, or uninstall software features for different systems using the same unattended installation package.
The REMOVE customization parameter can be included on the command line and assigned the feature ID (or IDs) of the software feature that you would like to uninstall. An example is msiexec.exe /i MgmtSt.msi REMOVE=RACMS /qb This command runs only the installation for management station and uninstalls Remote Access Controller management station, in an unattended and verbose mode. You can also choose to install, reinstall, and uninstall features with one execution of the msiexec.exe program.
Include Ranges. Click New Include Range to run the New Discovery Wizard, where you can specify the new CIM user name in the CIM Configuration window. See the IT Assistant online help for additional information. Other Known Issues for Microsoft Installations • Directories might be left behind during an uninstall for reasons such as sharing violations or open user interface connections. It is recommended that you close all open interface sessions before you perform an uninstallation.
To install the BMC Management Utility onto a management station, perform the following steps: 1 Log on as root to the system on which you want to install the management station features. 2 If necessary, mount the Dell Systems Management Tools and Documentation DVD to a desired location using the mount command or a similar command.
Upgrading Management Station Software To upgrade the BMC Management Utility onto a management station, perform the following steps: 1 Log on as root to the system on which you want to upgrade the management station features. 2 If necessary, mount the Dell Systems Management Tools and Documentation DVD to a desired location using the mount command or a similar command.
Uninstalling Management Station Software To uninstall the BMC Management Utility onto a management station, perform the following steps: 1 Log on as root to the system where you want to install the management station features. 2 Use the rpm query command to determine which version of the BMC Management Utility is installed. Use the rpm -qa | grep osabmcutil command. 3 Verify the package version to be uninstalled and uninstall the feature by using the rpm -e `rpm -qa | grep osabmcutil` command.
Installing Management Station Software
Installing Managed System Software on Microsoft Windows Operating Systems Overview The Dell Systems Management Tools and Documentation DVD provides a setup program to install, upgrade, and uninstall managed system software components on your managed systems. You can install these software components on multiple systems through an unattended installation across a network.
Unattended and Scripted Silent Installation You can use the Dell Systems Management Tools and Documentation DVD to perform an unattended and scripted silent installation of the managed system software on systems running supported Windows operating systems. Additionally, you can install and uninstall the features from the command line on systems running supported Windows operating systems.
Installation Requirements The following sections describe the general requirements for Server Administrator. Supported Operating System For supported operating systems, see the Dell Systems Software Support Matrix located at docs directory on the Dell-provided media or on the Dell support website at support.dell.com.
• A mouse, keyboard, and monitor to manage a system locally. The monitor must have a minimum screen resolution of 800 x 600. The recommended screen resolution setting is 1024 x 768. • The Server Administrator Remote Access Service requires that a remote access controller (RAC) be installed on the system to be managed. See the Dell Remote Access Controller 4 User’s Guide or the Dell Embedded Remote Access Controller/MC User's Guide for complete software and hardware requirements.
Windows Server 2003 R2 and the R2 IPMI Device Driver The information in this section is applicable only to PowerEdge x8xx, x9xx, xx0x, and PowerVault x00 systems. Windows Server 2003 R2 and Windows Storage Server R2 contain an optional component called Hardware Management. This component contains an IPMI driver. During installation, the component installs and enables its IPMI driver.
Server Administrator can switch over from using the Windows Server 2003 R2 IPMI driver to using its own internal IPMI support. To restart the service, you can either manually restart the service or reboot the system. Digital Certificates All Server Administrator packages for Microsoft are digitally signed with a Dell certificate that helps guarantee the integrity of the installation packages. If these packages are repackaged, edited, or manipulated in other ways, the digital signature will be invalidated.
Prerequisite Checker The setup program starts the Prerequisite Checker program. The setup program is located in the \SYSMGMT\srvadmin\windows directory on the Dell Systems Management Tools and Documentation DVD. The Prerequisite Checker program examines the prerequisites for software components without launching the actual installation.
Installing and Upgrading Server Administrator This section explains how to install and upgrade the Server Administrator using two installation options: • Use the setup program at \SYSMGMT\srvadmin\windows on the Dell Systems Management Tools and Documentation DVD to install or upgrade Server Administrator and other managed system software. • Use the unattended installation method through the Windows Installer Engine msiexec.
When you select the Custom Setup option, you can deselect one or more software features that the install program has identified as appropriate for the installed options on the system. During a Typical Setup, you cannot add to the list of features to install because all the features that are appropriate for the hardware configuration are preselected. The Server Administrator Storage Management Service is installed by default during Typical Setup.
7 Click Accept and Next if you agree. The Setup Type dialog box appears. 8 Select Custom and click Next. The Custom Setup dialog box appears. To select a specific managed system software application, click the drop-down arrow beside the listed feature. A selected feature has a hard drive icon depicted next to it. A deselected feature has a red X depicted next to it. By default, if the Prerequisite Checker finds a software feature with no supporting hardware, the checker deselects them.
Server Administrator Installation With Citrix Application Server Citrix remaps all your hard drive letters when installed. For example, if you install Server Administrator on drive C: and then install Citrix, it may change your drive letter C: to M:. Server Administrator may not work properly because of the remapping. In order to avoid this problem, select one of these options: Option 1: 1 Uninstall Server Administrator. 2 Install Citrix. 3 Reinstall Server Administrator.
Upgrade 1 Insert the Dell Systems Management Tools and Documentation DVD into your system's DVD drive. The autorun menu appears. 2 Select Dell OpenManage Server Administrator and click Install. If the autorun program does not start automatically, go to the SYSMGMT\srvadmin\windows directory on the DVD, and run the setup.exe file. The Dell OpenManage Server Administrator prerequisite status screen appears and runs the prerequisite checks for the managed station.
Upgrade Using the Windows Installer Patch File You can upgrade your Managed System software using the Windows Installer Patch (.MSP) file. The MSP file is available on the Dell Support website at support.dell.com. To apply the MSP file either double-click on the MSP file or enter the following command in your command-prompt window: msiexec.exe /p filename.msp NOTE: You can use other msiexec parameters like "/q" for silent upgrades. Modify 1 Navigate to the Windows Control Panel.
8 Click Install to install the selected software features. The Installing Dell OpenManage Server Administrator screen appears. Messages give 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 exit the Server Administrator installation. If you are prompted to reboot your system, you must do so to make the installed managed system software services available for use.
6 Click Install to install the selected software features. The Installing Dell OpenManage Server Administrator 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. 7 Click Finish to exit the Server Administrator installation. If you are prompted to reboot your system, select a reboot option: • Yes, reboot my system now. • No, I will reboot my system later.
An installation cannot be rolled back once it has finished; transacted installation is only intended as a safety net that protects the system during an installation session. If you want to remove an installed application, for instance, you should simply uninstall that application. NOTE: Driver installation and removal is not executed as part of the installation transaction and therefore cannot be rolled back if a fatal error occurs during execution.
a - Startup of actions r - Action-specific records m - Out-of-memory or fatal exit information u - User requests p - Terminal properties + - Append to existing file ! - Flush each line to the log "*" - Wildcard, log all information except for the v option. To include the v option, specify "/l*v". Once activated, you can find the log files that are generated in your %TEMP% directory. Some log files generated in this directory are: • Managed System Installation – • SysMgmt.
goto retry ) if %errorlevel% == 1638 ( REM THIS IS A MINOR UPGRADE start /wait msiexec /i SysMgmt.msi REINSTALL=ALL REINSTALLMODE=vomus/qn ) Performing an Unattended Installation of Managed System Software The Dell OpenManage installer features a Typical Setup option and a Custom Setup option for the unattended installation procedure. Unattended installation enables you simultaneously to install Server Administrator on multiple systems.
Mapping a Drive to Act as the Typical Unattended Installation Package 1 Share an image of the Dell Systems Management Tools and Documentation DVD with each remote system on which you want to install Server Administrator. You can accomplish this task by directly sharing the DVD or by copying the entire DVD to a drive and sharing the copy. 2 Create a script that maps a drive from the remote systems to the shared drive described in step 1. This script should execute msiexec.exe /i Mapped Drive\SYSMGMT\srvadmi
Creating and Distributing Custom Unattended Installation Packages To create a custom unattended installation package, perform the following steps: 1 Copy the SYSMGMT\srvadmin\windows directory from the DVD to the system hard drive. 2 Create a batch script that will execute the installation using the Windows Installer Engine (msiexec.exe). NOTE: For Customized Unattended Installation, each required feature must be included as a command line interface (CLI) parameter for it to be installed.
Unattended Installation Features Unattended installation provides the following features: • A set of optional command line settings to customize an unattended installation • Customization parameters to designate specific software features for installation • A Prerequisite Checker program that examines the dependency status of selected software features without having to perform an actual installation Optional Command Line Settings Table 6-1 shows the optional settings available for the msiexec.
Table 6-1. Command Line Settings for MSI Installer (continued) Setting Result /i SysMgmt.msi REINSTALL=ALL REINSTALLMODE= vomus /qn This commands carries out a minor upgrade, say from version 4.3 to version 4.4. You have to update your MSI engine before running this command if you are using a system running Windows 2000 Server, or Windows XP operating system. See "Upgrading the MSI Engine" for information on upgrading the MSI engine and installing/upgrading systems management software.
Table 6-1. Setting Command Line Settings for MSI Installer (continued) Result /f[p|o|e|d|c|a|u This command repairs a product. |m|s|v] missing. /fo – This option reinstalls a product if a file is missing or if an older version of a file is installed. /fe – This option reinstalls a product if a file is missing or an equal or older version of a file is installed.
Customization Parameters NOTE: Type the ADDLOCAL, REINSTALL, and REMOVE CLI parameters in upper case, as they are case-sensitive. ADDLOCAL, REINSTALL, and REMOVE customization CLI parameters provide a way to customize the exact software features to install, reinstall, or uninstall when running silently or unattended. With the customization parameters, you can selectively install, reinstall, or uninstall software features for different systems using the same unattended installation package.
You can include the REINSTALL customization parameter on the command line and assign the feature ID (or IDs) of the software feature that you would like to reinstall. An example is msiexec.exe /i SysMgmt.msi REINSTALL=BRCM /qb. This command will run the installation for Dell OpenManage Systems Management and reinstall only the Broadcom agent, in an unattended but not silent mode.
MSI Return Code An application event log entry is recorded in the SysMgmt.log file. Table 6-3 shows some of the error codes returned by the msiexec.exe Windows Installer Engine. Table 6-3. Windows Installer Return Codes Error Code Value Description ERROR_SUCCESS 0 The action completed successfully. ERROR_INVALID_PARAMETER 87 One of the parameters was invalid. ERROR_INSTALL_USEREXIT 1602 The user canceled the installation.
Uninstalling Managed System Software Using Dell-provided Media 1 Insert the Dell Systems Management Tools and Documentation DVD into your system's DVD drive. If the setup program does not start automatically, run the setup.exe in the SYSMGMT\srvadmin\windows directory on the DVD. The Dell OpenManage Server Administrator prerequisite status screen appears and runs the prerequisite checks for the managed system. Any relevant informational, warning, or error messages detected during checking are displayed.
Uninstalling Managed System Software Features Using the Operating System 1 Navigate to the Windows Control Panel. 2 Double-click Add/Remove Programs. 3 Click Dell OpenManage Server Administrator and click Remove. The Add or Remove Programs dialog box appears. 4 Click Yes to confirm uninstallation of Server Administrator. The Dell OpenManage Server Administrator screen appears and provides the status and progress of the software features being uninstalled.
Distributing the Unattended Uninstallation Package The Dell Systems Management Tools and Documentation DVD is 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 DVD Drive\SYSMGMT\srvadmin\windows\SystemsManagement\ SysMgmt.msi /qb command, if you are using the DVD, after the unattended uninstallation package has been distributed.
Managed System Software Installation Using Third-Party Deployment Software You can use third-party deployment software, such as Altiris Deployment Solution, to install managed systems software onto supported Dell systems. To distribute and install Server Administrator using Altiris, start your Altiris application and import OpenManage_Jobs.bin located at SYSMGMT\srvadmin\support\Altiris on the Dell Systems Management Tools and Documentation DVD. Specify a job folder into which to import OpenManage_Jobs.bin.
Installing Dell OpenManage Software On Microsoft Windows Server 2008 Core and Microsoft Hyper-V Server Introduction The Server Core installation option of the Microsoft® Windows Server® 2008 and Hyper-V™ Server operating system provides a minimal environment for running specific server roles that reduces the maintenance and management requirements and the attack surface for those server roles.
Installing Managed System and Management Station Software This section provides instructions on installing managed system and management station software on Windows Server 2008 Core or Hyper-V Server operating system, in the CLI mode. Running PreReqChecker In CLI Mode Run the PreReqChecker before you install Dell OpenManage software. See "Prerequisite Checker" for more information on running Prerequisite Checker in the CLI mode.
NOTE: If you encounter a return value of 2 or 3, it is recommended that you inspect the omprereq.htm file in the windows temporary folder %TEMP%. To find %TEMP%, run the echo %TEMP% command. NOTE: omprereq.htm is an html file. Transfer this file to another computer with a browser installed to read this file. Common causes for a return value of 2 from the prerequisite checker: • One of your storage controllers or drivers has outdated firmware or driver. See firmwaredriverversions_.
• Running managed system prereqchecker on the Windows Vista® operating system. Vista is not supported for managed system software. • Running the x64 edition of Windows 2008 Core, since some of the components are disabled from being installed. Ensure that any error or warning situation is corrected before you proceed to install OpenManage software components.
Installing Managed System Software In CLI Mode 1 Ensure that all errors or warnings that PreReqChecker detects are corrected before you install managed system components. 2 Launch the MSI file from the command prompt using the command msiexec /i SysMgmt.msi The MSI file SysMgmt.msi is located at SYSMGMT\srvadmin\windows\SystemsManagement on the Dell Systems Management Tools and Documentation DVD. To install the localized version of the managed system software, type msiexec /I SysMgmt.
Installing Dell OpenManage Software on Windows Server 2008 Core
Installing Managed System Software on Supported Linux Operating Systems Overview The Dell™ OpenManage™ installer provides installation scripts and RPM packages to install, upgrade, and uninstall Dell OpenManage Server Administrator and other managed system software components on your managed system. Additionally, you can install Server Administrator on multiple systems through an unattended installation across a network. The first installation method uses the custom install script srvadmin-install.sh.
Unattended and Scripted Silent Installation You can use the Dell Systems Management Tools and Documentation DVD to perform an unattended and scripted silent installation of managed systems software through the command line (using RPM packages) on systems running supported Red Hat® Enterprise Linux® and SUSE® Linux Enterprise Server operating systems. Before You Begin • Read the installation requirements to ensure that your system meets or exceeds the minimum requirements.
System Requirements Managed systems software must be installed on each system to be managed. You can then manage each system running the managed systems software locally or remotely through a supported Web browser. Managed System Requirements • One of the supported operating system versions. • A minimum of 512 MB of RAM. • A minimum of 256 MB of free hard drive space. • Administrator rights. • A TCP/IP connection on the monitored system and the remote system to facilitate remote system management.
Installation Procedures This section explains how to install, upgrade, and uninstall Server Administrator on a system that is running a supported Red Hat Enterprise Linux or a supported SUSE Linux Enterprise Server operating system. You can install or upgrade Server Administrator using scripts from the Dell Systems Management Tools and Documentation DVD, or through RPM.
If you see the following message during Server Administrator Device Drivers startup, then Server Administrator has attempted to use its DKS feature, but was unable to use the feature because certain prerequisites were not met: Building using DKS... [FAILED] where is dcdbas or dell_rbu NOTE: Server Administrator logs messages to the /var/log/messages log file. To use DKS, identify which kernel is running on the managed system, and check the DKS prerequisites.
Using Dynamic Kernel Support After Server Administrator Installation To enable Server Administrator to support a kernel that is not supported by a precompiled device driver and is loaded after Server Administrator has been installed, perform the following steps: Ensure that the DKS prerequisites are met on the system to be managed and boot the new kernel on the system.
4 Copy any dcdbas.* or dell_rbu.* files in the /lib/modules//kernel/drivers/firmware directory on system A to the /var/omsa/dks/ directory on system B, where is the kernel name returned by typing uname -r in step 3. NOTE: The /lib/modules//kernel/drivers/firmware directory may contain one or more of the following files: dcdbas.* or dell_rbu.* NOTE: You might have to create the /var/omsa/dks/ directory on system B. For example, if the kernel name is 1.2.
Determining if the Running Kernel is Tainted After Server Administrator services have been started, perform the following steps on Red Hat Enterprise Linux Update releases to determine if the kernel has been tainted: 1 Log in as root.
This requirement is checked and enforced by Server Administrator at three instances. Two of the instances are during installation, while the third is a run-time step. The instances are: • During custom installation of Server Administrator using the srvadmin-install.sh shell script. • During installation of Server Administrator using RPM. • At run-time when the Server Administrator Instrumentation Service is started.
During installation of Server Administrator using RPM, the srvadmin-hapi RPM will check if a sufficient version of the OpenIPMI device driver is currently installed on the system. If a sufficient version is not found, the srvadmin-hapi RPM will fail to install and will display an error message stating that you must install/upgrade the OpenIPMI device driver. In such a case, RPMs that depend on the srvadmin-hapi RPM will also fail to install.
Additionally, during the installation of the srvadmin-hapi RPM using RPM, if a required version of the OpenIPMI RPM is currently installed on the system, but OpenIPMI driver modules have not been built and installed for the given version of the OpenIPMI driver (because the kernel-source RPM is required but is not currently installed,) the srvadmin-hapi RPM will fail to install and will display an error message.
To account for a user uninstalling or replacing a sufficient version of the OpenIPMI device driver after Server Administrator has been installed, the Server Administrator Instrumentation Service checks the OpenIPMI device driver version whenever it is started. If a sufficient version of the OpenIPMI device driver is not found, the Server Administrator Instrumentation Service will degrade itself so that it does not provide any of its IPMI-based information or functionality.
Prerequisites for Installing Managed System Software • You must be logged in as root. • The running kernel must have loadable module support enabled. • The /opt directory must have at least 250 MB of free space, and the /tmp and /var directories must each have at least 20 MB of free space. If you choose to use a non-default directory for the installation, then that directory must also have at least 250 MB of free space.
If your system did not come with a factory installed Linux operating system, and you did not install a Red Hat Enterprise Linux (versions 4 and 5) or SUSE Linux Enterprise Server (version 9 and 10) operating system using the Dell Systems Build and Update Utility, you need to manually install the prerequisite RPMs prior to installing managed system software. For your convenience, these RPM files are provided on the Dell Systems Management Tools and Documentation DVD.
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, DVDs are auto-mounted with the -noexec mount option. This option does not allow you to run any executable from the DVD. You need to manually mount the DVD and then run executables.
Custom Install Managed system software provides two custom installation paths. One is RPM-based, with pre-configured custom directories, and the other is shell script-based. Using Pre-configured Custom Directories to Perform the Custom installation See Table 8-1 for details about using the RPMs to perform a custom installation using pre-configured custom directories. Table 8-1.
Table 8-1.
Using the Shell Script to Perform the Custom Installation You can run the Server Administrator Custom Install script in interactive mode or in silent and unattended mode. The basic usage of the script is: srvadmin-install.sh [OPTION]... Server Administrator Custom Installation Utility This utility will run in interactive mode if you do not specify any options, and it will run silently if you provide one or more options. The options are: [-x|--express] installs all components including RAC.
3 If necessary, mount the DVD using a command such as: mount /dev/dvdrom /mnt/dvdrom. 4 Navigate to SYSMGMT/srvadmin/linux/supportscripts. 5 To install the Storage Management Service components, type the following command. sh srvadmin-install.sh --storage (these are long options) or sh srvadmin-install.sh -s (these are short options) NOTE: Long options can be combined with short options, and vice-versa. NOTE: Just before the Server Administrator RPMs are installed, the srvadmin-install.
5 Execute the script with the sh srvadmin-install.sh command, which displays a list of component options. If any of the components are already installed, then those components are listed separately with a check mark next to them. The Server Administrator custom installation options are displayed. 6 Press to copy, to install, to reset and start over, or to quit. • If you press , you are prompted to enter the absolute destination path.
The custom unattended installation package is located in the directory you created as detailed in the section "Using the Shell Script to Perform the Custom Installation in Interactive Mode." This directory contains all the RPMs for the managed system software components for distribution. 1 Configure your ISV software distribution software to execute rpm –i *.rpm after the unattended installation package has been distributed.
NOTE: If a required version of the OpenIPMI driver is currently not installed on your remote systems, the srvadmin-hapi RPM fails to install and displays an error message stating that you must install or upgrade the OpenIPMI driver. In such a case, all RPMs that depend on the srvadmin-hapi RPM also fail to install. In such cases, you should also distribute the OpenIPMI-related RPM files in the SYSMGMT/srvadmin/linux/custom//openipmi directory on the DVD, where is RHEL4 or RHEL5 or SLES9 or SLES10.
Upgrading From Version 4.3 or Later For Dell OpenManage software versions 4.3 and later, you can upgrade your system using RPM commands or the srvadmin-install.sh shell script. Ensure that all installed components are upgraded when you perform either procedure. Using the RPM 1 Log on as root to the system running Red Hat Enterprise Linux or SUSE Linux Enterprise Server that requires the upgraded managed system components.
NOTE: The commands upgrade the existing Server Administrator RPM packages on your system. Starting with version 5.0, the openipmi and srvadmin-ipmi packages are new requirements for Server Administrator. The dkms RPM package under the openipmi sub-directory depends on the openipmi package. You may have to adjust the commands depending on the status of these packages on your system.
If the OpenIPMI driver is currently not installed on the system, or the version of the OpenIPMI driver installed on the system is less than the minimum version that is required by Server Administrator, the srvadmin-hapi RPM will fail to upgrade and will display an error message stating that you must install/upgrade the OpenIPMI driver. In such a case, any RPMs that depend on the srvadmin-hapi RPM will also fail to upgrade.
display an error message. The error message will state that you need to install the kernel-source RPM and build the OpenIPMI driver. In such a case, any RPMs that depend on the srvadmin-hapi RPM will also fail to upgrade.
If you are using the DVD, type one of the following commands: cd /mnt/dvdrom/SYSMGMT/srvadmin/linux/supportscripts cd /media/dvdrom/SYSMGMT/srvadmin/linux/supportscrip ts 4 Run the following script: sh srvadmin-install.sh The script detects any previous version of Server Administrator. If a previous version is installed, a message appears stating the current version and installed components. For example: Server Administrator version 4.4.0 is currently installed.
Uninstalling Managed System Software You can uninstall managed system software from the Red Hat Enterprise Linux or SUSE Linux Enterprise Server command line. Additionally, you can perform an unattended uninstallation on multiple systems simultaneously. Prerequisites for Uninstalling Managed System Software You must be logged in as root.
from Dell has an associated Dell VMware ESX Server Deployment Guide, also posted at this Web location. Instructions for installing supported versions of Dell OpenManage available at the time of that ESX Server release are found in that ESX Server release's Deployment Guide. Instructions for installing any supported subsequently released versions of Dell OpenManage are posted to the same location in a separate, clearly labeled document.
Installing Managed System Software on Supported Linux Operating Systems
Installing Managed System Software on Supported Linux Operating Systems 163
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.
Overview of the Active Directory Schema Extensions Dell created Classes, or groups of objects, that can be configured by the user to meet their unique needs. New Classes in the schema include an Association, a Product, and a Privilege class. An Association object links the users or groups to a given set of privileges and to systems (Product Objects) in your network.
Figure 9-1. Typical Setup for Active Directory Objects Association Object User(s) Group(s) Privilege Object RAC Privilege Object Server Administrator Privilege Object IT Assistant Privilege Object Dell Product(s) RAC Device Object Server Administrator Application Object IT Assistant Application Object In addition, you can set up Active Directory objects in a single domain or in multiple domains.
Figure 9-2. Setting Up Active Directory Objects in a Single Domain AO1 Group1 User1 User2 AO2 Priv1 User3 Priv2 RAC1 RAC2 To set up the objects for the single domain scenario, perform the following tasks: 1 Create two Association Objects. 2 Create two RAC Product Objects, RAC1 and RAC2, to represent the two DRAC 4 cards. 3 Create two Privilege Objects, Priv1 and Priv2, in which Priv1 has all privileges (Administrator) and Priv2 has Login privileges. 4 Group User1 and User2 into Group1.
Figure 9-3 shows how to setup the Active Directory objects in multiple domains for RAC. In this scenario, you have two DRAC 4 cards (RAC1 and RAC2) and three existing Active Directory users (User1, User2, and User3). User1 is in Domain1, but User2 and User3 are in Domain2. You want to give User1 and User2 Administrator privileges on both the RAC1 and the RAC2 card and give User3 a Login privilege on the RAC2 card. Figure 9-3.
5 Group User1 and User2 into Group1. The group scope of Group1 must be Universal. 6 Add Group1 as Members in Association Object 1 (AO1), Priv1 as Privilege Objects in AO1, and both RAC1 and RAC2 as Products in AO1. 7 Add User3 as Members in Association Object 2 (AO2), Priv2 as Privilege Objects in AO2, and RAC2 as a Product in AO2. For Server Administrator or IT Assistant, on the other hand, the users in a single Association can be in separate domains without needing to be added to a universal group.
To set up the objects for this multiple domain scenario, perform the following tasks: 1 Ensure that the domain forest function is in Native or Windows 2003 mode. 2 Create two Association Objects, AO1 and AO2, in any domain. The figure shows the objects in Domain1. 3 Create two Server Administrator Products, sys1 and sys2, to represent the two systems. Sys1 is in Domain1 and sys2 is in Domain2.
Extending the Active Directory Schema RAC, Server Administrator, and IT Assistant schema extensions are available. You only need to extend the schema for software or hardware that you are using. Each extension must be applied individually to receive the benefit of its software-specific settings. Extending your Active Directory schema will add schema classes and attributes, example privileges and association objects, and a Dell organizational unit to the schema.
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-2. Class Definitions for Classes Added to the Active Directory Schema (continued) Class Name Assigned Object Identification Number Class Type (OID) dellOmsa2AuxClass 1.2.840.113556.1.8000.1280.1.2.1.1 Auxiliary Class dellOmsaApplication 1.2.840.113556.1.8000.1280.1.2.1.2 Structural Class dellIta7AuxClass 1.2.840.113556.1.8000.1280.1.3.1.1 Auxiliary Class dellItaApplication 1.2.840.113556.1.8000.1280.1.3.1.2 Structural Class Table 9-3. dellRacDevice Class OID 1.2.840.113556.1.8000.
Table 9-5. 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-6. dellPrivileges Class OID 1.2.840.113556.1.8000.1280.1.1.1.
Table 9-7. 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-8. 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-10. 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-11. dellIta7AuxClass Class OID 1.2.840.113556.1.8000.1280.1.3.
Table 9-13. 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-14. 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-15. Server Administrator-Specific Attributes Added to the Active Directory Schema Attribute Name/Description Assigned OID/Syntax Object Identifier Single Valued dellOMSAIsReadOnlyUser 1.2.840.113556.1.8000.1280.1.2.2.1 TRUE TRUE if the User has Read-Only rights Boolean (LDAPTYPE_BOOLEAN in Server Administrator 1.3.6.1.4.1.1466.115.121.1.7) dellOMSAIsReadWriteUser 1.2.840.113556.1.8000.1280.1.2.2.2 TRUE if the User has Read-Write rights in Server Administrator Boolean (LDAPTYPE_BOOLEAN 1.3.
only need to extend the snap-in once, even if you have added more than one schema extension. You must install the snap-in on each system that you intend to use for managing these objects. The Dell Extension to the Active Directory Users and Computers Snap-In is an option that can be installed when you install your systems management software using the Dell Systems Management Tools and Documentation DVD.
Creating a Product Object NOTE: Server Administrator and IT Assistant users must use Universal-type Product Groups to span domains with their product objects. NOTE: When adding Universal-type Product Groups from separate domains, you have to create an Association object with Universal scope. The default Association objects created by the Dell Schema Extender utility are domain Local Groups and will not work with Universal-type Product Groups from other domains.
6 Click OK. 7 Right-click the privilege object that you created and select Properties. 8 Click the appropriate Privileges tab and select the privileges that you want the user to have (for more information, see Table 9-2 and Table 9-11). Creating an Association Object The Association Object is derived from a Group and must contain a group Type. The Association Scope specifies the Security Group Type for the Association Object.
To add Users or User Groups: 1 Right-click the Association Object and select Properties. 2 Select the Users tab and click Add. 3 Type the User or User Group name or browse to select one and click OK. Click the Privilege Object tab to add the privilege object to the association that defines the user’s or user group’s privileges when authenticating to a system. NOTE: You can add only one Privilege Object to an association object. To add a privilege: 1 Select the Privileges Object tab and click Add.
2 Enable SSL on each of your domain controllers by installing the SSL certificate for each controller. a Click Start→Administrative Tools→Domain Security Policy. b Expand the Public Key Policies folder, right-click Automatic Certificate Request Settings and click Automatic Certificate Request. c In the Automatic Certificate Request Setup Wizard, click Next and select Domain Controller. d Click Next and click Finish.
14 Click Next and save the certificate to a location of your choice. You will need to upload this certificate to the DRAC 4. To do this, go to the DRAC 4 Web-based interface→Configuration tab→Active Directory page. Or, you can use the racadm CLI commands (see "Configuring DRAC 4 and DRAC 5 Active Directory Settings Using the racadm CLI"). 15 Click Finish and click OK.
Importing the DRAC 5 Firmware SSL Certificate to All Domain Controllers’ Trusted Certificate Lists NOTE: If the DRAC 5 firmware SSL certificate is signed by a well-known CA, you do not need to perform the steps described in this section. NOTE: The following steps may vary slightly if you are using Windows 2000. The DRAC 5 SSL certificate is the same certificate that is used for the DRAC 4 Web server. All DRAC 4 controllers are shipped with a default self-signed certificate.
Configuring Active Directory Using CLI on Systems Running Server Administrator You can use the omconfig preferences dirservice command to configure the Active Directory service. The productoem.ini file is modified to reflect these changes. If the adproductname is not present in the productoem.ini file, a default name will be assigned.
productname=IT Assistant startmenu=Dell OpenManage Applications autdbid=ita accessmask=3 startlink=ITAUIServlet adsupport=true adproductname=mgmtStationITA NOTE: Restart the IT Assistant services after saving the itaoem.ini file to the disk. Configuring the DRAC 4 Using the Web-Based Interface 1 Log in to the Web-based interface using the default user, root, and its password. 2 Click the Configuration tab and select the Active Directory. 3 Select the Enable Active Directory check box.
10 If DRAC 4 NIC DHCP is enabled, place a check next to Use DHCP to obtain DNS server address. If you want to input a DNS server IP address manually, remove the check next to Use DHCP to obtain DNS server address and input your primary and alternate DNS Server IP addresses. 11 Click Apply to complete the DRAC 4 Active Directory feature configuration. Configuring the DRAC 5 Using the Web-Based Interface 1 Open a supported Web browser window. 2 Log in to the DRAC 5 Web-based interface.
13 Upload your domain forest Root CA certificate into the DRAC 5. • Select the Upload Active Directory CA Certificate check box and then click Next. • In the Certificate Upload page, type the file path of the certificate or browse to the certificate file, and click Apply. NOTE: The File Path value displays the relative file path of the certificate you are uploading. You must type the absolute file path, which includes the full path and the complete file name and file extension.
Configuring DRAC 4 and DRAC 5 Active Directory Settings Using the racadm CLI Using the following commands to configure the DRAC 4 Active Directory feature using the racadm CLI instead of the Web-based interface.
Using Active Directory to Log In To the DRAC 5 You can use Active Directory to log in to the DRAC 5 using one of the following methods: • Web-based interface • Remote RACADM • Serial or telnet console. The login syntax is consistent for all three methods: (or) \ (or) / where username is an ASCII string of 1–256 bytes. White space and special characters (such as \, /, or @) cannot be used in the user name or the domain name.
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 SYSMGMT\ManagementStation\windows\PreReqChecker or SYSMGMT\srvadmin\windows\PreReqChecker directory on the Dell Systems Management Tools and Documentation DVD. After running the prerequisite check, an HTML file will be created in the %Temp% directory. The file is named omprereq.htm, and it contains the results of the prerequisite check.
Table 10-1. Return Codes While Running the Prerequisite Check Silently Return Code Description 0 No condition, or conditions, is associated with the software. 1 An informational condition, or conditions, is associated with the software. It does not prevent a software product from being installed. 2 A warning condition, or conditions, is associated with the software. It is recommended that you resolve the conditions causing the warning before you proceed with the installation of the software.
Table 10-2. Feature IDs for the Management Station Feature ID Description ADS Microsoft Active Directory® Snap-in Utility BMC Baseboard Management Controller Management Utility ITA Dell OpenManage™ IT Assistant RACMS Remote Access Controller Table 10-3.
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 DVD kit. Also, you can find the guide on the Dell Support website at support.dell.com and on the Dell Systems Management Tools and Documentation DVD at docs directory. How do I install Dell OpenManage Server Administrator with only the CLI features? By choosing not to install the Server Administrator Web server, you will get CLI features only.
• Locate SysMgmt.msi from the SYSMGMT\srvadmin\windows\SystemsManagement directory and enter the following command at the command prompt to force a reinstall. msiexec /i SysMgmt.msi REINSTALL=ALL REINSTALLMODE=vomus • Select Custom Setup and choose all the features that were originally installed. If you are not sure which features were installed, select all of them and perform the installation.
What is an MSP service pack file? Should I upgrade my Dell OpenManage 5.4 version with the MSP file? A Microsoft Service Pack (MSP) file stores only the differences between an old version and a new version. It is much smaller in size than the upgrade file. You can use the MSP file to upgrade your Dell OpenManage 5.4 to 5.5. Using the MSP file is a good idea as it is more efficient. NOTE: You can upgrade from Dell Openmange software version 5.4 to 5.5 through a MSP installation.
What is the best way to use the Prerequisite Checker information? The Prerequisite Checker is available for Windows. See the readme file at SYSMGMT\srvadmin\windows\PreReqChecker\readme.txt on the Dell Systems Management Tools and Documentation DVD, for detailed information about how to use the Prerequisite Checker. In the Prerequisite Checker screen, I get the message "An error occurred while attempting to execute a Visual Basic Script. Please confirm that Visual Basic files are installed correctly.
Can I launch my installation without running the Prerequisite Checker? How do I do that? Yes, you can. For example, you can run the MSI of the managed system software, directly from the SYSMGMT\srvadmin\Windows\SystemsManagement. In general, it is not a good idea to bypass the prerequisite information as there could be important information that you would not know otherwise.
Table 11-1.
Why is the Prerequisite Checker not available under Red Hat Enterprise Linux and SUSE Linux Enterprise Server? The Prerequisite Checker is built into the omilcore RPM package. The checker uses a combination of RPM dependency checks and Dell hardware checks.
What do the directories under srvadmin/linux/custom/ contain? The following table lists the names of the directories in the SYSMGMT/srvadmin/linux/custom/ directory. Table 11-3. Names of the Directories Under the srvadmin/linux/custom/ Directory Name of RPM Description Other Server Administrator RPMs required srvadmin-base — This is the core code for Server Administrator.
Table 11-3. Names of the Directories Under the srvadmin/linux/custom/ Directory (continued) Name of RPM Description Other Server Administrator RPMs required 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) Name of RPM Description Other Server Administrator RPMs required 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 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.SLES9 dkms package — dkms Kernel modules for openipmi XX.Y.SLES9 in a DKMS wrapper.
What daemons run on Red Hat Enterprise Linux and SUSE Linux Enterprise Server operating systems after Server Administrator is started? The daemons that run on Red Hat Enterprise Linux and SUSE Linux Enterprise Server operating systems depend on what has been installed and what is enabled to run. The following table displays the daemons that typically run for a full install: Table 11-4.
What kernel modules are loaded when Server Administrator is started? This is dependent on the type of systems instrumentation. The following table displays the kernel modules loaded when Server Administrator is started. Table 11-5.
212 Frequently Asked Questions
Glossary The following list defines technical terms, abbreviations, and acronyms used in your system documents. attribute As it relates to an attribute is a piece of information related to a component. Attributes can be combined to form groups. If an attribute is defined as read-write, it may be defined by a management application. beep code A diagnostic message in the form of a pattern of beeps from your system's speaker.
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.
MPEG Acronym for Motion Picture Experts Group. MPEG is a digital video file format. 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.
NTLM Abbreviation for Windows NT LAN Manager. NTLM is the security protocol for the Windows NT operating system. NTLM is now known as Integrated Windows Authentication. 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.
PCI Abbreviation for Peripheral Component Interconnect. The predominant 32-bit or 64-bit local-bus standard developed by Intel Corporation. PERC Acronym for Expandable RAID controller. 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.
ppm Abbreviation for pages per minute. PPP Abbreviation for Point-to-Point Protocol. 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.
RBAC Abbreviation for role-based access control. 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.
after you turn off your system. Examples of code in ROM include the program that initiates your system's boot routine and the POST. 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.
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, 38 write, 38 ATA, 18 access control, 38 Active Directory, 23, 38, 40, 47, 49, 164, 169, 178, 186 object identifiers, 163 objects, 165 schema, 170 schema extender utility, 170-171 schema extensions, 163 ADDLOCAL, 90, 120 administrator, 38 Administrator Pack, 179 Administrator privileges, 38, 102 agent, 59 SNMP, 49 agents, 17 AGP, 213 alert filters, 15 alert log, 20 Altiris, 126, 161 ASCII, 213 attribute, 213 authentication, 23, 40, 164 authorization, 164
C cursor, 215 CA, 66, 184-185 Certificate, 187 custom setup, 74 certificates Web, 66 certification, 22 Certification Authority, 66, 184-185 custom unattended installation, 83 D DAT, 215 chip, 214 data redundancy, 18 CI/O, 214 dB, 215 CIM, 20, 37, 45, 51, 100 DCOM, 25, 31 CIM protocol, 91 Dell, 98, 163 Citrix, 107 Dell base OID, 163 CLI, 20, 40, 120, 197 Dell OpenManage, 199 cm, 214 Dell organizational unit, 170 command line, 121 Dell Remote Access Controller, 165 command line interfac
DNS, 33-34, 36 G domain, 47 domain controller, 182, 184-185 Globally Unique Identifier (GUID), 121 DRAC, 21, 179, 184-185 group privileges, 38 DRAC 4, 184-185, 187-188, 204 controller, 21 SSL certificate, 184-185 GUID, 112 DRAC 5 controller, 21 H help, 22 DRAC III, 21, 203 XT, 21 hot spares, 18 DRAC III/XT, 21 HTTPS, 24, 28, 31-32, 34-36, 40 HTTP, 25-26, 32-33, 35-36 Dynamic Kernel Support, 136 E I In, 183 encryption, 38 INI file, 111 ERA, 21 ERA/MC, 21 ERA/O, 21 inoperable system, 21
J MMC, 180-181, 183 Java Secure Socket Extension, 40 modular system, 21 JSSE, 40 MOF, 20 modular systems, 18 monitored systems, 17 monitoring, 12 L LDAP, 24, 28, 35, 175 LDAPS, 34-36 LDIF script file, 170 MSI, 111-112, 199 msiexec.
P R packets SNMP, 51 RAC, 21, 44, 163, 170, 180-181 devices, 164 installation, 44 software, 44, 100 PAM, 40 passwd, 49 Pluggable Authentication Modules, 40 racadm, 21, 23, 190 RAID, 70 port information, 24 RAID controllers, 14 ports, 23-24, 197 RBAC, 38 power user, 38 RDP, 28 Prerequisite Checker, 72, 104, 193, 200 readme, 21, 43 prerequisite status, 76 Red Hat Enterprise Linux, 14, 17, 43, 45, 48, 55, 59, 71, 92, 134-135, 160, 202 privilege object, 182 privileges administrator, 102 group, 3
role-based access control, 38 authority, 23 Root CA, 182 RPC, 24, 27, 29-30 RPM, 133, 148, 155, 202 rpms, 158 server proxy, 46 Server Administrator, 17, 20, 168, 203 Services, 148, 201 Server Update Utility, 19 session timeout, 65 S setup custom, 74 express, 44, 74 SAS, 18 setup.exe, 72, 76, 87 SATA, 18 shutdown, 15 schema, 163, 170-171 Simple Network Management Protocol, 20, 45, 100 SchemaExtenderOem.
SOL, 17 U SOL Proxy, 16 UDP, 26 SSH, 26, 29 unattended installation, 81, 114 SSL, 40, 169, 182-183 unattended uninstallation, 124 SSL encryption, 23 universal groups, 181 standard action, 111 update packages, 21 storage management, 39 updates, 19 software, 15 Storage Management Service, 18, 201 upgrade, 46, 78, 199 Subscription Kit, 14 user, 38 SUU, 19 user ID, 23 SysMgmt.
Windows Installer Engine, 116 Installer Service, 111 Windows Management Instrumentation, 45, 100 Windows Server 2003, 199 WMI, 45, 51, 100 write access, 38 X X.
