Thank you Bob. Yes I made sure the gmSignatures were the same. At this point, I believe its down to two potenital issues.
I need to try again and this time set the multicast TTL above 1, I will start with 50 or so. Also, having the network guys confirm that the multicast rendezvous point is working from both sides. Apparently they told me one of the switches doesn't know where its rendevous point is. This is a multicast routing config issue. If it works Ill post an update.. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Doolittle Sent: Tuesday, September 11, 2007 10:09 AM To: SunRay-Users mailing list Subject: Re: [SunRay-Users] WAN Failover Group Setup Lewick, Taylor wrote: > Okay, I realize this config may not be technically supported, but want > to know if it should work. > > I have 3 sunray servers running SRSS 3.1 with Windows Connector > software. > I set up two of the servers on the same subnet in a failover group. > Everything works great. > Network config is no interconnect configuration, just using default IP > addresses with mulitcast for FoG communication. > > A few days later attempt to add the third server to failover group. > This server is in another building on a different subnet. Have > verified with network guys that multicast should route between across the WAN. > > Run the utreplica -p -a on primary, and utreplica -s on secondary. > Also run utfwsync on secondary. > Everything completes, no errors, but when I run utgstatus on the > primary server, it only shows it and the secondary on same subnet. > When I run utgstatus on new secondary, it only shows itself. > You never mentioned the group signature. That also needs to match. Check that /etc/opt/SUNWut/gmSignature is the same on all hosts, and if it isn't use utgroupsig to change it as necessary. In SRSS 4.0, untrusted members of a FOG don't seem to show up utgstatus output, so you can't tell if you have a network issue or a configuration issue. Prior to 4.0, they would show up in the utgstatus output but without the "T" flag indicating that they were not part of the FoG (I'm hoping we can restore the old behavior, which was quite useful for such problems). So if you're not seeing them, the multicast packets aren't traveling over the subnets, as you suspected. > Utreplica -l on primary does show all three servers, and when run on > new secondary it does show the correct primary. > Snooping the interface for multicast and port 7009 only shows > multicast packets staying on the same subnet. > > My question is If I can work out with network team why multicast > packets aren't traversing the WAN then a WAN distributed FoG should > work with this setup correct? > It certainly should. I presume you have checked that the /etc/opt/SUNWut/auth.props enableMulticast is not set to "false", that you haven't set a different multicastAddress, and that the multicastTTL is sufficiently high to reach across the subnets (experiment by setting it to 100 or something temporarily, then reduce it to the size necessary). -Bob _______________________________________________ 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
