SDN Controller OAM Module Distribution for Datapath Nodes
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Software defined networking (SDN) datapath nodes lack the intelligence to implement Operations, Administration, and Management (OAM) functions independently, requiring special programming for each node, which goes against the SDN principle of centralized control.
Innovation Solution
A controller node determines the OAM actions capable by each datapath node and communicates OAM tool modules to implement OAM functions, allowing multiple types of datapath nodes to execute OAM actions under centralized control without individual programming.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If datapath nodes are specially programmed to implement OAM functions, then OAM functionality can be achieved, but this goes against the SDN principle of centralized control and increases device complexity
Solution Approach 1:
The controller node acts as an intermediary that provides OAM tool modules to datapath nodes. Instead of programming each datapath node directly with OAM functions, the controller generates and distributes pre-computed tool modules that datapath nodes can execute. This mediator approach maintains centralized control while enabling OAM functionality across the network.
Solution Approach 2:
The system uses copies of OAM tool modules that can be distributed to multiple datapath nodes. The controller node creates a master copy of the OAM tool module and distributes it to relevant datapath nodes, allowing them to execute the same functionality without individual programming. This copying approach reduces complexity while maintaining reliable OAM implementation.
2Adaptability or versatility
If multiple conventional network nodes with combined control and forwarding planes are used, then network functionality can be implemented, but programming each node becomes complex and costly
Solution Approach 1:
The controller node is designed with universal capability to program multiple types of datapath nodes through a common interface. The OAM tool module can be adapted to work with different datapath node types (switches, routers, etc.) without requiring separate programming for each node type. This universality simplifies the manufacturing and deployment process while maintaining network functionality.
Solution Approach 2:
The controller node serves as a universal intermediary that handles programming for multiple datapath nodes. Instead of programming each individual node, the controller generates unified OAM tool modules that can be distributed to various node types, significantly reducing the complexity of implementing network functionality across heterogeneous devices.
3Device complexity
If a single controller node is used to control multiple datapath nodes, then network cost is reduced and centralized control is achieved, but OAM intelligence must be distributed to nodes
Solution Approach 1:
The controller node performs preliminary action by pre-computing and preparing OAM tool modules before distributing them to datapath nodes. The controller analyzes the network topology and flow information, then generates appropriate OAM tool modules in advance. This preliminary action reduces the operational burden on datapath nodes while maintaining centralized control architecture.
Solution Approach 2:
The controller node acts as an intermediary that bridges the gap between centralized control and distributed execution. It receives OAM requests, processes them centrally, generates appropriate tool modules, and distributes them to datapath nodes for execution. This intermediary role maintains the simplicity of centralized architecture while enabling ease of operation for OAM functions.
Data Source
AI summary
Communication of a module to a datapath node is disclosed. A controller node receives connection information identifying a first datapath node in communication with a network. The controller node obtains Operations, Administration, and Management (OAM) information including an OAM action set that identifies one or more OAM actions the first datapath node is capable of implementing at the first datapath node. A first OAM tool module is determined that is operative to perform at least one of the one or more OAM actions identified in the OAM action set to implement a first OAM tool function. The first OAM tool module is communicated to the first datapath node.