3 Preparing the RIS Server

This chapter provides the steps you must follow to prepare a RIS server. These steps include the following:

Review RIS server/client version compatibility. (Section 3.1)

Plan disk space for RIS. (Section 3.2)

Install the operating system on the RIS server. (Section 3.3)

Set up a local area network. (Section 3.4)

Load and register the server extensions license. (Section 3.5)

If necessary, prepare RIS for running on a server that has C2 security enabled. (Section 3.6)

3.1 Reviewing RIS Server/Client Version Compatibility

This section only applies if you are installing a new version of the operating system into a RIS environment on a server that is running a previous version of the operating system. If not, go to section Section 3.2.

Perform the following steps to install the operating system into a RIS environment on a RIS server running a previous version of the operating system:

Log in to the RIS server as root, or use the su command to gain superuser privileges.

Mount the distribution media. For example, if your distribution media is a CD-ROM:
- If you are using an older version of the operating system that uses traditional device naming conventions (/dev/rrzNc), use a mount command similar to the following example:
```
# mount -rd /dev/rz4c /mnt
```
  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 device special file name for that unit.
  The CD-ROM drive's unit number is 4, and in this example is /dev/rrz4c.
  If you do not know your CD-ROM's unit number, refer to 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
```
  This 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.
  The CD-ROM drive's unit number is 0, and in this example is /dev/disk/cdrom0c.
  If you do not know your CD-ROM's unit number, refer to Section 1.3.

Use the utilupdate command to update the necessary RIS utilities on the server, as shown in the following example:
```
# /mnt/isl/utilupdate -r -m /mnt
```
- The -r option causes the utilupdate utility to copy files from the distribution media to the server's /usr/sbin directory. This ensures RIS compatibility with the operating system.
- The -m /mnt argument specifies the mount point of the distribution media and is a required parameter.

This command copies any files in the /usr/sbin directory to files with a .pre-V5.0A suffix. For example: /usr/sbin/setld is copied to /usr/sbin/setld.pre-V5.0A.

When the utilupdate script completes, this RIS server can serve the current version of the operating system to RIS clients. Appendix C describes the utilupdate utility.

When you are installing the operating system, if the utility finds existing *.pre-V files on your system, the existing utilities are updated with no changes to the saved *.pre-V files. If the server is already running the new or updated version of the operating system, a confirmation message is displayed and no copies are made.

After a client's operating system is installed and running, a server can serve additional product subsets to a client running a compatible operating system. The client loads the additional subsets with the SysMan Menu.

A RIS client can be booted by a RIS server by using the BOOTP protocol. This means that a server can serve both the base operating system as well as additional product subsets to the client over the network. The client loads additional product subsets with the SysMan Menu.

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.2 briefly describes the advantages and disadvantages of establishing symbolic links instead of extracting the software subsets into the RIS server area.

See Chapter 1 for a description of the RIS area's contents. A given server can have multiple RIS areas, in which some of the subsets can be duplicated. To organize your RIS server's disk space, perform the following steps:

Determine how many RIS environments you want.

Choose the software subsets you want to install, organizing them by the environments where they are to be installed.

Use the subset size information in the Release Notes to ensure that you have adequate disk space.

3.3 Installing the Operating System on the RIS Server

The Installation Guide describes how to install the operating system on the server, and lists all of the supported software subsets along with their names and descriptions. This information helps you organize the process before you perform the installation.

Because RIS areas are created in the /var/adm/ris directory, you may want to specify a separate /var file system during the installation for extra disk space. Refer to the instructions in the Installation Guide to specify a separate /var file system.

Install the Remote Installation Service and Additional Networking Services subsets on the system to be used as a RIS server. These subsets contain the tftp networking utility and the joind bootstrap daemon. If you want to use the Internet Boot Protocol (BOOTP) server daemon bootpd, install the Obsolete Commands and Utilities (Obsolete Components) subset OSFOBSOLETE505.

After you install the operating system, enter the following command to see if these subsets are installed:

# /usr/sbin/setld -i | grep -E "RIS|INET|OBSOLETE"

Your output is similar to the following:

OSFCLINET505   installed Basic Networking Services 
    (Network-Server/Communications)
OSFINET505     installed Additional Networking Services 
    (Network-Server/Communications)
OSFOBSOLETE505 installed Obsolete Commands and Utilities 
    (Obsolete Components)
OSFRIS505      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. If the Additional Networking Services, Remote Installation Service, or Obsolete Commands and Utilities subsets are not installed, you must install them with the SysMan Menu.

Refer to the Installation Guide and the sysman(8) reference page for more information about installing subsets.

3.4 Setting Up a Local Area Network

You must connect the RIS server and all of the client processors to a LAN using either Ethernet, FDDI, or Token Ring. The server and clients all must be on the same network or subnetwork unless the router connecting the networks or subnetworks can forward BOOTP requests.

For instructions on setting up a local area network, refer to the Network Administration guide.

3.5 Loading and Registering the Server Extensions License

The Server Extensions license (OSF-SVR or UNIX-SERVER) provides the right to use the RIS software if you are running this operating system. A product authorization key (PAK) accompanies the license. You must register the PAK information for your system before it can be configured as a RIS server. Register the PAK information by using the License Manager application.

Refer to the dxlicense(8) reference page, the Software License Management guide, and the License Manager online help for more information about registering license PAKs.

After you have registered the PAK information, you can complete the server setup tasks described in Chapter 4.

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:

Edit the file /tcb/files/auth/r/ris. Each field is delimited by a colon ( : ).

Set the current password field u_pwd to an asterisk ( * ).

Set the u_succhg value to any non-zero value. This value is a time_t type printed with %ld.

Set the u_life and u_exp fields to zero.

The following is an example of a modified /tcb/files/auth/r/ris user file:

ris:u_name=ris:u_id#11:\
        u_oldcrypt#0:\
        u_pwd=*:\
        u_exp#0:u_life#0:\
        u_succhg#79598399:\
        u_suclog#79598399:\
        u_lock@:chkent:

After you make these changes, the RIS password should not expire and cause a denial of service to clients.