CN112543141B - DNS forwarding server disaster tolerance scheduling method and system - Google Patents
DNS forwarding server disaster tolerance scheduling method and system Download PDFInfo
- Publication number
- CN112543141B CN112543141B CN202011410381.2A CN202011410381A CN112543141B CN 112543141 B CN112543141 B CN 112543141B CN 202011410381 A CN202011410381 A CN 202011410381A CN 112543141 B CN112543141 B CN 112543141B
- Authority
- CN
- China
- Prior art keywords
- forwarding
- abnormal
- server
- target
- list
- 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
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/28—Routing or path finding of packets in data switching networks using route fault recovery
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/74—Address processing for routing
- H04L45/745—Address table lookup; Address filtering
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
- H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
- H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L67/025—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
- H04L67/63—Routing a service request depending on the request content or context
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention relates to the technical field of Internet domain names, and discloses a method and a system for disaster recovery scheduling of a DNS forwarding server, wherein the method comprises the following steps: selecting a forwarding target from a forwarding list according to a query request of a user and sending the query request, judging whether the continuous overtime frequency of the forwarding target is greater than a set threshold value, and if so, reporting abnormal information; and detecting whether the corresponding abnormal server exists in a detection list or a forwarding blacklist or not according to the reported abnormal information, if not, adding the abnormal server into the detection list, detecting the abnormal server in the detection list, and if the detection fails for a plurality of times continuously, transferring the abnormal server into the forwarding blacklist and informing all forwarding servers in the cluster to delete the forwarding target. According to the method and the system for disaster recovery scheduling of the DNS forwarding server, the forwarding list of the cluster is uniformly managed by the control center, so that when the forwarding target is abnormal, the forwarding target can be quickly converged and switched to a normal target as soon as possible, and the overall performance of the cluster is improved.
Description
Technical Field
The invention relates to the technical field of internet, in particular to a method and a system for disaster recovery scheduling of a DNS forwarding server.
Background
When the current DNS forwarding server forwards, target selection is usually performed according to the size of RTT (round trip time) or a fixed sequence, when the forwarding target server is abnormal, a timeout penalty is performed by adding a certain RTT, and the server will not stop being used until the RTT of the abnormal target server is greater than that of other normal servers. In the cluster mode, each server only maintains its own forwarding list (forwarding target and corresponding RTT), and when the target server is abnormal, each forwarding server goes through the same process and cannot immediately switch to the normal target when the target server is abnormal.
In the cluster mode, each device only maintains its own forwarding list, and when the target server is abnormal, the forwarding server that has not processed the request will repeatedly perform RTT timeout punishment operation, which seriously affects the cluster performance.
Disclosure of Invention
Aiming at the defects of the prior art, the invention aims to provide a method and a system for disaster recovery scheduling of a DNS forwarding server, wherein a forwarding list of a cluster is uniformly managed by a control center, so that when a forwarding target is abnormal, the forwarding target can be quickly converged and switched to a normal target as soon as possible, and the overall performance of the cluster is improved.
In a first aspect of the present invention, a method for disaster recovery scheduling of a DNS forwarding server is provided, where the method includes:
selecting a forwarding target from a forwarding list according to a query request of a user, sending the query request, judging whether the continuous overtime frequency of the forwarding target is greater than a set threshold value or not, and if so, reporting abnormal information;
and detecting whether the corresponding abnormal server exists in a detection list or a forwarding blacklist or not according to the reported abnormal information, if not, adding the abnormal server into the detection list, detecting the abnormal server in the detection list, and if the abnormal server fails to be detected continuously for many times, transferring the abnormal server into the forwarding blacklist and informing all forwarding servers in the cluster to delete the forwarding target.
Further, the method further comprises: and detecting abnormal servers in the blacklist regularly, and when the detection is continuously carried out for multiple times and is successful, removing the abnormal servers from the blacklist and informing all the forwarding servers of adding the forwarding targets.
Further, when the abnormal server in the blacklist is continuously detected for multiple times, and the total detection time or the total detection times exceed a set threshold value, the abnormal server is deleted from the blacklist and alarm information is output.
Further, a continuous timeout number field is added to the forwarding list to record the continuous timeout number of the corresponding forwarding target, and an initial value is set to be zero.
Further, when sending the query request, if a response is received, the continuous overtime frequency is set to zero, a normal processing flow is entered, if no response is received, whether the continuous overtime frequency of the current forwarding target is greater than a set threshold value is judged, if not, the continuous overtime frequency of the current forwarding target is increased by one, and meanwhile, the next forwarding target is selected to continue sending the query request.
Further, the reported abnormal information includes a server address and a corresponding area name.
Further, when the abnormal server in the detection list is detected, if the detection is successful for a plurality of times, the abnormal server is removed from the detection list.
In another aspect of the present invention, a system for disaster recovery scheduling of a DNS forwarding server is further provided, where the system includes: a forwarding module and a forwarding scheduling module, wherein,
the forwarding module is positioned in the forwarding server, selects a forwarding target from a forwarding list after receiving an inquiry request of a user, sends the inquiry request, judges whether the continuous overtime frequency of the forwarding target is greater than a set threshold value or not, and reports abnormal information to the forwarding scheduling module if the continuous overtime frequency of the forwarding target is greater than the set threshold value;
and the forwarding scheduling module is positioned in the control center, detects according to the abnormal information reported by each forwarding module, judges whether the corresponding abnormal server exists in a detection list or a forwarding blacklist, if not, adds the abnormal server into the detection list, detects the abnormal server in the detection list, and if the abnormal server fails to be detected continuously for multiple times, transfers the abnormal server into the forwarding blacklist and informs all the forwarding servers in the cluster to delete the forwarding target.
Further, the control center communicates with all DNS servers of the cluster, detects abnormal information sent by each forwarding server, and then sends a related instruction to a server determined to be abnormal, and performs notification deletion.
Compared with the prior art, the method and the system for disaster recovery scheduling of the DNS forwarding server provided by the invention achieve the following technical effects:
1. when the forwarding target is abnormal, the method can quickly converge, eliminate the abnormal target, forward by using the normal forwarding target and reduce the influence of faults.
2. The control center uniformly detects and alarms abnormal targets, when a DNS server in the cluster finds the fault forwarding target, the control center can quickly inform the whole cluster, and the resource consumption of the whole cluster is reduced.
Drawings
Fig. 1 is a logic diagram of a DNS forwarding server disaster recovery scheduling method in an embodiment of the present invention.
Fig. 2 is an architecture diagram of a system for DNS forwarding server disaster recovery scheduling in an embodiment of the present invention.
Detailed Description
The technical solution in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. It is to be understood that the embodiments described are presently preferred modes of carrying out the invention, and that the description is made for the purpose of illustrating the general principles of the invention and not for the purpose of limiting the scope of the invention. The protection scope of the present invention shall be defined by the appended claims, and all other embodiments obtained by those skilled in the art without any inventive work shall fall within the protection scope of the present invention.
Referring to fig. 1, a method for disaster recovery scheduling of a DNS forwarding server disclosed in the embodiment of the present invention includes the following steps:
the method comprises the steps of firstly, selecting a forwarding target from a forwarding list according to a query request of a user, sending the query request, judging whether the continuous overtime frequency of the forwarding target is greater than a set threshold value, if so, indicating that a target server is possible to be abnormal, and reporting and prompting abnormal information; if the response is received within the set time threshold, the target server is normal, the normal processing flow is entered, and the inquiry request of the next forwarding target is continued.
And adding a continuous overtime frequency field in the forwarding list to record the continuous overtime frequency of the corresponding forwarding target and setting an initial value to be zero. When sending the inquiry request, if receiving the response, the continuous overtime times are set to zero, entering a normal processing flow, if not receiving the response, judging whether the continuous overtime times of the current forwarding target are larger than a set threshold value n, if not, adding one to the continuous overtime times of the forwarding target, and simultaneously selecting the next forwarding target to continue sending the inquiry request. It should be noted that if the current forwarding target times out, other forwarding targets are selected next time. After all forwarding targets have tried, retry will be started again from the first forwarding target. If the total time consumption of the request exceeds a certain time, the request is considered to be failed, servfail is returned, the processing of the next request is continued, and the continuous failure does not mean that the request is processed continuously for n times, but means that the current forwarding target is used for n times and all the requests fail.
By the method, when the forwarding target is abnormal, the forwarding target can be quickly converged, the abnormal target is eliminated, the normal forwarding target is used for forwarding, and the influence of faults is reduced.
And secondly, detecting whether the corresponding abnormal server exists in a detection list or a forwarding blacklist or not according to the reported abnormal information, if not, adding the abnormal server into the detection list, detecting the abnormal server in the detection list, and if the abnormal server fails to be detected continuously for many times, transferring the abnormal server into the forwarding blacklist and informing all forwarding servers in the cluster to delete the forwarding target.
After the abnormal server is transferred to the blacklist, the abnormal server is not completely eliminated and discarded, but the abnormal server in the blacklist is detected regularly, and when the abnormal server is detected continuously and successfully for many times, the abnormal server is removed from the blacklist and all forwarding servers are informed of adding the forwarding targets, so that the accuracy of judging the abnormal server can be improved, and the mistaken deletion can be prevented.
In addition, when the abnormal server in the blacklist is detected for multiple times continuously, for example, the total detection time or the total detection times exceeds a set threshold value, the abnormal server is deleted from the blacklist and alarm information is output. When the continuous detection for multiple times or the total detection time exceeds a set threshold value, which indicates that the abnormal server is really abnormal, the abnormal server is deleted, so that other forwarding servers can not make forwarding requests for the abnormal server any more.
By the method, the control center uniformly detects and pre-warns the abnormal target, reduces the resource consumption of the whole cluster and improves the performance of the cluster server.
Those skilled in the art will understand that some or all of the steps of the method of the above embodiments may be implemented by hardware instructions related to a program, the program may be stored in a computer readable storage medium, and when executed, the program includes the corresponding steps of the method of the above embodiments, and the storage medium may be: ROM/RAM, magnetic disks, optical disks, memory cards, and the like.
Corresponding to the above method, referring to fig. 2, another embodiment of the present invention further provides a system for DNS forwarding server disaster recovery scheduling, including: a forwarding module and a forwarding scheduling module, wherein,
the forwarding module is positioned in the forwarding server, selects a forwarding target from a forwarding list after receiving an inquiry request of a user, sends the inquiry request, judges whether the continuous overtime frequency of the forwarding target is greater than a set threshold value or not, and reports abnormal information to the forwarding scheduling module if the continuous overtime frequency of the forwarding target is greater than the set threshold value;
and the forwarding scheduling module is positioned in the control center, and the control center is responsible for comprehensively processing the abnormal information sent by each forwarding server, detecting the abnormal information reported by each forwarding module, judging whether the corresponding abnormal server exists in a detection list or a forwarding blacklist, if not, adding the abnormal server into the detection list, detecting the abnormal server in the detection list, and if the abnormal server fails to be detected continuously for multiple times, transferring the abnormal server into the forwarding blacklist and informing all the forwarding servers in the cluster to delete the forwarding target.
The working principles of the forwarding module of the forwarding server and the forwarding scheduling module of the control center are described in detail below.
A forwarding module of the forwarding server: and adding a continuous overtime frequency field in the forwarding list, wherein the continuous overtime frequency field is used for recording the continuous overtime frequency of the corresponding forwarding target, and the initial value is zero. And when the forwarding module receives the user request, selecting a forwarding target from the forwarding list and sending an inquiry request. If receiving the response, setting the continuous overtime times to zero, and entering a normal processing flow; if the response (overtime) is not received, judging whether the continuous overtime frequency of the current forwarding target is greater than n times, if not, adding one to the continuous overtime frequency of the forwarding target, and simultaneously selecting the next forwarding target to continuously send the query request; if the number of the forwarding addresses is larger than the number of the corresponding areas, the forwarding addresses and the corresponding area names are reported to a forwarding scheduling module of the control center, and meanwhile, a next forwarding target is selected to continuously send the query request.
A forwarding scheduling module of the control center: and the forwarding scheduling module receives the abnormal forwarding server information reported by the forwarding module and checks whether the abnormal forwarding server exists in a detection list or a forwarding blacklist. If the current time exists, no processing is carried out; if not, the exception server is saved to the probe list. Detecting abnormal servers in the detection list at regular time, and removing the abnormal servers from the detection list if the abnormal servers are successfully detected for k times continuously; if m continuous detection fails, moving to a forwarding blacklist and informing all forwarding servers in the cluster to delete the corresponding target, and then not forwarding the target, so that resources are saved. For abnormal servers in the blacklist, the control center detects the abnormal servers at regular time, and when the detection is successful for k times continuously, all forwarding servers are removed from the blacklist and informed of adding corresponding targets; and if the total detection time exceeds q, deleting the corresponding target from the blacklist and outputting alarm information.
The foregoing description shows and describes several preferred embodiments of the invention, but as aforementioned, it is to be understood that the invention is not limited to the forms disclosed herein, but is not to be construed as excluding other embodiments and is capable of use in various other combinations, modifications, and environments and is capable of changes within the scope of the inventive concept as expressed herein, commensurate with the above teachings, or the skill or knowledge of the relevant art. And that modifications and variations may be effected by those skilled in the art without departing from the spirit and scope of the invention as defined by the appended claims.
Claims (9)
1. A DNS forwarding server disaster recovery scheduling method is characterized by comprising the following steps:
selecting a forwarding target from a forwarding list according to a query request of a user, sending the query request, judging whether the continuous overtime frequency of the forwarding target is greater than a set threshold value or not, and if so, reporting abnormal information;
and detecting whether the corresponding abnormal server exists in a detection list or a forwarding blacklist or not according to the reported abnormal information, if not, adding the abnormal server into the detection list, detecting the abnormal server in the detection list, and if the abnormal server fails to be detected continuously for many times, transferring the abnormal server into the forwarding blacklist and informing all forwarding servers in the cluster to delete the forwarding target.
2. The method of claim 1, further comprising: and detecting abnormal servers in the blacklist regularly, and when the detection is continuously carried out for multiple times and is successful, removing the abnormal servers from the blacklist and informing all the forwarding servers of adding the forwarding targets.
3. The method according to claim 2, characterized in that when the abnormal server in the blacklist is detected for a plurality of times in succession, and the total detection time or the total detection times exceeds a set threshold value, the abnormal server is deleted from the blacklist and alarm information is output.
4. The method according to any one of claims 1 to 3, wherein a continuous timeout number field is added to the forwarding list to record the continuous timeout number of the corresponding forwarding target, and an initial value of the continuous timeout number field is set to zero.
5. The method according to claim 4, wherein when sending the query request, if the response is received, the number of continuous overtime times is set to zero, and the normal processing flow is entered, if the response is not received, it is determined whether the number of continuous overtime times of the current forwarding target is greater than the set threshold, if not, the number of continuous overtime times of the current forwarding target is increased by one, and at the same time, the next forwarding target is selected to continue sending the query request.
6. The method according to claim 1, wherein when probing an abnormal server in the probe list, if successive probing is successful, the abnormal server is removed from the probe list.
7. The method of claim 1, wherein the reported exception information comprises a server address and a corresponding area name.
8. A system for DNS forwarding server disaster recovery scheduling, the system comprises a forwarding module and a forwarding scheduling module, wherein,
the forwarding module is positioned in the forwarding server, selects a forwarding target from a forwarding list after receiving an inquiry request of a user, sends the inquiry request, judges whether the continuous overtime frequency of the forwarding target is greater than a set threshold value or not, and reports abnormal information to the forwarding scheduling module if the continuous overtime frequency of the forwarding target is greater than the set threshold value;
and the forwarding scheduling module is positioned in the control center, detects according to the abnormal information reported by each forwarding module, judges whether the corresponding abnormal server exists in a detection list or a forwarding blacklist, if not, adds the abnormal server into the detection list, detects the abnormal server in the detection list, and if the abnormal server fails to be detected continuously for multiple times, transfers the abnormal server into the forwarding blacklist and informs all the forwarding servers in the cluster to delete the forwarding target.
9. The system of claim 8, wherein the control center communicates with all DNS servers of the cluster, and detects and instructs the forwarding servers to send the exception information.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011410381.2A CN112543141B (en) | 2020-12-04 | 2020-12-04 | DNS forwarding server disaster tolerance scheduling method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011410381.2A CN112543141B (en) | 2020-12-04 | 2020-12-04 | DNS forwarding server disaster tolerance scheduling method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112543141A CN112543141A (en) | 2021-03-23 |
| CN112543141B true CN112543141B (en) | 2022-03-01 |
Family
ID=75017084
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011410381.2A Active CN112543141B (en) | 2020-12-04 | 2020-12-04 | DNS forwarding server disaster tolerance scheduling method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112543141B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113660275B (en) * | 2021-08-18 | 2023-02-24 | 中国电信股份有限公司 | Domain name system request processing method and device, electronic equipment and storage medium |
| CN115396516A (en) * | 2022-08-26 | 2022-11-25 | 中国建设银行股份有限公司 | Access request processing method, device, equipment and storage medium |
Family Cites Families (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7392421B1 (en) * | 2002-03-18 | 2008-06-24 | Symantec Operating Corporation | Framework for managing clustering and replication |
| US20100228819A1 (en) * | 2009-03-05 | 2010-09-09 | Yottaa Inc | System and method for performance acceleration, data protection, disaster recovery and on-demand scaling of computer applications |
| WO2013086214A1 (en) * | 2011-12-06 | 2013-06-13 | Seven Networks, Inc. | A system of redundantly clustered machines to provide failover mechanisms for mobile traffic management and network resource conservation |
| CN103780714B (en) * | 2012-10-25 | 2016-12-21 | 中国移动通信集团北京有限公司 | The detection method of a kind of dns server and device |
| CN103560922A (en) * | 2013-11-18 | 2014-02-05 | 北京特立信电子技术股份有限公司 | Disaster recovery method and system |
| CN104639366B (en) * | 2014-12-31 | 2017-03-15 | 北京奇虎科技有限公司 | DNS disaster recovery and backup systems isolated island response automatic switching method and device |
| CN105872118A (en) * | 2015-11-25 | 2016-08-17 | 乐视云计算有限公司 | Detection method and device of node servers in DNS (Domain Name System) network |
| CN107819605A (en) * | 2016-09-14 | 2018-03-20 | 北京百度网讯科技有限公司 | Method and apparatus for the switching server in server cluster |
| CN106453685A (en) * | 2016-11-15 | 2017-02-22 | 中国移动通信集团江苏有限公司 | Method for resolving with public DNS (Domain Name System) server, system and server |
| CN106487807A (en) * | 2016-11-18 | 2017-03-08 | 汉柏科技有限公司 | A kind of means of defence of domain name mapping and device |
| CN107317889A (en) * | 2017-08-21 | 2017-11-03 | 深圳市视维科技股份有限公司 | A kind of intelligent DNS scheduling system and dispatching method |
| CN109936613B (en) * | 2017-12-19 | 2021-11-05 | 北京京东尚科信息技术有限公司 | Disaster recovery method and device applied to server |
| CN108196501A (en) * | 2017-12-22 | 2018-06-22 | 北京东土科技股份有限公司 | A kind of disaster recovery method of the dcs based on PLC, device and system |
| US10938851B2 (en) * | 2018-03-29 | 2021-03-02 | Radware, Ltd. | Techniques for defense against domain name system (DNS) cyber-attacks |
| CN111464648B (en) * | 2020-04-02 | 2021-11-05 | 聚好看科技股份有限公司 | Distributed local DNS system and domain name query method |
-
2020
- 2020-12-04 CN CN202011410381.2A patent/CN112543141B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN112543141A (en) | 2021-03-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112543141B (en) | DNS forwarding server disaster tolerance scheduling method and system | |
| CN107015991B (en) | Self-checking method, device and system for data consistency and service device | |
| US7165192B1 (en) | Fault isolation in large networks | |
| CN108900379B (en) | Distributed network service scheduling method, device, computing equipment and storage medium | |
| KR100744448B1 (en) | Communication system | |
| CN111625841B (en) | Virus processing method, device and equipment | |
| CN106506490B (en) | A kind of distributed computing control method and distributed computing system | |
| US7430688B2 (en) | Network monitoring method and apparatus | |
| EP2176823A1 (en) | High availability transport | |
| CN113672415A (en) | Disk fault processing method, device, equipment and storage medium | |
| US20030014516A1 (en) | Recovery support for reliable messaging | |
| CN110119314B (en) | Server calling method and device, server and storage medium | |
| CN111342986A (en) | Distributed node management method and device, distributed system and storage medium | |
| CN113055203B (en) | Method and device for recovering exception of SDN control plane | |
| CN111880947B (en) | Data transmission method and device | |
| CN113542001B (en) | OSD (on-screen display) fault heartbeat detection method, device, equipment and storage medium | |
| WO2024113534A1 (en) | Method and apparatus for controlling storage resources in storage node, and storage node | |
| US9973421B2 (en) | Method and device for connection management in a telecommunication network | |
| CN108964992B (en) | Node fault detection method and device and computer readable storage medium | |
| CN113821414B (en) | Server protection method and device, electronic equipment and storage medium | |
| CN114697196A (en) | Network path switching method in data center, data center network system and equipment | |
| CN114116285A (en) | Processing method, device and medium for file gateway fault switching | |
| JPH0786841B2 (en) | Fault information logging method and data processing device | |
| CN113312234A (en) | Health detection optimization method and terminal | |
| CN112486750A (en) | Host fault processing method, device, control system and storage medium |
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 |