Will these two networks be able to talk to each other?
If the two NIC that are in both servers are talking to each other the VM's which talk through them also wil talk to each other.
Distributed switch is not an option as you don't have extra NIC. You will be able to use only standard switches.
Yes, that worked for me also, thanks to all involved.
Hello Sarek,
Even I faced the same problem. You can use the syntax: "remote, <identifer>"
eg: "remote, mpx.vmhba0:C0:T0:L0"
Thanks,
Mohan
We use vCenter Server Appliance (VMware-vCenter-Server-Appliance-5.5.0.5101-1398493_OVF10.ova) to build our vCenter.
It works fine.
However, today, after I update it to a new version (from the file: VMware-vCenter-Server-Appliance-5.5.0.10000-1440531-updaterepo.zip),
the hosts are disconnected from vCenter with error message: Disconnected from host. Reason: Agent upgrade.
The tasks in each host also shows Upgrade agent fail.
The parameter AgentUpgrade.autoUpgradeAgents is set to TRUE.
I couldn't find any useful thread on internet.
Please help. Thank you!!
Hi,
Seems to be something wrong with the vpxa agent on the host., may be the version did not get updated ,
check this KB : VMware KB: ESX hosts show as disconnected after VirtualCenter upgrade
Hope this helps.
Thanks,
Avinash
OK thanks all
Hi Friends,
I am trying to install the first vCenter server in our organization. vCenter SSO was installed successfully.
When Installing WebClient I'm getting following errors
"SSO registration failed. To remedy this:
- Verify that the certificate file specified in vcsso.properties is valied.
- Varify that the clock in the Single Sign In system and the vCenter Server system are in sync.
- Check the vm_ssoreglog in the system temporary folder for more details on the error.
Search the VMware knowledge base (http://kb.vmware.com) for "Error 29113" for more information"
1. Server Clean-installed with Windows 2008R2 +all updates
2. Server has fixed IP address and is member of Active Directory Domain
3. Server has manually installed DNS-suffix in IP settings
3. I can resolve FQDN using nslookup
4. I use only letters, numbers and a "_" sign in my password.
5. Server time is correct
6. I use the latest build of vCenter 5.5c (VMware-VIMSetup-all-5.5.0-1476387-20131201). The same issues were with the previous builds.
Any help would be greatly appreciated.
Amazing work TanyaVM, it turns out I had the same issue. My default OpenSSL is also v1.0.1. I went ahead and duplicated the Windows orientated instructions from that KB article and was able to get inventory service working. Thanks for posting the solution.
Ok, so in digging through all the documentation I can find, and barring my next steps of opening a packet sniffer, I am trying to get a real deep dive on how the vDS Health Check works. So, the documentation says it uses a Layer2 echo protocol, which is an ICMP ping, to check the VLAN configuration. So, if this is the case, how does it do this on VM Networks without any VMK ports and IP addresses? Does it randomly pick from an assigned IP Pool, meaning an IP Pool is required? Also, since it only checks the next hop, in blade enclosures, how does this actually help since the next hop will be the Virtual Connect (in HP land)?
Amigos,
Alguém já se deparou com essa mensagem? estou tentando instalar o SSO, li vários posts comentando da complexidade da senha, mas já tentei de tudo, até gerador de senhas e nada !!!
I understand Layer2 ping as arp ping using mac addresses and not ip addresses.
It should communicate among vdSw uplinks over L2 so it should be independent on HP virtualconnect VEPA Or cisco VN-TAG Ethernet enhancements.
Worked for me too, thanks TanyaVM.
VMware support had me increase the timeout value in the vSphere client for the server which has seemed to help. Administration -> vCenter Server Settings -> Timeout Settings -> Normal Operations - change from 30 seconds to 60 seconds.
Hi,
we are constantly getting these errors in the VCenter Event log. These errors are filling up our SQL Database.
Is there any way to find the cause for these errors, or a way to disable these errors?
Any help appreciated...
I am testing in preparation to upgrade vSphere from 5.0 to 5.5. One thing I have noticed is the web client seems to have a problem with IE 11. I get this message in a bar at the top of the browser:
This browser is not supported. Some features might not work correctly. A minimum of IE7, Firefox 9 or Chrome 14 are required on Windows. A minimum of Firefox 9 or Chrome 14 are required on Linux. A minimum of Firefox 9, Chrome 14 or Safari 5.1.3 are required on Mac OS X. Read the vSphere Web Client help for details.
Is there a fix for this? It seems safe to ignore this message, everything seems to work ok, but I don't really want to field all the questions about this message when 5.5 is deployed.
Thanks
Matt
It is actually not supported
vSphere 5.5 Documentation Center
You will have to wait for next release i guess.
Can anyone tell me how to mount a USB drive to vCenter Server Appliance 5.5?
I would like to copy over some Bash scripts I've created in another VM.
I've added a USB controller and tried adding both Client connected devices and Host connected devices but fdisk -l never lists the drive and lsusb is not a recognised command.
I am having problems in our Vcenter, one of the host just diconnected and when we try to re connect it it goes up untill 89% and then comes up with an error "Internal error : vmodl.fauly.hostcommunication". we dont use DNS but ping from vcenter to host responds fine, ping from host to vcenter works fine. telnet from either on port 902 is also working fine. the vxpa agent service is running on the esxi host. esxi host is versin 5.0. Host is part of HA in a cluster. we can connect to host directly via vshpere client. I have deleted the vpxuser from host, unistalled the vcenter agent and then tried connecting to host again and same problem. I have also removed host from Vcenter and when I try adding it back I get the same error. I have also tried adding host to another Vcenter and same problem. Any one experienced this problem before.
Dear all,
Please advise, steps by steps of Migrate vCenter 4.0 Standard from one physical host to another physical host (different IP Addresss) with vCenter 5.5 Standard.
Existing vCenter 4.0 Standard Configuration
OS: Windows Server 2003 Standard Edition
Database : SQL 2005 Express, bundle with vCenter.
Thanks,
Natthaphol
Just make sure there are no users logged in into the vCenter(or if its in use you could do it in off hours when the load is less). And migrate it like you migrate any other machine. Make sure the vMotion requirements are met.