Hello, I am trying to configure a dedicated migration network and am unable to get it to work. It is failing with a no route to host error in the cockpit logs, specifically a libvirtd error virNetSocketNewConnectTCP:591 : unable to connect to server at '192.168.1.50:49152': No route to host. Trying to migrate from Host 1 to Host 2. 192.168.1.50 is the ip address on the source host for the migration. If I try to migrate in the other direction I get the same error with tthat hosts migration network ip. My migration network is setup on a different VLAN than my ovirtmgmt network. Here is my configuration: - 2 Hosts - Host 1 - nic 1 - ovirtmgmt - 192.168.1.24/24 - VLAN 1 - nic 2 - migration network - 192.168.1.50/24 VLAN 25 - Host 2 - nic 1 - ovirtmgmnt - 192.168.1.24/24 - VLAN 1 - nic 2 - migration network - 192.168.1.51/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 I think I've got something fundamentally wrong with my host networking but I can't figure it out. Appreciate the help.
Just pointing out the obvious, but you have vlan 1 and 50 on the same subnet unless it's a mistype. Eric Evans Digital Data Services LLC. 304.660.9080 -----Original Message----- From: briandumont@gmail.com <briandumont@gmail.com> Sent: Friday, April 10, 2020 1:48 PM To: users@ovirt.org Subject: [ovirt-users] Can't migrate over migration network Hello, I am trying to configure a dedicated migration network and am unable to get it to work. It is failing with a no route to host error in the cockpit logs, specifically a libvirtd error virNetSocketNewConnectTCP:591 : unable to connect to server at '192.168.1.50:49152': No route to host. Trying to migrate from Host 1 to Host 2. 192.168.1.50 is the ip address on the source host for the migration. If I try to migrate in the other direction I get the same error with tthat hosts migration network ip. My migration network is setup on a different VLAN than my ovirtmgmt network. Here is my configuration: - 2 Hosts - Host 1 - nic 1 - ovirtmgmt - 192.168.1.24/24 - VLAN 1 - nic 2 - migration network - 192.168.1.50/24 VLAN 25 - Host 2 - nic 1 - ovirtmgmnt - 192.168.1.24/24 - VLAN 1 - nic 2 - migration network - 192.168.1.51/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 I think I've got something fundamentally wrong with my host networking but I can't figure it out. Appreciate the help. _______________________________________________ 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/UKECTE7BRDWYDV...
Apologies, vlans 1 and 25. They should be separate subnets. Eric Evans Digital Data Services LLC. 304.660.9080 -----Original Message----- From: briandumont@gmail.com <briandumont@gmail.com> Sent: Friday, April 10, 2020 1:48 PM To: users@ovirt.org Subject: [ovirt-users] Can't migrate over migration network Hello, I am trying to configure a dedicated migration network and am unable to get it to work. It is failing with a no route to host error in the cockpit logs, specifically a libvirtd error virNetSocketNewConnectTCP:591 : unable to connect to server at '192.168.1.50:49152': No route to host. Trying to migrate from Host 1 to Host 2. 192.168.1.50 is the ip address on the source host for the migration. If I try to migrate in the other direction I get the same error with tthat hosts migration network ip. My migration network is setup on a different VLAN than my ovirtmgmt network. Here is my configuration: - 2 Hosts - Host 1 - nic 1 - ovirtmgmt - 192.168.1.24/24 - VLAN 1 - nic 2 - migration network - 192.168.1.50/24 VLAN 25 - Host 2 - nic 1 - ovirtmgmnt - 192.168.1.24/24 - VLAN 1 - nic 2 - migration network - 192.168.1.51/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 I think I've got something fundamentally wrong with my host networking but I can't figure it out. Appreciate the help. _______________________________________________ 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/UKECTE7BRDWYDV...
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
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/htm... That should take care of the problem for you. Eric Evans Digital Data Services LLC. 304.660.9080 -----Original Message----- From: briandumont@gmail.com <briandumont@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-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/VLS2EVPDQDHIKM...
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:
I migrate over the vm network. You need to ask someone more familiar with Ovirt about the migration vs. the vm network. I have had issue getting different subnets for the vm’s to function properly. My understanding is that if the engine host knows and can use the network, you should be able to use it. However, the migration network has to be setup on the hosts and attached to a nic in order to use it. In the host properties and setup networks, is the migration network attached to a nic with the proper subnets or vlans? I’m not sure if that’s helpful or not. I just don’t know enough about Ovirt to give a definitive answer. Eric Evans Digital Data Services LLC. 304.660.9080 From: Brian Dumont <briandumont@gmail.com> Sent: Friday, April 10, 2020 5:15 PM To: users@ovirt.org Subject: [ovirt-users] Re: Can't migrate over migration network 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 <http://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 <mailto: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 <http://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 <http://192.168.1.24/24> - VLAN 1 - nic 2 - migration network - 192.168.25.5/24 <http://192.168.25.5/24> VLAN 25 - Host 2 - nic 1 - ovirtmgmnt - 192.168.1.24/24 <http://192.168.1.24/24> - VLAN 1 - nic 2 - migration network - 192.168.25.6/24 <http://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 <mailto:users@ovirt.org> To unsubscribe send an email to users-leave@ovirt.org <mailto: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/VLS2EVPDQDHIKM...
Evan, Thanx for your help. I think I've got the Networks setup correctly on the Setup Hosts Network section, but obviously I've got something fundamentally wrong. Just can't figure it out. Thanx again On Fri, Apr 10, 2020 at 5:14 PM Brian Dumont <briandumont@gmail.com> wrote:
I set a migration network today. At first I could not ping the other machines, but then I realized the vlan was a tagged vlan in ovirt. I changed the switch ports to general and tagged them and it worked. I don't know your network or config, but thought I would pass this along. If you have a vlan configured in ovirt, the ports attaching to that network card have to be tagged, not un-tagged. Not sure if this will help but wanted to pass it along.
This helped. I originally got the migration network to work by removing the vlan tags from the ovirt network and switch ports and just using a different subnet for the migration network. Worked fine. However I wanted to get the vlans working. Your suggestion got me thinking about my Aruba switch and how its different from a Cisco. I had my switchports in access mode which was passing all traffic as untagged when the traffic coming from ovirt was tagged. I put the vlan tags back on the ovirt network and then changed my switchports to trunk and removed the native vlan and now the traffic is tagged all the way through and the migration network is now working with the vlan. Appreciate the help.
Glad you got it worked out. Eric Evans Digital Data Services LLC. 304.660.9080 -----Original Message----- From: Brian Dumont <briandumont@gmail.com> Sent: Wednesday, April 15, 2020 1:41 PM To: users@ovirt.org Subject: [ovirt-users] Re: Can't migrate over migration network This helped. I originally got the migration network to work by removing the vlan tags from the ovirt network and switch ports and just using a different subnet for the migration network. Worked fine. However I wanted to get the vlans working. Your suggestion got me thinking about my Aruba switch and how its different from a Cisco. I had my switchports in access mode which was passing all traffic as untagged when the traffic coming from ovirt was tagged. I put the vlan tags back on the ovirt network and then changed my switchports to trunk and removed the native vlan and now the traffic is tagged all the way through and the migration network is now working with the vlan. Appreciate the help. _______________________________________________ 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/EI4T4XU4ZZ53P4...
participants (4)
-
Brian Dumont -
briandumont＠gmail.com
-
eevans＠digitaldatatechs.com -
Maton, Brett