9
edits
Changes
no edit summary
==Overview==
This page discusses working with multiple network interfaces on the Hardware Node (HN), how this results in ARP Flux, and how to address this.
==The Simple Case==
Unfortunately this involves editing the OpenVZ scripts. The only case we really care about is vps-net_add, as the others execute <code>ip neigh del proxy</code>.
Manually editing the vzarp script is a quick fix, but not advised. Creating your own ''fork'' of OpenVZ is difficult to maintain and may have unintended side affects. Fortunately there is a feature which will allow custom scripts to run during VE startup. This approach is also described in http://wiki.openvz.org/Virtual_Ethernet_device. In the VE configuration file, /etc/vz/conf/$VEID.conf, add the line <pre>CONFIG_CUSTOMIZED="yes"</pre> Now create the file /etc/vz/vznet.conf or /etc/vz/vznetcfg. Note that this will only work with a recent version of OpenVZ as the change was introduced in December, 2006. The file name seems to have changed between the two listed here so some trial and error will be required. <pre>#!/bin/bashEXTERNAL_SCRIPT="/usr/lib/vzctl/scripts/vznet-custom"</pre> Finally create the file /usr/lib/vzctl/scripts/vznet-custom and add your custom commands. TODO: Discuss changes contents of script and provide examples. Still need to work on getting this to scriptswork.
==Testing Environment==
