| Re: ( openvz 2.6.18-53.1.4.el5.028stab053.4 + intel e1000 ) not sending arp notifies [message #28343 is a reply to message #28335] |
Fri, 14 March 2008 14:22   |
rickb
Messages: 368
Registered: October 2006
|
Senior Member |
|
|
Hi, thank you for the reply. I am happy to provide further information. The steps your provided are all correct. The arpsend command I use to bring the VEs back to life is:
/usr/sbin/arpsend -U -i <IP> -c 2 eth0
When I do this for a VE's IP, the VE can reach the network fine. Doing so does trigger the syslog message I included previously but that is not such a huge problem, just some information I added.
I never restart the network interface on the HN. My assumption is that the NIC is not dispatching arp packets to notify the switch and local machines of what IPs the hardware node is assigned often enough (or at all aside from the initial network script start) to keep the VEs online. It seems like the HN's IP is always online as I am always able to reach it, but ALL of the VE's IPs will become unreachable at the same time hours or a day later. I SSH into the HN and use the arpsend in a little for loop for all of the VE's IPs and everything is back to normal for a few hours.
What I did in the meantime was add a static arp in the switch to the HN's mac addrsss, but it is a very bad solution because the IPs may be moved in the future.
Does the NIC send the arp packets automatically every XX minutes? What would cause this problem on a high level?, without thinking about openvz.
Thanks for any ideas!
-------------
Common Terms I post with: http://wiki.openvz.org/Category:Definitions
UBC. Learn it, love it, live it: http://wiki.openvz.org/Proc/user_beancounters
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
