Target Driven Peer-Zoning Synchronization via Database Versioning
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current zoning techniques in Fibre Channel storage area networks (SANs) are complex and error-prone, especially with target-driven peer zoning (TDPZ), where synchronization between target and switch databases can be disrupted by link down conditions, leading to communication breakdowns and database desynchronization.
Innovation Solution
Implementing versioning in TDPZ databases to maintain synchronization by tracking changes and comparing version numbers between target and switch databases, ensuring accurate record-keeping and updates upon re-establishment of communication links.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If target-driven peer zoning is implemented to simplify zoning management, then ease of operation is improved, but reliability deteriorates due to database desynchronization during link down conditions
Solution Approach 1:
The patent applies preliminary action by implementing version number tracking in advance before communication breakdowns occur. Each database entry includes a version number that is updated before changes are made, allowing the target device to proactively detect and resolve synchronization issues when links are re-established, rather than reacting to errors after they occur.
Solution Approach 2:
The patent implements feedback mechanisms where the target device periodically queries the switch for database version numbers and compares them against local versions. This continuous feedback loop enables the system to detect desynchronization caused by link down conditions and automatically resolve it by syncing the most current database state, thereby maintaining reliability while preserving ease of operation.
2Reliability
If versioning is implemented in TDPZ databases to maintain synchronization, then reliability is improved, but device complexity increases
Solution Approach 1:
The patent applies local quality by adding version numbers only to specific database entries that are subject to change (peer zone configurations), rather than implementing versioning across the entire database structure. This localized approach maintains reliability for critical synchronization points while minimizing the increase in overall device complexity.
Solution Approach 2:
The patent uses copying by maintaining a simplified local version of the zone database at the target device that mirrors the switch's database structure. Instead of implementing complex distributed consensus protocols, the target device copies and caches version information from the switch, enabling efficient synchronization with minimal added complexity while ensuring reliability.
3Reliability
If communication protocols are enhanced to verify database synchronization, then reliability is improved, but loss of time increases due to additional verification steps
Solution Approach 1:
The patent extracts the essential synchronization verification information by using only version numbers for comparison, rather than transmitting or comparing entire database contents. This extraction approach maintains high reliability by ensuring database consistency while minimizing the time required for verification, as version number comparison is computationally lightweight and rapid.
Solution Approach 2:
The patent applies partial action by implementing verification only when necessary - specifically when communication links are re-established after down conditions. Instead of continuous verification that would consume excessive time, the system performs targeted version number checks at critical transition points, achieving sufficient reliability without excessive time overhead.
Data Source
AI summary
A system and method for target driven peer-zoning (TDPZ) synchronization can include a principal member device and a switch. The principal member device can include to send an active peer zone list request to a switch. In an example, the principal member device can store a first TDPZ database version number and a first TDPZ zone list. In an example, the switch may send a response based on the active peer zone list request. In an example, the response can include a second TDPZ database version number and a second TDPZ zone list. The principal member device may compare the first TDPZ database version number to the second TDPZ database version number.