Segment Routing Header Encapsulation for Error Telemetry
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current computer networking technologies lack granular telemetry information for network operations, particularly for node-to-node communications, as typical ICMP messages are not included in standard telemetry data, limiting network administrators' ability to diagnose and correct issues effectively.
Innovation Solution
The implementation of a method using a Segment Routing Header (SRH) to encapsulate error messages and send them to a remote telemetry server, providing detailed error reporting by leveraging metadata capabilities, such as Type-Value-Length fields in SRv6 and Network Service Header in SFC, to offer a holistic view of network errors.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If ICMP messages are collected using traditional error counters or Netflow, then basic error information is obtained, but granular telemetry information for complete network operation characterization is lost
Solution Approach 1:
The patent introduces a telemetry server as an intermediary component that collects ICMP messages from transit nodes. This mediator captures error messages that would otherwise be lost, providing granular telemetry information without requiring complex changes to existing network devices. The telemetry server acts as a centralized collection point that aggregates error data from multiple sources.
Solution Approach 2:
The system performs preliminary actions by configuring transit nodes to capture and forward ICMP messages before they are discarded. By setting up error counters and Netflow collection in advance, and by pre-configuring the telemetry server to receive and process these messages, the system ensures that telemetry data is captured at the source before information loss occurs.
2Measurement precision
If detailed error telemetry is collected from all transit nodes, then complete network operation visibility is achieved, but system complexity and resource requirements increase
Solution Approach 1:
The telemetry server serves as a centralized intermediary that consolidates the complexity of detailed error telemetry collection. Instead of requiring each transit node to independently perform complex telemetry functions, the server centralizes data aggregation, processing, and analysis, thereby achieving high measurement precision without proportionally increasing device complexity at each node.
Solution Approach 2:
The telemetry server performs multiple functions including collecting ICMP messages from various transit nodes, storing error telemetry data, analyzing network operations, and providing visibility into complete network behavior. This multi-functional approach achieves comprehensive measurement precision through a single versatile system rather than multiple specialized components.
3Loss of information
If ICMP error messages are sent directly to source addresses, then error notification is provided, but network operators cannot obtain a full view of error exchanges between nodes
Solution Approach 1:
The telemetry server acts as an intermediary that intercepts ICMP error messages before they are sent to source addresses. By capturing these messages at the transit node level and forwarding them to the centralized server, the system provides network operators with a comprehensive view of error exchanges while simplifying the routing process through automated collection rather than manual configuration.
Solution Approach 2:
The system implements feedback by collecting ICMP error messages and making them available to network operators through the telemetry server. This feedback loop provides continuous visibility into network error conditions, allowing operators to monitor and analyze error exchanges between nodes without interfering with the normal error message delivery process.
Data Source
AI summary
A network device receives a data packet including a source address and a destination address. The network device drops the data packet before it reaches the destination address and generates an error message indicating that the data packet has been dropped. The network device encapsulates the error message with a segment routing header comprising a list of segments. The first segment of the list of segments in the segment routing header identifies a remote server, and at least one additional segment is an instruction for handling the error message. The network device sends the encapsulated error message to the remote server based on the first segment of the segment routing header.