Network path planning method, device and equipment and storage medium

Abstract

The application relates to a network path planning method and device, equipment and a storage medium. The method comprises the following steps: in response to a spine device query request sent by any data sender, selecting a spine device with the highest idle degree as a target spine device based on the idle degree of each spine device; returning a loopback interface address of the target spine device to the data sender, so that the data sender performs data encapsulation on the loopback interface address and elephant flow service data based on a preset encapsulation mode, obtains encapsulated data, and sends the encapsulated data to the target spine device corresponding to the loopback interface address through a data sending leaf device directly connected with the data sender; and the encapsulated data is disencapsulated by the target spine device, elephant flow service data is obtained, and the elephant flow service data is sent to a data receiving leaf device and then to a data receiver through the data receiving leaf device. The method can balance the flow pressure of each network device.

Description

Technical Field

[0001] This application relates to the field of network communication technology, and in particular to a network path planning method, apparatus, device, and storage medium. Background Technology

[0002] With the rapid development of data center network technology, high-bandwidth, high-throughput service scenarios are constantly increasing, and "elephant stream" services have become the mainstream business model within data centers. Current network transmission methods primarily rely on traditional routing and forwarding mechanisms to achieve data exchange.

[0003] However, traditional processing methods suffer from uneven device load, local congestion, and wasted bandwidth resources when transmitting large streams. Summary of the Invention

[0004] Therefore, it is necessary to provide a network path planning method, apparatus, device, and storage medium that can balance the traffic pressure of various network devices to address the above-mentioned technical problems.

[0005] Firstly, this application provides a network path planning method, including:

[0006] In response to a spine device query request sent by any data sender, the idle level of each spine device is determined based on the bandwidth utilization of each spine device port in the data center network, and the spine device with the highest idle level is selected as the target spine device.

[0007] The loopback interface address of the target ridge device is returned to the data sender, so that the data sender can encapsulate the data based on the loopback interface address and the elephant stream service data using a preset encapsulation method, obtain the encapsulated data, and send the encapsulated data to the target ridge device corresponding to the loopback interface address through the data sending leaf device directly connected to the data sender.

[0008] The encapsulated data is decapsulated by the target spine device to obtain the elephant stream business data;

[0009] The target ridge device sends the elephant stream service data to the data receiving leaf device pointed to by the destination IP address in the elephant stream service data, so that the elephant stream service data is sent to the data receiver directly connected to the data receiving leaf device through the data receiving leaf device.

[0010] In one embodiment, prior to responding to a spine device query request sent by any data sender, the method further includes:

[0011] Configure the border gateway protocol for leaf and spine devices within the same network unit of the data center network.

[0012] In one embodiment, border gateway protocol configuration includes:

[0013] Leaf devices connected to the same server are grouped into the same group, leaf devices in the same group are set to the same Autonomous System Number (ASN), and leaf devices in different groups are set to different ASN. The default route of each leaf device is directed to all spine devices. The spine devices are set to the same ASN, and a preset rule is configured on each spine device. The preset rule allows the receiving of routing information corresponding to its own ASN once.

[0014] In one embodiment, the method further includes:

[0015] Configure the preset decapsulation method corresponding to the preset encapsulation method of all spine devices on each spine device.

[0016] In one embodiment, the method further includes:

[0017] If the target ridge device is faulty, a secondary target ridge device is determined from the ridge devices other than the target ridge device based on the equal-cost multipath routing strategy. The loopback interface address of the secondary target ridge device is returned to the data sender, so that the data sender can encapsulate the data based on the loopback interface address and the elephant stream service data using a preset encapsulation method, obtain encapsulated data, and send the encapsulated data to the secondary target ridge device corresponding to the loopback interface address through the data sending leaf device directly connected to the data sender. Based on the tunnel termination of the target ridge device pre-configured on the secondary target ridge device, the encapsulated data is decapsulated through the secondary target ridge device to obtain the elephant stream service data.

[0018] In one embodiment, the method further includes:

[0019] If the communication link between the target ridge device and the data receiving leaf device pointed to by the destination IP address in the elephant stream service data is faulty, a secondary target ridge device is determined from the ridge devices other than the target ridge device based on the equal-cost multipath routing strategy. The elephant stream service data is sent from the target ridge device to the secondary target ridge device, and then sent through the secondary target ridge device to the data receiving leaf device pointed to by the destination IP address in the elephant stream service data, so that the elephant stream service data is sent through the data receiving leaf device to the data receiver directly connected to the data receiving leaf device.

[0020] Secondly, this application also provides a network path planning apparatus, comprising:

[0021] The selection module is used to respond to a spine device query request sent by any data sender, determine the idle level of each spine device based on the bandwidth utilization of each spine device port in the data center network, and select the spine device with the highest idle level as the target spine device.

[0022] The encapsulation module is used to return the loopback interface address of the target spine device to the data sender, so that the data sender can encapsulate the data based on the loopback interface address and the elephant stream service data using a preset encapsulation method, obtain encapsulated data, and send the encapsulated data to the target spine device corresponding to the loopback interface address through the data sending leaf device directly connected to the data sender.

[0023] The decapsulation module is used to decapsulate the encapsulated data through the target spine device to obtain the elephant stream business data;

[0024] The sending module is used to send the elephant stream service data to the data receiving leaf device pointed to by the destination IP address in the elephant stream service data through the target spine device, so that the elephant stream service data is sent to the data receiver directly connected to the data receiving leaf device through the data receiving leaf device.

[0025] Thirdly, this application also provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to perform the following steps:

[0026] In response to a spine device query request sent by any data sender, the idle level of each spine device is determined based on the bandwidth utilization of each spine device port in the data center network, and the spine device with the highest idle level is selected as the target spine device.

[0027] The loopback interface address of the target ridge device is returned to the data sender, so that the data sender can encapsulate the data based on the loopback interface address and the elephant stream service data using a preset encapsulation method, obtain the encapsulated data, and send the encapsulated data to the target ridge device corresponding to the loopback interface address through the data sending leaf device directly connected to the data sender.

[0028] The encapsulated data is decapsulated by the target spine device to obtain the elephant stream business data;

[0029] The target ridge device sends the elephant stream service data to the data receiving leaf device pointed to by the destination IP address in the elephant stream service data, so that the elephant stream service data is sent to the data receiver directly connected to the data receiving leaf device through the data receiving leaf device.

[0030] Fourthly, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, performs the following steps:

[0031] In response to a spine device query request sent by any data sender, the idle level of each spine device is determined based on the bandwidth utilization of each spine device port in the data center network, and the spine device with the highest idle level is selected as the target spine device.

[0032] The loopback interface address of the target ridge device is returned to the data sender, so that the data sender can encapsulate the data based on the loopback interface address and the elephant stream service data using a preset encapsulation method, obtain the encapsulated data, and send the encapsulated data to the target ridge device corresponding to the loopback interface address through the data sending leaf device directly connected to the data sender.

[0033] The encapsulated data is decapsulated by the target spine device to obtain the elephant stream business data;

[0034] The target ridge device sends the elephant stream service data to the data receiving leaf device pointed to by the destination IP address in the elephant stream service data, so that the elephant stream service data is sent to the data receiver directly connected to the data receiving leaf device through the data receiving leaf device.

[0035] Fifthly, this application also provides a computer program product, including a computer program that, when executed by a processor, performs the following steps:

[0036] In response to a spine device query request sent by any data sender, the idle level of each spine device is determined based on the bandwidth utilization of each spine device port in the data center network, and the spine device with the highest idle level is selected as the target spine device.

[0037] The loopback interface address of the target ridge device is returned to the data sender, so that the data sender can encapsulate the data based on the loopback interface address and the elephant stream service data using a preset encapsulation method, obtain the encapsulated data, and send the encapsulated data to the target ridge device corresponding to the loopback interface address through the data sending leaf device directly connected to the data sender.

[0038] The encapsulated data is decapsulated by the target spine device to obtain the elephant stream business data;

[0039] The target ridge device sends the elephant stream service data to the data receiving leaf device pointed to by the destination IP address in the elephant stream service data, so that the elephant stream service data is sent to the data receiver directly connected to the data receiving leaf device through the data receiving leaf device.

[0040] The aforementioned network path planning method, apparatus, device, and storage medium, in response to a spine device query request sent by any data sender, determines the idle level of each spine device based on the bandwidth utilization of each spine device port in the data center network, and selects the spine device with the highest idle level as the target spine device; returns the loopback interface address of the target spine device to the data sender, so that the data sender can encapsulate the data based on the loopback interface address and the elephant stream service data using a preset encapsulation method, obtain encapsulated data, and send the encapsulated data to the target spine device corresponding to the loopback interface address through a data sending leaf device directly connected to the data sender; the target spine device decapsulates the encapsulated data to obtain the elephant stream service data; and the target spine device sends the elephant stream service data to the data receiving leaf device pointed to by the destination IP address in the elephant stream service data, so that the data receiving leaf device sends the elephant stream service data to the data receiver directly connected to the data receiving leaf device. By combining the bandwidth utilization of each spine device port to determine the idle status and selecting the optimal target spine device, the transmission path can be dynamically planned according to the real-time network load, effectively balancing the traffic pressure of each network device and preventing problems such as uneven device load, local congestion, and wasted bandwidth resources caused by traditional fixed routing methods. Attached Figure Description

[0041] To more clearly illustrate the technical solutions in the embodiments of this application or related technologies, the drawings used in the description of the embodiments of this application or related technologies will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0042] Figure 1 This is a flowchart illustrating a network path planning method in one embodiment;

[0043] Figure 2 This is a connection structure diagram of the devices involved in the network path planning method in one embodiment;

[0044] Figure 3 This is a structural block diagram of a network path planning device in one embodiment;

[0045] Figure 4 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0046] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0047] In one embodiment, such as Figure 1 As shown, a network path planning method is provided. This embodiment illustrates the method applied to a terminal. It is understood that this method can also be applied to a server, and further to a system including both a terminal and a server, and implemented through interaction between the terminal and the server. In this embodiment, the method includes the following steps:

[0048] Step 102: In response to a spine device query request sent by any data sender, determine the idle level of each spine device based on the bandwidth utilization of each spine device port in the data center network, and select the spine device with the highest idle level as the target spine device.

[0049] Among them, such as Figure 2 The diagram shown illustrates the data transmission process of this application, including a server, leaf devices, and spine devices. The server can be either a data sender or a data receiver. When the server is a data sender, the leaf devices connected to the server are data receiving leaf devices. When the server is a data receiver, the leaf devices connected to the server are data receiving leaf devices.

[0050] In this application, the data center network refers to the POD (Point of Delivery) in the data center architecture, which is an independent spine-leaf networking unit consisting of a set of leaf devices and a set of spine devices. The devices within the unit are fully interconnected and adopt a unified routing and forwarding strategy. It is a scalable modular basic unit of the data center.

[0051] Optionally, the data sender can be a server.

[0052] Step 104: Return the loopback interface address of the target ridge device to the data sender, so that the data sender can encapsulate the data based on the loopback interface address and the elephant stream service data using a preset encapsulation method, obtain encapsulated data, and send the encapsulated data to the target ridge device corresponding to the loopback interface address through the data sending leaf device directly connected to the data sender.

[0053] The loopback interface is a virtual interface, typically configured as the device's local loopback address. In this invention, the Loopback0 address of the SPINE device (spine device) serves as the destination address for packets, used to receive and process tunnel packets from the server.

[0054] Optionally, the default encapsulation method can be IP-in-IP tunneling, a network tunneling technology that encapsulates an additional IP header on top of the original IP packet, transmitting the original packet as the tunnel payload. The destination IP of the tunnel is the IP address of the receiving end (in this invention, the loopback0 address of the SPINE device). When the data packet arrives at the receiving end, the encapsulated packet is decapsulated using tunnel decapsulation technology, the original packet is extracted, and forwarded according to its destination IP.

[0055] Step 106: Decapsulate the encapsulated data using the target spine device to obtain the elephant stream business data.

[0056] The target spine device identifies tunnel packets through a pre-configured tunnel termination function, strips off the outer IP header, and restores the original elephant flow service data, providing a basis for subsequent routing and forwarding based on the destination IP address.

[0057] Step 108: Send the elephant stream service data to the data receiving leaf device pointed to by the destination IP address in the elephant stream service data through the target spine device, so that the elephant stream service data is sent to the data receiver directly connected to the data receiving leaf device through the data receiving leaf device.

[0058] The target spine device queries the route based on the destination IP address carried by the decapsulated elephant stream service data, determines the corresponding receiving leaf device, and completes traffic forwarding; the data receiving leaf device, as the terminal access node, is responsible for distributing service data to the data receiver directly connected to it.

[0059] The aforementioned network path planning method, apparatus, device, and storage medium, in response to a spine device query request sent by any data sender, determines the idle level of each spine device based on the bandwidth utilization of each spine device port in the data center network, and selects the spine device with the highest idle level as the target spine device; returns the loopback interface address of the target spine device to the data sender, so that the data sender can encapsulate the data based on the loopback interface address and the elephant stream service data using a preset encapsulation method, obtain encapsulated data, and send the encapsulated data to the target spine device corresponding to the loopback interface address through a data sending leaf device directly connected to the data sender; the target spine device decapsulates the encapsulated data to obtain the elephant stream service data; and the target spine device sends the elephant stream service data to the data receiving leaf device pointed to by the destination IP address in the elephant stream service data, so that the data receiving leaf device sends the elephant stream service data to the data receiver directly connected to the data receiving leaf device. By combining the bandwidth utilization of each spine device port to determine the idle status and selecting the optimal target spine device, the transmission path can be dynamically planned according to the real-time network load, effectively balancing the traffic pressure of each network device and preventing problems such as uneven device load, local congestion, and wasted bandwidth resources caused by traditional fixed routing methods.

[0060] In one exemplary embodiment, prior to responding to a spine device query request sent by any data sender, the method further includes:

[0061] Configure the border gateway protocol for leaf and spine devices within the same network unit of the data center network.

[0062] Border Gateway Protocol (BGP) configuration refers to configuring Autonomous System Numbers (ASNs), route advertising rules, route reception policies, and default routes on leaf and spine devices. This enables network devices to automatically exchange routing information, establish forwarding paths, and automatically switch paths in case of failure, ensuring the normal transmission of elephant stream service data. An ASN is a unique identification number assigned to a group of network devices. A group of devices configured with the same ASN is considered an independent network unit. Based on this number, devices can distinguish their affiliation and thus send and receive routing information and manage data forwarding paths according to preset rules.

[0063] For example, a group of leaf devices and spine devices that are physically located and serve the same business cluster are grouped into the same network unit, while device groups corresponding to different data centers and different services are grouped into different network units. Before carrying out data transmission services, the relevant parameters of the border gateway protocol are uniformly configured for all leaf devices and spine devices within the same network unit, and the devices within the unit follow the same set of routing policies and autonomous system rules to achieve routing interoperability.

[0064] In this embodiment, by uniformly configuring the border gateway protocol for devices within the same network unit, a reliable routing and forwarding system can be built, simplifying operation and maintenance management, and laying the foundation for traffic forwarding and fault self-healing.

[0065] In one exemplary embodiment, border gateway protocol configuration includes:

[0066] Leaf devices connected to the same server are grouped into the same group, leaf devices in the same group are set to the same Autonomous System Number (ASN), and leaf devices in different groups are set to different ASN. The default route of each leaf device is directed to all spine devices. The spine devices are set to the same ASN, and a preset rule is configured on each spine device. The preset rule allows the receiving of routing information corresponding to its own ASN once.

[0067] Optionally, the default rule is allowas-in 1, which means that the spine device is allowed to receive routing information transmitted through its own autonomous system number once. When a link failure occurs between the spine device and the directly connected leaf device, it can obtain detour routes from other spine devices in the same autonomous system, which ensures path reachability in failure scenarios and strictly limits the number of route receptions to avoid routing loops.

[0068] For example, leaf devices are grouped and assigned Autonomous System Numbers (ASNs) according to the service to which the server belongs, enabling unified management and control of devices within the same service. All spine devices use the same ASN, simplifying core layer routing interaction logic. Leaf devices can distribute traffic to any normal spine device by relying on the default route pointing to all spine devices. AllowAs-in 1 is configured on each spine device.

[0069] In this embodiment, by configuring autonomous system numbers differently for leaf devices and spine devices, device group management and orderly route transmission can be achieved; by configuring default routes for leaf devices and route reception rules for spine devices, routing loops can be effectively avoided, and detour paths can be quickly generated when links or devices are abnormal, greatly improving the network's fault tolerance and self-healing capabilities.

[0070] In one exemplary embodiment, the method further includes:

[0071] Configure the preset decapsulation method corresponding to the preset encapsulation method of all spine devices on each spine device.

[0072] For example, a tunnel termination rule (preset decapsulation method) corresponding to the loopback address of all spine devices in this network unit is added to each spine device. The tunnel termination rule is used to decapsulate the packets encapsulated by IPinIP tunneling technology.

[0073] In this embodiment, by uniformly configuring global tunnel termination rules on all spine devices, any normal spine device can have the ability to decapsulate tunnel packets, avoiding packet parsing failures due to changes in forwarding nodes, and ensuring that data can still be parsed and forwarded normally after a fault switch.

[0074] In one exemplary embodiment, the method further includes:

[0075] If the target ridge device is faulty, a secondary target ridge device is determined from the ridge devices other than the target ridge device based on the equal-cost multipath routing strategy. The loopback interface address of the secondary target ridge device is returned to the data sender, so that the data sender can encapsulate the data based on the loopback interface address and the elephant stream service data using a preset encapsulation method, obtain encapsulated data, and send the encapsulated data to the secondary target ridge device corresponding to the loopback interface address through the data sending leaf device directly connected to the data sender. Based on the tunnel termination of the target ridge device pre-configured on the secondary target ridge device, the encapsulated data is decapsulated through the secondary target ridge device to obtain the elephant stream service data.

[0076] Optionally, in addition to selecting based on the equal-cost multipath routing policy, you can also reselect the most idle spine device other than the target spine device.

[0077] Equal cost multipath routing is a routing and forwarding mechanism. When multiple forwarding paths with the same routing cost and priority exist for the same destination address, the device can distribute traffic among the multiple paths; if one of the paths or forwarding devices fails, the traffic will automatically migrate to the remaining normal paths without manual intervention.

[0078] For example, during data transmission, the operating status of the target spine device is monitored in real time. Once a fault such as target spine device failure or port malfunction is detected, the device is stopped from being used as a forwarding node. The remaining normally operating spine devices within the current network unit are traversed, and a secondary target spine device is selected according to the equal-cost multi-path routing strategy. Its loopback interface address is then sent to the data sender. After receiving the new address, the data sender re-encapsulates the elephant stream service data through a tunnel. The data sending leaf device forwards the encapsulated data according to the new destination address. Even if the original destination address of the encapsulated packet is the faulty target spine device, the secondary target spine device, thanks to its pre-deployed global tunnel termination configuration, can still identify and parse the tunnel packet, decapsulate it to obtain the original service data, and execute the subsequent routing and forwarding process.

[0079] In this embodiment, by combining fault detection, equivalent multi-path routing, address retransmission and tunnel termination, proactive disaster recovery switching of forwarding nodes can be achieved, solving the transmission anomaly problem caused by the failure of a single spine device, and greatly improving the operational reliability of Elephant Stream service in complex fault scenarios.

[0080] In one exemplary embodiment, the method further includes:

[0081] If the communication link between the target ridge device and the data receiving leaf device pointed to by the destination IP address in the elephant stream service data is faulty, a secondary target ridge device is determined from the ridge devices other than the target ridge device based on the equal-cost multipath routing strategy. The elephant stream service data is sent from the target ridge device to the secondary target ridge device, and then sent through the secondary target ridge device to the data receiving leaf device pointed to by the destination IP address in the elephant stream service data, so that the elephant stream service data is sent through the data receiving leaf device to the data receiver directly connected to the data receiving leaf device.

[0082] For example, when a communication link between the target ridge device and the receiving leaf device fails due to disconnection or packet loss, the target ridge device queries its local routing table and selects an available secondary target ridge device as a relay node using an equal-cost multi-path routing strategy. The decapsulated elephant stream service data is first forwarded by the target ridge device to the secondary target ridge device, and then delivered via the normal link between the secondary target ridge device and the data receiving leaf device. Subsequently, the data receiving leaf device completes the data distribution to the data receiver.

[0083] In this embodiment, by building a link detour channel through an equal-cost multi-path routing strategy, the impact of single-point link failure can be effectively avoided, enabling seamless traffic switching and fully ensuring the continuous operation of high-traffic services such as Elephant Stream.

[0084] In an exemplary embodiment, a network path planning method includes: dividing leaf devices connected to the same server into the same group; setting leaf devices in the same group to the same Autonomous System Number (ASN); setting leaf devices in different groups to different ASN; and pointing the default route of each leaf device to all spine devices; setting spine devices to the same ASN; configuring a preset rule on each spine device, wherein the preset rule allows receiving routing information corresponding to its own ASN once; and configuring a preset decapsulation method corresponding to a preset encapsulation method for all spine devices on each spine device. In response to a spine device query request sent by any data sender, the idle level of each spine device is determined based on the bandwidth utilization of each spine device port in the data center network, and the spine device with the highest idle level is selected as the target spine device. The loopback interface address of the target spine device is returned to the data sender, so that the data sender can encapsulate the data based on the loopback interface address and the elephant stream service data using a preset encapsulation method, obtain encapsulated data, and send the encapsulated data to the target spine device corresponding to the loopback interface address through the data sending leaf device directly connected to the data sender. The target spine device decapsulates the encapsulated data to obtain the elephant stream service data. The target spine device sends the elephant stream service data to the data receiving leaf device pointed to by the destination IP address in the elephant stream service data, so that the data receiving leaf device can send the elephant stream service data to the data receiver directly connected to the data receiving leaf device. If the target ridge device is faulty, a secondary target ridge device is determined from the ridge devices other than the target ridge device based on the equal-cost multipath routing strategy. The loopback interface address of the secondary target ridge device is returned to the data sender, so that the data sender can encapsulate the data based on the loopback interface address and the elephant stream service data using a preset encapsulation method, obtain encapsulated data, and send the encapsulated data to the secondary target ridge device corresponding to the loopback interface address through the data sending leaf device directly connected to the data sender. Based on the tunnel termination of the target ridge device pre-configured on the secondary target ridge device, the encapsulated data is decapsulated through the secondary target ridge device to obtain the elephant stream service data. If the communication link between the target ridge device and the data receiving leaf device pointed to by the destination IP address in the elephant stream service data is faulty, a secondary target ridge device is determined from the ridge devices other than the target ridge device based on the equal-cost multipath routing strategy. The elephant stream service data is sent from the target ridge device to the secondary target ridge device, and then sent through the secondary target ridge device to the data receiving leaf device pointed to by the destination IP address in the elephant stream service data, so that the elephant stream service data is sent through the data receiving leaf device to the data receiver directly connected to the data receiving leaf device.

[0085] It should be understood that although the steps in the flowcharts of the above embodiments are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the above embodiments may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages in other steps. It is understood that the steps in different embodiments can be freely combined as needed, and all non-contradictory solutions formed by such combinations are within the scope of protection of this application.

[0086] In one exemplary embodiment, such as Figure 3 As shown, a network path planning device is provided, including: a selection module 301, an encapsulation module 302, a decapsulation module 303, and a transmission module 304, wherein:

[0087] The selection module is used to respond to a spine device query request sent by any data sender, determine the idle level of each spine device based on the bandwidth utilization of each spine device port in the data center network, and select the spine device with the highest idle level as the target spine device.

[0088] The encapsulation module is used to return the loopback interface address of the target spine device to the data sender, so that the data sender can encapsulate the data based on the loopback interface address and the elephant stream service data using a preset encapsulation method, obtain encapsulated data, and send the encapsulated data to the target spine device corresponding to the loopback interface address through the data sending leaf device directly connected to the data sender.

[0089] The decapsulation module is used to decapsulate the encapsulated data through the target spine device to obtain the elephant stream business data;

[0090] The sending module is used to send the elephant stream service data to the data receiving leaf device pointed to by the destination IP address in the elephant stream service data through the target spine device, so that the elephant stream service data is sent to the data receiver directly connected to the data receiving leaf device through the data receiving leaf device.

[0091] In one embodiment, the apparatus further includes a configuration module for:

[0092] Configure the border gateway protocol for leaf and spine devices within the same network unit of the data center network.

[0093] In one embodiment, the configuration module is further configured to:

[0094] Leaf devices connected to the same server are grouped into the same group, leaf devices in the same group are set to the same Autonomous System Number (ASN), and leaf devices in different groups are set to different ASN. The default route of each leaf device is directed to all spine devices. The spine devices are set to the same ASN, and a preset rule is configured on each spine device. The preset rule allows the receiving of routing information corresponding to its own ASN once.

[0095] In one embodiment, the configuration module is further configured to:

[0096] Configure the preset decapsulation method corresponding to the preset encapsulation method of all spine devices on each spine device.

[0097] In one embodiment, the apparatus further includes a fault handling module for:

[0098] If the target ridge device is faulty, a secondary target ridge device is determined from the ridge devices other than the target ridge device based on the equal-cost multipath routing strategy. The loopback interface address of the secondary target ridge device is returned to the data sender, so that the data sender can encapsulate the data based on the loopback interface address and the elephant stream service data using a preset encapsulation method, obtain encapsulated data, and send the encapsulated data to the secondary target ridge device corresponding to the loopback interface address through the data sending leaf device directly connected to the data sender. Based on the tunnel termination of the target ridge device pre-configured on the secondary target ridge device, the encapsulated data is decapsulated through the secondary target ridge device to obtain the elephant stream service data.

[0099] In one embodiment, the fault handling module is further configured to:

[0100] If the communication link between the target ridge device and the data receiving leaf device pointed to by the destination IP address in the elephant stream service data is faulty, a secondary target ridge device is determined from the ridge devices other than the target ridge device based on the equal-cost multipath routing strategy. The elephant stream service data is sent from the target ridge device to the secondary target ridge device, and then sent through the secondary target ridge device to the data receiving leaf device pointed to by the destination IP address in the elephant stream service data, so that the elephant stream service data is sent through the data receiving leaf device to the data receiver directly connected to the data receiving leaf device.

[0101] Each module in the aforementioned network path planning device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in the processor of a computer device in hardware form or independent of it, or stored in the memory of a computer device in software form, so that the processor can call and execute the operations corresponding to each module.

[0102] In one exemplary embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 4 As shown, this computer device includes a processor, memory, input / output interfaces (I / O), and a communication interface. The processor, memory, and I / O interfaces are connected via a system bus, and the communication interface is also connected to the system bus via the I / O interfaces. The processor provides computational and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and a database. The internal memory provides the environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The database stores large-scale business data. The I / O interfaces are used for exchanging information between the processor and external devices. The communication interface is used for communicating with external terminals via a network connection. When executed by the processor, the computer program implements a network path planning method.

[0103] Those skilled in the art will understand that Figure 4 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0104] In one exemplary embodiment, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to perform the following steps:

[0105] In response to a spine device query request sent by any data sender, the idle level of each spine device is determined based on the bandwidth utilization of each spine device port in the data center network, and the spine device with the highest idle level is selected as the target spine device.

[0106] The loopback interface address of the target ridge device is returned to the data sender, so that the data sender can encapsulate the data based on the loopback interface address and the elephant stream service data using a preset encapsulation method, obtain the encapsulated data, and send the encapsulated data to the target ridge device corresponding to the loopback interface address through the data sending leaf device directly connected to the data sender.

[0107] The encapsulated data is decapsulated by the target spine device to obtain the elephant stream business data;

[0108] The target ridge device sends the elephant stream service data to the data receiving leaf device pointed to by the destination IP address in the elephant stream service data, so that the elephant stream service data is sent to the data receiver directly connected to the data receiving leaf device through the data receiving leaf device.

[0109] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0110] Configure the border gateway protocol for all leaf devices and all spine devices within the same network unit of the data center network.

[0111] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0112] Leaf devices connected to the same server are grouped into the same group, leaf devices in the same group are set to the same Autonomous System Number (ASN), and leaf devices in different groups are set to different ASN. The default route of each leaf device is directed to all spine devices. The spine devices are set to the same ASN, and a preset rule is configured on each spine device. The preset rule allows the receiving of routing information corresponding to its own ASN once.

[0113] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0114] Configure the preset decapsulation method corresponding to the preset encapsulation method of all spine devices on each spine device.

[0115] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0116] If the target ridge device is faulty, a secondary target ridge device is determined from the ridge devices other than the target ridge device based on the equal-cost multipath routing strategy. The loopback interface address of the secondary target ridge device is returned to the data sender, so that the data sender can encapsulate the data based on the loopback interface address and the elephant stream service data using a preset encapsulation method, obtain encapsulated data, and send the encapsulated data to the secondary target ridge device corresponding to the loopback interface address through the data sending leaf device directly connected to the data sender. Based on the tunnel termination of the target ridge device pre-configured on the secondary target ridge device, the encapsulated data is decapsulated through the secondary target ridge device to obtain the elephant stream service data.

[0117] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0118] If the communication link between the target ridge device and the data receiving leaf device pointed to by the destination IP address in the elephant stream service data is faulty, a secondary target ridge device is determined from the ridge devices other than the target ridge device based on the equal-cost multipath routing strategy. The elephant stream service data is sent from the target ridge device to the secondary target ridge device, and then sent through the secondary target ridge device to the data receiving leaf device pointed to by the destination IP address in the elephant stream service data, so that the elephant stream service data is sent through the data receiving leaf device to the data receiver directly connected to the data receiving leaf device.

[0119] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, the computer program performing the following steps when executed by a processor:

[0120] In response to a spine device query request sent by any data sender, the idle level of each spine device is determined based on the bandwidth utilization of each spine device port in the data center network, and the spine device with the highest idle level is selected as the target spine device.

[0121] The loopback interface address of the target ridge device is returned to the data sender, so that the data sender can encapsulate the data based on the loopback interface address and the elephant stream service data using a preset encapsulation method, obtain the encapsulated data, and send the encapsulated data to the target ridge device corresponding to the loopback interface address through the data sending leaf device directly connected to the data sender.

[0122] The encapsulated data is decapsulated by the target spine device to obtain the elephant stream business data;

[0123] The target ridge device sends the elephant stream service data to the data receiving leaf device pointed to by the destination IP address in the elephant stream service data, so that the elephant stream service data is sent to the data receiver directly connected to the data receiving leaf device through the data receiving leaf device.

[0124] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0125] Configure the border gateway protocol for leaf and spine devices within the same network unit of the data center network.

[0126] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0127] Leaf devices connected to the same server are grouped into the same group, leaf devices in the same group are set to the same Autonomous System Number (ASN), and leaf devices in different groups are set to different ASN. The default route of each leaf device is directed to all spine devices. The spine devices are set to the same ASN, and a preset rule is configured on each spine device. The preset rule allows the receiving of routing information corresponding to its own ASN once.

[0128] In one embodiment, when the computer program is executed by a processor, it further performs the following steps:

[0129] Configure the preset decapsulation method corresponding to the preset encapsulation method of all spine devices on each spine device.

[0130] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0131] If the target ridge device is faulty, a secondary target ridge device is determined from the ridge devices other than the target ridge device based on the equal-cost multipath routing strategy. The loopback interface address of the secondary target ridge device is returned to the data sender, so that the data sender can encapsulate the data based on the loopback interface address and the elephant stream service data using a preset encapsulation method, obtain encapsulated data, and send the encapsulated data to the secondary target ridge device corresponding to the loopback interface address through the data sending leaf device directly connected to the data sender. Based on the tunnel termination of the target ridge device pre-configured on the secondary target ridge device, the encapsulated data is decapsulated through the secondary target ridge device to obtain the elephant stream service data.

[0132] In one embodiment, when the computer program is executed by a processor, it further performs the following steps:

[0133] If the communication link between the target ridge device and the data receiving leaf device pointed to by the destination IP address in the elephant stream service data is faulty, a secondary target ridge device is determined from the ridge devices other than the target ridge device based on the equal-cost multipath routing strategy. The elephant stream service data is sent from the target ridge device to the secondary target ridge device, and then sent through the secondary target ridge device to the data receiving leaf device pointed to by the destination IP address in the elephant stream service data, so that the elephant stream service data is sent through the data receiving leaf device to the data receiver directly connected to the data receiving leaf device.

[0134] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, performs the following steps:

[0135] In response to a spine device query request sent by any data sender, the idle level of each spine device is determined based on the bandwidth utilization of each spine device port in the data center network, and the spine device with the highest idle level is selected as the target spine device.

[0136] The loopback interface address of the target ridge device is returned to the data sender, so that the data sender can encapsulate the data based on the loopback interface address and the elephant stream service data using a preset encapsulation method, obtain the encapsulated data, and send the encapsulated data to the target ridge device corresponding to the loopback interface address through the data sending leaf device directly connected to the data sender.

[0137] The encapsulated data is decapsulated by the target spine device to obtain the elephant stream business data;

[0138] The target ridge device sends the elephant stream service data to the data receiving leaf device pointed to by the destination IP address in the elephant stream service data, so that the elephant stream service data is sent to the data receiver directly connected to the data receiving leaf device through the data receiving leaf device.

[0139] In one embodiment, when the computer program is executed by a processor, it further performs the following steps:

[0140] Configure the border gateway protocol for leaf and spine devices within the same network unit of the data center network.

[0141] In one embodiment, when the computer program is executed by a processor, it further performs the following steps:

[0142] Leaf devices connected to the same server are grouped into the same group, leaf devices in the same group are set to the same Autonomous System Number (ASN), and leaf devices in different groups are set to different ASN. The default route of each leaf device is directed to all spine devices. The spine devices are set to the same ASN, and a preset rule is configured on each spine device. The preset rule allows the receiving of routing information corresponding to its own ASN once.

[0143] In one embodiment, when the computer program is executed by a processor, it further performs the following steps:

[0144] Configure the preset decapsulation method corresponding to the preset encapsulation method of all spine devices on each spine device.

[0145] In one embodiment, when the computer program is executed by a processor, it further performs the following steps:

[0146] If the target ridge device is faulty, a secondary target ridge device is determined from the ridge devices other than the target ridge device based on the equal-cost multipath routing strategy. The loopback interface address of the secondary target ridge device is returned to the data sender, so that the data sender can encapsulate the data based on the loopback interface address and the elephant stream service data using a preset encapsulation method, obtain encapsulated data, and send the encapsulated data to the secondary target ridge device corresponding to the loopback interface address through the data sending leaf device directly connected to the data sender. Based on the tunnel termination of the target ridge device pre-configured on the secondary target ridge device, the encapsulated data is decapsulated through the secondary target ridge device to obtain the elephant stream service data.

[0147] In one embodiment, when the computer program is executed by a processor, it further performs the following steps:

[0148] If the communication link between the target ridge device and the data receiving leaf device pointed to by the destination IP address in the elephant stream service data is faulty, a secondary target ridge device is determined from the ridge devices other than the target ridge device based on the equal-cost multipath routing strategy. The elephant stream service data is sent from the target ridge device to the secondary target ridge device, and then sent through the secondary target ridge device to the data receiving leaf device pointed to by the destination IP address in the elephant stream service data, so that the elephant stream service data is sent through the data receiving leaf device to the data receiver directly connected to the data receiving leaf device.

[0149] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, artificial intelligence (AI) processors, etc., and are not limited to these.

[0150] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0151] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A network path planning method, characterized in that, The method includes: In response to a spine device query request sent by any data sender, the idle level of each spine device is determined based on the bandwidth utilization of each spine device port in the data center network, and the spine device with the highest idle level is selected as the target spine device. The loopback interface address of the target ridge device is returned to the data sender, so that the data sender can encapsulate the data based on the loopback interface address and the elephant stream service data using a preset encapsulation method, obtain encapsulated data, and send the encapsulated data to the target ridge device corresponding to the loopback interface address through the data sending leaf device directly connected to the data sender. The target ridge device decapsulates the encapsulated data to obtain elephant stream service data; The target ridge device sends the elephant stream service data to the data receiving leaf device pointed to by the destination IP address in the elephant stream service data, so that the data receiving leaf device sends the elephant stream service data to the data receiver directly connected to the data receiving leaf device.

2. The method according to claim 1, characterized in that, The response to a spine device query request sent by any data sender further includes: Configure the border gateway protocol for leaf and spine devices within the same network unit of the data center network.

3. The method according to claim 2, characterized in that, The border gateway protocol configuration includes: Leaf devices connected to the same server are grouped into the same group, leaf devices in the same group are set to the same autonomous system number, leaf devices in different groups are set to different autonomous system numbers, and the default route of each leaf device is pointed to all spine devices. Set the spine devices to have the same autonomous system number, and configure a preset rule on each spine device. The preset rule allows the device to receive routing information corresponding to its own autonomous system number once.

4. The method according to claim 1, characterized in that, The method further includes: Configure the preset decapsulation method corresponding to the preset encapsulation method of all spine devices on each spine device.

5. The method according to claim 4, characterized in that, The method further includes: If the target spine device is faulty, a secondary target spine device is determined from spine devices other than the target spine device based on the equal cost multipath routing strategy. The loopback interface address of the secondary target ridge device is returned to the data sender, so that the data sender can encapsulate the data based on the loopback interface address and the elephant stream service data using a preset encapsulation method, obtain encapsulated data, and send the encapsulated data to the secondary target ridge device corresponding to the loopback interface address through the data sending leaf device directly connected to the data sender. Based on the tunnel termination of the target ridge device pre-configured on the secondary target ridge device, the encapsulated data is decapsulated through the secondary target ridge device to obtain the elephant stream service data.

6. The method according to claim 1, characterized in that, The method further includes: If the communication link between the target ridge device and the data receiving leaf device pointed to by the destination IP address in the elephant stream service data is faulty, a secondary target ridge device is determined from the ridge devices other than the target ridge device based on the equal cost multipath routing strategy. The elephant stream service data is sent from the target ridge device to the secondary target ridge device, and then sent through the secondary target ridge device to the data receiving leaf device pointed to by the destination IP address in the elephant stream service data, so that the elephant stream service data is sent through the data receiving leaf device to the data receiver directly connected to the data receiving leaf device.

7. A network path planning device, characterized in that, The device includes: The selection module is used to respond to a spine device query request sent by any data sender, determine the idle level of each spine device based on the bandwidth utilization of each spine device port in the data center network, and select the spine device with the highest idle level as the target spine device. The encapsulation module is used to return the loopback interface address of the target ridge device to the data sender, so that the data sender can encapsulate the data based on the loopback interface address and elephant stream service data using a preset encapsulation method, obtain encapsulated data, and send the encapsulated data to the target ridge device corresponding to the loopback interface address through the data sending leaf device directly connected to the data sender. The decapsulation module is used to decapsulate the encapsulated data through the target spine device to obtain elephant stream service data; The sending module is used to send the elephant stream service data to the data receiving leaf device pointed to by the destination IP address in the elephant stream service data through the target spine device, so that the elephant stream service data is sent to the data receiver directly connected to the data receiving leaf device through the data receiving leaf device.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 6.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.

Images