Dell™ OpenManage™ Installation and Security User’s Guide Version 6.
Notes and Cautions NOTE: A NOTE indicates important information that helps you make better use of your computer. CAUTION: A CAUTION indicates potential damage to hardware or loss of data if instructions are not followed. ___________________ Information in this document is subject to change without notice. © 2009 Dell Inc. All rights reserved. Reproduction of these materials in any manner whatsoever without the written permission of Dell Inc. is strictly forbidden.
Contents 1 Introduction . Overview . . . . . . . . . . . . . . . . . . . . . . . 11 . . . . . . . . . . . . . . . . . . . . . . . . 11 . . . . 12 . . 12 . . . . . . . . . . . . . . . 13 Systems Management Software Overview Dell OpenManage Systems Management Software Deployment Software Dell Systems Management Tools and Documentation DVD 13 Dell Server Updates DVD . . . . . . . . . . . . . . 19 . . . . . . . . . . 19 . . . . . . . . . . . 20 . . . . . . . . . . . .
3 Using Unified Server Configurator to Install an Operating System . . . . . . . . . . . . . . . . . . 41 Overview . . . . . . . . . . . . . . . . . . . . . . . . . 41 . . . . . . . . 41 . . . . . . . . . 42 . . . . . . . . . . . . . 42 Starting the Unified Server Configurator Updating Unified Server Configurator . Installing the Operating System 4 Using Systems Build and Update Tools to Install an Operating System . . . . . . . . . . . . . . . . . . 45 Overview . . . . . . . . . . . . . . . .
Configuring the SNMP Agent for Systems Running Supported Windows Operating Systems . . . . . . . . . . . . 53 Configuring the SNMP Agent on Systems Running Supported Red Hat Enterprise Linux Operating Systems . . . . . . 57 Configuring the SNMP Agent on Systems Running Supported SUSE Linux Enterprise Server Operating Systems . 62 Secure Port Server and Security Setup . . . . . . . . . 66 . . . . . . . 66 . . . . . . . . . . 68 Setting User and Server Preferences X.509 Certificate Management .
Performing an Unattended Installation of Managed System Software . . . . . . . . . . . . . . . . . . . . . . 91 MSI Return Code . . . . . . . . . . . . . . . . . . 98 . . . . . . 99 Uninstalling Managed System Software Managed System Software Installation Using Third-Party Deployment Software . . . . . . . . . . . . . . . . . 102 8 Installing Dell OpenManage Software On Microsoft Windows Server 2008 Core and Microsoft Hyper-V Server . . . . . . . . . . . 103 Introduction . . . . . . . . . . . . . .
Copying a Dynamically Built Device Driver to Systems Running the Same Kernel . . . . . . . . . . . . . . . . . . 112 Forcing Dynamic Kernel Support on Red Hat Enterprise Linux Update Releases When Kernel is Tainted . . . . . 113 Forcing Dynamic Kernel Support on Red Hat Enterprise Linux Update Releases . . . . . . . . . . . . . . . . . . 114 OpenIPMI Device Driver . . . . . . . . . . . . . . . . . 114 Degradation of Functionality When the Server Administrator Instrumentation Service is Started . . . . .
10 Dell OpenManage on VMware ESXi Software 133 Dell OpenManage on VMware ESXi 3.5 Update 4 . . . 133 Dell OpenManage on VMware ESXi 4.0 Patch Release ESXi400-200906001 . . . . . . . . . . . . . . . . . . . 133 Using the vSphere CLI . . . . . . . . . . . . . . 134 Using the VMware vSphere Management Assistant 134 Troubleshooting . . . . . . . . . . . . . . . . . .
Modify. . . . . . . . . . . . . . . . . . . . . . . . 146 Repair . . . . . . . . . . . . . . . . . . . . . . . . 147 . . . . . . 147 System Recovery on Failed Installation Performing an Unattended Installation of Management Station Software . . . . . . . . . . . . . . . . . . . . . . 148 Uninstalling Management Station Software . . . . 154 Performing an Unattended Uninstallation of Management Station Software . . . . . . . . . . . . . . . . . . 155 Supported Management and Alerting Agents . . .
14 Frequently Asked Questions General . . . . . . . . . . 187 . . . . . . . . . . . . . . . . . . . . . . . . 187 Microsoft® Windows® . . . . . . . . . . . . . . . . 188 Red Hat® Enterprise Linux® or SUSE® Linux Enterprise Server 195 Glossary Index 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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.
• Prerequisite Checker • Frequently Asked Questions 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.
Deployment Software From Dell OpenManage version 6.0.1 onwards, you can install an operating system using either the Dell Unified Server Configurator or the Systems Build and Update Utility. The Dell Unified Server Configurator (USC) is an embedded utility that enables systems and storage management tasks from an embedded environment throughout the system’s lifecycle. USC resides on an embedded flash memory card, can be started during the boot sequence, and functions independently of the operating system.
The Dell Systems Management Tools and Documentation DVD contains the following products: Dell Systems Build and Update Utility Functionality You can use the Dell Systems Build and Update Utility to: • Update your system firmware and install an operating system. See "Using Systems Build and Update Tools to Install an Operating System". • Update the firmware and BIOS in a pre-operating system environment on multiple systems. • Configure your system hardware.
The Storage Management Service provides enhanced features for managing a system's locally-attached RAID and non-RAID disk storage.
For more information on Remote Access Controller, see the Dell Remote Access Controller Firmware User’s Guide in the docs directory or on the Dell Support site at support.dell.com. Location on the DVD For managed systems: \SYSMGMT\srvadmin For management stations: \SYSMGMT\ManagementStation BMC Management Utility Functionality The BMC Management Utility provides a command line based remote management application to manage all supported BMC functions.
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 configuration parameters, and perform remote chassis power control. For information on installing the BMU, see "Installing Management Station Software".
For more information on the Dell Systems Service and Diagnostics Tools, see the Dell Systems Service and Diagnostics Tools Quick Installation Guide in the docs directory or on the Dell Support site at support.dell.com. Location on the DVD \SERVICE Dell Online Diagnostics Functionality Dell Online Diagnostics runs operating system-based diagnostics to check the health of your Dell system.
Dell Server Updates DVD The Dell OpenManage subscription service kit is a collection of two DVDs: • Dell Systems Management Tools and Documentation DVD • Dell Server Updates DVD The Dell Server Updates DVD is available only to those customers who have subscribed to the subscription service. The Dell Server Updates DVD contains Dell Update Packages (DUPs) and Dell OpenManage Server Update Utility (SUU).
Other Documents You Might Need Besides this guide, you can find the following guides either on the Dell Support website at support.dell.com or on the Dell Systems Management Tools and Documentation DVD: 20 • The Dell Unified Server Configurator User’s Guide provides information on using Unified Server Configurator. • The Dell Management Console User’s Guide has information about installing, configuring, and using Dell Management Console.
• The Dell OpenManage Server Administrator SNMP Reference Guide documents the Simple Network Management Protocol (SNMP) management information base (MIB). The SNMP MIB defines variables that extend the standard MIB to cover the capabilities of systems management agents. • The Dell OpenManage Server Administrator CIM Reference Guide documents the Common Information Model (CIM) provider, which is an extension of the standard management object format (MOF) file.
• The Dell Remote Access Controller Installation and Setup Guide provides complete information about installing and configuring a DRAC III, DRAC III/XT, or ERA/O controller, configuring an ERA controller, and using a RAC to remotely access an inoperable system. • The Dell Remote Access Controller Racadm User's Guide provides information about using the racadm command line utility to manage DRAC III, DRAC III/XT, ERA, and ERA/O controllers.
Dell OpenManage Security Security Features The Dell™ OpenManage™ systems management software components provide the following security features: • Authentication for users through hardware-stored user IDs and passwords, or by using the optional Microsoft® Active Directory®. • Support for Network Information Services (NIS), Winbind, Kerberos, and Lightweight Directory Access Protocol (LDAP) authentication protocols for Linux operating systems.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations Port # Protocol Port Version Maximum Direction Usage Type Encryption Level Configurable Dell OpenManage Storage Management 5554 TCP TCP 4.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Version Maximum Direction Usage Type Encryption Level Configurable Dell OpenManage Client Connector 135 RPC TCP/ 2.0 UDP None In/Out Viewing of No client managemen t data 389 LDAP TCP 2.0 128-bit In/Out Domain No authenticati on 4995 HTTPS TCP 2.0 128-bit SSL In/Out Web GUI 1024 DCOM 65535 (Dynamically assigned) TCP/ 2.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Version Maximum Direction Usage Type Encryption Level 135 DCOM TCP 7.x None Out Event No transmissio n through WMI 102465535 (Dynamically DCOM TCP/ 7.x UDP None In/Out Monitoring and configuratio n through WMI assigned) Configurable Dell OpenManage IT Assistant For information on Dell OpenManage IT Assistant UDP/TCP Ports default location, see the Dell OpenManage IT Assistant User’s Guide.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Version Maximum Direction Usage Type Encryption Level 135 RPC TCP/ 2.0 UDP None In/Out CIM No managemen t queries 135 RPC TCP/ 2.0 UDP None In/Out Remote No Server Administrat or Command Line (for IT Assistant). Remote software update feature (for Windows operating systems). 139 NetBIOS TCP 2.0 None In/Out Remote No Server Administrat or Command Line (for IT Assistant).
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Version Maximum Direction Usage Type Encryption Level 162 SNMP UDP 1.x, 2.0 None Out SNMP trap No event 445 NetBIOS TCP 2.0 None In/Out Remote No software updates to Server Administrat or (for Windows operating systems) 1311 HTTPS TCP 1.x 128-bit SSL In/Out Web GUI 11487 Proprietary UDP 1.x None In Remote Yes Flash BIOS update initiation from IT Assistant 11489 Proprietary TCP 1.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Version Maximum Direction Usage Type Encryption Level Configurable Dell Remote Access Controller (DRAC): DRAC III, DRAC III/XT, ERA, and ERA/O NOTE: Only iDRAC6 is supported on xx1x systems. For information on iDRAC UDP/TCP Ports default location, see the Integrated Dell Remote Access Controller User's Guide. 21 FTP TCP 1.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Version Maximum Direction Usage Type Encryption Level 162 SNMP UDP 1.0 None Out SNMP trap No event 443 HTTPS TCP 1.0 128-bit SSL In/Out Web No managemen t GUI 443 HTTPS TCP 3.2 128-bit SSL In/Out Remote No racadm CLI utility 5869 Proprietary TCP 1.0 None In/Out Remote No racadm CLI utility 5900 VNC TCP 1.0 56 bit DES In/Out Video redirection Yes 5900 VNC TCP 3.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Version Maximum Direction Usage Type Encryption Level 25 SMTP TCP 1.0 None In/Out Optional e- No mail alert messages 53 DNS UDP 1.20 None In/Out Dynamic No Domain name server (DNS) registration of the host name assigned within DRAC 68 DHCP UDP 1.0 None In/Out DHCP assigned IP address 69 TFTP UDP 1.0 None In/Out Firmware No update through Trivial FTP 80 HTTP TCP 1.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Version Maximum Direction Usage Type Encryption Level 443 HTTPS TCP 1.0 128-bit SSL In/Out Web Yes managemen t GUI and remote racadm CLI utility 636 LDAPS TCP 1.0 128-bit SSL In/Out Optional No Active Directory Services (ADS) authenticati on 3269 LDAPS TCP 1.0 128-bit SSL In/Out Optional No ADS authenticati on 3668 Proprietary TCP 1.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Version Maximum Direction Usage Type Encryption Level Configurable DRAC/MC 23 Telnet TCP 1.0 None In/Out Optional Yes Telnet CLI managemen t 25 SMTP TCP 1.0 None In/Out Optional e- No mail alert messages 53 DNS UDP 1.0 None In/Out Dynamic No DNS registration of host name assigned within DRAC 68 DHCP UDP 1.0 None In/Out DHCP assigned IP address 69 TFTP UDP 1.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Version Maximum Direction Usage Type Encryption Level 389 LDAP TCP 1.0 None In/Out Optional No ADS authenticati on 443 HTTPS TCP 1.0 128-bit SSL In/Out Web No managemen t GUI and remote racadm CLI utility 636 LDAPS TCP 1.0 128-bit SSL In/Out No Optional ADS authenticati on 3269 LDAPS TCP 1.0 128-bit SSL In/Out Optional No ADS authenticati on 22 SSHv2 TCP 1.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Version Maximum Direction Usage Type Encryption Level 53 DNS UDP 1.0 None In/Out Dynamic No DNS registration of host name assigned within DRAC 68 DHCP UDP 1.0 None In/Out DHCP assigned 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 161 SNMP UDP 1.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Version Maximum Direction Usage Type Encryption Level 636 LDAPS TCP 1.0 128-bit SSL In/Out Optional No ADS authenticati on 3269 LDAPS TCP 1.0 128-bit SSL In/Out Optional No ADS authenticati on 3668 Proprietary TCP 1.0 None In/Out Virtual Media Service Yes 3669 Proprietary TCP 1.0 128-bit SSL In/Out Virtual Media Secure Service Yes 5900 TCP 1.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Version Maximum Direction Usage Type Encryption Level Configurable Digital KVM 2068 Proprietary TCP 1.0 128-bit SSL In/Out Video No Redirection — Keyboard/M ouse 3668 Proprietary TCP 1.0 None In/Out Virtual Media No 8192 Proprietary TCP 1.0 None In/Out Video redirection to client viewer No NOTE: CIM ports are dynamic. See the Microsoft knowledge base at support.microsoft.
User Privileges Server Administrator grants different access rights based on the user's assigned group privileges. The three user levels are User, Power User, and Administrator. Users can view most information. Power Users can set warning threshold values and configure which alert actions are to be taken when a warning or failure event occurs.
Privilege Levels to Access Server Administrator Services Table 2-3 summarizes which user levels have privileges to access and manage Server Administrator Services. Table 2-3. Server Administrator User Privilege Levels Service User Privilege Level Required View Manage Instrumentation U, P, A P, A Remote Access U, P, A A Update U, P, A A Storage Management U, P, A A Table 2-4 defines the user privilege level abbreviations used in Table 2-3. Table 2-4.
Red Hat Enterprise Linux and SUSE Linux Enterprise Server Authentication For supported Red Hat® Enterprise Linux® and SUSE® Linux Enterprise Server operating systems, Server Administrator authentication is based on the Pluggable Authentication Modules (PAM) library. This documented library of functions allows an administrator to determine how individual applications authenticate users.
Using Unified Server Configurator to Install an Operating System Overview You can use either Dell™ Unified Server Configurator (USC) or the Dell Systems Build and Update Utility (SBUU) to install an operating system. For information on installing an operating system using SBUU, see "Using Systems Build and Update Tools to Install an Operating System". USC is an embedded utility that enables systems and storage management tasks from an embedded environment throughout the server’s life cycle.
Updating Unified Server Configurator You can update to the next version of USC using the Platform Update wizard. It is recommended that you run the Platform Update wizard on a regular basis to access updates as they become available. For more information on updating USC, see Dell Unified Server Configurator User’s Guide. NOTE: In Version 1.0 of USC, the only available updates are for USC, diagnostics, and drivers. Additional updates (such as device firmware) will be available in later versions of USC.
6 Insert the OS installation media and click Next. USC verifies that the installation media is appropriate for the operating system you selected. If the inserted installation media does not match the operating system selection, it will be ejected. 7 Click Finish to reboot the system and continue with the OS installation. Upon reboot, the system boots to the OS installation media.
Using Unified Server Configurator to Install an Operating System
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 to install 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.
Setup and Administration Before You Begin • Read the Installation Requirements to ensure that your system meets or exceeds the minimum requirements. • Read the applicable Dell OpenManage readme files and the Dell Systems Software Support Matrix located on the Dell Support website at support.dell.com. These files contain the latest information about software, firmware, and driver versions, in addition to information about known issues.
Supported Operating Systems and Web Browsers For supported operating systems and Web browsers, see the Dell Systems Software Support Matrix located on the Dell Support website at support.dell.com.
• The Server Administrator Remote Access Controller service requires that a remote access controller (RAC) be installed on the system to be managed. See the relevant Dell Remote Access Controller User’s Guide for complete software and hardware requirements NOTE: The RAC software is installed as part of the Typical Setup installation option, when installing managed system software, provided that the managed system meets all of the RAC installation prerequisites.
Enterprise Server operating systems, Dell OpenManage software supports the SNMP systems management standard. You must install the SNMP package provided with the operating system. CIM and WMI are unsupported. NOTE: For information about installing a supported systems management protocol standard on your managed system, see your operating system documentation. Table 5-1 shows the availability of the systems management standards for each supported operating system. Table 5-1.
support. If your system is running Windows Server 2003 R2 or Windows Storage Server R2, it is recommended that after you install Server Administrator, you also install the optional Hardware Management component of R2. To install the Windows Server 2003 R2 IPMI driver on PowerEdge x8xx and PowerVault x00 systems, perform the following additional step: • From a command shell, execute the following command: Rundll32 ipmisetp.dll, AddTheDevice NOTE: This step is not required on PowerEdge x9xx systems.
Configuring a Supported Web Browser For a list of supported Web browsers, see "Supported Operating Systems and Web Browsers." If you are connecting to a Web-based interface from a management station that connects to a network through a proxy server, configure the Web browser to connect properly. See your Web browser’s documentation for more information. NOTE: Ensure that the Web browser is set to bypass the proxy server for local addresses.
NOTE: The default SNMP agent configuration usually includes an SNMP community name such as public. For security reasons, change the default SNMP community names. For information about changing SNMP community names, see the appropriate section below for your operating system. For additional guidelines, see the Securing an SNMP Environment article, dated May 2003, in the Dell Power Solutions magazine. This magazine is also available at www.dell.com/powersolutions.
Enabling SNMP Access By Remote Hosts on Windows Server 2003 Windows Server 2003, by default, does not accept SNMP packets from remote hosts. For systems running Windows Server 2003, you must configure the SNMP service to accept SNMP packets from remote hosts if you plan to manage the system by using SNMP management applications from remote hosts. To enable remote shutdown of a system from IT Assistant, SNMP Set operations must be enabled.
4 Scroll down the list of services to SNMP Service, right-click SNMP Service, and click Properties. The SNMP Service Properties window appears. 5 Click the Security tab to add or edit a community name. a To add a community name, click Add under the Accepted Community Names list. The SNMP Service Configuration window appears. b Type the community name of the management station (the default is public) in the Community Name text box and click Add. The SNMP Service Properties window appears.
5 Click the Security tab to change the access rights for a community. 6 Select a community name in the Accepted Community Names list, and then click Edit. The SNMP Service Configuration window appears. 7 Set the Community Rights to READ WRITE or READ CREATE, and click OK. The SNMP Service Properties window appears. 8 Click OK to save the changes. NOTE: In Dell OpenManage Server Administrator version 5.3 and later, SNMP Set Operations are disabled by default in Server Administrator.
5 Click the Traps tab to add a community for traps or to add a trap destination for a trap community. a To add a community for traps, type the community name in the Community Name box and click Add to list, which is located next to the Community Name box. b To add a trap destination for a trap community, select the community name from the Community Name drop-down box and click Add under the Trap Destinations box. The SNMP Service Configuration window appears. c Type the trap destination and click Add.
Server Administrator SNMP Agent Install Actions If Server Administrator detects the default SNMP configuration during installation, it attempts to modify the SNMP agent configuration to give read-only access to the entire MIB tree for the public community. Server Administrator modifies the /etc/snmp/snmpd.conf SNMP agent configuration file in two ways. The first change is to create a view to the entire MIB tree by adding the following line if it does not exist: view all included .
Changing the SNMP Community Name Configuring the SNMP community names determines which systems are able to manage your system through SNMP. The SNMP community name used by systems management applications must match an SNMP community name configured on the Server Administrator software system, so the systems management applications can retrieve management information from Server Administrator.
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.
Firewall Configuration on Systems Running Supported Red Hat Enterprise Linux Operating Systems If you enable firewall security when installing Red Hat Enterprise Linux, the SNMP port on all external network interfaces is closed by default. To enable SNMP management applications such as IT Assistant to discover and retrieve information from Server Administrator, the SNMP port on at least one external network interface must be open.
5 Select whether to open an entire network interface or just the SNMP port on all network interfaces. a To open an entire network interface, select one of the Trusted Devices and press the spacebar. An asterisk in the box to the left of the device name indicates that the entire interface will be opened. b To open the SNMP port on all network interfaces, select Other ports and type snmp:udp. 6 Select OK and press . The Firewall Configuration screen appears. 7 Select OK and press .
Sever Administrator SNMP Install Actions Server Administrator SNMP communicates with the SNMP agent using the SNMP Multiplexing (SMUX) protocol. When Server Administrator SNMP connects to the SNMP agent, it sends an object identifier to the SNMP agent to identify itself as a SMUX peer. Since the object identifier must be configured with the SNMP agent, Server Administrator adds the following line to the SNMP agent configuration file, /etc/snmpd.conf or /etc/snmp/snmpd.
To enable SNMP access from all remote hosts 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 this line by removing 127.0.0.1. When edited, the new line should read: rocommunity public 3 To enable SNMP configuration changes, restart the SNMP agent by typing: /etc/init.
Enabling SNMP Set Operations Enable SNMP Set operations on the system running Server Administrator in order to change Server Administrator attributes using IT Assistant. To enable remote shutdown of a system from IT Assistant, enable SNMP Set operations. NOTE: Rebooting your system for change management functionality does not require SNMP Set operations. To enable SNMP Set operations on the system running Server Administrator, edit the SNMP agent configuration file, /etc/snmpd.conf or /etc/snmp/snmpd.
Secure Port Server and Security Setup This section contains the following topics: • Setting User and Server Preferences • X.509 Certificate Management Setting User and Server Preferences You can set user and secure port server preferences for Server Administrator and IT Assistant from the respective Preferences Web page. Click General Settings and click either the User tab or Web Server tab. NOTE: You must be logged in with Administrator privileges to set or reset user or server preferences.
• The HTTPS Port field specifies the secure port for Server Administrator. The default secure port for Server Administrator is 1311. NOTE: Changing the port number to an invalid or in-use port number may prevent other applications or browsers from accessing Server Administrator on the managed system. • The IP Address to Bind to field specifies the IP address(es) for the managed system that Server Administrator binds to when starting a session.
X.509 Certificate Management Web certificates are necessary to ensure the identity of a remote system and ensure that information exchanged with the remote system cannot be viewed or changed by others. To ensure system security, it is strongly recommended that you either generate a new X.509 certificate, reuse an existing X.509 certificate, or import a root certificate or certificate chain from a Certification Authority (CA).
Deployment Scenarios for Server Administrator In Dell OpenManage version 6.
Table 6-1. Deployment Scenarios (continued) You want to Select View the status of local and remote storage attached to a managed system and obtain storage management information in an integrated graphical view. Storage Management. Remotely access an inoperable system, receive alert notifications when a system is down, and remotely restart a system. Remote Access Controller.
Table 6-2. Managed System Software Components Component What is Installed Deployment Scenario Systems on Which to be Installed Server Administrator Web Server Web-based systems management functionality that allows you to manage systems locally or remotely Install only the Server Administrator Web Server if you want to remotely monitor the managed system from your system. You need not have physical access to the managed system. Any system. For example, laptops, desktops, or Dell PowerEdge systems.
Table 6-2. Managed System Software Components (continued) Component What is Installed Deployment Scenario Systems on Which to be Installed Storage Management Server Administrator Storage Management Install the Storage Management to implement hardware RAID solutions and configure the storage components attached to your system.
Table 6-2. Managed System Software Components (continued) Component What is Installed Deployment Scenario Systems on Which to be Installed Remote Access Controller Server Administrator CLI + Instrumentation Service + iDRAC or DRAC 5, or DRAC 4 (depending on the type of your Dell PowerEdge system) Install Remote Access Service to receive e-mail alerts for warnings or errors related to voltages, temperatures, and fan speeds.
Deployment Scenarios for Server Administrator
Installing Managed System Software on Microsoft Windows Operating Systems Overview This section contains the procedure to install managed system software on systems running Microsoft® Windows® operating systems. On Microsoft Windows operating systems, an autorun utility appears when you insert the Dell Systems Management Tools and Documentation DVD. This utility allows you to choose the systems management software you want to install on your system.
Installation Procedures This section explains how to install, upgrade, and uninstall Server Administrator on a system running a supported Windows operating system. NOTE: If you want to use supporting agents for the Simple Network Management Protocol (SNMP), you must install the operating system support for the SNMP standard before or after you install Server Administrator. For more information about installing SNMP, see the installation instructions for the operating system you are running on your system.
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 the software feature. If you do not resolve the issue, the software feature is not installed. Use the RunPreReqChecks.exe /s command (at \SYSMGMT\srvadmin\windows\PreReqChecker) to run the prerequisite check silently. For more information, see "Prerequisite Checker.
Certificate Authority - Signed/Self-Signed Certificate You need a certificate signed by the Certificate Authority (CA) or a self-signed certificate to install and configure the Remote Enablement feature on your system. It is recommended that you use a certificate signed by the CA. You can also use the SelfSSL tool to generate self-signed certificates. Creating a Certificate 1 Download IIS Resource Kit from http://www.microsoft.com/downloads/details.
8 Click Close. 9 Click OK. 10 In the Console screen, expand Certificates (Local Computer) in the left navigation pane. 11 Expand Personal. 12 Select Certificates. 13 In the right-hand pane, double-click the required certificate. The Certificate screen displays. 14 Click Details tab. 15 Select Thumbprint. Copy the thumbprint to the clipboard. You can use this parameter while creating the HTTPS listener. 16 Click OK.
Configuring User Authorization for WinRM and WMI Servers To provide access rights to WinRM and WMI services, users must be explicitly added with the appropriate access levels. NOTE: You must login with administrator privileges to configure user authorization for WinRM and WMI Servers. NOTE: The administrator is configured by default. WinRM: 1 Click Start and click Run. 2 Type winrm configsddl and click OK. 3 Click Add and add the required users (local/domain) to the list.
Configuring the Windows Firewall for WinRM 1 Open the Control Panel. 2 Click Windows Firewall. 3 Click the Exceptions tab. 4 Select the Windows Remote Management check box. If you do not see the check box, click the Add Program button to add Windows Remote Management. Configuring the Envelope Size for WinRM 1 Open a command prompt. 2 Type winrm g winrm/config. 3 Check the value of the MaxEnvelopeSizekb attribute.
NOTE: After you have installed Server Administrator on PowerEdge 800, 830, 850, and 1800 systems, you may be prompted to reboot your system if you have chosen to install the Storage Management Service. NOTE: During installation of Server Administrator on supported Windows systems, if an Out of Memory error message displays, you must exit the installation and free up memory. Close other applications or perform any other task that will free up memory, before re-attempting Server Administrator installation.
remote access controller installed on it. You can, however, go to Custom Setup and select the Remote Access Controller software module for installation. NOTE: The Remote Enablement feature is available only through the Custom Setup option. NOTE: Server Administrator installation also installs some of the required Visual C++ runtime components on your system.
8 Select Custom and click Next. The Custom Setup dialog box appears. See Table 6-1and Table 6-2 to help you select the Server Administrator components for your system. If you are installing Server Administrator on a non-Dell PowerEdge system, the installer displays only the Server Administrator Web Server option. A selected feature has a hard drive icon depicted next to it. A deselected feature has a red X depicted next to it.
NOTE: If you have selected Remote Enablement during installion, an error message "A provider, WinTunnel, has been registered in the Windows Management Instrumentation namespace ROOT\dcim\sysman to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests." is logged in Windows Event Log. You can safely ignore this message and continue with installation.
The following procedures show how to upgrade Server Administrator and other managed system software. Upgrading Guidelines • You cannot upgrade Server Administrator earlier than version 5.0 to version 6.1. You must upgrade to a Server Administrator version later than 5.0 and then upgrade to Server Administrator version 6.1. • If you have installed Server Instrumentation on the managed system, ensure that you install Server Administrator Web Server version 6.1.
Modify If you want to add/remove Server Administrator components: 1 Navigate to the Windows Control Panel. 2 Double-click Add/Remove Programs. 3 Click Dell OpenManage Server Administrator and click Change. The Welcome to the Install Wizard for Dell OpenManage Server Administrator dialog box appears. 4 Click Next. The Program Maintenance dialog box appears. 5 Select the Modify option and click Next. The Custom Setup dialog box appears.
Repair If you want to repair an installed Server Administrator component that may be damaged: 1 Navigate to the Windows Control Panel. 2 Double-click Add/Remove Programs. 3 Click Dell Server Administrator and click Change. The Welcome to the Install Wizard for Dell OpenManage Server Administrator dialog box appears. 4 Click Next. The Program Maintenance dialog box appears. 5 Select the Repair option and click Next. The Ready to Repair the Program dialog box appears.
or removal, so they can be restored if necessary, which is a type of rollback. After a successful installation finishes, Windows deletes all of the temporary backup files. In addition to the rollback of MSI Standard Actions, the Dell OpenManage library also has the ability to undo commands listed in the INI file for each application if a rollback occurs. All files that are modified by the Dell OpenManage installation actions will be restored to their original state if a rollback occurs.
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Window s\Installer Reg_SZ: Logging Value: voicewarmup The letters in the value field can be in any order. Each letter turns on a different logging mode. Each letter's actual function is as follows for MSI version 3.
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. You can perform an unattended installation by creating an unattended installation package that contains all of the necessary managed system software files.
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 7-1 shows the optional settings available for the msiexec.
Table 7-1. Command Line Settings for MSI Installer (continued) Setting Result /q[n|b|r|f] This command sets the user interface (UI) level. /q or /qn – no UI. This option is used for silent and unattended installation. /qb – basic UI. This option is used for unattended but not silent installation. /qr – reduced UI. This option is used for unattended installation while displaying a modal dialog box showing install progress. /qf – full UI. This option is used for standard attended installation.
Table 7-1. Command Line Settings for MSI Installer (continued) Setting Result INSTALLDIR= This command installs a product to a specific location. If you specify an install directory with this switch, it must be created manually prior to executing the CLI install commands or they will fail with no error or message as to why they failed. /i SysMgmt.msi INSTALLDIR=c:\OpenManage /qn – installs a product to a specific location using c:\OpenManage as the install location. For example, running msiexec.
Table 7-2. Software Feature IDs (continued) Feature ID Description OMSM Storage Management RmtMgmt Remote Enablement RAC4 Remote Access Controller (DRAC 4) RAC5 Remote Access Controller (DRAC 5) iDRAC Integrated Dell Remote Access Controller SA Server Administrator NOTE: Only iDRAC6 is supported on xx1x systems. You can include the ADDLOCAL customization parameter on the command line, and assign the feature ID (or IDs) of the software feature that you would like to install.
You can also choose to install, reinstall, and uninstall features with one execution of the msiexec.exe program. An example is msiexec.exe /i SysMgmt.msi ADDLOCAL=INTEL REMOVE= BRCM /qb This command runs the installation for managed system software, and simultaneously installs the Intel agent, and uninstalls the Broadcom agent. This execution will be in an unattended but not silent mode.
Uninstalling Managed System Software You can uninstall managed system software features by using the Dell Systems Management Tools and Documentation DVD, or your operating system. Additionally, you can simultaneously perform an unattended uninstallation on multiple systems. NOTE: After you uninstall Server Administrator on PowerEdge 1650, 2650, 4600, 700, 750, 800, 830, 850, and 1800 systems, you may be prompted to reboot your system if you have chosen to uninstall Storage Management Service.
5 Click Remove. The Uninstalling Dell OpenManage Server Administrator screen appears and provides the status and progress of the software features being uninstalled. When the selected features are uninstalled, the Install Wizard Completed dialog box appears. 6 Click Finish to exit the Server Administrator uninstallation. If you are prompted to reboot your system, you must reboot your system in order for the uninstallation to be successful.
Unattended Uninstall Using the Product GUID If you do not have the installation DVD or the MSI package available during an uninstallation, you can use the following command line to uninstall Dell OpenManage systems management software on managed systems or management stations running Windows. For these cases, you can use the package GUIDs to uninstall the product. For managed systems, use this command: msiexec.
Unattended Uninstall Command Line Settings Table 7-1 shows the unattended uninstall command line settings available for unattended uninstallation. Type the optional settings on the command line after msiexec.exe /x SysMgmt.msi with a space between each setting. For example, running msiexec.exe /x SysMgmt.msi /qb runs the unattended uninstallation, and displays the unattended installation status while it is running. Running msiexec.exe /x SysMgmt.
Installing Dell OpenManage Software On Microsoft Windows Server 2008 Core and Microsoft Hyper-V Server Introduction The Server Core installation option of the Microsoft® Windows Server® 2008 and Hyper-V™ Server operating system provides a minimal environment for running specific server roles that reduces the maintenance and management requirements and the attack surface for those server roles.
Installing Managed System and Management Station Software This section provides instructions on installing managed system and management station software on Windows Server 2008 Core or Hyper-V Server operating system, in the CLI mode. Running PreReqChecker In CLI Mode Run the PreReqChecker before you install Dell OpenManage software. See "Prerequisite Checker" for more information on running Prerequisite Checker in the CLI mode.
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_.
• Prerequisite checker detects that another MSI package installation is currently running or that a reboot is pending: HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\Windows\Current Version\Installer\InProgress indicates another MSI package installation is in progress. HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\ \Session Manager\\PendingFileRenameOperations indicates that a reboot is pending.
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
Installing Managed System Software on Supported Linux and VMware ESX Server Operating Systems Overview The Dell™ OpenManage™ installer provides installation scripts and RPM packages to install 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.
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®, SUSE® Linux Enterprise Server, and VMware® ESX operating systems.
Determining the Running Kernel 1 Log in as root. 2 Type the following command at a console and press : uname -r The system displays a message identifying the running kernel. If it is not one of those listed in the managed system software readme file, then the managed system software may need to use DKS to support it. Dynamic Kernel Support Prerequisites For managed system software to use DKS, the following dependencies must be met before starting Server Administrator.
Copying a Dynamically Built Device Driver to Systems Running the Same Kernel When Server Administrator dynamically builds a device driver for the running kernel, it installs the device driver into the /lib/modules//kernel/drivers/firmware directory, where is the kernel name (returned by typing uname -r).
NOTE: You can also use this procedure when upgrading Server Administrator if the new version of Server Administrator does not support the running kernel with a precompiled device driver. NOTE: When you have uninstalled Server Administrator from system B, the /var/omsa/dks//*. files that you copied to system B are not removed. You must remove the files if they are no longer needed.
Forcing Dynamic Kernel Support on Red Hat Enterprise Linux Update Releases After the installation of Server Administrator, perform the following steps to force DKS to be used on Red Hat Enterprise Linux Update releases to build device drivers for the running kernel, if needed, so that they do not taint the kernel: 1 Ensure that the prerequisites of DKS are met. 2 Execute the following command: /etc/init.
Server Administrator installation blocks the installation of Server Administrator packages if an appropriate version of the OpenIPMI device driver is not currently installed on the system. However, it is still possible, though not typical, that you can uninstall or replace a sufficient version of the OpenIPMI device driver after Server Administrator has been installed. Server Administrator cannot prevent this.
Installing Base RPMs 1 Check if the base RPMs are already installed. If yes, remove the installed RPMs. 2 Check if the openwsmand and sfcbd binaries are already installed using make-install. You can check by running the commands: #openwsman or #sfcbd or You can check the existence of the above binaries in the /usr/local/sbin directory. 3 If the binaries are installed, uninstall these binaries. 4 Check for the required dependencies for the openwsman and sfcbd RPMs.
The dependencies for sblim-sfcb are: • Zlib • Curl RPM • Pam • Openssl RPM • Chkconfig (aaa_base in the SUSE Linux Enterprise Server operating system) • Initscript (aaa_base in the SUSE Linux Enterprise Server operating system) 5 Install the base RPMs. You can install all the RPMs with a single command. #rpm -ivh rpm1 rpm2 rpm3 rpm4 … rpmN You can also install the RPMs individually. NOTE: If you are installing RPMs individually, follow the sequence below.
Installing Managed System Software This section explains how to install managed system software using the following installation options: • Using the srvadmin-install.sh shell script for express installs or custom installs, in either interactive or unattended mode NOTE: If you have downloaded the managed system software installer (available as a .tar.gz file) from the Dell Support site at support.dell.com, the srvadmin-install.sh shell script is present as setup.sh in the root directory.
• Install all the prerequisite RPMs required for successful installation. If your system had VMware ESX (version 3.5 or 4) factory-installed, Red Hat Enterprise Linux (versions 4 and 5), or SUSE Linux Enterprise Server (version 10 and 11), see the Server Administrator installation readme file (readme_ins.txt) on the Dell Systems Management Tools and Documentation DVD for information on any RPMs that you need to manually install prior to installing managed system software.
3 When you have mounted the DVD, navigate to: cd /mnt/dvdrom/SYSMGMT/srvadmin/linux/ 4 Get a listing of the directories using the ls command.
5 Run the srvadmin-install.sh shell script as shown below, which performs a silent and unattended express installation, the setup program installs following the managed system software features: • • • • sh Server Administrator Web Server Server Instrumentation Storage Management Remote Access Controller srvadmin-install.sh --express or sh srvadmin-install.sh -x Server Administrator services do not start automatically.
Table 9-1.
3 If necessary, mount the DVD using a command such as: mount /dev/dvdrom /mnt/dvdrom. 4 Navigate to the SYSMGMT/srvadmin/linux/custom/, where is ESX35 or ESX40 or RHEL4 or RHEL5 or SLES10 or SLES11. Enter the operating system specific directory corresponding to your system. 5 Type the following command. rpm -ihv Server-Instrumentation/*.rpm add-StorageManagement/*.rpm NOTE: IPMI packages may already be installed on your system and hence may not require re-installation.
[-w|--web] installs Server Administrator Web Server. [-u|--update] updates applicable Server Administrator components. [-h|--help] displays this help text. Options that can be used along with the options above: [-p|--preserve] preserves the screen without clearing off. NOTE: If you do not use the [-p | --preserve] option during the custom installation, the history information on the screen gets cleared off. [-a|--autostart] starts the installed services after components have been installed.
Using the Shell Script to Perform the Custom Installation in Interactive Mode This procedure uses the installation shell script to prompt you for the installation of specific components through the installation. 1 Log in as root to the system running the supported Red Hat Enterprise Linux or SUSE Linux Enterprise Server operating system where you want to install the managed system components. 2 Insert the Dell Systems Management Tools and Documentation DVD into the DVD drive.
After installing all the base RPMs, execute the autoconf_cim_component.sh script. Before executing the autoconf_cim_component.sh script, ensure Dell OpenManage is installed. For information on installing Dell OpenManage see, "Installing Managed System Software." Execute the following command to configure sfbc and openwsman as per the default configurations: #./ autoconf_cim_component.sh Creating Server Certificate for WSMAN You can either create a new certificate for WSMAN or reuse an existing certificate.
Winbind Configuration for openwsman and sfcb for Red Hat Enterprise Linux Operating Systems 1 Take a backup of the following files: • /etc/pam.d/openwsman • /etc/pam.d/sfcb • /etc/pam.d/system-auth 2 Replace the content of /etc/pam.d/openwsman and /etc/pam.d/sfcb with: auth required pam_stack.so service=system-auth auth required /lib/security/pam_nologin.so account required pam_stack.so service=system-auth 3 Replace the content of /etc/pam.d/system-auth with: #%PAM-1.0 # This file is auto-generated.
account [default=bad success=ok user_unknown= ignore] /lib/security/$ISA/pam_winbind.so account required /lib/security/$ISA/pam_permit.so password requisite /lib/security/$ISA/pam_cracklib.so retry=3 password sufficient /lib/security/$ISA/pam_unix.so nullok use_authtok md5 shadow password sufficient /lib/security/$ISA/pam_krb5.so use_authtok password sufficient /lib/security/$ISA/pam_winbind.so use_authtok password required /lib/security/$ISA/pam_deny.so session required /lib/security/$ISA/pam_limits.
3 Replace the content of /etc/pam.d/common-auth with: auth required pam_env.so auth sufficient pam_unix2.so debug auth sufficient pam_winbind.so use_first_pass debug 4 Replace the content of /etc/pam.d/common-account with: account sufficient pam_unix2.so account sufficient pam_winbind.so Workaround for the Libssl Issue If the required library needed by openwsman is present on your system, the autoconf_cim_component.sh script tries to resolve the libssl.so issue.
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.
Creating and Distributing the Custom Unattended Installation Package The Custom Install unattended installation option creates an unattended installation package in a directory on your system's hard drive. To create an unattended installation package, use the copy capability described in the section "Using the Shell Script to Perform the Custom Installation in Interactive Mode" to create a custom directory with the RPM's you want to install. This directory will be your unattended installation directory.
Custom Uninstallation of Specific Components Some individual components of Dell OpenManage can be uninstalled without uninstalling all of Dell OpenManage.
Dell OpenManage on VMware ESXi Software VMware ESXi is factory-installed on some Dell™ systems. For a list of these systems, see the latest Dell Systems Software Support Matrix on the Dell Support website at support.dell.com. You can use Server Administrator Web Server version 6.1 to access VMware ESXi 3.5 update 4 and VMware ESXi 4.0 systems. Dell OpenManage on VMware ESXi 3.5 Update 4 You can use Server Administrator to manage a system with VMware® ESXi virtualization software.
Download VMware vSphere Command Line Interface (vSphere CLI) from http://www.vmware.com and install on your Microsoft Windows or Linux system. Alternately, you can import VMware vSphere Management Assistant (vMA) into your ESXi 4 host. Using the vSphere CLI 1 Copy the em-dell-openmanage-esxi_6.1-0000.zip file to a directory on your system. 2 If you are using Microsoft Windows, navigate to the folder where you have installed the vSphere CLI utilities to execute the command mentioned in step 4.
When you run the command, the following components are installed on your system: • Server Administrator Instrumentation Service • Remote Enablement • Server Administrator Storage Management • Remote Access Controller You must install the Server Administrator Web Server separately on a management station. For information on installing the Server Administrator Web Server, see "Installing Managed System Software on Microsoft Windows Operating Systems.
Enabling Server Administrator Services on the Managed System The Server Administrator Web Server communicates with the VMware ESXi 3.5 system through the Server Administrator Common Interface Model (CIM) provider. The Server Administrator CIM provider is an OEM provider on the VMware ESXi 3.5 system. CIM OEM providers are disabled by default on VMware ESXi 3.5. You must enable the CIM OEM providers on the VMware ESXi 3.5/ESXi 4.0 system before accessing it using Server Administrator Web Server.
Enabling CIM OEM Providers using VMware Infrastructure Remote CLI (for VMware ESXi 3.5) To enable CIM OEM providers using the VI Remote CLI, you need to have the VI Remote CLI tool installed. You can download and install the tool from the VMware website at http://www.vmware.com/go/remotecli/. To enable CIM OEM providers using the VI Remote CLI on Windows: 1 Open a command prompt. 2 Navigate to the directory where the Remote CLIs are installed. The default location is C:\Program Files\VMware\VMware VI Remote
4 In the Advanced Settings dialog box, click UserVars on the left pane. 5 Change the value of the CIMOEMProvidersEnabled field to 1. 6 Click OK. 7 Restart your VMware ESXi 4 host system for the change to take effect. Use the Summary tab in vSphere Client to restart the 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. The management station applications include DRAC Tools, the BMC Utilities, the Microsoft Active Directory® Snap-in Utility, and Dell OpenManage IT Assistant.
Management Station Requirements Microsoft Software Installer (MSI) version 3.1 or later is required on your system. Dell OpenManage software detects the MSI version on your system. If the version is lower than 3.1, the Prerequisite Checker prompts you to upgrade to MSI version 3.1. When installing management station applications on systems running a Windows operating system, you must select a disk drive that has space greater than the required space.
NOTE: If you are running any application on the Dell Systems Management Tools and Documentation DVD, close the application before installing the management station applications. Prerequisite Checker The setup program runs the Prerequisite Checker, which examines the prerequisites for software features without launching the actual installation.
Typical and Custom Installations The management station installer provides two setup options: Typical Setup and Custom Setup. The setup program runs the Prerequisite Checker and provides information about your system’s hardware and software that might affect installation and operation of features.
Installing Management Station On Microsoft Windows operating systems, perform the following steps: 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. NOTE: Microsoft SQL Server 2005 Express requires Microsoft Data Access components 2.8 (MDAC 2.8) and .NET 2.0 Runtime to be installed. The Prerequisite Checker utility will prompt you to install MDAC 2.8 and .NET 2.
7 Select I accept the terms in the license agreement and click Next. The Setup Type dialog box appears. 8 Select Custom and click Next. The Custom Setup dialog box appears. To select a specific management station software application, click the drop-down arrow beside the listed feature and select to either install or not to install the application. To accept the default directory path to install management station software, click Next.
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.
3 Click Next. The Installing Dell OpenManage Management Station screen appears. Messages provide the status and progress of the software features being installed or upgraded. When the selected features are installed or upgraded, the Install Wizard Completed dialog box appears. 4 Click Finish to leave the management station installation. Modify If you want to add/remove management station components: 1 Navigate to the Windows Control Panel. 2 Double-click Add/Remove Programs.
Repair If you want to repair installed management station components that may be damaged: 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.
the course of an installation or removal are temporarily saved to a backup location, so they can be restored if necessary. After an installation finishes successfully, all temporary backup files are deleted. 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.
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
Also, put the batch script in the windows directory on the system hard drive. See “Customization Parameters” for additional details and available feature identification. 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.
Table 11-1. Command Line Settings for MSI Installer Setting Result Installs or configures a product. /i management station software. Uninstalls a product. /x management station software. /q[n|b|r|f] Sets the User Interface (UI) level. /q or /qn – no UI. This option is used for silent and unattended installation. /qb – basic UI.
Table 11-1. Setting Command Line Settings for MSI Installer (continued) Result /f[p|o|e|d|c|a| Repairs a product. u|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 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. Navigate to the SYSMGMT\ManagementStation\windows directory on the DVD and double-click the setup.
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.
Unattended Uninstall Command Line Settings Table 11-1 shows the unattended uninstallation command line settings available for unattended uninstallation. Type the optional settings on the command line after msiexec.exe /x MgmtSt.msi with a space between each setting. For example, running msiexec.exe /x MgmtSt.msi /qb runs the unattended uninstallation and displays the unattended installation status while it is running. Running msiexec.exe /x MgmtSt.
Table 11-2. Feature IDs for the Management Station Feature ID Description ADS Active Directory Snap-in Utility BMU Baseboard Management Controller Management Utility ITA IT Assistant RACMS DRAC Tools NOTE: You have to type the ADDLOCAL, REINSTALL, and REMOVE CLI parameters in upper case as they are case-sensitive. You can include the ADDLOCAL customization parameter on the command line, and assign the feature ID (or IDs) of the software feature that you would like to install.
You can also choose to install, reinstall, and uninstall features with one execution of the msiexec.exe program. An example is msiexec.exe /i MgmtSt.msi ADDLOCAL=ADS REINSTALL= RACMS REMOVE=BMC /qb This command runs the installation for management station and simultaneously installs Active Directory Snap-in Utility, reinstalls Remote Access Controller management station, and uninstalls the Baseboard Management Controller utility. This execution will be in an unattended and verbose mode.
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. Manually remove directories left behind in the default installation directory or the user-specified installation directory. You might also have to manually remove the registry entries under HKEY_LOCAL_MACHINE\SOFTWARE\Dell Computer Cor
3 Navigate to the SYSMGMT/ManagementStation/linux/bmc directory and install the BMC software using the rpm commands specific to the operating system: • For systems running Red Hat Enterprise Linux, use osabmcutil*RHEL-*.rpm, for example, rpm -ivh osabmcutil*-RHEL*.rpm. • For systems running SUSE Linux Enterprise Server, use osabmcutil*-SUSE-*.rpm, for example, rpm -ivh osabmcutil*-SUSE-*.rpm.
3 Navigate to the SYSMGMT/ManagementStation/linux/bmc directory and upgrade the BMC software using the rpm commands specific to the operating system: • For systems running Red Hat Enterprise Linux, use osabmcutil*RHEL-*.rpm, for example, rpm -Uvh osabmcutil*-RHEL*.rpm. • For systems running SUSE Linux Enterprise Server, use osabmcutil*-SUSE-*.rpm, for example, rpm -Uvh osabmcutil*-SUSE-*.rpm.
To uninstall the DRAC Tools feature, 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 DRAC Tools is installed. Use the rpm -qa | grep mgmtst-racadm command. 3 Verify the package version to be uninstalled and uninstall the feature by using the rpm -e `rpm -qa | grep mgmtst-racadm` command.
Using Microsoft Active Directory Controlling Access to Your Network If you use Active Directory® service software, you can configure it to control access to your network. Dell has modified the Active Directory database to support remote management authentication and authorization. Dell™ OpenManage™ IT Assistant and Dell OpenManage Server Administrator, as well as Integrated Dell Remote Access Controllers (iDRAC), Dell Remote Access Controllers (DRAC), can now interface with Active Directory.
Dell extension is: dell Dell base OID is: 1.2.840.113556.1.8000.1280 Dell LinkID range is:12070 to 12079 The Active Directory OID database maintained by Microsoft can be viewed at msdn.microsoft.com/certification/ADAcctInfo.asp by entering our extension, dell. Overview of the Active Directory Schema Extensions Dell created Classes, or groups of objects, that can be configured by the user to meet their unique needs. New Classes in the schema include an Association, a Product, and a Privilege class.
Figure 12-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 12-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 12-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 12-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.
Configuring the Active Directory Product Name To configure the Active Directory product name: 1 Locate the omsaoem.ini file in your installation directory. 2 Edit the file to add the line adproductname=text, where text is the name of the product object that you created in Active Directory. For example, the omsaoem.ini file contains the following syntax if the Active Directory product name is configured to omsaApp.
The LDIF script files and the Dell Schema Extender are located in the following directories on your Dell Systems Management Tools and Documentation DVD: • :\SYSMGMT\ManagementStation\support\OMActiveDirectory_Tools\ \LDIF Files • :\SYSMGMT\ManagementStation\support\OMActiveDirectory_ Tools\ \Schema Extender Table 12-1 list the folder names and . Table 12-1.
To verify the schema extension, use the Active Directory Schema Snap-in in the Microsoft Management Console (MMC) to verify the existence of the following classes (listed in Table 12-2, Table 12-5, Table 12-7, Table 12-8, Table 12-9, and Table 12-10) and attributes (listed in Table 12-11 and Table 12-12). See your Microsoft documentation for more information on how to enable and use the Active Directory Schema Snap-in in the MMC.
Table 12-4. dellPrivileges Class OID 1.2.840.113556.1.8000.1280.1.1.1.4 Description This class is used as a container Class for the Dell Privileges (Authorization Rights). Class Type Structural Class SuperClasses User Attributes dellRAC4Privileges dellRAC3Privileges dellOmsaAuxClass dellItaAuxClass Table 12-5. dellProduct Class OID 1.2.840.113556.1.8000.1280.1.1.1.5 Description This is the main class from which all Dell products are derived.
Table 12-7. 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 12-8. dellIta7AuxClass Class OID 1.2.840.113556.1.8000.1280.1.3.1.
Table 12-10. 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 12-12. IT Assistant-Specific Attributes Added to the Active Directory Schema Attribute Name/Description Assigned OID/Syntax Object Identifier Single Valued dellItaIsReadWriteUser 1.2.840.113556.1.8000.1280.1.3.2.1 TRUE TRUE if the User has Read-Write rights in IT Assistant Boolean (LDAPTYPE_BOOLEAN 1.3.6.1.4.1.1466.115.121.1.7) dellItaIsAdminUser 1.2.840.113556.1.8000.1280.1.3.2.2 TRUE if the User has Administrator rights in IT Assistant Boolean (LDAPTYPE_BOOLEAN 1.3.6.1.4.1.1466.115.121.1.
NOTE: You must install the Administrator Pack on each management station that is managing the new Active Directory objects. The installation is described in the following section, "Opening the Active Directory Users and Computers Snap-In." If you do not install the Administrator Pack, then you cannot view the new object in the container. NOTE: For more information about the Active Directory Users and Computers snap-in, see your Microsoft documentation.
This will connect to the current domain controller. If this is not the Windows 2000 domain controller, then continue with the steps mentioned under "Connecting to a Windows 2000 Server Domain Controller from Another Domain Controller." To open the Active Directory Users and Computers snap-in, perform the following steps: 1 If you are on the domain controller, click Start→Admin Tools→Active Directory Users and Computers.
In the Console Root (MMC) window, right-click a container. 1 Select New. 2 Select a RAC, Server Administrator, or IT Assistant object, depending on which you have installed. The New Object window appears. 3 Type in a name for the new object.
the Association Scope that applies to the type of objects you intend to add. Selecting Universal, for example, means that Association Objects are only available when the Active Directory Domain is functioning in Native Mode or above. 1 In the Console Root (MMC) window, right-click a container. 2 Select New. 3 Select a RAC, Server Administrator, or IT Assistant object, depending on which you have installed. The New Object window appears. 4 Type in a name for the new object. 5 Select Association Object.
To add a privilege: 1 Select the Privileges Object tab and click Add. 2 Type the Privilege Object name or browse for one and click OK. Click the Products tab to add one or more systems or devices to the association. The associated objects specify the products connected to the network that are available for the defined users or user groups. NOTE: You can add multiple systems or RAC devices to an Association Object. To add Products: 1 Select the Products tab and click Add.
NOTE: Restart the Server Administrator service after you have configured Active Directory. Table 12-13 shows the valid parameters for the command. Table 12-13. Active Directory Service Configuration Parameters name=value pair Description prodname= Specifies the software product to which you want to apply the Active Directory configuration changes. Prodname refers to the name of the product defined in omprv32.ini. For Server Administrator, it is omsa.
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 13-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.
NOTE: The software feature IDs mentioned in Table 13-2 and Table 13-3 are casesensitive. Table 13-2. Feature IDs for the Management Station Feature ID Description ADS Microsoft Active Directory® Snap-in Utility ITA Dell OpenManage™ IT Assistant BMC Baseboard Management Controller Management Utility RACMS Remote Access Controller Table 13-3.
Prerequisite Checker
Frequently Asked Questions General Where can I find the quick installation instructions? The Quick Installation Guide comes as a small brochure with the DVD kit. You can also 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.
Microsoft® Windows® How do I fix a faulty installation of Server Administrator? You can fix a faulty installation by forcing a reinstall and then performing an uninstall of Server Administrator. To force a reinstall: • Find out the version of Server Administrator that was previously installed. • Download the installation package for that version from the Dell Support website at support.dell.com. • Locate SysMgmt.msi from the SYSMGMT\srvadmin\windows\SystemsManagement directory and enter the following c
What are the firewall relate configuration that needs to be done for WinRM? With firewall turned ON, WinRM need to be added to the firewall exclusion list to allow TCP port 443 for HTTPS traffic. For more information on TCP ports, see Built-in Security Features. When launching the Dell OpenManage Installer, an error message may display, stating a failure to load a specific library, a denial of access, or an initialization error.
I am getting an error message "An older version of Server Administrator software is detected on this system. You must uninstall all previous versions of Server Administrator applications before installing this version" while launching Dell OpenManage Install? If you see this error when trying to launch Dell OpenManage Install, it is recommended that you run the OMClean.exe program, under the SYSMGMT\srvadmin\support\OMClean directory, to remove an older version of Server Administrator on your system.
I see warning message while uninstalling Server Administrator on Microsoft Windows Server 2008 as the installer tries to remove the shortcut link? While uninstalling Server Administrator on Microsoft Windows Server 2008, you might see a warning message as the installer tries to remove the shortcut link. Click OK on the warning message to continue the uninstallation. How do I perform a silent (unattended) upgrade from Dell OpenManage 5.0 or later to Dell OpenManage 6.
For more detailed information, go to http://msdn.microsoft.com and search for: MEDIAPACKAGEPATH Property. Does Dell OpenManage Installer supports Windows Advertised installation? No. Dell OpenManage Install does not support Windows "Advertised" installation - the process of automatically distributing a program to client computers for installation, through the Windows group policies.
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.
After unattended installation is completed, can I use the same console window to execute CLI commands? No. A new console window must be opened and CLI commands executed from that window after an "Unattended Installation" has completed. Is the time shown during installation/uninstallation by Windows Installer Services is accurate? No. During installation/uninstallation, the Windows Installer Service may display the time remaining for the current task to complete.
Table 14-1.
I have performed a non-default install of your Linux operating system using your Linux operating system media, I see missing RPM file dependencies while installing Server Administrator? Server Administrator is a 32-bit application. When installed on a system running a 64-bit version of Red Hat Enterprise Linux operating system, the Server Administrator remains a 32-bit application, while the device drivers installed by Server Administrator are 64-bit.
I have installed Server Administrator in a non default location, when I uninstall Server Administrator the directories are not deleted, what do I do? If the default install location of Server Administrator has changed during installation, some of the directories in which Server Administrator is installed will not be deleted during its removal. This issue is related to the default behavior of the RPM engine.
In this case, NAME is a feature name, for example omacore. X.Y.Z-N is the version and build number of the feature. Some possible solutions to rectify this problem: 1 Attempt to uninstall again. For example, use the following command: rpm -e srvadmin-NAME-X.Y.Z-N.i386 2 Delete the "upgrade.relocation=bad" line if present in the /etc/omreg.cfg file and attempt to uninstall again. Why am I getting a warning concerning the RPM package key during installation? The RPM files are signed with a digital signature.
Table 14-2.
Table 14-3. Names of the Directories Under the srvadmin/linux/custom/ Directory (continued) Name of RPM Description Other Server Administrator RPMs required srvadmin-deng Server Administrator Data Engine — Systems srvadmin-omilcore management provides a data management framework for systems management software.
Table 14-3. Names of the Directories Under the srvadmin/linux/custom/ Directory (continued) Name of RPM Description Other Server Administrator RPMs required srvadminomilcore Server Administrator Install Core — This is the core install package that provides the tools necessary for the rest of the Systems management install packages. All Server Administrator RPM's require this RPM. srvadminsyscheck Package that checks the level of OpenManage srvadmin-omilcore support.
Table 14-3.
Table 14-3. Names of the Directories Under the srvadmin/linux/custom/ Directory (continued) Name of RPM Description Other Server Administrator RPMs required SA-WebServer — Provides Web access to management of the server srvadmin-hapi Server Administrator Hardware Application Programming Interface — This systems management package provides the device drivers and libraries needed by systems management software to access information about the hardware on supported systems.
Table 14-3. Names of the Directories Under the srvadmin/linux/custom/ Directory (continued) Name of RPM Description Other Server Administrator RPMs required Remote-Enablement — Manage and monitor your current system using some other remote system srvadmin-cm Server Administrator Inventory Collector — Systems management change management inventory collector. srvadmin-omilcore, srvadmin-deng, and srvadmin-omacore.
Table 14-3. Names of the Directories Under the srvadmin/linux/custom/ Directory (continued) Name of RPM Description Other Server Administrator RPMs required srvadminomacore Server Administrator — Systems management srvadmin-omilcore managed mode core and CLI. and srvadmin-deng srvadminomcommon Provides Common Framework required by Server Administrator.
In this case, if you try to install Server Administrator later by running the sh srvadmin-install.sh command, you will get the following message: Server Administrator version X.Y.Z is currently installed. Installed Components are: • srvadmin-omilcore-X.Y.Z-N • srvadmin-hapi-X.Y.Z-N Do you want to upgrade Server Administrator to X.Y.Z? Press (y for yes | Enter to exit): On pressing y, only those Server Administrator packages (in the above example, srvadmin-omilcore-X.Y.Z-N and srvadmin-hapi-X.Y.
Table 14-4. Daemons that run on Red Hat Enterprise Linux and SUSE Linux Enterprise Server once Server Administrator is started Daemon Name Name in Red Hat Enterprise Linux and SUSE Linux Enterprise Server For RPMs in the srvadmin-base directory dsm_sa_datamgr32d DSM SA Data Manager — Server Administrator data manager daemon started by DSM SA Data Engine service. dsm_sa_eventmgr32d DSM SA Event Manager — Server Administrator event and logging daemon started by DSM SA Data Engine service.
Table 14-5.
Glossary The following list defines technical terms, abbreviations, and acronyms used in your system documents. attribute As it relates to an attribute is a piece of information related to a component. Attributes can be combined to form groups. If an attribute is defined as 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.
DRAM Acronym for dynamic random-access memory. A system's RAM is usually made up entirely of DRAM chips. Because DRAM chips cannot store an electrical charge indefinitely, your system continually refreshes each DRAM chip in the system. ERA Abbreviation for embedded remote access. ERA/MC Abbreviation for embedded remote access modular computer. See modular system. ERA/O Abbreviation for embedded remote access option.
Fibre Channel A data transfer interface technology that allows for high-speed I/O and networking functionality in a single connectivity technology. The Fibre Channel Standard supports several topologies, including Fibre Channel Point-to-Point, Fibre Channel Fabric (generic switching topology), and Fibre Channel Arbitrated Loop (FC_AL). firmware Software (programs or data) that has been written onto read-only memory (ROM). Firmware can boot and operate a device.
h Abbreviation for hexadecimal. A base-16 numbering system, often used in programming to identify addresses in the system's RAM and I/O memory addresses for devices. The sequence of decimal numbers from 0 through 16, for example, is expressed in hexadecimal notation as: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, A, B, C, D, E, F, 10. In text, hexadecimal numbers are often followed by h. HBA Abbreviation for host bus adapter.
IDE Abbreviation for Integrated Drive Electronics. IDE is a computer system interface, used primarily for hard drives and CDs. I/O Abbreviation for input/output. The keyboard is an input device, and a printer is an output device. In general, I/O activity can be differentiated from computational activity. For example, when a program sends a document to the printer, it is engaging in output activity; when the program sorts a list of terms, it is engaging in computational activity.
ITE Abbreviation for information technology equipment. Java A cross-platform programming language developed by Sun Microsystems. JSSE Abbreviation for Java Secure Socket Extension. K Abbreviation for kilo-, indicating 1000. Kerberos A network authentication protocol. It is designed to provide strong authentication for client/server applications by using secret-key cryptography. key combination A command requiring you to press multiple keys at the same time.
managed system A managed system is any system that is monitored and managed using Dell OpenManage™ Server Administrator. Systems running Server Administrator can be managed locally or remotely through a supported Web browser. See remote management system. management station A system used to remotely manage one or more managed systems from a central location. math coprocessor See coprocessor. Mb Abbreviation for megabit. MB Abbreviation for megabyte(s).
mm Abbreviation for millimeter(s). MMC Abbreviation for Microsoft Management Console. modular system A system that can include multiple server modules. Each server module functions as an individual system. To function as a system, a server module is inserted into a chassis which includes power supplies, fans, a system management module, and at least one network switch module.
NIS Abbreviation for Network Information Services. NIS is a network naming and administration system for smaller networks. A user at any host can get access to files or applications on any host in the network with a single user identification and password. noninterlaced A technique for decreasing screen flicker by sequentially refreshing each horizontal line on the screen. ns Abbreviation for nanosecond(s), one billionth of a second.
parallel port An I/O port used most often to connect a parallel printer to your system. You can usually identify a parallel port on your system by its 25-hole connector. parameter A value or option that you specify to a program. A parameter is sometimes called a switch or an argument. partition You can divide a hard drive into multiple physical sections called partitions with the fdisk command. Each partition can contain multiple logical drives.
physical memory array mapped The physical memory array mapped refers to the way physical memory is divided. For example, one mapped area may have 640 KB and the other mapped area may have between 1 MB and 127 MB. pixel A single point on a video display. Pixels are arranged in rows and columns to create an image. A video resolution, such as 640 x 480, is expressed as the number of pixels across by the number of pixels up and down.
protected mode An operating mode supported by 80286 or higher microprocessors, protected mode allows operating systems to implement: • A memory address space of 16 MB (80286 microprocessor) to 4 GB (Intel386 or higher microprocessor) • Multitasking • Virtual memory, a method for increasing addressable memory by using the hard drive provider A provider is an extension of a CIM schema that communicates with managed objects and accesses data and event notifications from a variety of sources.
readme file A text file included with a software package or hardware product that contains information supplementing or updating the documentation for the software or hardware. Typically, readme files provide installation information, describe new product enhancements or corrections that have not yet been documented, and list known problems or other things you need to be aware of as you use the software or hardware.
schema A collection of class definitions that describes managed objects in a particular environment. A CIM schema is a collection of class definitions used to represent managed objects that are common to every management environment, which is why CIM is called the Common Information Model. SCSI Acronym for small computer system interface. An I/O bus interface with faster data transmission rates than standard ports. You can connect up to seven devices (15 for some newer SCSI types) to one SCSI interface.
service tag number A bar code label that identifies each system in the event that you need to call for customer or technical support. shadowing A computer's system and video BIOS code is usually stored on ROM chips. Shadowing refers to the performance-enhancement technique that copies BIOS code to faster RAM chips in the upper memory area (above 640 KB) during the boot routine. SIMM Acronym for single in-line memory module. A small circuit board containing DRAM chips that connects to the system board.
SVGA Abbreviation for super video graphics array. VGA and SVGA are video standards for video adapters with greater resolution and color display capabilities than previous standards. To display a program at a specific resolution, you must install the appropriate video drivers and your monitor must support the resolution. Similarly, the number of colors that a program can display depends on the capabilities of the monitor, the video driver, and the amount of video memory installed in the system.
System Setup program A BIOS-based program that allows you to configure your system's hardware and customize the system's operation by setting such features as password protection and energy management. Some options in the System Setup program require that you reboot the system (or the system may reboot automatically) in order to make a hardware configuration change. Because the System Setup program is stored in NVRAM, any settings remain in effect until you change them again. system.
TFTP Abbreviation for Trivial File Transfer Protocol. TFTP is a version of the TCP/IP FTP protocol that has no directory or password capability. text mode A video mode that can be defined as x columns by y rows of characters. threshold values Systems are normally equipped with various sensors that monitor temperature, voltage, current, and fan speed.
TSOP Abbreviation for thin small outline package. A very thin, plastic, rectangular surface mount chip package with gull-wing pins on its two short sides. UDP Abbreviation for user datagram protocol. UMB Abbreviation for upper memory blocks. unicode A fixed width, 16-bit world wide character encoding, developed and maintained by the Unicode Consortium. upper memory area The 384 KB of RAM located between 640 KB and 1MB.
the formula for specifying a unique identifier for the objects defined in that enterprise's MIB. variable A component of a managed object. A temperature probe, for example, has a variable to describe its capabilities, its health or status, and certain indexes that you can use to help you in locating the right temperature probe. VGA Abbreviation for video graphics array. VGA and SVGA are video standards for video adapters with greater resolution and color display capabilities than previous standards.
video driver A program that allows graphics-mode application programs and operating systems to display at a chosen resolution with the desired number of colors. A software package may include some "generic" video drivers. Any additional video drivers may need to match the video adapter installed in the system. video memory Most VGA and SVGA video adapters include memory chips in addition to your system's RAM.
VMS Acronym for Virtual Media Server. VNC Acronym for Virtual Network Computing. In a VNC system, servers provide applications, data, and the desktop environment, all of which may be accessed through the Internet. VRAM Acronym for video random-access memory. Some video adapters use VRAM chips (or a combination of VRAM and DRAM) to improve video performance. VRAM is dual-ported, allowing the video adapter to update the screen and receive new image data at the same time. W Abbreviation for watt(s).
win.ini file A start-up file for the Windows operating system. When you start Windows, it consults the win.ini file to determine a variety of options for the Windows operating environment. Among other things, the win.ini file records what printer(s) and fonts are installed for Windows. The win.ini file also usually includes sections that contain optional settings for Windows application programs that are installed on the hard drive.
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. Some systems use ZIF sockets and connectors to allow devices such as the microprocessor chip to be installed or removed with no stress applied to the device.
Index A attribute, 209 access read-only, 38 write, 38 authentication, 23, 39, 164 access control, 37 Active Directory, 23, 37, 40, 52, 164, 169, 176, 181-182 object identifiers, 163 objects, 165 schema, 170 schema extender utility, 170-171 schema extensions, 163 ADDLOCAL, 96-97, 156 administrator, 38 Administrator Pack, 177 Administrator privileges, 38 agent, 60 SNMP, 52 AGP, 209 alert log, 21 Altiris, 102, 132 ASCII, 209 authorization, 164 B Baseboard Management Controller, 16, 195, 199 Baseboard Man
certificates Web, 68 certification, 22 Certification Authority, 68 chip, 210 CI/O, 210 CIM, 21, 37, 49, 53 CIM protocol, 158 Citrix, 85 D DAT, 211 data redundancy, 15 dB, 211 DCOM, 25-26, 28 Dell, 75, 164 Dell base OID, 164 Dell organizational unit, 170 CLI, 21, 39, 96, 187 Dell Remote Access Controller, 165 cm, 210 Dell Support website, 20 command line, 97 dellIta7AuxClass, 174 command line interface, 21, 39 dellItaApplication, 174 Common Information Model, 21, 49 dellOmsaApplication, 174 confi
Dynamic Kernel Support, 110 I INI file, 89 E encryption, 37 ERA, 22 ERA/MC, 22 ERA/O, 22 express setup, 49, 142 inoperable system, 21 installation management station, 142, 146 unattended, 91, 148, 150 Instrumentation, 39 instrumentation service, 198 integrated NIC, 16 F fault logging, 16 firewall, 23, 37, 61 FTP, 25, 29 Intelligent Platform Management Interface, 16 IPMI, 16 shell, 16 ISV, 92, 101, 129-130, 150, 155 IT Assistant, 168, 187, 195 G Globally Unique Identifier (GUID), 98 group privileges, 3
M notification, 12 managed system, 11-12, 49 management information base, 21, 57 management object format, 21 management objects, 21 management station, 11-12, 16, 49, 56, 139, 142, 146 Management Station Services, 195 MIB, 21, 57 Microsoft Active Directory, 23, 37, 40, 52, 176 Software Installer, 89 Windows Installer Engine, 141 O oem.
proxy server, 52 restoration, 88 RMC, 24 Q Quick Installation Guide, 187 R RMCP, 24 role-based access control, 37 authority, 23 RPC, 25, 27 RPM, 109, 121, 195 RAC, 22, 49, 163, 170, 179-180 devices, 164 installation, 49 software, 49 S racadm, 22-23 SAS, 15 RAID, 46 SATA, 15 RAID controllers, 13 schema, 163, 170-171 RBAC, 37 SchemaExtenderOem.
server proxy, 52 SSL, 40, 169 Server Administrator, 20, 168, 198 Services, 121, 195 standard action, 88 session timeout, 66 Storage Management Service, 195 setup custom, 142 express, 49, 142 setup.
user ID, 23 user levels, 39 utilities Baseboard Management Controller (BMC) Management Utility, 159 racadm, 22 schema extender utility, 170-171 V VNC, 30, 232 W Web certificates, 68 Windows Installer Engine, 93 Installer Service, 89 Windows Management Instrumentation, 49 WMI, 49, 53 write access, 38 X X.
Index
