An enterprise network architect is creating documentation to clarify plane responsibilities and interfaces in traditional versus software-defined controller-based architectures. Match each operational task or network behavior on the left to the corresponding architectural component or interface model on the right.
- Independent, hop-by-hop calculation of routing topology and state maintenance on each individual deviceTraditional Distributed Control Plane
- Exposure of RESTful APIs allowing external management applications and scripts to communicate intent to the controllerController Northbound Interface (NBI)
- Provisioning and device configuration management via protocols like NETCONF and RESTCONF from the central controller to nodesController Southbound Interface (SBI)
- Line-rate frame switching and packet forwarding performed locally in ASIC hardware based on FIB tablesController-Based Data Plane (SDN Data Plane)
Cevap
Independent hop-by-hop topology calculation pairs with Traditional Distributed Control Plane; RESTful API exposure to management applications pairs with Controller Northbound Interface (NBI); Device provisioning via NETCONF/RESTCONF pairs with Controller Southbound Interface (SBI); Line-rate ASIC forwarding pairs with Controller-Based Data Plane (SDN Data Plane).
Independent routing calculations define traditional distributed control planes where every node operates autonomously. Northbound interfaces expose REST APIs for applications to automate network policies through the controller. Southbound interfaces enable the controller to program and monitor network elements using protocols such as NETCONF or RESTCONF. Localized ASIC-based forwarding represents the data plane, which continues to reside on physical network hardware in both traditional and controller-based models.
Adım Adım Çözüm
Anahtar Kavram
Distinction between control plane, data plane, Northbound APIs, and Southbound APIs in traditional vs controller-based architectures.
Tahmini Süre:1m 30s