VLAN Traffic Load Balancing via Master-Backup Core Designation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing network systems face inefficiencies in load balancing VLAN traffic, leading to excessive bandwidth waste and increased complexity due to distributed accounting and policing functions, as well as inefficient routing protocols.
Innovation Solution
A centralized approach where core devices are designated as master or back-up devices for virtual group identifiers, allowing for efficient routing and policing of VLAN traffic without increasing the number of routing table entries, by using a first core device to receive signals designating it as a master device and a second core device as a back-up, thereby directing data units accordingly.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If ECMP routing is used to send VLAN traffic to all core devices, then VLAN traffic can be distributed across multiple paths, but inter-core links waste bandwidth and core device ports are excessively occupied
Solution Approach 1:
The patent extracts the VLAN traffic handling function from the distributed core devices and concentrates it at the access node. The access node performs local routing decisions and forwards VLAN traffic directly to the destination without sending traffic through inter-core links, thereby eliminating bandwidth waste on those links while maintaining traffic distribution capability.
Solution Approach 2:
The access node acts as an intermediary between external networks and the VLAN devices. It receives VLAN traffic, makes routing decisions based on virtual routing table entries, and forwards traffic directly to destination devices within the VLAN, eliminating the need for traffic to traverse core devices and inter-core links.
2Productivity
If host-routing solution is implemented for core devices to advertise host-specific routes, then VLAN traffic routing can be optimized, but the number of routing table entries increases significantly
Solution Approach 1:
The patent segments the routing function by separating virtual routing table entries maintained at core devices from the actual routing decisions made at access nodes. Core devices only maintain aggregate VLAN route entries rather than individual host routes, while access nodes perform detailed routing based on virtual routing tables that are populated through control plane interactions.
Solution Approach 2:
The access node serves as an intermediary that maintains virtual routing tables for VLAN traffic, allowing detailed host-specific routing information to be stored locally at the access node rather than in core device routing tables. This reduces core device routing table complexity while enabling efficient host-specific routing.
3Reliability
If accounting and policing functions are implemented in a distributed fashion at multiple core devices, then VLAN traffic can be monitored, but the complexity of core devices increases and VLAN traffic management becomes difficult
Solution Approach 1:
The patent extracts accounting and policing functions from core devices and relocates them to access nodes. Access nodes perform local accounting and policing for VLAN traffic, reducing the functional complexity of core devices while maintaining comprehensive VLAN traffic monitoring capability through distributed enforcement at the network edge.
Data Source
AI summary
In some embodiments, an apparatus includes a first core device configured to be disposed within a network. The network has a set of access nodes and a second core device. The first core device is configured to receive a signal designating the first core device as a master device for a virtual group identifier such that the second core device is designated as a back-up device for that virtual group identifier.