@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

@olivierlambert Interesting, thanks.

@olivierlambert Yet things like pool settings (networks for example) are shared?

@olivierlambert For example:

I have 2 instances of XO, looking at the same servers/pools

Instance: I enable ldap-auth plugin, configure it, and sync groups
Instancev2: ldap-auth remains disabled with no configuration, and groups remain empty.

Thanks.

PS Your forum is running extremely slowly the last few days.

Murf

Bug or feature please?
Thanks,
Murf.

@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 I have rebuilt the servers, and configured Pool networking successfully keeping the MTU at 1500.
However when I create a VIF on one link for usage in a VM I kept getting data timeouts in ssh sessions and server (VM) access to resources, and setting the VIF and the underlying PIF to MTU 9000 resolved the issue.

I am assuming I will need to do the same to the rest of my links, including the management one, but I dont want to end up in the same situation as before and lose my cluster. Any suggestions?!
Thanks.

Brett.

@Danp Oh thanks, that makes sense, though I am not sure how I got it to work in the POC...
Cold migration will be fine for the time being anyway

Hi All.
I definitely had this working in our POC, but now I am using it in anger I cant seem to get this to work without powering down the VM in vCenter first;
The VM gets created in XO, but it happens instantly and there is no storage migration.
Any clues much appreciated please!

@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 I have 9000 everywhere on the network so i set the MTU to that.
I did notice in a previous POC that I used 1500 in XO/XCP-NG though....
Thoughts?
How can I recover, just delete /re-install the hypervisor and reconnect?