Dell OpenManage Version 4.3 Installation and Security User's Guide
Dependencies and Prerequisites
Configuring a Supported Web Browser
X.509 Certificate Management Prerequisites
Secure Port Server and Security Setup
Firewall Configuration on Systems Running Supported Red
Hat Enterprise Linux Operating Systems
The following sections describe the Dell OpenManage Systems Management software general requirements. Operating system-specific installation prerequisites are listed as part of the installation procedures.
Dell OpenManage Systems Management software runs, at a minimum, on each of the following operating systems:
|
NOTE: Support for updated kernels released by Red Hat and for later versions of Red Hat Enterprise Linux may require the use of Dynamic Kernel Support (see "Dynamic Kernel Support (DKS)" for a description of this feature). |
Dell OpenManage Server Administrator software must be installed on each system to be managed. You can then manage each system running Server Administrator locally or remotely through a supported Web browser.
|
NOTE: The RAC software is installed as part of the Express Setup and Custom Setup installation options when installing managed system software from the Installation and Server Management CD provided that the managed system meets all of the RAC installation prerequisites. See "Remote Access Controller Service" and the Dell Remote Access Controller Installation and Setup Guide or the Dell Embedded Remote Access/MC Controller User's Guide for complete software and hardware requirements. |
|
NOTE: IT Assistant supports the Mozilla 1.7.3 browser only on systems running Red Hat Enterprise Linux. |
A supported systems management protocol standard must be installed on the managed system before installing your management station or managed system software. On supported Microsoft Windows operating systems, Dell OpenManage software supports these two systems management standards: Common Information Model/Windows Management Instrumentation (CIM/WMI) and Simple Network Management Protocol (SNMP). On supported Red Hat Enterprise Linux and Novell NetWare operating systems, Dell OpenManage software supports the SNMP systems management standard.
|
NOTE: For information about installing a supported system management protocol standard on your managed system, see your operating system documentation. |
Table 3-1 shows the availability of the systems management standards for each supported operating system.
Table 3-1. Availability of Systems Management Protocol by Operating Systems
Upgrades from Dell OpenManage Software versions 1.x and 2.x are not supported. You must manually uninstall Dell OpenManage Software versions 1.x and 2.x before launching the Dell OpenManage Software installation. The installer will notify you if it detects Dell OpenManage Software versions 1.x and 2.x on the system.
The following sections provide instructions for configuring the supported Web browsers. For a list of supported Web browsers, see "Supported Web Browser Requirements."
If you are connecting to a Web-based interface from a management station that connects to the Internet through a proxy server, you need to configure the Web browser to connect properly. If you are using Microsoft's Internet Explorer browser, follow these steps:
Configure other browsers for the same functionality.
When using Internet Explorer or Netscape Navigator on systems running Microsoft Windows, to view localized versions of the Web-based interface, do the following:
To ensure critical system component security, you must properly assign user privileges to all Dell OpenManage software users before installing Dell OpenManage software.
The following sections provide step-by-step instructions for creating users and assigning user privileges for each supported operating system.
|
NOTICE: To protect access to your critical system components, you must assign a password to every user account that can access Dell OpenManage software. |
|
NOTICE: You should disable guest accounts for supported Microsoft Windows operating systems in order to protect access to your critical system components. See "Disabling Guest and Anonymous Accounts in Supported Windows Operating Systems" for instructions. |
|
NOTE: You must be logged in with Administrator privileges to perform these procedures. |
The following procedures create user accounts, assign user privileges, and add users to domains.
|
NOTE: For questions about creating users and assigning user group privileges, or for more detailed instructions, see your operating system documentation. |
|
NOTICE: You must assign a password to every user account that can access Dell OpenManage software to protect access to your critical system components. Additionally, users who do not have an assigned password cannot log into Dell OpenManage software on a system running Windows Server 2003 due to operating system constraints. |
New users can log into Dell OpenManage software with the user privileges for their assigned group.
|
NOTE: For questions about creating users and assigning user group privileges, or for more detailed instructions, see your operating system documentation. |
|
NOTICE: You must assign a password to every user account that can access Dell OpenManage software to protect access to your critical system components. Additionally, users who do not have an assigned password cannot log into Dell OpenManage software on a system running Windows Server 2003 because of operating system constraints. |
New users can log into Dell OpenManage software with the user privileges for their assigned group.
|
NOTE: For questions about creating users and assigning user group privileges or for more detailed instructions, see your operating system documentation. |
|
NOTE: You must have Active Directory installed on your system to perform the following procedures. See "Microsoft Active Directory" for more information about using Active Directory. |
|
NOTICE: You must assign a password to every user account that can access Dell OpenManage software to protect access to your critical system components. Additionally, users who do not have an assigned password cannot log into Dell OpenManage software on a system running Windows Server 2003 due to operating system constraints. |
New users can log into Dell OpenManage software with the user privileges for their assigned group and domain.
|
NOTE: You must be logged in with Administrator privileges to perform this procedure. |
A red circle with an X appears over the user name. The account is disabled.
|
NOTE: Consider renaming the accounts so that remote scripts cannot enable the accounts using the name. |
Administrator access privileges are assigned to the user logged in as root. To create users with User and Power User privileges, perform the following steps.
|
NOTE: You must be logged in as root to perform these procedures. |
|
NOTE: You must have the useradd utility installed on your system to perform these procedures. |
|
NOTE: For questions about creating users and assigning user group privileges, or for more detailed instructions, see your operating system documentation. |
useradd -d <home-directory> -g <group> <username>
where <group> is not root.
|
NOTE: If <group> does not exist, you must create it by using the groupadd command. |
|
NOTICE: You must assign a password to every user account that can access Dell OpenManage software to protect access to your critical system components. |
The new user can now log in to Dell OpenManage software with User group privileges.
useradd -d <home-directory> -g root <username>
|
NOTE: You must set root as the primary group. |
|
NOTICE: You must assign a password to every user account that can access Dell OpenManage software to protect access to your critical system components. |
The new user can now log in to Dell OpenManage software with Power User group privileges.
|
NOTE: For questions about creating users and assigning user group privileges or for more detailed instructions, see your operating system documentation. |
|
NOTICE: You must assign a password to every user account that can access Dell OpenManage software to protect access to your critical system components. |
An icon labeled with the new user name appears in the current container.
By default, three entries in the Assigned Rights category are available: Login Script, Print Job Configuration, and [All Attribute Rights].
New users can now log into Dell OpenManage software with User privileges.
|
NOTICE: You must assign a password to every user account that can access Dell OpenManage software to protect access to your critical system components. |
An icon labeled with the new user name appears in the current container.
New users can now log into Dell OpenManage software with Power User privileges.
|
NOTICE: You must assign a password to every user account that can access Dell OpenManage software to protect access to your critical system components. |
An icon labeled with the new user name appears in the current container.
By default, three entries in the Assigned Rights category are available: Login Script, Print Job Configuration, and All Attribute Rights.
New users can now log into Dell OpenManage software with Administrator privileges.
If you use Microsoft 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. IT Assistant and Server Administrator, as well as Dell remote access controllers, can now interface with Active Directory. With this tool, you can add and control users and privileges from one central database.
|
NOTE: Using Active Directory to recognize RAC, IT Assistant, or Server Administrator users is supported on the Microsoft Windows 2000 and Windows Server 2003 operating systems. |
The Active Directory data exists in a distributed database of Attributes and Classes. An example of a Active Directory Class is the User class. Some example Attributes of the user class might be the user's first name, last name, phone number, and so on. Every Attribute or Class that is added to an existing Active Directory schema must be defined with a unique ID. To maintain unique IDs throughout the industry, Microsoft maintains a database of Active Directory Object Identifiers (OIDs).
The Active Directory schema defines the rules for what data can be included in the database. To extend the schema in Microsoft's Active Directory, Dell received unique OIDs, unique name extensions, and unique linked attribute IDs for the new attributes and classes in the directory service.
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 http://msdn.microsoft.com/certification/ADAcctInfo.asp by entering our extension, Dell.
Dell created Classes, or groups of objects, that can be configured by the user to meet their unique needs. New Classes in the schema include an Association, a Product, and a Privilege class. An Association object links the users or groups to a given set of privileges and to systems (Product Objects) in your network. This model gives an administrator control over the different combinations of users, privileges, and systems or RAC devices on the network, without adding complexity.
For each of the systems that you want to integrate with Active Directory for Authentication and Authorization, there must be at least one Association Object and one Product Object. The Product Object represents the system. The Association Object links it with users and privileges. You can create as many Association Objects as you need.
Each Association Object can be linked to as many users, groups of users, and Product Objects as desired. The users and Product Objects can be from any domain. However, each Association Object may only link to one Privilege Object. This behavior allows an Administrator to control which users have which rights on specific systems.
The Product Object links the system to Active Directory for authentication and authorization queries. When a system is added to the network, the Administrator must configure the system and its product object with its Active Directory name so that users can perform authentication and authorization with Active Directory. The Administrator must also add the system to at least one Association Object in order for users to authenticate.
Figure 3-1 illustrates that the Association Object provides the connection that is needed for all of the Authentication and Authorization.
Typical Setup for Active Directory Objects
In addition, you can set up Active Directory objects in a single domain or in multiple domains. Setting up objects in a single domain does not vary, whether you are setting up RAC, Server Admistrator, or IT Assistant objects. When multiple domains are involved, however, there are some differences.
For example, you have two DRAC 4 cards (RAC1 and RAC2) and three existing Active Directory users (user1, user2, and user3). You want to give user1 and user2 an Administrator privilege on both DRAC 4 cards and give user3 a Login privilege on the RAC2 card. Figure 3-2 shows how you set up the Active Directory objects in this scenario.
Setting Up Active Directory Objects in a Single Domain
To set up the objects for the single domain scenario, perform the following tasks:
See "Adding Users and Privileges to Active Directory" for detailed instructions.
Figure 3-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.
Setting Up RAC Active Directory Objects in Multiple Domains
To set up the objects for this multiple domain scenario, perform the following tasks:
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. The following is a very similar example to show how Server Administrator or IT Assistant systems in separate domains affect the setup of directory objects. Instead of RAC devices, you'll have two systems running Server Administrator (Server Administrator Products sys1 and sys2). Sys1 and sys2 are in different domains. You can use any existing Users or Groups that you have in Active Directory. Figure 3-3 shows how to set up the Server Administrator Active Directory objects for this example.
Setting Up Server Administrator Active Directory Objects in Multiple Domains
To set up the objects for this multiple domain scenario, perform the following tasks:
Note that neither of the Association objects needs to be of Universal scope in this case.
Before you can use Active Directory to access your systems, you must configure both the Active Directory software and the systems.
RAC, Server Administrator, and IT Assistant schema extensions are available. You only need to extend the schema for software or hardware that you are using. Each extension must be applied individually to receive the benefit of its software-specific settings. Extending your Active Directory schema will add schema classes and attributes, example privileges and association objects, and a Dell organizational unit to the schema.
|
NOTE: Before you extend the schema, you must have Schema Admin privileges on the Schema Master Flexible Single Master Operation (FSMO) Role Owner of the domain forest. |
You can extend your schema using two different methods. You can use the Dell Schema Extender utility, or you can use the Lightweight Directory Interchange Format (LDIF) script file.
|
NOTE: The Dell organizational unit will not be added if you use the LDIF script file. |
The LDIF script files and Dell Schema Extender are located on your Dell OpenManage Installation and Server Management CD in the following respective directories:
where installation type will be either RAC4, RAC3, Dell OpenManage Server Administrator, or IT Assistant version 7.0, depending on your choice of schema extension.
To use the LDIF files, see the instructions in the readme that is in the LDIF files directory. To use the Dell Schema Extender to extend the Active Directory Schema, perform the steps in "Using the Dell Schema Extender."
You can copy and run the Schema Extender or LDIF files from any location.
|
NOTICE: The Dell Schema Extender uses the SchemaExtenderOem.ini file. To ensure that the Dell Schema Extender utility functions properly, do not modify the name or the contents of this file. |
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 3-2, Table 3-3, Table 3-4, Table 3-5, Table 3-6, Table 3-7, Table 3-8, Table 3-9, Table 3-10, Table 3-11, Table 3-12, and Table 3-13) and attributes (listed in Table 3-14, Table 3-15, and Table 3-16). See your Microsoft documentation for more information on how to enable and use the Active Directory Schema snap-in in the MMC.
Table 3-2. Class Definitions for Classes Added to the Active Directory Schema
|
Class Name | Assigned Object Identification Number (OID) | Class Type |
|---|---|---|
dellRacDevice | 1.2.840.113556.1.8000.1280.1.1.1.1 | Structural Class |
dellAssociationObject | 1.2.840.113556.1.8000.1280.1.1.1.2 | Structural Class |
dellRAC4Privileges | 1.2.840.113556.1.8000.1280.1.1.1.3 | Auxiliary Class |
dellPrivileges | 1.2.840.113556.1.8000.1280.1.1.1.4 | Structural Class |
dellProduct | 1.2.840.113556.1.8000.1280.1.1.1.5 | Structural Class |
dellRAC3Privileges | 1.2.840.113556.1.8000.1280.1.1.1.6 | Auxiliary Class |
dellOmsa2AuxClass | 1.2.840.113556.1.8000.1280.1.2.1.1 | Auxiliary Class |
dellOmsaApplication | 1.2.840.113556.1.8000.1280.1.2.1.2 | Structural Class |
dellIta7AuxClass | 1.2.840.113556.1.8000.1280.1.3.1.1 | Auxiliary Class |
dellItaApplication | 1.2.840.113556.1.8000.1280.1.3.1.2 | Structural Class |
Table 3-3. dellRacDevice Class
|
OID | 1.2.840.113556.1.8000.1280.1.1.1.1 |
|---|---|
|
Description | This class represents the Dell RAC device. The RAC Device must be configured as dellRacDevice in Active Directory. This configuration enables the DRAC 4 to send LDAP queries to Active Directory. |
|
Class Type | Structural Class |
|
SuperClasses | dellProduct |
|
Attributes | dellSchemaVersion |
Table 3-4. dellAssociationObject Class
|
OID | 1.2.840.113556.1.8000.1280.1.1.1.2 |
|---|---|
|
Description | This class represents the Dell Association Object. The Association Object provides the connection between the users and the devices or products. |
|
Class Type | Structural Class |
|
SuperClasses | Group |
|
Attributes | dellProductMembers dellPrivilegeMember |
Table 3-5. dellRAC4Privileges Class OID 1.2.840.113556.1.8000.1280.1.1.1.3 Description This class is used to define the privileges (Authorization Rights) for the DRAC 4 device. Class Type Auxiliary Class SuperClasses None Attributes dellIsLoginUser dellIsCardConfigAdmin dellIsUserConfigAdmin dellIsLogClearAdmin dellIsServerResetUser dellIsConsoleRedirectUser dellIsVirtualMediaUser dellIsTestAlertUser dellIsDebugCommandAdmin
Table 3-6. 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 |
|
OID | 1.2.840.113556.1.8000.1280.1.1.1.5 |
|---|---|
|
Description | This is the main class from which all Dell products are derived. |
|
Class Type | Structural Class |
|
SuperClasses | Computer |
|
Attributes | dellAssociationMembers |
Table 3-8. dellRAC3Privileges Class
|
OID | 1.2.840.113556.1.8000.1280.1.1.1.6 |
|---|---|
|
Description | This class is used to define the privileges (Authorization Rights) for the DRAC III, DRAC III/XT, ERA, ERA/O, and ERA/MC devices. |
|
Class Type | Auxiliary Class |
|
SuperClasses | None |
|
Attributes | dellIsLoginUser |
Table 3-9. dellOmsa2AuxClass Class
|
OID | 1.2.840.113556.1.8000.1280.1.2.1.1 |
|---|---|
|
Description | This class is used to define the privileges (Authorization Rights) for Server Administrator. |
|
Class Type | Auxiliary Class |
|
SuperClasses | None |
|
Attributes | dellOmsaIsReadOnlyUser dellOmsaIsReadWriteUser dellOmsaIsAdminUser |
Table 3-10. dellOmsaApplication Class
|
OID | 1.2.840.113556.1.8000.1280.1.2.1.2 |
|---|---|
|
Description | This class represents the Server Administrator application. Server Administrator must be configured as dellOmsaApplication in Active Directory. This configuration enables the Server Administrator application to send LDAP queries to Active Directory. |
|
Class Type | Structural Class |
|
SuperClasses | dellProduct |
|
Attributes | dellAssociationMembers |
Table 3-11. dellIta7AuxClass Class
|
OID | 1.2.840.113556.1.8000.1280.1.3.1.1 |
|---|---|
|
Description | This class is used to define the privileges (Authorization Rights) for IT Assistant. |
|
Class Type | Auxiliary Class |
|
SuperClasses | None |
|
Attributes | dellItaIsReadOnlyUser dellItaIsReadWriteUser dellItaIsAdminUser |
Table 3-12. dellItaApplication Class
|
OID | 1.2.840.113556.1.8000.1280.1.3.1.2 |
|---|---|
|
Description | This class represents the IT Assistant application. IT Assistant must be configured as dellItaApplication in Active Directory. This configuration enables IT Assistant to send LDAP queries to Active Directory. |
|
Class Type | Structural Class |
|
SuperClasses | dellProduct |
|
Attributes | dellAssociationMembers |
Table 3-13. General Attributes Added to the Active Directory Schema
Table 3-14. RAC-specific Attributes Added to the Active Directory Schema
Table 3-15. Server Administrator-Specific Attributes Added to the Active Directory Schema
Table 3-16. IT Assistant-Specific Attributes Added to the Active Directory Schema
When you extend the schema in Active Directory, you must also extend the Active Directory Users and Computers snap-in so that the administrator can manage Products, Users and User Groups, Associations, and Privileges. You only need to extend the snap-in once, even if you have added more than one schema extension. You must install the snap-in on each system that you intend to use for managing these objects. The Dell Extension to the Active Directory Users and Computers Snap-In is an option that can be installed when you install your systems management software using the Dell OpenManage Installation and Server Management CD.
|
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. |
To open the Active Directory Users and Computers snap-in, perform the following steps:
The Microsoft Management Console (MMC) window opens.
The Dell-extended Active Directory Users and Computers snap-in allows you to add DRAC, Server Administrator, and IT Assistant users and privileges by creating RAC, Association, and Privilege objects. To add an object, perform the steps in the applicable subsection.
|
NOTE: Server Administrator and IT Assistant users must use Universal-type Product Groups to span domains with their product objects. |
In the Console Root (MMC) window, right-click a container.
The New Object window opens.
Privilege Objects must be created in the same domain as the Association Object to which they are associated.
The New Object window opens.
The Association Object is derived from a Group and must contain a group Type. The Association Scope specifies the Security Group Type for the Association Object. When you create an Association Object, you must choose 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.
The New Object window opens.
By using the Association Object Properties window, you can associate users or user groups, privilege objects, systems, RAC devices, and system or device groups.
|
NOTE: RAC users must use Universal Groups to span domains with their users or RAC objects. |
You can add groups of Users and Products. You can create Dell-related groups in the same way that you created other groups.
To add Users or User Groups:
Click the Privilege Object tab to add the privilege object to the association that defines the user's or user group's privileges when authenticating to a system.
|
NOTE: You can add only one Privilege Object to an association object. |
To add a privilege:
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:
If you plan to use Microsoft Enterprise Root CA to automatically assign all your domain controllers SSL certificates, you must perform the following steps to enable SSL on each domain controller.
|
NOTE: The following steps may vary slightly if you are using Windows 2000. |
|
NOTE: If the DRAC 4 firmware SSL certificate is signed by a well-known CA, you do not need to perform the steps described in this section. |
|
NOTE: The following steps may vary slightly if you are using Windows 2000. |
If you have installed your own certificate, ensure that the CA signing your certificate is in the Trusted Root Certification Authority list. If the CA is not in the list, you must install it on all your Domain Controllers.
For instructions on how to configure your Server Administrator or IT Assistant systems using CLI commands, see "Configuring Active Directory Using CLI on Systems Running Server Administrator" and "Configuring Active Directory on Systems Running IT Assistant." For DRAC users, there are two ways to configure DRAC 4. See either "Configuring the DRAC 4 Using the Web-Based Interface" or "Configuring the DRAC 4 Active Directory Settings Using the racadm CLI."
|
NOTE: The systems on which Server Administrator and/or IT Assistant are installed must be a part of the Active Directory domain and should also have computer accounts on the domain. |
You can use the omconfig preferences dirservice command to configure the Active Directory service. The <product>oem.ini file is modified to reflect these changes. If the adproductname is not present in the <product>oem.ini file, a default name will be assigned. The default value will be <system name>-<software-product name>, where <system name> is the name of the system running Server Administrator, and <software-product name> refers to the name of the software product defined in omprv32.ini (that is, computerName-omsa).
|
NOTE: This command is applicable only on systems running the Windows operating system. |
|
NOTE: Restart the Server Administrator service after you have configured Active Directory. |
Table 3-17 shows the valid parameters for the command.
Table 3-17. Active Directory Service Configuration Parameters
By default, the Active Directory product name corresponds to the <machinename>-ita, where <machinename> is the name of the system on which IT Assistant is installed. To configure a different name, locate the itaoem.ini file in your installation directory. Edit the file to add the line "adproductname=<text>" where <text> is the name of the product object that you created in Active Directory. Here is a sample itaoem.ini file with the Active Directory product name configured as mgmtStationITA.
productname=IT Assistant
startmenu=Dell OpenManage Applications
autdbid=ita
accessmask=3
startlink=ITAUIServlet
adsupport=true
adproductname=mgmtStationITA
|
NOTE: Restart the IT Assistant services after saving the itaoem.ini file to the disk. |
Using the following commands to configure the DRAC 4 Active Directory feature using the racadm CLI instead of the Web-based interface.
racadm config -g cfgActiveDirectory -o cfgADEnable 1
racadm config -g cfgActiveDirectory -o cfgADRacDomain <fully qualified rac domain name>
racadm config -g cfgActiveDirectory -o cfgADRootDomain <fully qualified root domain name>
racadm config -g cfgActiveDirectory -o cfgADRacName <RAC common name>
racadm sslcertupload -t 0x2 -f <ADS root CA certificate>
racadm sslcertdownload -t 0x1 -f <RAC SSL certificate>
racadm config -g cfgLanNetworking -o cfgDNSServersFromDHCP 1
racadm config -g cfgLanNetworking -o cfgDNSServersFromDHCP 0
racadm config -g cfgLanNetworking -o cfgDNSServer1 <primary DNS IP address>
racadm config -g cfgLanNetworking -o cfgDNSServer2 <secondary DNS IP address>
See the Dell Remote Access Controller 4 User's Guide for more information.
Dell OpenManage software supports the Simple Network Management Protocol (SNMP) systems management standard on all supported operating systems. In most cases, SNMP is installed as part of your operating system installation. An installed supported systems management protocol standard, such as SNMP, is required before installing Dell OpenManage software. See "Installation Requirements" for more information.
You can configure the SNMP agent to change the community name, enable Set operations, and send traps to a management station. To configure your SNMP agent for proper interaction with management applications such as the IT Assistant and Array Manager, perform the procedures described in the following sections.
|
NOTE: For IT Assistant to retrieve management information from a system running Server Administrator, the community name used by IT Assistant must match a community name on the system running Server Administrator. For IT Assistant to modify information or perform actions on a system running Server Administrator, the community name used by IT Assistant must match a community name that allows Set operations on the system running Server Administrator. For IT Assistant to receive traps (asynchronous event notifications) from a system running Server Administrator, the system running Server Administrator must be configured to send traps to the system running IT Assistant. For more information, see the IT Assistant User's Guide. |
The following sections provide step-by-step instructions for configuring the SNMP agent for each supported operating system:
Dell OpenManage software uses the SNMP services provided by the Windows SNMP agent. (SNMP is one of the two supported ways of connecting to a System Administrator session; the other is CIM/WMI.) You can configure the SNMP agent to change the community name, enable Set operations, and send traps to a management station. To configure your SNMP agent for proper interaction with management applications such as IT Assistant and Array Manager, perform the procedures described in the following sections.
|
NOTE: See your operating system documentation for additional details on SNMP configuration. |
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 a system running the Windows Server 2003 operating system to receive SNMP packets from a remote host, perform the following steps:
The Computer Management window appears.
The SNMP Service Properties window appears.
Configuring the SNMP community names determines which systems are able to manage your system through SNMP. The SNMP community name used by management applications must match an SNMP community name configured on the Dell OpenManage software system so that the management applications can retrieve management information from Dell OpenManage software.
The Computer Management window appears.
The SNMP Service Properties window appears.
The SNMP Service Configuration window appears.
The SNMP Service Properties window appears.
The SNMP Service Configuration window appears.
The SNMP Service Properties window appears.
SNMP Set operations must be enabled on the Dell OpenManage software system to change Dell OpenManage software attributes using IT Assistant.
The Computer Management window opens.
The SNMP Service Properties window appears.
The SNMP Service Configuration window opens.
The SNMP Service Properties window opens.
Dell OpenManage software generates SNMP traps in response to changes in the status of sensors and other monitored parameters. You must configure one or more trap destinations on the Dell OpenManage software system for SNMP traps to be sent to a management station.
The Computer Management window opens.
The SNMP Service Properties window opens.
Type in the trap destination and click Add.
The SNMP Service Properties window opens.
Server Administrator uses the SNMP services provided by the ucd-snmp or net-snmp agent. You can configure the SNMP agent to change the community name, enable Set operations, and send traps to a management station. To configure your SNMP agent for proper interaction with management applications such as IT Assistant and Array Manager, perform the procedures described in the following sections.
|
NOTE: See your operating system documentation for additional details about SNMP configuration. |
The management information base (MIB) branch implemented by the Server Administrator Instrumentation Service is identified by the 1.3.6.1.4.1.674.10892.1 OID. Management applications must have access to this branch of the MIB tree to manage systems running the Instrumentation Service.
For Red Hat Enterprise Linux operating systems, the default SNMP agent configuration gives read-only access for the "public" community only to the MIB-II "system" branch (identified by the 1.3.6.1.2.1.1 OID) of the MIB tree. This configuration does not allow management applications to retrieve or change Instrumentation Service or other systems management information outside of the MIB-II "system" branch.
If Server Administrator detects this 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 .1
The second change is to modify the default "access" line to give read-only access to the entire MIB tree for the "public" community. Server Administrator looks for the following line:
access notConfigGroup "" any noauth exact systemview none none
If Server Administrator finds the line above, it modifies the line so that it reads:
access notConfigGroup "" any noauth exact all none none
These changes to the default SNMP agent configuration give read-only access to the entire MIB tree for the "public" community.
|
NOTE: To ensure that Server Administrator is able to modify the SNMP agent configuration to provide proper access to systems management data, it is recommended that any other SNMP agent configuration changes be made after installing Server Administrator. |
Configuring the SNMP community names determines which systems are able to manage your system through SNMP. The SNMP community name used by management applications must match an SNMP community name configured on the Dell OpenManage software system, so the management applications can retrieve management information from Dell OpenManage software.
To change the SNMP community name used for retrieving management information from a system running Dell OpenManage software, edit the SNMP agent configuration file, /etc/snmp/snmpd.conf, and perform the following steps:
com2sec publicsec default public
or
com2sec notConfigUser default public
com2sec publicsec default community_name
or
com2sec notConfigUser default community_name
service snmpd restart
SNMP Set operations must be enabled on the system running Dell OpenManage software in order to change Dell OpenManage software attributes using IT Assistant.
To enable SNMP Set operations on the system running Dell OpenManage software, edit the /etc/snmp/snmpd.conf SNMP agent configuration file and perform the following steps:
access publicgroup "" any noauth exact all none none
or
access notConfigGroup "" any noauth exact all none none
access publicgroup "" any noauth exact all all none
or
access notConfigGroup "" any noauth exact all all none
service snmpd restart
Dell OpenManage software generates SNMP traps in response to changes in the status of sensors and other monitored parameters. One or more trap destinations must be configured on the system running Dell OpenManage software for SNMP traps to be sent to a management station.
To configure your system running Dell OpenManage software to send traps to a management station, edit the /etc/snmp/snmpd.conf SNMP agent configuration file and perform the following steps:
trapsink IP_address community_name
where IP_address is the IP address of the management station and community_name is the SNMP community name
service snmpd restart
Dell OpenManage software uses the SNMP services provided by the NetWare SNMP agent. You can configure the SNMP agent to change the community name, enable Set operations, and send traps to a management station. To configure your SNMP agent for proper interaction with management station applications such as IT Assistant and Array Manager, perform the following tasks.
|
NOTE: See your operating system documentation for additional details on SNMP configuration. |
The SNMP community name used by management applications must match an SNMP community name configured on the system running Dell OpenManage software, so the management station applications can retrieve management information from Dell OpenManage software.
To change the SNMP community name used for retrieving management information from a Dell OpenManage software system, perform the following steps:
The Internetworking Configuration menu opens.
The Manage Configuration menu opens.
The SNMP Parameters menu opens.
The Monitor Community Handling menu choices are Any Community May Read, Leave as Default Setting, No Community May Read, and Specified Community May Read.
|
NOTE: Press <F1> for more information about the Monitor State menu item. Press <Esc> to clear the help window. |
A message box opens, prompting you to save changes.
The Manage Configuration menu opens.
The Internetworking Configuration menu opens.
SNMP Set operations must be enabled on the system running Dell OpenManage software in order to change Dell OpenManage software attributes using IT Assistant.
To enable SNMP Set operations on the system running Dell OpenManage software, perform the following steps:
The Internetworking Configuration menu opens.
The Manage Configuration menu opens.
The SNMP Parameters menu opens.
The Control Community Handling menu choices are Any Community May Write, Leave as Default Setting, No Community May Write, and Specified Community May Write.
|
NOTE: Press <F1> for more information about the Control State menu item. Press <Esc> to clear the help window. |
A message box opens, prompting you to save changes.
The Manage Configuration menu opens.
The Internetworking Configuration menu opens.
Dell OpenManage software generates SNMP traps in response to changes in the status of sensors and other monitored parameters. One or more trap destinations must be configured on the system running Dell OpenManage software for SNMP traps to be sent to a management station.
To configure a system running Dell OpenManage software to send SNMP traps to a management station, perform the following steps:
The Internetworking Configuration menu opens.
The Manage Configuration menu opens.
The SNMP Parameters menu opens.
The Trap Handling menu choices are Do Not Send Traps, Leave as Default Setting, and Send Traps With Specified Community.
|
NOTE: Press <F1> for more information about the Trap State menu item. Press <Esc> to clear the help window. |
A message box opens, prompting you to save changes.
The Manage Configuration menu opens.
The Internetworking Configuration menu opens.
The Protocol Configuration menu opens.
The TCP/IP Protocol Configuration menu opens.
The SNMP Manager Table menu opens.
|
NOTE: Press <F1> for more information about the SNMP Manager Table menu item. Press <Esc> to clear the help window. |
A message box opens, prompting you to update the database.
The TCP/IP Protocol Configuration menu opens.
The Internetworking Configuration menu opens.
Web certificates are necessary to ensure the identity of a remote system and to ensure that information exchanged with the remote system cannot be viewed or changed by others.
This section explains the administrative prerequisites for ensuring your ability to generate a new X.509 certificate, reuse an existing X.509 certificate, or import a root certificate or certificate chain from Certification Authority (CA) on each supported operating system.
The X.509 certificate management is provided through the Dell OpenManage software home page for all supported operating systems except NetWare 5.1. Additionally, NetWare 5.1 is the only supported operating system that has installation prerequisites to allow certificate management. See "Prerequisites for Systems Running NetWare Version 5.1."
The X.509 certificate management for systems running NetWare version 5.1 (with Service Pack 5 or later) requires that the following procedures be performed before installing Dell OpenManage software:
|
NOTE: PKIS, SAS, and NICI are installed by default. If any of these products are not currently installed, you must install the product from your Novell NetWare 5.1 operating system CD. After installation, you must reapply the correct support patch. |
After installing Dell OpenManage software, go to "Secure Port Server and Security Setup" to complete the X.509 certificate management procedures.
This section contains the following topics:
You set user and secure port server preferences from the Preferences home page (the web server settings page available under for Server Administrator and IT Assistant).
|
NOTE: You must be logged in with Admin privileges to set or reset user or server preferences. |
Perform the following steps to set up your user preferences:
The Preferences home page appears.
|
NOTE: Clicking Email in any window sends an e-mail message with an attached HTML file of the window to the designated e-mail address. |
Perform the following steps to set up your secure port server preferences:
The Preferences home page appears.
|
NOTE: Changing the port number to an invalid or in-use port number might prevent other applications or browsers from accessing Server Administrator on the managed system. |
|
NOTE: Changing the IP Address to Bind to value to a value other than All may prevent other applications or browsers from accessing Server Administrator on the managed system. |
|
NOTE: For security reasons, your company or organization might not allow e-mails to be sent through the SMTP server to outside accounts. |
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).
|
NOTE: You must be logged in with Admin privileges to perform certificate management. |
To manage X.509 certificates through the Preferences home page, click General Settings, click the Web Server tab, and click X.509 Certificate.
Use the X.509 certificate tool to either generate a new X.509 certificate, reuse an existing X.509 certificate, or import a root certificate or certificate chain from a CA. Authorized CAs include Verisign, Entrust, and Thawte.
Using ConsoleOne, you can create or recreate a server certificate if yours becomes corrupted.
|
NOTE: Back up your critical server certificate information before beginning the following procedures. |
To create a new server certificate signed by the NDS Organizational CA, perform the following steps:
Double-click ConsoleOne.
The New Object window appears.
The Create Server Certificate (KeyMaterial) window appears. The Standard creation method is selected by default.
nssl.keystore = certificate name - hostname
where certificate name is the name of the certificate you just created and hostname is the name of the managed system running NetWare
The Security Alert window appears.
The Certificate window appears. A white cross in a red circle appears over the certificate icon at the top of the window. This icon indicates that the certificate cannot be verified to a trusted certificate authority.
Information about the organizational CA is displayed.
The Certificate Manager Import Wizard appears.
The Automatically select the certificate store based on the type of certificate option is selected by default.
The Root Certificate Store window appears.
A window informs you that the import was successful.
The Java plug-in will now recognize the certificate as valid.
The Systems Management Log in window opens with a yellow lock (in the locked position) at the bottom corner of the window.
To create a new server certificate signed by an external Organizational Authority, perform the following steps:
The New Object window appears.
The Create Server Certificate window appears. The Standard creation method is selected by default.
ConsoleOne generates a Certificate Signing Request (CSR).
The Save Certificate Signing Request window appears.
The CA returns two files: one is the root certificate and the other is a response in a Public Key Cryptography Standard #7 (PKCS#7) format.
nssl.keystore = certificate name - hostname
where certificate name is the name of the certificate you just created and hostname is the name of the managed system running Novell NetWare.
The next time you log into Server Administrator, the Java plug-in recognizes the certificate as signed by an external trusted certificate authority.
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. If Server Administrator detects that the SNMP port is not open in the firewall for any external network interface, Server Administrator displays a warning message and logs a message to the system log. See "Ports" for additional information.
You can open the SNMP port by disabling the firewall, opening an entire external network interface in the firewall, or opening the SNMP port for at least one external network interface in the firewall. You can perform this action before or after Server Administrator is started.
To open the SNMP port using one of the previously described methods, perform the following steps:
|
NOTE: This command is available only if you have performed a default installation of the operating system. |
The Choose a Tool menu opens.
The Firewall Configuration screen opens.
|
NOTE: Press <F1> for more information about the firewall security levels. The default SNMP port number is 161. If you are using the X Windows GUI, pressing <F1> might not provide information about firewall security levels on newer versions of Red Hat Enterprise Linux. |
The Firewall Configuration - Customize screen opens.
The Firewall Configuration screen opens.
The Choose a Tool menu opens.