Lightweight Reliability Transport Protocol for Fibre-Channel Load-Balancing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current data communication techniques, such as Fibre-Channel and FC over Internet Protocol, face limitations in write acceleration and tape acceleration across metropolitan or wide area networks, restricting the use of equal-cost multi-path links and port-channels, which hinders high resiliency and performance in applications like remote replication and disaster recovery.
Innovation Solution
The implementation of a Lightweight Reliability Transport Protocol (LRTP) abstracts protocol intelligence from end-points of inter-switch links, placing it in service engines within the fabric, allowing for reliable and in-order delivery of Fibre-Channel packets across networks, enabling load-balancing and fault-tolerance by prepending a reliability protocol header to packets before transmission.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If protocol intelligence is placed at end-points of ISLs for write acceleration, then write acceleration is enabled, but equal-cost multi-path links and port-channels cannot be used
Solution Approach 1:
The patent introduces service engines as intermediary components that host the protocol intelligence for acceleration services. These service engines act as mediators between the end-points and the acceleration functionality, allowing traffic to be redirected through intermediate nodes. This intermediary architecture enables both write acceleration and multi-path link support, as the service engines can distribute traffic across multiple paths while maintaining acceleration capabilities.
Solution Approach 2:
The patent transitions from a two-endpoint architecture to a three-component architecture by introducing service engines in the middle. This dimensional change allows the system to simultaneously support acceleration services and ECMP/port-channel functionality, as the service engines provide an additional layer where traffic can be distributed across multiple paths while maintaining the acceleration processing capability.
2Productivity
If protocol intelligence is placed at end-points for tape acceleration, then tape acceleration is enabled, but port-channels cannot be used
Solution Approach 1:
The patent uses service engines as intermediaries to host tape acceleration functionality. Instead of placing intelligence directly at end-points, the service engines provide the acceleration services for tape workflows while sitting in the fabric. This allows port-channels to be utilized for redundancy and load-balancing, as the service engines can distribute tape acceleration traffic across multiple physical links.
Solution Approach 2:
The patent implements tape acceleration by copying the acceleration functionality into service engines rather than embedding it at end-points. This copying approach allows the same acceleration logic to be shared across multiple paths and deployed independently at different locations in the fabric, enabling both tape acceleration and port-channel support simultaneously.
3Reliability
If acceleration services are implemented to abstract protocol intelligence, then resiliency and multi-path support are improved, but device complexity increases
Solution Approach 1:
The patent designs service engines to perform multiple functions: they provide acceleration services for various workflows (write, tape, replication), handle traffic distribution across ECMP paths, manage port-channel bonding, and provide failover capabilities. By consolidating these diverse functions into universal service engines, the system achieves high resiliency and multi-path support without proportionally increasing overall system complexity.
Data Source
AI summary
Techniques are provided for transmitting a plurality of Fiber-Channel packets in an FC network. A reliability protocol header comprising reliability attributes and FC attributes are prepended to the FC packets prior to their transmission for each packet in an exchange block comprising a plurality of FC packets. The FC packets are transmitted with the reliability protocol header across the FC network for delivery to a destination device.


