This page discusses working with multiple network interfaces on the [[Hardware Node]] (HN), how this results in ARP Flux, and how to address this.
Not sure if people ==The Simple Case==In the simple case you have multiple network interfaces on the HN, all with IP addresses in the same subnet. Each of your containers also have IP addresses in the same subnet. You don't care which interfaces your containers use it. So, probably no action is required. Everything just works. because there Setup OpenVZ normally. The only downside is no driving factor now'''ARP flux'''. This describes the usually harmless condition where the network address (layer 3) drifts between multiple hardware addresses (layer 2). While this may cause some confusion to anyone trouble shooting, but if google starts indexing that metadataor generate alarms on network monitoring systems, weit doesn'll t interrupt network traffic. For an example of what this may look like, see more videos have metadata injected inthe example and tcpdump captures below. ,
==A More Complex Case==
This approach is also described in [[virtual Ethernet device]].
In the container configuration file, /etc/vz/conf/$CTID.conf, add the line <pre>CONFIG_CUSTOMIZED="yes"</pre> Now create Create the file /etc/vz/vznet.conf or /etc/vz/vznetcfg. Note that this will only work with a recent version of OpenVZ (vzctl-3.0.14) 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 may be required.
<pre>
