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 9 disc images, called an install server, to other systems on the network. You copy the contents of the Solaris 9 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
Task |
Description |
For Instructions |
---|---|---|
Use the setup_install_server(1M) command to copy the Solaris 9 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 |
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 2.6 or 7 operating environment, you must first apply one of the following patches.
Solaris 2.6 SPARC Platform Edition operating environment — Patch ID 107618-03
Solaris 2.6 Intel Platform Edition operating environment — Patch ID 107619-03
Solaris 7 SPARC Platform Edition operating environment — Patch ID 107259-03
Solaris 7 Intel Platform Edition operating environment — Patch ID 107260-03
SPARC: You cannot use a system that is running a SunOS version that was released prior to the Solaris 2.3 release.
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: Basic Administration 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 9 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_9/Tools |
For x86 DVD media, type:
# cd /cdrom/cdrom0/Solaris_9/Tools |
In the previous examples, cdrom0 is the path to the drive that contains the Solaris operating environment 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 9 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 10.
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 10.
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 |
Make sure that the install server's directory path is correctly shared.
# ps -ef | grep nfsd |
If the nfsd daemon is not running, start it.
# /etc/init.d/nfs.server start |
If the nfsd daemon is running, share the install server.
# shareall |
Change directories to root (/).
# cd / |
Eject the Solaris 9 DVD.
Decide if you want to patch the files that are located in the miniroot (/install_dir_path/Solaris_9/Tools/Boot) on the net install image that was created by setup_install_server. Patching a file might be necessary if a boot image has problems.
If no, continue.
If yes, use the patchadd -C command to patch the files that are located in the miniroot.
Don't use the patchadd -C command unless you have read the Patch README instructions or have contacted your local Sun support office.
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 is 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 9 DVD to the install server's /export/home/s9dvdsparc directory:
# mkdir -p /export/home/s9dvdsparc # cd /cdrom/cdrom0/s0/Solaris_9/Tools # ./setup_install_server /export/home/s9dvdsparc |
If you need 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/s9dvdsparc |
Check if the nfsd daemon is running. If the nfsd daemon is not running, start it and share it.
# ps -ef | grep nfsd # /etc/init.d/nfs.server start # shareall # cd / |
The following example illustrates how to create an install server by copying the Solaris 9 DVD to the install server's /export/home/s9dvdx86 directory:
# mkdir -p /export/home/s9dvdx86 # cd /cdrom/cdrom0/Solaris_9/Tools # ./setup_install_server /export/home/s9dvdx86 |
Add the following path to the /etc/dfs/dfstab file:
share -F nfs -o ro,anon=0 -d "install server directory" /export/home/s9dvdx86 |
Check if the nfsd daemon is running. If the nfsd daemon is not running, start it and share it.
# ps -ef | grep nfsd # /etc/init.d/nfs.server start # shareall # cd / |
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: Basic Administration 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 9 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:
For x86 DVD media, type:
# cd /cdrom/cdrom0/s2/Solaris_9/Tools |
For SPARC DVD media, type:
# cd /cdrom/cdrom0/Solaris_9/Tools |
In the previous examples, cdrom0 is the path to the drive that contains the Solaris operating environment 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 9 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 10.
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 10.
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 |
Make sure that the install server's directory path is correctly shared.
# ps -ef | grep nfsd |
If the nfsd daemon is not running, start it.
# /etc/init.d/nfs.server start |
If the nfsd daemon is running, share the install server.
# shareall |
Change directories to root (/).
# cd / |
Eject the Solaris 9 DVD.
Decide if you want to patch the files that are located in the miniroot (Solaris_9/Tools/Boot) on the net install image that was created by setup_install_server.
If no, continue.
If yes, use the patchadd -C command to patch the files that are located in the 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 example illustrates how to create an x86 install server by copying the Solaris 9 x86 Platform Edition DVD to the install server's /export/home/s9dvdx86 directory:
# mkdir -p /export/home/s9dvdx86 # cd /cdrom/cdrom0/s2/Solaris_9/Tools # ./setup_install_server /export/home/s9dvdx86 |
Add the following path to the /etc/dfs/dfstab file:
share -F nfs -o ro,anon=0 -d "install server directory" /export/home/s9dvdx86 |
Check if the nfsd daemon is running. If the nfsd daemon is not running, start it and share it.
# ps -ef | grep nfsd # /etc/init.d/nfs.server start # shareall # cd / |
The following example illustrates how to create an x86 install server by copying the Solaris 9 SPARC Platform Edition DVD to the install server's /export/home/s9dvdsparc directory:
# mkdir -p /export/home/s9dvdscparc # cd /cdrom/cdrom0/Solaris_9/Tools # ./setup_install_server /export/home/s9dvdsparc |
Add the following path to the /etc/dfs/dfstab file:
share -F nfs -o ro,anon=0 -d "install server directory" /export/home/s9dvdsparc |
Check if the nfsd daemon is running. If the nfsd daemon is not running, start it and share it.
# ps -ef | grep nfsd # /etc/init.d/nfs.server start # shareall # cd / |
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 are 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 9 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 9 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 9 DVD image.
# cd /mnt/Solaris_9/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 9 DVD image to /export/home/s9dvdsparc on the local disk of a boot server named crystal.
# mount -F nfs -o ro crystal:/export/home/s9dvdsparc /mnt # mkdir -p /export/home/s9dvdsparc # cd /mnt/Solaris_9/Tools # ./setup_install_server -b /export/home/s9dvdsparc # cd / # umount /mnt |
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:
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
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, see Example 11–6.
If your install server and client are on the same subnet, see Example 11–7.
If your install server and your client are not on the same subnet and you are not using DHCP, see Example 11–8.
For more options to use with this command, see the man page, add_install_client(1M).
If you have a boot server, make sure you have shared the install server installation image and started the appropriate daemons. See “To Create a SPARC Install Server With SPARC or x86 DVD Media” Step 6.
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 9 DVD image:
# cd /install_dir_path/Solaris_9/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]] client_name platform_group |
Specifies that the client is to use DHCP to obtain the network install parameters.
For x86 clients, use this option to boot the systems from the network by using PXE network boot.
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 9 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 9 net installation image, CD, or DVD.
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 Appendix C, Platform Names and Groups (Reference).
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/s9dvdsparc/Solaris_9/Tools contains the add_install_client command.
For more information on how to use DHCP to set installation parameters for network installations, see “Supporting Solaris Network Installation with the DHCP Service (Task Map)” in System Administration Guide: IP Services.
sparc_install_server# cd /export/home/s9dvdsparc/Solaris_9/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 UltraTM 5 system. The file system /export/home/s9dvdsparc/ contains the add_install_client command.
install_server# cd /export/home/s9dvdsparc/Solaris_9/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 UltraTM 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 9 SPARC Platform Edition DVD image in /export/home/s9dvdsparc.
boot_server# cd /export/home/s9dvdsparc/Solaris_9/Tools boot_server# ./add_install_client -s rosemary:/export/home/s9dvdsparc 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 DHCP class name SUNW.i86pc indicates that this command applies to all Solaris x86 network boot clients, not just a single client. 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 9 x86 Platform Edition DVD image in /export/boot/s9dvdx86.
For more information on how to use DHCP to set installation parameters for network installations, see “Supporting Solaris Network Installation with the DHCP Service (Task Map)” in System Administration Guide: IP Services.
x86_install_server# cd /export/boot/s9dvdx86/Solaris_9/Tools x86_install_server# ./add_install_client -d -s rosemary:/export/home/s9dvdx86 \ SUNW.i86pc i86pc |