Dell Products Inc.

Prakash Nara

Sudhir Vittal Shetty

Madhav Karri

Wei G Liu

Marshal F Savage

Charles E Rose

Santosh Kumar

Vijayasimha Reddy Naga

Dahir Nur Herzi

Venkata Bala Koteswararao Donepudi

Rhushabh Bhandari

Jacob R Hutcheson

Kathleen A Hattaway

Balaji Shanmugam

Mukund Purshottam Khatri

Sanjay Sane

Balaji Rajagopalan

Babu Krishna Chandrasekhar

Stephanos S Heracleous

Mayur Bhosle

An LCS/NVMe/TCP storage target system includes a storage system having a storage controller, host systems that are coupled to the storage system, and a resource management system that is coupled to the storage system and the host systems. The resource management system provides a first LCS using a first host system, and configures the first host system and the storage controller to present a first namespace provided by the storage system to the first LCS via first Host NVMe Qualified Name(s) (HNQN(s)). The resource management system then moves the first LCS to a second host system, removes the first HNQN(s) from the storage controller and the first host system, and configures the second host system and the storage controller to present the first namespace provided by the storage system to the first LCS via second HNQN(s).

LCS-NVME/TCP storage target system

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

In accordance with embodiments of the present disclosure, a system may include a plurality of chassis, each chassis comprising a plurality of information handling systems and a private inter-chassis network configured to couple the plurality of chassis to one another. Each chassis of the plurality of chassis may be configured to advertise a message to the private inter-chassis network, the message comprising information regarding such chassis. The plurality of chassis may detect the presence of each other based on messages advertised from each chassis and the plurality of chassis may nominate a lead chassis from the plurality of chassis to serve as a single point of management of the system.

Systems and methods of group automation for multi-chassis management

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

An information handling system may include a processor, a memory coupled to the processor, the memory having program instructions stored thereon that, upon execution by the processor, cause the processor to: (i) responsive to a physical connection being made between components of a system comprising multiple information handling system chassis, receive a message; (ii) process information present in the message indicative of a topology of connectivity among the components of the system; and (iii) update a data structure defining the topology of connectivity of the various components of the system based on the information present in the message.

Systems and methods for network topology discovery

In accordance with embodiments of the present disclosure, a method may include, in response to an attempted execution of an executable endpoint, determining if the executable endpoint is unexpired, performing an endpoint operation of the executable endpoint if the endpoint is unexpired, after performance of the endpoint operation, determining if the executable endpoint has met a condition for expiration, and modifying metadata associated with the executable endpoint such that the executable endpoint is prevented from further attempted execution if the executable endpoint has met a condition for expiration.

Systems and methods for dynamic availability of executable endpoints

A chassis management controller may, responsive to initialization of the chassis management controller, execute cluster-aware services of the chassis management controller in a stand-by mode and communicate via a private management network fabric to determine if one or more other chassis management controllers are communicatively coupled to the private management network fabric. The chassis management controller may also, responsive to determining that one or more other chassis management controllers are communicatively coupled to the private management network fabric, alone or in concert with the one or more other chassis management controllers, elect an active chassis management controller from a plurality of chassis management controllers comprising the chassis management controller and the one or more other chassis management controllers.

Systems and methods for high availability of management controllers

A request to perform a system configuration operation at an information handling system is received at a service processor included at the information handling system. The service processor determines that the configuration operation completed successfully and prepares an abstraction of the system configuration operation that can be used to replicate the system configuration operation at another information handling system. The abstraction is provided to a coordinating processor. The coordinating processor generates an identifier that uniquely identifies the abstraction and provides the identifier to the service processor. The service processor stores the identifier.

Growing community of inventors

Round Rock, TX, United States of America

Prakash Nara