Gary Mills wrote:
On Wed, Sep 26, 2007 at 10:34:42AM -0500, Gary Mills wrote:
I have two X4200 Sun Ray servers in a failover group. Both are
running version 3.1. I'd like to upgrade them to Sun Ray Software 4
09/07, which also requires upgrades to Solaris 10 8/07 by reinstall.
How do I prevent new session creation on one of them so I can upgrade
that one first? I've already tried `/opt/SUNWut/sbin/utadm -f', but I
still see new sessions there after running that command.
I've now completed this upgrade on both Sun Ray servers. Users
conveniently logged out on the weekend. I'm impressed with the
upgrade procedure. They are set up in the same primary/secondary
failover configuration as before. Most users do not use smart cards.
Only the few that do have persistent sessions.
I notice that after the upgrades, almost all of the idle sessions
(dtgreet processes) are on the first server that was upgraded.
Two that I killed from the GUI moved to the second server. One
more moved by itself overnight. I notice also that people who log
in without a smart card always have sessions on the server where
dtgreet was running. There seems to be no load balancing in this
case. Is that supposed to be how it works? I know that if you do
a control-moon on an idle Sun Ray, it will switch over to the other
server most of the time, but we don't want to teach users that.
I thought that load balancing was more dynamic than this.
Sessions will become load balanced when users insert cards, or log out from
a session.
If you're not using CAM/Kiosk mode, then enabling NSCM will mean that
non-smartcard users will get load balanced when they log in, also.
-Bob
Disclaimer: Opinions expressed in this mail are my own,
and are not necessarily shared by my employer
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
