This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

UTM2UTM RED redundancy

We use UTM2UTM red tunnels for many years and they are working very well. Recently our datacenters have upgraded to multi-homing and with multiple external transfer nets (one for each provider) we would like to have some fail-overs for the RED tunnels. They connect to the external IP address of the UTM, so in case an ISP link goes down the tunnel is also lost. For hardware REDs you can configure a secondary UTM uplink address, which somehow does not exist for UTM2UTM connections.

I tried an availability group, but thats also not supposed as the UTM peer address.

Of course, we could have two tunnels running at all times, one to each ISPs address space and then use OSPF on top of that, but it sounds a bit like overkill.

Any ideas on how that might be possible?

Thank you,

Ronny



This thread was automatically locked due to age.
  • Hi Ronny,

    what's your tunnels doing?

    Since my test environment had no license, i had to install one with Network Subscription, i saw the same behavior after one connection was down. Both tunnels came up, although "Skip rule on Interface error" wasn't ticked.

    Kind regards,

    Alex

  • HI Alex

    no change, the multi path definition is completely ignored by the UTM. I raised a ticket with Sophos support but I have to admit, I have been nothing but disappointed by them so far. I asked the question, how can a multi path definition be used for outgoing connections over multiple uplinks and their answer was "works as designed, case closed". Sometimes you have to wonder what you pay support for.

    So unless something magical happens I am left with a crippled setup which is "not working as designed".