Dell Products Inc.

Madhav Karri

Sudhir Vittal Shetty

Prakash Nara

Wei G Liu

Marshal F Savage

Charles E Rose

Santosh Kumar

Vance Edward Corn

Vijayasimha Reddy Naga

Dahir Nur Herzi

Venkata Bala Koteswararao Donepudi

Rhushabh Bhandari

Kathleen A Hattaway

Mukund Purshottam Khatri

Jianwen Yin

Weijia Zhang

Scott Alan Lenharth

William C Edwards

A device management system that receives a first service request message for a remote device node, the request including an address identifier and a connection profile identifier. The system retrieves from a database protocol configuration information associated with the service request. The system connects to the remote device using the protocol configuration information and iterates through device packs and identifies a device type and support for in-band and out-of band application protocols for the remote device. The system retrieves and stores the retrieved device type and in-band and out-of band application protocols. The system further receives a second service request message that includes a device identifier of the remote device and iteratively connect to the remote device associated with the device identifier using each of the in-band and out-of band application protocols and retrieves an inventory of management operations associated with each application protocol.

System and method for dynamic and extensible management of device nodes

A method may include determining if both of two redundant operating system images for executing functionality of a chassis management controller were found during one or more previous boot sessions of the chassis management controller to be unsecure, wherein each operating system image comprises an integrated kernel and initial file root system stored in a respective first partition of a memory of the chassis management controller, verity hashes of a root file system of such operating system image, the verity hashes stored in a respective second partition of the memory, and the root file system of such operating system image stored in a respective third partition of the memory. The method may also include, in response to determining that one of the two redundant operating system images is secure, initiate verification of such operating system image to determine if such operating system image has indicia of tampering.

Systems and methods for secure boot and runtime tamper detection

A verification for a secure boot process may include determining a determined signature for a compendium stored in a memory where the compendium includes a bootloader and an operating system, accessing a verification signature corresponding to the compendium, and comparing the verification signature with the determined signature where if the verification signature is the same as the determined signature, the compendium is verified as secure and a secure boot process is performed with the bootloader and operating system. The compendium may include one or more applications such that the applications may be verified as secure with the verification signature.

System and method for secure boot of an information handling system using verification signature and including verifying applications

Systems and methods are provided that may be implemented to manage machine-specific System Profile Unique Data (SPUD) information for one or more information handling systems. Such SPUD information may be managed and transported through in-band and/or out-of-band processing and communications, and may be employed to make restoration of machine-specific data possible either through network data communications and/or local system data communications.

Systems and methods for intelligent system profile unique data management

The present disclosure provides, in some embodiments, a method for managing applications and resources. According to some embodiments, a power orchestrator may comprise (a) receiving information handling system resource status, (b) receiving one or more application registrations from one or more applications to be executed on the information handling system, (c) formulating a resource priority schedule using the received resource status and the one or more application registrations, (d) formulating a resource allocation schedule in accordance with the resource priority schedule, (e) communicating the resource allocation schedule to the one or more applications, and (f) allocating one or more resources to the one or more applications in accordance with the resource allocation schedule. A method may comprise, according to some embodiments, determining whether one or more of the one or more applications will submit a registration update and/or determining whether available resource(s) match demand and adjusting resource status to match demand.

Mechanism for application management during server power changes

Growing community of inventors

Austin, TX, United States of America

Madhav Karri