I’ve been having some performance issues with my VCSA on vSphere 5.5. Since I’m running Essential Plus, I do not have the “Hot Add” capability. Therefore, in order to add memory to my VCSA I have to shut it off.
I fired up my vSphere Thick Client right clicked on my VCSA and went to “Edit Properties”. I got this error, as expected.
Which basically means that even if I turn off my vCenter server, I cannot add RAM. It HAS to be done though the Web Client since I’m running vmx-10.
The other option I have is to use PowerCLI. Once logged directly into the host, I ran “Get-VM VCSA” and got the below results.
MemoryGB = 8 was what I was expecting. Since I’ve been having problems, I’m going to go up to 10GB.
First I had to power off my VM, since I was already in PowerCLI I just did it all though command line. The command for this is “Shutdown-VMGuest VCSA”
I then verified it was powered off by running “Get-VM VCSA” again.
I then ran “Set-VM VCSA -MemoryMB 10240”. The key to this is to notice that the memory is in MB and not GB (like in the above screen shot). I then verified the MemoryGB by running “Get-VM VCSA” again.
I then powered on my VCSA by using “Start-VM VCSA” command. Once everything was back up, I double checked to verify amount of memory.
This wasn’t very difficult to do, and can be done pretty easily if you have a small understanding of PowerCLI. However, I found it pretty useful to have in one spot.
Having some issues with our storage, I had to create some new datastores and move virtual machines over to the new datastores. I thought it seemed easy enough, even having Essentials Plus licensing. I just took the server offline moved it and turned it back on. This worked for every server…except one…vCenter. I started searching around online and found some blogs pointing to utilizing SSH and the ‘vmware-cmd’ command. I typed that in, and got the error: “-sh: vmware-cmd: not found”
I then started to think, why not use both GUI and command line. I shutdown my vCenter server and unregistered by browsing into my datastore. After that I moved over to my SSH session with my ESXi host.
I used the command mv…
mv /vmfs/volumes/51926e41-5a58b725-cb40-782bcb19c270/vCenter /vmfs/volumes/5203e77b-392d6e9c-61a6-782bcb19c26c/vCenter
I got the 51926e41-5a58b725-cb40-782bcb19c270 from vSphere Client, highlighted below.
After the move (mv) command, I added the vCenter server into the inventory and powered it up.
I recently upgraded my VMware licensing to vSphere 5.1 Essentials Plus. With this I was able to utilize HA in a cluster. Since enabling HA, I’ve been getting this error:
Host hostname currently has no management network redundancy
It took me awhile to actually figure out what was wrong, and I couldn’t remember that it actually happened when I added the host to the cluster. Anyway, here is the link to the VMware article that solved my problem. Hopefully this helps someone find the answer faster than I did.