In-band Telemetry Packet Header Embedding for Multi-Tenant Scalability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In multi-tenant networks, centralized telemetry data collection is inefficient due to dependency on network administrators, irrelevant data collection, and scalability challenges with per-flow or per-tenant collector approaches, which require extensive hardware resources and manual configuration.
Innovation Solution
Implementing a designated collector for each tenant or flow, where the INT source embeds the packet header with the collector IP address and instructions, allowing network elements to send telemetry data directly to the designated collector without manual configuration, thus eliminating the need for per-flow or per-tenant IP address configuration and reducing resource usage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a centralized collector is used to collect telemetry data in multi-tenant networks, then data collection is simplified and centralized control is maintained, but tenants have no visibility into their specific network metrics and must depend on network administrators, resulting in inefficient troubleshooting
Solution Approach 1:
The patent segments the centralized collector into multiple distributed collectors, each responsible for specific tenants or flows. This segmentation allows tenants to have dedicated collectors that capture their specific telemetry data while maintaining the benefits of automated collection. The segmentation resolves the contradiction by providing tenant-specific visibility without requiring manual administrator intervention.
Solution Approach 2:
The patent implements self-service capabilities where tenants can autonomously configure and manage their own telemetry collection through programmable network interfaces. The distributed collectors automatically identify and collect relevant tenant data without requiring network administrator configuration. This self-service approach eliminates the dependency on administrators while maintaining ease of operation through automated processes.
2Device complexity
If traditional centralized methods are used for telemetry collection, then infrastructure control is simplified, but irrelevant or non-specific telemetry data is collected that is not useful to tenants for troubleshooting their specific application performance issues
Solution Approach 1:
The patent applies local quality by deploying distributed collectors that are locally positioned near specific tenants or flows. Each collector is optimized to collect only the telemetry data relevant to its assigned tenant or flow, providing precise, localized measurement capabilities. This resolves the contradiction by maintaining simple infrastructure control through standardized collector designs while achieving high measurement precision for tenant-specific metrics.
Solution Approach 2:
The patent introduces dynamic configuration capabilities where collectors can adapt their data collection behavior based on real-time network conditions and tenant requirements. The system dynamically adjusts which metrics are collected and how frequently, allowing precise measurement of tenant-specific issues while maintaining efficient resource utilization. This dynamic approach enables accurate tenant-specific measurements without the overhead of collecting all possible metrics continuously.
3Loss of information
If per-flow or per-tenant collector approach is used to provide tenant-specific telemetry data, then relevant telemetry data can be collected, but scalability challenges arise as the number of collectors must be commensurate with the scale of the network, requiring extensive hardware resources
Solution Approach 1:
The patent implements universal collectors that can serve multiple tenants and flows simultaneously through programmable interfaces. Each collector is designed with multi-functionality, capable of dynamically configuring itself to collect telemetry for different tenants based on packet headers and flow identification. This universality reduces the total number of collectors needed while maintaining tenant-specific data collection, resolving the scalability contradiction.
Solution Approach 2:
The patent merges multiple collection functions into single distributed collectors that can handle multiple tenants and flows. By combining what would traditionally require separate collectors for each tenant into shared, multi-tenant collectors, the system reduces hardware resources and device complexity while maintaining the ability to collect tenant-specific telemetry data through software-based configuration and isolation.
4Extent of automation
If per-flow or per-tenant collectors are deployed to collect specific telemetry data, then autonomous data collection is enabled, but manual configuration of each network element is required to allow reporting of telemetry and optimize hardware resources like TCAM
Solution Approach 1:
The patent implements self-service capabilities where distributed collectors automatically identify themselves and configure network elements for telemetry collection. The collectors use programmable interfaces to autonomously program network elements with the necessary flow identification and data collection instructions, eliminating manual configuration requirements. This maintains high automation while simplifying deployment.
Solution Approach 2:
The patent applies preliminary action by pre-configuring collectors with the capability to automatically program network elements upon deployment. The collectors are designed with built-in configuration templates and automated programming logic that enables them to quickly set up telemetry collection on network elements without requiring manual administrator intervention. This preliminary preparation maintains automation while reducing the complexity of initial system setup.
Data Source
AI summary
Systems and methods for INT telemetry are disclosed. The system selects a subset of flows from a plurality of flows to monitor. Parameters of the selected flows are sent by the management controller to an INT source for creating a watchlist. The INT source analyses an incoming packet against the parameters in the watchlist to determine if the packet belongs to a flow selected for monitoring. If the packet matches any one of the parameters, then the INT source embeds the packet with an IP address of a designated tenant collector and the INT instructions. A designated collector is allocated for each flow, set of flows, or tenant. Regardless of the path taken by the packet, the embedded INT packet contains all the information needed for a downstream network element to send telemetry data without the need for configuring the network element for telemetry.


