Users Guide

User Created Jobs
The following are the user created jobs:
• CreateTargetedConfigJob — This method is used while configuring RAID, NIC, BIOS, iDRAC, and System. Use
this method to commit the configuration changes and create a job to apply the configuration changes.
• CreateRebootJob — This method is used to create reboot jobs.
• InstallFromURI — This method is used to update the firmware for BIOS, RAID, NIC, iDRAC, PSU, Lifecycle
Controller, OS driver packs, and Diagnostics. On success, this method returns a job ID. This job ID runs the
software update on that entity.
NOTE: If the InstallFromURI() method is used to update the BIOS, RAID, NIC, iDRAC, and PSU firmware, use the
SetupJobQueue() method to schedule the job ID.
NOTE: If the InstallFromURI() method is used to update the Lifecycle Controller, driver pack, and Diagnostics, do
not schedule a job.
Job Scheduling
The jobs can be scheduled for job IDs that are returned using one of the job creation methods.
SetupJobQueue — This method is used only with those job IDs that are returned by one of the job creation methods and
are not already scheduled.
Job Deletion
Using the JID_CLEARALL() method, all the current jobs in a system can be deleted. Alternatively, delete a specific job
using its job ID.
Scheduling Separate Jobs for Multiple Actions
To schedule separate jobs for multiple actions (in the following example, BIOS and NIC/CNA update and NIC
configuration):
1. Invoke the InstallFromURI() method for the BIOS and NIC firmware update packages.
The method downloads the BIOS and NIC updates, and creates a job ID for each device update job.
2. Set the NIC attributes for a NIC (for example, Integrated NIC 1) and create a targeted job for this set. The method
returns a job ID.
3. Take these job IDs and use the SetupJobQueue() method to schedule these jobs so that they are executed in the
order specified at the specified start time.
NOTE: For iDRAC to automatically reboot the system at the scheduled time, create a reboot job (specifying the type
of reboot — graceful or power cycle) and include the reboot job ID in the list of jobs specified in the
SetupJobQueue() method invocation. If a reboot job is not included in the Job Queue setup, the jobs are ready to
run at the scheduled start time but rely on an external action to restart the system and start the job execution.
Running Multiple Target Jobs
To run multiple target jobs (for example, setting NIC attributes on multiple NICs) at one time:
NOTE: You can create target jobs during POST or System Setup. The jobs do not run until the system completes
POST or exits System Setup.
38