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.200.14)  6.391 ms  6.422 ms 192.168.200.30 
(192.168.200.30)  0.698 ms
3  ames-sw-wanrtr.emcins.com (192.168.200.97)  2.910 ms  2.980 ms  3.057 ms
4  192.168.100.26 (192.168.100.26)  4.358 ms  4.479 ms  4.642 ms
5  192.168.100.98 (192.168.100.98)  1.834 ms 192.168.100.102 (192.168.100.102)  
1.729 ms 192.168.100.98 (192.168.100.98)  2.048 ms
6  192.168.100.29 (192.168.100.29)  1.667 ms  1.530 ms 192.168.100.13 
(192.168.100.13)  1.535 ms
7  pdputopcomm01.emcins.com (172.22.20.31)  1.349 ms  1.301 ms  1.244 ms
-bash-4.2#
-bash-4.2#
-bash-4.2#
-bash-4.2# ip route add 172.22.20.31 via 172.21.12.61
-bash-4.2#
-bash-4.2#
-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)  1.453 ms  1.442 ms  1.441 ms
2  192.168.200.30 (192.168.200.30)  0.680 ms  0.958 ms 192.168.200.14 
(192.168.200.14)  0.809 ms
3  192.168.200.101 (192.168.200.101)  3.025 ms  3.128 ms  3.209 ms
4  192.168.100.26 (192.168.100.26)  3.976 ms  4.170 ms  4.298 ms
5  192.168.100.98 (192.168.100.98)  2.052 ms 192.168.100.102 (192.168.100.102)  
1.767 ms 192.168.100.98 (192.168.100.98)  2.064 ms
6  192.168.100.29 (192.168.100.29)  1.721 ms 192.168.100.13 (192.168.100.13)  
1.540 ms 192.168.100.33 (192.168.100.33)  1.637 ms
7  pdputopcomm01.emcins.com (172.22.20.31)  1.291 ms  1.282 ms  1.506 ms

[Count On EMC]<http://www.emcins.com/>

Doug Maxfield | Senior Operating Systems Analyst
EMC Insurance Companies
717 Mulberry St | Des Moines, IA 50265
Tel: 515.345.4507 | Fax: 866.331.1522
[email protected]<mailto:[email protected]> | 
www.emcins.com<http://www.emcins.com/>



From: Lev Veyde <[email protected]>
Sent: Tuesday, February 12, 2019 11:07 AM
To: Doug Maxfield <[email protected]>
Cc: users <[email protected]>
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 
<[email protected]<mailto:[email protected]>> 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.

[Count On EMC]<http://www.emcins.com/>

Doug Maxfield | Senior Operating Systems Analyst
EMC Insurance Companies
717 Mulberry St | Des Moines, IA 50265
Tel: 515.345.4507 | Fax: 866.331.1522
[email protected]<mailto:[email protected]> | 
www.emcins.com<http://www.emcins.com/>



From: Lev Veyde <[email protected]<mailto:[email protected]>>
Sent: Tuesday, February 12, 2019 10:50 AM
To: Doug Maxfield 
<[email protected]<mailto:[email protected]>>
Cc: users <[email protected]<mailto:[email protected]>>
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 
<[email protected]<mailto:[email protected]>> 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.

[Count On EMC]<http://www.emcins.com/>

Doug Maxfield | Senior Operating Systems Analyst
EMC Insurance Companies
717 Mulberry St | Des Moines, IA 50265
Tel: 515.345.4507 | Fax: 866.331.1522
[email protected]<mailto:[email protected]> | 
www.emcins.com<http://www.emcins.com/>



From: Lev Veyde <[email protected]<mailto:[email protected]>>
Sent: Tuesday, February 12, 2019 10:34 AM
To: Doug Maxfield 
<[email protected]<mailto:[email protected]>>
Cc: users <[email protected]<mailto:[email protected]>>
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 
<[email protected]<mailto:[email protected]>> 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 -- [email protected]<mailto:[email protected]>
To unsubscribe send an email to 
[email protected]<mailto:[email protected]>
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/[email protected]/message/WGXSLHAP3X5OT7DOXX3PMRLIMZBKTHR7/


--


Lev Veyde

Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

[email protected]<mailto:[email protected]> | 
[email protected]<mailto:[email protected]>
[https://www.redhat.com/profiles/rh/themes/redhatdotcom/img/logo-red-hat-black.png]<https://red.ht/sig>
TRIED. TESTED. TRUSTED.<https://redhat.com/trusted>

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


--


Lev Veyde

Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

[email protected]<mailto:[email protected]> | 
[email protected]<mailto:[email protected]>
[https://www.redhat.com/profiles/rh/themes/redhatdotcom/img/logo-red-hat-black.png]<https://red.ht/sig>
TRIED. TESTED. TRUSTED.<https://redhat.com/trusted>


--


Lev Veyde

Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

[email protected]<mailto:[email protected]> | 
[email protected]<mailto:[email protected]>
[https://www.redhat.com/profiles/rh/themes/redhatdotcom/img/logo-red-hat-black.png]<https://red.ht/sig>
TRIED. TESTED. TRUSTED.<https://redhat.com/trusted>
_______________________________________________
Users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]/message/UB57SBDGIZIB3BWHP6D2HLEYJVDYX6SU/

Reply via email to