New! View global litigation for patent families

US20040062200A1 - Packet storm control - Google Patents

Packet storm control Download PDF

Info

Publication number
US20040062200A1
US20040062200A1 US10261258 US26125802A US2004062200A1 US 20040062200 A1 US20040062200 A1 US 20040062200A1 US 10261258 US10261258 US 10261258 US 26125802 A US26125802 A US 26125802A US 2004062200 A1 US2004062200 A1 US 2004062200A1
Authority
US
Grant status
Application
Patent type
Prior art keywords
packets
designated
interval
device
value
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
US10261258
Other versions
US7274665B2 (en )
Inventor
Vijay Kesavan
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Intel Corp
Original Assignee
Intel Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic regulation in packet switching networks
    • H04L47/10Flow control or congestion control
    • H04L47/32Packet discarding or delaying
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic regulation in packet switching networks
    • H04L47/10Flow control or congestion control
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic regulation in packet switching networks
    • H04L47/10Flow control or congestion control
    • H04L47/11Congestion identification
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic regulation in packet switching networks
    • H04L47/10Flow control or congestion control
    • H04L47/15Flow control or congestion control in relation to multipoint traffic
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic regulation in packet switching networks
    • H04L47/10Flow control or congestion control
    • H04L47/28Flow control or congestion control using time considerations
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic regulation in packet switching networks
    • H04L47/10Flow control or congestion control
    • H04L47/29Using a combination of thresholds

Abstract

A system and method of packet storm control includes a storm control device configured to count designated packets and drop any such packets that are in excess of a threshold value per a specified time internal. The packet storm control system and method may be implemented with both ingress and egress designated packet traffic. A user may provide a maximum percentage of line speed for designated packet traffic, and the storm control device may determine an appropriate threshold value in response.

Description

    BACKGROUND
  • [0001]
    1. Technical Field
  • [0002]
    The system and method described herein relate to packet storm control in a network.
  • [0003]
    2. Discussion of the Related Art
  • [0004]
    Computer networks provide a variety of means for transmitting electronic data packets. In conventional unicast networking, packets are transmitted via a network between two devices; each device having a particular network address. A one-to-one relationship is maintained between these two devices for the duration of a session. Broadcast networking operates similarly, insofar as packets are transferred directly from one device to another, yet rather than being transmitted to and received by only one device, broadcast packets are transmitted to and received by all devices on a network.
  • [0005]
    In multicast networking, network traffic does not travel from one device directly to another. Rather, packets are transmitted from a device to an address that is contained within a lookup table in a switching device, such as a router or switch. A multicast client situated on the network may notify the router that it desires to receive the multicast stream, and, when so informed, the router replicates the traffic and transmits it to that client, and to any other client that similarly joins the session. In this fashion, multiple devices situated on a network may receive particular multicast packets transmitted thereupon, yet other devices situated on the same network may not be in receipt of the same packets.
  • [0006]
    Excessive broadcast and multicast packets may be detrimental to network performance, because every device residing on the network may process each broadcast and multicast packet. In addition, if packets from a specific device or a specific group of device produce an excessive amount of packets, network performance may also be degraded. Also, destination unresolved unicast packets may degrade network performance. A destination unresolved unicast packet is a packet in which the destination address does not have an address in the lookup table, and thus the switching device does not know where to transmit the packet. The switching device receives the destination unresolved unicast packet and transmits it to devices residing on a virtual local area network with the switching device. If large numbers of devices are present on the VLAN, excessive packet traffic may occur and degrade network performance.
  • [0007]
    Additional processing overhead required by either broadcast packets, multicast packets, destination unresolved unicast packets or excessive packets from a device or group of devices may cause a device to deny services or drop incoming packets from other devices. This occurrence may be called a packet storm, e.g., a broadcast storm or a multicast storm.
  • [0008]
    Unlike unicast packets, multicast packets can be identified by an odd value in the first bit of the first byte of the destination Media Access Control (“MAC”) address. Broadcast packets are identified as having all ones in the destination MAC address. If a device or group of devices are transmitting excessive packets, the packets can be identified by the originating/transmitting device address in the MAC address. By recognizing these distinctions among various packet types, a suppression system may be established to implement packet storm control.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • [0009]
    [0009]FIG. 1 illustrates a storm control device in a communications network according to an embodiment of the present technique;
  • [0010]
    [0010]FIG. 2 illustrates a storm control device according to an embodiment of the storm control technique;
  • [0011]
    [0011]FIG. 3a illustrates a flowchart of an algorithm to determine a threshold value, in terms of a number of frames/packets when a percentage of line speed is entered, according to an embodiment of the storm control method and apparatus;
  • [0012]
    [0012]FIG. 3b illustrates a flowchart of an algorithm to determine a threshold value, in terms of bytes when a percentage of line speed is entered according to an embodiment of the present invention;
  • [0013]
    [0013]FIG. 4 illustrates the operation of line speed adjustment module and a timing adjustment module according to an embodiment of a storm control apparatus and method;
  • [0014]
    [0014]FIG. 5 illustrates a flowchart of the operation of an embodiment of storm control apparatus and method for one port; and
  • [0015]
    [0015]FIG. 6 illustrates an alternative operation of an embodiment of a storm control apparatus and method for one port.
  • DETAILED DESCRIPTION
  • [0016]
    A storm control apparatus or method may be implemented to reduce the likelihood of packet storms, e.g., broadcast storms, multicast storms or destination unresolved unicast storms. The storm control apparatus or method may limit the bandwidth that broadcast packet traffic, multicast packet traffic, a combination of other broadcast/multicast packet traffic, destination unresolved unicast traffic, or any designated packet traffic occupies, thereby reducing the stifling of regular unicast traffic. The storm control apparatus or method may be implemented when a device receives packets (ingress) or when a device transmits packets (egress). Although the storm control apparatus or method is described in terms of controlling broadcast traffic or multicast traffic, the device may be utilized to control any type of designated packet traffic to eliminate bandwidth bottlenecks. For example, if packets sent from a specific network address, i.e., device, or group of network addresses, i.e., devices, are stifling traffic within a packet switching device, a storm control apparatus or method may be utilized to reduce/minimize the effect of the packets sent from the designated device or group of designated devices. Thus, designated packets may include broadcast packets, multicast packets, a combination of broadcast or multicast packets, destination unresolved unicast packets, or other types of specifically designated packets. In this application, packets or frames may be used interchangeably, in that the storm control device may be counting the number of frames or packets.
  • [0017]
    [0017]FIG. 1 illustrates a storm control device in a communications network according to an embodiment of the present technique. As depicted in FIG. 1, a computing device 101 is in electronic communication with at least one other computing device 102 over a communications network 103. The computing device 101 may be a local area network switch, a router, or any other similar device transmitting or receiving packets over the communications network 103. The computing device 101 may include a storm control device 110, a forwarding device 112, a media access control (MAC) layer 114, a physical layer 116, at least one port 106, 107, 108, and a memory 124. The computing device 101 may receive packets over the communications network 103 via the at least one port 106, 107, and 108. The physical layer 116 may provide an interface for the at least one port 106, 107, 108 to the media access control layer 114.
  • [0018]
    The packets may be transmitted from the at least one port 106, 107, 108, through the physical layer 116 to the media access control layer 114. In one embodiment, the storm control device 110 may receive the packets from the media access control layer 114 and may decide, based on the number of designated packets (e.g., multicast packets, broadcast packets, destination unresolved unicast packets, or combination of multicast and broadcast packets) within the received packets, to drop the designated packets until a time interval expires. This may be referred to as ingress storm control. In one embodiment of the present invention, the remaining packets may be stored in a memory 124 before they are transferred to the storm control device 110 from the MAC layer 114. The remaining packets, i.e., packets not dropped by the storm control device 110, within the received packets may be forwarded to the forwarding device 112. The forwarding device 112 may decide which other computing device 102 will receive the remaining packets and may determine a selected port 106, 107 or 108 to which the remaining packets should be transmitted in order to be transmitted to the other computing device 102.
  • [0019]
    In an embodiment, the forwarding device 112 may first transmit the packets bound for a selected port 106, 107, and 108 through the storm control device 110. This may be referred to as egress storm control. In an alternative embodiment, the forwarding device 112 may transmit the packets bound for a selected port 106, 107, and 108 directly through the media access control layer 114 to the physical layer 116 to the selected port 106, 107 or 108. In the embodiment where the forwarding device 112 transmits the packets bound for a selected port 106, 107, or 108 through the storm control device 110 for egress storm control, the storm control device 110 may decide, as discussed previously, to drop some of the packets being sent to the selected port 106, 107, or 108 based upon the number of designated packets, e.g., broadcast packets, multicast packets, destination unresolved unicast packets, or combination or broadcast & multicast packets, within the transmitted packets. In this embodiment, the storm control device 110 may then transmit the remaining packets to the selected port 106, 107, or 108 through the media access control layer 114 and the physical layer 116.
  • [0020]
    The media access control layer 114, the forwarding device 112, and the storm control device 110 may be located on a single physical structure. Illustratively, the single physical structure may be an application specific integrated circuit (ASIC). The memory 124 may also be located on a single physical structure with the storm control device 110, the MAC layer 114, and the forwarding device 112. In an alternative embodiment, the MAC layer 114, the forwarding device 112, and the storm control device 110 may be located on two or three separate physical structures.
  • [0021]
    [0021]FIG. 2 illustrates a storm control device 110 according to an embodiment of the storm control technique. A single storm control device 110 may be configured to handle one or may be configured to handle multiple ports 106, 107 and 108. In an alternative embodiment, a plurality of storm control devices (not shown) may be included with each storm control device 110 controlling one of the multiple ports 106, 107, and 108. The storm control device 110 may be configured to monitor and react to both the receiving of packets (ingress) or the transmitting of packets (egress). Alternatively, one storm control device 110 may be configured to monitor and react to the incoming packets while a second storm control device (not shown) may be configured to monitor and react to the packets being transmitted, i.e., outgoing packets.
  • [0022]
    As depicted in FIG. 2, the ports 106, 107 and 108 interfacing with the storm control device 110 may include both incoming (e.g., 106) and outgoing (e.g., 107) ports; although an alternative embodiment may include one port or multiple ports (e.g., 108) configured as both an incoming and outgoing port. Designated packets, e.g., broadcast packets, multicast packets, destination unresolved unicast packets, or a combination of broadcast and multicast packets, contained in general data may be received or alternatively transmitted by each port 106, 107 and 108, depending upon whether the port is an incoming, outgoing, or bi-directional port. For example, if port 106 is an ingress port, the storm control device 110 may enable ingress storm control and monitor and react to any designated packets received into port 106 from the network. Illustratively, if port 107 is an egress port, the storm control device 110 may enable egress storm control and monitor and react to any packets being transmitted to port 107 which were transmitted from another port, for example port 106 or port 108 after going through the forwarding device 112.
  • [0023]
    In one embodiment, a separate threshold value, in terms of number of packets or frames, and a separate time interval may be input to the storm control device 110 for each port 106, 107 and 108, respectively. Alternatively, one threshold value may be input to a storm control device 110 and applied to all of the ports 106, 107, and 108. In another embodiment, one time interval may be input to the storm control device 110 and applied to all of the ports 106, 107, and 108. The threshold value(s) and time value(s) may be either input by a system user, may be stored in the memory 124 of the computing device 102, or may be stored in a memory (not shown) of the storm control device 110.
  • [0024]
    A plurality of counters 115, 117, 119 i, and 119 e may be further included with each port 106, 107, and 108 having a counter responsible for monitoring and reacting to packet flow, respectively, to determine the number of incoming or outgoing designated packets for the corresponding port 106, 107 and 108, respectively. The plurality of counters 115, 117, 119 i, or 119 e may only monitor one of the receipt or transmission of designated packets, and not both. Thus, if a port is utilized for both receipt (ingress) and transmission (egress), and ingress and egress storm control are both enabled, two counters 119 i and 119 e may be needed with one counter 119 i counting either the number of or the byte count value of designated packets in the received packets and the other counter 119 e counting either the number of or the byte count value of designated packets in the transmitted packets.
  • [0025]
    In one embodiment, a plurality of timing modules 116, 118 and 120 may be included to mark the passage of the separate time interval for each port 106, 107 and 108, respectively. In the embodiment where one time interval may be applied to all the ports 106, 107, and 108, one timing module (not shown) may be included to mark the passage of time for all the ports 106, 107, and 108. In an alternative embodiment of the present invention, a separate timing module (not shown) may be applied for ingress traffic from port 108 and a separate timing module (not shown) may be applied for egress traffic to port 108.
  • [0026]
    A separate threshold value may be input for each port 106, 107 and 108, respectively, during the associated time interval. In an alternative embodiment, one threshold value may be utilized for all of the ports 106, 107, and 108. Alternatively, if a port has both ingress and egress storm control enabled, an ingress threshold value may be set and a separate egress threshold value may be set.
  • [0027]
    During operation, the plurality of counters 115, 117,119 i, and 119 e may determine whether the threshold value of designated packets, e.g., broadcast packets, multicast packets, destination unresolved unicast packets, or a combination of broadcast/multicast packets, has been exceeded in the packets received or, alternatively, transmitted in the configured time interval by each port 106, 107 and 108, respectively. Illustratively, storm control may be enabled for the receiving, i.e., ingress, of packets, the threshold value may be 70 designated packets, and the time interval may be one millisecond. Thus, in this example, if more than 70 designated packets are received and counted by the selected port before the time interval of one millisecond expires, any more designated packets received by the selected port may be dropped during the time interval of one millisecond. Once the time interval expires, i.e., one millisecond has elapsed, designated packets received by the selected port may be allowed to proceed through the storm control device 110. As discussed previously, multicast packets may be identified by an odd value in the first byte of the destination MAC address. Broadcast packets may be identified because they have a value of 1 in all bits of the destination MAC address. Other designated packets may be identified by the origination or sending address included in the packet. Destination unresolved unicast packets may have addresses which do not have a forwarding value in a lookup table.
  • [0028]
    In one embodiment, if a port is used to both receive and to transmit a packet, then an egress counter 119 e and an ingress counter 119 i may be utilized for one port 108, as illustrated in FIG. 2, to determine if the threshold value of designated packets has been exceeded in the transmitted packets (egress counter 119 e) or the received packets (ingress counter 119 i).
  • [0029]
    When the number of designated packets either received or, alternatively, transmitted by a particular port 106, 107 or 108 reaches the configured threshold value in the configured time interval, respectively, the storm control device 110 may drop the designated packets, e.g., broadcast, multicast, destination unresolved unicast packets, or a combination of broadcast and multicast packets, contained in general data for the remainder of the time interval identified for that particular port 106, 107 or 108. Once the time interval has expired for the associated port 106, 107 or 108, the storm control device 110 may again allow the receipt or, alternatively, transmittal of designated packets contained in general data for the associated port 106, 107 or 108.
  • [0030]
    In alternative embodiments of the present invention, different types of designated packet traffic, i.e., broadcast packet traffic, multicast packet traffic, destination unresolved unicast traffic, etc., may have separate threshold values, a separate counter, and a separate timing module. In an embodiment of the invention where different types of designated packet traffic has separate threshold values, counters and timing modules, a port 107 may have multiple threshold values applied to it, multiple counters (each controlling one type of designated packet traffic), and multiple timing modules, each controlling one type of designated packet traffic. For example, if a port 107 has egress control activated for both broadcast and multicast traffic, the port 107 may include two counters, with one for egress control of broadcast traffic and the other for egress control of multicast traffic. The port 107 may also include two timing modules with one for egress control of broadcast traffic and one for egress control of multicast traffic.
  • [0031]
    In another embodiment, a separate lower threshold value may also be established for each of the particular ports 106, 107, or 108 in addition to the original, i.e., higher threshold value. Alternatively, one lower threshold value may be established for all of the particular ports 106, 107, or 108. In another alternative embodiment, one lower threshold value may be established for ingress control on a particular port 106, 107, or 108 and a second lower threshold value may be established for egress control on the particular port 106, 107, or 108. The lower threshold value may be established by the user or may be automatically input to the storm control device 110, as discussed previously.
  • [0032]
    If during the immediately preceding time interval the upper threshold was exceeded, then during the time interval, i.e., the current time interval, the storm control device 110 may drop all designated packets, e.g., broadcast packets, multicast packets, destination unresolved unicast packets, or a combination of broadcast or multicast packets, for the current time interval. This may occur even though the original or higher threshold value was not exceeded in the current time interval. If the lower threshold was not exceeded during the current time interval, the storm control device 110 may allow designated packets to pass through without being dropped starting with the next time interval. If the lower threshold was exceeded during the current time interval, the storm control device may continue to drop all designated packets for the next time interval. This determination may be made for each succeeding time interval. This may prevent a constant cycle of dropping and not dropping packets when the number of designated packets or byte count value hovers near the upper threshold value. The storm control device 110 may continue to drop designated packets until the number of or the byte count value of the designated packets dropped during the time interval falls below the lower threshold value.
  • [0033]
    For example, if 32 designated packets were counted in the immediately preceding time interval, e.g., t1, the lower threshold value is 30 designated packets, and the upper threshold was exceeded in a prior time interval, e.g., t0, the storm control device 110 may continue to drop each designated packet in the current time interval, e.g., t2. The dropping of designated packets may continue to occur until a time interval occurs when less than 30 designated packets are counted during the time interval. Thus, if in the next time interval, e.g., t3, only 20 designated packets are counted, then in time interval t4 packets may no longer be dropped by the storm control device 110.
  • [0034]
    The storm control device 110 may also generate an event message when a specific event occurs. In one embodiment of the present invention, the event message may be an interrupt sent to the processor of the computing device 101. In an alternative embodiment of the present invention, the event message may be a Simple Network Management Protocol (SMNP) trap sent to a central device monitoring the communications network 103. An event generator 130 may generate one type of event message for a particular port 106, 107, or 108 if the threshold value is exceeded in the time interval but the threshold value was not exceeded in the immediately preceding time interval. The event generator 130 may generate a second type of event message for a particular port 106, 107, or 108, if the threshold value is not exceeded in the time interval but the threshold value was exceeded in the immediately preceding time interval.
  • [0035]
    Storm control may be also performed utilizing a threshold value based upon a number of byte count values of designated data, rather than a number of frames or packets, either transmitted from or received with general data by a computing device 102. In this embodiment, the plurality of counters 115, 117,119 i, and 119 e may increment once for each byte count value amount of designated data. The byte count value may be set to any appropriate value, although it generally ranges from 64 bytes to 1518 bytes. However, the byte count value may also be incremented by one byte. The byte count value for each port may have a default value of 64 bytes. For example, if 128 bytes are received by a port 106 and the byte count value is 64, the counter 115 associated with the port 106 may increment twice. A time interval may also be input for each port 106, 107, and 108, respectively, as described above. A timing module 116, 118 and 120 may further be included in the storm control device 110, for each port 106, 107, or 108, respectively, to mark the passage of the associated time interval for the associated port 106, 107, or 108.
  • [0036]
    For example, ingress storm control may be based on a number of segments, in this example 64-byte blocks, and the threshold value may be 20 64-byte segments. Segment size is configurable and may be 1, 64, 128, or 256-bytes in length. In this embodiment, the plurality of counters 115, 117, 119 i, or 119 e in the storm control device 110 may increment for each segment, i.e., 64-byte chunk of designated data, received on the selected port. Illustratively, if 1,280 bytes of designated data or 20 64-byte segments are counted by the one of the plurality of counters 115, 117, 119 i, or 119 e, then the remaining designated data for the associated time interval may be dropped by the storm control device.
  • [0037]
    The counter 115, 117, 119 i, or 119 e of the storm control device 110 may increment once for each byte count value of designated data (e.g., broadcast data, multicast data, destination unresolved unicast data, or a combination of broadcast and multicast data) contained in the general data received, or alternatively transmitted by each port 106, 107 and 108, respectively. When the counter 115, 117, 119 i, or 119 e reaches its configured threshold value in terms of byte count value during a time interval for a particular port 106, 107 and 108, respectively, the storm control device 110 may drop the designated data contained in the general data for the remainder of the time interval for that particular port 106, 107 or 108. Once the time interval has expired for that port 106, 107 or 108, the storm control device 110 may again allow the receipt or, alternatively, transmittal of designated data contained in general data for that port 106, 107 or 108.
  • [0038]
    In many circumstances, inputting a number of packets or a number of bytes and a byte count value may not easily understood. Instead, a maximum percentage of line speed may be input as the threshold value, e.g., 15% of the receiving line speed, the receiving line speed being 10 Mbps. The storm control device may include an algorithm to convert the percentage of line speed threshold value to a number of packets/frames threshold value or a byte count value threshold value. FIG. 3a illustrates a flowchart of an algorithm to determine a threshold value, in terms of a number of frames/packets when a percentage of line speed is entered, according to an embodiment of the storm control method and apparatus. The implementation of this algorithm is below. This feature may impart a user-friendly aspect to the present invention; because maximum percentage of line speed is generally a value more easily understood and readily known by a user than is the maximum number of designated packets or a specific byte count of designated data for a particular port.
  • [0039]
    A maximum percentage of line speed for designated data, i.e., broadcast data, multicast data, destination unresolved unicast data, or a combination of broadcast and multicast data, may be input by a user (or otherwise set by the system), and this value may then be converted to a threshold value. The packet size of packets being transmitted from, or alternatively, received by the system and the time interval discussed above may also be input as well. The port or line characteristics (e.g., line speed, inter-packet gap, etc.) may also be recognized by the system, and are accounted for by implementation of the following algorithm, which converts the maximum percentage of line speed to a threshold value in terms of number of packets.
  • [0040]
    With reference to FIG. 3a, first, the packet size (i.e., generally ranging from 64 bytes to 1518 bytes) is converted 301 from byte units to a number of bits (“NOB”), i.e., 8 bits represent a byte. The 8-byte preamble is accounted for, and the units converted, as follows:
  • NOB=8(bits/byte)×(packet size+8 byte preamble)
  • [0041]
    Second, the inter-packet gap is added to the NOB, generating 302 a full interval NOB (“NOBF”). The inter-packet gap is a function of line speed, and is combined with the NOB, as follows:
  • NOBF=NOB+(Inter-packet gap)
  • [0042]
    Third, the line speed is divided 303 by the NOBF to generate the maximum packet rate through the port, as follows: packet rate MAX = port speed ( bits / sec ) NOB F
    Figure US20040062200A1-20040401-M00001
  • [0043]
    Fourth, the maximum designated packet rate is calculated 304 by multiplying the maximum packet rate of the port by the maximum percentage of line speed for designated data, as follows:
  • packet rateB/M=packet rateMAX(percentage line speedB/M)
  • [0044]
    Finally, the threshold value is determined 305 by multiplying the time interval (the time interval has to be in seconds) with the maximum designated data rate, as follows:
  • threshold value=packet rateB/M(time interval)
  • [0045]
    [0045]FIG. 3b illustrates a flowchart of an algorithm to determine a threshold value, in terms of bytes, when a percentage of line speed is entered as a threshold value according to an embodiment of the present invention. The number of bits per second may be generated 310 by multiplying the % of line speed threshold value by the line speed and dividing by 100. The number of bytes per second may be generated 311 by dividing the number of bits per second by eight. The threshold value in bytes for a given time interval may be calculated 312 by multiplying the given time interval by the number of bytes per second.
  • [0046]
    [0046]FIG. 4 illustrates the operation of line speed adjustment module and a timing adjustment module according to an embodiment of the storm control apparatus and method. In one embodiment, the timing interval may be modified according to a line speed entering of one of the ports 106, 107, or 108. A line speed adjustment module 140 may modify the line speed of a port in order for the port to receive information from a port on another computing device in an optimal manner. This may be referred to as auto-negotiation between the ports. The line speed adjustment module 140 may provide the adjusted line speed information to a timing adjustment module 150. In one embodiment, the timing adjustment module 150 may modify the time interval according to the adjusted line speed information and provide this information to one of the plurality of timing modules 116, 118, 120 established for one of the ports 106, 107, 108, respectively. If the threshold value remains the same, i.e., the same number of designated packets or the same number of byte count values, the time window may need to be scaled to compensate for the increased or decreased line speed. For example, if the time interval is 10 msec, the threshold value is 70 designated packets, and the line speed increases from 10 Mbps to 100 Mbps, the time interval may be decreased to 1 msec if the threshold value remains at 70 designated packets.
  • [0047]
    [0047]FIG. 5 illustrates a flowchart of the operation of an embodiment of storm control apparatus and method for one port. A threshold value, and a time interval may be set 501 by the user for the port, as described above. Input of the threshold value may be performed indirectly by the user inputting a maximum packet count of designated packets, e.g., broadcast data, multicast data, destination unresolved unicast data, or the combination of broadcast/multicast data. A timing module and a counter may then be simultaneously started 502; the timing module marking the passage of the time interval, and the counter tallying either the number of packets that are either received by or transmitted towards the port. As described above, the counter is only counting either the received or the transmitted packets and not both. If the number of designated packets, e.g., broadcast packets, multicast packets, destination unresolved unicast packets, or the combination of broadcast & multicast packets, that are either received or transmitted by the port reaches the threshold value during a time interval (i.e., condition 503 is achieved), the storm control device drops 504 all designated packets until the time interval expires (i.e., condition 505 is achieved). If, however, the number of designated packets received, or alternatively transmitted by the port does not reach the threshold value (i.e., condition 503 is not achieved before condition 505 is achieved), then when the time interval expires (i.e., condition 505 is achieved), both the timing module and the counter are reset and restarted 502; and no broadcast data, multicast data, or combination of broadcast/multicast data has been dropped 504 by the storm control device.
  • [0048]
    [0048]FIG. 6 illustrates an alternative operation of an embodiment of a storm control apparatus and method for one port. An upper threshold value, a lower threshold value, and a time interval may be set 601 by the user for the port, as described above. Input of the upper threshold value and the lower threshold value may be performed as detailed above. A timing module and a counter may then be simultaneously started 602; the timer marking the passage of the time interval, and the counter tallying either the number of packets, frames, segments, or bytes that are received or alternatively transmitted by the port. As described above, the counter is only counting either the received or the transmitted packets and not both. If the number of designated packets, e.g., broadcast packets, multicast packets, destination unresolved unicast packets, or the combination of broadcast & multicast packets, that are received or, alternatively, transmitted by the port exceeds the upper threshold value during a time interval (i.e., condition 603 is achieved), or if a prior interval drop indicator was set in an immediately preceding timing interval (i.e., condition 604 is achieved), the storm control device will drop 605 all subsequent designated packets, until the time interval expires (i.e., condition 606 is achieved). After the time interval expires (i.e., condition 606 is achieved), if the lower threshold value was exceeded 607, the prior interval drop indicator is set 608 and both the timing module and counter are reset and restarted 602. If the lower threshold value is not exceeded 607 before condition 606 is achieved, then when the time interval expires (i.e., condition 606 is achieved), the prior interval drop indicator is zeroed out and both the timing module and the counter are reset and restarted 602.
  • [0049]
    For example, if the upper threshold value is 50 designated packets, the lower threshold value is 30 designated packets, and the number of designated packets received during a time interval t0 is 60, then the prior interval drop indicator may be set. For time interval t1 the number of designated packets counted may be 32 designated packets. In time interval t1 all designated packets may be dropped because the prior drop indicator has been set, condition 604. Because the lower threshold value has been exceeded, condition 607, the prior interval drop indicator remains set. In time interval t3, the number of designated packets counted may be 20 designated packets. In time interval t3, all designated packets may be dropped because the prior interval drop indicator was set. After the expiration of time interval t3, the storm control device may determine the lower threshold value was not exceeded for time interval t3 and may zero the prior interval drop indicator. Thus, in time interval t4, because the prior interval drop indicator has been zeroed, designated packet traffic may not be dropped unless the upper threshold value is exceeded.
  • [0050]
    While the description above refers to particular embodiments, it will be understood that many modifications may be made without departing from the spirit thereof The accompanying claims are intended to cover such modifications as would fall within the true scope and spirit of the storm control method and apparatus. The presently disclosed embodiments are therefore to be considered in all respects as illustrative and not restrictive, of the scope of the storm control method and apparatus being indicated by the appended claims, rather than the foregoing description, and all changes that come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein.

Claims (47)

    What is claimed is:
  1. 1. A storm control device, comprising:
    a counter to tally a number of designated packets received during a time interval; and
    a timing module to mark passage of said time interval;
    wherein said storm control device halts receipt of designated packets when said number of designated packets reaches a threshold value during said time interval.
  2. 2. The storm control device of claim 1, wherein the counter tallies a number of byte count values of designated data received during said time interval and the storm control device halts receipt of said designated data when said number of byte count values reaches a threshold value during said time interval.
  3. 3. The storm control device of claim 1, wherein said designated packets are selected from one of a group of broadcast packets, multicast packets, destination unresolved unicast packets, and a combination of broadcast packets and multicast packets.
  4. 4. The storm control device of claim 1, wherein said counter and said timing module are reset to zero at completion of said time interval.
  5. 5. The storm control device of claim 1, further including a timing adjustment module to scale said time interval based on a receiving line speed.
  6. 6. The storm control device of claim 1, further including logic to calculate said threshold value of designated packets from a specified maximum percentage of receiving line speed.
  7. 7. The storm control device of claim 1, further including an event generator to generate an event message when said threshold value is exceeded in said time interval but was not exceeded in an immediately preceding time interval, or if said threshold value was not exceeded in said time interval but was exceeded in said immediately preceding time interval.
  8. 8. The storm control device of claim 7, wherein said event message is an interrupt or a Simple Network Management Protocol trap.
  9. 9. The storm control device of claim 1, further including logic allowing said storm control device to count destination unresolved packets as said designated packets.
  10. 10. A storm control device, comprising:
    a counter to tally a number of designated packets transmitted during a time interval; and
    a timing module to mark passage of said time interval;
    wherein said storm control device halts transmission of designated packets when said number of designated packets reaches a threshold value during said time interval.
  11. 11. The storm control device of claim 10, further including a timing adjustment module to scale said time interval based on a transmitting line speed.
  12. 12. The storm control device of claim 10, further including logic to calculate said threshold value of designated packets from a specified maximum percentage of transmitting line speed.
  13. 13. The storm control device of claim 10, further including an event generator to generate an even t message when a specified event occurs.
  14. 14. A system to control ingress of designated packets, comprising:
    a port to receive data, said data including said designated packets; and
    a storm control device to receive said data from said port including,
    a counter to tally a number of designated packets received by said port during a time interval; and
    a timing module to mark passage of said time interval,
    wherein said control device halts receipt of said designated packets when said number of designated packets reaches a threshold value during said time interval.
  15. 15. The system of claim 14, wherein the counter tallies a number of byte count values of designated data received during said interval and the storm control device halts receipt of said designated data when said number of byte count values reaches a threshold value during said time interval.
  16. 16. The system of claim 15, further including at least two ports, each of said at least two ports being either an ingress port, an egress port, or a combination ingress egress port.
  17. 17. The system of claim 16, further including a separate timing module for each of said at least two ports which measures a unique time interval for each of said at least two ports.
  18. 18. The system of claim 16, further including a separate counter for each of said at least two ports.
  19. 19. The system of claim 16, wherein each of said at least two ports could have a different threshold value.
  20. 20. The system of claim 16, further including two separate counters for any combination ingress egress port.
  21. 21. The system of claim 16, further including a forwarding device and a Media Access Control (MAC) layer, said MAC layer to assist to connect said storm control device and said forwarding device to each of said at least two ports.
  22. 22. The system of claim 21, wherein said storm control device, said forwarding device, and said MAC layer are located within a single physical device.
  23. 23. The system of claim 22, wherein a physical layer device interfaces the media access control layer to each of said at least two ports.
  24. 24. A system to control egress of designated packets, comprising:
    a forwarding device to transmit data, said data including said designated packets; and
    a storm control device to receive said data from said forwarding device, including,
    a counter to tally a number of designated packets transmitted from said forwarding device during a time interval; and
    a timing module to mark passage of said time interval,
    wherein said storm control device halts transmittal of said designated packets when said number of designated packets reaches a threshold value during said time interval.
  25. 25. The system of claim 24, wherein said counter tallies a number of byte count values of designated data transmitted from said forwarding device during said time interval and said storm control device halts transmittal of said designated data when said number of byte count values of designated data reaches a threshold value during said time interval.
  26. 26. The system of claim 24, further including at least two ports, wherein a separate timing module is established for each of said at least two ports.
  27. 27. The system of claim 24, further including at least two ports, wherein a separate counter is established for each of said at least two ports.
  28. 28. A method of preventing designated packet storms, comprising:
    selecting a time interval for at least one port;
    selecting a threshold value for said at least one port, said threshold value indicating a maximum number of designated packets received by said at least one port during said time interval;
    counting a total number of designated packets received by said at least one port during said time interval; and
    halting passage of designated packets when said total number of designated packets reaches said threshold value for said at least one port prior to expiration of said time interval.
  29. 29. The method of claim 28, further including allowing said designated packets to pass through said at least one port after said time interval has expired.
  30. 30. The method of claim 28, wherein selecting a threshold value in terms of number of designated packets for said at least one port, when a maximum percentage of receiving line speed for designated packets is input as said threshold value, includes,
    specifying a packet size,
    converting said packet size to bits, converting an 8-byte preamble to bits, and adding the two together to generate a number of bits;
    adding an inter-packet gap to said number of bits to generate a full interval number of bits;
    dividing said receiving line speed of said at least one port by said full interval number of bits to generate a maximum packet rate;
    multiplying said maximum packet rate by said maximum percentage of receiving line speed for said designated packets to generate a maximum designated packet rate; and
    multiplying said maximum designated packet rate by said time interval to generate said threshold value.
  31. 31. The method of claim 28, further including
    selecting a lower threshold value for said at least one port;
    continuing to halt passage of designated packets when said designated packets were dropped in an immediately preceding time interval because said lower threshold value was exceeded or said threshold value was exceeded.
  32. 32. A method of preventing designated packet storms, comprising:
    selecting a time interval for at least one port;
    selecting a threshold value for said at least one port, said threshold value indicating a maximum number of byte count values of designated data received by said at least one port during said time interval;
    counting a total number of byte count values of said designated data received by said at least one port during said time interval; and
    halting passage of said designated data when said total number of byte count values of said designated data reaches said threshold value for said at least one port prior to expiration of said time interval.
  33. 33. The method of claim 32, further including
    selecting a lower threshold value for said at least one port;
    continuing to halt passage of designated data through said at least one port in which said designated data was dropped in an immediately preceding time interval because said lower threshold value was exceeded or said threshold value was exceeded.
  34. 34. A method of preventing designated packet storms, comprising:
    selecting a time interval for at least one port;
    selecting a threshold value for said at least one port, said threshold value indicating a maximum number of designated packets to be transmitted to said at least one port from a forwarding device during said time interval;
    counting a total number of designated packets transmitted from said forwarding device during said time interval; and
    halting passage of designated packets when said total number of designated packets reaches said threshold value for said at least one port prior to expiration of said time interval.
  35. 35. The method of claim 34, further including
    selecting a lower threshold value for said at least one port; and
    continuing to halt passage of said designated packets when said designated packets were dropped in an immediately preceding time interval because said lower threshold value was exceeded or said threshold value was exceeded.
  36. 36. A method of preventing designated packet storms, comprising:
    selecting a time interval for at least one port;
    selecting a threshold value for said at least one port, said threshold value indicating the maximum number of byte count values of designated data transmitted from a forwarding device to said at least one port during said time interval;
    counting a total number of byte count values of said designated data transmitted by said forwarding device during said time interval that are directed to said at least one port; and
    halting passage of said designated data when said total number of byte count values of said designated data reaches said threshold value for said at least one port prior to expiration of said time interval.
  37. 37. The method of claim 36, further including,
    selecting a lower threshold for said at least one port; and
    continuing to halt passage of said designated data through said at least one port in which said designated data was dropped in an immediately preceding time interval because said lower threshold value was exceeded or said threshold value was exceeded.
  38. 38. A program code storage device, comprising:
    a machine-readable storage medium; and
    machine-readable program code, stored on the machine-readable storage medium, the machine-readable program code having instructions to:
    select a time interval for at least one port;
    select a threshold value for said at least one port, said threshold value indicating a maximum number of designated packets received by said at least one port during said time interval;
    count a total number of designated packets received by said at least one port during said time interval; and
    halt passage of designated packets when said total number of designated packets reaches said threshold value for said at least one port prior to expiration of said time interval.
  39. 39. The program code storage device of claim 38, further including instructions to
    select a lower threshold value for said at least one port; and
    continue to halt passage of designated packets when said designated packets were dropped in the immediately preceding time interval because said lower threshold value was exceeded or said threshold value was exceeded.
  40. 40. The program code storage device of claim 38, further including allowing said designated packets to pass through to said at least one port after said time interval has expired.
  41. 41. The program code storage device of claim 38, wherein selecting a threshold value in terms of number of designated packets for said at least one port, when a maximum percentage of receiving line speed for designated packets is input as said threshold value, includes further instructions to:
    specify a packet size,
    convert said packet size to a first set of bits, converting an 8-byte preamble to a second set of bits, and adding the first set of bits to the second set of bits to generate a number of bits,
    add an inter-packet gap to said number of bits to generate a full interval number of bits,
    divide a receiving line speed of said at least one port by said full interval number of bits to generate a maximum packet rate,
    multiply said maximum packet rate by said maximum percentage of receiving line speed for said designated packets to generate a maximum designated packet rate, and
    multiply said maximum designated packet rate by said time interval to generate said threshold value.
  42. 42. A program code storage device, comprising:
    a machine-readable storage medium; and
    machine-readable program code, stored on the machine-readable storage medium, the machine-readable program code having instructions to:
    select a time interval for at least one port;
    select a threshold value for said at least one port, said threshold value indicating a maximum number of byte count values of designated data received by said at least one port during said time interval;
    count a total number of byte count values of said designated data received by said at least one port during said time interval; and
    halt passage of said designated data when said total number of byte count values of said designated data reaches said threshold value of said at least one port prior to expiration of said time interval.
  43. 43. The program code storage device of claim 42, further including instruction to
    select a lower threshold value for said at least one port; and
    continue to halt passage of said designated data when said designated data was dropped in an immediately preceding time interval because said lower threshold value was exceeded or said threshold value was exceeded.
  44. 44. A program code storage device, comprising:
    a machine-readable storage medium; and
    machine-readable program code, stored on the machine-readable storage medium, the machine-readable program code having instructions to:
    select a time interval for at least one port;
    select a threshold value for said at least one port, said threshold value indicating a maximum number of designated packets to be transmitted to said at least one port from a forwarding device during said time interval;
    count a total number of designated packets transmitted from said at least forwarding device during said time interval; and
    halt passage of designated packets directed to said at least one port when said total number of designated packets reaches said threshold value for said at least one port prior to expiration of said time interval.
  45. 45. The program code storage device of claim 44 further including instructions to select a lower threshold value for said at least one port; and
    continue to halt passage of designated packets when said designated packets were dropped in the immediately preceding time interval because the lower threshold value was exceeded or the threshold was exceeded.
  46. 46. A program code storage device, comprising:
    a machine-readable storage medium; and
    machine-readable program code, stored on the machine-readable storage medium, the machine-readable program code having instructions to:
    select a time interval for at least one port;
    selecting a threshold value for said at least one port, said threshold value indicating the maximum number of byte count values of designated data transmitted from a forwarding device to said at least one port during said time interval;
    count a total number of byte count values of said designated data transferred from said forwarding device during said time interval that are directed to said at least one port; and
    halt passage of said designated data directed to said at least one port when said total number of byte count values of said designated data reaches said threshold value for each of said at least one port prior to expiration of said time interval.
  47. 47. A program code storage device of claim 46, further including instructions to:
    select a lower threshold for each of said at least one port; and
    continuing to halt passage of said designated data when said designated data was dropped in an immediately preceding time interval because said lower threshold was exceeded or said upper threshold values was exceeded.
US10261258 2002-09-30 2002-09-30 Packet storm control Expired - Fee Related US7274665B2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US10261258 US7274665B2 (en) 2002-09-30 2002-09-30 Packet storm control

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US10261258 US7274665B2 (en) 2002-09-30 2002-09-30 Packet storm control

Publications (2)

Publication Number Publication Date
US20040062200A1 true true US20040062200A1 (en) 2004-04-01
US7274665B2 US7274665B2 (en) 2007-09-25

Family

ID=32029927

Family Applications (1)

Application Number Title Priority Date Filing Date
US10261258 Expired - Fee Related US7274665B2 (en) 2002-09-30 2002-09-30 Packet storm control

Country Status (1)

Country Link
US (1) US7274665B2 (en)

Cited By (28)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050100020A1 (en) * 2003-11-12 2005-05-12 Akihiro Hata Packet switching device
US20050157647A1 (en) * 2004-01-21 2005-07-21 Alcatel Metering packet flows for limiting effects of denial of service attacks
US20050232150A1 (en) * 2003-06-03 2005-10-20 Kazuto Nishimura Flow control method and apparatus thereof
US20060018343A1 (en) * 2004-07-23 2006-01-26 Rodrigo Miguel D V Method for transmitting data packets between nodes of a communication network
US20060067231A1 (en) * 2004-09-27 2006-03-30 Matsushita Electric Industrial Co., Ltd. Packet reception control device and method
US20060092840A1 (en) * 2004-10-29 2006-05-04 Broadcom Corporation Intelligent fabric congestion detection apparatus and method
US20060126550A1 (en) * 2002-09-02 2006-06-15 Infineon Tecnnologies Ag Data switch and a method for broadcast packet queue estimation
US20060195603A1 (en) * 2003-04-21 2006-08-31 Seungdong Lee Dongchul S Network traffic control system
US20070220573A1 (en) * 2006-03-20 2007-09-20 Chiussi Fabio M Unicasting and multicasting multimedia services
US20080123649A1 (en) * 2006-07-20 2008-05-29 Via Technologies, Inc. Systems and methods for broadcast storm control
US20080146253A1 (en) * 2006-12-19 2008-06-19 Conexant Systems, Inc. Systems and methods for retrieving buffered data from an access point
US20080307087A1 (en) * 2007-06-11 2008-12-11 Air Products And Chemicals, Inc. Protection of industrial equipment from network storms emanating from a network system
US20090059812A1 (en) * 2007-08-29 2009-03-05 Sudhagar Chinnaswamy Adaptive method and apparatus for adjusting network traffic volume reporting
US20090182854A1 (en) * 2008-01-11 2009-07-16 Alcatel Lucent Facilitating defense against MAC table overflow attacks
US20090190589A1 (en) * 2008-01-28 2009-07-30 Amrik Bains Flexible time stamping
US20090325571A1 (en) * 2007-09-05 2009-12-31 Conexant Systems Inc. Scanning Threshold
US20100180341A1 (en) * 2007-06-29 2010-07-15 Nokia Siemens Networks Oy Method for protection a network through port blocking
US20100191878A1 (en) * 2009-01-29 2010-07-29 Qualcomm Incorporated Method and apparatus for accomodating a receiver buffer to prevent data overflow
GB2477367A (en) * 2008-01-28 2011-08-03 Cisco Tech Inc Flexible time stamping
US8238239B2 (en) * 2005-03-31 2012-08-07 Intel Corporation Packet flow control
US8284665B1 (en) * 2008-01-28 2012-10-09 Juniper Networks, Inc. Flow-based rate limiting
US20130107890A1 (en) * 2011-10-26 2013-05-02 Fujitsu Limited Buffer management of relay device
CN103181128A (en) * 2010-10-28 2013-06-26 日本电气株式会社 Network system and method for controlling communication traffic
US20130167219A1 (en) * 2011-12-22 2013-06-27 Electronics And Telecommunications Research Institute Apparatus and method for cyber-attack prevention
EP2680514A1 (en) * 2012-06-29 2014-01-01 Tellabs Oy A method and a device for detecting originators of data frame storms
EP2720412A1 (en) * 2012-10-12 2014-04-16 Rockwell Automation Technologies, Inc. Hardware-based granular traffic storm protection
US20160080120A1 (en) * 2014-09-11 2016-03-17 Stephen John Unger Ethernet loopback detection and service traffic blocking
US9807013B1 (en) * 2015-03-19 2017-10-31 Amazon Technologies, Inc. Network broadcast traffic filtering

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7508757B2 (en) * 2004-10-15 2009-03-24 Alcatel Lucent Network with MAC table overflow protection
US9270556B2 (en) 2011-07-28 2016-02-23 Hewlett Packard Development Company, L.P. Flow control in packet processing systems
US8824297B2 (en) 2012-04-26 2014-09-02 Cisco Technology, Inc. Adaptive storm control

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5604867A (en) * 1994-07-22 1997-02-18 Network Peripherals System for transmitting data between bus and network having device comprising first counter for providing transmitting rate and second counter for limiting frames exceeding rate
US6587471B1 (en) * 1997-11-21 2003-07-01 International Business Machines Corporation Methods, systems and computer program products for suppressing multiple destination traffic in a computer network
US6826150B1 (en) * 2000-04-30 2004-11-30 Dipankar Bhattacharya Distriburted QoS policing system and method
US20050100020A1 (en) * 2003-11-12 2005-05-12 Akihiro Hata Packet switching device
US7106691B1 (en) * 2000-11-01 2006-09-12 At&T Corp. Method for tracking source and destination internet protocol data
US7120117B1 (en) * 2000-08-29 2006-10-10 Broadcom Corporation Starvation free flow control in a shared memory switching device

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5604867A (en) * 1994-07-22 1997-02-18 Network Peripherals System for transmitting data between bus and network having device comprising first counter for providing transmitting rate and second counter for limiting frames exceeding rate
US6587471B1 (en) * 1997-11-21 2003-07-01 International Business Machines Corporation Methods, systems and computer program products for suppressing multiple destination traffic in a computer network
US6826150B1 (en) * 2000-04-30 2004-11-30 Dipankar Bhattacharya Distriburted QoS policing system and method
US7120117B1 (en) * 2000-08-29 2006-10-10 Broadcom Corporation Starvation free flow control in a shared memory switching device
US7106691B1 (en) * 2000-11-01 2006-09-12 At&T Corp. Method for tracking source and destination internet protocol data
US20050100020A1 (en) * 2003-11-12 2005-05-12 Akihiro Hata Packet switching device

Cited By (56)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060126550A1 (en) * 2002-09-02 2006-06-15 Infineon Tecnnologies Ag Data switch and a method for broadcast packet queue estimation
US7602713B2 (en) * 2002-09-02 2009-10-13 Infineon Technologies Ag Data switch and a method for broadcast packet queue estimation
US20060195603A1 (en) * 2003-04-21 2006-08-31 Seungdong Lee Dongchul S Network traffic control system
US20050232150A1 (en) * 2003-06-03 2005-10-20 Kazuto Nishimura Flow control method and apparatus thereof
US7633862B2 (en) * 2003-06-03 2009-12-15 Fujitsu Limited Flow control method and apparatus thereof
US20050100020A1 (en) * 2003-11-12 2005-05-12 Akihiro Hata Packet switching device
US20050157647A1 (en) * 2004-01-21 2005-07-21 Alcatel Metering packet flows for limiting effects of denial of service attacks
US7436770B2 (en) * 2004-01-21 2008-10-14 Alcatel Lucent Metering packet flows for limiting effects of denial of service attacks
US20060018343A1 (en) * 2004-07-23 2006-01-26 Rodrigo Miguel D V Method for transmitting data packets between nodes of a communication network
US20060067231A1 (en) * 2004-09-27 2006-03-30 Matsushita Electric Industrial Co., Ltd. Packet reception control device and method
US20060092840A1 (en) * 2004-10-29 2006-05-04 Broadcom Corporation Intelligent fabric congestion detection apparatus and method
US7830801B2 (en) * 2004-10-29 2010-11-09 Broadcom Corporation Intelligent fabric congestion detection apparatus and method
US8238239B2 (en) * 2005-03-31 2012-08-07 Intel Corporation Packet flow control
WO2007109647A2 (en) * 2006-03-20 2007-09-27 Airvana, Inc. Unicasting and multicasting multimedia services
US20070220573A1 (en) * 2006-03-20 2007-09-20 Chiussi Fabio M Unicasting and multicasting multimedia services
GB2450285B (en) * 2006-03-20 2011-06-22 Airvana Inc Unicasting and multicasting multimedia services
GB2450285A (en) * 2006-03-20 2008-12-17 Airvana Inc Unicasting and multicasting multimedia services
WO2007109647A3 (en) * 2006-03-20 2008-04-17 Airvana Inc Unicasting and multicasting multimedia services
US20080123649A1 (en) * 2006-07-20 2008-05-29 Via Technologies, Inc. Systems and methods for broadcast storm control
US20080146253A1 (en) * 2006-12-19 2008-06-19 Conexant Systems, Inc. Systems and methods for retrieving buffered data from an access point
US8849315B2 (en) 2006-12-19 2014-09-30 Conexant Systems, Inc. Systems and methods for retrieving buffered data from an access point
US7689689B2 (en) * 2007-06-11 2010-03-30 Air Products And Chemicals, Inc. Protection of industrial equipment from network storms emanating from a network system
US20080307087A1 (en) * 2007-06-11 2008-12-11 Air Products And Chemicals, Inc. Protection of industrial equipment from network storms emanating from a network system
US8544088B2 (en) * 2007-06-29 2013-09-24 Adtran GmbH Method for protecting a network through port blocking
US20100180341A1 (en) * 2007-06-29 2010-07-15 Nokia Siemens Networks Oy Method for protection a network through port blocking
US7944836B2 (en) * 2007-08-29 2011-05-17 Ericsson Ab Adaptive method and apparatus for adjusting network traffic volume reporting
US20090059812A1 (en) * 2007-08-29 2009-03-05 Sudhagar Chinnaswamy Adaptive method and apparatus for adjusting network traffic volume reporting
US8077647B2 (en) * 2007-09-05 2011-12-13 Conexant Systems, Inc. Systems and methods for utilizing a scanning threshold to reduce power consumption
US20090325571A1 (en) * 2007-09-05 2009-12-31 Conexant Systems Inc. Scanning Threshold
US8396015B2 (en) * 2007-09-05 2013-03-12 Conexant Systems, Inc. Scanning threshold
US20120093026A1 (en) * 2007-09-05 2012-04-19 Maarten Menzo Wentink Scanning threshold
WO2009093224A3 (en) * 2008-01-11 2009-12-17 Alcatel Lucent Facilitating defense against mac table overflow attacks
US20090182854A1 (en) * 2008-01-11 2009-07-16 Alcatel Lucent Facilitating defense against MAC table overflow attacks
US8180874B2 (en) 2008-01-11 2012-05-15 Alcatel Lucent Facilitating defense against MAC table overflow attacks
WO2009093224A2 (en) * 2008-01-11 2009-07-30 Alcatel Lucent Facilitating defense against mac table overflow attacks
US8797869B2 (en) 2008-01-28 2014-08-05 Juniper Networks, Inc. Flow-based rate limiting
WO2009097251A2 (en) * 2008-01-28 2009-08-06 Cisco Technology, Inc. Flexible time stamping
US20090190589A1 (en) * 2008-01-28 2009-07-30 Amrik Bains Flexible time stamping
US8284665B1 (en) * 2008-01-28 2012-10-09 Juniper Networks, Inc. Flow-based rate limiting
GB2477367A (en) * 2008-01-28 2011-08-03 Cisco Tech Inc Flexible time stamping
US7860125B2 (en) * 2008-01-28 2010-12-28 Cisco Techology, Inc. Flexible time stamping
GB2477367B (en) * 2008-01-28 2016-01-06 Cisco Tech Inc Flexible time stamping
WO2009097251A3 (en) * 2008-01-28 2009-10-08 Cisco Technology, Inc. Flexible time stamping
US20100191878A1 (en) * 2009-01-29 2010-07-29 Qualcomm Incorporated Method and apparatus for accomodating a receiver buffer to prevent data overflow
US9137160B2 (en) * 2009-01-29 2015-09-15 Qualcomm Incorporated Method and apparatus for accomodating a receiver buffer to prevent data overflow
EP2634977A4 (en) * 2010-10-28 2015-01-07 Nec Corp Network system and method for controlling communication traffic
EP2634977A1 (en) * 2010-10-28 2013-09-04 Nec Corporation Network system and method for controlling communication traffic
CN103181128A (en) * 2010-10-28 2013-06-26 日本电气株式会社 Network system and method for controlling communication traffic
US20130107890A1 (en) * 2011-10-26 2013-05-02 Fujitsu Limited Buffer management of relay device
US9008109B2 (en) * 2011-10-26 2015-04-14 Fujitsu Limited Buffer management of relay device
US20130167219A1 (en) * 2011-12-22 2013-06-27 Electronics And Telecommunications Research Institute Apparatus and method for cyber-attack prevention
EP2680514A1 (en) * 2012-06-29 2014-01-01 Tellabs Oy A method and a device for detecting originators of data frame storms
US9374387B2 (en) 2012-10-12 2016-06-21 Rockwell Automation Technologies, Inc. Hardware-based granular traffic storm protection
EP2720412A1 (en) * 2012-10-12 2014-04-16 Rockwell Automation Technologies, Inc. Hardware-based granular traffic storm protection
US20160080120A1 (en) * 2014-09-11 2016-03-17 Stephen John Unger Ethernet loopback detection and service traffic blocking
US9807013B1 (en) * 2015-03-19 2017-10-31 Amazon Technologies, Inc. Network broadcast traffic filtering

Also Published As

Publication number Publication date Type
US7274665B2 (en) 2007-09-25 grant

Similar Documents

Publication Publication Date Title
US4769811A (en) Packet switching system arranged for congestion control
US6092115A (en) Method for supporting per-connection queuing for feedback-controlled traffic
US6748435B1 (en) Random early demotion and promotion marker
US6826150B1 (en) Distriburted QoS policing system and method
Ryu et al. Advances in internet congestion control
Romanow et al. Dynamics of TCP traffic over ATM networks
Cao et al. Rainbow fair queueing: Fair bandwidth sharing without per-flow state
US5231633A (en) Method for prioritizing, selectively discarding, and multiplexing differing traffic type fast packets
US7149187B1 (en) Random early detection policer using randomization of packet drops
Feng et al. BLUE: A new class of active queue management algorithms
US7499398B2 (en) Method and system for oversubscribing bandwidth in a communications network
US7158480B1 (en) Feedback output queuing system, apparatus, and method
US20060153092A1 (en) Active response communications network tap
US20020172205A1 (en) System and a method for processing data packets or frames
US20020141403A1 (en) Router
US20120207175A1 (en) Dynamic load balancing for port groups
US6980516B1 (en) Soft, prioritized early packet discard system
US7020143B2 (en) System for and method of differentiated queuing in a routing system
US20070183332A1 (en) System and method for backward congestion notification in network
US20070280239A1 (en) Method and system for power control based on application awareness in a packet network switch
Wang et al. Achieving bounded fairness for multicast and TCP traffic in the Internet
Romanow et al. Dynamics of TCP traffic over ATM networks
US20030169690A1 (en) System and method for separating communication traffic
US20040151184A1 (en) Class-based rate control using multi-threshold leaky bucket
US6839767B1 (en) Admission control for aggregate data flows based on a threshold adjusted according to the frequency of traffic congestion notification

Legal Events

Date Code Title Description
AS Assignment

Owner name: INTEL CORPORATION, CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:KESAVAN, VIJAY SARATHI;REEL/FRAME:013349/0651

Effective date: 20020930

FPAY Fee payment

Year of fee payment: 4

REMI Maintenance fee reminder mailed
LAPS Lapse for failure to pay maintenance fees
FP Expired due to failure to pay maintenance fee

Effective date: 20150925