Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.

Thread Info
  • State Verified Answer
  • +2 person also asked this people also asked this
  • Locked Locked
  • Replies 20 replies
  • Subscribers 44 subscribers
  • Views 3406 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

Multiple Red15s to XG

JPC

I have never seen this happen before and wonder if anyone would have any suggestions.

We have 6 Red15w devices deployed (and connected to our XGs) and had planned many more. We create our network setup and deploy the device without issue.

However, any subsequent changes to any one of the already deployed Reds cause them all to reboot/restart/reconnect.

I have reached out to support and they have not gotten back to me yet. So, I am looking for any suggestions on where to check or what might be causing this to happen.

 

Thanks!



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

    We get the same and we only have 2 Red devices connected, change one and the other reloads its config.  

    Very odd behaviour.

  • 0 in reply to Stewart Harrison

    I would say, you include them anywhere all together to the configuration, so XG has to reload all REDs to get a proper configuration to all REDs. 

    Could you observe the RED.log on XG, in Case you change something? Will the RED service on XG reload or the RED itself because new configuration arrives? 

    Could you show us a example RED config as Screenshot? 

    __________________________________________________________________________________________________________________

  • 0 in reply to LuCar Toni

    I have tested further.

    I have deleted and re-added the Reds. Changed network settings. Changed DHCP settings. Split/Unsplit the network. Disabled/enabled compression.

    Added, removed, changed WIFI settings. Created separate SSIDs (to see if sharing SSIDs/networks might be the cause.

    All changes in these two areas cause all Reds (both wired connection and WIFI) to go offline and restart though only one is edited.

    My past experience with these has always allowed me to add/change as need without bouncing all other devices (SG for sure).

  • 0 in reply to LuCar Toni

    Luca they have an issue with the configuration inside red config that only support can fix. This is clear from beginning. Help them to accelerate the process with support to fix the issue. Thanks

  • 0 in reply to JPC

    Just to be sure: You have only RED15w and all uses the same network (SSID)? 

    So if you change something on the RED15w (no matter which change) all reds reboot? 

    I would assume, if you change something on the SSID, this would be normal (because all REDS have to reload the wireless config). 

    __________________________________________________________________________________________________________________

  • 0 in reply to LuCar Toni

    , 

    you reply does not have any sense. If the user created a ticket with the support, this latter had checked your thoughts at the first instance. Please read carefully before replying.

    Thanks

Reply Children
  • 0 in reply to lferrara

    Why not? 

     

    Having two REDs15w with same SSID and changing this SSID (For example the configuration of MHz) would lead to a reboot of both REDs?

     

     

    __________________________________________________________________________________________________________________

  • 0 in reply to LuCar Toni

    ,

    I hope and I really presume that the support checked this already.

  • 0 in reply to lferrara

    Still waiting.

    With our without SSID spread through the Red 15w (as I have found that standard split does not all the wireless in the red to work correctly) they will all restart.

    Basically, after saving any configuration change to one Red, they will all bounce.

    So, yes, I have given support full access to the devices, provided them with screenshots of them all going down, and email alerts indicating the Red is offline.

    However, there has been no progress to date.

     

  • +1 in reply to JPC

    Hi  

    This is a confirmed issue.  Unfortunately development wont be fixing this as moving to "Unified Firmware" option in the RED settings, will fix the issue.

    If there are more cases for this that come to support, then they may look at fixing the older code.

    Any other people having the same issue, please log a case and reference this tracking number: NC-51090

    Thanks!

    KingChris
    Community Support | Sophos Support
    Sophos Support Videos | Knowledge Base  |  @SophosSupport | Sign up for SMS Alerts |
    If a post solves your question use the 'This helped me' link

Unfiltered HTML