Why Can't I Ping My EIP After It Is Bound to an RDS DB Instance?
Fault Location
- Check security group rules.
- Check network ACLs.
- Ping the affected EIP from another ECS 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.
- Click in the upper left corner of the page and choose Databases > Relational Database Service.
- On the Instances page, click the target DB instance name to go to the Overview page.
- Under Security Group, click the security group name.
- 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. If the network ACL is disabled, the default rule still takes effect.
- Ping the affected EIP from another ECS in the same region.
Use another ECS in the same region to ping the EIP. If the EIP can be pinged, the virtual network is normal. Contact technical support.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot