Network Device Configuration via Message Bus Intermediary
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current network configuration management in computer networks is bottlenecked by resource limitations in controllers, leading to inefficiencies in distributing and applying configuration changes across many devices, and lacks versatility in interoperating with diverse vendor formats, increasing the risk of misconfiguration and unintended operations.
Innovation Solution
Implementing a message bus system for notification and configuration data distribution between network devices and controllers, allowing devices to retrieve configuration data independently and translate abstract configurations into operational formats, thereby reducing controller load and enhancing interoperability with various vendor devices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the controller pushes configuration data to network devices using traditional protocols, then configuration management is centralized and controlled, but the controller becomes a bottleneck due to resource limitations when managing hundreds or thousands of devices
Solution Approach 1:
The patent introduces a configuration data store as an intermediary between the controller and network devices. The controller publishes configuration changes to the store, and devices subscribe to receive configurations independently, eliminating the controller as a bottleneck while maintaining centralized control through the publishing mechanism.
Solution Approach 2:
Network devices autonomously retrieve configuration data from the configuration data store based on their subscriptions and identifiers. This self-service approach allows devices to obtain configurations without waiting for controller push operations, significantly improving scalability to hundreds or thousands of devices.
2Adaptability or versatility
If the controller manages configuration for multiple vendors' devices using multiple protocols, then device compatibility is achieved, but the controller complexity increases
Solution Approach 1:
The configuration data store acts as a protocol-agnostic intermediary. The controller publishes abstract configuration data without vendor-specific protocol details, and individual devices subscribe and translate the data into their native formats. This eliminates the need for the controller to implement multiple vendor protocols directly.
Solution Approach 2:
The system segments the configuration management functionality: the controller handles high-level configuration intent and publishing, the configuration data store handles data persistence and distribution, and individual network devices handle protocol-specific translation and application. This segmentation reduces controller complexity while maintaining multi-vendor support.
3Stability of the object's composition
If the controller pushes configuration changes to all network devices, then configuration consistency is maintained, but the time required to distribute and apply changes increases
Solution Approach 1:
The controller publishes configuration changes to the configuration data store in advance, and devices independently retrieve and apply them based on their subscriptions. This preliminary publishing action allows parallel configuration application across all subscribed devices, dramatically reducing total configuration change time while maintaining consistency through the shared data store.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
In general, techniques are described for managing, with a network controller for a computer network, the configuration of network devices within the computer network using one or more message buses. In some examples, a controller includes processing circuitry coupled to memory. The processing circuitry is configured to generate data for implementing a configuration change for a network device and store, to a configuration database, the data for implementing the configuration change for the network device. The processing circuitry is further configured to add, to a message queue of a message bus executed by one or more or more computing devices separate from the controller, an indication of the configuration change for the network device to cause the network device to obtain, from the configuration database, the data for implementing the configuration change for the network device.