There has been some discussions around what the total number of VMware vCenter Concurrent vSphere Client Connections is. Currently there is no limit, but it is recommended to keep this at a total of 30. Anything over this total and performance issues may be experienced. It also depends on how you use the vSphere Client. If you have fewer entities opened in the inventory tree, your vSphere Client puts less burden on the vCenter server therefore it may support more vSphere Client without noticeable performance downgrade. Why? Because for every opened managed entity like virtual machine, the vSphere Client asks vCenter to monitor its status using vSphere PropertyCollector API. The more to monitor, the more burden on the vCenter of course. Thanks to Steve Jin (DoubleCloud.org) for providing the above information.
Tag Archives | vcenter
The New Resource Pool option is grayed out
So today I have been building my home cloud, and came across a little useful point that I had forgot about. When you try to create a resource pool within a cluster, the New Resource Pool… Menu option is greyed out. Now for a couple of seconds I was a little confused, why is this? Then of course I remembered, I had not enabled DRS yet on my cluster (there is currently only one host). I enabled DRS and the option is now available. You can also find an VMware KB article on this here.
How To: Install VMware ESXi from USB
I haven’t done this in a long time, due to working on large customer accounts that use automated build processes to build all there ESXi servers, but I needed to do this for my home lab, so thought I would post how to configure a USB key to boot into the ESXi installer. Handy if you have no CD/DVD drives. I used Windows to carry out this. 1) Download the latest version of Syslinux. Current version (At the time of writing) 4.02 – Download here 2) Insert the USB key. It will require about 300 MB free space for the ESXi install files and should be formatted as FAT32. 3) Run c:syslinuxwin32syslinux.exe <drive letter> – This alters the boot partition on the USB key and copy over the file ldlinux.sys to the root directory. 4) Mount the ESXi Install ISO and copy the contents to the USB key. 5) On […]
Cannot install the vCenter agent service Not enough space to install agent ESXi 4.x
I have been building a very basic home lab today, and came across this error when trying to add the host into vCenter. “Cannot install the vCenter agent service. Not enough space to install agent.” I began investigating the error, which to me sounded like a disk space error. The host is running ESXi 4.1 off a USB key. I checked the disk space and all was fine and acceptable. What I discovered was that a VM that was running on the host had eaten a huge chunk of memory, and there was only 128MB free (this host only has 2GB RAM, not ideal I know). I stopped a few of the VMs which free’d up some memory, and then tried to add the host to vCenter again. Everything worked well.
VMware vCloud Director – Q&A – Part 2
This is part 2 of the Q&A article published last week. If anyone has any more questions regarding VMware vCloud Director please post a comment and I will try to answer your questions as soon as possible. vCloud Director Network Isolation (vCD-NI) Q. What limits exist when creating a vCD-NI-backed network pool? A. You are limited to the maximum number of ephemeral portgroups you can have per vCenter Server, which is 1016. (This is the same as a VLAN-backed network pool. Q. How does vCD-NI scale past the 802.1q limit of 4096? A. The 802.1q protocol (in standard implementations) tops out at 4096 VLANs. The use of vCD-NI requires at most one VLAN per network pool for the transport network. Q. Is vCD-NI provided as part of vShield Edge? A. No, it is built into the VMkernel. This is why the product supports a minimum of vSphere 4.0 U2 or […]