Just noticed that VDSM creates these 2 files ,which should do the routing

[root@node01 network-scripts]# cat rule-vmtraffic
# Generated by VDSM version 4.19.10.1-1.el7.centos
from 192.168.192.0/24 table 3232284815
from all to 192.168.192.0/24 dev vmtraffic table 3232284815
[root@node01 network-scripts]# cat route-vmtraffic
# Generated by VDSM version 4.19.10.1-1.el7.centos
0.0.0.0/0 via 192.168.192.2 dev vmtraffic table 3232284815
192.168.192.0/24 via 192.168.192.143 dev vmtraffic table 3232284815
[root@node01 network-scripts]#

But for some reason these are not working and i am not able to ping the internet

On Thu, Apr 27, 2017 at 4:31 PM, martin chamambo <chamambom@gmail.com> wrote:

Here is my scenario

I have engine and 2 nodes running on VMware workstation with 5 interfaces each with these responsibilities

vmtraffic - 192.168.192.X
display - 192.168.193.X
storage - 192.168.194.X
migration- 192.168.195.X
ovirtmanagement - 192.168.196.X

Logical networks have been set up as above and all the networks are reachable....the only network with a gateway is the vmtraffic

192.168.192.143 with gateway 192.168.192.2

when i go to the nodes via the terminal , it doesnt set the gateway and theirfore that node when you do ip route ,i get this

[root@node01 ~]# ip route
192.168.192.0/24 dev vmtraffic proto kernel scope link src 192.168.192.143
192.168.193.0/24 dev ens37 proto kernel scope link src 192.168.193.143
192.168.194.0/24 dev ens34 proto kernel scope link src 192.168.194.143
192.168.195.0/24 dev ens35 proto kernel scope link src 192.168.195.143
192.168.196.0/24 dev ens36 proto kernel scope link src 192.168.196.143
[root@node01 ~]#

I know the solution is to insert a static route but isnt the interface with a gateway supposed to be default gateway for any traffic ?

and if i put the routes manually ,wont VDSM overwite it ,say if i upgrade.