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

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.
  • 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). 

  • FormerMember
    0 FormerMember in reply to lferrara

    Hi lferrara,

    I followed up on this issue and it is still under investigation, I will reply back on this post when there is an update. 

    Thanks,

     

  • 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

  • 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?

     

     

  • ,

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

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

     

  • FormerMember
    +1 FormerMember

    Hi JPC, 

    There is workaround provided for this issue and it is to use unified firmware. In order to change RED firmware to unified navigate to System service > RED > RED beta firmware and enable it. This issue seems to be resolved with use of RED unified firmware. 

    Thanks,

  • 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!

  • Hello JPC,

     

    just browsed through this thread and did not find whether you connected or REDs to a single network or each RED has its individual network.


    In the first case you use a bridge which seams not to be able to add additional interfaces without interruption. Maybe the REDs recognize this an "think" something is wrong and do a reboot.

    There is another thread regarding REDs here which discusses the pros and cons about the two scenarios.