The next part of the NSX deployment is to get the NSX Manager registered with vCenter. The first thing to do for this is to browse to the NSX Manager IP that you chose during the OVF deployment. You will be presented with a login screen as seen below.
VMware NSX for vSphere was announced at VMworld 2013. The surprising thing is there is not a lot of information available on how to install and configure it. So I set off on this venture and I thought I would share the information. NSX for vSphere is a combination of technologies from the traditional vCloud Network & Security (vCNS) as well as technologies from the Nicera acquisition. The underlying overlay protocol that NSX for vSphere uses is VXLAN, but it takes VXLAN to the next level by allowing unicast VXLAN and eliminates the requirement for multicast routing.
I will have a four post series on the steps from A to Z on how to install and configure NSX for vSphere. This first post will focus on how to install the NSX Manager. The NSX Manager is the API interface to the NSX Control Cluster. The NSX Manager comes in the form of an OVA template.
Vmware has made available their Disaster Recovery as a Service (DRaaS ) offering. It will be served out of the vCloud Hybrid Service datacenters. It is powered by the time proven VMware Site Recovery Manager and VMware Replication appliance.
The service is intended for mid-sized companies and promises to be a seamless integration with existing vSphere-based infrastructures. At a starting price of $835/month the service seems poised to hit the ground running.
When looking into performance on a virtualized workload, one of the most important statistics to watch is CPU Ready Time.
What is CPU Ready Time, you ask?
Well, CPU Ready Time is the amount of time that a vCPU is waiting for a time slot on a physical CPU core. In other words, if you are seeing a high CPU Ready Time, that means that your host is having a high amount of CPU contention and may be over subscribed.
There is a great VMware KB Article that explains how to calculate CPU Ready % from the CPU Ready summation values that you find on the performance tab in the vClient:
Converting between CPU summation and CPU % ready values
Sizing VM’s appropriately is very important. Just because you have a physical server that has 8 cores does not necessarily mean that its VM counterpart needs to have as many vCPUs. The best approach is to start small and grow as needed. A VM that is oversized can actually perform worse than one that is undersized.
After spending the last week in training, I was doing some research on memory management in ESXi. In doing so, I ran across one of the most amazingly clear depictions of memory flow from the inside of ESXi:
If you want to get it in PDF format, there is a downloadable version available on the VMware KB article:
VMware vSphere 5 Memory Management and Monitoring