Use connectivity tests to diagnose and troubleshoot your network
You want to make sure that resources that are necessary for network management are accessible while keeping resources that shouldn’t be accessible safe. Connectivity Tests is fortunately available to assist. With the use of connectivity tests, you can rapidly identify potential network connectivity issues and confirm that your firewall rules and other network configurations are operating as intended.
With the use of connectivity tests, a diagnostics tool, you may verify the connectivity between network endpoints, or the source or destination of network traffic, to aid in self-triage and troubleshooting of network issues. You can confirm that your setups are working as intended by using connectivity tests to evaluate the reachability of important network paths, such as those that lead to on-premises, and to make sure that your critical services, like Cloud SQL, are accessible. Connectivity tests can assist you in debugging:
- Inadequate layouts that are not designed
- Outdated setups brought about by migrations or modifications to the network configuration
- Configuration mistakes pertaining to various network services and features
With great pleasure, Google now have updated Connectivity Tests coverage to assist you in determining whether your network services are reachable.
Support for new static configuration analysis
In order to assess a packet’s reachability, connectivity tests analyze the static configuration between the source and destination endpoints, generating a trace path that illustrates the anticipated packet path hop-by-hop. Now let’s examine the modifications made to the static configuration analysis support for Connectivity Tests:
1. As a destination, support for forwarding rules
Connectivity Test destinations can now include Private Service Connect endpoints, external load balancers, and internal load balancers. The improved coverage makes it possible to diagnose connectivity problems impacting these endpoints more effectively.
2. Assistance with Cloud SQL instances based on Private Service Connect
You might want to use Private Service Connect to deploy Cloud SQL in order to construct customizable topologies. It is now possible to designate these instances as destinations for connectivity tests.
3. Assistance with external Cloud SQL instances (on-premises)
Connectivity Tests are now available for customers accessing Cloud SQL from on-premises apps to confirm their hybrid installations. With the ability to choose external Cloud SQL instances as sources or destinations for Connectivity Tests, this is now feasible.
4. Expanded protection for firewalls
Regional firewall settings can now be included in the analysis of Connectivity Tests, regulating traffic flow across several Google Cloud regions. With this improvement, the tool can now offer an even more thorough and integrated assessment of network connection, accounting for the effects of these more expansive firewall rules.
5. Better analysis of routes
The same routing data that is accessible through the Google Cloud console’s “Effective routes” section is now used for connectivity tests. Consequently, more support is offered for intricate peering configurations (where it is necessary to resolve conflicts between several peering routes) and sophisticated dynamic routing scenarios (especially those employing global routing mode).
Real-time data-plane evaluation
Connectivity Tests also carry out real data-plane analysis when applicable. By transferring several probe packets from the source endpoint to the destination, this function checks for connectivity. The analysis’s findings show the quantity of probes despatched, the quantity of probes that arrived at their target safely, and the reachability of the probes. The configuration analysis is not dependent on live data-plane analysis. Instead, real data-plane analysis offers a third-party evaluation of the connectivity condition.
