can add esx host to vcenter server
I am having real difficulties with an esx 192.168.0.203 host running 5.1 it will not connect to vcenter server 192.168.0.210 I have been looking and it seems an issue with 5.1
I have tried stopping vxpa and starting it again but that didn't work so I removed the vm's of and rebuilt it and still got the error vxpa timeout
as you will see in the bottom server it is configured correctly
I have tried stopping vxpa and starting it again but that didn't work so I removed the vm's of and rebuilt it and still got the error vxpa timeout
as you will see in the bottom server it is configured correctly
Danny McDaniel
is that a typo in your vcenter name for the host that you named it 192.168.0.201?
vCenter Server is 5.1?
ASKER
oh yes its 5.0 I cant seem to find 5.1 anywhere either
you will need to use vCenter Server 5.1 to manage ESXi 5.0 and ESXi 5.1 hosts?
are you trying to add a 5.1 host to vCenter Server 5.0?
are you trying to add a 5.1 host to vCenter Server 5.0?
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
I have heard its not easy to do update from 5.0 to 5.1 single sign on and loads of changes I may just role back to 5.0 for now actually
The best way, to implement vCenter Server 5.1 is a new installation. (unless you desperately want to keep performance Summary's)
for one host, do you really need SSO? did you get vCenter as you planned to roll out more hosts later or something?
I have recently performed a vCenter 4.x to 5.1 in-place upgrade.
In my case, vCenter 4.x was using SQL 2005 Express. We wanted to move it to SQL 2008 R2 Express. First, we upgraded SQL independently and then we let vCenter upgrade the existing DB. It wasn't that bad though. It installed all the new services (SSO, et all)
If you are already on SQL 2008 R2 Express, it might be even easier than you thought.
In my case, vCenter 4.x was using SQL 2005 Express. We wanted to move it to SQL 2008 R2 Express. First, we upgraded SQL independently and then we let vCenter upgrade the existing DB. It wasn't that bad though. It installed all the new services (SSO, et all)
If you are already on SQL 2008 R2 Express, it might be even easier than you thought.