CN116346585A - Cloud-protogenesis-based network fault self-repairing method and system - Google Patents
Cloud-protogenesis-based network fault self-repairing method and system Download PDFInfo
- Publication number
- CN116346585A CN116346585A CN202310236532.4A CN202310236532A CN116346585A CN 116346585 A CN116346585 A CN 116346585A CN 202310236532 A CN202310236532 A CN 202310236532A CN 116346585 A CN116346585 A CN 116346585A
- Authority
- CN
- China
- Prior art keywords
- network
- detector
- detection
- connection
- probe
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 37
- 238000011084 recovery Methods 0.000 claims abstract description 32
- 238000001514 detection method Methods 0.000 claims description 75
- 239000000523 sample Substances 0.000 claims description 58
- 230000000903 blocking effect Effects 0.000 claims description 20
- 238000004590 computer program Methods 0.000 claims description 13
- 230000002159 abnormal effect Effects 0.000 claims description 4
- 230000000977 initiatory effect Effects 0.000 claims 1
- 230000006870 function Effects 0.000 description 4
- 238000004891 communication Methods 0.000 description 3
- 238000010586 diagram Methods 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 230000003213 activating effect Effects 0.000 description 2
- 238000012937 correction Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 241001212789 Dynamis Species 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
- H04L41/0663—Performing the actions predefined by failover planning, e.g. switching to standby network elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/12—Avoiding congestion; Recovering from congestion
- H04L47/125—Avoiding congestion; Recovering from congestion by balancing the load, e.g. traffic engineering
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/50—Reducing energy consumption in communication networks in wire-line communication networks, e.g. low power modes or reduced link rate
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Health & Medical Sciences (AREA)
- Cardiology (AREA)
- General Health & Medical Sciences (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a cloud-protogenesis-based network fault self-repairing method and a cloud-protogenesis-based network fault self-repairing system, which are characterized in that a starting detector is used for detecting target network equipment, a network detector is started for detecting, and if the network detector is continuously blocked, the network detector continuously detects; and if the network detector is blocked, reselecting connection and switching, detecting whether the current detector is in the default gateway equipment while starting the network detector to detect, if not, starting the recovery detector to detect, judging whether the default gateway equipment network is reachable, and if so, switching connection to be the default gateway equipment. According to the scheme, when the default network outlet of the cluster fails, the access of the cluster to the outside is interrupted, the optimal network outlet is selected, and the normal access of the cluster to the outside is ensured; when the default network outlet fault is released, the network outlet needs to be restored to an initial state, other outlet bandwidths are not occupied, and a network fault self-repairing function is achieved.
Description
Technical Field
The application relates to the technical field of network fault self-repairing based on cloud primordia, in particular to a network fault self-repairing method and system based on cloud primordia.
Background
With the development and popularization of cloud protogenesis technology, enterprises using cloud protogenesis are increasing, and the requirements of the enterprises on networks are also becoming more complex. When the traffic of the cluster is continuously expanded, the requirement of the traffic on the network stability is higher, and when the network outlet of the cluster fails, the system capable of self-repairing can meet the current requirement. Load balancing is generally used at present to ensure network stability of a cluster, so that all requests can be accessed to a service.
Load balancing is to balance and split loads on a plurality of operation units to run, such as an FTP server, a Web server, an enterprise core application server, other main task servers and the like, so as to cooperatively complete work tasks.
The existing load balancing common hardware comprises a relatively expensive F5 and Array commercial load balancer, the software comprises ngi nx, LVS and HAproxy, but the hardware is quite expensive, the hardware is not suitable for small projects, the load balancing of the software has respective advantages and disadvantages, and the existing load balancing can only ensure the stability of a cluster entrance network and cannot ensure the accessibility of a cluster exit network.
Disclosure of Invention
Based on the above technical problems, the invention provides a network fault self-repairing method and a system based on cloud protogenesis, and the control program part of the invention operates in the cloud protogenesis environment, which has high reliability, thereby ensuring the high reliability of the life heart of the system, solving the problems that the existing load balance can only ensure the stability of the cluster entrance network and can not ensure the accessibility of the cluster exit network under the double guarantee of the high reliability of the system itself and the high reliability of the network exit, thereby ensuring the stable and reliable operation of the cluster
In a first aspect, a cloud-protogenesis-based network fault self-repair method includes:
starting a detector to detect the target network equipment;
starting a network detector to detect, and if the network detector is continuously blocked, continuously detecting by the network detector; if the network detector is blocked, reselecting connection and switching to end the detection;
detecting whether the current detector is in a default gateway device or not while starting the network detector to detect, if not, starting a recovery detector to detect, judging whether the default gateway device network is reachable, if so, switching connection to the default gateway device, and ending the detection;
and restarting the next detection after finishing the detection.
In the above solution, optionally, before the start-up detector detects the target network device, the method includes: detecting all connections of the target network device, and if the connections are more than two, starting a detector;
and recording the current position of the probe, wherein the default initial position of the probe is the default gateway equipment connection, and the probe records the position of the current connection, and the default initial position is on the default gateway equipment connection.
In the above solution, further optionally, the starting the network probe to detect, if the network probe is continuously blocked, the network probe continuously detects includes:
after the network detector is started to detect, the network detector is connected to the current record probe position; wherein the network probe is connected to a service where the currently recorded probe position is located;
the network detector continuously detects whether the current network outlet network is normal or not on the connected target service, if the current network outlet network is abnormal, the blocking is released, and the blocking of the network detector is ended.
In the above solution, further optionally, if the network probe blocks, the reselecting the connection and switching, and ending the current probe includes:
the network detector blocking ending specifically comprises: when the current connection is wrong, the recovery detector detects that the network of the main connection is recovered, or the network detector detects that the service network of the current connection is not reachable.
In the above solution, further optionally, the reselecting connection and switching ends the detection, specifically: and selecting the fastest network connection from all the connections of the target network equipment, switching and recording the probe positions.
In the above solution, further optionally, the starting the recovery detector to detect, determine whether the default gateway device network is reachable, if yes, switch connection to the default gateway device, and end the detection includes:
if the recovery detector is continuously blocked, the recovery detector continuously detects; and if the blocking of the recovery detector is finished, judging whether the default gateway equipment network is reachable, switching connection to the default gateway equipment, and finishing the detection.
In the above solution, further optionally, restarting the next detection after ending the present detection includes:
the next detection is to start the detector to detect the target network equipment;
starting a network detector to detect, and if the network detector is continuously blocked, continuously detecting by the network detector; if the network detector is blocked, reselecting connection and switching to end the detection;
detecting whether the current detector is in a default gateway device or not while starting the network detector to detect, if not, starting a recovery detector to detect, judging whether the default gateway device network is reachable, if so, switching connection to the default gateway device, and ending the detection;
and restarting the next detection after finishing the detection.
In a second aspect, a cloud-proto-based network failure self-repair system, the system comprising:
and a starting module: the method comprises the steps of starting a detector to detect target network equipment;
a first detection module: the network detector is used for starting the network detector to detect, and if the network detector is continuously blocked, the network detector continuously detects; if the network detector is blocked, reselecting connection and switching to end the detection;
and a second detection module: the network detector is used for detecting whether the current detector is in a default gateway device or not while starting the network detector to detect, if not, starting a recovery detector to detect, judging whether the default gateway device network is reachable, if so, switching connection to the default gateway device, and ending the detection;
and (3) a circulation module: for restarting the next detection after ending the detection.
In a third aspect, a computer device comprises a memory storing a computer program and a processor implementing the following steps when executing the computer program:
starting a detector to detect the target network equipment;
starting a network detector to detect, and if the network detector is continuously blocked, continuously detecting by the network detector; if the network detector is blocked, reselecting connection and switching to end the detection;
detecting whether the current detector is in a default gateway device or not while starting the network detector to detect, if not, starting a recovery detector to detect, judging whether the default gateway device network is reachable, if so, switching connection to the default gateway device, and ending the detection;
and restarting the next detection after finishing the detection.
In a fourth aspect, a computer readable storage medium having stored thereon a computer program which when executed by a processor performs the steps of:
starting a detector to detect the target network equipment;
starting a network detector to detect, and if the network detector is continuously blocked, continuously detecting by the network detector; if the network detector is blocked, reselecting connection and switching to end the detection;
detecting whether the current detector is in a default gateway device or not while starting the network detector to detect, if not, starting a recovery detector to detect, judging whether the default gateway device network is reachable, if so, switching connection to the default gateway device, and ending the detection;
and restarting the next detection after finishing the detection.
The invention has at least the following beneficial effects:
based on further analysis and research on the problems in the prior art, the invention recognizes that the existing load balancing can only ensure the stability of the cluster entrance network and can not ensure the accessibility of the cluster exit network; and if the network detector is blocked, reselecting connection and switching, ending the detection, detecting whether the current detector is in a default gateway device while starting the network detector to detect, if not, starting a recovery detector to detect, judging whether the default gateway device network is reachable, and if so, switching connection to the default gateway device, ending the detection. According to the scheme, once a default network outlet of the cluster fails, the access of the cluster to the outside is interrupted, an optimal network outlet is selected, and the normal access of the cluster to the outside is ensured; when the default network outlet fault is released, the network outlet needs to be restored to an initial state, other outlet bandwidths are not occupied, and a network fault self-repairing function is achieved.
And in the normal running process of the cluster, once the network outlet of the cluster is found to be faulty, the network outlet is immediately responded, and the network outlet is drifted to the optimal network outlet. And after the default network outlet fault is relieved, the initial configuration state is restored. The invention not only can be compatible with external load balance, but also can ensure the high reliability of own service and the self-correction of network faults.
Furthermore, the probe program runs in a cloud native environment, and has high reliability, so that the life and high reliability of the target system is ensured.
Drawings
Fig. 1 is a flow chart of a network fault self-repairing method based on cloud protogenesis according to an embodiment of the present invention;
fig. 2 is a schematic diagram of a processing procedure of a network failure self-repairing method based on cloud protogenesis according to an embodiment of the present invention;
FIG. 3 is an internal block diagram of a computer device in one embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application will be further described in detail with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the present application.
The network fault self-repairing method based on cloud protogenesis, as shown in fig. 1 and fig. 2, comprises the following steps:
starting a detector to detect the target network equipment;
starting a network detector to detect, and if the network detector is continuously blocked, continuously detecting by the network detector; if the network detector is blocked, reselecting connection and switching to end the detection;
detecting whether the current detector is in a default gateway device or not while starting the network detector to detect, if not, starting a recovery detector to detect, judging whether the default gateway device network is reachable, if so, switching connection to the default gateway device, and ending the detection;
and restarting the next detection after finishing the detection.
The main function of the embodiment is a network fault self-repairing system based on cloud primordia. The adoption of containerization automatic deployment ensures availability, elastic expansion and support of continuous delivery, and conforms to the concept of cloud primordia. The network availability is the key for ensuring the efficient and stable operation of the service, the invention is provided for solving the pain that the default gateway network is not enabled, and the service in the cluster can better complete the work only by entering and exiting.
In one embodiment, the enabling the probe to probe the target network device includes: detecting all connections of the target network device, and if the connections are more than two, starting a detector;
and recording the current position of the probe, wherein the default initial position of the probe is the default gateway equipment connection, and the probe records the position of the current connection, and the default initial position is on the default gateway equipment connection.
In one embodiment, the enabling the network probe to detect, if the network probe is continuously blocking, the network probe continuously detecting includes:
after the network detector is started to detect, the network detector is connected to the current record probe position; wherein the network probe is connected to a service where the currently recorded probe position is located;
the network detector continuously detects whether the current network outlet network is normal or not on the connected target service, if the current network outlet network is abnormal, the blocking is released, and the blocking of the network detector is ended.
In one embodiment, if the network probe blocks, the connection is reselected and switched, and ending the probe includes:
the network detector blocking ending specifically comprises: when the current connection is wrong, the recovery detector detects that the network of the main connection is recovered, or the network detector detects that the service network of the current connection is not reachable.
In one embodiment, the connection reselection and the handover are finished, specifically: and selecting the fastest network connection from all the connections of the target network equipment, switching and recording the probe positions.
In one embodiment, the starting the recovery detector detects, determines whether the default gateway device network is reachable, if yes, switches connection to the default gateway device, and ends the detection includes:
if the recovery detector is continuously blocked, the recovery detector continuously detects; and if the blocking of the recovery detector is finished, judging whether the default gateway equipment network is reachable, switching connection to the default gateway equipment, and finishing the detection.
In one embodiment, restarting the next probe after ending the present probe includes:
the next detection is to start the detector to detect the target network equipment;
starting a network detector to detect, and if the network detector is continuously blocked, continuously detecting by the network detector; if the network detector is blocked, reselecting connection and switching to end the detection;
detecting whether the current detector is in a default gateway device or not while starting the network detector to detect, if not, starting a recovery detector to detect, judging whether the default gateway device network is reachable, if so, switching connection to the default gateway device, and ending the detection;
and restarting the next detection after finishing the detection.
Through the scheme of the embodiment, once a default network outlet of the cluster fails, the access of the cluster to the outside is interrupted, and the optimal network outlet is selected, so that the normal access of the cluster to the outside is ensured; when the default network outlet fault is released, the network outlet needs to be restored to an initial state, other outlet bandwidths are not occupied, and a network fault self-repairing function is achieved. And in the normal running process of the cluster, once the network outlet of the cluster is found to be faulty, the network outlet is immediately responded, and the network outlet is drifted to the optimal network outlet. And after the default network outlet fault is relieved, the initial configuration state is restored. The invention not only can be compatible with external load balance, but also can ensure the high reliability of own service and the self-correction of network faults.
In one embodiment, a method for supporting cloud native network fault self-repairing is provided, in a cluster, once a default network outlet of the cluster fails, external access of the cluster is interrupted, and then an optimal network outlet needs to be selected to ensure that external access of the cluster is normal. When the default network outlet fault is released, the network outlet needs to be restored to an initial state, other outlet bandwidths are not occupied, and a network fault self-repairing function is achieved.
The network fault self-repairing method supporting cloud protogenesis described in this embodiment has several essential terms to be described:
the main connection: the current service location is the core location, and other connections are all imported.
Probe position: recording the position of the current connection, and defaulting the initial position to the main connection
Network probe: connecting to the service where the currently recorded probe position is located
Restoring the detector: the precondition for activating the restoration detector is that the probe location is not on the primary connection, and after activating the restoration detector, it is detected every thirty seconds whether the primary connection network is restored
As shown in fig. 2, the process flow of the multi-WAN port failover method of the present invention requires that the network probe and the recovery probe work cooperatively.
Resume the main operation of the detector: it is detected whether the primary connection network is restored.
And (5) recovering: and restoring the default gateway to a default state and ending the current blocking.
Unrecovered: and ending the detection and continuing the next detection.
The method comprises the following steps
Step one: start detector
Before the detector is started, some preparation work is carried out, if the detection passes, the detector is started, and the preparation work is as follows:
the number of connections is detected, and if more than two connections are made, the detector is activated, the purpose of the detection being to ensure that there is a target that can be diverted when a fault occurs.
The current position of the probe is recorded, and the default initial position is the first connection and the most dominant connection.
Judging whether the current probe is in the initial position or not, if not, starting a recovery detector, so that the recovery to the default state can be ensured when the main connection is recovered
Step two: the network reachable probe is activated and this probe will be connected to the current recorded probe position.
Step three: in the starting detection and blocking, the network detector is blocked after being started, and the main detection work is on the connected service at this time, and the service can always detect whether the current network outlet network is normal or not, and once abnormal network outlet network is found, blocking is released immediately.
Step four: the blocking ends, and three main cases are as follows:
when the current connection is wrong, blocking is finished;
when the recovery detector detects that the network which is mainly connected is recovered, the blocking is actively ended;
the network detector also ends the blocking when it detects that the currently connected serving network is not reachable.
Step five: switching the position of the record probe, and when the network detector is blocked, selecting the fastest new connection of the network, and switching the position of the record probe;
after the network detector is restored to stop, the recorded probe position is restored to an initial value.
Step six: ending the detection; after the detection is finished, the next detection is performed, and the same is performed, so that the whole network is ensured to be available.
It should be understood that, although the steps in the flowchart of fig. 1 are shown in sequence as indicated by the arrows, the steps are not necessarily performed in sequence as indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least a portion of the steps in fig. 1 may include a plurality of steps or stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of the steps or stages is not necessarily sequential, but may be performed in rotation or alternatively with at least a portion of the steps or stages in other steps or other steps.
In one embodiment, a cloud native based network failure self-repair system is provided, comprising the following program modules:
and a starting module: the method comprises the steps of starting a detector to detect target network equipment;
a first detection module: the network detector is used for starting the network detector to detect, and if the network detector is continuously blocked, the network detector continuously detects; if the network detector is blocked, reselecting connection and switching to end the detection;
and a second detection module: the network detector is used for detecting whether the current detector is in a default gateway device or not while starting the network detector to detect, if not, starting a recovery detector to detect, judging whether the default gateway device network is reachable, if so, switching connection to the default gateway device, and ending the detection;
and (3) a circulation module: for restarting the next detection after ending the detection.
For specific limitations regarding the cloud-based network failure self-repair system, reference may be made to the above limitation of the cloud-based network failure self-repair method, and no further description is given here. The above-described cloud-proto-based network failure self-repair system may be implemented in whole or in part by software, hardware, and combinations thereof. The above modules may be embedded in hardware or may be independent of a processor in the computer device, or may be stored in software in a memory in the computer device, so that the processor may call and execute operations corresponding to the above modules.
In one embodiment, a computer device is provided, which may be a terminal, and the internal structure of which may be as shown in fig. 3. The computer device includes a processor, a memory, a communication interface, a display screen, and an input system connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The communication interface of the computer device is used for communicating with an external terminal in a wired or wireless manner, and the wireless manner can be realized through WIF I, an operator network, NFC (near field communication) or other technologies. The computer program, when executed by a processor, implements a cloud-protogenesis-based network fault self-repair method. The display screen of the computer equipment can be a liquid crystal display screen or an electronic ink display screen, and the input system of the computer equipment can be a touch layer covered on the display screen, can also be keys, a track ball or a touch pad arranged on the shell of the computer equipment, and can also be an external keyboard, a touch pad or a mouse and the like.
It will be appreciated by those skilled in the art that the structure shown in fig. 3 is merely a block diagram of some of the structures associated with the present application and is not limiting of the computer device to which the present application may be applied, and that a particular computer device may include more or fewer components than shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, a computer device is provided, including a memory and a processor, the memory having stored therein a computer program, involving all or part of the flow of the methods of the embodiments described above.
In one embodiment, a computer readable storage medium having a computer program stored thereon is provided, involving all or part of the flow of the methods of the embodiments described above.
Those skilled in the art will appreciate that implementing all or part of the above described methods may be accomplished by way of a computer program stored on a non-transitory computer readable storage medium, which when executed, may comprise the steps of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in embodiments provided herein may include at least one of non-volatile and volatile memory. The nonvolatile Memory may include Read-only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical Memory, etc. Volatile memory can include random access memory (Random Access Memory, RAM) or external cache memory. By way of illustration, and not limitation, RAM can be in the form of a variety of forms, such as static random access memory (Stat i c Random Access Memory, SRAM) or dynamic random access memory (Dynami c Random Access Memory, DRAM), and the like.
The technical features of the above embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the description.
The above examples merely represent a few embodiments of the present application, which are described in more detail and are not to be construed as limiting the scope of the invention. It should be noted that it would be apparent to those skilled in the art that various modifications and improvements could be made without departing from the spirit of the present application, which would be within the scope of the present application. Accordingly, the scope of protection of the present application is to be determined by the claims appended hereto.
Claims (10)
1. A cloud-protogenesis-based network fault self-repair method, the method comprising:
starting a detector to detect the target network equipment;
starting a network detector to detect, and if the network detector is continuously blocked, continuously detecting by the network detector; if the network detector is blocked, reselecting connection and switching to end the detection;
detecting whether the current detector is in a default gateway device or not while starting the network detector to detect, if not, starting a recovery detector to detect, judging whether the default gateway device network is reachable, if so, switching connection to the default gateway device, and ending the detection;
and restarting the next detection after finishing the detection.
2. The method of claim 1, wherein the enabling the probe to probe the target network device is preceded by: detecting all connections of the target network device, and if the connections are more than two, starting a detector;
and recording the current position of the probe, wherein the default initial position of the probe is the default gateway equipment connection, and the probe records the position of the current connection, and the default initial position is on the default gateway equipment connection.
3. The method of claim 2, wherein the enabling network probe detection, if the network probe continues to block, the network probe continuing to detect comprises:
after the network detector is started to detect, the network detector is connected to the current record probe position; wherein the network probe is connected to a service where the currently recorded probe position is located;
the network detector continuously detects whether the current network outlet network is normal or not on the connected target service, if the current network outlet network is abnormal, the blocking is released, and the blocking of the network detector is ended.
4. A method according to claim 3, wherein if the network probe congestion ends, then reselecting the connection and switching, and ending the current probe comprises:
the network detector blocking ending specifically comprises: when the current connection is wrong, the recovery detector detects that the network of the main connection is recovered, or the network detector detects that the service network of the current connection is not reachable.
5. The method according to claim 4, wherein the reselecting the connection and switching ends the detection, specifically: and selecting the fastest network connection from all the connections of the target network equipment, switching and recording the probe positions.
6. The method of claim 5, wherein the initiating a recovery detector detects, determining whether the default gateway device network is reachable, if so, switching connection to the default gateway device, and ending the detection comprises:
if the recovery detector is continuously blocked, the recovery detector continuously detects; and if the blocking of the recovery detector is finished, judging whether the default gateway equipment network is reachable, switching connection to the default gateway equipment, and finishing the detection.
7. The method of claim 1, wherein restarting the next probe after ending the present probe comprises:
the next detection is to start the detector to detect the target network equipment;
starting a network detector to detect, and if the network detector is continuously blocked, continuously detecting by the network detector; if the network detector is blocked, reselecting connection and switching to end the detection;
detecting whether the current detector is in a default gateway device or not while starting the network detector to detect, if not, starting a recovery detector to detect, judging whether the default gateway device network is reachable, if so, switching connection to the default gateway device, and ending the detection;
and restarting the next detection after finishing the detection.
8. A cloud-proto-based network failure self-repair system, the system comprising:
and a starting module: the method comprises the steps of starting a detector to detect target network equipment;
a first detection module: the network detector is used for starting the network detector to detect, and if the network detector is continuously blocked, the network detector continuously detects; if the network detector is blocked, reselecting connection and switching to end the detection;
and a second detection module: the network detector is used for detecting whether the current detector is in a default gateway device or not while starting the network detector to detect, if not, starting a recovery detector to detect, judging whether the default gateway device network is reachable, if so, switching connection to the default gateway device, and ending the detection;
and (3) a circulation module: for restarting the next detection after ending the detection.
9. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor implements the steps of the method of any of claims 1 to 7 when the computer program is executed.
10. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310236532.4A CN116346585A (en) | 2023-03-13 | 2023-03-13 | Cloud-protogenesis-based network fault self-repairing method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310236532.4A CN116346585A (en) | 2023-03-13 | 2023-03-13 | Cloud-protogenesis-based network fault self-repairing method and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116346585A true CN116346585A (en) | 2023-06-27 |
Family
ID=86888787
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310236532.4A Pending CN116346585A (en) | 2023-03-13 | 2023-03-13 | Cloud-protogenesis-based network fault self-repairing method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116346585A (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101958831A (en) * | 2010-06-10 | 2011-01-26 | 福建星网锐捷网络有限公司 | Ethernet ring network failure recovery method, Ethernet ring network and switching equipment |
| CN102238067A (en) * | 2010-04-28 | 2011-11-09 | 杭州华三通信技术有限公司 | Switching method and device on Rapid Ring Protection Protocol (RRPP) ring |
| CN108881070A (en) * | 2018-09-12 | 2018-11-23 | 盛科网络（苏州）有限公司 | Method and apparatus for the selection port in Smart Link group |
| CN112202712A (en) * | 2020-08-26 | 2021-01-08 | 广东网堤信息安全技术有限公司 | Service recovery method based on distributed health state detection in cloud protection field |
| CN114257500A (en) * | 2021-12-24 | 2022-03-29 | 苏州浪潮智能科技有限公司 | Fault switching method, system and device for internal network of super-converged cluster |
| CN114884806A (en) * | 2022-04-01 | 2022-08-09 | 国网浙江省电力有限公司杭州供电公司 | Loop identification and blocking method based on high aggregation scene |
-
2023
- 2023-03-13 CN CN202310236532.4A patent/CN116346585A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102238067A (en) * | 2010-04-28 | 2011-11-09 | 杭州华三通信技术有限公司 | Switching method and device on Rapid Ring Protection Protocol (RRPP) ring |
| CN101958831A (en) * | 2010-06-10 | 2011-01-26 | 福建星网锐捷网络有限公司 | Ethernet ring network failure recovery method, Ethernet ring network and switching equipment |
| CN108881070A (en) * | 2018-09-12 | 2018-11-23 | 盛科网络（苏州）有限公司 | Method and apparatus for the selection port in Smart Link group |
| CN112202712A (en) * | 2020-08-26 | 2021-01-08 | 广东网堤信息安全技术有限公司 | Service recovery method based on distributed health state detection in cloud protection field |
| CN114257500A (en) * | 2021-12-24 | 2022-03-29 | 苏州浪潮智能科技有限公司 | Fault switching method, system and device for internal network of super-converged cluster |
| CN114884806A (en) * | 2022-04-01 | 2022-08-09 | 国网浙江省电力有限公司杭州供电公司 | Loop identification and blocking method based on high aggregation scene |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108984349B (en) | Method and device for electing master node, medium and computing equipment | |
| CN105204979A (en) | Recording method of Android logs and mobile terminal | |
| US7657734B2 (en) | Methods and apparatus for automatically multi-booting a computer system | |
| CN112596960A (en) | Distributed storage service switching method and device | |
| US8015432B1 (en) | Method and apparatus for providing computer failover to a virtualized environment | |
| CN111181780A (en) | HA cluster-based host pool switching method, system, terminal and storage medium | |
| CN113377702B (en) | Method and device for starting two-node cluster, electronic equipment and storage medium | |
| CN105959145B (en) | A kind of method and system for the concurrent management server being applicable in high availability cluster | |
| US8438277B1 (en) | Systems and methods for preventing data inconsistency within computer clusters | |
| CN113596152A (en) | Load balancing implementation method, system and device | |
| CN110535947B (en) | Storage device cluster configuration node switching method, device and equipment | |
| CN116346585A (en) | Cloud-protogenesis-based network fault self-repairing method and system | |
| CN109617716B (en) | Data center exception handling method and device | |
| CN112698979A (en) | Method and device for processing zookeeper double nodes, storage medium and processor | |
| US10514991B2 (en) | Failover device ports | |
| CN106209450B (en) | Server fault switching method and application automation deployment system | |
| CN113300913B (en) | Equipment testing method and device, testing equipment and storage medium | |
| CN115904773A (en) | Memory fault information collection method and device and storage medium | |
| CN112612652A (en) | Distributed storage system abnormal node restarting method and system | |
| CN107122228A (en) | The dispositions method and device of the management platform of super emerging system | |
| CN112269693A (en) | Node self-coordination method, device and computer readable storage medium | |
| CN107783855B (en) | Fault self-healing control device and method for virtual network element | |
| CN112804077B (en) | Data protection method, controller, control plane device and storage medium | |
| CN115858222B (en) | Virtual machine fault processing method, system and electronic equipment | |
| JP7332249B2 (en) | Destination determination program, device and method |
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 |