WO2021227863A1 - 混合云专线接入网络的灾备方法及装置 - Google Patents

混合云专线接入网络的灾备方法及装置 Download PDF

Info

Publication number
WO2021227863A1
WO2021227863A1 PCT/CN2021/090034 CN2021090034W WO2021227863A1 WO 2021227863 A1 WO2021227863 A1 WO 2021227863A1 CN 2021090034 W CN2021090034 W CN 2021090034W WO 2021227863 A1 WO2021227863 A1 WO 2021227863A1
Authority
WO
WIPO (PCT)
Prior art keywords
link
hybrid cloud
dedicated line
equal
cost route
Prior art date
Application number
PCT/CN2021/090034
Other languages
English (en)
French (fr)
Inventor
马鹏程
Original Assignee
北京金山云网络技术有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 北京金山云网络技术有限公司 filed Critical 北京金山云网络技术有限公司
Publication of WO2021227863A1 publication Critical patent/WO2021227863A1/zh

Links

Images

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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0663—Performing the actions predefined by failover planning, e.g. switching to standby network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0811—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking connectivity
    • 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

Definitions

  • This application relates to the field of computer technology, and in particular to a disaster recovery method and device for hybrid cloud private line access networks.
  • hybrid clouds Cloud computing technologies that integrate public cloud platforms and private cloud platforms are called hybrid clouds.
  • more and more companies provide both external and internal services. When providing external services, for cost-saving considerations, companies hope to use public cloud platforms. For internal services, for security reasons, companies It is hoped that a private cloud platform can be used. Therefore, hybrid cloud is becoming more and more popular.
  • a single physical leased line often contains multiple physical lines, that is, it is generally achieved by accessing multiple physical lines, and each physical line is connected to a different leased line switch, so as to realize the connection in any link ( That is, the network connection is still guaranteed in the case of a physical line failure.
  • the new leased line switch needs to be configured with routes to other leased line switches, and a new physical line needs to be connected. Obviously the configuration is complicated and the network Bloated.
  • the purpose of this application is to provide a disaster recovery method and device for a hybrid cloud private line access network, so as to alleviate the technical problem of complicated private line access network configuration in related technologies.
  • an embodiment of the present application provides a disaster recovery method for a hybrid cloud private line access network.
  • the above private line access network includes multiple private line links between the hybrid cloud gateway and the opposite network, and the above hybrid cloud gateway is configured There is an equal-cost route list, and each equal-cost route in the above-mentioned equal-cost route list corresponds to a dedicated line link; the above method includes: monitoring the link status of the above-mentioned multiple dedicated line links; when the above-mentioned multiple dedicated line links are monitored When the first leased line link fails, the hybrid cloud gateway sends an equal-cost route cancellation request for the first leased line link, so that the hybrid cloud gateway transfers the equal-cost route of the first leased line link to the equivalent route Revoked from the list.
  • the embodiments of the present application provide a disaster recovery method for a hybrid cloud private line access network.
  • the above private line access network includes multiple private line links between the hybrid cloud gateway and the opposite network; the above method includes: receiving monitoring The equivalent-cost route cancellation request of the first leased line link among the above-mentioned multiple leased line links sent by the device; wherein, the above-mentioned hybrid cloud gateway is configured with an equal-cost route list, and each equal-cost route in the above-mentioned equal-cost route list corresponds to A dedicated line link; the equal-cost route of the first dedicated line link is withdrawn from the above-mentioned equal-cost route list, so as to distribute hybrid cloud dedicated line services based on the equal-cost route list after the equal-cost route of the above-mentioned first dedicated line link is cancelled.
  • an embodiment of the present application provides a disaster recovery device for a hybrid cloud private line access network.
  • the above private line access network includes multiple private line links between the hybrid cloud gateway and the opposite network, and the above hybrid cloud gateway is configured There is an equal-cost route list, and each equal-cost route in the above-mentioned equal-cost route list corresponds to a dedicated line link;
  • the above-mentioned device includes: a detection module configured to monitor the link status of the above-mentioned multiple dedicated line links; a sending module set to When it is detected that the first leased line link of the multiple leased line links fails, the equivalent route cancellation request of the first leased line link is sent to the hybrid cloud gateway, so that the hybrid cloud gateway can remove the first leased line link.
  • the equal-cost route of is withdrawn from the above-mentioned equal-cost route list.
  • an embodiment of the present application provides a disaster recovery device for a hybrid cloud private line access network.
  • the above private line access network also includes multiple private line links between peer networks;
  • the above device includes: a receiving module configured to Receive the equivalent route cancellation request of the first leased line link among the multiple leased line links sent by the monitoring device; wherein, the hybrid cloud gateway is configured with an equivalent route list, and each of the equivalent route lists is equivalent
  • the route corresponds to a dedicated line link;
  • the cancellation module is set to cancel the equal-cost route of the first dedicated line link in the above-mentioned equal-cost route list, so as to cancel the equal-cost route based on the equal-cost route of the above-mentioned first dedicated line link List distribution of hybrid cloud private line services.
  • an embodiment of the application provides a disaster recovery system for a hybrid cloud private line access network, including: a hybrid cloud gateway configured with an equivalent-cost route list, and each equal-cost route in the above-mentioned equivalent route list corresponds to a private line Link, the multiple dedicated line links corresponding to the hybrid cloud gateway and the peer network; set to receive the equivalent route cancellation request of the first dedicated line link among the multiple dedicated line links sent by the monitoring device; The equal-cost route of the first dedicated line link is withdrawn from the above-mentioned equal-cost route list, so as to distribute hybrid cloud dedicated line services based on the equivalent-cost route list after the above-mentioned equal-cost route of the above-mentioned first dedicated line link is cancelled; the monitoring device is set to monitor the above The link status of the multiple dedicated line links; when it is detected that the first dedicated line link of the multiple dedicated line links fails, the equivalent route cancellation request of the first dedicated line link is sent to the hybrid cloud gateway.
  • an embodiment of the present application provides a computer device, including a memory and a processor.
  • the memory stores a computer program that can run on the processor.
  • the processor executes the computer program, any of the foregoing embodiments is implemented. Steps of a method.
  • embodiments of the present application provide a computer-readable storage medium.
  • the computer-readable storage medium stores machine-runnable instructions.
  • the computer-runnable instructions When the computer-runnable instructions are called and run by a processor, the computer-runnable instructions prompt
  • the above-mentioned processor runs the method of any one of the above-mentioned embodiments.
  • the embodiments of the present application provide a computer program product containing instructions.
  • the computer program product containing instructions runs on a computer, the computer executes the steps of any one of the above-mentioned embodiments.
  • an embodiment of the present application provides a computer program, which when the computer program runs on a computer, causes the computer to execute the steps of any one of the above-mentioned methods in the above-mentioned embodiments.
  • the disaster recovery method and device for hybrid cloud private line access network monitor the link status of multiple private line links; when it is detected that the first private line link of the multiple private line links fails At the time, send the equal-cost route cancellation request of the first leased line link to the hybrid cloud gateway, so that the hybrid cloud gateway cancels the equal-cost route of the first leased line link in the equal-cost route list. In this way, routing adjustments can be made on the hybrid cloud gateway to avoid configuring too much network content on the dedicated line switch, simplifying the network wiring in the computer room, reducing the difficulty of configuring the disaster recovery method, and improving the availability of the disaster recovery method.
  • each dedicated line switch is adjusted through the hybrid cloud gateway, so that there is no need to connect lines between each dedicated line switch, thereby simplifying the network.
  • it is necessary to add a physical line it is no longer necessary to connect to a new dedicated line switch.
  • Configure routing and physical lines to other dedicated line switches can reduce the complexity of network configuration and simplify the network.
  • Figure 1 is a schematic diagram of a hybrid cloud dedicated line access network
  • FIG. 2 is a schematic diagram of another hybrid cloud dedicated line access network
  • FIG. 3 is a schematic diagram of another hybrid cloud dedicated line access network
  • FIG. 4 is a schematic diagram of another hybrid cloud dedicated line access network provided by an embodiment of this application.
  • FIG. 5 is a schematic diagram of another hybrid cloud dedicated line access network provided by an embodiment of this application.
  • FIG. 6 is a schematic diagram of another hybrid cloud dedicated line access network provided by an embodiment of this application.
  • FIG. 7 is a schematic flowchart of a disaster recovery method for a hybrid cloud dedicated line access network provided by an embodiment of this application.
  • FIG. 8 is a schematic flowchart of another disaster recovery method for hybrid cloud dedicated line access network provided by an embodiment of this application.
  • FIG. 9 is a schematic structural diagram of another disaster recovery device for hybrid cloud dedicated line access network provided by an embodiment of the application.
  • FIG. 10 is a schematic structural diagram of another disaster recovery device for hybrid cloud dedicated line access network provided by an embodiment of this application.
  • FIG. 11 is a schematic structural diagram of a computer device provided by an embodiment of this application.
  • Figure 1 is a network solution for cloud computing vendors to achieve private line access.
  • the virtual machine traffic first passes through the hybrid cloud gateway to the private line switch (that is, the private line switch on the left in Figure 1).
  • the private line switch that is, the private line switch on the left in Figure 1).
  • the dedicated line switch is implemented using hardware network equipment (non-x86 servers).
  • IDC Internet Data Center
  • the dedicated line switch of the network that is, the dedicated line switch on the right in Figure 1). Because the leased line is exclusive to a certain customer, it does not need to be implemented through tunneling technology, and the message is directly sent to the peer network through the physical leased line.
  • the cloud environment is connected to the network at the opposite end through two private line switches connected to two physical lines, and the two private line switches are also directly connected. All network segments to the peer network are configured with two routes, the next hop of one route is the Internet Protocol (IP) address of the peer network (high priority), and the next hop of the other route passes through the other The line reaches another dedicated line switch (low priority).
  • IP Internet Protocol
  • NQA network quality analyzer
  • the link is detected to be unreachable, the route is cancelled, and the message is sent to other dedicated line switches through the previously configured low-priority route, and other dedicated line switches use other lines Send to the peer network.
  • the cloud vendor accesses multiple physical lines through multiple dedicated line switches, and then configures the backup route of the directly connected link in the dedicated line switch to achieve disaster recovery of the dedicated line.
  • the network is simpler and the management is more convenient in scenarios where the number of dedicated line switches is small, such as in the scenario of two or three dedicated line switches. But when the number of dedicated line switches and physical lines is large, the network will become particularly complex and difficult to manage.
  • each dedicated line switch in Figure 3 also needs to provide backup routes for other dedicated line switches to avoid network interruption when the line fails. Obviously, even the simplest method requires a backup route to other dedicated line switches to be configured on each dedicated line switch to prevent line failures.
  • the customer needs to add another physical line at this time, and then use a new leased line switch to carry it, then it needs to configure the route to other leased line switches on the new leased line switch, and it needs to connect the line. Obviously, the configuration is complicated and the network is bloated. Unbearable.
  • an embodiment of the present application provides a disaster recovery method for a hybrid cloud private line access network.
  • the private line access network includes multiple private lines between the hybrid cloud gateway and the peer network.
  • Link the hybrid cloud gateway is configured with an equal-cost route list, and each equal-cost route in the equal-cost route list corresponds to a dedicated line link; the method includes:
  • the equivalent route cancellation request of the first leased line link is sent to the hybrid cloud gateway, so that the hybrid cloud gateway will
  • the equal-cost route of the first dedicated line link is withdrawn from the equal-cost route list.
  • the equal-cost route in the equal-cost route list means that there are multiple different routing paths with the same cost value to the same destination IP or destination network segment.
  • the embodiments of this application can move the actions such as cancellation or validation of routes to the hybrid cloud gateway to avoid configuring an overly complicated network on the dedicated line switch used to connect to the peer network.
  • the frequency of wiring in the computer room is reduced, and on the other hand, The management of dedicated line switches is also much simpler.
  • the cloud environment which may include multiple computing nodes
  • the cloud environment is connected to the peer network through three dedicated lines (ie dedicated line links), three dedicated line switches, and the hybrid cloud gateway (Connected to the cloud environment) Three equal-cost routes are configured.
  • the next hop is the three dedicated line switches used to connect to the peer network. If there is no abnormality, the round-trip packets in this business scenario pass through the Three line loads.
  • the embodiment of the present application uses a middleware to detect the link quality of the dedicated line link corresponding to each dedicated line switch.
  • the route is adjusted on the hybrid cloud gateway, and the traffic corresponding to the failed link is switched to other non-faulty equivalent routes.
  • a monitoring device such as gobgp in Figure 5, where gobgp is an open source project on github and is implemented using golang bgp function.
  • Monitoring equipment can be used to monitor the status of the link. If a line is disconnected or a dedicated line switch goes down, the monitoring device can quickly monitor the link failure, and then feed the link failure back to the hybrid cloud gateway so that the hybrid cloud gateway deletes the corresponding route.
  • the BFD protocol or NQA protocol can be configured on the leased line switch to detect the link status
  • BGP Border Gateway Protocol
  • gobgp an example of middleware
  • the BGP protocol is configured on the dedicated line switch and gobgp. That is, in addition to the BFD protocol or NQA protocol configured with the access device at the opposite end, the dedicated line switch also configures BGP with the gobgp.
  • BGP is configured between dedicated line switches and monitoring equipment to exchange information to synchronize link status.
  • the leased line switch can detect the link interruption through the BFD protocol configured with the access device at the opposite end. At this time, the leased line switch cancels the route. After the private line switch withdraws the route, because BGP is configured between the private line switch and gobgp, this route cancellation operation can be synchronized to gobgp through BGP messages. After receiving the BGP message, gobgp calls the interface of the hybrid cloud gateway to notify the hybrid cloud gateway to withdraw the route corresponding to the interrupted link.
  • FIG. 7 is a schematic flowchart of a disaster recovery method for a hybrid cloud private line access network provided by an embodiment of the application.
  • the private line access network includes multiple private line links between the hybrid cloud gateway and the peer network.
  • the hybrid cloud gateway is configured with an equivalent route list (for example, the equivalent route list in the hybrid cloud gateway in Figure 4 "10.20.0.0/ 24gw1.1.1.1; 10.20.0.0/24gw1.1.1.2; 10.20.0.0/24gw1.1.1.3”), each equal-cost route in the equal-cost route list corresponds to a dedicated line link.
  • the equal-cost routing list may include multiple, and each equal-cost routing list corresponds to one user.
  • This method can be applied to a monitoring device, which is a middleware, for example, gobgp as shown in FIG. 6. Of course, this method can be applied to other devices, such as hybrid cloud gateways. As shown in Figure 7, the method may include:
  • Step S710 monitoring the link status of multiple dedicated line links
  • each dedicated line link can be monitored in a variety of ways. For example, you can monitor the link status of multiple dedicated line links based on the BFD protocol. Alternatively, the NQA protocol can also be analyzed based on network quality to monitor the link status of the multiple dedicated line links.
  • the monitoring device may establish a BGP-based peer relationship with the dedicated line switch of each dedicated line link. It should be noted that the BGP speakers who exchange messages in BGP are called peers. After the monitoring device establishes a peer with the private line switch of the private line link, the monitoring device and the private line switch are called peers, and they can act as BGP speakers that exchange messages with each other.
  • Each dedicated line switch can monitor the link status of its corresponding dedicated line link based on the BFD protocol, and the monitoring equipment can synchronize the link status detected by the dedicated line switch based on the BFD protocol/NQA protocol through BGP.
  • the monitoring device after the monitoring device establishes BGP-based peers with the dedicated line switches of each dedicated line link, it can also perform route learning for each BGP-based peer, so as to determine the corresponding to each dedicated line link Equal-cost routing. After that, when the monitoring equipment detects the failure of the first dedicated line link among the multiple dedicated line links, it can determine the first dedicated line link corresponding to the determined equivalent route corresponding to each dedicated line link And send the equal-cost route cancellation request of the first leased line link to the hybrid cloud gateway.
  • the monitoring device may be implemented using the gobgp open source project, and the monitoring device may be gobgp.
  • the three dedicated line switches in Figure 5 must be configured and take effect the next hop to the opposite network route (10.20.0.0/24).
  • gobgp can learn 10.20.0.0/24 through three peers, and can recognize that there are three paths (paths), which are three dedicated line switches (1.1.1.1, 1.1.1.2, and 1.1.1.3). If one of the three dedicated line links is interrupted, gobgp can learn the corresponding routing changes through BGP.
  • Step S720 When it is detected that the first leased line link of the multiple leased line links is faulty, the equivalent route cancellation request of the first leased line link is sent to the hybrid cloud gateway, so that the hybrid cloud gateway transfers the first leased line link to the hybrid cloud gateway.
  • the equal-cost route of is withdrawn from the equal-cost route list.
  • the dedicated line link corresponding to the dedicated line switch (1.1.1.3) is interrupted for some reason, the dedicated line switch can detect the link interruption through the BFD protocol, and then cancel the route. After the route is revoked, because there is BGP between the dedicated line switch and gobgp, the route revoking operation will be synchronized to gobgp. After gobgp receives the BGP message (the next hop of 10.20.0.0/24 is 1.1.1.3 withdraw), it calls the interface of the hybrid cloud gateway and cancels the route corresponding to the interrupted link in the hybrid cloud gateway.
  • the dedicated line switch may validate the related route through the BFD protocol.
  • the effective route can be synchronized to gobgp through BGP message. After the gobgp receives the effective BGP message of the route, it can call the interface of the hybrid cloud gateway to add the route.
  • the method may further include the following steps: when it is detected that the second leased line link of the multiple leased line links becomes effective, sending the equivalent-cost route validation request of the second leased line link to the hybrid cloud gateway, so that the hybrid The cloud gateway adds the equal-cost route of the second leased line link in the equal-cost route list.
  • the embodiment of this application monitors the link status of multiple dedicated line links; when it is detected that the first dedicated line link of the multiple dedicated line links fails, the equivalent route cancellation of the first dedicated line link is sent to the hybrid cloud gateway Request so that the hybrid cloud gateway removes the equal-cost route of the first leased line link from the equal-cost route list.
  • routing adjustments can be made on the hybrid cloud gateway to avoid configuring too much network content on the dedicated line switch, simplifying the network wiring in the computer room, reducing the difficulty of configuring the disaster recovery method, and improving the availability of the disaster recovery method.
  • the equal cost routing of each dedicated line switch is adjusted through the hybrid cloud gateway, so that there is no need to connect lines between each dedicated line switch, thereby simplifying the network. When it is necessary to add a physical line, it is no longer necessary to connect to a new dedicated line switch. Configure routing and physical lines to other dedicated line switches. It can be seen that this solution can reduce the complexity of network configuration and simplify the network.
  • the following will forward and receive messages based on the disaster recovery method for the hybrid cloud private line access network provided by the embodiment of the present application.
  • the equal-cost route list of the hybrid cloud gateway contains the equal-cost routes of each dedicated line switch.
  • the hybrid cloud gateway receives the message that needs to be forwarded, it determines the target route from multiple equal-cost routes based on the preset message forwarding strategy , And forward the received message to the private line switch corresponding to the target route, so that the private line switch can process the message.
  • the hybrid cloud gateway deletes the equivalent cost route corresponding to the dedicated line switch that has the link failure from the equivalent route list.
  • the hybrid cloud gateway will Determine the target route in the dedicated line switch without link failure.
  • FIG. 8 is a schematic flowchart of another disaster recovery method for a hybrid cloud dedicated line access network provided by an embodiment of the application.
  • the dedicated line access network includes multiple dedicated line links between the hybrid cloud gateway and the peer network; this method can be applied to the hybrid cloud gateway, but of course it is not limited to this, as shown in Figure 8, the method can include the following steps :
  • S810 Receive an equal-cost route cancellation request of the first leased line link among the multiple leased line links sent by the monitoring device.
  • an equal-cost route list is configured on the hybrid cloud gateway, and each equal-cost route in the equal-cost route list corresponds to a dedicated line link.
  • the dedicated line link corresponding to the dedicated line switch (1.1.1.3) is interrupted for some reason, and the dedicated line switch can detect the link interruption through the BFD protocol, and send to gobgp a sign indicating that the link is interrupted.
  • BGP message After receiving the BGP message (the next hop of 10.20.0.0/24 is 1.1.1.3 withdrawn), gobgp calls the interface of the hybrid cloud gateway to send the equivalent route of the first leased line link (10.20) to the hybrid cloud gateway. The next hop of .0.0/24 is 1.1.1.3) withdraw request.
  • S820 Withdraw the equal-cost route of the first dedicated line link in the equal-cost route list, so as to distribute the hybrid cloud dedicated line service based on the equal-cost route list after the equal-cost route of the first dedicated line link is cancelled.
  • the effective route can be synchronized to gobgp through a BGP message, and gobgp calls the interface of the hybrid cloud gateway to add the route.
  • the method also includes:
  • Step 1) receiving a request for validating the equivalent route of the second leased line link among the multiple leased line links sent by the monitoring device;
  • the embodiment of this application monitors the link status of multiple dedicated line links; when it is detected that the first dedicated line link of the multiple dedicated line links fails, the equivalent route cancellation of the first dedicated line link is sent to the hybrid cloud gateway Request so that the hybrid cloud gateway removes the equal-cost route of the first leased line link from the equal-cost route list.
  • routing adjustments can be made on the hybrid cloud gateway to avoid configuring too much network content on the dedicated line switch, simplifying the network wiring in the computer room, reducing the difficulty of configuring the disaster recovery method, and improving the availability of the disaster recovery method.
  • the equal cost routing of each dedicated line switch is adjusted through the hybrid cloud gateway, so that there is no need to connect lines between each dedicated line switch, thereby simplifying the network. When it is necessary to add a physical line, it is no longer necessary to connect to a new dedicated line switch. Configure routing and physical lines to other dedicated line switches. It can be seen that this solution can reduce the complexity of network configuration and simplify the network.
  • FIG. 9 is a schematic structural diagram of a disaster recovery device for a hybrid cloud dedicated line access network provided by an embodiment of the application.
  • the private line access network includes multiple private line links between the hybrid cloud gateway and the peer network.
  • the hybrid cloud gateway is configured with an equivalent route list, and each equivalent route in the equivalent route list corresponds to a private line link; As shown in Figure 9, the device includes:
  • the detection module 901 is configured to monitor the link status of multiple dedicated line links
  • the sending module 902 is configured to send an equivalent route cancellation request of the first leased line link to the hybrid cloud gateway when the first leased line link of the multiple leased line links is detected to be faulty, so that the hybrid cloud gateway sends the first leased line link to the hybrid cloud gateway.
  • the equal-cost route of the dedicated line link is withdrawn from the equal-cost route list.
  • the sending module 902 is further configured to:
  • the request for the effective route of the second leased line link is sent to the hybrid cloud gateway, so that the hybrid cloud gateway adds the first leased line to the equivalent route list Equal-cost routing of the link.
  • the detection module 901 is further configured to detect the link status of multiple dedicated line links based on the BFD protocol.
  • the detection module 901 is further configured to: respectively establish BGP-based peers with the dedicated line switches of each dedicated line link;
  • the link status detected by the BGP-based synchronizing dedicated line switch based on the BFD protocol is the link status detected by the BGP-based synchronizing dedicated line switch based on the BFD protocol.
  • it further includes a route learning module, which is configured to perform route learning for each peer established based on BGP, and determine an equivalent route corresponding to each dedicated line link.
  • the embodiment of this application monitors the link status of multiple dedicated line links; when it is detected that the first dedicated line link of the multiple dedicated line links fails, the equivalent route cancellation of the first dedicated line link is sent to the hybrid cloud gateway Request that the hybrid cloud gateway cancel the equal-cost route of the first leased line link in the equal-cost route list.
  • routing adjustments can be made on the hybrid cloud gateway to avoid configuring too much network content on the dedicated line switch, simplifying the network wiring in the computer room, reducing the difficulty of configuring the disaster recovery method, and improving the availability of the disaster recovery method.
  • the equal cost routing of each dedicated line switch is adjusted through the hybrid cloud gateway, so that there is no need to connect lines between each dedicated line switch, thereby simplifying the network. When it is necessary to add a physical line, it is no longer necessary to connect to a new dedicated line switch. Configure routing and physical lines to other dedicated line switches. It can be seen that this solution can reduce the complexity of network configuration and simplify the network.
  • FIG. 10 is a schematic structural diagram of a disaster recovery device for a hybrid cloud private line access network provided by an embodiment of the application.
  • the dedicated line access network includes multiple dedicated line links between the hybrid cloud gateway and the peer network; as shown in Figure 10, the device includes:
  • the receiving module 1001 is configured to receive the equivalent-cost route cancellation request of the first leased line link among the multiple leased line links sent by the monitoring device; wherein, the hybrid cloud gateway is configured with an equal-cost route list, and each of the equal-cost route lists is One equal-cost route corresponds to one dedicated line link;
  • the cancellation module 1002 is configured to cancel the equal-cost route of the first leased line link in the equal-cost route list, so as to distribute the hybrid cloud leased line service based on the equal-cost route list after the equal-cost route of the first leased line link is cancelled.
  • the receiving module 1001 is further configured to receive a request for validating an equivalent route of a second leased line link among the multiple leased line links sent by the monitoring device;
  • the adding module is configured to add the equal-cost route of the second leased line link to the equal-cost route list, so as to distribute the hybrid cloud leased line service based on the equal-cost route list after adding the equal-cost route of the second leased line link.
  • the disaster recovery device for the hybrid cloud private line access network provided by the embodiment of this application has the same technical features as the disaster recovery method for the hybrid cloud private line access network provided in the above embodiment, so it can also solve the same technical problems and achieve the same Technical effect.
  • the embodiment of the present application also provides a disaster recovery system for a hybrid cloud dedicated line access network.
  • a disaster recovery system for a hybrid cloud dedicated line access network.
  • the system shown in Figure 1. can include:
  • the hybrid cloud gateway is configured with an equal-cost route list. Each equal-cost route in the equal-cost route list corresponds to a dedicated line link. There are multiple dedicated line links between the hybrid cloud gateway and the peer network; set to receive monitoring The request for canceling the equal-cost route of the first leased line link among the multiple leased line links sent by the device; cancel the equal-cost route of the first leased line link in the equal-cost route list, so as to cancel the equal-cost route of the first leased line link.
  • the monitoring device is set to monitor the link status of multiple dedicated line links; when the first dedicated line link of the multiple dedicated line links is detected to be faulty, the equivalent route cancellation of the first dedicated line link is sent to the hybrid cloud gateway ask.
  • the system may also include a dedicated line switch, which is used to detect its own link status based on the BFD protocol, and synchronize the detected link status to the monitoring device.
  • a computer device 1100 provided by an embodiment of the present application includes a processor 1101, a memory 1102, and a bus.
  • the memory 1102 stores machine-readable instructions executable by the processor 1101.
  • the processor 1101 and the memory 1102 communicate through a bus, and the processor 1101 executes machine-readable instructions to execute the steps of the disaster recovery method for the hybrid cloud private line access network described above.
  • the aforementioned memory 1102 and the processor 1101 can be general-purpose memories and processors, which are not specifically limited here.
  • the processor 1101 runs the computer program stored in the memory 1102, it can execute the aforementioned hybrid cloud dedicated line access network Disaster preparedness method.
  • an embodiment of the present application also provides a computer-readable storage medium.
  • the computer-readable storage medium stores machine-runnable instructions, and the computer-runnable instructions are called by the processor. And when running, the computer can run instructions to cause the processor to run the steps of the disaster recovery method for the hybrid cloud dedicated line access network.
  • embodiments of the present application also provide a computer program product containing instructions.
  • the computer program product containing instructions runs on a computer, the computer executes the above hybrid cloud dedicated line access Network disaster recovery methods.
  • an embodiment of the present application further provides a computer program, which when running on a computer, causes the computer to execute the above disaster recovery method for the hybrid cloud private line access network.
  • the disaster recovery device for the hybrid cloud dedicated line access network provided in the embodiment of the present application may be specific hardware on the device or software or firmware installed on the device.
  • the implementation principles and technical effects of the device provided in the embodiments of the present application are the same as those of the foregoing method embodiments.
  • the specific working process of the aforementioned system, device, and unit can all refer to the corresponding process in the above method embodiment, which will not be repeated here.
  • the disclosed device and method may be implemented in other ways.
  • the device embodiments described above are merely illustrative.
  • the division of the above-mentioned units is only a logical function division, and there may be other divisions in actual implementation.
  • multiple units or components may be combined or may be Integrate into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be through some communication interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.
  • the units described above as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • each block in the flowchart or block diagram may represent a module, program segment, or part of the code, and the above-mentioned module, program segment, or part of the code contains one or more options for realizing the specified logical function.
  • Execute instructions may also occur in a different order from the order marked in the drawings.
  • each block in the block diagram and/or flowchart, and the combination of the blocks in the block diagram and/or flowchart can be implemented by a dedicated hardware-based system that performs the specified functions or actions Or it can be realized by a combination of dedicated hardware and computer instructions.
  • the functional units in the embodiments provided in this application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the above functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer readable storage medium.
  • the technical solution of the present application essentially or the part that contributes to the related technology or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including several
  • the instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the disaster recovery method for the hybrid cloud private line access network described in the various embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program code .
  • the disaster recovery method and device for hybrid cloud private line access network monitor the link status of multiple private line links; when it is detected that the first private line link of the multiple private line links is faulty At the time, send the equal-cost route cancellation request of the first leased line link to the hybrid cloud gateway, so that the hybrid cloud gateway cancels the equal-cost route of the first leased line link in the equal-cost route list. In this way, routing adjustments can be performed on the hybrid cloud gateway, avoid configuring too much network content on the dedicated line switch, simplify the network wiring in the computer room, reduce the configuration difficulty of the disaster recovery method, and improve the availability of the disaster recovery method. This application.
  • each dedicated line switch is adjusted through the hybrid cloud gateway, so that there is no need to connect lines between each dedicated line switch, which simplifies the network.
  • a physical line needs to be added, it is no longer necessary to connect to a new dedicated line switch.
  • Configure routing and physical lines to other dedicated line switches can reduce the complexity of network configuration and simplify the network.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Environmental & Geological Engineering (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Telephonic Communication Services (AREA)

Abstract

本申请提供了一种混合云专线接入网络的灾备方法及装置，涉及计算机技术领域，包括监测多个专线链路的链路状态；当监测到多个专线链路中的第一专线链路出现故障时，向混合云网关发送第一专线链路的等价路由撤销请求，以使混合云网关将第一专线链路的等价路由在等价路由列表中撤销。以此可以在混合云网关进行路由调整，避免在专线交换机上配置太多的网络内容，简化了机房的网络布线，降低了该灾备方法的配置难度，提升了灾备方法的可用性。并且，通过本方案可以降低网络配置复杂度，且简化了网络。

Description

混合云专线接入网络的灾备方法及装置
本申请要求于2020年05月09日提交中国专利局、申请号为202010391003.8发明名称为“混合云专线接入网络的灾备方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及计算机技术领域，尤其是涉及一种混合云专线接入网络的灾备方法及装置。
背景技术
在当前得云计算网络产品中，专线基本是所有大型云计算厂商都必须推出的产品，用来实现多云接入。融合了公有的云平台及私有的云平台的云计算技术的称为混合云。目前，越来越多的企业提供对外及对内两种服务，在提供对外服务时，出于成本节约考虑，企业希望可以应用公有的云平台，在对内服务时，出于安全考虑，企业希望可以应用私有的云平台，因此，混合云越来越流行。
为了实现物理专线的高可用性，单个物理专线往往包含多根物理线路，即一般通过接入多根物理线路，并且每根物理线路接入到不同的专线交换机实现的，以实现在任何链路(即物理线路)故障的情况下仍然保证网络连通。
如果此时客户需要再加一个物理线路，再用一个新的专线交换机承载，则需要在新的专线交换机上配置到其他的专线交换机的路由，而且需要新接物理线路，显然配置复杂，且网络臃肿不堪。
发明内容
本申请的目的在于提供一种混合云专线接入网络的灾备方法及装置，以缓解了相关技术中存在的专线接入网络配置复杂的技术问题。
第一方面，本申请实施例提供一种混合云专线接入网络的灾备方法，上述专线接入网络包括混合云网关和对端网络之间的多个专线链路，上述混合云网关上配置有等价路由列表，上述等价路由列表中的每个等价路由对应一个专线链路；上述方法包括：监测上述多个专线链路的链路状态；当监测到上述多个专线链路中的第一专线链路出现故障时，向上述混合云网关发送第一专线链路的等价路由撤销请求，以使上述混合云网关将上述第一专线链路 的等价路由在上述等价路由列表中撤销。第二方面，本申请实施例提供一种混合云专线接入网络的灾备方法，上述专线接入网络包括混合云网关和对端网络之间的多个专线链路；上述方法包括：接收监控设备发送的上述多个专线链路中的第一专线链路的等价路由撤销请求；其中，上述混合云网关上配置有等价路由列表，上述等价路由列表中的每个等价路由对应一个专线链路；将上述第一专线链路的等价路由在上述等价路由列表中撤销，以便基于撤销上述第一专线链路的等价路由后的等价路由列表分发混合云专线业务。
第三方面，本申请实施例提供一种混合云专线接入网络的灾备装置，上述专线接入网络包括混合云网关和对端网络之间的多个专线链路，上述混合云网关上配置有等价路由列表，上述等价路由列表中的每个等价路由对应一个专线链路；上述装置包括：检测模块，设置为监测上述多个专线链路的链路状态；发送模块，设置为当监测到上述多个专线链路中的第一专线链路出现故障时，向上述混合云网关发送第一专线链路的等价路由撤销请求，以便上述混合云网关将上述第一专线链路的等价路由在上述等价路由列表中撤销。
第四方面，本申请实施例提供一种混合云专线接入网络的灾备装置，上述专线接入网络还包括对端网络之间的多个专线链路；上述装置包括：接收模块，设置为接收监控设备发送的上述多个专线链路中的第一专线链路的等价路由撤销请求；其中，上述混合云网关上配置有等价路由列表，上述等价路由列表中的每个等价路由对应一个专线链路；撤销模块，设置为将上述第一专线链路的等价路由在上述等价路由列表中撤销，以便基于撤销上述第一专线链路的等价路由后的等价路由列表分发混合云专线业务。
第五方面，本申请实施例提供一种混合云专线接入网络的灾备系统，包括：混合云网关，配置有等价路由列表，上述等价路由列表中的每个等价路由对应一个专线链路，混合云网关和对端网络之间对应有的多个专线链路；设置为接收监控设备发送的上述多个专线链路中的第一专线链路的等价路由撤销请求；将上述第一专线链路的等价路由在上述等价路由列表中撤销，以便基于撤销上述第一专线链路的等价路由后的等价路由列表分发混合云专线业务；监控设备，设置为监测上述多个专线链路的链路状态；当监测到上述 多个专线链路中的第一专线链路出现故障时，向上述混合云网关发送第一专线链路的等价路由撤销请求。
第六方面，本申请实施例提供一种计算机设备，包括存储器、处理器，上述存储器中存储有可在上述处理器上运行的计算机程序，上述处理器执行上述计算机程序时实现上述前述实施方式任一项的方法的步骤。
第七方面，本申请实施例提供一种计算机可读存储介质，上述计算机可读存储介质存储有机器可运行指令，上述计算机可运行指令在被处理器调用和运行时，上述计算机可运行指令促使上述处理器运行上述前述实施方式任一项的方法。
第八方面，本申请实施例提供了一种包含指令的计算机程序产品，包含指令的计算机程序产品在计算机上运行时，使得计算机执行上述实施方式任一项的方法的步骤。
第九方面，本申请实施例提供了一种计算机程序，计算机程序在计算机上运行时，使得计算机执行上述实施方式任一项上述的方法的步骤。
本申请实施例提供的一种混合云专线接入网络的灾备方法及装置，通过监测多个专线链路的链路状态；当监测到多个专线链路中的第一专线链路出现故障时，向混合云网关发送第一专线链路的等价路由撤销请求，以使混合云网关将第一专线链路的等价路由在等价路由列表中撤销。以此可以在混合云网关进行路由调整，避免在专线交换机上配置太多的网络内容，简化了机房的网络布线，降低了该灾备方法的配置难度，提升了灾备方法的可用性。并且，通过混合云网关对各专线交换机的等价路由进行调整，使得不需要在各专线交换机之间连接线路，从而简化了网络，当需要再加一个物理线路，不再需要在新的专线交换机上配置到其他的专线交换机的路由以及物理线路。可见，通过本方案可以降低网络配置复杂度，且简化了网络。
附图说明
为了更清楚地说明本申请实施例和相关技术的技术方案，下面对实施例和相关技术中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，本领域普通技术人员来讲还可以根据这些附图获得其他的附图。
图1为一种混合云专线接入网络示意图；
图2为另一种混合云专线接入网络示意图；
图3为另一种混合云专线接入网络示意图；
图4为本申请实施例提供的另一种混合云专线接入网络示意图；
图5为本申请实施例提供的另一种混合云专线接入网络示意图；
图6为本申请实施例提供的另一种混合云专线接入网络示意图；
图7为本申请实施例提供的一种混合云专线接入网络的灾备方法流程示意图；
图8为本申请实施例提供的另一种混合云专线接入网络的灾备方法流程示意图；
图9为本申请实施例提供的另一种混合云专线接入网络的灾备装置结构示意图；
图10为本申请实施例提供的另一种混合云专线接入网络的灾备装置结构示意图；
图11为本申请实施例提供的一种计算机设备结构示意图。
具体实施方式
为使本申请实施例的目的、技术方案和优点更加清楚，下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。通常在此处附图中描述和示出的本申请实施例的组件可以以各种不同的配置来布置和设计。
因此，以下对在附图中提供的本申请的实施例的详细描述并非旨在限制要求保护的本申请的范围，而是仅仅表示本申请的选定实施例。基于本申请中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
应注意到：相似的标号和字母在下面的附图中表示类似项，因此，一旦某一项在一个附图中被定义，则在随后的附图中不需要对其进行进一步定义和解释。
为了更清楚的阐述本申请实施例的技术方案，首先对相关技术进行介绍：
如图1所示，图1为云计算厂商实现专线接入的网络方案，虚拟机流量先经过混合云网关到达专线交换机(即图1中的左侧的专线交换机)，从宿主机(即图1中的计算节点)到专线交换机之间是overlay(叠加)网络，专线交换机使用硬件网络设备实现(非x86服务器)。然后在专线交换机上插入专线接入到另一个互联网数据中心(Internet Data Center，IDC)或者网络的专线交换机(即图1中的右侧的专线交换机)。因为专线是某个客户独享的，所以不需要再通过隧道技术实现，直接将报文通过物理专线线路送到对端网络。
为了实现物理专线的高可用性，一般是通过接入多根物理线路，并且每根物理线路接入到不同的专线交换机实现的，以实现在任何物理线路故障的情况下仍然保证网络连通。
如图2所示，云环境通过两个专线交换机接入两根物理线路和对端的网络相连，两个专线交换机之间也直接相连。所有去往对端网络的网段配置两个路由，一个路由的下一跳为对端网络的互联网协议(Internet Protocol，IP)地址(优先级高)，另一个路由的下一跳通过另一条线路到达另一个专线交换机(优先级低)。专线交换机和对端的接入设备之间采用双向转发检测(Bidirectional Forwarding Detection，BFD)协议或者网络质量分析(Network Quality Analyzer，NQA)协议，检测链路质量。如果一旦线路出现故障(比如说被施工队挖断)，则探测到链路不通，撤销路由，将报文通过之前配置优先级低的路由，发送到其他专线交换机，由其他专线交换机使用其他线路发送到对端网络。
上述方案中，云厂商通过多个专线交换机接入多根物理线路，然后在专线交换机中配置直连的链路的备份路由，以实现专线的灾备。在专线交换机数量较少的场景下网络较为简单，管理也较为方便，如在两个或者三个专线交换机的场景下。但是当专线交换机和物理线路的数量较多时，网络将变得特别复杂，且难以管理。
如图3所示，如果客户需要接入多根物理线路，而且需要混合云提供多个设备接入，则多个专线交换机之间的网络拓扑则显得很杂乱。图3中每个专线交换机除了把优先级最高的路由的下一跳设置为对端网络以外，还需要给其他的专线交换机做备份路由，避免当线路故障时网络中断。显然，即便 是最简单的方法，也需要在每个专线交换机上配置到其他专线交换机的备份路由，以防止线路故障。
如果此时客户需要再加一个物理线路，再用一个新的专线交换机承载，则需要在新的专线交换机上配置到其他的专线交换机的路由，而且需要新接线路，显然配置复杂，且网络臃肿不堪。
为了解决上述相关技术所存在的技术问题，本申请实施例提供了一种混合云专线接入网络的灾备方法，所述专线接入网络包括混合云网关和对端网络之间的多个专线链路，所述混合云网关上配置有等价路由列表，所述等价路由列表中的每个等价路由对应一个专线链路；所述方法包括：
监测所述多个专线链路的链路状态；
当监测到所述多个专线链路中的第一专线链路出现故障时，向所述混合云网关发送第一专线链路的等价路由撤销请求，以使所述混合云网关将所述第一专线链路的等价路由在所述等价路由列表中撤销。其中，等价路由列表中的等价路由即为到达同一个目的IP或者目的网段存在多条Cost值相等的不同路由路径。
其中，本申请实施例中所指的专线链路即为前述所提及的物理专线中包含的物理线路。并且，混合云网关基于该等价路由列表对用户的业务数据进行传输。
本申请实施例可以将路由的撤销或生效等动作上移到混合云网关，避免在用于与对端网络接入的专线交换机上配置过于复杂的网络，一方面机房接线频次得到降低，另一方面对于专线交换机的管理也简单很多。作为一个示例，如图4所示，在一个业务场景下，云环境(可以包括多个计算节点)通过三条专线(即专线链路)、三个专线交换机和对端网络相连，在混合云网关(与云环境连接)上配置有三条等价路由，下一跳分别是用于与对端网络接入的三个专线交换机，在没有异常的情况下，该业务场景下往返的报文通过该三条线路负载。
另外，本申请实施例借助一个中间件，检测每个专线交换机对应的专线链路的链路质量。在把链路质量状况同步到中间件的进程中，一旦检测到出 现链路故障，则在混合云网关上调整路由，将故障链路对应的流量切换到其他的无故障的等价路由上。作为一个示例，如图5所示，在图4所示的网络中添加一个监控设备(中间件)，如图5中的gobgp，其中，gobgp是github上一个开源的项目，是使用golang实现的bgp功能。监控设备可以用来监控链路的状态。如果某个线路断开或者某个专线交换机宕机了，该监控设备能够迅速监控到链路故障，然后将该链路故障反馈给混合云网关，以便该混合云网关删除对应的路由。
如图6所示，在专线交换机上可以配置BFD协议或NQA协议，以检测链路状态，专线交换机和gobgp(中间件的一个示例)之间配置BGP(Border Gateway Protocol，边界网关协议)，即专线交换机和gobgp上配置有BGP协议。也就是，专线交换机除与对端的接入设备之间配置有BFD协议或NQA协议外，还与gobgp之间配置BGP。其中，BGP是在专线交换机和监控设备之间配置的，用于交换信息，以同步链路状态。
如果最左边的专线交换机的专线因为某种原因中断，则该专线交换机可以通过与对端的接入设备之间配置的BFD协议检测到链路中断，此时，该专线交换机撤销路由。在专线交换机撤销路由后，因为专线交换机和gobgp之间配置有BGP，这个路由撤销的操作可以通过BGP消息同步到gobgp中。gobgp在收到BGP消息以后，调用混合云网关的接口，以通知混合云网关撤销中断链路对应的路由。
下面结合附图，对本申请的一些实施方式作详细说明。在不冲突的情况下，下述的实施例及实施例中的特征可以相互组合。
图7为本申请实施例提供的一种混合云专线接入网络的灾备方法流程示意图。专线接入网络包括混合云网关和对端网络之间的多个专线链路，混合云网关上配置有等价路由列表(例如图4中混合云网关中的等价路由列表“10.20.0.0/24gw1.1.1.1；10.20.0.0/24gw1.1.1.2；10.20.0.0/24gw1.1.1.3”)，等价路由列表中的每个等价路由对应一个专线链路。另外，该等价路由列表可以包括多个，每个等价路由列表对应一个用户。该方法可以应用于监控设备，该监控设备为一个中间件，例如，图6中所示的gobgp。当然，该方法可以应用于其他设备，例如混合云网关。如图7所示，该方法可以包括：
步骤S710，监测多个专线链路的链路状态；
可以通过多种方式对每个专线链路的链路状态进行监测。例如，可以基于BFD协议，监测多个专线链路的链路状态。或者，也可以基于网络质量分析NQA协议，监测所述多个专线链路的链路状态。作为一个示例，监控设备可以分别与每个专线链路的专线交换机建立基于BGP的对等体。需要说明的是，在BGP中相互交换消息的BGP发言者之间互称对等体。监控设备在与专线链路的专线交换机建立对等体后，监控设备和专线交换机称为对等体，可以作为相互交换消息的BGP发言者。各个专线交换机可以基于BFD协议监测各自对应的专线链路的链路状态，而监控设备则可以通过BGP同步专线交换机基于BFD协议/NQA协议检测到的链路状态。
另外，在监控设备分别与每个专线链路的专线交换机建立基于BGP的对等体后，还可以对每个基于BGP建立的对等体进行路由学习，从而可以确定与每个专线链路对应的等价路由。在此之后，当监控设备监测到多个专线链路中的第一专线链路出现故障时，可以从确定出的与每个专线链路对应的等价路由中，确定第一专线链路对应的等价路由，并向混合云网关发送第一专线链路的等价路由撤销请求。
示例性的，结合图5所示，该监控设备可以使用gobgp开源项目实现，该监控设备可以为gobgp。使用gobgp和相关的专线交换机建立BGP对等体(peer)。正常网络环境下图5中的三个专线交换机都要配置并且生效下一跳到对端网络的路由(10.20.0.0/24)。则gobgp通过三个对等体能够学到10.20.0.0/24，并且能够识别到有三个path(路径)，分别是三个专线交换机(1.1.1.1、1.1.1.2以及1.1.1.3)。如果三个专线链路其中一个中断，gobgp通过BGP能够学习对应的路由变化。
步骤S720，当监测到多个专线链路中的第一专线链路出现故障时，向混合云网关发送第一专线链路的等价路由撤销请求，以使混合云网关将第一专线链路的等价路由在等价路由列表中撤销。
结合图6所示，专线交换机(1.1.1.3)对应的专线链路因为某种原因中断，则专线交换机通过BFD协议能够检测到链路中断，然后撤销路由。路由被撤销后，因为专线交换机和gobgp之间有BGP，则这个路由撤销的操作会被同 步到gobgp中。gobgp在收到BGP消息(10.20.0.0/24的下一跳为1.1.1.3撤销)以后，调用混合云网关的接口，在混合云网关中撤销掉中断链路对应的路由。
在一些实施例中，如果专线交换机中断的链路被修复，则专线交换机可以通过BFD协议使相关的路由生效。路由的生效可以通过BGP消息同步到gobgp。gobgp在接收到路由的生效的BGP消息后，可以调用混合云网关的接口添加路由。作为一个示例，该方法还可以包括如下步骤：当监测到多个专线链路中的第二专线链路生效时，向混合云网关发送第二专线链路的等价路由生效请求，以使混合云网关在等价路由列表中添加第二专线链路的等价路由。
本申请实施例通过监测多个专线链路的链路状态；当监测到多个专线链路中的第一专线链路出现故障时，向混合云网关发送第一专线链路的等价路由撤销请求，以使混合云网关将第一专线链路的等价路由在等价路由列表中撤销。以此可以在混合云网关进行路由调整，避免在专线交换机上配置太多的网络内容，简化了机房的网络布线，降低了该灾备方法的配置难度，提升了灾备方法的可用性。并且，通过混合云网关对各专线交换机的等价路由进行调整，使得不需要在各专线交换机之间连接线路，从而简化了网络，当需要再加一个物理线路，不再需要在新的专线交换机上配置到其他的专线交换机的路由以及物理线路。可见，通过本方案可以降低网络配置复杂度，且简化了网络。
为了更清楚阐述本申请实施例所提供的混合云专线接入网络的灾备方法，下面对基于本申请实施例所提供的混合云专线接入网络的灾备方法下的报文转发接收。
混合云网关的等价路由列表包含各专线交换机的等价路由，当混合云网关接收到需要转发的报文后，基于预设的报文转发策略，从多个等价路由中确定出目标路由，并将接收的报文转发至该目标路由对应的专线交换机，以使该专线交换机处理该报文。当某一专线交换机所在专线链路出现链路故障后，混合云网关从等价路由列表中删除出现链路故障的专线交换机对应的等价路由，当再次需要转发报文时，混合云网关从未出现链路故障的专线交换机中确定目标路由。
图8为本申请实施例提供的另一种混合云专线接入网络的灾备方法流程示意图。该专线接入网络包括混合云网关和对端网络之间的多个专线链路；该方法可以应用于混合云网关，当然并不局限于此，如图8所示，该方法可以包括如下步骤：
S810，接收监控设备发送的多个专线链路中的第一专线链路的等价路由撤销请求。
其中，混合云网关上配置有等价路由列表，等价路由列表中的每个等价路由对应一个专线链路。
示例性的，结合图6所示，专线交换机(1.1.1.3)对应的专线链路因为某种原因中断，则专线交换机通过BFD协议能够检测到链路中断，并向gobgp发送表征链路中断的BGP消息，gobgp在收到BGP消息(10.20.0.0/24的下一跳为1.1.1.3撤销)以后，调用混合云网关的接口，向混合云网关发送第一专线链路的等价路由(10.20.0.0/24的下一跳为1.1.1.3)的撤销请求。
S820，将第一专线链路的等价路由在等价路由列表中撤销，以便基于撤销第一专线链路的等价路由后的等价路由列表分发混合云专线业务。
在一些实施例中，如果中断的链路被修复，则路由的生效可以通过BGP消息同步到gobgp，gobgp再调用混合云网关的接口添加路由。作为一个示例，该方法还包括：
步骤1)，接收监控设备发送的多个专线链路中的第二专线链路的等价路由生效请求；
步骤2)，将第二专线链路的等价路由添加在等价路由列表中，以便基于添加第二专线链路的等价路由后的等价路由列表分发混合云专线业务。
本申请实施例通过监测多个专线链路的链路状态；当监测到多个专线链路中的第一专线链路出现故障时，向混合云网关发送第一专线链路的等价路由撤销请求，以使混合云网关将第一专线链路的等价路由在等价路由列表中撤销。以此可以在混合云网关进行路由调整，避免在专线交换机上配置太多的网络内容，简化了机房的网络布线，降低了该灾备方法的配置难度，提升了灾备方法的可用性。并且，通过混合云网关对各专线交换机的等价路由进行调整，使得不需要在各专线交换机之间连接线路，从而简化了网络，当需 要再加一个物理线路，不再需要在新的专线交换机上配置到其他的专线交换机的路由以及物理线路。可见，通过本方案可以降低网络配置复杂度，且简化了网络。
图9为本申请实施例提供的一种混合云专线接入网络的灾备装置结构示意图。专线接入网络包括混合云网关和对端网络之间的多个专线链路，混合云网关上配置有等价路由列表，等价路由列表中的每个等价路由对应一个专线链路；如图9所示，该装置包括：
检测模块901，设置为监测多个专线链路的链路状态；
发送模块902，设置为当监测到多个专线链路中的第一专线链路出现故障时，向混合云网关发送第一专线链路的等价路由撤销请求，以使混合云网关将第一专线链路的等价路由在等价路由列表中撤销。
在一些实施例中，发送模块902还设置为：
当监测到多个专线链路中的第二专线链路生效时，向混合云网关发送第二专线链路的等价路由生效请求，以使混合云网关在等价路由列表中添加第一专线链路的等价路由。
在一些实施例中，检测模块901还设置为：基于BFD协议，检测多个专线链路的链路状态。
在一些实施例中，检测模块901还设置为：分别与每个专线链路的专线交换机建立基于BGP的对等体；
通过基于BGP同步专线交换机基于BFD协议检测到的链路状态。
在一些实施例中，还包括，路由学习模块，设置为对每个基于BGP建立的对等体进行路由学习，确定与每个专线链路对应的等价路由。
本申请实施例通过监测多个专线链路的链路状态；当监测到多个专线链路中的第一专线链路出现故障时，向混合云网关发送第一专线链路的等价路由撤销请求，以混合云网关将第一专线链路的等价路由在等价路由列表中撤销。以此可以在混合云网关进行路由调整，避免在专线交换机上配置太多的网络内容，简化了机房的网络布线，降低了该灾备方法的配置难度，提升了灾备方法的可用性。并且，通过混合云网关对各专线交换机的等价路由进行 调整，使得不需要在各专线交换机之间连接线路，从而简化了网络，当需要再加一个物理线路，不再需要在新的专线交换机上配置到其他的专线交换机的路由以及物理线路。可见，通过本方案可以降低网络配置复杂度，且简化了网络。
图10为本申请实施例提供的一种混合云专线接入网络的灾备装置结构示意图。专线接入网络包括混合云网关和对端网络之间的多个专线链路；如图10所示，该装置包括：
接收模块1001，设置为接收监控设备发送的多个专线链路中的第一专线链路的等价路由撤销请求；其中，混合云网关上配置有等价路由列表，等价路由列表中的每个等价路由对应一个专线链路；
撤销模块1002，设置为将第一专线链路的等价路由在等价路由列表中撤销，以便基于撤销第一专线链路的等价路由后的等价路由列表分发混合云专线业务。
在一些实施例中，接收模块1001还设置为，接收监控设备发送的多个专线链路中的第二专线链路的等价路由生效请求；
添加模块，设置为将第二专线链路的等价路由添加在等价路由列表中，以便基于添加第二专线链路的等价路由后的等价路由列表分发混合云专线业务。
本申请实施例提供的混合云专线接入网络的灾备装置，与上述实施例提供的混合云专线接入网络的灾备方法具有相同的技术特征，所以也能解决相同的技术问题，达到相同的技术效果。
本申请实施例还提供一种混合云专线接入网络的灾备系统。例如图1所示的系统。该系统可以包括：
混合云网关，配置有等价路由列表，等价路由列表中的每个等价路由对应一个专线链路，混合云网关和对端网络之间对应有的多个专线链路；设置为接收监控设备发送的多个专线链路中的第一专线链路的等价路由撤销请求；将第一专线链路的等价路由在等价路由列表中撤销，以便基于撤销第一专线链路的等价路由后的等价路由列表分发混合云专线业务；
监控设备，设置为监测多个专线链路的链路状态；当监测到多个专线链 路中的第一专线链路出现故障时，向混合云网关发送第一专线链路的等价路由撤销请求。
该系统还可以包括专线交换机，该专线交换机用于基于BFD协议，检测自身的链路状态，并将检测到的链路状态同步至监控设备。
如图11所示，本申请实施例提供的一种计算机设备1100，包括：处理器1101、存储器1102和总线，存储器1102存储有处理器1101可执行的机器可读指令，当电子设备运行时，处理器1101与存储器1102之间通过总线通信，处理器1101执行机器可读指令，以执行如上述混合云专线接入网络的灾备方法的步骤。
在一些实施方式中，上述存储器1102和处理器1101能够为通用的存储器和处理器，这里不做具体限定，当处理器1101运行存储器1102存储的计算机程序时，能够执行上述混合云专线接入网络的灾备方法。
对应于上述混合云专线接入网络的灾备方法，本申请实施例还提供了一种计算机可读存储介质，计算机可读存储介质存储有机器可运行指令，计算机可运行指令在被处理器调用和运行时，计算机可运行指令促使处理器运行上述混合云专线接入网络的灾备方法的步骤。
对应于上述混合云专线接入网络的灾备方法，本申请实施例还提供一种包含指令的计算机程序产品，包含指令的计算机程序产品在计算机上运行时，使得计算机执行上述混合云专线接入网络的灾备方法。
对应于上述混合云专线接入网络的灾备方法，本申请实施例还提供一种计算机程序，计算机程序在计算机上运行时，使得计算机执行上述混合云专线接入网络的灾备方法。
本申请实施例所提供的混合云专线接入网络的灾备装置可以为设备上的特定硬件或者安装于设备上的软件或固件等。本申请实施例所提供的装置，其实现原理及产生的技术效果和前述方法实施例相同，为简要描述，装置实施例部分未提及之处，可参考前述方法实施例中相应内容。所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，前述描述的系统、装置和单元的具体工作过程，均可以参考上述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的实施例中，应该理解到，所揭露装置和方法，可以通过其它的方式实现。以上所描述的装置实施例仅仅是示意性的，例如，上述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，又例如，多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些通信接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
上述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
在本申请所提供的几个实施例中，应该理解到，所揭露的装置和方法，也可以通过其它的方式实现。以上所描述的装置实施例仅仅是示意性的，例如，附图中的流程图和框图显示了根据本申请的多个实施例的装置、方法和计算机程序产品的可能实现的体系架构、功能和操作。在这点上，流程图或框图中的每个方框可以代表一个模块、程序段或代码的一部分，上述模块、程序段或代码的一部分包含一个或多个用于实现规定的逻辑功能的可执行指令。也应当注意，在有些作为替换的实现方式中，方框中所标注的功能也可以以不同于附图中所标注的顺序发生。例如，两个连续的方框实际上可以基本并行地执行，它们有时也可以按相反的顺序执行，这依所涉及的功能而定。也要注意的是，框图和/或流程图中的每个方框、以及框图和/或流程图中的方框的组合，可以用执行规定的功能或动作的专用的基于硬件的系统来实现，或者可以用专用硬件与计算机指令的组合来实现。
另外，在本申请提供的实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
上述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对相关技术做出贡献的部分或者该技术方案的部分可 以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例上述混合云专线接入网络的灾备方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
应注意到：相似的标号和字母在下面的附图中表示类似项，因此，一旦某一项在一个附图中被定义，则在随后的附图中不需要对其进行进一步定义和解释，此外，术语“第一”、“第二”、“第三”等仅用于区分描述，而不能理解为指示或暗示相对重要性。
最后应说明的是：以上实施例，仅为本申请的具体实施方式，用以说明本申请的技术方案，而非对其限制，本申请的保护范围并不局限于此，尽管参照前述实施例对本申请进行了详细的说明，本领域的普通技术人员应当理解：任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，其依然可以对前述实施例所记载的技术方案进行修改或可轻易想到变化，或者对其中部分技术特征进行等同替换；而这些修改、变化或者替换，并不使相应技术方案的本质脱离本申请实施例技术方案的范围。都应涵盖在本申请的保护范围之内。以上仅为本申请的较佳实施例，并不用以限制本申请，凡在本申请的精神和原则之内，所做的任何修改、等同替换、改进等，均应包含在本申请保护的范围之内。
工业实用性
本申请实施例提供的一种混合云专线接入网络的灾备方法及装置，通过监测多个专线链路的链路状态；当监测到多个专线链路中的第一专线链路出现故障时，向混合云网关发送第一专线链路的等价路由撤销请求，以使混合云网关将第一专线链路的等价路由在等价路由列表中撤销。以此可以在混合云网关进行路由调整，避免在专线交换机上配置太多的网络内容，简化了机房的网络布线，降低了该灾备方法的配置难度，提升了灾备方法的可用性本申请。并且，通过混合云网关对各专线交换机的等价路由进行调整，使得不需要在各专线交换机之间连接线路，从而简化了网络，当需要再加一个物理 线路，不再需要在新的专线交换机上配置到其他的专线交换机的路由以及物理线路。可见，通过本方案可以降低网络配置复杂度，且简化了网络。

Claims (14)

  1. 一种混合云专线接入网络的灾备方法，所述专线接入网络包括混合云网关和对端网络之间的多个专线链路，所述混合云网关上配置有等价路由列表，所述等价路由列表中的每个等价路由对应一个专线链路；所述方法包括：
    监测所述多个专线链路的链路状态；
    当监测到所述多个专线链路中的第一专线链路出现故障时，向所述混合云网关发送第一专线链路的等价路由撤销请求，以使所述混合云网关将所述第一专线链路的等价路由在所述等价路由列表中撤销。
  2. 根据权利要求1所述的方法，其中，还包括：
    当监测到所述多个专线链路中的第二专线链路生效时，向所述混合云网关发送第二专线链路的等价路由生效请求，以使所述混合云网关在等价路由列表中添加所述第二专线链路的等价路由。
  3. 根据权利要求1或2所述的方法，其中，所述监测所述多个专线链路的链路状态的步骤，包括：
    基于双向转发检测BFD协议，监测所述多个专线链路的链路状态；或者
    基于网络质量分析NQA协议，监测所述多个专线链路的链路状态。
  4. 根据权利要求3所述的方法，其中，所述基于BFD协议，监测所述多个专线链路的链路状态的步骤包括：
    分别与每个所述专线链路的专线交换机建立基于BGP的对等体；
    通过所述BGP，同步所述专线交换机基于BFD协议检测到的链路状态；
    所述基于网络质量分析NQA协议，监测所述多个专线链路的链路状态，包括：
    分别与每个所述专线链路的专线交换机建立基于BGP的对等体；
    通过所述BGP，同步所述专线交换机基于网络质量分析NQA协议检测到的链路状态。
  5. 根据权利要求4所述的方法，其中，在所述分别与每个所述专线链路的专线交换机建立基于BGP的对等体的步骤之后，所述方法还包括：
    对每个基于BGP建立的对等体进行路由学习，确定与每个所述专线链路对应的等价路由。
  6. 一种混合云专线接入网络的灾备方法，应用于专线接入网络中的混合云网关，所述专线接入网络还包括对端网络之间的多个专线链路；所述方法包括：
    接收监控设备发送的所述多个专线链路中的第一专线链路的等价路由撤销请求；其中，所述混合云网关上配置有等价路由列表，所述等价路由列表中的每个等价路由对应一个专线链路；
    将所述第一专线链路的等价路由在所述等价路由列表中撤销，以便基于撤销所述第一专线链路的等价路由后的等价路由列表分发混合云专线业务。
  7. 根据权利要求6所述的方法，其中，还包括：
    接收监控设备发送的所述多个专线链路中的第二专线链路的等价路由生效请求；
    将所述第二专线链路的等价路由添加在所述等价路由列表中，以便基于添加所述第二专线链路的等价路由后的等价路由列表分发混合云专线业务。
  8. 一种混合云专线接入网络的灾备装置，所述专线接入网络包括混合云网关和对端网络之间的多个专线链路，所述混合云网关上配置有等价路由列表，所述等价路由列表中的每个等价路由对应一个专线链路；所述装置包括：
    检测模块，设置为监测所述多个专线链路的链路状态；
    发送模块，设置为当监测到所述多个专线链路中的第一专线链路出现故障时，向所述混合云网关发送第一专线链路的等价路由撤销请求，以使所述混合云网关将所述第一专线链路的等价路由在所述等价路由列表中撤销。
  9. 一种混合云专线接入网络的灾备装置，所述专线接入网络包括混合云网关和对端网络之间的多个专线链路；所述装置包括：
    接收模块，设置为接收监控设备发送的所述多个专线链路中的第一专线链路的等价路由撤销请求；其中，所述混合云网关上配置有等价路由列表，所述等价路由列表中的每个等价路由对应一个专线链路；
    撤销模块，设置为将所述第一专线链路的等价路由在所述等价路由列表中撤销，以便基于撤销所述第一专线链路的等价路由后的等价路由列表分发混合云专线业务。
  10. 一种混合云专线接入网络的灾备系统，包括：
    混合云网关，配置有等价路由列表，所述等价路由列表中的每个等价路由对应一个专线链路，混合云网关和对端网络之间对应有的多个专线链路；设置为接收监控设备发送的所述多个专线链路中的第一专线链路的等价路由撤销请求；将所述第一专线链路的等价路由在所述等价路由列表中撤销，以便基于撤销所述第一专线链路的等价路由后的等价路由列表分发混合云专线业务；
    监控设备，设置为监测所述多个专线链路的链路状态；当监测到所述多个专线链路中的第一专线链路出现故障时，向所述混合云网关发送第一专线链路的等价路由撤销请求。
  11. 一种计算机设备，包括存储器、处理器，所述存储器中存储有可在所述处理器上运行的计算机程序，所述处理器执行所述计算机程序时实现上述权利要求1至7任一项所述的方法的步骤。
  12. 一种计算机可读存储介质，所述计算机可读存储介质存储有机器可运行指令，所述计算机可运行指令在被处理器调用和运行时，所述计算机可运行指令促使所述处理器运行所述权利要求1至7任一项所述的方法。
  13. 一种包含指令的计算机程序产品，所述包含指令的计算机程序产品在计算机上运行时，使得计算机执行权利要求1至7任一所述的方法步骤。
  14. 一种计算机程序，所述计算机程序在计算机上运行时，使得计算机执行权利要求1至7任一所述的方法步骤。
PCT/CN2021/090034 2020-05-09 2021-04-26 混合云专线接入网络的灾备方法及装置 WO2021227863A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010391003.8A CN113630314B (zh) 2020-05-09 2020-05-09 混合云专线接入网络的灾备方法及装置
CN202010391003.8 2020-05-09

Publications (1)

Publication Number Publication Date
WO2021227863A1 true WO2021227863A1 (zh) 2021-11-18

Family

ID=78377723

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/090034 WO2021227863A1 (zh) 2020-05-09 2021-04-26 混合云专线接入网络的灾备方法及装置

Country Status (2)

Country Link
CN (1) CN113630314B (zh)
WO (1) WO2021227863A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114785670A (zh) * 2022-04-21 2022-07-22 中国建设银行股份有限公司 一种专线接入方法及装置
CN116566803A (zh) * 2023-06-15 2023-08-08 华章数据技术有限公司 一种基于流量监测的线路切换系统及方法

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114726780B (zh) * 2022-03-23 2024-04-02 阿里云计算有限公司 一种云上到云下的通信方法、设备及存储介质
CN115333994B (zh) * 2022-08-01 2024-05-31 北京金山云网络技术有限公司 实现vpn路由快速收敛的方法、装置以及电子设备
CN115442287B (zh) * 2022-08-10 2024-04-05 北京金山云网络技术有限公司 基于权重的专线网关方法以及装置
CN117596284B (zh) * 2024-01-18 2024-03-29 腾讯科技（深圳）有限公司 数据传输的方法、装置、计算机设备和存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109639557A (zh) * 2019-02-11 2019-04-16 北京百度网讯科技有限公司 用于网络通信的方法、装置和系统
CN109728956A (zh) * 2019-01-29 2019-05-07 网联清算有限公司 链路切换方法、装置、计算机设备和存储介质
CN110191067A (zh) * 2019-05-24 2019-08-30 深圳前海微众银行股份有限公司 专线网络访问控制方法、装置、设备及可读存储介质
US10579357B2 (en) * 2017-07-20 2020-03-03 International Business Machines Corporation Cognitive expected program code installation result assessment

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012165446A1 (ja) * 2011-05-30 2012-12-06 日本電気株式会社 通信経路制御システム、及び通信経路制御方法
CN102325154B (zh) * 2011-07-13 2014-11-05 百度在线网络技术（北京）有限公司 具有容灾备份功能的网络系统及实现容灾备份功能的方法
CN103812770B (zh) * 2012-11-12 2017-04-12 华为技术有限公司 云业务报文重定向的方法、系统和云网关
CN104253745B (zh) * 2013-06-29 2018-05-29 华为技术有限公司 一种路由撤销方法和网络设备
US9515918B2 (en) * 2013-11-18 2016-12-06 International Business Machines Corporation Computing forwarding tables for link failures
CN105681075B (zh) * 2015-12-30 2019-06-14 中国银联股份有限公司 基于混合云平台的网络管理系统
CN107948086A (zh) * 2016-10-12 2018-04-20 北京金山云网络技术有限公司 一种数据包发送方法、装置及混合云网络系统
WO2019135249A1 (en) * 2018-01-05 2019-07-11 Telefonaktiebolaget Lm Ericsson (Publ) Data center failure management in an sdn deployment using border gateway node control
CN109547269B (zh) * 2019-01-04 2021-12-14 烽火通信科技股份有限公司 一种ip ran设备实现lsp保护的方法及装置
CN109936629B (zh) * 2019-02-27 2021-09-03 浪潮云信息技术股份公司 一种混合云网络互连方法及系统
CN109768906B (zh) * 2019-03-29 2021-04-27 新华三技术有限公司 一种子网专线配置方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10579357B2 (en) * 2017-07-20 2020-03-03 International Business Machines Corporation Cognitive expected program code installation result assessment
CN109728956A (zh) * 2019-01-29 2019-05-07 网联清算有限公司 链路切换方法、装置、计算机设备和存储介质
CN109639557A (zh) * 2019-02-11 2019-04-16 北京百度网讯科技有限公司 用于网络通信的方法、装置和系统
CN110191067A (zh) * 2019-05-24 2019-08-30 深圳前海微众银行股份有限公司 专线网络访问控制方法、装置、设备及可读存储介质

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114785670A (zh) * 2022-04-21 2022-07-22 中国建设银行股份有限公司 一种专线接入方法及装置
CN116566803A (zh) * 2023-06-15 2023-08-08 华章数据技术有限公司 一种基于流量监测的线路切换系统及方法
CN116566803B (zh) * 2023-06-15 2024-04-05 华章数据技术有限公司 一种基于流量监测的线路切换系统及方法

Also Published As

Publication number Publication date
CN113630314B (zh) 2022-09-16
CN113630314A (zh) 2021-11-09

Similar Documents

Publication Publication Date Title
WO2021227863A1 (zh) 混合云专线接入网络的灾备方法及装置
US20220131740A1 (en) Method and system of a dynamic high-availability mode based on current wide area network connectivity
US7751329B2 (en) Providing an abstraction layer in a cluster switch that includes plural switches
JP4796184B2 (ja) エッジノード冗長システム
CN102439903B (zh) 实现容灾备份的方法、设备及系统
EP1905203B1 (en) Router and method for protocol process migration
RU2530338C2 (ru) Предварительно подготовленное сопряжение на основе состояния линий связи поставщиков (plsb) с маршрутизируемым резервированием
US9264302B2 (en) Methods and systems with enhanced robustness for multi-chassis link aggregation group
CN111865779B (zh) 一种路由同步方法及跨设备链路聚合组
US9137141B2 (en) Synchronization of load-balancing switches
US8861341B2 (en) Backup network connectivity
US9385944B2 (en) Communication system, path switching method and communication device
US20140067983A1 (en) Bi-directional synchronization enabling active-active redundancy for load-balancing switches
US11349735B2 (en) Faster fault-detection mechanism, for example using bidirectional forwarding detection (BFD), on network nodes and/or hosts multihomed using a link aggregation group (LAG)
WO2020057445A1 (zh) 一种通信系统、方法及装置
CN101692654A (zh) 一种HUB-Spoken组网的方法、系统及设备
US7869351B2 (en) Communication techniques and generic layer 3 automatic switching protection
KR20200072941A (ko) 실시간 오류 감지를 통한 vrrp 기반의 네트워크 장애 대응 방법 및 장치
WO2021098806A1 (zh) 报文传输路径的切换方法、设备和系统
CN112995027A (zh) 路由发布方法及vtep节点
US10887207B2 (en) System and method for determining branch gateway device availability in computer networks
US9774518B1 (en) Methods and apparatus for a distributed control plane
WO2014044088A1 (zh) L2tp网络的保护方法、装置及系统
CN116055393A (zh) 专线通信方法、装置及系统
US20140293827A1 (en) Method And Apparatus For Peer Node Synchronization

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21803278

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21803278

Country of ref document: EP

Kind code of ref document: A1