A. J.. Levy wrote:
Strange. I enabled "multicastAddress = 224.101.101.101", did a "utrestart -c" on both servers, and now "utgstatus" works on both systems. But I still don't get both servers in the Sun Ray web GUI, utselect or utswitch. I'm wondering, based on the web GUI, if Sun Ray has somehow set up two interfaces, my global zone (176.1.0.x) as a LAN, without being commanded to, or configured properly, and my intended interconnect (192.168.110.x) properly configured.

For SRSS to work properly, all interfaces utilized by clients must be plumbed and configured in the global zone, since that's where SRSS software runs. Then logical interface instances of those interfaces can be used in the local zones for TX security, but these are invisible to SRSS.

The SRSS group membership traffic runs over the global zone interfaces, not the labeled zone instances.

The group manager information (echo gstatus | /opt/SUNWut/lib/utnetpipe localhost 7010) is used in the same way by all of utgstatus, utswitch -l, utselect, and the web interface. You must always restart SRSS after making changes to auth.props.

If you share a single subnet between your servers (configured in the global zone), then using broadcast is going to greatly simplify your troubleshooting. Be sure to restart SRSS after making such a change, and you'll have a wait a few seconds for the group to assemble.

-Bob

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

Reply via email to