Fibre Channel Name Server IP Alias Failover
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The Fibre Channel (FC) protocol is not well-suited for cluster-failover configurations due to limitations in associating multiple IP addresses with ports, making it difficult to establish seamless failover partnerships between nodes.
Innovation Solution
Assigning multiple upper-level protocol addresses to Fibre Channel node devices and configuring them to resolve these addresses using an encoding scheme within the Fibre Channel protocol, allowing for the formation of failover clusters and seamless identity assumption in case of failures.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a ULP port queries a name server to discover the port ID of the corresponding ULP port, then the discovery process works for single IP address associations, but it cannot support failover clustering requiring multiple IP addresses per port
Solution Approach 1:
The patent segments the address association function by separating the primary IP address from additional IP addresses. The name server stores multiple IP addresses associated with a single port ID, allowing the system to distinguish between primary and backup addresses. This segmentation enables failover clustering while maintaining the existing name server query mechanism.
Solution Approach 2:
The patent makes the name server multi-functional by enabling it to store and retrieve multiple IP addresses for a single port ID. This universal approach allows the same name server infrastructure to support both single-address and multi-address scenarios, providing failover capability without requiring a completely new discovery mechanism.
2Adaptability or versatility
If FARP requests are used to discover port IDs, then all ports on the fabric receive the request, but each port can only match a single IP address, preventing failover partner discovery
Solution Approach 1:
The patent performs preliminary action by pre-configuring multiple IP addresses and their associations with port IDs in the name server before failover is needed. When a failover event occurs, the system can immediately query the name server for alternative IP addresses associated with the failed port, enabling rapid failover without requiring FARP requests to scan the entire fabric.
Solution Approach 2:
The patent introduces the name server as an intermediary between IP address resolution and port discovery. Instead of relying on FARP requests to propagate through all ports, the name server acts as a centralized mediator that stores the mapping between multiple IP addresses and port IDs, allowing direct resolution without fabric-wide broadcasting.
3Speed
If the FC protocol is used for high-speed storage communications, then performance is improved, but the protocol lacks support for multiple IP addresses per port, limiting cluster-failover configurations
Solution Approach 1:
The patent changes the parameter of IP address association by modifying how many IP addresses can be associated with a single port ID in the name server. This parameter change from one-to-one to one-to-many association enables cluster-failover configurations while maintaining the high-speed FC protocol communication framework.
Data Source
AI summary
In one embodiment, a method for building a failover-enabled communications systems is provided. The method comprises clustering a plurality of Fiber Channel (FC) node devices to form a failover cluster. A primary link is established between a first FC node device in the failover cluster and a FC node device outside the failover cluster. In the event of failure of the primary link, a backup link is established between the FC node device outside the failover cluster and a second FC node device in the failover cluster.