Network diagnosis

更新时间:
复制 MD 格式

Bastionhost lets you check the connectivity between your Bastionhost instance and your assets, either automatically or manually. This feature helps you pinpoint and troubleshoot connection issues by verifying network reachability.

Periodic connectivity checks

  1. Log on to the Bastionhost console. In the top navigation bar, select the region where your Bastionhost instance is located.

  2. In the list of Bastionhost instances, find the target instance and click Manage.

  3. In the navigation pane on the left, click System Settings.

  4. On the Network Diagnosis tab, in the Connectivity Check Settings section, select Periodic Check of Asset Connectivity and set a check interval.

    Valid values: 1 to 24 hours.

    The results of the connectivity check are displayed in the Network Status column of the asset list. Possible statuses include normal, port exception, network timeout, and proxy server exception. For more information, see Manage hosts.

Manual network connectivity test

  1. Log on to the Bastionhost console. In the top navigation bar, select the region where your Bastionhost instance is located.

  2. In the list of Bastionhost instances, find the target instance and click Manage.

  3. In the navigation pane on the left, click System Settings.

  4. On the Network Diagnosis tab, in the Connectivity Test section, enter the Target Address and Port, and then click Test Connection.

    The test result is displayed in a message. For troubleshooting steps, see Troubleshooting connectivity issues.

Note
  • Alternatively, navigate to the Assets > Hosts or Assets > Database page and click Check Network Status of Asset to run a connectivity check.

  • On an operations page, the network status for assets is retrieved from the Assets page by default upon a page refresh. If you manually run a check on the operations page, the result updates the network status for the current session on that page only. This result is not synchronized with the Assets page.

Troubleshooting connectivity issues

If a connectivity test fails, check the following possible causes:

  • Check if the security group rules allow traffic from the Bastionhost instance to the host's port.

  • Check if Cloud Firewall is enabled for the host and has an access control policy that allows traffic from the Bastionhost instance to the host's port. For more information, see Best practices for integrating Cloud Firewall with Bastionhost.

  • Check if an on-premises firewall is active on the host and has a policy that allows traffic from the Bastionhost instance to the host's port.

Related documents