@bleader said in Created a new bond interface and lost management connectivity to hosts:

The original problem could be a known issue when creating bond including the management interface that we have to investigate. Although the emergency network reset should have fixed that, so maybe it is a mix of the bond creation issue and MTU issue.

In the reinstalled pool, did you create the bonds already? If so I would think changing the MTU should be fine, especially as it worked on other PIF, but with MTU issue it is often quite sneaky, so I would not make any promises either.

Yes I have recreated them, but I am not game enough yet to change the management interfaces to MTU 9000, though I have done on bridge interfaces for VMs, because I was losing ssh sessions, and this solved the issue. Also, the bonded storage interface is MTU 9000 no problem.

@olivierlambert Thanks, I have tried using xe-reset-networking and the emergency network reset function in the UI of XCP-NG and neither seem to work to reset the management Interface, after rebooting they still have no interfaces at all (which happened when the failed uplink bond was created).
I will probably need to wipe and re-install to get traction again.
Also I am confused with the MTU.
The servers we are using are configured (using a server profile template) that we also use with vMware, and the uplinks on those are all MTU 9000 both in the VNIC templates (ie hardware side) and in the distributed vSwitches in vCenter (equivalent of bonded interfaces in XO?)
If their was a problem with MTU, I would have though they would not work either.
I will keep at it, thanks for the help.

@olivierlambert Thanks, I see they are there