1 |
Sun Ray System Overview |
This chapter describes the following components and how they work:
The Sun Ray website address has changed. The new address is shown below. All the characters should be entered in lower case:
- http://www.sun.com/sunray1
The Sun Ray enterprise server software 1.1 includes several improvements and new features.
Through continuous testing and customer feedback, bugs discovered in the previous release software have been corrected, the installation and upgrade script (utinstall) was refined, and the Administration application has been extended.
The 1.1 version of the Sun Ray server software integrates the following patches:
This list is not complete and newer or additional patches may be available on the CD-ROM. Refer to the Sun Ray Enterprise Server Software 1.1 Product Notes for more current patch information. Additionally, patch information is available at this URL:
- http://www.sun.com/products/sunray1/patches.html
The utinstall script has been refined to ease the process of installing or upgrading to the Sun Ray Enterprise Server Software 1.1. Bugs have been fixed, the script status is more informative, and the script reports any discrepancies and informs the system administrator if a particular action needs to be taken.
Release 1.0 of the Sun Ray server software provided a basic graphical user interface. In this release, an improved, user-friendly, and feature-rich GUI is provided as the default means of administering the Sun Ray server. Command-line interaction with the Sun Ray server is also possible. Refer to "Administration Application Overview" on page 91.
New features have been added to the Sun Ray server software so that power users can customize their servers with special abilities. More information about these features and installing them is in the Sun Ray Enterprise Server Software 1.1 Advanced Administrator's Guide.
New in this release is the Failover option. Two or more Sun Ray servers may "back-up" each other so that in the event of a Sun Ray server failure, a reserve Sun Ray server is available. For additional information regarding the failover feature (including architectural and configuration recommendations), refer to the Sun Ray Enterprise Server 1.1 Advanced Administrator's Guide.
In release 1.1 of the Sun Ray enterprise server software, the Sun Ray server can be configured to recognize additional standard smart card formats. This enables diverse card security protocols from different smart card vendors. Refer to "Managing Smart Cards From Different Vendors" on page 169.
The Sun Ray server software now supports the Sun EnterpriseTM 10000 server. For additional information see "Sun Enterprise 10000 Server Support Provided" on page 4.
The Sun Ray system consists of a SunTM server with the Solaris operating environment running the Sun Ray enterprise server software, Sun Ray 1 enterprise appliances, and an interconnect fabric (network) that ties the server and the appliances together (FIGURE 1-1). The software is installed on a server running the Solaris 2.6 or Solaris 7 operating environment.
With the Sun Ray server software, an end user has access to all Solaris applications and a variety of X Windows and legacy (mainframe) applications (currently third-party emulations). With the installation of third-party applications such as MetaFrameTM from Citrix, an end user can access Microsoft Windows NT applications.
Note - Because the Sun Ray server software is server-based technology, the ratio of appliances to servers depends on the type of applications and their access patterns.
Legend:
The Sun Ray system administrator's responsibilities are to set up, modify, and administer the Sun Ray server software and the interconnect fabric (Sun Ray network) as shown in FIGURE 1-1.
Peripheral devices such as keyboards and mice that are added to the appliances via USB are automatically recognized when attached (hot-pluggable). The Sun Ray server administers these peripherals.
This section describes the various hardware components specific to the Sun Ray system:
This section does not discuss the Sun Ray network configuration.
The Sun Ray server software is designed to operate on a server running the Solaris 2.6 or Solaris 7 operating environment and is used to support the appliances. See "Sun Ray Server Software" on page 17 for more information.
The Sun Ray 1 appliance is the ultimate thin client. It delivers the full functionality of a workstation or a multimedia PC. The key features of the units include:
Each appliance requires a monitor, keyboard, and mouse.
Essentially, the appliance acts as a frame buffer on the client-side of the Sun Ray network. Applications are run on the server and render their output to a virtual frame buffer. The Sun Ray server software formats and sends the rendered output to the appropriate appliance, where it is interpreted and displayed.
Sun Ray 1 appliances are identical, with the exception of the Ethernet MAC address. If an appliance fails, you can just replace it with another appliance. Sun Ray 1 appliance IP addresses are leased. IP address leasing is managed by the Dynamic Host Configuration Protocol (DHCP).
The Sun Ray 1 appliance has a small firmware module that can be updated from the server. This module checks the hardware with a power-on self test (POST) and boots the unit. The Sun Ray 1 appliance also contacts the server to authenticate the end user, and handles low-level input (such as keyboard, mouse, and display information) and output. If there is a problem with the appliance, the module displays an on-screen display (OSD) icon on the screen. Refer Appendix A, Troubleshooting for additional information.
The two most visible connectors (FIGURE 1-2) are the headphone output and the microphone input below the smart card reader slot. The headphone connector is designed to work with low impedance stereo headphones. The end user can adjust the headphone and speaker volume using a Sun keyboard or using the Settings screen. The microphone input supports non-powered and self-powered microphones. The end user can adjust the volume level and microphone input from the Settings screen.
FIGURE 1-2 Front Features of the Sun Ray 1 Enterprise Appliance
Legend:
In addition to the speaker near the front of the appliance you can also attach speakers to the line-out connection on the rear of the appliance (FIGURE 1-3).
FIGURE 1-3 Rear Features of the Sun Ray 1 Enterprise Appliance
Legend:
Note - USB keyboards and mice can be attached to any available USB port on a Sun Ray 1 appliance.
The video in (composite) connector accepts video signals supplied by standard VCRs, camcorders, video disc players, or video cameras. Stereo audio can be supplied through the line-in port. The following television video standards are compatible with the Sun Ray 1 appliance:
Connecting Devices
The Sun Ray 1 appliance can use the SunCameraTM II video camera via the composite video input connector (FIGURE 1-3). You can also attach standard VCRs or camcorders using the composite video connector. The Sun Ray 1 appliance does not manipulate or edit the incoming composite video stream. Refer to your application (for example, video conferencing or video editing) documentation for details on how to bring the data into an application.
Always refer to the product manual for complete instructions about the device you want to attach.
The Sun Ray 1 appliance can connect with other audio equipment to record and play back sound. The volume can be adjusted via the keyboard or through the window manager or through the Settings screen. Refer to "Using Sun Ray 1 Settings" on page 81.
The Sun Ray 1 appliance senses the presence of headphone, microphone, and line-in and reflects their presence in the Settings screen. The Sun Ray server software also plays/records at 48 khz and provides all common sample rates conversions from 8 kHz to 48 kHz.
Adjusting Volume
The end user can use the Sun keyboard's audio keys (FIGURE 1-4) to increase or decrease the volume from the speaker or headphone. Changes can also be made and are reflected on the Settings screen. For example, pressing the Audio Volume Up key (item 3 in FIGURE 1-4) to increase the volume is also reflected via the slider on the Settings screen.
Legend:
Audio Muting
Instant muting of audio is available either from the keyboard or the Settings screen. Pressing the Mute Audio key on an appliance's keyboard is also reflected on the Settings screen (the mute OSD is momentarily flashed on the screen as well).
Audio Playback
The Sun Ray server software mixes with other protocol-based sources, such as media players and the X11 bell, at the desktop during playback. The application playback volume does not affect the desktop volume control. The Sun Ray server software uses a master volume controller (FIGURE 1-5) that allows several feeds (for example, from applications).
Legend:
The Sun Ray 1 appliance uses an internal speaker, located on the right-hand side of the casing, to playback a stereo audio signal mixed into a monaural signal.
Audio playback via headphones is also available (FIGURE 1-2). Adjust the headphone volume using the Settings screen or the Sun keyboard. Keyboard beeps can be controlled through the Common Desktop Environment (CDE). Refer to the xset man page for additional information.
Audio Recording
Refer to your recording application's documentation for specific information on recording sound.
Connecting Devices
Audio line-in and line-out are located on the rear of the appliance. Use these connections for recording standard audio output similar to VCRs, tape decks, and for external powered speakers and power amps.
Note - The audio line-out is at a fixed level and is not adjustable. Audio line input level can be adjusted through the Settings screen.
You can use a variety of external audio devices with a Sun Ray 1 appliance. Always refer to the product manual for complete instructions about the device the end user wants to attach.
Device Emulation Capabilities
Each time an end user logs into a Sun Ray 1 appliance, a script automatically assigns the $AUDIODEV environment variable to that session. One utaudio(1)real-time process is assigned to each session. Refer to the audio(7i)man page for more information.
Note - If a program is "hardwired" to use /dev/audio, there is a dynamic library supplied (directed to by the LD_PRELOAD environment variable in each session), which redirects requests to the Sun Ray 1 appliance audio device emulator. For more information about the library, see "Troubleshooting" on page 193.
The emulated audio device follows the end user session during hot desking. The device name appears in the $AUDIODEV_environment variable but is transparently interpreted by audio programs for Sun systems. Device nodes currently appear in the /tmp/SUNWut/dev/utaudio directory.
Caution - Do not remove the /tmp/SUNWut/dev/utaudio directory. Deleting this directory prevents existing end users (with utaudio sessions) from using their audio pseudo device nodes. This directory tree is completely recreated at boot time.
If your application uses /dev/audio, the Sun Ray server software reroutes the audio signal appropriately.
If you or an end user must power cycle an appliance using the power cord (not the keyboard sequence Control + Power), you or the end user should disconnect the power cord, wait 15 seconds, and reconnect the power cord.
The Sun Ray interconnect fabric is a dedicated and private network. The Sun Ray 1 appliances are connected to the server over this network using an application-specific protocol. This network is based on 10/100BASE-T Ethernet technology, using unmanaged (level-2) switches or hubs and category 5 wiring.
Note - Category 3 wiring using 10BASE-T equipment can be used, but with reduced performance.
Each Sun Ray 1 appliance is attached to the interconnect fabric via its built-in 10/100BASE-T interface.
The scenarios described in the following paragraphs are intended to be conservative methods of providing good desktop performance to Sun Ray users at a low cost. Many other network scenarios are possible.
Caution - To avoid performance degradation, do not connect Sun Ray 1 appliances to networks with other devices.
Currently, 100BASE-T and gigabit Ethernet provide the lowest cost and most simple operation.
For small workgroups with between five and 50 Sun Ray 1 appliances, the Sun Ray server uses either single 100BASE-T cards or a quad 100Base-T card to connect to small (eight to 12 port), shared 100BASE-T hubs. These hubs, in turn connect to the Sun Ray 1 appliances.
For example (FIGURE 1-6), a Sun EnterpriseTM 2 (or a similar model) server with a Sun quad FastEthernetTM card and four inexpensive 100BASE-T hubs can easily support 24 users. Each link from the Sun Enterprise 2 transmits the traffic for six Sun Ray 1 appliances. This example represents a 6 to 1 multiplexing ratio.
Legend:
For departments with groups consisting of 100 or more Sun Ray 1 appliances, the Sun Ray server software uses multiple gigabit Ethernet cards to connect to large 100BASE-T switches. For example, a 100 user departmental system consisting of an Sun Enterprise 450 server, two gigabit Ethernet cards, and two large (72-port) switches deliver services to the 100 Sun Ray 1 appliances (FIGURE 1-7). In this example, the gigabit links are transmitting the traffic for up to 72 Sun Ray 1 appliances. This example represents a 8 to 1 ratio over the end 100BASE-T link speed.
Legend:
The Sun Ray interconnect fabric is a dedicated and private network. Each Sun Ray 1 enterprise appliance must be connected to the interconnect fabric via its built-in network interface. This means that the Sun Ray 1 appliances are attached to a dedicated switch.
Note - The Sun Ray interconnect fabric is not a corporate LAN. It is not to be shared with the corporate LAN or to be used in place of a corporate LAN. Do not connect Sun Ray 1 enterprise appliances to networks with other devices.
Using the Sun Ray server software, you configure the network connections, select an authentication protocol, administer users, define desktop properties, and monitor the system. The Sun Ray server software includes:
The Sun Ray server software process consists of several stages:
Legend:
There are two unique system functions that are crucial to the proper and continued operation of the Sun Ray system. The first of these is the Authentication Manager. The second function is the Session Manager (
For more information see "Session Manager" on page 22). For information on administering ports see "Administering Sun Ray Server Ports" on page 24.The Authentication Manager's main task is to implement the chosen policies for identifying and authenticating end users at Sun Ray 1 enterprise appliances. The Authentication Manager is also responsible for verifying user identities and for implementing site access policies. It must be available any time an end user attempts to access the system using a Sun Ray 1 enterprise appliance. The Authentication Manager is not visible to the end user.
When an end user first accesses the system, the enterprise appliance takes a token and uses it to present credentials to the Authentication Manager to request access. If the user inserts a smart card, the smart card's type and ID are used as the token. If the user is not using a smart card, the enterprise appliance's built-in type and ID (the unit's Ethernet address) are supplied as the token. Every token contains a type and ID that uniquely identifies the token to the Sun Ray system. For smart cards, the type is often derived from the card manufacturer. For enterprise appliances, the type is pseudo.
The Authentication Manager uses pluggable components called modules to implement various site-selectable authentication policies. The site administrator can construct a combination of the different modules and their options to implement a policy tailored to the site's needs. The modules are:
Once the user is presented with the dtlogin screen, the Authentication Manager has successfully completed its tasks.
Users can be registered in two ways:
Note - If self-registration is enabled, users still can be centrally registered as well.
Note - If a token has already been registered, but has been disabled, the user will not have an opportunity to re-register the token; the user must contact the site administrator to re-enable the token.
The interaction between the Authentication Manager and the enterprise appliance works as follows:
Depending on the authentication policy selected, users can be mobile within the workgroup. This means that if an end user starts a session on one appliance and moves to another, the session follows the end user to the new appliance. For more information on sessions, see "Session Manager" on page 22.
This section describes how the Session Manager interacts with the Authentication Manager and directs services to the end user. The Session Manager is used at start up, for services, for managing screen real estate, and as a rendezvous point for the Authentication Manager. The steps below describe how the process starts and ends:
Note - It is important to keep the session ID private. If the end user's session ID is revealed, unauthorized applications can connect directly to the appliance. The xprop(1) command can reveal an end user's secret session ID. Also, careless use of the xhost(1) command (for example, typing xhost +) can allow someone to use xprop to capture an end user's session ID. This action can expose the end user's screen images and keyboard input to anyone interested. Use xhost username@system to enable only those trusted by the system administrator to access the display and the end user's appliance.
For information on administering ports see "Administering Sun Ray Server Ports" on page 24.
A session consists of a group of services controlled by the Session Manager. The session is associated with an end user via an authentication token. A service is any application that can directly connect to the Sun Ray 1 appliance. This can include audio, video, X servers, and device control of the appliance. For example, dtmail is not a service because it is accessed through an X server.
The Session Manager keeps track of sessions and services by mapping services to sessions, and binding and unbinding related services to or from a specific appliance.
The Session Manager only takes authentication from authorized Authentication Managers listed in the /etc/opt/SUNWut/auth.permit file.
The Session Manager is consulted only if the state of the session changes, or if other services are added. When an end user's token is no longer mapped to an appliance (for example, when a card is removed), the Session Manager disconnects the services from the appliance, but the services remain active on the server. For example, programs attached to the X server continue to run, although their output is not visible.
Caution -The Session Manager daemon must be running all the time. You can verify it is running by using the ps command and looking for utsessiond.
If the Authentication Manager quits, the Session Manager disconnects all the sessions authorized by it and tells all the sessions that they will have to be re-authenticated. The services are disconnected, but still active.
If the Session Manager is disrupted, it automatically restarts. Each service contacts the Session Manager and requests being added back to a particular session. If you need to stop and restart both the Authentication Manager and Session Manager, type:
This command restarts both managers:
The Session Manager is configured to accept connections on a specific TCP port (the default is 7007). The Authentication Manager contacts the Session Manager to create and control the attachment and detachment of sessions to appliances by way of a callback mechanism. If the callback address matches what is in the Session Manager file (the list of permitted addresses), then the Session Manager replies to the call and the two managers can converse.
It is imperative that you do not assign other services to use the Sun Ray enterprise server ports. The following list details the port usage in the /etc/inet/services file.
All display rendering (for example, fonts, blending, overlays, compositing) is executed on the Sun Ray server software. Pixels are sent to the Sun Ray 1 appliance in an application-specific format. The Sun Ray server software does not modify or change any APIs. The Sun Ray 1 appliance uses a virtual device driver for each available rendering API (for example, the X11 interface). All rendering from JavaTM is done from the X server (from UNIX® servers), or the Win32 interface (from Microsoft Windows NT servers). Rendering output from the Win32 interface is translated to the native Sun Ray protocol through the use of Citrix clients running on Solaris servers.
Since the Sun Ray 1 appliance uses 24-bit graphics, an internal translation program translates legacy programs that require 8-bit indexed color into the 24-bit format acceptable for use by the Sun Ray 1 appliances. The default visual type is 24 bpp (bits per pixel) with 8-bit displays disabled).
The Sun Ray appliance attempts to determine the monitor's screen resolution using DDC 2B (display Data Channel). When successful, the Sun Ray appliance uses the best resolution possible for a given session. For example, if a session is at the default resolution 1280x1024, the Sun Ray appliance uses the highest refresh rate closest to 1280x1024 (that the monitor claims to support). If the user were configured (using utxconfig) for 1024x768, the Sun Ray appliance would attempt to use the highest refresh rate as close to 1024x768 as possible.
Note - If a monitor is not capable of DDC, the firmware selects the best resolution and refresh rate for the session (based on the server settings). Refer to the utconfig (1m) man page for additional information.
When there is no DDC response from the monitor, the Sun Ray appliance uses the value that is built into the firmware as the display resolution. The Sun Ray appliance can be loaded with two different choices of firmware. The first Sun Ray appliance model shipped with the sun default screen size of 1152x900 at 66 Hz (for use with older Sun monitors). The second Sun Ray appliance model uses the industry standard default screen size of 640x480 at 60 Hz. The installation program can choose which default should be in effect by selecting the correct firmware version.
The Sun Ray 1 appliance uses 24-bit graphics. If an application uses only
8-bit visual types an error message is displayed stating that 24-bit graphics is required. For more information regarding those error messages, refer to "Troubleshooting" on page 193.
Currently, only OpenGL ® 1.2 is compatible with the Sun Ray 1 enterprise appliance. In addition, using OpenGL applications with the 8-bit default visual may inadvertently cause a user's X server to crash.
Note - It is recommended that you use 24-bit visual to run OpenGL. When using the 8-bit visual, the display could become corrupted or the X server could crash. On the 64-bit kernel with 8-bit emulation, even ogl_install_check does not display properly. Currently there is no patch available for OpenGL 1.1.2.
You can download the latest OpenGL packages from the following web sites:
- http://www.sun.com/solaris/opengl
and
- http://www.opengl.org