Help Center/
Cloud Connect/
FAQs/
Cloud Connection/
Why VPCs Communicate with Each Other Across Regions After They Have Been Loaded to a Cloud Connection?
Updated on 2025-04-18 GMT+08:00
Why VPCs Communicate with Each Other Across Regions After They Have Been Loaded to a Cloud Connection?
After you complete all the required configuration, you can use ICMP or Telnet to verify network connectivity. If communication fails, do the following to locate the fault:
- Check whether the security group containing the ECSs in the destination VPC allows ICMP or Telnet traffic over the corresponding port in the inbound direction. If ICMP or Telnet traffic is not allowed, the packets will be blocked by the security group.
- Check whether a network ACL is configured for the subnet in the destination VPC to deny traffic from the source VPC. If such an ACL exists, the packets will be blocked by the ACL.
- Check whether there are overlapping subnets in the source and destination VPCs. If they have overlapping subnets, the packets will not be sent to the subnet of the destination VPC.
- Check whether an inter-region bandwidth is assigned between source and destination regions. If you have a bandwidth package but there is no inter-region bandwidth between different regions, the default 10 kbit/s of bandwidth may fail to transmit large ICMP packets or Telnet packets.
Parent topic: Cloud Connection
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.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot