Network Probe

Last updated: 2020-08-13 11:09:25

    The Tencent Cloud network probe service is used to monitor the quality of VPC network connections, including latency, packet loss rate, and other key metrics.

    Under the hybrid cloud network architecture, you can use VPN or Direct Connect to connect the VPC on Tencent Cloud with your own IDC. To monitor the network quality of connections in real time, you can create a network probe in the subnet that needs to communicate with the IDC. And then, you will obtain the packet loss rate and latency of the probed link, and fulfill the following purposes:

    • Real-time monitoring of connection quality
    • Real-time connection failure alarm

    Instructions

    • The network probe service adopts ping method with a frequency of 20 detections per minute.
    • Up to 50 probes are allowed for each VPC.
    • A maximum of 20 subnets under the same VPC can have network probes.

    Creating a Network Probe

    1. Log in to VPC Console.
    2. Select Diagnostic Tools -> Network Probe in the left sidebar to enter the management page.
    3. Click +New at the top of the Network Probe page.
    4. In the Create Network Probe pop-up window, fill in relevant fields.

      Note:

      • The network probe route is assigned by the system and cannot be modified.
      • When you switch the route of subnet, this default route will be removed from the original route table associated with the subnet, and be added to the new route table associated.


    Field description

    Field Description
    Name Name of the network probe.
    VPC The VPC to which the probe source IP belongs.
    Subnet The subnet to which the probe source IP belongs.
    Probe Destination IP A maximum of two destination IPs are supported for the network probe. Please ensure that you’ve enabled ICMP firewall policy for the destination server of network probe.
    Next hop You can choose to "Specify" or "Do Not Specify" the next hop.
    • If "Do Not Specify" is chosen, no next hop will be selected.
      Note:

      If you do not want to specify the next hop,submit a ticket to enable this allowlist feature.

    • If you specify the next hop, select the next hop type and instances. And then, the system automatically adds the corresponding 32-bit route to the subnet-associated route table.
    1. Verify the Probe Destination IP
      • If the connection succeeds, click OK.
      • If the connection fails, check whether the subnet route is correctly configured, and whether the probed device enables Network ACL, security group or other firewalls, which may block the connection. For more information, see Managing Network ACLs and Modifying a Security Group Rule.

    Checking the Latency and Packet Loss of a Network Probe

    1. Log in to VPC Console.
    2. Select Diagnostic Tools -> Network Probe in the left sidebar to enter the management page.
    3. Click the monitoring icon of the target network probe instance to view its latency and packet loss rate.

    Modifying a Network Probe

    1. Log in to VPC Console.
    2. Select Diagnostic Tools -> Network Probe in the left sidebar to enter the management page.
    3. In the list, locate the network probe to modify and click Edit in the operation column.
    4. In the Edit Network Probe pop-up window (this example has no next hop specified), make required changes and click Submit to save the changes.

    Deleting a Network Probe

    1. Log in to VPC Console.

    2. Select Diagnostic Tools -> Network Probe in the left sidebar to enter the management page.

    3. In the list, locate the network probe to delete and click Delete in the operation column.

    4. Click Delete in the pop-up window to confirm the deletion.

      Note:

      Deleting a network probe also deletes all related routes.

    Was this page helpful?

    Was this page helpful?

    • Not at all
    • Not very helpful
    • Somewhat helpful
    • Very helpful
    • Extremely helpful
    Send Feedback
    Help