Hewlett Packard Enterprise Development LP

Patrick Schoeller

Lidia Warnes

David F Heinrich

Alan L Goodrum

Suhas Shivanna

Charles W Cochran

Scott P Faasse

David J Koenen

Example implementations relate to system and method of managing transitioning of a computing system to a power-on state from a standby-power state. The computing system includes a manageability controller, an initialization controller, an auxiliary device, and a processor. In such examples, the manageability controller may first determine an initialization status of the auxiliary device from a data corresponding to the auxiliary device, when the computing system is transitioning from the standby-power state to the power-on state. In one or more examples, the initialization status may include the auxiliary device in an initialized stage or a non-initialized stage. Later, the manageability controller may direct the initialization controller to delay the transitioning of the computing system from the standby-power state to the power-on state, in response to determining that the initialization status of the auxiliary device is in the non-initialized stage.

Managing transitioning of computing system to power-on state from standby-power state

An example device includes a processor coupled to a network and a memory coupled to the processor. The memory includes computer code for causing the processor to establish a secure connection between a manageability application and an interconnect device, the interconnect device being in communication with a newly connected networked device; and securely communicate, from the manageability application to the interconnect device, temporary login information for the networked device.

Secure login information

In one example in accordance with the present disclosure, a system for partial backup during runtime includes a memory module having a volatile memory and a non-volatile memory. The system also includes a backup controller. The backup controller determines that a backup should occur in the memory module. The backup controller determines a backup domain of the volatile memory. The backup controller causes a deactivation domain of the volatile memory to be deactivated, where the deactivation domain includes the backup domain. The backup controller causes the backup to initiate during normal runtime of the system. The backup includes data in the backup domain of the volatile memory being saved to the non-volatile memory.

Partial backup during runtime for memory modules with volatile memory and non-volatile memory

Examples provide systems and a method for handling errors during run-time back up of volatile memory. The method includes initiating a backup of a volatile memory domain to a non-volatile memory domain. Memory registers are polled for completion of the backup. It is determined if the backup was successful. If not successful, an operating system (OS) is notified that the backup failed, and the backup is completed to an alternate media.

Handling errors during run time backups

Examples for shutdown of computing devices () are described In an example, a shutdown event based on a shutdown criterion may be detected The shutdown criterion may be based on available power of an auxiliary power supply unit () In response to detection of the shutdown event, a shutdown trigger to initiate shutdown of a computing device () powered by the auxiliary power supply unit () may be generated. Further, the shutdown trigger may be provided to a remote management processor () of the computing device (). The shutdown trigger may be provided based on port data (), which indicates an outlet path from the auxiliary power supply unit () to the at least one computing device.

Growing community of inventors

Houston, TX, United States of America

Patrick Schoeller