Diagnosing network connectivity and performance bug in the cloud can exist a challenge every bit your network evolves in complexity. Nosotros are pleased to announce the preview of a new feature to check network connectivity in a variety of scenarios when using VM.

The Azure Network Watcher Connectivity Bank check characteristic helps to drastically reduce the corporeality of fourth dimension needed to find and detect connectivity problems in the infrastructure. The results returned tin provide valuable insights to whether a connectivity outcome is due to a platform or a potential user configuration. Network Watcher Connectivity Check can be used from the Azure portal, using PowerShell, Azure CLI, and Remainder API.

Connectivity Check is supported in a diverseness of scenarios – VM to a VM, VM to an external endpoint, and VM to an on-premise endpoint. Leveraging a common and typical network topology, the example beneath illustrates how Connectivity Cheque can assist resolve network reachability issues using the Azure portal. At that place is a VNet hosting a multi-tier web application and four subnets, amongst which are an application subnet and a database subnet.

Figure 1 – Multi-tier web application

Figure 1 – Multi-tier web application

On the Azure portal, navigate to Azure Network Watcher and under Network Diagnostic Tools click on Connectivity Check. Once there, you can specify the Source and Destination VM and click the “Cheque” button to begin the connectivity bank check.

A status indicating
is returned in one case the connectivity cheque completes. The number of hops, the minimum, average and maximum latency to reach the destination are also returned.

Figure 2- Connectivity check – access from Portal
Figure 2 – Connectivity Check – access from portal

In this case, a connectivity check was washed from the VM running the awarding tier to the VM running the database tier. The status is returned as
and information technology’southward important to note, ane of the hops indicated a
condition. Clicking on the hop indicates the presence of an NSG rule that is blocking all traffic, thereby blocking end-to-end connectivity.

Baca Juga :   Jelaskan Hubungan Proses Sosialisasi Tidak Sempurna Dengan Kenakalan Remaja

Figure 3- Unreachable status
Effigy 3 – Unreachable status

The NSG dominion configuration error was rectified and a connectivity bank check was repeated as illustrated below, where the results at present bespeak an end-to-finish connectivity. The network latency betwixt source and destination, forth with hop data is also provided.

Figure 4 – Reachable status

Effigy 4 – Reachable status

The destination for Connectivity Cheque can exist an IP address, an FQDN, or an ARM URI.

We believe the Connectivity Bank check characteristic will give you deeper insights to network operation in Azure. Nosotros welcome you to reach out, every bit your feedback from using Network Watcher is crucial to help steer the product evolution and eco system growth.