Browse Prior Art Database

(BC) - Methods for Blade/Chassis management function compatibility checking with blade functional requirements.

IP.com Disclosure Number: IPCOM000030694D
Original Publication Date: 2004-Aug-23
Included in the Prior Art Database: 2004-Aug-23
Document File: 2 page(s) / 24K

Publishing Venue

IBM

Abstract

In a Blade/Chassis system, the service processor on blades (and potentially other modules) is powered independent from the controlled blade power. Thus, the service processor and chassis management entity can communicate and perform various functions without the main power up on the blade. The blade power-up is generally directly controlled by the blade service processor but under control of the chassis management entity via various supported commands. Further, the blade (or module) may have functions which require specific functionality in the chassis management to operate correctly within the context of the chassis. For example, a blade which requiring a high amount of power (aggregate capable of exceeding the power capacity of potential power supplies) requires power management function within the chassis management to insure that the blade can be powered up without disruption of the chassis power system. It is foreseen that blades will become more complex and will also be specialized for specific function, where these blades will require specialized management function within the chassis to become either fully functional or insure that they will not have some detrimental impact on other functions within the chassis. This is especially true in the Telco environment where blades have specific functions which require specific management function to work. For example where the voice processing blades need to maintain synchronization to the 8 khz driven PCM voice network. The master 8khz signals are redundant through redundant distribution paths, but which is active for the pertinent blades to used is selected by a component in the chassis management entity. Thus, management components need to be present in the chassis manager to support these specific blades. This disclosure addresses mechanisms to insure that blades and loaded chassis management functions are compatible. If not compatible, the chassis management function may not allow the blade (or other module) to power on.

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

Page 1 of 2

(BC) - Methods for Blade/Chassis management function compatibility checking with blade functional requirements.

Part1:

     Within BladeCenter there currently exists a mechanism to ensure service processor on the blade is compatible with the Management Module (chassis management entity). The Management Module gets this attribute ("service processor") and compares it to a list of supported values. If there is not a match, then the blade is not powered up. This mechasm can be used for simple (near term) compatibility checking. For example, the high powered blades would have a specific new attribute value(s) which would only be recognized by a management entity which included the power management function.

     By using a new value for this attribute for high power demand blades, and adding this value to the supported values in the power management capable Management Module, then these blades will only be accepted if the power management function is present in the Management Module (chassis management entity).

     Thus, the method of chassis management entity to blade compatibility checking comprises the steps of:

The representation of a blade attribute values for compatibility checking


1.


2.


3.


4.

The representation of a new value for the blades requiring power management

function

The representation of compatible blade values in a table in the chassis management

entity

The checking of the blade (compatibility) attribute value against the compatibility

table to proceed with acceptance checking

Part 2:

     Further for more general comp...