Practices Guide

Lifecycle Controller Integration―Best Practices Specification
154
described in section 5.2.1
- The total time taken for reboot depends on the RebootJobType specified.
o For a machine powered down, it shouldn’t take more than 30 seconds to power up.
o For a running machine, timeout depends on the RebootJobType:
 1 = PowerCycle – 30 seconds
 2 = Graceful Reboot without forced shutdown – 5 minutes
 3 = Graceful reboot with forced shutdown – 5 minutes
33.4.3 POST
33.4.3.1 Memory check
- Get the value of the BIOSEnumeration attribute MemTest, obtained during inventory as described
in section 5.3.3.
- If MemTest = Enabled, on power on, the BIOS memory test is executed.
- If memory test is executed, the total timeout for POST should include 10 seconds per GB of RAM
to check the total RAM installed on the target system, as obtained from enumeration described in
section 33.3.
33.4.3.2
Controller initialization
- Get the total number of NIC and RAID controllers on the target system, obtained from
enumerations described in sections 33.3.5 and 33.3.6.
- The total timeout for POST should include 10 seconds to initialize each NIC controller installed on
the target system.
- The total timeout for POST should include 1 minute to initialize each RAID controller installed on
the target system.
33.4.4 SSM
33.4.4.1 UEFI initialization
- Before executing SSM, the UEFI environment needs to load into memory. This includes various BIOS,
NIC, RAID and LC drivers that are loaded and started. This also includes initialization time for
various NIC device drivers which populate the HII database with their attribute configuration for
consumption by LC.
- The total timeout for SSM should include 2 minutes to load all BIOS and LC components.
- The total timeout for SSM should include 30 seconds to load and initialize each NIC driver installed
on the target system.
33.4.4.2
Job execution
- Once SSM starts to execute a job, JobStatus will transition from Scheduled to Running to
Completed, Completed with Errors, or Failed.
- The total timeout for SSM should include 5-10 minutes per job executed depending on the type of
job.
- Error to user if JobStatus != Completed or timeout occurs.
- If JobStatus = Completed with Errors, attributes that failed to set can be obtained from the LCL
as described in section 12.13 of the WSIG for Windows.
- Completion of all jobs from the JobStatus perspective will suggest that all job execution tasks are
done. However, various LC tasks such as inventory and refresh will still be in progress. The
timeouts for these tasks can be accounted for in the next section.
- JobStatus can be obtained as described in section 10.2.3 of the WSIG for Windows.