Browse Prior Art Database

Event Notification/Registry between pSeries eServers and Platform Management Consoles Disclosure Number: IPCOM000014408D
Original Publication Date: 2001-Jul-23
Included in the Prior Art Database: 2003-Jun-19
Document File: 2 page(s) / 43K

Publishing Venue



Event Notification/Registry between pSeries eServers and Platform Management Consoles

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 1 of 2

Event Notification/Registry between pSeries eServers and Platform Management


This disclosure discusses possible solutions to a hypothetical pSeries eServer that has functionality known as Logical Partitioning. In the past, a server was a standalone system and the customer installed the Operating System on the system. When some event occurred (error event or informational event), it was logged with the Operating System (or more lately with the on-board Control Service Processor that was a separate processor from the server's processors that ran the Operating System).

In this pSeries eServer, the Logical Partitioning is configured by a new standalone PC (aka platform management console PMC) that connects to the pSeries Control Service Processor. Now, this new connection allows error events or informational events another destination to be sent rather than just the Operating System. With Logical Partitioning, there are more information events occurring (partitions starting and stopping, processors starting and stopping, I/O slots starting and stopping).

The PMC models the pieces of the pSeries eServer as a set of objects. There are processor objects, I/O slot objects, memory objects. These new information events generally indicate some object's state has changed. If there is a lot of interaction at the pSeries eServer, there could be many information events and error events being sent from the CSP to the PMC. This paper discribes how the PMC can send commands to the CSP to regulate the type of events that are reported to that PMC.

There is a command that an PMC sends to register with the CSP that it wants to receive events from the CSP. This command is Set Event Handling Settings and each bit in this command correspond to 1 type of event that can occur in the pSeries eServer.

The current types of events are LPAR State Change events, CEC State Change events, H/W State Change events and an PMC Broadcast event. An PMC can register to receive all of these type of events or can chose a subset of these types to receive by passing a bit-mask in the Set Event Handling Settings command. Once a PMC has registered for an event, the CSP will save any future events of this type and send it up to that PMC. If the PMC doesn't respond to the message, the CSP will retry and send up the events multiple times every 1 minute until some pre-defined limit is met. At that point the CSP will assume the PMC is no longer availa...