Modular Router Configuration Distribution via OSPF
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current router configurations lack efficient mechanisms for distributing and maintaining consistent configuration modules across networks, leading to potential inconsistencies and reliability issues in routing protocols.
Innovation Solution
The proposed solution involves distributing configuration chunks or modules between routers, using Module Databases (MDBs) with unique IDs and revision numbers to ensure consistency and reliability, with Seed Devices and Alternate Seed Devices maintaining area MDBs and originating updates, and Area Boundary Devices redistributing modules between areas and MRC domains, utilizing protocols like OSPF for communication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If configuration modules are distributed manually or through traditional methods, then device complexity is reduced, but reliability and consistency of router configurations deteriorate
Solution Approach 1:
The patent introduces a Configuration Module Database (CMDB) as an intermediary system that stores and manages configuration modules. Routers query the CMDB to obtain configuration modules, ensuring consistent distribution across the network. The CMDB acts as a central repository that mediates between configuration sources and routers, eliminating manual distribution while maintaining reliability through standardized access procedures.
Solution Approach 2:
The patent implements a feedback mechanism where routers report their configuration module status to the CMDB, and the CMDB tracks which routers have which modules. This feedback system enables the network to detect missing or outdated configuration modules and automatically redistribute them, ensuring consistency without requiring complex manual intervention at each router.
2Reliability
If configuration modules are updated frequently to maintain consistency, then reliability improves, but loss of time increases due to distribution overhead
Solution Approach 1:
The patent pre-loads configuration modules into the CMDB before they are needed by routers. When a router requires a configuration module, it is already available in the database, eliminating the need for real-time generation or complex retrieval processes. This preliminary preparation reduces distribution time while maintaining the ability to update configurations when changes occur.
Solution Approach 2:
The patent implements selective distribution where only the specific configuration modules that routers need are distributed, rather than distributing all available modules to all routers. The CMDB tracks which modules are required by which routers and distributes only those, reducing overall distribution time and network overhead while maintaining configuration consistency where needed.
3Speed
If configuration modules are cached locally on routers, then speed of access improves, but reliability deteriorates due to potential staleness
Solution Approach 1:
The patent implements periodic validation where routers periodically check the CMDB to verify that their cached configuration modules are still current. The CMDB provides version information or validation tokens that routers can check against their local copies. This periodic verification maintains configuration freshness without requiring continuous connection to the CMDB, balancing speed and reliability.
Solution Approach 2:
The patent makes the configuration module distribution system dynamic by allowing routers to query the CMDB on-demand when configuration changes are detected or suspected. Rather than static caching, the system dynamically updates router configurations when the CMDB indicates changes are available, ensuring freshness while maintaining local caching benefits for speed.
Data Source
AI summary
A router can be configured using configuration modules and configuration rules passed between neighboring routers using an extension of the OSPF protocol or other protocol. The rules can be integrated into the configuration modules or separated therefrom. The rules can be interpreted to determine whether the configuration module is loaded within the router. For example, an identifier of the configuration module can be used to uniquely identify the module and compare it to already loaded modules.