Dynamic Routing Protocol Modifications for Virtual Router Traffic Optimization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In network topologies using dynamic routing protocols like OSPF and IS-IS with VRRP/MC-LAG clusters, data traffic often unnecessarily traverses inter-chassis links, leading to congestion, traffic loss, and increased latency due to inefficient forwarding paths.
Innovation Solution
Implementing MAC synchronization within VRRP/MC-LAG clusters to synchronize client-facing interface MAC addresses and using modified dynamic routing protocols to advertise virtual IP addresses, allowing nodes to perform local L3 routing and avoid unnecessary inter-chassis link forwarding.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If dynamic routing protocols are used with VRRP/MC-LAG clusters, then routing flexibility and adaptability are improved, but traffic forwarding efficiency deteriorates due to unnecessary inter-chassis link traversal
Solution Approach 1:
The patent pre-configures MAC address synchronization between cluster nodes before traffic arrives. Each node learns and synchronizes the MAC addresses of client-facing interfaces of other nodes in advance, so when traffic is forwarded, nodes can immediately perform local L3 routing without needing to query or forward through inter-chassis links, thus resolving the efficiency problem while maintaining routing flexibility
Solution Approach 2:
The patent segments the forwarding decision process into two independent parts: MAC address learning/synchronization (control plane) and traffic forwarding (data plane). By separating these functions, the system can maintain flexible dynamic routing in the control plane while achieving efficient direct forwarding in the data plane through pre-synchronized MAC address tables
2Measurement precision
If individual interface IP addresses are advertised via dynamic routing protocols, then routing precision and path selection are improved, but traffic flow optimization deteriorates due to equal cost path selection
Solution Approach 1:
The patent introduces asymmetry in the routing information by advertising the virtual IP address of the cluster as a single next-hop address instead of symmetrically advertising all individual interface IP addresses. This asymmetric approach allows the routing protocol to maintain precise path selection capability while the cluster internally optimizes traffic flow by directing all traffic to the receiving node that can then perform local L3 routing, avoiding equal cost path selection issues
3Measurement precision
If nodes forward traffic based on learned interface IP addresses, then routing accuracy is improved, but unnecessary inter-chassis link traversal occurs
Solution Approach 1:
The patent introduces MAC address synchronization as an intermediary mechanism between routing information and traffic forwarding. Instead of directly using learned interface IP addresses for forwarding decisions, nodes use the synchronized MAC address tables to determine the receiving node identity first, then perform local L3 routing. This intermediary step ensures routing accuracy while eliminating unnecessary inter-chassis link traversal and reducing latency
Data Source
AI summary
Techniques for optimizing traffic flows via dynamic routing protocol (DRP) modifications when server virtualization is used with dynamic routing are provided. In one embodiment, a network device can determine that it is part of a system of network devices acting as a virtual router. The network device can then transmit, to a client device, a DRP control packet that includes an interface IP address of the network device and a virtual IP address of the virtual router. In a further embodiment, the client device can receive the DRP control packet and store the interface IP address and the virtual IP address in a routing database. At the time of computing routing entries based on the routing database, the client device can replace, in entries that identify the interface IP address as the next hop, the interface IP address with the virtual IP address.


