OpenVZ Forum


Home » General » Support » arpsend: x.x.x.x is detected on another computer : b0:83:fe:de:a8:0c (IP detected on another computer)
arpsend: x.x.x.x is detected on another computer : b0:83:fe:de:a8:0c [message #51986] Wed, 15 April 2015 06:49 Go to next message
kuldeepbti is currently offline  kuldeepbti
Messages: 4
Registered: April 2015
Junior Member
From: 61.1.165*
I have issue in openvz container whenever create new container it stay still rechable in network till its not rebooted whenever i reboot the vz container i lost the network connectivity with it.

When i try to start the container from shell i always get below message and i lost the network connectivity with it.
I found some other issue like if i assign a new IP to container which never used then that IP also reachable but till the container not rebooted as many IP i can use same issue happened with all of them.

Please suggest me why this happens-

vzctl restart 102
Restarting container
Stopping container ...
Container was stopped
Container is unmounted
Starting container...
Container is mounted
Adding IP address(es): x.x.x.x
arpsend: x.x.x.x is detected on another computer : b0:83:fe:de:a8:0c
vps-net_add WARNING: arpsend -c 1 -w 1 -D -e x.x.x.x eth2 FAILED
Setting CPU limit: 400
Setting CPU units: 1000
Setting CPUs: 4
Container start in progress...


Re: arpsend: x.x.x.x is detected on another computer : b0:83:fe:de:a8:0c [message #51987 is a reply to message #51986] Wed, 15 April 2015 17:52 Go to previous messageGo to next message
Paparaciz
Messages: 302
Registered: August 2009
Senior Member
From: *static.zebra.lt
have you checked this?

http://forum.openvz.org/index.php?t=msg&th=12869

[Updated on: Wed, 15 April 2015 17:52]

Report message to a moderator

Re: arpsend: x.x.x.x is detected on another computer : b0:83:fe:de:a8:0c [message #51988 is a reply to message #51986] Wed, 15 April 2015 18:18 Go to previous message
kuldeepbti is currently offline  kuldeepbti
Messages: 4
Registered: April 2015
Junior Member
From: 117.224.186*
I have seen this what i have different issue.
I am using solusm master with openvz virtuallization whenever i create a new machine whenever it will from solsuvm admin panel or from shell with New IP which never used any time earlier that VPS still reachable in network till VPS not rebooted after the reboot VPS never comes in network.
Previous Topic: VM Wont start - Mountall event Failed
Next Topic: How to resume migration of big ploop container?
Goto Forum:
  


Current Time: Thu Dec 05 15:33:25 GMT 2019