Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've got a bit of an issue with our Citrix Xenserver system (were still running 5.6)

Last week we had to dismantle our server racks due to some required building work. Since reassembling one of our xenservers has had a bonded network connection listed as disconnected despite both NIC's being connected and operational.

I'm kinda inexperienced with it just got dumped on me a while back due to the original administrator leaving I have no training past what I have learnt myself (i know PACKT publishings Xenserver Administration Essentials Guide like the back of my hand but there isn't anything on troubleshooting this kind of problem.)

Anyway enough of my moaning

because I'm terrible at explaining things here's a couple of screen shots



Bonding Setting

So basically everything connected but the virtual bond interface is still being listed as disconnected which doesn't make any sense, I've even recreated the 2+3 bond but it still coming up as disconnected.

Any help would be appreciated


Hey Dan, I ran that command but it didn't list anything? I'm guessing thats a problem. They are setup on the actual xenserver interface (if you plug in a monitor/keyboard direct into the server)

I've already tried it. We have 3 xenservers in the pool so I just dropped it out of the pool re-setup the NIC's and re added it same issue and it's only with this server, the other 2 (exact same hardware) are working fine.

Hey the problem is now resolved but I can't seem to find out why. I just rebooted the server and suddenly everything was working, only things I changed was I recreated the links again but it still said it was disconnected, I rebooted it on a whim.

Not sure if it just needed the reboot to update it conf or something.

share|improve this question
Have you checked this from a completely different client? Sometimes XenCenter caches old information. – Striker_84 Aug 7 '13 at 12:59
What hardware? Try 'xe pif-scan host-uuid=<hosts UUID>' – Dan Aug 7 '13 at 22:49
How many virtual machines do you have? I'm thinking it may be easier to do a network reset and start from scratch. This will probably mean re-adding NICs to each VM, though. Not a problem if there's 5, but a nightmare if you have 45 VDI's or something! – Dan Aug 8 '13 at 8:14
Silly question but have you tried swapping network cables around to ensure the issue doesn't follow them. Just as a matter of ruling things out – Dan Aug 8 '13 at 16:30
Glad you go it working - if you could post a brief summary of what you did (Even though I know not everything made a difference) as an answer, you could accept it then. – Dan Aug 14 '13 at 8:34

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.