2
Votes

Traffic interruption after Omada Update

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
 
2
Votes

Traffic interruption after Omada Update

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Traffic interruption after Omada Update
Traffic interruption after Omada Update
2023-05-16 09:56:54 - last edited 2023-05-17 06:23:12

Hi.

 

After updating Omada Software Controller, it automatically readopts and reconfigures all switches and AP. During this adoption/configuration phase, the switches do not forward anything. Although this only takes a couple of seconds, it leads to major disturbances of clustered environments.  

 

Here are some ideas that might solve this problem:

1. The controller compares the current config of the switch with its own and only starts reconfiguration if there are some changes (which are usually not there after a controller update).

2. The switches are not adopted/configured all at once but subsequently, so there is always at least one working route for cluster communication.

3. Switches can be tagged as edge or core switches. At least for the core switches, #2 is applied.

 

Any other ideas?

 

Kind regards

Martin

 

#1
Options
1 Reply
Re:Traffic interruption after Omada Update
2023-05-16 13:53:13 - last edited 2023-05-17 06:23:04

  @mwo 

 

Agree, the controller update seems excessively invasive/impactful.  We already know that the controller can detect config inconsistencies between the controller DB and the device config (you get a message asking you to force update).  This same tech could be applied in reverse to avoid unnecessary device restarts.

 

@Fae  This should probably get moved to the Requests and Suggestions forum.

<< Paying it forward, one juicy problem at a time... >>
#2
Options