CN115277550A

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

Info

Publication number: CN115277550A
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: 2022-11-01
Anticipated expiration: 2042-06-21
Also published as: CN115277550B

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 target network segment and a server interface address initially configured by a virtual forwarding node of the target 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 actually connected with the virtual forwarding node; 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 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 the virtual tunnel endpoint address of the switch in the second type of routing information.

Description

Routing system, routing method and routing device of virtual network

Technical Field

The embodiment of the present specification relates to the field of computer technologies, and in particular, to a routing system, a routing method, and a routing apparatus for a virtual network.

Background

Cloud computing developed based on computing virtualization also puts a demand on virtualization on networks. In the mainstream network virtualization scheme at present, 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 below different switches. In order to ensure that traffic can be normally forwarded when a virtual forwarding node is migrated to a different switch, a switch usually advertises routing information in a virtual network of a tenant at present. Thus, a plurality of switches announce the routes of the same virtual forwarding node to the 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, one virtual forwarding node only exists under one switch at the same time, so when the network device shares the traffic 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 detour exists in the traffic forwarding process, thereby increasing the bandwidth occupation and traffic delay of the switch.

Disclosure of Invention

In view of the above, embodiments of the present specification 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 technical defects in the prior art.

According to a first aspect of embodiments herein, there is provided a routing system of a virtual network, including: a plurality of switches and a first network device. The switch configured to send a first type of routing information in a virtual network, the first type of routing information comprising: a target network segment and a server interface address initially configured by a virtual forwarding node of the target network segment; the switch is further configured to send a second type of routing information in the virtual network in response to receiving a notification message, the notification message for causing the switch to perceive that any virtual forwarding node is online on 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.

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

According to a second aspect of the embodiments of the present specification, there is provided a routing method for a virtual network, applied to a first network device, including: receiving first type routing information, wherein the first type routing information comprises: a target network segment and a server interface address initially configured by a virtual forwarding node of the target 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 actually connected to the any virtual forwarding node; 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 network segment is consistent with the destination network segment, 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.

Optionally, the method further comprises: and under the condition that the next hop of the routing entry is determined to be a valid outgoing interface, writing the routing entry into a forwarding table so as to forward the flow 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 entry according to the first type of routing information, wherein 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 which sends the first type of routing information; generating a second type of routing entry according to the second type of routing information, wherein in the second type of routing entry, a destination network segment is a server interface address initially configured by any virtual forwarding node, and a next hop is a virtual tunnel endpoint address of a switch actually connected with any virtual forwarding node; judging whether the first type of routing information carries a server interface address initially configured by the 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 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 any virtual forwarding node in the second type of routing entry includes: setting the server interface address initially configured by the virtual forwarding node of the destination network segment as the next hop in the first type of routing entry; comparing the next hop in the first routing entry with the server interface address initially configured by any virtual forwarding node in the second routing entry; if so, generating a routing entry, comprising: and if the virtual forwarding nodes are consistent with the first class of routing entries, setting the virtual tunnel endpoint address of the switch actually connected with any virtual forwarding node as the next hop in the first class of routing entries to obtain the routing entries.

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

According to a third aspect of the embodiments of the present specification, there is provided a routing method for a virtual network, applied to a switch, including: sending first type routing information in a virtual network, the first type routing information comprising: a target network segment and a server interface address initially configured by a virtual forwarding node of the target network segment; in response to receiving a notification message, sending a second type of routing information in the virtual network, where the notification message is used for a switch to perceive that any virtual forwarding node is online on a server connected to the switch, and the second type of routing information includes: a server interface address initially configured by any virtual forwarding node and a virtual tunnel endpoint address of a switch actually connected to the any virtual forwarding node; the first type of routing information and the second type of routing information are used for enabling a first network device in the virtual network 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 a border gateway protocol. The sending of the first type of routing information in the virtual network includes: and 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 includes: and sending an RT2 type route containing the second type of 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 a next hop is set as a virtual tunnel endpoint address of a switch actually connected with any virtual forwarding node.

Optionally, before sending the RT5 type route including the first type of route information in the virtual network, the method further includes: configuring a static route, wherein the static route comprises the following steps: 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 a target 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 initially configured by the virtual forwarding node.

According to a fourth aspect of the embodiments of the present specification, there is provided a routing apparatus of a virtual network, configured on a first network device, including: a first route receiving module configured to receive a first type of routing information, the first type of routing information including: and the server interface address is initially configured by the virtual forwarding node of the destination network segment. A second route receiving module configured to receive a second type of routing information, 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. An initial address lookup module 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 search module determines that the initial address search 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 routing information.

According to a fifth aspect of the embodiments of the present specification, there is provided a routing apparatus of a virtual network, configured in a switch, including: a first routing sending module configured to send a first type of routing information in a virtual network, the first type of routing information including: and the virtual forwarding node of the target network segment is initially configured with a server interface address. A second routing sending module configured to send, in response to receiving a notification message, a second type of routing information in the virtual network, where the notification message is used for a switch to perceive that any virtual forwarding node is online on a server connected to the switch, and the second type of 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 a first network device in the virtual network 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.

According to a sixth aspect of embodiments herein, there is provided a computing device comprising: a memory and a processor; the memory is used for storing computer executable instructions, and the processor is used for executing the computer executable instructions, and the computer executable instructions when executed by the processor realize the steps of the routing method of the virtual network according to any embodiment of the specification.

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

According to an eighth aspect of embodiments herein, 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-mentioned routing method for a virtual network.

An embodiment of the present specification provides a routing system of a virtual network, where the system includes multiple switches and a first network device, and a switch in the virtual network includes a destination network segment and a server interface address initially configured by a virtual forwarding node of the destination network segment in first-class routing information sent by the switch in the virtual network, and a switch in the virtual network sends second-class routing information including the server interface address initially configured by any virtual forwarding node and a virtual tunnel endpoint address of a switch actually connected to any virtual forwarding node in a case of sensing that any virtual forwarding node is online in a server connected to the switch, so that the first network device can compare the server interface address initially configured by the virtual forwarding node in the first-class routing information with a server interface address initially configured by a virtual forwarding node in a second-class routing information after receiving the first routing information and receiving the second routing information, and if the server interface addresses are consistent, generate a routing entry, and a next hop of the destination network segment in the routing entry is a tunnel address of the switch in the second-class routing information, and the virtual forwarding network device can reduce traffic flow of the virtual network and delay when the next hop is a virtual network segment connected to the virtual network.

Drawings

FIG. 1 is a schematic diagram of a virtual network provided by 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 provided in an embodiment of the present specification;

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

fig. 5 is a flowchart illustrating a processing procedure of a routing method for a virtual network according to an embodiment of the present disclosure;

fig. 6 is a flowchart illustrating a process of a routing method for 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 specification;

fig. 8 is a flowchart illustrating a processing procedure of a routing method for a virtual network according to still 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 apparatus configured in 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 according to an embodiment of the present disclosure.

Detailed Description

In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present specification. This description may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein, as those skilled in the art will be able to make and use the present disclosure without departing from the spirit and scope of the present disclosure.

The terminology used in the description of the one or more embodiments is for the purpose of describing the particular embodiments only and is not intended to be limiting of the description of the one or more embodiments. As used in one or more embodiments of the present specification 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 and all possible combinations of one or more of the associated listed items.

It will be understood that, although the terms first, second, etc. may be used herein in one or more embodiments 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 can also be referred to as a second and, similarly, a second can 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 \8230; \8230when" or "when 8230; \823030when" or "in response to a determination," depending on the context.

First, the noun terms referred to in one or more embodiments of the present specification are explained.

ARP (Address resolution Protocol) indicates an Address resolution Protocol.

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

TOR (Top Of Rack), top Of Rack switch.

BGP (Border Gateway Protocol), which is a decentralized autonomous routing Protocol for a core on the internet, represents a Border Gateway Protocol.

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

VXLAN (Virtual eXtensible Local Area Network) represents a Virtual eXtensible Local Area Network. VXLAN is characterized in that L2 ethernet frames are encapsulated into UDP packets (i.e., L2 over L4) and transmitted in L3 networks. Wherein L2 represents two layers, L3 represents three layers, and L4 represents four layers.

VTEP (virtual Tunnel End Point), representing a virtual Tunnel endpoint.

VRF (Virtual Routing and Forwarding) represents a Virtual route Forwarding instance.

IP, refers to a unique address specified by each device on the internet. Due to the unique IP address, it is ensured that the device which wants to communicate is efficiently found.

Cloud computing developed based on computing virtualization also puts a demand on virtualization on 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 is widely deployed and applied in the industry due to the advantages of no invasion to a server, excellent forwarding performance, clear operation and maintenance interfaces and the like.

In a network virtualization scenario, there often exists a forwarding node of a tenant deployed on a physical server in a virtual machine state. Such virtual forwarding nodes may behave as: virtual firewalls, virtual load balancing, virtual routers, and the like. The virtual forwarding node is not a forwarding destination of the traffic generally, but a transit node of the traffic. Therefore, switches (e.g., TORs) connected to the virtual forwarding node typically need to configure routes in the VRFs corresponding to the tenants. In order to reduce the coupling between the virtual forwarding node and the connected switch, a static route may be selected, and a dynamic route may be selected based on the actual application scenario. Because the route points to the network connected behind the virtual forwarding node, the switch needs to notify the route in the virtual network of the tenant, and then can correctly forward the traffic sent to the network to the virtual forwarding node, and then the virtual forwarding node forwards the traffic to the corresponding network. Virtual networks, also known as overlay networks, may be understood as logical networks built on top of physical networks.

In the following, taking the virtual network shown in fig. 1 as an example, a process of a switch advertising a route and forwarding traffic in the current virtual network implemented based on BGP EVPN is schematically described. As shown in fig. 1, a virtual switching node vRouter is deployed on a server 1 connected below 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 a network behind the virtual forwarding node vRouter is 172.18.1.0/24. To enable traffic to be forwarded to the VRF on the dormitor network, static routes may be configured in the VRF corresponding to the tenant on switch TOR 1. In the configured static route, 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 initially configured by the virtual forwarding node vRouter. Distributing the static route to a BGP EVPN protocol stack in a redistribution mode on a TOR1 of the switch, announcing the static route to remote network equipment by the BGP EVPN through an RT5 type route, and modifying a next hop into a virtual tunnel endpoint address VTEP IP of the TOR1 of the switch according to the BGP EVPN protocol during the announcement of the route. When the virtual forwarding node vruter is online for the first time at the switch TOR1, after the switch TOR1 receives an ARP type message (such as an ARP request and 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 as shown in fig. 1 see a RT2 type route to the server interface address 192.168.1.100/32 initially configured by the virtual forwarding node vRouter. Because the virtual forwarding node vRouter may be migrated to the server 2, in order to ensure that the traffic can be forwarded normally after the virtual forwarding node vRouter is migrated to the server 2, a static route pointing to a server interface address initially configured by the virtual forwarding node vRouter may also be preconfigured in a VRF corresponding to a tenant on the switch TOR2, and the static route is also redistributed to the BGP EVPN protocol stack. At this time, the GW learns two routes pointing to 172.18.1.0/24 simultaneously, and the next hop points to the VTEP IPs of TOR1 and TOR2, respectively, thereby forming load sharing on the GW. When GW receives the traffic to 172.18.1.0/24 segment, it can share the traffic to TOR1 and it can also share the traffic to TOR2. Sharing TOR1, traffic flows into the vruter through the route labeled "flow 1" in fig. 1. Sharing TOR2, traffic flows into the vruter through the route labeled "flow 2" in fig. 1. As can be seen from "flow 2", since the virtual forwarding node vRouter is actually connected under the switch TOR1, after the switch TOR2 receives the traffic sent by the GW, TOR2 needs to first search for the local route discovery 172.18.1.0/24 next hop of 192.168.1.100/32, and the 192.168.1.100/32 next hop is learned through the RT2 route and points to the virtual tunnel endpoint address VTEP IP of the switch TOR 1: 10.0.0.1. therefore, the switch TOR2 needs to forward traffic to TOR1 first, and TOR1 can finally forward the traffic to the virtual forwarding node vRouter, and there is detour in the traffic forwarding process.

As can be seen from the above exemplary 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 down different switches. Because the virtual forwarding node has the possibility of migration, the switch cannot sense the migration event of the virtual forwarding node, and in order to ensure that the traffic can be normally forwarded when the virtual forwarding node migrates to different switches, corresponding routing information is configured in the VRF corresponding to the tenant of the switch, and the switch advertises the routing information in the virtual network of the tenant. When a switch advertises route information for a virtual network out-to-the-home, the route information will be advertised by default to a remote network device in a 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 multiple switches all announce the routing information of the same virtual forwarding node to the far end, multiple load sharing is formed on the network equipment for the routing entries of the same virtual forwarding node, and the next hop points to the corresponding switch VTEP IP addresses respectively. However, because the virtual forwarding node only exists under one switch at the same time, when the remote network device shares the traffic to the virtual forwarding node to the switch without the virtual forwarding node below, after the switch receives the traffic, the switch where the interface address of the next-hop virtual forwarding node is located needs to be searched according to the RT2 type route, and the traffic is sent to the corresponding switch, and then the traffic can be finally sent to the virtual forwarding node. The bypass can exist in the whole process due to high flow probability, the occupied bandwidth of the switch is increased, and meanwhile, the flow delay can also be increased.

In some technical solutions, in a virtual network implemented based on BGP EVPN, a BGP route neighbor may be directly established in an overlay network by a virtual forwarding node vRouter and a network device GW, so that the virtual forwarding node vRouter and the network device GW directly interact with each other for routing, so as to achieve a target that the GW node learns an original next hop of the route, and then a route iteration is performed by the network device GW to obtain a virtual tunnel endpoint address of an switch where the vRouter is actually located. However, this may cause the coupling between the virtual forwarding node and the network device to increase, and generate dependence on the capability of the virtual forwarding node, so that the virtual forwarding node needs to support the BGP routing protocol, and the virtual forwarding node and the network device can interact with each other through the BGP protocol, thereby providing a requirement for the BGP protocol interoperability between the virtual forwarding node and the network device.

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

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

in step 202, the switch sends first type routing information in the virtual network, where the first type routing information includes: and the server interface address is initially configured by the virtual forwarding node of the destination network segment.

In the application scenario shown in fig. 2, the first type of routing information is specifically represented as routing information carried in EVPN RT5 type routing. For example, the route information of the overlay network is advertised to the outside by the switches TOR1 and TOR2 as shown in fig. 2. The routing information is sent by EVPN RT5 type routing, and the EVPN RT5 type routing example shown in fig. 2 includes: destination segment "ROUTE _ PREFIX:172.18.1.0/24", NEXT HOP" NEXT _ HOP:10.0.0.1 "and carrying the original next hop in the static route (represented as origin-next-hop" 192.168.1.100 "in fig. 2) in the form of BGP extended community attribute (represented as ext-community in fig. 2), so that any network device in the virtual network obtains the original next hop information of the static route. The original next hop in the static route refers to a server interface address initially configured by the virtual forwarding node or an upper connection port IP understood as the virtual forwarding node.

In step 204, the switch sends a second type of routing information in the virtual network in response to receiving a notification message, where the notification message is used for enabling the switch to perceive that any virtual forwarding node is online on a server connected to the switch, and the second type of 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 notification message may be referred to as an address resolution protocol notification message, and is a message that triggers the switch to sense that any virtual forwarding node is online on a server connected to the switch. For example, in a border gateway protocol based virtual network, the notification message appears as an ARP notification message, which can trigger a switch to perceive an ARP request, ARP protocol message, which changes the location of the MAC address.

The second type of routing information is embodied as routing information carried in an EVPN RT2 type route. For example, the switch TOR2 shown in fig. 2 advertises the original next hop information for the static route in an EVPN RT2 type route in response to receiving the advertisement message appearing as an ARP message. In the EVPN RT2 type route, the destination network segment is a 32-bit server interface address initially configured by the virtual forwarding node vRouter, and the next hop is a virtual tunnel endpoint address of the switch TOR1 actually connected to 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, in the first network device GW, the GW first determines the original next hop information in the extended community attribute in the EVPN RT5 type route, and performs lookup of the virtual tunnel endpoint address of the actually connected switch by using the original next hop to the RT2 route, and further writes the virtual tunnel endpoint address of the actually connected switch into the local route entry corresponding to the EVPN RT5 type route, so that the next hop in the route entry corresponding to the RT5 type route on the GW is the virtual tunnel endpoint address of the real switch connected to the virtual forwarding node vRouter.

Through the processing of the above steps, the GW obtains the virtual tunnel endpoint address of the switch to which the virtual forwarding node vRouter is actually connected, so that the traffic sent to the network behind the virtual forwarding node vRouter can be correctly sent to the switch to which the virtual forwarding node vRouter is actually connected, thereby avoiding traffic bypassing. When the virtual forwarding node vRouter migrates, the virtual forwarding node vRouter actively sends an ARP message (denoted as ARP packets in fig. 2) to the connected switch after migrating, so that the connected switch generates a new EVPN RT 2-type route after receiving the ARP message, so as to update the virtual tunnel endpoint address of the newly connected switch of the virtual forwarding node vRouter.

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

Referring to fig. 3, fig. 3 is a schematic structural diagram illustrating 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, the switches are illustrated as switch a and switch B, and the number of switches in practical application may be set as required. The first network device 304 may be represented 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 including: a target network segment and a server interface address initially configured by a virtual forwarding node of the target network segment; the switch 302 is further configured to send a second type of routing information in the virtual network in response to receiving a notification message, the notification message for enabling the switch to perceive that any virtual forwarding node is online on a server to which the switch is connected, the second type of 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.

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 with the server interface address initially configured by the virtual forwarding node in the second type of routing information, 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 switch in the virtual network includes a destination network segment and a server interface address initially configured by a virtual forwarding node of the destination network segment in first-class routing information sent by the switch in the virtual network, and the switch in the virtual network sends second-class routing information including 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 of perceiving that any virtual forwarding node is on the line of a server connected by the switch, the first network device can compare the server interface address initially configured by the virtual forwarding node in the first-class routing information with the server interface address initially configured by the virtual forwarding node in the second-class routing information after receiving the first routing information and receiving the second routing information, if the first routing information and the second routing information are consistent, a routing entry is generated, and a next hop of the destination network segment in the routing entry is the virtual tunnel endpoint address of the switch in the second-class routing information, and a next hop of the destination network segment in the routing entry is the tunnel address of the switch actually connected to the virtual forwarding node, thereby reducing traffic of the switch and reducing traffic flow in the virtual network.

It should be noted that the virtual network described in the embodiments of the present specification may be implemented based on any network virtualization technology. For example, 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 network device is a gateway device in the virtual network, and the switches are respectively connected with the gateway device. In this embodiment, a specific implementation manner in which the switch sends the routing information and the gateway device writes the virtual tunnel endpoint address of the switch to which the virtual forwarding node is actually connected into the routing entry may refer to the description in the application scenario embodiment shown in fig. 2, and details are not described here again.

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

step 402, sending first type routing information in a virtual network, where the first type routing information includes: and the virtual forwarding node of the target network segment is initially configured with a server interface address.

The first type of routing information is information indicating a flow direction of a data packet sent to a destination network segment. The route configured by the switch can be a static route or a dynamic route, and the switch advertises route information into the virtual network based on the route configured by the switch. When the switch advertises a route in the virtual network, any network device in the virtual network may receive the route advertised by the switch. In the route announced by the switch, the destination network segment and the next hop of the destination network segment can be included according to the requirements of practical application scenarios. The next hop of the destination network segment may be directly the server interface address initially configured by the virtual forwarding node, 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, the switch may send, in the virtual network, an RT5 type route including the first type of route information, where 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 remote network device by an RT5 type route. This RT5 type routing is also referred to as IP prefix routing. The next hop carried in the RT5 type route is the virtual tunnel endpoint address configured for the switch. In addition, in the EVPN RT5 type route, the original next hop of the static route is also carried in the form of BGP extended community attribute, that is, the server interface address initially configured by the virtual forwarding node, so that the network device at the receiving end obtains the original next hop information of the route.

Step 404, in response to receiving a notification message, sending second type routing information in the virtual network, where the notification message is used for enabling a switch to sense that any virtual forwarding node is online on 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 second type of routing information is information indicating an interface address of a server initially configured by any virtual forwarding node and an address of a virtual tunnel endpoint 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, the RT2 type route including the second type of route information may be sent in the virtual network, where a destination network segment in the RT2 type route is set as a server interface address initially configured by any virtual forwarding node, and a next hop is set as a virtual tunnel endpoint address of a switch actually connected to any virtual forwarding node.

The first type of routing information and the second type of routing information are used for enabling a first network device in the virtual network 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.

In the method, a switch in the virtual network includes a destination network segment and a server interface address initially configured by a virtual forwarding node of the destination network segment in first-class routing information sent by the switch in the virtual network, and a switch in the virtual network sends second-class routing information including 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 of sensing that any virtual forwarding node is online in a server connected by the switch, so that the first network device can compare the server interface address initially configured by the virtual forwarding node in the first-class routing information with the server interface address initially configured by the virtual forwarding node in the second-class routing information after receiving the first routing information and receiving the second routing information, if the server interface addresses are consistent, a routing entry is generated, and a next hop of the destination node in the routing entry is the virtual tunnel address of the switch in the second-class routing information, and a next hop of the destination node in the routing entry is the virtual tunnel address of the switch actually connected to the virtual forwarding node, thereby reducing traffic of the switch and reducing traffic flow of the routing network directly based on the switch.

In one or more embodiments of the present specification, in a virtual network implemented based on BGP EVPN, before sending, in the virtual network, an RT 5-type route including the first-type routing information, the method may further include: configuring a static route, wherein the static route comprises the following steps: a target network segment and a next hop of the target 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 a target 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 initially configured by the virtual forwarding node. In this embodiment, by configuring the static route on the switch, the switch advertises, in the virtual network, the RT 5-type route carrying the server interface address initially configured by the virtual forwarding node based on the static route, thereby obviating the need for the virtual forwarding node to support the BGP routing protocol. 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, and 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 in which the switch carries a server interface address initially configured by a virtual forwarding node through an RT5 type routing extended community attribute. Fig. 5 is a flowchart illustrating a processing procedure of a routing method of a virtual network according to an embodiment of the present specification. As shown in fig. 5, the method may specifically include:

step 502, each switch of the virtual network is respectively configured with static routes pointing to the same destination network segment and redistributed to the BGP EVPN address family.

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

Step 504, each switch generates a corresponding BGP EVPN RT5 type route, and the next hop is filled as its own VTEP IP.

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

Step 506, each switch checks whether the function of the node address of the server initially configured by the virtual forwarding node carried by the community attribute in the BGP EVPN RT5 type route of the switch is started.

If not, step 510 is entered directly.

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

For example, in conjunction with the application scenario shown in fig. 2, switches TOR1 and TOR2 attach an extended community attribute with an attribute value of 192.168.1.100/32 in the generated BGP EVPN RT 5-type route.

In step 510, each switch advertises the BGP EVPN RT5 routes 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 embodiment 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 illustrating a processing procedure of a routing method of a virtual network according to another embodiment of the present disclosure. As shown in fig. 6, the method may specifically include:

step 602, after the virtual forwarding node instance is initialized, an ARP request/GARP notification type ARP message is sent to the connected switch.

For example, in conjunction 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 type ARP message is sent.

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

For example, in combination with the application scenario shown in fig. 2, after receiving the ARP/GARP message, the vruter uplink TOR1 switch locally generates a corresponding ARP entry and also generates a corresponding BGP EVPN RT2 route, where the next hop is the own VTEP IP.

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

After receiving the BGP EVPN RT2 type route advertised by the switch, other network devices locally generate a second type of route entry, wherein in the second type of route entry, the destination network segment is a server interface address initially configured by the virtual forwarding node, and the next hop points to the VTEP IP of the switch which sends the BGP EVPN RT2 type route.

For example, in conjunction 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 is a flowchart illustrating a routing method of a virtual network according to an embodiment of the present specification. The routing method of the virtual network provided by the embodiment is applied to the first network device. As shown in fig. 7, the method may specifically include:

step 702, receiving first type routing information, where the first type routing information includes: and the virtual forwarding node of the target network segment is initially configured with a server interface address.

Step 704, receiving a second type of routing information, where the second type of 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.

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 process may be implemented in various ways, and the examples in this specification do not limit this. For example, the server interface address initially configured by the virtual forwarding node may be directly obtained from the first type of routing information and the second type of routing information, and compared. For another example, the corresponding routing entries may be automatically generated based on a gateway protocol of the virtual network, and then the server interface addresses initially configured by the virtual forwarding nodes are obtained from the routing entries and compared.

Step 708, if the two types of routing information are consistent, a routing entry is generated, 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.

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

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

According to 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 type of routing information with the server interface address initially configured by the virtual forwarding node in the second type of routing information, if the server interface addresses are consistent, a routing entry is generated, and the next hop of the target network segment in the routing entry is the virtual tunnel endpoint address of the switch in the second type of routing information, namely the next hop of the target network segment in the routing entry is the virtual tunnel endpoint address of the switch actually connected with the virtual forwarding node, so that the first network device can directly forward the flow to the switch actually connected with the virtual forwarding node based on the routing entry, thereby avoiding the bypassing of the flow in the network, and reducing the bandwidth occupation of the switch and the flow delay.

In one or more embodiments of the present description, 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, server interface addresses initially configured by virtual forwarding nodes in two pieces of routing information are compared, so that the method provided in the embodiments of the present description 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 entry according to the first type of routing information, wherein 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 which sends the first type of routing information;

generating a second type of routing entry according to the second type of routing information, wherein in the second type of routing entry, a destination network segment is a server interface address initially configured by any virtual forwarding node, and a next hop is a virtual tunnel endpoint address of a switch actually connected with 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 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 in 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 the server interface address initially configured by the virtual forwarding node of the destination network segment as the next hop in the first type of routing entry; comparing the next hop in the first routing entry with the server interface address initially configured by any virtual forwarding node in the second routing entry. Accordingly, if consistent, a routing entry is generated, including: and if the virtual forwarding nodes are consistent, setting the virtual tunnel endpoint address of the switch actually connected with any virtual forwarding node as the next hop in the first type of routing entries to obtain the routing entries.

In the above embodiment, the server interface address initially configured by the virtual forwarding node carried by the route is iterated to the next hop of the first-class routing entry generated correspondingly, so that a direct contact between the first-class routing entry and the server interface address initially configured by the virtual forwarding node is established, so as to compare the first-class routing entry with the server interface address initially configured by the virtual forwarding node in the second-class routing entry, and in a case of determining consistency, the virtual tunnel endpoint address of the switch actually connected by the virtual forwarding node can be more directly and quickly substituted into the next hop in the first-class routing entry.

Taking the example that the virtual network is an ethernet virtual private network based on a border gateway protocol, the receiving the first type of routing information includes: receiving a RT5 type route comprising the first type of route information. The determining whether the first type of routing information carries a server interface address initially configured by a virtual forwarding node of the destination network segment includes: and judging whether a server interface address initially configured by the virtual forwarding node of the destination network segment carried by the community attribute based on the border gateway protocol exists in the RT5 type route.

Next, with reference to fig. 8, a detailed description is given of a specific implementation in which the first network device finds, through iteration, a virtual tunnel endpoint address of a switch to which the virtual forwarding node is actually connected. Fig. 8 is a flowchart illustrating a process of a routing method of a virtual network according to still another embodiment of the present specification. As shown in fig. 8, the method may specifically include:

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

For example, in connection with the application scenario shown in fig. 2, the GW receives BGP EVPN RT5 type routes advertised by TOR1 and TOR2. The community attribute in the BGP EVPN RT5 type route 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 segment, and 172.18.1.0/24 is the value of the destination 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 the switch TOR1, ext-community represents the community attribute, origin-NEXT-HOP represents the original NEXT HOP, that is, 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.

Step 804, the first network device receives a BGP EVPN RT2 type route advertised in the virtual network by the switch sensing that any virtual forwarding node is online in a server connected to the switch, and correspondingly generates a second type of route entry.

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

routing 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;

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

wherein, the routing entry 1 and the routing entry 2 with the type information "type EVPN-RT5" are the first type routing entries correspondingly generated based on the BGP EVPN RT5 type routing, and the routing entry 3 with the type information "type EVPN-RT2" is the second type routing entries correspondingly generated based on the BGP EVPN RT2 type routing. As in the above example, the next hop "next-hop 10.0.0.1" or "next-hop 10.0.0.2" in the two first-type routing entries is the virtual tunnel endpoint address of the switch sending the routing information. The next hop "next-hop 10.0.0.1" in the second type of routing entry 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 RT 5-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 the 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:

routing 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;

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 conjunction with the application scenario shown in fig. 2, the GW compares 192.168.1.100 with destination segments of other routing entries in the routing table according to the fact that the next hops of routing entry 1 and routing entry 2 are 192.168.1.100, and finds whether or not there is a routing entry with a destination segment of 192.168.1.100. The GW finds that 192.168.1.100 has a corresponding second type route in the routing table: route entry 3.

Step 810, the first network device modifies the value of the next hop of the first type routing entry, which is consistent with the comparison result, to the value of the next hop corresponding to the second type routing entry.

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

routing 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 the forwarding table in order to forward traffic based on the forwarding table when determining that the next hop of the first type of routing entry is a valid egress interface.

For example, with reference to the application scenario shown in fig. 2, the GW checks that the egress interface of the routing entry 1 is vxlan1, and if the egress interface is a valid egress interface, writes the routing entry 1 into the forwarding table for subsequent forwarding.

As can be seen from the above embodiments, by configuring a static route on a switch, an extended community attribute support is added to a BGP EVPN RT5 route advertised by the switch to carry original next hop information, thereby obviating the need to establish a BGP neighbor between a virtual forwarding node and a network device, obviating the need for the virtual forwarding node to support a BGP routing protocol, enabling the network device to search for a virtual tunnel endpoint address of the switch to which the virtual forwarding node is actually connected based on the original next hop information carried by the BGP EVPN RT5 route, and avoiding traffic bypassing in the network.

Corresponding to the above routing method applied to the virtual network of the switch, the present specification further provides an embodiment of a routing apparatus configured in the virtual network of the switch, and fig. 9 illustrates a schematic structural diagram of a routing apparatus of the virtual network provided in an embodiment of the present specification. As shown in fig. 9, the apparatus includes:

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

A second routing module 904 may be configured to send a second type of routing information in the virtual network in response to receiving a notification message, the notification message being used for a switch to perceive that any virtual forwarding node is online on a server connected to the switch, the second type of 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.

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, in the virtual network, an RT 5-type route including the first type of route information, where a server interface address initially configured by the virtual forwarding node is carried in the RT 5-type route through a community attribute of the border gateway protocol. The second route sending module may be configured to send, in the virtual network, an RT2 type route including the second type of route information, where a destination network segment in the RT2 type route is set as a server interface address initially configured by any virtual forwarding node, and a next hop is set as a virtual tunnel endpoint address of a switch actually connected to any virtual forwarding node.

In one or more embodiments of the present description, the apparatus may further include: a route configuration module configured to configure a static route, the static route including: the virtual forwarding node 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 the virtual forwarding node. And the route generation module is configured to generate the RT5 type route based on the border gateway protocol according to the static route, a 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 initially configured by a virtual forwarding node.

Corresponding to the above routing method applied to the virtual network of the first network device, this specification further provides an embodiment of a routing apparatus configured in the virtual network of the first network device, and fig. 10 illustrates a schematic structural diagram of a routing apparatus of the virtual network provided in an embodiment of this specification. As shown in fig. 10, the apparatus includes:

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

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

An initial address lookup module 1006, which may be 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;

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

In one or more embodiments of the present description, the apparatus may further include: and the forwarding table writing module can be configured to write the routing entry into the forwarding table so as to perform traffic forwarding based on the forwarding table under the condition that the next hop of the routing entry is determined to be a valid egress interface.

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

the first routing entry generating 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 routing entry generating sub-module may be configured to generate a second type of routing entry according to the second type of routing information, where in the second type of routing entry, a destination network segment is a server interface address initially configured by 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 judgment sub-module can be configured to judge whether the first-type routing information carries a server interface address initially configured by the virtual forwarding node of the destination network segment;

the comparison submodule may be configured to, if the initial address determination submodule determines that the virtual forwarding node is configured to perform the virtual forwarding node, compare the server interface address initially configured by the virtual forwarding node in the destination network segment with the server interface address initially configured by any virtual forwarding node in the second type of routing entry.

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

and the initial address iteration submodule can be configured to set the server interface address initially configured by the virtual forwarding node of the destination network segment as the next hop in the first-class routing entry.

A comparison entry sub-module configured to compare a next hop in the first type of routing entry with a server interface address initially configured by any of the virtual forwarding nodes in the second type of routing entry.

Accordingly, the route generation module 1008 may be configured to, if the comparison entry sub-module determines that the virtual tunnel endpoint addresses of the switches actually connected to any of the virtual forwarding nodes are consistent, set the virtual tunnel endpoint address of the switch to be actually connected to any of the virtual forwarding nodes as the next hop in the first type of route entry, so as to 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 a RT 5-type route including the first type of route information. And the initial address judgment sub-module is used for judging whether a server interface address initially configured by the virtual forwarding node of the target network segment carried by the community attribute based on the border gateway protocol exists in the RT5 type route.

The foregoing is a schematic scheme of the routing apparatus of the virtual network according to this embodiment. It should be noted that the technical solution of the routing apparatus of the virtual network and the technical solution of the routing method of the virtual network belong to the same concept, and details that are not described in detail in the technical solution of the routing apparatus of the virtual network 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 that is provided according to one embodiment of the subject specification. Components of the computing device 1100 include, but are not limited to, a memory 1110 and a processor 1120. The processor 1120 is coupled to the memory 1110 via a bus 1130 and the database 1150 is used to store 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. Access device 1140 may include one or more of any type of network interface (e.g., a Network Interface Card (NIC)) whether wired or wireless, 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 architecture shown in FIG. 11 is for purposes of example only and is not limiting as to the scope of the present description. Those skilled in the art may add or replace other components as desired.

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

The processor 1120 is configured to execute computer-executable instructions, which when executed by the processor, implement the steps of the routing method for the virtual network described above.

The above is an illustrative scheme of a computing device of the present 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 that are not described in detail in the technical solution of the computing device can be referred to the description of the technical solution of the routing method of the virtual network.

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

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

An embodiment of the present specification further provides a computer program, wherein when the computer program is executed in a computer, the computer program causes the computer to execute the steps of the routing method for a virtual network.

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

The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may 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 may also be possible or may be advantageous.

The computer instructions comprise computer program code which may be in the form of source code, object code, an executable file or some intermediate form, or the like. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, U.S. disk, removable hard disk, magnetic diskette, optical disk, computer Memory, read-Only Memory (ROM), random Access Memory (RAM), electrical carrier wave signal, telecommunications signal, and software distribution medium, etc. It should be noted that the computer readable medium may contain content that is subject to appropriate increase or decrease as required by legislation and patent practice in jurisdictions, for example, in some jurisdictions, computer readable media does not include electrical carrier signals and telecommunications signals as is required by legislation and patent practice.

It should be noted that, for the sake of simplicity, the foregoing method embodiments are described as a series of combinations of acts, but it should be understood by those skilled in the art that the embodiments are not limited by the described order of acts, as some steps may be performed in other orders or simultaneously according to the embodiments. Furthermore, those skilled in the art will appreciate that the embodiments described in this specification are presently preferred and that no acts or modules are required in the implementations of the disclosure.

In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.

The preferred embodiments of the present specification disclosed above are intended only to aid in the description of the specification. Alternative embodiments are not exhaustive and do not limit the invention to the precise embodiments described. Obviously, many modifications and variations are possible in light of the teaching of the embodiments of the present disclosure. The embodiments were chosen and described in order to best explain the principles of the embodiments and the practical application, and to thereby enable others skilled in the art to best understand the specification and utilize the specification. The specification is limited only by the claims and their full scope and equivalents.

Claims

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

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

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 is a border gateway protocol based ethernet virtual private network;

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

3. A routing method of a virtual network is applied to a first network device and comprises the following steps:

receiving first type routing information, wherein the first type routing information comprises: a target network segment and a server interface address initially configured by a virtual forwarding node of the target 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 actually connected with the virtual forwarding node;

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 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 the virtual tunnel endpoint address of the switch in the second type of routing information.

4. The method of claim 3, further comprising:

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

5. The method of claim 3, wherein 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 comprises:

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

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

if so, 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.

6. The method of claim 5, said 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 of the virtual forwarding nodes in the second type of routing entry, comprising:

setting the server interface address initially configured by the virtual forwarding node of the destination network segment as the 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;

if the two are consistent, generating a routing entry, including:

and if the virtual forwarding nodes are consistent with the first class of routing entries, setting the virtual tunnel endpoint address of the switch actually connected with any virtual forwarding node as the next hop in the first class of routing entries to obtain the routing entries.

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

the receiving of the first type of routing information includes:

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

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

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

8. A routing method of a virtual network is applied to a switch and comprises the following steps:

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

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

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

the sending of the first type of routing information in the virtual network includes:

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 includes:

and transmitting an RT2 type route containing the second type of 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 a next hop is set as a virtual tunnel endpoint address of a switch actually connected with any virtual forwarding node.

10. The method of claim 9, prior to sending the RT 5-type route containing the first type of routing information in the virtual network, further comprising:

configuring a static route, wherein the static route comprises the following steps: a target network segment and a next hop of the target 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 a target network segment in the RT5 type route is a virtual tunnel endpoint address of the switch, and the community attribute in the RT5 type route carries a server node address initially configured by a virtual forwarding node.

11. A routing device of a virtual network, configured on a first network device, includes:

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

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

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 search module determines that the initial address search 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 routing information.

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

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

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

13. A computing device, comprising:

a memory and a processor;

the memory is configured to store computer-executable instructions, and the processor is configured to execute the computer-executable instructions, which when executed by the processor, implement the steps of the routing method of the virtual network according to 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 a routing method for a virtual network according to any one of claims 3 to 7 or 8 to 10.