It looks like Robyn may have been correct about not releasing IPs
I tried increasing my deadtime but that didin't work.
I tried removing the IPs that weren't being released and it only gave
errors about the next IP on the list before rebooting.
My cluster services consist of 31 IP addresses
Hi there,
Thank you for your email. I am currently away on reservist and will only be
back on the 3rd March 2008.
My access to email during this period will be limited.
If there is any urgent matter that require attention, please contact Choon Kiat
([EMAIL PROTECTED]) during this period and cc
Hi Ben,
You may be running into this issue:
https://bugzilla.vyatta.com/show_bug.cgi?id=2770
which involves clustering over VIF interfaces. This bug has been fixed
in Glendale and the fix will be available in the next release.
You can workaround this issue in VC3 but, you'll have to manually
Hi Ben,
I'm pretty sure that the clustering mechanism will reboot a system as a
last resort if it is unable to stop a resource. What resources do you
have in your cluster? I suppose this could be hardware related if the
systems (and their specific NICs) are having a difficult time
Hello I've been playing with clustering on VC3 (10/29/07) and I can't
get it to work well.
It seems that when one router moves from secondary to primary one or
both router have to reboot. Is this supposed to happen? Furthermore,
if I disconnect the secondary router the primary router or both
No, that's not intentional ;-) I haven't seen that before either - is
there any information
in the log files, or from show cluster status?
Do you end up in a split-brain situation where the two systems can't
exchange heartbeats?
The reboot-on-panic option takes effect on kernel panic, so it
