Troubleshooting the Failure of the eG Agent to Auto-discover the IP Addresses of VMs
If the eG agent is not able to discover the IP addresses of one/more VMs, then follow the steps given below:
- Login to the root partition.
- Go to the command prompt.
- Switch to the directory, <eg_install_dir>\lib.
Run the following command from that directory:
If this script executes successfully, it would return the following information:
- The names of the VMs on the Hyper-V host;
- The current state of each VM (the value 2 if the VM is running, and the value 3 if it is powered-off);
- The Fully Qualified Domain Name (FQDN) of every VM
- The operating system on which each VM is executing
- Make a note of the FQDN of a VM.
Then, issue the following command at the command prompt to identify the IP address of that VM:
- If this command fails to return the IP address of the VM, it could mean that the IP address is not resolvable in the DNS server.
On the other hand, if the eG_HypervGuestInfo.vbs script itself fails to return the FQDN and the operating system of the VMs, it could indicate one/more of the following:
- For VM discovery to occur, the Integration Services component should be installed on every target VM. Non-availability of the Integration Services component on a VM could cause the script to not report the FQDN and operating system of that VM.
The script may also fail if the target VMs are executing on any of the following Windows operating systems:
- Windows Server 2008 64-bit
- Windows Server 2008 x86
- Windows Server 2003 x64 with SP2
- Windows 2000 Server with SP4
- Windows 2000 Advanced Server SP4
- Windows Vista x64 with SP1
- Windows Vista x86 with SP1
- Windows XP x86 with SP2/SP3
- Windows XP x64 with SP2
This is because the eG_HypervGuestInfo.vbs script is not supported on any of the above-mentioned opeating systems.
- Similarly, if a VM is executing on a Linux operating system, then again the eG_HypervGuestInfo.vbs script will not be able to retrieve the FQDN of that VM.