Browse Prior Art Database

Method for IP Address Provisioning in the IBM Orchestrator With DHCP Disclosure Number: IPCOM000019970D
Original Publication Date: 2003-Oct-14
Included in the Prior Art Database: 2003-Oct-14
Document File: 1 page(s) / 39K

Publishing Venue



Server provisioning is currently an important and popular idea for allocation/configuration/installation/initialization of server resources. Along with virtualization technology, it is an important cornerstone of DLPAR mechanisms which are driving deployment in the IT industry. Here is a method for dynamic provisioning of IP addresses for servers in an on-demand environment.

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

Page 1 of 1

Method for IP Address Provisioning in the IBM Orchestrator With DHCP

DHCP (Dynamic Host Configuration Protocol) is currently the protocol of choice for IP address allocation for most environments. However, for servers, it is difficult to use DHCP to allocate addresses. This is because servers typically require the same address(es) over a period of time (across reboots, for example) which DHCP cannot guarantee. Using static addresses makes for a very inefficient solution because of its limited network management. It will be desirable to have the flexibility of DHCP's subnet management capabilities while simultaneously honoring a server's requirement for a permanent IP address in the managed subnet.

This will be especially important with the emergence of DLPARs and virtualization to integrate IP address provisioning into the system to support dynamic resource provisioning.

The key idea is the existence of an IP resource provisioner running on the system that manages IP resources across LPARS. At the initial bootup time it requests IP addresses from the DHCP servers on all the individually connected (physically) subnets. Once it is allocated the required addresses it writes it into the ODM (or similar database) marking them as its own and enabling them to be used across reboots. At the same time it administers the DHCP server to indicate that this is an address (es) which the DHCP server should not give out to future clients. The DHCP server puts this address(es) in...