US20090279441A1 - Techniques for transmitting failure detection protocol packets - Google Patents
Techniques for transmitting failure detection protocol packets Download PDFInfo
- Publication number
- US20090279441A1 US20090279441A1 US11/953,745 US95374507A US2009279441A1 US 20090279441 A1 US20090279441 A1 US 20090279441A1 US 95374507 A US95374507 A US 95374507A US 2009279441 A1 US2009279441 A1 US 2009279441A1
- Authority
- US
- United States
- Prior art keywords
- packet
- failure detection
- detection protocol
- fdp
- module
- 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.)
- Abandoned
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0823—Errors, e.g. transmission errors
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
Abstract
Description
- The present application claims the benefit and priority under 35 U.S.C. 119(e) from U.S. Provisional Application No. 60/880,074 filed Jan. 11, 2007 entitled TIMING SENSITIVE PROTOCOL PACKET HARDWARE ASSIST, the entire contents of which are herein incorporated by reference for all purposes.
- The present application also incorporates by reference for all purposes the entire contents of the following applications filed concurrently with the present application:
- (1) U.S. Non-Provisional Application No. ______ (Atty. Docket No. 019959-003910US) titled TECHNIQUES FOR PROCESSING INCOMING FAILURE DETECTION PROTOCOL PACKETS;
- (2) U.S. Non-Provisional Application No. ______ (Atty. Docket No. 019959-003920US) titled TECHNIQUES FOR DETECTING NON-RECEIPT OF FAULT DETECTION PROTOCOL PACKETS; and
- (3) U.S. Non-Provisional Application No. _______(Atty. Docket No. 019959-003940US) titled TECHNIQUES FOR USING DUAL MEMORY STRUCTURES FOR PROCESSING FAILURE DETECTION PROTOCOL PACKETS.
- The present application relates to networking technologies and more particularly to techniques for transmitting failure detection protocol packets from a network device.
- The ability to detect communication failures is an important aspect of any networking environment. Networks use several different mechanisms to detect failures. For example, several different failure detection protocols (FDP) are used that enable detection of failures in a networking environment. Examples of FDPs include “hello” protocols, “keep alive” protocols, various Organization Administration and Maintenance (OAM) protocols, and others.
- Network devices (e.g., routers, switches) in a network using a failure detection protocol are generally configured to continuously transmit FDP packets at regular intervals. A network device in the network receives FDP packets transmitted by other network devices in the network and uses the periodically received packets to ascertain the health of the other devices and the network connections. For example, if a network device does not receive an FDP packet within a period of time associated with the FDP packet, then the network device may assume that there is a network failure somewhere in the network that prevented the expected FDP packet from reaching the network device. The network device itself also transmits FDP packets on a periodic basis.
- A network device may receive and transmit different types of FDP packets and may be involved in one or more FDP sessions at a time. Each transmitted FDP packet comprises an identifier identifying a unique FDP session for which the packet has been transmitted.
- Traditionally, FDP-related processing in a network device is performed by software executed by a CPU or processor of the network device. For example, a processor of a network device executing software configured for FDP packets processing is configured to process FDP packets received by the network device from other network devices and handle transmission of FDP at regular intervals from the network device. In older failure detection protocols, the periodic time intervals associated with FDP protocols were generally in the range of seconds such as 1 second, 5 seconds, 10 seconds, 20 seconds, and the like. Such a time interval allowed sufficient time for the software running on the CPU to handle processing of the incoming FDP packets and also to process transmission of the FDP packets within the periodic time interval without detrimentally affecting the performance of the CPU or overwhelming the CPU. However, due to the large periodic interval time values, the time required to detect network failures is also quite large (usually several seconds). While this was acceptable in the past, it is no longer acceptable in today's larger and faster networks wherein a long failure detection time translates to large amounts of data being lost at today's fast networking speeds (e.g., at gigabit speeds).
- In order to reduce failure detection times, today's networks typically use newer fault detection protocols with significantly shorter periodic time intervals that dramatically reduce the failure detection times. Examples of such newer FDPs include OAM protocols such as Bidirectional Forwarding (BFD) protocol which is used to detect router link failures and the 802.1ag standard that specifies protocols, procedures, and managed objects to support transport fault management. The periodic time intervals associated with these new FDPs is usually in the order of milliseconds (msecs) or even faster.
- While these new protocols reduce failure detection times, they create an undue burden on a network device that is configured to handle processing of the FDP packets. As a result of the dramatically shorter periodic time intervals, a network device has to periodically transmit FDP packets in the order of milliseconds (msecs) or even faster, which is much faster than transmission processing done previously by network device for older FDPs. Due to the faster transmission rates, the number and rate at which FDP packets are received by a network device is also much faster than in the past. As a result, more CPU cycles per unit time are needed on the network device to perform FDP packets processing, including transmission of FDP packets and processing of incoming FDP packets. However, processors in conventional network devices executing software for processing the FDP packets are unable to cope up with the processing of newer FDP packets. As a result, conventional network devices are unable to handle and support the newer failure detection protocols.
- Embodiments of the present invention provide techniques that assist in processing of failure detection protocol (FDP) packets. Techniques are provided that assist a CPU of a network device in processing incoming FDP packets. The task of transmitting FDP packets from a network device is offloaded from the CPU of the network device and instead handled by another module of the network device. In this manner, the processing that the CPU of the network device has to perform for transmitting FDP packets for the various FDP sessions of the network device is reduced. This enables the network device to support newer FDPs with shorter periodic interval requirements.
- According to an embodiment of the present invention, techniques are provided for transmitting packets according to an FDP from a network device. The network device stores timer information specifying a periodic time interval for transmitting an FDP packet for an FDP. FDP packets for the FDP are transmitted periodically at times determined based upon the periodic time interval stored for the FDP. The transmitting is performed by a module of the network device other than a processor configured to execute software for processing FDP packets. The module may be a field-programmable logic device in one embodiment.
- In one embodiment, the transmitting comprises determining a time for transmitting an FDP packet for the FDP based upon the periodic time interval stored for the FDP, and transmitting an FDP packet at the determined time.
- In one embodiment, the timer information for an FDP may comprise a first timer specifying the periodic time interval for the FDP and a second timer identifying when an FDP packet was last transmitted by the network device for the FDP. An FDP packet may be transmitted when the second timer equals the first timer. The first timer may be set by the software executed by the processor of the network device and the second timer is updated by the module.
- In one embodiment, FDP packets for an FDP may comprise a field that is updated with every successive FDP packet transmission. In this scenario, transmitting an FDP packet may comprise transmitting a first FDP packet based upon the periodic time interval stored for the FDP, wherein the field of the first failure is set to a first value, and transmitting, after transmitting the first FDP packet, a second FDP packet based upon the periodic time interval stored for the FDP, wherein the field of the second FDP packet is set to a second value that is different from the first value. In one embodiment this may done by storing a parameter for the FDP. Prior to transmitting the first FDP packet, the field of the first FDP packet may be set to the first value based upon the value of the parameter. The value of the parameter may be updated upon transmission of the first FDP packet. Prior to transmitting the second FDP packet, the field of the second FDP packet may be set to the second value based upon the updated value of the parameter.
- Examples of FDPs include 802.1ag, Bidirectional Forwarding (BFD) protocol, and others. The periodic time intervals associated with the protocols may even be less than one second.
- The foregoing, together with other features, embodiments, and advantages of the present invention, will become more apparent when referring to the following specification, claims, and accompanying drawings.
-
FIG. 1 is a simplified diagram of a portion of a network that may incorporate an embodiment of the present invention; -
FIG. 2 depicts a simplified block diagram of a network device incorporating an embodiment of the present invention; -
FIG. 3 depicts a simplified flowchart showing a method performed by an FDP Packet Handler (FPH) module for processing a CPU-bound packet in the receive (Rx) path according to an embodiment of the present invention; -
FIG. 4 depicts a simplified flowchart showing a method performed by an FPH module for detecting non-receipt of FDP packets for a session according to an embodiment of the present invention; -
FIG. 5 depicts a simplified flowchart showing a method performed by an FPH module for transmitting FDP packets for an FDP session from a network device according to an embodiment of the present invention; -
FIG. 6 depicts an example of a linked list priority queue that may be used by an FPH module to facilitate transmission of FDP packets according to an embodiment of the present invention; -
FIG. 7 depicts a two ring structure that may be used by an FPH module to facilitate processing of FDP packets in the receive (Rx) path according to an embodiment of the present invention; -
FIG. 8 is simplified block diagram of an FPH module according to an embodiment of the present invention; -
FIG. 9 depicts a format for a BFD packet; -
FIG. 10 depicts the format for a BFD header field; -
FIG. 11 depicts a memory structure storing BFD reference information for multiple BFD sessions according to an embodiment of the present invention; -
FIG. 12 depicts contents of counter information for a BFD session entry according to an embodiment of the present invention; -
FIGS. 13A and 13B depict formats for two types of 802.1ag packets that may be processed by an embodiment of the present invention; -
FIG. 14 depicts contents of an 802.1ag packet data section; -
FIG. 15 depicts an 802.1ag packet reference table according to an embodiment of the present invention; -
FIG. 16 depicts contents of a hash table and sessions table storing reference information according to an embodiment of the present invention; -
FIG. 17 depicts a format of a Session Status FIFO according to an embodiment of the present invention; -
FIG. 18 depicts a linked list that may be used by an FPH module to facilitate transmission of 802.1ag packets according to an embodiment of the present invention; and -
FIG. 19 depicts a simplified flowchart showing a method performed by an FPH module for transmitting 802.1ag packets according to an embodiment of the present invention. - In the following description, for the purposes of explanation, specific details are set forth in order to provide a thorough understanding of the invention. However, it will be apparent that the invention may be practiced without these specific details.
- Embodiments of the present invention provide techniques that assist in processing of failure detection protocol (FDP) packets. Techniques are provided that assist a CPU of a network device in processing incoming FDP packets. A failure detection protocol (or FDP) is intended to include any protocol, standard, procedure, or method in which packets are transmitted at periodic intervals for purposes of monitoring, detecting, or identifying a failure in a network. A packet transmitted according to an FDP is referred to as an FDP packet. Examples of FDPs that may be supported by embodiments of the present invention include OAM protocols such as Bidirectional Forwarding (BFD) protocol which is used to detect router link failures and the 802.1ag standard that specifies protocols, procedures, and managed objects to support transport fault management.
-
FIG. 1 is a simplified diagram of a portion of anetwork 100 that may incorporate an embodiment of the present invention. The portion ofnetwork 100 depicted inFIG. 1 comprises a number ofnetwork devices - The network devices depicted in
FIG. 1 may use one or more types of failure detection protocols (FDPs) to facilitate detection of failures innetwork 100. The FDPs used may include OAM protocols such as BFD and 802.1ag, and others. A network device may be involved in one or more FDP sessions. For each FDP session, the network device may be configured to continuously transmit FDP packets at a periodic time interval associated with that FDP session. A network device may also receive FDP packets transmitted by other devices in the network. The periodic time intervals at which FDP packets are received or transmitted may vary from one FDP session to another depending on the type of FDP session. The periodic time intervals may be in the order of one or more milliseconds (msecs), one or more seconds, or other faster or slower time intervals. - In accordance with an embodiment of the present invention, a
network device 102 may be configured to receive FDP packets for one or more FDP sessions from other network devices.Network device 102 may also transmit FDP packets at periodic intervals for one or more FDP sessions to other devices in the network. The time intervals at which the packets are received and transmitted may vary from session to session and may be in the order of one or more milliseconds (as required by the newer FDPs) to seconds, or even faster or slower intervals.Network device 102 may be configured to ascertain the health of the other devices and the network connections based upon the FDP packets received bynetwork device 102. For example, ifnetwork device 102 does not receive an FDP packet for an FDP session within a preconfigured time interval for that session, thennetwork device 102 may assume that there is a network failure somewhere in the network that prevented the expected FDP packets from reachingnetwork device 102 for the session. Network device itself may transmit FDP packets at periodic intervals for one or more FDP sessions. - As depicted in
FIG. 1 ,network device 102 comprises a processor orCPU 114 and an FDP Packet Handler (FPH)module 116.CPU 114 is configured to execute software for performing various tasks performed bynetwork device 102. In one embodiment,CPU 114 executes software (e.g., program, code, instructions, etc.) that is configured to handle processing of FDP packets. According to an embodiment of the present invention,FPH module 116assists CPU 114 in FDP packets-related processing, including processing of incoming FDP packets and transmission of FDP packets.FPH module 116 may be implemented as a field programmable logic device (FPLD) such as a programmed field-programmable gate array (FPGA) device or an ASIC. - In one embodiment,
FPH module 116 is configured to filter FDP packets received bynetwork device 102 and bound forCPU 114 such that only a subset of received FDP packets are forwarded toCPU 114 for processing, the other FDP packets are dropped byFPH module 116 and not forwarded toCPU 114. In one embodiment,FPH module 116 receives CPU-bound packets and identifies FDP packets from other CPU-bound packets. For a packet identified as an FDP packet,FPH module 116 determines whether the packet needs to be sent toCPU 114. IfFPH module 116 determines that the FDP packet need not be forwarded toCPU 114, the FDP packet is dropped and not sent toCPU 114, thereby relievingCPU 114 from having to process the packet. An FDP packet is forwarded toCPU 114 only ifFPH module 116 determines that the packet cannot be consumed byFPH module 116 and needs to be forwarded toCPU 114 for inspection. In this manner, only a small subset of FDP packets received bynetwork device 102 is forwarded toCPU 114 for processing. This reduces the amount of processing thatCPU 114 has to do to process FDP packets received bynetwork device 102. -
FPH module 116 is also configured to assist in transmission of FDP packets fromnetwork device 102. For each FDP session in whichnetwork device 102 participates, FDP packets for that session are transmitted fromnetwork device 102 at periodic time intervals associated with the FDP for that session. The time intervals may be different for different FDP sessions. In this manner, the task of transmitting FDP packets is partially or completely offloaded fromCPU 114 ofnetwork device 102. - By assisting in processing of incoming FDP packets,
FPH module 116 reduces the number of incoming FDP packets thatCPU 114 has to process, thereby freeing CPU cycles for other tasks performed byCPU 114.FPH module 116 also offloads the task of transmitting FDP packets fromCPU 114. In this manner, the amount of FDP packets-related processing thatCPU 114 has to perform is reduced. This enablesnetwork device 102 to support various FDPs including FDPs with shorter periodic interval requirements (e.g., periodic time intervals measured in milliseconds or even faster).Network device 102 comprising aFPH module 116 may coexist in a network with other network devices that may or may not comprise FPH modules. -
FIG. 2 depicts a simplified block diagram of anetwork device 102 incorporating an embodiment of the present invention.FIG. 2 is merely illustrative of an embodiment incorporating the present invention and does not limit the scope of the invention as recited in the claims. One of ordinary skill in the art would recognize other variations, modifications, and alternatives.Network device 102 may be embodied as a switch or router, such as routers and switches provided by Foundry Networks®, Inc. of Santa Clara, Calif. - As depicted in
FIG. 2 ,network device 102 comprises one ormore ports 202, a traffic manager (TM)module 204, an FDP packet handler (FPH)module 116, and aCPU 114 with associated memory 206 (e.g., SDRAM).Network device 102 receives data, including FDP packets, via one ormore ports 202.Network device 102 may receive multiple streams of FDP packets concurrently from one or more sources for one or more FDP sessions. An FDP packet received from a source may comprise an FDP session identifier identifying the FDP session for which the packet is received.Ports 202 are also used to transmit data, including FDP packets, fromnetwork device 102. -
Network device 102 may support two data processing paths including a receive path (Rx path) and a transmit path (Tx path). Processing for the two paths may be performed in parallel. The Rx path is a path traversed by a packet from a port ofnetwork device 102 towardsCPU 114 ofnetwork device 102. The Tx path is a path traversed by a packet fromCPU 114 towards a port ofnetwork device 102. - In one embodiment, in the Rx path, packets received by
network device 102 via one or more ports 202 (or a subset of the received packets) are forwarded toTM module 204. These packets may include CPU-bound packets (i.e., packets to be forwarded toCPU 114 for processing) and other packets.TM module 204 is configured to forward the CPU-bound packets toFPH module 116. The CPU-bound packets may include FDP packets, packets that enableCPU 114 to learn network topologies, and other types of packets. In the Tx path,TM module 204 is configured to receive packets, including FDP packets, fromFPH module 116. The packets are then forwarded to their destinations, which may include one ormore ports 202 ofnetwork device 102. The packets, including FDP packets, are then transmitted fromnetwork device 102 using the destination ports. -
FPH module 116 is configured to assist with processing related to FDP packets. In one embodiment,FPH module 116 is implemented in hardware. For example,FPH module 116 may be implemented as a field programmable logic device (FPLD) such as a programmed field-programmable gate array (FPGA) device.FPH module 116 may also be implemented as an ASIC. As depicted inFIG. 2 ,FPH module 116 is positioned in the Rx path betweenTM module 204 andCPU 114 and in the Tx path betweenCPU 114 andTM module 204. This enablesFPH module 116 to receive all CPU-bound packets in the Rx path, including all FDP packets received bynetwork device 102, prior to the packets being forwarded toCPU 114. - Processing of Incoming FDP Packets
- In the Rx path,
FPH module 116 receives CPU-bound packets fromTM Interface module 204. From the packets received fromTM module 204,FPH module 116 is configured to identify FDP packets.FPH module 116 may use different techniques to identify FDP packets. For example, in one embodiment, contents of a packet, including the header and/or the payload of the packet, may be examined to determine if the packet is an FDP packet. For example, a BSD packet comprises a UDP header specifying a destination port that identifies the packet as a BSD packet and accordingly an FDP packet. For an 802.1ag packet, fields in the packet are used to identify if the packet is an 802.1ag packet. - For a packet identified as an FDP packet,
FPH module 116 determines if the FDP packet needs to be forwarded toCPU 114 or whether the FDP packet can be dropped without forwarding toCPU 114. Various different techniques may be used byFPH module 116 to determine if a packet needs to be forwarded toCPU 114. The techniques may be different for different FDPs. According to one technique, a portion of the FDP packet is compared with preconfigured reference information and the results of the comparison are used to determine if the FDP packet needs to be sent toCPU 114 or if the packet can be dropped without sending it toCPU 114. As part of the comparison,FPH module 116 is configured to determine if a portion of an FDP packet received for a session matches a corresponding entry in the reference information for that session. In one embodiment, a match indicates that the FDP packet need not be forwarded to the CPU. In such a case, the FDP packet for that session is dropped and not forwarded toCPU 114. As a result,CPU 114 does not receive the FDP packet and consequently does not have to process the dropped packet. In one embodiment, if the portion of the FDP packet being compared does not match information in the reference information, thenFPH module 116 forwards the FDP packet toCPU 114. In such a scenario,FPH module 116 may also raise an interrupt signaling toCPU 114 that a packet is being forwarded toCPU 114. - Different techniques may be used to forward an FDP packet from
FPH module 116 toCPU 114. In one embodiment, a direct memory access (DMA) technique may be used to forward the packet toCPU 114.FPH module 116 may DMA the packet to a buffer stored inmemory 106 associated withCPU 114.CPU 114 may then read the packet frommemory 206. Various other techniques may also be used to forward FDP packets toCPU 114. - The reference information that is used by
FPH module 116 to determine whether or not an FDP packet for a session needs to be forwarded toCPU 114 may be preconfigured and programmed by software executed byCPU 114. The reference information may comprise various rules configured by the software for various types of FDP sessions. The reference information may be stored in different formats. In one embodiment, the reference information is stored as a table with each row entry in the table corresponding to an FDP session. In one embodiment, the reference information is stored byFPH module 116. The reference information may also be stored in other memory locations accessible toFPH module 116. For example, in one embodiment, the reference information may be stored in one ormore memories 206 associated withCPU 114. -
FIG. 3 depicts asimplified flowchart 300 showing a method performed byFPH module 116 for processing a CPU-bound packet in the receive (Rx) path according to an embodiment of the present invention. As depicted inFIG. 3 , processing is initiated whenFPH module 116 receives a CPU-bound packet (step 302). For the embodiment depicted inFIG. 2 , processing may be initiated when a CPU-bound packet is received byFPH module 116 fromTM module 204. -
FPH module 116 then determines if the packet is an FDP packet (step 304). As previously described, various different techniques may be used to determine if a packet is an FDP packet. For example, information stored in the header and/or payload of the packet may be used to determine if the packet is an FDP packet. As part of 304,FPH module 116 may also determine a particular FDP (e.g., BFD or 802.1ag, or other) to which the packet belongs. If it is determined in 304 that the packet is not an FDP packet, then the packet is forwarded to CPU 114 (step 306) and processing ends. Various different techniques such as DMA techniques and others may be used to forward the packet toCPU 114. - If it is determined in 304 that the packet is an FDP packet, then a portion of the packet is compared with information stored in reference information (step 308). The reference information may be stored by
FPH module 116 or may be stored in some memory location accessible toFPH module 116. The portion of the packet being compared may include a portion of the header of the packet and/or a portion of the payload of the packet. In one embodiment, the packet information is compared with reference information configured for the FDP session for which the packet is received. - Different types of reference information may be stored and used for the comparison for different FDPs. Accordingly, in 308, the reference information that is used for the comparison may depend on the FDP corresponding to the FDP packet. For example, the reference information used for a BFD packet is different from the reference information used for an 802.1ag packet.
- Based upon the results of the comparison performed in 308, a determination is made if the packet is to be forwarded to CPU 114 (step 310). In one embodiment, if the portion of the FDP packet being compared matches information in the reference information for that FDP then this indicates that the packet is not to be forwarded to
CPU 114. If however the portion of the packet being compared does not match information in the reference information then the packet is identified to be forwarded toCPU 114. If it is determined in 310 that the packet is to be forwarded to CPU, then the FDP packet is forwarded toCPU 114 according to step 306 and processing terminates. If it is determined in 310 that the packet is not to be forwarded to CPU, then the FDP packet is dropped and not forwarded to CPU 114 (step 312) and processing terminates. - The processing depicted in
FIG. 3 and described above may be repeated for each packet received byFPH module 116. As a result of the processing depicted inFIG. 3 and described above, only a subset of CPU-bound FDP packets received byFPH module 116 may need to be forwarded toCPU 114 for processing. In this manner,CPU 114 may not receive each FDP packet received bynetwork device 102 thereby reducing the number of incoming FDP packets that need to be processed byCPU 114. - Determining Non-Receipt of FDP Packets
-
FPH module 116 is also configured to monitor non-receipt of FDP packets.FPH module 116 is configured to monitor and take appropriate actions in situations where an FDP packet for an FDP session is not received bynetwork device 102 within a periodic time interval for that FDP session. As previously described, an FDP specifies a periodic time interval in which packets for that FDP are to be transmitted and received. When an FDP packet is not received within the expected time interval,FPH module 116 is configured to signal such an occurrence toCPU 114 since it may indicate a network failure. - As previously described, a network device such as
network device 102 depicted inFIG. 2 may be involved in one or more FDP sessions. Each FDP session may have its own associated periodic time interval within which FDP packets should be received for that session.FPH module 116 is configured to monitor and track the receipt of FDP packets for each of the sessions and raise a signal if an FDP packet is not received within the time interval for a session. -
FPH module 116 may use different techniques to monitor receipt and non-receipt of FDP packets information for various FDP sessions. In one embodiment,FPH module 116 maintains a pair of timers for each session. The pair of timers includes a first timer (interval_limit timer) that indicates a time interval_limit within which an FDP packet should be received for that session. This timer is typically programmed by software executed by the CPU of the network device. The pair of timers also includes a second timer (last_received timer) that is used byFPH module 116 to monitor the time that it has waited to receive an FDP packet for the session since the last_receipt of an FDP packet for that session. When an FDP packet for that session is received, the last_received timer is reset byFPH module 116.FPH module 116 iteratively checks the values of the interval_limit timer and the last_received timer for each of the FDP sessions in which the network device participates. During each iteration for a session,FPH module 116 checks if the last_received timer for a session has reached the interval_limit timer for that session. When the last_received timer reaches or exceeds the interval_limit timer, it indicates that the FDP packet for the session was not received in the expected time interval andFPH module 116 signals this toCPU 114. The FDP session may be considered to have expired due to the non-receipt of an FDP packet. In one embodiment, an interrupt is generated byFPH module 116 to flag that the particular FDP session has expired possibly due to some failure in the network (e.g., a link is down). If the last_received timer has not reached he interval_limit timer, then the last_received timer is incremented. In this manner, the timers are used to monitor receipt and non-receipt of FDP packets for each FDP session. The timers information may be stored byFPH module 116 or in some memory location accessible toFPH module 116. -
FIG. 4 depicts asimplified flowchart 400 showing a method performed byFPH module 116 for detecting non-receipt of FDP packets for an FDP session according to an embodiment of the present invention.FIG. 4 depicts processing performed at each iteration byFPH module 116. As depicted inFIG. 4 , at each iteration,FPH module 116 checks if the last_received timer equals or exceeds the interval_limit timer (step 402). If it is determined in 402, that the last_received timer has not reached the interval_limit timer (i.e., the last_received timer is less than the interval_limit timer), the last_received timer is incremented (step 404). The amount by which the last_received timer is incremented depends upon the time frequency at whichFPH module 116 performs the iterations. For example, ifFPH module 116 checks the timers for a session every 1 msec, then the last_received timer is incremented by 1 msec, if the check is performed every 50 msecs then the last_received timer is incremented by 50 msecs, and so on. If it is determined in 402, that the last_received timer has reached or exceeded the interval_limit timer (i.e., the last_received timer is equal to or greater than the interval_limit timer) then this indicates that an FDP packet for the session has not been received within the time interval window for that particular FDP session and a signal is raised to indicate that the FDP session has expired (step 406). As also shown inFIG. 4 , the last_received timer for an FDP session is reset to zero upon receipt of an FDP packet for that session within the interval_limit timer period. - The processing depicted in
FIG. 4 is repeated byFPH module 116 for each of the FDP sessions at periodic intervals such as every one millisecond, every 50 milliseconds, etc. In one embodiment, the frequency at which the timers information is checked for a session is programmable. As previously indicated,FPH module 116 may monitor timers for multiple FDP sessions. The frequency with whichFPH module 116 checks the timers information for the sessions may also be automatically determined based upon the interval_limit timers for the various sessions. For example, in one embodiment, the iteration frequency may be set to the least common denominator of the various interval_limit timers being tracked for the various sessions byFPH module 116. For example, if three FDP sessions are being tracked having interval_limit timers of 4 msecs, 6 msecs, and 12 msecs, then the frequency at which the iterations are performed may be set to 2 msecs, which is the least common denominator for the three interval_limit timers. In this manner, the frequency is programmable and/or may be automatically determined from the interval_limit timers. - As described above, in the Rx path,
FPH module 116 handles processing of FDP packets received by a network device and also non-receipt of FDP packets. In the Tx path,FPH module 116 may receive packets fromCPU 114 and forward the packets toTM module 204.TM module 204 may then forward the packets to the appropriate destinations for the packets. - Transmission of FDP Packets
-
FPH module 116 is also configured to assist in transmission of FDP packets for the various FDP sessions in whichnetwork device 102 participates. In this manner, the FDP packets transmission task is offloaded fromCPU 114. In order to facilitate transmission of FDP packets, in one embodiment,FPH module 116 maintains a pair of timers for each FDP session. The pair of timers includes a first timer (trx_interval timer) that indicates the periodic transmission interval for transmitting an FDP packet for that FDP session. The trx_interval timer may be different for the different FDP sessions handled by the network device. This timer is typically programmed by software executed byCPU 114. The pair of timers also includes a second timer (last_sent timer) that is used byFPH module 116 to monitor the time when an FDP packet was last transmitted bynetwork device 102 for the FDP session. The two timers for each session are iteratively checked at periodic intervals to determine when to transmit an FDP packet for that session. In one embodiment, when the last_sent timer is equal to the trx_interval timer,FPH module 116 transmits an FDP packet for that session and the last_sent timer is reset to zero to restart the count. The FDP packet transmitted byFPH module 116 for a session is forwarded toTM module 204 and then to a destination port ofnetwork device 102. The FDP packet is then forwarded fromnetwork device 102 using the destination port. In this manner,FPH module 116 facilitates transmission of FDP packets fromnetwork device 102 for the various FDP sessions at periodic intervals associated with the FDP sessions. -
FIG. 5 depicts asimplified flowchart 500 showing a method performed byFPH module 116 for transmitting FDP packets for an FDP session fromnetwork device 102 according to an embodiment of the present invention.FIG. 5 depicts processing performed at each iteration byFPH module 116. As depicted inFIG. 5 , at each iteration,FPH module 116 checks if the last_sent timer has reached the trx_interval timer (step 502). If it is determined in 502, that the last_sent timer has not reached the trx_interval timer (i.e., the last_sent timer is less than the trx_interval timer), the last_sent timer is incremented (step 504). The amount by which the last_sent timer is incremented depends upon the time frequency at whichFPH module 116 checks the timers for the session. For example, ifFPH module 116 checks the timers for a session very 1 msec, then the last_received timer is incremented by 1 msec, if the iteration is performed every 50 msecs then the last_received timer is incremented by 50 msecs, and so on. If it is determined in 502 that the last_sent timer has reached the trx_interval timer (i.e., the last_sent timer is equal to the trx_interval timer), this indicates that it is time to transmit an FDP packet for the session and an FDP packet is transmitted (step 506). In one embodiment, as part of 506,FPH module 116 transmits an FDP packet for the session toTM module 204. The FDP packet is then forwarded to a port of the network device and transmitted from the network device via the port. After an FDP packet transmission, the last_sent timer is reset to zero to restart the countdown for the next time an FDP packet is to be sent for the session (step 508). The processing depicted inFIG. 5 is repeated at each iteration. - The processing depicted in
FIG. 5 and described above may be performed byFPH module 116 at periodic intervals for each FDP session ofnetwork device 102. The frequency at which the processing is performed may be every one millisecond, every 50 milliseconds, etc. In one embodiment, the frequency at whichFPH module 116 performs the processing depicted inFIG. 5 is programmable. The frequency may also be automatically determined based upon the trx_interval timers for the various sessions. For example, the processing frequency may be set to the least common denominator of the various trx_interval timers for the various FDP sessions ofnetwork device 102. For example, if three FDP sessions are being handled having trx_interval timers of 20 msecs, 40 msecs, and 100 msecs, then the frequency at which the iterations are performed may be set to 20 msecs. In this manner, the frequency is programmable and/or may be automatically determined from the trx_interval timers. - As depicted in
FIG. 5 and described above,FPH module 116 handles transmission of FDP packets at regular intervals for the various FDP sessions ofnetwork device 102. The sessions may correspond to different FDPs. Software executed byCPU 114 typically pre-configures the periodic intervals at which FDP packets are to be sent for the FDP sessions andFPH module 116 handles the transmission of FDP packets for the sessions. The periodic time interval for a session at which FDP packets are transmitted for that session may be measured in seconds (e.g., every 1 second, every 5 seconds, etc.) or even faster than one second such as measured in milliseconds (e.g., every 1 msec, every 5 msecs, etc.), or some other faster or slower time period. In this manner, the FDP packets transmission task is offloaded from CPU 113 byFPH module 116. - Various different memory structures may be used to facilitate automated transmission of FDP packets. In one embodiment,
CPU 114 may provide multiple priority queues for transmitting packets. Each priority queue is implemented as a linked list that contains a set of descriptor entries. In one embodiment, one or more such linked list priority queues are assigned toFPH module 116 to facilitate transmission of FDP packets.FIG. 6 depicts an example of a linkedlist priority queue 600 that may be used byFPH module 116 to facilitate transmission of FDP packets according to an embodiment of the present invention. As depicted inFIG. 6 , linkedlist 600 comprises a set ofdescriptor entries 602. Eachentry 602 corresponds to and stores information for an FDP session for which an FDP packet is to be transmitted. Eachentry 602 comprises: (1) abuffer pointer 604 pointing to amemory location 614 storing the corresponding FDP packet; (2)buffer size information 606 identifying the size of the corresponding FDP packet; (3)timers information 608; (4) command/status information 610; and (5) apointer 612 pointing to the next entry in the linked list.Pointer 612 is used to traverse the entries in linkedlist 600. In one embodiment, linkedlist 600 may be implemented as a circular linked list whereinpointer 612 of the last entry in the linked list points to the first entry in the linked list. For a session,FPH module 116 uses the information stored in theentry 602 for the session to transmit FDP packets for that session in an automated manner that does not require CPU processing. -
Timers information 608 in an entry stores the trx_interval timer and the last_sent timer values for the FDP session corresponding to the entry. The trx_interval timer value for the session is initialized by software executed byCPU 114. As previously described, the trx_interval and last_sent timers are used byFPH module 116 to determine when to send an FDP packet for the session. - According to an embodiment of the present invention, a base timer may be associated with linked
list 600 used byFPH module 116 to transmit FDP packets. The base timer for a linked list determines the interval at which the entries in the linked list are visited and checked byFPH module 116. For example, if the base timer for linkedlist 600 depicted inFIG. 6 is 5 msecs, thenFPH module 116 visits each entry in the linked list every 5 msecs.FPH module 116 may start with one entry in the linked list and then usenext pointer 612 to traverse through the various entries in the linked list. For a linked list with an associated base timer, the trx_interval and last_sent timer values stored for each entry in the linked list may be expressed as multiples of the base timer value. For example, if the base timer value associated with linkedlist 600 is 5 msecs, then the trx_interval and last_sent timer values inentries 602 may be expressed as a multiple of thebase timer 5 msecs. For example, if the periodic time interval for transmitting an FDP packet for a session is 20 msecs, then trx_interval for that session may be expressed as (4* base timer). In one embodiment, the base timer for a linked list is determined based upon the trx_interval timers for the various session entries in the linked list as the least common denominator of the trx_interval timer values. - Command/
status information 610 may store other information related to the FDP session. For example, if the FDP session requires any special processing then that information may be stored ininformation 610. - Various other types of data structures may also be used to facilitate FDP packets transmission in alternative embodiments. For example, in one embodiment multiple linked lists may be used by
FPH module 116 to facilitate transmission of FDP packets, each with its own associated base timer. In one embodiment using two linked lists, one linked list may have an associated base timer of 1 msec and the other may have an associated base timer of 50 msecs. A session may be allocated to one of the two linked lists based upon the trx_interval timer values associated with the session. For example, an FDP session having a trx_interval timer of 100 msecs may be allocated to the linked list having an associated base timer of 50 msecs whereas an FDP session having a trx_interval timer of 6 msecs may be allocated to the linked list having an associated base timer of 1 msec. In one embodiment,FPH module 116 may also be configured to transmit FDP packets for all the FDP session entries in a liked list at once (referred to as a “one-shot” transmission). - New entries may be added to a transmission linked list as more FDP sessions are initiated. In one embodiment, when a new entry is to be added to a linked list, the transmit functionality is disabled for the linked list to which the entry is to be added. In one embodiment, a one-shot transmission may be first performed for the linked list prior to the disabling. The new entry is then added to the linked list. The transmit operations for the linked list, now with the new entry for a new session, are then enabled. The trx_interval timer information for a session entry in the linked list may also be changed by software executed by the CPU of a network device.
- As described above,
FPH module 116 offloads some of the FDP packets-related processing that was conventionally performed by software executed by a CPU of a network device. In the Rx path,FPH module 116 determines if an FDP packet received bynetwork device 102 needs to be provided toCPU 114 for processing. If it is determined that the FDP packet does not need to be forwarded toCPU 114 then the FDP packet is dropped. If instead, it is determined that the FDP packet needs to be forwarded toCPU 114 thenFPH module 116 forwards the packet toCPU 114. - Processing Using Dual Ring Structures
- Various data structures may be used by
FPH module 116 to facilitate processing of FDP packets in the Rx path. According to an embodiment of the present invention, a dual ring structure is used to facilitate the processing. A dual ring structure may comprise two rings, with each ring being a circular linked list of entries.FIG. 7 depicts a tworing structure 700 that may be used byFPH module 116 to facilitate processing of FDP packets in the receive (Rx) path according to an embodiment of the present invention. As depicted inFIG. 7 ,structure 700 comprises a first ring 702 (referred to as a CPU_assist ring) and a second ring 704 (referred to as the CPU ring).CPU_assist ring 702 comprises a number of entries storing information related to FDP packets received byFPH module 116. The processing ofCPU_assist ring 702 is handled byFPH module 116.CPU ring 704 comprises several entries storing information for FDP packets (and possibly for other packets) that are to be processed byCPU 114.CPU 114 handles the processing ofCPU ring 704. - The number of entries in the two rings may be user-configurable. The entries are sometimes referred to as descriptor entries as they store information describing FDP packets. The number of entries in
CPU_assist ring 702 is generally greater than the number of entries inCPU ring 704. -
CPU_assist ring 702 is used byFPH module 116 to process FDP packets received by the network device and byFPH module 116 in the Rx path.CPU_assist ring 702 comprises a number of entries (“m” entries depicted inFIG. 7 ) for storing information used for processing FDP packets. As depicted inFIG. 7 ,CPU_assist ring 702 may be implemented as a circular linked list of entries storing information related to FDP packets. The FDP packets themselves may be buffered inbuffer memory 710. When an FDP packet is received by a network device, the packet is stored inbuffer memory 710 that is accessible toFPH module 116 and information corresponding to the buffered FDP packet is stored in an entry ofCPU_assist ring 702.FPH module 116 then manages processing of the FDP packets using the entries inCPU_assist ring 702. -
Buffer memory 710 used for buffering the FDP packets may be located inFPH module 116 or in some other location accessible toFPH module 116. In embodiments where the memory resources ofFPH module 116 are limited,buffer memory 710 may be stored for example in a memory (e.g., SDRAM 206) associated withCPU 114. - In one embodiment, each entry in
CPU_assist ring 702 for an FDP packet buffered inmemory 710 comprises the following information: (1) abuffer pointer 708 pointing to the location inbuffer memory 710 storing the FDP packet corresponding to the entry; (2) a “processed bit” 706 indicating if the FDP packet corresponding to the entry has been processed byFPH module 116; and (3) anext pointer 712 pointing to the next descriptor entry inCPU_assist ring 702. - Processed bit 706 in an entry is used to identify the processing status of the FDP packet corresponding to the entry. In one embodiment, if the bit is set to 0 (zero), it indicates that the FDP packet corresponding to the entry needs to be processed. If the bit is set to 1 (one), it indicates that the FDP packet for the entry has already been processed and the entry is available for storing information for a new FDP packet. The bit is set to 1 (one) after the FDP packet has been processed.
- A process_start_address pointer and a dma_start_addr pointer may also be provided (not shown in
FIG. 7 ) and function as read and write pointers forCPU_assist ring 702 respectively. The dma_start_addr points to the entry inring 702 that is available for storing information for an incoming FDP packet. The process_start_address points to the next entry inring 702 that is available for storing information for an incoming FDP packet.FPH module 116 uses these pointers to traverseCPU_assist ring 702 and process entries corresponding to buffered FDP packets. -
FPH module 116 traversesCPU_assist ring 702 at regular time intervals to process FDP packets corresponding to entries inCPU_assist ring 702. For an unprocessed entry (as indicated by processed bit set to 0 in the entry),FPH module 116 uses the buffer pointer of the entry to access the corresponding FDP packet stored inbuffer memory 710. A portion of the FDP packet is then selected and compared to information stored in reference information for the FDP. As described above, if there is a match, it indicates that the FDP packet need not be provided toCPU 114 and can be dropped. In this event, processed bit 706 of the entry inCPU_assist ring 702 is set to 1 to indicate that the FDP packet corresponding to the entry has been processed and the FDP packet is dropped. - If there is no match, it indicates that the FDP packet is to be provided to
CPU 114. In this case, a buffer swap is performed between the buffer pointed to by the entry inCPU_assist ring 702 and a free entry inCPU ring 704. In one embodiment, as a result of the swap, a buffer pointer in a previously available entry inCPU ring 704 is made to point to a buffer memory location pointed to by the buffer pointer in the entry inCPU_assist ring 702. In this manner, after the buffer swap, a buffer pointer in an entry inCPU ring 704 now points to the location of the buffered FDP packet. For example, inFIG. 7 ,buffer pointer 714 ofCPU ring 704 points to the FDP packet stored inbuffer memory 710.CPU 114 may then access the FDP packet frombuffer memory 710 and process the FDP packet. After the buffer swap, processed bit 706 in the entry inCPU_assist ring 702 is set to 1 to indicate that the entry is available for storing information for a new FDP packet and the buffer pointer for the entry is freed. - There may be situations where there are no available entries in
CPU ring 704 for performing the buffer swap. This may occur for example whenCPU 114 is backed up in its processing and is unable to process the FDP packets pointed to by entries inCPU ring 704 in a timely manner. This scenario may arise due to the rate at which FDP packets are received by the network device exceeding the rate at whichCPU 114 is able to process the FDP packets. In such a scenario,FPH module 116 drops the buffered FDP packet corresponding to the entry inCPU_assist ring 702 whose pointer is to be swapped.FPH module 116 then continues processing of the next entry inCPU_assist ring 702 corresponding to the next unprocessed FDP packet. In this manner,FPH module 116 is able to continue processing the incoming FDP packets even ifCPU 114 is backed up. This minimizes the number of incoming FDP packets that are dropped due toCPU 114 being busy. - The dual ring structure depicted in
FIG. 7 and described above decouples receipt of FDP packets bynetwork device 102 from processing of FDP packets byCPU 114 of the network device. FDP packets received by a network device are buffered inbuffer memory 710 and corresponding entries stored inCPU_assist ring 702 which is handled byFPH module 116. Buffering of FDP packets and processing of the packets byFPH module 116 is done separately from the processing of FDP packets performed byCPU 114 usingCPU ring 704. In this manner,CPU 114 may continue to process FDP packets (or perform other functions) usingCPU ring 704 while FDP packets are being received and buffered by the network device. The decoupling enables FDP packets to be received without being concerned about the status ofCPU 114. Accordingly, FDP packets may be received by a network device at a rate that is faster than the rate at which the CPU of the network device can process the FDP packets. Even ifCPU 114 is backed up processing FDP packets or performing other tasks, FDP packets may continue to be received and processed byFPH module 116 usingCPU_assist ring 702. As a result, incoming FDP packets do not have to be dropped due toCPU 114 being tied up with other processing activities (including processing of previously received FDP packets). This is particularly useful given the bursty nature of FDP packets. The decoupling also enablesCPU 114 to process FDP packets without being hindered by the frequency at which the FDP packets are received by the network device. Further, only those FDP packets that need to be sent toCPU 114 are sent toCPU ring 704 fromCPU_assist ring 702. In this manner,CPU 114 does not see or process FDP packets that do not need to be sent toCPU 114. -
FIG. 8 is simplified block diagram of aFPH module 116 according to an embodiment of the present invention.FPH module 116 includes a number of modules including aTM Interface module 802, aPacket Inspection module 804, a Receive (Rx)Handler module 806, a Transmit (Tx)Handler module 808, and aCPU interface module 810.FIG. 8 is merely illustrative of an embodiment incorporating the present invention and does not limit the scope of the invention as recited in the claims. One of ordinary skill in the art would recognize other variations, modifications, and alternatives.FPH module 116 may be incorporated in a network device such as a switch or router, such as routers and switches provided by Foundry Networks®, Inc. of Santa Clara, Calif. -
TM Interface module 802 provides an interface for receiving packets from and transmitting packet toTM module 204. In the Rx path,TM Interface module 802 receives CPU-bound packets, including FDP packets, fromTM module 204. The incoming packets may be buffered in Rx FIFO 816 for analysis.TM Interface module 802 identifies FDP packets from the CPU-bound packets received fromTM module 204. Packets that are not FDP packets are forwarded toRx handler module 806 for forwarding toCPU 114. For a packet identified as an FDP packet,TM Interface module 802 presents a portion of the FDP packet toPacket Inspection module 804 for analysis. In one embodiment, this is done by presenting an offset into the FDP packet toPacket Inspection module 804. The offset is programmable and may be different for different FDPs. The portion of the FDP packet presented toPacket Inspection module 804 may include a portion of the header of the FDP packet, a portion of the payload of the FDP packet, or even the entire FDP packet. The portion of the FDP packet generally includes the session identifier for the packet. -
Packet Inspection module 804 is configured to take the portion of the FDP packet received fromTM Interface module 802 and compare information in the portion with reference information that has been programmed by software running onCPU 114. The reference information may be stored by Packet Inspection module 804 (e.g.,reference information 812 depicted inFIG. 8 ) or alternatively may be stored in a memory location accessible toPacket Inspection module 804. In one embodiment, the reference information may store one or more session entries for different FDP sessions. -
Packet Inspection module 804 may use an indexing scheme to perform the compare operation. In one embodiment, a part of the portion of the FDP packet received fromTM Interface module 802 is used as an index into the reference information to identify an entry in the reference information corresponding to a particular session. The size of the index may vary based upon the number of session entries in the reference information. For example, a 9-bit index is needed for indexing 512 reference information entries. The information stored in a particular session entry identified using the index is then compared to the information in the portion of the FDP packet received fromTM Interface module 802 to determine if there is a match. Results of the match are provided toTM Interface module 802. The results identify whether or not the information in the portion of the FDP packet matched the information in the particular session entry indexed by the FDP packet portion. - As described above,
TM Interface module 802 receives a result response fromPacket Inspection module 804 indicating whether or not the FDP packet information matched the corresponding information in the reference information. If the received result indicates a match, then this indicates toTM Interface module 802 that the particular FDP packet can be dropped and need not be forwarded toCPU 114.TM Interface module 802 then drops the FDP packet and flushes Rx FIFO 816 buffers corresponding to the FDP packet. The FDP packet is dropped without notifyingCPU 114 about the packet. If the result received fromPacket Inspection module 804 indicates that the FDP packet information did not match information in the session entry in the reference information,TM Interface module 802 forwards the FDP packet toRx handler module 806 for forwarding toCPU 114. -
TM Interface module 802 is also configured to flag an error when an FDP packet for an FDP session is not received within a periodic time interval corresponding to the FDP session. In one embodiment, for each FDP session handled by the network device,TM Interface module 802 stores information (e.g., timers information) tracking when the last FDP packet for the session was received and when the next FDP packet is due to be received. If the next FDP packet for that session is not received within the time interval for that FDP session, then an error is flagged.CPU 114 may be notified about the error. -
Rx Handler 806 is configured to receive CPU-bound packets, including FDP packets, fromTM Interface module 802 and provide the packets toCPU Interface module 810 for forwarding toCPU 114.Rx Handler 806 may also comprise a FIFO for storing the CPU-bound packets before being forwarded toCPU 114. -
CPU Interface module 810 is configured to forward packets toCPU 114. In one embodiment, a DMA technique is used to forward packets toCPU 114. In such an embodiment,CPU Interface Module 810 acts as a DMA engine that DMAs the packets toCPU 114. In one embodiment, the packet is written to amemory 206 associated withCPU 114 from where the packet can be accessed byCPU 114. Different interfaces may be used to forward packets fromFPH module 116 toCPU 114. For example, in one embodiment, a PCI bus interface may be used to forward packets toCPU 114. In such an embodiment,CPU Interface Module 810 may comprise PCI-related modules for forwarding packets toCPU 114. In one embodiment, the DMA engine is part ofRx handler 806 andCPU interface module 810 initiates the DMA process. -
CPU Interface Module 810 is also configured to receive packets fromCPU 114. These packets are then forwarded toTx Handler module 808.Tx Handler module 808 may comprise a FIFO for storing the packets. The packets are then forwarded toTM Interface module 802. In one embodiment,Tx Handler module 808 comprises a DMA engine that retrieves FDP packets from the CPU SDRAM.TM Interface module 802 may comprise aTx FIFO 818 for storing the packets prior to transmission. A descriptor entries scheme may be used for retrieving and storing the packets.TM Interface module 204 then forwards the packets toTM module 204. The packets may then be forwarded to the appropriate destination ports and transmitted fromnetwork device 102 via the destination ports. - According to an embodiment of the present invention,
Tx Handler module 808 is configured to handle transmission of FDP packets fromnetwork device 102 for various FDP sessions. In one embodiment,Tx Handler module 808 maintains a pair of timers for each FDP session handled by the network device. As previously described, the pair of timers may include a trx_interval timer that indicates that transmission interval for transmitting an FDP packet for that FDP session and a last_sent timer that is used to monitor the time when an FDP packet was last transmitted by the network device for the FDP session. The two timers for each session are iteratively checked at periodic intervals to determine when to transmit an FDP packet for each session. -
Tx Handler module 808 may use different structures to facilitate automated transmission of FDP packets. For example, in one embodiment, one or more circular linked lists (such as linkedlist 600 depicted inFIG. 6 and described above) may be provided to facilitate the transmission. Multiple linked lists may also be used, each with an associated base timer. The base timer for a linked list determines the frequency at whichTx Handler 808 visits and checks the entries in the linked list. For example, a list having an associated base timer of 1-msec is checked every 1-msec, a list having an associated base timer of 50 msecs is checked every 50 msecs, a list having an associated base timer of 200 msecs is checked every 200 msecs, and so on. In one embodiment, two linked lists are used: a first linked list having a 1 millisecond based timer and a second linked list having a 50 milliseconds base timer may be used. The entries in the 1-msec linked list are checked byTx Handler module 808 every 1 msec. This linked list may store entries for FDP sessions whose periodic transmission intervals are multiples of 1 msec, e.g., 4 msecs, 15 msecs, etc. The 50-msec linked list entries are checked byTx Handler module 808 every 50 msecs. This linked list may store entries for FDP sessions whose periodic transmission intervals are multiples of 50 msecs, e.g., 100 msecs, 250 msecs, etc. - The FDP packets transmitted by
Tx Handler 808 are forwarded toTM Interface module 802 and then toTM module 204. The FDP packets are then forwarded to one or more ports of the network device and then transmitted from the network device using the one or more ports. - As described above, embodiments of the present invention reduce the amount of FDP packets-related processing that a CPU of a network device has to perform. For incoming FDP packets,
FPH module 116 assists the CPU by reducing the number of incoming FDP packets that a CPU has to process.FPH module 116 is also able to flag when an FDP packet for an FDP session is not received within the periodic time interval for the session.FPH module 116 also handles transmission of FDP packets for various sessions at regular time intervals. The FDP packets transmission task is thus offloaded from the CPU of the network device. This further reduces the processing cycles that the CPU of the network device has to spend on FDP-packets related processing. This enables the network device to be able to support newer FDPs such as 802.1ag and BFD having very short periodic time intervals for transmission of FDP packets (e.g., faster than 1 second, more typically in milliseconds such as 1 millisecond, 5 milliseconds, or even shorter) without adversely affecting CPU performance. Accordingly, embodiments of the present invention enable a network device to process reception and transmission of FDP packets that may be received and transmitted at a rate faster than 1 FDP packet per second. Embodiments of the present invention are able to handle FDPs having periodic time intervals that may be one or more milliseconds (msecs), one or more seconds, or other shorter or longer time intervals. - As previously indicated, there are several different types of FDPs. Examples include BFD and 802.1ag. The following sections of the application describe embodiments of present invention for BFD and 802.1ag packets processing.
- Processing of Bidirectional Forwarding (BFD) Protocol Packets
- As previously described, BFD is a type of FDP.
FIG. 9 depicts a format for a BFD packet. A BFD packet is delineated by a Start of Packet (SOP) and an End of Packet (EOP) field. A BFD packet is generally transmitted in a unicast, point-to-point mode. As depicted inFIG. 9 , a BFD packet comprises aUnicast header 902, aninternal header 904, aDestination MAC 906, asource MAC 908, anEtherType field 910, an IP header (IPv4 or IPv6) 912, aUDP header 914, aBFD header 916, anddata 918. -
EtherType Field 910 indicates whether the IP Header is IPv4 or IPv6. For example, a value of 0x0800 indicates IPv4 while 0x86DD indicates IPv6. In case of an IPv4 packet,IP header field 912 comprises 20 bytes of an IPv4 header (as specified by the IPv4 protocol). In case of an IPv6 packet,IP header field 912 comprises 40 bytes of an IPv6 header (as specified by the IPv6 protocol). -
UDP header section 914 of the packet is used byFPH module 116 to identify a packet as a BFD packet. The following Table A shows the contents ofUDP header section 914. -
TABLE A UDP Header Format Field Size (bits) Purpose Checksum 16 UDP checksum. Source Port 16 A free port on the sender's machine where any responses should be sent. Destination Port 16 This field identifies the destination program on the server this packet should be directed to. This value is (decimal) 3784 for BFD control and (decimal) 3785 for BFD echo packets. Message Length 16 Total size of UDP header plus data payload (but not the IP header) in 8-bit chunks (aka bytes or octets).
A BFD echo packet is addressed to the router who is sending it, so that the next-hop router will send the packet back to the initiating router.FPH module 116 uses the “Destination Port” field to identify a packet as a BFD packet. -
FIG. 10 depicts the format forBFD header field 916. The various fields in the BFD header field include: - (1) Version (3-bit): The version number of the protocol.
- (2) Diagnostic (Diag) (5-bit): A diagnostic code specifying the local system's reason for the last session state change. This field allows remote systems to determine the reason that the previous session failed. Values are: 0—No Diagnostic; 1—Control Detection Time Expired; 2—Echo Function Failed; 3—Neighbor Signaled Session Down; 4—Forwarding Plane Reset; 5—Path Down; 6—Concatenated Path Down; 7—Administratively Down; 8—Reverse Concatenated Path Down; 9-31—Reserved for future use.
- (3) State (STA) (2-bit): The current BFD session state as seen by the transmitting system. Values are: 0—AdminDown; 1—Down; 2—Init; 3—UpPoll (P) (1-bit): If set, the transmitting system is requesting verification of connectivity, or of a parameter change. If clear, the transmitting system is not requesting verification.
- (4) Final (F) (1-bit): If set, the transmitting system is responding to a received BFD Control packet that had the Poll (P) bit set. If clear, the transmitting system is not responding to a Poll.
- (5) Control Plane Independent (C) (1-bit): If set, the transmitting system's BFD implementation does not share fate with its control plane. If clear, the transmitting system's BFD implementation shares fate with its control plane.
- (6) Authentication Present (A) (1-bit): If set, the Authentication Section is present and the session is to be authenticated.
- (7) Demand (D) (1-bit): If set, the transmitting system wishes to operate in Demand Mode. If clear, the transmitting system does not wish to or is not capable of operating in Demand Mode.
- (8) Reserved (R) (1-bit): This bit must be zero on transmit, and ignored on receipt. Detect Multiple (8-bit): Detect time multiplier. The negotiated transmit interval, multiplied by this value, provides the detection time for the transmitting system in Asynchronous mode.
- (9) Length (8-bit): Length of the BFD Control packet, in bytes.
- (10) My Discriminator (32-bit): A unique, nonzero discriminator value generated by the transmitting system, used to demultiplex multiple BFD sessions between the same pair of systems.
- (11) Your Discriminator (32-bit): The discriminator received from the corresponding remote system. This field reflects back the received value of My Discriminator, or is zero if that value is unknown.
- (12) Desired Min TX Interval (32-bit): This is the minimum interval (in microseconds) that the local system would like to use when transmitting BFD Control packets.
- (13) Required Min RX Interval (32-bit): This is the minimum interval, in microseconds, between received BFD Control packets that this system is capable of supporting.
- (14) Required Min Echo RX Interval (32-bit): This is the minimum interval, in microseconds, between received BFD Echo packets that this system is capable of supporting. If this value is zero, the transmitting system does not support the receipt of BFD Echo packets.
- In the receive (Rx) path,
TM Interface module 802 determines if an incoming packet is a BFD packet based upon the “Destination Port” information in the UDP header portion of the packet.TM Interface module 802 then determines if the BFD packet should be dropped (or terminated) or otherwise should be sent toCPU 114 for inspection. As part of this determination,TM Interface module 802 presents a portion of the BFD packet toPacket Inspection module 804. Generally, an offset into the BFD packet is provided toPacket Inspection module 804. -
Packet Inspection module 804 then compares the information in the BFD packet portion received fromTM Interface module 802 to information stored in the reference information to see if there is a match. In one embodiment, the reference information for BFD packets comparison is stored byFPH module 116 and comprises 512 BFD session entries, each entry 12-bytes long.FIG. 11 depicts amemory structure 1100 storing BFD reference information for multiple BFD sessions according to an embodiment of the present invention. As depicted inFIG. 11 , eachentry 1102 stores information for a BFD session and has a 12-byte header 1104 and countersinformation 1106. The BFD reference information for each session may be configured by software executed byCPU 114 and used byTM Interface module 802 for the comparison. -
Packet Inspection module 804 uses an index to select which one of the 512 reference information session entries ofstructure 1100 is to be selected for comparison with BFD packet information. As previously described, a BFD packet has a 24-byteBFD header section 916. The 24-byte header section or a portion thereof (e.g., a 12-byte section of the BFD header) may be used as an index. In one embodiment, the least significant 9 bits of the “Your Discriminator” of the BFD header section of a BFD packet that are unique per BFD session are used by theTM Interface module 802 as an index to the BFD reference memory structure. The size of the index depends upon the number of entries stored in the BFD reference information. In alternative embodiments, any unique portion of the BFD packet may be used as an index. - The index, which is based upon a portion of the BFD packet, is then used to identify a particular session entry in the BFD reference information. The reference information from the selected session entry is then compared to the information in the portion of the BFD packet received by
Packet Inspection module 804 to see if there is a match. For example, for an entry inmemory structure 1100 depicted inFIG. 11 , the 12 header bytes of the entry are used for the comparison.Packet Inspection module 804 then sends a signal toTM Interface module 802 indicating the result of the comparison. - If
TM Interface module 802 receives a signal fromPacket Inspection module 804 indicating a match, then the particular BFD packet is dropped or terminated. In this manner, the BFD packet is not forwarded toCPU 114. If the signal received fromPacket Inspection module 804 indicates that there was no match, it indicates toTM Interface module 802 that the BFD packet needs to be forwarded toCPU 114 for inspection and processing.TM Interface module 802 then forwards the BFD packet toCPU 114 viaRx Handler 806 andCPU Interface Module 810. -
FPH module 116 is also configured to flag non-receipt of BFD packets for a BFD session. In one embodiment, this may be performed byTM Interface module 802. This is facilitated by counter information 1006 that is included in each session entry in theBFD reference information 1100 as depicted inFIG. 11 .FIG. 12 depicts contents ofcounter information 1106 for a BFD session entry according to an embodiment of the present invention. As depicted inFIG. 12 ,counter information 1106 includes aninterval_limit timer 1202 and alast_received timer 1204.Field 1202 is typically programmed by software executed byCPU 114.Interval_timer 1202 indicates the interval_limit within whichFPH module 116 should receive an FDP packet for that session.Last_received timer 1204 is used byFPH module 116 to monitor the time that it has waited to receive an FDP packet for the session. When a BFD packet is received for a session (i.e., when the information for a received BFD packet matches the reference information in the session entry) the last_received timer in the entry is reset. Other timers may also be provided in alternative embodiments. For example, a timer may be provided to count the number of times that the interval_limit timer value has been exceeded. -
FPH module 116 iteratively checks the counters information for the various BFD session entries inmemory structure 1100. WhenFPH module 116 determines for a session thatlast_received timer 1204 for the session reaches or exceedsinterval_limit timer 1202, it indicates that a BFD packet for the session was not received in the expected time interval andFPH module 116 signals this error condition toCPU 114. In one embodiment, an interrupt is generated byFPH module 116 to flag that the particular BFD session has expired and there may be some failure in the network (e.g., a link is down). In this manner, non-reception of a BFD packet for a session is detected and flagged. -
Counters information 1106 is monitored and checked byFPH module 116 on a periodic basis for the BFD entries. During a check,FPH module 116 walks through the session entries in theBFD reference information 1100 and checks the timers for each entry. In one embodiment, the frequency at which the checks are repeated is user-programmable. The frequency may also be determined automatically based upon the interval_limit timers for the sessions. For example, in one embodiment, the iteration frequency is set to the least common denominator of the various interval_limit timers being monitored for the various sessions byFPH module 116. In this manner, the frequency is programmable and/or may be automatically determined from the interval_limit timers information for the BFD sessions in the reference information. - In the transmit (Tx) path,
FPH module 116 is configured to perform automated transmission of BFD packets for the various BFD sessions. In one embodiment, this may be performed byTx handler 808. In one embodiment, a memory structure such as linkedlist 600 depicted inFIG. 6 and described above may be used to facilitate the automated transmission of BFD packets for different BFD sessions. In alternative embodiments, other types of memory structures may be used. The BFD packets transmitted byTx Handler module 808 are forwarded toTM Interface module 802 and then toTM module 204. The BFD packets are then forwarded to one or more ports of the network device. The BFD packets are then transmitted from the network device using the one or more ports of the network device. - Processing of 802.1ag Packets
- As previously indicated, 801.1ag packets are a type of FDP packets. The 802.1ag standard specifies protocols, procedures, and managed objects to support transport fault management. These allow discovery and verification of the path, through bridges and LANs, taken for frames addressed to and from specified network users, detection, and isolation of a connectivity fault to a specific bridge or LAN. 802.1ag Connectivity Fault Management (CFM) provides capabilities for detecting, verifying and isolating connectivity failures in multi-vendor networks.
FPH module 116 assists the CPU of a network device in processing 802.1ag packets, both in processing of incoming 802.1ag packets (e.g., determining if an 802.1ag packet should be forwarded to the CPU) and transmission of 802.1ag packets. -
FPH module 116 is capable of supporting multiple types (e.g., five different types in one embodiment) of 802.1ag packets.FIGS. 13A and 13B depict formats for two types of 802.1ag packets that may be processed by an embodiment of the present invention. The format depicted inFIG. 13A is for an 802.1ag packet received from VPLS/VLL uplink. The format depicted inFIG. 13B is for an 802.1ag packet received from a regular link. - Each 802.1ag packet has a data section (e.g.,
section 1302 depicted inFIG. 13A andsection 1304 depicted inFIG. 13B ) that is used byFPH module 116 for analysis.FPH module 116 determines the offset within an 802.1ag packet to access the data section of the packet.FIG. 14 depicts contents of an 802.1ag data section. The data section comprises a “Sequence Number”field 1402 that is incremented each time an 802.1ag packet is transmitted. Accordingly,sequence number 1402 changes with each transmission of an 802.1ag packet. This changing field has to be taken into account when performing comparisons to determine whether an 802.1ag packet it to be forwarded to a CPU and also while transmitting 802.1ag packets. -
FPH module 116 identifies a packet as an 802.1ag packet using an 802.1ag packet reference information table.FIG. 15 depicts an 802.1ag packet reference table 1500 according to an embodiment of the present invention. Table 1500 may be stored byFPH module 116 or in some location accessible toFPH module 116. As depicted inFIG. 15 , each entry in table 1500 has the following content: - (1) Etype 1 (2-bytes): This is the first Etype field after the Source MAC in the 802.1ag packet header. This field is 0x8847 for VPLS/VLL uplink and 0x8902 for a regular link. This field is used in the comparison performed by
FPH module 116 to determine if an 802.1ag packet needs to be sent to the CPU for processing and whether it can be dropped. - (2) Etype 2 Option (1-byte): This field consists of a 1-bit check field and a 7-bit offset field. If the check bit is set, the offset field indicates the number of bytes after
Etype 1 whereEtype 2 can be found. If the incoming packet is from a VPLS/VLL,FPH module 116 checks the MPLS label stack for the S bit. If the bit is 0, 4-bytes will get added to the offset field. - (3) Etype 2 (2-bytes): This is compared against an incoming packet's second Etype field if the check bit is set in the
Etype 2 Option's field. - (4) Etype 3 Option (1-byte): This field consists of a 1-bit check field and a 7-bit offset field. If the check bit is set, the offset field indicates the number of bytes after
Etype 1 whereEtype 3 can be found.Etype 3 is considered to be 0x8902 and the 802.1ag Data always starts after it. - (5) SMAC Option (1-byte): This field consists of a 1-bit check field and a 7-bit offset field. If the check bit is set, the offset field indicates the number of bytes from the last Etype where SMAC can be found.
- In one embodiment,
FPH module 116 uses the 802.1ag packet reference table to determine if an incoming packet is an 802.1ag packet. If the packet is determined to be an 802.1ag packet, then the packet is buffered and an entry for the packet created in the CPU_assist ring depicted inFIG. 7 . The 802.1ag packet is then processed as previously described with regards toFIG. 7 . A portion of the 802.1ag packet is used to perform a comparison with reference information. As described above, if there is a match, it indicates that the 802.1ag packet need not be provided toCPU 114 and can be dropped. If there is no match, it indicates that the 802.1ag packet is to be provided toCPU 114. In this case, a buffer swap is performed between the buffer pointed to by the entry in CPU_assist ring and a free entry in CPU ring, as previously described.CPU 114 may then access the 802.1ag packet frombuffer memory 710 and process the packet. - The use of the dual ring structure depicted in
FIG. 7 and described above may be used for processing incoming 802.1ag packets. This enables the network device to receive 802.1ag packets even when the CPU of the network device is unable to keep up with the processing of the packets. The incoming 802.1ag packets stored inCPU_assist ring 702 are processed byFPH module 116 to determine whether the packets need to be forwarded to the CPU of the network device for further processing. - In one embodiment, various checks are made to determine whether an 802.1ag packet needs to be forwarded to the CPU for processing.
FPH module 116 first checks the Opcode field (depicted inFIG. 14 ) of the packet. If Opcode is 1, the 802.1ag packet is a Continuity Check Message (CCM) and further comparisons are performed. Else, if the Opcode is not 1, then the packet is forwarded to the CPU for further processing. - As indicated above, if the 802.1ag packet is determined to be a CCM packet, then further comparisons are performed to determine if the packet needs to be forwarded to the CPU of the network device. In one embodiment, the reference information against which the comparisons are performed includes a hash table and a sessions table. The hash table and memory table may be stored in a memory location accessible to
FPH module 116 and are initialized by software executed by the CPU of the network device. In one embodiment, the hash table and sessions table may be stored in RAM (e.g., SDRAM) associated with the CPU. -
FIG. 16 depicts contents of a hash table 1602 and sessions table 1604 storing reference information according to an embodiment of the present invention. As depicted inFIG. 16 , as part of the processing, aportion 1606 of an 802.1ag packet is fed to ahash function 1608 to generate ahash index 1610. In one embodiment, the portion of the 802.1ag packet that is fed to hashfunction 1608 includes bytes 9-10 (MEPID), and bytes 13-17 and bytes 36-58 (MAID) (seeFIG. 14 ) of the header of a CCM 802.1ag packet. In one embodiment,hash function 1608 yields an 8-bit hash value 1610 that represents an index to anentry 1612 within hash table 1602.FPH module 116 then uses information in the entry within hash table 1602 to find an index to an entry in sessions table 1604. - According to an embodiment of the present invention, each
entry 1612 in hash table 1602 comprisespacket reference information 1614 to be used for comparison, asession table pointer 1616 pointing to an entry in sessions table 1604, and anext pointer 1618 pointing to the next entry in hash table 1602. In one embodiment,packet reference information 1614 comprises 50 bytes corresponding to bytes 9-10 of MEPID, and bytes 13-17 and 36-58 of MAID from a CCM 802.1ag packet. In this embodiment, after an entry in hash table 1602 has been identified byhash index 1610 for a received 802.1ag packet, bytes 9-10 of MEPID, and bytes 13-17 and 36-58 of MAID from the received 802.1ag packet are compared with the 50bytes 1614 stored in the hash table entry indexed by the 8-bit hash result. If the received packet information matches thepacket reference information 1614 stored in the hash table entry, thensession table pointer 1616 of the hash table entry is used to identify an entry in sessions table 1604. If there is no match, then the entries in hash table 1602 may be traversed usingnext pointer 1618 until a matching packet reference information is identified or until all entries have been traversed. Thesession table pointer 1616 of the entry comprising the matching packet reference information is then used to identify an entry in sessions table 1604. If no matching information is found in the hash table, then the received 802.1ag packet is forwarded to the CPU of the network device. - As depicted in
FIG. 16 , sessions table 1604 may store a number of entries, each entry corresponding to an 802.1ag session. In one embodiment, sessions table 1604 stores 256 entries. According to an embodiment of the present invention, each entry in sessions table 1604 comprises the following information: - (1) Ownership (1-bit): The ownership bit is used to indicate if
FPH module 116 can modify the sequence number of the entry. When the bit is set, the session can be used byFPH module 116. - (2) Accept (1-bit): When this bit is set,
FPH module 116 disregards the sequence number of the first 802.1ag packet matching the session.FPH module 116 saves the incremented CCM packet sequence number in the session entry and resets the accept bit. - (3) Version (5-bits): If the version field in the session table entry does not match the corresponding information in the received 802.1ag packet, the packet is forwarded to the CPU.
- (4) Flags (8-bits): If this field in the session table entry does not match the corresponding information in the received 802.1ag packet, the received packet is sent to the CPU.
- (5) Sequence number (32-bits): Software executing on the CPU initializes a value. When the Accept bit is set,
FPH module 116 accepts whatever sequence number it sees and stores it in the session entry and then resets the Accept bit. When the Accept bit is not set (i.e., is zero),FPH module 116 checks to see if the sequence number of an incoming 802.1ag packet is 1 greater than the stored sequence number in the session table entry. If true, the sequence number of the incoming packet is correct. If the ownership bit is 1, the sequence number value is incremented and saved into the sessions table entry, so that the right value is available for comparison for that session for the next received 802.1ag packet that will also have an incremented sequence number. If sequence number of an incoming 802.1ag packet is not 1 greater than the stored sequence number in the session table entry, there is a potential problem and a packet with the correct expected sequence number may have been dropped. In this case, the new sequence number of the packet is stored in the session entry in the session status FIFO (described below), but the received 802.1ag packet is not forwarded to the CPU. The updating of the sequence number in the session table entry prevents every packet, after a mismatch of sequence numbers, of being treated as a mismatch and being forwarded to the CPU. - (6) Source Port (10-bits) and VC Label (20-bits): Source port of a packet is internal header bits 64-73 and VC label is MPLS stack bits 0-19. An incoming 802.1ag packet is sent to the CPU if the field checks below against the session entry do not match:
-
- i) For packets coming from VPLS/VLL link (outer Etype is 0x8847 and Inner Etype is 0x8902)
FPH module 116 checks the VC label. - ii) For packets coming from regular link (Etype is 0x8902),
FPH module 116 checks the Source Port.
- i) For packets coming from VPLS/VLL link (outer Etype is 0x8847 and Inner Etype is 0x8902)
- (7) Source MAC (6-bytes): It can be outer or inner Source MAC.
- (8) Session Status (8-bits): These bits are set by
FPH module 116 and encode conditions related to the session corresponding to the sessions table entry. The conditions are: -
8′h01=Session timeout -
8′h02=Sequence number mismatch - (9) SW timer (16-bits) (referred to above as the interval_limit timer): This field is set by software executed by the CPU and indicates the time interval that an 802.1ag packet is expected to be received in for that session. This may be expressed as a multiple of some base timer. This is same as the interval_limit timer previously described.
- (10) HW timer (16-bits) (referred to above as the last-received timer): This field is used by
FPH module 116 to keep track of aging, i.e., the time that an 802.1ag packet matching the session has not been received. It is reset byFPH module 116 every time it processes a matching 802.1ag packet whether it is dropped or sent to the CPU. This is same as the trx_interval timer previously described. - (11) Error counter (8-bits): This field is incremented by
FPH module 116 every time there is a Sequence number mismatch. At a programmable interval,FPH module 116 writes the Session pointer of a session entry and the non-zero Error counter into the Session Status FIFO. - (12) Session counter (16-bits): This field keeps track of how many packets matching a session have been received. This field is incremented by
FPH module 116 every time a packet matching the session is received. Software executing on the CPU of the network device may reset the timer when it takes over the ownership of the session. - As previously described, if the received packet information matches the
packet reference information 1614 stored in the hash table entry,session table pointer 1616 of the hash table entry is used to identify an entry in session table 1604. The reference information in the session table entry is then compared to information in the packet. In one embodiment, one or more fields of the particular session table entry are compared to corresponding fields of the received packet. If the compared information matches, then the received packet is dropped and not forwarded to the CPU. If the compared information does not match, then the packet is forwarded to CPU. The fields of a session table entry that are compared to the corresponding information in a received packet may differ based upon the type of the received packet, for example, the type of 802.1ag packet. In this manner, a received 802.1ag packet is dropped if information from the packet matchesreference information 1614 of anentry 1612 in hash table 1602 and information from the packet also matches reference information in a session table entry pointed to bysession table pointer 1616 of the matchinghash table entry 1612—else, the packet is not dropped and forwarded to the CPU for processing. - As depicted in
FIG. 16 , a linkedlist 1620 is provided that enablesFPH module 116 to walk through the entries in sessions table 1604 in order to determine if an 802.1ag packet has not been received within the expected time interval for each of the sessions. For each session entry,FPH module 116 compares the hw_timer value for the entry with the sw_timer value for the entry. If the sw_timer and hw_timer are the same for a session entry, it indicates that an 802.1ag packet was not received within the time interval for that session and an error condition is flagged byFPH module 116. In one embodiment,FPH module 116 writes the session pointer into the Session Status FIFO that stores session pointers of the sessions that have had issues such as session timeouts or session sequence number mismatch, etc. and generates an interrupt. -
FIG. 17 depicts a format of a Session Status FIFO according to an embodiment of the present invention. As depicted inFIG. 17 , the session status FIFO entry comprises: - (1) Session Pointer (16-bits): Indicates the list significant 16 bits of the pointer where there is a sequence number mismatch.
- (2) Error Counter (8-bits): It is the same value as the Error Counter field in the Session Table entry. Relevant for Sequence number mismatch.
- (3) Used FIFO Entries (4-bits): Indicates the number of used FIFO entries in the Session Status FIFO in 32-bit increments i.e., 4′h0: 0-32 entries, 4′h1: 33-64 entries, . . 4′hF: 481-512.
- (4) Status (4-bits). This field indicates the condition that the entry was recorded for. The values are: 4′h1: Session timeout; 4′h2: Sequence number mismatch; Others: Reserved.
- In one embodiment, an 802.1ag packet is also sent to the CPU for processing if the following conditions below hold true: (1) The “First TLV Offset” (
byte 4 of the 802.1ag data section of a packet) is less than 70; or (2) If the “First TLV Offset” is equal to or more than 70 and the “Optional CCM TLVs” (byte 75 of CCM data) is not zero. - As indicated in
FIG. 14 , 802.1ag packets comprise a sequence number whose value is incremented with each transmitted 802.1ag packet for a session. Accordingly, when 802.1ag packets are transmitted, the sequence numbers of the packets have to be incremented with each packet transmission. According to an embodiment of the present invention,FPH module 116 performs processing to update the sequence number prior to transmission of 802.1 ag packets. -
FIG. 18 depicts a linkedlist 1800 that may be used byFPH module 116 to facilitate transmission of 802.1ag packets according to an embodiment of the present invention. Linkedlist 1800 comprises a set ofentries 1802 with each entry storing information for an 802.1ag session. Each entry comprises abuffer pointer 1804 pointing to amemory location 1820 storing the corresponding 802.1ag packet,buffer size information 1806 identifying the size of the corresponding 802.1ag packet,timers information 1808, command/status information 1810, offsetinformation 1812,other information 1814, and apointer 1816 pointing to the next entry in linkedlist 1800.Pointer 1816 is used to traverse the linked list. In one embodiment, linkedlist 1800 is a circular linked list whereinpointer 1816 of the last entry in the linked list points to the first entry in the linked list. -
Timers information 1808 in an entry stores the trx_interval timer and the last_sent timer values for the 802.1ag session corresponding to the entry. The trx_interval timer value for the session is initialized by software executed byCPU 114. As previously described, the trx_interval and last_sent timers are used to determine when to send an 802.1ag packet for the session. - According to an embodiment of the present invention, a base timer may be associated with linked
list 1800. The base timer determines the interval at which the entries in linkedlist 1800 are visited and checked byFPH module 116. For example, if the base timer for linkedlist 1800 depicted inFIG. 18 is 5 msecs, thenFPH module 116 visits each entry in linkedlist 1800 every 5 msecs. For a linked list with an associated base timer, the trx_interval and last_sent timer values are expressed as multiples of the base timer value. For example, if the base timer value associated with linkedlist 1800 is 5 msecs and the periodic time interval for transmitting an 802.1ag packet for a session is 20 msecs, then trx_interval may be represented as (4* base timer). In one embodiment, the base timer value for a linked list may be determined based upon the trx_interval timers for the various session entries in the linked list. - Command/
status information 1810 may store other information related to the 802.1ag session. For example, if the 802.1ag session requires any special processing then that information may be stored ininformation 1810. - Offset
information 1812 provides an offset into the 802.1ag packet pointed to bybuffer pointer 1804 pointing to information in the packet that needs to be changed prior to periodic transmission of the packet. Offsetinformation 1812 thus identifies the location within an 802.1ag packet that needs to be changed prior to transmission. For example, as previously described, the sequence number within an 802.1ag needs to be incremented with each transmitted 802.1ag packet. In such an embodiment, offsetinformation 1812 may provide an offset to a location in the 802.1ag packet storing sequence number information that needs to be incremented with every transmitted packet. In other types of FDP packets, other one or more offsets may be provided that may be used to access one or more sections or portions of the packet that need to be changed prior to transmission of the packet. - The sequence number information in an 802.1ag packet is incremented by
FPH module 116 with each transmission of an 802.1ag packet for that session. The initial sequence number value may be set by software executed by the CPU of a network device. Thesequence number information 1814 is then updated (e.g., incremented) after each 802.1ag packet transmission such that the updated value may subsequently be used for the next transmitted 802.1ag packet. In this manner, a parameter within an FDP packet may be updated with transmission of each FDP packet such that the correct parameter value is used for the next transmission. -
FIG. 19 depicts asimplified flowchart 1900 showing a method performed byFPH module 116 for transmitting 802.1ag packets according to an embodiment of the present invention. The processing depicted inFIG. 19 is performed byFPH module 116 for each entry in a transmission linked list (e.g., linkedlist 1800 depicted inFIG. 18 ) for every iteration when the entry is checked. For a session entry in the linked list, fromtimers information 1808 in the session entry,FPH module 116 checks if the last_sent timer has reached the trx_interval timer (step 1902). If it is determined in 1902, that the last_sent timer has not reached the trx_interval timer (i.e., the last_sent timer is less than the trx_interval timer), it is not time yet to transmit the 802.1ag packet and the last_sent timer is incremented (step 1904). The amount by which the last_sent timer is incremented depends upon the base timer associated with the linked list. For example, if the base timer is 5 msecs, then the last_received timer is incremented by 5 msecs. - If it is determined in 1902 that the last_sent timer has reached or exceeded the trx_interval timer for the session,
FPH module 116 prepares an 802.1ag packet for transmission. As part of this process,FPH module 116 first accesses the 802.1ag packet pointed to bybuffer pointer 1804 of the entry corresponding to the session (step 1906). Offsetinformation 1812 of the linked list entry is then used to locate the sequence number field within the 802.1ag packet accessed in 1906 (step 1908). An 802.1ag packet is then transmitted based upon the packet accessed in 1906 and having the sequence number located in 1908 (step 1910). As part of 1910,FPH module 116 may transmit the 802.1ag packet toTM module 204. The 802.1ag packet may then be forwarded to a port of the network device and transmitted from the network device via the port. - The sequence number located in 1908 in the packet accessed in 1906 is then incremented by one (step 1912). In this manner, an incremented sequence number is available for the next transmission of an 802.1ag packet for that session. The last_sent timer in
timer information 1808 for the entry is then reset to zero (step 1914) to restart the countdown to the next packet transmission. - As described above with respect to
FIG. 19 , the sequence number of an 802.1ag packet stored in the buffer is incremented with each transmission of an 802.1ag packet. In this manner, 802.1ag packets with the correct sequence number are transmitted. The technique described above with respect toFIG. 19 may also be used to change one or more fields of FDP packets prior to transmission, as necessitated by the FDPs. In alternative embodiments of the present invention, multiple linked lists may be used byFPH module 116 to facilitate transmission of 802.1ag packets. Each linked list may have its own associated base timer. - In the examples provided above, a linked list memory structure was used to facilitate transmission of FDP packets. Embodiments of the present invention are however not restricted to using linked lists. Other types of memory structures may also be used in alternative embodiments.
- Although specific embodiments of the invention have been described, various modifications, alterations, alternative constructions, and equivalents are also encompassed within the scope of the invention. The described invention is not restricted to operation within certain specific data processing environments, but is free to operate within a plurality of data processing environments. Additionally, although the present invention has been described using a particular series of transactions and steps, it should be apparent to those skilled in the art that the scope of the present invention is not limited to the described series of transactions and steps.
- Further, while the present invention has been described using a particular combination of hardware and software, it should be recognized that other combinations of hardware and software are also within the scope of the present invention. The present invention may be implemented only in hardware, or only in software, or using combinations thereof.
- The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense. It will, however, be evident that additions, subtractions, deletions, and other modifications and changes may be made thereunto without departing from the broader spirit and scope of the invention as set forth in the claim.
Claims (22)
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/953,745 US20090279441A1 (en) | 2007-01-11 | 2007-12-10 | Techniques for transmitting failure detection protocol packets |
US13/766,330 US9112780B2 (en) | 2007-01-11 | 2013-02-13 | Techniques for processing incoming failure detection protocol packets |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US88007407P | 2007-01-11 | 2007-01-11 | |
US11/953,745 US20090279441A1 (en) | 2007-01-11 | 2007-12-10 | Techniques for transmitting failure detection protocol packets |
Publications (1)
Publication Number | Publication Date |
---|---|
US20090279441A1 true US20090279441A1 (en) | 2009-11-12 |
Family
ID=41266796
Family Applications (5)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/953,743 Active 2028-10-02 US7978614B2 (en) | 2007-01-11 | 2007-12-10 | Techniques for detecting non-receipt of fault detection protocol packets |
US11/953,751 Active 2028-04-22 US8155011B2 (en) | 2007-01-11 | 2007-12-10 | Techniques for using dual memory structures for processing failure detection protocol packets |
US11/953,745 Abandoned US20090279441A1 (en) | 2007-01-11 | 2007-12-10 | Techniques for transmitting failure detection protocol packets |
US11/953,742 Active 2028-07-18 US8395996B2 (en) | 2007-01-11 | 2007-12-10 | Techniques for processing incoming failure detection protocol packets |
US13/766,330 Active 2028-06-19 US9112780B2 (en) | 2007-01-11 | 2013-02-13 | Techniques for processing incoming failure detection protocol packets |
Family Applications Before (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/953,743 Active 2028-10-02 US7978614B2 (en) | 2007-01-11 | 2007-12-10 | Techniques for detecting non-receipt of fault detection protocol packets |
US11/953,751 Active 2028-04-22 US8155011B2 (en) | 2007-01-11 | 2007-12-10 | Techniques for using dual memory structures for processing failure detection protocol packets |
Family Applications After (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/953,742 Active 2028-07-18 US8395996B2 (en) | 2007-01-11 | 2007-12-10 | Techniques for processing incoming failure detection protocol packets |
US13/766,330 Active 2028-06-19 US9112780B2 (en) | 2007-01-11 | 2013-02-13 | Techniques for processing incoming failure detection protocol packets |
Country Status (1)
Country | Link |
---|---|
US (5) | US7978614B2 (en) |
Cited By (24)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090213745A1 (en) * | 2008-02-21 | 2009-08-27 | Fujitsu Limited | Frame monitoring device and frame monitoring method |
US20090282148A1 (en) * | 2007-07-18 | 2009-11-12 | Foundry Networks, Inc. | Segmented crc design in high speed networks |
US7817659B2 (en) | 2004-03-26 | 2010-10-19 | Foundry Networks, Llc | Method and apparatus for aggregating input data streams |
US7830884B2 (en) | 2002-05-06 | 2010-11-09 | Foundry Networks, Llc | Flexible method for processing data packets in a network routing system for enhanced efficiency and monitoring capability |
US7948872B2 (en) | 2000-11-17 | 2011-05-24 | Foundry Networks, Llc | Backplane interface adapter with error control and redundant fabric |
US7953923B2 (en) | 2004-10-29 | 2011-05-31 | Foundry Networks, Llc | Double density content addressable memory (CAM) lookup scheme |
US20110141911A1 (en) * | 2009-12-10 | 2011-06-16 | Alcatel-Lucent | Connectivity fault management timeout period control |
US7978614B2 (en) | 2007-01-11 | 2011-07-12 | Foundry Network, LLC | Techniques for detecting non-receipt of fault detection protocol packets |
US7978702B2 (en) | 2000-11-17 | 2011-07-12 | Foundry Networks, Llc | Backplane interface adapter |
US8037399B2 (en) | 2007-07-18 | 2011-10-11 | Foundry Networks, Llc | Techniques for segmented CRC design in high speed networks |
US8090901B2 (en) | 2009-05-14 | 2012-01-03 | Brocade Communications Systems, Inc. | TCAM management approach that minimize movements |
US8149839B1 (en) | 2007-09-26 | 2012-04-03 | Foundry Networks, Llc | Selection of trunk ports and paths using rotation |
US8170044B2 (en) | 2002-05-06 | 2012-05-01 | Foundry Networks, Llc | Pipeline method and system for switching packets |
US8391319B2 (en) | 2010-10-14 | 2013-03-05 | Adtran, Inc. | Communications system and related method for reducing continuity check message (CCM) bursts in connectivity fault management (CFM) maintenance association (MA) |
US8448162B2 (en) | 2005-12-28 | 2013-05-21 | Foundry Networks, Llc | Hitless software upgrades |
US8599850B2 (en) | 2009-09-21 | 2013-12-03 | Brocade Communications Systems, Inc. | Provisioning single or multistage networks using ethernet service instances (ESIs) |
US8671219B2 (en) | 2002-05-06 | 2014-03-11 | Foundry Networks, Llc | Method and apparatus for efficiently processing data packets in a computer network |
US8718051B2 (en) | 2003-05-15 | 2014-05-06 | Foundry Networks, Llc | System and method for high speed packet transmission |
US9030943B2 (en) | 2006-11-22 | 2015-05-12 | Foundry Networks, Llc | Recovering from failures without impact on data traffic in a shared bus architecture |
US9497107B1 (en) * | 2013-06-06 | 2016-11-15 | Cisco Technology, Inc. | Seamless path monitoring and rapid fault isolation using bidirectional forwarding detection in a network environment |
US20190280914A1 (en) * | 2018-03-12 | 2019-09-12 | Spirent Communications, Inc. | Scalability, fault tolerance and fault management for twamp with a large number of test sessions |
US10613958B2 (en) | 2018-03-12 | 2020-04-07 | Spirent Communications, Inc. | Secure method for managing a virtual test platform |
US10693729B2 (en) | 2018-03-12 | 2020-06-23 | Spirent Communications, Inc. | Acceleration of node configuration for TWAMP with a large number of test sessions |
US10841196B2 (en) | 2018-03-26 | 2020-11-17 | Spirent Communications, Inc. | Key performance indicators (KPI) for tracking and correcting problems for a network-under-test |
Families Citing this family (41)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7649885B1 (en) * | 2002-05-06 | 2010-01-19 | Foundry Networks, Inc. | Network routing system for enhanced efficiency and monitoring capability |
US8730961B1 (en) | 2004-04-26 | 2014-05-20 | Foundry Networks, Llc | System and method for optimizing router lookup |
US8320242B2 (en) | 2004-12-24 | 2012-11-27 | Net Optics, Inc. | Active response communications network tap |
US7760859B2 (en) * | 2005-03-07 | 2010-07-20 | Net Optics, Inc. | Intelligent communications network tap port aggregator |
US7898984B2 (en) * | 2007-08-07 | 2011-03-01 | Net Optics, Inc. | Enhanced communication network tap port aggregator arrangement and methods thereof |
US7903576B2 (en) | 2007-08-07 | 2011-03-08 | Net Optics, Inc. | Methods and arrangement for utilization rate display |
US8094576B2 (en) | 2007-08-07 | 2012-01-10 | Net Optic, Inc. | Integrated switch tap arrangement with visual display arrangement and methods thereof |
CN101459594B (en) * | 2007-12-14 | 2011-04-13 | 华为技术有限公司 | BFD packet transmitting method, link failure detection method and apparatus |
US7773529B2 (en) | 2007-12-27 | 2010-08-10 | Net Optic, Inc. | Director device and methods thereof |
US9880954B2 (en) * | 2008-12-01 | 2018-01-30 | Micron Technology, Inc. | Method and apparatus for providing data access |
US8243608B2 (en) * | 2008-12-30 | 2012-08-14 | Rockstar Bidco, LP | Metro Ethernet connectivity fault management acceleration |
US8139479B1 (en) | 2009-03-25 | 2012-03-20 | Juniper Networks, Inc. | Health probing detection and enhancement for traffic engineering label switched paths |
US9137166B2 (en) * | 2010-01-28 | 2015-09-15 | Brocade Communications Systems, Inc. | In-order traffic aggregation with reduced buffer usage |
US8320399B2 (en) * | 2010-02-26 | 2012-11-27 | Net Optics, Inc. | Add-on module and methods thereof |
US9813448B2 (en) | 2010-02-26 | 2017-11-07 | Ixia | Secured network arrangement and methods thereof |
US9749261B2 (en) | 2010-02-28 | 2017-08-29 | Ixia | Arrangements and methods for minimizing delay in high-speed taps |
US8830841B1 (en) | 2010-03-23 | 2014-09-09 | Marvell Israel (M.I.S.L) Ltd. | Operations, administration, and maintenance (OAM) processing engine |
JP5460630B2 (en) * | 2011-03-10 | 2014-04-02 | 株式会社日立製作所 | Network system and management server |
US9009305B1 (en) * | 2012-08-23 | 2015-04-14 | Amazon Technologies, Inc. | Network host inference system |
US9559916B2 (en) * | 2012-10-17 | 2017-01-31 | The Forcemeister, Inc. | Methods and systems for tracking time in a web-based environment |
US9313093B2 (en) * | 2012-11-14 | 2016-04-12 | Ciena Corporation | Ethernet fault management systems and methods |
DE102012113116B4 (en) * | 2012-12-27 | 2014-09-18 | Georg Bernitz | Input / output device and communication system |
US9258234B1 (en) | 2012-12-28 | 2016-02-09 | Juniper Networks, Inc. | Dynamically adjusting liveliness detection intervals for periodic network communications |
CN103117928B (en) | 2013-01-21 | 2017-02-08 | 深圳市迪浦电子有限公司 | Method and device for improving chip forwarding performance |
US9455894B1 (en) * | 2013-09-27 | 2016-09-27 | Juniper Networks, Inc. | Selective fast re-route using forwarding plane liveliness detection protocols |
US9699057B2 (en) * | 2013-12-23 | 2017-07-04 | Dell Products L.P. | System and method for diagnostic packet identification |
CN105099805B (en) * | 2014-05-16 | 2019-05-07 | 新华三技术有限公司 | A kind of bidirectional forwarding detection (BFD) method and system |
CN105323160B (en) * | 2014-07-23 | 2021-01-26 | 中兴通讯股份有限公司 | Message receiving and sending method and device, channel unit and communication equipment |
US9769017B1 (en) | 2014-09-26 | 2017-09-19 | Juniper Networks, Inc. | Impending control plane disruption indication using forwarding plane liveliness detection protocols |
GB2536681A (en) * | 2015-03-25 | 2016-09-28 | Telesoft Tech Ltd | Methods and apparatus for processing data in a network |
CN106301835B (en) * | 2015-05-25 | 2020-03-13 | 中兴通讯股份有限公司 | BFD link establishing method and device and router |
US10530869B2 (en) * | 2015-10-08 | 2020-01-07 | Arista Networks, Inc. | Bidirectional forwarding detection accelerator |
US10374936B2 (en) * | 2015-12-30 | 2019-08-06 | Juniper Networks, Inc. | Reducing false alarms when using network keep-alive messages |
CN107370674B (en) * | 2016-05-13 | 2020-12-01 | 华为技术有限公司 | Data transmission method, equipment and system |
US10397085B1 (en) | 2016-06-30 | 2019-08-27 | Juniper Networks, Inc. | Offloading heartbeat responses message processing to a kernel of a network device |
CN106878113B (en) * | 2017-04-12 | 2020-04-03 | 杭州迪普科技股份有限公司 | Link connectivity detection method and device |
US10447586B2 (en) * | 2017-06-01 | 2019-10-15 | Zte Corporation | Defect detection in IP/MPLS network tunnels |
US10771312B2 (en) * | 2018-02-28 | 2020-09-08 | Zte Corporation | Failure detection in a data network |
US11750441B1 (en) * | 2018-09-07 | 2023-09-05 | Juniper Networks, Inc. | Propagating node failure errors to TCP sockets |
FR3109254B1 (en) * | 2020-04-09 | 2022-04-08 | Commissariat Energie Atomique | Deterministic hardware system for communication between at least one transmitter and at least one receiver, configured to statically and periodically schedule the data frames, and a method for managing the reception of data frames |
CN114513433B (en) * | 2022-01-06 | 2023-10-24 | 新华三技术有限公司 | Message processing method and device |
Citations (94)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US3866175A (en) * | 1974-04-24 | 1975-02-11 | Ncr Co | Data communication system between a central computer and a plurality of data terminals |
US4723243A (en) * | 1985-12-02 | 1988-02-02 | Advanced Micro Devices, Inc. | CRC calculation machine with variable bit boundary |
US4807280A (en) * | 1987-09-18 | 1989-02-21 | Pacific Bell | Cross-connect switch |
US4896277A (en) * | 1988-05-03 | 1990-01-23 | Thermo King Corporation | Method of mapping refrigerated containers in a power line carrier based monitoring system |
US4985889A (en) * | 1988-02-04 | 1991-01-15 | Sprint International Communications Corporation | Data packet switching |
US5101404A (en) * | 1988-08-26 | 1992-03-31 | Hitachi, Ltd. | Signalling apparatus for use in an ATM switching system |
US5195181A (en) * | 1992-01-10 | 1993-03-16 | Digital Equipment Corporation | Message processing system having separate message receiving and transmitting processors with message processing being distributed between the separate processors |
US5280582A (en) * | 1989-08-29 | 1994-01-18 | Digital Equipment Corporation | No-owner frame and multiple token removal mechanism for token ring networks |
US5282196A (en) * | 1991-10-15 | 1994-01-25 | Hughes Aircraft Company | Bursted and non-bursted data router |
US5287477A (en) * | 1991-08-07 | 1994-02-15 | Hewlett-Packard Company | Memory-resource-driven arbitration |
US5301192A (en) * | 1990-08-31 | 1994-04-05 | Alcatel N.V. | Temporary information storage system comprising a buffer memory storing data structured in fixed or variable length data blocks |
US5307345A (en) * | 1992-06-25 | 1994-04-26 | Digital Equipment Corporation | Method and apparatus for cut-through data packet transfer in a bridge device |
US5390173A (en) * | 1992-10-22 | 1995-02-14 | Digital Equipment Corporation | Packet format in hub for packet data communications system |
US5392279A (en) * | 1992-01-17 | 1995-02-21 | Fujitsu Limited | Interconnection network with self-routing function |
US5406643A (en) * | 1993-02-11 | 1995-04-11 | Motorola, Inc. | Method and apparatus for selecting between a plurality of communication paths |
US5408469A (en) * | 1993-07-22 | 1995-04-18 | Synoptics Communications, Inc. | Routing device utilizing an ATM switch as a multi-channel backplane in a communication network |
US5490258A (en) * | 1991-07-29 | 1996-02-06 | Fenner; Peter R. | Associative memory for very large key spaces |
US5506840A (en) * | 1992-12-18 | 1996-04-09 | Alcatel N.V. | Asynchronous switching node and routing logic means for a switching element used therein |
US5598410A (en) * | 1994-12-29 | 1997-01-28 | Storage Technology Corporation | Method and apparatus for accelerated packet processing |
US5600795A (en) * | 1993-08-28 | 1997-02-04 | U.S. Philips Corporation | Local network operating in asynchronous transfer mode (ATM) generating control cell containing information about the user, address of the station, and user-related identification |
US5619497A (en) * | 1994-12-22 | 1997-04-08 | Emc Corporation | Method and apparatus for reordering frames |
US5721819A (en) * | 1995-05-05 | 1998-02-24 | Silicon Graphics Corporation | Programmable, distributed network routing |
US5732080A (en) * | 1995-07-12 | 1998-03-24 | Bay Networks, Inc. | Method and apparatus for controlling data flow within a switching device |
US5740176A (en) * | 1994-05-19 | 1998-04-14 | Dagaz Technologies, Inc. | Scalable multimedia network |
US5862350A (en) * | 1994-12-22 | 1999-01-19 | Intel Corporation | Method and mechanism for maintaining integrity within SCSI bus with hot insertion |
US5867675A (en) * | 1996-08-06 | 1999-02-02 | Compaq Computer Corp | Apparatus and method for combining data streams with programmable wait states |
US5870538A (en) * | 1995-07-19 | 1999-02-09 | Fujitsu Network Communications, Inc. | Switch fabric controller comparator system and method |
US5872783A (en) * | 1996-07-24 | 1999-02-16 | Cisco Systems, Inc. | Arrangement for rendering forwarding decisions for packets transferred among network switches |
US5875200A (en) * | 1990-11-08 | 1999-02-23 | Cirrus Logic, Inc. | Reed-Solomon code system employing k-bit serial techniques for encoding and burst error trapping |
US6016310A (en) * | 1997-06-30 | 2000-01-18 | Sun Microsystems, Inc. | Trunking support in a high performance network device |
US6023471A (en) * | 1997-10-07 | 2000-02-08 | Extreme Networks | Network interconnect device and protocol for communicating data among packet forwarding devices |
US6035414A (en) * | 1996-11-08 | 2000-03-07 | Hitachi, Ltd. | Reliability of crossbar switches in an information processing system |
US6038288A (en) * | 1997-12-31 | 2000-03-14 | Thomas; Gene Gilles | System and method for maintenance arbitration at a switching node |
US6172990B1 (en) * | 1997-06-19 | 2001-01-09 | Xaqti Corporation | Media access control micro-RISC stream processor and method for implementing the same |
US6178520B1 (en) * | 1997-07-31 | 2001-01-23 | Lsi Logic Corporation | Software recognition of drive removal or insertion in a storage system |
US6181699B1 (en) * | 1998-07-01 | 2001-01-30 | National Semiconductor Corporation | Apparatus and method of assigning VLAN tags |
US6335932B2 (en) * | 1998-07-08 | 2002-01-01 | Broadcom Corporation | High performance self balancing low cost network switching architecture based on distributed hierarchical shared memory |
US20020001307A1 (en) * | 2000-05-20 | 2002-01-03 | Equipe Communications Corporation | VPI/VCI availability index |
US6343072B1 (en) * | 1997-10-01 | 2002-01-29 | Cisco Technology, Inc. | Single-chip architecture for shared-memory router |
US20020012585A1 (en) * | 2000-06-09 | 2002-01-31 | Broadcom Corporation | Gigabit switch with fast filtering processor |
US6351143B1 (en) * | 2000-05-01 | 2002-02-26 | Xilinx, Inc. | Content-addressable memory implemented using programmable logic |
US6356942B1 (en) * | 1998-05-13 | 2002-03-12 | Axis Ab | Integrated circuit and method for bringing an integrated circuit to execute instructions |
US6356550B1 (en) * | 1999-07-30 | 2002-03-12 | Mayan Networks Corporation | Flexible time division multiplexed bus using sonet formatting |
US6363077B1 (en) * | 1998-02-13 | 2002-03-26 | Broadcom Corporation | Load balancing in link aggregation and trunking |
US20030009466A1 (en) * | 2001-06-21 | 2003-01-09 | Ta John D. C. | Search engine with pipeline structure |
US20030033435A1 (en) * | 2001-07-17 | 2003-02-13 | Hanner Brian D. | System and method for multidimensional data compression |
US6522656B1 (en) * | 1994-09-12 | 2003-02-18 | 3Com Corporation | Distributed processing ethernet switch with adaptive cut-through switching |
US20030043848A1 (en) * | 2001-08-30 | 2003-03-06 | Sonksen Bradley Stephen | Method and apparatus for data item processing control |
US20030043800A1 (en) * | 2001-08-30 | 2003-03-06 | Sonksen Bradley Stephen | Dynamic data item processing |
US6532234B1 (en) * | 1997-07-01 | 2003-03-11 | Nec Corporation | Back-pressure type ATM switch |
US20030048785A1 (en) * | 2001-08-28 | 2003-03-13 | International Business Machines Corporation | Network processor with single interface supporting tree search engine and CAM |
US20030061459A1 (en) * | 2001-09-27 | 2003-03-27 | Nagi Aboulenein | Method and apparatus for memory access scheduling to reduce memory access latency |
US6678248B1 (en) * | 1997-08-29 | 2004-01-13 | Extreme Networks | Policy based quality of service |
US6681332B1 (en) * | 2000-03-13 | 2004-01-20 | Analog Devices, Inc. | System and method to place a device in power down modes/states and restore back to first mode/state within user-controlled time window |
US6687247B1 (en) * | 1999-10-27 | 2004-02-03 | Cisco Technology, Inc. | Architecture for high speed class of service enabled linecard |
US20040022263A1 (en) * | 2002-08-02 | 2004-02-05 | Xiaodong Zhao | Cross point switch with out-of-band parameter fine tuning |
US6691202B2 (en) * | 2000-12-22 | 2004-02-10 | Lucent Technologies Inc. | Ethernet cross point switch with reduced connections by using column control buses |
US20040028060A1 (en) * | 2002-08-08 | 2004-02-12 | Samsung Electronics Co., Ltd. | Link state synchronization method and apparatus on ad-hoc network, and data structure therefor |
US6697359B1 (en) * | 1999-07-02 | 2004-02-24 | Ancor Communications, Inc. | High performance switch fabric element and switch systems |
US6696917B1 (en) * | 2000-09-21 | 2004-02-24 | Nortel Networks Limited | Folded Clos architecture switching |
US6697368B2 (en) * | 2000-11-17 | 2004-02-24 | Foundry Networks, Inc. | High-performance network switch |
US6700894B1 (en) * | 2000-03-15 | 2004-03-02 | Broadcom Corporation | Method and apparatus for shared buffer packet switching |
US6708000B1 (en) * | 1999-10-29 | 2004-03-16 | Fujitsu Limited | Photonic node, photonic nodes for transmission and reception, and method of restoring traffic upon occurrence of link failure in optical path network |
US20040054867A1 (en) * | 2002-09-13 | 2004-03-18 | Paulus Stravers | Translation lookaside buffer |
US6839346B1 (en) * | 1999-04-05 | 2005-01-04 | Nec Corporation | Packet switching apparatus with high speed routing function |
US6839349B2 (en) * | 1999-12-07 | 2005-01-04 | Broadcom Corporation | Mirroring in a stacked network switch configuration |
US6842422B1 (en) * | 1999-06-15 | 2005-01-11 | Marconi Communications, Inc. | Data striping based switching system |
US20050010630A1 (en) * | 2003-05-13 | 2005-01-13 | International Business Machines Corporation | Method and apparatus for determining a remainder in a polynomial ring |
US6854117B1 (en) * | 2000-10-31 | 2005-02-08 | Caspian Networks, Inc. | Parallel network processor array |
US6859438B2 (en) * | 1998-02-03 | 2005-02-22 | Extreme Networks, Inc. | Policy based quality of service |
US20050041684A1 (en) * | 1999-10-01 | 2005-02-24 | Agilent Technologies, Inc. | Multi-channel network monitoring apparatus, signal replicating device, and systems including such apparatus and devices, and enclosure for multi-processor equipment |
US6865153B1 (en) * | 2000-09-20 | 2005-03-08 | Alcatel | Stage-implemented QoS shaping for data communication switch |
US6990102B1 (en) * | 2001-05-10 | 2006-01-24 | Advanced Micro Devices, Inc. | Parallel lookup tables for locating information in a packet switched network |
US20060031610A1 (en) * | 2004-08-03 | 2006-02-09 | Liav Ori R | FIFO sub-system with in-line correction |
US20060034452A1 (en) * | 2002-06-20 | 2006-02-16 | Hitachi, Ltd. | Code calculating device |
US7005812B2 (en) * | 2001-07-23 | 2006-02-28 | Lawrence Hardy Mitchell | Commutation converter for a brushless servo motor |
US7012919B1 (en) * | 2000-04-19 | 2006-03-14 | Caspian Networks, Inc. | Micro-flow label switching |
US7161948B2 (en) * | 2002-03-15 | 2007-01-09 | Broadcom Corporation | High speed protocol for interconnecting modular network devices |
US7176911B1 (en) * | 1999-02-02 | 2007-02-13 | Olympus Corporation | Solid-state imaging apparatus |
US20070038798A1 (en) * | 2004-09-10 | 2007-02-15 | Bouchard Gregg A | Selective replication of data structures |
US7185141B1 (en) * | 2001-12-27 | 2007-02-27 | Netlogic Microsystems, Inc. | Apparatus and method for associating information values with portions of a content addressable memory (CAM) device |
US7185266B2 (en) * | 2003-02-12 | 2007-02-27 | Alacritech, Inc. | Network interface device for error detection using partial CRCS of variable length message portions |
US7187687B1 (en) * | 2002-05-06 | 2007-03-06 | Foundry Networks, Inc. | Pipeline method and system for switching packets |
US7191277B2 (en) * | 2001-02-23 | 2007-03-13 | Hewlett-Packard Development Company, L.P. | Dynamic allocation of devices to host controllers |
US7190696B1 (en) * | 2002-03-05 | 2007-03-13 | Force10 Networks, Inc. | System and method for distributing packets among a plurality of paths to a destination |
US20080002707A1 (en) * | 2002-05-06 | 2008-01-03 | Davis Ian E | Flexible method for processing data packets in a network routing system for enhanced efficiency and monitoring capability |
US7324509B2 (en) * | 2001-03-02 | 2008-01-29 | Broadcom Corporation | Efficient optimization algorithm in memory utilization for network applications |
US20080031263A1 (en) * | 2006-08-07 | 2008-02-07 | Cisco Technology, Inc. | Method and apparatus for load balancing over virtual network links |
US20080037544A1 (en) * | 2006-08-11 | 2008-02-14 | Hiroki Yano | Device and Method for Relaying Packets |
US20080049742A1 (en) * | 2006-08-22 | 2008-02-28 | Deepak Bansal | System and method for ecmp load sharing |
US20080069125A1 (en) * | 2001-07-31 | 2008-03-20 | Interactic Holdings, Llc | Means and apparatus for a scalable congestion free switching system with intelligent control |
US7512127B2 (en) * | 2000-11-17 | 2009-03-31 | Foundry Networks, Inc. | Backplane interface adapter |
US7649885B1 (en) * | 2002-05-06 | 2010-01-19 | Foundry Networks, Inc. | Network routing system for enhanced efficiency and monitoring capability |
US7657703B1 (en) * | 2004-10-29 | 2010-02-02 | Foundry Networks, Inc. | Double density content addressable memory (CAM) lookup scheme |
Family Cites Families (387)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4348725A (en) | 1977-01-19 | 1982-09-07 | Honeywell Information Systems Inc. | Communication line service interrupt technique for a communications processing system |
US4325119A (en) | 1977-01-19 | 1982-04-13 | Honeywell Information Systems Inc. | Process and apparatus employing microprogrammed control commands for transferring information between a control processor and communications channels |
US4683564A (en) | 1982-11-22 | 1987-07-28 | Data Switch Corporation | Matrix switch system |
US4698748A (en) | 1983-10-07 | 1987-10-06 | Essex Group, Inc. | Power-conserving control system for turning-off the power and the clocking for data transactions upon certain system inactivity |
US4628480A (en) | 1983-10-07 | 1986-12-09 | United Technologies Automotive, Inc. | Arrangement for optimized utilization of I/O pins |
US4667323A (en) | 1985-09-03 | 1987-05-19 | Allen-Bradley Company, Inc. | Industrialized token passing network |
US4754482A (en) | 1985-11-26 | 1988-06-28 | Samco Investment Company | Method and apparatus for synchronizing encrypting and decrypting systems |
US4679190A (en) | 1986-04-28 | 1987-07-07 | International Business Machines Corporation | Distributed voice-data switching on multi-stage interconnection networks |
DE3616141A1 (en) | 1986-05-14 | 1987-11-19 | Siemens Ag | Contour collimator for radiation therapy (radiotherapy, X-ray therapy) |
US4791629A (en) | 1986-06-02 | 1988-12-13 | Ibm Corporation | Communications switching system |
DE3851084D1 (en) | 1987-05-15 | 1994-09-22 | Hitachi Ltd | Device for controlling packet switching networks. |
US5208856A (en) | 1988-12-23 | 1993-05-04 | Laboratoire Europeen De Recherches Electroniques Avancees | Scrambling and unscrambling method for composite video signals and implementing device |
US5377189A (en) | 1989-06-02 | 1994-12-27 | British Telecommunications Public Limited Company | Hybrid data communications systems |
US5163131A (en) | 1989-09-08 | 1992-11-10 | Auspex Systems, Inc. | Parallel i/o network file server architecture |
FR2654288B1 (en) | 1989-11-08 | 1996-11-29 | Europ Rech Electr Lab | METHOD FOR AUTHENTICATING A MICROPROCESSOR CARD AND SYSTEM USING THE SAME. |
US5231633A (en) | 1990-07-11 | 1993-07-27 | Codex Corporation | Method for prioritizing, selectively discarding, and multiplexing differing traffic type fast packets |
US5136584A (en) | 1990-07-11 | 1992-08-04 | At&T Bell Laboratories | Hardware interface to a high-speed multiplexed link |
JP2770936B2 (en) | 1990-12-18 | 1998-07-02 | インターナショナル・ビジネス・マシーンズ・コーポレイション | Method of creating communication network and communication channel |
DE69221338T2 (en) | 1991-01-18 | 1998-03-19 | Nat Semiconductor Corp | Repeater interface control device |
US5224108A (en) | 1991-01-23 | 1993-06-29 | Mcdysan David E | Method and apparatus for call control signaling |
US5734826A (en) * | 1991-03-29 | 1998-03-31 | International Business Machines Corporation | Variable cyclic redundancy coding method and apparatus for use in a multistage network |
NL9101335A (en) * | 1991-08-02 | 1993-03-01 | Emerson Electric Co | TRANSMISSION FOR ELECTRICALLY POWERED TOOLS. |
US6263374B1 (en) | 1992-09-17 | 2001-07-17 | International Business Machines Corporation | Apparatus for coupling a bus-based architecture to a switch network |
GB2273224B (en) | 1992-12-05 | 1997-01-22 | Netcomm Ltd | An ATM Cell switch suitable for multicast switching |
US5299190A (en) * | 1992-12-18 | 1994-03-29 | International Business Machines Corporation | Two-dimensional round-robin scheduling mechanism for switches with multiple input queues |
US5323386A (en) | 1993-02-01 | 1994-06-21 | Trw Inc. | Expandable high speed serial data switch |
FR2703545B1 (en) | 1993-03-31 | 1995-05-12 | Alcatel Nv | Asynchronous switching node dynamically distributing cells to outputs constituting a so-called irregular group. |
SE515148C2 (en) | 1993-06-23 | 2001-06-18 | Ericsson Telefon Ab L M | Control of cell selector |
US5365512A (en) | 1993-07-02 | 1994-11-15 | Ericsson Ge Mobile Communications Inc. | Multisite trunked RF communication system with reliable control messaging network |
DE4328862A1 (en) | 1993-08-27 | 1995-03-02 | Sel Alcatel Ag | Method and device for buffering data packets and switching center with such a device |
US5802287A (en) | 1993-10-20 | 1998-09-01 | Lsi Logic Corporation | Single chip universal protocol multi-function ATM network interface |
US5442628A (en) | 1993-11-15 | 1995-08-15 | Motorola, Inc. | Local area network data processing system containing a quad elastic buffer and layer management (ELM) integrated circuit and method of switching |
US5530302A (en) | 1994-01-13 | 1996-06-25 | Network Systems Corporation | Circuit module with hot-swap control circuitry |
US5640504A (en) | 1994-01-24 | 1997-06-17 | Advanced Computer Applications, Inc. | Distributed computing network |
WO1995024081A1 (en) | 1994-03-03 | 1995-09-08 | Proxim, Inc. | Frequency hopping medium access control protocol |
US6151301A (en) | 1995-05-11 | 2000-11-21 | Pmc-Sierra, Inc. | ATM architecture and switching element |
GB9408574D0 (en) | 1994-04-29 | 1994-06-22 | Newbridge Networks Corp | Atm switching system |
US5802394A (en) | 1994-06-06 | 1998-09-01 | Starlight Networks, Inc. | Method for accessing one or more streams in a video storage system using multiple queues and maintaining continuity thereof |
US5606359A (en) | 1994-06-30 | 1997-02-25 | Hewlett-Packard Company | Video on demand system with multiple data sources configured to provide vcr-like services |
US5907660A (en) | 1994-09-21 | 1999-05-25 | Mitsubishi Denki Kabushiki Kaisha | Digital video signal playback device with special playback data being in the form of a still image slice data |
US6243388B1 (en) | 1994-11-30 | 2001-06-05 | Verizon Laboratories Inc. | Broadband video switch that performs program merging and method therefor |
US5649089A (en) | 1994-11-30 | 1997-07-15 | Motorola, Inc. | Method and apparatus for maintaining a redundant database system |
EP0716370A3 (en) | 1994-12-06 | 2005-02-16 | International Business Machines Corporation | A disk access method for delivering multimedia and video information on demand over wide area networks |
JPH08167907A (en) | 1994-12-15 | 1996-06-25 | Nec Corp | Atm cell exchange |
US5550816A (en) | 1994-12-29 | 1996-08-27 | Storage Technology Corporation | Method and apparatus for virtual switching |
US5566170A (en) | 1994-12-29 | 1996-10-15 | Storage Technology Corporation | Method and apparatus for accelerated packet forwarding |
US5546385A (en) | 1995-01-19 | 1996-08-13 | Intel Corporation | Flexible switching hub for a communication network |
US5666353A (en) | 1995-03-21 | 1997-09-09 | Cisco Systems, Inc. | Frame based traffic policing for a digital switch |
US5936939A (en) | 1995-05-22 | 1999-08-10 | Fore Systems, Inc. | Digital network including early packet discard mechanism with adjustable threshold |
US5646878A (en) | 1995-06-02 | 1997-07-08 | Motorola, Inc. | Content addressable memory system |
US5663952A (en) | 1995-07-07 | 1997-09-02 | Sun Microsystems, Inc. | Checksum generation circuit and method |
US6147996A (en) | 1995-08-04 | 2000-11-14 | Cisco Technology, Inc. | Pipelined multiple issue packet switch |
US5968962A (en) * | 1995-09-01 | 1999-10-19 | Pharmacia & Upjohn Company | Phenyloxazolidinones having a C-C bond to 4-8 membered heterocyclic rings |
US6185222B1 (en) | 1995-09-28 | 2001-02-06 | Cisco Technology, Inc. | Asymmetric switch architecture for use in a network switch node |
US6427185B1 (en) | 1995-09-29 | 2002-07-30 | Nortel Networks Limited | Method and apparatus for managing the flow of data within a switching device |
JPH0998181A (en) | 1995-09-29 | 1997-04-08 | Fujitsu Ltd | Transmitter |
US5745708A (en) | 1995-09-29 | 1998-04-28 | Allen-Bradley Company, Inc. | Method for and apparatus for operating a local communications module in arbitrating for mastership of a data transfer across a back plane bus in industrial automation controller |
US5802065A (en) | 1995-10-23 | 1998-09-01 | Kawasaki Steel Corporation | Data receiving device |
SE508050C2 (en) | 1995-11-09 | 1998-08-17 | Ericsson Telefon Ab L M | Device and method of packet delivery |
US5838684A (en) | 1996-02-22 | 1998-11-17 | Fujitsu, Ltd. | Low latency, high clock frequency plesioasynchronous packet-based crossbar switching chip system and method |
GB2312353B (en) | 1996-04-16 | 2000-12-06 | Gpt Ltd | Digital telecommunications transmision systems |
US5835496A (en) | 1996-04-30 | 1998-11-10 | Mcdata Corporation | Method and apparatus for data alignment |
US6243667B1 (en) | 1996-05-28 | 2001-06-05 | Cisco Systems, Inc. | Network flow switching and flow data export |
US5751710A (en) | 1996-06-11 | 1998-05-12 | Cisco Technology, Inc. | Technique for connecting cards of a distributed network switch |
US5864555A (en) * | 1996-07-05 | 1999-01-26 | General Datacomm, Inc. | Method and apparatus for generating a proxy connection endpoint for operation administration and management (OAM) asynchronous transfer mode (ATM) cells |
JPH10126419A (en) | 1996-10-23 | 1998-05-15 | Nec Corp | Atm exchange system |
US6369855B1 (en) | 1996-11-01 | 2002-04-09 | Texas Instruments Incorporated | Audio and video decoder circuit and system |
FI103312B1 (en) | 1996-11-06 | 1999-05-31 | Nokia Telecommunications Oy | Switching matrix |
US6031843A (en) | 1996-11-21 | 2000-02-29 | Alcatel Data Networks Inc. | Digital communications switching fabric |
US6493347B2 (en) | 1996-12-16 | 2002-12-10 | Juniper Networks, Inc. | Memory organization in a switching device |
US6094434A (en) | 1996-12-30 | 2000-07-25 | Compaq Computer Corporation | Network switch with separate cut-through buffer |
CA2196958C (en) | 1997-02-06 | 2003-09-16 | David A. Brown | Multi-core atm switch with cells in the core from an inlet for an outlet being aligned |
US6076115A (en) | 1997-02-11 | 2000-06-13 | Xaqti Corporation | Media access control receiver and network management system |
US6222845B1 (en) | 1997-02-25 | 2001-04-24 | Cascade Communications Corp. | System and method for providing unitary virtual circuit in digital network having communication links of diverse service types |
US5920886A (en) | 1997-03-14 | 1999-07-06 | Music Semiconductor Corporation | Accelerated hierarchical address filtering and translation using binary and ternary CAMs |
US6011910A (en) * | 1997-04-08 | 2000-01-04 | 3Com Corporation | Supporting authentication across multiple network access servers |
US6000016A (en) | 1997-05-02 | 1999-12-07 | Intel Corporation | Multiported bypass cache in a bypass network |
US5907566A (en) | 1997-05-29 | 1999-05-25 | 3Com Corporation | Continuous byte-stream encoder/decoder using frequency increase and cyclic redundancy check |
JP3116860B2 (en) | 1997-06-05 | 2000-12-11 | 日本電気株式会社 | Data processing device, data processing system, data processing method, information storage medium |
US6118787A (en) | 1997-06-27 | 2000-09-12 | Advanced Micro Devices, Inc. | Apparatus and method for regulating assigned bandwidth in high speed packet switched networks |
US6195335B1 (en) | 1997-06-27 | 2001-02-27 | International Business Machines Corporation | Data switch |
US6081522A (en) | 1997-06-30 | 2000-06-27 | Sun Microsystems, Inc. | System and method for a multi-layer network element |
US5920566A (en) | 1997-06-30 | 1999-07-06 | Sun Microsystems, Inc. | Routing in a multi-layer distributed network element |
US5909686A (en) | 1997-06-30 | 1999-06-01 | Sun Microsystems, Inc. | Hardware-assisted central processing unit access to a forwarding database |
US6081512A (en) | 1997-06-30 | 2000-06-27 | Sun Microsystems, Inc. | Spanning tree support in a high performance network device |
US6088356A (en) | 1997-06-30 | 2000-07-11 | Sun Microsystems, Inc. | System and method for a multi-layer network element |
US6128666A (en) | 1997-06-30 | 2000-10-03 | Sun Microsystems, Inc. | Distributed VLAN mechanism for packet field replacement in a multi-layered switched network element using a control field/signal for indicating modification of a packet with a database search engine |
US6304903B1 (en) | 1997-08-01 | 2001-10-16 | Agilent Technologies, Inc. | State machine for collecting information on use of a packet network |
US6108306A (en) | 1997-08-08 | 2000-08-22 | Advanced Micro Devices, Inc. | Apparatus and method in a network switch for dynamically allocating bandwidth in ethernet workgroup switches |
US6157641A (en) | 1997-08-22 | 2000-12-05 | Cisco Technology, Inc. | Multiprotocol packet recognition and switching |
US6333929B1 (en) | 1997-08-29 | 2001-12-25 | Intel Corporation | Packet format for a distributed system |
US6272144B1 (en) | 1997-09-29 | 2001-08-07 | Agere Systems Guardian Corp. | In-band device configuration protocol for ATM transmission convergence devices |
TW371736B (en) | 1997-10-08 | 1999-10-11 | Yen-Yuan Chianh | Virtual IP gate and its IP construction |
US6480477B1 (en) | 1997-10-14 | 2002-11-12 | Innowave Eci Wireless Systems Ltd. | Method and apparatus for a data transmission rate of multiples of 100 MBPS in a terminal for a wireless metropolitan area network |
US6434620B1 (en) | 1998-08-27 | 2002-08-13 | Alacritech, Inc. | TCP/IP offload network interface device |
US6226680B1 (en) | 1997-10-14 | 2001-05-01 | Alacritech, Inc. | Intelligent network interface system method for protocol processing |
US6591302B2 (en) | 1997-10-14 | 2003-07-08 | Alacritech, Inc. | Fast-path apparatus for receiving data corresponding to a TCP connection |
US6157614A (en) | 1997-10-22 | 2000-12-05 | Netro Corporation | Wireless ATM network with high quality of service scheduling |
JP3542473B2 (en) * | 1997-10-30 | 2004-07-14 | キヤノン株式会社 | Developing device, process cartridge and image forming device |
US6366557B1 (en) | 1997-10-31 | 2002-04-02 | Nortel Networks Limited | Method and apparatus for a Gigabit Ethernet MAC (GMAC) |
US6320859B1 (en) | 1997-10-31 | 2001-11-20 | Nortel Networks Limited | Early availability of forwarding control information |
US6125417A (en) | 1997-11-14 | 2000-09-26 | International Business Machines Corporation | Hot plug of adapters using optical switches |
US6236658B1 (en) | 1997-11-21 | 2001-05-22 | Cisco Technology, Inc. | Method and apparatus for message routing, including a content addressable memory |
US6144668A (en) | 1997-11-26 | 2000-11-07 | International Business Machines Corporation | Simultaneous cut through and store-and-forward frame support in a network device |
EP0920152A3 (en) | 1997-11-27 | 2002-09-18 | Hitachi, Ltd. | Method and apparatus for multiplex transmission |
US6067606A (en) | 1997-12-15 | 2000-05-23 | Intel Corporation | Computer processor with dynamic setting of latency values for memory access |
US6160809A (en) | 1997-12-17 | 2000-12-12 | Compaq Computer Corporation | Distributed packet data with centralized snooping and header processing router |
US6307839B1 (en) | 1997-12-31 | 2001-10-23 | At&T Corp | Dynamic bandwidth allocation for use in the hybrid fiber twisted pair local loop network service architecture |
US6549519B1 (en) | 1998-01-23 | 2003-04-15 | Alcatel Internetworking (Pe), Inc. | Network switching device with pipelined search engines |
US6151497A (en) | 1998-02-12 | 2000-11-21 | Motorola, Inc. | Satellite based high bandwidth data broadcast |
EP0938212A1 (en) | 1998-02-19 | 1999-08-25 | International Business Machines Corporation | Process and system of flow control for a switching system |
US6249528B1 (en) | 1998-03-12 | 2001-06-19 | I-Cube, Inc. | Network switch providing per virtual channel queuing for segmentation and reassembly |
DE19912512B4 (en) * | 1998-03-20 | 2008-01-03 | Chuo Hatsujo K.K., Nagoya | Pressure-train-control cable |
US6662234B2 (en) | 1998-03-26 | 2003-12-09 | National Semiconductor Corporation | Transmitting data from a host computer in a reduced power state by an isolation block that disconnects the media access control layer from the physical layer |
US6795442B1 (en) | 1998-04-23 | 2004-09-21 | Emulex Design & Manufacturing Corporation | System and method for scheduling message transmission and processing in a digital data network |
US6359879B1 (en) * | 1998-04-24 | 2002-03-19 | Avici Systems | Composite trunking |
US6185208B1 (en) | 1998-04-30 | 2001-02-06 | Phone.Com, Inc. | Method and apparatus for fragmenting messages for a wireless network using group sharing of reference numbers |
US6160812A (en) | 1998-05-04 | 2000-12-12 | Cabletron Systems, Inc. | Method and apparatus for supplying requests to a scheduler in an input buffered multiport switch |
US6229788B1 (en) | 1998-05-27 | 2001-05-08 | Nortel Networks Limited | Method and apparatus for traffic shaping in a broadband fiber-based access system |
US6505281B1 (en) * | 1998-06-02 | 2003-01-07 | Raymond C. Sherry | Hard disk drives employing high speed distribution bus |
US6539011B1 (en) | 1998-06-10 | 2003-03-25 | Merlot Communications, Inc. | Method for initializing and allocating bandwidth in a permanent virtual connection for the transmission and control of audio, video, and computer data over a single network fabric |
IL134611A (en) | 1998-06-19 | 2004-05-12 | Juniper Networks Inc | Interconnect network for operation within a communication node |
US6496502B1 (en) | 1998-06-29 | 2002-12-17 | Nortel Networks Limited | Distributed multi-link trunking method and apparatus |
US6658002B1 (en) | 1998-06-30 | 2003-12-02 | Cisco Technology, Inc. | Logical operation unit for packet processing |
US7346063B1 (en) | 1998-07-08 | 2008-03-18 | Broadcom Corporation | Memory management unit for a network switch |
US6424659B2 (en) | 1998-07-17 | 2002-07-23 | Network Equipment Technologies, Inc. | Multi-layer switching apparatus and method |
US6032209A (en) | 1998-07-24 | 2000-02-29 | Storage Technology Corporation | Hot-swappable high speed point-to-point interface |
JP3002726B1 (en) * | 1998-07-31 | 2000-01-24 | 東京大学長 | Variable speed digital switching system |
JP3002727B1 (en) | 1998-07-31 | 2000-01-24 | 東京大学長 | Variable speed TDM switching system using TS connection |
EP1748617A3 (en) | 1998-09-11 | 2011-02-09 | Hitachi, Ltd. | IP packet communication apparatus |
US6731875B1 (en) | 1998-09-22 | 2004-05-04 | Lucent Technologies Inc. | Wavelength bus architecture for ultra-high speed dense wavelength division multiplexed systems |
US6370579B1 (en) | 1998-10-21 | 2002-04-09 | Genuity Inc. | Method and apparatus for striping packets over parallel communication links |
US6658552B1 (en) | 1998-10-23 | 2003-12-02 | Micron Technology, Inc. | Processing system with separate general purpose execution unit and data string manipulation unit |
US6457175B1 (en) | 1998-11-09 | 2002-09-24 | Tut Systems, Inc. | Method and apparatus for installing a software upgrade within a memory resource associated with a computer system |
DE19851923B4 (en) * | 1998-11-11 | 2008-06-12 | Michael Hörauf Maschinenfabrik GmbH & Co. KG | Device for transporting yarn through a climatic chamber |
US6324651B2 (en) | 1998-11-12 | 2001-11-27 | International Business Machines Corporation | Method and apparatus for saving device state while a computer system is in sleep mode |
US6470436B1 (en) | 1998-12-01 | 2002-10-22 | Fast-Chip, Inc. | Eliminating memory fragmentation and garbage collection from the process of managing dynamically allocated memory |
US6104969A (en) | 1998-12-30 | 2000-08-15 | Honeywell International Inc. | Methods and apparatus for operating an input device in a turbulent environment |
US6473428B1 (en) | 1998-12-31 | 2002-10-29 | Nortel Networks Limited | Multi-threaded, multi-cast switch |
US6532229B1 (en) | 1999-01-15 | 2003-03-11 | Brian Weatherred Johnson | Low cost link aggregation method and system |
US6535504B1 (en) | 1999-01-15 | 2003-03-18 | Brian Weatherred Johnson | Link aggregation path selection method |
US6934305B1 (en) | 1999-01-15 | 2005-08-23 | Cisco Technology, Inc. | Method and apparatus for detecting errors in a backplane frame |
US6982974B1 (en) | 1999-01-15 | 2006-01-03 | Cisco Technology, Inc. | Method and apparatus for a rearrangeably non-blocking switching matrix |
US6424658B1 (en) | 1999-01-29 | 2002-07-23 | Neomagic Corp. | Store-and-forward network switch using an embedded DRAM |
US6510138B1 (en) | 1999-02-25 | 2003-01-21 | Fairchild Semiconductor Corporation | Network switch with head of line input buffer queue clearing |
US6636483B1 (en) | 1999-02-25 | 2003-10-21 | Fairchild Semiconductor Corporation | Network switch with zero latency flow control |
US6556208B1 (en) | 1999-03-23 | 2003-04-29 | Intel Corporation | Network management card for use in a system for screen image capturing |
US6490280B1 (en) | 1999-03-31 | 2002-12-03 | Advanced Micro Devices, Inc. | Frame assembly in dequeuing block |
JP3319723B2 (en) | 1999-04-02 | 2002-09-03 | 日本電気株式会社 | Switch, scheduler thereof, and switch scheduling method |
US6747971B1 (en) | 1999-04-20 | 2004-06-08 | Cisco Technology, Inc. | Crosspoint switch with independent schedulers |
US6687217B1 (en) * | 1999-05-04 | 2004-02-03 | Carriercomm, Inc. | Method of and system for one plus one protection for radio equipment |
US6654346B1 (en) | 1999-07-19 | 2003-11-25 | Dunti Corporation | Communication network across which packets of data are transmitted according to a priority scheme |
US6842903B1 (en) * | 1999-05-19 | 2005-01-11 | Sun Microsystems, Inc. | System and method for providing dynamic references between services in a computer system |
US6873630B1 (en) | 1999-05-19 | 2005-03-29 | Sun Microsystems, Inc. | Method and apparatus for a multi-gigabit ethernet architecture |
JP3456923B2 (en) | 1999-05-20 | 2003-10-14 | シャープ株式会社 | Host device, synchronous communication system, communication interference prevention method, and computer-readable recording medium recording communication interference prevention program |
US6460088B1 (en) | 1999-05-21 | 2002-10-01 | Advanced Micro Devices, Inc. | Method and apparatus for port vector determination at egress |
US6813266B1 (en) | 1999-05-21 | 2004-11-02 | Advanced Micro Devices, Inc. | Pipelined access to address table in a network switch |
US6201492B1 (en) * | 1999-05-28 | 2001-03-13 | Cirrus Logic, Inc. | Techniques for converting a plurality of channels continuously in an A/D converter |
US6359859B1 (en) | 1999-06-03 | 2002-03-19 | Fujitsu Network Communications, Inc. | Architecture for a hybrid STM/ATM add-drop multiplexer |
US6665301B1 (en) | 1999-06-03 | 2003-12-16 | Fujitsu Network Communications, Inc. | Transmission slot allocation method and map for virtual tunnels in a transmission line |
US6677952B1 (en) | 1999-06-09 | 2004-01-13 | 3Dlabs Inc., Ltd. | Texture download DMA controller synching multiple independently-running rasterizers |
JP3449294B2 (en) | 1999-06-18 | 2003-09-22 | 日本電気株式会社 | Multiprotocol processing device, line interface, and multiprotocol switch system having the same |
WO2001015388A1 (en) | 1999-08-20 | 2001-03-01 | Fujitsu Limited | Atm communication monitor |
US6587432B1 (en) | 1999-08-31 | 2003-07-01 | Intel Corporation | Method and system for diagnosing network congestion using mobile agents |
AU7053400A (en) | 1999-09-03 | 2001-04-10 | Broadcom Corporation | Apparatus and method for enabling voice over ip support for a network switch |
US7010607B1 (en) | 1999-09-15 | 2006-03-07 | Hewlett-Packard Development Company, L.P. | Method for training a communication link between ports to correct for errors |
JP2001127766A (en) | 1999-10-25 | 2001-05-11 | Toshiba Corp | Line interface and packet exchange |
EP1096729A1 (en) | 1999-10-28 | 2001-05-02 | Hewlett-Packard Company, A Delaware Corporation | Rate adaptive payload transmission for local area networks |
WO2001033832A1 (en) | 1999-10-29 | 2001-05-10 | Fujitsu Limited | Image reproducing apparatus and image recording/reproducing apparatus |
US6570884B1 (en) | 1999-11-05 | 2003-05-27 | 3Com Corporation | Receive filtering for communication interface |
JP3482996B2 (en) | 1999-12-03 | 2004-01-06 | 日本電気株式会社 | ATM switch |
US6788697B1 (en) | 1999-12-06 | 2004-09-07 | Nortel Networks Limited | Buffer management scheme employing dynamic thresholds |
US6661791B1 (en) | 1999-12-28 | 2003-12-09 | Mosaid Technologies, Inc. | Method and apparatus for generating forward overrides in a packet switch |
US6856600B1 (en) | 2000-01-04 | 2005-02-15 | Cisco Technology, Inc. | Method and apparatus for isolating faults in a switching matrix |
JP3386117B2 (en) | 2000-01-11 | 2003-03-17 | 日本電気株式会社 | Multilayer class identification communication device and communication device |
GB2358332B (en) | 2000-01-14 | 2002-05-29 | Marconi Comm Ltd | Method of communicating data in a communication system |
US6813243B1 (en) | 2000-02-14 | 2004-11-02 | Cisco Technology, Inc. | High-speed hardware implementation of red congestion control algorithm |
US6977930B1 (en) * | 2000-02-14 | 2005-12-20 | Cisco Technology, Inc. | Pipelined packet switching and queuing architecture |
US6778546B1 (en) | 2000-02-14 | 2004-08-17 | Cisco Technology, Inc. | High-speed hardware implementation of MDRR algorithm over a large number of queues |
US6765866B1 (en) | 2000-02-29 | 2004-07-20 | Mosaid Technologies, Inc. | Link aggregation |
US6643269B1 (en) | 2000-03-03 | 2003-11-04 | Luminous Networks, Inc. | Routing switch automatically identifying network topology |
US6654342B1 (en) | 2000-03-07 | 2003-11-25 | Cisco Technology, Inc. | Accumulating and distributing flow control information via update messages and piggybacked flow control information in other messages in a packet switching system |
US6633580B1 (en) | 2000-03-07 | 2003-10-14 | Sun Microsystems | N×N crossbar packet switch |
US6798740B1 (en) | 2000-03-13 | 2004-09-28 | Nortel Networks Limited | Method and apparatus for switch core health monitoring and redundancy |
US6751224B1 (en) | 2000-03-30 | 2004-06-15 | Azanda Network Devices, Inc. | Integrated ATM/packet segmentation-and-reassembly engine for handling both packet and ATM input data and for outputting both ATM and packet data |
US6798933B2 (en) | 2000-04-14 | 2004-09-28 | Shipley Company, L.L.C. | Fiber optic array switch |
US6807179B1 (en) | 2000-04-18 | 2004-10-19 | Advanced Micro Devices, Inc. | Trunking arrangement in a network switch |
KR20000064177A (en) | 2000-05-01 | 2000-11-06 | 권용순 | mobile station |
US6601186B1 (en) | 2000-05-20 | 2003-07-29 | Equipe Communications Corporation | Independent restoration of control plane and data plane functions |
US6442067B1 (en) | 2000-05-23 | 2002-08-27 | Compaq Information Technologies Group, L.P. | Recovery ROM for array controllers |
US7075926B2 (en) | 2000-05-24 | 2006-07-11 | Alcatel Internetworking, Inc. (Pe) | Programmable packet processor with flow resolution logic |
WO2001095120A1 (en) | 2000-06-06 | 2001-12-13 | Vitesse Semiconductor Corporation | Crosspoint switch with switch matrix module |
US6658591B1 (en) | 2000-06-08 | 2003-12-02 | International Business Machines Corporation | Recovery from data fetch errors in hypervisor code |
US6654373B1 (en) | 2000-06-12 | 2003-11-25 | Netrake Corporation | Content aware network apparatus |
US6961347B1 (en) | 2000-06-20 | 2005-11-01 | Hewlett-Packard Development Company, L.P. | High-speed interconnection link having automated lane reordering |
US6690757B1 (en) | 2000-06-20 | 2004-02-10 | Hewlett-Packard Development Company, L.P. | High-speed interconnection adapter having automated lane de-skew |
US6993032B1 (en) * | 2000-06-29 | 2006-01-31 | Intel Corporation | Buffer arrangements to support differential link distances at full bandwidth |
US6463063B1 (en) | 2000-06-30 | 2002-10-08 | Marconi Communications, Inc. | Receiver makes right |
US7103041B1 (en) | 2000-06-30 | 2006-09-05 | Marconi Intellectual Property (Ringfence), Inc. | Optimization of number of transceivers used in a switch |
US6654370B1 (en) | 2000-06-30 | 2003-11-25 | Marconi Communications, Inc. | Backplane synchronization in a distributed system with clock drift and transport delay |
US6675258B1 (en) | 2000-06-30 | 2004-01-06 | Lsi Logic Corporation | Methods and apparatus for seamless firmware update and propagation in a dual raid controller system |
US6473433B1 (en) | 2000-06-30 | 2002-10-29 | Marconi Communications, Inc. | Queue resynch: synchronous real-time upgrade of a distributed switching system |
US6831932B1 (en) | 2000-07-14 | 2004-12-14 | Level 3 Communications, Inc. | Transfer of SONET traffic over a packet-switched network |
US6973092B1 (en) | 2000-07-28 | 2005-12-06 | Marconi Intellectual Property (Ringfence), Inc. | Dynamic queue utilization |
US6792484B1 (en) | 2000-07-28 | 2004-09-14 | Marconi Communications, Inc. | Method and apparatus for storing data using a plurality of queues |
US6978309B1 (en) | 2000-07-31 | 2005-12-20 | Cisco Technology, Inc. | Method and system for reprogramming instructions for a switch |
US6721313B1 (en) | 2000-08-01 | 2004-04-13 | International Business Machines Corporation | Switch fabric architecture using integrated serdes transceivers |
CA2387550A1 (en) | 2000-08-07 | 2002-02-14 | Inrange Technologies Corporation | Fibre channel architecture |
US6804731B1 (en) | 2000-08-11 | 2004-10-12 | Paion Company, Limited | System, method and article of manufacture for storing an incoming datagram in switch matrix in a switch fabric chipset system |
US7283547B1 (en) | 2000-08-11 | 2007-10-16 | Ericsson Ab | Switch fabrics logical synchronization utilizing propagation lockdown |
US6804815B1 (en) | 2000-09-18 | 2004-10-12 | Cisco Technology, Inc. | Sequence control mechanism for enabling out of order context processing |
US6965615B1 (en) | 2000-09-18 | 2005-11-15 | Cisco Technology, Inc. | Packet striping across a parallel header processor |
US7095753B1 (en) | 2000-09-19 | 2006-08-22 | Bbn Technologies Corp. | Digital network processor-based multi-protocol flow control |
US7543077B1 (en) | 2000-09-19 | 2009-06-02 | Stragent, Llc | Ternary content addressable memory embedded in a central processing unit |
US7171487B2 (en) | 2000-09-22 | 2007-01-30 | International Business Machines Corporation | Method and system for application specific packet forwarding |
US7224671B2 (en) | 2000-09-28 | 2007-05-29 | Force10 Networks, Inc. | Method and apparatus for load balancing in network processing device |
US6633952B2 (en) | 2000-10-03 | 2003-10-14 | Broadcom Corporation | Programmable refresh scheduler for embedded DRAMs |
US6553370B1 (en) | 2000-10-04 | 2003-04-22 | Lsi Logic Corporation | Flexible search engine having sorted binary search tree for perfect match |
US6745277B1 (en) | 2000-10-04 | 2004-06-01 | Force10 Networks, Inc. | Intelligent interleaving scheme for multibank memory |
US7106692B1 (en) | 2000-10-04 | 2006-09-12 | Ericsson Ab | APS/port mirroring |
US6792502B1 (en) | 2000-10-12 | 2004-09-14 | Freescale Semiconductor, Inc. | Microprocessor having a content addressable memory (CAM) device as a functional unit therein and method of operation |
US6952419B1 (en) | 2000-10-25 | 2005-10-04 | Sun Microsystems, Inc. | High performance transmission link and interconnect |
WO2002035359A2 (en) | 2000-10-26 | 2002-05-02 | Prismedia Networks, Inc. | Method and system for managing distributed content and related metadata |
US7046619B2 (en) | 2000-11-07 | 2006-05-16 | Ciena Corporation | Method and system for bi-directional path switched network |
US7080238B2 (en) | 2000-11-07 | 2006-07-18 | Alcatel Internetworking, (Pe), Inc. | Non-blocking, multi-context pipelined processor |
US6925516B2 (en) | 2001-01-19 | 2005-08-02 | Raze Technologies, Inc. | System and method for providing an improved common control bus for use in on-line insertion of line replaceable units in wireless and wireline access systems |
US20020089937A1 (en) | 2000-11-16 | 2002-07-11 | Srinivasan Venkatachary | Packet matching method and system |
US7596139B2 (en) | 2000-11-17 | 2009-09-29 | Foundry Networks, Inc. | Backplane interface adapter with error control and redundant fabric |
WO2002041544A2 (en) | 2000-11-17 | 2002-05-23 | Foundry Networks, Inc. | High-performance network switch |
US20020091884A1 (en) | 2000-11-17 | 2002-07-11 | Andrew Chang | Method and system for translating data formats |
US6735218B2 (en) | 2000-11-17 | 2004-05-11 | Foundry Networks, Inc. | Method and system for encoding wide striped cells |
US7356030B2 (en) | 2000-11-17 | 2008-04-08 | Foundry Networks, Inc. | Network switch cross point |
US6980521B1 (en) | 2000-11-29 | 2005-12-27 | Cisco Technology, Inc. | Method and apparatus for per session load balancing with improved load sharing in a packet switched network |
US6629099B2 (en) | 2000-12-07 | 2003-09-30 | Integrated Silicon Solution, Inc. | Paralleled content addressable memory search engine |
US6654862B2 (en) | 2000-12-29 | 2003-11-25 | Ncr Corporation | High performance disk mirroring |
US7023797B2 (en) | 2000-12-30 | 2006-04-04 | Intel Corporation | Flexible aggregation of output links |
US6967926B1 (en) | 2000-12-31 | 2005-11-22 | Cisco Technology, Inc. | Method and apparatus for using barrier phases to limit packet disorder in a packet switching system |
US20020126672A1 (en) | 2001-01-10 | 2002-09-12 | Nelson Chow | Method and apparatus for a flexible and reconfigurable packet classifier using content addressable memory |
US20020169786A1 (en) | 2001-02-16 | 2002-11-14 | Richek Martin D. | Type-safe homogeneous linkage for heterogeneous smart pointers |
WO2002069668A1 (en) | 2001-02-28 | 2002-09-06 | International Business Machines Corporation | Switching arrangement and method with separated output buffers |
US6959007B1 (en) | 2001-03-01 | 2005-10-25 | Lsi Logic Corporation | High speed network protocol stack in silicon |
US20020181476A1 (en) | 2001-03-17 | 2002-12-05 | Badamo Michael J. | Network infrastructure device for data traffic to and from mobile units |
US7193997B2 (en) | 2001-03-19 | 2007-03-20 | International Business Machines Corporation | Packet classification |
US7206309B2 (en) | 2001-03-27 | 2007-04-17 | Nortel Networks Limited | High availability packet forward apparatus and method |
US6957258B2 (en) | 2001-03-28 | 2005-10-18 | Netrake Corporation | Policy gateway |
JP2002300193A (en) | 2001-03-30 | 2002-10-11 | Hitachi Ltd | Router |
US6961340B2 (en) | 2001-04-06 | 2005-11-01 | Texas Instruments Incorporated | AAL2 receiver for filtering signaling/management packets in an ATM system |
US6937606B2 (en) | 2001-04-20 | 2005-08-30 | International Business Machines Corporation | Data structures for efficient processing of IP fragmentation and reassembly |
US8218555B2 (en) | 2001-04-24 | 2012-07-10 | Nvidia Corporation | Gigabit ethernet adapter |
US6829682B2 (en) | 2001-04-26 | 2004-12-07 | International Business Machines Corporation | Destructive read architecture for dynamic random access memories |
US20020161929A1 (en) | 2001-04-30 | 2002-10-31 | Longerbeam Donald A. | Method and apparatus for routing data through a computer network |
US6804220B2 (en) | 2001-05-07 | 2004-10-12 | Qualcomm Incorporated | Method and apparatus for generating control information for packet data |
US7206283B2 (en) | 2001-05-15 | 2007-04-17 | Foundry Networks, Inc. | High-performance network switch |
US7106739B2 (en) | 2001-06-27 | 2006-09-12 | Intel Corporation | Method enabling network address translation of incoming session initiation protocol connections based on dynamic host configuration protocol address assignments |
US20030200343A1 (en) | 2001-07-02 | 2003-10-23 | Globespan Virata Incorporated | Communications system using rings architecture |
JP3489573B2 (en) | 2001-07-11 | 2004-01-19 | 日本電気株式会社 | Packet processing device |
US7239642B1 (en) | 2001-07-16 | 2007-07-03 | Network Appliance, Inc. | Multi-protocol network interface card |
US7218637B1 (en) | 2001-07-20 | 2007-05-15 | Yotta Networks, Llc | System for switching data using dynamic scheduling |
US6868476B2 (en) | 2001-08-27 | 2005-03-15 | Intel Corporation | Software controlled content addressable memory in a general purpose execution datapath |
US6535924B1 (en) | 2001-09-05 | 2003-03-18 | Pluris, Inc. | Method and apparatus for performing a software upgrade of a router while the router is online |
US6996663B1 (en) | 2001-09-12 | 2006-02-07 | Cisco Technology, Inc. | Method and apparatus for performing address translation using a CAM |
US7050505B2 (en) | 2001-09-13 | 2006-05-23 | General Instrument Corporation | Aliasing and routing of plural MPEG data streams |
US6996117B2 (en) | 2001-09-19 | 2006-02-07 | Bay Microsystems, Inc. | Vertical instruction and data processing in a network processor architecture |
US7355970B2 (en) | 2001-10-05 | 2008-04-08 | Broadcom Corporation | Method and apparatus for enabling access on a network switch |
DE60116318T2 (en) | 2001-10-08 | 2006-08-31 | Alcatel | Method for load distribution between several common resources in a communication network and network for the application of the method |
US20030074657A1 (en) | 2001-10-12 | 2003-04-17 | Bramley Richard A. | Limited time evaluation system for firmware |
US7210003B2 (en) | 2001-10-31 | 2007-04-24 | Netlogic Microsystems, Inc. | Comparand generation in a content addressable memory |
US7286534B2 (en) | 2001-11-02 | 2007-10-23 | Infineon Technologies North America Corporation | SRAM based cache for DRAM routing table lookups |
JP3627697B2 (en) | 2001-11-16 | 2005-03-09 | 日本電気株式会社 | Packet destination search system |
US7236492B2 (en) | 2001-11-21 | 2007-06-26 | Alcatel-Lucent Canada Inc. | Configurable packet processor |
US7505458B2 (en) | 2001-11-27 | 2009-03-17 | Tellabs San Jose, Inc. | Apparatus and method for a fault-tolerant scalable switch fabric with quality-of-service (QOS) support |
JP3898498B2 (en) | 2001-12-06 | 2007-03-28 | 富士通株式会社 | Server load balancing system |
US6754881B2 (en) | 2001-12-10 | 2004-06-22 | International Business Machines Corporation | Field programmable network processor and method for customizing a network processor |
US8195705B2 (en) | 2001-12-11 | 2012-06-05 | International Business Machines Corporation | Hybrid search memory for network processor and computer systems |
US6920154B1 (en) | 2001-12-17 | 2005-07-19 | Supergate Technology Usa, Inc. | Architectures for a modularized data optimization engine and methods therefor |
US6944731B2 (en) | 2001-12-19 | 2005-09-13 | Agere Systems Inc. | Dynamic random access memory system with bank conflict avoidance feature |
US6721229B1 (en) | 2001-12-19 | 2004-04-13 | Network Equipment Technologies, Inc. | Method and apparatus for using SDRAM to read and write data without latency |
US6839797B2 (en) | 2001-12-21 | 2005-01-04 | Agere Systems, Inc. | Multi-bank scheduling to improve performance on tree accesses in a DRAM based random access memory subsystem |
US7212536B2 (en) | 2001-12-27 | 2007-05-01 | Alcatel-Lucent Canada Inc. | User priority mapping in bridged VLANS |
US6906936B1 (en) | 2001-12-27 | 2005-06-14 | Cypress Semiconductor Corporation | Data preclassifier method and apparatus for content addressable memory (CAM) device |
US20030128668A1 (en) | 2002-01-04 | 2003-07-10 | Yavatkar Rajendra S. | Distributed implementation of control protocols in routers and switches |
US7237058B2 (en) | 2002-01-14 | 2007-06-26 | Netlogic Microsystems, Inc. | Input data selection for content addressable memory |
US7212526B2 (en) | 2002-01-18 | 2007-05-01 | Hitachi, Ltd. | Method and apparatus for composing virtual links in a label switched network |
DE60308150T2 (en) | 2002-02-06 | 2007-07-19 | Koninklijke Philips Electronics N.V. | ADDRESS ROOM, BUS SYSTEM, STORAGE CONTROL AND SETUP SYSTEM |
US6781990B1 (en) | 2002-02-11 | 2004-08-24 | Extreme Networks | Method and system for managing traffic in a packet network environment |
US20030152096A1 (en) | 2002-02-13 | 2003-08-14 | Korey Chapman | Intelligent no packet loss networking |
US7719980B2 (en) | 2002-02-19 | 2010-05-18 | Broadcom Corporation | Method and apparatus for flexible frame processing and classification engine |
US6836808B2 (en) | 2002-02-25 | 2004-12-28 | International Business Machines Corporation | Pipelined packet processing |
US7126956B2 (en) | 2002-03-05 | 2006-10-24 | Applied Micro Circuits Corporation | System to provide fractional bandwidth data communications services |
WO2003079614A1 (en) | 2002-03-18 | 2003-09-25 | Nortel Networks Limited | Resource allocation using an auto-discovery mechanism for provider-provisioned layer-2 and layer-3 virtual private networks |
US6842791B2 (en) | 2002-03-20 | 2005-01-11 | Intel Corporation | Method and apparatus for memory efficient fast VLAN lookups and inserts in hardware-based packet switches |
US7126948B2 (en) | 2002-03-21 | 2006-10-24 | Hewlett-Packard Development Company, L.P. | Method and system for performing a hash transformation to generate a hash pointer for an address input by using rotation |
US7546399B2 (en) | 2002-03-25 | 2009-06-09 | Intel Corporation | Store and forward device utilizing cache to store status information for active queues |
JP2003289359A (en) | 2002-03-28 | 2003-10-10 | Hitachi Kokusai Electric Inc | Mobile telephone set |
US7496689B2 (en) | 2002-04-22 | 2009-02-24 | Alacritech, Inc. | TCP/IP offload device |
EP1499024B1 (en) | 2002-04-22 | 2010-06-30 | Fujitsu Limited | Error-detection encoder and decoder |
DE10219154A1 (en) | 2002-04-29 | 2003-11-20 | Siemens Ag | Procedure for monitoring the availability of connections in MPLS networks |
US7266117B1 (en) | 2002-05-06 | 2007-09-04 | Foundry Networks, Inc. | System architecture for very fast ethernet blade |
US20090279558A1 (en) | 2002-05-06 | 2009-11-12 | Ian Edward Davis | Network routing apparatus for enhanced efficiency and monitoring capability |
US20120155466A1 (en) | 2002-05-06 | 2012-06-21 | Ian Edward Davis | Method and apparatus for efficiently processing data packets in a computer network |
US20060165089A1 (en) | 2002-05-08 | 2006-07-27 | Joachim Klink | Method for assisting equivalent circuits in mpls networks |
US7151797B2 (en) | 2002-05-14 | 2006-12-19 | Limberg Allen Leroy | Adaptive K-factor-improvement filter for receiver of radio signals subject to multipath distortion |
US7590760B1 (en) | 2002-05-24 | 2009-09-15 | Cisco Technology, Inc. | Hybrid interface synchronization method and driver-client model for high availability systems |
US7061942B2 (en) | 2002-05-31 | 2006-06-13 | Skystream Networks Inc. | Apparatus for redundant multiplexing and remultiplexing of program streams and best effort data |
US7366100B2 (en) | 2002-06-04 | 2008-04-29 | Lucent Technologies Inc. | Method and apparatus for multipath processing |
US20030227913A1 (en) | 2002-06-05 | 2003-12-11 | Litchfield Communications, Inc. | Adaptive timing recovery of synchronous transport signals |
AU2002328419A1 (en) * | 2002-07-01 | 2004-01-19 | Ipsquare | Semiconductor circuit device, packet processing method, management system, management method, and packet processing method |
US6671275B1 (en) | 2002-08-02 | 2003-12-30 | Foundry Networks, Inc. | Cross-point switch with deadlock prevention |
US7558193B2 (en) | 2002-08-12 | 2009-07-07 | Starent Networks Corporation | Redundancy in voice and data communications systems |
US7096311B2 (en) | 2002-09-30 | 2006-08-22 | Innopath Software, Inc. | Updating electronic files using byte-level file differencing and updating algorithms |
JP4023281B2 (en) | 2002-10-11 | 2007-12-19 | 株式会社日立製作所 | Packet communication apparatus and packet switch |
US7277425B1 (en) | 2002-10-21 | 2007-10-02 | Force10 Networks, Inc. | High-speed router switching architecture |
US20040083475A1 (en) | 2002-10-25 | 2004-04-29 | Mentor Graphics Corp. | Distribution of operations to remote computers |
US7272611B1 (en) * | 2002-10-28 | 2007-09-18 | Network Appliance, Inc. | Apparatus and method for searching a n-branch data structure using information in entries |
US7188237B2 (en) | 2002-10-29 | 2007-03-06 | Brocade Communication Systems, Inc. | Reboot manager usable to change firmware in a high availability single processor system |
US7284236B2 (en) | 2002-10-29 | 2007-10-16 | Brocade Communications Systems, Inc. | Mechanism to change firmware in a high availability single processor system |
AU2003290550A1 (en) * | 2002-10-29 | 2004-05-25 | Arkados, Inc.United States Of America | Highly programmable mac architecture for handling protocols that require precision timing and demand very short response times |
US7065673B2 (en) | 2002-10-29 | 2006-06-20 | Brocade Communication Systems, Inc. | Staged startup after failover or reboot |
US7194652B2 (en) | 2002-10-29 | 2007-03-20 | Brocade Communications Systems, Inc. | High availability synchronization architecture |
US7802049B2 (en) | 2002-10-30 | 2010-09-21 | Intel Corporation | Links having flexible lane allocation |
US7403536B2 (en) | 2002-12-19 | 2008-07-22 | International Business Machines Corporation | Method and system for resequencing data packets switched through a parallel packet switch |
US7020814B2 (en) * | 2003-03-18 | 2006-03-28 | Cisco Technology, Inc. | Method and system for emulating a Fiber Channel link over a SONET/SDH path |
US7505416B2 (en) | 2003-03-31 | 2009-03-17 | Finisar Corporation | Network tap with integrated circuitry |
US7103808B2 (en) | 2003-04-10 | 2006-09-05 | International Business Machines Corporation | Apparatus for reporting and isolating errors below a host bridge |
US7346706B2 (en) * | 2003-05-02 | 2008-03-18 | Alcatel | Equivalent multiple path traffic distribution in communications networks |
US7688736B1 (en) | 2003-05-05 | 2010-03-30 | Marvell International Ltd | Network switch with quality of service flow control |
US7558268B2 (en) | 2003-05-08 | 2009-07-07 | Samsung Electronics Co., Ltd. | Apparatus and method for combining forwarding tables in a distributed architecture router |
US6901072B1 (en) | 2003-05-15 | 2005-05-31 | Foundry Networks, Inc. | System and method for high speed packet transmission implementing dual transmit and receive pipelines |
US7606161B2 (en) | 2003-06-27 | 2009-10-20 | Broadcom Corporation | Distributing information across equal-cost paths in a network |
US7391769B2 (en) | 2003-06-27 | 2008-06-24 | Lucent Technologies Inc. | Packet aggregation for real time services on packet data networks |
US7319674B2 (en) | 2003-07-24 | 2008-01-15 | Cisco Technology, Inc. | System and method for exchanging awareness information in a network environment |
US7613991B1 (en) | 2003-08-19 | 2009-11-03 | Altera Corporation | Method and apparatus for concurrent calculation of cyclic redundancy checks |
US7324553B1 (en) | 2003-09-30 | 2008-01-29 | Packeteer, Inc. | Dynamic bandwidth management responsive to access link state in redundant network topologies |
GB2406663B (en) | 2003-10-01 | 2006-03-22 | Toshiba Res Europ Ltd | Flexible protocol stack |
US7549042B2 (en) | 2003-12-16 | 2009-06-16 | Microsoft Corporation | Applying custom software image updates to non-volatile storage in a failsafe manner |
US20050138276A1 (en) | 2003-12-17 | 2005-06-23 | Intel Corporation | Methods and apparatus for high bandwidth random access using dynamic random access memory |
US7219293B2 (en) | 2003-12-17 | 2007-05-15 | Macronix International Co., Ltd. | High performance CRC calculation method and system with a matrix transformation strategy |
KR100600673B1 (en) | 2003-12-18 | 2006-07-18 | 한국전자통신연구원 | A method for requesting and reporting channel quality information in wireless system and apparatus thereof |
US7649855B1 (en) * | 2003-12-22 | 2010-01-19 | Marvell International Ltd. | Alternative 1000BASE-T scrambler |
US7603146B2 (en) | 2004-01-12 | 2009-10-13 | Avaya Inc. | Efficient power management in wireless local area networks |
WO2005067532A2 (en) | 2004-01-14 | 2005-07-28 | Riverstone Networks, Inc. | Managing processing utilization in a network node |
DE102004004878B4 (en) | 2004-01-30 | 2008-08-28 | Infineon Technologies Ag | Method and device for data transmission of voice data packets |
US7249306B2 (en) | 2004-02-20 | 2007-07-24 | Nvidia Corporation | System and method for generating 128-bit cyclic redundancy check values with 32-bit granularity |
US7817659B2 (en) | 2004-03-26 | 2010-10-19 | Foundry Networks, Llc | Method and apparatus for aggregating input data streams |
US8730961B1 (en) | 2004-04-26 | 2014-05-20 | Foundry Networks, Llc | System and method for optimizing router lookup |
US8806103B2 (en) | 2004-04-28 | 2014-08-12 | Hewlett-Packard Development Company, L.P. | System and method for interleaving memory |
JP4125262B2 (en) * | 2004-05-07 | 2008-07-30 | 矢崎総業株式会社 | Non-contact level sensor |
US8054751B2 (en) | 2004-05-10 | 2011-11-08 | Alcatel Lucent | Remote access link fault indication mechanism |
US7228509B1 (en) | 2004-08-20 | 2007-06-05 | Altera Corporation | Design tools for configurable serial communications protocols |
US8259562B2 (en) | 2004-10-07 | 2012-09-04 | Cisco Technology, Inc. | Wiring closet redundancy |
KR100674916B1 (en) | 2004-10-28 | 2007-01-26 | 삼성전자주식회사 | Twisted lines for transferring multi-phase clocks and a semiconductor device using the same |
US7680107B2 (en) | 2004-11-30 | 2010-03-16 | Broadcom Corporation | High speed trunking in a network device |
US7933947B2 (en) | 2004-12-28 | 2011-04-26 | Sap Ag | Connection manager that supports failover protection |
US7688476B2 (en) | 2005-01-03 | 2010-03-30 | Eastman Kodak Company | Apparatus and method for printing validated image data in a noisy environment |
US7782805B1 (en) | 2005-02-08 | 2010-08-24 | Med Belhadj | High speed packet interface and method |
US7499395B2 (en) * | 2005-03-18 | 2009-03-03 | Cisco Technology, Inc. | BFD rate-limiting and automatic session activation |
US7543305B2 (en) | 2005-03-24 | 2009-06-02 | International Business Machines Corporation | Selective event registration |
KR100687739B1 (en) | 2005-03-29 | 2007-02-27 | 한국전자통신연구원 | Method for monitoring link performance and diagnosing active status of link for Ethernet Passive Optical Network |
US7609617B2 (en) | 2005-04-14 | 2009-10-27 | Cisco Technology, Inc. | BGP hitless upgrade approaches |
US8730814B2 (en) | 2005-05-25 | 2014-05-20 | Alcatel Lucent | Communication network connection failure protection methods and systems |
US7424666B2 (en) | 2005-09-26 | 2008-09-09 | Intel Corporation | Method and apparatus to detect/manage faults in a system |
US7821972B1 (en) | 2005-09-29 | 2010-10-26 | Cisco Technology, Inc. | System and method for building large-scale layer 2 computer networks |
US8054830B2 (en) * | 2005-12-07 | 2011-11-08 | Alcatel Lucent | Managing the distribution of control protocol information in a network node |
US8448162B2 (en) | 2005-12-28 | 2013-05-21 | Foundry Networks, Llc | Hitless software upgrades |
US8131628B2 (en) | 2006-01-29 | 2012-03-06 | INXS Technologies Ltd. | System, method, and computer program for realizing a unified brokerage access channel |
US7624283B2 (en) | 2006-02-13 | 2009-11-24 | International Business Machines Corporation | Protocol for trusted platform module recovery through context checkpointing |
US7432467B2 (en) | 2006-03-28 | 2008-10-07 | Tokyo Electron Limited | Plasma processing apparatus |
US7606968B2 (en) | 2006-05-08 | 2009-10-20 | Mcdata Corporation | Multi-level content addressable memory |
US20070288690A1 (en) | 2006-06-13 | 2007-12-13 | Foundry Networks, Inc. | High bandwidth, high capacity look-up table implementation in dynamic random access memory |
EP2033305B1 (en) | 2006-06-27 | 2015-08-05 | Nxp B.V. | Mixer circuit and method to operate this mixer circuit |
US8718060B2 (en) | 2006-07-31 | 2014-05-06 | Cisco Technology, Inc. | Technique for multiple path forwarding of label-switched data traffic |
GB2443229B (en) | 2006-08-23 | 2009-10-14 | Cramer Systems Ltd | Capacity management for data networks |
US20080126652A1 (en) | 2006-09-27 | 2008-05-29 | Intel Corporation | Managing Interrupts in a Partitioned Platform |
US7827471B2 (en) | 2006-10-12 | 2010-11-02 | Intel Corporation | Determining message residue using a set of polynomials |
US7557689B2 (en) * | 2006-11-20 | 2009-07-07 | Solana Networks Inc. | Alerting method, apparatus, server, and system |
US8238255B2 (en) | 2006-11-22 | 2012-08-07 | Foundry Networks, Llc | Recovering from failures without impact on data traffic in a shared bus architecture |
US20080159309A1 (en) | 2006-12-29 | 2008-07-03 | Huawei Technologies Co., Inc. (Usa) | System and method of mapping between local and global service instance identifiers in provider networks |
US7978614B2 (en) | 2007-01-11 | 2011-07-12 | Foundry Network, LLC | Techniques for detecting non-receipt of fault detection protocol packets |
US7821925B2 (en) | 2007-01-29 | 2010-10-26 | Fulcrum Microsystems, Inc. | Traffic distribution techniques utilizing initial and scrambled hash values |
US8095846B2 (en) | 2007-06-08 | 2012-01-10 | Cortina Systems, Inc. | Data coding apparatus and methods |
US8037399B2 (en) | 2007-07-18 | 2011-10-11 | Foundry Networks, Llc | Techniques for segmented CRC design in high speed networks |
US8271859B2 (en) | 2007-07-18 | 2012-09-18 | Foundry Networks Llc | Segmented CRC design in high speed networks |
US8509236B2 (en) | 2007-09-26 | 2013-08-13 | Foundry Networks, Llc | Techniques for selecting paths and/or trunk ports for forwarding traffic flows |
US8014278B1 (en) | 2007-12-17 | 2011-09-06 | Force 10 Networks, Inc | Adaptive load balancing between ECMP or LAG port group members |
US8090901B2 (en) | 2009-05-14 | 2012-01-03 | Brocade Communications Systems, Inc. | TCAM management approach that minimize movements |
US8599850B2 (en) * | 2009-09-21 | 2013-12-03 | Brocade Communications Systems, Inc. | Provisioning single or multistage networks using ethernet service instances (ESIs) |
US8495418B2 (en) | 2010-07-23 | 2013-07-23 | Brocade Communications Systems, Inc. | Achieving ultra-high availability using a single CPU |
-
2007
- 2007-12-10 US US11/953,743 patent/US7978614B2/en active Active
- 2007-12-10 US US11/953,751 patent/US8155011B2/en active Active
- 2007-12-10 US US11/953,745 patent/US20090279441A1/en not_active Abandoned
- 2007-12-10 US US11/953,742 patent/US8395996B2/en active Active
-
2013
- 2013-02-13 US US13/766,330 patent/US9112780B2/en active Active
Patent Citations (99)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US3866175A (en) * | 1974-04-24 | 1975-02-11 | Ncr Co | Data communication system between a central computer and a plurality of data terminals |
US4723243A (en) * | 1985-12-02 | 1988-02-02 | Advanced Micro Devices, Inc. | CRC calculation machine with variable bit boundary |
US4807280A (en) * | 1987-09-18 | 1989-02-21 | Pacific Bell | Cross-connect switch |
US4985889A (en) * | 1988-02-04 | 1991-01-15 | Sprint International Communications Corporation | Data packet switching |
US4896277A (en) * | 1988-05-03 | 1990-01-23 | Thermo King Corporation | Method of mapping refrigerated containers in a power line carrier based monitoring system |
US5101404A (en) * | 1988-08-26 | 1992-03-31 | Hitachi, Ltd. | Signalling apparatus for use in an ATM switching system |
US5280582A (en) * | 1989-08-29 | 1994-01-18 | Digital Equipment Corporation | No-owner frame and multiple token removal mechanism for token ring networks |
US5301192A (en) * | 1990-08-31 | 1994-04-05 | Alcatel N.V. | Temporary information storage system comprising a buffer memory storing data structured in fixed or variable length data blocks |
US5875200A (en) * | 1990-11-08 | 1999-02-23 | Cirrus Logic, Inc. | Reed-Solomon code system employing k-bit serial techniques for encoding and burst error trapping |
US5490258A (en) * | 1991-07-29 | 1996-02-06 | Fenner; Peter R. | Associative memory for very large key spaces |
US5287477A (en) * | 1991-08-07 | 1994-02-15 | Hewlett-Packard Company | Memory-resource-driven arbitration |
US5282196A (en) * | 1991-10-15 | 1994-01-25 | Hughes Aircraft Company | Bursted and non-bursted data router |
US5195181A (en) * | 1992-01-10 | 1993-03-16 | Digital Equipment Corporation | Message processing system having separate message receiving and transmitting processors with message processing being distributed between the separate processors |
US5392279A (en) * | 1992-01-17 | 1995-02-21 | Fujitsu Limited | Interconnection network with self-routing function |
US5307345A (en) * | 1992-06-25 | 1994-04-26 | Digital Equipment Corporation | Method and apparatus for cut-through data packet transfer in a bridge device |
US5390173A (en) * | 1992-10-22 | 1995-02-14 | Digital Equipment Corporation | Packet format in hub for packet data communications system |
US5506840A (en) * | 1992-12-18 | 1996-04-09 | Alcatel N.V. | Asynchronous switching node and routing logic means for a switching element used therein |
US5406643A (en) * | 1993-02-11 | 1995-04-11 | Motorola, Inc. | Method and apparatus for selecting between a plurality of communication paths |
US5408469A (en) * | 1993-07-22 | 1995-04-18 | Synoptics Communications, Inc. | Routing device utilizing an ATM switch as a multi-channel backplane in a communication network |
US5600795A (en) * | 1993-08-28 | 1997-02-04 | U.S. Philips Corporation | Local network operating in asynchronous transfer mode (ATM) generating control cell containing information about the user, address of the station, and user-related identification |
US5740176A (en) * | 1994-05-19 | 1998-04-14 | Dagaz Technologies, Inc. | Scalable multimedia network |
US6522656B1 (en) * | 1994-09-12 | 2003-02-18 | 3Com Corporation | Distributed processing ethernet switch with adaptive cut-through switching |
US5862350A (en) * | 1994-12-22 | 1999-01-19 | Intel Corporation | Method and mechanism for maintaining integrity within SCSI bus with hot insertion |
US5619497A (en) * | 1994-12-22 | 1997-04-08 | Emc Corporation | Method and apparatus for reordering frames |
US5598410A (en) * | 1994-12-29 | 1997-01-28 | Storage Technology Corporation | Method and apparatus for accelerated packet processing |
US5721819A (en) * | 1995-05-05 | 1998-02-24 | Silicon Graphics Corporation | Programmable, distributed network routing |
US5732080A (en) * | 1995-07-12 | 1998-03-24 | Bay Networks, Inc. | Method and apparatus for controlling data flow within a switching device |
US5870538A (en) * | 1995-07-19 | 1999-02-09 | Fujitsu Network Communications, Inc. | Switch fabric controller comparator system and method |
US5872769A (en) * | 1995-07-19 | 1999-02-16 | Fujitsu Network Communications, Inc. | Linked list structures for multiple levels of control in an ATM switch |
US5872783A (en) * | 1996-07-24 | 1999-02-16 | Cisco Systems, Inc. | Arrangement for rendering forwarding decisions for packets transferred among network switches |
US5867675A (en) * | 1996-08-06 | 1999-02-02 | Compaq Computer Corp | Apparatus and method for combining data streams with programmable wait states |
US6035414A (en) * | 1996-11-08 | 2000-03-07 | Hitachi, Ltd. | Reliability of crossbar switches in an information processing system |
US6172990B1 (en) * | 1997-06-19 | 2001-01-09 | Xaqti Corporation | Media access control micro-RISC stream processor and method for implementing the same |
US6016310A (en) * | 1997-06-30 | 2000-01-18 | Sun Microsystems, Inc. | Trunking support in a high performance network device |
US6532234B1 (en) * | 1997-07-01 | 2003-03-11 | Nec Corporation | Back-pressure type ATM switch |
US6178520B1 (en) * | 1997-07-31 | 2001-01-23 | Lsi Logic Corporation | Software recognition of drive removal or insertion in a storage system |
US6678248B1 (en) * | 1997-08-29 | 2004-01-13 | Extreme Networks | Policy based quality of service |
US6343072B1 (en) * | 1997-10-01 | 2002-01-29 | Cisco Technology, Inc. | Single-chip architecture for shared-memory router |
US6023471A (en) * | 1997-10-07 | 2000-02-08 | Extreme Networks | Network interconnect device and protocol for communicating data among packet forwarding devices |
US6038288A (en) * | 1997-12-31 | 2000-03-14 | Thomas; Gene Gilles | System and method for maintenance arbitration at a switching node |
US6859438B2 (en) * | 1998-02-03 | 2005-02-22 | Extreme Networks, Inc. | Policy based quality of service |
US6363077B1 (en) * | 1998-02-13 | 2002-03-26 | Broadcom Corporation | Load balancing in link aggregation and trunking |
US6356942B1 (en) * | 1998-05-13 | 2002-03-12 | Axis Ab | Integrated circuit and method for bringing an integrated circuit to execute instructions |
US6181699B1 (en) * | 1998-07-01 | 2001-01-30 | National Semiconductor Corporation | Apparatus and method of assigning VLAN tags |
US6335932B2 (en) * | 1998-07-08 | 2002-01-01 | Broadcom Corporation | High performance self balancing low cost network switching architecture based on distributed hierarchical shared memory |
US6335935B2 (en) * | 1998-07-08 | 2002-01-01 | Broadcom Corporation | Network switching architecture with fast filtering processor |
US7176911B1 (en) * | 1999-02-02 | 2007-02-13 | Olympus Corporation | Solid-state imaging apparatus |
US6839346B1 (en) * | 1999-04-05 | 2005-01-04 | Nec Corporation | Packet switching apparatus with high speed routing function |
US6842422B1 (en) * | 1999-06-15 | 2005-01-11 | Marconi Communications, Inc. | Data striping based switching system |
US6697359B1 (en) * | 1999-07-02 | 2004-02-24 | Ancor Communications, Inc. | High performance switch fabric element and switch systems |
US6356550B1 (en) * | 1999-07-30 | 2002-03-12 | Mayan Networks Corporation | Flexible time division multiplexed bus using sonet formatting |
US20050041684A1 (en) * | 1999-10-01 | 2005-02-24 | Agilent Technologies, Inc. | Multi-channel network monitoring apparatus, signal replicating device, and systems including such apparatus and devices, and enclosure for multi-processor equipment |
US6687247B1 (en) * | 1999-10-27 | 2004-02-03 | Cisco Technology, Inc. | Architecture for high speed class of service enabled linecard |
US6708000B1 (en) * | 1999-10-29 | 2004-03-16 | Fujitsu Limited | Photonic node, photonic nodes for transmission and reception, and method of restoring traffic upon occurrence of link failure in optical path network |
US6839349B2 (en) * | 1999-12-07 | 2005-01-04 | Broadcom Corporation | Mirroring in a stacked network switch configuration |
US6681332B1 (en) * | 2000-03-13 | 2004-01-20 | Analog Devices, Inc. | System and method to place a device in power down modes/states and restore back to first mode/state within user-controlled time window |
US6700894B1 (en) * | 2000-03-15 | 2004-03-02 | Broadcom Corporation | Method and apparatus for shared buffer packet switching |
US7012919B1 (en) * | 2000-04-19 | 2006-03-14 | Caspian Networks, Inc. | Micro-flow label switching |
US6351143B1 (en) * | 2000-05-01 | 2002-02-26 | Xilinx, Inc. | Content-addressable memory implemented using programmable logic |
US20020001307A1 (en) * | 2000-05-20 | 2002-01-03 | Equipe Communications Corporation | VPI/VCI availability index |
US20020012585A1 (en) * | 2000-06-09 | 2002-01-31 | Broadcom Corporation | Gigabit switch with fast filtering processor |
US7009968B2 (en) * | 2000-06-09 | 2006-03-07 | Broadcom Corporation | Gigabit switch supporting improved layer 3 switching |
US6865153B1 (en) * | 2000-09-20 | 2005-03-08 | Alcatel | Stage-implemented QoS shaping for data communication switch |
US6696917B1 (en) * | 2000-09-21 | 2004-02-24 | Nortel Networks Limited | Folded Clos architecture switching |
US6854117B1 (en) * | 2000-10-31 | 2005-02-08 | Caspian Networks, Inc. | Parallel network processor array |
US6697368B2 (en) * | 2000-11-17 | 2004-02-24 | Foundry Networks, Inc. | High-performance network switch |
US7512127B2 (en) * | 2000-11-17 | 2009-03-31 | Foundry Networks, Inc. | Backplane interface adapter |
US6691202B2 (en) * | 2000-12-22 | 2004-02-10 | Lucent Technologies Inc. | Ethernet cross point switch with reduced connections by using column control buses |
US7191277B2 (en) * | 2001-02-23 | 2007-03-13 | Hewlett-Packard Development Company, L.P. | Dynamic allocation of devices to host controllers |
US7324509B2 (en) * | 2001-03-02 | 2008-01-29 | Broadcom Corporation | Efficient optimization algorithm in memory utilization for network applications |
US6990102B1 (en) * | 2001-05-10 | 2006-01-24 | Advanced Micro Devices, Inc. | Parallel lookup tables for locating information in a packet switched network |
US20030009466A1 (en) * | 2001-06-21 | 2003-01-09 | Ta John D. C. | Search engine with pipeline structure |
US20030033435A1 (en) * | 2001-07-17 | 2003-02-13 | Hanner Brian D. | System and method for multidimensional data compression |
US7191468B2 (en) * | 2001-07-17 | 2007-03-13 | The Boeing Company | System and method for multidimensional data compression |
US7005812B2 (en) * | 2001-07-23 | 2006-02-28 | Lawrence Hardy Mitchell | Commutation converter for a brushless servo motor |
US20080069125A1 (en) * | 2001-07-31 | 2008-03-20 | Interactic Holdings, Llc | Means and apparatus for a scalable congestion free switching system with intelligent control |
US20030048785A1 (en) * | 2001-08-28 | 2003-03-13 | International Business Machines Corporation | Network processor with single interface supporting tree search engine and CAM |
US7167471B2 (en) * | 2001-08-28 | 2007-01-23 | International Business Machines Corporation | Network processor with single interface supporting tree search engine and CAM |
US20030043800A1 (en) * | 2001-08-30 | 2003-03-06 | Sonksen Bradley Stephen | Dynamic data item processing |
US20030043848A1 (en) * | 2001-08-30 | 2003-03-06 | Sonksen Bradley Stephen | Method and apparatus for data item processing control |
US20030061459A1 (en) * | 2001-09-27 | 2003-03-27 | Nagi Aboulenein | Method and apparatus for memory access scheduling to reduce memory access latency |
US7185141B1 (en) * | 2001-12-27 | 2007-02-27 | Netlogic Microsystems, Inc. | Apparatus and method for associating information values with portions of a content addressable memory (CAM) device |
US7190696B1 (en) * | 2002-03-05 | 2007-03-13 | Force10 Networks, Inc. | System and method for distributing packets among a plurality of paths to a destination |
US7161948B2 (en) * | 2002-03-15 | 2007-01-09 | Broadcom Corporation | High speed protocol for interconnecting modular network devices |
US7187687B1 (en) * | 2002-05-06 | 2007-03-06 | Foundry Networks, Inc. | Pipeline method and system for switching packets |
US7649885B1 (en) * | 2002-05-06 | 2010-01-19 | Foundry Networks, Inc. | Network routing system for enhanced efficiency and monitoring capability |
US20080002707A1 (en) * | 2002-05-06 | 2008-01-03 | Davis Ian E | Flexible method for processing data packets in a network routing system for enhanced efficiency and monitoring capability |
US20060034452A1 (en) * | 2002-06-20 | 2006-02-16 | Hitachi, Ltd. | Code calculating device |
US20040022263A1 (en) * | 2002-08-02 | 2004-02-05 | Xiaodong Zhao | Cross point switch with out-of-band parameter fine tuning |
US20040028060A1 (en) * | 2002-08-08 | 2004-02-12 | Samsung Electronics Co., Ltd. | Link state synchronization method and apparatus on ad-hoc network, and data structure therefor |
US20040054867A1 (en) * | 2002-09-13 | 2004-03-18 | Paulus Stravers | Translation lookaside buffer |
US7185266B2 (en) * | 2003-02-12 | 2007-02-27 | Alacritech, Inc. | Network interface device for error detection using partial CRCS of variable length message portions |
US20050010630A1 (en) * | 2003-05-13 | 2005-01-13 | International Business Machines Corporation | Method and apparatus for determining a remainder in a polynomial ring |
US20060031610A1 (en) * | 2004-08-03 | 2006-02-09 | Liav Ori R | FIFO sub-system with in-line correction |
US20070038798A1 (en) * | 2004-09-10 | 2007-02-15 | Bouchard Gregg A | Selective replication of data structures |
US7657703B1 (en) * | 2004-10-29 | 2010-02-02 | Foundry Networks, Inc. | Double density content addressable memory (CAM) lookup scheme |
US20080031263A1 (en) * | 2006-08-07 | 2008-02-07 | Cisco Technology, Inc. | Method and apparatus for load balancing over virtual network links |
US20080037544A1 (en) * | 2006-08-11 | 2008-02-14 | Hiroki Yano | Device and Method for Relaying Packets |
US20080049742A1 (en) * | 2006-08-22 | 2008-02-28 | Deepak Bansal | System and method for ecmp load sharing |
Cited By (50)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7978702B2 (en) | 2000-11-17 | 2011-07-12 | Foundry Networks, Llc | Backplane interface adapter |
US8619781B2 (en) | 2000-11-17 | 2013-12-31 | Foundry Networks, Llc | Backplane interface adapter with error control and redundant fabric |
US9030937B2 (en) | 2000-11-17 | 2015-05-12 | Foundry Networks, Llc | Backplane interface adapter with error control and redundant fabric |
US7995580B2 (en) | 2000-11-17 | 2011-08-09 | Foundry Networks, Inc. | Backplane interface adapter with error control and redundant fabric |
US7948872B2 (en) | 2000-11-17 | 2011-05-24 | Foundry Networks, Llc | Backplane interface adapter with error control and redundant fabric |
US8964754B2 (en) | 2000-11-17 | 2015-02-24 | Foundry Networks, Llc | Backplane interface adapter with error control and redundant fabric |
US8671219B2 (en) | 2002-05-06 | 2014-03-11 | Foundry Networks, Llc | Method and apparatus for efficiently processing data packets in a computer network |
US7830884B2 (en) | 2002-05-06 | 2010-11-09 | Foundry Networks, Llc | Flexible method for processing data packets in a network routing system for enhanced efficiency and monitoring capability |
US8170044B2 (en) | 2002-05-06 | 2012-05-01 | Foundry Networks, Llc | Pipeline method and system for switching packets |
US8989202B2 (en) | 2002-05-06 | 2015-03-24 | Foundry Networks, Llc | Pipeline method and system for switching packets |
US8194666B2 (en) | 2002-05-06 | 2012-06-05 | Foundry Networks, Llc | Flexible method for processing data packets in a network routing system for enhanced efficiency and monitoring capability |
US9461940B2 (en) | 2003-05-15 | 2016-10-04 | Foundry Networks, Llc | System and method for high speed packet transmission |
US8718051B2 (en) | 2003-05-15 | 2014-05-06 | Foundry Networks, Llc | System and method for high speed packet transmission |
US8811390B2 (en) | 2003-05-15 | 2014-08-19 | Foundry Networks, Llc | System and method for high speed packet transmission |
US8493988B2 (en) | 2004-03-26 | 2013-07-23 | Foundry Networks, Llc | Method and apparatus for aggregating input data streams |
US9338100B2 (en) | 2004-03-26 | 2016-05-10 | Foundry Networks, Llc | Method and apparatus for aggregating input data streams |
US7817659B2 (en) | 2004-03-26 | 2010-10-19 | Foundry Networks, Llc | Method and apparatus for aggregating input data streams |
US7953923B2 (en) | 2004-10-29 | 2011-05-31 | Foundry Networks, Llc | Double density content addressable memory (CAM) lookup scheme |
US7953922B2 (en) | 2004-10-29 | 2011-05-31 | Foundry Networks, Llc | Double density content addressable memory (CAM) lookup scheme |
US8448162B2 (en) | 2005-12-28 | 2013-05-21 | Foundry Networks, Llc | Hitless software upgrades |
US9378005B2 (en) | 2005-12-28 | 2016-06-28 | Foundry Networks, Llc | Hitless software upgrades |
US9030943B2 (en) | 2006-11-22 | 2015-05-12 | Foundry Networks, Llc | Recovering from failures without impact on data traffic in a shared bus architecture |
US9112780B2 (en) | 2007-01-11 | 2015-08-18 | Foundry Networks, Llc | Techniques for processing incoming failure detection protocol packets |
US7978614B2 (en) | 2007-01-11 | 2011-07-12 | Foundry Network, LLC | Techniques for detecting non-receipt of fault detection protocol packets |
US8395996B2 (en) | 2007-01-11 | 2013-03-12 | Foundry Networks, Llc | Techniques for processing incoming failure detection protocol packets |
US8155011B2 (en) | 2007-01-11 | 2012-04-10 | Foundry Networks, Llc | Techniques for using dual memory structures for processing failure detection protocol packets |
US8037399B2 (en) | 2007-07-18 | 2011-10-11 | Foundry Networks, Llc | Techniques for segmented CRC design in high speed networks |
US8271859B2 (en) | 2007-07-18 | 2012-09-18 | Foundry Networks Llc | Segmented CRC design in high speed networks |
US20090282148A1 (en) * | 2007-07-18 | 2009-11-12 | Foundry Networks, Inc. | Segmented crc design in high speed networks |
US8149839B1 (en) | 2007-09-26 | 2012-04-03 | Foundry Networks, Llc | Selection of trunk ports and paths using rotation |
US8509236B2 (en) | 2007-09-26 | 2013-08-13 | Foundry Networks, Llc | Techniques for selecting paths and/or trunk ports for forwarding traffic flows |
US20090213745A1 (en) * | 2008-02-21 | 2009-08-27 | Fujitsu Limited | Frame monitoring device and frame monitoring method |
US8090901B2 (en) | 2009-05-14 | 2012-01-03 | Brocade Communications Systems, Inc. | TCAM management approach that minimize movements |
US8599850B2 (en) | 2009-09-21 | 2013-12-03 | Brocade Communications Systems, Inc. | Provisioning single or multistage networks using ethernet service instances (ESIs) |
US9166818B2 (en) | 2009-09-21 | 2015-10-20 | Brocade Communications Systems, Inc. | Provisioning single or multistage networks using ethernet service instances (ESIs) |
US8576698B2 (en) * | 2009-12-10 | 2013-11-05 | Alcatel Lucent | Connectivity fault management timeout period control |
US20110141911A1 (en) * | 2009-12-10 | 2011-06-16 | Alcatel-Lucent | Connectivity fault management timeout period control |
US8804770B2 (en) | 2010-10-14 | 2014-08-12 | Adtran Inc. | Communications system and related method for reducing continuity check message (CCM) bursts in connectivity fault management (CFM) maintenance association (MA) |
US8391319B2 (en) | 2010-10-14 | 2013-03-05 | Adtran, Inc. | Communications system and related method for reducing continuity check message (CCM) bursts in connectivity fault management (CFM) maintenance association (MA) |
US9497107B1 (en) * | 2013-06-06 | 2016-11-15 | Cisco Technology, Inc. | Seamless path monitoring and rapid fault isolation using bidirectional forwarding detection in a network environment |
US20190280914A1 (en) * | 2018-03-12 | 2019-09-12 | Spirent Communications, Inc. | Scalability, fault tolerance and fault management for twamp with a large number of test sessions |
US10613958B2 (en) | 2018-03-12 | 2020-04-07 | Spirent Communications, Inc. | Secure method for managing a virtual test platform |
US10693729B2 (en) | 2018-03-12 | 2020-06-23 | Spirent Communications, Inc. | Acceleration of node configuration for TWAMP with a large number of test sessions |
US10848372B2 (en) * | 2018-03-12 | 2020-11-24 | Spirent Communications, Inc. | Scalability, fault tolerance and fault management for TWAMP with a large number of test sessions |
US11032147B2 (en) | 2018-03-12 | 2021-06-08 | Spirent Communications, Inc. | Acceleration of node configuration for TWAMP with a large number of test sessions |
US11226883B2 (en) | 2018-03-12 | 2022-01-18 | Spirent Communications, Inc. | Secure method for managing a virtual test platform |
US11762748B2 (en) | 2018-03-12 | 2023-09-19 | Spirent Communications, Inc. | Test controller securely controlling a test platform to run test applications |
US10841196B2 (en) | 2018-03-26 | 2020-11-17 | Spirent Communications, Inc. | Key performance indicators (KPI) for tracking and correcting problems for a network-under-test |
US11483226B2 (en) | 2018-03-26 | 2022-10-25 | Spirent Communications, Inc. | Key performance indicators (KPI) for tracking and correcting problems for a network-under-test |
US11843535B2 (en) | 2018-03-26 | 2023-12-12 | Spirent Communications, Inc. | Key performance indicators (KPI) for tracking and correcting problems for a network-under-test |
Also Published As
Publication number | Publication date |
---|---|
US8155011B2 (en) | 2012-04-10 |
US20090279542A1 (en) | 2009-11-12 |
US9112780B2 (en) | 2015-08-18 |
US20090279440A1 (en) | 2009-11-12 |
US7978614B2 (en) | 2011-07-12 |
US20130343199A1 (en) | 2013-12-26 |
US20090279541A1 (en) | 2009-11-12 |
US8395996B2 (en) | 2013-03-12 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9112780B2 (en) | Techniques for processing incoming failure detection protocol packets | |
US20200259834A1 (en) | Fast heartbeat liveness between packet processing engines using media access control security (macsec) communication | |
US8634308B2 (en) | Path detection in trill networks | |
US8885488B2 (en) | Reachability detection in trill networks | |
US11902139B2 (en) | Diagnosing and resolving issues in a network using probe packets | |
US8098682B2 (en) | System and method for interfacing with a management system | |
EP3188450B1 (en) | Reducing false alarms when using network keep-alive messages | |
US20150003259A1 (en) | Network system and method of managing topology | |
EP3007494B1 (en) | Data processing method and device | |
US7580407B2 (en) | Method and apparatus for forwarding packet | |
US8811190B2 (en) | Maximum transmission unit (MTU) size discovery mechanism and method for data-link layers | |
TW200845608A (en) | Redundant wireless base station | |
US11489752B2 (en) | Forwarding entry monitoring method and apparatus | |
US20090132666A1 (en) | Method and apparatus for implementing a network based debugging protocol | |
WO2017157318A1 (en) | Link discovery method and apparatus | |
WO2020057475A1 (en) | Method for determining routing oscillation information and related device therefor | |
EP2929659A1 (en) | A method for automatically detecting physical connections of ethernet bridges connected to a root bridge | |
US7649906B2 (en) | Method of reducing buffer usage by detecting missing fragments and idle links for multilink protocols and devices incorporating same | |
WO2019196853A1 (en) | Tcp acceleration method and apparatus | |
US20210006512A1 (en) | Packet forwarding apparatus, network system, and packet forwarding method | |
JPH10336228A (en) | Router and network management equipment |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: FOUNDRY NETWORKS, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:WONG, YUEN;MOOBED, PEDMAN;REEL/FRAME:020233/0874 Effective date: 20071206 |
|
AS | Assignment |
Owner name: BANK OF AMERICA, N.A. AS ADMINISTRATIVE AGENT, CAL Free format text: SECURITY AGREEMENT;ASSIGNORS:BROCADE COMMUNICATIONS SYSTEMS, INC.;FOUNDRY NETWORKS, INC.;INRANGE TECHNOLOGIES CORPORATION;AND OTHERS;REEL/FRAME:022012/0204 Effective date: 20081218 Owner name: BANK OF AMERICA, N.A. AS ADMINISTRATIVE AGENT,CALI Free format text: SECURITY AGREEMENT;ASSIGNORS:BROCADE COMMUNICATIONS SYSTEMS, INC.;FOUNDRY NETWORKS, INC.;INRANGE TECHNOLOGIES CORPORATION;AND OTHERS;REEL/FRAME:022012/0204 Effective date: 20081218 |
|
AS | Assignment |
Owner name: WELLS FARGO BANK, NATIONAL ASSOCIATION, AS COLLATE Free format text: SECURITY AGREEMENT;ASSIGNORS:BROCADE COMMUNICATIONS SYSTEMS, INC.;FOUNDRY NETWORKS, LLC;INRANGE TECHNOLOGIES CORPORATION;AND OTHERS;REEL/FRAME:023814/0587 Effective date: 20100120 |
|
AS | Assignment |
Owner name: FOUNDRY NETWORKS, LLC, CALIFORNIA Free format text: CHANGE OF NAME;ASSIGNOR:FOUNDRY NETWORKS, INC.;REEL/FRAME:024733/0739 Effective date: 20090511 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |
|
AS | Assignment |
Owner name: INRANGE TECHNOLOGIES CORPORATION, CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:034792/0540 Effective date: 20140114 Owner name: FOUNDRY NETWORKS, LLC, CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:034792/0540 Effective date: 20140114 Owner name: BROCADE COMMUNICATIONS SYSTEMS, INC., CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:034792/0540 Effective date: 20140114 |
|
AS | Assignment |
Owner name: BROCADE COMMUNICATIONS SYSTEMS, INC., CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:WELLS FARGO BANK, NATIONAL ASSOCIATION, AS COLLATERAL AGENT;REEL/FRAME:034804/0793 Effective date: 20150114 Owner name: FOUNDRY NETWORKS, LLC, CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:WELLS FARGO BANK, NATIONAL ASSOCIATION, AS COLLATERAL AGENT;REEL/FRAME:034804/0793 Effective date: 20150114 |
|
AS | Assignment |
Owner name: EXTREME NETWORKS, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BROCADE COMMUNICATIONS SYSTEMS, INC.;FOUNDRY NETWORKS, LLC;REEL/FRAME:044125/0547 Effective date: 20171107 |