Multicast Tree Path Tracing With Upstream and Downstream Visibility
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current multicast tree path tracing techniques are directionally limited, primarily upstream tracing only, and lack a deterministic mechanism to visualize the entire multicast tree from any part of the network, making it difficult to troubleshoot and maintain high service performance in complex web service infrastructure.
Innovation Solution
A device, acting as a mid-node in the multicast tree, performs both upstream and downstream traces to generate an end-to-end visible topology of the multicast tree, enabling visualization from any network point.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If upstream tracing only is used, then the tracing mechanism is simple to implement, but the ability to visualize the entire multicast tree from any part of the network is lost
Solution Approach 1:
The tracing mechanism is segmented into two independent directional traces: upstream trace (from node to source) and downstream trace (from node to receivers). Each trace operates independently with its own packet forwarding and processing logic, allowing the system to achieve comprehensive visualization capability by combining results from both segments without requiring a single complex bidirectional mechanism
2Adaptability or versatility
If bidirectional tracing is implemented, then comprehensive visualization of the multicast tree is achieved, but the packet processing complexity increases
Solution Approach 1:
Different packet processing behaviors are applied locally based on node type: source nodes perform only upstream tracing, receiver nodes perform only downstream tracing, and intermediate nodes perform both upstream and downstream tracing. This local differentiation allows comprehensive topology visualization while keeping individual node processing simple and targeted
3Ease of operation
If receiver-to-source tracing begins at LHR, then the tracing can be initiated from receivers, but the tracing cannot be performed from arbitrary mid-nodes in the network
Solution Approach 1:
The tracing mechanism is designed to be universally applicable to any node type in the multicast tree. Any node (source, intermediate, or receiver) can initiate a trace by performing appropriate upstream and/or downstream traces based on its position in the tree, making the system globally applicable rather than limited to specific node types or locations
Data Source
AI summary
In one embodiment, a device may receive a multicast path trace request for a multicast tree, wherein the device is a mid-node in the multicast tree. The device may perform, based on the device being a mid-node in the multicast tree, an upstream trace of network topology of the multicast tree from the device to a head-node of the multicast tree and a downstream trace of network topology of the multicast tree from the device to at least one tail-node. The device may generate an end-to-end visible topology of the multicast tree based on the upstream trace and the downstream trace. The device may provide the end-to-end visible topology of the multicast tree to an observability manager.