Multicast Reprogramming via Real-Time Buffer Feedback
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Egress replication buffering in network elements can lead to congestion and packet loss during multicast transmissions due to limited resources and traffic bursts, as it requires replicating packets at the ingress buffer, causing inefficiencies and hindering unicast traffic.
Innovation Solution
A network element is configured to monitor egress buffers in real-time for errors and selectively switch to ingress replication buffering, using virtual output queues to manage multicast traffic, thereby optimizing the use of limited resources and reducing packet loss.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of energy
If egress replication buffering is used for multicast traffic, then memory and bandwidth use is minimized, but packet loss increases during buffer overflow
Solution Approach 1:
The system dynamically switches between egress replication buffering and ingress replication buffering modes based on real-time buffer status. When egress buffers are full, the system transitions to ingress replication buffering to prevent packet loss, and switches back to egress replication when buffers are available, optimizing both resource efficiency and reliability
Solution Approach 2:
The system implements real-time monitoring of egress buffer status with feedback mechanisms that trigger mode switching. Buffer status information is continuously monitored and fed back to the control logic, which automatically adjusts the replication buffering mode to prevent overflow while minimizing resource consumption
2Reliability
If ingress replication buffering is used for multicast traffic, then packet loss is reduced during congestion, but unicast traffic is hindered
Solution Approach 1:
The system applies different buffering strategies to different traffic types locally. Multicast traffic uses ingress replication buffering when egress buffers are full to prevent loss, while unicast traffic continues to use standard egress buffering, ensuring each traffic type receives appropriate handling without interfering with the other
Solution Approach 2:
The buffering mode is dynamically selected based on traffic type and buffer status. Ingress replication buffering is activated only for multicast traffic during congestion conditions, while unicast traffic maintains its normal flow path, preventing hindrance to unicast performance
3Loss of energy
If egress replication buffering is used, then fabric bandwidth is reduced, but egress buffers fill up quickly during traffic bursts
Solution Approach 1:
The system performs preliminary replication of multicast packets at the ingress buffer before they reach the egress buffer when congestion is detected. This preliminary action prevents the egress buffer from filling up during traffic bursts, while still allowing efficient fabric utilization during normal conditions
Data Source
AI summary
Methods and systems are described for programming a substitution of ingress replication buffering for egress replication buffering after identifying egress buffer errors (such as overflow) for multicast traffic. A network element is configured to identify which ports drop packets by monitoring egress buffers and/or multicast traffic in real time. A hardware forwarding engine provides feedback to a control plane processor of the network element to adapt and selectively reprogram multicast ingress replication, temporarily, for certain egress ports that may have, e.g., egress buffer errors or risk of issues due to high network traffic. Using virtual output queues in ingress buffers may reduce risk of egress port congestion, as egress buffers have more limited resources than ingress buffers; however, relying solely on ingress replication for multicast traffic may hinder unicast traffic. Ingress buffer replication of multicast traffic may be used selectively and temporarily.