White Papers

Workflow
6 Updating Firmware using OpenManage Enterprise APIs
2 Workflow
2.1 Update using a Catalog
1. Create a catalog from an online source or point to a remote repository that hosts a catalog and the
associated DUP files referenced in the catalog. The online catalog source is
https://downloads.dell.com. The supported offline catalog sources are:
‐ HTTP
‐ HTTPS
‐ CIFS
‐ NFS
2. Create a firmware baseline for the targets (device/devices/group of devices) using the catalog
specified in step 1a.
3. Check the firmware baseline compliance report to see which components need to be updated /
downgraded.
4. Update specific components and track the spawned job to completion.
2.2 Update using a single DUP
1. Upload the DUP file to OME and retrieve the file token returned on a successful upload.
2. Determine for the device or group if there are specific components that this DUP applies to for an
update/downgrade.
3. Apply the DUP in the case of an update/downgrade to the specified components and parse the ID of
the returned job that handles the application of the DUP file.
4. Track the job to completion and indicate errors / success.
2.3 Create firmware catalog
Catalogs are bundles of firmware based on device types.
Create the online catalog - All the available catalogs (update packages) are validated and posted to
support.dell.com. When you create an online catalog, the catalog file is downloaded but the corresponding
DUPs are not downloaded. When the devices are being updated, the DUP files are downloaded locally and
deleted on successful completion of associated update tasks.
Customer-created catalogs (using the Dell Repository Manager tool for instance) can be stored on
CIFS/NFS/HTTP/HTTPS shares.