This part describes how to install a system that is on your local area network (LAN).
This chapter provides an introduction on how to set up your local area network and systems to install the Solaris software from the network instead of from DVD or CD media. This chapter provides overview information on the following topics.
For information on how to install a client over a wide area network, see Chapter 11, WAN Boot (Overview).
This section provides you with information you need before you can perform an installation from the network. Network installations enable you to install the Solaris software from a system, called an install server, that has access to the Solaris 10 6/06 disc images. You copy the contents of the Solaris 10 6/06 DVD or CD media to the install server's hard disk. Then, you can install the Solaris software from the network by using any of the Solaris installation methods.
To install the Solaris OS from the network, the systems to be installed require the following servers to be present on the network.
Install server – A networked system that contains the Solaris 10 6/06 disc images from which you can install Solaris 10 6/06 software on other systems on the network. You create an install server by copying the images from the following media:
Solaris DVD
Solaris Software CDs
After you copy the image from the Solaris Software CDs, you can also copy the image from the Solaris Languages CD as necessary for your installation requirements.
You can enable a single install server to provide disc images for different Solaris releases and for multiple platforms by copying the images on to the install server's hard disk. For example, a single install server could contain the disc images for the SPARC platform and x86 platform.
For details about how to create an install server, refer to one of the following sections.
Boot server – A server system that provides client systems on the same network subnet with the information that they need to boot in order to install the OS. A boot server and install server are typically the same system. However, if the system on which the Solaris 10 6/06 software is to be installed is located in a different subnet than the install server and you are not using DHCP, a boot server is required on that subnet.
A single boot server can provide Solaris 10 6/06 boot software for multiple releases, including the Solaris 10 6/06 boot software for different platforms. For example, a SPARC boot server can provide the Solaris 9 and Solaris 10 6/06 boot software for SPARC based systems. The same SPARC boot server can also provide the Solaris 10 6/06 boot software for x86 based systems.
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:
(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).
The install server and name server can be the same or different systems.
Figure 7–1 illustrates the servers that are typically used for network installation. Note that this sample network does not include a DHCP server.
This section provides an overview of the Preboot Execution Environment (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.
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.
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 Solaris 10 6/06 disc images, called an install server, to other systems on the network. You copy the contents of the Solaris 10 6/06 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:
Task Map: Preparing to Install From the Network With DVD Media
Adding Systems to Be Installed From the Network With a DVD Image
Booting and Installing the System From the Network With a DVD Image
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. | |
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) |
(Optional) Preconfigure system information. |
You can preconfigure system information to avoid being prompted for the information during the installation or upgrade. |
Chapter 6, Preconfiguring System Configuration Information (Tasks) |
Use the setup_install_server(1M) command to copy the Solaris DVD to the install server's hard disk. | ||
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. | ||
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 |
|
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. |
Booting and Installing the System From the Network With a DVD Image |
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.
If you want use the Solaris DVD media to set up an install server on a system that is running the Solaris 7 OS, you must first apply one of the following patches.
Solaris 7 SPARC Platform Edition operating environment - Patch ID 107259-03
Solaris 7 Intel Platform Edition operating environment - Patch ID 107260-03
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 for detailed information about managing removable media without the Volume Manager.
On the SPARC system that is to become the install server, become superuser.
The system must include a DVD-ROM drive and be part of the site's network and name service. If you use a name service, the system must already be in a service, such as NIS, NIS+, DNS, or LDAP. If you do not use a name service, you must distribute information about this system by following your site's policies.
Insert the Solaris DVD in the SPARC system's drive.
Create a directory to contain the DVD image.
# mkdir -p install_dir_path |
Change to the Tools directory on the mounted disc.
For SPARC DVD media, type:
# cd /cdrom/cdrom0/s0/Solaris_10/Tools |
For x86 DVD media, type:
# cd /cdrom/cdrom0/Solaris_10/Tools |
In the previous examples, cdrom0 is the path to the drive that contains the Solaris OS DVD media.
Copy the DVD image in the drive to the install server's hard disk.
# ./setup_install_server install_dir_path |
Specifies the directory where the DVD image is to be copied
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.
Verify that the path to the install server's image is shared appropriately.
# share | grep 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.
Make the install server available to the boot server by adding this entry to the /etc/dfs/dfstab file.
share -F nfs -o ro,anon=0 -d "install server directory" install_dir_path |
Verify that the nfsd daemon is running.
If the install server is running the Solaris 10 6/06 OS, 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 |
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 SPARC based installation images, use the patchadd-c command to patch the files that are located in the miniroot.
# patchadd -C install_dir_path path-to-patch/patch-id |
Specifies the path to the network installation miniroot.
Specifies the path to the patch that you want to add, for example, /var/sadm/spool.
Specifies the patch ID that you want to apply.
Don't use the patchadd -C command unless you have read the Patch README instructions or have contacted your local Sun support office.
For x86 based installation images, follow these steps to patch an x86 network installation miniroot.
These steps assume that you have a system on your network that is running the Solaris 10 6/06 for x86 release, and that system is accessible over the network.
On a system that is running the Solaris 10 6/06 for x86 release, log in as superuser.
Change to the Tools directory of the installation image you created in Step 5.
# cd install-server-path/install-dir-path/Solaris_10/Tools |
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 Solaris 10 6/06 for x86 release.
# ./setup_install_server remote_install_dir_path |
Specifies the path on the Solaris 10 6/06 for x86 system in which to create the new installation image.
This command creates a new installation image on the Solaris 10 6/06 for x86 system. In order to patch this image, you must temporarily place this image on a system that is running the Solaris 10 6/06 for x86 release.
On the Solaris 10 6/06 for x86 system, unpack the network installation boot archive.
# /boot/solaris/bin/root_archive unpackmedia remote_install_dir_path \ destination_dir |
Specifies the path to the x86 network installation image on the Solaris 10 6/06 for x86 system.
Specifies the path to the directory to contain the unpacked boot archive.
On the Solaris 10 6/06 for x86 system, patch the unpacked boot archive.
# patchadd -C destination_dir path-to-patch/patch-id |
Specifies the path to the patch that you want to add, for example, /var/sadm/spool.
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).
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 Solaris 10 6/06 for x86 system, pack the x86 boot archive.
# /boot/solaris/bin/root_archive packmedia destination_dir \ remote_install_dir_path |
Copy the patched miniroot to the installation image on the install server.
# cp remote_install_dir_path/boot/x86.miniroot \ install-server-path/install_dir_path/boot/x86.miniroot |
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.
The following example illustrates how to create an install server by copying the Solaris DVD to the install server's /export/home/dvdsparc directory. This example assumes that the install server is running the Solaris 10 6/06 OS.
# mkdir -p /export/home/dvdsparc # cd /cdrom/cdrom0/s0/Solaris_10/Tools # ./setup_install_server /export/home/dvdsparc |
If you need a separate boot server, type these commands:
Add the following path 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 / |
The following example illustrates how to create an install server by copying the Solaris DVD to the install server's /export/home/dvdx86 directory. This example assumes that the install server is running the Solaris 10 6/06 OS.
# mkdir -p /export/home/dvdx86 # cd /cdrom/cdrom0/Solaris_10/Tools # ./setup_install_server /export/home/dvdx86 |
Add the following path to the /etc/dfs/dfstab file:
share -F nfs -o ro,anon=0 -d "install server directory" /export/home/dvdx86 |
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 / |
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.
For additional information about the setup_install_server and the add_to_install_server commands, see install_scripts(1M).
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 for detailed information about managing removable media without the Volume Manager.
On the x86 system that is to become the install server, become superuser.
The system must include a DVD-ROM drive and be part of the site's network and name service. If you use a name service, the system must also be in the NIS, NIS+, DNS, or LDAP name service. If you do not use a name service, you must distribute information about this system by following your site's policies.
Insert the Solaris DVD into the system's drive.
Create a directory to contain the boot image.
# mkdir -p 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 |
In the previous example, cdrom0 is the path to the drive that contains the Solaris OS DVD media.
Copy the disc in the drive to the install server's hard disk by using the setup_install_server command:
# ./setup_install_server install_dir_path |
Specifies the directory where the DVD image is to be copied
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.
Verify that the path to the install server's image is shared appropriately.
# share | grep install_dir_path |
Specifies 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.
Make the install server available to the boot server by adding this entry to the /etc/dfs/dfstab file.
share -F nfs -o ro,anon=0 -d "install server directory" install_dir_path |
Verify that the nfsd daemon is running.
If the install server is running the Solaris 10 6/06 OS, 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 |
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.
For SPARC based installation images, use the patchadd -C command to patch the files that are located in the miniroot.
# patchadd -C install_dir_path path-to-patch/patch-id |
Specifies the path to the network installation miniroot.
Specifies the path to the patch that you want to add, for example, /var/sadm/spool.
Specifies the patch ID that you want to apply.
Don't use the patchadd -C command unless you have read the Patch README instructions or have contacted your local Sun support office.
For x86 based installation images, follow these steps to patch an x86 network installation miniroot.
If the installation server is not running the Solaris 10 6/06 for x86 release, log in as superuser to another system on the network that is running the Solaris 10 6/06 for x86 release.
To patch a Solaris 10 6/06 for x86 miniroot, your system must be running the Solaris 10 6/06 for x86 release.
If your installation server is running the Solaris 10 6/06 for x86 release, go to Step d.
Change to the Tools directory of the installation image you created in Step 5.
# cd install-server-path/install-dir-path/Solaris_10/Tools |
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 Solaris 10 6/06 for x86 release.
# ./setup_install_server remote_install_dir_path |
Specifies the path on the Solaris 10 6/06 for x86 system in which to create the new installation image.
This command creates a new installation image on the Solaris 10 6/06 for x86 system. In order to patch this image, you must temporarily place this image on a system that is running the Solaris 10 6/06 for x86 release.
Unpack the network installation boot archive.
# /boot/solaris/bin/root_archive unpackmedia install_dir_path \ destination_dir |
Specifies the path to the x86 network installation image. If you created a new installation image in Step c, specify the path to the new image on the Solaris 10 6/06 for x86 system.
Specifies the path to the directory to contain the unpacked boot archive.
Patch the unpacked boot archive.
# patchadd -C destination_dir path-to-patch/patch-id |
Specifies the path to the patch that you want to add, for example, /var/sadm/spool.
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).
Don't use the patchadd -C command unless you have read the Patch README instructions or have contacted your local Sun support office.
Pack the x86 boot archive.
# /boot/solaris/bin/root_archive packmedia destination_dir \ install_dir_path |
If necessary, copy the patched miniroot to the installation image on the install server.
If you patched the miniroot on a remote Solaris 10 6/06 for x86 system, you must copy the patched miniroot to the install server.
# cp remote_install_dir_path/boot/x86.miniroot \ install-server-path/install_dir_path/boot/x86.miniroot |
Decide if you need to create a boot server.
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. See Adding Systems to Be Installed From the Network With a DVD Image.
If the install server is not on the same subnet as the system to be installed and you are not using DHCP, you must create a boot server. For detailed instructions on how to create a boot server, refer to Creating a Boot Server on a Subnet With a DVD Image.
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. This example assumes that the install server is running the Solaris 10 6/06 OS.
Set up the installation server.
# mkdir -p /export/home/dvdx86 # cd /cdrom/cdrom0/Solaris_10/Tools # ./setup_install_server /export/home/dvdx86 |
Add the following path to the /etc/dfs/dfstab file:
share -F nfs -o ro,anon=0 -d "install server directory" /export/home/dvdx86 |
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 / |
The following example illustrates how to create an x86 install server by copying the Solaris Operating System for SPARC Platforms DVD to the install server's /export/home/dvdsparc directory. This example assumes that the install server is running the Solaris 10 6/06 OS.
# mkdir -p /export/home/dvdscparc # cd /cdrom/cdrom0/Solaris_10/Tools # ./setup_install_server /export/home/dvdsparc |
Add the following path 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 / |
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 CD Image.
For additional information about the setup_install_server and the add_to_install_server commands, see install_scripts(1M).
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.
On the system you intend to make the boot server for the subnet, log in and become superuser.
The system must have access to a remote Solaris 10 6/06 disc image, which is normally the install server. If you use a name service, the system should also be in a name service. If you do not use a name 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 |
Is the install server name and absolute path to the disc image
Create a directory for the boot image.
# mkdir -p 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 |
Specifies to set up the system as a boot server
Specifies the directory where the boot software is to be copied
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.
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 |
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.
For additional information about the setup_install_server command, see install_scripts(1M).
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 name 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 8–6.
If your install server and client are on the same subnet, see Example 8–7.
If your install server and your client are not on the same subnet and you are not using DHCP, see Example 8–8.
If you are using DHCP to set installation parameters for x86 clients, see Example 8–9.
If you want to use a specific serial port to display output during the installation of an x86 based system, see Example 8–10.
For more options to use with this command, see the man page, add_install_client(1M).
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.
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 name 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.
If you use the NIS, NIS+, DNS, or LDAP name service, verify that the following information about the system to be installed has been added to the name service.
Host name
IP address
Ethernet address
For more information on name services, see System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP).
Change to the Tools directory on the Solaris DVD image:
# cd /install_dir_path/Solaris_10/Tools |
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 |
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.
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.
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.
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.
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 Solaris 10 6/06 net installation image, CD, or DVD.
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.
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 Solaris 10 6/06 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.
Is the name of the system to be installed from the network. This name is not the host name of the install server.
Is the platform group of the system to be installed. For more information, see Platform Names and Groups.
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 UltraTM 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 |
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 |
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 |
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).
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.
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.
For additional information about the add_install_client command, see install_scripts(1M).
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 Boot the Client Over the Network (DVD) for instructions about how to boot and install SPARC based systems over the network.
See x86: To Boot the Client Over the Network With GRUB (DVD) for instructions about how to boot and install x86 based systems over the network.
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 SPARC: To Create a SPARC 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.
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 name service to preconfigure system information. For information about how to preconfigure information with a name service, see Preconfiguring With the Name 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 6, Preparing Custom JumpStart Installations (Tasks), in Solaris 10 6/06 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 - install |
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 6, Preconfiguring System Configuration Information (Tasks) for more information.
If you did not preconfigure all the system information, use the Checklist for Installation to help you answer the configuration questions.
If you are using the GUI, after you confirm the system configuration information, the Welcome to Solaris dialog box 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 6, Preconfiguring System Configuration Information (Tasks) for more information.
If you did not preconfigure all the installation options, use the Checklist for Installation to help you answer the installation questions.
If you are upgrading a system that has non-global zones installed, follow these steps.
When you are prompted to select initial installation or upgrade, choose Upgrade. Click Next.
If your system has multiple root (/) partitions, select the partition that you want to upgrade on the Select Version to Upgrade panel.
The Solaris installation program displays a message that indicates that you cannot customize your upgrade. The Solaris installation program analyzes your system to determine if the system can be upgraded. The Ready to Upgrade panel is displayed.
If your system has only one root partition, the Solaris installation program does not prompt you to select a partition to upgrade. The partition is automatically selected.
If you want to continue the upgrade, click Install Now on the Ready to Upgrade panel.
The Solaris installation program begins to upgrade your system.
If you do not want to continue the upgrade, click Back to perform an initial installation.
For information about how to complete an interactive installation with the Solaris installation GUI, see To Install or Upgrade With the Solaris Installation Program With GRUB in Solaris 10 6/06 Installation Guide: Basic Installations.
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 4, x86: GRUB Based Booting For Solaris Installation.
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.
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 x86: To Create an x86 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.
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 name service to preconfigure system information. For information about how to preconfigure information with a name service, see Preconfiguring With the Name 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 6, Preparing Custom JumpStart Installations (Tasks), in Solaris 10 6/06 Installation Guide: Custom JumpStart and Advanced Installations.
This procedure also assumes that your system can boot from the network.
If you are upgrading a system that has non-global zones installed, you cannot customize your upgrade.
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.
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 6/06 /sol_10_x86 | | | | | +-------------------------------------------------------------------------+ 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 x86: To Create an x86 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).
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/sol_10_x86/boot \ module /platform/i86pc/boot_archive |
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.
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 10–1.
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.
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.
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 6/06 Installation Guide: Custom JumpStart and Advanced Installations.
For detailed information about the Solaris installation GUI and text installer, see System Requirements and Recommendations.
The system configures the devices and interfaces, and searches for configuration files. The kdmconfig utility detects the drivers that are necessary to configure the keyboard, display, and mouse on your system. 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 6, Preconfiguring System Configuration Information (Tasks) for more information.
If you did not preconfigure all the system information, use the Checklist for Installation to help you answer the configuration questions.
If you are using the installation GUI, after you confirm the system configuration information, the Welcome to Solaris dialog box 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 6, Preconfiguring System Configuration Information (Tasks) for more information.
If you did not preconfigure all the installation options, use the Checklist for Installation to help you answer the installation questions.
If you are upgrading a system that has non-global zones installed, follow these steps.
When you are prompted to select initial installation or upgrade, choose Upgrade. Click Next.
If your system has multiple root (/) partitions, select the partition that you want to upgrade on the Select Version to Upgrade panel.
The Solaris installation program displays a message that indicates that you cannot customize your upgrade. The Solaris installation program analyzes your system to determine if the system can be upgraded. The Ready to Upgrade panel is displayed.
If your system has only one root partition, the Solaris installation program does not prompt you to select a partition to upgrade. The partition is automatically selected.
If you want to continue the upgrade, click Install Now on the Ready to Upgrade panel.
The Solaris installation program begins to upgrade your system.
If you do not want to continue the upgrade, click Back to perform an initial installation.
After the system boots and installs over the network, instruct the system to boot from the disk drive on subsequent boots.
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 the Solaris Boot Behavior by Editing the GRUB Menu in System Administration Guide: Basic Administration.
For information about how to complete an interactive installation with the Solaris installation GUI, see To Install or Upgrade With the Solaris Installation Program With GRUB in Solaris 10 6/06 Installation Guide: Basic Installations.
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 Solaris 10 6/06 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:
Task Map: Preparing to Install From the Network With CD Media
Adding Systems to Be Installed From the Network With a CD Image
Booting and Installing the System From the Network With a CD Image
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. | |
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) |
(Optional) Preconfigure system information. |
You can preconfigure system information to avoid being prompted for the information during the installation or upgrade. |
Chapter 6, Preconfiguring System Configuration Information (Tasks) |
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 CD to the install server's hard disk. | ||
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. | ||
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 |
|
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. |
Booting and Installing the System From the Network With a CD Image |
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 separate 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 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.
Use this procedure to create a SPARC install server with SPARC or x86 CD media.
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 for detailed information about managing removable media without the Volume Manager.
If you want to upgrade a system that has non-global zones installed, you cannot use a CD-based network installation image to upgrade the system. You must create a network installation image from the Solaris DVD. For instructions about how to create a network installation image from a DVD, see Chapter 8, Preparing to Install From the Network With DVD Media (Tasks).
On the system that is to become the install server, become superuser.
The system must include a CD-ROM drive and be part of the site's network and name service. If you use a name service, the system must already be in a name service, such as NIS, NIS+, DNS, or LDAP. If you do not use a name 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 |
Specifies the directory where the CD image is to be copied
Change to the Tools directory on the mounted disc.
If you are creating an installation image from the Solaris Software for SPARC Platforms - 1 CD, type the following command.
# cd /cdrom/cdrom0/s0/Solaris_10/Tools |
If you are creating an installation image from the Solaris Software for x86 Platforms - 1 CD, type the following command.
# cd /cdrom/cdrom0/Solaris_10/Tools |
In the previous examples, cdrom0 is the path to the drive that contains the Solaris OS CD media.
Copy the image in the drive to the install server's hard disk.
# ./setup_install_server install_dir_path |
Specifies the directory where the CD image is to be copied
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.
Verify that the path to the install server's image is shared appropriately.
# share | grep 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.
Make the install server available by adding this entry to the /etc/dfs/dfstab file.
share -F nfs -o ro,anon=0 -d "install server directory" install_dir_path |
Verify that the nfsd daemon is running.
If the install server is running the Solaris 10 6/06 OS, 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 |
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.
If you are creating an installation image from the Solaris Software for SPARC Platforms - 1 CD, type the following command.
# cd /cdrom/cdrom0/s0/Solaris_10/Tools |
If you are creating an installation image from the Solaris Software for x86 Platforms - 1 CD, type the following command.
# cd /cdrom/cdrom0/Solaris_10/Tools |
In the previous examples, cdrom0 is the path to the drive that contains the Solaris OS CD media.
Copy the CD in the CD-ROM drive to the install server's hard disk.
# ./add_to_install_server 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 Solaris Languages CD in the system's CD-ROM drive.
Change to the Tools directory on the mounted CD.
# cd /cdrom/cdrom0/Tools |
Copy the CD in the CD-ROM drive to the install server's hard disk.
# ./add_to_install_server install_dir_path |
Specifies the directory where the CD image is to be copied
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 SPARC based installation images, use the patchadd -C command to patch the files that are located in the miniroot.
# patchadd -C install_dir_path path-to-patch/patch-id |
Specifies the path to the network installation miniroot.
Specifies the path to the patch that you want to add, for example, /var/sadm/spool.
Specifies the patch ID that you want to apply.
Don't use the patchadd -C command unless you have read the Patch README instructions or have contacted your local Sun support office.
For x86 based installation images, follow these steps to patch an x86 network installation miniroot.
These steps assume that you have a system on your network that is running the Solaris 10 6/06 for x86 release, and that system is accessible over the network.
On a system that is running the Solaris 10 6/06 for x86 release, log in as superuser.
Change to the Tools directory of the installation image you created in Step 4.
# cd install-server-path/install-dir-path/Solaris_10/Tools |
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 Solaris 10 6/06 for x86 release.
# ./setup_install_server remote_install_dir_path |
Specifies the path on the Solaris 10 6/06 for x86 system in which to create the new installation image.
This command creates a new installation image on the Solaris 10 6/06 for x86 system. In order to patch this image, you must temporarily place this image on a system that is running the Solaris 10 6/06 for x86 release.
On the Solaris 10 6/06 for x86 system, unpack the network installation boot archive.
# /boot/solaris/bin/root_archive unpackmedia remote_install_dir_path \ destination_dir |
Specifies the path to the x86 network installation image on the Solaris 10 6/06 for x86 system.
Specifies the path to the directory to contain the unpacked boot archive.
On the Solaris 10 6/06 for x86 system, patch the unpacked boot archive.
# patchadd -C destination_dir path-to-patch/patch-id |
Specifies the path to the patch that you want to add, for example, /var/sadm/spool.
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).
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 Solaris 10 6/06 for x86 system, pack the x86 boot archive.
# /boot/solaris/bin/root_archive packmedia destination_dir \ remote_install_dir_path |
Copy the patched miniroot to the installation image on the install server.
# cp remote_install_dir_path/boot/x86.miniroot \ install-server-path/install_dir_path/boot/x86.miniroot |
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.
The following example illustrates how to create an install server by copying the following CDs to the install server's /export/home/cdsparc directory. This example assumes that the install server is running the Solaris 10 6/06 OS.
Solaris Software for SPARC Platforms CDs
Solaris Languages for SPARC Platforms CD
Insert the Solaris Software for SPARC Platforms - 1 CD in the system's CD-ROM drive.
# mkdir -p /export/home/cdsparc # cd /cdrom/cdrom0/s0/Solaris_10/Tools # ./setup_install_server /export/home/cdsparc |
If you have a separate boot server, add these steps.
Add the following path to the /etc/dfs/dfstab file.
share -F nfs -o ro,anon=0 -d "install server directory" \ /export/home/cdsparc |
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 |
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 for SPARC Platforms - 1 CD. Insert the Solaris Software for SPARC Platforms - 2 CD in the CD-ROM drive.
# cd /cdrom/cdrom0/Solaris_10/Tools # ./add_to_install_server /export/home/cdsparc # cd / |
Repeat the previous commands for each Solaris Software CD that you want to install.
Insert the Solaris Languages for SPARC Platforms CD in the CD-ROM drive.
# cd /cdrom/cdrom0/Tools # ./add_to_install_server /export/home/cdsparc |
Use the following example to create an x86 network installation image on a SPARC based install server. The following example illustrates how to create a cross platform install server by copying the Solaris Software for x86 Platforms CDs to the install server's /export/home/cdx86 directory. This example assumes that the install server is running the Solaris 10 6/06 OS.
Solaris Software for x86 Platforms CDs
Solaris Languages for x86 Platforms CD
Insert the Solaris Software for x86 Platforms - 1 CD in the system's CD-ROM drive.
# mkdir -p /export/home/cdsparc # cd /cdrom/cdrom0/Solaris_10/Tools # ./setup_install_server /export/home/cdsparc |
If you have a separate boot server, add these steps.
Add the following path to the /etc/dfs/dfstab file.
share -F nfs -o ro,anon=0 -d "install server directory" \ /export/home/cdsparc |
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 |
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 for x86 Platforms - 1 CD. Insert the Solaris Software for x86 Platforms - 2 CD in the CD-ROM drive.
# cd /cdrom/cdrom0/Solaris_10/Tools # ./add_to_install_server /export/home/cdsparc # cd / |
Repeat the previous commands for each Solaris Software for x86 Platforms CD that you want to install.
Insert the Solaris Languages for x86 Platforms CD in the CD-ROM drive.
# cd /cdrom/cdrom0/Tools # ./add_to_install_server /export/home/cdsparc |
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.
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 CD Image.
For additional information about the setup_install_server and the add_to_install_server commands, see install_scripts(1M).
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 separate 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 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.
This procedure creates an x86 install server with x86 CD media.
If you want to create a SPARC network installation image, see SPARC: To Create a SPARC Install Server With SPARC or x86 CD Media.
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 for detailed information about managing removable media without the Volume Manager.
If you want to upgrade a system that has non-global zones installed, you cannot use a CD-based network installation image to upgrade the system. You must create a network installation image from the Solaris DVD. For instructions about how to create a network installation image from a DVD, see Chapter 8, Preparing to Install From the Network With DVD Media (Tasks).
On the system that is to become the install server, become superuser.
The system must include a CD-ROM drive and be part of the site's network and name service. If you use a name service, the system must already be in a name service, such as NIS, NIS+, DNS, or LDAP. If you do not use a name 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 |
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 |
In the previous example, cdrom0 is the path to the drive that contains the Solaris OS CD media.
Copy the image in the drive to the install server's hard disk.
# ./setup_install_server install_dir_path |
Specifies the directory where the CD image is to be copied
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.
Verify that the path to the install server's image is shared appropriately.
# share | grep 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.
Make the install server available by adding this entry to the /etc/dfs/dfstab file.
share -F nfs -o ro,anon=0 -d "install server directory" install_dir_path |
Verify that the nfsd daemon is running.
If the install server is running the Solaris 10 6/06 OS, 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 |
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 |
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 Solaris Languages CD in the system's CD-ROM drive.
Change to the Tools directory on the mounted CD:
# cd /cdrom/cdrom0/Tools |
Copy the CD in the CD-ROM drive to the install server's hard disk.
# ./add_to_install_server install_dir_path |
Specifies the directory where the CD image is to be copied
Change directories to root (/).
# cd / |
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. Follow these substeps to patch an x86 network installation miniroot.
If the installation server is not running the Solaris 10 6/06 for x86 release, log in as superuser to another system on the network that is running the Solaris 10 6/06 for x86 release.
To patch a Solaris 10 6/06 for x86 miniroot, your system must be running the Solaris 10 6/06 for x86 release.
Change to the Tools directory of the installation image you created in Step 5.
# cd install-server-path/install-dir-path/Solaris_10/Tools |
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 Solaris 10 6/06 for x86 release.
# ./setup_install_server remote_install_dir_path |
Specifies the path on the Solaris 10 6/06 for x86 system in which to create the new installation image.
This command creates a new installation image on the Solaris 10 6/06 for x86 system. In order to patch this image, you must temporarily place this image on a system that is running the Solaris 10 6/06 for x86 release.
Unpack the network installation boot archive.
# /boot/solaris/bin/root_archive unpackmedia install_dir_path \ destination_dir |
Specifies the path to the x86 network installation image.
Specifies the path to the directory to contain the unpacked boot archive.
Patch the unpacked boot archive.
# patchadd -C destination_dir path-to-patch/patch-id |
Specifies the path to the patch that you want to add, for example, /var/sadm/spool.
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).
Don't use the patchadd -C command unless you have read the Patch README instructions or have contacted your local Sun support office.
Pack the x86 boot archive.
# /boot/solaris/bin/root_archive packmedia destination_dir \ install_dir_path |
If necessary, copy the patched miniroot to the installation image on the install server.
If you patched the miniroot on a remote Solaris 10 6/06 6/06 for x86 system, you must copy the patched miniroot to the install server.
# cp remote_install_dir_path/boot/x86.miniroot \ install-server-path/install_dir_path/boot/x86.miniroot |
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.
The following examples illustrate how to create an install server by copying the following CDs to the install server's /export/home/cdx86 directory. This example assumes that the install server is running the Solaris 10 6/06 OS.
Solaris Software for x86 Platforms CDs
Solaris Languages for x86 Platforms CD
Insert the Solaris Software for x86 Platforms - 1 CD in the system's CD-ROM drive.
Set up an install server.
# mkdir -p /export/home/dvdx86 # cd /cdrom/cdrom0/Solaris_10/Tools # ./setup_install_server /export/home/cdx86 |
If you have a separate boot server, add these steps.
Add the following path to the /etc/dfs/dfstab file:
share -F nfs -o ro,anon=0 -d "install server directory" \ /export/home/cdx86 |
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 |
Continue with the following steps.
If you do not need a boot server or have completed the steps for a separate boot server, continue with the following steps.
# cd / |
Eject the Solaris Software for x86 Platforms - 1 CD. Insert the Solaris Software for x86 Platforms - 2 CD in the CD-ROM drive.
# cd /cdrom/cdrom0/Solaris_10/Tools # ./add_to_install_server /export/home/cdx86 # cd / |
Repeat the previous commands for each Solaris Software CD that you want to install.
Insert the Solaris Languages for x86 Platforms CD in the CD-ROM drive.
# cd /cdrom/cdrom0/Tools # ./add_to_install_server /export/home/cdx86 |
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.
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 CD Image.
For additional information about the setup_install_server and the add_to_install_server commands, see install_scripts(1M).
This section explains how to create an x86 network installation image on a SPARC system.
A remote x86 system is not required to create a SPARC install server with x86 CD media. See SPARC: To Create a SPARC Install Server With SPARC or x86 CD Media for more information.
Use this procedure to create a SPARC install server on an x86 system with SPARC CD media.
In this procedure, x86-system is the x86 system that is to be the install server and remote-SPARC-system is the remote SPARC system to be used with the SPARC CD media.
You need the following items to perform this task.
An x86 system
A SPARC system with a CD-ROM drive
A set of CDs for the remote SPARC system
Solaris Software for SPARC Platforms CDs
Solaris Languages for SPARC Platforms CD
If you want to upgrade a system that has non-global zones installed, you cannot use a CD-based network installation image to upgrade the system. You must create a network installation image from the Solaris DVD. For instructions about how to create a network installation image from a DVD, see Chapter 8, Preparing to Install From the Network With DVD Media (Tasks).
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 for detailed information about managing removable media without the Volume Manager.
On the remote SPARC system, become superuser.
The system must include a CD-ROM drive and be part of the site's network and name service. If you use a name service, the system must also be in the NIS, NIS+, DNS, or LDAP name service. If you do not use a name service, you must distribute information about this system by following your site's policies.
On the remote SPARC system, insert the Solaris Software for SPARC Platforms - 1 CD into the system's drive.
On the remote SPARC system, add the following entries to the /etc/dfs/dfstab file.
share -F nfs -o ro,anon=0 /cdrom/cdrom0/s0 share -F nfs -o ro,anon=0 /cdrom/cdrom0/s1 |
On the remote SPARC system, start the NFS daemon.
If the install server is running the Solaris 10 6/06 OS, or compatible version, type the following command.
remote-SPARC-system# svcadm enable svc:/network/nfs/server |
If the install server is running the Solaris 9 OS, or compatible version, type the following command.
remote-SPARC-system# /etc/init.d/nfs.server start |
On the remote SPARC system, verify that the CD is available to other systems by using the share command.
remote-SPARC-system# share - /cdrom/cdrom0/sol_10_sparc/s0 ro,anon=0 " " - /cdrom/cdrom0/sol_10_sparc/s1 ro,anon=0 " " |
In the previous sample output, sol_10_sparc refers to the Solaris 10 6/06 OS on SPARC based systems. This text string varies for each version of the Solaris OS.
On the x86 system that is to be the SPARC install server, become superuser.
Verify that the CD is properly exported on the remote x86 system.
x86-system# showmount -e remote-SPARC-system export list for remote-SPARC-system: /cdrom/sol_10_sparc/s0 (everyone) /cdrom/sol_10_sparc/s1 (everyone) |
On the x86 system, change to the Tools directory on the mounted disc:
x86-system# cd /net/remote-SPARC-system/cdrom/sol_10_sparc/s0/Solaris_10/Tools |
On the x86 system, copy the disc in the drive to the install server's hard disk in the directory you've created by using the setup_install_server command:
x86-system# ./setup_install_server install_dir_path |
Specifies the directory where the disc image is to be copied. The directory must be empty.
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.
On the x86 system, change to the top directory.
x86-system# cd / |
On the x86 system, unmount both directories.
x86-system# umount /net/remote-SPARC-system/cdrom/sol_10_sparc/s0 |
On the SPARC system, unshare both CD-ROM slices.
remote-SPARC-system# unshare /cdrom/cdrom0/s0 |
remote-SPARC-system# unshare /cdrom/cdrom0/ |
On the SPARC system, eject the Solaris Software for SPARC Platforms - 1 CD.
Insert the Solaris Software for SPARC Platforms - 2 CD into the x86 system's CD-ROM drive.
On the x86 system, change to the Tools directory on the mounted CD:
x86-system# cd /cdrom/cdrom0/Solaris_10/Tools |
On the x86 system, copy the CD to the install server's hard disk:
x86-system# ./add_to_install_server install_dir_path |
Specifies the directory where the CD image is to be copied
Eject the Solaris Software for SPARC Platforms - 2 CD.
Repeat Step 14 through Step 17 for each Solaris Software CD you want to install.
On the x86 system, insert the Solaris Languages for SPARC Platforms CD into the x86 system's CD-ROM drive and mount the CD.
On the x86 system, change to the Tools directory on the mounted CD:
x86-system# cd /cdrom/cdrom0/Tools |
On the x86 system, copy the CD to the install server's hard disk:
x86-system# ./add_to_install_server install_dir_path |
Specifies the directory where the CD image is to be copied
Decide if you want to patch the files that are located in the miniroot (Solaris_10/Tools/Boot) on the net install image that was created by setup_install_server.
Decide if you need to create a boot server.
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. See Adding Systems to Be Installed From the Network With a CD Image.
If the install server is not on the same subnet as the system to be installed and you are not using DHCP, you must create a boot server. For detailed instructions on how to create a boot server, refer to To Create a Boot Server on a Subnet With a CD Image.
The following example illustrates how to create a SPARC install server on an x86 system that is named richards. The following SPARC CDs are copied from a remote SPARC system that is named simpson to the x86 install server's /export/home/cdsparc directory.
Solaris Software for SPARC Platforms CDs
Solaris Languages for SPARC Platforms CD
This example assumes that the install server is running the Solaris 10 6/06 OS.
On the remote SPARC system, insert the Solaris Software for SPARC Platforms - 1 CD, then type the following commands:
simpson (remote-SPARC-system)# share -F nfs -o ro,anon=0 /cdrom/cdrom0/s0 simpson (remote-SPARC-system)# share -F nfs -o ro,anon=0 /cdrom/cdrom0/s1 simpson (remote-SPARC-system)# svcadm enable svc:/network/nfs/server |
On the x86 system:
richards (x86-system)# cd /net/simpson/cdrom/sol_10_sparc/s0//Solaris_10/Tools richards (x86-system)# ./setup_install_server /export/home/cdsparc richards (x86-system)# cd / richards (x86-system)# umount /net/simpson/cdrom/sol_10_sparc/s0/ |
On the remote SPARC system:
simpson (remote-SPARC-system) unshare /cdrom/cdrom0/s0 simpson (remote-SPARC-system) unshare /cdrom/cdrom0/s1 |
On the x86 system:
richards (x86-system)# cd /cdrom/cdrom0/Solaris_10/Tools richards (x86-system)# ./add_to_install_server /export/home/cdsparc |
Repeat the previous commands for each Solaris Software for x86 Platforms CD that you want to install.
richards (x86-system)# cd /cdrom/cdrom0/Tools richards (x86-system)# ./add_to_install_server /export/home/cdsparc |
In this example, each CD is inserted and automatically mounted before each of the commands. After each command, the CD is removed.
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.
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 CD Image.
For additional information about the setup_install_server and the add_to_install_server commands, see install_scripts(1M).
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 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.
On the system you intend to make the boot server for the subnet, log in and become superuser.
The system must include a local CD-ROM drive or have access to the remote Solaris 10 6/06 disc images, which are normally on the install server. If you use a name service, the system should be in the name service. If you do not use a name 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 |
Is the install server name and absolute path to the disc image
Create a directory for the boot image.
# mkdir -p 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 |
Specifies to set up the system as a boot server
Specifies the directory where the boot software is to be copied
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 |
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.
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 CD Image.
For additional information about the setup_install_server command, see install_scripts(1M).
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 name 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).
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.
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 name 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.
If you use the NIS, NIS+, DNS, or LDAP name service, verify that the following information about the system to be installed has been added to the name service:
Host name
IP address
Ethernet address
For more information on name services, see System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP).
Change to the Tools directory on the Solaris 10 6/06 CD image on the install server:
# cd /install_dir_path/Solaris_10/Tools |
Specifies the path to the Tools directory
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 |
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.
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 10 6/06 CD image
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.
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.
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 Solaris 10 6/06 net installation image, CD, or DVD.
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.
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 Solaris 10 6/06 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.
Is the name of the system to be installed from the network. This name is not the host name of the install server.
Is the platform group of the system to be installed. A detailed list of platform groups appears in Platform Names and Groups.
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 |
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 |
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 10 6/06 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 |
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).
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.
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.
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.
For additional information about the add_install_client command, see install_scripts(1M).
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 Boot the Client Over the Network (CDs) for instructions about how to boot and install SPARC based systems over the network.
See x86: To Boot the Client Over the Network With GRUB (CDs) for instructions about how to boot and install x86 based systems over the network.
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 a SPARC 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.
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 name service to preconfigure system information. For information about how to preconfigure information with a name service, see Preconfiguring With the Name 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 6, Preparing Custom JumpStart Installations (Tasks), in Solaris 10 6/06 Installation Guide: Custom JumpStart and Advanced Installations.
If you want to upgrade a system that has non-global zones installed, you cannot use a CD-based network installation image to upgrade the system. You must create a network installation image from the Solaris DVD. For instructions about how to create a network installation image from a DVD, see Chapter 8, Preparing to Install From the Network With DVD Media (Tasks).
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 - install |
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 6, Preconfiguring System Configuration Information (Tasks) for more information.
If you did not preconfigure all the system information, use the Checklist for Installation to help you answer the configuration questions.
If you are using the GUI, after you confirm the system configuration information, the Welcome to Solaris dialog box 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 6, Preconfiguring System Configuration Information (Tasks) for more information.
If you did not preconfigure all the installation options, use the Checklist for Installation to help you answer the installation questions.
If you are upgrading a system that has non-global zones installed, follow these steps.
When you are prompted to select initial installation or upgrade, choose Upgrade. Click Next.
If your system has multiple root (/) partitions, select the partition that you want to upgrade on the Select Version to Upgrade panel.
The Solaris installation program displays a message that indicates that you cannot customize your upgrade. The Solaris installation program analyzes your system to determine if the system can be upgraded. The Ready to Upgrade panel is displayed.
If your system has only one root partition, the Solaris installation program does not prompt you to select a partition to upgrade. The partition is automatically selected.
If you want to continue the upgrade, click Install Now on the Ready to Upgrade panel.
The Solaris installation program begins to upgrade your system.
If you do not want to continue the upgrade, click Back to perform an initial installation.
For information about how to complete an interactive installation with the Solaris installation GUI, see To Install or Upgrade With the Solaris Installation Program With GRUB in Solaris 10 6/06 Installation Guide: Basic Installations.
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 4, x86: GRUB Based Booting For Solaris Installation.
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.
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 x86: To Create an x86 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.
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 name service to preconfigure system information. For information about how to preconfigure information with a name service, see Preconfiguring With the Name 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 6, Preparing Custom JumpStart Installations (Tasks), in Solaris 10 6/06 Installation Guide: Custom JumpStart and Advanced Installations.
This procedure also assumes that your system can boot from the network.
If you want to upgrade a system that has non-global zones installed, you cannot use a CD-based network installation image to upgrade the system. You must create a network installation image from the Solaris DVD. For instructions about how to create a network installation image from a DVD, see Chapter 8, Preparing to Install From the Network With DVD Media (Tasks).
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.
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 6/06 /sol_10_x86 | | | | | +-------------------------------------------------------------------------+ 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 x86: To Create an x86 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).
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/sol_10_x86/boot \ module /platform/i86pc/boot_archive |
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.
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 10–1.
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.
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.
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 6/06 Installation Guide: Custom JumpStart and Advanced Installations.
For detailed information about the Solaris installation GUI and text installer, see System Requirements and Recommendations.
The system configures the devices and interfaces, and searches for configuration files. The kdmconfig utility detects the drivers that are necessary to configure the keyboard, display, and mouse on your system. 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 6, Preconfiguring System Configuration Information (Tasks) for more information.
If you did not preconfigure all the system information, use the Checklist for Installation to help you answer the configuration questions.
If you are using the installation GUI, after you confirm the system configuration information, the Welcome to Solaris dialog box 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 6, Preconfiguring System Configuration Information (Tasks) for more information.
If you did not preconfigure all the installation options, use the Checklist for Installation to help you answer the installation questions.
If you are upgrading a system that has non-global zones installed, follow these steps.
When you are prompted to select initial installation or upgrade, choose Upgrade. Click Next.
If your system has multiple root (/) partitions, select the partition that you want to upgrade on the Select Version to Upgrade panel.
The Solaris installation program displays a message that indicates that you cannot customize your upgrade. The Solaris installation program analyzes your system to determine if the system can be upgraded. The Ready to Upgrade panel is displayed.
If your system has only one root partition, the Solaris installation program does not prompt you to select a partition to upgrade. The partition is automatically selected.
If you want to continue the upgrade, click Install Now on the Ready to Upgrade panel.
The Solaris installation program begins to upgrade your system.
If you do not want to continue the upgrade, click Back to perform an initial installation.
After the system boots and installs over the network, instruct the system to boot from the disk drive on subsequent boots.
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 the Solaris Boot Behavior by Editing the GRUB Menu in System Administration Guide: Basic Administration.
For information about how to complete an interactive installation with the Solaris installation GUI, see To Install or Upgrade With the Solaris Installation Program With GRUB in Solaris 10 6/06 Installation Guide: Basic Installations.
This chapter lists the commands used to set up network installations. This chapter includes the following topics.
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 |
---|---|---|
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. |
|
All |
A script that copies the Solaris 10 6/06 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. |
|
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. |
|
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. |
|
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. |
|
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. The patchadd(1M) man page contains more information. Caution – Don't use the patchadd -C command unless you have read the Patch README instructions or have contacted your local Sun support office. |
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. |
|
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. |
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/sol_10_x86/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, see the eeprom(1M) man page.
Table 10–1 x86: GRUB Menu Commands and Options