Help Center> Relational Database Service> FAQs> Database Connection> Why Can't I Ping My EIP After It Is Bound to a DB Instance?
View PDF

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

Fault Location

  1. Check security group rules.
  2. Check network ACLs.
  3. Ping the affected EIP from another ECS 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 a project.
    3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
    4. On the Instance Management page, click the target DB instance.
    5. In the Connection Information area, click the security group.
    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 ACLs.
    1. Check the network ACL status.
    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 affected EIP from another ECS 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 customer service for technical support.

Parent topic: Database Connection