This is a huge help.
The new (third) member of the FOG is on a different subnet
from the first two, and our NOC disallows multicast across
most of our data center. So, no wonder...
I have options, so shouldn't need to do anything to void the
warranty, at least not yet.
Thanks,
-m
---- Original message ----
Date: Wed, 8 Jul 2009 17:31:53 -0700
From: ottomeister <[email protected]>
Subject: Re: [SunRay-Users] Trouble adding to a FOG
To: SunRay-Users mailing list <[email protected]>
On Wed, Jul 8, 2009 at 12:50 PM, <[email protected]> wrote:
We have an existing FOG of two servers, and we'd like to add a
third.
I've followed the instructions, used "utreplica -p -a" on the
primary, "utreplica -s" on the new secondary
<snip>
But in the web interface on each, nothing has changed. If I
log in to the primary server, it still only lists itself and
the previously-existing secondary in the "Servers" tab. On
the new secondary, it only lists itself.
Replicating the contents the Sun Ray Data Store has nothing to do
with the establishment of a new Sun Ray host group. There's
a page
in the sunray-users wiki
(http://wiki.sun-rays.org/index.php/Host_Group)
that talks about this.
The group will not form until and unless the servers can see each
others' group membership announcements and can agree that their
group signatures match.
Start by verifying that the group signature on the new machine
matches the signature on the existing systems. The output of
'sum /etc/opt/SUNWut/gmSignature' will tell you whether they
match.
If the signatures match then you need to figure out why group
announcements aren't being seen. Group membership traffic is
sent as UDP to and from port 7009. Use 'wireshark' or 'snoop' to
check that the new server is sending announcements (it should
send one every 20 seconds or so) and then try to figure out why
those announcements aren't being seen or accepted by the
original servers.
Announcements are sent as multicast by default, with a
time-to-live
(maximum subnet hop count) of 1 which means that they won't
propagate beyond the directly-attached subnet. If the original
machines don't share a subnet with the new one then technically
your configuration is unsupported but you might be able to make
it work by increasing the TTL on all of the servers. If the
original
servers have been reconfigured to use a non-default multicast
group address or to use broadcasts then you'll need to
reconfigure
the new server to match, otherwise they'll just talk past
each other.
When everything is working the 'utgstatus' command should show
all three servers. The web GUI basically shows a fancy
presentation
of the 'utgstatus' output, so until 'utgstatus' is happy the
web GUI
won't be happy either.
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
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
__________ Información de NOD32, revisión 4215 (20090704) __________
Este mensaje ha sido analizado con NOD32 antivirus system
http://www.nod32.com
