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

All RED Devices unable to connect

Last night at 22:58:16 ET all of our RED devices began disconnecting and are unable to reconnect.

We've made no recent configuration changes to our network or Sophos UTMs.

We have 37 REDs of various models, many of which have been in use for several years.

This is a summary of the logged events from the initial disconnection to the current looping errors:

2022:07:28-22:58:16 gateway-2 red_server[34459]: R20001GHKVGDX50: command '{"data":{"message":"Failed to send keepalive frame: Trying to send PING but expecting PONG to receive first","type":"RUNTIME_ERROR_OCCURRED"},"type":"DISCONNECT"}'
2022:07:28-22:58:16 gateway-2 red_server[34459]: R20001GHKVGDX50: Disconnecting: RUNTIME_ERROR_OCCURRED, Failed to send keepalive frame: Trying to send PING but expecting PONG to receive first


2022:07:29-08:22:09 gateway-2 red_server[43473]: SELF: New connection from XX.XX.43.9 with ID R20001GHKVGDX50 (cipher AES256-GCM-SHA384), rev1
2022:07:29-08:22:09 gateway-2 red_server[43473]: SELF: no such client: R20001GHKVGDX50
2022:07:29-08:22:09 gateway-2 red_server[43473]: R20001GHKVGDX50: Sending json message {"data":{},"type":"DEVICE_NOT_BOUND_TO_UTM"}

Failed attempts to resolve:

  • Toggling the devices enabled status
  • Enabling and disabling tunnel compression
  • Changing UTM hostname
  • Physically restarting RED devices

We have a critical case open with Sophos, but it has been over an hour with no contact from them.



This thread was automatically locked due to age.
Parents
  • What happens if you edit and save the Server definition for the device with ID R20001GHKVGDX50?

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • Didn't appear to have any effect.

    Worked with Sophos Support for about 3 hours today. There appears to be a communication issue between our UTM and the cloud interface to save RED configs. Escalation engineered recommended restarting the UTM. Going to try that tonight and see what happens.

    Our case notes:

    Confirmed connection to the registry service over port 3400 but could not find configuration for the RED devices uploaded to the registry service.

    Tried re-starting the red service by enabling debug and disabling debug mode for the RED devices, did not make any difference.

    We also tried manually saving a RED's config to a USB drive and booting from that. Nothing we changed seemed to have any impact.

    I'll update once we have more information and a resolution.

Reply
  • Didn't appear to have any effect.

    Worked with Sophos Support for about 3 hours today. There appears to be a communication issue between our UTM and the cloud interface to save RED configs. Escalation engineered recommended restarting the UTM. Going to try that tonight and see what happens.

    Our case notes:

    Confirmed connection to the registry service over port 3400 but could not find configuration for the RED devices uploaded to the registry service.

    Tried re-starting the red service by enabling debug and disabling debug mode for the RED devices, did not make any difference.

    We also tried manually saving a RED's config to a USB drive and booting from that. Nothing we changed seemed to have any impact.

    I'll update once we have more information and a resolution.

Children
No Data