CN115134232B

CN115134232B - Virtual router management method, device, system and storage medium

Info

Publication number: CN115134232B
Application number: CN202210786077.0A
Authority: CN
Inventors: 陶缘; 王立坤
Original assignee: Sangfor Technologies Co Ltd
Current assignee: Sangfor Technologies Co Ltd
Priority date: 2022-07-04
Filing date: 2022-07-04
Publication date: 2024-02-23
Anticipated expiration: 2042-07-04
Also published as: CN115134232A

Abstract

The embodiment of the application discloses a virtual router management method, which is applied to virtual router management equipment running a Virtual Router Redundancy Protocol (VRRP) process, and comprises the following steps: acquiring instance configuration information of at least one VRRP instance through the VRRP process to obtain at least one instance configuration information; the VRRP process and each VRRP instance are in communication connection by providing a corresponding communication channel through a virtual extended local area network (VXLAN); performing, by the VRRP process, a management operation on at least one of the VRRP instances based on at least one of the instance configuration information; wherein the management operation includes at least one of: add instance operations, delete instance operations, and modify instance operations. The embodiment of the application also discloses a virtual router management device, a virtual router management system and a virtual router management storage medium.

Description

Virtual router management method, device, system and storage medium

Technical Field

The present disclosure relates to the field of communications technologies, and in particular, to a virtual router management method, device, and storage medium.

Background

With the rapid development of internet communication technology, internet applications are widely used in various fields. In internet applications, local area networks are often employed to provide network services to users. The user terminals in the lan access to the external network usually by configuring a default gateway, if the default gateway device fails at this time, network access of all the user terminals will be interrupted, which may possibly bring unexpected loss to the user, so that the single point failure problem is solved by deploying multiple gateways.

Currently, according to the rules of the virtual routing redundancy protocol (Virtual Router Redundancy Protocol, VRRP), a virtual router group supporting at most 255 VRRP instances in one connected domain, this specification is most demanding in physical networks. However, in a virtual network scenario, up to 1500 virtual router instances may be running on one physical server that provide access to the external network for the connected virtual network. Each virtual router instance is usually maintained by 2 keepalive processes in the running process, so that 3000 keepalive processes are needed in the case of running 1500VRRP instances on a single physical server, which results in very large occupation of kernel scheduling and memory resources.

Disclosure of Invention

In view of this, the embodiments of the present application expect to provide a virtual router management method, apparatus, platform and storage medium, which solve the problem that the core scheduling and memory resources occupy a large amount when the virtual router instance is running and managed at present, and propose a virtual router management method, which manages and controls a plurality of VRRP instances through one VRRP process, so as to effectively reduce the core scheduling pressure and the memory resource occupancy rate.

In order to achieve the above purpose, the technical scheme of the application is realized as follows:

in a first aspect, a virtual router management method applied to a virtual router management device running a virtual router redundancy protocol VRRP process, the method comprising:

acquiring instance configuration information of at least one VRRP instance through the VRRP process to obtain at least one instance configuration information; the VRRP process and each VRRP instance are in communication connection by providing a corresponding communication channel through a virtual extended local area network (VXLAN);

performing, by the VRRP process, a management operation on at least one of the VRRP instances based on at least one of the instance configuration information; wherein the management operation includes at least one of: add instance operations, delete instance operations, and modify instance operations.

Optionally, the method further comprises:

if the virtual router management device is the master device, generating a target address resolution protocol ARP message including a multiprotocol label switching MPLS header corresponding to each VRRP instance through the VRRP process according to a preset time period; wherein, the MPLS header includes VXLAN identifier VNI information allocated by the VXLAN for the corresponding VRRP instance;

sending the target ARP message to a target virtual switch through the VRRP process; wherein the target virtual switch operates in the virtual router management device.

Optionally, the method further comprises:

if the target virtual switch receives the target ARP message, analyzing the target ARP message through the target virtual switch to obtain a first target MPLS header and a first target forwarding message;

storing the first target MPLS header to a first target storage area through the target virtual switch;

and sending the first target forwarding message to a virtual router management device belonging to the standby device through the target virtual switch.

Optionally, if the target virtual switch receives the target ARP packet, the target virtual switch performs parsing processing on the target ARP packet to obtain a first target MPLS header and a first target forwarding packet, including:

If the target virtual switch receives the target ARP message, acquiring the first target MPLS header from the target ARP message through the target virtual switch;

if the first field in the first target MPLS header is the target field, the target virtual switch analyzes the first target MPLS header, stores the tag field in the first target MPLS header into the first storage field of the first target forwarding packet, and stores the time-to-live value field in the first target MPLS header into the second storage field of the first target forwarding packet.

Optionally, the method further comprises:

if the target virtual switch receives a first Hello message sent by the standby equipment, generating a first reference MPLS header by the target virtual switch based on the first Hello message;

adding the first reference MPLS header into the message of the first Hello message through the target virtual switch to obtain a second Hello message;

and sending the second Hello message to the VRRP process through the target virtual switch.

Optionally, if the target virtual switch receives the first Hello packet sent by the standby device, generating, by the target virtual switch, a first reference MPLS header based on the first Hello packet, including:

If the target virtual switch receives a first Hello message sent by the standby equipment, analyzing the first Hello message through the target virtual switch to obtain first data and second data;

storing, by the target virtual switch, the first data into a label field of the first reference MPLS header and the second data into a time-to-live value field of the first reference MPLS header;

and setting a flow grade field in the first reference MPLS header as target identification information through the target virtual switch to obtain the first reference MPLS header.

Optionally, the method further comprises:

if the VRRP process receives the second Hello message, analyzing the second Hello message through the VRRP process to obtain a second target MPLS header and a second target forwarding message;

storing the second target MPLS header to a second target storage area through the VRRP process;

determining a target VRRP instance based on the second target forwarding message through the VRRP process;

and distributing the second target forwarding message to the target VRRP instance through the VRRP process.

Optionally, the method further comprises:

If the virtual router management equipment is the main equipment, monitoring a physical network card of the virtual router management equipment through the VRRP process;

if the VRRP process does not monitor the physical signal of the physical network card, adjusting the operation priority of at least one VRRP instance from the first priority to the second priority through the VRRP process; wherein the priority level of the second priority is lower than the priority level of the first priority.

Optionally, the VRRP process communicates with the target virtual switch through at least one communication port.

In a second aspect, a virtual router management apparatus, the apparatus comprising: memory, processor, and communication bus; wherein:

the memory is used for storing executable instructions;

the communication bus is used for realizing communication connection between the processor and the memory;

the processor is configured to execute a virtual router management program stored in the memory, and implement the steps of the virtual router management method according to any one of the foregoing.

In a third aspect, a virtual route management system, the system comprising at least two virtual route management devices, at least two of the virtual route management devices, determining one master device and at least one standby device from the at least two virtual route management devices by master election; wherein:

At least two of the virtual router management devices are configured to implement the steps of the virtual router management method according to any of the above.

In a fourth aspect, a storage medium having stored thereon a virtual router management program that, when executed by a processor, implements the steps of the virtual router management method according to any of the preceding claims.

The virtual router management method, the device, the system and the storage medium provided by the embodiment of the application acquire the instance configuration information of at least one VRRP instance through one VRRP process which is only operated in the virtual router management device, execute management operation on the at least one VRRP instance through the VRRP process based on the at least one instance configuration information after obtaining the at least one instance configuration information, and distribute the at least one VRRP instance to the request device through the VRRP process according to the route acquisition request so as to provide router service for the request device through the VRRP instance. In this way, the virtual router management device performs allocation management control on the VRRP instances managed by the virtual router management device through one VRRP process, solves the problem of large core scheduling and memory resource occupation caused by the operation management of the existing virtual router instances, and provides a virtual router management method.

Drawings

Fig. 1 is a schematic flow chart of a virtual router management method according to an embodiment of the present application;

fig. 2 is a flow chart of another virtual router management method according to an embodiment of the present application;

fig. 3 is a flow chart of another virtual router management method according to an embodiment of the present application;

fig. 4 is a flowchart of a virtual router management method according to another embodiment of the present application;

FIG. 5 is a flowchart illustrating another virtual router management method according to another embodiment of the present disclosure;

FIG. 6 is a flowchart illustrating a virtual router management method according to another embodiment of the present application;

FIG. 7 is a schematic diagram of a router high availability design architecture according to an embodiment of the present disclosure;

fig. 8 is a schematic diagram of a message structure with an MPLS header according to an embodiment of the present application;

FIG. 9 is a schematic diagram of a connection between a virtual switch and a single VRRP process provided by an embodiment of the present application;

fig. 10 is a schematic structural diagram of a virtual router management device according to an embodiment of the present application;

fig. 11 is a schematic structural diagram of a virtual router management system according to an embodiment of the present application.

Detailed Description

It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the present application.

An embodiment of the present application provides a virtual router management method applied to a virtual router management device for running a virtual router redundancy protocol VRRP process, referring to fig. 1, the method includes the steps of:

step 101, obtaining instance configuration information of at least one VRRP instance through a VRRP process, and obtaining the instance configuration information.

And the VRRP process and each VRRP instance are in communication connection by providing a corresponding communication channel through the virtual extended local area network VXLAN.

In the embodiment of the application, the virtual router management device may be a physical server, which may run more than about 1500 virtual routers, where each VRRP instance uniquely corresponds to a virtual border router. The user can input the instance configuration information of the corresponding VRRP instance by operating the VRRP process.

Step 102, executing management operation on at least one VRRP instance based on at least one instance configuration information through the VRRP process.

Wherein the management operation includes at least one of: add instance operations, delete instance operations, and modify instance operations.

In the embodiment of the application, after the VRRP process receives at least one instance configuration information, according to the configuration requirement in the instance configuration information, a corresponding instance management operation is executed. For example, when the instance configuration information indicates that the instance operation is added, the VRRP process creates a VRRP instance matched with the instance configuration information according to the instance configuration information; for example, when the instance configuration information indicates that the instance is modified, the VRRP process modifies the relevant parameters of the corresponding VRRP instance in the instance configuration information; for example, when the instance configuration information indicates that the instance is deleted, the VRRP process deletes the corresponding VRRP instance in the instance configuration information. At least one VRRP instance managed by the VRRP process can be displayed on a display interface corresponding to the virtual router management device, the displayed content can be the number of VRRP instances managed by the VRRP process, and further, the VRRP process can also comprise specific configuration information such as identification information of the VRRP instances managed by the VRRP process.

In this way, the messages leaving the virtual machine are not confused in the internet because the messages are packaged in different virtual expansion local area network (Virtual Extensible Local Area Network, VXLAN) tunnels when leaving the virtual machine, namely, the messages are isolated through the VXLAN, and because the VXLAN identifier (VXLAN Network Identifier, VNI) of the VXLAN can support 24 different values of 2, a single virtual router management device also supports 24 VRRP instances of 2 at most, the limitation of 255 instances in the VRRP protocol is relieved, the capacity expansion requirement is fully met, and the management and control of so many VRRP instances are carried out through one VRRP process, so that the pressure of kernel scheduling and the occupancy rate of memory resources are effectively reduced.

According to the virtual router management method provided by the embodiment of the application, the instance configuration information of at least one VRRP instance is obtained through one VRRP process which is only operated in the virtual router management equipment, after the instance configuration information is obtained, the management operation is executed on the at least one VRRP instance through the VRRP process based on the instance configuration information, and the at least one VRRP instance is distributed to the request equipment through the VRRP process according to the route obtaining request, so that router service is provided for the request equipment through the VRRP instance. In this way, the virtual router management device performs allocation management control on the VRRP instances managed by the virtual router management device through one VRRP process, solves the problem of large core scheduling and memory resource occupation caused by the operation management of the existing virtual router instances, and provides a virtual router management method.

Based on the foregoing embodiments, embodiments of the present application provide a virtual router management method, as shown in fig. 2, which is applied to a virtual router management device running a virtual router redundancy protocol VRRP process, the method including the steps of:

Step 201, obtaining instance configuration information of at least one VRRP instance through a VRRP process, and obtaining the at least one instance configuration information.

In this embodiment of the present application, when the VRRP process obtains the instance configuration information of at least one VRRP instance, the method may be specifically implemented by a registration mechanism of an open virtual switch database (OpenvSwitch Database, OVSDB), that is, after the user writes the instance configuration information of the VRRP instance into the OVSDB through a local control plane, the VRRP process registers on the OVSDB server side, the VRRP process may monitor a change of the instance configuration information, so that the VRRP process may obtain the changed at least one instance configuration information from the OVSDB.

Step 202, performing, by the VRRP process, a management operation on at least one VRRP instance based on the at least one instance configuration information.

In the embodiment of the application, according to the obtained at least one instance configuration information, the VRRP process performs management operations such as instance adding operation, instance deleting operation or instance modifying operation, which are matched with the VRRP instance corresponding to each instance configuration information.

Thus, when receiving a route allocation request sent by a route request device, the VRRP process responds to the route allocation request and allocates a VRRP instance for the route request device from at least one unallocated VRRP instance. The route request device may be a virtual device, or may be an access device that needs to access an external network, for example, a computer device, an intelligent terminal device, or the like.

Step 203, if the virtual router management device is a master device, generating a target address resolution protocol ARP message corresponding to each VRRP instance and including a multiprotocol label switching MPLS header according to a preset time period through a VRRP process.

The MPLS header includes VXLAN identification VNI information allocated by VXLAN for a corresponding VRRP instance.

In the embodiment of the application, the master device is a router device which is determined to be used for providing a network port for communication with the internet from a router high-availability architecture according to a master-slave switching strategy, and the router device is a virtual router which virtualizes a plurality of routers. The preset time period is a time period empirical value obtained according to a large number of experiments, and can be correspondingly adjusted according to actual conditions. Because the virtual router management device is the main device, it needs to send ARP messages outwards at regular time according to preset time period for informing the standby device of the normal working information, so the main device generates the target ARP messages including MPLS heads corresponding to each VRRP instance managed by the main device through the VRRP process. Because the MPLS header includes VXLAN identification VNI information distributed by VXLAN for the corresponding VRRP instance, different VRRP instances can be identified through different VNI information, and a single virtual router management device can identify and manage 24 VRRP instances at most.

Step 204, the target ARP message is sent to the target virtual switch through the VRRP process.

The target virtual switch operates in the virtual router management device.

In the embodiment of the application, the VRRP process sends the generated target ARP message to the target virtual switch, where the target virtual switch is a switch that is in communication connection with the VRRP process and is used for conducting drainage allocation on the corresponding traffic. In this way, the target virtual switch may send the target ARP message to the standby device to cause the standby device to determine that the virtual router management device is still the master device.

Based on the foregoing embodiments, in other embodiments of the present application, referring to fig. 3, the virtual router management apparatus is further configured to perform steps 205 to 207:

step 205, if the target virtual switch receives the target ARP message, the target virtual switch analyzes the target ARP message to obtain the first target MPLS header and the first target forwarding message.

In the embodiment of the application, after receiving the target ARP message, the target virtual switch in the virtual router management device analyzes the target ARP message, and determines to obtain the first target MPLS header and the first target forwarding message. The first target forwarding message is notification message information for indicating the virtual router management device as the master device.

Step 206, storing the first target MPLS header to the first target storage area through the target virtual switch.

In the embodiments of the present application. The target virtual switch stores the first target MPLS header to the first target storage area so that subsequent traffic steering may be performed according to the first target MPLS header. The first target storage area is a storage area where the target virtual switch can access data storage.

Step 207, a first target forwarding message is sent to a virtual router management device belonging to the standby device through the target virtual switch.

In the embodiment of the application, the target virtual switch sends the first target forwarding message to the virtual router management device belonging to the standby device, so that the virtual router management device belonging to the standby device determines that the main device still works normally, and the main device does not need to perform the preemption operation. The main device is a virtual router management device for realizing the function of the main router, and the standby device is a device for executing the preemption function when the main device fails and can be used as the main device for providing the routing function, so that replacement devices can be rapidly generated when the main device fails, and the normal operation of the communication network is ensured. When the target virtual switch communicates with the virtual router management device belonging to the standby device, the communication is realized through a virtual expansion local area network (Virtual Extensible Local Area Network, VXLAN), and the first target forwarding message sent by the target virtual switch is packaged in different VXLAN tunnels, so that confusion in the network cannot occur, and therefore, the VXLAN plays an isolating role, so that the virtual router management device belonging to the main device can support 24 VRRP instances to the maximum extent of 2, the limitation of 255 VRRP instances in the primary VRRP protocol is relieved, and the capacity expansion requirement is fully met.

Based on the foregoing embodiments, in other embodiments of the present application, step 205 may be implemented by steps 205 a-205 b:

step 205a, if the target virtual switch receives the target ARP message, the target virtual switch obtains the first target MPLS header from the target ARP message.

In this embodiment of the present application, the first target MPLS header is stored in the header of the target ARP packet, so the target virtual switch performs parsing processing on the header of the target ARP packet, and may obtain the first target MPLS header.

Step 205b, if the first field in the first target MPLS header is the target field, resolving the first target MPLS header by the target virtual switch, storing the label field in the first target MPLS header in the first storage field of the first target forwarding message, and storing the lifetime value field in the first target MPLS header in the second storage field of the first target forwarding message.

In the embodiment of the present application, the target field is a field for indicating that the message type is an ARP message. When the first field in the first target MPLS header is the target field, the target virtual switch parses the first target MPLS header, obtains a LABEL (LABEL) field from the first target MPLS header, stores the LABEL field obtained in the first target MPLS header into a first storage field of the first target forwarding message, and stores a Time To Live (TTL) value field in the first target MPLS header into a second storage field of the first target forwarding message, so that the first target forwarding message can be obtained. The first storage field of the first target forwarding packet may be, for example, a field corresponding to 20 bits of 0 to 19 bits of the first target forwarding packet, and the second storage field may be a field corresponding to 8 bits of 20 to 27 bits of the first target forwarding packet. In an actual application scenario, the upper 4 bits in the second storage field may be set to 0.

Based on the foregoing embodiment, in other embodiments of the present application, after the virtual router management device performs step 202, referring to fig. 4, the virtual router management device is further configured to perform steps 208 to 210:

step 208, if the target virtual switch receives the first Hello message sent by the standby device, generating, by the target virtual switch, a first reference MPLS header based on the first Hello message.

In the embodiment of the present application, the first Hello packet is a packet for maintaining a neighbor state. When the target virtual switch receives a first Hello message sent by the standby device, the virtual router management device belonging to the main device analyzes the first Hello message through the target virtual switch to generate a first reference MPLS header, so as to realize the setting of a flow table.

Step 209, adding the first reference MPLS header to the first Hello packet through the target virtual switch, to obtain a second Hello packet.

In the embodiment of the application, the target virtual switch adds the generated first reference MPLS header to the message of the first Hello message to obtain the second Hello message, so that the route identity information of the specific VRRP instance is identified between the target virtual switch and the VRRP process through the information in the MPLS header.

Step 210, sending the second Hello message to the VRRP process through the target virtual switch.

In the embodiment of the application, the target virtual switch sends the second Hello message to the VRRP process, so that the VRRP process sends the second Hello message to the corresponding VRRP instance.

Based on the foregoing embodiments, in other embodiments of the present application, step 208 may be implemented by steps 208 a-208 c:

step 208a, if the target virtual switch receives the first Hello message sent by the standby device, the target virtual switch analyzes the first Hello message to obtain first data and second data.

In the embodiment of the application, after receiving the first Hello message sent by the standby device, the target virtual switch analyzes the first Hello message to obtain first data and second data. The first data is 20 bits of data from 0 th bit to 19 th bit in metadata of the first Hello message, and the second data is 8 bits of data from 20 th bit to 27 th bit in metadata of the first Hello message.

Step 208b, storing, by the target virtual switch, the first data into a label field of the first reference MPLS header and the second data into a lifetime value field of the first reference MPLS header.

And step 208c, setting a traffic class field in the first reference MPLS header as target identification information through the target virtual switch to obtain the first reference MPLS header.

In the embodiments of the present application. The destination identification information is type identification information for identifying the first Hello message as an internet protocol (Internet Protocol, IP) message. For example, the type identification information of the IP packet may be denoted as 1, and the type identification information of the arp packet may be denoted as 2.

Based on the foregoing embodiments, in other embodiments of the present application, referring to fig. 5, after performing step 210, the virtual router management device is further configured to perform steps 211 to 214:

step 211, if the VRRP process receives the second Hello message, analyzing the second Hello message by the VRRP process to obtain a second target MPLS header and a second target forwarding message.

In this embodiment of the present application, after the VRRP process receives the second Hello packet sent by the target virtual switch, the second Hello packet is parsed, so as to obtain a second target MPLS header and a second target forwarding packet. The VRRP process analyzes the second Hello message, acquires a second target MPLS header from the message header of the second Hello message, and removes the second target MPLS header in the second Hello message to acquire a second target forwarding message.

Step 212, storing the second target MPLS header to the second target storage area through the VRRP process.

In the embodiment of the application, the VRRP process stores the second target MPLS header in the second target storage area, so that when the corresponding VRRP instance returns a message, the second target MPLS header is added to the message returned by the corresponding VRRP instance and forwarded to the target virtual switch, so that the message information sent by the VRRP instance is distinguished between the VRRP process and the target virtual switch through the MPLS header.

Step 213, determining the target VRRP instance based on the second target forwarding message through the VRRP process.

In the embodiment of the application, the VRRP process analyzes the second target forwarding message, determines to obtain the route identity information of the corresponding VRRP instance, and thus, can determine to obtain the target VRRP instance according to the determined route identity information.

Step 214, distributing the second target forwarding message to the target VRRP instance through the VRRP process.

In the embodiment of the application, the VRRP process distributes the second target forwarding message to the target VRRP instance, so that the target VRRP instance responds to the second target forwarding message.

Based on the foregoing embodiments, in other embodiments of the present application, referring to fig. 6, the virtual router management apparatus is further configured to perform steps 215 to 216:

Step 215, if the virtual router management device is the master device, monitoring the physical network card of the virtual router management device through the VRRP process.

In this embodiment of the present application, when the virtual router management device is a master device, the VRRP process detects a network card signal of a physical network card corresponding to the virtual router management device, where the VRRP process may be specifically implemented by using an OVSDB server, that is, the VRRP process registers the network card signal of the monitoring physical network card through the OVSDB server.

Step 216, if the VRRP process does not monitor the physical signal of the physical network card, the VRRP process adjusts the operation priority of at least one VRRP instance from the first priority to the second priority.

Wherein the priority level of the second priority is lower than the priority level of the first priority.

In the embodiment of the application, when the VRRP process does not monitor the physical signal of the physical network card, indicating that the physical network card is aged, at this time, the VRRP process adjusts the operation priority of at least one corresponding VRRP instance from the first priority to the second priority, that is, the VRRP process traverses each VRRP instance corresponding to the physical network card, and performs degradation processing on each VRRP instance. In this way, the switching of the primary equipment and the standby equipment can be triggered, and the availability of the communication network is effectively ensured. The first priority is the highest priority level.

Based on the foregoing embodiments, in other embodiments of the present application, communication is performed between the VRRP-process and the target virtual switch through at least one communication port that is provided.

In this embodiment of the present application, when at least two communication ports are provided between the VRRP process and the target virtual switch for communication, at least one VRRP instance currently managed in the VRRP process may be grouped into VRRP instances with the same number of groups as the at least two communication ports, and then the message information corresponding to each group of VRRP instances is transmitted through the corresponding communication port, or each communication port is configured to send the message information of the VRRP instance corresponding to the corresponding route identity information. For example, when two communication ports, namely, port 1 and port 2, are set between the VRRP process and the target virtual switch, the currently managed VRRP process is configured to group the 4 VRRP instances, namely, VRRP instance 3 and 254.89.81.254 of VRRP instance 2 and 128.89.81.221 of VRRP instance 1 and 126.89.81.221 of 11.89.81.1, respectively, into 2 groups, one group is configured to be VRRP instance 1 and VRRP instance 2, the other group is configured to be VRRP instance 3 and VRRP instance 4, and the corresponding message information of VRRP instance 1 and VRRP instance 2 may be transmitted through port 1, the message information of VRRP instance 3 and VRRP instance 4 may be transmitted through port 2, or when the message information corresponding to VRRP instances of VRRP instance 2 and VRRP instance 3 of which route identification information is set to be 0.0.0.0-123.123.123.123 is configured to be transmitted through port 1, the message information corresponding to VRRP instances of 123.123.123.124-255.255.255.255 is correspondingly, the message information corresponding to VRRP instance 1 may be transmitted through port 1, and the message information corresponding to VRRP instance 2 and VRRP instance 4 may be transmitted through port 2.

Based on the foregoing embodiments, in other embodiments of the present application, a router high availability design architecture schematic is provided, and referring to fig. 7, the router high availability design architecture schematic includes: the system comprises the external Internet, a physical server 1, a physical server 2 and a physical server 3; wherein, at least one virtual switch and one VRRP process are operated in the physical server 1 and the physical server 2, the VRRP process is used for managing and controlling N VRRP instances, N is an integer greater than or equal to 1, the value of N can be different for different physical servers, and M virtual machines are operated in the physical server 3. Message data transmission is performed among the physical server 1, the physical server 2 and the physical server 3 through an internal network VXLAN tunnel.

The VRRP process manages at least one VRRP instance by distinguishing it by router identification information (Identity document, ID). The router ID of each VRRP instance is stored in the configuration information of the VRRP instance, and also exists in a packet header of the incoming and outgoing VRRP process, that is, a 4-byte MPLS header that is preceded by an ethernet packet, and is used for transferring the router ID between the VRRP process and a virtual switch (Openvswitch) bridge.

The virtual rtrid of the protocol in the Hello message of different VRRP examples is 1, but when the message leaves the Openvswitch, the Openvswitch encapsulates the message in different VXLAN tunnels, so that the Hello messages sent by different VRRP examples are not confused in the network, because the VXLAN plays an isolating role.

When the message transmission is performed between the VRRP process and the Openvswitch bridge, the VRRP process and the Openvswitch bridge realize message receiving and transmitting in a socket mode.

The specific procedure for the VRRP process to obtain the configuration information for each VRRP instance may be: the local control plane writes the configuration information of each VRRP instance into the OVSDB, thus, after registering with the OVSDB server, the VRRP process monitors the change of the configuration information of the VRRP instance in the OVSDB server to generate the corresponding VRRP instance, or performs deletion processing or modification on the corresponding VRRP instance, and each VRRP instance uniquely corresponds to a virtual border router. Illustratively, the configuration information for a VRRP instance may be as follows:

in fig. 6, when the VRRP instance managed by the VRRP process running in the physical server 1 is a VRRP master, the corresponding physical server 1 may be referred to as a master, and thus, the VRRP instance managed by the VRRP process running in the physical server 2 is a VRRP standby instance, and the corresponding physical server 2 is a standby device. The change of the primary and standby states of the VRRP instance is strictly executed according to a series of files (Request For Comments, RFC) defined by numbering in the VRRP protocol, and the primary instance and the standby instance can be obtained by comparing priority fields in a Hello message sent by the VRRP instance. The VRRP process registers and monitors the change of the connection state of the physical network card corresponding to the VRRP master instance with the OVSDB server, i.e. whether the physical signal of the physical network card corresponding to the VRRP master instance is lost, which can be specifically completed by the network interface driver of the linux kernel system. When the local control plane monitors that the physical signals of the physical network cards corresponding to the VRRP main instances are lost, the local control plane can inform the VRRP process, the VRRP process traverses the VRRP main instances associated with the physical network cards corresponding to the VRRP main instances, and the operation priority of the VRRP main instances is reduced, so that the master-slave switching is triggered. After the primary-standby switching is performed, the VRRP process generates an ARP message for the new VRRP primary instance, and sends the ARP message to the Openvswitch so that the Openvswitch enters the virtual network and the physical network to guide the traffic to the new VRRP primary instance.

The foregoing schematic message structure with MPLS header may refer to fig. 8, where the MPLS header includes a label value field, a priority field, a lifetime value field, and a stack bottom identification bit field, where the label value field is used to store 0-19 bits of metadata of a message, the priority field is used to store a message type, and the lifetime value field is used to store 20-27 bits of metadata of the message. When the message type is an IP message, the message type can be identified by 1, and when the message type is an ARP message, the message type can be identified by 2.

Correspondingly, when the VRRP process receives the Hello message sent by the virtual machine switch, the flow table corresponding to the corresponding operation flow is shown as the following code:

ovs-ofctl add-flow anet-br table＝0,nw_proto＝112,\

actions＝push_mpls:0x8847,\

move:OXM_OF_METADATA[0..19]-\>mpls_label,\

move:OXM_OF_METADATA[20..27]-\>mpls_ttl,load:0x1-\>mpls_tc,\

output: "VRRP service Port"

The meaning of the above code is: matching is performed on the first flow table of the virtual machine switch bridge anet-br, if a message (nw_proto=112) of which the IP protocol is VRRP is received, a 4-byte MPLS header is added to the message header, wherein 0-19 bits in metadata of the message sent by the virtual switch are stored in a tag value field in the MPLS header, 20 bits in total are stored in a lifetime value field in the MPLS header, 8 bits (always 0 in high 4 bits) in total are stored in metadata of the message sent by the virtual switch, a priority field in the MPLS header stores a network layer protocol type, 1 indicates that the message is an IP message, and then the message after the MPLS header is added is sent to a VRRP service port. It should be noted that, the purpose of selecting the first flow table from the flow tables is to make a judgment as soon as possible by the virtual switch, so as to improve the processing efficiency.

When the VRRP process sends a Hello message to the virtual switch, the flow table corresponding to the corresponding operation flow is shown as the following code:

ovs-offctl add-flow-br in_port= "VRRP service port", mpls, mpls_tc=1,

actions＝move:mpls_label-\>OXM_OF_METADATA[0..19],

move:mpls_ttl-\>OXM_OF_METADATA[20..27],

pop_mpls:0x0800,resubmit(,3)

the meaning of the above code is: on the VRRP service port of the bridge anet-br of the virtual switch, if the packet encapsulated by the MPLS is received and the priority field in the MPLS header is 1, storing the data stored in the tag value field in the MPLS header to the 0-19 bits of the metadata of the packet in the virtual switch, storing the data stored in the lifetime value field in the MPLS header to the 20-27 bits of the metadata of the packet in the virtual switch, then removing the MPLS header, notifying the packet of the inner layer of the virtual switch to be an IP packet, and then sending the packet data generated after removing the MPLS header to a subsequent packet pipeline.

When the VRRP process sends an ARP message to the virtual switch, the flow table corresponding to the corresponding operation flow is shown as the following code:

ovs-offctl add-flow-br in_port= "VRRP service port", mpls, mpls_tc=2,

actions＝move:mpls_label-\>OXM_OF_METADATA[0..19],

move:mpls_ttl-\>OXM_OF_METADATA[20..27],

pop_mpls:0x0806,resubmit(,3)

the meaning of the above code is: on the VRRP service port of the virtual machine bridge anet-br, if the packet encapsulated by MPLS is received and the priority field in the MPLS header is 2, storing the data stored in the tag value field in the MPLS header to the bits 0-19 of the metadata of the packet in the virtual switch, storing the data stored in the lifetime value field in the MPLS header to the bits 20-27 of the metadata of the packet in the virtual switch, then removing the MPLS header, notifying the packet at the inner layer of the virtual switch to be an ARP packet, and then sending the packet data generated after removing the MPLS header to a subsequent packet pipeline.

As shown in fig. 6, the virtual switch and the VRRP-process are implemented by one communication port, and referring to fig. 9, the virtual switch and the VRRP-process may also be implemented by at least two communication ports.

It should be noted that, in this embodiment, the explanation of the same steps or concepts as those in other embodiments may refer to the descriptions in other embodiments, and are not repeated here.

Based on the foregoing embodiments, the present embodiment provides a virtual router management apparatus 3, and the virtual router management apparatus 3 may be applied to the embodiments corresponding to fig. 1 to 6, and as shown with reference to fig. 10, the virtual router management apparatus 3 includes: a memory 31, a processor 32, and a communication bus 33; wherein:

a memory 31 for storing executable instructions;

a communication bus 33 for enabling a communication connection between the processor and the memory;

a processor 32 for executing the virtual router management program stored in the memory 31 to realize the steps of:

acquiring instance configuration information of at least one VRRP instance through a VRRP process to obtain the at least one instance configuration information; the VRRP process and each VRRP instance are in communication connection by providing a corresponding communication channel through a virtual extended local area network (VXLAN);

performing, by the VRRP process, a management operation on the at least one VRRP instance based on the at least one instance configuration information; wherein the management operation includes at least one of: adding instance operations, deleting instance operations and modifying instance operations;

and distributing at least one VRRP instance to the request equipment through the VRRP process according to the route acquisition request so as to provide router service for the request equipment through the VRRP instance.

In other embodiments of the present application, the processor is further configured to perform the steps of:

if the virtual router management equipment is the main equipment, generating a target Address Resolution Protocol (ARP) message which corresponds to each VRRP instance and comprises a multiprotocol label switching (MPLS) head through a VRRP process according to a preset time period; wherein, the MPLS header includes VXLAN identification VNI information distributed by VXLAN for the corresponding VRRP instance;

sending a target ARP message to a target virtual switch through a VRRP process; the target virtual switch operates in the virtual router management device.

storing the first target MPLS header to the first target storage area through the target virtual switch;

and sending the first target forwarding message to the virtual router management equipment belonging to the standby equipment through the target virtual switch.

In other embodiments of the present application, if the target virtual switch receives the target ARP message, the processor performs the step of analyzing the target ARP message by using the target virtual switch, and when obtaining the first target MPLS header and the first target forwarding message, the step may be implemented by:

If the target virtual switch receives the target ARP message, acquiring a first target MPLS header from the target ARP message through the target virtual switch;

if the first field in the first target MPLS header is the target field, analyzing the first target MPLS header by the target virtual switch, storing the tag field in the first target MPLS header into the first storage field of the first target forwarding message, and storing the lifetime value field in the first target MPLS header into the second storage field of the first target forwarding message.

if the target virtual switch receives a first Hello message sent by the standby equipment, generating a first reference MPLS header based on the first Hello message through the target virtual switch;

In other embodiments of the present application, the processor executes the step of, if the target virtual switch receives the first Hello message sent by the standby device, generating, by the target virtual switch, a first reference MPLS header based on the first Hello message, and is further configured to execute the following steps:

If the target virtual switch receives a first Hello message sent by the standby equipment, the target virtual switch analyzes the first Hello message to obtain first data and second data;

and setting a traffic class field in the first reference MPLS header as target identification information through the target virtual switch to obtain the first reference MPLS header.

storing the second target MPLS header to the second target storage area through the VRRP process;

if the virtual router management equipment is the main equipment, monitoring a physical network card of the virtual router management equipment through a VRRP process;

In other embodiments of the present application, communication is performed between the VRRP-process and the target virtual switch through at least one communication port that is provided.

It should be noted that, in the embodiment, the information interaction process between the units and the modules may refer to the information interaction process described in the foregoing method embodiment, which is not described herein again.

The virtual router management device provided by the embodiment of the application acquires the instance configuration information of at least one VRRP instance through one VRRP process which is uniquely operated in the virtual router management device, executes management operation on the at least one VRRP instance through the VRRP process based on the at least one instance configuration information after the at least one instance configuration information is obtained, and distributes the at least one VRRP instance to the request device through the VRRP process according to the route acquisition request so as to provide router service for the request device through the VRRP instance. In this way, the virtual router management device performs allocation management control on the VRRP instances managed by the virtual router management device through one VRRP process, solves the problem of large core scheduling and memory resource occupation caused by the operation management of the existing virtual router instances, and provides a virtual router management method.

Based on the foregoing embodiments, the present embodiment provides a virtual router management system 6, where the virtual router management system 4 may be applied to the embodiments corresponding to fig. 1 to 6, and referring to fig. 11, the virtual router management system includes at least two virtual router management devices, where one primary device 41 and at least one standby device 42 are determined from the at least two virtual router management devices through primary election; wherein:

at least two virtual router management devices are used to implement the virtual router management method provided in the embodiments corresponding to fig. 1 to 6, and are not described herein.

Based on the foregoing embodiments, embodiments of the present application provide a computer readable storage medium, simply referred to as a storage medium, where one or more virtual router management programs are stored, and the one or more virtual router management programs may be executed by one or more processors, so as to implement the virtual router management method provided in the embodiments corresponding to fig. 1 to 6, which is not described herein again.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

The foregoing embodiment numbers of the present application are merely for describing, and do not represent advantages or disadvantages of the embodiments.

From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) comprising several instructions for causing a terminal (which may be a mobile phone, a computer, … …, an air conditioner, or a network communication link device, etc.) to perform the method described in the embodiments of the present application.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

The foregoing description is only of the preferred embodiments of the present application, and is not intended to limit the scope of the claims, and all equivalent structures or equivalent processes using the descriptions and drawings of the present application, or direct or indirect application in other related technical fields are included in the scope of the claims of the present application.

Claims

1. A virtual router management method, the method being applied to a virtual router management device running a virtual router redundancy protocol VRRP process, the method comprising:

2. The method according to claim 1, wherein the method further comprises:

3. The method according to claim 2, wherein the method further comprises:

4. The method of claim 3, wherein if the target virtual switch receives the target ARP message, analyzing the target ARP message by the target virtual switch to obtain a first target MPLS header and a first target forwarding message, includes:

5. The method according to claim 2, wherein the method further comprises:

6. The method of claim 5, wherein if the target virtual switch receives a first Hello message sent by a standby device, generating, by the target virtual switch, a first reference MPLS header based on the first Hello message, comprising:

7. The method of claim 5, wherein the method further comprises:

8. The method according to claim 1, wherein the method further comprises:

9. The method according to any one of claims 2 to 7, wherein communication between the VRRP-process and the target virtual switch is performed through at least one communication port provided.

10. A virtual router management apparatus, the apparatus comprising: memory, processor, and communication bus; wherein:

the memory is used for storing executable instructions;

the processor is configured to execute a virtual router management program stored in the memory, and implement the steps of the virtual router management method according to any one of claims 1 to 9.

11. A virtual routing management system, said system comprising at least two virtual routing management devices, at least two of said virtual routing management devices, from which a primary device and at least one backup device are determined by primary election; wherein:

at least two of said virtual router management devices for implementing the steps of the virtual router management method according to any of claims 1 to 9.

12. A storage medium having stored thereon a virtual router management program which when executed by a processor performs the steps of the virtual router management method according to any of claims 1 to 9.