Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm trying to configure an identical pair of devices to run Vyatta and work as a failover cluster. I can configure the clustering just fine through

vyatta@firewall# [set clustering configs]
vyatta@firewall# commit

vyatta@firewall# save

The configs all work just fine - I can see the configs by running show cluster

show cluster 
 dead-interval 5000
 group cluster1 {
     auto-failback false
     monitor [monitor ip]
     primary bender
     secondary flexo
     service [private IP]/16/eth1
     service [public virtual IP]/28/eth0
 interface eth5
 keepalive-interval 2000
 monitor-dead-interval 5000
 pre-shared-secret supersekretpassword

on both machines.

However, whenever either machine reboots, the cluster config gets dropped. It looks like it's loading an old version of the boot config file that doesn't get updated when you run save.

Anyone else have this issue?

share|improve this question
up vote 1 down vote accepted

There is a known bug (Bug 3877 - Cluster configuration does not load if cluster communication interface is down on boot) in the Vyatta software. If the cluster monitor link is not up at boot time (in your case eth5) it doesn't load the cluster info. If you look at the actual config.boot file, or issue a load command, you will see it.

Hope this helps.

share|improve this answer

Still no real clue as to what was causing the problem... I ended up reinstalling Vyatta on both firewalls and re-creating the configs, with cluster configs and conntrack-sync on each device individually. After that, they seemed to work just fine.

I'd love to know what caused it to flip out, though.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.