Seamless Multi-Cloud SDWAN Disaster Recovery Using Orchestration Planes
By utilizing virtual bonds in the orchestration plane to manage SD-WAN migration, the solution addresses the limitations of third-party witness components, enhancing reliability and visibility in multi-cloud architectures for seamless disaster recovery.
Patent Information
- Application Number
- KR1020227000637
- Authority / Receiving Office
- KR · KR
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2020-03-02
- Filing Date
- 2020-06-30
- Publication Date
- 2026-11-06
- Estimated Expiration
- 2040-06-30
AI Technical Summary
Current SD-WAN migration solutions in multi-cloud architectures rely on third-party witness components, which introduce additional burdens, lack visibility, are single points of failure, and require high availability, complicating the management and selection of destination clouds during failover events.
The proposed solution eliminates the need for third-party witness components by using virtual bonds within the orchestration plane to monitor and manage SD-WAN migration across clouds, ensuring secure connections and selecting destination clouds based on policies and health metrics.
This approach enhances SD-WAN migration by eliminating single points of failure, improving visibility, and optimizing destination cloud selection, thereby ensuring seamless and reliable disaster recovery without the need for third-party components.
Smart Images

Figure R1020227000637_ABST
Abstract
Description
Technology Field
[0001] Cross-reference regarding related applications
[0002] This application claims the benefit of U.S. Provisional Application No. 62 / 872,125, filed July 9, 2019, titled “SEAMLESS MULTI-CLOUD SDWAN DISASTER RECOVERY USING ORCHESTRATION PLANE,” and the benefit and priority of U.S. Regular Application No. 16 / 806,750, filed March 2, 2020, titled “SEAMLESS MULTI-CLOUD SDWAN DISASTER RECOVERY USING ORCHESTRATION PLANE,” and these U.S. applications are incorporated herein by reference in their entirety.
[0003] The gist of the invention of this disclosure generally relates to the field of computer networking, and more specifically, to systems and methods for managing the migration of software defined network components in a multi-cloud configuration from a source cloud to a destination cloud. Background Technology
[0004] A Software Defined Network (SD-WAN) provides connectivity for computing devices (e.g., servers, workstations, desktop computers, laptop computers, tablets, mobile phones, etc.) and objects (e.g., desk phones, security cameras, lighting, heating, ventilation, and air conditioning (HVAC), windows, doors, locks, medical devices, industrial and manufacturing equipment, etc.) within environments such as offices, hospitals, universities, and factories. SD-WAN implementations can take place in a multi-cloud architecture.
[0005] In the event of a failure in a multi-cloud architecture, specific SD-WAN solutions implemented using this architecture may need to be moved and migrated from one cloud architecture to another. Current solutions to enable this migration rely on third-party witness components that need to be stitched into the SD-WAN fabric. Furthermore, managing the lifecycle of third-party witness components places an additional burden on the network, visibility into the health of third-party witness components is minimal or almost non-existent, and third-party witness components are a single point of failure requiring high availability and dependency. Brief explanation of the drawing
[0006] To provide a more complete understanding of the present disclosure and its features and advantages, reference is made to the following descriptions taken together with the accompanying drawings: FIG. 1 illustrates a network architecture according to an embodiment of the present disclosure; FIG. 2 illustrates an example of a multi-cloud architecture having a third-party witness component for managing SD-WAN migration according to an embodiment of the present disclosure; FIG. 3 illustrates an example of a multi-cloud architecture for managing SD-WAN migration without relying on a third-party witness component, according to an aspect of the present disclosure; FIG. 4 illustrates an exemplary method for managing SD-WAN migration in a multi-cloud architecture according to an embodiment of the present disclosure; and FIGS. 5a and 5b illustrate examples of systems according to an embodiment of the present disclosure. Specific details for implementing the invention
[0007] Various exemplary embodiments of the disclosure are discussed in detail below. While specific embodiments are discussed, it should be understood that this is done solely for illustrative purposes. A person skilled in the art will recognize that other components and configurations may be used without departing from the spirit and scope of the disclosure. Accordingly, the following description and drawings are illustrative and should not be interpreted as restrictive. Numerous specific details are described to provide a thorough understanding of the disclosure. However, in some instances, widely known or existing details are not described to avoid obscuring the description. One embodiment or reference to an embodiment in this disclosure may be a reference to the same embodiment or any embodiment; such references mean at least one of the embodiments.
[0008] References to "one embodiment" or "an embodiment" mean that a specific feature, structure, or characteristic described in relation to an embodiment is included within at least one embodiment of the disclosure. The appearance of the phrase "in one embodiment" in various places within the specification does not necessarily refer to the same embodiment, nor to separate or alternative embodiments that are mutually exclusive of the other embodiments. Additionally, various features that may be present in some embodiments and not in others are described.
[0009] Without intent to limit the scope of the disclosure, examples of apparatuses, devices, methods, and related results according to embodiments of the disclosure are given below. Titles or subtitles may be used in the examples for the convenience of the reader and should not in any way limit the scope of the disclosure. Unless otherwise defined, technical and scientific terms used herein have the same meaning as commonly understood by a person skilled in the art to which this disclosure pertains. In the event of a conflict, this document, including definitions, shall prevail.
[0010] Additional features and advantages of the disclosure will be described in the following description and, in part, will be self-evident from the description or can be learned by practicing the principles disclosed herein. Features and advantages of the disclosure can be realized and obtained by the mechanisms and combinations indicated in detail in the appended claims. These and other features of the disclosure will become more fully apparent from the following description and the appended claims or can be learned by practicing the principles described herein.
[0011] The detailed description provided below is intended to describe various configurations of the embodiments and is not intended to represent the only configurations in which the gist of this disclosure can be implemented. The accompanying drawings are incorporated herein and constitute part of the detailed description. The detailed description includes specific details for the purpose of providing a more thorough understanding of the gist of this disclosure. However, it will be clear and obvious that the gist of this disclosure is not limited to the specific details described herein and can be implemented without these details. In some instances, structures and components are depicted in block diagram form to avoid obscuring the concepts of the gist of this disclosure.
[0012] outline
[0013] Aspects of the invention are described in independent claims, and preferred features are described in dependent claims. Features of one aspect may be applied to each aspect alone or in combination with other aspects.
[0014] As mentioned above, currently, Software Defined Network (SD-WAN) fabric owners must create third-party witness components and stitch them into the SD-WAN fabric to manage the migration of SD-WAN from a source cloud to a destination cloud in a multi-cloud architecture. The present disclosure provides solutions and mechanisms for achieving the migration of SD-WAN components from a source cloud to a destination cloud in a multi-cloud architecture without using third-party witness components, thereby eliminating the disadvantages of dependency on third-party witness components.
[0015] In one embodiment, the method comprises monitoring clusters of virtual management components of a plurality of cloud networks using virtual bonds of network orchestration components, wherein the corresponding virtual management components of one of the plurality of cloud networks implement one or more services of a Software-Defined Wide Access Network (SD-WAN) solution; detecting a failover event in one of the plurality of cloud networks using virtual bonds; and identifying a new destination cloud network for migrating one or more services of the SD-WAN solution from the source cloud network where the failover event is detected by virtual bonds.
[0016] In another aspect, each of the virtual bonds has an established security channel to each of the virtual management components in each of the clusters.
[0017] In another aspect, monitoring the clusters includes determining the number of inactive virtual management components of each cloud network among a number of cloud networks.
[0018] In another embodiment, detecting a failover event comprises determining an active status or an inactive status for a corresponding cluster by each of the virtual bonds and based on the number of inactive virtual management components in one of the plurality of cloud networks; and determining a failover event for one of the plurality of cloud networks when a first threshold number of virtual bonds determines that the number of inactive virtual management components in the corresponding cluster is equal to a second threshold.
[0019] In another embodiment, identifying a new destination cloud network includes determining the combined weight of virtual management components in a target destination cloud; and identifying the target destination cloud as a new destination cloud when the combined weight of virtual management components in the target destination cloud is greater than or equal to a third threshold.
[0020] In another embodiment, determining the combined weight is based on the corresponding assigned weight, the corresponding configuration parameters, and the corresponding location of each virtual management component among the virtual management components in the target destination cloud.
[0021] In another aspect, the method further comprises communicating identification information of a new destination cloud to virtual smart components in the network control and data plane, and the virtual smart components trigger network edge devices to shift to a cluster of virtual network components of the new destination cloud.
[0022] In one embodiment, the network controller includes memory storing computer-readable instructions and one or more processors. The one or more processors execute computer-readable instructions to monitor clusters of virtual management components of a plurality of cloud networks—wherein the corresponding virtual management components of one of the plurality of cloud networks implement one or more services of a software-defined wide area access network (SD-WAN) solution—; detect a failover event in one of the plurality of cloud networks; and are configured as virtual bonds of the software-defined wide area network (SD-WAN) solution to identify a new destination cloud network for migrating one or more services of the SD-WAN solution from the source cloud network where the failover event is detected.
[0023] In one embodiment, one or more non-transient computer-readable media comprise computer-readable instructions, and when executed by one or more processors, the computer-readable instructions enable one or more processors to monitor clusters of virtual management components of a plurality of cloud networks—corresponding virtual management components of one of the plurality of cloud networks implement one or more services of a software-defined wide area access network (SD-WAN) solution—; detect a failover event in one of the plurality of cloud networks; and to function as virtual bonds of a software-defined wide area network (SD-WAN) solution to identify a new destination cloud network for migrating one or more services of the SD-WAN solution from the source cloud network where the failover event is detected.
[0024] details
[0025] Using such third-party witness components has several disadvantages. First, the third-party witness component needs to be stitched into the SD-WAN fabric. Second, the third-party witness component cannot select the correct destination cloud for migration based on policies executed at the edge of the network overlay. Third, the third-party witness component needs to establish secure communication with the vManage cluster in a multi-cloud architecture. Fourth, since vBond is in the orchestration plane of the overlay, the third-party witness component needs to have a persistent secure connection with vBond to configure the destination cloud's vManage cluster as valid and ensure control and data plane migration to the destination vManage cluster. Fifth, the management of the third-party witness component's lifecycle lies with the SD-WAN fabric owner. Sixth, there is no visibility into the health of the third-party witness component. Finally, the third-party witness component is a single point of failure and, accordingly, requires high reliability and availability.
[0026] To manage the migration of SD-WANs across a multi-cloud architecture in the event of a failure in the architecture, the solutions proposed by this disclosure eliminate the use of third-party witness components and address the aforementioned disadvantages of using third-party witness components. The proposed solutions will be fully described below.
[0027] The introduction begins with an overview of SD-WAN and the corresponding architecture.
[0028] FIG. 1 illustrates a network architecture according to an embodiment of the present disclosure. An example of an implementation of the network architecture (100) is a Cisco® Software Defined Wide Area Network (SD-WAN) architecture. However, a person skilled in the art will understand that for the network architecture (100) and any other system discussed in the present disclosure, there may be additional or fewer components in similar or alternative configurations. The examples and illustrations provided in the present disclosure are for brevity and clarity. Other exemplary embodiments may include different numbers and / or types of elements, but a person skilled in the art will recognize that such variations do not depart from the scope of the present disclosure.
[0029] In this example, the network architecture (100) may include an orchestration plane (102), a management plane (120), a control plane (130), and a data plane (140). The orchestration plane (102) may assist in the automatic on-boarding of edge network devices (142) (e.g., switches, routers, etc.) in an overlay network. The orchestration plane (102) may include one or more physical or virtual network orchestrator appliances (104). The network orchestrator appliances (104) may perform initial authentication of the edge network devices (142) and may orchestrate connectivity between devices in the control plane (130) and the data plane (140). In some exemplary embodiments, network orchestrator devices (104) may also enable communication of devices located behind a Network Address Translation (NAT). In some exemplary embodiments, physical or virtual Cisco® SD-WAN vBond devices may operate as network orchestrator devices (104).
[0030] The management plane (120) may be responsible for the central configuration and monitoring of the network. The management plane (120) may include one or more physical or virtual network management devices (122). The network management devices (122) may provide centralized management of the network through a graphical user interface to enable a user to monitor, configure, and maintain edge network devices (142) and links (e.g., Internet transport network (160), Multi-Protocol Label Switching (MPLS) network (162), 4G / LTE network (164)) in underlay and overlay networks. The network management devices (122) may support multi-tenancy and enable centralized management of logically isolated networks associated with different entities (e.g., enterprises, departments within enterprises, groups within departments, etc.). Alternatively or additionally, the network management devices (122) may be dedicated network management systems for a single entity. In some exemplary embodiments, physical or virtual Cisco® SD-WAN vManage devices may operate as network management devices (122).
[0031] The management plane (120) may also include an analysis engine (124) for providing visibility into applications and network performance over time, such as best and worst performance applications, most bandwidth-consuming applications, anomalous application families (e.g., applications whose bandwidth consumption changes over time), network availability and circuit availability, carrier health, best and worst performance tunnels, etc. The analysis engine (124) may generate graphical representations of the overlay network and may enable users to drill down to display the characteristics of a single carrier, tunnel, or application at a specific time and present the same information to the network administrator through the user interface of network management devices (122) (e.g., vManage). The user interface may serve as an entrance point for an interactive overview of the network and more details. In some exemplary embodiments, the user interface may display information for the last 24 hours and may enable the user to drill down to select different time periods for different data sets to display. The user interface may also display data on network availability, WAN performance by the carrier, and applications, among other network analyses.
[0032] In some exemplary embodiments, the analysis engine (124) may provide application performance having a Virtual Quality of Experience (vQoE) value that can be customized for individual applications. This value may range from 0 to 10, where 0 is worst performance and 10 is best. The analysis engine may calculate vQoE based on latency, loss, and jitter, and may customize the calculation for each application.
[0033] The control plane (130) can establish and maintain a network topology and make determinations about where traffic flows. The control plane (130) may include one or more physical or virtual network controller devices (132). Network controller devices (132) can establish secure connections to each edge network device (142) and distribute root and policy information through control plane protocols (e.g., Overlay Management Protocol (OMP), Open Shortest Path First (OSPF), Intermediate System to Intermediate System (IS-IS), Border Gateway Protocol (BGP), Protocol-Independent Multicast (PIM), Internet Group Management Protocol (IGMP), Internet Control Message Protocol (ICMP), Address Resolution Protocol (ARP), Bidirectional Forwarding Detection (BFD), Link Aggregation Control Protocol (LACP), etc.). In some exemplary embodiments, network controller devices (132) may operate as route reflectors. Network controller devices (132) may also orchestrate secure connectivity between edge network devices (142) and in the data plane (140) among them.For example, in some exemplary embodiments, network controller devices (132) can distribute crypto key information between edge network devices (142). This can allow the network to support secure network protocols or applications (e.g., Internet Protocol Security (IPSec), Transport Layer Security (TLS), Secure Shell (SSH), etc.) without Internet Key Exchange (IKE) and can enable the scalability of the network. In some exemplary embodiments, physical or virtual Cisco® SD-WAN vSmart controllers can operate as network controller devices (132).
[0034] The data plane (140) may be responsible for forwarding packets based on decisions from the control plane (130). The data plane (140) may include edge network devices (142), which may be physical or virtual network devices. The edge network devices (142) may operate at the edges of various network sites associated with an organization, such as in one or more data centers or colocation centers (150), campus networks (152), branch office networks (154), home office networks (156), etc., or in the cloud (e.g., Infrastructure as a Service (IaaS), Platform as a Service (PaaS), SaaS, and other cloud service provider networks).Edge network devices (142) are one or more Internet transmission networks (160) (e.g., Digital Subscriber Line (DSL), cable, etc.), MPLS networks (162) (or other private packet-switched networks (e.g., Metro Ethernet, Frame Relay, Asynchronous Transfer Mode (ATM), etc.)), mobile networks (164) (e.g., 3G, 4G / LTE, 5G, etc.), or other WAN technologies (e.g., Synchronous Optical Networking (SONET), Synchronous Digital Hierarchy (SDH), Dense Wavelength Division Multiplexing (DWDM), or other optical fiber technologies; dedicated lines (e.g., Tl / El, T3 / E3, etc.); public switched telephone networks Secure data plane connectivity between sites can be provided over one or more WAN transmissions, such as through a Public Switched Network (PSTN), an Integrated Services Digital Network (ISDN), or other private circuit-switched networks; a small aperture terminal (VS AT) or other satellite networks; etc. Edge network devices (142) can be responsible for traffic forwarding, security, encryption, quality of service (QoS), and routing (e.g., BGP, OSPF, etc.), among other tasks. In some embodiments, physical or virtual Cisco® SD-WAN vEdge routers can operate as edge network devices (142).
[0035] FIG. 2 illustrates an example of a multi-cloud architecture having a third-party witness component for managing SD-WAN migration according to an embodiment of the present disclosure.
[0036] The architecture (200) is a multi-cloud architecture having multiple cloud structures. The number of multiple cloud structures may be two or more. In the example of FIG. 2, multiple cloud structures (202-1, 202-2, ..., 202-N) are shown, where N is an integer greater than or equal to 3. Each of the multiple cloud structures (202-1, 202-2, ..., 202-N) may have a cluster of vManages (e.g., within the corresponding management plane (120) described above with reference to FIG. 1). For example, cloud structure (202-1) has a cluster (204-1) of interconnected vManages (205-1) (in this example, including three vManages (205-1), but the number of vManages (205-1) may differ, such as 1, 2, 3, etc.). Similarly, the cloud structure (202-2) has a cluster (204-2) of interconnected vManages (205-2), the cloud structure (202-N) has a cluster (204-N) of interconnected vManages (205-N), and so on. In the example of FIG. 2, the SD-WAN solution is assumed to be currently deployed and operating on the cloud structure (202-1). Therefore, the cloud structure (202-1) can be referred to as the source cloud.
[0037] vManage components, such as vManage (205-1), are graphical user interface-based controllers for provisioning and managing SD-WAN infrastructure deployed in the corresponding cloud of the multi-cloud architecture of FIG. 2. vManage provides the capability to manage all aspects of the WAN, from provisioning, monitoring, and upgrading routers to application visibility and WAN fault recovery.
[0038] The architecture (200) further includes control and data plane components (206) for an SD-WAN solution currently operating on a cloud architecture (202-1). Among other components known to those skilled in the art, the control and data plane components (202) include a number of vEdge (206-1) and vSmart (206-2) components. The number of vEdge (206-1) and vSmart (206-2) is not limited to that shown in FIG. 2, but may be more or fewer. A vSmart is a centralized brain / controller of an SD-WAN solution that implements policies and connectivity between SD-WAN branches. The centralized policy engine in Cisco vSmart controllers provides policy constructs for manipulating routing information, access control, segmentation, extranets, and service chaining. As described above, vEdges are SD-WAN routers that can operate as edge network devices.
[0039] The network architecture (200) further includes a third-party witness component (208) currently used to manage the migration of SD-WAN solutions from a source cloud (e.g., cloud structure (202-1)) to a destination cloud (e.g., one of the cloud structures (202-2, ..., 202-N)) when a specific cloud structure and support cluster of vManages fails (this migration process may also be referred to as disaster recovery).
[0040] As mentioned above, the third-party witness component for disaster recovery and SD_WAN solution migration has several disadvantages. First, the third-party witness component (208) needs to be stitched into the fabric as illustrated in FIG. 2. Second, the third-party witness component (209) cannot select the correct destination cloud based on policies executed on the edge of the overlay. Third, the third-party witness component (208) needs to establish a secure connection with the vManage clusters of source and destination cloud structures (e.g., one of the clusters (204-1), and clusters (204-2, ..., 204-N). Fourth, since vBonds are orchestrators of overlays, the third-party witness component (208) needs to have a permanent secure connection with the vBond to configure the destination vManage cluster as valid (e.g., one of the vManage clusters (204-2, ..., 204-N)). This will ensure the control of the SD-WAN solution and the migration of the data plane to the destination vManage cluster. Fifth, the responsibility for managing the lifecycle of the third-party witness component (208) lies with the fabric owners. Sixth, the third-party witness component (208) relies on a polling model that checks only the reachability of the currently operating vManage cluster, and accordingly, there is no visibility into the service health of the third-party witness component. Seventh, since the third-party witness component (208) is therefore a single point of failure, high availability and reliability of the third-party witness component (208) must be ensured.
[0041] Given the above disadvantages of relying on a third-party witness component (208) to manage SD-WAN migration and disaster recovery, the structure and process of FIGS. 3 and 4 are described below to address these disadvantages.
[0042] FIG. 3 illustrates an example of a multi-cloud architecture for managing SD-WAN migration without relying on third-party witness components, according to an aspect of the present disclosure. When describing the architecture (300) of FIG. 3, the components identical to the corresponding parts of FIG. 2 are numbered identically and, accordingly, will not be described further for brevity.
[0043] In contrast to the architecture (200), the architecture (300) has an orchestration plane (302) that may be identical to the orchestration plane (102) of FIG. 1. The orchestration plane (302) has one or more vBonds (304) which are orchestrators capable of facilitating the initial bring-up of the SD-WAN solution by performing authentication and authorization of all elements to the SD-WAN. The vBond orchestrators (304) also provide information on how each of the components of the SD-WAN solution connects to other components.
[0044] As can be seen from the structure of FIG. 3, the orchestration plane (302) and the vBonds (304) are connected to each of the cloud structures (202-1, ..., 202-N), as well as to the control and data plane (206). Additionally, each vManage of each cluster among the clusters (204-1, ..., 204-N) has a weight assigned to it, and these are used to manage the migration of SD-WAN solutions across the clouds, as described in more detail below.
[0045] The architecture (300) uses and utilizes an existing orchestration plane (302) to monitor the vManages of the clusters (204-1, ..., 204-N) and to trigger the control of the SD-WAN solution and the migration of the data plane from the source cloud to the destination cloud during disaster recovery. By relying on the existing orchestration plane (302), the third-party witness component (208) is no longer needed, and its disadvantages as described above are resolved according to the process of FIG. 4 below.
[0046] FIG. 4 illustrates an exemplary method for managing SD-WAN migration in a multi-cloud structure according to an aspect of the present disclosure. FIG. 4 will be described in terms of an orchestration plane (302) and, more specifically, vBonds (304). For the purposes of describing FIG. 4, the vBonds (304) may be referred to as controllers (network controllers). It should be noted that these vBonds (304) may be implemented by one or more processors executing computer-readable instructions to implement the steps of FIG. 4 described below.
[0047] In S400, vBonds (304) monitor clusters of virtual management components (e.g., vManage clusters (204-1, 204-2, ..., 204-N)). Thanks to the design of SD-WANs, vBonds (304) maintain a permanent secure connection to each vManage cluster of the clusters (204-1, 204-2, ..., 204-N). In S400, vBonds (304) monitor not only the reachability of the clusters (204-1, 204-2, ..., 204-N) but also the health, including but not limited to the availability of various services operating on a given vManage cluster (databases, messaging bus, etc.). vBonds (304) are connected to each cluster (204-1, 204-2, ..., 204-N), as well as to each vManage within each of these clusters.
[0048] In S402, vBonds (304) may receive information regarding the preferences, weights, and locations of each vManage cluster. In one example, these preferences, weights, and location information may be configured by the network manager through the vManage itself. Preferences may be numerical values based on the best effort to use a preferred circuit to access another component within the network. Weights may also be numerical values used for load balancing among the vManages of a given cluster. Locations may represent the geographical location of each vManage of a given cluster that can be used to reduce latency and redundancy within the network.
[0049] In one example, a similar process may be used in vSmarts (206-2) for load balancing, as described in U.S. Application No. 15 / 286,116 filed on October 5, 2016, the entire contents of which are incorporated herein by reference.
[0050] In S404, vBonds (304) maintain records of active versus inactive vManage clusters based on received preferences, weights, and locations. For example, a vManage cluster may be determined to be active if the number of vManages in an active cluster exceeds a configurable threshold (determined based on experiments and / or empirical studies).
[0051] In S406, the threshold number of vBonds (304) determines whether the number of active vManages in a given vManage cluster (e.g., the threshold number of vManages in cluster (204-1)) is active (and / or alternatively inactive). This may be referred to as the quorum of vBonds (304). The threshold for the quorum of vBonds (304) is a configurable parameter that can be determined based on experiments and / or empirical studies. For example, assuming that an SD-WAN solution is currently running on cluster (202-1), in S406, it is determined whether the quorum of vBonds (304) is achieved, indicating that the threshold number of vManages in vManage cluster (204-1) is active (and / or inactive).
[0052] At S406, if the quorum of vBonds (304) is not reached, the process returns to S400, and S400 through S406 are repeated. However, if the quorum of vBonds (304) is reached at S406, a failover event is detected at S408. The failover event triggers the migration of the SD-WAN solution from the current cloud structure (e.g., cloud (202-1)) to the destination cloud (e.g., one of the cloud structures (202-2, ..., 202-N)).
[0053] When a failover event is detected in S408, in S410, a target destination cloud (e.g., cloud structures (202-2, ..., 202-N)) is selected.
[0054] In S412, vBonds (304) determine combined weights for the target destination cloud. In one example, the target destination cloud is assigned a configurable preference and location, while each vManage in the corresponding cluster (e.g., one of the vManage clusters (204-2, ..., 204-N)) has a configurable weight. Based on the configurable weight and configurable preference and location of each vManage, combined weights are determined for the target destination cloud.
[0055] For example, the structure (300) may have three clouds (202-1, 202-2, and 202-3) (e.g., Amazon Web Services®, Google®, and Microsoft®, respectively), and the cloud structure (202-1) may be the source (main) cloud structure. Therefore, the cloud structures (202-2 and 202-3) may each be the target destination cloud. Additionally, it is assumed that the combined weight for the vManages (205-2) of the cloud structure (202-2) has a combined numerical value of 10, while the vManages (205-3) of the cloud structure (202-3) (not explicitly illustrated in FIG. 3) have a combined numerical value of 5. Additionally, it is assumed that the preference of the cloud structure (202-2) has a numerical value of 2, while the preference of the cloud structure (202-3) has a numerical value of 4. Finally, it is assumed that the location of the infrastructure providing the cloud structure (202-2) (an exemplary numerical value of 1) is preferred for the execution of the SD-WAN solution compared to the location of the cloud structure (202-3) (an exemplary numerical value of 0). Therefore, the combined weight of the cloud structure (202-2) is 13, whereas the combined weight of the cloud structure (202-3) is 9.
[0056] In S414, it is determined whether the combined weight of the target destination cloud is less than a configurable threshold (target threshold, the non-limiting numerical example being 10). If it is determined that the combined weight is less than the target threshold (e.g., 9 for the cloud structure (2020-3) in the non-limiting example described above), in S416, the next target destination cloud is selected, and S412 and S414 are repeated for the next target destination cloud.
[0057] Once in S414, if it is determined that the combined weight of the target destination cloud is greater than or equal to the target threshold (or alternatively, only exceeding the target threshold), in S418, the target destination cloud is marked as valid and is selected as the destination cloud (e.g., cloud structure (202-2)) for migrating the SD-WAN solution from the source cloud (e.g., from cloud structure (202-1)). In the non-limiting example described above, the combined weight of the cloud structure (202-2) is 13, which is greater than the exemplary threshold of 10, and accordingly, is selected as the destination cloud.
[0058] In S420, vBonds (304) mark the source cloud (e.g., cloud structure (202-1)) as invalid and transmit information about the invalid status of the source cloud and the selected destination cloud (e.g., cloud structure (202-2)) to all vSmarts in the control and data plane component (206). In one example, when vSmarts receive new destination cloud information (e.g., cloud structure (202-2)), they will perform a before break operation to access the new destination cloud and notify all edge devices (vEdges) in the control and data plane component (206) of the change in the management plane, thereby triggering a shift of all edge devices to a new vManage cluster (e.g., vManage cluster (204-2)) in the destination cloud (e.g., destination cloud structure (202-2)).
[0059] Since the above examples of the peer node detection process have been described, the disclosure now returns to a description of device components and architectures that can be implemented as any one of network management devices (122), network controller devices (132), edge network devices (142), etc.
[0060] Along with examples of migration management of SD-WAN cases in a multi-cloud structure as described above, the disclosure now returns to a description of exemplary components that can be used as controllers and components of the multi-cloud structure (200) to implement migration management.
[0061] FIGS. 5a and 5b illustrate examples of systems according to an embodiment of the present disclosure.
[0062] FIG. 5a illustrates an example of a bus computing system (500) in which components of the system are electrically communicating with each other using a bus (505). The computing system (500) may include a system bus (505) capable of connecting various system components to the processor (510), including a processing unit (CPU or processor) (510) and system memory (515), such as read-only memory (ROM) (520) and random access memory (RAM) (525). The computing system (500) may include a cache (512) of high-speed memory that is connected directly or very close to the processor (510) or integrated as part of the processor (510). The computing system (500) may copy data from memory (515), ROM (520), RAM (525), and / or storage device (530) to the cache (512) for rapid access by the processor (510). In this way, the cache (512) can provide performance enhancements that avoid processor delays while waiting for data. These and other modules can control the processor (510) to perform various actions. Other system memory (515) may likewise be available for use. Memory (515) may include a number of different types of memory having different performance characteristics. The processor (510) may include any general-purpose processor, and hardware or software modules such as SERVICE (SVC) 1 (532), SERVICE (SVC) 2 (534), and SERVICE (SVC) 3 (536) stored in a storage device (530) configured to control the processor (510) as well as a special-purpose processor when software instructions are incorporated into an actual processor design.The processor (510) may essentially be a fully self-contained computing system including multiple cores or processors, a bus, a memory controller, a cache, etc. The multi-core processor may be symmetric or asymmetric.
[0063] To enable user interaction with the computing system (500), the input device (545) may represent any number of input mechanisms, such as a microphone for voice, a touch-protected screen for gesture or graphic input, a keyboard, a mouse, motion input, voice, etc. The output device (535) may also be one or more of the numerous output mechanisms known to those skilled in the art. In some cases, multimodal systems may enable a user to provide multiple types of inputs to communicate with the computing system (500). The communication interface (540) may govern and manage user inputs and system outputs. There may be no limitation on operating on any particular hardware arrangement, and therefore, the basic features herein may be easily replaced by improved hardware or firmware arrangements as they are developed.
[0064] The storage device (530) may be a non-volatile memory and may be a hard disk or other types of computer-readable media that are accessible by a computer and can store data, such as magnetic cassettes, flash memory cards, solid-state memory devices, digital multifunction disks, cartridges, random access memory, read-only memory, and hybrids thereof.
[0065] As discussed above, the storage device (530) may include software services (532, 534, 536) for controlling the processor (510). Other hardware or software modules are considered. The storage device (530) may be connected to the system bus (505). In some embodiments, a hardware module performing a specific function may include a software component stored in a computer-readable medium in relation to necessary hardware components such as the processor (510), the bus (505), the output device (535), etc., to perform the function.
[0066] FIG. 5b illustrates an exemplary architecture for a chipset computing system (550) that may be used according to an embodiment. The computing system (550) may include a processor (555) representing any number of physically and / or logically distinct resources capable of executing software, firmware, and hardware configured to perform identified operations. The processor (555) may communicate with a chipset (560) capable of controlling inputs to the processor (555) and outputs from the processor (555). In this example, the chipset (560) may output information to an output device (565), such as a display, read information, and write information to a storage device (570), the storage device (570) may include magnetic media, solid-state media, and other suitable storage media. The chipset (560) may also read data from RAM (575) and write data to RAM (575). A bridge (580) for interfacing with various user interface components (585) may be provided to interface with the chipset (560). The user interface components (585) may include a keyboard, a microphone, a touch detection and processing circuit, a pointing device such as a mouse, etc. Input to the computing system (550) may come from any of the various sources generated by a machine and / or generated by a human.
[0067] The chipset (560) may also interface with one or more communication interfaces (590) that may have different physical interfaces. The communication interfaces (590) may include interfaces for wired and wireless LANs, broadband wireless networks, as well as personal area networks. Some applications of methods for generating, displaying, and utilizing the technology disclosed herein may include receiving ordered datasets on a physical interface, or may be generated by the machine itself by a processor (555) that analyzes data stored in a storage device (570) or RAM (575). Additionally, the computing system (550) may receive inputs from a user through user interface components (585) and execute appropriate functions, such as browsing functions, by decoding these inputs using the processor (555).
[0068] It will be recognized that computing systems (500 and 550) may each have more than one processor (510 and 555) or may be part of a group or cluster of computing devices networked together to provide greater processing power.
[0069] In summary, the present disclosure relates to the management of migration of SD-WAN solutions in a multi-cloud architecture upon detection of a failover event. In one embodiment, the method comprises monitoring clusters of virtual management components of a plurality of cloud networks using virtual bonds of network orchestration components—wherein the corresponding virtual management components of one of the plurality of cloud networks implement one or more services of a Software-Defined Wide Area Access Network (SD-WAN) solution—; detecting a failover event in one of the plurality of cloud networks using virtual bonds; and identifying a new destination cloud network for migrating one or more services of the SD-WAN solution from the source cloud network where the failover event is detected by virtual bonds.
[0070] For clarity of explanation, in some cases, various embodiments may be presented as comprising individual functional blocks including devices, device components, steps or routines in a method embodied in software, or combinations of hardware and software.
[0071] In some embodiments, computer-readable storage devices, media, and memories may include cable or wireless signals including bit streams, etc. However, when referred to, non-transient computer-readable storage media explicitly exclude media such as energy, carrier signals, electromagnetic waves, and the signals themselves.
[0072] The methods according to the examples described above may be implemented using computer-executable instructions that are stored or, if not, available from computer-readable media. These instructions may include, for example, instructions and data that cause a general-purpose computer, a special-purpose computer, or a special-purpose processing device to perform a function or group of functions, or otherwise constitute them. A portion of the computer resources used may be accessible over a network. The computer-executable instructions may be binary intermediate format instructions, such as assembly language, firmware, or source code. Examples of computer-readable media that may be used to store the instructions, the information used, and / or the information generated during the methods according to the described examples include magnetic or optical disks, flash memory, USB devices provided with non-volatile memory, networked storage devices, etc.
[0073] Devices implementing the methods according to these disclosures may include hardware, firmware, and / or software and may take any of various form factors. Some examples of such form factors include general-purpose computing devices such as servers, rack mount devices, desktop computers, laptop computers, etc., or general-purpose mobile computing devices such as tablet computers, smartphones, personal digital assistants, wearable devices, etc. The functionality described herein may also be embodied in peripherals or add-in cards. Such functionality may also, as an additional example, be implemented on a circuit board between different processes or different chipsets running on a single device.
[0074] Instructions, media for transmitting such instructions, computing resources for executing them, and other structures for supporting such computing resources are means for providing the functions described in this disclosure.
[0075] Various examples and other information have been used to describe embodiments within the scope of the appended claims; however, since a person skilled in the art could use these examples to derive a wide range of embodiments, the claims should not be implied to be limited based on specific features or arrangements in these examples. Furthermore, while some essence may have been described in language specific to examples of structural features and / or method steps, it should be understood that the essence defined in the appended claims is not necessarily limited to these described features or acts. For example, such functionality may be differently distributed or performed in components other than those identified herein. Rather, the described features and steps are disclosed as examples of components of systems and methods within the scope of the appended claims.
Claims
Claim 1 A method performed by one or more processors of a network controller, comprising the steps of: monitoring clusters of virtual management components of a plurality of cloud networks using virtual bonds of an orchestration plane of a Software-Defined Wide Access Network (SD-WAN) - wherein the corresponding virtual management components of one of the plurality of cloud networks implement one or more services of an SD-WAN solution -; and detecting a failover event in one of the plurality of cloud networks using the virtual bonds. A method comprising: identifying a new destination cloud network for migrating one or more services of the SD-WAN solution from a source cloud network where the failover event is detected by the virtual bonds; each of the virtual bonds having an established security channel for each virtual management component in each of the clusters; the step of monitoring the clusters including determining the number of inactive virtual management components in each of the plurality of cloud networks; and the step of detecting the failover event including: determining an active status or an inactive status for a corresponding cluster by each of the virtual bonds and based on the number of inactive virtual management components in one of the plurality of cloud networks; and determining the failover event for one of the plurality of cloud networks when a first threshold number of virtual bonds determines that the number of inactive virtual management components in the corresponding cluster is equal to a second threshold. Claim 2 delete Claim 3 delete Claim 4 delete Claim 5 A method according to claim 1, wherein the step of identifying the new destination cloud network comprises: determining the combined weight of virtual management components in the target destination cloud; and identifying the target destination cloud as the new destination cloud when the combined weight of the virtual management components in the target destination cloud is greater than or equal to a third threshold. Claim 6 In claim 5, the step of determining the combined weight is based on the corresponding assigned weight, the corresponding configuration parameters, and the corresponding location of each virtual management component among the virtual management components in the target destination cloud. Claim 7 A method according to claim 1, further comprising the step of communicating identification information of the new destination cloud to virtual smart components in the network control and data plane—the virtual smart components triggering network edge devices to shift to a cluster of virtual network components of the new destination cloud. Claim 8 A network controller comprising: a non-transient computer-readable memory storing computer-readable commands; and one or more processors, wherein the one or more processors execute the computer-readable commands to monitor clusters of virtual management components of a plurality of cloud networks using virtual bonds of an orchestration plane of a software-defined wide area access network (SD-WAN) - the corresponding virtual management components of one of the plurality of cloud networks implement one or more services of the SD-WAN solution -; detect a failover event in one of the plurality of cloud networks using the virtual bonds; and are programmed to identify, by the virtual bonds, a new destination cloud network for migrating one or more services of the SD-WAN solution from a source cloud network where the failover event is detected; A network controller comprising: each of the virtual bonds having an established security channel for each virtual management component in each of the clusters; monitoring the clusters including determining the number of inactive virtual management components in each of the plurality of cloud networks; detecting the failover event including: determining an active status or an inactive status for a corresponding cluster by each of the virtual bonds and based on the number of inactive virtual management components in one of the plurality of cloud networks; and determining the failover event for one of the plurality of cloud networks when a first threshold number of virtual bonds determines that the number of inactive virtual management components in the corresponding cluster is equal to a second threshold. Claim 9 delete Claim 10 delete Claim 11 delete Claim 12 A network controller configured to execute computer-readable commands to identify the new destination cloud network by: determining the combined weight of the virtual management components in the target destination cloud; and identifying the target destination cloud as the new destination cloud when the combined weight of the virtual management components in the target destination cloud is greater than or equal to a third threshold. Claim 13 A network controller according to claim 12, wherein determining the combined weights is based on corresponding assigned weights, corresponding configuration parameters, and the corresponding location of each of the virtual management components among the virtual management components in the target destination cloud. Claim 14 A network controller according to any one of claims 8 and 12 to 13, wherein the virtual bonds are configured to execute the computer-readable commands to communicate identification information of the new destination cloud to virtual smart components in the network control and data plane, and the virtual smart components trigger network edge devices to shift to a cluster of virtual network components of the new destination cloud. Claim 15 One or more non-transient computer-readable media comprising computer-readable instructions, wherein the computer-readable instructions, when executed by one or more processors, cause the one or more processors to: monitor clusters of virtual management components of a plurality of cloud networks using virtual bonds of an orchestration plane of a software-defined wide area access network (SD-WAN) - the corresponding virtual management components of one of the plurality of cloud networks implement one or more services of an SD-WAN solution -; and detect a failover event in one of the plurality of cloud networks using the virtual bonds. One or more non-transient computer-readable media, wherein the virtual bonds perform operations including identifying a new destination cloud network for migrating one or more services of the SD-WAN solution from a source cloud network where the failover event is detected; each of the virtual bonds has an established security channel to each virtual management component in each of the clusters; the operation of monitoring the clusters includes determining the number of inactive virtual management components in each of the plurality of cloud networks; the operation of detecting the failover event includes: determining an active status or an inactive status for a corresponding cluster by each of the virtual bonds and based on the number of inactive virtual management components in one of the plurality of cloud networks; and determining the failover event for one of the plurality of cloud networks when a first threshold number of virtual bonds determines that the number of inactive virtual management components in the corresponding cluster is equal to a second threshold. Claim 16 delete Claim 17 delete Claim 18 delete Claim 19 In paragraph 15, the execution of the computer-readable instructions by the one or more processors causes the virtual bonds to: determine the combined weight of the virtual management components in the target destination cloud; and, when the combined weight of the virtual management components in the target destination cloud is greater than or equal to a third threshold, identify the new destination cloud network by identifying the target destination cloud as the new destination cloud, one or more non-transient computer-readable media. Claim 20 In paragraph 19, one or more non-transient computer-readable media, wherein determining the combined weights is based on corresponding assigned weights, corresponding configuration parameters, and the corresponding location of each of the virtual management components among the virtual management components in the target destination cloud. Claim 21 A device comprising means for implementing a method according to any one of claims 1 and 5 through 7. Claim 22 delete Claim 23 A non-transient computer-readable storage medium comprising instructions, wherein the instructions, when executed by a computer, cause the computer to perform the steps of the method of any one of claims 1 and 5 through 7.
Citation Information
Patent Citations
Replication of virtualized infrastructure within distributed computing environments
US20160048408A1
