Trunking for fabric ports in fibre channel switches and attached devices

• US 7,916,628 B2
• Filed: 11/01/2004
• Issued: 03/29/2011
• Est. Priority Date: 11/01/2004
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Desai, Tushar, Gupta, Shashank, Jain, Praveen, Ghosh, Kalyan K.
• Primary Examiner(s): Patel; Jayanti K
• Assistant Examiner(s): PARK, JUNG H
• Application Number:
  US10/979,886
• Publication Number:
  US 20060092932A1
• Time in Patent Office: 2,339 Days
• Field of Search: 370/218, 370/235, 370/252, 370/389, 370/401, 709/220, 709/223, 709/226, 709/238, 709/250
• US Class Current: 370/218
• CPC Class Codes: H04L 49/25 Routing or path finding in a switch fabric
• CPC Class Codes: H04L 49/3009 Header conversion, routing tables or routing tags
• CPC Class Codes: H04L 49/357 Fibre channel switches

Abstract

N_Ports and F_Ports are provided with logic allowing designation of multiple virtual interfaces on a single host bus adaptor or other Fiber Channel interface, one virtual interface for each VSAN operating on the node interface. Node ports with this additional functionality are referred to as trunking N_Ports or TN_Ports. These ports have a functional design allowing creation of the multiple virtual interfaces as appropriate for the application at hand. This port design also includes logic for communicating with a peer fabric port to initialize and modify the configuration of the virtual interfaces on the TN_Port. A corresponding functional design and communication logic is provided for fabric ports, referred to herein as trunking F_Ports or TF_Ports.

Claims

1. A trunking N_Port for a Fibre Channel node, the trunking N_Port comprising:

a physical N_Port interface designed or configured to provide functionality of a non-trunking N_Port when virtual Storage Area Network (SAN) functionality is not available; and

a controller for managing trunking on the trunking N_Port, wherein the controller is designed or configured to communicate with an F_Port on a Fibre Channel switch and determine whether virtual SAN functionality exists on the F_Port and if so define one or more virtual SAN interfaces on the trunking N_Port for one or more virtual SANs that are common to the F_Port and the trunking N_Port, with each of the virtual SAN interfaces providing the functionality of an N_Port for a corresponding one of the one or more virtual SANs that are common to the F_Port and the trunking N_Port;

wherein the controller is designed or configured to identify the one or more virtual SANs that are common to the F_Port and the trunking N_Port, to thereby define the one or more virtual SAN interfaces on the trunking N_Port.

2. The trunking N_Port of claim 1, wherein the trunking N_Port is implemented at least partially as software.

3. The trunking N_Port of claim 1, further comprising one or more instances of said virtual SAN interfaces.

4. The trunking N_Port of claim 1, wherein the physical N_Port functionality provides no information regarding virtual SANs in frames transmitted therefrom.

5. The trunking N_Port of claim 1, wherein each of one or more of the virtual SAN interfaces is designed or configured to provide frames containing information identifying the corresponding one of the one or more virtual SANs.

6. The trunking N_Port of claim 5, wherein the information identifying the particular virtual SAN to which it belongs is provided in an Extended Inter-Switch Link (EISL) header for the frames.

7. The trunking N_Port of claim 5, wherein the frames comprise QoS parameters defining levels of quality of service available for the virtual SANs.

8. The trunking N_Port of claim 1, wherein the controller is designed or configured to communicate with the F_Port using Exchange Peer Parameter (EPP) protocol.

9. The trunking N_Port of claim 1, wherein the controller has a Fibre Channel well known address but is designed or configured such that it does not take part in data traffic.

10. The trunking N_Port of claim 1, wherein the controller is designed or configured to negotiate a mode of operation with the F_Port and available modes of operation include trunking and non-trunking

11. The trunking N_Port of claim 1, wherein the controller is designed or configured to use EPP protocol to identify the VSANs common to the F_Port and the trunking N_Port.

12. The trunking N_Port of claim 1, wherein the controller is designed or configured to identify the one or more virtual SANs that are common to the F_Port and the trunking N_Port based upon a list of supported virtual SANs that is received from the F_Port, the list of supported virtual SANs identifying the one or more virtual SANs.

13. The trunking N_Port of claim 1, wherein the one or more virtual SANs that are common to the F_Port and the trunking N_Port includes two or more virtual SANs, wherein the controller defines two or more virtual SAN interfaces on the trunking N_Port for the two or more virtual SANs, with each of the two or more virtual SAN interfaces providing the functionality of an N_Port for a corresponding one of the two or more virtual SANs, thereby enabling the trunking N_Port to carry traffic for the two or more virtual SANs over a single link between the trunking N_Port and the F_Port.

14. A trunking N_Port or F_Port for a Fibre Channel device, the trunking N_Port or F_Port comprising a controller for managing trunking on the trunking N_Port or F_Port, wherein the controller is designed or configured to communicate with a peer port over a Fibre Channel link and determine whether virtual SAN functionality exists on the peer port and if so define one or more virtual Storage Area Network (SAN) interfaces on the trunking N_Port or F_Port for one or more virtual SANs that are common to the trunking N_Port or F_Port and the peer port, with each of the virtual SAN interfaces providing the functionality of a corresponding one of the one or more virtual SANs that are common to the trunking N_Port or F_Port and the peer port, wherein the controller is further designed or configured to identify the one or more virtual SANs that are common to the trunking N_Port or F_Port and the peer port, to thereby define the one or more virtual SAN interfaces on the trunking N_Port or F_Port.

15. The trunking N_Port or F_Port of claim 14, wherein the controller is designed or configured to negotiate a mode of operation with the peer and available modes of operation include trunking and non-trunking

16. The trunking N_Port or F_Port of claim 14, wherein the controller is designed or configured to identify the VSANs common to the F_Port or the trunking N_Port and the peer port based upon a list of supported virtual SANs that is received from the peer port, the list of supported virtual SANs identifying the one or more virtual SANs, to thereby define the one or more virtual SAN interfaces on the trunking N_Port or F_Port.

17. The trunking N_Port or F_Port of claim 15, wherein the controller is designed or configured to use Exchange Peer Parameter (EPP) protocol to identify VSANs common to the F_Port and the trunking N_Port.

18. The trunking N_Port or F_Port of claim 14, wherein each of the virtual SAN interfaces providing the functionality of a corresponding one of the one or more virtual SANs that are common to the trunking N_Port or F_Port and the peer port by providing frames containing information identifying the corresponding one of the one or more virtual SANs.

19. A storage area network comprising:

(a) two or more nodes, each comprising a trunking N_Port coupled to a Fibre Channel link; and

(b) one or more Fibre Channel switches comprising multiple F_Ports in communication with the trunking N_Ports and defining a fabric allowing communication among the two or more nodes,

wherein the trunking N_Ports comprise controllers designed or configured to communicate with F_Ports on a Fibre Channel switch and determine whether virtual Storage Area Network (SAN) functionality exists on the F_Ports and if so define one or more virtual SAN interfaces on their trunking N_Ports for one or more virtual SANs that are common to the trunking N_Ports and the F_Ports, with each of the one or more virtual SAN interfaces providing the functionality of an N_Port for a corresponding one of the one or more virtual SANs, wherein each of the controllers is further designed or configured to identify virtual SANs that are common to the corresponding one of the trunking N_Ports and a corresponding one of the F_Ports, to thereby define the one or more virtual SAN interfaces on the trunking N_Ports.

20. The storage area network of claim 19, wherein the two or more nodes comprise one or more storage nodes and one or more host nodes.

21. The storage area network of claim 19, wherein the controllers communicate with the F_Ports using Exchange Peer Parameter (EPP) protocol.

22. The storage area network of claim 19, wherein the controllers employ the Exchange Peer Parameter (EPP) protocol to identify VSANs common to the F_Ports and the trunking N_Ports.

23. A method of establishing a link between a trunking N_Port on a node and an F_Port on a Fibre Channel switch, the method comprising:

(a) determining whether virtual Storage Area Network (SAN) functionality exists on the F_Port; and

(b) defining two or more virtual SAN interfaces on the trunking N_Port, with each of the two or more virtual SAN interfaces providing the functionality of an N_Port for a corresponding one of two or more virtual SANs that are supported by the link between the trunking N_Port and the F_Port, wherein the functionality of an N_Port for a corresponding one of the two or more virtual SANs includes transmitting frames containing information identifying the corresponding one of the two or more virtual SANs.

24. The method of claim 23, wherein (a) and (b) are both implemented by communicating between the trunking N_Port on a node and the F_Port, the method further comprising:

identifying the two or more virtual SANs that are supported by the link between the trunking N_Port and the F_Port.

25. The method of claim 24, wherein the communicating comprises exchanging frames in Exchange Peer Parameter (EPP) protocol.

26. The method of claim 23, further comprising transmitting frames from one of the two or more of the virtual SAN interfaces, which frames containing information identifying the corresponding one of the two or more virtual SANs to which it belongs.

27. The method of claim 26, wherein the information identifying the particular virtual SAN to which it belongs is provided in an Extended Inter-Switch Link (EISL) header for the frames.

28. The method of claim 26, wherein the frames comprise QoS parameters defining levels of quality of service available for the virtual SANs.

29. The method of claim 23, further comprising conducting a negotiation between the trunking N_Port and the F_Port to determine a mode of operation with the F_Port, wherein available modes of operation include trunking and non-trunking.

30. A computer program product comprising a non-transitory computer-readable storage medium on which is provided program instructions for establishing a link between a trunking N_Port on a node and an F_Port on a Fibre Channel switch, wherein the program instructions comprise:

(a) code for determining by the N_Port whether virtual Storage Area Network (SAN) functionality exists on the F_Port;

(b) code for defining one or more virtual SAN interfaces on the trunking N_Port for one or more virtual SANs that are supported by the link between the trunking N_Port and the F_Port, with each of the virtual SAN interfaces providing the functionality of an N_Port for a corresponding one of the one or more virtual SANs that are supported by the link between the trunking N_Port and the F_Port; and

(c) code for identifying the one or more virtual SANs that are supported by the link between the F_Port and the trunking N_Port, to thereby define the one or more virtual SAN interfaces on the trunking N_Port.

31. The computer program product of claim 30, wherein the program code for both (a) and (c) comprises code for communicating between the trunking N_Port on a node and the F_Port.

32. The computer program product of claim 31, wherein the code for communicating comprises code for exchanging frames in Exchange Peer Parameter (EPP) protocol.

33. The computer program product of claim 30, further comprising code for transmitting frames from the one or more of the virtual SAN interfaces, which frames containing information identifying the corresponding one of the one or more virtual SANs to which it belongs.

34. The computer program product of claim 33, wherein the code for transmitting frames comprises code for providing an Extended Inter-Switch Link (EISL) header for the frames.

35. The computer program product of claim 33, wherein the code for transmitting frames comprises code for providing QoS parameters defining levels of quality of service available for the virtual SANs.

36. The computer program product of claim 30, further comprising code for conducting a negotiation between the trunking N_Port and the F_Port to determine a mode of operation with the F_Port, wherein available modes of operation include trunking and non-trunking.

37. A trunking N_Port for a Fibre Channel node, the trunking N_Port comprising:

(a) means for determining whether virtual Storage Area Network (SAN) functionality exists on a F_Port to which the trunking N_Port is linked;

(b) means for defining one or more virtual SAN interfaces on the trunking N_Port for one or more virtual SANs that are supported by the F_Port, with each of the virtual SAN interfaces providing the functionality of an N_Port for a corresponding one of the one or more virtual SANs that are supported by the F_Port; and

(c) means for identifying the one or more virtual SANs that are supported by the F_Port, to thereby define the one or more virtual SAN interfaces on the trunking N_Port.

38. The trunking N_Port of claim 37, wherein the means for determining is designed or configured to exchange frames in Exchange Peer Parameter (EPP) protocol.

39. The trunking N_Port of claim 37, further comprising means for transmitting frames from the one or more of the virtual SAN interfaces, which frames containing information identifying the corresponding one of the one or more virtual SANs to which it belongs.

40. The trunking N_Port of claim 39, wherein the information identifying the particular virtual SAN to which it belongs is provided in an Extended Inter-Switch Link (EISL) header for the frames.

41. The trunking N_Port of claim 39, wherein the frames comprise QoS parameters defining levels of quality of service available for the virtual SANs.

42. The trunking N_Port of claim 37, further comprising means for conducting a negotiation between the trunking N_Port and the F_Port to determine a mode of operation with the F_Port, wherein available modes of operation include trunking and non-trunking.