CN116527507A - KAFKA-based network topology synchronization method - Google Patents

KAFKA-based network topology synchronization method Download PDF

Info

Publication number
CN116527507A
CN116527507A CN202310058458.1A CN202310058458A CN116527507A CN 116527507 A CN116527507 A CN 116527507A CN 202310058458 A CN202310058458 A CN 202310058458A CN 116527507 A CN116527507 A CN 116527507A
Authority
CN
China
Prior art keywords
data
kafka
cvk
network topology
synchronization method
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.)
Granted
Application number
CN202310058458.1A
Other languages
Chinese (zh)
Other versions
CN116527507B (en
Inventor
杨志鹏
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Unicloud Technology Co Ltd
Original Assignee
Unicloud Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Unicloud Technology Co Ltd filed Critical Unicloud Technology Co Ltd
Priority to CN202310058458.1A priority Critical patent/CN116527507B/en
Priority claimed from CN202310058458.1A external-priority patent/CN116527507B/en
Publication of CN116527507A publication Critical patent/CN116527507A/en
Application granted granted Critical
Publication of CN116527507B publication Critical patent/CN116527507B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/12Discovery or management of network topologies
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06Management of faults, events, alarms or notifications
    • H04L41/0631Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/02Topology update or discovery
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/02Topology update or discovery
    • H04L45/021Ensuring consistency of routing table updates, e.g. by using epoch numbers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/32Flooding
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00Reducing energy consumption in communication networks
    • Y02D30/50Reducing energy consumption in communication networks in wire-line communication networks, e.g. low power modes or reduced link rate

Landscapes

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

Abstract

The invention provides a network topology synchronization method based on KAFKA, which comprises the following steps: starting a service; establishing a KAFKA cluster; registering a partition network card on-line data routing algorithm; virtual machine on-line; acquiring online related configuration information; registering callback monitoring; pushing data by KAFKA, and analyzing the data; the topology below the VPC is updated. The invention has the beneficial effects that: the method has the advantages that the network topology instant change notification can be carried out through a broadcasting mechanism, the network communication delay is reduced, the topology convergence capacity is improved, and the data consistency is ensured by utilizing timing comparison; the incremental mode is adopted to carry out data synchronization, so that the total topological synchronization data volume is reduced, the calculation pressure of an Agent process on CVK is reduced, and the topological synchronization efficiency is improved; the message data is actively notified to broadcast, so that the time consumption for communicating with the CVK cluster can be reduced.

Description

KAFKA-based network topology synchronization method
Technical Field
The invention belongs to the technical field of basic capability-cloud computing, and particularly relates to a network topology synchronization method based on KAFKA.
Background
In a cloud computing system, the limitation of hardware communication equipment is relieved through capability support of complex application scenes such as cross-cloud network management, interconnection and intercommunication of a traditional network architecture and an infrastructure, an edge set community and the like, most of communication schemes are realized by virtual network topology, and the communication of resources such as virtual machines is determined by the synchronization speed of the network topology and the convergence scheme of a network protocol. Due to the increasing number of virtual machines used by users and the steep increase in the CVK number of CVK clustered nanotubes, how fast and instantaneous synchronous network topology affects the communication of network traffic. There is therefore a need for a way to synchronize network topologies that combines security, operability, manageability, and performance.
Disclosure of Invention
In view of this, the present invention aims to propose a network topology synchronization method based on KAFKA to solve the deficiencies of the prior art.
In order to achieve the above purpose, the technical scheme of the invention is realized as follows:
a network topology synchronization method based on KAFKA comprises the following steps:
s1, starting service, acquiring information of a KAFKA cluster, and establishing the KAFKA cluster;
s2, registering a partition network card on-line data routing algorithm;
s3, virtual machine on-line;
s4, acquiring online related configuration information;
s5, splicing JSON messages of KAFKA, pushing the data messages to CVK, completing successful data pushing, registering callback monitoring, and waiting for callback results;
s6, if the KAFKA pushing monitoring callback fails, rolling back Mysql data and data in Redis, and sending an alarm mail; if the monitoring callback successfully stores the information of the network card to the Redis, adding the VPC into an audit resource pool;
s7, if the KAFKA pushing monitoring callback fails, rolling back Mysql data and data in Redis, and sending an alarm mail; if the monitoring callback successfully stores the information of the network card to the Redis, adding the VPC into an audit resource pool, and simultaneously executing an audit timing task and a step S8;
s8, CVK-AGNENT process receives KAFKA pushed data, analyzes json data, and judges whether the target L3vni has data at current CVK or not through judging conditions;
s9, updating the topology below the VPC.
Further, the online data routing algorithm in step S2 is a hash modulo partition number algorithm of VPCID.
Further, the configuration information related to the online in step S4 includes L3vni of VPC, network card MAC address, and subnet L2vni information.
Further, the successful data push of the completion in step S5 includes the following steps:
and pushing the data to the KAFKA through the existing API interface of the KAFKA, if the data is pushed, directly rolling back the data stored correspondingly in the Mysql and sending an alarm mail, and if the data is pushed without abnormal conditions, judging that the data is pushed successfully.
Further, the audit timing task in step S7 includes the steps of:
s71, judging whether the VPC exists in the timing comparison person, if so, completing the task, and if not, writing the VPC into the timing comparison list;
s72, comparing the data of the VPCs in the list at fixed time.
Further, the judging condition in step S8 includes the steps of:
s81, judging whether the target L3vni has data at the current CVK, and simultaneously entering step S82 and step S83;
s82, if the current CVK memory data has the target L3vni, directly constructing a synchronous topology, and performing configuration issuing;
s83, if the current CVK memory data does not contain the target L3vni, judging whether CVK information in JSON is current CVK, and simultaneously entering step S84 and step S85;
s84, if the current topology is CVK, pulling the full topology of the current VPC from the control layer, and completing configuration issuing;
and S85, if the message is not the current CVK, discarding the message, and ignoring the relevant configuration issue.
Compared with the prior art, the KAFKA-based network topology synchronization method has the following advantages:
(1) According to the KAFKA-based network topology synchronization method, the broadcasting mechanism can be used for carrying out instant change notification on the network topology, so that network communication delay is reduced, topology convergence capacity is improved, and data consistency is ensured by utilizing timing comparison; the incremental mode is adopted to carry out data synchronization, so that the total topological synchronization data volume is reduced, the calculation pressure of an Agent process on CVK is reduced, and the topological synchronization efficiency is improved; the message data is actively notified to broadcast, so that the time consumption of the trunking communication with CVK can be reduced; topology data compensation is carried out on failure training at regular time through the retention of monitoring records of event change, and virtual machine operation in abnormal state can be effectively synchronized to CVK.
(2) According to the KAFKA-based network topology synchronization method, the data is compared regularly, so that the consistency of the data of a network control layer and the network topology on CVK is ensured; and alarming and sending the alarm immediately through the alarm mail with abnormal operation, and informing operation and maintenance personnel to enter into fault processing in advance.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description serve to explain the invention. In the drawings:
FIG. 1 is a schematic diagram of the overall method according to an embodiment of the present invention.
Detailed Description
It should be noted that, without conflict, the embodiments of the present invention and features of the embodiments may be combined with each other.
In the description of the present invention, it should be understood that the terms "center", "longitudinal", "lateral", "upper", "lower", "front", "rear", "left", "right", "vertical", "horizontal", "top", "bottom", "inner", "outer", etc. indicate orientations or positional relationships based on the orientations or positional relationships shown in the drawings, are merely for convenience in describing the present invention and simplifying the description, and do not indicate or imply that the devices or elements referred to must have a specific orientation, be configured 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 for descriptive purposes only and are not to be construed as indicating or implying a relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first", "a second", etc. may explicitly or implicitly include one or more such feature. In the description of the present invention, unless otherwise indicated, the meaning of "a plurality" is two or more.
In the description of the present invention, it should be noted that, unless explicitly specified and limited otherwise, the terms "mounted," "connected," and "connected" are to be construed broadly, and may be either fixedly connected, detachably connected, or integrally connected, for example; can be mechanically or electrically connected; can be directly connected or indirectly connected through an intermediate medium, and can be communication between two elements. The specific meaning of the above terms in the present invention can be understood by those of ordinary skill in the art in a specific case.
The invention will be described in detail below with reference to the drawings in connection with embodiments.
As shown in fig. 1, the network topology synchronization method based on KAFKA includes the following steps:
1.1 data synchronization in an incremental manner
Data synchronization is performed in a delta topology mode, so that the calculation time of an Agent process on CVK is reduced, and concurrency capacity is improved;
1.2 incremental data synchronization with message notification
Based on the KAFKA message notification mode, incremental synchronization of configuration information is carried out, and data change synchronization topology on the batch notification CVK is carried out;
1.3, ordered message Notification, ensuring reliable arrival of event Notification
Establishing a monitoring mechanism for judging whether the notification is successful or not, reserving data, and orderly issuing and compensating the failed notification again in a timing training mode;
1.4, improving data reliability
By using the message persistence of KAFKA, the partition multiple copies and the ACK mechanism, the loss of configuration information can be effectively avoided, and the system stability is improved;
1.5, improve the operation and maintenance capability
And carrying out alarm monitoring on the operation of failure in sending the message or failure in network card online, and informing operation and maintenance personnel to enter by instant mail to repair related problems and reduce subsequent operation problems.
In the distributed system, KAFKA can effectively solve the current problem, KAFKA can be used as a tens of millions of message pushing middleware, can timely and rapidly push messages, can also obtain relevant configuration information through the persistence message of KAFKA by a client, and can timely inform the client to update the configuration information through message pushing to open traffic. In order to prevent single-point faults, a cluster can be formed by starting a plurality of KAFAKs, multiple copies of a configuration theme are created, multiple copies of data are guaranteed, the fault tolerance of the cluster is improved, the KAFKA cluster uses a multiple copy mechanism of the data, and strong consistency of multi-node data is guaranteed. The network topology synchronization method based on KAFKA of the invention uses the data pushing capability of KAFKA to instantly send configuration related data, informs the network topology information of a large-scale CVK cluster synchronization target resource, relies on an ACK message confirmation mechanism to ensure the reliable arrival of configuration change, introduces a training compensation mechanism to effectively compensate failure data, ensures the final consistency of network topology on a control layer and equipment, and improves the effectiveness and reliability of network communication.
The invention has the advantages that:
the KAFAK-based network topology instant synchronization method can carry out network topology instant change notification through a broadcasting mechanism, reduces network communication delay, improves topology convergence capacity, and ensures data consistency by utilizing timing comparison. The incremental mode is adopted to carry out data synchronization, so that the total topological synchronization data volume is reduced, the calculation pressure of an Agent process on CVK is reduced, and the topological synchronization efficiency is improved; the message data is actively notified to broadcast, so that the time consumption of the trunking communication with CVK can be reduced; topology data compensation is carried out on failure training at regular time through the retention of monitoring records of event change, so that virtual machine operation in abnormal state can be effectively synchronized to CVK; the data is compared regularly, so that the consistency of the data of a network control layer and the network topology on CVK is ensured; and alarming and sending the alarm immediately through the alarm mail with abnormal operation, and informing operation and maintenance personnel to enter into fault processing in advance.
Example 1
The network topology synchronization method based on KAFKA comprises the following steps:
1. service starting to acquire KAFKA cluster information and establishing connection;
2. registering a push network card information algorithm (a hash modulo partition number algorithm according to the VPCID), wherein the algorithm performs hash value taking on the VPCID according to a mode that a built-in API (application program interface) of JAVA programming language character string operation takes hash value on the character string, and then performs modulo taking on the hash value and the file copy number built in KAFKA;
3. according to virtual network card information of virtual machine on-line, obtaining L3vni, network card MAC address and subnet L2vni information of VPC to which the network card belongs, storing data into a database table through Mysql Insert sentence, splicing and pushing KAFKA related JSON message (storing data into Mysql table structure through Mysql Insert sentence) through java character string, wherein the pushing purpose is to make the data message reach CVK to generate network topology information corresponding to the network card information so that the data message reaches CVK to generate topology corresponding to the network card information;
4. pushing to KAFKA data through an existing API interface of KAFKA, if data is pushed, directly reporting barriers, such as link errors, overtime errors and the like, directly rolling back data stored correspondingly in Mysql and sending alarm mails, if the push data does not have abnormal conditions, successfully pushing preliminary task data, registering callback monitoring through the existing API interface of KAFKA, and waiting for callback results;
5. if the KAFKA pushes the monitoring callback to fail, rolling back Mysql data and data in Redis, and sending an alarm mail; if the monitoring callback successfully stores the information of the network card to the Redis, adding the VPC into an audit resource pool;
6. CVK-AGNENT process receives KAFKA pushed data, analyzes JSON data (JSON data is analyzed into the prior art in http transmission, only the deserialization operation of data message is needed, which is the prior art), and judges whether the target L3vni has data at the current CVK;
if the current CVK memory data has the target L3vni, directly constructing a synchronous topology, and performing configuration issuing;
if the current CVK memory data does not contain the target L3vni, judging whether CVK information in the JSON is the current CVK (by analyzing the nic_ cvk _ip attribute of the data message, comparing with the IP of cvk, judging whether the data message is the own CVK), if the data message is the current CVK, pulling the full topology of the current VPC from the control layer to finish configuration issuing, if the data message is not the current CVK, discarding the message, and ignoring relevant configuration issuing;
7. and the audit timing task performs timing comparison on the configuration of the VPCs in the resource pool according to the data of the resource pool to be audited, and completes data detection comparison.
The foregoing description of the preferred embodiments of the invention is not intended to be limiting, but rather is intended to cover all modifications, equivalents, alternatives, and improvements that fall within the spirit and scope of the invention.

Claims (9)

1. The network topology synchronization method based on KAFKA is characterized in that: the method comprises the following steps:
s1, starting service, acquiring information of a KAFKA cluster, and establishing the KAFKA cluster;
s2, registering a partition network card on-line data routing algorithm;
s3, virtual machine on-line;
s4, acquiring online related configuration information;
s5, splicing JSON messages of KAFKA, pushing the data messages to CVK, completing successful data pushing, registering callback monitoring, and waiting for callback results;
s6, if the KAFKA pushing monitoring callback fails, rolling back Mysql data and data in Redis, and sending an alarm mail; if the monitoring callback successfully stores the information of the network card to the Redis, adding the VPC into an audit resource pool;
s7, if the KAFKA pushing monitoring callback fails, rolling back Mysql data and data in Redis, and sending an alarm mail; if the monitoring callback successfully stores the information of the network card to the Redis, adding the VPC into an audit resource pool, and simultaneously executing an audit timing task and a step S8;
s8, CVK-AGNENT process receives KAFKA pushed data, analyzes json data, and judges whether the target L3vni has data at current CVK or not through judging conditions;
s9, updating the topology below the VPC.
2. The KAFKA based network topology synchronization method of claim 1, wherein: the online data routing algorithm in step S2 is a hash modulo partition number algorithm of VPCID.
3. The KAFKA based network topology synchronization method of claim 1, wherein: the online relevant configuration information in step S4 includes L3vni of VPC, network card MAC address, subnet L2vni information.
4. The KAFKA based network topology synchronization method of claim 1, wherein: the successful completion data push in step S5 includes the steps of:
and pushing the data to the KAFKA through the existing API interface of the KAFKA, if the data is pushed, directly rolling back the data stored correspondingly in the Mysql and sending an alarm mail, and if the data is pushed without abnormal conditions, judging that the data is pushed successfully.
5. The KAFKA based network topology synchronization method of claim 1, wherein: the audit timing task in step S7 includes the steps of:
s71, judging whether the VPC exists in the timing comparison person, if so, completing the task, and if not, writing the VPC into the timing comparison list;
s72, comparing the data of the VPCs in the list at fixed time.
6. The KAFKA based network topology synchronization method of claim 1, wherein: the judgment condition in step S8 includes the steps of:
s81, judging whether the target L3vni has data at the current CVK, and simultaneously entering step S82 and step S83;
s82, if the current CVK memory data has the target L3vni, directly constructing a synchronous topology, and performing configuration issuing;
s83, if the current CVK memory data does not contain the target L3vni, judging whether CVK information in JSON is current CVK, and simultaneously entering step S84 and step S85;
s84, if the current topology is CVK, pulling the full topology of the current VPC from the control layer, and completing configuration issuing;
and S85, if the message is not the current CVK, discarding the message, and ignoring the relevant configuration issue.
7. An electronic device comprising a processor and a memory communicatively coupled to the processor for storing processor-executable instructions, characterized in that: the processor is configured to perform the KAFKA based network topology synchronization method of any one of claims 1-6.
8. A server, characterized by: comprising at least one processor and a memory communicatively coupled to the processor, the memory storing instructions executable by the at least one processor to cause the at least one processor to perform the KAFKA based network topology synchronization method of any one of claims 1-6.
9. A computer-readable storage medium storing a computer program, characterized in that: the computer program, when executed by a processor, implements the KAFKA based network topology synchronization method of any one of claims 1-6.
CN202310058458.1A 2023-01-16 KAFKA-based network topology synchronization method Active CN116527507B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310058458.1A CN116527507B (en) 2023-01-16 KAFKA-based network topology synchronization method

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310058458.1A CN116527507B (en) 2023-01-16 KAFKA-based network topology synchronization method

Publications (2)

Publication Number Publication Date
CN116527507A true CN116527507A (en) 2023-08-01
CN116527507B CN116527507B (en) 2024-05-24

Family

ID=

Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160269247A1 (en) * 2015-03-13 2016-09-15 Nec Laboratories America, Inc. Accelerating stream processing by dynamic network aware topology re-optimization
CN106131919A (en) * 2016-07-15 2016-11-16 中国电子科技集团公司第五十四研究所 A kind of synchronous method of non-stop layer self-organized network topology
US20170102933A1 (en) * 2015-10-08 2017-04-13 Opsclarity, Inc. Systems and methods of monitoring a network topology
US20190238636A1 (en) * 2018-01-31 2019-08-01 Symantec Corporation Systems and methods for synchronizing microservice data stores
US20200042365A1 (en) * 2018-07-31 2020-02-06 Parallel Wireless, Inc. Service Bus for Telecom Infrastructure
CN111314023A (en) * 2020-02-18 2020-06-19 中国电子科技集团公司第五十四研究所 Synchronization method of tree network topology information
CN113129063A (en) * 2021-04-20 2021-07-16 国网江西省电力有限公司信息通信分公司 Electricity charge calculation and distribution method and system based on cloud platform and data center
CN114661490A (en) * 2022-02-23 2022-06-24 盈立数智科技(深圳)有限公司 Market delay method and system based on streaming system
WO2022233204A1 (en) * 2021-05-06 2022-11-10 中兴通讯股份有限公司 D2d network topology control method, network device, and storage medium
CN115589365A (en) * 2022-08-26 2023-01-10 紫光云技术有限公司 Network topology synchronization method based on Canal

Patent Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160269247A1 (en) * 2015-03-13 2016-09-15 Nec Laboratories America, Inc. Accelerating stream processing by dynamic network aware topology re-optimization
US20170102933A1 (en) * 2015-10-08 2017-04-13 Opsclarity, Inc. Systems and methods of monitoring a network topology
CN106131919A (en) * 2016-07-15 2016-11-16 中国电子科技集团公司第五十四研究所 A kind of synchronous method of non-stop layer self-organized network topology
US20190238636A1 (en) * 2018-01-31 2019-08-01 Symantec Corporation Systems and methods for synchronizing microservice data stores
US20200042365A1 (en) * 2018-07-31 2020-02-06 Parallel Wireless, Inc. Service Bus for Telecom Infrastructure
CN111314023A (en) * 2020-02-18 2020-06-19 中国电子科技集团公司第五十四研究所 Synchronization method of tree network topology information
CN113129063A (en) * 2021-04-20 2021-07-16 国网江西省电力有限公司信息通信分公司 Electricity charge calculation and distribution method and system based on cloud platform and data center
WO2022233204A1 (en) * 2021-05-06 2022-11-10 中兴通讯股份有限公司 D2d network topology control method, network device, and storage medium
CN114661490A (en) * 2022-02-23 2022-06-24 盈立数智科技(深圳)有限公司 Market delay method and system based on streaming system
CN115589365A (en) * 2022-08-26 2023-01-10 紫光云技术有限公司 Network topology synchronization method based on Canal

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
MIKHAIL A. MISHCHENKO 等: ""The role of connections topology on synchronization in neural network"", 《2022 6TH SCIENTIFIC SCHOOL DYNAMICS OF COMPLEX NETWORKS AND THEIR APPLICATIONS (DCNA)》, 21 October 2022 (2022-10-21) *
QIN ZHEN 等: ""Synchronization of multi-weighted complex dynamical networks with fixed and switching topologies"", 《2017 36TH CHINESE CONTROL CONFERENCE (CCC)》, 11 October 2017 (2017-10-11) *
吕翎: ""具有不确定拓扑及不同节点的时滞网络的时空同步"", 《万方数据库》, 24 February 2021 (2021-02-24) *
郝修清 等: ""拓扑结构时变的复杂动态网络的自适应同步"", 《西安电子科技大学学报(自然科学版)》, 27 April 2015 (2015-04-27) *
陆君安: ""复杂网络的同步和拓扑结构的识别"", 《复杂***与复杂性科学》, 28 January 2011 (2011-01-28) *

Similar Documents

Publication Publication Date Title
EP2434688B1 (en) Method and system for analyzing alarm root cause
EP3905590A1 (en) System and method for obtaining network topology, and server
CN107925619B (en) System and method for handling link loss in a network
CN106850260A (en) A kind of dispositions method and device of virtual resources management platform
CN102916825A (en) Management equipment of dual-computer hot standby system, management method and dual-computer hot standby system
CN112787960B (en) Stack splitting processing method, device and equipment and storage medium
CN105959349B (en) A kind of Distributed Services end operating system and method
WO2011120452A2 (en) Method for updating data and control apparatus thereof
US11831746B2 (en) Time consistency synchronization method for distributed simulation
CN111385107A (en) Main/standby switching processing method and device for server
CN113965578A (en) Method, device, equipment and storage medium for electing master node in cluster
CN113746733A (en) Table item synchronization method, gateway equipment, networking system and storage medium
WO2022037359A1 (en) Configuration data access method, apparatus, and device, configuration center, and storage medium
CN116527507B (en) KAFKA-based network topology synchronization method
CN114553867A (en) Cloud-native cross-cloud network monitoring method and device and storage medium
CN116527507A (en) KAFKA-based network topology synchronization method
CN104780067A (en) Method and device for rebooting PE (port extender)
US20230095362A1 (en) Routing Packet Processing Method, Communication Device, Storage Medium, and System
CN116094938B (en) KAFKA-based network topology synchronization method, KAFKA-based network topology synchronization equipment, server and storage medium
CN112615944B (en) Method and system for master-slave synchronization of distributed DNS (Domain name System)
CN111464346B (en) Main and standby control board synchronization method and system based on ATCA (advanced telecom computing architecture)
CN114257500B (en) Fault switching method, system and device for super-fusion cluster internal network
CN114490691B (en) Distributed system data consistency method
CN107231308B (en) Cross-site basic data intelligent learning and link pre-searching method
CN214959613U (en) Load balancing equipment

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