On 5/22/08, Gérard Henry <[EMAIL PROTECTED]> wrote: > i have to do it on a machine where SRSS 3.1 is configured with CAM only. > I found this thread related to it: > http://www.filibeto.org/pipermail/sunray-users/2006-August/004378.html > and i'm wondering if there is a better solution now?
The solution is the same. If you don't want to destroy the old configuration and build a new one then you'll need to make the change manually in a few places. You should carry out these changes after you've renamed the system and changed its IP address, and after making sure that the new name and IP are visible in whatever name services are used by the members of the Sun Ray host group to which this system belongs. It would be a good idea to have as few Sun Ray sessions as possible running on the system while this is happening, so use 'utadm -f' as far as necessary in advance of the change to encourage sessions to run on other systems in the group. After you've fixed everything, use 'utadm -n' to allow sessions to be placed on this system. In addition to whatever other things you need to change just to keep the operating system itself happy, you'll need to do the following things to keep your Sun Rays happy. If the Sun Ray server issues DHCP addresses then you need to change the "owner" of every record in every subnet table on this system. The DHCP server writes the IP address returned by the equivalent of "getent hosts `hostname`" into the address record when it takes control of an unowned record. If it sees a different address in the record (eg the system's previous IP address) then it thinks some other system owns that record. This is easy to do manually; see below. If you're changing the IP address that Sun Ray units use when they connect to this machine then you need to fix the places that supply this address to the Sun Ray units. It's probably in a DHCP table somewhere, and probably in multiple DHCP tables if this system is a member of a Sun Ray host group. This is slightly more difficult than changing the "owner" field, because you have to make this change in the middle of a DHCP variable (called a "macro" in the jargon of the Solaris DHCP server) and you might have to change it on multiple systems (perhaps every member of the host group). Depnding on how you run your site the system's IP address might be in some other DHCP service, or with newer releases of SRSS this IP might be in TFTP-able SRSS "params" files or even configured locally in the Sun Ray units themselves. Wherever it is, you have to update it. If this system issues IP addresses onto the subnet whose IP address is changing then if the subnet itself is changing you'll need to create a whole new table for the new subnet, and perhaps delete the table for the old subnet if it's not going to be used any longer. Just use 'utadm' to do both of those tasks. If the system is a member of a group that is using a replicated Sun Ray Data Store then you need to tell the other systems that the name of this system has changed. If this system is a DS secondary then the primary needs to be told about the change. If this system is the DS primary then all of the secondaries need to be told about the change. Use 'utreplica' to make these changes. The DS will then need to be restarted on the systems that were modified, which means that SRSS itself will need to be restarted on those systems. This can be a warm restart, so sessions will be interrupted for a few seconds but not destroyed. If you're a neat freak you might prefer to restart every instance of SRSS in the group, in order to purge the old hostname from the Sun Ray Group Manager table shown by 'utgstatus'. If the old hostname happens to be used in the DS rootDN (look in /etc/opt/SUNWut/utadmin.conf) then don't worry about that, it's OK to leave the old name there. Changing the rootDN without losing the DS content is a major undertaking. If you use the Sun Ray web GUI (actually if you run a web server on this system for any reason) then you might need to tell the web server that the name of the system has changed. If you're using Apache then you definitely need to tell it that the name has changed, by editing the ServerName directive in its httpd.conf file and then restarting the web server. That's everything I can think of. If I've missed anything perhaps someone else can fill the gap. > I have to change the hostname of the running machine, and i don't want > to unconfigure then reconfigure CAM mode with the correct app, it's a > very long time since i had done it. If there's anything in your CAM scripts that depends on the machine's hostname or IP then you'll have to fix those yourself. > I'm trying to grep the name into /etc/opt/SUNWut/* and found some files > containing the hostname. And i also tried to update dhcptab with dhtadm, > but with no success so far! What does "no success" mean? What did you do, and what was the result? You might find it easier to use the 'dhcpmgr' GUI than the 'dhtadm' CLI. In the GUI you can select the 'Owner' column and change the owner for the entire subnet table in one go. You can also use the 'dhcpmgr' GUI to edit this system's IP address in any macros. Don't try to add new Sun Ray subnets manually unless you're certain that you know what you're doing. Using 'utadm' for that is far easier and safer. OttoM. __ ottomeister Disclaimer: These are my opinions. I do not speak for my employer. _______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users
