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, but it has been over 2 months. I will send the traceroute in a couple of minutes.
Running Red Hat Enterprise 7.4
oVirt Management version – 4.1.9.1-0.1.el7
-bash-4.2# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eno3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master ovirtmgmt state UP qlen 1000
link/ether 4c:52:62:09:ea:14 brd ff:ff:ff:ff:ff:ff
3: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
link/ether 90:1b:0e:e9:15:8d brd ff:ff:ff:ff:ff:ff
inet 172.26.5.31/16 brd 172.26.255.255 scope global eno1
valid_lft forever preferred_lft forever
inet6 fe80::921b:eff:fee9:158d/64 scope link
valid_lft forever preferred_lft forever
4: eno4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
link/ether 4c:52:62:09:ea:15 brd ff:ff:ff:ff:ff:ff
inet 172.17.53.15/16 brd 172.17.255.255 scope global eno4
valid_lft forever preferred_lft forever
inet6 fe80::4e52:62ff:fe09:ea15/64 scope link
valid_lft forever preferred_lft forever
5: eno2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
link/ether 90:1b:0e:e9:15:8e brd ff:ff:ff:ff:ff:ff
21: ovirtmgmt: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP qlen 1000
link/ether 4c:52:62:09:ea:14 brd ff:ff:ff:ff:ff:ff
inet 172.21.5.31/16 brd 172.21.255.255 scope global ovirtmgmt
valid_lft forever preferred_lft forever
inet6 fe80::4e52:62ff:fe09:ea14/64 scope link
valid_lft forever preferred_lft forever
22: ;vdsmdummy;: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
link/ether 32:1d:65:0e:90:65 brd ff:ff:ff:ff:ff:ff
ip route
default via 172.21.0.250 dev ovirtmgmt
169.254.0.0/16 dev eno4 scope link metric 1004
169.254.0.0/16 dev ovirtmgmt scope link metric 1021
172.17.0.0/16 dev eno4 proto kernel scope link src 172.17.53.15
172.21.0.0/16 dev ovirtmgmt proto kernel scope link src 172.21.5.31
172.26.0.0/16 dev eno1 proto kernel scope link src 172.26.5.31
|
|
Doug Maxfield
| Senior Operating Systems Analyst |
From: Lev Veyde <lveyde@redhat.com>
Sent: Tuesday, February 12, 2019 11:07 AM
To: Doug Maxfield <Doug.L.Maxfield@EMCIns.com>
Cc: users <users@ovirt.org>
Subject: Re: [ovirt-users] Creating a static route
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 have added the static route?
Thanks in advance,
On Tue, Feb 12, 2019 at 6:58 PM Doug Maxfield <Doug.L.Maxfield@emcins.com> wrote:
Lev,
One other question, since there are multiple enabled interfaces (ovirtmgmt and eno1), do I need to specify an interface for the route add.
Doug Maxfield | Senior Operating Systems Analyst
EMC Insurance Companies
717 Mulberry St | Des Moines, IA 50265
Tel: 515.345.4507 | Fax: 866.331.1522
Doug.L.Maxfield@EMCIns.com | www.emcins.com
From: Lev Veyde <lveyde@redhat.com>
Sent: Tuesday, February 12, 2019 10:50 AM
To: Doug Maxfield <Doug.L.Maxfield@EMCIns.com>
Cc: users <users@ovirt.org>
Subject: Re: [ovirt-users] Creating a static route
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) you see, the version of your OS and oVirt, output of "ip a" and "ip route" on your host(s), so that it will be easier to help you.
Thanks in advance,
On Tue, Feb 12, 2019 at 6:43 PM Doug Maxfield <Doug.L.Maxfield@emcins.com> wrote:
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 ovirtmgmt interface and set the same static route, the required data is routed correctly over that static route.
Doug Maxfield | Senior Operating Systems Analyst
EMC Insurance Companies
717 Mulberry St | Des Moines, IA 50265
Tel: 515.345.4507 | Fax: 866.331.1522
Doug.L.Maxfield@EMCIns.com | www.emcins.com
From: Lev Veyde <lveyde@redhat.com>
Sent: Tuesday, February 12, 2019 10:34 AM
To: Doug Maxfield <Doug.L.Maxfield@EMCIns.com>
Cc: users <users@ovirt.org>
Subject: Re: [ovirt-users] Creating a static route
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 <doug.l.maxfield@emcins.com> 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 need to setup a static route for specific data between 2 remote sites. The ovirtmgmt is configured with the correct IP and gateway for the server. We need to route data over a different gateway so that we don't "max out" the default network connection between the 2 sites. Example below
Ovirtmgmt IP - 172.21.5.31
Gateway IP - 172.21.0.250
We need any traffic with a destination of 172.22.20.31(Remote site) to route over this gateway, 172.21.12.61
There are multiple servers in this configuration. Servers that are not using the ovirtmgmt interface for their default, we are able to route the data. The only problem is with attempting to setup a different static route on the ovirtmgmt interfaces.
Thanks in advance for any help!!!
Doug
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/WGXSLHAP3X5OT7DOXX3PMRLIMZBKTHR7/
--
NOTICE: This message (including any attachments) is intended for a specific individual and may contain information that is either confidential or legally protected. If you believe that it has been sent to you in error, please reply to the sender that you have received the message in error, then delete it. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Thank you. EMC071856
--
--