Switch Fabric VLAN Scalability via Extended Identifiers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing switch fabric systems are limited in the number of virtual local area networks (VLANs) they can support, as they either adhere to existing standards or impractically modify them to increase capacity, failing to scale with the size of the system.
Innovation Solution
A switch module that receives multicast data units with VLAN identifiers, selects appropriate port modules, and sends unmodified instances to each module, where filters restrict data transmission based on VLAN domains, allowing for increased VLAN support without altering existing standards.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If existing standards (IEEE 802.1Q) are used to assign VLAN identifiers, then compatibility with existing systems is maintained, but the number of supported VLANs is limited to the same capacity as a single switch
Solution Approach 1:
The system segments VLAN management into two parts: standard 12-bit VLAN identifiers (1-4094) for compatibility, and an extended VLAN identifier (EVID) for additional capacity. The switch fabric maintains separate tables (flood table for standard VLANs, filter table for EVIDs) to handle different identifier types, allowing scalable VLAN support without breaking existing standards.
Solution Approach 2:
The patent adds a new dimension to VLAN identification by introducing extended VLAN identifiers (EVIDs) that go beyond the traditional 12-bit limit. This creates a two-layer identification system where standard VLAN IDs operate within the conventional space while EVIDs extend into additional address space, enabling the switch fabric to support millions of VLANs without interfering with existing IEEE 802.1Q operations.
2Adaptability or versatility
If more bits in the data unit header are used to specify more VLAN identifiers, then the number of supported VLANs increases, but the existing standard must be changed which is heavily in use
Solution Approach 1:
The system introduces an intermediary mechanism where the switch fabric internally handles extended VLAN identifiers while presenting standard-compliant behavior to external systems. The fabric uses private communication channels and internal table lookups to process EVIDs without requiring changes to the public IEEE 802.1Q standard, thus mediating between the need for extended capacity and standard compatibility.
Solution Approach 2:
The patent creates copies of VLAN identification functionality at different levels: standard VLAN ID handling copies the existing IEEE 802.1Q behavior for compatibility, while EVID handling copies the identification function in an extended form. This allows the system to support both standard and extended VLANs simultaneously without requiring all systems to adopt the extended format.
3Productivity
If VLAN identifiers are extended beyond standard limits, then scalability of the switch fabric system improves, but filters must be applied at multiple stages to restrict data transmission across VLAN domains
Solution Approach 1:
The system performs preliminary filtering by creating domain-specific filter tables that pre-establish which extended VLAN identifiers belong to which VLAN domains. This preliminary organization allows the fabric to efficiently enforce domain boundaries without requiring complex real-time analysis of each data unit, as the filtering rules are prepared in advance based on the EVID-to-domain mappings.
Solution Approach 2:
The patent introduces filter tables as intermediary structures that mediate between extended VLAN identifiers and VLAN domain boundaries. These tables act as lookup mechanisms that translate EVIDs into domain information, enabling the fabric to enforce domain restrictions without direct complex comparisons. The intermediary filter tables simplify the filtering operation while maintaining scalability.
Data Source
AI summary
In some embodiments, a switch module is configured to receive from a first edge device a multicast data unit having a VLAN identifier. The switch module is configured to select a set of port modules based on the VLAN identifier. The switch module is configured to define an unmodified instance of the multicast data unit for each port module from the set of port modules. The switch module is configured to send the unmodified instance of the multicast data unit to each port module from the set of port modules, such that each port module applies a filter to the received instance of the multicast data unit to restrict that received instance of the multicast data unit from being sent to a second edge device via that port module if the second edge device is associated with a VLAN domain different than a VLAN domain of the first edge device.