Bulk Trap Message Aggregation for Network Event Reporting
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Network congestion and processor overload in network management systems occur due to the large number of trap messages sent by network elements for catastrophic failures or significant configuration changes, such as virtual circuit failures or creations, overwhelming the system.
Innovation Solution
Packaging event information for multiple events into a trap message and sending it periodically or when a predetermined number of events is reached, rather than sending individual messages for each event, using a network management protocol like SNMP to reduce the load on the network management system.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If individual trap messages are sent for each event, then complete event reporting is achieved, but network congestion and processor overload occur
Solution Approach 1:
The patent combines multiple individual trap messages into a single bulk trap message that contains event information for multiple events. This merging approach maintains complete event reporting while reducing the total number of messages transmitted, thereby eliminating network congestion and processor overload caused by individual trap messages.
Solution Approach 2:
The patent creates a consolidated copy of event information from multiple individual events into a single bulk trap message structure. This copying mechanism preserves all event data while transmitting it in an aggregated format, achieving both complete reporting and reduced message volume.
2Loss of information
If multiple trap messages are sent for catastrophic failures, then all failures are reported, but the network management system becomes overloaded
Solution Approach 1:
The patent merges information from multiple failure events into a single bulk trap message, ensuring all failure information is reported while preventing the network management system from becoming overloaded with individual trap messages.
Solution Approach 2:
The patent implements periodic bulk trap messages that aggregate failure information over time intervals, allowing the network management system to process information in manageable batches rather than being overwhelmed by continuous individual trap messages.
3Measurement precision
If individual trap messages are sent for configuration changes, then detailed monitoring is achieved, but network bandwidth is consumed
Solution Approach 1:
The patent combines configuration change events into bulk trap messages that maintain detailed monitoring capability while significantly reducing the volume of network traffic compared to individual trap messages for each configuration change.
Data Source
AI summary
A method for reporting events relating to objects of a network element manageable by a network management device, using a network management protocol, and devices, a network, and computer-readable storage medium storing control logic, that operate in accordance with the method. Events for each object are detected, event information is generated for detected events, generated event information for multiple events is packaged into a trap message for each object type, the trap message is communicated from the network element to the network management device, and the event information from the communicated trap message is unpacked at the network management device. In this manner, network congestion and processor overload at the network management device can be reduced.