WO2002059765A1 - Dense virtual router packet switching - Google Patents

Dense virtual router packet switching Download PDF

Info

Publication number
WO2002059765A1
WO2002059765A1 PCT/US2002/000936 US0200936W WO02059765A1 WO 2002059765 A1 WO2002059765 A1 WO 2002059765A1 US 0200936 W US0200936 W US 0200936W WO 02059765 A1 WO02059765 A1 WO 02059765A1
Authority
WO
WIPO (PCT)
Prior art keywords
routing
virtual
vprns
vprn
protocol
Prior art date
Application number
PCT/US2002/000936
Other languages
French (fr)
Inventor
Stephen M. Alfieri
Chase T. Tingley
Original Assignee
Crescent Networks, Inc.
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 Crescent Networks, Inc. filed Critical Crescent Networks, Inc.
Priority to EP02703116A priority Critical patent/EP1417586B1/en
Priority to AT02703116T priority patent/ATE549682T1/en
Publication of WO2002059765A1 publication Critical patent/WO2002059765A1/en

Links

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
    • 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/52Multiprotocol routers
    • 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 present invention is related to the field of routed networks, and more particularly to routed networks employing virtual private routed network (VPRN) techniques.
  • VPRN virtual private routed network
  • VPRN virtual private routed network
  • the VPRN employs Internet Protocol (IP) technology of the same type used in the Internet, complete with a private instance of a distributed IP routing protocol such as Open Shortest Path First (OSPF) and a private set of network addresses such as IPv4 addresses.
  • IP Internet Protocol
  • OSPF Open Shortest Path First
  • a mesh of "tunnels", or dedicated virtual channels, are established among a set of router nodes in the Internet.
  • the router nodes encapsulate VPRN traffic in a format required by the tunnels, transmit encapsulated traffic to other router nodes using the Internet address space and routing protocols, decapsulate received traffic to recover the original VPRN traffic, and then use the VPRN routing protocols and address space to forward the traffic to other nodes in the VPRN outside the Internet.
  • a dense virtual router packet switching system is disclosed that achieves improved performance even in very large networks with a large number of routes.
  • the disclosed system includes a memory divided into a number of context areas for a set of virtual private routed networks (VPRNs) , where each VPRN employs a respective routing protocol and network address space. Multiple instances of the same routing protocol may be in use by different VPRNs, and different VPRNs may also use overlapping network addresses.
  • Each context area of the memory includes a routing table and routing protocol state information for a corresponding VPRN.
  • the system further includes a set of routing tasks, including at least one routing task for each different type of routing protocol employed in the set of VPRNs. Each routing task operates with a separate routing table and separate routing protocol state information to realize a "virtual router" to carry out routing operations .
  • Context selection logic selectively couples the routing tasks to the different context areas of the memory, thereby realizing a set of virtual routers for all the VPRNs supported by the dense virtual routing system.
  • the use of VPRNs can improve performance over a non-segmented network by reducing the processing load for each VPRN by an amount that more than compensates for replicating the processing for each VPRN. For example, if one million routes are supported in a non-segmented network, the processing load is on the order of the square of 1 million, or 10 12 , processing operations per unit time.
  • the processing load is on the order of 1000 x (1000) 2 , or 10 9 , processing operations per unit time.
  • FIG. 1 is a block diagram of a network including routers employing dense virtual router packet switching in accordance with the present invention
  • Figure 2 is a high-level functional block diagram of a router in the network of Figure 1;
  • Figure 3 is a more detailed functional block diagram of the router of Figure 2;
  • Figure 4 is a high-level block diagram depicting the hardware/software architecture of the router of Figures 2 and 3; and '
  • FIG. 5 is a block diagram of a virtual router subsystem in the router of Figures 2-4.
  • FIG 1 shows a network in which a wide-area routed network 10 is utilized to carry traffic for a number of virtual private routed networks (VPRNs) .
  • Each VPRN includes corresponding VPRN subnetworks 12.
  • VPRNs numbered 1 through 3 are shown, with each including corresponding subnetworks 12-1, 12-2 and 12-3.
  • the wide-area routed network 10 includes a number of routers 14.
  • Each router 14 has connections to access links 16 that connect the router 14 to local VPRN subnetworks 12, and has connections to backbone links 18 that connect the router 14 to other routers 14 in the wide-area routed network 10.
  • An example of the wide-area routed network 10 is a global network such as the Internet.
  • the wide-area routed network 10 has a given network address space and a defined set of communications protocols, including routing protocols.
  • the wide-area routed network 10 may employ the Internet Protocol (IP) with IP version 4 (IPv4) addressing, and employ routing protocols such as Border Gateway Protocol (BGP) , Open Shortest Path First (OSPF) , Routing Information Protocol (RIP) , etc.
  • IP Internet Protocol
  • IPv4 IP version 4
  • routing protocols such as Border Gateway Protocol (BGP) , Open Shortest Path First (OSPF) , Routing Information Protocol (RIP) , etc.
  • Border Gateway Protocol BGP
  • OSPF Open Shortest Path First
  • RIP Routing Information Protocol
  • Each VPRN which is made up of a corresponding set of VPRN subnetworks 12, is a routed network having its own network address space and network communications protocols, including a routing protocol.
  • Nodes within a VPRN are generally not assigned addresses in the address space of the wide-area routed network 10, nor do the routers 14 carry traffic on their specific behalf. Rather, as described in more detail below, the routers 14 utilize the address space and routing protocols of the wide-area routed network 10 on behalf of the VPRN subnetworks 12 as entities.
  • the VPRN subnetworks 12 utilize their respective private address spaces and routing protocols for internal routing of data traffic among specific computers or other types of network sources and destinations. Fundamentally, the wide-area routed network 10 and routers 14 serve to provide dedicated virtual connections among the VPRN subnetworks 12 to form the various larger-scale VPRNs.
  • FIG 2 shows an exemplary organization of a router 14.
  • VARs virtual access routers
  • VBR virtual backbone router
  • the VBR 22 uses IP addresses from the address space of the wide area routed network 10, which is separate from the address spaces of the VPRNs.
  • the VBR 22 provides a tunneling service to VARs 20 that is used in constructing the VPRNs.
  • a signaling protocol such as the Resource Reservation Protocol (RSVP) is used to set up the tunnels.
  • RSVP Resource Reservation Protocol
  • the VBR 22 may also provide direct access to the wide area routed network 10 for customers desiring such service, such as Customer D in Figure 2.
  • the VBR 22 participates in the full routing for the wide-area routed network 10.
  • the VBR 22 generally maintains a full BGP routing table.
  • Each VAR 20 has its own routing table and runs its own instances of the routing protocols used in the corresponding VPRN.
  • the network addresses (e.g., IP addresses) of a VAR 20 are taken from the address space of the VPRN to which the VAR belongs. Different VARs 20 can use overlapping sets of addresses, i.e., the same address may appear in different sets, even though the different instances of the address belong to different nodes in different VPRNs.
  • RSVP signaling is used to create tunnels within the wide-area routed network 10 to connect VARs 20 residing in different routers 14.
  • This signaling is accomplished through the use of virtual tunnel adapters (VTAs) 24.
  • VTAs virtual tunnel adapters
  • These devices resemble IP hosts residing in the wide-area routed network 10, and have host IP addresses in the address space of the wide-area routed network 10.
  • Each VTA 24 has a signaling interface via which the VTA 24 is instructed to establish a tunnel connection between a local VAR 20 and a remote VAR 20 residing on another router 14 (not shown in Figure 2) .
  • FIG. 3 shows a more detailed view of a router 14.
  • the VARs 20 are associated with Virtual Interfaces (Vis) 30, which in turn are associated with MPLS label switched paths (LSPs) on the backbone links 18 of the wide area routed network 10.
  • LSPs are established to form the tunnels through the wide area routed network 10 that link the various VPRN subnetworks 12.
  • An "inner” LSP 32 carries traffic specifically associated with a given VI 30.
  • An "outer” LSP 34 carries a group of inner LSPs 32.
  • a different outer LSP 34 is defined between each pair of routers 14 in the wide-area routed network 10.
  • the router 14 also includes various additional functional entities such as a VPN Agent 36, Quality of Service (QoS) Manager 38, LSP Manager 40, MPLS Signaling function 42, and Line Control Processor (LCP) Interface 44.
  • the VPN Agent 36 coordinates the configuration of the VPRNs.
  • the VPN Agent 36 instantiates VARs 20 and Vis 30, interacts with the LSP Manager 40 to coordinate the use of labels, and passes QoS information to the LSP manager 40 for dynamically configured labels.
  • the QoS Manager 38 handles the QoS aspect of the setting up of LSPs, which includes interpreting the QoS parameters of RSVP.
  • the LSP Manager 40 coordinates all aspects of LSPs, including the creation and deletion of LSPs and the maintenance of label information.
  • the MPLS signaling function 42 interfaces with the VPN agent 36 and the MPLS signaling function 42 in the creation, monitoring, and deletion of LSPs.
  • the MPLS signaling function 42 implements RSVP signaling for MPLS.
  • the MPLS signaling function 42 signals downstream to obtain a label.
  • the MPLS signaling function 42 passes labels upstream.
  • the MPLS signaling function 42 interfaces with upstream and downstream routers to distribute labels.
  • the MPLS signaling function 42 also interfaces with routing code to obtain next hop information, and passes label information to the LSP Manager 40.
  • the LCP interface 44 passes forwarding information from the software-implemented functions of Figure 3, such as the VARs 20 and Vis 30, to hardware forwarding engines residing on line cards (not shown) within the router 14.
  • the forwarding information falls into four categories: next hop routing information, MPLS label information, packet classification information, and QoS information.
  • FIG 4 shows a high-level software and hardware organization for the routers 14.
  • a number of physical interfaces (Pis) 50 connect to the access links 16 and backbone links 18 of Figures 1-3. Examples of such interfaces include Ethernet interfaces, SONET interfaces, etc.
  • a layer-2 protocol such as ATM may also be used.
  • Each PI 50 is also connected to a virtual interface (VI) subsystem 52, which includes all of the Vis in the router 14, such as the Vis 30 of Figure 3.
  • the VI subsystem 52 has a number of connections to a virtual router (VR) subsystem 54, which includes all the virtual routers such as the VARs 20 and VBR 22 of Figure 3.
  • VIP virtual router
  • the Pis 50, VI subsystem 52, and VR subsystem 54 are coupled to a collection of other functional elements labeled in Figure 4 as a management subsystem 56.
  • the management subsystem 56 includes the VPN agent 36, QoS Manager 38, LSP Manager 40, MPLS Signaling function 42 and LCP interface 44 of Figure 3.
  • the virtual routers (VRs) within the VR subsystem 54 generally consist of processes and associated data that behave as a number of separate, distinct routers. Each VR is associated with a different VPRN.
  • a given router 14 may include a few or many such VRs in accordance with the number of VPRNs having traffic flowing through the router 14. Subject to hardware constraints of a given platform, such as processing power and memory capacity, a router 14 may be configured with as many as hundreds or potentially thousands of such VRs.
  • the VI subsystem 52 provides a special function within the router 14.
  • a conventional router generally includes a routing subsystem tied directly to physical interfaces, without an intermediate subsystem such as the VI subsystem 52 shown in Figure 4. Accordingly, changes to the underlying physical network result in the need to change routing tables and other data structures in the routing subsystem. Examples of such changes to the physical network include manual reconfigurations and automatic protection switching.
  • the routing subsystem has a very large routing data structure, as is the case for the VR subsystem 54, it is difficult and inefficient to maintain physical-layer information within it.
  • the arrangement of Figure 4 addresses these problems by "virtualizing" the interfaces from the perspective of the virtual routers in the VR subsystem 54.
  • Each virtual router employs static, generic interface identifiers, and the VI subsystem 52 handles the translation between these interface identifiers and details of underlying physical interfaces, which in general are subject to dynamic change.
  • FIG. 5 shows the VR subsystem 5 .
  • a collection of routing processes or tasks such as OSPF tasks 60-O, BGP tasks 60-B, and RIP tasks 60-R are coupled to a memory 62 via context selection logic 64.
  • the memory 62 is divided into a number of context areas, shown as CTXT 1, CTXT 2, ... CTXT M, for M distinct VRs .
  • Each context area contains a routing table and other operating state information for a different VR.
  • the tasks 60 are independent processes that are time-shared among the various VRs . The time-sharing is accomplished in part via the context selection logic 64.
  • the context selection logic 64 couples the appropriate task 60 to the context area CTXT for that VR.
  • the task 60 executes using the data from that context area CTXT. This processing continues to completion before a subsequent event is permitted to activate another VR, at which time the same or a different task 60 becomes coupled to a context area CTXT for the other VR.
  • VR #134 is part of a VPRN in which the OSPF routing protocol is used.
  • Context area CTXT 134 of the memory 62 contains the routing table and other operating state for this VR.
  • an OSPF task 60-0 is activated, and the context selection logic 64 connects the OSPF task 60-O to context area CTXT 134.
  • the OSPF task 60-O performs operations in accordance with the received packet, which may include updating the routing table and initiating the transmission of one or more routing protocol packets to other routers in the VPRN.
  • the context selection logic 64 is free to break the connection between the OSPF task 60 and context area CTXT 134 in favor of a new connection, which will generally involve a different context area CTXT of the memory 62 and may involve a different task 60 as well.
  • the context selection logic 64 employs an inner-LSP label appearing in encapsulated protocol packets to identify which context area 62 to select for processing the packet.
  • a mapping table (not shown) within the context selection logic 64 maps the label to a base address of the associated context area 62.
  • the inner-LSP label appearing in the encapsulated protocol packets is likewise mapped to the generic interface identifiers used in the routing table that resides in the selected context area 62.
  • the number of tasks 60 can vary in accordance with the routing protocols being used by the active VPRNs and the processing resources available in the router 14. There must be at least one active task 60 for each different routing protocol used by any of the VPRNs supported by the router 14. Thus, if all of the active VPRNs are using either OSPF or BGP routing, for example, then the minimum set of tasks 60 is one OSPF task 60-O and one BGP task 60-B. In general, one task 60 can support a number of VPRNs of the same type (i.e., using the same routing protocol) , depending on the processing resources allocated to the task 60 and the demand from the VPRNs.
  • the memory 62 may be a single memory containing all the context areas CTXT for all VRs of the router 14, or it may be a system having multiple independent memories, each containing some subset of the context areas CTXT.
  • the context selection logic 64 is generally designed to exploit parallelism in ' order to maximize performance. If the hardware platform is capable of running multiple tasks 60 simultaneously and accessing multiple context areas CTXT of the memory 62 simultaneously, then preferably the context selection logic 64 looks for opportunities to activate two or more VRs simultaneously.
  • connections 66 shown in Figure 5 represent logical connections between each VR and the VI subsystem 52 of Figure 4. In general, there are multiple such logical connections between each VR and the VI subsystem 52, with each logical connection corresponding to a different interface identifier. Some VRs may have as few as two associated Vis, whereas other VRs may have many.

Abstract

A dense virtual router packet switching system includes a memory (62) divided into context areas for a set of virtual private routed networks (VPRNs). Each context area includes a routing table and routing protocol state information for a corresponding VPRN. Each of a set of different routing tasks (60) operates with a separate routing table and separate routing protocol state information to realize a corresponding virtual router. Context selection logic (64) selectively couples the routing tasks to the different context areas of the memory to realize a set of virtual routers for all the VPRNs. The system supports a large number of routes by exploiting the segmentation of the VPRNs. Rather than having a single large routing table and associated routing process, which can load hardware resources in proportion to the square of the number of routes in the routing table, routes are distributed among a number of VPRNs having generally smaller tables and correspondingly less processing demand.

Description

TITLE OF THE INVENTION Dense Virtual Router Packet Switching
CROSS REFERENCE TO RELATED APPLICATIONS This application claims priority under 35 U.S.C. §119 (e) of U.S. Provisional Patent Application No. 60/264,093 filed January 25, 2001.
STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT —Not Applicable—
BACKGROUND OF THE INVENTION The present invention is related to the field of routed networks, and more particularly to routed networks employing virtual private routed network (VPRN) techniques.
One of the challenges facing designers of data communications networks is to provide improved performance in the face of tremendous growth in network size and complexity. As the number of nodes using distinct network addresses in a network grows, the sizes of routing tables used for routing in the network increase, and more processing power is required to calculate routes and carry out the routing of network traffic. In fact, the processing load associated with routing increases generally as the square of the number of distinct routes. In large networks having a generally flat shared address space, such as the Internet, it may be infeasible for routers to support sufficiently large routing tables, due to constraints in the available processing power.
It has been known to emulate a private, wide-area routed network within another, generally more public, wide-area network. Such an emulated network is referred to as a virtual private routed network (VPRN) . Because a VPRN "piggybacks" on a separate and generally shared network, it can be more cost effective than a distinct private wide area network. At the same time, there is significant functional separation between the VPRN and the underlying network, so that VPRN largely behaves like a standalone network, with attendant benefits in security, network management, and other aspects of network operation.
In a common VPRN configuration, the VPRN employs Internet Protocol (IP) technology of the same type used in the Internet, complete with a private instance of a distributed IP routing protocol such as Open Shortest Path First (OSPF) and a private set of network addresses such as IPv4 addresses. A mesh of "tunnels", or dedicated virtual channels, are established among a set of router nodes in the Internet. The router nodes encapsulate VPRN traffic in a format required by the tunnels, transmit encapsulated traffic to other router nodes using the Internet address space and routing protocols, decapsulate received traffic to recover the original VPRN traffic, and then use the VPRN routing protocols and address space to forward the traffic to other nodes in the VPRN outside the Internet.
BRIEF SUMMARY OF THE INVENTION In accordance with the present invention, a dense virtual router packet switching system is disclosed that achieves improved performance even in very large networks with a large number of routes.
The disclosed system includes a memory divided into a number of context areas for a set of virtual private routed networks (VPRNs) , where each VPRN employs a respective routing protocol and network address space. Multiple instances of the same routing protocol may be in use by different VPRNs, and different VPRNs may also use overlapping network addresses. Each context area of the memory includes a routing table and routing protocol state information for a corresponding VPRN. The system further includes a set of routing tasks, including at least one routing task for each different type of routing protocol employed in the set of VPRNs. Each routing task operates with a separate routing table and separate routing protocol state information to realize a "virtual router" to carry out routing operations . Context selection logic selectively couples the routing tasks to the different context areas of the memory, thereby realizing a set of virtual routers for all the VPRNs supported by the dense virtual routing system. For a given total number of routes, the use of VPRNs can improve performance over a non-segmented network by reducing the processing load for each VPRN by an amount that more than compensates for replicating the processing for each VPRN. For example, if one million routes are supported in a non-segmented network, the processing load is on the order of the square of 1 million, or 1012, processing operations per unit time. If the same one million routes are segmented into 1000 VPRNs of 1000 routes apiece, then the processing load is on the order of 1000 x (1000) 2, or 109, processing operations per unit time. Other aspects, features, and advantages of the present invention are disclosed in the detailed description that follows .
BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING The invention will be more fully understood by reference to the following Detailed Description in conjunction with the Drawing, of which:
Figure 1 is a block diagram of a network including routers employing dense virtual router packet switching in accordance with the present invention;
Figure 2 is a high-level functional block diagram of a router in the network of Figure 1;
Figure 3 is a more detailed functional block diagram of the router of Figure 2; Figure 4 is a high-level block diagram depicting the hardware/software architecture of the router of Figures 2 and 3; and '
Figure 5 is a block diagram of a virtual router subsystem in the router of Figures 2-4.
DETAILED DESCRIPTION OF THE INVENTION The disclosure of U.S. Provisional Patent Application No. 60/264,093 filed January 25, 2001, is hereby incorporated by reference herein.
Figure 1 shows a network in which a wide-area routed network 10 is utilized to carry traffic for a number of virtual private routed networks (VPRNs) . Each VPRN includes corresponding VPRN subnetworks 12. In Figure 1, VPRNs numbered 1 through 3 are shown, with each including corresponding subnetworks 12-1, 12-2 and 12-3. The wide-area routed network 10 includes a number of routers 14. Each router 14 has connections to access links 16 that connect the router 14 to local VPRN subnetworks 12, and has connections to backbone links 18 that connect the router 14 to other routers 14 in the wide-area routed network 10.
An example of the wide-area routed network 10 is a global network such as the Internet. In general, the wide-area routed network 10 has a given network address space and a defined set of communications protocols, including routing protocols. For example, the wide-area routed network 10 may employ the Internet Protocol (IP) with IP version 4 (IPv4) addressing, and employ routing protocols such as Border Gateway Protocol (BGP) , Open Shortest Path First (OSPF) , Routing Information Protocol (RIP) , etc.
Each VPRN, which is made up of a corresponding set of VPRN subnetworks 12, is a routed network having its own network address space and network communications protocols, including a routing protocol. Nodes within a VPRN are generally not assigned addresses in the address space of the wide-area routed network 10, nor do the routers 14 carry traffic on their specific behalf. Rather, as described in more detail below, the routers 14 utilize the address space and routing protocols of the wide-area routed network 10 on behalf of the VPRN subnetworks 12 as entities. The VPRN subnetworks 12, in turn, utilize their respective private address spaces and routing protocols for internal routing of data traffic among specific computers or other types of network sources and destinations. Fundamentally, the wide-area routed network 10 and routers 14 serve to provide dedicated virtual connections among the VPRN subnetworks 12 to form the various larger-scale VPRNs.
Figure 2 shows an exemplary organization of a router 14. Several "virtual access routers" (VARs) 20 are associated with respective customers and connected to the respective customers' access links 16. These are described in more detail below. A provider "virtual backbone router" (VBR) 22 is connected to the backbone links 18 of the wide area routed network 10 of Figure 1. The VBR 22 uses IP addresses from the address space of the wide area routed network 10, which is separate from the address spaces of the VPRNs. The VBR 22 provides a tunneling service to VARs 20 that is used in constructing the VPRNs. A signaling protocol such as the Resource Reservation Protocol (RSVP) is used to set up the tunnels. The VBR 22 may also provide direct access to the wide area routed network 10 for customers desiring such service, such as Customer D in Figure 2. The VBR 22 participates in the full routing for the wide-area routed network 10. In the case of the Internet, the VBR 22 generally maintains a full BGP routing table. Each VAR 20 has its own routing table and runs its own instances of the routing protocols used in the corresponding VPRN. The network addresses (e.g., IP addresses) of a VAR 20 are taken from the address space of the VPRN to which the VAR belongs. Different VARs 20 can use overlapping sets of addresses, i.e., the same address may appear in different sets, even though the different instances of the address belong to different nodes in different VPRNs. There is generally no direct connection, in the sense of an IP routing adjacency, between different VARs 20 within a router 14 or between a VAR 20 and the VBR 22.
As mentioned, RSVP signaling is used to create tunnels within the wide-area routed network 10 to connect VARs 20 residing in different routers 14. This signaling is accomplished through the use of virtual tunnel adapters (VTAs) 24. These devices resemble IP hosts residing in the wide-area routed network 10, and have host IP addresses in the address space of the wide-area routed network 10. Each VTA 24 has a signaling interface via which the VTA 24 is instructed to establish a tunnel connection between a local VAR 20 and a remote VAR 20 residing on another router 14 (not shown in Figure 2) .
Figure 3 shows a more detailed view of a router 14. The VARs 20 are associated with Virtual Interfaces (Vis) 30, which in turn are associated with MPLS label switched paths (LSPs) on the backbone links 18 of the wide area routed network 10. LSPs are established to form the tunnels through the wide area routed network 10 that link the various VPRN subnetworks 12. As shown, a two-level hierarchy of LSPs is used. An "inner" LSP 32 carries traffic specifically associated with a given VI 30. An "outer" LSP 34 carries a group of inner LSPs 32. A different outer LSP 34 is defined between each pair of routers 14 in the wide-area routed network 10.
The router 14 also includes various additional functional entities such as a VPN Agent 36, Quality of Service (QoS) Manager 38, LSP Manager 40, MPLS Signaling function 42, and Line Control Processor (LCP) Interface 44. The VPN Agent 36 coordinates the configuration of the VPRNs. The VPN Agent 36 instantiates VARs 20 and Vis 30, interacts with the LSP Manager 40 to coordinate the use of labels, and passes QoS information to the LSP manager 40 for dynamically configured labels. The QoS Manager 38 handles the QoS aspect of the setting up of LSPs, which includes interpreting the QoS parameters of RSVP. The LSP Manager 40 coordinates all aspects of LSPs, including the creation and deletion of LSPs and the maintenance of label information. It interfaces with the VPN agent 36 and the MPLS signaling function 42 in the creation, monitoring, and deletion of LSPs. The MPLS signaling function 42 implements RSVP signaling for MPLS. At an ingress node for an LSP, the MPLS signaling function 42 signals downstream to obtain a label. At an egress node, the MPLS signaling function 42 passes labels upstream. At a transit node, the MPLS signaling function 42 interfaces with upstream and downstream routers to distribute labels.
The MPLS signaling function 42 also interfaces with routing code to obtain next hop information, and passes label information to the LSP Manager 40.
The LCP interface 44 passes forwarding information from the software-implemented functions of Figure 3, such as the VARs 20 and Vis 30, to hardware forwarding engines residing on line cards (not shown) within the router 14. The forwarding information falls into four categories: next hop routing information, MPLS label information, packet classification information, and QoS information.
Figure 4 shows a high-level software and hardware organization for the routers 14. A number of physical interfaces (Pis) 50 connect to the access links 16 and backbone links 18 of Figures 1-3. Examples of such interfaces include Ethernet interfaces, SONET interfaces, etc. A layer-2 protocol such as ATM may also be used. Each PI 50 is also connected to a virtual interface (VI) subsystem 52, which includes all of the Vis in the router 14, such as the Vis 30 of Figure 3. The VI subsystem 52 has a number of connections to a virtual router (VR) subsystem 54, which includes all the virtual routers such as the VARs 20 and VBR 22 of Figure 3. The Pis 50, VI subsystem 52, and VR subsystem 54 are coupled to a collection of other functional elements labeled in Figure 4 as a management subsystem 56. The management subsystem 56 includes the VPN agent 36, QoS Manager 38, LSP Manager 40, MPLS Signaling function 42 and LCP interface 44 of Figure 3.
The virtual routers (VRs) within the VR subsystem 54 generally consist of processes and associated data that behave as a number of separate, distinct routers. Each VR is associated with a different VPRN. A given router 14 may include a few or many such VRs in accordance with the number of VPRNs having traffic flowing through the router 14. Subject to hardware constraints of a given platform, such as processing power and memory capacity, a router 14 may be configured with as many as hundreds or potentially thousands of such VRs.
The VI subsystem 52 provides a special function within the router 14. A conventional router generally includes a routing subsystem tied directly to physical interfaces, without an intermediate subsystem such as the VI subsystem 52 shown in Figure 4. Accordingly, changes to the underlying physical network result in the need to change routing tables and other data structures in the routing subsystem. Examples of such changes to the physical network include manual reconfigurations and automatic protection switching. When the routing subsystem has a very large routing data structure, as is the case for the VR subsystem 54, it is difficult and inefficient to maintain physical-layer information within it. The arrangement of Figure 4 addresses these problems by "virtualizing" the interfaces from the perspective of the virtual routers in the VR subsystem 54. Each virtual router employs static, generic interface identifiers, and the VI subsystem 52 handles the translation between these interface identifiers and details of underlying physical interfaces, which in general are subject to dynamic change.
Figure 5 shows the VR subsystem 5 . A collection of routing processes or tasks such as OSPF tasks 60-O, BGP tasks 60-B, and RIP tasks 60-R are coupled to a memory 62 via context selection logic 64. The memory 62 is divided into a number of context areas, shown as CTXT 1, CTXT 2, ... CTXT M, for M distinct VRs . Each context area contains a routing table and other operating state information for a different VR. The tasks 60 are independent processes that are time-shared among the various VRs . The time-sharing is accomplished in part via the context selection logic 64. As events occur that require action for a given VR (most such events being associated with the sending and receiving of routing protocol messages or packets) , the context selection logic 64 couples the appropriate task 60 to the context area CTXT for that VR. The task 60 then executes using the data from that context area CTXT. This processing continues to completion before a subsequent event is permitted to activate another VR, at which time the same or a different task 60 becomes coupled to a context area CTXT for the other VR.
As an example, let it be assumed that a VR identified as
VR #134 is part of a VPRN in which the OSPF routing protocol is used. Context area CTXT 134 of the memory 62 contains the routing table and other operating state for this VR. Upon receipt of a routing protocol packet on a VI associated with VR #134, an OSPF task 60-0 is activated, and the context selection logic 64 connects the OSPF task 60-O to context area CTXT 134. The OSPF task 60-O performs operations in accordance with the received packet, which may include updating the routing table and initiating the transmission of one or more routing protocol packets to other routers in the VPRN. Once the processing associated with the received routing protocol packet is complete, the context selection logic 64 is free to break the connection between the OSPF task 60 and context area CTXT 134 in favor of a new connection, which will generally involve a different context area CTXT of the memory 62 and may involve a different task 60 as well.
In the illustrated embodiment, the context selection logic 64 employs an inner-LSP label appearing in encapsulated protocol packets to identify which context area 62 to select for processing the packet. A mapping table (not shown) within the context selection logic 64 maps the label to a base address of the associated context area 62. The inner-LSP label appearing in the encapsulated protocol packets is likewise mapped to the generic interface identifiers used in the routing table that resides in the selected context area 62.
The number of tasks 60 can vary in accordance with the routing protocols being used by the active VPRNs and the processing resources available in the router 14. There must be at least one active task 60 for each different routing protocol used by any of the VPRNs supported by the router 14. Thus, if all of the active VPRNs are using either OSPF or BGP routing, for example, then the minimum set of tasks 60 is one OSPF task 60-O and one BGP task 60-B. In general, one task 60 can support a number of VPRNs of the same type (i.e., using the same routing protocol) , depending on the processing resources allocated to the task 60 and the demand from the VPRNs. If there are a large number of active VPRNs using a given protocol, it may be desirable that there be multiple tasks 60 of the same type. These tasks may time-share the same physical processor (s) , or may be distributed in a parallel fashion among different processors if such hardware processing resources are available in the router 14. Similarly, the memory 62 may be a single memory containing all the context areas CTXT for all VRs of the router 14, or it may be a system having multiple independent memories, each containing some subset of the context areas CTXT. The context selection logic 64 is generally designed to exploit parallelism in 'order to maximize performance. If the hardware platform is capable of running multiple tasks 60 simultaneously and accessing multiple context areas CTXT of the memory 62 simultaneously, then preferably the context selection logic 64 looks for opportunities to activate two or more VRs simultaneously.
The connections 66 shown in Figure 5 represent logical connections between each VR and the VI subsystem 52 of Figure 4. In general, there are multiple such logical connections between each VR and the VI subsystem 52, with each logical connection corresponding to a different interface identifier. Some VRs may have as few as two associated Vis, whereas other VRs may have many.
It will be apparent to those skilled in the art that modifications to and variations of the above-described techniques are possible without departing from the inventive concepts disclosed herein. Accordingly, the invention should be viewed as limited solely by the scope and spirit of the appended claims .

Claims

CLAIMS What is claimed is:
1. A virtual routing system, comprising: a memory divided into a configurable number of context areas for a corresponding set of virtual private routed networks (VPRNs) , each context area including a routing table and associated routing protocol state information for the corresponding VPRN, each VPRN employing a respective routing protocol and network address space; a set of one or more routing tasks, the set including at least one routing task for each different type of routing protocol employed in the set of VPRNs, each routing task being operable only with a separate routing table and with separate routing protocol state information to realize a corresponding virtual router to carry out associated routing operations in a VPRN; and context selection logic operative to selectively couple the routing tasks to the different context areas of the memory to realize a set of virtual routers, each virtual router being associated with a corresponding one of the VPRNs.
2. A virtual routing system according to claim 1, wherein the set of routing tasks includes at least one Open Shortest Path First (OSPF) routing task and at least one Border Gateway Protocol (BGP) routing task.
3. A virtual routing system according to claim 1, further comprising a set of virtual interfaces operative to translate between generic interface identifiers used by the virtual routers and physical interface information for physical network links to which the virtual routing system is connected.
4. A virtual routing system according to claim 3, wherein the physical network links to which the virtual routing system is connected employ label switched paths, and wherein the set of virtual interfaces include virtual interfaces containing information for encapsulating and attaching labels to packets on the label switched paths.
5. A virtual routing system according to claim 1, wherein the selective coupling of the routing tasks to the different context areas of the memory is performed at the rate at which protocol packets for the various VPRNs are received by the virtual routing system.
6. A method of operating a routing system, comprising: maintaining a number of context areas in a memory for a corresponding set of virtual private routed networks (VPRNs) , each context area including a routing table and associated routing protocol state information for the corresponding VPRN, each VPRN employing a respective routing protocol and network address spacer- executing a set of one or more routing tasks, the set including at least one routing task for each different type of routing protocol employed in the set of VPRNs, each routing task being operable only with a separate routing table and with separate routing protocol state information to realize a corresponding virtual router to carry out associated routing operations in a VPRN; and selectively coupling the routing tasks to the different context areas of the memory to realize a set of virtual routers, each virtual router being associated with a corresponding one of the VPRNs.
7. A method according to claim 6, wherein the set of routing tasks includes at least one Open Shortest Path First (OSPF) routing task and at least one Border Gateway Protocol (BGP) routing task.
8. A method according to claim 6, further comprising maintaining a set of virtual interfaces operative to translate between generic interface identifiers used by the virtual routers and physical interface information for physical network links to which the virtual routing system is connected.
9. A method according to claim 8, wherein the physical network links to which the virtual routing system is connected employ label switched paths, and wherein the set of virtual interfaces include virtual interfaces containing information for encapsulating and attaching labels to packets on the label switched paths.
10. A method according to claim 6, wherein the selective coupling of the routing tasks to the different context areas of the memory is performed at the rate at which protocol packets for the various VPRNs are received by the virtual routing system.
PCT/US2002/000936 2001-01-25 2002-01-10 Dense virtual router packet switching WO2002059765A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP02703116A EP1417586B1 (en) 2001-01-25 2002-01-10 Dense virtual router packet switching
AT02703116T ATE549682T1 (en) 2001-01-25 2002-01-10 PACKET SHIPPING WITH DENSE VIRTUAL ROUTER

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US26409301P 2001-01-25 2001-01-25
US60/264,093 2001-01-25
US10/000,191 US7039720B2 (en) 2001-01-25 2001-10-19 Dense virtual router packet switching
US10/000,191 2001-10-19

Publications (1)

Publication Number Publication Date
WO2002059765A1 true WO2002059765A1 (en) 2002-08-01

Family

ID=26667321

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2002/000936 WO2002059765A1 (en) 2001-01-25 2002-01-10 Dense virtual router packet switching

Country Status (4)

Country Link
US (1) US7039720B2 (en)
EP (1) EP1417586B1 (en)
AT (1) ATE549682T1 (en)
WO (1) WO2002059765A1 (en)

Families Citing this family (69)

* 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
US7349979B1 (en) * 1999-12-02 2008-03-25 Cisco Technology, Inc. Method and apparatus for redirecting network traffic
US7058007B1 (en) 2000-01-18 2006-06-06 Cisco Technology, Inc. Method for a cable modem to rapidly switch to a backup CMTS
US6839829B1 (en) 2000-01-18 2005-01-04 Cisco Technology, Inc. Routing protocol based redundancy design for shared-access networks
US7574495B1 (en) 2000-09-13 2009-08-11 Fortinet, Inc. System and method for managing interworking communications protocols
US7272643B1 (en) * 2000-09-13 2007-09-18 Fortinet, Inc. System and method for managing and provisioning virtual routers
US7487232B1 (en) 2000-09-13 2009-02-03 Fortinet, Inc. Switch management system and method
US7111072B1 (en) 2000-09-13 2006-09-19 Cosine Communications, Inc. Packet routing system and method
US8250357B2 (en) 2000-09-13 2012-08-21 Fortinet, Inc. Tunnel interface for securing traffic over a network
US7286532B1 (en) * 2001-02-22 2007-10-23 Cisco Technology, Inc. High performance interface logic architecture of an intermediate network node
US7036123B2 (en) * 2001-04-25 2006-04-25 Sun Microsystems, Inc. System using fair-share scheduling technique to schedule processes within each processor set based on the number of shares assigned to each process group
US7881208B1 (en) 2001-06-18 2011-02-01 Cisco Technology, Inc. Gateway load balancing protocol
US7181547B1 (en) 2001-06-28 2007-02-20 Fortinet, Inc. Identifying nodes in a ring network
US7441017B2 (en) * 2001-06-29 2008-10-21 Thomas Lee Watson System and method for router virtual networking
JP2003069609A (en) * 2001-08-23 2003-03-07 Fujitsu Ltd System for providing virtual private network service
US7484003B2 (en) * 2001-11-17 2009-01-27 Redback Networks Inc. Method and apparatus for multiple contexts and layer 3 virtual private networks
US20030128668A1 (en) * 2002-01-04 2003-07-10 Yavatkar Rajendra S. Distributed implementation of control protocols in routers and switches
US7359387B2 (en) * 2002-03-01 2008-04-15 Verizon Business Global Llc Systems and methods for implementing virtual router
US7801155B2 (en) * 2002-03-01 2010-09-21 Verizon Business Global Llc Resource allocation in virtual routers
US7203192B2 (en) 2002-06-04 2007-04-10 Fortinet, Inc. Network packet steering
US7177311B1 (en) * 2002-06-04 2007-02-13 Fortinet, Inc. System and method for routing traffic through a virtual router-based network switch
US7334048B1 (en) * 2002-06-04 2008-02-19 Extreme Networks, Inc. Method and apparatus for fast route table update
US7376125B1 (en) 2002-06-04 2008-05-20 Fortinet, Inc. Service processing switch
US7161904B2 (en) 2002-06-04 2007-01-09 Fortinet, Inc. System and method for hierarchical metering in a virtual router based network switch
US7340535B1 (en) 2002-06-04 2008-03-04 Fortinet, Inc. System and method for controlling routing in a virtual router system
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
US7327675B1 (en) * 2002-08-01 2008-02-05 At&T Corp. Fairness of capacity allocation for an MPLS-based VPN
US7096383B2 (en) 2002-08-29 2006-08-22 Cosine Communications, Inc. System and method for virtual router failover in a network routing system
AU2003277300A1 (en) 2002-10-04 2004-05-04 Starent Networks Corporation Managing resources for ip networking
US7266120B2 (en) 2002-11-18 2007-09-04 Fortinet, Inc. System and method for hardware accelerated packet multicast in a virtual routing system
US7983239B1 (en) * 2003-01-07 2011-07-19 Raytheon Bbn Technologies Corp. Systems and methods for constructing a virtual model of a multi-hop, multi-access network
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
US7529257B1 (en) * 2003-04-30 2009-05-05 Cisco Technology, Inc. Method for supporting a GMPLS hierarchy through multiple routing instances
US9160714B2 (en) * 2003-06-30 2015-10-13 Telefonaktiebolaget L M Ericsson (Publ) Using tunneling to enhance remote LAN connectivity
US7881229B2 (en) * 2003-08-08 2011-02-01 Raytheon Bbn Technologies Corp. Systems and methods for forming an adjacency graph for exchanging network routing data
US7720095B2 (en) 2003-08-27 2010-05-18 Fortinet, Inc. Heterogeneous media packet bridging
US7606927B2 (en) * 2003-08-27 2009-10-20 Bbn Technologies Corp Systems and methods for forwarding data units in a communications network
US8166204B2 (en) * 2003-08-29 2012-04-24 Raytheon Bbn Technologies Corp. Systems and methods for automatically placing nodes in an ad hoc network
US7852856B2 (en) * 2003-08-29 2010-12-14 Broadcom Corp. System and method for providing pooling or dynamic allocation of connection context data
US7668083B1 (en) 2003-10-28 2010-02-23 Bbn Technologies Corp. Systems and methods for forwarding data in a communications network
US20060007926A1 (en) * 2003-12-19 2006-01-12 Zur Uri E System and method for providing pooling or dynamic allocation of connection context data
US7633961B2 (en) * 2004-04-07 2009-12-15 Alcatel Lucent Edge-router scaling for BGP peering with virtual private routed networks (VPRN)
US8204967B2 (en) * 2004-04-14 2012-06-19 Cisco Technology, Inc. Dynamic chain creation and segmentation of the packet-forwarding plane
JP4416593B2 (en) * 2004-07-21 2010-02-17 富士通株式会社 Network connection control method and network connection control system
US7499419B2 (en) 2004-09-24 2009-03-03 Fortinet, Inc. Scalable IP-services enabled multicast forwarding with efficient resource utilization
US7808904B2 (en) 2004-11-18 2010-10-05 Fortinet, Inc. Method and apparatus for managing subscriber profiles
US7782870B1 (en) * 2005-04-22 2010-08-24 Oracle America, Inc. Method and apparatus for consolidating available computing resources on different computing devices
US7532632B2 (en) * 2005-07-08 2009-05-12 At&T Intellectual Property Ii, L.P. Method for controlling memory consumption in router-based virtual private networks
CN100541413C (en) * 2005-10-21 2009-09-16 中国科学院计算技术研究所 A kind of network RAID system and method based on dynamic mode
US7978602B2 (en) * 2005-11-14 2011-07-12 Juniper Networks, Inc. Dynamic construction of label switching protocol interfaces
US8234361B2 (en) 2006-01-13 2012-07-31 Fortinet, Inc. Computerized system and method for handling network traffic
US7668920B2 (en) * 2006-03-01 2010-02-23 Fortinet, Inc. Electronic message and data tracking system
US8169903B2 (en) * 2006-03-07 2012-05-01 Cisco Technology, Inc. Managing traffic within and between virtual private networks when using a session border controller
US7522595B2 (en) 2006-06-16 2009-04-21 Cisco Technology, Inc. Communicating packets between forwarding contexts using virtual interfaces
US8488488B1 (en) 2007-02-22 2013-07-16 Cisco Technology, Inc. Mitigating threats in a network
US7889739B2 (en) * 2007-10-22 2011-02-15 Verizon Patent And Licensing Inc. Label and exp field based MPLS network device
US8238265B2 (en) * 2009-05-07 2012-08-07 Alcatel Lucent Auto-binding SDP RSVP LSP tunnel
US9274851B2 (en) * 2009-11-25 2016-03-01 Brocade Communications Systems, Inc. Core-trunking across cores on physically separated processors allocated to a virtual machine based on configuration information including context information for virtual machines
US8769155B2 (en) * 2010-03-19 2014-07-01 Brocade Communications Systems, Inc. Techniques for synchronizing application object instances
US8503289B2 (en) 2010-03-19 2013-08-06 Brocade Communications Systems, Inc. Synchronizing multicast information for linecards
US8495418B2 (en) 2010-07-23 2013-07-23 Brocade Communications Systems, Inc. Achieving ultra-high availability using a single CPU
US9104619B2 (en) 2010-07-23 2015-08-11 Brocade Communications Systems, Inc. Persisting data across warm boots
US9143335B2 (en) 2011-09-16 2015-09-22 Brocade Communications Systems, Inc. Multicast route cache system
US10581763B2 (en) 2012-09-21 2020-03-03 Avago Technologies International Sales Pte. Limited High availability application messaging layer
US9967106B2 (en) 2012-09-24 2018-05-08 Brocade Communications Systems LLC Role based multicast messaging infrastructure
US9203690B2 (en) 2012-09-24 2015-12-01 Brocade Communications Systems, Inc. Role based multicast messaging infrastructure
CN104009929B (en) * 2013-02-21 2019-01-18 中兴通讯股份有限公司 A kind of method and physical router managing virtual router
US9619349B2 (en) 2014-10-14 2017-04-11 Brocade Communications Systems, Inc. Biasing active-standby determination
CN113811857A (en) * 2020-04-17 2021-12-17 华为技术有限公司 Method and apparatus for resource management of network connections to process tasks across networks

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6205488B1 (en) * 1998-11-13 2001-03-20 Nortel Networks Limited Internet protocol virtual private network realization using multi-protocol label switching tunnels

Family Cites Families (14)

* 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
US6188671B1 (en) * 1997-07-03 2001-02-13 At&T Corp Traffic management for frame relay switched data service
CA2255294A1 (en) * 1997-12-23 1999-06-23 Scott Pegrum Multiple virtual router
US6493349B1 (en) * 1998-11-13 2002-12-10 Nortel Networks Limited Extended internet protocol virtual private network architectures
US6614781B1 (en) * 1998-11-20 2003-09-02 Level 3 Communications, Inc. Voice over data telecommunications network architecture
US6789118B1 (en) * 1999-02-23 2004-09-07 Alcatel Multi-service network switch with policy based routing
US6674756B1 (en) * 1999-02-23 2004-01-06 Alcatel Multi-service network switch with multiple virtual routers
US6850531B1 (en) * 1999-02-23 2005-02-01 Alcatel Multi-service network switch
US6693878B1 (en) * 1999-10-15 2004-02-17 Cisco Technology, Inc. Technique and apparatus for using node ID as virtual private network (VPN) identifiers
US6594704B1 (en) * 1999-12-15 2003-07-15 Quarry Technologies Method of managing and using multiple virtual private networks in a router with a single routing table
EP1111532A1 (en) * 1999-12-20 2001-06-27 TELEFONAKTIEBOLAGET LM ERICSSON (publ) Method for transporting physical objects, transportation system and transportation means
US6954463B1 (en) * 2000-12-11 2005-10-11 Cisco Technology, Inc. Distributed packet processing architecture for network access servers
US6778498B2 (en) * 2001-03-20 2004-08-17 Mci, Inc. Virtual private network (VPN)-aware customer premises equipment (CPE) edge router
US6744774B2 (en) * 2002-06-27 2004-06-01 Nokia, Inc. Dynamic routing over secure networks

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6205488B1 (en) * 1998-11-13 2001-03-20 Nortel Networks Limited Internet protocol virtual private network realization using multi-protocol label switching tunnels

Also Published As

Publication number Publication date
ATE549682T1 (en) 2012-03-15
US20020099849A1 (en) 2002-07-25
EP1417586A1 (en) 2004-05-12
US7039720B2 (en) 2006-05-02
EP1417586B1 (en) 2012-03-14
EP1417586A4 (en) 2006-09-20

Similar Documents

Publication Publication Date Title
US7039720B2 (en) Dense virtual router packet switching
US7242665B2 (en) Network device virtual interface
KR102113749B1 (en) System and method for routing traffic between distinct infiniband subnets based on source routing
US7411955B2 (en) 3-layer VPN and constructing method thereof
CN113169928B (en) Logical router including a disaggregated network element
CN102857494B (en) Universal network interface controller
CN100421380C (en) Data mirroring in a service
US7633937B2 (en) Methods and apparatus for switching between Metro Ethernet networks and external networks
RU2493677C2 (en) Method and router for implementing mirroring
US6385204B1 (en) Network architecture and call processing system
WO2022100554A1 (en) Method for forwarding bier message, and device and system
CN102413060B (en) User private line communication method and equipment used in VPLS (Virtual Private LAN (Local Area Network) Service) network
US6608817B1 (en) Method and apparatus for connection-oriented multiplexing and switching network analysis, management, and troubleshooting
JP2003524930A (en) Multi-service network switch
JP2002508123A (en) System and method for a multilayer network element
WO2002061599A1 (en) Extension of address resolution protocol (arp) for internet protocol (ip) virtual networks
CN107070789A (en) The flow black hole of active active PBB EVPN redundancies is avoided and rapid fusion
CN105391635A (en) Network virtualization method based on software defined network (SDN)
CN110034993A (en) Transmit method, equipment and the network system of data
CN106059946A (en) Message forwarding method and message forwarding device
CN111654441A (en) Pseudo wire load sharing method and device
CN110311860A (en) Multi-link load balance method and device under VXLAN
CN110191042B (en) Message forwarding method and device
CN112822097A (en) Message forwarding method, first network device and first device group
CN103269300A (en) Method and equipment for achieving heterogeneous network interconnection

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ OM PH PL PT RO RU SD SE SG SI SK SL TJ TM TN TR TT TZ UA UG UZ VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

WWE Wipo information: entry into national phase

Ref document number: 2002703116

Country of ref document: EP

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: COMMUNICATION PURSUANT TO RULE 69 EPC (EPO FORM 1205A DATED 01.12.2003)

WWP Wipo information: published in national office

Ref document number: 2002703116

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: JP

WWW Wipo information: withdrawn in national office

Country of ref document: JP