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 8 disc images, called an install server, to other systems on the network. You copy the contents of the Solaris 8 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 |
Description |
For Instructions |
---|---|---|
Create an install server. |
Use the setup_install_server(1M) command to copy the Solaris 8 DVD to the install server's hard disk. | |
(Optional) Create boot servers. |
If you want to install systems from the network that are not on the same subnet as the install server and you are not using DHCP, you must create a boot server on the subnet to boot the systems. | |
Add systems to be installed from the network. |
Setup each system that you want to install from the network. Each system that you want to install needs to know where on the network to find the install server, the boot server, and configuration information. |
You must create an install server to install the Solaris software on a system from the network. If systems that you are installing are not in the same subnet as the install server and you are not using DHCP, you must do one of the following:
Create separate boot servers for each subnet
Create an install server for each subnet. However, this requires more disk space.
You cannot use a SunOS 4.1.x system as an install server.
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 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.
Create a directory to contain the boot image.
# mkdir -p install_dir_path |
install_dir_path |
Specifies the directory where the DVD image is to be copied |
Decide if you want to copy the Solaris 8 DVD to the install server's hard disk.
If yes, continue.
If no, go to Step 8.
Change to the Tools directory on the mounted disc:
For SPARC DVD media:
# cd /cdrom/cdrom0/s0/Solaris_8/Tools |
For IA DVD media:
# cd /cdrom/cdrom0/Solaris_8/Tools |
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 |
install_dir_path |
Specifies the directory where the DVD image is to be copied |
The setup_install_server command indicates whether or not there is enough disk space available for the Solaris 8 Software disc images. To determine available disk space, use the df -kl command.
Eject the Solaris 8 DVD.
Decide if you want to patch the files that are located in the miniroot (Solaris_8/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. Go to Adding Systems to Be Installed From the Network.
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 install server by copying the Solaris 8 DVD to the install server's /export/home/s8dvdsparc directory:
# mkdir -p /export/home/s8dvdsparc # cd /cdrom/cdrom0/s0/Solaris_8/Tools # ./setup_install_server /export/home/s8dvdsparc |
The following example illustrates how to create an install server by copying the Solaris 8 DVD to the install server's /export/home/s8dvdia directory:
# mkdir -p /export/home/s8dvdia # cd /cdrom/cdrom0/Solaris_8/Tools # ./setup_install_server /export/home/s8dvdia |
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 IA 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.
Create a directory to contain the boot image.
# mkdir -p install_dir_path |
install_dir_path |
Specifies the directory where the DVD image is to be copied |
Decide if you want to copy the Solaris 8 DVD to the install server's hard disk.
If yes, continue.
If no, go to Step 8.
Change to the Tools directory on the mounted disc:
For IA DVD media:
# cd /cdrom/cdrom0/s2/Solaris_8/Tools |
For SPARC DVD media:
# cd /cdrom/cdrom0/Solaris_8/Tools |
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 |
install_dir_path |
Specifies the directory where the DVD image is to be copied |
The setup_install_server command indicates whether or not there is enough disk space available for the Solaris 8 Software disc images. To determine available disk space, use the df -kl command.
Eject the Solaris 8 DVD.
Decide if you want to patch the files that are located in the miniroot (Solaris_8/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. Go to Adding Systems to Be Installed From the Network.
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 install server by copying the Solaris 8 DVD to the install server's /export/home/s8dvdsparc directory:
# mkdir -p /export/home/s8dvdsparc # cd /cdrom/cdrom0/s2/Solaris_8/Tools # ./setup_install_server /export/home/s8dvdsparc |
The following example illustrates how to create an install server by copying the Solaris 8 DVD to the install server's /export/home/s8dvdia directory:
# mkdir -p /export/home/s8dvdia # cd /cdrom/cdrom0/s0/Solaris_8/Tools # ./setup_install_server /export/home/s8dvdia |
You can install the Solaris software from the network from any install server on the network. If you use the add_install_client command with the -d option for DHCP, you do not need to create a boot server. DHCP provides the installation parameters necessary for installation. However, a system that needs to use an install server on another subnet and does not use DHCP requires a separate boot server on its own subnet. 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.
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 system you intend to make the boot server for the subnet, log in and become superuser.
The system must have access to the remote Solaris 8 disc images. 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.
Mount the Solaris 8 DVD from an image on an NFS server.
# mount -F nfs -o ro,anon=0 server_name:path /mnt |
server_name:path |
Is the host name and absolute path to the disc image |
Change directory to the mounted disc image:
# cd /mnt |
Change to the Tools directory on the Solaris 8 DVD image by typing:
# cd Solaris_8/Tools |
Copy the boot software to the boot server.
# ./setup_install_server -b boot_dir_path |
-b |
Specifies to setup the system as a boot server |
boot_dir_path |
Specifies the directory where the boot software is to be copied |
The setup_install_server command indicates whether or not there is enough disk space available for the images. To determine available disk space, use the df -kl command.
You are now ready to set up systems to be installed from the network. See Adding Systems to Be Installed From the Network.
The following example illustrates how to create a boot server on a subnet. These commands copy the boot software from the Solaris 8 DVD image to /export/home/s8dvdsparc on the system's local disk.
# mount -F nfs -o ro,anon=0 crystal:/export/home/s8dvdsparc /mnt # cd /mnt # cd Solaris_8/Tools # ./setup_install_server -b /export/home/s8dvdsparc |
In this example, the disc is inserted and automatically mounted before the command. After the command, the disc is removed.
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 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
When you install from the network, a system checks for this information in the name service in the bootparams database in the /etc files, NIS, NIS+, DNS, or LDAP. You must add this information to the name service for every system that is to be installed from the network. You add this information by using the add_install_client command.
If you use the /etc files to store network installation information, the information must be located on the install server or the boot server, if a boot server is required
You use the add_install_client(1M) command to set up systems to be installed from the network. You need to run this command on the install server and the boot server if a boot server is required.
The add_install_client command updates only the /etc files.
In this procedure host1 is the install server and host2 is boot server.
On the install server, host1, become superuser.
If you use the NIS or NIS+ name service, verify that the following information about the system to be installed has been added to the name service in the /etc files:
Host name
IP address
Ethernet address
Change to the Tools directory on the Solaris 8 DVD image on the install server:
host1# cd Solaris_8/Tools |
Use the add_install_client command to set up a system to be installed from the network:
host1# ./add_install_client [[-d]] [[-c server:jumpstart_dir_path]] \ [[-p server:path]] client_name platform_group |
-d |
Specifies that the client is to use DHCP to obtain the network install parameters. For IA clients, use this option to boot the systems from the network using PXE network boot. |
-c server:jumpstart_dir_path |
Specifies a JumpStart directory for custom JumpStart installations. server is the host name of the server on which the JumpStart directory is located. jumpstart_dir_path is the absolute path to the JumpStart directory. |
-p server:path |
Specifies the sysidcfg file for preconfiguring system information. server is either a valid host name or IP address for the server that contains the file. path is the absolute path to the sysidcfg file. |
client_name |
Is the name of the system to be installed from the network. This name is not the host name of the install server. The client must be in the name service for this command to work. |
platform_group |
Is the platform group of the system to be installed. For more information, see Chapter 37, Platform Names and Groups. |
Decide if you need to run the command on a boot server.
If a boot server is not required, you are finished.
If a boot server is required, continue.
On the boot server, host2, become superuser.
Change to the Tools directory on the Solaris 8 DVD image on the boot server's boot directory:
host2# cd Solaris_8/Tools |
Use the add_install_client command to set up a system to boot from the boot server and to be installed from the network:
host2# ./add_install_client [[-d]] [[-c server:jumpstart_dir_path]] \ -s install_server:install_dir_path [[-p server:path]] client_name platform_group |
-d |
Specifies that the client is to use DHCP to obtain the network install parameters. For IA clients, use this option to boot the systems from the network by using PXE network boot. |
-c server:jumpstart_dir_path |
Specifies a JumpStart directory for custom JumpStart installations. 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. |
-s install_server:install_dir_path |
Specifies the install server. This option is required only when you are using add_install_client on a boot server. install_server is the host name of the install server. install_dir_path is the absolute path to the Solaris 8 DVD image for your platform. |
-p server:path |
Specifies the sysidcfg file for preconfiguring system information. server is either a valid host name or IP address for the server that contains the file. path is the absolute path to the sysidcfg file. |
client_name |
Is the name of the system to be installed from the network. This name is not the host name of the install server. The client must be in the name service for this command to work. |
platform_group |
Is the platform group of the system to be installed. For more information, see Chapter 37, Platform Names and Groups. |
The following example illustrates how to add a system that is named basil, which is a UltraTM 5, to be installed from the network. The system requires a boot server, so the command is run on the install server and is run again on the boot server. The -s option is used to specify the install server that is named install_server1, which contains a Solaris 8 SPARC Platform Edition DVD image in export/home/s8dvdsparc.
host1# cd /export/install/boot/Solaris_8/Tools host1# ./add_install_client basil sun4u host2# cd /export/install/boot/Solaris_8/Tools host2# ./add_install_client -s install_server1:/export/home/s8dvdsparc basil sun4u |
The following example illustrates how to set up IA systems to be booted and installed from the network by using the DHCP protocol. 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 IA 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 install_server1, which contains a Solaris 8 Intel Platform Edition DVD image in /export/home/s8dvdia:
# cd /export/boot/Solaris_8/Tools # ./add_install_client -d -s install_server1:/export/home/s8dvdia SUNW.i86pc i86pc |