DISTRIBUTED NODE DISCOVERY AND OVERLAY PATH MANAGEMENT ON A DATA COMMUNICATION NETWORK

Abstract

An initial provisioning by a management plane of the SD-WAN is received from a centralized SD-WAN gateway with static path overlay between the network edge device on a local LAN and the centralized SD-WAN gateway. At runtime, intelligent decision are made about which overlay path to select and when for the new flow over a control plane of the SD-WAN, based on the topology of the remote network edge and the local SDWAN policy, and to build the selected overlay path.

Claims

1. A network edge device in an SD-WAN (software-defined-wide area network) of a data communication network for dynamic overlay path management at runtime on a control plane of the SD-WAN, the network edge device comprising: a processor; a network communication interface, communicatively coupled to the data communication network; and a memory, communicatively coupled to the processor and storing: a control module to receive initial provisioning by a management plane of the SD-WAN from a centralized SD-WAN manager with static path overlay between the network edge device on a local LAN and the centralized SD-WAN gateway, wherein the initial provisioning includes a local SD-WAN policy; an edge discovery module to, responsive to new data flow from a client on the local LAN in real-time, discover a remote network edge device associated with a destination of the new flow and a topology of the remote network edge device having two or more links connecting the remote network edge device to the data communication network; a dynamic path manager to make intelligent decision about which overlay path to select and when for the new flow over a control plane of the SD-WAN, based on the topology of the remote network edge and the local SDWAN policy, and to build the selected overlay path.

2. The network edge device of claim 1, wherein the network edge device comprises a gateway device.

3. The network edge device of claim 1, wherein the dynamic path manager automatically updates the path selection based on a current health of the path, without additional provisioning.

4. The network edge device of claim 1, wherein the current health comprises one or more of latency, packet loss and jitter.

5. The network edge device of claim 1, wherein the centralized SD-WAN gateway administers a plurality of SD-WANs.

6. The at least one computing device of claim 1, wherein the source node uses a first file sharing technology and the target node uses a second file sharing technology.

7. The at least one computing device of claim 1, wherein control module deletes the file from the workspace directory after being copied.

8. The at least one computing device of claim 1, further comprising a second target node, wherein responsive to the commend, the second target node copies the file from the workspace directory.

9. The at least one computing device of claim 1, wherein the file is part of a highly available system.

10. The at least one computing device of claim 1, wherein the source node and the target node are part of a highly available system.

11. The at least one computing device of claim 1, wherein the file comprises an addon for a SOAR (security, orchestration, automation and response) platform.

12. The at least one computing device of claim 1, wherein the file comprises a configuration file for the cluster of nodes.

13. The at least one computing device of claim 1, further comprising a new node detector, wherein responsive to detecting onboarding of a new node, generating the command towards the new node as the target node to synch configuration files for the cluster of nodes.

14. The computing device of claim 1, wherein the control module updates a whitelist responsive to the process executing after exposure to the virtual machine parameters.

15. The computing device of claim 1, wherein the computing device notifies a remote server responsive to the process not executing after exposure to the virtual machine parameters.

16. The network switch device of claim 1, wherein the encryption module does not interfere with OSI layers 1 to 3 of the data packet.

17. The network switch device of claim 1, wherein the specific headless endpoint device connects wirelessly to the network interface of the network device.

18. The network switch device of claim 1, wherein the network device is also communicatively coupled to the Internet.

19. A method for using an artificial virtual machine in a computer device for preventing malware execution by injecting virtual machine characteristics in a real computing environment of the computer device, the method comprising the steps of: detecting a process being initiated for exposure to an operating system of the computer device that has not been whitelisted; injecting virtual machine parameters for an artificial virtual machine for the process to the real computing environment, the virtual machine parameters simulating execution of an actual virtual machine in a virtual environment; detecting that the process does not execute responsive to the process detecting to the virtual machine parameters of the artificial virtual machine; responsive to the process not executing, taking a security action on the process including preventing the process from being exposed to the operating system.

20. A non-transitory computer-readable media in a network device, implemented at least partially in hardware for, when executed by a processor, for preventing malware execution by injecting virtual machine characteristics in a real computing environment of the computer device, the method comprising the steps of: detecting a process being initiated for exposure to an operating system of the computer device that has not been whitelisted; injecting virtual machine parameters for an artificial virtual machine for the process to the real computing environment, the virtual machine parameters simulating execution of an actual virtual machine in a virtual environment; detecting that the process does not execute responsive to the process detecting to the virtual machine parameters of the artificial virtual machine; responsive to the process not executing, taking a security action on the process including preventing the process from being exposed to the operating system.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0010] In the following drawings, like reference numbers are used to refer to like elements. Although the following figures depict various examples of the invention, the invention is not limited to the examples depicted in the figures.

[0011] FIG. 1 is a high-level block diagram illustrating a system for dynamic overlay path management at runtime on a control plane of the SD-WAN, according to an embodiment.

[0012] FIG. 2 is a more detailed block diagram illustrating of a local access point of the system of FIG. 1, according to an embodiment.

[0013] FIG. 3 is a more detailed block diagram illustrating of a local access point of the system of FIG. 1, according to an embodiment.

[0014] FIG. 4 is a high-level flow diagram illustrating a method for dynamic overlay path management at runtime on a control plane of the SD-WAN, according to one preferred embodiment.

[0015] FIG. 5 is a block diagram illustrating a computer device for implementing components of the system of FIG. 1, according to one embodiment.

DETAILED DESCRIPTION

[0016] The description below provides methods, computer program products, and systems for dynamic overlay path management at runtime on a control plane of the SD-WAN.

[0017] One of ordinary skill in the art will recognize many additional variations made possible by the succinct description of techniques below.

[0018] I. Systems for Dynamic Overlay Path Management at Runtime (FIGS. 1-3)

[0019] FIG. 1 is a high-level illustration of a system 100 for dynamic overlay path management at runtime on a control plane of the SD-WAN, according to an embodiment. The system 100 comprises an SD-WAN gateway 110, a local access point 120, and a remote access point 130. Many other configurations are possible, for example, with additional network components such routers, switches, repeaters, firewalls, and the like. Also, there can be many more or fewer clients in FIG. 1. The system components can be implemented in computer devices with non-transitory source code, such as set forth below with reference to FIG. 5.

[0020] The components of the system 100 are coupled in communication over the data communication network. Preferably, the SD-WAN gateway 110 and the access points 120, 130 are connected to the data communication system via hard wire. More specifically, the local access point 120 has a broadband wired connection 101 and the remote access point 130 has a broadband wired connection 102 and an LTE wired connection 103. The stations 130A,B are preferably connected to access points via a wireless channel. The data communication network 199 can be any data communication network such as an SDWAN, an SDN (Software Defined Network), WAN, a LAN, WLAN, a cellular network (e.g., 3G, 4G, 5G or 6G), or a hybrid of different types of networks. Various data protocols can dictate format for the data packets. For example, Wi-Fi data packets can be formatted according to IEEE 802.11.

[0021] In one embodiment, the SD-WAN gateway 110 statically provisions overlay paths at set-up. Overlay paths can be VPN (virtual private network) links using IPSec as security. In another embodiment, just a framework of data is provided for dynamic overlay paths at runtime. Runtime data including current conditions and current remote pathways either alone, or with the framework, determines pathways at the time triggered, rather than at initial set-up. In other operations, a spoke communication module 210 tracks and monitors each of the connected spokes. A network topology module 220 maintains an overview of the network or different networks based on information collected from spokes. A policy manager 230 applies polies from a network-wide perspective.

[0022] The local access point 120 and the remote access point 130, dynamically provision overlay paths at runtime. Runtime can be policy based or when a data packet is received from transmission to another spoke in a SD-WAN. A control plane of the SD-WAN permits adjustments without operator intervention. As a result, overlay paths can be built, measured and torn down dynamically, based on a combination of traffic patterns, real-time network conditions and administratively configured policies. To do so, an edge discovery process between the edge device 120 and a remote edge device is triggered to exchange necessary properties about each other, such as which underlay transport(s) are currently connected, special attributes about each connection, real-time remote conditions, and the like. For example, WAN link descriptors can be exchanged, along with its IP address for IKE negotiations and a domain ID to specify the type of underly transport. In another example, site name and site ID are exchanged.

[0023] Next, a path management process uses discovered information to make a local decision as to what overlay path(s) to build and when. Additionally, a local overlay path is set up within a local LAN of the local access point 120. An embodiment maintains a table of active speakers. Entries can be removed due to inactivity.

[0024] The path selection can involve whether there is any current traffic flow between A and B; what underlay transports A and B are currently connected to (e.g., Internet, MPLS, LTE, broadband, etc.); real-time health measurements of different feasible paths between A and B; and administratively configured policies such as underlay transport properties, path preferences, per-application SLA targets, and the like. The path health be defined by one or more of latency, packet loss and jitter measurements. Latency is the time that it takes for a data packet to travel from source to destination. Packet loss occurs when packets fail to reach a destination. Jitter refers to a disruption in data flows due to network traffic jams, improper packet queueing and set up errors.

[0025] FIG. 2 is a more detailed illustration of the intelligent SD-WAN module 122 (or the SD-WAN module 132) of the system 100 of FIG. 1. The intelligent SD-WAN module 122 includes a control module 310, an edge discovery module 320, and a dynamic path manager 330. The modules can be implemented in source code stored in non-transitory memory executed by a processor. Alternatively, the modules can be implemented in hardware with microcode. The modules can be singular or representative of functionality spread over multiple components. Many other variations are possible.

[0026] The control module 310 can receive initial provisioning by a management plane of the SD-WAN from a centralized SD-WAN manager with static path overlay between the network edge device on a local LAN and the centralized SD-WAN gateway. The initial provisioning includes a local SD-WAN policy. In some embodiments, updated provisioning is received.

[0027] The edge discovery module 320, responsive to new data flow from a client on the local LAN in real-time, discovers a remote network edge device associated with a destination of the new flow and a topology of the remote network edge device having two or more links connecting the remote network edge device to the data communication network.

[0028] The dynamic path manager 330 to make intelligent decision about which overlay path to select and when for the new flow over a control plane of the SD-WAN, based on the topology of the remote network edge and the local SDWAN policy, and to build the selected overlay path.

[0029] II. Method for Dynamic Overlay Path Management at Runtime (FIG. 4)

[0030] FIG. 4 is a high-level flow diagram illustrating a method for dynamic overlay path management at runtime on a control plane of the SD-WAN, according to one embodiment. The method 400 can be implemented, for example, by the system 100 of FIG. 1. The steps are merely representative groupings of functionality, as there can be more or fewer steps, and the steps can be performed in different orders. Many other variations of the method 400 are possible.

[0031] At step 410, initial provisioning by a management plane of the SD-WAN is received from a centralized SD-WAN manager with static path overlay between the network edge device on a local LAN and the centralized SD-WAN gateway. The initial provisioning includes a local SD-WAN policy.

[0032] At step 420 responsive to new data flow from a client on the local LAN in real-time, a remote network edge device associated with a destination of the new flow and a topology of the remote network edge device having two or more links connecting the remote network edge device to the data communication network, are discovered (e.g., Internet, MPLS, LTE, broadband, etc.).

[0033] At step 430, intelligent decisions are made about which overlay path to select and when for the new flow over a control plane of the SD-WAN, based on the topology of the remote network edge and the local SDWAN policy, and to build the selected overlay path.

[0034] III. Generic Computing Environment (FIG. 5)

[0035] Computer software products (e.g., non-transitory computer products storing source code) may be written in any of various suitable programming languages, such as C, C++, C#, Oracle® Java, JavaScript, PHP, Python, Perl, Ruby, AJAX, and Adobe® Flash®. The computer software product may be an independent application with data input and data display modules. Alternatively, the computer software products may be classes that are instantiated as distributed objects. The computer software products may also be component software such as Java Beans (from Sun Microsystems) or Enterprise Java Beans (EJB from Sun Microsystems). Some embodiments can be implemented with artificial intelligence.

[0036] Furthermore, the computer that is running the previously mentioned computer software may be connected to a network and may interface with other computers using this network. The network may be on an intranet or the Internet, among others. The network may be a wired network (e.g., using copper), telephone network, packet network, an optical network (e.g., using optical fiber), or a wireless network, or any combination of these. For example, data and other information may be passed between the computer and components (or steps) of a system of the invention using a wireless network using a protocol such as Wi-Fi (IEEE standards 802.11, 802.11a, 802.11b, 802.11e, 802.11g, 802.11i, 802.11n, and 802.11ac, just to name a few examples). For example, signals from a computer may be transferred, at least in part, wirelessly to components or other computers.

[0037] In an embodiment, with a Web browser executing on a computer workstation system, a user accesses a system on the World Wide Web (WWW) through a network such as the Internet. The Web browser is used to download web pages or other content in various formats including HTML, XML, text, PDF, and postscript, and may be used to upload information to other parts of the system. The Web browser may use uniform resource identifiers (URLs) to identify resources on the Web and hypertext transfer protocol (HTTP) in transferring files on the Web.

[0038] The phrase “network appliance” generally refers to a specialized or dedicated device for use on a network in virtual or physical form. Some network appliances are implemented as general-purpose computers with appropriate software configured for the particular functions to be provided by the network appliance; others include custom hardware (e.g., one or more custom Application Specific Integrated Circuits (ASICs)). Examples of functionality that may be provided by a network appliance include, but is not limited to, layer 2/3 routing, content inspection, content filtering, firewall, traffic shaping, application control, Voice over Internet Protocol (VoIP) support, Virtual Private Networking (VPN), IP security (IPSec), Secure Sockets Layer (SSL), antivirus, intrusion detection, intrusion prevention, Web content filtering, spyware prevention and anti-spam. Examples of network appliances include, but are not limited to, network gateways and network security appliances (e.g., FORTIGATE family of network security appliances and FORTICARRIER family of consolidated security appliances), messaging security appliances (e.g., FORTIMAIL family of messaging security appliances), database security and/or compliance appliances (e.g., FORTIDB database security and compliance appliance), web application firewall appliances (e.g., FORTIWEB family of web application firewall appliances), application acceleration appliances, server load balancing appliances (e.g., FORTIBALANCER family of application delivery controllers), vulnerability management appliances (e.g., FORTISCAN family of vulnerability management appliances), configuration, provisioning, update and/or management appliances (e.g., FORTIMANAGER family of management appliances), logging, analyzing and/or reporting appliances (e.g., FORTIANALYZER family of network security reporting appliances), bypass appliances (e.g., FORTIBRIDGE family of bypass appliances), Domain Name Server (DNS) appliances (e.g., FORTIDNS family of DNS appliances), wireless security appliances (e.g., FORTIWIFI family of wireless security gateways), FORIDDOS, wireless access point appliances (e.g., FORTIAP wireless access points), switches (e.g., FORTISWITCH family of switches) and IP-PBX phone system appliances (e.g., FORTIVOICE family of IP-PBX phone systems).

[0039] This description of the invention has been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form described, and many modifications and variations are possible in light of the teaching above. The embodiments were chosen and described in order to best explain the principles of the invention and its practical applications. This description will enable others skilled in the art to best utilize and practice the invention in various embodiments and with various modifications as are suited to a particular use. The scope of the invention is defined by the following claims.