Multiple Logical Channels for Use in Network Devices

• US 20110110236A1
• Filed: 01/14/2011
• Published: 05/12/2011
• Est. Priority Date: 07/23/2001
• Status: Active Grant

• Current Assignee: Avago Technologies International Sales Pte Limited (Broadcom, Inc.)
• Original Assignee: Broadcom Corporation (Broadcom, Inc.)
• Inventors: Kadambi, Shiri, Talayco, Daniel, Relan, Sandeep, Christie, Allan, Elzur, Uri, Kalkunte, Mohan, Ambe, Shekhar, Lund, Martin
• Granted Patent: US 8,493,857 B2
• Time in Patent Office: Days
• US Class Current: 370/235
• CPC Class Codes: H04L 12/4641 Virtual LANs, VLANs, e.g. virtual private networks [VPN] LAN interconnection over a bridge based backbone H04L12/462; encapsulation techniques H04L12/4633; routing of packets H04L45/00; packet switches H04L49/00; virtual private networks for security H04L63/0272
• CPC Class Codes: H04L 45/66 Layer 2 routing, e.g. in Ethernet based MAN's
• CPC Class Codes: H04L 47/10 Flow control; Congestion control
• CPC Class Codes: H04L 47/11 Identifying congestion
• CPC Class Codes: H04L 47/16 in connection oriented networks, e.g. frame relay
• CPC Class Codes: H04L 47/18 End to end
• CPC Class Codes: H04L 47/24 Traffic characterised by specific attributes, e.g. priority or QoS
• CPC Class Codes: H04L 47/2433 Allocation of priorities to traffic types
• CPC Class Codes: H04L 47/2441 relying on flow classification, e.g. using integrated services [IntServ]
• CPC Class Codes: H04L 47/266 Stopping or restarting the source, e.g. X-on or X-off
• CPC Class Codes: H04L 47/29 using a combination of thresholds
• CPC Class Codes: H04L 47/30 in combination with information about buffer occupancy at either end or at transit nodes
• CPC Class Codes: H04L 47/33 using forward notification
• CPC Class Codes: H04L 47/50 Queue scheduling
• CPC Class Codes: H04L 47/6205 Arrangements for avoiding head of line blocking
• CPC Class Codes: H04L 47/6215 Individual queue per QOS, rate or priority
• CPC Class Codes: H04L 47/6225 Fixed service order, e.g. Round Robin
• CPC Class Codes: H04L 49/205 Quality of Service based
• CPC Class Codes: H04L 49/3018 Input queuing
• CPC Class Codes: H04L 49/351 for local area network [LAN], e.g. Ethernet switches
• CPC Class Codes: H04L 49/50 : Overload detection or protection within a single switching element
• CPC Class Codes: H04L 49/508 : Head of Line Blocking Avoidance
• CPC Class Codes: H04L 49/90 : Buffering arrangements
• CPC Class Codes: H04L 9/40 : Network security protocols
• CPC Class Codes: Y02D 30/50 : in wire-line communication networks, e.g. low power modes or reduced link rate

Abstract

A method for establishing a virtual channel between network devices is disclosed. In the case of a local network device establishing a virtual channel with a remote network device, a virtual channel request message is sent from the local network device to the remote network device. A virtual channel acknowledgement message and a remote capability list are received and a virtual channel resume message and a local capability list are sent. The virtual channel is then enabled. In the case of a remote network device establishing a virtual channel with a local network device, a virtual channel request message is received from a local network device by a remote network device. A virtual channel acknowledgement message and a remote capability list are sent and a virtual channel resume message and a local capability list are received. The virtual channel is then enabled.

Claims

1-24. -24. (canceled)

25. A method for controlling flow between network devices, the method comprising:

receiving a flow message from at least one of a plurality of first network devices by a second network device, the flow message indicating congestion at the at least one first network device;

receiving an Ethernet frame by the second network device, wherein the Ethernet frame is interpreted as a pause frame if the second network device has not acknowledged an ability to establish a logical connection between network devices over a physical connection;

halting, by the second network device, transmission of selected packets associated with the flow message; and

continuing transmission, by the second network device, of packets not associated with the flow message.

26. The method of claim 25, wherein the flow message includes a flow identifier and halting further comprises suspending transmission of the selected packets associated with the flow identifier.

27. The method of claim 25, wherein the flow message identifies priority information of the packets, and halting further comprises suspending transmission of the selected packets associated with the priority information.

28. The method of claim 27, wherein the at least one first network device comprises a switch and wherein the second network device is connected to the switch and transmits packets to the switch for forwarding to a plurality of network devices connected to the switch.

29. The method of claim 27, wherein the flow message further includes a criterion for resuming transmission and wherein transmission of the selected packets associated with the flow message is resumed when the criterion for resuming transmission is satisfied.

30. The method of claim 29, wherein the criterion is time duration for a selective halt.

31. The method of claim 26, wherein suspending transmission includes resuming transmission of the selected packets associated with the flow message when an indication is received that the congestion at the at least one first network device is reduced.

32. A network device comprising:

at least one processor operable to;

receive a flow message from a switch, wherein the flow message indicates congestion in at least one logical channel;

receive an Ethernet frame that is interpreted as a pause frame if the switch does not acknowledge an ability to establish a logical connection between network devices over a physical connection;

halt transmission of selected packets associated with the flow message; and

continue transmission of packets not associated with the flow message.

33. The network device of claim 32, wherein the flow message identifies priority information of the packets, and halting further comprises selectively excluding selected packets associated with the priority information.

34. The network device of claim 33, wherein the network device is a server.

35. A network device that is able to establish a logical connection between network devices over a physical connection, the network device comprising:

a plurality of electrical boundaries for transmitting and receiving data and being configured to establish a logical channel between the network device and one or more other network devices, wherein the other network devices are able to establish a logical connection between network devices over a physical connection; and

a record of local operations, wherein the record of local operations indicates operations that the network device is able to perform locally, wherein the network device is configured to transmit the record of local operations via the logical channel, wherein the record of local operations provides priority information related to data associated with the network device, wherein the priority information enables a selective flow control of transmitted and received data between the network device and the other network devices, wherein the network device transmits an Ethernet frame that is interpreted as a pause frame after at least one of the other network devices does not acknowledge the ability to establish a logical connection between network devices over a physical connection.

36. The network device of claim 35, wherein the network device comprises a record of remote operations, wherein the record of remote operations indicates whether at least one of the other network devices can perform selective flow control of the transmitted and received data.

37. The network device of claim 36, wherein the record of local operations indicates that the network device can generate selective priority flow control frames.

38. The network device of claim 37, wherein the record of remote operations indicates whether at least one of the other network devices can obey selective priority flow control frames.

39. The network device of claim 38, wherein the established logical channel permits a flow message to be transmitted between network devices, the flow message indicating congestion at one of the network devices.

40. A switch configured to establish a logical channel between network devices, the switch comprising:

a plurality of ports, at least one of the plurality of ports being configured with the capability to process a first flow control message having priority information received by the port, to halt transmission on the port of packets associated with the priority information while continuing to transmit packets not associated with the first flow control message to the port, and

the port being further configured with the capability to send at least one other flow control message having priority information to devices connected to the switch, and wherein the port sends an Ethernet frame that is interpreted as a pause frame after at least one network device does not acknowledge the ability to establish a logical connection between network devices over a physical connection.

41. The switch of claim 40, wherein the switch is configured to detect memory utilization by packets associated with at least one of the priority information and an ingress port.

42. The switch of claim 40, wherein the switch is configured to send the flow control message based on the occurrence of a criterion at one of the plurality of ports.

43. The switch of claim 40, wherein the switch is configured to send the flow control message based on the occurrence of a criterion at one of the plurality of ports.

44. The switch of claim 40, wherein the switch is configured to send a flow control message having priority information to the ingress port when memory utilization exceeds a threshold.

45. An end node configured to establish a logical connection between network devices over a physical connection, the end node comprising:

at least one port configured with the capability to process a first flow control message having priority information received by the port, to halt transmission on the port of packets associated with the priority information while continuing to transmit packets not associated with the first flow control message, and to send at least one other flow control message having priority information to the network devices connected to the end node,

wherein the end node receives an Ethernet frame that is interpreted as a pause frame from a network device that is not able to establish a logical connection between network devices over a physical connection.

46. The end node of claim 45, wherein the end node is configured to detect memory utilization by packets associated with at least one of the priority information and an ingress port.