US5610905A - Communication apparatus and methods - Google Patents
Communication apparatus and methods Download PDFInfo
- Publication number
- US5610905A US5610905A US08/358,211 US35821194A US5610905A US 5610905 A US5610905 A US 5610905A US 35821194 A US35821194 A US 35821194A US 5610905 A US5610905 A US 5610905A
- Authority
- US
- United States
- Prior art keywords
- ports
- packet
- packets
- monitoring
- port
- 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.)
- Expired - Lifetime
Links
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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
Definitions
- This invention relates to packet oriented multi-port bridges and routers and, in particular, to the monitoring of packet traffic arriving at the bridges and routers or generated internally.
- Multi-port bridges and routers allow the connection of two or more packet-based networks of possibly different types. Information in such networks is transmitted by means of packets, each containing data and appropriate addressing information.
- the purpose of the bridge or router is to relay packets between network segments (a process called forwarding) so that stations connected to different network segments may communicate.
- An example of a packet-based network protocol is that implemented by the IEEE 802.3 Ethernet standard.
- Monitoring of packet networks can be carried out with monitoring devices such as SnifferTM from Network General of Menlo Park, Calif. or LANalyzerTM from Novell, Inc. of Provo, Utah. These devices are connected to the network medium, such as coaxial cable, and examine each network transmission regardless of the actual destination of the packets.
- network monitors provide the capability of filtering the examined transmission so that only packets with properties of interest to the network manager are captured or displayed.
- Facilities are usually provided to gather statistics, such as error rates, traffic between stations or groups of stations and so forth, as well as the packets themselves. Because of the need to capture and analyze large amounts of data, and the potential complexity of filtering, network monitors are expensive relative to other network components such as stations or bridges.
- a serious limitation of prior-art network monitors is that the monitor must be connected physically to the network segment to be monitored. In a multi-port bridge where several network segments are connected by a bridge, it is only possible to examine one of the attached network segments at a time since the bridge isolates the physical media of the network segments.
- a further limitation is that the network monitor is not able to easily differentiate packets originating on the attached network segment and those originating on other network segments attached to the bridge and forwarded to the monitored network segment, especially if the packets have wrong addresses due to malfunction or sabotage.
- a router moreover, replaces the source address of the packet by the router address, which makes it even more difficult for the network monitor to determine where the packet originated. In particular, it may be difficult or impossible for the monitor to isolate, for example, all the packets originating on a selected network segment.
- Each Sniffer is a network monitor coupled to a processing element that can be controlled over the network. If several network segments attached to a bridge are to be monitored, then one Distributed Sniffer must be attached to each physical network segment. Operation of each Distributed Sniffer can be controlled over the network from a network-attached station using an upper level protocol such as TELNET. With this approach, one station located on any attached network segment can view results obtained from each Distributed Sniffer.
- TELNET upper level protocol
- a Sniffer detecting a packet may be unable to determine the network segment on which the packet originated even if that network segment is connected to another Sniffer which has detected the packet, because the two Sniffers may be unable to determine whether the packet they have detected is the same packet or two different packets.
- each Distributed Sniffer must use some portion of the bandwidth of the monitored network to send information to the monitoring station, and thus the performance of the monitored network is affected.
- monitoring of any or all network segments on a multi-port bridge or router may be carried out from a network segment on one port, referred to as a monitoring port.
- Packets of a selected network segment attached to a port designated as the monitored port are forwarded to their normal destination ports, if any, and also to the monitoring port.
- Monitored ports and monitoring ports may be specified in any number, thus allowing, for example, packet traffic from several ports to be simultaneously monitored at one port.
- a network monitor of conventional design may be connected to the monitoring port and will thus be able to view traffic just as if it were connected directly to a monitored port.
- Port monitoring is enabled, disabled and specified via a supervisory access terminal attached to the bridge or router. Alternately, these supervisory functions are carried out from any network-attached terminal using well-known protocols. Using the supervisory access terminal, the network manager is able to define the type of traffic to be copied to the monitoring port. Several traffic types are allowed, for example, monitoring of all packets incoming to a selected port, all packets forwarded to a selected port or all packets generated within the bridge or router and then transmitted on a selected port. In particular, the packets originating on a selected network segment can be isolated for viewing on the network monitor. Further, the monitoring of traffic forwarded between selected pairs of ports is allowed.
- Forwarding of a packet from a monitored port to a monitoring port does not require the packet to be copied from one place to another in the bridge's internal buffer memory. Instead, an indirect scheme is specified, that allows a packet to be sent to one or more destination ports without moving the packet.
- Internal data structures are defined to support efficient packet forwarding and to define the ports to which a packet should be forwarded under various circumstances. The data structures are intended to promote efficient forwarding and also to support simple and regular modification when a port monitoring command is issued from the supervisory access terminal.
- a further object is to allow selection of the type of packet traffic to be monitored.
- Another object of the invention is to "transmit" a single packet to multiple ports in an efficient manner and without the need to make multiple copies of the packet itself.
- Yet another object of the invention is to promote an efficient way to carry out the forwarding computations.
- FIG. 1 illustrates an example multi-port bridge with six attached network segments
- FIG. 2 depicts the format of a packet in conformance with the Ethernet standard
- FIG. 3 sets out two formats of packet destination address
- FIG. 4 exhibits a Bridging Table related to the example system
- FIG. 5 shows the evaluation of a Custom Filtering Rule
- FIG. 6 is a block diagram of the example bridge
- FIG. 7 depicts shared memory data structures related to packet reception and transmission
- FIG. 8 illustrates the format of a Packet Descriptor
- FIG. 9 illustrates the format of the XMASK
- FIGS. 10A and 10B illustrate the reception of a packet and the transmission of a packet, respectively
- FIG. 11 is a state diagram illustrating the sequencing of Packet Descriptor state
- FIG. 12 illustrates the Forwarding Table for the example bridge
- FIG. 13 illustrates the Broadcast/Multicast Table for the example bridge
- FIG. 14 illustrates the Management Table for the example bridge
- FIG. 15 depicts a Bridging Cache
- FIG. 16 is a flowchart of the forwarding algorithm
- FIGS. 17A and 17B depict the Forwarding Table and Broadcast/Multicast Table, respectively, after modification to support monitoring of incoming packets;
- FIGS. 18A and 18B depict the Forwarding Table and Broadcast/Multicast Table, respectively, after modification to support monitoring of forwarded packets;
- FIG. 19 illustrates the Management Table after modification to support monitoring of generated packets.
- FIGS. 20A and 20B depict the Forwarding Table and Broadcast/Multicast Table, respectively, after modification to support port-pair monitoring.
- the purpose of the bridge to be described below is to connect together multiple packet-based segments of a network, allowing efficient communications between stations on each network segment and also between stations located on different network segments connected to the bridge. It is also possible for stations on network segments not connected to a common bridge to communicate, provided that there is at least one segment-to-segment path between the stations.
- network segments attached to the bridge will employ a packet-based communication protocol based on either Ethernet or FDDI.
- packet-based protocols are possible.
- the details of Ethernet and FDDI protocols are well known and are documented in standards, particularly in IEEE Standard 802.3 for Ethernet and ANSI Standard X3T9.5 for FDDI.
- the following review of packet communications is intended to establish a terminology for further exposition of the preferred embodiment.
- the Ethernet scheme will be used as an example.
- FIG. 1 illustrates an example of a bridge with the port monitoring feature.
- the bridge 1 provides bridging services to six attached network segments 2 via ports 3 numbered 0 through 5.
- Item 2 illustrates a typical Ethernet configuration based on "10Base5" technology or "10Base2" technology in which the attached stations 4 are connected via a coaxial cable 5 of the appropriate type. Such a cable would be terminated electrically via terminator 6.
- An alternative arrangement making use of "10BaseT" technology is shown for Port 5. In this instance, each station is connected via a twisted pair of wires 7 to a unique connection B on the port.
- Each station illustrated has been given a unique name consisting of a letter followed by a port number. This naming is arbitrary and is used only to simplify discussion in order to illustrate the operation of the invention.
- FIG. 1 also shows the attachment of a monitoring device 9 to the monitoring port 10.
- the monitoring port will be Port 4.
- the monitoring device 9 will be the only station on the network segment attached to the monitoring port 10.
- a supervisory terminal 12 may also be attached to the bridge to provide control of the bridge in general and of the port-monitoring feature in particular.
- this attachment is made via a supervisory port 11, which is independent of the other ports illustrated and is only used to provide access to the bridge. It is possible, through the appropriate protocol, to provide access to supervisory terminal services at any of the connected stations 4.
- any or all of the ports 3 may be monitored ports.
- FIG. 2 illustrates the logical composition of a single packet 13.
- the packet itself consists of a variable number of octets, or 8 bit data units, and is divided into fields of an integral number of octets as shown.
- the nomenclature and purpose of the fields is as follows:
- Destination Address 15--A pattern that specifies the address of the station or stations 4 to receive the packet
- FCS 18--A check sequence over packet (excluding the preamble field) that is used by the destination stations to assess the validity of the received packet
- FIG. 3 illustrates the formation of the destination address 15 referred to also as DA.
- DA destination address 15
- two forms of DA may be used.
- One is the non-broadcast form 19 and the other is the broadcast form 20.
- a DA 15 consists of 6 octets, or 48 bits, and one of these bits, the Broadcast/Multicast flag 21, is used to differentiate between the two DA forms.
- the Broadcast/Multicast flag is zero
- the destination address consists of two components: a vendor code 22 and a device code 23. These codes are assigned by a central authority so that each station has a unique station address. The station address is physically associated with the station and is used to identify it, no matter where it may be located on a network, either on a single-segment network or in a larger network composed of multiple segments.
- the DA field 15 is interpreted differently. If the remaining bits of the DA (the Broadcast/Multicast address 24) are all ones, then the destination address is considered to designate all stations in the network, including stations on other segments connected to the bridge 1. In the case where the Broadcast/Multicast flag 21 is one, but the remaining bits of the DA 15 are not all ones, a multicast packet is indicated. The remaining bits then signify a subset of stations in the network that are destinations. Such stations may be attached to any one or different segments.
- the identification protocol is application dependent and will not be further specified here.
- the source address field 16 also referred to as SA, identifies the source station using an addressing scheme as discussed for the DA 15.
- SA does not make use of the Broadcast/Multicast flag, and so the contents of the source address field always consist of the vendor code 22 and device number 23 only and thus uniquely identify the station originating the packet.
- Stations transmit packets 13 in which the SA 16 contains their unique station address and in which the DA 15 contains the address of the station they wish to communicate with. Alternately, they can form a DA 15 so that it has broadcast address format 20 and the packet 13 will be received by all stations attached to the segment.
- Each station attached to the segment listens to all transmissions on that segment and checks the DA of each packet.
- a packet is intended for a station's address if a non-broadcast DA matches its station address exactly or a Broadcast/Multicast DA is received. In the case of a Broadcast/Multicast DA 20, the station will receive the packet if the Broadcast/Multicast address 24 matches according to application-specific rules.
- the purpose of the bridge 1 is to allow stations on different attached network segments to communicate with each other.
- network segments can be smaller physically (i.e., each segment can contain fewer station) and, therefore, each segment's electrical limits can be more easily met. From a performance standpoint, the transmission capacity of a segment is limited, and therefore the rate at which messages can be transferred between stations on a segment is limited.
- the overall usage of a connected segment will be reduced on average.
- stations on Port 2 such as A2 and C2
- stations on Port 3 may communicate at full segment speed simultaneously while stations on another port, say Port 3, also use the full capacity of their attached segment.
- the bridge 1 comes into play when a station on one segment, such as A0, must communicate with a station (or stations) on another segment, say C3. In this case, the bridge must pass packets for the two communicating stations between appropriate ports, in this case between Port 0 and Port 3. Because a station might be portable and thus might move from one segment to another, it is necessary for the bridge to implement an adaptive algorithm.
- One such prior-art algorithm is described in U.S. Pat. No. 4,597,078, entitled “Bridge Circuit for Interconnecting Networks.” Bridges constructed according to this algorithm are referred to as "learning bridges.” The following brief discussion of learning bridge operation is given here, since this is the preferred mode of bridge operation to which the invention applies.
- each station 4 has a unique address and that each packet 13 always contains the unique address of the originating station in the SA field 16.
- the bridge examines and evaluates all packet transmissions on its attached ports 3. Using information derived from this process, the bridge builds a Bridging Table 25, as illustrated in FIG. 4.
- Each Bridging Table Entry 26 consists of a Station Address field 27 and corresponding Port Number 28. There is one Bridging Table Entry 26 for each station currently known to the bridge. In the Bridging Table Entry 26 the Port Number 28 indicates the port to which the corresponding station is attached.
- FIG. 4 illustrates a Bridging Table corresponding to the example bridge and network configuration shown in FIG. 1. In the illustrated case, all bridge-attached station addresses are present in the Bridging Table 25. Because networks have a dynamic character, it is not necessarily the case that all station address/port number pairs will be in the Bridging Table 25 at all times.
- the Bridging Table 25 is built dynamically by the bridge, as discussed later. Ignoring for now the port monitor feature, the Bridging Table is used to forward received packets to their destinations as follows:
- the packet is forwarded to all attached ports, except the port on which it was received.
- the DA field 15 contains a unique station address.
- the Bridging Table 25 is accessed using the DA field 15 of the received packet. If the Bridging Table 25 contains an entry with a Station Address field 27 matching the DA field 15 of the received packet, then the corresponding Port Number field 28 is retrieved. There are two cases to consider. If the retrieved port number 28 is identical to the port number on which the packet was received, then the packet is destined for the same network segment as the sending station. In this case, no action is taken as the transmission has already occurred on the proper segment. The alternative case is where the retrieved port number 28 does not match the port number on which the packet was received. In this case, the packet is forwarded to the port number indicated by the retrieved Bridging Table Entry 26.
- the packet is forwarded to all attached ports, except for the port on which it was received. This ensures that the destination station, if present on any bridge-attached segment, will receive the packet.
- the Bridging Table 25 is built dynamically, as packets are received.
- the bridge examines the source address field 16 of each packet received on each port. If the station address in the source address field 16 of a received packet matches the Station Address field 27 of an entry in the Bridging Table 25 and the port number on which the packet was received matches the port number field 28 of that entry, then the Bridging Table is not modified. However, if the SA 16 of a received packet matches a Station Address field 27 of a Bridging Table Entry 26, but the port number on which the packet was received is not equal to the corresponding Port Number field 28 for that entry, then the Port Number field 28 is written with the port number on which the packet was received. Other actions, such as flushing the Bridging Cache 83 may also be required.
- the source address 16 of the received packet does not match the Station Address field 27 of any Bridging Table entry 26, then a new entry is added to the Bridging Table 25.
- This entry consists of a Station Address field 27 containing the SA of the received packet and a corresponding Port Number field 28 containing the port number of the port on which the packet was received.
- the Bridging Table 25 is empty. As packets on the attached network segments are examined, Bridging Table Entries 26 are formed and added to the Bridging Table 25. By this process, the bridge "learns" the correspondence between the attached stations and the port to which they are attached. To accommodate for the fact that networks change and stations may be added, removed or moved from one segment to another, the learning bridge incorporates an aging algorithm to periodically remove Bridging Table Entries 26 that have not been used for a period of time.
- the bridge could be configured not to forward packets to any DA on a particular port unless the Bridging Table contains a permanent entry for that DA, matching that port.
- bridge 1 is typically part of a large network consisting of many bridges and their attached segments.
- the topology of the network might include loops in which there is more than one network path between two bridges. This may be unintentional or intentional, for example where redundancy is required in the network.
- the packet is forwarded to all ports. If network loops are present, this forwarding activity can lead to infinite duplication and propagation of a packet.
- the learning bridge implements an algorithm, referred to as a "spanning-tree algorithm", that limits the ports to which packets of the type discussed above can be forwarded.
- This algorithm is well defined by IEEE Standard 802.1d. Operation of the spanning-tree algorithm requires that the bridge 1 form an internal map of the network to which it is attached. This is done by communicating periodically with other bridges attached to the segments that are attached to the bridge 1. Thus, there are instances in which the bridge itself may generate packets for transmission even though it has not received any specific packets instructing it to do so.
- the bridge makes forwarding decisions based only on the DA field 15 of a packet 13.
- more useful bridge operation can be had by further qualifying the forwarding decision based on specific contents of each packet.
- the forwarding of certain packets may be suppressed (that is, they are filtered out) if conditions based on packet contents are met. These conditions are referred to here as custom filtering rules (CFRs) and are implemented through the use of templates 29 as shown in FIG. 5.
- CFRs custom filtering rules
- a template 29 consists of three components, an offset 30, a 32-bit mask 31, and a 32-bit comparator 32.
- the template defines a test to be applied to a packet according to the following algorithm.
- the offset 30 is used to identify the start of a four-octet field, W, 33 of the packet. Offset 30 is expressed in octets from the start of the destination field 15.
- the identified field, W, 30 is then logically ANDed bit for bit with the 32-bit mask 31.
- the 32-bit result 34 is then compared logically (bit for bit) with the comparator 32 of the template yielding a logical result 35 which is true or false.
- the packet is not forwarded (i.e., it is filtered).
- the filtering algorithm is implemented with software; however, a strictly hardware implementation or a mixed hardware/software implementation is also possible.
- the bridge 1 should provide for a plurality of templates and that facilities be provided to allow for multiple templates to be evaluated against a given packet and for the results of such evaluation 35 to be combined according to the well-known rules of Boolean logic.
- filtering of a packet can be based on quite complex conditions. These complex conditions are referred to here as "custom filtering rules," or "CFRs.”
- CFRs custom filtering rules
- the bridge allow for the association of CFRs with the port on which the packet is received, the SA 16 of the received packet, the DA 15 of the received packet, and the destination port (or ports) to which the packet is forwarded.
- Various combinations of such associations are also possible.
- templates 29 and rules are defined through the use of the supervisory access terminal 12.
- the bridge is able to handle several situations reflecting the various packet generating and forwarding situations.
- these include:
- Packet routing involves receiving a packet on a port (i.e., from an attached network) and retransmitting it to another port based on information contained in the Data field 17.
- the DA of a packet to be routed will be either the station address of the router or a broadcast/multicast address.
- the SA 16 is the station address of the station or router originating the packet.
- the router may be physically and/or logically incorporated in a bridge. (Devices which combined router and bridge functionality are known as "brouters".)
- the Data field 17 is parsed and examined. Specific protocols are defined for each type of packet to be routed and are indicated by sub-fields in the packet Data field 17.
- One of the sub-fields may be a network address which is a logical, rather than a physical, address indicating the ultimate destination of the packet.
- the router modifies the DA 15 to point to the next link or hop in the route and substitutes its own address for SA 16.
- Sub-fields of the Data field 17 may also be modified. In particular, there is usually a "hop count" indicating the maximum number of hops a packet may traverse before it is considered invalid or mis-routed.
- Other sub-fields of Data 17 may include control options, length, type, serial number, priority and so forth. These sub-fields are used to further specify the route.
- CFRs may be applied to routed packets just as they are to bridged packets. It is also the case that some routed packets are consumed by the router or possibly generated internally for transmission to other routers. Thus it will be seen that routed packets can generate packet forwarding situations similar to those arising for bridges, as discussed above under "Summary of Bridge Operations.”
- FIG. 6 illustrates the hardware of the example bridge 1 in block diagram form.
- port controllers 37 are illustrated, although those skilled in the art of hardware system design will see that the design may be readily extended to additional ports 3.
- Each port is based on the ILACC 32-bit Ethernet Controller, available from Advanced Micro Devices (AMD) of Sunnyvale, Calif. These controllers have the capability of sending and receiving packets directly to and from the shared memory 39 via the shared memory interface 38 without direct intervention of the bridge Main CPU 42 or I/O CPU 43. This process will be discussed further below.
- AMD Advanced Micro Devices
- the bridge contains two processors whose primary function is to examine packets stored in the shared memory and make the appropriate changes to shared memory tables and data structures to allow forwarding to take place.
- the main CPU 42 is based on the MIPS R3001 25 MHz processor from Integrated Device Technology (IDT) of Santa Clara, Calif. Associated with the chip is a 256K Byte cache memory in which frequently referenced portions of the real-time packet forwarding code and control data are held.
- An attached Program Memory 41 contains up to 8 MBytes of additional storage for less time critical software and data, such as that related to the supervisory access function.
- a serial interface 45 is connected to the Main CPU to provide the Supervisory Access Port 11.
- a Floppy Disk 44 that provides a convenient means of updating the system software and saving configuration information, such as permanent Bridging Table entries and CFRs, to be read at system startup.
- a second processor, the I/O CPU 43, is based on a MIPS R3051 33 MHz processor also available from IDT.
- the primary purpose of this processor is to supervise the sending and receiving of packets 13, manage Packet Buffers in shared memory 39, handle packet reception errors and similar activities.
- This processor supports an onboard cache 46, which holds all of the I/O CPU code, thus providing very high performance.
- Packets received from the ports and packets generated within the system to support management functions are stored in the shared memory 39, which is based on a 1.5 Mbyte array of SRAMs.
- the structure of typical shared memory 39 is described in patent application "Methods and Apparatus for Data Transfer Between Source and Destination Modules," Ser. No. 07/304,053, now U.S. Pat. No. 5,237,670.
- the configured array has an aggregate bandwidth of 400 Mbytes/second.
- Shared memory is made available to the port controllers 37, the Main CPU 42, and the I/O CPU 43 via the shared memory interface 38.
- Each Port controller 37 is allocated 32 Kbytes of shared memory for received packets and 64 Kbytes of shared memory for transmitted packets.
- Packet forwarding is the process by which a received packet (or possibly one generated internally) is transmitted on one or more ports 3. While the forwarding decisions are made primarily by the Main CPU, the port controllers 37 and the I/O CPU 43 also participate in the mechanics of forwarding.
- FIG. 7 shows shared memory 39 data structures involved in the reception, forwarding, and transmission of packets. Portions of these data structures can be manipulated by the port controllers, Main CPU and I/O CPU. Packets being processed are stored in Packet Buffers 47 maintained in the Packet Buffer Pool 48. Each Packet Buffer 47 is a contiguous shared memory area sufficient to hold an average sized Ethernet packet (of up to 256 octets). When longer packets must be handled, several Packet Buffers 47 are used.
- a Packet Descriptor 49 is a shared-memory data structure and has five components.
- the packet pointer 50 points to the actual packet data held in a Packet Buffer 47 in the Packet Buffer Pool 48.
- the Packet Descriptor 49 may be copied or moved.
- Move means to copy and delete the original.
- the packet itself is not moved or copied, it is only referred to via the packet pointer 50. This indirect approach saves considerable shared-memory space and access bandwidth.
- Flags 51 within the Packet Descriptor indicate various conditions related to packet status, such as the presence of errors and their causes. Packet processing is directed by the State field 52 of the Packet Descriptor. Details of packet processing and State field 52 manipulation will be discussed below.
- the Length field 53 indicates the length of the packet within the Packet Buffer 47.
- the XMASK-Pointer 54 that points to an XMASK 55 indicating the destination port or ports (if any) to which the packet is to be transmitted.
- the Main CPU 42 fills in the XMASK-Pointer field based on the forwarding algorithm and conditions in effect at the time a packet is processed. Execution of the forwarding algorithm produces a data quantity referred to as an XMASK 55 and illustrated in FIG. 9.
- XMASK 55 is simply a bit vector in which each bit indicates a port 3 to which the packet 13 is to be dispatched. If multiple bits are set, then the packet will be dispatched to each port indicated. If no bits are set, then the packet will not be dispatched (forwarded) to any port.
- XMASK 55 will be represented in binary with the rightmost bit being the least significant bit and designating port 0. Table I shows some examples of XMASK values for the 6 port example system.
- a computed XMASK value 55 related to a packet 13 is held in the XMASK Pool 57, a data structure in shared memory 39.
- the XMASK-Pointer field 54 will point to the computed XMASK 55 in the XMASK Pool 57. This allows multiple Packet Descriptors 49 to point to the same XMASK value 55 and facilitates dispatching the same packet 13 to several ports, as would be required in a Broadcast/Multicast situation or when port monitoring is enabled.
- XMASK 55 designates only one destination port
- the port number itself may be held directly in the XMASK-Pointer 50 if a flag designating the alternate format is provided. This may be more efficient on some hardware systems.
- Packet processing will be explained by way of example using FIGS. 10A and 10B, which illustrate changes to the shared memory data structure as packet processing progresses. Use will also be made of FIG. 11 showing the sequence of processing steps.
- the actual Packet Buffer 47 is not moved or copied in shared memory 39. Instead, the Packet Descriptor 49 associated with that packet buffer is moved from one shared memory data structure to the next and possibly copied and/or modified.
- the State field 52 of the Packet Descriptor 49 is modified according to the sequence outlined in FIG. 11 where enclosed text, such as 64, 65, 66, 67, 68, 69 and 70 represent states. What is shown in FIG. 11 is the normal sequence of state processing where no errors have occurred.
- Receive Descriptor Ring 72 and Transmit Descriptor Ring (TDR) 71 realized in shared memory 39.
- FIGS. 10A and 10B only illustrate the RDR for Port 0 and the TDR for Ports 2 and 4.
- Receive and Transmit Descriptor Rings 72 and 71 are circular data structures of well known design and are of a fixed size designed to hold an integral number of Packet Descriptors 49. Descriptor ring size is a design choice based on various system parameters of the particular implementation.
- the RDR 72 will contain one or more Packet Descriptors 49, each with a State field 52 marked “Available for Reception” indicating that the associated Packet Buffers are available for the port controller 37 to fill with received packets.
- One Packet Descriptor in the RDR will be designated as to the next to be filled packet.
- Each "Available for Reception" Packet Descriptor 49 in the RDR will point to an empty Packet Buffer 47 in the Packet Buffer Pool 48 which is a data structure held in shared memory.
- the Packet Descriptor 49 is in the "Available for Reception" state 64.
- the Port 0 controller 37 When a packet arrives at Port 0, the Port 0 controller 37 will transfer the data received to the Packet Buffer 47, as directed by the Packet Pointer field 50 of the Packet Descriptor 49. In the preferred implementation, this process is under the control of the Port Controller 37 and occurs independently of other processes on other port controllers and processes on the Main CPU 42 and I/O CPU 43. It will be recognized, however, that other approaches to providing independent processes are possible.
- Port 0 Controller Once the Port 0 Controller has placed the received packet in the Packet Buffer 47, it will update the Packet Descriptor 49 by supplying the proper Length field 53, setting Flags 51 as required, and changing the State to "Received” 65 as shown in FIG. 11. At this point, Port Controller 0 will access the next "Available for Reception" Packet Descriptor 49 in preparation for receiving a new packet.
- the I/O CPU 43 supports a process that polls each Port RDR 72 and inspects the Packet Descriptors 49.
- a Packet Descriptor 49 is found to be in the "Received" state 65, the I/O CPU 43 will process the packet checking for packet errors and updating receive statistics (such as number of packets received on this port).
- receive statistics such as number of packets received on this port.
- the State field 52 of the Packet Descriptor 49 is marked as "Available for Forwarding" 66.
- the Main CPU 42 working independently of the Port Controller 37 and the I/O CPU 43, periodically polls all RDRs 72 to determine if any queued packets are to be forwarded. Based on the SA 16 and DA 15 fields of the Packet 13 and upon the port number of the RDR 72, on which the packet is queued (RPORT), the Main CPU will carry out the Forwarding Algorithm as in FIG. 16. The result of this process will be an XMASK value 55 designating the port or ports (possibly none) to which the packet 13 is to be forwarded. This XMASK 55 value will be placed in an available entry in the XMASK Pool 57 and the appropriate pointer to the entry will be entered into the XMASK-Pointer field 54 of the Packet Descriptor 49. The State field 52 of the Packet Descriptor is then changed to "Forwarded" 67.
- the I/O CPU 43 will scan the RDRs 72 to determine if any Packet Descriptors 49 are in a "Forwarded" state 67. When such a Packet Descriptor 49 is found, it will be copied to each TDR 71 (if any) as indicated by the set bits in the associated XMASK value 55.
- the State field 52 of each Packet Descriptor 49 copied to the TDR 71 is changed to "Available for Transmission" 68.
- Each Packet Descriptor 49 copied to a TDR 71 will contain a Packet Pointer 50 pointing to the packet in the Packet Buffer Pool 48 and an XMASK-Pointer 54 pointing to the XMASK value 55 in the XMASK pool 57.
- FIG. 10B illustrates the situation after the example packet has been forwarded to the TDRs for ports 2 and 4.
- Port Controllers 37 Each Port Controller 37 scans its associated TDR 71 and on encountering a Packet Descriptor 49 with a State field 52 marked "Available for Transmission” 68 will begin transmitting the Packet 13 from Packet Buffer 47 to its associated port. Upon completion of the transmission, the State field 52 is marked "Transmitted” 69.
- a packet When a packet is sent to two or more ports, it may be transmitted at different times, since packet transmission on a particular port depends on the state of the TDR associated with that port and the traffic queued on that port.
- Clean up of the TDR 71 is carried out by the I/O CPU 43, which periodically scans all TDRs 71.
- a Packet Descriptor 49 with a State field 52 marked "Transmitted” 69 is found, the bit in the XMASK 55 designated by the XMASK Pointer 54 corresponding to the port under examination is reset. If the XMASK 55 is now cleared, there are no more outstanding Packet Descriptors 49 associated with the packet 13; therefore, the Packet Buffer 47 is free and may be linked to a position on the Packet Buffer Free List 56 for later reuse.
- the Packet Descriptor 49 on the TDR 71 is marked as "Free" 70 making it available for reuse.
- the XMASK 55 is made available for reuse in the XMASK Pool 57.
- Forwarding of a packet 13 is based on several inputs and produces, as an output, an XMASK value 55.
- Required algorithmic inputs are DA 15--the destination address of a received packet, RPORT--the port number on which the packet was received, SA 16--the source address of the received packet, RSTATE--the state of the receiving port (RPORT 85), NG--the network groups, and the current CFRs in effect.
- RSTATE reflects the state of the receiving port. This is a port specific indicator (one per port) and indicates whether packets arriving at a port from its attached segment should be forwarded and whether packets from other ports or the packets generated within the bridge itself (management packets) may be forwarded to the port.
- RSTATE for a port varies slowly relative to the reception of packets and usually remains static for a long period of time. For example, RSTATE changes during the execution of the spanning-tree algorithm as ports are enabled and disabled to prevent logical loops.
- NG Network Groups
- NG Network Groups
- NG values are defined by a network administrator using the supervisory terminal 12 or its network-based equivalent connection.
- RSTATE NG values remain static for long periods of time relative to the transmission time of packets.
- CFRs Customer Filtering Rules
- SA 16 and DA 15 Data Field 17 contents
- CFRs when specified will have a dynamic effect on packet forwarding. That is, each packet arriving at a port (RPORT 85) with the same SA 16 and DA 15 may be forwarded differently. Thus CFRs must be evaluated for every packet forwarded between ports and specific addresses (SA 16 and DA 15) for which CFRs are currently defined. The discussion below initially assumes that CFRs are not in effect.
- the Bridging Table 25 (FIG. 4), the Forwarding Table 80 (FIG. 12), the Broadcast/Multicast Table 81 (FIG. 13), Management Table 82 (FIG. 14), and the Bridging Cache (FIG. 15).
- the structure of the Bridging Table 25 has been discussed above.
- FIG. 12 illustrates the Forwarding Table 80.
- This data structure is a two-dimensional array.
- One index of the array is RPORT 85, the number of the port on which the packet to be forwarded was received.
- the other index is XPORT 86, the number of the port on which the packet is to be sent based on the DA 15 field.
- XPORT 86 is determined by accessing the Bridging Table 25 with DA 15 and retrieving the corresponding Port Number field 28.
- Entries in the Forwarding Table 80 are XMASK values 55 and reflect the current port-to-port connectivity of the bridge based on NG and RSTATE. For normal forwarding (port monitoring not in effect) XMASK 55 will either be null (all zeroes) or will indicate a single port.
- FIG. 12 illustrates an example Forwarding Table 80 for a typical situation where all ports may communicate with each other. Null (all zeroes) XMASK values along the diagonal of the Forwarding Table indicate that if RPORT 85 is equal to XPORT 86 the packet should not be forwarded since the destination station is on the same port as the source station.
- Port 4 is isolated logically from all other ports.
- the monitoring port 10 will be Port 4.
- the Monitoring Port 10 is isolated logically so that only specifically identified monitored packets appear on the attached network segment.
- the Broadcast/Multicast Table 81 is illustrated in FIG. 13. When a received packet indicates a Broadcast or Multicast address (that is When the Broadcast/Multicast flag 21 is set), the Broadcast/Multicast Table 81 is used in place of the Forwarding Table 80 to develop XMASK 55.
- the Broadcast/Multicast Table 81 is a one dimensional array indexed by RPORT 85. Each array entry is an XMASK value 55.
- FIG. 13 illustrates a Broadcast/Multicast Table 81 in which all ports are allowed to communicate with one another, except for Port 4, the monitoring port of the example. Therefore, each entry will have a 1 in each XMASK 55 bit position except for bit 4 (the monitoring port) and the bit corresponding to RPORT (thereby preventing broadcast to the source port).
- Network Groups affect the contents of the Forwarding Table 80 and the Broadcast/Multicast Table 81.
- the examples in FIGS. 12 and 13 assume that all ports are allowed to communicate. If a network administrator has restricted communication by defining network groups, then some of the "1" entries in FIGS. 12 and 13 will be set to 0. For example, if ports 0 and 1 were defined as belonging to one network group, and ports 2, 3, 4, 5 were defined as belonging to another, then all of the Forwarding Table entries in the outlined regions 90, 92 in FIG. 12 would be 000000. Similarly, the Broadcast/Multicast Table bits in the outlined regions 94, 96 in FIG. 13 would also be zeros. Subsequent examples do not show Network Groups, but the port-monitoring operations described later take into account the possibility that Network Groups have been defined.
- Management Table 82 For packets generated within the bridge or router related to network management and router operation, Management Table 82 (FIG. 14) is used. This table is a one dimensional array indexed by MPORT 78, the port number on which the management related packet is to be sent. FIG. 14 illustrates an example Management Table 82 in which each port is available for participation in management functions except for Port 4, the monitoring port 10.
- the Bridging Cache 83 contains multiple logical entries in which specific RPORT 85, SA 16 and DA 15 values are associated with an XMASK 55. Since this association changes slowly, it is usually possible to bypass the normal forwarding calculation and retrieve the XMASK 55 value directly from the Bridging Cache 83. Other factors, such as NG and RSTATE also change slowly and thus do not degrade the operation of the Bridging Cache 83 unduly.
- the RPORT 85, SA 16 and DA 15 value used in the calculation are combined into an entry and placed in the Bridging Cache 83.
- the Bridging Cache 83 is accessed to determine if the RPORT 85, SA 16 and DA 15 associated with the packet match the RPORT 85, SA 16, and DA 15 of a Bridging Cache entry. If a match is found, then the XMASK value 55 from the Bridging Cache 83 can be used. Otherwise, the full forwarding algorithm must be carried out.
- the Bridging Cache is partitioned into separate sub-caches--one associated with each RPORT 85. Since the maximum number of the receiving ports is relatively small, this is a very efficient method of handling part of the cache look-up.
- the Bridging Cache is accessed with the 3-tuple ⁇ RPORT,SA,DA>. Based on RPORT 85, the appropriate sub-cache associated 77 with the receive port is selected. Next the 96-bit value consisting of SA 16 concatenated with DA 15 is hashed using well-known techniques to produce a pointer to a Bridging Cache entry 79 in the selected sub-cache 77. A comparison is then made between the input SA, DA values and the SA, DA values in the selected Bridging Cache entry 79.
- the XMASK value 55 for that entry is retrieved. If no match occurs, the next Bridging Cache entry 79 is examined in like manner. This process continues until a match is found or a maximum number of attempts is made. Other approaches to accessing of the Bridging Cache 83 achieving the same result will be evident to those skilled in the art.
- Bridging Cache 83 replaces the need to validate the received SA 16 in the Bridging Table 25, to look-up XPORT 86 in the Bridging Table 25 and to use the Forwarding Table 80 to retrieve XMASK 55.
- RPORT 85 and SA 16 are both used in the cache access so that changes to the port association of SA can be detected and accommodated as described next.
- Bridging Cache entries 79 must be invalidated or flushed if they no longer reflect the outcome of the Bridging Algorithm. If, for example, the correspondence between SA 16 and RPORT 85 is found to be invalid, all Bridging Cache entries 79 with the corresponding SA 16 value in the RPORT sub-cache 77 must be cleared (the "flush" step in FIG. 16). System level events may also cause a cache flush. For example, any change to the CFRs, the network groups NG, or the spanning-tree state may result in Bridging Cache entries 79 becoming invalid. In these cases, the offending Bridging Cache entries 79 must be removed or, if it is more efficient, all cache entries may be invalidated. Commands issued from the Supervisory Access Terminal 12 (or its network equivalent) may also cause a cache flush.
- Bridging Cache entries 79 include additional fields indicating the presence of a CFR and its point of application (DA, SA, RPORT). In some implementations this may allow CFR-related information to be accessed more quickly, depending on how data structures selected are realized.
- Packets that require forwarding may be incoming packets arriving at the bridge from its ports 3 or internally generated management packets.
- the forwarding algorithm discussed below operates in both cases and is also independent of whether port monitoring is enabled or disabled. To aid in illustrating the approach, a flow chart is provided in FIG. 16. It is assumed that the forwarding algorithm will be entered with parameters DA 15, SA 16, RPORT 85 from incoming packets and with MPORT 78 for internally generated packets. Execution of the forwarding algorithm in the preferred embodiment is carried out on the Main CPU 42.
- the SA 16 and DA 15 from the packet and the RPORT 85 value reflecting the port number on which the packet was received are used to access the Bridging Cache 83. If the 3-tuple ⁇ RPORT,SA,DA> is found in the Bridging Cache 83, the XMASK value 55 is retrieved immediately and the bridging algorithm is complete. Alternatively, if the 3-tuple ⁇ RPORT,SA,DA> is not found, full processing of the packet addresses must take place. In some embodiments, the Bridging Cache 83 will never contain an XMASK entry 55 for a Broadcast/Multicast addresses or if a custom filter rule is applicable to DA, SA or their associated ports. This restriction avoids wasting space in the bridging cache, since custom filtering rules must make decisions on the packet data as well as the SA 16 and DA 15 and thus cannot have a valid, static XMASK 55 value in the Bridging Cache.
- Full packet processing (i.e. when no matching cache entry is found), first involves a test of the DA 15 to determine if the Broadcast/Multicast flag 21 is set. If it is set then the XMASK value 55 is retrieved directly from the Broadcast/Multicast Table 81 using RPORT 85.
- the next step is to access the Bridging Table 25 using SA 16 to determine if the source address and its associated RPORT value 85 are currently present and correct. If it is determined that the SA 16, RPORT 85 relationship has changed or SA 16 is not present, then the Bridging Table 25 must be updated to reflect the new relationship. When this occurs, it is also necessary to search the Bridging Cache 83 and invalidate any entries with a Source Address field 16 equal to the SA 16 from the received packet 13.
- the Bridging Table 25 access shows that SA 16 is present and has the correct RPORT value
- the Bridging Table 25 is re-accessed using DA 15 in an attempt to retrieve the XPORT value 15 corresponding to DA.
- the RPORT value will be used to access the Broadcast/Multicast Table 81 to retrieve an XMASK 55. This XMASK will indicate ports to which the packet will be directed in an attempt to place it on a network where DA is located.
- the XPORT value 86 will be retrieved indicating the port where DA 15 is located.
- the Forwarding Table 80 is accessed and an XMASK 55 is retrieved.
- an XMASK value 55 is available for use in dispatching. In cases where XMASK 55 is obtained from the Bridging Cache 83, dispatching may be done directly. In all other cases, it is necessary to check for the presence of custom filtering rules. Flags indicating the presence of custom filtering rules are maintained in the Bridge Table 25 for SA 16 and DA 15 and in separate rule tables associated with each port. When indicated, the appropriate CFRs are evaluated and the XMASK 55 is modified as required to produce a final value. This process can be quite involved and may affect performance significantly.
- the Bridging Cache 83 is updated from ⁇ RPORT,SA,DA> to reflect the new XMASK value 55.
- the Bridging Cache 83 is better used if entries are devoted exclusively to single address DAs 15. In situations with different traffic profiles from the preferred embodiment, it may be desirable to include multicast and broadcast addresses in the Bridging Cache 83.
- Port monitoring is a process by which packets arriving at the bridge or generated internally may be copied to one or more monitoring ports 10 (FIG. 1).
- a monitoring device 9 attached to the monitoring port 10 is then able to provide analysis of the monitored packets.
- the monitoring device 9 would be, for example, a SnifferTM from Network General or a LANalyzerTM from Novell. These devices analyze packet traffic on a network and provide various diagnostic information enabling the network manager to locate problems, evaluate performance, and determine appropriate adjustments to network parameters.
- Port monitoring is controlled from the supervisory access terminal 12. Using this terminal, the network manager may identify monitored ports 3 and monitoring ports 10. When port monitoring is enabled, packets associated with the monitored ports 3 will be forwarded to monitoring ports 10. In the preferred implementation, these packets are not actually copied, but the packet processing protocol described above is used in which only the Packet Descriptors 49 are copied.
- Port monitoring is controlled by the Supervisory Access Terminal 12 using a simple command-line language.
- Table II illustrates the syntax of the commands. For each command, the prefix “pm" indicates that this is a port-monitoring command. There are three basic commands: “view”, “viewpair” and “close”. The first three commands shown in Table II are of the "view” type as identified by the command word "view”. These commands designate a ⁇ monitored-port-number> and ⁇ monitoring-port-number>. There is also a field to designate the type of monitoring desired, either "incoming", "forwarded” or "generated”. Incoming packets are those arriving at a designated monitored port 3. Forwarded packets are all packets forwarded to the designated monitored port 3 from any other port.
- Generated packets are those generated internally by the bridge and forwarded to the monitored port 3.
- all packets of the designated type will be "copied" from the port designated by ⁇ monitored-port-number> to the port designated by ⁇ monitoring-port-number>, in addition to their normal dispatching.
- a "viewpair" command specifies a pair of ports 3 and a monitoring port 10. Packets received on the port designated by the ⁇ source-monitored-port-number> and forwarded to the port designated by ⁇ destination-monitored-port-number> will be "copied" to the port designated by ⁇ monitoring-port-number>.
- command syntax outlined above could be enhanced using well-known techniques to provide a compound type of command allowing several monitored ports, monitoring ports, and packet forwarding situations to be specified in one command line or through other types of user interfaces.
- port monitoring involves modifying the data structures discussed previously to indicate the monitored 3 and monitoring ports 10. Modification will be illustrated for each of the monitoring situations: forwarded, incoming, generated, and port pairs.
- Port 4 As the designated monitoring port 10.
- port 2 For single-port monitoring, port 2 will be used, and for port-pair monitoring, port 2 will be the source-monitored-port and port 3 will be the destination monitored port.
- Port 4 is used only for monitoring. Therefore, packets will only be forwarded to Port 4 due to the enabling of the port-monitor function. This is the preferred mode of operation for the bridge when port monitoring is enabled, since other stations on the monitoring port may be unable to properly interpret packet traffic arising from the port-monitoring function.
- incoming packets on a port are to be monitored, then all packets received at the designated monitored port must be copied to the monitoring port. Packets are copied to the monitoring port even if they are not to be sent to any other port (i.e. they are consumed by the bridge).
- the Forwarding Table 80 and the Broadcast/Multicast Table 81 are modified.
- the Management Table 82 is not modified, since it affects only generated packets.
- each entry in the Forwarding Table 80 where RPORT 85 is equal to ⁇ monitored-port-number> is modified.
- the XMASK bit corresponding to ⁇ monitoring-port-number> is set.
- FIG. 17A shows the results of executing the command "pm view 2 on 4" on the example Forwarding Table of FIG. 12. Since port 2 is to be monitored on Port 4, each XMASK entry 55 in "row 2" 60 will have bit 4 set.
- Management Table 82 No modifications are made to the Management Table 82 to support the monitoring of incoming packets since XMASK values 55 in the table apply only to packets generated by the bridge.
- FIG. 18A shows the result of executing the command "pm view forwarded 2 on 4" on the example Forwarding Table 80 of FIG. 12.
- the modified entries are the "column 2" 3 and indicate that packets forwarded to port 2 should also be forwarded to Port 4, the monitoring port.
- Broadcast/Multicast packets can also be forwarded to the monitored port 3, thus it is necessary to modify the Broadcast/Multicast Table 81.
- Each XMASK entry in the Broadcast/Multicast Table 81 is modified by ORing the bit corresponding to ⁇ monitored-port-number> with the bit corresponding to ⁇ monitoring-port-number> and placing the result in the bit corresponding to ⁇ monitoring-port-number>.
- FIG. 18B shows the results of modifying the Broadcast/Multicast Table of FIG. 13 according to the command above.
- bit column 2 62 is ORed with "bit column” 4 63, and the result is returned to bit column 4 63 indicating that each Broadcast/Multicast packet from an RPORT that is forwarded to port 2 should also be forwarded to Port 4.
- Monitoring of generated packets involves modifying only the Management Table 82.
- the Forwarding Table 80 and the Broadcast/Multicast Table 81 remain unchanged since they have no effect on the forwarding of generated packets originating within the bridge itself.
- each XMASK entry 55 in the Management Table 82 is modified so that the bit corresponding to ⁇ monitored-port-number> is ORed with the bit corresponding to ⁇ monitoring-port-number>, and the result is placed in the bit corresponding to ⁇ monitoring-port-number>.
- FIG. 19 illustrates the result of the command "pm view generated 2 on 4" as applied to the example Management Table of FIG. 14.
- "Bit column” 2 75 corresponding to the monitored port 2 has been ORed with "bit column” 4 76 representing the monitoring Port 4, and the result is returned to bit column 4 76.
- FIG. 20A shows the results of applying the command "pm view pair 2 3 on 4" to the example Forwarding Table 80 of FIG. 12. The modified entry 84 is highlighted.
- Port Monitoring works naturally with the Bridging Cache 83.
- XMASK values obtained from the Forwarding Table 80 are placed in the Bridging Cache 83 provided no CFRs are in effect as would be the case in normal processing. Operation of the Bridging Cache 83 is unaffected by port monitoring.
- CFRs may be applied to the monitoring port 10. However, in the preferred embodiment this was not allowed so as to improve efficiency.
- monitoring commands may change XMASK values 55, it is important to flush the Bridging Cache 83 whenever a monitoring command is given.
- packets with errors and those that are too large or too small are not "copied" to monitoring port 10. This could be done if it was desirable in a particular implementation.
- the uncertainty as to the monitored packet's originating network segment is reduced. Indeed, the bridge knows precisely on which port each incoming packet was received, even if the packet's SA is wrong due to malfunction or sabotage. Thus the packets received on precisely selected port or ports can be isolated and forwarded to the network monitor even if the packets have wrong source addresses. The bridge debugging is therefore facilitated. In particular, security problems become easier to solve. The uncertainty is reduced also in the router embodiments because the router also determines the packet's receiving port independently of the packet's SA.
- different network segments connected to the bridge use different protocols.
- the bridge translates packets from one protocol format to another as needed.
- each packet transmitted to the monitoring port 10 is translated, if needed, to the format of the segment attached to the monitoring port.
- the bridge's ability to translate packets allows freedom in selecting the network segment attached to the monitoring port.
- some non-monitoring port segments are FDDI segments, and the segment attached to the monitoring port is an Ethernet segment. Using the Ethernet segment allows reducing the network cost because Ethernet network monitors are typically less expensive than FDDI network monitors.
- Packets are routed based on the contents of the Data Field 17. Routing depends on data structures similar to those used in bridging. For instance, there may be a Routing Table for translating network addresses into ports and network destinations. There may also be Address Resolution Tables to translate router and host targets into actual Ethernet addresses, which are in turn used to update the DA 15 of the packet 13 to direct it to the next link or to the final destination. As in bridging, performance can be improved by caching recently calculated results. For example, the Network address, Ethernet address and port number may be cached together with an XMASK 55 value.
- the forwarding decision depends on many factors, such as router state, state of the next hop, and the state of the route it is not possible to compute the XMASK 55 in a static, direct manner as can be done for bridging.
- the XMASK 55 derived from the Routing Table and Address Resolution Table is modified algorithmically according to the monitoring currently enabled. This XMASK 55 is then cached for later reference in the Routing Cache.
- a router When forwarding an incoming packet, a router normally modifies a portion of the packet header. For example, it replaces the SA and DA of the received packet with its own SA and the DA of the next hop, and it may update a hop count. When port monitoring is in effect, the packet forwarded on the monitoring port is the modified packet, not exactly the received packet.
- the router in order to forward exactly the received packet to the monitoring port, the router makes a copy of the received packet before modifying it. It will be apparent to those skilled in the art that it may not be necessary to copy the entire packet, only the modified part, if the Port Controllers 37 can "gather" multiple buffers into a single packet for transmission. In this case, an extra buffer can be allocated for the copied and modified part of the packet, while the original buffer can be used to forward the packet to the monitoring port (or vice versa).
Abstract
Description
TABLE I ______________________________________ Examples of XMASK XMASK ACTION ______________________________________ 000000 Do Not Dispatch 000001 Dispatch toPort 0 only 010011 Dispatch to0, 1 and 4 111111 Dispatch to All Ports ______________________________________ Ports
TABLE II ______________________________________ Port Monitoring Command Syntax ______________________________________ pm view incoming <monitored-port number> on <monitoring-port number> pm view forwarded <monitored-port number> on <monitoring-port number> pm view generated <monitored-port number> on <monitoring-port number> pm viewpair <source-monitored-port-number>, <destination-monitored-port-number> on <monitoring-port-number> pm close ______________________________________
Claims (53)
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US08/358,211 US5610905A (en) | 1993-07-19 | 1994-12-13 | Communication apparatus and methods |
US08/713,046 US6545982B1 (en) | 1993-07-19 | 1996-09-12 | Communication apparatus and methods |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US08/093,397 US5515376A (en) | 1993-07-19 | 1993-07-19 | Communication apparatus and methods |
US08/358,211 US5610905A (en) | 1993-07-19 | 1994-12-13 | Communication apparatus and methods |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US08/093,397 Division US5515376A (en) | 1993-07-19 | 1993-07-19 | Communication apparatus and methods |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US08/713,046 Division US6545982B1 (en) | 1993-07-19 | 1996-09-12 | Communication apparatus and methods |
Publications (1)
Publication Number | Publication Date |
---|---|
US5610905A true US5610905A (en) | 1997-03-11 |
Family
ID=22238695
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US08/093,397 Expired - Lifetime US5515376A (en) | 1993-07-19 | 1993-07-19 | Communication apparatus and methods |
US08/358,211 Expired - Lifetime US5610905A (en) | 1993-07-19 | 1994-12-13 | Communication apparatus and methods |
US08/713,046 Expired - Lifetime US6545982B1 (en) | 1993-07-19 | 1996-09-12 | Communication apparatus and methods |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US08/093,397 Expired - Lifetime US5515376A (en) | 1993-07-19 | 1993-07-19 | Communication apparatus and methods |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US08/713,046 Expired - Lifetime US6545982B1 (en) | 1993-07-19 | 1996-09-12 | Communication apparatus and methods |
Country Status (6)
Country | Link |
---|---|
US (3) | US5515376A (en) |
EP (1) | EP0710415B1 (en) |
JP (1) | JP3335358B2 (en) |
AT (1) | ATE293327T1 (en) |
DE (1) | DE69434330T2 (en) |
WO (1) | WO1995003659A1 (en) |
Cited By (127)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5715250A (en) * | 1995-03-31 | 1998-02-03 | Nec Corporation | ATM-lan connection apparatus of a small scale capable of connecting terminals of different protocol standards and ATM-lan including the ATM-lan connection apparatus |
US5802054A (en) * | 1996-08-15 | 1998-09-01 | 3Com Corporation | Atomic network switch with integrated circuit switch nodes |
US5835696A (en) * | 1995-11-22 | 1998-11-10 | Lucent Technologies Inc. | Data router backup feature |
WO1999000950A1 (en) * | 1997-06-30 | 1999-01-07 | Sun Microsystems, Inc. | Trunking support in a high performance network device |
US5898837A (en) * | 1996-02-23 | 1999-04-27 | Bay Networks, Inc. | Method and apparatus for monitoring a dedicated communications medium in a switched data network |
US5920566A (en) * | 1997-06-30 | 1999-07-06 | Sun Microsystems, Inc. | Routing in a multi-layer distributed network element |
US5938736A (en) * | 1997-06-30 | 1999-08-17 | Sun Microsystems, Inc. | Search engine architecture for a high performance multi-layer switch element |
WO1999046882A2 (en) * | 1998-03-12 | 1999-09-16 | Whale Communications Ltd. | Techniques for protection of data-communication networks |
US6014380A (en) * | 1997-06-30 | 2000-01-11 | Sun Microsystems, Inc. | Mechanism for packet field replacement in a multi-layer distributed network element |
US6044087A (en) * | 1997-06-30 | 2000-03-28 | Sun Microsystems, Inc. | Interface for a highly integrated ethernet network element |
US6044400A (en) * | 1995-03-25 | 2000-03-28 | Lucent Technologies Inc. | Switch monitoring system having a data collection device using filters in parallel orientation and filter counter for counting combination of filtered events |
US6044401A (en) * | 1996-11-20 | 2000-03-28 | International Business Machines Corporation | Network sniffer for monitoring and reporting network information that is not privileged beyond a user's privilege level |
US6044418A (en) * | 1997-06-30 | 2000-03-28 | Sun Microsystems, Inc. | Method and apparatus for dynamically resizing queues utilizing programmable partition pointers |
US6047321A (en) * | 1996-02-23 | 2000-04-04 | Nortel Networks Corporation | Method and apparatus for monitoring a dedicated communications medium in a switched data network |
US6049824A (en) * | 1997-11-21 | 2000-04-11 | Adc Telecommunications, Inc. | System and method for modifying an information signal in a telecommunications system |
US6049528A (en) * | 1997-06-30 | 2000-04-11 | Sun Microsystems, Inc. | Trunking ethernet-compatible networks |
US6052738A (en) * | 1997-06-30 | 2000-04-18 | Sun Microsystems, Inc. | Method and apparatus in a packet routing switch for controlling access at different data rates to a shared memory |
EP1005739A1 (en) * | 1997-06-30 | 2000-06-07 | Sun Microsystems, Inc. | Shared memory management in a switched network element |
US6078977A (en) * | 1993-11-02 | 2000-06-20 | Micron Electronics, Inc. | Hierarchical bus structure access system |
US6081532A (en) * | 1995-10-20 | 2000-06-27 | International Business Machines Corporation | Bridging apparatus for traffic filtering in communication networks |
US6081522A (en) * | 1997-06-30 | 2000-06-27 | Sun Microsystems, Inc. | System and method for a multi-layer network element |
US6081512A (en) * | 1997-06-30 | 2000-06-27 | Sun Microsystems, Inc. | Spanning tree support in a high performance network device |
US6088356A (en) * | 1997-06-30 | 2000-07-11 | Sun Microsystems, Inc. | System and method for a multi-layer network element |
US6094435A (en) * | 1997-06-30 | 2000-07-25 | Sun Microsystems, Inc. | System and method for a quality of service in a multi-layer network element |
US6098120A (en) * | 1997-01-16 | 2000-08-01 | Alps Electric Co., Ltd. | Peripheral sharing system using a bus bridge to emulate peripherals on a first bus to a host on a second bus |
US6119196A (en) * | 1997-06-30 | 2000-09-12 | Sun Microsystems, Inc. | System having multiple arbitrating levels for arbitrating access to a shared memory by network ports operating at different data rates |
US6128666A (en) * | 1997-06-30 | 2000-10-03 | Sun Microsystems, Inc. | Distributed VLAN mechanism for packet field replacement in a multi-layered switched network element using a control field/signal for indicating modification of a packet with a database search engine |
EP1045539A2 (en) * | 1999-04-13 | 2000-10-18 | Alcatel | Monitoring of the transmission quality in a digital telecommunication network |
US6154462A (en) * | 1997-08-21 | 2000-11-28 | Adc Telecommunications, Inc. | Circuits and methods for a ring network |
US6189042B1 (en) * | 1997-04-09 | 2001-02-13 | Alcatel | LAN internet connection having effective mechanism to classify LAN traffic and resolve address resolution protocol requests |
US6198920B1 (en) | 1995-06-01 | 2001-03-06 | Padcom, Inc. | Apparatus and method for intelligent routing of data between a remote device and a host system |
US6205147B1 (en) * | 1997-02-11 | 2001-03-20 | Newbridge Networks Corporation | Virtual network architecture |
US6230271B1 (en) * | 1998-01-20 | 2001-05-08 | Pilot Network Services, Inc. | Dynamic policy-based apparatus for wide-range configurable network service authentication and access control using a fixed-path hardware configuration |
US6246680B1 (en) | 1997-06-30 | 2001-06-12 | Sun Microsystems, Inc. | Highly integrated multi-layer switch element architecture |
US20010006524A1 (en) * | 2000-01-05 | 2001-07-05 | Wilfried Krug | Network coupling device and data network with network coupling device |
US6272133B1 (en) * | 1998-05-21 | 2001-08-07 | Inviscid Networks, Inc. | Packet filtering method |
WO2001063838A2 (en) * | 2000-02-22 | 2001-08-30 | Top Layer Networks, Inc. | System and method for flow mirroring in a network switch |
US6308218B1 (en) * | 1997-09-17 | 2001-10-23 | Sony Corporation | Address look-up mechanism in a multi-port bridge for a local area network |
US6310876B1 (en) * | 1997-02-14 | 2001-10-30 | Advanced Micro Devices, Inc. | Method and apparatus for managing bin chains in a memory |
US20010048687A1 (en) * | 1997-08-21 | 2001-12-06 | Adc Telecommunications, Inc. | Telecommunication network with variable address learning, switching and routing |
EP1168710A2 (en) * | 2000-06-19 | 2002-01-02 | Broadcom Corporation | Method and device for frame forwarding in a switch fabric |
US6347089B1 (en) * | 1997-07-02 | 2002-02-12 | Advanced Communication Devices Corp. | Simplified ethernet frame switching system architecture without local buffer requirement |
US20020018470A1 (en) * | 2000-08-11 | 2002-02-14 | Peter Galicki | Datapipe routing bridge |
WO2002019585A1 (en) * | 2000-08-31 | 2002-03-07 | Verizon Communications Inc. | Methods, apparatus and data structures for segmenting customers using at least a portion of a layer 2 address header or bits in the place of layer 2 address header |
US6389030B1 (en) | 1998-08-21 | 2002-05-14 | Adc Telecommunications, Inc. | Internet access over a ring network |
US6392996B1 (en) * | 1998-04-13 | 2002-05-21 | At&T Corp. | Method and apparatus for frame peeking |
US6425015B1 (en) * | 1997-11-28 | 2002-07-23 | 3 Com Technologies | Stacked communication devices and method for port mirroring using modified protocol |
US20020098840A1 (en) * | 1998-10-09 | 2002-07-25 | Hanson Aaron D. | Method and apparatus for providing mobile and other intermittent connectivity in a computing environment |
US20020099827A1 (en) * | 2001-01-22 | 2002-07-25 | Shah Hemal V. | Filtering calls in system area networks |
US6441931B1 (en) | 1996-02-23 | 2002-08-27 | Nortel Networks Limited | Method and apparatus for monitoring a dedicated communications medium in a switched data network |
US20020138646A1 (en) * | 2001-03-26 | 2002-09-26 | Tetsuya Tsuboi | Subscriber terminating apparatus and packet processing method |
US6463479B1 (en) | 1997-11-28 | 2002-10-08 | 3Com Technologies | Apparatus for trunking in stacked communication devices |
US20020156916A1 (en) * | 2001-04-23 | 2002-10-24 | The Furukawa Electric Co., Ltd. | Network relay installation, port monitoring method, and computer program for executing this method |
US20030012196A1 (en) * | 1996-11-08 | 2003-01-16 | Ramakrishnan Kadangode K. | Promiscuous network monitoring utilizing multicasting within a switch |
US6539546B1 (en) | 1998-08-21 | 2003-03-25 | Adc Telecommunications, Inc. | Transport of digitized signals over a ring network |
US20030067913A1 (en) * | 2001-10-05 | 2003-04-10 | International Business Machines Corporation | Programmable storage network protocol handler architecture |
US6570880B1 (en) | 1998-08-21 | 2003-05-27 | Adc Telecommunications, Inc. | Control data over a ring network |
US20030123458A1 (en) * | 2000-05-26 | 2003-07-03 | Kari Innala | Network for data transfer |
FR2834848A1 (en) * | 2002-01-15 | 2003-07-18 | France Telecom | METHOD FOR OBSERVING A COMMUNICATION NETWORK AND SYSTEM FOR IMPLEMENTING SAID METHOD |
US20030174705A1 (en) * | 2002-03-15 | 2003-09-18 | Broadcom Corporation | Multilevel parser for conditional flow detection in a network device |
US20030179754A1 (en) * | 2002-03-20 | 2003-09-25 | Broadcom Corporation | Two stage egress scheduler for a network device |
US20030182431A1 (en) * | 1999-06-11 | 2003-09-25 | Emil Sturniolo | Method and apparatus for providing secure connectivity in mobile and other intermittent computing environments |
US20030198231A1 (en) * | 1999-06-30 | 2003-10-23 | Broadcom Corporation | Frame forwarding in a switch fabric |
US6671739B1 (en) * | 2000-07-10 | 2003-12-30 | International Business Machines Corporation | Controlling network access by modifying packet headers at a local hub |
US6717914B1 (en) * | 1999-05-27 | 2004-04-06 | 3Com Corporation | System for probing switched virtual circuits in a connection oriented network |
US6738384B1 (en) | 1997-09-17 | 2004-05-18 | Sony Corporation | Technique for optimizing cut-through for broadcast and multi-cast packets in a multi-port bridge for a local area network |
US6751219B1 (en) | 2000-04-20 | 2004-06-15 | Aztech Partners, Inc. | Multicast packet duplication at random node or at egress port with frame synchronization |
US6772267B2 (en) * | 2000-02-18 | 2004-08-03 | Bridgeco Ag | Multi-portal bridge for providing network connectivity |
US20040153854A1 (en) * | 2003-01-10 | 2004-08-05 | Andiamo Systems, Inc. | Port analyzer adapter |
US20040170176A1 (en) * | 1999-03-17 | 2004-09-02 | Broadcom Corporation | Method for handling IP multicast packets in network switch |
US20040181686A1 (en) * | 2003-03-13 | 2004-09-16 | Krause Joel M. | Integrated customer premises equipment device |
US6807182B1 (en) * | 1999-11-02 | 2004-10-19 | 3Com Corporation | Stacked network devices including a protocol engine and distributed trunk ports and method of operating same |
US20050053073A1 (en) * | 2003-09-03 | 2005-03-10 | Andiamo Systems, Inc. A Delaware Corporation | Switch port analyzers |
US20050066081A1 (en) * | 2003-09-23 | 2005-03-24 | Chandra Prashant R. | Free packet buffer allocation |
US6876654B1 (en) * | 1998-04-10 | 2005-04-05 | Intel Corporation | Method and apparatus for multiprotocol switching and routing |
US20050094567A1 (en) * | 2003-08-01 | 2005-05-05 | West Ridge Networks | Systems and methods for intelligent probe testing |
US6891801B1 (en) * | 1999-05-05 | 2005-05-10 | Siemens Aktiengesellschaft | Method of operating a data transmission system |
US6901075B1 (en) * | 1998-03-12 | 2005-05-31 | Whale Communications Ltd. | Techniques for protection of data-communication networks |
US20050125424A1 (en) * | 2003-12-05 | 2005-06-09 | Guy Herriott | Decision cache using multi-key lookup |
US6907036B1 (en) * | 1999-06-28 | 2005-06-14 | Broadcom Corporation | Network switch enhancements directed to processing of internal operations in the network switch |
US6944127B1 (en) * | 2000-08-07 | 2005-09-13 | Bbnt Solutions Llc | System for detecting spurious network traffic |
US6952421B1 (en) * | 1999-10-07 | 2005-10-04 | Cisco Technology, Inc. | Switched Ethernet path detection |
US20050223114A1 (en) * | 1998-10-09 | 2005-10-06 | Netmotion Wireless, Inc. | Method and apparatus for providing mobile and other intermittent connectivity in a computing environment |
US20050223115A1 (en) * | 1998-10-09 | 2005-10-06 | Netmotion Wireless, Inc. | Method and apparatus for providing mobile and other intermittent connectivity in a computing environment |
US20060023676A1 (en) * | 1995-06-01 | 2006-02-02 | Padcom, Inc. | Port routing |
US20060050653A1 (en) * | 2004-09-09 | 2006-03-09 | James Guichard | Routing protocol support for half duplex virtual routing and forwarding instance |
US20060114914A1 (en) * | 2004-11-30 | 2006-06-01 | Broadcom Corporation | Pipeline architecture of a network device |
US20060114906A1 (en) * | 2004-11-30 | 2006-06-01 | Broadcom Corporation | System and method for maintaining a layer 2 modification buffer |
US20060123079A1 (en) * | 2001-09-12 | 2006-06-08 | Netmotion Wireless, Inc. | Mobile networking system and method |
US20060187936A1 (en) * | 2005-02-18 | 2006-08-24 | Broadcom Corporation | Table searching techniques in a network device |
US20060187923A1 (en) * | 2005-02-18 | 2006-08-24 | Broadcom Corporation | Dynamic filter processor key generation based on packet type |
US20060187832A1 (en) * | 2005-02-18 | 2006-08-24 | Broadcom Corporation | Filter based range check in a network device |
US20060187948A1 (en) * | 2005-02-18 | 2006-08-24 | Broadcom Corporation | Layer two and layer three virtual private network support in a network device |
US20060187941A1 (en) * | 2005-02-23 | 2006-08-24 | Broadcom Corporation | Self-correcting memory system |
US20060187945A1 (en) * | 2005-02-18 | 2006-08-24 | Broadcom Corporation | Weighted-fair-queuing relative bandwidth sharing |
US20060187825A1 (en) * | 2005-02-18 | 2006-08-24 | Broadcom Corporation | Dynamic color threshold in a queue |
US20060190777A1 (en) * | 2005-02-18 | 2006-08-24 | Broadcom Corporation | Memory command unit throttle and error recovery |
US20060187924A1 (en) * | 2005-02-18 | 2006-08-24 | Broadcom Corporation | Ingress handling of data in a network device |
US20060187826A1 (en) * | 2005-02-18 | 2006-08-24 | Broadcom Corporation | Dynamic sharing of a transaction queue |
US20060203824A1 (en) * | 2005-02-18 | 2006-09-14 | Song-Huo Yu | Passing values through a memory management unit of a network device |
US20060209865A1 (en) * | 2005-02-18 | 2006-09-21 | Broadcom Corporation | Multi-part parsing in a network device |
US20070076730A1 (en) * | 2005-09-20 | 2007-04-05 | Shahriar Rahman | Internetworking support between a LAN and a wireless mesh network |
US20070110024A1 (en) * | 2005-11-14 | 2007-05-17 | Cisco Technology, Inc. | System and method for spanning tree cross routes |
US20070115966A1 (en) * | 2005-11-21 | 2007-05-24 | Broadcom Corporation | Compact packet operation device and method |
US7293107B1 (en) | 1998-10-09 | 2007-11-06 | Netmotion Wireless, Inc. | Method and apparatus for providing mobile and other intermittent connectivity in a computing environment |
US7315554B2 (en) | 2000-08-31 | 2008-01-01 | Verizon Communications Inc. | Simple peering in a transport network employing novel edge devices |
US7366171B2 (en) | 1999-03-17 | 2008-04-29 | Broadcom Corporation | Network switch |
CN100411388C (en) * | 2005-05-24 | 2008-08-13 | 华为技术有限公司 | Method for implementing image in exchange system |
US7574597B1 (en) | 2001-10-19 | 2009-08-11 | Bbn Technologies Corp. | Encoding of signals to facilitate traffic analysis |
US20090327903A1 (en) * | 2006-07-06 | 2009-12-31 | Referentia Systems, Inc. | System and Method for Network Topology and Flow Visualization |
US7643481B2 (en) | 1999-03-17 | 2010-01-05 | Broadcom Corporation | Network switch having a programmable counter |
US7710867B1 (en) * | 2003-05-23 | 2010-05-04 | F5 Networks, Inc. | System and method for managing traffic to a probe |
US7778260B2 (en) | 1998-10-09 | 2010-08-17 | Netmotion Wireless, Inc. | Method and apparatus for providing mobile and other intermittent connectivity in a computing environment |
US7787361B2 (en) | 2005-07-29 | 2010-08-31 | Cisco Technology, Inc. | Hybrid distance vector protocol for wireless mesh networks |
US7899048B1 (en) * | 2003-01-15 | 2011-03-01 | Cisco Technology, Inc. | Method and apparatus for remotely monitoring network traffic through a generic network |
US20110164618A1 (en) * | 1996-12-16 | 2011-07-07 | Juniper Networks, Inc. | Memory organization in a switching device |
US8087064B1 (en) | 2000-08-31 | 2011-12-27 | Verizon Communications Inc. | Security extensions using at least a portion of layer 2 information or bits in the place of layer 2 information |
US8165136B1 (en) | 2003-09-03 | 2012-04-24 | Cisco Technology, Inc. | Virtual port based SPAN |
US8238344B1 (en) * | 2007-03-30 | 2012-08-07 | Juniper Networks, Inc. | Multicast load balancing |
US8418233B1 (en) | 2005-07-29 | 2013-04-09 | F5 Networks, Inc. | Rule based extensible authentication |
US8533308B1 (en) | 2005-08-12 | 2013-09-10 | F5 Networks, Inc. | Network traffic management through protocol-configurable transaction processing |
US8559313B1 (en) | 2006-02-01 | 2013-10-15 | F5 Networks, Inc. | Selectively enabling packet concatenation based on a transaction boundary |
US8842127B1 (en) * | 2005-04-25 | 2014-09-23 | Apple Inc. | Text rendering with improved glyph cache management |
US9106606B1 (en) | 2007-02-05 | 2015-08-11 | F5 Networks, Inc. | Method, intermediate device and computer program code for maintaining persistency |
US9130846B1 (en) | 2008-08-27 | 2015-09-08 | F5 Networks, Inc. | Exposed control components for customizable load balancing and persistence |
US9614772B1 (en) | 2003-10-20 | 2017-04-04 | F5 Networks, Inc. | System and method for directing network traffic in tunneling applications |
US9832069B1 (en) | 2008-05-30 | 2017-11-28 | F5 Networks, Inc. | Persistence based on server response in an IP multimedia subsystem (IMS) |
Families Citing this family (207)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6157621A (en) * | 1991-10-28 | 2000-12-05 | Teledesic Llc | Satellite communication system |
US5515376A (en) | 1993-07-19 | 1996-05-07 | Alantec, Inc. | Communication apparatus and methods |
US6269398B1 (en) * | 1993-08-20 | 2001-07-31 | Nortel Networks Limited | Method and system for monitoring remote routers in networks for available protocols and providing a graphical representation of information received from the routers |
WO1997000471A2 (en) * | 1993-12-15 | 1997-01-03 | Check Point Software Technologies Ltd. | A system for securing the flow of and selectively modifying packets in a computer network |
US5835726A (en) * | 1993-12-15 | 1998-11-10 | Check Point Software Technologies Ltd. | System for securing the flow of and selectively modifying packets in a computer network |
JP3542159B2 (en) * | 1994-03-17 | 2004-07-14 | 株式会社日立製作所 | Bridge with multiprocessor structure |
US5666292A (en) * | 1994-12-13 | 1997-09-09 | Pitney Bowes Inc. | External interface unit having message routing and protocol conversion |
US5857075A (en) * | 1995-01-11 | 1999-01-05 | Sony Corporation | Method and integrated circuit for high-bandwidth network server interfacing to a local area network |
US6256313B1 (en) | 1995-01-11 | 2001-07-03 | Sony Corporation | Triplet architecture in a multi-port bridge for a local area network |
US5790799A (en) * | 1995-05-17 | 1998-08-04 | Digital Equipment Corporation | System for sampling network packets by only storing the network packet that its error check code matches with the reference error check code |
JPH08331137A (en) * | 1995-05-31 | 1996-12-13 | Fujitsu Ltd | Smds exchange |
US5608892A (en) * | 1995-06-09 | 1997-03-04 | Alantec Corporation | Active cache for a microprocessor |
US5691984A (en) * | 1995-08-15 | 1997-11-25 | Honeywell Inc. | Compact, adaptable brouting switch |
US5740175A (en) * | 1995-10-03 | 1998-04-14 | National Semiconductor Corporation | Forwarding database cache for integrated switch controller |
US5754791A (en) * | 1996-03-25 | 1998-05-19 | I-Cube, Inc. | Hierarchical address translation system for a network switch |
US6243667B1 (en) | 1996-05-28 | 2001-06-05 | Cisco Systems, Inc. | Network flow switching and flow data export |
US6381632B1 (en) * | 1996-09-10 | 2002-04-30 | Youpowered, Inc. | Method and apparatus for tracking network usage |
EP0849911A3 (en) * | 1996-12-18 | 1999-02-10 | Nortel Networks Corporation | Communications network monitoring |
US6222840B1 (en) * | 1996-12-30 | 2001-04-24 | Compaq Computer Corporation | Method and system for performing concurrent read and write cycles in network switch |
US6098110A (en) * | 1996-12-30 | 2000-08-01 | Compaq Computer Corporation | Network switch with a multiple bus structure and a bridge interface for transferring network data between different buses |
US6098109A (en) * | 1996-12-30 | 2000-08-01 | Compaq Computer Corporation | Programmable arbitration system for determining priority of the ports of a network switch |
US6665733B1 (en) * | 1996-12-30 | 2003-12-16 | Hewlett-Packard Development Company, L.P. | Network communication device including bonded ports for increased bandwidth |
US6233246B1 (en) | 1996-12-30 | 2001-05-15 | Compaq Computer Corporation | Network switch with statistics read accesses |
US6201789B1 (en) * | 1996-12-30 | 2001-03-13 | Compaq Computer Corporation | Network switch with dynamic backpressure per port |
US6173364B1 (en) * | 1997-01-15 | 2001-01-09 | At&T Corp. | Session cache and rule caching method for a dynamic filter |
US5953335A (en) * | 1997-02-14 | 1999-09-14 | Advanced Micro Devices, Inc. | Method and apparatus for selectively discarding packets for blocked output queues in the network switch |
US6175902B1 (en) | 1997-12-18 | 2001-01-16 | Advanced Micro Devices, Inc. | Method and apparatus for maintaining a time order by physical ordering in a memory |
US6130891A (en) * | 1997-02-14 | 2000-10-10 | Advanced Micro Devices, Inc. | Integrated multiport switch having management information base (MIB) interface temporary storage |
US6233244B1 (en) | 1997-02-14 | 2001-05-15 | Advanced Micro Devices, Inc. | Method and apparatus for reclaiming buffers |
US6151316A (en) * | 1997-02-14 | 2000-11-21 | Advanced Micro Devices, Inc. | Apparatus and method for synthesizing management packets for transmission between a network switch and a host controller |
US6061351A (en) * | 1997-02-14 | 2000-05-09 | Advanced Micro Devices, Inc. | Multicopy queue structure with searchable cache area |
US6094436A (en) * | 1997-02-14 | 2000-07-25 | Advanced Micro Devices, Inc. | Integrated multiport switch having shared media access control circuitry |
US6128654A (en) * | 1997-02-14 | 2000-10-03 | Advanced Micro Devices, Inc. | Method and apparatus for transmitting multiple copies by replicating data identifiers |
US6487212B1 (en) | 1997-02-14 | 2002-11-26 | Advanced Micro Devices, Inc. | Queuing structure and method for prioritization of frames in a network switch |
US6115387A (en) * | 1997-02-14 | 2000-09-05 | Advanced Micro Devices, Inc. | Method and apparatus for controlling initiation of transmission of data as a function of received data |
US6041042A (en) * | 1997-05-27 | 2000-03-21 | Cabletron Systems, Inc. | Remote port mirroring system and method thereof |
US6324516B1 (en) * | 1997-06-11 | 2001-11-27 | Matthew P. Shults | System and apparatus for utilization review of medical claims |
US6449273B1 (en) * | 1997-09-04 | 2002-09-10 | Hyundai Electronics America | Multi-port packet processor |
US6442168B1 (en) * | 1997-09-17 | 2002-08-27 | Sony Corporation | High speed bus structure in a multi-port bridge for a local area network |
US6617879B1 (en) | 1997-09-17 | 2003-09-09 | Sony Corporation | Transparently partitioned communication bus for multi-port bridge for a local area network |
US6301256B1 (en) | 1997-09-17 | 2001-10-09 | Sony Corporation | Selection technique for preventing a source port from becoming a destination port in a multi-port bridge for a local area network |
US6363067B1 (en) * | 1997-09-17 | 2002-03-26 | Sony Corporation | Staged partitioned communication bus for a multi-port bridge for a local area network |
US6446173B1 (en) | 1997-09-17 | 2002-09-03 | Sony Corporation | Memory controller in a multi-port bridge for a local area network |
US6157951A (en) * | 1997-09-17 | 2000-12-05 | Sony Corporation | Dual priority chains for data-communication ports in a multi-port bridge for a local area network |
US6128296A (en) * | 1997-10-03 | 2000-10-03 | Cisco Technology, Inc. | Method and apparatus for distributed packet switching using distributed address tables |
US5926463A (en) * | 1997-10-06 | 1999-07-20 | 3Com Corporation | Method and apparatus for viewing and managing a configuration of a computer network |
GB2333428B (en) * | 1997-11-28 | 2002-10-16 | 3Com Technologies Ltd | Congestion control in a management port |
US6128729A (en) * | 1997-12-16 | 2000-10-03 | Hewlett-Packard Company | Method and system for automatic configuration of network links to attached devices |
US6075721A (en) * | 1997-12-18 | 2000-06-13 | Advanced Micro Devices, Inc. | Random access memory having bit selectable mask for memory writes |
US6084878A (en) * | 1997-12-18 | 2000-07-04 | Advanced Micro Devices, Inc. | External rules checker interface |
US6091707A (en) * | 1997-12-18 | 2000-07-18 | Advanced Micro Devices, Inc. | Methods and apparatus for preventing under-flow conditions in a multiple-port switching device |
US6084856A (en) * | 1997-12-18 | 2000-07-04 | Advanced Micro Devices, Inc. | Method and apparatus for adjusting overflow buffers and flow control watermark levels |
US6080203A (en) * | 1997-12-18 | 2000-06-27 | Advanced Micro Devices, Inc. | Apparatus and method for designing a test and modeling system for a network switch device |
US6084877A (en) * | 1997-12-18 | 2000-07-04 | Advanced Micro Devices, Inc. | Network switch port configured for generating an index key for a network switch routing table using a programmable hash function |
JPH11249823A (en) * | 1998-02-27 | 1999-09-17 | Hitachi Ltd | Bus control system |
US6175868B1 (en) * | 1998-05-15 | 2001-01-16 | Nortel Networks Limited | Method and apparatus for automatically configuring a network switch |
US6871229B2 (en) * | 1998-08-26 | 2005-03-22 | Sts Software Systems Ltd. | Method for storing on a computer network a portion of a communication session between a packet source and a packet destination |
US6229538B1 (en) | 1998-09-11 | 2001-05-08 | Compaq Computer Corporation | Port-centric graphic representations of network controllers |
US6272113B1 (en) | 1998-09-11 | 2001-08-07 | Compaq Computer Corporation | Network controller system that uses multicast heartbeat packets |
US6381218B1 (en) | 1998-09-11 | 2002-04-30 | Compaq Computer Corporation | Network controller system that uses directed heartbeat packets |
US6347087B1 (en) * | 1998-10-05 | 2002-02-12 | Packet Engines Incorporated | Content-based forwarding/filtering in a network switching device |
EP0993156B1 (en) * | 1998-10-05 | 2007-01-03 | Alcatel | Network switching device with forwarding database tables populated based on use |
US6611891B1 (en) * | 1998-11-23 | 2003-08-26 | Advanced Micro Devices, Inc. | Computer resource configuration mechanism across a multi-pipe communication link |
CN100369437C (en) * | 1999-01-14 | 2008-02-13 | 诺基亚网络有限公司 | Interception method and system |
DE60020417T2 (en) * | 1999-01-25 | 2005-10-27 | Nippon Telegraph And Telephone Corp. | Push network |
US6636523B1 (en) | 1999-01-27 | 2003-10-21 | Advanced Micro Devices, Inc. | Flow control using rules queue monitoring in a network switching system |
US6463032B1 (en) | 1999-01-27 | 2002-10-08 | Advanced Micro Devices, Inc. | Network switching system having overflow bypass in internal rules checker |
US6546010B1 (en) | 1999-02-04 | 2003-04-08 | Advanced Micro Devices, Inc. | Bandwidth efficiency in cascaded scheme |
US6466580B1 (en) | 1999-02-23 | 2002-10-15 | Advanced Micro Devices, Inc. | Method and apparatus for processing high and low priority frame data transmitted in a data communication system |
US6393028B1 (en) | 1999-02-25 | 2002-05-21 | Advanced Micro Devices, Inc. | Method and apparatus for providing EOF for frame modification |
US6769055B1 (en) | 1999-03-08 | 2004-07-27 | Advanced Micro Devices, Inc. | Two-part memory address generator |
AU3889300A (en) * | 1999-03-15 | 2000-10-04 | Smartsan Systems, Inc. | System and method of zoning and access control in a computer network |
US6490280B1 (en) | 1999-03-31 | 2002-12-03 | Advanced Micro Devices, Inc. | Frame assembly in dequeuing block |
US6515990B1 (en) | 1999-03-31 | 2003-02-04 | Advanced Micro Devices, Inc. | Dequeuing logic architecture and operation in a multiport communication switch |
US6731596B1 (en) | 1999-04-01 | 2004-05-04 | Advanced Micro Devices, Inc. | Network switch having system for automatically detecting change in network node connection |
US6487199B1 (en) | 1999-04-07 | 2002-11-26 | Advanced Micro Devices, Inc. | Method and apparatus for maintaining randomly accessible copy number information on a network switch |
US6336156B1 (en) | 1999-04-22 | 2002-01-01 | Advanced Micro Devices, Inc. | Increased speed initialization using dynamic slot allocation |
US7369550B1 (en) | 1999-04-22 | 2008-05-06 | Advanced Micro Devices | Method and apparatus for locking a table in a network switch |
US6480490B1 (en) | 1999-05-05 | 2002-11-12 | Advanced Micro Devices, Inc. | Interleaved access to address table in network switching system |
US6335938B1 (en) | 1999-05-05 | 2002-01-01 | Advanced Micro Devices, Inc. | Multiport communication switch having gigaport and expansion ports sharing the same time slot in internal rules checker |
US6405258B1 (en) | 1999-05-05 | 2002-06-11 | Advanced Micro Devices Inc. | Method and apparatus for controlling the flow of data frames through a network switch on a port-by-port basis |
US6895015B1 (en) * | 1999-05-05 | 2005-05-17 | Advanced Micro Devices, Inc. | Dynamic time slot allocation in internal rules checker scheduler |
US6345371B1 (en) | 1999-05-05 | 2002-02-05 | Advanced Micro Devices Inc. | Method of performing diagnostic procedures on a queue structure |
US6701489B1 (en) | 1999-05-07 | 2004-03-02 | Advanced Micro Devices, Inc. | Method and apparatus for changing register implementation without code change |
US6483844B1 (en) | 1999-05-13 | 2002-11-19 | Advanced Micro Devices, Inc. | Apparatus and method for sharing an external memory between multiple network switches |
US6563818B1 (en) | 1999-05-20 | 2003-05-13 | Advanced Micro Devices, Inc. | Weighted round robin cell architecture |
US20060023716A1 (en) * | 1999-05-20 | 2006-02-02 | Advanced Micro Devices, Inc. | Bit bucket |
US6625157B2 (en) | 1999-05-20 | 2003-09-23 | Advanced Micro Devices, Inc. | Apparatus and method in a network switch port for transferring data between buffer memory and transmit and receive state machines according to a prescribed interface protocol |
US6477170B1 (en) | 1999-05-21 | 2002-11-05 | Advanced Micro Devices, Inc. | Method and apparatus for interfacing between systems operating under different clock regimes with interlocking to prevent overwriting of data |
US6618390B1 (en) | 1999-05-21 | 2003-09-09 | Advanced Micro Devices, Inc. | Method and apparatus for maintaining randomly accessible free buffer information for a network switch |
US6725270B1 (en) | 1999-05-21 | 2004-04-20 | Advanced Micro Devices, Inc. | Apparatus and method for programmably modifying a limit of a retry counter in a network switch port in response to exerting backpressure |
US6904043B1 (en) | 1999-05-21 | 2005-06-07 | Advanced Micro Devices, Inc. | Apparatus and methods for storing and processing header information in a network switch |
US6563790B1 (en) | 1999-05-21 | 2003-05-13 | Advanced Micro Devices, Inc. | Apparatus and method for modifying a limit of a retry counter in a network switch port in response to exerting backpressure |
US6535489B1 (en) | 1999-05-21 | 2003-03-18 | Advanced Micro Devices, Inc. | Method and apparatus in a network switch for handling link failure and link recovery in a trunked data path |
US6816488B1 (en) | 1999-05-21 | 2004-11-09 | Advanced Micro Devices, Inc. | Apparatus and method for processing data frames in a network switch |
US6553027B1 (en) | 1999-05-21 | 2003-04-22 | Advanced Micro Devices, Inc. | Apparatus and method for cascading multiple network switch devices |
US6813266B1 (en) | 1999-05-21 | 2004-11-02 | Advanced Micro Devices, Inc. | Pipelined access to address table in a network switch |
US6597693B1 (en) | 1999-05-21 | 2003-07-22 | Advanced Micro Devices, Inc. | Common scalable queuing and dequeuing architecture and method relative to network switch data rate |
US6507564B1 (en) * | 1999-05-21 | 2003-01-14 | Advanced Micro Devices, Inc. | Method and apparatus for testing aging function in a network switch |
US6529503B1 (en) | 1999-05-21 | 2003-03-04 | Advanced Micro Devices, Inc. | Apparatus and method for storing header information in a network switch |
US6577636B1 (en) | 1999-05-21 | 2003-06-10 | Advanced Micro Devices, Inc. | Decision making engine receiving and storing a portion of a data frame in order to perform a frame forwarding decision |
US6463478B1 (en) | 1999-05-21 | 2002-10-08 | Advanced Micro Devices, Inc. | Method and apparatus for identifying runt data frames received by a network switch |
US6574231B1 (en) | 1999-05-21 | 2003-06-03 | Advanced Micro Devices, Inc. | Method and apparatus for queuing data frames in a network switch port |
US7027437B1 (en) | 1999-05-21 | 2006-04-11 | Advanced Micro Devices, Inc. | Network switch multiple-port sniffing |
US6504846B1 (en) | 1999-05-21 | 2003-01-07 | Advanced Micro Devices, Inc. | Method and apparatus for reclaiming buffers using a single buffer bit |
US6401147B1 (en) | 1999-05-24 | 2002-06-04 | Advanced Micro Devices, Inc. | Split-queue architecture with a first queue area and a second queue area and queue overflow area having a trickle mode and an overflow mode based on prescribed threshold values |
US6442137B1 (en) | 1999-05-24 | 2002-08-27 | Advanced Micro Devices, Inc. | Apparatus and method in a network switch for swapping memory access slots between gigabit port and expansion port |
US6775290B1 (en) | 1999-05-24 | 2004-08-10 | Advanced Micro Devices, Inc. | Multiport network switch supporting multiple VLANs per port |
US7031305B1 (en) | 1999-05-24 | 2006-04-18 | Advanced Micro Devices, Inc. | Apparatus and method for programmable memory access slot assignment |
US6501734B1 (en) | 1999-05-24 | 2002-12-31 | Advanced Micro Devices, Inc. | Apparatus and method in a network switch for dynamically assigning memory interface slots between gigabit port and expansion port |
US6584106B1 (en) | 1999-05-24 | 2003-06-24 | Advanced Micro Devices, Inc. | Backbone forwarding scheme for multiport network switch |
US6680945B1 (en) | 1999-05-24 | 2004-01-20 | Advanced Micro Devices, Inc. | Method and apparatus for support of tagging and untagging per VLAN per port |
GB2350530B (en) * | 1999-05-25 | 2001-05-30 | 3Com Corp | Port mirroring across a trunked stack of multi-port communication devices |
US6625146B1 (en) | 1999-05-28 | 2003-09-23 | Advanced Micro Devices, Inc. | Method and apparatus for operating a network switch in a CPU-less environment |
US6515993B1 (en) | 1999-05-28 | 2003-02-04 | Advanced Micro Devices, Inc. | Method and apparatus for manipulating VLAN tags |
US6721277B1 (en) | 1999-05-28 | 2004-04-13 | Advanced Micro Devices, Inc. | Generic register interface for accessing registers located in different clock domains |
US6658015B1 (en) | 1999-05-28 | 2003-12-02 | Advanced Micro Devices, Inc. | Multiport switch with plurality of logic engines for simultaneously processing different respective data frames |
US6697371B1 (en) * | 1999-06-01 | 2004-02-24 | Advanced Micro Devices, Inc. | Network switch with on-board management information based (MIB) counters |
AU5461600A (en) * | 1999-06-03 | 2000-12-28 | Fujitsu Network Communications, Inc. | Method and system for transmitting traffic in a virtual tunnel of a transmission line |
US6665301B1 (en) | 1999-06-03 | 2003-12-16 | Fujitsu Network Communications, Inc. | Transmission slot allocation method and map for virtual tunnels in a transmission line |
US6658006B1 (en) | 1999-06-03 | 2003-12-02 | Fujitsu Network Communications, Inc. | System and method for communicating data using modified header bits to identify a port |
US6760332B1 (en) * | 1999-06-03 | 2004-07-06 | Fujitsu Network Communications, Inc. | ATM multicasting system and method |
US6501758B1 (en) | 1999-06-03 | 2002-12-31 | Fujitsu Network Communications, Inc. | Hybrid ATM/TDM transport over a common fiber ring |
US6785285B1 (en) * | 1999-06-03 | 2004-08-31 | Fujitsu Network Communications, Inc. | Method and system for providing broadcast channels over an emulated subnetwork |
US6542512B1 (en) | 1999-07-02 | 2003-04-01 | Jenny Liu Fischer | Architecture and method for flushing non-transmitted portions of a data frame from a transmitted FIFO buffer |
US6731601B1 (en) | 1999-09-09 | 2004-05-04 | Advanced Micro Devices, Inc. | Apparatus and method for resetting a retry counter in a network switch port in response to exerting backpressure |
FR2801454B1 (en) * | 1999-11-18 | 2004-04-30 | Cit Alcatel | X25 NETWORK AND DATA TRANSMISSION METHOD |
US7239633B1 (en) * | 1999-12-29 | 2007-07-03 | Winbond Electronics Corp. | Ethernet switch and method of switching |
US6697870B1 (en) * | 2000-01-28 | 2004-02-24 | Networks Associates Technology, Inc. | Method and apparatus for real-time protocol analysis using an auto-throttling front end process |
US6732184B1 (en) | 2000-01-31 | 2004-05-04 | Advanced Micro Devices, Inc. | Address table overflow management in a network switch |
US6873600B1 (en) * | 2000-02-04 | 2005-03-29 | At&T Corp. | Consistent sampling for network traffic measurement |
JP4436960B2 (en) * | 2000-05-16 | 2010-03-24 | 日本電気株式会社 | Packet communication system and mobile communication system |
US7054272B1 (en) * | 2000-07-11 | 2006-05-30 | Ciena Corporation | Upper layer network device including a physical layer test port |
US8619793B2 (en) * | 2000-08-21 | 2013-12-31 | Rockstar Consortium Us Lp | Dynamic assignment of traffic classes to a priority queue in a packet forwarding device |
US7143185B1 (en) * | 2000-08-29 | 2006-11-28 | Advanced Micro Devices, Inc. | Method and apparatus for accessing external memories |
US6857027B1 (en) * | 2000-11-14 | 2005-02-15 | 3Com Corporation | Intelligent network topology and configuration verification using a method of loop detection |
CA2329097A1 (en) * | 2000-12-20 | 2002-06-20 | Nortel Networks Limited | Apparatus and method for signal recognition within wdm optical nodes |
DE60212599D1 (en) * | 2001-03-01 | 2006-08-03 | Storeage Networking Technologi | SECURITY FOR A SAN (STORAGE AREA NETWORK) |
JP2003099341A (en) * | 2001-09-20 | 2003-04-04 | Canon Inc | Network device-managing device, managing system, managing method and network device |
US20030084219A1 (en) * | 2001-10-26 | 2003-05-01 | Maxxan Systems, Inc. | System, apparatus and method for address forwarding for a computer network |
US7240123B2 (en) * | 2001-12-10 | 2007-07-03 | Nortel Networks Limited | Distributed routing core |
US7145914B2 (en) | 2001-12-31 | 2006-12-05 | Maxxan Systems, Incorporated | System and method for controlling data paths of a network processor subsystem |
US7085846B2 (en) * | 2001-12-31 | 2006-08-01 | Maxxan Systems, Incorporated | Buffer to buffer credit flow control for computer network |
US20030210696A1 (en) * | 2002-04-25 | 2003-11-13 | Globespanvirata Incorporated | System and method for routing across segments of a network switch |
US7406038B1 (en) | 2002-04-05 | 2008-07-29 | Ciphermax, Incorporated | System and method for expansion of computer network switching system without disruption thereof |
US7379970B1 (en) | 2002-04-05 | 2008-05-27 | Ciphermax, Inc. | Method and system for reduced distributed event handling in a network environment |
US7307995B1 (en) | 2002-04-05 | 2007-12-11 | Ciphermax, Inc. | System and method for linking a plurality of network switches |
US7295561B1 (en) | 2002-04-05 | 2007-11-13 | Ciphermax, Inc. | Fibre channel implementation using network processors |
US20030195956A1 (en) * | 2002-04-15 | 2003-10-16 | Maxxan Systems, Inc. | System and method for allocating unique zone membership |
US20030200330A1 (en) * | 2002-04-22 | 2003-10-23 | Maxxan Systems, Inc. | System and method for load-sharing computer network switch |
US20030202510A1 (en) * | 2002-04-26 | 2003-10-30 | Maxxan Systems, Inc. | System and method for scalable switch fabric for computer network |
US8165114B2 (en) * | 2002-06-13 | 2012-04-24 | Nice Systems Ltd. | Voice over IP capturing |
US7660297B2 (en) * | 2002-06-13 | 2010-02-09 | Nice Systems Ltd. | Voice over IP forwarding |
GB2389736B (en) * | 2002-06-13 | 2005-12-14 | Nice Systems Ltd | A method for forwarding and storing session packets according to preset and/or dynamic rules |
EP1525678B1 (en) | 2002-06-21 | 2008-07-30 | QUALCOMM Incorporated | Wireless local area network repeater |
JP3996010B2 (en) * | 2002-08-01 | 2007-10-24 | 株式会社日立製作所 | Storage network system, management apparatus, management method and program |
US20040030766A1 (en) * | 2002-08-12 | 2004-02-12 | Michael Witkowski | Method and apparatus for switch fabric configuration |
US6823383B2 (en) * | 2002-09-10 | 2004-11-23 | Capital One Financial Corporation | Stealth network |
US7936688B2 (en) * | 2002-09-16 | 2011-05-03 | Jds Uniphase Corporation | Protocol cross-port analysis |
US8058371B2 (en) * | 2002-09-20 | 2011-11-15 | Exxonmobil Chemical Patents Inc. | Super-solution homogeneous propylene polymerization |
JP2004118250A (en) * | 2002-09-24 | 2004-04-15 | Hitachi Ltd | Computer management system and management program |
US8885688B2 (en) | 2002-10-01 | 2014-11-11 | Qualcomm Incorporated | Control message management in physical layer repeater |
US20060063484A1 (en) * | 2002-10-24 | 2006-03-23 | Proctor James A Jr | Wireless local area network repeater with in-band control channel |
US8122134B2 (en) | 2002-10-11 | 2012-02-21 | Qualcomm Incorporated | Reducing loop effects in a wireless local area network repeater |
US8078100B2 (en) | 2002-10-15 | 2011-12-13 | Qualcomm Incorporated | Physical layer repeater with discrete time filter for all-digital detection and delay generation |
CN100574147C (en) * | 2002-10-15 | 2009-12-23 | 高通股份有限公司 | The WLAN (wireless local area network) transponder that is used for expanding coverage area of network with automatic gain control |
US7230935B2 (en) * | 2002-10-24 | 2007-06-12 | Widefi, Inc. | Physical layer repeater with selective use of higher layer functions based on network operating conditions |
CA2504347A1 (en) * | 2002-11-15 | 2004-06-03 | Widefi, Inc. | Wireless local area network repeater with detection |
US20050102497A1 (en) * | 2002-12-05 | 2005-05-12 | Buer Mark L. | Security processor mirroring |
JP2006510326A (en) * | 2002-12-16 | 2006-03-23 | ワイデファイ インコーポレイテッド | Improved wireless network repeater |
US8769164B2 (en) * | 2003-09-18 | 2014-07-01 | International Business Machines Corporation | Methods and apparatus for allocating bandwidth for a network processor |
US7672318B2 (en) * | 2003-11-06 | 2010-03-02 | Telefonaktiebolaget L M Ericsson (Publ) | Adaptable network bridge |
JP4516306B2 (en) | 2003-11-28 | 2010-08-04 | 株式会社日立製作所 | How to collect storage network performance information |
US7690040B2 (en) | 2004-03-10 | 2010-03-30 | Enterasys Networks, Inc. | Method for network traffic mirroring with data privacy |
US8027642B2 (en) | 2004-04-06 | 2011-09-27 | Qualcomm Incorporated | Transmission canceller for wireless local area network |
WO2005109718A1 (en) | 2004-05-05 | 2005-11-17 | Gigamon Systems Llc | Asymmetric packet switch and a method of use |
US7606230B1 (en) * | 2004-05-10 | 2009-10-20 | Marvell International Ltd. | Link aggregation for routed ports |
JP4960223B2 (en) | 2004-05-13 | 2012-06-27 | クゥアルコム・インコーポレイテッド | Non-frequency conversion repeater for detection and media access control |
US7554990B2 (en) * | 2004-05-13 | 2009-06-30 | Micrel, Inc. | Static address reservation protocol in a data network |
US7187904B2 (en) * | 2004-06-03 | 2007-03-06 | Widefi, Inc. | Frequency translating repeater with low cost high performance local oscillator architecture |
WO2006023829A2 (en) * | 2004-08-20 | 2006-03-02 | Enterasys Networks, Inc. | System, method and apparatus for traffic mirror setup, service and security in communication networks |
US20060161689A1 (en) * | 2005-01-18 | 2006-07-20 | Hewlett-Packard Development Company, L.P. | Apparatus and systems for monitoring communication |
WO2006081405A2 (en) * | 2005-01-28 | 2006-08-03 | Widefi, Inc. | Physical layer repeater configuration for increasing mino performance |
US8108673B2 (en) | 2005-04-29 | 2012-01-31 | Cisco Technology, Inc. | Configuring interfaces of a switch using templates |
US20070016637A1 (en) * | 2005-07-18 | 2007-01-18 | Brawn John M | Bitmap network masks |
JP4652285B2 (en) * | 2006-06-12 | 2011-03-16 | 株式会社日立製作所 | Packet transfer device with gateway selection function |
JP4791301B2 (en) | 2006-09-13 | 2011-10-12 | 株式会社オートネットワーク技術研究所 | In-vehicle LAN system |
US8559379B2 (en) | 2006-09-21 | 2013-10-15 | Qualcomm Incorporated | Method and apparatus for mitigating oscillation between repeaters |
JP4875164B2 (en) | 2006-10-26 | 2012-02-15 | クゥアルコム・インコーポレイテッド | Repeater technology for multiple inputs and multiple outputs using beamformers |
JP4680866B2 (en) * | 2006-10-31 | 2011-05-11 | 株式会社日立製作所 | Packet transfer device with gateway load balancing function |
US20080107109A1 (en) * | 2006-11-03 | 2008-05-08 | General Instrument Corporation | Method and Apparatus for Managing Multicast Traffic in a Network at the Data Link or Level 2 Layer |
US7957273B2 (en) * | 2008-06-06 | 2011-06-07 | Redpine Signals, Inc. | Packet re-transmission controller for block acknowledgement in a communications system |
JP5251457B2 (en) * | 2008-11-27 | 2013-07-31 | 富士通株式会社 | Data transmission device |
US8934495B1 (en) | 2009-07-31 | 2015-01-13 | Anue Systems, Inc. | Filtering path view graphical user interfaces and related systems and methods |
US8018943B1 (en) | 2009-07-31 | 2011-09-13 | Anue Systems, Inc. | Automatic filter overlap processing and related systems and methods |
US8098677B1 (en) | 2009-07-31 | 2012-01-17 | Anue Systems, Inc. | Superset packet forwarding for overlapping filters and related systems and methods |
US8463928B2 (en) * | 2009-10-27 | 2013-06-11 | Verisign, Inc. | Efficient multiple filter packet statistics generation |
JP5328754B2 (en) * | 2010-11-22 | 2013-10-30 | 三菱電機株式会社 | Message collection and analysis device, message collection and analysis method, and program |
US9094318B2 (en) * | 2012-03-29 | 2015-07-28 | Avaya Inc. | Remote mirroring |
US9467385B2 (en) | 2014-05-29 | 2016-10-11 | Anue Systems, Inc. | Cloud-based network tool optimizers for server cloud networks |
US9781044B2 (en) | 2014-07-16 | 2017-10-03 | Anue Systems, Inc. | Automated discovery and forwarding of relevant network traffic with respect to newly connected network tools for network tool optimizers |
US10050847B2 (en) | 2014-09-30 | 2018-08-14 | Keysight Technologies Singapore (Holdings) Pte Ltd | Selective scanning of network packet traffic using cloud-based virtual machine tool platforms |
US10355964B2 (en) * | 2014-10-31 | 2019-07-16 | At&T Intellectual Property I, L.P. | Method and system to capture selected network data |
US9992134B2 (en) | 2015-05-27 | 2018-06-05 | Keysight Technologies Singapore (Holdings) Pte Ltd | Systems and methods to forward packets not passed by criteria-based filters in packet forwarding systems |
US10116528B2 (en) | 2015-10-02 | 2018-10-30 | Keysight Technologies Singapore (Holdings) Ptd Ltd | Direct network traffic monitoring within VM platforms in virtual processing environments |
US10652112B2 (en) | 2015-10-02 | 2020-05-12 | Keysight Technologies Singapore (Sales) Pte. Ltd. | Network traffic pre-classification within VM platforms in virtual processing environments |
US10142212B2 (en) | 2015-10-26 | 2018-11-27 | Keysight Technologies Singapore (Holdings) Pte Ltd | On demand packet traffic monitoring for network packet communications within virtual processing environments |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US3938144A (en) * | 1973-11-28 | 1976-02-10 | Johnson Service Company | Digital multiplexing system remote scanning of a plurality of monitoring points |
US4817080A (en) * | 1987-02-24 | 1989-03-28 | Digital Equipment Corporation | Distributed local-area-network monitoring system |
US4920529A (en) * | 1987-02-27 | 1990-04-24 | Hitachi, Ltd. | Network control method and apparatus therefor |
US5151897A (en) * | 1990-03-20 | 1992-09-29 | Fujitsu Limited | Inter-LAN connection apparatus and inter-LAN connection method |
US5274631A (en) * | 1991-03-11 | 1993-12-28 | Kalpana, Inc. | Computer network switching system |
US5321695A (en) * | 1991-05-01 | 1994-06-14 | Hewlett-Packard Company | Port arrival identification for computer network packets |
Family Cites Families (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
NO123200B (en) | 1967-11-23 | 1971-10-11 | Svenska Handelsbanken | |
JPS58134554A (en) * | 1982-02-03 | 1983-08-10 | Nec Corp | Transmission line monitoring device |
JPS59198043A (en) | 1983-04-25 | 1984-11-09 | Fujitsu Ltd | System for collecting traffic density information |
US5088032A (en) * | 1988-01-29 | 1992-02-11 | Cisco Systems, Inc. | Method and apparatus for routing communications among computer networks |
US5097469A (en) * | 1989-05-19 | 1992-03-17 | Concord Communications, Inc. | Passive monitor for broadcast communication network |
JPH03123137A (en) | 1989-10-05 | 1991-05-24 | Fujitsu Ltd | Manual registration system in routing table of mac bridge |
US5165021A (en) * | 1991-01-18 | 1992-11-17 | Racal-Datacom, Inc. | Transmit queue with loadsheding |
JPH05114905A (en) | 1991-04-08 | 1993-05-07 | Digital Equip Corp <Dec> | Message processing filtering using single address and protocol table bridge |
US5420862A (en) * | 1991-06-14 | 1995-05-30 | Digital Equipment Corporation | Router using remote address resolution to enable bridge like data forwarding |
JP3123137B2 (en) | 1991-08-20 | 2001-01-09 | チッソ株式会社 | Method for producing optically active 3-substituted-2-norbornanone |
US5515376A (en) | 1993-07-19 | 1996-05-07 | Alantec, Inc. | Communication apparatus and methods |
-
1993
- 1993-07-19 US US08/093,397 patent/US5515376A/en not_active Expired - Lifetime
-
1994
- 1994-06-29 DE DE69434330T patent/DE69434330T2/en not_active Expired - Lifetime
- 1994-06-29 AT AT94921361T patent/ATE293327T1/en not_active IP Right Cessation
- 1994-06-29 JP JP50515195A patent/JP3335358B2/en not_active Expired - Lifetime
- 1994-06-29 WO PCT/US1994/007082 patent/WO1995003659A1/en active IP Right Grant
- 1994-06-29 EP EP94921361A patent/EP0710415B1/en not_active Expired - Lifetime
- 1994-12-13 US US08/358,211 patent/US5610905A/en not_active Expired - Lifetime
-
1996
- 1996-09-12 US US08/713,046 patent/US6545982B1/en not_active Expired - Lifetime
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US3938144A (en) * | 1973-11-28 | 1976-02-10 | Johnson Service Company | Digital multiplexing system remote scanning of a plurality of monitoring points |
US4817080A (en) * | 1987-02-24 | 1989-03-28 | Digital Equipment Corporation | Distributed local-area-network monitoring system |
US4920529A (en) * | 1987-02-27 | 1990-04-24 | Hitachi, Ltd. | Network control method and apparatus therefor |
US5151897A (en) * | 1990-03-20 | 1992-09-29 | Fujitsu Limited | Inter-LAN connection apparatus and inter-LAN connection method |
US5274631A (en) * | 1991-03-11 | 1993-12-28 | Kalpana, Inc. | Computer network switching system |
US5321695A (en) * | 1991-05-01 | 1994-06-14 | Hewlett-Packard Company | Port arrival identification for computer network packets |
Cited By (217)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6078977A (en) * | 1993-11-02 | 2000-06-20 | Micron Electronics, Inc. | Hierarchical bus structure access system |
US6044400A (en) * | 1995-03-25 | 2000-03-28 | Lucent Technologies Inc. | Switch monitoring system having a data collection device using filters in parallel orientation and filter counter for counting combination of filtered events |
US5715250A (en) * | 1995-03-31 | 1998-02-03 | Nec Corporation | ATM-lan connection apparatus of a small scale capable of connecting terminals of different protocol standards and ATM-lan including the ATM-lan connection apparatus |
US20060023676A1 (en) * | 1995-06-01 | 2006-02-02 | Padcom, Inc. | Port routing |
US6826405B2 (en) | 1995-06-01 | 2004-11-30 | Padcom, Inc. | Apparatus and method for intelligent routing of data between a remote device and a host system |
US6198920B1 (en) | 1995-06-01 | 2001-03-06 | Padcom, Inc. | Apparatus and method for intelligent routing of data between a remote device and a host system |
US6418324B1 (en) * | 1995-06-01 | 2002-07-09 | Padcom, Incorporated | Apparatus and method for transparent wireless communication between a remote device and host system |
US6081532A (en) * | 1995-10-20 | 2000-06-27 | International Business Machines Corporation | Bridging apparatus for traffic filtering in communication networks |
US5835696A (en) * | 1995-11-22 | 1998-11-10 | Lucent Technologies Inc. | Data router backup feature |
US5898837A (en) * | 1996-02-23 | 1999-04-27 | Bay Networks, Inc. | Method and apparatus for monitoring a dedicated communications medium in a switched data network |
US6441931B1 (en) | 1996-02-23 | 2002-08-27 | Nortel Networks Limited | Method and apparatus for monitoring a dedicated communications medium in a switched data network |
US6047321A (en) * | 1996-02-23 | 2000-04-04 | Nortel Networks Corporation | Method and apparatus for monitoring a dedicated communications medium in a switched data network |
US6256306B1 (en) * | 1996-08-15 | 2001-07-03 | 3Com Corporation | Atomic network switch with integrated circuit switch nodes |
US5802054A (en) * | 1996-08-15 | 1998-09-01 | 3Com Corporation | Atomic network switch with integrated circuit switch nodes |
US20030012196A1 (en) * | 1996-11-08 | 2003-01-16 | Ramakrishnan Kadangode K. | Promiscuous network monitoring utilizing multicasting within a switch |
US7151772B1 (en) * | 1996-11-08 | 2006-12-19 | At&T Corp. | Method for performing lawfully-authorized electronic surveillance |
US6044401A (en) * | 1996-11-20 | 2000-03-28 | International Business Machines Corporation | Network sniffer for monitoring and reporting network information that is not privileged beyond a user's privilege level |
US20110164618A1 (en) * | 1996-12-16 | 2011-07-07 | Juniper Networks, Inc. | Memory organization in a switching device |
US8477784B2 (en) * | 1996-12-16 | 2013-07-02 | Juniper Networks, Inc. | Memory organization in a switching device |
US20130215886A1 (en) * | 1996-12-16 | 2013-08-22 | Juniper Networks, Inc. | Memory organization in a network device |
US8761180B2 (en) * | 1996-12-16 | 2014-06-24 | Juniper Networks, Inc. | Memory organization in a network device |
US6098120A (en) * | 1997-01-16 | 2000-08-01 | Alps Electric Co., Ltd. | Peripheral sharing system using a bus bridge to emulate peripherals on a first bus to a host on a second bus |
US6205147B1 (en) * | 1997-02-11 | 2001-03-20 | Newbridge Networks Corporation | Virtual network architecture |
US6310876B1 (en) * | 1997-02-14 | 2001-10-30 | Advanced Micro Devices, Inc. | Method and apparatus for managing bin chains in a memory |
US6189042B1 (en) * | 1997-04-09 | 2001-02-13 | Alcatel | LAN internet connection having effective mechanism to classify LAN traffic and resolve address resolution protocol requests |
US6044087A (en) * | 1997-06-30 | 2000-03-28 | Sun Microsystems, Inc. | Interface for a highly integrated ethernet network element |
US6081522A (en) * | 1997-06-30 | 2000-06-27 | Sun Microsystems, Inc. | System and method for a multi-layer network element |
US6088356A (en) * | 1997-06-30 | 2000-07-11 | Sun Microsystems, Inc. | System and method for a multi-layer network element |
US6119196A (en) * | 1997-06-30 | 2000-09-12 | Sun Microsystems, Inc. | System having multiple arbitrating levels for arbitrating access to a shared memory by network ports operating at different data rates |
US6128666A (en) * | 1997-06-30 | 2000-10-03 | Sun Microsystems, Inc. | Distributed VLAN mechanism for packet field replacement in a multi-layered switched network element using a control field/signal for indicating modification of a packet with a database search engine |
US6052738A (en) * | 1997-06-30 | 2000-04-18 | Sun Microsystems, Inc. | Method and apparatus in a packet routing switch for controlling access at different data rates to a shared memory |
WO1999000950A1 (en) * | 1997-06-30 | 1999-01-07 | Sun Microsystems, Inc. | Trunking support in a high performance network device |
US6081512A (en) * | 1997-06-30 | 2000-06-27 | Sun Microsystems, Inc. | Spanning tree support in a high performance network device |
US6049528A (en) * | 1997-06-30 | 2000-04-11 | Sun Microsystems, Inc. | Trunking ethernet-compatible networks |
EP1005739A1 (en) * | 1997-06-30 | 2000-06-07 | Sun Microsystems, Inc. | Shared memory management in a switched network element |
US6016310A (en) * | 1997-06-30 | 2000-01-18 | Sun Microsystems, Inc. | Trunking support in a high performance network device |
US6246680B1 (en) | 1997-06-30 | 2001-06-12 | Sun Microsystems, Inc. | Highly integrated multi-layer switch element architecture |
US6014380A (en) * | 1997-06-30 | 2000-01-11 | Sun Microsystems, Inc. | Mechanism for packet field replacement in a multi-layer distributed network element |
US6094435A (en) * | 1997-06-30 | 2000-07-25 | Sun Microsystems, Inc. | System and method for a quality of service in a multi-layer network element |
US5938736A (en) * | 1997-06-30 | 1999-08-17 | Sun Microsystems, Inc. | Search engine architecture for a high performance multi-layer switch element |
US6044418A (en) * | 1997-06-30 | 2000-03-28 | Sun Microsystems, Inc. | Method and apparatus for dynamically resizing queues utilizing programmable partition pointers |
US5920566A (en) * | 1997-06-30 | 1999-07-06 | Sun Microsystems, Inc. | Routing in a multi-layer distributed network element |
EP1005739A4 (en) * | 1997-06-30 | 2006-03-22 | Sun Microsystems Inc | Shared memory management in a switched network element |
US6061362A (en) * | 1997-06-30 | 2000-05-09 | Sun Microsystems, Inc. | Interface for a highly integrated ethernet network element |
US6347089B1 (en) * | 1997-07-02 | 2002-02-12 | Advanced Communication Devices Corp. | Simplified ethernet frame switching system architecture without local buffer requirement |
US7194005B1 (en) | 1997-08-21 | 2007-03-20 | Adc Telecommunications, Inc. | Circuits and methods for a ring network |
US6331985B1 (en) | 1997-08-21 | 2001-12-18 | Adc Telecommunications, Inc. | Telecommunication network with variable address learning, switching and routing |
US20010048687A1 (en) * | 1997-08-21 | 2001-12-06 | Adc Telecommunications, Inc. | Telecommunication network with variable address learning, switching and routing |
US6154462A (en) * | 1997-08-21 | 2000-11-28 | Adc Telecommunications, Inc. | Circuits and methods for a ring network |
US7065095B2 (en) | 1997-08-21 | 2006-06-20 | Adc Telecommunications, Inc. | Telecommunication network with variable address learning, switching and routing |
US6308218B1 (en) * | 1997-09-17 | 2001-10-23 | Sony Corporation | Address look-up mechanism in a multi-port bridge for a local area network |
US20070206591A1 (en) * | 1997-09-17 | 2007-09-06 | Padcom Holdings, Inc. | Apparatus and method for intelligent routing of data between a remote device and a host system |
US6816490B1 (en) | 1997-09-17 | 2004-11-09 | Sony Corporation | Statistical learning technique in a multi-port bridge for a local area network |
US6751225B1 (en) * | 1997-09-17 | 2004-06-15 | Sony Corporation | Port within a multi-port bridge including a buffer for storing routing information for data packets received in the port |
US6744728B1 (en) | 1997-09-17 | 2004-06-01 | Sony Corporation & Sony Electronics, Inc. | Data pipeline timing optimization technique in a multi-port bridge for a local area network |
US6738384B1 (en) | 1997-09-17 | 2004-05-18 | Sony Corporation | Technique for optimizing cut-through for broadcast and multi-cast packets in a multi-port bridge for a local area network |
US7602782B2 (en) | 1997-09-17 | 2009-10-13 | Padcom Holdings, Inc. | Apparatus and method for intelligent routing of data between a remote device and a host system |
US20100046436A1 (en) * | 1997-09-17 | 2010-02-25 | Padcom Holdings, Inc. | Apparatus and method for intelligent routing of data between a remote device and a host system |
US6049824A (en) * | 1997-11-21 | 2000-04-11 | Adc Telecommunications, Inc. | System and method for modifying an information signal in a telecommunications system |
US6801953B2 (en) | 1997-11-28 | 2004-10-05 | 3Com Corporation | Trunking in stacked communication devices |
US6463479B1 (en) | 1997-11-28 | 2002-10-08 | 3Com Technologies | Apparatus for trunking in stacked communication devices |
US6425015B1 (en) * | 1997-11-28 | 2002-07-23 | 3 Com Technologies | Stacked communication devices and method for port mirroring using modified protocol |
US6230271B1 (en) * | 1998-01-20 | 2001-05-08 | Pilot Network Services, Inc. | Dynamic policy-based apparatus for wide-range configurable network service authentication and access control using a fixed-path hardware configuration |
WO1999046882A3 (en) * | 1998-03-12 | 1999-11-11 | Whale Communications Ltd | Techniques for protection of data-communication networks |
WO1999046882A2 (en) * | 1998-03-12 | 1999-09-16 | Whale Communications Ltd. | Techniques for protection of data-communication networks |
US6901075B1 (en) * | 1998-03-12 | 2005-05-31 | Whale Communications Ltd. | Techniques for protection of data-communication networks |
US6876654B1 (en) * | 1998-04-10 | 2005-04-05 | Intel Corporation | Method and apparatus for multiprotocol switching and routing |
US6392996B1 (en) * | 1998-04-13 | 2002-05-21 | At&T Corp. | Method and apparatus for frame peeking |
US6272133B1 (en) * | 1998-05-21 | 2001-08-07 | Inviscid Networks, Inc. | Packet filtering method |
US6570880B1 (en) | 1998-08-21 | 2003-05-27 | Adc Telecommunications, Inc. | Control data over a ring network |
US6539546B1 (en) | 1998-08-21 | 2003-03-25 | Adc Telecommunications, Inc. | Transport of digitized signals over a ring network |
US6389030B1 (en) | 1998-08-21 | 2002-05-14 | Adc Telecommunications, Inc. | Internet access over a ring network |
US7136645B2 (en) | 1998-10-09 | 2006-11-14 | Netmotion Wireless, Inc. | Method and apparatus for providing mobile and other intermittent connectivity in a computing environment |
US9473925B2 (en) | 1998-10-09 | 2016-10-18 | Netmotion Wireless, Inc. | Method and apparatus for providing mobile and other intermittent connectivity in a computing environment |
US20050223115A1 (en) * | 1998-10-09 | 2005-10-06 | Netmotion Wireless, Inc. | Method and apparatus for providing mobile and other intermittent connectivity in a computing environment |
US8060656B2 (en) | 1998-10-09 | 2011-11-15 | Netmotion Wireless, Inc. | Method and apparatus for providing mobile and other intermittent connectivity in a computing environment |
US20020098840A1 (en) * | 1998-10-09 | 2002-07-25 | Hanson Aaron D. | Method and apparatus for providing mobile and other intermittent connectivity in a computing environment |
US20050223114A1 (en) * | 1998-10-09 | 2005-10-06 | Netmotion Wireless, Inc. | Method and apparatus for providing mobile and other intermittent connectivity in a computing environment |
US9083622B2 (en) | 1998-10-09 | 2015-07-14 | Netmotion Wireless, Inc. | Method and apparatus for providing mobile and other intermittent connectivity in a computing environment |
US7293107B1 (en) | 1998-10-09 | 2007-11-06 | Netmotion Wireless, Inc. | Method and apparatus for providing mobile and other intermittent connectivity in a computing environment |
US7574208B2 (en) | 1998-10-09 | 2009-08-11 | Netmotion Wireless, Inc. | Method and apparatus for providing mobile and other intermittent connectivity in a computing environment |
US8078727B2 (en) | 1998-10-09 | 2011-12-13 | Netmotion Wireless, Inc. | Method and apparatus for providing mobile and other intermittent connectivity in a computing environment |
US7778260B2 (en) | 1998-10-09 | 2010-08-17 | Netmotion Wireless, Inc. | Method and apparatus for providing mobile and other intermittent connectivity in a computing environment |
US7643481B2 (en) | 1999-03-17 | 2010-01-05 | Broadcom Corporation | Network switch having a programmable counter |
US7782891B2 (en) | 1999-03-17 | 2010-08-24 | Broadcom Corporation | Network switch memory interface configuration |
US20040170176A1 (en) * | 1999-03-17 | 2004-09-02 | Broadcom Corporation | Method for handling IP multicast packets in network switch |
US6850521B1 (en) * | 1999-03-17 | 2005-02-01 | Broadcom Corporation | Network switch |
US7366171B2 (en) | 1999-03-17 | 2008-04-29 | Broadcom Corporation | Network switch |
US7720055B2 (en) | 1999-03-17 | 2010-05-18 | Broadcom Corporation | Method for handling IP multicast packets in network switch |
EP1045539A2 (en) * | 1999-04-13 | 2000-10-18 | Alcatel | Monitoring of the transmission quality in a digital telecommunication network |
EP1045539A3 (en) * | 1999-04-13 | 2003-06-25 | Alcatel | Monitoring of the transmission quality in a digital telecommunication network |
US6891801B1 (en) * | 1999-05-05 | 2005-05-10 | Siemens Aktiengesellschaft | Method of operating a data transmission system |
US6717914B1 (en) * | 1999-05-27 | 2004-04-06 | 3Com Corporation | System for probing switched virtual circuits in a connection oriented network |
US20030182431A1 (en) * | 1999-06-11 | 2003-09-25 | Emil Sturniolo | Method and apparatus for providing secure connectivity in mobile and other intermittent computing environments |
US7882247B2 (en) | 1999-06-11 | 2011-02-01 | Netmotion Wireless, Inc. | Method and apparatus for providing secure connectivity in mobile and other intermittent computing environments |
US6907036B1 (en) * | 1999-06-28 | 2005-06-14 | Broadcom Corporation | Network switch enhancements directed to processing of internal operations in the network switch |
US20030198231A1 (en) * | 1999-06-30 | 2003-10-23 | Broadcom Corporation | Frame forwarding in a switch fabric |
US7315552B2 (en) | 1999-06-30 | 2008-01-01 | Broadcom Corporation | Frame forwarding in a switch fabric |
US6952421B1 (en) * | 1999-10-07 | 2005-10-04 | Cisco Technology, Inc. | Switched Ethernet path detection |
US6807182B1 (en) * | 1999-11-02 | 2004-10-19 | 3Com Corporation | Stacked network devices including a protocol engine and distributed trunk ports and method of operating same |
US6904042B2 (en) * | 2000-01-05 | 2005-06-07 | Siemens Aktiengesellschaft | Network coupling device and data network with network coupling device |
US20010006524A1 (en) * | 2000-01-05 | 2001-07-05 | Wilfried Krug | Network coupling device and data network with network coupling device |
US6772267B2 (en) * | 2000-02-18 | 2004-08-03 | Bridgeco Ag | Multi-portal bridge for providing network connectivity |
WO2001063838A3 (en) * | 2000-02-22 | 2002-04-11 | Top Layer Networks Inc | System and method for flow mirroring in a network switch |
WO2001063838A2 (en) * | 2000-02-22 | 2001-08-30 | Top Layer Networks, Inc. | System and method for flow mirroring in a network switch |
US6751219B1 (en) | 2000-04-20 | 2004-06-15 | Aztech Partners, Inc. | Multicast packet duplication at random node or at egress port with frame synchronization |
US20030123458A1 (en) * | 2000-05-26 | 2003-07-03 | Kari Innala | Network for data transfer |
US7583679B2 (en) * | 2000-05-26 | 2009-09-01 | Fulcrum Laboratories Ag | Network for data transfer |
EP1168710A3 (en) * | 2000-06-19 | 2003-08-13 | Broadcom Corporation | Method and device for frame forwarding in a switch fabric |
EP1168710A2 (en) * | 2000-06-19 | 2002-01-02 | Broadcom Corporation | Method and device for frame forwarding in a switch fabric |
US6671739B1 (en) * | 2000-07-10 | 2003-12-30 | International Business Machines Corporation | Controlling network access by modifying packet headers at a local hub |
US6944127B1 (en) * | 2000-08-07 | 2005-09-13 | Bbnt Solutions Llc | System for detecting spurious network traffic |
US6982976B2 (en) * | 2000-08-11 | 2006-01-03 | Texas Instruments Incorporated | Datapipe routing bridge |
US20020018470A1 (en) * | 2000-08-11 | 2002-02-14 | Peter Galicki | Datapipe routing bridge |
US7839802B2 (en) | 2000-08-31 | 2010-11-23 | Verizon Communications Inc. | Methods, apparatus and data structures for segmenting customers using at least a portion of a layer 2 address header or bits in the place of a layer 2 address header |
US8087064B1 (en) | 2000-08-31 | 2011-12-27 | Verizon Communications Inc. | Security extensions using at least a portion of layer 2 information or bits in the place of layer 2 information |
US6850495B1 (en) * | 2000-08-31 | 2005-02-01 | Verizon Communications Inc. | Methods, apparatus and data structures for segmenting customers using at least a portion of a layer 2 address header or bits in the place of a layer 2 address header |
US8243627B2 (en) | 2000-08-31 | 2012-08-14 | Verizon Communications Inc. | Methods, apparatus and data structures for preserving address and service level information in a virtual private network |
US7315554B2 (en) | 2000-08-31 | 2008-01-01 | Verizon Communications Inc. | Simple peering in a transport network employing novel edge devices |
US8264987B2 (en) * | 2000-08-31 | 2012-09-11 | Verizon Communications Inc. | Methods, apparatus and data structures for segmenting customers using at least a portion of a layer 2 address header or bits in the place of a layer 2 address header |
US20090168776A1 (en) * | 2000-08-31 | 2009-07-02 | Verizon Communications Inc. | Methods, apparatus and data structures for preserving address and service level information in a virtual private network |
US8793764B2 (en) | 2000-08-31 | 2014-07-29 | Verizon Patent And Licensing Inc. | Security extensions using at least a portion of layer 2 information or bits in the place of layer 2 information |
WO2002019585A1 (en) * | 2000-08-31 | 2002-03-07 | Verizon Communications Inc. | Methods, apparatus and data structures for segmenting customers using at least a portion of a layer 2 address header or bits in the place of layer 2 address header |
US20090225675A1 (en) * | 2000-08-31 | 2009-09-10 | Verizon Communications Inc. | Methods, apparatus and data structures for segmenting customers using at least a portion of a layer 2 address header or bits in the place of a layer 2 address header |
US20020099827A1 (en) * | 2001-01-22 | 2002-07-25 | Shah Hemal V. | Filtering calls in system area networks |
US7024479B2 (en) | 2001-01-22 | 2006-04-04 | Intel Corporation | Filtering calls in system area networks |
US20020138646A1 (en) * | 2001-03-26 | 2002-09-26 | Tetsuya Tsuboi | Subscriber terminating apparatus and packet processing method |
US7072978B2 (en) * | 2001-03-26 | 2006-07-04 | Fujitsu Limited | Subscriber terminating apparatus and packet processing method |
US20020156916A1 (en) * | 2001-04-23 | 2002-10-24 | The Furukawa Electric Co., Ltd. | Network relay installation, port monitoring method, and computer program for executing this method |
US7644171B2 (en) | 2001-09-12 | 2010-01-05 | Netmotion Wireless, Inc. | Mobile networking system and method using IPv4 and IPv6 |
US20060123079A1 (en) * | 2001-09-12 | 2006-06-08 | Netmotion Wireless, Inc. | Mobile networking system and method |
US20030067913A1 (en) * | 2001-10-05 | 2003-04-10 | International Business Machines Corporation | Programmable storage network protocol handler architecture |
US7072970B2 (en) * | 2001-10-05 | 2006-07-04 | International Business Machines Corporation | Programmable network protocol handler architecture |
US7574597B1 (en) | 2001-10-19 | 2009-08-11 | Bbn Technologies Corp. | Encoding of signals to facilitate traffic analysis |
WO2003061201A1 (en) * | 2002-01-15 | 2003-07-24 | France Telecom | Method for monitoring a communication network and system therefor |
FR2834848A1 (en) * | 2002-01-15 | 2003-07-18 | France Telecom | METHOD FOR OBSERVING A COMMUNICATION NETWORK AND SYSTEM FOR IMPLEMENTING SAID METHOD |
US20050041656A1 (en) * | 2002-01-15 | 2005-02-24 | Nicolas Dubois | Method for monitoring a communication network and system therefor |
US7274698B2 (en) | 2002-03-15 | 2007-09-25 | Broadcom Corporation | Multilevel parser for conditional flow detection in a network device |
US20030174705A1 (en) * | 2002-03-15 | 2003-09-18 | Broadcom Corporation | Multilevel parser for conditional flow detection in a network device |
US20030179754A1 (en) * | 2002-03-20 | 2003-09-25 | Broadcom Corporation | Two stage egress scheduler for a network device |
US7782784B2 (en) | 2003-01-10 | 2010-08-24 | Cisco Technology, Inc. | Port analyzer adapter |
US20040153854A1 (en) * | 2003-01-10 | 2004-08-05 | Andiamo Systems, Inc. | Port analyzer adapter |
US7899048B1 (en) * | 2003-01-15 | 2011-03-01 | Cisco Technology, Inc. | Method and apparatus for remotely monitoring network traffic through a generic network |
US20040181686A1 (en) * | 2003-03-13 | 2004-09-16 | Krause Joel M. | Integrated customer premises equipment device |
US8503437B2 (en) * | 2003-03-13 | 2013-08-06 | Verizon Business Global Llc | Integrated customer premises equipment device |
US8615010B1 (en) * | 2003-05-23 | 2013-12-24 | F5 Networks, Inc. | System and method for managing traffic to a probe |
US7710867B1 (en) * | 2003-05-23 | 2010-05-04 | F5 Networks, Inc. | System and method for managing traffic to a probe |
US8130661B2 (en) * | 2003-08-01 | 2012-03-06 | Opnet Technologies, Inc. | Systems and methods for intelligent probe testing |
US20050094567A1 (en) * | 2003-08-01 | 2005-05-05 | West Ridge Networks | Systems and methods for intelligent probe testing |
US20050053073A1 (en) * | 2003-09-03 | 2005-03-10 | Andiamo Systems, Inc. A Delaware Corporation | Switch port analyzers |
US8165136B1 (en) | 2003-09-03 | 2012-04-24 | Cisco Technology, Inc. | Virtual port based SPAN |
US7474666B2 (en) | 2003-09-03 | 2009-01-06 | Cisco Technology, Inc. | Switch port analyzers |
US8811214B2 (en) | 2003-09-03 | 2014-08-19 | Cisco Technology, Inc. | Virtual port based span |
US8170025B2 (en) | 2003-09-03 | 2012-05-01 | Cisco Technology, Inc. | Switch port analyzers |
US7159051B2 (en) * | 2003-09-23 | 2007-01-02 | Intel Corporation | Free packet buffer allocation |
US20050066081A1 (en) * | 2003-09-23 | 2005-03-24 | Chandra Prashant R. | Free packet buffer allocation |
US9614772B1 (en) | 2003-10-20 | 2017-04-04 | F5 Networks, Inc. | System and method for directing network traffic in tunneling applications |
US20050125424A1 (en) * | 2003-12-05 | 2005-06-09 | Guy Herriott | Decision cache using multi-key lookup |
US7474653B2 (en) * | 2003-12-05 | 2009-01-06 | Hewlett-Packard Development Company, L.P. | Decision cache using multi-key lookup |
US7623535B2 (en) | 2004-09-09 | 2009-11-24 | Cisco Technology, Inc. | Routing protocol support for half duplex virtual routing and forwarding instance |
US20060050653A1 (en) * | 2004-09-09 | 2006-03-09 | James Guichard | Routing protocol support for half duplex virtual routing and forwarding instance |
WO2006031443A3 (en) * | 2004-09-09 | 2006-05-04 | Cisco Tech Ind | Routing protocol support for half duplex virtual routing and forwarding instance |
US20100061281A1 (en) * | 2004-09-09 | 2010-03-11 | Cisco Technology, Inc. | Routing protocol support for half duplex virtual routing and forwarding instance |
US7957408B2 (en) | 2004-09-09 | 2011-06-07 | Cisco Technology, Inc. | Routing protocol support for half duplex virtual routing and forwarding instance |
US20060114914A1 (en) * | 2004-11-30 | 2006-06-01 | Broadcom Corporation | Pipeline architecture of a network device |
US20060114906A1 (en) * | 2004-11-30 | 2006-06-01 | Broadcom Corporation | System and method for maintaining a layer 2 modification buffer |
US8000324B2 (en) | 2004-11-30 | 2011-08-16 | Broadcom Corporation | Pipeline architecture of a network device |
US7583588B2 (en) | 2004-11-30 | 2009-09-01 | Broadcom Corporation | System and method for maintaining a layer 2 modification buffer |
US20060187923A1 (en) * | 2005-02-18 | 2006-08-24 | Broadcom Corporation | Dynamic filter processor key generation based on packet type |
US20060187936A1 (en) * | 2005-02-18 | 2006-08-24 | Broadcom Corporation | Table searching techniques in a network device |
US7409624B2 (en) | 2005-02-18 | 2008-08-05 | Broadcom Corporation | Memory command unit throttle and error recovery |
US20090067446A1 (en) * | 2005-02-18 | 2009-03-12 | Broadcom Corporation | Multi-part parsing in a network device |
US20060187832A1 (en) * | 2005-02-18 | 2006-08-24 | Broadcom Corporation | Filter based range check in a network device |
US7860091B2 (en) | 2005-02-18 | 2010-12-28 | Broadcom Corporation | Multi-part parsing in a network device |
US20070255998A1 (en) * | 2005-02-18 | 2007-11-01 | Broadcom Corporation | Memory command unit throttle and error recovery |
US7254768B2 (en) | 2005-02-18 | 2007-08-07 | Broadcom Corporation | Memory command unit throttle and error recovery |
US7463630B2 (en) | 2005-02-18 | 2008-12-09 | Broadcom Corporation | Multi-part parsing in a network device |
US7948896B2 (en) | 2005-02-18 | 2011-05-24 | Broadcom Corporation | Weighted-fair-queuing relative bandwidth sharing |
US20060187945A1 (en) * | 2005-02-18 | 2006-08-24 | Broadcom Corporation | Weighted-fair-queuing relative bandwidth sharing |
US20060209865A1 (en) * | 2005-02-18 | 2006-09-21 | Broadcom Corporation | Multi-part parsing in a network device |
US20060187825A1 (en) * | 2005-02-18 | 2006-08-24 | Broadcom Corporation | Dynamic color threshold in a queue |
US20060187948A1 (en) * | 2005-02-18 | 2006-08-24 | Broadcom Corporation | Layer two and layer three virtual private network support in a network device |
US20060190777A1 (en) * | 2005-02-18 | 2006-08-24 | Broadcom Corporation | Memory command unit throttle and error recovery |
US20060187924A1 (en) * | 2005-02-18 | 2006-08-24 | Broadcom Corporation | Ingress handling of data in a network device |
US7522622B2 (en) | 2005-02-18 | 2009-04-21 | Broadcom Corporation | Dynamic color threshold in a queue |
US7630306B2 (en) | 2005-02-18 | 2009-12-08 | Broadcom Corporation | Dynamic sharing of a transaction queue |
US20060187826A1 (en) * | 2005-02-18 | 2006-08-24 | Broadcom Corporation | Dynamic sharing of a transaction queue |
US20090190605A1 (en) * | 2005-02-18 | 2009-07-30 | Broadcom Corporation | Dynamic color threshold in a queue |
US20060203824A1 (en) * | 2005-02-18 | 2006-09-14 | Song-Huo Yu | Passing values through a memory management unit of a network device |
US20060187941A1 (en) * | 2005-02-23 | 2006-08-24 | Broadcom Corporation | Self-correcting memory system |
US7802148B2 (en) | 2005-02-23 | 2010-09-21 | Broadcom Corporation | Self-correcting memory system |
US8842127B1 (en) * | 2005-04-25 | 2014-09-23 | Apple Inc. | Text rendering with improved glyph cache management |
CN100411388C (en) * | 2005-05-24 | 2008-08-13 | 华为技术有限公司 | Method for implementing image in exchange system |
US8418233B1 (en) | 2005-07-29 | 2013-04-09 | F5 Networks, Inc. | Rule based extensible authentication |
US9210177B1 (en) | 2005-07-29 | 2015-12-08 | F5 Networks, Inc. | Rule based extensible authentication |
US7787361B2 (en) | 2005-07-29 | 2010-08-31 | Cisco Technology, Inc. | Hybrid distance vector protocol for wireless mesh networks |
US9225479B1 (en) | 2005-08-12 | 2015-12-29 | F5 Networks, Inc. | Protocol-configurable transaction processing |
US8533308B1 (en) | 2005-08-12 | 2013-09-10 | F5 Networks, Inc. | Network traffic management through protocol-configurable transaction processing |
US7660318B2 (en) | 2005-09-20 | 2010-02-09 | Cisco Technology, Inc. | Internetworking support between a LAN and a wireless mesh network |
US20070076730A1 (en) * | 2005-09-20 | 2007-04-05 | Shahriar Rahman | Internetworking support between a LAN and a wireless mesh network |
US20070110024A1 (en) * | 2005-11-14 | 2007-05-17 | Cisco Technology, Inc. | System and method for spanning tree cross routes |
US7869411B2 (en) | 2005-11-21 | 2011-01-11 | Broadcom Corporation | Compact packet operation device and method |
US20070115966A1 (en) * | 2005-11-21 | 2007-05-24 | Broadcom Corporation | Compact packet operation device and method |
US8611222B1 (en) | 2006-02-01 | 2013-12-17 | F5 Networks, Inc. | Selectively enabling packet concatenation based on a transaction boundary |
US8565088B1 (en) | 2006-02-01 | 2013-10-22 | F5 Networks, Inc. | Selectively enabling packet concatenation based on a transaction boundary |
US8559313B1 (en) | 2006-02-01 | 2013-10-15 | F5 Networks, Inc. | Selectively enabling packet concatenation based on a transaction boundary |
US9246772B2 (en) | 2006-07-06 | 2016-01-26 | LiveAction, Inc. | System and method for network topology and flow visualization |
US20090327903A1 (en) * | 2006-07-06 | 2009-12-31 | Referentia Systems, Inc. | System and Method for Network Topology and Flow Visualization |
US9240930B2 (en) | 2006-07-06 | 2016-01-19 | LiveAction, Inc. | System for network flow visualization through network devices within network topology |
US9350622B2 (en) | 2006-07-06 | 2016-05-24 | LiveAction, Inc. | Method and system for real-time visualization of network flow within network device |
US9003292B2 (en) * | 2006-07-06 | 2015-04-07 | LiveAction, Inc. | System and method for network topology and flow visualization |
US9106606B1 (en) | 2007-02-05 | 2015-08-11 | F5 Networks, Inc. | Method, intermediate device and computer program code for maintaining persistency |
US9967331B1 (en) | 2007-02-05 | 2018-05-08 | F5 Networks, Inc. | Method, intermediate device and computer program code for maintaining persistency |
US8238344B1 (en) * | 2007-03-30 | 2012-08-07 | Juniper Networks, Inc. | Multicast load balancing |
US8798072B2 (en) | 2007-03-30 | 2014-08-05 | Juniper Networks, Inc. | Multicast load balancing |
US9832069B1 (en) | 2008-05-30 | 2017-11-28 | F5 Networks, Inc. | Persistence based on server response in an IP multimedia subsystem (IMS) |
US9130846B1 (en) | 2008-08-27 | 2015-09-08 | F5 Networks, Inc. | Exposed control components for customizable load balancing and persistence |
Also Published As
Publication number | Publication date |
---|---|
DE69434330D1 (en) | 2005-05-19 |
EP0710415A1 (en) | 1996-05-08 |
EP0710415A4 (en) | 2002-03-27 |
EP0710415B1 (en) | 2005-04-13 |
US6545982B1 (en) | 2003-04-08 |
DE69434330T2 (en) | 2006-03-09 |
JPH09500774A (en) | 1997-01-21 |
ATE293327T1 (en) | 2005-04-15 |
US5515376A (en) | 1996-05-07 |
JP3335358B2 (en) | 2002-10-15 |
WO1995003659A1 (en) | 1995-02-02 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US5610905A (en) | Communication apparatus and methods | |
US5757795A (en) | Method and apparatus for hashing addresses in a network switch | |
US6018526A (en) | Bridge device with self learning between network media and integrated circuit and method based on the same | |
US6308218B1 (en) | Address look-up mechanism in a multi-port bridge for a local area network | |
US6539022B1 (en) | Network device with multicast forwarding data | |
US6181702B1 (en) | Method and apparatus for capturing source and destination traffic | |
CN101156408B (en) | Network communications for operating system partitions | |
JP3621646B2 (en) | Communication network with variable address learning, switching and routing | |
US6172980B1 (en) | Multiple protocol support | |
US5884043A (en) | Conversion technique for routing frames in a source route bridge network | |
US5805816A (en) | Network packet switch using shared memory for repeating and bridging packets at media rate | |
US6256306B1 (en) | Atomic network switch with integrated circuit switch nodes | |
JP4068166B2 (en) | Search engine architecture for high performance multilayer switch elements | |
US6944130B1 (en) | Method and apparatus for determining a layer 2 path in a switched network | |
US6091725A (en) | Method for traffic management, traffic prioritization, access control, and packet forwarding in a datagram computer network | |
US20030185152A1 (en) | Remote monitoring of switch network | |
US6829651B1 (en) | Local MAC address learning in layer 2 frame forwarding | |
JPH06511615A (en) | Method and apparatus for maintaining packet sequence within a packet transmission system | |
JPH04265037A (en) | Distance vector routing method and device on link between two spot of datagram | |
EP0603443A1 (en) | Token star bridge | |
US6625146B1 (en) | Method and apparatus for operating a network switch in a CPU-less environment | |
US6785738B1 (en) | ARP packet to preserve canonical form of addresses | |
US7474660B1 (en) | MAC address extension to maintain router information in source routed computer networks | |
WO1997010661A1 (en) | Method and apparatus for filtering and forwarding messages in a computer network using a last source address | |
US5905712A (en) | Data communication network |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
CC | Certificate of correction | ||
AS | Assignment |
Owner name: FORE SYSTEMS TECHNOLOGY, INC., PENNSYLVANIA Free format text: MERGER;ASSIGNOR:ALANTEC CORPORATION;REEL/FRAME:009883/0994 Effective date: 19980324 |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
AS | Assignment |
Owner name: MARCONI COMMUNICATIONS TECHNOLOGY INC, PENNSYLVANI Free format text: CORRECTION TO COVERSHEET;ASSIGNOR:FORE SYSTEMS TECHNOLOGY INC;REEL/FRAME:014455/0755 Effective date: 20000117 |
|
FPAY | Fee payment |
Year of fee payment: 8 |
|
AS | Assignment |
Owner name: MARCONI INTELLECTUAL PROPERTY (RINGFENCE) INC., PE Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MARCONI COMMUNICATIONS TECHNOLOGY, INC.;REEL/FRAME:015766/0523 Effective date: 20040713 |
|
AS | Assignment |
Owner name: ERICSSON AB,SWEDEN Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MARCONI INTELLECTUAL PROPERTY (RINGFENCE) INC.;REEL/FRAME:018047/0028 Effective date: 20060101 Owner name: ERICSSON AB, SWEDEN Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MARCONI INTELLECTUAL PROPERTY (RINGFENCE) INC.;REEL/FRAME:018047/0028 Effective date: 20060101 |
|
FPAY | Fee payment |
Year of fee payment: 12 |
|
REMI | Maintenance fee reminder mailed |