Follow this article to add the extra addrs. On the ovirtmgmt interface on the 
hosts, go to custom  and add the IP's you need. See the attached screenshot.
https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/html/administration_guide/sect-Hosts_and_Networking#Editing-VLAN-Settings
That should take care of the problem for you.


Eric Evans
Digital Data Services LLC.
304.660.9080


-----Original Message-----
From: briandum...@gmail.com <briandum...@gmail.com> 
Sent: Friday, April 10, 2020 3:55 PM
To: users@ovirt.org
Subject: [ovirt-users] Re: Can't migrate over migration network

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

_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/IIKZ35KTDDF2VDFP3Z2EGXEUX2IK5W2Q/

Reply via email to