Help Center > > FAQs> Connectivity> What Should I Do If a Virtual IP Address Cannot Be Pinged After It Is Bound to an ECS NIC?

What Should I Do If a Virtual IP Address Cannot Be Pinged After It Is Bound to an ECS NIC?

Updated at:Dec 09, 2020 GMT+08:00

Symptom

After a virtual IP address is bound to an ECS NIC, the virtual IP address cannot be pinged.

Troubleshooting

The following fault causes are sequenced based on their occurrence probability.

If the fault persists after a possible cause is rectified, check other possible causes.

Figure 1 Troubleshooting
Table 1 Troubleshooting

Possible Cause

Solution

Incorrect Virtual IP Address of the ECS NIC

See Incorrect Virtual IP Address of the ECS NIC

Incorrect ECS NIC Configuration

See Incorrect ECS NIC Configuration

Incorrect Security Group or Network ACL Configuration

See Incorrect Security Group or Network ACL Configuration

Incorrect Virtual IP Address of the ECS NIC

Check whether the source/destination check of the NIC is disabled and whether the virtual IP address has been bound to the NIC.
  1. Log in to the management console.
  2. Click Service List and click Elastic Cloud Server under Computing.
  3. In the ECS list, click the name of the target ECS.
  4. On the displayed ECS details page, click the NICs tab.
  5. Ensure that Source/Destination Check is disabled.
  6. Ensure that an IP address is displayed for Virtual IP Address on the NIC details page. If no IP address is displayed for Virtual IP Address, click Manage Virtual IP Address and configure an IP address.

Incorrect ECS NIC Configuration

This following uses Linux and Windows ECSs as examples to describe how to check whether an ECS NIC has been correctly configured.

For a Linux ECS:
  1. Run the following command on the ECS and check whether NIC ethX:X exists:

    ifconfig

    Figure 2 Checking for NIC ethX:X

    The command output in the preceding figure contains the NIC of the ethX:X type. 192.168.1.137 is the virtual IP address of the ECS NIC.

    • If yes, the ECS NIC is correctly configured.
    • If no, perform the following operations:
  2. If the command output does not contain the NIC of the ethX:X type, run the following command to switch to the /etc/sysconfig/network-scripts directory:

    cd /etc/sysconfig/network-scripts

  3. Run the following command to create and then modify the ifcfg-eth0:1 file:

    vi ifcfg-eth0:1

    Add the following NIC information to the file:

    Figure 3 Adding NIC information
  4. Press Esc, enter :wq!, and save the file and exit.
  5. Restart the ECS and run the ifconfig command to check whether the virtual IP address has been configured for the ECS.

For a Windows ECS:

  1. In the Start menu, open the Windows command line window and run the following command to check whether the virtual IP address has been configured:

    ipconfig /all

    Figure 4 Checking whether the virtual IP address has been configured

    In the preceding command output, check whether the value of IPv4 Address is the virtual IP address 192.168.10.137 of the ECS NIC.

    • If yes, the virtual IP address has been configured for the ECS NIC.
    • If no, perform the following operations:
  2. Choose Control Panel > Network and Internet > Network Connections. Right-click the corresponding local connection and then click Properties.
  3. On the Network tab page, select Internet Protocol Version 4 (TCP/IPv4).
  4. Click Properties.
  5. Select Use the following IP address, and set IP address to the private IP address displayed in Figure 4. For example, 192.168.10.41.
    Figure 5 Configuring private IP address
  6. Click Advanced.
  7. On the IP Settings tab, click Add in the IP addresses area.

    Add the virtual IP address configured in Figure 4. For example, 192.168.10.137.

    Figure 6 Configuring virtual IP address

Incorrect Security Group or Network ACL Configuration

Check whether the ECS security groups and the network ACL rules associated with the subnet used by the ECS NIC block traffic.
  1. On the ECS details page, click the Security Groups tab and confirm that required security group rules have been configured for the virtual IP address. If the required security group rules have not been configured, click Change Security Group or Modify Security Group Rule to change the security group or modify the security group rules.
  2. Click Service List. Under Network, click Virtual Private Cloud. In the navigation pane on the left of the network console, click Network ACLs and check whether the network ACL rules associated with the subnet used by the ECS NIC block access to the virtual IP address.

Submitting a Service Ticket

If the problem persists, submit a service ticket.

Did you find this page helpful?

Submit successfully!

Thank you for your feedback. Your feedback helps make our documentation better.

Failed to submit the feedback. Please try again later.

Which of the following issues have you encountered?







Please complete at least one feedback item.

Content most length 200 character

Content is empty.

OK Cancel