Nothing Special   »   [go: up one dir, main page]

CN114157606B - Virtual network element device switching method, device and storage medium - Google Patents

Virtual network element device switching method, device and storage medium Download PDF

Info

Publication number
CN114157606B
CN114157606B CN202111501300.4A CN202111501300A CN114157606B CN 114157606 B CN114157606 B CN 114157606B CN 202111501300 A CN202111501300 A CN 202111501300A CN 114157606 B CN114157606 B CN 114157606B
Authority
CN
China
Prior art keywords
virtual network
network element
element device
virtual
switch
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202111501300.4A
Other languages
Chinese (zh)
Other versions
CN114157606A (en
Inventor
王展耀
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Ruijie Networks Co Ltd
Original Assignee
Ruijie Networks Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Ruijie Networks Co Ltd filed Critical Ruijie Networks Co Ltd
Priority to CN202111501300.4A priority Critical patent/CN114157606B/en
Publication of CN114157606A publication Critical patent/CN114157606A/en
Application granted granted Critical
Publication of CN114157606B publication Critical patent/CN114157606B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic control in data switching networks
    • H04L47/10Flow control; Congestion control
    • H04L47/12Avoiding congestion; Recovering from congestion
    • H04L47/125Avoiding congestion; Recovering from congestion by balancing the load, e.g. traffic engineering
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00Packet switching elements
    • H04L49/25Routing or path finding in a switch fabric
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00Packet switching elements
    • H04L49/55Prevention, detection or correction of errors
    • H04L49/557Error correction, e.g. fault recovery or fault tolerance
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00Packet switching elements
    • H04L49/70Virtual switches

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The embodiment of the disclosure provides a virtual network element device switching method, device and storage medium, wherein the method comprises the following steps: respectively constructing boundary gateway protocol neighbor relations between at least two virtual network element devices and access switches corresponding to a physical network; determining a static route corresponding to each virtual network element device; determining a target virtual network element device and at least one standby virtual network element device in at least two virtual network element devices based on a load balancing metric value corresponding to each virtual network element device; each static route is redistributed to the access switch based on the border gateway protocol neighbor relation so as to switch traffic borne by the target virtual network element device to any one of the at least one standby virtual network element device through the access switch.

Description

Virtual network element device switching method, device and storage medium
Technical Field
The disclosure relates to the technical field of cloud data center communication, in particular to a virtual network element device switching method, device and storage medium.
Background
In the public cloud data center which is common at present, virtual network element equipment such as software load balancing, software NAT gateway, software firewall and the like which provide network application services for tenants or users are generally deployed on a physical server of a computing resource pool in the form of a KVM virtual machine, and one or more virtual network element equipment on a single physical server can be deployed according to the hardware configuration condition of the server.
In the process of implementing the inventive concept of the present disclosure, the inventor found that there are at least the following problems in the related art: because the number of the virtual network element devices is large, more operation resources are occupied when the virtual network element devices are detected in the related technology, the service flow of the whole network is improved, the normal operation of tenant service is influenced, and the use experience of the tenant is poor.
Disclosure of Invention
The embodiment of the disclosure provides a virtual network element device switching method, device and storage medium, which are used for realizing rapid convergence of virtual network element devices.
In a first aspect, an embodiment of the present disclosure provides a method for switching a virtual network element device, where the method includes:
Respectively constructing boundary gateway protocol neighbor relations between at least two virtual network element devices and access switches corresponding to a physical network, wherein each virtual network element device is respectively deployed in different resource nodes, each resource node is internally provided with a virtual switch connected with the virtual network element device, the physical network is loaded with the virtual network, and the resource nodes are used for connecting the physical network and the virtual network;
Determining a static route corresponding to each piece of virtual network element equipment, wherein the next hop of each static route is an internet protocol address of the virtual switch corresponding to each piece of virtual network element equipment;
Redistributing each of the static routes to the access switch based on the border gateway protocol neighbor relation, wherein the static routes each correspond to a load balancing metric value;
And determining a target virtual network element device and at least one standby virtual network element device from the at least two virtual network element devices based on the load balancing metric value corresponding to each virtual network element device, so as to switch the service born by the target virtual network element device to any one of the at least one standby virtual network element device through the access switch.
According to an embodiment of the present disclosure, the constructing border gateway protocol neighbor relationships between at least two virtual network element devices and access switches corresponding to a physical network, respectively, includes:
Accessing each virtual network element device to the physical network, wherein the virtual network element device is connected with the access switch of the physical network through the virtual switch;
And constructing a border gateway protocol neighbor relation between each virtual network element device and an access switch corresponding to the physical network based on a border gateway protocol.
According to an embodiment of the present disclosure, the above method further includes:
the internet protocol address corresponding to each of the virtual switches is generated in response to an internet protocol address configuration operation for each of the virtual switches.
According to an embodiment of the present disclosure, the virtual network element device in each of the resource nodes is connected to the virtual switch through a first port and a second port, where the first port is used to receive or transmit virtual network traffic of the virtual network through the virtual switch, and the second port is used to receive and transmit physical network traffic of the physical network through the virtual switch, and a port number of the first port is different from a port number of the second port.
According to an embodiment of the present disclosure, the determining a static route corresponding to each of the virtual network element devices includes:
and generating the static route corresponding to each virtual network element device in response to the static route configuration operation of each virtual network element device.
According to an embodiment of the present disclosure, the above method further includes:
And determining the load balancing metric value of each static route in response to a load balancing metric value configuration operation for each static route, wherein the load balancing metric value of each static route is different.
According to an embodiment of the present disclosure, the determining, based on the load balancing metric value corresponding to each of the virtual network element devices, one target virtual network element device and at least one standby virtual network element device from among the at least two virtual network element devices includes:
Sorting each of the virtual network element devices according to the magnitude of the load balancing metric value of the static route corresponding to each of the virtual network element devices;
And determining one target virtual network element device and at least one standby virtual network element device from the at least two virtual network element devices based on the sorting result.
According to an embodiment of the present disclosure, the access switch switches the service borne by the target virtual network element device to any one of the at least one standby virtual network element device by:
Detecting the running state of the target virtual network element equipment based on a bidirectional forwarding detection mechanism, and outputting a detection result;
Determining a target standby virtual network element device corresponding to the target virtual network element device in the at least one standby virtual network element device based on a border gateway protocol under the condition that the detection result represents that the target virtual network element device fails;
And switching the service born by the target virtual network element equipment to the target standby virtual network element equipment.
According to an embodiment of the present disclosure, the physical network is an underley network; the virtual network is an overlay network; the load balancing metric value is a metric value.
In a second aspect, an embodiment of the present disclosure provides a switching apparatus of a virtual network element device, where the apparatus includes:
A building module, configured to build a border gateway protocol neighbor relation between at least two virtual network element devices and an access switch corresponding to a physical network, where each virtual network element device is deployed in a different resource node, each resource node is deployed with a virtual switch connected to the virtual network element device, the physical network carries a virtual network, and the resource node is configured to connect the physical network and the virtual network;
A first determining module, configured to determine a static route corresponding to each of the virtual network element devices, where a next hop of each of the static routes is an internet protocol address of the virtual switch corresponding to each of the virtual network element devices;
A redistribution module, configured to redistribute each of the static routes to the access switch based on the border gateway protocol neighbor relation, where the static routes each correspond to a load balancing metric value;
and the switching module is used for determining a target virtual network element device and at least one standby virtual network element device in the at least two virtual network element devices based on the load balance metric value corresponding to each virtual network element device so as to switch the service born by the target virtual network element device to any one of the at least one standby virtual network element device through the access switch.
In a third aspect, an embodiment of the present disclosure provides an electronic device, including: a memory, a processor; wherein the memory has executable code stored thereon, which when executed by the processor causes the processor to perform the virtual network element device switching method as described in the first aspect.
In a fourth aspect, embodiments of the present disclosure provide a non-transitory machine-readable storage medium having executable code stored thereon, which when executed by a processor of an electronic device, causes the processor to perform a virtual network element device switching method as described in the first aspect.
In the solution for the embodiment of the present disclosure, it is assumed that the problem of failure detection and handover of virtual network element devices is to be solved, and rapid convergence of the virtual network element devices is achieved, for this purpose, first, a border gateway protocol neighbor relation between a plurality of virtual network element devices and access switches of a physical network is established, the virtual network element devices in each resource node are configured with the same static route, the next hop of each static route is an internet protocol address of the virtual switch corresponding to each virtual network element device, and each virtual switch corresponds to the same internet protocol address, so that the access switches can learn the static route of each virtual network element device based on the border gateway protocol neighbor; then, based on the load balance metric value of each static route, a master-slave relation among a plurality of virtual network element devices is established so as to determine target virtual network element devices and at least one slave virtual network element device; finally, the target virtual network element device is detected by a border gateway protocol (Border Gateway Protocol, BGP) and a parallel bidirectional forwarding detection mechanism (Bidirectional Forwarding Detection, BFD), so that the service borne by the target virtual network element device can be switched to any one of the at least one standby virtual network element device through the access switch when the failure of the target virtual network element device is detected. According to the virtual network element device convergence method and device, the virtual network element device convergence is achieved through the border gateway protocol and the bidirectional forwarding detection mechanism, the influence on the service flow of the whole network bearer is reduced, and the use experience of tenants is improved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the drawings required for the description of the embodiments will be briefly described below, and it is apparent that the drawings in the following description are some embodiments of the present disclosure, and other drawings may be obtained according to these drawings without inventive effort for a person of ordinary skill in the art.
Fig. 1 is a flowchart of a method for switching virtual network element devices according to an embodiment of the present disclosure;
Fig. 2 is a schematic diagram of a neighbor relation of a border gateway protocol according to an embodiment of the present disclosure;
Fig. 3 is a flowchart of a method for determining a target virtual network element device and a standby virtual network element device according to an embodiment of the present disclosure;
fig. 4 is a flowchart of a method for switching a service borne by a target virtual network element device to a standby virtual network element device according to an embodiment of the present disclosure;
fig. 5 is a schematic diagram of a virtual network element device switching method according to another embodiment of the present disclosure;
Fig. 6 is a schematic structural diagram of a switching apparatus of a virtual network element device according to an embodiment of the present disclosure;
Fig. 7 is a schematic structural diagram of a first electronic device provided in an embodiment of the present disclosure;
Fig. 8 is a schematic structural diagram of a second electronic device according to an embodiment of the disclosure.
Detailed Description
For the purposes of making the objects, technical solutions and advantages of the embodiments of the present disclosure more apparent, the technical solutions of the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present disclosure, and it is apparent that the described embodiments are some embodiments of the present disclosure, but not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art without inventive effort, based on the embodiments in this disclosure are intended to be within the scope of this disclosure.
In addition, in some of the flows described in the specification and claims of this disclosure and the foregoing figures, a plurality of operations occurring in a particular order are included, but it should be understood that the operations may be performed out of order or performed in parallel, with the order of operations such as 101, 102, etc., being merely used to distinguish between the various operations, the order of the operations themselves not representing any order of execution. In addition, the flows may include more or fewer operations, and the operations may be performed sequentially or in parallel. It should be noted that, the descriptions of "first" and "second" herein are used to distinguish different messages, devices, modules, etc., and do not represent a sequence, and are not limited to the "first" and the "second" being different types.
First, several concepts involved in the embodiments of the disclosure are first described below to aid in understanding the context.
NFV: NFV, network function virtualization (Network Functions Virtualization), constructs many types of network devices (such as servers, switches, storage, etc.) as a data center network, virtualizes to form VMs (Virtual machines) by using a virtualization technology of IT (internet technology ), and then deploys conventional CT (communication technology ) traffic onto the VMs.
BGP: border gateway protocol BGP (Border Gateway Protocol) is a distance vector routing protocol that enables routing between autonomous systems AS (Autonomous System) to be reachable and selects the best route.
BFD: BFD (Bidirectional Forwarding Detection) is a bidirectional forwarding detection mechanism, which can provide millisecond detection, can realize rapid detection of links, and BFD can realize rapid convergence of routes by linking with an upper layer routing protocol, thereby ensuring permanence of services.
VXLAN: the VXLAN is a network virtualization technology, can improve the problem of expansion of large-scale cloud computing in deployment, and is an expansion of VLAN. VXLAN is a powerful tool that can extend two layers across three-layer networks. It can solve the portability limitation of VMS (virtual memory system) by encapsulating traffic and expanding it to a third layer gateway so that it can access servers on the external IP subnet.
VTEP: VTEP (VXLAN Tunnel EndPoint) is the device directly connected to the terminal, responsible for VXLAN encapsulation and decapsulation of the original ethernet message. The VTEP may be a virtual switch or a physical switch in morphology.
Open vSwitch: open vSwitch is an Open-source virtual switch software that specifically manages a multi-tenancy public cloud computing environment, providing network administrators with traffic visibility and control between and within virtual VMs.
In the public cloud data center which is common at present, NFV devices (such as software load balancing, software NAT gateway, software firewall, etc.) for providing network application services for tenants are generally deployed on physical servers of a computing resource pool in the form of KVM virtual machines, and multiple NFV virtual machines on a single physical server can be deployed according to the hardware configuration situation of the servers. Open vSwitch is deployed simultaneously on each physical server as an access switch for all NFV devices running on that server. To avoid the problem of single point failure of NFV devices, NFV device groups that provide network services for the same tenant are typically deployed on multiple physical servers in an AA (primary-primary load balancing)/AS (primary-standby redundancy) manner.
At present, fault detection of NFV high availability clusters in the related art requires VTEP devices that rely on tenant host access,
But the number of VTEP devices, NFV devices is generally large. Taking the number of VTEP devices as m and the number of NFV devices as n as an example, m×n times of detection are needed when fault detection is performed, so that service flow of the whole data center network is increased, normal operation of tenant service is affected, and the use experience of the tenant is poor.
In order to solve the above technical problems, a core idea of the virtual network element device switching method provided by the embodiments of the present disclosure is that: respectively constructing boundary gateway protocol neighbor relations between at least two virtual network element devices and access switches corresponding to a physical network, wherein each virtual network element device is respectively deployed in different resource nodes, each resource node is internally provided with a virtual switch connected with the virtual network element device, each virtual switch corresponds to the same Internet protocol address, the physical network is loaded with the virtual network, and the resource nodes are used for connecting the physical network and the virtual network; determining a static route corresponding to each virtual network element device, wherein the next hop of each static route is an internet protocol address of a virtual switch corresponding to each virtual network element device, and each static route corresponds to a load balancing metric value, so that the access switch can learn the static route of each virtual network element device based on a border gateway protocol neighbor; determining a target virtual network element device and at least one standby virtual network element device in at least two virtual network element devices based on a load balancing metric value corresponding to each virtual network element device; each static route is redistributed to the access switch based on the border gateway protocol neighbor relation so as to switch traffic borne by the target virtual network element device to any one of the at least one standby virtual network element device through the access switch. The rapid convergence of the virtual network element equipment is realized through the border gateway protocol and the bidirectional forwarding detection mechanism, the influence on the service flow of the whole network bearer is reduced, and the use experience of the tenant is improved. It should be noted that, the method for switching virtual network element devices provided by the embodiment of the present disclosure may be applicable to switching virtual network element devices in a cloud data center in a scenario of accessing a virtual switch.
The method for switching the virtual network element device provided in the embodiments of the present disclosure may be performed by an electronic device, which may be a terminal device such as a PC, a notebook, or a server. The server may be a physical server or may be a virtual server. The server may be a physical or virtual server on the user side, or may be a cloud server.
The following describes in detail the execution procedure of the image generation method provided by the present disclosure with reference to the following embodiments.
Fig. 1 is a flowchart of a virtual network element device switching method provided by an embodiment of the present disclosure, where, as shown in fig. 1, the virtual network element device switching method may include operations S101 to S104.
In operation S101, a border gateway protocol neighbor relation between at least two virtual network element devices and an access switch corresponding to a physical network is respectively constructed.
In operation S102, a static route corresponding to each virtual network element device is determined.
In operation S103, each static route is redistributed to the access switch based on the border gateway protocol neighbor relation.
In operation S104, a target virtual network element device and at least one standby virtual network element device are determined among the at least two virtual network element devices based on the load balancing metric value corresponding to each virtual network element device, so that the service borne by the target virtual network element device is switched to any one of the at least one standby virtual network element device through the access switch.
First, a border gateway protocol neighbor relationship between at least two virtual network element devices and an access switch corresponding to a physical network is respectively constructed. In this embodiment, the border gateway protocol neighbor relationship between the virtual network element device and the access switch may be constructed based on BGP; the physical network may be, for example, a virtual network, and the virtual network and the physical network may be connected through a resource node. Each virtual network element device is respectively deployed in different resource nodes, and a virtual switch connected with the virtual network element device is deployed in each resource node.
For ease of understanding, a neighbor relation diagram of the border gateway protocol is exemplarily described below in conjunction with fig. 2. As shown in fig. 2, the physical network is connected to two resource nodes through an access switch, and one of the two resource nodes is deployed with a first virtual switch and a first virtual network element device, and the other resource node is deployed with a second virtual switch and a second virtual network element device. Wherein the first virtual switch and the second virtual switch have the same internet protocol address. The first virtual network element device is connected with the access switch through the first virtual switch, and the second virtual network element device is connected with the access switch through the second virtual switch. Then, the first virtual network element device may establish a border gateway protocol neighbor relationship with the access switch through the first virtual switch, and the second virtual network element device may establish a border gateway protocol neighbor relationship with the access switch through the second virtual switch. It should be noted that, the connection of the physical network to two resource nodes through the access switch is merely an exemplary embodiment, and according to the specific implementation requirement, the physical network may be connected to any number of resource nodes through the access switch.
In practical applications, optionally, the virtual network element device may include an NFV device, the physical network may include an underley network, and the virtual network may include an overlay network, for example, but not limited to this.
After the border gateway protocol neighbor relation between each virtual network element device and the access switch is constructed, a static route corresponding to each virtual network element device is determined. Specifically, the next hop of each static route is the internet protocol address of the virtual switch corresponding to each virtual network element device.
In practical application, when the service flow of the virtual network is forwarded to the virtual network element device, the service flow needs to be forwarded to the virtual switch corresponding to the virtual network element device, and then the service flow is forwarded to the virtual network element device by the virtual switch in a flow table mode. Therefore, the virtual network element device can establish a border gateway protocol neighbor relation with the access switch and issue the static route, in which case the access switch can perform forwarding selection of the virtual network element device according to the static route.
It should be noted that, the internet protocol address of the virtual switch may refer to an IP address of an interface of the virtual switch connection access switch. That is, the next hop of the static route is the IP address of the virtual switch connection access switch interface, and the destination address of the static route may include the VTEP IP address of the virtual switch, which may be additionally configured according to the specific implementation requirement. Wherein the VTEP IP address of each virtual switch may be the same.
For ease of understanding, each static route is explained again below in connection with fig. 2. As shown in fig. 2, the VTEP IP addresses of the first virtual switch and the second virtual switch are 192.168.1.1/32. A static route of 192.168.1.1/32 is created for the first virtual network element device and the second virtual network element device, respectively. The next hop of the static route corresponding to the first virtual network element device is the internet protocol address of the first virtual switch, and the next hop of the static route corresponding to the second virtual network element device is the internet protocol address of the second virtual switch.
Each static route is then redistributed to the access switch based on the border gateway protocol neighbor relation so that the access switch learns of each static route. Specifically, before the static route redistribution, each static route is converted into a BGP route through a border gateway protocol, and then each BGP route is synchronized to an access switch, so as to complete the static route redistribution. It should be noted that, each BGP route carries a load balancing metric, which may be generated, for example, by configuration. The load balancing metric value carried by the BGP route is a load balancing metric value corresponding to the static route, and each load balancing metric value corresponding to the static route may be the same or different. It should be noted that, the load balancing metric value corresponding to the static route may include, for example, a metric value.
Further, when the load balancing metric value corresponding to each virtual network element device is the same, balancing the load of each virtual network element device; when the load balance metric values corresponding to each virtual network element device are different, the plurality of virtual network element devices are redundant. The traffic sharing mode of the virtual network device can be arbitrarily selected according to specific implementation requirements.
Then, based on the load balance metric value corresponding to each virtual network element device, one target virtual network element device and at least one standby virtual network element device are determined in at least two virtual network element devices, so that the service born by the target virtual network element device is switched to any standby virtual network element device in the at least one standby virtual network element device through an access switch. The target virtual network element device may include, for example, a primary traffic sharing virtual network element device, and the standby virtual network element device may include a secondary traffic sharing virtual network element device. Since there may be a plurality of virtual network element devices, and the virtual network element device for primary traffic sharing is generally only set up one, the standby virtual network element device may include one or more.
In order to implement the above-mentioned construction of the border gateway protocol neighbor relation, each virtual network element device needs to be first accessed into the physical network. Specifically, the virtual network element device may be connected to a virtual switch in the resource node to which the virtual network element device belongs, and then connected to an access switch of the physical network through the virtual switch, so as to access each virtual network element device to the physical network.
After each virtual network element device is accessed to the physical network, a border gateway protocol neighbor relation between each virtual network element device and an access switch corresponding to the physical network is constructed based on a border gateway protocol.
Based on this, to implement configuration of the corresponding internet protocol address for each virtual switch, an internet protocol address configuration page may be first displayed, and then based on the internet protocol address configuration page, an internet protocol address configuration operation for each virtual switch may be obtained and responded, so that an internet protocol address corresponding to each virtual switch is generated according to the above-mentioned internet protocol address configuration operation.
According to an embodiment of the present disclosure, a virtual network element device within each resource node is connected to a virtual switch through a first port and a second port, where a port number of the first port is different from a port number of the second port.
For ease of understanding, the first port and the second port are respectively Gi0/0 and Gi0/1, that is, the virtual network element device is connected to the virtual switch through two ports Gi0/0 and Gi 0/1. The Gi0/0 port may be used to receive or send virtual network traffic of the virtual network through the virtual switch, that is, the virtual network traffic may be sent to the virtual switch by the tenant host, and then the Gi0/0 port of the virtual network element device receives the virtual network traffic sent by the virtual switch, or the virtual network traffic may be sent to the virtual switch through the Gi0/0 port of the virtual network element device, and then the virtual switch sends the virtual network traffic to the tenant host. The Gi0/1 port may be used to receive and transmit physical network traffic of the physical network through the virtual switch, i.e., the physical network traffic may be transmitted to the virtual switch by the Gi0/1 port of the virtual network element device and then transmitted to the access switch of the physical network by the virtual switch, or the physical network traffic may be transmitted to the virtual switch by the access switch of the physical network and then received by the Gi0/1 port of the virtual network element device through the virtual switch.
In practical application, optionally, the Gi0/1 port of the virtual network element device may be directly connected to the access switch in two layers, i.e. the Gi0/1 port of the virtual network element device and the access switch may directly perform information interaction, but cannot perform forwarding by the virtual switch.
According to the embodiment of the disclosure, when determining the static route corresponding to each virtual network element device, for example, a static route configuration page may be displayed first, and then based on the static route configuration page, a static route configuration operation for each virtual network element device is obtained and responded, so that the static route corresponding to each virtual network element device is generated according to the static route configuration operation.
According to the embodiment of the disclosure, when determining the load balancing metric value of each static route, for example, a load balancing metric value configuration page may be presented first, and then, based on the load balancing metric value configuration page, a load balancing metric value configuration operation for each static route is obtained and responded, so that a load balancing metric value corresponding to each static route device is generated according to the load balancing metric value configuration operation.
For convenience of explanation, how one target virtual network element device and at least one standby virtual network element device are determined among at least two virtual network element devices based on the load balancing metric value corresponding to each virtual network element device is exemplarily described below with reference to fig. 3. As shown in fig. 3, the method includes operations S301 to S302.
First, in operation S301, each virtual network element device is ordered according to the magnitude of the load balancing metric value of the static route corresponding to each virtual network element device. The load balancing metric value of each static route may be the same or different. In the case that the load balancing value of each static route is the same, the load of each virtual network element device is balanced, in which case it is not necessary to distinguish between the target virtual network element device and the standby virtual network element device. And under the condition that the load balance measurement values of the virtual network element devices are different, the main and standby virtual network element devices are redundant, namely the target virtual network element device and the standby virtual network element device need to be distinguished.
In practical application, in order to realize high availability of the virtual network element device cluster, the load balancing value of each static route is different, and the target virtual network element device and the standby virtual network element device need to be distinguished. Because the load balancing values of the static routes corresponding to each virtual network element device are different, and the target virtual network element device needs to be determined in the plurality of virtual network element devices, the ordering is needed according to the numerical value of the load balancing value of the static routes corresponding to each virtual network element device.
Then, in operation S302, a target virtual network element device and at least one standby virtual network element device are determined among the at least two virtual network element devices based on the sorting result. After the sequencing result of each static route is generated, the corresponding virtual network element device of the load balancing value with the minimum value can be determined, so that the virtual network element device can be determined as a target virtual network element device, and other virtual network element devices except the target virtual network element device are determined as standby virtual network element devices.
In accordance with an embodiment of the present disclosure, how an access switch switches traffic assumed by a target virtual network element device to any one of at least one standby virtual network element device is illustrated below in connection with fig. 4. As shown in fig. 4, the method includes operations S401 to S403.
First, in operation S401, the operation state of the target virtual network element device is detected based on the bidirectional forwarding detection mechanism, and a detection result is output. Then, in operation S402, in case that the detection result indicates that the target virtual network element device fails, a target standby virtual network element device corresponding to the target virtual network element device is determined among the at least one standby virtual network element devices based on the border gateway protocol. Finally, in operation S403, the service borne by the target virtual network element device is switched to the target standby virtual network element device.
In summary, based on the scheme provided by the embodiment of the present disclosure, by using the resource node to which the virtual network element device belongs and the BGP dynamic routing protocol of the access switch, when the virtual network element device fails, path switching can be performed on the virtual network traffic and the physical network traffic carried by the virtual network element device in the cloud data center network at the same time, so as to avoid the problem of traffic packet loss caused by different high availability mechanisms of the virtual network traffic and the physical network traffic. The convergence performance of the virtual network element equipment can be improved through the BFD characteristic, BFD multi-hop detection or ICMP detection keep-alive of the whole network is not needed, the influence on the service flow carried by the whole network is reduced, the resource pressure of the virtual network element equipment and other Overlay ECMP equipment is reduced, and the service processing efficiency is improved.
Having described the steps in the foregoing embodiments by way of example, the overall implementation is described in conjunction with fig. 5 for a complete understanding of the processing logic provided by the embodiments of the present disclosure.
As shown in fig. 5, in practical application, BGP neighbors of a first NFV device, a second NFV device, and an access switch corresponding to an underway network are first constructed, and the same VTEP IP address is configured for a first virtual switch corresponding to the first NFV device and a second virtual switch corresponding to the second NFV device, for example, the VTEP IP address is 192.168.1.1/32. Creating a 192.168.1.1/32 static route for the first NFV device, wherein the destination address is a VTEP IP address of the first virtual switch, and the next hop is an internet protocol address of the first virtual switch; a static route of 192.168.1.1/32 is created for the second NFV device, the destination address being the VTEP IP address of the second virtual switch, the next hop being the internet protocol address of the second virtual switch. And then determining the target NFV device and the standby NFV device according to the load balancing metric value of the static route of the first NFV device and the second NFV device, wherein in the embodiment, the first NFV device is the target NFV device, and the second NFV device is the standby NFV device. In this way, the access switch of the underway network may learn each static route according to BGP routing protocols.
In general, when the tenant host sends the virtual network traffic to the target NFV device through the tenant virtual switch and the VXLAN tunnel, the destination address of the VXLAN packet of the virtual network traffic is 192.168.1.1/32, and when the virtual network traffic is forwarded to the access switch through the Underlay network, the access switch performs routing according to the route learned by the BGP routing protocol.
When the target NFV equipment fails, the routing protocol of BGP is converged, and VXLAN message with the destination address of 192.168.1.1/32, which is sent to the NFV equipment by the tenant host, is switched to the spare NFV equipment which does not fail in the access switch; meanwhile, the underway traffic sent to the NFV device also converges in the BGP-passing routing protocol, and the traffic is switched to the spare NFV device that is not faulty.
Switching apparatuses of virtual network element devices of one or more embodiments of the present disclosure will be described in detail below. Those skilled in the art will appreciate that these means may be configured by the steps taught by the present solution using commercially available hardware components.
Fig. 6 is a schematic structural diagram of a switching apparatus 600 of a virtual network element device according to an embodiment of the present disclosure, as shown in fig. 6, where the apparatus includes: a construction module 601, a first determination module 602, a redistribution module 603 and a switching module 604.
A construction module 601, configured to respectively construct a border gateway protocol neighbor relationship between at least two virtual network element devices and an access switch corresponding to a physical network, where each virtual network element device is deployed in a different resource node, each resource node is deployed with a virtual switch connected to the virtual network element device, the physical network carries a virtual network, and the resource nodes are used to connect the physical network and the virtual network;
A first determining module 602, configured to determine a static route corresponding to each of the virtual network element devices, where a next hop of each of the static routes is the internet protocol address of the virtual switch corresponding to each of the virtual network element devices;
A redistribution module 603, configured to redistribute each of the static routes to the access switch based on the border gateway protocol neighbor relation, where the static routes each correspond to a load balancing metric value;
a switching module 604, configured to determine, from among the at least two virtual network element devices, a target virtual network element device and at least one standby virtual network element device based on the load balancing metric value corresponding to each of the virtual network element devices, so as to switch, through the access switch, a service borne by the target virtual network element device to any one of the at least one standby virtual network element device.
Through the resource node to which the virtual network element equipment belongs and the BGP dynamic routing protocol of the access switch, when the virtual network element equipment fails, the path switching can be carried out on the virtual network flow and the physical network flow carried by the virtual network element equipment in the cloud data center network at the same time, so that the problem of flow packet loss caused by different high-availability mechanisms of the virtual network flow and the physical network flow is avoided. The convergence performance of the virtual network element equipment can be improved through the BFD characteristic, BFD multi-hop detection or ICMP detection keep-alive of the whole network is not needed, the influence on the service flow carried by the whole network is reduced, the resource pressure of the virtual network element equipment and other Overlay ECMP equipment is reduced, and the service processing efficiency is improved.
Alternatively, the building block 601 may comprise an access unit and a building unit.
And the access unit is used for accessing each virtual network element device into the physical network, wherein the virtual network element device is connected with the access switch of the physical network through the virtual switch.
And the construction unit is used for constructing a border gateway protocol neighbor relation between each virtual network element device and the access switch corresponding to the physical network based on a border gateway protocol.
Optionally, the switching apparatus 600 of the virtual network element device may further include a first generation module.
And a first generation module, configured to generate, in response to an internet protocol address configuration operation for each virtual switch, the internet protocol address corresponding to each virtual switch.
Alternatively, the first determination module 602 may include a second generation module.
And the second generation module is used for responding to the static route configuration operation of each virtual network element device and generating the static route corresponding to each virtual network element device.
Optionally, the switching apparatus 600 of the virtual network element device may further include a second determining module.
And a second determining module, configured to determine a load balancing metric value of each static route in response to a load balancing metric value configuration operation for each static route, where the load balancing metric value of each static route is different.
Alternatively, the switching module 604 may include a sorting unit and a first determining unit.
The ordering unit is used for ordering each virtual network element device according to the numerical value of the load balancing metric value of the static route corresponding to each virtual network element device;
and the first determining unit is used for determining one target virtual network element device and at least one standby virtual network element device in the at least two virtual network element devices based on the sorting result.
Optionally, the switching module 604 may further include a detection unit, a second determination unit, and a switching unit.
And the detection unit is used for detecting the running state of the target virtual network element equipment based on the bidirectional forwarding detection mechanism and outputting a detection result.
And the second determining unit is used for determining target standby virtual network element equipment corresponding to the target virtual network element equipment in the at least one standby virtual network element equipment based on a border gateway protocol under the condition that the detection result represents that the target virtual network element equipment fails.
And the switching unit is used for switching the service born by the target virtual network element equipment to the target standby virtual network element equipment.
In one possible design, the structure of the address mapping device shown in fig. 7 may be implemented as a first electronic device. As shown in fig. 7, the first electronic device 700 may include: a processor 701 and a memory 702. Wherein the memory 702 has stored thereon executable code which, when executed by the processor 701, at least enables the processor 701 to implement the address mapping method as provided in the embodiment shown in fig. 1 described above.
The first electronic device 700 may further include a communication interface 703 configured to communicate with other devices.
Fig. 8 is a schematic structural diagram of a second electronic device according to the present embodiment, and as shown in fig. 8, the second electronic device 800 may include one or more of the following components: a processing component 802, a memory 804, a power component 806, a multimedia component 808, an audio component 810, an input/output (I/O) interface 812, a sensor component 814, and a communication component 816.
The processing component 802 generally controls overall operation of the second electronic device 800, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. The processing component 802 may include one or more processors 820 to execute instructions to perform all or part of the method steps 101-105 described above. Further, the processing component 802 can include one or more modules that facilitate interactions between the processing component 802 and other components. For example, the processing component 802 can include a multimedia module to facilitate interaction between the multimedia component 808 and the processing component 802.
The memory 804 is configured to store various types of data to support operation at the second electronic device 800. Examples of such data include instructions for any application or method operating on the second electronic device 800, contact data, phonebook data, messages, pictures, videos, and so forth. The memory 804 may be implemented by any type or combination of volatile or nonvolatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk.
The power supply component 806 provides power to the various components of the second electronic device 800. The power supply components 806 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the second electronic device 800.
The multimedia component 808 includes a screen between the second electronic device 800 and the user that provides an output interface. In some embodiments, the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensor may sense not only the boundary of a touch or slide action, but also the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 808 includes a front camera and/or a rear camera. When the second electronic device 800 is in an operation mode, such as a photographing mode or a video mode, the front camera and/or the rear camera may receive external multimedia data. Each front camera and rear camera may be a fixed optical lens system or have focal length and optical zoom capabilities.
The audio component 810 is configured to output and/or input audio signals. For example, the audio component 810 includes a Microphone (MIC) configured to receive external audio signals when the second electronic device 800 is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signals may be further stored in the memory 804 or transmitted via the communication component 816. In some embodiments, audio component 810 further includes a speaker for outputting audio signals.
Input/output interface 812 provides an interface between processing component 802 and peripheral interface modules, which may be keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to: homepage button, volume button, start button, and lock button.
The sensor assembly 814 includes one or more sensors for providing status assessment of various aspects for the second electronic device 800. For example, the sensor assembly 814 may detect an on/off state of the second electronic device 800, a relative positioning of the components, such as a display and keypad of the second electronic device 800, the sensor assembly 814 may also detect a change in position of the second electronic device 800 or a component of the second electronic device 800, the presence or absence of a user's contact with the second electronic device 800, a change in orientation or acceleration/deceleration of the second electronic device 800, and a change in temperature of the second electronic device 800. The sensor assembly 814 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. The sensor assembly 814 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 814 may also include an acceleration sensor, a gyroscopic sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
The communication component 816 is configured to facilitate communication between the second electronic device 800 and other devices, either wired or wireless. The second electronic device 800 may access a wireless network based on a communication standard, such as WiFi,2G or 3G or 4G or a combination thereof. In one exemplary embodiment, the communication component 816 receives broadcast signals or broadcast related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, the communication component 816 further includes a Near Field Communication (NFC) module to facilitate short range communications. For example, the NFC module may be implemented based on radio frequency identification (rfid) technology, infrared data association (irda) technology, ultra Wideband (UWB) technology, bluetooth (BT) technology, and other technologies.
In an exemplary embodiment, the second electronic device 800 may be implemented by one or more Application Specific Integrated Circuits (ASICs), digital Signal Processors (DSPs), digital Signal Processing Devices (DSPDs), programmable Logic Devices (PLDs), field Programmable Gate Arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic elements for executing the methods described above.
In an exemplary embodiment, a non-transitory computer readable storage medium is also provided, such as memory 804 including instructions executable by processor 820 of second electronic device 800 to perform the above-described method. For example, the non-transitory computer readable storage medium may be implemented by any type of volatile or non-volatile memory device or combination thereof, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk, or optical disk.
Additionally, embodiments of the present disclosure provide a non-transitory machine-readable storage medium having executable code stored thereon that, when executed by a processor of an electronic device, causes the processor to perform the address mapping method provided in the embodiment of fig. 1 described above.
The apparatus embodiments described above are merely illustrative, wherein the various modules illustrated as separate components may or may not be physically separate. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment. Those of ordinary skill in the art will understand and implement the present invention without undue burden.
From the above description of embodiments, it will be apparent to those skilled in the art that the embodiments may be implemented by adding necessary general purpose hardware platforms, or may be implemented by a combination of hardware and software. Based on such understanding, the foregoing aspects, in essence, or portions thereof, may be embodied in the form of a computer program product, which may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.
Finally, it should be noted that: the above embodiments are merely for illustrating the technical solution of the present disclosure, and are not limiting thereof; although the present disclosure has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present disclosure.

Claims (11)

1. A method for switching virtual network element devices, comprising:
Respectively constructing boundary gateway protocol neighbor relations between at least two virtual network element devices and access switches corresponding to a physical network, wherein each virtual network element device is respectively deployed in different resource nodes, each resource node is internally provided with a virtual switch connected with the virtual network element device, the physical network is loaded with the virtual network, and the resource nodes are used for connecting the physical network and the virtual network;
Determining a static route corresponding to each virtual network element device, wherein the next hop of each static route is an internet protocol address of the virtual switch corresponding to each virtual network element device;
redistributing each static route to the access switch based on the border gateway protocol neighbor relation, wherein the static routes each correspond to a load balancing metric value;
determining a target virtual network element device and at least one standby virtual network element device in the at least two virtual network element devices based on the load balancing metric value corresponding to each virtual network element device, so as to switch the service born by the target virtual network element device to any one standby virtual network element device in the at least one standby virtual network element device through the access switch;
The access switch switches the service borne by the target virtual network element device to any one of the at least one standby virtual network element device by the following method:
Detecting the running state of the target virtual network element equipment based on a bidirectional forwarding detection mechanism, and outputting a detection result;
Determining target standby virtual network element equipment corresponding to the target virtual network element equipment in the at least one standby virtual network element equipment based on a border gateway protocol under the condition that the detection result represents that the target virtual network element equipment fails;
and switching the service born by the target virtual network element equipment to the target standby virtual network element equipment.
2. The method of claim 1, wherein constructing border gateway protocol neighbor relationships between at least two virtual network element devices and access switches corresponding to the physical network, respectively, comprises:
Accessing each virtual network element device to the physical network, wherein the virtual network element device is connected with the access switch of the physical network through the virtual switch;
And constructing a border gateway protocol neighbor relation between each virtual network element device and an access switch corresponding to the physical network based on a border gateway protocol.
3. The method according to claim 2, wherein the method further comprises:
In response to an internet protocol address configuration operation for each of the virtual switches, the internet protocol address corresponding to each of the virtual switches is generated.
4. The method of claim 1, wherein the virtual network element devices within each of the resource nodes are connected to the virtual switch through a first port for receiving or transmitting virtual network traffic of the virtual network through the virtual switch and a second port for receiving and transmitting physical network traffic of the physical network through the virtual switch, the port number of the first port being different from the port number of the second port.
5. The method of claim 1, wherein said determining a static route corresponding to each of said virtual network element devices comprises:
And generating the static route corresponding to each virtual network element device in response to the static route configuration operation for each virtual network element device.
6. The method according to claim 1, wherein the method further comprises:
Determining the load balancing metric value for each of the static routes in response to a load balancing metric value configuration operation for each of the static routes, wherein the load balancing metric value for each of the static routes is different.
7. The method of claim 1, wherein the determining a target virtual network element device and at least one backup virtual network element device among the at least two virtual network element devices based on the load balancing metric value corresponding to each of the virtual network element devices comprises:
Sorting each virtual network element device according to the numerical value of the load balancing metric value of the static route corresponding to each virtual network element device;
And determining one target virtual network element device and at least one standby virtual network element device in the at least two virtual network element devices based on the sequencing result.
8. The method according to any one of claims 1 to 7, wherein the physical network is an underly network; the virtual network is an overlay network; the load balancing metric value is a metric value.
9. A switching apparatus for a virtual network element device, comprising:
The system comprises a construction module, a physical network and a physical network, wherein the construction module is used for respectively constructing a boundary gateway protocol neighbor relation between at least two virtual network element devices and an access switch corresponding to the physical network, each virtual network element device is respectively deployed in different resource nodes, a virtual switch connected with the virtual network element device is deployed in each resource node, the physical network is loaded with the virtual network, and the resource nodes are used for connecting the physical network and the virtual network;
A first determining module, configured to determine a static route corresponding to each virtual network element device, where a next hop of each static route is an internet protocol address of the virtual switch corresponding to each virtual network element device;
A redistribution module, configured to redistribute each of the static routes to the access switch based on the border gateway protocol neighbor relation, where the static routes each correspond to a load balancing metric value;
A switching module, configured to determine, from among the at least two virtual network element devices, a target virtual network element device and at least one standby virtual network element device based on the load balancing metric value corresponding to each virtual network element device, so as to switch, through the access switch, a service borne by the target virtual network element device to any one of the at least one standby virtual network element device;
the detection unit is used for detecting the running state of the target virtual network element equipment based on the bidirectional forwarding detection mechanism and outputting a detection result;
A second determining unit, configured to determine, in the case where the detection result indicates that the target virtual network element device fails, a target standby virtual network element device corresponding to the target virtual network element device in the at least one standby virtual network element device based on a border gateway protocol;
and the switching unit is used for switching the service born by the target virtual network element equipment to the target standby virtual network element equipment.
10. An electronic device, comprising: a memory, a processor; wherein the memory has stored thereon executable code which, when executed by the processor, causes the processor to perform the virtual network element device switching method according to any of claims 1 to 8.
11. A non-transitory machine-readable storage medium having stored thereon executable code, which when executed by a processor of an electronic device, causes the processor to perform the virtual network element device switching method of any of claims 1 to 8.
CN202111501300.4A 2021-12-09 2021-12-09 Virtual network element device switching method, device and storage medium Active CN114157606B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202111501300.4A CN114157606B (en) 2021-12-09 2021-12-09 Virtual network element device switching method, device and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202111501300.4A CN114157606B (en) 2021-12-09 2021-12-09 Virtual network element device switching method, device and storage medium

Publications (2)

Publication Number Publication Date
CN114157606A CN114157606A (en) 2022-03-08
CN114157606B true CN114157606B (en) 2024-06-18

Family

ID=80454202

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202111501300.4A Active CN114157606B (en) 2021-12-09 2021-12-09 Virtual network element device switching method, device and storage medium

Country Status (1)

Country Link
CN (1) CN114157606B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114826823B (en) * 2022-03-25 2024-02-27 阿里云计算有限公司 Virtual network segmentation method, device and system

Family Cites Families (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8743683B1 (en) * 2008-07-03 2014-06-03 Silver Peak Systems, Inc. Quality of service using multiple flows
CN101931520B (en) * 2010-09-02 2014-01-01 中兴通讯股份有限公司 A switching method and system
CN102611628B (en) * 2012-04-05 2015-08-05 杭州华三通信技术有限公司 For realizing the method and apparatus that transmission path switches
CN102932247A (en) * 2012-10-10 2013-02-13 福建星网锐捷网络有限公司 VPN (Virtual Private Network) fast rerouting method and device and provider edge device
US9985867B2 (en) * 2015-12-11 2018-05-29 Cisco Technology, Inc. Optimizing EVPN for data centers with redundant top-of-rack deployments
CN107645402B (en) * 2016-07-22 2021-02-26 新华三技术有限公司 Route management method and device
WO2019012546A1 (en) * 2017-07-11 2019-01-17 Telefonaktiebolaget Lm Ericsson [Publ] Efficient load balancing mechanism for switches in a software defined network
CN110324241B (en) * 2018-03-30 2022-05-31 北京华为数字技术有限公司 A method for adjusting a traffic forwarding path, a message forwarding method and device
CN108306777B (en) * 2018-04-20 2021-04-13 平安科技(深圳)有限公司 SDN controller-based virtual gateway active/standby switching method and device
US10938626B2 (en) * 2018-07-25 2021-03-02 Microsoft Technology Licensing, Llc Fast failover for gateway instances
US10805193B1 (en) * 2019-04-30 2020-10-13 Juniper Networks, Inc. Faster fault-detection mechanism, for example using bidirectional forwarding detection (BFD), on network nodes and/or hosts multihomed using a link aggregation group (LAG)
CN111049925B (en) * 2019-12-20 2022-07-19 网易(杭州)网络有限公司 Hybrid cloud network system, communication system and communication method
CN111355668B (en) * 2020-03-12 2022-07-22 北京嘀嘀无限科技发展有限公司 Method for determining forwarding path, switch and storage medium
CN112511435B (en) * 2020-12-17 2022-09-23 四川灵通电讯有限公司 Method for realizing OSPF quick convergence in internal gateway protocol
CN113328916B (en) * 2021-06-07 2022-08-26 新华三技术有限公司 BFD detection mode switching method, device and equipment

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
Wen-Kuei Hsieh ; Wen-Hsu Hsieh ; Jiann-Liang Chen ; Feng-Yi Chou ; Yung-Sheng Lee.Load_balancing_virtual_machines_deployment_mechanism_in_SDN_open_cloud_platform.2015 17th International Conference on Advanced Communication Technology (ICACT).2015,329-335. *
基于SDN环境下的虚拟网络映射研究;温海涛;中国优秀硕士论文库信息科技辑;20190115;1-47页 *

Also Published As

Publication number Publication date
CN114157606A (en) 2022-03-08

Similar Documents

Publication Publication Date Title
US9191271B2 (en) Fast traffic recovery in VRRP based routers
TWI448131B (en) Failover in a host concurrently supporting multiple virtual ip addresses across multiple adapters
KR20210064294A (en) Communication access method and apparatus, computer device, and storage medium
US8339940B2 (en) Multi-active detection method and stack member device
US10454756B2 (en) Wearable group communication device bypass connectivity
JP2024150665A (en) Logical Router with Decomposed Network Elements
CN109728962B (en) Method and equipment for sending message
JP6072278B2 (en) Virtual chassis system control protocol
CN109862127B (en) Message transmission method and related device
US11824765B2 (en) Fast redirect of traffic when pods fail
CN113572831A (en) Communication method between Kubernetes clusters, computer equipment and medium
CN104065553B (en) Virtual network moving method and relevant device
CN113225252B (en) Establishment method, processing method and related equipment for Bidirectional Forwarding Detection (BFD) session
CN112328318B (en) Method, device and storage medium for automatic planning of proprietary cloud platform
CN114157606B (en) Virtual network element device switching method, device and storage medium
EP3695569A1 (en) A system and method for providing a layer 2 fast re-switch for a wireless controller
JP6077945B2 (en) Network system and control method
CN110289991B (en) Fault gateway detection method, device, storage medium and terminal
WO2022217786A1 (en) Cross-network communicaton method, apparatus, and system for multi-bus network, and storage medium
JP6383232B2 (en) Relay system and switch device
CN112564983A (en) Data transmission method, device, computer system and medium
CN115987890B (en) Method, device, electronic equipment and storage medium for cross-cluster access to virtual IP address
CN107948002B (en) AP access control method and device
CN113992571B (en) Multipath service convergence method, device and storage medium in SDN network
CN112887185B (en) Communication method and device of overlay network

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant