CN116192801B - DHCP (dynamic host configuration protocol) table entry synchronization method, equipment and medium based on MLAG (media-based access control) environment - Google Patents

DHCP (dynamic host configuration protocol) table entry synchronization method, equipment and medium based on MLAG (media-based access control) environment Download PDF

Info

Publication number
CN116192801B
CN116192801B CN202310142375.0A CN202310142375A CN116192801B CN 116192801 B CN116192801 B CN 116192801B CN 202310142375 A CN202310142375 A CN 202310142375A CN 116192801 B CN116192801 B CN 116192801B
Authority
CN
China
Prior art keywords
dhcp
equipment
address
type
message
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202310142375.0A
Other languages
Chinese (zh)
Other versions
CN116192801A (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.)
Inspur Cisco Networking Technology Co Ltd
Original Assignee
Inspur Cisco Networking 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 Inspur Cisco Networking Technology Co Ltd filed Critical Inspur Cisco Networking Technology Co Ltd
Priority to CN202310142375.0A priority Critical patent/CN116192801B/en
Publication of CN116192801A publication Critical patent/CN116192801A/en
Application granted granted Critical
Publication of CN116192801B publication Critical patent/CN116192801B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/50—Reducing energy consumption in communication networks in wire-line communication networks, e.g. low power modes or reduced link rate

Abstract

The application discloses a DHCP table entry synchronization method, equipment and medium based on an MLAG environment. The method comprises the following steps: the aggregation transmission equipment deploys a DHCP server address pool and classifies a common class address pool and a private class address pool; receiving a DHCP message and determining an address pool type of a corresponding address pool and aggregation transmission equipment; if the address pool corresponding to the DHCP message is a private class address pool, the DHCP message is processed through the aggregation transmission equipment corresponding to the DHCP message, and if the address pool corresponding to the DHCP message is a common class address pool, the equipment type of the aggregation transmission equipment corresponding to the DHCP message is determined; if the equipment type of the DHCP message corresponding to the aggregation transmission equipment is the main equipment type, the DHCP message is processed by the main equipment in the MLAG, and if the equipment type of the DHCP message corresponding to the aggregation transmission equipment is the standby equipment type, the DHCP message is forwarded to the main equipment for processing by the peer-link interface; and taking the corresponding allocation address table entry of the main equipment as a common address table entry and synchronizing the main equipment with the standby equipment, so as to realize the DHCP table entry synchronization under the MLAG environment.

Description

DHCP (dynamic host configuration protocol) table entry synchronization method, equipment and medium based on MLAG (media-based access control) environment
Technical Field
The present application relates to the field of communications technologies, and in particular, to a DHCP entry synchronization method, device, and medium based on an MLAG environment.
Background
Conventional lateral virtualization techniques are commonly used in cross-device link aggregation group (Multi-chassis Link Aggregation Group, MLAG), which guarantees high reliability due to its device-level redundancy, policing separation, eliminating STP loops, and reducing CPU usage. The traditional park network core equipment needs to deploy a DHCP Server, so as to meet the requirement of park network user address acquisition; the core equipment of the park network can use MLAG to realize the backup of the master equipment and the slave equipment, and the control plane separation reduces the CPU pressure and increases the network reliability; but the data plane cannot synchronize DHCP Server entries with each other. When a DHCP Server is deployed in an MLAG scene, if the address pools configured on the main and the standby are different, the distributed address list items are not synchronous, and the problems of repeated address distribution, client renting and address releasing failure and the like are caused.
At present, in the prior art scheme for synchronizing DHCP Server entries under the MLAG scene, all DHCP messages are processed by a master device, the slave device receives the DHCP messages and then forwards the DHCP messages to the master device, and after the master device allocates an address, the master device synchronizes the binding address entries to the slave device in real time, so that the mutual synchronization of the master device and the slave device is realized. However, for the manner of processing all DHCP messages by the master device in the MLAG scenario, it is necessary to ensure that the address pools of the master device and the slave device are the same, and if there is a difference in the address pools of the master device and the slave device, the synchronization of the DHCP Server entries will be affected. If the main equipment fails, the unsynchronized address list items cannot be rented and released on the standby equipment, so that the address allocation is abnormal; in addition, since all DHCP messages of the standby equipment are forwarded to the main equipment, other clients cannot be externally connected to the standby equipment, and limitation exists in network deployment.
Disclosure of Invention
The embodiment of the application provides a DHCP (dynamic host configuration protocol) table entry synchronization method, equipment and medium based on an MLAG (media-based access control) environment, which are used for solving the technical problems that the existing table entry synchronization method needs to ensure that the address pools of main equipment and standby equipment are the same, if the main equipment fails, the unsynchronized address table entries cannot be leased and released on the standby equipment, so that the address allocation is abnormal, and because all DHCP messages of the standby equipment are forwarded to the main equipment, other clients cannot be externally connected to the standby equipment, and the network deployment is limited.
On one hand, the embodiment of the application provides a DHCP table entry synchronization method based on an MLAG environment, which comprises the following steps:
receiving a DHCP message, and determining an address pool type of an address pool corresponding to the DHCP message and aggregation transmission equipment corresponding to the DHCP message; the address pool type comprises a common class address pool and a private class address pool;
if the address pool corresponding to the DHCP message is a private type address pool, processing the DHCP message through aggregation transmission equipment corresponding to the DHCP message, and if the address pool corresponding to the DHCP message is a common type address pool, determining the equipment type of the aggregation transmission equipment corresponding to the DHCP message; the device types comprise a main device type and a standby device type in a cross-device link aggregation group (MLAG);
If the equipment type of the aggregation transmission equipment corresponding to the DHCP message is a main equipment type, the DHCP message is processed through a main equipment in a cross-equipment link aggregation group (MLAG), and if the equipment type of the aggregation transmission equipment corresponding to the DHCP message is a standby equipment type, the DHCP message is forwarded to the main equipment through a peer-link interface for processing;
and taking the allocation address table entry corresponding to the main equipment as a common address table entry, and synchronizing the common address table entry to the standby equipment in the cross-equipment link aggregation group MLAG through the main equipment so as to realize DHCP table entry synchronization in the MLAG environment.
In one implementation manner of the present application, before the receiving the DHCP packet and determining an address pool type of an address pool corresponding to the DHCP packet and an aggregation transmission device corresponding to the DHCP packet, the method further includes:
determining a main device and a standby device in a cross-device link aggregation group (MLAG), and configuring a corresponding address pool for the main device and the standby device in the cross-device link aggregation group (MLAG);
performing consistency check on address pools corresponding to the main equipment and the standby equipment, and obtaining corresponding consistency check results; the consistency check includes at least one or more of: subnet mask check, gateway address check, and DNS server address check;
If the consistency check results are all passed, determining that the types of the address pools corresponding to the main equipment and the standby equipment are common class address pools;
if the consistency check results are not passed, determining that the types of the address pools corresponding to the main equipment and the standby equipment are private type address pools;
and if the consistency check results are abnormal alarms, taking the address pools corresponding to the main equipment and the standby equipment as invalid address pools.
In one implementation manner of the present application, the receiving a DHCP packet and determining an address pool type of an address pool corresponding to the DHCP packet and an aggregation transmission device corresponding to the DHCP packet specifically includes:
receiving a DHCP Discover message of a DHCP client, and associating an address pool and distributing an IP address for the DHCP client based on the DHCP Discover message;
and determining aggregation transmission equipment corresponding to the DHCP message in a cross-equipment link aggregation group (MLAG) and an address pool type corresponding to the DHCP message according to the IP address allocated to the DHCP client and the associated address pool.
In one implementation manner of the present application, if the address pool corresponding to the DHCP packet is a private address pool, processing the DHCP packet by using an aggregation transmission device corresponding to the DHCP packet specifically includes:
Under the condition that the address pool corresponding to the DHCP message is determined to be a private address pool, determining the equipment type of aggregation transmission equipment corresponding to the DHCP message;
if the aggregation transmission equipment corresponding to the DHCP message is of a main equipment type, processing the DHCP message through a main equipment in a cross-equipment link aggregation group (MLAG), and taking an allocation address table entry in the main equipment as a private address table entry of the main equipment;
if the aggregation transmission equipment corresponding to the DHCP message is of a standby equipment type, the DHCP message is processed through the standby equipment in the cross-equipment link aggregation group MLAG, and an allocation address table entry in the standby equipment is used as a private address table entry of the standby equipment.
In one implementation manner of the present application, if the device type of the aggregation transmission device corresponding to the DHCP packet is a master device type, the processing, by the master device in the cross-device link aggregation group MLAG, the DHCP packet specifically includes:
under the condition that the equipment type of the aggregation transmission equipment corresponding to the DHCP message is the main equipment type, distributing an IP address to a DHCP client corresponding to a DHCP Discover message through a main equipment in a cross-equipment link aggregation group (MLAG) and based on the DHCP Offer message;
Receiving a DHCP Request message returned by the DHCP client side, and determining an IP address to be requested carried in the DHCP Request message;
and through the DHCP Ack message, the corresponding IP address to be requested is determined to be allocated for the DHCP client.
In one implementation manner of the present application, if the device type of the aggregation transmission device corresponding to the DHCP packet is a standby device type, forwarding the DHCP packet to the master device through the peer-link interface for processing, including:
under the condition that the equipment type of the aggregation transmission equipment corresponding to the DHCP message is the spare equipment type, forwarding the DHCP message to the main equipment through the spare equipment in the cross-equipment link aggregation group MLAG and based on a peer-link interface between the main equipment and the spare equipment in the cross-equipment link aggregation group MLAG;
and associating an address pool and distributing an IP address for the DHCP client through the master equipment based on the DHCP Offer message so that the DHCP client obtains the corresponding IP address.
In one implementation manner of the present application, the step of using the allocation address table entry corresponding to the master device as a common address table entry, and synchronizing, by the master device, the common address table entry to a standby device in the cross-device link aggregation group MLAG, to achieve DHCP table entry synchronization in an MLAG environment, includes:
Determining that the DHCP message corresponds to a DHCP client, and taking an allocation address table entry corresponding to the allocation address of the host equipment for the DHCP client as a common address table entry;
and synchronizing the common address table entry to the standby equipment through the main equipment based on a peer-link interface and a TCP protocol between the main equipment and the standby equipment so as to realize DHCP table entry synchronization in an MLAG environment.
In one implementation manner of the present application, after the synchronizing, by the master device, the common address entry to the backup device in the cross-device link aggregation group MLAG, the DHCP entry in the MLAG environment is synchronized, the method further includes:
determining that the address pool type is a private address pool and the equipment type of the aggregation transmission equipment is a DHCP client of the main equipment type, and releasing the IP address acquired by the corresponding DHCP client through the main equipment;
determining that the address pool type is a private address pool and the equipment type of the aggregation transmission equipment is a DHCP client of the standby equipment type, and releasing an IP address acquired by the DHCP client through the standby equipment;
determining that the address type is a DHCP client side of a common class address pool, and determining that an address Release message corresponds to the equipment type of receiving equipment;
If the equipment type is the main equipment type, processing the address Release message through the main equipment;
if the equipment type is the standby equipment type, forwarding the address Release message to a main equipment through the standby equipment so as to process the address Release message through the main equipment and synchronize the corresponding address table entry to the standby equipment.
On the other hand, the embodiment of the application also provides a DHCP entry synchronization device based on the MLAG environment, which comprises:
at least one processor;
and a memory communicatively coupled to the at least one processor;
wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to perform a DHCP entry synchronization method based on an MLAG environment as described above.
In another aspect, embodiments of the present application also provide a non-volatile computer storage medium storing computer-executable instructions configured to:
the DHCP table entry synchronization method based on the MLAG environment is as described above.
The embodiment of the application provides a DHCP table entry synchronization method, equipment and medium based on an MLAG environment, which at least comprise the following beneficial effects:
the received DHCP message can determine the DHCP client corresponding to the DHCP message, the address pool type of the corresponding address pool and the aggregation transmission equipment for receiving the DHCP message; when the address pool is a private type address pool, the DHCP message is processed through the corresponding aggregation transmission equipment, when the address pool is a common type address pool, the equipment type of the aggregation transmission equipment is continuously determined, when the equipment type is a main equipment type, the DHCP message is processed through a main equipment in a cross-equipment link aggregation group (MLAG), when the equipment type is a standby equipment type, the DHCP message is forwarded to the main equipment for processing through a standby equipment in the cross-equipment link aggregation group (MLAG), the common type address pool is subjected to item synchronization through a method for classifying the MLAG main and standby equipment address pools, and the private type address pool is independently processed through the corresponding main and standby equipment, so that the limitation of network deployment can be solved, and the item synchronization of the common type address pool can be ensured.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiments of the application and together with the description serve to explain the application and do not constitute an undue limitation to the application. In the drawings:
Fig. 1 is a schematic flow chart of a DHCP entry synchronization method based on an MLAG environment according to an embodiment of the present application;
fig. 2 is a schematic view of an application scenario provided in an embodiment of the present application;
fig. 3 is a flow chart of another DHCP entry synchronization method based on an MLAG environment according to an embodiment of the present application;
fig. 4 is a schematic internal structure diagram of a DHCP entry synchronization device based on an MLAG environment according to an embodiment of the present application.
Detailed Description
For the purposes, technical solutions and advantages of the present application, the technical solutions of the present application will be clearly and completely described below with reference to specific embodiments of the present application and corresponding drawings. It will be apparent that the described embodiments are only some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.
The embodiment of the application provides a DHCP table entry synchronization method, equipment and medium based on an MLAG environment, which can determine a DHCP client corresponding to a DHCP message, an address pool type of a corresponding address pool and aggregation transmission equipment for receiving the DHCP message through the received DHCP message; when the address pool is a private type address pool, the DHCP message is processed through the corresponding aggregation transmission equipment, when the address pool is a common type address pool, the equipment type of the aggregation transmission equipment is continuously determined, when the equipment type is a main equipment type, the DHCP message is processed through a main equipment in a cross-equipment link aggregation group (MLAG), when the equipment type is a standby equipment type, the DHCP message is forwarded to the main equipment for processing through a standby equipment in the cross-equipment link aggregation group (MLAG), the common type address pool is subjected to item synchronization through a method for classifying the MLAG main and standby equipment address pools, and the private type address pool is independently processed through the corresponding main and standby equipment, so that the limitation of network deployment can be solved, and the item synchronization of the common type address pool can be ensured.
The following describes in detail the technical solutions provided by the embodiments of the present application with reference to the accompanying drawings.
As shown in fig. 1, a DHCP entry synchronization method based on an MLAG environment provided in an embodiment of the present application includes:
101. and receiving the DHCP message, and determining the address pool type of the address pool corresponding to the DHCP message and the aggregation transmission equipment corresponding to the DHCP message.
The DHCP server receives the DHCP message broadcast by the DHCP client and determines the address pool type of the address pool corresponding to the DHCP message and the aggregation transmission equipment corresponding to the DHCP message. It should be noted that, in the embodiment of the present application, the address pool type includes a common class address pool and a private class address pool.
Specifically, the DHCP client sends a DHCP Discover message to inquire whether a DHCP server exists or not in a broadcast mode, the DHCP server receives the DHCP Discover message broadcast by the DHCP client, associates an address pool for the DHCP client corresponding to the DHCP Discover message and allocates an IP address for the DHCP client based on the DHCP Discover message, and then determines an aggregation transmission device corresponding to the DHCP message in the cross-device link aggregation group MLAG and an address pool type corresponding to the DHCP message according to the IP address allocated for the DHCP client and the associated address pool.
In one embodiment of the present application, before receiving a DHCP packet and determining an address pool type of an address pool corresponding to the DHCP packet and an aggregation transmission device corresponding to the DHCP packet, the DHCP server needs to determine a master device and a slave device in a cross-device link aggregation group MLAG, configure the corresponding address pools for the master device and the slave device in the cross-device link aggregation group MLAG, and then further needs to perform a consistency check on the address pools corresponding to the master device and the slave device, and obtain a corresponding consistency check result. It should be noted that, the consistency check in the embodiments of the present application at least includes one or more of the following: subnet mask check, gateway address check, and DNS server address check.
If the consistency check results are all passed, the DHCP server determines that the address pools corresponding to the main equipment and the standby equipment are common address pools, if the consistency check results are not passed, the DHCP server determines that the address pools corresponding to the main equipment and the standby equipment are private address pools, and if the consistency check results are abnormal alarms, the DHCP server takes the address pools corresponding to the main equipment and the standby equipment as invalid address pools.
Fig. 2 is a schematic view of an application scenario provided in the embodiment of the present application. As shown in fig. 2, the present application constructs switch 1 and switch 2 as a cross-device link aggregation group MLAG through a cross-device aggregation port, takes switch 1 as a master device in the cross-device link aggregation group MLAG, and configures a DHCP server address pool for switch 1: address pool 12 and address pool 1, and switch 2 as a backup device in the cross device link aggregation group MLAG, and configures a DHCP server address pool for switch 2: address pool 12 and address pool 2.
The DHCP server performs consistency check on the address pool 12 and the address pool 1 corresponding to the switch 1 and the address pool 12 and the address pool 2 corresponding to the switch 2, so that it can be determined that the address pool 12 and the address pool 12 corresponding to the switch 1 and the switch 2 are common class address pools, the address pool 1 corresponding to the switch 1 is a private class address pool of the switch 1, and the address pool 2 corresponding to the switch 2 is a private class address pool of the switch 2.
102. If the address pool corresponding to the DHCP message is a private type address pool, the DHCP message is processed through aggregation transmission equipment corresponding to the DHCP message, and if the address pool corresponding to the DHCP message is a common type address pool, the equipment type of the aggregation transmission equipment corresponding to the DHCP message is determined.
If the address pool corresponding to the DHCP message is determined to be the private type address pool, the DHCP server directly processes the DHCP message through the aggregation transmission equipment corresponding to the determined DHCP message, and under the condition that the address pool corresponding to the DHCP message is determined to be the common type address pool, the DHCP server also needs to determine the equipment type of the aggregation transmission equipment corresponding to the DHCP message. It should be noted that, the device types in the embodiments of the present application include a primary device type and a backup device type in the cross-device link aggregation group MLAG.
Specifically, when determining that the address pool corresponding to the DHCP packet is a private address pool, the DHCP server also needs to determine a device type of the aggregation transmission device corresponding to the DHCP packet, and when the aggregation transmission device corresponding to the DHCP packet is a master device type, the DHCP packet is processed by a master device in the cross-device link aggregation group MLAG, and an allocation address table in the master device is used as a private address table of the master device, and when the aggregation transmission device corresponding to the DHCP packet is a spare device type, the DHCP server processes the DHCP packet by a spare device in the cross-device link aggregation group MLAG, and takes the allocation address table in the spare device as a private address table of the spare device.
In one embodiment of the present application, as shown in fig. 2, when the DHCP client 1 in the present application obtains the IP address in the address pool 1, the switch 1 receives, as the DHCP server, the DHCP Discover message broadcasted by the DHCP client 1, and then determines that the address pool 1 where the DHCP client 1 needs to obtain the IP address is the private address pool corresponding to the switch 1, so that the service requirement that the DHCP client 1 obtains the IP address can be achieved by directly using the switch 1 as the DHCP server to allocate the IP address to the DHCP client 1, and the allocation address entry allocated by the DHCP server for the DHCP client 1 belongs to the private address entry of the DHCP client 1, without synchronizing the private address entry to the switch 2 as the standby device.
Similarly, when the DHCP client 2 acquires the IP address in the address pool 2, the switch 2 receives, as the DHCP server, the DHCP Discover message broadcasted by the DHCP client 2, and then determines that the address pool 2 from which the DHCP client 2 needs to acquire the IP address is the private class address pool corresponding to the switch 2, so that the service requirement that the DHCP client 2 acquires the IP address can be achieved by directly using the switch 2 as the DHCP server to allocate the IP address to the DHCP client 2, and an allocation address table entry of the DHCP server for allocating the address to the DHCP client 2 belongs to the private address table entry of the DHCP client 2, without synchronizing the private address table entry to the switch 1 serving as the master device.
103. If the equipment type of the aggregation transmission equipment corresponding to the DHCP message is the main equipment type, the DHCP message is processed through the main equipment in the cross-equipment link aggregation group MLAG, and if the equipment type of the aggregation transmission equipment corresponding to the DHCP message is the standby equipment type, the DHCP message is forwarded to the main equipment through a peer-link interface for processing.
Specifically, when the device type of the aggregation transmission device corresponding to the DHCP packet is the master device type, the DHCP server allocates an IP address to the DHCP client corresponding to the DHCP Discover packet through the master device in the cross-device link aggregation group MLAG and based on the DHCP Offer packet, then receives a DHCP Request packet returned by the DHCP client, determines an IP address to be requested carried in the DHCP Request packet, and further determines to allocate the corresponding IP address to be requested to the DHCP client through the DHCP Ack packet.
And the DHCP server forwards the DHCP message to the main device through the standby device in the cross-device link aggregation group MLAG and based on a peer-link interface between the main device and the standby device in the cross-device link aggregation group MLAG under the condition that the device type of the aggregation transmission device corresponding to the DHCP message is the standby device type, then distributes an IP address for a DHCP client corresponding to the DHCP Discover message through the main device in the cross-device link aggregation group MLAG and based on the DHCP Offer message, further receives a DHCP Request message returned by the DHCP client, determines an IP address to be requested carried in the DHCP Request message, and finally determines to distribute the corresponding IP address to be requested for the DHCP client through the DHCP Ack message.
In an embodiment of the present application, as shown in fig. 2, when the DHCP client 3 acquires the IP address in the address pool 12, since the address pool 12 is a common class address pool, the DHCP server also needs to determine whether the address pool 12 of the IP address acquired by the DHCP client 3 is the common class address pool corresponding to the switch 1 as the master device or the common class address pool corresponding to the switch 2 as the standby device.
When the IP address acquired by the DHCP client 3 is the address in the address pool 12 in the switch 1 as the master device, the switch 1 as the master device in the cross-device link aggregation group MLAG directly processes the DHCP message broadcasted by the DHCP client 3, and allocates the IP address to the DHCP client 3. In the case where the IP address acquired by the DHCP client 3 is an address in the address pool 12 in the switch 2 as the standby device, the switch 2 as the standby device in the cross-device link aggregation group MLAG cannot process the DHCP packet sharing the class address pool, and therefore, it is necessary to forward the DHCP packet to the host device for processing through the peer-link interface between the host device and the standby device.
104. And taking the allocation address table entry corresponding to the main equipment as a common address table entry, and synchronizing the common address table entry to the standby equipment in the cross-equipment link aggregation group MLAG through the main equipment, so as to realize the DHCP table entry synchronization in the MLAG environment.
After the DHCP server processes the DHCP message in the shared class address pool through the main device, the distributed address table item corresponding to the DHCP message processed by the main device is used as the shared address table item, and the shared address table item is synchronized to the standby device in the cross-device link aggregation group MLAG through the main device, so that the DHCP table item synchronization under the MLAG environment can be realized.
Specifically, the DHCP server needs to determine that the DHCP packet corresponds to the DHCP client, and uses an allocation address table corresponding to an allocation address of the DHCP client as a common address table, and then synchronizes the common address table to the backup device based on a peer-link interface and a TCP protocol between the primary device and the backup device through the primary device, so as to achieve DHCP table synchronization in the MLAG environment.
In one embodiment of the present application, after synchronizing, by a host device, a common address entry to a standby device in a cross-device link aggregation group MLAG, and implementing DHCP entry synchronization in an MLAG environment, a DHCP server determines that an address pool type is a private type address pool, and that a device type of an aggregation transmission device is a DHCP client of a host device type, and then directly releases, by the host device, an IP address acquired by the DHCP client of the type.
The DHCP server determines that the address pool type is a private address pool, the equipment type of the aggregation transmission equipment is a DHCP client of the standby equipment type, and then the standby equipment is used for directly releasing the IP address acquired by the DHCP client of the type.
The DHCP server determines that the address type is a DHCP client side of a common type address pool, determines that the address Release message corresponds to the equipment type of the receiving equipment, processes the address Release message through the main equipment aiming at the receiving equipment with the equipment type being the main equipment type, and forwards the address Release message to the main equipment through the standby equipment aiming at the receiving equipment with the equipment type being the standby equipment type, processes the address Release message through the main equipment, and then synchronizes an address table item corresponding to the processed address Release message to the standby equipment.
In one embodiment of the present application, as shown in fig. 2, when the DHCP client 3 in the present application acquires the IP address in the address pool 12, since the address pool 12 is a common class address pool, the switch 1 as the master device needs to synchronize the allocation address table entry for allocating the IP address to the DHCP client 3 to the switch 2 as the slave device, so as to achieve DHCP table synchronization in the MLAG environment.
Fig. 3 is a flowchart of another DHCP entry synchronization method based on an MLAG environment according to an embodiment of the present application. As shown in fig. 3, when receiving a DHCP message broadcast by a DHCP client, the DHCP server needs to associate an address pool with the DHCP client, and can determine whether the DHCP message is a DHCP message received by a common class address pool according to the associated address pool.
If not, the DHCP server needs to continuously determine whether the DHCP message is received by the private address pool, if not, the address pool corresponding to the DHCP message is directly used as an invalid address pool, so that the DHCP message is directly discarded, if so, the receiving equipment corresponding to the address pool through the DHCP message directly processes the DHCP message, and because the address pool corresponding to the DHCP message is the private address pool, the DHCP server allocates an address table entry for the DHCP message as the private address table entry of the receiving equipment corresponding to the address pool, and synchronization is not needed.
If yes, the DHCP server continues to judge whether the address pool for receiving the DHCP message is the main device in the MLAG, if yes, the DHCP message is processed directly through the main device, the address list item of the DHCP server is used as a shared address list item and is synchronized to the standby device, if not, the DHCP message is required to be forwarded to the main device through a peer-link interface between the main device and the standby device, then the main device processes the DHCP message, and the address list item of the DHCP server is used as a shared address list item and is synchronized to the standby device. Then, the standby device acquires the synchronized common address table entry and adds the common address table entry to the common address table entry of the DHCP server.
It should be noted that the method shown in fig. 3 is substantially the same as the method shown in fig. 1, and therefore, the portions not described in detail in fig. 3 may be specifically referred to the related description in fig. 1, which is not repeated herein.
The foregoing is a method embodiment presented herein. Based on the same inventive concept, the embodiment of the application also provides a DHCP entry synchronization device based on the MLAG environment, and the structure of the DHCP entry synchronization device is shown in fig. 4.
Fig. 4 is a schematic internal structure diagram of a DHCP entry synchronization device based on an MLAG environment according to an embodiment of the present application. As shown in fig. 4, the apparatus includes:
at least one processor;
and a memory communicatively coupled to the at least one processor;
wherein the memory stores instructions executable by the at least one processor, the instructions being executable by the at least one processor to enable the at least one processor to:
receiving a DHCP message, and determining an address pool type of an address pool corresponding to the DHCP message and aggregation transmission equipment corresponding to the DHCP message; the address pool type comprises a common class address pool and a private class address pool;
if the address pool corresponding to the DHCP message is a private type address pool, the DHCP message is processed through aggregation transmission equipment corresponding to the DHCP message, and if the address pool corresponding to the DHCP message is a common type address pool, the equipment type of the aggregation transmission equipment corresponding to the DHCP message is determined; the device types include a master device type and a slave device type in a cross device link aggregation group (MLAG);
If the equipment type of the aggregation transmission equipment corresponding to the DHCP message is the main equipment type, the DHCP message is processed through the main equipment in the cross-equipment link aggregation group MLAG, and if the equipment type of the aggregation transmission equipment corresponding to the DHCP message is the standby equipment type, the DHCP message is forwarded to the main equipment through a peer-link interface for processing;
and taking the allocation address table entry corresponding to the main equipment as a common address table entry, and synchronizing the common address table entry to the standby equipment in the cross-equipment link aggregation group MLAG through the main equipment, so as to realize the DHCP table entry synchronization in the MLAG environment.
The embodiments of the present application also provide a nonvolatile computer storage medium storing computer executable instructions configured to:
receiving a DHCP message, and determining an address pool type of an address pool corresponding to the DHCP message and aggregation transmission equipment corresponding to the DHCP message; the address pool type comprises a common class address pool and a private class address pool;
if the address pool corresponding to the DHCP message is a private type address pool, the DHCP message is processed through aggregation transmission equipment corresponding to the DHCP message, and if the address pool corresponding to the DHCP message is a common type address pool, the equipment type of the aggregation transmission equipment corresponding to the DHCP message is determined; the device types include a master device type and a slave device type in a cross device link aggregation group (MLAG);
If the equipment type of the aggregation transmission equipment corresponding to the DHCP message is the main equipment type, the DHCP message is processed through the main equipment in the cross-equipment link aggregation group MLAG, and if the equipment type of the aggregation transmission equipment corresponding to the DHCP message is the standby equipment type, the DHCP message is forwarded to the main equipment through a peer-link interface for processing;
and taking the allocation address table entry corresponding to the main equipment as a common address table entry, and synchronizing the common address table entry to the standby equipment in the cross-equipment link aggregation group MLAG through the main equipment, so as to realize the DHCP table entry synchronization in the MLAG environment.
In the 90 s of the 20 th century, improvements to one technology could clearly be distinguished as improvements in hardware (e.g., improvements to circuit structures such as diodes, transistors, switches, etc.) or software (improvements to the process flow). However, with the development of technology, many improvements of the current method flows can be regarded as direct improvements of hardware circuit structures. Designers almost always obtain corresponding hardware circuit structures by programming improved method flows into hardware circuits. Therefore, an improvement of a method flow cannot be said to be realized by a hardware entity module. For example, a programmable logic device (Programmable Logic Device, PLD) (e.g., field programmable gate array (Field Programmable Gate Array, FPGA)) is an integrated circuit whose logic function is determined by the programming of the device by a user. A designer programs to "integrate" a digital system onto a PLD without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Moreover, nowadays, instead of manually manufacturing integrated circuit chips, such programming is mostly implemented by using "logic compiler" software, which is similar to the software compiler used in program development and writing, and the original code before the compiling is also written in a specific programming language, which is called hardware description language (Hardware Description Language, HDL), but not just one of the hdds, but a plurality of kinds, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), lava, lola, myHDL, PALASM, RHDL (Ruby Hardware Description Language), etc., VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog are currently most commonly used. It will also be apparent to those skilled in the art that a hardware circuit implementing the logic method flow can be readily obtained by merely slightly programming the method flow into an integrated circuit using several of the hardware description languages described above.
The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer readable medium storing computer readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, application specific integrated circuits (Application Specific Integrated Circuit, ASIC), programmable logic controllers, and embedded microcontrollers, examples of which include, but are not limited to, the following microcontrollers: ARC 625D, atmel AT91SAM, microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic of the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller in a pure computer readable program code, it is well possible to implement the same functionality by logically programming the method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers, etc. Such a controller may thus be regarded as a kind of hardware component, and means for performing various functions included therein may also be regarded as structures within the hardware component. Or even means for achieving the various functions may be regarded as either software modules implementing the methods or structures within hardware components.
The system, apparatus, module or unit set forth in the above embodiments may be implemented in particular by a computer chip or entity, or by a product having a certain function. One typical implementation is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
For convenience of description, the above devices are described as being functionally divided into various units, respectively. Of course, the functions of each element may be implemented in one or more software and/or hardware elements when implemented in the present specification.
It will be appreciated by those skilled in the art that the present description may be provided as a method, system, or computer program product. Accordingly, the present specification embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present description embodiments may take the form of a computer program product on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.
The present description is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the specification. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In one typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.
Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises the element.
The description may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
In this specification, each embodiment is described in a progressive manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for apparatus, devices, non-volatile computer storage medium embodiments, the description is relatively simple, as it is substantially similar to method embodiments, with reference to the section of the method embodiments being relevant.
The foregoing describes specific embodiments of the present disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.
The foregoing is merely one or more embodiments of the present description and is not intended to limit the present description. Various modifications and alterations to one or more embodiments of this description will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement, or the like, which is within the spirit and principles of one or more embodiments of the present description, is intended to be included within the scope of the claims of the present description.

Claims (10)

1. A DHCP entry synchronization method based on an MLAG environment, the method comprising:
receiving a DHCP message, and determining an address pool type of an address pool corresponding to the DHCP message and aggregation transmission equipment corresponding to the DHCP message; the address pool type comprises a common class address pool and a private class address pool;
if the address pool corresponding to the DHCP message is a private type address pool, processing the DHCP message through aggregation transmission equipment corresponding to the DHCP message, and if the address pool corresponding to the DHCP message is a common type address pool, determining the equipment type of the aggregation transmission equipment corresponding to the DHCP message; the device types comprise a main device type and a standby device type in a cross-device link aggregation group (MLAG);
if the equipment type of the aggregation transmission equipment corresponding to the DHCP message is a main equipment type, the DHCP message is processed through a main equipment in a cross-equipment link aggregation group (MLAG), and if the equipment type of the aggregation transmission equipment corresponding to the DHCP message is a standby equipment type, the DHCP message is forwarded to the main equipment through a peer-link interface for processing;
and taking the allocation address table entry corresponding to the main equipment as a common address table entry, and synchronizing the common address table entry to the standby equipment in the cross-equipment link aggregation group MLAG through the main equipment so as to realize DHCP table entry synchronization in the MLAG environment.
2. The method for synchronizing DHCP entries based on an MLAG environment according to claim 1, wherein before receiving a DHCP packet and determining an address pool type of an address pool corresponding to the DHCP packet and an aggregation transmission device corresponding to the DHCP packet, the method further comprises:
determining a main device and a standby device in a cross-device link aggregation group (MLAG), and configuring a corresponding address pool for the main device and the standby device in the cross-device link aggregation group (MLAG);
performing consistency check on address pools corresponding to the main equipment and the standby equipment, and obtaining corresponding consistency check results; the consistency check includes at least one or more of: subnet mask check, gateway address check, and DNS server address check;
if the consistency check results are all passed, determining that the types of the address pools corresponding to the main equipment and the standby equipment are common class address pools;
if the consistency check results are not passed, determining that the types of the address pools corresponding to the main equipment and the standby equipment are private type address pools;
and if the consistency check results are abnormal alarms, taking the address pools corresponding to the main equipment and the standby equipment as invalid address pools.
3. The method for synchronizing DHCP entries based on an MLAG environment according to claim 1, wherein said receiving a DHCP packet and determining an address pool type of an address pool corresponding to the DHCP packet and an aggregation transmission device corresponding to the DHCP packet specifically comprises:
receiving a DHCP Discover message of a DHCP client, and associating an address pool and distributing an IP address for the DHCP client based on the DHCP Discover message;
and determining aggregation transmission equipment corresponding to the DHCP message in a cross-equipment link aggregation group (MLAG) and an address pool type corresponding to the DHCP message according to the IP address allocated to the DHCP client and the associated address pool.
4. The method for synchronizing DHCP entries based on an MLAG environment according to claim 1, wherein if the address pool corresponding to the DHCP packet is a private address pool, processing the DHCP packet by the aggregation transmission device corresponding to the DHCP packet specifically includes:
under the condition that the address pool corresponding to the DHCP message is determined to be a private address pool, determining the equipment type of aggregation transmission equipment corresponding to the DHCP message;
if the aggregation transmission equipment corresponding to the DHCP message is of a main equipment type, processing the DHCP message through a main equipment in a cross-equipment link aggregation group (MLAG), and taking an allocation address table entry in the main equipment as a private address table entry of the main equipment;
If the aggregation transmission equipment corresponding to the DHCP message is of a standby equipment type, the DHCP message is processed through the standby equipment in the cross-equipment link aggregation group MLAG, and an allocation address table entry in the standby equipment is used as a private address table entry of the standby equipment.
5. The method for synchronizing DHCP entry based on MLAG environment according to claim 1, wherein if the device type of the aggregation transmission device corresponding to the DHCP packet is a master device type, processing the DHCP packet by a master device in a cross-device link aggregation group MLAG, specifically comprising:
under the condition that the equipment type of the aggregation transmission equipment corresponding to the DHCP message is the main equipment type, distributing an IP address to a DHCP client corresponding to a DHCP Discover message through a main equipment in a cross-equipment link aggregation group (MLAG) and based on the DHCP Offer message;
receiving a DHCP Request message returned by the DHCP client side, and determining an IP address to be requested carried in the DHCP Request message;
and through the DHCP Ack message, the corresponding IP address to be requested is determined to be allocated for the DHCP client.
6. The method for synchronizing DHCP entry based on MLAG environment according to claim 1, wherein if the device type of the aggregation transmission device corresponding to the DHCP packet is a standby device type, forwarding the DHCP packet to the master device through the peer-link interface for processing, specifically comprising:
Under the condition that the equipment type of the aggregation transmission equipment corresponding to the DHCP message is the spare equipment type, forwarding the DHCP message to the main equipment through the spare equipment in the cross-equipment link aggregation group MLAG and based on a peer-link interface between the main equipment and the spare equipment in the cross-equipment link aggregation group MLAG;
and associating an address pool and distributing an IP address for the DHCP client through the master equipment based on the DHCP Offer message so that the DHCP client obtains the corresponding IP address.
7. The method for synchronizing DHCP entries based on an MLAG environment according to claim 1, wherein the step of using the allocated address entry corresponding to the master device as a common address entry and synchronizing the common address entry to a standby device in the cross-device link aggregation group MLAG by the master device, includes:
determining that the DHCP message corresponds to a DHCP client, and taking an allocation address table entry corresponding to the allocation address of the host equipment for the DHCP client as a common address table entry;
and synchronizing the common address table entry to the standby equipment through the main equipment based on a peer-link interface and a TCP protocol between the main equipment and the standby equipment so as to realize DHCP table entry synchronization in an MLAG environment.
8. The method for synchronizing DHCP entries based on an MLAG environment according to claim 1, wherein said synchronizing, by said master device, said common address entry to a standby device in said cross-device link aggregation group MLAG, after implementing DHCP entry synchronization in an MLAG environment, said method further comprises:
determining that the address pool type is a private address pool and the equipment type of the aggregation transmission equipment is a DHCP client of the main equipment type, and releasing the IP address acquired by the corresponding DHCP client through the main equipment;
determining that the address pool type is a private address pool and the equipment type of the aggregation transmission equipment is a DHCP client of the standby equipment type, and releasing an IP address acquired by the DHCP client through the standby equipment;
determining that the address type is a DHCP client side of a common class address pool, and determining that an address Release message corresponds to the equipment type of receiving equipment;
if the equipment type is the main equipment type, processing the address Release message through the main equipment;
if the equipment type is the standby equipment type, forwarding the address Release message to a main equipment through the standby equipment so as to process the address Release message through the main equipment and synchronize the corresponding address table entry to the standby equipment.
9. A DHCP entry synchronization device based on an MLAG environment, the device comprising:
at least one processor;
and a memory communicatively coupled to the at least one processor;
wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to perform a DHCP entry synchronization method based on an MLAG environment as claimed in any one of claims 1 to 8.
10. A non-transitory computer storage medium storing computer-executable instructions, the computer-executable instructions configured to:
a DHCP entry synchronization method based on an MLAG environment as claimed in any one of claims 1 to 8.
CN202310142375.0A 2023-02-17 2023-02-17 DHCP (dynamic host configuration protocol) table entry synchronization method, equipment and medium based on MLAG (media-based access control) environment Active CN116192801B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310142375.0A CN116192801B (en) 2023-02-17 2023-02-17 DHCP (dynamic host configuration protocol) table entry synchronization method, equipment and medium based on MLAG (media-based access control) environment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310142375.0A CN116192801B (en) 2023-02-17 2023-02-17 DHCP (dynamic host configuration protocol) table entry synchronization method, equipment and medium based on MLAG (media-based access control) environment

Publications (2)

Publication Number Publication Date
CN116192801A CN116192801A (en) 2023-05-30
CN116192801B true CN116192801B (en) 2024-03-26

Family

ID=86444104

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310142375.0A Active CN116192801B (en) 2023-02-17 2023-02-17 DHCP (dynamic host configuration protocol) table entry synchronization method, equipment and medium based on MLAG (media-based access control) environment

Country Status (1)

Country Link
CN (1) CN116192801B (en)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1738269A (en) * 2004-08-17 2006-02-22 杭州华为三康技术有限公司 Method to allocate protocol relay address table and server address pool for synchronization dynamic host machine
CN107547678A (en) * 2017-06-21 2018-01-05 新华三技术有限公司 A kind of address distribution method and device
CN115499414A (en) * 2022-08-15 2022-12-20 新华三技术有限公司 Address allocation method and device
CN115567486A (en) * 2022-09-20 2023-01-03 浪潮思科网络科技有限公司 Lease synchronization method, device, equipment and medium in MLAG environment

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140006568A1 (en) * 2012-06-28 2014-01-02 Alcatel-Lucent Canada, Inc. Prioritization based on ip pool and subnet by dhcp
US10375744B2 (en) * 2016-12-06 2019-08-06 At&T Intellectual Property I, L.P. Session continuity between software-defined network-controlled and non-software-defined network-controlled wireless networks

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1738269A (en) * 2004-08-17 2006-02-22 杭州华为三康技术有限公司 Method to allocate protocol relay address table and server address pool for synchronization dynamic host machine
CN107547678A (en) * 2017-06-21 2018-01-05 新华三技术有限公司 A kind of address distribution method and device
CN115499414A (en) * 2022-08-15 2022-12-20 新华三技术有限公司 Address allocation method and device
CN115567486A (en) * 2022-09-20 2023-01-03 浪潮思科网络科技有限公司 Lease synchronization method, device, equipment and medium in MLAG environment

Also Published As

Publication number Publication date
CN116192801A (en) 2023-05-30

Similar Documents

Publication Publication Date Title
CN110704155B (en) Container network construction method and device, physical host and data transmission method
CN113300985B (en) Data processing method, device, equipment and storage medium
CN109376197B (en) Data synchronization method, server and computer storage medium
CN111459724B (en) Node switching method, device, equipment and computer readable storage medium
CN107196772B (en) Method and device for broadcasting message
CN111682927A (en) Message synchronization method, device, equipment and medium based on MLAG environment
CN112104499B (en) Container network model construction method, device, equipment and medium
KR20100099319A (en) Node system, server switching method, server device, and data transfer method
CN111866169B (en) Service updating method, device and system
CN113301174B (en) Data processing and conversion rule deployment method and device
CN105991463B (en) Method, message main node, token server and system for realizing flow control
CN115408468A (en) Data synchronization method and device, readable storage medium and electronic equipment
CN116192801B (en) DHCP (dynamic host configuration protocol) table entry synchronization method, equipment and medium based on MLAG (media-based access control) environment
CN116170289A (en) Node election method and device, storage medium and electronic equipment
CN111930530B (en) Equipment message processing method, device and medium based on Internet of things
CN110502575B (en) Method, device and equipment for data synchronization
CN112698979A (en) Method and device for processing zookeeper double nodes, storage medium and processor
CN116737345A (en) Distributed task processing system, distributed task processing method, distributed task processing device, storage medium and storage device
CN110275782B (en) Data processing method and device
CN116048886A (en) Method and device for performing active-standby switching of block chain nodes
CN114531394B (en) Data synchronization method and device
CN114296869A (en) Server node service method and device based on TCP long connection
CN112346912A (en) Stateful service master and standby high availability system and method based on network file system
CN112583740B (en) Network communication method and device
CN110764690B (en) Distributed storage system and leader node election method and device thereof

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant