Abstract: A method for configuring hardware within a computing system. The method includes one or more computer processors identifying information respectively associated with a plurality of hardware resources within a portion of a computing system. The method further includes determining whether a set of memory modules of differing performance ratings are operatively coupled to a shared bus fabric. The method further includes responding to determining that the set of memory modules of differing performance ratings is operatively coupled to the shared bus fabric by configuring a subsystem to selectively access respective groups of memory modules within the set of memory modules based on a performance rating corresponding to a respective group of memory modules.

Abstract: Techniques are disclosed for performing dump collection on a computing system. One technique includes detecting an error event on the computing system. After detecting the error event, a subset of hardware registers associated with the error event are determined. One or more hardware units within the computing system to capture data from are determined from a set of rules that specify an association between the one or more hardware units and the subset of hardware registers associated with the error event. Data is captured from each of the one or more hardware units.

Abstract: A method for configuring hardware within a computing system. The method includes one or more computer processors identifying information respectively associated with a plurality of hardware resources within a portion of a computing system. The method further includes determining whether a set of memory modules of differing performance ratings are operatively coupled to a shared bus fabric. The method further includes responding to determining that the set of memory modules of differing performance ratings is operatively coupled to the shared bus fabric by configuring a subsystem to selectively access respective groups of memory modules within the set of memory modules based on a performance rating corresponding to a respective group of memory modules.

Abstract: Techniques are disclosed for performing dump collection on a computing system. One technique includes detecting an error event on the computing system. After detecting the error event, a subset of hardware registers associated with the error event are determined. One or more hardware units within the computing system to capture data from are determined from a set of rules that specify an association between the one or more hardware units and the subset of hardware registers associated with the error event. Data is captured from each of the one or more hardware units.

Abstract: Embodiments of the present invention provide systems and method for improving platform dump collection. The method includes upon receiving a platform dump request for a system, accessing a model of the system hardware and a list of commands for the dump. The method further includes determining whether a constraint exists for the command in the list, identifying which software and hardware locks are required by the constraints, determining whether a hardware and software lock is required by multiple constraints, generating a grouping of the constraints requiring the hardware and software lock, and generating an executable list of commands.

Abstract: An approach for at least one service processor to receive a notification of at least one failure during an initial program load of a server and to identify at least one step failing the initial program load. The at least one service processor determines whether a set of conditions are met to switch the initial program load responsibility from a master processor to a service processor. Furthermore, responsive to the at least one service processor determining that the set of one or more conditions are met to switch initial program load responsibility, the at least one service processor assumes the initial program load responsibility.

Abstract: An approach for at least one service processor to receive a notification of at least one failure during an initial program load of a server and to identify at least one step failing the initial program load. The at least one service processor determines whether a set of conditions are met to switch the initial program load responsibility from a master processor to a service processor. Furthermore, responsive to the at least one service processor determining that the set of one or more conditions are met to switch initial program load responsibility, the at least one service processor assumes the initial program load responsibility.

Abstract: Embodiments of the present invention provide systems and method for improving platform dump collection. The method includes upon receiving a platform dump request for a system, accessing a model of the system hardware and a list of commands for the dump. The method further includes determining whether a constraint exists for the command in the list, identifying which software and hardware locks are required by the constraints, determining whether a hardware and software lock is required by multiple constraints, generating a grouping of the constraints requiring the hardware and software lock, and generating an executable list of commands.

Abstract: Failover process for switching from a “failing” blade server to a “replacing” blade server. This process includes the following steps: (i) booting a replacing blade server to a set of operating system(s) including a first operating system; and (ii) subsequent to the booting of the replacing blade server, sending command data to the replacing blade server. The command data includes a command for the replacing blade server to configure itself to replace the failing blade server.

Abstract: Failover process for switching from a “failing” blade server to a “replacing” blade server. This process includes the following steps: (i) booting a replacing blade server to a set of operating system(s) including a first operating system; and (ii) subsequent to the booting of the replacing blade server, sending command data to the replacing blade server. The command data includes a command for the replacing blade server to configure itself to replace the failing blade server.

Abstract: Failover process for switching from a “failing” blade server to a “replacing” blade server. This process includes the following steps: (i) booting a replacing blade server to a set of operating system(s) including a first operating system; and (ii) subsequent to the booting of the replacing blade server, sending command data to the replacing blade server. The command data includes a command for the replacing blade server to configure itself to replace the failing blade server.

Abstract: Failover process for switching from a “failing” blade server to a “replacing” blade server. This process includes the following steps: (i) booting a replacing blade server to a set of operating system(s) including a first operating system; and (ii) subsequent to the booting of the replacing blade server, sending command data to the replacing blade server. The command data includes a command for the replacing blade server to configure itself to replace the failing blade server.