US20200296039A1 - Dynamic next-hop selection for routes in a network fabric - Google Patents
Dynamic next-hop selection for routes in a network fabric Download PDFInfo
- Publication number
- US20200296039A1 US20200296039A1 US16/886,973 US202016886973A US2020296039A1 US 20200296039 A1 US20200296039 A1 US 20200296039A1 US 202016886973 A US202016886973 A US 202016886973A US 2020296039 A1 US2020296039 A1 US 2020296039A1
- Authority
- US
- United States
- Prior art keywords
- network
- address
- next hop
- subnetwork
- network device
- 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.)
- Abandoned
Links
- 239000004744 fabric Substances 0.000 title description 5
- 238000000034 method Methods 0.000 claims description 24
- 230000009977 dual effect Effects 0.000 description 21
- 238000010586 diagram Methods 0.000 description 7
- 238000013459 approach Methods 0.000 description 6
- 230000006870 function Effects 0.000 description 5
- 230000009471 action Effects 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 238000011084 recovery Methods 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 230000006855 networking Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 206010047289 Ventricular extrasystoles Diseases 0.000 description 1
- 230000002776 aggregation Effects 0.000 description 1
- 238000004220 aggregation Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000005055 memory storage Effects 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 230000000644 propagated effect Effects 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 238000005129 volume perturbation calorimetry Methods 0.000 description 1
Images
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/74—Address processing for routing
- H04L45/745—Address table lookup; Address filtering
-
- 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
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/46—Interconnection of networks
- H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/02—Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
- H04L63/0272—Virtual private networks
Definitions
- the present disclosure relates to route advertisement in computer networking.
- Network elements in a computer network may advertise routes to hosts/subnets that are attached to particular network elements via a control plane, such as a Border Gateway Protocol (BGP) Ethernet Virtual Private Network (EVPN) control plane.
- BGP Border Gateway Protocol
- EVPN Virtual Private Network
- the route advertisements will associate the host/subnet with a “next hop” address associated with the particular network element to which the host/subnet is attached.
- VPC Virtual Extensible Local Area Network
- M-LAG Multi-Chassis Link Aggregation Group
- VPC peer network elements typically advertise routes to hosts and/or subnets that are attached to the VPC peer network elements in a control plane (e.g., Border Gateway Protocol (BGP) EVPN control plane) with a virtual network address associated with the VPC.
- BGP Border Gateway Protocol
- the virtual network address is a Virtual Tunnel Endpoint (VTEP) Internet Protocol (IP) address that is configured as a secondary address on a Network Virtualization Endpoint (NVE) interface of the peer VPC network elements.
- VTEP Virtual Tunnel Endpoint
- IP Internet Protocol
- NVE Network Virtualization Endpoint
- each of the peer VPC network elements is also associated with its own network address (e.g., IP address) on the NVE interface.
- FIG. 1 is a simplified block diagram of a system for advertising routes in a network domain that includes peer VPC network elements, according to an example embodiment.
- FIG. 2A illustrates advertising a dual homed host using the virtual network address of the VPC, according to an example embodiment.
- FIG. 2B illustrates advertising a dual connected subnet using the virtual network address of the VPC, according to an example embodiment.
- FIG. 3A illustrates advertising an orphan host using the individual network address of the peer VPC network element to which the orphan host is attached, according to an example embodiment.
- FIG. 3B illustrates advertising singly connected subnet using the individual network address of the peer VPC network element to which the subnet is attached, according to an example embodiment.
- FIG. 4 is a simplified block diagram of a peer VPC network device configured to advertise routes for attached hosts or subnets, according to an example embodiment.
- FIG. 5 is a flowchart depicting operations of a peer VPC network element advertising a route to an attached host, according to an example embodiment.
- a method for a first network device to advertise routes of locally connected routes/subnetworks comprises establishing a virtual port channel associated with a virtual network address.
- the virtual port channel comprises a plurality of network devices including the first network device associated with a first network address and a second network device associated with a second network address.
- the method further comprises detecting that a host is connected to the first network device and determining a next hop address to associate with the host.
- the next hop address is determined based on whether the host is also connected to the second network device of the virtual port channel.
- the method also comprises generating a route advertisement associating the next hop address with the host.
- VXLAN EVPN which is a Media Access Control (MAC) in IP/User Datagram Protocol (UDP) overlay
- MAC Media Access Control
- UDP IP/User Datagram Protocol
- the MAC table on the remote network elements can use the virtual network address of the VPC as the destination IP address for the VXLAN header whenever traffic is directed to an orphan or dual-homed host behind a particular VPC.
- the remote network elements do not need to update the network address from the virtual network address of the VPC.
- the underlay will detect the VPC peer failure and instead of an Equal Cost Multi-Path (ECMP) route, the virtual network address will be carried on a single path that is advertised by the VPC peer that remains functional.
- ECMP Equal Cost Multi-Path
- VPC virtual network address
- some of the traffic e.g., 50% on average
- destined to orphan hosts is directed to the wrong VPC peer based on the underlay ECMP hash, and travels across the VPC peer link to reach the final destination. This situation may occur for both layer 3 (i.e., routed) and layer 2 (i.e., bridged) traffic.
- an EVPN multi-homing approach with Ethernet Segment Identifier uses the individual network addresses of the VPC peer network elements to advertise the reachability of host (e.g., MAC and optionally IP address) and subnet prefix routes. While this ensures that orphan host reachability will only be advertised from its directly attached network element, for multi-homed hosts, the remote network elements will see an N-way ECMP route on the overlay, which requires support of MAC multipath routing. Some network elements may not support MAC multipath routing, and the convergence duration in case of a node failure may be quite long for network elements that do support MAC multipath routing, especially for multi-homed host routes.
- the techniques presented herein provide a hybrid approach in which the virtual network address is advertised for dual homed hosts (and dual attached subnets) and the individual network address of the network element is advertised for orphan hosts (and orphan subnets).
- This hybrid approach optimizes Forwarding Information Base (FIB) space, traffic forwarding, latency, and convergence.
- FIB Forwarding Information Base
- the network domain 110 may be an EVPN domain.
- the network domain 110 includes a plurality of network elements 120 , 122 , 124 , and 126 .
- the network elements 120 , 122 , 124 , and 126 may include routers, switches, or other physical or virtual network devices that route traffic throughout the network domain 110 .
- the network domain 110 may configure the network elements 120 , 122 , 124 , and 126 in a number of topologies (e.g., spine/leaf, ring, star, mesh, etc.).
- a route advertisement logic 130 in the network element 120 is configured to advertise routes (e.g., via Border Gateway Protocol (BGP) or Interior Gateway Protocol (IGP)) for hosts and subnetworks that are attached to the network domain 110 via the network element 120 .
- routes e.g., via Border Gateway Protocol (BGP) or Interior Gateway Protocol (IGP)
- BGP Border Gateway Protocol
- IGP Interior Gateway Protocol
- the other network elements 122 , 124 , and 126 may also include similar route advertisement logic.
- Network elements 120 and 122 are paired in a Virtual Port Channel (VPC) 140 as peer devices.
- VPC 140 is assigned a virtual network address that the underlay of the network domain 110 can route to either VPC peer 120 or VPC 122 .
- each of the VPC peers 120 and 122 is informed of any hosts or subnetworks that connect to the network domain 110 via either of the VPC peers 120 and 122 .
- the network elements advertise host routes and subnetwork route prefix reachability with a specific next hop address.
- the routes are advertised with the virtual network address associated with the VPC.
- the routes are advertised with the individual network address of the network element to which the host/subnetwork is attached.
- the host routes referred to herein include MAC, IPv4 and/or IPv6 addresses.
- the techniques described herein optimize forwarding, latency, and convergence by only advertising the most appropriate host routes. By only advertising the optimal routes with an intelligently selected next hop address, the remote network elements are not forced to use hardware FIB resources on saving suboptimal routes. These optimizations provide a distinct improvement in scalable data center network solutions.
- a simplified block diagram illustrates how the route advertisement logic 130 optimizes the route advertisement for a dual homed host 210 that is attached to both VPC peers 120 and 122 of the VPC 140 .
- the route advertisement logic 130 sends a route advertisement message 220 (e.g., a BGP update message) throughout the network domain 110 , such as to network element 126 .
- the route advertisement message 220 includes the MAC address of the host 210 (e.g., 1.1.1), the IP address/range of the host 210 (e.g., 10.1.1.1/32), and a next hop address that indicates the IP address to which messages to the host 210 should be addressed from within the network domain 110 . Since the dual homed host 210 is attached to both of the VPC peers 120 and 122 , the route advertisement logic 130 includes the IP address of the VPC (e.g., 5.5.5.5), which the underlay of the network domain 110 may route to either network element 120 or network element 122 .
- any messages sent over the network domain 110 to the host 210 will be addressed to the virtual network address (e.g., 5.5.5.5) of the VPC 140 rather than network address of either of the network elements 120 (e.g., 1.1.1.1) or 122 (e.g., 2.2.2.2).
- the virtual network address e.g., 5.5.5.5
- the network elements 120 e.g., 1.1.1.1
- 122 e.g., 2.2.2.2.
- FIG. 2B a simplified block diagram illustrates how the route advertisement logic 130 optimizes the route advertisement for a dual connected subnetwork 230 that is connected to both VPC peers 120 and 122 of the VPC 140 .
- the dual connected subnetwork 230 which includes a range of IP addresses (e.g., 30.1.1.0/24)
- the route advertisement logic 130 sends a route advertisement logic message 240 (e.g., a BGP update message) throughout the network domain 110 , such as to network element 126 .
- the route advertisement message 240 does not include a MAC address, since the subnetwork 230 may include multiple devices with multiple MAC addresses. However, the advertisement message 240 includes the IP address/range of the subnetwork 230 (e.g., 30.1.1.0/24), and a next hop address that indicates the IP address to which messages to hosts on the subnetwork 230 should be addressed from within the network domain 110 . Since the dual connected subnetwork 230 is attached to both of the VPC peers 120 and 122 , the route advertisement logic 130 includes the IP address of the VPC (e.g., 5.5.5.5), which the underlay of the network domain 110 may route to either network element 120 or network element 122 .
- IP address/range of the subnetwork 230 e.g., 30.1.1.0/24
- the route advertisement logic 130 includes the IP address of the VPC (e.g., 5.5.5.5), which the underlay of the network domain 110 may route to either network element 120 or network element 122 .
- any messages sent over the network domain 110 to hosts on the subnetwork 230 will be addressed to the virtual network address (e.g., 5.5.5.5) of the VPC 140 rather than network address of either of the network elements 120 (e.g., 1.1.1.1) or 122 (e.g., 2.2.2.2).
- the virtual network address e.g., 5.5.5.5
- the network elements 120 e.g., 1.1.1.1
- 122 e.g., 2.2.2.2.
- FIG. 2A and FIG. 2B show route advertisements for a dual homed host 210 and a dual connected subnetwork 230 , respectively.
- a similar route advertisement may be implemented for a host/subnetwork that is connected to more than two network elements, e.g. a multi-homed host or N-way connected subnetwork.
- the virtual network address associated with the aggregated N-way peered network elements i.e., analogous to the two-way VPC 140 and its associated virtual network address
- is advertised for the N-way host/subnetwork if all of the N-way peered network elements are all actively connected to the multi-homed host or N-way connected subnetwork.
- one or more route advertisements are propagated with the network address of the individual network element(s) that is/are connected to the host/subnetwork, as described hereinafter with respect to FIG. 3A and FIG. 3B .
- a simplified block diagram illustrates how the route advertisement logic 130 optimizes the route advertisement for an orphan host 310 that is attached to only one VPC peer 120 of the VPC 140 .
- the route advertisement logic 130 sends a route advertisement message 320 (e.g., a BGP update message) throughout the network domain 110 , such as to network element 126 .
- the route advertisement message 320 includes the MAC address of the orphan host 210 (e.g., 2 . 2 .
- the route advertisement logic 130 includes the IP address of the VPC peer 120 to which the orphan host is attached (e.g., 1.1.1.1). In other words, any messages sent over the network domain 110 to the orphan host 310 will be addressed to the individual network address (e.g., 1.1.1.1) of the network element 120 to which it is attached, rather than the virtual network address of VPC 140 (e.g., 5.5.5.5).
- FIG. 3B a simplified block diagram illustrates how the route advertisement logic 130 optimizes the route advertisement for a single connected subnetwork 330 that is connected to only one VPC peer 122 of the VPC 140 .
- the single connected subnetwork 330 which includes a range of IP address (e.g., 30.1.1.0/24)
- the route advertisement logic 130 sends a route advertisement logic message 340 (e.g., a BGP update message) throughout the network domain 110 , such as to network element 126 .
- the route advertisement message 340 does not include a MAC address, since the subnetwork 330 may include multiple devices with multiple MAC addresses. However, the advertisement message 340 includes the IP address/range of the subnetwork 230 (e.g., 30.1.1.0/24), and a next hop address that indicates the IP address to which messages to hosts on the subnetwork 230 should be addressed from within the network domain 110 . Since the single connected subnetwork 330 is only connected to the VPC peer 122 , the route advertisement logic 130 includes the IP address of the VPC peer 122 (e.g., 2.2.2.2).
- any messages sent over the network domain 110 to hosts on the subnetwork 330 will be addressed to the individual network address (e.g., 2.2.2.2) of the network element 122 , rather than the virtual network address of VPC 140 (e.g., 5.5.5.5).
- the VPC peer network element 120 dynamically selects the next hop address for host routes according to varying conditions.
- a host is dual/multi homed if the host is learned via a VPC peer link or as part of an ESI. If the host is dual/multi homed, then the BGP EVPN control plane will dynamically select the virtual IP address of the VPC as the next hop address of the host route.
- a host is single homed/orphaned if the host is learned via an individual port. If the host is single homed/orphaned, then the BGP EVPN control plane will dynamically select the IP address of the port/network element that found the host.
- the host route may be updated for other events that affect the reachability of the host. For instance, a VPC domain failure or recovery will affect whether the virtual IP address of the VPC is available as a next hop address.
- the failure (or recovery) of the VPC may be attributed to the failure/recovery of the VPC peer network elements and/or the VPC peer link.
- ARP Address Resolution Protocol
- ND Neighbor Discovery entries
- the decision on whether or not reachability of a given host is advertised over the network domain may be based on whether the host is reachable via a locally attached leg (e.g., VPC or orphan).
- the EVPN control plane may monitor for a host changing from being single homed/orphaned to dual/multi homed, or changing from being dual/multi homed to single homed/orphaned.
- the control plane may change the route advertisement from the individual network address of the single network element to the virtual network address of the VPC.
- the control plane may change the route advertisement from the virtual network address of the VPC to the individual network address of the single network element.
- the VPC peer network element 120 dynamically selects the next hop address for network prefix routes according to varying conditions.
- a subnetwork is single homed (or orphaned) if it exists local to only one VPC peer network element.
- the BGP EVPN control plane selects the individual network address of the local network element as the next hop address.
- the next hop address selection process may be introduced through a route map that is applied when redistributing network prefix routes (e.g., EVPN Type 5 routes) into the BGP EVPN control plane. This may include external subnetworks as well as subnetworks associated with networks that are locally instantiated on the VPC peers.
- the route map may include a new “set” action to influence the selection of the next hop address.
- the “set” action may modify the next hop address in the BGP update messages when advertising reachability to other BGP peers.
- this approach may be extended to other “match” objects to provide maximum flexibility in customizing the next hop address. This approach is not limited to the use cases described herein, and may be extended to other use cases.
- the networking device includes a network interface unit in the form of a plurality of network ports 410 - 415 , a processor Application Specific Integrated Circuit (ASIC) 420 that performs network processing functions, one or more processors 430 (e.g., microprocessors or microcontrollers), and memory 440 .
- the network device 120 may include multiple network processor ASICs to perform various network processing functions.
- the memory 440 stores the route advertisement logic 130 , which may include instructions for advertising host/subnetwork routes, such as via BGP update messages. It is to be understood that, in certain examples, the network device 120 may be a virtual (software-based) appliance.
- the processor 430 performs higher level control functions of the network device 120 , in concert with functions of the network processor ASIC 420 .
- the memory 440 may include read only memory (ROM), random access memory (RAM), magnetic disk storage media devices, optical storage media devices, flash memory devices, electrical, optical, or other physical/tangible memory storage devices.
- the memory 440 may comprise one or more tangible (non-transitory) computer readable storage media (e.g., a memory device) encoded with software comprising computer executable instructions and when the software is executed (by the one or more processors 430 ) it is operable to perform the operations described herein.
- the memory 440 stores instructions for the route advertisement logic 130 described above.
- the processor 430 executes the instructions for the route advertisement logic 130
- the processor 430 is caused to control the network device 120 to perform the operations described herein.
- the functions of the route advertisement logic 130 may be performed by the network processor ASIC 420 .
- a flowchart illustrates a process 500 performed by a first network device (e.g., VPC peer network element 120 ) in selecting and advertising a host route for a host connected to the network device.
- a VPC is established between a plurality of network devices including a first network device and a second network device.
- the first network device and the second network device are VPC peer devices.
- the first network device detects a host connected to the first network device.
- the host may be a physical computing device, a virtual machine on a physical device, or a container workload running on a physical or virtual machine.
- the first network device determines whether the host is connected to the second network device of VPC. In one example, the first network device determines a next hop address for the host based on whether the host is connected to one or both of the first network device and the second network device. If the host is connected to second network device, as well as the first network device, then the first network device selects the virtual network address of the VPC as the next hop address of the host in step 540 . Alternatively, if the host is only connected to the first network device, but not the second network device, then the first network device selects the network address of the first network device as the next hop address for the host in step 545 .
- the VPC may include more than the first network device and the second network device.
- the first network device only selects the virtual network address as the next hop address if all of the peer devices in the VPC are connected to the host. If at least one of the peer devices in the VPC are not connected to the host, then the first network element will select the network address of the first device as the next hop address.
- the first network device In step 550 , the first network device generates a route advertisement associating the next hop address selected in either step 540 or step 545 with the host.
- the route advertisement may include a BGP update message.
- the first network device may use a similar process to determine a next hop address for a subnetwork connected to one or both of the VPC peer network elements.
- the format of the route advertisement may differ when advertising a subnetwork instead of a host, but the steps of determining a next hop address will be similar between the two formats. For instance, advertising a host with an EVPN Type 2 route and advertising a subnetwork with an EVPN Type 5 route will not differ in how the first network device determines the next hop address to include in each type of route advertisement.
- the techniques presented herein influence the selection of a next hop address for a network domain (e.g., an EVPN domain with BGP) that includes a VPC environment, to optimize forwarding, convergence, and hardware table usage in single/dual/multi homing scenarios.
- the next hop address for a host route is dynamically selected based on the specific host connectivity options (e.g., single or dual/multi homed), which improves forwarding to orphan hosts specifically in VPC scenarios.
- the new route map “set” action provides an extensible way to influence the selection of various selection objects (e.g., the next hop address). These approaches optimize the route advertisement for orphan/single homed hosts while keeping the flexibility for handling new use case scenarios.
- the techniques presented herein avoid two hop forwarding for any traffic directed to orphan or singly connected hosts within a BGP EVPN fabric. Additionally, the dynamic selection of the next hop address optimizes the usage of FIB, MAC, and associated ECMP tables by using the virtual network address for dual/multi homed prefixes, and using individual network addresses of network elements for single homed/orphan prefixes.
- a method for a first network device in a virtual port channel.
- the method comprises establishing a virtual port channel associated with a virtual network address.
- the virtual port channel comprises a plurality of network devices including the first network device associated with a first network address and a second network device associated with a second network address.
- the method further comprises detecting that a host is connected to the first network device and determining a next hop address to associate with the host.
- the next hop address is determined based on whether the host is also connected to the second network device of the virtual port channel.
- the method also comprises generating a route advertisement associating the next hop address with the host.
- an apparatus comprising a network interface unit and a processor.
- the network interface unit is configured to communicate over a computer network with computing devices.
- the processor is configured to establish a virtual port channel associated with a virtual network address.
- the virtual port channel comprises a plurality of network devices including the apparatus as a first network device associated with a first network address and a second network device associated with a second network address.
- the processor is also configured to detect that a host is connected to the first network device via the network interface unit and determine a next hop address to associate with the host.
- the processor determines the next hop address based on whether the host is also connected to the second network device of the virtual port channel.
- the processor is further configured to generate a route advertisement associating the next hop address with the host.
- one or more non-transitory computer readable storage media is encoded with software comprising computer executable instructions and, when the software is executed by a processor on a first network device, operable to cause the processor to establish a virtual port channel associated with a virtual network address.
- the virtual port channel comprises a plurality of network devices including the first network device associated with a first network address and a second network device associated with a second network address.
- the instructions are also operable to cause the processor to detect that a host is connected to the first network device and determine a next hop address to associate with the host.
- the instructions cause the processor to determine the next hop address based on whether the host is also connected to the second network device of the virtual port channel.
- the instructions also cause the processor to generate a route advertisement associating the next hop address with the host.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Description
- This application is a continuation of U.S. patent application Ser. No. 15/827,183, filed Nov. 30, 2017, entitled “Dynamic Next-Hop Selection for Routes in a Network Fabric,” the entire contents of which are hereby incorporated by reference.
- The present disclosure relates to route advertisement in computer networking.
- Network elements in a computer network may advertise routes to hosts/subnets that are attached to particular network elements via a control plane, such as a Border Gateway Protocol (BGP) Ethernet Virtual Private Network (EVPN) control plane. The route advertisements will associate the host/subnet with a “next hop” address associated with the particular network element to which the host/subnet is attached.
- Network elements in a computer network, such as a Virtual Extensible Local Area Network (VXLAN) EVPN fabric, may be grouped to provide redundancy and increase bandwidth for connected devices, such as servers. For instance, Virtual Port Channel (VPC) groups are one example of a Multi-Chassis Link Aggregation Group (MC-LAG) that group multiple network elements. VPC peer network elements typically advertise routes to hosts and/or subnets that are attached to the VPC peer network elements in a control plane (e.g., Border Gateway Protocol (BGP) EVPN control plane) with a virtual network address associated with the VPC. In some instances, the virtual network address is a Virtual Tunnel Endpoint (VTEP) Internet Protocol (IP) address that is configured as a secondary address on a Network Virtualization Endpoint (NVE) interface of the peer VPC network elements. However, each of the peer VPC network elements is also associated with its own network address (e.g., IP address) on the NVE interface.
-
FIG. 1 is a simplified block diagram of a system for advertising routes in a network domain that includes peer VPC network elements, according to an example embodiment. -
FIG. 2A illustrates advertising a dual homed host using the virtual network address of the VPC, according to an example embodiment. -
FIG. 2B illustrates advertising a dual connected subnet using the virtual network address of the VPC, according to an example embodiment. -
FIG. 3A illustrates advertising an orphan host using the individual network address of the peer VPC network element to which the orphan host is attached, according to an example embodiment. -
FIG. 3B illustrates advertising singly connected subnet using the individual network address of the peer VPC network element to which the subnet is attached, according to an example embodiment. -
FIG. 4 is a simplified block diagram of a peer VPC network device configured to advertise routes for attached hosts or subnets, according to an example embodiment. -
FIG. 5 is a flowchart depicting operations of a peer VPC network element advertising a route to an attached host, according to an example embodiment. - A method is provided for a first network device to advertise routes of locally connected routes/subnetworks. The method comprises establishing a virtual port channel associated with a virtual network address. The virtual port channel comprises a plurality of network devices including the first network device associated with a first network address and a second network device associated with a second network address. The method further comprises detecting that a host is connected to the first network device and determining a next hop address to associate with the host. The next hop address is determined based on whether the host is also connected to the second network device of the virtual port channel. The method also comprises generating a route advertisement associating the next hop address with the host.
- Using the virtual network address of a VPC provides several advantages. All of the other network elements (and hosts attached to the other network elements) only store a single network address for the peered VPC network elements (and hosts attached to the VPC). In this way, the number of network addresses stored at each network element scales with the number of VPCs rather than with the number of individual network elements. Specific to a VXLAN EVPN implementation, which is a Media Access Control (MAC) in IP/User Datagram Protocol (UDP) overlay, the MAC table on the remote network elements can use the virtual network address of the VPC as the destination IP address for the VXLAN header whenever traffic is directed to an orphan or dual-homed host behind a particular VPC. Additionally, in the case of a single VPC peer failure, the remote network elements do not need to update the network address from the virtual network address of the VPC. The underlay will detect the VPC peer failure and instead of an Equal Cost Multi-Path (ECMP) route, the virtual network address will be carried on a single path that is advertised by the VPC peer that remains functional.
- However, one issue with using the virtual network address of the VPC arises when some of the traffic (e.g., 50% on average) destined to orphan hosts is directed to the wrong VPC peer based on the underlay ECMP hash, and travels across the VPC peer link to reach the final destination. This situation may occur for both layer 3 (i.e., routed) and layer 2 (i.e., bridged) traffic.
- In one example, an EVPN multi-homing approach with Ethernet Segment Identifier (ESI) uses the individual network addresses of the VPC peer network elements to advertise the reachability of host (e.g., MAC and optionally IP address) and subnet prefix routes. While this ensures that orphan host reachability will only be advertised from its directly attached network element, for multi-homed hosts, the remote network elements will see an N-way ECMP route on the overlay, which requires support of MAC multipath routing. Some network elements may not support MAC multipath routing, and the convergence duration in case of a node failure may be quite long for network elements that do support MAC multipath routing, especially for multi-homed host routes.
- The techniques presented herein provide a hybrid approach in which the virtual network address is advertised for dual homed hosts (and dual attached subnets) and the individual network address of the network element is advertised for orphan hosts (and orphan subnets). This hybrid approach optimizes Forwarding Information Base (FIB) space, traffic forwarding, latency, and convergence.
- Referring now to
FIG. 1 , a network system is shown that is configured to advertise routes across anetwork domain 110. In one example, thenetwork domain 110 may be an EVPN domain. Thenetwork domain 110 includes a plurality ofnetwork elements network elements network domain 110. Thenetwork domain 110 may configure thenetwork elements route advertisement logic 130 in thenetwork element 120 is configured to advertise routes (e.g., via Border Gateway Protocol (BGP) or Interior Gateway Protocol (IGP)) for hosts and subnetworks that are attached to thenetwork domain 110 via thenetwork element 120. Though not explicitly depicted inFIG. 1 , theother network elements -
Network elements peer link 145 connects the twoVPC peer devices VPC 140 is assigned a virtual network address that the underlay of thenetwork domain 110 can route to eitherVPC peer 120 orVPC 122. Additionally, in configuring theVPC 140, each of theVPC peers network domain 110 via either of theVPC peers - In order to optimize the usage of resources and forwarding in a network domain (e.g., a VXLAN BGP EVPN fabric with VPC), the network elements advertise host routes and subnetwork route prefix reachability with a specific next hop address. For dual homed prefixes (e.g., hosts or subnetworks) the routes are advertised with the virtual network address associated with the VPC. For single homed/orphan prefixes (i.e., hosts or subnetworks) the routes are advertised with the individual network address of the network element to which the host/subnetwork is attached. In one example, the host routes referred to herein include MAC, IPv4 and/or IPv6 addresses.
- The techniques described herein optimize forwarding, latency, and convergence by only advertising the most appropriate host routes. By only advertising the optimal routes with an intelligently selected next hop address, the remote network elements are not forced to use hardware FIB resources on saving suboptimal routes. These optimizations provide a distinct improvement in scalable data center network solutions.
- Referring now to
FIG. 2A , a simplified block diagram illustrates how theroute advertisement logic 130 optimizes the route advertisement for a dual homedhost 210 that is attached to both VPC peers 120 and 122 of theVPC 140. When the dual homedhost 210, which has a MAC address of 1.1.1 and an IP address of 10.1.1.1, connects to thenetwork domain 110 via both of the VPC peers 120 and 122, theroute advertisement logic 130 sends a route advertisement message 220 (e.g., a BGP update message) throughout thenetwork domain 110, such as tonetwork element 126. Theroute advertisement message 220 includes the MAC address of the host 210 (e.g., 1.1.1), the IP address/range of the host 210 (e.g., 10.1.1.1/32), and a next hop address that indicates the IP address to which messages to thehost 210 should be addressed from within thenetwork domain 110. Since the dual homedhost 210 is attached to both of the VPC peers 120 and 122, theroute advertisement logic 130 includes the IP address of the VPC (e.g., 5.5.5.5), which the underlay of thenetwork domain 110 may route to eithernetwork element 120 ornetwork element 122. In other words, any messages sent over thenetwork domain 110 to thehost 210 will be addressed to the virtual network address (e.g., 5.5.5.5) of theVPC 140 rather than network address of either of the network elements 120 (e.g., 1.1.1.1) or 122 (e.g., 2.2.2.2). - Referring now to
FIG. 2B , a simplified block diagram illustrates how theroute advertisement logic 130 optimizes the route advertisement for a dualconnected subnetwork 230 that is connected to both VPC peers 120 and 122 of theVPC 140. Similar to the example described with respect toFIG. 2A , when the dualconnected subnetwork 230, which includes a range of IP addresses (e.g., 30.1.1.0/24), connects to thenetwork domain 110 via both of the VPC peers 120 and 122, theroute advertisement logic 130 sends a route advertisement logic message 240 (e.g., a BGP update message) throughout thenetwork domain 110, such as tonetwork element 126. Theroute advertisement message 240 does not include a MAC address, since thesubnetwork 230 may include multiple devices with multiple MAC addresses. However, theadvertisement message 240 includes the IP address/range of the subnetwork 230 (e.g., 30.1.1.0/24), and a next hop address that indicates the IP address to which messages to hosts on thesubnetwork 230 should be addressed from within thenetwork domain 110. Since the dualconnected subnetwork 230 is attached to both of the VPC peers 120 and 122, theroute advertisement logic 130 includes the IP address of the VPC (e.g., 5.5.5.5), which the underlay of thenetwork domain 110 may route to eithernetwork element 120 ornetwork element 122. In other words, any messages sent over thenetwork domain 110 to hosts on thesubnetwork 230 will be addressed to the virtual network address (e.g., 5.5.5.5) of theVPC 140 rather than network address of either of the network elements 120 (e.g., 1.1.1.1) or 122 (e.g., 2.2.2.2). - For ease of illustration, the examples depicted in
FIG. 2A andFIG. 2B show route advertisements for a dual homedhost 210 and a dualconnected subnetwork 230, respectively. However, a similar route advertisement may be implemented for a host/subnetwork that is connected to more than two network elements, e.g. a multi-homed host or N-way connected subnetwork. In these instances, the virtual network address associated with the aggregated N-way peered network elements (i.e., analogous to the two-way VPC 140 and its associated virtual network address) is advertised for the N-way host/subnetwork if all of the N-way peered network elements are all actively connected to the multi-homed host or N-way connected subnetwork. If any of the peered network elements are not connected to the host/subnetwork, then one or more route advertisements are propagated with the network address of the individual network element(s) that is/are connected to the host/subnetwork, as described hereinafter with respect toFIG. 3A andFIG. 3B . - Referring now to
FIG. 3A , a simplified block diagram illustrates how theroute advertisement logic 130 optimizes the route advertisement for anorphan host 310 that is attached to only oneVPC peer 120 of theVPC 140. When theorphan host 310, which has a MAC address of 2.2.2 and an IP address of 10.1.1.2, connects to thenetwork domain 110 via theVPC peer 120, but not theVPC peer 122, theroute advertisement logic 130 sends a route advertisement message 320 (e.g., a BGP update message) throughout thenetwork domain 110, such as tonetwork element 126. Theroute advertisement message 320 includes the MAC address of the orphan host 210 (e.g., 2.2.2), the IP address/range of the host 310 (e.g., 10.1.1.2/32), and a next hop address that indicates the IP address to which messages to thehost 210 should be addressed from within thenetwork domain 110. Since theorphan host 210 is only attached to one of the VPC peers (e.g., network element 120), theroute advertisement logic 130 includes the IP address of theVPC peer 120 to which the orphan host is attached (e.g., 1.1.1.1). In other words, any messages sent over thenetwork domain 110 to theorphan host 310 will be addressed to the individual network address (e.g., 1.1.1.1) of thenetwork element 120 to which it is attached, rather than the virtual network address of VPC 140 (e.g., 5.5.5.5). - Referring now to
FIG. 3B , a simplified block diagram illustrates how theroute advertisement logic 130 optimizes the route advertisement for a singleconnected subnetwork 330 that is connected to only oneVPC peer 122 of theVPC 140. Similar to the example described with respect toFIG. 3A , when the singleconnected subnetwork 330, which includes a range of IP address (e.g., 30.1.1.0/24), connects to thenetwork domain 110 via theVPC peer 122, but not theVPC peer 120, theroute advertisement logic 130 sends a route advertisement logic message 340 (e.g., a BGP update message) throughout thenetwork domain 110, such as tonetwork element 126. Theroute advertisement message 340 does not include a MAC address, since thesubnetwork 330 may include multiple devices with multiple MAC addresses. However, theadvertisement message 340 includes the IP address/range of the subnetwork 230 (e.g., 30.1.1.0/24), and a next hop address that indicates the IP address to which messages to hosts on thesubnetwork 230 should be addressed from within thenetwork domain 110. Since the singleconnected subnetwork 330 is only connected to theVPC peer 122, theroute advertisement logic 130 includes the IP address of the VPC peer 122 (e.g., 2.2.2.2). In other words, any messages sent over thenetwork domain 110 to hosts on thesubnetwork 330 will be addressed to the individual network address (e.g., 2.2.2.2) of thenetwork element 122, rather than the virtual network address of VPC 140 (e.g., 5.5.5.5). - Referring back to
FIG. 2A and toFIG. 3A , the VPCpeer network element 120 dynamically selects the next hop address for host routes according to varying conditions. In general, a host is dual/multi homed if the host is learned via a VPC peer link or as part of an ESI. If the host is dual/multi homed, then the BGP EVPN control plane will dynamically select the virtual IP address of the VPC as the next hop address of the host route. Alternatively, a host is single homed/orphaned if the host is learned via an individual port. If the host is single homed/orphaned, then the BGP EVPN control plane will dynamically select the IP address of the port/network element that found the host. - In addition to dynamically selecting the next hop address with a host that is first learned, the host route may be updated for other events that affect the reachability of the host. For instance, a VPC domain failure or recovery will affect whether the virtual IP address of the VPC is available as a next hop address. The failure (or recovery) of the VPC may be attributed to the failure/recovery of the VPC peer network elements and/or the VPC peer link. Additionally, while Address Resolution Protocol (ARP)/Neighbor Discovery (ND) entries may be synchronized between the VPC peers, the decision on whether or not reachability of a given host is advertised over the network domain may be based on whether the host is reachable via a locally attached leg (e.g., VPC or orphan). Further, the EVPN control plane may monitor for a host changing from being single homed/orphaned to dual/multi homed, or changing from being dual/multi homed to single homed/orphaned. In other words, when the host moves from being attached to a single network element to two (or more) network elements in a VPC, the control plane may change the route advertisement from the individual network address of the single network element to the virtual network address of the VPC. Similarly, when the host moves from being dual/multi homed to single homed/orphaned, the control plane may change the route advertisement from the virtual network address of the VPC to the individual network address of the single network element.
- Referring back to
FIG. 2B and toFIG. 3B , the VPCpeer network element 120 dynamically selects the next hop address for network prefix routes according to varying conditions. A subnetwork is single homed (or orphaned) if it exists local to only one VPC peer network element. In this case, the BGP EVPN control plane selects the individual network address of the local network element as the next hop address. The next hop address selection process may be introduced through a route map that is applied when redistributing network prefix routes (e.g.,EVPN Type 5 routes) into the BGP EVPN control plane. This may include external subnetworks as well as subnetworks associated with networks that are locally instantiated on the VPC peers. The route map may include a new “set” action to influence the selection of the next hop address. The “set” action may modify the next hop address in the BGP update messages when advertising reachability to other BGP peers. With the flexibility of the route map, this approach may be extended to other “match” objects to provide maximum flexibility in customizing the next hop address. This approach is not limited to the use cases described herein, and may be extended to other use cases. - Referring now to
FIG. 4 , a simplified block diagram illustrates a network device (e.g., VPC peer network element 120) that is configured to participate in the techniques presented herein. The networking device includes a network interface unit in the form of a plurality of network ports 410-415, a processor Application Specific Integrated Circuit (ASIC) 420 that performs network processing functions, one or more processors 430 (e.g., microprocessors or microcontrollers), andmemory 440. Thenetwork device 120 may include multiple network processor ASICs to perform various network processing functions. Thememory 440 stores theroute advertisement logic 130, which may include instructions for advertising host/subnetwork routes, such as via BGP update messages. It is to be understood that, in certain examples, thenetwork device 120 may be a virtual (software-based) appliance. Theprocessor 430 performs higher level control functions of thenetwork device 120, in concert with functions of thenetwork processor ASIC 420. - The
memory 440 may include read only memory (ROM), random access memory (RAM), magnetic disk storage media devices, optical storage media devices, flash memory devices, electrical, optical, or other physical/tangible memory storage devices. Thus, in general, thememory 440 may comprise one or more tangible (non-transitory) computer readable storage media (e.g., a memory device) encoded with software comprising computer executable instructions and when the software is executed (by the one or more processors 430) it is operable to perform the operations described herein. For example, thememory 440 stores instructions for theroute advertisement logic 130 described above. When theprocessor 430 executes the instructions for theroute advertisement logic 130, theprocessor 430 is caused to control thenetwork device 120 to perform the operations described herein. As an alternative, the functions of theroute advertisement logic 130 may be performed by thenetwork processor ASIC 420. - Referring now to
FIG. 5 , a flowchart illustrates aprocess 500 performed by a first network device (e.g., VPC peer network element 120) in selecting and advertising a host route for a host connected to the network device. Instep 510, a VPC is established between a plurality of network devices including a first network device and a second network device. In one example, the first network device and the second network device are VPC peer devices. Instep 520, the first network device detects a host connected to the first network device. In one example, the host may be a physical computing device, a virtual machine on a physical device, or a container workload running on a physical or virtual machine. - In
step 530, the first network device determines whether the host is connected to the second network device of VPC. In one example, the first network device determines a next hop address for the host based on whether the host is connected to one or both of the first network device and the second network device. If the host is connected to second network device, as well as the first network device, then the first network device selects the virtual network address of the VPC as the next hop address of the host instep 540. Alternatively, if the host is only connected to the first network device, but not the second network device, then the first network device selects the network address of the first network device as the next hop address for the host instep 545. - In another example, the VPC may include more than the first network device and the second network device. In this instance, the first network device only selects the virtual network address as the next hop address if all of the peer devices in the VPC are connected to the host. If at least one of the peer devices in the VPC are not connected to the host, then the first network element will select the network address of the first device as the next hop address.
- In
step 550, the first network device generates a route advertisement associating the next hop address selected in either step 540 or step 545 with the host. In one example, the route advertisement may include a BGP update message. - The first network device may use a similar process to determine a next hop address for a subnetwork connected to one or both of the VPC peer network elements. The format of the route advertisement may differ when advertising a subnetwork instead of a host, but the steps of determining a next hop address will be similar between the two formats. For instance, advertising a host with an EVPN Type 2 route and advertising a subnetwork with an
EVPN Type 5 route will not differ in how the first network device determines the next hop address to include in each type of route advertisement. - In summary, the techniques presented herein influence the selection of a next hop address for a network domain (e.g., an EVPN domain with BGP) that includes a VPC environment, to optimize forwarding, convergence, and hardware table usage in single/dual/multi homing scenarios. In one instance, the next hop address for a host route is dynamically selected based on the specific host connectivity options (e.g., single or dual/multi homed), which improves forwarding to orphan hosts specifically in VPC scenarios. Additionally, the new route map “set” action provides an extensible way to influence the selection of various selection objects (e.g., the next hop address). These approaches optimize the route advertisement for orphan/single homed hosts while keeping the flexibility for handling new use case scenarios.
- In particular, the techniques presented herein avoid two hop forwarding for any traffic directed to orphan or singly connected hosts within a BGP EVPN fabric. Additionally, the dynamic selection of the next hop address optimizes the usage of FIB, MAC, and associated ECMP tables by using the virtual network address for dual/multi homed prefixes, and using individual network addresses of network elements for single homed/orphan prefixes.
- In one form, a method is provided for a first network device in a virtual port channel. The method comprises establishing a virtual port channel associated with a virtual network address. The virtual port channel comprises a plurality of network devices including the first network device associated with a first network address and a second network device associated with a second network address. The method further comprises detecting that a host is connected to the first network device and determining a next hop address to associate with the host. The next hop address is determined based on whether the host is also connected to the second network device of the virtual port channel. The method also comprises generating a route advertisement associating the next hop address with the host.
- In another form, an apparatus is provided comprising a network interface unit and a processor. The network interface unit is configured to communicate over a computer network with computing devices. The processor is configured to establish a virtual port channel associated with a virtual network address. The virtual port channel comprises a plurality of network devices including the apparatus as a first network device associated with a first network address and a second network device associated with a second network address. The processor is also configured to detect that a host is connected to the first network device via the network interface unit and determine a next hop address to associate with the host. The processor determines the next hop address based on whether the host is also connected to the second network device of the virtual port channel. The processor is further configured to generate a route advertisement associating the next hop address with the host.
- In still another form, one or more non-transitory computer readable storage media is encoded with software comprising computer executable instructions and, when the software is executed by a processor on a first network device, operable to cause the processor to establish a virtual port channel associated with a virtual network address. The virtual port channel comprises a plurality of network devices including the first network device associated with a first network address and a second network device associated with a second network address. The instructions are also operable to cause the processor to detect that a host is connected to the first network device and determine a next hop address to associate with the host. The instructions cause the processor to determine the next hop address based on whether the host is also connected to the second network device of the virtual port channel. The instructions also cause the processor to generate a route advertisement associating the next hop address with the host.
- The above description is intended by way of example only. Although the present disclosure has been described in detail with reference to particular arrangements and configurations, these example configurations and arrangements may be changed significantly without departing from the scope of the present disclosure. In particular, while specific protocols, such as EVPN, BGP, and VPC, have been used herein as examples, other protocols may be used by a person of ordinary sill in the art with a scope similar to the present disclosure. Additionally, while subnetworks have been described herein as connected to one or more network elements, subnetworks that are locally originated may also be used by a person of ordinary skill in the art in a manner similar to what is presented in the present disclosure.
Claims (20)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16/886,973 US20200296039A1 (en) | 2017-11-30 | 2020-05-29 | Dynamic next-hop selection for routes in a network fabric |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US15/827,183 US10708185B2 (en) | 2017-11-30 | 2017-11-30 | Dynamic next-hop selection for routes in a network fabric |
US16/886,973 US20200296039A1 (en) | 2017-11-30 | 2020-05-29 | Dynamic next-hop selection for routes in a network fabric |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/827,183 Continuation US10708185B2 (en) | 2017-11-30 | 2017-11-30 | Dynamic next-hop selection for routes in a network fabric |
Publications (1)
Publication Number | Publication Date |
---|---|
US20200296039A1 true US20200296039A1 (en) | 2020-09-17 |
Family
ID=66633756
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/827,183 Active 2037-12-06 US10708185B2 (en) | 2017-11-30 | 2017-11-30 | Dynamic next-hop selection for routes in a network fabric |
US16/886,973 Abandoned US20200296039A1 (en) | 2017-11-30 | 2020-05-29 | Dynamic next-hop selection for routes in a network fabric |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/827,183 Active 2037-12-06 US10708185B2 (en) | 2017-11-30 | 2017-11-30 | Dynamic next-hop selection for routes in a network fabric |
Country Status (1)
Country | Link |
---|---|
US (2) | US10708185B2 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20220337515A1 (en) * | 2019-12-31 | 2022-10-20 | Huawei Technologies Co., Ltd. | Routing Information Processing Method and Apparatus |
Families Citing this family (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11425031B2 (en) * | 2019-03-28 | 2022-08-23 | Hewlett Packard Enterprise Development Lp | Layer 3 multi-chassis link aggregation group |
CN111740899B (en) * | 2020-07-13 | 2022-07-12 | 中国联合网络通信集团有限公司 | ARP request message forwarding method, cross-device link aggregation group and network device |
US11658934B2 (en) * | 2021-04-26 | 2023-05-23 | Verizon Patent And Licensing Inc. | Systems and methods for advertising internet protocol (IP) version 4 network layer routing information with an IP version 6 Next Hop address |
CN113765805B (en) * | 2021-08-31 | 2023-10-20 | 上海完美时空软件有限公司 | Calling-based communication method, device, storage medium and equipment |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20080019383A1 (en) * | 2006-07-20 | 2008-01-24 | British Telecommunications Public Limited Company | Telecommunications switching |
US20100074268A1 (en) * | 2005-05-31 | 2010-03-25 | Cisco Technology, Inc. | Multi-homing using controlled route leakage at a backup service provider |
US10135683B1 (en) * | 2010-12-30 | 2018-11-20 | Juniper Networks, Inc. | Dynamically generating application-layer traffic optimization protocol endpoint attributes |
Family Cites Families (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6970464B2 (en) | 2003-04-01 | 2005-11-29 | Cisco Technology, Inc. | Method for recursive BGP route updates in MPLS networks |
US8953590B1 (en) | 2011-03-23 | 2015-02-10 | Juniper Networks, Inc. | Layer two virtual private network having control plane address learning supporting multi-homed customer networks |
US9258266B2 (en) | 2012-08-30 | 2016-02-09 | Cisco Technology, Inc. | Host detection by top of rack switch devices in data center environments |
US9356886B2 (en) * | 2012-10-05 | 2016-05-31 | Cisco Technology, Inc. | Techniques for scalable and foolproof virtual machine move handling with virtual port channels |
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 |
US9225597B2 (en) | 2014-03-14 | 2015-12-29 | Nicira, Inc. | Managed gateways peering with external router to attract ingress packets |
US9503391B2 (en) | 2014-04-11 | 2016-11-22 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and system for network function placement |
US9716628B2 (en) | 2014-05-23 | 2017-07-25 | Cisco Technology, Inc. | Touchless orchestration for layer 3 data center interconnect in communications networks |
US9590824B1 (en) | 2014-08-05 | 2017-03-07 | Cisco Technology, Inc. | Signaling host move in dynamic fabric automation using multiprotocol BGP |
US10476797B2 (en) | 2015-04-13 | 2019-11-12 | Dell Products L.P. | Systems and methods to route over a link aggregation group to a true next hop |
US9985867B2 (en) | 2015-12-11 | 2018-05-29 | Cisco Technology, Inc. | Optimizing EVPN for data centers with redundant top-of-rack deployments |
-
2017
- 2017-11-30 US US15/827,183 patent/US10708185B2/en active Active
-
2020
- 2020-05-29 US US16/886,973 patent/US20200296039A1/en not_active Abandoned
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20100074268A1 (en) * | 2005-05-31 | 2010-03-25 | Cisco Technology, Inc. | Multi-homing using controlled route leakage at a backup service provider |
US20080019383A1 (en) * | 2006-07-20 | 2008-01-24 | British Telecommunications Public Limited Company | Telecommunications switching |
US10135683B1 (en) * | 2010-12-30 | 2018-11-20 | Juniper Networks, Inc. | Dynamically generating application-layer traffic optimization protocol endpoint attributes |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20220337515A1 (en) * | 2019-12-31 | 2022-10-20 | Huawei Technologies Co., Ltd. | Routing Information Processing Method and Apparatus |
US11870686B2 (en) * | 2019-12-31 | 2024-01-09 | Huawei Technologies Co., Ltd. | Routing information processing method and apparatus |
Also Published As
Publication number | Publication date |
---|---|
US20190166048A1 (en) | 2019-05-30 |
US10708185B2 (en) | 2020-07-07 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20200296039A1 (en) | Dynamic next-hop selection for routes in a network fabric | |
US9985867B2 (en) | Optimizing EVPN for data centers with redundant top-of-rack deployments | |
US10541905B2 (en) | Automatic optimal route reflector root address assignment to route reflector clients and fast failover in a network environment | |
US10333836B2 (en) | Convergence for EVPN multi-homed networks | |
US20200021523A1 (en) | Route Processing Method, Device, and System | |
US9858163B2 (en) | Dual adjacency between edge devices at a network site | |
US8948181B2 (en) | System and method for optimizing next-hop table space in a dual-homed network environment | |
US8953441B2 (en) | Re-routing network traffic after link failure | |
US9559962B2 (en) | Optimizing traffic flows via dynamic routing protocol modifications when using server virtualization with dynamic routing | |
US9742586B2 (en) | Intelligent host route distribution for low latency forwarding and ubiquitous virtual machine mobility in interconnected data centers | |
US9118604B2 (en) | Method and system for routing packets | |
US10771380B2 (en) | Fast control path and data path convergence in layer 2 overlay networks | |
US9178816B1 (en) | Control plane messaging in all-active multi-homed ethernet virtual private networks | |
US20160065503A1 (en) | Methods, systems, and computer readable media for virtual fabric routing | |
US10110465B2 (en) | Distributed HSRP gateway in VxLAN flood and learn environment with faster convergence | |
CN106572021B (en) | Method for realizing network virtualization superposition and network virtualization edge node | |
US20160226753A1 (en) | Scheme for performing one-pass tunnel forwarding function on two-layer network structure | |
US20220124019A1 (en) | Optimized Layer 3 VPN Control Plane using Segment Routing | |
US11362954B2 (en) | Tunneling inter-domain stateless internet protocol multicast packets | |
WO2023125239A1 (en) | Flood attack defense method and related device | |
US10142223B2 (en) | Symmetric intersubnet traffic load balancing in multihomed networks | |
US10530873B1 (en) | Techniques for optimizing EVPN-IRB for IPv6-enabled data centers with top-of-rack deployments | |
US10999183B2 (en) | Link state routing protocol adjacency state machine | |
CN108768845B (en) | Multi-homing host routing synchronization method and device | |
US20230412503A1 (en) | Determining unicast addresses of gateway network devices associated with an anycast address in vxlan-evpn dci environments |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: CISCO TECHNOLOGY, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SRINIVASAN, SATHISH;KAPADIA, SHYAM;KRATTIGER, LUKAS;AND OTHERS;SIGNING DATES FROM 20171109 TO 20171129;REEL/FRAME:052784/0383 |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: APPLICATION DISPATCHED FROM PREEXAM, NOT YET DOCKETED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |