Solaris 10 6/06 Installation Guide: Network-Based Installations

Chapter 7 Preparing to Install From the Network (Overview)

This chapter provides an introduction on how to set up your local area network and systems to install the Solaris software from the network instead of from DVD or CD media. This chapter provides overview information on the following topics.

For information on how to install a client over a wide area network, see Chapter 11, WAN Boot (Overview).

Planning for a Network Installation Introduction

This section provides you with information you need before you can perform an installation from the network. Network installations enable you to install the Solaris software from a system, called an install server, that has access to the Solaris 10 6/06 disc images. You copy the contents of the Solaris 10 6/06 DVD or CD media to the install server's hard disk. Then, you can install the Solaris software from the network by using any of the Solaris installation methods.

Required Servers for Network Installation

To install the Solaris OS from the network, the systems to be installed require the following servers to be present on the network.

Install server – A networked system that contains the Solaris 10 6/06 disc images from which you can install Solaris 10 6/06 software on other systems on the network. You create an install server by copying the images from the following media:
- Solaris DVD
- Solaris Software CDs
  
  After you copy the image from the Solaris Software CDs, you can also copy the image from the Solaris Languages CD as necessary for your installation requirements.
You can enable a single install server to provide disc images for different Solaris releases and for multiple platforms by copying the images on to the install server's hard disk. For example, a single install server could contain the disc images for the SPARC platform and x86 platform.

For details about how to create an install server, refer to one of the following sections.
Boot server – A server system that provides client systems on the same network subnet with the information that they need to boot in order to install the OS. A boot server and install server are typically the same system. However, if the system on which the Solaris 10 6/06 software is to be installed is located in a different subnet than the install server and you are not using DHCP, a boot server is required on that subnet.

A single boot server can provide Solaris 10 6/06 boot software for multiple releases, including the Solaris 10 6/06 boot software for different platforms. For example, a SPARC boot server can provide the Solaris 9 and Solaris 10 6/06 boot software for SPARC based systems. The same SPARC boot server can also provide the Solaris 10 6/06 boot software for x86 based systems.

Note –
When using DHCP, you do not need to create a separate boot server. For more information, see Preconfiguring System Configuration Information With the DHCP Service (Tasks).

For details about how to create a boot server, refer to one of the following sections:
- Creating a Boot Server on a Subnet With a DVD Image
- Creating a Boot Server on a Subnet With a CD Image
(Optional) DHCP server – A server that uses the Dynamic Host Configuration Protocol (DHCP) to provide the network parameters that are necessary for installation. You can configure a DHCP server to configure and install specific clients, all clients on a specific network, or an entire class of clients. When using DHCP, you do not need to create a separate boot server.

After you have created the install server, you add clients to the network with the add_install_client command and the -d option. The -d option enables you to set up client systems for Solaris installation from the network by using DHCP.

For information on DHCP options for installation parameters, see Preconfiguring System Configuration Information With the DHCP Service (Tasks).
(Optional) Name server – A system that manages a distributed network database, such as DNS, NIS, NIS+, or LDAP, that contains information about systems on the network.

For details about how to create a name server, refer to System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP).

Note –
The install server and name server can be the same or different systems.

Figure 7–1 illustrates the servers that are typically used for network installation. Note that this sample network does not include a DHCP server.

Figure 7–1 Network Installation Servers

This illustration depicts the servers that are typically used
for network installation.

x86: Overview of Booting and Installing Over the Network With PXE

This section provides an overview of the Preboot Execution Environment (PXE).

x86: What is PXE?

PXE network boot is a “direct” network boot. No boot media is required on the client system. With PXE, you can install an x86 based client over the network by using DHCP.

PXE network boot is available only for devices that implement the Intel Preboot Execution Environment specification. To determine if your system supports PXE network boot, see your hardware manufacturer's documentation.

x86: Guidelines for Booting With PXE

To boot over the network by using PXE, you need the following systems.

An install server
A DHCP server
An x86 client that supports PXE

When you are preparing to use PXE to install a client over the network, consider the following issues.

Set up only one DHCP server on the subnet that includes the client system that you want to install. The PXE network boot does not work properly over subnets that include multiple DHCP servers.
Some early versions of PXE firmware have a variety of shortcomings. If you experience difficulty with a particular PXE adapter, obtain firmware upgrade information from the adapter manufacturer's web site. Refer to the elxl(7D) and iprb(7D) man pages for more information.