Nyheter / Dokumentasjon / Serverpark / Sophos

Sophos

Vi har Brannmur_Pri og Brannmur_Sec hvor den andre er satt som slave. For at dette skal fungere må følgende være satt:

Thought I might provide an update. This has been resolved.
Sophos Support spent a couple weeks investigating and came up with the answer.
The issue here was caused by the virtual MAC address of a UTM HA system.
In short I had two options, either verify the MAC Spoofing function the Hyper-V or disable the virtual MAC on the master UTM before joining the HA.
Details Below:
How to resolve issues with Virtual UTMs configured for High Availability
This article describes some potential issues when using HA with virtual UTMs and how to resolve them.
Related product: Sophos UTM Software Appliance v9.107
Related version: since version 8.0
What To Do
Issue: All connectivity drops after a short time after enabling HA
When enabling HA in a virtual environment, the slave UTM will generate a virtual MAC address for each interface identical to that of the master UTM. In many cases, virtual switches don't handle this properly and connectivity is lost as a result.
To resolve this issue, you can either enable virtual MAC address spoofing on your virtual machine host (to ensure the spoofed addresses are detected correctly), or disable virtual mac address creation on the UTM. See below for instructions on doing so:
Where to configure: Console/SSH
Access required: root
1. Login to the UTM console as root.
2. Enter the following command to determine if HA virtual_mac is enabled:
cc get ha advanced virtual_mac
3. If the output is 1, you can disable it by entering the following:
cc set ha advanced virtual_mac 0
4. Restart all virtual UTMs.
Hope this helps anyone else having the same or similar problem.
-MrGoodBytes