Cloud Network Reachability Analysis
The cloud network reachability analysis method simulates forwarding paths using packet headers to determine reachability status and configuration information, addressing the complexity of VPC networks by identifying and correcting configuration issues.
Patent Information
- Application Number
- JP2023122374
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2019-04-05
- Filing Date
- 2023-07-27
- Publication Date
- 2024-11-28
- Estimated Expiration
- 2040-04-03
AI Technical Summary
The complexity and size of virtual private clouds (VPCs) require significant network configuration, making it difficult to manage network reachability and identify inconsistent or obsolete configurations.
A method and system for cloud network reachability analysis that uses a data processing hardware to simulate forwarding paths based on packet headers, determining reachability status using a network abstraction state machine, and providing network configuration information for each path.
Enables efficient verification of network reachability and detection of configuration errors within and between VPC networks, allowing users to validate desired connectivity and detect inconsistencies without actual data packet transmission.
Smart Images

Figure 0007591625000001 
Figure 0007591625000002 
Figure 0007591625000003
Abstract
Description
[Technical field]
[0001] Technical Field The present disclosure relates to reachability analysis of cloud networks. [Background technology]
[0002] background A Virtual Private Cloud (VPC) is an on-demand, configurable pool of shared computing resources allocated within a public cloud environment. A VPC provides users with isolation from other cloud users. A VPC may run one or more virtual machines (VMs) that may communicate with a user's on-premises network or other remote resources via a Virtual Private Network (VPN). Due to the potential size and complexity of a VPC, which may include many VMs, network gateways, load balancers, etc., significant network configuration is often required to operate and maintain a VPC. Summary of the Invention
[0003] overview One aspect of the disclosure provides a method for providing cloud network reachability analysis. The method includes receiving a reachability query at data processing hardware requesting a reachability status of a target. The reachability query includes a packet header associated with a data packet. The packet header includes a source Internet Protocol (IP) address associated with a source of the data packet and a destination IP address associated with a destination of the data packet. The analysis also includes the data processing hardware generating one or more simulated forwarding paths for the data packet based on the packet header using a data plane model. Each simulated forwarding path includes corresponding network configuration information. The method also includes the data processing hardware determining the reachability status of the target based on the one or more simulated forwarding paths. The method also includes the data processing hardware providing the determined reachability status and the one or more simulated forwarding paths to a user device associated with the reachability query. The one or more simulated forwarding paths, upon being received by the user device, cause the user device to present the network configuration information for each simulated forwarding path.
[0004] Implementations of the present disclosure may include one or more of any of the following features: In some implementations, determining the reachability status of the one or more simulated forwarding paths includes using a network abstract state machine. The user device may be configured to send the data packet from a remote network using a locally advertised route. In some examples, the network configuration information includes at least one of: a port / interface for directing the data packet within a Virtual Private Cloud (VPC) network, a port / interface for directing the data packet between VPC networks, a port / interface for directing the data packet between a VPC network and a non-VPC network, firewall rules applied to the data packet at each step along the corresponding simulated forwarding path, or a network configuration associated with each step along the corresponding simulated forwarding path. Contains at least one.
[0005] Optionally, the method includes the step of the data processing hardware performing a network reachability analysis for each of the one or more simulated forwarding paths based on the corresponding network configuration information, the network reachability analysis being configured to perform at least one of: determining a final state of reachability of the data packet along the corresponding simulated forwarding path, discovering one or more misconfigurations along the corresponding simulated forwarding path, or discovering inconsistent or obsolete configurations along the corresponding simulated forwarding path.
[0006] In some implementations, the reachability final state includes any one of a delivered state indicating the data packet is delivered to the destination, a forwarded state indicating the data packet is forwarded to another network having an unknown configuration, a deleted state indicating the data packet is deleted due to a configuration checkpoint failure or missing configuration, or an aborted state indicating the network reachability analysis is not possible due to missing critical configuration. Performing the network reachability analysis may include performing the network reachability analysis in at least one of an on-demand mode, a continuous mode, a pre-submit mode, or a post-submit mode.
[0007] In some examples, the packet header further includes a protocol associated with the data packet, a source port associated with the data packet, and a destination port associated with the data packet. The source of the data packet may include a first instance running in a first network, and the destination of the data packet may include a second instance running in a second network different from the first network. In some implementations, the first network includes a VPC network and the second network includes an on-premises network. The first network and the second network may include respective VPC networks.
[0008] The source of the data packet may include a first instance and the destination of the data packet may include a second instance. Both the first instance and the second instance run in the same VPC network. The source of the data packet may be located in an external network and the destination of the data packet may include a global HTTPS load balancer running in a VPC network. The global HTTPS load balancer is configured to route the data packet to one of a plurality of different backends. Generating one or more simulated forwarding paths for the data packet may include generating a corresponding simulated forwarding path from the global HTTPS load balancer to each of the plurality of different backends.
[0009] Another aspect of the present disclosure provides a system for providing cloud reachability analysis. The system includes data processing hardware and memory hardware in communication with the data processing hardware. The memory hardware stores instructions that, when executed on the data processing hardware, cause the data processing hardware to perform operations. The operations include receiving a reachability query requesting reachability status of a target. The reachability query includes a packet header associated with a data packet. The packet header includes a source Internet Protocol (IP) address associated with a source of the data packet and a destination Internet Protocol (IP) address associated with a destination of the data packet. and a destination IP address associated with the packet header. The analysis also includes generating one or more simulated forwarding paths for the data packet based on the packet header using a data plane model. Each simulated forwarding path includes corresponding network configuration information. The operations also include determining the reachability status of the target based on the one or more simulated forwarding paths. The operations also include providing the determined reachability status and the one or more simulated forwarding paths to a user device associated with the reachability query. The one or more simulated forwarding paths, upon receipt by the user device, cause the user device to present the network configuration information for each simulated forwarding path.
[0010] This aspect may include one or more of any of the following features. In some implementations, determining the reachability status of the one or more simulated forwarding paths includes using a network abstract state machine. The user device may be configured to transmit the data packet from a remote network using a locally advertised route. In some examples, the network configuration information includes at least one of a port / interface for directing the data packet within a Virtual Private Cloud (VPC) network, a port / interface for directing the data packet between VPC networks, a port / interface for directing the data packet between a VPC network and a non-VPC network, a firewall rule applied to the data packet at each step along the corresponding simulated forwarding path, or a network configuration associated with each step along the corresponding simulated forwarding path.
[0011] Optionally, the operations include performing a network reachability analysis for each of the one or more simulated forwarding paths based on the corresponding network configuration information, the network reachability analysis being configured to perform at least one of: determining a final state of reachability of the data packet along the corresponding simulated forwarding path, discovering one or more misconfigurations along the corresponding simulated forwarding path, or discovering inconsistent or obsolete configurations along the corresponding simulated forwarding path.
[0012] In some implementations, the reachability final state includes any one of a delivered state indicating the data packet is delivered to the destination, a forwarded state indicating the data packet is forwarded to another network having an unknown configuration, a deleted state indicating the data packet is deleted due to a configuration checkpoint failure or missing configuration, or an aborted state indicating the network reachability analysis is not possible due to missing critical configuration. Performing the network reachability analysis may include performing the network reachability analysis in at least one of an on-demand mode, a continuous mode, a pre-submit mode, or a post-submit mode.
[0013] In some examples, the packet header further includes a protocol associated with the data packet, a source port associated with the data packet, and a destination port associated with the data packet. The source of the data packet may include a first instance running in a first network, and the destination of the data packet may include a second instance running in a second network different from the first network. In some implementations, the first The first network may include a VPC network and the second network may include an on-premise network. The first network and the second network may include respective VPC networks.
[0014] The source of the data packet may include a first instance and the destination of the data packet may include a second instance. Both the first instance and the second instance run in the same VPC network. The source of the data packet may be located in an external network and the destination of the data packet may include a global HTTPS load balancer running in a VPC network. The global HTTPS load balancer is configured to route the data packet to one of a plurality of different backends. Generating one or more simulated forwarding paths for the data packet may include generating a corresponding simulated forwarding path from the global HTTPS load balancer to each of the plurality of different backends.
[0015] The details of one or more implementations of the disclosure are set forth in the accompanying drawings and the description below. Other aspects, features, and advantages will be apparent from the description and drawings, and from the claims. [Brief description of the drawings]
[0016] [Figure 1] 1 is a schematic diagram of an example system for performing cloud network reachability analysis. [Diagram 2] FIG. 2 is a schematic diagram of exemplary components of a virtual machine of the system of FIG. 1. [Figure 3A] FIG. 2 is a schematic diagram of example components including a network abstract state machine of the system of FIG. 1. [Figure 3B] FIG. 13 is a schematic diagram of an example report showing determined reachability status of simulated forwarding paths; [Figure 4] FIG. 4 is a schematic diagram of the network abstract state machine of FIG. 3. [Diagram 5] FIG. 2 is a schematic diagram of a state diagram of a network abstract state machine for simulating a forwarding path between a virtual machine and another virtual machine. [Figure 6] FIG. 1 is a schematic diagram of a state diagram of a network abstract state machine for simulating a forwarding path between a virtual machine and a load balancer. [Figure 7] FIG. 1 is a schematic diagram of a state diagram of a network abstraction state machine for simulating a forwarding path between a virtual machine and an on-premise network. [Figure 8] FIG. 2 is a schematic diagram of a state diagram of a network abstract state machine for simulating a forwarding path between the Internet and a virtual machine. [Figure 9] A schematic diagram of a state diagram of a network abstract state machine for simulating a forwarding path between an on-premise network virtual machine and a virtual private cloud virtual machine. [Figure 10A] 13 is a table of causes of final reachability states of simulated data packets. [Figure 10B] 13 is a table of causes of final reachability states of simulated data packets. [Figure 11] FIG. 1 is a schematic diagram of a simulated forwarding path between an external host and a virtual private cloud virtual machine via a load balancer. [Figure 12] 1 is a flowchart of an example arrangement of operations for a method of performing a cloud network reachability analysis. [Figure 13] FIG. 1 is a schematic diagram of an example computing device that can be used to implement the systems and methods described herein. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0017] Like reference numbers in the various drawings indicate like elements. Detailed Description A Virtual Private Cloud (VPC) is an on-demand, configurable pool of shared computing resources allocated within a public cloud environment to provide a user with isolation from other cloud users. This isolation may be achieved by allocating private Internet Protocol (IP) subnets and / or virtual communication constructs. A VPC may run one or more virtual machines (VMs) that may communicate with a user's on-premises network or other remote resources via a Virtual Private Network (VPN) to ensure highly secure access to the VPC environment. Some VPC environments can be very large (i.e., containing many VMs, network gateways, load balancers, etc.) and complex, so substantial network configuration is often required to operate and maintain a VPC network.
[0018] Implementations herein are directed to a cloud reachability analyzer that allows a user to specify a packet header having multiple fields (e.g., source and destination addresses, protocol, source and destination ports, etc.) to simulate (using the packet header) at least one expected forwarding path of a data packet through a VPC network, a peering VPC network, a VPN tunnel, and / or to a user's on-premise network. The cloud reachability analyzer provides configuration information, including, for example, routes and firewall rules, for each simulated path. In contrast to actually verifying the state of a forwarding path (i.e., actually sending a data packet), the cloud reachability analyzer instead performs the analysis based on the active configuration of the VPC network. This is sometimes referred to as "intent-based" packet tracing.
[0019] That is, the cloud reachability analyzer provides configuration-based static analysis of network reachability within a VPC or between a VPC network and a non-VPC network (e.g., an on-premise network). A user may specify one or more parameters of a packet header, and the cloud reachability analyzer generates and simulates a packet forwarding path. For each step of each simulated path, the cloud reachability analyzer provides a matching configuration (e.g., firewall rules, routes, etc.). Thus, the cloud reachability analyzer enables a user to verify the intended reachability with a network configuration, and helps discover inconsistent, obsolete, or incorrectly configured configurations. The cloud reachability analyzer also checks and detects errors from new configuration changes, and analyzes the impact of the proposed configuration changes on network connectivity.
[0020] 1, in some implementations, an exemplary system 100 includes a user device 10 associated with a respective user 12 and communicating with a remote system 140 via a network 60 (e.g., the Internet) and an on-premise network 70 (i.e., a local network that the user device 10 uses to connect to the network 60). The on-premise network 70 includes a network gateway 72 (e.g., a router) that acts as a forwarding host for the on-premise network 70. The user device 10 may correspond to any computing device, such as a desktop workstation, a laptop workstation or a mobile device (i.e., a smartphone). The user device 10 includes computing resources 18 (e.g., data processing hardware) and / or storage resources 16 (e.g., memory hardware).
[0021] The remote system 140 may be a single computer, multiple computers, or a distributed system (e.g., a cloud environment) having scalable / elastic resources 142 including computing resources 144 (e.g., data processing hardware) and / or storage resources 146 (e.g., memory hardware). A data store (i.e., a remote storage device) may be located on the storage resources 146 to enable scalable use of the storage resources 146 by one or more of the clients or computing resources 144. The remote system 140 is configured to implement and run one or more virtual machines (VMs) 250, 250a-n. One or more of the VMs are securely executed in a Virtual Private Cloud (VPC) environment or VPC network 148 associated with or operated by the user 12. The VPC network 148 may include various other network elements such as load balancers, gateways, front-ends and back-ends.
[0022] 2, the distributed system 140 includes a collection 210 of resources 110 (e.g., hardware resources 110h), a virtual machine monitor (VMM) 220, a VM layer 240 that executes one or more of the VMs 250, and an application layer 260. Each hardware resource 110h may include one or more physical central processing units (pCPUs) 144 ("physical processors 144") and memory hardware 146. Although each hardware resource 110h is shown as having a single physical processor 144, any hardware resource 110h may include multiple physical processors 144. An operating system 212 may run on the collection 210 of resources 110.
[0023] In some examples, the VMM 220 corresponds to a hypervisor 220 (e.g., Compute Engine) including at least one of software, firmware, or hardware configured to create and run VMs 250. A computer (i.e., data processing hardware 144) associated with the VMM 220 that runs one or more VMs 250 may be referred to as a host machine, while each VM 250 may be referred to as a guest machine. Here, the VMM 220 or hypervisor is configured to provide each VM 250 with a corresponding guest operating system (OS) 212g having a virtual operating platform and manage the execution of the corresponding guest OS 212g on the VM 250. As used herein, each VM 250 may be referred to as an "instance" or "VM instance." In some examples, multiple instances of various operating systems may share virtualized resources. For example, a first VM 250 of a Linux™ operating system, a second VM 250 of a Windows™ operating system, and a third VM 250 of an OS X™ operating system may all run on a single physical x86 machine.
[0024] The VM layer 240 includes one or more virtual machines 250. The distributed system 140 allows the user 12 to launch the VMs 250 on demand. The VMs 250 emulate real computer systems and operate based on the computer architecture and functions of real or virtual computer systems, which may include dedicated hardware, software, or a combination thereof. In some examples, the distributed system 140 authorizes and authenticates the user 12 before launching one or more VMs 250. An instance of software, or simply an instance, is a VM 250 provided (running) on the data processing hardware 144 of the distributed system 140.
[0025] Each VM 250 may include one or more virtual central processing units (vCPUs) 252 ("virtual processors"). In the illustrated example, a first virtual machine 250a includes a first set 252a of one or more virtual processors 252, and a second virtual machine 250b includes a second set 252b of one or more virtual processors 252. Although the second set 252b is shown as including only one virtual processor 252, any number of virtual processors 252 may be included. Each virtual processor 252 emulates one or more physical processors 144. For example, the first set 252a of one or more virtual processors 252 emulates the first set 113a of one or more physical processors 144, and the second set 252b of one or more virtual processors 252 emulates the second set 113b of one or more physical processors 144. The application layer 260 includes software resources 110s, 110sa, and 110sb (software applications) that can be executed on the virtual machine 250.
[0026] Generally, each instance of software (e.g., virtual machine 250) includes at least one virtual storage device 262 that provides volatile and non-volatile storage capacity for services on physical memory hardware 146. For example, the storage capacity on physical memory hardware 146 may include a persistent disk (PD), which stores data for user 12 across several physical disks (e.g., memory area 116 (FIG. 13)) of memory hardware 146 or random access memory (RAM) to provide volatile memory. More specifically, each virtual storage device 262 of a corresponding VM 250 moves data in a sequence of bytes or bits (blocks) to an associated physical block storage volume V on memory hardware 146 to provide non-volatile storage. Thus, the virtual storage device 262 of the corresponding VM instance 250 provides storage capacity that maps to the corresponding physical block storage volume V on memory hardware 146. In some examples, the virtual storage device 262 supports random access to data on memory hardware 146, typically using buffered I / O. Examples include hard disks, CD-ROM drives, and flash drives. Similarly, a portion of the volatile memory (e.g., RAM) of the physical memory hardware 146 may be distributed across virtual storage devices 262.
[0027] Within the guest operating system 212g is a guest kernel 214g. The kernel is a computer program that is the core of the operating system with full access and control over the OS. That is, the kernel is the intermediary between the host machine's applications 110s and the hardware resources 110h. Most modern computing systems separate virtual memory into a protected kernel space and a user space 216g. Generally, the kernel remains in volatile memory in the protected kernel space and is separated from the user space 216g. To improve safety and reliability, the applications 110s and other software services generally run in the guest user space 216g and do not have the necessary privileges to interact with the protected kernel space.
[0028] Returning to FIG. 1 , the remote system 140 may execute a cloud reachability analyzer 150 to analyze one or more network forwarding paths 80, 80a-n between or within the VPC network 148 and / or the on-premise network 70 to generate a reachability status 172 and / or network configuration 173 for each network forwarding path 80. Identifying information 162.
[0029] The cloud reachability analyzer 150 receives a reachability query 20 from the user device 10 requesting a reachability status 172 of a target. The target may include an on-premise network gateway 72, one or more VMs 250, a firewall rule, and / or other components of the VPC network 148, such as a load balancer (FIG. 11). If the target is a firewall rule, the reachability status 172 depends on whether there is a packet that can be delivered to the VPC network 148 and hit a particular rule in the configuration. The reachability query 20 includes a packet header 22 (e.g., an Internet Protocol (IP) version 4 (IPv4) or IP version 6 (IPv6) packet header) associated with the data packet 24. In some examples, the reachability query 20 includes the data packet 24 and the associated packet header 22, while in other examples, the cloud reachability analyzer 150 receives the packet header 22 and generates a corresponding data packet 24. The packet header 22 includes a number of data packet parameters 25, 25a-n. For example, the packet header 22 includes a source Internet Protocol (IP) address 25a and a destination IP address 25b. Optionally, the packet header 22 includes other parameters 25, such as a protocol type 25c, a source port 25d, and / or a destination port 25e.
[0030] The cloud reachability analyzer 150 includes a path generator 160 that receives or obtains a data packet 24 having an associated packet header 22. The path generator 160 uses a data plane model 164 to generate one or more simulated forwarding paths 80 (also referred to herein as traces) of the data packet 24 based on the packet header 22. Each simulated forwarding path 80 includes corresponding network configuration information 162. The data plane model 164 obtains the network configuration information 162 from network components of the VPC network 148, including, for example, ports / interfaces for directing the data packet 24 within the VPC network 148, ports / interfaces for directing the data packet 24 between different VPC networks 148, ports / interfaces for directing the data packet 24 between the VPC network 148 and a non-VPC network (e.g., the on-premise network 70), firewall rules applied to the data packet 24 at each step along the corresponding simulated forwarding path 80, and / or network configurations associated with each step along the corresponding simulated forwarding path 80. As used herein, each step along the simulated forwarding path 80 refers to an intermediate device (eg, a gateway, a load balancer, etc.) between the source instance and the destination instance.
[0031] In some implementations, the data plane model 164 is an ideal data plane model that models the data plane of the network 148 by deriving instances from the network configuration information 162. In some examples, the network configuration information 162 is stored in a project configuration associated with the VPC network 148. The data plane model 164 analyzes the derived instances to identify and verify reachability characteristics. That is, the data plane model 164 abstracts relevant network configurations for reachability analysis. The network configuration information 162 may include VPC network configuration information, network service information (e.g., load balancers), hybrid cloud configurations, VM configurations, and / or platform configurations (e.g., platforms for containerized applications).
[0032] The simulated forwarding path 80 may be within a VPC network 148 and / or The simulated forwarding path 80 represents a forwarding path of a data packet 24 between a VPC network 148 and an on-premise network 70. For example, one simulated forwarding path 80 represents a forwarding path from a first instance (e.g., VM 250a) to a second instance (e.g., VM 250b), both of which are executed in the same VPC network 148. Optionally, the source of the data packet for one simulated forwarding path 80 is an instance (e.g., VM 250) executed in a first network, which is the VPC network 148, and the destination is a second instance (e.g., a different VM 250) executed in a second network, which is a VPC network 148 different from the first network.
[0033] In another example, one simulated forwarding path 80 represents a forwarding path 80 from one VM 250 to an external network (e.g., the Internet 60). That is, the source (i.e., source IP address 25a) of the data packet 24 includes a first instance running in a first network (e.g., VM 250 in VPC network 148) and the destination (i.e., destination IP address 25b) of the data packet 24 includes a second instance running in a second network (e.g., on-premise network 70) different from the first network. In yet another example, the simulated forwarding path 80 represents from the VM 250 to the load balancer 1110 (FIG. 11) and / or from the VM 250 to a network gateway 72 of the on-premise network 70 (e.g., via a virtual private network (VPN) tunnel). Each of these examples may be reversed in direction. That is, one of the simulated forwarding paths 80 may include from the Internet 60 to the VM 250 or the load balancer 1110, and / or from the on-premise network gateway 72 to the VM 250. The user device 10 may be configured to send the data packet 24 from a remote network (e.g., the on-premise network 70) using a locally advertised route. That is, since the cloud reachability analyzer 150 may not have access to the network configuration information 162 of the on-premise network 70, the cloud reachability analyzer 150 may not be able to verify whether the correct route and firewall rules are configured for the data packet 24 originating from the on-premise network 70. However, the cloud reachability analyzer 150 may verify whether the configuration from the VPC network 148 allows the data packet 24 to be delivered to the intended destination. The most important configurations verified by the cloud reachability analyzer 150 include the advertised route and the ingress firewall rules.
[0034] As another example, a source of data packet 24 may be located in an external network (e.g., on-premise network 70) and a destination of data packet 24 may include a global HTTPS load balancer 1110 running in VPC network 148. Global HTTPS load balancer 1110 may be configured to route data packet 24 to one of a number of different backend VMs 250 ( FIG. 11 ). Path generator 160 may generate corresponding simulated forwarding paths 80 from the global HTTPS load balancer to each of the number of different backend VMs 250.
[0035] The example paths 80 described herein are illustrative only and are not intended to be limiting. That is, the cloud reachability analyzer 150 may analyze or simulate other forwarding paths 80 as well. For example, the cloud reachability analyzer 150 may receive or obtain (e.g., from the user 12) network configuration information 162 for other networks (e.g., the on-premise network 70 or peering VPC networks) and include simulated paths 80 through those networks. In other words, cloud reachability analyzer 150 may analyze forwarding paths 80 through any networks and associated network components (e.g., gateways, load balancers, front-ends, back-ends, etc.) for which cloud reachability analyzer 150 obtains network configuration information 162. In some examples, cloud reachability analyzer 150 stops analyzing when network configuration information 162 is no longer available (e.g., at on-premise gateway 72).
[0036] The path generator 160 passes the paths 80 and corresponding network configuration information 162 to the path analyzer 170, which determines a reachability status 172 of the target of the reachability query 20 based on the one or more simulated forwarding paths 80. In some examples, the path analyzer 170 performs a network reachability analysis for each of the one or more simulated forwarding paths 80 based on the corresponding network configuration information 162. The path analyzer 170 may perform the network reachability analysis in at least one of an on-demand mode, a continuous mode, a pre-submit mode, or a post-submit mode. For example, the reachability query 20 may indicate a request for a single simulation or continuous simulation until the user device 10 instructs the cloud reachability analyzer 150 to stop (or until some other threshold is met, e.g., until a certain time has elapsed). In some implementations, the path analyzer 170 determines a final state 172 of reachability of the data packet 24 along the corresponding simulated forwarding path 80 (also referred to herein as reachability status 172) by discovering one or more faulty configurations along the corresponding simulated forwarding path 80 or by discovering an inconsistent or obsolete configuration along the corresponding simulated forwarding path 80.
[0037] The cloud reachability analyzer 150 provides the determined reachability status 172 and the one or more simulated forwarding paths 80 to the user device 10 associated with the reachability query 20. As described in more detail below, the one or more simulated forwarding paths 80, once received by the user device 10, cause the user device 10 to present network configuration information 162 for each simulated forwarding path 80 to the user 12.
[0038] 3A, in some implementations, the path analyzer 170 includes a network abstraction state machine (NAM) 400 for generating one or more simulated forwarding paths 80. The NAM 400 may be an ideal model of how the VPC network 148 processes data packets. In some examples, the NAM 400 is abstract and therefore independent of the actual implementation of the VPC network 148. Optionally, the NAM 400 identifies a final reachability state 172 of the data packet 24, which includes any one of a delivery state 174a indicating that the data packet 24 is delivered to the destination, a forwarding state 174b indicating that the data packet 24 is forwarded to another network having an unknown configuration, a deletion state 174c indicating that the data packet 24 is deleted due to a configuration checkpoint failure or missing configuration, or an abort state 174d indicating that network reachability analysis is not possible due to missing critical configuration. The NAM 400 may be non-deterministic in that a state may have multiple successor states. For example, if several routes with the same IP mask and priority are applied to a data packet, a route is selected among them based on an unspecified hash function. This is essentially a deterministic process, but is better modeled by selecting one of the routes non-deterministically, since the hash function is an internal implementation that may change.
[0039] 3B, the cloud reachability analyzer 150 provides the determined reachability status 172 of each simulated forwarding path 80 to the user device 10. This causes the user device to present the network configuration information 162 of each simulated forwarding path 80 to the user 12. For example, the report 300 may show the user 12 details about the generated data packets 24 (e.g., packet headers 22). The report 300 may show information related to each step 310, 310a-n or hop along the traced or simulated forwarding path 80. In the illustrated example, a data packet 24 departs from a source instance in step 310a (i.e., step 0), has egress firewall rules applied in step 310b (i.e., step 1), is routed in step 310c (i.e., step 2), reaches a destination instance in step 310d (i.e., step 3), has ingress firewall rules applied in step 310e (i.e., step 4), and is delivered to the destination instance in step 310f (i.e., step 5). Each of these steps 310 includes associated network configuration information 162.
[0040] The report 300 may indicate the reason or rationale for the identified reachability status 172 of each simulated forwarding path 80 (e.g., the packet was dropped because it was rejected by a firewall rule) to aid in troubleshooting and / or to detect network connectivity caused by inconsistent and invalid configurations, or to validate new or changed configurations. In some examples, the cloud reachability analyzer 150 provides a configuration change impact analysis. Each of the simulated forwarding paths 80 may be presented as part of a graphical user interface (GUI) on a user device as part of an application (e.g., a web browser). Although the illustrated example provides details about only one forwarding path 80 (i.e., trace 1), each simulated forwarding path 80 (i.e., multiple traces) may be provided. In some examples, the report 300 includes a summary section 320 that indicates the identified reachability status 172 of the data packet 24.
[0041] 4, in some implementations, NAM 400 includes egress check 410, ingress check 420, and path-specific check 430. In some examples, egress check 410 includes egress firewall check 412 and match route 414. Egress firewall check looks for a matching egress firewall rule (e.g., in network configuration information 162). The egress firewall rule is a firewall rule that applies to the source instance (e.g., VM 250). Match route 414 may look for and apply an appropriate route for simulated forwarding path 80. Match route 414 may also determine whether there is a matching route for destination IP address 25b when the source instance is VM 250. If there is no matching route, NAM 400 may match the route to a default route with the next hop as an Internet gateway. Ingress firewall check 422, like egress firewall check 412, finds and applies matching ingress firewall rules (i.e., firewall rules that apply to the destination instance).
[0042] The path-specific checks 430 are based on the type of simulated forwarding path 80 that the NAM 400 is evaluating. That is, the path-specific checks 430 depend on the source and destination instances of the simulated forwarding path 80. For example, if the destination instance is a VPN gateway 432 via VPN tunnel 434, certain states (FIG. 7) are included in the evaluation by NAM 400. Similarly, if the destination instance is a load balancer with forwarding rule 436, different states (FIGS. 6 and 8) are evaluated. If the destination instance is a peering network gateway 438, still other states are evaluated in the state machine of NAM 400.
[0043] 5-9 are diagrams illustrating example state machines 500, 600, 700, 800, 900 representing the NAM 400 when analyzing various simulated forwarding paths 80 of a data packet 24. For example, FIG. 5 illustrates a state machine 500 of the NAM 400 when analyzing a simulated forwarding path 80 between a first VM 250 and a second VM 250 or from the first VM 250 to the Internet 60. The state machine 500 starts at an instance state 510 corresponding to a source VM 250. From there, the state machine 500 transitions to an abort state 512 (e.g., where the analysis cannot continue due to missing network configuration information 162), an apply egress firewall rule 514, or a check spoof 518 state where the VM 250 is permitted to send and receive data packets with a foreign IP. In a delete state 516, the data packet 24 may be deleted due to a failed network configuration check or missing network configuration information 162. In state 520, an appropriate route is found and applied, the data packet 24 may reach the VM instance in state 522, the data packet 24 may be forwarded to another network whose configuration is unknown (and thus analysis stops) in state 528, the packet header 22 may be modified by network address translation (NAT) in state 526, or ingress firewall rules may be applied in state 524. In state 530, the data packet 24 is delivered to the destination specified in the packet header 22.
[0044] 6, state machine 600 represents NAM 400 as it analyzes a simulated forwarding path 80 between VM 250 and load balancer 1110 (FIG. 11). State machine 600 starts at an instance state 610 corresponding to source VM 250. From there, state machine 600 transitions to abort state 612 (e.g., analysis cannot continue due to missing network configuration information 162), apply egress firewall rules 614, or check spoof 618 states where VM 250 is allowed to send and receive data packets with an external IP. In delete state 616, data packet 24 may be deleted due to a failed network configuration check or missing network configuration information 162. In state 620, an appropriate route is found and applied, and in state 622, the data packet may be forwarded to another network whose configuration is unknown (and thus analysis stops). In state 624, the NAM 400 applies the appropriate forwarding rules and reaches the internal or external load balancer 1110 in state 626. From there, the data packet 24 may be forwarded to one or more backends 628, 628a-n, where the data packet is either dropped in state 630 or delivered in state 632.
[0045] 7, state machine 700 represents NAM 400 as it analyzes a simulated forwarding path 80 between VM 250 and on-premise network 70 over a VPN. State machine 700 begins with an instance state 710 corresponding to source VM 250. From there, state machine 600 transitions to an abort state 712 (e.g., analysis cannot continue due to missing network configuration information 162), apply egress firewall rules 714, or check spoofing 718 state where VM 250 is allowed to send and receive data packets with an external IP. In delete state 716, data packet 24 is deleted due to a network configuration check failure or missing network configuration information 162. In state 720, the data packet 24 may be removed due to lack of information 162. In state 720, an appropriate route is found and applied, and in state 722, the data packet 24 is forwarded to another network whose configuration is unknown (thus, analysis stops) and then forwarded to one or more on-premise backends 728, 728a-n. In state 724, the data packet 24 reaches the local side of the VPN tunnel, and in state 726, the data packet 24 may reach a VPN gateway and be forwarded to one or more VCP backends 628.
[0046] 8, state machine 800 represents NAM 400 in analyzing a simulated forwarding path 80 between Internet 60 and VM 250 or between Internet 60 and load balancer 1110. State machine 800 starts with an Internet state 810 with a data packet 24 originating from Internet 60. From there, state machine 800 may proceed to state 816 where the data packet 24 is dropped due to a failed network configuration check or missing network configuration information 162. State machine 800 may also proceed to state 812 where the packet header 22 is modified by NAT. From NAT state 812, data packet 24 reaches a VM instance in 818 and is either dropped in state 820 or delivered in state 822. State machine 800 may also proceed to state 814 where the appropriate forwarding rules are applied if the destination is load balancer 1110. From there, the state machine 800 proceeds to state 824, where the data packet 24 reaches an external load balancer. The state machine 800 then transitions to a proxy connection state 826, where the previous connection is proxied to a new connection and the NAM 400 generates a new data packet 24 for subsequent tracing or simulation. Otherwise, the state machine 800 simulates forwarding the data packet 24 to one or more backends 628, and the data packet is either dropped in state 828 or delivered in state 830.
[0047] 9, state machine 900 represents NAM 400 in analyzing a simulated forwarding path 80 between on-premise network 70 (e.g., a VM located within on-premise network 70) and VCP VM 250. Here, state machine 900 begins at state 910 where a data packet 24 originates from a private network (e.g., on-premise network 70). From there, state machine 900 transitions to state 912 to apply the appropriate route. State machine 900 then either drops the packet due to a failed network configuration check or missing network configuration information 162 in state 914, or proceeds to reach an instance in state 916. From there, NAM 400 applies ingress firewall rules in state 918 and delivers the data packet in state 920.
[0048] In some examples, the cloud reachability analyzer 150 simulates the forwarding path 80 by tracing the route advertised by the VPC network 148 back to the on-premise network 70. Although the cloud reachability analyzer 150 does not generally have access to the on-premise network configuration, the cloud reachability analyzer 150 does have access to the configuration of static and dynamic routes to the on-premise network 70, for example, via a VPN. Thus, the cloud reachability analyzer may simulate the route of the VPC network 148 that the on-premise network 70 should have configured or received due to the dynamic route. If the data packet 24 is sourced from the on-premise network range (derived from the VPN-related route), the cloud reachability analyzer 150 may apply the "inferred" route on the packet.
[0049] 10A and 10B, Tables 1000a and 1000b show the NAM40 10 shows the possible final reachability states 172 (i.e., delete 174a, forward 174b, deliver 174c or abort 174d) of a data packet at state machine 500, 600, 700, 800, 900, the states of NAM 400 prior to the final state (FIGS. 5-9), and the associated causes of the final states. That is, tables 1000a, 1000b provide examples of causes of transitions to final states 174a-d in state machines 500, 600, 700, 800, 900.
[0050] 11, an exemplary forwarding path 80c starts from an external host (e.g., user device 10) and proceeds through the Internet 60 to a load balancer 1110 in the VPC network 148. The load balancer 1110 forwards the data packet to a front-end server 1020, which distributes the data packet to one or more back-ends or VMs 250. In this scenario, the forwarding path 80c is more complex than a typical network-level load balancer. In this example, the cloud reachability analyzer 150 traces the data packet 24 from the external host (e.g., user device 10) to the load balancer 1110 (e.g., a global HTTPS load balancer). In some examples, the load balancer is a proxy load balancer, so the TCP connection terminates at the front-end server 1020, which initiates a new TCP connection with one or more back-end VMs 250. The cloud reachability analyzer uses the NAM 400 to simulate this behavior. In a real data plane, a load balancing algorithm may select a VM for each connection, but cloud reachability analyzer 150 may be a static configuration analysis tool that does not predict data plane paths, but instead identifies any configuration issues and provides the user with further visibility into expected behavior. Thus, in this case, cloud reachability analyzer 150 provides a trace for each possible path (e.g., a first trace for VM 250a, a second trace for VM 250b, and a third trace for VM 250b).
[0051] 12 is a flow chart of an example arrangement of operations for a method 1200 of performing cloud network reachability analysis. The method 1200 includes, at operation 1202, receiving, at the data processing hardware 144, a reachability query 20 requesting a reachability status 172 of a target 70, 250, 1110. The reachability query 20 includes a packet header 22 associated with a data packet 24, the packet header 22 including a source IP address 25a associated with a source of the data packet 24 and a destination IP address 25b associated with a destination of the data packet 24.
[0052] At operation 1204, the method 1200 includes the data processing hardware 144 generating one or more simulated forwarding paths 80 for the data packet 24 based on the packet header 22 using the data plane model 164. Each of the simulated forwarding paths 80 includes corresponding network configuration information 162. At operation 1206, the method 1200 includes the data processing hardware 144 determining a reachability status 172 for the target 70, 250, 1110 based on the one or more simulated forwarding paths 80. At operation 1208, the method 1200 includes the data processing hardware 144 providing the determined reachability status 172 and the one or more simulated forwarding paths 80 to the user device 10 associated with the reachability query 20. The one or more simulated forwarding paths 80, when received by the user device 10, cause the user device 10 to present the network configuration information 162 for each simulated forwarding path 80.
[0053] FIG. 13 illustrates a system that may be used to implement the systems and methods described herein. 13 is a schematic diagram of an exemplary computing device 1300. Computing device 1300 is intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other suitable computers. The components shown, their connections and relationships, and their functions are intended to be exemplary only and are not intended to limit the implementation of the invention as described and / or claimed herein.
[0054] The computing device 1300 includes a processor 1310, a memory 1320, a storage device 1330, a high-speed interface / controller 1340 that connects to the memory 1320 and a high-speed expansion port 1350, and a low-speed interface / controller 1360 that connects to a low-speed bus 1370 and the storage device 1330. Each of the components 1310, 1320, 1330, 1340, 1350, and 1360 are interconnected using various buses and may be mounted on a common motherboard or otherwise as appropriate. The processor 1310 can process instructions for execution within the computing device 1300, including instructions stored in the memory 1320 or on the storage device 1330 for displaying graphical information for a graphical user interface (GUI) on an external input / output device, such as a display 1380 coupled to the high-speed interface 1340. In other implementations, multiple processors and / or multiple buses may be used as appropriate, along with multiple memories and multiple types of memories. Also, multiple computing devices 1300 may be connected, with each device providing a portion of the required operations (eg, as a server bank, a group of blade servers, or a multi-processor system).
[0055] The memory 1320 stores information non-transiently within the computing device 1300. The memory 1320 may be a computer readable medium, a volatile memory unit, or a non-volatile memory unit. The non-transient memory 1320 may be a physical device used to temporarily or permanently store programs (e.g., sequences of instructions) or data (e.g., program state information) for use by the computing device 1300. Examples of non-volatile memory include, but are not limited to, flash memory and read-only memory (ROM) / programmable read-only memory (PROM) / erasable programmable read-only memory (EPROM) / electronically erasable programmable read-only memory (EEPROM) (e.g., commonly used in firmware such as boot programs). Examples of volatile memory include, but are not limited to, random access memory (RAM), dynamic random access memory (DRAM), static random access memory (SRAM), phase change memory (PCM), and disk or tape.
[0056] The storage device 1330 can provide mass storage for the computing device 1300. In some implementations, the storage device 1330 is a computer-readable medium. In various different implementations, the storage device 1330 may be a floppy disk device, a hard disk device, an optical disk device, or a tape device, a flash memory or other similar solid-state memory device, or an array of devices, including devices in a storage area network or other configurations. In further implementations, a computer program product is tangibly embodied in an information carrier. The computer program product includes instructions that, when executed, perform one or more methods, such as the methods described above. The information carrier is a computer or machine-readable medium, such as the memory 1320, the storage device 1330, or the memory on processor 1310.
[0057] The high-speed controller 1340 manages bandwidth-intensive operations for the computing device 1300, while the low-speed controller 1360 manages less bandwidth-intensive operations. Such role assignments are merely exemplary. In some implementations, the high-speed controller 1340 is coupled to the memory 1320, the display 1380 (e.g., via a graphics processor or accelerator), and a high-speed expansion port 1350 that may accept various expansion cards (not shown). In some implementations, the low-speed controller 1360 is coupled to the storage device 1330 and the low-speed expansion port 1390. The low-speed expansion port 1390, which may include various communication ports (e.g., USB, Bluetooth, Ethernet, wireless Ethernet), may be coupled to one or more input / output devices (keyboards, pointing devices, scanners, etc.) or networking devices (such as switches or routers), for example, via a network adapter.
[0058] The computing device 1300 may be implemented in many different forms, as shown in the figure: for example, it may be implemented as a standard server 1300a, or multiple times in a cluster of such servers 1300a, or as a laptop computer 1300b, or as part of a rack server system 1300c.
[0059] Various implementations of the systems and techniques described herein may be realized in digital electronic and / or optical circuitry, integrated circuits, specially designed ASICs (application specific integrated circuits), computer hardware, firmware, software, and / or combinations thereof. These various implementations may include implementations in one or more computer programs executable and / or interpretable on a programmable system including at least one programmable processor, which may be a special purpose processor or a general purpose processor, coupled to transmit and receive data and instructions from a storage system, at least one input device, and at least one output device.
[0060] A software application (i.e., a software resource) may refer to computer software that causes a computing device to perform tasks. In some examples, a software application may be referred to as an "application," "app," or "program." Examples of applications include, but are not limited to, system diagnostic applications, system management applications, system maintenance applications, word processing applications, spreadsheet applications, messaging applications, media streaming applications, social networking applications, and gaming applications.
[0061] These computer programs (also known as programs, software, software applications or code) contain machine instructions for a programmable processor and may be implemented in high level procedural and / or object oriented programming languages and / or in assembly / machine languages. As used herein, the terms "machine readable medium" and "computer readable medium" refer to any computer program product, non-transitory computer readable medium, apparatus and / or device (e.g., magnetic disk, optical disk, memory, programmable logic device (PLD)) used to provide machine instructions and / or data to a programmable processor, including machine readable media that receive machine instructions as a machine readable signal. The term "machine readable signal" refers to a medium that receives the machine instructions and / or data. This refers to any signal used to provide a programmable processor with
[0062] The processes and logic flows described herein can be executed by one or more programmable processors, also referred to as data processing hardware, which execute one or more computer programs to perform functions by operating on input data and generating output. The processes and logic flows can also be executed by special purpose logic circuitry (e.g., FPGAs (field programmable gate arrays) or ASICs (application specific integrated circuits)). Processors suitable for executing computer programs include, by way of example, general purpose and special purpose microprocessors, and include any one or more processors of any type of digital computer. In general, a processor receives instructions and data from a read-only memory or a random access memory or both. The essential elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. In general, a computer also includes one or more mass storage devices (e.g., magnetic, magneto-optical or optical disks) for storing data, or is operatively coupled to receive, transmit, and receive data from one or more mass storage devices. However, a computer need not have such devices. Computer-readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media and memory devices, including, by way of example, semiconductor memory devices (e.g., EPROM, EEPROM and flash memory devices), magnetic disks (e.g., internal hard disks or removable disks), magneto-optical disks, and CD-ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.
[0063] To provide for user interaction, one or more aspects of the disclosure can be implemented on a computer having a display device (e.g., a CRT (cathode ray tube), LCD (liquid crystal display) monitor or touch screen) for displaying information to the user, and optionally a keyboard and pointing device (e.g., a mouse or trackball) by which the user can provide input to the computer. Other types of devices can also be used to provide user interaction, for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback or tactile feedback), and input from the user can be received in any form, including acoustic input, speech input or tactile input. The computer can also interact with the user by sending and receiving documents to and from a device used by the user, for example by sending a web page to a web browser on the user's client device in response to a request received from the web browser.
[0064] Several implementations have been described. However, it will be understood that various modifications may be made without departing from the spirit and scope of the disclosure. Accordingly, other implementations are within the scope of the following claims.
Claims
1. 1. A computer-implemented method executed by data processing hardware, the method causing the data processing hardware to perform operations, the operations comprising: receiving a Virtual Private Cloud (VPC) reachability request from a user device requesting reachability status of network traffic from a source Internet Protocol (IP) address of a VPC network to a destination IP address of the VPC network, the VPC reachability request including a protocol type, the operations further comprising: Obtaining network configuration information that defines a configuration of the VPC network; and generating a simulated forwarding path for the data packet based on a source IP address and the destination IP address using the model and the network configuration information, the simulated forwarding path including a plurality of hops, the operations further comprising: determining that the destination IP address is unreachable from the source IP address based on the simulated forwarding path; and generating a reachability report in response to determining that the destination IP address is unreachable, the reachability report comprising: each hop of the plurality of hops of the simulated forwarding path; and a reason why the destination IP address is unreachable from the source IP address, the operation further comprising: providing the reachability report to the user device.
2. The method of claim 1 , wherein the VPC reachability request further comprises a destination port.
3. The method of claim 1 or 2, wherein determining that the destination IP address is unreachable comprises using a network abstraction state machine.
4. The network configuration information is a port / interface for directing the data packet within the VPC network; firewall rules applied to the data packet at each step along the simulated forwarding path; and The method of any of claims 1 to 3, comprising a network configuration associated with each hop of said plurality of hops along said simulated forwarding path.
5. Determining that the destination IP address is unreachable includes: a deleted state indicating that said data packet is deleted due to a configuration checkpoint failure or missing configuration; or The method of any of claims 1 to 4, further comprising determining an abort condition, indicating that network reachability analysis of the destination IP address is not possible due to a missing configuration.
6. The VPC reachability request is: A source port associated with the data packet; and The method of any one of claims 1 to 5, further comprising: a destination port associated with said data packet.
7. the source IP address is associated with a first virtual machine (VM); The method of any preceding claim, wherein the destination IP address is associated with a second VM.
8. The method according to any one of claims 1 to 7, wherein at least one hop of the plurality of hops includes a load balancer within the VPC network.
9. The method of any one of claims 1 to 8, wherein determining that the destination IP address is unreachable includes determining path-specific checks from the network configuration information based on a type of the simulated forwarding path.
10. The method of claim 9 , wherein the type of the simulated forwarding path is based on a source instance and a destination instance of the simulated forwarding path.
11. 1. A system comprising: Data processing hardware; and memory hardware in communication with the data processing hardware, the memory hardware storing instructions that, when executed on the data processing hardware, cause the data processing hardware to perform operations, the operations including: receiving a Virtual Private Cloud (VPC) reachability request from a user device requesting reachability status of network traffic from a source Internet Protocol (IP) address of a VPC network to a destination IP address of the VPC network, the VPC reachability request including a protocol type, the operations further comprising: Obtaining network configuration information that defines a configuration of the VPC network; and generating a simulated forwarding path for the data packet based on a source IP address and the destination IP address using the model and the network configuration information, the simulated forwarding path including a plurality of hops, the operations further comprising: determining that the destination IP address is unreachable from the source IP address based on the simulated forwarding path; and generating a reachability report in response to determining that the destination IP address is unreachable, the reachability report comprising: each hop of the plurality of hops of the simulated forwarding path; and a reason why the destination IP address is unreachable from the source IP address, the operation further comprising: providing the reachability report to the user device.
12. The system of claim 11 , wherein the VPC reachability request further comprises a destination port.
13. 13. The system of claim 11 or 12, wherein determining that the destination IP address is unreachable includes using a network abstraction state machine.
14. The network configuration information is a port / interface for directing the data packet within the VPC network; firewall rules applied to the data packet at each step along the simulated forwarding path; and The system of any of claims 11 to 13, comprising a network configuration associated with each hop of said plurality of hops along said simulated forwarding path.
15. Determining that the destination IP address is unreachable includes: a deleted state indicating that said data packet is deleted due to a configuration checkpoint failure or missing configuration; or The system of any of claims 11 to 14, further comprising determining an abort condition indicating that network reachability analysis of the destination IP address is not possible due to missing configuration.
16. The VPC reachability request is: A source port associated with the data packet; and A system according to any one of claims 11 to 15, further comprising a destination port associated with the data packet.
17. the source IP address is associated with a first virtual machine (VM); The system of any of claims 11 to 16, wherein the destination IP address is associated with a second VM.
18. The system of any one of claims 11 to 17, wherein at least one hop of the plurality of hops includes a load balancer within the VPC network.
19. The system of any one of claims 11 to 18, wherein determining that the destination IP address is unreachable includes determining path-specific checks from the network configuration information based on a type of the simulated forwarding path.
20. 20. The system of claim 19, wherein the type of the simulated forwarding path is based on a source instance and a destination instance of the simulated forwarding path.
Citation Information
Patent Citations
System and method for network management
JP2017524320A
Network system and method for cross region virtual private network peering
US20190097940A1
