Using jobs for device control. Dell EMC OpenManage Enterprise

Add to My manuals
215 Pages

advertisement

Using jobs for device control. Dell EMC OpenManage Enterprise | Manualzz

15

Using jobs for device control

A job is a set of instructions for performing a task on one or more devices. The jobs include discovery, firmware update, inventory refresh for devices, warranty, and so on. You can view the status and details of jobs that are initiated in the devices and its components, on the Jobs screen. OpenManage Enterprise has many internal maintenance jobs which are triggered on a set schedule automatically by the appliance. For more information on the 'default' jobs and their schedule, see

Default jobs and job schedules

.

Topics:

Create and manage jobs

View job lists

View job details

Create a job to blink device LEDs

Create a job for managing power devices

Create a remote command job for managing devices

Create a job to change the virtual console plugin type

Select target devices and device groups

Manage jobs

Create and manage jobs

To create and manage jobs such as blink, power control, managing firmware baselines, managing configuration compliance baseline, and so on, where the device selection task is involved.

Prerequisites

Ensure you have the necessary user privileges as described in Role and scope-based access .

● Each job type is limited to devices that you must have:

○ Permission to access.

○ Ability to complete the required action.

Steps

1. Select Monitor > Jobs .

You can perform the following tasks on the Jobs screen:

View job lists

to check if jobs are currently running, failed, or successfully completed.

Create jobs to blink device LEDs, control the device power, and run remote command on devices as described in Create a remote command job for managing devices

, and

Create a job to blink device LEDs . You can perform similar actions on a

server on the device details screen, as described in

View and configure individual devices

.

Manage jobs

such as run, stop, enable, disable or delete jobs.

2. To view more information about a job, select the check box corresponding to a job, and then click View Details to

View job details

View job lists

View status of jobs run on OpenManage Enterprise for device monitoring and management.

From OpenManage Enterprise, click Monitor > Jobs to view the list of existing jobs. Information about jobs are provided in the following columns:

● Job Status : Provides the execution status of a job.

See

Jobs status and Jobs type description .

Using jobs for device control 169

● State : Provides the state of a job. The available options are Enabled or Disabled.

● Job Name : Name of a job.

● Job Type : Provides the type of a job.

See

Jobs status and Jobs type description .

● Description : Detail description of a job.

● Last Run : Last run period of a job.

Jobs can also be filtered by entering or selecting the values in the Advanced Filters section. The following additional information can be provided to filter the alerts:

● Last run start date: Jobs last run start date.

● Last run end date : Jobs last run end date.

● Source : The available options are All, User Generated (Default), and System.

To view more information about a job, select a job and click View Details in the right pane. See

View job details

.

OpenManage Enterprise provides a built-in report to view the list of scheduled jobs. Click OpenManage Enterprise > Monitor

> Reports > Scheduled Jobs Report . Click Run . See

Run reports

.

NOTE:

● On the Discovery and Inventory Schedules pages, the status of a scheduled job is identified by Queued in the

STATUS column. However, the same status is indicated as Scheduled on the Jobs page.

● Users are currently allowed to select multiple jobs either individually, or by selecting all on the current page or across all pages, and click Run Now . If any of the selected jobs contain a device reboot (example: device action or firmware update job), target devices could be adversely impacted. Exercise extreme caution when using this feature.

Jobs status and Jobs type description

Statuses of a job indicate its completion state. Jobs can be run for device discovery, health status upgrade, updating

OpenManage Enterprise version, etc.

Table 26. Job status and description

Job Status

Scheduled

Description

Job is scheduled for run at a later date or time.

Jobs that are waiting to be executed.

Queued

Starting

Running

Completed

Failed

New

Completed with errors

Aborted

Paused

Stopped

Canceled

Not run

Job is triggered using Run Now

Job has run.

Job run was unsuccessful.

Job is created but not run.

Job run was partially successful and was completed with errors.

Job run was paused by the user.

Job run was stopped by the user.

Job run was interrupted by the user.

Job is either Queued or Scheduled and is yet to run.

A job can belong to any one of the following types:

Table 27. Job Types and description

Job Type

Health

Description

Checks the health status of the devices. See

Device health statuses

.

170 Using jobs for device control

Table 27. Job Types and description (continued)

Job Type

Inventory

Description

Creates inventory report of the devices. See Managing device inventory .

Device Config

Report_Task

Warranty

Onboarding_Task

Discovery

Console Update Execution Task

Creates device configuration compliance baseline. See Configuration compliance .

Creates reports about devices by using built-in or customized data fields. See

Monitoring reports

.

Generate data about devices' warranty status. See

Managing device warranty .

Onboards the discovered devices. See

Onboarding devices

.

Discovers devices. See

Discovering devices

.

Console Upgrade Job is being tracked using this task. This task helps to identify if the upgrade has completed or failed

Creates a file backup of the appliance and deposits it in a secure location.

Backup

Chassis Profiles

Debug Logs

Device Action

Diagnostic_Task

Collects Debug logs of the application monitoring tasks, events, and the task execution history.

Creates actions on devices such as Turn LED On, Turn LED Off, IPMI CLI, RACADM

CLI, and so on.

Download/Run of Diagnostic/TSR or Services (SupportAssist) tasks are related to

Diagnostic task. See Run and download Diagnostic reports .

Import VLAN Definition Import of VLAN definitions from excel or from MSM.

OpenID Connect Provider

PluginDownload_Task

Post_Upgrade_Task

Report_Task

Restore

Settings Update

Software Rollback

Update

Upgrade_Bundle_Download_Task

Configuration on OpenID connection. See OpenManage Enterprise login using OpenID

Connect providers

.

Plugin Download task is being tracked and this task helps to identify wether the

downloading of Plugins RPM are completed and ready for installation. See Check and update the version of the OpenManage Enterprise and the available plugins .

PostUpgrade task is been tracked to set the appliance settings peformed in N-1 or N-2

Version also runs the discovery task which were created in Previous Version to make sure all devices are being listed.

Report Task is being tracked when user runs the report (for Canned as well for

Custom).

Reinstates appliance data after upgrades, major configuration changes, or when migrating from VM to VM.

Settings Update task is being tracked when user applies a new setting under

Application Settings tab.

Rollback is task being tracked when user performs Rollback operation on a target device.

Update task is being tracked when user performs the Firmware or Driver Update on the target devices.

Upgrade bundle download task is being tracked and this task helps to identify wether the downloading of OMEnterprise RPM are completed and ready for installation

Using jobs for device control 171

Default jobs and job schedules

OpenManage Enterprise has many internal maintenance jobs which are triggered automatically by the appliance on a set schedule.

Table 28. Default jobs and job schedules

Job Name Cron Expression Cron Expression Description

Configuration Inventory 0 0 0 1/1 * ? * At 00:00:00am, every day starting on the

1st, every month

Default Console Update

Task

Default Inventory Task

Device Config Purge

Task for cleanup

File Purge Task for

Share Utilization

File Purge Task for

Single DUP Files

Global Health Task

Internal Sync Task

Metrics Purge Task

Metrics Task

0 0 12 ? * MON *

0 0 5 * * ? *

0 0/1 * * * ? *

0 0 0 1/1 * ? *

0 0 0/4 1/1 * ? *

0 0 0/1 1/1 * ? *

0 0/5 * 1/1 * ? *

0 0 * ? * *

0 0/15 * 1/1 * ? *

At 12:00:00pm, on every Monday, every month

At 05:00:00am every day

At second :00, every minute starting at minute :00, of every hour

At 00:00:00am, every day starting on the

1st, every month

At second :00, at minute :00, every 4 hours starting at 00am, every day starting on the 1st, every month

Example

● Tue May 18 00:00:00 UTC

2021

● Wed May 19 00:00:00 UTC

2021

● Mon May 24 12:00:00 UTC

2021

● Mon May 31 12:00:00 UTC

2021

● Tue May 18 05:00:00 UTC

2021

● Wed May 19 05:00:00 UTC

2021

● Mon May 17 18:39:00 UTC

2021

● Mon May 17 18:40:00 UTC

2021

● Tue May 18 00:00:00 UTC

2021

● Wed May 19 00:00:00 UTC

2021

● Mon May 17 20:00:00 UTC

2021

● Tue May 18 00:00:00 UTC

2021

● Tue May 18 04:00:00 UTC

2021

● Tue May 18 04:00:00 UTC

2021

At second :00, at minute :00, every hour starting at 00am, every day starting on the

1st, every month

● Mon May 17 19:00:00 UTC

2021

● Mon May 17 20:00:00 UTC

2021

At second :00, every 5 minutes starting at minute :00, every hour, every day starting on the 1st, every month

● Mon May 17 18:45:00 UTC

2021

● Mon May 17 18:50:00 UTC

2021

At second :00 of minute :00 of every hour ● Mon May 17 19:00:00 UTC

2021

● Mon May 17 20:00:00 UTC

2021

● Mon May 17 21:00:00 UTC

2021

At second :00, every 15 minutes starting at minute :00, every hour, every day starting on the 1st, every month

● Mon May 17 18:45:00 UTC

2021

● Mon May 17 19:00:00 UTC

2021

172 Using jobs for device control

Table 28. Default jobs and job schedules (continued)

Job Name

Mobile Subscription

Task

Node Initiated

Discovery Task

Password Rotation

Task

Periodic Metrics

Registration

Cron Expression Cron Expression Description

0 0/2 * 1/1 * ? *

At second :00, every 2 minutes starting at minute :00, every hour, every day starting on the 1st, every month

0 0/10 * 1/1 * ? *

0 0 0/6 1/1 * ? *

0 0 3 * * ?

At second :00, at minute :00, every 6 hours starting at 00am, every day starting on the 1st, every month

At 03:00:00am every day

Example

● Mon May 17 18:54:00 UTC

2021

● Mon May 17 18:56:00 UTC

2021

At second :00, every 10 minutes starting at minute :00, every hour, every day starting on the 1st, every month

● Mon May 17 19:00:00 UTC

2021

● Mon May 17 19:10:00 UTC

2021

● Tue May 18 00:00:00 UTC

2021

● Tue May 18 06:00:00 UTC

2021

● Tue May 18 12:00:00 UTC

2021

● Tue May 18 03:00:00 UTC

2021

● Wed May 19 03:00:00 UTC

2021

Purge On Demand

Health Task for Table:

Task

0 0 0/5 1/1 * ? *

At second :00, at minute :00, every 5 hours starting at 00am, every day starting on the 1st, every month

Purge Task

Table :Event_Archive

Purge Task

Table :Group_Audit

Purge Task Table :Task 0 0 0 1/1 * ? *

Purge Task

Table :announced_targ et

Purge Task for Table:

Core Application Log

0 0 18/12 ? * * *

0 0 0 1/1 * ? *

0 0 0 1/1 * ? *

0 0 0/5 1/1 * ? *

At second :00, at minute :00, every 12 hours starting at 18pm, of every day

At 00:00:00am, every day starting on the

1st, every month

At 00:00:00am, every day starting on the

1st, every month

At 00:00:00am, every day starting on the

1st, every month

At second :00, at minute :00, every 5 hours starting at 00am, every day starting on the 1st, every month

● Tue May 18 00:00:00 UTC

2021

● Tue May 18 05:00:00 UTC

2021

● Tue May 18 10:00:00 UTC

2021

● Tue May 18 18:00:00 UTC

2021

● Wed May 19 18:00:00 UTC

2021

● Thu May 20 18:00:00 UTC

2021

● Tue May 18 00:00:00 UTC

2021

● Wed May 19 00:00:00 UTC

2021

● Thu May 20 00:00:00 UTC

2021

● Tue May 18 00:00:00 UTC

2021

● Wed May 19 00:00:00 UTC

2021

● Thu May 20 00:00:00 UTC

2021

● Tue May 18 00:00:00 UTC

2021

● Wed May 19 00:00:00 UTC

2021

● Thu May 20 00:00:00 UTC

2021

● Tue May 18 00:00:00 UTC

2021

● Tue May 18 05:00:00 UTC

2021

Using jobs for device control 173

Table 28. Default jobs and job schedules (continued)

Job Name

Purge Task for Table:

Event

Purge Task for Table:

Infrastructure Device

Cron Expression Cron Expression Description

0 0/30 * 1/1 * ? *

At second :00, every 30 minutes starting at minute :00, every hour, every day starting on the 1st, every month

0 0/30 * 1/1 * ? * At second :00, every 30 minutes starting at minute :00, every hour, every day starting on the 1st, every month

Subscription poller task 0 0/30 * 1/1 * ? *

At second :00, every 30 minutes starting at minute :00, every hour, every day starting on the 1st, every month

Example

● Mon May 17 19:30:00 UTC

2021

● Mon May 17 20:00:00 UTC

2021

● Mon May 17 20:30:00 UTC

2021

● Mon May 17 19:30:00 UTC

2021

● Mon May 17 20:00:00 UTC

2021

● Mon May 17 20:30:00 UTC

2021

● Mon May 17 19:30:00 UTC

2021

● Mon May 17 20:00:00 UTC

2021

● Mon May 17 20:30:00 UTC

2021

View job details

View job status and restart if necessary. Export job data to an Excel file.

Steps

1. In the Jobs screen, select the checkbox corresponding to a job.

2. In the right pane, click View Details .

In the Job Details screen:

● The Execution History contains an entry for each time the job ran.

● The Execution Details section lists the devices on which the job was run, and displays the time taken to run the job.

NOTE: If a job's start, end or elapsed time is incorrect, update your local time zone and settings in the Application

Settings > Network > Time Configuration screen.

● Click Restart Job if the status of a job is: Stopped , Failed , or New . A message is displayed when the job has started running.

● To export the job details to an Excel file, select the relevant job checkboxes, and click Export to

Export data

.

Create a job to blink device LEDs

The following steps describe how you can blink the LEDs of the specified devices using the Blink Devices Wizard.

Prerequisites

● To perform any tasks on OpenManage Enterprise, you must have necessary role-based user privileges and scope-based operational access to the devices. See

Role and scope-based access

● After submitting this job for execution the console will first try and verify the service tag of the intended target to ensure the operation is performed on the correct system. If the verification fails the job will complete with errors, and the task execution history detail will show the following:

Running

Verifying if the device Service Tag is valid.

The device Service Tag could not be verified.

Task Failed. Completed With Errors.

Please check the system to ensure the IP address has not changed since the last

174 Using jobs for device control

discovery was completed. Remediate by discovering the system with the updated IP address, and retrying the operation.

Steps

1. The Blink Devices wizard can be activate in the following ways: a. From the Jobs page ( OpenManage Enterprise > Monitor > Jobs ) click Create , and then select Blink Devices .

b. From the All Devices page ( OpenManage Enterprise > Devices ), select the devices and click the More Actions drop down and then either click Turn LED On or Turn LED Off .

2. In the Blink Devices Wizard dialog box: a. In the Options section: i.

In the Job Name box, enter a job name.

ii. From the Blink LED Duration drop-down menu, select options to blink the LED for a set duration, turn on, or to turn off.

iii. Click Next .

b. In the Target section, select the target devices or target groups and click Next . See

Select target devices and device groups

.

c. In the Schedule drop down select Run Now , or Run Later , or Run on Schedule . See

Schedule job field definitions

.

3. Click Finish .

A Blink LED job is created and listed in the Jobs page ( OpenManage Enterprise > Monitor > Jobs ) JOB STATUS column.

Create a job for managing power devices

Create a job to blink device(s) LED so you can identify the device.

Prerequisites

Power control actions can be performed only on devices that are discovered and managed using iDRAC (out-of-band).

Steps

1. Click Create , and then select Power Control Devices .

2. In the Power Control Devices Wizard dialog box: a. In the Options section: i.

Enter the job name in Job Name .

ii. From the Power Options drop-down menu, select any one of the tasks: Power on , Power off , or Power cycle .

iii. Click Next .

b. In the Target section, select the target devices and click Next . See

Select target devices and device groups

.

c. In the Schedule section, run the job immediately or schedule for a later point of time. See

Schedule job field definitions

.

3. Click Finish .

The job is created and listed in the Jobs list and identified by an appropriate status in the JOB STATUS column.

4. If the job is scheduled for a later point of time, but you want to run the job immediately:

● On the Jobs page, select the check box corresponding to the Scheduled job.

● Click Run Now . The job is run and the status is updated.

● To view the job data, click View Details in the right pane. See

View job details

.

Create a remote command job for managing devices

Create a job to remotely run a command and control devices.

About this task

Use the Command Line Job wizard, to create command jobs to manage target devices remotely.

Using jobs for device control 175

NOTE: After submitting this job for execution the console will first try and verify the service tag of the intended target to ensure the operation is performed on the correct system. If the verification fails the job will complete with errors, and the task execution history detail will show the following:

Running

Verifying if the device Service Tag is valid.

The device Service Tag could not be verified.

Task Failed. Completed With Errors.

Please check the system to ensure the IP address has not changed since the last discovery was completed. Remediate by discovering the system with the updated IP address, and retrying the operation.

Steps

1. Click Create > Remote Command on Devices .

2. In the Command Line Job Wizard dialog box, in the Options section: a. Enter the job name in Job Name .

b. From the Interface drop-down menu, select one of the interfaces depending on the target devices you want to manage:

● IPMI CLI — for iDRACs and non-Dell servers.

● RACADM CLI — for iDRACs discovered using the WSMAN protocol.

● SSH CLI — for Linux servers discovered using the SSH protocol.

c. In the Arguments box, enter the command. Up to 100 commands can be typed with each command required to be on a new line.

NOTE: The commands in the Arguments box are run one at a time.

d. Click Next .

A green tick mark next to Options indicates that the necessary data is provided.

3. In the Target section, select the target devices and click Next . See

Select target devices and device groups

.

4. In the Schedule section, run the job immediately or schedule for a later time. See

Schedule job field definitions

.

5. Click Finish .

The job is created and listed in the jobs list and identified by an appropriate status in the Job Status column.

6. If the job is scheduled for a later point, but you want to run the job immediately:

● On the Jobs page, select the check box corresponding to the Scheduled job.

● Click Run Now . The job is run and the status is updated.

● To view the job data, click View Details in the right pane. See

View job details

.

Create a job to change the virtual console plugin type

Create a job to change the plugin type of a virtual console of devices to HTML5.

About this task

You can change the virtual console plugin type to HTML5 on multiple devices. Updating to HTML5 can lead to a better browser experience.

Steps

1. Click OpenManage Enterprise > Monitor > Jobs

2. Click Create , and then select Change Virtual Console Plugin on Devices .

3. In the Change Virtual Console Plugin Wizard dialog box, in the Options section: a. Enter the job name in Job Name . By default, the plugin type is displayed as HTML5.

b. Click Next .

4. In the Job Target section, select the target devices and click Next . See

Select target devices and device groups

.

a. Click Next .

5. In the Schedule section, run the job immediately or schedule for a later point of time. See

Schedule job field definitions .

6. Click Finish .

176 Using jobs for device control

The job is created and listed in the Jobs list and identified by an appropriate status in the JOB STATUS column.

7. If the job is scheduled for a later point of time, but you want to run the job immediately:

● On the Jobs page, select the check box corresponding to the Scheduled job.

● Click Run Now . The job is run and the status is updated.

● To view the job data, click View Details in the right pane. See

View job details

.

Select target devices and device groups

Select target devices or device groups perform actions such as monitoring and upgrade.

About this task

By default, Select Devices is selected to indicate that the job can be run on the devices. You can run a job on device groups also by selecting Select Groups .

NOTE: The device groups and devices displayed are governed by the scope-based operational access that the user has to the devices. For more information, see

Role and scope-based access .

Steps

1. Click Select Devices .

In the Job Target dialog box, the left pane lists the devices monitored by OpenManage Enterprise. In the working pane, list of devices associated with each group, and device details are displayed. For field descriptions, see

All Devices screen device list . For information about device groups, see

Organize devices into groups

.

2. Select the check box corresponding to a device and click OK .

The selected devices are displayed in the All Selected Devices section of the selected group.

Manage jobs

After jobs have been created and displayed on the Jobs page, you can manage them as follows.

● Run jobs : Select the check box corresponding to a job, and then click Run Now to execute the task on the targeted devices. You can run a job when it is in enabled status.

● Enable jobs : Select the check box corresponding to a job, and then click Enable .

● Disable jobs : Select the check box corresponding to a job, and then click Disable .

NOTE: Only the 'Scheduled' jobs can be disabled from running. Jobs which are active and in their 'Running' state cannot be disabled midway.

● Stop jobs : Select the check box corresponding to a job, and then click Stop . You can stop a job when it is in running status.

● Delete : Select the check box corresponding to a job, and then click Delete .

Using jobs for device control 177

advertisement

Related manuals

Download PDF

advertisement

Table of contents