Network management method, system, switch and storage medium for cross-device link aggregation

Abstract

The embodiment of the present application relates to the field of communication transmission, in particular to a network management method and system for cross-device link aggregation, a switch and a storage medium. The switch is applied to a cross-device link aggregation switch system, each switch is respectively provided with a sub-IP address of a cross-device link aggregation switch system IP, and the method comprises the following steps: receiving a request for operating the switch sent by a network management server through a convergence node; the request carries a sub-IP address of a target switch of operation; if the sub-IP address of the target switch is a sub-IP address of another switch in the cross-device link aggregation switch system, the request is forwarded to the another switch through a first link, wherein the first link is a communication link between the current switch and the another switch. The network management can be directly performed on each switch device of the cross-device link aggregation switch system without adding additional configuration, so that the network configuration cost is saved.

Description

Technical Field

[0001] This application relates to the field of communication transmission, and in particular to a network management method, system, switch, and storage medium for cross-device link aggregation. Background Technology

[0002] The common management method for cross-device link aggregation switches is to configure each of the two switches in the cross-device link aggregation switch system, the upstream aggregation node, and the network management server into a separate Layer 3 network for independent management. In this separate Layer 3 network, the aggregation node acts as the gateway, and the cross-device link aggregation switch system is no longer considered a single aggregation link, but rather as multiple independent switches, each with a different IP address. Through the routing of the Layer 3 network, the network management server can manage the two switches in the cross-device link aggregation switch system separately.

[0003] Therefore, in order to ensure that the cross-device link aggregation switch system can be correctly managed, it is necessary to configure an additional Layer 3 network specifically for network management. However, configuring a Layer 3 network is complex, requiring the reconfiguration of a dedicated Layer 3 network for network management and the establishment of management channels to the two switches in the cross-device link aggregation switch system. Furthermore, the need to configure a dedicated Layer 3 network for network management consumes additional IP addresses and VLAN IDs, increasing maintenance complexity, as a management network must be maintained on the device in addition to the network for service operations. Summary of the Invention

[0004] The purpose of this invention is to provide a network management method, system, switch, and storage medium for cross-device link aggregation, which can manage the cross-device link aggregation system without adding any network configuration, thereby reducing the complexity of network maintenance and saving network resources.

[0005] To address the aforementioned technical problems, embodiments of the present invention provide a network management method for cross-device link aggregation, applied to switches in a cross-device link aggregation switch system, wherein each switch is provided with a sub-IP address of the cross-device link aggregation switch system IP, comprising the following steps:

[0006] Receive a request from the network management server via the aggregation node for operating the switch; the request carries the sub-IP address of the target switch to be operated.

[0007] If the sub-IP address of the target switch is the sub-IP address of another switch in the cross-device link aggregation switch system, then the request is forwarded to the other switch through the first link, wherein the first link is the communication link between the current switch and the other switch.

[0008] To address the aforementioned technical problems, embodiments of the present invention provide a network management system for cross-device link aggregation, comprising: a network management server, an aggregation node communicatively connected to the network management server, and a cross-device link aggregation switch system communicatively connected to the aggregation node. The cross-device link aggregation switch system includes at least two switches, each switch having a sub-IP address of the cross-device link aggregation switch system IP.

[0009] The network management server is used to send a request for operating the switch to the switch in the cross-device link switching system through the aggregation node, the request containing the sub-IP address of the target switch to be operated.

[0010] An aggregation node is used to forward the request to the switches in the cross-device link aggregation switch system.

[0011] The switch is used to receive the request sent by the network management server through the aggregation node. If the sub-IP address of the target switch is the sub-IP address of another switch in the cross-device link aggregation switch system, the request is forwarded to the other switch through the first link, wherein the first link is the communication link between the current switch and the other switch.

[0012] To address the aforementioned technical problems, embodiments of the present invention provide a switch located in a cross-device link aggregation switch system, and having a sub-IP address of the cross-device link aggregation switch system IP. The switch includes:

[0013] The receiving unit is used to receive a request from the network management server to operate the switch through the aggregation node; the request carries the sub-IP address of the target switch to be operated.

[0014] The processing unit is configured to forward the request to the other switch via a first link when the sub-IP address of the target switch is the sub-IP address of another switch in the cross-device link aggregation switch system, wherein the first link is a communication link between the current switch and the other switch.

[0015] To address the aforementioned technical problems, embodiments of the present invention provide a switch, comprising:

[0016] At least one processor; and,

[0017] A memory communicatively connected to the at least one processor; wherein,

[0018] The memory stores instructions that can be executed by the at least one processor, which enables the at least one processor to perform the network management method for cross-device link aggregation described above.

[0019] To address the aforementioned technical problems, embodiments of the present invention provide a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the aforementioned network management method for cross-device link aggregation.

[0020] The cross-device link aggregation network management method proposed in this application utilizes the sub-IPs of each switch in the current cross-device link aggregation switch system and the first switching link between the switches for information exchange. This allows the network management server to directly manage each switch device in the cross-device link aggregation switch system without adding extra configuration, thereby improving the convenience of network management, enhancing network usability, and saving network configuration costs. Attached Figure Description

[0021] One or more embodiments are illustrated by way of example with reference numerals in the accompanying drawings. These illustrations do not constitute a limitation on the embodiments. Elements with the same reference numerals in the drawings are denoted as similar elements. Unless otherwise stated, the figures in the drawings are not to be limited by scale.

[0022] Figure 1 This is a flowchart of a network management method for cross-device link aggregation according to an embodiment of this application;

[0023] Figure 2 This is a schematic diagram of a network management system for cross-device link aggregation according to an embodiment of this application;

[0024] Figure 3 This is a schematic diagram of a switch provided according to an embodiment of this application;

[0025] Figure 4 This is a schematic diagram of a switch provided according to an embodiment of this application. Detailed Implementation

[0026] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the various embodiments of this application will be described in detail below with reference to the accompanying drawings. However, those skilled in the art will understand that many technical details have been provided in the various embodiments of this application to help readers better understand this application. However, the technical solutions claimed in this application can be implemented even without these technical details and various changes and modifications based on the following embodiments. The division of the various embodiments below is for the convenience of description and should not constitute any limitation on the specific implementation of this application. The various embodiments can be combined with and referenced by each other without contradiction.

[0027] The terms "first" and "second" used in the embodiments of this application are for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this application, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a system, product, or device that includes a series of components or units is not limited to the listed components or units, but may optionally include unlisted components or units, or may optionally include other components or units inherent to such products or devices. In the description of this application, "a plurality of" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0028] One embodiment of the present invention relates to a network management method for cross-device link aggregation, applied to switches in a cross-device link aggregation switch system, wherein each switch is provided with a sub-IP address of the cross-device link aggregation switch system IP. The specific process is as follows: Figure 1 As shown.

[0029] Step 101: Receive a request from the network management server through the aggregation node for operating the switch. The request carries the sub-IP address of the target switch to be operated.

[0030] Step 102: If the sub-IP address of the target switch is the sub-IP address of another switch in the cross-device link aggregation switch system, the request will be forwarded to the other switch through the first link, where the first link is the communication link between the current switch and the other switch.

[0031] In this embodiment, by utilizing the sub-IPs of each switch in the current cross-device link aggregation switch system and the first switching link between the switches for information exchange, the network management server can directly manage each switch device in the cross-device link aggregation switch system without adding additional configuration, thereby improving the convenience of network management, enhancing network usability, and saving network configuration costs.

[0032] The following is a detailed description of the implementation details of the cross-device link aggregation network management method in this embodiment. The following content is only for the convenience of understanding and is not necessary for implementing this solution.

[0033] In step 101, a request for operating the switch is received from the network management server through the aggregation node. The request carries the sub-IP address of the target switch to be operated.

[0034] Generally, when a network management server accesses a network containing a cross-device link aggregation switch system, the access point is at the aggregation node. From the aggregation node's perspective, the forwarding of data requests in the cross-device link aggregation switch system is load-balanced. However, when the network management server manages the cross-device link aggregation switch system, if it needs to manage a specific switch, the data request may be load-balanced at the aggregation node. This means that after processing by the aggregation node, the data request may not necessarily be sent to the target switch, leading to a network management disconnection problem. In this implementation, the switches in the cross-device link aggregation switch system not only display the system's external IP address to external devices but also display the sub-IP addresses of each switch to clarify the target switch for the request. Based on this, the network management server sends a request through the aggregation node that includes the sub-IP address of the target switch to clarify the target switch for the request.

[0035] In step 102, the target switch is determined based on the sub-IP address of the current switch. If the sub-IP address of the target switch is the sub-IP address of another switch in the cross-device link aggregation switch system, the request is forwarded to the other switch through the first link, where the first link is the communication link between the current switch and the other switch.

[0036] After receiving a request from the aggregation node, the switch determines whether it is the target switch by comparing its current sub-IP address (which receives the request) with the target switch's sub-IP address carried in the request. That is, if the current switch's sub-IP address matches the target switch's sub-IP address in the request, then the current switch receiving the request is the target switch, and the request can be processed or responded to accordingly. In one example, when the current switch receives a request and its central processing unit (CPU) determines that it is the target switch, it obtains the source MAC address of the request from the request, processes or responds to the request, and replies to the source MAC address.

[0037] In one example, the first link can be a peer-link between the current switch and another switch (the target switch). No new communication link needs to be created, nor is any additional maintenance required.

[0038] In one example, the network management method for cross-device link aggregation also includes: if the current switch receives the request from the first link, the current switch prohibits updating the mapping between the MAC address and the transmission port of the request. In some cases, this can be defined as not learning MAC addresses. The MAC address in the request is the target address for the switch to respond to the request. Prohibiting the updating of the mapping between the MAC address and the transmission port of the request means that the mapping between the MAC address and the transmission port in the request will not be updated or overwritten multiple times. That is, after one forwarding in the first link, the target switch still retains the mapping between the MAC address and the uplink interface, thereby avoiding MAC drift and maintaining the normal use of the MAC address table entries. If MAC drift occurs, it means that because the transmission port corresponding to the MAC address has been updated, the target switch will store the mapping between the MAC address and the port of the first link. When it receives the next request sent to the target switch by the aggregation node, it will reply or process according to the mapping between the MAC address and the port of the first link. After processing, the mapping between the MAC address and the uplink interface will overwrite the original mapping. Repeated occurrences will lead to transmission path chaos and hinder information reply and response in this system. In this example, by prohibiting the mapping between MAC addresses and transmission ports in the update request, the target address of the response information is ensured to be correct and the transmission path is stable. The transmission path will not be disordered due to MAC address drift, thus ensuring the normal information transmission path in the cross-device link aggregation device.

[0039] In one example, the network management method for cross-device link aggregation further includes: if the current switch receives the request from the first link, the current switch prohibits the request from being retransmitted, or in some examples, this can be defined as broadcast suppression for each switch. That is, the same data is only allowed to be sent once by the switch device, and if a received request is sent by a switch, it is not allowed to be retransmitted. This is to avoid request loopback to the switch that forwarded the request, avoid request backtracking to the aggregation node, and also avoid request transmission to downstream devices, reducing unnecessary waste of transmission and processing resources, and improving the data processing quality and speed of this cross-device link aggregation switch system.

[0040] In another example, the network management method for cross-device link aggregation further includes: if the current switch receives a request from the first link, the current switch transmits the response message of the request to the aggregation node from its uplink interface; wherein, the uplink interface is the interface through which the current switch and the aggregation node interact. That is, if the request received by the current switch is directly sent by the aggregation node, the response is sent to the current switch's uplink interface; if the request is forwarded from another switch, the response is also sent to the current switch's uplink interface. Specifying the response message's path ensures that the response message can respond to the request over the shortest distance, i.e., directly sent to the aggregation node through the switch's uplink interface, reducing response time and improving the data processing rate of this cross-device link aggregation switch system.

[0041] Alternatively, the first link can be a peer-link link, and the request includes Address Resolution Protocol (ARP) requests.

[0042] In one implementation, when the network management server sends an ARP request to access a switch in a cross-device link aggregation system, if this ARP request is load-balanced to another cross-device link aggregation switch by the aggregation node, the request will be dropped because it cannot receive a correct response, resulting in the network management server's ARP not being responded to correctly. However, this implementation allows ARP request packets to be allowed on the peer-link port through access control or other methods, ensuring that regardless of which side of the cross-device link aggregation system the ARP packet is load-balanced to, it can reach the target side through the peer-link. Furthermore, the identification and determination of the switch is based on the sub-IP addresses of the existing switches in the original network, eliminating the need for a new network architecture, reducing resource consumption and subsequent maintenance requirements. Simultaneously, broadcast suppression prevents the ARP packet from looping back to the aggregation node. To prevent MAC address drift between the uplink interfaces of the switches and aggregation nodes and the peer-link port, the peer-link port remains in a non-learning MAC address state. In addition, after the CPU of the target switch receives this ARP packet, whether it is received from the switch's uplink interface or from the port of the peer-link link, it will send an ARP reply from the switch's uplink interface.

[0043] Using the method described in this implementation, ARP requests sent by the network management server to a switch in a cross-device link aggregation switch system can be correctly forwarded to the switch device that needs a response, regardless of which side the aggregation node sends them to. Furthermore, no entries or forwarding behaviors that abnormally interfere with the cross-device link aggregation switch system will occur throughout the entire process. Network management of each switch device in the cross-device link aggregation switch system can be performed directly without additional configuration, improving the convenience of network management, enhancing network usability, and saving network configuration costs.

[0044] The steps of the various methods described above are only for clarity. In practice, they can be combined into one step or some steps can be split into multiple steps. As long as they include the same logical relationship, they are all within the scope of protection of this patent. Adding insignificant modifications or introducing insignificant designs to the algorithm or process, but without changing the core design of the algorithm and process, are also within the scope of protection of this patent.

[0045] One embodiment of the present invention relates to a network management system for cross-device link aggregation. For example... Figure 2 As shown, it includes:

[0046] The network management server, the aggregation node that communicates with the network management server, and the cross-device link aggregation switch system that communicates with the aggregation node. The cross-device link aggregation switch system includes at least two switches, and each switch is provided with a sub-IP address of the cross-device link aggregation switch system IP.

[0047] Network management server 201 is used to send requests for operating the switches to the switches in the cross-device link switching system through the aggregation node. The requests include the sub-IP address of the target switch to be operated.

[0048] Aggregation node 202 is used to forward requests to switches in the cross-device link aggregation switch system;

[0049] Switch 203 is used to receive requests sent by the network management server through the aggregation node. If the sub-IP address of the target switch is the sub-IP address of another switch in the cross-device link aggregation switch system, the request will be forwarded to the other switch through the first link, where the first link is the communication link between the current switch and the other switch.

[0050] In one example, switch 203 is also used to transmit requests to aggregation node 202 via the uplink interface.

[0051] In one example, when an aggregation node forwards a request to a target switch—for instance, a network management server accessing a switch in a cross-device link aggregation switch system broadcasts a request packet to the aggregation node—the aggregation node, through load balancing, directly forwards this packet to the correct switch requiring a response. The switch requiring a response processes this request packet on its CPU, learns the MAC address of the network management server on its uplink interface connected to the aggregation node, and responds to the request packet. This response information is sent from the uplink interface to the aggregation node, which then forwards the response to the network management server. In another example, specifically, network management server C needs to manage switch A. The network management server broadcasts an ARP request packet to aggregation node G. Aggregation node G, through load balancing, forwards the ARP request to switch A. Switch A receives this ARP packet from port A1, sends it to its CPU for processing, learns the MAC address of network management server C on port A1, and responds to the network management server's ARP request. This response data is sent from A1 to aggregation node G. Aggregation node G then forwards the ARP response to network management server C. This establishes a network management path.

[0052] In one example, when the aggregation node forwards a request to a non-target switch—for instance, when a network management server accesses a switch in a cross-device link aggregation system and broadcasts a request packet to the aggregation node—the aggregation node, through load balancing, forwards this packet to a non-target switch in the cross-device link aggregation system. This switch processes the request packet in its CPU, and if the CPU finds that the request packet is not for itself, it forwards it through the first link to the target switch that needs a response. The target switch processes the request packet in its CPU, and simultaneously activates its broadcast isolation function, ceasing to forward the request packet and not learning its MAC address. It then writes the MAC address of the request packet into its uplink interface and responds to the network management server, sending the response data from the uplink interface to the aggregation node. The aggregation node then sends the response to the network management server. In another example, specifically, network management server C needs to manage switch A. Network management server C broadcasts an ARP request message to aggregation node G. Aggregation node G, through load balancing, forwards the ARP request to switch B. Switch B sends this ARP to its CPU for processing. Switch B's CPU detects that this ARP is not for itself, so it forwards it to the target switch A, which needs a response, via a peer-link. Switch A sends this ARP to its CPU for processing, and simultaneously, broadcast isolation is activated; switch A no longer forwards this ARP message and does not learn its MAC address. After processing the ARP in its CPU, switch A writes the MAC address of this ARP message into uplink interface A1 and sends an ARP response to network management server C. This response data is sent from uplink interface A1 to aggregation node G. Aggregation node G then sends the ARP response back to network management server C. This also establishes a network management path.

[0053] As can be seen from the above technical solutions, compared with the network management system of a typical cross-device link aggregation switch system, this technical approach eliminates the need to build any new management network. The network management server can correctly access any switch in the cross-device link aggregation switch system without altering the forwarding policy of the aggregation node or the forwarding behavior and policy of the entire system. This method greatly simplifies the network management network configuration of the cross-device link aggregation switch system, allowing direct management through the service network. Since no additional network configuration is required, IP addresses and VLAN resources are saved, improving network stability and reliability while reducing network maintenance costs.

[0054] One embodiment of the present invention relates to a switch located in a cross-device link aggregation switch system, and having a sub-IP address of the cross-device link aggregation switch system IP, such as... Figure 3 As shown, it includes:

[0055] The receiving unit 301 is used to receive a request sent by the network management server through the aggregation node; the request carries the sub-IP address of the target switch corresponding to the request.

[0056] The processing unit 302 is configured to forward the request to another switch via the first link if the sub-IP address of the target switch is the sub-IP address of another switch in the cross-device link aggregation switch system, wherein the first link is the communication link between the current switch and the other switch.

[0057] Additionally, if the current switch receives a request from the first link, the current switch is prohibited from updating the mapping between the MAC address and the transmission port of the request.

[0058] Additionally, if the current switch receives a request from the first link, the current switch will prevent the request from being transmitted again.

[0059] Additionally, if the current switch receives the request from the first link, the current switch will transmit the response message of the request to the aggregation node from the uplink interface of the current switch; wherein, the uplink interface is the interface through which the current switch and the aggregation node exchange information.

[0060] Additionally, the first link is a peer-link link; the request includes an Address Resolution Protocol (ARP) request.

[0061] It is not difficult to see that this embodiment is a system implementation corresponding to the first embodiment, and this embodiment can be implemented in conjunction with the first embodiment. The relevant technical details mentioned in the first embodiment are still valid in this embodiment, and will not be repeated here to reduce repetition. Accordingly, the relevant technical details mentioned in this embodiment can also be applied to the first embodiment.

[0062] It is worth mentioning that all modules involved in this embodiment are logical modules. In practical applications, a logical unit can be a physical unit, a part of a physical unit, or a combination of multiple physical units. Furthermore, to highlight the innovative aspects of this invention, this embodiment does not introduce units that are not closely related to solving the technical problem proposed by this invention; however, this does not mean that other units are absent from this embodiment.

[0063] One embodiment of the present invention relates to a switch, such as Figure 4 As shown, including

[0064] At least one processor 401; and,

[0065] Memory 402 communicatively connected to the at least one processor; wherein,

[0066] The memory stores instructions that can be executed by the at least one processor, which enables the at least one processor to perform the network management method for cross-device link aggregation described above.

[0067] The memory and processor are connected via a bus, which can include any number of interconnecting buses and bridges, connecting various circuits of one or more processors and memories. The bus can also connect various other circuits, such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and will not be described further herein. The bus interface provides an interface between the bus and the transceiver. The transceiver can be a single element or multiple elements, such as multiple receivers and transmitters, providing a unit for communicating with various other devices over a transmission medium. Data processed by the processor is transmitted over the wireless medium via an antenna, which further receives data and transmits it to the processor.

[0068] The processor manages the bus and general processing, and also provides various functions, including timing, peripheral interfaces, voltage regulation, power management, and other control functions. Memory is used to store data used by the processor during operation.

[0069] One embodiment of the present invention relates to a computer-readable storage medium storing a computer program. When executed by a processor, the computer program implements the method embodiments described above.

[0070] That is, those skilled in the art will understand that all or part of the steps in the methods of the above embodiments can be implemented by a program instructing related hardware. This program is stored in a storage medium and includes several instructions to cause a device (which may be a microcontroller, chip, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as a USB flash drive, a portable hard drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0071] Those skilled in the art will understand that the above embodiments are specific examples of implementing the present invention, and in practical applications, various changes in form and detail may be made without departing from the spirit and scope of the present invention.

Claims

1. A network management method for cross-device link aggregation, characterized in that, A method for using switches in a cross-device link aggregation switch system, wherein each switch is provided with a sub-IP address of the cross-device link aggregation switch system IP, the method comprising: Receive a request from the network management server via the aggregation node for operating the switch; the request carries the sub-IP address of the target switch to be operated. If the sub-IP address of the target switch is the sub-IP address of another switch in the cross-device link aggregation switch system, then the request is forwarded to the other switch through the first link, wherein the first link is the communication link between the switch and the other switch.

2. The network management method for cross-device link aggregation according to claim 1, characterized in that, Also includes: If the switch receives the request from the first link, the switch prohibits updating the mapping between the MAC address and the transmission port of the request.

3. The network management method for cross-device link aggregation according to claim 1, characterized in that, Also includes: If the switch receives the request from the first link, the switch prohibits the request from being transmitted again.

4. The network management method for cross-device link aggregation according to claim 1, characterized in that, Also includes: If the switch receives the request from the first link, the switch transmits the response message of the request to the aggregation node from the uplink interface of the switch; wherein, the uplink interface is the interface through which the switch and the aggregation node exchange information.

5. The network management method for cross-device link aggregation according to any one of claims 1 to 4, characterized in that, The first link is a peer-link link; The request includes an Address Resolution Protocol (ARP) request.

6. A network management system for cross-device link aggregation, characterized in that, include: A network management server, an aggregation node connected to the network management server, and a cross-device link aggregation switch system connected to the aggregation node. The cross-device link aggregation switch system includes at least two switches, each of which is provided with a sub-IP address of the cross-device link aggregation switch system IP. The network management server is used to send a request for operating the switch to the switch in the cross-device link switch system through the aggregation node, and the request includes the sub-IP address of the target switch to be operated. The aggregation node is used to forward the request to the switches in the cross-device link aggregation switch system; The switch is used to receive the request sent by the network management server through the aggregation node. If the sub-IP address of the target switch is the sub-IP address of another switch in the cross-device link aggregation switch system, the request is forwarded to the other switch through the first link, wherein the first link is the communication link between the switch and the other switch.

7. The network management system for cross-device link aggregation according to claim 6, characterized in that, The switch is also used to transmit the request to the aggregation node via the uplink interface.

8. A switch, characterized in that, The switch is located in a cross-device link aggregation switch system and has a sub-IP address of the cross-device link aggregation switch system IP. The switch includes: The receiving unit is used to receive a request from the network management server to operate the switch through the aggregation node; the request carries the sub-IP address of the target switch to be operated. The processing unit is configured to forward the request to the other switch via a first link when the sub-IP address of the target switch is the sub-IP address of another switch in the cross-device link aggregation switch system, wherein the first link is a communication link between the switch and the other switch.

9. A switch, characterized in that, include: At least one processor; as well as, A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform the network management method for cross-device link aggregation as described in any one of claims 1 to 5.

10. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by the processor, it implements the network management method for cross-device link aggregation as described in any one of claims 1 to 5.

Images