EP0594199A1 - Paketformat in Knotenpunkt für ein Datenübertragungssystem - Google Patents
Paketformat in Knotenpunkt für ein Datenübertragungssystem Download PDFInfo
- Publication number
- EP0594199A1 EP0594199A1 EP93117159A EP93117159A EP0594199A1 EP 0594199 A1 EP0594199 A1 EP 0594199A1 EP 93117159 A EP93117159 A EP 93117159A EP 93117159 A EP93117159 A EP 93117159A EP 0594199 A1 EP0594199 A1 EP 0594199A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- packet
- network
- header
- address
- message packet
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000004891 communication Methods 0.000 title claims abstract description 14
- 238000012546 transfer Methods 0.000 claims abstract description 16
- 238000000034 method Methods 0.000 claims description 107
- 230000008569 process Effects 0.000 claims description 89
- 238000013519 translation Methods 0.000 abstract description 28
- 230000014616 translation Effects 0.000 abstract description 28
- 230000005540 biological transmission Effects 0.000 abstract description 10
- 238000012545 processing Methods 0.000 description 24
- 230000006870 function Effects 0.000 description 18
- 238000010586 diagram Methods 0.000 description 8
- 238000001914 filtration Methods 0.000 description 7
- 230000007246 mechanism Effects 0.000 description 3
- 230000000977 initiatory effect Effects 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000006399 behavior Effects 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 230000002457 bidirectional effect Effects 0.000 description 1
- 230000000593 degrading effect Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/46—Interconnection of networks
Definitions
- This invention relates to packet data communication networks, and more particularly to a way of handling packets through a hub, switch or router for a network, using a special header attached to the packets.
- Packet data communication networks of type using Ethernet, token ring, or FDDI technologies, or other network varieties, hubs are used for switching or routing, or for bridges to additional segments of the network.
- a bridge or router in a computer interconnect system is shown in U.S. Patent 5,020,020, assigned to Digital Equipment Corporation. It is typical to use address translation in a bridge or router of this type, as shown, for example, in U.S. Patent 4,933,937. The need to translate addresses is due to the address length.
- Some protocols or system specify a 48-bit source and destination address so that a globally unique address is provided.
- Various other information may be locally useful in a bridge or router that need not be carried by a packet throughout its lifetime.
- the network segments may be locally named (assigned an identifying number) so that packets may be routed by link number instead of or in addition to their local destination node address.
- the packets may be assigned a priority or "service class" for local use, aside from the priority attached to the packet by the protocol being implemented.
- Status information may be locally useful, but not part of the packet protocol and not necessary for transmission with the packet throughout the network. For example, local congestion information, or results of address translations, or end-of-message information, are types of such status information.
- the invention in its broad form resides in a packet data communications network as recited in claim 1.
- the invention also resides in a method of operating a packet data communications network as recited in claim 5.
- a packet data communication network employs a local switch, router or bridge device functioning to transfer packets between segments of a larger network.
- a local switch, router or bridge device functioning to transfer packets between segments of a larger network.
- an address translation is performed to generate local source and destination addresses which are much shorter than the globally-unique addresses contained in the packet as dictated by the protocol.
- These local addresses are inserted in a header that is added to the packet, in addition to any header already contained in the packet. This added header travels with the packet through the local switch, router or bridge device, but then is stripped off before the packet is sent out onto another network segment.
- the added header may also contain other information, such as a local name for the source and destination segment (link), as well as status information that is locally useful, but not part of the packet protocol and not necessary for transmission with the packet throughout the network.
- a local name for the source and destination segment (link) as well as status information that is locally useful, but not part of the packet protocol and not necessary for transmission with the packet throughout the network.
- Local congestion information, results of address translations, and end-of-message information are examples of such status information.
- a packet data communications network which may use the features of the invention includes a controller 10 for interface between an FDDI link 11 and a crossbar switch device 12.
- the crossbar switch device 12 has a number of input/output ports 13, and each one of these ports 13 may be connected by another controller 10 to another network segment 11 such as an FDDI link or a token ring or Ethernet bus, for example.
- the crossbar switch 10 ordinarily makes a direct point-to-point interconnect between one port 13 and another port 13, so that the crossbar acts as a bridge or router in the network, linking one network segment to another.
- a station on a link 11 sends a packet onto its network segment with a destination address which is on another, different segment.
- the controller 10 for this segment detects the address as being that of a station on one of the remote segments, and generates local switching information to send to the crossbar 12 so that the appropriate interconnect can be made to send the packet to the proper port 13 and link 11, via another controller 10.
- the crossbar switch device can function as a flexible interconnect device to create a ring or bus using the ports 13, as well as functioning as a point-to-point connector as is the usual case for crossbar switches.
- each port 13 of the crossbar has a data-in path 14 and a separate data-out path 15.
- the interface between the controller 10 and the FDDI link 11 is by way of a media access control (MAC) device 16, functioning to convert the serial light transmission on the incoming fiber optic cable 17 to electrical pulses, to recover the clock, convert the serial data on the optic loop to 6-bit parallel symbols, act as an elastic buffer to allow reclocking of data entering the controller 10, etc.
- MAC media access control
- the interface between the controller 10 and the MAC device 16 is by an incoming 8-bit parallel data path 19a (with additional parity and control lines) and an outgoing 8-bit parallel path 19b.
- the controller 10 contains a processor or state machine 20 to execute various processes as will be described, and accesses a packet memory 21 via an interface 22, as well as a content addressable memory (CAM) 23 via interface 24.
- the packet memory 21 is addressed by a 20-bit address bus, and data is transferred by a 56-bit bidirectional data bus, included in the interface 22; various control lines are also in the interface 22.
- the CAM 23 is driven by a 14-bit bus and various control lines in the interface 24.
- the packet memory 21 is a RAM which stores a number of queues for incoming and outgoing data packets, as well as translation tables and hash tables as will be described. In addition, the packet memory stores certain data for which addresses are matched in the CAM 23.
- the controller 10 also interfaces with a line card processor 25 by bus 26.
- the line card processor 25 is used to execute some diagnostic and initialization functions, and does not operate in routine packet transfer.
- the processor 20 in the controller 10 executes six independent processes. There are two for inbound packet processing, two for outbound packet processing, one for interfacing to the external packet memory, and one for line card processor access. Packets inbound on FDDI line 17 and going through the controller 10 to the crossbar switch 12 are referred to as "inbound.” Likewise, packets going in the direction of crossbar switch 12 through the controller 10 to the FDDI output line 18 are referred to as "outbound.” By having independent processes which can operate in parallel, the controller 10 can process inbound and outbound packets at full speed. Distributed among the processes are control, parameter and status registers that are used to define the operational modes and to determine the internal state of the controller 10; these registers are accessed through the node processor interface 26.
- the inbound receive (IR) process 27 executed on the processor 20 receives packets from the interface 19a to the FDDI ring via the media access control device 16.
- the IR process 27 parses and decodes each incoming packet from line 19a, places the packet data into an intermediate FIFO 28, and performs the necessary processing to determine if the packet is to be forwarded to the crossbar 12. For bridged packets, this decision is made by performing destination address, source address, and protocol field lookups, with the aid of the content addressable memory 23 and the internal hash function, according to the invention. The result of the lookup will determine where the packet is to go.
- the packet may have to be transmitted to another port 13 on the crossbar 12 to reach its destination, the packet may be destined for the line card processor 25, the packet may be destined for a processing engine 38 in the crossbar switch 12, or the packet may be filtered and discarded.
- the IR process 27 decides a packet is to be forwarded to the crossbar 12, it uses the lockup results to generate the information in an added header as will be described. It will select an inbound queue to store the packet in the external packet memory 21 and will initiate memory requests to transfer the data from its intermediate FIFO 28 to the selected queue in the external packet memory 21. The processor 20 executing this IR process 27 performs this operation by generating IR requests that are sent to the packet memory 21.
- the IR process 27 also handles a number of exception conditions.
- the forwarding of packets to processing engines in the switch 12 can be rate limited by software to prevent the traffic from a single port from overwhelming the shared processing resources of the switch 12. When these rate limits are exceeded the IR process 27 will discard these packets until the rate limit is replenished.
- the IT process 29 Prior to requesting the connection, the IT process 29 checks the timestamp stored with the packet and will discard the packet if it has expired. If the IT process 29 determines that a packet has expired after a connection has been requested but before the connection is made, it will discard the packet, abort the requested connection and continue servicing the enabled queues.
- the IT process 29 transfers the data from its intermediate FIFO 30 to the crossbar 12 via path 14 and performs the proper packet formatting during transmission.
- the outbound receive (OR) process 31 executing on the processor 20 receives packets from the crossbar switch 12 interface 15, parses and decodes each packet, places the packet data into an intermediate FIFO 32 and performs the necessary validity checks of the packet's added header to determine if the packet should be received and placed at the tail of an enabled queue in packet memory 21. Packet reception is established when the controller 38 for the crossbar indicates that this controller 10 is the desired destination port for a connection.
- the OR process 31 indicates its willingness to take part in a connection by asserting a "next" control signal in the interface 15 that the crossbar controller 38 samples.
- the crossbar controller may return a signal indicating that a connection between a source port and this destination port has been made on the crossbar 12.
- the OR process 31 immediately monitors the outbound data received at the crossbar interface 15 to delimit a packet. It will also deassert the "next" signal and will not reassert it until it has determined that it is appropriate to establish a new connection.
- the OR process 31 uses the service class field and one specific protocol class field value from the added header of the outbound packet to place the packet on a queue in external packet memory 21.
- the OR process 31 also handles multiple exception conditions on the crossbar including parity errors in the symbols, and packets with bad delimiters.
- the outbound transmit (OT) process 33 services the queues in packet memory 21 that contain packets to be transmitted to the FDDI line 18 via path 19b and device 16. These packets are stored in the external packet memory 21 of the controller 10. When an enabled queue has a packet count greater than one, the OT process 33 will begin processing the packet by initiating packet memory requests to move the data from the external memory 21 to an internal fifo 34. The OT process 33 will discard the packet if the time stamp stored with the packet has expired, otherwise it will request the MAC device 16 to begin a transmission to the FDDI line 18. If the OT process 33 is operating in a bridge link mode, it will decapsulate the packet by removing the added header that was stored with the packet, prior to transmission on the path 19b to the FDDI link. If the OT process 33 is attached to a switch link, it will keep and update the appropriate fields of the added header during transmission to the path 19b and FDDI link.
- the packet memory (PM) access process 35 controls the interface 22 to the external packet memory 21.
- the packet memory 21 is used to hold the packet data of the multiple inbound and outbound queues and is also used to store the PC table, the hash table as described herein, and the translation database used for lookups.
- the PM process 35 controls access to the external packet memory 21 by arbitrating among all the processes requesting access to it. The PM process 35 will indicate to the requesting process when a cycle has been granted.
- the external packet memory is accessed via a 56-bit data bus in interface 22.
- the PM process 35 can select up to 1-million 56-bit words over its 20-bit external packet memory address bus in interface 22. Read or write cycles can be performed every 80-ns to provide 600-Mbps of packet memory bandwidth.
- a process 27, 29, 31, or 33 requests a memory cycle via paths 36, 37, 42, or 43, respectively, it also indicates to the PM process 35 the desired queue that the cycle is associated with by driving the queue number.
- the PM process 35 grants the cycle to the requesting process, it uses the queue number provided to simultaneously enable the pointers for the queue to the external memory 21.
- the PM process 35 will drive the corresponding tail (write cycle) or head (read cycle) pointer onto the external address pins of interface 22 and will perform the necessary pointer maintenance when the cycle completes.
- the maintenance includes wrapping the head or tail pointer when the boundary of a queue is reached.
- the PM process 35 will also monitor the queue pointers to detect and signal when a queue is approaching an overflow condition.
- Each queue in the external packet memory 21 must be defined before the PM process 35 can perform an access to it.
- the boundaries for the queue must be specified by programming the external memory block addresses that point to the beginning and end of each queue.
- a queue is programmable in size in increments of 256 56-bit word units (1792 bytes) which constitute a block.
- the owners of the queue head and tail must be specified, to control the direction of packet flow.
- a separate queue enable is provided for each queue in order to turn each one on and off independently.
- the line card processor (LCP) access process 40 provides the interface between the processor 25 and the command and status registers 41 within the controller 10. Some of these registers are accessed directly by the processor 25 and some are accessed indirectly using the LCP process 40. The registers 41 that are indirectly accessible are shared among the processes 27, 29, 31, 33, and 35 of the controller 10 and must be arbitrated for.
- the indirect access interface of the LCP process 40 provides the mechanisms to select the desired indirect register and to trigger the desired read or write operation. Since the processor 25 does not have direct access to the external packet memory 21 of the controller 10, it must also use the indirect access interface of the LCP process 40 to perform read and write cycles to the external memory 21.
- the LCP process 40 In addition to direct and indirect register 41 access, the LCP process 40 also maintains the traffic event counters and interrupt event registers.
- the LCP process 40 monitors the traffic events signaled by the processes 27, 29, 31, 33, and 35 to update the corresponding counter.
- the LCP process 40 provides two general purpose counters that can be programmed to count a particular traffic event. The LCP monitors events in the controller 10 and will set corresponding interrupts. These interrupts are categorized to be associated with inbound traffic, outbound traffic, or fatal interrupts. All interrupts, except fatal interrupts, are maskable. The presence of a non-masked interrupt will result in the assertion of an interrupt signal.
- the operation of the processor 20 in controller 10 using the processes referred to includes a number of functions related to inbound and outbound packets. These include filtering, address lookup, address matching, rate limiting, parity checking, etc.
- the controller 10 performs input port filtering to prevent undesired traffic from entering the net, and this filtering is based on certain addresses contained in a packet.
- a 48-bit destination address and a 48-bit source address in the packet can be filtered for a number of addresses, up to the size of the translation table in memory 21.
- Certain addresses identified in the protocol as IEEE 802.2 LLC DSAP and IEEE 802.2 LLC SNAP can be filtered by checking against items stored in the CAM 23, e.g., 256 entries.
- the controller 10 implements an optimized hash algorithm which can perform a 48-bit address lookup in at most four references to the external memory 21.
- the hash function is programmable, and is specified by a 48-bit value called the hash function.
- the lookup includes one memory reference to a hash table in memory 21, followed by at most three references to the translation database which contains a breadth-first binary tree in which hashed 48-bit addresses are stored, as will be explained.
- the controller 10 supports exact matching of certain 48-bit destination addresses (group or individual), certain 48-bit source addresses, 8-bit DSAP and 40-bit PID fields, by an interface to the external CAM 23.
- the controller 10 can obtain by interface 24 a 14-bit associated data field for each entry stored in the CAM 23.
- the ability to match data fields of varying byte widths is achieved by specifying a type code field driven by the controller 10 during the reception of packets.
- the bits of the type code indicate the size of the field to match in the CAM array 23 and the type of key data.
- a key can be from one to six bytes in length.
- the controller 10 provides programmable rate limits to throttle the packet rate and limit the transmit queue length of excess packets that are destined for switch processing engines. For example, these rate limits would be applied to errored packets, monitor packets, or bridge learning packets with an unknown source address to be sent to the controller 38 for the switch 12.
- the controller 10 performs output port filtering based on the added header protocol class, and performs parity checking of the crossbar data path.
- the controller 10 can be used to attach a variety of links to the crossbar 12.
- the parameters that define the operation of controller 10 describe the type of link to which the controller 10 is attached through the MAC interface 19a, 19b, the type of inbound and outbound forwarding procedures it is to perform, and the format of the packets it is to handle.
- All external links are attached to the controller 10 through the MAC interface 19a, 19b. Any physical channel can be attached to the controller 10 through a formatter that adheres to the specification of the MAC receive and transmit data paths 19a, 19b.
- the MAC interface 19a, 19b and the controller 10 can operate in either half or full duplex modes.
- the crossbar interface 14, 15 of the controller 10 is a full duplex interface that can establish connections and transmit to the crossbar 12 while simultaneously accepting connections and receiving frames from the crossbar.
- the services that the controller 10 is to provide for the traffic on the attached link 11 must be specified.
- This aspect of link specification defines the controller 10 inbound and outbound forwarding/filtering procedures and additionally defines the format of the frames which the controller 10 will process.
- the controller 10 can attach to three types of links, particularly bridge links, internal switch links, and relay links.
- a bridge link attaches a network segment 11 of an extended LAN to the net. That is, referring to Figure 3, what may be thought of as a higher level network 50 (referred to also as the "GigaNet”) contains the crossbar switch 12 as one of its elements, and the controller 10 is the bridge between the FDDI link 11 and the net 50.
- GigaNet higher level network 50
- the controller 10 is the bridge between the FDDI link 11 and the net 50.
- many other LANs such as the FDDI 11 or Ethernet LANs, etc., would be connected to the net 50 via other ports 13 of the crossbar switch 12, or through other crossbar switches 12 in the net 50 (using other controllers 10 or their equivalent).
- the crossbar device 12 may function as classic point-to-point connector, or as set forth in the above-mentioned copending applications, may create a ring or bus, or may be create a mixed configuration of rings, buses and point-to-point connectors.
- the controller 10 will expect to receive and transmit frames in FDDI format at the MAC interface 19a, 19b, and will perform inbound lookups on the destination address, source address, and protocol fields, and translate the packet to switch frame format.
- the controller 10 will perform outbound checks and will perform protocol class lookup on the switch frames received from the crossbar 12 and translate the frames back to FDDI frame format prior to transmission to the MAC interface 19a, 19b.
- An internal switch link connects switches in the net 50 together or attaches net end nodes to the net 50.
- the controller 10 can operate in this switch link mode. In this mode, the controller 10 will expect to receive and transmit frames in switch frame format at its MAC interface 19a, 19b. It will perform inbound checks on the switch frame and transmit the packet to the crossbar 12. The controller 10 will perform outbound checks on the switch frame received from the crossbar and will transmit to the MAC interface 19a, 19b a switch frame.
- a relay link uses a full duplex FDDI link to attach switches 12 in the net 50 together.
- the controller 10 functioning in this mode will expect to receive and transmit frames in a relay frame format at the MAC interface 19a, 19b, and here its operation is similar to switch link attachment and simply translates the packet format by adding or stripping a local packet header.
- the type of link (bridge link, switch link, or relay link) that the controller 10 is attached to at the MAC interface 19a, 19b is specified by either decoding the frame control field of the received packet or by a type field in a control register 41 within the controller 10.
- the inbound and outbound processes 27, 29, 31, and 33 know the format of the frames that will be processed and the forwarding procedures it is to perform.
- the three different frame formats that may exist at the MAC interface 19a, 19b are illustrated, including an FDDI frame format 54, a switch frame format 55 (which encapsulates the FDDI frame 54), and a relay frame format 56 (which encapsulates the switch format 55).
- the original FDDI frame format 54 is of the form specified by the FDDI protocol, and will not be described in detail.
- FDDI format 54 Within the FDDI format 54 are an FDDI header 57, an 802.2 LLC header 58, an information field 59 (the payload), and an FDDI CRC field 60.
- Various other elements such as starting and ending delimiters are present.
- Within the header 57 are 48-bit source and destination addresses 61 and 62, and these are used in the address lookups as described herein.
- Other special addresses or identification specified in the protocol are contained in the LLC header 58, such as the ones mentioned above (DSAP and SNAP). Each of these addresses is extracted by the controller 10 and used for lookups and filtering as described herein.
- the FDDI frame format 54 is found at the MAC interface 19a, 19b of the controller 10. When attached to bridge links, this will be the format of the frames received by the IR process 27 and will be the format of frames transmitted by the OT process 33.
- the switch frame format 55 of Figure 4 is seen to be merely the original FDDI frame 54 to which is attached at the beginning an added header 63, also referred to as the "gigaheader". This added header 63 is described in detail below and is an important feature of the invention.
- the switch frame format 55 can appear on both the MAC interface 19a, 19b and the crossbar interface 14, 15. At the crossbar interface 14, 15, this is the common packet format used by the switch ports 13. It is the format transmitted by the IT process 29, and it is the format received by the OR process 31.
- the relay frame format 56 of Figure 4 consists of a switch frame format 55 (including FDDI format 54 and added header 63), to which is added a local FDDI header 64 and a local FDDI CRC field 65.
- the local FDDI header 64 is of the same specification as the FDDI header 57, and is defined in the FDDI protocol. This type of frame 56 is found at the MAC interface 19a, 19b of the controller 10 when it is attached to a relay link.
- the added header 63 (or "gigaheader”) is a thirteen byte (104-bit) field that is present in switch frames 55 and relay frames 56. It contains information that is generated by the inbound receive (IR) process 27 when a packet first enters the net 50 and is used to direct the packet to its destination within the net 50. This field 63 defines how the packet is to be serviced within the net 50. The packet processing within the net 50 is performed by examining the fields of this added header 63. Each of the fields in the added header 63 will now be described, referring also to Figure 5.
- the service class field 65 is a four-bit field that specifies the service class for the packet.
- the service class is used to determine the queue number in memory 21 that a packet is to be placed on by doing a lookup using certain internal registers 41.
- the service class is also used for connection queue servicing.
- the destination switch field 66 is a 12-bit field representing the switch number (i.e., local address) of the final destination of the packet within the net 50.
- the IR process 27 performs a lookup operation to derive the destination switch value for the packet.
- a 12-bit field allows 4096 ports; a single crossbar 12 has only thirty-six ports in one embodiment, so the need for a 12-bit address is because a number of the crossbars 12 may be within a net 50, and to allow for expansion to larger crossbars and larger nets 50.
- switch values are reserved: 02 hex and 03 hex indicate that the final destination is unknown to the IR process 29, and 00 hex and 01 hex indicate that the final destination address is to be filtered at this port. Other values derived for this field will direct the packet to its destination within the switch.
- the decapsulate bit 67 when set to one, indicates that this packet is to be decapsulated when it goes out onto a link that supports both relay and bridge frames.
- the outbound processes 31 and 33 of the controller 10 will sample this bit to make a determination of the transmission format to use. Usually this bit is set to zero.
- the destination link 68 is a 7-bit field representing the logical link number of the final destination of the packet, except when switch field 66 equals 00 hex , in which case this field 68 is the physical link number of the port that is to receive the message.
- the IR process 29 will generate this field when constructing the added header 63 for frames received from the FDDI interface 19a, 19b.
- the OR process 31 When enabled, the OR process 31 will compare this field to its own logical link number to verify that the crossbar connection is established in the correct port.
- Logical link numbers 00-to-07 hex are reserved for addressing the switch control processors x for switches 12 in the net 50.
- the protocol class field 69 of Figure 5 is an 8-bit field representing the protocol class assigned to the packet within the net 50.
- the IR process 29 will generate this field 69 when constructing the added header 63 for frames received from the FDDI interface 19a, 19b.
- the OR process 31 will sample this field 69 for frames received from the crossbar 12 to determine if the packet is enabled to be forwarded in the outbound direction.
- the values F0-to-FD hex of this field 69 are reserved for special net-wide protocols such as inter-switch control messages, initialization protocols, implementation of protocol trapping, and frames destined for a line control processor 25.
- the values FE and FF hex are used as filter protocol values. All other numbers are user-assignable.
- the source link type field 70 is a four bit field representing the type of data link that sourced the packet that the current added header 63 is attached to. This field 70 can be used to specify additional translation processing during the forwarding of the frame. The controller 10 does not use this field during packet processing.
- the source switch field 71 is a 12-bit field representing the switch number of the original source of this packet in the net 50.
- the values 00-to-03 hex are illegal on all data links, and certain ones are reserved; all other numbers are user assignable.
- the source link field 72 is a 7-bit field representing the logical link number of the original source of this packet in the net 50.
- the values 00-to-07 hex are reserved for use by the switch control processor x.
- the previous hop link field 73 is a 7-bit field representing the physical link number of the previous hop link. Thus it represents the link number that is currently sending the packet to the crossbar 12.
- the translation status field 74 is a 4-bit field which stores the result of the automatic translation performed on the current packet. The status may indicate whether the frame is to be forwarded to its destination, monitored, trapped, logged, or whether the source address of the frame was "new.”
- the type of time field 75 of Figure 5 is a 1-bit field representing the format for the timestamp in the current packet. When this bit is "0" the timestamp field represents absolute time, and when set to "1" the time stamp field is interpreted as a relative time to live.
- the end-of-packet stream field 76 is a 1-bit field which, when set to one, indicates that this packet is the last packet in a packet stream. Otherwise, when set to zero, it indicates the first or a middle packet in a packet stream.
- the system port field 77 is a 1-bit field which, when set to one, indicates that this packet is being sent from a system port (e.g., a switch control processor x port). This bit can be used during outbound packet processing to restrict certain types of packet to originate only from system ports.
- the copied frame field 78 is a 1-bit field which, when set to one, indicates that a copy frame is being sent to the crossbar 12. Copy frames are used to send exception traffic to engines within the switch 12.
- the outbound congestion bit 79 is a 1-bit field that is used to associate outbound congestion information with the added header 12 of the current packet.
- the inbound congestion bit 80 is a 1-bit field that is used to associate inbound congestion information with the added header 12 of the current packet.
- the timestamp field 81 is a 16-bit field representing a value from 00 to 65535 which is either the lowest 16-bits of an absolute time that the packet must be destroyed, or the number of time units the packet has to live. One time nit is 10-milliseconds.
- the timestamp is generated by the inbound receive process 27.
- Reserved field 82 represents 4-bits reserved for future specification. These should be sent as zeros and otherwise ignored.
- the header check field 83 is an 8-bit CRC covering the previous 96-bits of the 104-bit added header 63 (the "gigaheader").
- the controller 10 forwards inbound and outbound frames and performs the necessary translation to generate the desired packet formats 54-56, e.g., adding the header 63 if necessary.
- the forwarding and translation procedures that are performed by the processes 27, 29, 31, and 33 of the controller 10 are a function of the link type that the controller 10 is attached to and of course a function of whether the packet is inbound or outbound.
- the actions performed are: Perform a lookup of the frame control field of the received packet. Process the destination address 61, source address 62, and protocol fields of the inbound FDDI frame 54. Determine if the packet is to be forwarded/monitored and if there are any exception conditions. Generate the service class field 65, the destination switch field 66, the destination link field 68, and the protocol class field 69. Add a timestamp field 82 and the remaining header 63 fields to form a switch frame 55. Queue the packet in memory 21.
- the actions performed are: Perform a CAM lookup in CAM 23 using the protocol class field 69 of the received header 63. Check if the packet is to be monitored or trapped. Clear the system port bit 77 and check the timestamp 82 and checksum 83 for the header 63. Add the updated header 63 to the frame.
- the actions performed are: Perform a lookup of the frame control field of the received packet.
- the local header 64 is checked and removed from the relay frame 56. The procedure then proceeds as specified by the switch link.
- the actions performed are: Check added header 63 checksum 83 for the received frame. Check the fields of the header 63, including destination switch field 66, destination link field 68, and system port bit 77. Perform protocol class lookup for field 69. Verify that the timestamp 82 is still good, if not discard the frame. Strip header 63 from the packet to realize an FDDI frame format 54.
- the actions performed are: Check the added header 63 checksum 83 for the received frame. Check the fields of the header 63, including destination switch field 66, destination link field 68, and system port bit 77. Perform protocol class lookup for field 69. Verify that the timestamp 82 is still good, if not discard the frame.
- the actions performed are:
- the local header 64 is added to the switch frame 55.
- the procedures then proceed just as specified by the switch link, i.e., the frame is treated as if it were an FDDI frame 54.
- the controller 10 makes use of several lookup mechanisms to process the fields of the frame. These include the CAM lookup, the hash lookup, a class specifier lookup, and a protocol class lookup.
- the CAM lockup consists of applying an address or value to the CAM 23, and getting back an indication of whether or not a match is found in the CAM 23.
- the CAM 23 is of limited size due to the cost (number of transistors) inherent in constructing a CAM. In an example embodiment, the CAM 23 holds 256 entries. Thus, there can be 256 values (addresses, etc.) that are searched for in a CAM lockup.
- the IR process 27 uses the CAM lookup to perform matches using the various fields of the received frame 54, 55, or 56 as keys.
- Variable width key matching is provided, up to six bytes wide, and this is specified by the IR process 27 during the parse of the frame, and a match result return an associated data value that will be used by the IR process 27.
- This CAM match can be used to find the frame control, destination address, source address, DSAP and SNAP fields of bridge and relay link packets. It can also be used to find the protocol class field 69 of the added header 63 of the switch link packets 55.
- a protocol class lookup is performed by the OR process 31 to determine if the protocol class field 69 in the added header 63 for a frame received from the crossbar switch 12 via line 15 indicates that this protocol class is enabled to be forwarded outbound.
- a hash lookup is used by the IR process 27 (in conjunction with a CAM lookup) to process the 48-bit destination and source fields 61 and 62 of received frames.
- the 48-bit addresses 61 and 62 may be globally unique addresses, i.e., each station may have an address that is unique to that station.
- the address range covers 240 or approximately 3x1014 (300 trillion) unique values, so an address may never need to be duplicated in any foreseeable systems.
- the number of unique addresses needed is usually only a few thousands or at most tens of thousands.
- a table of all of the addresses being used in a network at a given configuration only contains, for example, a maximum of 64K or 216, entries, which would use merely a 16-bit address. For this reason, the 48-bit globally-unique address 61 or 62 is hashed, producing a 16-bit locally-unique address.
- An incoming address field 85 as seen in Figure 8 is subjected to a hash function 86 to produce another 48-bit value 87, then a 16-bit part 88 of this 48-bit value 87 (the least significant 16-bit field) is used to index into a 64K-entry table in memory 21, this being referred to as the hash table 89.
- Each word of the memory 21 is 56-bits wide, so a word can contain three of these hash entries, in three "hash buckets" 90 for each word 91, as seen in Figure 6.
- the 16-bit index 88 is used to select one of the 22K words 91 in the hash table 89 and one of the three hash buckets 90 at this index.
- Each bucket 90 is an 18-bit field containing a 3-bit value 92 indicating the bucket size, one to seven entries, and a 15-bit field 93 acting as a translation table pointer.
- the 16-bit input 88 indexes to a word 91 depending upon its lower order bits and one-of-three buckets 90 in a word 91 depending upon its higher ordered bits, indexed for one-of-22K selection of the word 91 in the table.
- the translation table pointer 93 returned by the hash bucket 90 in the hash table 89 is used to select a breadth-first balanced binary tree as illustrated in Figure 7.
- the trees are stored in a translation table 94 in memory 21, and each tree has between one and seven entries, as indicated by the size field 92.
- the binary tree cannot cross a block boundary in the translation table 94 in memory 21.
- the ordering of entries 96 in a breadth-first balanced binary tree for various table sizes is illustrated in Figure 7.
- Each entry 96 contains 32-bit hash remainder field 97 that is left after using the low-order 16-bit value 88 from the hashed 48-bit address to store an address.
- the IR process fetches the first entry 96, and the 32-bit value 97 in this entry is compared to the upper 32-bit value 97 of the incoming hashed address 87 (from the packet being evaluated). If the two values match, the remaining fields of the entry 96 in the translation table 94 provide the IR process 27 with the information it needs for processing that field of the packet.
- the IR process will continue traversing the binary tree by selecting the next entry as a function of whether the has remainder is less than or greater than the current entry 96.
- the hash remainders 97 are compared, and if the incoming value 97 is less than the stored value 97 the left branch 98 is picked, while if greater than the right branch 99 is picked.
- the tree traversal will continue until a match is found until a match is found or the tree is exhausted. For each hash lookup and tree traversal, up to four memory requests to external memory 21 will be made by the IR process 27.
- One memory request is required to obtain the hash bucket 90, and then up to three more memory requests are needed to traverse the binary tree of Figure 7 (e.g., D - B - C of the 7-entry tree).
- the arbiter of the PM process 35 provides priority service for memory requests associated with this search process in the IR process 27, and will allocate up to every other memory cycle for the IR lookup during packet reception.
- the address lookup procedure used by the IR process 27, as just described, is also illustrated in Figure 8.
- the 48-bit destination address 61 from an incoming packet is simultaneously subjected to the hash function 86 and a CAM match; if a CAM match is found in CAM 23, an index into the translation table 94 is immediately generated as indicated by the line 100.
- the 16-bit field 88 of the hashed address 87 is used to index into the hash table 89 to select a hash bucket 90, and this selected hash bucket contains a pointer 93 into the translation table 94.
- the binary tree found in the translation table 94 will have a size indicated by the 3-bit field 92.
- Each entry 96 in the tree has a 32-bit remainder field 97 which is compared at comparator 101 with the 32-bit remainder in the hashed address 87 to either find a match or progress through the tree from a maximum of three fetches.
- the hash function 86 When the hash function 86 is implemented to build the hash table 89 and translation table 94, as upon initialization of a network and whenever the network is reconfigured by adding stations or bridges, there is a small but finite probability that more than seven addresses will hash to the same bucket. If this occurs, the address producing the collision in trying to load the table will be stored in the CAM 23. Perhaps thirty-two or so of these collision addresses can be stored in the 256-entry CAM 23 without degrading its other functions. Thus, since every address is compared with the CAM entries anyway (to filter for multicast messages, SNAP filtering, etc.), and this compare in the CAM is done in parallel with the hash function, the CAM compare is without cost in time or new circuitry.
- one way of avoiding the consequences of having to rebuild the hash table 89 is to generate two hash tables in memory 21 using two different hash functions, so if the one being used generates a collision (more than seven in a hash bucket), processing switches to the alternate hash table where a collision is very unlikely; this requires extra size for memory 21, however.
- the availability of the CAM lookup for instances where there are a few collisions in loading the hash buckets has the advantage of not imposing any significant burden in time or in memory usage.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US07/965,651 US5390173A (en) | 1992-10-22 | 1992-10-22 | Packet format in hub for packet data communications system |
US965651 | 1992-10-22 |
Publications (2)
Publication Number | Publication Date |
---|---|
EP0594199A1 true EP0594199A1 (de) | 1994-04-27 |
EP0594199B1 EP0594199B1 (de) | 1999-07-07 |
Family
ID=25510280
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP93117159A Expired - Lifetime EP0594199B1 (de) | 1992-10-22 | 1993-10-22 | Paketformat in Knotenpunkt für ein Datenübertragungssystem |
Country Status (3)
Country | Link |
---|---|
US (1) | US5390173A (de) |
EP (1) | EP0594199B1 (de) |
DE (1) | DE69325557T2 (de) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB2372679A (en) * | 2001-02-27 | 2002-08-28 | At & T Lab Cambridge Ltd | Network Bridge and Network |
US7043548B2 (en) | 2000-12-22 | 2006-05-09 | Nokia Corporation | Download status indicators in wireless short range devices |
US7640350B2 (en) | 2000-12-22 | 2009-12-29 | Nokia Corporation | Transferring objects within an ongoing file transfer operation |
Families Citing this family (303)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5617547A (en) * | 1991-03-29 | 1997-04-01 | International Business Machines Corporation | Switch network extension of bus architecture |
US5664107A (en) * | 1992-10-13 | 1997-09-02 | Bay Networks, Inc. | Method for providing for automatic topology discovery in an ATM network or the like |
US5694547A (en) * | 1992-10-13 | 1997-12-02 | Bay Networks, Inc. | System for registration of clients in an ATM network providing for communication of client registration messages to a central manager |
ATE171325T1 (de) * | 1993-03-20 | 1998-10-15 | Ibm | Verfahren und vorrichtung zur herausarbeitung der vermittlungsinformation aus dem kopfteil eines protokolls |
DE69329709D1 (de) * | 1993-04-29 | 2001-01-04 | Ibm | Verfahren und Gerät für Mehrfachübertragung von Daten in einem Kommunikationssystem |
JPH0779233A (ja) * | 1993-06-29 | 1995-03-20 | Synoptics Commun Inc | トポロジを確定する装置及びトポロジ情報を通信する方法及び装置 |
FR2707775B1 (fr) * | 1993-07-12 | 1996-04-12 | Duret Chrsitian | Procédé et dispositif d'analyse d'informations contenues dans des structures de données. |
JPH0738596A (ja) * | 1993-07-16 | 1995-02-07 | Toshiba Corp | ネットワーク間接続装置 |
US5708659A (en) * | 1993-10-20 | 1998-01-13 | Lsi Logic Corporation | Method for hashing in a packet network switching system |
JPH07147592A (ja) * | 1993-11-24 | 1995-06-06 | Fujitsu Ltd | 輻輳制御方法、この方法を用いたターミナルアダプタ及びこのターミナルアダプタを有する通信システム |
EP0675616A3 (de) * | 1994-03-04 | 1995-11-29 | At & T Corp | Lokales Netz. |
US5526344A (en) * | 1994-04-15 | 1996-06-11 | Dsc Communications Corporation | Multi-service switch for a telecommunications network |
US5634004A (en) * | 1994-05-16 | 1997-05-27 | Network Programs, Inc. | Directly programmable distribution element |
JP3224963B2 (ja) * | 1994-08-31 | 2001-11-05 | 株式会社東芝 | ネットワーク接続装置及びパケット転送方法 |
JPH08223195A (ja) * | 1994-11-22 | 1996-08-30 | At & T Corp | ポート数の拡張が可能なローカル・エリア・ハブ・ネットワーク及びそのポート数拡張方法 |
ZA959722B (en) * | 1994-12-19 | 1996-05-31 | Alcatel Nv | Traffic management and congestion control for packet-based networks |
US6256313B1 (en) * | 1995-01-11 | 2001-07-03 | Sony Corporation | Triplet architecture in a multi-port bridge for a local area network |
GB9510932D0 (en) * | 1995-05-31 | 1995-07-26 | 3Com Ireland | Adjustable fifo-based memory scheme |
US5682512A (en) * | 1995-06-30 | 1997-10-28 | Intel Corporation | Use of deferred bus access for address translation in a shared memory clustered computer system |
US5651002A (en) * | 1995-07-12 | 1997-07-22 | 3Com Corporation | Internetworking device with enhanced packet header translation and memory |
US5856974A (en) * | 1996-02-13 | 1999-01-05 | Novell, Inc. | Internetwork address mapping gateway |
US5781545A (en) * | 1996-05-22 | 1998-07-14 | Harris Corporation | Packet source exclusion method |
US5991854A (en) * | 1996-07-01 | 1999-11-23 | Sun Microsystems, Inc. | Circuit and method for address translation, using update and flush control circuits |
US7088726B1 (en) * | 1996-07-04 | 2006-08-08 | Hitachi, Ltd. | Translator for IP networks, network system using the translator, and IP network coupling method therefor |
US5940394A (en) | 1996-08-08 | 1999-08-17 | At&T Corp | Transferring messages in networks made up of subnetworks with different namespaces |
US5802054A (en) * | 1996-08-15 | 1998-09-01 | 3Com Corporation | Atomic network switch with integrated circuit switch nodes |
US5857080A (en) * | 1996-09-10 | 1999-01-05 | Lsi Logic Corporation | Apparatus and method for address translation in bus bridge devices |
JP3662378B2 (ja) * | 1996-12-17 | 2005-06-22 | 川崎マイクロエレクトロニクス株式会社 | ネットワーク中継器 |
US6101186A (en) * | 1996-12-24 | 2000-08-08 | Lucent Technologies, Inc. | Method and system for organizing data in a relational database |
US5999541A (en) * | 1997-02-28 | 1999-12-07 | 3Com Corporation | Transmission of token-ring packets over ethernet by tunneling |
US6285679B1 (en) * | 1997-08-22 | 2001-09-04 | Avici Systems, Inc. | Methods and apparatus for event-driven routing |
US6370145B1 (en) * | 1997-08-22 | 2002-04-09 | Avici Systems | Internet switch router |
US5974467A (en) * | 1997-08-29 | 1999-10-26 | Extreme Networks | Protocol for communicating data between packet forwarding devices via an intermediate network interconnect device |
US6023471A (en) * | 1997-10-07 | 2000-02-08 | Extreme Networks | Network interconnect device and protocol for communicating data among packet forwarding devices |
US6160809A (en) * | 1997-12-17 | 2000-12-12 | Compaq Computer Corporation | Distributed packet data with centralized snooping and header processing router |
US6266336B1 (en) * | 1998-02-18 | 2001-07-24 | International Business Machines Corporation | Apparatus and method for setting A/C bits in token ring frames for switches |
US6560227B1 (en) | 1998-02-23 | 2003-05-06 | International Business Machines Corporation | LAN frame copy decision for LAN switches |
US6876654B1 (en) | 1998-04-10 | 2005-04-05 | Intel Corporation | Method and apparatus for multiprotocol switching and routing |
US6052368A (en) * | 1998-05-22 | 2000-04-18 | Cabletron Systems, Inc. | Method and apparatus for forwarding variable-length packets between channel-specific packet processors and a crossbar of a multiport switch |
JP4105293B2 (ja) * | 1998-06-30 | 2008-06-25 | 富士通株式会社 | ネットワーク監視システムと監視装置および被監視装置 |
US6876653B2 (en) | 1998-07-08 | 2005-04-05 | Broadcom Corporation | Fast flexible filter processor based architecture for a network device |
US6430188B1 (en) * | 1998-07-08 | 2002-08-06 | Broadcom Corporation | Unified table for L2, L3, L4, switching and filtering |
AU6311299A (en) * | 1998-07-08 | 2000-02-01 | Broadcom Corporation | Network switching architecture with multiple table synchronization, and forwarding of both IP and IPX packets |
US7133400B1 (en) * | 1998-08-07 | 2006-11-07 | Intel Corporation | System and method for filtering data |
US7333484B2 (en) * | 1998-08-07 | 2008-02-19 | Intel Corporation | Services processor having a packet editing unit |
US6574238B1 (en) * | 1998-08-26 | 2003-06-03 | Intel Corporation | Inter-switch link header modification |
US6785278B1 (en) * | 1998-12-10 | 2004-08-31 | International Business Machines Corporation | Methods, systems and computer program products for hashing address values |
US6542961B1 (en) * | 1998-12-22 | 2003-04-01 | Hitachi, Ltd. | Disk storage system including a switch |
US7382736B2 (en) * | 1999-01-12 | 2008-06-03 | Mcdata Corporation | Method for scoring queued frames for selective transmission through a switch |
US6109290A (en) * | 1999-01-25 | 2000-08-29 | Sabatinelli; Arthur A. | Fuel dispensing system |
US7120117B1 (en) | 2000-08-29 | 2006-10-10 | Broadcom Corporation | Starvation free flow control in a shared memory switching device |
US6850521B1 (en) * | 1999-03-17 | 2005-02-01 | Broadcom Corporation | Network switch |
US7643481B2 (en) | 1999-03-17 | 2010-01-05 | Broadcom Corporation | Network switch having a programmable counter |
US7031302B1 (en) | 1999-05-21 | 2006-04-18 | Broadcom Corporation | High-speed stats gathering in a network switch |
WO2000072533A1 (en) * | 1999-05-21 | 2000-11-30 | Broadcom Corporation | Stacked network switch configuration |
EP1181791B1 (de) * | 1999-05-24 | 2009-12-02 | Broadcom Corporation | Vorrichtung zur verteilung der auslastung über eine leitungsgruppe |
JP4110671B2 (ja) * | 1999-05-27 | 2008-07-02 | 株式会社日立製作所 | データ転送装置 |
US6859454B1 (en) | 1999-06-30 | 2005-02-22 | Broadcom Corporation | Network switch with high-speed serializing/deserializing hazard-free double data rate switching |
US7315552B2 (en) * | 1999-06-30 | 2008-01-01 | Broadcom Corporation | Frame forwarding in a switch fabric |
US6981155B1 (en) * | 1999-07-14 | 2005-12-27 | Symantec Corporation | System and method for computer security |
AU6107600A (en) * | 1999-07-14 | 2001-01-30 | Recourse Technologies, Inc. | System and method for computer security |
US7117532B1 (en) * | 1999-07-14 | 2006-10-03 | Symantec Corporation | System and method for generating fictitious content for a computer |
US6597661B1 (en) * | 1999-08-25 | 2003-07-22 | Watchguard Technologies, Inc. | Network packet classification |
US7203962B1 (en) * | 1999-08-30 | 2007-04-10 | Symantec Corporation | System and method for using timestamps to detect attacks |
AU7053400A (en) | 1999-09-03 | 2001-04-10 | Broadcom Corporation | Apparatus and method for enabling voice over ip support for a network switch |
US6578086B1 (en) | 1999-09-27 | 2003-06-10 | Nortel Networks Limited | Dynamically managing the topology of a data network |
US7131001B1 (en) | 1999-10-29 | 2006-10-31 | Broadcom Corporation | Apparatus and method for secure filed upgradability with hard wired public key |
US7143294B1 (en) | 1999-10-29 | 2006-11-28 | Broadcom Corporation | Apparatus and method for secure field upgradability with unpredictable ciphertext |
US7539134B1 (en) | 1999-11-16 | 2009-05-26 | Broadcom Corporation | High speed flow control methodology |
WO2001037484A2 (en) * | 1999-11-16 | 2001-05-25 | Broadcom Corporation | Serializing data using hazard-free multilevel glitchless multiplexing |
DE60031712T2 (de) * | 1999-11-18 | 2007-09-06 | Broadcom Corp., Irvine | Tabellen-nachschlage-mechanismus zur adressauflösung in einer paket-netzwerkvermittlung |
DE60010328T2 (de) | 1999-12-07 | 2005-05-04 | Broadcom Corp., Irvine | Spiegelung in einer netzwerkvermittlungsstapelanordnung |
US6665297B1 (en) * | 1999-12-09 | 2003-12-16 | Mayan Networks Corporation | Network routing table |
US7324514B1 (en) * | 2000-01-14 | 2008-01-29 | Cisco Technology, Inc. | Implementing access control lists using a balanced hash table of access control list binary comparison trees |
US7009973B2 (en) * | 2000-02-28 | 2006-03-07 | Broadcom Corporation | Switch using a segmented ring |
US6678678B2 (en) | 2000-03-09 | 2004-01-13 | Braodcom Corporation | Method and apparatus for high speed table search |
US6310880B1 (en) * | 2000-03-17 | 2001-10-30 | Silicon Aquarius, Inc. | Content addressable memory cells and systems and devices using the same |
US6895004B1 (en) * | 2000-04-17 | 2005-05-17 | Alcatel | Internal use only addresses |
US7103053B2 (en) * | 2000-05-03 | 2006-09-05 | Broadcom Corporation | Gigabit switch on chip architecture |
US6826561B2 (en) * | 2000-05-22 | 2004-11-30 | Broadcom Corporation | Method and apparatus for performing a binary search on an expanded tree |
AU2001263424A1 (en) * | 2000-05-31 | 2001-12-11 | Cygnal Integrated Products, Inc. | Priority cross-bar decoder |
EP1162788B1 (de) * | 2000-06-09 | 2012-11-21 | Broadcom Corporation | "Trunking" und "Mirroring" über "stacked gigabit" Vermittlungsstellen |
DE60126533T2 (de) | 2000-06-19 | 2007-11-22 | Broadcom Corp., Irvine | Vermittlungsstelle mit einer Speicherverwaltungeinheit zur Verbesserung der Flusssteurung |
US7126947B2 (en) * | 2000-06-23 | 2006-10-24 | Broadcom Corporation | Switch having external address resolution interface |
US7111163B1 (en) | 2000-07-10 | 2006-09-19 | Alterwan, Inc. | Wide area network using internet with quality of service |
US6999455B2 (en) * | 2000-07-25 | 2006-02-14 | Broadcom Corporation | Hardware assist for address learning |
US7227862B2 (en) * | 2000-09-20 | 2007-06-05 | Broadcom Corporation | Network switch having port blocking capability |
AU2001296628A1 (en) * | 2000-09-27 | 2002-04-08 | Hrl Laboratories, Llc | Method and apparatus for providing directed communications through a networked array of nodes |
US6851000B2 (en) | 2000-10-03 | 2005-02-01 | Broadcom Corporation | Switch having flow control management |
US6988177B2 (en) * | 2000-10-03 | 2006-01-17 | Broadcom Corporation | Switch memory management using a linked list structure |
US7120155B2 (en) * | 2000-10-03 | 2006-10-10 | Broadcom Corporation | Switch having virtual shared memory |
US7020166B2 (en) * | 2000-10-03 | 2006-03-28 | Broadcom Corporation | Switch transferring data using data encapsulation and decapsulation |
US7420977B2 (en) * | 2000-10-03 | 2008-09-02 | Broadcom Corporation | Method and apparatus of inter-chip bus shared by message passing and memory access |
US7274705B2 (en) | 2000-10-03 | 2007-09-25 | Broadcom Corporation | Method and apparatus for reducing clock speed and power consumption |
US8149048B1 (en) | 2000-10-26 | 2012-04-03 | Cypress Semiconductor Corporation | Apparatus and method for programmable power management in a programmable analog circuit block |
US8103496B1 (en) | 2000-10-26 | 2012-01-24 | Cypress Semicondutor Corporation | Breakpoint control in an in-circuit emulation system |
US6724220B1 (en) | 2000-10-26 | 2004-04-20 | Cyress Semiconductor Corporation | Programmable microcontroller architecture (mixed analog/digital) |
US8160864B1 (en) | 2000-10-26 | 2012-04-17 | Cypress Semiconductor Corporation | In-circuit emulator and pod synchronized boot |
US8176296B2 (en) | 2000-10-26 | 2012-05-08 | Cypress Semiconductor Corporation | Programmable microcontroller architecture |
US7035255B2 (en) * | 2000-11-14 | 2006-04-25 | Broadcom Corporation | Linked network switch configuration |
US7035286B2 (en) * | 2000-11-14 | 2006-04-25 | Broadcom Corporation | Linked network switch configuration |
US7424012B2 (en) * | 2000-11-14 | 2008-09-09 | Broadcom Corporation | Linked network switch configuration |
US6850542B2 (en) | 2000-11-14 | 2005-02-01 | Broadcom Corporation | Linked network switch configuration |
US7236490B2 (en) | 2000-11-17 | 2007-06-26 | Foundry Networks, Inc. | Backplane interface adapter |
US7356030B2 (en) * | 2000-11-17 | 2008-04-08 | Foundry Networks, Inc. | Network switch cross point |
US6735218B2 (en) * | 2000-11-17 | 2004-05-11 | Foundry Networks, Inc. | Method and system for encoding wide striped cells |
US7596139B2 (en) | 2000-11-17 | 2009-09-29 | Foundry Networks, Inc. | Backplane interface adapter with error control and redundant fabric |
US7002980B1 (en) * | 2000-12-19 | 2006-02-21 | Chiaro Networks, Ltd. | System and method for router queue and congestion management |
SE0004736D0 (sv) * | 2000-12-20 | 2000-12-20 | Ericsson Telefon Ab L M | Mapping system and method |
US6965945B2 (en) | 2001-03-07 | 2005-11-15 | Broadcom Corporation | System and method for slot based ARL table learning and concurrent table search using range address insertion blocking |
US6993037B2 (en) * | 2001-03-21 | 2006-01-31 | International Business Machines Corporation | System and method for virtual private network network address translation propagation over nested connections with coincident local endpoints |
US7120896B2 (en) * | 2001-10-31 | 2006-10-10 | Vitria Technology, Inc. | Integrated business process modeling environment and models created thereby |
US7388872B2 (en) * | 2001-04-06 | 2008-06-17 | Montgomery Jr Charles D | Dynamic communication channel allocation method and system |
US7206283B2 (en) * | 2001-05-15 | 2007-04-17 | Foundry Networks, Inc. | High-performance network switch |
US7133405B2 (en) * | 2001-08-30 | 2006-11-07 | International Business Machines Corporation | IP datagram over multiple queue pairs |
US6996663B1 (en) * | 2001-09-12 | 2006-02-07 | Cisco Technology, Inc. | Method and apparatus for performing address translation using a CAM |
US7155537B1 (en) * | 2001-09-27 | 2006-12-26 | Lsi Logic Corporation | Infiniband isolation bridge merged with architecture of an infiniband translation bridge |
US7355970B2 (en) * | 2001-10-05 | 2008-04-08 | Broadcom Corporation | Method and apparatus for enabling access on a network switch |
US6785760B2 (en) | 2001-10-19 | 2004-08-31 | International Business Machines Corporation | Performance of a PCI-X to infiniband bridge |
US8325716B2 (en) * | 2001-10-22 | 2012-12-04 | Broadcom Corporation | Data path optimization algorithm |
US7406674B1 (en) | 2001-10-24 | 2008-07-29 | Cypress Semiconductor Corporation | Method and apparatus for generating microcontroller configuration information |
US8078970B1 (en) | 2001-11-09 | 2011-12-13 | Cypress Semiconductor Corporation | Graphical user interface with user-selectable list-box |
US8042093B1 (en) | 2001-11-15 | 2011-10-18 | Cypress Semiconductor Corporation | System providing automatic source code generation for personalization and parameterization of user modules |
US8069405B1 (en) | 2001-11-19 | 2011-11-29 | Cypress Semiconductor Corporation | User interface for efficiently browsing an electronic document using data-driven tabs |
US6971004B1 (en) | 2001-11-19 | 2005-11-29 | Cypress Semiconductor Corp. | System and method of dynamically reconfiguring a programmable integrated circuit |
US7844437B1 (en) * | 2001-11-19 | 2010-11-30 | Cypress Semiconductor Corporation | System and method for performing next placements and pruning of disallowed placements for programming an integrated circuit |
US7194008B2 (en) * | 2002-03-15 | 2007-03-20 | Broadcom Corporation | Method and apparatus for parsing data streams |
US7274698B2 (en) * | 2002-03-15 | 2007-09-25 | Broadcom Corporation | Multilevel parser for conditional flow detection in a network device |
US8103497B1 (en) | 2002-03-28 | 2012-01-24 | Cypress Semiconductor Corporation | External interface for event architecture |
US7649885B1 (en) | 2002-05-06 | 2010-01-19 | Foundry Networks, Inc. | Network routing system for enhanced efficiency and monitoring capability |
US7187687B1 (en) * | 2002-05-06 | 2007-03-06 | Foundry Networks, Inc. | Pipeline method and system for switching packets |
US20120155466A1 (en) * | 2002-05-06 | 2012-06-21 | Ian Edward Davis | Method and apparatus for efficiently processing data packets in a computer network |
US20090279558A1 (en) * | 2002-05-06 | 2009-11-12 | Ian Edward Davis | Network routing apparatus for enhanced efficiency and monitoring capability |
US7468975B1 (en) * | 2002-05-06 | 2008-12-23 | Foundry Networks, Inc. | Flexible method for processing data packets in a network routing system for enhanced efficiency and monitoring capability |
US7266117B1 (en) * | 2002-05-06 | 2007-09-04 | Foundry Networks, Inc. | System architecture for very fast ethernet blade |
US7274690B1 (en) * | 2002-05-09 | 2007-09-25 | Silicon Image, Inc. | Age selection switching scheme for data traffic in a crossbar switch |
US7519066B1 (en) | 2002-05-09 | 2009-04-14 | Silicon Image, Inc. | Method for switching data in a crossbar switch |
US7116664B2 (en) * | 2002-05-13 | 2006-10-03 | International Business Machines Corporation | Lookups by collisionless direct tables and CAMs |
US7230929B2 (en) * | 2002-07-22 | 2007-06-12 | Qlogic, Corporation | Method and system for dynamically assigning domain identification in a multi-module fibre channel switch |
US7154886B2 (en) * | 2002-07-22 | 2006-12-26 | Qlogic Corporation | Method and system for primary blade selection in a multi-module fiber channel switch |
US7397768B1 (en) | 2002-09-11 | 2008-07-08 | Qlogic, Corporation | Zone management in a multi-module fibre channel switch |
EP1404053A1 (de) * | 2002-09-25 | 2004-03-31 | Thomson Multimedia Broadband Belgium | Verfahren zur Leitweglenkung von Datenpaketen, und Vorrichtungen zur Implementierung dieses Verfahrens |
US6886141B1 (en) * | 2002-10-07 | 2005-04-26 | Qlogic Corporation | Method and system for reducing congestion in computer networks |
US7461167B1 (en) | 2002-11-22 | 2008-12-02 | Silicon Image, Inc. | Method for multicast service in a crossbar switch |
US7505422B1 (en) * | 2002-11-22 | 2009-03-17 | Silicon Image, Inc. | Preference programmable first-one detector and quadrature based random grant generator |
US7352764B1 (en) | 2003-05-08 | 2008-04-01 | Silicon Image, Inc. | Content addressable merged queue architecture for switching data |
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 |
US7463646B2 (en) * | 2003-07-16 | 2008-12-09 | Qlogic Corporation | Method and system for fibre channel arbitrated loop acceleration |
US7471635B2 (en) * | 2003-07-16 | 2008-12-30 | Qlogic, Corporation | Method and apparatus for test pattern generation |
US7620059B2 (en) * | 2003-07-16 | 2009-11-17 | Qlogic, Corporation | Method and apparatus for accelerating receive-modify-send frames in a fibre channel network |
US7453802B2 (en) * | 2003-07-16 | 2008-11-18 | Qlogic, Corporation | Method and apparatus for detecting and removing orphaned primitives in a fibre channel network |
US7792115B2 (en) * | 2003-07-21 | 2010-09-07 | Qlogic, Corporation | Method and system for routing and filtering network data packets in fibre channel systems |
US7420982B2 (en) * | 2003-07-21 | 2008-09-02 | Qlogic, Corporation | Method and system for keeping a fibre channel arbitrated loop open during frame gaps |
US7522529B2 (en) * | 2003-07-21 | 2009-04-21 | Qlogic, Corporation | Method and system for detecting congestion and over subscription in a fibre channel network |
US7583597B2 (en) * | 2003-07-21 | 2009-09-01 | Qlogic Corporation | Method and system for improving bandwidth and reducing idles in fibre channel switches |
US7525983B2 (en) | 2003-07-21 | 2009-04-28 | Qlogic, Corporation | Method and system for selecting virtual lanes in fibre channel switches |
US7430175B2 (en) * | 2003-07-21 | 2008-09-30 | Qlogic, Corporation | Method and system for managing traffic in fibre channel systems |
US7646767B2 (en) | 2003-07-21 | 2010-01-12 | Qlogic, Corporation | Method and system for programmable data dependant network routing |
US7406092B2 (en) * | 2003-07-21 | 2008-07-29 | Qlogic, Corporation | Programmable pseudo virtual lanes for fibre channel systems |
US7447224B2 (en) * | 2003-07-21 | 2008-11-04 | Qlogic, Corporation | Method and system for routing fibre channel frames |
US7558281B2 (en) * | 2003-07-21 | 2009-07-07 | Qlogic, Corporation | Method and system for configuring fibre channel ports |
US7573909B2 (en) * | 2003-07-21 | 2009-08-11 | Qlogic, Corporation | Method and system for programmable data dependant network routing |
US7522522B2 (en) * | 2003-07-21 | 2009-04-21 | Qlogic, Corporation | Method and system for reducing latency and congestion in fibre channel switches |
US7684401B2 (en) * | 2003-07-21 | 2010-03-23 | Qlogic, Corporation | Method and system for using extended fabric features with fibre channel switch elements |
US7477655B2 (en) * | 2003-07-21 | 2009-01-13 | Qlogic, Corporation | Method and system for power control of fibre channel switches |
US7630384B2 (en) * | 2003-07-21 | 2009-12-08 | Qlogic, Corporation | Method and system for distributing credit in fibre channel systems |
US7580354B2 (en) * | 2003-07-21 | 2009-08-25 | Qlogic, Corporation | Multi-speed cut through operation in fibre channel switches |
US7894348B2 (en) * | 2003-07-21 | 2011-02-22 | Qlogic, Corporation | Method and system for congestion control in a fibre channel switch |
US7512067B2 (en) * | 2003-07-21 | 2009-03-31 | Qlogic, Corporation | Method and system for congestion control based on optimum bandwidth allocation in a fibre channel switch |
US7466700B2 (en) * | 2003-07-21 | 2008-12-16 | Qlogic, Corporation | LUN based hard zoning in fibre channel switches |
US7664946B2 (en) * | 2003-07-28 | 2010-02-16 | Qcom Tv Partners | System and method of guaranteed anonymity of cable television viewership behavior |
US7397796B1 (en) * | 2003-08-21 | 2008-07-08 | Smiljanic Aleksandra | Load balancing algorithms in non-blocking multistage packet switches |
US7349436B2 (en) | 2003-09-30 | 2008-03-25 | Intel Corporation | Systems and methods for high-throughput wideband wireless local area network communications |
US7185172B1 (en) * | 2003-10-31 | 2007-02-27 | Integrated Device Technology, Inc. | CAM-based search engine devices having index translation capability |
US7581249B2 (en) * | 2003-11-14 | 2009-08-25 | Enterasys Networks, Inc. | Distributed intrusion response system |
US7480293B2 (en) * | 2004-02-05 | 2009-01-20 | Qlogic, Corporation | Method and system for preventing deadlock in fibre channel fabrics using frame priorities |
US7564789B2 (en) * | 2004-02-05 | 2009-07-21 | Qlogic, Corporation | Method and system for reducing deadlock in fibre channel fabrics using virtual lanes |
US7295049B1 (en) | 2004-03-25 | 2007-11-13 | Cypress Semiconductor Corporation | Method and circuit for rapid alignment of signals |
US7817659B2 (en) | 2004-03-26 | 2010-10-19 | Foundry Networks, Llc | Method and apparatus for aggregating input data streams |
US7930377B2 (en) * | 2004-04-23 | 2011-04-19 | Qlogic, Corporation | Method and system for using boot servers in networks |
US7340167B2 (en) | 2004-04-23 | 2008-03-04 | Qlogic, Corporation | Fibre channel transparent switch for mixed switch fabrics |
US8730961B1 (en) | 2004-04-26 | 2014-05-20 | Foundry Networks, Llc | System and method for optimizing router lookup |
US20050289613A1 (en) * | 2004-06-18 | 2005-12-29 | Honeywell International Inc. | Control architecture for audio/video (A/V) systems |
US7593997B2 (en) | 2004-10-01 | 2009-09-22 | Qlogic, Corporation | Method and system for LUN remapping in fibre channel networks |
US7411958B2 (en) * | 2004-10-01 | 2008-08-12 | Qlogic, Corporation | Method and system for transferring data directly between storage devices in a storage area network |
US8295299B2 (en) | 2004-10-01 | 2012-10-23 | Qlogic, Corporation | High speed fibre channel switch element |
US7657703B1 (en) | 2004-10-29 | 2010-02-02 | Foundry Networks, Inc. | Double density content addressable memory (CAM) lookup scheme |
US7519058B2 (en) * | 2005-01-18 | 2009-04-14 | Qlogic, Corporation | Address translation in fibre channel switches |
US7332976B1 (en) * | 2005-02-04 | 2008-02-19 | Cypress Semiconductor Corporation | Poly-phase frequency synthesis oscillator |
US20060187828A1 (en) * | 2005-02-18 | 2006-08-24 | Broadcom Corporation | Packet identifier for use in a network device |
US7400183B1 (en) | 2005-05-05 | 2008-07-15 | Cypress Semiconductor Corporation | Voltage controlled oscillator delay cell and method |
KR101213932B1 (ko) * | 2005-05-17 | 2012-12-18 | 삼성전자주식회사 | 이종망 환경에서 종단간 서비스 품질 연동장치 및 그 방법 |
US7370048B2 (en) * | 2005-05-27 | 2008-05-06 | International Business Machines Corporation | File storage method and apparatus |
US8448162B2 (en) | 2005-12-28 | 2013-05-21 | Foundry Networks, Llc | Hitless software upgrades |
US9098641B1 (en) * | 2006-01-30 | 2015-08-04 | Cypress Semiconductor Corporation | Configurable bus |
US20070198420A1 (en) * | 2006-02-03 | 2007-08-23 | Leonid Goldstein | Method and a system for outbound content security in computer networks |
US8067948B2 (en) * | 2006-03-27 | 2011-11-29 | Cypress Semiconductor Corporation | Input/output multiplexer bus |
US7952997B2 (en) * | 2006-05-18 | 2011-05-31 | Mcdata Corporation | Congestion management groups |
US20070288690A1 (en) * | 2006-06-13 | 2007-12-13 | Foundry Networks, Inc. | High bandwidth, high capacity look-up table implementation in dynamic random access memory |
US7903654B2 (en) * | 2006-08-22 | 2011-03-08 | Foundry Networks, Llc | System and method for ECMP load sharing |
US20080095143A1 (en) * | 2006-10-19 | 2008-04-24 | Research In Motion Limited | System and method for providing debug information in session initiation protocol sessions |
JP4701152B2 (ja) * | 2006-10-20 | 2011-06-15 | 富士通株式会社 | データ中継装置、データ中継方法およびデータ中継プログラム |
US8238255B2 (en) * | 2006-11-22 | 2012-08-07 | Foundry Networks, Llc | Recovering from failures without impact on data traffic in a shared bus architecture |
US20080159260A1 (en) * | 2006-12-15 | 2008-07-03 | Brocade Communications Systems, Inc. | Fibre channel over ethernet frame |
US20080181243A1 (en) * | 2006-12-15 | 2008-07-31 | Brocade Communications Systems, Inc. | Ethernet forwarding in high performance fabrics |
US20080159277A1 (en) * | 2006-12-15 | 2008-07-03 | Brocade Communications Systems, Inc. | Ethernet over fibre channel |
US20090279441A1 (en) * | 2007-01-11 | 2009-11-12 | Foundry Networks, Inc. | Techniques for transmitting failure detection protocol packets |
US8040266B2 (en) * | 2007-04-17 | 2011-10-18 | Cypress Semiconductor Corporation | Programmable sigma-delta analog-to-digital converter |
US8026739B2 (en) | 2007-04-17 | 2011-09-27 | Cypress Semiconductor Corporation | System level interconnect with programmable switching |
US8130025B2 (en) | 2007-04-17 | 2012-03-06 | Cypress Semiconductor Corporation | Numerical band gap |
US9720805B1 (en) | 2007-04-25 | 2017-08-01 | Cypress Semiconductor Corporation | System and method for controlling a target device |
US8271859B2 (en) * | 2007-07-18 | 2012-09-18 | Foundry Networks Llc | Segmented CRC design in high speed networks |
US8037399B2 (en) * | 2007-07-18 | 2011-10-11 | Foundry Networks, Llc | Techniques for segmented CRC design in high speed networks |
US8049569B1 (en) | 2007-09-05 | 2011-11-01 | Cypress Semiconductor Corporation | Circuit and method for improving the accuracy of a crystal-less oscillator having dual-frequency modes |
US8509236B2 (en) | 2007-09-26 | 2013-08-13 | Foundry Networks, Llc | Techniques for selecting paths and/or trunk ports for forwarding traffic flows |
US8190881B2 (en) | 2007-10-15 | 2012-05-29 | Foundry Networks Llc | Scalable distributed web-based authentication |
US8583780B2 (en) * | 2007-11-20 | 2013-11-12 | Brocade Communications Systems, Inc. | Discovery of duplicate address in a network by reviewing discovery frames received at a port |
US8108454B2 (en) * | 2007-12-17 | 2012-01-31 | Brocade Communications Systems, Inc. | Address assignment in Fibre Channel over Ethernet environments |
US7957396B1 (en) * | 2008-01-29 | 2011-06-07 | Juniper Networks, Inc. | Targeted flow sampling |
US20090296726A1 (en) * | 2008-06-03 | 2009-12-03 | Brocade Communications Systems, Inc. | ACCESS CONTROL LIST MANAGEMENT IN AN FCoE ENVIRONMENT |
JP2010109530A (ja) * | 2008-10-29 | 2010-05-13 | Sony Corp | 無線通信装置および無線通信方法 |
US8285900B2 (en) | 2009-02-17 | 2012-10-09 | The Board Of Regents Of The University Of Texas System | Method and apparatus for congestion-aware routing in a computer interconnection network |
US8848575B2 (en) | 2009-02-23 | 2014-09-30 | Brocade Communications Systems, Inc. | High availability and multipathing for fibre channel over ethernet |
US8665886B2 (en) | 2009-03-26 | 2014-03-04 | Brocade Communications Systems, Inc. | Redundant host connection in a routed network |
US8090901B2 (en) | 2009-05-14 | 2012-01-03 | Brocade Communications Systems, Inc. | TCAM management approach that minimize movements |
US8625427B1 (en) | 2009-09-03 | 2014-01-07 | Brocade Communications Systems, Inc. | Multi-path switching with edge-to-edge flow control |
US8599850B2 (en) | 2009-09-21 | 2013-12-03 | Brocade Communications Systems, Inc. | Provisioning single or multistage networks using ethernet service instances (ESIs) |
US8369335B2 (en) | 2010-03-24 | 2013-02-05 | Brocade Communications Systems, Inc. | Method and system for extending routing domain to non-routing end stations |
US8427958B2 (en) | 2010-04-30 | 2013-04-23 | Brocade Communications Systems, Inc. | Dynamic latency-based rerouting |
US9270486B2 (en) | 2010-06-07 | 2016-02-23 | Brocade Communications Systems, Inc. | Name services for virtual cluster switching |
US9716672B2 (en) | 2010-05-28 | 2017-07-25 | Brocade Communications Systems, Inc. | Distributed configuration management for virtual cluster switching |
US9001824B2 (en) | 2010-05-18 | 2015-04-07 | Brocade Communication Systems, Inc. | Fabric formation for virtual cluster switching |
US9461840B2 (en) | 2010-06-02 | 2016-10-04 | Brocade Communications Systems, Inc. | Port profile management for virtual cluster switching |
US9231890B2 (en) | 2010-06-08 | 2016-01-05 | Brocade Communications Systems, Inc. | Traffic management for virtual cluster switching |
US9769016B2 (en) | 2010-06-07 | 2017-09-19 | Brocade Communications Systems, Inc. | Advanced link tracking for virtual cluster switching |
US8989186B2 (en) | 2010-06-08 | 2015-03-24 | Brocade Communication Systems, Inc. | Virtual port grouping for virtual cluster switching |
US8625616B2 (en) | 2010-05-11 | 2014-01-07 | Brocade Communications Systems, Inc. | Converged network extension |
US8867552B2 (en) | 2010-05-03 | 2014-10-21 | Brocade Communications Systems, Inc. | Virtual cluster switching |
US8885488B2 (en) | 2010-06-02 | 2014-11-11 | Brocade Communication Systems, Inc. | Reachability detection in trill networks |
US8634308B2 (en) | 2010-06-02 | 2014-01-21 | Brocade Communications Systems, Inc. | Path detection in trill networks |
US9608833B2 (en) | 2010-06-08 | 2017-03-28 | Brocade Communications Systems, Inc. | Supporting multiple multicast trees in trill networks |
US8446914B2 (en) | 2010-06-08 | 2013-05-21 | Brocade Communications Systems, Inc. | Method and system for link aggregation across multiple switches |
US9628293B2 (en) | 2010-06-08 | 2017-04-18 | Brocade Communications Systems, Inc. | Network layer multicasting in trill networks |
US9806906B2 (en) | 2010-06-08 | 2017-10-31 | Brocade Communications Systems, Inc. | Flooding packets on a per-virtual-network basis |
US9246703B2 (en) | 2010-06-08 | 2016-01-26 | Brocade Communications Systems, Inc. | Remote port mirroring |
US9807031B2 (en) | 2010-07-16 | 2017-10-31 | Brocade Communications Systems, Inc. | System and method for network configuration |
US9154394B2 (en) | 2010-09-28 | 2015-10-06 | Brocade Communications Systems, Inc. | Dynamic latency-based rerouting |
US10558705B2 (en) * | 2010-10-20 | 2020-02-11 | Microsoft Technology Licensing, Llc | Low RAM space, high-throughput persistent key-value store using secondary memory |
US8780896B2 (en) * | 2010-12-29 | 2014-07-15 | Juniper Networks, Inc. | Methods and apparatus for validation of equal cost multi path (ECMP) paths in a switch fabric system |
US8798077B2 (en) | 2010-12-29 | 2014-08-05 | Juniper Networks, Inc. | Methods and apparatus for standard protocol validation mechanisms deployed over a switch fabric system |
US9270572B2 (en) | 2011-05-02 | 2016-02-23 | Brocade Communications Systems Inc. | Layer-3 support in TRILL networks |
US9401861B2 (en) | 2011-06-28 | 2016-07-26 | Brocade Communications Systems, Inc. | Scalable MAC address distribution in an Ethernet fabric switch |
US9407533B2 (en) | 2011-06-28 | 2016-08-02 | Brocade Communications Systems, Inc. | Multicast in a trill network |
US8948056B2 (en) | 2011-06-28 | 2015-02-03 | Brocade Communication Systems, Inc. | Spanning-tree based loop detection for an ethernet fabric switch |
US8879549B2 (en) | 2011-06-28 | 2014-11-04 | Brocade Communications Systems, Inc. | Clearing forwarding entries dynamically and ensuring consistency of tables across ethernet fabric switch |
US9007958B2 (en) | 2011-06-29 | 2015-04-14 | Brocade Communication Systems, Inc. | External loop detection for an ethernet fabric switch |
US8885641B2 (en) | 2011-06-30 | 2014-11-11 | Brocade Communication Systems, Inc. | Efficient trill forwarding |
US9736085B2 (en) | 2011-08-29 | 2017-08-15 | Brocade Communications Systems, Inc. | End-to end lossless Ethernet in Ethernet fabric |
US9699117B2 (en) | 2011-11-08 | 2017-07-04 | Brocade Communications Systems, Inc. | Integrated fibre channel support in an ethernet fabric switch |
US9450870B2 (en) | 2011-11-10 | 2016-09-20 | Brocade Communications Systems, Inc. | System and method for flow management in software-defined networks |
US8995272B2 (en) | 2012-01-26 | 2015-03-31 | Brocade Communication Systems, Inc. | Link aggregation in software-defined networks |
US9742693B2 (en) | 2012-02-27 | 2017-08-22 | Brocade Communications Systems, Inc. | Dynamic service insertion in a fabric switch |
US9154416B2 (en) | 2012-03-22 | 2015-10-06 | Brocade Communications Systems, Inc. | Overlay tunnel in a fabric switch |
US9256550B2 (en) * | 2012-03-28 | 2016-02-09 | International Business Machines Corporation | Hybrid address translation |
US9374301B2 (en) | 2012-05-18 | 2016-06-21 | Brocade Communications Systems, Inc. | Network feedback in software-defined networks |
US10277464B2 (en) | 2012-05-22 | 2019-04-30 | Arris Enterprises Llc | Client auto-configuration in a multi-switch link aggregation |
EP2853066B1 (de) | 2012-05-23 | 2017-02-22 | Brocade Communications Systems, Inc. | Layer-3-überlagerungs-gateways |
US9602430B2 (en) | 2012-08-21 | 2017-03-21 | Brocade Communications Systems, Inc. | Global VLANs for fabric switches |
US9401872B2 (en) | 2012-11-16 | 2016-07-26 | Brocade Communications Systems, Inc. | Virtual link aggregations across multiple fabric switches |
US9350680B2 (en) | 2013-01-11 | 2016-05-24 | Brocade Communications Systems, Inc. | Protection switching over a virtual link aggregation |
US9413691B2 (en) | 2013-01-11 | 2016-08-09 | Brocade Communications Systems, Inc. | MAC address synchronization in a fabric switch |
US9548926B2 (en) | 2013-01-11 | 2017-01-17 | Brocade Communications Systems, Inc. | Multicast traffic load balancing over virtual link aggregation |
US9565113B2 (en) | 2013-01-15 | 2017-02-07 | Brocade Communications Systems, Inc. | Adaptive link aggregation and virtual link aggregation |
US9565099B2 (en) | 2013-03-01 | 2017-02-07 | Brocade Communications Systems, Inc. | Spanning tree in fabric switches |
US9401818B2 (en) | 2013-03-15 | 2016-07-26 | Brocade Communications Systems, Inc. | Scalable gateways for a fabric switch |
US9565028B2 (en) | 2013-06-10 | 2017-02-07 | Brocade Communications Systems, Inc. | Ingress switch multicast distribution in a fabric switch |
US9699001B2 (en) | 2013-06-10 | 2017-07-04 | Brocade Communications Systems, Inc. | Scalable and segregated network virtualization |
US9806949B2 (en) | 2013-09-06 | 2017-10-31 | Brocade Communications Systems, Inc. | Transparent interconnection of Ethernet fabric switches |
US9912612B2 (en) | 2013-10-28 | 2018-03-06 | Brocade Communications Systems LLC | Extended ethernet fabric switches |
US9548873B2 (en) | 2014-02-10 | 2017-01-17 | Brocade Communications Systems, Inc. | Virtual extensible LAN tunnel keepalives |
US10581758B2 (en) | 2014-03-19 | 2020-03-03 | Avago Technologies International Sales Pte. Limited | Distributed hot standby links for vLAG |
US10476698B2 (en) | 2014-03-20 | 2019-11-12 | Avago Technologies International Sales Pte. Limited | Redundent virtual link aggregation group |
US10063473B2 (en) | 2014-04-30 | 2018-08-28 | Brocade Communications Systems LLC | Method and system for facilitating switch virtualization in a network of interconnected switches |
US9800471B2 (en) | 2014-05-13 | 2017-10-24 | Brocade Communications Systems, Inc. | Network extension groups of global VLANs in a fabric switch |
US10616108B2 (en) | 2014-07-29 | 2020-04-07 | Avago Technologies International Sales Pte. Limited | Scalable MAC address virtualization |
US9544219B2 (en) | 2014-07-31 | 2017-01-10 | Brocade Communications Systems, Inc. | Global VLAN services |
US9807007B2 (en) | 2014-08-11 | 2017-10-31 | Brocade Communications Systems, Inc. | Progressive MAC address learning |
US9524173B2 (en) | 2014-10-09 | 2016-12-20 | Brocade Communications Systems, Inc. | Fast reboot for a switch |
US9699029B2 (en) | 2014-10-10 | 2017-07-04 | Brocade Communications Systems, Inc. | Distributed configuration management in a switch group |
US9628407B2 (en) | 2014-12-31 | 2017-04-18 | Brocade Communications Systems, Inc. | Multiple software versions in a switch group |
US9626255B2 (en) | 2014-12-31 | 2017-04-18 | Brocade Communications Systems, Inc. | Online restoration of a switch snapshot |
US10003552B2 (en) | 2015-01-05 | 2018-06-19 | Brocade Communications Systems, Llc. | Distributed bidirectional forwarding detection protocol (D-BFD) for cluster of interconnected switches |
US9942097B2 (en) | 2015-01-05 | 2018-04-10 | Brocade Communications Systems LLC | Power management in a network of interconnected switches |
US9807005B2 (en) | 2015-03-17 | 2017-10-31 | Brocade Communications Systems, Inc. | Multi-fabric manager |
US10038592B2 (en) | 2015-03-17 | 2018-07-31 | Brocade Communications Systems LLC | Identifier assignment to a new switch in a switch group |
US10579406B2 (en) | 2015-04-08 | 2020-03-03 | Avago Technologies International Sales Pte. Limited | Dynamic orchestration of overlay tunnels |
US10439929B2 (en) | 2015-07-31 | 2019-10-08 | Avago Technologies International Sales Pte. Limited | Graceful recovery of a multicast-enabled switch |
US10171303B2 (en) | 2015-09-16 | 2019-01-01 | Avago Technologies International Sales Pte. Limited | IP-based interconnection of switches with a logical chassis |
US9912614B2 (en) | 2015-12-07 | 2018-03-06 | Brocade Communications Systems LLC | Interconnection of switches based on hierarchical overlay tunneling |
JP6616230B2 (ja) * | 2016-04-07 | 2019-12-04 | APRESIA Systems株式会社 | ネットワーク装置 |
US10237090B2 (en) | 2016-10-28 | 2019-03-19 | Avago Technologies International Sales Pte. Limited | Rule-based network identifier mapping |
EP3764233A1 (de) * | 2019-07-08 | 2021-01-13 | Continental Teves AG & Co. OHG | Verfahren zur erkennung von fehlern in oder manipulationen von in einer vorrichtung gespeicherten daten oder software |
CN112988653B (zh) * | 2019-12-16 | 2024-04-12 | 广州希姆半导体科技有限公司 | 数据处理电路、装置以及方法 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP0281785A2 (de) * | 1987-03-12 | 1988-09-14 | Hughes LAN Systems, Inc. | Brückensystem zur Verbindung von Netzwerken |
EP0404337A2 (de) * | 1989-06-22 | 1990-12-27 | Digital Equipment Corporation | Lokales Maschennetzwerk hoher Geschwindigkeit |
DE4103888A1 (de) * | 1990-02-09 | 1991-08-14 | Hitachi Ltd | Adressfiltereinheit und -verfahren zum ausfuehren eines adressfilterverfahrens unter einer vielzahl von netzwerken |
EP0473066A1 (de) * | 1990-08-27 | 1992-03-04 | Mitsubishi Denki Kabushiki Kaisha | Verbindungssystem für eine Anzahl von lokalen Netzwerken |
Family Cites Families (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4706081A (en) * | 1984-12-14 | 1987-11-10 | Vitalink Communications Corporation | Method and apparatus for bridging local area networks |
JPH0793634B2 (ja) * | 1986-11-29 | 1995-10-09 | 株式会社東芝 | アドレス変換機能付きバスアダプタ |
US5060228A (en) * | 1988-11-19 | 1991-10-22 | Fujitsu Limited | Bridge communication system |
US5020020A (en) * | 1989-04-07 | 1991-05-28 | Digital Equipment Corporation | Computer interconnect system with transmit-abort function |
US5220562A (en) * | 1989-05-12 | 1993-06-15 | Hitachi, Ltd. | Bridge apparatus and a communication system between networks using the bridge apparatus |
US5115432A (en) * | 1989-12-12 | 1992-05-19 | At&T Bell Laboratories | Communication architecture for high speed networking |
US5121383A (en) * | 1990-11-16 | 1992-06-09 | Bell Communications Research, Inc. | Duration limited statistical multiplexing in packet networks |
-
1992
- 1992-10-22 US US07/965,651 patent/US5390173A/en not_active Expired - Lifetime
-
1993
- 1993-10-22 EP EP93117159A patent/EP0594199B1/de not_active Expired - Lifetime
- 1993-10-22 DE DE69325557T patent/DE69325557T2/de not_active Expired - Lifetime
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP0281785A2 (de) * | 1987-03-12 | 1988-09-14 | Hughes LAN Systems, Inc. | Brückensystem zur Verbindung von Netzwerken |
EP0404337A2 (de) * | 1989-06-22 | 1990-12-27 | Digital Equipment Corporation | Lokales Maschennetzwerk hoher Geschwindigkeit |
DE4103888A1 (de) * | 1990-02-09 | 1991-08-14 | Hitachi Ltd | Adressfiltereinheit und -verfahren zum ausfuehren eines adressfilterverfahrens unter einer vielzahl von netzwerken |
EP0473066A1 (de) * | 1990-08-27 | 1992-03-04 | Mitsubishi Denki Kabushiki Kaisha | Verbindungssystem für eine Anzahl von lokalen Netzwerken |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7043548B2 (en) | 2000-12-22 | 2006-05-09 | Nokia Corporation | Download status indicators in wireless short range devices |
US7640350B2 (en) | 2000-12-22 | 2009-12-29 | Nokia Corporation | Transferring objects within an ongoing file transfer operation |
GB2372679A (en) * | 2001-02-27 | 2002-08-28 | At & T Lab Cambridge Ltd | Network Bridge and Network |
Also Published As
Publication number | Publication date |
---|---|
EP0594199B1 (de) | 1999-07-07 |
DE69325557D1 (de) | 1999-08-12 |
DE69325557T2 (de) | 2000-01-27 |
US5390173A (en) | 1995-02-14 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP0594199B1 (de) | Paketformat in Knotenpunkt für ein Datenübertragungssystem | |
EP0594196B1 (de) | Aufsuchen von Adressen bei Paketübertragung mittels Hashing und eines inhaltsadressierten Speichers | |
US6571291B1 (en) | Apparatus and method for validating and updating an IP checksum in a network switching system | |
AU680931B2 (en) | Network station with multiple network addresses | |
US5764895A (en) | Method and apparatus for directing data packets in a local area network device having a plurality of ports interconnected by a high-speed communication bus | |
US6172980B1 (en) | Multiple protocol support | |
US5604867A (en) | System for transmitting data between bus and network having device comprising first counter for providing transmitting rate and second counter for limiting frames exceeding rate | |
KR100506323B1 (ko) | 네트워크 프로세서를 사용하는 네트워크 스위치 및 그의방법 | |
US7573876B2 (en) | Interconnecting network processors with heterogeneous fabrics | |
US5655140A (en) | Apparatus for translating frames of data transferred between heterogeneous local area networks | |
EP1224773B1 (de) | Verfahren und vorrichtung zur erkennung von datenpaketen in echtzeit in dem anschluss einer netzwerkvermittlungsstelle | |
KR100498824B1 (ko) | Vlsi 네트워크 프로세서 및 방법 | |
US20050226259A1 (en) | Fibre channel switching fabric hub | |
KR20020024332A (ko) | 네트워크 프로세서, 메모리 조직 및 방법 | |
JP2010172011A (ja) | ネットワークスイッチング装置におけるコンテントベースの転送/フィルタリング方法 | |
KR20020024330A (ko) | 네트워크 스위치와 그 콤포넌트 및 동작 방법 | |
US20170052913A1 (en) | Network controller - sideband interface port controller | |
KR20010043460A (ko) | 디지털 통신 프로세서 | |
EP1329073B1 (de) | Verfahren und vorrichtung zur paketklassifikation | |
CA2330014C (en) | Method of mapping fibre channel frames based on control and type header fields | |
US7031325B1 (en) | Method and apparatus for enabling a network device to operate in accordance with multiple protocols | |
US6778547B1 (en) | Method and apparatus for improving throughput of a rules checker logic | |
US6711165B1 (en) | Apparatus and method for storing min terms in network switch port memory for access and compactness | |
US6693906B1 (en) | Apparatus and method for buffer-free evaluation of packet data bytes with multiple min terms | |
US6195334B1 (en) | Apparatus and method for terminating a data transfer in a network switch in response to a detected collision |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): DE FR GB IT |
|
17P | Request for examination filed |
Effective date: 19940627 |
|
17Q | First examination report despatched |
Effective date: 19970630 |
|
GRAG | Despatch of communication of intention to grant |
Free format text: ORIGINAL CODE: EPIDOS AGRA |
|
GRAG | Despatch of communication of intention to grant |
Free format text: ORIGINAL CODE: EPIDOS AGRA |
|
GRAH | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOS IGRA |
|
RAP1 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: CABLETRON SYSTEMS, INC. |
|
GRAH | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOS IGRA |
|
GRAH | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOS IGRA |
|
GRAH | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOS IGRA |
|
GRAA | (expected) grant |
Free format text: ORIGINAL CODE: 0009210 |
|
AK | Designated contracting states |
Kind code of ref document: B1 Designated state(s): DE FR GB IT |
|
REF | Corresponds to: |
Ref document number: 69325557 Country of ref document: DE Date of ref document: 19990812 |
|
ITF | It: translation for a ep patent filed | ||
ET | Fr: translation filed | ||
PLBE | No opposition filed within time limit |
Free format text: ORIGINAL CODE: 0009261 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT |
|
26N | No opposition filed | ||
REG | Reference to a national code |
Ref country code: GB Ref legal event code: IF02 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IT Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES;WARNING: LAPSES OF ITALIAN PATENTS WITH EFFECTIVE DATE BEFORE 2007 MAY HAVE OCCURRED AT ANY TIME BEFORE 2007. THE CORRECT EFFECTIVE DATE MAY BE DIFFERENT FROM THE ONE RECORDED. Effective date: 20051022 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: DE Payment date: 20121029 Year of fee payment: 20 Ref country code: FR Payment date: 20121107 Year of fee payment: 20 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: GB Payment date: 20121025 Year of fee payment: 20 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R071 Ref document number: 69325557 Country of ref document: DE |
|
REG | Reference to a national code |
Ref country code: GB Ref legal event code: PE20 Expiry date: 20131021 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: DE Free format text: LAPSE BECAUSE OF EXPIRATION OF PROTECTION Effective date: 20131023 Ref country code: GB Free format text: LAPSE BECAUSE OF EXPIRATION OF PROTECTION Effective date: 20131021 |