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:

12.1    DMS Client Database File

The DMS client database is located in the /var/adm/dms/clients/dmsdb file. Entries in this file are similar to the following: 

client1:xx-xx-xx-xx-xx-xx:/var/adm/dms/dms0.alpha:/clients/client1:
rz0b:RZ26:None:ln0:255.255.255.0

In this example:

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.

Before you can add a client, you already must have followed the procedures in Chapter 11 to install software in at least one DMS environment. Optionally, you may want to customize the .proto.. files as described in Section 11.4.1.

The DMS client must be connected to a local area network (LAN) and must be registered with the DMS server through one of the network naming services (see Section 10.8) or must have an entry in the server's /etc/hosts file.

When you add a client to a DMS environment, the root directory from the server's DMS environment gets copied to the client area.

Follow these steps to add a client to a 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. You see the DMU Main Menu: 

    *** DMU Main Menu ***
 
    a) ADD a client
    c) CONFIGURE software environments
    d) DELETE software environments
    i) INSTALL software environments
    l) LIST registered clients
    m) MODIFY a client
    r) REMOVE a client
    s) SHOW software environments
    x) EXIT
 
Enter your choice:

  3. Enter a to select ADD a client. You see a prompt similar to the following: 

    You have chosen to add a client for dataless service.
 
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. You must know the client's interface type, subnet
      mask.
   4. You must know the type of kernel build area.
   5. You must know the swap device and partition on the
      client.
   6. You must know the client's hardware Ethernet or FDDI
      address.
   7. If the client and the server reside on different subnets,
      you will need the address of the gateway(s) that the
      client can sue to communicate with the server.
 
Do you want to continue? (y/n) [y]:

  4. Enter y to continue. You see the following prompt: 

    Enter the client processor's hostname or press RETURN to quit: 
 

  5. Enter the host name for the DMS client.

    If you enter a host name that is not in the server's host database, you see a message similar to the following: 

    arp failed on hostname "client1"
 

    In the above message, arp is the Address Resolution Protocol. If you receive this message, check the /etc/hosts file to determine the correct host name. If the client was never registered with a network naming service (such as BIND or NIS) or was never entered in the /etc/hosts file, press [Ctrl/C] to exit the dmu utility and manually add the client to the /etc/hosts file before you restart the procedure.

    Note

    For the remaining examples, assume that the [Return] key is pressed to accept the default response.

    You see a prompt similar to the following: 

    Enter the path to contain the root file system. [/clients/client1]:
 

  6. Enter a path, or press [Return] for the default, /clients/hostname. If you specify a path other than the default , the directories in that path must already exist. The path must begin with /clients, and can be no longer than 25 characters.

    For example, if you want to differentiate between client systems in different departments at your site, you could specify /clients/deptname/hostname as the root location. The deptname directory must exist already under the /clients directory.

    You see a prompt similar to the following: 

    Enter the swap device and partition on client1. [dsk0b]: 
 

  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. Enter the DMS client's network subnet mask.

    You may see the following prompts:

    Refer to the Network Administration guide for information about obtaining the client's network information.

    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.0
       ROUTE:  network: nn.nn.nnn gateway: nn.nn.nnn.nnn
Is this correct (y/n) [y]:

  12. Enter y to confirm your selections or n to return to the DMU Main Menu.

    If you enter y, you see a prompt similar to the following: 

    The existing environment is /var/adm/dms/dms0.alpha.
 
The following environment will be installed from
/var/adm/dms/dms0.alpha:
 
Description
   1    'Tru64 UNIX VAAA Operating System (Rev nnn)'
 
Is that correct? (y/n) [y]:

    If there is more than one DMS environment, you are prompted to select one and confirm your selection.

  13. Enter y to confirm your selection or n to return to the DMU Main Menu. You see a prompt similar to the following: 

    Enter the client processor's hardware network 
address. For example, 08-00-2b-02-67-e1:

  14. Enter the DMS client's hardware network address.

    Note

    The dms utility does not check the validity of the address you enter, but it does check to make sure the address you enter is in the correct format.

    You see a prompt similar to the following: 

    Checking file system space required for client
root and var file systems.

    You see the DMU Main Menu.

Notify the client's system administrator when client registration is complete and inform them that they now can boot the client across the network. See Section 12.3 for basic information about booting a client. Refer to the Installation Guide -- Advanced Topics for additional information.

12.3    Booting a DMS Client

After a DMS client is added to the appropriate environment, the client's system administrator can boot the client over the network. When the client starts to boot, the kernel that boots over the network is: /clients/hostname /.vmunix

The following steps occur when the client boots:

  1. The /clients/hostname directory is mounted by NFS as root ( / ).

  2. The /var/adm/dms/dmsN.alpha/root/usr directory is mounted by NFS as /usr.

The network information you entered about the client when you added it to the DMS environment is sufficient to boot the DMS client across the LAN.

DMS clients must be able to boot over Ethernet or FDDI LAN. The basic procedure for booting a processor over the network from a server is to shut down the client system to console mode and then issue a boot command from the client.

Refer to the Installation Guide -- Advanced Topics for information about booting systems over the network.

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.4    Deleting a Software Environment

When you delete a software environment, the environment itself and all clients registered to that environment are deleted. Once you confirm your choice, there is no opportunity to undo the deletion.

Caution

Make sure that the clients registered to the environment have been notified and shut down before you delete the environment. Failure to do so will cause a running client to lose its operating system.

To delete a software environment, follow these steps:

  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 DMS utility. You see the DMU Main Menu: 

    *** DMU Main Menu ***
 
    a) ADD a client
    c) CONFIGURE software environments
    d) DELETE software environments
    i) INSTALL software environments
    l) LIST registered clients
    m) MODIFY a client
    r) REMOVE a client
    s) SHOW software environments
    x) EXIT
 
Enter your choice:

  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. Enter the number that corresponds to the DMS environment you want to delete, for example: 1. You see a prompt similar to the following:

    After you select the dataless environment to delete, a confirmation displays your choice: 

    The following environment will be deleted from
/var/adm/dms/dms0.alpha:
 
Description
       'Tru64 UNIX VAAA Operating System (Rev nnn)'
 
Is that correct? (y/n) [y]:

  5. Confirm your selection.

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. Refer to Section 1.3 for instructions about how to obtain the hardware address of a client.

Perform the following steps to modify a DMS client's information:

  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. You see the DMU Main Menu: 

    *** DMU Main Menu ***
 
    a) ADD a client
    c) CONFIGURE software environments
    d) DELETE software environments
    i) INSTALL software environments
    l) LIST registered clients
    m) MODIFY a client
    r) REMOVE a client
    s) SHOW software environments
    x) EXIT
 
Enter your choice:

  3. Enter m to select MODIFY a client. You see a prompt similar to the following: 

    The following clients are available to modify:
 
client4 client5 client6
 
Enter the client processor's hostname or press RETURN to quit:

  4. Enter the name of the client you want to modify, for example: client4.

    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. You see a message similar to the following: 

    Client client4 has been modified.
 
*** DMU Main Menu ***
 
    a) ADD a client
    c) CONFIGURE software environments
    d) DELETE software environments
    i) INSTALL software environments
    l) LIST registered clients
    m) MODIFY a client
    r) REMOVE a client
    s) SHOW software environments
    x) EXIT
 
Enter your choice:

If you want to change the client's IP address or the environment to which the client is registered, follow these steps:

  1. Log in to the DMS client as root or use the su command to gain superuser privileges.

  2. Use the SysMan Menu or the shutdown -h command to shut down the DMS client.

  3. Log in to the DMS server as root or use the su command to gain superuser privileges.

  4. Enter /usr/sbin/dmu to start the dmu utility. You see the DMU Main Menu: 

    *** DMU Main Menu ***
 
    a) ADD a client
    c) CONFIGURE software environments
    d) DELETE software environments
    i) INSTALL software environments
    l) LIST registered clients
    m) 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 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. Log in to the DMS client as root or use the su command to gain superuser privileges.

  2. Use the shutdown -h command to shut down the DMS client.

  3. Log in to the DMS server as root or use the su command to gain superuser privileges.

  4. Enter /usr/sbin/dmu to start the dmu utility. You see the DMU Main Menu 

    *** DMU Main Menu ***
 
    a) ADD a client
    c) CONFIGURE software environments
    d) DELETE software environments
    i) INSTALL software environments
    l) LIST registered clients
    m) MODIFY a client
    r) REMOVE a client
    s) SHOW software environments
    x) EXIT
 
Enter your choice:

  5. Enter r to select REMOVE a client. You see the following prompt: 

    You have chosen to remove a client from the remote
dataless service.
 
Enter the client processor's hostname or press RETURN to quit:

  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 following additional items:

If you remove a client but save the root ( / ) file system, you cannot reuse that root file system if you subsequently add a client with the same client name.

12.7    Listing DMS Clients

Follow these steps to view registered DMS clients:

  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. You see the DMU Main Menu: 

    *** DMU Main Menu ***
 
    a) ADD a client
    c) CONFIGURE software environments
    d) DELETE software environments
    i) INSTALL software environments
    l) LIST registered clients
    m) MODIFY a client
    r) REMOVE a client
    s) SHOW software environments
    x) EXIT
 
Enter your choice:

  3. Enter l to select LIST registered clients.

    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.

  2. Enter /usr/sbin/dmu to start the dmu utility. You see the DMU Main Menu: 

    *** DMU Main Menu ***
 
    a) ADD a client
    c) CONFIGURE software environments
    d) DELETE software environments
    i) INSTALL software environments
    l) LIST registered clients
    m) MODIFY a client
    r) REMOVE a client
    s) SHOW software environments
    x) EXIT
 
Enter your choice:

  3. Enter s to select SHOW software environments. You see output similar to the following: 

    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)''
 
*** DMU Main Menu ***
 
    a) ADD a client
    c) CONFIGURE software environments
    d) DELETE software environments
    i) INSTALL software environments
    l) LIST registered clients
    m) MODIFY a client
    r) REMOVE a client
    s) SHOW software environments
    x) EXIT
 
Enter your choice:

12.9    Maintaining the DMS Environment

This section contains information about maintaining the DMU server area, and includes the following topics:

12.9.1    Controlling Root File System Growth

The df command displays statistics about the amount of free space on a specified file system or on a file system that contains a specified file.

The du command displays a summary of disk usage for file systems. Use this command to monitor the file growth in each client's root directory. If clients use too much space, performance is adversely affected. Users must then be told to delete all unnecessary files from their file systems. Monitor disk usage periodically depending upon the systems' use.

Refer to the df(1) and du(1) reference pages for more information about monitoring file system growth.

12.9.2    Listing Installed Software Subsets

Use the setld utility to determine which software subsets are installed into a particular dmsN .alpha area. For example, the following command produces a list of the subsets installed into the client root area of /var/adm/dms/dms0.alpha: 

# setld -D /var/adm/dms/dms0.alpha/root -i

Refer to the setld(8) reference page for more information.

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.

Caution

If the setld utility placed files in the root file system during the installation, the product may not be fully removed from the client's root file system. Be careful about removing any subset that may be used by client systems. For example:

You should understand client dependencies before you remove a software component. You may need to delete and reregister all clients before you can reload a subset.