WO2004047377A2 - Forewarding system with multiple logical sub-system functionality - Google Patents
Forewarding system with multiple logical sub-system functionality Download PDFInfo
- Publication number
- WO2004047377A2 WO2004047377A2 PCT/CA2003/001711 CA0301711W WO2004047377A2 WO 2004047377 A2 WO2004047377 A2 WO 2004047377A2 CA 0301711 W CA0301711 W CA 0301711W WO 2004047377 A2 WO2004047377 A2 WO 2004047377A2
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- mapping
- next hop
- hop interface
- interfaces
- data element
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/56—Routing software
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/58—Association of routers
- H04L45/586—Association of routers of virtual routers
Definitions
- the present invention • relates generally to data communications forwarding systems and, more particularly, to a data forwarding apparatus capable of exhibiting the functionality of multiple interconnected logical forwarding sub-systems while maintaining efficient usage of its communication interfaces.
- Modern data communications forwarding systems typically have functionality that is partitioned into a "control plane” and a “data plane.”
- the control plane is typically implemented using hardware that can execute complex software written in general-purpose languages to implement control protocols and operator interfaces.
- the data plane is implemented in special-purpose hardware, with forwarding and processing decisions implemented in different ways on different systems. Even when the data plane processing is implemented in a general-purpose CPU, the data plane is typically treated as a separate entity and is optimized for efficient forwarding.
- Examples of forwarding systems having functionality partitioned into a control plane and a data plane include IP routers, layer-2 switches of various types (e.g., Ethernet, Frame Relay (FR) , Asynchronous Transfer Mode (ATM), Multi- Protocol Label Switching (MPLS) ) , circuit switches of various types (e.g., DACS, Synchronous Optical Network (SONET) Add- Drop Multiplexers (ADMs), Optical Cross-Connects (OXCs) ) , wireless telephony equipment, equipment that performs combinations of the above operations and most other programmable communications equipment that performs a forwarding function.
- IP routers layer-2 switches of various types (e.g., Ethernet, Frame Relay (FR) , Asynchronous Transfer Mode (ATM), Multi- Protocol Label Switching (MPLS) ) , circuit switches of various types (e.g., DACS, Synchronous Optical Network (SONET) Add- Drop Multiplexers (ADMs), Optical Cross-Connects (OXCs)
- Examples of processing accomplished by the data plane include label lookup (MPLS, FR, ATM, X.25), source lookup (Ethernet, Internet Protocol (IP)), destination lookup (Ethernet, IP) , egress interface lookup (all switching types) , egress sub-interface lookup (most switching types) , encapsulation (most switching types) , filtering, metering, statistics accumulation and sampling.
- label lookup MPLS, FR, ATM, X.25
- source lookup Ethernet, Internet Protocol (IP)
- destination lookup Ethernet, IP
- egress interface lookup all switching types
- egress sub-interface lookup egress sub-interface lookup
- encapsulation most switching types
- a service provider may wish to provide a router for each customer without actually installing a separate piece of equipment for each customer.
- a forwarding system > that performs two functions (e.g., IP routing and Frame Relay switching) it may be easier to implement logically separate . control planes for the two functions.
- the present invention is applicable to forwarding systems of the type where data is logically processed first by the data plane of one of a plurality of logical forwarding subsystems, and then by the data plane of another of the subsystems.
- the present invention is also applicable when the data planes of three or more logical forwarding sub-systems must sequentially process the same data.
- the present invention relates to creation of a consolidated mapping function that is based on the individual mapping functions that specify the forwarding behaviour of the individual logical routers. This concept enables efficient shared data-plane operation in a forwarding system that instantiates multiple logical forwarding sub-systems. The efficiency arises when the same data is processed by more than one logical forwarding sub-system in the same physical forwarding system.
- the concept is applicable to systems with centralized . or distributed data planes. It is also applicable to systems with centralized or distributed control planes .
- the invention provides a method of generating a mapping for use by a data forwarding entity having a plurality of communication interfaces.
- the method includes receiving a first mapping specifying a next hop interface for data elements received at the communication interfaces, wherein at least one next hop interface belongs
- the method also includes receiving a second mapping specifying a second next hop interface for certain data elements for which the next hop interface specified by the first mapping belongs to the set of logical interfaces, wherein at least one second next hop interface belongs to the plurality of communication interfaces. Further, the method includes generating a consolidated mapping from the first and second mappings by replacing each portion of the first mapping that specifies a next hop interface belonging to the set of logical interfaces by a corresponding portion of the second mapping that specifies a second next hop interface.
- the present invention may be summarized as a data forwarding apparatus.
- the data forwarding apparatus includes a plurality of ' communication interfaces at which data elements are received by the apparatus, a memory and a processing entity connected to the communication interfaces and to the memory.
- the memory stores a first mapping, a second mapping and a consolidated mapping.
- the first mapping specifies a next hop interface for data elements received at the communication interfaces, wherein at least one next hop interface belongs to a set of logical interfaces.
- the second mapping specifies a second next hop interface for certain data elements for which the next hop interface specified by the first mapping belongs to the set of logical interfaces, wherein at least one second next hop interface belongs to the plurality of communication interfaces.
- the consolidated mapping specifies a next hop interface for data elements received at the communication interfaces, wherein no next hop interface specified by the consolidated mapping belongs to the set of logical interfaces.
- the processing entity generates the consolidated mapping from the first and .second mappings by replacing each portion of the first mapping that specifies a next hop interface belonging to the set of logical interfaces by a corresponding portion of the second mapping that specifies a second next hop interface. Additionally, the processing entity accesses the consolidated mapping to determine a next hop interface associated with each data element received at the communication interfaces and forwards the received data element to the next hop interface determined at the accessing step.
- the present invention may be summarized as a memory for storing data for access by an application program being executed on a data processing system having a plurality of communication interfaces.
- the memory includes a data structure stored in the memory that includes information regarding a first mapping specifying a next hop interface for data elements received at the communication interfaces, wherein at least one next hop interface belongs to a set of logical interfaces.
- the data structure also includes information regarding a second mapping specifying a second next hop interface for certain data elements for which the next hop interface specified by the first mapping belongs to the set of logical interfaces, wherein at least one second next hop interface belongs to the plurality of communication interfaces.
- the data structure includes information regarding a consolidated mapping created from the first and second mappings by replacing each portion of the first mapping that specifies a next hop interface belonging to the set of logical interfaces by a corresponding portion of the second mapping that specifies a second next hop interface.
- the present invention is also applicable to a multicast environment and may be summarized as a method of generating a mapping for use by a data forwarding entity having a plurality of communication interfaces.
- the method includes receiving a first mapping specifying a next hop interface for data elements received at the communication interfaces, wherein at least one of the plurality of next hop interfaces specified for at least one of the certain ones of the received data elements belongs to a set of logical interfaces.
- the method also includes receiving a second mapping specifying a plurality of second next hop interfaces for certain data elements for which the next hop interface specified by the first mapping belongs to the set of logical interfaces, wherein at least one second next hop interface belongs to the plurality of communication interfaces.
- the method includes generating a consolidated mapping from the first and second mappings by replacing at least one portion of the first mapping that specifies a next hop interface belonging to the set of logical interfaces by a corresponding portion of the second mapping that specifies a plurality of second next hop interfaces.
- the present invention may also be summarized as computer- readable media tangibly embodying a program of instructions executable by a data forwarding apparatus to perform the above described method.
- Fig. 1 shows a pair of routers to be replaced by a single router in accordance with an embodiment of the present invention
- Fig. 2A shows a router in accordance with an embodiment of the present invention, which is provided with a pair of mappings
- Fig. 2B shows one manner of creating a consolidated mapping from the mappings provided to the router of Fig. 2A
- Fig. 2C shows another manner of creating a consolidated mapping from the mappings provided to the router of Fig. 2A;
- Fig. 3 shows an example physical implementation of a router in accordance with an embodiment of the present invention
- Fig. 4A shows a router in accordance with another embodiment of the present invention, which is provided with a pair of mappings ;
- Fig. 4B shows one manner of creating a partial consolidated mapping from the mappings provided to the router of Fig. 4A;
- Fig. 4C shows another manner of creating a partial consolidated mapping from the mappings provided to the router of Fig. 4A.
- a cluster of data communications forwarding systems (hereinafter referred to simply as a "cluster" 10) to be replaced by a single data communications forwarding system of the present invention.
- the cluster 10 includes two data communications forwarding systems, namely a first router Rl and a second router R2.
- the components of the cluster 10 may be data communications systems other than routers and, furthermore, the number of components may be greater than two, and furthermore, the components need not be of the same type.
- IP routers for example, IP routers, layer-2 switches of various types (e.g., Ethernet, Frame Relay (FR) , Asynchronous Transfer Mode (ATM) , Multi-Protocol Label Switching (MPLS) ) , circuit switches of various types (e.g., DACS, Synchronous Optical Network (SONET) Add-Drop Multiplexers (ADMs) , Optical Cross-Connects (OXCs) ) , wireless telephony equipment, equipment that performs combinations of the above operations and most other programmable communications equipment that performs a forwarding function.
- IP routers e.g., IP, IP routers, layer-2 switches of various types (e.g., Ethernet, Frame Relay (FR) , Asynchronous Transfer Mode (ATM) , Multi-Protocol Label Switching (MPLS) ) , circuit switches of various types (e.g., DACS, Synchronous Optical Network (SONET) Add-Drop Multiplexers (ADMs) , Optical
- data element is intended to encompass an element of packet-switched data (e.g., a packet or datagram) or an element of circuit- switched data (e.g., the data contained in a time slot), depending on the context in which it is described.
- packet is not to be construed in a limitative fashion. Rather, this term is intended to broadly encompass any statistically multiplexed unit of information.
- packet applies to data forwarding entities that perform either or both packet- switching and circuit-switching functions.
- the cluster 10 includes a plurality of extra-cluster interfaces x, y, z, w, as well as a plurality of intra-cluster interfaces a, b, c, d.
- the extra- cluster interfaces x, y, z, w receive data elements from outside the cluster 10 and also forward routed data elements to destinations outside of the cluster 10.
- extra-cluster interfaces x, y, z, w are connected to destinations 1.3.2.7, 1.5.7.9, 1.2.3.4, 2.4.6.8, respectively.
- the intra-cluster interfaces a, b, c, d serve to connect the routers Rl and R2 to one another.
- intra-cluster interface a on router Rl is connected to intra-cluster interface c on router R2, while intra-cluster interface b on router Rl is connected to intra- cluster interface d on router R2.
- the number- of extra- cluster interfaces and intra-cluster interfaces is shown by way of illustration only; it should be understood that the data communications forwarding system of the present invention may replace a cluster 10 having a wide range of extra-cluster interfaces and intra-cluster interfaces.
- Each of the routers Rl, R2 typically has a control plane for storing a mapping that defines the forwarding behaviour of the particular router in question.
- Ml and M2 represent the mappings associated with the routers Rl and R2, respectively.
- mapping Ml will define a mapping amongst the interfaces x, y, a and b
- mapping M2 will define a mapping amongst the interfaces z, w, c and d. More specifically, mappings Ml and M2 will specify a next hop interface for each data element received at' one of its interfaces.
- the next hop interface may be looked up as a function of a source of the data element (identified by an IP address, for example), a destination of the data element (e.g., identified by an IP address, for example), a priority level associated with the data element, the identity of the interface at which the data element arrives, a connection state (e.g., for connection-oriented switching) or some other characteristic of the received data element.
- a data element arriving at one of the extra-cluster interfaces x, y, z, w will be forwarded either directly out through one of the extra-cluster interfaces on the same router or it will have to travel to the other router of the cluster 10, from which' it will emerge at one of the extra-cluster interfaces of that other router.
- a data element arriving at interface x will either exit the router Rl through interface y (or x, although this is rare) , or it will travel to router R2 via one of the intra-cluster interfaces a, b.
- the data element will then emerge from router R2 via one of the extra- cluster interfaces z, w.
- the behaviour of data elements from the point of view of entering and leaving the cluster 10 via the extra-cluster interfaces x, y, z, w needs to be replicated.
- a data communications forwarding system 200 in accordance with an embodiment of the present invention.
- the data communications forwarding system 200 is a router, although it may assume other roles in accordance with the operational requirements of the invention.
- the single router 200 is functionally equivalent to the cluster 10 described herein above with reference to Fig. 1.
- the routers Rl and R2 although they do not physically exist, are manifested within the router 200 in a logical form and will hereinafter be referred to as "logical routers" for convenience.
- the router 200 has a data plane that receives and forwards data elements in accordance with a mapping maintained in a control plane. Data elements are received on a plurality of communication interfaces x, y, z, w corresponding to the extra-cluster interfaces x, y, z, w, of the cluster 10. However, the router 200 does not possess any communication interfaces to match the intra-cluster interfaces a, b, c, d of the cluster 10. Rather, these former intra-cluster interfaces are logical in nature and are denoted Va, Vb, Vc, Vd, in this example. Thus, it will be apparent that the router 200 does not require a greater number of communication interfaces than the number of extra-cluster interfaces of the cluster 10 it is designed to replace.
- the communication interfaces x, y, z, w may reside on a plurality of line cards 220, which include processors and other hardware.
- the data plane of ' the router 200 may also physically include a switch fabric 230 to which the line cards 220 connect and which allows data elements to travel (i.e., "hop") from one line card to another.
- the line cards 220 on which are located communication interfaces x and y are associated with logical
- router Rl solid blocks
- the line cards 220 on which are located communication interfaces z and w are associated with logical router R2 (striped blocks) .
- the partitioning of physical resources amongst logical routers need not be on a per-line-card basis. In all cases of the router 200, however, no line cards or other physical resources are associated with the logical interfaces Va, Vb, Vc, Vd.
- the control plane of the router 200 of the present invention maintains a mapping M3 which defines the forwarding behaviour of the router 200.
- the control plane may be distributed amongst the line cards 220 or it may be implemented on a set of control cards provided separately within the chassis of the router 200.
- the mapping M3 specifies a next hop interface for each data element received at one of the communication interfaces x, y, z, w. Since the router 200 is designed to replace the routers Rl and R2, the mapping M3 must bear some relation to the mappings Ml and M2. In fact, mappings Ml and M2, which are provided to the router 200, contain all of the information needed to create mapping M3.
- mappings Ml and M2 involve the (no longer existent) intra-cluster interfaces and thus the mapping M3 must differ from the mappings Ml and M2.
- One way of consolidating the mappings Ml and M2 to arrive at the mapping M3 is now described in greater detail.
- the mapping M3 is created by a consolidation engine 240, which may be implemented as a software component of the control plane.
- the consolidated mapping M3 specifies a mapping function for the physical data plane function that is equivalent to a "convolution" of the mapping functions specified by the mappings Ml and M2.
- the consolidated mapping M3, applied once, will have the same result (as far as external operation is concerned) as applying the appropriate individual mappings Ml and M2 in the appropriate sequence.
- the forwarding action specified by the mapping Ml depends on the destination of each data element received at one of the communication interfaces x, y, z, w.
- the data plane obtains knowledge of the destination of each received data element from a header of that data element.
- the forwarding action does not depend on the communication interface at which a data element is received, although it should be understood that in other cases (see Figs. 4A through 4C) , the forwarding action may indeed be dependent on the communication interface at which a data element is received and possibly on other characteristics of the received data element, such as its priority level, age, etc.
- mapping Ml specifies that a data element with destination 1.3.2.7 is to be forwarded to communication interface x, a data element with destination 1.5.7.9 is to be forwarded to communication interface y, a data element with destination 1.2.3.4 is intended to be forwarded to logical interface Va, and a data element with destination 2.4.6.8 is intended to be forwarded to logical interface Vb.
- mapping M2 specifies that a data element with destination 1.2.3.4 is to be forwarded to communication interface z, a data element with destination 2.4.6.8 is to be forwarded to communication interface w, a data element with destination 1.3.2.7 is intended to be forwarded to logical interface Vc, and a data element with destination 1.5.7.9 is intended to be forwarded to logical interface Vd.
- the consolidated mapping M3 can be created by taking a basic portion of the mapping Ml and consolidating it with an augmented portion of the mapping M2.
- the basic portion of the mapping Ml denoted Ml B as ⁇ c is taken to be the entire mapping Ml
- the augmented portion of the mapping M2, denoted M2 AUG refers only to that portion of the mapping M2 in which a next hop interface is provided for those data elements that would be routed to logical router R2 by logical router Rl .
- M2 AOG includes only the portion of the mapping M2 that specifies the next hop interface for data elements having a destination 1.2.3.4 or a destination 2.4.6.8, since these are the only data elements that would have been forwarded to logical router R2 by logical router Rl if these logical routers were implemented separately.
- M1 BASIC which specify a forwarding action towards logical router R2
- M2 ADG that continues the forwarding process
- mapping M3 specifies that a data element with destination 1.3.2.7 is to be forwarded to communication interface x (as in Ml B as ⁇ c) r a data element with destination 1.5.7.9 is to be forwarded to communication interface y (as in MI BASIC ) - a data element with destination 1.2.3.4 is to be forwarded to communication interface z (as in M2 AUG ) I and a data element with destination 1.5.7.9 is to be forwarded to communication interface w (as in M1 AUG ) • '
- the mapping M3 is a single-next-hop mapping function, which means that a data element is routed immediately to the same communication interface after one lookup as it would have been routed to if it had followed multiple passes (through the mappings Ml and M2) .
- mapping M3 is identical to the net forwarding behaviour of the cluster 10 from the point of view of the communication interfaces x, y, . z, w. Furthermore, no communication interfaces need to be reserved for intra-router communications. Moreover, no data element will ever be "forwarded" by the router 200 to a logical interface via the data plane, which is consistent with the notion that the logical interfaces Va, Vb, Vc, Vd do not exist as physical entities.
- the consolidated mapping M3 can be created by taking a basic portion of the mapping M2 and consolidating it with an augmented portion of the mapping Ml.
- the basic portion of the mapping M2, denoted M2 B As ⁇ c is taken to be the entire mapping M2
- the augmented portion of the mapping Ml denoted MI AUG refers only to that portion of the mapping Ml in which a next hop interface is provided for those data elements that would be routed to logical router Rl by logical router R2.
- M1 AUG includes only the portion of the mapping Ml that specifies the next hop interface for data elements having a destination 1.3.2.7 or a destination 1.5.7.9, since these are the only data elements that would have been forwarded to logical router Rl by logical router R2 if these logical routers were implemented separately.
- M2 BA s ⁇ c which specify a forwarding action towards logical router Rl
- M1 AUG that continues the forwarding process
- a mapping Ml' is provided, which specifies a next hop interface to which to forward a received data element based not only on the destination of the data element but also on the basis of the communication interface at which the data element is received.
- some of the communication interfaces are adapted to communicate with the control plane. This may be useful ⁇ in operation, administration and maintenance functions. For example, the ability to transmit data elements to the control plane may be used to perform error detection and / or correction or to transmit control information or even changes to the mappings Ml and M2. ' ⁇ .
- data plane can obtain, as before, the destination of a received data element from the data element's header.
- the data plane can be assumed to have knowledge of the communication interface at which the data element is received, since it processes incoming ' • data elements.
- mappings Ml' and M2' are associated with logical routers Rl and R2, certain portions of each mapping will refer to interfaces that are physically non-existent, namely, logical interfaces Va, Vb, Vc, Vd.
- mapping Ml' specifies that a data element with destination 1.2.3.4 and received at communication interface x is intended to be forwarded to logical interface Va, a data element with destination 1.2.3.4 and received at communication interface y is intended to be forwarded to logical interface Vb, a data element with destination 1.2.3.4 and "arriving" at logical interface Va is intended to be forwarded to logical interface Vb and a data element with destination 1.2.3.4 and "arriving" at logical interface Vb is intended to be forwarded to logical interface Va.
- a data element with destination 1.3.2.7 and received at communication interface y is to be forwarded to communication interface x
- a data element with destination 1.3.2.7 and received at communication interface x is to be forwarded to the control plane (because it should never have entered the router 200)
- a data element with destination 1.3.2.7 and "arriving" at either logical interface Va or logical interface Vb is to be forwarded to communication interface x.
- a data element with destination 1.5.7.9 and received at communication interface x is to be forwarded to communication interface y
- a data element with destination 1.5.7.9 and received at communication interface y is to be forwarded to the control plane (because it should never have entered the router 200) and a data element with destination 1.5.7.9 and "arriving" at either logical interface Va or logical interface Vb is to be forwarded to communication interface y.
- a data element with destination 2.4.6.8 and received at communication interface x is intended to be forwarded to logical interface Va
- a data element with destination 2.4.6.8 and received at communication interface y is intended to be forwarded to logical interface Vb
- a data element with destination 2.4.6.8 and “arriving" at logical interface Va is intended to be forwarded to logical interface Vb
- a data element with destination 2.4.6.8 and "arriving" at logical interface Vb is intended to be forwarded to logical interface Va.
- mapping M2' specifies that a data element with destination 1.2.3.4 and "arriving" at logical interface Vc or logical interface Vd is to be forwarded to communication interface z, a data element with destination 1.2.3.4 and received at communication interface w is to be forwarded to communication interface z, a data element with destination 1.2.3.4 and received at communication interface z is to be .forwarded to the control plane (because it should never have entered the router 200) , a data element with destination 1.3.2.7 and arriving at communication interface z is intended to be forwarded to logical interface Vc, a data element with destination 1.3.2.7 and received at communication interface w is intended to be forwarded to logical interface Vd, a data element with destination 1.3.2.7 and “arriving" at logical interface Vc is intended tio be forwarded to logical interface Vd, a data element with destination 1.3.2.7 and “arriving" at logical interface Vd is intended to be forwarded to logical interface Vc, a data element with destination 1.
- the consolidated mapping M3' consists of two halves, the first half dealing with data elements received by the router
- mapping M3' ⁇ is illustrated in Fig. 4B
- mapping M3' ⁇ - is illustrated in Fig. 4C.
- mapping M3' is itself a consolidated mapping and its construction falls within the scope of the present invention.
- mapping M3' ⁇ is constructed by taking a basic portion of the mapping Ml', denoted MI' ⁇ BASIC - which relates to data elements received at the communication interfaces x and y, and consolidating it with an augmented portion of the mapping M2' , denoted M2' ⁇ AUG which relates to the portion of the mapping M2' in which a next hop interface is provided for those data elements that would have been routed to logical router R2 by logical router Rl.
- M2' ⁇ AUG includes only the portion of the mapping M2' that specifies the next hop interface for data elements "arriving" at logical interface Vc or logical interface Vd, since these are the only data elements that would have been forwarded to logical router R2 by logical router Rl if these logical routers were implemented separately.
- MI' ⁇ BASIC which specify a forwarding action towards logical router R2
- M2' ⁇ AOG that continues the forwarding process
- mapping M3' ⁇ specifies that a data element with destination 1.2.3.4 and received at communication interface x or communication interface y will be forwarded to communication interface z (combination of Ml' ⁇ BA s ⁇ c and
- ⁇ at communication interface y will be forwarded to communication interface .
- mapping M3' ⁇ is a single-next- hop mapping function, which means that a data element is routed immediately to the same communication interface after one lookup as it would have been routed to if it had followed multiple passes (through the mappings MI' ⁇ B ASIC and M2' ⁇ A ⁇ G ) •
- the net effect of the mapping M3' ⁇ is identical to the net forwarding behaviour of the cluster 10 from the point of view of data elements received at the communication interfaces x and y.
- no communication interfaces need to be reserved for intra-router communications.
- no data element will ever be "forwarded" by the router 200 to a logical interface via the data plane, which is consistent with the notion that the logical interfaces Va, Vb, Vc, Vd, do not exist as physical entities.
- mapping M3' ⁇ - is constructed by taking a basic portion of the mapping M2' , denoted M2' ⁇ - BA siC which relates to data elements received at the communication interfaces x and y, and consolidating it with an augmented portion of the mapping Ml', denoted M1' ⁇ - A T JG , which relates to the portion of the mapping Ml' in which a next hop interface is provided for those data elements that would have been routed to logical router Rl by logical router R2.
- M1' ⁇ - AUG includes only the portion of the mapping Ml' that specifies the next hop interface for data elements "arriving" at logical interface Va or logical interface Vb, since these are the only data elements that would have been forwarded to logical router Rl by logical router R2 if these logical routers were implemented separately.
- M2' ⁇ - BAS ⁇ c which specify a forwarding action towards logical router Rl with a corresponding portion of M1' ⁇ - AUG that continues the forwarding process, one has created the mapping M3' ⁇ -.
- mapping M3' ⁇ - specifies that a data element with destination 1.3.2.7 and received at communication interface z or communication interface w will be forwarded to communication interface x (combination of M2' ⁇ - B A SIC and M1' ⁇ - AUG ) data element with destination 1.2.3.4 and received at communication interface w will be forwarded to communication interface z (as per M2' ⁇ - BASIC ) / a data element with destination 1.2.3.4 and received at communication interface z will be forwarded to the control plane (as per M2' ⁇ -BASIC) ⁇ a data element with destination 2.4.6.8 and received at communication interface z will be forwarded to communication interface w (as per M2' ⁇ - B ASI C ) a data element with destination 2.4.6.8 and received at communication interface w will be forwarded to the control plane (as per M2' ⁇ - BASIC ) and a data element with destination 1.5.7.9 and received at communication interface z or communication interface w will be forwarded to
- mapping M3' ⁇ - is a single-next- hop mapping function, which means that a data element is routed immediately to the same communication interface after one lookup as it would have been routed to if it had followed multiple passes (through the mappings M2' «- BASIC and M1' ⁇ - AUG ) .
- the net effect of the mapping M3' ⁇ - is identical to the net forwarding behaviour of the cluster 10 from the point of view of data elements received at the communication interfaces z and w.
- no communication interfaces need to be reserved for intra-router communications.
- no data element will ever be "forwarded" by the router 200 to a logical interface via the data plane, which is consistent with the notion that the logical interfaces Va, Vb, Vc, Vd do not exist as physical entities .
- mappings M3' ⁇ and M3' ⁇ - into a single mapping M3' , which would specify the same net forwarding behaviour as the cluster 10 from the point of view of data elements received at any of the communication interfaces x, y, z, w.
- Those skilled in the art will appreciate that there are many ways to implement a consolidated mapping that has the same overall effecti as multiple mappings for multiple routers, and the utility of the consolidated mapping concept is independent of the precise implementation.
- the result of applying the consolidated mapping to the physical data plane is that each data element is processed once by the data plane to produce the same result that would be produced if the appropriate logical router mappings were applied sequentially.
- a received data element may undergo other actions by the router that are .composite actions based on actions specified for the two logical routers Rl and R2.
- the final action taken by the router 200 with respect to a given data element will be a function of the path through the cluster 10 that would have been followed if the logical routers had been implemented separately.
- some actions are independent of subsequent actions, other actions are superseded by subsequent actions,
- a consolidated mapping function is useful for any data plane architecture, but it is particularly useful in modern highspeed switching ' equipment with ' distributed data plane processing.
- partitioning of the physical data plane to permit distribution is independent of the partitioning of the system into logical data communications forwarding systems.
- the consolidated mapping concept applies to the data plane as a whole.
- partition the processing it is possible to partition the processing to align it to the logical switch partitioning, or to the data plane partitioning, or to both.
- the precise implementation will depend on the operational requirements of ,the system, as determined by those of ordinary skill in the art.
- mapping function that can be applied to the logical interfaces. This is merely a specific instance of a general phenomenon whereby different interface types have different constraints. To the extent that these capabilities differ from the capabilities of a physical interface between physical switches, the functionality of the physical system instantiating the logical switches will differ from an equivalent collection of interconnected physical switches.
- the present invention may be applied to a multicast environment.
- multicast means the receipt of a single unit of data that results in its replication and transmission to more than one egress point. This is a generalization of the way the term is used with respect to the Internet Protocol (IP) .
- IP Internet Protocol
- each mapping function for each of the logical routers specifies a one-to-many mapping (a multicast "tree") of the ingress space, and the consolidated mapping specifies the convolved mapping, which will also be a one-to-many mapping.
- the convolution follows each "branch" of the multicast tree.
- control planes of the logical routers Rl and R2 will be implemented separately within the single physical router 200, with control signaling passing among the individual control planes.
- present invention can also be applied to the control planes of the logical routers Rl, R2 in addition to being applied to their data planes, which would effectively result in the creation of a single "consolidated" control plane.
- processors used in the data plane or the control plane may be each implemented as an arithmetic and logic unit (ALU) having access to a code memory (not shown) which stores program instructions for the operation of the ALU.
- the program instructions could be stored on a medium which is fixed, tangible and readable directly by the processor (e.g., removable diskette, CD-ROM, ROM, or fixed disk) , or the program instructions could be stored remotely but transmittable to the processor via a modem or other interface device (e.g., a communications adapter) connected to a network over a transmission medium.
- the transmission medium may be either a tangible medium (e.g., optical or analog communications lines) or a medium implemented using wireless techniques (e.g., microwave, infrared or other transmission schemes) .
- program instructions stored in the code memory can be compiled from a high level program written in a number of programming languages for use with many computer architectures or operating systems.
- the high level program may be written in assembly language, while other versions may be written in a procedural programming language (e.g., "C") or an object oriented programming language (e.g., "C++” or "JAVA").
- processors may be implemented as pre-programmed hardware or firmware elements (e.g., application specific integrated circuits (ASICs) , electrically erasable programmable readonly memories (EEPROMs) , etc.), or other related components.
- ASICs application specific integrated circuits
- EEPROMs electrically erasable programmable readonly memories
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Communication Control (AREA)
Abstract
Description
Claims
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2004552298A JP4454499B2 (en) | 2002-11-20 | 2003-11-05 | Transmission system with functionality of multiple logical sub-transmission systems |
KR1020057009100A KR101100804B1 (en) | 2002-11-20 | 2003-11-05 | Forwarding system with multiple logical sub-system functionality |
AU2003283112A AU2003283112A1 (en) | 2002-11-20 | 2003-11-05 | Forewarding system with multiple logical sub-system functionality |
EP03773387A EP1563647A2 (en) | 2002-11-20 | 2003-11-05 | Forewarding system with multiple logical sub-system functionality |
CA002503508A CA2503508A1 (en) | 2002-11-20 | 2003-11-05 | Forewarding system with multiple logical sub-system functionality |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/299,857 US20040098505A1 (en) | 2002-11-20 | 2002-11-20 | Forwarding system with multiple logical sub-system functionality |
US10/299,857 | 2002-11-20 |
Publications (2)
Publication Number | Publication Date |
---|---|
WO2004047377A2 true WO2004047377A2 (en) | 2004-06-03 |
WO2004047377A3 WO2004047377A3 (en) | 2004-08-26 |
Family
ID=32297787
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CA2003/001711 WO2004047377A2 (en) | 2002-11-20 | 2003-11-05 | Forewarding system with multiple logical sub-system functionality |
Country Status (8)
Country | Link |
---|---|
US (2) | US20040098505A1 (en) |
EP (1) | EP1563647A2 (en) |
JP (1) | JP4454499B2 (en) |
KR (1) | KR101100804B1 (en) |
CN (1) | CN100493028C (en) |
AU (1) | AU2003283112A1 (en) |
CA (1) | CA2503508A1 (en) |
WO (1) | WO2004047377A2 (en) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20150163142A1 (en) * | 2013-12-09 | 2015-06-11 | Nicira, Inc. | Detecting an elephant flow based on the size of a packet |
US9967199B2 (en) | 2013-12-09 | 2018-05-08 | Nicira, Inc. | Inspecting operations of a machine to detect elephant flows |
US11962518B2 (en) | 2020-06-02 | 2024-04-16 | VMware LLC | Hardware acceleration techniques using flow selection |
Families Citing this family (156)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7295509B2 (en) | 2000-09-13 | 2007-11-13 | Qualcomm, Incorporated | Signaling method in an OFDM multiple access system |
US9130810B2 (en) | 2000-09-13 | 2015-09-08 | Qualcomm Incorporated | OFDM communications methods and apparatus |
WO2004064310A2 (en) * | 2003-01-11 | 2004-07-29 | Omnivergent Communications Corporation | Cognitive network |
US9032095B1 (en) | 2004-01-06 | 2015-05-12 | Juniper Networks, Inc. | Routing device having multiple logical routers |
US9137822B2 (en) | 2004-07-21 | 2015-09-15 | Qualcomm Incorporated | Efficient signaling over access channel |
US9148256B2 (en) | 2004-07-21 | 2015-09-29 | Qualcomm Incorporated | Performance based rank prediction for MIMO design |
US8996722B2 (en) * | 2004-11-01 | 2015-03-31 | Alcatel Lucent | Softrouter feature server |
US9246560B2 (en) | 2005-03-10 | 2016-01-26 | Qualcomm Incorporated | Systems and methods for beamforming and rate control in a multi-input multi-output communication systems |
US9154211B2 (en) | 2005-03-11 | 2015-10-06 | Qualcomm Incorporated | Systems and methods for beamforming feedback in multi antenna communication systems |
US8446892B2 (en) | 2005-03-16 | 2013-05-21 | Qualcomm Incorporated | Channel structures for a quasi-orthogonal multiple-access communication system |
US9520972B2 (en) | 2005-03-17 | 2016-12-13 | Qualcomm Incorporated | Pilot signal transmission for an orthogonal frequency division wireless communication system |
US9143305B2 (en) | 2005-03-17 | 2015-09-22 | Qualcomm Incorporated | Pilot signal transmission for an orthogonal frequency division wireless communication system |
US9461859B2 (en) | 2005-03-17 | 2016-10-04 | Qualcomm Incorporated | Pilot signal transmission for an orthogonal frequency division wireless communication system |
US9184870B2 (en) | 2005-04-01 | 2015-11-10 | Qualcomm Incorporated | Systems and methods for control channel signaling |
US9036538B2 (en) | 2005-04-19 | 2015-05-19 | Qualcomm Incorporated | Frequency hopping design for single carrier FDMA systems |
US9408220B2 (en) | 2005-04-19 | 2016-08-02 | Qualcomm Incorporated | Channel quality reporting for adaptive sectorization |
US8879511B2 (en) | 2005-10-27 | 2014-11-04 | Qualcomm Incorporated | Assignment acknowledgement for a wireless communication system |
US8611284B2 (en) | 2005-05-31 | 2013-12-17 | Qualcomm Incorporated | Use of supplemental assignments to decrement resources |
US8565194B2 (en) | 2005-10-27 | 2013-10-22 | Qualcomm Incorporated | Puncturing signaling channel for a wireless communication system |
US8462859B2 (en) | 2005-06-01 | 2013-06-11 | Qualcomm Incorporated | Sphere decoding apparatus |
US9179319B2 (en) | 2005-06-16 | 2015-11-03 | Qualcomm Incorporated | Adaptive sectorization in cellular systems |
US8599945B2 (en) | 2005-06-16 | 2013-12-03 | Qualcomm Incorporated | Robust rank prediction for a MIMO system |
US8885628B2 (en) | 2005-08-08 | 2014-11-11 | Qualcomm Incorporated | Code division multiplexing in a single-carrier frequency division multiple access system |
US20070041457A1 (en) | 2005-08-22 | 2007-02-22 | Tamer Kadous | Method and apparatus for providing antenna diversity in a wireless communication system |
US9209956B2 (en) | 2005-08-22 | 2015-12-08 | Qualcomm Incorporated | Segment sensitive scheduling |
US8644292B2 (en) | 2005-08-24 | 2014-02-04 | Qualcomm Incorporated | Varied transmission time intervals for wireless communication system |
US9136974B2 (en) | 2005-08-30 | 2015-09-15 | Qualcomm Incorporated | Precoding and SDMA support |
US9210651B2 (en) | 2005-10-27 | 2015-12-08 | Qualcomm Incorporated | Method and apparatus for bootstraping information in a communication system |
US8693405B2 (en) * | 2005-10-27 | 2014-04-08 | Qualcomm Incorporated | SDMA resource management |
US9088384B2 (en) | 2005-10-27 | 2015-07-21 | Qualcomm Incorporated | Pilot symbol transmission in wireless communication systems |
US8477684B2 (en) | 2005-10-27 | 2013-07-02 | Qualcomm Incorporated | Acknowledgement of control messages in a wireless communication system |
US8045512B2 (en) | 2005-10-27 | 2011-10-25 | Qualcomm Incorporated | Scalable frequency band operation in wireless communication systems |
US9225488B2 (en) | 2005-10-27 | 2015-12-29 | Qualcomm Incorporated | Shared signaling channel |
US9225416B2 (en) | 2005-10-27 | 2015-12-29 | Qualcomm Incorporated | Varied signaling channels for a reverse link in a wireless communication system |
US9172453B2 (en) | 2005-10-27 | 2015-10-27 | Qualcomm Incorporated | Method and apparatus for pre-coding frequency division duplexing system |
US8582509B2 (en) | 2005-10-27 | 2013-11-12 | Qualcomm Incorporated | Scalable frequency band operation in wireless communication systems |
US9144060B2 (en) | 2005-10-27 | 2015-09-22 | Qualcomm Incorporated | Resource allocation for shared signaling channels |
US8582548B2 (en) | 2005-11-18 | 2013-11-12 | Qualcomm Incorporated | Frequency division multiple access schemes for wireless communication |
US20070140235A1 (en) * | 2005-12-21 | 2007-06-21 | Nortel Networks Limited | Network visible inter-logical router links |
US8619771B2 (en) | 2009-09-30 | 2013-12-31 | Vmware, Inc. | Private allocated networks over shared communications infrastructure |
US8892706B1 (en) | 2010-06-21 | 2014-11-18 | Vmware, Inc. | Private ethernet overlay networks over a shared ethernet in a virtual environment |
KR100708588B1 (en) * | 2006-05-01 | 2007-04-20 | 한국정보통신대학교 산학협력단 | Method for forwarding preference-based in network and its system |
US8924524B2 (en) | 2009-07-27 | 2014-12-30 | Vmware, Inc. | Automated network configuration of virtual machines in a virtual lab data environment |
CA2700866C (en) | 2007-09-26 | 2016-06-21 | Martin Casado | Network operating system for managing and securing networks |
US8195774B2 (en) | 2008-05-23 | 2012-06-05 | Vmware, Inc. | Distributed virtual switch for virtualized computer systems |
US7944844B2 (en) | 2008-07-10 | 2011-05-17 | At&T Intellectual Property I, L.P. | Methods and apparatus to monitor network layer functionalities |
CN101662421B (en) * | 2008-08-28 | 2012-09-05 | 中兴通讯股份有限公司 | Method and device for transmitting control message based on ethernet multi-ring network |
EP2804350B1 (en) | 2009-04-01 | 2019-07-24 | Nicira, Inc. | Method and apparatus for implementing and managing virtual switches |
US8369345B1 (en) * | 2009-11-13 | 2013-02-05 | Juniper Networks, Inc. | Multi-router system having shared network interfaces |
US9491085B2 (en) | 2010-05-24 | 2016-11-08 | At&T Intellectual Property I, L.P. | Methods and apparatus to route control packets based on address partitioning |
US8699484B2 (en) | 2010-05-24 | 2014-04-15 | At&T Intellectual Property I, L.P. | Methods and apparatus to route packets in a network |
US9680750B2 (en) | 2010-07-06 | 2017-06-13 | Nicira, Inc. | Use of tunnels to hide network addresses |
US8964528B2 (en) | 2010-07-06 | 2015-02-24 | Nicira, Inc. | Method and apparatus for robust packet distribution among hierarchical managed switching elements |
US9525647B2 (en) | 2010-07-06 | 2016-12-20 | Nicira, Inc. | Network control apparatus and method for creating and modifying logical switching elements |
US8717895B2 (en) | 2010-07-06 | 2014-05-06 | Nicira, Inc. | Network virtualization apparatus and method with a table mapping engine |
US10103939B2 (en) | 2010-07-06 | 2018-10-16 | Nicira, Inc. | Network control apparatus and method for populating logical datapath sets |
US9043452B2 (en) | 2011-05-04 | 2015-05-26 | Nicira, Inc. | Network control apparatus and method for port isolation |
CN106850444B (en) | 2011-08-17 | 2020-10-27 | Nicira股份有限公司 | Logical L3 routing |
AU2012296330B2 (en) | 2011-08-17 | 2016-03-17 | Nicira, Inc. | Hierarchical controller clusters for interconnecting different logical domains |
US9288104B2 (en) | 2011-10-25 | 2016-03-15 | Nicira, Inc. | Chassis controllers for converting universal flows |
US9203701B2 (en) | 2011-10-25 | 2015-12-01 | Nicira, Inc. | Network virtualization apparatus and method with scheduling capabilities |
US9137107B2 (en) | 2011-10-25 | 2015-09-15 | Nicira, Inc. | Physical controllers for converting universal flows |
US9154433B2 (en) | 2011-10-25 | 2015-10-06 | Nicira, Inc. | Physical controller |
WO2013074855A1 (en) | 2011-11-15 | 2013-05-23 | Nicira, Inc. | Control plane interface for logical middlebox services |
AU2013249152B2 (en) | 2012-04-18 | 2016-04-28 | Nicira, Inc. | Using transactions to minimize churn in a distributed network control system |
US9231892B2 (en) | 2012-07-09 | 2016-01-05 | Vmware, Inc. | Distributed virtual switch configuration and state management |
US9432215B2 (en) | 2013-05-21 | 2016-08-30 | Nicira, Inc. | Hierarchical network managers |
US10218564B2 (en) | 2013-07-08 | 2019-02-26 | Nicira, Inc. | Unified replication mechanism for fault-tolerance of state |
US9559870B2 (en) | 2013-07-08 | 2017-01-31 | Nicira, Inc. | Managing forwarding of logical network traffic between physical domains |
US9571386B2 (en) | 2013-07-08 | 2017-02-14 | Nicira, Inc. | Hybrid packet processing |
US9282019B2 (en) | 2013-07-12 | 2016-03-08 | Nicira, Inc. | Tracing logical network packets through physical network |
US9407580B2 (en) | 2013-07-12 | 2016-08-02 | Nicira, Inc. | Maintaining data stored with a packet |
US9197529B2 (en) | 2013-07-12 | 2015-11-24 | Nicira, Inc. | Tracing network packets through logical and physical networks |
US9887960B2 (en) | 2013-08-14 | 2018-02-06 | Nicira, Inc. | Providing services for logical networks |
US9952885B2 (en) | 2013-08-14 | 2018-04-24 | Nicira, Inc. | Generation of configuration files for a DHCP module executing within a virtualized container |
US9973382B2 (en) | 2013-08-15 | 2018-05-15 | Nicira, Inc. | Hitless upgrade for network control applications |
US9503371B2 (en) | 2013-09-04 | 2016-11-22 | Nicira, Inc. | High availability L3 gateways for logical networks |
US9577845B2 (en) | 2013-09-04 | 2017-02-21 | Nicira, Inc. | Multiple active L3 gateways for logical networks |
US9602398B2 (en) | 2013-09-15 | 2017-03-21 | Nicira, Inc. | Dynamically generating flows with wildcard fields |
US9674087B2 (en) | 2013-09-15 | 2017-06-06 | Nicira, Inc. | Performing a multi-stage lookup to classify packets |
US9596126B2 (en) | 2013-10-10 | 2017-03-14 | Nicira, Inc. | Controller side method of generating and updating a controller assignment list |
US10063458B2 (en) | 2013-10-13 | 2018-08-28 | Nicira, Inc. | Asymmetric connection with external networks |
US9910686B2 (en) | 2013-10-13 | 2018-03-06 | Nicira, Inc. | Bridging between network segments with a logical router |
US9569368B2 (en) | 2013-12-13 | 2017-02-14 | Nicira, Inc. | Installing and managing flows in a flow table cache |
US9996467B2 (en) | 2013-12-13 | 2018-06-12 | Nicira, Inc. | Dynamically adjusting the number of flows allowed in a flow table cache |
US9313129B2 (en) | 2014-03-14 | 2016-04-12 | Nicira, Inc. | Logical router processing by network controller |
US9419855B2 (en) | 2014-03-14 | 2016-08-16 | Nicira, Inc. | Static routes for logical routers |
US9225597B2 (en) | 2014-03-14 | 2015-12-29 | Nicira, Inc. | Managed gateways peering with external router to attract ingress packets |
US9590901B2 (en) | 2014-03-14 | 2017-03-07 | Nicira, Inc. | Route advertisement by managed gateways |
US9647883B2 (en) | 2014-03-21 | 2017-05-09 | Nicria, Inc. | Multiple levels of logical routers |
US9503321B2 (en) | 2014-03-21 | 2016-11-22 | Nicira, Inc. | Dynamic routing for logical routers |
US9893988B2 (en) | 2014-03-27 | 2018-02-13 | Nicira, Inc. | Address resolution using multiple designated instances of a logical router |
US9413644B2 (en) | 2014-03-27 | 2016-08-09 | Nicira, Inc. | Ingress ECMP in virtual distributed routing environment |
US9686200B2 (en) | 2014-03-31 | 2017-06-20 | Nicira, Inc. | Flow cache hierarchy |
US9385954B2 (en) | 2014-03-31 | 2016-07-05 | Nicira, Inc. | Hashing techniques for use in a network environment |
US10193806B2 (en) | 2014-03-31 | 2019-01-29 | Nicira, Inc. | Performing a finishing operation to improve the quality of a resulting hash |
US10164894B2 (en) | 2014-05-05 | 2018-12-25 | Nicira, Inc. | Buffered subscriber tables for maintaining a consistent network state |
US9742881B2 (en) | 2014-06-30 | 2017-08-22 | Nicira, Inc. | Network virtualization using just-in-time distributed capability for classification encoding |
US9858100B2 (en) | 2014-08-22 | 2018-01-02 | Nicira, Inc. | Method and system of provisioning logical networks on a host machine |
US9768980B2 (en) | 2014-09-30 | 2017-09-19 | Nicira, Inc. | Virtual distributed bridging |
US10020960B2 (en) | 2014-09-30 | 2018-07-10 | Nicira, Inc. | Virtual distributed bridging |
US10511458B2 (en) | 2014-09-30 | 2019-12-17 | Nicira, Inc. | Virtual distributed bridging |
US10250443B2 (en) | 2014-09-30 | 2019-04-02 | Nicira, Inc. | Using physical location to modify behavior of a distributed virtual network element |
US11178051B2 (en) | 2014-09-30 | 2021-11-16 | Vmware, Inc. | Packet key parser for flow-based forwarding elements |
US10469342B2 (en) | 2014-10-10 | 2019-11-05 | Nicira, Inc. | Logical network traffic analysis |
US10079779B2 (en) | 2015-01-30 | 2018-09-18 | Nicira, Inc. | Implementing logical router uplinks |
US10038628B2 (en) | 2015-04-04 | 2018-07-31 | Nicira, Inc. | Route server mode for dynamic routing between logical and physical networks |
US9967134B2 (en) | 2015-04-06 | 2018-05-08 | Nicira, Inc. | Reduction of network churn based on differences in input state |
CN106302181B (en) * | 2015-05-19 | 2020-06-26 | 中兴通讯股份有限公司 | Message forwarding configuration method and device of communication equipment and message forwarding method |
US10348625B2 (en) | 2015-06-30 | 2019-07-09 | Nicira, Inc. | Sharing common L2 segment in a virtual distributed router environment |
US10129142B2 (en) | 2015-08-11 | 2018-11-13 | Nicira, Inc. | Route configuration for logical router |
US10075363B2 (en) | 2015-08-31 | 2018-09-11 | Nicira, Inc. | Authorization for advertised routes among logical routers |
US10204122B2 (en) | 2015-09-30 | 2019-02-12 | Nicira, Inc. | Implementing an interface between tuple and message-driven control entities |
US10095535B2 (en) | 2015-10-31 | 2018-10-09 | Nicira, Inc. | Static route types for logical routers |
US10313271B2 (en) * | 2016-03-16 | 2019-06-04 | At&T Intellectual Property I, L.P. | Providing and using a distributed forwarding service |
US10333849B2 (en) | 2016-04-28 | 2019-06-25 | Nicira, Inc. | Automatic configuration of logical routers on edge nodes |
US10484515B2 (en) | 2016-04-29 | 2019-11-19 | Nicira, Inc. | Implementing logical metadata proxy servers in logical networks |
US11019167B2 (en) | 2016-04-29 | 2021-05-25 | Nicira, Inc. | Management of update queues for network controller |
US10841273B2 (en) | 2016-04-29 | 2020-11-17 | Nicira, Inc. | Implementing logical DHCP servers in logical networks |
US10091161B2 (en) | 2016-04-30 | 2018-10-02 | Nicira, Inc. | Assignment of router ID for logical routers |
US10560320B2 (en) | 2016-06-29 | 2020-02-11 | Nicira, Inc. | Ranking of gateways in cluster |
US10153973B2 (en) | 2016-06-29 | 2018-12-11 | Nicira, Inc. | Installation of routing tables for logical router in route server mode |
US10454758B2 (en) | 2016-08-31 | 2019-10-22 | Nicira, Inc. | Edge node cluster network redundancy and fast convergence using an underlay anycast VTEP IP |
US10341236B2 (en) | 2016-09-30 | 2019-07-02 | Nicira, Inc. | Anycast edge service gateways |
US10742746B2 (en) | 2016-12-21 | 2020-08-11 | Nicira, Inc. | Bypassing a load balancer in a return path of network traffic |
US10212071B2 (en) | 2016-12-21 | 2019-02-19 | Nicira, Inc. | Bypassing a load balancer in a return path of network traffic |
US10237123B2 (en) | 2016-12-21 | 2019-03-19 | Nicira, Inc. | Dynamic recovery from a split-brain failure in edge nodes |
US10616045B2 (en) | 2016-12-22 | 2020-04-07 | Nicira, Inc. | Migration of centralized routing components of logical router |
US10200306B2 (en) | 2017-03-07 | 2019-02-05 | Nicira, Inc. | Visualization of packet tracing operation results |
US10681000B2 (en) | 2017-06-30 | 2020-06-09 | Nicira, Inc. | Assignment of unique physical network addresses for logical network addresses |
US10637800B2 (en) | 2017-06-30 | 2020-04-28 | Nicira, Inc | Replacement of logical network addresses with physical network addresses |
US10608887B2 (en) | 2017-10-06 | 2020-03-31 | Nicira, Inc. | Using packet tracing tool to automatically execute packet capture operations |
US10374827B2 (en) | 2017-11-14 | 2019-08-06 | Nicira, Inc. | Identifier that maps to different networks at different datacenters |
US10511459B2 (en) | 2017-11-14 | 2019-12-17 | Nicira, Inc. | Selection of managed forwarding element for bridge spanning multiple datacenters |
US10999220B2 (en) | 2018-07-05 | 2021-05-04 | Vmware, Inc. | Context aware middlebox services at datacenter edge |
US11184327B2 (en) | 2018-07-05 | 2021-11-23 | Vmware, Inc. | Context aware middlebox services at datacenter edges |
US10931560B2 (en) | 2018-11-23 | 2021-02-23 | Vmware, Inc. | Using route type to determine routing protocol behavior |
US10735541B2 (en) | 2018-11-30 | 2020-08-04 | Vmware, Inc. | Distributed inline proxy |
US10797998B2 (en) | 2018-12-05 | 2020-10-06 | Vmware, Inc. | Route server for distributed routers using hierarchical routing protocol |
US10938788B2 (en) | 2018-12-12 | 2021-03-02 | Vmware, Inc. | Static routes for policy-based VPN |
US11095480B2 (en) | 2019-08-30 | 2021-08-17 | Vmware, Inc. | Traffic optimization using distributed edge services |
US11641305B2 (en) | 2019-12-16 | 2023-05-02 | Vmware, Inc. | Network diagnosis in software-defined networking (SDN) environments |
US11283699B2 (en) | 2020-01-17 | 2022-03-22 | Vmware, Inc. | Practical overlay network latency measurement in datacenter |
US11616755B2 (en) | 2020-07-16 | 2023-03-28 | Vmware, Inc. | Facilitating distributed SNAT service |
US11606294B2 (en) | 2020-07-16 | 2023-03-14 | Vmware, Inc. | Host computer configured to facilitate distributed SNAT service |
US11611613B2 (en) | 2020-07-24 | 2023-03-21 | Vmware, Inc. | Policy-based forwarding to a load balancer of a load balancing cluster |
US11451413B2 (en) | 2020-07-28 | 2022-09-20 | Vmware, Inc. | Method for advertising availability of distributed gateway service and machines at host computer |
US11902050B2 (en) | 2020-07-28 | 2024-02-13 | VMware LLC | Method for providing distributed gateway service at host computer |
US11558426B2 (en) | 2020-07-29 | 2023-01-17 | Vmware, Inc. | Connection tracking for container cluster |
US11196628B1 (en) | 2020-07-29 | 2021-12-07 | Vmware, Inc. | Monitoring container clusters |
US11570090B2 (en) | 2020-07-29 | 2023-01-31 | Vmware, Inc. | Flow tracing operation in container cluster |
US11736436B2 (en) | 2020-12-31 | 2023-08-22 | Vmware, Inc. | Identifying routes with indirect addressing in a datacenter |
US11336533B1 (en) | 2021-01-08 | 2022-05-17 | Vmware, Inc. | Network visualization of correlations between logical elements and associated physical elements |
US11687210B2 (en) | 2021-07-05 | 2023-06-27 | Vmware, Inc. | Criteria-based expansion of group nodes in a network topology visualization |
US11711278B2 (en) | 2021-07-24 | 2023-07-25 | Vmware, Inc. | Visualization of flow trace operation across multiple sites |
US11706109B2 (en) | 2021-09-17 | 2023-07-18 | Vmware, Inc. | Performance of traffic monitoring actions |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2000072533A1 (en) * | 1999-05-21 | 2000-11-30 | Broadcom Corporation | Stacked network switch configuration |
Family Cites Families (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH06178343A (en) * | 1992-12-02 | 1994-06-24 | Toshiba Corp | Remote line storing system for private branch exchange |
KR100660529B1 (en) * | 1999-01-07 | 2006-12-22 | 삼성전자주식회사 | Communication system and control method thereof |
US6594704B1 (en) * | 1999-12-15 | 2003-07-15 | Quarry Technologies | Method of managing and using multiple virtual private networks in a router with a single routing table |
US7158497B2 (en) * | 2000-08-31 | 2007-01-02 | Nortel Networks Limited | Methods and apparatus for supporting micro-mobility within a radio access network |
US20020103921A1 (en) * | 2001-01-31 | 2002-08-01 | Shekar Nair | Method and system for routing broadband internet traffic |
US6944168B2 (en) * | 2001-05-04 | 2005-09-13 | Slt Logic Llc | System and method for providing transformation of multi-protocol packets in a data stream |
US7286479B2 (en) * | 2001-07-13 | 2007-10-23 | Nortel Networks Limited | Routing for a communications network |
US7561517B2 (en) * | 2001-11-02 | 2009-07-14 | Internap Network Services Corporation | Passive route control of data networks |
US6744774B2 (en) * | 2002-06-27 | 2004-06-01 | Nokia, Inc. | Dynamic routing over secure networks |
US7209976B2 (en) * | 2002-07-16 | 2007-04-24 | Jeremy Benjamin | Protocol communication and transit packet forwarding routed between multiple virtual routers within a single physical router |
-
2002
- 2002-11-20 US US10/299,857 patent/US20040098505A1/en not_active Abandoned
-
2003
- 2003-11-05 CA CA002503508A patent/CA2503508A1/en not_active Abandoned
- 2003-11-05 KR KR1020057009100A patent/KR101100804B1/en not_active IP Right Cessation
- 2003-11-05 CN CNB2003801037431A patent/CN100493028C/en not_active Expired - Fee Related
- 2003-11-05 EP EP03773387A patent/EP1563647A2/en not_active Withdrawn
- 2003-11-05 JP JP2004552298A patent/JP4454499B2/en not_active Expired - Fee Related
- 2003-11-05 AU AU2003283112A patent/AU2003283112A1/en not_active Abandoned
- 2003-11-05 WO PCT/CA2003/001711 patent/WO2004047377A2/en active Application Filing
-
2008
- 2008-09-18 US US12/232,491 patent/US20090031041A1/en not_active Abandoned
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2000072533A1 (en) * | 1999-05-21 | 2000-11-30 | Broadcom Corporation | Stacked network switch configuration |
Cited By (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20150163142A1 (en) * | 2013-12-09 | 2015-06-11 | Nicira, Inc. | Detecting an elephant flow based on the size of a packet |
US9548924B2 (en) * | 2013-12-09 | 2017-01-17 | Nicira, Inc. | Detecting an elephant flow based on the size of a packet |
US9838276B2 (en) | 2013-12-09 | 2017-12-05 | Nicira, Inc. | Detecting an elephant flow based on the size of a packet |
US9967199B2 (en) | 2013-12-09 | 2018-05-08 | Nicira, Inc. | Inspecting operations of a machine to detect elephant flows |
US10158538B2 (en) | 2013-12-09 | 2018-12-18 | Nicira, Inc. | Reporting elephant flows to a network controller |
US10193771B2 (en) | 2013-12-09 | 2019-01-29 | Nicira, Inc. | Detecting and handling elephant flows |
US10666530B2 (en) | 2013-12-09 | 2020-05-26 | Nicira, Inc | Detecting and handling large flows |
US11095536B2 (en) | 2013-12-09 | 2021-08-17 | Nicira, Inc. | Detecting and handling large flows |
US11539630B2 (en) | 2013-12-09 | 2022-12-27 | Nicira, Inc. | Inspecting operations of a machine to detect elephant flows |
US11811669B2 (en) | 2013-12-09 | 2023-11-07 | Nicira, Inc. | Inspecting operations of a machine to detect elephant flows |
US11962518B2 (en) | 2020-06-02 | 2024-04-16 | VMware LLC | Hardware acceleration techniques using flow selection |
Also Published As
Publication number | Publication date |
---|---|
JP4454499B2 (en) | 2010-04-21 |
US20040098505A1 (en) | 2004-05-20 |
JP2006506858A (en) | 2006-02-23 |
AU2003283112A1 (en) | 2004-06-15 |
WO2004047377A3 (en) | 2004-08-26 |
CN100493028C (en) | 2009-05-27 |
EP1563647A2 (en) | 2005-08-17 |
KR101100804B1 (en) | 2012-01-02 |
KR20050065679A (en) | 2005-06-29 |
CA2503508A1 (en) | 2004-06-03 |
CN1714548A (en) | 2005-12-28 |
US20090031041A1 (en) | 2009-01-29 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20040098505A1 (en) | Forwarding system with multiple logical sub-system functionality | |
US7852771B2 (en) | Method and apparatus for implementing link-based source routing in generic framing protocol | |
US8270319B2 (en) | Method and apparatus for exchanging routing information and establishing connectivity across multiple network areas | |
US8611363B2 (en) | Logical port system and method | |
US9124567B2 (en) | Methods and devices for converting routing data from one protocol to another in a virtual private network | |
US9882838B2 (en) | Forwarding inter-switch connection (ISC) frames in a network-to-network interconnect topology | |
US20070177597A1 (en) | Ethernet connection-based forwarding process | |
US20160255019A1 (en) | Methods and apparatus related to a distributed switch fabric | |
KR101228284B1 (en) | Data communication system and method | |
KR20210093312A (en) | Logic routers with segmented network elements | |
US20020110119A1 (en) | Method and apparatus for stream aggregation in a multiprotocol label switching network environment | |
EP3020164A1 (en) | Support for virtual extensible local area network segments across multiple data center sites | |
MX2007008112A (en) | Connection-oriented communications scheme for connection-less communications traffic. | |
US20030152182A1 (en) | Optical exchange method, apparatus and system for facilitating data transport between WAN, SAN and LAN and for enabling enterprise computing into networks | |
WO2002059765A1 (en) | Dense virtual router packet switching | |
CN112311673A (en) | Using and processing per-slice segment identifiers in networks employing segment routing | |
US9755854B2 (en) | Tag conversion apparatus | |
US8861545B2 (en) | Method for performing protocol translation in a network switch | |
WO2021052381A1 (en) | Message sending method and apparatus | |
CN102415061B (en) | Packet flood control | |
Gringeri et al. | Optimizing transport systems to integrate TDM and packet services | |
Chang et al. | Quasi-circuit switching and quasi-circuit switches | |
CN117955913A (en) | Message processing method and related device | |
JPH11298484A (en) | Atm communication regulation system | |
JPH0537546A (en) | Cross connect communication equipnent for asynchronous transfer mode |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A2 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ OM PH PL PT RO RU SC SD SE SG SK SL TJ TM TN TR TT TZ UA UG UZ VC VN YU ZA ZM ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A2 Designated state(s): BW GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
WWE | Wipo information: entry into national phase |
Ref document number: 2503508 Country of ref document: CA |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2003773387 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1020057009100 Country of ref document: KR Ref document number: 2004552298 Country of ref document: JP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 20038A37431 Country of ref document: CN |
|
WWP | Wipo information: published in national office |
Ref document number: 1020057009100 Country of ref document: KR |
|
WWP | Wipo information: published in national office |
Ref document number: 2003773387 Country of ref document: EP |