Sun Microsystems, Inc.  Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-75-1007713.1
Update Date:2011-03-16
Keywords:

Solution Type  Troubleshooting Sure

Solution  1007713.1 :   Sun Ray[TM]: The Sun Ray[TM] appliance does not get over the 22D icon state  


Related Items
  • Sun Ray Hardware
  •  
  • Sun Ray Hardware
  •  
  • Sun Ray Hardware
  •  
  • Sun Ray Software
  •  
  • Sun Ray Hardware
  •  
  • Sun Ray Hardware
  •  
  • Sun Ray Hardware
  •  
  • Sun Ray Hardware
  •  
Related Categories
  • GCS>Sun Microsystems>Desktops>Desktop Virtualization>Sun Ray Hardware
  •  
  • GCS>Sun Microsystems>Desktops>Desktop Virtualization>Sun Ray Software
  •  

PreviouslyPublishedAs
210686


Description
The appliance doesn't get over the 22D icon state and you don't get a session.

The OSD icon 22D is the last state on the Sun Ray[TM] appliance. After a while, the appliance tries again and run through it's states, but it always ends in 22D.

See also
* Troubleshooting <Document: 1005063.1> The Sun Ray[TM] appliance does not get over the 22B icon state
* Technical Instruction <Document: 1004977.1> Sun Ray[TM]: OSD Icons on Sun Ray[TM] Server Software (SRSS) 2.0, 3.0 and 3.1



Steps to Follow
The icon 22D means, that the Sun Ray[TM] unit is booting up and is now waiting for the initial connection to a Sun Ray[TM} server. In detail it means that the Sun Ray appliance received all Sun Ray specific DHCP vendor tags, but cannot get a connection to an authentication manager.


If the DTU doesn't get over the 22D state, this can have quite a few possible root causes. The most important ones are described here:

1. Check if the authentication daemon is down or unresponsive

Finer problem statement
The OSD icon 22D stays on the Sun Ray[TM] appliance. After 20 seconds, the appliance tries again and runs through it's states, but it always ends in 22D. The appliance doesn't get over the 22D icon state and you don't get a session.
Note: the server IP addresse is not shown in the OSD icon.

Resolution:
Check if the authd appears in the process list:

# /usr/ucb/ps -axwww | grep utauthd
24557 pts/14   S  0:01 /etc/opt/SUNWut/jre/bin/java auth.utauthd.utauthd

If it is not there, restart the services:

# /etc/init.d/utsv restart

Notice that utauthd troubleshooting is not part of this troubleshooting guide.

2. Firewall blocks the Sun Ray traffic

Finer problem statement
The OSD icon 22D stays on the Sun Ray[TM] appliance. After 60 seconds, the appliance tries again and runs through it's states, but it always ends in 22D. The appliance doesn't get over the 22D icon state and you don't get a session.

Resolution
the firewall is probably misconfigured. Firewall issues are common on Linux, where a firewall is enabled by default. To confirm a firewall issue, briefly
disable the firewall.

On Red Hat ES AS 3.0 Linux, go to the GUI called "Security Level". To access the GUI, run /usr/bin/redhat-config-securitylevel or select "Main Menu/System Settings/Security Level". At the GUI mark your Sun Ray interface (e. g. eth1 as a trusted device or (at your opinion) select "disable firewall" rather than "enable firewall".

On JDS and SuSE run /sbin/yast2 to configure or disable the firewall for the Sun Ray interfaces.

On Solaris, there is no firewall enabled by default. If a firewall has been set up, run the appropriate commands to configure or (at your opinion) disable the firewall for the Sun Ray interfaces.

Notice that firewall configuration for a Sun Ray environment is not part of this troubleshooting guide.

3. AltAuth tag

Finer problem statement
The OSD icon 22D is the last state on the Sun Ray[TM] appliance. After a few seconds, the appliance tries again and runs through it's states, but it always ends in 22D. The appliance doesn't get over the 22D icon state and you don't get a session.

Resolution
The DHCP tag called AltAuth replaces the DHCP tag called AuthSrvr. You will get 22D when the values in the AltAuth tag does not direct the Sun Ray appliance to a server where a Sun Ray authentication manager is running.

Example:

Two servers, 10.50.50.240, and 10.50.50.241.

Misconfiguration on 10.50.21.240 (excerpt from dhcptab, respectively the "dhtadm -P" output). For SRSS 2.0 and higher the command utquery -d is recommended:

 AuthSrvr=10.50.50.240:AltAuth=10.50.50.241:

Here, any Sun Ray appliance which gets a DHCP address from 10.50.50.240 will then try to connect to the authentication manager on 10.50.50.241. If the auth manager on 10.50.50.241 is down, the appliance will not get a session. You will see 10.50.50.241 as server IP address in the OSD icon.

Correct configuration in this example when using AltAuth:
AuthSrvr=10.50.50.240:AltAuth=10.50.50.240 10.50.50.241:



Product
Sun Ray Server Software 3.0
Sun Ray Server Software 2.0
Sun Ray 1 Ultra-Thin Client
Sun Ray 100 Ultra-Thin Client
Sun Ray 1g Ultra-Thin Client
Sun Ray 150 Ultra-Thin Client
Sun Ray Server Software 3.1
Sun Ray 2FS Virtual Display Client
Sun Ray 2 Virtual Display Client
Sun Ray 170 Ultra-Thin Client

SunRay, sunray, OSD, 22D, Linux, Red Hat, JDS, SuSE, AltAuth, AltAuthSrvr, DHCP, firewall
Previously Published As
80507

Change History
Date: 2006-05-03
User Name: 111868
Action: Approved
Comment: checked trade mark - ok
checked keywords - ok
checked expiry date - ok
checked audience - ok
checked product tags - ok
publishing

Attachments
This solution has no attachment
  Copyright © 2011 Sun Microsystems, Inc.  All rights reserved.
 Feedback