Dell Products Inc.

Sap Se

Rajib Saha

Chitrak Gupta

Anurag Sharma

Chandrasekhar Puthillathe

Parmeshwr Prasad

Santosh Hanamant Gore

Krishnaprasad Koladi

Raghavendra Venkataramudu

Bharath Koushik Bangalore Suryanarayana

Venkata Ramana Murthy K

Jitendra Kumar Rath

Vaideeswaran Ganesan

Raveendra Babu Madala

Babu Krishna Chandrasekhar

Sanjay Rao

Prasoon Kumar Sinha

Divya Vijayvargiya

Pravin Janakiram

Ramesha He

Sateesh Babu Chilamakuri

Faizal Sn

Srihari Srirangam

Chinmay Shripad Hegde

Jo Ann Varble

Sivakanth Jayaram

Sai Hari Prasad Pabbathi

Faizal Saidalavi Nabeesa

Prince Kumar

Ghislain Hude

Laurent Pelecq

Interaction with different remote cloud drives is achieved utilizing a drive engine comprising a browsing component and a file manager. The browsing component receives from a consumer, a request to perform an action (e.g., upload; download) with a particular cloud drive. In response to the request, the browsing component retrieves a directory from the cloud drive. The browsing component generates a JavaScript Object Notation (JSON) object including the directory, a placeholder, and a parameter, communicating same to the consumer. The file manager in turn receives from the consumer, the JSON object including selected directory information (e.g., upload destination folder; file for download). The file manager fills in the placeholder with a value. Based upon the value, the file manager communicates an action request to the cloud drive. In response, the file manager receives an action output (e.g., upload confirmation; downloaded content) from the remote storage, forwarding same to the consumer.

Cloud drive management

In an example, a framework is provided that provides a secure mechanism to limit misuse of licensed applications. Specifically, a mutual handshake is established, using existing properties of a requesting application, and wraps objects with dynamic parameters, such as a current timestamp, to perform masking, hashing, and encryption for the handshake.

Encrypted handshake for trust validation between two applications

Disclosed herein are system, method, and computer program product embodiments for utilizing non-RAM memory to implement a cloud storage system. An embodiment operates by receiving a request from an on-premises computer system to securely access a cloud drive by receiving an object specific template for an object. Based on the object specific template, an object specific plugin is selected, wherein the object specific plugin is configured to provide a connection to a cloud-based repository to obtain real time data for the object. An instance of the object is generated and communicated to a cloud plugin, wherein the cloud plugin is configured to communicate to a specific cloud drive through an HTTP client and further upload the instance of the object to the specific cloud drive.

Holistic way of cloud connector integration on existing on-premise product

An Information Handling System (IHS) includes multiple hardware devices, and a Baseboard Management Controller (BMC) in communication with the hardware devices. The BMC includes executable code to cause the BMC to receive a message associated with a non-registered hardware device that is not registered to be managed by the BMC in which the message formatted according to a native protocol of the BMC. The code further causes the code to transmit the message to a device plugin associated with the non-registered hardware device in which the device plugin comprises custom instructions that, upon execution by a system processor, cause the IHS to convert the message into a protocol associated with the non-registered hardware device, and forward the converted message to the non-registered hardware device using the protocol of the non-registered hardware device.

System and method for secure management of non-registered components of an information handling system using a baseboard management controller

An information handling system includes a network interface device configured to provide indications of faults on the network interface device, a baseboard management controller agent configured to receive the indications, and a baseboard management controller coupled to a management system. The management system mitigates the faults on the network interface device. The network interface device further detects a fault on the network interface device and provides an indication to the baseboard management controller agent in response to detecting the fault. The baseboard management controller agent further receives the indication from the network interface device, receives an identification of the management system from the baseboard management controller, and provides a second indication to the management system based upon the identification.

Rapid appraisal of NIC status for high-availability servers

An information handling system includes a service module that may detect an action performed on a passthrough device, invoke an application programming interface on a hypervisor, receive a response to the action on the passthrough device from the hypervisor, and push management information to a management controller. The hypervisor may detect the passthrough device, proxy an operating system call associated with the action to a guest operating system of the virtual machine over the application programming interface, and transmit the response received from the guest operating system to the service module. The guest operating system may echo the operating system call on a virtual machine, and proxy the response to the operating system call to the hypervisor.

System and method to monitor and manage a passthrough device

Support is provided for remote monitoring and management of non-standard devices of an IHS (Information Handling System) that are not supported by a remote management interface, such as the Redfish management interface. The IHS may be configured for remote management of a non-standard device as part of the manufacture of the IHS. Software for management of the non-standard device is validated against a checksum stored to the IHS during its manufacture to confirm the software for managing the non-standard device has not been altered. If the software is validated, the software is used to initialize a plugin for management of the non-standard device. Data collected by the plugin from monitoring of the non-standard device is provided to a remote access controller of the IHS and the remote access controller issues commands to the non-standard device via the plugin.

Systems and methods for remote management of non-standard devices

Methods and systems are provided for managing dynamic devices of an IHS (Information Handling System) that include re-programmable logic circuitry. The dynamic devices of the IHS are identified and the type of a dynamic device is determined based on operations implemented by the re-programmable logic circuitry of that dynamic device. The dynamic device is enrolled for management by a remote access controller of the IHS based on its determined type. Messages are registered for management of the dynamic device, where the messages are selected based on its determined type. Remote management of the dynamic device is initiated using the registered messages. Any programming that changes the type of the dynamic device of the dynamic device is detected. If a change is detected, the dynamic device is enrolled for remote management using updated messages based on its updated type.

Systems and methods for management of dynamic devices

A unified installer reduces system down time attributable to product installation, by eliminating redundant activities. An engine receives a request to install a first software product and a second software product. The engine references respective seed files of the first and second products to confirm their membership in a same family, and also to confirm compatibility between the product versions. The engine first performs a logical merger to create a merged seed file identifying components (e.g., deployment units, prerequisites, properties, features) that are duplicated between the products. Next, the engine performs a second, physical merger of the products to create a unified installer which avoids redundant components. The unified installer is passed by the engine to the installation procedure, which installs the components only once, thereby promoting efficiency and reducing system down time incurred by product installation.

Unified installer

An asset includes a physical computing resource. The physical computing resource is directly used by a virtual entity. The asset also includes a resource manager. The resource manager disconnects the virtual entity from the physical computing resource during a low resource consumption reboot of the asset until the low resource consumption reboot of the asset is complete. The resource manager also directly connects the virtual entity to the physical computing resource after the low resource consumption reboot of the asset.

System and method for managing devices during reboot

An information handling system includes a processor, a baseboard management controller (BMC) agent that establishes a Transport Layer Security (TLS) session including a first cryptographic parameter shared between the BMC and the BMC agent, receives a request to register the BMC agent with the BMC via the TLS session, and provides a second cryptographic parameter to the BMC agent. The BMC establishes a second TLS session including a third cryptographic parameter, determines that the second TLS session is suspected of being from a malicious agent, and renegotiates with the BMC agent using the second cryptographic parameter within the TLS session to share a fourth cryptographic parameter between the BMC and the first BMC agent in response to determining that the second TLS session is suspect.

System and method to secure renegotiation of connections between a baseboard management controller and a hosted agent

An information handling system includes a baseboard management controller (BMC) configured to communicate with a processor via a BMC-to-Operating System (OS) communication link, and a first device coupled to the processor and including a Management Component Transport Protocol (MCTP) module. The MCTP module provides access to a first manageability feature of the first device. A BMC agent a) receives a first MCTP command from the BMC via the BMC-To-OS communication link, the first MCTP command to configure the first manageability feature, and b) provides the first MCTP command to the MCTP module.

System and method to scale baseboard management controller management of storage instrumentation

A software update system includes a chassis housing a plurality of component, an Operating System (OS) engine that is configured to provide an OS, and a Baseboard Management Controller (BMC). The BMC is coupled to each of the plurality of components, as well as to the OS engine via an OS-to-BMC interface. The BMC retrieves a software update catalog that includes a plurality of software updates, and identifies OS software updates that are included in the plurality of software updates in the software update catalog, and component software updates that are included in the plurality of software updates in the software update catalog. The BMC provides the OS software updates to the OS engine via the OS-to-BMC interface, and the OS engine provides the OS software updates for the OS. The BMC then provides the component software updates for the plurality of components.

Software update system

An information handling system may include a host system including a host system processor and a host system memory coupled to the host system processor; and a management controller configured to provide out-of-band management of the host system. The management controller may be configured to establish a virtual console session between the host system and a remote terminal. The management controller may further be configured to, in response to a command from the remote terminal to send data from the remote terminal to the host system, mount a partition of the management controller such that the partition is accessible to the host system, wherein the partition includes the data. The management controller may be further configured to transmit a notification to the host system indicating the command and the partition, wherein the host system is configured to receive the data from the partition in accordance with the command.

Growing community of inventors

Bengaluru, India

Rajib Saha