VMware Cloud Community
techguru007
Contributor
Contributor
Jump to solution

After Virtual Center upgrade from 2.0.2 to 2.0.5 - Alerts ; Host Connection State = Not Responding

Greetings,

After Virtual Center upgrade from 2.0.2 to 2.0.5 - Alerts ; Host Connection State = Not Responding. Currently ESX ver 3.3. Service Console RAM is 800MB. Does anyone come across this Issue. Please suggest.

Thanks

Techguru007

0 Kudos
1 Solution

Accepted Solutions
Cooldude09
Commander
Commander
Jump to solution

Sounds good the problem got fixed...fir alarms...restart VC service from services.msc and see if it helps...else we may need to look into log files to see if there are any errors.

Regards

Anil

Save the planet, Go Green

if you found my answer to be useful, feel free to mark it as Helpful or Correct.

If U find my answer useful, feel free to give points by clicking Helpful or Correct.

Subscribe yourself at walkonblock.com

View solution in original post

0 Kudos
9 Replies
oreeh
Immortal
Immortal
Jump to solution

FYI: this thread has been moved to the vCenter Server forum.

Oliver Reeh[/i]

[VMware Communities User Moderator|http://communities.vmware.com/docs/DOC-2444][/i]

0 Kudos
Cooldude09
Commander
Commander
Jump to solution

are we seeing any errors in/var/log/vmkernel file. Also try to remove the esx and add it back to the VC and see if it helps.

Regards

Anil

Save the planet, Go Green

if you found my answer to be useful, feel free to mark it as Helpful or Correct.

If U find my answer useful, feel free to give points by clicking Helpful or Correct.

Subscribe yourself at walkonblock.com

0 Kudos
techguru007
Contributor
Contributor
Jump to solution

Tried by running following commands.

  1. service vmware-vpxa stop

  1. service mgmt-vmware restart

  1. service vmware-vpxa start

And then login to VI Client as say Example: ESX06

User name as : root

Password: ***

After successful login, check for connection VM status, And found no issues.

>>> disconnect.

Again login to VI Client through regular credentials Check for successful login / VM status. And found no issues.

Currently no issues with VM's. All sHosts servers are up and running fine .

Except the Alert Messages.

Please find the attachment of Sample Alerts. Please suggest.

0 Kudos
Cooldude09
Commander
Commander
Jump to solution

Sounds good the problem got fixed...fir alarms...restart VC service from services.msc and see if it helps...else we may need to look into log files to see if there are any errors.

Regards

Anil

Save the planet, Go Green

if you found my answer to be useful, feel free to mark it as Helpful or Correct.

If U find my answer useful, feel free to give points by clicking Helpful or Correct.

Subscribe yourself at walkonblock.com

0 Kudos
Wimo
Hot Shot
Hot Shot
Jump to solution

Sounds like you're all set, but other things to try for this problem are to check that the directory /tmp/vmware-root exists, and create it if not; and to delete vpxuser, which will get recreated when VC connects to the host again.

0 Kudos
techguru007
Contributor
Contributor
Jump to solution

Hi Wimo,

Still my problem continues.. Could you please, brief the steps to be followed for the same.

Thanks

0 Kudos
Wimo
Hot Shot
Hot Shot
Jump to solution

cd to /tmp, do an ls and see if there is directory called vmware-root.

If not, create it - mkdir vmware-root

If still no luck - userdel vpxuser. That account will be recreated when VC and ESX talk to each other again.

Another possiblity is that you will have to manually install the vpxa agent:

http://kb.vmware.com/selfservice/viewContent.do?externalId=1003714&sliceId=1

Message was edited by: Wimo

0 Kudos
techguru007
Contributor
Contributor
Jump to solution

Hello Wimo,

Found the directory (vmware-root) was unavailable. Created the directory and deleted the vpxuser.

Already followed the KB 1003714 - But no luck. Any other suggestions please..

Currently ESX server is 3.0.3 Does 3.0.5 update helps.

Thanks in Advance

0 Kudos
Wimo
Hot Shot
Hot Shot
Jump to solution

Running out of ideas, short of a reboot. Any management agents installed? Like HP agents?

service hpasm stop

will stop them - or whatever the command would be if a different vendor.

0 Kudos