Distributed Switch Multicast Table Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Distributed switches face inefficiencies in forwarding multicast data due to lack of multicast membership information, leading to bandwidth wastage and security risks through flooding, as they default to broadcasting when information is unavailable.
Innovation Solution
A method and apparatus for managing a global forwarding table in a distributed switch, which includes starting a timer for multicast destination addresses, checking hit status to determine if forwarding units have sent data, and determining if entries are cast-out candidates based on this status, thereby expediting learning of current membership information and reducing flooding.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the distributed switch floods multicast packets to all hosts when multicast membership information is unavailable, then all hosts receive the multicast packet ensuring delivery, but bandwidth is wasted and security risks increase due to transmission to unintended hosts
Solution Approach 1:
The system performs preliminary actions by starting a timer when an entry is added to the global forwarding table, and proactively checking hit status before flooding occurs. This allows the system to determine whether forwarding units have successfully delivered multicast data before resorting to flooding, thereby avoiding unnecessary bandwidth consumption while ensuring reliable delivery when needed
Solution Approach 2:
The system implements feedback mechanisms by checking hit status from forwarding units to determine whether multicast data was successfully delivered. This feedback information is used to decide whether to flood packets or allow entries to be cast out, creating a closed-loop control system that adapts to actual network conditions and avoids both over-flooding and under-delivery
2Reliability
If the distributed switch floods multicast packets to all hosts, then delivery to intended hosts is ensured, but security risks increase due to transmission to unintended hosts
Solution Approach 1:
The system performs preliminary verification by checking hit status before flooding multicast packets. This preliminary action determines whether forwarding units have successfully delivered data to intended hosts, preventing security risks by avoiding transmission to unintended hosts while still ensuring delivery to legitimate recipients
Solution Approach 2:
The system uses feedback from hit status checks to make intelligent forwarding decisions. When hit status indicates successful delivery, flooding is avoided thereby preventing security exposures. When hit status shows failure, targeted flooding is performed only when necessary, minimizing security risks while maintaining delivery assurance
3Measurement precision
If the distributed switch maintains multicast membership information in the global forwarding table, then accurate multicast forwarding is achieved, but system resources are consumed storing and managing the table
Solution Approach 1:
The system applies dynamics by implementing time-based expiration and hit status-based retention in the global forwarding table. Entries are not permanently stored but are dynamically maintained based on timer expiration and whether they have been hit. This dynamic approach allows accurate forwarding when needed while automatically removing stale entries to conserve memory resources
Solution Approach 2:
The system discards stale multicast membership information from the global forwarding table when timer expiration occurs and hit status indicates no recent forwarding activity. This discarding of unnecessary data recovers memory resources while maintaining forwarding accuracy for active multicast groups that are regularly used
4Measurement precision
If the distributed switch checks hit status for all forwarding units when timer expires, then accurate determination of cast-out candidates is achieved, but processing time increases
Solution Approach 1:
The system performs partial checking of hit status rather than exhaustive checking of all forwarding units. By checking only relevant forwarding units or using sampling approaches, the system achieves sufficient accuracy in determining cast-out candidates while significantly reducing processing time compared to checking every single forwarding unit
Data Source
AI summary
Apparatuses and methods to manage a global forwarding table in a distributed switch are provided. A particular method may include managing a global forwarding table in a distributed switch. The distributed switch may include a plurality of switch forwarding units. The method may start a timer for an entry in the global forwarding table, and the entry may include a multicast destination address and corresponding multicast membership information. The method may also, in response to expiration of the timer of the entry, check at least one hit status to determine whether at least one switch forwarding unit of the plurality of switch forwarding units has forwarded multicast data to the corresponding multicast membership information of the multicast destination address of the entry. The method may further determine whether the entry is a cast-out candidate based on the hit status.