In my earlier post vCenter Server 6.* – Replacing SSL certificates with Custom VMCA I described how you can replace SSL certificates with Custom CA certificates. Today in post vCenter Server 6.* – Replacing SSL certificates with Enterprise VMCA I would like to guide you through replacement of VMCA self-signed SSL certificate with Microsoft CA certificates. This will allow you to take advantage of VMCA as a single point of certificate management in your environment while ensuring that
Certificates are very common in our daily life. Starting from logging to your banking account, checking email or simply visiting social media, we use secure communication. One of ingredients of it are certificates. I will not describe you in details how do we use them – if you are reading this most likely you know what you are doing.
Please note that this class is delivered using electronic books ONLY; you will either need one of the following to complete this course: one 23″ monitor, two smaller monitors, an android tablet or an IOS tablet in order to see the manual and execute the lab. No printed material will be provided with this class. You will receive a redemption code with instructions on how to download the eBook no later than 3 days before the class is scheduled to start. Please ensure this is complete before the class starts.
Today I received the official notification from Corey Romero that I had been selected as one of the first NSX vExpert holders. After that i am very happy and I’m very excited to be working with NSX Evangelist.
I am very humbled to be part of such a select group of the vExpert community.
A lot of the customers I talk to who are considering virtualizing their network ask what the “overhead” or “performance penalty” is for running NSX. The general answer is “so low that you probably won’t be able to measure it”. For some people, that’s not enough. They want to know an exact figure for, say, the latency added for east-west VM communication when the NSX Distributed Firewall is enabled. Or how much latency is added by using VXLANs instead of native VLANs with the software VTEPs built into NSX? Or what is the latency introduced when I go from a VM on a VXLAN through an Edge Security Gateway to a physical server on a native VLAN?