CN114285795B - State control method, device, equipment and storage medium of virtual equipment - Google Patents
State control method, device, equipment and storage medium of virtual equipment Download PDFInfo
- Publication number
- CN114285795B CN114285795B CN202111458135.9A CN202111458135A CN114285795B CN 114285795 B CN114285795 B CN 114285795B CN 202111458135 A CN202111458135 A CN 202111458135A CN 114285795 B CN114285795 B CN 114285795B
- Authority
- CN
- China
- Prior art keywords
- virtual device
- virtual
- master
- target
- slave
- 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
Links
Images
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The embodiment of the application provides a method, a device, equipment and a storage medium for controlling the state of virtual equipment, which relate to the technical field of cloud computing, and the method comprises the following steps: when the target virtual device meets the master-slave switching triggering condition, the network node where the target virtual device is located acquires the target virtual device and at least one other virtual device from the central node, and the master-slave state information corresponds to the target virtual device and the at least one other virtual device, wherein the at least one other virtual device and the target virtual device belong to the same virtual network. If it is determined that one master virtual device exists in the target virtual device and at least one other virtual device based on the obtained master-slave state information, and the target virtual device is a slave virtual device, the target virtual device is kept as the slave virtual device, and when a network congestion occurs, which causes that the virtual routing redundancy protocol packet sent by the network node where the master virtual device is located cannot be received by the network node where the slave virtual device is located, the split brain situation can be effectively avoided.
Description
Technical Field
The embodiment of the invention relates to the technical field of cloud computing, in particular to a method, a device, equipment and a storage medium for controlling the state of virtual equipment.
Background
With the continuous growth of applications, cloud computing has been greatly developed. The cloud computing is to acquire and connect a cloud computing platform consisting of a large number of servers and storage device clusters through a computer network to acquire services required by remote clients. Openstack serves as a cloud computing platform and provides extensible and elastic cloud computing services for private clouds and public clouds. With the increasing application of the cloud computing platform Openstack, the network, the virtual machine system, the enterprise application and the like of the external client are difficult to avoid faults, so that the service is interrupted, and normal service cannot be provided.
Since most of the current application programs have very low fault tolerance, the requirement of the external client for high-availability performance of the computer is very urgent, that is, for important applications, two virtual devices are used to backup each other and execute the same application together. When one virtual device fails, the other virtual device can undertake an application task, so that the system can be automatically ensured to continuously provide applications without manual intervention, wherein the virtual device for executing the service is a Master virtual device (Master), the virtual device for backing up is a Backup virtual device (Backup), and the Backup virtual device can also be called a slave virtual device.
The master Virtual device is responsible for periodically sending a VRRP (Virtual Router Redundancy Protocol) Protocol packet to the standby Virtual device, and informing the standby Virtual device of the configuration information and the working state of the current master Virtual device. When the network is congested, the standby virtual devices cannot acquire the VRRP protocol message of the main virtual device within a certain time, and the standby virtual devices can initiate the main device to contend for the standby virtual device, so that the main virtual devices in the network, namely the network has a split brain condition, and thus the execution result of the application is wrong.
Disclosure of Invention
The embodiment of the application provides a state control method, a state control device and a storage medium of a virtual device, which are used for avoiding the occurrence of split brain in a virtual network and causing the error of an execution result of an application.
In one aspect, an embodiment of the present application provides a method for controlling a state of a virtual device, where the method includes:
when the target virtual equipment meets a master-slave switching trigger condition, acquiring corresponding master-slave state information of the target virtual equipment and at least one other virtual equipment from a central node, wherein the at least one other virtual equipment and the target virtual equipment belong to the same virtual network;
if it is determined that one master virtual device exists in the target virtual device and the at least one other virtual device based on the obtained master-slave state information, and the target virtual device is a slave virtual device, the target virtual device is kept as the slave virtual device.
Optionally, the method further comprises:
if it is determined that a master virtual device does not exist in the target virtual device and the at least one other virtual device based on the obtained master-slave state information, determining whether to switch the target virtual device to a master virtual device based on the priorities corresponding to the target virtual device and the at least one other virtual device.
Optionally, the determining whether to switch the target virtual device to the master virtual device based on the priorities corresponding to the target virtual device and the at least one other virtual device includes:
and if a maximum priority exists in the priorities corresponding to the target virtual device and the at least one other virtual device, and the maximum priority corresponds to the target virtual device, switching the target virtual device to a main virtual device.
Optionally, the determining whether to switch the target virtual device to the master virtual device based on the priorities corresponding to the target virtual device and the at least one other virtual device includes:
if the target virtual device and the at least one other virtual device respectively correspond to at least two same maximum priorities, and one of the at least two maximum priorities corresponds to the target virtual device, judging whether the virtual IP address of the target virtual device is larger than the virtual IP addresses of the virtual devices corresponding to the other maximum priorities;
if yes, switching the target virtual equipment to main virtual equipment;
otherwise, the target virtual device is maintained as a slave virtual device.
Optionally, the master-slave switching triggering condition is that a virtual routing redundancy protocol message sent by the master virtual device is not received within a preset time length.
Optionally, the method further comprises:
if it is determined that at least two main virtual devices exist in the target virtual device and the at least one other virtual device based on the obtained master-slave state information, and the target virtual device is one of the main virtual devices, comparing virtual IP addresses of the at least two main virtual devices;
if the virtual IP address of the target virtual device is larger than the virtual IP addresses of other main virtual devices in the at least two main virtual devices, keeping the target virtual device as the main virtual device;
otherwise, switching the target virtual device to the slave virtual device.
Optionally, the at least one other virtual device and the target virtual device are located in different network nodes, each network node comprising at least one virtual device.
In one aspect, an embodiment of the present application provides a state control apparatus for a virtual device, where the apparatus includes:
an obtaining module, configured to obtain, from a central node, master-slave status information corresponding to a target virtual device and at least one other virtual device when the target virtual device meets a master-slave switching trigger condition, where the at least one other virtual device and the target virtual device belong to the same virtual network;
a first master-slave switching module, configured to, if it is determined that one master virtual device exists in the target virtual device and the at least one other virtual device based on the obtained master-slave status information, and the target virtual device is a slave virtual device, maintain the target virtual device as the slave virtual device.
Optionally, the system further includes a second master-slave switching module, specifically configured to:
if it is determined that a master virtual device does not exist in the target virtual device and the at least one other virtual device based on the obtained master-slave status information, determining whether to switch the target virtual device to a master virtual device based on the priorities corresponding to the target virtual device and the at least one other virtual device.
Optionally, the second master-slave switching module is further configured to:
and if a maximum priority exists in the priorities corresponding to the target virtual device and the at least one other virtual device, and the maximum priority corresponds to the target virtual device, switching the target virtual device to a main virtual device.
Optionally, the second master-slave switching module is further configured to:
if the target virtual device and the at least one other virtual device respectively correspond to at least two same maximum priorities, and one of the at least two maximum priorities corresponds to the target virtual device, judging whether the virtual IP address of the target virtual device is larger than the virtual IP addresses of the virtual devices corresponding to the other maximum priorities;
if yes, switching the target virtual equipment to main virtual equipment;
otherwise, the target virtual device is maintained as a slave virtual device.
Optionally, the master-slave switching triggering condition is that a virtual routing redundancy protocol message sent by the master virtual device is not received within a preset time length.
Optionally, the system further includes a third master-slave switching module, specifically configured to:
if it is determined that at least two main virtual devices exist in the target virtual device and the at least one other virtual device based on the obtained master-slave state information, and the target virtual device is one of the main virtual devices, comparing virtual IP addresses of the at least two main virtual devices;
if the virtual IP address of the target virtual device is larger than the virtual IP addresses of other main virtual devices in the at least two main virtual devices, keeping the target virtual device as the main virtual device;
otherwise, switching the target virtual device to the slave virtual device.
Optionally, the at least one other virtual device and the target virtual device are located in different network nodes, each network node comprising at least one virtual device.
In one aspect, an embodiment of the present application provides a computer device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor implements the steps of the state control method for the virtual device when executing the program.
In one aspect, embodiments of the present application provide a computer-readable storage medium, which stores a computer program executable by a computer device, and when the program runs on the computer device, the computer device is caused to execute the steps of the above-mentioned state control method for a virtual device.
In this embodiment of the present application, when a target virtual device meets a master-slave switching trigger condition, a network node where the target virtual device is located acquires, from a central node, master-slave state information corresponding to the target virtual device and at least one other virtual device, where the at least one other virtual device and the target virtual device belong to a same virtual network. If it is determined that one master virtual device exists in the target virtual device and at least one other virtual device based on the obtained master-slave state information, and the target virtual device is a slave virtual device, the target virtual device is kept as the slave virtual device, so that when a network congestion occurs, which causes that a network node where the slave virtual device is located cannot receive a virtual routing redundancy protocol message sent by the network node where the master virtual device is located, race selection initiated by multiple slave virtual devices can be effectively avoided, multiple master virtual devices in the same virtual network are further avoided, and a split brain situation is effectively avoided.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise.
Fig. 1 is a schematic diagram of a system architecture according to an embodiment of the present application;
FIG. 2 is a system architecture diagram according to an embodiment of the present application;
fig. 3 is a schematic flowchart of a method for controlling a state of a virtual device according to an embodiment of the present disclosure;
fig. 4 is a schematic flowchart of a method for controlling a state of a virtual device according to an embodiment of the present disclosure;
fig. 5 is a schematic flowchart of a method for controlling a state of a virtual device according to an embodiment of the present disclosure;
fig. 6 is a schematic structural diagram of a state control apparatus for a virtual device according to an embodiment of the present disclosure;
fig. 7 is a schematic structural diagram of a computer device according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more clearly apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
Referring to fig. 1, a system architecture diagram applicable to the embodiment of the present application is shown, where the system architecture diagram at least includes a central node 101, network nodes 102-1, network nodes 102-2, \8230, and network nodes 102-X, where X is an integer greater than 0.
The central node 101 may be an independent physical server, may also be a server cluster or a distributed system formed by a plurality of physical servers, and may also be a cloud server that provides basic cloud computing services such as cloud service, a cloud database, cloud computing, a cloud function, cloud storage, network service, cloud communication, middleware service, domain name service, security service, content Delivery Network (CDN), and a big data and artificial intelligence platform.
The Network nodes 102-1 to 102-X may be independent physical servers, may also be a server cluster or a distributed system formed by a plurality of physical servers, and may also be cloud servers providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content Delivery Networks (CDNs), and big data and artificial intelligence platforms.
The central node 101 is connected to the network nodes 102-1 to 102-X, and may be connected directly or indirectly through wired or wireless communication, which is not limited herein. The network nodes 102-1 and 102-X are connected to each other, and may be connected directly or indirectly through wired or wireless communication, which is not limited herein.
Each network node may be deployed with multiple virtual devices executing the same function, multiple virtual devices executing different functions, and one virtual device, where the virtual device may be a virtual network card, a virtual router, a virtual optical drive, and the like. Virtual devices executing the same function in each network node belong to one virtual network, and virtual devices executing different functions belong to different virtual networks. Only one virtual device in the same virtual network is a master virtual device, and the other virtual devices are slave virtual devices. The master virtual device periodically sends a virtual routing redundancy protocol message to each slave virtual device belonging to the same virtual network so as to inform each slave virtual device of the configuration information and the working state of the master virtual device.
When the network node where each slave virtual device is located does not receive the virtual routing redundancy protocol packet sent by the network node where the master virtual device is located within the preset time length, each slave virtual device initiates the master virtual device election to ensure that the normal execution of the application is not affected, and one slave virtual device is selected from the multiple slave virtual devices to serve as the master virtual device. It should be noted here that, any virtual device sends or receives a message through the network node where the virtual device is located, and details are not described later.
The central node 101 stores master-slave status information for each virtual device in each network node.
For example, as shown in fig. 2, the configuration system architecture includes a central node 101 and 2 network nodes, which are network nodes 102-1 and network nodes 102-2, respectively. It is set that a virtual router 1 and a virtual network card 1 are deployed in the network node 102-1, and a virtual router 2 and a virtual network card 2 are deployed in the network node 102-2. The virtual router 1 and the virtual router 2 belong to a virtual network, and the virtual network card 1 and the virtual network card 2 belong to a virtual network.
The virtual router 1 in the network nodes 102 to 1 is set as a master virtual device, and the virtual router 2 in the network nodes 102 to 2 is set as a slave virtual device. Therefore, the virtual router 1 in the network nodes 102 to 1 completes the application such as the routing corresponding to the router, and the virtual router 2 in the network nodes 102 to 2 is in the backup state and does not execute any application.
The virtual network card 1 in the network node 102-1 is a slave virtual device, and the virtual network card 2 in the network node 102-2 is a master virtual device. Therefore, the virtual network card 2 in the network node 102-2 completes the application such as data encapsulation corresponding to the network card, and the virtual network card 1 in the network node 101-2 is in the backup state and does not execute any application.
The central node 101 stores master-slave status information corresponding to each of the 4 virtual devices, as shown in table 1.
Table 1.
| Virtual appliance | Master-slave status information |
| |
Master virtual device |
| |
Slave virtual device |
| |
Slave virtual device |
| |
Master virtual device |
Based on the system architecture diagram shown in fig. 1, an embodiment of the present application provides a process of a method for controlling a state of a virtual device, where the process is applied to a network node including a target virtual device, and as shown in fig. 3, the process of the method is executed by any one of network nodes 102-1 to 102-X shown in fig. 1, and includes the following steps:
step S301, when the target virtual device meets the master-slave switching trigger condition, the target virtual device and at least one other virtual device, respectively corresponding master-slave status information, are obtained from the central node.
Wherein the at least one other virtual device and the target virtual device belong to the same virtual network.
Specifically, the zookeeper acquires master-slave state information of each virtual device, and reports the master-slave state information to the central node. Meanwhile, the central node may also periodically obtain the operation state information of each network node, including: an active state and a down state.
In a possible case, when the target virtual device is a slave virtual device, if the network node where the target virtual device is located does not receive the virtual routing redundancy protocol packet sent by the network node where the master virtual device is located within a preset time period, the network node where the target virtual device is located obtains, from the central node, the master-slave state information corresponding to the target virtual device and at least one other virtual device.
The preset duration may be a constant value, or may be determined according to a period in which the virtual routing redundancy protocol packet is sent by the master virtual device.
For example, the target virtual device is set as a slave virtual device, and when the network node where the target virtual device is located does not receive the virtual routing redundancy protocol packet sent by the network node where the master virtual device is located within 3 cycles, the network node where the target virtual device is located acquires, from the central node, the master-slave status information corresponding to the target virtual device and the at least one other virtual device.
In another possible case, when the target virtual device is a master virtual device, if the network node where the target virtual device is located receives a virtual routing redundancy protocol packet sent by a network node where another master virtual device is located, the network node where the target virtual device is located obtains, from the central node, the master-slave status information corresponding to the target virtual device and at least one other virtual device, respectively.
For example, the configuration system architecture includes a central node 101 and 3 network nodes, which are network nodes 102-1, network nodes 102-2, and network nodes 102-3, respectively. The network node 102-1 is deployed with a virtual device 1, the network node 102-2 is deployed with a virtual device 2, the network node 102-3 is deployed with a virtual device 3, and the virtual device 1, the virtual device 2 and the virtual device 3 belong to a virtual network.
Assume that virtual device 1 is the master virtual device, virtual device 2 is the master virtual device, and virtual device 3 is the slave virtual device due to several factors. Setting the virtual device 2 as a target virtual device, and when a network node 102-2 where the virtual device 2 is located receives a virtual routing redundancy protocol packet sent by a network node 102-1 where the virtual device 1 is located, the network node 102-2 acquires the virtual device 1, the virtual device 2, and the virtual device 3, and corresponding master-slave status information from the central node.
Step S302, if it is determined that one master virtual device exists in the target virtual device and the at least one other virtual device based on the obtained master-slave status information, and the target virtual device is a slave virtual device, the target virtual device is maintained as the slave virtual device.
For example, the configuration system architecture includes a central node 101 and 3 network nodes, which are network nodes 102-1, network nodes 102-2, and network nodes 102-3, respectively. The virtual device 1 is deployed in the network node 102-1, the virtual device 2 is deployed in the network node 102-2, the virtual device 3 is deployed in the network node 102-3, and the virtual device 1, the virtual device 2 and the virtual device 3 belong to a virtual network.
The virtual device 1 is set as a master virtual device, and the virtual devices 2 and 3 are set as slave virtual devices.
When congestion occurs in the network, the network node 102-2 where the virtual device 2 is located does not receive the virtual routing redundancy protocol packet sent by the network node 102-1 where the virtual device 1 is located within 3 cycles, and then the network node 102-2 acquires the virtual device 1, the virtual device 2, and the virtual device 3, and the master-slave status information corresponding to each of the virtual device 1, the virtual device 2, and the virtual device 3, from the central node. Based on the obtained master-slave status information, it is determined that the virtual device 1 is the master virtual device, and thus it is determined that the master virtual device exists in the current virtual network, so the virtual device 2 is kept unchanged as the slave virtual device.
Similarly, when congestion occurs in the network, which causes the network node 102-3 where the virtual device 3 is located to not receive the virtual routing redundancy protocol packet sent by the network node 102-1 where the virtual device 1 is located within 3 cycles, the network node 102-3 obtains the master-slave status information corresponding to each of the virtual device 1, the virtual device 2, and the virtual device 3 from the central node. Based on the obtained master-slave status information, it is determined that the virtual device 1 is the master virtual device, and thus it is determined that the master virtual device exists in the current virtual network, so the virtual device 3 remains as the slave virtual device.
In this embodiment of the present application, when a target virtual device meets a master-slave switching trigger condition, a network node where the target virtual device is located acquires, from a central node, master-slave state information corresponding to the target virtual device and at least one other virtual device, where the at least one other virtual device and the target virtual device belong to a same virtual network. If it is determined that one master virtual device exists in the target virtual device and at least one other virtual device based on the obtained master-slave state information, and the target virtual device is a slave virtual device, the target virtual device is kept as the slave virtual device, so that when a network congestion occurs, which causes that a network node where the slave virtual device is located cannot receive a virtual routing redundancy protocol message sent by the network node where the master virtual device is located, race selection initiated by multiple slave virtual devices can be effectively avoided, multiple master virtual devices in the same virtual network are further avoided, and a split brain situation is effectively avoided.
Optionally, in the step S302, if it is determined that the master virtual device does not exist in the target virtual device and the at least one other virtual device based on the obtained master-slave status information, it is determined whether to switch the target virtual device to the master virtual device based on the priorities corresponding to the target virtual device and the at least one other virtual device.
Specifically, the priority information corresponding to each of the target virtual device and the at least one other virtual device may be stored in the central node.
The case where the master virtual device does not exist in the same virtual network includes two cases: when the target virtual device and at least one other virtual device just access the virtual network, the target virtual device and the at least one other virtual device do not have a master virtual device; or when the network node where the main virtual device is located is down, the main virtual device does not exist in the target virtual device and the at least one other virtual device.
For whether the target virtual device is switched to the master virtual device, the application provides two optional schemes:
in an optional scheme, if there is a maximum priority in the priorities corresponding to the target virtual device and the at least one other virtual device, and the maximum priority corresponds to the target virtual device, the target virtual device is switched to the master virtual device.
For example, the configuration system architecture includes a central node 101 and 3 network nodes, which are network nodes 102-1, network nodes 102-2, and network nodes 102-3, respectively. The virtual device 1 deployed in the network node 102-1 is a slave virtual device, the virtual device 2 deployed in the network node 102-2 is a slave virtual device, the virtual device 3 deployed in the network node 102-3 is a slave virtual device, and the virtual device 1, the virtual device 2, and the virtual device 3 all belong to a virtual network.
Sequencing the virtual devices according to the sequence of the priorities from large to small, wherein the obtained priority sequencing result is as follows: virtual device 1, virtual device 2, and virtual device 3.
When the virtual device 1 is the target virtual device, the network node 102-1 where the virtual device 1 is located determines that the priority of the virtual device 1 is the maximum according to the priority ranking result, so the virtual device 1 is switched from the slave virtual device to the master virtual device.
When the virtual device 2 is the target virtual device, the network node 102-2 in which the virtual device 2 is located determines that the priority of the virtual device 1 is the maximum according to the priority ranking result, and thus the virtual device 2 is kept as the slave virtual device.
When the virtual device 3 is the target virtual device, the network node 102-3 in which the virtual device 3 is located determines that the priority of the virtual device 1 is the maximum according to the priority ranking result, and thus the virtual device 3 is maintained as the slave virtual device.
In another optional scheme, if at least two maximum priorities that are the same exist in the priorities corresponding to the target virtual device and at least one other virtual device, and one of the at least two maximum priorities corresponds to the target virtual device, it is determined whether the virtual IP address of the target virtual device is greater than the virtual IP addresses of the virtual devices corresponding to the other maximum priorities; if so, switching the target virtual equipment to the main virtual equipment; otherwise, the target virtual device is maintained as the slave virtual device.
Specifically, the virtual IP addresses corresponding to the target virtual device and the at least one other virtual device may be stored in the central node.
For example, the configuration system architecture includes a central node 101 and 3 network nodes, which are network nodes 102-1, network nodes 102-2, and network nodes 102-3, respectively. The virtual device 1 deployed in the network node 102-1 is a slave virtual device, the virtual device 2 deployed in the network node 102-2 is a slave virtual device, the virtual device 3 deployed in the network node 102-3 is a slave virtual device, and the virtual device 1, the virtual device 2 and the virtual device 3 all belong to a virtual network.
The priorities of the virtual device 1 and the virtual device 2 are set to be the same and the maximum, and the priority of the virtual device 3 is set to be the minimum. Meanwhile, the virtual IP addresses corresponding to the virtual device 1, the virtual device 2, and the virtual device 3 are shown in table 2.
Table 2.
| Virtual appliance | Virtual IP address |
| |
10.202.118.101 |
| |
10.202.118.102 |
| Virtual device 3 | 10.202.118.103 |
When the virtual device 1 is a target virtual device, the network node 102-1 where the virtual device 1 is located determines that the priorities of the virtual device 1 and the virtual device 2 are the same and the maximum according to the size relationship of the priorities corresponding to the virtual device 1, the virtual device 2, and the virtual device 3. Further, since the virtual IP address of the virtual device 1 is 10.202.118.101 and the virtual IP address of the virtual device 2 is 10.202.118.102, the virtual IP address of the virtual device 1 is smaller than the virtual IP address of the virtual device 2, and thus the virtual device 1 is maintained as a slave virtual device.
When the virtual device 2 is the target virtual device, the network node 102-2 in which the virtual device 2 is located determines that the priorities of the virtual device 1 and the virtual device 2 are the same and the largest according to the size relationship of the priorities of the virtual device 1, the virtual device 2, and the virtual device 3, and further, switches the virtual device 2 from the slave virtual device to the master virtual device because the virtual IP address of the virtual device 1 is smaller than the virtual IP address of the virtual device 2.
To better explain the embodiment of the present application, when a target virtual device is a slave virtual device and a network node where the target virtual device is located does not receive a virtual routing redundancy protocol packet sent by a network node where a master virtual device is located within a preset time, the embodiment of the present application provides a flow of a state control method for the following virtual devices, as shown in fig. 4:
step S401, obtain the master-slave status information corresponding to the target virtual device and at least one other virtual device from the central node.
Step S402, judging whether a main virtual device exists in the target virtual device and at least one other virtual device based on the obtained master-slave state information, and if so, executing step S403; otherwise, step S404 is performed.
Step S403, the target virtual device is held as the slave virtual device, and the process ends.
Step S404, judging whether the priority corresponding to the target virtual equipment is the maximum priority, if so, executing step S406; otherwise, step S405 is executed.
Step S405, the target virtual device is held as the slave virtual device, and ends.
Step S406, judging whether the priority corresponding to at least one other virtual device is the same as the priority corresponding to the target virtual device, if so, executing step S408; otherwise, step S407 is executed.
Step S407, the target virtual device is switched to the master virtual device, and the process ends.
Step S408, judging whether the virtual IP address of the target virtual equipment is larger than the virtual IP addresses of other virtual equipment with the same priority, if so, executing step S409; otherwise, step S410 is performed.
And step S409, switching the target virtual equipment to the main virtual equipment, and ending.
Step S410, the target virtual device is held as the slave virtual device, and ends.
In the embodiment of the application, when the main virtual device does not exist in each virtual device belonging to the same virtual network, the network node where the target virtual device is located judges according to the respective corresponding priority of each virtual device, and determines the master-slave state of the target virtual device, so that the problem that the main virtual device does not exist in the virtual network when the network node where the main virtual device is located is down is effectively avoided, and the service flow can be quickly recovered.
Optionally, in the step S302, if it is determined that at least two main virtual devices exist in the target virtual device and the at least one other virtual device based on the obtained master-slave status information, the target virtual device is one of the main virtual devices.
In a first possible implementation manner, priorities corresponding to at least two pieces of main virtual equipment are compared, and if the priority corresponding to the target virtual equipment is greater than priorities corresponding to other pieces of main virtual equipment in the at least two pieces of main virtual equipment, the target virtual equipment is kept as the main virtual equipment; otherwise, the target virtual device is switched to the slave virtual device.
For example, the configuration system architecture includes a central node 101 and 3 network nodes, which are network nodes 102-1, network nodes 102-2, and network nodes 102-3, respectively. The method comprises the steps that a network node 102-1 is set to be provided with a virtual device 1, a network node 102-2 is set to be provided with a virtual device 2, a network node 102-3 is provided with a virtual device 3, and the virtual device 1, the virtual device 2 and the virtual device 3 belong to a virtual network.
Assume that virtual device 1 is the master virtual device, virtual device 2 is the master virtual device, and virtual device 3 is the slave virtual device due to some factors. Sequencing the virtual devices according to the sequence of the priorities from large to small, wherein the obtained priority sequencing result is as follows: virtual device 1, virtual device 2, and virtual device 3.
When the virtual device 1 is the target virtual device, the network node 102-1 in which the virtual device 1 is located determines that the priority of the virtual device 1 is greater than that of the virtual device 2 according to the magnitude relationship between the priorities corresponding to the virtual device 1 and the virtual device 2, and thus the virtual device 1 is kept as the master virtual device.
When the virtual device 2 is a target virtual device, the network node 102-2 where the virtual device 2 is located determines that the priority of the virtual device 1 is greater than that of the virtual device 2 according to the magnitude relationship of the priorities corresponding to the virtual device 1 and the virtual device 2, so that the virtual device 2 is switched from the master virtual device to the slave virtual device.
In a second possible implementation manner, the virtual IP addresses of at least two main virtual devices are compared, and if the virtual IP address of the target virtual device is greater than the virtual IP addresses of other main virtual devices in the at least two main virtual devices, the target virtual device is maintained as the main virtual device; otherwise, the target virtual device is switched to the slave virtual device.
For example, the configuration system architecture includes a central node 101 and 3 network nodes, which are network nodes 102-1, network nodes 102-2, and network nodes 102-3, respectively. The method comprises the steps that a network node 102-1 is set to be provided with a virtual device 1, a network node 102-2 is set to be provided with a virtual device 2, a network node 102-3 is provided with a virtual device 3, and the virtual device 1, the virtual device 2 and the virtual device 3 belong to a virtual network.
Assume that virtual device 1 is the master virtual device, virtual device 2 is the master virtual device, and virtual device 3 is the slave virtual device due to some factors. The virtual IP addresses corresponding to the virtual device 1, the virtual device 2, and the virtual device 3 are shown in table 2.
When the virtual device 1 is a target virtual device, the network node where the virtual device 1 is located determines according to the size relationship of the virtual IP addresses corresponding to the virtual device 1 and the virtual device 2, and because the virtual IP address of the virtual device 1 is smaller than the virtual IP address of the virtual device 2, the virtual device 1 is switched from the master virtual device to the slave virtual device.
When the virtual device 2 is a target virtual device, the network node where the virtual device 2 is located determines according to the magnitude relationship of the virtual IP addresses corresponding to the virtual device 1 and the virtual device 2, and since it is determined that the virtual IP address of the virtual device 1 is smaller than the virtual IP address of the virtual device 2, the virtual device 2 is kept unchanged from the master virtual device.
In a third possible implementation manner, priorities corresponding to at least two main virtual devices are compared, if at least two same maximum priorities exist in the priorities corresponding to the at least two main virtual devices and one of the at least two maximum priorities corresponds to the target virtual device, whether a virtual IP address of the target virtual device is larger than virtual IP addresses of virtual devices corresponding to other maximum priorities is determined, and if so, the target virtual device is kept as the main virtual device; otherwise, the target virtual device is switched to the slave virtual device.
For example, the configuration system architecture includes a central node 101 and 3 network nodes, which are network nodes 102-1, network nodes 102-2, and network nodes 102-3, respectively. The method comprises the steps that a network node 102-1 is set to be provided with a virtual device 1, a network node 102-2 is set to be provided with a virtual device 2, a network node 102-3 is provided with a virtual device 3, and the virtual device 1, the virtual device 2 and the virtual device 3 belong to a virtual network.
Assume that virtual device 1 is the master virtual device, virtual device 2 is the master virtual device, and virtual device 3 is the slave virtual device due to some factors. The priorities corresponding to the virtual device 1 and the virtual device 2 are the same and the largest, and the priority corresponding to the virtual device 3 is the smallest. Meanwhile, the virtual IP addresses corresponding to the virtual device 1, the virtual device 2, and the virtual device 3 are shown in table 2.
When the virtual device 1 is a target virtual device, the network node where the virtual device 1 is located determines that the priorities of the virtual device 1 and the virtual device 2 are the same and the largest according to the size relationship of the priorities of the virtual device 1 and the virtual device 2, and therefore, the network node determines that the priorities of the virtual device 1 and the virtual device 2 are the same and the largest according to the size relationship of the virtual IP addresses of the virtual device 1 and the virtual device 2, and because the virtual IP address of the virtual device 1 is smaller than the virtual IP address of the virtual device 2, the virtual device 1 is switched from the master virtual device to the slave virtual device.
When the virtual device 2 is a target virtual device, the network node where the virtual device 2 is located determines that the priorities of the virtual device 1 and the virtual device 2 corresponding to each other are the same and the maximum according to the size relationship of the priorities of the virtual device 1 and the virtual device 2 corresponding to each other, and therefore, according to the size relationship of the virtual IP addresses of the virtual device 1 and the virtual device 2 corresponding to each other, since the virtual IP address of the virtual device 1 is smaller than the virtual IP address of the virtual device 2, the virtual device 2 is maintained as a main virtual device.
To better explain the embodiment of the present application, when a target virtual device is a master virtual device and a network node where the target virtual device is located receives a virtual routing redundancy protocol packet sent by a network node where other master virtual devices are located, the embodiment of the present application provides a process of a state control method for a virtual device, as shown in fig. 5:
step S501, a target virtual device and at least one other virtual device, and their corresponding master-slave status information are obtained from the central node.
Step S502, based on the obtained master-slave state information, judging whether the priority corresponding to the target virtual equipment is the maximum priority, if so, executing step S504; otherwise, step S503 is executed.
In step S503, the target virtual device is switched to the slave virtual device.
Step S504, judge whether there is at least one priority of the main virtual device and priority of the target virtual device the same, if, carry out step S506; otherwise, step S505 is executed.
In step S505, the target virtual device is maintained as the master virtual device.
Step S506, determining whether the virtual IP address of the target virtual device is greater than the virtual IP address of at least one main virtual device with the same priority, if yes, performing step S508; otherwise, step S507 is executed.
In step S507, the target virtual device is switched to the slave virtual device.
Step S508, the target virtual device is maintained as the master virtual device.
In the embodiment of the present application, when at least two main virtual devices exist in each virtual device belonging to one virtual network and a target virtual device is one of the main virtual devices, a network node where the target virtual device is located may determine, according to a priority corresponding to each main virtual device, a master-slave state of the target virtual device; the master-slave state of the target virtual equipment can be determined by judging according to the virtual IP address corresponding to each master virtual equipment; the master-slave state of the target virtual equipment can be determined according to the priority and the virtual IP address corresponding to each master virtual equipment, so that various determination schemes are provided, the accuracy of the master-slave state of the target virtual equipment is enhanced, and the problem of application result error caused by the existence of a plurality of master virtual equipment in the same network is effectively solved.
Based on the same technical concept, an embodiment of the present application provides a state control apparatus for a virtual device, as shown in fig. 6, the apparatus 600 includes:
an obtaining module 601, configured to obtain, from a central node, master-slave status information corresponding to a target virtual device and at least one other virtual device when the target virtual device meets a master-slave switching trigger condition, where the at least one other virtual device and the target virtual device belong to the same virtual network;
a first master-slave switching module 602, configured to, if it is determined that one master virtual device exists in the target virtual device and the at least one other virtual device based on the obtained master-slave status information, and the target virtual device is a slave virtual device, maintain the target virtual device as the slave virtual device.
Optionally, the system further includes a second master-slave switching module 603, specifically configured to:
if it is determined that a master virtual device does not exist in the target virtual device and the at least one other virtual device based on the obtained master-slave state information, determining whether to switch the target virtual device to a master virtual device based on the priorities corresponding to the target virtual device and the at least one other virtual device.
Optionally, the second master-slave switching module 603 is further configured to:
and if a maximum priority exists in the priorities corresponding to the target virtual device and the at least one other virtual device, and the maximum priority corresponds to the target virtual device, switching the target virtual device to a main virtual device.
Optionally, the second master-slave switching module 603 is further configured to:
if the target virtual device and the at least one other virtual device respectively correspond to at least two same maximum priorities, and one of the at least two maximum priorities corresponds to the target virtual device, judging whether the virtual IP address of the target virtual device is larger than the virtual IP addresses of the virtual devices corresponding to the other maximum priorities;
if yes, switching the target virtual equipment to a main virtual equipment;
otherwise, the target virtual device is maintained as a slave virtual device.
Optionally, the master-slave switching triggering condition is that a virtual routing redundancy protocol message sent by the master virtual device is not received within a preset time length.
Optionally, the system further includes a third master-slave switching module 604, specifically configured to:
if it is determined that at least two main virtual devices exist in the target virtual device and the at least one other virtual device based on the obtained master-slave state information, and the target virtual device is one of the main virtual devices, comparing virtual IP addresses of the at least two main virtual devices;
if the virtual IP address of the target virtual device is larger than the virtual IP addresses of other main virtual devices in the at least two main virtual devices, keeping the target virtual device as the main virtual device;
otherwise, switching the target virtual device to the slave virtual device.
Optionally, the at least one other virtual device and the target virtual device are located in different network nodes, each network node comprising at least one virtual device.
Based on the same technical concept, the embodiment of the present application provides a computer device, which may be a terminal or a server, as shown in fig. 7, including at least one processor 701 and a memory 702 connected to the at least one processor, where a specific connection medium between the processor 701 and the memory 702 is not limited in this embodiment of the present application, and the processor 701 and the memory 702 are connected through a bus in fig. 7 as an example. The bus may be divided into an address bus, a data bus, a control bus, etc.
In the embodiment of the present application, the memory 702 stores instructions executable by the at least one processor 701, and the at least one processor 701 may execute the steps included in the method for controlling the state of the virtual device by executing the instructions stored in the memory 702.
The processor 701 is a control center of the computer device, and may connect various parts of the computer device by using various interfaces and lines, and perform state control of the virtual device by executing or executing instructions stored in the memory 702 and calling data stored in the memory 702. Optionally, the processor 701 may include one or more processing units, and the processor 701 may integrate an application processor and a modem processor, wherein the application processor mainly handles an operating system, a user interface, an application program, and the like, and the modem processor mainly handles wireless communication. It will be appreciated that the modem processor described above may not be integrated into the processor 701. In some embodiments, processor 701 and memory 702 may be implemented on the same chip, or in some embodiments, they may be implemented separately on separate chips.
The processor 701 may be a general-purpose processor, such as a Central Processing Unit (CPU), a digital signal processor, an Application Specific Integrated Circuit (ASIC), a field programmable gate array or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or the like, that may implement or perform the methods, steps, and logic blocks disclosed in the embodiments of the present Application. A general purpose processor may be a microprocessor or any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in a processor.
Based on the same inventive concept, embodiments of the present application provide a computer-readable storage medium storing a computer program executable by a computer device, which, when the program runs on the computer device, causes the computer device to execute the steps of the above-described state control method of the virtual device.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application 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, and so forth) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams 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.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.
Claims (10)
1. A method for controlling the state of a virtual device, which is applied to a network node including a target virtual device, includes:
when the target virtual equipment meets a master-slave switching trigger condition, acquiring corresponding master-slave state information of the target virtual equipment and at least one other virtual equipment from a central node, wherein the at least one other virtual equipment and the target virtual equipment belong to the same virtual network;
if it is determined that one master virtual device exists in the target virtual device and the at least one other virtual device based on the obtained master-slave state information, and the target virtual device is a slave virtual device, the target virtual device is kept as the slave virtual device.
2. The method of claim 1, further comprising:
if it is determined that a master virtual device does not exist in the target virtual device and the at least one other virtual device based on the obtained master-slave state information, determining whether to switch the target virtual device to a master virtual device based on the priorities corresponding to the target virtual device and the at least one other virtual device.
3. The method of claim 2, wherein the determining whether to switch the target virtual device to a master virtual device based on the priorities corresponding to the target virtual device and the at least one other virtual device, respectively, comprises:
and if a maximum priority exists in the priorities corresponding to the target virtual device and the at least one other virtual device, and the maximum priority corresponds to the target virtual device, switching the target virtual device to a main virtual device.
4. The method of claim 2, wherein the determining whether to switch the target virtual device to a master virtual device based on the priorities of the target virtual device and the at least one other virtual device, respectively, comprises:
if the target virtual device and the at least one other virtual device respectively correspond to at least two same maximum priorities, and one of the at least two maximum priorities corresponds to the target virtual device, judging whether the virtual IP address of the target virtual device is larger than the virtual IP addresses of the virtual devices corresponding to the other maximum priorities;
if yes, switching the target virtual equipment to main virtual equipment;
otherwise, the target virtual device is maintained as a slave virtual device.
5. The method according to claim 1, wherein the master-slave switching trigger condition is that a virtual routing redundancy protocol packet sent by a master virtual device is not received within a preset time length.
6. The method of claim 1, further comprising:
if it is determined that at least two main virtual devices exist in the target virtual device and the at least one other virtual device based on the obtained master-slave state information, and the target virtual device is one of the main virtual devices, comparing virtual IP addresses of the at least two main virtual devices;
if the virtual IP address of the target virtual device is larger than the virtual IP addresses of other main virtual devices in the at least two main virtual devices, keeping the target virtual device as the main virtual device;
otherwise, switching the target virtual device to the slave virtual device.
7. The method of any of claims 1 to 6, wherein the at least one other virtual device and the target virtual device are located in different network nodes, each network node comprising at least one virtual device.
8. A state control apparatus for a virtual device, comprising:
an obtaining module, configured to obtain, from a central node, master-slave state information corresponding to a target virtual device and at least one other virtual device when the target virtual device meets a master-slave switching trigger condition, where the at least one other virtual device and the target virtual device belong to a same virtual network;
and the master-slave switching module is used for keeping the target virtual device as a slave virtual device if the target virtual device and the at least one other virtual device have one master virtual device based on the obtained master-slave state information and the target virtual device is the slave virtual device.
9. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the steps of the method of any one of claims 1 to 7 when executing the program.
10. A computer-readable storage medium, having stored thereon a computer program executable by a computer device, the program, when executed on the computer device, causing the computer device to perform the steps of the method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111458135.9A CN114285795B (en) | 2021-12-02 | 2021-12-02 | State control method, device, equipment and storage medium of virtual equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111458135.9A CN114285795B (en) | 2021-12-02 | 2021-12-02 | State control method, device, equipment and storage medium of virtual equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114285795A CN114285795A (en) | 2022-04-05 |
| CN114285795B true CN114285795B (en) | 2023-01-31 |
Family
ID=80870523
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111458135.9A Active CN114285795B (en) | 2021-12-02 | 2021-12-02 | State control method, device, equipment and storage medium of virtual equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114285795B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115086219B (en) * | 2022-05-31 | 2024-04-09 | 深信服科技股份有限公司 | Virtual router determining method, device and computer readable storage medium |
| CN115296983A (en) * | 2022-08-03 | 2022-11-04 | 青岛海信微联信号有限公司 | Equipment management method and device, electronic equipment and storage medium |
| CN115665035A (en) * | 2022-10-27 | 2023-01-31 | 深信服科技股份有限公司 | Information processing method and device, first node and storage medium |
| CN115967669B (en) * | 2023-03-16 | 2023-06-27 | 北京志凌海纳科技有限公司 | VRRP (virtual router redundancy protocol) expansion protocol-based brain crack inhibition method and device |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1929324A (en) * | 2006-10-17 | 2007-03-14 | 杭州华为三康技术有限公司 | Master-salve switching method and system for mutual backup device |
| CN101702681A (en) * | 2009-11-26 | 2010-05-05 | 福建星网锐捷网络有限公司 | Switching method and device of main/standby router in virtual route redundancy protocol |
| WO2012109941A1 (en) * | 2011-02-15 | 2012-08-23 | 中兴通讯股份有限公司 | Redundancy backup method and system in trill network |
| CN105681187A (en) * | 2014-11-18 | 2016-06-15 | 华为技术有限公司 | VRRP (Virtual Router Redundancy Protocol) backup set management method and related device |
| CN112422422A (en) * | 2020-11-23 | 2021-02-26 | 浪潮思科网络科技有限公司 | Network redundancy method, device and equipment |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7603480B2 (en) * | 2004-09-16 | 2009-10-13 | Nec Corporation | System using pseudo redundant configurator to switch network devices between operating and standby states |
| US8514854B2 (en) * | 2009-06-11 | 2013-08-20 | Brocade Communications Systems, Inc. | Virtual router redundancy for server virtualization |
| CN102546430A (en) * | 2012-02-05 | 2012-07-04 | 华为技术有限公司 | Method for redundant backup of network equipment, and routing equipment and system |
| CN107846358B (en) * | 2016-09-19 | 2020-07-10 | 北京金山云网络技术有限公司 | Data transmission method, device and network system |
| CN112187533B (en) * | 2020-09-18 | 2023-04-18 | 北京浪潮数据技术有限公司 | Virtual network equipment defense method, device, electronic equipment and medium |
-
2021
- 2021-12-02 CN CN202111458135.9A patent/CN114285795B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1929324A (en) * | 2006-10-17 | 2007-03-14 | 杭州华为三康技术有限公司 | Master-salve switching method and system for mutual backup device |
| CN101702681A (en) * | 2009-11-26 | 2010-05-05 | 福建星网锐捷网络有限公司 | Switching method and device of main/standby router in virtual route redundancy protocol |
| WO2012109941A1 (en) * | 2011-02-15 | 2012-08-23 | 中兴通讯股份有限公司 | Redundancy backup method and system in trill network |
| CN105681187A (en) * | 2014-11-18 | 2016-06-15 | 华为技术有限公司 | VRRP (Virtual Router Redundancy Protocol) backup set management method and related device |
| CN112422422A (en) * | 2020-11-23 | 2021-02-26 | 浪潮思科网络科技有限公司 | Network redundancy method, device and equipment |
Non-Patent Citations (1)
| Title |
|---|
| Bidirectional Forwarding Detection (BFD) for Multi-point Networks and Virtual Router Redundancy Protocol (VRRP) Use Case draft-mirsky-bfd-p2mp-vrrp-use-case-04;G. Mirsky等;《IETF 》;20200727;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114285795A (en) | 2022-04-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN114285795B (en) | State control method, device, equipment and storage medium of virtual equipment | |
| CN109344014B (en) | Main/standby switching method and device and communication equipment | |
| US10198338B2 (en) | System and method of generating data center alarms for missing events | |
| CN109981493B (en) | Method and device for configuring virtual machine network | |
| WO2015196686A1 (en) | Data storage method and data storage management server | |
| US10216593B2 (en) | Distributed processing system for use in application migration | |
| US11388109B2 (en) | Hierarchical capacity management in a virtualization environment | |
| CN112217727B (en) | Multi-metric-dimension routing method and device, computer equipment and storage medium | |
| CN113489149B (en) | Power grid monitoring system service master node selection method based on real-time state sensing | |
| CN111580959B (en) | Data writing method, data writing device, server and storage medium | |
| US20150372895A1 (en) | Proactive Change of Communication Models | |
| US10951732B2 (en) | Service processing method and device | |
| CN112055347A (en) | Multi-gateway cooperative work method and system | |
| US10735248B2 (en) | Cloudified N-way routing protection at hyper scale | |
| CN114422427B (en) | Flow balancing method and device, electronic equipment and storage medium | |
| CN107332771B (en) | Method for guaranteeing routing consistency, router and routing system | |
| CN110932878A (en) | Management method, equipment and system of distributed network | |
| CN109617779A (en) | Routing table maintenance method and device based on VTEP | |
| CN112637053B (en) | Method and device for determining backup forwarding path of route | |
| CN113783751A (en) | Method, electronic device and medium for detecting user broadband quality | |
| US10567507B2 (en) | Message processing method and apparatus, and message processing system | |
| CN113452766B (en) | Node switching method and device, storage medium and electronic device | |
| CN110958182B (en) | Communication method and related equipment | |
| US9960957B2 (en) | Methods for prioritizing failover of logical interfaces (LIFs) during a node outage and devices thereof | |
| CN109218206B (en) | Method and device for limiting link state advertisement quantity |
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 |