CN114553867A - Cloud-native cross-cloud network monitoring method and device and storage medium - Google Patents
Cloud-native cross-cloud network monitoring method and device and storage medium Download PDFInfo
- Publication number
- CN114553867A CN114553867A CN202210071429.4A CN202210071429A CN114553867A CN 114553867 A CN114553867 A CN 114553867A CN 202210071429 A CN202210071429 A CN 202210071429A CN 114553867 A CN114553867 A CN 114553867A
- Authority
- CN
- China
- Prior art keywords
- network monitoring
- cloud
- pingmesh
- agent
- pinglist
- 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
- 238000012544 monitoring process Methods 0.000 title claims abstract description 344
- 238000000034 method Methods 0.000 title claims abstract description 53
- 238000001514 detection method Methods 0.000 claims abstract description 31
- 230000004044 response Effects 0.000 claims description 20
- 239000000523 sample Substances 0.000 claims 1
- 238000012806 monitoring device Methods 0.000 abstract description 7
- 239000003795 chemical substances by application Substances 0.000 description 64
- 238000012423 maintenance Methods 0.000 description 7
- 230000005540 biological transmission Effects 0.000 description 4
- 238000004891 communication Methods 0.000 description 4
- 230000006870 function Effects 0.000 description 4
- 108010026228 mRNA guanylyltransferase Proteins 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- 238000012360 testing method Methods 0.000 description 4
- 230000001360 synchronised effect Effects 0.000 description 3
- 238000012384 transportation and delivery Methods 0.000 description 3
- 238000004458 analytical method Methods 0.000 description 2
- 238000004364 calculation method Methods 0.000 description 2
- 238000004590 computer program Methods 0.000 description 2
- 238000013499 data model Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000001914 filtration Methods 0.000 description 2
- 230000002452 interceptive effect Effects 0.000 description 2
- 238000007726 management method Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 238000010791 quenching Methods 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 235000000332 black box Nutrition 0.000 description 1
- 244000085682 black box Species 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000011835 investigation Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 238000013439 planning Methods 0.000 description 1
- 238000005096 rolling process Methods 0.000 description 1
Images
Classifications
-
- 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
-
- 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/04—Network management architectures or arrangements
- H04L41/042—Network management architectures or arrangements comprising distributed management centres cooperatively managing the network
-
- 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/04—Processing captured monitoring data, e.g. for logfile generation
-
- 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
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/12—Network monitoring probes
-
- 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/50—Testing arrangements
-
- 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/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
Abstract
The invention discloses a cloud-native cross-cloud network monitoring method, a cloud-native cross-cloud network monitoring device and a storage medium, wherein the cloud-native cross-cloud network monitoring method comprises the following steps: respectively deploying a network monitoring node Pingmesh Agent in a container service system of each cloud; the method comprises the steps that a network monitoring node Pingmesh Agent on each cloud end obtains a network monitoring list pinglist by a network monitoring control center Pingmesh Controller, wherein the network monitoring list pinglist comprises address information of the cloud end deployed by each network monitoring node Pingmesh Agent; the network monitoring nodes Pingmesh Agent on each cloud terminal concurrently perform ICMP detection aiming at the addresses in the network monitoring list pinglist; and the network monitoring nodes Pingmesh Agent on each cloud report the ICMP detected data to a network monitoring control center Pingmesh Controller. The method solves the problem of cross-cloud network monitoring caused by non-uniform network models among multiple clouds and incapability of intercommunicating monitoring data, fills the blank of cross-cloud network monitoring in the cloud native field, and has high novelty and practical value.
Description
Technical Field
The invention relates to the technical field of cloud computing, in particular to a cloud-native cross-cloud network monitoring method and device and a storage medium.
Background
Cloud is native, a technical ecology in the field of cloud computing, which is a set of cloud technology product system established based on distributed deployment and unified operation and maintenance distributed cloud and technologies such as container, micro-service and DevOps.
With the development of cloud computing, multiple clouds are deployed as an effective means for avoiding single cloud failures, and meanwhile, a series of challenges are provided, and cross-cloud network monitoring is one of the challenges. The method has the advantages that the cross-cloud network condition is mastered, the method has important significance for preventing potential network problems and quickly discovering network faults, at present, network models of cloud manufacturers are not uniform, monitoring of all the cloud manufacturers is integrated, data cannot be communicated, and a network monitoring solution blackbox of an industry K8s (namely Kubernets, a standard open source container arrangement and scheduling platform in the cloud native field) can only play a role in a single cluster. At present, no solution for cross-cloud network monitoring exists in the cloud native field, so that the cross-cloud network problem cannot be found and processed in time, the problem can be found only by manual investigation of an operation and maintenance engineer, and the efficiency is low.
In view of this, the present invention is specifically disclosed.
Disclosure of Invention
In order to solve the above problems, the present invention provides a method, an apparatus and a storage medium for cloud-native cross-cloud network monitoring, and specifically, the following technical solutions are adopted:
a cloud-native cross-cloud network monitoring method comprises the following steps:
respectively deploying a network monitoring node Pingmesh Agent in a container service system of each cloud;
the method comprises the steps that a network monitoring node Pingmesh Agent on each cloud end obtains a network monitoring list pinglist by a network monitoring control center Pingmesh Controller, wherein the network monitoring list pinglist comprises address information of the cloud end deployed by each network monitoring node Pingmesh Agent;
the network monitoring nodes Pingmesh Agent on each cloud terminal concurrently perform ICMP detection aiming at the addresses in the network monitoring list pinglist;
and the network monitoring nodes Pingmesh Agent on each cloud report the ICMP detected data to a network monitoring control center Pingmesh Controller.
As an optional implementation manner of the present invention, in the cloud-based cross-cloud network monitoring method of the present invention, when the network monitoring node Pingmesh Agent is started, the network monitoring node Pingmesh Agent may automatically register to the network monitoring control center Pingmesh Controller, and the network monitoring control center Pingmesh Controller obtains and maintains the network monitoring list pinglist including the address information of the cloud deployed by each network monitoring node Pingmesh Agent.
As an optional implementation manner of the present invention, in the cloud-native cross-cloud network monitoring method of the present invention, a heartbeat is maintained between the network monitoring node Pingmesh Agent on each cloud and the network monitoring control center Pingmesh Controller;
the network monitoring node Pingmesh Agent regularly requests a network monitoring control center Pingmesh Controller to obtain the latest version number of a network monitoring list pinglist;
if the obtained network monitoring list pinglist version number is larger than the local version number of the network monitoring node Pingmeshagent, the network monitoring node Pingmesh Agent obtains the network monitoring list pinglist version of a network monitoring control center Pingmesh Controller and updates the version to the local;
and if the obtained version number of the network monitoring list pinglist is not greater than the local version number of the network monitoring node Pingmesh Agent, the network monitoring node Pingmesh Agent carries out ICMP detection aiming at the address in the local network monitoring list pinglist version.
As an optional implementation manner of the present invention, in the cloud-native cross-cloud network monitoring method of the present invention, if the network monitoring control center Pingmesh Controller does not receive the heartbeat request of the network monitoring node Pingmesh Agent within a preset time period T, it is determined that the corresponding network monitoring node Pingmesh Agent is offline, and the network monitoring control center Pingmesh Controller removes the offline network monitoring node Pingmesh Agent and synchronously updates data in the network monitoring list pinglist.
As an optional implementation manner of the present invention, in the cloud-native cross-cloud network monitoring method of the present invention, the data detected by the ICMP of the Pingmesh Agent at the network monitoring node includes an average response delay, a maximum response delay, and a packet loss rate of the cloud server.
As an optional implementation manner of the present invention, in the cloud-native cross-cloud network monitoring method of the present invention, the ICMP detection data of the network monitoring node Pingmesh Agent on each cloud received by the network monitoring control center Pingmesh Controller is periodically collected and used as a data source for subsequent monitoring chart drawing and alarm.
As an optional implementation manner of the present invention, in the cloud-native cross-cloud network monitoring method of the present invention, the network monitoring control center Pingmesh Controller includes:
the database is used for storing a network monitoring list pinglist containing address information of a cloud end deployed by each network monitoring node Pingmesh Agent;
the register is used for registering in a Pingmesh Controller of a network monitoring control center when a Pingmesh Agent is newly deployed on a cloud end;
the network monitoring list generator is used for generating a network monitoring list pinglist in the database, adding new address information containing a cloud terminal deployed by a new network monitoring node Pingmesh Agent, and removing the address information of the cloud terminal deployed by the offline network monitoring node Pingmesh Agent;
and the Web service module is used for sending display information to a system interface and for monitoring an alarm system and a time sequence database Promeeus to collect ICMP detection data of the Pingmesh Agent of the network monitoring nodes on the cloud terminals received by the Pingmesh Controller in real time.
As an optional implementation manner of the present invention, in the cloud-native cross-cloud network monitoring method of the present invention, the container service system of each cloud is a K8s cluster, and the network monitoring node Pingmesh Agent is deployed in the K8s cluster of each cloud in a Deployment manner.
The invention also provides a cloud-native cross-cloud network monitoring device, which comprises:
the network monitoring node modules are respectively deployed in the container service systems of all the cloud ends;
the network monitoring control center module is used for storing a network monitoring list pinglist containing address information of a cloud end deployed by each network monitoring node Pingmesh Agent;
the network monitoring node modules on the cloud terminals acquire the network monitoring lists pinglist from the network monitoring control center module, perform ICMP detection aiming at the addresses in the network monitoring lists pinglist concurrently, and report ICMP detected data to the network monitoring control center module.
The invention also provides a storage medium which stores a computer executable program, and when the computer executable program is executed, the cross-cloud network monitoring method of cloud-native is realized.
Compared with the prior art, the invention has the beneficial effects that:
the invention provides a cross-cloud network monitoring method operating in a cloud native mode, which is characterized in that a network monitoring node Pingmesh Agent is respectively deployed at each cloud end to carry out ICMP detection aiming at the address concurrency in a network monitoring list pinglist, so that the real-time monitoring of the network quality among multiple clouds is realized, and then a network monitoring control center Pingmesh Controller synchronizes the ICMP detection data of each network monitoring node Pingmesh Agent, so that cluster managers can better know the quality of a cross-cloud network, and the network problem discovery efficiency is greatly improved.
Therefore, the cloud-native cross-cloud network monitoring method provided by the invention solves the problem of cross-cloud network monitoring caused by non-uniform network models among multiple clouds and incapability of intercommunicating monitoring data, makes up the blank of cross-cloud network monitoring in the cloud-native field, and has higher novelty and practical value.
Description of the drawings:
FIG. 1 is a first flowchart of a cross-cloud network monitoring method of cloud-native according to an embodiment of the present invention;
FIG. 2 is a diagram illustrating an overall architecture of a cross-cloud network monitoring method according to an embodiment of the present invention;
FIG. 3 is a flow chart of a cross-cloud network monitoring method of embodiment cloud-native of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be described clearly and completely with reference to the accompanying drawings. It is to be understood that the embodiments described are only a few embodiments of the present invention, and not all embodiments.
Thus, the following detailed description of the embodiments of the invention is not intended to limit the scope of the invention as claimed, but is merely representative of some embodiments of the invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
It should be noted that the embodiments of the present invention and the features and technical solutions thereof may be combined with each other without conflict.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures.
In the description of the present invention, it should be noted that the terms "upper", "lower", and the like refer to orientations or positional relationships based on those shown in the drawings, or orientations or positional relationships that are conventionally arranged when the products of the present invention are used, or orientations or positional relationships that are conventionally understood by those skilled in the art, and such terms are used for convenience of description and simplification of the description, and do not refer to or imply that the devices or elements referred to must have a specific orientation, be constructed and operated in a specific orientation, and thus, should not be construed as limiting the present invention. Furthermore, the terms "first," "second," and the like are used merely to distinguish one description from another, and are not to be construed as indicating or implying relative importance.
Referring to fig. 1 to fig. 3, a cloud-native cross-cloud network monitoring method according to the present embodiment includes:
respectively deploying a network monitoring node Pingmesh Agent in a container service system of each cloud;
the method comprises the steps that a network monitoring node Pingmesh Agent on each cloud end obtains a network monitoring list pinglist by a network monitoring control center Pingmesh Controller, wherein the network monitoring list pinglist comprises address information of the cloud end deployed by each network monitoring node Pingmesh Agent;
the network monitoring nodes Pingmesh Agent on each cloud terminal concurrently perform ICMP detection aiming at the addresses in the network monitoring list pinglist;
and the network monitoring nodes Pingmesh Agent on each cloud report the ICMP detected data to a Pingmesh Controller of the network monitoring control center.
The embodiment provides a cross-cloud network monitoring method operating in a cloud native mode, which is characterized in that a network monitoring node Pingmesh Agent is respectively deployed at each cloud end to perform ICMP detection aiming at addresses in a network monitoring list pinglist, so that the real-time monitoring of the network quality among multiple clouds is realized, and then a network monitoring control center Pingmesh Controller is used for synchronizing the ICMP detection data of each network monitoring node Pingmesh Agent, so that cluster managers can better know the quality of a cross-cloud network, and the efficiency of network problem discovery is greatly improved.
Therefore, the cloud-native cross-cloud network monitoring method provided by the embodiment solves the problem of cross-cloud network monitoring caused by non-uniform network models among multiple clouds and incapability of intercommunicating monitoring data, makes up the blank of cross-cloud network monitoring in the cloud-native field, and has high novelty and practical value.
The ICMP detection in this embodiment is a network quality detection method using an ICMP protocol, which is an ICMP (Internet Control Message protocol) Internet Control Message protocol, and is a sub-protocol of a TCP/IP protocol cluster, and is used to transmit Control messages between an IP host and a router. The ICMP protocol belongs to a network layer protocol and is mainly used for transferring control information between a host and a router, including reporting errors, exchanging limited control and status information, and the like.
As an optional implementation manner of this embodiment, the network monitoring node Pingmesh Agent performs ICMP detection through a Ping command, where the Ping command is a very good TCP/IP tool in the network, and its main function is to detect the connectivity of the network and analyze the network speed. The ping command is an echo (ping) request message that requests a response by ICMP. If there is no problem in the remote network function, it will respond to echo (ping) reply message, so as to know that the operation is normal. The user can determine whether the target is enabled and the network is normal through the ping command.
Network connectivity problems are typically caused by many reasons, such as local configuration errors, remote host protocol failures, and the like, and of course, failures caused by devices and the like. The step of testing network connectivity using Ping commands:
1. ipconfig/all is used to observe whether the local network settings are correct.
The Ping loopback address is used to check whether the local TCP/IP protocol is set.
Ping native IP address, so as to check if the native IP address is set with an error.
Ping home gateway or home IP address, which is to check if there is a problem with the hardware device, and also to check if the connection between the home and the home network is normal.
Ping remote IP address, which is mainly to check whether the connection between the local network or the local machine and the outside is normal.
Analysis of returned information after Ping command:
request timed out, in at least several cases.
(1) The opposite party has been powered off or there is no such address on the network at all.
(2) The other party and the self are not in the same network segment, and the other party cannot be found through the route, but sometimes the other party exists really, and certainly, no information which is also the overtime is returned is existed.
(3) The partner does exist but sets ICMP packet filtering (e.g., firewall settings).
(4) Setting IP address erroneously
2.Destination host Unreachable
(1) The opposite side is not in the same network segment with itself, and the default route is not set.
(2) Network cable goes wrong
It should be noted that the difference between the destination host unknown and the time out is that if the routing table of the router has a route to the destination, and the destination is not reachable for other reasons, the time out will appear at this time, and if no route to the destination is in the routing table, the destination host unknown will appear.
3.Bad IP address
This information indicates that you may not be connected to the DNS server and therefore cannot resolve the IP address, or that an IP address does not exist.
4.Source quench received
This information is special and it occurs only with a small probability. It indicates that the other party or the server in the middle is busy and cannot respond.
5.Unknown host
This error message means that the name of the remote host cannot be translated to an IP address by a Domain Name Server (DNS). The cause of the failure may be a failure of the domain name server, or its name may be incorrect, or a failure of the communication line between the network administrator's system and the remote host.
6.No answer
This failure indicates that the local system has a route to the central host, but does not receive any information it sends to the central host. The cause of the failure may be one of: the central host does not work; local or central host network configuration is incorrect; the local or central router is not working; a fault in the communication line; the central host has routing problems.
7, Ping 127.0.0.1: 127.0.0.1 is the local loop address
If the address can not be Ping communicated, the TCP/IP protocol of the local machine can not work normally.
No rout to host: the network card is not working properly.
Transmit failed, error code: 10043 the network card is not normally driven.
Unknown host name: the DNS configuration is incorrect.
As an optional implementation manner of this embodiment, in the cloud-native cross-cloud network monitoring method described in this embodiment, when the network monitoring node Pingmesh Agent is started, the network monitoring node Pingmesh Agent may automatically register to the network monitoring control center Pingmesh Controller, and the network monitoring control center Pingmesh Controller obtains and maintains a network monitoring list pinglist including address information of a cloud deployed by each network monitoring node Pingmesh Agent. In this embodiment, when all the network monitoring nodes Pingmesh agents are started, deployed cloud address information is registered in a Pingmesh Controller of a network monitoring control center, and the Pingmesh Controller performs unified maintenance and monitoring, so that the starting states of the network monitoring nodes Pingmesh agents on all the clouds are synchronized and monitored.
Further, in the cloud-native cross-cloud network monitoring method of the embodiment, a heartbeat is maintained between the network monitoring node Pingmesh Agent on each cloud and the network monitoring control center Pingmesh Controller;
the network monitoring node Pingmesh Agent regularly requests a network monitoring control center Pingmesh Controller to obtain the latest version number of a network monitoring list pinglist;
if the obtained network monitoring list pinglist version number is larger than the local version number of the network monitoring node Pingmesh Agent, the network monitoring node Pingmesh Agent obtains the network monitoring list pinglist version of a network monitoring control center Pingmesh Controller and updates the version to the local;
and if the obtained version number of the network monitoring list pinglist is not more than the local version number of the network monitoring node Pingmeshagent, the network monitoring node Pingmesh Agent carries out ICMP detection aiming at the address in the local network monitoring list pinglist version.
The network monitoring control center pinmesh Controller of the embodiment maintains the network monitoring list pinlist of the network monitoring node pinmesh Agent of each cloud, and the version number of the network monitoring list pinlist of the network monitoring node pinmesh Agent of any cloud is upgraded through the network monitoring control center pinmesh Controller, so that the network monitoring requirements of each cloud are met, and cross-cloud network monitoring unified control is realized.
Further, in the cloud-native cross-cloud network monitoring method of this embodiment, if the network monitoring control center Pingmesh Controller does not receive the heartbeat request of the network monitoring node Pingmesh Agent within the preset time period T, it is determined that the corresponding network monitoring node Pingmesh Agent is offline, and the network monitoring control center Pingmesh Controller removes the offline network monitoring node Pingmesh Agent and synchronously updates the corresponding pinglist. The embodiment not only monitors and synchronizes data for the network monitoring node Pingmesh Agent in the starting state, but also removes the network monitoring node Pingmesh Agent in time for the offline network monitoring node Pingmesh Agent, thereby preventing the offline network monitoring node Pingmesh Agent from occupying system resources and ensuring the efficiency and stability of system resource operation.
The data detected by the ICMP of the network monitoring node Pingmesh Agent in this embodiment includes an average response delay, a maximum response delay, and a packet loss rate of the cloud server. The response delay refers to the total time consumed by the user from the sending of the request to the completion of the receiving of the response, and is composed of a plurality of parts, such as network transmission time consumption, service processing time consumption and the like. Typically in milliseconds (ms). The average response latency refers to the average time taken for all requests, if there are 100 requests, 98 of which take 1ms and the other two 100 ms. Then the average response time is (98 x 1+2 x 100)/100.0-2.98 ms. The maximum response latency is the longest time spent in all requests. The Loss Rate (Loss toll or Packet Loss Rate) is the ratio of the number of lost data packets in the transmitted data group in the test, the calculation method is [ (input message-output message)/input message ]. 100% ", the Loss Rate is related to the length of the data Packet and the transmission frequency of the Packet.
Further, in the cloud-native cross-cloud network monitoring method of this embodiment, the ICMP detection data of the network monitoring node Pingmesh Agent on each cloud received by the network monitoring control center Pingmesh Controller is periodically collected and used as a data source for subsequent monitoring chart drawing and alarming.
In the embodiment, the reported ICMP detection data is used as a data source for subsequent monitoring chart drawing and alarming, so that cluster management personnel can be helped to better know the quality of the cross-cloud network, and the efficiency of network problem discovery is greatly improved.
As an optional implementation manner of this embodiment, in the cloud-native cross-cloud network monitoring method of this embodiment, the network monitoring control center Pingmesh Controller includes:
the database is used for storing a network monitoring list pinglist containing address information of a cloud end deployed by each network monitoring node Pingmesh Agent;
the register is used for registering in a Pingmesh Controller of a network monitoring control center when a Pingmesh Agent is deployed on a new cloud;
the network monitoring list generator is used for generating a network monitoring list pinglist in the database, adding new address information containing a cloud end deployed by a new network monitoring node Pingmesh Agent, and removing the address information of the cloud end deployed by the offline network monitoring node Pingmesh Agent;
and the Web service module is used for sending display information to a system interface and for monitoring an alarm system and a time sequence database Promeeus to collect ICMP detection data of the Pingmesh Agent of the network monitoring nodes on the cloud terminals received by the Pingmesh Controller in real time.
The network monitoring control center Pingmesh Controller of this embodiment further has an interactive UI, which is used for cluster managers to analyze ICMP detected data, understand quality of the cross-cloud network, and find network problems in time.
Prometheus of the present example is an open source monitoring alarm system and Time Series Database (TSDB) developed by soundlog. Characteristics of Prometheus: a multi-dimensional data model; a flexible query language; independent of distributed storage, a single server node is autonomous; collecting time sequence data in a pull mode based on HTTP; time sequence data can be pushed through the intermediate gateway; discovering a target service object through service discovery or static configuration; a wide variety of charts and interface presentations are supported, such as Grafana, and the like.
As an optional implementation manner of this embodiment, the container service system of each cloud is a K8s cluster, and the network monitoring node Pingmesh Agent is deployed in the K8s cluster of each cloud in a Deployment manner.
K8s is fully known as kubernets, which is an open source for managing containerized applications on multiple hosts in a cloud platform, and aims to make it simple and efficient (powerfull) to deploy containerized applications, which provides a mechanism for application deployment, planning, updating, and maintenance. Deployment is the most common way to deploy stateless services. The Deploymet controller enables you to update the Pod and the ReplicaSet in a declarative manner. Pod and replicase are managed in a "declarative" manner, which is essential to solidify a series of operation and maintenance steps for some specific scenarios for fast and error-free execution. The Deployment determines the following operation and maintenance scenarios for us:
creating a Deployment: after creating the Deployment, the Deployment controller will immediately create a set of copies of the replicase, and create the required Pod from the replicase.
Updating the Deployment: the definition of Pod in the Deployment is updated (e.g., a new version of the container image is released). At this time, the delivery controller will create a new replicase copy set for the delivery, and gradually create Pod in the new copy set and delete Pod in the old copy set, so as to achieve the effect of rolling update.
Rollback Deployment: roll back to an earlier delivery version.
Telescoping Deployment: the Deployment is extended horizontally to support larger loads or contracted horizontally to save server resources.
The Deployment is paused and resumed.
The Deployment status is viewed.
This embodiment provides a native cloud network monitoring device that strides of cloud simultaneously, includes:
the network monitoring node modules are respectively deployed in the container service systems of all the cloud ends;
the network monitoring control center module is used for storing a network monitoring list pinglist containing address information of a cloud end deployed by each network monitoring node Pingmesh Agent;
the network monitoring node modules on the cloud terminals acquire the network monitoring lists pinglist from the network monitoring control center module, perform ICMP detection aiming at the addresses in the network monitoring lists pinglist concurrently, and report ICMP detected data to the network monitoring control center module.
This embodiment has provided a cross cloud network monitoring device with operation of cloud primary mode, carry out ICMP through deploying network monitoring node module respectively in each high in the clouds and aim at the address concurrency in the network monitoring list pinglist and survey, realize the real time monitoring of the network quality between the many clouds, the data that the ICMP of each network monitoring node Pingmesh Agent was surveyed is synchronized to rethread network monitoring control center module for help cluster administrator's better understanding cross cloud network's quality, improve the efficiency that the network problem was discovered by a wide margin.
Therefore, the cloud-native cross-cloud network monitoring device provided by the embodiment solves the problem of cross-cloud network monitoring caused by non-uniform network models among multiple clouds and incapability of intercommunicating monitoring data, makes up the blank of cross-cloud network monitoring in the cloud-native field, and has high novelty and practical value.
The ICMP detection in this embodiment is a network quality detection method using an ICMP protocol, which is an ICMP (Internet Control Message protocol) Internet Control Message protocol, and is a sub-protocol of a TCP/IP protocol cluster, and is used to transmit Control messages between an IP host and a router. The ICMP protocol belongs to a network layer protocol and is mainly used for transferring control information between a host and a router, including reporting errors, exchanging limited control and status information, etc.
As an optional implementation manner of this embodiment, the network monitoring node module performs ICMP detection through a Ping command, where the Ping command is a very good TCP/IP tool in the network, and its main function is to detect the connectivity of the network and analyze the network speed. The ping command is an echo (ping) request message that requests a response by ICMP. If there is no problem in the remote network function, it will respond to echo (ping) reply message, so as to know that the operation is normal. The user can determine whether the target is enabled and the network is normal through the ping command.
Network connectivity problems are typically caused by many reasons, such as local configuration errors, remote host protocol failures, and the like, and of course, failures caused by devices and the like. The step of testing network connectivity using Ping commands:
1. ipconfig/all is used to observe whether the local network settings are correct.
The Ping loopback address is used to check whether the local TCP/IP protocol is set.
Ping native IP address, so as to check if the native IP address is set with an error.
Ping home gateway or home IP address, which is to check if there is a problem with the hardware device, and also to check if the connection between the home and the home network is normal.
Ping remote IP address, which is mainly to check whether the connection between the local network or the local machine and the outside is normal.
Analysis of returned information after Ping command:
request timed out, in at least several cases.
(1) The opposite party has been powered off or there is no such address on the network at all.
(2) The other party and the self are not in the same network segment, and the other party cannot be found through the route, but sometimes the other party exists really, and certainly, no information which is also the overtime is returned is existed.
(3) The partner does exist but sets ICMP packet filtering (e.g., firewall settings).
(4) Setting IP address erroneously
2.Destination host Unreachable
(1) The opposite side is not in the same network segment with itself, and the default route is not set.
(2) Network cable goes wrong
It should be noted that the difference between the destination host unknown and the time out is that if the routing table of the router has a route to the destination, and the destination is not reachable for other reasons, the time out will appear at this time, and if no route to the destination is in the routing table, the destination host unknown will appear.
3.Bad IP address
This information indicates that you may not be connected to the DNS server and therefore cannot resolve the IP address, or that an IP address does not exist.
4.Source quench received
This information is special and it occurs only with a small probability. It indicates that the other party or the server in the middle is busy and cannot respond.
5.Unknown host
This error message means that the name of the remote host cannot be translated to an IP address by a Domain Name Server (DNS). The cause of the failure may be a failure of the domain name server, or its name may be incorrect, or a failure of the communication line between the network administrator's system and the remote host.
6.No answer
This failure indicates that the local system has a route to the central host, but does not receive any information it sends to the central host. The cause of the failure may be one of: the central host does not work; local or central host network configuration is incorrect; the local or central router is not working; a fault in the communication line; the central host has routing problems.
7, Ping 127.0.0.1: 127.0.0.1 is the local loop address
If the address can not be Ping communicated, the TCP/IP protocol of the local machine can not work normally.
No rout to host: the network card is not working properly.
Transmit failed, error code: 10043 the network card is not normally driven.
Unknown host name: the DNS configuration is incorrect.
As an optional implementation manner of this embodiment, in the cloud-native cross-cloud network monitoring apparatus described in this embodiment, the network monitoring node modules may be automatically registered in the network monitoring control center module when being started, and the network monitoring control center module obtains and maintains a network monitoring list pinglist including address information of a cloud deployed by each network monitoring node module. When all the network monitoring node modules of this embodiment are started, the deployed cloud address information is registered in the network monitoring control center module, and the network monitoring control center module performs unified maintenance and monitoring, so that the starting states of all the network monitoring node modules on the cloud are synchronized and monitored.
Further, in the cloud-native cross-cloud network monitoring device of this embodiment, the network monitoring node modules on the cloud ends respectively have heartbeat modules, and a heartbeat is maintained between each network monitoring node module and the network monitoring control center module through the heartbeat module;
the network monitoring node module regularly requests a network monitoring control center module to obtain the latest network monitoring list pinglist version number;
if the obtained network monitoring list pinglist version number is larger than the local version number of the network monitoring node module, the network monitoring node module obtains the network monitoring list pinglist version of the network monitoring control center module and updates the network monitoring list pinglist version to the local;
and if the obtained version number of the network monitoring list pinglist is not greater than the local version number of the network monitoring node module, the network monitoring node module carries out ICMP detection on the address in the local network monitoring list pinglist version.
The network monitoring control center module of this embodiment maintains the network monitoring list pinglist of the network monitoring node module to each high in the clouds, realizes upgrading the version number of the network monitoring list pinglist of the network monitoring node module to arbitrary high in the clouds through the network monitoring control center module to satisfy the network monitoring requirement to each high in the clouds, realize the unified control of the network monitoring of crossing the clouds.
Further, if the network monitoring control center module does not receive the heartbeat request of the network monitoring node module within the preset time period T, the corresponding network monitoring node module is judged to be offline, the network monitoring node module which is offline is removed by the network monitoring control center module, and the corresponding pinglist is synchronously updated. The embodiment not only carries out monitoring and data synchronization on the network monitoring node module in the starting state, but also removes the network monitoring node module from the off-line in time, prevents the network monitoring node module from occupying system resources from the off-line, and ensures the efficiency and stability of system resource operation.
In this embodiment, the ICMP detected data of the network monitoring node module includes an average response delay, a maximum response delay, and a packet loss rate of the cloud server. The response delay refers to the total time consumed by the user from the sending of the request to the completion of the receiving of the response, and is composed of a plurality of parts, such as network transmission time consumption, service processing time consumption and the like. Typically in milliseconds (ms). The average response latency refers to the average time taken for all requests, if there are 100 requests, 98 of which take 1ms and the other two 100 ms. Then the average response time is (98 x 1+2 x 100)/100.0-2.98 ms. The maximum response latency is the longest time spent in all requests. The Loss Rate (Loss toll or Packet Loss Rate) is the ratio of the number of lost data packets in the transmitted data group in the test, the calculation method is [ (input message-output message)/input message ]. 100% ", the Loss Rate is related to the length of the data Packet and the transmission frequency of the Packet.
Further, the cloud-native cross-cloud network monitoring device of this embodiment further includes a monitoring module, and the monitoring module periodically collects ICMP detection data of the network monitoring node modules on the cloud ends, which is received by the network monitoring control center module, and uses the ICMP detection data as a data source for subsequent monitoring chart drawing and alarm.
In the embodiment, the reported ICMP detection data is used as a data source for subsequent monitoring chart drawing and alarming, so that cluster management personnel can be helped to better know the quality of the cross-cloud network, and the efficiency of network problem discovery is greatly improved.
As an optional implementation manner of this embodiment, in the cloud-native cross-cloud network monitoring apparatus of this embodiment, the network monitoring control center module includes:
the database is used for storing a network monitoring list pinglist containing address information of a cloud end deployed by each network monitoring node module;
the register is used for registering in the network monitoring control center module when the network monitoring node module is deployed on the new cloud end;
the network monitoring list generator is used for generating a network monitoring list pinglist in the database, newly adding address information containing a cloud end deployed by a new network monitoring node module, and removing the address information of the cloud end deployed by an off-line network monitoring node module;
and the Web service unit is used for sending display information to a system interface and is used for monitoring an alarm system and a time sequence database Promeheus to acquire ICMP detection data of the network monitoring node modules on the cloud ends, which are received by the network monitoring control center module, in real time.
The network monitoring control center module of this embodiment further has an interactive UI unit for cluster managers to analyze ICMP detected data, understand quality of the cross-cloud network, and find network problems in time.
Prometheus of the present example is an open source monitoring alarm system and Time Series Database (TSDB) developed by soundlog. Characteristics of Prometheus: a multi-dimensional data model; a flexible query language; independent of distributed storage, a single server node is autonomous; collecting time sequence data in a pull mode based on HTTP; time sequence data pushing can be carried out through the intermediate gateway; discovering a target service object through service discovery or static configuration; a wide variety of charts and interface presentations are supported, such as Grafana, and the like.
As an optional implementation manner of this embodiment, the container service system of each cloud is a K8s cluster, and the network monitoring node module is deployed in the K8s cluster of each cloud in a Deployment manner. The present embodiment provides a storage medium storing a computer executable program, and when the computer executable program is executed, the method for monitoring a cloud-native cross-cloud network is implemented.
The storage medium of this embodiment may comprise a propagated data signal with readable program code embodied therein, either in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A readable storage medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a readable storage medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
The present embodiment also provides an electronic device, including a processor and a memory, where the memory is used to store a computer executable program, and when the computer program is executed by the processor, the processor executes the cross-cloud network monitoring method native to the cloud.
The electronic device is in the form of a general purpose computing device. The processor can be one or more and can work together. The invention does not exclude that the processing is distributed, i.e. the processors may be distributed over different physical devices. The electronic device of the present invention is not limited to a single entity, and may be a sum of a plurality of entity devices.
The memory stores a computer executable program, typically machine readable code. The computer readable program may be executed by the processor to enable an electronic device to perform the method of the invention, or at least some of the steps of the method.
The memory may include volatile memory, such as Random Access Memory (RAM) and/or cache memory, and may also be non-volatile memory, such as read-only memory (ROM).
It should be understood that elements or components not shown in the above examples may also be included in the electronic device of the present invention. For example, some electronic devices further include a display unit such as a display screen, and some electronic devices further include a human-computer interaction element such as a button, a keyboard, and the like. Electronic devices are considered to be covered by the present invention as long as the electronic devices are capable of executing a computer-readable program in a memory to implement the method of the present invention or at least a part of the steps of the method.
From the above description of the embodiments, those skilled in the art will readily appreciate that the present invention can be implemented by hardware capable of executing a specific computer program, such as the system of the present invention, and electronic processing units, servers, clients, mobile phones, control units, processors, etc. included in the system. The invention may also be implemented by computer software for performing the method of the invention, e.g. control software executed by a microprocessor, an electronic control unit, a client, a server, etc. It should be noted that the computer software for executing the method of the present invention is not limited to be executed by one or a specific hardware entity, and can also be realized in a distributed manner by non-specific hardware. For computer software, the software product may be stored in a computer readable storage medium (which may be a CD-ROM, a usb disk, a removable hard disk, etc.) or may be distributed over a network, as long as it enables the electronic device to perform the method according to the present invention.
The above embodiments are only used for illustrating the invention and not for limiting the technical solutions described in the invention, and although the present invention has been described in detail in the present specification with reference to the above embodiments, the present invention is not limited to the above embodiments, and therefore, any modification or equivalent replacement of the present invention is made; all such modifications and variations are intended to be included herein within the scope of this disclosure and the appended claims.
Claims (10)
1. A cloud-native cross-cloud network monitoring method is characterized by comprising the following steps:
respectively deploying a network monitoring node Pingmesh Agent in a container service system of each cloud;
the method comprises the steps that a network monitoring node Pingmesh Agent on each cloud end obtains a network monitoring list pinglist by a network monitoring control center Pingmesh Controller, wherein the network monitoring list pinglist comprises address information of the cloud end deployed by each network monitoring node Pingmesh Agent;
the network monitoring nodes Pingmesh Agent on each cloud terminal concurrently perform ICMP detection aiming at the addresses in the network monitoring list pinglist;
and the network monitoring nodes Pingmesh Agent on each cloud report the ICMP detected data to a Pingmesh Controller of the network monitoring control center.
2. The cloud-based cross-cloud network monitoring method according to claim 1, wherein the network monitoring node Pingmesh Agent automatically registers to a network monitoring Control center Pingmesh Controller when being started, and the network monitoring Control center Pingmesh Controller obtains and maintains a network monitoring list pinglist including address information of a cloud deployed by each network monitoring node Pingmesh Agent.
3. The cross-cloud network monitoring method of claim 2, wherein a heartbeat is maintained between the network monitoring node Pingmesh Agent and a network monitoring control center Pingmesh Controller on each cloud;
the network monitoring node Pingmesh Agent regularly requests a network monitoring control center Pingmesh Controller to obtain the latest version number of a network monitoring list pinglist;
if the obtained network monitoring list pinglist version number is larger than the local version number of the network monitoring node Pingmesh Agent, the network monitoring node Pingmesh Agent obtains the network monitoring list pinglist version of a network monitoring control center Pingmesh Controller and updates the version to the local;
and if the obtained version number of the network monitoring list pinglist is not greater than the local version number of the network monitoring node Pingmesh Agent, the network monitoring node Pingmesh Agent carries out ICMP detection aiming at the address in the local network monitoring list pinglist version.
4. The cloud-based cross-cloud network monitoring method according to claim 3, wherein if the network monitoring Control center Pingmesh Controller does not receive a heartbeat request of the network monitoring node Pingmesh Agent within a preset time period T, it is determined that the corresponding network monitoring node Pingmesh Agent is offline, and the network monitoring Control center Pingmesh Controller removes the offline network monitoring node Pingmesh Agent and synchronously updates data in the network monitoring list pinglist.
5. The method as claimed in claim 1, wherein the data detected by the ICMP of the Pingmesh Agent of the network monitoring node includes an average response delay, a maximum response delay, and a packet loss rate of a cloud server.
6. The method as claimed in claim 1, wherein the ICMP probe data of the pincesh Agent of the network monitoring nodes on the respective cloud terminals received by the pincesh Controller is periodically collected and used as a data source for subsequent drawing of monitoring charts and alarming.
7. The cross-cloud network monitoring method of claim 6, wherein the Pingmesh Controller of the network monitoring control center comprises:
the database is used for storing a network monitoring list pinglist containing address information of a cloud end deployed by each network monitoring node Pingmesh Agent;
the register is used for registering in a Pingmesh Controller of a network monitoring control center when a Pingmesh Agent is newly deployed on a cloud end;
the network monitoring list generator is used for generating a network monitoring list pinglist in the database, adding new address information containing a cloud end deployed by a new network monitoring node Pingmesh Agent, and removing the address information of the cloud end deployed by the offline network monitoring node Pingmesh Agent;
and the Web service module is used for sending display information to a system interface and for monitoring an alarm system and a time sequence database Promeeus to collect ICMP detection data of the Pingmesh Agent of the network monitoring nodes on the cloud terminals received by the network monitoring Control center Pingmesh controller in real time.
8. The method according to claim 1, wherein the container service system of each cloud is a K8s cluster, and the network monitoring node Pingmesh Agent is deployed in the K8s cluster of each cloud in a Deployment manner.
9. A cloud-native, cross-cloud network monitoring apparatus, comprising:
the network monitoring node modules are respectively deployed in the container service systems of all the cloud ends;
the network monitoring control center module is used for storing a network monitoring list pinglist containing address information of a cloud end deployed by each network monitoring node Pingmesh Agent;
the network monitoring node modules on the cloud terminals acquire the network monitoring lists pinglist from the network monitoring control center module, perform ICMP detection aiming at the addresses in the network monitoring lists pinglist concurrently, and report ICMP detected data to the network monitoring control center module.
10. A storage medium storing a computer executable program, wherein the computer executable program, when executed, implements a cloud-native cross-cloud network monitoring method according to any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210071429.4A CN114553867A (en) | 2022-01-21 | 2022-01-21 | Cloud-native cross-cloud network monitoring method and device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210071429.4A CN114553867A (en) | 2022-01-21 | 2022-01-21 | Cloud-native cross-cloud network monitoring method and device and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114553867A true CN114553867A (en) | 2022-05-27 |
Family
ID=81672117
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210071429.4A Pending CN114553867A (en) | 2022-01-21 | 2022-01-21 | Cloud-native cross-cloud network monitoring method and device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114553867A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115883400A (en) * | 2022-11-10 | 2023-03-31 | 中国联合网络通信集团有限公司 | Network monitoring method, device and storage medium |
| CN116781564A (en) * | 2023-07-26 | 2023-09-19 | 上海道客网络科技有限公司 | Network detection method and system for container cloud platform |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104516744A (en) * | 2013-09-27 | 2015-04-15 | 无锡华润微电子有限公司 | Software updating method and system |
| US20170250887A1 (en) * | 2016-02-26 | 2017-08-31 | Arista Networks, Inc. | System and method of a cloud service provider tracer |
| CN110224883A (en) * | 2019-05-29 | 2019-09-10 | 中南大学 | A kind of Grey Fault Diagnosis method applied to telecommunications bearer network |
| CN110784337A (en) * | 2019-09-26 | 2020-02-11 | 平安科技（深圳）有限公司 | Cloud service quality monitoring method and related product |
| CN111193727A (en) * | 2019-12-23 | 2020-05-22 | 成都烽创科技有限公司 | Operation monitoring system and operation monitoring method |
| CN112527354A (en) * | 2020-12-11 | 2021-03-19 | 山东中创软件商用中间件股份有限公司 | Monitoring software upgrading method, device, equipment and readable storage medium |
-
2022
- 2022-01-21 CN CN202210071429.4A patent/CN114553867A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104516744A (en) * | 2013-09-27 | 2015-04-15 | 无锡华润微电子有限公司 | Software updating method and system |
| US20170250887A1 (en) * | 2016-02-26 | 2017-08-31 | Arista Networks, Inc. | System and method of a cloud service provider tracer |
| CN110224883A (en) * | 2019-05-29 | 2019-09-10 | 中南大学 | A kind of Grey Fault Diagnosis method applied to telecommunications bearer network |
| CN110784337A (en) * | 2019-09-26 | 2020-02-11 | 平安科技（深圳）有限公司 | Cloud service quality monitoring method and related product |
| CN111193727A (en) * | 2019-12-23 | 2020-05-22 | 成都烽创科技有限公司 | Operation monitoring system and operation monitoring method |
| CN112527354A (en) * | 2020-12-11 | 2021-03-19 | 山东中创软件商用中间件股份有限公司 | Monitoring software upgrading method, device, equipment and readable storage medium |
Non-Patent Citations (1)
| Title |
|---|
| GUO, CX ET AL: "Pingmesh: A Large-Scale System for Data Center Network Latency Measurement and Analysis", ACM SIGCOMM COMPUTER COMMUNICATION REVIEW, pages 139 - 152 * |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115883400A (en) * | 2022-11-10 | 2023-03-31 | 中国联合网络通信集团有限公司 | Network monitoring method, device and storage medium |
| CN116781564A (en) * | 2023-07-26 | 2023-09-19 | 上海道客网络科技有限公司 | Network detection method and system for container cloud platform |
| CN116781564B (en) * | 2023-07-26 | 2024-02-13 | 上海道客网络科技有限公司 | Network detection method, system, medium and electronic equipment of container cloud platform |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106790595B (en) | Docker container active load balancing device and method | |
| US10389596B2 (en) | Discovering application topologies | |
| US20210328856A1 (en) | Scalability, fault tolerance and fault management for twamp with a large number of test sessions | |
| CN107357571B (en) | Maintenance method and system for equipment component program | |
| US20080016115A1 (en) | Managing Networks Using Dependency Analysis | |
| CN108259215B (en) | Equipment management method and device | |
| CN114553867A (en) | Cloud-native cross-cloud network monitoring method and device and storage medium | |
| CN106411629B (en) | Method and equipment for monitoring state of CDN node | |
| CN110659109A (en) | Openstack cluster virtual machine monitoring system and method | |
| CN111538763A (en) | Method for determining main node in cluster, electronic equipment and storage medium | |
| CN101621548A (en) | Method and system for realizing terminal resource sharing based on peer connection system | |
| US11012306B2 (en) | Autonomous datacenter management plane | |
| US20160092537A1 (en) | Polling based synchronization in managed networks | |
| Abouzamazem et al. | Efficient inter-cloud replication for high-availability services | |
| US7792045B1 (en) | Method and apparatus for configuration and analysis of internal network routing protocols | |
| JP5686027B2 (en) | Network failure detection method, apparatus, and program in virtual machine environment | |
| WO2001022550A1 (en) | Identyfying a failed device in a network | |
| CN103080913B (en) | Method for finding communication devices connected to communication network, and management device | |
| JP2003006068A (en) | Network device managing device, managing method and management program | |
| CN112787868B (en) | Information synchronization method and device | |
| CN112804313B (en) | Data synchronization method, device, equipment and medium based on cross-domain edge node | |
| EP1654653B1 (en) | Active storage area network discovery system and method | |
| CN112511595B (en) | Message pushing method and message service system | |
| CN112073322B (en) | Discovery method and device of network tester | |
| JP2003015973A (en) | Network device management device, management method and management program |
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 |