@olivierlambert well someone had to test it

Hi im coming back to xcpng and xenorchestra.
Once ive tested almost all the hypervisors and gui I have to say that xcpng + xoce is ideal for us but i have problems with the gui usability.

All the gui we have tried are tree structured, even xcenter, why us xoce using that (for me) not friendly interface? When trying to use nodes, vm an details is not a big deal. Seems a program made by IT to be used by IT

Thats why we still use xcenter and xoce only for backups.

Could be nice to have a gui similar to proxmox, the best I used ( but they cannot manage multiple pools, here is where i discarted them)

@rizaemet-0 thanks you've got the right. I already doing this, but I didn't know if you uninstalled it and installed a previous version.

it was just curiosity. So I'm gonna rollback to a previous snapshot too.

Thank you

hi there, yes we're using XOCE and I said that we have this problem because may be something wrong in the latests releases.

just trying to help the developers to show that there is a problem in the new versions, as I can see XOA is more tested may be because the XOCE users help to test it.

so my posts are intended to help not to complain about this wonderful product.

ok, I changed the ETHs order to make them be the same as the production server, so both pool have their ETHs numbers in the same order.

eth0,1 - management
eth2,3 - vm
eth4,5 - SAN

and now the Disaster Recovery backup set the correct NIC in the VM.

problem solved.

Congratulations ! Very glad to hear that !

@Danp thanks ! but I have rolled back to a previous version ( 5.50.1) and now I'm testing the backup again.

@rizaemet-0 thanks you've got the right. I already doing this, but I didn't know if you uninstalled it and installed a previous version.

it was just curiosity. So I'm gonna rollback to a previous snapshot too.

Thank you

@rizaemet-0 could you tell me how have you reverted to 5.50.1 ? thanks

hi there, yes we're using XOCE and I said that we have this problem because may be something wrong in the latests releases.

just trying to help the developers to show that there is a problem in the new versions, as I can see XOA is more tested may be because the XOCE users help to test it.

so my posts are intended to help not to complain about this wonderful product.

I have to say that I'm having the same problems.

everything is updated to the last version.

xcp-ng 8.0.0

xo-server 5.51.1
xo-web 5.51.0

ok, I changed the ETHs order to make them be the same as the production server, so both pool have their ETHs numbers in the same order.

eth0,1 - management
eth2,3 - vm
eth4,5 - SAN

and now the Disaster Recovery backup set the correct NIC in the VM.

problem solved.

hi, may be this gonna be a problem for another users, and may be could be an improvement for XO.

meanwhile I found this
http://www.ultimaforsan.com/logs/2011/8/10/xenserver-addremove-network-interface.html

that is useful for changing VM NIC, also tried and works fine.

and another solution is changing the order of NICs in XCP-ng
https://support.citrix.com/article/CTX135809#Identifying Existing NIC Characteristics

There will be an easy way to do a massive change of network, isn't it? With a bash script or something like that.

I copied a huge amount of VM from a one pool to another via Disaster Recovery

everything went fine, but when I checked the network of the VM i realized that it has assigned it a management NIC

has you can see the first pool it has a bond core with 2+3 NIC,

in the backup VM it has a NIC that is Network 3, that it belongs to the management bond 2+3

the order and NIC bonds have different order in one pool and the other.

pool 1.
bond 0+1 = management (1Gb)
bond 2+3 = VM (10Gb)
bond 4+5 = SAN (10Gb)

pool2
bond 0+1 = VM (10Gb)
bond 2+3 = management (1Gb)
bond 4+5 = SAN (10Gb)

is there a way I can tell with network has the backup VM use in the new pool ?

thanks