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

UTM 9.601 - RED issues!

Since upgrading all our customers to 9.601, a bigger part of them are complaining about RED's re/disconnection in a no-pattern way.

It started for all of them just the night we upgraded to 9.601, and they all are on different ISP's and located different places around the country.

Been with Sophos support for 2 hours today, and now they escalated it to higher grounds.

Will return with an update....

Suspicious entries in the log - but all connected REDs do this before connection:

2019:03:06-15:15:38 fw01-2 red_server[17509]: SELF: Cannot do SSL handshake on socket accept from 'xxx.xxx.xxx.xxx': SSL connect accept failed because of handshake problems

2019:03:06-15:15:46 fw01-2 red2ctl[12420]: Missing keepalive from reds3:0, disabling peer xxx.xxx.xxx.xxx

I know the last line is written before the tunnel disconnects, because there was no "PING/PONG" answer...

One customer has 2 x RD 50, one 1 100% stable and the other fluctuates in random intervals - we replaced this with a new RED 50, but the same thing occurs.



This thread was automatically locked due to age.
Parents
  • Sorry,

     

    but it is a very angry issue! And i think nothing happend by Sophos. We upgrade an Friday one our SG105 with 1 RED50 to 9.605-1. Now the RED50 doesn´t boot, no Workaround helps. It is bullshit, sorry.

    Now i take a RMA and one of our Office ist down since Friday.

    Greetings,

     

    Ingo 

Reply
  • Sorry,

     

    but it is a very angry issue! And i think nothing happend by Sophos. We upgrade an Friday one our SG105 with 1 RED50 to 9.605-1. Now the RED50 doesn´t boot, no Workaround helps. It is bullshit, sorry.

    Now i take a RMA and one of our Office ist down since Friday.

    Greetings,

     

    Ingo 

Children
No Data