American Megatrends, Inc.

American Megatrends International, LLC

Paul Anthony Rhea

Stefano Righi

Saikat Bhattacharjee

Madhan B Santharam

Muthukkumaran Ramalingam

Oleksiy Yakovlev

Ganesan Vengateswaran

Satheesh Thomas

Presanna Raman

Brandon Burrell

An application framework for managing information technology ('IT') infrastructure includes components that enable jobs to be defined and executed that perform IT infrastructure management tasks. Jobs are defined utilizing a user interface (“UI”) that includes a first pane that provides functionality for receiving a selection of a target type of IT infrastructure for a job. Compatible action blocks are then displayed in a second pane of the UI. User input can be received associating action blocks with a third pane of the UI. When user input is received associating an action block with the third pane of the UI, a task identifier is displayed in the third pane of the UI. The UI can also receive a selection of target devices upon which the actions defined by a job are to be performed. The framework executes program code corresponding to action blocks in the job on the target devices.

Application framework for managing information technology infrastructure

A computing system includes a baseboard management controller ('BMC') that receives a security token from a management system. The computing system also executes a firmware that collects measurements from components of the computing system. The measurements include data describing the components for use in attestation. The firmware provides the measurements to the BMC, which generates a digital signature of the measurements and the security token. The BMC provides the measurements and the digital signature to the management system, which attempts to verify the digital signature utilizing a public key associated with the BMC. If the management system can verify the digital signature, then the BMC utilized the correct security key to generate the digital signature and the measurements were not tampered with after collection by the firmware. The measurements can then be utilized to attest the computing system.

Out-of-band (OOB) remote attestation

Technologies are disclosed herein that allow for utilization of firmware specific data through an Advanced Configuration and Power Interface (ACPI) Firmware Identification (FID) table in a computing system. The ACPI FID table can be loaded during a boot of a computer system. The ACPI FID table can be read after an operating system has been loaded on the computer system. Based upon firmware specific data in the ACPI FID table, functionality provided by the application can be restricted. The use of various features provided by the application can be restricted or the application can be restricted from executing entirely. Compatibility between the application and the firmware can be ensured based upon firmware specific data in the ACPI FID table.

Providing firmware specific information via ACPI tables

Technologies are provided for generation of firmware configured to restrict use of a firmware tool. Some embodiments include a computing system that can obtain firmware source code comprising a module configured to copy contents of a digitally signed binary file to an advanced configuration and power management interface (ACPI) table at runtime of a firmware. The computing system can generate a firmware image of the firmware, the firmware image comprising the module, a first firmware globally unique identifier (GUID), and a defined area storing digital content that remains unchanged upon a change to the firmware. The computing system also can obtain a binary file comprising a second firmware GUID, a firmware tool GUID, and a feature GUID, and can digitally sign the binary file using a private encryption key to generate the digitally signed binary file. The computing system can store the digitally signed binary file within the defined area.

Generation of a firmware configured for use in restricting the use of a firmware tool

A firmware includes a firmware module for copying a digitally signed binary file that includes a firmware globally unique identifier (GUID), tool GUIDs, and feature GUIDs to an Advanced Configuration and Power Management interface (ACPI) table (the Firmware Enabled Tool Registry (FETR) table). If the FETR table is stored in memory, a firmware tool determines whether a digital signature of the signed binary file can be verified. If the digital signature can be verified, the firmware tool determines if the firmware GUID stored in the FETR table matches a firmware GUID stored in another ACPI table. If the firmware GUIDs match, the firmware tool determines whether its tool GUID matches a tool GUID stored in the FETR table. The firmware tool can continue to execute if the tool GUIDs match. Firmware tool features are enabled if feature GUIDs in the FETR table match feature GUIDs of the firmware tool.

Restricting the use of a firmware tool to a specific platform

A firmware development tool generates platform-specific firmware images for a multitude of different computing platforms. A multi-platform firmware image creation tool receives the platform-specific firmware images and generates a multi-platform firmware image therefrom. A portion of the multi-platform firmware image includes firmware files that are common across all of the platform-specific firmware images. Other portions of the multi-platform firmware image include firmware files that are specific to each of the platform-specific firmware images. At boot time of a computer system utilizing the multi-platform firmware image, the platform that the computer system uses is detected. The firmware files that are common across the platform-specific firmware images are then loaded into memory. The firmware files that are specific to the detected platform are also loaded into memory. Once the firmware files have been loaded into memory, they can be executed to boot the computer system and provide other types of functionality.

Multi-platform firmware support

Methods and computer-readable media provide for the creation of basic input/output system (BIOS) components. Embodiments include a component creation wizard that guides a user through the component creation process. The component creation wizard utilizes a project template file that includes templates of the required files for any given component, organized into a folder-based file structure. The component creation wizard searches the folders within the project template file according to project type, component categories, and template categories, as determined by a user, to locate and copy the applicable template files to create a BIOS component template.

Template-based BIOS component creation

Methods and computer-readable media provide for the creation of a basic input/output system (BIOS) project. Embodiments include a project creation wizard that guides a user through the project creation process. The project creation wizard utilizes a script file that includes entries corresponding to each category of BIOS component that should be included within a given project. Upon receiving a project type indicator from the user, the project creation wizard locates a corresponding script file and parses through each entry of the script file, systematically utilizing the corresponding information to search for applicable BIOS components and to allow or reject user selections of the located BIOS components according to the data within the script file entry. The BIOS components that are selected according to the script file data are copied to a designated location to create a BIOS project file.

Template-based BIOS project creation

Methods and systems provide automated testing of computer facilitated audio input and output devices. A tone is converted from a digital to analog signal and is sent to a sound mixing device. At the sound mixing device, the analog tone is looped back through a recording line to an analog to digital converter. The recorded tone is converted from a time domain to a frequency domain using a Fast Fourier Transform (FFT) analysis. The frequency, and if desired, the intensity of the recorded tone is compared against the known frequency and at the desired intensity of the played tone. If the recorded tone is the same as the played tone, the ability of the sound card to play the tone is designated as passing.

Audio feedback test

Methods and systems provide automated testing of computer facilitated audio input and output devices. A tone is converted from a digital to analog signal and is sent to a sound mixing device. At the sound mixing device, the analog tone is looped back through a recording line to an analog to digital converter. The recorded tone is converted from a time domain to a frequency domain using a Fast Fourier Transform (FFT) analysis. The frequency, and if desired, the intensity of the recorded tone is compared against the known frequency, and at the desired intensity of the played tone. If the recorded tone is the same as the played tone, the ability of the sound card to play the tone is designated as passing. The FFT analysis results also may be utilized to calculate a signal to noise ratio (SNR), a total harmonic distortion (THD) value, a total harmonic distortion plus noise (THD+N) and a DC-offset value. Each of these calculated values may be compared against pass/fail thresholds for the played tone.

A method, system, and apparatus enabling the use of server-side entry points when providing diagnostics on-demand services are provided. A request is received at a client computer to perform a diagnostic. In response to the request, an entry point is called on a server computer to retrieve a configuration file identifying one or more additional entry points. One of the entry points identified in the configuration file may be called to obtain authorization to download a diagnostics module to perform the requested diagnostic. Another entry point may be provided at the server computer for actually downloading the requested module. An additional entry point may also be called for obtaining a data file containing instructions regarding the installation of the diagnostics module and other configuration data. Another entry point may be utilized to obtain authorization to execute the diagnostics module and to perform the requested diagnostic. Another entry point provided at the server computer may be called with the results of the execution of the diagnostics module. If an error condition occurs, another entry point may be called to report the error condition.

Method, system, and apparatus for providing and utilizing server-side entry points for use in diagnostics on-demand services

A method, system, computer-readable medium, and computer-controlled apparatus are provided for logging and accessing diagnostic result messages. Diagnostic client modules transmit diagnostic result messages to a diagnostic event service module. The diagnostic event service module receives diagnostic result messages from the diagnostic client modules and relays the messages to diagnostic subscriber modules. Diagnostic subscriber modules may comprise a log writer module for storing the messages in a diagnostic results database or a progress viewer module for displaying an indication of the progress of a diagnostic test based on the diagnostic result messages. A query access layer module, a log viewer module, a report tools module, and a report server module may also be provided.

Method and system for logging and accessing diagnostic result messages

An instrumentation data provider module is provided for use within a diagnostics application program. The instrumentation data provider module provides a communication path between legacy, or proprietary, diagnostics modules and a standard instrumentation platform. Through the instrumentation data provider module, diagnostics status messages may be translated into event messages and forwarded to the instrumentation platform. A data consumer module for use within a diagnostics application program is also provided. The instrumentation data consumer module provides a communication path between a presentation layer and an instrumentation platform. Through the data consumer module, a management console or other type of management application can register for and receive events from the instrumentation platform.

Growing community of inventors

Lawrenceville, GA, United States of America

Paul Anthony Rhea