Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 22 replies
  • Subscribers 7 subscribers
  • Views 7402 views
  • Users 0 members are here
Options
Suggested
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

rbremer

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.
  • 0 in reply to Admin Team

    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".

  • 0 in reply to rbremer

    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

  • 0 in reply to Admin Team

    Its a SUM host definition, maybe that's why it doesn't have an icon?

  • 0 in reply to rbremer

    Hm...

    Why have the Destinations in your Multipath Rules Question Marks?

  • 0 in reply to Admin Team

    Hi Alex

    I would like to give them to you, but the stickiness to the interface cannot be established. I added a secondary external address to FW A and created a second RED tunnel to this new IP, also changed the first multi patch rule to have the destination pointing to that new IP. Still the connection comes into FW A from the IP of the other ISP, so both REDs are established from the same source IP and therefore going across the same interface.

    Maybe the multi path rules are not honored or my RED group is wrong. I specified 3400/TCP, 3400/UDP, 3401/UDP and 3410/UDP in that group, according to the documentation of Sophos.

  • 0 in reply to rbremer

    You're welcome, looking forward to hear good news. ;)

  • 0 in reply to Admin Team

    which UTM, the client UTM or the server UTM?

    Edit: ahh wait, you asked for server UTM. I could use one of the additional address from the transfer network, didn't think about that. Nice one :) Thanks, I will try it tomorrow and give an update.

  • 0 in reply to rbremer

    Ah, now i got it...

    Do you have another external IP on your Server UTM, since you cannot diffentiate the RED Traffic? In my example i have two Server IPs via two lines.

  • 0 in reply to Admin Team

    Hi Alex,

    sorry for all the confusion. Current setup is as follows:

    FW A: one ISP uplink, RED server (plan to upgrade to second ISP link later this month)

    FW B: two ISP uplinks, BGP full table, RED client

    internal routing is all done via OSPF, BGP is only used externally (we advertise our own PI networks behind the FWs)

    RED client is connecting to the external IP of FW A (which is provided in a transfer network from the ISP)

    FW B also has two transfer networks, one for each ISP

    This is the FW B setup:

  • 0 in reply to rbremer

    Hi Ronny,

    to get it: You have two links at your client side and two links at your server side, which are all active? You are able to connect to all of your IPs? You mentioned BGB -> You get a subnet via BGP distributed over two different providers/lines? To which IPs do you connect?

    How's your configuration of the multipath rules? In my screenshot were two black fields in every of the rules. The first field defines the target IP (External Interface IP) to which the RED Tunnel should connect. The second one is the Interface, to which the connection should be bound.

Unfiltered HTML