This topic describes how to diagnose elastic IP addresses (EIPs) and troubleshoot EIP issues. The instance diagnostics feature allows you to check EIP configurations and status, and provides solutions based on detected EIP issues.
Prerequisites
Network Intelligence Service (NIS) is activated. You can activate NIS on the Service activation page.
If this is the first time that you perform an instance diagnostic, the system automatically creates the service-linked role AliyunServiceRoleForNis. For more information, see Service-linked roles.
An EIP is created. For more information, see Apply for an EIP.
Procedure
- Log on to the Elastic IP Address console .
- In the top navigation bar, select the region where the EIP is created.
On the Elastic IP Addresses page, find the EIP and choose in the Diagnose column.
In the Instance Diagnostics panel, you can view the progress, summary, and details of the diagnostic task.
In the Diagnostic Items section, you can select Show All Diagnostic Items to view all diagnostic items of the EIP. In the upper part of the Instance Diagnostics panel, you can click Go to the NIS console to view diagnostic records to go to the Overview page of the NIS console to view more details of the EIP diagnostic. For more information about EIP diagnostic items, see Diagnostic items.
To further diagnose Internet ISP issues of the EIP, perform the following operations.
In the lower part of the Diagnostic Items in the Instance Diagnostics panel, click Internet Diagnostics or Re-diagnose.
In the Internet Diagnostics dialog box, specify Access Area and Destination Instance, and click OK.
After you specify Access Area, you can check the Internet connectivity between ISPs in the Chinese mainland and the EIP, or between ISPs outside the Chinese mainland and the EIP. If access fails, the system provides you with possible causes, as well as suggestions on how to solve the issues. For more information, see Internet diagnostic results.
Diagnostic items and details
Diagnostic items and details
The following table describes the EIP diagnostic items.
Category | Diagnostic item and description |
Configuration Diagnostics |
|
Quota Limit Diagnostics |
|
Security Policy Diagnostics |
|
Cost Diagnostics |
|
Internet diagnostic result
The following table describes the possible causes of access failure and provides suggestions after you run EIP Internet diagnostics.
Possible cause | Suggestion |
Blocked by cloud security policies | Check whether the request is blocked by the security policies of the following services:
|
Blocked by security policies of the associated resource | Check whether requests are blocked by the resource associated with the EIP. For example, if the EIP is associated with an Elastic Compute Service (ECS) instance, requests may be blocked by security rules of the ECS instance. You need to check iptables rules, firewall rules, and third-party security applications of the ECS instance, and check whether the network driver is properly installed. |
Blocked by the ISP | After you complete the preceding steps, if the EIP still cannot be accessed, another possible cause for EIP access failure is ISP blocking. You can run an Internet diagnostic on the EIP to check the regions where access to the EIP fails. For more information, see Diagnose an EIP. If the EIP is blocked by the ISP, refer to the following suggestions:
|
References
For more information about the instance diagnostics feature, see Work with instance diagnostics.
You can also use the self-service diagnostics feature to troubleshoot EIP issues, such as access failures, access exceptions, quota issues, and fee issues. For more information, see Troubleshooting.