VMM2.1 - ports in use?

[Ole Thomsen_1]

In our ESX3.01 cluster i managed to install vmm2.1 on 3 of 4 servers. The last server claims that the ports for vmm agent are in use, which is rather weird as the servers has identical setup.

From the agent installation task log (manual installation has same result):

HP Virtual Machine Management Agent 4.1.0.1214 Installer for VMware ESX Server

An older version of HP Virtual Machine Management Agent is installed.

Removing older version of HP Virtual Machine Management Agent.

Stopping hpvmmcnt: [ OK ]

Removed older version HP Virtual Machine Management Agent successfully.

Installing VMM Agent

Preparing... ##################################################

hpvmmagent ##################################################

Starting hpvmmcnt: [ OK ]

checking the port usage.

No port range change is required.

The agent installation has not completed since one of the port´s 1124 -1126 are in use. Try installing the agents after freeing the ports.


Ole Thomsen

[Rob Buxton]

Ole,
I saw this error on one of ours as well, but it didn't seem to affect the operation of VMM at all.
All servers in our cluster show up and list all of the associated VM's.
The big test comes later today when I do a P2V!

[Ole Thomsen_1]

Thanks Rob, that did cross my mind.

But when i try to register i get the following error:

Agent registration failed! - 192.168.106.43
The VMM agent cannot be connected or is locked to another service. Install the VMM agent or unregister it from the other CMS.

Ole Thomsen

[Rob Buxton]

You could try restarting the VMM Service or looking at the logs. I tried looking briefly here, but it's full of the usual java messages and whether they are errors or not is anyone's guess.
Not too sure if the netstat command would show what might have it.

[Ole Thomsen_1]

I tried restarting the HPSIM server, also running netstat on the ESX host, but according to that none of the ports are in use.

Ole Thomsen

[Rob Buxton]

I was thinking more of the vmm agent itself.
The start shell for vmm seems to be;
/etc/rc.d/init.d/hpvmmcntsvc
You could try running that with a start or restart parameter. You can also use the status parameter.

[pal_pal]

I would suggest that you try the following steps:

1. Check if the ESX is pingable from the CMS
2. Turn off the VMM agent on the ESX box.
service hpvmmsvccnt stop
3. Check if the ports are in use
If yes you need to check who is using it and make sure the ports are freed. These ports are HP IANA registered ports.
4. If the ports are free, start the agent
service hpvmmsvccnt start
5. Again check if the ports are occupied. If the agent is running properly, they should be in use
6. Try registering the system now.

Hope that should help.

[Ole Thomsen_1]

Well, I just found out that netstat on ESX default shows only connected ports (I'm a Windows guy)....

The case is that when I stop or uninstall the agent nothing is using the ports, and as soon as the agent is installed/started it claims the ports 1125 and 1126.

But....agent installation does not finish, no matter if I uninstall first or not. The installation always ends with:

checking the port usage.

No port range change is required.

The agent installation has not completed since one of the ports 1124 -1126 are in use. Try installing the agents after freeing the ports.


After that I'm unable to register the server:

Agent registration failed! - 192.168.106.43
The VMM agent cannot be connected or is locked to another service. Install the VMM agent or unregister it from the other CMS.


My guess is that one of the "not completed" things could be ESX firewall configuration?

Thanks for all the help so far.

Ole Thomsen

[Ole Thomsen_1]

It seems that the firewall services.xml was f*cked up by our VCB install, there was an entry like this:



I can't tell who needs help, but after removing the entry, adding vmmsrc.xml from the install package to services.xml and refreshing the firewall, I was able to register the host.

Thanks,
Ole Thomsen

[Ole Thomsen_1]

Case closed...