Thread Info
  • State Verified Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 5 replies
  • Subscribers 4 subscribers
  • Views 6865 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

RED Box(es) offline after UTM Update

rem0tecontr0l

Dear Sophos Community

 

this is my first post in this forum :)

 

Im facing a severe issue at the moment and have no idea why this happens to me :(

Ok, let me explain:

 

I'm running Sophos UTM with a bunch of RED Devices (mostly RED15). Yesterday I upgraded the UTM to the latest Firmware 9.509-3.

The Update worked properly and after a while all RED Devices re-connected, except:

 

The RED Boxes, connected to the UTM through an MPLS Network ("Intranet").

Those Boxes have no Internet Access whatsoever and are directly connected to the UTM through a routed MPL Network - wo we provisioned them via USB Stick.

Before the update the MPLS-RED-Boxes worked properly - there are no restrictions in this Network, except the Bandwith Limit of 1 Mbit per Box.

 

The Log shows me messages of such Boxes going online and offline after a short while, but they don't show up as online in the overview at all.

 

Has anyone experienced a similar issue?

If anyone need further Infos, please let me know.

 

Thank you in Advance!

Martin

 

 

////Edit: One Box is now Online through MPLS-Network, so i assume that is no general Issue with Sophos.



This thread was automatically locked due to age.
Parents
  • 0

    Here the Log of one MPLS RED Box:

     

    2018:07:12-09:03:16 utm red_server[29526]: SELF: New connection from 1.2.3.4 with ID A350XXXXXXXXX (cipher AES256-GCM-SHA384), rev1

    2018:07:12-09:03:16 utm red_server[29526]: A350XXXXXXXXX: connected OK, pushing config

    2018:07:12-09:04:48 utm red_server[31714]: A350XXXXXXXXX: No ping for 30 seconds, exiting.

    2018:07:12-09:04:48 utm red_server[31714]: id="4202" severity="infored" sys="System" sub="RED" name="RED Tunnel Down" _id="A350XXXXXXXXX" forced="0"

    2018:07:12-09:04:48 utm red_server[31714]: A350XXXXXXXXX is disconnected.

Reply
  • 0

    Here the Log of one MPLS RED Box:

     

    2018:07:12-09:03:16 utm red_server[29526]: SELF: New connection from 1.2.3.4 with ID A350XXXXXXXXX (cipher AES256-GCM-SHA384), rev1

    2018:07:12-09:03:16 utm red_server[29526]: A350XXXXXXXXX: connected OK, pushing config

    2018:07:12-09:04:48 utm red_server[31714]: A350XXXXXXXXX: No ping for 30 seconds, exiting.

    2018:07:12-09:04:48 utm red_server[31714]: id="4202" severity="infored" sys="System" sub="RED" name="RED Tunnel Down" _id="A350XXXXXXXXX" forced="0"

    2018:07:12-09:04:48 utm red_server[31714]: A350XXXXXXXXX is disconnected.

Children
  • +1 in reply to rem0tecontr0l

    Hey Guys,

     

    we found the Solution ourselves. For anyone struggling with similar Problem:

     

    - Do not keep the USB Stick in the RED Box, the Boxes could get caught in an reboot loop.

    After we removed the USB Stick, the boxes went back online.

     

    This makes no sense to me whatsoever, but thanks to anyone involved.

     

Unfiltered HTML