HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
Server Management - Systems Insight Manager
cancel
Showing results for 
Search instead for 
Did you mean: 

but the VM Host is not communicating with HP VMM

 
Matts_2
Contributor

but the VM Host is not communicating with HP VMM

Hi

I get this in my SIM
The VM Guest is associated with a licensed VM Host, but the VM Host is not communicating with HP VMM

And also this

Communication has been lost with the HP VMM Agent service.
VMM Information will become accessible once the communication with the VMM Agent is re-established.
HP VMM agent service on the host can be started using Configure->Virtualization Management->Restart VMM Agent For more information, refer to the user guide section troubleshooting.

I have done this Configure->Virtualization Management->Restart VMM Agent
on my VMWare machine and it say No, Host ESX01 is connected
I have try to run Configure and Repair agent
and I have still same problem

SIM version C.05.01.00.02
and the other is
HP BladeSystem Integrated Manager 2.3
HP Insight Power Manager 1.0
HP Performance Management Pack 4.6
HP Server Migration Pack 2.1
HP Virtual Machine Management Pack 2.1


What to do?

/Matts
2 REPLIES
BonaChrister
Occasional Visitor

Re: but the VM Host is not communicating with HP VMM

Has it been working? SIM lost communication with my ESX Hosts after upgrading ESX to 3.0.2. Had to upgrade SIM to 5.1 SP1, install new version of HP-VMM pack 4.3.0, redeploy VMM agent from HP SIM to ESX servers again.
After this SIM to VMM communication works fine.
Robert Brooks_1
Honored Contributor

Re: but the VM Host is not communicating with HP VMM

So the first question to be answered is "what changed"? That presumes that your configuration has worked in the past. What version of ESX are you running and what version of the management agents have you installed on the ESX host?

Have you considered upgrading to VMM V3.0? I'm not claiming that will solve your problem, but absent some specific reason to stay at 2.1, I'd think about upgrading VMM on the CMS. Of course, if you do that, you'll need to deploy VMM to the various ESX host(s) on your CMS.

Have you verified that no other CMS is managing that ESX host?

-- Rob