Article ID: 120266, created on Feb 21, 2014, last review on May 11, 2014

  • Applies to:
  • Virtuozzo
  • Virtuozzo containers for Linux
  • Virtuozzo hypervisor

Symptoms

When starting/restarting a container, aprsend for an IP address fails with "IP is detected on another computer"

    [root@vz ~]# vzctl restart 1406
    Restart the Container
    ...
    Adding IP addresses: 192.158.21.16
    arpsend: 192.158.21.16 is detected on another computer: XX:XX:XX:d6:84:66
    vz-net_add WARNING: arpsend -c 1 -w 1 -D  -e 192.158.21.16 eth0 FAILED
    ...
    Starting the Container ...

Another symptoms you may observe for such container:

  1. Parallels Power Panel is not accessible for this container or drops connection from time to time.
  2. Container is not pingable/cannot be accessed via SSH.

How to troubleshoot

  1. Check the arp entries for the container in question on the node where it resides:

    [root@vz ~]# arp -an | grep 192.158.21.16
    
    ? (192.158.21.16) at XX:XX:XX:d6:84:66 [ether] on eth0
    ? (192.158.21.16) at * PERM PUP on eth3
    ? (192.158.21.16) at * PERM PUP on eth2
    ? (192.158.21.16) at * PERM PUP on eth1
    ? (192.158.21.16) at * PERM PUP on eth0
    

    In the example above we see that there is an entry for MAC that does not belong to localhost:

    ? (192.158.21.16) at XX:XX:XX:d6:84:66 [ether] on eth0
    
  2. Do arping from another node in the network, most probably, you will see that reply comes from two different MACs, as on the example below:

    [root@vz2 ~]# arping 192.158.21.16 -I eth2
    ARPING 192.158.21.16 from 192.158.21.2 eth2
    Unicast reply from 192.158.21.16 [XX:XX:XX:D6:84:66]  1.078ms
    Unicast reply from 192.158.21.16 [YY:YY:YY:00:1C:26]  545.118ms
    

Resolution

Network conflicts should be resolved by network administrators.

Search Words

is detected on another computer

PPP not accessible

arpsend

vz-net_add WARNING

vz-net_add

arpsend failed

arping

network conflict

a26b38f94253cdfbf1028d72cf3a498b 2897d76d56d2010f4e3a28f864d69223 d02f9caf3e11b191a38179103495106f e8e50b42231236b82df27684e7ec0beb 0dd5b9380c7d4884d77587f3eb0fa8ef

Email subscription for changes to this article
Save as PDF