After further experimentation with vrrpd, let me amplify my earlier "it doesn't work."
It sort of works, in that the first router to claim the virtual IP address sets it. Although it also does seem to delete your default route. However, when that router goes down, vrrpd never fails over to the other router. I think this is because ifconfig isn't smart enough to know that setting that IP address failed the first time because an OSA (or HiperSocket) won't let you allocate the same IP address from different guests. So the second guest *thinks* it has the virtual IP address, but really it doesn't. And vrrpd doesn't try to re-set it when the other router goes away. At least, that seems to be what's happening--it certainly doesn't pick it up immediately, and it seems that the interval timer is a mere one second, so the delay should be three seconds if I understand the source. Certainly nothing came back within three, or thirty, seconds in my tests. VRT gets around this in a sneaky fashion by watching /var/log/messages to see if setting that IP address failed. If it did it ifconfigs it down, so Linux doesn't (incorrectly) believe that it owns that address. I think that if vrrpd were somehow extended to do this kind of checking, then it would work. Adam
