Abstract: Methods and systems for managing the operation of data processing systems are disclosed. A data processing system may include a computing device that may enter various operating states by performing various types of startups. The startups may include use of code bases for which the computing device may not inherently be able to validate. To reduce risk of using the code bases, the computing device may perform processes to validate the code bases prior to using the code bases. Additionally, the computing devices may limit the types of interfaces that may be established during the startups while allowing other types of interfaces to be established to provide startup flexibility.

Abstract: An Information Handling System (IHS) includes multiple hardware devices, and a baseboard Management Controller (BMC) in communication with the plurality of hardware devices. The BMC includes executable instructions for beginning execution of a first BMC firmware stack, and during execution of the first BMC firmware stack, halt execution of the first BMC firmware stack, and begin execution of a second BMC firmware stack. At least a portion of the executable instructions used to generate the first BMC firmware stack are different than the executable instructions used to generate the second BMC firmware stack.

Abstract: An information handling system includes a memory and a baseboard management controller. The memory includes a recovery partition including a recovery kernel, a first boot partition including first firmware, and a second boot partition including backup firmware. The baseboard management controller (BMC) attempts a first boot operation of the first firmware in the first boot partition. In response to a failure of the first boot operation, the BMC attempts a second boot operation of the backup firmware in the second boot partition. In response to a failure of the second boot operation, the BMC operates a recovery kernel. During the operation of the recovery kernel, the BMC provides a firmware request to an enclosure controller, receives blocks of correct firmware from a functioning baseboard management controller, stores the blocks of correct firmware in the first boot partition, attempts and completes a third boot operation of the correct firmware.

Abstract: Methods, systems, and devices for providing for trust during startup of an information handling system (IHS) are disclosed. When an IHS starts up, data may be read into memory and used by a processor of the IHS to begin execution of a startup management entity that places the IHS into a desired operating system. To reduce the likelihood of the data used for IHS startup causing the IHS to enter an undesired state (e.g., due to data corruption or intentional action), the data may be verified prior to be being read into memory. If the data is unverifiable, then corrective action may be taken.

Abstract: An Information Handling System (IHS) includes multiple hardware devices, and a baseboard Management Controller (BMC) in communication with multiple hardware devices of the IHS. The BMC includes executable instructions for monitoring a parameter of one or more of the hardware devices when a custom BMC firmware stack is executed on the BMC. The instructions that monitor the parameter are separate and distinct from the instructions of the custom BMC firmware stack. The instructions also control the BMC to perform one or more operations to remediate an excessive parameter when the parameter exceeds a specified threshold.

Abstract: An information handling system includes a first memory and a baseboard management controller. The first memory stores a first firmware partition and a second firmware partition. The baseboard management controller includes a second memory. The baseboard management controller begins execution of a DM-Verity daemon, and performs periodic patrol reads of the first firmware partition. The baseboard management controller detects one or more block failures in the first firmware partition, and stores information associated with the one or more block failures in a message box of the second memory. In response to the entire first firmware partition being scanned, the baseboard management controller switches a boot partition from the first firmware partition to the second firmware partition, and initiates a reboot of the information handling system.

Abstract: In one or more embodiments, one or more systems, one or more methods, and/or one or more processes may read configuration information that indicates utilization of a custom information handling system firmware IHSFW image by an information handling system (IHS); provide the custom IHSFW image and a signature of the custom IHSFW image to a processor of the IHS; decrypt the signature of the custom IHSFW image to obtain a hash value of the custom IHSFW image; determine a test hash value of the custom IHSFW image; determine if the hash value matches the test hash value; if the hash value matches the test hash value, boot a custom IHSFW from the custom IHSFW image; and if the hash value does not match the test hash value, boot another IHSFW from another IHSFW image stored by a non-volatile memory medium of the IHS.

Abstract: An information handling system includes a host processor that instantiates a hosted environment. A baseboard management controller executes core firmware code to provide a first plurality of functions of the baseboard management controller. The first functions include a container management system. The container management system provides a plurality of extension slots. Each extension slot provides one of a second plurality of functions of the baseboard management controller.

Abstract: Methods, systems, and devices for providing for trust during startup of an information handling system (IHS) are disclosed. When an IHS starts up, data may be read into memory and used by a processor of the IHS to begin execution of a startup management entity that places the IHS into a desired operating system. To reduce the likelihood of the data used for IHS startup causing the IHS to enter an undesired state (e.g., due to data corruption or intentional action), the data may be verified prior to be being read into memory. If the data is unverifiable, then corrective action may be taken.

Abstract: An information handling system includes a memory and a baseboard management controller. The memory includes a recovery partition including a recovery kernel, a first boot partition including first firmware, and a second boot partition including backup firmware. The baseboard management controller (BMC) attempts a first boot operation of the first firmware in the first boot partition. In response to a failure of the first boot operation, the BMC attempts a second boot operation of the backup firmware in the second boot partition. In response to a failure of the second boot operation, the BMC operates a recovery kernel. During the operation of the recovery kernel, the BMC provides a firmware request to an enclosure controller, receives blocks of correct firmware from a functioning baseboard management controller, stores the blocks of correct firmware in the first boot partition, attempts and completes a third boot operation of the correct firmware.

Abstract: In one or more embodiments, one or more systems, one or more methods, and/or one or more processes may read configuration information that indicates utilization of a custom information handling system firmware IHSFW image by an information handling system (IHS); provide the custom IHSFW image and a signature of the custom IHSFW image to a processor of the IHS; decrypt the signature of the custom IHSFW image to obtain a hash value of the custom IHSFW image; determine a test hash value of the custom IHSFW image; determine if the hash value matches the test hash value; if the hash value matches the test hash value, boot a custom IHSFW from the custom IHSFW image; and if the hash value does not match the test hash value, boot another IHSFW from another IHSFW image stored by a non-volatile memory medium of the IHS.

Abstract: An information handling system includes a first memory and a baseboard management controller. The first memory stores a first firmware partition and a second firmware partition. The baseboard management controller includes a second memory. The baseboard management controller begins execution of a DM-Verity daemon, and performs periodic patrol reads of the first firmware partition. The baseboard management controller detects one or more block failures in the first firmware partition, and stores information associated with the one or more block failures in a message box of the second memory. In response to the entire first firmware partition being scanned, the baseboard management controller switches a boot partition from the first firmware partition to the second firmware partition, and initiates a reboot of the information handling system.

Abstract: An information handling system may include at least one processor and a memory. The information handling system may be configured to: host a container; execute a containerized application within the container, wherein the containerized application executes with privileges associated with a container-internal user; determine an association between the container-internal user and a host user associated with an operating system external to the container, wherein the determining is based on a cache that maintains a mapping between container-internal users and host users; and grant privileges to the containerized application based on the host user.

Abstract: An Information Handling System (IHS) includes multiple hardware devices, and a baseboard Management Controller (BMC) in communication with multiple hardware devices of the IHS. The BMC includes executable instructions for monitoring a parameter of one or more of the hardware devices when a custom BMC firmware stack is executed on the BMC. The instructions that monitor the parameter are separate and distinct from the instructions of the custom BMC firmware stack. The instructions also control the BMC to perform one or more operations to remediate an excessive parameter when the parameter exceeds a specified threshold.

Abstract: An Information Handling System (IHS) includes multiple hardware devices, and a baseboard Management Controller (BMC) in communication with the plurality of hardware devices. The BMC includes executable instructions for beginning execution of a first BMC firmware stack, and during execution of the first BMC firmware stack, halt execution of the first BMC firmware stack, and begin execution of a second BMC firmware stack. At least a portion of the executable instructions used to generate the first BMC firmware stack are different than the executable instructions used to generate the second BMC firmware stack.

Abstract: An Information Handling System (IHS) includes multiple hardware devices, and a baseboard Management Controller (BMC) in communication with the plurality of hardware devices. The BMC includes instructions for executing a first BMC firmware stack that uses certain data for its operation. The data used by the first BMC firmware stack is stored in a first memory location. The instructions are further configured to halt execution of the first BMC firmware stack, and begin execution of a second BMC firmware stack by copying the data from the first memory location to a second memory location used by the second BMC firmware stack.

Abstract: An information handling system may include a management controller configured to provide out-of-band management of the information handling system. The management controller may be configured to: receive a user indication of a desired interface; and set a target readiness level based on the user indication. Upon a subsequent boot of the management controller, the target readiness level may be configured to cause the management controller to prioritize initialization of the desired interface such that the desired interface is made ready prior to a different, non-desired interface.

Abstract: An information handling system may include a host system and a management controller configured to provide out-of-band management of the information handling system. The management controller may be configured to: receive, via a management bus of the management controller, a user login request for access to a first user account associated with the management controller; determine a second user account corresponding to the first user account, wherein the second user account is associated with a security policy; and provide the user access to the management controller via the first user account, wherein a privilege level of the provided access is based on a set of privileges associated with the second account.

Abstract: A management system for an information handling system includes a memory device and a management controller. The memory device includes a primary firmware image and a backup firmware image. The management controller boots the management system. The boot of the management system includes a read of a first block at an offset within the primary firmware image. The management controller further determines that the read of the first block had a first read error, and reboots the management system in response to determining that the read of the first block had the first read error. The reboot of the management system includes a read of a second block at the offset within the backup firmware image.

Abstract: A method may include, at a management module configured to manage a plurality of information handling systems: receiving administrator preferences for a job to be scheduled at each of the plurality of information handling systems, based on the administrator preferences, assigning for each of the plurality of information handling systems a respective time slot for performing the job at such information handling system, in order to avoid or minimize overlap among the respective time slots, and creating for each of the plurality of information handling systems a respective job request for performing the job at such information handling system, the job request including a scheduled time for execution of the job based on the respective time slot of such information handling system.