Peer Zone Database Distribution in Fibre Channel Fabric
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional Fibre Channel (FC) Fabric zoning protocols require a Fabric lock, which can lead to deadlocks and delayed zone activation, especially when multiple devices connect simultaneously, disrupting continuous operation and zone updates.
Innovation Solution
Implementing peer zone servers that enable switches to communicate and share new or modified peer zone definitions without locking the FC Fabric, using unique domain IDs for simultaneous distribution across the Fabric, eliminating the need for a Fabric-wide lock.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Stability of the object's composition
If a Fabric lock is used to ensure consistent zone definition distribution, then zoning information consistency is improved, but system availability and update speed deteriorate due to deadlocks and delayed activation
Solution Approach 1:
The patent introduces a domain controller as an intermediary component that mediates zone definition distribution. Instead of requiring all switches to lock the entire fabric simultaneously, the domain controller acts as a coordinator that manages zone definition updates and distributes them to switches sequentially. This intermediary approach maintains consistency without requiring global fabric locking, thereby preventing deadlocks and improving system availability.
Solution Approach 2:
The patent segments the zone definition distribution process into individual switch-level operations rather than requiring a monolithic fabric-wide lock. Each switch can independently receive and apply zone definitions from the domain controller without blocking other switches. This segmentation allows parallel processing of zone updates across different switches, eliminating the deadlock condition that arises from centralized fabric locking.
2Stability of the object's composition
If a Fabric lock is used to distribute zone definitions, then consistent update control is improved, but convergence time and update speed deteriorate
Solution Approach 1:
The domain controller performs preliminary actions by preparing and staging zone definition updates before distributing them to switches. The controller can pre-validate zone definitions, prepare distribution sequences, and coordinate updates in advance. This preliminary preparation enables faster, more efficient distribution without requiring time-consuming fabric lock acquisition and release cycles, thereby reducing convergence time while maintaining update consistency.
Solution Approach 2:
The patent enables continuous zone definition distribution by eliminating the stop-start nature of fabric locking. The domain controller can continuously receive zone definitions from storage devices and distribute them to switches without interruption. This continuous operation allows zone updates to propagate through the fabric without the delays inherent in acquiring and releasing fabric locks, significantly reducing convergence time while maintaining consistent updates.
3Reliability
If multiple devices connect simultaneously without Fabric locking, then system availability and update speed are improved, but merge conflicts and distribution errors increase
Solution Approach 1:
The domain controller implements feedback mechanisms to monitor and track zone definition distribution across all switches. When multiple devices connect simultaneously and initiate zone updates, the controller receives feedback about the current state of each switch and coordinates the distribution sequence accordingly. This feedback loop prevents merge conflicts by detecting potential conflicts before they occur and resolving them through coordinated distribution, thereby maintaining zone definition accuracy while allowing simultaneous connections.
Solution Approach 2:
Before distributing zone definitions to multiple switches simultaneously, the domain controller performs preliminary validation and conflict detection. It checks for potential merge conflicts in advance and prepares a coordinated distribution sequence. This preliminary action ensures that even when multiple devices connect simultaneously, their zone definitions are distributed in a controlled manner that prevents errors and maintains accuracy, while still allowing parallel processing that preserves system availability.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Provided are techniques for the efficient distribution of peer zone databases in a FC Fabric. In an example, a switch instantiates a peer zone definition defining a peer zone in which two or more initiator host devices are each permitted to communicate with one or more target storage devices via the switched FC fabric and the two or more initiator host devices are prevented from communicating with each other. The switch stores the peer zone definition in a peer zone database at the FC switch, and distributes the peer zone definition to other FC switches of the switched FC fabric without performing a Fabric lock operation.