For anyone following, I reverted the changes back to using em1 only and will wait for the 3 node cluster to be functional before making changes as recommended.
Thanks Simon -----Original Message----- From: [email protected] <[email protected]> On Behalf Of [email protected] Sent: September 6, 2019 1:02 PM To: 'Dominik Holler' <[email protected]>; [email protected] Cc: [email protected] Subject: RE: [ovirt-users] Re: network config change So in the case here, the work was already started outside of the ovirt engine UI. I inherited the problem, so far I've made sure to point the em1,3 to the bond0, confirmed it was working (in mode 4, lacp), pointed the bond0 to the ovirtmgmt bridge. Now the current setup uses dhcp and the IP address is successfully assigned. One of the issue I'm seeing right now is that the hosted engine VM will not start. So I started looking a bit further and I can see that route has some issues: 192.168.20.0/24 dev em1 proto kernel scope link src 192.168.20.108 192.168.20.0/24 dev ovirtmgmt proto kernel scope link src 192.168.20.108 The first line prevents the host from talking to it's default gateway (20.1) because it's using em1 which has no IP (part of bond0) If I remove the line from the routing table, I can successfully ping the default gateway through the ovirtmgmt interface. I can't figure out how to prevent the system from recreating the first line during a reboot. I don’t know if this is one of the reason why the engine fails or not, but since the ovirt startup process seems to validate ping, when the services are starting during boot time, they'll fail because that route is re-added. Thanks again Simon -----Original Message----- From: Dominik Holler <[email protected]> Sent: September 6, 2019 2:07 AM To: [email protected] Cc: [email protected] Subject: [ovirt-users] Re: network config change On Thu, 5 Sep 2019 08:27:07 -0400 <[email protected]> wrote: > Greetings, > > So we have a single hosted engine ovirt box deployed. > > When this was deployed, the network requirements were poorly > determined and there was no port teaming or any vlan configuration. > > now we need to change that. > > I have searched all over for any form of procedure or guide as to how > we do this. > > in summary: > > I need to go from a setup that uses em1 as it's default device and > gateway to a setup where em1 and 3 are bonded into bond0 and now use > that instead. > > All modifications should be done via oVirt Engine, e.g. in Administration Portal via Compute > Hosts > hostname > Network Interfaces > Setup Host Networks because this way the change will be rolled back automatically on failures. Because this change modifies many aspects of the management network, I would recommend to add a temporary second host, migrate the hosted Engine on this second host, and put the first host in maintenance and migrate back to the first host after the change succeeded. > > As for the vlan we could live with keeping the native vlan configured > on the cisco side for management and only add extra ones for VMs. > > any assistance as to what I need to go through from a bash shell would > be appreciated. > > thanks > > Simon > _______________________________________________ Users mailing list -- [email protected] To unsubscribe send an email to [email protected] Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/[email protected]/message/FBWLN2RGHSQO7NJPSQR7RMEE62RAFDU2/ _______________________________________________ Users mailing list -- [email protected] To unsubscribe send an email to [email protected] Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/[email protected]/message/TYB2NNC4PEKV7WJXR23Q5TU5L3E3SIIR/
