C H A P T E R 7

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/opt/SUNWut/net/dhcp/SunRay-options

/etc/opt/SUNWut/net/dhcp/SunRay-interface-eth1

/etc/opt/SUNWut/net/hostname.eth1

/etc/hosts

/etc/opt/SUNWut/net/netmasks

/etc/opt/SUNWut/net/networks

/etc/dhcpd.conf

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. 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. 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 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/log/SUNWut/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.

Note - If a common home directory is mounted on machines with different Gnome versions, conflicts between or among the versions cause unpredictable behavior. Do not try to use multiple Gnome versions with a common home directory.

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/log/SUNWut/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 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.