Research the given solution for different subnet IPs allocated to hardware node

[Gary]

Given the following scenario:

(IPs and domain names changed to protect the innocent.)

[root@cco2 ~]# vzlist -a
      CTID      NPROC STATUS  IP_ADDR         HOSTNAME
       172         81 running 88.34.183.228  elastix16.verizon.com
       222         87 running 88.34.183.229  sip.releagogo.com
       252         83 running 88.34.183.231  xioncap2.chkgroup.net
       312         59 running 88.34.183.233  a2billing17.verizon.com
       352         84 running 88.34.183.232  routes.verizon.com
       372         82 running 88.34.183.234  sip2.releagogo.com
       402         86 running 88.34.183.227  ems.verizon.com
       432         67 running 88.34.183.235  inbound.verizon.com
       442         83 running 88.34.183.236  bbe.verizon.com
       452         83 running 88.34.183.237  eucserv.verizon.com
       462         82 running 88.34.183.238  eucpre.verizon.com
       502         38 running 88.34.183.230  nas.verizon.com
       512         33 running 88.34.183.130  eucfs.verizon.com
[root@cco2 ~]# ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:26:B9:58:CF:A2
          inet addr:88.34.183.226  Bcast:88.34.183.239  Mask:255.255.255.240
          inet6 addr: fe80::226:b9ff:fe58:cfa2/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:5973668 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6504923 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1391700655 (1.2 GiB)  TX bytes:1523661366 (1.4 GiB)
          Interrupt:66 Memory:da000000-da012800

[root@cco2 ~]# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
88.34.183.130  0.0.0.0         255.255.255.255 UH    0      0        0 venet0
88.34.183.227  0.0.0.0         255.255.255.255 UH    0      0        0 venet0
88.34.183.228  0.0.0.0         255.255.255.255 UH    0      0        0 venet0
88.34.183.229  0.0.0.0         255.255.255.255 UH    0      0        0 venet0
88.34.183.230  0.0.0.0         255.255.255.255 UH    0      0        0 venet0
88.34.183.231  0.0.0.0         255.255.255.255 UH    0      0        0 venet0
88.34.183.232  0.0.0.0         255.255.255.255 UH    0      0        0 venet0
88.34.183.233  0.0.0.0         255.255.255.255 UH    0      0        0 venet0
88.34.183.234  0.0.0.0         255.255.255.255 UH    0      0        0 venet0
88.34.183.235  0.0.0.0         255.255.255.255 UH    0      0        0 venet0
88.34.183.236  0.0.0.0         255.255.255.255 UH    0      0        0 venet0
88.34.183.237  0.0.0.0         255.255.255.255 UH    0      0        0 venet0
88.34.183.238  0.0.0.0         255.255.255.255 UH    0      0        0 venet0
88.34.183.224  0.0.0.0         255.255.255.240 U     0      0        0 eth0
192.168.25.0    0.0.0.0         255.255.255.0   U     0      0        0 eth1
169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 eth1
0.0.0.0         88.34.183.225  0.0.0.0         UG    0      0        0 eth0

The solution was:

Edit /etc/vz/vz.conf and change:

NEIGHBOR_DEVS=detect

to

NEIGHBOR_DEVS=all

[Gary]

This is the comment for the setting, in the file mentioned above:

...
# Controls which interfaces to send ARP requests and modify APR tables on.
NEIGHBOUR_DEVS=all
...