"Walter R. Moore" <[EMAIL PROTECTED]> wrote: > hydra # utgstatus > hostflags interface flags > 4.38.104.0/24 > --------- ------------------- > hydra TN 4.38.104.2 UA- > medusa TN 4.38.104.5 -A-
The group-memebership protocol isn't able to see traffic from the other machine. It was able to see it in the recent past, which is how the machines are aware of each other and know that belong to the same group, but they're no longer able to exhange membership handshakes. By default the membership protocol uses multicast datagrams. It's possible that the switch connecting the machines has lost its mind and is no longer forwarding multicast packets, or it's possible that there's a problem with multicast handling in the kernel or in the NIC driver. I'd try power-cycling the switch. If that works then I'd look for an update to the switch firmware, multicast is something that some switch vendors are still struggling to do right. If power-cycling the switch doesn't work then that points at a kernel or NIC problem, so make sure these machines have up-to-date patches. You might be able to get temporary relief by utrestart'ing one or both servers (the restart of a multicast-using app can sometimes prod the system into doing the right thing). A longer-term workaround might be to tell the membership protocol to use broadcast rather than multicast, you can do that by setting enableMulticast=false in /etc/opt/SUNWut/auth.props and then running utrestart. OttoM. __ ottomeister Disclaimer: These are my opinions. I do not speak for my employer. -- ___________________________________________________________ Sign-up for Ads Free at Mail.com http://promo.mail.com/adsfreejump.htm _______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users
