Help Center/ GaussDB/ FAQs/ Database Connections/ Why Can't I Ping My EIP After It Is Bound to a GaussDB Instance?
Updated on 2024-09-13 GMT+08:00
View PDF
Share

Why Can't I Ping My EIP After It Is Bound to a GaussDB Instance?

Troubleshooting Process

  1. Check security group rules.
  2. Check network ACL rules.
  3. Ping the ECS to the instance in the same region.

Solution

  1. Check security group rules.
    1. Log in to the management console.
    2. Click in the upper left corner and select a region and project.

    3. Click in the upper left corner of the page and choose Databases > GaussDB.
    4. On the Instances page, click the name of the target instance to go to the Basic Information page.
    5. In the Network Information area, click the security group name in the Security Group field.
    6. Check whether the ECS NIC security group allows the inbound ICMP traffic.
      Table 1 Security group rules

      Direction

      Type

      Protocol/Port Range

      Source IP Address

      Inbound

      IPv4

      Any/Any

      0.0.0.0/0

      0.0.0.0/0 indicates all IP addresses.

      Inbound

      IPv4

      ICMP/Any

      0.0.0.0/0

      0.0.0.0/0 indicates all IP addresses.
  2. Check network ACL rules.
    1. Check whether the network ACL is enabled or disabled.
    2. Check whether the NIC to which the EIP bound belongs to the subnet associated with the network ACL.
    3. If the network ACL is enabled, add an ICMP rule to allow traffic.

    The default network ACL rule denies all incoming and outgoing packets. After the network ACL is disabled, the default rule still takes effect.

  3. Ping the ECS to the instance in the same region.

    If the affected EIP can be pinged from another ECS in the same region, the virtual network is functional. In such a case, contact technical support.

Parent topic: Database Connections