Hi Yedidyah, Thank you for you update.
This platform started with 4.3 deployment. The Default mac address pool, apparently on all Clusters (5) is: from_mac | to_mac -------------------+------------------- 56:6f:ef:88:00:00 | 56:6f:ef:88:ff:ff Interestingly enough, I am alos not able to add another mac pool to Default. I can only create new one, let's say MacPool2 and also create only single pool inside. Option to add second mac range under same name is grayed out, whether I login as SuperUser or Admin to Aministration Portal. Never mind, it is as so, but I am still not "happiest" with: > Question2: Would there be an harming effect on existing VMs if the default mac pool would be changed? => I am pretty certain it's harmless, but didn't try that myself. Reason is that I have 600VMs on 5 cluster setup in production - If I make the change where currently required and we are wrong, its going to affect almost half of those existing VMs. I did test the change on the staging, and it did not seem to have any harmful effect but that one has like 5VMs atm. I will run some additional tests on staging to see if I can get more comfortable before making change in production, but if anyone else can contribute boosting the confidence, please let me know. ----- kind regards/met vriendelijke groeten Marko Vrgotic ActiveVideo On 22/01/2020, 09:03, "Yedidyah Bar David" <d...@redhat.com> wrote: On Tue, Jan 21, 2020 at 2:30 PM Vrgotic, Marko <m.vrgo...@activevideo.com> wrote: > > Dear oVirt, > > > > While investigating and DHCP & DDNS collision issues between two VM servers from different oVirt clusters, I noticed that oVirt assigns same default MAC range for each of it’s managed clusters. Is this a new 4.3 setup, or upgraded from earlier versions? See also: https://bugzilla.redhat.com/show_bug.cgi?id=1516445 Fixed in 4.3 (and backported to 4.2.7), only for new setups. The default changed several times in versions before these, and upgrades do not change the stored default. What's your default mac pool in each engine? You can get it with: /usr/share/ovirt-engine/dbscripts/engine-psql.sh -c "select from_mac, to_mac from mac_pools, mac_pool_ranges where id=mac_pool_id and default_pool='t'" Or by checking admin ui - Administration -> Configure, there "MAC Address Pools", and double click Default. > > > > Question1: Does oVirt-Engine keep separate place in DB or … for MAC addresses assigned per cluster or it keeps them all in same place? By *default*, all in same place, and above bug (and patches linked from it) describe the current specifics. This changed several times along the versions before these. You can manually configure it, including to be per cluster - search for "MAC Address Pools" here: https://www.ovirt.org/documentation/admin-guide/chap-Global_Configuration.html > > > > Question2: Would there be an harming effect on existing VMs if the default mac pool would be changed? I am pretty certain it's harmless, but didn't try that myself. > > > > > > Additional info: > > Self Hosted ovirt-engine – 4.3.4 and 4.3.7 > > > > > > ----- > > kind regards/met vriendelijke groeten > > > > Marko Vrgotic > ActiveVideo > > > > > > _______________________________________________ > 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/TCNZHWSYS2VKGAE24ECMCYKK4YVYYLYL/ -- Didi _______________________________________________ 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/373K7N4LGHX4ZHXFMP6EAAX4XV63RQFN/