Once you have an install server set up, you then provide basic system information about the workstations (hosts) that you are going to install. You also add the Trusted Solaris configuration information.
You have a choice of two methods for entering the information:
Using the Host Manager with the NIS+ naming service.
Use this method to have the NIS+ name service provide the client information. This is the most efficient method.
Using the add_install_client(1M) command to modify the install server's local files.
Use this method if you have scripts that run the add_install_client command for your clients.
On the install server, log in as a user who can assume the role admin.
As role admin, at label admin_low
,
launch the Host Manager using the NIS+ naming service.
See "To Open and Modify a Solstice_Apps Database" if you are unfamiliar with the steps.
If the workstation already exists, select it in the Host Manager main window, choose Edit > Convert > Standalone.
If the workstation does not already exist, add it by choosing Edit > Add.
For each workstation, fill out the host information.
Enable remote install.
Complete all fields up to the Boot Server.
Entry |
Value |
Host Name |
|
IP Address |
|
Ethernet Address |
|
System Type |
|
Timezone Region |
|
Timezone |
|
Remote Install |
4 Enable Remote Install |
Install Server |
install_server_name (entered for you) |
Set Path |
/export/install/ts7_sparc (sample) |
OS release |
Choose client's platform group and software cluster |
Boot Server
|
boot_server_name (if separate server) path to boot file |
Profile Server |
Enter JumpStart directory (for Custom JumpStart). |
If the Ethernet address field was not filled in, choose the workstation, choose Edit > Modify, and enter the Ethernet address.
Choose File > Save Changes.
The window prints "All changes successful" when finished.
Repeat for all hosts to be installed over the network.
Go to "Check Client Information".
If you added hosts with the Host Manager, do not add information locally, as this command does.
On the install server, as secadmin at label admin_low
, add the add_install_client and rm_install_client commands to the root role's profile.
The path to the commands is install_dir_path. For the continuing example, the path is /export/install/ts7_sparc.
See "To Add a Command to a Role's Profile" for the full procedure.
On the install server, as root at label admin_low
, launch the Name Service Switch action.
Ensure that the value of ethers and bootparams is files nisplus, as in:
ethers: files nisplus dns netmasks: files nisplus dns bootparams: files nisplus dns
As root, verify that the commands add_install_client and rm_install_client are in your profile.
# clist -p | grep install_client It should display: /export/install/ts7_sparc/add_install_client: all /export/install/ts7_sparc/rm_install_client: all |
See "To Verify That a Command is in a Role's Profile" for the full procedure.
Change to the Trusted Solaris boot information directory.
# cd boot_dir_path |
For example, if the boot server is also the install server:
# cd /export/install/ts7_sparc |
Run the add_install_client(1M) command for every client you plan to install over the network.
# ./add_install_client [ -e ethernet_address ] \ -s install_server:install_dir_path host_name platform_group |
Specifies the ethernet address.
Specifies the install server.
install_server is the host name of the install server. install_dir_path is the absolute path name of the directory that has the copy of the Trusted Solaris CD image.
Is the host name of the standalone workstation or the server receiving the network installation. The host must be in the NIS+ name service for this command to work.
Is the platform group (sun4c, sun4m, sun4u) of the host being installed. (For a detailed list of platform groups, see Solaris 7 Sun Hardware Platform Guide.)
For example, issuing the command:
# ./add_install_client -e 8:0:20:17:22:a4 \ -s heron:/export/install/ts7_sparc willet sun4m |
Creates (if necessary) and copies boot information to the boot server's local bootparams database.
Creates (if necessary) and copies ethernet information to the boot server's local ethers file.
Creates (if necessary) and sets up the /tftpboot directory on the boot server with an entry for willet, whose platform group is sun4m.
Points the client to platform information on the install server's (heron's) file system, /export/install/ts7_sparc.
Result: The client willet can be installed over the network.
As secadmin, at label admin_low
,
remove the add_install_client script from the Custom Root
Role.
See "To Remove a Command from a Role's Profile" for the full procedure.
Go to "Check Client Information".
As root, at label admin_low
,
verify that rm_install_client is in the root profile shell.
# clist -p | grep rm_install_client It should display: /export/install/ts7_sparc/rm_install_client: all |
Change to the Trusted Solaris boot information directory.
# cd boot_dir_path |
As root, at label admin_low
,
run the rm_install_client command for every client you
plan to remove from the network install.
# ./rm_install_client host_name |
Once all clients are removed, assume the role secadmin and remove the rm_install_client script from the Custom Root Role.
See "To Remove a Command from a Role's Profile" for the full procedure.