Match each network operation or architectural mechanism to its corresponding structural component in traditional vs. controller-based networking.
- Autonomous path computation executed locally on individual routing nodes using distributed routing protocolsTraditional Network Control Plane
- RESTful API abstractions that enable network applications and orchestrators to communicate policy intent to a centralized platformController-Based Northbound Interface (NBI)
- Centralized software engine maintaining a global network topology view and dictating forwarding logic across the fabricController-Based Centralized Control Plane
- Data-model driven communication protocols (such as NETCONF, RESTCONF, or OpenFlow) used to program physical switch tablesController-Based Southbound Interface (SBI)
Cevap
Autonomous local path computation maps to the Traditional Network Control Plane. RESTful APIs for applications map to the Controller-Based Northbound Interface (NBI). The central software engine maintaining global topology maps to the Controller-Based Centralized Control Plane. Protocols like NETCONF/RESTCONF programming hardware map to the Controller-Based Southbound Interface (SBI).
Autonomous local path computation corresponds to the traditional distributed control plane. RESTful application interaction corresponds to the Northbound Interface. The central topology engine corresponds to the controller's centralized control plane. Protocol mechanisms like NETCONF/RESTCONF/OpenFlow correspond to the Southbound Interface.
Adım Adım Çözüm
Anahtar Kavram
Decoupling and centralization of control planes and API classification (NBI vs SBI) in controller-based networking