Dec 21, 2012

No Interface Configured After Re-IP'ing XenServers

I really like XenServer. Although I'm more of a VMWare man, and am VMWare certified, I still prefer the free version of XenServer over VMWare ESXi because you can cluster it. Because you can cluster it, and it's free, we use it at my company's office to host our local company servers.

Well over the weekend we replaced our Firewall with a new one, and since I had to swap out the firewall I thought it would be a good opportunity to re-design the network, which meant a new IP scheme. With new IP addresses, that meant I had to re-IP the XenServers.

I re-IP'ed the XenServers through XenCenter, but after I did that only the master server could be contacted. I went over to the physcial servers and opened up a local terminal, and it appeared like the NICs were missing! When I went to configure the IP addresses, there was a message saying, "No Interface Configured."

Needless to say, that was quite the set back as I couldn't continue with the rest of the stuff I had to do for the re-design until I got that working again. Here's what I had to do on each of the slave XenServers:

  • Drop to the shell and run the following command to make the slave the master temporarily:

    #xe pool-emergency-transition-to-master
  • Exit the shell, and now you should be able to configure a management IP address through the local GUI.
  • Drop back to the shell and run the following to make the REAL master the master again, and slave the affected machine to the master:

    #xe pool-emergency-reset-master master-address=[IP of Master]
That's it, after doing the above on each of the slaves, I was able to re-IP them and re-attach them to the master.

Have you ever run into a similar issue? Did you resolve it differently? If so, let me know in the comments!

Twitter Delicious Facebook Digg Stumbleupon Favorites More

Design by Free WordPress Themes | Bloggerized by Lasantha - Premium Blogger Themes | stopping spam