Controller-Based Broadcast Domain Segmentation in Switch Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Managing network switches from different vendors is challenging due to incompatibilities in operating systems and control protocols, leading to difficulties in centralized control and efficient packet forwarding, especially with broadcast packets that generate excessive network traffic.
Innovation Solution
A centralized or distributed controller server maintains information on broadcast domains, configures switches to forward broadcast packets to the controller, and uses flow table entries to direct switches to forward matching packets to the appropriate end hosts, thereby isolating broadcast domains and reducing unnecessary network traffic.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If broadcast network packets are flooded throughout the network to all end hosts, then all end hosts receive the broadcast packets, but excessive network traffic is generated
Solution Approach 1:
The network is segmented into multiple broadcast domains based on end host groupings. The controller divides the network into logical segments where broadcast packets are confined to specific domains rather than being flooded across the entire network. This segmentation allows broadcast coverage within domains while reducing overall network traffic.
Solution Approach 2:
Different regions of the network (broadcast domains) are given different forwarding characteristics. The controller applies local forwarding rules to each domain, allowing broadcast packets to be forwarded only to end hosts within the same domain rather than universally to all hosts. This local quality approach reduces unnecessary traffic while maintaining appropriate broadcast coverage.
2Adaptability or versatility
If a centralized controller is used to manage switches from different vendors, then cross-platform control is achieved, but controller complexity increases
Solution Approach 1:
The controller is designed with universal functionality to manage switches from multiple vendors through a single interface. It implements cross-platform protocols that enable it to communicate with and control diverse switch equipment uniformly. This multi-functionality allows the controller to handle different vendor protocols and formats without requiring separate control systems for each vendor.
Solution Approach 2:
The controller acts as an intermediary layer between the network administrator and the diverse switch equipment. It translates high-level control commands into vendor-specific instructions and aggregates status information from different switch types into a unified view. This intermediary role simplifies the complexity by providing a standardized interface while handling the underlying vendor-specific complexities.
3Productivity
If switches forward broadcast packets to all ports, then complete broadcast distribution is achieved, but switch load increases
Solution Approach 1:
The controller performs preliminary actions by pre-configuring flow table entries in switches that define broadcast domain boundaries and membership. Before broadcast packets arrive, the switches are already programmed with the information needed to forward packets only to appropriate domains. This preliminary configuration reduces the processing load during actual broadcast operations while maintaining efficient distribution.
Solution Approach 2:
Instead of forwarding broadcast packets to all ports (excessive action), the system uses partial forwarding only to ports within the same broadcast domain. The controller determines the appropriate subset of end hosts for each broadcast domain and configures switches to forward packets only to those specific ports. This partial action approach maintains necessary broadcast distribution while avoiding unnecessary traffic to unrelated hosts, thereby reducing switch processing load.
Data Source
AI summary
A network of switches that forwards network packets between end hosts may be controlled by a controller. The controller may maintain information that identifies subsets of the end hosts that are associated with respective broadcast domains. The controller may configure the switches in the network to identify broadcast network packets and to forward the broadcast network packets to the controller. The controller may identify which broadcast domain is associated with a received broadcast network packet based on information such as source information retrieved from the broadcast network packet. The controller may identify switches that are coupled to the end hosts of a broadcast domain associated with the received broadcast network packet. The controller may forward the broadcast network packet to the identified switches through network control paths and may direct the identified switches to forward the broadcast network packet to end hosts of the associated broadcast domain.