Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: Embodiments are described for supporting 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 according. 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.

Abstract: 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.

Abstract: Present invention discloses a high strength hot rolled steel product with tensile strength at least 1100 MPa and elongation not less than 21%. The steel further has uniform elongation not less than 10% and yield and tensile ratio 0.6-0.7. The steel further has tensile toughness in the range 19-23.5 GPa %. The developed steel is primarily aimed for automotive structural applications and also for many other such as defence where good combination of strength and ductility required is very high. The developed steel product has following composition C: 0.15-0.23, Mn: 0.8-2.1, Si: 0.3-1.1, Cr: 0.8-1.3, Mo: 0.08-0.25, Nb: 0.018-0.035, Ti—0.01-0.1 S—0.008 max, P—0.025 max, Al—0.05 to 0.3, N—0.005 max. The liquid metal was continuous cast into slab casting. The cast slab was soaked above 1150° C. for few hours and subsequently the cast structure was broken by deformation prior to hot rolling.

Abstract: 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.

Abstract: A method includes receiving a host operation request sent without a first credential that is associated with a first user, wherein the host operation request by a second user includes a second user credential, the second user is an administrator of a systems management application, and the first user has a privilege to perform the host operation request. The method also sends the host operation request to a host operating system agent to generate an authentication token, the host operation request includes a digital certificate associated with the management controller, and the authentication token based on the first user credential of the first user. The method may also receive the authentication token generated by the host operating system agent, and send a response to the host operation request of the second user, wherein the response includes the authentication token.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.