CN112367254A

CN112367254A - Cross-device link aggregation method and device and electronic device

Info

Publication number: CN112367254A
Application number: CN202011197313.2A
Authority: CN
Inventors: 熊定山
Original assignee: Hangzhou H3C Technologies Co Ltd
Current assignee: New H3C Information Technologies Co Ltd
Priority date: 2020-10-30
Filing date: 2020-10-30
Publication date: 2021-02-12
Anticipated expiration: 2040-10-30
Also published as: CN112367254B

Abstract

The application provides a cross-device link aggregation method, a cross-device link aggregation device and an electronic device. In this application, when any member device in the cross-device aggregation receives an ARP/ND request or a response message through a member port in the cross-device aggregation gate AGG, it learns a corresponding forwarding table entry, such as an ARP/ND table entry (an outgoing interface in the forwarding table entry is AGG), and sends the received ARP/ND request or response message and an identifier of the cross-device aggregation gate AGG to other member devices in the cross-device aggregation through a forwarding path of an existing network (i.e., a port connected to other member devices in the cross-device aggregation), so as to synchronously forward the table entry, such as the ARP/ND table entry, between the member devices in the cross-device aggregation. The method solves the problem that the member equipment of the cross-equipment aggregation can not learn the ARP/ND table entry, and realizes the synchronization of the forwarding table entries among the member equipment in the cross-equipment aggregation.

Description

Cross-device link aggregation method and device and electronic device

Technical Field

The present application relates to network communication technologies, and in particular, to a cross-device link aggregation method, an apparatus, and an electronic device.

Background

Cross-device Aggregation refers to aggregating ports (ports) on at least two independently operating network devices into one cross-device Aggregation Interface (AGG). The member ports in the cross-device aggregation port are mutually backed up, and load sharing can also be carried out.

In the networking shown in fig. 1, a Port1 of Device C connected to Device a and a Port2 of Device C connected to Device B are aggregated into an AGG, and

ports

1 and 2 are member ports in the AGG. In the networking shown in fig. 1, Device a and Device B form load sharing through a cross-Device aggregation link (or a cross-Device aggregation port), and jointly forward traffic, and when one Device fails, the traffic can be quickly switched to another Device, thereby ensuring normal operation of services.

However, in the current cross-device aggregation, a network device (denoted as a member device of the cross-device aggregation) where each member port in the cross-device aggregation port is located may have a problem that the network device cannot learn a forwarding entry for message forwarding, such as an ARP/ND entry. For example, when Device B wants to learn the MAC address corresponding to the IPv4/IPv6 interface on Device C, Device B sends an ARP/ND request message to Device C, and under normal circumstances, Device C will select one Port from Port 3 and Port 4 of the member Port of the aggregation group to respond to the ARP/ND reply message, and if Port 3 is selected to respond to the ARP/ND reply message, Device B cannot receive the reply message, so Device B cannot learn the ARP/ND entry of Device C.

Disclosure of Invention

The application provides a cross-device link aggregation method, a cross-device link aggregation device and electronic equipment, so as to solve the problem that member devices aggregated by cross-device cannot learn ARP/ND table items.

The technical scheme provided by the application comprises the following steps:

a cross-device link aggregation method is applied to network equipment, a first port of the network equipment is a member port in an AGG (aggregation gateway group) of the cross-device, and the IP address and the MAC address of each member port in the AGG are the same; the method comprises the following steps:

when a first message is received through the first port, the first message is an ARP/ND request message or an ARP/ND response message, a corresponding forwarding table entry for message forwarding is learned according to the first message, an output interface in the forwarding table entry is the AGG, the first message and an AGG identifier of the AGG are sent through a second port locally connected with other network equipment, so that the other network equipment learns a corresponding forwarding table entry for message forwarding according to the received first message and the AGG identifier, and the output interface in the forwarding table entry is the AGG corresponding to the AGG identifier; the other network devices refer to: a network device having a port which is a member port of the AGG;

when a second message and an AGG identifier are received through the second port, the second message is an ARP/ND request message or an ARP/ND response message, a corresponding forwarding table item for message forwarding is learned according to the second message and the AGG identifier, and an output interface in the forwarding table item is the AGG corresponding to the AGG identifier.

Optionally, the method further comprises:

and when the first port is detected to be changed from normal to fault, deleting all forwarding table entries of which the outgoing interfaces are the AGG from all learned forwarding table entries.

Optionally, the method further comprises:

when the first port is detected to be changed from the fault to the normal state, a third message is sent through one of the local second ports, wherein the third message is an ARP/ND request message of which the target IP address is the designated IP address; the third message carries the AGG identifier; the third message is used to indicate that other network devices receiving the third message refresh the learned egress interfaces as all forwarding entries of the AGG corresponding to the AGG identifier.

Optionally, the method further comprises:

when a third message is received through a local second port, wherein the third message is an ARP/ND request message with a target IP address as an appointed IP address, the third message carries the AGG identifier, a corresponding fourth message is generated for each forwarding table item of the AGG corresponding to the AGG identifier by the learned output interface, the generated fourth message is the ARP/ND request message, and the target IP address is the IP address in the forwarding table item;

and sending the fourth message through the first port.

Optionally, the method further comprises:

when detecting that a link connected with a second port is changed from normal to fault, if the equipment level of the equipment is smaller than the equipment levels of other network equipment connected with the fault link and the equipment levels are represented by equipment priority or equipment health parameters, switching the state of the first port from an UP running state to a shut down state, and deleting all forwarding table entries of which the output interfaces are the AGG from all the learned forwarding table entries;

when detecting that a link connected with a second port is changed from fault to normal, switching the state of the first port from a shutdown shut down state to an UP state, and sending a third message through one of the local second ports, wherein the third message is an ARP/ND request message of which the target IP address is the designated IP address; the third message carries the AGG identifier; the third message is used to indicate that other network devices receiving the third message refresh the learned egress interfaces as all forwarding entries of the AGG corresponding to the AGG identifier.

A cross-device link aggregation device is applied to network equipment, a first port of the network equipment is a member port in an AGG (aggregation gateway group) of the cross-device, and the IP address and the MAC address of each member port in the AGG are the same; the device includes:

a first processing unit, configured to learn, when a first message is received through the first port, a corresponding forwarding entry for forwarding the message according to the first message, where an output interface in the forwarding entry is the AGG, and send the first message and an AGG identifier of the AGG through a second port locally connected to another network device, so that the other network device learns, according to the received first message and the AGG identifier, a corresponding forwarding entry for forwarding the message, where the output interface in the forwarding entry is the AGG corresponding to the AGG identifier; the other network devices refer to: a network device having a port which is a member port of the AGG;

and a second processing unit, configured to learn, when a second message and an AGG identifier are received through the second port, a corresponding forwarding table entry for forwarding the message according to the second message and the AGG identifier, where the second message is an ARP/ND request message or an ARP/ND response message, and an output interface in the forwarding table entry is the AGG corresponding to the AGG identifier.

Optionally, the first processing unit is configured to delete all forwarding entries of which the egress interfaces are the AGG from all learned forwarding entries when it is detected that the first port changes from normal to failure; and the number of the first and second groups,

Optionally, the second processing unit is further configured to, when a third packet is received through the local second port, where the third packet is an ARP/ND request packet whose destination IP address is an assigned IP address, and the third packet carries the AGG identifier, generate a corresponding fourth packet for each forwarding entry of the AGG corresponding to the AGG identifier for the learned egress interface, where the generated fourth packet is the ARP/ND request packet, and the destination IP address is an IP address in the forwarding entry;

the first processing unit is further configured to send the fourth packet through the first port.

Optionally, the second processing unit is further configured to, when it is detected that a link connected to the second port is changed from a normal state to a failure state, switch the state of the first port from an UP running state to a shut down state and delete all forwarding entries whose interfaces are AGGs from all learned forwarding entries if the device level of the device is smaller than the device levels of other network devices connected to the failed link, where the device levels are represented by device priorities or device health parameters; and the number of the first and second groups,

when detecting that a link connected with a second port is changed from fault to normal, switching the state of the first port from a shutdown shut down state to an UP state, and sending a third message through one of the local second ports, wherein the third message is an ARP/ND request message of which the target IP address is the designated IP address; the third message carries the AGG identifier; the third message is used to indicate other network devices receiving the third message to refresh the learned output interfaces into all forwarding table entries of the AGG corresponding to the AGG identifier

An electronic device, comprising: a processor and a machine-readable storage medium;

the machine-readable storage medium stores machine-executable instructions executable by the processor;

the processor is configured to execute machine-executable instructions to implement the above-described method steps.

According to the above technical solution, in the present application, when any member device in the cross-device aggregation (a network device where each member port in the cross-device aggregation AGG is located) receives an ARP/ND request or a response message through a member port in the cross-device aggregation AGG, it learns a corresponding forwarding entry, such as an ARP/ND entry (an outgoing interface in the forwarding entry is AGG), and sends the received ARP/ND request or response message and an identifier of the cross-device aggregation AGG to other member devices in the cross-device aggregation through a forwarding path of an existing network (i.e., a port connected to other member devices in the cross-device aggregation, which is collectively referred to as a second port). When receiving the ARP/ND request or the response packet and the identifier of the AGG of the cross-device aggregation port, other member devices of the cross-device aggregation learn a corresponding forwarding entry, such as an ARP/ND entry (an output interface in the forwarding entry is an AGG corresponding to the AGG identifier). The method solves the problem that the member equipment of the cross-equipment aggregation can not learn the ARP/ND table entry, and realizes the synchronization of the forwarding table entries among the member equipment in the cross-equipment aggregation.

Further, in this embodiment, each member device in the cross-device aggregation operates independently from each other, and there is no coupling relationship between the member devices, which can facilitate upgrading of device versions in the networking, and improve reliability and maintainability of the cross-device aggregation.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure.

FIG. 1 is a schematic diagram of cross-device aggregation networking;

FIG. 2 is a flow chart of a method provided by an embodiment of the present application;

fig. 3 is a schematic diagram of an embodiment of a cross-device aggregation networking provided in an embodiment of the present application;

FIG. 4 is a block diagram of an apparatus according to an embodiment of the present disclosure;

fig. 5 is a hardware structure diagram of the device according to the embodiment of the present application.

Detailed Description

In order to make the method provided by the present application easier to understand, the method provided by the present application is described in detail below with reference to the accompanying drawings and examples:

in this embodiment, cross-device link aggregation is improved, so that forwarding table entries (such as ARP/ND table entries) for message forwarding are synchronized by sending ARP/ND messages through an existing network forwarding path on the premise that each member device of the cross-device aggregation operates independently, which eliminates the problem that the member devices of the cross-device aggregation cannot learn the ARP/ND table entries, and can also improve reliability and maintainability of the cross-device aggregation link.

The methods provided herein are described below:

referring to fig. 2, fig. 2 is a flow chart of a method provided by the present application. The flow is applied to a network device. Optionally, in this embodiment, the network device and the at least one other network device may perform cross-device Aggregation through Simple cross-device Link Aggregation (S-MLAG) to form the cross-device Aggregation port AGG. The first port on the network device is a member port in the cross-device aggregation port AGG. The first Port is named here for ease of description only, such as Port1 shown in FIG. 1.

Optionally, in this embodiment, the IP address and the MAC address of each member port in the same AGG are the same.

As shown in fig. 2, the process may include the following steps:

step 201, when a first message is received through a first port, where the first message is an ARP/ND request message or an ARP/ND reply message, learning a corresponding forwarding entry for forwarding the message according to the first message, where an output interface in the forwarding entry is the AGG, and sending the first message and an AGG identifier of the AGG through a second port locally connected to another network device, so that the other network device learns a corresponding forwarding entry for forwarding the message according to the received first message and the AGG identifier, where the output interface in the forwarding entry is the AGG corresponding to the AGG identifier.

In this embodiment, the other network device in step 201 is a network device that satisfies the condition, for example, the other network device refers to a network device whose one port is a member port in the AGG.

It should be noted that the first message is only named for convenience of description and is not meant to be limiting.

As can be seen from step 201, when any member device in the cross-device aggregation (the network device where each member port in the cross-device aggregation AGG is located) receives the ARP/ND request or the response message through the member port in the cross-device aggregation AGG, it learns the corresponding forwarding table entry, such as the ARP/ND table entry (the outgoing interface in the forwarding table entry is AGG), and sends the received ARP/ND request or the response message and the identifier of the cross-device aggregation AGG to the other member devices in the cross-device aggregation through the forwarding path of the existing network (i.e., the port connected to the other member devices in the cross-device aggregation, which is collectively referred to as the second port). When receiving the ARP/ND request or the response packet and the identifier of the AGG of the cross-device aggregation port, other member devices of the cross-device aggregation learn a corresponding forwarding entry, such as an ARP/ND entry (an output interface in the forwarding entry is an AGG corresponding to the AGG identifier). And finally, the synchronization of forwarding table entries among member devices in cross-device aggregation is realized.

Step 202, when a second message and an AGG identifier are received through a second port, where the second message is an ARP/ND request message or an ARP/ND reply message, learning a corresponding forwarding table entry for forwarding the message according to the second message and the AGG identifier, where an output interface in the forwarding table entry is the AGG corresponding to the AGG identifier.

It should be noted that the second message is only named for convenience of description and is not meant to be limiting.

In this embodiment, when the device receives the ARP/ND request or the response packet and the identifier of the AGG across the device aggregation port through a forwarding path of the existing network (i.e., a port connected to another member device in the device aggregation is collectively referred to as a second port), it learns a corresponding forwarding entry, such as an ARP/ND entry (an output interface in the forwarding entry is an AGG corresponding to the AGG identifier). Finally, the synchronization of the forwarding table items of the equipment and other member equipment in cross-equipment aggregation is realized.

Thus, the flow shown in fig. 2 is completed.

As can be seen from the flow shown in fig. 2, in this embodiment, when any member device in the cross device aggregation (the network device where each member port in the cross device aggregation AGG is located) receives the ARP/ND request or the response message through the member port in the cross device aggregation AGG, it learns the corresponding forwarding entry, such as the ARP/ND entry (the outgoing interface in the forwarding entry is AGG), and sends the received ARP/ND request or the response message and the identifier of the cross device aggregation AGG to other member devices in the cross device aggregation through the forwarding path of the existing network (i.e., the port connected to other member devices in the cross device aggregation, which is collectively referred to as the second port). When receiving the ARP/ND request or the response packet and the identifier of the AGG of the cross-device aggregation port, other member devices of the cross-device aggregation learn a corresponding forwarding entry, such as an ARP/ND entry (an output interface in the forwarding entry is an AGG corresponding to the AGG identifier). The method solves the problem that the member equipment of the cross-equipment aggregation can not learn the ARP/ND table entry, and realizes the synchronization of the forwarding table entries among the member equipment in the cross-equipment aggregation.

It should be noted that, in this embodiment, after learning a forwarding entry, such as an ARP/ND entry, each member device in the cross-device aggregation generates a corresponding host route based on the learned forwarding entry, such as the ARP/ND entry, so as to forward a packet.

To make the flow shown in fig. 2 clearer, the following description is made with reference to a specific embodiment:

referring to fig. 3, fig. 3 is a schematic diagram of networking according to an embodiment provided in the present application. As shown in FIG. 3, device 301 and device 302 run S-MLAGs, based on which Port1_3 on device 301 and Port2_3 on device 302 can be added to the cross-device aggregation Port (based on S-MLAG, here, the cross-device aggregation Port can be denoted as S-MLAG AGG 1). Port 3_1 and Port 3_2 on device 303 are member ports of a common aggregation Port (denoted AGG 2). It should be noted that fig. 3 only uses two devices 301 and 302 to perform cross-device aggregation, and the principles of multiple devices are similar, which are not described herein again.

In FIG. 3, the cross-plant polymerization port S-MLAG AGG1 interfaces with a generic polymerization port AGG 2. Among them, the member ports 1_3 and 2_3 of the S-MLAG AGG1 have the same interface IP address such as 1.1.1.1 and the same interface MAC address such as 0-0-1. For device 303, devices 301, 302 appear to be one device.

As shown in fig. 3, the device 303 sends an ARP/ND request message or a reply message (here, the ARP/ND request message is taken as an example, and the ARP/ND reply message is similar) through Port 3_ 1. The ARP/ND request message will carry the IP address (e.g., 1.1.1.2/1::2) and MAC address (e.g., 0-0-2) of the device 303.

Port1_3 of the device 301 is connected to Port 3_1 of the device 303, and when the device 303 sends an ARP/ND request packet through Port 3_1, the device 301 receives the ARP/ND request packet through Port1_3, and learns a corresponding ARP/ND entry according to the received ARP/ND request packet, as shown in table 1:

TABLE 1

It should be noted that, when the device 301 receives the ARP/ND request message through Port1_3, it will respond to the ARP/ND response message through Port1_3 (the interface IP address of the device 301 is 1.1.1.1/1::1, and the MAC address is 0-0-2). Of course, if the device 301 receives the ARP/ND reply message through Port1_3, it will not respond through Port1_ 3.

In fig. 3, devices 301 and 302 (i.e., member devices aggregated across devices) communicate with each other through a network in a large network.

In fig. 3, if Port1_2 on device 301 and Port2_1 on device 302 are two-layer interworking, device 301 sends the ARP/ND request packet received through Port1_3 and the information of S-MLAG AGG1 through Port1_ 2.

Alternatively, here, the device 301 adds the information of the S-MLAG AGG1 to the ARP/ND request message received through Port1_3 and sends it through Port1_ 2.

Taking ARP request messages (similar to ARP reply messages) as an example, the information of adding S-MLAG AGG1 to ARP request messages can be shown in table 2:

TABLE 2

Taking ND request messages (ND response messages are similar) as an example, the information of S-MLAG AGG1 added by NP request messages can be shown in table 3:

TABLE 3

In fig. 3, suppose that Port1_2 on device 301 is three-layer interworking with Port2_1 on device 302. A three-layer tunnel, such as a three-layer GRE tunnel, can be established between Port1_2 on device 301 and Port2_1 on device 302, with one interface being Port1_2 on device 301 and the other interface being Port2_1 on device 302. The device 301 sends the ARP/ND request message received through Port1_3 and the information of the S-MLAG AGG1 through Port1_2, which is a three-layer tunnel interface. Optionally, here, the device 301 adds the information of the S-MLAG AGG1 to the ARP/ND request packet received through Port1_3 and sends it through three-layer tunnel interface Port1_ 2.

Taking ARP request messages (similar ARP reply messages) as an example, if the three-layer tunnel is a three-layer GRE tunnel, the information of adding S-MLAG AGG1 to the ARP request message can be shown in table 4:

TABLE 4

Taking ND request message (ND response message is similar) as an example, if the three-layer tunnel is a three-layer GRE tunnel, the information of S-MLAG AGG1 added to the NP request message may be as shown in table 5:

TABLE 5

The above describes that the device 301 adds information of the S-MLAG AGG1 to the ARP/ND request packet received through Port1_3 and transmits it through Port1_ 2. It should be noted that, it is described here only by taking cross-device aggregation performed by two devices 301 and 302 as an example, if multiple devices are aggregated in a cross-device manner, the device 301 may further send information of adding the S-MLAG AGG1 to the ARP/ND request packet received through Port1_3 to other devices except the device 302, and the specific sending manner is similarly sent to the device 302.

When the device 302 receives the ARP/ND request packet sent by the device 301 and the information of the S-MLAG AGG1 through the Port2_1, it learns the corresponding ARP/ND entry, as shown in table 6:

TABLE 6

It should be noted that when the device 302 receives the ARP/ND request message through the Port2_1, it also does not need to send the ARP/ND reply message, because the device 301 already replies to the ARP/ND reply message and does not need to reply again.

As described above, both device 301 and device 302 learn the ARP/ND entry for the outbound interface S-MLAG AGG 1. And then, generating a host route according to the ARP/ND table entry, wherein the host route is used for forwarding a corresponding message.

The description of the embodiment shown in fig. 3 is thus completed.

In this embodiment, when any network device detects that a port (here, the first port is also described as an example) on which the port is a member port of the cross-device aggregation port changes from normal to failure, all forwarding entries whose egress interfaces are the cross-device aggregation port are deleted from all learned forwarding entries. Correspondingly, the host routes corresponding to all forwarding table entries of the AGG for the egress interfaces can be further deleted. Taking the device 301 shown in fig. 3 as an example, when the device 301 detects that Port1_3 changes from normal to failure, all forwarding table entries whose egress interfaces are S-MLAG AGG1, such as table 1 above, are deleted from all learned forwarding table entries. Meanwhile, the host routes generated according to all forwarding table entries of the S-MLAG AGG1 on the egress interface are also deleted, so as to ensure that the packet sent to the device 303 is not forwarded through the device 301 any more.

Optionally, later, when the network device detects that the first port changes from the failure to the normal state again, a third message is sent through one of the local second ports, where the third message is an ARP/ND request message whose destination IP address is an assigned IP address; the third message carries the AGG identifier; the third message is used to indicate that other network devices receiving the third message refresh the learned egress interfaces as all forwarding entries of the AGG corresponding to the AGG identifier.

Still taking the device 301 shown in fig. 3 as an example, when the device 301 detects that Port1_3 changes from failure to normal, the device 301 sends an ARP/ND request packet whose destination IP address is a designated IP address (for example, all 0) through the local Port1_2, where the ARP/ND request packet carries S-MLAG AGG 1. When the device 302 receives the ARP/ND request packet through the Port2_1, it generates a corresponding ARP/ND request packet for each forwarding entry, such as the above table 6, whose learned outgoing interface is S-MLAG AGG1, where the destination IP address of the ARP/ND request packet is the IP address in the forwarding entry, and forwards the packet through a Port2_3, which is a member Port locally belonging to S-MLAG AGG 1. It should be noted that, it is described here only by taking cross-device aggregation of two devices 301 and 302 as an example, if multiple devices are aggregated in a cross-device manner, the device 301 only sends an ARP/ND request message with a destination IP address of a specified IP address (for example, all 0) to one member device, for example, the device 302. When the device 303 receives the ARP/ND request message sent by the device 302, it will return an ARP/ND reply message via Port 3_1 or Port 3_ 2. The device 301 receives the ARP/ND reply message through the member Port1_3 of the S-MLAG AGG1, or the device 302 receives the ARP/ND reply message through the member Port2_3 of the S-MLAG AGG1, which returns to the operation executed when the device 301 receives the ARP/ND request message in the embodiment shown in fig. 3, so as to implement ARP/ND entry synchronization among the member devices in the cross-device aggregation. It should be noted that, if the device 302 receives the ARP/ND response message through the member Port2_3 of the S-MLAG AGG1, the device 302 may find the corresponding entry based on the ARP/ND response message (the IP address in the entry is the source IP address of the ARP/ND response message, and the MAC address in the entry is the source MAC address of the ARP/ND response message), and update the aging timestamp of the found entry.

In this embodiment, when any network device receives an ARP/ND request packet (carrying an aggregate gateway AGG identifier) with a destination IP address of a specified IP address (for example, all 0), the operation performed when the device 302 receives the ARP/ND request packet (carrying the S-MLAG AGG1) with the destination IP address of the specified IP address (for example, all 0) will be performed, and details thereof will not be described here.

In this embodiment, the network link (also called network forwarding path) between the member devices in the cross-device aggregation (the devices where the member ports in the cross-device aggregation port AGG are located) can be detected through the multi-hop BFD session, and when any member device detects that the network link (also called a network forwarding path) between it and the other member devices has changed from normal to failed, the device level at this device is less than the device levels of the other network devices connected by the failed link, characterized by device priority or device health parameters, the state of a port (still referred to as a first port) on the present apparatus as a member port in the inter-apparatus aggregation gate AGG is switched from the UP state to the down state, and deleting all forwarding table entries of which the outgoing interfaces are AGGs (aggregation gateway group) of the cross-device from all learned forwarding table entries. Correspondingly, the host routes corresponding to all forwarding table entries of the cross-device aggregation gateway AGG for the egress interfaces can be further deleted. Still taking the device 301 shown in fig. 3 as an example, when the device 301 detects that the network link between the device 301 and the device 302 changes from normal to failure, the device level of the device 301 is compared with the device level of the device 302, and if the device level of the device 302 is found to be lower, the Port1_3 status in the device 301 is maintained to be UP. Then, when the device 302 detects that the network link between the device 302 and the device 301 is changed from normal to failure, the device level of the device 302 and the device level of the device 301 are compared, and if the device level of the device 302 is found to be relatively low, the state of the Port2_3 in the device 302 is switched from the UP state to the shut down state, and all forwarding table entries, such as the table 6, whose egress interfaces are S-MLAG AGG1 are deleted from all the learned forwarding table entries. Correspondingly, the host routes corresponding to all forwarding table entries of the S-MLAG AGG1 on the egress interfaces may be further deleted, so as to ensure that the packet sent to the device 303 is not forwarded through the device 302 any more.

If the member device subsequently detects that all the failed links (also called network forwarding paths) change from failure to normal, the state of the first port in the shutdown state is switched from the shutdown state to the UP state, and a third message is sent through the port locally connected with the link which is recovered to be normal, wherein the third message is an ARP/ND request message with a target IP address as a specified IP address; the third message carries the AGG identifier; the third message is used to indicate that other network devices receiving the third message refresh the learned egress interfaces as all forwarding entries of the AGG corresponding to the AGG identifier.

Taking the example that the device 302 shown in fig. 3 switches the state of the Port2_3 from the UP state to the shut down state, if the device 302 subsequently finds that the network link between the device 302 and the device 301 changes from failure to normal, the state of the Port2_3 is switched from the shut down state to the UP state, and an ARP/ND request message with a destination IP address being a designated IP address (for example, all 0) is sent through the local Port2_1, where the ARP/ND request message carries the S-MLAG AGG 1. When the device 301 receives the ARP/ND request packet through the Port1_2, a corresponding ARP/ND request packet is generated for each forwarding entry, such as the above table 6, whose learned outgoing interface is S-MLAG AGG1, and the destination IP address of the ARP/ND request packet is the IP address in the forwarding entry, and is forwarded through a Port1_3, which is a member Port locally belonging to S-MLAG AGG 1. It should be noted that, it is described here only by taking cross-device aggregation of two devices 301 and 302 as an example, if multiple devices are aggregated in a cross-device manner, the device 302 only sends an ARP/ND request message with a destination IP address of a specified IP address (for example, all 0) to one member device, for example, the device 302. When the device 303 receives the ARP/ND request message sent by the device 301, it will return an ARP/ND reply message via Port 3_1 or Port 3_ 2. The device 301 receives the ARP/ND reply message through the member Port1_3 of the S-MLAG AGG1, or the device 302 receives the ARP/ND reply message through the member Port2_3 of the S-MLAG AGG1, which returns to the operation executed when the device 301 receives the ARP/ND request message in the embodiment shown in fig. 3, so as to implement ARP/ND entry synchronization among the member devices in the cross-device aggregation. It should be noted that, if the device 301 receives the ARP/ND response message through the member Port1_3 of the S-MLAG AGG1, the device 301 finds a corresponding entry based on the ARP/ND response message (the IP address in the entry is the source IP address of the ARP/ND response message, and the MAC address in the entry is the source MAC address of the ARP/ND response message), and updates the aging timestamp of the found entry.

Through the above description, any member device in the cross-device aggregation (the network device where each member port in the cross-device aggregation port AGG is located) can handle the failure in time regardless of the failure of the member port in the cross-device aggregation port AGG or the failure of the network link between the member device and another member device, so as to prevent the interruption of the message forwarding;

further, whether any member device (the network device where each member port in the cross-device aggregation port AGG is located) detects that the member port in the cross-device aggregation port AGG recovers from the failure to be normal or the network link failure with other member devices recovers from the failure to be normal, it also processes in time, and the forwarding table entries between each member device in the cross-device aggregation are synchronized.

The methods provided herein are described above. The following describes the apparatus provided in the present application:

referring to fig. 4, fig. 4 is a structural diagram of an apparatus provided in an embodiment of the present application. The device is applied to network equipment, a first port of the network equipment is a member port in an equipment-spanning aggregation port AGG, and the IP address and the MAC address of each member port in the AGG are the same; the device includes:

Thus, the structure of the apparatus shown in FIG. 4 is completed.

Correspondingly, the application also provides a hardware structure diagram of the device shown in FIG. 4. As shown in fig. 5, the electronic apparatus includes: a processor and a machine-readable storage medium;

the processor is configured to execute machine-executable instructions to perform the method steps of the method of FIG. 2 described above

Based on the same application concept as the method, embodiments of the present application further provide a machine-readable storage medium, where several computer instructions are stored, and when the computer instructions are executed by a processor, the method disclosed in the above example of the present application can be implemented.

The machine-readable storage medium may be, for example, any electronic, magnetic, optical, or other physical storage device that can contain or store information such as executable instructions, data, and the like. For example, the machine-readable storage medium may be: a RAM (random Access Memory), a volatile Memory, a non-volatile Memory, a flash Memory, a storage drive (e.g., a hard drive), a solid state drive, any type of storage disk (e.g., an optical disk, a dvd, etc.), or similar storage medium, or a combination thereof.

The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. A typical implementation device is a computer, which may take the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email messaging device, game console, tablet computer, wearable device, or a combination of any of these devices.

For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functionality of the units may be implemented in one or more software and/or hardware when implementing the present application.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams 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.

Furthermore, 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.

The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. A cross-device link aggregation method is characterized in that the method is applied to network equipment, a first port of the network equipment is a member port in an AGG (aggregation gateway group) of the cross-device, and the IP address and the MAC address of each member port in the AGG are the same; the method comprises the following steps:

2. The method of claim 1, further comprising:

3. The method of claim 1, further comprising:

4. The method of claim 1, further comprising:

and sending the fourth message through the first port.

5. The method of claim 1, further comprising:

6. A cross-device link aggregation device is characterized in that the device is applied to network equipment, a first port of the network equipment is a member port in an AGG (aggregation gateway group) of the cross-device, and the IP address and the MAC address of each member port in the AGG are the same; the device includes:

7. The apparatus according to claim 6, wherein the first processing unit is configured to, when it is detected that the first port goes from normal to failure, delete all forwarding entries whose egress interfaces are the AGG from all learned forwarding entries; and the number of the first and second groups,

8. The apparatus according to claim 6, wherein the second processing unit is further configured to, when a third packet is received through the local second port, where the third packet is an ARP/ND request packet whose destination IP address is a specified IP address, and the third packet carries the AGG identifier, generate a corresponding fourth packet for each forwarding entry of the AGG corresponding to the AGG identifier for the learned egress interface, where the generated fourth packet is the ARP/ND request packet and the destination IP address is an IP address in the forwarding entry;

9. The apparatus according to claim 6, wherein the second processing unit is further configured to, when it is detected that a link connected to the second port is changed from normal to failed, if a device level of the device is smaller than device levels of other network devices connected to the failed link, where the device levels are characterized by device priorities or device health parameters, switch the state of the first port from an UP running state to a down running state, and delete all forwarding entries whose interfaces are AGGs from all learned forwarding entries; and the number of the first and second groups,

10. An electronic device, comprising: a processor and a machine-readable storage medium;

the processor is configured to execute machine executable instructions to implement the method steps of any of claims 1-5.