Why Cannot I Ping My EIP After It Is Bound to a DB Instance?
Fault Locating
- Check security group rules.
- Check network ACLs.
- Ping the ECS to the instance in the same region.
Solution
- Check security group rules.
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click in the upper left corner of the page, choose .
- On the Instances page, click the instance name to go to the Basic Information page.
- In the Network Information area on the Basic Information page, click the security group.
- 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
(all IP addresses)
Inbound
IPv4
ICMP: Any
0.0.0.0/0
(all IP addresses)
- Check network ACLs.
- Check the network ACL status.
- Check whether the NIC to which the EIP bound belongs to the subnet associated with the network ACL.
- 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.
- 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.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.