5

Supporting a Centralized System - HP

This chapter contains procedures for setting up the necessary operating system support files. Use the Workbook (Chapter 2) to determine the procedures needed.

Your environment and the features you enable dictate the operating system tasks. You must be root to modify the host files.

• NFS directories must be exported if NFS is used for booting or file access.
• tftp must be configured and enabled if tftp is used for booting or file access.
• bootp must be configured and running for the network computer to automatically find boot information for a tftp or NFS boot.
• HP-VUE must be running to use vuelogin or DTLogin to manage your network computer's display. For further information on vuelogin or DTLogin, see the HP Visual User Environment System Administration manual. If you do not use vuelogin or DTLogin, you can use xdm to manage the display and login procedures.

Note:

To enable vuelogin to read the user's $HOME/.xsession file, modify the /usr/vue/config/Xconfig file as follows: Vuelogin*xdmMode: True

• Local Motif Window Manager (MWM). (See Chapter 10, Window Managers.)

Enabling NFS Access

NFS is included as part of the optional NFS services software package for the Hewlett-Packard operating system. If the boot host does not provide NFS, use tftp to download network computer files. This section describes the steps necessary to set up the host if NFS is used as the boot_method or file_access_method.

1. Edit the /etc/exports file. Add each of the file systems to be exported now and at boot, along with any options.

   The file systems must be exported to be accessible to the network computer. The exported systems are specified with an nfs_table command in the xp.cnf file, or in the nfs.tbl file. An example xp.cnf file entry:

   nfs_table "montana:/tekxp" "/tekxp"  "8192"

   An example nfs.tbl entry:

   montana:/tekxp /tekxp 8192

   /etc/exports entry:

   /tekxp

2. Invoke SAM to edit the /etc/hosts file. Choose the menu items:

   Network Communication->
   ARPA Services Configuration->
   Add Connectivity to a Remote System

   Specify the host name, Internet address, and optional hostname aliases and comments in response to the SAM prompts. For example:

   128.07.60.30 portland

3. Use the ps command to see if nfsd is running:

   # ps -ef | grep nfsd | sed /grep/d
   root 75 74 0 Aug 14 ? 0:05 /etc/nfsd 4
   root 76 74 0 Aug 14 ? 0:04 /etc/nfsd 4
   root 77 74 0 Aug 14 ? 0:04 /etc/nfsd 4

4. If nfsd is running, use the kill command with the PIDs to kill the daemons:

   # kill -15 PID

   The output from step 3 shows the PID of the nfsd process in the second column and the parent process in the third column. Several daemons can be started by the same parent process; check the third column for a repeated number. If you kill this PID, you may not need to kill the others.

5. Restart the NFS daemon to enable NFS access with the command:

   # /etc/nfsd 4 &

Enabling TFTP

This section describes the steps necessary to set up tftp if it is used as the boot_method or file_access_method.This is the default boot method for network computers not equipped with TDEnet, Flash Memory or ROM options. For details, see the tftp man page on your host, or in /tekxp/man.

There are considerations to make if the boot or font host uses secure tftp.

To determine if you use secure tftp, check the file /etc/inetd.conf for a line similar to:

tftp dgram udp wait root /usr/etc/in.tftpd in.tftpd -s /tftpboot

1. The tftpd daemon should be started each time the host boots. The /etc/inetd.conf file is read at startup, and should contain the tftp command line. If the line does not exist in your inetd.conf file, you need to add it. To verify that the tftp startup command is in the file:

   # grep tftp /etc/inetd.conf
   tftp dgram udp wait root /etc/tftpd tftpd

2. The boot_directory and install_directory used during the tape installation must have a common parent directory. In addition, if the /etc/inetd.conf file contains a tftp entry with the -s (secure tftp) option:

   tftp dgram udp wait root /etc/tftpd tftpd -s /tekxp

   both the boot_directory and install_directory used during the tape installation would have to be within the secure path, in this case, /tekxp.

3. Check the /etc/services file for a tftp entry. If a tftp entry does not exist, edit the file and add the line (maintain numeric order with other entries):

   tftp 69/udp

4. Check the /etc/passwd file for a tftp entry. This entry provides secure tftp access and allows tftp operations. If it does not exist, add the line:

   tftp:*user_ID:group_ID:tftp server:/tekxp:/bin/false

   Use appropriate values for user_ID and group_ID.

5. If /etc/tftpd does not exist, copy /tekxp/bin/<host>/tftpd to /etc.
6. After you edit inetd.conf to add the tftp entry, kill and restart the inetd daemon for your changes to take effect:

   # /etc/inetd -k

   # /etc/inetd

   The host starts tftpd whenever it receives an external request for tftp service.

Note:

The tftp binary from the installation media requires a /usr/tmp directory to perform the file transfers. If this directory does not exist, it must be created.

Enabling bootp

This section describes the steps necessary to set up the host so that the network computer automatically boots using the Internet Boot Protocol to transfer boot information upon power-up. The bootp daemon is included as part of Hewlett-Packard's optional ARPA software package for HP-UX release 8.0 operating system. If the bootp daemon is not available, contact Hewlett-Packard or use the boot monitor and Setup to configure each network computer. For additional information on the configuration of bootpd, see Volume 3 of the HP-UX Reference manual.

To enable bootp, perform the following steps:

1. Edit the /etc/bootptab file:

A typical section of the /etc/bootptab file looks like the following:

# Global entry that every host uses:

global.d:\
sm=255.255.255.0:\
hd=/tekxp:\
ds=134.62.5.17 134.62.61.219:\
:to=18000:

# Subnet entry:

subnet64:\
tc=global.d: gw=134.62.64.120:

# Individual entry:

portland:\
c=subnet64: ht=ethernet: ha=080011010031:\
ip=134.62.64.53: bf=/boot/os.900:\
# T134="config/admin.cnf":

Note:

The T134 line allows you to use a different configuration file path. The network computer will then look for a different configuration file, admin.cnf, instead of the usual configuration file, xp.cnf.

A sample bootptab file is located in /tekxp/examples. Table 5-1 briefly describes the bootp fields.

Table 5-1 bootp Fields

Field	Description
hostname	The Internet name of the host (required)
hd	The full path of the home directory (typically /tftpboot)
bf	The path and name of the bootfile within the home directory (ie /XP10/os)
cs	The Internet address of the cookie server(s)
ds	The Internet address of the domain name server(s)
gw	The Internet address of the gateway server(s)
ha	The network computer's hardware address
ht	The network computer's hardware type (typically ethernet)
im	The Internet address of the impress server(s)
ip	The Internet address of the host
lg	The Internet address of the log server(s)
lp	The Internet address of the LPR server(s)
ns	The Internet address of the IEN-116 name server(s)
rl	The resource location protocol servers
sm	The subnet mask
tc	The template entry which bootp uses
to	The time offset in seconds
ts	The Internet address of the time server(s)
T134	The location and name of the remote configuration file

Note:

T134 is a user-defined variable to the bootptab file. It is intended for use with the bootp and bootptab file included on the media.

Ensuring that bootp is Running

The final step is to ensure that bootp is running. To see if bootp is running:

# ps -e | grep bootpd | sed /grep/d

61 ? 0:01 bootpd

If bootp is not running:

1. Verify that bootpd and its associated data file bootptab are in /etc:

   # ls /etc

2. If necessary, add the bootps command to the inetd.conf file. To verify the bootps command in the inetd.conf file:

   # grep bootp /etc/inetd.conf
   bootps dgram udp wait root /etc/bootpd bootpd

3. Verify that bootpd resides where it is specified in /etc/inetd.conf. For the preceding examples, bootpd is in /etc. If there is a mismatch between the actual location and the specified location, either move the bootpd binary or change the /etc/inetd.conf file.
4. The port numbers for bootp listening and replying must be set in the /etc/services file. If they are not set, edit the file and add them. To verify that the ports are set in the file:

   # grep bootp /etc/services
   bootps 67/udp
   bootpc 68/udp

5. If you have edited inetd.conf, restart the inetd daemon:

   # inetd -k
   # /etc/inetd

To run bootpd as a stand-alone daemon, start bootp directly from /etc using the -s option as follows:

# /etc/bootpd -s

This method of invocation often works better in environments with large numbers of network computers making bootp requests.