Page 3 - Contents; About This Manual
Contents About This Manual 1 Introduction to Sharing Software 1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1 1.2 Understanding the Software Sharing Environment . . . . . . . . . . . . 1–2 1.3 Identifying ...
Page 9 - Audience
About This Manual This manual describes the Remote Installation Services (RIS) and DatalessManagement Services (DMS) environments and utilities maintained on aCompaq Tru64™ UNIX operating system. • RIS lets you install software kits across a network from a centrallyadministered server instead of usi...
Page 10 - Organization; This manual is organized as follows:
The Tru64 UNIX documentation is available on the World Wide Web at thefollowing URL: http://www.tru64unix.compaq.com/docs/ Organization This manual is organized as follows: Chapter 1 Introduces the concept of servers and clients, explainingwhat they are and how they work together. It also describest...
Page 11 - Related Documentation; You should have the following documentation available:; Icons on Tru64 UNIX Printed Manuals; The
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 aDMS area serving an older version of the operating system. Related Docum...
Page 12 - Reader’s Comments; You can send your comments in the following ways:
Reader’s Comments Compaq welcomes any comments and suggestions you have on this andother 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: [email protected] A Reader ’s Comment form is l...
Page 13 - Conventions; The following conventions are used in this manual:; cat; file
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 theBourne, Korn, and POSIX shells. # A number sign represents the superuser prompt. % cat Boldface type in interactive examples indica...
Page 15 - Note; DMS is not supported in a clusters environment.
1 Introduction to Sharing Software This chapter introduces software sharing and the components that make upa software sharing environment. This chapter includes the following topics: • Software sharing concepts, components, and benefits (Section 1.1) • Describing the software sharing environment (Se...
Page 16 - Understanding the Software Sharing Environment; A server
The RIS and DMS utilities share architectural similarities; the primarydifferences 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 softwarebetween computer...
Page 17 - Identifying a CD-ROM Drive Device Name
Ethernet or FDDI using the BOOTP and TFTP protocols to install the base operating system from a server. Layered products can be installedafter the client’s operating system is running with the SysMan Menu. DMS clients must be capable of booting over Ethernet or FDDIusing the BOOTP and TFTP protocols...
Page 18 - ls; mount
• If you are using a later version of the operating system that uses newerdevice naming conventions ( /dev/disk/cdrom N c ), use the ls command as shown in the following example: # ls -l /dev/disk/cdrom* brw------- 1 root system 19, 69 Nov 18 06:11 /dev/disk/cdrom0a brw------- 1 root system 19, 71 N...
Page 20 - Figure 2–1: RIS Server and Client; setld
Figure 2–1: RIS Server and Client Kits Server Client ZK-0268U-AI Local Disk Local Disk Local Area Network RIS Area The server maintains information in the RIS areas about what softwarekits clients can access. Kits are organized so that RIS can serve differentversions of a software product to multipl...
Page 21 - root; RIS Areas and Product Environments
• RIS uses a single set of kit files for all clients having the samearchitecture. • You can perform a cloned installation on a RIS client, letting youduplicate a similar system installation or configuration. See the Installation Guide — Advanced Topics for information about installation cloning and ...
Page 22 - Figure 2–2: Sample RIS Area Overview; Network Administration: Services; RIS Client Characteristics
Figure 2–2: Sample RIS Area Overview ris0.alpha product_001 product_002 ZK-0620U-AI /var/adm/ris subsets subsets kit/isl Client Installation Tools In Figure 2–2, the RIS area /var/adm/ris contains one product environment, ris0.alpha . Each product environment contains products for a specific platfor...
Page 23 - Registering Clients; Cluster Installation; Identifying a Client Hardware Network Address
it is registered on the server. The installation procedure runs entirelyon the client and, after the necessary software is installed, no continuingrelationship is required between the RIS server and client. The operating system itself can be among the kits that are available from theserver. To insta...
Page 24 - show dev
• 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 ....
Page 25 - Reviewing RIS Server/Client Version Compatibility
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...
Page 27 - Planning Disk Space for RIS; Release Notes; Installing the Operating System on the RIS Server; Installation Guide
3.2 Planning Disk Space for RIS Before beginning to set up a RIS area, you must calculate the amount of diskstorage required for the software subsets in the RIS areas on the server. Ifspace on the server ’s system disk is an issue and your server ’s distributionmedia is a CD − ROM, you might want to...
Page 28 - Setting Up a Local Area Network; Network; Loading and Registering the Server Extensions License; Software License Management
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 insta...
Page 29 - Preparing RIS for C2 Security
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...
Page 31 - Installing Software into a New RIS Area; Operating System Volume 1
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 prod...
Page 33 - Install software products; Install software into a new area
The RIS Utility Main Menu does not display option letters for menuitems that cannot be accessed. As you add environments, software, andclients to the system, other menu options become available. 4. Enter i to select Install software products . You see the following prompt: RIS Software Installation ...
Page 34 - Caution
Choose one of the following options: 1) Extract software from /mnt/ALPHA/BASE 2) 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 thespecified source. Disk space pla...
Page 35 - Installing Software into an Existing RIS Area; Guide to Preparing Product Kits
The following choices override your previous selections: 74) ALL mandatory and all optional subsets75) MANDATORY subsets only 76) CANCEL selections and redisplay menus Choices (for example, 1 2 4-6): 74 The following subsets will be loaded: . . . {selected subset list - all mandatory & optional ...
Page 36 - Return
Choices without key letters are not available. a) ADD a client d) DELETE software products i) INSTALL software products ) LIST registered clients ) MODIFY a client) REMOVE a client s) SHOW software products in remote installation environments x) EXIT Enter your choice: 3. Enter i to select INSTALL s...
Page 37 - Including Hardware Product Kits into a RIS Area; Guide to
4.4 Including Hardware Product Kits into a RIS Area In addition to the base operating system, you may need to install hardwareproduct kits onto client systems from the RIS server. For example, ahardware product kit can be a third-party driver for a device not supportedin the base operating system. T...
Page 38 - Add software into an existing area
RIS Software Installation Menu: 1) Install software into a new area 2) Add software into an existing area 3) 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...
Page 39 - You see the following prompt:; Select; to confirm your selection. You see a prompt similar to the
You see the following prompt: Choose one of the following options: 1) Extract software from /HWKIT/MYVGA/kit 2) 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 opti...
Page 40 - Using a RIS Area Mounted on NFS; arch
4.5 Using a RIS Area Mounted on NFS You can use an NFS mount point to install software from an extracted RISarea on another system or from an operating system distribution CD − ROM mounted on another system. You can use this method to create an extractedRIS area with the base operating system subset...
Page 43 - Booting a RIS Client; Remote Boot Files and Daemons; Table 5–1: Remote Boot Files and Daemons; Name
5 Booting a RIS Client You must register a RIS client on the RIS server before you can use RIS toinstall the operating system on the RIS client. If you use RIS to install theoperating system on a client, the client must boot across the network byissuing a BOOTP request. This chapter includes the fol...
Page 44 - The Internet Daemon and Configuration File
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 BOOTPand DHCP requests, if configured) /usr/sbin/tftpd The tftpd server daemon 5.1.1 The Internet Daemon and Configuration File The inetd...
Page 45 - hostname
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:/ri...
Page 46 - tg; Remote Boot Process Flow; Installation Guide — Advanced
• ha : Client’s network hardware address • ip : Client’s IP address 4 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...
Page 49 - Preregistration Tasks; Obtaining Information About Each Client
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)...
Page 50 - Registering Client Host Names and IP Addresses; Network Administration: Connections; Adding a RIS Client with the ris Utility
• The client’s hardware network address • The address of the gateway from the client to the server, if the serverand 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 (...
Page 51 - ADD a client; client1
) MODIFY a client ) REMOVE a client s) SHOW software products in remote installation environments x) 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...
Page 52 - . You see a prompt similar to the following:; . You see a prompt similar to; Enter; all
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 cli...
Page 55 - Adding a RIS Client from the Command Line; clientname; Modifying RIS Clients
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-...
Page 57 - Removing RIS Clients
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 hardwarenetwork address. You see a message similar to the following: Client client01 has been mo...
Page 58 - Listing Registered RIS Clients
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 s...
Page 59 - Listing Products in RIS Server Areas
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:...
Page 60 - Deleting Products from RIS Server Areas
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 choosea RIS area and then guides you through the procedure to delete products. 1. Log in as root or use th...
Page 61 - Correcting RIS Gateways File Entries
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]: ...
Page 64 - Installation Guide — Advanced Topics; Creating Profile Sets
• User-supplied files are a way to extend and customize the installationprocess, and can contain scripts, executables, or programs. The FullInstallation and Update Installation processes execute user-suppliedfiles at predetermined points during the installation. User-installed files may include some...
Page 65 - Registering Clients for Profile Sets; Example 7–1: Sample RIS Client Profile Set Registration
3. Create the profile set directory. For example: # mkdir engineering 4. Go to the newly created directory to ensure that the necessary files arecopied to the correct destination. For example: # cd engineering 5. Copy the CDFs, any user-supplied files, and all other related files fromyour working ar...
Page 67 - Converting Old Configuration Description Files; If you had existing CDFs in the
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. For example, 08-00-2b-02-67-e1: xx-xx-xx-xx-xx-xx Client pubs08 has been added. *** RIS Utility Main Menu *** a)...
Page 68 - Determining RIS Client Profile Set Registration; Deleting Profile Sets from the RIS Server
Converting old cdf directory to new sets directory format... CDF File acctng moved to set acctng and renamed install.cdfCDF 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 r...
Page 70 - Client Password Expiration; Root File System Mounting; mountd; RIS Client Registration
8.2 Client Password Expiration If the RIS server is using C2 security and the RIS password has been setto allow expiration, it is possible for the RIS clients to be denied service. Ifthe RIS client receives a message similar to the following, the RIS passwordon the server probably has expired: Canno...
Page 71 - No Prompt for Client Hardware Address; Duplicate Client Hardware Addresses
8.4.1 No Prompt for Client Hardware Address The server requires a client’s hardware address in order to boot the clientover 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 − RO...
Page 72 - albany; Client Registered on Multiple RIS Servers; BOOTP
• If the hardware address you entered is correct, deregister and reregisterthe existing client (in this example, albany ). • If the existing client is not registered, contact your RIS systemadministrator. 8.4.3 Cloned Client Registration A CDF is created during a Full Installation. To use the CDF fo...
Page 73 - risdb
8.4.5 Client Not in RIS Database If a message appears on the client’s console while you are performing a RISinstallation that states that the client is not in the RIS database, look atthe following on the server: • As shown in Section 8.5, look at the /var/adm/ris/clients/risdb file to see if the cl...
Page 74 - RIS Server Response
8.5 RIS Server Response Problems with RIS server response comprise several categories. Thefollowing 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 failure...
Page 77 - rcmgr get JOIND.FLAGS; joind; tftpd
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 debuggingturned on. Use the JOIND_FLAGS argument to in...
Page 79 - dmu
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 stillmaintaining their own root ( / ) and /var file systems that reside on the DMS server. With DMS, you can save disk space by sha...
Page 80 - Relationship Between DMS Servers and Clients
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...
Page 81 - Figure 9–1: File Sharing Between the DMS Server and Client
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 thatdisk area through a LANconnection with the server. Each DMS client isbooted across the network from its private root area on the server. After itis booted, t...
Page 82 - Figure 9–2: Environment Portion of DMS Area; vmunix
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 root shared /usr ZK-0935U-AI shared /usr The root file system contains copies of t...
Page 83 - Figure 9–3: DMS Client Area; ClientB
9.3.3 Client Portion of DMS Area A DMS client area for individual DMS client systems also resides in aDMS area. Figure 9–3 shows a DMS client area named /clients . Place this DMS client area in its own partition after you calculate the requiredsize with the worksheets in Appendix B. Next, add the mo...
Page 84 - Figure 9–4: Client Views of the DMS Area; Client B; ClientA
Figure 9–4: Client Views of the DMS Area Client B Server Client A ClientA root /usr root /usr ClientB shared /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 theclient to produce this view. ...
Page 85 - Requirements for DMS Servers; Additional Networking Services (
10 Preparing DMS Servers and Clients This chapter describes how to get DMS servers and clients ready to run in adataless environment. Perform the following steps to prepare DMS serversand clients: 1. Meet requirements for DMS servers. (Section 10.1) 2. Meet requirements for DMS clients. (Section 10....
Page 86 - Requirements for DMS Clients; BIND Configuration Application
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...
Page 88 - portmap; man portmap; Planning Disk Space for DMS; Disk Space Required for DMS Environments; dms
# ps ax | grep -E "portmap|mountd|nfsd|nfsiod" If these daemons are not all running, start the inoperative ones. See theappropriate reference pages for information about starting these daemons.For example, enter the following command to display the portmap (8) reference page: # man portmap 1...
Page 89 - Table 10–1: Estimated Subset Sizes for DMS; Subsets
Each dms N .alpha environment also can contain additional software for the clients registered to access that environment. Section 11.2 describes how toinstall software in DMS environments. Reserve the following space in addition to space needed for the mandatorysubsets and the subsets required by DM...
Page 90 - Considering Types of Kernel Builds; DATALESS
Reserve additional space for any other software products you plan to installlater. These products’ space requirements must be factored into the 10percent 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’ r...
Page 91 - Installing the Operating System on the DMS Server; Registering DMS Clients
kernel objects. If you choose a partial build, allow an additional 15 Mbfor each client’s root area. The space required by individual clients will not be the same, but you canadd all the needed spaces together to arrive at the total requirement for the /clients area. You also must remember to reserv...
Page 92 - Registering Clients Host Names and IP Addresses
10.8.1 Obtaining DMS Client Information You need to know the following information about each processor you planto add as a client to a /var/adm/dms/dms N .alpha environment and to register the client with the appropriate naming service: • The host name Only lowercase letters ( a-z ), numerals ( 0-9...
Page 93 - Considering Security Issues; bootp
file when you initially set up your LAN. The Network ConfigurationApplication 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 proces...
Page 95 - Ensuring DMS Server and Client Compatibility
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 topicsare discussed: • Ensuring version compatibility between DMS servers and clients(Section 11.1) • Installing software into a ...
Page 96 - Installing Software in a New DMS Environment
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 op...
Page 100 - Adding Software to an Existing DMS Environment
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 ...
Page 103 - Configuring DMS Environments
11.4 Configuring DMS Environments After you install software into a new or existing DMS environment, youmust configure the environment. Configuring the environment includes thefollowing steps: 1. Customizing the .proto.. system files (Section 11.4.1). This step is optional; you do not have to custom...
Page 106 - Installing WLS Support in DMS
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...
Page 107 - Building an Asian Kernel for DMS Clients
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 availableDMS environments and you are prompted to select the environmentfor adding software. 7. Select the D...
Page 109 - DMS Client Database File
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 inthis chapter includes the following topics: • Locating and interpreting the DMS client database file (Section 12.1) • Ad...
Page 110 - Adding a DMS Client
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 SetupWorksheet in Appendix B. Fill out a worksheet f...
Page 114 - Booting a DMS Client
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 v...
Page 115 - Deleting a Software Environment
When the client system boots, the client system administrator is promptedto 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 theCommon Desktop...
Page 117 - Modifying Client Information; client4
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 ret...
Page 119 - Removing a Client
i) INSTALL software environments l) LIST registered clientsm) MODIFY a client r) REMOVE a client s) SHOW software environments x) 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 cl...
Page 120 - client5; Listing DMS Clients; LIST registered clients
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. The dmu utility removes the client’s registration to the DMS environment, along with the followingadditional items: • The client’s root d...
Page 121 - Showing Software Environments
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 cl...
Page 122 - Maintaining the DMS Environment; Controlling Root File System Growth
i) INSTALL software environments l) LIST registered clientsm) MODIFY a client r) REMOVE a client s) SHOW software environments x) EXIT Enter your choice: 12.9 Maintaining the DMS Environment The following sections contain information about maintaining the DMUserver area, and includes the following t...
Page 125 - Removing DMS Lock Files; If the
13 Troubleshooting DMS This chapter contains information to assist you in troubleshooting problemswith DMS. If a DMS client has trouble booting, you can check several aspectsof server operation to ensure that the server ’s end of the network connectionis functioning properly. These are grouped into ...
Page 126 - Checking NFS Server Status; rcmgr get NFSSERVING; Checking Network Daemon Status
13.2 Checking NFS Server Status Some DMS client boot problems occur if the DMS server is not a NetworkFile System (NFS) server. To check whether or not a DMS server is an NFSserver, enter the following command on the DMS server: # rcmgr get NFSSERVING If the response is a 1 , the system is an NFS se...
Page 127 - swapdev; swap; swap
13.5 Checking Version Compatibility If you cannot execute commands on the DMS client and the DMS server andclient are running different versions of the operating system, look to see ifyou copied the client’s dmu version to the server. See Section 11.1 for more information. 13.6 Correcting Swap Devic...
Page 128 - Reconfiguring for a Hardware Update Release
4. Shut down and reboot the DMS client. You may encounter a situation where the client cannot boot to multiuser mode because the client machine has insufficient memory and thedisk specified to serve as the swap volume does not have the correct filesystem type in the disklabel. If this occurs, it wil...
Page 137 - Disk Space for the /clients File System
Step 2 Step 1 ZK-1018U-AI Using the appropriate memory size information for your clients, follow thesesteps to find how much space you need for the area. To allow at least 30 megabytes(MB) for an individual client’s root area, multiply the number of clients in the area by 30. MB Step 3 Allocate an a...
Page 139 - DMS Information; The name of the dataless environment to which this client; The client’s network interface type.; Registration Information for DMS Client; The name of the area.; DMS Client Setup Worksheet
DMS Information The name of the dataless environment to which this client Network The client’s network interface type. ZK-1520U-AI This worksheet is used for recording the information you need to know whenadding a client to a DMS environment using the menuoption. If you are adding multiple clients, ...
Page 141 - utilupdate; directory
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 theoperating system to client systems. Syntax for th...
Page 143 - This appendix includes the following topics:
D Hardware Update Releases in DMS A hardware release is a version of the operating system that includes newor updated kernel modules to support hardware devices. In the currentversion of the operating system, the function of hardware releases has beensuperseded by the New Hardware Delivery (NHD) pro...
Page 144 - D.2 Installing a Hardware Release into a DMS Area
– Which directory in the RIS area conains the operatingsystem software. Examine the /usr/var/adm/ris/ris N .alpha/ProdNames file to determine this directory. • If you install from a base operating system CD-ROM mounted on themount point /mnt , the /mnt/ALPHA/UPDATE directory contains the operating s...
Page 145 - Glossary; BIND; hosts; boot command; boot; Glossary–1
Glossary This glossary defines terms and concepts related to software sharing. B BIND The Berkeley Internet Name Domain. A distributed database lookup servicethat allows you to distribute the hosts database network-wide. boot command The boot command performs the initial installation and bootstrap o...
Page 146 - Glossary–2
the cluster member accessing the file. CDSLs make it possible to maintainsystem-specific configuration and data files on file systems shared by thecluster. See also cluster , cluster member , member-specific file , shared file client A computer system that uses resources provided by another computer...
Page 147 - Glossary–3
DHCP Dynamic Host Configuration Protocol. Enables the automatic assignmentof an IP address to clients on networks from a pool of addresses. The IPaddress assignment and configuration occurs automatically wheneverappropriate client systems (workstations and portable computers) attach toa network. The...
Page 148 - Dynamic Host Configuration Protocol; See; generic root; kit; See also; layered product; Glossary–4
between DMS servers and clients. The dmu utility allows users to install, configure, show, and delete DMS environments and add, list, modify, andremove DMS clients. Dynamic Host Configuration Protocol See DHCP G generic root In DMS, a portion of the DMS environment that contains system software ina ...
Page 149 - Glossary–5
M member-specific file A file used by a specific cluster member. The contents of a member-specificfile differ for each cluster member, and each member has its own copy of amember-specific file. See also cluster , cluster member , shared file N Network File System See NFS new hardware delivery See NH...
Page 150 - Glossary–6
P private area In DMS, a portion of the DMS area that is reserved for the exclusive use of asingle client. The private area contains the client’s custom-tailored copy ofcertain operating system software files, including the kernel. product environment In RIS, a portion of the RIS area containing a s...
Page 151 - Glossary–7
installed on registered clients. Kits are organized so that a software productcan supply several different versions for multiple hardware platforms. RIS client A computer system that has permission to install software across thenetwork by accessing kits stored in the server ’s RIS area. RIS server A...
Page 152 - TFTP; tftp; Glossary–8
T TFTP Trivial File Transfer Protocol. TFTP is used during the RIS startupprocedure to transfer the network kernel and supporting files from the RISserver 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 th...
Page 153 - Index; Index–1
Index A 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 Na...
Page 154 - Index–2
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 compatibilit...
Page 155 - Index–3
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 f...
Page 156 - Index–4
specifying for DMS client , 12–5 exported file systems for DMS , 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.. , 9–4 root area , 9–3 /usr area , 9–4 file system DMS environments , 10–4 exported for DMS cli...
Page 157 - Index–5
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 buil...
Page 158 - Index–6
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 cli...
Page 159 - Index–7
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 se...
Page 160 - Index–8
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 t...
Page 161 - Index–9
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 ...
