WO2015157096A1 - Proxy of routing protocols to redundant controllers - Google Patents

Proxy of routing protocols to redundant controllers Download PDF

Info

Publication number
WO2015157096A1
WO2015157096A1 PCT/US2015/024157 US2015024157W WO2015157096A1 WO 2015157096 A1 WO2015157096 A1 WO 2015157096A1 US 2015024157 W US2015024157 W US 2015024157W WO 2015157096 A1 WO2015157096 A1 WO 2015157096A1
Authority
WO
WIPO (PCT)
Prior art keywords
reachability information
forwarding
sessions
external routing
session
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.)
Ceased
Application number
PCT/US2015/024157
Other languages
English (en)
French (fr)
Inventor
William Thomas SELLA
James Michael SELLA
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.)
Level 3 Communications LLC
Original Assignee
Level 3 Communications LLC
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 Level 3 Communications LLC filed Critical Level 3 Communications LLC
Priority to JP2016560540A priority Critical patent/JP6562466B2/ja
Priority to CN201580018996.1A priority patent/CN106165322B/zh
Priority to EP15777320.1A priority patent/EP3130092B1/en
Priority to CA2945333A priority patent/CA2945333C/en
Publication of WO2015157096A1 publication Critical patent/WO2015157096A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/02—Topology update or discovery
    • H04L45/033—Topology update or discovery by updating distance vector protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/12—Discovery or management of network topologies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/12—Shortest path evaluation
    • H04L45/122—Shortest path evaluation by minimising distances, e.g. by selecting a route with minimum of number of hops
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/26—Route discovery packet
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/02—Topology update or discovery
    • H04L45/04—Interdomain routing, e.g. hierarchical routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/54—Organization of routing tables
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/58—Association of routers
    • H04L45/586—Association of routers of virtual routers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/64—Routing or path finding of packets in data switching networks using an overlay routing layer

Definitions

  • This application is generally related to network routing.
  • a communication network may, for example, provide a network connection that allows data to be transferred between two geographically remote locations.
  • a network connection may span multiple links connecting communication devices such as routers.
  • Networks may have different topologies depending on how the links are interconnected through communication devices. Given a particular network topology, multiple routes may be available between a source and destination. Some routes may be more desirable than others depending on current capacity and usage.
  • a router maintains such information in a routing table.
  • the routing table has entries designating a next hop for various destination addresses, or groups of destination addresses. Based on the destination address of an incoming packet, a router uses its routing table to forward the packet to a specific neighboring device.
  • each router uses a protocol like Border Gateway Protocol (BGP) to exchange routing and reachability information with local neighboring routers. In this way, each router both forwards packets and conducts control functions to update its own routing table.
  • Border Gateway Protocol BGP
  • SDNs Software Defined Networks
  • a method exchanges routing data within a network including control and forwarding on separate devices.
  • a first reachability information session is established between a forwarding device and a first control device
  • a second reachability information session is established between the forwarding device and a second control device.
  • the first and second reachability information sessions enable the respective first and second control devices to send advertisements indicating what addresses are reachable through the network.
  • a third reachability information session is established between the forwarding device and an external routing device.
  • the third reachability information session enables the forwarding device to exchange advertisements with the external routing device indicating what addresses are reachable through the respective forwarding and external routing devices.
  • advertisements are exchanged between the first and second reachability information sessions and the third reachability information session such that the first and second control device appear to the external routing device to be a single device.
  • FIG. 1A is a diagram of a network having multiple, redundant control devices that are separate from the forwarding devices.
  • FIG. IB is a diagram of a network having a local termination module that masks the multiple control devices to an external network.
  • FIGs. 2A-B are diagrams illustrating an example operation of the system in FIG.
  • FIG. 3 is a flowchart of a method for masking redundant controllers, according to an embodiment.
  • FIG. 4 is a diagram showing the system of figure 1 in greater detail.
  • having a control device separate from the forwarding devices make routing decision can enable more intelligent routing decisions on a service provider network. But having a single control device creates a single point of failure. If that control device fails, no updates could be made to any of the routing tables on the forwarding devices. To deal with this, embodiments have multiple, redundant control devices.
  • BGP Border Gateway Protocol
  • having multiple reachability information sessions to the customer network may require transmission of extra traffic and involve extra processing overhead on the customer routers. While aspects are described with respect to customer networks and customer routing devices for illustrative purposes, a skilled artisan would recognize that embodiments apply to any external network, that is, any network external to the service provider network.
  • embodiments provide an additional module on a forwarding device at the edge of the service provider network, where the service provider network interfaces with the customer network.
  • the module masks the existence of the multiple control devices, making it appear to the customer that only a single control device is being used.
  • the module establishes reachability information sessions, such as
  • the module exchanges routing data, such as route advertisements, obtained from the customer equipment's reachability information session and the control device's reachability information sessions.
  • routing data such as route advertisements
  • the module receives a route advertisement from the customer equipment, it forwards it onto each of the control devices.
  • the control devices broadcast route advertisements, the module forwards only the first-received one onto the customer routing equipment.
  • FIG. 1A is a diagram of a system 100 having multiple, redundant control devices that are separate from the forwarding devices.
  • System 100 includes a service provider network 120 and a customer network
  • Service provider network 120 may be a metropolitan area network (MAN) or wide area network (WAN) that connects at least two geographically disparate locations.
  • Customer network 130 may be a local area network that, for example, connects different computers within a single entity or building.
  • Service provider network 120 includes a plurality of forwarding devices: forwarding devices 106, 108, and 1 10. Each forwarding device may have a plurality of ports and forward packets of data from one port to another. To forward the data, each forwarding device may have a routing table and may forward information according to information in its routing table. Specifically, the routing table may map particular addresses or subnets to particular output ports.
  • the forwarding device When the forwarding device receives a packet of data, the forwarding device examines the packet's destination address to identify an entry in the routing table. In addition to examining the packet's destination address, the forwarding device examines any labels associated with packet, such as Multiprotocol Label Switching (MPLS) labels, to identify the entry in the routing table. That entry in the routing table specifies which port on the forwarding device to forward the packet.
  • MPLS Multiprotocol Label Switching
  • FIG. 1A depicts two control devices: control devices 102 and 104.
  • Control devices 102 and 104 each may transmit information to forwarding devices 106, 108, and 110 to configure their routing tables.
  • Control devices 102 and 104 may configure the routing tables to route data from a particular data flow along a particular path.
  • control devices 102 and 104 may be redundant. Each control device may have identical, or mirror image, information about the topology of service provider network 120 and may be able to determine identical paths through service provider network 120 independently of one another. By being redundant, if one of the control devices goes down, the other may continue to configure all of the forwarding devices on service provider network 120. While for illustration only two control devices are shown in figure 1 A, a skilled artisan would recognize that additional control devices may be used and adding additional control devices would add additional redundancy to system 100.
  • control devices 102 and 104 may each establish respective reachability information sessions 120 and 122 with at least one device on customer network 130.
  • the reachability information sessions may exchange routing and reachability information between service provider network 120 and the devices on customer network 130.
  • Border gateway protocol (BGP) is a common type of reachability information session protocol, but other types of reachability information session protocols may be used, for example Open Shortest Path First (OSPF) and Intermediate System to Intermediate System (ISIS).
  • OSPF Open Shortest Path First
  • ISIS Intermediate System to Intermediate System
  • Control devices 102 and 104 may use the information received from customer network 130 over reachability information sessions 120 and 122 respectively to develop their knowledge of the global network topology. For example, customer network 130 may inform control devices 102 and 104, over reachability information sessions 120 and 122, that it includes or can reach a particular set of destination addresses (such as an IP address subnet). Based on this information, control devices 102 and 104 may update their respective models of the global network topology. And control devices 102 and 104 may use the updated information to determine the routing tables for forwarding devices 106-1 10.
  • customer network 130 may inform control devices 102 and 104, over reachability information sessions 120 and 122, that it includes or can reach a particular set of destination addresses (such as an IP address subnet). Based on this information, control devices 102 and 104 may update their respective models of the global network topology. And control devices 102 and 104 may use the updated information to determine the routing tables for forwarding devices 106-1 10.
  • the routing devices on customer network 130 may also use the information received over reachability information sessions 120 and 122 to configure their routing tables.
  • Customer network 130 may include separate control and forwarding devices as similar to service provider network 120, or customer network 130 may include routers and switches that both forward data, and control and calculate their own routing tables. Either way, the routing devices on customer network 130 use the reachability information received from reachability information sessions 120 and 122 to configure their routing tables. They configure their routing tables such that data destined for an address reachable through service provider network 120 can be forwarded to service provider network 120.
  • Having multiple control devices in this way may add to redundancy. But having multiple reachability information sessions 120 and 122 may increase the burden on the customer of configuring devices on customer network 130. Specifically, a customer may have to configure its devices to operate with both reachability information session 120 and 122. For an administrator of customer network 130 that may be unfamiliar with service provider network 120, this configuration can be burdensome. To deal with this issue, embodiments aggregate data from the different control devices 102 and 104 to make for a single reachability information session with customer network 130 as illustrated in FIG. IB.
  • FIG. IB illustrates a system 150 that has a local termination module 170 that masks the multiple control devices to a customer network.
  • system 150 has a customer network 130, which includes a customer routing device 180, and a service provider network 120, which in turn has two control devices (102 and 104) and three forwarding devices (106, 108, and 110).
  • forwarding devices reside on an edge of service provider network 120, meaning that they directly connect to an outside network. According to embodiment, it is these edge forwarding devices that include a local termination module.
  • forwarding device 108 is an edge forwarding device, because it connects with customer network 130. Accordingly, forwarding device 108 includes local termination module 170.
  • Local termination module 170 establishes a reachability information session with the external network that its forwarding device is connected to and with each control device on service provider network 120.
  • local termination module 170 establishes a reachability information session 164 with customer network 130, and reachability information sessions 160 and 162 with control devices 102 and 104 respectively.
  • Local termination module 170 acts as a proxy for the reachability information sessions exchanging messages between them.
  • local termination module 170 exchanges messages between reachability information sessions 160, 162, and 164 to make the multiple control devices 102 and 104 appear to customer routing device 180 to be a single device.
  • local termination module 170 may receive an advertisement from customer routing device 180 via the reachability information session 164.
  • the advertisement may include reachability information, and the reachability information may indicate which addresses customer routing device 180 can forward information received from service provider network 120 to.
  • local termination module 170 receives the advertisement, it sends the enclosed reachability information to the control devices 102 and 104 via the reachability information sessions 160 and 162.
  • control devices 102 and 104 may update their knowledge of the network topology.
  • control devices 102 and 104 use the updated network topology to determine routing tables for forwarding devices 106, 108, and 110 with respect to those addresses in the reachability information. Specifically, control devices 102 and 104 may add entries to the routing tables to route data destined for addresses within customer network 130, and reachable from customer network 130, toward customer network 130. Then, control devices 102 and 104 transmit the updated routing tables to forwarding devices 106, 108, and 110, enabling forwarding devices 106, 108, and 110 to route data to customer network 130.
  • local termination module 170 Because local termination module 170 has reachability information sessions 160 and 162 with both control device 102 and 104, it will receive reachability information from both. And because control device 102 and 104 are redundant, and potentially mirror images of each other, the information received from control devices 102 and 104 will be duplicative. When duplicative information is received, local termination module 170 may only forward on the first-received information. To determine whether reachability information has been previously sent, local termination module 170 may store the reachability information, or an identification of it such as a hash. When local termination module 170 receives reachability information from a control device, it may check the storage to determine whether the reachability information has been previously forwarded to the customer routing device. Then, depending on the check, it may forward the information.
  • local termination module 170 may receive an advertisement from control device 102 via reachability information session 160.
  • the advertisement may include reachability information that in turn includes a number of entries. Each entry may map destination addresses reachable through service provider network 120 to a next hop address.
  • local termination module 170 may check its local storage to determine whether it has already sent. If it has already been sent, local termination module 170 does nothing. If it has not already been sent, local termination module 170 may forward on the data to customer routing device 180.
  • FIGs. 2A-B are diagrams showing a system 200 that illustrates how reachability information is propagated from one network to another.
  • system 200 includes a customer network 230 that includes a routing device 204.
  • Routing device 204 is connected to the service provider network at forwarding device 110.
  • forwarding device 1 being an edge forwarding device, includes a local termination module 220.
  • customer network 130 has an address space of
  • Advertisement message 210 includes reachability information indicating that the 20.0.0.0/24 subnet is addressable through customer routing device 180.
  • Forwarding device 108 receives advertisement message 210 and forwards its reachability information onto both control devices in two separate routing messages: routing messages 212 and 214 for control devices 102 and 104 respectively.
  • Control devices 102 and 104 update their model of the global network topology according to the reachability information in messages 212 and 214. As described above with respect to FIG. IB, it uses this information to update the routing tables of forwarding devices 106, 108, and 1 10 to route traffic addressed to 20.0.0.0/24 to customer routing device 180.
  • control devices 102 and 104 can also send routing advertisements to other external networks as illustrated in FIG. 2B.
  • FIG. 2B illustrates how control devices 102 and 104 advertise reachability information to customer network 230.
  • control devices 104 have each updated their models of the global network topology to reflect the fact that 20.0.0.0/24 is reachable through customer network 130, which is connected to the service provider network at forwarding device 108.
  • control devices 102 and 104 advertise to customer network 230 that 20.0.0.0/24 is reachable through the service provider network.
  • Control devices 102 and 104 having both updated their topology models, each send a respective advertisement 260 and 262 to forwarding device 1 10 and its local termination module 230.
  • Advertisements 260 and 262 include reachability information indicating that the destination addresses within the subnet 20.0.0.0/24 are reachable though the service provider network and specifically forwarding device 110.
  • the reachability information may have a next-hop IP address to reach 20.0.0.0/24 as the IP address of forwarding device 1 10.
  • advertisement 260 reaches forwarding device 1 10 first.
  • Local termination module 230 stores the reachability information, or a hash of the reachability information, in a local storage and sends the reachability information onto customer routing device 204 in an advertisement 264.
  • customer routing device 204 configures its routing table according to the reachability information. For example, customer routing device 204 may configure its routing table to route traffic addressed to the subnet 20.0.0.0/24 to forwarding device 110.
  • FIG. 3 is a flowchart of a method 300 for masking redundant controllers, according to an embodiment.
  • Method 300 begins at step 302 when a customer routing device establishes a reachability information session with the edge forwarding device.
  • Step 302 may occur when the customer routing device and the edge forwarding device discover that they are physically connected to each other.
  • the reachability information session created at step 302 enables the forwarding device to exchange advertisements with the customer routing device. Advertisements from the customer routing device may indicate what addresses are reachable through the customer routing device on the customer network. And advertisements from the forwarding device may indicate what addresses are reachable through the forwarding device on the service provider network.
  • the edge forwarding device establishes reachability information sessions with each control device on the service provider network at step 304. These reachability information sessions enable the respective first and second control devices to send advertisements indicating what addresses are reachable through the service provider network to the forwarding device.
  • the routing devices start exchanging reachability information.
  • the control devices learn that a new address prefix is available through the service provider network at decision block 312
  • each of the control devices advertise the prefix to the edge forwarding device at step 314.
  • the edge forwarding forwards one of the advertisements onto the customer routing device at step 316 and discards the other.
  • Steps 314 and 316 may execute to communicate all accessible prefixes when the session is first established. Then, as illustrated in FIG. 3, steps 314 and 316 may execute incremental updates as the control devices learn that new prefixes are accessible.
  • Steps 308 and 310 may execute to communicate all accessible prefixes when the session is first established. Then, as illustrated in FIG. 3, steps 308 and 310 may execute incremental updates as the customer routing device learns that new prefixes are accessible.
  • FIG. 4 is a diagram showing a system 400 that illustrates components of the local termination module 170 in greater detail.
  • Local termination module 170 includes three sub-modules: control session module 402, external session module 404, and exchange module 406.
  • Control session module 402 establishes the reachability information sessions between forwarding device 108 and control devices 102 and 104 as described above for example with respect to step 302.
  • External session module 404 establishes a reachability information session between the forwarding device and a customer routing device with respect to 304.
  • Exchange module 406 exchanges advertisements between the first and second reachability information sessions and the third reachability information session such that the first and second control device appear to the customer routing device to be a single device.
  • Exchange module 406 may send messages as illustrated in steps 306-316 in FIG. 3.
  • Each of the devices and modules disclosed herein may be implemented on the same or different computing devices.
  • Such computing devices can include, but are not limited to, a personal computer, a mobile device such as a mobile phone, workstation, embedded system, game console, television, set-top box, or any other computing device.
  • a computing device can include, but is not limited to, a device having a processor and memory, including a non-transitory memory, for executing and storing instructions.
  • the memory may tangibly embody the data and program instructions.
  • Software may include one or more applications and an operating system.
  • Hardware can include, but is not limited to, a processor, a memory, and a graphical user interface display.
  • the computing device may also have multiple processors and multiple shared or separate memory components.
  • the computing device may be a part of or the entirety of a clustered or distributed computing environment or server farm.
  • Identifiers such as "(a),” “(b),” “(i),” “(ii),” etc., are sometimes used for different elements or steps. These identifiers are used for clarity and do not necessarily designate an order for the elements or steps.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
PCT/US2015/024157 2014-04-10 2015-04-02 Proxy of routing protocols to redundant controllers Ceased WO2015157096A1 (en)

Priority Applications (4)

Application Number Priority Date Filing Date Title
JP2016560540A JP6562466B2 (ja) 2014-04-10 2015-04-02 冗長コントローラに対するルーティングプロトコルのプロキシ
CN201580018996.1A CN106165322B (zh) 2014-04-10 2015-04-02 向冗余控制器路由协议的代理
EP15777320.1A EP3130092B1 (en) 2014-04-10 2015-04-02 Proxy of routing protocols to redundant controllers
CA2945333A CA2945333C (en) 2014-04-10 2015-04-02 Proxy of routing protocols to redundant controllers

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US14/250,141 2014-04-10
US14/250,141 US9124507B1 (en) 2014-04-10 2014-04-10 Proxy of routing protocols to redundant controllers

Publications (1)

Publication Number Publication Date
WO2015157096A1 true WO2015157096A1 (en) 2015-10-15

Family

ID=53939000

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2015/024157 Ceased WO2015157096A1 (en) 2014-04-10 2015-04-02 Proxy of routing protocols to redundant controllers

Country Status (6)

Country Link
US (4) US9124507B1 (enExample)
EP (1) EP3130092B1 (enExample)
JP (1) JP6562466B2 (enExample)
CN (1) CN106165322B (enExample)
CA (1) CA2945333C (enExample)
WO (1) WO2015157096A1 (enExample)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111817907A (zh) * 2019-04-11 2020-10-23 华为技术有限公司 一种可达性的验证方法和装置

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9124507B1 (en) 2014-04-10 2015-09-01 Level 3 Communications, Llc Proxy of routing protocols to redundant controllers
US10033628B2 (en) * 2015-04-06 2018-07-24 Verizon Digital Media Services Inc. Application controlled path selection over different transit providers
US9736059B2 (en) 2015-04-06 2017-08-15 Verizon Digital Media Services Inc. Purging failover through application controlled transit selection
US9787579B2 (en) 2015-04-06 2017-10-10 Verizon Digital Media Services Inc. Application controlled path selection based on type-of-service
US9900222B2 (en) * 2015-10-26 2018-02-20 Microsoft Technology Licensing, Llc Validating routing tables of routing devices
CN106155637B (zh) * 2016-07-26 2019-03-29 中国航空工业集团公司西安飞行自动控制研究所 一种基于多余度的多目标机并行通信方法
CN114070857A (zh) * 2018-03-26 2022-02-18 华为技术有限公司 一种数据处理的方法以及相关设备
JP2021016067A (ja) * 2019-07-11 2021-02-12 富士ゼロックス株式会社 中継システム、中継装置及びプログラム
US10992540B1 (en) 2020-05-19 2021-04-27 Cisco Technology, Inc. Determining formal models using weighting factors for computing elements in multi-cloud environments
US11283688B2 (en) * 2020-05-19 2022-03-22 Cisco Technology, Inc. Delayed recomputation of formal network topology models based on modifications to deployed network topologies
US11424989B2 (en) 2020-06-15 2022-08-23 Cisco Technology, Inc. Machine-learning infused network topology generation and deployment
US11398948B2 (en) 2020-06-29 2022-07-26 Cisco Technology, Inc. Generation and deployment of inherited network topology models
CN112187519A (zh) * 2020-09-09 2021-01-05 中盈优创资讯科技有限公司 一种基于bgp协议实现策略控制的多活并发方法及装置

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060092857A1 (en) * 2004-11-01 2006-05-04 Lucent Technologies Inc. Softrouter dynamic binding protocol
US20060291378A1 (en) * 2005-06-28 2006-12-28 Alcatel Communication path redundancy protection systems and methods
US20070076591A1 (en) * 2005-09-16 2007-04-05 Khan Mohiuddin M Method and system of providing redundancy in a network device
US20070110017A1 (en) * 2005-08-02 2007-05-17 Waav Inc. Mobile router device
US20120014386A1 (en) * 2010-06-29 2012-01-19 Futurewei Technologies, Inc. Delegate Gateways and Proxy for Target Hosts in Large Layer 2 and Address Resolution with Duplicated Internet Protocol Addresses
US20120176934A1 (en) * 2007-07-31 2012-07-12 Cisco Technology, Inc. Overlay transport virtualization

Family Cites Families (78)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6421731B1 (en) * 1996-10-29 2002-07-16 Telxon Corporation Dynamic next hop routing protocol
US6374316B1 (en) * 1999-03-19 2002-04-16 Sony Corporation Method and system for circumscribing a topology to form ring structures
JP4183379B2 (ja) * 2000-11-27 2008-11-19 富士通株式会社 ネットワーク及びエッジルータ
US7333482B2 (en) * 2000-12-22 2008-02-19 Interactive People Unplugged Ab Route optimization technique for mobile IP
US7389265B2 (en) * 2001-01-30 2008-06-17 Goldman Sachs & Co. Systems and methods for automated political risk management
US7339903B2 (en) * 2001-06-14 2008-03-04 Qualcomm Incorporated Enabling foreign network multicasting for a roaming mobile node, in a foreign network, using a persistent address
US7120120B2 (en) * 2001-11-29 2006-10-10 Ipsum Networks, Inc. Method and system for topology construction and path identification in a two-level routing domain operated according to a simple link state routing protocol
CA2365681A1 (en) * 2001-12-19 2003-06-19 Alcatel Canada Inc. System and method for managing information for elements in a communication network
US7096251B2 (en) * 2002-01-23 2006-08-22 Sun Microsystems, Inc. Calculation of layered routes in a distributed manner
US20040107242A1 (en) * 2002-12-02 2004-06-03 Microsoft Corporation Peer-to-peer content broadcast transfer mechanism
JP3798754B2 (ja) * 2003-03-13 2006-07-19 インターナショナル・ビジネス・マシーンズ・コーポレーション ルータを介して接続されたサブネットワーク間のブロードキャスト
US7624195B1 (en) * 2003-05-08 2009-11-24 Cisco Technology, Inc. Method and apparatus for distributed network address translation processing
US7373660B1 (en) * 2003-08-26 2008-05-13 Cisco Technology, Inc. Methods and apparatus to distribute policy information
US20050068968A1 (en) * 2003-09-30 2005-03-31 Shlomo Ovadia Optical-switched (OS) network to OS network routing using extended border gateway protocol
US7428221B2 (en) * 2004-06-01 2008-09-23 Cisco Technology, Inc. Arrangement for providing network prefix information from attached mobile routers to a clusterhead in a tree-based ad hoc mobile network
US7512064B2 (en) * 2004-06-15 2009-03-31 Cisco Technology, Inc. Avoiding micro-loop upon failure of fast reroute protected links
US7509330B2 (en) * 2004-09-03 2009-03-24 Crossroads Systems, Inc. Application-layer monitoring of communication between one or more database clients and one or more database servers
JP4459018B2 (ja) * 2004-10-28 2010-04-28 富士通株式会社 ノード装置
US7551551B2 (en) * 2004-12-10 2009-06-23 Cisco Technology, Inc. Fast reroute (FRR) protection at the edge of a RFC 2547 network
US7468954B2 (en) * 2004-12-14 2008-12-23 Harris Corporation Mobile ad-hoc network providing expedited conglomerated broadcast message reply features and related methods
US7835276B2 (en) * 2004-12-30 2010-11-16 Cisco Technology, Inc. Admission control mechanism for multicast receivers
US7602778B2 (en) * 2005-06-29 2009-10-13 Cisco Technology, Inc. System and methods for compressing message headers
CN1893419A (zh) * 2005-07-06 2007-01-10 华为技术有限公司 一种路由更新方法
US7515544B2 (en) * 2005-07-14 2009-04-07 Tadaaki Chigusa Method and system for providing location-based addressing
US7889655B2 (en) * 2006-01-17 2011-02-15 Cisco Technology, Inc. Techniques for detecting loop-free paths that cross routing information boundaries
US7522603B2 (en) * 2006-03-14 2009-04-21 Cisco Technology, Inc. Technique for efficiently routing IP traffic on CE-CE paths across a provider network
JP2007258955A (ja) * 2006-03-22 2007-10-04 Fujitsu Ltd 先着学習方法、中継装置および中継装置用プログラム
US7673061B2 (en) * 2006-03-28 2010-03-02 Tellabs San Jose, Inc. Method and apparatus for neighborhood discovery across disparate point-to-point networks
US8649497B1 (en) * 2006-04-28 2014-02-11 At&T Intellectual Property Ii, L.P. Method and apparatus for providing reliable path for direct inward dial calls
US7957306B2 (en) * 2006-09-08 2011-06-07 Cisco Technology, Inc. Providing reachability information in a routing domain of an external destination address in a data communications network
US7693073B2 (en) * 2006-10-13 2010-04-06 At&T Intellectual Property I, L.P. System and method for routing packet traffic
US7995500B2 (en) * 2006-11-30 2011-08-09 Cisco Technology, Inc. Managing an amount of tunnels in a computer network
JP2008160385A (ja) * 2006-12-22 2008-07-10 Nec Corp ネットワーク経路制御システム、経路制御装置および経路制御方法
CN100579072C (zh) * 2006-12-22 2010-01-06 华为技术有限公司 一种在ip设备之间进行通信的方法和系统
US8233395B2 (en) * 2007-02-21 2012-07-31 At&T Intellectual Property I, Lp System for advertising routing updates
US7782797B2 (en) * 2007-02-27 2010-08-24 Hatteras Networks Methods and apparatus for self partitioning a data network to prevent address conflicts
US8102775B2 (en) * 2007-03-12 2012-01-24 Cisco Technology, Inc. Joining tree-based networks into an autonomous system using peer connections between the tree-based networks
JP4899959B2 (ja) * 2007-03-19 2012-03-21 富士通株式会社 Ｖｐｎ装置
US7561024B2 (en) * 2007-04-05 2009-07-14 Harris Corporation Ad-hoc network routing protocol including the use of forward and reverse multi-point relay (MPR) spanning tree routes
US8223660B2 (en) * 2007-04-18 2012-07-17 Rockstar Bidco Lp Failure notification in a network having serially connected nodes
US7782882B2 (en) * 2007-09-17 2010-08-24 The Boeing Company Method and apparatus for distributing dynamic auto-summarization of internet protocol reachable addresses
US7821970B2 (en) * 2007-09-26 2010-10-26 Cisco Technology, Inc. Protection of transit links in a network
US7751405B1 (en) * 2007-09-26 2010-07-06 Juniper Networks, Inc. Automatic configuration of label switched path tunnels using BGP attributes
US7860027B2 (en) * 2007-11-21 2010-12-28 Cisco Technology, Inc. Extending an IP everywhere network over a plurality of flooding domains
US9432213B2 (en) * 2007-12-31 2016-08-30 Rpx Clearinghouse Llc IP forwarding across a link state protocol controlled ethernet network
US8098663B2 (en) * 2008-07-08 2012-01-17 Cisco Technology, Inc. Carrier's carrier without customer-edge-to-customer-edge border gateway protocol
US8391276B2 (en) * 2008-10-03 2013-03-05 At&T Intellectual Property I, Lp Methods and apparatus to form secure cross-virtual private network communications sessions
US7978612B2 (en) * 2008-10-13 2011-07-12 Cisco Technology, Inc. Two-hop relay for reducing distance vector routing information
US8121118B2 (en) * 2008-10-31 2012-02-21 At&T Intellectual Property I, L.P. Methods and apparatus to dynamically control connectivity within virtual private networks
US7953097B2 (en) * 2009-01-09 2011-05-31 Alcatel Lucent Neighbour discovery protocol mediation
JP5001966B2 (ja) * 2009-02-24 2012-08-15 日本電信電話株式会社 経路情報管理方法およびその管理システム
US9294395B2 (en) * 2009-04-23 2016-03-22 Futurewei Technologies, Inc. Media access control bridging in a mesh network
US9210065B2 (en) * 2009-06-22 2015-12-08 Alcatel Lucent Providing cloud-based services using dynamic network virtualization
WO2011065268A1 (ja) * 2009-11-26 2011-06-03 日本電気株式会社 負荷分散システム、負荷分散方法、及びプログラム
US8345540B2 (en) * 2010-04-13 2013-01-01 Calix, Inc. Virtual snooping bridge in computer networks
US8743886B2 (en) * 2011-01-10 2014-06-03 Cisco Technology, Inc. Managing active edge devices in VPLS using BGP signaling
US8667172B2 (en) * 2011-06-07 2014-03-04 Futurewei Technologies, Inc. Method and apparatus for content identifier based radius constrained cache flooding to enable efficient content routing
WO2013086204A1 (en) * 2011-12-07 2013-06-13 Citrix Systems, Inc. Controlling a network interface using virtual switch proxying
US9172636B2 (en) * 2012-02-28 2015-10-27 Cisco Technology, Inc. Efficient link repair mechanism triggered by data traffic
US9729424B2 (en) * 2012-06-11 2017-08-08 Futurewei Technologies, Inc. Defining data flow paths in software-defined networks with application-layer traffic optimization
US9191139B1 (en) * 2012-06-12 2015-11-17 Google Inc. Systems and methods for reducing the computational resources for centralized control in a network
US8837479B1 (en) * 2012-06-27 2014-09-16 Juniper Networks, Inc. Fast reroute between redundant multicast streams
US9178797B2 (en) * 2012-06-30 2015-11-03 Juniper Networks, Inc. Selective BGP graceful restart in redundant router deployments
US8948181B2 (en) * 2012-10-23 2015-02-03 Cisco Technology, Inc. System and method for optimizing next-hop table space in a dual-homed network environment
US8989194B1 (en) * 2012-12-18 2015-03-24 Google Inc. Systems and methods for improving network redundancy and for facile initialization in a centrally-controlled network
US8693374B1 (en) * 2012-12-18 2014-04-08 Juniper Networks, Inc. Centralized control of an aggregation network with a reduced control plane
US9100285B1 (en) * 2012-12-18 2015-08-04 Juniper Networks, Inc. Dynamic control channel establishment for software-defined networks having centralized control
CN103916905A (zh) * 2013-01-06 2014-07-09 中兴通讯股份有限公司 组播源的注册、组播路径的建立方法及装置
US9094285B2 (en) * 2013-01-25 2015-07-28 Argela Yazilim ve Bilisim Teknolojileri San. ve Tic. A.S. Automatic discovery of multiple controllers in Software Defined Networks (SDNs)
US9294384B2 (en) * 2013-03-01 2016-03-22 Skytap Distributed service routing protocol suitable for virtual networks
US9450817B1 (en) * 2013-03-15 2016-09-20 Juniper Networks, Inc. Software defined network controller
US9306800B2 (en) * 2013-05-10 2016-04-05 Telefonaktiebolaget L M Ericsson (Publ) Inter-domain fast reroute methods and network devices
US9438439B2 (en) * 2013-10-30 2016-09-06 Aruba Networks, Inc. Dynamic optimization of advertisement packets
US9225641B2 (en) * 2013-10-30 2015-12-29 Globalfoundries Inc. Communication between hetrogenous networks
US9225597B2 (en) * 2014-03-14 2015-12-29 Nicira, Inc. Managed gateways peering with external router to attract ingress packets
US9124507B1 (en) 2014-04-10 2015-09-01 Level 3 Communications, Llc Proxy of routing protocols to redundant controllers
US10116464B2 (en) * 2015-03-18 2018-10-30 Juniper Networks, Inc. EVPN inter-subnet multicast forwarding
GB2549797B (en) * 2016-04-29 2018-09-19 Advanced Risc Mach Ltd Feedback mechanism for multicast protocols

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060092857A1 (en) * 2004-11-01 2006-05-04 Lucent Technologies Inc. Softrouter dynamic binding protocol
US20060291378A1 (en) * 2005-06-28 2006-12-28 Alcatel Communication path redundancy protection systems and methods
US20070110017A1 (en) * 2005-08-02 2007-05-17 Waav Inc. Mobile router device
US20070076591A1 (en) * 2005-09-16 2007-04-05 Khan Mohiuddin M Method and system of providing redundancy in a network device
US20120176934A1 (en) * 2007-07-31 2012-07-12 Cisco Technology, Inc. Overlay transport virtualization
US20120014386A1 (en) * 2010-06-29 2012-01-19 Futurewei Technologies, Inc. Delegate Gateways and Proxy for Target Hosts in Large Layer 2 and Address Resolution with Duplicated Internet Protocol Addresses

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3130092A4 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111817907A (zh) * 2019-04-11 2020-10-23 华为技术有限公司 一种可达性的验证方法和装置
EP3930262A4 (en) * 2019-04-11 2022-05-04 Huawei Technologies Co., Ltd. AVAILABILITY VERIFICATION METHOD AND DEVICE
US11743066B2 (en) 2019-04-11 2023-08-29 Huawei Technologies Co., Ltd. Reachability verification method and apparatus

Also Published As

Publication number Publication date
US20160294672A1 (en) 2016-10-06
US9379966B2 (en) 2016-06-28
US10367715B2 (en) 2019-07-30
CN106165322A (zh) 2016-11-23
CA2945333A1 (en) 2015-10-15
CN106165322B (zh) 2019-08-09
US9124507B1 (en) 2015-09-01
CA2945333C (en) 2021-10-19
US20190349285A1 (en) 2019-11-14
EP3130092A4 (en) 2017-11-29
JP6562466B2 (ja) 2019-08-21
EP3130092B1 (en) 2019-10-23
US10778564B2 (en) 2020-09-15
JP2017511069A (ja) 2017-04-13
EP3130092A1 (en) 2017-02-15
US20160020989A1 (en) 2016-01-21

Similar Documents

Publication Publication Date Title
US10778564B2 (en) Proxy of routing protocols to redundant controllers
US12106160B2 (en) First hop gateway redundancy in a network computing environment
US20230048749A1 (en) Service Function Chaining SFC-Based Packet Forwarding Method, Apparatus, and System
JP6369698B2 (ja) トラフィック切り替え方法、デバイス、およびシステム
US8824334B2 (en) Dynamic shared risk node group (SRNG) membership discovery
US8989199B1 (en) Control device discovery in networks having separate control and forwarding devices
US8995444B2 (en) Method and system for extending routing domain to non-routing end stations
CN104426763B (zh) 隧道切换方法、装置及交换机
US8891536B2 (en) Layer-3 services for united router farm
US8667174B2 (en) Method and system for survival of data plane through a total control plane failure
JP2019519146A (ja) ルーティング確立、パケット送信
US10530873B1 (en) Techniques for optimizing EVPN-IRB for IPv6-enabled data centers with top-of-rack deployments
US20220116317A1 (en) Processing a flow at the egress node in segment routing
CN102355398B (zh) Mpls l3vpn私有虚拟网快速重路由方法及系统
HK1233779B (en) Proxy of routing protocols to redundant controllers
HK1233779A1 (en) Proxy of routing protocols to redundant controllers
US12184545B2 (en) Packet processing method and related apparatus

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15777320

Country of ref document: EP

Kind code of ref document: A1

REEP Request for entry into the european phase

Ref document number: 2015777320

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2015777320

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2016560540

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2945333

Country of ref document: CA

NENP Non-entry into the national phase

Ref country code: DE