Protocol Independent Multicasting in MLAG Domains
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In multilayer switch implementations, proprietary tags used for IP multicast packet management reduce interoperability and complicate network troubleshooting, especially in multichassis link aggregation (MLAG) domains where ensuring distinct delivery of IP multicast packets to different destinations is challenging.
Innovation Solution
Implementing tagless protocol-independent multicasting (PIM) in MLAG domains by using two separate IP multicast routers with independent routing tables, each maintaining its own forwarding and control protocol instances, and coordinating through a peer link to synchronize forwarding tables and manage packet delivery across the domain.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If proprietary tags are attached to IP multicast packets by multilayer switches, then multiple copies of IP multicast packets can be prevented from being delivered to the same destination, but interoperability between various switches decreases and network troubleshooting becomes difficult
Solution Approach 1:
The patent removes proprietary tags from the packet forwarding mechanism. Instead of attaching custom tags to multicast packets, the system uses standard VLAN tags that are already present in the network infrastructure. This extraction of the proprietary tagging mechanism eliminates the interoperability issues while maintaining reliable packet delivery through alternative means (peer link synchronization and forwarding table coordination).
Solution Approach 2:
The patent makes the MLAG domain universal by using standard VLAN tagging that is compatible with multiple switch vendors and network configurations. The system achieves multi-functionality by using the existing VLAN infrastructure for both unicast and multicast packet management, eliminating the need for proprietary tag structures and enabling broader interoperability across different network equipment.
2Reliability
If proprietary tags are used for IP multicast packet management, then packet delivery control is improved, but network troubleshooting complexity increases
Solution Approach 1:
The patent extracts the troubleshooting complexity by removing proprietary tags from the system. By using standard VLAN tags and peer link synchronization mechanisms, the packet delivery control functionality is maintained while the network becomes easier to troubleshoot using standard tools and protocols that network administrators are already familiar with.
Solution Approach 2:
The patent introduces the peer link as an intermediary mechanism for coordinating multicast packet delivery between MLAG peers. This peer link carries synchronization traffic that allows both switches to maintain consistent forwarding tables without requiring proprietary tags on data packets. The intermediary peer link separates the control plane communication from the data plane, making troubleshooting easier by isolating control mechanisms.
3Adaptability or versatility
If two separate IP multicast routers with independent routing tables are used in MLAG domains, then interoperability and troubleshooting are improved, but system complexity increases
Solution Approach 1:
The patent segments the multicast routing functionality into two independent IP multicast routers, each with its own routing table maintained on separate MLAG peers. This segmentation allows each router to operate independently with standard protocols, improving interoperability. The complexity is managed through the peer link that synchronizes forwarding tables, coordinating the segmented systems without requiring a single complex unified router.
Solution Approach 2:
The patent merges the functionality of two separate IP multicast routers into a single MLAG domain that appears as one logical switch to external devices. While the internal architecture uses two independent routing instances for interoperability, the peer link synchronizes their forwarding tables to present a unified behavior externally, combining the benefits of independent routing with the simplicity of a single switch from the network's perspective.
Data Source
Figure 1
Figure 2
Figure 3A
AI summary
A method for processing IP multicast packets in a MLAG domain. The method includes processing the IP multicast packet using the bridging functionality and the routing functionality implemented by each of the MLAG peers to process the IP multicast packets.