Generic Network Topology Discovery Agent
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing network topology discovery mechanisms require multiple discovery agents for different switch vendors, leading to duplicate code, increased complexity, and difficulty in field trials due to the need for code changes and recompilation for each vendor-specific switch.
Innovation Solution
A multi-faceted discovery agent that adjusts its Layer 2 connectivity and VLAN discovery algorithms based on the Management Information Base (MIB) organization of the network switch, using a generic agent with a configuration schema that encapsulates specific steps for each switch type, allowing a single agent to communicate with various network devices using a network management protocol.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple discovery agents are used for different switch vendors, then vendor-specific compatibility is improved, but device complexity and code duplication increase
Solution Approach 1:
The patent implements a universal discovery agent that can discover multiple vendor-specific switch types (Cisco, HP, Foundry, etc.) using a single multi-threaded process. The agent loads vendor-specific MIB modules dynamically and uses configuration schemas to adapt its discovery algorithms to different switch types, eliminating the need for separate discovery agents for each vendor while maintaining full compatibility.
Solution Approach 2:
The discovery agent is segmented into modular components: a core discovery engine, vendor-specific MIB modules, and configuration schemas. This segmentation allows the system to handle different vendor types through standardized interfaces while maintaining vendor-specific functionality, reducing complexity by organizing code into manageable, reusable units.
2Adaptability or versatility
If multiple discovery agents are used for different switch vendors, then vendor-specific functionality is improved, but ease of maintenance and field trials worsen due to code changes and recompilation requirements
Solution Approach 1:
The system dynamically loads vendor-specific MIB modules and configuration schemas at runtime rather than requiring static compilation. This allows the discovery agent to adapt to different switch vendors without recompilation, and enables easy updates by simply replacing MIB modules or configuration files rather than recompiling the entire agent.
Solution Approach 2:
The patent uses configuration schemas that can be copied and modified for different vendor types without changing the core agent code. Vendor-specific discovery parameters and algorithms are stored as configurable schemas that can be replicated and adjusted as needed, simplifying maintenance and deployment across different environments.
3Device complexity
If a generic agent with configuration schemas is used, then device complexity is reduced, but adaptability to different network device types may worsen
Solution Approach 1:
The configuration schemas allow dynamic changing of discovery algorithm parameters based on the detected switch vendor and model. The generic agent adjusts its behavior by loading appropriate configuration schemas that specify vendor-specific MIB modules, discovery parameters, and algorithm settings, maintaining full adaptability while using a single agent instance.
Data Source
AI summary
The present invention relates to a method for determining the topology of a network. The method, including the step of a generic agent communicating with a plurality of network devices, using a network management protocol, in order to extract data about the network; wherein the generic agent includes a communication algorithm and wherein each network device corresponds to one of a plurality of network device types and the algorithm is adjusted for each network device using a configuration schema based on the corresponding network device type.


