GB2469690A - A method of assignment of a TCP/IP address to a blade server in which the IP address is based on the number of the blade centre and blade slot. - Google Patents

Abstract

A method for assigning a transmission control protocol/internet protocol address to a blade server when it is newly added to a blade centre. When a new blade server is added, a blade discovery module identifies the configuration data from the new blade server, which comprises a unique number of the blade centre, a unique number of a blade slot and a media access control address for a network interface of the new blade server. This data is then sent to an address assignment module, which then derives an IP address based on the unique blade centre and slot numbers and assigns it to the server.

Description

DYNAMIC HOST CONFIGURATION PROTOCOL AUTOMATION FOR SLOT-

BASED BLADESERVER CONFIGURATION

BACKGROUND OF THE INVENTION

Field of the invention:

The present invention relates to a method for assigning a transmission control protocol/internet protocol address to a blade server when it is newly added to a blade center.

Description of the Related Art:

Transmission Control Protocol/Internet protocol (TCP/IP) addresses are used to route packets between various network locations. TCP/IP is a two-layer program. The higher layer, Transmission Control Protocol, manages the assembly of a message or file into smaller packets that are transmitted over the network and received by a TCP layer that reassembles the packets into the original message. The lower layer, Internet Protocol, handles the address part of each packet so that it gets to the right destination.

Each new component added to the network is assigned a Transmission Control Protocol/Internet protocol address. The assigned Transmission Control Protocol/Internet protocol address is generally randomly assigned from an available pool that has been previously allocated to the assigning organization.

The random nature of this assignment makes the Transmission Control Protocol/Internet protocol address arbitrary. A network engineer or systems operator can not determine a corresponding network component simply by examining the Transmission Control Protocol/Internet protocol address. An address translation table must be consulted in order to determine a network component to which a Transmission Control Protocol/Internet protocol address is assigned.

BRIEF SUMMARY OF THE INVENTION

According to one embodiment of the present invention, a method assigns a transmission control protocol/internet protocol address to a blade server when it is newly added to a blade center. Responsive to identifying that a new blade server is installed into the blade center, a blade discovery module identifies configuration data from the new blade server. The configuration data includes a unique number of the blade center, a unique number of a blade slot for the new blade server, and a media access control address for a network interface of the new blade server. The blade discovery module then communicates the configuration data to an address assignment module. The address assignment module then derives the transmission control protocol/internet protocol address for the new blade server from the number of the blade center and the number of the blade slot for the new blade server so that a subnet address of the transmission control protocol/internet protocol address is the number of the blade center and a host address of the transmission control protocol/internet protocol address is the number of the blade slot for the new blade server. The relation between the media access control address of the new blade server and the derived transmission control protocol/internet protocol address is then stored in the address assignment module, and the transmission control protocol/internet protocol address for the new blade server is assigned to the network interface of the new blade server.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Figure 1 is a pictorial representation of a network of data processing systems in which illustrative embodiments may be implemented; Figure 2 is a block diagram of a data processing system in which illustrative embodiments may be implemented; Figure 3 is blade center configuration according to the prior art; Figure 4 is a blade center configuration according to an illustrative embodiment; Figure 5 is a flowchart of a process for determining and assigning a transmission control protocol/internet protocol address based on configuration data according to an illustrative embodiment; and Figure 6 is a flowchart of a process for integrating an address assignment module with a dynamic host configuration protocol is shown according to an illustrative embodiment.

DETAILED DESCRIPTION OF THE INVENTION

As will be appreciated by one skilled in the art, the present invention may be embodied as a system, method, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.), or an embodiment combining software and hardware aspects that may all generally be referred to herein as a "circuit," "module", or "system." Furthermore, the present invention may take the form of a computer program product embodied in any tangible medium of expression having computer usable program code embodied in the medium.

Any combination of one or more computer usable or computer readable medium(s) may be utilized. The computer-usable or computer-readable medium may be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or propagation medium. More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CDROM), an optical storage device, a transmission media such as those supporting the Internet or an intranet, or a magnetic storage device. Note, that the computer-usable or computer-readable medium could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via, for instance, optical scanning of the paper or other medium, then compiled, interpreted, or otherwise processed in a suitable manner, if necessary, and then stored in a computer memory. In the context of this document, a computer-usable or computer-readable medium may be any medium that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. The computer-usable medium may include a propagated data signal with the computer-usable program code embodied therewith, either in baseband or as part of a carrier wave. The computer usable program code may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc. Computer program code for carrying out operations of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smailtalk, C++, or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer, or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

The present invention is described below with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions.

These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer program instructions may also be stored in a computer-readable medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable medium produce an article of manufacture including instruction means which implement the functionlact specified in the flowchart and/or block diagram block or blocks.

The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart andlor block diagram block or blocks.

With reference now to the figures and in particular with reference to Figures 1-2, exemplary diagrams of data processing environments are provided in which illustrative embodiments may be implemented. It should be appreciated that Figures 1-2 are only exemplary and are not intended to assert or imply any limitation with regard to the environments in which different embodiments may be implemented. Many modifications to the depicted environments may be made.

Figure 1 depicts a pictorial representation of a network of data processing system in which illustrative embodiments may be implemented. Network data processing system 100 is a network of computers in which the illustrative embodiments may be implemented. Network data processing system 100 contains network 102, which is the medium used to provide communications links between various devices and computers connected together within network data processing system 100. Network 102 may include connections, such as wire, wireless communication links, or fiber optic cables.

In the depicted example, server 104 and server 106 connect to network 102 along with storage unit 108. In addition, clients 110, 112, and 114 connect to network 102. Clients 110, 112, and 114 may be, for example, personal computers or network computers. In the depicted example, server 104 provides data, such as boot files, operating system images, and applications to clients 110, 112, and 114. Clients 110, 112, and 114 are clients to server 104 in this example. Network data processing system 100 may include additional servers, clients, and other devices not shown.

Program code located in network data processing system 100 may be stored on a computer recordable storage medium and downloaded to a data processing system or other device for use. For example, program code may be stored on a computer recordable storage medium on server 104 and downloaded to client 110 over network 102 for use on client 110.

In the depicted example, network data processing system 100 is the Internet with network 102 representing a worldwide collection of networks and gateways that use the Transmission Control Protocol/Internet Protocol (transmission control protocol/internet protocol) suite of protocols to communicate with one another. At the heart of the Internet is a backbone of high-speed data communication lines between major nodes or host computers, consisting of thousands of commercial, governmental, educational and other computer systems that route data and messages. Of course, network data processing system 100 also may be implemented as a number of different types of networks, such as for example, an intranet, a local area network (LAN), or a wide area network (WAN). Figure 1 is intended as an example, and not as an architectural limitation for the different illustrative embodiments.

With reference now to Figure 2, a block diagram of a data processing system is shown in which illustrative embodiments may be implemented. Data processing system 200 is an example of a computer, such as server 104 or client 110 in Figure 1, in which computer usable program code or instructions implementing the processes may be located for the illustrative embodiments. In this illustrative example, data processing system 200 includes communications fabric 202, which provides communications between processor unit 204, memory 206, persistent storage 208, communications unit 210, input/output (110) unit 212, and display 214.

Processor unit 204 serves to execute instructions for software that may be loaded into memory 206. Processor unit 204 may be a set of one or more processors or may be a multi-processor core, depending on the particular implementation. Further, processor unit 204 may be implemented using one or more heterogeneous processor systems in which a main processor is present with secondary processors on a single chip. As another illustrative example, processor unit 204 may be a symmetric multi-processor system containing multiple processors of the same type.

Memory 206 and persistent storage 208 are examples of storage devices. A storage device is any piece of hardware that is capable of storing information either on a temporary basis and/or a permanent basis. Memory 206, in these examples, may be, for example, a random access memory or any other suitable volatile or non-volatile storage device. Persistent storage 208 may take various forms depending on the particular implementation. For example, persistent storage 208 may contain one or more components or devices. For example, persistent storage 208 may be a hard drive, a flash memory, a rewritable optical disk, a rewritable magnetic tape, or some combination of the above. The media used by persistent storage 208 also may be removable. For example, a removable hard drive may be used for persistent storage 208.

Communications unit 210, in these examples, provides for communications with other data processing systems or devices. In these examples, communications unit 210 is a network interface card. Communications unit 210 may provide communications through the use of either or both physical and wireless communications links. Communication unit 210 may be connected to network 102 of Figure 1.

Input/output unit 212 allows for input and output of data with other devices that may be connected to data processing system 200. For example, input/output unit 212 may provide a connection for user input through a keyboard and mouse. Further, input/output unit 212 may send output to a printer. Display 214 provides a mechanism to display information to a user.

Instructions for the operating system and applications or programs are located on persistent storage 208. These instructions may be loaded into memory 206 for execution by processor unit 204. The processes of the different embodiments may be performed by processor unit 204 using instructions, which may be located in a memory, such as memory 206. These instructions are referred to as program code, computer usable program code, or computer readable program code that may be read and executed by a processor in processor unit 204.

The program code in the different embodiments may be embodied on different physical or 3 0 tangible computer readable media, such as memory 206 or persistent storage 208.

Program code 216 is located in a functional form on computer readable media 218 that is selectively removable and may be loaded onto or transferred to data processing system 200 for execution by processor unit 204. Program code 216 and computer readable media 218 form computer program product 220 in these examples. In one example, computer readable media 218 may be in a tangible form, such as, for example, an optical or magnetic disc that is inserted or placed into a drive or other device that is part of persistent storage 208 for transfer onto a storage device, such as a hard drive that is part of persistent storage 208. In a tangible form, computer readable media 218 also may take the form of a persistent storage, such as a hard drive, a thumb drive, or a flash memory that is connected to data processing system 200.

The tangible form of computer readable media 218 is also referred to as computer recordable storage media. In some instances, computer recordable media 218 may not be removable.

Alternatively, program code 216 may be transferred to data processing system 200 from computer readable media 218 through a communications link to communications unit 210 and/or through a connection to inputloutput unit 212. The communications link and/or the connection may be physical or wireless in the illustrative examples. The computer readable media also may take the form of non-tangible media, such as communications links or wireless transmissions containing the program code.

In some illustrative embodiments, program code 216 may be downloaded over a network to persistent storage 208 from another device or data processing system for use within data processing system 200. For instance, program code stored in a computer readable storage medium in a server data processing system may be downloaded over a network from the server to data processing system 200. The data processing system providing program code 216 may be a server computer, a client computer, or some other device capable of storing and transmitting program code 216.

The different components illustrated for data processing system 200 are not meant to provide architectural limitations to the manner in which different embodiments may be implemented.

The different illustrative embodiments may be implemented in a data processing system including components in addition to or in place of those illustrated for data processing system 200. Other components shown in Figure 2 can be varied from the illustrative examples shown.

The different embodiments may be implemented using any hardware device or system capable of executing program code. As one example, the data processing system may include inorganic components integrated with organic components and/or may be comprised entirely of organic components excluding a human being. For example, a storage device may be comprised of an organic semiconductor.

As another example, a storage device in data processing system 200 is any hardware apparatus that may store data. Memory 206, persistent storage 208, and computer readable media 218 are examples of storage devices in a tangible form.

In another example, a bus system may be used to implement communications fabric 202 and may be comprised of one or more buses, such as a system bus or an input/output bus. Of course, the bus system may be implemented using any suitable type of architecture that provides for a transfer of data between different components or devices attached to the bus system. Additionally, a communications unit may include one or more devices used to transmit and receive data, such as a modem or a network adapter. Further, a memory may be, for example, memory 206 or a cache such as found in an interface and memory controller hub that may be present in communications fabric 202.

Referring now to Figure 3, a blade center configuration is shown according to the prior art.

Blade center 300 comprises server chassis 302. Server chassis 302 provides the housing, power, and internal blade center network 304 for server blades 306-3 12 and blade controller 314. Server blades 306-3 12 are each data processing systems, such as data processing system of Figure 2. Thus, server chassis 302 provides the housing for a plurality of computing devices. Blade center 300 can be one of server 104 or server 106 of Figure 1.

Blade controller 314 is connected to each of server blades 306-312 via internal blade center network 304. Internal blade center network 304 allows blade controller 314 to obtain the configuration from each of server blades 306-312. Blade controller 314 is also connected to external network 316 via network interface 318. Blade controller 314 stores a unique identifier for blade center 300. This unique identifier is referred to as a blade center number.

Each of server blades 306-3 12 is placed in a unique slot of server chassis 302. Each slot has a unique number or address which is also referred to as a blade number. Each of server blades 306-312 is provided with one of network interfaces 320-326. Each of network interfaces 320-326 is connected to external network 316. External network 316 can be, for example, but not limited to, an Ethernet based network running the transmission control protocol/internet protocol protocol.

Server blades 306-3 12 are usually configured to obtain the transmission control protocol/internet protocol network address for their respective network interfaces 320-326 automatically. For example, the transmission control protocol/internet protocol network address can be obtained via the Dynamic Host Configuration Protocol (dynamic host configuration protocol) which is implemented on dynamic host configuration protocol server 328 connected to external network 316. Dynamic host configuration protocol is a protocol used by networked devices such as server blades 306-3 12 in blade center 300 to automatically obtain the parameters necessary for operation in external network 316.

When one of server blades 306-312 is initially connected into server chassis 302, the associated one of network interfaces 320-326 sends a broadcast message on external network 316. Dynamic host configuration protocol server 328 responds to the broadcast message and provides the associated one of network interfaces 320-326 of the connected server blade with the parameters necessary for networked operations, including the transmission control protocol/internet protocol address. The associated one of network interfaces 320-326 then configures these parameters, with the transmission control protocol/internet protocol address automatically assigned to the associated network interface of the newly connected server blade.

The illustrative embodiments herein provide a system and method for assigning a network address to the network interface of a blade which is based on configuration data such as the blade center identification number and the number of blades within the blade center. A blade center includes a blade discovery module and a dynamic host configuration protocol server including a novel address assignment module. The blade discovery module discovers a new blade installed in a blade center, reads out the configuration data and notifies the address assignment module. The address assignment module determines the transmission control protocol/internet protocol address to be assigned to the blade based on the configuration data and policies and assigns a transmission control protocol/internet protocol address to the newly added blade.

A assigns a transmission control protocol/internet protocol address to a blade server when it is newly added to a blade center. Responsive to identifying that a new blade server is installed into the blade center, a blade discovery module identifies configuration data from the new blade server. The configuration data includes a number of the blade center, a number of a blade slot for the new blade server, and a media access control address for a network interface of the new blade server. The blade discovery module then communicates the configuration data to an address assignment module. The address assignment module then derives the transmission control protocol/internet protocol address for the new blade server from the number of the blade center and the number of the blade slot for the new blade server so that a subnet address of the transmission control protocol/internet protocol address is the number of the blade center and a host address of the transmission control protocol/internet protocol address is the number of the blade slot for the new blade server. The relation between the media access control address of the new blade server and the derived transmission control protocol/internet protocol address is then stored in the address assignment module, and the transmission control protocol/internet protocol address for the new blade server is assigned to the network interface of the new blade server.

Referring now to Figure 4, a blade center configuration is shown according to an illustrative embodiment. Blade center 400 is a blade center such as blade center 300 of Figure 3.

However, blade controller 414 is extended to include blade discovery module 430.

Furthermore, dynamic host configuration protocol server 428 is extended to include address assignment module 432. Blade controller 414 includes network interface 418.

In a server farm having multiple blade centers such as blade center 400, blades 406-412 pertaining to blade center 400 are all assigned an identical subnet address, while blades of different blade centers are assigned different subnet addresses. In one illustrative embodiment, for example, blades 406-412 of blade center 400 are assigned a transmission control protocol/internet protocol address of 1 O.O.x.y where x is the blade center identification number and y is the number of the blade slot within the blade center where this blade is 3 0 installed. The number y indicates the subnet address. This address assignment makes each blade center configuration easier to manage because each blade of one blade center is identified by the same subnet address.

Blade center 400 allows for the dynamic assignment of identical subnet addresses for all blades 406-4 12 installed in blade center 400, while blades of different blade centers are assigned different subnet addresses. Because different blade centers are assigned different subnet addresses, all blade centers within a server farm might be connected to the same external network, such as external network 416.

Blade center 400 allows for automated transmission control protocol/internet protocol address assignment to network interfaces 420-426 of blades 406-412 based on a blade center identification number and the number of the blade slot within the blade center. Blade controller 414 includes blade discovery module 430. Blade discovery module 430 periodically checks if a new blade is installed into server chassis 402. Blade discovery module 430 utilizes internal blade center network 404 to discover new blades. When a new blade is installed in blade center 400, such as one of blades 406-4 12, blade discovery module 430 obtains the configuration data of the newly installed blade. The configuration data includes, but is not limited to, the slot number of server chassis 402 into which the blade is installed, and the unique address of the network interface 104 such as a Media Access Control address (media access control address). Blade discovery module 430 then sends the configuration data to address assignment module 432.

Dynamic host configuration protocol server 428 includes address assignment module 432.

Address assignment module 432 assigns an address to one of network interfaces 420-426 based on the configuration data obtained by blade discovery module 430. Blade discovery module 430 and address assignment module 432 communicate via network external network 416.

In one illustrative embodiment, dynamic host configuration protocol server 428 can be configured with rules for the transmission control protocol/internet protocol network address assignment. For example a range of transmission control protocol/internet protocol addresses can be preconfigured in the dynamic host configuration protocol server and an address from this range is assigned to network interfaces 420-426 of blades 406-412.

In one illustrative embodiment, a method for transmission control protocol/internet protocol address assignment to network interfaces 420-426 of blades 406-412 is a static address configuration. Each of network interfaces 420-426 pertaining to one of blades 406-412 is configured with a unique and static transmission control protocol/internet protocol address.

Referring now to Figure 5, a flowchart of a process for determining and assigning a transmission control protocol/internet protocol address based on configuration data is shown according to an illustrative embodiment. Process 500 is a software process, executing on a software component, such as blade discovery module 430 of Figure 4, in conjunction to address assignment module 432 of Figure 4. Process 500 is a process for automated address assignment to a network interface of a blade within a blade center.

Process 500 begins by checking if a new blade is installed into server chassis (step 502). This check can be performed by a blade discovery module, such as blade discovery module 430 of Figure 4.

Responsive to not identifying that a new blade is connected into the server chassis ("no" at step 504), process 500 returns to step 502. In this manner, process 500 continuously checks for the installation of new blades into the server chassis.

Responsive to identifying that a new blade has been connected into the server chassis ("yes" at step 504), process 500 reads the configuration data of the newly added blade (step 506).

The configuration data includes the unique number of the blade in the blade center, the unique number of the blade center and the media access control address of the network interface of the newly added blade. Responsive to reading the configuration data of the newly added blade, process 500 sends the configuration data to an address assignment module of a dynamic host configuration protocol server (step 508).

Process 500 then determines the transmission control protocol/internet protocol address for the network interface of the newly added blade (step 510). The determination of the transmission control protocol/internet protocol address for the network interface of the newly added blade based on the configuration data is done according to policies which are configured in the address assignment module, such as address assignment module 432 of Figure 4. In one illustrative embodiment, the transmission control protocol/internet protocol address is derived from the unique blade center number (y) and the unique number of the blade within the blade center (x). The transmission control protocol/internet protocol address is configured as 10.0.y.x. This policy assures that all blades have the same subnet address y.

For example if the blade center number is 5 and the blade number is I then the address for this blade is: 10.0.5.1. The transmission control protocol/internet protocol address which is determined in this step is configured in the dynamic host configuration protocol server.

Responsive to determining the transmission control protocol/internet protocol address for the network interface of the newly added blade, process 500 assigns the transmission control protocol/internet protocol address to the network interface of the newly added blade according dynamic host configuration protocol methods (step 512), with the process terminating thereafter.

Referring now to Figure 6, a flowchart of a process for integrating an address assignment module with a dynamic host configuration protocol is shown according to an illustrative embodiment. Process 600 is a software process executing for the integration of the address assignment module with the dynamic host configuration protocol. Process 600 is an illustrative embodiment of assigning the transmission control protocol/internet protocol address to the network interface of the newly added blade according to dynamic host configuration protocol methods such as described in step 512 of Figure 5.

Process 600 begins by receiving the configuration data from a blade discovery module (step 602). The configuration data includes the unique number of the blade in the blade center, the unique number of the blade center, and the media access control address of the network interface of the newly added blade.

Responsive to receiving the configuration data, process 600 stops dynamic host configuration protocol (step 604). Dynamic host configuration protocol must be reconfigured with the address for new blade. One way to reconfigure the dynamic host configuration protocol is to stop dynamic host configuration protocol, change a configuration and then restart the dynamic host configuration protocol.

Responsive to stopping dynamic host configuration protocol, process 600 derives the transmission control protocol/internet protocol address (step 606). The determination of the transmission control protocol/internet protocol address for the network interface of the newly added blade based on the configuration data is done according to policies which are configured in the address assignment module such as address assignment module 432 of Figure 4. In one illustrative embodiment, the transmission control protocol/internet protocol address is derived from the unique blade center number (y) and the unique number of the blade within the blade center (x). The transmission control protocol/internet protocol address is configured as I 0.0.y.x. This policy assures that all blades have the same subnet address y.

For example if the blade center number is 5 and the blade number is 1 then the address for this blade is: 10.0.5.1. The transmission control protocol/internet protocol address which is determined in this step is configured in the dynamic host configuration protocol server. This step 606 corresponds to step 510 of Figure 5.

Responsive to deriving the transmission control protocol/internet protocol address, process 600 creates a new dynamic host configuration protocol configuration file which includes a mapping of the media access control address to the determined transmission control protocol/internet protocol address (step 608). Process 600 then restarts dynamic host configuration protocol (step 610) whereby the changed configuration file with the appropriate address configuration for the new blade is loaded. The, process terminates thereafter.

Dynamic host configuration protocol now has a mapping of the niedia access control address of the newly added blade to the transmission control protocol/internet protocol address. The assignment of the transmission control protocol/internet protocol address to the network interface of the newly added blade is done according to the dynamic host configuration protocol.

The illustrative embodiments herein provide a system and method for assigning a network address to the network interface of a blade which is based on configuration data such as the blade center identification number and the number of the blade within the blade center. A blade center includes a blade discovery module and a dynamic host configuration protocol server including a novel address assignment module. The blade discovery module discovers a new blade installed in a blade center, reads out the configuration data and notifies the address assignment module. The address assignment module determines the transmission control protocol/internet protocol address to be assigned to the blade based on the configuration data and policies and assigns a transmission control protocol/internet protocol address to the newly added blade.

A method assigns a transmission control protocol/internet protocol address to a blade server when it is newly added to a blade center. Responsive to identifying that a new blade server is installed into the blade center, a blade discovery module identifies configuration data from the new blade server. The configuration data includes a number of the blade center, a number of a blade slot for the new blade server, and a media access control address for a network interface of the new blade server. The blade discovery module then communicates the configuration data to an address assignment module. The address assignment module then derives the transmission control protocol/internet protocol address for the new blade server from the number of the blade center and the number of the blade slot for the new blade server so that a subnet address of the transmission control protocol/internet protocol address is the number of the blade center and a host address of the transmission control protocol/internet protocol address is the number of the blade slot for the new blade server. The relation between the media access control address of the new blade server and the derived transmission control protocol/internet protocol address is then stored in the address assignment module, and the transmission control protocol/internet protocol address for the new blade server is assigned to the network interface of the new blade server.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the blocks may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the singular fornis "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and/or comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

The corresponding structures, materials, acts, and equivalents of all means or step plus function elements in the claims below are intended to include any structure, material, or act for performing the function in combination with other claimed elements as specifically claimed. The description of the present invention has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the invention in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the invention. The embodiment was chosen and described in order to best explain the principles of the invention and the practical application, and to enable others of ordinary skill in the art to understand the invention for various embodiments with various modifications as are suited to the particular use contemplated.

The invention can take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment containing both hardware and software elements. In a preferred embodiment, the invention is implemented in software, which includes but is not limited to firmware, resident software, microcode, etc. Furthermore, the invention can take the form of a computer program product accessible from a computer-usable or computer-readable medium providing program code for use by or in connection with a computer or any instruction execution system. For the purposes of this description, a computer-usable or computer readable medium can be any tangible apparatus that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.

3 0 The medium can be an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system (or apparatus or device), or a propagation medium. Examples of a computer-readable medium include a semiconductor or solid state memory, magnetic tape, a removable computer diskette, a random access memory (RAM), a read-only memory (ROM), a rigid magnetic disk, and an optical disk. Current examples of optical disks include compact disk -read only memory (CD-ROM), compact disk -read/write (CD-RJW), and DVD.

A data processing system suitable for storing and/or executing program code will include at least one processor coupled directly or indirectly to memory elements through a system bus.

The memory elements can include local memory employed during actual execution of the program code, bulk storage, and cache memories which provide temporary storage of at least some program code in order to reduce the number of times code must be retrieved from bulk storage during execution.

Inputloutput or I/O devices (including but not limited to keyboards, displays, pointing devices, etc.) can be coupled to the system either directly or through intervening I/O controllers.

Network adapters may also be coupled to the system to enable the data processing system to become coupled to other data processing systems or remote printers or storage devices through intervening private or public networks. Modems, cable modems, and Ethernet cards are just a few of the currently available types of network adapters.

The description of the present invention has been presented for purposes of illustration and description, and is not intended to be exhaustive or limited to the invention in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art. The embodiment was chosen and described in order to best explain the principles of the invention, the practical application, and to enable others of ordinary skill in the art to understand the invention for various embodiments with various modifications as are suited to the particular use contemplated.

Claims (1)

1. CLAIMS1. A method for assigning a transmission control protocol/internet protocol address to a blade server when it is newly added to a blade center, the method comprising the steps of: responsive to identifying that a new blade server is installed into the blade center, identifying configuration data from the new blade server, wherein the identifying is performed by a blade discovery module, and wherein the configuration data includes a unique number of the blade center, a unique number of a blade slot for the new blade server, and a media access control address for a network interface of the new blade server; responsive to identifying the configuration data from the new blade server, communicating the configuration data to an address assignment module; deriving the transmission control protocol/internet protocol address for the new blade server from the number of the blade center and the number of the blade slot for the new blade server, so that a subnet address of the transmission control protocol/internet protocol address is the number of the blade center and a host address of the transmission control protocol/internet protocol address is the number of the blade slot for the new blade server; responsive to deriving the transmission control protocol/internet protocol address for the new blade server, permanently storing a relation between the media access control address of the new blade server and the derived transmission control protocol/internet protocol address in the address assignment module; and assigning the transmission control protocol/internet protocol address for the new blade server to the network interface of the new blade server.