Practices Guide

Lifecycle Controller IntegrationBest Practices Specification
43
4.13 USC Firmware DUP Update from CIFS or TFTP Share
This workflow performs an update of the USC (LC) firmware from a DUP by first downloading
the DUP to the system, then applying the update. By design, the update of the USC firmware
will be invoked immediately following download completion and cannot be scheduled for a
later time. Approximate time for completion is 30-60 minutes depending on the system
configuration.
Applies to: LC1.3.0+
Prerequisites for script:
Desired DUP must be present on network share
Set script variables by editing script
Script: USC_LC_update.win
A) The Lifecycle Controller remote service must be in a “ready” state before executing any
other WSMAN commands. The GetRSStatus() method or the GetRemoteServicesAPIStatus()
method may be used depending on the version of the LC Management registered profile.
B) GetSoftwareIdentities(): ENUMERATE the DCIM_SoftwareIdentity class to list the
firmwares of the system. See section 2.2 for a definition of
ENUMERATE.
C) Search the results from B) for "ElementName = Dell Lifecycle Controller" and note the
accompanying instanceID to be used in D). There may be additional characters and
numbers after the substring “Controller”.
D) InstallFromURI(): Invokes firmware update operation [ReturnValue=4096]
NOTE: The USC update is applied immediately, and cannot be scheduled for a later time.
E) Poll jobstatus for Completed: GET the InstanceID of from D). See section 2.3 for a
definition of
GET.
F) RequestiDRACStateChange(): Must reset idrac for changes to take effect [ReturnValue=0]
G) [LC1.5.0/LC1.5.1]Sleep for 10 minutes to allow reboot, POST, and CSIOR to complete
See Appendix 33.4.3 and 33.4.7 for more information about POST and CSIOR
H) The Lifecycle Controller remote service must be in a “ready” state before executing any
other WSMAN commands The GetRSStatus() method or the GetRemoteServicesAPIStatus()
method may be used depending on the version of the LC Management registered profile.
4.14
Automatic Firmware Update (12
th
Generation and Later
Version of Servers Only)
This workflow creates a recurring schedule to perform multiple firmware updates by
specifying a network repository that contains a catalog of available updates and the
scheduling parameters. At the specified schedule, all applicable updates contained in the
repository will be applied to the system.