Run the PING command from an Elastic Compute Service (ECS) instance to verify network connectivity to a Tair or Redis Open-Source Edition instance. Use this check when you cannot connect to an instance after creation or during normal operation.
Prerequisites
Before you begin, ensure that you have:
-
A running Tair or Redis Open-Source Edition instance
Test connectivity
-
Get the endpoint of the Tair instance. For details, see View endpoints.
-
Log on to the ECS instance and run the following command in the CLI, replacing the endpoint with your own:
NoteThis command works on both Windows and Linux.
ping r-bp1zx****.redis.rds.aliyuncs.com -
Check the output:
-
Success: All responses return successfully.
-
Failure: No responses are returned. See Troubleshooting below.
-
Windows
By default, Windows sends four PING packets and then stops. To run a continuous test:
ping <host> -t
Linux
Linux continuously sends PING packets. Press Ctrl+C to stop and view statistics.
Figure 1. PING command output on Linux 
Troubleshooting
If no successful responses are returned, check the following common causes.
DNS resolution failure
The domain name of the Tair instance endpoint cannot be resolved. For steps to diagnose and fix this, see How do I troubleshoot connection issues caused by failed DNS resolution?
Security group misconfiguration
Abnormal behavior on the ECS instance may trigger a security policy that blocks outbound traffic. Configure precise outbound rules for the ECS security group to allow connections to the Tair instance IP address on port 6379 (in this example). For steps, see Add a security group rule.
Client firewall restrictions
The network firewall on the ECS instance may be blocking outbound connections to the Tair instance. Check the firewall settings on the client and allow traffic to the Tair instance endpoint.