CN115277550B

CN115277550B - Routing system, routing method and routing device of virtual network

Info

Publication number: CN115277550B
Application number: CN202210704835.XA
Authority: CN
Inventors: 李旅; 齐辰晨; 费腾; 白晓磊
Original assignee: Alibaba China Co Ltd
Current assignee: Alibaba China Co Ltd
Priority date: 2022-06-21
Filing date: 2022-06-21
Publication date: 2023-11-28
Anticipated expiration: 2042-06-21
Also published as: CN115277550A

Abstract

The embodiment of the specification provides a routing system, a routing method and a routing device of a virtual network, wherein the method comprises the following steps: receiving first-type routing information, wherein the first-type routing information comprises: a server interface address initially configured by a virtual forwarding node of a destination network segment; receiving second-type routing information, wherein the second-type routing information comprises: a server interface address initially configured by any virtual forwarding node and a virtual tunnel endpoint address of a switch to which the any virtual forwarding node is actually connected; comparing the server interface address initially configured by the virtual forwarding node in the first type of routing information with the server interface address initially configured by the virtual forwarding node in the second type of routing information; and if the two types of route information are consistent, generating a route entry, wherein the route entry comprises the destination network segment and the next hop of the destination network segment, and the next hop is the virtual tunnel endpoint address of the switch in the second type of route information.

Description

Routing system, routing method and routing device of virtual network

Technical Field

The embodiment of the specification relates to the technical field of computers, in particular to a routing system, a routing method and a routing device of a virtual network.

Background

Based on cloud computing developed from computing virtualization, there is also a demand for virtualization for networks. In the network virtualization scheme currently mainstream, a switch is used as a virtual tunnel endpoint to implement the network virtualization scheme. Since the virtual forwarding nodes are deployed in the form of virtual machines, there is a possibility of migration between physical servers connected under different switches. In order to ensure that traffic can be normally forwarded when a virtual forwarding node migrates under different switches, at present, the switches typically advertise routing information in a virtual network of a tenant. Thus, a plurality of switches announce the routes of the same virtual forwarding node to network equipment in the virtual network, so that a plurality of load shares are formed on the network equipment for the routes of the same virtual forwarding node, and the next hop points to the virtual tunnel endpoint addresses of the corresponding switches respectively.

However, only one virtual forwarding node can exist under one switch at the same time, so when the network equipment distributes the traffic sent to the virtual forwarding node to the switch without the virtual forwarding node below, the switch is required to forward the traffic to other switches to send the traffic to the virtual forwarding node, and detouring exists in the traffic forwarding process, so that the bandwidth occupation of the switch and the traffic delay are increased.

Disclosure of Invention

In view of this, the embodiments of the present disclosure provide a routing system, a routing method, a routing apparatus, a computing device, a computer-readable storage medium, and a computer program for a virtual network, so as to solve the technical drawbacks in the prior art.

According to a first aspect of embodiments of the present specification, there is provided a routing system of a virtual network, including: a plurality of switches and a first network device. The switch is configured to send a first type of routing information in a virtual network, the first type of routing information comprising: a server interface address initially configured by a virtual forwarding node of a destination network segment; the switch is further configured to send, in response to receiving a notification message, a second type of routing information in the virtual network, the notification message for causing the switch to perceive that any virtual forwarding node is on-line with a server to which the switch is connected, the second type of routing information comprising: and the server interface address initially configured by any virtual forwarding node and the virtual tunnel endpoint address of the switch to which the any virtual forwarding node is actually connected. The first network device is configured to receive the first type of routing information, receive the second type of routing information, compare a server interface address initially configured by a virtual forwarding node in the first type of routing information with a server interface address initially configured by a virtual forwarding node in the second type of routing information, and if the server interface addresses are consistent, generate a routing entry, where the routing entry includes the destination network segment and a next hop of the destination network segment, and the next hop is a virtual tunnel endpoint address of a switch in the second type of routing information.

Optionally, the virtual network is an ethernet virtual private network based on border gateway protocol. The first network device is gateway device in the virtual network, and the switches are respectively connected with the gateway device.

According to a second aspect of embodiments of the present disclosure, there is provided a routing method of a virtual network, applied to a first network device, including: receiving first-type routing information, wherein the first-type routing information comprises: a server interface address initially configured by a virtual forwarding node of a destination network segment; receiving second-type routing information, wherein the second-type routing information comprises: the server interface address initially configured by any virtual forwarding node and the virtual tunnel endpoint address of the switch to which any virtual forwarding node is actually connected; comparing the server interface address initially configured by the virtual forwarding node in the first type of routing information with the server interface address initially configured by the virtual forwarding node in the second type of routing information; and if the two types of route information are consistent, generating a route entry, wherein the route entry comprises the destination network segment and the next hop of the destination network segment, and the next hop is a virtual tunnel endpoint address of a switch in the second type of route information.

Optionally, the method further comprises: and writing the routing entry into a forwarding table under the condition that the next hop of the routing entry is determined to be a valid outgoing interface, so as to forward traffic based on the forwarding table.

Optionally, the comparing the server interface address initially configured by the virtual forwarding node in the first type of routing information with the server interface address initially configured by the virtual forwarding node in the second type of routing information includes: generating a first type of routing item according to the first type of routing information, wherein in the first type of routing item, a destination network segment is a destination network segment in the first type of routing information, and the next hop is a virtual tunnel endpoint address of a switch for transmitting the first type of routing information; generating a second type of routing item according to the second type of routing information, wherein in the second type of routing item, a destination network segment is a server interface address initially configured by any virtual forwarding node, and the next hop is a virtual tunnel endpoint address of a switch actually connected with the any virtual forwarding node; judging whether the first type of routing information carries a server interface address initially configured by a virtual forwarding node of the destination network segment; if yes, comparing the server interface address initially configured by the virtual forwarding node of the destination network segment with the server interface address initially configured by any virtual forwarding node in the second type of routing entry.

Optionally, the comparing the server interface address initially configured by the virtual forwarding node of the destination network segment with the server interface address initially configured by the any virtual forwarding node in the second class of routing entries includes: setting a server interface address initially configured by a virtual forwarding node of the destination network segment as a next hop in the first type of routing entry; comparing the next hop in the first type of routing entry with the server interface address initially configured by any virtual forwarding node in the second type of routing entry; and if so, generating a routing entry, including: and if the virtual tunnel endpoint addresses of the switches actually connected by any virtual forwarding node are consistent, setting the virtual tunnel endpoint address of the switch actually connected by any virtual forwarding node as the next hop in the first type of routing item, and obtaining the routing item.

Optionally, the virtual network is an ethernet virtual private network based on border gateway protocol; the receiving the first type of routing information includes: and receiving RT5 type route containing the first type route information. The judging whether the first type of routing information carries the server interface address initially configured by the virtual forwarding node of the destination network segment comprises the following steps: and judging whether the RT5 type route has a server interface address which is initially configured by a virtual forwarding node of the destination network segment and carried by the community attribute of the border gateway protocol.

According to a third aspect of embodiments of the present disclosure, there is provided a routing method of a virtual network, applied to a switch, including: transmitting a first type of routing information in a virtual network, the first type of routing information comprising: a server interface address initially configured by a virtual forwarding node of a destination network segment; in response to receiving a notification message, sending second type routing information in the virtual network, where the notification message is used to make a switch perceive that any virtual forwarding node is on-line at a server connected to the switch, and the second type routing information includes: the server interface address initially configured by any virtual forwarding node and the virtual tunnel endpoint address of the switch to which any virtual forwarding node is actually connected; the first type of routing information and the second type of routing information are used for enabling first network equipment in the virtual network to receive the first type of routing information, receiving the second type of routing information, comparing a server interface address initially configured by a virtual forwarding node in the first type of routing information with a server interface address initially configured by the virtual forwarding node in the second type of routing information, and if the server interface address is consistent with the server interface address initially configured by the virtual forwarding node in the second type of routing information, generating a routing entry, wherein the routing entry comprises the destination network segment and a next hop of the destination network segment, and the next hop is a virtual tunnel endpoint address of a switch in the second type of routing information.

Optionally, the virtual network is an ethernet virtual private network based on border gateway protocol. The sending the first type of routing information in the virtual network comprises the following steps: and sending the RT5 type route containing the first type of route information in the virtual network, wherein the server interface address initially configured by the virtual forwarding node is carried in the RT5 type route through the community attribute of the border gateway protocol. The sending the second type of routing information in the virtual network comprises the following steps: and sending an RT2 type route containing the second type route information in the virtual network, wherein a destination network segment in the RT2 type route is set as a server interface address initially configured by any virtual forwarding node, and the next hop is set as a virtual tunnel endpoint address of a switch actually connected by any virtual forwarding node.

Optionally, before sending the RT5 type route including the first type route information in the virtual network, the method further includes: configuring a static route, wherein the static route comprises the following steps: the method comprises the steps of a destination network segment and a next hop of the destination network segment, wherein the next hop is a server interface address initially configured by a virtual forwarding node; and generating the RT5 type route based on the border gateway protocol according to the static route, wherein the next hop of the destination network segment in the RT5 type route is the virtual tunnel endpoint address of the switch, and the community attribute in the RT5 type route carries the server node address of the initial configuration of the virtual forwarding node.

According to a fourth aspect of embodiments of the present disclosure, there is provided a routing device of a virtual network, configured to a first network device, including: a first route receiving module configured to receive a first type of route information, the first type of route information comprising: the method comprises the steps of a destination network segment and a server interface address initially configured by a virtual forwarding node of the destination network segment. A second route receiving module configured to receive a second type of route information, the second type of route information comprising: and the server interface address initially configured by any virtual forwarding node and the virtual tunnel endpoint address of the switch to which the any virtual forwarding node is actually connected. And the initial address searching module is configured to compare the server interface address initially configured by the virtual forwarding node in the first type of routing information with the server interface address initially configured by the virtual forwarding node in the second type of routing information. And the route generation module is configured to generate a route entry if the initial address lookup module determines that the initial address lookup module is consistent, wherein the route entry comprises the destination network segment and a next hop of the destination network segment, and the next hop is a virtual tunnel endpoint address of the switch in the second type of route information.

According to a fifth aspect of embodiments of the present disclosure, there is provided a routing device of a virtual network, configured to a switch, including: a first routing module configured to send a first type of routing information in a virtual network, the first type of routing information comprising: the method comprises the steps of a destination network segment and a server interface address initially configured by a virtual forwarding node of the destination network segment. A second route sending module configured to send, in response to receiving a notification message, second type routing information in the virtual network, the notification message being used to cause a switch to perceive that any virtual forwarding node is on-line with a server to which the switch is connected, the second type routing information including: and the server interface address initially configured by any virtual forwarding node and the virtual tunnel endpoint address of the switch to which the any virtual forwarding node is actually connected. The first type of routing information and the second type of routing information are used for enabling first network equipment in the virtual network to receive the first type of routing information, receiving the second type of routing information, comparing a server interface address initially configured by a virtual forwarding node in the first type of routing information with a server interface address initially configured by the virtual forwarding node in the second type of routing information, and if the server interface address is consistent with the server interface address initially configured by the virtual forwarding node in the second type of routing information, generating a routing entry, wherein the routing entry comprises the destination network segment and a next hop of the destination network segment, and the next hop is a virtual tunnel endpoint address of a switch in the second type of routing information.

According to a sixth aspect of embodiments of the present specification, there is provided a computing device comprising: a memory and a processor; the memory is configured to store computer-executable instructions that, when executed by the processor, perform the steps of the virtual network routing method of any embodiment of the present specification.

According to a seventh aspect of embodiments of the present specification, there is provided a computer readable storage medium storing computer executable instructions which, when executed by a processor, implement the steps of the method for routing a virtual network according to any embodiment of the present specification.

According to an eighth aspect of embodiments of the present specification, there is provided a computer program, wherein the computer program, when executed in a computer, causes the computer to perform the steps of the above-described routing method of a virtual network.

The first network device can compare the server interface address initially configured by the virtual forwarding node in the first type of routing information with the server interface address initially configured by the virtual forwarding node in the second type of routing information after receiving the first routing information and the second routing information, if the server interface address initially configured by the virtual forwarding node in the first type of routing information is consistent, a routing entry is generated, the next hop of the network segment in the routing entry is the server on which the switch is connected, the second type of routing information comprising the server interface address initially configured by the virtual forwarding node and the virtual tunnel endpoint address of the switch actually connected by the virtual forwarding node is transmitted, and therefore the time delay flow of the virtual forwarding node in the first type of routing information can be reduced by the virtual tunnel endpoint address of the switch actually connected by the virtual forwarding node.

Drawings

FIG. 1 is a schematic diagram of a virtual network provided in one embodiment of the present description;

fig. 2 is a schematic application scenario diagram of a routing system of a virtual network according to an embodiment of the present disclosure;

fig. 3 is a schematic structural diagram of a routing system of a virtual network according to an embodiment of the present disclosure;

fig. 4 is a flowchart of a routing method applied to a virtual network of a switch according to an embodiment of the present disclosure;

FIG. 5 is a process flow diagram of a method for routing a virtual network provided in one embodiment of the present disclosure;

fig. 6 is a flowchart of a process of a method for routing a virtual network according to another embodiment of the present disclosure;

fig. 7 is a flowchart of a routing method applied to a virtual network of a first network device according to an embodiment of the present disclosure;

fig. 8 is a process flow diagram of a method for routing a virtual network according to yet another embodiment of the present disclosure;

fig. 9 is a schematic structural diagram of a routing device configured in a virtual network of a switch according to an embodiment of the present disclosure;

fig. 10 is a schematic structural diagram of a routing device configured to a virtual network of a first network device according to an embodiment of the present disclosure;

FIG. 11 is a block diagram of a computing device provided in one embodiment of the present description.

Detailed Description

In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present description. This description may be embodied in many other forms than described herein and similarly generalized by those skilled in the art to whom this disclosure pertains without departing from the spirit of the disclosure and, therefore, this disclosure is not limited by the specific implementations disclosed below.

The terminology used in the one or more embodiments of the specification is for the purpose of describing particular embodiments only and is not intended to be limiting of the one or more embodiments of the specification. As used in this specification, one or more embodiments and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used in one or more embodiments of the present specification refers to and encompasses any or all possible combinations of one or more of the associated listed items.

It should be understood that, although the terms first, second, etc. may be used in one or more embodiments of this specification to describe various information, these information should not be limited by these terms. These terms are only used to distinguish one type of information from another. For example, a first may also be referred to as a second, and similarly, a second may also be referred to as a first, without departing from the scope of one or more embodiments of the present description. The word "if" as used herein may be interpreted as "at … …" or "at … …" or "responsive to a determination", depending on the context.

First, terms related to one or more embodiments of the present specification will be explained.

ARP (Address Resolve Protocol), which represents an address resolution protocol.

NDP (Neighbor Discover Protocol), which represents a neighbor discovery protocol, is part of the TCP/IP protocol stack. The neighbor discovery protocol is at the data link layer and is responsible for discovering other nodes and corresponding IP addresses on the link and determining available routes and maintaining information reachability about available paths and other active nodes.

TOR (Top Of Rack), a roof-top exchange.

BGP (Border Gateway Protocol), which represents the border gateway protocol, is a core de-centralized autonomous routing protocol on the internet.

EVPN (Ethenet VPN), which represents an ethernet virtual private network, in which L2 ethernet traffic is forwarded, generally refers to BGP EVPN protocol as a network virtualization technology forwarding control plane.

VXLAN (Virtual eXtensible Local Area Network), which represents a virtual extensible local area network. VXLAN features encapsulating the L2 ethernet frame into a UDP message (i.e., L2 over L4) and transmitting in the L3 network. Wherein L2 represents two layers, L3 represents three layers, and L4 represents four layers.

VTEP (Virutal Tunnel End Point), which represents virtual tunnel endpoints.

VRF (Virtual Routing and Forwarding), which represents a virtual route forwarding instance.

IP refers to a unique address specified by each device on the internet. With this unique IP address, it is ensured that the device that wants to communicate can be efficiently found.

Based on cloud computing developed from computing virtualization, there is also a demand for virtualization for networks. At present, in some network virtualization schemes, a hardware switch is used as a VTEP point, network virtualization is realized based on BGP EVPN and VXLAN, and the network virtualization scheme has the advantages of no invasion to a server, excellent forwarding performance, clear operation and maintenance interfaces and the like, and is widely deployed and applied in the industry.

In a network virtualization scenario, there is often a tenant of forwarding nodes deployed on a physical server in a virtual machine manner. Such virtual forwarding nodes may be represented as: virtual firewalls, virtual load balancing, virtual routers, etc. The virtual forwarding node is not generally a forwarding destination of the traffic, but is a transit node of the traffic. Thus, a switch (e.g., TOR) connected to a virtual forwarding node typically needs to configure a route in the VRF corresponding to the tenant. In order to reduce the coupling between the virtual forwarding node and the uplink switch, a static route can be selected, and a dynamic route can be selected based on the actual application scene. Because the routes are directed to networks connected behind the virtual forwarding nodes, the switch needs to advertise the routes in the virtual networks of the tenants to accurately forward traffic destined for these networks to the virtual forwarding nodes, which in turn forward traffic to the corresponding networks. Virtual networks, also known as overlay networks, may be understood as building logical networks on top of physical networks.

In the following, taking the virtual network shown in fig. 1 as an example, a process of advertising a route and forwarding traffic by a switch in the virtual network currently implemented based on BGP EVPN is schematically described. As shown in fig. 1, the virtual switching node vruter is deployed on a server 1 connected to a switch TOR1, an interface IP of the server 1 is 192.168.1.100/32/24, a distributed gateway IP on the corresponding switch TOR1 is 192.168.1.1, and a destination network segment of the network behind the virtual forwarding node vruter is 172.18.1.0/24. In order to enable traffic to be forwarded to the VRF behind the vrrouter, static routing may be configured in the VRF corresponding to the tenant on switch TOR 1. In the static route configured, the destination network segment points to 172.18.1.0/24, and the next hop is the server interface address 192.168.1.100/32 originally configured by the virtual forwarding node vruter. On the switch TOR1, the static route is distributed to a BGP EVPN protocol stack in a redistribution mode, the BGP EVPN is advertised to a network device at a far end in a RT5 type route, and when the route is advertised, the next hop is modified into a virtual tunnel endpoint address VTEP IP of the switch TOR1 according to the BGP EVPN protocol. When the virtual forwarding node vruter is first on-line to the switch TOR1, after the switch TOR1 receives an ARP message (such as an ARP request or GARP) sent by the virtual forwarding node vruter, the switch TOR1 forms a corresponding ARP entry, generates a corresponding RT2 type route in a BGP EVPN protocol stack according to the ARP entry, and notifies other BGP EVPN neighbors. Thus, both the network device GW and the switch TOR2 shown in fig. 1 see an RT2 type route pointing to the server interface address 192.168.1.100/32 of the initial configuration of the virtual forwarding node vruter. Because the virtual forwarding node vruter may be migrated to the server 2, in order to ensure that the traffic can be forwarded normally after the virtual forwarding node vruter migrates to the server 2, static routes pointing to the server interface address initially configured by the virtual forwarding node vruter may be preconfigured in the VRF corresponding to the tenant on the switch TOR2, and also redistributed to the BGP EVPN protocol stack. At this time, two routes directed to 172.18.1.0/24 are simultaneously learned on the GW, and the next hop is directed to the VTEP IP of each of TOR1 and TOR2, respectively, and load sharing is formed on the GW. When the GW receives traffic destined for the 172.18.1.0/24 segment, it may be possible to share the traffic to TOR1, or to share the traffic to TOR2. When shared to TOR1, traffic flows into the vruter through a route identified as "flow 1" in fig. 1. When shared to TOR2, traffic flows into the vruter through a route identified as "flow 2" in fig. 1. As seen from the "flow direction 2", since the virtual forwarding node vruter is actually connected under the switch TOR1, when the switch TOR2 receives the traffic sent by the GW, the switch TOR2 needs to find that the local route finds that the next hop of 172.18.1.0/24 is 192.168.1.100/32, and that the next hop of 192.168.1.100/32 is learned by the RT2 route, the virtual tunnel endpoint address VTEP IP pointing to the switch TOR 1: 10.0.0.1. therefore, the switch TOR2 needs to forward the traffic to TOR1 first, and TOR1 can forward the traffic to the virtual forwarding node vruter finally, and there is a bypass in the traffic forwarding process.

As can be seen from the above example process, since the virtual forwarding node is deployed in the form of a virtual machine, there is a possibility of migration between physical servers connected under different switches. Because the virtual forwarding node has the possibility of migration, the switch cannot sense the migration event of the virtual forwarding node, in order to ensure that traffic can be normally forwarded when the virtual forwarding node migrates under different switches, corresponding routing information is configured in VRFs corresponding to the switch tenant, and the switch advertises the routing information in the virtual network of the tenant. When the switch advertises the routing information of the virtual network to the outside, the routing information is advertised by default to the network device at the far end as RT5 type route. The next-hop information carried in the RT5 type route is a VTEP IP address (i.e., virtual tunnel endpoint address) configured on the switch. Thus, when the switches announce the route information of the same virtual forwarding node to the far end, a plurality of load shares are formed on the network equipment for the route entry of the same virtual forwarding node, and the next hop points to the corresponding switch VTEP IP address respectively. However, since the virtual forwarding node only exists under one switch at the same time, when the network device at the far end shares the traffic sent to the virtual forwarding node to the switch without the virtual forwarding node below, after the switch receives the traffic, the switch at which the interface address of the virtual forwarding node of the next hop is located needs to be searched according to the RT2 type route, and after the traffic is sent to the corresponding switch, the traffic can be finally sent to the virtual forwarding node. The large probability of the flow in the whole process can bypass, so that the bandwidth occupation of the switch is increased, and meanwhile, the flow time delay is also increased.

In some technical schemes, a virtual network implemented based on BGP EVPN can directly establish BGP route neighbors in an overlay network by using a virtual forwarding node vrRouter and a network device GW, so that the virtual forwarding node vrRouter and the network device GW directly interact with each other to achieve the goal that a GW node learns the route original next hop, and then obtain a virtual tunnel endpoint address of a switch where the vrRouter is actually located by performing route iteration by using the network device GW. However, this may result in increased coupling between the virtual forwarding node and the network device, and rely on the capability of the virtual forwarding node, so that the virtual forwarding node needs to support the BGP routing protocol, so that interaction between the virtual forwarding node and the network device is enabled through the BGP protocol, and requirements are set for BGP protocol interoperability between the virtual forwarding node and the network device.

In view of this, in the present specification, there are provided a virtual network routing system, a virtual network routing method, a virtual network routing apparatus, a computing device, and a computer-readable storage medium, which are described in detail in the following embodiments one by one.

Referring to fig. 2, fig. 2 shows a schematic application scenario of a routing system of a virtual network according to an embodiment of the present disclosure. The virtual network shown in fig. 2 is an ethernet virtual private network based on border gateway protocol. The routing system of the virtual network may include: switch TOR1 and switch TOR2, and a first network device GW. In this application scenario, the various switches in the virtual network, such as switches TOR1, TOR2, and the first network device GW, avoid traffic detours by the following processing steps. Specifically:

In step 202, the switch sends a first type of routing information in the virtual network, the first type of routing information including: the method comprises the steps of a destination network segment and a server interface address initially configured by a virtual forwarding node of the destination network segment.

In the application scenario shown in fig. 2, the first type of routing information is embodied as routing information carried in EVPN RT5 type routing. For example, the switches TOR1 and TOR2 as shown in fig. 2 advertise routing information for the overlay network. The routing information is sent in an EVPN RT5 type route, and the EVPN RT5 type route example shown in fig. 2 includes: destination segment "route_prefix:172.18.1.0/24", NEXT HOP" NEXT HOP:10.0.0.1 "and the original next hop (denoted as origin-next-hop in fig. 2) in the static route is carried in the form of BGP extended community attribute (denoted as ext-community in fig. 2) to cause any network device in the virtual network to obtain the original next hop information of the static route. The original next hop in the static route refers to the server interface address initially configured by the virtual forwarding node or the upper connection port IP understood as the virtual forwarding node.

In step 204, the switch sends, in response to receiving the notification message, a second type of routing information in the virtual network, the notification message being used to cause the switch to perceive that any virtual forwarding node is on-line with a server to which the switch is connected, the second type of routing information including: and the server interface address initially configured by any virtual forwarding node and the virtual tunnel endpoint address of the switch to which the any virtual forwarding node is actually connected.

The notification message may be referred to as an address resolution protocol notification message, and is a message that triggers a switch to perceive that any virtual forwarding node is on-line at a server connected to the switch. For example, in a virtual network based on border gateway protocol, the notification message appears as an ARP notification message, which can trigger a switch to perceive an ARP-like request, ARP protocol message, of a MAC address location change.

Wherein the second type of routing information is embodied as routing information carried in EVPN RT2 type routing. For example, switch TOR2 as shown in fig. 2 advertises the original next-hop information for the static route in an EVPN RT2 type route in response to receiving a notification message that appears as an ARP message. In the EVPN RT2 type route, a destination network segment is a 32-bit server interface address initially configured by a virtual forwarding node vRouter, and the next hop is a virtual tunnel endpoint address of a switch TOR1 actually connected by the virtual forwarding node vRouter.

In step 206, the first network device receives the first type of routing information, receives the second type of routing information, compares the server interface address initially configured by the virtual forwarding node in the first type of routing information with the server interface address initially configured by the virtual forwarding node in the second type of routing information, and if the server interface addresses are consistent, generates a routing entry, where the routing entry includes the destination network segment and a next hop of the destination network segment, and the next hop is a virtual tunnel endpoint address of the switch in the second type of routing information.

For example, as shown in fig. 2, the first network device GW determines, in the EVPN RT5 type route, original next hop information in the extended community attribute, and searches for a virtual tunnel endpoint address of an actually connected switch by using the original next hop to perform RT2 routing, and then writes the virtual tunnel endpoint address of the actually connected switch into a local route entry corresponding to the EVPN RT5 type route, so that a next hop in the route entry corresponding to the RT5 type route on the GW is a virtual tunnel endpoint address of a real switch connected to the virtual forwarding node vruter.

Through the processing of the steps, the GW obtains the virtual tunnel endpoint address of the switch actually connected by the virtual forwarding node vRouter, so that the traffic sent to the network behind the virtual forwarding node vRouter can be correctly sent to the switch actually connected by the virtual forwarding node vRouter, thereby avoiding traffic bypass. In the case that the virtual forwarding node vruter migrates, since the switch to which the virtual forwarding node vruter is connected after migrating actively sends out an ARP message (denoted as ARP packets in fig. 2), the upstream switch generates a new EVPN RT2 type route after receiving the ARP packet, so as to update the virtual tunnel endpoint address of the switch to which the virtual forwarding node vruter is newly connected.

In fig. 2, protocol packet paths and traffic forwarding paths are drawn by different types of dashed lines, respectively, to illustrate the differences.

Referring to fig. 3, fig. 3 is a schematic structural diagram of a routing system of a virtual network according to an embodiment of the present disclosure. As shown in fig. 3, the routing system of the virtual network may include: a plurality of switches 302 and a first network device 304. In fig. 3, a plurality of switches are shown as switch a and switch B, and the number of switches in practical application can be set as required. The first network device 304 may be implemented as any network device such as a gateway, a switch, etc. in practical applications.

The switch 302 may be configured to send a first type of routing information in a virtual network, the first type of routing information comprising: a server interface address initially configured by a virtual forwarding node of a destination network segment; the switch 302 is further configured to send, in response to receiving a notification message, a second type of routing information in the virtual network, the notification message for causing the switch to perceive that any virtual forwarding node is on-line with a server to which the switch is connected, the second type of routing information comprising: and the server interface address initially configured by any virtual forwarding node and the virtual tunnel endpoint address of the switch to which the any virtual forwarding node is actually connected.

The first network device 304 may be configured to receive the first type of routing information, receive the second type of routing information, compare a server interface address initially configured by a virtual forwarding node in the first type of routing information with a server interface address initially configured by a virtual forwarding node in the second type of routing information, and if the server interface addresses are consistent, generate a routing entry, where the routing entry includes the destination network segment and a next hop of the destination network segment, and the next hop is a virtual tunnel endpoint address of a switch in the second type of routing information.

Because the first type of route information sent by the switch in the virtual network comprises a destination network segment and a server interface address initially configured by a virtual forwarding node in the destination network segment, and the switch in the virtual network sends second type of route information comprising the server interface address initially configured by any virtual forwarding node and a virtual tunnel endpoint address of the switch actually connected by any virtual forwarding node under the condition that the switch is perceived to be on line, the first type of route information is sent, after the first type of route information is received and the second type of route information is received, the server interface address initially configured by the virtual forwarding node in the first type of route information is compared with the server interface address initially configured by the virtual forwarding node in the second type of route information, if the server interface address is consistent with the server interface address, a route entry is generated, and the next hop of the destination network segment in the route entry is the virtual tunnel endpoint address of the switch in the second type of route information, namely the next hop of the network segment in the route entry is the virtual tunnel endpoint address of the switch, so that the time delay of the virtual forwarding node in the route entry can be reduced, and the traffic can be prevented from occupying the virtual forwarding node in the network to the actual network node based on the actual traffic.

It should be noted that, the virtual network described in the embodiments of the present disclosure may be implemented based on any network virtualization technology. For example, in one or more embodiments of the present description, the virtual network is a border gateway protocol based ethernet virtual private network. The first network device is gateway device in the virtual network, and the switches are respectively connected with the gateway device. In this embodiment, the specific implementation manner of the switch sending the routing information and the gateway device writing the virtual tunnel endpoint address of the switch actually connected to the virtual forwarding node into the routing entry may refer to the description in the application scenario embodiment shown in fig. 2, which is not described in detail herein.

Referring to fig. 4, fig. 4 shows a flowchart of a method for routing a virtual network according to one embodiment of the present disclosure. The routing method of the virtual network provided by the embodiment is applied to the switch. As shown in fig. 4, specifically, the method may include:

step 402, sending first type routing information in a virtual network, where the first type routing information includes: the method comprises the steps of a destination network segment and a server interface address initially configured by a virtual forwarding node of the destination network segment.

The first type of routing information is information indicating the flow direction of a data packet sent to a destination network segment. The routes configured by the switch can be static routes or dynamic routes, and the switch advertises route information into the virtual network based on the routes configured by the switch. When a switch advertises a route in a virtual network, any network device in the virtual network may receive the switch advertised route. In the routing advertised by the switch, according to the actual application scene, a destination network segment and the next hop of the destination network segment can be included. The next hop of the destination network segment may be the server interface address initially configured for the virtual forwarding node directly, or may be the virtual tunnel endpoint address of the switch that sends the route. In the case where the next hop of the destination network segment in the advertised route is the virtual tunnel endpoint address of the switch that sent the route, the server interface address initially configured by the virtual forwarding node may be carried in other attributes of the route.

Taking the virtual network as a virtual private network based on a border gateway protocol as an example, a switch can send an RT5 type route containing the first type route information in the virtual network, wherein a server interface address initially configured by the virtual forwarding node is carried in the RT5 type route through a community attribute of the border gateway protocol.

In a virtual network implemented based on BGP EVPN, when a switch advertises a static route in the virtual network, the static route is advertised to a network device at a remote end as an RT5 type route. This RT5 type route is also referred to as IP prefix route. The next hop carried in the RT5 type route is the virtual tunnel endpoint address configured by the switch. In addition, in the EVPN RT5 type route, the original next hop of the static route, that is, the server interface address initially configured by the virtual forwarding node, is also carried in the form of BGP extended community attribute, so that the network device at the receiving end obtains the original next hop information of the route.

Step 404, in response to receiving the notification message, sending second type routing information in the virtual network, where the notification message is used to make the switch perceive that any virtual forwarding node is on line at a server connected to the switch, and the second type routing information includes: and the server interface address initially configured by any virtual forwarding node and the virtual tunnel endpoint address of the switch to which the any virtual forwarding node is actually connected.

The second type of routing information is information indicating a server interface address initially configured by any virtual forwarding node and a virtual tunnel endpoint address of a switch to which the any virtual forwarding node is actually connected.

Taking the virtual network as a virtual network based on a border gateway protocol as an example, an RT2 type route containing the second type route information can be sent in the virtual network, wherein a destination network segment in the RT2 type route is set as a server interface address initially configured by any virtual forwarding node, and the next hop is set as a virtual tunnel endpoint address of a switch actually connected by the any virtual forwarding node.

The first type of routing information and the second type of routing information are used for enabling first network equipment in the virtual network to receive the first type of routing information, receiving the second type of routing information, comparing a server interface address initially configured by a virtual forwarding node in the first type of routing information with a server interface address initially configured by the virtual forwarding node in the second type of routing information, and if the server interface address is consistent with the server interface address initially configured by the virtual forwarding node in the second type of routing information, generating a routing entry, wherein the routing entry comprises the destination network segment and a next hop of the destination network segment, and the next hop is a virtual tunnel endpoint address of a switch in the second type of routing information.

In the method, a switch in a virtual network sends first class route information which contains a destination network segment and a server interface address initially configured by a virtual forwarding node in the destination network segment in the virtual network, and when the switch in the virtual network perceives that any virtual forwarding node is on line with a server connected with the switch, a second class route information which contains the server interface address initially configured by any virtual forwarding node and a virtual tunnel endpoint address of a switch actually connected with any virtual forwarding node is sent, so that a first network device can compare the server interface address initially configured by the virtual forwarding node in the first class route information with the server interface address initially configured by the virtual forwarding node in the second class route information after receiving the first route information and the second route information, if the server interface address is consistent with the server interface address, a route entry is generated, and a next hop of the destination network segment in the route entry is the virtual tunnel endpoint address of the switch in the second route information, namely the next hop of the destination network segment is the virtual tunnel endpoint address of the switch in the route entry, and the time delay of the virtual forwarding node in the route entry can be reduced to the virtual forwarding node in the network node, and the network traffic can be prevented from occupying the actual traffic by the virtual forwarding node in the network device.

In one or more embodiments of the present disclosure, before sending the RT5 type route including the first type routing information in the virtual network implemented based on BGP EVPN, the method may further include: configuring a static route, wherein the static route comprises the following steps: the method comprises the steps of a destination network segment and a next hop of the destination network segment, wherein the next hop is a server interface address initially configured by a virtual forwarding node; and generating the RT5 type route based on the border gateway protocol according to the static route, wherein the next hop of the destination network segment in the RT5 type route is the virtual tunnel endpoint address of the switch, and the community attribute in the RT5 type route carries the server node address of the initial configuration of the virtual forwarding node. In this embodiment, by configuring the static route on the switch, the switch advertises an RT5 type route in the virtual network based on the static route that carries the server interface address initially configured by the virtual forwarding node, obviating the need for the virtual forwarding node to support BGP routing protocols. Under the condition that the switch complies with the border gateway protocol, the first network equipment can directly forward the traffic to the switch actually connected with the virtual forwarding node, so that the traffic is prevented from bypassing in the network.

Next, with reference to fig. 5, a detailed description will be given of a specific embodiment of the switch carrying the server interface address initially configured by the virtual forwarding node through the RT5 type route extension community attribute. Fig. 5 is a flowchart of a process of a method for routing a virtual network according to one embodiment of the present disclosure. As shown in fig. 5, specifically, the method may include:

in step 502, static routes pointing to the same destination network segment are respectively configured on each switch of the virtual network, and reissued to BGP EVPN address families.

For example, in connection with the application scenario shown in fig. 2, switches TOR1 and TOR2 are configured with static routes directed to destination network segments 172.18.1.0/24, respectively, with a next hop of 192.168.1.100/32. 192.168.1.100/32 is the server interface address initially configured by the virtual forwarding node of the destination network segment.

In step 504, each switch generates a corresponding BGP EVPN RT5 route, and the next hop fills in the VTEP IP of itself.

For example, in connection with the application scenario shown in fig. 2, switches TOR1 and TOR2 respectively generate corresponding BGP EVPN RT5 routes. In BGP EVPN RT5 routing, the destination network segment is the next hop 172.18.1.0/24, and the next hop is the own VTEP IP.

In step 506, each switch checks whether the function of carrying the server node address initially configured by the virtual forwarding node by the community attribute in the BGP EVPN RT5 route of itself is started.

If not, step 510 is entered directly.

Step 508, if the switch is started, the switch attaches an extended community attribute in the generated BGP EVPN RT5 type route, where the attribute value is a server interface address initially configured by the virtual forwarding node.

For example, in connection with the application scenario shown in fig. 2, in the generated BGP EVPN RT5 type route, the switches TOR1 and TOR2 attach an extended community attribute, where the attribute value is 192.168.1.100/32.

In step 510, each switch advertises the BGP EVPN RT5 type route generated by each switch in the virtual network.

For example, in connection with the application scenario shown in fig. 2, switches TOR1 and TOR2 advertise BGP EVPN RT5 type routes to the GW.

Next, with reference to fig. 6, a detailed description will be given of a specific implementation manner in which the switch advertises the host route through the RT2 type route after the virtual forwarding node is on line. Fig. 6 is a flowchart of a process of a virtual network routing method according to another embodiment of the present disclosure. As shown in fig. 6, specifically, the method may include:

Step 602, after the initialization of the virtual forwarding node instance is completed, an ARP request/GARP notification ARP-like message is sent to the up-connected switch.

For example, in connection with the application scenario shown in fig. 2, after the initialization of the virtual forwarding node vruter instance is completed, an ARP request/GARP notification ARP-like message is sent.

Step 604, after receiving the ARP/GARP message, the switch generates a corresponding ARP entry locally, and generates a corresponding BGP EVPN RT2 type route at the same time, where the next hop in the BGP EVPN RT2 type route is the VTEP IP of the switch itself.

For example, in connection with the application scenario shown in fig. 2, after receiving the ARP/GARP message, the vrRouter upper link TOR1 switch locally generates a corresponding ARP entry, and simultaneously generates a corresponding BGP EVPN RT2 route, where the next hop is the VTEP IP of itself.

The switch advertises the BGP EVPN RT2 type route to other network devices in the virtual network, step 606.

After receiving the BGP EVPN RT2 type route advertised by the switch, other network equipment locally generates a second type route item, wherein in the second type route item, a destination network segment is a server interface address initially configured for a virtual forwarding node, and the next hop points to the VTEP IP of the switch for transmitting the BGP EVPN RT2 type route.

For example, in connection with the application scenario shown in fig. 2, after receiving the BGP EVPN RT2 route advertised by the TOR1 switch, the GW locally generates a route to the server interface address initially configured by the vruter, and the next hop points to the TOR1 switch VTEP IP.

Referring to fig. 7, fig. 7 shows a flowchart of a method for routing a virtual network according to one embodiment of the present disclosure. The virtual network routing method provided by the embodiment is applied to the first network device. As shown in fig. 7, specifically, the method may include:

step 702, receiving first type routing information, where the first type routing information includes: the method comprises the steps of a destination network segment and a server interface address initially configured by a virtual forwarding node of the destination network segment.

Step 704, receiving second-type routing information, where the second-type routing information includes: and the server interface address initially configured by any virtual forwarding node and the virtual tunnel endpoint address of the switch to which the any virtual forwarding node is actually connected.

Step 706, comparing the server interface address initially configured by the virtual forwarding node in the first type of routing information with the server interface address initially configured by the virtual forwarding node in the second type of routing information.

It should be noted that the comparison may be implemented in various ways, and the examples in this specification are not limited thereto. For example, the server interface address initially configured by the virtual forwarding node may be obtained directly from the first type of routing information and the second type of routing information and compared. For another example, the gateway protocol of the virtual network may be used to automatically generate the corresponding routing entries, and then obtain the server interface address initially configured by the virtual forwarding node from the routing entries and compare the server interface addresses.

And 708, if so, generating a routing entry, wherein the routing entry comprises the destination network segment and a next hop of the destination network segment, and the next hop is a virtual tunnel endpoint address of the switch in the second type of routing information.

Wherein the generating a routing entry may include: an updated route entry generated based on updating the route entry, or a newly generated route entry using the route information.

In addition, the first network device may further write the routing entry into a forwarding table in case that it is determined that a next hop of the routing entry is a valid egress interface, so as to forward traffic based on the forwarding table.

In the method, after receiving the first routing information and the second routing information, the first network device can compare the server interface address initially configured by the virtual forwarding node in the first routing information with the server interface address initially configured by the virtual forwarding node in the second routing information, if the server interface addresses are consistent with the server interface address initially configured by the virtual forwarding node in the second routing information, a routing entry is generated, and the next hop of the destination network segment in the routing entry is the virtual tunnel endpoint address of the switch in the second routing information, namely, the next hop of the destination network segment in the routing entry is the virtual tunnel endpoint address of the switch actually connected by the virtual forwarding node, so that the first network device can directly forward the traffic to the switch actually connected by the virtual forwarding node based on the routing entry, thereby avoiding the detour of the traffic in the network, and reducing the bandwidth occupation and the traffic delay of the switch.

In one or more embodiments of the present disclosure, based on a mechanism that a network device generally automatically generates a corresponding routing entry when receiving routing information, after the routing entry is automatically generated, a server interface address initially configured by a virtual forwarding node in two pieces of routing information is compared, so that the method provided in the embodiment of the present disclosure is easier to implement in an actual application scenario. Specifically, the comparing the server interface address initially configured by the virtual forwarding node in the first type of routing information with the server interface address initially configured by the virtual forwarding node in the second type of routing information includes:

Generating a first type of routing item according to the first type of routing information, wherein in the first type of routing item, a destination network segment is a destination network segment in the first type of routing information, and the next hop is a virtual tunnel endpoint address of a switch for transmitting the first type of routing information;

generating a second type of routing item according to the second type of routing information, wherein in the second type of routing item, a destination network segment is a server interface address initially configured by any virtual forwarding node, and the next hop is a virtual tunnel endpoint address of a switch actually connected with the any virtual forwarding node;

judging whether the first type of routing information carries a server interface address initially configured by a virtual forwarding node of the destination network segment;

if yes, comparing the server interface address initially configured by the virtual forwarding node of the destination network segment with the server interface address initially configured by any virtual forwarding node in the second type of routing entry.

Taking the virtual network as an ethernet virtual private network based on a border gateway protocol as an example, the comparing the server interface address initially configured by the virtual forwarding node of the destination network segment with the server interface address initially configured by any virtual forwarding node in the second type of routing entry includes: setting a server interface address initially configured by a virtual forwarding node of the destination network segment as a next hop in the first type of routing entry; and comparing the next hop in the first type of routing entry with the server interface address initially configured by any virtual forwarding node in the second type of routing entry. Correspondingly, if the route entries are consistent, generating the route entries comprises: and if the virtual tunnel endpoint addresses of the switches actually connected by any virtual forwarding node are consistent, setting the virtual tunnel endpoint address of the switch actually connected by any virtual forwarding node as the next hop in the first type of routing item, and obtaining the routing item.

In the above embodiment, by iterating the server interface address initially configured by the virtual forwarding node carried by the route to the next hop of the first type of route entry correspondingly generated, a direct connection between the first type of route entry and the server interface address initially configured by the virtual forwarding node is established, so that the first type of route entry and the server interface address initially configured by the virtual forwarding node in the second type of route entry are compared, and under the condition of consistent determination, the virtual tunnel endpoint address of the switch actually connected by the virtual forwarding node can be substituted into the next hop in the first type of route entry more directly and rapidly.

Taking the virtual network as an ethernet virtual private network based on a border gateway protocol as an example, the receiving the first type of routing information includes: and receiving RT5 type route containing the first type route information. The judging whether the first type of routing information carries the server interface address initially configured by the virtual forwarding node of the destination network segment comprises the following steps: and judging whether the RT5 type route has a server interface address which is initially configured by a virtual forwarding node of the destination network segment and carried by the community attribute of the border gateway protocol.

Next, a detailed description will be given of a specific embodiment of the first network device by iteratively searching for the virtual tunnel endpoint address of the switch to which the virtual forwarding node is actually connected, with reference to fig. 8. Fig. 8 is a flowchart illustrating a process of a virtual network routing method according to still another embodiment of the present disclosure. As shown in fig. 8, specifically, the method may include:

in step 802, the first network device receives BGP EVPN RT5 routes advertised by the switch, and correspondingly generates a first type of route entry.

For example, in connection with the application scenario shown in fig. 2, the GW receives BGP EVPN RT5 type routes advertised by TOR1 and TOR 2. The community attribute in BGP EVPN RT5 type routes carries the server node address initially configured by the virtual forwarding node. For example, the EVPN RT5 routing example received by GW from TOR1 is as follows:

{ROUTE_PREFIX:172.18.1.0/24

NEXT_HOP:10.0.0.1

ext-community{origin-next-hop:192.168.1.100}

}

where route_prefix represents the destination network segment and 172.18.1.0/24 is the value of the destination network segment in the scenario shown in fig. 2. Next_hop represents the NEXT HOP, 10.0.0.1 is the virtual tunnel endpoint address of switch TOR1, ext-community represents the community attribute, origin-NEXT-HOP represents the original NEXT HOP, i.e., the server interface address initially configured by the virtual forwarding node, and 192.168.1.100 is the value of the server interface address initially configured by the virtual forwarding node.

In step 804, the first network device receives BGP EVPN RT2 type route advertised in the virtual network by the switch perceiving that any virtual forwarding node is on-line at a server connected to the switch, and correspondingly generates a second type route entry.

For example, in connection with the application scenario shown in fig. 2, the GW receives BGP EVPN RT2 type routes advertised by TOR1, and correspondingly generates second type route entries. The contents of the first type of routing entry and the second type of routing entry are as follows, including:

route entry 1:172.18.1.0/24, next-hop 10.0.0.1,type EVPN-RT5, oif vxlan1;

route entry 2:172.18.1.0/24, next-hop 10.0.0.2,type EVPN-RT5, oif vxlan2;

routing entry 3:192.168.1.100/32, next-hop 10.0.0.1,type EVPN-RT2, oif vxlan1;

the routing entry 1 and the routing entry 2 with the type information of "type EVPN-RT5" are first-class routing entries generated based on BGP EVPN RT5 type routing correspondence, and the routing entry 3 with the type information of "type EVPN-RT2" is second-class routing entries generated based on BGP EVPN RT2 type routing correspondence. As illustrated above, the next hops "next-hop 10.0.0.1", "next-hop 10.0.0.2" in the two first type of routing entries are virtual tunnel endpoint addresses of the switches that send the routing information. The next hop "next-hop 10.0.0.1" in the second class of routing entries is the virtual tunnel endpoint address of the switch to which the virtual forwarding node is actually connected.

Step 806, the first network device parses the received BGP EVPN RT5 type route, obtains the server interface address initially configured by the virtual forwarding node from the community attribute, and sets the server interface address initially configured by the virtual forwarding node as a next hop of the first type route entry.

For example, in connection with the application scenario shown in fig. 2, the modified first type of routing entry is as follows:

route entry 1:172.18.1.0/24, next-hop 192.168.1.100,type EVPN-RT5, oif vxlan1;

route entry 2:172.18.1.0/24, next-hop 192.168.1.100,type EVPN-RT5, oif vxlan2;

at step 808, the first network device compares the next hop in the first type of routing entry with the destination network segment of the second type of routing entry in the routing table.

For example, in connection with the application scenario shown in fig. 2, the GW compares 192.168.1.100 with destination network segments of other route entries in the routing table according to the next hop of route entry 1 and route entry 2 being 192.168.1.100, and searches whether there is a route entry with destination network segment being 192.168.1.100. The GW searches 192.168.1.100 for a corresponding second type of route in the route table: routing entry 3.

In step 810, the first network device modifies the value of the next hop of the first type of routing entry that is consistent as a result of the comparison to a value of the next hop of the corresponding second type of routing entry.

For example, in connection with the application scenario shown in fig. 2, the GW modifies the next hops of routing entry 1 and routing entry 2 to the next hop of routing entry 3 according to the comparison result. The routing entries for the modified GW are as follows:

route entry 1:172.18.1.0/24, next-hop 10.0.0.1,type EVPN-RT5, oif vxlan1;

route entry 2:172.18.1.0/24, next-hop 10.0.0.1,type EVPN-RT5, oif vxlan2;

in step 812, the first network device writes the first type of routing entry into a forwarding table in order to forward traffic based on the forwarding table if it is determined that the next hop of the first type of routing entry is a valid egress interface.

For example, in connection with the application scenario shown in fig. 2, the GW checks that the egress interface of the routing entry 1 is vxlan1, and is an effective egress interface, and writes the routing entry 1 into the forwarding table for subsequent forwarding.

According to the embodiment, by configuring the static route on the switch, the extended community attribute support carries the original next hop information in the BGP EVPN RT5 route advertised by the switch, so that the need of establishing BGP neighbors between the virtual forwarding node and the network equipment is eliminated, the need of supporting a BGP routing protocol by the virtual forwarding node is eliminated, the network equipment can search the virtual tunnel endpoint address of the switch actually connected by the virtual forwarding node based on the original next hop information carried by the BGP EVPN RT5 route, and the detour of traffic in the network is avoided.

Correspondingly to the above-mentioned routing method applied to the virtual network of the switch, the present disclosure further provides an embodiment of a routing device configured in the virtual network of the switch, and fig. 9 is a schematic structural diagram of a routing device of the virtual network according to one embodiment of the present disclosure. As shown in fig. 9, the apparatus includes:

the first route sending module 902 may be configured to send, in the virtual network, first type of route information, including: the method comprises the steps of a destination network segment and a server interface address initially configured by a virtual forwarding node of the destination network segment.

A second routing module 904, configured to send, in response to receiving a notification message, a second type of routing information in the virtual network, the notification message for causing a switch to perceive that any virtual forwarding node is on-line with a server to which the switch is connected, the second type of routing information comprising: and the server interface address initially configured by any virtual forwarding node and the virtual tunnel endpoint address of the switch to which the any virtual forwarding node is actually connected.

The first type of routing information and the second type of routing information are used for enabling first network equipment in the virtual network to receive the first type of routing information, receiving the second type of routing information, comparing a server interface address initially configured by a virtual forwarding node in the first type of routing information with a server interface address initially configured by a virtual forwarding node in the second type of routing information, and if the server interface address is consistent with the server interface address initially configured by the virtual forwarding node in the second type of routing information, generating a routing entry, wherein the routing entry comprises the destination network segment and a next hop of the destination network segment, and the next hop is a virtual tunnel endpoint address of a switch in the second type of routing information.

In one or more embodiments of the present description, the virtual network is an ethernet virtual private network based on a border gateway protocol. The first route sending module may be configured to send an RT5 type route including the first type route information in the virtual network, where a server interface address initially configured by the virtual forwarding node is carried in the RT5 type route by a community attribute of the border gateway protocol. The second route sending module may be configured to send an RT2 type route including the second type route information in the virtual network, where a destination network segment in the RT2 type route is set as a server interface address initially configured by the any virtual forwarding node, and a next hop is set as a virtual tunnel endpoint address of a switch actually connected by the any virtual forwarding node.

In one or more embodiments of the present disclosure, the apparatus may further include: a route configuration module configured to configure a static route, the static route including: the network comprises a destination network segment and a next hop of the destination network segment, wherein the next hop is a server interface address initially configured by a virtual forwarding node. The route generation module is configured to generate the RT5 type route based on the border gateway protocol according to the static route, wherein the next hop of a destination network segment in the RT5 type route is a virtual tunnel endpoint address of the switch, and a community attribute in the RT5 type route carries a server node address of initial configuration of a virtual forwarding node.

Correspondingly to the above-mentioned routing method applied to the virtual network of the first network device, the present disclosure further provides an embodiment of a routing device of the virtual network configured in the first network device, and fig. 10 is a schematic structural diagram of a routing device of the virtual network according to one embodiment of the present disclosure. As shown in fig. 10, the apparatus includes:

the first route receiving module 1002 may be configured to receive a first type of route information, including: the method comprises the steps of a destination network segment and a server interface address initially configured by a virtual forwarding node of the destination network segment.

The second route receiving module 1004 may be configured to receive a second type of route information, including: and the server interface address initially configured by any virtual forwarding node and the virtual tunnel endpoint address of the switch to which the any virtual forwarding node is actually connected.

An initial address lookup module 1006, which may be configured to compare a server interface address initially configured by a virtual forwarding node in the first type of routing information with a server interface address initially configured by a virtual forwarding node in the second type of routing information;

The route generation module 1008 may be configured to generate a route entry if the route information is consistent, where the route entry includes the destination network segment and a next hop of the destination network segment, and the next hop is a virtual tunnel endpoint address of the switch in the second type of route information.

In one or more embodiments of the present disclosure, the apparatus may further include: and a forwarding table writing module, configured to write the routing entry into a forwarding table in order to forward traffic based on the forwarding table if it is determined that the next hop of the routing entry is a valid egress interface.

In one or more embodiments of the present specification, the initial address lookup module includes:

the first routing entry generation sub-module may be configured to generate a first type of routing entry according to the first type of routing information, where in the first type of routing entry, a destination network segment is a destination network segment in the first type of routing information, and a next hop is a virtual tunnel endpoint address of a switch that sends the first type of routing information.

The second route entry generating sub-module may be configured to generate a second type route entry according to the second type route information, where in the second type route entry, a destination network segment is a server interface address initially configured by the any virtual forwarding node, and a next hop is a virtual tunnel endpoint address of a switch actually connected to the any virtual forwarding node.

The initial address judging sub-module can be configured to judge whether the first type of routing information carries a server interface address initially configured by the virtual forwarding node of the destination network segment;

the comparing sub-module may be configured to compare the server interface address initially configured by the virtual forwarding node of the destination network segment with the server interface address initially configured by the any virtual forwarding node in the second type of routing entry, if the initial address determination sub-module determines that the virtual forwarding node of the destination network segment is not a virtual forwarding node.

In one or more embodiments of the present specification, the comparing sub-module may include:

an initial address iteration sub-module may be configured to set a server interface address initially configured by a virtual forwarding node of the destination network segment as a next hop in the first class of routing entries.

The compare entry sub-module may be configured to compare a next hop in the first type of routing entry with a server interface address initially configured by the any virtual forwarding node in the second type of routing entry.

Accordingly, the route generating module 1008 may be configured to determine that the comparison entry submodule is consistent, set a virtual tunnel endpoint address of a switch actually connected by the any virtual forwarding node as a next hop in the first type of route entry, and obtain the route entry.

In one or more embodiments of the present description, the virtual network is an ethernet virtual private network based on a border gateway protocol. The first route receiving module may be configured to receive an RT5 type route containing the first type of route information. And the initial address judging sub-module judges whether the RT5 type route has a server interface address which is initially configured by the virtual forwarding node of the destination network segment and carried by the community attribute based on the border gateway protocol.

The above is a schematic scheme of the routing device of the virtual network of the present embodiment. It should be noted that, the technical solution of the routing device of the virtual network and the technical solution of the routing method of the virtual network belong to the same concept, and details of the technical solution of the routing device of the virtual network, which are not described in detail, can be referred to the description of the technical solution of the routing method of the virtual network.

Fig. 11 illustrates a block diagram of a computing device 1100 provided according to one embodiment of the present description. The components of computing device 1100 include, but are not limited to, a memory 1110 and a processor 1120. Processor 1120 is coupled to memory 1110 via bus 1130, and database 1150 is used to hold data.

The computing device 1100 also includes an access device 1140, the access device 1140 enabling the computing device 1100 to communicate via one or more networks 1160. Examples of such networks include the Public Switched Telephone Network (PSTN), a Local Area Network (LAN), a Wide Area Network (WAN), a Personal Area Network (PAN), or a combination of communication networks such as the internet. The access device 1140 may comprise one or more of any type of network interface, wired or wireless (e.g., a Network Interface Card (NIC)), such as an IEEE802.11 Wireless Local Area Network (WLAN) wireless interface, a worldwide interoperability for microwave access (Wi-MAX) interface, an ethernet interface, a Universal Serial Bus (USB) interface, a cellular network interface, a bluetooth interface, a Near Field Communication (NFC) interface, and so forth.

In one embodiment of the present description, the above components of computing device 1100, as well as other components not shown in FIG. 11, may also be connected to each other, such as by a bus. It should be understood that the block diagram of the computing device illustrated in FIG. 11 is for exemplary purposes only and is not intended to limit the scope of the present description. Those skilled in the art may add or replace other components as desired.

Computing device 1100 may be any type of stationary or mobile computing device, including a mobile computer or mobile computing device (e.g., tablet, personal digital assistant, laptop, notebook, netbook, etc.), mobile phone (e.g., smart phone), wearable computing device (e.g., smart watch, smart glasses, etc.), or other type of mobile device, or a stationary computing device such as a desktop computer or PC. Computing device 1100 may also be a mobile or stationary server.

Wherein the processor 1120 is configured to execute computer-executable instructions that, when executed by the processor, perform the steps of the virtual network routing method described above.

The foregoing is a schematic illustration of a computing device of this embodiment. It should be noted that, the technical solution of the computing device and the technical solution of the routing method of the virtual network belong to the same concept, and details of the technical solution of the computing device, which are not described in detail, can be referred to the description of the technical solution of the routing method of the virtual network.

An embodiment of the present disclosure also provides a computer-readable storage medium storing computer-executable instructions that, when executed by a processor, implement the steps of the virtual network routing method described above.

The above is an exemplary version of a computer-readable storage medium of the present embodiment. It should be noted that, the technical solution of the storage medium and the technical solution of the routing method of the virtual network belong to the same concept, and details of the technical solution of the storage medium which are not described in detail can be referred to the description of the technical solution of the routing method of the virtual network.

An embodiment of the present disclosure further provides a computer program, where the computer program, when executed in a computer, causes the computer to perform the steps of the virtual network routing method described above.

The above is an exemplary version of a computer program of the present embodiment. It should be noted that, the technical solution of the computer program and the technical solution of the routing method of the virtual network belong to the same concept, and details of the technical solution of the computer program, which are not described in detail, can be referred to the description of the technical solution of the routing method of the virtual network.

The foregoing describes specific embodiments of the present disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

The computer instructions include computer program code that may be in source code form, object code form, executable file or some intermediate form, etc. The computer readable medium may include: any entity or device capable of carrying the computer program code, a recording medium, a U disk, a removable hard disk, a magnetic disk, an optical disk, a computer Memory, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), an electrical carrier signal, a telecommunications signal, a software distribution medium, and so forth. It should be noted that the computer readable medium contains content that can be appropriately scaled according to the requirements of jurisdictions in which such content is subject to legislation and patent practice, such as in certain jurisdictions in which such content is subject to legislation and patent practice, the computer readable medium does not include electrical carrier signals and telecommunication signals.

It should be noted that, for simplicity of description, the foregoing method embodiments are all expressed as a series of combinations of actions, but it should be understood by those skilled in the art that the embodiments are not limited by the order of actions described, as some steps may be performed in other order or simultaneously according to the embodiments of the present disclosure. Further, those skilled in the art will appreciate that the embodiments described in the specification are all preferred embodiments, and that the acts and modules referred to are not necessarily all required for the embodiments described in the specification.

In the foregoing embodiments, the descriptions of the embodiments are emphasized, and for parts of one embodiment that are not described in detail, reference may be made to the related descriptions of other embodiments.

The preferred embodiments of the present specification disclosed above are merely used to help clarify the present specification. Alternative embodiments are not intended to be exhaustive or to limit the invention to the precise form disclosed. Obviously, many modifications and variations are possible in light of the teaching of the embodiments. The embodiments were chosen and described in order to best explain the principles of the embodiments and the practical application, to thereby enable others skilled in the art to best understand and utilize the invention. This specification is to be limited only by the claims and the full scope and equivalents thereof.

Claims

1. A routing system for a virtual network, comprising: a plurality of switches and a first network device;

the switch is configured to send a first type of routing information in a virtual network, the first type of routing information comprising: a server interface address initially configured by a virtual forwarding node of a destination network segment; the switch is further configured to send, in response to receiving a notification message, a second type of routing information in the virtual network, the notification message for causing the switch to perceive that any virtual forwarding node is on-line with a server to which the switch is connected, the second type of routing information comprising: the server interface address initially configured by any virtual forwarding node and the virtual tunnel endpoint address of the switch to which any virtual forwarding node is actually connected;

the first network device is configured to receive the first type of routing information, receive the second type of routing information, compare a server interface address initially configured by a virtual forwarding node in the first type of routing information with a server interface address initially configured by a virtual forwarding node in the second type of routing information, and if the server interface addresses are consistent, generate a routing entry, where the routing entry includes the destination network segment and a next hop of the destination network segment, and the next hop is a virtual tunnel endpoint address of a switch in the second type of routing information.

2. The system of claim 1, the virtual network being a border gateway protocol based ethernet virtual private network;

the first network device is gateway device in the virtual network, and the switches are respectively connected with the gateway device.

3. A routing method of a virtual network, applied to a first network device, comprising:

receiving first-type routing information, wherein the first-type routing information comprises: a server interface address initially configured by a virtual forwarding node of a destination network segment;

receiving second-type routing information, wherein the second-type routing information comprises: a server interface address initially configured by any virtual forwarding node and a virtual tunnel endpoint address of a switch to which the any virtual forwarding node is actually connected;

comparing the server interface address initially configured by the virtual forwarding node in the first type of routing information with the server interface address initially configured by the virtual forwarding node in the second type of routing information;

and if the two types of route information are consistent, generating a route entry, wherein the route entry comprises the destination network segment and the next hop of the destination network segment, and the next hop is a virtual tunnel endpoint address of a switch in the second type of route information.

4. A method according to claim 3, further comprising:

and writing the routing entry into a forwarding table under the condition that the next hop of the routing entry is determined to be a valid outgoing interface, so as to forward traffic based on the forwarding table.

5. A method according to claim 3, said comparing the server interface address initially configured by the virtual forwarding node in the first type of routing information with the server interface address initially configured by the virtual forwarding node in the second type of routing information, comprising:

6. The method of claim 5, wherein comparing the server interface address initially configured by the virtual forwarding node of the destination network segment with the server interface address initially configured by the any virtual forwarding node in the second type of routing entry comprises:

setting a server interface address initially configured by a virtual forwarding node of the destination network segment as a next hop in the first type of routing entry;

comparing the next hop in the first type of routing entry with the server interface address initially configured by any virtual forwarding node in the second type of routing entry;

and if so, generating a routing entry, including:

and if the virtual tunnel endpoint addresses of the switches actually connected by any virtual forwarding node are consistent, setting the virtual tunnel endpoint address of the switch actually connected by any virtual forwarding node as the next hop in the first type of routing item, and obtaining the routing item.

7. The method of claim 5, the virtual network being a border gateway protocol based ethernet virtual private network;

The receiving the first type of routing information includes:

receiving an RT5 type route containing the first type route information;

the judging whether the first type of routing information carries the server interface address initially configured by the virtual forwarding node of the destination network segment comprises the following steps:

and judging whether the RT5 type route has a server interface address which is initially configured by a virtual forwarding node of the destination network segment and carried by the community attribute of the border gateway protocol.

8. A routing method of a virtual network, applied to a switch, comprising:

transmitting a first type of routing information in a virtual network, the first type of routing information comprising: a server interface address initially configured by a virtual forwarding node of a destination network segment;

in response to receiving a notification message, sending second type routing information in the virtual network, where the notification message is used to make a switch perceive that any virtual forwarding node is on-line at a server connected to the switch, and the second type routing information includes: the server interface address initially configured by any virtual forwarding node and the virtual tunnel endpoint address of the switch to which any virtual forwarding node is actually connected;

9. The method of claim 8, the virtual network being a border gateway protocol based ethernet virtual private network;

the sending the first type of routing information in the virtual network comprises the following steps:

transmitting an RT5 type route containing the first type of route information in the virtual network, wherein a server interface address initially configured by the virtual forwarding node is carried in the RT5 type route through a community attribute of the border gateway protocol;

the sending the second type of routing information in the virtual network comprises the following steps:

And sending an RT2 type route containing the second type route information in the virtual network, wherein a destination network segment in the RT2 type route is set as a server interface address initially configured by any virtual forwarding node, and the next hop is set as a virtual tunnel endpoint address of a switch actually connected by any virtual forwarding node.

10. The method of claim 9, further comprising, prior to sending the RT5 type route containing the first type of route information in a virtual network:

configuring a static route, wherein the static route comprises the following steps: the method comprises the steps of a destination network segment and a next hop of the destination network segment, wherein the next hop is a server interface address initially configured by a virtual forwarding node;

and generating the RT5 type route based on the border gateway protocol according to the static route, wherein the next hop of the destination network segment in the RT5 type route is the virtual tunnel endpoint address of the switch, and the community attribute in the RT5 type route carries the server node address of the initial configuration of the virtual forwarding node.

11. A routing apparatus of a virtual network, configured in a first network device, comprising:

a first route receiving module configured to receive a first type of route information, the first type of route information comprising: a server interface address initially configured by a virtual forwarding node of a destination network segment;

A second route receiving module configured to receive a second type of route information, the second type of route information comprising: a server interface address initially configured by any virtual forwarding node and a virtual tunnel endpoint address of a switch to which the any virtual forwarding node is actually connected;

an initial address lookup module configured to compare a server interface address initially configured by a virtual forwarding node in the first type of routing information with a server interface address initially configured by a virtual forwarding node in the second type of routing information;

and the route generation module is configured to generate a route entry if the initial address lookup module determines that the initial address lookup module is consistent, wherein the route entry comprises the destination network segment and a next hop of the destination network segment, and the next hop is a virtual tunnel endpoint address of the switch in the second type of route information.

12. A routing device of a virtual network, configured in a switch, comprising:

a first routing module configured to send a first type of routing information in a virtual network, the first type of routing information comprising: a server interface address initially configured by a virtual forwarding node of a destination network segment;

A second route sending module configured to send, in response to receiving a notification message, second type routing information in the virtual network, the notification message being used to cause a switch to perceive that any virtual forwarding node is on-line with a server to which the switch is connected, the second type routing information including: the server interface address initially configured by any virtual forwarding node and the virtual tunnel endpoint address of the switch to which any virtual forwarding node is actually connected;

13. A computing device, comprising:

a memory and a processor;

the memory is configured to store computer executable instructions that, when executed by the processor, implement the steps of the virtual network routing method of any one of claims 3 to 7 or 8 to 10.

14. A computer readable storage medium storing computer executable instructions which when executed by a processor implement the steps of the virtual network routing method of any one of claims 3 to 7 or 8 to 10.