Solaris 10 5/09 Installation Guide: Network-Based Installations

Part II Installing Over a Local Area Network

This part describes how to install a system that is on your local area network (LAN).

Chapter 4 Installing 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 10, WAN Boot (Overview).

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 current Solaris release disc images. You copy the contents of the current Solaris release 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 current Solaris release disc images from which you can install current Solaris release 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 CDs 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.
- To Create an Install Server With SPARC or x86 DVD Media
- SPARC: To Create an Install Server With SPARC or x86 CD Media
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 current Solaris release 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 current Solaris release boot software for multiple releases, including the current Solaris release boot software for different platforms. For example, a SPARC boot server can provide the Solaris 9 and current Solaris release boot software for SPARC based systems. The same SPARC boot server can also provide the current Solaris release 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 4–1 illustrates the servers that are typically used for network installation. Note that this sample network does not include a DHCP server.

Figure 4–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.

Chapter 5 Installing From the Network With DVD Media (Tasks)

This chapter describes how to use DVD media to set up your network and systems to install the Solaris software from the network. Network installations enable you to install the Solaris software from a system that has access to the current Solaris release disc images, called an install server, to other systems on the network. You copy the contents of the current Solaris release DVD 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.

This chapter covers the following topics:

Note –

Starting with the Solaris 10 11/06 release, you have the option during an initial installation to change the network security settings so that all network services, except Secure Shell, are disabled or restricted to respond to local requests only. This security option is available only during an initial installation, not during an upgrade. An upgrade maintains any previously set services. If necessary, you can restrict network services after an upgrade by using the netservices command. See Planning Network Security in Solaris 10 5/09 Installation Guide: Planning for Installation and Upgrade.

The network services can be enabled after installation by using the netservices open command or by enabling individual services by using SMF commands. See Revising Security Settings After Installation in Solaris 10 5/09 Installation Guide: Planning for Installation and Upgrade.
Starting with the Solaris 10 10/08 release, the structure of the Solaris DVD and Solaris Software - 1 CD has changed for the SPARC platform. Slice 0 is no longer at the top of the directory structure. Therefore, the structure of the x86 and SPARC DVDs and Solaris Software - 1 CD are the same. This change in structure makes setting up an install server easier if you have a mix of platforms, such as a SPARC install server and x86 media.

Task Map: Installing From the Network With DVD Media

Table 5–1 Task Map: Setting Up an Install Server With DVD Media


Task	Description	For Instructions
(x86 only): Verify that your system supports PXE.	If you want to install an x86 based system over the network, confirm that your machine can use PXE to boot without local boot media. If your x86 based system does not support PXE, you must boot the system from a local DVD or CD.	Check your hardware manufacturer's documentation or the system BIOS.
Choose an installation method.	The Solaris OS provides several methods for installation or upgrade. Choose the installation method that is most appropriate for your environment.	Choosing a Solaris Installation Method in Solaris 10 5/09 Installation Guide: Planning for Installation and Upgrade
Gather information about your system.	Use the checklist and complete the worksheet to collect all of the information that you need to install or upgrade.	Chapter 5, Gathering Information Before Installation or Upgrade (Planning), in Solaris 10 5/09 Installation Guide: Planning for Installation and Upgrade
(Optional) Preconfigure system information.	You can preconfigure system information to avoid being prompted for the information during the installation or upgrade.	Chapter 2, Preconfiguring System Configuration Information (Tasks)
Create an install server.	Use the setup_install_server(1M) command to copy the Solaris DVD to the install server's hard disk.	Creating an Install Server With DVD Media
(Optional) Create boot servers.	If you want to install systems from the network that are not on the same subnet as the install server, you must create a boot server on the subnet to boot the systems. Use the `setup_install_server` command with the `-b` option to set up a boot server. If you are using Dynamic Host Configuration Protocol (DHCP), a boot server is not necessary.	Creating a Boot Server on a Subnet With a DVD Image
Add systems to be installed from the network.	Use the `add_install_client` command to set up each system that you want to install from the network. Each system that you want to install needs to find the install server, the boot server if required, and configuration information on the network.	Adding Systems to Be Installed From the Network With a DVD Image
(Optional) Configure the DHCP server.	If you want to use DHCP to provide system configuration and installation parameters, configure the DHCP server, then create the appropriate options and macros for your installation. Note – If you want to install an x86 based system from the network with PXE, you must configure a DHCP server.	Chapter 13, Planning for DHCP Service (Tasks), in System Administration Guide: IP Services Preconfiguring System Configuration Information With the DHCP Service (Tasks)
Install the system over the network.	Begin the installation by booting the system from the network.	Installing the System From the Network With a DVD Image

Creating an Install Server With DVD Media

The install server contains the installation image needed to install systems from the network. You must create an install server to install the Solaris software on a system from the network. You do not always need to set up a boot server.

If you are using DHCP to set installation parameters or your install server and client are on the same subnet, you do not need a boot server.
If your install server and your client are not on the same subnet and you are not using DHCP, you must create separate boot servers for each subnet. You could create an install server for each subnet. However, install servers require more disk space.

To Create an Install Server With SPARC or x86 DVD Media

Note –

This procedure assumes that the system is running the Volume Manager. If you are not using the Volume Manager to manage media, refer to System Administration Guide: Devices and File Systems.

On the system that is to become the install server, become superuser or assume an equivalent role.

The system must include a DVD-ROM drive and be part of the site's network and naming service. If you use a naming service, the system must already be in a service, such as NIS, NIS+, DNS, or LDAP. If you do not use a naming service, you must distribute information about this system by following your site's policies.

Insert the Solaris DVD in the system's drive.

Create a directory to contain the DVD image.
# mkdir -p install_dir_path
install_dir_path specifies the directory where the DVD image is to be copied.

Change to the Tools directory on the mounted disc.
# cd /cdrom/cdrom0/Solaris_10/Tools

Copy the DVD image in the drive to the install server's hard disk.
# ./setup_install_server install_dir_path
install_dir_path

Specifies the directory where the DVD image is to be copied

Note –
The setup_install_server command indicates whether you have enough disk space available for the Solaris Software disc images. To determine available disk space, use the df -kl command.

Decide if you need to make the install server available for mounting.
- If the install server is on the same subnet as the system to be installed or you are using DHCP, you do not need to create a boot server. Proceed to Step 7.
- If the install server is not on the same subnet as the system to be installed and you are not using DHCP, complete the following steps.
  1. Verify that the path to the install server's image is shared appropriately.
    # share | grep install_dir_path
    install_dir_path
    
    Specifies the path to the installation image where the DVD image was copied
    - If the path to the install server's directory is displayed and anon=0 is displayed in the options, proceed to Step 7.
    - If the path to the install server's directory is not displayed or you do not have anon=0 in the options, continue.
  2. Make the install server available to the boot server.
    
    Using the share command, add this entry to the /etc/dfs/dfstab file.
    share -F nfs -o ro,anon=0 -d "install server directory" install_dir_path
  3. Verify that the nfsd daemon is running.
    - If the install server is running the current Solaris release, or compatible version, type the following command.
      # svcs -l svc:/network/nfs/server:default
      If the nfsd daemon is online, continue to Step d. If the nfsd daemon is not online, start it.
      # svcadm enable svc:/network/nfs/server
    - If the install server is running the Solaris 9 OS, or compatible version, type the following command.
      # ps -ef | grep nfsd
      If the nfsd daemon is running, continue to Step d. If the nfsd daemon is not running, start it.
      # /etc/init.d/nfs.server start
  4. Share the install server.
    # shareall

Change directories to root (/).
# cd /

Eject the Solaris DVD.

(Optional) Patch the files that are located in the miniroot on the net install image that was created by setup_install_server.

Patching a file might be necessary if a boot image has problems. For step-by-step procedures, see Chapter 7, Patching the Miniroot Image (Tasks).

Decide if you need to create a boot server.
- If you are using DHCP or the install server is on the same subnet as the system to be installed, you do not need to create a boot server. Proceed to Adding Systems to Be Installed From the Network With a DVD Image.
- If you are not using DHCP and the install server and the client are on a different subnet, you must create a boot server. Proceed to Creating a Boot Server on a Subnet With a DVD Image.

Example 5–1 SPARC: Creating an Install Server With a DVD

The following example illustrates how to create an install server by copying the Solaris DVD to the install server's /export/home/dvd directory. This example assumes that the install server is running the current Solaris release.

# mkdir -p /export/home/dvd
# cd /cdrom/cdrom0/Solaris_10/Tools
# ./setup_install_server /export/home/dvd

If you need a separate boot server, make the install server available to the boot server.

Using the share command, add this entry to the /etc/dfs/dfstab file.

share -F nfs -o ro,anon=0 -d "install server directory" /export/home/dvdsparc

Check if the nfsd daemon is online. If the nfsd daemon is not online, start it and share it.

# svcs -l svc:/network/nfs/server:default
# svcadm enable svc:/network/nfs/server
# shareall 
# cd /

Continuing the Installation

After you set up the install server, you must add the client as an installation client. For information about how to add client systems to install over the network, see To Add Systems to Be Installed From the Network With add_install_client (DVD).

If you are not using DHCP, and your client system is on a different subnet than your install server, you must create a boot server. For more information, see Creating a Boot Server on a Subnet With a DVD Image.

Creating a Boot Server on a Subnet With a DVD Image

You must create an install server to install the Solaris software on a system from the network. You do not always need to set up a boot server. A boot server contains enough of the boot software to boot systems from the network, and then the install server completes the installation of the Solaris software.

If you are using DHCP to set installation parameters or your install server or client is on the same subnet as the install server, you do not need a boot server. Proceed to Adding Systems to Be Installed From the Network With a DVD Image.
If your install server and your client are not on the same subnet and you are not using DHCP, you must create separate boot servers for each subnet. You could create an install server for each subnet; however, install servers require more disk space.

To Create a Boot Server on a Subnet With a DVD Image

On the system you intend to make the boot server for the subnet, log in and become superuser or assume an equivalent role.

The system must have access to a remote current Solaris release disc image, which is normally the install server. If you use a naming service, the system should also be in a naming service. If you do not use a naming service, you must distribute information about this system by following your site's policies.

Mount the Solaris DVD from the install server.
# mount -F nfs -o ro server_name:path /mnt
server_name:path

Is the install server name and absolute path to the disc image

Create a directory for the boot image.
# mkdir -p boot_dir_path
boot_dir_path

Specifies the directory where the boot software is to be copied

Change to the Tools directory on the Solaris DVD image.
# cd /mnt/Solaris_10/Tools

Copy the boot software to the boot server.
# ./setup_install_server -b boot_dir_path
-b

Specifies to set up the system as a boot server

boot_dir_path

Specifies the directory where the boot software is to be copied

Note –
The setup_install_server command indicates whether you have enough disk space available for the images. To determine available disk space, use the df -kl command.

Change directories to root (/).
# cd /

Unmount the installation image.
# umount /mnt
You are now ready to set up systems to be installed from the network. See Adding Systems to Be Installed From the Network With a DVD Image.

Example 5–2 Creating a Boot Server on a Subnet (DVD)

The following example illustrates how to create a boot server on a subnet. These commands copy the boot software from the Solaris DVD image to /export/home/dvdsparc on the local disk of a boot server named crystal.

# mount -F nfs -o ro crystal:/export/home/dvdsparc /mnt 
# mkdir -p  /export/home/dvdsparc
# cd /mnt/Solaris_10/Tools
# ./setup_install_server -b /export/home/dvdsparc
# cd /
# umount /mnt

Continuing the Installation

After you set up the boot server, you must add the client as an installation client. For information about how to add client systems to install over the network, see Adding Systems to Be Installed From the Network With a DVD Image.

Adding Systems to Be Installed From the Network With a DVD Image

After you create an install server and, if necessary, a boot server, you must set up each system that you want to install from the network. Each system that you want to install needs to find the following:

An install server
A boot server if it is required
The sysidcfg file if you use a sysidcfg file to preconfigure system information
A name server if you use a naming service to preconfigure system information
The profile in the JumpStart directory on the profile server if you are using the custom JumpStart installation method

Use the following add_install_client procedure for setting up install servers and clients. Also, see the example procedures for the following:

If you are using DHCP to set installation parameters for a SPARC client, see Example 5–3.
If your install server and client are on the same subnet, see Example 5–4.
If your install server and your client are not on the same subnet and you are not using DHCP, see Example 5–5.
If you are using DHCP to set installation parameters for x86 clients, see Example 5–6.
If you want to use a specific serial port to display output during the installation of an x86 based system, see Example 5–7.

For more options to use with this command, see the man page, add_install_client(1M).

To Add Systems to Be Installed From the Network With `add_install_client` (DVD)

After you create an install server, you must set up each system that you want to install from the network.

Use the following add_install_client procedure for set up an x86 client to install from the network.

Before You Begin

If you have a boot server, make sure you have shared the install server installation image and started the appropriate services. See “To Create a SPARC Install Server With SPARC or x86 DVD Media” Step 6.

Each system that you want to install needs to find the following items.

Install server
Boot server if it is required
sysidcfg file if you use a sysidcfg file to preconfigure system information
Name server if you use a naming service to preconfigure system information
The profile in the JumpStart directory on the profile server if you are using the custom JumpStart installation method

On the install server or boot server, become superuser or assume an equivalent role.

If you use the NIS, NIS+, DNS, or LDAP naming service, verify that the following information about the system to be installed has been added to the naming service.
- Host name
- IP address
- Ethernet address
For more information on naming services, see System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP).

Add the client to the install server's /etc/ethers file.
1. On the client, find the ethers address. The /etc/ethers map is taken from the local file.
  # ifconfig -a grep ether ether 8:0:20:b3:39:1d
2. On the install server, open the /etc/ethers file in an editor. Add the address to the list.

Change to the Tools directory on the Solaris DVD image:
# cd /install_dir_path/Solaris_10/Tools
install_dir_path

Specifies the path to the Tools directory

Set up the client system so it can be installed from the network.

# ./add_install_client -d -s install_server:install_dir_path \
-c jumpstart_server:jumpstart_dir_path  -p sysid_server:path \
-t boot_image_path -b "boot-property=value" \
-e ethernet_address client_name platform_group

-d

Specifies that the client is to use DHCP to obtain the network install parameters. If you use the -d only, the add_install_client command sets up the installation information for client systems of the same class, for example, all SPARC client machines. To set up the installation information for a specific client, use the -d with the -e option.

For x86 clients, use this option to boot the systems from the network by using PXE network boot. The output of this option lists the DHCP options you need to create on the DHCP server.

For more information about class-specific installations by using DHCP, see Creating DHCP Options and Macros for Solaris Installation Parameters.

-s install_server:install_dir_path

Specifies the name and path to the install server.

install_server is the host name of the install server.
install_dir_path is the absolute path to the Solaris DVD image.

-c jumpstart_server:jumpstart_dir_path

Specifies a JumpStart directory for custom JumpStart installations. jumpstart_server is the host name of the server on which the JumpStart directory is located. jumpstart_dir_path is the absolute path to the JumpStart directory.

-p sysid_server:path

Specifies the path to the sysidcfg file for preconfiguring system information. sysid_server is either a valid host name or an IP address for the server that contains the file. path is the absolute path to the directory containing the sysidcfg file.

-t boot_image_path

Specifies the path to an alternate boot image if you want to use a boot image other than the one in the Tools directory on the current Solaris release net installation image, CD, or DVD.

-b “boot-property=value”

x86 based systems only: Enables you to set the value of a boot property variable that you want to use to boot the client from the network. The -b option must be used with the -e option.

See the eeprom(1M) man page for descriptions of boot properties.

-e ethernet_address

Specifies the Ethernet address of the client that you want to install. This option enables you to set up the installation information to use for a specific client, including a boot file for that client.

The nbp. prefix is not used in boot file names. For example, if you specify -e 00:07:e9:04:4a:bf for an x86 based client, the command creates the boot file 010007E9044ABF.i86pc in the /tftpboot directory. However, the current Solaris release supports the use of legacy boot files with the nbp. prefix.

For more information about client-specific installations by using DHCP, see Creating DHCP Options and Macros for Solaris Installation Parameters.

client_name

Is the name of the system to be installed from the network. This name is not the host name of the install server.

platform_group

Is the platform group of the system to be installed. For more information, see Platform Names and Groups in Solaris 10 5/09 Installation Guide: Planning for Installation and Upgrade.

Example 5–3 SPARC: Adding a SPARC Install Client on a SPARC Install Server When Using DHCP (DVD)

The following example illustrates how to add an install client when you are using DHCP to set installation parameters on the network. The install client is named basil, which is an Ultra^TM 5 system. The file system /export/home/dvdsparc/Solaris_10/Tools contains the add_install_client command.

For more information on how to use DHCP to set installation parameters for network installations, see Preconfiguring System Configuration Information With the DHCP Service (Tasks).

sparc_install_server# cd /export/home/dvdsparc/Solaris_10/Tools
sparc_install_server# ./add_install_client -d basil sun4u

Example 5–4 Adding an Install Client That Is On the Same Subnet As Its Server (DVD)

The following example illustrates how to add an install client that is on the same subnet as the install server. The install client is named basil, which is an Ultra 5 system. The file system /export/home/dvdsparc/ contains the add_install_client command.

install_server# cd /export/home/dvdsparc/Solaris_10/Tools
install_server# ./add_install_client basil sun4u

Example 5–5 Adding an Install Client to a Boot Server (DVD)

The following example illustrates how to add an install client to a boot server. The install client is named rose, which is an Ultra 5 system. Run the command on the boot server. The -s option is used to specify an install server that is named rosemary, which contains a Solaris Operating System for SPARC Platforms DVD image in /export/home/dvdsparc.

boot_server# cd /export/home/dvdsparc/Solaris_10/Tools
boot_server# ./add_install_client -s rosemary:/export/home/dvdsparc rose sun4u

Example 5–6 x86: Adding a Single x86 Install Client on an x86 Install Server When Using DHCP (DVD)

The following example illustrates how to add an x86 install client to an install server when you are using DHCP to set installation parameters on the network.

The -d option is used to specify that clients are to use the DHCP protocol for configuration. If you plan to use PXE network boot, you must use the DHCP protocol.
The -e option indicates that this installation will only occur on the client with the Ethernet address 00:07:e9:04:4a:bf .
The -s option is used to specify that the clients are to be installed from the install server that is named rosemary.

This server contains a Solaris Operating System for x86 Platforms DVD image in /export/home/dvdx86.

x86_install_server# cd /export/boot/dvdx86/Solaris_10/Tools
x86_install_server# ./add_install_client -d -e 00:07:e9:04:4a:bf \ 
-s rosemary:/export/home/dvdx86 i86pc

The previous commands set up the client with the Ethernet address 00:07:e9:04:4a:bf as an installation client. The boot file 010007E9044ABF.i86pc is created on the installation server. In previous releases, this boot file was named nbp.010007E9044ABF.i86pc.

For more information on how to use DHCP to set installation parameters for network installations, see Preconfiguring System Configuration Information With the DHCP Service (Tasks).

Example 5–7 x86: Specifying a Serial Console to Use During a Network Installation (DVD)

The following example illustrates how to add an x86 install client to an install server and specify a serial console to use during the installation. This example sets up the install client in the following manner.

The -d option indicates that the client is set up to use DHCP to set installation parameters.
The -e option indicates that this installation will occur only on the client with the Ethernet address 00:07:e9:04:4a:bf.
The -b option instructs the installation program to use the serial port ttya as an input and an output device.

Use this set of commands to add the client.

install server# cd /export/boot/dvdx86/Solaris_10/Tools
install server# ./add_install_client -d -e "00:07:e9:04:4a:bf" \
-b "console=ttya" i86pc

For a complete description of the boot property variables and values you can use with the -b option, see the eeprom(1M) man page.

Continuing the Installation

If you are using a DHCP server to install the x86 based client over the network, configure the DHCP server and create the options and macros that are listed in the output of the add_install_client -d command. For instructions about how to configure a DHCP server to support network installations, see Preconfiguring System Configuration Information With the DHCP Service (Tasks).

x86 based systems: If you are not using a DHCP server, you must boot the system from a local Solaris OS DVD or CD.

Installing the System From the Network With a DVD Image

After you add the system as an installation client, you can install the client from the network. This section describes the following tasks.

See SPARC: To Install the Client Over the Network (DVD) for instructions about how to boot and install SPARC based systems over the network.
See x86: To Install the Client Over the Network With GRUB (DVD) for instructions about how to boot and install x86 based systems over the network.

SPARC: To Install the Client Over the Network (DVD)

Before You Begin

This procedure assumes that you have completed the following tasks.

Set up an install server. For instructions about how to create an install server from DVD media, see To Create an Install Server With SPARC or x86 DVD Media.
Set up a boot server or a DHCP server, if necessary. If the system you want to install is on a different subnet than the installation server, you must set up a boot server, or use a DHCP server. For instructions about how to set up a boot server, see Creating a Boot Server on a Subnet With a DVD Image. For instructions about how to set up a DHCP server to support network installations, see Preconfiguring System Configuration Information With the DHCP Service (Tasks).
Gathered or preconfigured the information you need to install. You can perform this task in one or more of the following ways.
- Gather the information in Checklist for Installation in Solaris 10 5/09 Installation Guide: Planning for Installation and Upgrade.
  
  Note –
  If you have a system that contains non-global zones, Solaris Live Upgrade is the recommended upgrade program or program to add patches. Other upgrade programs might require extensive upgrade time, because the time required to complete the upgrade increases linearly with the number of installed non-global zones.
  
  For information about upgrading with Solaris Live Upgrade, see Part I, Upgrading With Solaris Live Upgrade, in Solaris 10 5/09 Installation Guide: Solaris Live Upgrade and Upgrade Planning.
- Create a sysidcfg file if you use a sysidcfg file to preconfigure system information. For information about how to create a sysidcfg file, see Preconfiguring With the sysidcfg File.
- Set up a name server if you use a naming service to preconfigure system information. For information about how to preconfigure information with a naming service, see Preconfiguring With the Naming Service.
- Create a profile in the JumpStart directory on the profile server if you are using the custom JumpStart installation method. For information about how to set up a custom JumpStart installation, see Chapter 3, Preparing Custom JumpStart Installations (Tasks), in Solaris 10 5/09 Installation Guide: Custom JumpStart and Advanced Installations.

Turn on the client system.

If the system is currently running, bring the system to run level 0.

The ok prompt is displayed.

Boot the system from the network.
- To install with the Solaris interactive installation GUI, type the following command.
  ok boot net
- To install with the Solaris interactive text installer in a desktop session, type the following command.
  ok boot net - text
- To install with the Solaris interactive text installer in a console session, type the following command.
  ok boot net - nowin
The system boots from the network.

If you are prompted, answer the system configuration questions.
- If you preconfigured all of the system information, the installation program does not prompt you to enter any configuration information. See Chapter 2, Preconfiguring System Configuration Information (Tasks) for more information.
- If you did not preconfigure all the system information, use the Checklist for Installation in Solaris 10 5/09 Installation Guide: Planning for Installation and Upgrade to help you answer the configuration questions.
  
  Note –
  If the keyboard is self-identifying, the keyboard layout automatically configures during installation. If the keyboard is not self-identifying, you can select from a list of supported keyboard layouts during installation.
  
  PS/2 keyboards are not self-identifying. You will be asked to select the keyboard layout during the installation.
  
  For further information, see keyboard Keyword.
If you are using the GUI, after you confirm the system configuration information, the Welcome to Solaris panel appears.

If you are prompted, answer any additional questions to complete your installation.
- If you preconfigured all of the installation options, the installation program does not prompt you to enter any installation information. See Chapter 2, Preconfiguring System Configuration Information (Tasks) for more information.
- If you did not preconfigure all the installation options, use the Checklist for Installation in Solaris 10 5/09 Installation Guide: Planning for Installation and Upgrade to help you answer the installation questions.

x86: To Install the Client Over the Network With GRUB (DVD)

The Solaris installation programs for x86 based systems use the GRUB boot loader. This procedure describes how to install an x86 based system over the network with the GRUB boot loader. For overview information about the GRUB boot loader, see Chapter 7, SPARC and x86 Based Booting (Overview and Planning), in Solaris 10 5/09 Installation Guide: Planning for Installation and Upgrade.

To install the system over the network, you must instruct the client system to boot over the network. Enable network boot on the client system by using the BIOS setup program in the system BIOS, the network adapter BIOS, or both. On some systems, you must also adjust the boot device priority list so that network boot is attempted before booting from other devices. See the manufacturer's documentation for each setup program, or watch for setup program instructions during boot.

Before You Begin

This procedure assumes that you have completed the following tasks.

Set up an install server. For instructions about how to create an install server from DVD media, see To Create an Install Server With SPARC or x86 DVD Media.
Set up a boot server or a DHCP server, if necessary. If the system you want to install is on a different subnet than the installation server, you must set up a boot server, or use a DHCP server. For instructions about how to set up a boot server, see Creating a Boot Server on a Subnet With a DVD Image. For instructions about how to set up a DHCP server to support network installations, see Preconfiguring System Configuration Information With the DHCP Service (Tasks).
Gathered or preconfigured the information you need to install. You can perform this task in one or more of the following ways.
- Gather the information in Checklist for Installation in Solaris 10 5/09 Installation Guide: Planning for Installation and Upgrade.
  
  Note –
  If you have a system that contains non-global zones, Solaris Live Upgrade is the recommended upgrade program or program to add patches. Other upgrade programs might require extensive upgrade time, because the time required to complete the upgrade increases linearly with the number of installed non-global zones.
  
  For information about upgrading with Solaris Live Upgrade, see Part I, Upgrading With Solaris Live Upgrade, in Solaris 10 5/09 Installation Guide: Solaris Live Upgrade and Upgrade Planning.
- Create a sysidcfg file if you use a sysidcfg file to preconfigure system information. For information about how to create a sysidcfg file, see Preconfiguring With the sysidcfg File.
- Set up a name server if you use a naming service to preconfigure system information. For information about how to preconfigure information with a naming service, see Preconfiguring With the Naming Service.
- Create a profile in the JumpStart directory on the profile server if you are using the custom JumpStart installation method. For information about how to set up a custom JumpStart installation, see Chapter 3, Preparing Custom JumpStart Installations (Tasks), in Solaris 10 5/09 Installation Guide: Custom JumpStart and Advanced Installations.

This procedure also assumes that your system can boot from the network.

Turn on the system.

Type the appropriate keystroke combination to enter the system BIOS.

Some PXE-capable network adapters have a feature that enables PXE boot if you type a particular keystroke in response to a brief boot-time prompt.

In the system BIOS, instruct the system to boot from the network.

See your hardware documentation for information about how to set the boot priority in the BIOS.

Exit the BIOS.

The system boots from the network. The GRUB menu is displayed.

Note –

The GRUB menu that is displayed on your system might vary from the following sample, depending on the configuration of your network installation server.

GNU GRUB version 0.95 (631K lower / 2095488K upper memory)
+-----------------------------------------------------------------------------------------------------------+
| Solaris 10 5/09 /cdrom0                                                           
|                                                                                                           |
|                                                                                                           |
+-----------------------------------------------------------------------------------------------------------+
Use the ^ and v keys to select which entry is highlighted.
Press enter to boot the selected OS, 'e' to edit the
commands before booting, or 'c' for a command-line.

Select the appropriate installation option.
- To install the Solaris OS from the network, select the appropriate Solaris entry on the menu, then press Enter.
  
  Select this entry if you want to install from the network installation server you set up in To Create an Install Server With SPARC or x86 DVD Media.
- To install the Solaris OS from the network with specific boot arguments, follow these steps.
  
  You might need to set specific boot arguments if you want to modify the device configuration during the installation, and did not set these boot arguments previously with the add_install_client command as described in To Add Systems to Be Installed From the Network With add_install_client (DVD).
  1. On the GRUB menu, select the installation option you want to edit, then press e.
    
    Boot commands that are similar to the following text are displayed in the GRUB menu.
    kernel /I86pc.Solaris_10/multiboot kernel/unix \ -B install_media=192.168.2.1:/export/cdrom0/boot \ module /platform/i86pc/boot_archive
  2. Use the arrow keys to select the boot entry that you want to edit, then press e.
    
    The boot command that you want to edit is displayed in the GRUB edit window.
  3. Edit the command by typing the boot arguments or options you want to use.
    
    The command syntax for the Grub edit menu is as follows.
    grub edit>kernel /image_directory/multiboot kernel/unix/ \ install [url|ask] -B options install_media=media_type
    For information about boot arguments and command syntax, see Table 9–1.
  4. To accept your edits and return to the GRUB menu, press Enter.
    
    Note –
    To cancel your edits and return to the GRUB menu, press Escape.
    
    The GRUB menu is displayed. The edits you made to the boot command are displayed.
  5. To begin the installation, type b in the GRUB menu.
The Solaris installation program checks the default boot disk for the requirements to install or upgrade the system. If the Solaris installation cannot detect the system configuration, the program prompts you for any missing information.

When the check is completed, the installation selection screen is displayed.

Select an installation type.

The installation selection screen displays the following options.

      Select the type of installation you want to perform:

         1 Solaris Interactive
         2 Custom JumpStart
         3 Solaris Interactive Text (Desktop session)
         4 Solaris Interactive Text (Console session)
         5 Apply driver updates
         6 Single user shell

         Enter the number of your choice followed by the <ENTER> key.
         Alternatively, enter custom boot arguments directly.

         If you wait 30 seconds without typing anything,
         an interactive installation will be started.

To install the Solaris OS, choose from the following options.
- To install with the Solaris interactive installation GUI, type 1, then press Enter.
- To install with the interactive text installer in a desktop session, type 3, then press Enter.
  
  Select this installation type to override the default GUI installer and run the text installer.
- To install with the interactive text installer in a console session, type 4, then press Enter.
  
  Select this installation type to override the default GUI installer and run the text installer.
If you want to perform an unattended custom JumpStart installation (option 2), see Solaris 10 5/09 Installation Guide: Custom JumpStart and Advanced Installations.

For detailed information about the Solaris installation GUI and text installer, see System Requirements and Recommendations in Solaris 10 5/09 Installation Guide: Planning for Installation and Upgrade.

The system configures the devices and interfaces, and searches for configuration files.The installation program begins. Go to Step 7 to continue the installation.

To perform system administration tasks before your installation, choose from the following options.
- To update drivers or install an install time update (ITU), insert the update media, type 5, then press Enter.
  
  You might need to update drivers or install an ITU to enable the Solaris OS to run on your system. Follow the instructions for your driver update or ITU to install the update.
- To perform system administration tasks, type 6, then press Enter.
  
  You might want to launch a single user shell if you need to perform any system administration tasks on your system before you install. For information about system administration tasks you can perform prior to installation, see System Administration Guide: Basic Administration.
After you perform these system administration tasks, the previous list of options is displayed. Select the appropriate option to continue the installation.

If you are prompted, answer the system configuration questions.
- If you preconfigured all of the system information, the installation program does not prompt you to enter any configuration information. See Chapter 2, Preconfiguring System Configuration Information (Tasks) for more information.
- If you did not preconfigure all the system information, use the Checklist for Installation in Solaris 10 5/09 Installation Guide: Planning for Installation and Upgrade to help you answer the configuration questions.
  
  Note –
  If the keyboard is self-identifying, the keyboard layout automatically configures during installation. If the keyboard is not self-identifying, you can select from a list of supported keyboard layouts during installation.
  
  For further information, see keyboard Keyword.
  
  Note –
  During installation, you can choose the default NFSv4 domain name. Or, you can specify a custom NFSv4 domain name. For further information, see nfs4_domain Keyword.
If you are using the installation GUI, after you confirm the system configuration information, the Welcome to Solaris panel appears.

If you are prompted, answer any additional questions to complete your installation.
- If you preconfigured all of the installation options, the installation program does not prompt you to enter any installation information. See Chapter 2, Preconfiguring System Configuration Information (Tasks) for more information.
- If you did not preconfigure all the installation options, use the Checklist for Installation in Solaris 10 5/09 Installation Guide: Planning for Installation and Upgrade to help you answer the installation questions.

After the system boots and installs over the network, instruct the system to boot from the disk drive on subsequent boots.

Note –
When you boot the system after the installation, a GRUB menu lists the operating systems that are installed, including the newly-installed Solaris OS. Select which operating system you want to boot. The default selection loads if you do not make another selection.

Next Steps

If you install multiple operating systems on your machine, you need to instruct the GRUB boot loader to recognize these operating systems in order to boot. For more information, see Modifying Boot Behavior on x86 Based Systems in System Administration Guide: Basic Administration.

Chapter 6 Installing From the Network With CD Media (Tasks)

This chapter describes how to use CD media to set up your network and systems to install the Solaris software from the network. Network installations enable you to install the Solaris software from a system that has access to the current Solaris release disc images, called an install server, to other systems on the network. You copy the contents of the 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. This chapter covers the following topics:

Note –

Starting with the Solaris 10 11/06 release, you have the option during an initial installation to change the network security settings so that all network services, except Secure Shell, are disabled or restricted to respond to local requests only. This security option is available only during an initial installation, not during an upgrade. An upgrade maintains any previously set services. If necessary, you can restrict network services after an upgrade by using the netservices command. See Planning Network Security in Solaris 10 5/09 Installation Guide: Planning for Installation and Upgrade.

The network services can be enabled after installation by using the netservices open command or by enabling individual services by using SMF commands. See Revising Security Settings After Installation in Solaris 10 5/09 Installation Guide: Planning for Installation and Upgrade.
Starting with the Solaris 10 10/08 release, the structure of the Solaris DVD and Solaris Software - 1 CD has changed for the SPARC platform. Slice 0 is no longer at the top of the directory structure. Therefore the structure of the x86 and SPARC DVDs and Solaris Software - 1 CD are the same. This change in structure makes setting up an install server easier if you have a mix of platforms, such as a SPARC install server and x86 media.

Task Map: Installing From the Network With CD Media

Table 6–1 Task Map: Setting Up an Install Server With CD Media


Task	Description	For Instructions
(x86 only): Verify that your system supports PXE.	If you want to install an x86 based system over the network, confirm that your machine can use PXE to boot without local boot media. If your x86 based system does not support PXE, you must boot the system from a local DVD or CD.	Check your hardware manufacturer's documentation or the system BIOS.
Choose an installation method.	The Solaris OS provides several methods for installation or upgrade. Choose the installation method that is most appropriate for your environment.	Choosing a Solaris Installation Method in Solaris 10 5/09 Installation Guide: Planning for Installation and Upgrade
Gather information about your system.	Use the checklist and complete the worksheet to collect all of the information that you need to install or upgrade.	Chapter 5, Gathering Information Before Installation or Upgrade (Planning), in Solaris 10 5/09 Installation Guide: Planning for Installation and Upgrade
(Optional) Preconfigure system information.	You can preconfigure system information to avoid being prompted for the information during the installation or upgrade.	Chapter 2, Preconfiguring System Configuration Information (Tasks)
Create an install server.	Use the setup_install_server(1M) command to copy the Solaris Software - 1 CD to the install server's hard disk. Use the add_to_install_server(1M) command to copy additional Solaris Software CDs and the Solaris Languages CDs to the install server's hard disk.	Creating an Install Server With SPARC or x86 CD Media
(Optional) Create boot servers.	If you want to install systems from the network that are not on the same subnet as the install server, you must create a boot server on the subnet to boot the systems. Use the `setup_install_server` command with the `-b` option to set up a boot server.If you are using Dynamic Host Configuration Protocol (DHCP), a boot server is not necessary.	Creating a Boot Server on a Subnet With a CD Image
Add systems to be installed from the network.	Use the `add_install_client` command to set up each system that you want to install from the network. Each system that you want to install needs to find the install server, the boot server if required, and configuration information on the network.	Adding Systems to Be Installed From the Network With a CD Image
(Optional) Configure the DHCP server.	If you want to use DHCP to provide system configuration and installation parameters, configure the DHCP server, then create the appropriate options and macros for your installation. Note – If you want to install an x86 based system from the network with PXE, you must configure a DHCP server.	Chapter 13, Planning for DHCP Service (Tasks), in System Administration Guide: IP Services Preconfiguring System Configuration Information With the DHCP Service (Tasks)
Install the system over the network.	Begin the installation by booting the system from the network.	Installing the System From the Network With a CD Image

Creating an Install Server With SPARC or x86 CD Media

If you are using DHCP to set installation parameters or your install server and client are on the same subnet, you do not need a separate boot server.
If your install server and your client are not on the same subnet and you are not using DHCP, you must create separate boot servers for each subnet. You could create an install server for each subnet; however, install servers require more disk space.

SPARC: To Create an Install Server With SPARC or x86 CD Media

Note –

This procedure assumes that the system is running the Volume Manager. If you are not using the Volume Manager to manage media, refer to System Administration Guide: Devices and File Systems.

On the system that is to become the install server, become superuser or assume an equivalent role.

The system must include a CD-ROM drive and be part of the site's network and naming service. If you use a naming service, the system must already be in a naming service, such as NIS, NIS+, DNS, or LDAP. If you do not use a naming service, you must distribute information about this system by following your site's policies.

Insert the Solaris Software - 1 CD in the system's drive.

Create a directory for the CD image.
# mkdir -p install_dir_path
install_dir_path

Specifies the directory where the CD image is to be copied

Change to the Tools directory on the mounted disc.
# cd /cdrom/cdrom0/Solaris_10/Tools

Copy the image in the drive to the install server's hard disk.
# ./setup_install_server install_dir_path
install_dir_path

Specifies the directory where the CD image is to be copied

Note –
The setup_install_server command indicates whether you have enough disk space available for the Solaris Software disc images. To determine available disk space, use the df -kl command.

Decide if you need to make the install server available for mounting.
- If the install server is on the same subnet as the system to be installed or you are using DHCP, you do not need to create a boot server. Proceed to Step 7.
- If the install server is not on the same subnet as the system to be installed and you are not using DHCP, complete the following steps.
  1. Verify that the path to the install server's image is shared appropriately.
    # share | grep install_dir_path
    install_dir_path
    
    Specifies the path to the installation image where the CD image was copied
    - If the path to the install server's directory is displayed and anon=0 is displayed in the options, proceed to Step 7.
    - If the path to the install server's directory is not displayed or you do not have anon=0 in the options, continue.
  2. Make the install server available to the boot server.
    
    Using the share command, add this entry to the /etc/dfs/dfstab file.
    share -F nfs -o ro,anon=0 -d "install server directory" install_dir_path
  3. Verify that the nfsd daemon is running.
    - If the install server is running the current Solaris release, or compatible version, type the following command.
      # svcs -l svc:/network/nfs/server:default
      If the nfsd daemon is online, continue to Step d. If the nfsd daemon is not online, start it.
      # svcadm enable svc:/network/nfs/server
    - If the install server is running the Solaris 9 OS, or compatible version, type the following command.
      # ps -ef | grep nfsd
      If the nfsd daemon is running, continue to Step d. If the nfsd daemon is not running, start it.
      # /etc/init.d/nfs.server start
  4. Share the install server.
    # shareall

Change directories to root (/).
# cd /

Eject the Solaris Software - 1 CD.

Insert the Solaris Software - 2 CD in the system's CD-ROM drive.

Change to the Tools directory on the mounted CD.
# cd /cdrom/cdrom0/Solaris_10/Tools

Copy the CD in the CD-ROM drive to the install server's hard disk.
# ./add_to_install_server install_dir_path
install_dir_path

Specifies the directory where the CD image is to be copied

Change directories to root (/).
# cd /

Eject the Solaris Software - 2 CD.

Repeat Step 9 through Step 13 for each Solaris Software CD that you want to install.

Insert the first Solaris Languages CD in the system's CD-ROM drive.

Change to the Tools directory on the mounted CD.
# cd /cdrom/cdrom0/Solaris_10/Tools

Copy the CD in the CD-ROM drive to the install server's hard disk.
# ./add_to_install_server install_dir_path
install_dir_path

Specifies the directory where the CD image is to be copied

Eject theCD.

Repeat Step 15 through Step 18 for the second Solaris Languages CD.

Change directories to root (/).
# cd /

(Optional) Patch the files that are located in the miniroot on the net install image that was created by setup_install_server.

Patching a file might be necessary if a boot image has problems. For step-by-step procedures, see Chapter 7, Patching the Miniroot Image (Tasks).

Decide if you need to create a boot server.
- If you are using DHCP or the install server is on the same subnet as the system to be installed, you do not need to create a boot server. Proceed to Adding Systems to Be Installed From the Network With a CD Image.
- If you are not using DHCP and the install server and the client are on a different subnet, you must create a boot server. Proceed to Creating a Boot Server on a Subnet With a CD Image.

Example 6–1 x86: Creating an Install Server With CD Media

The following example illustrates how to create an install server by copying the following CDs to the install server's /export/home/cdimage directory. This example assumes that the install server is running the current Solaris release.

Solaris Software CDs
Solaris Languages CDs

Insert the Solaris Software - 1 CD in the system's CD-ROM drive.

# mkdir -p /export/home/cdimage
# cd /cdrom/cdrom0/Solaris_10/Tools
# ./setup_install_server /export/home/cdimage

If you have a separate boot server, add these steps.
1. Make the install server available to the boot server.
  
  Using the share command, add this entry to the /etc/dfs/dfstab file.
  share -F nfs -o ro,anon=0 -d "install server directory" /export/home/cdimage
2. Check if the nfsd daemon is online. If the nfsd daemon is not online, start it and share it.
  # svcs -l svc:/network/nfs/server:default # svcadm enable svc:/network/nfs/server # shareall
3. Continue with the following steps.
If you do not need a boot server or have completed the steps for a separate boot server, continue.

# cd /

Eject the Solaris Software - 1 CD. Insert the Solaris Software - 2 CD in the CD-ROM drive.

# cd /cdrom/cdrom0/Solaris_10/Tools
# ./add_to_install_server /export/home/cdimage
# cd /

Repeat the previous commands for each Solaris Software CD that you want to install.

Insert the first Solaris Languages CD in the CD-ROM drive.

# cd /cdrom/cdrom0/Solaris_10/Tools
# ./add_to_install_server /export/home/cdimage

Eject the CD.

Repeat the previous commands for each Solaris Languages CD.

Continuing the Installation

After you set up the install server, you must add the client as an installation client. For information about how to add client systems to install over the network, see Adding Systems to Be Installed From the Network With a CD Image.

Creating a Boot Server on a Subnet With a CD Image

If you are using DHCP to set installation parameters or your install server and client are on the same subnet, you do not need a boot server. Proceed to Adding Systems to Be Installed From the Network With a CD Image.
If your install server and your client are not on the same subnet and you are not using DHCP, you must create separate boot servers for each subnet. You could create an install server for each subnet; however, install servers require more disk space.

To Create a Boot Server on a Subnet With a CD Image

On the system you intend to make the boot server for the subnet, log in and become superuser or assume an equivalent role.

The system must include a local CD-ROM drive or have access to the remote current Solaris release disc images, which are normally on the install server. If you use a naming service, the system should be in the naming service. If you do not use a naming service, you must distribute information about this system by following your site's policies.

Mount the Solaris Software - 1 CD image from the install server.
# mount -F nfs -o ro server_name:path /mnt
server_name:path

Is the install server name and absolute path to the disc image

Create a directory for the boot image.
# mkdir -p boot_dir_path
boot_dir_path

Specifies the directory where the boot software is to be copied

Change to the Tools directory on the Solaris Software - 1 CD image.
# cd /mnt/Solaris_10/Tools

Copy the boot software to the boot server.
# ./setup_install_server -b boot_dir_path
-b

Specifies to set up the system as a boot server

boot_dir_path

Specifies the directory where the boot software is to be copied

Note –
The setup_install_server command indicates whether you have enough disk space available for the images. To determine available disk space, use the df -kl command.

Change directories to root (/).
# cd /

Unmount the installation image.
# umount /mnt

Example 6–2 Creating a Boot Server on a Subnet With CD Media

The following example illustrates how to create a boot server on a subnet. These commands copy the boot software from the Solaris Software for SPARC Platforms - 1 CD image to /export/install/boot on the system's local disk.

# mount -F nfs -o ro crystal:/export/install/boot /mnt 
# mkdir -p /export/install/boot 
# cd /mnt/Solaris_10/Tools
# ./setup_install_server -b /export/install/boot
# cd /
# umount /mnt

In this example, the disc is inserted and automatically mounted before the command. After the command, the disc is removed.

Continuing the Installation

Adding Systems to Be Installed From the Network With a CD Image

An install server
A boot server if it is required
The sysidcfg file if you use a sysidcfg file to preconfigure system information
A name server if you use a naming service to preconfigure system information
The profile in the JumpStart directory on the profile server if you are using the custom JumpStart installation method

Use the following add_install_client procedure for setting up install servers and clients.

For more options to use with this command, see the man page, add_install_client(1M).

To Add Systems to Be Installed From the Network With `add_install_client` (CDs)

After you create an install server, you must set up each system that you want to install from the network.

Use the following add_install_client procedure for set up an x86 client to install from the network.

Before You Begin

If you have a boot server, make sure you have shared the install server installation image. See the procedure “To Create an Install Server,” Step 6.

Each system that you want to install needs to find the following items.

An install server
A boot server if it is required
The sysidcfg file if you use a sysidcfg file to preconfigure system information
A name server if you use a naming service to preconfigure system information
The profile in the JumpStart directory on the profile server if you are using the custom JumpStart installation method

On the install server or boot server, become superuser or assume an equivalent role.

If you use the NIS, NIS+, DNS, or LDAP naming service, verify that the following information about the system to be installed has been added to the naming service:
- Host name
- IP address
- Ethernet address
For more information about naming services, see System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP).

Change to the Tools directory on the current Solaris release CD image on the install server:
# cd /install_dir_path/Solaris_10/Tools
install_dir_path

Specifies the path to the Tools directory

Add the client to the install server's /etc/ethers file.
1. On the client, find the ethers address. The /etc/ethers map is taken from the local file.
  # ifconfig -a grep ether ether 8:0:20:b3:39:1d
2. On the install server, open the /etc/ethers file in an editor. Add the address to the list.

Set up the client system to be installed from the network.

# ./add_install_client -d -s install_server:install_dir_path \
-c jumpstart_server:jumpstart_dir_path   -p sysid_server:path \
  -t boot_image_path -b "network_boot_variable=value" \
-e ethernet_address client_name platform_group

-d

For x86 clients, use this option to boot the systems from the network by using PXE network boot. The output of this option lists the DHCP options you need to create on the DHCP server.

For more information about class-specific installations by using DHCP, see Creating DHCP Options and Macros for Solaris Installation Parameters.

-s install_server:install_dir_path

Specifies the name and path to the install server.

install_server is the host name of the install server
install_dir_path is the absolute path to the current Solaris release CD image

-c jumpstart_server:jumpstart_dir_path

-p sysid_server:path

-t boot_image_path

Specifies the path to an alternate boot image if you want to use a boot image other than the one in the Tools directory on the current Solaris release net installation image, CD, or DVD.

-b “boot-property=value”

x86 based systems only: Enables you to set the value of a boot property variable that you want to use to boot the client from the network. The -b must be used with the -e option.

See the eeprom(1M) man page for descriptions of boot properties.

-e ethernet_address

For more information about client-specific installations by using DHCP, see Creating DHCP Options and Macros for Solaris Installation Parameters.

client_name

Is the name of the system to be installed from the network. This name is not the host name of the install server.

platform_group

Is the platform group of the system to be installed. A detailed list of platform groups appears in Platform Names and Groups in Solaris 10 5/09 Installation Guide: Planning for Installation and Upgrade.

Example 6–3 SPARC: Adding a SPARC Install Client on a SPARC Install Server When Using DHCP (CDs)

The following example illustrates how to add an install client when you are using DHCP to set installation parameters on the network. The install client is named basil, which is an Ultra 5 system. The file system /export/home/cdsparc/Solaris_10/Tools contains the add_install_client command.

For more information on how to use DHCP to set installation parameters for network installations, see Preconfiguring System Configuration Information With the DHCP Service (Tasks).

sparc_install_server# cd /export/home/cdsparc/Solaris_10/Tools
sparc_install_server# ./add_install_client -d basil sun4u

Example 6–4 Adding an Install Client That Is on the Same Subnet as Its Server (CDs)

The following example illustrates how to add an install client that is on the same subnet as the install server. The install client is named basil, which is an Ultra 5 system. The file system /export/home/cdsparc/Solaris_10/Tools contains the add_install_client command.

install_server# cd /export/home/cdsparc/Solaris_10/Tools
install_server# ./add_install_client basil sun4u

Example 6–5 Adding an Install Client to a Boot Server (CDs)

The following example illustrates how to add an install client to a boot server. The install client is named rose, which is an Ultra 5 system. Run the command on the boot server. The -s option is used to specify an install server that is named rosemary, which contains a current Solaris release CD image in /export/home/cdsparc.

boot_server# cd /export/home/cdsparc/Solaris_10/Tools
boot_server# ./add_install_client -s rosemary:/export/home/cdsparc rose sun4u

Example 6–6 x86: Adding a Single x86 Install Client on an x86 Install Server When Using DHCP (CD)

The GRUB bootloader does not use the SUNW.i86pc DHCP class name. The following example illustrates how to add an x86 install client to an install server when you are using DHCP to set installation parameters on the network.

The -d option is used to specify that clients are to use the DHCP protocol for configuration. If you plan to use PXE network boot, you must use the DHCP protocol.
The -e option indicates that this installation will only occur on the client with the Ethernet address 00:07:e9:04:4a:bf .
The -s option is used to specify that the clients are to be installed from the install server that is named rosemary.

This server contains a Solaris Operating System for x86 Platforms DVD image in /export/home/cdx86.

x86_install_server# cd /export/boot/cdx86/Solaris_10/Tools
x86_install_server# ./add_install_client -d -e 00:07:e9:04:4a:bf \ 
-s rosemary:/export/home/cdx86 i86pc

The previous commands set up the client with the Ethernet address 00:07:e9:04:4a:bf as an installation client. The boot file 010007E9044ABF.i86pc is created on the installation server. In previous releases, this boot file was named nbp.010007E9044ABF.i86pc.

For more information on how to use DHCP to set installation parameters for network installations, see Preconfiguring System Configuration Information With the DHCP Service (Tasks).

Example 6–7 x86: Specifying a Serial Console to Use During a Network Installation (CDs)

The -d option indicates that the client is set up to use DHCP to set installation parameters.
The -e option indicates that this installation will occur only on the client with the Ethernet address 00:07:e9:04:4a:bf.
The -b option instructs the installation program to use the serial port ttya as an input and an output device.

Add the client.

install server# cd /export/boot/cdx86/Solaris_10/Tools
install server# ./add_install_client -d -e "00:07:e9:04:4a:bf" \
-b "console=ttya" i86pc

For a complete description of the boot property variables and values you can use with the -b option, see the eeprom(1M) man page.

Continuing the Installation

x86 based systems: If you are not using a DHCP server, you must boot the system from a local Solaris OS DVD or CD.

Installing the System From the Network With a CD Image

After you add the system as an installation client, you can install the client from the network. This section describes the following tasks.

See SPARC: To Install the Client Over the Network (CDs) for instructions about how to boot and install SPARC based systems over the network.
See x86: To Install the Client Over the Network With GRUB (CDs) for instructions about how to boot and install x86 based systems over the network.

SPARC: To Install the Client Over the Network (CDs)

Before You Begin

This procedure assumes that you have completed the following tasks.

Set up an install server. For instructions about how to create an install server from CD media, see SPARC: To Create an Install Server With SPARC or x86 CD Media.
Set up a boot server or a DHCP server, if necessary. If the system you want to install is on a different subnet than the installation server, you must set up a boot server, or use a DHCP server. For instructions about how to set up a boot server, see Creating a Boot Server on a Subnet With a CD Image. For instructions about how to set up a DHCP server to support network installations, see Preconfiguring System Configuration Information With the DHCP Service (Tasks).
Gathered or preconfigured the information you need to install. You can perform this task in one or more of the following ways.
- Gather the information in Checklist for Installation in Solaris 10 5/09 Installation Guide: Planning for Installation and Upgrade.
- Create a sysidcfg file if you use a sysidcfg file to preconfigure system information. For information about how to create a sysidcfg file, see Preconfiguring With the sysidcfg File.
- Set up a name server if you use a naming service to preconfigure system information. For information about how to preconfigure information with a naming service, see Preconfiguring With the Naming Service.
- Create a profile in the JumpStart directory on the profile server if you are using the custom JumpStart installation method. For information about how to set up a custom JumpStart installation, see Chapter 3, Preparing Custom JumpStart Installations (Tasks), in Solaris 10 5/09 Installation Guide: Custom JumpStart and Advanced Installations.

Turn on the client system.

If the system is currently running, bring the system to run level 0.

The ok prompt is displayed.

Boot the system from the network.
- To install with the Solaris interactive installation GUI, type the following command.
  ok boot net
- To install with the Solaris interactive text installer in a desktop session, type the following command.
  ok boot net - text
- To install with the Solaris interactive text installer in a console session, type the following command.
  ok boot net - nowin
The system boots from the network.

If you are prompted, answer the system configuration questions.
- If you preconfigured all of the system information, the installation program does not prompt you to enter any configuration information. See Chapter 2, Preconfiguring System Configuration Information (Tasks) for more information.
- If you did not preconfigure all the system information, use the Checklist for Installation in Solaris 10 5/09 Installation Guide: Planning for Installation and Upgradeto help you answer the configuration questions.
  
  Note –
  If the keyboard is self-identifying, the keyboard layout automatically configures during installation. If the keyboard is not self-identifying, you can select from a list of supported keyboard layouts during installation.
  
  PS/2 keyboards are not self-identifying. You will be asked to select the keyboard layout during the installation.
  
  For further information, see keyboard Keyword.
  
  Note –
  During installation, you can choose the default NFSv4 domain name. Or, you can specify a custom NFSv4 domain name. For further information, see NFSv4 Domain Name Configurable During Installation in Solaris 10 5/09 Installation Guide: Planning for Installation and Upgrade.
If you are using the GUI, after you confirm the system configuration information, the Welcome to Solaris panel appears.

If you are prompted, answer any additional questions to complete your installation.
- If you preconfigured all of the installation options, the installation program does not prompt you to enter any installation information. See Chapter 2, Preconfiguring System Configuration Information (Tasks) for more information.
- If you did not preconfigure all the installation options, use the Checklist for Installation in Solaris 10 5/09 Installation Guide: Planning for Installation and Upgrade to help you answer the installation questions.

x86: To Install the Client Over the Network With GRUB (CDs)

Before You Begin

This procedure assumes that you have completed the following tasks.

Set up an install server. For instructions about how to create an install server from CD media, see To Create an Install Server With SPARC or x86 DVD Media.
Set up a boot server or a DHCP server, if necessary. If the system you want to install is on a different subnet than the installation server, you must set up a boot server, or use a DHCP server. For instructions about how to set up a boot server, see Creating a Boot Server on a Subnet With a DVD Image. For instructions about how to set up a DHCP server to support network installations, see Preconfiguring System Configuration Information With the DHCP Service (Tasks).
Gathered or preconfigured the information you need to install. You can perform this task in one or more of the following ways.
- Gather the information in Checklist for Installation in Solaris 10 5/09 Installation Guide: Planning for Installation and Upgrade.
- Create a sysidcfg file if you use a sysidcfg file to preconfigure system information. For information about how to create a sysidcfg file, see Preconfiguring With the sysidcfg File.
- Set up a name server if you use a naming service to preconfigure system information. For information about how to preconfigure information with a naming service, see Preconfiguring With the Naming Service.
- Create a profile in the JumpStart directory on the profile server if you are using the custom JumpStart installation method. For information about how to set up a custom JumpStart installation, see Chapter 3, Preparing Custom JumpStart Installations (Tasks), in Solaris 10 5/09 Installation Guide: Custom JumpStart and Advanced Installations.

This procedure also assumes that your system can boot from the network.

Turn on the system.

Type the appropriate keystroke combination to enter the system BIOS.

Some PXE-capable network adapters have a feature that enables PXE boot if you type a particular keystroke in response to a brief boot-time prompt.

In the system BIOS, instruct the system to boot from the network.

See your hardware documentation for information about how to set the boot priority in the BIOS.

Exit the BIOS.

The system boots from the network. The GRUB menu is displayed.

Note –

The GRUB menu that is displayed on your system might vary from the following sample, depending on the configuration of your network installation server.

GNU GRUB version 0.95 (631K lower / 2095488K upper memory)
+-----------------------------------------------------------------------------------------------------------+
| Solaris 10 5/09  /cdrom0                                                           
|                                                                                                           |
|                                                                                                           |
+-----------------------------------------------------------------------------------------------------------+
Use the ^ and v keys to select which entry is highlighted.
Press enter to boot the selected OS, 'e' to edit the
commands before booting, or 'c' for a command-line.

Select the appropriate installation option.
- To install the Solaris OS from the network, select the appropriate Solaris entry on the menu, then press Enter.
  
  Select this entry if you want to install from the network installation server you set up in To Create an Install Server With SPARC or x86 DVD Media.
- To install the Solaris OS from the network with specific boot arguments, follow these steps.
  
  You might need to set specific boot arguments if you want to modify the device configuration during the installation, and did not set these boot arguments previously with the add_install_client command as described in To Add Systems to Be Installed From the Network With add_install_client (DVD).
  1. On the GRUB menu, select the installation option you want to edit, then press e.
    
    Boot commands that are similar to the following text are displayed in the GRUB menu.
    kernel /I86pc.Solaris_10/multiboot kernel/unix \ -B install_media=192.168.2.1:/export/cdrom0/boot \ module /platform/i86pc/boot_archive
  2. Use the arrow keys to select the boot entry that you want to edit, then press e.
    
    The boot command that you want to edit is displayed in the GRUB edit window.
  3. Edit the command by typing the boot arguments or options you want to use.
    
    The command syntax for the Grub edit menu is as follows.
    grub edit>kernel /image_directory/multiboot kernel/unix/ \ install [url|ask] -B options install_media=media_type
    For information about boot arguments and command syntax, see Table 9–1.
  4. To accept your edits and return to the GRUB menu, press Enter.
    
    The GRUB menu is displayed. The edits you made to the boot command are displayed.
  5. To begin the installation, type b in the GRUB menu.
The Solaris installation program checks the default boot disk for the requirements to install or upgrade the system. If the Solaris installation cannot detect the system configuration, the program prompts you for any missing information.

When the check is completed, the installation selection screen is displayed.

Select an installation type.

The installation selection screen displays the following options.

      Select the type of installation you want to perform:

         1 Solaris Interactive
         2 Custom JumpStart
         3 Solaris Interactive Text (Desktop session)
         4 Solaris Interactive Text (Console session)
         5 Apply driver updates
         6 Single user shell

         Enter the number of your choice followed by the <ENTER> key.
         Alternatively, enter custom boot arguments directly.

         If you wait 30 seconds without typing anything,
         an interactive installation will be started.

To install the Solaris OS, choose from the following options.
- To install with the Solaris interactive installation GUI, type 1, then press Enter.
- To install with the interactive text installer in a desktop session, type 3, then press Enter.
  
  Select this installation type to override the default GUI installer and run the text installer.
- To install with the interactive text installer in a console session, type 4, then press Enter.
  
  Select this installation type to override the default GUI installer and run the text installer.
If you want to perform an unattended custom JumpStart installation (option 2), see Solaris 10 5/09 Installation Guide: Custom JumpStart and Advanced Installations.

For detailed information about the Solaris installation GUI and text installer, see System Requirements and Recommendations in Solaris 10 5/09 Installation Guide: Planning for Installation and Upgrade.

The system configures the devices and interfaces, and searches for configuration files. The installation program begins. Go to Step 7 to continue the installation.

To perform system administration tasks before your installation, choose from the following options.
- To update drivers or install an install time update (ITU), insert the update media, type 5, then press Enter.
  
  You might need to update drivers or install an ITU to enable the Solaris OS to run on your system. Follow the instructions for your driver update or ITU to install the update.
- To perform system administration tasks, type 6, then press Enter.
  
  You might want to launch a single user shell if you need to perform any system administration tasks on your system before you install. For information about system administration tasks you can perform prior to installation, see System Administration Guide: Basic Administration.
After you perform these system administration tasks, the previous list of options is displayed. Select the appropriate option to continue the installation.

If you are prompted, answer the system configuration questions.
- If you preconfigured all of the system information, the installation program does not prompt you to enter any configuration information. See Chapter 2, Preconfiguring System Configuration Information (Tasks) for more information.
- If you did not preconfigure all the system information, use the Checklist for Installation in Solaris 10 5/09 Installation Guide: Planning for Installation and Upgrade to help you answer the configuration questions.
  
  Note –
  If the keyboard is self-identifying, the keyboard layout automatically configures during installation. If the keyboard is not self-identifying, you can select from a list of supported keyboard layouts during installation.
  
  For further information, see keyboard Keyword.
  
  Note –
  During installation, you can choose the default NFSv4 domain name. Or, you can specify a custom NFSv4 domain name. For further information, see NFSv4 Domain Name Configurable During Installation in Solaris 10 5/09 Installation Guide: Planning for Installation and Upgrade.
If you are using the installation GUI, after you confirm the system configuration information, the Welcome to Solaris panel appears.

If you are prompted, answer any additional questions to complete your installation.
- If you preconfigured all of the installation options, the installation program does not prompt you to enter any installation information. See Chapter 2, Preconfiguring System Configuration Information (Tasks) for more information.
- If you did not preconfigure all the installation options, use the Checklist for Installation in Solaris 10 5/09 Installation Guide: Planning for Installation and Upgrade to help you answer the installation questions.

After the system boots and installs over the network, instruct the system to boot from the disk drive on subsequent boots.

Note –
When you boot the system after the installation, a GRUB menu lists the operating systems that are installed, including the newly-installed Solaris OS. Select which operating system you want to boot. The default selection loads if you do not make another selection.

Next Steps

If you install multiple operating systems on your machine, you need to instruct the GRUB boot loader to recognize these operating systems in order to boot. For more information, see Modifying Boot Behavior by Editing the GRUB Menu at Boot Time in System Administration Guide: Basic Administration.

Chapter 7 Patching the Miniroot Image (Tasks)

This chapter provides a step-by-step procedure and an example to patch the miniroot image when you are setting up an install server.

This chapter covers the following topics:

Patching the Miniroot Image (Tasks)

You might need to Patch the files that are located in the miniroot on the network installation image that was created by setup_install_server.

About the Miniroot Image (Overview)

The miniroot is a minimal, bootable root (/) file system that resides on the Solaris installation media. A miniroot consists of all the Solaris software that is required to boot the system to either install or upgrade the system. The miniroot software is used by the installation media to perform a full installation of the Solaris OS. The miniroot runs only during the installation process.

You might need to patch the miniroot before installation if the boot image has problems booting or if you need to add driver and hardware support. When you patch the miniroot image, the patch is not installed on the system where the Solaris OS installation occurs or on the system that the patchadd command is run. Patching the miniroot image is strictly used for adding driver and hardware support to the process that performs the actual installation of the Solaris OS.

Note –

This procedure is only for patching the miniroot, not for patching the complete network installation image. If you need to patch the network installation image, perform the task after the installation completes.

How To Patch the Miniroot Image

Follow these steps to patch a network installation miniroot image.

Note –

These steps assume that you have a system on your network that is running the current Solaris release, and that system is accessible over the network.

On a system that is running the current Solaris release, log in as superuser or assume an equivalent role.

Change to the Tools directory of the installation image you created in Step 5.
# cd install-server-path/install-dir-path/Solaris_10/Tools
install-server-path

Specifies the path to the install server system on your network, for example, /net/installserver-1.

Create a new installation image, and place that image on the system that is running the current Solaris release.
# ./setup_install_server remote_install_dir_path
remote_install_dir_path

Specifies the path on the current Solaris release in which to create the new installation image.

This command creates a new installation image on the current Solaris release. In order to patch this image, you must temporarily place this image on a system that is running the current Solaris release.

On the current Solaris release, unpack the network installation boot archive.
# /boot/solaris/bin/root_archive unpackmedia remote_install_dir_path \ destination_dir
remote_install_dir_path

Specifies the path to the network installation image on the current Solaris release.

destination_dir

Specifies the path to the directory to contain the unpacked boot archive.

On the current Solaris release, patch the unpacked boot archive.
# patchadd -C destination_dir path-to-patch/patch-id
path-to-patch

Specifies the path to the patch that you want to add, for example, /var/sadm/spool.

patch-id

Specifies the patch ID that you want to apply.

You can specify multiple patches with the patchadd -M option. For more information, see patchadd(1M).

Caution –
Don't use the patchadd -C command unless you have read the Patch README instructions or have contacted your local Sun support office.

On the current Solaris release, pack the boot archive.

# /boot/solaris/bin/root_archive packmedia remote_install_dir_path \
  destination_dir

Copy the patched archives to the installation image on the install server.

# cd remote_install_dir_path
# find boot Solaris_10/Tools/Boot | cpio -pdum \
   install-server-path/install_dir_path

Next Steps

After you have set up the install server and patched the miniroot, you might need to set up a boot server or add systems to be installed from the network.

If you are using DHCP or the install server is on the same subnet as the system to be installed, you do not need to create a boot server. Proceed to Adding Systems to Be Installed From the Network With a DVD Image.
If you are not using DHCP and the install server and the client are on a different subnet, you must create a boot server. Proceed to Creating a Boot Server on a Subnet With a DVD Image.

Patching the Miniroot Image (Example)

This example describes the steps to patch a miniroot image to create a modified miniroot.

Patching the Miniroot Image

In this example, you perform the unpacking and packing of the miniroot on a system that is running the current release.

How to Modify the Miniroot (Example)

This procedure shows how to install a Kernel Update (KU) patch on a Solaris 10 5/09 miniroot image. On a system that is running the Solaris 10 OS, follow these steps, but note these details.

jmp-start1 — Is a network installation server that is running the Solaris 9 OS
v20z-1 — Is a system that is running the Solaris 10 OS, with GRUB implemented
v20z-1:/export/mr — Is the unpacked miniroot location
v20z-1:/export/u1 — Is the installation image that was created, so it could be modified

The network installation image is located at/net/jmpstart1/export/images/solaris_10_u1/Solaris_10/Tools.

On a system that is running the current Solaris release, log in as superuser or assume an equivalent role.

Change to the directory where you want to unpack the miniroot and place the network installation image.
# cd /net/server-1/export

Create the installation and miniroot directories.
# mkdir /export/u1 /export/mr

Change directories to the Tools directory where the Solaris 10 5/09 installation images are located.
# cd /net/jmp-start1/export/images/solaris_10/Solaris_10/Tools

Create a new installation image, and place the image on the system that is running the current Solaris release.

# ./setup_install_server /export/u1
Verifying target directory...
Calculating the required disk space for the Solaris_10 product
Calculating space required for the installation boot image
Copying the CD image to disk...
Copying Install Boot Image hierarchy...
Copying /boot  netboot hierarchy...
Install Server setup complete

The installation server setup is now complete.

Run the following command to unpack the miniroot.

 # /boot/solaris/bin/root_archive unpackmedia /export/u1 /export/mr

Change directories.
# cd /export/mr/sbin

Make a copy of the rc2 and the sulogin files.

# cp rc2 rc2.orig
# cp sulogin sulogin.orig

Apply all required patches to the miniroot.

patchadd -C /export/mr /export patchid

patchid specifies the patch ID that you want to apply.

In this example, five patches are applied to the miniroot.

# patchadd -C /export/mr /export/118344-14
# patchadd -C /export/mr /export/122035-05
# patchadd -C /export/mr /export/119043-10
# patchadd -C /export/mr /export/123840-04
# patchadd -C /export/mr /export/118855-36

Export the SVCCFG_REPOSITORY variable.
# export SVCCFG_REPOSITORY=/export/mr/etc/svc/repository.db
Caution –
The SVCCFG_REPOSITORY variable must point to the location of the unpacked miniroot's repository.db file. In this example, that location is the /export/mr/etc/svc directory. The repository.db file is located in the directory /etc/svc under the unpacked miniroot. Failure to export this variable results in the modification of the live repository, which prevents the live system from booting.

Modify the miniroot's repository.db file.

# svccfg -s system/manifest-import setprop start/exec = :true
# svccfg -s system/filesystem/usr setprop start/exec = :true
# svccfg -s system/identity:node setprop start/exec = :true
# svccfg -s system/device/local setprop start/exec = :true
# svccfg -s network/loopback:default setprop start/exec = :true
# svccfg -s network/physical:default setprop start/exec = :true
# svccfg -s milestone/multi-user setprop start/exec = :true

For more information, see the svccfg(1M) man page.

Change directories. Then, restore the original copies of the rc2.orig and sulogin.orig files.
# cd /export/mr/sbin # mv rc2.orig rc2 # mv sulogin.orig sulogin

Pack the modified miniroot that contains the changes you made. Place the modified miniroot in the /export/u1 directory.
# /boot/solaris/bin/root_archive packmedia /export/u1 /export/mr
This step essentially replaces /export/u1/boot/miniroot directory, along with some other necessary files.

Next Steps

After you have set up the install server and patched the miniroot, you might need to set up a boot server or add systems to be installed from the network.

If you are using DHCP or the install server is on the same subnet as the system to be installed, you do not need to create a boot server. You are finished. Proceed to Adding Systems to Be Installed From the Network With a DVD Image.
If you are not using DHCP and the install server and the client are on a different subnet, you must create a boot server. Proceed to Creating a Boot Server on a Subnet With a DVD Image.

Chapter 8 Installing Over the Network (Examples)

This chapter provides examples that illustrate how to use DVD or CD media to install the Solaris OS over the network.

All examples in this chapter have the following conditions.

The install server
- Is a network installation image.
- Runs the current Solaris release.
- Is already part of the site's network and naming service.
You have already gathered or preconfigured the information that you need in order to install. For further information, see Chapter 5, Gathering Information Before Installation or Upgrade (Planning), in Solaris 10 5/09 Installation Guide: Planning for Installation and Upgrade.

Choose an example from one of the following additional options.

Network Installation Over the Same Subnet (Examples)
- The install client is on the same subnet as the install server. Therefore, you do not need to create a boot server.
- The network installation uses a graphical user interface (GUI) in a desktop session.
Network Installation Over a Different Subnet (Examples TBD)
- The install client is on the different subnet from the install server. Therefore, you must create a boot server.
- The network installation uses a text installer in a desktop session

Network Installation Over the Same Subnet (Examples)

This section includes the following examples.

Example 8–1: SPARC: Install on the Same Subnet (With DVD Media)
Example 8–2: SPARC: Install on the Same Subnet (With CD Media)
Example 8–3: x86: Install on the Same Subnet (With DVD Media)
Example 8–4: x86: Install on the Same Subnet (With CD Media)

Example 8–1 SPARC: Install Over the Same Subnet (With DVD Media)

This example creates a SPARC install server with SPARC DVD media.

This example has the following conditions:

The install client is on the same subnet as the install server.
The network installation uses a graphical user interface (GUI) in a desktop session.
General conditions for this example are listed at Chapter 8, Installing Over the Network (Examples).

Create and set up a SPARC install server.

This example creates an install server by copying the Solaris DVD to the install server's /export/home/dvdsparc directory.
1. Insert the Solaris DVD in the SPARC system's drive.
2. Use the following command to create a directory to contain the DVD image. This command also changes to the Tools directory on the mounted disc. Then the command copies the DVD image in the drive to the install server's hard disk.
  # mkdir -p /export/home/dvdsparc # cd /cdrom/cdrom0/Solaris_10/Tools # ./setup_install_server /export/home/dvdsparc
Install the system with a network installation image.

In this example, you install with the Solaris interactive installation GUI.
1. Boot the system from the network.
2. To install with the Solaris interactive installation GUI, type the following command.
  ok bootnet - install
  The system installs from the network.
3. If you are prompted, answer the system configuration questions. If you preconfigured all of the system information, the installation program does not prompt you to enter any configuration information.
  
  After you confirm the system configuration information, the Welcome to Solaris panel appears. The installation is complete.

For a more detailed explanation about the network installation procedures that are used in this example, see Chapter 5, Installing From the Network With DVD Media (Tasks).

Example 8–2 SPARC: Install Over the Same Subnet (With CD Media)

This example creates a SPARC install server with SPARC CD media.

This example has the following conditions:

The install client is on the same subnet as the install server.
The network installation uses a graphical user interface (GUI) in a desktop session.
General conditions for this example are listed at Chapter 8, Installing Over the Network (Examples).

Create and set up a SPARC install Server.

The following example illustrates how to create an install server by copying the CD media to the install server's /export/home/cdsparc directory.
1. Insert the Solaris Software for SPARC Platforms - 1 CD in the system's CD-ROM drive.
2. Use the following command to create a directory for the CD image. This command also changes to the Tools directory on the mounted disc, and copies the image in the drive to the install server's hard disk.
  # mkdir -p /export/home/cdsparc # cd /cdrom/cdrom0/Solaris_10/Tools # ./setup_install_server /export/home/cdsparc # cd /
Add systems to be installed from the network.
1. Insert the Solaris Software for SPARC Platforms - 2 CD in the CD-ROM drive.
2. Use the following command. This command changes to the Tools directory on the mounted CD. The command copies the CD in the CD-ROM drive to the install server's hard disk. Then the command changes to the root (/) directory.
  # cd /cdrom/cdrom0/Solaris_10/Tools # ./add_to_install_server /export/home/cdsparc # cd /
3. Repeat the previous commands for each Solaris Software CD that you want to install.
4. Insert the first Solaris Languages for SPARC Platforms CD in the CD-ROM drive.
  # cd /cdrom/cdrom0/Solaris_10/Tools # ./add_to_install_server /export/home/cdsparc
5. Eject the CD.
6. Repeat the previous commands for each Solaris Languages for SPARC Platforms CD CD that you want to install.
Install the system with a network installation image.
1. Boot the system from the network.
2. To install with the Solaris interactive installation GUI, type the following command.
  ok boot net
  The system installs from the network.
3. If you are prompted, answer the system configuration questions.
  
  After you confirm the system configuration information, the Welcome to Solaris panel appears. The installation is complete.

For a more detailed explanation about the network installation procedures that are used in this example, see Chapter 6, Installing From the Network With CD Media (Tasks).

Example 8–3 x86: Install Over the Same Subnet (With DVD Media)

This example creates an x86 install server with x86 DVD media.

This example has the following conditions:

The install client is on the same subnet as the install server.
The network installation uses a graphical user interface (GUI) in a desktop session.
General conditions for this example are listed at Chapter 8, Installing Over the Network (Examples).

Create and set up an x86 install server.

The following examples illustrate how to create an x86 install server by copying the Solaris Operating System for x86 Platforms DVD to the install server's /export/home/dvdx86 directory.
1. Insert the Solaris DVD into the system's drive.
2. Use the following command. This command creates a directory to contain the boot image. Then this command changes to the Tools directory on the mounted disc. Also, the command copies the disc in the drive to the install server's hard disk by using the setup_install_server command:
  # mkdir -p /export/home/dvdx86 # cd /cdrom/cdrom0/Solaris_10/Tools # ./setup_install_server /export/home/dvdx86
3. Make the install server available to the boot server.
  
  Using the share command, add this entry to the /etc/dfs/dfstab file.
  share -F nfs -o ro,anon=0 -d "install server directory" install_dir_path
4. Check if the nfsd daemon is online. If the nfsd daemon is not online, start it and share it.
  # svcs -l svc:/network/nfs/server:default # svcadm enable svc:/network/nfs/server # shareall # cd /
Note –
If the install server was running the Solaris 9 OS, or compatible version, you would type the following command instead.
# ps -ef | grep nfsd
For this older release, if the nfsd daemon was running, you would continue to the next step. If the nfsd daemon was not running, you would start it.
# /etc/init.d/nfs.server start
Add systems to be installed from the network.
1. Add the client to the install server's /etc/ethers file.
  
  On the client, find the ethers address. The /etc/ethers map is taken from the local file.
  # ifconfig -a grep ether ether 8:0:20:b3:39:1d
  On the install server, open the /etc/ethers file in an editor. Add the address to the list.
2. Use the following command. This command changes to the Tools directory on the Solaris DVD image. Then, this command sets up the client system so that it can be installed from the network.
  install_server# cd /export/home/dvdx86/Solaris_10/Tools install_server# ./add_install_client basil i86pc
Install the system with a network installation image.

The Solaris installation programs for x86 based systems use the GRUB boot loader. This example installs an x86 based system over the network with the GRUB boot loader.
1. In the system BIOS, instruct the system to boot from the network.
  
  After you exit BIOS, the system installs from the network. The GRUB menu is displayed.
2. To install the Solaris OS from the network, select the appropriate Solaris entry on the menu, then press Enter.
  
  The installation selection screen is displayed.
3. To install with the Solaris interactive installation GUI, type 1, then press Enter.
  
  The installation program begins.
4. If you are prompted, answer the system configuration questions.
  
  After you confirm the system configuration information, the Welcome to Solaris panel appears.
  
  After the system boots and installs over the network, instruct the system to boot from the disk drive on subsequent boots.
  
  Note –
  When you boot the system after the installation, a GRUB menu lists the operating systems that are installed, including the newly-installed Solaris OS. Select which operating system you want to boot. The default selection loads if you do not make another selection.

For further information, see the following references.

Procedure	Reference
For a more detailed explanation about the network installation procedures that are used in this example	Chapter 5, Installing From the Network With DVD Media (Tasks)
For information about how to complete an interactive installation with the Solaris installation GUI	To Install or Upgrade With the Solaris Installation Program With GRUB in Solaris 10 5/09 Installation Guide: Basic Installations
For overview information about the GRUB boot loader	Chapter 7, SPARC and x86 Based Booting (Overview and Planning), in Solaris 10 5/09 Installation Guide: Planning for Installation and Upgrade

Example 8–4 x86: Install Over the Same Subnet (With CD Media)

This example creates an x86 install server with x86 CD media.

This example has the following conditions:

The install client is on the same subnet as the install server.
The network installation uses a graphical user interface (GUI) in a desktop session.
General conditions for this example are listed at Chapter 8, Installing Over the Network (Examples).

Create and set up an x86 install server.
1. Insert the Solaris Software - 1 CD in the system's drive.
2. Use the following command. This command creates a directory for the CD image and changes to the Tools directory on the mounted disc. This command then copies the image in the drive to the install server's hard disk.
  # mkdir -p /export/home/dvdx86 # cd /cdrom/cdrom0/Solaris_10/Tools # ./setup_install_server /export/home/cdx86
3. Insert the Solaris Software - 2 CD in the system's CD-ROM drive.
4. Use the following command. This command changes to the Tools directory on the mounted CD. Then this command copies the CD in the CD-ROM drive to the install server's hard disk and changes to the root (/) directory.
  # cd /cdrom/cdrom0/Solaris_10/Tools # ./add_to_install_server /export/home/cdx86 # cd /
5. Repeat the previous commands for each Solaris Software CD that you want to install.
6. Insert the first Solaris Languages CD in the system's CD-ROM drive.
7. Use the following command. This command changes to the Tools directory on the mounted CD. This command then copies the CD in the CD-ROM drive to the install server's hard disk.
  # cd /cdrom/cdrom0/Solaris_10/Tools # ./add_to_install_server /export/home/cdx86
8. Eject the CD.
9. Repeat the previous commands for each Solaris Languages for SPARC Platforms CD CD that you want to install.
Add systems to be installed from the network.

In this example, the install client is named basil, which is an x86 system. The file system /export/home/cdx86/Solaris_10/Tools contains the add_install_client command.
1. Add the client to the install server's /etc/ethers file. On the client, find the ethers address. The /etc/ethers map is taken from the local file.
  # ifconfig -a grep ether ether 8:0:20:b3:39:1d
2. On the install server, open the /etc/ethers file in an editor. Add the address to the list.
3. Use the following command. This command changes to the Tools directory on the current Solaris release CD image on the install server. Then this command adds the client system to be installed from the network.
  install_server# cd /export/home/cdx86/Solaris_10/Tools install_server# ./add_install_client basil i86pc
Install the system with a network installation image.

This step describes how to install an x86 based system over the network with the GRUB boot loader.
1. In the system BIOS, instruct the system to boot from the network.
  
  After you exit BIOS, the system installs from the network. The GRUB menu is displayed.
2. To install the Solaris OS from the network, select the appropriate Solaris entry on the menu, then press Enter.
  
  The installation selection screen is displayed.
3. To install with the Solaris interactive installation GUI, type 1, then press Enter.
  
  The installation program begins.
4. If you are prompted, answer the system configuration questions.
  
  After you confirm the system configuration information, the Welcome to Solaris panel appears.
5. After the system boots and installs over the network, instruct the system to boot from the disk drive on subsequent boots.
  
  Note –
  When you boot the system after the installation, a GRUB menu lists the operating systems that are installed, including the newly-installed Solaris OS. Select which operating system you want to boot. The default selection loads if you do not make another selection.

For further information, see the following references.

Procedure	Reference
For a more detailed explanation about the network installation procedures that are used in this example	Chapter 6, Installing From the Network With CD Media (Tasks)
For information about how to complete an interactive installation with the Solaris installation GUI	To Install or Upgrade With the Solaris Installation Program With GRUB in Solaris 10 5/09 Installation Guide: Basic Installations
For overview information about the GRUB boot loader	Chapter 7, SPARC and x86 Based Booting (Overview and Planning), in Solaris 10 5/09 Installation Guide: Planning for Installation and Upgrade

Chapter 9 Installing From the Network (Command Reference)

This chapter lists the commands used to set up network installations. This chapter includes the following topics.

Network Installation Commands

This table describes the commands you use to install Solaris software over the network. The table also indicates to which platform the commands apply.

Command	Platform	Description
`add_install_client`	All	A command that adds network installation information about a system to an install server or boot server from the network. The `add_install_client`(1M) man page contains more information.
`setup_install_server`	All	A script that copies the current Solaris release DVD or CDs to an install server's local disk or copies the boot software to a boot server. The setup_install_server(1M) man page contains more information.
(CD media only) `add_to_install_server`	All	A script that copies additional packages within a product tree on the CDs to the local disk on an existing install server. The add_to_install_server(1M) man page contains more information.
`mount`	All	A command that enables the mounting of file systems and shows the mounted file systems, including the file system on the Solaris DVD or Solaris Software and Solaris Languages CDs. The mount(1M) man page contains more information.
`showmount -e`	All	A command that lists all the shared file systems that are located on a remote host. The showmount(1M) man page contains more information.
`uname -i`	All	A command for determining a system's platform name, for example, SUNW,Ultra-5_10, or i86pc. You might need the system's platform name when you install the Solaris software. The uname(1) man page contains more information.
`patchadd -C` `net_install_image`	All	A command to add patches to the files that are located in the miniroot, `Solaris_10 /Tools/Boot`, on a net installation image of a DVD or CD that is created by `setup_install_server`. This facility enables you to patch Solaris installation commands and other miniroot-specific commands. `net_install_image` is the absolute path name of the net installation image. Caution – Don't use the `patchadd -C` command unless you have read the `Patch README` instructions or have contacted your local Sun support office. For more information, see the following references: Chapter 7, Patching the Miniroot Image (Tasks) The patchadd(1M) man page contains more information.
`reset`	SPARC	An Open Boot PROM command for resetting the system and rebooting the machine. Or, if you boot and see a series of error messages about I/O interrupts, press the Stop and A keys at the same time, and then type `reset` at the `ok` or `>` PROM prompt.
`banner`	SPARC	An Open Boot PROM command that displays system information, such as model name, Ethernet address, and memory installed. You can issue this command only at the `ok` or `>` PROM prompt.

x86: GRUB Menu Commands for Installation

You can customize the network boot and installation of your system by editing the commands in the GRUB menu. This section describes several commands and arguments you can insert in the commands in the GRUB menu.

In the GRUB menu, you can access the GRUB command line by typing b at the prompt. A command line that is similar to the following output is displayed.

kernel /Solaris_10_x86/multiboot kernel/unix 
-B install_media=192.168.2.1:/export/cdrom0/boot
module /platform/i86pc/boot_archive

You can edit this command line to customize your boot and installation. The following list describes several common commands you might want to use. For a complete list of boot arguments that you can use with the -B option, see the eeprom(1M) man page.

Note –

To add multiple arguments with the -B option, separate the arguments with a comma.

Table 9–1 x86: GRUB Menu Commands and Options

Command/Option

Description and Examples

install

Insert this option before the -B option to perform a custom JumpStart installation.

kernel /Solaris_10_x86/multiboot install 
-B install_media=192.168.2.1:/export/cdrom0/boot
module /platform/i86pc/boot_archive

url|ask

Specifies the location of the custom JumpStart files or prompts you for the location. Insert either option with the install option.

url - Specifies the path to the files. You can specify a URL for files that are located in the following places:

Local hard disk

file://jumpstart_dir_path/compressed_config_file

For example:

kernel /Solaris_10_x86/multiboot install 
file://jumpstart/config.tar 
-B install_media=192.168.2.1:/export/cdrom0/boot
module /platform/i86pc/boot_archive

NFS server

nfs://server_name:IP_address/jumpstart_dir_path/compressed_config_file

For example:

kernel /Solaris_10_x86/multiboot install 
myserver:192.168.2.1/jumpstart/config.tar 
-B install_media=192.168.2.1:/export/cdrom0/boot
module /platform/i86pc/boot_archive

HTTP server
http://server_name:IP_address/jumpstart_dir_path/ compressed_config_file&proxy_info
- If you placed a sysidcfg file in the compressed configuration file, you must specify the IP address of the server that contains the file, as in the following example:
  kernel /Solaris_10_x86/multiboot install http://192.168.2.1/jumpstart/config.tar -B install_media=192.168.2.1:/export/cdrom0/boot module /platform/i86pc/boot_archive
- If you saved the compressed configuration file on an HTTP server that is behind a firewall, you must use a proxy specifier during boot. You do not need to specify an IP address for the server that contains the file. You must specify an IP address for the proxy server, as in the following example:
  kernel /Solaris_10_x86/multiboot install http://www.shadow.com/jumpstart/config.tar&proxy=131.141.6.151 -B install_media=192.168.2.1:/export/cdrom0/boot module /platform/i86pc/boot_archive

url|ask (continued)

ask - When used with the install option, specifies that the installation program prompt you to type the location of the compressed configuration file after the system boots and connects to the network. If you use this option, you are not able to do a completely hands off JumpStart installation.

If you bypass the prompt by pressing Return, the Solaris installation program interactively configures the network parameters. The installation program then prompts you for the location of the compressed configuration file.

The following example performs a custom JumpStart and boots from a network installation image. You are prompted to input the location of the configuration file after the system connects to the network.
kernel /Solaris_10_x86/multiboot install ask -B install_media=192.168.2.1:/export/cdrom0/boot module /platform/i86pc/boot_archive

dhcp

Insert this option before the -B option to instruct the installation programs to use a DHCP server to obtain network installation information that is needed to boot the system. If you do not specify to use a DHCP server by typing dhcp, the system uses the /etc/bootparams file or the naming service bootparams database. For example, you would not specify dhcp if you wanted keep a static IP address.

kernel /Solaris_10_x86/multiboot dhcp 
-B install_media=192.168.2.1:/export/cdrom0/boot
module /platform/i86pc/boot_archive

- text

Insert this option before the -B option to perform a text-based installation in a desktop session.

kernel /Solaris_10_x86/multiboot - text 
-B install_media=192.168.2.1:/export/cdrom0/boot
module /platform/i86pc/boot_archive

- nowin

Insert this option before the -B option to perform a text-based installation in a console session.

kernel /Solaris_10_x86/multiboot - nowin 
-B install_media=192.168.2.1:/export/cdrom0/boot
module /platform/i86pc/boot_archive

console=serial-console

Use this argument with the -B option to instruct the system to use a serial console, such as ttya (COM1) or ttyb (COM2).

kernel /Solaris_10_x86/multiboot -B console=ttya 
install_media=192.168.2.1:/export/cdrom0/boot
module /platform/i86pc/boot_archive

ata-dma-enabled=[0|1]

Use this argument with the -B option to enable or disable Advanced Technology Attachment (ATA) or Integrated Drive Electronics (IDE) devices and Direct Memory Access (DMA) during the installation.

kernel /Solaris_10_x86/multiboot -B ata-dma-enabled=0 
install_media=192.168.2.1:/export/cdrom0/boot
module /platform/i86pc/boot_archive

acpi-enum=[0|1]

Use this argument with the -B option to enable or disable Advanced Configuration and Power Interface (ACPI ) power management.

kernel /Solaris_10_x86/multiboot -B acpi-enum=0 
install_media=192.168.2.1:/export/cdrom0/boot
module /platform/i86pc/boot_archive

atapi-cd-dma-enabled=[0|1]

Use this argument with the -B option to enable or disable DMA for CD or DVD drives during the installation.

kernel /Solaris_10_x86/multiboot -B atapi-cd-dma-enabled=0
install_media=192.168.2.1:/export/cdrom0/boot
module /platform/i86pc/boot_archive

Note –

The DMA name atapi is the current variable name used for DMA. This variable is subject to change.

Part II Installing Over a Local Area Network

Chapter 4 Installing From the Network (Overview)

Network Installation Introduction

Required Servers for Network Installation

Figure 4–1 Network Installation Servers

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

x86: What is PXE?

x86: Guidelines for Booting With PXE

Chapter 5 Installing From the Network With DVD Media (Tasks)

Task Map: Installing From the Network With DVD Media

Creating an Install Server With DVD Media

To Create an Install Server With SPARC or x86 DVD Media

Example 5–1 SPARC: Creating an Install Server With a DVD

Continuing the Installation

See Also

Creating a Boot Server on a Subnet With a DVD Image

To Create a Boot Server on a Subnet With a DVD Image

Example 5–2 Creating a Boot Server on a Subnet (DVD)

Continuing the Installation

See Also

Adding Systems to Be Installed From the Network With a DVD Image

To Add Systems to Be Installed From the Network With add_install_client (DVD)

Before You Begin

Example 5–3 SPARC: Adding a SPARC Install Client on a SPARC Install Server When Using DHCP (DVD)

Example 5–4 Adding an Install Client That Is On the Same Subnet As Its Server (DVD)

Example 5–5 Adding an Install Client to a Boot Server (DVD)

Example 5–6 x86: Adding a Single x86 Install Client on an x86 Install Server When Using DHCP (DVD)

Example 5–7 x86: Specifying a Serial Console to Use During a Network Installation (DVD)

Continuing the Installation

See Also

Installing the System From the Network With a DVD Image

SPARC: To Install the Client Over the Network (DVD)

Before You Begin

See Also

x86: To Install the Client Over the Network With GRUB (DVD)

Before You Begin

Next Steps

See Also

Chapter 6 Installing From the Network With CD Media (Tasks)

Task Map: Installing From the Network With CD Media

Creating an Install Server With SPARC or x86 CD Media

SPARC: To Create an Install Server With SPARC or x86 CD Media

Example 6–1 x86: Creating an Install Server With CD Media

Continuing the Installation

See Also

Creating a Boot Server on a Subnet With a CD Image

To Create a Boot Server on a Subnet With a CD Image

Example 6–2 Creating a Boot Server on a Subnet With CD Media

Continuing the Installation

See Also

Adding Systems to Be Installed From the Network With a CD Image

To Add Systems to Be Installed From the Network With add_install_client (CDs)

Before You Begin

Example 6–3 SPARC: Adding a SPARC Install Client on a SPARC Install Server When Using DHCP (CDs)

Example 6–4 Adding an Install Client That Is on the Same Subnet as Its Server (CDs)

Example 6–5 Adding an Install Client to a Boot Server (CDs)

Example 6–6 x86: Adding a Single x86 Install Client on an x86 Install Server When Using DHCP (CD)

Example 6–7 x86: Specifying a Serial Console to Use During a Network Installation (CDs)

Continuing the Installation

See Also

Installing the System From the Network With a CD Image

SPARC: To Install the Client Over the Network (CDs)

Before You Begin

See Also

x86: To Install the Client Over the Network With GRUB (CDs)

Before You Begin

Next Steps

See Also

Chapter 7 Patching the Miniroot Image (Tasks)

Patching the Miniroot Image (Tasks)

About the Miniroot Image (Overview)

How To Patch the Miniroot Image

Next Steps

Patching the Miniroot Image (Example)

Patching the Miniroot Image

How to Modify the Miniroot (Example)

Next Steps

Chapter 8 Installing Over the Network (Examples)

Network Installation Over the Same Subnet (Examples)

Example 8–1 SPARC: Install Over the Same Subnet (With DVD Media)

To Add Systems to Be Installed From the Network With `add_install_client` (DVD)

To Add Systems to Be Installed From the Network With `add_install_client` (CDs)