Skip Headers
Oracle® Enterprise Manager Lifecycle Management Administrator's Guide
12c Release 4 (12.1.0.4)

E27046-26
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

32 Administering Hosts

As you monitor your host, you will find that the host needs to be fine-tuned to perform at optimum levels. This chapter explains how to administer your host to reap the best performance. In particular, this chapter explains:

32.1 Configuration Operations on Hosts

There are a number of configuration operations you can perform on hosts to enhance their effectiveness. These operations include:

To access the configuration operations explained in this section, perform the following steps:

  1. From the Targets menu, select either All Targets or Hosts.

  2. Either type the name of the desired host in the Search field or scroll down to the name of the host in the Name column.

  3. Click the name of the host.

  4. From the Host menu, select Monitoring, then Metric and Collection Settings.

Follow the instructions for each configuration explanation.

32.1.1 Configuring File and Directory Monitoring Criteria

Enterprise Manager monitors the files and directories for the operator-specified criteria on hosts running various flavors of the UNIX operating system. The operator should configure the criteria for monitoring the desired files and directories.

Operator should specify the criteria for file and directory monitoring using the Monitoring Settings Page.

To configure the file and directory monitoring criteria, do the following:

  1. On the Metric and Collection Settings page, select All metrics in the View menu. Locate the File and Directory Monitoring metrics. The metrics are:

    • File or Directory Attribute Not Found

    • File or Directory Permissions

    • File or Directory Size (MB)

    • File or Directory Size Change Rate (KB/minute)

  2. After reviewing each metric, decide which metrics need to change. Click the pencil icon to navigate to the corresponding Edit Advanced Settings page.

  3. You can specify new criteria for monitoring by clicking Add on this page. Refer to Notes about Specifying Monitored Objects for details on configuring the criteria.

  4. You can edit or remove existing criteria by selecting the row from the Monitored Objects table and clicking Edit or Remove.

Notes about Specifying Monitored Object

File or Directory Name specifies the criteria to be monitored. Each row in the Monitored Object table specifies a unique criteria to be monitored.

File or Directory Name is the name of the file or directory being monitored from the host operating system. Specified value should correspond to the absolute path for the desired file or directory.

Either exact name or name with SQL wild cards (% and _) can be specified for File or Directory Name. SQL wild card matches 0 or more characters. SQL wild card _ matches exactly one character.

32.1.2 Configuring Generic Log File Monitor Criteria

Enterprise Manager monitors the log files for the occurrence of operator-specified patterns that the owner of the Management Agent software is able to read. You can use this facility for monitoring abnormal conditions recorded in the log files present on the host.

Log files are periodically scanned for the occurrence of desired patterns and an alert is raised when the pattern occurs during a given scan. During a scan, new content created since the last scan is searched for the occurrence of the desired patterns.

The operator should specify the criteria for log file monitoring using the Metric and Collection Settings Page. To configure the log file monitoring criteria, first identify the monitoring criteria using the form <log file name, match pattern in perl, ignore pattern in perl>.

Perform the following steps using the Enterprise Manager console:

  1. Search for Log File Pattern Matched Line Count in the table displayed for Metrics with Thresholds filter. Click the pencil icon in this row to navigate to the Edit Advanced Settings: Log File Pattern Matched Line Count page.

  2. You can edit or remove existing criteria by selecting the row from the Monitored Objects table and clicking Edit or Remove. Refer to Notes about Specifying Monitored Objects for details on configuring the criteria.

Optionally, perform the following steps directly in the ORACLE_HOME directory of the Management Agent present on the managed host.

  1. By default, matching number of lines is reported through log file monitoring. To enable upload of matching content for a specific file, add the absolute path for the file to the $ORACLE_HOME/sysman/admin/lfm_ifiles file. The $ORACLE_HOME/sysman/admin/lfm_ifiles.template file is a template needed for creating the $ORACLE_HOME/sysman/admin/lfm_ifiles file.

  2. For security purposes, you may want to disable monitoring of sensitive files by Enterprise Manager permanently by adding the names of the sensitive files to the $ORACLE_HOME/sysman/admin/lfm_efiles file. The $ORACLE_HOME/sysman/admin/lfm_efiles.template file is a template needed for creating the $ORACLE_HOME/sysman/admin/lfm_efiles file.

Notes about Specifying Monitored Object

The set of columns (Log File Name, Match Pattern In Perl, Ignore Pattern In Perl) uniquely specifies the criteria to be monitored. Each row in the Monitored Object table specifies a unique criteria to be monitored. Multiple criteria can exist against the same log file.

Column Description
Log File Name In this column, specify the absolute path for the log file to be monitored. SQL wild characters can be used for specifying multiple file names.

Examples:

(a) /orahome/log/f1.log This value would monitor single log file.(b) /orahome/log/%.log This value would monitor all files with suffix .log in /orahome/log directory.

Match Pattern in Perl In this column, specify the pattern to be matched for. Perl expressions are supported.

This column specifies the pattern that should be monitored in the log file. During each scan, the file is scanned for occurrence of the specified match pattern [with case ignored].

Example:

(a) Pattern Value = ERROR This pattern will be true for any line containing error

(b) Pattern Value = .*fan.*error.* This pattern will be true for lines containing fan and error

Ignore Pattern in Perl This column specifies the ignore pattern. In the given Log file, line containing the match pattern will be ignored if the ignore pattern is contained in that line.

In this column, specify any pattern that should be ignored. Perl expressions are supported.

If nothing needs to be ignored, specify %

Time Stamp If this column is present, always specify it to be %.

32.1.3 Configuring Program Resource Utilization Monitoring Criteria

Enterprise Manager monitors the CPU resources consumed by the combination of <program name, owner> on hosts running various flavors of UNIX operating systems. The operator should configure the criteria for monitoring the resources consumed. This facility can be used for usage tracking of CPU resources.

The operator should specify the criteria for program resource utilization monitoring by using the Monitoring Settings Page.

To configure the program resource utilization criteria, do the following:

  1. On the Metric and Collection Settings page, select All metrics in the View menu. Locate the Program Resource Utilization metrics. The metrics are:

    • Program's Max CPU Time Accumulated (Minutes)

    • Program's Max CPU Utilization (%)

    • Program's Max Process Count

    • Program's Max Resident Memory (MB)

    • Program's Min Process Count

    • Program's Total CPU Time Accumulated (Minutes)

    • Program's Total CPU Utilization (%)

  2. After reviewing each metric, decide which metrics need to change. Click the pencil icon to navigate to the corresponding Edit Advanced Settings page.

  3. You can edit or remove existing criteria by selecting the row from the Monitored Objects table and clicking Edit or Remove. Refer to Notes about Specifying Monitored Objects for details on configuring the criteria.

Notes about Specifying Monitored Object

Set of <Program Name, Owner> specifies the criteria to be monitored. Each row in the Monitored Object table specifies an unique criteria to be monitored.

Column Description
Program Name Program name is the name of the command being executed on the host operating system. On UNIX systems, ps command displays the name for each process being executed.Either exact name or name with SQL wild cards (% and _) can be specified for program name. SQL wild card matches 0 or more characters. SQL wild card _ matches exactly one character.
Owner Owner is the name of the user running the given process on the host operating system. On UNIX systems, ps command displays the name for each process being executed.Either exact name or name with SQL wild cards (% and _) can be specified for owner. SQL wild card matches 0 or more characters. SQL wild card _ matches exactly one character.

32.2 Administration Tasks

The Administration tab gives you access to all the administrative tasks you can perform on this host. With the categories listed, you can easily access the appropriate pages for system services, network connections, and user and group settings.The tasks include starting services, setting users, and configuring network cards.

Using the Administration tab, you can manage:

  • Services

    View statistics of individual service and edit their services.

    Note: This feature is only available on hosts running Oracle Linux, Red Hat Linux and SUSE Linux Operating Systems (x86 and x64 architectures only).

  • Default System Run Level

  • Network Cards

    Manage routing configuration, view configuration statistics, and view network file system clients.

  • Host Lookup Table

  • NFS Client

  • User and Group Administration

    Manage user and group settings.

Note: For Linux systems, to perform administration tasks on these items, you must have YAST and EM Wrapper Scripts installed. See the Required Installations section of the Setting Up the Environment to Monitor Hosts chapter for information.

To access the administration tasks explained in this section, perform the following steps:

  1. From the Targets menu, select either All Targets or Hosts.

  2. Either type the name of the desired host in the Search field or scroll down to the name of the host in the Name column.

  3. Click the name of the host.

  4. From the Host menu, select Administration, then the entity on which you want to make changes.

Note: To see a video showing the navigation in the Administration menu option, see http://www.youtube.com/watch?v=ROfqR2GhQ_E.

32.2.1 Services

The Services page provides a list of all the services and their statistics for this host. This page enables you to:

  • Start, stop, and restart services

  • Access the page that allows you to edit the properties of individual services.

  • View the current system run level. When no run level is defined for the service, the service uses the current system run level.

  • Determine whether the service is enabled and view the service run levels:

    Run Level Description
    0 System halt
    1 Single user mode

    Only one user can be logged on at any point in time. Additional users will not be allowed to log on until the user using the system logs off.

    2 Basic multiuser mode without network
    3 Full multiuser mode with network
    4 This run level is for future Oracle use.
    5 Full multiuser mode with network and X display manager
    6 System reboot

Note: Be aware that you must restart the system for the run level to take effect.

32.2.2 Default System Run Level

The Default System Run Level page allows you to change the run level that the system uses when it reboots. The change to the system run level takes effect after the system reboots.

Run Level Description
0 System halted.
1 Single user mode
2 Basic multiuser mode without network
3 Full multiuser mode with network
4 Unused. This run level is for future Oracle use.
5 Full multiuser mode with network and X display manager
6 Reboot the system.

Note the following:

  • Click Change to change the host credentials. You must have SUDOER credentials to complete the Default System Run Level operation. If you do not have SUDOER credentials, this button provides the opportunity to change credentials.

  • Click Cancel to abandon the changes and return to the Host Administration page.

  • Click Save to keep the changes made to the default system run level and return to the Host Administration page.

  • You need to install the YAST toolkit to use the Default System Run Level feature. See Required Installations.

The run levels are not immediately affected and hence the default run level and current run level may be different if the system has not been rebooted.

Caution:

The default run level is a powerful tool. You should only change the default system run level if you have sufficient knowledge and experience. Changing the default system run level inappropriately could result in improper system functionality after rebooting.

32.2.3 Network Card

The Network Card page provides detailed information on the network cards in your enterprise. With this information, you can decide whether edits need to be made to global domain name system (DNS) settings and routing table configuration.

Using the Network Card page, you can:

  • Configure, enable, and disable network cards

  • View the device name and IP address of the network card used by Enterprise Manager

  • View the DNS settings and click Edit to change the global DNS settings for the listed domains.

  • Edit a default gateway if it is available, or click Add to define a routing configuration.

Notes

Note the following:

  • Click Done to exit the page without making any changes.

  • Click Change to edit the credentials used for this page.

Configuring the Network Card

Use the Configure Network Card page to change the specifications of the network card. Using this page, you can:

  • Opt to use either of the following setup methods: Static Address Setup or Automatic Address Setup using DHCP.

  • Add the IP Address

  • Add Subnet Mask information

  • Maximum Transfer Unit (Bytes)

Adding Routing Configuration

Use the Add Routing Configuration page to add either a gateway or network device for routing requests. Using this page, you can:

  • Specify the Gateway to use

  • Specify the network Device to use

  • When configuring routing to a network, specify the Netmask and Destination

32.2.4 Host Lookup Table

The Host Lookup Table page displays the mapping of IP address to a host name or its aliases. Using this page, you can:

  • Edit hostname and aliases

  • Delete a lookup table entry for a host

  • Add a lookup table entry for a host by accessing the Add Host Configuration page.

Note the following:

  • A host can have one or more aliases.

  • Click Done to exit the page without making any changes.

  • Click Change to edit the credentials used for this page. You do not need to reboot for changes to take effect.

  • Each alias should be comma-separated.

32.2.5 NFS Client

The NFS Client page provides a list of all the network file system (NFS) clients mounted on the current host. Using this page, you can:

  • Mount, unmount, and delete clients

  • Access the page that allows you to edit the properties of individual clients

  • Access the page that allows you to add NFS clients to the host

  • View the statistics of the various clients

    Client Statistic Description
    Server Hostname of the remote NFS server
    Remote File System Location of the remote file system
    Mount Point Local mount point
    Mounted Indicates whether the remote file system is mounted.
    Persist Over Reboot Retains mount points between reboots.
    Options Displays mount options.

Note the following:

  • Click Done to exit the page without making any changes and returning to the previous page.

  • Click Change to edit the host credentials used for this page.

Adding and Editing an NFS Client

The Add and Edit NFS Client pages provide the ability to mount a file system on a remote NFS server to a location on a local host. Using these pages, you can create and edit an NFS mount by providing:

  • The local mount point

  • The name of the NFS Server host name

  • The location of the remote file system

  • Mount options

Options
ro
rsize=32768
wsize=32768
acregmin=1200
acregmax=1200
acdirmin=1200
acdirmax=1200
hard
intr
tcp
lock
rw
nosuid
nodev

Note the following:

  • Click Cancel to ignore all changes and return to the NFS Client page.

  • Click OK to accept all changes made. All changes are implemented immediately.

  • Check Persist Over Reboot to ensure mounts are available between reboots

32.2.6 User and Group Administration (Users)

The User and Group Administration (Users) page provides a list of all the user accounts on this host along with their statistics. On this page you can:

  • Access the page to edit user account statistics

  • Access the page to add a user account to the host

  • Delete a user account from the host

  • View the statistics of specific user accounts

    User Statistic Description
    Login User account name that allows you to access the software
    Name Full name of user account

    Many logins can have the same name. For example, logins aim1, aim2, and aim3 can all have the same name - AIM Manager.

    UID User account identifier

    This identifier is unique to the login.

    Groups Categories to which the user account belongs

    User account inherits the permissions given to the group.


Adding or Editing a Local User

This option enables you to add and edit a user account to this host. The following table describes the fields.

Group Information Description
User's Full Name Full name of user account
Username Name used as login
Password In conjunction with the username, a set of characters that allows access to this host

The password must be no shorter than 5 characters and no longer than 72 characters. If you have changed the user's password, ensure you inform the user of this change.

Confirm Password The password typed in this field must be exactly as the password typed in the Password field

If the confirm password does not match the password typed in the Password field, either retype the password or define a new password and confirm it.

User ID (UID) User identifier

This identifier is unique to the user account. The ID must be a whole number greater than 499.

Home Directory Ensure the home directory begins with a slash (/)
Additional User Information Enter any additional user information
Login Shell Select the Login Shell from the list of available shells from the drop-down list
Default Group Select the default group from the drop-down list of available groups
Group Memberships Groups to which the user account belongs

Group names are separated by a comma. Do not include any spaces. An example: adm,daemon,root


When editing a local user, you can:

  • Change the password

  • Change the profile information, for example, the default group

32.2.7 User and Group Administration (Groups)

The User and Group Administration (Groups) page provides a list of all the groups on the host and their statistics. Using this page, you can:

  • Access the page to edit group statistics

  • Access the page to add a group to the host

  • Delete a group from the host

  • View the statistics of particular groups

Group Statistic Description
Group Name Name of the group
Group ID Group identifier. This identifier is unique to the group.
Group Members Groups that belong to the group. Group shares the permissions given to the subordinate groups.

Note: This feature is only available on Linux.

Adding or Editing a Local Group

The Add New Local Group page provides you the opportunity to add a group to this host. On the Add New Local Group page, you can add information for the fields listed in the following table:

Group Information Description
Group Name Name of the group
Group ID Group identifier. This identifier is unique to the group.
Group Members Groups that belong to this group. Group shares the permissions given to the subordinate groups. Group names are separated by a comma. Do not include any spaces: for example, adm,daemon,root

When editing a local group, you can:

  • Change the group ID

  • Add, delete, or change group members

32.3 Using Tools and Commands

There are a number of tools and commands available to you to facilitate your administration of hosts. This section introduces you to:

  • Sudo and Power Broker

  • Host Command

  • Remote File Editor

32.3.1 Enabling Sudo and Power Broker

The sudo command is a program for UNIX-like operating systems that allows users to run programs with the security privileges of another user (normally the root user). It also provides auditing capabilities.

PowerBroker is a tool used for restricting the type of commands that can be run by users and maintains an audit trail of what users have done or have tried to do. PowerBroker allows for policy-defined authorization controls which allow administrators to define where and when their end-users can access other accounts they are authorized to use, up to and including root.

To enable Sudo or PowerBroker, perform these steps:

  1. From the Setup menu located at the top-right of the page, select Security then select Named Credentials.

  2. On the Named Credentials page, click Create.

  3. On the Create Credential page, provide host credentials with root privileges.

  4. In the Credential Properties section, select Sudo or PowerBroker from Run Privilege.

  5. Provide the details for Sudo or PowerBroker and the system performs the administrative task.

Using Sudo or Power Broker

To use Sudo or Power Broker as Linux administrator, perform the following steps:

  • Navigate to the Host target page.

  • View list of administration activities on Host target.

  • Select an administration task.

  • Provide host credentials with root privileges. Provide information for Sudo (runas) support or Power Broker (profile) support.

  • Provide the details and the system performs the administrative task.

32.3.2 Executing the Host Command Using Sudo or PowerBroker

To execute Host command using Sudo or PowerBroker, perform these steps:

  1. Navigate to the Host target page.

    From the Targets menu, select Hosts. On the Hosts page, click the name of the host in which you are interested.

  2. Click the Run Host Command button.

  3. Provide host target credentials. Provide information for Sudo (runas) support or PowerBroker (profile) support.

    Note: On the target host, the /etc/sudoers file needs to be present with the target user information inserted.

  4. Type the specific command to be run on the system and view the command output.

32.3.3 Remote File Editor

The Remote File Editor enables you to view and edit text files on the remote host. For example, using this utility, you can update the contents of configuration files on the remote host. In addition, you can:

  • With the appropriate privileges, view and edit any text file present on the remote host.

  • Save a file that has been edited on the remote host by clicking Save.

  • Save the contents to a different file on the remote host by clicking Save a Copy.

  • Change to another user account or use another set of Host Preferred Credentials by clicking Change next to User.

  • After you have opened a file for editing, select a new file for editing by clicking Change next to File Name.

  • Revert to text at the time of the last successful save operation by clicking Revert.

Accessing Remote File Editor

To navigate to the Remote File Editor, perform the following steps:

  1. From the Targets menu, select Hosts. On the Hosts page, click the name of the host in which you are interested.

  2. On the resulting Host home page, select Remote File Editor from the Host menu (located at the top-left of the page).

  3. If the preferred credentials are not set for the host target, the Host Credentials page appears. Three options are available: Preferred, Named, and New.

    You must have permissions to perform operations on a target host.

  4. Once credentials are set, you can perform the following on the Remote File Editor page:

    • Perform operations on files, for example, listing of files in a directory, opening a file for reading, editing, and saving.

    • Provide host target credentials.

    • Provide details of the file and type of operation to be done.

Notes

Note the following:

  • The file must be an ASCII text file and cannot be larger than 100 KB.

  • In the case where the credential check is successful, the file exists and you have read privilege on the file, the file content is loaded for editing.

  • If you do not have write privilege, you will not be able to save the file. Click Save a Copy and save the file to a directory on which you have write privilege.

  • In the case the file does not exist but you have write privilege on the directory, a new empty file is opened for text input.

32.4 Adding Host Targets

To add a host target, install the Oracle Management Agent on the host computer you want to manage.

Detailed information is available in:

32.5 Running Host Command

The Host Command enables you to interactively perform administrative operations on a single host, multiple hosts, or group composed of multiple hosts. For example, using this command the DBA can list the contents of some common directory of a set of hosts.

32.5.1 Accessing Host Command

To access the Execute Host Command page to perform administrative operations on hosts, do the following:

  1. From the Targets menu, select either All Targets or Hosts.

  2. Either type the name of the desired host in the Search field or scroll down to the name of the host in the Name column.

  3. Click the name of the host. Enterprise Manager displays the Home page for the host.

  4. From the Host menu, select Execute Host Command.

  5. On the Host Credentials page, type the user name and password for the host.

  6. The Execute Host Command page appears.

32.5.2 Executing Host Command Using Sudo or Power Broker

To execute the Host Command using Sudo or Power Broker, perform the following steps:

  • Navigate to the Host target page.

  • Run the command on the host target.

  • Provide host target credentials. Provide information for Sudo (runas) support or Power Broker (profile) support.

  • Type a specific command to be run on the system and view the command output.

Note: If the credentials (with runas Sudo/PowerBroker) are not set, then you will be prompted to create credentials. To create credentials, select Security from the Setup menu, then select either Named Credentials or Preferred Credentials.

32.5.3 Execute Host Command - Multiple Hosts

The Execute Host Command page enables you to type operating system commands against multiple hosts and immediately view the results. This gives you the opportunity to perform administrative operations on multiple hosts within the context of Enterprise Manager.

On this page, you can:

  • Refine the command, reexecute the command, and view the execution results, all on the same page.

  • Either type operating system commands, load the commands from a script on the browser machine or on the host, or load host commands from a job defined in the job library.

  • Select hosts individually or through the use of a group. You can also switch to Single Target Mode where only one host target is acted upon.

  • Interactively view command execution results or hide the results to be viewed at a later time.

  • Use preferred credentials or override preferred credentials.

  • Add targets and modify the targets list.

Note the following:

  • Reexecute the command by clicking Execute.

  • Cancel execution of the command is possible when the Processing: Executing Host Command page appears.

  • Execution history reflects the host commands that have been executed in the current Execute Host Command session, as well as any host commands executed in previous sessions that were executed with the 'Keep the execution history for this command' option chosen.

  • Clicking Add launches the Target Selection page with the target type list limited to host targets and any groups that contain host targets.

  • When saving the OS script or execution results, the saved file is located on the browser machine.

  • No more than 500 lines appear in the history list.

  • At most, 10 rows of command execution results data will be displayed in the targets table. If more data is returned, click the Execution Status icon in the table or click Complete Execution Results.

  • When switching from multiple to single target mode, the first host in the targets table will be used.

32.5.3.1 Target Properties

The host command is executed using the Enterprise Manager job system. The job system allows you to specify system variables called target properties. The supported target properties are listed in the following table. Note that the available properties change according to the type of target the job is run against.

Name Description Target Type
%emd_root% Location of Management Agent Host, Database Instance
%perlbin% Location of Perl binary used by Management Agent Host, Database Instance
%TargetName% Target Name Host, Database Instance
%TargetType% Target Type Host, Database Instance
%orcl_gtp_comment% Comment Host, Database Instance
%orcl_gtp_contact% Contact Host, Database Instance
%orcl_gtp_deployment_type% Deployment Type Host, Database Instance
%orcl_gtp_line_of_bus% Line of Business Host, Database Instance
%orcl_gtp_location% Location Host, Database Instance
%OracleHome% Oracle home path Database Instance
%Port% Port Database Instance
%SID% Database SID Database Instance
%Role% Database Role Database Instance
%MachineName% Listener Machine Name Database Instance

Note the following:

  • Property names are case-sensitive.

  • Properties can be used in both the Command and OS Script fields.

  • To use the % character without a target property, escape it with a second %.

  • To use the Database Instance target type, launch Execute Host Command from a group containing one or more host targets and switch the Target Type.

Examples:

To execute a Perl script, passing in the target name as an argument, enter the following in the Command field: %perlbin%/perl myPerlScript %TargetName%

To execute a program in the directory identified by the TEMP environment variable on a Windows host: %%TEMP%%/myProgram

32.5.4 Execute Host Command - Group

The Execute Host Command page enables you, in the context of a group, to type operating system commands against multiple hosts and immediately view the results. This gives you the opportunity to perform administrative operations on multiple hosts within the context of Enterprise Manager.

On this page, you can:

  • Choose the target type. You can choose hosts directly, or choose hosts by way of database instance targets.

  • Refine the command, reexecute the command, and view the execution results, all without leaving the page.

  • Either type operating system commands, load the commands from a script on the browser machine or on the host, or load host commands from a job defined in the job library.

  • Select hosts individually or through the use of a group. You can also switch to Single Target Mode where only one host target is acted upon.

  • Interactively view command execution results or hide the results to be viewed at a later time.

  • Use preferred credentials or override preferred credentials.

  • Add targets and modify the targets list.

Notes

Note the following:

  • Reexecute the command by clicking Execute.

  • Cancel execution of the command by clicking Cancel on the Processing: Executing Host Command page.

  • If the current target type is Host, clicking Add launches the Target Selection page with the target type list limited to host targets and any groups that contain host targets.

  • If the current target type is Database Instance, clicking Add launches the Target Selection page with the target type list limited to database targets and any groups that contain database targets.

  • Execution history reflects the host commands that have been executed in the current Execute Host Command session, as well as any host commands executed in previous sessions that were executed with the 'Keep the execution history for this command' option chosen.

  • Changing the target type reinitializes the host credentials, command, OS script, and targets table.

  • When saving the OS script or execution results, the saved file is located on the browser machine.

  • At most, 10 rows of command execution results data will be displayed in the targets table. If more data is returned, click the Execution Status icon in the table or click Complete Execution Results.

  • When switching from multiple to single target mode, the first host in the targets table will be used.

32.5.5 Execute Host Command - Single Host

The Execute Host Command page enables you to type operating system commands against one host and immediately view the results. This gives you the opportunity to perform administrative operations on the host within the context of Enterprise Manager.

On this page, you can:

  • Refine the command, reexecute the command, and view the execution results, all without leaving the page

  • Switch to Multiple Target Mode where multiple host targets are acted upon

  • Change credentials

Notes

Note the following:

  • Reexecute the command by clicking Execute.

  • Cancel the execution of the command by clicking Abort.

  • Context will be preserved if you switch to Multiple Target Mode, including the host command, host, and credentials.

32.5.6 Load OS Script

The Load OS Script page is used to load commands from a script into the OS Script field on the Execute Host Command page.

On this page, you can:

  • Click Browse to launch the browser's file selector window to locate and choose a script file.

  • Click the Host field's search icon to choose which host to search, then click the Host File field's search icon to locate and choose a script file on that host.

32.5.7 Load From Job Library

The Load From Job Library page provides the mechanism by which to search the Job Library directly for an existing job. This encourages the reuse of existing jobs.

On this page, you can click the icon in the 'Load' column of any row to return to the Execute Host Command page loading the complete context of the library job in that row. The complete context includes the host command, OS script, targets, and credentials.

Note: Jobs displayed in the table on this page will be host command jobs from the Job Library that are owned by the current Enterprise Manager user.

32.5.8 Execution History

The Execution History page lists the host commands executed during the current Enterprise Manager session, as well as any host commands executed in previous sessions that were executed with the 'Keep the execution history for this command' option chosen.

On this page, you can:

  • Click the icon in the 'Load' column of any row to return to the Execute Host Command page loading the complete execution context of the host command in that row. The complete execution context includes the host command, OS script, targets, credentials, and results.

  • Click the icon in the 'Load Command And OS Script Only' column of any row to return to the Execute Host Command page loading only the host command and the OS script in that row. Any targets, credentials, and most recent results will remain.

  • Click the icon in the 'Remove' column of any row to remove the host command in that row, along with all its execution context, from the Execution History. This will delete the job that was used to execute the host command.

32.5.9 Execution Results

The Execution Results page provides the full listing of the results of the executed host command, for a specific host. This listing chronicles all the information from the run.

On this page, you can:

  • Cut the text from the listing and paste it into another script.

  • Study the results uninterrupted and separate from all the other executions.

Note: The extent of the editing features is dependent upon the browser displaying the results.

32.6 Miscellaneous Tasks

This section miscellaneous tasks you can perform:

32.6.1 Enabling Collection of WBEM Fetchlet Based Metrics

To enable the Web-Based Enterprise Management (WBEM) Fetchlet based collections for the host target, configure the WBEM Host Username and WBEM Host Password properties.

Note: Host targets running with Linux and Windows operating systems do not, by default, have WBEM Fetchlet based metric collections. This is due to the fact that these operating systems, by default, do not run a DMTF (Distributed Management Task Force) WBEM-compliant Common Information Model (CIM) Object Manager. If the systems have been configured to run a WBEM-compliant CIM Object Manager, then WBEM Fetchlet based metric collections will be possible

To configure the collections on systems with WBEM compliant CIM Object Managers, use the following steps:

  1. Navigate to the home page of the specific host.

  2. From the Host menu, select Target Setup, then Monitoring Configuration.

  3. Set the Username and Password values.

32.6.2 Enabling Hardware Monitoring for Dell PowerEdge Linux Hosts

Hardware-specific monitoring is available for Dell PowerEdge Linux hosts with Enterprise Manager. To enable the hardware monitoring of your Dell PowerEdge Linux hosts, perform the following steps:

  1. Download the latest Dell OpenManage Server Administrator (OMSA) software certified for your Linux OS by accessing the Dell FTP site at http://ftp.dell.com/sysman/.

    Note: This link was accurate at time of writing. If you find this link to be out of date, contact Dell support.

    To identify the latest OMSA software, perform the following steps:

  2. Install the software using the instructions provided by Dell.

  3. Verify that the installation was successful by performing the following steps:

    • Verify that snmp daemon is up and running.

      % ps -ef | grep snmpd

    • Verify that the following commands execute without errors:

      % /usr/bin/omreport about

      % /usr/bin/omreport system version

  4. Verify the Dell OMSA software is functioning correctly by verifying that the Dell OpenManage Server Administrator website is up and running.

    • Using your web browser, access the URL https://target_hostname:1311

    • Log in using an operating system account. Check that you are able to successfully log in and navigate in the website.

  5. If the SNMP Community String for the SNMP daemon running on the Linux host is not public, set the SNMP Community String property in Enterprise Manager using the following steps:

    1. Login into Enterprise Manager Cloud Control

    2. Navigate to the home page of the specific host

    3. From the Host menu, select Target Setup, then Monitoring Configuration.

    4. Set the SNMP Community String property to the correct value on this page

  6. Restart the Management Agent on the host.

    % login into host as the owner account of emagent software

    % emctl stop agent

    % emctl start agent

  7. Note: The following step is not required if the Dell OMSA software was functional prior to the previous startup of the Management Agent.

    Verify that hardware monitoring is working correctly using the following steps:

    1. Log in to Enterprise Manager Cloud Control

    2. Navigate to the home page of the specific host

    3. From the Host menu, select Monitoring, then All Metrics.

    4. Verify that the following metrics are present on this page: Fans, Memory Devices, PCI Devices, Power Supplies, Processors, Remote Access Card, System BIOS, and Temperature

    5. You can navigate to the metric data page by clicking on one of the metrics listed in the previous step and view the data that Enterprise Manager is able to fetch.

32.6.3 Adding and Editing Host Configuration

The Add Host Configuration page provides you the opportunity to add a host to the /etc/hosts file. When you add a host to the /etc/hosts file, Enterprise Manager can then translate host names into IP addresses. In most cases, host names are much easier to remember than IP addresses.

On the Add Host Configuration page, you can:

  • Associate a host's IP address with a host name.

  • Add, delete, or change the aliases associated with a host

Note: Changes take effect after you click OK.

When editing a host configuration, you can:

  • Change the name of the host

  • Add, delete, or change the aliases associated with the host

Note: Changes are in effect immediately after you click OK.