Table item synchronization method and device, electronic equipment and computer readable storage medium

Abstract

The invention provides a table item synchronization method and device, electronic equipment and a computer readable storage medium, in an MLAGE-Lite network system, an opposite-end leaf node converts a learned ARP table item into a host route, then the host route is notified to a home-end leaf node through two backbone nodes, and the host route is sent to the home-end leaf node through the two backbone nodes. Therefore, the leaf node of the home terminal can add the routing table item corresponding to the access equipment to the dynamic routing table of the home terminal based on the received two host routes, and converts the host routes into the ARP table item of the access equipment when determining that the VLAN network to which at least one specific link convergence port in the up state belongs and the access equipment belong to the same network segment. Compared with the prior art in which double network cards of a server need to be configured to send ARP messages at regular time, the leaf node at the home terminal can add the routing table item corresponding to the access equipment and realize ARP table item synchronization with the leaf node at the opposite terminal, so that three-layer intercommunication between the leaf node at the home terminal and the access equipment can be realized; and the configuration work during network deployment can be effectively reduced.

Description

Technical Field

[0001] The present invention relates to the field of communications, and in particular to a table entry synchronization method, device, electronic device and computer-readable storage medium. Background Art

[0002] In order to meet the requirements of increased business volume and higher network reliability, the current data center network adopts MLAG (Multi-chassis Link Aggregation Group) virtualization technology, which can improve the reliability of links from the single-board level to the device level by aggregating links between multiple devices.

[0003] See also Figure 1 In M-LAG virtualization technology, different ports on different devices are grouped into an aggregation group to achieve the same function as a common LAG (Link Aggregation Group). The main application scenario is the "dual-homing access" scenario, that is, the user side is dual-homed to two devices. For the downstream device, the upstream device is considered to be one device. In addition, a peer-link is configured between the two upstream devices, so that the two upstream devices can synchronize protocol packets to achieve the purpose of active-active forwarding.

[0004] MLAG-Lite virtualization technology was born because users expect the access layer to achieve device independence, control plane isolation, and device fault isolation, and to be able to perform active-active forwarding processing without affecting each other under the premise of version upgrades. Figure 1 For the M-LAG networking shown in Figure 2 MLAG-Lite networking removes the peer links between devices, which simplifies deployment and saves costs. During the upgrade process, the service is not interrupted. MLAG Lite can ensure the decoupling of the control planes between multiple devices, and there is no need to configure peer links between devices to synchronize protocol messages to achieve the purpose of active-active forwarding.

[0005] See also Figure 3 The typical MLAG-Lite network diagram shown in Figure 3In the example, the same gateway is configured for Server1 and Server2 on the leaf node devices Leaf1 and Leaf2. For servers connected to the Leaf switch in load balancing, ARP packets (reply packets or request packets) are sent to Leaf1 or Leaf2 through HASH routing. Since the peer link between Leaf1 and Leaf2 is removed, assuming that the ARP packet sent by the server is sent to Leaf1 after HASH routing, Leaf2 cannot receive the ARP packet sent by the server. In this case, only Leaf1 can learn the ARP table entry of the server, while Leaf2 cannot learn the ARP table entry of the server, resulting in Leaf2 and the server being unable to communicate at Layer 3.

[0006] The current solution to this problem is to configure the server to periodically send ARP messages to both Leaf1 and Leaf2 through dual network cards so that both Leaf1 and Leaf2 can receive ARP messages and learn the server's ARP table entries. However, some vendors' servers do not support active sending of ARP messages, so the consistency of ARP entries maintained between Leaf1 and Leaf2 cannot be guaranteed. Even if the server supports active sending of ARP messages, by default, the server will not send ARP messages to both servers, so it is necessary to configure the server to allow dual network cards to send ARP messages to both servers. This method adds additional configuration work to the server during network deployment. Summary of the invention

[0007] The object of the present invention is to provide a table entry synchronization method, device, electronic device and computer-readable storage medium to improve the problems existing in the prior art.

[0008] The embodiments of the present invention can be implemented as follows:

[0009] In a first aspect, the present invention provides a table entry synchronization method, which is applied to a local leaf node in an MLAG-Lite network system, wherein the MLAG-Lite network system further includes a peer leaf node, a first backbone node, and a second backbone node, wherein the local leaf node and the peer leaf node are both communicatively connected to the first backbone node and the second backbone node, and the local leaf node and the peer leaf node are commonly connected to at least one access device; the method includes:

[0010] Receiving the host route announced by the opposite leaf node through the first backbone node and the second backbone node respectively; the host route is obtained by the opposite leaf node converting the ARP table entry generated based on the ARP message after receiving the ARP message sent by any of the access devices;

[0011] Based on the received host route, adding a routing table entry corresponding to the access device to the local dynamic routing table;

[0012] If it is confirmed that there is at least one specific link aggregation port in the up state and the VLAN network to which the access device belongs belongs to the same network segment, the host route is converted into an ARP table entry of the access device.

[0013] In an optional implementation manner, the step of adding a routing table entry corresponding to the access device to the local dynamic routing table based on the received host route includes:

[0014] Obtaining the IP address of the access device from the received host route;

[0015] Based on the IP address of the access device, the IP address of the first backbone node that announces the host route or the IP address of the second backbone node, and the packet receiving interface of the host route, a routing table entry corresponding to the access device is added to the local dynamic routing table; wherein the destination address of the routing table entry corresponding to the access device is the IP address of the access device, the next hop is the IP address of the first backbone node or the IP address of the second backbone node, and the outgoing interface is the packet receiving interface of the host route.

[0016] In an optional implementation manner, if it is confirmed that the VLAN network to which at least one specific link aggregation port in an up state belongs belongs to the same network segment as the access device, the step of converting the host route into an ARP table entry of the access device includes:

[0017] Acquire the IP address of the access device based on the host route;

[0018] Find the VLAN network to which the Layer 3 interface IP address that belongs to the same network segment as the IP address of the access device belongs, and find at least one link aggregation port belonging to the VLAN network;

[0019] If there is only one specific link aggregation port in the up state among the at least one link aggregation port, determining that the specific link aggregation port is the target link aggregation port to which the access device that sends the ARP message is connected, and directly converting the host route into an ARP table entry of the access device;

[0020] If there is more than one specific link aggregation port in the up state among the at least one link aggregation port, the target link aggregation port is found by sending ARP unicast detection messages to the devices connected to each of the specific link aggregation ports in turn, and after the target link aggregation port is found, the host route is converted into the ARP table entry of the access device.

[0021] In an optional implementation manner, the step of finding the target link aggregation port by sending ARP unicast detection messages to devices connected to each of the specific link aggregation ports in sequence includes:

[0022] The first specific link aggregation port is used as the current port to be tested, the layer 3 interface IP address of the current port to be tested is used as the source address and the IP address of the access device in the host route is used as the destination address to construct the ARP unicast detection message;

[0023] Sending the ARP unicast detection message to the device under test connected to the current port under test;

[0024] Determine whether an ARP unicast response message returned by the device under test or a dedicated Update message carrying a preset detection mark notified by the opposite leaf node through the first backbone node or the second backbone node is received within a preset detection time; wherein the dedicated Update message is generated after the opposite leaf node receives the ARP unicast response message sent by the device under test;

[0025] If yes, determining that the current port to be tested is the target link aggregation port to which the access device that sends the ARP message is connected;

[0026] If not, the next specific link aggregation port is used as the current port to be tested, and the process returns to execute the step of constructing the ARP unicast detection message with the three-layer interface IP address of the current port to be tested as the source address and the IP address of the access device in the host route as the destination address, until an ARP unicast response message returned by the device to be tested is received within the preset detection time, or a special Update message carrying a preset detection mark is received by the opposite leaf node through the first backbone node or the second backbone node, and the current port to be tested is determined to be the target link aggregation port to which the access device that sent the ARP message is connected.

[0027] In a second aspect, the present invention provides a table entry synchronization method, which is applied to a peer leaf node in an MLAG-Lite network system, wherein the MLAG-Lite network system further includes a local leaf node, a first backbone node, and a second backbone node, wherein the local leaf node and the peer leaf node are both communicatively connected to the first backbone node and the second backbone node, and the local leaf node and the peer leaf node are commonly connected to at least one access device; the method includes:

[0028] When an ARP message sent by any of the access devices is received, an ARP table entry of the access device is generated based on the ARP message;

[0029] The ARP table entry of the access device is converted into a host route, and the host route is notified to the local leaf node through the first backbone node and the second backbone node respectively, so that the local leaf node adds the routing table entry corresponding to the access device to the local dynamic routing table based on the received host route, and when it is confirmed that the VLAN network to which there is at least one specific link aggregation port in the up state belongs belongs to the same network segment as the access device, the host route is converted into the ARP table entry of the access device.

[0030] In an optional implementation, a BGP neighbor relationship is established between the local leaf node and the first backbone node and the second backbone node, and a BGP neighbor relationship is established between the opposite leaf node and the first backbone node and the second backbone node;

[0031] The step of notifying the host route to the local leaf node through the first backbone node and the second backbone node respectively includes:

[0032] The host route is notified to the first backbone node and the second backbone node respectively based on the BGP neighbor relationship, so that the first backbone node and the second backbone node respectively notify the received host route to the local leaf node based on the BGP neighbor relationship.

[0033] In an optional embodiment, the method further comprises:

[0034] When receiving an ARP unicast response message sent by the device under test, finding the ARP table entry of the device under test to generate a dedicated Update message carrying a preset detection tag; the device under test is an access device that sends the ARP message, and the ARP unicast response message is generated by the access device after receiving the ARP unicast detection message sent by the local leaf node;

[0035] Notifying the dedicated Update message to the first backbone node or the second backbone node based on the BGP neighbor relationship, so that the first backbone node or the second backbone node notifies the received dedicated Update message to the local leaf node based on the BGP neighbor relationship;

[0036] Among them, when the local leaf node receives the special Update message within the preset detection time after sending the ARP unicast detection message, it confirms that the current port to be tested connected to the device to be tested is the target link aggregation port; the current port to be tested is any specific link aggregation port found by the local leaf node.

[0037] In a third aspect, the present invention provides a table entry synchronization device, which is applied to a local leaf node in an MLAG-Lite network system, wherein the MLAG-Lite network system further includes a peer leaf node, a first backbone node, and a second backbone node, wherein the local leaf node and the peer leaf node are both communicatively connected to the first backbone node and the second backbone node, and the local leaf node and the peer leaf node are commonly connected to at least one access device; the device includes:

[0038] An announcement receiving module, used for receiving the host route announced by the opposite leaf node through the first backbone node and the second backbone node respectively; the host route is obtained by the opposite leaf node converting the ARP table entry generated based on the ARP message after receiving the ARP message sent by any of the access devices;

[0039] A conversion module is used to add a routing table entry corresponding to the access device to the local dynamic routing table based on the two received host routes; if it is confirmed that the VLAN network to which at least one specific link aggregation port in the up state belongs belongs to the same network segment as the access device, the host route is converted into an ARP table entry of the access device.

[0040] In a fourth aspect, the present invention provides a table entry synchronization device, which is applied to a peer leaf node in an MLAG-Lite network system, wherein the MLAG-Lite network system further includes a local leaf node, a first backbone node, and a second backbone node, wherein the local leaf node and the peer leaf node are both communicatively connected to the first backbone node and the second backbone node, and the local leaf node and the peer leaf node are commonly connected to at least one access device; the device includes:

[0041] An ARP module, configured to generate an ARP table entry of the access device based on the ARP message when an ARP message sent by any of the access devices is received;

[0042] A notification issuing module is used to convert the ARP table entry of the access device into a host route, and to notify the host route to the local leaf node through the first backbone node and the second backbone node respectively, so that the local leaf node can add the routing table entry corresponding to the access device to the local dynamic routing table based on the received host route, and when it is confirmed that the VLAN network to which there is at least one specific link aggregation port in the up state belongs belongs to the same network segment as the access device, the host route is converted into the ARP table entry of the access device.

[0043] In a fifth aspect, the present invention provides an electronic device, comprising: a memory and a processor, wherein the memory stores a software program, and when the electronic device is running, the processor executes the software program to implement the table entry synchronization method as described in the first aspect or the second aspect above.

[0044] In a sixth aspect, the present invention provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the table entry synchronization method described in the first aspect or the second aspect is implemented.

[0045] Compared with the prior art, the embodiments of the present invention provide a table item synchronization method, device, electronic device and computer-readable storage medium. In the MLAG-Lite network system, after receiving the ARP message sent by any access device and learning the ARP table item, the opposite leaf node converts the ARP table item into a host route, and then notifies the host route to the local leaf node through the first backbone node and the second backbone node respectively, so that the local leaf node can add the routing table item corresponding to the access device to the local dynamic routing table based on the two received host routes, and when it is confirmed that the VLAN network to which at least one specific link aggregation port in the up state belongs belongs to the same network segment as the access device, the host route is converted into the ARP table item of the access device. Compared with the prior art that requires the configuration of the server's dual network cards to periodically send two ARP messages, the local leaf node in the present invention can add the routing table item corresponding to the access device based on the two received host routes and realize the synchronization of the ARP table items with the opposite leaf node, so that the local leaf node and the access device can be interconnected at three layers, which can also effectively reduce the configuration work during network deployment. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for use in the embodiments are briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present invention and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without creative work.

[0047] Figure 1 The figure is a schematic diagram of the principle of M-LAG virtualization technology.

[0048] Figure 2 Schematic diagram of the MLAG-Lite virtualization technology.

[0049] Figure 3 A schematic diagram of the structure of a classic MLAG-Lite networking system provided in an embodiment of the present invention.

[0050] Figure 4 One of the flowcharts of a table entry synchronization method provided by an embodiment of the present invention.

[0051] Figure 5 The second flowchart of a table entry synchronization method provided by an embodiment of the present invention.

[0052] Figure 6 The third flowchart of a table entry synchronization method provided by an embodiment of the present invention.

[0053] Figure 7 This is one of the structural schematic diagrams of a table entry synchronization device provided by an embodiment of the present invention.

[0054] Figure 8 The second structural diagram of a table entry synchronization device provided by an embodiment of the present invention.

[0055] Fig. 9 A schematic diagram of the structure of an electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0056] In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Generally, the components of the embodiments of the present invention described and shown in the drawings here can be arranged and designed in various different configurations.

[0057] Therefore, the following detailed description of the embodiments of the present invention provided in the accompanying drawings is not intended to limit the scope of the invention claimed for protection, but merely represents selected embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0058] It should be noted that similar reference numerals and letters denote similar items in the following drawings, and therefore, once an item is defined in one drawing, further definition and explanation thereof is not required in subsequent drawings.

[0059] In addition, the terms “first”, “second”, etc., if used, are merely used to distinguish between the descriptions and should not be understood as indicating or implying relative importance.

[0060] It should be noted that, in the absence of conflict, the features in the embodiments of the present invention may be combined with each other.

[0061] Here, we first introduce an application scenario of the present invention. Figure 3 , Figure 3This is a schematic diagram of the structure of a classic MLAG-Lite network system. The MLAG-Lite network system is based on the Spine-Leaf architecture. The Spine layer is the backbone of the network, including a pair of Spine switches (Spine1 and Spine2), and the Leaf layer includes a pair of Leaf switches (Leaf1 and Leaf2) for accessing servers. The two Leaf switches in the Leaf layer are connected to the two Spine switches in the Spine layer, and the two physical servers (Sever1 and Sever2) are connected to the two Leaf switches using cross-device link aggregation (MLAG-Lite).

[0062] It should be noted that the number of access devices connected to the Leaf layer is not unique. Figure 3 The two access devices Sever1 and Sever2 shown are only examples and are not limited here.

[0063] The local leaf node and the opposite leaf node referred to in the present invention are Figure 3 The two Leaf switches shown in the figure are the first backbone node and the second backbone node. Figure 3 The two Spine switches shown in the figure are access devices that are servers (Sever1, Sever2) accessing the Leaf layer. The following describes in detail the table entry synchronization method provided by the present invention from the perspectives of the local leaf node (assuming Leaf2) and the opposite leaf node (assuming Leaf1).

[0064] First, please refer to Figure 4 , Figure 4 One of the flow diagrams of a table item synchronization method provided in an embodiment of the present invention, the table item synchronization method is applied to the local leaf node (Leaf2) in the MLAG-Lite network system, the MLAG-Lite network system also includes the opposite leaf node (Leaf1), the first backbone node (Spine1) and the second backbone node (Spine2), the local leaf node and the opposite leaf node are both connected to the first backbone node and the second backbone node, and the local leaf node and the opposite leaf node are connected to at least one access device. The table item synchronization method includes the following steps S101 to S103:

[0065] S101: Receive host routes announced by the opposite leaf node through the first backbone node and the second backbone node respectively.

[0066] In this embodiment, the host route is obtained by converting the ARP table entry generated based on the ARP message after the peer leaf node receives the ARP message sent by any access device.

[0067] It can be understood that an access device can send an ARP message to the opposite leaf node after HASH routing. The ARP message can be an ARP request message or an ARP reply message, which is not limited in the embodiment of the present invention. When the opposite leaf node receives the ARP message sent by the access device, it can learn the ARP table entry of the access device (the correspondence between the IP address and MAC address of the access device) based on the ARP message. Since there is no peer link between the local leaf node and the opposite leaf node, the opposite leaf node cannot directly synchronize the ARP table entry of the access device to the local leaf node based on the peer link.

[0068] In the MLAG-Lite network system, the network device turns on the function of converting the host table to the routing table by default, so the opposite leaf node can convert the ARP table entry of the access device into a 32-bit host route, which carries the IP address and MAC address of the access device. Then the opposite leaf node can announce the host route to the local leaf node through the first backbone node and the second backbone node respectively. Therefore, the local leaf node can receive two identical host routes.

[0069] S102: Based on the received host route, a routing table entry corresponding to the access device is added to the local dynamic routing table.

[0070] In this embodiment, for the local leaf node, when receiving the host routes notified by the first backbone node and the second backbone node respectively, a new routing table entry with the access device as the destination address can be added to the local dynamic routing table maintained by itself. The routing table entry can be used to indicate the path for the local leaf node to perform three-layer forwarding on the network traffic that needs to reach the access device.

[0071] S103: If it is confirmed that the VLAN (Virtual Local Area Network) network to which at least one specific link aggregation port in the up state belongs belongs to the same network segment as the access device, convert the host route into an ARP table entry of the access device.

[0072] In this embodiment, the local leaf node also needs to determine that the target link aggregation port of the access device is in the up state when accessing, which means that there is no port failure in the target link aggregation port corresponding to the access device, and the local leaf node can interact normally with the access device, and then convert the host route into the ARP table entry of the access device. In this way, the local leaf node not only stores the routing table entry corresponding to the access device, but also synchronizes the ARP table entry of the access device from the opposite leaf node. Subsequently, the local leaf node can perform three-layer forwarding on the network traffic to the access device.

[0073] The table entry synchronization method provided by the embodiment of the present invention can form a routing table entry corresponding to the access device based on the two host routes announced by the opposite leaf node, and synchronously learn the ARP table entry of the access device, so as to realize the three-layer intercommunication between the local leaf node and the access device. Since it is not necessary to configure the dual network cards of the server to periodically send dual ARP messages to realize ARP table entry synchronization as in the prior art, the configuration work during network deployment is effectively reduced. In the optional implementation method, the sub-steps of the above step S102 may include S1021~S1022:

[0074] S1021. Obtain an IP address of the access device from the received host route;

[0075] S1022: Based on the IP address of the access device, the IP address of the first backbone node that announces the host route or the IP address of the second backbone node, and the packet receiving interface of the host route, a routing table entry corresponding to the access device is added to the local dynamic routing table.

[0076] In this embodiment, in the routing table entry corresponding to the access device: the destination address can be the IP address of the access device, the next hop can be the IP address of the first backbone node or the IP address of the second backbone node, and the outgoing interface can be the packet receiving interface of the host route (since the local leaf node can receive two host routes, there are also two outgoing interfaces).

[0077] It should be noted that the routing table entry corresponding to the newly added access device may also include other information, such as hop count (Metric), flag information (Flags), etc.

[0078] In an optional implementation, the prerequisite for the local leaf node to convert the host route into the ARP table entry of the access device is that it is necessary to find the target link aggregation port to which the access device that sends the ARP message is connected, and the target link aggregation port is in the up state. Correspondingly, the sub-steps of the above step S103 may include S1031 to S1034:

[0079] S1031. Obtain an IP address of the access device based on the host route.

[0080] S1032. Find the VLAN network to which the Layer 3 interface IP address that belongs to the same network segment as the IP address of the access device belongs, and find out at least one link aggregation port that belongs to the VLAN network.

[0081] In this embodiment, the local leaf node can maintain the Layer 3 interface IP address of each link aggregation port and the VLAN network to which it belongs. The local leaf node can first check whether there is a Layer 3 interface IP address that belongs to the same network segment as the IP address of the access device. If so, the VLAN network to which the access device belongs can be determined, and then the local leaf node can find at least one link aggregation port belonging to the VLAN network.

[0082] S1033: If there is only one specific link aggregation port in the up state among the at least one link aggregation port, determine that the specific link aggregation port is the target link aggregation port to which the access device that sends the ARP message is connected, and directly convert the host route into an ARP table entry of the access device.

[0083] In this embodiment, if there is only one specific link aggregation port in the up state among the at least one link aggregation port found by the leaf node on this end, the specific link aggregation port in the up state is the target link aggregation port corresponding to the access device that sends the ARP message, and the host route can be directly converted into the ARP table entry of the access device.

[0084] S1034. If there is more than one specific link aggregation port in the up state among at least one link aggregation port, the target link aggregation port is found by sending ARP unicast detection messages to the devices connected to each specific link aggregation port in turn, and after the target link aggregation port is found, the host route is converted into the ARP table entry of the access device.

[0085] In this embodiment, if there is more than one specific link aggregation port in the up state among at least one link aggregation port found by the local leaf node, then the local leaf node needs to use ARP unicast detection message to detect each specific link aggregation port in turn to find the target link aggregation port before converting the host route into the ARP table entry of the access device.

[0086] Optionally, when detecting a specific link aggregation port A, the source address of the ARP unicast detection message is the three-layer interface IP address of the specific link aggregation port, and the destination address is the IP address of the access device in the host router. When the device connected to the specific link aggregation port A receives the ARP unicast detection message, it checks whether the destination address of the ARP unicast detection message is consistent with its own IP address. If they are consistent, it sends an ARP unicast response message to the local leaf node or the opposite leaf node through HASH routing; if they are inconsistent, the device connected to the specific link aggregation port A will not respond.

[0087] Correspondingly, see Figure 5In step S1034, the process of finding the target link aggregation port by sending ARP unicast detection messages to the devices connected to each specific link aggregation port in turn may include the following sub-steps S10341 to S10345:

[0088] S10341. Use the first specific link aggregation port as the current port to be tested.

[0089] S10342: Construct an ARP unicast detection message with the layer 3 interface IP address of the current port to be tested as the source address and the IP address of the access device in the host route as the destination address.

[0090] S10343. Send an ARP unicast detection message to the device under test connected to the current port under test.

[0091] S10344: Determine whether an ARP unicast response message returned by the device under test or a dedicated Update message carrying a preset detection mark notified by the opposite leaf node through the first backbone node or the second backbone node is received within a preset detection time.

[0092] In this embodiment, the dedicated Update message can be generated after the opposite leaf node receives the ARP unicast response message sent by the device under test. In the MLAG-Lite network system, a BGP (Border Gateway Protocol) neighbor relationship is established between the local leaf node and the first backbone node and the second backbone node, and a BGP neighbor relationship is established between the opposite leaf node and the first backbone node and the second backbone node. Therefore, the opposite leaf node can notify the dedicated Update message to the local leaf node through the first backbone node or the second backbone node based on the BGP neighbor relationship.

[0093] Among them, the BGP protocol specifies five types of BGP messages:

[0094] 1. Open message: used to establish neighbor relationship;

[0095] 2. Keepalive message: This message is sent periodically between peers (two parties that establish a neighbor relationship are called peers) to maintain the BGP connection;

[0096] 3. Update message: used to transmit routing information between BGP peers;

[0097] 4. Notification message: When BGPSpeaker detects an error, it sends this message to the peer;

[0098] 5. Route-refresh message: used to notify the peer that it supports route refresh capability; used to request the peer to resend routing information after changing the routing policy. Only BGP devices that support route refresh capability will send and respond to this message.

[0099] Optionally, the dedicated Update message may be an Update message specified by the BGP protocol, and a specific field of the dedicated Update message carries a preset detection tag.

[0100] It can be understood that after receiving the ARP unicast detection message, the device under test will check whether the destination address of the ARP unicast detection message is consistent with its own IP address. If they are consistent, it means that the device under test is the access device that sends the ARP message to the opposite leaf node. At this time, the device under test needs to respond with an ARP unicast response message (the destination address is the source address of the ARP unicast detection message, that is, the three-layer interface IP address of the current port under test). The device under test determines the recipient of the ARP unicast response message through HASH routing. For the local leaf node, the information received within the preset detection time may be in the following two situations:

[0101] (1) Receiving an ARP unicast response message: the device under test directly hashes the ARP unicast response message to the local leaf node. As long as the local leaf node receives the ARP unicast response message within the preset detection time, it can be determined that the current port under test corresponding to the device under test is the target link aggregation port to which the access device that sent the ARP message is connected;

[0102] (2) Receiving a dedicated Update message: the device under test directly hashes the ARP unicast response message to the opposite leaf node. At this time, the opposite leaf node checks that the destination address of the received ARP unicast response message is not its own layer-3 interface IP address, and then generates a dedicated Update message carrying a preset detection tag. Then, based on the BGP neighbor relationship, the dedicated Update message is notified to the local leaf node through the first backbone node or the second backbone node.

[0103] Optionally, the dedicated Update message carries a preset detection tag to distinguish it from a general Update message. In addition, the dedicated Update message may also include the IP address and MAC address of the device under test, which are obtained by the peer leaf node from the ARP table entry of the device under test.

[0104] Therefore, as long as the leaf node on this end receives a special Update message carrying a preset detection mark within the preset detection time, and determines that the IP address and MAC address of the device under test carried in the special Update message are the same as the IP address and MAC address in the host route, it can be determined that the current port under test corresponding to the device under test is the target link aggregation port to which the access device that sends the ARP message is connected.

[0105] Therefore, if the judgment result of step S10344 is yes, directly execute step S10345; if the judgment result of step S10344 is no, then it is necessary to continue to detect the next specific link aggregation port, execute the following step S10346 and then return to execute the above step S10342 until the judgment result of step S10344 is yes (that is, the leaf node at this end receives the ARP unicast response message returned by the device to be tested within the preset detection time or the special Update message carrying the preset detection mark notified by the leaf node at the other end through the first backbone node or the second backbone node), then execute step S10345.

[0106] S10345: Determine that the current port to be tested is the target link aggregation port to which the access device that sends the ARP message is connected.

[0107] S10346. Use the next specific link aggregation port as the current port to be tested.

[0108] For optional examples, see Figure 3 , the local leaf node is Leaf2. Assuming that the access device that sends the ARP message to the peer leaf node Leaf1 is Sever2, the local leaf node finds the specific link aggregation ports Gi 0 / 1 and Gi 0 / 2. Then, detection needs to be performed in sequence:

[0109] (1) Detect Gi 0 / 1: construct an ARP unicast detection message with the Layer 3 interface IP address of Gi 0 / 1 as the source address and the IP address of Sever2 as the destination address, and then send the ARP unicast detection message to the current device under test Sever1 through Gi 0 / 1. Sever1 checks that the destination address of the received ARP unicast detection message is inconsistent with its own IP address and does not respond. At this time, if the local leaf node Leaf2 does not receive a response (ARP unicast detection message or dedicated Update message) from the device under test within the preset detection time, it will continue to detect Gi 0 / 2;

[0110] (2) Probe Gi 0 / 2: Construct an ARP unicast probe message with the Layer 3 interface IP address of Gi 0 / 2 as the source address and the IP address of Sever2 as the destination address, and then send the ARP unicast probe message to the current device under test Sever2 through Gi 0 / 2. Sever2 checks that the destination address of the received ARP unicast probe message is consistent with its own IP address and needs to respond (HASH sends an ARP unicast response message to the local leaf node or the opposite leaf node). At this time, the local leaf node Leaf2 can receive the response (ARP unicast response message or dedicated Update message) from the device under test within the preset detection time, and then determines that Gi 0 / 2 is the target link aggregation port to which the access device that sent the ARP message is connected.

[0111] The above examples are merely illustrative and are not intended to be limiting.

[0112] It should be noted that the preset detection time length can be flexibly set according to actual application conditions. For example, the preset detection time length can be 0.02s or 0.1s, etc. This example is only an example and the embodiment of the present invention is not limited to this.

[0113] The above-mentioned embodiment of the table entry synchronization method is mainly based on the local leaf node, and introduces the table entry synchronization process between the opposite end leaf node and the local leaf node.

[0114] In combination with the above content, the following mainly introduces the table item synchronization process between the opposite end leaf node and the local end leaf node. It should be noted that its basic principle and the technical effect produced are the same or similar to the above embodiment. For the sake of brief description, the parts not mentioned in this embodiment can refer to the corresponding content in the above embodiment.

[0115] See also Figure 6 , Figure 6 A flowchart of a table item synchronization method provided in an embodiment of the present invention is provided. The table item synchronization method is applied to a peer leaf node (Leaf1) in an MLAG-Lite network system. The MLAG-Lite network system also includes a local leaf node (Leaf2), a first backbone node (Spine1) and a second backbone node (Spine2). Both the local leaf node and the peer leaf node are connected to the first backbone node and the second backbone node in communication. The local leaf node and the peer leaf node are connected to at least one access device. The table item synchronization method may include the following steps S2101 to S202:

[0116] S201. When an ARP message sent by any access device is received, an ARP table entry of the access device is generated based on the ARP message.

[0117] In this embodiment, for any access device, an ARP message can be sent to the opposite leaf node after HASH routing, so that the opposite leaf node can directly learn the ARP table entry of the access device based on the ARP message.

[0118] S202. Convert the ARP table entry of the access device into a host route, and notify the host route to the local leaf node through the first backbone node and the second backbone node respectively, so that the local leaf node adds the routing table entry corresponding to the access device to the local dynamic routing table based on the received host route, and converts the host route into the ARP table entry of the access device when it is confirmed that the VLAN network to which at least one specific link aggregation port in the up state belongs belongs to the same network segment as the access device.

[0119] It can be understood that in the MLAG-Lite network system, the network device turns on the function of converting the host table to the routing table by default, so the opposite leaf node can convert the learned ARP table entry of the access device into a 32-bit host route, which carries the IP address and MAC address of the access device. Then the opposite leaf node can respectively notify the host route to the local leaf node through the first backbone node and the second backbone node, so that the local leaf node can also learn the ARP table entry of the access device based on the two received host routes.

[0120] According to the table entry synchronization method provided by the embodiment of the present invention, the opposite leaf node learns the ARP table entry of the access device based on the ARP message received from the access device, and then converts the ARP table entry of the access device into a host route, and notifies the host route to the local leaf node through the first backbone node and the second backbone node respectively, so that the local leaf node can form the routing table entry corresponding to the access device based on the two identical host routes notified by the opposite leaf node, and synchronously learn the ARP table entry of the access device, so as to realize the three-layer intercommunication between the local leaf node and the access device. Since there is no need to configure the dual network cards of the server to periodically send dual ARP messages as in the prior art to realize ARP table entry synchronization, the configuration work during network deployment is effectively reduced.

[0121] In an optional implementation, in the MLAG-Lite network system, a BGP neighbor relationship is established between the local leaf node and the first backbone node and the second backbone node, and a BGP neighbor relationship is established between the opposite leaf node and the first backbone node and the second backbone node. Correspondingly, the process of announcing the host route to the local leaf node through the first backbone node and the second backbone node in the above step S202 can include the following sub-step S2021:

[0122] S2021. Notify the host route to the first backbone node and the second backbone node respectively based on the BGP neighbor relationship, so that the first backbone node and the second backbone node respectively notify the received host route to the local leaf node based on the BGP neighbor relationship.

[0123] In an optional implementation, since the local leaf node needs to detect each specific link aggregation port found in the process of learning table entries based on the two received host routes, when detecting the current port to be tested (any specific link aggregation port found by the local leaf node), the local leaf node sends the generated ARP unicast detection message to the device to be tested corresponding to the current port to be tested. If the device to be tested finds that the destination address of the received ARP unicast detection message is consistent with its own IP address, it will respond. If the ARP unicast response message responded after HASH routing is sent to the opposite leaf node, then after the process of notifying the host route to the local leaf node through the first backbone node and the second backbone node in the above step S202, the opposite leaf node can also perform the following steps S203 to S204:

[0124] S203: When an ARP unicast response message sent by the device under test is received, an ARP table entry of the device under test is searched to generate a dedicated Update message.

[0125] In this embodiment, the device under test is an access device that sends an ARP message to the opposite leaf node, and the ARP unicast response message is generated by the access device after receiving the ARP unicast detection message sent by the local leaf node. Therefore, the opposite leaf node can find the ARP table entry of the device under test, that is, the ARP table entry learned when executing the above step S201, and then generate a dedicated Update message carrying a preset detection tag based on the ARP table entry of the device under test.

[0126] Optionally, the dedicated Update message carries a preset detection tag to distinguish it from a general Update message. In addition, the dedicated Update message may also include the IP address and MAC address of the device under test, which are obtained by the peer leaf node from the ARP table entry of the device under test.

[0127] S204: Notify the dedicated Update message to the first backbone node or the second backbone node based on the BGP neighbor relationship, so that the first backbone node or the second backbone node notifies the received dedicated Update message to the local leaf node based on the BGP neighbor relationship.

[0128] In this embodiment, the opposite leaf node can use the HASH routing method to notify the dedicated Update message to the local leaf node through the first backbone node or the second backbone node based on the BGP neighbor relationship.

[0129] Therefore, when the local leaf node receives a dedicated Update message within the preset detection time after sending the ARP unicast detection message, and determines that the IP address and MAC address of the device under test carried in the dedicated Update message are the same as the IP address and MAC address in the host route, it can be confirmed that the current port under test to which the device under test is connected is the target link aggregation port, that is, the access device that sends the ARP message is connected to the link aggregation port of the local leaf node.

[0130] It should be noted that in the above two method embodiments, the leaf nodes of the local end and the leaf nodes of the opposite end are respectively Figure 3 The leaf nodes of the local end and the leaf nodes of the opposite end are described as Leaf2 and Leaf1, and it can be understood that the leaf nodes of the local end and the leaf nodes of the opposite end are only a relative description, and the leaf nodes of the local end and the leaf nodes of the opposite end can also be Figure 3 The principle of table entry synchronization for Leaf1 and Leaf2 shown in the figure is consistent with the above process and will not be described in detail here.

[0131] It should be noted that the execution order of each step in the above method embodiment is not limited to that shown in the drawings, and the execution order of each step shall be based on the actual application situation.

[0132] Compared with the prior art, the embodiments of the present invention have the following beneficial effects:

[0133] The present invention does not need to configure the server to perform dual-network card dual-sending ARP messages. After the opposite leaf node learns the ARP table entry of the access device based on the ARP message of the access device received, it needs to convert the ARP table entry of the access device into a host route, and announce the host route to the local leaf node through the first backbone node and the second backbone node respectively. In this way, the local leaf node can form a routing table entry corresponding to the access device based on the two identical host routes announced by the opposite leaf node, and synchronously learn the ARP table entry of the access device, so as to realize the three-layer intercommunication between the local leaf node and the access device. Since there is no need to configure the server's dual network cards to periodically send ARP messages to realize ARP table entry synchronization as in the prior art, the server configuration work during network deployment is effectively reduced, making service deployment more convenient and simple.

[0134] In the prior art, MLAG-Lite needs to use a server with multiple network ports to connect to two Leaf switches in order to configure the server to send dual ARP messages through dual network ports. All prior art must also use the server as an access device for R&D testing. Since server resources are expensive, the testing cost of the prior art in the R&D testing stage of MLAG-Lite is also high. In the present invention, in addition to using the server as an access device for testing during the R&D testing stage, other communication devices (such as personal notebook computers) can also be used as access devices for testing, which can significantly reduce the cost of testing MLAG-Lite.

[0135] In order to execute the corresponding steps in the above method embodiment and each possible implementation mode, two implementation modes of the table entry synchronization device respectively applied to the local leaf node and the opposite leaf node are given below.

[0136] See also Figure 7 , Figure 7 One of the structural schematic diagrams of the table item synchronization device provided by an embodiment of the present invention is shown. The table item synchronization device 200 is applied to the local leaf node in the MLAG-Lite network system. The MLAG-Lite network system also includes the opposite leaf node, the first backbone node and the second backbone node. The local leaf node and the opposite leaf node are both communicatively connected to the first backbone node and the second backbone node. The local leaf node and the opposite leaf node are commonly connected to at least one access device. The table item synchronization device 200 includes: a notification receiving module 210 and a conversion module 220.

[0137] The notification receiving module 210 is used to receive the host route notified by the opposite leaf node through the first backbone node and the second backbone node respectively; the host route is obtained by the opposite leaf node converting the ARP table entry generated based on the ARP message after receiving the ARP message sent by any access device;

[0138] The conversion module 220 is used to add a routing table entry corresponding to the access device to the local dynamic routing table based on the received host route; if it is confirmed that the VLAN network to which at least one specific link aggregation port in the up state belongs belongs to the same network segment as the access device, the host route is converted into an ARP table entry of the access device.

[0139] See also Figure 8 , Figure 8The second structural schematic diagram of the table entry synchronization device provided by an embodiment of the present invention is shown. The table entry synchronization device 400 is applied to the opposite leaf node in the MLAG-Lite network system. The MLAG-Lite network system also includes a local leaf node, a first backbone node and a second backbone node. The local leaf node and the opposite leaf node are both communicatively connected to the first backbone node and the second backbone node. The local leaf node and the opposite leaf node are commonly connected to at least one access device. The table entry synchronization device 400 may include an ARP module 410 and a notification issuing module 420.

[0140] The ARP module 410 is used to generate an ARP table entry of the access device based on the ARP message when receiving an ARP message sent by any access device;

[0141] The notification sending module 420 is used to convert the ARP table entry of the access device into a host route, and to notify the host route to the local leaf node through the first backbone node and the second backbone node respectively, so that the local leaf node can add the routing table entry corresponding to the access device to the local dynamic routing table based on the received host route, and convert the host route into the ARP table entry of the access device when it is confirmed that the VLAN network to which at least one specific link aggregation port in the up state belongs belongs to the same network segment as the access device.

[0142] Those skilled in the art can clearly understand that the notification receiving module 210 can be used to implement the above step S101, the conversion module 220 can be used to implement the above steps S102, S103 and their respective sub-steps, the ARP module 410 can be used to implement the above step S201, and the notification issuing module 420 can be used to implement the above steps S202, S203 and S204. For the convenience and simplicity of description, the specific working process of the table entry synchronization device 200 and the table entry synchronization device 400 described above can refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here.

[0143] See also Fig. 9 , Fig. 9 The electronic device 300 includes a processor 310 , a memory 320 , and a bus 330 , wherein the processor 310 is connected to the memory 320 via the bus 330 .

[0144] The memory 320 may be used to store software programs, for example, software programs corresponding to the table entry synchronization device 200 or the table entry synchronization device 400 provided in the embodiment of the present invention. The processor 310 executes various functional applications and data processing to implement the table entry synchronization method provided in the embodiment of the present invention by running the software programs stored in the memory 320.

[0145] Among them, the memory 320 can be but is not limited to: RAM (Random Access Memory), ROM (Read Only Memory), FLASH (Flash Memory), PROM (Programmable Read-Only Memory), EPROM (Erasable Programmable Read-Only Memory), EEPROM (Electric Erasable Programmable Read-Only Memory), etc.

[0146] The processor 310 may be an integrated circuit chip with signal processing capability. The processor 310 may be a general-purpose processor, including: CPU (Central Processing Unit), NP (Network Processor), etc.; it may also be: DSP (Digital Signal Processing), ASIC (Application Specific Integrated Circuit), FPGA (Field-Programmable Gate Array) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.

[0147] Understandably, Fig. 9 The structure shown is for illustration only. The electronic device 300 may also include Fig. 9 More or fewer components as shown, or with Fig. 9 Different configurations are shown. Fig. 9 Each component shown in the figure can be implemented by hardware, software or a combination thereof.

[0148] The embodiment of the present invention also provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the table entry synchronization method disclosed in the above embodiment is implemented. The computer-readable storage medium can be, but is not limited to, various media that can store program codes, such as a USB flash drive, a mobile hard disk, a ROM, a RAM, a PROM, an EPROM, an EEPROM, a FLASH disk, or an optical disk.

[0149] In summary, the embodiments of the present invention provide a table item synchronization method, device, electronic device and computer-readable storage medium. In the MLAG-Lite network system, after receiving the ARP message sent by any access device and learning the ARP table item, the opposite leaf node converts the ARP table item into a host route, and then notifies the host route to the local leaf node through the first backbone node and the second backbone node respectively, so that the local leaf node can add a routing table item corresponding to the access device to the local dynamic routing table based on the two received host routes, and when it is confirmed that the VLAN network to which at least one specific link aggregation port in the up state belongs belongs to the same network segment as the access device, the host route is converted into the ARP table item of the access device. Compared with the prior art that requires the configuration of the server's dual network cards to periodically send two ARP messages, the local leaf node in the present invention can add a routing table item corresponding to the access device based on the two received host routes and realize the synchronization of the ARP table items with the opposite leaf node, so that the local leaf node and the access device can communicate at three layers, which can also effectively reduce the configuration work during network deployment.

[0150] The above are only specific embodiments of the present invention, but the protection scope of the present invention is not limited thereto. Any changes or substitutions that can be easily thought of by a person skilled in the art within the technical scope disclosed by the present invention should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims

1. A table entry synchronization method, characterized in that: A local leaf node applied to an MLAG-Lite network system, wherein the MLAG-Lite network system further comprises a peer leaf node, a first backbone node, and a second backbone node, wherein both the local leaf node and the peer leaf node are communicatively connected to the first backbone node and the second backbone node, and the local leaf node and the peer leaf node are commonly connected to at least one access device; the method comprises: Receiving the host route announced by the opposite leaf node through the first backbone node and the second backbone node respectively; the host route is obtained by the opposite leaf node converting the ARP table entry generated based on the ARP message after receiving the ARP message sent by any of the access devices; Based on the received host route, adding a routing table entry corresponding to the access device to the local dynamic routing table; If it is confirmed that there is at least one specific link aggregation port in the up state and the VLAN network to which the access device belongs belongs to the same network segment, the host route is converted into an ARP table entry of the access device.

2. The method according to claim 1, characterized in that The step of adding a routing table entry corresponding to the access device to the local dynamic routing table based on the received host route includes: Obtaining the IP address of the access device from the received host route; Based on the IP address of the access device, the IP address of the first backbone node or the IP address of the second backbone node that announces the host route, and the packet receiving interface of the host route, a routing table entry corresponding to the access device is added to the local dynamic routing table; wherein the destination address of the routing table entry corresponding to the access device is the IP address of the access device, the next hop is the IP address of the first backbone node or the IP address of the second backbone node, and the outgoing interface is the packet receiving interface of the host route.

3. The method according to claim 1, characterized in that If it is confirmed that the VLAN network to which at least one specific link aggregation port in the up state belongs belongs to the same network segment as the access device, the step of converting the host route into an ARP table entry of the access device comprises: Acquire the IP address of the access device based on the host route; Find the VLAN network to which the Layer 3 interface IP address that belongs to the same network segment as the IP address of the access device belongs, and find at least one link aggregation port belonging to the VLAN network; If there is only one specific link aggregation port in the up state among the at least one link aggregation port, determining that the specific link aggregation port is the target link aggregation port to which the access device that sends the ARP message is connected, and directly converting the host route into an ARP table entry of the access device; If there is more than one specific link aggregation port in the up state among the at least one link aggregation port, the target link aggregation port is found by sending ARP unicast detection messages to the devices connected to each of the specific link aggregation ports in turn, and after the target link aggregation port is found, the host route is converted into the ARP table entry of the access device.

4. The method according to claim 3, characterized in that The step of finding the target link aggregation port by sending ARP unicast detection messages to the devices connected to each of the specific link aggregation ports in sequence includes: The first specific link aggregation port is used as the current port to be tested, the layer 3 interface IP address of the current port to be tested is used as the source address and the IP address of the access device in the host route is used as the destination address to construct the ARP unicast detection message; Sending the ARP unicast detection message to the device under test connected to the current port under test; Determine whether an ARP unicast response message returned by the device under test or a dedicated Update message carrying a preset detection mark notified by the opposite leaf node through the first backbone node or the second backbone node is received within a preset detection time; wherein the dedicated Update message is generated after the opposite leaf node receives the ARP unicast response message sent by the device under test; If yes, determining that the current port to be tested is the target link aggregation port to which the access device that sends the ARP message is connected; If not, the next specific link aggregation port is used as the current port to be tested, and the process returns to execute the step of constructing the ARP unicast detection message with the three-layer interface IP address of the current port to be tested as the source address and the IP address of the access device in the host route as the destination address, until an ARP unicast response message returned by the device to be tested is received within the preset detection time, or a special Update message carrying a preset detection mark is received by the opposite leaf node through the first backbone node or the second backbone node, and the current port to be tested is determined to be the target link aggregation port to which the access device that sent the ARP message is connected.

5. A table entry synchronization method, characterized in that: The method is applied to a peer leaf node in an MLAG-Lite network system, wherein the MLAG-Lite network system further includes a local leaf node, a first backbone node, and a second backbone node, wherein both the local leaf node and the peer leaf node are communicatively connected to the first backbone node and the second backbone node, and the local leaf node and the peer leaf node are commonly connected to at least one access device; the method includes: When an ARP message sent by any of the access devices is received, an ARP table entry of the access device is generated based on the ARP message; The ARP table entry of the access device is converted into a host route, and the host route is notified to the local leaf node through the first backbone node and the second backbone node respectively, so that the local leaf node adds the routing table entry corresponding to the access device to the local dynamic routing table based on the received host route, and when it is confirmed that the VLAN network to which there is at least one specific link aggregation port in the up state belongs belongs to the same network segment as the access device, the host route is converted into the ARP table entry of the access device.

6. The method according to claim 5, characterized in that A BGP neighbor relationship is established between the local leaf node and the first backbone node and the second backbone node, and a BGP neighbor relationship is established between the opposite leaf node and the first backbone node and the second backbone node; The step of notifying the host route to the local leaf node through the first backbone node and the second backbone node respectively includes: The host route is notified to the first backbone node and the second backbone node respectively based on the BGP neighbor relationship, so that the first backbone node and the second backbone node respectively notify the received host route to the local leaf node based on the BGP neighbor relationship.

7. The method according to claim 6, characterized in that The method further comprises: When receiving an ARP unicast response message sent by the device under test, finding the ARP table entry of the device under test to generate a dedicated Update message carrying a preset detection tag; the device under test is an access device that sends the ARP message, and the ARP unicast response message is generated by the access device after receiving the ARP unicast detection message sent by the local leaf node; Notifying the dedicated Update message to the first backbone node or the second backbone node based on the BGP neighbor relationship, so that the first backbone node or the second backbone node notifies the received dedicated Update message to the local leaf node based on the BGP neighbor relationship; Among them, when the local leaf node receives the special Update message within the preset detection time after sending the ARP unicast detection message, it confirms that the current port to be tested connected to the device to be tested is the target link aggregation port; the current port to be tested is any specific link aggregation port found by the local leaf node.

8. A table entry synchronization device, characterized in that: A local leaf node applied to an MLAG-Lite network system, wherein the MLAG-Lite network system further comprises a peer leaf node, a first backbone node, and a second backbone node, wherein both the local leaf node and the peer leaf node are communicatively connected to the first backbone node and the second backbone node, and the local leaf node and the peer leaf node are commonly connected to at least one access device; the device comprises: An announcement receiving module, used for receiving the host route announced by the opposite leaf node through the first backbone node and the second backbone node respectively; the host route is obtained by the opposite leaf node converting the ARP table entry generated based on the ARP message after receiving the ARP message sent by any of the access devices; A conversion module is used to add a routing table entry corresponding to the access device to the local dynamic routing table based on the two received host routes; if it is confirmed that the VLAN network to which at least one specific link aggregation port in the up state belongs belongs to the same network segment as the access device, the host route is converted into an ARP table entry of the access device.

9. A table entry synchronization device, characterized in that: The device is applied to a peer leaf node in an MLAG-Lite network system, wherein the MLAG-Lite network system further includes a local leaf node, a first backbone node, and a second backbone node, wherein both the local leaf node and the peer leaf node are communicatively connected to the first backbone node and the second backbone node, and the local leaf node and the peer leaf node are commonly connected to at least one access device; the device includes: An ARP module, configured to generate an ARP table entry of the access device based on the ARP message when an ARP message sent by any of the access devices is received; A notification issuing module is used to convert the ARP table entry of the access device into a host route, and to notify the host route to the local leaf node through the first backbone node and the second backbone node respectively, so that the local leaf node can add the routing table entry corresponding to the access device to the local dynamic routing table based on the received host route, and when it is confirmed that the VLAN network to which there is at least one specific link aggregation port in the up state belongs belongs to the same network segment as the access device, the host route is converted into the ARP table entry of the access device.

10. An electronic device, characterized in that: include: A memory and a processor, wherein the memory stores a software program, and when the electronic device is running, the processor executes the software program to implement the table entry synchronization method as described in any one of claims 1-4 or 5-7.

11. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the table entry synchronization method described in any one of claims 1-4 or 5-7 is implemented.

Images