[ovirt-users] Re: Creating a static route

2019-02-20 Thread Greg Sheremeta
Thanks all. I agree with Lev, mostly because it's a better experience for our users. And we typically document workaround type things in the appendices. I could argue vdsm hooks are all workarounds for something and we document those pretty extensively :) Maybe this section would make sense? https

[ovirt-users] Re: Creating a static route

2019-02-20 Thread Edward Haas
On Wed, Feb 20, 2019 at 2:14 PM Lev Veyde wrote: > Hi Edward, > > Thanks for your feedback on the issue. > > I still think that we do need to to add a note to the documentation, so > that customers/integrators who want to add custom static routes will be > aware of the issue. > Unfortunately, th

[ovirt-users] Re: Creating a static route

2019-02-20 Thread Lev Veyde
Hi Edward, Thanks for your feedback on the issue. I still think that we do need to to add a note to the documentation, so that customers/integrators who want to add custom static routes will be aware of the issue. As previously discussed we should note of course, that this feature is currently no

[ovirt-users] Re: Creating a static route

2019-02-20 Thread Edward Haas
As mentioned in this thread oVirt currently does not support customized routes. It supports only a host level default route and per network gateways (default route per network). If someone understands well the Linux network details, workarounds may be applied to overcome oVirt limitations. With th

[ovirt-users] Re: Creating a static route

2019-02-18 Thread Lev Veyde
Hi Doug, Thanks for the update, I'm glad that we could help and everything worked out just fine! I also opened a BZ, asking to add a note in the documentation regarding this issue. Thanks in advance, On Mon, Feb 18, 2019 at 7:15 PM Doug Maxfield wrote: > Lev, > > Just wanted to update you on

[ovirt-users] Re: Creating a static route

2019-02-14 Thread Lev Veyde
Hi Doug, Just one more thing that I forgot to mention, even though it may be obvious - you can use subnets in both rules and routes. So if all the IPs you want to route sit in the same subnet then you can contain them with a single command e.g. "to 172.22.20.0/24 priority 32764" Thanks in advance

[ovirt-users] Re: Creating a static route

2019-02-14 Thread Lev Veyde
Hi Doug, Sure, np. >> 1. - yes it is the priority setting of the specific rule. Basically you put in the file the post "ip rule add" part of the command e.g. for "ip rule add to 172.22.20.31 priority 32764" you need to put a line of "to 172.22.20.31 priority 32764" >> 2. - yes, the same priority

[ovirt-users] Re: Creating a static route

2019-02-14 Thread Lev Veyde
Hi Doug, Sorry that it took a bit of time to get back to you. Managed to catch today somebody from the oVirt/RHV network team to discuss the issue. It seems that we don't currently support custom static routes on the hosts, so the workaround that I suggested is the way to do it. Thanks in advance

[ovirt-users] Re: Creating a static route

2019-02-12 Thread Doug Maxfield
Will do. Thanks again for all your help!! Looking forward to a confirmation of the fix or a different solution. Either way, I know I have a working fix. [Count On EMC] Doug Maxfield | Senior Operating Systems Analyst EMC Insurance Companies 717 Mulberry St | Des Moines

[ovirt-users] Re: Creating a static route

2019-02-12 Thread Lev Veyde
Hi Doug, Just a small note - the commands in the rc.local should be placed *before* the very last line (the touch ... command). Thanks in advance, On Tue, Feb 12, 2019 at 10:56 PM Lev Veyde wrote: > Hi Doug, > > Thanks, you're welcome! > > It's generally possible to add persistent rules by eit

[ovirt-users] Re: Creating a static route

2019-02-12 Thread Lev Veyde
Hi Doug, Thanks, you're welcome! It's generally possible to add persistent rules by either using the legacy /etc/rc.d/rc.local boot script (chmod +x /etc/rc.d/rc.local and put the relevant commands at the end of the file, that way you can actually run any commands) or by using the /etc/sysconfig/

[ovirt-users] Re: Creating a static route

2019-02-12 Thread Doug Maxfield
Lev, You have no idea how helpful you have been!! I’ve been having this issue for over 2 months and starting to cause major problems. Please let me know if you find a better solution. I’m going to wait to hear back from you before implementing. If we go with this workaround, is there a wa

[ovirt-users] Re: Creating a static route

2019-02-12 Thread Lev Veyde
Hi Doug, Yes, it looks like it did. I'll try to catch somebody from my local oVirt/RHV networking team to take a look at this issue, maybe there is a better solution for that issue than my workaround. But meanwhile you can use this workaround (ip route add + ip rule add), just please be aware th

[ovirt-users] Re: Creating a static route

2019-02-12 Thread Doug Maxfield
Lev, Here’s the results. It appears to fix the issue!! From non-working system: -bash-4.2# ip rule add to 172.22.20.31 priority 32764 -bash-4.2# traceroute 172.22.20.31 traceroute to 172.22.20.31 (172.22.20.31), 30 hops max, 60 byte packets 1 CenteraAmesAN1.emcins.com (172.21.12.61) 0.487 ms

[ovirt-users] Re: Creating a static route

2019-02-12 Thread Lev Veyde
Hi Doug, OK, I think that I have a guess of what may have happened here... Can you please run the following command on the (non-working) host: ip rule add to 172.22.20.31 priority 32764 This needs to be run in addition to the ip route add ... command. And then please run the traceroute command

[ovirt-users] Re: Creating a static route

2019-02-12 Thread Doug Maxfield
Lev, Here you go. From non-working system -bash-4.2# ip rule 0: from all lookup local 32764: from all to 172.21.0.0/16 iif ovirtmgmt lookup 2887058719 32765: from 172.21.0.0/16 lookup 2887058719 32766: from all lookup main 32767: from all lookup default From working system [root@paput

[ovirt-users] Re: Creating a static route

2019-02-12 Thread Lev Veyde
Hi Doug, That shouldn't really matter, since ovirtmgmt is just a bridged interface, and unless I'm missing something it shouldn't really affect routing. Can you please also provide the output of "ip rule" from both working and non-working hosts ? Thanks in advance, On Tue, Feb 12, 2019 at 8:01

[ovirt-users] Re: Creating a static route

2019-02-12 Thread Doug Maxfield
Lev, Here’s the ip route from the server that worked and didn’t work IP Route from server that worked [root@paputopcomm04 ~]# ip route default via 172.21.0.250 dev eno3 169.254.0.0/16 dev eno3 scope link metric 1002 169.254.0.0/16 dev eno4 scope link metric 1005 172.17.0.0/16 dev eno4 proto kerne

[ovirt-users] Re: Creating a static route

2019-02-12 Thread Lev Veyde
Hi Doug, This is indeed quite weird... It looks like the OS for some reason disregards the static route that you have added. BTW, have you verified that it's indeed was added by running "ip route" following the "ip route add ..." command ? Maybe somebody from the network team has an idea of what

[ovirt-users] Re: Creating a static route

2019-02-12 Thread Doug Maxfield
Lev, I’m showing you the same outputs (ip a, ip route, traceroute, ip route add, and traceroute) from another server in this group that doesn’t use the ovirtmgmt for it’s default interface. [root@paputopcomm04 ~]# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN qlen 1 link/loopback 00:00:

[ovirt-users] Re: Creating a static route

2019-02-12 Thread Doug Maxfield
Lev, Output of traceroute. Showed routing before and after putting in the static route. -bash-4.2# traceroute 172.22.20.31 traceroute to 172.22.20.31 (172.22.20.31), 30 hops max, 60 byte packets 1 ames-acc1-agg-1.emcins.com (172.21.0.246) 9.854 ms 9.848 ms 9.853 ms 2 192.168.200.14 (192.168

[ovirt-users] Re: Creating a static route

2019-02-12 Thread Doug Maxfield
Lev, Here are the outputs from the ip a and ip route commands. I have not enabled the route yet. Eno1 was added after the ovirtmgmt was configured on the server. Sorry for not having a lot of the information you need. This is new to us and were hoping the vendor would figure the issue out, b

[ovirt-users] Re: Creating a static route

2019-02-12 Thread Lev Veyde
Hi Doug, In most cases it should not be required, especially as my guess (again it would be easier if you could post the output of the "ip a" and "ip route") is that the eno1 is part of the ovirtmgmt bridge. What is the output of the "traceroute 172.22.20.31" that you get on the host after you ha

[ovirt-users] Re: Creating a static route

2019-02-12 Thread Doug Maxfield
Lev, One other question, since there are multiple enabled interfaces (ovirtmgmt and eno1), do I need to specify an interface for the route add. [Count On EMC] Doug Maxfield | Senior Operating Systems Analyst EMC Insurance Companies 717 Mulberry St | Des Moines, IA 50265 T

[ovirt-users] Re: Creating a static route

2019-02-12 Thread Doug Maxfield
Lev, I guess “refused” is the incorrect word. If we set the static route as below, our network team can see that the traffic is not going over that interface and is going over the default interface. That’s why I used the term “refused”. I can certainly attempt to try that and let you know the

[ovirt-users] Re: Creating a static route

2019-02-12 Thread Lev Veyde
Hi Doug, What do you mean by "static route is refused"? What is the error message(s) you see? Can you please try to add the route with the following command: ip route add 172.22.20.31 via 172.21.12.61 If that doesn't work, then please provide more details, i.e. what is the exact error message(s

[ovirt-users] Re: Creating a static route

2019-02-12 Thread Doug Maxfield
Lev, Thanks for your response. If I attempt to manually add the route using route add: route add -net 172.22.20.31 netmask 255.255.255.255 gw 172.21.12.61 dev ovirtmgmt This static route is refused and all traffic is routed over the default gateway. But if I use a server that doesn’t use the o

[ovirt-users] Re: Creating a static route

2019-02-12 Thread Lev Veyde
Hi Doug, What is the exact problem you are having while attempting to add a static route on the hosts? Thanks in advance, On Tue, Feb 12, 2019 at 5:23 PM wrote: > Good Morning, > New to oVirt. We are using this with a backup solution from Commvault. > The issue that we are having is that we n