Backward congestion notification

• US 8,121,038 B2
• Filed: 08/21/2007
• Issued: 02/21/2012
• Est. Priority Date: 08/21/2007
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Bergamasco, Davide, Dutt, Dinesh
• Primary Examiner(s): Yao, Kwang B
• Assistant Examiner(s): Tran, Tung Q
• Application Number:
  US11/842,866
• Publication Number:
  US 20090052326A1
• Time in Patent Office: 1,645 Days
• Field of Search: 370229-240
• US Class Current: 370/236
• CPC Class Codes: H04L 47/10 Flow control; Congestion control
• CPC Class Codes: H04L 47/11 Identifying congestion
• CPC Class Codes: H04L 47/17 Interaction among intermediate nodes, e.g. hop by hop
• CPC Class Codes: H04L 47/263 Rate modification at the source after receiving feedback
• CPC Class Codes: H04L 47/33 using forward notification

Abstract

In one embodiment, an apparatus comprises a network interface system having at least one input port configured for receiving frames and a logic system comprising at least one logic device. The logic system may be configured to perform the following functions: determining a source address and a destination address of a frame received at an ingress port; calculating a flow hash based at least upon the source address and the destination address; forming a congestion management (“CM”) tag that includes the flow hash; inserting the CM tag in the frame; and forwarding the frame to the destination address.

Claims

1. A method, comprising:

receiving by a first network device a Backwards Congestion Notification (BCN) frame from a congestion point, wherein the BCN frame that is received indicates information pertaining to congestion for a flow associated with a source address and a destination address;

receiving a frame at an ingress port of the first network device;

determining a source address and a destination address of the frame by the first network device;

determining by the first network device that the source address of the frame is equal to the source address identified in the BCN frame, and that the destination address of the frame is equal to the destination address identified in the BCN frame;

calculating a flow hash based at least upon the source address and the destination address by the first network device;

forming a congestion management (“

CM”

) tag that includes the flow hash and additional information pertaining to the congestion for the flow associated with the source address and the destination address;

inserting the CM tag in the frame by the first network device; and

forwarding the frame by the first network device to the destination address;

wherein the BCN frame that is received indicates a manner in which traffic associated with the flow identified by the source address and the destination address is to be handled by another network device receiving the BCN frame;

wherein the another network device is an edge switch and the congestion point is a core switch.

2. The method of claim 1, further comprising determining a virtual local area network value of the frame, wherein the calculating step comprises calculating the flow hash based upon the source address, the destination address and the virtual local area network value.

3. The method of claim 1, further comprising determining whether a BCN frame has recently been received for the identified flow.

4. The method of claim 1, wherein the forming further comprises including a backwards congestion notification (“

BCN”

) address in the CM tag, wherein the BCN address comprises an address of the ingress port.

5. The method of claim 1, wherein the ingress port is not configured to provide backwards congestion notification (“

BCN”

) reaction point functionality and wherein an egress port of the first network device is configured to provide BCN reaction point functionality, further comprising forming, by the egress port, an indication for an ingress port of a second network device to add a BCN address in the CM tag.

6. The method of claim 3, wherein it is determined that a recent indication of congestion has been received for the identified flow, the method further comprising determining congestion point information identifying the congestion point, wherein the forming further comprises including the congestion point information identifying the congestion point in the CM tag.

7. The method of claim 4, wherein the forming further comprises including an indication in one or more bits of the CM tag, the indication when in a first state indicating that the BCN address comprises a Media Access Control (MAC) hierarchical address, and the indication when in a second state indicating that the BCN address is a combination of a MAC address and a port index.

8. The method of claim 6, wherein determining congestion point information comprises retrieving a stored congestion point identification hash value.

18. The method of claim 1, wherein the BCN frame indicates a level of congestion for the flow.

20. The method of claim 1, wherein the BCN frame indicates a condition of mild or severe congestion for the flow.

21. The method of claim 1, wherein the BCN frame includes information pertaining to congestion at the congestion point.

22. The method as recited in claim 21, further comprising:

providing at least a portion of the information pertaining to the congestion at the congestion point in the CM tag prior to forwarding the frame to the destination address.

31. The method as recited in claim 1, wherein the CM tag includes a code that indicates that the CM tag pertains to congestion management.

32. The method as recited in claim 1, wherein the CM tag indicates whether the first network device has recently received an indication of congestion for the flow from the congestion point.

33. The method as recited in claim 1, wherein the CM tag indicates whether BCN reaction point functionality is implemented on all input ports of the first network device.

34. The method as recited in claim 1, wherein the CM tag includes one or more bits to include information pertaining to a congestion managed domain that includes Data Center Ethernet (DCE) portions and at least one classical Ethernet portion.

35. The method as recited in claim 1, wherein the BCN flame when in a first state is a positive BCN feedback message indicating that the congestion has improved or has dissipated.

36. The method as recited in claim 1, wherein the BCN flame when in a first state indicates that the first network device should increase a rate at which traffic associated with the flow is to be transmitted.

37. The method as recited in claim 1, wherein the BCN flame includes one or more bits that indicate a condition of mild congestion when the one or more bits are in a first state, and indicate a condition of severe congestion when the one or more bits are in a second state.

40. The method as recited in claim 1, wherein at least a portion of the additional information pertaining to the congestion for the flow associated with the source address and the destination address is obtained from the BCN frame.

9. An apparatus, comprising:

a network interface system comprising at least one input port configured for receiving frames; and

a logic system comprising at least one logic device configured to perform the following functions;

receiving a Backwards Congestion Notification (BCN) frame from a congestion point, wherein the BCN frame that is received indicates information pertaining to congestion for a flow associated with a source address and a destination address;

determining a source address and a destination address of a frame received at an ingress port;

determining that the source address of the frame is equal to the source address identified in the BCN frame, and that the destination address of the frame is equal to the destination address identified in the BCN frame;

calculating a flow hash based at least upon the source address and the destination address;

forming a congestion management (“

CM”

) tag that includes the flow hash and additional information pertaining to the congestion for the flow associated with the source address and the destination address;

inserting the CM tag in the frame; and

forwarding the frame to the destination address.

10. The apparatus of claim 9, wherein the logic system is further configured to determine a virtual local area network value of the frame and wherein the calculating function comprises calculating the flow hash based upon the source address, the destination address and the virtual local area network value.

11. The apparatus of claim 9, wherein the logic system is further configured to determine whether a backwards congestion notification (“

BCN”

) frame has recently been received for the identified flow, wherein the CM tag indicates whether the apparatus has recently received an indication of congestion for the flow from the congestion point.

12. The apparatus of claim 9, wherein the forming function further comprises including a backwards congestion notification (“

BCN”

) address in the CM tag, wherein the BCN address comprises an address of the ingress port.

13. The apparatus of claim 9, wherein the ingress port is not configured to provide backwards congestion notification (“

BCN”

) reaction point functionality and wherein an egress port of the apparatus is configured to provide BCN reaction point functionality, further comprising forming, by the egress port, an indication for an ingress port of another apparatus to add a BCN address in the CM tag.

14. The apparatus of claim 11, wherein the logic system determines that a recent indication of congestion has been received for the identified flow, wherein the logic system is further configured to determine congestion point information identifying the congestion point, wherein the forming function further comprises including the congestion point information identifying the congestion point in the CM tag.

15. The apparatus of claim 12, wherein the forming function further comprises including an indication in one or more bits of the CM tag, the indication when in a first state indicating that the BCN address comprises a Media Access Control (MAC) hierarchical address, and the indication when in a second state indicating that the BCN address is a combination of a MAC address and a port index.

16. The apparatus of claim 14, further comprising a memory, wherein determining congestion point information comprises retrieving a stored congestion point identification hash value that identifies the congestion point from the memory.

23. The apparatus as recited in claim 9, wherein the BCN frame that is received indicates a manner in which traffic associated with the flow identified by the source address and the destination address is to be handled by another network device receiving the BCN frame.

24. The apparatus as recited in claim 23, wherein the another network device is an edge switch and the congestion point is a core switch.

17. An apparatus, comprising:

means for receiving a Backwards Congestion Notification (BCN) frame from a congestion point, wherein the BCN frame that is received indicates information pertaining to congestion for a flow associated with a source address and a destination address;

means for receiving a frame at an ingress port of a first network device;

means for determining a source address and a destination address of the frame;

means for determining that the source address of the frame is equal to the source address identified in the BCN frame, and that the destination address of the frame is equal to the destination address identified in the BCN frame;

means for forming a congestion management (“

CM”

) tag that identifies the flow and includes additional information pertaining to the congestion for the flow associated with the source address and the destination address;

means for inserting the CM tag in the frame; and

means for forwarding the frame to the destination address;

wherein the BCN frame that is received indicates a manner in which traffic associated with the flow identified by the source address and the destination address is to be handled by another network device receiving the BCN frame;

wherein the another network device is an edge switch and the congestion point is a core switch.

19. The method of 1, wherein the CM tag contains congestion point identification data identifying the congestion point from which the BCN frame was received.

25. An apparatus, comprising:

a processor; and

a memory, at least one of the processor or the memory being configured to perform the following functions;

receiving a Backwards Congestion Notification (BCN) frame from a congestion point, wherein the BCN frame that is received indicates information pertaining to congestion for a flow associated with a source address and a destination address;

receiving a frame at an ingress port of a first network device;

determining a source address and a destination address of the frame;

determining that the source address of the frame is equal to the source address identified in the BCN frame, and that the destination address of the frame is equal to the destination address identified in the BCN frame;

forming a congestion management (“

CM”

) tag that identifies the flow and includes additional information pertaining to the congestion for the flow associated with the source address and the destination address;

inserting the CM tag in the frame; and

forwarding the frame to the destination address;

wherein the BCN frame that is received indicates a manner in which traffic associated with the flow identified by the source address and the destination address is to be handled by another network device receiving the BCN frame;

wherein the another network device is a first edge switch and the congestion point is a core switch.

26. A method, comprising:

receiving a Backwards Congestion Notification (BCN) frame from a congestion point, wherein the BCN frame that is received indicates information pertaining to congestion for a flow associated with a source address and a destination address;

receiving a frame at an ingress port of a first network device;

determining a source address and a destination address of the frame;

determining that the source address of the frame is equal to the source address identified in the BCN frame, and that the destination address of the frame is equal to the destination address identified in the BCN frame;

forming a congestion management (“

CM”

) tag that identifies the flow and includes additional information pertaining to the congestion for the flow associated with the source address and the destination address;

inserting the CM tag in the frame; and

forwarding the frame to the destination address;

wherein the BCN frame that is received indicates a manner in which traffic associated with the flow identified by the source address and the destination address is to be handled by another network device receiving the BCN frame.

27. The method as recited in claim 26, further comprising:

determining congestion point information identifying the congestion point from the BCN frame, wherein the forming further comprises including an identifier of the congestion point in the CM tag to elicit feedback from the congestion point.

28. The method as recited in claim 27, wherein the congestion point is a core switch and the method is performed by an edge device.

29. The method as recited in claim 26, wherein the frame is not a BCN frame.

30. The method as recited in claim 26, wherein the frame is a data frame.

39. The method as recited in claim 27, further comprising:

receiving one or more additional BCN frames from the congestion point, the one or more additional BCN frames including congestion change information and at least one measure of congestion, the congestion change information and the at least one measure of congestion pertaining to the flow associated with the source address and the destination address.

41. The method as recited in claim 26, wherein at least a portion of the additional information pertaining to the congestion for the flow associated with the source address and the destination address is obtained from the BCN frame or has previously been obtained from another BCN frame.

38. A method, comprising:

receiving a frame at an ingress port of the first network device;

determining a source address and a destination address of the frame;

calculating a flow hash based at least upon the source address and the destination address by the first network device;

forming a congestion management (“

CM”

) tag that includes the flow hash, wherein the forming includes providing a backwards congestion notification (“

BCN”

) address in the CM tag, wherein the BCN address includes an address of the ingress port;

inserting the CM tag in the frame by the first network device;

forwarding the frame by the first network device to the destination address; and

receiving by the first network device a BCN frame from a congestion point, wherein the BCN frame is received at the ingress port identified in the CM tag of the frame, wherein the BCN frame that is received indicates information pertaining to congestion for the flow associated with the source address and the destination address, wherein the BCN frame that is received indicates a manner in which traffic associated with the flow identified by the source address and the destination address is to be handled by another network device receiving the BCN frame;

wherein the another network device is an edge switch and the congestion point is a core switch.