With latest v7.402, what's the best way to change the heartbeat interface (eg: from eth0 to eth5)? I don't see that is modifyable in the web admin gui.
The "standard" Heartbeat interface is Eth3. Most people assign the Internal interface as the backup for the Heartbeat should the Eth3 connection go down. This all can be changed on the 'Configuration' tab of 'Management >> High Availablity'.
Cheers - Bob
Sophos UTM Community Moderator Sophos Certified Architect - UTM Sophos Certified Engineer - XG Gold Solution Partner since 2005
Not sure about yours, but on my system under 'Configuration' tab of 'Management >> High Availability', I can't change the standard heartbeat NIC, it is greyed out. Maybe because I used automatic configuration of new devices?
I don't think you can change the inteface while HA is active, only by turning it "Off" then back on again.
If you are on a machine that you intend to join to an existing Master, then the mode will change from "Automatic Configuration" to "Hot-standby" or "Cluster" depending on how the Master is configured. This only works if 'Enable automatic configuration of new devices' is checked in the 'Advanced' box on the Master.
If you intended for this to become the Master of an HA installation, then I would NOT set to "Off" as that might cause it to do a factory reset. Instead, restore one of the backups done prior to setting it on "Automatic Configuration" and then select the correct setting.
Cheers - Bob
Sophos UTM Community Moderator Sophos Certified Architect - UTM Sophos Certified Engineer - XG Gold Solution Partner since 2005
I don't think you can change the inteface while HA is active, only by turning it "Off" then back on again.
If you are on a machine that you intend to join to an existing Master, then the mode will change from "Automatic Configuration" to "Hot-standby" or "Cluster" depending on how the Master is configured. This only works if 'Enable automatic configuration of new devices' is checked in the 'Advanced' box on the Master.
If you intended for this to become the Master of an HA installation, then I would NOT set to "Off" as that might cause it to do a factory reset. Instead, restore one of the backups done prior to setting it on "Automatic Configuration" and then select the correct setting.
Cheers - Bob
Thanks for the explanation! Back to my original question: I have a cluster (master/slave) running fine, but I need to change the the main heartbeat interface from eth0 to eth5. What's the best way to do that? Here is what I was thinking: 1) go to web gui, and set HA to off, and this should shutdown slave and factory reset it. 2) enable HA on master again, and pick the eth5 as the main heartbeat interface, enable auto config of new device. 3) power on slave, and let it join cluster.
Last time I tried above steps, the firewall quit working right after step 1. For some reasons, the ASG quit functioning as soon as I set HA off. No one from internal network can browse Internet anymore. I was hoping the single master should at least work, but everyone had to wait until all the above 3 steps were completed.
That's why I am asking to see if anyone has a better solution with no downtime.
The problem is we can't make any changes to the master, the option to change is greyed out. The only way is to turn off the HA first. Unfortunately during my test, turning off HA has a side effect of firewall completely down. You would think the single node should function just fine without HA. I guess that is just a bug.
The problem is we can't make any changes to the master, the option to change is greyed out. The only way is to turn off the HA first. Unfortunately during my test, turning off HA has a side effect of firewall completely down. You would think the single node should function just fine without HA. I guess that is just a bug.
