Abstract: A bootloader process executing on a service management processor (SMP) subsystem for a server device determines whether flag stored within non-volatile memory of the subsystem is set. The flag corresponds to whether a full cold initialization process of the subsystem is to occur. In response to determining that the flag has not been set, the bootloader process loads an image stored in the non-volatile memory into volatile memory of the subsystem. The image corresponds to processes properly running on the SMP subsystem after the SMP subsystem has booted, including a management process. The processes begin executing on the subsystem. The management process, determines whether a hardware configuration change within the subsystem has been made since when the image was saved to the non-volatile memory. In response to determining that the hardware configuration change has been made, the management process sets the flag and rebooting the subsystem.

Abstract: A target server is queried to build an inventory of components installed within the target server. The target server has a boot process by which it is employed within a production environment. Updated software is received for each component from an update server, based on the inventory built. The boot process is configured so that the target server installs the updated software for each component the next time it boots, instead of being employed within the production environment. The target server is caused to boot such that it installs the updated software for each component. Upon completion of the target server installing the update software for each component, the boot process is reconfigured so that the next time the target server boots it is again employed within the production environment. The target server is again caused to boot such that it is again employed within the production environment.

Abstract: A bootloader process executing on a service management processor (SMP) subsystem for a server device determines whether an initialization flag stored within non-volatile memory of the subsystem is set. The initialization flag corresponds to whether a full cold initialization process of the subsystem is to occur. In response to determining that the initialization flag has not been set, the bootloader process loads an image stored in the non-volatile memory into volatile memory of the subsystem. The image corresponds to processes properly running on the SMP subsystem after the SMP subsystem has booted, including a management process. The processes begin executing on the subsystem. The management process, determines whether a hardware configuration change within the subsystem has been made since when the image was saved to the non-volatile memory. In response to determining that the hardware configuration change has been made, the management process sets the initialization flag and rebooting the subsystem.

Abstract: A method and system are provided for dynamically managing delivery of power to partitionable elements in a computer system while supporting terms of a Service Level Agreement (SLA). Parameters of the SLA are gathered in conjunction with the topology of the computer system. Transactions associated with the SLA are monitored and high and low usage periods are predicted based upon a history of transactions. Power to partitionable elements of the computer system may be adjusted during high and low usage periods. In addition, dynamic management of the partitionable elements is provided in response to current demands. Management of the partitionable elements is all made in compliance with the SLA.

Abstract: A power management system for a multiple compute component system. The management system enables operational management of individual compute components in two low power states of operation, suspend and hibernate. In addition, the management system enables granular management of power consuming accessories within an individual compute component. When a compute component is in the low power state of suspend or hibernate, it may be hot-swapped to a different locale. In addition, when a compute component is restored from a low power state of hibernate, it may access an alternate image in the system. Accordingly, the power management system allows for five state of operation of an individual component in a multiple compute component system.

Abstract: A target server is queried to build an inventory of components installed within the target server. The target server has a boot process by which it is employed within a production environment. Updated software is received for each component from an update server, based on the inventory built. The boot process is configured so that the target server installs the updated software for each component the next time it boots, instead of being employed within the production environment. The target server is caused to boot such that it installs the updated software for each component. Upon completion of the target server installing the update software for each component, the boot process is reconfigured so that the next time the target server boots it is again employed within the production environment. The target server is again caused to boot such that it is again employed within the production environment.

Abstract: A method and system are provided for dynamically managing delivery of power to partitionable elements in a computer system while supporting terms of a Service Level Agreement (SLA). Parameters of the SLA are gathered in conjunction with the topology of the computer system. Transactions associated with the SLA are monitored and high and low usage periods are predicted based upon a history of transactions. Power to partitionable elements of the computer system may be adjusted during high and low usage periods. In addition, dynamic management of the partitionable elements is provided in response to current demands. Management of the partitionable elements are all made in compliance with the SLA.

Abstract: A power management system (100) for a multiple compute component system (30). The management system (100) enables operational management of individual compute components (40, 50) in two low power states of operation, suspend (158) and hibernate (164). In addition, the management system (100) enables granular management (110, 112) of power consuming accessories (44, 190) within an individual compute component. When a compute component is in the low power state of suspend (158) or hibernate (164), it may be hot-swapped to a different locale. In addition, when a compute component is restored from a low power state of hibernate (164), it may access an alternate image in the system. Accordingly, the power management system (100) allows for five state of operation of an individual component in a multiple compute component system.

Abstract: A power management system (100) for a multiple compute component system (30). The management system (100) enables operational management of individual compute components (40, 50) in two low power states of operation, suspend (158) and hibernate (164). In addition, the management system (100) enables granular management (110, 112) of power consuming accessories (44, 190) within an individual compute component. When a compute component is in the low power state of suspend (158) or hibernate (164), it may be hot-swapped to a different locale. In addition, when a compute component is restored from a low power state of hibernate (164), it may access an alternate image in the system. Accordingly, the power management system (100) allows for five state of operation of an individual component in a multiple compute component system.