Virtual Chassis System for Network Resiliency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Data networks face challenges in maintaining high availability and network resiliency due to difficulties in upgrading or transitioning between different node architectures and topologies, which hinders seamless traffic routing and bandwidth efficiency.
Innovation Solution
A virtual chassis system is implemented, where network nodes operate as a single logical device with unified management, using virtual fabric links for communication and load balancing, allowing for seamless transition between node architectures and topologies while maintaining network resiliency through a master node and synchronized MAC address tables.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If network nodes use different node architectures and topologies to provide redundancy, then network resiliency is improved, but device complexity increases and transition between architectures becomes difficult
Solution Approach 1:
Multiple network nodes with different architectures (single switching elements, stackable switching elements, multi-slot chassis based network elements) are merged into a unified virtual chassis that operates as a single logical device. The virtual chassis manager coordinates control plane protocols across heterogeneous nodes, while the data plane maintains unified forwarding behavior, effectively hiding architectural diversity from external observers while preserving redundancy benefits.
Solution Approach 2:
The virtual chassis system provides universal functionality across different node architectures by implementing a common virtual chassis interface and control plane protocol. This allows nodes of varying physical architectures to perform identical logical functions within the virtual chassis, enabling seamless transition and migration between different hardware platforms while maintaining network resiliency.
2Reliability
If multiple physical paths are provided between nodes for redundancy, then network resiliency is improved, but convergence time increases due to topology complexity
Solution Approach 1:
The control plane is segmented into distributed control elements that operate autonomously at each node, while the data plane maintains unified forwarding decisions. This segmentation allows parallel processing of convergence decisions across multiple paths without requiring centralized coordination, reducing convergence time while maintaining the redundancy benefits of multiple physical paths.
Solution Approach 2:
The virtual chassis pre-establishes redundant forwarding paths and maintains topology information in advance through continuous control plane communication. When failures occur, pre-computed alternate paths are immediately activated without requiring full topology re-convergence, significantly reducing failure detection and recovery time while maintaining network resiliency.
3Productivity
If network nodes are configured for specific topologies, then traffic routing is optimized, but adaptability to topology changes and upgrades is reduced
Solution Approach 1:
The virtual chassis implements dynamic configuration capabilities that allow real-time adjustment of topology parameters and node roles without disrupting traffic forwarding. The control plane protocols enable live migration of control functions between nodes and adaptation to changing physical topologies, maintaining optimized routing efficiency while providing flexibility for upgrades and reconfiguration.
Solution Approach 2:
The system enables parameter changes in topology configuration and node architecture without requiring physical reconfiguration. Virtual chassis parameters such as node roles, forwarding paths, and control plane protocols can be dynamically adjusted through software control, allowing efficient traffic routing to be maintained while adapting to topology changes, upgrades, or failures.
Data Source
AI summary
A virtual chassis system includes a plurality of network nodes configured with a master virtual chassis address. The network nodes are connected by virtual fabric link (VFLs) that provide a connection for exchange of packets between the network nodes. The packets include source MAC addresses and associated hardware device information, such as source chassis ID, source network interface identifier and source port identifier information. The network nodes use this information to maintain synchronized MAC address tables for forwarding of packets in the virtual chassis system.


