White Papers

25 Lifecycle Controller Integration Best Practices Guide
3 Anomalous Algorithms and Descriptions
3.1 Setting CNA Bandwidth
The recommended algorithm is to schedule jobs such that MinBandwidths are first reduced, and then increased.
Essentially, delta values need to be sorted, and jobs scheduled in that order.
Consider the following example:
Current: 25, 25, 25, 25
Target: 30, 30, 20, 20
Since 20, 20 are both reducing values from 25, they should be scheduled first. This makes space for increasing the other
values. Next, values being increased can be scheduled – 30, 30.
A more complex example:
FQDD: 1, 2, 3, 4
Current: 5, 5, 50, 40
Target: 40, 50, 5, 5
Deltas: -35, -45, 45, 35
Order of job FQDDs: 3, 4, 1, 2
MinBandwidth limitations are documented in the Simple NIC Profile in section 6.7.
http://attachments.wetpaintserv.us/chcAMan6fnC1y8Z8qYSnag350700
3.2 iDRAC Cloning
Blade cloning consists of a pull, enumerating attributes, and a push, applying attributes. The pull command is a basic
enumeration command using the DCIM_iDRACCardAttribute class.
Applies to: LC2+
Script: iDRACClonePull.win
a. The remote service must be in a “ready” state before running 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. ENUMERATE the DCIM_iDRACCardAttribute class (same as DCIM_iDRACCardEnumeration class)
and store the results to be pushed. See section 2.2 for a definition of ENUMERATE . The blade cloning
push requires an extended WSMAN timeout of 120 seconds, versus the default of 60 seconds. This is
needed because of the numerous amounts of attributes that need to be applied.