Surgient Success

I am trying to add my host to the pool, and got the following error in an email.  Can you tell me what things to look at please?  

 
For part two, the host is no longer available on that "add a host to this pool" list.  How do I get it back?
 

9/26/2007 4:08:37 PM|Severe|initialize-nail-vm.20 |[ScriptEngine] Script 20 "initialize-nail-vm", LAB-DEV-H01 (name="LAB-DEV-H01-NailServer-1", type="NailServer", poolid="1") failed with exception: Surgient.Automation.AutomationException: 00350084 The NAIL server agent on LAB-DEV-H01 has not registered with the VCS after 600 seconds.  This error is most often the result of one of the two following problems:  1.  The NAIL server's assigned pooled IP address is incompatible with its host's default network (if the 'Use Pooled IP Address' option was chosen when the host was added to the pool).  2.  The NAIL server was not able to obtain an IP address from a DHCP server (if the 'DHCP' option was chosen when the host was added to the pool).
 

majaroo:

I am trying to add my host to the pool, and got the following error in an email.  Can you tell me what things to look at please?  

This is an error scenario covered in the Troubleshooting chapter of the Install Guide, page 71 of the PDF or page 61 if you printed it out.  The error message itself covers two possibilities of what went wrong, and the Install Guide covers two more.  Regardless, the symptom is the same--an agent that we run inside of an infrastructure VM (i.e. the NAIL server) cannot contact the VQMS server.

Here is what you can check:

1. Make sure you pick the right host network adapter when you added the host to the pool.  This is the NIC that is physically cabled to a network that has connectivity to your VQMS server.  Eventually this will be the network to which your VMs will be connected.  The host's network adapters are presented in the Add Host to Pool dialog via their associated Port Group (ESX) or Virtual Network (MVS), so if you don't see the NIC in the list, you need to go back to the VMware VI Client or the Microsoft Virtual Server console and add a Port Group or Virtual Network and associate it with the right host network adapter.
2. Our infrastructure VM needs an IP address and maybe it isn't getting one.  It can be assigned an IP address either via DHCP or by consuming one of the network resources that you added to the pool.  This is another choice on the Add Host to Pool dialog.  If you chose DHCP then maybe you picked the wrong host network adapter (case #1) or maybe your network's DHCP server isn't assigning IP addresses to unknown hardware addresses (unlikely).  If you chose to consume a Pool IP Address, then double-check the network resources.  Specifically, the IP range must be compatible with the physical network (i.e. one of the logical networks configured on the router), and it cannot overlap with IP addresses managed by the DHCP server on the network.  Also, make sure you got the network mask and default gateway IP address right.  These are visible on the Details tab when you select the IP Address range in the Network Resources view.

Let us know what you find.

Well, it looks like I accidentally typed in the wrong gateway address.  Oops.  I then managed to repool the host successfully from the hosts view of the resource tab ("assign to pool" button), so things are working again.  At least until my next adventure!

 Thanks so much for your help.