Stack Address Retention During Master Failover
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In stack switch systems, frequent primary master to secondary master failovers lead to changes in stack addresses, causing disruptions, increased latency, and burdensome recalculation of protocols like spanning trees and link aggregations, impacting network performance and requiring updates in ARP and routing tables.
Innovation Solution
A system that allows stack switches to retain their stack address during multiple failovers by using a stack manager to elect primary and secondary masters and determine when to replace the stack address based on restart times, minimizing protocol recalculation and table updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the stack address changes to reflect the MAC address of the new primary master during failover, then the system maintains accurate address representation, but network latency increases and ARP tables and routing tables must be updated
Solution Approach 1:
The system pre-assigns a stable stack address to the secondary master before failover occurs. When the primary master fails, the secondary master can immediately assume the pre-assigned stack address without requiring address changes or network table updates, thus preventing latency while maintaining address accuracy
2Reliability
If the stack address changes during primary master failover, then the new primary master's identity is reflected accurately, but protocol recalculation (spanning tree, link aggregation) becomes burdensome
Solution Approach 1:
The stack manager pre-configures the stack address assignment for the secondary master in advance. Upon failover, the secondary master already has the stack address assigned, eliminating the need for spanning tree recalculation and link aggregation recomputation, thus maintaining identity representation while reducing protocol complexity
3Stability of the object's composition
If the stack address is retained during failover, then network stability improves and ARP tables remain unchanged, but the stack address no longer reflects the current primary master's MAC address
Solution Approach 1:
The patent introduces an intermediary mapping mechanism where the stack address is decoupled from the primary master's MAC address. The stack manager acts as a mediator that maintains the stable stack address while internally managing the relationship between the stack address and the current primary master, thus preserving network stability without losing address correspondence information
Data Source
AI summary
The present invention features embodiments of alleviating the impact to a system of stack switches, as well as to neighboring nodes communicating with such a system, when a primary master switch to secondary master switch failover occurs. The features of the present invention, generally enables a system of stack switches to retain, for a fixed or indefinite period of time, its stack address even when multiple primary master to secondary master failovers occur. This way recalculation of certain protocols—e.g., spanning trees and link aggregations—and updating of certain tables—e.g., address resolution protocol (ARP) and routing tables—are minimized.