I received a reply from a Citrix representative - here's what they said:
Whenever there is no network found, it is because the XenServer is unable to reach the pool master. The XenServer console display network information from the pool database. How can this happen? When a slave is upgraded before the pool master. Another way this can happen, is if the pool master has been placed into maintenance mode (thereby making it a slave). How to resolve? Upgrade the pool master and then the slaves will rejoin the pool and display the network information. The upgrade steps for upgrading a pool are discussed in the XenServer installation guide "rolling pool upgrade". If you log into the XenServer, and type "ifconfig", you will indeed see an IP address on an interface. Looking at /etc/xensource/pool.conf will show that it is a slave, followed by the IP address of the pool master. The pool master is always backwards compatible to an previous version, but is not forward compatible to a newer (unknown) version of XenServer.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
It looks like I just installed the upgrade in the wrong order. I rolled back the server that was hosed to 5.0 and I"m going to upgrade the Pool Master here the first chance I get. Thanks for your response though.
Main Topics
Browse All Topics





by: ToxicPigPosted on 2009-11-09 at 12:46:34ID: 25779871
Will it take a license if you reapply it?
Worst case, you could back up your server/pool metadata and/or export your VM's if they are on local disk (root disk that would be formatted), and then reinstall. Fully depends on your setup. I make sure all of my VM's are on shared storage, and then I can just treat my XS hosts as throw-away. I've done clean installs on pool members several times to fix hardware issues.