Changes between Version 50 and Version 51 of Internal/OpenFlow/Controllers/MultiCtl

Timestamp:

Jan 30, 2013, 1:24:49 AM (11 years ago)

Author:

akoshibe

Comment:

—

Internal/OpenFlow/Controllers/MultiCtl

@@ -475 +475 @@
  1. reworked routing table + forwarding table for the control plane implementing a very simplified RIP/split horizon -like service info dissipation mechanism. Hop count is used as the preferred reachability mechanism, and is encoded in the CPLVendorData header. 
  1. transparency mechanism for topology information. A higher-tier controller seeking switch info is assumed to be seeking topology transparency. This implies:
-  * transmission of all collected feature replies from the lower tiers (no two low-tier controllers connect to the same switch)
-  * escalation of topology data (!PacketIn and !PortStats, required by topology and link discovery modules)
- 
+    * transmission of all collected feature replies from the lower tiers (no two low-tier controllers connect to the same switch)
+    * escalation of topology data (!PacketIn and !PortStats, required by topology and link discovery modules)
+ 1. Need to work out the details of what is needed/not needed for a control plane to be deemed functional. Do we need all of the controllers properly running? Currently this is the case. However, if each controller is a separate functional component, technically not all components are equally critical to the core functions of a NOS.  
 ----
 [#home Home.]