You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current implementation, can support up to 10000 switches totally. This limitation derives from some naming conventions for switches, that were posed by a specific controller, OpenDaylight. A strange behaviour was observed with wireshark on the southbound interface of the controller, flooding of FLOW_MOD messages and also error messages in the log of the controller, when switches did not follow a specific naming pattern. Switch names affect DPID value, used by the controller to identify them. This might be a controller bug. We should figure out how we could make a better implementation to support topologies with more than 10000 switches
The text was updated successfully, but these errors were encountered:
The current implementation, can support up to 10000 switches totally. This limitation derives from some naming conventions for switches, that were posed by a specific controller, OpenDaylight. A strange behaviour was observed with wireshark on the southbound interface of the controller, flooding of FLOW_MOD messages and also error messages in the log of the controller, when switches did not follow a specific naming pattern. Switch names affect DPID value, used by the controller to identify them. This might be a controller bug. We should figure out how we could make a better implementation to support topologies with more than 10000 switches
The text was updated successfully, but these errors were encountered: