To all,

Yup, apparently that was it.  Our network guy had told us that multicast
was allowed (several times), but as it turns out, he had missed that
IGMP was enabled.  Apparently, if IGMP is enabled but not groups are
created, no one multicasts.  You can either disable IGMP or set up a
group for the appropriate ports.

Thanks for the pointer, brad!

sean

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Brad Lackey -
US-SW Desktop Product Lead
Sent: Monday, December 31, 2007 10:57 AM
To: SunRay-Users mailing list
Cc: Propst, Clinton W CTR 375 CSPTS/SCO
Subject: Re: [SunRay-Users] Trouble getting failover group to function
properly; trusted servers are "available" but not "up"

Do you switches allow multicast? If not, then the group won't work.

As an alternative, you can tell SRSS to use broadcast.

edit /etc/opt/SUNWut/auth.props

uncomment the multicast entry and set it to false.

Brad

Abbott, Sean CTR 375 CSPTS wrote: 

        Hi all,

         

        Myself and my co-worker have been beating our heads against a
wall with this for about 2 days now.  We're ready for some help.  We're
trying to get two solaris 10 boxes, with SRSS 4.0, to get into a working
failover group.

         

        We had 3.1 working on these same two servers, but decided to
upgrade to the 4.0.  We upgraded the OS, and then we uninstalled the old
run ray software and installed the new.  We used the same packages for
both servers, so we're certain we've got the same version of all the
software.

         

        Both sunray's appear to be functioning independently, but they
are not entering into full replication status.

         

        sr01 is our primary, sr02 is the secondary. 

         

        We have two subnets configured under utadm for both servers,
192.168.0.165/27 (sr01), 192.168.0.130/26  network and a
192.168.1.18/29(sr01), 192.168.1.24/28(sr02) network.  (I keep wondering
if the different sizes on the subnets or using two separate subnets
might be causing an issue, but we can't figure out how it would, since
each server knows to contact the other on a specific ip address)

         

        utgstatus shows UA- for the server it is run on, -A- on the
other server.  both show TN on both servers.

         

        We can ping both servers from each other.

         

        both servers are listening on 7008-7012.

         

        utadm -l shows both servers and a broadcast address listed in
the altauth key.  Both have only themselves listed for the firmware
server and the AuthSrvr.  Everything else is identical.

         

        utauthd is running on both servers, using
/etc/opt/SUNWut/jre/bin/java -client auth.utauthd.utauthd for a command.


         

        The admin password is the same on both (we've reset it a few
times to make sure)

         

        group signature is the same on both, we've checked
/etc/opt/SUWut/gmSignature to make sure.

         

        Running a utpulld on the secondary responds with  

        utpulld: starting

        utpulld: terminating normally

         

        The auth_log on the secondary is showing "token query time out
to host sr01 interface 192.168.0.21".

        Googling on that, we tried checking netstat -in (no errors) and
utcapture (no errors), so as far as we can tell it's not a network
issue...

         

        I'm totally out of ideas. What am I missing?

         

        Thanks!

         

        sean

        
________________________________


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


-- 

        Brad Lackey
Desktop Product Lead
US Software Practice
(720) 548-3339
[EMAIL PROTECTED]
        

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

Reply via email to