Link aggregation in software-defined networks

• US 9,729,387 B2
• Filed: 02/18/2015
• Issued: 08/08/2017
• Est. Priority Date: 01/26/2012
• Status: Active Grant

• Current Assignee: Avago Technologies International Sales Pte Limited (Broadcom, Inc.)
• Original Assignee: Brocade Communications Systems, Inc. (Broadcom, Inc.)
• Inventors: Ananthapadmanabha, Kashyap Tavarekere, Lakshminarasimhan, Arvindsrinivasan, Agarwal, Vivek
• Primary Examiner(s): Elliott, IV, Benjamin H
• Application Number:
  US14/625,536
• Publication Number:
  US 20150172098A1
• Time in Patent Office: 902 Days
• CPC Class Codes: H04L 41/0654 using network fault recovery ring fault isolation or reconfiguration in loop networks without recovery actions by a network management system H04L12/437
• CPC Class Codes: H04L 45/245 Link aggregation, e.g. trunking
• CPC Class Codes: H04L 47/10 Flow control; Congestion control
• CPC Class Codes: H04L 49/25 Routing or path finding in a switch fabric
• CPC Class Codes: Y02D 30/50 in wire-line communication networks, e.g. low power modes or reduced link rate

Abstract

One embodiment of the present invention provides a switch capable of processing software-defined data flows. The switch includes an identifier management module and a flow definition management module. During operation, the identifier management module allocates a logical identifier to a link aggregation port group which includes a plurality of ports associated with different links. The flow definition management module processes a flow definition corresponding to the logical identifier, applies the flow definition to ports in the link aggregation port group, and update lookup information for the link aggregation port group based on the flow definition.

Claims

1. A switch, comprising:

identifier management circuitry configured to create a mapping between a logical identifier identifying a link aggregation port group and a respective port participating in the port group, wherein the port group includes a plurality of ports associated with different links; and

flow definition management circuitry configured to;

identify a first flow definition comprising a rule and the logical identifier, wherein the rule indicates how a flow is processed based on the logical identifier;

identify one or more ports of the switch corresponding to the logical identifier based on the mapping;

convert the first flow definition to a second flow definition applicable to the identified one or more ports of the switch; and

apply the second flow definition to traffic associated with the identified one or more ports.

2. The switch of claim 1, wherein the flow definition management circuitry is further configured to incorporate, in the second flow definition, a local policy regarding traffic distribution across the identified local ports.

3. The switch of claim 1, further comprising high-availability circuitry configured to:

detect a failure associated with one of the identified local ports;

identify active ports in the identified one or more ports; and

update lookup information to associate the second flow definition with the identified active ports.

4. The switch of claim 1, wherein the logical identifier appears as a port identifier in the first flow definition.

5. A switch, comprising:

identifier management circuitry configured to create a mapping between a logical identifier identifying a multi-switch link aggregation port group and a respective port participating in the port group, wherein the port group includes a plurality of ports of the switch and a remote switch;

election circuitry configured to elect a master switch between the switch and the remote switch, wherein the switch and the remote switch participate in the multi-switch link aggregation port group, and wherein the master switch is responsible for obtaining flow definitions for the port group;

wherein the logical identifier is same in the switch and the remote switch; and

flow definition management circuitry configured to identify a first flow definition comprising a rule and the logical identifier, wherein the first flow definition is received based on a data path identifier, which identifies the switch to a controller, and wherein the rule indicates how a flow is processed based on the logical identifier.

6. The switch of claim 5, wherein the flow definition management circuitry is further configured to:

identify one or more ports of the switch corresponding to the logical identifier based on the mapping;

convert the first flow definition to a second flow definition applicable to the identified one or more ports; and

apply the second flow definition to traffic associated with the identified one or more ports.

7. The switch of claim 5, further comprising synchronization circuitry configured to, in response to the switch being the master switch, construct, for the remote switch, a message comprising the data path identifier.

8. The switch of claim 5, further comprising synchronization circuitry configured to, in response to the remote switch being the master switch, identify the first flow definition in a message from the remote switch.

9. The switch of claim 8, further comprising high-availability circuitry configured to detect a failure associated with the remote switch;

and

wherein the flow definition management circuitry is further configured to, in response to the detection of the failure, construct a connection request destined to the network controller based on the data path identifier.

10. The switch of claim 8, wherein the flow definition management circuitry is further configured to, in response to identifying a take-over message from the remote switch, construct a connection request destined to the network controller based on the data path identifier, wherein the take-over message instructs the switch to operate as the master switch.

11. A computer-executable method, comprising:

creating at a switch a mapping between a logical identifier identifying a link aggregation port group and a respective port participating in the port group, wherein the port group includes a plurality of ports associated with different links;

identifying a first flow definition comprising a rule and the logical identifier, wherein the rule indicates how a flow is processed based on the logical identifier;

identifying one or more ports of the switch corresponding to the logical identifier based on the mapping;

converting the first flow definition to a second flow definition applicable to the identified one or more ports of the switch; and

applying the converted flow definition to traffic associated with the identified one or more ports.

12. The method of claim 11, further comprising incorporating, in the second flow definition, a local policy regarding traffic distribution across the identified one or more ports.

13. The method of claim 11, further comprising:

detecting a failure associated with one of the identified local ports;

identifying active ports in the identified one or more ports; and

updating lookup information to associate the second flow definition with the identified active ports.

14. The method of claim 11, wherein the logical identifier appears as a port identifier in the first flow definition.

15. A computer-executable method, comprising:

creating at a first switch a mapping between a logical identifier identifying a multi-switch link aggregation port group and a respective port participating in the port group, wherein the port group includes a plurality of ports of the first switch and a second switch;

electing a master switch between the first switch and the second switch, wherein the first switch and the second switch participate in the multi-switch link aggregation port group, and wherein the master switch is responsible for obtaining flow definitions for the port group;

wherein the logical identifier is same in the first switch and the second switch; and

identifying a first flow definition comprising a rule and the logical identifier, wherein the first flow definition is received based on a data path identifier, which identifies the switch to a controller, and wherein the rule indicates how a flow is processed based on the logical identifier.

16. The method of claim 15, further comprising:

identifying one or more ports of the first switch corresponding to the logical identifier based on the mapping;

converting the first flow definition to a second flow definition applicable to the identified one or more ports; and

applying the second flow definition to traffic associated with the identified one or more ports.

17. The method of claim 15, further comprising:

in response to the first switch being the master switch, constructing, for the second switch, a message comprising the data path identifier.

18. The method of claim 15, further comprising, in response to the second switch being the master switch, identifying the first flow definition in a message from the second switch.

19. The method of claim 18, further comprising:

detecting a failure associated with the second switch; and

in response to the detection of the failure, constructing a connection request destined to the network controller based on the data path identifier.

20. The method of claim 15, wherein, in response to identifying a take-over message from the second switch, constructing a connection request destined to the network controller based on the data path identifier, wherein the take-over message instructs the first switch to operate as the master switch.