BGP sFlow Export via Separate Metadata Tables
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Retrieving up-to-date BGP metadata for BGP routes is computationally intensive and requires significant CPU and memory resources due to constant network route updates and redundancy in BGP information, making efficient management of network resources challenging.
Innovation Solution
The solution involves generating separate tables for BGP attribute information, community list information, and autonomous systems path (AS_PATH) attribute information, and populating a BGP route information table to facilitate efficient export of BGP data in sFlow samples, minimizing redundancy and resource consumption by using a partial copy of hash tables managed by the routing agent.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If BGP metadata is stored and retrieved for each routing update, then complete routing information is available, but CPU and memory resources are excessively consumed
Solution Approach 1:
The patent creates a simplified copy of the BGP routing table that contains only the essential fields needed for sFlow sampling (source/destination IP addresses, next-hop address, and AS_PATH). This copy is maintained separately from the full BGP routing table, allowing fast retrieval without accessing the complete routing information. The copy is updated incrementally when routing changes occur, reducing the computational overhead of maintaining and searching the full BGP metadata while still providing the necessary information for network traffic analysis.
2Loss of information
If full BGP routing tables are maintained for accurate route tracking, then routing path visibility is complete, but memory resources are excessively consumed
Solution Approach 1:
The patent extracts only the essential routing information needed for sFlow sampling from the complete BGP routing table. Specifically, it extracts source IP address, destination IP address, next-hop address, and AS_PATH attributes, while discarding or deferring access to less critical BGP attributes. This extraction creates a streamlined data structure that maintains the essential routing path visibility required for network monitoring while occupying minimal memory resources.
3Measurement precision
If BGP metadata is retrieved for every sFlow sample, then accurate routing information is provided, but processing time increases
Solution Approach 1:
The patent performs preliminary actions by pre-processing and organizing BGP routing information into a simplified lookup table structure before sFlow sampling occurs. The essential routing fields (IP addresses, next-hop, AS_PATH) are pre-extracted and stored in an optimized format that enables rapid retrieval. When sFlow samples need routing information, the system can quickly match the sample's IP addresses against the pre-organized table without performing complex BGP attribute retrieval or parsing operations at sampling time, thus maintaining accuracy while minimizing processing delay.
Data Source
AI summary
A method and apparatus of a device that exports Border Gateway Protocol (BGP) data in sFlow samples. The device generates separate tables for BGP attribute information, community list information, and autonomous systems path (AS_PATH) attribute information, where each entry in the BGP attribute information table is associated with an entry in the community list information table and an entry in the AS_PATH attribute information table. The device further populates a BGP route information table that defines a mapping from a network address prefix to an entry in the BGP attribute information table. The device generates a sFlow sample related to the network address prefix using the BGP attribute information table, the community list information table, the AS_PATH attribute information table, and the BGP route information table.