|
|
This chapter provides instructions for installing and deleting SBus adapter diskless boot software. Diskless boot driver software is provided for both SunOS 4.1.x and Solaris 2.x operating systems.
A diskless client is any system that does not have a hard disk and relies on an assigned server for all of its resources. The diskless boot client's file systems, disk storage, and swap space, which are stored on a server, require access to a server to boot.
Before you can begin installation and configuration, you will need the following:
This section describes how to install and delete diskless boot clients using the SunOS 4.1.x operating system. The section includes the following:
This section provides an overview of how to install the SunOS 4.1.x diskless boot software using the ./install.fddi command and how to add a client using the add_client command. Refer to the section "Administering Workstations" in the Sun System and Network Configuration manual for detailed installation instructions.
To use the add_client command to add a client to the server database, refer to the section "Administering Workstations" in the Sun System and Network Configuration manual for detailed instructions.
Perform the following tasks to add the client to the server databases:
Step 1 Change directories to /usr/etc/install to use the add_client utility.
Step 2 At the server command line, enter the ./add_client -i command. The -i option invokes full screen interactive mode, as shown in the following example:
add_client -i
The following screen appears:
[sun4c.sunos.4.1.3] x [sun4m.sunos.4.1.3_u1]cisco-fddi
Choice : x [create] [delete] [display] [edit]
[x/X=select choice] [space=next choice] [^B/^P=backward] [^F/^N=forward]Step 3 From the preceding screen, select the following:
Information similar to the following is added to the screen:
CLIENT FORM [?=help] [DEL= erase one char] [RET=end of input data]
---------------------------------------------------------------
Architecture type : [sun4c.sunos.4.1] x [sun4m.sunos.4.1.3_u1]
Client name : cisco-fddi
Choice : x [create] [delete] [display] [edit]
Root fs: /export/root (sd3h) 118805504 Hog: 3d3h 118805504
Swap fs: /export/swap (sd3h) 118805504 Hog: 3d3h 118805504
Client Information :
Internet Address : 198.133.219.2511
Ethernet Address : 8:00:20:19:ef:4
NIS Type : X [none] [client]
Swap size (e.g. 8B, 8K) : 16M
Path to Root : /export/root/cisco-fddi
Path to Swap : /export/swap/cisco-fddi
Path to Executable : /usr
Path to Kernel Executable : /usr/kvm
Path to Home : /export/home/Boot-server-fddi
Terminal type : sun
Ok to use these values [y/n] y
[x/X=select choice][space=next choice][^B/^P=backward][^F/^N=forward]
Step 4 Verify that all displayed variables are correct. If all the displayed variables are correct, enter y. The following confirmation screen appears:
CLIENT FORM [?=Help] [DEL= erase one char] [RET=end of input data]
----------------------------------------------------------------------
Architecture type : [sun4c.sunos.4.1] x [sun4m.sunos.4.1.3_u1]
Client name : cisco-fddi
Choice : x [create] [delete] [display] [edit]
sun4m.sunos.4.1.3_u1 Clients:
cisco-fddi
Are you finished with this form [y/n]
[x/X=select choice][space=next choice][^B/^P=backward][^F/^N=forward]
Step 5 Enter y. The add_client utility will add the new client. The following message appears:
Step 6 If the server where you ran the add_client utility contains the network information services (NIS) database, verify that the following files were updated:
If this server does not contain the NIS database, the system administrator must update the following files in the database:
swap=Boot_server:/export/swap/cisco-fddi
Perform the following tasks to install the SunOS diskless boot driver:
Step 1 At the server, change the directory to /usr/local/diskless/cfddi.
Step 2 At the prompt, enter ./install.fddi to run the install script:
./install.fddi
You have invoked the ./install.fddi script, which is used to install software for FDDI SBus Adapters.
y?
Step 3 At the prompt, enter y to perform the installation for a diskless station. The following prompt appears:
/export/root/cisco-fddi
Step 4 At the prompt, enter the path to the diskless boot files as in the preceding example. The following prompt appears:
Step 5 At the prompt, enter y to install the SNMP agent on the diskless station. The following information appears:
Step 6 At the prompt, enter the number of FDDI interfaces installed in this workstation. The following prompt appears:
Step 7 The FDDI interface host name prompt appears. Enter the new host name of this workstation or use the default assigned (the existing name appended with -fddi). The following prompt appears:
Step 8 Enter y to have the IP address retrieved from the host. The following prompt appears:
Step 9 Confirm the IP address retrieved and displayed in default brackets is correct or manually add the correct IP address if needed. The following prompt appears:
Step 10 Enter the correct client architecture for this system. Enter sun4m. The following information and prompt appears:
Step 11 At the prompt, enter the path to the client architecture kernel. In this example, the path is /export/exec/kvm/sun4m. The following prompt appears:
Step 12 At the prompt, enter the name of the existing kernel configuration file to be copied and modified in the next step. The following prompt appears:
Step 13 At the prompt, enter the name you want given to the new kernel configuration file. Information similar to the following appears:
When the server console prompt reappears, the SunOS diskless boot driver installation is complete. Continue with the instructions in the following section "Configuring the SunOS 4.1.x Diskless Boot Client" at each diskless boot client.
Perform the following steps at each diskless boot client to boot from the remote server:
Step 1 At the diskless station command line, enter boot device_path, where device_path is your type of workstation. See Table 7-1 for the proper device path.
| Workstation Type | Device Path | Notes |
|---|---|---|
| Sun4c | /sbus/fddi | |
| Sun4d | /io-unit@f,e0200000/sbi/fddi | For Solaris only |
| Sun4m | /iommu/sbus/fddi |
Following is an example of the boot device path for a Sun4c workstation:
The following information appears, displaying the device path:
show-devs
Step 2 At the ok prompt, enter setenv boot-device device_path to set the diskless workstation open boot PROM (OBP) environment path to use the FDDI adapter as the default boot device. See Table 7-1 for the proper device path or use the absolute device path, as shown in the preceding example.
Following is an example setting the environment path for a Sun4c workstation:
Step 3 Use the printenv command to show the OBP's current settings; the device path is displayed as in the following example:
Step 4 At the next ok prompt, enter boot to boot the diskless workstation using the FDDI adapter as the boot device, as in the following example:
Example:
This section describes how to configure the diskless workstation and server to use the Sun Microsystems Custom JumpStart utility to automatically install the Solaris software over the FDDI network. Refer to the Sun Microsystems document SPARC: Installing Solaris Software for detailed installation instructions.
Follow the instructions in the Sun document to configure the local server as an installation server and/or as a boot server.
The following instructions will not affect the kernel running on the server, but will make changes to JumpStart files to allow Solaris installation over the FDDI.
Follow these steps in preparing the installation server to perform the JumpStart function over FDDI.
Step 1 Access the diskette file system from the server. Use a file manager, or mount the Solaris FDDI/CDDI diskette.
Step 2 Copy the SBUSfddi directory and its contents from the diskette to the install_dir_path/Solaris_2.4 directory on the server:
cp -r SBUSfddi install_dir_path/Solaris_2.4
This creates a directory with all FDDI files and scripts in install_dir _path/Solaris_2.4/SBUSfddi.
Step 3 Change directories to install_dir_path/Solaris_2.4/SBUSfddi/reloc.
Step 4 Change the permission of the neti file. Enter the following:
Step 5 Enter ./neti to run the neti script. The following appears:
Step 6 Enter y to continue with the FDDI jumpstart network installation script. The following appears:
Step 7 At the prompt, enter the type of Sun architecture on the target workstation, either sun4m, sun4c or sun 4d. Information similar to the following appears:
Step 8 Change directories to the install_dir_path, and run the add_an_install_client utility. Following is an example:
Step 9 Refer to the document Sun SPARC: Installing Solaris Software, Chapter 4, "Preparing Custom Jumpstart Installations," for instructions on how to create the JumpStart directory and profile. Confirm that the SBUSfddi package is included in the profile. For example:
Step 10 Create a rules file following the instructions in the section, "Creating the Rules File," in Chapter 4 of the Sun SPARC: Installing Solaris Software document.
The server is now configured to use custom JumpStart to automatically install the Solaris software over the FDDI.
Step 11 At the diskless station command line, enter boot device_path -install where the device_path is your type of workstation. See Table 7-2 for the proper device path.
| Workstation Type | Device Path | Notes |
|---|---|---|
| Sun4c | /sbus/fddi | |
| Sun4d | /io-unit@f,e0200000/sbi/fddi | For Solaris only |
| Sun4m | /iommu/sbus/fddi |
Following is an example of the boot device path entered for a Sun4d workstation:
Step 12 Once the installation is complete, you see the following message:
Step 13 Reboot and clear the problem or use the ifconfig command to initiate the interface:
# plumb
# diskless_name up
where:
fddi# is the FDDI adapter number, usually fddi0.
plumb opens the device associated with the interface.
diskless_name is the name of the diskless workstation.
The Solaris custom JumpStart feature configuration is complete.
You can use the rm_client command to delete a client from the server database. To do so, refer to the section "Administering Workstations" in the Sun System and Network Configuration manual for detailed instructions.
Perform the following tasks to delete the client patch to the server databases:
Step 1 Change directories to /usr/etc/install to use the rm_client utility.
Step 2 At the server command line, enter the ./rm_client clientname command, as in the following example where cisco-fddi is the client name:
The following screen appears:
Step 3 Enter y to delete the client cisco-fddi /etc/hosts entry from the server database. The following screen appears:
Step 4 Enter y to delete the client cisco-fddi /etc/ethers entry from the server database. The following screen appears:
Step 5 Enter y to delete the client cisco-fddi /export/root entry from the server database. The following screen appears:
Step 6 If the server where you ran the rm_client utility contains the network information services (NIS) database, verify that the following files were updated:
If this server does not contain the NIS database, the system administrator must update the following files in the database:
This section describes how to install and delete diskless boot clients using the Sun Solaris operating system. The section includes the following:
This section provides an overview on how to install the Sun Solaris diskless boot software using the administration tool, and how to add a client using the pkg_add command. Refer to the section "Introducing a Machine to a Network" in the Solaris 2.3 System Configuration and Installation Guide for detailed installation instructions.
Perform the following steps to modify the administration files using the host manager:
Step 1 Start the administration tool at the boot server by entering /usr/bin/admintool at the command line, as in the following example:
The Administration Tool base screen appears.
Step 2 From the Administration Tool screen, select Host Manager. The Host Manager: Select Naming Service screen appears.
Step 3 Under Naming Service, select none.
Step 4 After selecting none at the prompt Use /etc files on host, enter the name of the server where the diskless workstation's /etc configuration files will reside.
Step 5 Select apply. The Host Manager base screen appears.
Step 6 From the Host Manager base screen, select Edit. The Host Manager Add Host screen appears.
Step 7 Click on the Client Type menu button, and select diskless.
Step 8 In the host name field, enter a host name for the diskless client workstation.
Step 9 In the IP address field, enter the IP address for the diskless client workstation.
Step 10 In the Ethernet address field, enter the Ethernet address for the diskless client workstation.
Step 11 Select the correct variable for time zone and region, file server, and OS release.
Step 12 Enter the correct root and swap paths, swap size, system core path, and size.
Step 13 Select add to update the administration files.
Step 14 After adding all the diskless workstations to the server administration files, quit the administration tool.
Step 15 If the server where you ran the admin_tool utility contains the network information services (NIS) database, verify that the following files were updated:
If this server does not contain the NIS database, the system administrator must update the following files in the database:
Continue with the following section "Installing the Solaris Client Using the pkgadd Script" at each diskless boot client.
At the server, use the pkgadd utility to add the SBus fddi diskless boot adapter driver for the client workstation.
Perform the following steps:
Step 1 At the command line, enter the following command to start the pkgadd script:
pkgadd -R /export/root/client name -d /floppy/floppy0
following is an example:
Step 2 At the prompt, select packages 1 and 2. The following information appears:
Step 3 At the prompt, enter y to install a diskless workstation adapter driver. The following appears:
Step 4 At the prompt, enter y if the adapter is currently installed. The following appears:
Step 5 At the prompt, enter y to continue to use the Ethernet interface. The following appears:
Step 6 At the prompt, enter the number of interfaces installed in this machine. The following appears:
Step 7 At the prompt, enter y if you want to get the IP address from NIS. The following information will appear:
Step 8 At the prompt, enter the new host name for this workstation. The following appears:
Step 9 At the prompt, enter the IP address for the diskless workstation. The following appears:
Step 10 At the confirmation, enter y to continue with the installation. The following information appears:
Step 11 When the initial screen reappears, enter q to quit the pkgadd utility, and reboot the client workstation.
Step 12 If the server where you ran the pkgadd utility contains the network information services (NIS) database, verify that the following files were updated:
If this server does not contain the NIS database, the system administrator must update the following files in the database:
See the section "pkgrm Script Example" in the appendix "Running the FDDI deinstall Script" to delete a client from the server database using the command pkgrm -R /export/root/client name.
|
|