Abstract: A first information handling system may receive a telemetry metric report from a client information handling system. The first information handling system may determine that one or more characteristics of the telemetry metric report do not match one or more predetermined telemetry metric report characteristics. The first information handling system may perform one or more corrective actions based, at least in part, on the determination that the one or more characteristics of the telemetry metric report do not match one or more predetermined telemetry metric report characteristics.

Abstract: Embodiments provide unique identification of telemetry reports generated by components of an IHS (Information Handling System) that supports a plurality of metric data sources. A source of metric data is detected, where the source may be a fixed or replaceable IHS component. The metric source is identified within a device descriptor table maintained by a remote access controller of the IHS. Based on a unique user-friendly label that is associated with the metric data source in the device descriptor table, the metric source is configured to generate metric reports. The generated metric reports are received and the label provided by the metric source is used to store data from the metric reports in a database row using the label as a unique database key. The user-friendly label can be used to perform efficient database queries without using a separate database column for storing a user-friendly description of the metric source.

Abstract: Telemetry system metric data that is collected within a data center may be collectively analyzed in order to identify zones within the data center that exhibit deviations in reported metric data. The analyzed metric data is collected from IHSs (Information Handling Systems), such as servers, operating in the data center. The metric data reported by the respective IHSs identifies the location the IHS within the data center. The collected metric data is analyzed to identify metrics that are correlated with locations within the data center. Within the identified metric data that is correlated with data center locations, a zone of the data center is identified that includes a subset of IHSs that have reported anomalous metric data relative to the metric data reported by neighboring IHSs. For instance, such a zone may be an aisle of the data center, one or more racks, and/or rows of servers spanning multiple racks.

Abstract: Systems and methods utilize telemetry data to provide administrators with metric information related to a detected IHS (Information Handling System) event, such as an error condition, where the provided metric information is particularized to the context of the event. A remote access controller (RAC) of the IHS stores metric reports received from metric sources. The RAC receives an indication of the event that specifies a first IHS component as a source of the event and specifies a time associated with the event. The RAC identifies stored metric reports generated by the first component prior to the first time and identifies stored metric reports generated by components that are logically and/o physically related to the first component. The RAC generates an event report that includes the metric reports generated by the first component prior to the first time and the metric reports generated by components related to the first component.

Abstract: A system for distributing firmware, comprising a group controller operating on a processor and configured to perform an algorithmic process of sending an update task with a download host to one of two or more group members. A group member operating on a processor and configured to perform an algorithmic process of receiving the update task with the download host and to request a payload file from the download host.

Abstract: A first information handling system may receive a telemetry metric report from a client information handling system. The first information handling system may determine that one or more characteristics of the telemetry metric report do not match one or more predetermined telemetry metric report characteristics. The first information handling system may perform one or more corrective actions based, at least in part, on the determination that the one or more characteristics of the telemetry metric report do not match one or more predetermined telemetry metric report characteristics.

Abstract: Embodiments provide unique identification of telemetry reports generated by components of an IHS (Information Handling System) that supports a plurality of metric data sources. A source of metric data is detected, where the source may be a fixed or replaceable IHS component. The metric source is identified within a device descriptor table maintained by a remote access controller of the IHS. Based on a unique user-friendly label that is associated with the metric data source in the device descriptor table, the metric source is configured to generate metric reports. The generated metric reports are received and the label provided by the metric source is used to store data from the metric reports in a database row using the label as a unique database key. The user-friendly label can be used to perform efficient database queries without using a separate database column for storing a user-friendly description of the metric source.

Abstract: A system for distributing firmware, comprising a group controller operating on a processor and configured to perform an algorithmic process of sending an update task with a download host to one of two or more group members. A group member operating on a processor and configured to perform an algorithmic process of receiving the update task with the download host and to request a payload file from the download host.

Abstract: Telemetry system metric data that is collected within a data center may be collectively analyzed in order to identify zones within the data center that exhibit deviations in reported metric data. The analyzed metric data is collected from IHSs (Information Handling Systems), such as servers, operating in the data center. The metric data reported by the respective IHSs identifies the location the IHS within the data center. The collected metric data is analyzed to identify metrics that are correlated with locations within the data center. Within the identified metric data that is correlated with data center locations, a zone of the data center is identified that includes a subset of IHSs that have reported anomalous metric data relative to the metric data reported by neighboring IHSs. For instance, such a zone may be an aisle of the data center, one or more racks, and/or rows of servers spanning multiple racks.

Abstract: Systems and methods utilize telemetry data to provide administrators with metric information related to a detected IHS (Information Handling System) event, such as an error condition, where the provided metric information is particularized to the context of the event. A remote access controller (RAC) of the IHS stores metric reports received from metric sources. The RAC receives an indication of the event that specifies a first IHS component as a source of the event and specifies a time associated with the event. The RAC identifies stored metric reports generated by the first component prior to the first time and identifies stored metric reports generated by components that are logically and/o physically related to the first component. The RAC generates an event report that includes the metric reports generated by the first component prior to the first time and the metric reports generated by components related to the first component.

Abstract: Methods and systems for access in a management controller group hierarchy may involve receiving a request for a user at an information handling system, determining whether a link of trust is established, and validating the single sign-on request. The request may be to authenticate the user for access using a single sign-on token. Determination of whether the link of trust is established may be based on an initial login location stored in the single sign-on token. Validation of the single sign-on token may be based on a determination that the link of trust is established.

Abstract: A converged infrastructure includes a shared device and compute devices. The compute devices include a baseboard management controller and applications including one or more entitled initiators. The baseboard management controllers generate a distributed provision list including certificates chains for the entitled initiators; and configure the shared device with the certificate chains. The shared device receive a critical command and an encrypted hash, determine a calculated hash of the critical command, decrypt the encrypted hash using keys from the certificate chains, and compare the calculated hash with the decrypted hashes to determine if the critical command comes from one of the entitled initiators.

Abstract: Methods, systems, and computer programs encoded on computer storage medium, for identifying a first user access event that failed authentication at the first computing device; creating a transaction block of a distributed ledger based on the first user access event; determining that data indicating the first user access event is not included by the distributed ledger, and in response, adding the transaction block to a temporal vector space of the distributed ledger; sharing, to each other computing device of the local network, the transaction block, wherein each of the others computing devices of the local network updates a local copy of the distributed ledger to include the transaction block in the temporal vector space.

Abstract: A system for distributing firmware, comprising a group controller operating on a processor and configured to perform an algorithmic process of sending an update task with a download host to one of two or more group members. A group member operating on a processor and configured to perform an algorithmic process of receiving the update task with the download host and to request a payload file from the download host.

Abstract: A system for distributing firmware, comprising a group controller operating on a processor and configured to perform an algorithmic process of sending an update task with a download host to one of two or more group members. A group member operating on a processor and configured to perform an algorithmic process of receiving the update task with the download host and to request a payload file from the download host.

Abstract: A host device access monitoring and reporting system includes a management system coupled to server devices through a network. Each server device includes a BIOS that generates and transmits pre-boot access event reports for pre-boot access events occurring prior to the completion of a boot process for that server device, and an operating system that generates and transmits post-boot access event reports for post-boot access events occurring subsequent to the completion of the boot process for that server device. A remote access controller in each server device receives pre-boot access event reports from the BIOS in that server device and, in response, publishes pre-boot access event notifications to the management system. The remote access controller in each server device also receives the post-boot access event reports from the operating system in that server device and, in response, publishes post-boot access event notifications to the management system.

Abstract: A converged infrastructure includes a shared device and compute devices. The compute devices include a baseboard management controller and applications including one or more entitled initiators. The baseboard management controllers generate a distributed provision list including certificates chains for the entitled initiators; and configure the shared device with the certificate chains. The shared device receive a critical command and an encrypted hash, determine a calculated hash of the critical command, decrypt the encrypted hash using keys from the certificate chains, and compare the calculated hash with the decrypted hashes to determine if the critical command comes from one of the entitled initiators.

Abstract: Methods and systems for providing quality of service to an information handling system may involve generating a new transport encryption key for a management controller group, notifying nodes in the management controller group to negotiate for the new transport encryption key, and encrypting a first message to be sent to a first node in the management controller group using a current transport encryption key. The new transport encryption key for encrypted communications in the management controller group and to replace a current transport encryption key. The first message encrypted after notifying the nodes in the management controller group to negotiate for the new transport encryption key. The nodes of the management controller group including the first node.

Abstract: Methods and systems for account authentication in a distributed computing node group may involve sending a message to a member, the message having a first timestamp, increasing an authentication failure count, receiving a first key-exchange message from the member, the first key-exchange message having a second timestamp, evaluating the second timestamp, and determining whether to ignore the first key-exchange message based on an evaluation of the second timestamp. The first timestamp may be associated with a message received from the member prior to sending the message with the first timestamp to the member. The first key-exchange message may include a value computed by the member based on a group passcode shared with the member. The evaluation of the second timestamp may be based on at least one of a default value, the authentication failure count, or a timestamp associated with the group passcode.

Abstract: Methods, systems, and computer programs encoded on computer storage medium, for identifying a first user access event that failed authentication at the first computing device; creating a transaction block of a distributed ledger based on the first user access event; determining that data indicating the first user access event is not included by the distributed ledger, and in response, adding the transaction block to a temporal vector space of the distributed ledger; sharing, to each other computing device of the local network, the transaction block, wherein each of the others computing devices of the local network updates a local copy of the distributed ledger to include the transaction block in the temporal vector space.