Ethernet Ring Protection Switching Design for Dual Hub Spoke Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing Ethernet ring protection switching methods, such as G.8032, face challenges in efficiently configuring networks to avoid logical loops and ensure reliable operation, particularly in dual hub and spoke designs where a single common node can be a point of failure, impacting network performance and resilience.
Innovation Solution
A method is introduced that identifies core nodes and virtual nodes, creates virtual links, and configures sub-rings to provide diverse paths, ensuring network connectivity and minimizing hops and sub-rings, while adhering to bandwidth constraints, to enhance Ethernet ring protection switching and network resilience.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If RPLs block network traffic to avoid logical loops in Ethernet ring networks, then logical loop avoidance is achieved, but network traffic transmission is hindered during normal operation
Solution Approach 1:
The network is segmented into multiple sub-rings, each managed independently with its own RPL configuration. This allows different segments to have different RPL states (blocked or unblocked), enabling traffic transmission in some segments while maintaining loop avoidance in others, thus resolving the contradiction between loop avoidance and traffic transmission
Solution Approach 2:
The RPL configuration is made dynamic rather than static. The system can adaptively change RPL states based on network conditions, allowing RPLs to be unblocked when needed for traffic transmission while maintaining loop avoidance through coordinated control across multiple sub-rings
2Device complexity
If a single common node is used in dual hub and spoke designs, then network configuration is simplified, but single-point failure risk increases
Solution Approach 1:
Different nodes are assigned different roles and characteristics. Core nodes form a mesh backbone providing redundancy, while non-core nodes have simplified configurations. This local differentiation allows simplified configuration for most nodes while maintaining high reliability through the redundant core mesh, resolving the contradiction between configuration simplicity and failure risk
Solution Approach 2:
The network is designed with pre-established redundant paths through the core node mesh before failures occur. When a non-core node or its connection fails, alternative paths through core nodes are already in place, providing beforehand cushioning against single-point failures while keeping the overall configuration manageable
3Reliability
If multiple sub-rings are configured to provide diverse paths, then network resilience is improved, but configuration complexity increases
Solution Approach 1:
Core nodes serve multiple functions: they form the mesh backbone, act as RPL owners for different sub-rings, and provide diverse paths for multiple non-core nodes. This multi-functionality reduces the need for separate dedicated structures for each sub-ring, simplifying overall configuration while maintaining resilience through diverse paths
Solution Approach 2:
Multiple sub-rings are merged at core nodes, allowing shared resources and coordinated RPL management. Instead of completely independent sub-rings, the merging at core nodes enables consolidated configuration management while still providing diverse paths and resilience, reducing configuration complexity
Data Source
AI summary
A method and system for designing Ethernet ring protection services in a network is used to identify a major ring and sub-rings for a dual hub and spoke network architecture.