Abstract: An information handling system includes a console bid manager that may intercept an event from a managed node, transmit notification to eligible management consoles for bids on the event, process the bids to determine one or more interrelated actions in response to the event, and coordinate performance of the one or more interrelated actions in handling the event. The performance of the one or more interrelated actions may be delegated to the eligible management consoles to resolve the event from the managed node.

Abstract: Systems and methods provided for vulnerability proofing updates to an IHS (Information Handling System). Upon receipt of an update to hardware component configurations of the IHS, vulnerability proofing requirements for modifications to the hardware component configurations are retrieved, including requirements for modifications that are validated for operation of a computational workload by the IHS. Based on the vulnerability proofing requirements, catalogs specifying known vulnerabilities of hardware components are consulted to determine whether the modifications are identified as vulnerable in the catalogs and whether remediations to the identified vulnerabilities are validated for operation of the workload. If the modifications are not identified as vulnerable in the catalogs, the update is transmitted to the IHS. If the modifications are identified as vulnerable in the catalogs and remediations to the identified vulnerabilities are not validated for operation of the workload, the update is terminated.

Abstract: Systems and methods provided for vulnerability proofing updates to an IHS (Information Handling System). Upon receipt of an update to hardware component configurations of the IHS, vulnerability proofing requirements for modifications to the hardware component configurations are retrieved, including requirements for modifications that are validated for operation of a computational workload by the IHS. Based on the vulnerability proofing requirements, catalogs specifying known vulnerabilities of hardware components are consulted to determine whether the modifications are identified as vulnerable in the catalogs and whether remediations to the identified vulnerabilities are validated for operation of the workload. If the modifications are not identified as vulnerable in the catalogs, the update is transmitted to the IHS. If the modifications are identified as vulnerable in the catalogs and remediations to the identified vulnerabilities are not validated for operation of the workload, the update is terminated.

Abstract: Systems and methods provided for vulnerability proofing updates to an IHS (Information Handling System). Upon receipt of an update to hardware component configurations of the IHS, vulnerability proofing requirements for modifications to the hardware component configurations are retrieved, including requirements for modifications that are validated for operation of a computational workload by the IHS. Based on the vulnerability proofing requirements, catalogs specifying known vulnerabilities of hardware components are consulted to determine whether the modifications are identified as vulnerable in the catalogs and whether remediations to the identified vulnerabilities are validated for operation of the workload. If the modifications are not identified as vulnerable in the catalogs, the update is transmitted to the IHS. If the modifications are identified as vulnerable in the catalogs and remediations to the identified vulnerabilities are not validated for operation of the workload, the update is terminated.

Abstract: An information handling system receives a notification regarding a state of the information handling system, and determines an alert management policy associated with the notification regarding the state of the information handling system. The system also applies an alert management action to enforce the alert management policy.

Abstract: A method for managing a resource system includes obtaining, by a hardware resource manager, a firmware update lockdown request for a lockdown for a firmware device of the resource system, in response to the firmware update lockdown request: identifying a firmware protocol corresponding to the firmware device, generating a firmware lockdown command corresponding to the firmware device based on the firmware protocol, and initiating updating of a lockdown policy based on the firmware lockdown command.

Abstract: A method for managing a resource system includes obtaining, by a hardware resource manager, a firmware update lockdown request for a lockdown for a firmware device of the resource system, in response to the firmware update lockdown request: identifying a firmware protocol corresponding to the firmware device, generating a firmware lockdown command corresponding to the firmware device based on the firmware protocol, and initiating updating of a lockdown policy based on the firmware lockdown command.

Abstract: An information handling system includes a console bid manager that may intercept an event from a managed node, transmit notification to eligible management consoles for bids on the event, process the bids to determine one or more interrelated actions in response to the event, and coordinate performance of the one or more interrelated actions in handling the event. The performance of the one or more interrelated actions may be delegated to the eligible management consoles to resolve the event from the managed node.

Abstract: In one or more embodiments, one or more systems, one or more methods, and/or one or more processes may: receive, via a network, multiple discovery messages respectively from multiple information handling systems (IHSs); receive, via the network, a first message associated with a first event from a first information handling system of the multiple IHSs; determine, based at least on the first message, that none of multiple rules is associated with the first event; in response to determining that none of the multiple rules is associated with the first event, provide a second message associated with the first event to a back end information handling system (IHS); receive, from the back end IHS, data indicating how to handle the first event; add, to the multiple rules, a rule based at least on the data indicating how to handle the first event; and provide the rule to the multiple IHSs.

Abstract: An asset includes physical computing resources and a physical computing resources manager. The physical computing resources manager obtains a resource update for the asset; makes a determination that the resource update requires a reset of a portion of the physical computing resources; and, based on the determination, resets the portion of the physical computing resources during a low resource consumption reboot of the asset without resetting a second portion of the physical computing resources, the second portion of the physical computing resources are not reset as part of the low resource consumption reboot.

Abstract: Methods, systems, and computer programs encoded on computer storage medium, for performing firmware activation, including obtaining input/output (I/O) metrics of the disks; determining an index value for the disk based on a disk weighted index (DWI); determining a DWI value for the array of disks based on the index value for each disk of the array of disks; comparing the DWI value for the array of disks to a DWI threshold; determining that the DWI value for a first array of disks is greater than the DWI threshold, and in response: aggregating the I/O metrics for each disk of the first array of disks; comparing the aggregated I/O metrics for the first array of disks to an activation threshold; determining that the aggregated I/O metrics for the first array of disks is less than the activation threshold, and in response triggering firmware activation for the first array of disks.

Abstract: In one or more embodiments, one or more systems, one or more methods, and/or one or more processes may: receive, via a network, multiple discovery messages respectively from multiple information handling systems (IHSs); receive, via the network, a first message associated with a first event from a first information handling system of the multiple IHSs; determine, based at least on the first message, that none of multiple rules is associated with the first event; in response to determining that none of the multiple rules is associated with the first event, provide a second message associated with the first event to a back end information handling system (IHS); receive, from the back end IHS, data indicating how to handle the first event; add, to the multiple rules, a rule based at least on the data indicating how to handle the first event; and provide the rule to the multiple IHSs.

Abstract: Systems and methods for transferring firmware updates using an in-band interface are described. In an embodiment, an Information Handling System (IHS) may include a processor and a memory coupled to the processor, the memory having program instructions stored thereon that, upon execution, cause the IHS to: receive a firmware update package having a payload; create a namespace in a persistent memory; copy the payload to a segment of the persistent memory associated with the namespace; and write, to an Extensible Firmware Interface (EFI) variable, an Emulator Device Path (EDP) pointing to the payload.

Abstract: An information handling system includes a basic input/output system (BIOS) that performs a firmware boot operation. During the firmware boot operation, the BIOS determines whether a driver pack management controller setting is enabled within a baseboard management controller of the information handling system. In response to the driver pack management controller setting being enabled, the BIOS copies a binary utility from the baseboard management controller to a system memory, and creates an operating system specific platform binary table to point to the binary utility on the baseboard management controller. In response to the operating system being initialized, a processor invokes the binary utility, mounts a memory partition of the baseboard management controller as a virtual drive of the operating system, and executes the operating system specific binary stage under a fixed globally unique identifier to install a driver pack.

Abstract: An information handling system includes a basic input/output system (BIOS) that performs a firmware boot operation. During the firmware boot operation, the BIOS determines whether a driver pack management controller setting is enabled within a baseboard management controller of the information handling system. In response to the driver pack management controller setting being enabled, the BIOS copies a binary utility from the baseboard management controller to a system memory, and creates an operating system specific platform binary table to point to the binary utility on the baseboard management controller. In response to the operating system being initialized, a processor invokes the binary utility, mounts a memory partition of the baseboard management controller as a virtual drive of the operating system, and executes the operating system specific binary stage under a fixed globally unique identifier to install a driver pack.

Abstract: Methods, systems, and computer programs encoded on computer storage medium, for performing firmware activation, including obtaining input/output (I/O) metrics of the disks; determining an index value for the disk based on a disk weighted index (DWI); determining a DWI value for the array of disks based on the index value for each disk of the array of disks; comparing the DWI value for the array of disks to a DWI threshold; determining that the DWI value for a first array of disks is greater than the DWI threshold, and in response: aggregating the I/O metrics for each disk of the first array of disks; comparing the aggregated I/O metrics for the first array of disks to an activation threshold; determining that the aggregated I/O metrics for the first array of disks is less than the activation threshold, and in response triggering firmware activation for the first array of disks.

Abstract: Systems and methods for transferring firmware updates using an in-band interface are described. In an embodiment, an Information Handling System (IHS) may include a processor and a memory coupled to the processor, the memory having program instructions stored thereon that, upon execution, cause the IHS to: receive a firmware update package having a payload; create a namespace in a persistent memory; copy the payload to a segment of the persistent memory associated with the namespace; and write, to an Extensible Firmware Interface (EFI) variable, an Emulator Device Path (EDP) pointing to the payload.

Abstract: An asset includes physical computing resources and a physical computing resources manager. The physical computing resources manager obtains a resource update for the asset; makes a determination that the resource update requires a reset of a portion of the physical computing resources; and, based on the determination, resets the portion of the physical computing resources during a low resource consumption reboot of the asset without resetting a second portion of the physical computing resources, the second portion of the physical computing resources are not reset as part of the low resource consumption reboot.

Abstract: A method, an information handling system (IHS) and a data center location system for determining physical locations of devices in a data center. The method includes generating an initial grouping of servers into a plurality of racks based on the at least one of a MAC address or IP address. Each server in a first rack is paired with each other server in communication with a switch aggregator to generate server pairs. The server pairs are transmitted to the respective servers. Each of the servers are triggered to measure and transmit received signal strength indication (RSSI) values for its respective server pairs. Positions of the servers in rows are determined based on the RSSI values. An intermediate grouping of the servers in rows is generated based on the determined positions.

Abstract: A method, system and computer-usable medium are disclosed for determining a projected warranty cost for use of an electronic product comprising: generating a warranty cost projection model based on historical usage data associated with the electronic product; acquiring customer specific usage data for the electronic product of an existing customer, wherein the customer specific usage data includes usage data acquired from the electronic product during operation of the electronic product by the existing customer; and determining a warranty cost projection for use of the electronic product by the existing customer, wherein the warranty cost projection is determined by applying the customer specific usage data to the warranty cost projection model.