On Fri, May 8, 2009 at 5:39 AM, Joseph Chiong <[email protected]> wrote: > Please confirm the following is a known problem: > > Case 1: > Given a 10.200.100.0/24 subnet, > > Sun Ray Server 1 (SR1) with single NIC > - Interconnect: 10.200.100.1 > - DHCP Scope: 10.200.100.10 - 10.200.100.70 > > Sun Ray Server 2 (SR2) with single NIC > - Interconnect: 10.200.100.2 > - DHCP Scope: 10.200.100.71 - 10.200.100.130 > > SR1 and SR2 are configured in the same FOG. > > When DTU gets an address in the DHCP scope of SR1 (e.g. 10.200.100.30) and > connects to SR2 in a Kiosk session, this cause a problem.
This should be fine. What problem does it cause? Do these machines literally have a single NIC that is attached to a Sun Ray interconnect, and no other network connectivity? Or do they have other NICs that connect them to the rest of the world? > Case 2: > Given a 10.200.100.0/24 subnet, > > Sun Ray Server (SR) with two NICs > - Interconnect 1: 10.200.100.1 > - DHCP Scope: 10.200.100.10 - 10.200.100.70 > > - Interconnect 2: 10.200.200.1 > - DHCP Scope: 10.200.200.10 - 10.200.200.70 > > Is this a supported configuration? Technically it's supported, but unless you're a DHCP expert we recommend that you don't do this because it can fail in a surprising way. If you decide to take this approach then the range of DHCP addresses should be at least double the number of Sun Rays that you intend to deploy onto this interconnect. 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
