The IBM eServer BladeCenter JS20 - IBM Redbooks
The IBM eServer BladeCenter JS20 - IBM Redbooks
The IBM eServer BladeCenter JS20 - IBM Redbooks
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
same Linux distribution in the network installation server that you are planning to<br />
install on the <strong>BladeCenter</strong> <strong>JS20</strong>s.<br />
In some situations, you may want to install AIX on some <strong>BladeCenter</strong> <strong>JS20</strong>s and<br />
Linux on other <strong>BladeCenter</strong> <strong>JS20</strong>s. While it is possible to use a single AIX server<br />
to do this, we recommend that you establish two network install servers, one for<br />
installing AIX and the other for installing your chosen Linux distribution.<br />
Important: A potential problem may arise when you have multiple servers<br />
acting as BOOTP or DHCP servers. Be careful when planning your network so<br />
that they do not interfere with one another.<br />
One approach is to place the <strong>BladeCenter</strong> <strong>JS20</strong>s running AIX and the AIX<br />
network install server on a different VLAN from the <strong>BladeCenter</strong> <strong>JS20</strong>s<br />
running Linux and the Linux install server. If you use this approach, you must<br />
also disable the relay of BOOTP or DHCP requests in your network routers.<br />
To learn how to set up AIX network install servers, see Chapter 7, “Installing AIX<br />
on the <strong>JS20</strong>” on page 123. Or to set up Linux network install servers, see<br />
Chapter 6, “Installing Linux” on page 101.<br />
Setting up network installation<br />
<strong>The</strong> <strong>BladeCenter</strong> <strong>JS20</strong> firmware has the capability to boot an operating system<br />
over a network using the BOOTP. You use this capability to initiate network<br />
installation of the <strong>BladeCenter</strong> <strong>JS20</strong>.<br />
<strong>The</strong> BOOTP protocol is a client-server protocol. When initiating a network<br />
installation on a <strong>BladeCenter</strong> <strong>JS20</strong>, it behaves as a BOOTP client. <strong>The</strong>refore,<br />
you need to set up a BOOTP server to support initiating a network installation.<br />
When you instruct the <strong>BladeCenter</strong> <strong>JS20</strong> firmware to boot over a network using<br />
BOOTP, it sends a request to the BOOTP server. <strong>The</strong> BOOTP server should<br />
generate a response that contains the following information:<br />
► <strong>The</strong> IP address, subnet mask, and default gateway that the <strong>BladeCenter</strong> <strong>JS20</strong><br />
should use for the network interface that sent the BOOTP request<br />
► <strong>The</strong> IP address of a TFTP server that the <strong>BladeCenter</strong> <strong>JS20</strong> should contact,<br />
and the name of the file on that server that the <strong>BladeCenter</strong> <strong>JS20</strong> should<br />
request, to get the operating system installation boot image<br />
<strong>The</strong> BOOTP protocol has been around since the mid1980s. In many<br />
environments, BOOTP has now been replaced by the newer DHCP protocol.<br />
DHCP was designed to interoperate with BOOTP, and most DHCP servers can<br />
serve BOOTP clients.<br />
Chapter 4. Planning considerations 61
Change language