Like this article? We recommend
Like this article? We recommend
Like this article? We recommend
Network Topology Options
There are three basic topology options for Sun Ray deployment. DTUs can be deployed on:
a directly-connected dedicated interconnect.
a directly-connected shared subnet.
a remote shared subnet.
A Sun Ray server can support any combination of these topologies, which are shown in FIGURE 1.
)
FIGURE 1 Network
Topologies for Sun Ray DTU Deployment
NOTE
Sun Ray traffic on shared networks is potentially more exposed to an eavesdropper than traffic on a dedicated Sun Ray interconnect would have been. Modern switched network infrastructures are far less susceptible to snooping activity than earlier shared technologies, but to obtain additional security the administrator may choose to activate Sun Ray's encryption and authentication features. These capabilities are discussed in the "Encryption and Authentication" section of the Sun Ray Server Software Administrator's Guide.
Directly-Connected Dedicated Interconnect
The directly-connected dedicated interconnect—often referred to simply as an interconnect—places DTUs on subnets that are:
directly connected to the Sun Ray server (that is, the server has a network interface connected to the subnet).
devoted entirely to carrying Sun Ray traffic. Prior to the release of Sun Ray Server Software 2.0, this was the only officially supported Sun Ray topology.
The Sun Ray server, which guarantees the delivery of the full set of DTU configuration parameters, is always used to provide DHCP service for a dedicated interconnect.
Directly-Connected Shared Subnet
Sun Ray Server Software 2.0 introduced official support for DTUs on a directly-connected shared subnet, in which:
the Sun Ray server has a network interface connected to the subnet.
the subnet may carry a mix of Sun Ray and non-Sun Ray traffic.
the subnet is generally accessible to the enterprise intranet.
On a directly-connected shared subnet, DHCP service can be provided by the Sun Ray server, or some external server, or both. Since the Sun Ray server can see broadcast DHCP traffic from the DTU, it can participate in DTU initialization without requiring a DHCP Relay Agent.
Remote Shared Subnet
Sun Ray Server Software 2.0 also introduced official support for DTUs on a remote shared subnet. On a remote shared subnet:
a Sun Ray server does not have a network interface connected to the subnet.
the subnet can carry a mix of Sun Ray and non-Sun Ray traffic.
all traffic between the server and the DTU flows through at least one router.
the subnet is generally accessible to the enterprise intranet.
On a remote shared subnet, DHCP service can be provided by the Sun Ray server, by some external server, or by both. For DHCP service on the Sun Ray server to participate in DTU initialization, a DHCP Relay Agent must be configured on the remote subnet, where it collects DHCP broadcast traffic and forwards it to the Sun Ray server.