Let me get this straight. Do you have a configuration like this:

DTU  X      Server A        Server B      DTU Y
 \----------/   \-----------/   \---------/
   subnet 1        subnet 2       subnet 3


You create a session on Server B using DTU Y, then you go to DTU X and you are being redirected to server B, which is unreachable from subnet 1?

Did you configure with "utadm -A <subnet>" or "utadm -L" on Servers A and B? If so, this is expected behavior. For a "LAN" configuration, all servers must be reachable from all subnets. This is more of an "Interconnect" configuration, since subnet 1 and subnet 3 are not routable to each other. Thus you should be using "utadm -a <intf>" to configure these subnets. If, however, you have routers between the Servers and the DTUs, yet not all DTUs can reach all Servers, you're out of luck. You might be able to get something to work, but we can't support it or give you a lot of guidance since such a configuration is very hard to manage.

-Bob

Jim Klimov wrote:
Hello Alfred,

  Thanks for the input, but I've thought of utselect, too.
Alas, when the session is redirected to the IP address of
the server unreachable from the DTU, there's no longer any
means to send Ctrl-Alt-Backspace from the Sun Ray DTU to
its current server - these packets don't reach it.

  And pressing whatever keys at the moment that the OSD
shows successful connection to the reachable server (the
one which redirects me further to the unreachable server
that has a session for my token) - pressing whatever keys
didn't help as of yet.


Sunday, April 26, 2009, 6:02:17 PM, you wrote:

AL> I've got "utselect" before dtlogin on my Sun Rays, so the user can choose
AL> which Sun Ray server to log into. Had a similar problem to yours. I use
AL> Ctrl-Alt-Backspace once to bring up utselect. I had a DTU that was hung, and
AL> had to use the Sun Ray GUI to punt the Sun Ray's token from the server that
AL> was having problems. Then, when the DTU attempted a reconnect, it found the
AL> good server. My $0.02.

AL> AJ


AL> On 4/26/09 5:28 AM, "Jim Klimov" <[email protected]> wrote:

Hello SunRay-Users,

  We have an installation with a couple of SRSS 4.0 servers
in a FOG. They have public IP addresses in different subnets
for external DTUs to try and connect to (experimental setup -
we tried to make failover over two different net providers).

  At the moment one servers is reachable over one network,
and another is reachable over the second network. That is,
not "both servers are reachable over both networks".

  I've hit a problem as follows: it is possible that a DTU
(or other Token) already has a session on one server, but
this server is currently not reachable from the DTU in terms
of networking. When the DTU tries to connect, it reaches the
other server of a FOG. This server finds that the token has
a session and redirects the DTU to the unreachable server.

  Is it possible to use some mighty keypress and abort this
redirection - so that the reachable server creates a new
session on itself for this token?


AL> ___________________ AL> AL> This email has been scanned for all viruses by Webroot Email AL> Security System. AL> ___________________




_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users

Reply via email to