Hi,
I'm not sure what your question is.
It sounds like you are setting up all your servers in a single
fail-over group, but some of them are across a WAN from
the Sun Rays? Does the WAN provide sufficient bandwidth?
Are there no Sun Rays in the "8th building"?
Is the "9th building" separated by WAN from the 8th?
I'd recommend making your 9th building servers a separate
failover group, and then if your users are mobile between the
9th building and the first 6 use AMGH to bridge them. You
don't use AMGH within a failover group. Within a failover
group hotdesk mobility is automatic.
I presume all your networks route multicast packets properly?
Otherwise you can't have failover groups that span subnets.
Regarding AMGH:
Do all your users use smartcards? Do they have
fixed "seats" from which they normally do their
work, with mobility being the exception rather
than the rule? If so, using AMGH and assigning
smartcards to the failover group near the building
in which the associated user resides would be the
way to go (e.g. your AMGH script should map the
smartcard which belongs to user A, who resides in
building 1, to the servers in building 7, while
the smartcard belonging to user Y, who resides in
building 9, should be mapped to the servers in
building 9). I have a blog about "Getting started
with AMGH" that may help, after you've read the
Admin guide:
http://blogs.sun.com/bobd
Note that, unfortunately, you're using CAM. AMGH
is not supported for CAM yet (will be in the next
SRSS release). However, in my blog I've placed
some tools that should help you use AMGH with CAM.
Not officially supported - a spare time project
from me (consider it a Newtday present :-). If
you're not comfortable using it you're stuck with
configuring a single failover group for now, but
with WAN links in the middle I'd be concerned
about load balancing, since it won't take the
restricted bandwidth bottlenecks into account.
-Bob
David Partingtin wrote:
All,
We are continuing to grow our Sun Rays on one our secure (KG-175
Taclane(E100)enterprise networks. I have 6 buildings with a total of 75 Sun
Ray that are using DHCP Relay to point to the SRS Servers located in a 7th
building on a (utadm -A) shared and (255.255.255.224) subnetted environment.
I currently have the two V240's and two V20's setup for failover in the
seventh building. Both V240's are on the same subnet and work flawlessly for
DHCP Relay Host, failover and session mobility. For Further redundancy and
expansion, I am adding two additional V240's and V20's in an 8th building
data center. The problem is the new SRS servers will be on an entirely new
subnet on the WAN Side. They will be part of the DHCP Relay list for all of
the original 6 buildings with the 75 Sun Rays. So I know for failover and
session mobility I have to use amgh. To further complicate the mix, I am
turning on a new 9th building on the same enterprise secure network with 270
Sun Rays, with 3 V490's and 3 V40Z Servers next week. The V490's will be on
a different WAN subnet, but the 270 Sun Rays are on three (utadm -a )
dedicated SRS subnets (255.255.255.0). My problem is that I need to have
session mobility across the entire enterprise. Not that it complicates
things, but all the Sun Rays are running Windows RDP via rdesktop in CAM,
smart card only mode. Here is the IP Configuration. The IP's are bogus for
security reasons.
Building 7
V240Z SRSSERV1 IP 192.168.1.18
V240Z SRSSERV2 IP 192.168.1.19
Building 8
V240Z SRSSERV3 IP 190.167.1.18
V240Z SRSSERV4 IP 190.167.1.19
Building 1
DHCP RELAY 192.168.1.18, 192.168.1.19 192.167.1.18 192.167.1.19
DHCP IP's offered 22.150.21.2-29
Building 1
Network 22.150.21.0
Subnet 255.255.255.224
Router 22.150.21.1
Broadcast 22.150.21.30
Building 2
DHCP RELAY 192.168.1.18, 192.168.1.19 192.167.1.18 192.167.1.19
DHCP IP's offered 22.150.21.22-60
Building 1
Network 22.150.21.31
Subnet 255.255.255.224
Router 22.150.21.32
Broadcast 22.150.21.61
Building 3,5,6 continue with same IP Scheme and BOOTP Relay's
Building 9
V490Z SRSSERV5
Port 1 WAN IP 192.189.1.1
Port 2 Sun Ray Dedicated DHCP 22.165.100.16-200
V490Z SRSSERV6
Port 1 WAN IP 192.189.1.2
Port 2 Sun Ray Dedicated DHCP 22.165.101.16-200
V490Z SRSSERV7
PORT 1 WAN IP 192.189.1.3
Port 2 Sun Ray Dedicated DHCP 22.165.102.16-200
Sorry about the post being so long, I could really use some guidance. Thanks
for reading.
David Partington
Ft Huachuca, Az
[EMAIL PROTECTED]
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
