C H A P T E R 7

Configuration

This chapter describes how to configure the Sun Ray server. Procedures in this chapter include:

To Configure a Dedicated Sun Ray Interconnect Interface

To Configure the Sun Ray Server on a LAN

To Turn the Sun Ray LAN Connection On or Off

To Configure Sun Ray Server Software

To Configure the Sun Ray Server Hierarchy

To Synchronize Primary and Secondary Sun Ray Servers

To Synchronize the Sun Ray DTU Firmware

To Convert and Synchronize the Sun Ray Data Store Port

To Re-enable the Old SunDS Service

To Determine the Integrity of the Configuration Files

To Replace the Xservers and Xconfig Files

To Configure an HTTP Server Manually

To Reboot the Sun Ray Server

For further explanation of Sun Ray network configuration, see of the Sun Ray Server Software 3.1 Administrator's Guide.

Configuring the Sun Ray Server

Sun Ray Server Software manipulates the /etc/dt/config/Xservers file. Generally speaking, you should copy /usr/dt/config/Xservers to /etc/dt/config/Xservers.SUNWut.prototype and customize it as needed. Sun Ray Server Software uses the contents of that file as a base configuration when you add Sun Rays DTUs to /etc/dt/config/Xservers.

The Xservers file shipped with dtlogin includes an entry for DISPLAY:0, on the assumption that there is a frame buffer in the system. On a headless Sun Ray server, you need to configure /etc/dt/config/Xservers.SUNWut.prototype so that dtlogin does not try to start an Xsun on DISPLAY:0. For instructions, see /etc/dt/config/README.SUNWut.

Note - If the server is headless, it has no display and cannot, therefore, have a meaningful value for the DISPLAY variable.

To Configure a Dedicated Sun Ray Interconnect Interface

1. Log in as the superuser of the Sun Ray server, either locally or remotely.

2. Open a shell window and change to the following directory:

# cd /opt/SUNWut/sbin

Note - Make sure that the /etc/hosts file contains the following entry:
ip-address of the system hostname

3. Configure the Sun Ray interconnect interface:

# ./utadm -a interface-name

where interface-name is the name of the interface to the Sun Ray interconnect, for example: hme1, qfe0, or ge0.

The utadm script begins configuring DHCP for the Sun Ray interconnect, restarts the DHCP daemon, and configures the interface. The script then lists the default values and asks if they are acceptable.

Caution - If the IP addresses and DHCP configuration data are not set up correctly when the interfaces are configured, the failover feature cannot work properly. In particular, configuring the Sun Ray server's interconnect IP address as a duplicate of any other server's interconnect IP address may cause the Sun Ray Authentication Manager to generate "Out of Memory" errors.

4. If you are satisfied with the default values, and the server is not part of a failover group, answer y.

5. Otherwise, answer n and accept whatever default values are shown by pressing return or provide the correct values from the worksheet.

The utadm script prompts for the following:

New host address (192.168.128.1)

New netmask (255.255.255.0)

New host name (hostname-interface-name)

Offer IP addresses for this interface? ([Y]/N)

New first Sun Ray DTU address (192.168.128.16)

Total number of Sun Ray DTU address (X)

New authorization server address (192.168.128.1)

New firmware server address (192.168.128.1)

New router address (192.168.128.1)

To specify an additional server list.
If you answer yes, it requests either a filename (filename) or a
Server IP Address (192.168.128.2)

6. The utadm script again lists the configuration values and asks if they are acceptable. Answer appropriately.

If you answer n, go back to Step 5.

If you answer y, the following Sun Ray-specific files are configured:

/etc/hostname.interface-name

/etc/inet/hosts

/etc/inet/netmasks

/etc/inet/networks

The utadm script configures the Sun Ray DTU firmware versions and restarts the DHCP daemon.

7. Repeat Step 1 through Step 6 for each of the secondary servers in your failover group.

8. Do one of the following:

If you upgraded Sun Ray Server Software without upgrading the Solaris operating environment, go to To Synchronize the Sun Ray DTU Firmware.

Otherwise, go to Configuring the Sun Ray Server.

To Configure the Sun Ray Server on a LAN

1. Log in as the superuser of the Sun Ray server.

You can log in locally or remotely use the rlogin or telnet commands.

2. Open a shell window and change to the following directory:

# cd /opt/SUNWut/sbin

3. Configure the Sun Ray LAN subnet:

# ./utadm -A subnet#

Where subnet# is the name (really a number) of the subnet, such as 192.168.128.0.

Caution - If the IP addresses and DHCP configuration data are not set up correctly when the interfaces are configured, the failover feature cannot work properly. In particular, configuring the Sun Ray server's subnet IP address as a duplicate of any other server's subnet IP address may cause the Sun Ray Authentication Manager to throw "Out of Memory" errors.

4. If you are satisfied with the default values, and the server is not part of a failover group, answer y.

5. Otherwise, answer n and accept whatever default values are shown by pressing return or provide the correct values from the worksheet.

The utadm script prompts for the following:

New netmask (255.255.255.0)

New first Sun Ray DTU address (192.168.128.16)

Total number of Sun Ray DTU addresses

New authorization server address (192.168.128.1)

New firmware server address (192.168.128.10)

New router address (192.168.128.1)

To specify an additional server list. If you answer yes, it requests either:

Filename (filename)

Server IP Address (192.168.128.2)

6. The utadm script again lists the configuration values and asks if they are acceptable. Answer appropriately.

If you answer n, go back to Step 5.

If you answer y, the utadm script configures the Sun Ray DTU firmware versions and restarts the DHCP daemon.

7. Repeat Step 1 through Step 6 for each of the secondary servers in your failover group. See To Configure Sun Ray Server Software.

8. Do one of the following:

If you upgraded Sun Ray Server Software without upgrading the Solaris operating environment, go to To Synchronize the Sun Ray DTU Firmware.

Otherwise, proceed to To Configure Sun Ray Server Software.

9. Proceed to To Configure Sun Ray Server Software.

To Turn the Sun Ray LAN Connection On or Off

When you configure a Sun Ray server for a shared network, the utadm -A command enables the server's LAN connection. If you do not use utadm -A, however, and you still wish to enable or disable the LAN connection, use this procedure.

When the LAN connection is turned off, Sun Ray DTUs on the LAN cannot attach to the server.

Tip - If you plan to use an existing DHCP server to provide Sun Ray parameters, use this procedure to turn the LAN connection on or off on the Sun Ray server.

1. Log in as the superuser of the Sun Ray server, either locally or remotely.

2. Turn the Sun Ray LAN connection on:

# /opt/SUNWut/sbin/utadm -L on

Tip - Use utadm -l to verify the current setting for Sun Ray LAN connection. To disable all Sun Ray LAN connections, use utadm -L off.

3. Restart services as prompted:

# utrestart

To Configure Sun Ray Server Software

1. If you have not already done so, log in as the superuser of the Sun Ray server.

You can log in locally or remotely use the rlogin or telnet commands.

2. Open a shell window and change to the following directory:

# cd /opt/SUNWut/sbin

3. Configure Sun Ray Server Software

# ./utconfig

4. Accept the default utconfig values shown by pressing Return or provide the correct values from the worksheet.

The utconfig script prompts for the following:

Whether the script should continue (press Return)

Sun Ray administration password (adminpass)

Sun Ray administration password again

Note - All servers in a failover group must use the same administration password.

To configure the Sun Ray Admin GUI, (press Return)

Web server port number (1660)

CGI username (utwww)

Whether you want to use the existing Apache Web Server to host Sun Ray Web Administration

Note - You may not want to use the existing Apache Web Server if it is already configured for another purpose

Whether you want to enable remote administration.

Whether you want to configure Controlled Access Mode (available for Solaris only). It requests:

User prefix (utcu)

User ID range start (150000)

Number of users (25)

Whether you want to configure for a failover group

Whether the script should continue (press Return)

The utconfig script begins configuring Sun Ray Server Software.

If you responded that this is a failover group, the script requests the signature (signature1)

The signature again

The Sun Ray Data Store is restarted.

Note - The utconfig script states that you must restart the authentication manager. This happens automatically when you reboot the Sun Ray server.

The utconfig script ends, indicating a log file is available at the following locations:

/var/adm/log/utconfig.year_month_date_hour:minute:second.log

Where the year, month, etc are represented by numeric values reflecting the time utconfig was started.

5. Repeat Step 1 through Step 4 for each secondary server if in a failover group.

6. Do one of the following:

If you have a failover group, see To Configure the Sun Ray Server Hierarchy.

Otherwise, go to To Synchronize the Sun Ray DTU Firmware.

To Configure the Sun Ray Server Hierarchy

Perform this task after all servers in the failover group have been configured.

1. If you have not already done so, log in as the superuser of the primary Sun Ray server.

You can log in locally or remotely use the rlogin or telnet commands.

2. Open a shell window and change to the following directory:

# cd /opt/SUNWut/sbin

3. Configure this server as the primary Sun Ray server and identify all secondary servers.

# ./utreplica -p secondary-server1 secondary-server2 ...

Where secondary-server1, secondary-server2, ... identifies the host names of the secondary servers. Include all secondary servers in this command.

The utreplica script:

Stops and starts the Sun Ray services

Reads the Authentication Manager policy

Indicates a log file is available at the appropriate location:

/var/adm/log/utreplica.year_month_date_hour:minute:second.log

4. Log in as the superuser of a secondary Sun Ray server.

You can log in locally or remotely using the rlogin or telnet commands.

5. Open a shell window and change to the following directory:

# cd /opt/SUNWut/sbin

6. Configure the server as a secondary Sun Ray server and identify the primary server.

# ./utreplica -s primary-server

Where primary-server is the host name of the primary server configured in Step 3.

7. Repeat Step 4 through Step 6 for all remaining secondary servers.

8. When you are finished, go to To Synchronize the Sun Ray DTU Firmware.

To Synchronize Primary and Secondary Sun Ray Servers

Log files for Sun Ray servers contain time-stamped error messages which are difficult to interpret if the time is out of sync. To make troubleshooting easier, please make sure that all secondary servers periodically synchronize with their primary server. For instance:

# rdate <primary-server>

To Synchronize the Sun Ray DTU Firmware

Note - This task is performed on standalone Sun Ray servers or the last Sun Ray server configured in a failover group. If your server is not one of these, see To Reboot the Sun Ray Server.

1. If you have not already done so, log in as the superuser of the Sun Ray server.

You can log in locally or remotely using the rlogin or telnet commands.

2. Open a shell window and change to the following directory:

# cd /opt/SUNWut/sbin

3. Synchronize the Sun Ray DTU firmware:

# ./utfwsync

The Sun Ray DTUs will reboot themselves and load the new firmware.

4. When you are finished, go to To Reboot the Sun Ray Server for instructions how to reboot the server.

To Convert and Synchronize the Sun Ray Data Store Port

In place of the old Sun Directory Service (Sun DS) used in Sun Ray Server Software versions 1.0 through 1.3, versions 2.0, 3, and later provides a private data store service, the Sun Ray Data Store (SRDS).

SRDS uses service port 7012, to avoid conflict with the standard LDAP port number, 389. When you upgrade a server to SRSS 2.0 or later, the LDAP port remains in use until all the servers in the failover group have been upgraded and converted. Port conversion is required only if you plan to continue to run SunDS on the recently upgraded SRSS server.

Note - Even though you have upgraded a server, you cannot run the Sun Ray Data Store until you also convert the port number.

Tip - Perform this task on standalone Sun Ray servers or on the primary server in a failover group after all the servers in the group have been upgraded.

1. If you have not already done so, log in as the superuser of the primary Sun Ray server.

You can log in locally or remotely use the rlogin or telnet commands.

2. Open a shell window and change to the following directory:

# cd /opt/SUNWut/sbin

3. Convert and synchronize the Sun Ray Data Store service port number on all the servers in a failover group:

# ./utdssync

This step restarts the Sun Ray Data Store on all the servers.

To Re-enable the Old SunDS Service

This procedure re-enables the old SunDS, in case you need to use it for old private data on the Sun Ray servers.

Note - You can re-enable the SunDS service only if you have chosen to preserve the old SunDS data when you upgraded from an earlier version of Sun Ray Server Software.

The following task requires you to have completed the utdssync command. See To Convert and Synchronize the Sun Ray Data Store Port.

1. If you have not already done so, log in as the superuser of the primary Sun Ray server.

2. Open a shell window and change to the following directory:

# cd /etc/opt/SUNWconn/ldap/current

3. Rename the saved configuration file to dsserv.conf:

# mv dsserv.conf_save_date_time dsserv.conf

where date is the current date in YYMMDD format and time is the time save file is created in <hh:mm> format.

4. Start the SunDS service:

 # /etc/init.d/dsserv start

Support for the Sun DS product was discontinued as of the Sun Ray Server Software 2.0 release. In any case, unless you have purchased the SunDS product separately, you cannot use it.

To Determine the Integrity of the Configuration Files

Two configuration files are susceptible to corruption:

/etc/dt/config/Xservers

/etc/dt/config/Xconfig

When they are corrupt, the dtlogin daemon cannot start the Xsun server properly. To prevent or correct this problem, use the following procedure.

1. As a user of the Sun Ray server, open a shell window and compare the
/usr/dt/config/Xservers and /etc/dt/config/Xservers files:

% diff /usr/dt/config/Xservers /etc/dt/config/Xservers

This command compares a known good file with the suspect file. The output should be similar to the following example:

106a107,130

> # BEGIN SUNRAY CONFIGURATION

> :3 SunRay local@none /etc/opt/SUNWut/basedir/lib/utxsun :3 -nobanner

> :18 SunRay local@none /etc/opt/SUNWut/basedir/lib/utxsun :18 -nobanner

> # END SUNRAY CONFIGURATION

Note - This is a simplified example. Your output may have tens of lines between the BEGIN SUNRAY CONFIGURATION and END SUNRAY CONFIGURATION comments.

In the first line of output, there is 106a107,130. The 106 means that the two files are identical to the 106th line of the files. The a107,130 means that the information on lines 107 through 130 of the second file would have to be added to the first file to make it the same as the second.

If your output shows the first three digits to be a number less than 100, the
/etc/dt/config/Xservers file is corrupt.

2. Compare the /usr/dt/config/Xconfig and /etc/dt/config/Xconfig files:

% diff /usr/dt/config/Xconfig /etc/dt/config/Xconfig

The output should be similar to the following example:

156a157,180

> # BEGIN SUNRAY CONFIGURATION

> Dtlogin.*_8.environment: SUN_SUNRAY_TOKEN=ZeroAdmin.m1.at88sc1608.6d0400aa

> Dtlogin.*_9.environment: SUN_SUNRAY_TOKEN=ZeroAdmin.m1.at88sc1608.a10100aa

> # END SUNRAY CONFIGURATION

Note - This is a simplified example. Your output may have tens of lines between the BEGIN SUNRAY CONFIGURATION and END SUNRAY CONFIGURATION comments.

If your output shows the first three digits to be a number less than 154, the
/etc/dt/config/Xconfig file is corrupt.

To Replace the `Xservers` and `Xconfig` Files

Caution - Replacing the Xservers file requires shutting down all Sun Ray DTU services. Remember to inform users of the outage.

1. As superuser, open a shell window and stop the Sun Ray server:

# /etc/init.d/utsvc stop

2. Replace the Xservers and Xconfig files as appropriate:

# /bin/cp -p /usr/dt/config/Xservers /etc/dt/config/Xservers

# /bin/cp -p /usr/dt/config/Xconfig /etc/dt/config/Xconfig

3. Re-initialize the authentication policy:

# /opt/SUNWut/sbin/utrestart -c

The extra lines within the previous Xservers and Xconfig files are automatically rebuilt.

To Configure an HTTP Server Manually

To successfully configure an HTTP server to host the Sun Ray Administration Tool (Admin GUI), you must choose to configure the web server manually in utconfig. The utconfig script creates the directories, symbolic links, and user/group identities required to operate the Admin GUI.

Any web server can be manually configured to host the Admin GUI as long as:

The web server supports the CGI version 1.1 specification.

The web server supports directory and script aliasing.

The web server allows you to set the user and group ID.

The best way to manually configure a web server is to look at /etc/opt/SUNWut/http/http.conf after running utconfig. This file contains all the specific parameters and values you will need to manipulate in order to properly configure the web server.

For manual configuration, the key components needed to make a web server work with the Sun Ray Admin GUI are:

Component	Description	Comments
port number	Port number that the web server should listen on	The administrator can decide which port number to use. The default is 1660.
document root	The root to the document tree structure (HTML, images, JavaScript, etc.)	The document root must be set to: `/var/opt/SUNWut/http/docroot - document root`
server name	The name of the server the web server is running on	The name of the server where SRSS and the web server are running.
cgi-bin	The directory where files are to be executed as cgi scripts	The cgi-bin directory is: `/var/opt/SUNWut/http/docroot/cgi-bin`
user id	The user id that the web server should be run as	The user to run the web server as. The default value is utwww.
group	The user group the web server should be run as	The group to run the web server as. Only `utadmin` is used at this time.
aliases id	Any other directory aliases used by the HTML or CGI to point to specific directories	Some HTML and CGI files use aliases to access directories in the document tree. These aliases need to be created in order for everything to function properly: `/docroot` `/var/opt/SUNWut/http/docroot/` `/images/ /var/opt/SUNWut/http/docroot/public/images/` `/javascript/ /var/opt/SUNWut/http/docroot/public/javascript/`
homepage	The page where the server should start	Set to `/var/opt/SUNWut/http/docroot/cgi-bin/start`

To Reboot the Sun Ray Server

After following the configuration procedures, reboot the Sun Ray server(s).

1. If you have not already done so, log in as the superuser of the Sun Ray server.

You can log in locally or remotely use the rlogin or telnet commands.

2. Open a shell window and reboot the Sun Ray server:

# sync;sync;init 6

The Sun Ray server is rebooted.

3. Repeat Step 1 and Step 2 for each Sun Ray server.

See Appendix A for more information and procedures.

Configuring the Sun Ray Server

To Configure a Dedicated Sun Ray Interconnect Interface

To Configure the Sun Ray Server on a LAN

To Turn the Sun Ray LAN Connection On or Off

To Configure Sun Ray Server Software

To Configure the Sun Ray Server Hierarchy

To Synchronize Primary and Secondary Sun Ray Servers

To Synchronize the Sun Ray DTU Firmware

To Convert and Synchronize the Sun Ray Data Store Port

To Re-enable the Old SunDS Service

To Determine the Integrity of the Configuration Files

To Replace the Xservers and Xconfig Files

To Configure an HTTP Server Manually

To Reboot the Sun Ray Server

To Replace the `Xservers` and `Xconfig` Files