The IBM zEnterprise A Unified Resource Manager support for the IBM zEnterprise BladeCenter A Extension (zBX) hardware management and operational controls was established as an extension of the z196 system. System z hardware control design principles of concurrency, security, and automatic configuration were mainstays for the extended and new support for the zBX hardware and controls. This paper describes the hardware integration approach and different aspects of management: change, problem, serviceability, configuration, operations, performance, and business. In addition, included in this paper are details of the zBX firmware, components within the zBX blades, and the automation interfaces used between the hardware management console, Support Element, and the zBX components.

The communication interface between support element applications and applications running on the zSeries system processors is an essential part of the zSeries system design. For example, the interface is used to load firmware during startup, it is used for service actions such as configuring or deconfiguring I/O channels, and for many other functions. It must be fast, reliable, and failsafe. A special hardware interface in the clock chip is used to connect the service infrastructure (support element and cage controller) to the central electronic complex (CEC). Four firmware parties are involved in the communication: support element, cage controller, and two firmware layers running on the processors in the CEC: millicode and i390 code. Starting with the z900, the interface between the support element and cage controller was implemented using the NetMessage protocol, whereas the interface between the cage controller and processors still used the legacy service-word communication protocol from previous IBM S/390 models. This meant that the cage controller had to translate the NetMessage protocol from the support element side to the legacy service-word protocol toward the CEC side. In the z990, the communication interface between the support element and the CEC was generally replaced by the NetMessage protocol. The following paper describes the new design and structure of the support element to CEC communication.