I have a Solaris Sunray Server on the same LAN as a Linux Sunray Server with the Solaris Sunray Server acting as the dhcp server too. They are not in failover. There are many multihead groups configured on the Solaris Server which I've configured on the Linux Server too. These multiheads are configured using Sunray 1's and 1G's. When a user switches from the Solaris server to the Linux server by any means possible, i.e. utswitch, utselect (Enter Server), the primary sunray switches to the Linux server but the secondary doesn't. Work around is done by plugging a keyboard/mouse into the secondary and running utswitch, etc to get to the Linux server. Whenever the secondary sunray server is power cycled or the Linux server is rebooted, then the secondary goes back to the Solaris Server. I realize that if I broke up the addresses for DHCP and assigned IP's from the Linux sunray server to the secondary sunray's I'd get multihead on the Linux sunray server, but what if I wanted then to go back to the Solaris sunray server at that workstation? I've tried changing "macros" in the dhcpmgr on the Solaris server but that seems to break the authentication all together. 'utmhadm -a' command on the Linux sunray server indicates "<secondaryMAC> not in admin database", but 'utdesktop' says it is. I deleted the utmhadm group and readded it, then it doesn't complain about "not in admin database".
Point is I want to maintain both the Solaris Sunray Server and Linux Sunray Server in non-failover but be able to switch back and forth between Solaris and Linux depending on user. Would AMGH help at all? I will be deploying SunRay 2fs's soon, and they work great in the multihead capacity, but in the meantime I need the 1's and 1G's to be flexible. Thanks, Suzie
_______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users
