Leaf Isolation in E-Tree Networks via TPID Tag Control Information
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Implementing leaf isolation rules in a multi-node Ethernet virtual circuit system with aggregated switches is cumbersome and complex, as switches need to know the leaf status of ports on other switches, leading to increased forwarding table entries and potential network congestion issues when modifying the CFI/DEI bit for leaf indication.
Innovation Solution
Modifying the TPID field in the Ethernet packet header to indicate the leaf status of the ingress port, allowing nodes to enforce leaf isolation rules without affecting downstream components by ensuring the TPID field is restored to its original state upon egress.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the CFI/DEI bit is modified to indicate leaf status, then leaf isolation rules can be enforced in aggregated switch environments, but downstream components lose the ability to use the CFI/DEI bit for congestion dropping decisions
Solution Approach 1:
The patent divides the packet header into different functional segments: the VLAN tag contains the leaf status indicator (derived from TCI bits), while the original CFI/DEI bit is preserved in the Ethernet header for downstream congestion control. This segmentation allows both functions to coexist without interference.
Solution Approach 2:
The patent introduces the TCI (Tag Control Information) bits as an intermediary mechanism to convey leaf status information. These bits act as a mediator that enables leaf isolation enforcement without directly modifying the CFI/DEI bit, thus preserving its original functionality for downstream components.
2Reliability
If switches provision information about leaf status of ports on other switches, then leaf isolation rules can be enforced in multi-node networks, but the design and provisioning becomes burdensome and complicated
Solution Approach 1:
Each switch autonomously determines its own leaf status based on the TCI bits in incoming packets and independently enforces leaf isolation rules. This self-service approach eliminates the need for centralized provisioning of leaf status information across multiple switches, significantly reducing operational complexity.
Solution Approach 2:
The patent uses different values in the TCI bits (effectively different 'colors' or states) to indicate whether a port is a leaf port or root port. This visual differentiation mechanism allows switches to easily distinguish between port types without complex provisioning, enabling intuitive and simple operation.
3Reliability
If the number of entries in forwarding tables is increased to support leaf isolation, then leaf status information can be stored, but the forwarding tables become drastically increased for large numbers of aggregated switches
Solution Approach 1:
The patent merges the leaf status indication with the existing VLAN tag structure by using the TCI bits within the VLAN header. This consolidation eliminates the need for separate forwarding table entries to store leaf status information, as the status is already embedded in the packet header that switches process routinely.
Solution Approach 2:
The TCI bits serve multiple functions: they indicate leaf port status for isolation enforcement, and can be interpreted as part of the VLAN tagging mechanism. This multi-functionality reduces the need for dedicated forwarding table entries, as the same header fields serve both VLAN identification and leaf status indication purposes.
Data Source
AI summary
The present disclosure generally pertains to systems and methods for enabling leaf isolation in a multi-node tree network. In one exemplary embodiment, an Ethernet virtual network (EVC) system has a multi-node E-Tree network comprising a plurality of nodes (e.g., switches), including at least one ingress node and at least one egress node. The ingress node is configured to receive a data packet to be communicated through the E-Tree network and to modify a field, such as the tag protocol identifier (TPID), in the packet's header to indicate whether the data packet is received by the ingress node via a leaf port. As the data packet is communicated through the E-Tree network, the nodes determine the leaf status of the packet based on the modified field thereby enabling the nodes to enforce leaf isolation rules. The egress node upon receiving the packet is configured to adjust the modified field as appropriate such that the field on egress matches the field on ingress. Accordingly, the use of the field as a leaf indicator in the E-Tree network should not affect the ability of downstream components to properly handle the data packet.