Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices
There are two types of services that need to be discovered and used by a client:
A firmware server that provides the latest firmware for a Sun Ray Client.
A session server that provides a Sun Ray session to a client.
By default, these services are provided by the same server but they may be separated. There are many ways to configure how these servers are discovered. This section describes using pre-defined DNS entries to enable clients to find the servers. For other discovery methods that may provide more granularity or flexibility, see Chapter 19, Alternate Network Configurations.
The on-screen display (OSD), when enabled, shows status during a client's server discoveries. For example, during DNS lookups, a status line in the OSD window shows the name being looked up and, if one is found, the IP address.
Starting with Sun Ray Software 5.3, the firmware for Sun Ray Clients (called Sun Ray Operating Software) must be downloaded and installed separately on Sun Ray servers. Any Sun Ray server providing the latest Sun Ray Operating Software for Sun Ray Clients is considered a firmware server. For details, see Section 3.2.4, “Installing Firmware Before Sun Ray Software Installation”.
When a Sun Ray Client boots in a properly configured environment, it checks with a firmware server to determine if it needs a Sun Ray Operating Software update. A Sun Ray Client's firmware server is discovered in the following order:
Locally configured value (configured through Configuration GUI)
DHCP Sun Ray vendor option (FWSrvr)
Standard DHCP option 66 (TftpSrvr) (IP Address or DNS name)
DNS lookup of sunray-config-servers (if
mapped to multiple addresses, choose one randomly)
Each of these values are attempted in order until one succeeds. Although it is the last value attempted, the DNS lookup is the recommended firmware discovery configuration, as described below.
If the local configuration value is used and fails, none of the others are attempted. This prevents the overwriting of custom-configured firmware in a situation where the controlling firmware server happens to be temporarily unresponsive. See Section 13.2.11, “Sun Ray Client Boot Process” for more details on how a Sun Ray Client finds its firmware server.
Once a firmware server is discovered by a Sun Ray Client, the
client retrieves a parameter file (.parms)
via TFTP. This file is used by the client to determine if its
currently installed Sun Ray Operating Software is older than the version on the
firmware server. If so, the newer firmware is automatically
downloaded and installed on the client.
In the event of an error in the firmware download, error messages through OSD display icons (if enabled) provide additional information that can be useful in diagnosing and correcting the problem. See Chapter 16, Troubleshooting Icons for details.
By default, a client's firmware uses the configuration
provided by the Sun Ray server's .parms
file, which provides a centralized mechanism to administer
firmware. However, you can enable the Configuration GUI on a
client, which enables users to modify a Sun Ray Client's local
configuration. See Chapter 14, Sun Ray Client Firmware for details.
Once a client resolves whether it has the latest firmware installed, the next step in the boot process is to obtain a session from a Sun Ray server. As with discovering a firmware server, the client searches for a session server in the following order:
Locally configured value (configured through Configuration GUI)
Standard DHCP option 49 (IP Address or DNS name)
The servers= key in the client's
.parms file
DNS lookup of sunray-servers (if mapped
to multiple addresses, choose one randomly)
Each of these values are attempted in order until one succeeds. Although it is the last value attempted, the DNS lookup is the recommended session server discovery, as described in Section 2.2.3, “Using Domain Name Service (DNS)”.
See Section 13.2.11, “Sun Ray Client Boot Process” for more details on how a Sun Ray Client finds its session server.
Although there are multiple ways to configure server discovery, the recommended way is through DNS entries. If the Sun Ray DNS entries are defined appropriately for the Sun Ray Clients, no extra DHCP parameters are required by the Sun Ray Client beyond the basic network information. When the default DNS method for server resolution is used, the TFTP transport is the only method available for Sun Ray Client configuration and firmware updates.
The DNS entries for Sun Ray server discovery are as follows:
sunray-config-servers for firmware
servers
sunray-servers for session servers
In both cases, if the DNS entry contains multiple server addresses, one is picked randomly. And, both entries should consist of several servers in your failover group for redundancy purposes.
A DNS client incorporated in a Sun Ray Client's firmware allows many values to be names rather than IP addresses. Most values can be either a name or an IP address. If a name is specified, the DNS lookup appends the DHCP (or Configuration GUI) provided domain name. Components or the domain name are stripped successively until the lookup succeeds or only two components are left. If none of those lookups succeed, the name is looked up by itself. If the name itself ends with a dot character ("."), the name is taken to be a rooted name, and it is looked up without domain name components appended.
Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices