CN118487993B - Network communication method, device and storage medium based on cloud network - Google Patents
Network communication method, device and storage medium based on cloud network Download PDFInfo
- Publication number
- CN118487993B CN118487993B CN202410718480.9A CN202410718480A CN118487993B CN 118487993 B CN118487993 B CN 118487993B CN 202410718480 A CN202410718480 A CN 202410718480A CN 118487993 B CN118487993 B CN 118487993B
- Authority
- CN
- China
- Prior art keywords
- target
- switch
- target server
- network
- spine
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 62
- 238000004891 communication Methods 0.000 title claims abstract description 56
- 230000003068 static effect Effects 0.000 claims abstract description 170
- 238000013507 mapping Methods 0.000 claims abstract description 22
- 230000004913 activation Effects 0.000 claims description 14
- 230000002159 abnormal effect Effects 0.000 claims description 13
- 238000004590 computer program Methods 0.000 claims description 10
- 230000002776 aggregation Effects 0.000 abstract description 17
- 238000004220 aggregation Methods 0.000 abstract description 17
- 230000005540 biological transmission Effects 0.000 abstract description 8
- 230000006855 networking Effects 0.000 description 12
- 238000012545 processing Methods 0.000 description 9
- 238000010586 diagram Methods 0.000 description 8
- 230000006870 function Effects 0.000 description 7
- 230000008569 process Effects 0.000 description 6
- 230000003287 optical effect Effects 0.000 description 5
- 238000011084 recovery Methods 0.000 description 4
- 230000000694 effects Effects 0.000 description 2
- 239000013307 optical fiber Substances 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 239000004065 semiconductor Substances 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 230000009977 dual effect Effects 0.000 description 1
- 238000009429 electrical wiring Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/24—Multipath
- H04L45/245—Link aggregation, e.g. trunking
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/28—Routing or path finding of packets in data switching networks using route fault recovery
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/74—Address processing for routing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/12—Avoiding congestion; Recovering from congestion
- H04L47/125—Avoiding congestion; Recovering from congestion by balancing the load, e.g. traffic engineering
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The embodiment of the disclosure provides a network communication method, device and storage medium based on a cloud network, wherein one static route corresponding to a plurality of IP addresses of a target server connected with the target leaf switch is obtained through any non-stacked target leaf switch in a leaf spine network structure, the static route comprises a static route prefix with unified IP addresses, the next hop is an interface IP address of the target server, whether the connection between the target server and the target leaf switch is normal or not is judged, if the connection is normal, the static route is transmitted to each spine switch, and after receiving network traffic matched with the target route, each spine switch transmits the network traffic to the target server through the target leaf switch according to a load balancing strategy. The method and the device can realize normal network traffic transmission of the unstacked cross-device aggregation network, avoid excessive address mapping table entries in the leaf switch and the spine switch, and simultaneously ensure load balance and link disaster tolerance in the network traffic transmission process.
Description
Technical Field
The embodiment of the disclosure relates to the technical field of computer and network communication, in particular to a network communication method, device and storage medium based on a cloud network.
Background
The existing cloud network networking scheme can be divided into a stacking mode cross-device dynamic aggregation networking scheme and a non-stacking mode cross-device dynamic aggregation networking scheme, wherein in the stacking mode cross-device dynamic aggregation networking scheme, a plurality of switch devices are connected through cables and then are combined together to be virtualized into one device, and switches in the non-stacking mode cross-device dynamic aggregation networking scheme are mutually independent and control planes are decoupled.
In the stacking mode cross-equipment dynamic aggregation networking scheme, a server is connected with a plurality of switches in a stacking mode, and if the server needs a plurality of IP addresses, only one static network segment or one dynamic network segment is configured on the plurality of switches in the stacking mode, and the next hop of the static network segment or the dynamic network segment points to the interface IP address of the server. However, in the non-stacking mode cross-device dynamic aggregation networking scheme, the server is connected with a plurality of mutually independent switches, if the server needs a plurality of IP addresses, the server cannot be realized by configuring one static network segment or one dynamic network segment, and address mapping table entries of each IP address generally need to be configured on the switch, so that the number of address mapping table entries on the switch is too large, and the problems of scale and stability are brought.
Disclosure of Invention
The embodiment of the disclosure provides a network communication method, equipment and a storage medium based on a cloud network, which are used for solving the problem of excessive address mapping table items on a switch in a non-stacking mode cross-equipment dynamic aggregation networking scheme.
In a first aspect, an embodiment of the present disclosure provides a network communication method based on a cloud network, where the cloud network adopts a leaf spine network structure, the leaf spine network structure includes a plurality of spine switches and a plurality of leaf switches, any one of the leaf switches is a non-stacked switch and is connected to each spine switch, and each server is connected to at least two leaf switches, the method includes:
Acquiring a static route corresponding to a plurality of IP addresses of a target server connected with a target leaf switch, wherein the static route comprises a static route prefix unified by the plurality of IP addresses, and the next hop is an interface IP address of the target server;
judging whether the connection between the target server and the target leaf switch is normal or not;
And if the connection between the target server and the target leaf switch is determined to be normal, transmitting the static route to each spine switch, so that each spine switch receives the network traffic of which the target route is matched with the static route and then transmits the network traffic to the target leaf switch according to a load balancing strategy, and the target leaf switch transmits the network traffic to the target server.
In a second aspect, an embodiment of the present disclosure provides a network communication device based on a cloud network, where the cloud network adopts a leaf spine network structure, the leaf spine network structure includes a plurality of spine switches and a plurality of leaf switches, any leaf switch is a non-stacked switch and is connected to each spine switch, each server is connected to at least two leaf switches, and the network communication device is any one target leaf switch of the plurality of leaf switches, and the network communication device includes:
The system comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is used for acquiring one static route corresponding to a plurality of IP addresses of a target server connected with the target leaf switch, the static route comprises a static route prefix unified by the plurality of IP addresses, and the next hop is an interface IP address of the target server;
the sensing unit is used for judging whether the connection between the target server and the target leaf switch is normal or not;
And the communication unit is used for transmitting the static route to each spine switch if the connection between the target server and the target leaf switch is determined to be normal, so that each spine switch receives the network traffic of which the target route is matched with the static route and then transmits the network traffic to the target leaf switch according to a load balancing strategy, and the target leaf switch transmits the network traffic to the target server.
In a third aspect, an embodiment of the present disclosure provides an electronic device comprising at least one processor and a memory;
the memory stores computer-executable instructions;
the at least one processor executes the computer-executable instructions stored by the memory, causing the at least one processor to perform the cloud network-based network communication method as described above in the first aspect and the various possible designs of the first aspect.
In a fourth aspect, embodiments of the present disclosure provide a computer readable storage medium, where computer executable instructions are stored, when executed by a processor, to implement the cloud network-based network communication method according to the first aspect and the various possible designs of the first aspect.
In a fifth aspect, embodiments of the present disclosure provide a computer program product, including computer-executable instructions, which when executed by a processor, implement the cloud network-based network communication method according to the first aspect and the various possible designs of the first aspect.
The network communication method, the device and the storage medium based on the cloud network provided by the embodiment of the disclosure acquire one static route corresponding to a plurality of IP addresses of a target server connected with the target leaf switch through any non-stacked target leaf switch in a leaf spine network structure, wherein the static route comprises a static route prefix with unified IP addresses, the next hop is an interface IP address of the target server, whether the connection between the target server and the target leaf switch is normal is judged, if the connection between the target server and the target leaf switch is determined to be normal, the static route is transmitted to each spine switch, so that the network flow matched with the static route is transmitted to the target leaf switch according to a load balancing strategy after the target route is received by each spine switch, and the network flow is transmitted to the target server by the target leaf switch. By configuring a static routing prefix for a plurality of IP addresses of a target server and sensing whether the connection between the target server and a target leaf switch is normal, normal network traffic transmission of a non-stacked cross-device aggregation network can be realized, excessive address mapping table entries in the leaf switch and a spine switch are avoided, and meanwhile, load balancing and link disaster recovery in the network traffic transmission process can be ensured.
Drawings
In order to more clearly illustrate the embodiments of the present disclosure or the solutions in the prior art, a brief description will be given below of the drawings that are needed in the embodiments or the description of the prior art, it being obvious that the drawings in the following description are some embodiments of the present disclosure, and that other drawings may be obtained from these drawings without inventive effort to a person of ordinary skill in the art.
Fig. 1 is a diagram illustrating a network architecture of a network communication method based on a cloud network according to an embodiment of the disclosure;
fig. 2 is a schematic flow chart of a network communication method based on a cloud network according to an embodiment of the disclosure;
fig. 3 is a block diagram of a network communication device based on a cloud network according to an embodiment of the present disclosure;
fig. 4 is a schematic hardware structure of an electronic device according to an embodiment of the disclosure.
Detailed Description
For the purposes of making the objects, technical solutions and advantages of the embodiments of the present disclosure more apparent, the technical solutions of the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present disclosure, and it is apparent that the described embodiments are some embodiments of the present disclosure, but not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art without inventive effort, based on the embodiments in this disclosure are intended to be within the scope of this disclosure.
Compared with the traditional stacked dynamic aggregation networking scheme, the non-stacked cross-device dynamic aggregation networking scheme has the following advantages:
1) The switches are mutually independent, the control planes are decoupled, and the operation and maintenance risks are reduced;
2) No synchronization address mapping table entries (such as MAC/ARP/ND table entries) are required between switches;
3) The switches can realize double activities without interconnection links;
additional functions are required as follows:
1) Requiring the server to support dual address resolution (Address Resolution Protocol, ARP) and/or neighbor discovery (Neighbor Discovery, ND) requests, i.e., to be sent simultaneously to a plurality of switches connected thereto;
2) In a Spine-to-Spine network structure (Spine-to-Leaf), a Spine switch is imported by way of ARP/ND to border gateway protocol (Border Gateway Protocol, BGP) routing to achieve load sharing.
In the stacking mode cross-equipment dynamic aggregation networking scheme, a server is connected with a plurality of switches in a stacking mode, and if the server needs a plurality of IP addresses, only one static network segment or one dynamic network segment is configured on the plurality of switches in the stacking mode, and the next hop of the static network segment or the dynamic network segment points to the interface IP address of the server.
In the non-stacking mode cross-device dynamic aggregation networking scheme, a server is connected with a plurality of mutually independent switches, if the server needs a plurality of IP addresses, the implementation is limited by the prior art, and the implementation cannot be realized by configuring a static network segment or a dynamic network segment, because the leaf switches connected with the server are mutually independent, if the static network segment or the dynamic network segment is configured in the leaf switch, the spine switch can be uploaded, but the spine switch can not sense whether the leaf switch is normally connected with the server or not, if the connection is abnormal, the spine switch still needs to send network traffic sent to the server to the leaf switch which is abnormally connected with the server, so that the part of network traffic is lost. It is therefore often necessary to configure address mapping entries for individual IP addresses on the switch.
In one scheme, the multiple IP addresses of the server send ARP and/or ND requests to leaf switches connected to the server independently, and the ARP and/or ND requests are led to each spine switch by means of ARP/ND to BGP routes, for example, assuming that each leaf switch is connected to 40 servers, and each server needs 256 IP addresses, an address mapping table (ARP/ND table) of each leaf switch is 40×256=10240 entries, and if each spine switch in a group of spine switches is connected to 32 leaf switches, a routing table required by each spine switch is 10240×32= 327680, which results in excessive address mapping tables on the switches, and causes problems of scale and stability.
In order to solve the technical problems, the disclosure provides a network communication method based on a cloud network, which is characterized in that a static route corresponding to a plurality of IP addresses of a target server connected with the target leaf switch is obtained through any non-stacked target leaf switch in a leaf spine network structure, wherein the static route comprises a static route prefix with unified IP addresses, the next hop is an interface IP address of the target server, whether the connection between the target server and the target leaf switch is normal is judged, if the connection between the target server and the target leaf switch is determined to be normal, the static route is transmitted to each spine switch, so that the network flow matched with the static route is transmitted to the target leaf switch according to a load balancing strategy after each spine switch receives the network flow, and the network flow is transmitted to the target server by the target leaf switch. By configuring a static routing prefix for a plurality of IP addresses of a target server and sensing whether the connection between the target server and a target leaf switch is normal, normal network traffic transmission of a non-stacked cross-device aggregation network can be realized, excessive address mapping table entries in the leaf switch and a spine switch are avoided, and meanwhile, load balancing and link disaster recovery in the network traffic transmission process can be ensured.
The cloud network-based network communication method provided by the present disclosure is applied to a non-stacked cross-device aggregation network, for example, a Spine-Leaf network structure (Spine-Leaf) shown in fig. 1, where the Spine-Leaf network structure includes a Spine switch and a plurality of Leaf switches, any one of the Leaf switches is a non-stacked switch (there is no connection between the Leaf switches), and is connected to each Spine switch, and each server is connected to at least two Leaf switches. The network communication method based on the cloud network is characterized in that an execution main body of the network communication method based on the cloud network is any one target leaf switch of a plurality of leaf switches, one static route corresponding to a plurality of IP addresses of a target server connected with the target leaf switch can be obtained, wherein the static route comprises a static route prefix with unified IP addresses, the next hop is an interface IP address of the target server, whether connection between the target server and the target leaf switch is normal or not is judged, if the connection between the target server and the target leaf switch is determined to be normal, the static route is transmitted to each spine switch, so that each spine switch receives network traffic matched with the static route and then transmits the network traffic to the target leaf switch according to a load balancing strategy, and the target leaf switch transmits the network traffic to the target server.
The network communication method based on the cloud network of the present disclosure will be described in detail with reference to specific embodiments.
Referring to fig. 2, fig. 2 is a flowchart of a network communication method based on a cloud network according to an embodiment of the disclosure. In the method of this embodiment, a Spine-to-Spine network structure (Spine-to-Leaf) is used in the cloud network, where the Spine-to-Spine network structure includes a plurality of Spine (Spine) switches and a plurality of Leaf (Leaf) switches, any of the Leaf switches is a non-stacked switch and is connected to each Spine switch, each server is connected to at least two Leaf switches, and the method of this embodiment may be applied to a target Leaf switch in the Spine-to-Spine network structure, where the target Leaf switch is any one of the plurality of Leaf switches, and the network communication method based on the cloud network includes:
S201, acquiring a static route corresponding to a plurality of IP addresses of a target server connected with a target leaf switch, wherein the static route comprises a static route prefix unified by the plurality of IP addresses, the next hop is an interface IP address of the target server, and the target leaf switch is any one of the plurality of leaf switches.
In this embodiment, the target server is any server connected to the target leaf switches, if the target server needs multiple IP addresses, one static route corresponding to the multiple IP addresses may be configured on each target leaf switch connected to the target server, where the static routes corresponding to the multiple IP addresses include a unified static route prefix, and the next hop is a static route of an interface IP address of the target server, where an interface of the target server is an aggregation (Bond) interface connected to at least two target leaf switches. The purpose of the static route prefix is that network traffic for which the target route matches the static route prefix may all be sent to the target server.
For example, if the target server needs 256 addresses based on the first internet protocol, the target server is connected to two target leaf switches, and both target leaf switches need to configure static routes of the network based on the first internet protocol corresponding to the multiple IPR addresses of the target server, where the first internet protocol may be IPv4, that is, the target server needs 256 IPv4 addresses, one Prefix may be configured as/24, the next hop is a static route of the aggregate interface IP address of the target server, and if the target server needs 256 addresses based on the second internet protocol, the target server is connected to two target leaf switches, both target leaf switches need to configure static routes of the network based on the second internet protocol corresponding to the multiple IPR addresses of the target server, where the second internet protocol may be IPv6, that is, the target server needs 256 IPv6 addresses, one Prefix may be configured as/120, and the next hop is a static route of the aggregate interface IP address of the target server. In addition, the target server does not conflict between the requirements based on the first internet protocol address and the second internet protocol address, namely the target leaf switch can simultaneously configure the static route of the network based on the first internet protocol and the static route of the network based on the second internet protocol corresponding to a plurality of IP addresses. Of course, the first internet protocol is not limited to IPv4, and the second internet protocol is not limited to IPv6, and further, in this embodiment, more internet protocols may be supported at the same time, for example, a third internet protocol, a fourth internet protocol, etc. may be supported on the basis of the first internet protocol and the second internet protocol.
S202, judging whether the connection between the target server and the target leaf switch is normal or not.
In this embodiment, the target leaf switch may sense whether the connection between the target server and the target leaf switch is normal, that is, determine whether the next hop in the static route is reachable, and further, inform each spine switch whether to transmit data to the target server through the target leaf switch, so as to avoid that each spine switch still transmits data to the target server through the target leaf switch after the connection between the target server and the target leaf switch is abnormal, thereby causing data loss.
Optionally, the target leaf switch determines whether the connection between the target server and the target leaf switch is normal, specifically, whether an address resolution (Address Resolution Protocol, ARP) and/or neighbor discovery (Neighbor Discovery, ND) request sent by the target server is received, and if the target leaf switch receives the ARP and/or ND request sent by the target server, determines that the connection between the target server and the target leaf switch is normal. The method comprises the steps of judging whether an ARP and/or ND request sent by a target server is received or not, judging in real time or judging at specific time intervals, and if the ARP and/or ND request sent by the target server is not received for more than a preset time, determining that the connection between the target server and a target leaf switch is abnormal. The ARP request is directed to the IPv4 (i.e. the first internet protocol) network, and is used for resolving an IP address into a MAC address, and the ND request is directed to the IPv6 (i.e. the second internet protocol) network, and may be used for resolving an IP address into a MAC address, and may also be used for reachability detection, etc.
Optionally, if the target leaf switch only receives the ARP request sent by the target server, it is determined that the IPv4 network connection between the target server and the target leaf switch is normal, or if the target leaf switch only receives the ND request sent by the target server, it is determined that the IPv6 network connection between the target server and the target leaf switch is normal, or if the target leaf switch receives the ARP request and the ND request sent by the target server, it is determined that the IPv4 network connection and the IPv6 network connection between the target server and the target leaf switch are normal.
Optionally, if the target leaf switch receives the ARP and/or ND request sent by the target server, the host address mapping table (ARP/ND table) of the target leaf switch may have an ARP/ND table (address resolution and/or neighbor discovery address mapping table) corresponding to the target server, where the ARP/ND table is a mapping table between an IP address and an MAC address, so it may be determined whether the ARP/ND table of the target leaf switch has an ARP/ND table corresponding to the target server, and if so, it is determined that the ARP and/or ND request sent by the target server is received. Further, if the ARP list item corresponding to the target server exists, it is determined that the ARP request sent by the target server is received, and if the ND list item corresponding to the target server exists, it is determined that the ND request sent by the target server is received.
And S203, if the connection between the target server and the target leaf switch is determined to be normal, transmitting the static route to each spine switch, so that each spine switch receives the network traffic of which the target route is matched with the static route and then transmits the network traffic to the target leaf switch according to a load balancing strategy, and the target leaf switch transmits the network traffic to the target server.
In this embodiment, if it is determined that the connection between the target server and the target leaf switch is normal, the static route described above may be dynamically transmitted to each spine switch.
Alternatively, the static route may be converted into a border gateway protocol (Border Gateway Protocol, BGP) route and then transmitted to each spine switch, where the BGP route is used for dynamic, flexible and extensible route management of each spine switch, and specifically, the BGP route may be transmitted to a BGP process of each spine switch, and added to a BGP table, and based on the BGP table, the spine switch may learn network topology information, perform route selection, and so on.
Furthermore, after each spine switch receives the static route, it can know which target leaf switches are normally connected with the target server, and when each spine switch receives the network traffic (i.e. the network traffic which needs to be sent to the target server) with the target route matched with the static route, the network traffic can be transmitted to the target leaf switch which is normally connected with the target server according to the load balancing policy, and then the target leaf switches transmit the network traffic to the target server, wherein the network traffic can be any message or data which needs to be sent to the target server.
Taking the Spine-Leaf network structure shown in fig. 1 as an example, taking a server 1 as a target server, connecting the server 1 with a Leaf switch 1-1 and a Leaf switch 1-2, wherein each Leaf switch 1-1 and each Leaf switch 1-2 are respectively connected with a Spine switch 1-4, configuring one static route corresponding to a plurality of IP addresses of the server 1 on the Leaf switch 1-1 and the Leaf switch 1-2, and if the server 1 is normally connected with the Leaf switch 1-1 and the Leaf switch 1-2, respectively transmitting the static routes of the server 1 to the Spine switch 1-4 by the Leaf switch 1-1 and the Leaf switch 1-2, so that the Spine switch 1-4 can know that the server 1 is normally connected with the Leaf switch 1-1 and the Leaf switch 1-2;
Assuming that the server 3 needs to transmit network traffic to the server 1, and that the connection between the server 3 and the leaf switches 2-1 and 2-2 is normal, the network traffic is transmitted to the spine switches 1-4 through the leaf switches 2-1 and 2-2 according to a load balancing policy, for example, half of the network traffic is transmitted to the spine switches 1-4 through the leaf switches 2-1 and equally divided into 4 parts, the other half of the network traffic is transmitted to the spine switches 1-4 through the leaf switches 2-2 and equally divided into 4 parts, respectively, and the spine switches 1-4 are known that the server 1 is normally connected with the leaf switches 1-1 and 1-2, namely, the server 1 is reachable through the leaf switches 1-1 and 1-2, so that the spine switches 1-4 transmit the network traffic received by each to the server 1 through the leaf switches 1-1 and 1-2 according to the load balancing policy, for example, the spine switches 1 equally divide the network traffic received by the spine switches into 2 parts and equally divided into 2 parts, respectively, and then transmit the network traffic to the leaf switches 1-2 and the specific IP addresses to the server 1-2. The above process is in a load balancing state.
It should be noted that, the server may perceive that the connection with the leaf switch is normal, and in the process that the server 3 transmits the network traffic to the spine switch 1-4 through the leaf switch 2-1 and the leaf switch 2-2 according to the load balancing policy, if the server 3 perceives that the connection with the leaf switch 2-1 and the leaf switch 2-2 is normal, the load balancing policy is executed, and if the server 3 perceives that the connection with the leaf switch 2-1 is normal and the connection with the leaf switch 2-2 is abnormal, the network traffic is transmitted to the spine switch 1-4 near through the leaf switch 2-1.
In addition, on the basis of any of the above embodiments, if it is determined that the connection between the target server and the target leaf switch is abnormal, the target leaf switch may dynamically withdraw the static route from each spine switch, so that each spine switch stops transmitting to the target leaf switch after receiving the network traffic of which the target route matches the static route.
For example, in the example of the Spine-Leaf network structure shown in fig. 1, if one of the server 1 and the Leaf switch 1-2 is connected normally, and the other is connected abnormally, for example, the server 1 and the Leaf switch 1-1 are connected normally, and the server 1 and the Leaf switch 1-2 are connected abnormally, the Leaf switch 1-1 may transmit the static routes of the server 1to the Spine switches 1-4 respectively, so that the Spine switches 1-4 can know that the server 1 and the Leaf switch 1-1 are connected normally, and the Leaf switch 1-2 may withdraw the static routes of the server 1 from the Spine switches 1-4 respectively, so that the Spine switches 1-4 can know that the server 1 and the Leaf switch 1-2 are connected abnormally;
Further, it is also assumed that the server 3 needs to transmit network traffic to the server 1, and that the server 3 is normally connected to the leaf switches 2-1 and 2-2, and transmits network traffic to the spine switches 1-4, and that the spine switches 1-4 are all known that the server 1 is normally connected to the leaf switch 1-1, and that the connection to the leaf switch 1-2 is abnormal, that is, the server 1 can only be reached through the leaf switch 1-1, so that the spine switches 1-4 transmit the network traffic received by each to the server 1 through the leaf switch 1-1, and stop transmitting to the server 1 through the leaf switch 1-2, and further transmit to the specific IP address from the server 1. The above process is disaster recovery state.
In addition, if it is determined that all the target leaf switches connected to the target server are abnormal in connection with the target server, for example, in the above example, the connection between the server 1 and the leaf switches 1-1 and the connection between the leaf switches 1-2 are abnormal, each spine switch cannot transmit network traffic to the target server through any one of the target leaf switches, that is, the target server is in an unavailable state.
According to the cloud network-based network communication method, one static route corresponding to a plurality of IP addresses of a target server connected with the target leaf switch is obtained through any non-stacked target leaf switch in a leaf spine network structure, wherein the static route comprises a plurality of static route prefixes with unified IP addresses, the next hop is an interface IP address of the target server, whether connection between the target server and the target leaf switch is normal or not is judged, if the connection between the target server and the target leaf switch is determined to be normal, the static route is transmitted to each spine switch, so that the network traffic matched with the static route is transmitted to the target leaf switch according to a load balancing strategy after each spine switch receives the network traffic, and the network traffic is transmitted to the target server by the target leaf switch. By configuring a static routing prefix for a plurality of IP addresses of a target server and sensing whether the connection between the target server and a target leaf switch is normal, normal network traffic transmission of a non-stacked cross-device aggregation network can be realized, excessive address mapping table entries in the leaf switch and a spine switch are avoided, and meanwhile, load balancing and link disaster recovery in the network traffic transmission process can be ensured.
On the basis of any one of the embodiments, when determining that the connection between the target server and the target leaf switch is normal, and transmitting the static route to each spine switch, if it is determined that the connection between the target server and the target leaf switch is normal, transmitting the static route of the IPv4 network corresponding to a plurality of IP addresses of the target server to each spine switch, so that each spine switch can know that the connection between the IPv4 network between the target server and the target leaf switch is normal, and/or if it is determined that the connection between the target server and the target leaf switch is normal, transmitting the static route of the IPv6 network corresponding to a plurality of IP addresses of the target server to each spine switch, so that each spine switch can know that the connection between the target server and the target leaf switch is normal.
Further, after the target leaf switch transmits the IPv4 network static route corresponding to the plurality of IP addresses of the target server to each spine switch, if each spine switch receives the IPv4 network traffic (i.e., the IPv4 network traffic that needs to be sent to the target server) whose destination route matches the above-mentioned IPv4 network static route, each spine switch transmits the respective received IPv4 network traffic to the target leaf switch according to the load balancing policy, and the target leaf switch transmits the respective IPv6 network traffic to the target server, and/or after the target leaf switch transmits the IPv6 network static route corresponding to the plurality of IP addresses of the target server to each spine switch, if each spine switch receives the IPv6 network traffic (i.e., the IPv6 network traffic that needs to be sent to the target server) whose destination route matches the above-mentioned IPv6 network static route, each spine switch transmits the respective received IPv6 network traffic to the target leaf switch according to the load balancing policy, and the target leaf switch transmits the respective received IPv6 network traffic to the target server. The procedure described in this embodiment is similar to the above embodiment, and only IPv4 network traffic and IPv6 network traffic are distinguished.
On the basis of any one of the above embodiments, when the target leaf switch determines whether the connection between the target server and the target leaf switch is normal, the target leaf switch may set the activation state of the static route according to the determination result of whether the connection between the target server and the target leaf switch is normal, for example, if the connection between the target server and the target leaf switch is normal, the static route is set to be the activation state, if the connection between the target server and the target leaf switch is abnormal, the static route is set to be the non-activation state, further, whether the static route is transmitted to each spine switch or whether the static route is withdrawn from each spine switch may be controlled according to the activation state of the static route, specifically, if the static route is the activation state, the static route is transmitted to each spine switch, and if the static route is the non-activation state, the static route is withdrawn from each spine switch.
Corresponding to the network communication method based on the cloud network in the above embodiment, fig. 3 is a block diagram of a network communication device based on the cloud network according to the embodiment of the present disclosure. For ease of illustration, only portions relevant to embodiments of the present disclosure are shown. The cloud network adopts a leaf spine network structure, the leaf spine network structure comprises a plurality of spine switches and a plurality of leaf switches, any leaf switch is a non-stacked switch and is respectively connected with each spine switch, each server is connected with at least two leaf switches, the network communication equipment is any target leaf switch in the plurality of leaf switches, and referring to fig. 3, the cloud network-based network communication equipment 300 comprises an acquisition unit 301, a sensing unit 302 and a communication unit 303.
An obtaining unit 301, configured to obtain one static route corresponding to a plurality of IP addresses of a target server connected to the target leaf switch, where the static route includes a static route prefix unified by the plurality of IP addresses, and a next hop is an interface IP address of the target server;
a sensing unit 302, configured to determine whether a connection between the target server and the target leaf switch is normal;
And the communication unit 303 is configured to transmit the static route to each spine switch if it is determined that the connection between the target server and the target leaf switch is normal, so that each spine switch receives the network traffic of which the destination route matches with the static route, and then transmits the network traffic to the target leaf switch according to a load balancing policy, and the target leaf switch transmits the network traffic to the target server.
In one or more embodiments of the present disclosure, the communication unit 303 is further configured to:
And if the connection between the target server and the target leaf switch is abnormal, the static route is withdrawn from each spine switch, so that each spine switch stops transmitting to the target leaf switch after receiving network traffic of which the target route is matched with the static route.
In one or more embodiments of the present disclosure, the sensing unit 302 is configured, when determining whether the connection between the target server and the target leaf switch is normal, to:
judging whether an address resolution and/or neighbor discovery request sent by the target server is received or not;
And if the address resolution and/or neighbor discovery request sent by the target server is received, determining that the connection between the target server and the target leaf switch is normal.
In one or more embodiments of the present disclosure, the sensing unit 302 is configured, when determining whether an address resolution and/or neighbor discovery request sent by the target server is received, to:
judging whether an address resolution and/or neighbor discovery address mapping table item corresponding to the target server exists in the host address mapping table item, and if so, determining that an address resolution and/or neighbor discovery request sent by the target server is received.
In one or more embodiments of the present disclosure, the sensing unit 302 is configured to, when receiving an address resolution and/or neighbor discovery request sent by the target server, determine that a connection between the target server and the target leaf switch is normal:
If only the address resolution request sent by the target server is received, determining that the connection between the target server and the target leaf switch based on the first Internet protocol network is normal, or
If only the neighbor discovery request sent by the target server is received, determining that the connection between the target server and the target leaf switch based on the second Internet protocol network is normal, or
And if the address resolution request and the neighbor discovery request sent by the target server are received, determining that the connection between the target server and the target leaf switch based on the first Internet protocol network and the connection between the target server and the target leaf switch based on the second Internet protocol network are normal.
In one or more embodiments of the present disclosure, the communication unit 303, when determining that the connection between the target server and the target leaf switch is normal, transmits the static route to each spine switch, is configured to:
If it is determined that the first IP-based network connection between the target server and the target leaf switch is normal, transmitting a first IP-based network static route corresponding to a plurality of IP addresses of the target server to each spine switch, and/or
And if the second internet protocol network-based connection between the target server and the target leaf switch is determined to be normal, transmitting the second internet protocol network-based static route corresponding to a plurality of IP addresses of the target server to each spine switch.
In one or more embodiments of the present disclosure, the communication unit 303 is further configured to:
after a first internet protocol network-based static route corresponding to a plurality of IP addresses of the target server is transmitted to each spine switch, receiving first internet protocol network-based traffic matched with the first internet protocol network-based static route by each spine switch according to a destination route transmitted by a load balancing strategy, and transmitting the first internet protocol network-based traffic to the target server, and/or
And after the second internet protocol network-based static route corresponding to the plurality of IP addresses of the target server is transmitted to each spine switch, receiving second internet protocol network-based traffic matched with the second internet protocol network-based static route by each spine switch according to the destination route transmitted by the load balancing strategy, and transmitting the second internet protocol network-based traffic to the target server.
In one or more embodiments of the present disclosure, the communication unit 303, when transmitting the static route to each spine switch, is configured to:
And converting the static route into a border gateway protocol route and transmitting the border gateway protocol route to each spine switch.
In one or more embodiments of the present disclosure, the sensing unit 302 is further configured to:
And setting an activation state of the static route according to a judging result of whether the connection between the target server and the target leaf switch is normal, wherein the activation state is used for indicating to transmit the static route to each spine switch or withdraw the static route from each spine switch.
The device provided in this embodiment may be used to execute the technical solution of the foregoing method embodiment, and its implementation principle and technical effects are similar, and this embodiment will not be described herein again.
Referring to fig. 4, there is shown a schematic structural diagram of an electronic device 400 suitable for use in implementing embodiments of the present disclosure, which electronic device 400 may be a terminal device or a server. The terminal device may include, but is not limited to, a mobile terminal such as a mobile phone, a notebook computer, a digital broadcast receiver, a Personal Digital Assistant (PDA) or the like, a tablet computer (Portable Android Device) or the like, a Portable Multimedia Player (PMP) or the like, a car-mounted terminal (e.g., car navigation terminal) or the like, and a fixed terminal such as a digital TV or a desktop computer or the like. The electronic device shown in fig. 4 is merely an example and should not be construed to limit the functionality and scope of use of the disclosed embodiments.
As shown in fig. 4, the electronic apparatus 400 may include a processing device (e.g., a central processing unit, a graphics processor, etc.) 401 that may perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 402 or a program loaded from a storage device 408 into a random access Memory (Random Access Memory RAM) 403. In the RAM 403, various programs and data necessary for the operation of the electronic device 400 are also stored. The processing device 401, the ROM 402, and the RAM 403 are connected to each other by a bus 404. An input/output (I/O) interface 405 is also connected to bus 404.
In general, devices may be connected to I/O interface 405 including input devices 406 such as a touch screen, touch pad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc., output devices 407 including, for example, a Liquid CRYSTAL DISPLAY (LCD), speakers, vibrator, etc., storage devices 408 including, for example, magnetic tape, hard disk, etc., and communications devices 409. The communication means 409 may allow the electronic device 400 to communicate with other devices wirelessly or by wire to exchange data. While fig. 4 shows an electronic device 400 having various means, it is to be understood that not all of the illustrated means are required to be implemented or provided. More or fewer devices may be implemented or provided instead.
In particular, according to embodiments of the present disclosure, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method shown in the flowcharts. In such an embodiment, the computer program may be downloaded and installed from a network via communications device 409, or from storage 408, or from ROM 402. The above-described functions defined in the methods of the embodiments of the present disclosure are performed when the computer program is executed by the processing device 401.
It should be noted that the computer readable medium described in the present disclosure may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of a computer-readable storage medium may include, but are not limited to, an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this disclosure, a computer-readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present disclosure, however, the computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with the computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to electrical wiring, fiber optic cable, RF (radio frequency), and the like, or any suitable combination of the foregoing.
The computer readable medium may be included in the electronic device or may exist alone without being incorporated into the electronic device.
The computer-readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to perform the methods shown in the above-described embodiments.
Computer program code for carrying out operations of the present disclosure may be written in one or more programming languages, including an object oriented programming language such as Java, smalltalk, C ++ and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any kind of network, including a local area network (Local Area Network, LAN for short) or a wide area network (Wide Area Network, WAN for short), or may be connected to an external computer (e.g., through the internet using an internet service provider).
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units involved in the embodiments of the present disclosure may be implemented by means of software, or may be implemented by means of hardware. The name of the unit does not in any way constitute a limitation of the unit itself, for example the first acquisition unit may also be described as "unit acquiring at least two internet protocol addresses".
The functions described above herein may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic that may be used include Field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), systems-on-a-chip (SOCs), complex Programmable Logic Devices (CPLDs), and the like.
In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
According to a first aspect, according to one or more embodiments of the present disclosure, there is provided a network communication method based on a cloud network, the cloud network adopting a leaf spine network structure, the leaf spine network structure including a plurality of spine switches and a plurality of leaf switches, any leaf switch being a non-stacked switch and being connected to each spine switch, respectively, each server being connected to at least two leaf switches, the method comprising:
Acquiring a static route corresponding to a plurality of IP addresses of a target server connected with a target leaf switch, wherein the static route comprises a static route prefix unified by the plurality of IP addresses, and the next hop is an interface IP address of the target server;
judging whether the connection between the target server and the target leaf switch is normal or not;
And if the connection between the target server and the target leaf switch is determined to be normal, transmitting the static route to each spine switch, so that each spine switch receives the network traffic of which the target route is matched with the static route and then transmits the network traffic to the target leaf switch according to a load balancing strategy, and the target leaf switch transmits the network traffic to the target server.
According to one or more embodiments of the present disclosure, the method further comprises:
And if the connection between the target server and the target leaf switch is abnormal, the static route is withdrawn from each spine switch, so that each spine switch stops transmitting to the target leaf switch after receiving network traffic of which the target route is matched with the static route.
According to one or more embodiments of the present disclosure, the determining whether the connection between the target server and the target leaf switch is normal includes:
judging whether an address resolution and/or neighbor discovery request sent by the target server is received or not;
And if the address resolution and/or neighbor discovery request sent by the target server is received, determining that the connection between the target server and the target leaf switch is normal.
According to one or more embodiments of the present disclosure, the determining whether an address resolution and/or neighbor discovery request sent by the target server is received includes:
judging whether an address resolution and/or neighbor discovery address mapping table item corresponding to the target server exists in the host address mapping table item, and if so, determining that an address resolution and/or neighbor discovery request sent by the target server is received.
According to one or more embodiments of the present disclosure, the determining that the connection between the target server and the target leaf switch is normal if the address resolution and/or neighbor discovery request sent by the target server is received includes:
If only the address resolution request sent by the target server is received, determining that the connection between the target server and the target leaf switch based on the first Internet protocol network is normal, or
If only the neighbor discovery request sent by the target server is received, determining that the connection between the target server and the target leaf switch based on the second Internet protocol network is normal, or
And if the address resolution request and the neighbor discovery request sent by the target server are received, determining that the connection between the target server and the target leaf switch based on the first Internet protocol network and the connection between the target server and the target leaf switch based on the second Internet protocol network are normal.
According to one or more embodiments of the present disclosure, the transmitting the static route to each spine switch if it is determined that the connection between the target server and the target leaf switch is normal includes:
If it is determined that the first IP-based network connection between the target server and the target leaf switch is normal, transmitting a first IP-based network static route corresponding to a plurality of IP addresses of the target server to each spine switch, and/or
And if the second internet protocol network-based connection between the target server and the target leaf switch is determined to be normal, transmitting the second internet protocol network-based static route corresponding to a plurality of IP addresses of the target server to each spine switch.
According to one or more embodiments of the present disclosure, the method further comprises:
after a first internet protocol network-based static route corresponding to a plurality of IP addresses of the target server is transmitted to each spine switch, receiving first internet protocol network-based traffic matched with the first internet protocol network-based static route by each spine switch according to a destination route transmitted by a load balancing strategy, and transmitting the first internet protocol network-based traffic to the target server, and/or
And after the second internet protocol network-based static route corresponding to the plurality of IP addresses of the target server is transmitted to each spine switch, receiving second internet protocol network-based traffic matched with the second internet protocol network-based static route by each spine switch according to the destination route transmitted by the load balancing strategy, and transmitting the second internet protocol network-based traffic to the target server.
In accordance with one or more embodiments of the present disclosure, the transmitting the static route to each spine switch includes:
And converting the static route into a border gateway protocol route and transmitting the border gateway protocol route to each spine switch.
According to one or more embodiments of the present disclosure, the method further comprises:
And setting an activation state of the static route according to a judging result of whether the connection between the target server and the target leaf switch is normal, wherein the activation state is used for indicating to transmit the static route to each spine switch or withdraw the static route from each spine switch.
In a second aspect, according to one or more embodiments of the present disclosure, there is provided a network communication device based on a cloud network, the cloud network adopting a leaf spine network structure, the leaf spine network structure including a plurality of spine switches and a plurality of leaf switches, any leaf switch being a non-stacked switch and being connected to each spine switch, each server being connected to at least two leaf switches, the network communication device being any one target leaf switch of the plurality of leaf switches, the network communication device comprising:
The system comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is used for acquiring one static route corresponding to a plurality of IP addresses of a target server connected with the target leaf switch, the static route comprises a static route prefix unified by the plurality of IP addresses, and the next hop is an interface IP address of the target server;
the sensing unit is used for judging whether the connection between the target server and the target leaf switch is normal or not;
And the communication unit is used for transmitting the static route to each spine switch if the connection between the target server and the target leaf switch is determined to be normal, so that each spine switch receives the network traffic of which the target route is matched with the static route and then transmits the network traffic to the target leaf switch according to a load balancing strategy, and the target leaf switch transmits the network traffic to the target server.
According to one or more embodiments of the present disclosure, the communication unit is further configured to:
And if the connection between the target server and the target leaf switch is abnormal, the static route is withdrawn from each spine switch, so that each spine switch stops transmitting to the target leaf switch after receiving network traffic of which the target route is matched with the static route.
According to one or more embodiments of the present disclosure, the sensing unit, when determining whether the connection between the target server and the target leaf switch is normal, is configured to:
judging whether an address resolution and/or neighbor discovery request sent by the target server is received or not;
And if the address resolution and/or neighbor discovery request sent by the target server is received, determining that the connection between the target server and the target leaf switch is normal.
According to one or more embodiments of the present disclosure, the sensing unit, when determining whether an address resolution and/or neighbor discovery request sent by the target server is received, is configured to:
judging whether an address resolution and/or neighbor discovery address mapping table item corresponding to the target server exists in the host address mapping table item, and if so, determining that an address resolution and/or neighbor discovery request sent by the target server is received.
According to one or more embodiments of the present disclosure, the sensing unit, when determining that the connection between the target server and the target leaf switch is normal if an address resolution and/or neighbor discovery request sent by the target server is received, is configured to:
If only the address resolution request sent by the target server is received, determining that the connection between the target server and the target leaf switch based on the first Internet protocol network is normal, or
If only the neighbor discovery request sent by the target server is received, determining that the connection between the target server and the target leaf switch based on the second Internet protocol network is normal, or
And if the address resolution request and the neighbor discovery request sent by the target server are received, determining that the connection between the target server and the target leaf switch based on the first Internet protocol network and the connection between the target server and the target leaf switch based on the second Internet protocol network are normal.
According to one or more embodiments of the present disclosure, the communication unit, when determining that the connection between the target server and the target leaf switch is normal, transmits the static route to each spine switch, is configured to:
If it is determined that the first IP-based network connection between the target server and the target leaf switch is normal, transmitting a first IP-based network static route corresponding to a plurality of IP addresses of the target server to each spine switch, and/or
And if the second internet protocol network-based connection between the target server and the target leaf switch is determined to be normal, transmitting the second internet protocol network-based static route corresponding to a plurality of IP addresses of the target server to each spine switch.
According to one or more embodiments of the present disclosure, the communication unit is further configured to:
after a first internet protocol network-based static route corresponding to a plurality of IP addresses of the target server is transmitted to each spine switch, receiving first internet protocol network-based traffic matched with the first internet protocol network-based static route by each spine switch according to a destination route transmitted by a load balancing strategy, and transmitting the first internet protocol network-based traffic to the target server, and/or
And after the second internet protocol network-based static route corresponding to the plurality of IP addresses of the target server is transmitted to each spine switch, receiving second internet protocol network-based traffic matched with the second internet protocol network-based static route by each spine switch according to the destination route transmitted by the load balancing strategy, and transmitting the second internet protocol network-based traffic to the target server.
According to one or more embodiments of the present disclosure, the communication unit, when transmitting the static route to each spine switch, is configured to:
And converting the static route into a border gateway protocol route and transmitting the border gateway protocol route to each spine switch.
According to one or more embodiments of the present disclosure, the sensing unit is further configured to:
And setting an activation state of the static route according to a judging result of whether the connection between the target server and the target leaf switch is normal, wherein the activation state is used for indicating to transmit the static route to each spine switch or withdraw the static route from each spine switch.
In a third aspect, according to one or more embodiments of the present disclosure, there is provided an electronic device comprising at least one processor and a memory;
the memory stores computer-executable instructions;
the at least one processor executes the computer-executable instructions stored by the memory, causing the at least one processor to perform the cloud network-based network communication method as described above in the first aspect and the various possible designs of the first aspect.
In a fourth aspect, according to one or more embodiments of the present disclosure, there is provided a computer-readable storage medium having stored therein computer-executable instructions which, when executed by a processor, implement the cloud network-based network communication method according to the first aspect and the various possible designs of the first aspect.
In a fifth aspect, according to one or more embodiments of the present disclosure, there is provided a computer program product comprising computer-executable instructions which, when executed by a processor, implement the cloud network-based network communication method according to the first aspect and the various possible designs of the first aspect.
The foregoing description is only of the preferred embodiments of the present disclosure and description of the principles of the technology being employed. It will be appreciated by persons skilled in the art that the scope of the disclosure referred to in this disclosure is not limited to the specific combinations of features described above, but also covers other embodiments which may be formed by any combination of features described above or equivalents thereof without departing from the spirit of the disclosure. Such as those described above, are mutually substituted with the technical features having similar functions disclosed in the present disclosure (but not limited thereto).
Moreover, although operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order. In certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of the present disclosure. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.
Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are example forms of implementing the claims.
Claims (13)
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410718480.9A CN118487993B (en) | 2024-06-04 | 2024-06-04 | Network communication method, device and storage medium based on cloud network |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410718480.9A CN118487993B (en) | 2024-06-04 | 2024-06-04 | Network communication method, device and storage medium based on cloud network |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN118487993A CN118487993A (en) | 2024-08-13 |
| CN118487993B true CN118487993B (en) | 2024-12-13 |
Family
ID=92187832
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202410718480.9A Active CN118487993B (en) | 2024-06-04 | 2024-06-04 | Network communication method, device and storage medium based on cloud network |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN118487993B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN121728022A (en) * | 2024-09-23 | 2026-03-24 | 云智能资产控股（新加坡）私人股份有限公司 | Data transmission methods, network access systems, equipment, media and software products |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106982179A (en) * | 2016-12-30 | 2017-07-25 | 中国银联股份有限公司 | A kind of method for controlling network flow and switch device |
| CN111030926A (en) * | 2019-12-20 | 2020-04-17 | 苏州浪潮智能科技有限公司 | A method and device for improving network high availability |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9985867B2 (en) * | 2015-12-11 | 2018-05-29 | Cisco Technology, Inc. | Optimizing EVPN for data centers with redundant top-of-rack deployments |
| CN111327523B (en) * | 2020-02-28 | 2022-03-22 | 深信服科技股份有限公司 | Network protection method and device based on aggregation port, network equipment and storage medium |
| US12021740B2 (en) * | 2021-05-28 | 2024-06-25 | Juniper Networks, Inc. | Policy enforcement for bare metal servers by top of rack switches |
| CN114726826B (en) * | 2022-03-28 | 2023-10-13 | 新华三技术有限公司 | Method and device for interfacing container network through MLAG networking |
| CN116566752B (en) * | 2023-07-11 | 2023-09-12 | 苏州浪潮智能科技有限公司 | Safety drainage system, cloud host and safety drainage method |
-
2024
- 2024-06-04 CN CN202410718480.9A patent/CN118487993B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106982179A (en) * | 2016-12-30 | 2017-07-25 | 中国银联股份有限公司 | A kind of method for controlling network flow and switch device |
| CN111030926A (en) * | 2019-12-20 | 2020-04-17 | 苏州浪潮智能科技有限公司 | A method and device for improving network high availability |
Also Published As
| Publication number | Publication date |
|---|---|
| CN118487993A (en) | 2024-08-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110708393B (en) | Methods, devices and systems for transmitting data | |
| CN109889621B (en) | Configuration method and device for virtual private cloud service | |
| KR20150013860A (en) | Clientless cloud computing | |
| CN110177047B (en) | Message sending method, device, electronic equipment and computer readable storage medium | |
| WO2014154087A1 (en) | A gateway and its method of transfering data | |
| CN115225634B (en) | Data forwarding method, device and computer program product under virtual network | |
| CN118487993B (en) | Network communication method, device and storage medium based on cloud network | |
| CN113162836A (en) | Virtual local area network communication method and device, cloud server, medium and electronic equipment | |
| CN119902907A (en) | Method and device for switching network card devices based on bonding mode | |
| CN117499318B (en) | Cloud computing virtual network system, and use method, device, equipment and medium thereof | |
| WO2024183775A1 (en) | Network authentication method and apparatus, storage medium, and electronic device | |
| CN111800340B (en) | Data packet forwarding method and device | |
| JP7717988B2 (en) | Method, device, electronic device, computer-readable medium and computer program for acquiring video stream data | |
| US20260039507A1 (en) | Data transmission method based on cloud network, device and medium | |
| US9451049B2 (en) | Sharing media among remote access clients in a universal plug and play environment | |
| CN115987890B (en) | Method, device, electronic equipment and storage medium for cross-cluster access to virtual IP address | |
| CN118740716A (en) | Network communication method, system and storage medium based on multi-container cluster | |
| CN114430364B (en) | Information display method, device, electronic device and computer readable medium | |
| CN115996187B (en) | Routing information processing method and device, routing information interaction system and routing equipment | |
| CN117377129A (en) | Network sharing method and device, chips, electronic equipment, storage media | |
| CN118118393A (en) | Functional testing method, device, electronic device and storage medium | |
| CN119697267B (en) | A network access method, apparatus, device, and storage medium | |
| CN119697112B (en) | Traffic processing method, device, equipment and storage medium | |
| CN119697136B (en) | A network communication method, apparatus, device, and storage medium | |
| CN118740550B (en) | Message forwarding method and device based on cloud network |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |