[ovirt-users] Re: Creating a static route

[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://www.ovirt.org/documentation/admin-guide/appe-Custom_Network_Properties.html

Sandro, your opinion please?

Greg

On Wed, Feb 20, 2019 at 7:21 AM 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.
> As previously discussed we should note of course, that this feature is
> currently not officially supported, and adding the routes manually is a
> workaround.
>
> Thanks in advance,
>
> On Wed, Feb 20, 2019 at 1:41 PM Edward Haas  wrote:
>
>> 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 that said, as oVirt manages the host network details, the community
>> and future development cannot take into account such workarounds.
>>
>> To solve this problem correctly, oVirt needs to support customize routes.
>> From my perspective, this workaround should not be formally documented.
>>
>> Thanks,
>> Edy.
>>
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/ENLA36PL2CPVDIJNZTOGLWYTZCPUGJ6Z/

[ovirt-users] Re: Creating a static route

[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, the users can't do that today in a safe manner. I do not
think we should document things that are breakable or that is tailored to
work for a specific user.
If we document it, it means we support it.

If someone is willing to write a blog on how to add a custom route, as a
non formal documentation, it will be great.

As previously discussed we should note of course, that this feature is
> currently not officially supported, and adding the routes manually is a
> workaround.
>
> Thanks in advance,
>
> On Wed, Feb 20, 2019 at 1:41 PM Edward Haas  wrote:
>
>> 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 that said, as oVirt manages the host network details, the community
>> and future development cannot take into account such workarounds.
>>
>> To solve this problem correctly, oVirt needs to support customize routes.
>> From my perspective, this workaround should not be formally documented.
>>
>> Thanks,
>> Edy.
>>
>> On Tue, Feb 19, 2019 at 2:22 AM Lev Veyde  wrote:
>>
>>> 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 <
>>> doug.l.maxfi...@emcins.com> wrote:
>>>
>>>> Lev,
>>>>
>>>> Just wanted to update you on the progress.  We created the persistent
>>>> static routes and rules and the data is routing correctly over the required
>>>> gateway.
>>>>
>>>>
>>>>
>>>> Thank you for all of your help!!!
>>>>
>>>>
>>>>
>>>> [image: 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
>>>> doug.l.maxfi...@emcins.com | www.emcins.com
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> *From:* Lev Veyde 
>>>> *Sent:* Thursday, February 14, 2019 9:14 AM
>>>> *To:* Doug Maxfield 
>>>> *Cc:* users 
>>>> *Subject:* Re: [ovirt-users] Creating a static route
>>>>
>>>>
>>>>
>>>> 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,
>>>>
>>>>
>>>>
>>>> On Thu, Feb 14, 2019 at 4:59 PM Lev Veyde  wrote:
>>>>
>>>> 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 can be used for all of them. E.g. if you
>>>> want to route 172.22.20.31, 172.22.34.56 and 172.22.67.89 you will need to
>>>> add:
>>>>
>>>> to 172.22.20.31 priority 32764
>>>> to 172.22.34.56 priority 32764
>>>> to 172.22.67.89 priority 32764
>>>>
>>>> into the rule- file e.g. rule-ovirtmgmt or rule-eno3.
>>>>
>>>>
>>>>
>>>> Please note that you will also need to add the static route for ea

[ovirt-users] Re: Creating a static route

[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 not officially supported, and adding the routes manually is a
workaround.

Thanks in advance,

On Wed, Feb 20, 2019 at 1:41 PM Edward Haas  wrote:

> 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 that said, as oVirt manages the host network details, the community
> and future development cannot take into account such workarounds.
>
> To solve this problem correctly, oVirt needs to support customize routes.
> From my perspective, this workaround should not be formally documented.
>
> Thanks,
> Edy.
>
> On Tue, Feb 19, 2019 at 2:22 AM Lev Veyde  wrote:
>
>> 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 the progress.  We created the persistent
>>> static routes and rules and the data is routing correctly over the required
>>> gateway.
>>>
>>>
>>>
>>> Thank you for all of your help!!!
>>>
>>>
>>>
>>> [image: 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
>>> doug.l.maxfi...@emcins.com | www.emcins.com
>>>
>>>
>>>
>>>
>>>
>>> *From:* Lev Veyde 
>>> *Sent:* Thursday, February 14, 2019 9:14 AM
>>> *To:* Doug Maxfield 
>>> *Cc:* users 
>>> *Subject:* Re: [ovirt-users] Creating a static route
>>>
>>>
>>>
>>> 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,
>>>
>>>
>>>
>>> On Thu, Feb 14, 2019 at 4:59 PM Lev Veyde  wrote:
>>>
>>> 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 can be used for all of them. E.g. if you
>>> want to route 172.22.20.31, 172.22.34.56 and 172.22.67.89 you will need to
>>> add:
>>>
>>> to 172.22.20.31 priority 32764
>>> to 172.22.34.56 priority 32764
>>> to 172.22.67.89 priority 32764
>>>
>>> into the rule- file e.g. rule-ovirtmgmt or rule-eno3.
>>>
>>>
>>>
>>> Please note that you will also need to add the static route for each one
>>> of these as well w/ "ip route add ... " command e.g. "ip route add
>>> 172.22.20.31 via 172.21.12.61".
>>>
>>> You can also use the route- putting just the route info
>>> part, similar to the "ip rule" e.g. for equivalent of "ip route add
>>> 172.22.20.31 via 172.21.12.61" you need put in the file a line with the
>>> content "172.22.20.31 via 172.21.12.61".
>>>
>>> For routes it's important to use specifically the route-ovirtmgmt file
>>> since the script automatically adds the device to the route command i.e.
>>> you can put the following lines into your route-ovirtmgmt file:
>>>
>>> 172.22.20.31 via 172.21.12.61
>>> 172.22.34.56 via 172.21.12.61
>>> 172.22.67.89 via 172.21.12.68
>>>

[ovirt-users] Re: Creating a static route

[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 that said, as oVirt manages the host network details, the community
and future development cannot take into account such workarounds.

To solve this problem correctly, oVirt needs to support customize routes.
>From my perspective, this workaround should not be formally documented.

Thanks,
Edy.

On Tue, Feb 19, 2019 at 2:22 AM Lev Veyde  wrote:

> 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 the progress.  We created the persistent
>> static routes and rules and the data is routing correctly over the required
>> gateway.
>>
>>
>>
>> Thank you for all of your help!!!
>>
>>
>>
>> [image: 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
>> doug.l.maxfi...@emcins.com | www.emcins.com
>>
>>
>>
>>
>>
>> *From:* Lev Veyde 
>> *Sent:* Thursday, February 14, 2019 9:14 AM
>> *To:* Doug Maxfield 
>> *Cc:* users 
>> *Subject:* Re: [ovirt-users] Creating a static route
>>
>>
>>
>> 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,
>>
>>
>>
>> On Thu, Feb 14, 2019 at 4:59 PM Lev Veyde  wrote:
>>
>> 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 can be used for all of them. E.g. if you
>> want to route 172.22.20.31, 172.22.34.56 and 172.22.67.89 you will need to
>> add:
>>
>> to 172.22.20.31 priority 32764
>> to 172.22.34.56 priority 32764
>> to 172.22.67.89 priority 32764
>>
>> into the rule- file e.g. rule-ovirtmgmt or rule-eno3.
>>
>>
>>
>> Please note that you will also need to add the static route for each one
>> of these as well w/ "ip route add ... " command e.g. "ip route add
>> 172.22.20.31 via 172.21.12.61".
>>
>> You can also use the route- putting just the route info
>> part, similar to the "ip rule" e.g. for equivalent of "ip route add
>> 172.22.20.31 via 172.21.12.61" you need put in the file a line with the
>> content "172.22.20.31 via 172.21.12.61".
>>
>> For routes it's important to use specifically the route-ovirtmgmt file
>> since the script automatically adds the device to the route command i.e.
>> you can put the following lines into your route-ovirtmgmt file:
>>
>> 172.22.20.31 via 172.21.12.61
>> 172.22.34.56 via 172.21.12.61
>> 172.22.67.89 via 172.21.12.68
>>
>> (In case the first 2 of the mentioned IPs should be routed through the
>> 172.21.12.61 gateway, and the last one should be routed through the
>> 172.21.12.68 gateway).
>>
>>
>>
>> For the reference you can take a look at the
>> /etc/sysconfig/network-scripts/ifup-routes script.
>> It does the actual processing of both "route" and "rule" files for all
>> network interfaces on a system.
>>
>>
>>
>> Please feel free to contact if you have further questions.
>>
>>
>>
>> Thanks in advance,
>>
>>
>>
>> On Thu, Feb 14, 2019 at 3:39 PM Doug Maxfield 
>> wrote:
>>
>> Lev,
>>
>> Thanks for the response.  I was just getting ready to contact you about
>> this.  I do have 2 follow-up questions, if you don’t mind.
>>
>>
>

[ovirt-users] Re: Creating a static route

[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 the progress.  We created the persistent
> static routes and rules and the data is routing correctly over the required
> gateway.
>
>
>
> Thank you for all of your help!!!
>
>
>
> [image: 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
> doug.l.maxfi...@emcins.com | www.emcins.com
>
>
>
>
>
> *From:* Lev Veyde 
> *Sent:* Thursday, February 14, 2019 9:14 AM
> *To:* Doug Maxfield 
> *Cc:* users 
> *Subject:* Re: [ovirt-users] Creating a static route
>
>
>
> 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,
>
>
>
> On Thu, Feb 14, 2019 at 4:59 PM Lev Veyde  wrote:
>
> 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 can be used for all of them. E.g. if you
> want to route 172.22.20.31, 172.22.34.56 and 172.22.67.89 you will need to
> add:
>
> to 172.22.20.31 priority 32764
> to 172.22.34.56 priority 32764
> to 172.22.67.89 priority 32764
>
> into the rule- file e.g. rule-ovirtmgmt or rule-eno3.
>
>
>
> Please note that you will also need to add the static route for each one
> of these as well w/ "ip route add ... " command e.g. "ip route add
> 172.22.20.31 via 172.21.12.61".
>
> You can also use the route- putting just the route info
> part, similar to the "ip rule" e.g. for equivalent of "ip route add
> 172.22.20.31 via 172.21.12.61" you need put in the file a line with the
> content "172.22.20.31 via 172.21.12.61".
>
> For routes it's important to use specifically the route-ovirtmgmt file
> since the script automatically adds the device to the route command i.e.
> you can put the following lines into your route-ovirtmgmt file:
>
> 172.22.20.31 via 172.21.12.61
> 172.22.34.56 via 172.21.12.61
> 172.22.67.89 via 172.21.12.68
>
> (In case the first 2 of the mentioned IPs should be routed through the
> 172.21.12.61 gateway, and the last one should be routed through the
> 172.21.12.68 gateway).
>
>
>
> For the reference you can take a look at the
> /etc/sysconfig/network-scripts/ifup-routes script.
> It does the actual processing of both "route" and "rule" files for all
> network interfaces on a system.
>
>
>
> Please feel free to contact if you have further questions.
>
>
>
> Thanks in advance,
>
>
>
> On Thu, Feb 14, 2019 at 3:39 PM Doug Maxfield 
> wrote:
>
> Lev,
>
> Thanks for the response.  I was just getting ready to contact you about
> this.  I do have 2 follow-up questions, if you don’t mind.
>
>
>
>1. When we were talking about creating the route that would be enabled
>again after a reboot, you said to modify “the
>/etc/sysconfig/network-scripts/rule- e.g. rule-ovirtmgmt or
>rule-eno3 (just put in the file "to 172.22.20.31 priority 32764”.  Is
>priority 32764 for the ip rule command?
>2. If I have multiple IPs that I would need to create a static route,
>    would the priority be 32764 for all of them?
>
>
>
> Once again, thank you for all of your help with this!!
>
>
>
> [image: 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
> doug.l.maxfi...@emcins.com | www.emcins.com
>
>
>
>
>
> *From:* Lev Veyde 
> *Sent:* Thursday, February 14, 2019 3:19 AM
> *To:* Doug Maxfield 
> *Cc:* users 
> *Subject:* Re: [ovirt-users] Creating a static route
>
>
>
> Hi Doug,
>
> Sorry that it took a bit of time to get back to you.
> Managed to catch today somebody from the oVirt

[ovirt-users] Re: Creating a static route

[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,

On Thu, Feb 14, 2019 at 4:59 PM Lev Veyde  wrote:

> 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 can be used for all of them. E.g. if you
> want to route 172.22.20.31, 172.22.34.56 and 172.22.67.89 you will need to
> add:
>
> to 172.22.20.31 priority 32764
> to 172.22.34.56 priority 32764
> to 172.22.67.89 priority 32764
>
> into the rule- file e.g. rule-ovirtmgmt or rule-eno3.
>
> Please note that you will also need to add the static route for each one
> of these as well w/ "ip route add ... " command e.g. "ip route add
> 172.22.20.31 via 172.21.12.61".
>
> You can also use the route- putting just the route info
> part, similar to the "ip rule" e.g. for equivalent of "ip route add
> 172.22.20.31 via 172.21.12.61" you need put in the file a line with the
> content "172.22.20.31 via 172.21.12.61".
> For routes it's important to use specifically the route-ovirtmgmt file
> since the script automatically adds the device to the route command i.e.
> you can put the following lines into your route-ovirtmgmt file:
>
> 172.22.20.31 via 172.21.12.61
> 172.22.34.56 via 172.21.12.61
> 172.22.67.89 via 172.21.12.68
>
> (In case the first 2 of the mentioned IPs should be routed through the
> 172.21.12.61 gateway, and the last one should be routed through the
> 172.21.12.68 gateway).
>
> For the reference you can take a look at the
> /etc/sysconfig/network-scripts/ifup-routes script.
> It does the actual processing of both "route" and "rule" files for all
> network interfaces on a system.
>
> Please feel free to contact if you have further questions.
>
> Thanks in advance,
>
> On Thu, Feb 14, 2019 at 3:39 PM Doug Maxfield 
> wrote:
>
>> Lev,
>>
>> Thanks for the response.  I was just getting ready to contact you about
>> this.  I do have 2 follow-up questions, if you don’t mind.
>>
>>
>>
>>1. When we were talking about creating the route that would be
>>enabled again after a reboot, you said to modify “the
>>/etc/sysconfig/network-scripts/rule- e.g. rule-ovirtmgmt 
>> or
>>rule-eno3 (just put in the file "to 172.22.20.31 priority 32764”.  Is
>>priority 32764 for the ip rule command?
>>2. If I have multiple IPs that I would need to create a static route,
>>would the priority be 32764 for all of them?
>>
>>
>>
>> Once again, thank you for all of your help with this!!
>>
>>
>>
>> [image: 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
>> doug.l.maxfi...@emcins.com | www.emcins.com
>>
>>
>>
>>
>>
>> *From:* Lev Veyde 
>> *Sent:* Thursday, February 14, 2019 3:19 AM
>> *To:* Doug Maxfield 
>> *Cc:* users 
>> *Subject:* Re: [ovirt-users] Creating a static route
>>
>>
>>
>> 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,
>>
>>
>>
>> On Tue, Feb 12, 2019 at 11:12 PM Doug Maxfield <
>> doug.l.maxfi...@emcins.com> wrote:
>>
>> 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.
>>
>>
>>
>> [image: 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
>> doug.l.maxfi...@emcins.com | www.emcins.com
>>
>>
>>
>>
>>

[ovirt-users] Re: Creating a static route

[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 can be used for all of them. E.g. if you
want to route 172.22.20.31, 172.22.34.56 and 172.22.67.89 you will need to
add:

to 172.22.20.31 priority 32764
to 172.22.34.56 priority 32764
to 172.22.67.89 priority 32764

into the rule- file e.g. rule-ovirtmgmt or rule-eno3.

Please note that you will also need to add the static route for each one of
these as well w/ "ip route add ... " command e.g. "ip route add
172.22.20.31 via 172.21.12.61".

You can also use the route- putting just the route info
part, similar to the "ip rule" e.g. for equivalent of "ip route add
172.22.20.31 via 172.21.12.61" you need put in the file a line with the
content "172.22.20.31 via 172.21.12.61".
For routes it's important to use specifically the route-ovirtmgmt file
since the script automatically adds the device to the route command i.e.
you can put the following lines into your route-ovirtmgmt file:

172.22.20.31 via 172.21.12.61
172.22.34.56 via 172.21.12.61
172.22.67.89 via 172.21.12.68

(In case the first 2 of the mentioned IPs should be routed through the
172.21.12.61 gateway, and the last one should be routed through the
172.21.12.68 gateway).

For the reference you can take a look at the
/etc/sysconfig/network-scripts/ifup-routes script.
It does the actual processing of both "route" and "rule" files for all
network interfaces on a system.

Please feel free to contact if you have further questions.

Thanks in advance,

On Thu, Feb 14, 2019 at 3:39 PM Doug Maxfield 
wrote:

> Lev,
>
> Thanks for the response.  I was just getting ready to contact you about
> this.  I do have 2 follow-up questions, if you don’t mind.
>
>
>
>1. When we were talking about creating the route that would be enabled
>again after a reboot, you said to modify “the
>/etc/sysconfig/network-scripts/rule- e.g. rule-ovirtmgmt or
>rule-eno3 (just put in the file "to 172.22.20.31 priority 32764”.  Is
>priority 32764 for the ip rule command?
>2. If I have multiple IPs that I would need to create a static route,
>would the priority be 32764 for all of them?
>
>
>
> Once again, thank you for all of your help with this!!
>
>
>
> [image: 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
> doug.l.maxfi...@emcins.com | www.emcins.com
>
>
>
>
>
> *From:* Lev Veyde 
> *Sent:* Thursday, February 14, 2019 3:19 AM
> *To:* Doug Maxfield 
> *Cc:* users 
> *Subject:* Re: [ovirt-users] Creating a static route
>
>
>
> 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,
>
>
>
> On Tue, Feb 12, 2019 at 11:12 PM Doug Maxfield 
> wrote:
>
> 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.
>
>
>
> [image: 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
> doug.l.maxfi...@emcins.com | www.emcins.com
>
>
>
>
>
> *From:* Lev Veyde 
> *Sent:* Tuesday, February 12, 2019 3:09 PM
> *To:* Doug Maxfield 
> *Cc:* users 
> *Subject:* Re: [ovirt-users] Creating a static route
>
>
>
> 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 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/network-scripts/rule- name> e.g. rule-ovirtmgmt or rule-eno3 (just put in the file "to
> 172.22.20.31 priority 32764" - without quotes), however of c

[ovirt-users] Re: Creating a static route

[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,

On Tue, Feb 12, 2019 at 11:12 PM Doug Maxfield 
wrote:

> 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.
>
>
>
> [image: 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
> doug.l.maxfi...@emcins.com | www.emcins.com
>
>
>
>
>
> *From:* Lev Veyde 
> *Sent:* Tuesday, February 12, 2019 3:09 PM
> *To:* Doug Maxfield 
> *Cc:* users 
> *Subject:* Re: [ovirt-users] Creating a static route
>
>
>
> 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 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/network-scripts/rule- name> e.g. rule-ovirtmgmt or rule-eno3 (just put in the file "to
> 172.22.20.31 priority 32764" - without quotes), however of course this
> needs to be tested to verify that it works.
>
> I forwarded the issue to the network team and hopefully they will update
> soon.
>
>
>
> Thanks in advance,
>
>
>
> On Tue, Feb 12, 2019 at 10:17 PM Doug Maxfield 
> wrote:
>
> 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 way to add the ip rule so it’s
> persistent?  I know how to make the ip route add persistent.
>
>
>
> [image: 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
> doug.l.maxfi...@emcins.com | www.emcins.com
>
>
>
>
>
> *From:* Lev Veyde 
> *Sent:* Tuesday, February 12, 2019 2:14 PM
> *To:* Doug Maxfield 
> *Cc:* users 
> *Subject:* Re: [ovirt-users] Creating a static route
>
>
>
> 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 that these should be run after each host reboot, since
> these commands are not persistent.
>
>
>
> Thanks in advance,
>
>
>
> On Tue, Feb 12, 2019 at 10:07 PM Doug Maxfield 
> wrote:
>
> 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  1.082 ms  1.313 ms
>
> 2  192.168.90.9 (192.168.90.9)  1.507 ms  2.090 ms  2.294 ms
>
> 3  pdputopcomm01.emcins.com (172.22.20.31)  1.403 ms  1.401 ms  1.348 ms
>
>
>
> [image: 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
> doug.l.maxfi...@emcins.com | www.emcins.com
>
>
>
>
>
> *From:* Lev Veyde 
> *Sent:* Tuesday, February 12, 2019 2:01 PM
> *To:* Doug Maxfield 
> *Cc:* users 
> *Subject:* Re: [ovirt-users] Creating a static route
>
>
>
> 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 ..

[ovirt-users] Re: Creating a static route

[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]<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
doug.l.maxfi...@emcins.com<mailto:doug.l.maxfi...@emcins.com> | 
www.emcins.com<http://www.emcins.com/>



From: Lev Veyde 
Sent: Tuesday, February 12, 2019 3:09 PM
To: Doug Maxfield 
Cc: users 
Subject: Re: [ovirt-users] Creating a static route

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 
mailto:lve...@redhat.com>> wrote:
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/network-scripts/rule- 
e.g. rule-ovirtmgmt or rule-eno3 (just put in the file "to 172.22.20.31 
priority 32764" - without quotes), however of course this needs to be tested to 
verify that it works.
I forwarded the issue to the network team and hopefully they will update soon.

Thanks in advance,

On Tue, Feb 12, 2019 at 10:17 PM Doug Maxfield 
mailto:doug.l.maxfi...@emcins.com>> wrote:
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 way to add the ip rule so it’s 
persistent?  I know how to make the ip route add persistent.

[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
doug.l.maxfi...@emcins.com<mailto:doug.l.maxfi...@emcins.com> | 
www.emcins.com<http://www.emcins.com/>



From: Lev Veyde mailto:lve...@redhat.com>>
Sent: Tuesday, February 12, 2019 2:14 PM
To: Doug Maxfield 
mailto:doug.l.maxfi...@emcins.com>>
Cc: users mailto:users@ovirt.org>>
Subject: Re: [ovirt-users] Creating a static route

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 that these should be run after each host reboot, since these 
commands are not persistent.

Thanks in advance,

On Tue, Feb 12, 2019 at 10:07 PM Doug Maxfield 
mailto:doug.l.maxfi...@emcins.com>> wrote:
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<http://CenteraAmesAN1.emcins.com> (172.21.12.61)  
0.487 ms  1.082 ms  1.313 ms
2  192.168.90.9 (192.168.90.9)  1.507 ms  2.090 ms  2.294 ms
3  pdputopcomm01.emcins.com<http://pdputopcomm01.emcins.com> (172.22.20.31)  
1.403 ms  1.401 ms  1.348 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
doug.l.maxfi...@emcins.com<mailto:doug.l.maxfi...@emcins.com> | 
www.emcins.com<http://www.emcins.com/>



From: Lev Veyde mailto:lve...@redhat.com>>
Sent: Tuesday, February 12, 2019 2:01 PM
To: Doug Maxfield 
mailto:doug.l.maxfi...@emcins.com>>
Cc: users mailto:users@ovirt.org>>
Subject: Re: [ovirt-users] Creating a static route

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 and let me know if that fixed the 
issue.

Thanks in advance,

On Tue, Feb 12, 2019 at 9:30 PM Doug Maxfield 
mailto:doug.l.maxfi...@emcins.com>> wrote:
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<http://172.21.0.0/16> iif ovirtmgmt lookup 
2887058719
32765:  from 172.21.0.0/16<http://172.21.0.0/16> lookup 2887058719
32766:  from all lookup main
32767:  from all lookup default


From working system

[root@paputopcomm04 ~]# ip rule
0:  from all lookup local
32766:  from all lookup main
3

[ovirt-users] Re: Creating a static route

[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 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/network-scripts/rule- name> e.g. rule-ovirtmgmt or rule-eno3 (just put in the file "to
> 172.22.20.31 priority 32764" - without quotes), however of course this
> needs to be tested to verify that it works.
>
> I forwarded the issue to the network team and hopefully they will update
> soon.
>
> Thanks in advance,
>
> On Tue, Feb 12, 2019 at 10:17 PM Doug Maxfield 
> wrote:
>
>> 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 way to add the ip rule so it’s
>> persistent?  I know how to make the ip route add persistent.
>>
>>
>>
>> [image: 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
>> doug.l.maxfi...@emcins.com | www.emcins.com
>>
>>
>>
>>
>>
>> *From:* Lev Veyde 
>> *Sent:* Tuesday, February 12, 2019 2:14 PM
>> *To:* Doug Maxfield 
>> *Cc:* users 
>> *Subject:* Re: [ovirt-users] Creating a static route
>>
>>
>>
>> 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 that these should be run after each host reboot, since
>> these commands are not persistent.
>>
>>
>>
>> Thanks in advance,
>>
>>
>>
>> On Tue, Feb 12, 2019 at 10:07 PM Doug Maxfield <
>> doug.l.maxfi...@emcins.com> wrote:
>>
>> 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  1.082 ms  1.313 ms
>>
>> 2  192.168.90.9 (192.168.90.9)  1.507 ms  2.090 ms  2.294 ms
>>
>> 3  pdputopcomm01.emcins.com (172.22.20.31)  1.403 ms  1.401 ms  1.348 ms
>>
>>
>>
>> [image: 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
>> doug.l.maxfi...@emcins.com | www.emcins.com
>>
>>
>>
>>
>>
>> *From:* Lev Veyde 
>> *Sent:* Tuesday, February 12, 2019 2:01 PM
>> *To:* Doug Maxfield 
>> *Cc:* users 
>> *Subject:* Re: [ovirt-users] Creating a static route
>>
>>
>>
>> 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 and let me know if that fixed
>> the issue.
>>
>>
>>
>> Thanks in advance,
>>
>>
>>
>> On Tue, Feb 12, 2019 at 9:30 PM Doug Maxfield 
>> wrote:
>>
>> 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
>>
&

[ovirt-users] Re: Creating a static route

[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/network-scripts/rule- e.g. rule-ovirtmgmt or rule-eno3 (just put in the file "to
172.22.20.31 priority 32764" - without quotes), however of course this
needs to be tested to verify that it works.

I forwarded the issue to the network team and hopefully they will update
soon.

Thanks in advance,

On Tue, Feb 12, 2019 at 10:17 PM Doug Maxfield 
wrote:

> 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 way to add the ip rule so it’s
> persistent?  I know how to make the ip route add persistent.
>
>
>
> [image: 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
> doug.l.maxfi...@emcins.com | www.emcins.com
>
>
>
>
>
> *From:* Lev Veyde 
> *Sent:* Tuesday, February 12, 2019 2:14 PM
> *To:* Doug Maxfield 
> *Cc:* users 
> *Subject:* Re: [ovirt-users] Creating a static route
>
>
>
> 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 that these should be run after each host reboot, since
> these commands are not persistent.
>
>
>
> Thanks in advance,
>
>
>
> On Tue, Feb 12, 2019 at 10:07 PM Doug Maxfield 
> wrote:
>
> 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  1.082 ms  1.313 ms
>
> 2  192.168.90.9 (192.168.90.9)  1.507 ms  2.090 ms  2.294 ms
>
> 3  pdputopcomm01.emcins.com (172.22.20.31)  1.403 ms  1.401 ms  1.348 ms
>
>
>
> [image: 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
> doug.l.maxfi...@emcins.com | www.emcins.com
>
>
>
>
>
> *From:* Lev Veyde 
> *Sent:* Tuesday, February 12, 2019 2:01 PM
> *To:* Doug Maxfield 
> *Cc:* users 
> *Subject:* Re: [ovirt-users] Creating a static route
>
>
>
> 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 and let me know if that fixed
> the issue.
>
>
>
> Thanks in advance,
>
>
>
> On Tue, Feb 12, 2019 at 9:30 PM Doug Maxfield 
> wrote:
>
> 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@paputopcomm04 ~]# ip rule
>
> 0:  from all lookup local
>
> 32766:  from all lookup main
>
> 32767:  from all lookup default
>
>
>
> [image: 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
> doug.l.maxfi...@emcins.com | www.emcins.com
>
>
>
>
>
> *From:* Lev Veyde 
> *Sent:* Tuesday, February 12, 2019 12:35 PM
> *To:* Doug Maxfield 
> *Cc:* users 
> *Subject:* Re: [ovirt-users] Creating a static route
>
>
>
> Hi Doug,
>
> That shouldn't really matter, since ovir

[ovirt-users] Re: Creating a static route

[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 way to add the ip rule so it’s 
persistent?  I know how to make the ip route add persistent.

[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
doug.l.maxfi...@emcins.com<mailto:doug.l.maxfi...@emcins.com> | 
www.emcins.com<http://www.emcins.com/>



From: Lev Veyde 
Sent: Tuesday, February 12, 2019 2:14 PM
To: Doug Maxfield 
Cc: users 
Subject: Re: [ovirt-users] Creating a static route

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 that these should be run after each host reboot, since these 
commands are not persistent.

Thanks in advance,

On Tue, Feb 12, 2019 at 10:07 PM Doug Maxfield 
mailto:doug.l.maxfi...@emcins.com>> wrote:
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<http://CenteraAmesAN1.emcins.com> (172.21.12.61)  
0.487 ms  1.082 ms  1.313 ms
2  192.168.90.9 (192.168.90.9)  1.507 ms  2.090 ms  2.294 ms
3  pdputopcomm01.emcins.com<http://pdputopcomm01.emcins.com> (172.22.20.31)  
1.403 ms  1.401 ms  1.348 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
doug.l.maxfi...@emcins.com<mailto:doug.l.maxfi...@emcins.com> | 
www.emcins.com<http://www.emcins.com/>



From: Lev Veyde mailto:lve...@redhat.com>>
Sent: Tuesday, February 12, 2019 2:01 PM
To: Doug Maxfield 
mailto:doug.l.maxfi...@emcins.com>>
Cc: users mailto:users@ovirt.org>>
Subject: Re: [ovirt-users] Creating a static route

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 and let me know if that fixed the 
issue.

Thanks in advance,

On Tue, Feb 12, 2019 at 9:30 PM Doug Maxfield 
mailto:doug.l.maxfi...@emcins.com>> wrote:
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<http://172.21.0.0/16> iif ovirtmgmt lookup 
2887058719
32765:  from 172.21.0.0/16<http://172.21.0.0/16> lookup 2887058719
32766:  from all lookup main
32767:  from all lookup default


From working system

[root@paputopcomm04 ~]# ip rule
0:  from all lookup local
32766:  from all lookup main
32767:  from all lookup default

[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
doug.l.maxfi...@emcins.com<mailto:doug.l.maxfi...@emcins.com> | 
www.emcins.com<http://www.emcins.com/>



From: Lev Veyde mailto:lve...@redhat.com>>
Sent: Tuesday, February 12, 2019 12:35 PM
To: Doug Maxfield 
mailto:doug.l.maxfi...@emcins.com>>
Cc: users mailto:users@ovirt.org>>
Subject: Re: [ovirt-users] Creating a static route

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 PM Doug Maxfield 
mailto:doug.l.maxfi...@emcins.com>> wrote:
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<http://169.254.0.0/16> dev eno3 scope link metric 1002
169.254.0.0/16<http://169.254.0.0/16> dev eno4 scope link metric 1005
172.17.0.0/16<http://172.17.0.0/16> dev eno4 proto kernel scope link src 
172.17.53.18
172.21.0.0/16<http://172.21.0.0/16> dev eno3 proto kernel scope link src 
172.21.5.34
172.22.20.31 via 172.21.12.61 dev eno3
172.26.0.0/16<http://172.26.0.0/16> dev eno1 proto kernel scope link src 
172.26.5.34



IP Route from server that didn't work

-bash-4.

[ovirt-users] Re: Creating a static route

[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 that these should be run after each host reboot, since
these commands are not persistent.

Thanks in advance,

On Tue, Feb 12, 2019 at 10:07 PM Doug Maxfield 
wrote:

> 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  1.082 ms  1.313 ms
>
> 2  192.168.90.9 (192.168.90.9)  1.507 ms  2.090 ms  2.294 ms
>
> 3  pdputopcomm01.emcins.com (172.22.20.31)  1.403 ms  1.401 ms  1.348 ms
>
>
>
> [image: 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
> doug.l.maxfi...@emcins.com | www.emcins.com
>
>
>
>
>
> *From:* Lev Veyde 
> *Sent:* Tuesday, February 12, 2019 2:01 PM
> *To:* Doug Maxfield 
> *Cc:* users 
> *Subject:* Re: [ovirt-users] Creating a static route
>
>
>
> 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 and let me know if that fixed
> the issue.
>
>
>
> Thanks in advance,
>
>
>
> On Tue, Feb 12, 2019 at 9:30 PM Doug Maxfield 
> wrote:
>
> 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@paputopcomm04 ~]# ip rule
>
> 0:  from all lookup local
>
> 32766:  from all lookup main
>
> 32767:  from all lookup default
>
>
>
> [image: 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
> doug.l.maxfi...@emcins.com | www.emcins.com
>
>
>
>
>
> *From:* Lev Veyde 
> *Sent:* Tuesday, February 12, 2019 12:35 PM
> *To:* Doug Maxfield 
> *Cc:* users 
> *Subject:* Re: [ovirt-users] Creating a static route
>
>
>
> 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 PM Doug Maxfield 
> wrote:
>
> 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 kernel scope link src 172.17.53.18
>
> 172.21.0.0/16 dev eno3 proto kernel scope link src 172.21.5.34
>
> *172.22.20.31 via 172.21.12.61 dev eno3*
>
> 172.26.0.0/16 dev eno1 proto kernel scope link src 172.26.5.34
>
>
>
>
>
>
>
> IP Route from server that didn't work
>
>
>
> -bash-4.2# 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.22.20.31 via 172.21.12.61 dev ovirtmgmt*
>
> 172.26.0.0/16 dev eno1 proto kernel scope link src 172.26.5.31
>
>
>
> We have had our network team look and they don’t know.  As I said, the was
> setup by Commvault.  It’s almost like the ovirtmgmt interface will not
> allow a route add due to the wa

[ovirt-users] Re: Creating a static route

[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  1.082 ms  1.313 ms
2  192.168.90.9 (192.168.90.9)  1.507 ms  2.090 ms  2.294 ms
3  pdputopcomm01.emcins.com (172.22.20.31)  1.403 ms  1.401 ms  1.348 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
doug.l.maxfi...@emcins.com<mailto:doug.l.maxfi...@emcins.com> | 
www.emcins.com<http://www.emcins.com/>



From: Lev Veyde 
Sent: Tuesday, February 12, 2019 2:01 PM
To: Doug Maxfield 
Cc: users 
Subject: Re: [ovirt-users] Creating a static route

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 and let me know if that fixed the 
issue.

Thanks in advance,

On Tue, Feb 12, 2019 at 9:30 PM Doug Maxfield 
mailto:doug.l.maxfi...@emcins.com>> wrote:
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<http://172.21.0.0/16> iif ovirtmgmt lookup 
2887058719
32765:  from 172.21.0.0/16<http://172.21.0.0/16> lookup 2887058719
32766:  from all lookup main
32767:  from all lookup default


From working system

[root@paputopcomm04 ~]# ip rule
0:  from all lookup local
32766:  from all lookup main
32767:  from all lookup default

[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
doug.l.maxfi...@emcins.com<mailto:doug.l.maxfi...@emcins.com> | 
www.emcins.com<http://www.emcins.com/>



From: Lev Veyde mailto:lve...@redhat.com>>
Sent: Tuesday, February 12, 2019 12:35 PM
To: Doug Maxfield 
mailto:doug.l.maxfi...@emcins.com>>
Cc: users mailto:users@ovirt.org>>
Subject: Re: [ovirt-users] Creating a static route

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 PM Doug Maxfield 
mailto:doug.l.maxfi...@emcins.com>> wrote:
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<http://169.254.0.0/16> dev eno3 scope link metric 1002
169.254.0.0/16<http://169.254.0.0/16> dev eno4 scope link metric 1005
172.17.0.0/16<http://172.17.0.0/16> dev eno4 proto kernel scope link src 
172.17.53.18
172.21.0.0/16<http://172.21.0.0/16> dev eno3 proto kernel scope link src 
172.21.5.34
172.22.20.31 via 172.21.12.61 dev eno3
172.26.0.0/16<http://172.26.0.0/16> dev eno1 proto kernel scope link src 
172.26.5.34



IP Route from server that didn't work

-bash-4.2# ip route
default via 172.21.0.250 dev ovirtmgmt
169.254.0.0/16<http://169.254.0.0/16> dev eno4 scope link metric 1004
169.254.0.0/16<http://169.254.0.0/16> dev ovirtmgmt scope link metric 1021
172.17.0.0/16<http://172.17.0.0/16> dev eno4 proto kernel scope link src 
172.17.53.15
172.21.0.0/16<http://172.21.0.0/16> dev ovirtmgmt proto kernel scope link src 
172.21.5.31
172.22.20.31 via 172.21.12.61 dev ovirtmgmt
172.26.0.0/16<http://172.26.0.0/16> dev eno1 proto kernel scope link src 
172.26.5.31

We have had our network team look and they don’t know.  As I said, the was 
setup by Commvault.  It’s almost like the ovirtmgmt interface will not allow a 
route add due to the way it’s configured?   They, Commvault, are trying 
different things within their software to get this working, but it’s causing us 
more problems.  I figured I would take a shot and see if someone, who works 
with the oVirt software, would have any ideas.


[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
doug.l.maxfi...@emcins.com<mailto:doug.l.maxfi...@emcins.com> | 
www.emcins.com<http://www.emcins.com/>



From: Lev Veyde mailto:lve...@redhat.com>>
Sent: Tuesday, February 12, 2019 11:51 AM
To: Doug Maxfield 
mailto:doug.l.maxfi...@emcins.com>>
Cc: users mailto:users@ovirt.org>>
Subject: Re: [ovirt-users] Creating a static route

Hi Dou

[ovirt-users] Re: Creating a static route

[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 and let me know if that fixed
the issue.

Thanks in advance,

On Tue, Feb 12, 2019 at 9:30 PM Doug Maxfield 
wrote:

> 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@paputopcomm04 ~]# ip rule
>
> 0:  from all lookup local
>
> 32766:  from all lookup main
>
> 32767:  from all lookup default
>
>
>
> [image: 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
> doug.l.maxfi...@emcins.com | www.emcins.com
>
>
>
>
>
> *From:* Lev Veyde 
> *Sent:* Tuesday, February 12, 2019 12:35 PM
> *To:* Doug Maxfield 
> *Cc:* users 
> *Subject:* Re: [ovirt-users] Creating a static route
>
>
>
> 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 PM Doug Maxfield 
> wrote:
>
> 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 kernel scope link src 172.17.53.18
>
> 172.21.0.0/16 dev eno3 proto kernel scope link src 172.21.5.34
>
> *172.22.20.31 via 172.21.12.61 dev eno3*
>
> 172.26.0.0/16 dev eno1 proto kernel scope link src 172.26.5.34
>
>
>
>
>
>
>
> IP Route from server that didn't work
>
>
>
> -bash-4.2# 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.22.20.31 via 172.21.12.61 dev ovirtmgmt*
>
> 172.26.0.0/16 dev eno1 proto kernel scope link src 172.26.5.31
>
>
>
> We have had our network team look and they don’t know.  As I said, the was
> setup by Commvault.  It’s almost like the ovirtmgmt interface will not
> allow a route add due to the way it’s configured?   They, Commvault, are
> trying different things within their software to get this working, but it’s
> causing us more problems.  I figured I would take a shot and see if
> someone, who works with the oVirt software, would have any ideas.
>
>
>
>
>
> [image: 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
> doug.l.maxfi...@emcins.com | www.emcins.com
>
>
>
>
>
> *From:* Lev Veyde 
> *Sent:* Tuesday, February 12, 2019 11:51 AM
> *To:* Doug Maxfield 
> *Cc:* users 
> *Subject:* Re: [ovirt-users] Creating a static route
>
>
>
> 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 may be the cause
> of this issue...
>
>
>
> Thanks in advance,
>
>
>
> On Tue, Feb 12, 2019 at 7:36 PM Doug Maxfield 
> wrote:
>
> 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
>
>   

[ovirt-users] Re: Creating a static route

[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@paputopcomm04 ~]# ip rule
0:  from all lookup local
32766:  from all lookup main
32767:  from all lookup default

[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
doug.l.maxfi...@emcins.com<mailto:doug.l.maxfi...@emcins.com> | 
www.emcins.com<http://www.emcins.com/>



From: Lev Veyde 
Sent: Tuesday, February 12, 2019 12:35 PM
To: Doug Maxfield 
Cc: users 
Subject: Re: [ovirt-users] Creating a static route

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 PM Doug Maxfield 
mailto:doug.l.maxfi...@emcins.com>> wrote:
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<http://169.254.0.0/16> dev eno3 scope link metric 1002
169.254.0.0/16<http://169.254.0.0/16> dev eno4 scope link metric 1005
172.17.0.0/16<http://172.17.0.0/16> dev eno4 proto kernel scope link src 
172.17.53.18
172.21.0.0/16<http://172.21.0.0/16> dev eno3 proto kernel scope link src 
172.21.5.34
172.22.20.31 via 172.21.12.61 dev eno3
172.26.0.0/16<http://172.26.0.0/16> dev eno1 proto kernel scope link src 
172.26.5.34



IP Route from server that didn't work

-bash-4.2# ip route
default via 172.21.0.250 dev ovirtmgmt
169.254.0.0/16<http://169.254.0.0/16> dev eno4 scope link metric 1004
169.254.0.0/16<http://169.254.0.0/16> dev ovirtmgmt scope link metric 1021
172.17.0.0/16<http://172.17.0.0/16> dev eno4 proto kernel scope link src 
172.17.53.15
172.21.0.0/16<http://172.21.0.0/16> dev ovirtmgmt proto kernel scope link src 
172.21.5.31
172.22.20.31 via 172.21.12.61 dev ovirtmgmt
172.26.0.0/16<http://172.26.0.0/16> dev eno1 proto kernel scope link src 
172.26.5.31

We have had our network team look and they don’t know.  As I said, the was 
setup by Commvault.  It’s almost like the ovirtmgmt interface will not allow a 
route add due to the way it’s configured?   They, Commvault, are trying 
different things within their software to get this working, but it’s causing us 
more problems.  I figured I would take a shot and see if someone, who works 
with the oVirt software, would have any ideas.


[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
doug.l.maxfi...@emcins.com<mailto:doug.l.maxfi...@emcins.com> | 
www.emcins.com<http://www.emcins.com/>



From: Lev Veyde mailto:lve...@redhat.com>>
Sent: Tuesday, February 12, 2019 11:51 AM
To: Doug Maxfield 
mailto:doug.l.maxfi...@emcins.com>>
Cc: users mailto:users@ovirt.org>>
Subject: Re: [ovirt-users] Creating a static route

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 may be the cause of 
this issue...

Thanks in advance,

On Tue, Feb 12, 2019 at 7:36 PM Doug Maxfield 
mailto:doug.l.maxfi...@emcins.com>> wrote:
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:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8<http://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:  mtu 1500 qdisc mq state UP qlen 1000
link/ether 90:1b:0e:db:bc:c0 brd ff:ff:ff:ff:ff:ff
inet 172.21.5.34/16<http://172.21.5.34/16> brd 172.21.255.255 scope global 
eno3
   valid_lft forever preferred_lft forever
inet6 fe80::921b:eff:fedb:bcc0/64 scope link
   valid_lft forever preferred_lft forever
3: eno1:  mtu 1500 qdisc mq state UP qlen 1000
link/ether 90:1b:0e:e8:da:03 brd ff:ff:ff:ff:ff:ff
inet 172.26.5.34/16<http://172.26.5.34/16> brd 172.26.255.255 scope global 
eno1
   valid

[ovirt-users] Re: Creating a static route

[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 PM Doug Maxfield 
wrote:

> 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 kernel scope link src 172.17.53.18
>
> 172.21.0.0/16 dev eno3 proto kernel scope link src 172.21.5.34
>
> *172.22.20.31 via 172.21.12.61 dev eno3*
>
> 172.26.0.0/16 dev eno1 proto kernel scope link src 172.26.5.34
>
>
>
>
>
>
>
> IP Route from server that didn't work
>
>
>
> -bash-4.2# 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.22.20.31 via 172.21.12.61 dev ovirtmgmt*
>
> 172.26.0.0/16 dev eno1 proto kernel scope link src 172.26.5.31
>
>
>
> We have had our network team look and they don’t know.  As I said, the was
> setup by Commvault.  It’s almost like the ovirtmgmt interface will not
> allow a route add due to the way it’s configured?   They, Commvault, are
> trying different things within their software to get this working, but it’s
> causing us more problems.  I figured I would take a shot and see if
> someone, who works with the oVirt software, would have any ideas.
>
>
>
>
>
> [image: 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
> doug.l.maxfi...@emcins.com | www.emcins.com
>
>
>
>
>
> *From:* Lev Veyde 
> *Sent:* Tuesday, February 12, 2019 11:51 AM
> *To:* Doug Maxfield 
> *Cc:* users 
> *Subject:* Re: [ovirt-users] Creating a static route
>
>
>
> 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 may be the cause
> of this issue...
>
>
>
> Thanks in advance,
>
>
>
> On Tue, Feb 12, 2019 at 7:36 PM Doug Maxfield 
> wrote:
>
> 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: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:  mtu 1500 qdisc mq state UP qlen
> 1000
>
> link/ether 90:1b:0e:db:bc:c0 brd ff:ff:ff:ff:ff:ff
>
> inet 172.21.5.34/16 brd 172.21.255.255 scope global eno3
>
>valid_lft forever preferred_lft forever
>
> inet6 fe80::921b:eff:fedb:bcc0/64 scope link
>
>valid_lft forever preferred_lft forever
>
> 3: eno1:  mtu 1500 qdisc mq state UP qlen
> 1000
>
> link/ether 90:1b:0e:e8:da:03 brd ff:ff:ff:ff:ff:ff
>
> inet 172.26.5.34/16 brd 172.26.255.255 scope global eno1
>
>valid_lft forever preferred_lft forever
>
> inet6 fe80::921b:eff:fee8:da03/64 scope link
>
>valid_lft forever preferred_lft forever
>
> 4: eno2:  mtu 1500 qdisc mq state DOWN
> qlen 1000
>
> link/ether 90:1b:0e:e8:da:04 brd ff:ff:ff:ff:ff:ff
>
> 5: eno4:  mtu 1500 qdisc mq state UP qlen
> 1000
>
> link/ether 90:1b:0e:db:bc:c1 brd ff:ff:ff:ff:ff:ff
>
> inet 172.17.53.18/16 brd 172.17.255.255 scope global eno4
>
>valid_lft forever preferred_lft forever
>
> inet6 fe80::921b:eff:fedb:bcc1/64 scope link
>
>valid_lft forever preferred_lft forever
>
> [root@paputopcomm04 ~]#
>
> [root@paputopcomm04 ~]#
>
> [root@paputopcomm04 ~]

[ovirt-users] Re: Creating a static route

[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 kernel scope link src 172.17.53.18
172.21.0.0/16 dev eno3 proto kernel scope link src 172.21.5.34
172.22.20.31 via 172.21.12.61 dev eno3
172.26.0.0/16 dev eno1 proto kernel scope link src 172.26.5.34



IP Route from server that didn't work

-bash-4.2# 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.22.20.31 via 172.21.12.61 dev ovirtmgmt
172.26.0.0/16 dev eno1 proto kernel scope link src 172.26.5.31

We have had our network team look and they don’t know.  As I said, the was 
setup by Commvault.  It’s almost like the ovirtmgmt interface will not allow a 
route add due to the way it’s configured?   They, Commvault, are trying 
different things within their software to get this working, but it’s causing us 
more problems.  I figured I would take a shot and see if someone, who works 
with the oVirt software, would have any ideas.


[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
doug.l.maxfi...@emcins.com<mailto:doug.l.maxfi...@emcins.com> | 
www.emcins.com<http://www.emcins.com/>



From: Lev Veyde 
Sent: Tuesday, February 12, 2019 11:51 AM
To: Doug Maxfield 
Cc: users 
Subject: Re: [ovirt-users] Creating a static route

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 may be the cause of 
this issue...

Thanks in advance,

On Tue, Feb 12, 2019 at 7:36 PM Doug Maxfield 
mailto:doug.l.maxfi...@emcins.com>> wrote:
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:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8<http://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:  mtu 1500 qdisc mq state UP qlen 1000
link/ether 90:1b:0e:db:bc:c0 brd ff:ff:ff:ff:ff:ff
inet 172.21.5.34/16<http://172.21.5.34/16> brd 172.21.255.255 scope global 
eno3
   valid_lft forever preferred_lft forever
inet6 fe80::921b:eff:fedb:bcc0/64 scope link
   valid_lft forever preferred_lft forever
3: eno1:  mtu 1500 qdisc mq state UP qlen 1000
link/ether 90:1b:0e:e8:da:03 brd ff:ff:ff:ff:ff:ff
inet 172.26.5.34/16<http://172.26.5.34/16> brd 172.26.255.255 scope global 
eno1
   valid_lft forever preferred_lft forever
inet6 fe80::921b:eff:fee8:da03/64 scope link
   valid_lft forever preferred_lft forever
4: eno2:  mtu 1500 qdisc mq state DOWN qlen 
1000
link/ether 90:1b:0e:e8:da:04 brd ff:ff:ff:ff:ff:ff
5: eno4:  mtu 1500 qdisc mq state UP qlen 1000
link/ether 90:1b:0e:db:bc:c1 brd ff:ff:ff:ff:ff:ff
inet 172.17.53.18/16<http://172.17.53.18/16> brd 172.17.255.255 scope 
global eno4
   valid_lft forever preferred_lft forever
inet6 fe80::921b:eff:fedb:bcc1/64 scope link
   valid_lft forever preferred_lft forever
[root@paputopcomm04 ~]#
[root@paputopcomm04 ~]#
[root@paputopcomm04 ~]# ip route
default via 172.21.0.250 dev eno3
169.254.0.0/16<http://169.254.0.0/16> dev eno3 scope link metric 1002
169.254.0.0/16<http://169.254.0.0/16> dev eno4 scope link metric 1005
172.17.0.0/16<http://172.17.0.0/16> dev eno4 proto kernel scope link src 
172.17.53.18
172.21.0.0/16<http://172.21.0.0/16> dev eno3 proto kernel scope link src 
172.21.5.34
172.26.0.0/16<http://172.26.0.0/16> dev eno1 proto kernel scope link src 
172.26.5.34
[root@paputopcomm04 ~]#
[root@paputopcomm04 ~]#
[root@paputopcomm04 ~]# 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<http://ames-acc1-agg-1.emcins.com> (172.21.0.246) 
 1.081 ms  1.816 ms  1.832 ms
2  192.168.200.30 (192.168.200.30)  0.639 ms 192.168.200.14 (192.168.200.14)  
1.063 ms  1.577 ms
3  192.168.200.101 (192.168.200.101)  3.110 ms 
ames-sw-wanrtr.emcins.com<http://ames-sw-wanrtr.emcins.com> (192.168.200.97)  
3.191 m

[ovirt-users] Re: Creating a static route

[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 may be the cause
of this issue...

Thanks in advance,

On Tue, Feb 12, 2019 at 7:36 PM Doug Maxfield 
wrote:

> 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: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:  mtu 1500 qdisc mq state UP qlen
> 1000
>
> link/ether 90:1b:0e:db:bc:c0 brd ff:ff:ff:ff:ff:ff
>
> inet 172.21.5.34/16 brd 172.21.255.255 scope global eno3
>
>valid_lft forever preferred_lft forever
>
> inet6 fe80::921b:eff:fedb:bcc0/64 scope link
>
>valid_lft forever preferred_lft forever
>
> 3: eno1:  mtu 1500 qdisc mq state UP qlen
> 1000
>
> link/ether 90:1b:0e:e8:da:03 brd ff:ff:ff:ff:ff:ff
>
> inet 172.26.5.34/16 brd 172.26.255.255 scope global eno1
>
>valid_lft forever preferred_lft forever
>
> inet6 fe80::921b:eff:fee8:da03/64 scope link
>
>valid_lft forever preferred_lft forever
>
> 4: eno2:  mtu 1500 qdisc mq state DOWN
> qlen 1000
>
> link/ether 90:1b:0e:e8:da:04 brd ff:ff:ff:ff:ff:ff
>
> 5: eno4:  mtu 1500 qdisc mq state UP qlen
> 1000
>
> link/ether 90:1b:0e:db:bc:c1 brd ff:ff:ff:ff:ff:ff
>
> inet 172.17.53.18/16 brd 172.17.255.255 scope global eno4
>
>valid_lft forever preferred_lft forever
>
> inet6 fe80::921b:eff:fedb:bcc1/64 scope link
>
>valid_lft forever preferred_lft forever
>
> [root@paputopcomm04 ~]#
>
> [root@paputopcomm04 ~]#
>
> [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 kernel scope link src 172.17.53.18
>
> 172.21.0.0/16 dev eno3 proto kernel scope link src 172.21.5.34
>
> 172.26.0.0/16 dev eno1 proto kernel scope link src 172.26.5.34
>
> [root@paputopcomm04 ~]#
>
> [root@paputopcomm04 ~]#
>
> [root@paputopcomm04 ~]# 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.081 ms  1.816 ms  1.832 ms
>
> 2  192.168.200.30 (192.168.200.30)  0.639 ms 192.168.200.14
> (192.168.200.14)  1.063 ms  1.577 ms
>
> 3  192.168.200.101 (192.168.200.101)  3.110 ms ames-sw-wanrtr.emcins.com
> (192.168.200.97)  3.191 ms  3.277 ms
>
> 4  192.168.100.26 (192.168.100.26)  4.146 ms  4.273 ms  4.394 ms
>
> 5  192.168.100.98 (192.168.100.98)  1.893 ms  2.364 ms  2.397 ms
>
> 6  192.168.100.50 (192.168.100.50)  5.707 ms 192.168.100.33
> (192.168.100.33)  5.134 ms 192.168.100.50 (192.168.100.50)  4.105 ms
>
> 7  pdputopcomm01.emcins.com (172.22.20.31)  1.359 ms  1.374 ms  1.351 ms
>
> [root@paputopcomm04 ~]#
>
> [root@paputopcomm04 ~]#
>
> [root@paputopcomm04 ~]#
>
> [root@paputopcomm04 ~]#
>
> [root@paputopcomm04 ~]# ip route add 172.22.20.31 via 172.21.12.61
>
> [root@paputopcomm04 ~]#
>
> [root@paputopcomm04 ~]#
>
> [root@paputopcomm04 ~]#
>
> [root@paputopcomm04 ~]# 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)  6.184 ms  6.475 ms  6.686 ms
>
> 2  192.168.90.9 (192.168.90.9)  1.770 ms  1.979 ms  2.189 ms
>
> 3  pdputopcomm01.emcins.com (172.22.20.31)  1.405 ms *  1.354 ms
>
>
>
> [image: 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
> doug.l.maxfi...@emcins.com | www.emcins.com
>
>
>
>
>
> *From:* Lev Veyde 
> *Sent:* Tuesday, February 12, 2019 11:07 AM
> *To:* Doug Maxfield 
> *Cc:* users 
> *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 y

[ovirt-users] Re: Creating a static route

[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: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:  mtu 1500 qdisc mq state UP qlen 1000
link/ether 90:1b:0e:db:bc:c0 brd ff:ff:ff:ff:ff:ff
inet 172.21.5.34/16 brd 172.21.255.255 scope global eno3
   valid_lft forever preferred_lft forever
inet6 fe80::921b:eff:fedb:bcc0/64 scope link
   valid_lft forever preferred_lft forever
3: eno1:  mtu 1500 qdisc mq state UP qlen 1000
link/ether 90:1b:0e:e8:da:03 brd ff:ff:ff:ff:ff:ff
inet 172.26.5.34/16 brd 172.26.255.255 scope global eno1
   valid_lft forever preferred_lft forever
inet6 fe80::921b:eff:fee8:da03/64 scope link
   valid_lft forever preferred_lft forever
4: eno2:  mtu 1500 qdisc mq state DOWN qlen 
1000
link/ether 90:1b:0e:e8:da:04 brd ff:ff:ff:ff:ff:ff
5: eno4:  mtu 1500 qdisc mq state UP qlen 1000
link/ether 90:1b:0e:db:bc:c1 brd ff:ff:ff:ff:ff:ff
inet 172.17.53.18/16 brd 172.17.255.255 scope global eno4
   valid_lft forever preferred_lft forever
inet6 fe80::921b:eff:fedb:bcc1/64 scope link
   valid_lft forever preferred_lft forever
[root@paputopcomm04 ~]#
[root@paputopcomm04 ~]#
[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 kernel scope link src 172.17.53.18
172.21.0.0/16 dev eno3 proto kernel scope link src 172.21.5.34
172.26.0.0/16 dev eno1 proto kernel scope link src 172.26.5.34
[root@paputopcomm04 ~]#
[root@paputopcomm04 ~]#
[root@paputopcomm04 ~]# 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.081 ms  1.816 ms  1.832 ms
2  192.168.200.30 (192.168.200.30)  0.639 ms 192.168.200.14 (192.168.200.14)  
1.063 ms  1.577 ms
3  192.168.200.101 (192.168.200.101)  3.110 ms ames-sw-wanrtr.emcins.com 
(192.168.200.97)  3.191 ms  3.277 ms
4  192.168.100.26 (192.168.100.26)  4.146 ms  4.273 ms  4.394 ms
5  192.168.100.98 (192.168.100.98)  1.893 ms  2.364 ms  2.397 ms
6  192.168.100.50 (192.168.100.50)  5.707 ms 192.168.100.33 (192.168.100.33)  
5.134 ms 192.168.100.50 (192.168.100.50)  4.105 ms
7  pdputopcomm01.emcins.com (172.22.20.31)  1.359 ms  1.374 ms  1.351 ms
[root@paputopcomm04 ~]#
[root@paputopcomm04 ~]#
[root@paputopcomm04 ~]#
[root@paputopcomm04 ~]#
[root@paputopcomm04 ~]# ip route add 172.22.20.31 via 172.21.12.61
[root@paputopcomm04 ~]#
[root@paputopcomm04 ~]#
[root@paputopcomm04 ~]#
[root@paputopcomm04 ~]# 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)  6.184 ms  6.475 ms  6.686 ms
2  192.168.90.9 (192.168.90.9)  1.770 ms  1.979 ms  2.189 ms
3  pdputopcomm01.emcins.com (172.22.20.31)  1.405 ms *  1.354 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
doug.l.maxfi...@emcins.com<mailto:doug.l.maxfi...@emcins.com> | 
www.emcins.com<http://www.emcins.com/>



From: Lev Veyde 
Sent: Tuesday, February 12, 2019 11:07 AM
To: Doug Maxfield 
Cc: users 
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 
mailto:doug.l.maxfi...@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.

[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
doug.l.maxfi...@emcins.com<mailto:doug.l.maxfi...@emcins.com> | 
www.emcins.com<http://www.emcins.com/>



From: Lev Veyde mailto:lve...@redhat.com>>
Sent: Tuesday, February 12, 2019 10:50 AM
To: Doug Maxfield 
mailto:doug.l.maxfi...@emcins.com>>
Cc: users mailto: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

[ovirt-users] Re: Creating a static route

[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.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
doug.l.maxfi...@emcins.com<mailto:doug.l.maxfi...@emcins.com> | 
www.emcins.com<http://www.emcins.com/>



From: Lev Veyde 
Sent: Tuesday, February 12, 2019 11:07 AM
To: Doug Maxfield 
Cc: users 
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 
mailto:doug.l.maxfi...@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.

[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
doug.l.maxfi...@emcins.com<mailto:doug.l.maxfi...@emcins.com> | 
www.emcins.com<http://www.emcins.com/>



From: Lev Veyde mailto:lve...@redhat.com>>
Sent: Tuesday, February 12, 2019 10:50 AM
To: Doug Maxfield 
mailto:doug.l.maxfi...@emcins.com>>
Cc: users mailto: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 
mailto:doug.l.maxfi...@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.

[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
doug.l.maxfi...@emcins.com<mailto:doug.l.maxfi...@emcins.com> | 
www.emcins.com<http://www.emcins.com/>



From: Lev Veyde mailto:lve...@redhat.com>>
Sent: Tuesday, February 12, 2019 10:34 AM
To: Doug Maxfield 
mailto:doug.l.maxfi...@emcins.com>>
Cc: users mailto: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

[ovirt-users] Re: Creating a static route

[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, 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:  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:  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:  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:  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:  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:  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;:  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

[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
doug.l.maxfi...@emcins.com<mailto:doug.l.maxfi...@emcins.com> | 
www.emcins.com<http://www.emcins.com/>



From: Lev Veyde 
Sent: Tuesday, February 12, 2019 11:07 AM
To: Doug Maxfield 
Cc: users 
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 
mailto:doug.l.maxfi...@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.

[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
doug.l.maxfi...@emcins.com<mailto:doug.l.maxfi...@emcins.com> | 
www.emcins.com<http://www.emcins.com/>



From: Lev Veyde mailto:lve...@redhat.com>>
Sent: Tuesday, February 12, 2019 10:50 AM
To: Doug Maxfield 
mailto:doug.l.maxfi...@emcins.com>>
Cc: users mailto: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 
mailto:doug.l.maxfi...@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.

[C

[ovirt-users] Re: Creating a static route

[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 have added the static route?

Thanks in advance,


On Tue, Feb 12, 2019 at 6:58 PM Doug Maxfield 
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.
>
>
>
> [image: 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
> doug.l.maxfi...@emcins.com | www.emcins.com
>
>
>
>
>
> *From:* Lev Veyde 
> *Sent:* Tuesday, February 12, 2019 10:50 AM
> *To:* Doug Maxfield 
> *Cc:* users 
> *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 
> 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.
>
>
>
> [image: 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
> doug.l.maxfi...@emcins.com | www.emcins.com
>
>
>
>
>
> *From:* Lev Veyde 
> *Sent:* Tuesday, February 12, 2019 10:34 AM
> *To:* Doug Maxfield 
> *Cc:* users 
> *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  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-le...@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/
>
>
>
> --
>
>
>
> *Lev Veyde*
>
> Software Engineer, RHCE | RHCVA | MCITP
>
> Red Hat Israel
>
> <https://www.redhat.com>
>
> l...@redhat.com | lve...@redhat.com
>
> <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.  I

[ovirt-users] Re: Creating a static route

[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]<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
doug.l.maxfi...@emcins.com<mailto:doug.l.maxfi...@emcins.com> | 
www.emcins.com<http://www.emcins.com/>



From: Lev Veyde 
Sent: Tuesday, February 12, 2019 10:50 AM
To: Doug Maxfield 
Cc: users 
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 
mailto:doug.l.maxfi...@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.

[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
doug.l.maxfi...@emcins.com<mailto:doug.l.maxfi...@emcins.com> | 
www.emcins.com<http://www.emcins.com/>



From: Lev Veyde mailto:lve...@redhat.com>>
Sent: Tuesday, February 12, 2019 10:34 AM
To: Doug Maxfield 
mailto:doug.l.maxfi...@emcins.com>>
Cc: users mailto: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 
mailto:doug.l.maxfi...@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<mailto:users@ovirt.org>
To unsubscribe send an email to 
users-le...@ovirt.org<mailto:users-le...@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/


--


Lev Veyde

Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com<mailto:l...@redhat.com> | 
lve...@redhat.com<mailto:lve...@redhat.com>
[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>

l...@redhat.com<mailto:l...@redhat.com> | 
lve...@redhat.com<mailto:lve...@redhat.com>
[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>
___

[ovirt-users] Re: Creating a static route

[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 results.

[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
doug.l.maxfi...@emcins.com<mailto:doug.l.maxfi...@emcins.com> | 
www.emcins.com<http://www.emcins.com/>



From: Lev Veyde 
Sent: Tuesday, February 12, 2019 10:50 AM
To: Doug Maxfield 
Cc: users 
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 
mailto:doug.l.maxfi...@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.

[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
doug.l.maxfi...@emcins.com<mailto:doug.l.maxfi...@emcins.com> | 
www.emcins.com<http://www.emcins.com/>



From: Lev Veyde mailto:lve...@redhat.com>>
Sent: Tuesday, February 12, 2019 10:34 AM
To: Doug Maxfield 
mailto:doug.l.maxfi...@emcins.com>>
Cc: users mailto: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 
mailto:doug.l.maxfi...@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<mailto:users@ovirt.org>
To unsubscribe send an email to 
users-le...@ovirt.org<mailto:users-le...@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/


--


Lev Veyde

Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com<mailto:l...@redhat.com> | 
lve...@redhat.com<mailto:lve...@redhat.com>
[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>

l...@redhat.com<mailto:l...@redhat.com> | 
lve...@redhat.com<mailto:lve...@red

[ovirt-users] Re: Creating a static route

[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) 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 
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.
>
>
>
> [image: 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
> doug.l.maxfi...@emcins.com | www.emcins.com
>
>
>
>
>
> *From:* Lev Veyde 
> *Sent:* Tuesday, February 12, 2019 10:34 AM
> *To:* Doug Maxfield 
> *Cc:* users 
> *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  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-le...@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/
>
>
>
> --
>
>
>
> *Lev Veyde*
>
> Software Engineer, RHCE | RHCVA | MCITP
>
> Red Hat Israel
>
> <https://www.redhat.com>
>
> l...@redhat.com | lve...@redhat.com
>
> <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>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/VSRTKE2I26JZZNPCAGO4NXK22F4632YW/

[ovirt-users] Re: Creating a static route

[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 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
doug.l.maxfi...@emcins.com<mailto:doug.l.maxfi...@emcins.com> | 
www.emcins.com<http://www.emcins.com/>



From: Lev Veyde 
Sent: Tuesday, February 12, 2019 10:34 AM
To: Doug Maxfield 
Cc: users 
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 
mailto:doug.l.maxfi...@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<mailto:users@ovirt.org>
To unsubscribe send an email to 
users-le...@ovirt.org<mailto:users-le...@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/


--


Lev Veyde

Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com<mailto:l...@redhat.com> | 
lve...@redhat.com<mailto:lve...@redhat.com>
[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
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/E3HEE6T3DA447BCI522G4JJVDKXJH2DD/

[ovirt-users] Re: Creating a static route

[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 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-le...@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/
>


-- 

Lev Veyde

Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel



l...@redhat.com | lve...@redhat.com

TRIED. TESTED. TRUSTED. 
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/SDDEUFJ63LKLUR6TVJWM7YSWXD46AFUD/