VMware KB: Implementing CA signed SSL certificates in vSphere 6.0.
This is a big change from previous CA/PKI components provided from VMware.
VMware KB: Implementing CA signed SSL certificates in vSphere 6.0.
This is a big change from previous CA/PKI components provided from VMware.
VMware KB: Best practices for configuring OSPF areas with VMware NSX for vSphere 6.x logical routers.
Just putting this here for reference in my current SDDC project. The best practices described are essentially a common sense approach.
VMware KB: Important information before upgrading to vSphere 6.0.
Chock full of links to critical information for anyone considering an upgrade to vSphere 6. Updated today.
We have been waiting for this update to be released since it was mentioned at PEX in February. Now to get it into the lab!
VMware KB: User Name and Password fields does not appear on the vRealize Automation login page.
This problem is between the vRealize Automation 6.2 Client integration plug-in and recent versions of Firefox.
As a workaround, you may be able to move the horizontal scroll bar, causing the screen to be redrawn, thus revealing the username and password input boxes.
Internet Explorer 11 appears to be pretty well behaved and the latest versions of Chrome also work well, though the Flash components may be old.
VMware KB: Registering NSX Manager to vCenter Server or configuring the SSO Lookup Service fails with the error: nested exception is java.net.UnknownHostException.
I have seen this error with customer installations. Even if you don’t run across the error, this KB contains very succinct instructions for troubleshooting basic infrastructure requirements for NSX Manager.
A couple of students mentioned this error during a lab in the VMware NSX: Install, Configure and Manage class this week.
The issue is simple to create and remedy. Logical switches are assigned VNI (VXLAN Number Identifier) from a Segment ID Pool. If the Segment ID Pool is not configured before you try to provision a logical switch then you will get the “Unable to allocate an available resource” error. The resolution is to configure the Segment ID Pool before attempting to create Logical Switches.