
John V. answered 11/19/20
Cisco/Juniper/Microsoft Certified Network Plumber
The key to answering the SDN related questions (1 and 2) is to understand what OpenFlow is:
Firstly, OpenFlow is not synonymous with SDN. SDN is more than a split control/data plane. But OpenFlow is used as part of many SDN solutions.
OpenFlow is a network stack designed to manage and direct traffic among routers and switches from various vendors. It separates the programming of routers and switches from underlying hardware. (different vendors do have varying levels of support for OpenFlow.)
The technology consists of three parts: flow tables installed on switches, a controller and a the OpenFlow protocol for the controller to talk securely with switches.
Flow tables are set up on switches. Controllers talk to the switches via the OpenFlow protocol and impose policies on flows. As a result it is the controller that can add, update, and delete flow entries in flow tables, both reactively and proactively.
In an OpenFlow network, each OpenFlow switch contains at least 1 flow table (usually more) and a set of flow entries within that table. These flow entries contain match fields, counters and instructions to apply to matched packets. If a matching entry is found, the instructions associated with the specific flow entry are executed. If no match is found in a flow table, the outcome depends on the configuration of the Table-miss flow entry. The Table-miss flow entry is the last in the table. It’s basically a catch-all, and the actions to be taken depend on how you configure it. You can forward the packet to the controller over the OpenFlow Channel, or you could drop the packet, or continue with the next flow table.
Hope that helps
Sarah D.
Thank you for the explanation but I still not sure what to pick as for Q1,2,3. As you said I am thinking the Q1 would be flow table and Q2 remote controller, not sure about Q311/19/20