Network Management Trap Definitions via Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional SNMP systems require significant engineering effort and source code modifications to support new event traps, making them non-scalable and inefficient in processing new network management events.
Innovation Solution
A network management system is configured to use a trap definitions folder containing specific trap definition files, allowing users to easily add new trap definitions by dropping in auxiliary files, eliminating the need for source code revisions and enabling user-configurable functionality.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the global trap definition file is modified to support a new trap, then the network management software can process the new trap, but significant engineering effort and source code modifications are required
Solution Approach 1:
The patent segments the trap definition functionality from the core network management software by introducing separate trap definition files. These files contain trap information such as trap codes, trap names, and trap descriptions, which can be independently created and maintained without modifying the base software code. This segmentation allows the system to support new traps by simply adding new definition files rather than modifying existing code.
Solution Approach 2:
The patent extracts the trap definition data from the monolithic global trap definition file and software code, placing it into separate, standalone trap definition files. This extraction enables the trap definitions to be independently managed, stored, and loaded, eliminating the need for software engineers to modify source code when new traps need to be supported.
2Adaptability or versatility
If the global trap definition file is modified to support new traps, then new trap processing is enabled, but the process is non-scalable and inefficient
Solution Approach 1:
The patent implements preliminary action by pre-defining trap information in separate trap definition files before the network management software needs to process new traps. These files contain all necessary trap metadata (codes, names, descriptions) that can be prepared in advance and simply loaded into the system, eliminating the need for time-consuming source code modifications and software recompilation when new traps are introduced.
3Adaptability or versatility
If users want to add new trap functionality, then the system needs to support new traps, but source code revisions are required in conventional systems
Solution Approach 1:
The patent enables self-service by allowing users to create and add their own trap definition files without requiring access to or modifications of the software source code. Users can independently define new traps by creating files with the appropriate format and placing them in the system, making the system self-configurable and eliminating the need for software engineers to be involved in adding new trap functionality.
Data Source
AI summary
One embodiment disclosed relates to a process of configuring a network management system to support a new event trap. A new trap definition file is created which corresponds to the event trap. The new trap definition file is dropped into a trap definitions folder that is known to the network management system, Another embodiment disclosed relates to a method of processing an event trap by network management software. The trap is received, and a determination is made as to the trap code of the trap. Trap definition files in a trap definitions folder are scanned for a corresponding trap definition file having the trap code. Other embodiments are also disclosed.