Thanx for the note. Still not working. I made the change on the hosts and manager and then added the custom ip addresses to the ovirtmgmt network. The attached screenshot shows the custom IP address added to ovirtmgmt.

Same issue.

2020-04-10 21:05:13.882+0000: 5801: error : virNetSocketNewConnectTCP:591 : unable to connect to server at '192.168.25.5:49152': No route to host.

I can ping the 192.168.25.x address on the host - but I can't ping the .25.x address on the other host.

I also can't ping either 192.168.25.x address from the manager.

One question I had is does the migration network need to be a VM Network? I've tried it several ways - but just wanted to know the right configuration.

Thanx!!!

On Fri, Apr 10, 2020 at 3:55 PM <briandumont@gmail.com> wrote:

Thanx for the suggestion. Changed my networks to the following and still got the same error:

5801: error : virNetSocketNewConnectTCP:591 : unable to connect to server at '192.168.25.5:49152': No route to host

Here is my updated configuration:
- 2 Hosts
- Host 1
- nic 1 - ovirtmgmt - 192.168.1.24/24 - VLAN 1
- nic 2 - migration network - 192.168.25.5/24 VLAN 25
- Host 2
- nic 1 - ovirtmgmnt - 192.168.1.24/24 - VLAN 1
- nic 2 - migration network - 192.168.25.6/24 - VLAN 25

Migration network is setup as follows:
- Assign - Yes
- Required - Yes
- VM Network - No (tried it with VM Nework = Yes with same results)
- Migration Network - Yes
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/VLS2EVPDQDHIKMWLLQVMHOPL22CQVQB2/