US7948994B2 - Method and apparatus for routing and forwarding between virtual routers within a single network element - Google Patents

Method and apparatus for routing and forwarding between virtual routers within a single network element Download PDF

Info

Publication number
US7948994B2
US7948994B2 US10/883,070 US88307004A US7948994B2 US 7948994 B2 US7948994 B2 US 7948994B2 US 88307004 A US88307004 A US 88307004A US 7948994 B2 US7948994 B2 US 7948994B2
Authority
US
United States
Prior art keywords
virtual router
virtual
logical interface
routing
storage medium
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.)
Active, expires
Application number
US10/883,070
Other versions
US20040240455A1 (en
Inventor
Naiming Shen
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Ericsson AB
Original Assignee
Ericsson AB
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Ericsson AB filed Critical Ericsson AB
Priority to US10/883,070 priority Critical patent/US7948994B2/en
Publication of US20040240455A1 publication Critical patent/US20040240455A1/en
Assigned to ERICSSON AB reassignment ERICSSON AB ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: REDBACK NETWORKS INC.
Priority to US13/087,337 priority patent/US8472451B2/en
Application granted granted Critical
Publication of US7948994B2 publication Critical patent/US7948994B2/en
Active legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/58Association of routers
    • H04L45/586Association of routers of virtual routers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/44Star or tree networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46Interconnection of networks
    • H04L12/4641Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46Interconnection of networks
    • H04L12/4641Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • H04L12/4675Dynamic sharing of VLAN information amongst network nodes
    • H04L12/4679Arrangements for the registration or de-registration of VLAN attribute values, e.g. VLAN identifiers, port VLAN membership
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/02Topology update or discovery
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/02Topology update or discovery
    • H04L45/033Topology update or discovery by updating distance vector protocols
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/54Organization of routing tables
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/74Address processing for routing
    • H04L45/745Address table lookup; Address filtering
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/76Routing in software-defined topologies, e.g. routing between virtual machines

Definitions

  • the invention relates to the field of communication. More specifically, the invention relates to communication networks.
  • FIG. 1 is a diagram of a single network element with virtual routers.
  • a network element 101 includes virtual routers VR-A 111 , VR-B 113 , and VR-C 115 .
  • Each of the virtual routers 111 , 113 , and 115 respectively receive traffic from ingress ports 103 A- 103 C and respectively transmit traffic out of the egress ports 151 A- 151 C as illustrated in FIG. 1 .
  • the virtual router VR-A 111 receives traffic 109 A from the ingress port 103 A and transmits the traffic 109 A out of the egress port 151 A.
  • the virtual router VR-B 113 receives traffic 109 B from the ingress port 103 B and transmits the traffic 109 B out of the ingress port 151 B.
  • the virtual router VR-C 115 receives traffic 109 C from the ingress port 103 C and transmits the traffic 109 C out of the egress port 151 C.
  • Network elements that support the virtual routers performed inter-VR forwarding based on the forwarding scheme described (i.e., with standard interfaces). If VR-A 111 received a packet for transmission to VR-B 113 , then the VR-A 111 looked up the next hop in its routing table, found an interface that was associated with the ingress port 103 B, and forwarded the packet based on that interface.
  • the virtual routers within a single network element do not communicate routing and/or forwarding information as if separate routers.
  • a method in a single network element provides for peering a first virtual router to a second virtual router, wherein the first and second virtual routers have separate address spaces and separate routing tables.
  • a set of one or more routes are distributed from the first first virtual router to the second virtual router, wherein a first of the set of routes identifies the first virtual router as a next hop of the first route, said first route including a destination.
  • the method provides for downloading to a set of one or more forwarding tables, the destination and the next hop.
  • FIG. 1 (Prior Art) is a diagram of a single network element with virtual routers.
  • FIG. 2 is an exemplary diagram illustrating forwarding between virtual routers according to one embodiment of the invention.
  • FIG. 3A is an exemplary diagram illustrating peering of virtual routers according to one embodiment of the invention.
  • FIG. 3B is an exemplary diagram illustrating additional peering of virtual routers according to one embodiment of the invention.
  • FIG. 3C is an exemplary diagram illustrating inter-VR interfaces as local area network interfaces according to one embodiment of the invention.
  • FIG. 4 is an exemplary diagram illustrating external route distribution between virtual routers according to one embodiment of the invention.
  • FIG. 5 is a diagram of an exemplary network element according to one embodiment of the invention.
  • routing table and forwarding table are used throughout the description, but are not limited to being tables.
  • a routing table and a forwarding table may be implemented with a variety of data structures (e.g., trees, tries, linked lists, hash tables, hybrid data structures, etc.).
  • FIG. 2 is an exemplary diagram illustrating forwarding between virtual routers according to one embodiment of the invention.
  • FIG. 2 illustrates a network element 202 as including a virtual router 205 A and a virtual router 205 B.
  • the virtual router 205 A is identified as VR-A and the virtual router 205 B is identified as VR-B.
  • the virtual router 205 A includes interior gateway routing tables 209 , an exterior gateway routing table 211 , and a main routing table 213 .
  • Interior gateway routing protocol processes e.g., OSPF, RIP, iBGP, IS-IS, etc.
  • the interior gateway routing tables 209 indicate routing information for reaching a destination, as determined by a corresponding interior gateway routing protocol process, that is internal to an autonomous system (AS), which includes the virtual router 205 A.
  • a process implementing an exterior gateway protocol (e.g., BGP-v4, EGP, etc.) builds the exterior gateway routing table 211 .
  • the exterior gateway routing table 211 indicates routing information for reaching destinations external to the AS of the virtual router 205 A.
  • the main routing table 213 is built using route entries from the interior gateway routing tables 209 , the exterior gateway routing table 211 , and interfaces from an interface manager 271 .
  • the interface manager 271 includes a data structure that indicates interfaces and their corresponding reachable IP addresses via the interfaces. In certain embodiments of the invention, the interface manager also associates lower layer hardware information learned from lower layer protocols with interfaces. Each routing process exchanges routing information with other network elements through interfaces and install learned reachable routes into the main routing table, which are eventually downloaded into forwarding tables of the data plane from the main routing table in the control plane. The interface manager 271 indicates and maintains a status for each interface of the host network element. A routing process utilizes interface status to make correct routing decisions.
  • the first column of each entry within each of the routing tables 209 , 211 , and 213 indicates a destination.
  • the last column of each entry within each of the routing tables 209 , 211 , and 213 as illustrated in FIG. 2 indicates a next hop.
  • a next hop is either an interface next hop (i.e., a logical or physical interface) or a non-interface next hop (e.g., an IP address, a virtual router name, etc.).
  • the remaining columns within each of the routing tables 209 , 211 , and 213 indicate additional routing information, such as line, metrics, etc.
  • the virtual router 205 A also includes a forwarding module 207 and a forwarding table 219 .
  • the forwarding module 207 forwards packets that are received by the virtual router 205 A in accordance with the forwarding table 219 .
  • the forwarding table 219 receives information downloaded from the main routing table.
  • the interior gateway routing tables 209 includes internal destinations ID 1 , ID 2 , and ID 3 with corresponding next hops I/F 1 , VR-B, and ADDRESS, respectively.
  • ID 1 , ID 2 and ID 3 are identifying data (e.g., IP addresses, prefixes, etc.) of other network elements within the same AS as the virtual router 205 A.
  • One or more of the internal destinations may also be another virtual router within the same network element (e.g., ID 1 may be VR-B).
  • next hop I/F is a physical interface and the next hop VR-B may be a logical interface that indicates a VR instead of an IP address (i.e., an inter-VR interface), a virtual router handle, etc.
  • An inter-virtual router next hop is a unique value within the network element 202 that identifies a specific virtual router.
  • the administrator provides a user-friendly virtual router identifier (“VR name”) for the created virtual router.
  • the network element 202 creates and associates a unique virtual router identifier (“VR identifier”) to be utilized by the network element 202 to identify the created virtual router.
  • inter-virtual router next hops in the routing tables are VR identifiers
  • alternative embodiments of the invention may utilize alternative techniques to identify inter-VR next hops (e.g., the routing table indicates the VR name and a table that associates the VR name to a VR identifier is used to access the VR identifier, an inter-VR interface value is created within the network element and associated with a VR-identifier or VR-name in another data structure, etc.).
  • an inter-VR next hop is the VR identifier.
  • the exterior gateway routing table 211 as illustrated in FIG. 2 indicates external destinations ED 1 , ED 2 , and ED 3 and corresponding next hops ADDRESS, I/F 2 , and VR-B, respectively.
  • the external destinations ED 1 , ED 2 , and ED 3 can be IP addresses, prefixes, etc. While in one embodiment of the invention, external destinations that are other virtual routers are identified by an IP address or prefix, in alternative embodiments of the invention the external destination may be a VR name or VR identifier.
  • the forwarding module 207 determines the destination of the packet 201 .
  • the destination of the packet 201 is looked up in the forwarding table 219 to determine the appropriate outgoing interface. If the destination of the packet 201 is ID 1 , then the forwarding module 207 forwards the packet 201 to an egress port that corresponds to the outgoing interface I/F. If the destination of the packet 201 is ED 3 , then the forwarding module 207 forwards the packet 201 to the virtual router 205 B.
  • the virtual router 205 B will process the packet 201 in accordance with its forwarding/routing information (e.g., drop the packet 201 , forward the packet 201 to the appropriate egress port, forward the packet 201 to another virtual router, etc.).
  • forwarding/routing information e.g., drop the packet 201 , forward the packet 201 to the appropriate egress port, forward the packet 201 to another virtual router, etc.
  • the forwarding module determines if the next hop indicated by the forwarding table for a packet is an inter-VR next hop. If the next hop is an inter-VR next hop then the corresponding packet is forwarded to the appropriate virtual router. If the next hop is not an inter-VR next hop (e.g., a logical or physical interface that does not indicate a virtual router, an IP address, etc.), then the packet is processed accordingly (e.g., if the next hop is a physical interface, then the packet is processed at lower layers in order to forward the packet along the appropriate hardware lines to the egress port).
  • inter-VR next hop e.g., a logical or physical interface that does not indicate a virtual router, an IP address, etc.
  • a switching module is implemented separately from the forwarding module. If the next hop for a packet is a physical interface, then the forwarding module passes the packet to the switching module, which forwards the packet along the hardware lines that correspond to the physical interface. If the next hop is an inter-VR next hop, then the forwarding module forwards the packet to the appropriate virtual router.
  • next hop is a virtual router, an IP address, a physical interface, a logical interface, etc.
  • an additional field is included in each routing and forwarding table entry to explicitly indicate a type for the outgoing interface.
  • the value of the next hop implicitly indicates whether the next hop is a VR next hop or non-VR next hop.
  • Enabling inter-VR routing and forwarding provides additional functionality.
  • a service provider that is a customer of a network provider, which owns a network element with inter-VR routing and forwarding, can allow its virtual private network (VPN) customers to exchange routes.
  • VPN virtual private network
  • inter-VR routing and forwarding enables a service provider's VPN customers to use the provider's network for Internet access.
  • Inter-VR routing and forwarding can also be utilized to allow service providers to announce VPN customers' routes if they are part of the public address space.
  • Inter-VR routing and forwarding also enables virtual routers to replace customer premise equipment (CPE) routers.
  • CPE customer premise equipment
  • the service provider and/or network provider can utilize a virtual router to perform the tasks typically performed by a CPE router, especially for those customers that access the network from multiple locations.
  • inter-VR routing and forwarding enables local area, metro area, and/or intra-continental private peerings without utilizing physical lines and/or ports to connect virtual routers.
  • Inter-VR routing and forwarding also provides additional capabilities with respect to testing and parallel network inter-communication. Since virtual routers can be connected without wires, then numerous virtual routers can be peered or connected to represent the topology of actual networks. The inter-VR routing and forwarding can then be used to simulate routing in different network topologies without cables and wires.
  • a service provider with an operational legacy network and a next generation network can utilize inter-VR routing and forwarding for experimental, trial, and/or operational exchanges of routes between the different networks (assuming the different networks include virtual routers within individual network elements).
  • the service provider can utilize inter-VR routing and forwarding to migrate their customers from a legacy network to a next generation network.
  • FIGS. 3A-3C are exemplary diagrams illustrating interior gateway routing tables being built with inter-VR routes according to one embodiment of the invention.
  • FIG. 3A is an exemplary diagram illustrating peering of virtual routers according to one embodiment of the invention.
  • a virtual router 303 A (VR-A) is peered with virtual routers 303 B and 303 C.
  • the virtual routers 303 A, 303 B, and 303 C respectively have IP addresses 10.1.1.1, 10.1.1.2, and 10.1.1.3.
  • the virtual routers are peered with static routing (i.e., an administrator configures the connections between the virtual routers).
  • An administrator configures an inter-VR interface 315 L.B on the virtual router 303 A to reach the virtual router 303 B and an inter-VR interface 315 L.C also on the virtual router 303 A to reach the virtual router 303 C. While configuring the interfaces on the virtual router 303 A, the administrator also configures inter-VR interfaces 315 B.L and 315 C.L respectively on the virtual routers 303 B and 303 C. In response to the configuration, the interior gateway routing tables of the virtual routers are updated.
  • An interior gateway routing tables 307 A for the virtual router 303 A is updated to include a routing entry that indicates destination 10.1.1.2 reachable via next hop VR-B and a destination 10.1.1.3 reachable via next hop VR-C. While in one embodiment, the next hops to a virtual router are indicated with a VR identifier, alternative embodiments of the invention may indicate a virtual router next hop with the virtual router's name or IP address.
  • An interior gateway routing tables 307 B for the virtual router 303 B is updated to include a routing entry that indicates a destination 10.1.1.1 reachable via inter-VR interface 315 B.L, which is the VR identifier for the virtual router 303 A.
  • An interior gateway routing tables 307 C for the virtual router 303 C is updated to include a routing entry that indicates the destination 10.1.1.1 reachable via inter-VR interface 315 C.L.
  • a packet can be processed without inter-process communication. For example, if RIP is configured on inter-VR interface 315 L.B and the RIP process sends a packet over the inter-VR interface 315 L.B, the RIP packet immediately considers the packet as received on the inter-VR interface 315 B.L by the single RIP process.
  • Routing processes can exchange routing information via the inter-VR interfaces. The routing processes download these routes into the main routing table using inter-VR interfaces as next hops.
  • FIG. 3B is an exemplary diagram illustrating peering of virtual routers that are not virtual router local (virtual router 303 A) according to one embodiment of the invention.
  • the virtual routers 303 B and 303 C have been connected.
  • the virtual router 303 B has been configured to reach the virtual router 303 C via the inter-VR interface 315 B.C and the virtual router 303 C has been configured to reach the virtual router 303 B via the inter-VR interface 315 C.B.
  • Various techniques can be implemented to prevent redundant connections being created between virtual routers. In one embodiment of the invention, a check is performed when the administrator enters a configuration that binds interfaces of two virtual routers.
  • an inter-VR point-to-point (p2p) interface is utilized.
  • the interface manager ensures only a single bind number is utilized to connect a pair of virtual routers, although alternative embodiments of the invention may allow for multiple connections between virtual routers.
  • An interior gateway routing protocol process registers an interest in the configured interfaces for each virtual router with the interface manager.
  • the interface manager provides the registering interior gateway routing protocol process with the corresponding bind number, bound virtual router, and the type of interface. For example, assume the following configuration is entered:
  • the first set of configuration commands configures the interface I/F 1 on the virtual router A.
  • the second set of commands configures the interface I/F 2 on the virtual router B.
  • the interface manager creates a tuple that reflects the configuration of these interfaces on their corresponding virtual routers.
  • FIG. 3C is an exemplary diagram illustrating inter-VR interfaces as local area network interfaces according to one embodiment of the invention.
  • each of the virtual routers 303 A, 303 B and 303 C are connected to a virtual router local area network (VR-LAN) 323 .
  • the VR-LAN 323 is identified as VR-LAN- 1 .
  • the virtual routers 303 A, 303 B and 303 C are illustrated as being connected to the VR-LAN 323 for this example, fewer or more virtual routers may be connected to the VR-LAN.
  • multiple VR-LANs can be defined with various different groups of virtual routers connected to the different VR-LANS.
  • VR-B, VR-C and VR-A may be connected to VR-LAN- 1 , while VR-A, VR-C are connected to VR-LAN- 2 .
  • VR-LAN- 1 may comprise VR-A, VR-B and VR-C while VR-LAN- 2 may comprise VR-A, VR-B, and VR-C.
  • the interior gateway routing protocol process registers an interest in the interface 315 L.V for the virtual router 303 A with the interface manager.
  • the interface manager provides the registering interior gateway routing protocol process with the associated VR-LAN number, VR-LAN- 1 , which identifies the VR-LAN 323 .
  • the interior gateway routing protocol process accesses a data structure (e.g., a linked list) which indicates each VR-LAN interface associated with the VR-LAN identified by the interface manager
  • a data structure e.g., a linked list
  • alternative embodiments of the invention may provide the interior gateway routing protocol process the associated VR-LAN interfaces differently (e.g., the interface manager may maintain a data structure that indicates the VR-LAN and associated VR-LAN interfaces).
  • the interior gateway routing protocol process updates its interior gateway routing tables to indicate the associated VR-LAN interfaces as illustrated in FIG. 3C .
  • the interior gateway routing protocol process accesses the VR-LAN data structure that indicates associated VR-LAN interfaces instead of inserting the data structure in the interior gateway routing table.
  • the interior gateway routing protocol process transmits a control packet
  • the interior gateway routing protocol processes transmits to each VR-LAN interface associated with the VR-LAN.
  • the interior gateway routing protocol process marks the associated VR-LAN interfaces as received. For example, assume OSPF is configured on interfaces 315 L.V, 315 B.V, 315 C.V. If OSPF sends a packet on 315 B.V to the VR-LAN 323 for the VR-B 303 B, the sent OSPF packet is implicitly received on the interfaces 315 L.V and 315 C.V.
  • the single routing process e.g., OSPF
  • packets forwarded between virtual routers are passed directly between virtual routers and not passed down for lower layer processing.
  • packets may be passed down for lower layer processing (e.g., to the kernel socket, which is a communication channel between routing processes and the data plane that includes line cards) to maintain agnostic routing or minimize the amount of modification made to routing protocols.
  • FIG. 4 is an exemplary diagram illustrating external route distribution between virtual routers according to one embodiment of the invention.
  • a virtual router 401 with IP address 10.1.1.1 is peered with virtual routers 403 A and 403 B via inter-VR interfaces 415 L.B and 415 L.C, respectively.
  • the peering is established with either static routing or with interior gateway routing protocol process.
  • the virtual routers 401 , 403 A and 403 B respectively have exterior gateway routing tables 405 , 407 A and 407 B.
  • the bolded entries in the exterior gateway routing tables 405 , 407 A, and 407 B have been learned from other virtual routers.
  • the virtual router 401 has learned routes to external destinations ED 2 and ED 7 directly from virtual routers 403 A and 403 B, respectively.
  • the virtual router 403 A has learned routes to external destinations ED 1 and ED 7 from the virtual router 401 .
  • the virtual router 403 B has learned routes to external destinations ED 1 , ED 2 , and ED 5 from the virtual router 401 .
  • route distribution policies can be applied to distribution of routes between virtual routers. If a customer does not want routes from its virtual router distributed, then the customer's virtual router should not be peered with any other virtual routers that do not fall under the customer's control.
  • a policy may be implemented on a network element that allows the virtual router local to learn routes but not distribute routers. Alternatively, certain routes may be tagged as either restricted or unrestricted for inter-VR route distribution.
  • FIG. 5 is a diagram of an exemplary network element according to one embodiment of the invention.
  • a network element 500 includes a control card 503 coupled with a set of line cards 515 A- 515 C via a transmission medium 551 (e.g., a packet mesh, switching medium, etc.).
  • the control card 503 hosts external routing processes 505 A- 505 F and corresponding exterior gateway routing tables 507 A- 507 F.
  • the control card 503 also hosts internal routing processes 506 A- 506 F and corresponding interior gateway routing tables 509 A- 509 F.
  • Each of the internal routing processes 506 A- 506 F and their corresponding VR interior gateway routing tables 509 A- 509 F are used by a different virtual router configured on the network element 500 .
  • Each of the external routing processes 505 A- 505 F and their corresponding VR exterior gateway routing tables 507 A- 507 F are used by the different virtual router configured on the network element 500 .
  • Each of the line cards 515 A- 515 C include one or more forwarding tables.
  • the line card 515 A includes VR forwarding tables 517 A- 517 F.
  • the line card 515 B includes VR forwarding tables 517 B- 517 E.
  • the line card 515 C includes the VR forwarding table 517 A.
  • the forwarding tables 517 A- 517 F are created from forwarding information downloaded from the control card 503 .
  • Each of the VR forwarding tables corresponds to a different virtual router configured on the network element 500 .
  • a virtual router uses more than one VR forwarding table, VR interior gateway routing table, and/or VR exterior gateway routing table.
  • a single external and/or internal routing process is shared by different virtual routers.
  • the control card 503 and line cards 517 A - 517 C illustrated in FIG. 5 and the network elements described in the Figures include memories, processors, and/or ASICs.
  • Such memories include a machine-readable medium on which is stored a set of instructions (i.e., software) embodying any one, or all, of the methodologies described herein.
  • Software can reside, completely or at least partially, within this memory and/or within the processor and/or ASICs.
  • the term “machine-readable medium” shall be taken to include any mechanism that provides (i.e., stores and/or transmits) information in a form readable by a machine (e.g., a computer).
  • a machine-readable medium includes machine readable storage media (e.g., read only memory (“ROM”), random access memory (“RAM”), magnetic disk storage media, optical storage media, flash memory devices), machine readable transmission media (e.g., electrical, optical, acoustical, or other forms of propagated signals (e.g., carrier waves, infrared signals, digital signals, etc.)), etc.
  • machine readable storage media e.g., read only memory (“ROM”), random access memory (“RAM”), magnetic disk storage media, optical storage media, flash memory devices
  • machine readable transmission media e.g., electrical, optical, acoustical, or other forms of propagated signals (e.g., carrier waves, infrared signals, digital signals, etc.)

Abstract

A method and apparatus for routing and forwarding between virtual routers is described. A method in a single network element comprises peering a first virtual router to a second virtual router, wherein the first and second virtual routers have separate address spaces and separate routing tables, distributing a set of one or more routes from the first virtual router to the second virtual router, wherein a first of the set of routes identifies the first virtual router as a next hop of the first route, said first route including a destination, and downloading to a set of one or more forwarding tables, the destination and the next hop.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS
This application is a divisional of application Ser. No. 10/265,789, filed Oct. 7, 2002, now U.S. Pat. No. 6,907,039 which claims the benefit of U.S. Provisional Patent Application No. 60/397,353, entitled “Method and Apparatus for Routing and Forwarding Between Virtual Routers Within a Single Network Element” filed on Jul. 20, 2002, now issued as U.S. Pat. No. 6,907,039.
BACKGROUND OF THE INVENTION
1. Field of the Invention
The invention relates to the field of communication. More specifically, the invention relates to communication networks.
2. Background of the Invention
The development of virtual routers within a single network element provided certain benefits and functionality unavailable with legacy routers. For example, a single network element with virtual routers could service multiple Internet Service Providers and/or corporations with the single network element.
FIG. 1 (Prior Art) is a diagram of a single network element with virtual routers. In FIG. 1, a network element 101 includes virtual routers VR-A 111, VR-B 113, and VR-C 115. Each of the virtual routers 111, 113, and 115 respectively receive traffic from ingress ports 103A-103C and respectively transmit traffic out of the egress ports 151A-151C as illustrated in FIG. 1. The virtual router VR-A 111 receives traffic 109A from the ingress port 103A and transmits the traffic 109A out of the egress port 151A. The virtual router VR-B 113 receives traffic 109B from the ingress port 103B and transmits the traffic 109B out of the ingress port 151B. The virtual router VR-C 115 receives traffic 109C from the ingress port 103C and transmits the traffic 109C out of the egress port 151C.
Network elements that support the virtual routers, performed inter-VR forwarding based on the forwarding scheme described (i.e., with standard interfaces). If VR-A 111 received a packet for transmission to VR-B 113, then the VR-A 111 looked up the next hop in its routing table, found an interface that was associated with the ingress port 103B, and forwarded the packet based on that interface.
Despite the advantages offered by virtual routers and the capability of a single network element to behave as multiple routers, the virtual routers within a single network element do not communicate routing and/or forwarding information as if separate routers.
BRIEF SUMMARY OF THE INVENTION
A method and apparatus for routing and forwarding between virtual routers is described. According to one aspect of the invention, a method in a single network element provides for peering a first virtual router to a second virtual router, wherein the first and second virtual routers have separate address spaces and separate routing tables. A set of one or more routes are distributed from the first first virtual router to the second virtual router, wherein a first of the set of routes identifies the first virtual router as a next hop of the first route, said first route including a destination. In addition, the method provides for downloading to a set of one or more forwarding tables, the destination and the next hop.
These and other aspects of the present invention will be better described with reference to the Detailed Description and the accompanying Figures.
BRIEF DESCRIPTION OF THE DRAWINGS
The invention may best be understood by referring to the following description and accompanying drawings that are used to illustrate embodiments of the invention. In the drawings:
FIG. 1 (Prior Art) is a diagram of a single network element with virtual routers.
FIG. 2 is an exemplary diagram illustrating forwarding between virtual routers according to one embodiment of the invention.
FIG. 3A is an exemplary diagram illustrating peering of virtual routers according to one embodiment of the invention.
FIG. 3B is an exemplary diagram illustrating additional peering of virtual routers according to one embodiment of the invention.
FIG. 3C is an exemplary diagram illustrating inter-VR interfaces as local area network interfaces according to one embodiment of the invention.
FIG. 4 is an exemplary diagram illustrating external route distribution between virtual routers according to one embodiment of the invention.
FIG. 5 is a diagram of an exemplary network element according to one embodiment of the invention.
DETAILED DESCRIPTION OF THE INVENTION
In the following description, numerous specific details are set forth to provide a thorough understanding of the invention. However, it is understood that the invention may be practiced without these specific details. In other instances, well-known circuits, structures, standards, and techniques have not been shown in detail in order not to obscure the invention. The terms “routing table” and “forwarding table” are used throughout the description, but are not limited to being tables. A routing table and a forwarding table may be implemented with a variety of data structures (e.g., trees, tries, linked lists, hash tables, hybrid data structures, etc.).
FIG. 2 is an exemplary diagram illustrating forwarding between virtual routers according to one embodiment of the invention. FIG. 2 illustrates a network element 202 as including a virtual router 205A and a virtual router 205B. The virtual router 205A is identified as VR-A and the virtual router 205B is identified as VR-B.
The virtual router 205A includes interior gateway routing tables 209, an exterior gateway routing table 211, and a main routing table 213. Interior gateway routing protocol processes (e.g., OSPF, RIP, iBGP, IS-IS, etc.) build each of the interior gateway routing tables 209. The interior gateway routing tables 209 indicate routing information for reaching a destination, as determined by a corresponding interior gateway routing protocol process, that is internal to an autonomous system (AS), which includes the virtual router 205A. A process implementing an exterior gateway protocol (e.g., BGP-v4, EGP, etc.) builds the exterior gateway routing table 211. The exterior gateway routing table 211 indicates routing information for reaching destinations external to the AS of the virtual router 205A. The main routing table 213 is built using route entries from the interior gateway routing tables 209, the exterior gateway routing table 211, and interfaces from an interface manager 271.
The interface manager 271 includes a data structure that indicates interfaces and their corresponding reachable IP addresses via the interfaces. In certain embodiments of the invention, the interface manager also associates lower layer hardware information learned from lower layer protocols with interfaces. Each routing process exchanges routing information with other network elements through interfaces and install learned reachable routes into the main routing table, which are eventually downloaded into forwarding tables of the data plane from the main routing table in the control plane. The interface manager 271 indicates and maintains a status for each interface of the host network element. A routing process utilizes interface status to make correct routing decisions.
The first column of each entry within each of the routing tables 209, 211, and 213 indicates a destination. The last column of each entry within each of the routing tables 209, 211, and 213 as illustrated in FIG. 2 indicates a next hop. A next hop is either an interface next hop (i.e., a logical or physical interface) or a non-interface next hop (e.g., an IP address, a virtual router name, etc.). The remaining columns within each of the routing tables 209, 211, and 213 indicate additional routing information, such as line, metrics, etc.
The virtual router 205A also includes a forwarding module 207 and a forwarding table 219. The forwarding module 207 forwards packets that are received by the virtual router 205A in accordance with the forwarding table 219. The forwarding table 219 receives information downloaded from the main routing table.
In the example illustrated by FIG. 1, the interior gateway routing tables 209 includes internal destinations ID1, ID2, and ID3 with corresponding next hops I/F1, VR-B, and ADDRESS, respectively. ID1, ID2 and ID3 are identifying data (e.g., IP addresses, prefixes, etc.) of other network elements within the same AS as the virtual router 205A. One or more of the internal destinations may also be another virtual router within the same network element (e.g., ID1 may be VR-B). While in one embodiment of the invention, internal destinations that are other virtual routers are identified with a virtual router identifier (i.e., virtual router handle), alternative embodiments of the invention may identify an internal destination with other techniques (e.g., IP address, inter-VR interface, etc.). The next hop I/F is a physical interface and the next hop VR-B may be a logical interface that indicates a VR instead of an IP address (i.e., an inter-VR interface), a virtual router handle, etc.
An inter-virtual router next hop is a unique value within the network element 202 that identifies a specific virtual router. When an administrator creates a virtual router, the administrator provides a user-friendly virtual router identifier (“VR name”) for the created virtual router. In response to the creation of a virtual router, the network element 202 creates and associates a unique virtual router identifier (“VR identifier”) to be utilized by the network element 202 to identify the created virtual router. While in one embodiment inter-virtual router next hops in the routing tables are VR identifiers, alternative embodiments of the invention may utilize alternative techniques to identify inter-VR next hops (e.g., the routing table indicates the VR name and a table that associates the VR name to a VR identifier is used to access the VR identifier, an inter-VR interface value is created within the network element and associated with a VR-identifier or VR-name in another data structure, etc.). For the purposes of this description, an inter-VR next hop is the VR identifier.
The exterior gateway routing table 211 as illustrated in FIG. 2 indicates external destinations ED1, ED2, and ED3 and corresponding next hops ADDRESS, I/F2, and VR-B, respectively. As with the internal destinations, the external destinations ED1, ED2, and ED3 can be IP addresses, prefixes, etc. While in one embodiment of the invention, external destinations that are other virtual routers are identified by an IP address or prefix, in alternative embodiments of the invention the external destination may be a VR name or VR identifier.
When the forwarding module 207 receives a packet 201, the forwarding module 207 determines the destination of the packet 201. The destination of the packet 201 is looked up in the forwarding table 219 to determine the appropriate outgoing interface. If the destination of the packet 201 is ID1, then the forwarding module 207 forwards the packet 201 to an egress port that corresponds to the outgoing interface I/F. If the destination of the packet 201 is ED3, then the forwarding module 207 forwards the packet 201 to the virtual router 205B. If the packet 201 is forwarded to the virtual router 205B, the virtual router 205B will process the packet 201 in accordance with its forwarding/routing information (e.g., drop the packet 201, forward the packet 201 to the appropriate egress port, forward the packet 201 to another virtual router, etc.).
The decision mechanism for determining whether a packet will be forwarded to an egress port or another virtual router can be implemented with a variety of techniques. In one embodiment of the invention, the forwarding module determines if the next hop indicated by the forwarding table for a packet is an inter-VR next hop. If the next hop is an inter-VR next hop then the corresponding packet is forwarded to the appropriate virtual router. If the next hop is not an inter-VR next hop (e.g., a logical or physical interface that does not indicate a virtual router, an IP address, etc.), then the packet is processed accordingly (e.g., if the next hop is a physical interface, then the packet is processed at lower layers in order to forward the packet along the appropriate hardware lines to the egress port). In another embodiment of the invention, a switching module is implemented separately from the forwarding module. If the next hop for a packet is a physical interface, then the forwarding module passes the packet to the switching module, which forwards the packet along the hardware lines that correspond to the physical interface. If the next hop is an inter-VR next hop, then the forwarding module forwards the packet to the appropriate virtual router.
In addition other techniques can be used to determine whether the next hop is a virtual router, an IP address, a physical interface, a logical interface, etc. In one embodiment of the invention, an additional field is included in each routing and forwarding table entry to explicitly indicate a type for the outgoing interface. In another embodiment of the invention, the value of the next hop implicitly indicates whether the next hop is a VR next hop or non-VR next hop.
Enabling inter-VR routing and forwarding provides additional functionality. A service provider that is a customer of a network provider, which owns a network element with inter-VR routing and forwarding, can allow its virtual private network (VPN) customers to exchange routes. In addition, inter-VR routing and forwarding enables a service provider's VPN customers to use the provider's network for Internet access. Inter-VR routing and forwarding can also be utilized to allow service providers to announce VPN customers' routes if they are part of the public address space.
Inter-VR routing and forwarding also enables virtual routers to replace customer premise equipment (CPE) routers. The service provider and/or network provider can utilize a virtual router to perform the tasks typically performed by a CPE router, especially for those customers that access the network from multiple locations.
If multiple customers of a network provider are on the same network element with virtual routers, then inter-VR routing and forwarding enables local area, metro area, and/or intra-continental private peerings without utilizing physical lines and/or ports to connect virtual routers.
Inter-VR routing and forwarding also provides additional capabilities with respect to testing and parallel network inter-communication. Since virtual routers can be connected without wires, then numerous virtual routers can be peered or connected to represent the topology of actual networks. The inter-VR routing and forwarding can then be used to simulate routing in different network topologies without cables and wires. For parallel network inter-communication, a service provider with an operational legacy network and a next generation network can utilize inter-VR routing and forwarding for experimental, trial, and/or operational exchanges of routes between the different networks (assuming the different networks include virtual routers within individual network elements). Moreover, the service provider can utilize inter-VR routing and forwarding to migrate their customers from a legacy network to a next generation network.
FIGS. 3A-3C are exemplary diagrams illustrating interior gateway routing tables being built with inter-VR routes according to one embodiment of the invention. FIG. 3A is an exemplary diagram illustrating peering of virtual routers according to one embodiment of the invention. In FIG. 3A, a virtual router 303A (VR-A) is peered with virtual routers 303B and 303C. The virtual routers 303A, 303B, and 303C respectively have IP addresses 10.1.1.1, 10.1.1.2, and 10.1.1.3. The virtual routers are peered with static routing (i.e., an administrator configures the connections between the virtual routers). An administrator configures an inter-VR interface 315L.B on the virtual router 303A to reach the virtual router 303B and an inter-VR interface 315L.C also on the virtual router 303A to reach the virtual router 303C. While configuring the interfaces on the virtual router 303A, the administrator also configures inter-VR interfaces 315B.L and 315C.L respectively on the virtual routers 303B and 303C. In response to the configuration, the interior gateway routing tables of the virtual routers are updated.
An interior gateway routing tables 307A for the virtual router 303A is updated to include a routing entry that indicates destination 10.1.1.2 reachable via next hop VR-B and a destination 10.1.1.3 reachable via next hop VR-C. While in one embodiment, the next hops to a virtual router are indicated with a VR identifier, alternative embodiments of the invention may indicate a virtual router next hop with the virtual router's name or IP address.
An interior gateway routing tables 307B for the virtual router 303B is updated to include a routing entry that indicates a destination 10.1.1.1 reachable via inter-VR interface 315B.L, which is the VR identifier for the virtual router 303A. An interior gateway routing tables 307C for the virtual router 303C is updated to include a routing entry that indicates the destination 10.1.1.1 reachable via inter-VR interface 315C.L.
In an embodiment that processes packets sent over inter-VR interfaces with a single routing process, a packet can be processed without inter-process communication. For example, if RIP is configured on inter-VR interface 315L.B and the RIP process sends a packet over the inter-VR interface 315L.B, the RIP packet immediately considers the packet as received on the inter-VR interface 315B.L by the single RIP process. Routing processes (both interior and exterior gateway routing protocol processes) can exchange routing information via the inter-VR interfaces. The routing processes download these routes into the main routing table using inter-VR interfaces as next hops.
FIG. 3B is an exemplary diagram illustrating peering of virtual routers that are not virtual router local (virtual router 303A) according to one embodiment of the invention. In FIG. 3B, the virtual routers 303B and 303C have been connected. The virtual router 303B has been configured to reach the virtual router 303C via the inter-VR interface 315B.C and the virtual router 303C has been configured to reach the virtual router 303B via the inter-VR interface 315C.B. Various techniques can be implemented to prevent redundant connections being created between virtual routers. In one embodiment of the invention, a check is performed when the administrator enters a configuration that binds interfaces of two virtual routers.
In another embodiment of the invention, an inter-VR point-to-point (p2p) interface is utilized. The interface manager ensures only a single bind number is utilized to connect a pair of virtual routers, although alternative embodiments of the invention may allow for multiple connections between virtual routers. An interior gateway routing protocol process registers an interest in the configured interfaces for each virtual router with the interface manager. In response, the interface manager provides the registering interior gateway routing protocol process with the corresponding bind number, bound virtual router, and the type of interface. For example, assume the following configuration is entered:
    • virtualrouter A
    • interface I/F1 inter-VR-p2p bind1
    • igp router networkA
    • virtualrouter B
    • interface I/F2 inter-VR-p2p bind1
    • igp router networkB
The first set of configuration commands configures the interface I/F1 on the virtual router A. The second set of commands configures the interface I/F2 on the virtual router B. The interface manager creates a tuple that reflects the configuration of these interfaces on their corresponding virtual routers. When the interior gateway routing protocol process learns this inter-VR interface binding from the interface state manager, the interior gateway routing protocol process can do peering between VR-A and VR-B across this inter-VR interface as if VR-A and VR-B were two separate network elements.
FIG. 3C is an exemplary diagram illustrating inter-VR interfaces as local area network interfaces according to one embodiment of the invention. In FIG. 3C, each of the virtual routers 303A, 303B and 303C are connected to a virtual router local area network (VR-LAN) 323. The VR-LAN 323 is identified as VR-LAN-1. Although the virtual routers 303A, 303B and 303C are illustrated as being connected to the VR-LAN 323 for this example, fewer or more virtual routers may be connected to the VR-LAN. In addition, multiple VR-LANs can be defined with various different groups of virtual routers connected to the different VR-LANS. For example, VR-B, VR-C and VR-A may be connected to VR-LAN-1, while VR-A, VR-C are connected to VR-LAN-2. Alternatively, VR-LAN-1 may comprise VR-A, VR-B and VR-C while VR-LAN-2 may comprise VR-A, VR-B, and VR-C.
After the administrator configures VR-LAN interfaces 315L.V, 315B.V, and 315C.V respectively on the virtual routers 303A, 303B and 303C, the interior gateway routing protocol process registers an interest in the interface 315L.V for the virtual router 303A with the interface manager. The interface manager provides the registering interior gateway routing protocol process with the associated VR-LAN number, VR-LAN-1, which identifies the VR-LAN 323. While in one embodiment of the invention, the interior gateway routing protocol process accesses a data structure (e.g., a linked list) which indicates each VR-LAN interface associated with the VR-LAN identified by the interface manager, alternative embodiments of the invention may provide the interior gateway routing protocol process the associated VR-LAN interfaces differently (e.g., the interface manager may maintain a data structure that indicates the VR-LAN and associated VR-LAN interfaces). The interior gateway routing protocol process updates its interior gateway routing tables to indicate the associated VR-LAN interfaces as illustrated in FIG. 3C. In an alternative embodiment of the invention, the interior gateway routing protocol process accesses the VR-LAN data structure that indicates associated VR-LAN interfaces instead of inserting the data structure in the interior gateway routing table. When the interior gateway routing protocol process transmits a control packet, the interior gateway routing protocol processes transmits to each VR-LAN interface associated with the VR-LAN. After transmitting the control packet, the interior gateway routing protocol process marks the associated VR-LAN interfaces as received. For example, assume OSPF is configured on interfaces 315L.V, 315B.V, 315C.V. If OSPF sends a packet on 315B.V to the VR-LAN 323 for the VR-B 303B, the sent OSPF packet is implicitly received on the interfaces 315L.V and 315C.V. In an embodiment that implements a single routing process for more than one virtual router, the single routing process (e.g., OSPF) handles the sending and receiving without inter-process communication.
Regardless of the interface technique being used, packets forwarded between virtual routers are passed directly between virtual routers and not passed down for lower layer processing. In alternative embodiments of the invention, packets may be passed down for lower layer processing (e.g., to the kernel socket, which is a communication channel between routing processes and the data plane that includes line cards) to maintain agnostic routing or minimize the amount of modification made to routing protocols.
FIG. 4 is an exemplary diagram illustrating external route distribution between virtual routers according to one embodiment of the invention. In FIG. 4, a virtual router 401 with IP address 10.1.1.1 is peered with virtual routers 403A and 403B via inter-VR interfaces 415L.B and 415L.C, respectively. The peering is established with either static routing or with interior gateway routing protocol process. The virtual routers 401, 403A and 403B respectively have exterior gateway routing tables 405, 407A and 407B. The bolded entries in the exterior gateway routing tables 405, 407A, and 407B have been learned from other virtual routers.
The virtual router 401 has learned routes to external destinations ED2 and ED7 directly from virtual routers 403A and 403B, respectively. The virtual router 403A has learned routes to external destinations ED1 and ED7 from the virtual router 401. The virtual router 403B has learned routes to external destinations ED1, ED2, and ED5 from the virtual router 401.
Various route distribution policies can be applied to distribution of routes between virtual routers. If a customer does not want routes from its virtual router distributed, then the customer's virtual router should not be peered with any other virtual routers that do not fall under the customer's control. A policy may be implemented on a network element that allows the virtual router local to learn routes but not distribute routers. Alternatively, certain routes may be tagged as either restricted or unrestricted for inter-VR route distribution.
FIG. 5 is a diagram of an exemplary network element according to one embodiment of the invention. In FIG. 5, a network element 500 includes a control card 503 coupled with a set of line cards 515A-515C via a transmission medium 551 (e.g., a packet mesh, switching medium, etc.). The control card 503 hosts external routing processes 505A-505F and corresponding exterior gateway routing tables 507A-507F. The control card 503 also hosts internal routing processes 506A-506F and corresponding interior gateway routing tables 509A-509F. Each of the internal routing processes 506A-506F and their corresponding VR interior gateway routing tables 509A-509F are used by a different virtual router configured on the network element 500. Each of the external routing processes 505A-505F and their corresponding VR exterior gateway routing tables 507A-507F are used by the different virtual router configured on the network element 500.
Each of the line cards 515A-515C include one or more forwarding tables. The line card 515A includes VR forwarding tables 517A-517F. The line card 515B includes VR forwarding tables 517B-517E. The line card 515C includes the VR forwarding table 517A. The forwarding tables 517A-517F are created from forwarding information downloaded from the control card 503. Each of the VR forwarding tables corresponds to a different virtual router configured on the network element 500. In an alternative embodiment of the invention, a virtual router uses more than one VR forwarding table, VR interior gateway routing table, and/or VR exterior gateway routing table. In another alternative embodiment of the invention, a single external and/or internal routing process is shared by different virtual routers.
The control card 503 and line cards 517A - 517C illustrated in FIG. 5 and the network elements described in the Figures include memories, processors, and/or ASICs. Such memories include a machine-readable medium on which is stored a set of instructions (i.e., software) embodying any one, or all, of the methodologies described herein. Software can reside, completely or at least partially, within this memory and/or within the processor and/or ASICs. For the purpose of this specification, the term “machine-readable medium” shall be taken to include any mechanism that provides (i.e., stores and/or transmits) information in a form readable by a machine (e.g., a computer). For example, a machine-readable medium includes machine readable storage media (e.g., read only memory (“ROM”), random access memory (“RAM”), magnetic disk storage media, optical storage media, flash memory devices), machine readable transmission media (e.g., electrical, optical, acoustical, or other forms of propagated signals (e.g., carrier waves, infrared signals, digital signals, etc.)), etc.
While the invention has been described in terms of several embodiments, those skilled in the art will recognize that the invention is not limited to the embodiments described. The method and apparatus of the invention can be practiced with modification and alteration within the spirit and scope of the appended claims The description is thus to be regarded as illustrative instead of limiting on the invention.

Claims (16)

1. A non-transitory computer-readable storage medium that provides instructions which, when executed by a set of one or more processors, cause said set of processors to perform operations within a single network element comprising:
instantiating a first and second virtual router in the single network element;
indicating for a route a first logical interface as a next hop for a destination, wherein a logical interface couples virtual routers internally within the single network element, said first logical interface identifying the first virtual router, said first virtual router including a first routing table;
inserting said route into a second routing table of the second virtual router, wherein said first routing table is for a first address space different than the second routing table's address space and the first routing table has different content than the second routing table;
forwarding packets directly from the second virtual router to the first virtual router with the logical interface without lower layer processing.
2. The computer-readable storage medium of claim 1 further comprising:
indicating for a second route a second logical interface as a second next hop for a second destination, said second logical interface identifying the second virtual router;
inserting said second route into the first routing table; and
exchanging route information between the first and second virtual routers via the second and first logical interfaces.
3. The computer-readable storage medium of claim 1 further comprising downloading the destination and the first logical interface to a data plane.
4. The computer-readable storage medium of claim 1 further comprising:
transmitting a packet from the second virtual router to a third virtual router via a second logical interface that identifies a virtual local area network (VLAN); and
receiving the packet on a third logical interface associated with the VLAN and the third virtual router.
5. A non-transitory computer-readable storage medium that provides instructions, which, when executed by a set of one or more processors, cause said set of processors to perform operations within a single network element comprising:
instantiating a first and second virtual router in the single network element;
peering the first virtual router to the second virtual router through a first logical interface, wherein the first logical interface couples the first and second virtual routers internally within the single network element, the first and second virtual routers have separate address spaces and separate routing tables, and the routing table for the first virtual router has different content that the routing table for the second virtual router;
distributing a set of one or more routes from the first virtual router to the second virtual router, wherein a first of the set of routes identifies the first virtual router as a next hop of the first route, said first route including a destination;
downloading to a set of one or more forwarding tables, the destination and the next hop; and
forwarding packets directly from the second virtual router to the first virtual router with the logical interface without lower layer processing.
6. The computer-readable storage medium of claim 5 wherein said peering comprises:
generating the first logical interface that indicates the first virtual router;
generating a second logical interface that indicates the second virtual router;
associating the first logical interface with the second virtual router; and
associating the second logical interface with the first virtual router.
7. The computer-readable storage medium of claim 6 further comprising a routing protocol process exchanging routing information via the first and second logical interlaces.
8. The computer-readable storage medium of claim 5 wherein the next hop is a logical interface that indicates the first virtual router.
9. The computer-readable storage medium of claim 5 wherein the next hop is the first virtual router's identifier.
10. The computer-readable storage medium of claim 5 further comprising associating the first and second virtual routers with a virtual local area network (VLAN).
11. The computer-readable storage medium of claim 10 wherein said associating comprises:
generating in said second virtual router's routing table a first route that includes said VLAN as a destination and the first logical interface that indicates said first virtual router; and
generating in said first virtual router's routing table a second route that includes said VLAN as a destination and a second logical interface that indicates said second virtual router.
12. The computer-readable storage medium of claim 10 further comprising said first and second virtual routers exchanging routing information via the VLAN.
13. A non-transitory computer-readable storage medium that provides instructions which, when executed by a set of one or more processors, cause said set of processors to perform operations within a single network element comprising:
instantiating a first and second virtual router in the single network element;
inserting in a first virtual router's routing table a route, said route indicating a destination and a logical interface, wherein the logical interface couples virtual routers internally within the single network element, said logical interface identifying a second virtual router, wherein said first virtual router corresponds to a first address space different from a second address space that corresponds to the second virtual router and the first routing table has different content than the second routing table;
downloading the route to a forwarding table; and
forwarding packets directly from the first virtual router to the second virtual router with the logical interface without lower layer processing.
14. The computer-readable storage medium of claim 13 wherein said logical interface is the second virtual router's identifier.
15. The computer-readable storage medium of claim 13 further comprising said first virtual router exchanges routing information with said second virtual router via said route.
16. The computer-readable storage medium of claim 13 further comprising forwarding a packet from said first virtual router to said second virtual router in accordance with said logical interface indicated in said forwarding table.
US10/883,070 2002-07-20 2004-06-30 Method and apparatus for routing and forwarding between virtual routers within a single network element Active 2026-03-21 US7948994B2 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US10/883,070 US7948994B2 (en) 2002-07-20 2004-06-30 Method and apparatus for routing and forwarding between virtual routers within a single network element
US13/087,337 US8472451B2 (en) 2002-07-20 2011-04-14 Method and apparatus for routing and forwarding between virtual routers within a single network element

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US39735302P 2002-07-20 2002-07-20
US10/265,789 US6907039B2 (en) 2002-07-20 2002-10-07 Method and apparatus for routing and forwarding between virtual routers within a single network element
US10/883,070 US7948994B2 (en) 2002-07-20 2004-06-30 Method and apparatus for routing and forwarding between virtual routers within a single network element

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US10/265,789 Division US6907039B2 (en) 2002-07-20 2002-10-07 Method and apparatus for routing and forwarding between virtual routers within a single network element

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US13/087,337 Continuation US8472451B2 (en) 2002-07-20 2011-04-14 Method and apparatus for routing and forwarding between virtual routers within a single network element

Publications (2)

Publication Number Publication Date
US20040240455A1 US20040240455A1 (en) 2004-12-02
US7948994B2 true US7948994B2 (en) 2011-05-24

Family

ID=30448088

Family Applications (8)

Application Number Title Priority Date Filing Date
US10/265,789 Expired - Lifetime US6907039B2 (en) 2002-07-20 2002-10-07 Method and apparatus for routing and forwarding between virtual routers within a single network element
US10/883,070 Active 2026-03-21 US7948994B2 (en) 2002-07-20 2004-06-30 Method and apparatus for routing and forwarding between virtual routers within a single network element
US10/883,425 Active 2025-11-11 US8045547B2 (en) 2002-07-20 2004-06-30 Method and apparatus for routing and forwarding between virtual routers within a single network element
US10/883,109 Active 2025-12-08 US7715381B2 (en) 2002-07-20 2004-06-30 Method and apparatus for routing and forwarding between virtual routers within a single network element
US13/087,337 Expired - Lifetime US8472451B2 (en) 2002-07-20 2011-04-14 Method and apparatus for routing and forwarding between virtual routers within a single network element
US13/281,194 Active 2025-10-24 US9246791B2 (en) 2002-07-20 2011-10-25 Method and apparatus for routing and forwarding between virtual routers within a single network element
US14/985,133 Expired - Lifetime US10116556B2 (en) 2002-07-20 2015-12-30 Techniques for routing and forwarding between multiple virtual routers implemented by a single device
US16/121,618 Abandoned US20190007312A1 (en) 2002-07-20 2018-09-04 Techniques for routing and forwarding between multiple virtual routers implemented by a single device

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US10/265,789 Expired - Lifetime US6907039B2 (en) 2002-07-20 2002-10-07 Method and apparatus for routing and forwarding between virtual routers within a single network element

Family Applications After (6)

Application Number Title Priority Date Filing Date
US10/883,425 Active 2025-11-11 US8045547B2 (en) 2002-07-20 2004-06-30 Method and apparatus for routing and forwarding between virtual routers within a single network element
US10/883,109 Active 2025-12-08 US7715381B2 (en) 2002-07-20 2004-06-30 Method and apparatus for routing and forwarding between virtual routers within a single network element
US13/087,337 Expired - Lifetime US8472451B2 (en) 2002-07-20 2011-04-14 Method and apparatus for routing and forwarding between virtual routers within a single network element
US13/281,194 Active 2025-10-24 US9246791B2 (en) 2002-07-20 2011-10-25 Method and apparatus for routing and forwarding between virtual routers within a single network element
US14/985,133 Expired - Lifetime US10116556B2 (en) 2002-07-20 2015-12-30 Techniques for routing and forwarding between multiple virtual routers implemented by a single device
US16/121,618 Abandoned US20190007312A1 (en) 2002-07-20 2018-09-04 Techniques for routing and forwarding between multiple virtual routers implemented by a single device

Country Status (5)

Country Link
US (8) US6907039B2 (en)
AU (1) AU2003253747A1 (en)
GB (4) GB2427786B (en)
HK (1) HK1091621A1 (en)
WO (1) WO2004010654A1 (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090327903A1 (en) * 2006-07-06 2009-12-31 Referentia Systems, Inc. System and Method for Network Topology and Flow Visualization
US8660129B1 (en) 2012-02-02 2014-02-25 Cisco Technology, Inc. Fully distributed routing over a user-configured on-demand virtual network for infrastructure-as-a-service (IaaS) on hybrid cloud networks
US9154327B1 (en) 2011-05-27 2015-10-06 Cisco Technology, Inc. User-configured on-demand virtual layer-2 network for infrastructure-as-a-service (IaaS) on a hybrid cloud network

Families Citing this family (199)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8213431B2 (en) * 2008-01-18 2012-07-03 The Boeing Company System and method for enabling wireless real time applications over a wide area network in high signal intermittence environments
US7389358B1 (en) 2000-09-13 2008-06-17 Fortinet, Inc. Distributed virtual system to support managed, network-based services
US8250357B2 (en) * 2000-09-13 2012-08-21 Fortinet, Inc. Tunnel interface for securing traffic over a network
US7272643B1 (en) 2000-09-13 2007-09-18 Fortinet, Inc. System and method for managing and provisioning virtual routers
US7444398B1 (en) 2000-09-13 2008-10-28 Fortinet, Inc. System and method for delivering security services
US7111072B1 (en) * 2000-09-13 2006-09-19 Cosine Communications, Inc. Packet routing system and method
US7487232B1 (en) 2000-09-13 2009-02-03 Fortinet, Inc. Switch management system and method
US7574495B1 (en) 2000-09-13 2009-08-11 Fortinet, Inc. System and method for managing interworking communications protocols
US6885635B1 (en) * 2000-11-21 2005-04-26 Juniper Networks, Inc. High capacity router having redundant components
US6529481B2 (en) * 2000-11-30 2003-03-04 Pluris, Inc. Scalable and fault-tolerant link state routing protocol for packet-switched networks
US7181547B1 (en) * 2001-06-28 2007-02-20 Fortinet, Inc. Identifying nodes in a ring network
US7630358B1 (en) * 2001-07-09 2009-12-08 Sable Networks, Inc. Mechanism for implementing multiple logical routers within a single physical router
US7161904B2 (en) 2002-06-04 2007-01-09 Fortinet, Inc. System and method for hierarchical metering in a virtual router based network switch
US7203192B2 (en) 2002-06-04 2007-04-10 Fortinet, Inc. Network packet steering
US7116665B2 (en) 2002-06-04 2006-10-03 Fortinet, Inc. Methods and systems for a distributed provider edge
US7376125B1 (en) * 2002-06-04 2008-05-20 Fortinet, Inc. Service processing switch
US6907039B2 (en) * 2002-07-20 2005-06-14 Redback Networks Inc. Method and apparatus for routing and forwarding between virtual routers within a single network element
US7480256B2 (en) * 2002-08-14 2009-01-20 Pluris, Inc. Scalable and fault-tolerant link state routing protocol for packet-switched networks
US7096383B2 (en) 2002-08-29 2006-08-22 Cosine Communications, Inc. System and method for virtual router failover in a network routing system
US20040078772A1 (en) * 2002-10-16 2004-04-22 Cosine Communications, Inc. Dynamic route exchange
US7266120B2 (en) 2002-11-18 2007-09-04 Fortinet, Inc. System and method for hardware accelerated packet multicast in a virtual routing system
US7489700B2 (en) * 2002-11-20 2009-02-10 Hitachi Communication Technologies, Ltd. Virtual access router
EP1429497B1 (en) * 2002-12-09 2016-03-02 Alcatel Lucent Method of relaying traffic from a source to a targeted destination in a communications network and corresponding equipment
US7486659B1 (en) * 2003-02-24 2009-02-03 Nortel Networks Limited Method and apparatus for exchanging routing information between virtual private network sites
US7617327B1 (en) * 2003-03-17 2009-11-10 Network Equipment Technologies, Inc. Method and system for implementing external applications using remote socket application programming interface for virtual routers
US7673070B1 (en) * 2003-03-17 2010-03-02 Network Equipment Technologies, Inc. Method of sharing telecommunications node equipment facilities
US6970464B2 (en) * 2003-04-01 2005-11-29 Cisco Technology, Inc. Method for recursive BGP route updates in MPLS networks
US7720095B2 (en) 2003-08-27 2010-05-18 Fortinet, Inc. Heterogeneous media packet bridging
US8838743B2 (en) * 2004-02-13 2014-09-16 Intel Corporation Apparatus and method for a dynamically extensible virtual switch
US7730294B2 (en) * 2004-06-04 2010-06-01 Nokia Corporation System for geographically distributed virtual routing
DE112005001934T5 (en) * 2004-08-10 2007-07-05 MeshNetworks, Inc., Maitland Software architecture and hardware abstraction layer for multi-routing and method of providing the same
US7519009B2 (en) * 2004-09-29 2009-04-14 The Boeing Company Virtual exterior gateway protocol and related methods
US7808904B2 (en) * 2004-11-18 2010-10-05 Fortinet, Inc. Method and apparatus for managing subscriber profiles
US8254285B2 (en) * 2005-02-25 2012-08-28 Ip Infusion, Inc. Hardware abstraction layer
US7760742B2 (en) * 2005-03-15 2010-07-20 Hewlett-Packard Development Company, L.P. Systems and methods of using pseudo-routes for data transmissions
CA2611527A1 (en) * 2005-06-09 2006-12-21 Whirlpool Corporation Software architecture system and method for communication with, and management of, at least one component within a household appliance
US8442042B2 (en) * 2005-06-09 2013-05-14 Whirlpool Corporation Appliance and a consumable holder with an embedded virtual router
US7761595B1 (en) * 2006-01-25 2010-07-20 Sprint Communications Company L.P. Dynamic server addition using virtual routing
US7668920B2 (en) * 2006-03-01 2010-02-23 Fortinet, Inc. Electronic message and data tracking system
US8619771B2 (en) 2009-09-30 2013-12-31 Vmware, Inc. Private allocated networks over shared communications infrastructure
US8924524B2 (en) 2009-07-27 2014-12-30 Vmware, Inc. Automated network configuration of virtual machines in a virtual lab data environment
US8892706B1 (en) 2010-06-21 2014-11-18 Vmware, Inc. Private ethernet overlay networks over a shared ethernet in a virtual environment
US7522595B2 (en) * 2006-06-16 2009-04-21 Cisco Technology, Inc. Communicating packets between forwarding contexts using virtual interfaces
CN100579072C (en) * 2006-12-22 2010-01-06 华为技术有限公司 Method and system for communication between IP devices
US8295295B2 (en) * 2007-01-24 2012-10-23 Cooper Technologies Company System and method for automatically segmenting and merging routing domains within networks
US8340090B1 (en) * 2007-03-08 2012-12-25 Cisco Technology, Inc. Interconnecting forwarding contexts using u-turn ports
US7933198B1 (en) 2007-05-30 2011-04-26 Foundry Networks, Llc Virtual router failover dampening
US8954601B1 (en) * 2007-06-15 2015-02-10 Juniper Networks, Inc. Authentication and encryption of routing protocol traffic
US20090210523A1 (en) * 2008-02-14 2009-08-20 Matthew Edward Duggan Network management method and system
US8195774B2 (en) 2008-05-23 2012-06-05 Vmware, Inc. Distributed virtual switch for virtualized computer systems
TW201018140A (en) * 2008-10-16 2010-05-01 Chunghwa Telecom Co Ltd System and method for protecting data of network user
EP2457409A1 (en) * 2009-07-24 2012-05-30 Nokia Siemens Networks OY Method and device for conveying traffic in a proxy mobile ip system
US20110032830A1 (en) * 2009-08-06 2011-02-10 Jacobus Van Der Merwe Live Router Migration
US7937438B1 (en) 2009-12-07 2011-05-03 Amazon Technologies, Inc. Using virtual networking devices to manage external connections
US9036504B1 (en) 2009-12-07 2015-05-19 Amazon Technologies, Inc. Using virtual networking devices and routing information to associate network addresses with computing nodes
US9203747B1 (en) 2009-12-07 2015-12-01 Amazon Technologies, Inc. Providing virtual networking device functionality for managed computer networks
US8995301B1 (en) 2009-12-07 2015-03-31 Amazon Technologies, Inc. Using virtual networking devices to manage routing cost information
US7953865B1 (en) 2009-12-28 2011-05-31 Amazon Technologies, Inc. Using virtual networking devices to manage routing communications between connected computer networks
US8224971B1 (en) 2009-12-28 2012-07-17 Amazon Technologies, Inc. Using virtual networking devices and routing information to initiate external actions
US7991859B1 (en) 2009-12-28 2011-08-02 Amazon Technologies, Inc. Using virtual networking devices to connect managed computer networks
US8615014B2 (en) * 2010-03-03 2013-12-24 Iwebgate Technology Limited System and method for multiple concurrent virtual networks
US9425986B2 (en) * 2010-03-03 2016-08-23 Iwebgate Technology Limited System and method for multiple concurrent virtual networks
US9413649B2 (en) * 2010-03-12 2016-08-09 Force10 Networks, Inc. Virtual network device architecture
US9525647B2 (en) 2010-07-06 2016-12-20 Nicira, Inc. Network control apparatus and method for creating and modifying logical switching elements
US9680750B2 (en) 2010-07-06 2017-06-13 Nicira, Inc. Use of tunnels to hide network addresses
US8958292B2 (en) 2010-07-06 2015-02-17 Nicira, Inc. Network control apparatus and method with port security controls
US8964528B2 (en) 2010-07-06 2015-02-24 Nicira, Inc. Method and apparatus for robust packet distribution among hierarchical managed switching elements
CN102959908B (en) 2010-11-22 2016-04-20 日本电气株式会社 For the communication system of the forward-path of control packet stream, communication equipment, controller and method and program
US9009217B1 (en) * 2011-01-06 2015-04-14 Amazon Technologies, Inc. Interaction with a virtual network
CN102123097B (en) * 2011-03-14 2015-05-20 杭州华三通信技术有限公司 Method and device for protecting router
WO2011113394A2 (en) * 2011-04-27 2011-09-22 华为技术有限公司 Router, virtual cluster router system and establishion method thereof
CN107071087B (en) 2011-08-17 2021-01-26 Nicira股份有限公司 Logical L3 routing
US9185056B2 (en) * 2011-09-20 2015-11-10 Big Switch Networks, Inc. System and methods for controlling network traffic through virtual switches
US8953599B1 (en) * 2012-06-29 2015-02-10 Juniper Networks, Inc. Traffic cut-through within network device having multiple virtual network devices
US9787567B1 (en) 2013-01-30 2017-10-10 Big Switch Networks, Inc. Systems and methods for network traffic monitoring
JP6014279B2 (en) * 2013-02-06 2016-10-25 華為技術有限公司Huawei Technologies Co.,Ltd. Method, device and routing system for network virtualization data transmission
US9571386B2 (en) 2013-07-08 2017-02-14 Nicira, Inc. Hybrid packet processing
US9407580B2 (en) 2013-07-12 2016-08-02 Nicira, Inc. Maintaining data stored with a packet
US9344349B2 (en) 2013-07-12 2016-05-17 Nicira, Inc. Tracing network packets by a cluster of network controllers
US9282019B2 (en) 2013-07-12 2016-03-08 Nicira, Inc. Tracing logical network packets through physical network
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
US9577845B2 (en) 2013-09-04 2017-02-21 Nicira, Inc. Multiple active L3 gateways for logical networks
US9503371B2 (en) 2013-09-04 2016-11-22 Nicira, Inc. High availability 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
US9575782B2 (en) 2013-10-13 2017-02-21 Nicira, Inc. ARP for logical router
US10063458B2 (en) 2013-10-13 2018-08-28 Nicira, Inc. Asymmetric connection with external networks
CN104579728B (en) * 2013-10-17 2019-02-26 中兴通讯股份有限公司 Network element device configuration and management method, device and network element device
US9374294B1 (en) 2013-11-05 2016-06-21 Cisco Technology, Inc. On-demand learning in overlay networks
US9769078B2 (en) 2013-11-05 2017-09-19 Cisco Technology, Inc. Dynamic flowlet prioritization
US10778584B2 (en) 2013-11-05 2020-09-15 Cisco Technology, Inc. System and method for multi-path load balancing in network fabrics
US10951522B2 (en) 2013-11-05 2021-03-16 Cisco Technology, Inc. IP-based forwarding of bridged and routed IP packets and unicast ARP
US9674086B2 (en) 2013-11-05 2017-06-06 Cisco Technology, Inc. Work conserving schedular based on ranking
US9655232B2 (en) 2013-11-05 2017-05-16 Cisco Technology, Inc. Spanning tree protocol (STP) optimization techniques
US9825857B2 (en) 2013-11-05 2017-11-21 Cisco Technology, Inc. Method for increasing Layer-3 longest prefix match scale
US9502111B2 (en) 2013-11-05 2016-11-22 Cisco Technology, Inc. Weighted equal cost multipath routing
US9397946B1 (en) 2013-11-05 2016-07-19 Cisco Technology, Inc. Forwarding to clusters of service nodes
US9876711B2 (en) 2013-11-05 2018-01-23 Cisco Technology, Inc. Source address translation in overlay networks
US9509092B2 (en) 2013-11-06 2016-11-29 Cisco Technology, Inc. System and apparatus for network device heat management
US9967199B2 (en) 2013-12-09 2018-05-08 Nicira, Inc. Inspecting operations of a machine to detect elephant flows
US10193771B2 (en) 2013-12-09 2019-01-29 Nicira, Inc. Detecting and handling elephant flows
US9996467B2 (en) 2013-12-13 2018-06-12 Nicira, Inc. Dynamically adjusting the number of flows allowed in a flow table cache
US9569368B2 (en) 2013-12-13 2017-02-14 Nicira, Inc. Installing and managing flows in a flow table cache
US9419855B2 (en) 2014-03-14 2016-08-16 Nicira, Inc. Static routes for logical routers
US9590901B2 (en) 2014-03-14 2017-03-07 Nicira, Inc. Route advertisement by managed gateways
US9225597B2 (en) 2014-03-14 2015-12-29 Nicira, Inc. Managed gateways peering with external router to attract ingress packets
US9313129B2 (en) 2014-03-14 2016-04-12 Nicira, Inc. Logical router processing by network controller
US9503321B2 (en) 2014-03-21 2016-11-22 Nicira, Inc. Dynamic routing for logical routers
US9647883B2 (en) 2014-03-21 2017-05-09 Nicria, Inc. Multiple levels of 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
US10193806B2 (en) 2014-03-31 2019-01-29 Nicira, Inc. Performing a finishing operation to improve the quality of a resulting hash
US9385954B2 (en) 2014-03-31 2016-07-05 Nicira, Inc. Hashing techniques for use in a network environment
US9985896B2 (en) 2014-03-31 2018-05-29 Nicira, Inc. Caching of service decisions
US9769685B1 (en) 2014-04-01 2017-09-19 Sprint Communications Company L.P. Long term evolution (LTE) network management system to process and display internet protocol usage data
US9742881B2 (en) 2014-06-30 2017-08-22 Nicira, Inc. Network virtualization using just-in-time distributed capability for classification encoding
US10270645B2 (en) 2014-07-21 2019-04-23 Big Switch Networks, Inc. Systems and methods for handling link aggregation failover with a controller
US9768980B2 (en) 2014-09-30 2017-09-19 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
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
US10469342B2 (en) 2014-10-10 2019-11-05 Nicira, Inc. Logical network traffic analysis
US9985882B2 (en) 2014-10-29 2018-05-29 Metaswitch Networks Ltd Packet data routing
US10116493B2 (en) 2014-11-21 2018-10-30 Cisco Technology, Inc. Recovering from virtual port channel peer failure
US10079779B2 (en) 2015-01-30 2018-09-18 Nicira, Inc. Implementing logical router uplinks
US9813323B2 (en) 2015-02-10 2017-11-07 Big Switch Networks, Inc. Systems and methods for controlling switches to capture and monitor network traffic
US10038628B2 (en) 2015-04-04 2018-07-31 Nicira, Inc. Route server mode for dynamic routing between logical and physical networks
US10348625B2 (en) 2015-06-30 2019-07-09 Nicira, Inc. Sharing common L2 segment in a virtual distributed router environment
US10230629B2 (en) 2015-08-11 2019-03-12 Nicira, Inc. Static route configuration for logical router
US10057157B2 (en) 2015-08-31 2018-08-21 Nicira, Inc. Automatically advertising NAT routes between logical routers
US10095535B2 (en) 2015-10-31 2018-10-09 Nicira, Inc. Static route types for logical routers
US9985867B2 (en) * 2015-12-11 2018-05-29 Cisco Technology, Inc. Optimizing EVPN for data centers with redundant top-of-rack deployments
US10142163B2 (en) 2016-03-07 2018-11-27 Cisco Technology, Inc BFD over VxLAN on vPC uplinks
WO2017161340A1 (en) * 2016-03-18 2017-09-21 Coco Communications Corp. Systems and methods for sharing network information
US10333849B2 (en) 2016-04-28 2019-06-25 Nicira, Inc. Automatic configuration of logical routers on edge nodes
US10841273B2 (en) 2016-04-29 2020-11-17 Nicira, Inc. Implementing logical DHCP servers in logical networks
US10484515B2 (en) 2016-04-29 2019-11-19 Nicira, Inc. Implementing logical metadata proxy servers in logical networks
US10091161B2 (en) 2016-04-30 2018-10-02 Nicira, Inc. Assignment of router ID for logical routers
US10333828B2 (en) 2016-05-31 2019-06-25 Cisco Technology, Inc. Bidirectional multicasting over virtual port channel
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
US11509501B2 (en) 2016-07-20 2022-11-22 Cisco Technology, Inc. Automatic port verification and policy application for rogue devices
US10630576B2 (en) * 2016-08-05 2020-04-21 Huawei Technologies Co., Ltd. Virtual network routing to dynamic end point locations in support of service-based traffic forwarding
US10454758B2 (en) * 2016-08-31 2019-10-22 Nicira, Inc. Edge node cluster network redundancy and fast convergence using an underlay anycast VTEP IP
US10193750B2 (en) 2016-09-07 2019-01-29 Cisco Technology, Inc. Managing virtual port channel switch peers from software-defined network controller
US10341236B2 (en) 2016-09-30 2019-07-02 Nicira, Inc. Anycast edge service gateways
US10212071B2 (en) 2016-12-21 2019-02-19 Nicira, Inc. Bypassing a load balancer in a return path of network traffic
US10742746B2 (en) 2016-12-21 2020-08-11 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
CN107171953B (en) * 2017-05-22 2020-04-28 浙江工商大学 Virtual router implementation method
US10659352B2 (en) 2017-05-31 2020-05-19 Juniper Networks, Inc. Signaling private context forwarding tables for a private forwarding layer
US10432523B2 (en) 2017-05-31 2019-10-01 Juniper Networks, Inc. Routing protocol signaling of multiple next hops and their relationship
US10389635B2 (en) * 2017-05-31 2019-08-20 Juniper Networks, Inc. Advertising selected fabric paths for service routes in virtual nodes
US10382333B2 (en) * 2017-05-31 2019-08-13 Juniper Networks, Inc. Fabric path context-based forwarding for virtual nodes
US10476817B2 (en) 2017-05-31 2019-11-12 Juniper Networks, Inc. Transport LSP setup using selected fabric path between virtual nodes
US10547509B2 (en) 2017-06-19 2020-01-28 Cisco Technology, Inc. Validation of a virtual port channel (VPC) endpoint in the network fabric
US10848421B2 (en) * 2017-06-27 2020-11-24 Level 3 Communications, Llc Internet service through a virtual routing and forwarding table of a multiprotocol label switching network
US10637800B2 (en) 2017-06-30 2020-04-28 Nicira, Inc Replacement of logical network addresses with physical network addresses
US10681000B2 (en) 2017-06-30 2020-06-09 Nicira, Inc. Assignment of unique physical network addresses for logical network addresses
US10810033B2 (en) * 2017-08-11 2020-10-20 International Business Machines Corporation Propagating external route changes into a cloud network
US10511546B2 (en) * 2017-09-29 2019-12-17 Juniper Networks, Inc. Connecting virtual nodes in a network device using abstract fabric interfaces
US10608887B2 (en) 2017-10-06 2020-03-31 Nicira, Inc. Using packet tracing tool to automatically execute packet capture operations
US10419327B2 (en) 2017-10-12 2019-09-17 Big Switch Networks, Inc. Systems and methods for controlling switches to record network packets using a traffic monitoring network
US20190116119A1 (en) * 2017-10-17 2019-04-18 Huawei Technologies Co., Ltd. Inter-vrf routing using normal network operation model
US10511459B2 (en) 2017-11-14 2019-12-17 Nicira, Inc. Selection of managed forwarding element for bridge spanning multiple datacenters
US10374827B2 (en) 2017-11-14 2019-08-06 Nicira, Inc. Identifier that maps to different networks at different datacenters
CN108667726B (en) * 2018-04-26 2021-03-02 中体彩科技发展有限公司 Transaction system and secondary routing control method
CN109005080B (en) * 2018-06-25 2020-09-01 烽火通信科技股份有限公司 Distributed packet forwarding implementation method, implementation system and automatic test method
US11463324B2 (en) 2018-07-09 2022-10-04 At&T Intellectual Property I, L.P. Systems and methods for supporting connectivity to multiple VRFs from a data link
US10791004B2 (en) 2018-10-29 2020-09-29 Cisco Technology, Inc. Methods and apparatus for use in network overlay fabrics to facilitate external network connectivity including access to extranet shared services
US10931560B2 (en) 2018-11-23 2021-02-23 Vmware, Inc. Using route type to determine routing protocol behavior
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
CN111917649B (en) * 2019-05-10 2022-06-28 华为云计算技术有限公司 Virtual private cloud communication and configuration method and related device
US11095735B2 (en) 2019-08-06 2021-08-17 Tealium Inc. Configuration of event data communication in computer networks
US11159343B2 (en) 2019-08-30 2021-10-26 Vmware, Inc. Configuring traffic optimization using distributed edge services
US11146656B2 (en) 2019-12-20 2021-10-12 Tealium Inc. Feature activation control and data prefetching with network-connected mobile devices
CN113542111A (en) * 2020-04-20 2021-10-22 华为技术有限公司 Message forwarding method and network equipment
US11606294B2 (en) 2020-07-16 2023-03-14 Vmware, Inc. Host computer configured to facilitate distributed SNAT service
US11616755B2 (en) 2020-07-16 2023-03-28 Vmware, Inc. Facilitating 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
US11902050B2 (en) 2020-07-28 2024-02-13 VMware LLC Method for providing distributed gateway service at host computer
US11451413B2 (en) 2020-07-28 2022-09-20 Vmware, Inc. Method for advertising availability of distributed gateway service and machines at host computer
US11558426B2 (en) 2020-07-29 2023-01-17 Vmware, Inc. Connection tracking for container cluster
US11570090B2 (en) 2020-07-29 2023-01-31 Vmware, Inc. Flow tracing operation in container cluster
US11196628B1 (en) 2020-07-29 2021-12-07 Vmware, Inc. Monitoring container clusters
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
US11715056B2 (en) 2021-03-16 2023-08-01 Bank Of America Corporation Performance monitoring for communication systems
US11595527B2 (en) 2021-03-16 2023-02-28 Bank Of America Corporation Dynamic routing for communication systems
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
US11677645B2 (en) 2021-09-17 2023-06-13 Vmware, Inc. Traffic monitoring
CN114422214B (en) * 2021-12-31 2023-12-29 深信服科技股份有限公司 Access information processing method, device, equipment and computer storage medium
CN115277550B (en) * 2022-06-21 2023-11-28 阿里巴巴(中国)有限公司 Routing system, routing method and routing device of virtual network

Citations (35)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5550816A (en) * 1994-12-29 1996-08-27 Storage Technology Corporation Method and apparatus for virtual switching
US5920699A (en) 1996-11-07 1999-07-06 Hewlett-Packard Company Broadcast isolation and level 3 network switch
US6148411A (en) 1996-04-05 2000-11-14 Hitachi, Ltd. Network system having function of changing route upon failure
US6151635A (en) 1993-06-29 2000-11-21 Hewlett-Packard Company Router connections through switching networks using virtual circuits
US6192051B1 (en) 1999-02-26 2001-02-20 Redstone Communications, Inc. Network router search engine using compressed tree forwarding table
US6205488B1 (en) 1998-11-13 2001-03-20 Nortel Networks Limited Internet protocol virtual private network realization using multi-protocol label switching tunnels
US20010048661A1 (en) * 2000-05-24 2001-12-06 David Clear Method and apparatus for multi-protocol redundant router protocol support
US6397260B1 (en) 1999-03-08 2002-05-28 3Com Corporation Automatic load sharing for network routers
US20020067725A1 (en) * 2000-12-06 2002-06-06 Naoki Oguchi Virtual network construction method, system, and relaying apparatus
US20020097730A1 (en) * 2001-01-25 2002-07-25 Cresent Networks, Inc. Network device virtual Interface
US20020099849A1 (en) * 2001-01-25 2002-07-25 Crescent Networks, Inc. Dense virtual router packet switching
US20020133534A1 (en) * 2001-01-08 2002-09-19 Jan Forslow Extranet workgroup formation across multiple mobile virtual private networks
US20020184387A1 (en) * 2001-05-31 2002-12-05 The Furukawa Electric Co., Ltd. Method for connecting between networks, virtual router, and system for connecting between networks by using this virtual router
US6496510B1 (en) * 1997-11-14 2002-12-17 Hitachi, Ltd. Scalable cluster-type router device and configuring method thereof
US20030051048A1 (en) 2001-06-29 2003-03-13 Watson Thomas Lee System and method for router virtual networking
US6556547B1 (en) 1998-12-15 2003-04-29 Nortel Networks Limited Method and apparatus providing for router redundancy of non internet protocols using the virtual router redundancy protocol
US6560236B1 (en) * 1993-06-23 2003-05-06 Enterasys Networks, Inc. Virtual LANs
US20030126233A1 (en) * 2001-07-06 2003-07-03 Mark Bryers Content service aggregation system
US20030123446A1 (en) * 2001-12-21 2003-07-03 Muirhead Charles S. System for supply chain management of virtual private network services
US6597699B1 (en) 1999-09-28 2003-07-22 Telefonaktiebolaget Lm Ericsson (Publ) Quality of service management in a packet data router system having multiple virtual router instances
US6609153B1 (en) 1998-12-24 2003-08-19 Redback Networks Inc. Domain isolation through virtual network machines
US20030169747A1 (en) 2002-03-01 2003-09-11 Yang Wang Resource allocation in virtual routers
US6674756B1 (en) 1999-02-23 2004-01-06 Alcatel Multi-service network switch with multiple virtual routers
WO2004010654A1 (en) 2002-07-20 2004-01-29 Redback Networks Inc. Method and apparatus for routing and forwarding between virtual routers within a single network element
US20040073715A1 (en) * 2002-07-16 2004-04-15 Folkes Ronald P. Method to enable routing protocol communication and transit packet forwarding between virtual routers
US20040076160A1 (en) * 1998-12-23 2004-04-22 Kaustubh Phaltankar High resiliency network infrastructure
US20040165581A1 (en) * 2002-11-20 2004-08-26 Minoru Oogushi Virtual access router
US20050281249A1 (en) * 2004-06-18 2005-12-22 Nokia Corporation Multi-instancing of routing/forwarding tables and socket API
US7085827B2 (en) 2001-09-20 2006-08-01 Hitachi, Ltd. Integrated service management system for remote customer support
US7133365B2 (en) * 2001-11-02 2006-11-07 Internap Network Services Corporation System and method to provide routing control of information over networks
US20070183421A1 (en) * 2001-10-18 2007-08-09 Terrell William C Router and methods using network addresses for virtualization
US7260648B2 (en) * 2001-01-25 2007-08-21 Ericsson, Inc. Extension of address resolution protocol (ARP) for internet protocol (IP) virtual networks
US7272643B1 (en) 2000-09-13 2007-09-18 Fortinet, Inc. System and method for managing and provisioning virtual routers
US7274704B1 (en) 2000-07-14 2007-09-25 Nortel Networks Limited Piggybacking VPN information in BGP for network based VPN architectures
US7769862B2 (en) * 2003-12-19 2010-08-03 Check Point Software Technologies Inc. Method and system for efficiently failing over interfaces in a network

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6751191B1 (en) * 1999-06-29 2004-06-15 Cisco Technology, Inc. Load sharing and redundancy scheme
US7272634B2 (en) 2004-03-18 2007-09-18 Sony Corporation System and method for integrating multiple messaging systems

Patent Citations (43)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6560236B1 (en) * 1993-06-23 2003-05-06 Enterasys Networks, Inc. Virtual LANs
US6151635A (en) 1993-06-29 2000-11-21 Hewlett-Packard Company Router connections through switching networks using virtual circuits
US5550816A (en) * 1994-12-29 1996-08-27 Storage Technology Corporation Method and apparatus for virtual switching
US6148411A (en) 1996-04-05 2000-11-14 Hitachi, Ltd. Network system having function of changing route upon failure
US5920699A (en) 1996-11-07 1999-07-06 Hewlett-Packard Company Broadcast isolation and level 3 network switch
US6496510B1 (en) * 1997-11-14 2002-12-17 Hitachi, Ltd. Scalable cluster-type router device and configuring method thereof
US6205488B1 (en) 1998-11-13 2001-03-20 Nortel Networks Limited Internet protocol virtual private network realization using multi-protocol label switching tunnels
US6556547B1 (en) 1998-12-15 2003-04-29 Nortel Networks Limited Method and apparatus providing for router redundancy of non internet protocols using the virtual router redundancy protocol
US20040076160A1 (en) * 1998-12-23 2004-04-22 Kaustubh Phaltankar High resiliency network infrastructure
US6609153B1 (en) 1998-12-24 2003-08-19 Redback Networks Inc. Domain isolation through virtual network machines
US6674756B1 (en) 1999-02-23 2004-01-06 Alcatel Multi-service network switch with multiple virtual routers
US6192051B1 (en) 1999-02-26 2001-02-20 Redstone Communications, Inc. Network router search engine using compressed tree forwarding table
US6397260B1 (en) 1999-03-08 2002-05-28 3Com Corporation Automatic load sharing for network routers
US6597699B1 (en) 1999-09-28 2003-07-22 Telefonaktiebolaget Lm Ericsson (Publ) Quality of service management in a packet data router system having multiple virtual router instances
US20010048661A1 (en) * 2000-05-24 2001-12-06 David Clear Method and apparatus for multi-protocol redundant router protocol support
US7274704B1 (en) 2000-07-14 2007-09-25 Nortel Networks Limited Piggybacking VPN information in BGP for network based VPN architectures
US7272643B1 (en) 2000-09-13 2007-09-18 Fortinet, Inc. System and method for managing and provisioning virtual routers
US20020067725A1 (en) * 2000-12-06 2002-06-06 Naoki Oguchi Virtual network construction method, system, and relaying apparatus
US20020133534A1 (en) * 2001-01-08 2002-09-19 Jan Forslow Extranet workgroup formation across multiple mobile virtual private networks
US20020099849A1 (en) * 2001-01-25 2002-07-25 Crescent Networks, Inc. Dense virtual router packet switching
US7242665B2 (en) * 2001-01-25 2007-07-10 Ericsson Ab Network device virtual interface
US20020097730A1 (en) * 2001-01-25 2002-07-25 Cresent Networks, Inc. Network device virtual Interface
US7260648B2 (en) * 2001-01-25 2007-08-21 Ericsson, Inc. Extension of address resolution protocol (ARP) for internet protocol (IP) virtual networks
US20020184387A1 (en) * 2001-05-31 2002-12-05 The Furukawa Electric Co., Ltd. Method for connecting between networks, virtual router, and system for connecting between networks by using this virtual router
US20030051048A1 (en) 2001-06-29 2003-03-13 Watson Thomas Lee System and method for router virtual networking
US20030126233A1 (en) * 2001-07-06 2003-07-03 Mark Bryers Content service aggregation system
US7464152B2 (en) 2001-09-20 2008-12-09 Hitachi, Ltd. Integrated service management system for remote customer support
US7085827B2 (en) 2001-09-20 2006-08-01 Hitachi, Ltd. Integrated service management system for remote customer support
US20070183421A1 (en) * 2001-10-18 2007-08-09 Terrell William C Router and methods using network addresses for virtualization
US7133365B2 (en) * 2001-11-02 2006-11-07 Internap Network Services Corporation System and method to provide routing control of information over networks
US20030123446A1 (en) * 2001-12-21 2003-07-03 Muirhead Charles S. System for supply chain management of virtual private network services
US20030169747A1 (en) 2002-03-01 2003-09-11 Yang Wang Resource allocation in virtual routers
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
US20040073715A1 (en) * 2002-07-16 2004-04-15 Folkes Ronald P. Method to enable routing protocol communication and transit packet forwarding between virtual routers
US20040240429A1 (en) 2002-07-20 2004-12-02 Naiming Shen Method and apparatus for routing and forwarding between virtual routers within a single network element
US6907039B2 (en) 2002-07-20 2005-06-14 Redback Networks Inc. Method and apparatus for routing and forwarding between virtual routers within a single network element
WO2004010654A1 (en) 2002-07-20 2004-01-29 Redback Networks Inc. Method and apparatus for routing and forwarding between virtual routers within a single network element
US20040240455A1 (en) 2002-07-20 2004-12-02 Naiming Shen Method and apparatus for routing and forwarding between virtual routers within a single network element
US20040233913A1 (en) 2002-07-20 2004-11-25 Naiming Shen Method and apparatus for routing and forwarding between virtual routers within a single network element
US7715381B2 (en) * 2002-07-20 2010-05-11 Ericsson Ab Method and apparatus for routing and forwarding between virtual routers within a single network element
US20040165581A1 (en) * 2002-11-20 2004-08-26 Minoru Oogushi Virtual access router
US7769862B2 (en) * 2003-12-19 2010-08-03 Check Point Software Technologies Inc. Method and system for efficiently failing over interfaces in a network
US20050281249A1 (en) * 2004-06-18 2005-12-22 Nokia Corporation Multi-instancing of routing/forwarding tables and socket API

Non-Patent Citations (24)

* Cited by examiner, † Cited by third party
Title
Aweya, "On the design of IP routers. Part 1: Router Architectures", Apr. 2000, Journal of Systems Architecture, vol. 46, Issue 6, pp. 483-511.
Bjorkman, N. et al., "Open control of partitioned switches", Jun. 26-29, 2000, IEEE, ISBN: 0-7803-5884-8, pp. 549-556.
Final Office Action, U.S. Appl. No. 10/883,109, dated Sep. 11, 2009, 12 pages.
Final Office Action, U.S. Appl. No. 10/883,109, dated Sep. 3, 2008, 12 pages.
Final Office Action, U.S. Appl. No. 10/883,425, dated Jul. 20, 2010, 13 pages.
Final Office Action, U.S. Appl. No. 10/883,425, dated Nov. 2, 2009, 18 pages.
Final Office Action, U.S. Appl. No. 10/883,425, dated Oct. 29, 2008, 12 pages.
Gopal L., Ram, "Seperation of Control and Forwarding Plane Inside a Network Element," Nokia Research Center, 0-7803-7600-5/02/$17.00 © 2002 IEEE, pp. 161-166.
Gopal, Ram, "Forwarding Element Model draft-gopal-forces-femodel-00.txt.," Internet Draft, Nokia, Feb. 2002, Expires Aug. 2002, http://www3.tools.ietf.org/html/draft-gopal-forces-femodel-00, (Aug. 28, 2007), pp. 1-13.
McDysan, D. et al., "Multiservice networking using a component-based switch and router architecture", Jun. 26-29, 2000, IEEE, pp. 97-104.
Non-Final Office Action for U.S. Appl. No. 10/883,425, dated Jan. 21, 2011, 17 pages.
Non-Final Office Action, U.S. Appl. No. 10/265,789, dated Oct. 27, 2003, 10 pages.
Non-Final Office Action, U.S. Appl. No. 10/883,109, dated Aug. 21, 2007, 9 pages.
Non-Final Office Action, U.S. Appl. No. 10/883,109, dated Feb. 22, 2008, 16 pages.
Non-Final Office Action, U.S. Appl. No. 10/883,109, dated Jan. 28, 2009, 10 pages.
Non-Final Office Action, U.S. Appl. No. 10/883,425, dated Apr. 28, 2009, 13 pages.
Non-Final Office Action, U.S. Appl. No. 10/883,425, dated Mar. 2, 2010, 17 pages.
Non-Final Office Action, U.S. Appl. No. 10/883,425, dated May 13, 2008, 15 pages.
Non-Final Office Action, U.S. Appl. No. 10/883,425, dated Sep. 17, 2007, 10 pages.
Notice of Allowance, U.S. Appl. No. 10/265,789, dated Apr. 19, 2004, 5 pages.
Notice of Allowance, U.S. Appl. No. 10/265,789, dated Apr. 5, 2005, 5 pages.
Notice of Allowance, U.S. Appl. No. 10/883,109, dated Dec. 29, 2009, 5 pages.
White, "Catalyst 8500 CSR Architecture", 1988, Cisco Systems, pp. 1-19.
Yu, Jessica, "Network Based IP VPN Architecture Using Virtual Routers", Feb. 19, 2001, CoSineCommunications, all slides.

Cited By (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090327903A1 (en) * 2006-07-06 2009-12-31 Referentia Systems, Inc. System and Method for Network Topology and Flow Visualization
US20130159865A1 (en) * 2006-07-06 2013-06-20 John Kei Smith Method and System for Real-Time Visualization of Network Flow within Network Device
US20130159864A1 (en) * 2006-07-06 2013-06-20 John Kei Smith System for Network Flow Visualization through Network Devices within Network Topology
US20130159863A1 (en) * 2006-07-06 2013-06-20 John Kei Smith System and Method for Network Topology and Flow Visualization
US9003292B2 (en) * 2006-07-06 2015-04-07 LiveAction, 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
US9246772B2 (en) * 2006-07-06 2016-01-26 LiveAction, Inc. System and method for network topology and flow visualization
US9350622B2 (en) * 2006-07-06 2016-05-24 LiveAction, Inc. Method and system for real-time visualization of network flow within network device
US9154327B1 (en) 2011-05-27 2015-10-06 Cisco Technology, Inc. User-configured on-demand virtual layer-2 network for infrastructure-as-a-service (IaaS) on a hybrid cloud network
US10148500B2 (en) 2011-05-27 2018-12-04 Cisco Technologies, Inc. User-configured on-demand virtual layer-2 network for Infrastructure-as-a-Service (IaaS) on a hybrid cloud network
US8660129B1 (en) 2012-02-02 2014-02-25 Cisco Technology, Inc. Fully distributed routing over a user-configured on-demand virtual network for infrastructure-as-a-service (IaaS) on hybrid cloud networks
US9197543B2 (en) 2012-02-02 2015-11-24 Cisco Technology, Inc. Fully distributed routing over a user-configured on-demand virtual network for infrastructure-as-a-service (IaaS) on hybrid cloud networks

Also Published As

Publication number Publication date
US20110194567A1 (en) 2011-08-11
US20160112307A1 (en) 2016-04-21
GB0521044D0 (en) 2005-11-23
US20120039333A1 (en) 2012-02-16
WO2004010654A1 (en) 2004-01-29
HK1091621A1 (en) 2007-01-19
GB0501759D0 (en) 2005-03-02
US10116556B2 (en) 2018-10-30
US8472451B2 (en) 2013-06-25
GB2407452B (en) 2005-12-28
US6907039B2 (en) 2005-06-14
GB2417161B (en) 2006-06-28
US20040013120A1 (en) 2004-01-22
AU2003253747A1 (en) 2004-02-09
US20040240429A1 (en) 2004-12-02
GB0607355D0 (en) 2006-05-24
GB2407452A (en) 2005-04-27
US9246791B2 (en) 2016-01-26
US20040233913A1 (en) 2004-11-25
US20190007312A1 (en) 2019-01-03
GB2417161A (en) 2006-02-15
GB0607357D0 (en) 2006-05-24
US20040240455A1 (en) 2004-12-02
GB2422513A (en) 2006-07-26
US7715381B2 (en) 2010-05-11
GB2422513B (en) 2006-10-04
GB2427786A (en) 2007-01-03
US8045547B2 (en) 2011-10-25
GB2427786B (en) 2007-02-21

Similar Documents

Publication Publication Date Title
US10116556B2 (en) Techniques for routing and forwarding between multiple virtual routers implemented by a single device
US11290340B2 (en) Segment routing over label distribution protocol
US9319312B2 (en) Segment routing mapping server for LDP/SR interoperability
EP2974164B1 (en) Indexed segment id
US7484003B2 (en) Method and apparatus for multiple contexts and layer 3 virtual private networks
US9948576B2 (en) Mechanism for enabling layer two host addresses to be shielded from the switches in a network
KR100431207B1 (en) Exteranet ip-vpn service provinding methode in mpls based network

Legal Events

Date Code Title Description
AS Assignment

Owner name: ERICSSON AB,SWEDEN

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:REDBACK NETWORKS INC.;REEL/FRAME:024002/0363

Effective date: 20070125

Owner name: ERICSSON AB, SWEDEN

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:REDBACK NETWORKS INC.;REEL/FRAME:024002/0363

Effective date: 20070125

STCF Information on status: patent grant

Free format text: PATENTED CASE

CC Certificate of correction
FPAY Fee payment

Year of fee payment: 4

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 8

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 12TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1553); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 12