Tru64 UNIX Sharing Software on a Local Area Network Part Number: AA-RH9DC-TE June 2001 Product Version: Tru64 UNIX Version 5.1A This manual describes Remote Installation Services (RIS) and Dataless Management Services (DMS) in CompaqTru64 UNIX. RIS is used to install software kits across a network instead of using locally mounted distribution media. DMS lets client systems share the /usr file system on a networked server while maintaining their own root ( / ) and /var file systems on a DMS server.
© 2001 Compaq Computer Corporation COMPAQ, the Compaq logo, and TruCluster Registered in the U.S. Patent and Trademark Office. Tru64 is a trademark of Compaq Information Technologies Group, L.P. UNIX is a trademark of The Open Group. All other product names mentioned herein may be trademarks of their respective companies. Confidential computer software. Valid license from Compaq required for possession, use, or copying. Consistent with FAR 12.211 and 12.
Contents About This Manual 1 Introduction to Sharing Software 1.1 1.2 1.3 2 Overview . . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . Starting RIS . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . RIS Areas and Product Environments . . . .. . .. . .. . .. . . .. . .. . .. . .. . RIS Client Characteristics . . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . Registering Clients .
5 Booting a RIS Client 5.1 5.1.1 5.1.2 5.1.3 5.1.4 5.2 6 Preregistration Tasks .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . Obtaining Information About Each Client .. . .. . . .. . .. . .. . .. . Registering Client Host Names and IP Addresses . .. . .. . .. . Adding a RIS Client with the ris Utility . .. . .. . .. . .. . . .. . .. . .. . .. . Adding a RIS Client from the Command Line .. . .. . . .. . .. . .. . .. . Modifying RIS Clients .. . .. . . .. . .. . .. . .. .
8.4.4 8.4.5 8.5 8.5.1 8.5.2 8.5.3 9 Client Registered on Multiple RIS Servers . . .. . . .. . .. . .. . .. . Client Not in RIS Database . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . RIS Server Response . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . Servers Using the bootpd Daemon . . . .. . .. . .. . .. . . .. . .. . .. . .. . Servers Using the joind Daemon . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . Loading an Incorrect Kernel File . .. . . .. . .
11.5.1 11.5.2 11.5.3 Setting Up a DMS Server for WLS . . . .. . .. . .. . .. . . .. . .. . .. . .. . Setting Up a DMS Client for WLS . . . .. . .. . .. . .. . . .. . .. . .. . .. . Building an Asian Kernel for DMS Clients . . .. . . .. . .. . .. . .. . 11–12 11–13 11–13 12 Managing DMS Clients and Environments 12.1 12.2 12.3 12.4 12.5 12.6 12.7 12.8 12.9 12.9.1 12.9.2 12.9.3 DMS Client Database File . . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . Adding a DMS Client . .. . .. .
Glossary Index Examples 5–1 6–1 7–1 8–1 Sample /etc/bootptab File . . . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . Sample /var/adm/ris/gateways File .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . Sample RIS Client Profile Set Registration .. . .. . .. . . .. . .. . .. . .. . Sample daemon.log File . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . 5–3 6–14 7–3 8–7 RIS Server and Client .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . .. . .
About This Manual This manual describes the Remote Installation Services (RIS) and Dataless Management Services (DMS) environments and utilities maintained on a Compaq Tru64™ UNIX operating system. • RIS lets you install software kits across a network from a centrally administered server instead of using locally mounted media.
The Tru64 UNIX documentation is available on the World Wide Web at the following URL: http://www.tru64unix.compaq.com/docs/ Organization This manual is organized as follows: Chapter 1 Introduces the concept of servers and clients, explaining what they are and how they work together. It also describes the basic architecture of the server/client environment. Chapter 2 Describes the relationship between the RIS server and RIS clients.
Appendix C Describes the utilupdate utility, used to update the the ris and dmu utilities on a server that is running an older version of the operating system. Appendix D Describes how to install a hardware update release into a DMS area serving an older version of the operating system.
Reader’s Comments Compaq welcomes any comments and suggestions you have on this and other Tru64 UNIX manuals. You can send your comments in the following ways: • Fax: 603-884-0120 Attn: UBPG Publications, ZKO3-3/Y32 • Internet electronic mail: readers_comment@zk3.dec.com A Reader’s Comment form is located on your system in the following location: /usr/doc/readers_comment.txt Please include the following information along with your comments: • The full title of the manual and the order number.
Conventions The following conventions are used in this manual: % $ A percent sign represents the C shell system prompt. A dollar sign represents the system prompt for the Bourne, Korn, and POSIX shells. # A number sign represents the superuser prompt. % cat Boldface type in interactive examples indicates typed user input. file Italic (slanted) type indicates variable values, placeholders, and function argument names.
1 Introduction to Sharing Software This chapter introduces software sharing and the components that make up a software sharing environment. This chapter includes the following topics: • Software sharing concepts, components, and benefits (Section 1.1) • Describing the software sharing environment (Section 1.2) • Identifying your CD-ROM drive’s device name (Section 1.3) 1.1 Overview A server is a computer system that provides another computer system with required or useful information or resources.
The RIS and DMS utilities share architectural similarities; the primary differences are in the contents of their respective server disk areas. The following list illustrates some of the benefits of sharing software: • You can reduce your software and hardware costs by sharing software between computers. • You are not limited to sharing one piece of software; you can share virtually all of your operating system software.
Ethernet or FDDI using the BOOTP and TFTP protocols to install the base operating system from a server. Layered products can be installed after the client’s operating system is running with the SysMan Menu. DMS clients must be capable of booting over Ethernet or FDDI using the BOOTP and TFTP protocols. Most Alpha workstations and servers have this capability, but some data center servers cannot be configured as DMS clients.
• If you are using a later version of the operating system that uses newer device naming conventions (/dev/disk/cdromNc), use the ls command as shown in the following example: # ls -l /dev/disk/cdrom* brw------1 root system brw------1 root system # 19, 69 Nov 18 06:11 /dev/disk/cdrom0a 19, 71 Nov 18 06:11 /dev/disk/cdrom0c The CD-ROM drive’s unit number is 0, and in the character special device name in this example is /dev/disk/cdrom0c.
2 Remote Installation Services This chapter introduces Remote Installation Services (RIS) and the ris utility, and explains the relationship between RIS servers and clients. The following topics are included: • Understanding RIS concepts and the benefits of using RIS (Section 2.1) • Starting RIS (Section 2.2) • Introducing RIS areas and product environments (Section 2.3) • Understanding RIS client characteristics (Section 2.4) • Registering RIS clients (Section 2.
Figure 2–1: RIS Server and Client Local Area Network Server Client RIS Area Kits Local Disk Local Disk ZK-0268U-AI The server maintains information in the RIS areas about what software kits clients can access. Kits are organized so that RIS can serve different versions of a software product to multiple hardware platforms and operating systems. The server’s RIS area uses the Network File System (NFS) to provide read-only access to RIS clients.
• RIS uses a single set of kit files for all clients having the same architecture. • You can perform a cloned installation on a RIS client, letting you duplicate a similar system installation or configuration. See the Installation Guide — Advanced Topics for information about installation cloning and configuration cloning. 2.2 Starting RIS You always should run the ris utility as superuser.
Figure 2–2: Sample RIS Area Overview /var/adm/ris ris0.alpha product_001 subsets product_002 subsets kit/isl Client Installation Tools ZK-0620U-AI In Figure 2–2, the RIS area /var/adm/ris contains one product environment, ris0.alpha. Each product environment contains products for a specific platform. In Figure 2–2, the target platform is machines using Alpha processors. Multiple product environments can exist in a single RIS area.
it is registered on the server. The installation procedure runs entirely on the client and, after the necessary software is installed, no continuing relationship is required between the RIS server and client. The operating system itself can be among the kits that are available from the server. To install the operating system, the client processor is booted across the network using a minimal generic kernel that is part of the software kit.
• Log in to the RIS client as root or use the su command to gain superuser privileges, then shut down the system to the console prompt ( >>> ). Use the show dev command to show all devices, and look for the hardware address of your network interface in the form xx-xx-xx-xx-xx-xx. For example: >>> show dev . . . ewa0.0.0.0.1000.0 EWA0 xx-xx-xx-xx-xx-xx . . . • Log in to the RIS client as root or use the su command to gain superuser privileges.
3 Preparing the RIS Server This chapter provides the steps you must follow to prepare a RIS server. These steps include the following: 1. Review RIS server/client version compatibility. (Section 3.1) 2. Plan disk space for RIS. (Section 3.2) 3. Install the operating system on the RIS server. (Section 3.3) 4. Set up a local area network. (Section 3.4) 5. Load and register the server extensions license. (Section 3.5) 6. If necessary, prepare RIS for running on a server that has C2 security enabled.
If you do not know your CD−ROM’s unit number, see Section 1.3. • If you are using a newer version of the operating system that uses newer device naming conventions (/dev/disk/cdromNc), use a mount command similar to the following example: # mount -rd /dev/disk/cdrom0c /mnt The previous example uses a CD−ROM drive that is unit 0 and specifies /mnt as the mount point; if your drive is a different unit, substitute the device special file name for that unit.
3.2 Planning Disk Space for RIS Before beginning to set up a RIS area, you must calculate the amount of disk storage required for the software subsets in the RIS areas on the server. If space on the server’s system disk is an issue and your server’s distribution media is a CD−ROM, you might want to create symbolic links from the RIS server area to the software on the CD−ROM. Section 4.
Your output is similar to the following: OSFCLINET520 installed Basic Networking Services (Network-Server/Communications) OSFINET520 installed Additional Networking Services (Network-Server/Communications) OSFOBSOLETE520 installed Obsolete Commands and Utilities (Obsolete Components) OSFRIS520 installed Remote Installation Service (Network-Server/Communications) The Basic Networking Services subset is mandatory and is installed as a mandatory subset when you install the base operating system.
3.6 Preparing RIS for C2 Security If your RIS server will have C2 security enabled, the ris user file must be changed to ensure that the ris password does not expire and deny client access. Perform the following steps on the RIS server as superuser to modify the ris user file if you are going to use RIS with C2 security enabled: 1. Edit the file /tcb/files/auth/r/ris. Each field is delimited by a colon (:). 2. Set the current password field u_pwd to an asterisk (*). 3.
4 Setting Up a RIS Area This chapter describes how to use the ris utility to configure a RIS server. This chapter includes the following topics: • Establishing a new RIS area with the ris utility (Section 4.2) • Installing software kits in an existing RIS area (Section 4.3) • Including hardware product kits into an existing RIS area (Section 4.4) • Using a RIS area mounted on NFS (Section 4.5) • Modifying the /etc/exports file, if necessary, to export RIS areas (Section 4.6) 4.
• If your server is running the current version of the operating system, use a command similar to the following example: # mount -rd /dev/disk/cdrom0c /mnt The previous example mounts a CD-ROM drive that is device 0 on the mount point /mnt. If your drive is a different device, substitute the correct device name. The mount point does not have to be /mnt. See Section 1.3 if you do not know the CD-ROM drive’s device name.
The RIS Utility Main Menu does not display option letters for menu items that cannot be accessed. As you add environments, software, and clients to the system, other menu options become available. 4. Enter i to select Install software products. You see the following prompt: RIS Software Installation Menu: 1) 2) 3) Install software into a new area Add software into an existing area Return to previous menu Enter your choice: 5. Enter 1 to select Install software into a new area.
Choose one of the following options: 1) 2) Extract software from /mnt/ALPHA/BASE Create symbolic link to /mnt/ALPHA/BASE Enter your choice: – If you select Create symbolic link, the ris utility creates symbolic links from the RIS area to the subset directories on the specified source. Disk space planning is not required because the subsets do not reside in the RIS area. The source must be on line and mounted for clients to access the subsets. Unlike subset extraction, no subset selection is required.
The 74) 75) 76) following choices ALL mandatory and MANDATORY subsets CANCEL selections override your previous selections: all optional subsets only and redisplay menus Choices (for example, 1 2 4-6): 74 The following subsets will be loaded: . . . {selected subset list - all mandatory & optional in this example} . . . Are these the subsets that should be loaded (y/n) ? If you enter y, the ris utility loads the subsets.
Choices without key letters are not available. a) d) i) ) ) ) s) x) ADD a client DELETE software products INSTALL software products LIST registered clients MODIFY a client REMOVE a client SHOW software products in remote installation environments EXIT Enter your choice: 3. Enter i to select INSTALL software products.
4.4 Including Hardware Product Kits into a RIS Area In addition to the base operating system, you may need to install hardware product kits onto client systems from the RIS server. For example, a hardware product kit can be a third-party driver for a device not supported in the base operating system. The ris utility lets you include hardware product kits into a RIS area for subsequent installation onto a client system.
RIS Software Installation Menu: 1) 2) 3) Install software into a new area Add software into an existing area Return to previous menu Enter your choice: 4. Enter 2 to select Add software into an existing area. You see the following prompt, including all available RIS environments: You have chosen to add a product to an existing environment. Select the remote installation environment: 1) /var/adm/ris/ris1.alpha ’Tru64 UNIX V5.1A Operating System (Rev nnn )’ Enter your choice or press RETURN to quit: 5.
You see the following prompt: Choose one of the following options: 1) 2) Extract software from /HWKIT/MYVGA/kit Create symbolic link to /HWKIT/MYVGA/kit Enter your choice: 9. Select 1 to extract the software. You see the following prompt: The subsets listed below are optional: There may be more optional subsets than can be presented on a single screen. If this is the case, you can choose subsets screen by screen or all at once on the last screen.
4.5 Using a RIS Area Mounted on NFS You can use an NFS mount point to install software from an extracted RIS area on another system or from an operating system distribution CD−ROM mounted on another system. You can use this method to create an extracted RIS area with the base operating system subsets. _____________________ Caution _____________________ The information in this section can be used only if you are installing software on a client after you install the operating system software.
When you create the risN.arch RIS area, the ris utility supplies you with a name based on the choices you make when you create the RIS area. The server’s /etc/exports file must include an entry for each RIS area that it is exporting. When you create a RIS area, the ris utility automatically edits the /etc/exports file and adds the correct entry for that area. However, if you modify the path to a RIS area, you also must modify the corresponding line in the /etc/exports file.
5 Booting a RIS Client You must register a RIS client on the RIS server before you can use RIS to install the operating system on the RIS client. If you use RIS to install the operating system on a client, the client must boot across the network by issuing a BOOTP request. This chapter includes the following topics: • Describing remote boot files and daemons (Section 5.1) • Explaining the remote boot process flow (Section 5.2) 5.
Table 5–1: Remote Boot Files and Daemons (cont.) Name Description /usr/sbin/inetd The Internet server daemon /usr/sbin/joind The BOOTP server daemon (handles both BOOTP and DHCP requests, if configured) /usr/sbin/tftpd The tftpd server daemon 5.1.1 The Internet Daemon and Configuration File The inetd internet daemon starts networking-related daemons on the system. Some of these daemons, such as tftpd, are related to RIS; others, such as fingerd, are not.
Example 5–1: Sample /etc/bootptab File .ris.dec:hn:vm=rfc1048 1 .ris0.alpha:tc=.ris.dec:bf=/var/adm/ris/ris0.alpha/vmunix: 2 atlanta:tc=.ris0.alpha:ht=ethernet:gw=nn.nn.nnn.nnn: \ ha=nnnnnnnnnnnn:ip=nn.nn.nnn.nnn : 3 .ris93.alpha:tc=.ris.dec:bf=/ris/ris93.a/vmunix: \ rp="ds9:/ris/ris93.a/product_001": 4 1 2 The .ris.dec entry defines characteristics common to all clients.
4 • ha: Client’s network hardware address • ip: Client’s IP address The .ris93.alpha entry defines characteristics for the current version of the operating system RIS area. The fields specify the following: • tc: Table continuation The tc field lets you follow pointers back to common entries. For example, the tc entry for .ris93.alpha in Example 5–1 points to the .ris.dec entry. The .ris.dec entry contains the common hardware type (ht) and vendor specific (vm) information. The .ris93.
3. The BOOTP server daemon compares the Ethernet hardware address in the packet with the client registration information stored in its /etc/bootptab file to determine if the client requesting the remote boot is registered to the RIS server. 4. If a matching address is found in the /etc/bootptab file, the BOOTP daemon sends the client an information packet that includes the server’s Internet address, the client’s Internet address, and the name of the file to be loaded from the server.
6 Managing RIS Clients and Environments Use the ris utility to manage RIS environments and clients. This chapter includes the following topics: • Preparing to register RIS clients (Section 6.1) • Adding a client with the ris utility (Section 6.2) • Adding a client from the command line (Section 6.3) • Modifying a client (Section 6.4) • Removing a client (Section 6.5) • Listing registered clients (Section 6.6) • Listing software products in RIS areas (Section 6.
• The client’s hardware network address • The address of the gateway from the client to the server, if the server and client are on different networks • The type of network where the client is connected: Ethernet, FDDI, or Token Ring • Whether or not you want to use a profile set during installation (see Chapter 7 for information about profile sets) 6.1.
) ) s) x) MODIFY a client REMOVE a client SHOW software products in remote installation environments EXIT Enter your choice: 3. Enter a to select ADD a client. You see the following prompt: You have chosen to add a client for remote installation services. The following conditions must be met to add a client: 1. You must know the client processor’s hostname. 2. The client’s hostname must be in your system’s host database(s). 3.
Select the remote installation environment: 1) /usr/var/adm/ris/ris2.alpha ’Tru64 UNIX V5.1 Operating System (Rev nnn)’ 2) /usr/var/adm/ris/ris3.alpha ’Tru64 UNIX V5.1A Operating System (Rev nnn)’ Enter your choice or press RETURN to quit: a. Enter the RIS environment where you want to add the client, for example: 2. You see a prompt similar to the following: Select one or more products for the client to install from /usr/var/adm/ris/ris3.alpha: Product Description 1 ’Tru64 UNIX V5.
___________________ Note ___________________ You must enter all for the new hardware support to be loaded during the installation process. You see a prompt similar to the following: You chose the following products: 1 2 ’Tru64 UNIX V5.1A Operating System (Rev nnn )’ with ’MYVGASTATIC software version 1’ ’MYVGASTATIC software version 1’ Is that correct? (y/n) [y]: 7. Enter y to confirm your selection. What happens next depends upon whether profile sets reside on the RIS server.
9. Select the type of network where the client is connected, for example: 1 for Ethernet. • If the server and client are connected to the same network, the ris utility proceeds to the next step. • If the server and client are on different networks, the ris utility looks at the /var/adm/ris/gateways file and displays the gateway information needed for the client to connect to the server: Using nn.nn.nnn.nnn for gateway address between client and server subnet.
6.3 Adding a RIS Client from the Command Line You can add a single RIS client from the command line by invoking the ris utility with its −a option. Other options supply the network address, path, and product list. Use the following syntax for the ris utility: /usr/sbin/ris -a clientname -h network-address -p path,product [ ,product...] For example: # /usr/sbin/ris -a fargo -h xx-xx-xx-xx-xx-xx -p ris0.alpha,product_1 If the client is a cluster alias, then the -h option should be "cluster alias". 6.
4. Enter the client name, for example: client01. You see a prompt similar to the following: Select the remote installation environment: 1) /var/adm/ris/ris10.alpha ’Tru64 UNIX V5.1 Operating System ( Rev nnn )’ 2) /var/adm/ris/ris11.alpha ’Tru64 UNIX V5.1A Operating System ( Rev nnn )’ Enter your choice or press RETURN to quit: 5. Enter the number of the RIS environment you want, for example: 2.
Enter your client’s hardware network address, or press Return if the default is correct. The default is the client’s existing hardware address. See Section 2.6 for information about determining a system’s hardware network address. You see a message similar to the following: Client client01 has been modified.
Enter your choice: 3. Enter r to select REMOVE a client. You see a prompt similar to the following: You have chosen to remove a client from the remote installation services. Enter the client processor’s hostname or press RETURN to quit: 4. Enter the client’s host name, for example: client01. You see a prompt similar to the following: Remove client01? (y/n) [n]: 5. Enter y to confirm the removal. You see the RIS Utility Main Menu. You also can use a ris command line to remove several clients at once.
The following clients are registered for /var/adm/ris/ris11.alpha: client01 client03 client04 6.7 Listing Products in RIS Server Areas Follow these steps to list the available product in RIS server areas: 1. Log in as root or use the su command to gain superuser privileges. 2. Start the ris utility: # /usr/sbin/ris You see the RIS Utility Main Menu: *** RIS Utility Main Menu *** Choices without key letters are not available.
6.8 Deleting Products from RIS Server Areas To delete one or more of the current products in a RIS area, invoke the ris utility and choose the option to delete products. The utility asks you to choose a RIS area and then guides you through the procedure to delete products. 1. Log in as root or use the su command to gain superuser privileges. 2. Start the ris utility: # /usr/sbin/ris You see the RIS Utility Main Menu: *** RIS Utility Main Menu *** Choices without key letters are not available.
Enter one or more choices as a space-separated list (for example, 1 2 3) or "all" for all products: 5. Enter the number of the product you want to delete, for example: 1. You see a prompt similar to the following: You chose the following products: 1 ’Product 03’ Is that correct? (y/n) [y]: 6. Enter y to confirm your selection. RIS does not keep empty RIS areas. If there is only one product in the RIS area you selected, the ris utility verifies your intentions. a.
Example 6–1 shows a typical /var/adm/ris/gateways file: Example 6–1: Sample /var/adm/ris/gateways File 16.168.64:16.168.64.1 16.69.240:16.69.224.199 16.140.144:16.140.144.2 16.69.144:16.69.144.199 After you correct the entries in this file, you must use the ris utility to remove all clients using the incorrect gateway address and register them again.
7 Managing RIS Profile Sets A profile set is a logically organized subdirectory of the /var/adm/ris/clients/sets directory on a RIS server. It contains configuration description files (CDFs) and user-supplied files that can be invoked during a Full Installation and used for Installation Cloning. When you register a RIS client for a RIS area, you can specify a profile set that contains CDFs or user-supplied files that you want to execute when you install software from the RIS area.
• User-supplied files are a way to extend and customize the installation process, and can contain scripts, executables, or programs. The Full Installation and Update Installation processes execute user-supplied files at predetermined points during the installation. User-installed files may include some or all of the following files: • – preinstall – update_preinstall – postload – update_postload – postreboot Any files called by the user-supplied files.
3. Create the profile set directory. For example: # mkdir engineering 4. Go to the newly created directory to ensure that the necessary files are copied to the correct destination. For example: # cd engineering 5. Copy the CDFs, any user-supplied files, and all other related files from your working area to the new engineering profile set directory using a copy tool such as cp, ftp, or rcp.
Example 7–1: Sample RIS Client Profile Set Registration (cont.) Enter your choice: a You have chosen to add a client for remote installation services. The following conditions must be met to add a client: 1. You must know the client processor’s host name 2. The client’s host name must be in your system’s host database(s). 3. You must know whether the client is on an Ethernet, FDDI, or Token Ring network. 4.
Example 7–1: Sample RIS Client Profile Set Registration (cont.) Network type: 1) Ethernet or FDDI 2) Token Ring Enter your choice: 1 Enter the client processor’s hardware network address. example, 08-00-2b-02-67-e1: xx-xx-xx-xx-xx-xx For Client pubs08 has been added.
Converting old cdf directory to new sets directory format... CDF File acctng moved to set acctng and renamed install.cdf CDF File acctng.cdf moved to set acctng1 and renamed install.cdf CDF File acctng1.cdf moved to set acctng11 and renamed install.cdf CDF File acctng.cdf2 moved to set acctng12 and renamed install.cdf done After the old CDFs are converted to profile sets, these messages are not displayed again. 7.
8 Troubleshooting RIS This chapter contains information to help you troubleshoot problems with your RIS system. These problems are grouped into the following categories: • RIS lock files (Section 8.1) • Client password expiration (Section 8.2) • Root file system mounting (Section 8.3) • RIS client registration (Section 8.4) • RIS server response (Section 8.5) 8.
8.2 Client Password Expiration If the RIS server is using C2 security and the RIS password has been set to allow expiration, it is possible for the RIS clients to be denied service. If the RIS client receives a message similar to the following, the RIS password on the server probably has expired: Cannot find the name for client using bin/getname. Check with the system manager of your RIS server To fix this problem, see Section 3.6. 8.
8.4.1 No Prompt for Client Hardware Address The server requires a client’s hardware address in order to boot the client over the network. The ris utility prompts you for the client’s address during the registration process. If it does not, check the following: • If the RIS area is linked to a CD−ROM Check that the CD−ROM that is the target of the links is mounted. • If the RIS area is serving a version of the operating system prior to Version 3.
• If the hardware address you entered is correct, deregister and reregister the existing client (in this example, albany). • If the existing client is not registered, contact your RIS system administrator. 8.4.3 Cloned Client Registration A CDF is created during a Full Installation. To use the CDF for Installation Cloning, the hardware configuration and the software subsets to load must be substantially similar.
8.4.5 Client Not in RIS Database If a message appears on the client’s console while you are performing a RIS installation that states that the client is not in the RIS database, look at the following on the server: • As shown in Section 8.5, look at the /var/adm/ris/clients/risdb file to see if the client’s name is entered correctly. If it is not, use the ris utility to add or modify the client’s registration.
8.5 RIS Server Response Problems with RIS server response comprise several categories. The following topics are discussed in this section: • Servers using the bootpd daemon (Section 8.5.1) • Servers using the joind daemon (Section 8.5.2) • Loading an incorrect kernel file (Section 8.5.3) Boot failures often occur because the RIS server has invalid information.
3. Use the following command to find the process IDs for the Internet daemons. You see output similar to the following: # ps x | grep -E "inetd|bootpd" 228 ?? I 0:00.93 /usr/sbin/inetd 243 ?? I 0:00.91 /usr/sbin/bootpd 9134 p2 S 0:00.23 grep -E inetd|bootpd 4. Send a HUP (hangup) signal to the inetd daemon so it will reread the /etc/inetd.conf configuration file and kill the bootpd daemon. You must kill the inetd daemon before you kill the bootpd daemon.
Example 8–1: Sample daemon.log File (cont.) Jul 28 16:35:47 stlouis bootpd[1228]: read 3 entries from "/etc/bootptab" Jul 28 16:35:47 stlouis bootpd[1228]: request from hardware address \ 4 nnnnnnnnnnnn Jul 28 16:36:08 stlouis bootpd[1228]: request from hardware address \ 5 nnnnnnnnnnnn Jul 28 16:36:08 stlouis bootpd[1228]: found: host1.xsamplex.com (nnnnnnnnnnnn) at (nn.nn.nnn.nnn) Jul 28 16:36:08 stlouis bootpd[1228]: file /var/adm/ris/ris0.alpha/\ vmunix.host1.xsamplex.
2. Enter the following command to determine the current setting of JOIND_FLAGS: # rcmgr get JOIND.FLAGS 3. Enter the following command to stop the joind daemon: # /sbin/init.d/dhcp stop 4. Enter the following commands to restart the daemon with debugging turned on. Use the JOIND_FLAGS argument to indicate debugging is turned on. # rcmgr set JOIND_FLAGS y -dx Where x is the level of debugging. A value from 0 to 9 is valid. Where y is the previously determined setting of the JOIND_FLAGS. # /sbin/init.
9 Dataless Management Services Dataless Management Services (DMS) lets client systems share the /usr file system on a centrally administered server over a network while still maintaining their own root ( /) and /var file systems that reside on the DMS server. With DMS, you can save disk space by sharing the actual operating system software between systems. A DMS server stores the operating system software in a DMS area.
9.2 DMS Benefits The advantages of installing DMS include the following: • Less disk space is required on client systems. By sharing the /usr area, you eliminate the need for disk space to hold a separate /usr area for each client. For Alpha systems, you can save more than 425 megabytes (Mb) for each client. • Installation and setup of servers and clients are done by automated scripts, thereby simplifying the task of the server system administrator.
A DMS client’s system disk space (root and /usr areas) is physically connected to the server instead of to the client. The client accesses that disk area through a LAN connection with the server. Each DMS client is booted across the network from its private root area on the server. After it is booted, the client continues to use its root files and /usr files from the server’s DMS area. These files appear to the client as if they were on local disks, as shown in Figure 9–1.
copied to each client system. The /usr file system is read only and is shared among all client systems registered to the environment. Figure 9–2: Environment Portion of DMS Area /var/adm/dms dms1.alpha dms0.alpha root shared /usr root shared /usr ZK-0935U-AI The root file system contains copies of the kernel, .vmunix, vmunix and other primary system files. These primary files can be in either new form (files supplied in the operating system distribution kit and prefixed with .new..
9.3.3 Client Portion of DMS Area A DMS client area for individual DMS client systems also resides in a DMS area. Figure 9–3 shows a DMS client area named /clients. Place this DMS client area in its own partition after you calculate the required size with the worksheets in Appendix B. Next, add the mount point of the /clients DMS client area to the /etc/fstab file.
Figure 9–4: Client Views of the DMS Area Server ClientA shared /usr Client A ClientB Client B root root /usr /usr ZK-0937U-AI In Figure 9–4, the small boxes represent what the clients think they see; the arrows show how the real disk areas on the server are mounted by the client to produce this view. Clients can be timesharing systems or workstations.
10 Preparing DMS Servers and Clients This chapter describes how to get DMS servers and clients ready to run in a dataless environment. Perform the following steps to prepare DMS servers and clients: 1. Meet requirements for DMS servers. (Section 10.1) 2. Meet requirements for DMS clients. (Section 10.2) 3. Allocate disk partitions for DMS. (Section 10.3) 4. Set up a local area network. (LAN) (Section 10.4) 5. Set up a Network File System. (NFS) (Section 10.5) 6.
See Software License Management for more information about software licensing. • The DMS server must be able to install software into the DMS area: – The DMS server can have a CD−ROM drive to install software subsets for one or more specific products from the CD−ROM to the DMS area on the server. – The DMS server can use a Network File System (NFS) mount point to install software from a Remote Installation Services (RIS) area or an operating system distribution CD−ROM from another processor.
• DMS clients must be capable of booting over Ethernet or FDDI using the bootp and tftp protocols. This is the same requirement to be able to install the operating system from a RIS server. Most Alpha workstations and deskside servers have this capability, but most data center servers would not be configured as DMS clients. Look at your system’s hardware documentation to determine whether it supports bootp and tftp over Ethernet or FDDI. • The client must not be registered on another RIS or DMS server.
# ps ax | grep -E "portmap|mountd|nfsd|nfsiod" If these daemons are not all running, start the inoperative ones. See the appropriate reference pages for information about starting these daemons. For example, enter the following command to display the portmap(8) reference page: # man portmap 10.6 Planning Disk Space for DMS You must calculate the amount of disk space required to ensure that you have enough space in the DMS areas in which the dmu utility will be created.
Each dmsN .alpha environment also can contain additional software for the clients registered to access that environment. Section 11.2 describes how to install software in DMS environments.
Reserve additional space for any other software products you plan to install later. These products’ space requirements must be factored into the 10 percent overhead allocation. 10.6.2 Estimating Disk Space for Clients You must reserve disk space in the /clients file system on the server for clients’ root areas. The amount of disk space required depends upon the type of kernel build you choose for the client.
kernel objects. If you choose a partial build, allow an additional 15 Mb for each client’s root area. The space required by individual clients will not be the same, but you can add all the needed spaces together to arrive at the total requirement for the /clients area. You also must remember to reserve additional space for clients that add files to their root areas. 10.
10.8.1 Obtaining DMS Client Information You need to know the following information about each processor you plan to add as a client to a /var/adm/dms/dmsN .alpha environment and to register the client with the appropriate naming service: • The host name Only lowercase letters (a-z ), numerals ( 0-9), and the period ( .) and dash (-) characters are permitted in host names, which must begin with a letter.
file when you initially set up your LAN. The Network Configuration Application is described in the Network Administration: Connections manual. You also can place the host name and IP address in the /etc/hosts file by using a text editor such as vi. The host name and IP address for each client processor must be unique. See the Network Administration: Services manual for information about setting up NIS and the BIND Configuration Application. 10.
11 Setting Up a DMS Environment This chapter describes how to use the dmu utility to add software to a DMS environment and how to configure the environment. The following topics are discussed: • Ensuring version compatibility between DMS servers and clients (Section 11.1) • Installing software into a new DMS area (Section 11.2) • Adding software into an existing DMS environment (Section 11.3) • Customizing and configuring a DMS environment (Section 11.4) • Installing WLS support in DMS (Section 11.
3. Use the mount command to update DMS on the server, as in the following example (using /mnt as the mount point): # /mnt/isl/utilupdate -d -m /mnt • In this example, the -d copies several files from the distribution CD to the server’s /usr/sbin directory. This ensures DMU compatibility with the operating system. The -m directory is the mount point of the distribution media. In this example, directory is /mnt, and is a required parameter.
This example uses a CD-ROM drive that is unit 4 and specifies /mnt as the mount point. If your drive is a different unit, substitute the correct device name. The mount point does not have to be /mnt. See Section 1.3 if you do not know the CD-ROM drive’s unit number. ____________________ Note _____________________ You can use a Network File System (NFS) mount point to install software from a Remote Installation Services (RIS) area or Operating System Volume 1 CD-ROM from another processor. See Section 4.
Enter your choice: 5. Enter 1 to select Install software into a new area. You see the following prompt: You have chosen to establish a new remote dataless environment. Enter the device special file name or the path of the directory where the software is located (for example, /mnt/ALPHA/BASE): 6. Enter the software location, for example: /mnt/ALPHA/BASE. • If your distribution media is CD−ROM mounted on /mnt, the directory where the software is located is /mnt/ALPHA/BASE.
. . . Are these the subsets that should be loaded (y/n) ? If you enter y, the dmu utility loads the subsets. If you enter n, the list of subsets is displayed again and you can restart your selection process. The new DMS environment is located in the /usr/v ar/dms/dmsN.alpha directory. If there is not enough disk space to perform the installation, you see a prompt similar to the following: fitset: file system /usr needs 74683 Kbytes more to install the software specified.
11.3 Adding Software to an Existing DMS Environment Perform the following steps to add software to an existing DMS environment: 1. Log in as root to each DMS client registered to the DMS environment or use the su command to gain superuser privileges. 2. Use the shutdown command to shut down the DMS client. ___________________ Caution ___________________ If DMS clients that mount the usr area of the target /var/adm/dms/dmsN .
6. Enter i to select INSTALL software environments. You see the DMS Software Installation Menu: DMU Software Installation Menu: 1) 2) 3) 4) Install software into a new area Add software to an existing area Perform configuration phase on an existing area Return to previous menu Enter your choice: 7. Enter 2 to select Add software to an existing area. You see a prompt similar to the following: You have chosen to add a product to an existing environment. The existing environment is /var/adm/dms/dms0.
9. Select the subsets that you want to extract; the dmu utility displays your list for confirmation. For example: The following subsets are mandatory and will be installed automatically unless you choose to exit without installing any subsets: . . . {mandatory subset list} . . . Optional subsets are listed below. There may be more optional subsets than can be presented on a single screen. If this is the case, you can choose subsets screen by screen, or all at once on the last screen.
11.4 Configuring DMS Environments After you install software into a new or existing DMS environment, you must configure the environment. Configuring the environment includes the following steps: 1. Customizing the .proto.. system files (Section 11.4.1). This step is optional; you do not have to customize these files for the environment. This step is performed outside of the dmu utility. 2. Building the environment’s kernel (Section 11.4.2).
Table 11–1: List of /etc/.proto.* Files .proto..TIMEZONE .proto..lprsetup.dat .proto..acucap .proto..magic .proto..autopush .proto..motd .proto..binlog.conf .proto..networks .proto..conf .proto..ntp.conf .proto..ddr.db .proto..passwd .proto..ddr.dbase .proto..phones .proto..dhcptab .proto..profile .proto..dvrdevtab .proto..proto.disktab .proto..exports .proto..protocols .proto..fstab .proto..rc.config .proto..ftpusers .proto..remote .proto..gen_databases .proto..rpc .proto..
11.4.2 Configuring the DMS Environment After you modify the .proto.. files, use the following procedures to configure the DMS environment: 1. Log in to the DMS server as root or use the su command to gain superuser privileges. 2. Enter /usr/sbin/dmu to start the dmu utility.
environment. Do you want to (c)ontinue or (r)eturn to the main menu? (c/r) [c]: • If you enter r, the dmu utility returns to the DMU Main Menu to let you exit the dmu utility and modify the /etc/.proto.. files. • If you enter c to continue, the dmu utility displays progress messages as it configures each software subset, similar to the following output: Configuring "Base System " (OSFBASE505) Configuring "Base System-Hardware Support" (OSFHWBASE505) . . . {subset list} . . .
5. Select INSTALL software environments. You see the DMU Software Installation Menu. 6. Select Add software to an existing area. If you have more than one DMS environment, you see a list of available DMS environments and you are prompted to select the environment for adding software. 7. Select the DMS area where the operating system is installed. You are prompted for the location of the software. 8. Enter the full pathname of the device special file or mount points for the distribution media.
12 Managing DMS Clients and Environments This chapter describes how to use the dmu utility to manage Dataless Management Services (DMS) environments and clients. The information in this chapter includes the following topics: • Locating and interpreting the DMS client database file (Section 12.1) • Adding a client to a DMS environment (Section 12.2) • Booting a DMS client (Section 12.3) • Deleting a DMS environment (Section 12.4) • Modifying a DMS client (Section 12.
When you use add, modify, or delete a DMS client from the DMU Main Menu, the client’s entry in the dmsdb file is added, modified, or deleted, respectively. 12.2 Adding a DMS Client The information you need to add a DMS client is shown in the Client Setup Worksheet in Appendix B. Fill out a worksheet for each client you want to add before you use the dmu utility to add clients to a DMS environment.
3. You must know the mask. 4. You must know the 5. You must know the client. 6. You must know the address. 7. If the client and you will need the client can sue to client’s interface type, subnet type of kernel build area. swap device and partition on the client’s hardware Ethernet or FDDI the server reside on different subnets, address of the gateway(s) that the communicate with the server. Do you want to continue? (y/n) [y]: 4. Enter y to continue.
7. Enter the swap device and partition on the DMS client. You see a prompt similar to the following: Enter the swap device drive type for dsk0b. [RZ26]: 8. Enter the swap device drive type for your previous entry. You see a prompt similar to the following: Enter the network interface for client1 (nn.nn.nnn.nnn) [ln0]: 9. Enter the DMS client’s network hardware address. You see a prompt similar to the following: Enter the subnet mask for ln0. [255.255.255.0]: 10.
You see a prompt similar to the following: Enter the type of kernel build area for client1. You may select one of [F]ull, [P]artial, [N]one or [H]elp for more information. [P]: 11. Enter the letter corresponding with the type of kernel build that you want. You see a prompt similar to the following: You have specified the following configuration for client1: ROOT: /clients/client1 SWAP_DEVICE: /dev/disk/dsk0b SWAP_TYPE: RZ26 BUILD_TYPE: Partial INTERFACE: ln0 (nn.nn.nnn.nnn) SUBNET_MASK: 255.255.255.
You see a prompt similar to the following: Checking file system space required for client root and var file systems. • If there is not enough free space available to create the file systems, you see a prompt similar to the following: There is not enough free space in /clients to create the root and var file systems for client1. client1 has not been added.
When the client system boots, the client system administrator is prompted to enter a superuser password: *** SUPERUSER PASSWORD SPECIFICATION ** Changing password for root. Enter root password: Retype root password: System information is displayed while the client system boots. When the Common Desktop Environment (CDE) login window or the login prompt appears, enter root as the login name. At the prompt for a password, enter the superuser password that was specified previously. 12.
3. Enter d to select DELETE software environments. You see a prompt similar to the following example, which lists three DMS environments: Select the remote dataless environment: 1) /var/adm/dms/dms0.alpha ’Tru64 UNIX VAAA Operating System (Rev nnn)’ 2) /var/adm/dms/dms1.alpha ’Tru64 UNIX VBBB Operating System (Rev nnn)’ 3) /var/adm/dms/dms2.alpha ’Tru64 UNIX VCCC Operating System (Rev nnn)’ Enter your choice: 4.
The dmu utility also prompts you to remove the root and /var file systems for each client registered to the environment. After you confirm your selections, the dmu utility proceeds to delete the DMS environment and all its registered clients. After the DMS environment is deleted, the dmu utility returns to the DMU Main Menu. 12.5 Modifying Client Information The dmu utility lets you modify the network hardware address of a client. See Section 1.
You see a prompt similar to the following, with the DMS client’s current hardware network address as the default response: Enter the client processor’s hardware network address. For example, 08-00-2b-02-67-e1 [xx-xx-xx-xx-xx-xx]: ___________________ Caution ___________________ The dms utility checks the format of the address you enter but does not check its validity. 5. Enter the DMS client’s hardware network address or press Return to accept the default.
i) l) m) r) s) x) INSTALL software environments LIST registered clients MODIFY a client REMOVE a client SHOW software environments EXIT Enter your choice: 5. Enter r to select REMOVE a client, and follow the instructions in Section 12.6. You see the DMU Main Menu again. 6. Enter a to select ADD a client, and follow the instructions in Section 12.2. 7. Restart the DMS client. 12.6 Removing a Client Follow these steps to remove a client from a DMS environment: 1.
6. Enter the DMS client’s host name, for example: client5. You see a prompt similar to the following: Remove client5? (y/n) [n]: 7. Enter y to delete the client.
You see output similar to the following: The following clients are registered for /var/adm/dms/ dms0.alpha: client1 client2 client3 The following clients are registered for /var/adm/dms/ dms1.alpha: client4 client5 client6 The following clients are registered for /var/adm/dms/ dms2.alpha: client7 client8 client9 12.8 Showing Software Environments The dmu utility lets you display a list of the current DMS environments: 1. Log in to the DMS server as root or use the su command to gain superuser privileges.
i) l) m) r) s) x) INSTALL software environments LIST registered clients MODIFY a client REMOVE a client SHOW software environments EXIT Enter your choice: 12.9 Maintaining the DMS Environment The following sections contain information about maintaining the DMU server area, and includes the following topics: • Controlling root file system growth (Section 12.9.1) • Listing installed software subsets (Section 12.9.2) • Removing software subsets (Section 12.9.3) 12.9.
12.9.3 Removing Subsets Use the setld utility to remove software subsets from a dmsN .alpha area. For example, if you want to remove the Document Preparation Tools Extensions subset, OSFDCMTEXT505, use a command similar to the following: # setld -D /var/adm/dms/dms0.alpha/root -d OSFDCMTEXT505 The Installation Guide contains a list of all software subsets.
13 Troubleshooting DMS This chapter contains information to assist you in troubleshooting problems with DMS. If a DMS client has trouble booting, you can check several aspects of server operation to ensure that the server’s end of the network connection is functioning properly. These are grouped into the following categories: • Removing DMS lock files (Section 13.1) • Checking NFS server status (Section 13.2) • Checking network daemon status (Section 13.3) • Checking directory exports (Section 13.
13.2 Checking NFS Server Status Some DMS client boot problems occur if the DMS server is not a Network File System (NFS) server. To check whether or not a DMS server is an NFS server, enter the following command on the DMS server: # rcmgr get NFSSERVING If the response is a 1, the system is an NFS server. If the response is a 0, the system is not an NFS server. Run nfsconfig to configure the server to be an NFS server. See nfsconfig(8X) for more information. 13.
13.5 Checking Version Compatibility If you cannot execute commands on the DMS client and the DMS server and client are running different versions of the operating system, look to see if you copied the client’s dmu version to the server. See Section 11.1 for more information. 13.
4. Shut down and reboot the DMS client. You may encounter a situation where the client cannot boot to multi user mode because the client machine has insufficient memory and the disk specified to serve as the swap volume does not have the correct file system type in the disklabel. If this occurs, it will be necessary to reboot the client to single-user mode and set the disklabel correctly. 1. At the “>>>” prompt type: >>>boot -flag s {network boot device} 2.
A RIS Worksheet This appendix contains a worksheet for recording setup information for the RIS client. Make as many copies of this worksheet as you need.
RIS Client Configuration Worksheet Network System name: Network hardware address: IP network address: Internet domain: RIS Info Client operating system: Processor architecture: Server system name: RIS environment name: Products: Duplication Duplicate another client? No Yes Name of client to copy: ZK-0618U-AI RIS Worksheet A–2
B DMS Worksheets This appendix contains three DMS worksheets. Two of the worksheets are used to calculate the amount of disk space required for the DMS environments and /clients area. The third worksheet is used to record individual DMS client information. Make as many copies of these worksheets as you need. The worksheets are printed on only one side of the page so you can photocopy them easily.
Disk Space Required for Dataless Environments Use this worksheet to calculate the amount of space required for a single /var/adm/dms file system. If you want multiple /var/adm/dms environments, you must prepare a separate sheet for each environment. Each environment has a number: the first is /var/adm/dms/dms0.alpha, the second is /var/adm/dms/dms1.alpha, and so on. Fill in the number of this /var/adm/dms/dms n.alpha environment on the top line. Disk Space for the /var/adm/dms/dms .
Disk Space for the /clients File System Using the appropriate memory size information for your clients, follow these steps to find how much space you need for the /clients area. Step 1 To allow at least 30 megabytes(MB) for an individual client’s root area, multiply the number of clients in the /clients area by 30. Number of clients ( Step 2 MB ) x 15 = Allocate an additional 100 MB for clients that have full kernel build areas.
DMS Client Setup Worksheet This worksheet is used for recording the information you need to know when adding a client to a DMS environment using the ADD a client menu option. If you are adding multiple clients, you must prepare a separate sheet for each client. Fill in the client’s system name (host name) on the next line. Registration Information for DMS Client Network The client’s Ethernet or FDDI hardware address in the form of six two-character groups separated by minus signs.
C Using the utilupdate Utility Use the utilupdate utility provided on your distribution media to update the ris and dmu utilities on a server that is running an older version of the operating system. This enables you to serve the latest version of the operating system to client systems.
D Hardware Update Releases in DMS A hardware release is a version of the operating system that includes new or updated kernel modules to support hardware devices. In the current version of the operating system, the function of hardware releases has been superseded by the New Hardware Delivery (NHD) process and, to a lesser degree, hardware product kits. This appendix includes the following topics: • An overview of hardware releases, describing how to prepare for the installation (Section D.
– • Which directory in the RIS area conains the operating system software. Examine the /usr/var/adm/ris/risN .alpha/ProdNames file to determine this directory. If you install from a base operating system CD-ROM mounted on the mount point /mnt, the /mnt/ALPHA/UPDATE directory contains the operating system hardware update release. D.2 Installing a Hardware Release into a DMS Area Follow these steps to install the operating system hardware update release into an existing DMS area: 1.
Glossary This glossary defines terms and concepts related to software sharing. B BIND The Berkeley Internet Name Domain. A distributed database lookup service that allows you to distribute the hosts database network-wide. boot command The boot command performs the initial installation and bootstrap of the operating system. You invoke the boot utility from the >>> console prompt. See to your hardware documentation for information about valid parameters for the boot utility on your system.
the cluster member accessing the file. CDSLs make it possible to maintain system-specific configuration and data files on file systems shared by the cluster. See also cluster, cluster member, member-specific file, shared file client A computer system that uses resources provided by another computer, called a server. See also server client area In DMS, an area containing a single client’s custom-tailored root files including the operating system kernel.
DHCP Dynamic Host Configuration Protocol. Enables the automatic assignment of an IP address to clients on networks from a pool of addresses. The IP address assignment and configuration occurs automatically whenever appropriate client systems (workstations and portable computers) attach to a network. The current implementation of DHCP is based on the JOIN product by Competitive Automation. DMS Dataless Management Services.
between DMS servers and clients. The dmu utility allows users to install, configure, show, and delete DMS environments and add, list, modify, and remove DMS clients. Dynamic Host Configuration Protocol See DHCP G generic root In DMS, a portion of the DMS environment that contains system software in a generic form, ready to be copied for tailoring to fit an individual client’s requirements. H hardware product A hardware product includes kernel modules to support hardware devices.
M member-specific file A file used by a specific cluster member. The contents of a member-specific file differ for each cluster member, and each member has its own copy of a member-specific file. See also cluster, cluster member, shared file N Network File System See NFS new hardware delivery See NHD NFS Network File System, an open operating system that allows all network users to access shared files stored on computers of different types.
P private area In DMS, a portion of the DMS area that is reserved for the exclusive use of a single client. The private area contains the client’s custom-tailored copy of certain operating system software files, including the kernel. product environment In RIS, a portion of the RIS area containing a set of software kits that are intended for installation on a particular client type, such as RISC processors.
installed on registered clients. Kits are organized so that a software product can supply several different versions for multiple hardware platforms. RIS client A computer system that has permission to install software across the network by accessing kits stored in the server’s RIS area. RIS server A computer system that serves other computers by providing operating system software for them to install; the software is stored on disks belonging to the server and is accessed across the network by the clients.
T TFTP Trivial File Transfer Protocol. TFTP is used during the RIS startup procedure to transfer the network kernel and supporting files from the RIS server to the RIS client. See tftp(1) and tftpd(8) for more information. U user-supplied file User-supplied files are a way to extend and customize the installation process, and can contain scripts, executables, or programs. The Full Installation and Update Installation processes execute user-supplied files at predetermined points during the installation.
Index A C adding a DMS client, 12–2 a RIS client, 6–2 DMS clients to /etc/hosts file, 10–2 RIS clients to /etc/hosts file, 6–2 software to existing DMS environment, 11–6 address gateway, 6–1 hardware, 6–1 allocating disk partitions for DMS, 10–3 architecture of RIS, 2–1 B Berkeley Internet Name Domain ( See BIND ) BIND, 6–2, 10–8 BIND Configuration Application, 10–8 booting a DMS client, 12–6 a RIS client, 5–1 problems with DMS clients, 13–1 BOOTP, 5–1 daemon, 5–2 BOOTP protocol requirement for, 3–3 bo
naming service registration for DMS, 10–8 registering for DMS, 10–7 registration for RIS, 6–1 registration information, 12–2 registration information for DMS, 10–8 removing from DMS, 12–11 removing from RIS, 6–9 software version compatibility for DMS, 10–1, 11–1 software version compatibility for RIS, 3–2 view of DMS areas, 9–5 client area calculating disk space for DMS, 10–6 in DMS, 9–5 client areas establishing multiple for DMS, 9–5 cloned client registration problems, 8–4 cluster rolling upgrade, 2–5 c
definition of, 9–1 deleting an environment, 12–7 disk space for environments, 10–4 environment, 9–3 files in /usr area, 9–4 installing operating system on server, 10–7 installing required software subsets, 10–7 installing software in new environment, 11–2 listing clients, 6–10, 12–12 lock files, 13–1 maintaining the environment, 12–14 multiple environments, 9–4 planning disk space, 10–4 problems booting a client, 13–1 removing a client, 6–9, 12–11 required software for environments, 10–4 root area, 9–2, 9
specifying for DMS client, 12–5 exported file systems for DMS, RIS support of, 4–7 hardware update release release installation, D–1 troubleshooting, 13–4 host name limitations on, 10–8 restrictions, 6–3 hosts file adding DMS clients to, 10–8 adding RIS clients to, 6–2 13–2 exports file, 13–2 F FDDI, 3–4 ( See also LAN ) setting up a client on, 3–4 FDDI address specifying for DMS client, 12–5 file .new..
Internet address ( See IP address ) Internet Boot Protocol ( See BOOTP ) internet daemon, 5–2 IP address registering, 6–2 registering for DMS client, 10–8 J joind, 5–2 joind daemon, 5–1, 8–6 K kernel customized for DMS clients, 9–5 full build support for DMS client, 10–6 generic, 9–3 no build support for DMS client, 10–6 partial build support for DMS client, 10–6 types of build support for DMS clients, 10–6 kit ( See subset ) L LAN, 1–1 host addresses on, 10–8 installation of RIS server, 3–4 install
Network File System ( See NFS ) network hardware address modifying for DMS client, 12–9 specifying for DMS client, 12–5 network information for DMS servers and clients, 10–2 Network Information Service ( See NIS ) network interface for DMS clients, 10–8 network naming service registering DMS client, 10–7 .new..
Remote Installation Services ( See RIS ) definition, 2–1 remove DMS client root directory, 11–6 removing a DMS client, 12–11 a DMS software environment, 12–7 a RIS client, 6–9 software subsets, 12–15 required software subsets for DMS server, 10–1 requirements for DMS clients, 10–2 for DMS servers, 10–1 response failures servers using bootpd daemon, 8–6 servers using joind daemon, 8–8 restrictions running bootpd and joind, 8–6n RIS, 1–1 architecture of, 2–1 checking client system registration, 7–6 converti
losing DMS customization during remove, 11–6 route for network for DMS clients, 10–8 running bootpd and joind restrictions, 8–6n S security in DMS, 10–9 security in RIS, 3–5 server architecture of DMS, 9–2 compatibility with the client, 11–1 defined, 1–1 description of, 1–2 DMS management tasks, 12–1 function in DMS, 9–2 function in RIS, 2–1 hardware compatibility for DMS, product list, 12–13 RIS product list, 6–11 software sharing via servers, 1–2 software subsets choosing for DMS, 11–4, 11–7 choosing fo
tftpd, 5–4 tftpd daemon, 5–1, 8–9 Token Ring setting up a client on, 3–4 Trivial File Transfer Protocol ( See TFTP ) troubleshooting client not in RIS database, 8–5 duplicate client hardware address, 8–3 getname failure on RIS client, 8–2 hardware update release, 13–4 inability to mount root file system, copying to RIS server, 7–2 installation cloning, 7–1 /usr area files in, 9–4 utilities utilupdate, C–1 utilupdate utility, C–1 V /var/adm/ris/clients/risdb file, 8–6 /var/adm/ris/gateways file, 6–13 ver